PHM system design based on micro-service architecture
By adopting a microservice architecture-based design in the railway locomotive PHM system, the shortcomings of traditional single architecture in complex applications and high concurrent access are solved, and the system is lightweight, loose coupling, and high scalability is realized. It supports fully automatic independent deployment and thermal updates, meeting the needs of modern railway locomotive PHM systems.
Patent Information
- Application Number
- CN202411926044.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-25
- Publication Date
- 2025-05-06
AI Technical Summary
When traditional monolithic architectures face complex applications and high concurrent access, they have problems such as code redundancy, low development and deployment efficiency, database bottlenecks, and poor scalability, which are difficult to meet the needs of modern railway locomotive PHM systems.
The PHM system design based on the microservice architecture is divided into interface layer, business layer and data layer platforms. Through the design concept and technical means of microservices, the system can be achieved lightweight, loosely coupled and high scalability. The interface layer uses JavaScript, HTML, and CSS for page development. The business layer communicates with the data layer platform through json messages, and the data layer platform communicates with the external subsystem through data channels.
It realizes the lightweight, loose coupling, and high scalability of the system, supports fully automatic independent deployment and hot updates, and solves the problems of traditional systems in operation and maintenance, deployment, and updates. The addition of the PHM subsystem does not affect the operation of other systems, and can be independently deployed and operated.
Smart Images
Figure CN119938441A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of PHM system design based on microservice architecture, and in particular to a PHM system design based on microservice architecture. Background Art
[0002] Prognostics and Health Management (PHM) technology uses sensors to collect system data information, and uses information technology and artificial intelligence reasoning algorithms to evaluate, monitor and manage the health status of the system itself. By predicting system failures and combining existing resource information, it provides a series of maintenance and assurance suggestions or decisions. Therefore, PHM is a comprehensive technology that integrates fault detection, isolation, health assessment, health prediction and maintenance decision-making.
[0003] As the operation of railway locomotives develops towards high-speed, heavy-load, and long-distance rotation systems, higher requirements are placed on the quality status of locomotives, and the maintenance schedule of railway locomotives is also moving from planned preventive maintenance to condition-based maintenance. It is necessary to accelerate the integration of new-generation information technology and railways, and use big data and Internet of Things technologies to achieve the goals of scientific decision-making and resource optimization. Therefore, it is imperative to accelerate technological innovation and achieve breakthroughs and applications in fault prediction and health management (PHM) technology for locomotives and key components as soon as possible.
[0004] The emergence of the microservice architecture idea can be used to build complex applications. It has great advantages in agile development and deployment and complex enterprise-level application implementation, and can better solve the problems faced by traditional monolithic architecture. Its basic idea is to split the traditional monolithic application into a series of software service units that can be independently designed, developed, deployed and maintained according to business functions, and integrate these microservice units to build the system. Therefore, building a PHM system based on the idea of microservice architecture will be of great benefit to the future system upgrade, expansion, and operation and maintenance, laying a solid foundation for future development.
[0005] Microservices refer to small and autonomous services that are built around business functions and work together. These independent services together constitute the entire application system. The characteristics of microservices divided by business rather than technology make them highly cohesive, scalable and autonomous. The business layer includes easy upgrade and expansion. Microservices communicate with each other through network calls, thereby strengthening the isolation between services. The business layer includes avoiding tight coupling. Each service, as an independent entity, can be independently developed, managed and deployed, and each microservice supports development using different programming languages and can also use different data storage technologies independently. In addition, unified and centralized service management mechanisms should be avoided as much as possible. For a specific service, appropriate programming languages and tools should be selected according to the business context to build it.
[0006] Traditional application architecture such as Figure 1 As shown, it is usually divided into presentation layer, business logic layer and data layer. The business layer includes this type of architecture, which is simple to develop, has a transparent project structure, is easy to test, and has no distributed management overhead and call overhead, but the disadvantages are also obvious: (1) The business layer includes redundant business code, and there is duplicate code in multiple terminal applications; (2) The business layer, including system development, testing, and deployment, is becoming increasingly difficult and inefficient, and the project launch cycle is lengthening; (3) The business layer includes multiple applications that rely on the same database, and the database has reached a bottleneck and cannot be restructured or optimized; (4) The business layer includes a large number of users with high concurrent access, but the number is limited; (5) The business layer includes poor application scalability and changes that cannot meet demand.
[0007] Microservice architecture Figure 2 As shown in the figure, based on the actual business, complex applications are broken down into small-scale components. Although the overall function remains unchanged, each service can be managed independently after the breakdown. The business layer includes services that communicate internally through the business layer, including RPC or message-driven APIs, and lightweight information is exchanged externally through RESTful APIs. Microservices have clear context boundaries to strengthen the modularity of applications. Each service component can be developed synchronously without interference or conflict. The development speed is much faster than that of traditional application architectures, thereby achieving agile development iterations.
[0008] In general, the microservice architecture adopts a decentralized, bottom-up design, which is significantly different from the traditional application architecture. While the system business remains unchanged, the microservice architecture has risen to a new level in terms of system attributes such as scalability, maintainability, and reliability. Summary of the invention
[0009] In order to overcome the existing deficiencies, the present invention provides a PHM system design based on a microservice architecture.
[0010] The technical solution adopted by the present invention to solve its technical problems is: a PHM system design based on a microservice architecture, including an interface layer mainly responsible for data display and page presentation, a business layer as a data interface layer and a hub for data processing, a data layer platform for data processing and data services, and an external liaison subsystem; the interface layer is a group of pages contained in a basic website, the pages are rendered in JavaScript, HTML, and CSS, the interface of the business layer is called by using an Ajax request method and the data of the database is directly accessed, and communication with the business layer platform is achieved through the http communication protocol; the business layer achieves communication with the data layer platform through json messages; the data layer platform communicates bidirectionally with the external liaison subsystem through a data channel, and the business layer communicates bidirectionally with the external liaison subsystem through a data interface.
[0011] According to another embodiment of the present invention, further comprising: the page development of the interface layer is based on the design concept of microservices, using open source tools such as VS code, and the web pages are composed of HTML, CSS and JavaScript, wherein HTML is the structural layer, which builds the web page structure from a semantic perspective; CSS is the style layer, which modifies the page style from an aesthetic perspective; JavaScript is the behavioral layer, which describes the page behavior from an interactive perspective.
[0012] According to another embodiment of the present invention, further comprising: the HTML (Hyper Text Markup Language) is a hypertext markup language, including a series of tags, through which the document format on the network is unified, so that scattered network resources are connected into a logical whole.
[0013] According to another embodiment of the present invention, it further includes that the CSS is used to define the style of the web page, including the design and layout for different devices and screen sizes, and describes how elements on other media such as screens, paper, audio, etc. should be rendered. It is usually saved in an external .css file, and CSS3 is currently widely used.
[0014] According to another embodiment of the present invention, further including, the JavaScript is mainly used to add interactive behaviors to HTML pages, usually by being embedded in HTML to realize its own functions, including ECMAScript for describing the syntax and basic objects of the language, a document object model for describing methods and interfaces for processing web page content, and a browser object model for describing methods and interfaces for interacting with a browser.
[0015] According to another embodiment of the present invention, further comprising: the Ajax selects corresponding calling modes according to the interface mode of the business layer, namely get, post, put, and delete.
[0016] According to another embodiment of the present invention, it further includes that the business layer includes an nginx part, a zuul gateway, a Spring Cloud part, a middle part, a monitoring and protection part, and a governance and configuration part; the nginx part is responsible for load balancing when the system is called externally; the monitoring and protection monitoring includes link tracking, cluster monitoring, and degradation fault tolerance; the governance and configuration part includes service instructions and configuration management; the zuul gateway is responsible for network restriction settings; SpringCloud is responsible for interacting with the data layer; the middle part is the core part of the business layer, which is composed of components of different services, wherein each service is responsible for data processing of a PHM subsystem.
[0017] According to another embodiment of the present invention, further including, the data layer platform includes a data service layer, a monitoring and early warning layer, a task scheduling layer, a data computing layer, a data storage layer, a data acquisition layer, a data source layer and a data instruction layer; the data service layer is mainly responsible for interacting with the business logic layer; the monitoring and early warning layer monitors the operating status of the entire data platform to ensure the healthy operation of the platform; the task scheduling layer, data computing layer, data storage layer, data acquisition layer, data source layer and data instruction layer are responsible for receiving source data and processing data according to demand.
[0018] The beneficial effects of the present invention are: the architecture design and key technologies of the three important components of the system, namely the interface layer, the business layer and the data layer platform; the realization of the system's lightweight, loosely coupled and highly scalable development principles; the realization of the system's fully automatic independent deployment and hot update operation and maintenance; and the solution of the problems encountered by the system in operation, maintenance, deployment and update in future practical applications; the addition of a PHM subsystem does not affect the operation of other systems and can be independently deployed and operated. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] The present invention is further described below in conjunction with the accompanying drawings and embodiments.
[0020] Figure 1 It is a traditional application architecture diagram; Figure 2 It is a microservice architecture diagram; Figure 3 is a diagram of the PHM system architecture of the present invention; Figure 4 This is the interface layer architecture diagram; Figure 5 It is the business layer architecture diagram; Figure 6This is the data layer platform architecture diagram. DETAILED DESCRIPTION
[0021] like Figure 3 It is a structural diagram of the present invention, a PHM system design based on microservice architecture, including an interface layer mainly responsible for data display and page presentation, a business layer as a data interface layer and a hub for data processing, a data layer platform for data processing and data services, and an external liaison subsystem; the interface layer is a group of pages contained in a basic website, the pages are rendered by JavaScript, HTML, and CSS, the interface of the business layer is called by using Ajax request method and the data in the database is directly accessed, and communication with the business layer platform is achieved through the http communication protocol; the business layer communicates with the data layer platform through json messages; the data layer platform communicates bidirectionally with the external liaison subsystem through a data channel, and the business layer communicates bidirectionally with the external liaison subsystem through a data interface.
[0022] Specifically, strengthening the collection of operating data of in-service locomotives is a basic requirement for locomotive fault diagnosis and health prediction. In order to comprehensively improve the company's intelligent operation and maintenance and accelerate product design improvement, the company has established a locomotive PHM platform based on the industrial Internet technology architecture, which realizes the collection and analysis of the company's export locomotive operating data, monitoring of the status of the entire vehicle and major components, diagnosis and message push of events and faults, analysis of historical data, and management of mechanism models. The interface layer is mainly responsible for data display and page presentation; the business layer is the data interface layer and the hub of data processing; the data layer is mainly data processing and data services.
[0023] According to another embodiment of the present invention, further comprising: Figure 4 As shown, the page development of the interface layer is based on the design concept of microservices, using open source tools such as VS code. The web pages are composed of HTML, CSS and JavaScript, among which HTML is the structural layer, which builds the web page structure from a semantic perspective; CSS is the style layer, which modifies the page style from an aesthetic perspective; JavaScript is the behavioral layer, which describes the page behavior from an interactive perspective.
[0024] Specifically, during the development of the PHM system, different development languages and technologies are used for the three levels of the interface layer, business layer, and data layer platform. The interface layer uses three languages, JavaScript, HTML, and CSS. HTML, CSS, and JavaScript are called the three elements of the front end. A basic website contains many web pages, and each web page is composed of HTML, CSS, and JavaScript. The three complement each other. HTML is the structural layer, which builds the web page structure from a semantic perspective; CSS is the style layer, which modifies the page style from an aesthetic perspective; JavaScript is the behavioral layer, which describes the page behavior from an interactive perspective. The page development of the interface layer is based on the design concept of microservices. It uses open source tools such as VS code, customizes the development environment, applies agile development, and realizes rapid iteration of functions. The external display of the interface layer is the page. Each page is a small service. They do not affect each other when adding, updating, and deploying, and can be completely decoupled.
[0025] According to another embodiment of the present invention, further comprising: the HTML (Hyper Text Markup Language) is a hypertext markup language, including a series of tags, through which the document format on the network is unified, so that scattered network resources are connected into a logical whole.
[0026] Specifically, HTML text is a descriptive text composed of HTML commands, which are used to describe text, images, videos, tables, links, etc. HTML5 is currently widely used. CSS (Cascading Style Sheets) is a cascading style sheet, a standard language used to express the style of HTML files.
[0027] According to another embodiment of the present invention, it further includes that the CSS is used to define the style of the web page, including the design and layout for different devices and screen sizes, and describes how elements on other media such as screens, paper, audio, etc. should be rendered. It is usually saved in an external .css file, and CSS3 is currently widely used.
[0028] Specifically, CSS priority: inline styles have the highest priority, and internal styles and external styles follow the principle of proximity: inline styles, internal styles, external styles.
[0029] According to another embodiment of the present invention, further including, the JavaScript is mainly used to add interactive behaviors to HTML pages, usually by being embedded in HTML to realize its own functions, including ECMAScript for describing the syntax and basic objects of the language, a document object model for describing methods and interfaces for processing web page content, and a browser object model for describing methods and interfaces for interacting with a browser.
[0030] Specifically, ECMAScript describes the syntax and basic objects of the language, the syntax standards of JavaScript, such as ES5, ES6, ES7, etc.; the Document Object Model (DOM) describes the methods and interfaces for processing web page content, such as various HTML tags; the Browser Object Model (BOM) describes the methods and interfaces for interacting with the browser, such as browser forward, back, refresh, close, etc.
[0031] According to another embodiment of the present invention, further comprising: the Ajax selects corresponding calling modes according to the interface mode of the business layer, namely get, post, put, and delete.
[0032] According to another embodiment of the present invention, it further includes that the business layer includes an nginx part, a zuul gateway, a Spring Cloud part, a middle part, a monitoring and protection part, and a governance and configuration part; the nginx part is responsible for load balancing when the system is called externally; the monitoring and protection monitoring includes link tracking, cluster monitoring, and degradation fault tolerance; the governance and configuration part includes service instructions and configuration management; the zuul gateway is responsible for network restriction settings; SpringCloud is responsible for interacting with the data layer; the middle part is the core part of the business layer, which is composed of components of different services, wherein each service is responsible for data processing of a PHM subsystem.
[0033] Specifically, with the increase of page users and the complexity of PHM system functions, the system access volume has become larger and larger. At this time, it is no longer possible to support such a large number of user visits by optimizing the performance of a single server. Therefore, it is necessary to use multiple servers to process requests, use load balancing to balance traffic, and form a high-performance cluster. Load balancing is to distribute requests to multiple servers evenly according to a certain forwarding strategy through a load balancer. The back-end server can respond and process requests independently, thereby achieving the effect of distributing the load. In the PHM system, the business layer uses load balancing technology in the process of receiving client requests and sending requests to the data layer platform, and applies Nginx as a load balancing server. As an open source software, Nginx does not require additional purchase, has good system resource overhead and CPU utilization efficiency, and has powerful performance, which basically meets many business requirements of load balancing. Nginx supports 24-hour uninterrupted operation. The business layer does not need to be restarted even if it runs for several months, and can upgrade the software version without interrupting service. Spring Cloud is an ordered collection of a series of frameworks. It uses the development convenience of Spring Boot to cleverly simplify the development of distributed system infrastructure, such as service discovery registration, configuration center, message bus, load balancing, circuit breaker, data monitoring, etc., which can all be started and deployed with one click using the Spring Boot development style. SpringCloud does not reinvent the wheel. It simply combines the more mature and proven service frameworks developed by various companies, and re-encapsulates them in the Spring Boot style to shield the complex configuration and implementation principles, ultimately leaving developers with a set of easy-to-understand, easy-to-deploy and easy-to-maintain distributed system development toolkits. Using Spring Cloud to deploy a microservice framework can quickly get started, which is simple and safe, and can meet the basic requirements and functions of the framework. When the framework module cannot meet the needs, the framework can be easily expanded without affecting the normal use of the previous functions and framework. The interface design of the PHM business layer can realize control methods such as connection authentication, serialization / deserialization, encryption / decryption, asynchronous matching flow control, etc. The business layer can support message types such as XML, json, custom, and mixed messages, support TCP / IP, HTTP / HTTPS, WCF, WEB SERVICE and other communication protocols, and support synchronous short connection, synchronous long connection, asynchronous long connection and other communication modes. In actual development, json messages and http communication protocols are used to realize the communication between the business layer platform and the client and data layer platform. For the devices and systems accessing the system, the business layer includes strict access authentication to ensure the security of access.The system supports backup and redundancy measures for key equipment, key data and key program modules, and has strong fault tolerance and system recovery capabilities to ensure the long-term normal operation of the system. When designing the system, the expansion of system capacity and functions is fully considered to facilitate system expansion and smooth upgrade. The physical structure design of the PHM system is currently divided into three layers: the front-end area, the back-end area and the data area. Corresponding to the logical architecture diagram, the business layer is placed in the back-end area and the data layer is placed in the data area. Apply nginx load balancing. According to the logical architecture, the system is divided into different levels, so load balancing can be implemented according to different levels. According to the application scenarios of the PHM system, nginx is used for load balancing in the business logic layer. The business layer is developed in JAVA language. Based on the design concept of microservices and microcontainers, open source tools such as Idea, Maven, and Nexus are used to customize the development environment, apply agile development, and realize rapid iteration of functions. The services of the business layer are exposed to the outside in the form of interfaces, and the request message is in json format. This article develops each microservice as a subsystem, divides different microservices according to different subsystems, and can start and stop and hot update each subservice during deployment. Each microservice in the business layer will have a corresponding log record to record the behavior generated by the service. The performance of the microservice can be adjusted based on these behaviors, including fault detection and error troubleshooting. The log information is centrally displayed through the log management console, and the generated alarm information is sent to the system monitoring platform to notify the operation and maintenance management personnel.
[0034] According to another embodiment of the present invention, further including, the data layer platform includes a data service layer, a monitoring and early warning layer, a task scheduling layer, a data computing layer, a data storage layer, a data acquisition layer, a data source layer and a data instruction layer; the data service layer is mainly responsible for interacting with the business logic layer; the monitoring and early warning layer monitors the operating status of the entire data platform to ensure the healthy operation of the platform; the task scheduling layer, data computing layer, data storage layer, data acquisition layer, data source layer and data instruction layer are responsible for receiving source data and processing data according to demand.
[0035] Specifically, the data layer platform refers to a service platform that interacts with the database, which realizes the decoupling between the business logic layer and the data persistence layer. The data layer platform is mainly responsible for establishing a connection with the business logic layer, parsing the functional requests of the business layer, responding to the data requirements of the business layer, and ensuring that the requests meet the design requirements. The platform is mainly responsible for interacting with the database or encryption machine to complete the logic related to data processing. The composition of the data layer mainly includes two parts: the data platform and the data service. The data platform can be considered as the implementation of the microservice container; the data service is a service mounted on the data layer platform, which is a microservice that interacts with the database according to the needs to realize specific functions. The PHM data layer does not use the traditional model to establish entity classes and database table mappings to complete the interaction with the database. Instead, it is based on the concept of microservices and adopts the design of microservices and microcontainers to encapsulate low-granularity database operation behaviors and provide data operation services for the business layer. The data layer platform adopts the design concept of microservices and microcontainers, which has many advantages in design and use. First of all, unlike the traditional data persistence layer code as part of the business logic processing, the platform realizes the decoupling between the logic processing code and the database interaction code, so that the platform can not only be applied to the PHM system, but also be reused by other application systems, with strong scalability. At the same time, changes in the database access layer will not affect the business layer logic code, minimizing the risks of deployment and operation and maintenance. In addition, the data layer platform supports interaction with different types of databases. The database type can be selected according to actual conditions, and service development is more flexible. Each data layer service is a software service unit that can be independently designed, developed, deployed, and operated. These service units can be written in different programming languages and can also be developed and managed by different teams. They respond quickly to business needs and shorten the development cycle. The services are independent of each other and support independent deployment and hot updates at the service level. The key technologies and methods used in the design and time of the data platform layer are as follows: (1) Json message format. The request and response messages between the communication module of the data layer platform and the business logic layer use the Json message format. The Json format has a concise and clear hierarchical structure, is easy to read and write, and is also easy to machine parse and generate. It can effectively improve network transmission efficiency. The relevant open source libraries are relatively mature and stable, and have been used and improved many times in other projects, with high availability.
[0036] (2) Multi-threaded technology to process requests. After the data layer platform and the business logic layer are successfully connected, the platform will use multi-threaded technology to read and parse the message to achieve the purpose of parallel processing and forwarding requests, which can greatly improve the platform's processing capabilities. Combined with the message queue mechanism and thread lock to ensure thread safety, it can reasonably and efficiently utilize the server's multi-core advantages and server resources. At the same time, the business layer includes continuous improvement of multi-threaded related technologies during stress testing.
[0037] (3) Data computing capability. The data computing of the data layer platform includes two parts: offline computing and real-time computing. Offline computing is the processing of historical data, which can effectively analyze the changes in historical data and obtain valid information about the data. Real-time computing is to perform real-time computing on data, process the timeliness of data in a timely manner, and obtain the latest changes and information of the data.
[0038] (4) Data monitoring and early warning. The data layer platform uses the Grafana and Prometheus technical framework to build monitoring and early warning for the data layer platform. Prometheus obtains and processes data from various parts of the platform, and Grafana can realize interface display and observe the operating health of the entire platform in real time.
[0039] Specifically, the data platform is a container for operation services, and the operation services are microservices installed on the data platform. The data layer platform can establish different data service subsystems for each database. The programs of each data service subsystem are consistent, but the services are different. Each call completed by a service is a transaction of the database. Services are installed on the data layer platform in the form of components. Services are independent of each other, and service updates do not affect the normal operation of the data layer platform and other services. Figure 6The data layer platform architecture. The data platform is mainly responsible for establishing a connection with the business logic layer, parsing request messages, receiving requests and loading encapsulated data services for specific logic processing. Among them, the data service layer is mainly responsible for interacting with the business logic layer, including establishing a connection with the business logic layer, receiving request messages, and sending back response messages; the monitoring and early warning layer mainly monitors the operating status of the entire data platform to ensure the healthy operation of the platform; the other five layers are mainly responsible for receiving source data and processing data according to demand. Data service is a microservice mounted on the data platform, a service that interacts with the database or encryption machine. The business layer includes the data layer platform encapsulating fine-grained data operation services, which are provided to the business logic layer for calling, thereby realizing the complete system business logic processing operation. Different from the traditional data persistence layer code as part of the business logic processing, the data service exists independently, and the addition and update of the service will not affect the business layer logic code. The data service is developed as a component service, with the base class as the container type. When starting the platform, all data services are injected into the container. When calling, the corresponding memory address is retrieved according to the service number and called. The underlying layer of data service is developed using embedded SQL to interact with different types of databases. The advantage of embedded SQL is that SQL related information can be sent to the database server during the compilation phase. There is no need to regenerate the execution plan when the SQL statement is actually executed, which can greatly improve the execution speed. The business layer includes the business logic layer and the data layer platform to negotiate and stipulate the data service number as the identification standard for requests and responses of both parties, so as to enable normal communication between the two platforms. Therefore, each data service has its own unique identifier. When mounted as a microservice in the data layer platform container, the number of platform types and the specific services mounted inside can be divided according to demand.
[0040] The above description is only illustrative rather than restrictive of the present invention. Those skilled in the art will understand that many modifications, changes or equivalents may be made without departing from the spirit and scope defined by the appended claims, but all will fall within the scope of protection of the present invention.
Claims
1. A PHM system design based on microservice architecture, characterized by: It includes an interface layer mainly responsible for data display and page presentation, a business layer as a data interface layer and a hub for data processing, a data layer platform for data processing and data services, and an external liaison subsystem; the interface layer is a group of pages contained in a basic website, the pages are rendered using JavaScript, HTML, and CSS, the interface of the business layer is called using Ajax requests and the data in the database is directly accessed, and communication with the business layer platform is achieved through the http communication protocol; the business layer communicates with the data layer platform through json messages; the data layer platform communicates bidirectionally with the external liaison subsystem through a data channel, and the business layer communicates bidirectionally with the external liaison subsystem through a data interface.
2. The PHM system design based on microservice architecture according to claim 1 is characterized in that: The page development of the interface layer is based on the design concept of microservices, using open source tools such as VS code. The web pages are composed of HTML, CSS and JavaScript, among which HTML is the structural layer, which builds the web page structure from a semantic perspective; CSS is the style layer, which modifies the page style from an aesthetic perspective; JavaScript is the behavioral layer, which describes the page behavior from an interactive perspective.
3. The PHM system design based on microservice architecture according to claim 2 is characterized in that: The HTML (HyperText Markup Language) is a hypertext markup language, including a series of tags, through which the document format on the network is unified, so that scattered network resources are connected into a logical whole.
4. The PHM system design based on microservice architecture according to claim 2 is characterized in that: The CSS is used to define the style of a web page, including the design and layout for different devices and screen sizes. It describes how elements on screens, paper, audio, and other media should be rendered. It is usually saved in an external .css file. Currently, CSS3 is widely used.
5. The PHM system design based on microservice architecture according to claim 2 is characterized in that: The JavaScript is mainly used to add interactive behaviors to HTML pages, usually by being embedded in HTML to implement its own functions. It includes ECMAScript, which describes the syntax and basic objects of the language, the document object model, which describes the methods and interfaces for processing web page content, and the browser object model, which describes the methods and interfaces for interacting with browsers.
6. The PHM system design based on microservice architecture according to claim 1 is characterized in that: The Ajax uses the corresponding calling methods according to the interface mode of the business layer, which are get, post, put, and delete.
7. The PHM system design based on microservice architecture according to claim 1 is characterized in that: The business layer includes nginx part, zuul gateway, Spring Cloud part, middle part, monitoring and protection part, and governance and configuration part; the nginx part is responsible for load balancing when external calls are made to the system; Monitoring and protection monitoring includes link tracking, cluster monitoring, and downgrade fault tolerance; governance and configuration include service instructions and configuration management; Zuul gateway is responsible for network restriction settings; Spring Cloud is responsible for interacting with the data layer; The middle part is the core of the business layer, which consists of different service components, where each service is responsible for data processing of a PHM subsystem.
8. The PHM system design based on microservice architecture according to claim 1 is characterized in that: The data layer platform includes a data service layer, a monitoring and early warning layer, a task scheduling layer, a data computing layer, a data storage layer, a data acquisition layer, a data source layer and a data instruction layer; the data service layer is mainly responsible for interacting with the business logic layer; the monitoring and early warning layer monitors the operating status of the entire data platform to ensure the healthy operation of the platform; the task scheduling layer, the data computing layer, the data storage layer, the data acquisition layer, the data source layer and the data instruction layer are responsible for receiving the source data and processing the data according to demand.