Data processing method, apparatus, system, electronic device and storage medium

Abstract

Provided in the present disclosure are a data processing method, an apparatus, a system, an electronic device and a storage medium. The method is applied to a device comprising a plurality of physical boards, and comprises: for each physical board among a plurality of physical boards, on the basis of a description file corresponding to the physical board, creating a plurality of target components corresponding to the physical board, the target components comprising at least one of the following: a management component, a device component and an application component, the management component being used for managing the device component and the application component, and the application component being deployed in the device component; on the basis of integrated information, establishing connections between the plurality of target components; and running the plurality of target components to achieve a control function and / or a protection function of the device.

Description

Data processing method, device and system, electronic device and storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This disclosure is based on Chinese patent application number 202410339981.6, application date March 22, 2024, and invention name “Data processing method, device and system, electronic device and storage medium”, and claims the priority of the Chinese patent application. The entire content of the Chinese patent application is hereby introduced into this disclosure as a reference. Technical Field

[0003] The present disclosure relates to, but is not limited to, the technical field of power equipment, and in particular to a data processing method, device and system, electronic equipment and storage medium. Background Art

[0004] In the related art, most power equipment (for example, control equipment, protection equipment, control protection equipment, etc.) is customized and developed according to demand, which has problems such as high development cost and low efficiency. Summary of the Invention

[0005] In view of this, the embodiments of the present disclosure provide a data processing method, device and system, electronic device and storage medium, which realize the control function and / or protection function of the device through various target components abstracted by software, improve the reusability and portability of the target components, thereby reducing development costs while improving development efficiency.

[0006] The technical solution of the embodiment of the present disclosure is implemented as follows:

[0007] The present disclosure provides a data processing method, which is applied to a device including multiple physical boards. The method includes:

[0008] For each of the multiple physical boards, based on a description file corresponding to the physical board, a plurality of target components corresponding to the physical board are created, wherein the target components include at least one of the following: a management component, a device component, and an application component, wherein the management component is used to manage the device component and the application component, and the application component is deployed in the device component;

[0009] Based on the integration information, connections between multiple target components are established;

[0010] Multiple target components are run to implement the control function and / or protection function of the equipment.

[0011] In the embodiments disclosed herein, first, by abstracting each physical board to provide a universal hardware framework, the needs of different devices can be met; second, the control function and / or protection function of the device is realized by software-abstracting each target component, which improves the reusability and portability of the target component, thereby reducing development costs and improving development efficiency; finally, through the hardware and software decoupling design, the complexity of the device is reduced while also reducing costs.

[0012] In some embodiments, when the physical board includes a management board, the multiple target components include a first management component, a first device component, and a first application component; based on the description file corresponding to the physical board, multiple target components corresponding to the physical board are created, including: based on the description file corresponding to the management board, the first management component, the first device component, and the first application component corresponding to the management board are created.

[0013] In the embodiment of the present disclosure, on the one hand, the physical board with management function is abstracted as a management board to facilitate the unification of the hardware framework; on the other hand, corresponding components are created according to the description file corresponding to the management board, thereby improving the function of the management board.

[0014] In some embodiments, the first management component includes a system management component, a first device management component and a first application management component; creating the first management component, the first device component and the first application component corresponding to the management board includes: creating and instantiating the system management component; installing the first device management component based on the device management interface of the system management component; registering the first device component based on the device registration interface of the first device management component; installing the first application management component based on the application management interface of the system management component; and creating the first application component based on the application creation interface of the first application management component.

[0015] In the embodiment of the present disclosure, multiple components in the management board are created in sequence according to the logical relationship between the various components in the software framework, thereby ensuring the realization of the component functions.

[0016] In some implementations, the first management component further includes a file management component, and the method further includes: creating the file management component, and mounting the target file system based on a file mounting interface of the file management component.

[0017] In the embodiment of the present disclosure, a file system is mounted on the management board to facilitate management of files in the device.

[0018] In some embodiments, when the physical board includes an application board, the multiple target components include a second management component, a second device component, and a second application component; based on the description file corresponding to the physical board, creating multiple target components corresponding to the physical board includes: based on the description file corresponding to the application board, creating the second management component, the second device component, and the second application component corresponding to the application board.

[0019] In the embodiment of the present disclosure, on the one hand, the physical board with application function is abstracted as an application board to facilitate the unification of the hardware framework; on the other hand, corresponding components are created according to the description file corresponding to the application board, thereby improving the function of the application board.

[0020] In some embodiments, the second management component includes a second device management component and a second application management component; based on the description file corresponding to the application board, the second management component, the second device component and the second application component corresponding to the application board are created, including: installing the second device management component based on the device management interface of the system management component corresponding to the management board; registering the second device component based on the device registration interface of the second device management component; installing the second application management component based on the application management interface of the system management component; and creating the second application component based on the application creation interface of the second application management component.

[0021] In the embodiment of the present disclosure, multiple components in the application board are created in sequence according to the logical relationship between the various components in the software framework, thereby ensuring the realization of the component functions.

[0022] In some embodiments, when the physical board includes an interface board, the multiple target components include a third device management component and a third device component; based on the description file corresponding to the physical board, multiple target components corresponding to the physical board are created, including: based on the description file corresponding to the interface board, the third device management component and the third device component corresponding to the interface board are created.

[0023] In the embodiment of the present disclosure, on the one hand, the physical board with interface function is abstracted as an interface board to facilitate the unification of the hardware framework; on the other hand, corresponding components are created according to the description file corresponding to the interface board, thereby improving the function of the interface board.

[0024] In some embodiments, creating a third device management component and a third device component corresponding to the interface board includes: installing the third device management component based on the device management interface of the system management component corresponding to the management board; and registering the third device component based on the device registration interface of the third device management component.

[0025] In the embodiment of the present disclosure, multiple components in the interface board are created in sequence according to the logical relationship between the various components in the software framework, thereby ensuring the realization of the component functions.

[0026] In some embodiments, the integration information includes deployment information and connection information. Based on the integration information, connections are established between multiple target components, including: based on the deployment information, deploying the application component to the device component through the application interface of the system management component corresponding to the management board; based on the connection information, establishing connections between multiple target components.

[0027] In the embodiment of the present disclosure, connections between target components are established in sequence according to the deployment information and the connection information, thereby ensuring the execution of each component and thus ensuring the precise implementation of the control function and / or protection function.

[0028] An embodiment of the present disclosure provides a data processing system, the system including a device including multiple physical boards and a processing module, wherein:

[0029] The processing module is used to: for each physical board among the multiple physical boards, create multiple target components corresponding to the physical board based on a description file corresponding to the physical board, where the target components include at least one of the following: a management component, a device component, and an application component, where the management component is used to manage the device component and the application component, and the application component is deployed in the device component; establish connections between the multiple target components based on the integration information; and run the multiple target components to realize the control function and / or protection function of the device.

[0030] In the embodiments disclosed herein, first, by abstracting each physical board to provide a universal hardware framework, the needs of different devices can be met; second, the control function and / or protection function of the device is realized by software-abstracting each target component, which improves the reusability and portability of the target component, thereby reducing development costs and improving development efficiency; finally, through the hardware and software decoupling design, the complexity of the device is reduced while also reducing costs.

