Truck-tablet interface

Abstract

A material handling vehicle includes a distributed processor system including a vehicle network that facilitates exchanging information with vehicle electronic components and a distributed multi-processor vehicle control architecture. The distributed multi-processor vehicle control architecture includes an embedded information hub having a hub processor communicably coupled to the vehicle network and a tablet having a tablet processor, wherein the tablet is communicably coupled to and detachable from the distributed multi-processor vehicle control architecture. When the tablet is detached from the distributed multi-processor vehicle control architecture, the hub processor functions as a master processor that communicates with the vehicle electronic components by communicating across the vehicle network therewith. When the tablet is communicably attached to the distributed multi-processor vehicle control architecture, the tablet processor functions as a master processor and the hub processor functions as a slave processor.

Description

Technical Field

[0001] This embodiment generally relates to a material handling vehicle with a computer control interface, and more specifically, to a material handling vehicle that incorporates a conventional tablet computer (e.g., a ruggedized tablet computer) as an interface. Background Technology

[0002] Material handling vehicles are typically used for picking inventory in warehouses and distribution centers. Such vehicles usually include a power unit and a load-carrying assembly, which may include load-carrying forks. In a typical warehouse implementation, the management system directs the tasks of the material handling vehicle operators, for example, by instructing them where and / or how to pick, pack, store, move, temporarily store, process, or otherwise move items within the facility. Summary of the Invention

[0003] According to various aspects of this disclosure, a material handling vehicle communication system includes a vehicle network, an embedded information core, and a tablet computer. The vehicle network facilitates information exchange with electronic components associated with the material handling vehicle. Thus, for example, the vehicle network can be implemented as a network integrated with the material handling vehicle, such as a CAN bus, RS422 bus, etc. The embedded information core includes a core processor network communicatively coupled to the vehicle network. In this respect, the embedded information core can be integrated with the material handling vehicle. Furthermore, the tablet computer includes a tablet computer processor. When the tablet computer is communicatively coupled to the embedded information core, the tablet computer processor operates collaboratively with the core processor to define a distributed multiprocessor vehicle control architecture, wherein the core processor and the tablet computer processor cooperate to exchange at least one vehicle parameter between the tablet computer and an associated vehicle electronic component within the vehicle electronics.

[0004] In some embodiments, when the tablet computer is communicatively coupled to an embedded information core, the tablet computer processor is used as an auxiliary processor for the core processor, thereby defining a distributed multiprocessor vehicle control architecture, wherein the core processor and the auxiliary processor cooperate to exchange at least one vehicle parameter between the tablet computer and an associated vehicle electronic component in the electronic components.

[0005] According to another aspect of this disclosure, a process for modifying the operation of a material handling vehicle is provided. The process includes receiving an electrical signal representing an instruction to modify the operating conditions of the material handling vehicle. In this regard, the instruction is received from a tablet computer, and the instruction is formatted using an open standard communication protocol. In some embodiments, the open standard communication protocol is open, but the information itself is obfuscated or encrypted so that it cannot be easily or readily intercepted, understood, or used in an unintended manner. The process also includes converting the instruction received using the open standard communication protocol into a modification command that modifies associated electrical components of the material handling vehicle based on parameters extracted from the instruction. Furthermore, the process includes transmitting the modification command to the electrical components of the material handling vehicle via the vehicle network. Here, the electrical components receive the modification command and change their operating state, thereby causing a comprehensive modification to the operation of the material handling vehicle.

[0006] According to another aspect of this disclosure, a process for protecting access to a material handling vehicle is provided. The process includes coupling a tablet computer to the material handling vehicle via a wired open standard communication protocol, and receiving a first device identifier of the tablet computer coupled via the wired open standard communication protocol. The process also includes storing the first device identifier in a memory. The process further includes receiving a second device identifier via a wireless open standard communication protocol. Optionally, the process may include determining whether another device has already been coupled to the material handling vehicle via a wireless open standard communication protocol. Moreover, the process includes coupling the tablet computer to the material handling vehicle via a wireless open standard communication protocol if another device has not yet been communicatively coupled to the material handling vehicle via a wireless open standard communication protocol and the second device identifier matches the first device identifier. Attached Figure Description

[0007] Figure 1 This is a flowchart of the enterprise's material handling vehicles based on various aspects of this disclosure;

[0008] Figure 2 This is a block diagram of specialized handling equipment on material handling vehicles based on the various aspects disclosed in this text;

[0009] Figure 3A This is an example illustration of a tablet computer;

[0010] Figure 3B yes Figure 3A An illustration of a tablet computer mounted on a material handling vehicle implemented as a forklift;

[0011] Figure 4 This is a block diagram illustrating the communication and control configuration of the tablet computer interface to the material handling vehicle;

[0012] Figure 5This is a block diagram of another communication and control configuration for interfaced tablet computers to material handling vehicles;

[0013] Figure 6 This is a flowchart illustrating the process of transmitting commands to material handling vehicles;

[0014] Figure 7 This is a flowchart illustrating the process of modifying the operation of a material handling vehicle according to various aspects of this disclosure;

[0015] Figure 8 This is a flowchart illustrating a process for protecting access to material handling vehicles according to various aspects of this disclosure; and

[0016] Figure 9 It is a block diagram of a computing system capable of performing the various aspects of this disclosure. Detailed Implementation

[0017] According to various aspects of this article, removable, replaceable handling devices (hereinafter referred to as “tablets” for convenience) are integrated with material handling vehicles, for example, to function as if the tablets were original equipment manufacturer (OEM) parts.

[0018] As used herein, the term “tablet computer” is intended to include portable devices such as tablet computers, general-purpose tablet computers, ruggedized tablet computers, computers, smartphones, laptop computers, specialized appliances, Internet of Things (IoT) devices, specialized computing devices, information processing and / or collection devices, or other devices capable of communicating via a network 104 and performing one or more of the functions described herein.

[0019] In practical applications, portable devices (i.e., tablets) typically include a touchscreen or a non-touchscreen display. Portable devices may also optionally include one or more user input controls (e.g., a collection of user input controls, such as buttons, switches, encoders, or combinations thereof). In this regard, portable devices can run readily available operating systems such as Android (a registered trademark of Google, Inc., Delaware, Inc.), Windows (a registered trademark of Microsoft, Inc., Delaware, Inc.), Linux (a registered trademark of William R. Della Croce, Jr., Massachusetts), macOS (a registered trademark of Apple, Inc., California, Inc.), iOS (a registered trademark of Cisco Technology, Inc., California, Inc.), and so on.

[0020] The processing device can also run a proprietary operating system. It also includes a data processing circuitry system, including a processor and memory. Furthermore, the processing device includes connectivity features, including wireless connectivity, such as via Wi-Fi (Wi-Fi is a registered trademark of the Wi-Fi Alliance, Inc., California), Bluetooth (the Bluetooth word mark and logo are registered trademarks of Bluetooth SIG, Inc., Delaware), ultra-wideband, cellular (including 5G), etc. Connectivity features may also include wired connectivity, such as via USB, serial ports, etc.

[0021] In some embodiments, a tablet computer effectively replaces one or more typically required embedded and / or vehicle-mounted components. For example, in some embodiments, the tablet computer decouples material handling vehicle hardware (e.g., traction controllers, hydraulic controllers, and other conventional vehicle electronics) from the technical hardware typically required to interface such material handling vehicle hardware to end users (e.g., operators, maintenance technicians, or other users) (e.g., processor chips, memory, transceivers(s), touchscreen technology, user input / output, etc.). This approach effectively utilizes the tablet computer as a portable, replaceable device for the technical hardware portion of electronic systems that are expected to change over technology cycles (wireless radios, displays / touchscreens, processing power, memory speed and / or memory size, etc.), allowing for a flexible architecture that can be rapidly updated and is less effort-intensive to upgrade than a fully embedded approach.

[0022] In this regard, when properly coupled, the tablet computer is integrated with electronic components (e.g., native material handling vehicle electronics, original equipment manufacturer (OEM) electronics, electronic add-ons, electronic peripherals, other electronic components on or associated with the material handling vehicle, or combinations thereof). As some non-limiting examples, the tablet computer can serve as a graphical user interface, redundant displays, dual displays or auxiliary displays, communication interfaces for exchanging information with equipment located remotely from the material handling vehicle, redundant or auxiliary communication devices, processing devices for controlling certain functions of the material handling vehicle, combinations thereof, etc.

[0023] Furthermore, in some embodiments, the tablet computer can display data generated by other control electronics on or associated with the material handling vehicle, data from accessories associated with the material handling vehicle, data wirelessly received from remote devices (such as remote servers or other electronic devices), directly and locally computed and displayed data, or a combination thereof. For example, this allows vehicle operation data to be distributed from a standard dashboard or instrument panel, thereby allowing the operator, for instance, to position the display of vehicle data in a location convenient for performing tasks requiring relocation within the operator's cab of the material handling vehicle.

[0024] In some embodiments, the tablet computer may send data including commands to one or more electronic components to control the functions of a material handling vehicle, receive commands from the material handling vehicle to perform processing within the tablet computer, send information to a remote device (such as a remote server or other electronic device), receive commands from a remote device to perform processing within the tablet computer, or a combination thereof.

[0025] Therefore, tablet PCs can replace some of the functions typically reserved for embedded systems (e.g., telematics modules, processing modules, user I / O modules, etc.) that are limited in terms of functionality and development cycle. In this respect, tablet PCs effectively replace many components that would otherwise be required in embedded systems. However, tablet PCs can be detached from material handling vehicles and can be exchanged with different tablet PC instances, thus allowing for easy upgrades and / or replacement of multiple technology systems with a single exchange.

[0026] In other embodiments, the tablet computer delegates non-operationally critical processing, enabling the material handling vehicle to function normally and be fully operable without the tablet computer. However, when the tablet computer is integrated with the material handling vehicle's embedded systems or other electronics, enhanced processing and / or operational capabilities, features, information presentation, information processing, and combinations thereof are achieved.

