Systems, methods, and apparatus for providing local electronic repair

Abstract

Systems, methods, and apparatus for providing local electronic maintenance of a machine may include: providing access to the network manager to the mobile device via a network pairing and connection process between the machine's network manager and the mobile device; enabling local electronic access functionality, such as privileged functionality, on the mobile device from a background system when the network manager and the mobile device are successfully paired and connected; and using the mobile device to electronically access the machine's data when the mobile device and the network manager are paired and connected.

Description

Technical Field

[0001] This disclosure relates to providing local repair, and more specifically, to providing local repair functionality to mobile devices for local repair of the machine. Background Technology

[0002] Typically, without a wired connection, a technician and electronic repair tools located next to the machine may not be recognized as close enough to perform local repair tasks (e.g., troubleshooting, diagnostics, etc.) on-site. Therefore, without a wired connection, a technician's electronic repair tools may not be able to utilize some or all of their local repair capabilities. Furthermore, even with a wired connection, a technician may need to follow numerous steps to reach the point where they can begin repairing the machine using electronic repair tools.

[0003] U.S. Patent No. 8,996,232 (“232 Patent”) describes wireless vehicle repair, which allows for the exchange of diagnostic information between a client terminal and the vehicle's vehicle computing system (VCS) to diagnose one or more vehicle problems. According to the 232 Patent, repair software can be stored on the client terminal, and the client terminal's repair software can transmit repair operation information as repair data packets to the VCS via a wireless cloud. Summary of the Invention

[0004] In one aspect, this disclosure implements a method comprising: providing access to the network manager to the mobile troubleshooting device via a pairing process between the network manager of the machine and the mobile troubleshooting device through a personal area network; enabling a local troubleshooting function on the mobile troubleshooting device from a background system when the network manager and the mobile troubleshooting device are successfully paired and connected through the personal area network; and performing a local troubleshooting operation in response to operator input at the mobile troubleshooting device when the mobile troubleshooting device and the network manager are paired and connected.

[0005] In another aspect, this disclosure implements or provides a non-transitory computer-readable storage medium storing computer-readable instructions that, when executed by one or more computers, cause the one or more computers to perform a method. The method may include: providing access to a network manager for a mobile device having at least one of the one or more computers, via a pairing and connection process between the mobile device and the network manager on or within the machine through a short-wavelength, UHF radio wave wireless network; and providing local troubleshooting functionality at the mobile device to perform local troubleshooting operations when the mobile device accesses the network manager. The local troubleshooting functionality of the mobile device may be limited according to the permissions granted to (authorized to access the network manager) a subscriber.

[0006] In another aspect, a system for troubleshooting a work machine locally can be provided or implemented. The system may include: a first communication entity for the work machine, the first communication entity including a network manager; a background system remote from the work machine; a mobile device hosting a thin client application for troubleshooting the work machine locally upon gaining access to the network manager; a first communication network accessible by the background system and the first communication entity for communication between the first communication entity and the background system; a second communication network accessible by the mobile device and the network manager for the mobile device to gain access to the network manager; and a third communication network accessible by the mobile device and the background system for communication between the mobile device and the background system. The second communication network may be a personal area network (PAN), and the thin client application gains access to the network manager only when the mobile device is local to the network manager and within the transmission distance of the PAN. When the thin client application accesses the network manager via the second communication network, the mobile device and the network manager can transmit troubleshooting data to each other through the background system via the first communication network and the third communication network.

[0007] Other features and aspects of this disclosure will become apparent from the following description and accompanying drawings. Attached Figure Description

[0008] Figure 1 An exemplary system based on one or more embodiments of the disclosed subject matter is shown.

[0009] Figure 2 It is a block diagram of a system according to one or more embodiments of the disclosed subject matter.

[0010] Figure 3 It is a flowchart of a method according to one or more embodiments of the disclosed subject matter.

[0011] Figure 4 It is a maintenance sequence diagram based on one or more embodiments of the disclosed subject matter. Detailed Implementation

[0012] This disclosure relates to providing local repair, and more specifically, to providing local repair capabilities to mobile devices for local repair of the device (e.g., diagnostics, updates, troubleshooting).

[0013] Figure 1 and Figure 2 An exemplary system 100 according to one or more embodiments of the disclosed subject matter is illustrated. System 100 may include one or more components that perform various tasks that facilitate machine environment tasks (e.g., mining, construction, transportation, agriculture, manufacturing, oil and gas) or any other type of task associated with other types of industries. For example, system 100 may include machine 110 (or multiple machines of the same or different types).