[0031] In some embodiments, the processing module includes an application part, a communication middleware and a driver part, wherein: the application part is used to create multiple target components corresponding to the physical board card based on the description file corresponding to the physical board card; establish connections between the multiple target components based on the integration information; and run the multiple target components; the communication middleware is used to realize data transmission between the application part and the driver part; and the driver part is used to drive the corresponding physical board card based on the data transmitted by the communication middleware to realize the control function and / or protection function of the device.

[0032] In the embodiments of the present disclosure, the decoupling between the application part and the driver part is achieved through the communication middleware, which reduces the difficulty and complexity of communication system development and can also improve the portability, stability and scalability of the communication system.

[0033] In some embodiments, when the physical board includes a management board, the multiple target components include a first management component, a first device component, and a first application component; the processing module is also used to: create the first management component, the first device component, and the first application component corresponding to the management board based on the description file corresponding to the management board.

[0034] In the embodiment of the present disclosure, on the one hand, the physical board with management function is abstracted as a management board to facilitate the unification of the hardware framework; on the other hand, corresponding components are created according to the description file corresponding to the management board, thereby improving the function of the management board.

[0035] In some embodiments, the first management component includes a system management component, a first device management component and a first application management component; the processing module is further used to: create and instantiate the system management component; install the first device management component based on the device management interface of the system management component; register the first device component based on the device registration interface of the first device management component; install the first application management component based on the application management interface of the system management component; and create the first application component based on the application creation interface of the first application management component.

[0036] In the embodiment of the present disclosure, multiple components in the management board are created in sequence according to the logical relationship between the various components in the software framework, thereby ensuring the realization of the component functions.

[0037] In some embodiments, when the physical board includes an application board, the multiple target components include a second management component, a second device component, and a second application component; the processing module is also used to: create a second management component, a second device component, and a second application component corresponding to the application board based on the description file corresponding to the application board.

[0038] In the embodiment of the present disclosure, on the one hand, the physical board with application function is abstracted as an application board to facilitate the unification of the hardware framework; on the other hand, corresponding components are created according to the description file corresponding to the application board, thereby improving the function of the application board.

[0039] In some embodiments, when the physical board includes an interface board, the multiple target components include a third device management component and a third device component; the processing module is also used to: create a third device management component and a third device component corresponding to the interface board based on the description file corresponding to the interface board.

[0040] In the embodiment of the present disclosure, on the one hand, the physical board with interface function is abstracted as an interface board to facilitate the unification of the hardware framework; on the other hand, corresponding components are created according to the description file corresponding to the interface board, thereby improving the function of the interface board.

[0041] In some embodiments, the integration information includes deployment information and connection information; the processing module is also used to: based on the deployment information, deploy the application component to the device component through the application interface of the system management component corresponding to the management board; based on the connection information, establish connections between multiple target components.

[0042] In the embodiment of the present disclosure, connections between target components are established in sequence according to the deployment information and the connection information, thereby ensuring the execution of each component and thus ensuring the precise implementation of the control function and / or protection function.

[0043] An embodiment of the present disclosure provides a data processing device, which is applied to a device including multiple physical boards. The device includes:

[0044] a creation module, configured to create, for each of the plurality of physical boards, a plurality of target components corresponding to the physical board based on a description file corresponding to the physical board, the target components including at least one of the following: a management component, a device component, and an application component, the management component being configured to manage the device component and the application component, and the application component being deployed into the device component;

[0045] A connection module, used for establishing connections between multiple target components based on the integration information;

[0046] The operation module is used to operate multiple target components to implement the control function and / or protection function of the device.

[0047] An embodiment of the present disclosure provides an electronic device, including a processor and a memory, wherein the memory stores a computer program that can be run on the processor, and when the processor executes the computer program, any of the above methods is implemented.

[0048] An embodiment of the present disclosure provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, any of the above methods is implemented.

[0049] An embodiment of the present disclosure provides a computer program product, including a computer program or instructions. When the computer program or instructions are executed by a processor, any of the above methods is implemented.

[0050] It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] The accompanying drawings herein are incorporated into and constitute a part of the specification. These drawings illustrate embodiments consistent with the present disclosure and, together with the specification, are used to explain the technical solutions of the present disclosure.

[0052] FIG1 is a schematic diagram of a first implementation flow of a data processing method provided by an embodiment of the present disclosure;

[0053] FIG2 is a schematic diagram of an inheritance relationship between different components provided by an embodiment of the present disclosure;

[0054] FIG3 is a schematic diagram of a relationship between various description files provided in an embodiment of the present disclosure;

[0055] FIG4 is a schematic diagram showing the connection of various components provided in an embodiment of the present disclosure;

[0056] FIG5 is a schematic diagram of the structure of a data processing system provided by an embodiment of the present disclosure;

[0057] FIG6 is a schematic diagram of the composition structure of a device provided by an embodiment of the present disclosure;

[0058] FIG7 is a schematic diagram of the composition of components corresponding to a physical board provided by an embodiment of the present disclosure;

[0059] FIG8 is a schematic diagram of the composition structure of a processing module provided in an embodiment of the present disclosure;

[0060] FIG9 is a second schematic diagram of an implementation flow of a data processing method provided by an embodiment of the present disclosure;

[0061] FIG10 is a schematic diagram of the structure of a data processing device provided by an embodiment of the present disclosure;

[0062] FIG11 is a schematic diagram of a hardware entity of an electronic device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0063] In order to make the purpose, technical solutions and advantages of the present disclosure clearer, the present disclosure will be further described in detail below with reference to the accompanying drawings. The described embodiments should not be regarded as limiting the present disclosure. All other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present disclosure.

[0064] In the following description, reference is made to “some embodiments”, which describes a subset of all possible embodiments, but it will be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0065] In the following description, the terms "first\second\third" are merely used to distinguish similar objects and do not represent a specific ordering of the objects. It is understandable that "first\second\third" can be interchanged with a specific order or sequence where permitted, so that the embodiments of the present disclosure described herein can be implemented in an order other than that illustrated or described herein.

[0066] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art in the art of the present disclosure. The terms used herein are only for the purpose of describing the embodiments of the present disclosure and are not intended to limit the present disclosure.

[0067] In related technologies, under the traditional development model, most power equipment (for example, control equipment, protection equipment, control protection equipment, etc.) are customized and developed according to demand. There is no unified design framework, so the interconnection between various modules in the equipment needs to be adapted according to the project, resulting in problems such as high development cost and low efficiency.

[0068] The embodiment of the present disclosure provides a data processing method. First, by abstracting each physical board to provide a universal hardware framework, it can meet the needs of different security devices; secondly, by implementing the control function and / or protection function of the device through each target component abstracted by software, the reusability and portability of the target component are improved, thereby reducing development costs while improving development efficiency; finally, through the hardware and software decoupling design, the complexity of the device is reduced while also reducing costs. The method provided by the embodiment of the present disclosure can be executed by an electronic device, and the electronic device can be various types of terminals such as laptops, tablets, desktop computers, set-top boxes, mobile devices (for example, mobile phones, portable music players, personal digital assistants, dedicated messaging devices, portable gaming devices), etc., and can also be implemented as a server. The server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms.

