Software update system and method for components of a work machine

The software update system for work machines uses differential data and a gateway device with separate boards to efficiently update components, addressing resource limitations and ensuring software integrity.

JP7596072B2Active Publication Date: 2024-12-09KOMATSU LTD
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
JP2020031851
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2020-02-27
Publication Date
2024-12-09
Estimated Expiration
2040-02-27

AI Technical Summary

Technical Problem

Components of work machines often lack sufficient computational resources for differential application calculations, making it difficult to efficiently update their software.

Method used

A software update system that utilizes differential data to update software on work machine components, involving a gateway device with separate boards to manage and generate updated software, and a network structure to distribute and apply difference data.

Benefits of technology

Enables software updates on work machine components regardless of their computational resources, reducing network communication load and allowing more resources for machine control, with backup mechanisms for software integrity.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007596072000001
    Figure 0007596072000001
  • Figure 0007596072000002
    Figure 0007596072000002
  • Figure 0007596072000003
    Figure 0007596072000003
Patent Text Reader

Abstract

To update software for components of a work machine using difference data.SOLUTION: A reception section receives, over an external network, difference data for updating a first component to be connected over an internal network of a work machine. A software obtainment section obtains, from the first component, first software which the first component stores and executes. A software generation section applies the difference data to first software, for generating second software. A software output section outputs the generated second software to the first component.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a system and method for updating software for components onboard a work machine. [Background technology]

[0002] A work machine is provided with components for controlling the work machine or for monitoring the state of the work machine. The components are configured with microcomputers or the like, and perform their functions by executing software. For this reason, the software of the components may be updated in order to expand the functions of the components, for example. Patent Document 1 discloses a technique for applying software difference data to update software for components of a work machine. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2014-177816 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, the work machine components may not have sufficient computational resources for the application of the differentials. An object of the present disclosure is to provide a system and method for updating software for a component of a work machine, which is capable of updating software of the component of the work machine using difference data. [Means for solving the problem]

[0005] According to a first aspect of the present invention, a software updating system for updating software of a first component of a work machine includes a receiving unit that receives, via an external network, differential data for updating the first component connected via an internal network of the work machine, a software acquisition unit that acquires from the first component first software that is stored and executed by the first component, a software generation unit that generates second software by applying the differential data to the first software, and a software output unit that outputs the generated second software to the first component. Effect of the Invention

[0006] According to the above aspect, it is possible to update software of components of a work machine using difference data. [Brief description of the drawings]

[0007] [Figure 1] 1 is a configuration diagram of a software update system according to a first embodiment. [Diagram 2] FIG. 1 is a perspective view showing the appearance of a work machine. [Diagram 3] 2 is a block diagram showing the configuration of a control system of the work machine. FIG. [Figure 4] 2 is a block diagram showing a configuration of a component management server according to the first embodiment. FIG. [Diagram 5] 2 is a block diagram showing a configuration of a software management server according to the first embodiment. FIG. [Figure 6] 4 is an example of a software table according to the first embodiment. [Figure 7] FIG. 2 is a sequence diagram showing a method for updating software of a component in the software update system according to the first embodiment. [Figure 8] 5 is a flowchart showing a part number confirmation process of the gateway device according to the first embodiment. [Figure 9]5 is a flowchart showing a software update process of the gateway device according to the first embodiment. [Figure 10] FIG. 11 is a schematic block diagram showing a configuration of a gateway device according to a second embodiment. [Figure 11] FIG. 11 is a schematic block diagram showing a configuration of a gateway device according to a third embodiment. [Figure 12] FIG. 13 is a schematic block diagram showing a configuration of a gateway device according to a fourth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] First Embodiment FIG. 1 is a configuration diagram of a software update system 1 according to the first embodiment. The software update system 1 manages the product numbers of software for components 12 equipped in multiple work machines 10. The software update system 1 includes multiple work machines 10, a component management server 30, a software management server 50, and a developer terminal 70. Software is data used to realize the functions of hardware. Software may include programs and setting data. The software product number is a unique identifier for identifying the software. The software product number is expressed, for example, by a combination of multiple numbers or letters.

[0009] Each work machine 10 includes a gateway device 11 and two or more components 12. The gateway device 11 is also an example of the component 12. The gateway device 11 is connected to an internal network of the work machine 10 and an external network. The internal network is a network that connects the components 12 inside the work machine 10 with each other. The external network is a wide area network (WAN) that connects the work machine 10 with devices outside the work machine. Each component exerts a function for controlling the work machine 10 or monitoring the status of the work machine 10. Each component 12 and the gateway device 11 are connected to each other via the internal network of the work machine 10. In FIG. 1, a hydraulic excavator is illustrated as the work machine 10, but other work machines may be used, for example, a bulldozer, a dump truck, or a wheel loader.

[0010] The component management server 30 stores the part numbers of the hardware and software of the components 12 equipped in a plurality of work machines 10, and provides the work machines 10 with data for updating the software of the components 12. Specifically, the component management server 30 provides the work machines 10 with difference data between the pre-update software and post-update software of the components 12 via an external network.

[0011] The software management server 50 associates with the hardware part number of the component 12 and stores multiple pieces of software with different part numbers that are applicable to the component 12 related to the part number. The software management server 50 also generates difference data for software updates and transmits it to the component management server 30. The hardware part number is a unique identifier for identifying the component 12. The hardware part number is expressed, for example, by a combination of multiple numbers or letters of the alphabet.