[0014] The machine according to embodiments of the disclosed subject matter can be a stationary or mobile machine configured to perform operations associated with the environment of system 100. Thus, as used herein, "machine" can refer to a stationary or mobile machine performing some type of operation associated with a particular industry (e.g., mining, construction, agriculture, etc.) and operating between or within an engineering environment (e.g., construction site, mine, power plant, etc.). Furthermore, the term "machine" can be used to refer to any remote asset operating within or associated with system 100. Non-limiting examples of stationary machine include engine systems operating in plants, material conveyors, or offshore environments (e.g., offshore drilling platforms). Non-limiting examples of mobile machine include construction machinery, such as trucks, cranes, earthmoving vehicles, mining vehicles, backhoes, or any type of mobile machine operating in a working environment. For example, in Figure 1 In this context, machine 110 is a tractor truck, but embodiments of the disclosed subject matter are not limited thereto. As a non-limiting example, the machine according to embodiments of the disclosed subject matter may be driven by a combustion engine or an electric motor.

[0015] In addition to machine 110, system 100 may also include mobile device 120 and background system 130. For example, when mobile device 120 is used to troubleshoot machine 110 at the work site, the mobile device can be considered to be local to machine 110. For example, when mobile device 120 is local to machine 110, background system 130 can be considered to be remote from mobile device 120.

[0016] As used herein, "local" may refer to mobile device 120 and machine 110 within a specific restricted wireless communication range of each other based on the specific wireless communication protocols, wireless communication networks, and wireless communication circuitry of mobile device 120 and machine 110. According to embodiments of the disclosed subject matter, such wireless communication may be conducted via a Personal Area Network (PAN). As used herein, a Personal Area Network may refer to any short-range (e.g., 1m, 10m, etc.) wireless communication protocol that enables secure communication between two or more of one or more PAN-approved and compatible devices (e.g., machine 110 and mobile device 120). According to one or more embodiments, the PAN may present a wireless communication network using short-wavelength UHF radio waves from 2.400 GHz to 2.485 GHz (e.g., In the form of ), the PAN can be a network that cannot be enhanced or duplicated, and it can be implemented to better ensure that the local authentication of the mobile device 120 is accurate. The so-called local wireless communication network may be referred to herein as the second wireless communication network 144. Local may also mean, for example... The wireless communication connection has not yet been extended by the extender.

[0017] As used herein, remote may mean non-local. For example, remote may mean that each of mobile device 120 and machine 110 is within a specific wireless communication range (or ranges) of background system 130, but not within a specific smaller communication range of background system 130, based on a specific wireless communication protocol (or several protocols), wireless communication network, and wireless communication circuitry of mobile device 120 and background system 130. Thus, machine 110 may be remote from background system 130. For example, depending on the location of mobile device 120, background system 130 may also be considered remote from mobile device 120. Remote may also mean, for example, The wireless communication connection has been extended by the extender.

[0018] The communication network between machine 110 and backend system 130 may be referred to herein as first communication network 142, and the communication network between mobile device 120 and backend system 130 may be referred to herein as third communication network 146. In this respect, first communication network 142 and / or third communication network 146 may comprise any network providing bidirectional communication between two and / or more of one or more facilities, computer systems and / or servers (e.g., between machine 110 and backend system 130 and between mobile device 120 and backend system 130, respectively).

[0019] The first communication network 142 and / or the third communication network 146 may be wireless communication networks. For example, the first wireless communication network 142 and / or the third wireless communication network 146 may be broadband-based, such as cellular-based and / or LAN-based (e.g., Wi-Fi or a client router). In this respect, the first wireless communication network 142 and / or the third wireless communication network 146 may implement NMT, GSM, LET, or 5G, along with corresponding platforms and access, or be implemented via them.

[0020] Optionally, the first communication network 142 and the third communication network 146 may be the same type of network and / or use the same communication protocol (e.g., the same wireless communication protocol). According to one or more embodiments, the first communication network 142 and / or the third communication network 146 may include internet access and therefore include the internet. The first communication network 142 and / or the third communication network 146 may include one or more devices and subsystems adapted to support cellular communication networks (e.g., one or more cellular communication towers and / or antennas), as well as wired or wireless network components supporting cellular communication networks (e.g., wireless or wired switches, hubs, multiplexers, demultiplexers, etc.).