[0069] Below, the technical solutions in the embodiments of the present disclosure will be clearly and completely described in conjunction with the drawings in the embodiments of the present disclosure.

[0070] FIG1 is a schematic diagram of a first implementation flow of a data processing method provided by an embodiment of the present disclosure, which is applied to a device including multiple physical boards. As shown in FIG1 , the method includes steps S11 to S13, wherein:

[0071] Step S11: For each physical board among the multiple physical boards, based on the description file corresponding to the physical board, create multiple target components corresponding to the physical board, where the target components include at least one of the following: a management component, a device component, and an application component. The management component is used to manage the device component and the application component, and the application component is deployed in the device component.

[0072] Here, the device can be any suitable device, such as a control device, a protection device, or a control and protection device. A control device is primarily used to implement a control function. A protection device is primarily used to implement a protection function. A control and protection device is primarily used to implement both control and protection functions. In some embodiments, the control and protection device may include, but is not limited to, a DC control and protection device, an AC control and protection device, or other control and protection devices. A DC control and protection device, also known as a DC control and protection device, primarily refers to a secondary device used to control and protect primary equipment such as valves and switches in a DC power transmission system. In implementation, different DC control and protection devices can implement different protection functions. For example, a nitrogen protection device (NPSDevice) primarily refers to a device that replaces oxygen in the air by injecting high-purity nitrogen into the air, thereby creating a low-oxygen environment to protect items. Another example is a valve cooling device (VCCPDevice), which primarily transfers heat generated by various components on the valve body to maintain safe operation of the valve under specified conditions. For example, HVAC device mainly refers to a device that protects objects by injecting warm air.

[0073] AC control and protection equipment, also known as AC control and protection equipment, mainly refers to primary / secondary equipment that controls and protects AC equipment.

[0074] The physical board can be any suitable board. For example, a control board such as an FPGA (Field Programmable Gate Array) or a CPU (Central Processing Unit) can be used. Another example is a communication board such as CAN or Ethernet.

[0075] In some embodiments, each physical board can be divided into a management board, an application board, and an interface board according to the function of the physical board. Among them, the management board is mainly used to manage the status and initialization of the device. The application board mainly refers to the board that performs control protection, algorithms, exception handling, etc., and is used to complete the application function. The interface board mainly refers to the board used for internal and external communication. In some embodiments, different devices may include different physical boards, and the number of physical boards with different functions may be at least one. For example, for device A, it includes a management board, two application boards, and two interface boards; for device B, it includes a management board, three application boards, and one interface board.

[0076] In some embodiments, the physical boards are interconnected through a variety of buses. The buses may include but are not limited to data buses, management buses, etc. The management bus is mainly used for program distribution, instruction interaction, etc. In implementation, the management bus may include but is not limited to CAN bus, 100M Ethernet and other medium and low-speed buses. The data bus is mainly used for data interaction and has high bandwidth and real-time requirements. In implementation, the data bus may include but is not limited to LVDS (Low Voltage Differential Signaling) bus, Gigabit Ethernet, RapidIO, etc. RapidIO is a high-performance, low-pin-count, data packet switching-based interconnection architecture pioneered by companies such as Motorola and Mercury. It is an open interconnection technology standard designed to meet the needs of future high-performance embedded systems.

[0077] Management components mainly refer to components used to implement management functions, such as the device management component DeviceManager, the file management component FileManager, the application management component ApplicationManager, the system management component SystemManager, and the resource management component ResourceManager.

[0078] DeviceManager is a component used for unified device management, providing interfaces for registering, deregistering, and deactivating devices. For example, a device can be registered using the device registration interface registerDevice(); released using the device deregistration interface unregisterDevice(); and shut down using the device deactivation interface shutdownDevice(). In some implementations, this device management component also provides attributes such as the name, device description file path, and device information. Device information primarily includes information about registered devices.

[0079] ApplicationManager is a component that manages application components and provides corresponding interfaces for creating applications. For example, applications are created through the application creation interface createApplication(). In some embodiments, the application management component also provides related properties such as naming and software package description file path.

[0080] FileManager is used to manage file systems, providing corresponding interfaces for mounting, unmounting, and obtaining file systems. For example, a file system can be mounted using the mount() method, unmounted using the umount() method, and a mounted file system can be obtained using the getMounts() method.

[0081] SystemManager is used to manage other management components, application components, etc., and to install and uninstall other management components and application components by providing corresponding interfaces. For example, a device management component is installed through the device management interface registerDeviceManager(), and a device management uninstallation interface unregisterDeviceManager() is used to uninstall a device management component; an application management component is installed through the application management interface registerApplicationManager(), and an application management component is uninstalled through the application management uninstallation interface unregisterApplicationManager(); an application is installed through the application interface installApplication(), and an application is uninstalled through the application uninstallation interface uninstallApplication(). In some embodiments, the system management component also provides related attributes such as device management information, application management information, application information, file management information, and system description file path. Device management information mainly refers to obtaining installed device management components. Application management information mainly refers to obtaining installed application management components. Application information mainly refers to obtaining installed application components. File management information mainly refers to obtaining installed file management components.

[0082] The ResourceManager manages resource components by providing corresponding interfaces for creating, destroying, and deactivating them. For example, a resource can be created using the resource creation interface createRegister(); a resource can be released using the resource destruction interface releaseResource(); and a resource can be shut down using the resource deactivation interface shutdownResource(). In some implementations, the resource management component also provides related attributes such as an identifier.

[0083] In some implementations, the number of management components may be at least one.

[0084] Application components mainly refer to components that implement application functions. For example, control application components, algorithm application components, communication application components, valve control application components (i.e., control of energy storage valves), data acquisition application components, etc. Application inherits the resource component Resource and provides related properties such as naming label, description file path Profile, calling device componentDevices, etc. Resource is the smallest unit of functional components, inherits the basic component, and provides component start interface start(), stop interface stop(), etc. In some embodiments, Resource also provides related properties such as identification.

[0085] Basic components may include, but are not limited to, port components, LifeCycle components, and Property components. Port primarily provides the port connection interface connect(), disconnection interface disconnect(), and acquisition interface getPort(). During implementation, data is transferred between components through the Port component. LifeCycle primarily provides the component initialization interface initialize() and release interface releaseObject(). Property primarily provides the component property configuration interface configure() and query interface query(). In some implementations, the number of application components may be at least one.

[0086] The device component Device is mainly a software component used to implement device functions. For example, communication device components, control device components, fire protection equipment components, FPGA device components, Ethernet device components, voltage and current acquisition device components, input and output device components (i.e., devices that implement switch functions), etc. Device inherits Resource, provides resource acquisition interface allocateCapacity(), resource release interface deallocateCapacity(), etc., and provides related properties such as usage status and software package description file path. In some embodiments, the number of device components can be at least one. In some embodiments, commonly used power equipment components such as FPGA device FPGADevice, nitrogen protection device NPSDevice, valve cooling protection device VCCPDevice, HVAC protection device HVACDevice, etc. can be pre-established, and these power equipment components inherit the device component.