[0012] The developer terminal 70 is a terminal operated by a software developer. The developer develops software using the developer terminal 70, and transmits the developed software from the developer terminal 70 to the software management server 50.

[0013] Configuration of the work machine 10 FIG. 2 is a perspective view showing the external appearance of the work machine 10. As shown in FIG. The work machine 10 includes a hydraulically operated work implement 1100, a rotating body 1200 that supports the work implement 1100, and a running body 1300 that supports the rotating body 1200.

[0014] "Work Machine 1100" The work machine 1100 includes a boom 1110 , an arm 1120 , a bucket 1130 , a boom cylinder 1140 , an arm cylinder 1150 , and a bucket cylinder 1160 .

[0015] The boom 1110 is a support that supports the arm 1120 and the bucket 1130. A base end of the boom 1110 is attached to the front of the rotating body 1200 via a pin. The arm 1120 connects the boom 1110 and the bucket 1130. The base end of the arm 1120 is attached to the tip of the boom 1110 via a pin. The bucket 1130 is a container having a blade for digging up earth and sand, etc. The base end of the bucket 1130 is attached to the tip of the arm 1120 via a pin.

[0016] The boom cylinder 1140 is a hydraulic cylinder for operating the boom 1110. A base end of the boom cylinder 1140 is attached to the rotating body 1200. A tip end of the boom cylinder 1140 is attached to the boom 1110. The arm cylinder 1150 is a hydraulic cylinder for driving the arm 1120. A base end of the arm cylinder 1150 is attached to the boom 1110. A tip end of the arm cylinder 1150 is attached to the arm 1120. The bucket cylinder 1160 is a hydraulic cylinder for driving the bucket 1130. A base end of the bucket cylinder 1160 is attached to the arm 1120. A tip end of the bucket cylinder 1160 is attached to the bucket 1130.

[0017] "Rotating Body 1200" The rotating body 1200 is provided with an operator's cab 1210 in which an operator sits. The operator's cab 1210 is provided at the front of the rotating body 1200 and on the left side of the work machine 1100.

[0018] An operating device 1211 for operating the work machine 1100 is provided inside the operator's cab 1210. Hydraulic oil is supplied to the boom cylinder 1140, the arm cylinder 1150, and the bucket cylinder 1160 in accordance with the amount of operation of the operating device 1211, thereby driving the work machine 1100. Furthermore, hydraulic oil is supplied to a rotation motor (not shown) in accordance with the amount of operation of the operating device 1211, thereby rotating the rotating body 1200.

[0019] Component 12 The work machine 10 is equipped with a position / orientation calculator 12a and a tilt detector 12b. The position / orientation calculator 12a and the tilt detector 12b are examples of components 12. The work machine 10 is also equipped with a gateway device 11 that connects an internal network that connects the various components with an external network. The gateway device 11 is provided in a cab 1210. The other components 12 may be similarly provided in the cab 1210, or may be provided outside the cab 1210 on the rotating body 1200, for example.

[0020] The position and orientation calculator 12a calculates the position of the rotating body 1200 and the orientation in which the rotating body 1200 faces. The position and orientation calculator 12a includes a first receiver 12a1 and a second receiver 12a2 that receive positioning signals from artificial satellites that constitute a Global Navigation Satellite System (GNSS). The first receiver 12a1 and the second receiver 12a2 are installed at different positions on the rotating body 1200. The position and orientation calculator 12a detects the position of a representative point O (origin of a vehicle body coordinate system) of the rotating body 1200 in a site coordinate system (not shown) based on the positioning signal received by the first receiver 12a1. For example, the position and orientation calculator 12a detects the position of the first receiver 12a1 based on the positioning signal received by the first receiver 12a1, and detects the position of the representative point O by horizontally moving the position of the first receiver 12a1 based on the relative position of the representative point O with respect to the first receiver 12a1 that is stored in advance. The position and orientation calculator 12a uses the positioning signal received by the first receiver 12a1 and the positioning signal received by the second receiver 12a2 to calculate the orientation of the rotating body 1200 as the relationship between the detected installation position of the first receiver 12a1 and the installation position of the second receiver 12a2.

[0021] The inclination detector 12b measures the acceleration and angular velocity of the rotating body 1200, and detects the inclination (e.g., roll angle and pitch angle) of the rotating body 1200 based on the measurement results. The inclination detector 12b is installed, for example, on the underside of the cab 1210. For example, an IMU (Inertial Measurement Unit), which is an inertial measurement device, can be used as the inclination detector 12b.

[0022] FIG. 3 is a block diagram showing the configuration of a control system of the work machine 10. The gateway device 11 includes a first board 100 and a second board 200 which are physically separate.

[0023] The first board 100 includes a first processor 110, a first main memory 130, a first storage 150, and a first interface 170. The first processor 110 reads a program from the first storage 150, expands it in the first main memory 130, and executes a predetermined process according to the program. The first storage 150 stores the same software including the program in two systems as main software and backup software. The main software is software used to exercise the function of the software under normal circumstances. The backup software is software used to recover the main software when an abnormality occurs in the main software. That is, the first board 100 exercises its function by executing the main software. In addition, when an abnormality occurs due to, for example, a software update error and the main software cannot be executed, the first board 100 recovers the main software by copying the backup software to the main software, and executes the recovered main software. The first board 100 is an example of a component 12. The first interface 170 is connected to a plurality of components 12 for controlling the work machine 10 via a first network N1, which is an internal network. Examples of the components 12 connected to the first board 100 include an engine control component that acquires various engine data by sensors and controls the operation of the engine, a hydraulic control component that acquires various data related to hydraulic equipment that controls the operation of the work machine 1100 by sensors and controls the hydraulic equipment, and a monitor control component that acquires data from various sensors of the work machine 10 and controls the display of a monitor (not shown). Basic operational control regarding the operation of the work machine 10 is performed by the components 12 connected to the first network N1.