[0021] The first communication network 142 can provide streaming, real-time, bandwidth-optimized secure data, including operational data, from machine 110 to backend system 130. Therefore, for example, the first communication network 142 can upload data (including operational data) from machine 110 to backend system 130. That is, data (including operational data) can be uploaded to backend system 130 via the first communication network 142, and / or backend system 130 can gain access to data on machine 110 via the first communication network 142.

[0022] Machine 110 may include an onboard system 115 for communicating with onboard components of machine 110 and non-onboard components such as mobile device 120 and background system 130. For example, onboard system 115 may provide (e.g., upload to or allow access to) operational data of machine 110 to (e.g., onboard components such as mobile device 120 and background system 130), and optionally to the onboard components of machine 110. Onboard system 115 may also monitor and collect operational data of machine 110. Access to operational data may include reading and / or writing selected operational data by non-onboard components (e.g., mobile device 120 and background system 130) and / or assigning operational data to said non-onboard components.

[0023] As used herein, operational data can refer to any type of data indicating at least one operational aspect associated with machine 110 or any of its components or subsystems. Operational data may include information relating to the health, productivity, status, settings, control signal transmissions, parameters, operating conditions, and / or performance of one or more components of machine 110 and / or the entire machine 110. Generally, access to or distribution of operational data can be made via a back-end system 130 through a first communication network 142 and via a mobile device 120 through the back-end system 130 and a third communication network 146.

[0024] The airborne system 115 may include a controller 117 (or a distributed controller group), one or more communication components 118, and one or more monitoring devices 119. Typically, data from the monitoring devices 119 can be transmitted to the controller 117 and stored in a memory accessible by the controller 117. Figure 1 (Not explicitly shown) and / or transmitted to one or more non-airborne components (e.g., background system 130 and mobile device 120). Optionally, controller 117 may process data before providing data (or providing access to data) to other components (airborne and / or non-airborne). Controller 117, or one or more of controller 117 and communication components 118, may be referred to herein as a communication entity or a first communication entity. In other words, the communication entity of machine 110 may include controller 117 and one or more of communication components 118.

[0025] Monitoring device 119 may include any means for collecting operational data associated with machine 110. For example, monitoring device 119 may include one or more sensors to measure operating parameters, such as engine and / or machine speed and / or position; fluid pressure, flow rate, temperature, contamination level and / or viscosity; current and / or voltage levels; fluid (i.e., fuel, oil, etc.) consumption rate; load levels (i.e., payload value, percentage of maximum payload limit, payload history, payload distribution, etc.); transmission output ratio, slip, etc.; towing rating and traction data; drive shaft torque; intervals between planned or performed maintenance and / or repair operations; and any other operating parameters of machine 110.

[0026] focus on Figure 2As described above, controller 117 may have components for receiving data from monitoring device 119, processing machine-related data (including operational data), and allowing access to or otherwise outputting such data for use by airborne and non-airborne components (e.g., backend system 130 and mobile device 120). More specifically, according to one or more embodiments, controller 117 may have or implement network manager component 217 regarding access to data. According to one or more embodiments, controller 117 may package the monitored operational data for transmission to backend system 130.

[0027] Network manager 217 may have or implement processor (or processing circuitry) 220 and memory (e.g., database, flash memory, etc.), the processor providing electronic service logic (e.g., data link logic, feature logic). Such components may be operatively provided to establish and control network connections and facilitate communication with other components or systems via appropriate networks, such as communication with backend system 130 and mobile device 120 via first communication network 142 and second communication network 144, respectively. For example, the ET database may collect and store status parameters, configuration parameters, diagnostic codes, disassembly / assembly instructions, etc., and the ET server may provide data from the ET database to backend system 130 (or provide access to the ET database) via first communication network 142.

[0028] Network manager 217 may also provide a communication interface with communications component 118 via dedicated data link 1180 (e.g., J1939 or CDL). Incidentally, communications component 118 may be one or more components that provide airborne cellular radio, Wi-Fi radio, and / or client routing communications to off-board systems (e.g., back-end system 130).

[0029] Network manager 217 can establish a first network interface 222 and communicate with the background system 130 (via the first communication network 142). Similarly, network manager 217 can establish a second network interface 224 and communicate with the mobile device 120 (via the second communication network 144). As discussed in more detail below, the mobile device 120 and controller 117 can communicate with each other (e.g., transmit, receive, and provide access to data) through the background system 130.