[0087] FIG2 is a schematic diagram of an inheritance relationship between different components provided by an embodiment of the present disclosure, as shown in FIG2 , wherein:

[0088] The resource component Resource inherits the port component Port, the lifecycle component LifeCycle and the property component Property;

[0089] The application component Application and the device component Device inherit the resource component Resource;

[0090] The system management component SystemManager manages the file management component FileManager, the application management component ApplicationManage and the device management component DeviceManager. The file management component FileManager is used to mount the file system component FileSystem, the device management component DeviceManager is used to manage the device component Device, and the application management component ApplicationManager is used to manage the application component Application.

[0091] Description files are primarily used to describe information about software, components, hardware, and integration. Description files can be in any suitable format, such as XML (Extensible Markup Language) or HTML (Hypertext Markup Language). In some implementations, each physical board has a corresponding description file. Different physical boards have different description files. These description files may include, but are not limited to, system descriptors, device configuration descriptors, component descriptors, software package descriptors, and assembly descriptors. System descriptors are primarily used by system management components to describe resources within the entire system and their relationships. Resources may include, but are not limited to, applications and devices. Device descriptors are primarily used by device components to describe device types and parameters. Component descriptors primarily describe component information, such as its name, identifier, type, and file storage path. Software package descriptors are primarily used by application components to describe application information, such as which devices the application component runs on. The integration description file is mainly used to describe the deployment of each application and the connection information of each component.

[0092] Figure 3 is a schematic diagram of the relationship between various description files provided in an embodiment of the present disclosure. As shown in Figure 3, the system description file 310 may include a device description file 311, a software package description file 312 and an integration description file 313. The device description file 311 may include a component description file 3111, and the software package description file 312 may include a component description file 3112.

[0093] In some embodiments, different physical boards correspond to different target components. For example, for a management board or an application board, the target component may include, but is not limited to, a management component, an application component, a device component, etc. For another example, for an interface board, the target component may include, but is not limited to, a management component, a device component, etc.

[0094] Step S12: Establish connections between multiple target components based on the integration information.

[0095] Integration information may include, but is not limited to, deployment information and connection information. Deployment information describes the deployment between application components and device components. For example, application component A1 and application component A2 are both deployed on device component B1. Connection information describes the connection between target components using ports. For example, device component B2 is connected to device component B2 via port C.

[0096] In some implementations, the integration information includes deployment information and connection information, and step S12 includes steps S121 to S122, wherein:

[0097] Step S121: Based on the deployment information, the application component is deployed to the device component through the application interface of the system management component corresponding to the management board.

[0098] Here, the device includes at least a management board. The target component corresponding to this management board includes at least a system management component. This system management component includes interfaces for installing and uninstalling ApplicationManager, DeviceManager, and Application, and provides related properties such as device management information, application management information, application information, file management information, and the path to the system description file. For example, the application management component is installed using the registerApplicationManager() interface. Another example is obtaining device management information through the defined deviceManagers variable.

[0099] During implementation, the application is deployed to the device component through the installApplication() interface to complete the loading of the application on the device.

[0100] Step S122: Establish connections between multiple target components based on the connection information.

[0101] Here, the connection information is used to establish connections between different components through ports. In implementation, data communication between components is also completed through ports.

[0102] Figure 4 is a connection diagram of various components provided in an embodiment of the present disclosure. As shown in Figure 4, a certain function of the device is completed through the control application component 411, the algorithm application component 412 and the communication application component 413. The control application component 411 is connected to the algorithm application component 412 and the communication application component 413 through a port. During implementation, the control application component 411 and the algorithm application component 412 are both deployed on the FPGA device 421, and the communication application component 413 is deployed on the communication device component 422.

[0103] In the embodiment of the present disclosure, connections between target components are established in sequence according to the deployment information and the connection information, thereby ensuring the execution of each component and thus ensuring the precise implementation of the control function and / or protection function.

[0104] Step S13: running multiple target components to implement the control function and / or protection function of the device.

[0105] Here, each target component is started and operated. Upon receiving a trigger signal, the corresponding control and / or protection logic operations are executed sequentially according to the execution order of each target component to achieve the corresponding function. For example, for the secondary equipment of a smart substation, upon receiving a timed trigger signal, the operating parameters of the secondary equipment of the smart substation are checked and an alarm is issued for abnormal signals.

[0106] In the embodiments disclosed herein, first, by abstracting each physical board to provide a universal hardware framework, the needs of different devices can be met; second, the control function and / or protection function of the device is realized by software-abstracting each target component, which improves the reusability and portability of the target component, thereby reducing development costs and improving development efficiency; finally, through the hardware and software decoupling design, the complexity of the device is reduced while also reducing costs.

[0107] In some embodiments, when the physical board includes a management board, the multiple target components include a first management component, a first device component, and a first application component; and the step S11 of "creating multiple target components corresponding to the physical board based on a description file corresponding to the physical board" includes step S111, wherein:

[0108] Step S111: Based on the description file corresponding to the management board, create a first management component, a first device component, and a first application component corresponding to the management board.

[0109] Here, the management board is primarily used to manage device status, initialization, and other aspects. There can be at least one first management component. This first management component is primarily used to manage the various components corresponding to the management board. In some embodiments, the management board may also provide devices, necessitating the creation of a device component and a device management component. In some embodiments, the devices in the management board may also run applications, necessitating the creation of an application component and an application management component.

[0110] In some embodiments, the first management component may include, but is not limited to, a system management component, a first device management component, a first application management component, a file management component, and the like. The first device management component is primarily used to manage the first device component. During implementation, there may be at least one first device component. The first application management component is primarily used to manage the first application component. During implementation, there may be at least one first application component.

[0111] The management board may correspond to at least one description file, such as a system description file, a device description file, a component description file, a software package description file, or an integration description file. During implementation, the first management component, the first device component, and the first application component corresponding to the management board may be sequentially created according to the description files corresponding to the management board.

[0112] In some embodiments, the first management component includes a system management component, a first device management component, and a first application management component; and the step S111 of "creating the first management component, the first device component, and the first application component corresponding to the management board" includes steps S1111 to S1115, wherein:

[0113] Step S1111: Create and instantiate a system management component.

[0114] Here, the system management component is used to manage other management components, application components, etc., and provides corresponding interfaces to install and uninstall other management components and application components. During implementation, the system management component is instantiated through a system description file.

[0115] Step S1112: Install a first device management component based on the device management interface of the system management component.

[0116] Here, the system management component at least includes a device management interface registerDeviceManager(). During implementation, the first device management component is installed through the device management interface according to the device description file corresponding to the management board.

[0117] In some implementations, the system management component further includes a device management uninstallation interface unregisterDeviceManager(), through which the first device management component is uninstalled.

[0118] Step S1113: Register the first device component based on the device registration interface of the first device management component.

