Multi-source satellite remote sensing data processing and analyzing system for marine meteorological environment

Abstract

The invention discloses a multi-source satellite remote sensing data processing and analyzing system for a marine meteorological environment, which belongs to the technical field of satellite remote sensing, and comprises a basic environment layer for defining a basic software environment on which software design, development and operation depend; the platform framework layer is used for providing support of all framework layers for the whole software; according to the method, a satellite marine meteorology multi-source observation data acquisition and product display system is built, various marine meteorology related satellite data and products are acquired in real time, and time-space matching and lattice processing of multi-source satellite similar data products and data product retrieval and display are carried out on the basis; the integrated service of real-time collection, matching and display of data is realized, comprehensive support of multi-source satellite remote sensing data on marine weather is formed, the defect of comprehensive guarantee of meteorological satellite engineering on marine meteorology is made up, and real-time acquisition of the multi-source satellite remote sensing data, generation of lattice data products and visual display can be realized.

Description

Technical Field

[0001] The invention belongs to the technical field of satellite remote sensing, and in particular relates to a multi-source satellite remote sensing data processing and analysis system for marine meteorological environment. Background Art

[0002] The marine meteorological environment includes many factors, such as sea surface temperature, wave height, wind speed and direction, sea fog, sea ice, etc. Changes in sea surface temperature not only affect the marine ecosystem, but also have a profound impact on global climate patterns. When studying the marine meteorological environment, it is necessary to use advanced satellite remote sensing technology, buoy observation systems, and numerical simulations to obtain accurate and comprehensive data.

[0003] At present, there is a lack of corresponding processing and analysis systems to ensure the development of ocean navigation, marine economic activities, and marine engineering construction, to timely understand the relevant information of marine meteorology and ocean conditions, to collect, process and monitor marine meteorology and ocean information in real time, and to realize the release and display of three-dimensional geographic information platforms, laying the foundation for further deepening satellite remote sensing services and enhancing marine meteorological monitoring capabilities. Summary of the invention

[0004] The purpose of the present invention is to solve the above-mentioned problems and to propose a multi-source satellite remote sensing data processing and analysis system for marine meteorological environment.

[0005] In order to achieve the above object, the present invention adopts the following technical scheme: a multi-source satellite remote sensing data processing and analysis system for marine meteorological environment, comprising: The basic environment layer defines the basic software environment on which software design, development, and operation depend; The platform framework layer provides all framework-level support for the entire software. All business application logic components of the software will be designed and developed based on the basic framework provided by the platform framework layer. The application integration and call layer implements the access and interaction between business application components and the platform framework layer.

[0006] As a further description of the above technical solution: The platform framework layer includes a transaction processing unit, a log control unit, a data access unit, a process control unit, a plug-in framework unit, a state monitoring unit, a business information configuration unit and a task scheduling unit. The transaction processing unit solves the problem of consistency in all processes related to data storage and acquisition in the system. The log control unit solves the problem of system log collection, configuration and analysis. The data access unit solves the problem of data security access in the system. The process control unit solves the problem of online configuration of the data processing process in the system. The plug-in framework unit proposes a set of interface specifications, and through the support of the underlying plug-in engine, provides a framework foundation for the dynamic scalability of the system. The state monitoring unit solves the system security problem in the system, dynamically detects the relevant state of the system during operation, and processes the corresponding events according to pre-defined strategies. The business information configuration unit solves the problem of immediate effectiveness of a series of configuration files such as policies and business parameters in the system. The task scheduling unit solves the problem of job scheduling based on time, event, priority and other strategies in the system, so that the application system can automatically run and complete related jobs according to the corresponding strategies.

[0007] As a further description of the above technical solution: The transaction processing unit consists of application components, resource managers, and transaction managers. Application components are clients of transactional resources, and they are programs used by application developers to implement transactions; the resource manager is a component that manages a persistent and stable data storage system, and participates in the two-phase commit and recovery protocol with the transaction manager; the transaction manager is the core component of a transaction processing environment.