[0024] The second board 200 includes a second processor 210, a second main memory 230, a second storage 250, and a second interface 270. The second processor 210 reads a program from the second storage 250, expands it in the second main memory 230, and executes a predetermined process according to the program. The second interface 270 is connected to a plurality of components 12 for expanding the functions of the work machine 10 via a second network N2, which is an internal network. Examples of the components 12 connected to the second board 200 include an image display component that performs predetermined image processing on an image captured by a camera and controls the display, a machine guidance component that displays and controls a guidance monitor for guiding the operator on the positional relationship between the design surface of the construction site and the work machine 10, a payload component for measuring the amount of soil excavated by the work machine 1100, and a communication component that controls communication equipment for communicating with an external server or the like and acquires data from various sensors of the work machine. The components 12 connected to the second network N2 provide the work machine 10 and the operator with expanded information, such as information for improving the functions of the work machine. The second substrate 200 may be an example of a component of a work machine. The first interface 170 and the second interface 270 are connected to be able to communicate with each other. In addition, the first board 100 and the second board 200 store connection information indicating paths to each component 12 included in the work machine 10. The connection information may be, for example, a routing table. The connection information is updated by exchanging information between the first board 100 and the second board 200 every time a component 12 is attached to or removed from the work machine 10.

[0025] In other embodiments, the first substrate 100 or the second substrate 200 may include a custom LSI (Large Scale Integrated Circuit) such as a PLD (Programmable Logic Device) in addition to or instead of the above configuration. Examples of PLDs include PAL (Programmable Array Logic), GAL (Generic Array Logic), CPLD (Complex Programmable Logic Device), and FPGA (Field Programmable Gate Array). In this case, some or all of the functions realized by the first substrate 100 or the second substrate 200 may be realized by the integrated circuit.

[0026] Examples of the first storage 150 and the second storage 250 include a magnetic disk, a magneto-optical disk, an optical disk, a semiconductor memory, etc. The first storage 150 and the second storage 250 may be internal media directly connected to a bus line, or may be external media connected to the gateway device 11 via the first interface 170 or a communication line. In at least one embodiment, the first storage 150 and the second storage 250 are non-transitory tangible storage media. The computational resources of the second substrate 200 are greater than the computational resources of at least one component 12. The computational resources of the second substrate 200 are preferably greater than the computational resources of the first substrate 100. The computational resources are resources used in calculations in a computer. The computational resources are resources that provide the computation time or memory capacity of a computer. Examples of computational resources include a CPU, a main memory, and a storage. The capacity of the second main memory 230 is preferably greater than the capacity of the first main memory 130. The capacity of the second storage 250 is preferably greater than the capacity of the first storage 150.

[0027] The first processor 110 functions as an input unit 111, an access unit 112, an update unit 113, and an output unit 114 by executing a program stored in the first storage 150.

[0028] The input unit 111 receives an input of an instruction to acquire the software of the component 12 from the second board 200. The input unit 111 also receives an input of an instruction to update the software of the component 12 from the second board 200.

[0029] The access unit 112 acquires current software from the component 12 in accordance with a software acquisition instruction received from the second substrate 200. The current software refers to software that is stored in the component 12 and is being executed to perform its function when accessed by the access unit 112. The current software is an example of first software. The access unit 112 also outputs software to the component 12 in accordance with a software update instruction received from the second substrate 200. The component 12 that receives the software rewrites the software. The access unit 112 is an example of a software acquisition unit that acquires current software from the component 12 and a software output unit that outputs the generated software to the component 12.

[0030] The update unit 113 reads the primary software from the first storage 150 in accordance with the software update instruction received from the second substrate 200. The primary software is an example of current software. The update unit 113 also rewrites the standby software and the primary software in accordance with the software update instruction received from the second substrate 200.

[0031] The output unit 114 outputs the software acquired by the access unit 112 or the update unit 113 to the second board 200.

[0032] The second processor 210 executes a program stored in the second storage 250 to function as a receiving unit 211, an output unit 212, an input unit 213, an access unit 214, a software generating unit 215, and a transmitting unit 216. In addition, in the second storage 250, a storage area for a standby software storage unit 251 is secured.

[0033] The receiving unit 211 receives an instruction to update the software of the component 12 together with the difference data of the software of the component 12 from the component management server 30. The receiving unit 211 also receives an instruction to confirm the product number of the software of the component.

[0034] When the component 12 to be updated is connected to the first board 100, or when the component 12 to be updated is the first board 100, the output unit 212 outputs a software acquisition instruction to the first board 100. The output unit 212 also outputs a software update instruction to the first board 100.

[0035] The input unit 213 receives an input of the software of the component 12 to be updated from the first board 100.

[0036] When the component 12 to be updated is connected to the second board 200, the access unit 214 acquires software from the component 12. The access unit 214 also outputs the software generated by the software generation unit 215 to the component 12 to be updated. The component 12 that receives the software rewrites the software. The access unit 214 is an example of a software acquisition unit that acquires current software from the component 12 and a software output unit that outputs the generated software to the component 12.