[0119] Here, the first device management component at least includes a device registration interface registerDevice(). During implementation, the first device component is registered through the device registration interface according to the device description file corresponding to the management board.

[0120] In some embodiments, the first device management component further includes a device deregistration interface unregisterDevice(), a device deactivation interface shutdownDevice(), etc. The device deregistration interface is used to deregister the first device component. The device deactivation interface is used to shut down the first device component.

[0121] Step S1114: Install the first application management component based on the application management interface of the system management component.

[0122] Here, the system management component at least includes an application management interface registerApplicationManager(). During implementation, the first application management component is installed through the application management interface according to the software package description file corresponding to the management board.

[0123] In some implementations, the system management component further includes an application management uninstallation interface unregisterApplicationManager(), through which the first application management component is uninstalled.

[0124] Step S1115: Create a first application component based on the application creation interface of the first application management component.

[0125] Here, the first application management component at least includes an application creation interface createApplication(). During implementation, the first application component is created through the application creation interface according to the software package description file corresponding to the management board.

[0126] In this way, according to the logical relationship between the various components in the software framework, multiple components in the management board are created in sequence, ensuring the realization of the component functions.

[0127] In the embodiment of the present disclosure, on the one hand, the physical board with management function is abstracted as a management board to facilitate the unification of the hardware framework; on the other hand, corresponding components are created according to the description file corresponding to the management board, thereby improving the function of the management board.

[0128] In some embodiments, the first management component further includes a file management component, and the method further includes step S14, wherein:

[0129] Step S14: Create a file management component, and mount the target file system based on the file mounting interface of the file management component.

[0130] Here, the file management component manages the file system and provides corresponding interfaces for mounting and unmounting the file system. This file management component includes at least the file mounting interface mount(), which adds the required file system to the device. In implementation, this file management component does not require frequent installation and unmounting.

[0131] In some implementations, the file management component further includes a file unmounting interface umount(), a mount information interface getMounts(), etc. During implementation, before mounting or unmounting a file system, the mount information interface can be used to obtain the mounted file system on the device, and then the file system can be mounted or unmounted through the corresponding interface.

[0132] In some embodiments, after a file system is mounted, operations on the file system can be performed using a predefined file system component, FileSystem. This file system component provides interfaces such as remove() for file deletion, copy() for file copying, exist() for path checking, create() for file creation, open() for file opening, and mkdir() for folder removal. In some embodiments, this file system component also provides related properties such as free space and size.

[0133] In some implementations, file operations can be performed using a predefined file component called "File." This file component provides a file read interface called "read()," a file write interface called "write()," a close interface called "close()," a position interface called "seek()," and a file size interface called "sizeOf()." In some implementations, this file component also provides attributes such as a name and a pointer position.

[0134] The target file system may be any suitable file system, for example, FAT32, NTFS (New Technology File System), exFAT (Extended File Allocation Table File System), EXT (Extended file system), and the like.

[0135] In the embodiment of the present disclosure, a file system is mounted on the management board to facilitate management of files in the device.

[0136] In some embodiments, when the physical board includes an application board, the multiple target components include a second management component, a second device component, and a second application component; the step of "creating multiple target components corresponding to the physical board based on a description file corresponding to the physical board" in step S11 includes step S112, wherein:

[0137] Step S112: Based on the description file corresponding to the application board, create a second management component, a second device component, and a second application component corresponding to the application board.

[0138] Here, the application board primarily refers to the board that performs control protection, algorithms, exception handling, and other functions, and is used to complete application functions. There can be at least one second management component. This second management component is primarily used to manage the various components corresponding to the application board. In some embodiments, the application board may also provide devices, necessitating the creation of a device component and a device management component. In some embodiments, the devices in the application board may also run applications, necessitating the creation of an application component and an application management component.

[0139] In some embodiments, the second management component may include, but is not limited to, a second device management component, a second application management component, and the like. The second device management component is primarily used to manage the second device component. In implementation, there may be at least one second device component. The second application management component is primarily used to manage the second application component. In implementation, there may be at least one second application component.

[0140] The application board may correspond to at least one description file, such as a device description file, a component description file, a software package description file, or an integration description file. During implementation, the second management component, the second device component, and the second application component corresponding to the application board may be sequentially created according to the description files corresponding to the application board.

[0141] In some embodiments, the second management component includes a second device management component and a second application management component; and the step S112 of "creating the second management component, the second device component, and the second application component corresponding to the application board" includes steps S1121 to S1124, wherein:

[0142] Step S1121: Install a second device management component based on the device management interface of the system management component corresponding to the management board.

[0143] Here, the second device management component is installed through the device management interface of the system management component according to the device description file corresponding to the application board.

[0144] Step S1122: Register the second device component based on the device registration interface of the second device management component.

[0145] Here, the second device management component is similar to the first device management component. During implementation, the second device component is registered through the device registration interface according to the device description file corresponding to the application board.

[0146] Step S1123: Install the second application management component based on the application management interface of the system management component.

[0147] Here, the second application management component is similar to the first application management component. During implementation, the second application management component is installed through the application management interface according to the software package description file corresponding to the application board.

[0148] Step S1124: Create a second application component based on the application creation interface of the second application management component.

[0149] Here, the second application component is similar to the first application component. During implementation, the second application component is created through the application creation interface according to the software package description file corresponding to the application board.

[0150] In this way, according to the logical relationship between the various components in the software framework, multiple components in the application board are created in sequence, ensuring the realization of the component functions.

[0151] In the embodiment of the present disclosure, on the one hand, the physical board with application function is abstracted as an application board to facilitate the unification of the hardware framework; on the other hand, corresponding components are created according to the description file corresponding to the application board, thereby improving the function of the application board.

[0152] In some embodiments, when the physical board includes an interface board, the multiple target components include a third device management component and a third device component; and the step S11 of "creating multiple target components corresponding to the physical board based on a description file corresponding to the physical board" includes step S113, wherein:

[0153] Step S113: Based on the description file corresponding to the interface board, create a third device management component and a third device component corresponding to the interface board.

[0154] Here, the interface card mainly refers to a card used for internal and external communication. The third management component is mainly used to manage the third device component corresponding to the interface card. The number of the third device component can be at least one.

[0155] The interface board may include at least one description file, such as a device description file, a component description file, and an integration description file. During implementation, the third device component and the third device management component corresponding to the interface board may be created sequentially according to the description files corresponding to the interface board.

[0156] In some implementations, the step S113 of “creating a third device management component and a third device component corresponding to the interface board” includes steps S1131 to S1132, wherein:

[0157] Step S1131: Install a third device management component based on the device management interface of the system management component corresponding to the management board.

[0158] Here, the third device management component is installed through the device management interface of the system management component according to the device description file corresponding to the interface board.

[0159] Step S1132: Register the third device component based on the device registration interface of the third device management component.

[0160] Here, the third device management component is similar to the first device management component. During implementation, the third device component is registered through the device registration interface according to the device description file corresponding to the interface board.

[0161] In this way, according to the logical relationship between the various components in the software framework, multiple components in the interface board are created in sequence, ensuring the realization of the component functions.