[0008] As a further description of the above technical solution: The log control unit is composed of a log information collection platform, a log collection scheduling, a log statistical analysis, and a log interface.

[0009] As a further description of the above technical solution: The data access unit is composed of a unified data access interface, a database adapter, and a file adapter. The unified data access interface carries all application requests for data information; the database adapter carries all specific operations related to the database; and the file adapter carries all specific operations related to the file system.

[0010] As a further description of the above technical solution: The process control unit is composed of a process configurator, a node configurator, a process scheduling controller, a node activator and a process template. The process configurator carries the process ID number of all data; the node configurator carries the specific operation items of all processes; the node activator is responsible for activating the nodes in the process template; the process scheduling controller is the core of the process configuration and scheduling technology; the process template defines the skeleton of the process.

[0011] As a further description of the above technical solution: The plug-in framework unit consists of a plug-in application framework, a plug-in resource library, a public function library, and plug-in standard specifications. The plug-in application framework is responsible for the overall operation of the application; the plug-in resource library centrally manages all plug-ins contained in the application; the public function library is a set of functions or classes that can be called by both the application framework and plug-ins; the plug-in standard specifications provide support for the plug-in software framework from the standard specification level, including plug-in interface standards, plug-in design and development standards, plug-in calling standards, etc., providing guidance for all aspects involved in the plug-in framework.

[0012] As a further description of the above technical solution: The application integration and calling layer includes an access control unit, a component calling unit and a data communication to implement a business application component unit. The access control unit, the component calling unit and the data communication are used to implement the safe and reliable calling of the platform framework component by the business application component unit. The interface and function expansion of the platform framework layer for the actual business logic are implemented through component registration and publishing.

[0013] In summary, due to the adoption of the above technical solution, the beneficial effects of the present invention are: In the present invention, by constructing a satellite marine meteorological multi-source observation data acquisition and product display system, a variety of marine meteorological related satellite data and products are acquired in real time. On this basis, time-space matching and grid processing, data product retrieval and display of multi-source satellite similar data products are carried out to realize the integrated service of real-time data collection, matching and display, form a comprehensive support for marine weather by multi-source satellite remote sensing data, make up for the insufficiency of comprehensive marine meteorological support by meteorological satellite projects, and realize real-time acquisition of multi-source satellite remote sensing data, time-space matching, generation of gridded data products, and visual display. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 The block diagram is a multi-source satellite remote sensing data processing and analysis system for marine meteorological environment.

[0015] Figure 2 The present invention is a block diagram of a transaction processing unit in a multi-source satellite remote sensing data processing and analysis system for marine meteorological environment.

[0016] Figure 3 The present invention is a block diagram of a log control unit in a multi-source satellite remote sensing data processing and analysis system for marine meteorological environment.

[0017] Figure 4 The present invention is a block diagram of a data access unit in a multi-source satellite remote sensing data processing and analysis system for marine meteorological environment.

[0018] Figure 5 The present invention is a block diagram of a process control unit in a multi-source satellite remote sensing data processing and analysis system for marine meteorological environment.

[0019] Figure 6 The present invention is a block diagram of a plug-in framework unit in a multi-source satellite remote sensing data processing and analysis system for marine meteorological environment.

[0020] Figure 7 The present invention is a block diagram of a state monitoring unit in a multi-source satellite remote sensing data processing and analysis system for marine meteorological environment.

[0021] Figure 8 The present invention is a block diagram of a business information configuration unit in a multi-source satellite remote sensing data processing and analysis system for marine meteorological environment. DETAILED DESCRIPTION