[0037] The software generation unit 215 generates updated software by applying the difference data received by the receiving unit 211 to the current software input to the input unit 213 or the current software acquired by the access unit 214. The updated software is an example of the second software. For example, the difference data holds a combination of an offset, which is the number of bits from the beginning of the file, and a changed value for each changed portion. In this case, the software generation unit 215 identifies the relevant portion of the current software based on the offset of the difference data, and rewrites the pre-change value indicated by the difference data in the relevant portion to the changed value. This allows the software generation unit 215 to generate updated software from the current software and the difference data.

[0038] The transmitting unit 216 transmits a response to the request received by the receiving unit 211 to the component management server 30 .

[0039] <Configuration of component management server 30> FIG. 4 is a block diagram showing the configuration of the component management server 30 according to the first embodiment. The component management server 30 includes a processor 310, a main memory 330, a storage 350, and an interface 370. The processor 310 reads a program from the storage 350, loads the program in the main memory 330, and executes a predetermined process in accordance with the program. The interface 370 is connected to the second board 200 of the gateway device 11 and the software management server 50 so as to be able to communicate with each other.

[0040] The programs stored in the storage 350 may be for implementing some of the functions to be performed by the component management server 30. In another embodiment, the component management server 30 may include a custom LSI such as a PLD in addition to or instead of the above configuration. In this case, some or all of the functions implemented by the component management server 30 may be implemented by the integrated circuit.

[0041] Examples of storage 350 include a magnetic disk, a magneto-optical disk, an optical disk, a semiconductor memory, etc. Storage 350 may be an internal medium directly connected to a bus line, or an external medium connected to component management server 30 via interface 370 or a communication line. Also, a program may not be stored in storage 350, but may be delivered to component management server 30 via a communication line, and processor 310 may execute the program. In at least one embodiment, storage 350 is a non-transitory tangible storage medium.

[0042] The processor 310, by executing a program stored in the storage 350, is provided with a differential data receiving unit 311, an update target identifying unit 312, a product number checking unit 313, an update instruction sending unit 314, and a table updating unit 315. In addition, a storage area for a component table 351 is secured in the storage 350.

[0043] The component table 351 stores the part numbers of the hardware and software of the components 12 provided in each of the multiple work machines 10. In other words, the component table 351 stores the machine ID of the work machine 10, and the hardware part number and software part number of the component in association with each other.

[0044] The difference data receiving unit 311 receives, from the software management server 50, the software difference data and the product number of the software to which the difference data is to be applied.

[0045] The update target identifying unit 312 refers to the component table 351 and identifies the component 12 related to the software product number received by the difference data receiving unit 311 and the work machine 10 equipped with that component 12.

[0046] The product number confirmation unit 313 transmits a confirmation request for the software product number of the component 12 to be updated to the work machine 10 identified by the update target identification unit 312. The product number confirmation unit 313 receives the confirmation result of the software product number from the work machine 10. The product number confirmation unit 313 is an example of a product number acquisition unit that acquires the product number of the current software of the component 12 from the component 12.

[0047] The update instruction sending unit 314 sends a software update instruction to the work machine 10 when the confirmation result received by the product number confirmation unit 313 from the work machine 10 matches the software product number received by the differential data receiving unit 311 from the software management server 50. The software update instruction includes the differential data received by the differential data receiving unit 311, a gateway script for execution by the gateway device 11, and a component script for execution by the component 12 to be updated. The gateway script describes the procedure by which the gateway 11 processes the differential data included in the update instruction. The component script describes the procedure for installing the updated program. Note that if the component 12 has a function for installing the updated program, the update instruction does not need to include a gateway script.

[0048] The table update unit 315 determines whether or not the software has been updated based on the confirmation result received by the product number confirmation unit 313 from the work machine 10 after the software update instruction. When the table update unit 315 determines that the software has been updated, it updates the component table 351. The table update unit 315 is an example of an update determination unit that determines whether or not the current software of the component 12 has been updated based on the product number acquired from the component 12.

[0049] Configuration of the software management server 50 FIG. 5 is a block diagram showing the configuration of the software management server 50 according to the first embodiment. The software management server 50 includes a processor 510, a main memory 530, a storage 550, and an interface 570. The processor 510 reads a program from the storage 550, loads the program in the main memory 530, and executes a predetermined process in accordance with the program. The interface 570 is connected to the component management server 30 so as to be able to communicate with the component management server 30.

[0050] The programs stored in storage 550 may be for implementing some of the functions to be performed by software management server 50. In another embodiment, software management server 50 may include a custom LSI such as a PLD in addition to or instead of the above configuration. In this case, some or all of the functions implemented by software management server 50 may be implemented by the integrated circuit.

[0051] Examples of storage 550 include a magnetic disk, a magneto-optical disk, an optical disk, a semiconductor memory, etc. Storage 550 may be an internal medium directly connected to a bus line, or an external medium connected to software management server 50 via interface 570 or a communication line. The program may be distributed to software management server 50 via a communication line, and processor 510 may execute the program. In at least one embodiment, storage 550 is a non-transitory tangible storage medium.

[0052] The processor 510 executes a program stored in the storage 550 to provide a software recording unit 511, a differential data generating unit 512, and a differential data transmitting unit 513. In the storage 550, a storage area for a software table 551 is secured.