[0030] The backend system 130 may have remote service components 132 and telematics components or modules 136 that are operatively connected to each other. Each of the remote service components 132 and telematics components 136 may be implemented by a server or a group of servers (e.g., via the cloud).

[0031] Remote service component 132 can be operatively coupled to telematics component 136, which may provide memory (e.g., an ET database), a data aggregator, graphical user interface (GUI) logic, and digital steward platform (DSP). Remote service component 132 can also provide online (i.e., network) access to electronic technician (ET) services, such as access to troubleshooting manuals, code lists, parameter lists, etc. According to one or more embodiments, remote service component 132 may provide (e.g., services) content (e.g., machine operation data) and / or network content (e.g., manuals) to mobile device 120.

[0032] Telematics processing unit 136 can be operatively coupled to remote service unit 132, and the telematics processing unit can provide capabilities including MQ (i.e., message passing via a message server according to MQ Telemetry Transport (MQTT), ED, and Common Data Service (CDS). Telematics processing unit 136 can also provide a gateway (e.g., a priority queue) between backend system 130 and machine 110. Typically, telematics processing unit 136 can integrate telematics data (e.g., operation time, location, fuel consumption, odometer readings, etc.) from one or more machines (e.g., machine 110).

[0033] The telematics unit 136 can establish a network interface 137 and communicate with the network manager 217 via the network interface 137 (via the first communication network 142). Similarly, the remote service unit 132 can establish a network interface 133 and communicate with the mobile device 120 via the network interface 133 (via the third communication network 146).

[0034] The mobile device 120, which can be operated by the technician 10, can be a tablet computer, a PDA, or some other handheld portable device. The mobile device 120 may be referred to herein as a mobile repair or troubleshooting device 120 because the technician 10 can use the mobile device 120 to repair (e.g., diagnose, troubleshoot, service) one or more machines, such as machine 110. As discussed in more detail below, such troubleshooting can be wireless and local to machine 110.

[0035] The mobile device 120 may include a controller or control circuit 122, an operator interface 124, and a communication component (or circuitry) 126. The operator interface 124 and the communication component 126 may be operatively coupled to the controller 122, which may consist of one or more processors and corresponding memories.

[0036] Controller 122 can run a thin mobile application. As used herein, a thin mobile application can mean an application that executes a relatively small amount of code on mobile device 120 and relies on external servers or hardware components, particularly backend system 130, for most of its functionality and code-based maintenance. Discussed in more detail below, the thin mobile application can assist in wirelessly pairing mobile device 120, particularly communication component 126, with machine 110, particularly its network manager 217. The thin mobile application can also render an operator interface to receive input from technician 10 and output information to technician 10. According to one or more embodiments, the thin mobile application can provide an in-app web browser for accessing web pages via the Internet (via backend system 130). Accessing web pages can display additional content on mobile device 120, such as maintenance data in the form of manuals (e.g., repair or troubleshooting manuals), parts lists, inventory, parts delivery times, estimated lifespan, etc. According to one or more embodiments, the additional content can be content from backend system 130 that relates to the maintenance of machine 110 but is not directly derived from data received from machine 110 at backend system 110.

[0037] Operator interface 124 can receive input from technician 10 and output information to technician 10. For example, operator interface 124 can enable a graphical user interface (GUI) on a display device to receive input from technician 10 to communicate with machine 110 and back-end system 130. Operator interface 124 can also display or otherwise output data received from back-end system 130 (including machine operation data). According to one or more embodiments, operator interface 124 can display or otherwise output data directly from machine 110, for example, to establish and maintain a local wireless connection. As described above, operator interface 124 can be rendered at least in part by a thin mobile application running on mobile device 120. It is also noted above that operator interface 124 can provide an in-app web browser via the thin mobile application to access web pages over the Internet (via back-end system 130).

[0038] The communication component 126 can establish a network interface 123 and communicate with the backend system 130 via a third communication network 146. The communication component 126 can also establish a communication interface 127 in conjunction with a thin mobile application running on the mobile device 120 to communicate directly with the machine 110 via a second communication network 144.

[0039] Industrial applicability

[0040] As described above, this disclosure relates to providing local repair, and more specifically, to enabling local service functionality of mobile devices for local repair of the machine.

[0041] According to embodiments of the disclosed subject matter, a maintenance (e.g., diagnostic, update, troubleshooting) system may include one or more communication components of a mobile device and a machine that are independently (e.g., wirelessly) connected to a remote back-end system. As described above, the mobile device may be referred to herein as a mobile maintenance or troubleshooting device. This arrangement may also allow the mobile device to communicate via (e.g., using short-wavelength UHF radio waves from 2.400 GHz to 2.485 GHz, for example...) A local wireless connection is established between the mobile device and the machine on a specific personal area network (LAN). This local wireless connection between the mobile device and the machine verifies that the mobile device is located locally on the machine.

[0042] Authentication of the mobile device locally on the machine, i.e., proximity authentication, may also include an authorization protocol and can be enabled by a thin mobile application running on the mobile device. Such authorization may include cryptographic operations, for example, to verify that the local network is not based on an extended connection (e.g., an extended-range connection). connect).