[0027] An improved overall vehicle computer architecture is provided by collocating technical features that include hardware and software that are updated and / or require servicing at relatively rapid intervals (e.g., touchscreens, processors, memory, user interaction software, etc. in a tablet)—measured over cycles ranging from months to years—and by collocating more robust but more difficult-to-upgrade, repair, or change electronic features (e.g., vehicle network bus interfaces, vehicle configuration managers, vehicle monitoring processors, etc., which are components natively integrated into the vehicle)—measured over cycles ranging from five to ten years, up to the vehicle's lifespan. This improved vehicle computer architecture enhances the hardware upgradeability of conventional vehicle computer systems by facilitating security features that can be easily monitored, updated, and upgraded; providing effective and persistent network vulnerability monitoring and patching; and improving the efficiency and maximizing the lifespan of processing hardware by distributing tasks in a multiprocessor environment, enabling task sharing, parallel processing, redundant communication, and other technical features described more fully herein.

[0028] System Overview

[0029] Now refer to the attached diagram, especially Figure 1 The schematic diagram illustrates a material handling vehicle system 100 according to various aspects of this disclosure. The material handling vehicle system 100 is a dedicated (specific) computing environment that includes a plurality of hardware-equipped processing devices 102 linked together via one or more networks 104.

[0030] Network 104 provides communication links between various processing devices 102 and can be supported by networking 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 (one or more) 104 can include connections using one or more network configurations, examples of which include intranets, extranets, local area networks (LANs), wide area networks (WANs), wireless networks (Wi-Fi), the Internet (including the World Wide Web), cellular networks, and / or other arrangements for enabling communication between the processing devices 102.

[0031] The processing device 102 may be implemented as a server, computer, tablet computer, smartphone, purpose-driven appliance, Internet of Things (IoT) device, dedicated computing device, information processing and / or collection device in a vehicle, information processing and / or collection device in a machine (fixed or mobile), or other device capable of communicating via network 104.

[0032] Specifically, the processing device 102 is provided on one or more material handling vehicles 108. In the example configuration shown, the processing device 102 on the material handling vehicle 108 wirelessly communicates with a corresponding networking component 106 via one or more access points 110, the networking component 106 serving as a connection to one or more networks 104. Alternatively, the material handling vehicle 108 may be equipped with cellular or other suitable wireless technologies that allow the processing device 102 on the material handling vehicle 108 to communicate directly with remote devices (e.g., via one or more networks 104).

[0033] System 100 also includes processing devices that are implemented to support platform 114 and corresponding data sources (collectively referred to as data source 116) server 112 (e.g., web server, file server and / or other processing devices).

[0034] Material handling vehicles 108 typically operate in work environments such as warehouses, distribution centers, and retail establishments. Therefore, platform 114 provides monitoring, management, control, or a combination thereof for material handling vehicles.

[0035] In the illustrative example, data source 116 does not need to be located in the same place to assemble data from multiple different domains for the benefit of the enterprise. In the illustrated example, data source 116 includes material handling vehicle information data source 118, which collects data from the operation of material handling vehicles 108 in, for example, the material handling vehicle domain. For example, material handling vehicle information data source 118 may store electronic vehicle records, for example, wirelessly received from the fleet of material handling vehicles 108 via access point 110 or other means. In this respect, each electronic vehicle record may include driving-related data, operational data, maintenance data, observation data, configuration data, or other information recorded, collected, generated, etc., by processing equipment 102 on the relevant material handling vehicle 108 operating in the working environment.

[0036] Data source 116 may also include management system data source 120, such as a warehouse management system (WMS). The WMS associates information with the movement and tracking of goods in the work environment within the WMS domain.

[0037] Furthermore, data source 116 may include one or more other data sources required by the work environment, such as a workforce management system (LMS) 122, a geographic location system 124, etc. The above list is not exhaustive and is for illustrative purposes only.

[0038] Material handling vehicles

[0039] refer to Figure 2 The diagram illustrates system 200, which includes material handling vehicle 108. Figure 1The selected electronic component. For example, a processing device 202 is illustrated, which can be mounted on a material handling vehicle or supplied natively to a material handling vehicle (OEM). The processing device 202 is... Figure 1 An example embodiment of the processing device 102 on the material handling vehicle 108. Here, the processing device 202 is a dedicated, specific hardware device.

[0040] The processing device 202 shown is implemented as an embedded information core 204, which can interface with the tablet computer 206. When coupled together, the embedded information core 204 and the tablet computer 206 define a distributed, multiprocessor vehicle control architecture.

[0041] Embedded Information Core

[0042] The embedded information core 204 is typically implemented as a native electronic embedded processing system. In some embodiments, the embedded system is a system permanently or semi-permanently mounted to the material handling vehicle. That is, in some embodiments, the embedded information core 204 represents hardware designed to remain coupled to the corresponding material handling vehicle. In this regard, the embedded information core 204 can be integrated directly into the vehicle's electronics, either alone or in combination with other electronic devices. In alternative embodiments, the embedded information core 204 is packaged in a housing that can be mounted, attached to, or otherwise mounted to the corresponding material handling vehicle.

