Distributed system and data transmission method
The distributed system addresses the challenge of managing complex edge device controllers by cooperating edge devices with cloud servers to convert and aggregate diagnostic data, reducing communication volume and enhancing failure analysis efficiency.
Patent Information
- Application Number
- JP2020193217
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2020-11-20
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2040-11-20
AI Technical Summary
Existing systems struggle to efficiently manage and analyze complex internal states of controllers in edge devices, particularly in handling abnormal conditions, due to unique data formats and types for each component, leading to excessive data communication and limited ability to factor analyze or cooperate with external servers.
A distributed system where edge devices and diagnostic data cloud servers cooperate, converting and aggregating diagnostic data to reduce data communication, enabling factor analysis and identifying failure causes through rule-based or machine learning methods.
This approach reduces data communication volume and enables effective management of edge device internal states by generalizing data formats, allowing for efficient failure analysis and precise identification of abnormal conditions.
Smart Images

Figure 0007584284000001 
Figure 0007584284000002 
Figure 0007584284000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a distributed system and a data transmission method. [Background technology]
[0002] Patent Document 1 describes a configuration in which a monitoring device mounted on a vehicle has an interface for communicating with a diagnostic device, an ECU, a server device, etc., and when it receives a request from the diagnostic device, it selects a communication connection destination based on the vehicle state, acquires information from the connection destination, and transmits it to the diagnostic device. Furthermore, it describes that the server device searches a database in which a maintenance manual (inspection procedure) is stored to present the optimal maintenance procedure, and when this maintenance procedure is updated, the latest information is always presented to the repair person. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2005-300390 A Summary of the Invention [Problem to be solved by the invention]
[0004] The controllers in edge devices that control the moving mechanisms of moving objects, such as motors and engines, and the operating mechanisms of equipment, such as actuators, are expected to become more complex in order to realize moving objects that can operate automatically. In this case, the controllers in the edge devices can take on various types of internal states. Furthermore, the elimination of these internal states (especially abnormal states) is not necessarily limited to the types of internal states that can be restored within the edge device alone.
[0005] In the technology described in Patent Document 1, a monitoring device monitors the internal state (particularly abnormal states) of each component in the ECU, collects physical state data specific to each component, and transmits it to the outside of the edge device. Therefore, the type and format of data are unique for each component and hardware configuration mounted on the edge device, and the amount of data sent and received increases because physical data is communicated as is.
[0006] In addition, the server device that receives the data collected by the monitoring device only uses the received data to compare it with past cases, and is unable to respond to multiple types of phenomena, data, and abnormal conditions that occur in a complex manner. Furthermore, the server device does not perform cause analysis using the collected data, and is unable to handle the internal state of the controller in the edge device in cooperation with the edge device.
[0007] The present invention has been made in consideration of the above points, and aims to provide a technology that enables an edge device and a computer such as a cloud server to work together to handle the internal state of a controller in the edge device, and further to enable the generalization of data communication for such cooperation and a reduction in the amount of data communication. [Means for solving the problem]
[0008] The present application includes a number of means for solving at least part of the above problems, examples of which are as follows.
[0009] In order to solve the above problem, a distributed system according to one embodiment of the present invention is a distributed system comprising an edge device which is at least one of a mobile body and equipment capable of automatic operation, and a diagnostic data calculator, wherein the edge device has an intra-edge controller including at least a processing unit, and a system element which is monitored by the intra-edge controller, and the processing unit diagnoses whether or not there is an abnormality in the processing unit caused by an abnormality occurring in the system element, generates first diagnostic data indicating the presence or absence of an abnormality in the processing unit, converts the first diagnostic data into second diagnostic data indicating a type of abnormality in the processing unit, and transmits the second diagnostic data to the diagnostic data calculator. Effect of the Invention
[0010] According to the present invention, a technology can be provided in which an edge device and a computer such as a cloud server work together to handle the internal state of a controller in the edge device, and further, it is possible to generalize the data communication for this cooperation and reduce the amount of data communication.
[0011] Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiments. [Brief description of the drawings]
[0012] [Figure 1] FIG. 1 is a diagram showing an example of the configuration of a distributed system according to a first embodiment of the present invention. [Diagram 2] FIG. 2 is a diagram showing an application example of a distributed system. [Diagram 3] FIG. 3 is a diagram illustrating an example of a hardware configuration of a computer. [Figure 4] FIG. 4 is a diagram showing a method for classifying failure causes and diagnostic data in edge device components. [Diagram 5] FIG. 5 is a diagram showing an example of the configuration of a distributed system according to the second embodiment of the present invention. [Figure 6]FIG. 6 is a diagram showing an example of a data structure of the diagnostic data. [Figure 7] FIG. 7 is a diagram showing an example of a transmission and reception protocol for status data. [Figure 8] FIG. 8 is a diagram showing an example of the configuration of a distributed system according to the third embodiment of the present invention. [Figure 9] FIG. 9 is a diagram showing a display example of the information presentation screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0013] In the following embodiments, for convenience, when necessary, the description will be divided into multiple sections or embodiments, but unless otherwise expressly stated, they are not unrelated to each other and one is a partial or complete variation, detail, supplementary explanation, etc. of the other.
[0014] In addition, in the following embodiments, when referring to the number of elements (including the number, numerical value, amount, range, etc.), unless specifically stated or clearly limited to a specific number in principle, the number is not limited to that specific number and may be more than or less than the specific number.
[0015] Furthermore, it goes without saying that in the following embodiments, the components (including element steps, etc.) are not necessarily essential unless specifically stated or considered to be clearly essential in principle.
[0016] Similarly, in the following embodiments, when referring to the shapes, positional relationships, etc. of components, etc., unless otherwise specified or considered to be obviously different in principle, it includes those that are substantially similar or similar to the shapes, etc. The same applies to the above numerical values and ranges.
[0017] In addition, in all the drawings for explaining the embodiments, the same members are generally designated by the same reference numerals, and the repeated explanation thereof will be omitted. Hereinafter, each embodiment of the present invention will be explained with reference to the drawings.
[0018] <Configuration Example of Distributed System 101 According to the First Embodiment of the Present Invention> FIG. 1 shows an example of the configuration of a distributed system 101 according to a first embodiment of the present invention.
[0019] The distributed system 101 includes an edge device 20 and a diagnostic data cloud server (CS) 30. The edge device 20 is connected to the diagnostic data cloud server 30 via a network 1. The network 1 is a two-way communication network represented by, for example, a mobile phone communication network, the Internet (including Ethernet), and the like.
[0020] The edge device 20 is assumed to be, for example, an automatically operable mobile body (e.g., a vehicle, a drone, a robot) or equipment (e.g., a robot arm, a machine tool, a numerically controlled lathe, etc.). Here, the automatic operation includes automatic driving.
[0021] The edge device 20 includes an intra-edge controller 21, a processing unit 22, a system element 25, and a communication unit 26.
[0022] The intra-edge controller 21 has one or more processing units 22. The processing unit 22 has a control unit 23 that controls a system element 25, and a diagnostic unit 24 that generates diagnostic data representing the state of the processing unit 22.
[0023] The control unit 23 controls an actuator unit included in the system element 25 based on sensing information from a sensor unit included in the system element 25, for example.
[0024] The diagnostic unit 24 has a sequence storage memory 241 in which collection procedures (including collection cycles) are stored for collecting status data of the sensor unit, power supply unit, actuator unit, etc., which are components of the system element 25. The diagnostic unit 24 executes a data collection process P1, a unit diagnosis process P2, a data conversion process P3, and a data shaping process P4. The details of each process will be described later.
[0025] The system element 25 has a sensor unit, a power supply unit, an actuator unit, etc., which are components of the edge device 20, and a plurality of detection units that detect abnormalities in these components. The sensor unit, power supply unit, actuator unit, etc. output status data indicating their own status to the diagnosis unit 24. Each detection unit monitors the status of the corresponding sensor unit, power supply unit, actuator unit, etc., and outputs an abnormality signal S1 to the diagnosis unit 24 when an abnormality is detected.
[0026] The communication unit 26 transmits the shaped second diagnostic data input from the diagnosing unit 24 to the diagnostic data cloud server 30 via the network 1.
[0027] The diagnostic data cloud server 30 is composed of one or more computers existing on the network 1. In this embodiment, one or more locally existing computers may be used instead of a cloud server such as the diagnostic data cloud server 30. Conversely, a cloud server may be used instead of a local computer.
[0028] The diagnostic data cloud server 30 corresponds to a diagnostic data calculator of the present invention. The diagnostic data cloud server 30 has a configuration information database 31. The configuration information database 31 stores information representing components (sensor unit, power supply unit, actuator unit, etc.) of the edge device 20 in association with identification information unique to the edge device 20. The configuration information database 31 also stores second diagnostic data transmitted from the edge device 20.
[0029] The diagnostic data cloud server 30 executes a condition diagnosis process P11, a cause analysis process P12, and a part identification process P13. The details of each process will be described later.
[0030] <Overview of Distributed System 101> In the distributed system 101 configured as described above, the diagnostic unit 24 of the edge device 20 collects status data from each component included in the system element 25 according to the collection procedure stored in the sequence storage memory 241 as a data collection process P1.
[0031] Next, in unit diagnosis processing P2, the diagnosis section 24 monitors the operating state of the processing unit 22, diagnoses whether or not there is an abnormality, and generates first diagnosis data representing the diagnosis result.
[0032] Next, in data conversion process P3, if there is no abnormality in the processing unit 22, the diagnostic unit 24 converts the first diagnostic data into second diagnostic data including information indicating that there is no abnormality and part of the status data collected from the system element 25. If there is an abnormality in the processing unit 22, the diagnostic unit 24 classifies the abnormal status of the processing unit 22 into a plurality of status types and generates second diagnostic data representing the classification results. Note that the second diagnostic data includes unique identification information of the edge device 20.
[0033] Next, the diagnostic unit 24 performs data shaping processing P4, which is processing for encoding and shaping the data format suitable for transmitting the second diagnostic data to the diagnostic data cloud server 30. For example, when the network 1 is Ethernet, processing for storing the second diagnostic data in an Ethernet data container is performed. In the data shaping processing P4, it is possible to generate a format in the data container of each communication protocol, regardless of the protocol standard used for communication.
[0034] Next, the communication unit 26 transmits the formatted second diagnostic data to the diagnostic data cloud server 30 via the network 1 in accordance with a predetermined communication protocol.
[0035] In the data collection process P1, not only the status data is collected from each component of the system element 25, but also an abnormality signal S1 detected by a detector corresponding to each component is received, and the next unit diagnosis process P2 is started in response to the reception of the abnormality signal S1. Also, the abnormality signal S1 from the detector corresponding to each component may be added to the second diagnosis data as attribute information and transmitted to the diagnosis data cloud server 30.
[0036] The diagnostic data cloud server 30 receives the second diagnostic data transmitted from the edge device 20, and performs a status diagnosis process P11 to diagnose whether or not there is an abnormality in the edge device 20 based on the second diagnostic data transmitted from the edge device 20. If there is an abnormality, the second diagnostic data is handed over to a cause analysis process P12 and a part identification process P13.
[0037] Next, in the cause analysis process P12, the cause of the failure that caused the abnormality is analyzed based on the second diagnostic data. The cause of the failure includes a hardware failure of the components of the processing unit 22 and the system element 25 of the edge device 20, and an abnormality in the operation of software.
[0038] The method of analyzing the cause of the failure may be, for example, to make a rule of the correlation between the operating state of the processing unit 22 stored in the second diagnostic data and the cause of the failure, and to find the cause of the failure based on the rule. The method of implementing this rule may be to list conditions and results, or to use machine learning using a neural network. In other words, any method and format for associating the correlation between the operating state of the processing unit 22 and the cause of the failure in the edge device may be used.
[0039] Next, in the part identification process P13, the part where the failure has occurred is identified by obtaining the components of the system elements 25 of the edge device 20 from the configuration information database 31 based on the unique identification information of the edge device 20 included in the second diagnosis data. The part may be identified by using the correlation between the operating state of the processing unit 22 and the cause of the failure.
[0040] As described above, the distributed system 101 can provide a technique for handling an abnormal state in the edge device 20 by linking the edge device 20 with the diagnostic data cloud server 30 external to the edge device 20. In addition, the physical state data of the components of the edge device 20 (sensor unit, power supply unit, actuator unit, etc.) is not transmitted directly to the diagnostic data cloud server 30, but is aggregated into second diagnostic data representing the operating state of the processing unit 22 and transmitted, thereby reducing the amount of data communication required for linking the edge device 20 with the diagnostic data cloud server 30 and enabling generalization of diagnostic data independent of the configuration of the edge device 20.
[0041] <Application example of Distributed Systems 101> Next, FIG. 2 shows a data flow in a distributed system 1000 which is an application example of the distributed system 101 shown in FIG.
[0042] The distributed system 1000 is multi-tiered and includes one or more edge devices 20, one or more cloud servers (or computers) included in a data management layer 40, and one or more cloud servers (or computers) included in a data utilization layer 50.
[0043] 1 is divided into a diagnostic data management cloud server 301 and an analysis outsourcing cloud server 302. The diagnostic data management cloud server 301 is disposed in the data management layer 40, and the analysis outsourcing cloud server 302 is disposed in the data utilization layer 50.
[0044] The edge device 20 includes an intra-edge controller 21 , a movement / actuation mechanism 251 , and a sensor 252 .
[0045] The edge controller 21 is, for example, an ECU (Electronic Control Unit) or the like, and controls the moving / actuating mechanism 251. The moving / actuating mechanism 251 is at least one of a moving mechanism and an actuating mechanism. The moving mechanism is, for example, an engine or a motor in a moving body. The actuating mechanism is, for example, an actuator such as a motor or hydraulics in equipment. The moving / actuating mechanism 251 corresponds to an actuator section which is a component of the system element 25 (FIG. 1). The sensor 252 is, for example, a GPS (Global Positioning System) receiver or the like. The sensor 252 corresponds to a sensor section and its corresponding detection section included in the system element 25 (FIG. 1).
[0046] In relation to the moving / operating mechanism 251, "operation" means at least "performing a certain action, causing the equipment to change its state in accordance with the operation command (in accordance with JIS B 0132)."
[0047] In the following description, for the sake of simplicity, an example will be described in which the edge device 20 is a moving body and the movement / operation mechanism 251 is a moving mechanism. The intra-edge controller 21 is abbreviated as an ECTL (Edge Controller) 21.
[0048] The ECTL 21 is responsible for at least a part of the processing for realizing the automatic operation of the edge device 20. Therefore, the ECTL 21 is becoming more complex in terms of hardware or software. For example, an example of the complexity of the hardware may include a GPU (Graphics Processing Unit), an FPGA (Field-Programmable Gate Array), a processor dedicated to neural networks, or other hardware that accelerates machine learning in order to introduce machine learning processing or processing for recognizing and determining data input from various sensors and cameras in real time.
[0049] The data management layer 40 is a virtual layer or group introduced for the sake of simplicity. The cloud server (or computer) included in the data management layer 40 is mainly used to store data generated by the edge device 20.
[0050] The data management layer 40 may include cloud servers (or computers) for purposes other than those described above. Also, the data management layer 40 may omit cloud servers (or computers) for the purposes described above.
[0051] In the case of the same figure, the data management layer 40 includes an edge device manufacturer computer 41, an edge data distribution company cloud server (CS) 42, and a diagnostic data management cloud server (CS) 301.
[0052] The edge device manufacturer computer 41 is a computer owned by a company that designs or manufactures the edge device 20. The manufacturing company manages edge data related to the edge device 20 for the development and maintenance of its own products, and therefore is included in the data management layer 40 for convenience. The edge device manufacturer computer 41 transmits update data D23 of the edge data to the edge data distribution company cloud server 42.
[0053] The edge data distribution company cloud server 42 stores edge data related to the edge device 20, and transmits unprocessed or processed edge data D25 to the requesting cloud server in response to a request from another cloud server. The edge data D25 is assumed to be, for example, information about the components of the edge device 20.
[0054] Here, data processing refers to, for example, changing the data expression format, calculating differential values, calculating statistical values, encryption, decryption, compression, decompression, removal of unnecessary data, adding or removing redundant codes, data extraction, etc., but if the processing entity changes some or all of the data it received and then transmits it, this may be considered as processing.
[0055] The diagnostic data management cloud server 301 stores diagnostic data (hereinafter also referred to as edge controller diagnostic data or EXTL diagnostic data) D11 that indicates the internal state of EXTL 21 and is used to diagnose EXTL 21 from outside, and transmits unprocessed or processed diagnostic data D21, D27 in response to requests from other cloud servers. Note that the EXTL diagnostic data is an example of edge data.
[0056] From one perspective, a company that has a cloud server (or a computer) included in the data management layer 40 may be considered to be a company that designs or manufactures the edge device 20 or its parts, or a company that distributes edge data. From this perspective, the cloud servers of a communication company, a company that provides a car navigation program executed on a smartphone, and a manufacturer of a mobile device can be considered to be included in the data management layer 40.
[0057] The data utilization layer 50 is a virtual layer or group introduced for the sake of simplicity. The cloud servers (or computers) included in the data utilization layer 50 are used for purposes that are closer to providing services than the cloud servers included in the data management layer 40.
[0058] The services provided by the cloud servers included in the data utilization layer 50 may include edge device-related services that utilize the edge device 20, target entities related to the edge device 20, or target the edge device 20 itself.
[0059] Here, entities may be, for example, a group or group of people, animals, or equipment (a traffic light, a ship transporting the edge device 20, or an equipment outside the edge device 20 that supports the automatic operation of the edge device 20).
[0060] In the same figure, the data utilization layer 50 includes a dealer / repair company cloud server (CS) 51, an insurance company cloud server (CS) 52, a transportation company cloud server (CS) 53, a MaaS company cloud server (CS) 54, a rental company cloud server (CS) 55, and an analysis outsourcing cloud server (CS) 302.
[0061] The dealer / repair company cloud server 51 receives the edge data D25 or the post-analysis data D32 provided from the analysis outsourcing cloud server 302, in order to support the arrangement of repairs and maintenance of the edge device 20 and the work of the dealer or repair company that repairs the edge device 20, and generates information necessary for maintenance services (failure prevention, repairs, etc.) or repair services (accident response) and presents it to the user.
[0062] The insurance company cloud server 52 executes a part or all of the processes for determining insurance rates by referring to the edge data D25 or the post-analysis data D32 provided from the analysis outsourcing cloud server 302 at an insurance company that underwrites a predetermined risk related to the business of a company that performs a predetermined function using the edge device 20. Note that the risk underwritten by the insurance company may be a risk related to an entity that uses the edge device 20. For example, automobile insurance contracted by an individual is envisioned.
[0063] The transportation company cloud server 53 executes processing for providing transportation services based on the edge data D25 or the post-analysis data D32 provided from the analysis outsourcing cloud server 302 at a transportation company that directly uses the edge device 20 or uses the services of other transportation companies to operate a transportation business. Examples of the processing include vehicle dispatch planning for the edge device 20, fare calculation, and analysis processing for revising service specifications including fares.
[0064] The MaaS (Mobility as a Service) company cloud server 54 receives the edge data D25 or the post-analysis data D31 provided from the analysis outsourcing cloud server 302 and generates information required for a maintenance plan for the owned vehicles, in order to support the business of the MaaS company that directly uses the edge device 20 or provides a transportation means service using the services of other companies. The information is provided to employees of the MaaS company, etc.
[0065] The rental company cloud server 55, like the MaaS company cloud server 54, directly uses the edge device 20 or supports the business of a rental company that provides a means of transportation service using the services of other companies, and receives the edge data D25 or the post-analysis data D31 provided from the analysis outsourcing cloud server 302 and generates information required for a maintenance plan for the owned vehicles, etc. The information is provided to employees of the rental company, etc.
[0066] The analysis outsourcing cloud server 302 is a cloud server to which companies included in the data utilization layer 50 outsource the analysis of service-related analysis processes necessary for providing or improving services. In this embodiment, the analysis outsourcing cloud server 302 is responsible for outsourcing the analysis of diagnostic data (especially EXTL diagnostic data) D11, but it can also be responsible for outsourcing the analysis of edge device manufacturers and the like included in the data management layer 40. The service-related analysis process by the analysis outsourcing cloud server 302 corresponds to a factor analysis process related to the internal state of the edge device 20 or EXTL 21 in each solution described later.
[0067] The division into the data management layer 40 and the data utilization layer 50 is not limited to the example shown in the figure, and may not be exclusive. For example, the cloud server of a communications company corresponds to the edge data distribution company cloud server 42 included in the data management layer 40 from the perspective of the distribution of edge data described above, but it can also be considered to be included in the data utilization layer 50 from the perspective of providing "communication services" to the edge device 20.
[0068] Furthermore, from another perspective, a company that has a cloud server included in the data utilization layer 50 can be considered as a company that does not design or manufacture the edge device 20 or its parts.
[0069] <Example of the configuration of the computer 100 that constitutes the cloud server> Next, an example of a hardware configuration of the computer 100 constituting a cloud server such as the diagnostic data cloud server 30 is shown.
[0070] The computer 100 includes a processor 101, a memory 102, an external storage device 103, a voice output device 104, a biometric information input device 105, an input device 106, an output device 107, and a communication device 108, all of which are connected via a data bus 109.
[0071] The processor 101 includes a CPU, a GPU, an FPGA, etc., and controls the entire computer 100. The memory 102 is a main storage device such as a RAM (Random Access Memory), etc. The external storage device 103 is a non-volatile storage device capable of storing digital information, such as an HDD (Hard Disk Drive), an SSD (Solid State Drive), or a flash memory.
[0072] The audio output device 104 includes a speaker, etc. The biometric information input device 105 includes a camera, a gaze input device, a microphone, etc. The input device 106 includes a keyboard, a mouse, a touch panel, etc. The output device 107 includes a display, a printer, etc.
[0073] The communication device 108 is composed of a NIC (Network Interface Card) or the like. The communication device 108 communicates with other devices connected to the same network by at least one of wired communication and wireless communication. For this communication, packet communication according to TCP / IP (Transmission Control Protocol / Internet Protocol) is adopted, but the present invention is not limited to this, and communication according to other protocols such as UDP (User Datagram Protocol) may also be adopted.
[0074] The hardware configuration of the computer 100 is not limited to the above example, and some of the above components may be omitted or other components may be included. The computer 100 may be any of various information processing devices, such as a server computer, a personal computer, a notebook computer, a tablet computer, a smartphone, or a television device.
[0075] The computer 100 can store and externally load programs such as an OS (Operating System), middleware, and application programs, and can execute various types of processing by the processor 101 executing these programs.
[0076] <Failure Causes and Diagnostic Data Classification Method for Components of Edge Device 20> Next, FIG. 4 shows a method for classifying the causes of failures and diagnostic data in components of the edge device 20.
[0077] When a physical failure 201 occurs in a component of the edge device 20 (such as the sensor unit, power supply unit, or actuator unit of the system element 25 (FIG. 1)), the failure 201 manifests itself as an abnormality in the function of the edge device 20 (functional failure 202). The functional failure 202 is detected by a mechanism for detecting functional failures in the edge device 20. The detection result 203 is then converted into diagnostic data 204 that is aggregated by the state of the abnormality or the type of detection situation.
[0078] For example, when an "open" failure 201 occurs in which the bus that transmits the data output by the sensor 252 is disconnected, a "data communication abnormality" appears as a functional failure 202. Then, the processing unit 22 captures the phenomenon caused by the "data communication abnormality" as first diagnostic data representing a state called "readback detection" and converts the "readback detection" into diagnostic data (second diagnostic data) 204 representing a state called "data mismatch".
[0079] If the abnormal state of the components of the edge device 20 is considered as a physical phenomenon such as "open", "wire short", "power short", etc., the number of types will be very large, and various phenomena will be handled for each component of the system element 25, so it is necessary to handle various types of data. However, in this embodiment, by aggregating these as the state of the processing unit 22, it is possible to significantly reduce the types of data (second diagnostic data) to be transmitted to the diagnostic data cloud server 30a.
[0080] <Configuration Example of Distributed System 102 According to the Second Embodiment of the Present Invention> FIG. 5 shows an example of the configuration of a distributed system 102 according to the second embodiment of the present invention.
[0081] In addition to having the same functions as the distributed system 101 (FIG. 1), the distributed system 102 is configured to enable the diagnostic data cloud server 30 to request detailed status data from the edge device 20.
[0082] The distributed system 102 is different from the distributed system 101 in that a related information search process P14 is added to the processes executed by the diagnostic data cloud server 30, and an address storage memory 242 is provided in the diagnostic unit 24 of the edge device 20.
[0083] In the distributed system 102, when the diagnostic data cloud server 30 receives from the edge device 20 second diagnostic data that aggregates abnormal conditions in the processing unit 22 of the edge device 20, it diagnoses the presence or absence of an abnormality in the edge device 20 based on the second diagnostic data transmitted from the edge device 20 as a condition diagnosis process P11, and if an abnormality is found, it passes the second diagnostic data on to a cause analysis process P12 and a part identification process P13.
[0084] Next, in a cause analysis process P12, the cause of the failure that caused the abnormality is analyzed based on the second diagnostic data. Next, in a part identification process P13, the components of the system element 25 of the edge device 20 are obtained from the configuration information database 31 based on the unique identification information of the edge device 20 included in the second diagnostic data, and the part where the failure occurred is identified.
[0085] Then, a related information search process P14 is executed to improve the accuracy of identifying the abnormal part, or to identify in more detail the part where the abnormality has occurred in the system element 25. Specifically, a detailed information request command including information specifying the component identified in the part identification process P13 as a candidate for the abnormal part is issued and transmitted to the edge device 20 via the network 1.
[0086] The detailed information request command includes, for example, the access location address of a register in which the internal state of the image processing LSI is stored in order to identify whether an abnormality has occurred in the camera, image processing LSI (Large Scale Integration), or image memory, which are components of system element 25, and to identify the part at the component level.
[0087] In the edge device 20, the communication unit 26 receives the detailed information request command from the diagnostic data cloud server 30, and stores an access location address for reading out the register storing the state of the system element 25 stored in the detailed information request command in the address storage memory 242 of the diagnostic unit 24. In addition, the collection procedure is stored in the sequence storage memory 241. Here, the access location address is, for example, an access space address of various registers of the system element 25 managed by the processing unit 22.
[0088] After that, the diagnostic unit 24 reads out the status data stored in the access location address as a data collection process P1, generates first diagnostic data including the status data as a unit diagnosis process P2, converts the first diagnostic data into second diagnostic data as a data conversion process P3, and formats the diagnostic data of the machine 2 as a data formatting process P4, and the communication unit 26 transmits it to the diagnostic data cloud server 30.
[0089] According to the distributed system 102 described above, in addition to the same actions and effects as those of the distributed system 101, it becomes possible for the diagnostic data cloud server 30 to discriminate in a fine-grained manner which part of the system element 25 in the edge device 20 has an abnormality.
[0090] Next, FIG. 6 shows an example of a data structure of the second diagnostic data transmitted from the edge device 20 to the diagnostic data cloud server 30. In FIG.
[0091] The second diagnostic data converted in the data conversion process P3 has a diagnostic data type field, a domain name field, a processor I / F field, a data collection time field, and a status data field.
[0092] The diagnostic data type field stores the type of diagnostic data that summarizes and classifies abnormal conditions. Specifically, for example, the diagnostic data types stored are periodic observation data, bit error, data mismatch, test error, data number error, timeout, range violation, data order violation, element error, watchdog (WD) error, processing unit error notification, memory abnormality, processing unit exception error, etc.
[0093] The domain name field stores a domain name that indicates the type of input / output I / F in which an abnormality has been detected by the processing unit 22. Examples of domain names include digital I / O, memory bus, communication bus, and interrupt.
[0094] The processor I / F field stores the name of a signal in the processing unit 22 that detected the abnormality. Specifically, for example, a pin group, a pin number, etc. are stored as the signal name.
[0095] The data collection time field stores the time when status data is detected and collected. Specifically, for example, the time when an abnormality is detected, the time when diagnostic data is collected, etc. are stored.
[0096] The status data field stores status data during periodic status monitoring of the edge device 20. Specifically, for example, status data of the system elements 25, input / output data of the edge device 20 with the outside, etc. are stored.
[0097] The information stored in the domain name field, the processor I / F field, the data collection time field, and the status data field corresponds to the cause identification auxiliary information of the present invention, and is used in the cause analysis process P12.
[0098] The data structure of the second diagnostic data is not limited to the example shown in the figure, and may be changed according to the type of edge device 20 and the method of factor analysis.
[0099] Next, FIG. 7 shows an example of a transmission / reception protocol between the edge device 20 and the diagnostic data cloud server 30.
[0100] In the edge device 20, the diagnostic unit 24 periodically monitors the state of the system element 25 at a predetermined cycle and transmits second diagnostic data representing the state of the processing unit 22 caused by the state of the system element 25 to the diagnostic data cloud server 30.
[0101] Although the predetermined period is set in advance, it can be changed from the diagnostic data cloud server 30 in a third embodiment described later.
[0102] The diagnostic data cloud server 30 stores the received second diagnostic data in the configuration information database 31. The stored second diagnostic data is used as history information for analyzing the cause of the failure. Furthermore, if an abnormality occurs in the edge device 20, the diagnostic unit 24 transmits second diagnostic data indicating the occurrence of the abnormality to the diagnostic data cloud server 30. (Data collection process P1, unit diagnosis process P2, data conversion process P3, and data shaping process P4 in FIG. 1).
[0103] The diagnostic data cloud server 30 executes a cause analysis and a generation part identification process based on the second diagnostic data. When collecting detailed information, the diagnostic data cloud server 30 issues a detailed information request command and transmits it to the edge device 20 (related information search process P14 in FIG. 5). In accordance with the received detailed information request command, the edge device 20 reads out the status data, converts it into second diagnostic data, and transmits it to the diagnostic data cloud server 30.
[0104] Thereafter, the edge device 20 will periodically transmit the second diagnostic data to the diagnostic data cloud server 30 at a predetermined period.
[0105] 7, the edge device 20 can periodically transmit second diagnostic data indicating the state of the processing unit 22 to the diagnostic data cloud server 30 at a predetermined cycle. Furthermore, when an abnormality occurs, the edge device 20 can periodically transmit second diagnostic data indicating the occurrence of the abnormality to the diagnostic data cloud server 30 at a predetermined cycle.
[0106] <Configuration example of distributed system 103 according to the third embodiment of the present invention> FIG. 8 shows an example of the configuration of a distributed system 103 according to the third embodiment of the present invention.
[0107] In addition to having the same functions as the distributed system 101 (Figure 1), the distributed system 103 is configured to enable the period for periodically transmitting second diagnostic data from the edge device 20 to the diagnostic data cloud server 30 to be changed from the diagnostic data cloud server 30 side.
[0108] The distributed system 103 is obtained by providing a diagnostic result memory 32 in the diagnostic data cloud server 30, adding a diagnostic result statistical process P15, and providing an address storage memory 242 in the diagnostic unit 24 of the edge device 20, in comparison with the distributed system 101 (FIG. 1).
[0109] In the distributed system 103, when the diagnostic data cloud server 30 receives from the edge device 20 second diagnostic data that aggregates abnormal conditions in the processing unit 22 of the edge device 20, the diagnostic data cloud server 30 diagnoses the presence or absence of an abnormality in the edge device 20 based on the second diagnostic data transmitted from the edge device 20 as a condition diagnosis process P11, and if an abnormality is detected, the second diagnostic data is handed over to a cause analysis process P12 and a part identification process P13.
[0110] Next, in a cause analysis process P12, the cause of the failure that caused the abnormality is analyzed based on the second diagnostic data. Next, in a part identification process P13, based on the unique identification information of the edge device 20 included in the second diagnostic data, the components of the system element 25 of the edge device 20 are obtained from the configuration information database 31 to identify the part where the failure occurred, and the part where the failure occurred is stored in the diagnostic result memory 32 and handed over to the diagnostic result statistical process P15. Note that if there is no abnormality in the edge device 20, the regular second diagnostic data from the edge device 20 is handed over to the diagnostic result statistical process P15.
[0111] In the diagnostic result statistical processing P15, statistical processing is performed based on the failure location when an abnormality occurs in the edge device 20 and the second diagnostic data when there is no abnormality in the edge device 20, to derive candidates for components of the system element 25 that are at risk of occurrence of an abnormality, etc.
[0112] As the statistical processing, for example, a change in the error frequency of the data communication part in the system element 25 is monitored, the amount of change over time is calculated, and when the slope of the amount of change exceeds a predetermined threshold, a collection timing change command is sent to the edge device 20 to change the collection sequence, such as shortening the interval of periodic state data collection of the data communication part or reading state data (such as a status register) in the related system element 25. Based on the collection timing change command, the edge device 20 changes the collection procedure stored in the sequence storage memory 241 or changes the address of the address storage memory 242. As a result, the edge device 20 changes the cycle for periodically transmitting the second diagnostic data to the diagnostic data cloud server 30.
[0113] According to the distributed system 103 described above, in addition to the same actions and effects as those of the distributed system 101, it becomes possible to detect a symptom of a functional failure in the edge device 20 before the failure occurs.
[0114] <Display example of information presentation screen 600> 9 shows an example of the information presentation screen 600 displayed on, for example, the dealer / repair company cloud server 51 (FIG. 2) etc. The information presentation screen 600 is for requesting the cause analysis result of a failure that has occurred in the edge device 20 and detailed status data.
[0115] The information presentation screen 600 displays the result of the failure cause analysis and the state data collection result by the diagnostic data cloud server 30. Specifically, the result of diagnosis by the state diagnosis process P11 of the second diagnostic data periodically collected at a predetermined cycle is displayed in chronological order. If there is no abnormality in the edge device 20, information indicating that there is no abnormality and the periodically collected state data are displayed. If an abnormality occurs in the edge device 20, a message notifying the occurrence of the abnormality is displayed, and the processing results of the cause analysis process P12 and the part identification process P13 are displayed as related parts (candidates for abnormal parts). Furthermore, if a detailed information request command is issued by the related information search process P14, the type of the detailed information request command and address information are displayed, and the cause analysis result and the flow of the detailed information request processing are displayed in chronological order.
[0116] In the same figure, the information presentation screen 600 has a display area 601 that displays the name and model number of the edge device 20 that is the subject of the causal analysis, a display area 602 that displays the history of the entity used, and a display area 603 that displays the analysis results.
[0117] For example, when the edge device targeted for the causal analysis is an automobile, the vehicle type, model, configuration information ID, etc. are displayed in the display area 601. The ID of the entity that used the edge device 20 is displayed in a history format in the display area 602. Note that the display area 602 may also display other histories (for example, operation start date, maintenance history).
[0118] Display area 603 displays the processor unit (PU) status, the ID of the component in the abnormal state, the date and time when the abnormal state occurred, the status display of the processing unit, possible locations where the abnormality occurred, the command issue log, information indicating the cause of the abnormality, etc. However, it is not essential to display all of the above items. Here, the cause of the abnormality also includes information for determining whether the abnormality is a software abnormality or a hardware abnormality depending on the cause of the abnormality that has occurred. This is because the methods for resolving software abnormalities and hardware abnormalities often differ greatly.
[0119] By displaying such information presentation screen 600, the dealer or repair company can quickly grasp that the edge device 20 is in an abnormal state and needs repair. In addition, since the dealer or repair company does not need to use design data to identify parts that need to be replaced, a wider range of people can be engaged in repair work at the dealer or repair company.
[0120] The above-mentioned solutions for dealers and repair companies can also be applied to rental companies and MaaS companies. However, compared to dealers and repair companies, rental companies and MaaS companies do not perform detailed repairs on the edge device 20. On the other hand, in the case of services provided by rental companies and MaaS companies, the edge device 20 is operating normally, so that the appropriate fees can be obtained from the service users.
[0121] The information for shortening the recovery time from an abnormal state of the edge device 20 includes the location, the urgency, and the time required for response. The rental company or the MaaS company can select an appropriate recovery method by taking these factors into consideration. The recovery methods that become possible by providing the information presentation screen 600 are, for example, as follows.
[0122] Method 1: Priority is given to performing recovery work on edge devices 20 where an abnormal state has occurred that are farther away from the base location of the rental company or MaaS company. An example of a case in which this priority is reflected is the arrangement of an alternative edge device 20.
[0123] Method 2: Eliminate an abnormal state with a low urgency before it becomes an abnormal state with a high urgency. In the present embodiment, this is possible because the urgency response level can be determined in detail based on the internal state of the ECTL 21. Note that this urgency level may be determined by performing a correlation analysis of the ECTL diagnostic data as an analysis process in the analysis outsourcing cloud server 302, obtaining the correlation as post-analysis data, and taking this into consideration when setting the urgency level. For example, if an abnormal state is not fatal to the edge device 20 by itself, the priority level can be set to low, but if an abnormal state with a high correlation is of high urgency, the former abnormal state is set to medium or high, which is higher than low.
[0124] Method 3: Prioritize recovery operations based on urgency. In particular, when abnormal conditions with different urgency levels occur within the same edge device 20, resolving the abnormal condition with a higher urgency may also resolve the abnormal condition with a lower urgency.
[0125] Next, we will explain the application of this solution to an insurance company.
[0126] Even if the insurance premium is low, if the insurance payment conditions are strict, the contracting entity will not enter into a contract. On the other hand, if the insurance payment conditions are too relaxed, the insurance company's balance sheet will deteriorate too much and the service will not be able to continue. Therefore, by referring to the processed data provided by the analysis outsourcing cloud server 302, the insurance payment conditions can be set taking into account the frequency of occurrence of abnormal conditions inside the edge device 20.
[0127] For example, if it is found that the frequency of occurrence of an abnormal state inside the edge device 20 is high under certain conditions (e.g., type of edge device 20, usage environment, type of usage entity), it becomes possible to optimize the insurance premium by increasing the insurance premium for those conditions and decreasing the premium for conditions where the frequency of occurrence is low.
[0128] Furthermore, by monitoring the state of the edge device 20, it becomes possible to take action before a functional failure occurs, increasing the probability of preventing opportunity loss due to accidents or breakdowns. In that case, insurance payments can be reduced, and the insurance premium rate can be lowered. This advantage becomes even greater when the number of abnormalities related to the edge device 20 increases due to the spread of automated operation.
[0129] The technology according to the present invention is not limited to a distributed system and a data transmission method, but can be provided in various forms such as a computer and a computer-readable program.
[0130] The present invention is not limited to the above-described embodiment, and various modifications are possible. For example, the above-described embodiment has been described in detail to clearly explain the present invention, and is not necessarily limited to those having all of the configurations described. In addition, it is possible to replace a part of the configuration of one embodiment with a configuration of another embodiment, or to add a part of the configuration of another embodiment.
[0131] In addition, each of the above configurations, functions, processing units, processing means, etc. may be realized in hardware, for example, by designing a part or all of them in an integrated circuit. In addition, each of the above configurations, functions, etc. may be realized in software by a processor interpreting and executing a program that realizes each function. Information such as a program, table, file, etc. that realizes each function can be placed in a memory, a recording device such as a hard disk or SSD, or a recording medium such as an IC card, an SD card, or a DVD. In addition, the control lines and information lines are shown as being necessary for explanation, and not all control lines and information lines are necessarily shown in the product. In reality, it may be considered that almost all configurations are connected to each other. [Explanation of symbols]
[0132] 1 Network, 20 Edge device, 21 Edge controller, 22 Processing unit, 23 Control unit, 24 Diagnostic unit, 25 System element, 26 Communication unit, 30 Diagnostic data cloud server, 31 Configuration information database, 32 Diagnostic result memory, 40 Data management layer, 41 Edge device manufacturer computer, 42 Edge data distribution company cloud server, 50 Data utilization layer, 51 Dealer / repair company cloud server, 52 Insurance company cloud server, 53 Transport company cloud server, 54 MaaS company cloud server, 55 Rental company cloud server, 100, computer, 101, processor, 102, memory, 103, external storage device, 104, audio output device, 105, bioinformation input device, 106, input device, 107, output device, 108, communication device, 109, data bus, 241, sequence storage memory, 242, address storage memory, 251, movement and actuation mechanism, 252, sensor, 301, diagnostic data management cloud server, 302, analysis outsourcing cloud server, 600, information presentation screen, 601, display area, 602, display area, 603, display area, 1000, distributed system
Claims
1. A distributed system including an edge device that is at least one of a mobile object and a facility capable of automatic operation, and a diagnostic data calculator, The edge device includes: an edge controller including at least a processing unit; A system element to be monitored by the edge controller; The processing unit includes: Diagnosing whether or not there is an abnormality in the processing unit due to an abnormality occurring in the system element; generating first diagnostic data indicative of the presence or absence of an abnormality in the processing unit; classifying the first diagnostic data into a plurality of status types of abnormal states of the processing unit, and converting the first diagnostic data into second diagnostic data that is aggregated by type and does not depend on the configuration of the edge device; transmitting the second diagnostic data to the diagnostic data calculator; The diagnostic data calculator includes: Analyzing a cause of the abnormality in the processing unit based on the second diagnostic data. A distributed system comprising:
2. 2. The distributed system of claim 1, The diagnostic data calculator includes: A configuration information database in which information representing configurations included in the system elements of the edge device is stored, The configuration information database is referenced, and the configuration in which an abnormality has occurred in the system element of the edge device is identified based on the second diagnostic data transmitted from the edge device. A distributed system comprising:
3. 2. The distributed system of claim 1, The diagnostic data calculator includes: A configuration information database in which information representing configurations included in the system elements of the edge device is stored, referring to the configuration information database, and identifying a candidate for the configuration in which an abnormality has occurred in the system element of the edge device based on the second diagnostic data transmitted from the edge device; A detailed information request command is issued to request detailed information of the candidate and is transmitted to the edge device. A distributed system comprising:
4. 4. The distributed system of claim 3, The edge device includes: reading out the status data of the candidate from a register corresponding to address information included in the detailed information request command transmitted from the diagnostic data computer; The read status data is stored in the second diagnostic data and transmitted to the diagnostic data calculator. A distributed system comprising:
5. 2. The distributed system of claim 1, The second diagnostic data includes auxiliary information for identifying a cause of the malfunction, The diagnostic data calculator analyzes the cause of the abnormality of the processing unit based on the cause identification auxiliary information. A distributed system comprising:
6. 2. The distributed system of claim 1, The diagnostic data calculator transmits a collection timing change command to the edge device, the collection timing change command instructing the edge device to change the transmission cycle of the second diagnostic data. A distributed system comprising:
7. A data transmission method in a distributed system including an edge device having an edge controller that is at least one of an automatically operable mobile body and equipment and includes at least a processing unit, and a system element to be monitored by the edge controller, and a diagnostic data calculator, comprising: The processing unit Diagnosing whether or not there is an abnormality in the processing unit due to an abnormality occurring in the system element; generating first diagnostic data indicative of the presence or absence of an abnormality in the processing unit; classifying the first diagnostic data into a plurality of status types of abnormal states of the processing unit, and converting the first diagnostic data into second diagnostic data that is aggregated by type and does not depend on the configuration of the edge device; transmitting the second diagnostic data to the diagnostic data calculator; The diagnostic data calculator Analyzing a cause of the abnormality in the processing unit based on the second diagnostic data.
1. A data transmission method comprising the steps of:
Citation Information
Patent Citations
Auxiliary analysis method for causes of exceptions, server and intelligent equipment
CN104270275A
Method and device used for processing unstructured logs
CN107301120A
Exception detection method and system during application program running, equipment and storage medium
CN111209213A
Method and system for detecting exception state
CN111240882A
Data collection method and data collection device used for its execution
JP1994019750A