[0043] Once the mobile device has been verified as being local to the machine, it can be enabled to perform operations on the machine, such as troubleshooting, diagnostics, and repairs. In other words, once the mobile device has been verified as being local to the machine, restrictions on the selection of which repair functions the mobile device has relative to the machine can be removed. Alternatively, the mobile device may not be able to access higher-privilege repair functions. Such higher-privilege repair functions may include: writing configuration parameters, resetting parameters, overwriting outputs, performing calibrations, diagnostic tests, and / or diagnostic procedures.

[0044] Verifying that the mobile device is local to the machine ensures that the technician operating it possesses context awareness and the ability to respond to changes. This allows local technicians to directly perform machine maintenance (e.g., diagnostics, troubleshooting, parameter writing) using the mobile device, without relying on remote technicians. This is especially important when remote technicians might intentionally limit their maintenance capabilities due to a lack of context awareness or the ability to respond to local changes, which could be available locally. For example, remote technicians could be restricted from changing machine thresholds, operating modes, speed limits, etc.

[0045] Such an arrangement can also facilitate access to local service functions for mobile devices when verifying that the mobile device is local to the machine, rather than requiring communication and coordination with a remotely located technician relative to the machine's local technician. This is because the mobile device may already have local maintenance functions pre-configured (e.g., as a subscriber or under subscriber control, using a password entered by the technician on the mobile device for network security purposes). According to one or more embodiments, if a technician is near the machine within range of the machine's PAN, the mobile device can automatically connect to the machine, for example, by entering a password on the mobile device before or during the connection process.

[0046] According to embodiments of the disclosed subject matter, the mobile device can connect directly (e.g., wirelessly) to the backend system, rather than via one or more communication components that can also connect directly (e.g., wirelessly) to the backend system. Therefore, the mobile device can connect directly to the machine and the backend system via a different network and without directly connecting to the backend system via the machine itself. This eliminates the need for the mobile device to connect to the machine via a wired connection for maintenance operations. A wireless adapter may also not be required on the machine.

[0047] This arrangement also allows mobile devices to provide local repair capabilities to the machine when wirelessly connected and authenticated as being local, while simultaneously accessing the internet (via a direct wireless connection to the back-end system). As mentioned above, local repair capabilities requiring higher privileges may include: writing configuration parameters, resetting parameters, overriding outputs, performing calibrations, diagnostic tests, and / or diagnostic procedures.

[0048] Thin mobile applications running on mobile devices can provide a web browser to access websites independently of the local maintenance capabilities also provided by the thin mobile application. Therefore, the mobile device can avoid attempting to connect directly to the machine, which is considered the means of gaining internet access. Thin mobile applications can also be operating system-agnostic (OS), meaning they can run on mobile devices with different OSs.

[0049] Turn Figure 3 , Figure 3 This is a flowchart of method 300 according to one or more embodiments of the disclosed subject matter.

[0050] Typically, method 300 can be characterized as a method for providing local maintenance functionality to a mobile device such as mobile device 120, thus mobile device 120 can be used to provide local maintenance (e.g., troubleshooting, diagnosis, repair, etc.) to a machine such as machine 110. Method 300 can be implemented by a system (e.g., system 100) according to embodiments of the disclosed subject matter. Therefore, method 300 or portions thereof can be implemented using a non-transitory computer-readable storage medium (or different media distributed across machine 110, mobile device 120, and background system 130) storing computer-readable instructions that, when executed by one or more computers (again, including machine 110, mobile device 120, and background system 130), cause one or more computers to perform method 300 or, as appropriate, perform portions of the method.