[0043] In the illustrative example, the embedded information core 204 may optionally be communicatively connected to a transceiver 212 for wireless communication, or may optionally include a transceiver 212 integrated therein. In practice, the transceiver 212 may implement one or more wireless communication technologies (e.g., Wi-Fi, Bluetooth, ultra-wideband (UWB), cellular, radio frequency (RF), infrared (IR), any other wireless technology, or combinations thereof). Moreover, each technology may include one or more antennas, for example, for redundancy, for location / position determination, for reliability, or combinations thereof. For example, the transceiver 212 may be able to cross... Figure 1 Access point 110 connects to a remote server (e.g., via 802.11) via 802.11. Figure 1 Communicating with server 112. For example, using a cellular transceiver that communicates with a 5G router or other form of cellular-to-IP (Internet Protocol) bridge, transceiver 212 may be able to use cellular signals to communicate directly with a remote server (e.g., a manufacturer's server).

[0044] As an illustrative example, transceiver 212 may include communication technologies such as Bluetooth. This allows information core 204 to communicate with nearby Bluetooth-enabled devices. For example, a corresponding material handling vehicle may include a battery as a power source. Battery monitor 214 may be coupled to the battery to measure and record battery characteristics, such as current discharge, temperature, resistance, etc., for measuring and / or calculating remaining battery capacity, battery health status, battery state of charge, etc. Here, battery monitor 214 may include a Bluetooth transceiver paired with transceiver 212, enabling information core 204 and battery monitor 214 to share information.

[0045] As another example, transceiver 212 may include an ultra-wideband (UWB) transceiver in addition to or in place of Bluetooth. The UWB transceiver can be used to create temporary local mesh networks to facilitate communication with electronic badges used for truck and pedestrian tracking, and with UWB-enabled devices(s) such as anchors, tags, talking markers, etc. Here, the UWB transceiver may include multiple antennas (e.g., two or more antennas) so that the information core 204 can perform localization, position determination, distance determination, distance, direction, and orientation measurements of nearby corresponding UWB badges, etc.

[0046] As yet another example, the transceiver may include a 5G wireless device for communicating with a 5G network, which may be local (e.g., within a facility), outside a facility, etc.

[0047] In an example embodiment, transceiver 212 is connected to processing device 202 via a suitable electrical connection 216 (e.g., Ethernet connection, USB connection, etc.). However, transceiver 212 may be integrated into information core 204 using other connectivity methods, or it may be omitted entirely. For example, in some embodiments, transceiver 212 is a component of a material handling vehicle. In other embodiments, transceiver 212 is integrated into information core 204. In still other embodiments, the information core itself does not include transceiver 212. Here, one or more transceivers may be integrated into or otherwise coupled to tablet computer 206. In this respect, the transceivers(s) of tablet computer 206 may implement any combination of the functions described with reference to transceiver(s) 212.

[0048] In other embodiments, multiple transceivers or transceiver instances may exist, for example, for different purposes, for redundancy, to support vehicle functionality when the tablet is unavailable, to support different communication protocols, or combinations thereof. In this example embodiment, the embedded information core 204 and the tablet 206 may each include at least one transceiver that may implement the same or different communication protocols.

[0049] The embedded information core 204 also includes a data processing circuitry, such as a controller 218 illustrated. The controller 218 includes a processor coupled to memory for implementing computer instructions, including related processes or aspects thereof, as set forth and described more fully herein. The controller 218 may also include other necessary processing circuitry and software, such as for implementing a display engine, a camera processing engine, one or more data processing engines, etc.

[0050] Furthermore, the memory of the controller 218 may include memory for storing processing instructions and memory for data storage, for example, to implement one or more databases, data repositories, registers, arrays, etc.

[0051] The embedded information core 204 may also include additional support circuitry 220 necessary to support the functionality of the controller 218. As a non-limiting example, example additional circuitry 220 may include video ports, camera ports, input / output ports, interfaces (e.g., universal serial bus interfaces, spring-loaded interfaces, Bluetooth interfaces, one or more network interfaces, etc.), event stacks, processing stacks, configuration data management, client management, event management, etc.

[0052] The processing device 202 may also optionally include or otherwise communicate with a vehicle power activation circuit system 222. The vehicle power activation circuit system 222 is controlled by a controller 218 to selectively enable or disable the material handling vehicle 108 and / or selectively enable or disable selected components of the material handling vehicle 108. In some embodiments, the controller 218 controls the vehicle power activation circuit system 222 to partially enable or fully enable the material handling vehicle, for example, based on correct operator or service technician login. For example, the material handling vehicle power activation circuit system 222 may provide selective power to components via appropriate power connections or otherwise command certain vehicle components not to respond to vehicle operator control via vehicle messaging (e.g., across one or more vehicle communication buses).

[0053] In some implementations, the information core 204 includes monitoring input / output (I / O) capabilities to communicate via wired or wireless connections with peripheral devices (such as cameras, sensors, lasers, meters, encoders, light strips, switches, Internet of Things (IoT) devices, etc., collectively indicated by reference numeral 224) mounted to or otherwise mounted on the material handling vehicle. The information core 204 may also communicate via wired or wireless connections with third-party devices 224 (such as RFID scanners, displays, barcode scanners, or other devices).

[0054] Information core 204, particularly controller 218, is coupled to and / or communicates with other material handling vehicle system components via a suitable material handling vehicle network 226 (e.g., at least one bus). Material handling vehicle network 226 refers to any wired or wireless network, bus (or multiple buses), or other communication capability (or a combination of multiple independent networks, buses, or other communication capabilities) that allows the electronics of material handling vehicle 108 to communicate with each other. As an example, vehicle network 226 may include one or more Controller Area Network (CAN) buses (or multiple CAN buses), Zigbee (Zigbee is a registered trademark of Connectivity Standards Alliance, California, Inc.), Bluetooth, Local Interconnect Network (LIN), Time Triggered Data Bus Protocol (TTP), RS422, Ethernet, USB, other suitable communication strategies, or combinations thereof.

[0055] For example, controller 218 can communicate with vehicle electronic components (such as controllers (hydraulic, traction, etc.), modules (such as battery monitors), devices (such as collision sensors), location tracking systems, etc. (collectively referred to as device 228)) across vehicle network 226. Other example devices 228 may include displays, light bars, sirens, sensor systems, navigation systems, IoT devices, data collection devices, communication devices, user interaction devices, etc.

[0056] The controller 218 of the processing device 202 can also communicate with the remote key reader 230 (or keypad, card reader or any other device) to receive operator credentials.

[0057] According to another aspect of this disclosure, the embedded information core 204 can communicate with a location tracking device or system 232 provided on the material handling vehicle 108. The location tracking device or system 232 enables the material handling vehicle 108 to know its spatial location within a local space (e.g., within a warehouse).

[0058] The use of vehicle network 226 enables seamless integration of components of material handling vehicle 108 with embedded information core 204, particularly controller 218. For example, controller 218 can facilitate communication of information from any electronic peripherals or third-party devices 224, one or more controllers (such as one or more devices 228, remote key reader 230, location tracking devices or systems 232, etc.) associated with material handling vehicle 108, which is integrated with and can communicate through network system 226. Therefore, embedded information core 204 connects to, understands, and can communicate with vehicle components such as controllers, modules, devices, bus-enabled sensors, displays, lights, light strips, sound devices, headsets, microphones, haptic devices, peripherals, etc.

[0059] Tablet PC

[0060] As described above, the tablet computer 206 can be implemented as any suitable portable device, such as a tablet computer, a general-purpose tablet computer, a ruggedized tablet computer, a computer, a smartphone, a purpose-driven appliance, an Internet of Things (IoT) device, a dedicated computing device, an information processing and / or collection device, or any other device capable of communicating via the network 104 and performing one or more of the functions described herein.

[0061] In practical applications, tablet computer 206 includes a touch display, a processor, and memory. Furthermore, tablet computer 206 includes connectivity features, including wireless connectivity, such as via Wi-Fi, Bluetooth, ultra-wideband, cellular / 5G, etc. Connectivity features may also include wired connectivity, such as USB, serial ports, etc., or combinations thereof.

[0062] In some embodiments, because the tablet computer 206 is integrated with the information core 204, for example via the supporting circuitry 220, the tablet computer 206 may be unaware of any other devices communicating with the information core 204. Therefore, the tablet computer 206 does not need to know any network system protocols used for communicating across the vehicle network system 226 or otherwise accessing the vehicle network system 226.

[0063] Although Figure 2 A tablet computer 206 is schematically illustrated as being communicatively coupled to an embedded information core 204 via a supporting circuitry system 220 (e.g., via a USB connection). However, in practice, the tablet computer 206 may communicate with the controller 218 of the embedded information core 204 via Bluetooth or other wireless technologies, USB or other hardwired technologies, combinations thereof, etc.

[0064] Brief reference Figure 3A The illustration shows a tablet computer 306, which can be used to achieve... Figure 2 The tablet computer 206 includes a housing 308 having a front surface 310 defining a display section 312 and an optional vehicle operator control section 314. In an example embodiment, a touchscreen display is provided within the display section 312 of the tablet computer 306. In this regard, the tablet computer 306 includes suitable technology to respond to gesture control implemented by touching the screen, pressing or releasing the screen, swiping across the screen, making gestures on the screen (but not touching the screen), performing other gesture functions associated with the display, etc. (collectively referred to herein as gesture commands). In some embodiments, the display may respond to gesture commands that do not strictly require touching the display.

[0065] Furthermore, in some embodiments, the set of controls is arranged within the vehicle operator control section 314 of the tablet computer 306. The vehicle operator control section 314 is optional, but when provided, it may include buttons, switches, sliders, encoders, knobs, voice recognition, keypads, external controls connected to I / O (such as Bluetooth or USB keyboards), other forms of receiving vehicle operator input, and combinations thereof.

[0066] For example, in an example implementation, the set of controls 314 (e.g., function keys) is located in the same location as the touchscreen display. User input controls interact with or control elements in the graphical user interface seen on the touchscreen display, serve as input controls for applications running on the tablet 306, and so on. Depending on the implementation, user input controls may be programmed to function in a specific manner when provided.

[0067] refer to Figure 3B For ease of explanation, Figure 3A The tablet computer 306 is shown as a support rod 352 mounted to a material handling vehicle 108, which is implemented as a seated forklift. In practice, the tablet computer 306 can be mounted in, on, integrated with, or otherwise provided to various types of material handling vehicles, including but not limited to forklifts, telescopic forklifts, inventory picking vehicles, slewing forklifts, tow trailers, pallet jacks, and pedestrian stackers. Here, the housing of the graphical user interface 302 can be mounted inside or outside the corresponding material handling vehicle, for example, via a mounting bracket, mounting baffle, shell, or other suitable structure.

[0068] In this respect, size, shape, and other physical characteristics can vary depending on the application. For example, if the housing 308 of the tablet 306 is installed inside a material handling vehicle, such as to a docking station, then the front face 310 can conform to adjacent structures (e.g., instrument / control clusters, etc.). Moreover, in some embodiments, if the tablet 306 is mounted to a material handling vehicle (e.g., to a support rod 352), additional support structures (such as mounting brackets, wiring harnesses, docking stations, and / or other accessories) can be provided. Therefore, the processing apparatus described herein is adaptable to a variety of installation options for different types and modes of material handling vehicles, including modes with or without an operator (e.g., operator-controlled, semi-automatic, fully automatic, etc.).

[0069] In some embodiments, mounting hardware attaches tablet computer 306 to a material handling vehicle. In some embodiments, the mounting hardware enables easy attachment and removal of the tablet computer, for example, using a ball, quick-connect, snap-fit, slide-in, button release, or other suitable mechanism. In some embodiments, such as when the tablet computer is used as an outward-facing display (e.g., a pedestrian / information display), the mounting hardware may be configurable or repositionable to allow easy positioning of tablet computer 306 for optimal personal viewing by the operator outdoors.

[0070] In other embodiments, the mounting hardware includes a wiring harness that brings electrical connections to the tablet computer. These electrical connections may include power, wired connections to vehicle electronics (e.g., USB bus connections), spring pins, or other suitable connectors.

[0071] Overall reference Figure 2 , Figure 3A and Figure 3B Tablet PCs 206 and 306 can be mounted to and / or detached from material handling vehicle 108, regardless of whether they are communicatively coupled to the material handling vehicle (e.g., coupled to embedded information core 204). Similarly, tablet PCs 206 and 306 can be communicatively coupled to or decoupled from the material handling vehicle (e.g., coupled / decoupled from embedded information core 204), regardless of whether they are mounted to and / or detached from the material handling vehicle. Furthermore, whether mounted or detached, tablet PCs 206 and 306 can be communicatively coupled to embedded information core 204 via wired or wireless connections (and in some embodiments, both wired and wireless connections).

[0072] For example, tablets 206 and 306 can be connected to a material handling vehicle, for example, for charging, but can be coupled to the embedded information core 204 without pairing or otherwise communicating. As another example, tablets 206 and 306 can run one or more applications, such as information displays, pedestrian warning displays, beacons, WMS interfaces, communication interfaces, web browsers, etc., which are independent of vehicle functionality and therefore do not require a connection to the information core 204.

[0073] Similarly, regardless of whether tablet computers 206 and 306 are installed on the material handling vehicle, tablet computers 206 and 306 can be communicatively coupled to or decoupled from the material handling vehicle. For example, as will be described in more detail herein, tablet computers 206 and 306 can be communicatively coupled to the embedded information core 204 of the material handling vehicle via a wired or wireless connection. An operator can remove tablet computers 206 and 306 (if previously installed) and use them, for example, wirelessly coupled to the embedded information core 204 to perform pre-use checklists, take photos of items of interest, scan product information, remotely control truck features (such as vehicle locking functions, automation functions), and provide remote display of truck information. Here, tablet computers 206 and 306 maintain communicative coupling to the embedded information system, regardless of whether they are docked.

[0074] As another example, tablet computers 206 and 306 can display the current vehicle operating status, for instance, via one or more graphical widgets. For example, the widgets can display speed, battery level, fork height, load weight, time, date, shift, vehicle performance tuning, and combinations thereof, wherein the displayed data is discovered or otherwise received from the embedded information core 204. Furthermore, tablet computers 206 and 306 can display vehicle data based on information extracted from controllers on the vehicle (such as timers, task-based schedules, etc.), wherein such data is obtained or otherwise discovered through communication with the embedded information core 204. Other examples are described in more detail herein.

[0075] Truck / Tablet Interface Example 1

[0076] refer to Figure 4 The block diagram illustrates an example truck / tablet interface 400. Similar components are shown in Figure 3, but are 100 mm higher and smaller. Figure 2 Middle and high 200, compared to Figure 1 The reference numerals for the middle and high 300 levels are shown in the accompanying figures. Therefore, the discussion of the preceding figures is... Figure 4 Similarly, this applies to similar / like components.

[0077] Interface 400 includes components that collectively implement processing device 402.

[0078] According to various aspects of this disclosure, the processing device 402 is implemented as an embedded information core 404 and a tablet computer 406, which together define a distributed multiprocessor vehicle control architecture. In this respect, the processing device 402 can implement... Figure 2 The processing device 202. Therefore, similar elements are illustrated using similar reference numerals of height 200. Similarly, similar to processing device 202, processing device 402 is... Figure 1 An example embodiment of the processing equipment 102 on the material handling vehicle 108.

[0079] As shown in the figure, the embedded information core 404 includes an information controller 416. The information controller 416 includes a core processor 418 and memory necessary to perform the capabilities described more fully herein.

[0080] For reference Figure 2 In a similar manner, the embedded information core 404 communicates with vehicle components via a material handling vehicle network 426. For simplicity, the material handling vehicle network 426 is shown as including one or more CAN buses (or multiple buses), an RS422 bus, and an Ethernet bus that couples the information controller of the embedded information core 404 to electronic modules (e.g., controllers, modules, sensors, encoders, etc., such as vehicle control modules (VCM), traction control modules (TCM), hydraulic control modules (HCM), steering control modules (SCM); impact sensors, etc.).

[0081] However, in practice, any combination of vehicle networks or combinations of vehicle networks can be implemented.

[0082] As shown in the figure, the memory of the information controller 416 includes a memory 440 that stores various components of data used by the system. Example data includes client data 442 (e.g., software client (MFRSW client) data from a material handling vehicle manufacturer), truck configuration data 444, and event data 446.

[0083] Client data 442 stores data that is unique to a specific instance of a major component (e.g., embedded information core 404) and allows the major component (embedded information core 404) to uniquely identify itself within the fleet.

[0084] Truck configuration data 444 stores information such as that specific to the associated material handling vehicle, including model, serial number, parts, software version, performance tuning parameters, customization parameters, etc.

[0085] Event data 446 includes, for example, data collected by the system when a material handling vehicle is operated. This may include event codes, error codes, and other messages transmitted across vehicle network 426, data collected by processor 418 when the material handling vehicle is operated, etc. For example, event data 446 may record encounters with geographic features, operator login information, checklist compliance information, and other information generated based on usage.

[0086] The data synchronization manager 450 can be implemented, for example, through a process executed by the processor 418 of the information controller 416, and is responsible for synchronizing the information exchange between the material handling vehicle and external devices (e.g., tablet computer 406, remote server, one or more wireless remote devices, etc.).

[0087] The multi-communication protocol module 452 is a process executed by the processor 418 of the information controller 416 and is responsible for managing the physical communication ports of the main modules, including, for example, USB, Bluetooth, ultra-wideband, cellular, video ports, input / output ports (I / O), and combinations thereof, such as by implementing communication protocols.

[0088] The tablet computer 406 forms an interface to the embedded information core 404 and to the operator of the material handling vehicle. In this regard, the tablet computer 406 includes a tablet computer processor 458 coupled to memory and a data synchronization manager 460 that works with the data synchronization manager 450 of the embedded information core 404.

[0089] The tablet computer 406 also includes a multi-communication protocol module 462 configured to interact with the multi-communication protocol module 452 of the embedded information core 404. For example, the tablet computer 406 shown is coupled to the embedded information core 404 via any combination of USB, Bluetooth, or spring-loaded pins and corresponding pin adapters.

[0090] The tablet computer 406 also includes other functional components, including, for example, program code for handling the display at 464, program code for handling the menu at 466, program code for handling language preferences at 468, program code for managing audio / video / image assets at 470, or combinations thereof.

[0091] Tablet PC 406 also includes one or more transceivers 472 and corresponding stacks, hardware, and software. For example, the illustrated tablet PC 406 includes a Wi-Fi transceiver and a Bluetooth transceiver. Tablet PC 406 may also include a cellular transceiver, an ultra-wideband transceiver, an RF transceiver (e.g., for communicating with RFID devices or NFC (Near Field Communication) devices), etc. In practical applications, any one or more transceivers can be provided in any combination. However, for example, a Wi-Fi transceiver can wirelessly communicate with a remote server, for example, via Wi-Fi and the Internet, Wi-Fi to a cellular gateway, etc. For example, a Wi-Fi transceiver can communicate with a remote server 112 (… Figure 1 Communication. Transceiver 472 may also include a Bluetooth transceiver capable of pairing with nearby Bluetooth devices. Tablet 406 may also include a cellular transceiver. The cellular transceiver can communicate with one or more cellular networks (e.g., via communication with a 5G network, router, etc.), cellular-to-Wi-Fi gateways, etc. Bluetooth transceivers, Wi-Fi transceivers, cellular transceivers, combinations thereof (or any other suitable transceiver technology or combinations thereof) can be used to interact with download tools, service tools, or other devices and / or systems to provide input to tablet 406.

[0092] One or more transceivers are used to enable tablet computer 406 to communicate with applications outside the associated material handling vehicle, such as enabling tablet computer 406 to communicate with cloud storage systems / manufacturer servers (e.g., storing collected truck data and performing manufacturer / truck-specific interactions). Tablet computer 406 can also interact with download tools, such as those provided by the material handling vehicle manufacturer, for downloading software updates, firmware updates, receiving updated parameters, programming, etc. As another example, tablet computer 406 can interact with service tools, such as to log service requests, transmit error or fault codes, facilitate service / maintenance checklists, etc.

[0093] In some embodiments, the embedded information core 404 may further include one or more transceivers 472 and corresponding stacks, hardware, and software. For example, the embedded information core 404 may include a Wi-Fi transceiver, a Bluetooth transceiver, a cellular transceiver, an ultra-wideband transceiver, an RF transceiver (e.g., for communicating with RFID or NFC devices), etc. In practical applications, any combination of one or more transceivers may be provided, as described more fully herein.

[0094] It is worth noting that in the example interface shown, the information controller 416 includes a core processor 418 independent of the tablet processor 458. Similarly, the information controller 416 includes memory independent of the tablet memory. Therefore, the information controller 416 can be used as an information manager. However, the tablet processor 458 can share information stored in the tablet memory with the core processor 418, and the core processor 418 can share information stored in the embedded information core (e.g., memory 440) with the tablet processor 458. Exchanges can occur via push, pull, query, or other interactions.

[0095] Truck / Tablet Interface Example 2

[0096] refer to Figure 5 The block diagram illustrates an example truck / tablet interface 500. Similar components are shown in the diagram. Figure 4 Medium-high 100, compared to the medium-high 200 in Figure 3, compared to Figure 2 The reference numerals for the middle and high 300 levels are shown in the accompanying figures. Therefore, the discussion of the preceding figures is... Figure 5 Similarly, this applies to similar components. As shown, interface 500 includes components that commonly define processing device 502.

[0097] In this respect, processing device 502 is similar to processing device 202, and therefore is Figure 1 An example embodiment of the processing equipment 102 on the material handling vehicle 108.

[0098] According to various aspects of this disclosure, the processing device 502 is implemented as an embedded information core 504 and a tablet computer 506, which are coupled together to create a distributed multiprocessor vehicle control architecture. In this respect, the processing device 502 can achieve... Figure 2 The processing device 202. Therefore, similar components are shown using similar reference numerals at a height of 300. Furthermore, Figure 5 Many functions and features exist in Figure 4 In interface 400. Therefore, similar reference numerals are represented by similar reference numerals with a height of 100. Similar functions are implemented in reference. Figure 4 In the aspects described, this disclosure, through analogy, enables the application of... Figure 5 The differences will be described in detail only.

[0099] As shown in the figure, with Figure 4 The difference is that the embedded information core 504 is logically implemented as two components: an interface component 504A and a management component 504B. Logically, the interface component 504A and the management component 504B constitute the embedded information core 404. Figure 4However, the management component 504B includes an additional transceiver 512 for wireless communication, for example, via Wi-Fi, Bluetooth, ultra-wideband, or combinations thereof.

[0100] As shown in the figure, the embedded information core 504 includes an information controller 516. The information controller 516 includes the processing and memory necessary to perform the capabilities described more fully herein. For example, the information controller 516 includes a core processor 518 and memory 540 storing various components of the data used by the storage system. Example data includes client data 542 (e.g., software client (MFR SW client) data from a material handling vehicle manufacturer), truck configuration data 544, and event data 546.

[0101] The data synchronization manager 550 can be implemented, for example, by a process executed by the processor 518 of the embedded information core 504 (e.g., interface component 504A and / or management component 504B), and is responsible for synchronizing the information exchange between the material handling vehicle and external devices (e.g., tablet computer 506, remote server, one or more wireless remote devices, etc.).

[0102] The multi-communication protocol module 552 is executed by the embedded information core 504 (e.g., interface component 504A and / or management component 504B) and is responsible for managing the physical communication ports of the main module, including, for example, USB, Bluetooth, ultra-wideband, cellular / 5G, video ports, input / output ports (I / O), etc. (See reference...) Figure 2 In a similar manner, the embedded information core 504 (e.g., interface component 504A and / or management component 504B) communicates with vehicle components via a material handling vehicle network 526. For the sake of simplicity, the material handling vehicle network 526 is shown as including one or more CAN buses (or multiple buses), RS422 buses, and Ethernet buses, which couples the embedded information core 504 to several controllers, modules, and devices, such as a vehicle control module (VCM), a traction control module (TCM), a hydraulic control module (HCM), a steering control module (SCM), impact sensors, etc.

[0103] However, in practice, any combination of vehicle networks or combinations of vehicle networks can be implemented.

[0104] The tablet PC 506 forms an interface to the embedded information core 504 (e.g., interface component 504A and / or management component 504B) and to the operator of the material handling vehicle. In this regard, the tablet PC 506 includes a tablet PC processor 558 coupled to memory. The tablet PC 506 also includes a data synchronization manager 560 that works with the data synchronization manager 550 of the main module.

[0105] The tablet computer 506 also includes a multi-communication protocol module 562 configured to interact with the multi-communication protocol module 552 (e.g., interface component 504A and / or management component 504B) of the embedded information core 504. For example, the tablet computer 506 shown is coupled to the main component 504 via any combination of USB, Bluetooth, or spring-loaded pins and corresponding pin adapters.

[0106] The tablet computer 506 also includes other functional components, including program code for handling the display at 564, program code for handling the menu at 566, program code for handling language preferences at 568, and audio / video / image asset management at 570.

[0107] Embedded information core 504 (e.g., interface component 504A and / or management component 504B as shown) and / or tablet 506 may include one or more transceivers 512, 572 and corresponding stacks, hardware, and software. For example, management component 504B and tablet 506 each include a Wi-Fi transceiver and a Bluetooth transceiver. Management component 504B and tablet 506 may also include cellular transceivers, ultra-wideband transceivers, RF transceivers (e.g., for communicating with RFID or NFC devices), etc. In practical applications, any one or more transceivers can be provided in any combination. However, for example, a Wi-Fi transceiver can wirelessly communicate with a remote server, for example, via Wi-Fi and the Internet, Wi-Fi to a cellular gateway, etc. For example, a Wi-Fi transceiver can communicate with a remote server 112 ( Figure 1 Communication. Transceiver 572 may also include a Bluetooth transceiver capable of pairing with nearby Bluetooth devices. Tablet 506 may also include a cellular transceiver. The cellular transceiver can communicate with one or more cellular networks (e.g., via communication with a 5G network, router, etc.), cellular-to-Wi-Fi gateways, etc. Bluetooth transceivers, Wi-Fi transceivers, cellular transceivers, combinations thereof (or any other suitable transceiver technology or combination thereof) can be used to interact with download tools, service tools, or other devices and / or systems to provide input to management component 504B and / or tablet 506.

[0108] In practical applications, the management component 504B and the tablet computer 506 do not need to include the same transceiver type. Moreover, in some embodiments, for example, the interface component 504A may include one or more transceivers in addition to or in place of the transceivers in the management component 504B.

[0109] Similarly, the interface component 504A of the embedded information core 504 may also include one or more transceivers and corresponding stacks, hardware and software, similar to those described above.

[0110] like Figure 5 As shown, management component 504B can communicate wirelessly with a remote server, for example, via Wi-Fi and the Internet, cellular to Wi-Fi gateway, etc. For example, the Wi-Fi transceiver can communicate with remote server 112 (… Figure 1 Communication. The transceiver can be used to interact with cloud / manufacturer databases, download tools, service tools, or other similar devices and / or systems as described more fully herein. Communication with manufacturer clouds, download tools, service tools, etc., can provide input to the embedded information core 504 (e.g., interface component 504A and / or management component 504B).

[0111] and Figure 4 Similar to other embodiments, the information controller 516 includes a core processor 518 independent of the tablet processor 558. Likewise, the information controller 516 includes memory independent of the tablet memory. However, the tablet processor 558 may share information stored in the tablet memory with the core processor 518, and the core processor 518 may share information stored in the embedded memory 540 with the tablet processor 558. Exchanges may occur via push, pull, query, or other interactions.

[0112] Distributed processor system

[0113] Overall reference Figures 1 to 5 The present disclosure provides a material handling vehicle communication system that includes a distributed multiprocessor vehicle control architecture.

[0114] According to various aspects of this disclosure, material handling vehicles (e.g., Figure 1 108) includes a material handling vehicle communication system. More specifically, the material handling vehicle communication system includes a vehicle network (e.g., 226) that facilitates the exchange of information with the vehicle's electronic components. Figure 2 ;426, Figure 4 526, Figure 5 The material handling vehicle communication system also includes an embedded information core and a tablet computer.

[0115] Embedded information core (e.g., embedded information core 204, Figure 2 Embedded Information Core 404 Figure 4 The embedded information core 504 is implemented as interface component 504A and management component 504B. Figure 5 It includes a core processor that can be communicatively coupled to the vehicle network.

[0116] Tablet PCs (e.g., Tablet 206, Figure 2 Tablet PC 406 Figure 4 Tablet PC 506 Figure 5 The tablet computer has a tablet processor. Furthermore, in some embodiments, the tablet computer is programmably configured to be communicatively coupled to and decoupled from the embedded information core. Additionally, in some embodiments, the tablet computer can be mounted on and removed from a material handling vehicle, independent of communicative coupling to the embedded information core. Moreover, in some embodiments, communicative coupling can be via a wired connection, a wireless connection, or both.

[0117] When a tablet computer is communicatively coupled to an embedded information core, the tablet processor works in cooperation with the core processor (e.g., the tablet processor can be used as an auxiliary processor for the core processor), thereby defining a distributed multiprocessor vehicle control architecture in which the core processor and the tablet processor cooperate to exchange at least one vehicle parameter between the tablet computer and an associated vehicle electronic component in the vehicle electronics.

[0118] In some embodiments, when the tablet is decoupled from the distributed multiprocessor vehicle control architecture, the core processor of the information controller acts as the main processor (e.g., at least for vehicle functionality), communicating with and controlling at least one vehicle electronic component via cross-vehicle networks. For example, as... Figure 2 , Figure 4 and Figure 5 As shown in the optimal configuration, the information controller is directly connected to the vehicle network and includes its own processor and memory. Therefore, the core processor is capable of autonomous operation and independent of the tablet computer. That is, in some embodiments, the tablet computer is not necessary for the normal operation of the material handling vehicle, as the core processor can handle all necessary vehicle functions.

[0119] Furthermore, the embedded controller can communicate with the tablet to exchange information. In this regard, the core processor can have a fixed set of tasks, regardless of whether the tablet is communicatively coupled to it. As another example, when the tablet is not communicatively coupled, the core processor can extend its processing responsibilities.

[0120] In some embodiments, when the tablet computer is communicatively coupled to the information controller, the tablet processor acts as the master processor, and the core processor acts as the slave processor, such that the slave processor receives commands from the master processor and transmits those commands directly to the vehicle network to control at least one vehicle electronic component. The slave processor can also transmit information to the master processor for processing, display, and manipulation of that information.

[0121] In some embodiments, when the tablet computer is communicatively coupled to the information controller, the tablet processor acts as a slave processor, and the core processor acts as a master processor, such that the slave processor receives commands from the master processor and transmits these commands directly or indirectly to the vehicle network to control at least one vehicle electronic component. The slave processor can also transmit information to the master processor for processing, display, and manipulation of said information.

[0122] In other embodiments, the distributed multiprocessor vehicle control architecture is configured such that a set of tasks is assigned to a core processor, and a set of tasks is assigned to a tablet processor. Therefore, the core processor continues to execute the assigned tasks regardless of whether the tablet is communicatively coupled. In some embodiments, tasks are dynamically adjusted based on the tablet's state. For example, when the tablet is mounted to a material handling vehicle and communicatively coupled to an embedded information core, the tablet can be used as a dashboard, for example, to display a widget indicating the vehicle's current operating status, such as travel speed, direction of travel, fork height, load weight, etc. When the tablet is detached (but still communicatively coupled), its tasks can automatically change to checklists, etc. The above examples are not exhaustive.

[0123] As an example, such as Figure 4 As shown, tablet 406 can receive configuration information from a remote server across network connections (such as Wi-Fi connections). More specifically, as... Figure 4 As best shown in the example embodiment, the tablet computer includes a remote server 112, such as a remote server 112 coupled to a material handling vehicle information data source 118, for example, for communication with a remote server. Figure 1 This is a transceiver for wireless communication. The tablet computer receives information from a remote server corresponding to instructions for modifying the operation of a material handling vehicle. The tablet computer processor, in response to receiving the information from the remote server, transmits the information to the core processor. For example, the tablet computer 406 then communicates with the multi-communication protocol module 452 of the embedded controller via the multi-communication protocol module 462. In this example, the tablet computer processor communicates with the core processor via at least one of Bluetooth and Universal Serial Bus. In this respect, the system of this invention can perform wireless updates, etc. Furthermore, updates can be implemented via local connections, such as USB, flash drive, PC, PC USB to CAN download, etc.

[0124] The embedded information core's processor accordingly includes program code read and processed by the core processor to transmit configuration data received from the tablet computer 406 to appropriate vehicle components, such as transmitting updated setpoints, configurations, settings, parameters, etc., across the vehicle network 426. For example, as noted more fully herein, the embedded information core includes a data synchronization manager that manages synchronization data collected from the material handling vehicle and information exchange with the tablet computer. The core processor can use the data synchronization manager to facilitate modifications to the operation of the material handling vehicle. For example, the core processor can implement modifications to the operation of the material handling vehicle by communicating across the vehicle network.

[0125] In some embodiments, the tablet computer can transmit configuration information and other commands (e.g., modifying setpoints, requesting recorded data, configuring vehicle performance, updating software, etc.) to the core processor via a multi-communication protocol module, enabling the core processor to ultimately execute the commands from the tablet computer. Furthermore, the tablet computer can display widgets and other material handling vehicle information, where the core processor extracts necessary information from vehicle components across the vehicle network. The core processor processes the collected information and transmits it to the tablet computer for display, for example, by using widgets in a graphical user interface.

[0126] In alternative examples, for instance, refer to Figure 5 The embedded information core may include a transceiver for wireless communication with a remote server (e.g., see management component 504B, which can communicate with a server via wireless technologies such as Wi-Fi). Figure 1 (Communication with remote servers such as server 112). The embedded information core receives information corresponding to instructions for modifying the operation of the material handling vehicle from the remote server, and the core processor implements the modification by communicating across the vehicle network to modify the operation of the material handling vehicle.

[0127] Here, the core processor sends messages to the tablet PC processor to modify the tablet PC display based on modifications to the material handling vehicle (e.g., modifying the content displayed on the tablet PC display, such as icons, widgets, values, symbols, or any other displayable information displayed on the tablet PC). For example, updated data can be stored by the data synchronization manager 550. The communication protocol module 552 handles communication with the tablet PC's communication protocol module 562. The tablet PC processor can then retrieve the information and use it to update relevant widgets, such as the speed widget, lift widget, task widget, timer widget, etc. For example, if the modification is setting a maximum speed, a message specifying this can be provided and / or the speed widget can be modified to reflect the maximum speed, etc.

[0128] Referring generally to the accompanying drawings, in some embodiments, the tablet computer can act as a controller, middleware, display, or a combination thereof for interacting with an embedded information core, or for use with one or more other devices, control modules, peripherals, etc., associated with the material handling vehicle. For example, the tablet computer can be paired, connected, or otherwise communicate directly with a battery monitor, impact sensor, or other devices on the material handling vehicle that can communicate with the tablet computer.

[0129] In some embodiments, the tablet runs a "control app" that controls what apps can be installed on the tablet. This allows manufacturers to review and approve apps loaded on the tablet while fully leveraging the tablet's flexibility and capabilities. For example, third-party apps approved by the source (e.g., the manufacturer) can still be loaded and run on the tablet.

[0130] Distributed location information

[0131] Tablet computers may include a Global Positioning System (GPS). However, material handling vehicles may use different location tracking systems to address indoor operations. In some embodiments, however, GPS from the tablet computer may be used, modified, enhanced, coordinated, or otherwise integrated with the material handling vehicle's location tracking system. This allows different types of location / spot information to be fully utilized for different applications.

[0132] Example Information Exchange

[0133] refer to Figure 6 A process 600 for modifying the operation of a material handling vehicle is provided. Process 600 includes receiving, at 602, an electrical signal representing an instruction to modify the operating conditions of the material handling vehicle. Here, the instruction may be received, for example, from a tablet computer removably mounted to the material handling vehicle. Furthermore, the instruction is in the format of an open standard communication protocol. Process 600 also includes, at 604, converting the instruction received in the open standard communication protocol into a modification command for modifying associated electrical components of the material handling vehicle based on parameters extracted from the instruction. Process 600 further includes, at 606, transmitting the modification command to the electrical components of the material handling vehicle via the vehicle network. The electrical components receive the modification command and change their operating state, thereby causing a comprehensive modification to the operation of the material handling vehicle.

[0134] As noted more fully herein, in some embodiments, the tablet computer is configured to be communicatively coupled to and communicatively decoupled from the material handling vehicle. Furthermore, in some embodiments, the tablet computer can be mounted to the material handling vehicle independently of its communicative coupling with the vehicle.

[0135] In some embodiments, receiving an electrical signal at 602 representing an instruction to modify the operating conditions of the material handling vehicle includes receiving the electrical signal by a processor integrated into the material handling vehicle, the processor being communicatively coupled to a material handling vehicle network for communicating with electronic modules on the material handling vehicle.

[0136] Furthermore, in some embodiments, receiving an electrical signal at 602 indicating an instruction to modify the operating conditions of the material handling vehicle includes receiving an electrical signal from a tablet computer removably mounted to the material handling vehicle while the tablet computer is detached from the material handling vehicle and connected to the material handling vehicle via a wireless connection.

[0137] Furthermore, in some embodiments, receiving an electrical signal at 602 indicating an instruction to modify the operating conditions of the material handling vehicle may also include receiving an instruction generated by an application executed on the tablet computer in response to user interaction with a graphical user interface on the tablet computer's touchscreen.

[0138] In some embodiments, converting instructions received in the Open Standard Communication Protocol (OSP) at 604 into modification commands for modifying associated electrical components of a material handling vehicle based on parameters extracted from the instructions may include formatting the instructions in the OSP as packets with a header and a payload, wherein the payload contains the modification commands and the packets are encrypted.

[0139] In addition, in some embodiments, process 600 may also include determining whether the tablet computer is communicatively coupled to the material handling vehicle, determining whether the tablet computer can handle processing tasks associated with the material handling vehicle, sending data associated with the processing tasks from the material handling vehicle to the tablet computer, receiving modified parameters from the tablet computer based on an application executed on the tablet computer, and modifying the material handling vehicle according to the modified parameters received from the tablet computer.

[0140] Furthermore, in some embodiments, process 600 may further include determining whether a portable tablet computer is communicatively coupled to a material handling vehicle via a wired open standard communication protocol, a wireless open standard communication protocol, or both wired and wireless open standard communication protocols, with the wired open standard communication protocol taking precedence over the wireless open standard communication protocol. Both the wired and wireless open standard communication protocols are used, and the wired open standard communication protocol is detected as active. In some embodiments, determining whether a portable tablet computer is communicatively coupled to a material handling vehicle via a wired open standard communication protocol may include detecting the presence of a hardwired Universal Serial Bus (USB) connection and detecting that the USB connection is active by detecting an acknowledgment signal from the portable tablet computer via the USB connection. Moreover, process 600 may also include prioritizing the wireless open standard communication protocol over the wired open standard communication protocol, with the wired open standard communication protocol detected as inactive.

[0141] In some embodiments, process 600 may further include initiating a communication sequence between the mobile tablet and the material handling vehicle by using a wired open standard communication protocol, detecting that the wired open standard communication protocol has become inactive, and switching to a wireless open standard communication protocol without interrupting the communication sequence.

[0142] In some other embodiments, process 600 may also include initiating a communication sequence using a wireless open standard communication protocol to complete a communication sequence between the mobile tablet and the material handling vehicle, detecting that the wireless open standard communication protocol has become inactive, and switching to a wired open standard communication protocol without interrupting the communication sequence.

[0143] refer to Figures 1-6 In the example embodiment, the electrical signal representing the instruction to modify the operating conditions of the material handling vehicle is transmitted by a processor integrated into the material handling vehicle (e.g., the processor in the information controller 218 of the information core 204). Figure 2 The core processor in the information controller 416 Figure 4 The core processor in the information controller 516, for example, via an interface component 504A and / or a management component 504B embedded information core, Figure 5 (etc.) receive. Regardless of configuration, the processor can be communicatively coupled to the material handling vehicle network for communication with electronic modules on the material handling vehicles (see, for example...). Figure 2 Vehicle network 226 Figure 4 Vehicle network 426 Figure 5 (e.g., vehicle network 526, etc.). Therefore, network connectivity facilitates the ability to transmit modification commands.

[0144] As noted more fully herein, some embodiments distinguish when the tablet PC is communicatively coupled to the embedded controller (e.g., connected / paired). For example, this allows the tablet PC processor to act as a supervisor during connection / pairing, while the core processor acts as a subordinate. Alternatively, the tablet PC processor can act as an auxiliary to the core processor's core role. This also allows the tablet PC to be communicatively decoupled from the embedded information controller (e.g., unpaired), enabling the tablet PC to perform other functions without affecting the operation of the material handling vehicle. Regardless of the electrical connection status, the tablet PC can be physically docked to and / or detached from the material handling vehicle.

[0145] This article discusses the pairing / interface between the tablet's processor and the core processor in more detail. However, by presenting the aspects outlined here, this article enables the tablet to operate in modes including the following:

[0146] Pairing and docking

[0147] In the paired and docked configuration, the tablet is physically mounted on the material handling vehicle, electrically connected to the material handling vehicle, and paired with the core processor.

[0148] Unpaired and docked

[0149] In an unpaired and docked configuration, the tablet is physically mounted on the material handling vehicle and can be electrically connected to receive power / charge, for example. However, the tablet does not communicate with the embedded core processor.

[0150] Therefore, the tablet can be electrically disconnected from the material handling vehicle and is not paired with the core processor.

[0151] Paired but not docked

[0152] In a paired but not docked configuration, the tablet is communicatively coupled to the core processor of the material handling vehicle and can communicate with the core processor via a wired or wireless connection. However, the tablet is not physically mounted on the material handling vehicle.

[0153] Unpaired and not docked

[0154] In an unpaired and unconnected configuration, the tablet is not communicatively coupled to the core processor of the material handling vehicle and therefore cannot communicate with the core processor via wired or wireless connections. Furthermore, the tablet is not physically mounted on the material handling vehicle. However, the tablet can still be used, for example, by the operator to display information from the warehouse management system, to function in an operable manner to facilitate communication (e.g., via messaging), to capture photos or videos of operating environment conditions, and so on.

[0155] As some example embodiments, the tablet computer may include software specifically designed for material handling vehicles, such as software specific to the type, model, category, etc., of the material handling vehicle. In this regard, the tablet computer may implement a graphical user interface (GUI) that displays one or more widgets, gauges, meters, operator scores, warnings, instructions, messages, dashboard information, etc., on the tablet's touchscreen based on interaction with the material handling vehicle, a remote server, or a combination thereof. For example, suppose the material handling vehicle has load-carrying features, such as forks that can be raised and lowered. Here, the tablet computer's GUI may display widgets or programs, such as a rack height selection widget. The vehicle operator can interact with the rack height selection widget, for example, by touching the touchscreen to select the height to raise the forks. In this example, in response to the vehicle operator's interaction with the GUI on the touchscreen of the portable tablet computer, the core processor on the material handling vehicle receives instructions generated by an application (e.g., the rack height selection widget) executing on the tablet computer.

[0156] It is worth noting that in this example, the application can be programmed to selectively enable or disable operator interaction. For example, in some applications, rack height selection controls can be enabled even if the mobile tablet is not docked. For instance, a vehicle operator can unload a material handling vehicle to check advantageous locations, shelf positions, etc. Therefore, in this example, it is irrelevant whether the mobile tablet is docked or not, as long as it is paired (communically coupled). In other examples, it may be desirable to require the tablet to be both docked (e.g., and therefore in the operator's cab of the material handling vehicle) and paired with the core processor.

[0157] Therefore, the portable tablet virtualizes rack height selection functionality, freeing vehicle operators from being confined to a single physical location, as is required when using hardwired / integrated interfaces. That is, the tablet includes software applications, implemented, for example, as widgets, that mimic the hardware controls physically present on the material handling vehicle. Thus, in response to the tablet performing controls that virtualize the features of the material handling vehicle, the software application receives electrical signals from the tablet and modifies commands to translate the virtualized controls into corresponding physical controls for the material handling vehicle. Other examples may include using a portable tablet to virtualize widgets for hybrid control, speed control, load weight control, timers or other workflow / job functions, widgets for controlling horns or lights on the material handling vehicle, and so on.

[0158] Therefore, receiving an electrical signal indicating an instruction to modify the operating conditions of a material handling vehicle may include receiving an instruction generated by an application executed on a tablet computer in response to user interaction with a graphical user interface on a tablet computer's touchscreen.

[0159] In practical applications, instructions sent to the core processor can be generated by applications running on the tablet, for example, through calculation, user input, or in response to wireless communication between the tablet and remote devices (e.g., another nearby material handling vehicle, a remote server, a remote electronic badge or tag, a smartphone, other tablets, laptops, etc.).

[0160] As another example, an operator may be required to complete a pre-use checklist. Typically, this requires the operator to be positioned at the monitor. However, in this disclosure, because the communication connection is independent of the physical connection, the operator can remove the tablet from the material handling vehicle and walk around the vehicle holding the tablet, thereby completing the checklist at the checkpoint.

[0161] Furthermore, because tablet computers can virtualize outputs (e.g., widgets, gauges, camera feeds, dashboard icons, checklist displays, etc.) and optionally virtualize vehicle controls (e.g., one or more inputs such as steering wheel, accelerator, brake, hybrid, hydraulic, forklift, load handling, and combinations thereof), checklists, maintenance checklists, and picking operations, and can perform other features outside the normal operator's cab location, virtualization can mimic or alter the vehicle's physical counterpart. For example, some virtualizations can provide reduced functionality, performance tuning or detuning capabilities, or other modifications desired by the vehicle manufacturer.

[0162] Open Standard Communication

[0163] As described above, in this example embodiment, the instructions are formatted as an open standard communication protocol. As some illustrative examples, open standards may include Bluetooth, USB, Ethernet, ultra-wideband, cellular, other open standards, or combinations thereof. Typically, open standards will have published or open specifications, various rights granted to users, or a combination thereof. For example, refer to... Figure 4 and Figure 5 The tablet computer is coupled to the embedded information core via USB, Bluetooth, or both (or other connection methods). Here, the tablet computer processor formats instructions in open standard communication protocols into packets with headers and payloads, where the payloads contain modification commands.

[0164] In some embodiments, instructions can be received by coordinating messages using at least two independent and different open standard communication protocols (e.g., Bluetooth and USB). By coordinating wired and wireless connections, the embedded controller has an increased guarantee of receiving correct messages.

[0165] Alternatively, protocols can be prioritized. For example, the process could be responsible for prioritizing wireless open standard communication protocols over wired open standard communication protocols, where the wired open standard communication protocols are detected as inactive, and / or prioritizing wired open standard communication protocols over wireless open standards, where the wireless open standard communication protocols are detected as inactive.

[0166] Figure 7 The illustration depicts a process 700 for modifying the operation of a material handling vehicle, wherein instructions are transmitted across open standard communication protocols. At 702, the process for modifying the operation of the material handling vehicle may include receiving instructions from a processor on the material handling vehicle, from a tablet computer communicatively coupled to the material handling vehicle, to modify the operating conditions of the electrical components of the material handling vehicle. In this example, the instructions are transmitted across open standard communication protocols. The process also includes, at 704, determining whether a portable tablet computer is communicatively coupled to the material handling vehicle via a wired open standard communication protocol, a wireless open standard communication protocol, or both wired and wireless open standard communication protocols.

[0167] At 706, the process further includes prioritizing the wired open standard communication protocol over the wireless open standard communication protocol, wherein the wired open standard communication protocol is detected as active. At 708, the process includes having a processor on the material handling vehicle translate instructions into modification commands that modify associated electrical components of the material handling vehicle based on parameters extracted from the instructions. At 710, the process includes transmitting the modification commands to the electrical components of the material handling vehicle via the vehicle network, wherein the electrical components receive the modification commands and change their operating states to comprehensively modify the operation of the material handling vehicle.

[0168] This process can determine whether a portable tablet is communicatively coupled to a material handling vehicle via a wired open standard communication protocol by detecting the presence of a wired connection (e.g., a wired USB connection). The USB connection is active by detecting an acknowledgment signal from the tablet. Similarly, this process can determine whether a portable tablet is communicatively coupled to a material handling vehicle via a wireless open standard communication protocol by detecting the presence of a Bluetooth connection (e.g., via detection of a pairing request, identification of a broadcast name, etc.).

[0169] The exchange can flow bidirectionally. As noted in more detail herein, the core processor can communicatively couple to truck data (e.g., truck configuration data 444, 544) stored in memory on the material handling vehicle. Here, the core processor can retrieve the truck data from the memory on the material handling vehicle, format the retrieved truck data into vehicle information in an open standard communication protocol, and transmit the information to a tablet computer, for example, by displaying it graphically on a widget output to the tablet computer's touchscreen display. The core processor can communicate with the tablet computer using communication protocols across one or more protocols, including open standard protocols (such as USB, Bluetooth, etc.).

[0170] This two-way communication allows the tablet to send information, such as commands to the material handling vehicle. It also allows the material handling vehicle to send information to the tablet. Here, the tablet can process and display the information, send the processed information back to the material handling vehicle, or use a tablet transceiver to send material handling vehicle information to a remote destination, such as a remote server 112. For example, the material handling vehicle's core processor can send information to the tablet, such as storing the current state of the vehicle's operating parameters, enabling the tablet to transmit at least one vehicle operating parameter to a remote device, regardless of whether the material handling vehicle is powered on or off.

[0171] As another example, the core processor can execute software code to read the current state of vehicle operating parameters and store it in embedded memory. In this case, the tablet is configured not to store vehicle operating parameters unless specifically instructed to do so by the material handling vehicle processor.

[0172] Therefore, for example, the core processor can determine whether a mobile tablet is communicatively coupled to a material handling vehicle, and optionally, whether the mobile tablet can handle processing tasks associated with the material handling vehicle. The core processor then sends data associated with the processing task from the material handling vehicle to the tablet, receives modified parameters from the tablet based on the application executed on the tablet, and modifies the material handling vehicle according to the modified parameters received from the tablet.

[0173] In other embodiments, the information exchange between the material handling vehicle and the tablet can switch between open protocols. For example, the communication sequence between the tablet and the material handling vehicle can be initiated using a wireless open standard communication protocol (e.g., Bluetooth). If the component detects that the wireless open standard communication protocol has become inactive, the communication sequence will switch to a wired open standard communication protocol (e.g., USB) without interrupting the communication sequence. Similarly, the communication sequence can be initiated using a wired open standard communication protocol (e.g., USB). If the USB connection becomes inactive, the communication sequence can switch to a wireless open standard communication protocol (e.g., Bluetooth) without interrupting the communication sequence.

[0174] Android

[0175] In an example embodiment, the tablet runs the Android operating system. The Android operating system can execute widgets and other applications specific to material handling vehicles. The material handling vehicle can also utilize the tablet's camera, video, ports, and other built-in capabilities to provide technical capabilities for the material handling vehicle. In some embodiments, the Android operating system is locked to prevent third-party applications from being loaded onto the tablet. In other embodiments, the tablet allows third-party applications (e.g., garage door opener applications, calculator applications, warehouse management interface applications, remote light switch control applications, etc.).

[0176] In some embodiments, the tablet processor acquires information about the current status of the material handling vehicle, such as time, location, operator identification, etc. The acquired information can be derived from the tablet itself by interacting with a remote server or by communicating with the core processor of the information controller. This allows the dashboard widget to be either fixed or dynamic, for example, based on the acquired status information. As an example, the widget can be modular and adaptively change dynamically based on vehicle location data, truck telematics data, operator location data, etc.

[0177] Furthermore, a proprietary app repository can be used to deliver new and updated apps to tablets. This allows for facial or other biometric integration, new apps, and other capabilities. Additionally, the Android operating system supports regular web browsers. Therefore, vehicle operators can selectively access the internet for purposes such as streaming music, uploading photos of work tasks, checking the weather, logging into fleet management software, and more.

[0178] Security

[0179] According to other aspects of this disclosure and with reference to Figure 8A process 800 is provided for protecting access to material handling vehicles. This process includes coupling a tablet computer to the material handling vehicle at point 802 via a wired open standard communication protocol.

[0180] The process also includes receiving the first device identifier of the tablet computer coupled via a wired open standard communication protocol at 804.

[0181] The process also includes storing the first device identifier in memory at 806.

[0182] The process also includes receiving the 808 second device identifier via the wireless open standard communication protocol.

[0183] Furthermore, the process may optionally include determining at 810 whether another device has been coupled to the material handling vehicle via a wireless open standard communication protocol.

[0184] The process further includes, at 812, communicatively coupling the tablet computer to the material handling vehicle via a wireless open standard communication protocol if another device has not yet been coupled to the material handling vehicle via a second communication protocol and the second device identifier matches the first device identifier.

[0185] In some embodiments, the process may further include providing a processor coupled to a memory on the material handling vehicle, the processor implementing software code to read the current state of vehicle operating parameters and store the current state of vehicle operating parameters in the memory, and configuring the tablet to not store vehicle operating parameters unless specifically instructed to do so by the material handling vehicle processor.

[0186] Furthermore, in some embodiments, the process also includes instructing a tablet computer to store the current state of vehicle operating parameters by the processor of the material handling vehicle, such that the tablet computer can transmit at least one vehicle operating parameter to a remote device, regardless of whether the material handling vehicle is powered on or off.

[0187] For example, wired communication protocols (such as USB) can be used to pass discovery parameters from a tablet to an embedded controller (or from an embedded controller to a tablet). These discovery parameters can then be used to authenticate wireless connections. For instance, a tablet can broadcast a discovery name as a secondary device identifier. Here, even if many tablets are broadcasting within range of the embedded controller, the embedded controller will always select the correct wireless connection to the tablet because the correct discovery name has already been sent to the embedded controller via USB.

[0188] The tablet can also authenticate with a remote server using authentication protocols, for example, by using a random password each time a socket is opened between the tablet and the remote server.

[0189] Packets can also be wrapped in encryption, such as a Transport Layer Security (TLS) cryptographic protocol, to provide additional security between the tablet and the embedded information core. As another example, the packet format can depend on the cipher. Here, the cipher can be fixed or change continuously based on predetermined intervals. For example, the tablet can communicate using a protocol that changes at each predetermined time interval, where packets transmitted using that protocol are encrypted. In another example embodiment, the packet format depends on a cipher that changes continuously based on predetermined intervals.

[0190] As another example, the security process may include establishing a connection between a tablet and an embedded controller in a material handling vehicle, and identifying challenge and answer tuples from a set of challenge and answer tuples. The identified challenge is presented to the tablet, which provides the answer. The embedded controller receives the answer via the tablet and determines whether the received answer corresponds to the answer associated with the challenge and answer tuple. Therefore, if the received answer corresponds to the answer associated with the challenge and answer tuple, the embedded information core can maintain the secure connection; otherwise, if the received answer does not correspond to the answer associated with the challenge and answer tuple, the secure connection can be terminated.

[0191] To add an extra layer of security, the system can utilize a control app to run the tablet in kiosk mode. This control app acts as a supervisory app to use at least one physical button on the tablet (e.g., a home button). If the boot kernel is not authorized and signed, this allows the tablet to refuse the loading of the tablet's boot kernel. In this regard, a first authorized signature can be requested to load the application onto the tablet, and a second authorized signature can be requested to modify the tablet's operating system.

[0192] In this context, an "authorized" signature is a signature that satisfies one or more authentication credentials, which may be specified by a trusted source (e.g., a manufacturer, a trusted third party, or other authorized source of the digital information). In some embodiments, the algorithm verifies the authenticity, integrity, origin, source, content, and combinations thereof of digital information (e.g., signatures, certificates, signed code) to ensure that only valid and authorized code (the boot kernel in the example above) is loaded and / or executed. Correspondingly, an "unauthorized" signature may include a non-existent signature, a signature presented but determined to be invalid, a signature presented but determined to be expired, a signature that otherwise cannot specify or otherwise provide the correct one or more authentication credentials, a signature that fails an integrity check, etc.

[0193] The tablet computer can be configured to operate exclusively with a material handling vehicle for the purpose of performing the vehicle's functional requirements. Alternatively, the tablet computer may be allowed access to the operating system, for example, to perform non-vehicle functions such as playing games, accessing the internet, playing music, etc. Access can be restricted based on time, date, shift, location, or other environmental parameters. As an example, based on at least one environmental parameter (such as time of day), the tablet computer can be controlled to restrict access to its wireless radio devices. This allows the tablet computer to wirelessly communicate with only one remote internet site (or a set of pre-approved sites) during a predefined time-limited window.

[0194] Miscellaneous

[0195] Referring generally to the accompanying drawings, references to a wireless connection can be made to any wireless connection. Therefore, although Bluetooth is used as a reference for illustration, the connection can be replaced by ultra-wideband, Wi-Fi, cellular, Zigbee, etc. Similarly, references to a wired connection can be made to any wired connection, such as USB, Firewire, Thunderbolt, Universal Asynchronous Receiver / Transmitter (UART), Serial Peripheral Interface (SPI), Internal Integrated Circuit (I2C), Controller Area Network (CAN), etc.

[0196] Conventional user interfaces on material handling vehicles include screens, such as LCD (liquid crystal display) screens with embedded operating systems (OS) (such as custom OS, Linux, Windows, Android, etc.). However, aspects of this disclosure decouple industrial hardware from technical hardware. Leveraging portable devices to handle design components (wireless radios, displays / touchscreens, processing power) that change frequently with technology cycles allows for a flexible and robust architecture that can be updated faster and less effort compared to a fully embedded approach.

[0197] Overview of Computer Systems

[0198] refer to Figure 9A schematic block diagram illustrates an exemplary computer system 900 for implementing the various processes described herein. The exemplary computer system 900 includes one or more (hardware) microprocessors (μPs) 910 and corresponding (hardware) memories 920 (e.g., random access memory and / or read-only memory) connected to a system bus 930. Information can be transferred between the system bus 930 and a local bus 950 for communicating with various input / output devices via a suitable bridge 940. For example, the local bus 950 is used to interface peripheral devices to one or more microprocessors (μPs) 910, such as storage devices 960 (e.g., hard disk drives); removable media storage devices 970 (e.g., flash drives, DVD-ROM drives, CD-ROM drives, floppy disk drives, etc.); I / O devices 980 (e.g., input devices (e.g., mice, keyboards, scanners, etc.), output devices (e.g., monitors, printers, etc.)); and network adapters 990. The list of peripheral devices above is presented by way of illustration and is not intended to be limiting. Other peripheral devices may be appropriately integrated into the computer system 900.

[0199] One or more microprocessors 910 control the operation of the exemplary computer system 900. Moreover, one or more of the microprocessors 910 execute computer-readable code (e.g., stored in memory 920, storage device 960, a removable medium that can be inserted into removable medium storage device 970, or a combination thereof (collectively or individually referred to as a computer program product)) that instructs the microprocessors 910 to implement the computer implementation of the process described herein.

[0200] The computer implementation process described in this paper can be implemented in a computer system (e.g., Figure 1 On one or more of the processing devices 102, in a reference Figures 1 to 5 The machine-executable process described is executed on a specific computing device, such as a vehicle computer, or a combination thereof.

[0201] Therefore, an exemplary computer system or its components 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 900. In the latter scenario, a remote computer may be connected to computer system 900 via any type of network connection (e.g., using network adapter 990 of computer system 900).

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

[0203] The description of this embodiment is presented for illustrative and descriptive purposes and is not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the disclosed embodiments.

[0204] Having described the embodiments of this application in such detail, it will be apparent that modifications and variations are possible without departing from the scope of the appended claims.

Claims

1. A communication system for material handling vehicles, comprising: Vehicle networks facilitate information exchange with the electronic components of material handling vehicles; An embedded information core with a core processor that can be communicatively coupled to the vehicle network to communicate with vehicle electronic components; as well as A tablet computer installed on a material handling vehicle, the tablet computer having a tablet computer processor, wherein: The tablet is configured to communicate with the embedded information core without using the vehicle network; and The tablet computer is unaware of vehicle electronic components that communicate across vehicle networks and embedded information cores. in: When a tablet computer is communicatively coupled to an embedded information core, the tablet processor and the core processor work together to define a distributed multiprocessor vehicle control architecture, in which the core processor receives instructions from the tablet processor to modify the operation of the material handling vehicle. The core processor translates the instruction into a modification command based on the parameters extracted from the instruction; and The core processor sends modification commands across the vehicle network to associated vehicle electronic components to modify their operation.

2. The material handling vehicle communication system as described in claim 1, wherein: The tablet computer is configured to be communicatively coupled to and communicatively decoupled from the embedded information core; The tablet can be mounted onto a material handling vehicle and can be detached from the material handling vehicle independently of its communicative coupling with the embedded information core; and The tablet computer is configured to be communicatively coupled to the embedded information core regardless of whether the tablet computer is installed.

3. The material handling vehicle communication system as described in claim 1, wherein: The tablet computer includes a first multi-communication protocol module, which is configured to interact with a second multi-communication protocol module of an embedded information core to enable the tablet computer processor to communicate with the core processor via at least one wireless connection and at least one wired connection. Also includes: Set the wired or wireless connection to have a higher priority than the other.

4. The material handling vehicle communication system as described in claim 1, wherein: The embedded information core includes a transceiver for wireless communication with a remote server; The embedded information core receives and modifies the information corresponding to the operation instructions of the material handling vehicle from the remote server; The core processor modifies the operation of material handling vehicles through cross-vehicle network communication; as well as The core processor sends a message to the tablet computer processor to modify the content displayed on the tablet computer's display based on the modifications made to the material handling vehicle.

5. The material handling vehicle communication system as described in claim 1, wherein, The tablet computer operates independently of the vehicle's functional applications, eliminating the need for a connection between the tablet computer and the embedded information core.

6. The material handling vehicle communication system as described in claim 1, wherein, The tablet maintains communicative coupling to the embedded information core, regardless of whether the tablet is installed on or removed from the material handling vehicle.

7. The material handling vehicle communication system as described in claim 1, wherein: The core processor receives instructions from the tablet processor to modify the operation of the material handling vehicle by receiving electrical signals representing instructions to modify the operating conditions of the material handling vehicle, wherein the instructions are formatted according to an open standard communication protocol; and The core processor translates instructions received using open standard communication protocols into modification commands that modify the associated vehicle electronics of the material handling vehicle based on parameters extracted from the instructions.

8. The material handling vehicle communication system as described in claim 7, wherein, Instructions received using open standard communication protocols consist of packets with headers and payloads, where the payloads contain modification commands, and the packets are encapsulated in encryption.

9. The material handling vehicle communication system as described in claim 1, wherein: When the tablet computer is communicatively coupled to the core processor, the tablet processor acts as a supervisor; and When the tablet is communicatively coupled to the core processor, the core processor acts as a subordinate.

10. The material handling vehicle communication system as described in claim 1, wherein, Tablet computers play a supporting role to the core processor.

11. The material handling vehicle communication system as described in claim 1, wherein, Core processor: Determine whether the tablet computer is communicatively coupled to the material handling vehicle via a wired open standard communication protocol, a wireless open standard communication protocol, or both wired open standard communication protocols and wireless open standard communication protocols; and When a wired open standard communication protocol is detected to be active, the wired open standard communication protocol is prioritized over the wireless open standard communication protocol.

12. The material handling vehicle communication system as described in claim 11, wherein, Core processor: The wired open standard communication protocol has been detected to be inactive; and Switch to the wireless open standard communication protocol without interrupting the communication sequence.

13. The material handling vehicle communication system as described in claim 1, wherein: The tablet is configured to communicate with the embedded information core without using the vehicle network in the following ways: A universal serial bus interface is used for communication between the tablet and the embedded information core.

14. The material handling vehicle communication system as described in claim 1, wherein: The tablet computer receives instructions from a remote server across a wireless network to modify the operation of the material handling vehicle; In response to receiving instructions from a remote server, the tablet processor transmits the instructions to the core processor. and The core processor uses a data synchronization manager to convert received instructions into configuration information, which includes a selected one of updated setpoints, configurations, settings, or parameters, and the core processor transmits the configuration information across the vehicle network to the appropriate vehicle components.

15. The material handling vehicle communication system as described in claim 1, wherein: The embedded information core receives instructions from devices other than tablets to modify the operation of material handling vehicles; The core processor transmits configuration information to the appropriate vehicle components across the vehicle network based on the received instructions; The data synchronization manager converts at least one of the commands and received configuration information into output; and The tablet processor uses its output to update the tablet display.

16. The material handling vehicle communication system as described in claim 1, wherein: The embedded information core includes a data synchronization manager that collaborates with a corresponding data synchronization manager on the tablet computer to exchange vehicle information.

17. The material handling vehicle communication system as described in claim 1, wherein: The tablet runs the Android operating system.

18. The material handling vehicle communication system as described in claim 1, wherein: The tablet PC is communicatively coupled to the embedded information core via at least one direct physical communication port; and The tablet computer is unaware of the network system protocols required for cross-vehicle network communication or otherwise access to the vehicle network.

19. The material handling vehicle communication system as described in claim 1, wherein: The core processor is configured as follows: Receive the first device identifier of the tablet computer coupled via a wired open standard communication protocol; Receive the second device identifier via open wireless standard communication protocols; Determine whether another device has been coupled to the material handling vehicle via a wireless open standard communication protocol; and If another device has not yet been coupled to the material handling vehicle via the wireless open standard communication protocol, and the second device identifier matches the first device identifier, then the tablet computer is communicatively coupled to the material handling vehicle via the wireless open standard communication protocol.

20. The material handling vehicle communication system as described in claim 1, wherein: The embedded information core and the tablet communicate via direct communication over a Universal Serial Bus (USB) connection and a Bluetooth connection, with the USB connection used to transfer discovery parameters between the tablet and the embedded information core.

Images