[0022] In order to make the purpose, technical solution and advantages of the embodiment of the present invention clearer, the technical solution in the embodiment of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiment of the present invention. Obviously, the described embodiment is a part of the embodiment of the present invention, rather than all the embodiments. The components of the embodiment of the present invention described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiment of the present invention provided in the drawings is not intended to limit the scope of the claimed invention, but only represents the selected embodiment of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention. It should be noted that similar numbers and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings. In the description of the embodiments of the present invention, it should be noted that the terms "upper", "inside", etc. indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings, or the orientation or positional relationship in which the invented product is usually placed when in use, which is only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation of the present invention. In the description of the present invention, it should also be noted that, unless otherwise clearly specified and limited, the terms "set", "install", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be directly connected, or indirectly connected through an intermediate medium, or it can be the internal connection of two elements. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0023] See also Figure 1-8 The present invention provides a technical solution: a multi-source satellite remote sensing data processing and analysis system for marine meteorological environment, comprising: The basic environment layer defines the basic software environment that software design, development, and operation rely on. The software will use a data access and storage management mechanism that combines a database with a shared file system. It will implement storage and shared access to all relational data through a relational database, and shared access to all file data through a shared file system. The entire software will be compiled and deployed on the server side based on the Linux operating system. The platform framework layer provides all framework-level support for the entire software. All business application logic components of the software will be designed and developed based on the basic framework provided by the platform framework layer. The application integration and call layer implements the access and interaction between business application components and the platform framework layer; The platform framework layer includes a transaction processing unit, a log control unit, a data access unit, a process control unit, a plug-in framework unit, a status monitoring unit, a business information configuration unit and a task scheduling unit, thereby effectively ensuring the reliability, stability and efficient development of the entire software. The transaction processing unit solves the problem of maintaining consistency in all processes related to data storage and acquisition in the system. The log control unit solves the problem of system log collection, configuration and analysis. The data access unit solves the problem of data security access in the system, provides convenient data access and management interfaces for applications, and meets the security and effectiveness requirements of interactions between applications and database systems. The process control unit solves the problem of online configuration of data processing processes in the system, realizes the configurability of processing methods, improves the flexibility of processing methods and the flexibility of business process control, and meets the configurability and scalability requirements of processing methods. The plug-in framework unit proposes a set of interface specifications, and through the support of the underlying plug-in engine, provides a framework foundation for the dynamic scalability of the system to realize the update module. Dynamic identification, automatic loading and immediate effectiveness at runtime meet the flexibility and scalability requirements of the system during operation. The state monitoring unit solves the system security problem in the system, dynamically detects the relevant state of the system during operation, and processes the corresponding events according to pre-defined strategies to ensure the safe and stable operation of the system and meet the security and reliability requirements of the system. The business information configuration unit solves the problem of immediate effectiveness of a series of configuration files such as policies and business parameters in the system, so that the configuration files have the flexibility and configurability to be modified, meeting the scalability and maintainability requirements of policies and business parameters. The task scheduling unit solves the problem of job scheduling based on time, event, priority and other strategies in the system, so that the application system can automatically run and complete related jobs according to the corresponding strategies, and realize the automatic operation mode of the system; parallel computing will use the relevant technologies of MPI / OpenMP in software design and development to realize the parallel processing of the system and abstract and extract the public parallel processing interface for the parallel processing of application business logic; The transaction processing unit consists of application components, resource managers, and transaction managers. Application components are clients of transactional resources. They are programs used by application developers to implement transactions. With the help of the transaction manager, these components establish global transactions, propagate transaction contexts if necessary, and operate transactional resources within the scope of these transactions. These components are not responsible for implementing ACID protection of transactions. Attributes, but as part of the application logic, these components usually make the decision whether to commit or rollback a transaction; a resource manager is a component that manages a persistent and stable data storage system and participates in the two-phase commit and recovery protocol with the transaction manager. A resource manager is typically a driver or a wrapper on a stable storage system, with interfaces for operating data, and in order to participate in the two-phase commit and recovery protocol coordinated by the transaction server, this component can also, directly or indirectly, register resources with the transaction manager so that the transaction manager can track all resources participating in the transaction. This process is called resource enlistment. In order to implement the two-phase commit and recovery protocol, the resource manager should implement additional mechanisms that may be used by recovery; the transaction manager is the core component of a transaction processing environment. Its main responsibilities are to establish transactions when required by application components, allow resource enlistment and delisting, and direct the two-phase commit or recovery protocol with resource managers. A typical transactional application starts a transaction by issuing a request to the transaction manager to initiate a transaction. In response, the transaction manager starts a transaction and associates it with a calling thread. The transaction manager also establishes a transaction context. All application components and / or threads in a transaction share the transaction context. The thread that initially issues a request to start the transaction, or any other thread if permitted by the transaction manager, can eventually terminate the transaction by issuing a commit or rollback request. Before a transaction is terminated, multiple components and / or threads can complete transactional operations on multiple data known to the transaction manager. If permitted by the transaction manager, a transaction can be suspended or continued before the transaction is finally completed. Once the application issues a commit request, the transaction manager prepares all resources for a commit operation and issues a commit or rollback request to all resources based on whether all resources are ready for commit. The log control unit is composed of a log information collection platform, log collection scheduling, log statistical analysis, and a log interface. The collection and processing of log information is the core of log control. Due to the diversity of the information to be collected, such as business data, performance data, configuration data, etc., the data volume is also relatively large, so it is necessary to support multiple interfaces in the collection method and to have an efficient information processing platform. Here, the collection layer is responsible for information collection, and different collection methods are adopted for different collection objects, such as SNMP agent, Syslog, Trap probe, MQ-based JMS agent, etc.; the data processing layer, as the log information processing center, shall perform preliminary preprocessing on the information transmitted by the collection layer; at the application component interface layer, the information shall be statistically analyzed and processed according to the established strategy, and the processing results shall be further published; The data access unit is composed of a unified data access interface, a database adapter, and a file adapter. The unified data access interface carries all application requests for data information. The application can submit data requests to the unified data access interface through various methods such as interface API calls and interface batch file execution, and finally obtain the required data result set; the database adapter carries all specific operations related to the database. In the system related to database operations, it is necessary to read and process data from the custom database and complete write operations. There are already data display classes and data processing classes. These classes are developed for relational databases, but can also be used in real-time data display. Since these classes operate on DataSet, a special adapter can be defined to fill DataSet from the real-time database interface object, so that the operations for these custom databases are exactly the same as those for general relational databases, involving query, update and deletion for the database. The use of data adapters allows data sources of different formats to be used by the same upper-layer application, thereby improving the scalability and maintainability of the system; the file adapter carries all specific operations related to the file system. The file adapter consists of two adapters: a receiving adapter and a sending adapter. The file receiving adapter can be used to read messages from files and submit them to the server. When reading from a file, the adapter will lock the file to ensure that the file content cannot be modified. The file receiving adapter reads messages from files on the local file system or network share. If the specified location in the network share cannot be accessed due to network problems, the receiving adapter will retry the read operation. After the file is read and successfully accepted, the receiving adapter will delete the file from the file system or network share. If the message has been read but the pipeline If the message is not processed successfully, the adapter places the message in a suspended queue and then deletes the file from the file system or network share. You can also configure the file receive adapter to rename the file as it is processed. The file should be renamed to ensure that the receive adapter does not generate duplicate messages when the receive location is closed and restarted. This is a configurable option for file receive locations. The file send adapter transfers the file from the file system to the specified destination. Before writing content to the file, the file send adapter resolves wildcards to actual file names. When writing messages to a file, the file send adapter obtains the corresponding content from the body of the data file. The file adapter can write the file directly to the file system or use the file system cache to write it to the file system. This can improve performance, especially for large files.The main features of the data access component are as follows: applications that have access, read and write requests for data only need to maintain a standardized interface call relationship with the unified data access interface to perform various operations on the data they need to access; when the access address of existing data changes, database products are updated, versions are replaced, library table structures are adjusted, and file organization forms change, only corresponding settings need to be made within the unified data access interface, and no revisions need to be made to other parts of the software, and the system can work in the original working mode; effective integration with other frameworks such as business parameter configuration and module hot swapping is achieved;. The process control unit is composed of a process configurator, a node configurator, a process scheduling controller, a node activator and a process template. The process configurator carries the process ID number of all data, and its data is obtained through the configuration file, and the data process ID number in the configuration file is read into the process configurator through the policy and parameter configuration framework; the node configurator carries the specific operation items of all processes, and its data is obtained through the configuration file, and the specific operation items of the data process in the configuration file are read into the node configurator through the policy and parameter configuration framework; the node activator is responsible for activating the nodes in the process template. Each node in the process template has two states: activated state and inactivated state. When the node is in the inactivated state, it means that the node does not belong to a specific operation item in the process, that is, it is in an invalid state; when the node is in the activated state, it means that the node is a specific operation item in the process and belongs to a specific step in the process. The node activator activates the process template according to the node state transmitted by the process scheduling controller. Activate the corresponding nodes in the process; the process scheduling controller is the core of process configuration and scheduling technology. When the application needs a process to process data, it submits data information to the process scheduling controller. The process scheduling controller calls the process configurator according to the information of the data to obtain the process ID number of the data, and then calls the node configurator to obtain the specific node of the process, and finally calls the node activator to activate the node in the process template; the process template defines the skeleton of the process, and the node represents an operation item in the process. All operation items are combined to represent a process template. Once a process module is fixed, the sequence of its nodes is determined. The process is represented by a process template. Each node in the process template corresponds to two states, and the setting of its state is achieved through the node activator. In this way, when the node activator sets the state of each node in the process template, a specific process is formed. The process change here is to achieve different combinations of nodes through the change of node state, thereby forming different processes. However, the order of nodes in a process template is relatively fixed, or determined in advance, and it is not allowed to change the order arbitrarily during the operation of the system. The main features of the process engine component are as follows: when the process of existing data needs to be adjusted within the framework of the current process template, the dynamic update of the process can be achieved by modifying the configuration file of the process; when the existing data needs to expand a new node task, or some new data is added to the system, and the data needs a new node task, the dynamic update of the process can be achieved by re-implementing a process template and assigning task logic to the new node in the template; it realizes effective integration with other frameworks such as business parameter configuration and module hot swapping; The plug-in framework unit is composed of a plug-in application framework, a plug-in resource library, a public function library, and plug-in standard specifications. The plug-in application framework is responsible for the overall operation of the application. It knows the entire calling process of the program, but does not know what each process specifically does. It understands the calling relationship between each plug-in, and provides an entry point for plug-in calling, calling some plug-ins at appropriate times to complete the real function. Plug-in calling is the function implemented by calling each plug-in. Another part of the function implemented by the platform plug-in processing function is the specific implementation of the platform extension interface. The framework provides plug-in maintenance processing functions, including plug-in registration and management, as well as the function implementation of the platform extension interface. Plug-in registration is to first search for installed plug-ins in the system according to a certain mechanism, and then register the searched plug-ins on the platform, and The corresponding calling mechanism is generated on the platform, including menu options, toolbars, internal calls, etc. The plug-in management completes the coordination between the plug-in and the platform, generates management information for each plug-in on the platform, and tracks the status of the plug-in. Another major component of the framework is the plug-in interface. The plug-in interface is a protocol, which may be described in IDL, may be a header file, or may be a text description. The plug-in is implemented according to this protocol and can be added to the application. Of course, for complex systems, there may be multiple plug-in interfaces, each with independent functions. The plug-in resource library centrally manages all plug-ins included in the application. The plug-ins included are entities that perform actual functions and implement the required plug-in interfaces. Although what to implement and how to implement it are entirely the freedom of the plug-in itself. In practice, there are usually some limitations, because the plug-in interface itself may be a limitation. For example, a plug-in that implements the compilation function cannot be implemented as a plug-in for the chat function. The public function library is a set of functions or classes that can be called by both the application framework and the plug-in. It is usually an independent dynamic library. The application framework itself is public and is a way to reuse code, but not all reusable code can be placed in the framework, especially the public code used by the plug-in. That will cause the plug-in to rely on the framework. It is a good method to extract these public codes into an independent library. The plug-in standard specification is a standard specification for plug-in-style software frameworks. It provides support at the standard level, including plug-in interface standards, plug-in design and development standards, plug-in calling standards, etc., and provides guidance for all aspects involved in the plug-in framework. The main features of the plug-in framework technology are as follows: the system overall framework applies plug-in technology, proposes standard specifications for plug-in interfaces, provides plug-in integration capabilities, and integrates various algorithms and functional controls into the platform plug-in framework in the form of plug-ins; various algorithms and functional controls can be added or adjusted without changing the overall system architecture to achieve hot-swappable integration; other components of the technical framework are developed and integrated according to plug-in standards, together forming a loosely coupled and easily expandable information system; The application integration and calling layer includes an access control unit, a component calling unit and a data communication to implement a business application component unit. The access control unit, the component calling unit and the data communication are used to implement the safe and reliable calling of the platform framework component by the business application component unit. The interface and function expansion of the platform framework layer for the actual business logic are implemented through component registration and publishing.