[0053] The software table 551 stores a plurality of software programs with different product numbers that are applicable to the component 12 related to the product number, in association with the hardware product number of the component 12. That is, the software table 551 stores the hardware product number of the component, the software entity, and the software product number of the software in association with each other. FIG. 6 is an example of a software table according to the first embodiment. The software table 551 stores the hardware product number indicating the image display component, the software product number indicating the image display component application, and the software entity in association with each other. Note that the image display component application 1, the image display component application 2, and the image display component application 3 are examples of the software entity. Also, in the example shown in FIG. 6, the software table 551 stores the hardware product number indicating the machine guidance component, the software product number indicating the machine guidance component application, and the software entity in association with each other. Note that the machine guidance component application 1 and the machine guidance component application 2 ...

[0054] Software recording unit 511 accepts input of the software entity, the software product number, and the hardware product number of component 12 to which the software is applied from a server administrator or software developer, and records this in software table 551. The administrator or developer operates developer terminal 70 to transmit the software entity, the software product number, and the hardware product number of component 12 to which the software is applied to software management server 50.

[0055] The differential data generating unit 512 generates differential data between the software newly recorded in the software table 551 and software with a different product number that is applied to the hardware to which the software is applied.

[0056] The differential data transmission unit 513 transmits to the component management server 30 the differential data generated by the differential data generation unit 512 and the software product number to which the differential data is to be applied in association with each other.

[0057] How to update the software FIG. 7 is a sequence diagram showing a method for updating software of the component 12 in the software update system 1 according to the first embodiment. When the developer updates the software of component 12, he or she operates developer terminal 70 to transmit the software entity, the product number of the software, and the hardware product number of component 12 to which the software is to be applied in association with each other to software management server 50. Software recording unit 511 of software management server 50 associates the received software entity, software product number, and hardware product number and records them in software table 551 (step S1). Note that the software product number received by software recording unit 511 is the updated product number, which is the software product number after the update.

[0058] The differential data generation unit 512 acquires from the software table 551 the software entity and software product number associated with the hardware product number received in step S1 (step S2). The differential data generation unit 512 generates differential data for each software product number by calculating the difference between the software received in step S1 and each piece of software read in step S2 (step S3). If the software stored in the component 12 is always the latest version, differential data may be generated only for the latest software among the software read in step S2. The differential data transmission unit 513 transmits the differential data generated in step S3 to the component management server 30 in association with the hardware product number received in step S1, the update product number received in step S1, and the target product number, which is the software product number read in step S2 (step S4).

[0059] The difference data receiving unit 311 of the component management server 30 receives the difference data, software product number, and hardware product number from the software management server 50. The update target identifying unit 312 references the component table 351 and identifies the work machine 10 equipped with the component 12 related to the received hardware product number (step S5). Note that multiple work machines 10 equipped with the component 12 related to the hardware product number may be identified. Next, the product number confirmation unit 313 transmits a confirmation request for the software product number of the component to be updated to the gateway device 11 of the identified work machine 10 (step S6). That is, the confirmation request for the software product number includes the hardware product number of the component 12 to be updated.

[0060] The gateway device 11 receives a confirmation request for the software product number from the component management server 30 (step S6). The gateway device 11 executes a product number confirmation process for the component 12, and transmits the identified software product number to the component management server 30 (step S7). The software product number is written as a constant in the software entity, and is identified, for example, by executing a product number confirmation command possessed by the software. The product number confirmation process by the gateway device 11 will be described in detail later.

[0061] The product number confirmation unit 313 of the component management server 30 receives the software product number from the work machine 10 (step S7). If the software product number received in step S7 matches the target product number received in step S4, the update instruction transmission unit 314 transmits an instruction to update the software of the component to be updated to the gateway device 11 of that work machine 10 (step S8). The software update instruction includes the difference data received in step S4, a gateway script to be executed by the gateway device 11, and a component script to be executed by the component 12 to be updated. The gateway script includes the hardware product number of the component to which the difference data is to be applied.

[0062] The gateway device 11 receives a software update instruction from the component management server 30 (step S8). The gateway device 11 executes software update processing of the components 12 according to the gateway script included in the update instruction (step S9). The gateway script may describe that after the key of the work machine 10 is turned off, the individual components 12 are woken up by a function such as Wake-on-LAN to execute the software update processing. This is to prevent the components 12 from becoming inoperable due to an update while the work machine 10 is in operation. In addition, it may describe that after the key is turned on, the software update processing is executed when the operation of the work machine 10 is locked by a lock lever (a lever that blocks the flow paths of all hydraulic circuits for the work machine, swing, and travel) of the work machine 10, not shown. Details of the software update processing by the gateway device 11 will be described later.

[0063] A predetermined time after the differential data receiving unit 311 of the component management server 30 sends the update instruction in step S9, the part number confirmation unit 313 sends a confirmation request for the software part number of the component to be updated to the gateway device 11 of the work machine 10 that sent the update instruction (step S10). The predetermined time is sufficiently longer than the calculation time required for the process of applying the differential data to the software. Note that in another embodiment, the gateway device 11 of the work machine 10 may send a completion notification to the component management server 30 after completing the update, and the part number confirmation unit 313 may send a confirmation request for the software part number of the component to be updated to the gateway device 11 of the work machine 10 that sent the completion notification.

[0064] The gateway device 11 receives a confirmation request for the software product number from the component management server 30. The gateway device 11 executes a product number confirmation process for the component 12, and transmits the identified software product number to the component management server 30 (step S11). Since the software product number is written as a constant in the software entity, if the software update process in step S9 is normally completed, the software product number is also updated accordingly.