[0162] In the embodiment of the present disclosure, on the one hand, the physical board with interface function is abstracted as an interface board to facilitate the unification of the hardware framework; on the other hand, corresponding components are created according to the description file corresponding to the interface board, thereby improving the function of the interface board.

[0163] Based on the above embodiments, the present disclosure further provides a data processing system. FIG5 is a schematic diagram of the structure of a data processing system provided by the present disclosure. As shown in FIG5 , the data processing system 50 includes a device 51 including multiple physical boards and a processing module 52, wherein:

[0164] The processing module 52 is used to: for each physical board among the multiple physical boards, create multiple target components corresponding to the physical board based on the description file corresponding to the physical board, where the target components include at least one of the following: a management component, a device component, and an application component, where the management component is used to manage the device component and the application component, and the application component is deployed in the device component; establish connections between the multiple target components based on the integration information; and run the multiple target components to implement the control function and / or protection function of the device.

[0165] Here, physical boards may include, but are not limited to, management boards, application boards, and interface boards. In some embodiments, different devices may include different physical boards, and the number of physical boards with different functions may be at least one. The physical boards are interconnected via various buses, including, but not limited to, data buses and management buses.

[0166] FIG6 is a schematic diagram of the composition structure of a device provided by an embodiment of the present disclosure. As shown in FIG6 , the device includes a management board 511, multiple application boards 512, multiple interface boards 513, a management bus 514, and a data bus 515, wherein:

[0167] Management board 511, multiple application boards 512 and multiple interface boards 513, which distribute programs and exchange instructions through management bus 514;

[0168] The management board 511 , the plurality of application boards 512 and the plurality of interface boards 513 exchange data via a data bus 515 .

[0169] The processing module can be any suitable module capable of implementing the function. The description file can include, but is not limited to, a system description file, a device description file, a component description file, a software package description file, an integration description file, etc. During implementation, the process of the processing module creating each target component can refer to the specific implementation of the aforementioned step S11.

[0170] FIG7 is a schematic diagram of the components corresponding to a physical board provided in an embodiment of the present disclosure. As shown in FIG7 , the device includes a management board 711, an application board 712, and an interface board 713, wherein:

[0171] The target components corresponding to the management board 711 include system management component, device management component, device component, application management component, application component, and file management component;

[0172] The target components corresponding to the application board 712 include device management components, device components, application management components and application components;

[0173] The target components corresponding to the interface board 713 include a device management component and a device component.

[0174] In some embodiments, the processing module includes an application part, a communication middleware and a driver part, wherein: the application part is used to create multiple target components corresponding to the physical board card based on the description file corresponding to the physical board card; establish connections between the multiple target components based on the integration information; and run the multiple target components; the communication middleware is used to realize data transmission between the application part and the driver part; and the driver part is used to drive the corresponding physical board card based on the data transmitted by the communication middleware to realize the control function and / or protection function of the device.

[0175] Here, the application part can be any suitable part that can realize the function. During implementation, the application part can create various components, such as application components, device components, management components, etc.

[0176] The communication middleware can be any suitable middleware, such as CORBA (Common Object Request Broker Architecture), DDS (Data Distribution Service), or SOME / IP (Scalable Service-Oriented Middleware over IP). DDS is a distributed communication specification published by the Object Management Group (OMG). It uses a publish-subscribe model and provides communication services in the form of middleware. In some embodiments, the communication middleware includes functions such as event and naming services to achieve decoupling of the entire software.

[0177] The driver component includes drivers for various physical boards, such as FPGA board drivers, CPU board drivers, and communication board drivers. In some embodiments, the driver component may reside within an operating system. The operating system may be any suitable operating system, such as Microsoft Windows, Linux, or VxWorks. In some embodiments, the operating system may also include a target file system, which is mounted via a file system component during implementation.

[0178] In the embodiments of the present disclosure, the decoupling between the application part and the driver part is achieved through the communication middleware, which reduces the difficulty and complexity of communication system development and can also improve the portability, stability and scalability of the communication system.

[0179] FIG8 is a schematic diagram of the composition structure of a processing module provided in an embodiment of the present disclosure. As shown in FIG8 , the processing module includes an application part 521, a communication middleware 522, and a driver part 523, wherein:

[0180] The application part 521 is used to create target components corresponding to the device (for example, DC control and protection device) according to the description files;

[0181] The communication middleware 522 is used to implement communication between the application part 521 and the driver part 523;

[0182] The driver part 523 is located in the operating system 524 and is used to drive each physical board to implement the control function and / or protection function.

[0183] FIG9 is a second schematic diagram of an implementation flow of a data processing method provided by an embodiment of the present disclosure. As shown in FIG9 , the method includes steps S211 to S216, wherein:

[0184] Step S211: Create and instantiate a system management component according to the system description file;

[0185] Step S212: Create a file management component;

[0186] Step S213: Create a device management component using the device management interface of the system management component according to the device description file, and register the device component using the device registration interface of the device management component;

[0187] Step S214: Create an application management component using the application management interface of the system management component according to the software package description file, and create an application component using the application management interface of the application management component;

[0188] Step S215: Deploy the application components to the corresponding device components according to the integration description file, and connect the components in sequence according to the ports;

[0189] Step S216: Run each component to implement the control function and / or protection function of the device.

[0190] Here, the device may be a DC control and protection device, which realizes control and protection functions by operating various components.

[0191] In the embodiments disclosed herein, first, by abstracting each physical board to provide a universal hardware framework, the needs of different devices can be met; second, the control function and / or protection function of the device is realized by software-abstracting each target component, which improves the reusability and portability of the target component, thereby reducing development costs and improving development efficiency; finally, through the hardware and software decoupling design, the complexity of the device is reduced while also reducing costs.

[0192] In some embodiments, when the physical board includes a management board, the multiple target components include a first management component, a first device component, and a first application component; the processing module is also used to: create the first management component, the first device component, and the first application component corresponding to the management board based on the description file corresponding to the management board.

[0193] In some embodiments, the first management component includes a system management component, a first device management component and a first application management component; the processing module is further used to: create and instantiate the system management component; install the first device management component based on the device management interface of the system management component; register the first device component based on the device registration interface of the first device management component; install the first application management component based on the application management interface of the system management component; and create the first application component based on the application creation interface of the first application management component.

[0194] In some implementations, the first management component further includes a file management component, and the processing module is further configured to: create the file management component, and mount the target file system based on a file mounting interface of the file management component.

[0195] In some embodiments, when the physical board includes an application board, the multiple target components include a second management component, a second device component, and a second application component; the processing module is also used to: create a second management component, a second device component, and a second application component corresponding to the application board based on the description file corresponding to the application board.

[0196] In some embodiments, the second management component includes a second device management component and a second application management component; the processing module is also used to: install the second device management component based on the device management interface of the system management component corresponding to the management board; register the second device component based on the device registration interface of the second device management component; install the second application management component based on the application management interface of the system management component; and create the second application component based on the application creation interface of the second application management component.

[0197] In some embodiments, when the physical board includes an interface board, the multiple target components include a third device management component and a third device component; the processing module is also used to: create a third device management component and a third device component corresponding to the interface board based on the description file corresponding to the interface board.