[0024] Working principle: First, the basic environment layer defines the basic software environment that software design, development, and operation rely on. The software will adopt a data access and storage management mechanism that combines databases and shared file systems. The storage and shared access of all relational data are realized through relational databases, and shared access of all file data is realized through shared file systems. The entire software will be compiled and deployed on the server side based on the Linux operating system. Secondly, the platform framework layer includes transaction processing units, log control units, data access units, process control units, plug-in framework units, status monitoring units, business information configuration units, and task scheduling units, thereby effectively ensuring the reliability, stability, and efficient development of the entire software. The transaction processing unit solves the problem of consistency in all processes related to data storage and acquisition in the system. The log control unit solves the problem of system log collection, configuration, and analysis. The data access unit solves the problem of data security access in the system, provides convenient data access and management interfaces for applications, and meets the security and effectiveness requirements of the interaction between applications and database systems. The process control unit solves the problem of online configuration of the data processing process in the system, realizes the configurability of the processing method, improves the flexibility of the processing method and the flexibility of business process control, and meets the configurability and scalability of the processing method. The plug-in framework unit proposes a set of interface specifications. Through the support of the underlying plug-in engine, it provides a framework foundation for the dynamic scalability of the system, realizes dynamic identification, automatic loading and immediate effectiveness of the update module at runtime, and meets the flexibility and scalability requirements of the system during operation. The state monitoring unit solves the system security problem in the development system, dynamically detects the relevant state of the system at runtime, and processes the corresponding events according to the pre-defined strategy to ensure the safe and stable operation of the system and meet the security and reliability requirements of the system. The business information configuration unit solves the problem of immediate effectiveness of a series of configuration files such as policies and business parameters in the system, so that the configuration files have the flexibility and configurability of modification, and meet the scalability and maintainability requirements of policies and business parameters. The task scheduling unit solves the problem of job scheduling based on time, event, priority and other strategies in the system, so that the application system can automatically run and complete related jobs according to the corresponding strategy, and realize the automatic operation mode of the system; parallel computing will use the relevant technologies of MPI / OpenMP in software design and development to realize the parallel processing of the system and abstract and extract the public parallel processing interface for the parallel processing of application business logic. Finally, the application integration and call layer realizes the access and interaction between business application components and the platform framework layer.