[0065] The product number confirmation unit 313 of the component management server 30 receives the software product number from the work machine 10 (step S11). If the software product number received in step S11 matches the updated product number received in step S4, the table update unit 315 updates the software product number of the component 12 stored in the component table 351 to the software product number received in step S11 (step S12). The sequence diagram shown in FIG. 7 shows an example of the process, and does not prevent the software from being updated by other processes. For example, the software update system 1 according to another embodiment may not perform the processes of steps S6, S7, S10, S11, and S12. In another embodiment, the software product number may be stored in a main memory or storage (not shown) of the component 12. In this case, the gateway device 11 may transmit a product number confirmation request for the component 12 to the component 12 in steps S7 and S11, and the component 12 may read out the software product number stored in the main memory or storage and transmit it to the gateway device 11.

[0066] <<Product number confirmation process of gateway device 11>> Here, the operation of the gateway device 11 in the software update process will be described. When the receiving unit 211 of the second board 200 of the gateway device 11 receives a confirmation request for the software product number from the component management server 30 in step S6 or step S10, the gateway device 11 executes product number confirmation process.

[0067] FIG. 8 is a flowchart showing the part number confirmation process of the gateway device 11 according to the first embodiment. The receiving unit 211 determines whether the component 12 to be confirmed, that is, the component 12 related to the hardware product number included in the confirmation request, is connected to the second board 200 (step S31). If the component 12 to be confirmed is connected to the second board 200 (step S31: YES), the accessing unit 214 acquires the software product number from the component 12 to be confirmed via the second network N2 (step S32).

[0068] On the other hand, if the component 12 to be checked is not connected to the second board 200 (step S31: NO), the output unit 212 outputs a request to check the software product number to the first board 100 (step S33). The input unit 111 of the first board 100 receives an input of a request to confirm the software product number from the second board 200 (step S34). Next, the access unit 112 acquires the software product number from the component 12 to be confirmed via the first network N1 (step S35). The output unit 114 outputs the read software product number to the second board 200 (step S36). The input unit 213 of the second board 200 receives an input of the software product number from the component 12 to be confirmed from the first board 100 (step S37).

[0069] The transmitting section 216 of the second board 200 transmits the software product number from the component 12 to be confirmed, identified in step S32 or step S37, to the component management server 30 (step S38). This enables the gateway device 11 to notify the software product number of the component 12 in response to a confirmation request from the component management server 30 . The flowchart shown in FIG. 8 shows an example of processing, and does not prevent the part number from being confirmed by other processing. Furthermore, gateway device 11 according to other embodiments may not need to perform part number confirmation processing. Furthermore, in other embodiments, the software part number may be stored in a main memory or storage (not shown) of component 12. In this case, second board 200 may transmit a part number confirmation request for component 12 to component 12 in steps S32 and S37, and component 12 may read out the software part number stored in the main memory or storage and transmit it to the second board.

[0070] <<Software Update Processing of Gateway Device 11>> When the receiving unit 211 of the second board 200 of the gateway device 11 receives a software update instruction from the component management server 30 in step S8, the gateway device 11 executes the gateway script included in the update instruction, thereby performing the software update process.

[0071] FIG. 9 is a flowchart showing the software update process of the gateway device 11 according to the first embodiment. In order to communicate with the component 12 that is the target of software update, i.e., the component 12 related to the hardware product number described in the gateway script, the receiving unit 211 refers to the connection information to determine whether the component 12 is connected to the second board 200 (step S61). If the component 12 to be checked is connected to the second board 200 (step S61: YES), the access unit 214 acquires the current software from the component 12 to be checked via the second network N2 (step S62).

[0072] On the other hand, if the component 12 to be updated is connected to the first board 100, or if the component 12 to be updated is the first board 100 (step S61: NO), the output unit 212 outputs a software acquisition instruction to the first board 100 (step S63). The input unit 111 of the first board 100 receives an input of a software acquisition instruction from the second board 200 (step S64). The update unit 113 judges whether the component 12 to be updated is the first board 100 itself (step S65). If the component 12 to be updated is the first board 100 itself (step S65: YES), the update unit 113 reads the main system software from the first storage 150 (step S66). On the other hand, if the component 12 to be updated is not the first board 100 itself (step S65: NO), the access unit 112 acquires the current software from the component 12 to be updated via the first network N1 (step S67). Note that the component 12 may transmit the information on the current software to the first board in multiple batches. This allows the component 12 with small computational resources that cannot transmit the current software to the first board in one transmission to transmit the information on the current software to the first board by transmitting the information in multiple batches. The output unit 114 outputs the software read out in step S66 or step S67 to the second substrate 200 (step S68). The input unit 213 of the second board 200 receives an input of the software of the component 12 to be updated from the first board 100 (step S69).

[0073] Then, the software generation unit 215 generates updated software by applying the difference data included in the update instruction received from the component management server 30 to the software acquired in step S62 or step S69 in accordance with the gateway script (step S70). The software generation unit 215 records the generated software in the standby software storage unit in association with the hardware product number of the component 12 (step S71).

[0074] In order to transmit the generated software to the component 12 to be updated, the software generation unit 215 refers to the connection information to determine whether the component 12 to be updated is connected to the second board 200 (step S72). The component 12 to be updated is an example of a first component. Examples of the component 12 to be updated include the component 12 connected to the first network N1, the component 12 connected to the second network N2, the first board 100, and the second board 200. The second board 200 including the software generation unit 215 is an example of a second component. Note that in other embodiments, a component other than the second board 200 may be the second component. That is, in other embodiments, a component other than the second board 200 may include the software generation unit 215.