[0051] At S302, method 300 may include providing mobile device 120 with access to a network manager (e.g., network manager 217) of machine 110. Such access may include a pairing process between network manager 217 and mobile device 120 via a wireless communication network (e.g., a wireless communication network 144 of a personal area network (PAN)). Reference Figure 4 In more detail, providing access in S302 may further include: mobile device 120 searching for one or more network managers of the corresponding one or more machines 110; mobile device 120 receiving machine-related information, such as device name, type, and / or serial number, from each of the one or more network managers; and, in response to a technician 10 operating mobile device 120 selecting a machine from the machines, pairing mobile device 120 with one of the network managers of said machine. The pairing process may involve encryption, for example, to prevent the use of extended connections (e.g., connections extended using a range extender). connect).

[0052] Upon successful pairing, at S304, method 300 may include providing (e.g., enabling) a local repair function on mobile device 120, enabling mobile device 120 to perform local repairs on machine 110 (i.e., the paired machine). The following section discusses... Figure 4In more detail, enabling may include the mobile device 120 connecting to the machine 110 via a remote system, such as a back-end system 130. According to one or more embodiments, the back-end system 130 may authorize the connection prior to pairing and / or as part of the provision at S304. Authorization prior to pairing may include limiting the permissions (e.g., higher access permissions) of the technician or operator of the mobile device 120. Such permissions may be associated with the user of the machine 110, a subscriber associated with the mobile device 120, a subscriber associated with the technician 10 (e.g., the employer of the technician 10), and / or a subscriber identifier associated with the machine, a subscriber associated with the mobile device, or a subscriber associated with the technician 10.

[0053] If mobile device 120 is not paired and connected to machine 110, local repair functions may be disabled. However, according to one or more embodiments, mobile device 120 with remote or non-local repair functions may still be enabled even when mobile device 120 and machine 110 are not paired and connected according to local connection requirements to enable local repair functions. These remote or non-local repair functions may be more restrictive than local repair functions. Remote or non-local repair functions may not require higher privileges.

[0054] After the mobile device 120 and the machine 110 are paired and connected, at S306, method 300 may include performing local maintenance operations using the mobile device 120. The local maintenance operations may be performed using a thin mobile application running on the mobile device 120 and based on input from the technician 10 to the mobile device 120.

[0055] Performing local maintenance operations may include transmitting maintenance data, such as troubleshooting data, between network manager 217 and backend system 130 via a communication network such as first communication network 142. Performing local maintenance operations may also include transmitting maintenance data, such as troubleshooting data, between the network, manager 217, and mobile device 120 via a communication network such as third communication network 146. Such maintenance data may not be transmitted directly from network manager 217 to mobile device 120 via second communication network 144. According to one or more embodiments, local maintenance may include using mobile device 120 to write (e.g., set configuration parameters) data to network manager 217 and / or other components of machine 110 (e.g., controller 117 or its associated memory). For example, local maintenance may include: writing configuration parameters, resetting parameters, overwriting outputs, performing calibration, diagnostic tests, and / or diagnostic procedures.

[0056] The local repair operation of S306 may also include accessing network content via a third network 146 in the form of the Internet using a thin mobile application running on mobile device 120. That is, mobile device 120 can access network content while still being paired with and connected to the network manager 217 of machine 110 locally.

[0057] Figure 4 This is a maintenance sequence diagram according to one or more embodiments of the disclosed subject matter. The sequence diagram may represent an exemplary sequence of events providing local maintenance functionality to a mobile device (e.g., mobile device 120), so that mobile device 120 can be used to provide local maintenance (e.g., troubleshooting, diagnosis, repair, etc.) to a machine (e.g., machine 110).

[0058] First, a local access level can be set for operators such as technician 10. The local access level can be specifically set for a particular technician or another subscriber (e.g., the owner of machine 110 and / or the owner of mobile device 120). Local access level settings may include setting the local access level for the owner or administrator 140 of the local service function methods and processes (including software, such as a thin mobile application running on mobile device 120) and sending such information to the backend system 130 for storage, for example, by the remote service component 132.

[0059] This sequence may then involve a login procedure at mobile device 120. The login procedure may involve, for example, a technician or the owner of mobile device 120 entering an identifier and password at mobile device 120. The login information may be transmitted and processed by a thin mobile application 125 running on mobile device 120, and then transferred from mobile device 120 to background system 130. In response, background system 130 (e.g., its remote service component 132) may retrieve a previously stored local access level associated with the login information and send authorization information to mobile device 120 via thin mobile application 125. The authorization information may include the local access level, a security token, and, for example, a digital signature from the owner or administrator 140.