[0025] The above description is only a preferred specific implementation manner of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can make equivalent replacements or changes according to the technical scheme and inventive concept of the present invention within the technical scope disclosed by the present invention, which should be covered by the protection scope of the present invention.

Claims

1. A multi-source satellite remote sensing data processing and analysis system for marine meteorological environment, characterized by: include: The basic environment layer defines the basic software environment on which software design, development, and operation depend; The platform framework layer provides all framework-level support for the entire software. All business application logic components of the software will be designed and developed based on the basic framework provided by the platform framework layer. The application integration and call layer implements the access and interaction between business application components and the platform framework layer.

2. A multi-source satellite remote sensing data processing and analysis system for marine meteorological environment according to claim 1, characterized in that: The platform framework layer includes a transaction processing unit, a log control unit, a data access unit, a process control unit, a plug-in framework unit, a state monitoring unit, a business information configuration unit and a task scheduling unit. The transaction processing unit solves the problem of consistency in all processes related to data storage and acquisition in the system. The log control unit solves the problem of system log collection, configuration and analysis. The data access unit solves the problem of data security access in the system. The process control unit solves the problem of online configuration of the data processing process in the system. The plug-in framework unit proposes a set of interface specifications, and through the support of the underlying plug-in engine, provides a framework foundation for the dynamic scalability of the system. The state monitoring unit solves the system security problem in the system, dynamically detects the relevant state of the system during operation, and processes the corresponding events according to pre-defined strategies. The business information configuration unit solves the problem of immediate effectiveness of a series of configuration files such as policies and business parameters in the system. The task scheduling unit solves the problem of job scheduling based on time, event, priority and other strategies in the system, so that the application system can automatically run and complete related jobs according to the corresponding strategies.