[0075] If the component 12 to be updated is connected to the second board 200 (step S72: YES), the access unit 214 outputs the software generated in step S70 and the component script included in the update instruction to the component 12 to be updated via the second network N2. As a result, the component 12 rewrites the software it stores with the software generated in step S70 by executing the component script (step S73). In this way, for example, the component 12 to be updated in software is an example of a first component. Also, for example, the second board 200 is an example of a second component different from the component 12 to be updated.

[0076] On the other hand, if the component 12 to be updated is connected to the first board 100, or if the component 12 to be updated is the first board 100 (step S72: NO), the output unit 212 outputs a software update instruction to the first board 100 (step S74). The software update instruction includes the software generated in step S70 and the component script included in the update instruction. The input unit 111 of the first board 100 receives an input of a software update instruction from the second board 200 (step S75). The update unit 113 determines whether the component 12 to be updated is the first board 100 itself (step S76). If the component 12 to be updated is the first board 100 itself (step S76: YES), the update unit 113 rewrites the standby software stored in the first storage 150 to the software included in the update instruction (step S77). In this way, for example, the first board 100 to be updated in software is an example of a first component. Also, for example, the second board 200 different from the first component is an example of a second component. When the rewriting of the standby software is completed, the update unit 113 rewrites the main software stored in the first storage 150 to the software included in the update instruction (step S78).

[0077] On the other hand, if the component 12 to be updated is not the first board 100 itself (step S76: NO), the access unit 112 outputs the software and component script included in the update instruction to the component 12 to be updated via the first network N1. As a result, the component 12 rewrites the software it stores to the software included in the update instruction by executing the component script (step S79). In this way, for example, the component 12 to be updated in software is an example of a first component. Also, for example, the second board 200 different from the first component is an example of a second component. Also, the first board 100 connected to the component 12 to be updated in software is an example of another component. This enables the gateway device 11 to update the software of the component 12 based on the difference data. 9 shows an example of the process, and does not prevent software from being updated by other processes. For example, the gateway device 11 according to other embodiments may not perform the process of step S71 and the process of step S77. In other embodiments, the gateway device 11 may update any one of the first board 100, the component 12 connected to the first board 100, and the component 12 connected to the second board 200. In addition, if the component 12 to be updated stores a component script, the component script may not be included in the update instruction.

[0078] Actions and Effects Thus, according to the first embodiment, the gateway device 11 receives differential data for updating the component 12 of the work machine 10 via the external network, and applies the differential data to the current software of the component connected via the internal network. Then, the gateway device 11 outputs the generated software to the component 12. In this way, the gateway device 11 can update the software of the component 12 regardless of the size of the computational resources of the component 12. Furthermore, by updating the software using the differential data, the gateway device 11 can reduce the amount of communication on the external network.

[0079] Furthermore, the gateway device 11 according to the first embodiment generates software using the difference data in the second board 200 having a larger storage capacity than the first board 100. This allows the gateway device 11 according to the first embodiment to allocate more of the computational resources of the first board 100 to the control of the work machine 10. In addition, the second board 200 updates the software of the component 12 connected to the first board 100.

[0080] Furthermore, the gateway device 11 according to the first embodiment stores the generated software of the component 12 in the standby software storage unit 251. As a result, even if the software is damaged due to a power outage or the like during the software rewrite process in step S73 or step S79, the software can be generated using the software stored in the standby software storage unit 251. Furthermore, the first board 100 records the updated software in order as the standby software and the main software in the first storage 150. As a result, even if the recording of the standby software is completed and the main software is damaged due to an interruption in processing during the recording of the main software, the main software can be restored using the standby software for which recording has been completed. The restoration of the damaged software may be performed by an automatic operation by the gateway device 11, or may be performed manually by a serviceman or an operator.

[0081] Second embodiment The gateway device 11 according to the first embodiment generates software for all of the components 12 of the work machine 10 on a second board 200 mounted on the work machine 10. On the other hand, some of the components 12 have sufficient computational resources. In the second embodiment, some of the components 12 autonomously update their own software.

[0082] FIG. 10 is a schematic block diagram showing a configuration of a gateway device 11 according to the second embodiment. 10, the second board 200 further includes a determination unit 217 in addition to the configuration of the first embodiment.

[0083] The component storage unit 252 pre-stores the software product number of the component 12 having the function of applying differential data. The information stored in the component storage unit 252 is updated by a serviceman or the like when the component 12 is replaced. The determining unit 217 refers to the component storage unit 252 and determines whether the component 12 to be updated has a function for applying differential data.

[0084] When the gateway device 11 according to the second embodiment executes a software update process, first, the determination unit 217 refers to the component storage unit 252 to determine whether or not the component 12 to be updated has a function for applying differential data. If the component 12 to be updated has a function for applying differential data, the access unit 112 transfers the update instruction received from the component management server 30 to the component 12 to be updated. As a result, the component 12 to be updated updates its software using the differential data included in the update instruction. On the other hand, if the component 12 to be updated does not have the function of applying differential data, the gateway device 11 updates the software of the component 12 by executing the processes of steps S61 to S79 ​​according to the first embodiment.

[0085] Third embodiment The gateway device 11 according to the first embodiment includes a first board 100 and a second board 200 which are physically separate. In contrast, the gateway device 11 according to the third embodiment is mounted on a single board.