[0060] This sequence can then involve a pairing process, whereby mobile device 120 and machine 110 can pair when mobile device 120 is local to machine 110. The pairing process can involve using a specific Personal Area Network (PAN), for example... As a non-limiting example, under the control of the operating system (OS) 121 of the mobile device 120, a search is conducted for devices that output local wireless communication signals. Each machine, including machine 110, can send device information, such as device name, type, and serial number, from its network manager 217. Therefore, based on the number of machines whose transmission distance is within range of the mobile device 120, the mobile device 120 can generate a list of candidate machines for selection. The technician 10 can select one of the listed machines via the mobile device 120 to pair the mobile device 120 with the selected machine 110.

[0061] The pairing process may involve network-specific pairing and authentication between the mobile device 120 and the network manager 217 of the machine 110. Optionally, the mobile device 120 may pair with only one machine at a time. Alternatively, the mobile device 120 may pair with multiple machines simultaneously, both machines and multiple machines within the mobile device 120's transmission capacity. Optionally, the pairing process may involve encryption, for example, to prevent the use of already extended connections (e.g., connections extended using a range extender). connect).

[0062] Once the mobile device 120 is paired with the machine 110, the sequence can proceed to the connection process. According to one or more embodiments, the mobile device 120 may connect to only one machine 110 at a time. However, in other embodiments of the disclosed subject matter, the mobile device 120 may pair with multiple machines simultaneously, continuously or intermittently.

[0063] The connection process may include setting up and establishing a secure connection between the mobile device 120 and the machine 110, and may be initiated by a technician 10 using the mobile device 120 to input a connection command for a specific machine. According to one or more embodiments, the connection command may be generated in response to input to the operator interface 124 of the mobile device 120.

[0064] Figure 4 Exemplary processes are illustrated, including setting up a secure connection between the thin application 125 and the network manager 217, secure heartbeat, local state, and digital signature processing between the thin application 125 and the network manager 217; setting up and connecting a real-time (RT) session between the thin application 125 and the background system 130; setting up and connecting an RT session between the background system 130 and the network manager 217; providing an interactive web user interface (UI) from the background system 130 to the mobile device 120; and providing machine data, such as machine operation data, from the network manager 217 to the background system 130 for access by the mobile device 120.

[0065] Once the mobile device 120 is connected to the machine 110, the technician 10 can use the mobile device 120 to perform local repairs. According to one or more embodiments, such as Figure 4 As shown, technician 10 can use mobile device 120 to select a specific maintenance feature associated with machine 110. Such a process may involve sending selection information from mobile device 120 to network manager 217 via background system 130. Network manager 217 may then provide mobile device 120 with access to data associated with the specific maintenance feature, such as operational data (e.g., transmitted to mobile device), via background system 130.

[0066] The data can be interactive data in the sense that the technician 10 can use the mobile device 120 to modify the provided data. For example, the technician 10 can provide input to the mobile device 120 to write data such as machine parameter data to the machine 110. According to one or more embodiments, in the case where the mobile device 120 outputs comments to modify the data of the machine 110 (e.g., write parameter data), the background system 130 can verify that the mobile device 120 is still local to the machine 110 and that the subscriber associated with the mobile device 120 has the right to write the parameter data before actual writing is permitted. Local may mean that the mobile device 120 is paired with and connected to the machine 110 as discussed above. During verification, local maintenance can be performed (e.g., local maintenance may include writing configuration parameters, resetting parameters, overwriting outputs, performing calibration, diagnostic tests, and / or diagnostic procedures). For example, as Figure 4 As shown, one or more parameters can be written via network manager 217 as described above, and then written to airborne system 115 or its components (e.g., controller 117).

[0067] Although various aspects of this disclosure have been specifically shown and described with reference to the foregoing embodiments, those skilled in the art will understand that various additional embodiments can be contemplated through modifications to the disclosed machines, systems, and methods without departing from the spirit and scope of the disclosure. Such embodiments should be understood to fall within the scope of this disclosure as defined by the claims and any equivalents.

Claims