3. A multi-source satellite remote sensing data processing and analysis system for marine meteorological environment according to claim 2, characterized in that: The transaction processing unit consists of application components, resource managers, and transaction managers. Application components are clients of transactional resources, and they are programs used by application developers to implement transactions; the resource manager is a component that manages a persistent and stable data storage system, and participates in the two-phase commit and recovery protocol with the transaction manager; the transaction manager is the core component of a transaction processing environment.

4. A multi-source satellite remote sensing data processing and analysis system for marine meteorological environment according to claim 3, characterized in that: The log control unit is composed of a log information collection platform, a log collection scheduling, a log statistical analysis, and a log interface.

5. A multi-source satellite remote sensing data processing and analysis system for marine meteorological environment according to claim 4, characterized in that: The data access unit is composed of a unified data access interface, a database adapter, and a file adapter. The unified data access interface carries all application requests for data information; the database adapter carries all specific operations related to the database; and the file adapter carries all specific operations related to the file system.

6. A multi-source satellite remote sensing data processing and analysis system for marine meteorological environment according to claim 5, characterized in that: The process control unit is composed of a process configurator, a node configurator, a process scheduling controller, a node activator and a process template. The process configurator carries the process ID number of all data; the node configurator carries the specific operation items of all processes; the node activator is responsible for activating the nodes in the process template; The process scheduling controller is the core of process configuration and scheduling technology; the process template defines the skeleton of the process.