[0086] 11 is a schematic block diagram showing the configuration of the gateway device 11 according to the third embodiment. That is, the gateway device 11 according to the third embodiment includes a processor 210a, a main memory 230a, a storage 250a, and an interface 270a. The processor 210a, the main memory 230a, the storage 250a, and the interface 270a have computational resources equivalent to those of the second processor 210, the second main memory 230, the second storage 250, and the second interface 270 of the second board according to the first embodiment, respectively.

[0087] The gateway device 11 according to the third embodiment does not need to communicate with other boards, and therefore does not need to have functions corresponding to the output unit 212 and the input unit 213 of the gateway device 11 according to the first embodiment. In addition, the gateway device 11 according to the third embodiment does not need to perform the judgment of step S31, the processing of steps S33 to S37, the judgment of step S61, the processing of steps S63 to S69, the judgment of step S72, and the processing of steps S74 to S79 ​​according to the first embodiment.

[0088] Fourth embodiment In the gateway device 11 according to the first embodiment, the first board 100 and the second board 200 each include one processor. In contrast, in the gateway device 11 according to the fourth embodiment, one board includes two processors.

[0089] 12 is a schematic block diagram showing a configuration of a gateway device 11 according to the fourth embodiment. That is, the gateway device 11 according to the fourth embodiment includes a first processor 110, a first main memory 130, a first storage 150, a first interface 170, a second processor 210, a second main memory 230, a second storage 250, and a second interface 270 on one board. The first processor 110 and the second processor 210 may be realized by each core of a multi-core CPU. The first processor 110 and the second processor 210 may be two virtual processors virtualized from one physical processor by virtualization technology. The first main memory 130 and the second main memory 230, and the first storage 150 and the second storage 250 may also be realized by one main memory and storage. In this case, available storage areas of the main memory and storage are assigned to each processor in advance. The first interface 170 and the second interface 270 may be realized by one interface. In this case, the first network N1 and the second network N2 may be virtually separated by software.

[0090] The gateway device 11 according to the fourth embodiment can update the software of the component 12 by the same process as in the first embodiment.

[0091] Although one embodiment has been described in detail above with reference to the drawings, the specific configuration is not limited to the above, and various design modifications and the like are possible. For example, in other embodiments, the gateway device 11 may include three or more boards. Also, in other embodiments, the roles of the multiple boards included in the gateway device 11 may be different from those in the above-described embodiment. In another embodiment, the software management server 50 and the component management server 30 may not be separate entities, but may be realized by a single device.

[0092] In the second embodiment, the gateway device 11 determines whether or not the component 12 to be updated has a function for applying differential data, but this is not limited to the above. For example, if it is known that the component 12 connected to the second board 200 necessarily has a function for applying differential data, and the component 12 connected to the first board 100 necessarily does not have a function for applying differential data, the determination unit 217 may determine to which board the component 12 to be updated is connected, thereby determining whether or not to apply differential data. [Explanation of symbols]

[0093] 1...Software update system 10...Work machine 11...Gateway device 12...Component 30...Component management server 50...Software management server 100...First board 111...Input section 112...Access section 113...Update section 114...Output section 200...Second board 211...Receiving section 212...Output section 213...Input section 214...Access section 215...Software generation section 216...Transmitting section 311...Differential data receiving section 312...Update target identification section 313...Product number confirmation section 314...Update instruction transmitting section 315...Table updating section 511...Software recording section 512...Differential data generating section 513...Differential data transmitting section

Claims

1. 1. A software update system for updating software of a first component of a work machine, comprising: a receiving unit that receives, via an external network, difference data for updating the first component connected via an internal network of the work machine; a software acquisition unit that acquires, from the first component, first software that is stored and executed by the first component; a software generation unit that generates second software by applying the difference data to the first software; a software output unit that outputs the generated second software to the first component; A first processor and a second processor communicatively connected to each other, the first processor is connected to the first component for controlling the work machine; the second processor is connected to the first component for expanding a function of the work machine; The second processor functions as the software generation unit. Software update system for work machine components.

2. The software generation unit is mounted on a second component different from the first component.

2. The work machine component software update system of claim 1.

3. The software generation unit generates the second software related to the first component connected to the first processor.

2. The work machine component software update system of claim 1.

4. a product number acquiring unit that acquires a product number of the first software of the first component from the first component after outputting the generated second software to the first component; an update determination unit that determines whether or not the first software of the first component has been updated based on the acquired product number; A system for updating software for a component of a work machine according to any one of claims 1 to 3, comprising:

5. A software update method for updating software of a work machine control system comprising a first processor and a second processor communicatively connected to each other, the first processor being connected to a first component for controlling the work machine, and the second processor being connected to a first component for expanding a function of the work machine, the method comprising: receiving, via an external network, difference data for updating the first component connected via an internal network of the work machine; obtaining from the first component a first software item stored and executed by the first component; generating second software by applying the difference data to the first software by the second processor; outputting the generated second software to the first component; A method for updating software for a component of a work machine, comprising:

Citation Information

Patent Citations

  • Software update system, portable information terminal and server to be used for the same, software updating method, its computer program and recording medium with the program recorded thereon

    JP2003076554A

  • Work machine

    JP2014177816A

  • Terminal device and software rewrite program

    JP2017156937A

  • Information processing device, information processing system, and information processing method

    JP2018055615A

  • Program update system, control system, moving body, program update method and program

    JP2020144682A