[0198] In some embodiments, the processing module is further configured to: install a third device management component based on a device management interface of a system management component corresponding to the management board; and register the third device component based on a device registration interface of the third device management component.

[0199] In some embodiments, the integration information includes deployment information and connection information; the processing module is also used to: based on the deployment information, deploy the application component to the device component through the application interface of the system management component corresponding to the management board; based on the connection information, establish connections between multiple target components.

[0200] The description of the above system embodiment is similar to the description of the above method embodiment and has similar beneficial effects as the method embodiment. For technical details not disclosed in the system embodiment of the present disclosure, please refer to the description of the method embodiment of the present disclosure for understanding.

[0201] Based on the above embodiments, an embodiment of the present disclosure provides a data processing device, which is applied to a device including multiple physical boards. FIG10 is a schematic diagram of the structure of a data processing device provided by an embodiment of the present disclosure. As shown in FIG10 , the data processing device 100 includes a creation module 101, a connection module 102, and an operation module 103, wherein:

[0202] The creation module 101 is configured to create, for each of the plurality of physical boards, a plurality of target components corresponding to the physical board based on a description file corresponding to the physical board, wherein the target components include at least one of the following: a management component, a device component, and an application component, wherein the management component is configured to manage the device component and the application component, and the application component is deployed in the device component;

[0203] A connection module 102 is used to establish connections between multiple target components based on the integration information;

[0204] The operation module 103 is used to operate multiple target components to implement the control function and / or protection function of the device.

[0205] In some embodiments, when the physical board includes a management board, the multiple target components include a first management component, a first device component, and a first application component; the creation module 101 is also used to: create the first management component, the first device component, and the first application component corresponding to the management board based on the description file corresponding to the management board.

[0206] In some embodiments, the first management component includes a system management component, a first device management component and a first application management component; the creation module 101 is also used to: create and instantiate the system management component; install the first device management component based on the device management interface of the system management component; register the first device component based on the device registration interface of the first device management component; install the first application management component based on the application management interface of the system management component; and create the first application component based on the application creation interface of the first application management component.

[0207] In some implementations, the first management component further includes a file management component, and the creation module 101 is further configured to: create the file management component, and mount the target file system based on a file mounting interface of the file management component.

[0208] In some embodiments, when the physical board includes an application board, the multiple target components include a second management component, a second device component, and a second application component; the creation module 101 is also used to: create the second management component, the second device component, and the second application component corresponding to the application board based on the description file corresponding to the application board.

[0209] In some embodiments, the second management component includes a second device management component and a second application management component; the creation module 101 is also used to: install the second device management component based on the device management interface of the system management component corresponding to the management board; register the second device component based on the device registration interface of the second device management component; install the second application management component based on the application management interface of the system management component; and create the second application component based on the application creation interface of the second application management component.

[0210] In some embodiments, when the physical board includes an interface board, the multiple target components include a third device management component and a third device component; the creation module 101 is also used to: create the third device management component and the third device component corresponding to the interface board based on the description file corresponding to the interface board.

[0211] In some implementations, the creation module 101 is further configured to: install a third device management component based on a device management interface of a system management component corresponding to the management board; and register the third device component based on a device registration interface of the third device management component.

[0212] In some embodiments, the integration information includes deployment information and connection information; the connection module 102 is also used to: based on the deployment information, deploy the application component to the device component through the application interface of the system management component corresponding to the management board; based on the connection information, establish connections between multiple target components.

[0213] The description of the above device embodiment is similar to the description of the above method embodiment, and has similar beneficial effects as the method embodiment. For technical details not disclosed in the device embodiment of the present disclosure, please refer to the description of the method embodiment of the present disclosure for understanding.

[0214] It should be noted that, in the embodiments of the present disclosure, if the above method is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present disclosure is essentially or the part that contributes to the relevant technology can be embodied in the form of a software product, which is stored in a storage medium and includes a number of instructions for enabling an electronic device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the methods of each embodiment of the present disclosure. The aforementioned storage medium includes: various media that can store program codes, such as a U disk, a mobile hard disk, a read-only memory (ROM), a magnetic disk or an optical disk. In this way, the embodiments of the present disclosure are not limited to any specific combination of hardware and software.

[0215] An embodiment of the present disclosure provides an electronic device, including a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and the above method is implemented when the processor executes the computer program.

[0216] The present disclosure provides a computer-readable storage medium having a computer program stored thereon, which implements the above method when executed by a processor. The computer-readable storage medium may be transient or non-transient.

[0217] The present disclosure provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program. When the computer program is read and executed by a computer, some or all of the steps in the above method are implemented. The computer program product can be implemented in hardware, software, or a combination thereof. In one optional embodiment, the computer program product is embodied as a computer storage medium. In another optional embodiment, the computer program product is embodied as a software product, such as a software development kit (SDK).

[0218] It should be noted that FIG11 is a schematic diagram of a hardware entity of an electronic device provided in an embodiment of the present disclosure. As shown in FIG11 , the hardware entity of the electronic device 110 includes: a processor 111, a communication interface 112, and a memory 113, wherein:

[0219] The processor 111 generally controls the overall operations of the electronic device 110 .

[0220] The communication interface 112 enables the electronic device to communicate with other terminals or servers through a network.

[0221] The memory 113 is configured to store instructions and applications executable by the processor 111. It can also cache data to be processed or processed by the processor 111 and various modules in the electronic device 110 (for example, image data, audio data, voice communication data, and video communication data). It can be implemented using flash memory (FLASH) or random access memory (RAM). Data can be transmitted between the processor 111, the communication interface 112, and the memory 113 via the bus 114.

[0222] It should be noted that the description of the above storage medium and device embodiments is similar to the description of the above method embodiments and has similar beneficial effects as the method embodiments. For technical details not disclosed in the storage medium and device embodiments of the present disclosure, please refer to the description of the method embodiments of the present disclosure for understanding.

[0223] It should be understood that references to "one embodiment" or "an embodiment" throughout this specification mean that specific features, structures, or characteristics associated with the embodiment are included in at least one embodiment of the present disclosure. Therefore, the appearance of "in one embodiment" or "in an embodiment" throughout this specification does not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of the present disclosure, the order of execution of the above-mentioned processes does not necessarily indicate a precedence in execution. The execution order of each process should be determined by its function and inherent logic and should not constitute any limitation on the implementation of the embodiments of the present disclosure. The above-mentioned numbers of the embodiments of the present disclosure are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments. It should be noted that, in this document, the terms "comprise," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus comprising a list of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. Without further limitation, the phrase "comprises an..." does not preclude the presence of other identical elements in the process, method, article, or apparatus comprising such elements.

[0224] In the several embodiments provided in the present disclosure, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of units is merely a logical function division. In actual implementation, there may be other division methods, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of devices or units can be electrical, mechanical or other forms.