7. A multi-source satellite remote sensing data processing and analysis system for marine meteorological environment according to claim 6, characterized in that: The plug-in framework unit is composed of a plug-in application framework, a plug-in resource library, a public function library, and plug-in standard specifications. The plug-in application framework is responsible for the overall operation of the application; the plug-in resource library centrally manages all plug-ins contained in the application; the public function library is a group of functions or classes that can be called by both the application framework and the plug-in; the plug-in standard specifications provide support for the plug-in software framework from the standard specification level, including plug-in interface standards, plug-in design and development standards, plug-in calling standards, etc., providing guidance for all aspects involved in the plug-in framework. The main features of the plug-in framework technology are as follows: the system overall framework applies plug-in technology, proposes standard specifications for plug-in interfaces, provides plug-in integration capabilities, and integrates various algorithms and functional controls into the platform plug-in framework in the form of plug-ins; various algorithms and functional controls can be added or adjusted without changing the overall system architecture to achieve hot-swappable integration; the components of other technical frameworks are developed and integrated according to plug-in standards, and together constitute a loosely coupled and easily expandable information system.

8. A multi-source satellite remote sensing data processing and analysis system for marine meteorological environment according to claim 7, characterized in that: The application integration and calling layer includes an access control unit, a component calling unit and a data communication to implement a business application component unit. The access control unit, the component calling unit and the data communication are used to implement the safe and reliable calling of the platform framework component by the business application component unit. The interface and function expansion of the platform framework layer for the actual business logic are implemented through component registration and publishing.

Images