1. A system for troubleshooting a working machine locally, comprising: A first communication entity (117) is mounted on the working machine (110), the first communication entity (117) including a network manager (217). A background system (130) located away from the working machine (110); A mobile device (120) hosting a thin client application (125) to troubleshoot the work machine (110) locally when it gains access to the network manager (217); A first communication network (142) is accessible by the backend system (130) and the first communication entity (117) for the first communication entity (117) to communicate with the backend system (130); A second communication network (144) is accessible by the mobile device (120) and the network manager (217) to allow the mobile device (120) to gain access to the network manager (217); as well as A third communication network (146) is accessible to the mobile device (120) and the backend system (130) for communication between the mobile device (120) and the backend system (130). The second communication network (144) is a personal area network (PAN), and the thin client application (125) only gains access to the PAN when the mobile device (120) is local to the PAN manager (217) and within the transmission distance of the PAN. When the thin client application (125) accesses the network manager (217) via the second communication network (144), the mobile device (120) and the network manager (217) transmit troubleshooting data to each other through the background system (130) only via the first communication network (142) and the third communication network (146) without through the second communication network (144).

2. The system according to claim 1, wherein the mobile device (120) accesses the network manager (217) via the second communication network (144) while using the thin client application (125) to access the media via the background system (130) through the Internet, which is the third communication network (146).

3. The system of claim 1, wherein the mobile device (120) uses the network manager (217) to write troubleshooting data to one or more controllers of the work machine (110) in response to input from a technician operating the mobile device (120).

4. The system of claim 1, wherein the mobile device (120) obtains local troubleshooting capability to troubleshoot the work machine (110) based on the permission granted to the network manager (217) by the subscriber associated with the work machine (110) and the mobile device (120).

5. The system of claim 1, wherein the second communication network (144) is a wireless communication network using short-wavelength UHF radio waves from 2.400 GHz to 2.485 GHz.

6. The system according to claim 1, When the thin client application (125) does not obtain or has lost access to the network manager (217) via the second communication network (144), the mobile device (120) is prohibited from writing data to the network manager (217) via the background system (130) through the first communication network (142) and the third communication network (146). When the thin client application (125) does not obtain or has lost access to the network manager (217) via the second communication network (144), the mobile device (120) is authorized to read data from the network manager (217) via the background system (130) through the first communication network (142) and the third communication network (146).

7. The system of claim 1, wherein the mobile device (120) has a limited troubleshooting capability to troubleshoot the work machine (110) without accessing the network manager (217) via the second communication network (144), based on permissions granted to the subscriber associated with the work machine (110) and the mobile device (120).

8. A method for troubleshooting a working machine locally, comprising: Access to the network manager (217) is provided to the mobile troubleshooting device (120) via a pairing process between the network manager (217) of the machine (110) and the mobile troubleshooting device (120) through a personal area network; When the network manager (217) and the mobile troubleshooting device (120) are successfully paired and connected via the personal area network, the local troubleshooting function on the mobile troubleshooting device (120) is enabled from the background system (130); and With the mobile troubleshooting device (120) and the network manager (217) paired and connected, a local troubleshooting operation is performed in response to operator input at the mobile troubleshooting device (120). The local troubleshooting operation includes transmitting troubleshooting data between the background system (130) and the network manager (217) via a first wireless communication network (142) and between the background system (130) and the mobile troubleshooting device (120) via a third wireless communication network (146), without transmitting the troubleshooting data between the network manager (217) and the mobile troubleshooting device (120) via the personal area network.

9. The method according to claim 8, wherein each of the first wireless communication network (142) and the third wireless communication network (146) is the Internet.

10. The method of claim 8 further includes, when the mobile troubleshooting device (120) and the network manager (217) are paired and connected, using an application running on the mobile troubleshooting device (120) to access network content via the Internet through the background system (130).

11. The method of claim 8, wherein the local troubleshooting function of the mobile troubleshooting device (120) is limited according to the permissions granted to the subscriber associated with the machine (110) and the mobile troubleshooting device (120).

12. The method of claim 8 further includes disabling some or all of the local troubleshooting operations when the mobile troubleshooting device (120) and the network manager (217) are not connected.

13. The method of claim 8, wherein the personal area network uses short-wavelength UHF radio waves from 2.400 GHz to 2.485 GHz.

14. The method of claim 8, further comprising providing a limited troubleshooting function relative to the local troubleshooting function of the mobile troubleshooting device (120) when the mobile troubleshooting device (120) and the network manager (217) are not connected.

Images