[0225] The units described above as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; they may be located in one place or distributed across multiple network units; some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment. In addition, the various functional units in the embodiments of the present disclosure may all be integrated into one processing unit, or each unit may be separately used as a unit, or two or more units may be integrated into one unit; the above-mentioned integrated units may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0226] Those skilled in the art will understand that all or part of the steps of implementing the above-mentioned method embodiment can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above-mentioned method embodiment; and the aforementioned storage medium includes: mobile storage devices, read-only memories (ROM), magnetic disks or optical disks, and other media that can store program codes.

[0227] Alternatively, if the above-mentioned integrated unit of the present disclosure is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present disclosure, or the part that contributes to the relevant technology, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for enabling an electronic device (which can be a personal computer, server, or network device, etc.) to execute all or part of the methods of each embodiment of the present disclosure. The aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROMs, magnetic disks, or optical disks.

[0228] The above are only implementation methods of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any technician familiar with this technical field can easily think of changes or replacements within the technical scope disclosed in this disclosure, and they should all be covered by the protection scope of the present disclosure.

Claims

1. A data processing method, applied to a device comprising multiple physical boards, comprising: For each of the plurality of physical boards, creating a plurality of target components corresponding to the physical board based on a description file corresponding to the physical board, the target components comprising at least one of the following: a management component, a device component, and an application component, the management component being used to manage the device component and the application component, and the application component being deployed in the device component; establishing connections between the plurality of target components based on the integration information; The plurality of target components are operated to implement a control function and / or a protection function of the device.

2. The method according to claim 1, wherein In the case where the physical board includes a management board, the plurality of target components include a first management component, a first device component and a first application component; The step of creating a plurality of target components corresponding to the physical board based on the description file corresponding to the physical board includes: Based on the description file corresponding to the management board, a first management component, a first device component, and a first application component corresponding to the management board are created.

3. The method according to claim 2, wherein: The first management component includes a system management component, a first device management component and a first application management component; The step of creating the first management component, the first device component, and the first application component corresponding to the management board includes: Creating and instantiating the system management component; Installing the first device management component based on the device management interface of the system management component; registering the first device component based on a device registration interface of the first device management component; Installing the first application management component based on the application management interface of the system management component; The first application component is created based on the application creation interface of the first application management component.

4. The method according to claim 2 or 3, wherein: The first management component further includes a file management component, and the method further includes: The file management component is created, and the target file system is mounted based on the file mounting interface of the file management component.

5. The method according to any one of claims 1 to 4, wherein In the case where the physical board includes an application board, the plurality of target components include a second management component, a second device component, and a second application component; The step of creating a plurality of target components corresponding to the physical board based on the description file corresponding to the physical board includes: Based on the description file corresponding to the application board, a second management component, a second device component, and a second application component corresponding to the application board are created.

6. The method according to claim 5, wherein: The second management component includes a second device management component and a second application management component; The step of creating a second management component, a second device component, and a second application component corresponding to the application board based on the description file corresponding to the application board includes: Installing the second device management component based on the device management interface of the system management component corresponding to the management board; registering the second device component based on a device registration interface of the second device management component; Installing the second application management component based on the application management interface of the system management component; The second application component is created based on the application creation interface of the second application management component.

7. The method according to any one of claims 1 to 6, wherein In the case where the physical board includes an interface board, the plurality of target components include a third device management component and a third device component; The step of creating a plurality of target components corresponding to the physical board based on the description file corresponding to the physical board includes: Based on the description file corresponding to the interface board, a third device management component and a third device component corresponding to the interface board are created.

8. The method according to claim 7, wherein: The step of creating a third device management component and a third device component corresponding to the interface board includes: Installing the third device management component based on the device management interface of the system management component corresponding to the management board; Register the third device component based on the device registration interface of the third device management component.

9. The method according to any one of claims 1 to 8, wherein The integration information includes deployment information and connection information; and establishing connections between the plurality of target components based on the integration information includes: Based on the deployment information, deploy the application component to the device component through the application interface of the system management component corresponding to the management board; Based on the connection information, connections are established between the multiple target components.

10. A data processing system, comprising a device including a plurality of physical boards and a processing module, wherein: The processing module is configured to: for each physical board among the plurality of physical boards, create a plurality of target components corresponding to the physical board based on a description file corresponding to the physical board, wherein the target components include at least one of the following: a management component, a device component, and an application component, wherein the management component is configured to manage the device component and the application component, and the application component is deployed in the device component; Based on the integration information, connections are established between the multiple target components; and the multiple target components are operated to implement the control function and / or protection function of the device.

11. The system according to claim 10, wherein: The processing module includes an application part, a communication middleware and a driver part, wherein: The application part is used to create multiple target components corresponding to the physical board based on the description file corresponding to the physical board; establish connections between the multiple target components based on the integration information; and run the multiple target components; The communication middleware is used to realize data transmission between the application part and the driver part; The driving part is used to drive the corresponding physical board based on the data transmitted by the communication middleware to realize the control function and / or protection function of the device.

12. The system according to claim 10 or 11, wherein: In the case where the physical board includes a management board, the plurality of target components include a first management component, a first device component and a first application component; The processing module is further configured to create a first management component, a first device component, and a first application component corresponding to the management board based on a description file corresponding to the management board.

13. The system according to claim 12, wherein: The first management component includes a system management component, a first device management component and a first application management component; The processing module is further configured to: create and instantiate the system management component; install the first device management component based on the device management interface of the system management component; and register the first device component based on the device registration interface of the first device management component. Installing the first application management component based on the application management interface of the system management component; The first application component is created based on the application creation interface of the first application management component.

14. The system according to any one of claims 10 to 13, wherein: In the case where the physical board includes an application board, the plurality of target components include a second management component, a second device component, and a second application component; The processing module is further configured to create a second management component, a second device component, and a second application component corresponding to the application board based on a description file corresponding to the application board.

15. The system according to any one of claims 10 to 14, wherein: In the case where the physical board includes an interface board, the plurality of target components include a third device management component and a third device component; The processing module is further configured to create a third device management component and a third device component corresponding to the interface board based on a description file corresponding to the interface board.

16. The system according to any one of claims 10 to 15, wherein: The integration information includes deployment information and connection information; The processing module is further configured to: deploy the application component to the device component through an application interface of a system management component corresponding to a management board based on the deployment information; Based on the connection information, connections are established between the multiple target components.

17. A data processing device, applied to a device comprising multiple physical boards, comprising: a creation module, configured to create, for each physical board among the plurality of physical boards, a plurality of target components corresponding to the physical board based on a description file corresponding to the physical board, wherein the target components include at least one of the following: a management component, a device component, and an application component, wherein the management component is configured to manage the device component and the application component, and the application component is deployed in the device component; a connection module, configured to establish connections between the plurality of target components based on the integration information; An operation module is used to operate the multiple target components to implement the control function and / or protection function of the device.

18. An electronic device comprising a processor and a memory, wherein the memory stores a computer program executable on the processor, and the processor implements the method according to any one of claims 1 to 9 when executing the computer program.

19. A computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

20. A computer program product comprising a computer program or instructions, wherein when the computer program or instructions are executed by a processor, the method according to any one of claims 1 to 9 is implemented.

Images