WO2020259163A1 - 设备部署方法及装置、设备运行方法及电子设备 - Google Patents

设备部署方法及装置、设备运行方法及电子设备 Download PDF

Info

Publication number
WO2020259163A1
WO2020259163A1 PCT/CN2020/092020 CN2020092020W WO2020259163A1 WO 2020259163 A1 WO2020259163 A1 WO 2020259163A1 CN 2020092020 W CN2020092020 W CN 2020092020W WO 2020259163 A1 WO2020259163 A1 WO 2020259163A1
Authority
WO
WIPO (PCT)
Prior art keywords
module
function
interface
library
functional
Prior art date
Application number
PCT/CN2020/092020
Other languages
English (en)
French (fr)
Inventor
丁振江
金文波
Original Assignee
深圳开立生物医疗科技股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 深圳开立生物医疗科技股份有限公司 filed Critical 深圳开立生物医疗科技股份有限公司
Publication of WO2020259163A1 publication Critical patent/WO2020259163A1/zh

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment

Definitions

  • This application relates to the field of computer technology, and more specifically, to a device deployment method, device, electronic device, storage medium, and a device operation method, electronic device, and storage medium.
  • the software driver interface that is connected to the hardware will be adapted.
  • the interface of the Linux operating system By directly calling the interface of the Linux operating system to implement related functions, it will not be affected by hardware changes.
  • the existing technical solution can solve the above-mentioned problem of time-consuming and labor-intensive application software development, it still has the following problem: Although the operating system interface remains unchanged, the combined functional process or interface parameters will change, which will cause the application Corresponding changes in software, and at the same time, in order to distinguish from the old products, the development of new functions is generally re-developed by adding branches.
  • the purpose of this application is to provide a device deployment method and device, an electronic device and a computer-readable storage medium, which effectively saves the development and maintenance costs of application software and improves the reusability of functional modules.
  • this application provides a device deployment method, including:
  • the function module library is deployed between the application software and the operating system, so that when the application software calls the function interface corresponding to the interface index, it uses the adaptation of the module adaptation layer to access or call the corresponding hardware Functional modules under the platform.
  • Optional also includes:
  • the common module includes any one or any combination of I2C module, SPI module, UART module, USB module, NET module, CRC algorithm module and Log module.
  • the corresponding functional modules of the device hardware functions required by the encapsulation under different hardware platforms include:
  • the interface of the operating system is called to encapsulate the required device hardware functions into corresponding functional modules.
  • the interface index is a header file
  • the construction of the interface index in the function module library includes:
  • the header file is stored in the header file directory of the function module library, so that the application software calls the function interface corresponding to the interface declaration based on the interface declaration of the header file in the header file directory.
  • the constructing a module adaptation layer in the function module library includes:
  • the corresponding relationship between the identification information of the device and the functional module under the corresponding hardware platform is constructed, so that the module adaptation layer finds the module object of the functional module under the corresponding hardware platform based on the identification information of the device.
  • the identification information is an identification number preset for the target device.
  • Optional also includes:
  • model object Construct a global object for storing pointers to specific model objects of the device in the functional module library; wherein the model object includes module objects of all modules, and records storage information of log files and device identification information , For the module adaptation layer to use.
  • Optional also includes:
  • the required system functions of the operating system are encapsulated as system modules in the function module library, so that the function modules can access or call the system modules.
  • the operating system is a linux operating system
  • the function module library is a dynamic library.
  • this application provides a device deployment device, including:
  • the packaging module is used to encapsulate the function modules corresponding to the required device hardware functions under different hardware platforms, and save the corresponding function modules under the different hardware platforms in a pre-created function module library;
  • the deployment module is used to deploy the function module library between the application software and the operating system, so that the application software uses the adaptation of the module adaptation layer when calling the function interface corresponding to the interface index Access or call the function modules under the corresponding hardware platform.
  • the encapsulation module is further used to: encapsulate the common functions of the device as a common module, and save the common module in a public directory under the function module library, so that the function module is based on the public directory pair The public module is called.
  • the common module includes any one or any combination of I2C module, SPI module, UART module, USB module, NET module, CRC algorithm module and Log module.
  • the corresponding functional modules of the device hardware functions required by the encapsulation under different hardware platforms include:
  • the interface of the operating system is called to encapsulate the required device hardware functions into corresponding functional modules.
  • the interface index is a header file
  • the construction of the interface index in the function module library includes:
  • the header file is stored in the header file directory of the function module library, so that the application software calls the function interface corresponding to the interface declaration based on the interface declaration of the header file in the header file directory.
  • the constructing a module adaptation layer in the function module library includes:
  • the corresponding relationship between the identification information of the device and the functional module under the corresponding hardware platform is constructed, so that the module adaptation layer finds the module object of the functional module under the corresponding hardware platform based on the identification information of the device.
  • the identification information is an identification number set by the target device in advance.
  • the building module is also used for:
  • model object Construct a global object for storing pointers to specific model objects of the device in the functional module library; wherein the model object includes module objects of all modules, and records storage information of log files and device identification information , For the module adaptation layer to use.
  • packaging module is also used for:
  • the required system functions of the operating system are encapsulated as system modules in the function module library, so that the function modules can access or call the system modules.
  • the operating system is a linux operating system
  • the function module library is a dynamic library.
  • this application provides a method for operating a device.
  • the device includes application software, an operating system, and a function module library.
  • the function module library is set between the application software and the operating system, and The library encapsulates the function modules corresponding to the required device hardware functions under different hardware platforms, and the function module library is provided with an interface index and a module adaptation layer, and the operation method includes:
  • the application software calls the functional interface corresponding to the interface index
  • the function interface accesses or calls the function module under the corresponding hardware platform based on the adaptation of the module adaptation layer.
  • the interface index is a header file
  • the header file is stored in a header file directory of the function module library
  • the application software calls the functional interface corresponding to the interface declaration based on the interface declaration of the header file in the header file directory.
  • the module adaptation layer stores the correspondence between the identification information of the device and the functional modules under the corresponding hardware platform; the adaptation of the module adaptation layer includes:
  • the module adaptation layer finds the module object of the functional module under the corresponding hardware platform based on the identification information of the device.
  • the application software specifies the functional modules that need to be accessed or called.
  • the application software specifies the function module that needs to be accessed or called, it further includes:
  • the application software uses the initialization interface of the function module library to initialize all different function modules under the corresponding hardware platform that can realize the hardware functions of the same device.
  • the identification information is an identification number preset for the target device.
  • public modules corresponding to the public functions of the device are encapsulated in the public directory of the function module library; the operation method further includes:
  • the function module accesses or calls the public module based on the public directory.
  • the common module includes any one or any combination of I2C module, SPI module, UART module, USB module, NET module, CRC algorithm module and Log module.
  • system modules corresponding to the required system functions of the operating system are encapsulated in the function module library; the operation method further includes:
  • the function module accesses or calls the system module.
  • the function interface accesses or calls the function module under the corresponding hardware platform based on the adaptation of the module adaptation layer, it further includes:
  • the module adaptation layer records the access or calling operation information in a log file after completing the adaptation.
  • the method before calling the functional interface corresponding to the interface index, the method further includes:
  • the application software uses the initialization interface provided by the function module library to initialize all module objects of the device.
  • the initialization interface initializes the module objects of all modules of the device based on the identification information of the device.
  • the operating system is a linux operating system
  • the function module library is a dynamic library.
  • an electronic device including:
  • Memory used to store computer programs
  • the processor is used to implement the steps of any device deployment method disclosed above when executing the computer program.
  • an electronic device including:
  • Memory used to store computer programs
  • the processor is used to implement the steps of any one of the device operating methods disclosed above when the computer program is executed.
  • the present application provides a computer-readable storage medium having a computer program stored on the computer-readable storage medium, and when the computer program is executed by a processor, it implements any of the device deployment methods disclosed above. step.
  • the present application provides a computer-readable storage medium having a computer program stored on the computer-readable storage medium, and when the computer program is executed by a processor, it implements any of the foregoing disclosed device operating methods. step.
  • a device deployment method includes: encapsulating the required device hardware functions corresponding to the functional modules under different hardware platforms, and saving the corresponding functional modules under the different hardware platforms to the advance Create a function module library; create an interface index and a module adaptation layer in the function module library; deploy the function module library between the application software and the operating system, so that the application software calls the interface index When the corresponding function interface is used, the adaptation of the module adaptation layer is used to access or call the function module under the corresponding hardware platform.
  • the application software can access or call the function modules under the corresponding hardware platform in the function module library by calling the function interface corresponding to the interface index to realize the corresponding equipment Hardware function. Therefore, on the one hand, when the internal deployment of the electronic device is completed by the above-mentioned device deployment method, if the device introduces new hardware or is replaced with new hardware, the original hardware functions of the device have been encapsulated by means of functional modules. In the function module library, therefore, during development, only the function module of the new hardware function needs to be encapsulated in the function module library, and the application software only needs to develop new interface codes for the new hardware or the newly replaced hardware.
  • the original interface code of the application software does not need to be changed, which greatly reduces the development and maintenance costs of the application software; on the other hand, because the required equipment hardware functions are packaged and developed, the hardware functions will be differentiated in a targeted manner.
  • the corresponding functional modules under the hardware platform are encapsulated in the functional module library. Therefore, if new products on different hardware platforms are developed, when the functional module library is developed or transplanted, the functional modules of the same function on the old hardware platform do not need to undergo any changes. It can be used directly under another hardware platform, which can improve the reusability of related functional modules, and can save or reduce the process of code familiarization and problem debugging after source code transplantation, thereby effectively reducing labor and time costs.
  • This application also discloses a device deployment device, an electronic device, a storage medium and a device operation method, electronic device and storage medium, which can also achieve the above technical effects.
  • FIG. 1 is a flowchart of a device deployment method disclosed in an embodiment of the application
  • Figure 2 is a schematic diagram of a specific device deployment disclosed in an embodiment of the application.
  • FIG. 3 is a structural diagram of another device deployment apparatus disclosed in an embodiment of the application.
  • FIG. 4 is a flowchart of a device operation method disclosed in an embodiment of the application.
  • FIG. 5 is a schematic diagram of a specific implementation manner of a device operation method disclosed in an embodiment of this application.
  • FIG. 6 is a flow chart of using a functional module library by an application software disclosed in an embodiment of the application
  • FIG. 7 is a structural diagram of an electronic device disclosed in an embodiment of the application.
  • FIG. 8 is a structural diagram of another electronic device disclosed in an embodiment of the application.
  • the embodiment of the present application discloses a device deployment method, which effectively saves the development and maintenance costs of application software, and improves the reusability of functional modules.
  • a flowchart of a device deployment method disclosed in an embodiment of the present application, as shown in Fig. 1, includes:
  • S101 Encapsulate the function modules corresponding to the required device hardware functions under different hardware platforms, and save the corresponding function modules under the different hardware platforms in a pre-created function module library;
  • the device hardware functions required by the device are encapsulated in corresponding functional modules under different hardware platforms.
  • the corresponding audio modules under different platforms such as ARM audio modules and X86 audio modules can be packaged, and then the packaged function modules can be saved in a pre-created function module library.
  • the hardware function of the device in this embodiment may specifically refer to a set of functional logic and/or operation logic that can use the related hardware modules of the device to achieve related functional effects, which can be characterized in the form of source code (non-low-level driver ), so that it can be packaged as a corresponding function module, such as the audio function mentioned above.
  • the audio function needs to be realized by using relevant audio hardware modules, which can be characterized by source code and can be packaged as a corresponding audio function module By calling or accessing the audio function module, the relevant audio hardware module can be operated to realize audio functions such as volume adjustment and audio playback.
  • the aforementioned functional module library can be specifically designed as a dynamic library.
  • Dynamic libraries can be accessed or used by multiple applications at the same time, which is conducive to resource sharing.
  • the foregoing process of encapsulating corresponding functional modules under different hardware platforms may include, but is not limited to: encapsulating required device hardware functions into corresponding functional modules by invoking an interface of the operating system.
  • this embodiment can also encapsulate the common functions of the device as a common module, and save the common module to the function module library.
  • the common module may include, but is not limited to, any one or a combination of any of the I2C module, SPI module, UART module, USB module, NET module, CRC algorithm module, and Log module.
  • this embodiment may also encapsulate the required system functions of the operating system as system modules in the function module library, so that the function modules can access or call the system modules.
  • the file management module is packaged as a system module and saved in the function module library, so that the function module can access or call the file management module.
  • a corresponding interface index can be created based on the interface of the functional module, so that the corresponding functional interface can be called based on the interface index.
  • the interface index may be a header file
  • the process of constructing the interface index in the function module library may include but is not limited to: constructing a functional interface corresponding to the required device hardware function and corresponding to the functional interface
  • the header file store the header file in the header file directory of the function module library.
  • the above process of creating a module adaptation layer in the functional module library may include, but is not limited to: constructing the correspondence between the identification information of the device and the functional modules under the corresponding hardware platform, so as to find out based on the identification information of the device
  • the module object of the function module under the corresponding hardware platform can pre-set corresponding identification information for the device, such as identification information such as ID number, so that based on the pre-built correspondence between the device identification information and the functional module, the corresponding identification information can be directly used to obtain the corresponding identification information.
  • the module object of the function module under the hardware platform is not limited to: constructing the correspondence between the identification information of the device and the functional modules under the corresponding hardware platform, so as to find out based on the identification information of the device
  • the module object of the function module under the corresponding hardware platform can pre-set corresponding identification information for the device, such as identification information such as ID number, so that based on the pre-built correspondence between the device identification information and the functional module, the corresponding identification information can be directly used to obtain
  • the module adaptation layer of this embodiment can also specifically store the correspondence between the device identifier and the hardware platform, and the correspondence between the hardware platform and the functional modules under the platform.
  • the hardware platform corresponding to the current device can be determined through the identification information of the device, and then the functional module corresponding to the hardware platform can be obtained.
  • this embodiment deploys the above function module library between the application software and the operating system, so that the application software is
  • the function interface can be used to find the function module under the corresponding hardware platform based on the adaptation of the module adaptation layer, and the application software can access or call the function module under the corresponding hardware platform.
  • the module will drive the corresponding hardware module to implement related functions after receiving the visit or call.
  • the aforementioned operating system may be a linux operating system.
  • a device deployment method includes: encapsulating the required device hardware functions corresponding to functional modules under different hardware platforms, and saving the corresponding functional modules under different hardware platforms to pre-created In the function module library; create the interface index and module adaptation layer in the function module library; deploy the function module library between the application software and the operating system, so that the application software can use the module adaptation when calling the function interface corresponding to the interface index.
  • the configuration layer is adapted to access or call the function modules under the corresponding hardware platform.
  • the application software can access or call the function modules under the corresponding hardware platform in the function module library by calling the function interface corresponding to the interface index to realize the corresponding equipment Hardware functions. Therefore, on the one hand, when the internal deployment of the electronic device is completed through the above-mentioned device deployment method, if the device introduces new hardware or replaces new hardware, the original hardware functions of the device have passed the functional module Encapsulated in the functional module library, so that, when developing, the functional module library only needs to encapsulate the functional modules of new hardware functions, and the application software only needs to develop new interface codes for new hardware or newly replaced hardware.
  • the original interface code of the application software does not need to be changed, regardless of whether it is developed by adding branches or not, it can greatly reduce the development and maintenance costs of the application software; on the other hand, because the required equipment hardware functions are encapsulated During development, the functional modules corresponding to the hardware functions under different hardware platforms will be packaged into the functional module library in a targeted manner. Therefore, if new products on different hardware platforms are developed, when the functional module library is developed or transplanted, the old hardware The functional modules of the same function on the platform can be used directly under another hardware platform without any changes, which can improve the reusability of related functional modules, and can save or reduce code familiarity and problem debugging after source code migration Process, which can effectively reduce labor costs and time costs.
  • FIG. 2 is a schematic diagram of a specific device deployment provided by this embodiment.
  • the function module library is deployed between the application software and the operating system, and the required device hardware functions, System functions, common functions, etc. are encapsulated into corresponding function modules and stored in the function module library, and the module adaptation layer and interface index are constructed in the function module library, so that the application software can use the adaptation call interface index corresponding to the module adaptation layer The interface of the corresponding hardware platform to access or call the function module.
  • this embodiment can also construct a global object in the function module library for storing pointers to specific model objects of the device; among them, the model object includes all modules Module object, and records storage information of log files and device identification information for use by the module adaptation layer.
  • this embodiment can create a pointer to a specific model object.
  • the model object is specifically used to characterize the type of device, that is, the hardware platform corresponding to the device.
  • a global object is further created to store the above pointer, and the global object is used to record the device. Therefore, the module adaptation layer can access the global object to obtain the specific model object through the pointer, and can read the identification information of the device.
  • the aforementioned global object may also store a log file, and the function module library can be debugged using the information recorded in the log file.
  • the following describes a device deployment apparatus provided in an embodiment of the present application.
  • the device deployment device described below and the device deployment method described above may refer to each other.
  • FIG. 3 a structural diagram of a device deployment apparatus provided by an embodiment of the present application, as shown in FIG. 3, includes:
  • the encapsulation module 201 is used to encapsulate the function modules corresponding to the required device hardware functions under different hardware platforms, and save the corresponding function modules under the different hardware platforms in a pre-created function module library;
  • the construction module 202 is used to construct an interface index and a module adaptation layer in the functional module library;
  • the deployment module 203 is used to deploy the function module library between the application software and the operating system, so that the application software uses the adaptation of the module adaptation layer when calling the function interface corresponding to the interface index To access or call the functional modules under the corresponding hardware platform.
  • the above-mentioned encapsulation module can also be used to: encapsulate the common functions of the device as a common module, and save the common module in a public directory under the function module library, So that the function module calls the public module based on the public directory.
  • the above-mentioned common module may include any one or several of I2C module, SPI module, UART module, USB module, NET module, CRC algorithm module and Log module combination.
  • the corresponding functional modules of the device hardware functions required by the encapsulation under different hardware platforms include:
  • the interface of the operating system is called to encapsulate the required device hardware functions into corresponding functional modules.
  • the interface index is a header file
  • the construction of the interface index in the functional module library includes:
  • the header file is stored in the header file directory of the function module library, so that the application software calls the function interface corresponding to the interface declaration based on the interface declaration of the header file in the header file directory.
  • the constructing a module adaptation layer in the functional module library includes:
  • the corresponding relationship between the identification information of the device and the functional module under the corresponding hardware platform is constructed, so that the module adaptation layer finds the module object of the functional module under the corresponding hardware platform based on the identification information of the device.
  • the identification information is an identification number set by the target device in advance.
  • the building module can also be used for:
  • model object Construct a global object for storing pointers to specific model objects of the device in the functional module library; wherein the model object includes module objects of all modules, and records storage information of log files and device identification information , For the module adaptation layer to use.
  • the packaging module can also be used for:
  • the required system functions of the operating system are encapsulated as system modules in the function module library, so that the function modules can access or call the system modules.
  • the operating system may be specifically a linux operating system
  • the function module library may be specifically a dynamic library.
  • the embodiment of the present application also discloses a device operation method, which can realize the operation of the device on the basis of the above-mentioned device deployment.
  • the device includes application software, an operating system, and a functional module library. Between the application software and the operating system, the function module library encapsulates the function modules corresponding to the required device hardware functions under different hardware platforms, and the function module library is provided with an interface index and a module adaptation layer, As shown in Figure 4, the operation method includes:
  • the device hardware functions required to be implemented by the device are encapsulated in advance in corresponding functional modules under different hardware platforms, the encapsulated functional modules are saved in a pre-created functional module library, and the functional modules
  • the library is set between the application software and the operating system.
  • the aforementioned functional module library can be specifically designed as a dynamic library. Dynamic libraries can be accessed or used by multiple applications at the same time, which is conducive to resource sharing.
  • the aforementioned operating system may be a linux operating system.
  • the application software calls the corresponding function interface through the interface index, and the function interface can realize the access or invocation of the function module under the corresponding hardware platform based on the adaptation of the module adaptation layer.
  • the above interface index can be a header file.
  • the functional interface corresponding to the required device hardware function and the header file corresponding to the functional interface can be constructed in advance, and the header file can be stored in the header file directory of the function module library, so that the application software can be based on the header file
  • the interface declaration of the header file in the directory calls the corresponding functional interface.
  • the application software before calling the functional interface corresponding to the interface index, can initialize all the module objects of the device by using the initialization interface provided by the functional module library.
  • the foregoing initialization interface may initialize the module objects of all modules of the device based on the identification information of the device.
  • the function interface accesses or calls the function module under the corresponding hardware platform based on the adaptation of the module adaptation layer.
  • this embodiment pre-builds the correspondence between the identification information of the device and the functional module under the corresponding hardware platform and stores it in the module adaptation layer, so that the correspondence between the pre-built device identification information and the functional module can be Access or call the function modules under the corresponding hardware platform.
  • the identification information of the device may be a type of identification information such as an ID number preset for the device.
  • the application software can specify the required access or call Functional modules. That is, if there are multiple functional modules corresponding to the current device identification information, the module that is finally confirmed to be accessed or called can be selected from the multiple functional modules.
  • the function modules that need to be accessed or called by the application software can be specified in a preset manner, or the selection interface can be provided to the user through the display screen to receive the user's selection instruction and determine the module that needs to be accessed or called .
  • the above-mentioned process of initializing all module objects of the device before calling the function interface corresponding to the interface index can be delayed until the application software specifies the function module that needs to be accessed or called, and then use the function module library
  • the initialization interface of the corresponding hardware platform initializes different functional modules that can implement the same device hardware functions, thereby avoiding the need to initialize multiple unnecessary functional modules when the same module with different implementations exists under one hardware platform .
  • the function module library in this embodiment may also include a public directory, in which function modules corresponding to the public functions of the device are encapsulated, so that the function modules can access or call the public modules based on the public directory.
  • the above-mentioned public modules may include, but are not limited to, any one or a combination of any of the I2C module, SPI module, UART module, USB module, NET module, CRC algorithm module, and Log module. It can be understood that this embodiment can also encapsulate the required system functions of the operating system as system modules in the function module library, and the function modules can access or call the system modules to implement corresponding system functions.
  • this embodiment can further access or call the function module under the corresponding hardware platform after the function interface accesses or calls the function module under the corresponding hardware platform based on the adaptation of the module adaptation layer.
  • the called operation information is recorded in the log file, so as to use the operation record to realize the historical record tracking and debugging of the function module library.
  • the device operating method provided by this application includes application software, an operating system, and a functional module library.
  • the functional module library is set between the application software and the operating system, and the required hardware functions of the device are encapsulated.
  • the corresponding function module under the hardware platform, and the function module library is provided with an interface index and a module adaptation layer.
  • the operation method includes: the application software calls the function interface corresponding to the interface index; the function interface is based on the adaptation of the module adaptation layer To access or call the functional modules under the corresponding hardware platform.
  • the application software can access or call the function module under the corresponding hardware platform in the function module library by calling the function interface corresponding to the interface index, and the corresponding device hardware function can be realized, effectively saving the development and maintenance cost of the application software. , Improve the reusability of functional modules.
  • the audio function interface can be called based on the interface declaration of the audio header file of the function module library.
  • the audio function interface will find the hardware of all audio function modules under different hardware platforms and the current function software based on the adaptation of the module adaptation layer.
  • the audio function module corresponding to the platform, such as the ARM audio module thus realizes the access or invocation of the corresponding audio function module by the above-mentioned application software, thereby realizing the audio function.
  • FIG. 6 is a flow chart of using the functional module library by the application software provided by an embodiment of the application, and the flow chart reflects the device operation method of this embodiment.
  • the application software needs to initialize the function before calling the function of the function module library, and the initialization interface is provided by the function module library. Specifically, the ID parameter of the identification device is passed into the initialization interface, and then the application software will analyze the ID parameter and confirm the hardware platform used by the project device based on the ID parameter; if the analysis is successful, the device will be initialized through the ID parameter All module objects contained in. If the initialization is successful, the function interface declared in the header file is used to access the related function module.
  • the function interface declared in the header file finds the specific function module under the corresponding hardware platform through the module adaptation layer, and then The function module performs the access operation, thereby driving the hardware device or hardware module related to the function module to realize the relevant function, and at the same time storing the information recorded in the operation process in the log file under the platform.
  • the initialization of these functional modules can be delayed to the module preprocessing stage. The software initializes after specifying the specific functional module to be accessed.
  • FIG. 7 a structural diagram of an electronic device provided by an embodiment of the application, as shown in FIG. 7, includes:
  • the memory 11 is used to store computer programs
  • the processor 12 is configured to implement the steps of the device deployment method or the device operation method provided in the foregoing embodiments when executing the computer program.
  • the memory 11 includes a non-volatile storage medium and an internal memory.
  • the non-volatile storage medium stores an operating system and computer-readable instructions
  • the internal memory provides an environment for the operation of the operating system and the computer-readable instructions in the non-volatile storage medium.
  • the processor 12 may be a central processing unit (CPU), controller, microcontroller, microprocessor or other data processing chip, which provides computing and control capabilities for electronic devices, and executes the The computer program stored in the memory 11 can implement the device deployment method or device operating method disclosed in the foregoing embodiments.
  • the electronic device further includes:
  • the input interface 13 is connected to the processor 12 and is used to obtain externally imported computer programs, parameters, and instructions, and store them in the memory 11 under the control of the processor 12.
  • the input interface 13 can be connected to an input device to receive parameters or instructions manually input by the user.
  • the input device may be a touch layer covered on the display screen, a button, a trackball, or a touch pad provided on the terminal housing, or a keyboard, a touch pad, or a mouse.
  • the display unit 14 is connected to the processor 12 and is used for displaying the data processed by the processor 12 and for displaying a visualized user interface.
  • the display unit 14 may be an LED display, a liquid crystal display, a touch liquid crystal display, an OLED (Organic Light-Emitting Diode, organic light-emitting diode) touch device, etc.
  • the network port 15 is connected to the processor 12 and is used to communicate with external terminal devices.
  • the communication technology used in the communication connection can be wired communication technology or wireless communication technology, such as mobile high-definition link technology (MHL), universal serial bus (USB), high-definition multimedia interface (HDMI), wireless fidelity technology (WiFi), Bluetooth communication technology, low-power Bluetooth communication technology, communication technology based on IEEE802.11s, etc.
  • FIG. 8 only shows an electronic device with components 11-15. Those skilled in the art can understand that the structure shown in FIG. 8 does not constitute a limitation on the electronic device, and may include fewer or more components than shown. Components, or combinations of certain components, or different component arrangements.
  • equipment or electronic equipment of the present application may be medical equipment, such as ultrasonic diagnostic equipment or electronic endoscopic equipment.
  • This application also provides a computer-readable storage medium, which may include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic Various media that can store program codes, such as discs or optical discs.
  • the storage medium stores a computer program that, when executed by a processor, implements the steps of the device deployment method or the device operation method provided in the foregoing embodiments.
  • the application software can access or call the function modules under the corresponding hardware platform in the function module library by calling the function interface corresponding to the interface index to realize the corresponding equipment Hardware functions. Therefore, on the one hand, when the internal deployment of the electronic device is completed through the above-mentioned device deployment method, if the device introduces new hardware or replaces new hardware, the original hardware functions of the device have passed the functional module Encapsulated in the functional module library, so that, when developing, the functional module library only needs to encapsulate the functional modules of new hardware functions, and the application software only needs to develop new interface codes for new hardware or newly replaced hardware.
  • the original interface code of the application software does not need to be changed, which greatly reduces the development and maintenance costs of the application software; on the other hand, because the required equipment hardware functions are packaged and developed, the hardware will be targeted
  • the function modules corresponding to the functions under different hardware platforms are encapsulated in the function module library. Therefore, if new products of different hardware platforms are developed, when the function module library is developed or transplanted, the function modules of the same function on the old hardware platform do not need to go through Any changes can be directly used under another hardware platform, which can improve the reusability of related functional modules, and can save or reduce the process of code familiarization and problem debugging after source code migration, which can effectively reduce labor costs and Time costs.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

一种设备部署方法及装置、设备运行方法及电子设备,设备部署方法包括:封装所需的设备硬件功能在不同硬件平台下对应的功能模块,并将不同硬件平台下对应的功能模块均保存至预先创建的功能模块库中;在功能模块库中创建接口索引和模块适配层;将功能模块库部署于应用软件与操作系统之间,以便应用软件在调用接口索引所对应的功能接口时,利用模块适配层的适配来访问或调用相应硬件平台下的功能模块。本申请中基于模块适配层的适配,应用软件通过调用接口索引所对应的功能接口对功能模块库中相应硬件平台下的功能模块进行访问或调用,即可实现相应的设备硬件功能,有效节约了应用软件的开发和维护成本,提高了功能模块的可复用性。

Description

设备部署方法及装置、设备运行方法及电子设备
本申请要求于2019年06月27日提交中国专利局、申请号为201910569174.2、发明名称为“设备部署方法及装置、设备运行方法及电子设备”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机技术领域,更具体地说,涉及一种设备部署方法、装置、电子设备、存储介质及一种设备运行方法、电子设备和存储介质。
背景技术
随着人们对产品的需求日益增加,产品厂家需要经常为现有产品增加新的功能或直接开发新的产品取代老产品。为了保证新功能或新产品快速推向市场,技术人员一般在现有产品的基础上进行更改,一是为了保证产品的稳定,二是可以有效节约开发成本。
产品功能的新增一般涉及到软件功能的增加,对于一些比较高级的功能需要引入高性能的硬件,这种情况下,应用软件会有较大变动,从而增加了研发成本,延迟了新功能的推出。
为了解决硬件变动导致应用软件开发耗时耗力的问题,和硬件对接的软件驱动接口会做适配,通过直接调用Linux操作系统的接口来实现相关功能便可不受硬件变动的影响。然而,现有技术方案虽然可以解决上述应用软件开发耗时耗力的问题,但仍然存在如下问题:操作系统接口虽然不变,但是组合完成的功能流程或者接口参数会存在变化,这样会导致应用软件的相应变化,同时为了与旧产品进行区分,一般会通过增加分支的形式重新进行新功能的开发,随着功能需求的不断叠加,分支会呈爆炸式增长,这极大地增加了维护成本;如果开发不同平台的新产品,需要将旧平台中的模块源码移植到新平台上,移植过程中代码熟悉与问题调试会消耗较多时间和人力,不利于相同模块的复用。
因此,如何解决上述问题是本领域技术人员需要重点关注的。
发明内容
本申请的目的在于提供一种设备部署方法、装置及一种电子设备和一种计算机可读存储介质,有效节约了应用软件的开发和维护成本,提高了功能模块的可复用性。
为实现上述目的,本申请提供了一种设备部署方法,包括:
封装所需的设备硬件功能在不同硬件平台下对应的功能模块,并将所述不同硬件平台下对应的功能模块均保存至预先创建的功能模块库中;
在所述功能模块库中创建接口索引和模块适配层;
将所述功能模块库部署于应用软件与操作系统之间,以便所述应用软件在调用所述接口索引所对应的功能接口时,利用所述模块适配层的适配来访问或调用相应硬件平台下的功能模块。
可选的,还包括:
将设备公用功能封装为公用模块,并将所述公用模块保存至所述功能模块库下的公用目录,以便所述功能模块基于所述公用目录对所述公用模块进行访问或调用。
可选的,所述公用模块包括I2C模块、SPI模块、UART模块、USB模块、NET模块、CRC算法模块及Log日志模块中任一项或任几项组合。
可选的,所述封装所需的设备硬件功能在不同硬件平台下对应的功能模块包括:
调用所述操作系统的接口将所述所需的设备硬件功能封装为相应的功能模块。
可选的,所述接口索引为头文件,所述在所述功能模块库中构建接口索引包括:
构建与所述所需的设备硬件功能相对应的功能接口以及与所述功能接口相对应的头文件;
将所述头文件存放于所述功能模块库的头文件目录中,以便所述应用软件基于所述头文件目录中的头文件的接口声明,调用所述接口声明所对应的功能接口。
可选的,所述在所述功能模块库中构建模块适配层包括:
构建设备的标识信息与相应硬件平台下的功能模块之间的对应关系,以便所述模块适配层基于所述设备的标识信息找到相应硬件平台下的功能模块的模块对象。
可选的,所述标识信息为预先为所述目标设备设置的标识号。
可选的,还包括:
在所述功能模块库中构建用于存放设备具体机型对象的指针的全局对象;其中,所述机型对象包括有所有模块的模块对象,并记录有日志文件和设备的标识信息的存放信息,以供所述模块适配层使用。
可选的,还包括:
在所述功能模块库中将所需的所述操作系统的系统功能封装为系统模块,以便所述功能模块对所述系统模块进行访问或调用。
可选的,所述操作系统为linux操作系统,所述功能模块库为动态库。
为实现上述目的,本申请提供了一种设备部署装置,包括:
封装模块,用于封装所需的设备硬件功能在不同硬件平台下对应的功能模块,并将所述不同硬件平台下对应的功能模块均保存至预先创建的功能模块库中;
构建模块,用于在所述功能模块库中构建接口索引和模块适配层;
部署模块,用于将所述功能模块库部署于应用软件与操作系统之间,以便所述应用软件在调用所述接口索引所对应的功能接口时,利用所述模块适配层的适配来访问或调用相应硬件平台下的功能模块。
可选的,所述封装模块还用于:将设备公用功能封装为公用模块,并将所述公用模块保存至所述功能模块库下的公用目录,以便所述功能模块基于所述公用目录对所述公用模块进行调用。
可选的,所述公用模块包括I2C模块、SPI模块、UART模块、USB模块、NET模块、CRC算法模块及Log日志模块中任一项或任几项组合。
可选的,所述封装所需的设备硬件功能在不同硬件平台下对应的功能模块包括:
调用所述操作系统的接口将所述所需的设备硬件功能封装为相应的功能模块。
可选的,所述接口索引为头文件,所述在所述功能模块库中构建接口索引包括:
构建与所述所需的设备硬件功能相对应的功能接口以及与所述功能接口相对应的头文件;
将所述头文件存放于所述功能模块库的头文件目录中,以便所述应用软件基于所述头文件目录中的头文件的接口声明,调用所述接口声明所对应的功能接口。
可选的,所述在所述功能模块库中构建模块适配层包括:
构建设备的标识信息与相应硬件平台下的功能模块之间的对应关系,以便所述模块适配层基于所述设备的标识信息找到相应硬件平台下的功能模块的模块对象。
可选的,所述标识信息预先为所述目标设备设置的标识号。
可选的,所述构建模块还用于:
在所述功能模块库中构建用于存放设备具体机型对象的指针的全局对象;其中,所述机型对象包括有所有模块的模块对象,并记录有日志文件和设备的标识信息的存放信息,以供所述模块适配层使用。
可选的,所述封装模块还用于:
在所述功能模块库中将所需的所述操作系统的系统功能封装为系统模块,以便所述功能模块对所述系统模块进行访问或调用。
可选的,所述操作系统为linux操作系统,所述功能模块库为动态库。
为实现上述目的,本申请提供了一种设备运行方法,所述设备包括应用软件、操作系统和功能模块库,所述功能模块库设置于所述应用软件和操作系统之间,所述功能模块库内封装有所需的设备硬件功能在不同硬件平台下对应的功能模块,且所述功能模块库内设置有接口索引和模块适配层,所述运行方法包括:
所述应用软件调用所述接口索引所对应的功能接口;
所述功能接口基于所述模块适配层的适配来访问或调用相应硬件平台下的功能模块。
可选的,所述接口索引为头文件,所述头文件存放于所述功能模块库 的头文件目录中;所述应用软件调用所述接口索引所对应的功能接口包括:
所述应用软件基于所述头文件目录中的头文件的接口声明,调用所述接口声明所对应的功能接口。
可选的,所述模块适配层保存有设备的标识信息与相应硬件平台下的功能模块之间的对应关系;所述模块适配层的适配包括:
所述模块适配层基于所述设备的标识信息找到相应硬件平台下的功能模块的模块对象。
可选的,当所述设备的标识信息与相应硬件平台下的可实现相同设备硬件功能的不同功能模块均相对应时,由所述应用软件指定所需要访问或调用的功能模块。
可选的,所述应用软件指定所需要访问或调用的功能模块之后还包括:
所述应用软件利用所述功能模块库的初始化接口对所述相应硬件平台下的可实现相同设备硬件功能的不同功能模块都进行初始化。
可选的,所述标识信息为预先为所述目标设备设置的标识号。
可选的,所述功能模块库的公用目录中封装有与设备公用功能相对应的公用模块;所述运行方法还包括:
所述功能模块基于所述公用目录对所述公用模块进行访问或调用。
可选的,所述公用模块包括I2C模块、SPI模块、UART模块、USB模块、NET模块、CRC算法模块及Log日志模块中任一项或任几项组合。
可选的,所述功能模块库中封装有与所需的所述操作系统的系统功能相对应的系统模块;所述运行方法还包括:
所述功能模块对所述系统模块进行访问或调用。
可选的,所述功能接口基于所述模块适配层的适配来访问或调用相应硬件平台下的功能模块之后,还包括:
所述模块适配层在完成适配后将所述访问或调用的操作信息记录于日志文件中。
可选的,所述调用所述接口索引所对应的功能接口之前,还包括:
所述应用软件利用所述功能模块库所提供的初始化接口对所述设备的所有模块对象进行初始化。
可选的,所述初始化接口基于设备的标识信息对所述设备的所有模块的模块对象进行初始化。
可选的,所述操作系统为linux操作系统,所述功能模块库为动态库。
为实现上述目的,本申请提供了一种电子设备,包括:
存储器,用于存储计算机程序;
处理器,用于执行所述计算机程序时实现前述公开的任一种设备部署方法的步骤。
为实现上述目的,本申请提供了一种电子设备,包括:
存储器,用于存储计算机程序;
处理器,用于执行所述计算机程序时实现前述公开的任一种设备运行方法的步骤。
为实现上述目的,本申请提供了一种计算机可读存储介质,所述计算机可读存储介质上存储有计算机程序,所述计算机程序被处理器执行时实现前述公开的任一种设备部署方法的步骤。
为实现上述目的,本申请提供了一种计算机可读存储介质,所述计算机可读存储介质上存储有计算机程序,所述计算机程序被处理器执行时实现前述公开的任一种设备运行方法的步骤。
通过以上方案可知,本申请提供的一种设备部署方法,包括:封装所需的设备硬件功能在不同硬件平台下对应的功能模块,并将所述不同硬件平台下对应的功能模块均保存至预先创建的功能模块库中;在所述功能模块库中创建接口索引和模块适配层;将所述功能模块库部署于应用软件与操作系统之间,以便所述应用软件在调用所述接口索引所对应的功能接口时,利用所述模块适配层的适配来访问或调用相应硬件平台下的功能模块。由上可知,本申请中基于模块适配层的适配,应用软件通过调用接口索引所对应的功能接口对功能模块库中相应硬件平台下的功能模块进行访问或调用,即可实现相应的设备硬件功能。因此,一方面,当电子设备内部通过上述设备部署方法完成部署后,若该设备引入了新的硬件或更换了新的硬件,则由于该设备原有的各硬件功能已经通过功能模块的方式封装在功能模块库中,从而,在开发时,功能模块库中只需封装入新的硬件功能的 功能模块,应用软件只需针对新的硬件或新更换的硬件开发新的接口代码即可,而应用软件原有的接口代码可以不用变化,这极大地降低了应用软件的开发和维护成本;另一方面,由于所需的设备硬件功能在封装开发时,都会针对性地将该硬件功能在不同硬件平台下所对应的功能模块封装入功能模块库中,从而,如果开发不同硬件平台的新产品,在开发或移植功能模块库时,旧硬件平台上相同功能的各功能模块无需经过任何更改便可以直接在另一个硬件平台下使用,则可提高相关功能模块的可复用性,并可省去或减少源码移植后代码熟悉和问题调试的过程,由此可有效降低人力成本和时间成本。
本申请还公开了一种设备部署装置、电子设备、存储介质及设备运行方法、电子设备和存储介质,同样能实现上述技术效果。
应当理解的是,以上的一般描述和后文的细节描述仅是示例性的,并不能限制本申请。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案,下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本申请的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1为本申请实施例公开的一种设备部署方法的流程图;
图2为本申请实施例公开的一种具体的设备部署示意图;
图3为本申请实施例公开的另一种设备部署装置的结构图;
图4为本申请实施例公开的一种设备运行方法的流程图;
图5为本申请实施例公开的设备运行方法的一种具体实施方式的示意图;
图6为本申请实施例公开的一种应用软件对于功能模块库的使用流程图;
图7为本申请实施例公开的一种电子设备的结构图;
图8为本申请实施例公开的另一种电子设备的结构图。
具体实施方式
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例仅仅是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本申请保护的范围。
在现有技术中,为了解决硬件变动导致应用软件开发耗时耗力的问题,和硬件对接的软件驱动接口会做适配,通过直接调用Linux操作系统的接口来实现相关功能便可不受硬件变动的影响。然而,为了与旧产品进行区分,一般会通过增加分支的形式重新进行新功能的开发,极大地增加了维护成本;如果开发不同平台的新产品,需要将旧平台中的模块源码移植到新平台上,移植过程中代码熟悉与问题调试会消耗时间和人力,不利于相同模块的复用。
因此,本申请实施例公开了一种设备部署方法,有效节约了应用软件的开发和维护成本,提高了功能模块的可复用性。
参见图1,本申请实施例公开的一种设备部署方法的流程图,如图1所示,包括:
S101:封装所需的设备硬件功能在不同硬件平台下对应的功能模块,并将所述不同硬件平台下对应的功能模块均保存至预先创建的功能模块库中;
本实施例中,将设备所需实现的设备硬件功能在不同硬件平台下对应的功能模块进行封装。例如,若设备需要实现音频功能,则可将ARM音频模块、X86音频模块等不同平台下对应的音频模块进行封装,进而将封装后的功能模块保存至预先创建的功能模块库中。应当理解的是,本实施例的设备硬件功能具体可以是指可使用设备的相关硬件模块来实现相关功能效果的一套功能逻辑和/或操作逻辑,其可以源码的形式表征(非底层驱 动程序),从而其可以封装为相应的功能模块,比如上文中提及的音频功能,该音频功能需要利用相关音频硬件模块才能实现,其可通过源码的方式表征并可以被封装为相应的音频功能模块,通过对该音频功能模块的调用或访问便可对相关音频硬件模块进行操作来实现音量调节、音频播放等音频功能。
优选的,上述功能模块库可以具体设计为动态库。动态库可由多个应用程序同时访问或使用,有利于实现资源的共享。
具体地,上述对不同硬件平台下对应的功能模块进行封装的过程可以包括但不限于:通过调用操作系统的接口将所需的设备硬件功能封装为相应的功能模块。
除了封装所需的设备硬件功能在不同硬件平台下对应的功能模块,作为一种优选实施方式,本实施例还可以将设备公用功能封装为公用模块,并将公用模块保存至功能模块库下的公用目录下,以便功能模块基于公用目录对公用模块进行访问或调用。其中,公用模块可以包括但不限于I2C模块、SPI模块、UART模块、USB模块、NET模块、CRC算法模块及Log日志模块中任一项或任几项组合。
另外,本实施例还可以在功能模块库中将所需的操作系统的系统功能封装为系统模块,以便功能模块对系统模块进行访问或调用。例如,将文件管理模块封装为系统模块并保存至功能模块库中,从而功能模块可以对该文件管理模块进行访问或调用。
S102:在所述功能模块库中创建接口索引和模块适配层;
本步骤中,可以基于功能模块的接口创建对应的接口索引,以便基于接口索引调用对应的功能接口。在一种具体实施方式下,接口索引可以为头文件,在功能模块库中构建接口索引的过程可以包括但不限于:构建与所需的设备硬件功能相对应的功能接口以及与功能接口相对应的头文件;将头文件存放于功能模块库的头文件目录中。通过上述过程,应用软件在调用功能接口时,可以查询头文件目录,并基于头文件目录中头文件的接口声明,调用接口声明所对应的功能接口。
本实施例中,上述在功能模块库中创建模块适配层的过程可以包括但不限于:构建设备的标识信息与相应硬件平台下的功能模块之间的对应关系,以便基于设备的标识信息找到相应硬件平台下的功能模块的模块对象。可以理解的是,本实施例可以预先为设备设置对应的标识信息,例如ID号等标识信息,从而基于预先构建的设备标识信息与功能模块之间的对应关系,可以直接利用标识信息获取到对应硬件平台下功能模块的模块对象。
需要指出的是,本实施例模块适配层也可以具体保存设备标识与硬件平台之间的对应关系,以及硬件平台与其平台下的功能模块之间的对应关系。在这种实施方式下,本实施例可以通过设备的标识信息确定当前设备所对应的硬件平台,进而获取该硬件平台对应的功能模块。
S103:将所述功能模块库部署于应用软件与操作系统之间,以便所述应用软件在调用所述接口索引所对应的功能接口时,利用所述模块适配层的适配来访问或调用相应硬件平台下的功能模块。
在将功能模块封装保存至功能模块库,并在功能模块库中创建好接口索引和模块适配层之后,本实施例将上述功能模块库部署于应用软件与操作系统之间,从而应用软件在调用相应接口索引所对应的功能接口时,可以使该功能接口基于模块适配层的适配找到相应硬件平台下的功能模块,实现应用软件对相应硬件平台下功能模块的访问或调用,而功能模块在接受访问或调用后会驱动相应的硬件模块实现相关功能。其中,上述操作系统可以为linux操作系统。
通过以上方案可知,本申请提供的一种设备部署方法,包括:封装所需的设备硬件功能在不同硬件平台下对应的功能模块,并将不同硬件平台下对应的功能模块均保存至预先创建的功能模块库中;在功能模块库中创建接口索引和模块适配层;将功能模块库部署于应用软件与操作系统之间,以便应用软件在调用接口索引所对应的功能接口时,利用模块适配层的适配来访问或调用相应硬件平台下的功能模块。由上可知,本申请中基于模块适配层的适配,应用软件通过调用接口索引所对应的功能接口对功能模块库中相应硬件平台下的功能模块进行访问或调用,即可实现相应的设备硬件功能,因此,一方面,当电子设备内部通过上述设备部署方法完成部 署后,若该设备引入了新的硬件或更换了新的硬件,则由于该设备原有的各硬件功能已经通过功能模块的方式封装在功能模块库中,从而,在开发时,功能模块库中只需封装入新的硬件功能的功能模块,应用软件只需针对新的硬件或新更换的硬件开发新的接口代码即可,而应用软件原有的接口代码可以不用变化,无论是否采用添加分支的方式进行开发,都能够极大地降低应用软件的开发和维护成本;另一方面,由于所需的设备硬件功能在封装开发时,都会针对性地将该硬件功能在不同硬件平台下所对应的功能模块封装入功能模块库中,从而,如果开发不同硬件平台的新产品,在开发或移植功能模块库时,旧硬件平台上相同功能的各功能模块无需经过任何更改便可以直接在另一个硬件平台下使用,则可提高相关功能模块的可复用性,并可省去或减少源码移植后代码熟悉和问题调试的过程,由此可有效降低人力成本和时间成本。
图2为本实施例提供的一种具体的设备部署示意图,参见图2所示,将功能模块库部署于应用软件和操作系统之间,通过调用操作系统的接口将所需的设备硬件功能、系统功能、公用功能等封装成对应的功能模块保存至功能模块库中,并在功能模块库中构建模块适配层以及接口索引,从而应用软件可以利用模块适配层的适配调用接口索引对应的接口,实现对应硬件平台下功能模块的访问或调用。
在上述实施例的基础上,作为一种优选实施方式,本实施例还可以在功能模块库中构建用于存放设备具体机型对象的指针的全局对象;其中,机型对象包括有所有模块的模块对象,并记录有日志文件和设备的标识信息的存放信息,以供模块适配层使用。
具体地,本实施例可以创建指向具体机型对象的指针,机型对象具体用于表征设备的类型,即设备对应的硬件平台,进一步创建全局对象用于存放上述指针,并利用全局对象记录设备的标识信息,从而模块适配层可访问该全局对象以通过指针获取到具体机型对象,并可以读取设备的标识信息。另外,上述全局对象还可以存储有日志文件,能够利用日志文件记录的信息对功能模块库进行调试。
下面对本申请实施例提供的一种设备部署装置进行介绍,下文描述的一种设备部署装置与上文描述的一种设备部署方法可以相互参照。
参见图3,本申请实施例提供的一种设备部署装置的结构图,如图3所示,包括:
封装模块201,用于封装所需的设备硬件功能在不同硬件平台下对应的功能模块,并将所述不同硬件平台下对应的功能模块均保存至预先创建的功能模块库中;
构建模块202,用于在所述功能模块库中构建接口索引和模块适配层;
部署模块203,用于将所述功能模块库部署于应用软件与操作系统之间,以便所述应用软件在调用所述接口索引所对应的功能接口时,利用所述模块适配层的适配来访问或调用相应硬件平台下的功能模块。
在上述实施例的基础上,作为一种优选实施方式,上述封装模块还可以用于:将设备公用功能封装为公用模块,并将所述公用模块保存至所述功能模块库下的公用目录,以便所述功能模块基于所述公用目录对所述公用模块进行调用。
在上述实施例的基础上,作为一种优选实施方式,上述公用模块可以包括I2C模块、SPI模块、UART模块、USB模块、NET模块、CRC算法模块及Log日志模块中任一项或任几项组合。
在上述实施例的基础上,作为一种优选实施方式,所述封装所需的设备硬件功能在不同硬件平台下对应的功能模块包括:
调用所述操作系统的接口将所述所需的设备硬件功能封装为相应的功能模块。
在上述实施例的基础上,作为一种优选实施方式,所述接口索引为可以头文件,所述在所述功能模块库中构建接口索引包括:
构建与所述所需的设备硬件功能相对应的功能接口以及与所述功能接口相对应的头文件;
将所述头文件存放于所述功能模块库的头文件目录中,以便所述应用软件基于所述头文件目录中的头文件的接口声明,调用所述接口声明所对应的功能接口。
在上述实施例的基础上,作为一种优选实施方式,所述在所述功能模块库中构建模块适配层包括:
构建设备的标识信息与相应硬件平台下的功能模块之间的对应关系,以便所述模块适配层基于所述设备的标识信息找到相应硬件平台下的功能模块的模块对象。
在上述实施例的基础上,作为一种优选实施方式,所述标识信息预先为所述目标设备设置的标识号。
在上述实施例的基础上,作为一种优选实施方式,所述构建模块还可以用于:
在所述功能模块库中构建用于存放设备具体机型对象的指针的全局对象;其中,所述机型对象包括有所有模块的模块对象,并记录有日志文件和设备的标识信息的存放信息,以供所述模块适配层使用。
在上述实施例的基础上,作为一种优选实施方式,所述封装模块还可以用于:
在所述功能模块库中将所需的所述操作系统的系统功能封装为系统模块,以便所述功能模块对所述系统模块进行访问或调用。
在上述实施例的基础上,作为一种优选实施方式,所述操作系统可以具体为linux操作系统,所述功能模块库可以具体为动态库。
关于上述模块更加具体的工作过程可参考前述实施例公开的相应内容,在此不再进行赘述。
此外,本申请实施例还公开了一种设备运行方法,能够在上述设备部署的基础上实现设备的运行,所述设备包括应用软件、操作系统和功能模块库,所述功能模块库设置于所述应用软件和操作系统之间,所述功能模块库内封装有所需的设备硬件功能在不同硬件平台下对应的功能模块,且所述功能模块库内设置有接口索引和模块适配层,参见图4所示,所述运行方法包括:
S301:所述应用软件调用所述接口索引所对应的功能接口;
需要说明的是,本实施例预先将设备所需实现的设备硬件功能在不同硬件平台下对应的功能模块进行封装,将封装后的功能模块保存至预先创建的功能模块库中,并将功能模块库设置于应用软件和操作系统之间。优选的,上述功能模块库可以具体设计为动态库。动态库可由多个应用程序同时访问或使用,有利于实现资源的共享。其中,上述操作系统可以为linux操作系统。
本实施例中,应用软件通过接口索引调用对应的功能接口,进而功能接口可以基于模块适配层的适配实现相应硬件平台下功能模块的访问或调用。
上述接口索引可以为头文件。本实施例可以预先构建与所需的设备硬件功能相对应的功能接口以及与功能接口相对应的头文件,并将头文件存放于功能模块库的头文件目录中,从而应用软件可以基于头文件目录中头文件的接口声明调用对应的功能接口。
在具体实施中,调用接口索引所对应的功能接口之前,应用软件可以利用功能模块库所提供的初始化接口对设备的所有模块对象进行初始化。具体地,上述初始化接口可以基于设备的标识信息对设备的所有模块的模块对象进行初始化。
S302:所述功能接口基于所述模块适配层的适配来访问或调用相应硬件平台下的功能模块。
本步骤中,本实施例预先构建设备的标识信息与相应硬件平台下的功能模块之间的对应关系存入模块适配层,从而基于预先构建的设备标识信息与功能模块之间的对应关系可以访问或调用相应硬件平台下的功能模块。其中,设备的标识信息可以为预先为设备设置的ID号等类型的标识信息。
需要指出的是,当基于模块适配层的适配查找到当前设备标识信息与相应硬件平台下可实现相同设备硬件功能的不同功能模块均相对应时,可以由应用软件指定所需要访问或调用的功能模块。也即,若与当前设备标识信息对应的功能模块有多个时,可以从多个功能模块中选择最终确认访问或调用的模块。具体地,由应用软件指定所需要访问或调用的功能模块 可以通过预先设定的方式进行指定,或可以通过显示屏向用户提供选择界面,以接收用户的选择指令,确定需要访问或调用的模块。
作为一种优选实施方式,上述在调用接口索引所对应的功能接口之前对设备的所有模块对象进行初始化的过程,可以延迟到应用软件指定所需要访问或调用的功能模块之后,再利用功能模块库的初始化接口对相应硬件平台下的可实现相同设备硬件功能的不同功能模块进行初始化,从而避免在一种硬件平台下存在不同实现的相同模块的情况下需要初始化多个不必要的功能模块的情况。
进一步地,本实施例中功能模块库中还可以包括公用目录,其中封装有与设备公用功能对应的功能模块,从而功能模块可以基于公用目录对公用模块进行访问或调用。其中,上述公用模块可以包括但不限于I2C模块、SPI模块、UART模块、USB模块、NET模块、CRC算法模块及Log日志模块中任一项或任几项组合。可以理解的是,本实施例还可以在功能模块库中将所需的操作系统的系统功能封装为系统模块,功能模块对系统模块进行访问或调用实现对应的系统功能。
在上述实施例的基础上,作为一种优选实施方式,本实施例在功能接口基于所述模块适配层的适配来访问或调用相应硬件平台下的功能模块之后,还可以进一步将访问或调用的操作信息记录于日志文件中,以便利用操作记录实现功能模块库的历史记录追踪和调试。
由上可知,本申请提供的设备运行方法,所述设备包括应用软件、操作系统和功能模块库,功能模块库设置于应用软件和操作系统之间,其中封装有所需的设备硬件功能在不同硬件平台下对应的功能模块,且功能模块库内设置有接口索引和模块适配层,所述运行方法包括:应用软件调用接口索引所对应的功能接口;功能接口基于模块适配层的适配来访问或调用相应硬件平台下的功能模块。也即,应用软件通过调用接口索引所对应的功能接口对功能模块库中相应硬件平台下的功能模块进行访问或调用,即可实现相应的设备硬件功能,有效节约了应用软件的开发和维护成本,提高了功能模块的可复用性。
如图5所示,在本实施例提供的设备运行方法的一种具体实施方式中,不同硬件平台下的应用软件,如ARM功能软件、X86功能软件,若应用软件,比如ARM功能软件需要实现音频功能时,可以基于功能模块库的音频头文件的接口声明调用音频功能接口,该音频功能接口会基于模块适配层的适配找到不同硬件平台下所有音频功能模块中与当前功能软件的硬件平台对应的音频功能模块,比如ARM音频模块,由此实现上述应用软件对相应音频功能模块的访问或者调用,进而实现音频功能。
图6为本申请实施例提供的一种应用软件对于功能模块库的使用流程图,该流程图反映了本实施例的设备运行方法。如图6所示,应用软件调用功能模块库的功能之前需要进行初始化功能,初始化接口由功能模块库提供。具体地,向初始化接口中传入标识设备的ID参数,然后应用软件会解析该ID参数,并基于该ID参数确认项目设备所使用的硬件平台;若解析成功,则通过该ID参数来初始化设备中包含的所有模块对象。若初始化成功,则使用头文件中声明的功能接口对相关功能模块进行访问,在该过程中,头文件中声明的功能接口经过模块适配层找到相应硬件平台下的具体功能模块,并对该功能模块进行访问操作,由此驱动与该功能模块相关的硬件设备或硬件模块实现相关功能,同时将操作过程记录的信息存放在该平台下的日志文件中。在具体实施中,可能一个硬件平台下存在不同实现的多个可实现相同功能的功能模块,为了能准确的匹配对应功能模块,可以将这些功能模块的初始化工作延迟到模块预处理阶段,由应用软件指定需要访问的具体功能模块后进行初始化。
本申请还提供了一种电子设备,参见图7,本申请实施例提供的一种电子设备的结构图,如图7所示,包括:
存储器11,用于存储计算机程序;
处理器12,用于执行所述计算机程序时可以实现上述实施例所提供的设备部署方法的步骤或设备运行方法的步骤。
具体的,存储器11包括非易失性存储介质、内存储器。该非易失性存储介质存储有操作系统和计算机可读指令,该内存储器为非易失性存储介 质中的操作系统和计算机可读指令的运行提供环境。处理器12在一些实施例中可以是一中央处理器(Central Processing Unit,CPU)、控制器、微控制器、微处理器或其他数据处理芯片,为电子设备提供计算和控制能力,执行所述存储器11中保存的计算机程序时,可以实现前述实施例公开的设备部署方法或设备运行方法。
在上述实施例的基础上,作为优选实施方式,参见图8,所述电子设备还包括:
输入接口13,与处理器12相连,用于获取外部导入的计算机程序、参数和指令,经处理器12控制保存至存储器11中。该输入接口13可以与输入装置相连,接收用户手动输入的参数或指令。该输入装置可以是显示屏上覆盖的触摸层,也可以是终端外壳上设置的按键、轨迹球或触控板,也可以是键盘、触控板或鼠标等。
显示单元14,与处理器12相连,用于显示处理器12处理的数据以及用于显示可视化的用户界面。该显示单元14可以为LED显示器、液晶显示器、触控式液晶显示器以及OLED(Organic Light-Emitting Diode,有机发光二极管)触摸器等。
网络端口15,与处理器12相连,用于与外部各终端设备进行通信连接。该通信连接所采用的通信技术可以为有线通信技术或无线通信技术,如移动高清链接技术(MHL)、通用串行总线(USB)、高清多媒体接口(HDMI)、无线保真技术(WiFi)、蓝牙通信技术、低功耗蓝牙通信技术、基于IEEE802.11s的通信技术等。
图8仅示出了具有组件11-15的电子设备,本领域技术人员可以理解的是,图8示出的结构并不构成对电子设备的限定,可以包括比图示更少或者更多的部件,或者组合某些部件,或者不同的部件布置。
需要指出的是,本申请的设备或电子设备可以是医疗设备,比如超声诊断设备或电子内窥设备。
本申请还提供了一种计算机可读存储介质,该存储介质可以包括:U盘、移动硬盘、只读存储器(Read-Only Memory,ROM)、随机存取存 储器(Random Access Memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。该存储介质上存储有计算机程序,所述计算机程序被处理器执行时实现上述实施例所提供的设备部署方法的步骤或设备运行方法的步骤。
由上可知,本申请中基于模块适配层的适配,应用软件通过调用接口索引所对应的功能接口对功能模块库中相应硬件平台下的功能模块进行访问或调用,即可实现相应的设备硬件功能,因此,一方面,当电子设备内部通过上述设备部署方法完成部署后,若该设备引入了新的硬件或更换了新的硬件,则由于该设备原有的各硬件功能已经通过功能模块的方式封装在功能模块库中,从而,在开发时,功能模块库中只需封装入新的硬件功能的功能模块,应用软件只需针对新的硬件或新更换的硬件开发新的接口代码即可,而应用软件原有的接口代码可以不用变化,这极大地降低了应用软件的开发和维护成本;另一方面,由于所需的设备硬件功能在封装开发时,都会针对性地将该硬件功能在不同硬件平台下所对应的功能模块封装入功能模块库中,从而,如果开发不同硬件平台的新产品,在开发或移植功能模块库时,旧硬件平台上相同功能的各功能模块无需经过任何更改便可以直接在另一个硬件平台下使用,则可提高相关功能模块的可复用性,并可省去或减少源码移植后代码熟悉和问题调试的过程,由此可有效降低人力成本和时间成本。
说明书中各个实施例采用递进的方式描述,每个实施例重点说明的都是与其他实施例的不同之处,各个实施例之间相同相似部分互相参见即可。对于实施例公开的系统而言,由于其与实施例公开的方法相对应,所以描述的比较简单,相关之处参见方法部分说明即可。应当指出,对于本技术领域的普通技术人员来说,在不脱离本申请原理的前提下,还可以对本申请进行若干改进和修饰,这些改进和修饰也落入本申请权利要求的保护范围内。
还需要说明的是,在本说明书中,诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来,而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且, 术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素,而且还包括没有明确列出的其他要素,或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下,由语句“包括一个……”限定的要素,并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。

Claims (37)

  1. 一种设备部署方法,其特征在于,包括:
    封装所需的设备硬件功能在不同硬件平台下对应的功能模块,并将所述不同硬件平台下对应的功能模块均保存至预先创建的功能模块库中;
    在所述功能模块库中创建接口索引和模块适配层;
    将所述功能模块库部署于应用软件与操作系统之间,以便所述应用软件在调用所述接口索引所对应的功能接口时,利用所述模块适配层的适配来访问或调用相应硬件平台下的功能模块。
  2. 根据权利要求1所述的设备部署方法,其特征在于,还包括:
    将设备公用功能封装为公用模块,并将所述公用模块保存至所述功能模块库下的公用目录,以便所述功能模块基于所述公用目录对所述公用模块进行访问或调用。
  3. 根据权利要求2所述的设备部署方法,其特征在于,所述公用模块包括I2C模块、SPI模块、UART模块、USB模块、NET模块、CRC算法模块及Log日志模块中任一项或任几项组合。
  4. 根据权利要求1所述的设备部署方法,其特征在于,所述封装所需的设备硬件功能在不同硬件平台下对应的功能模块包括:
    调用所述操作系统的接口将所述所需的设备硬件功能封装为相应的功能模块。
  5. 根据权利要求1所述的设备部署方法,其特征在于,所述接口索引为头文件,所述在所述功能模块库中构建接口索引包括:
    构建与所述所需的设备硬件功能相对应的功能接口以及与所述功能接口相对应的头文件;
    将所述头文件存放于所述功能模块库的头文件目录中,以便所述应用软件基于所述头文件目录中的头文件的接口声明,调用所述接口声明所对应的功能接口。
  6. 根据权利要求1所述的设备部署方法,其特征在于,所述在所述功能模块库中构建模块适配层包括:
    构建设备的标识信息与相应硬件平台下的功能模块之间的对应关系,以便所述模块适配层基于所述设备的标识信息找到相应硬件平台下的功能模块的模块对象。
  7. 根据权利要求6所述的设备部署方法,其特征在于,所述标识信息为预先为所述目标设备设置的标识号。
  8. 根据权利要求1所述的设备部署方法,其特征在于,还包括:
    在所述功能模块库中构建用于存放设备具体机型对象的指针的全局对象;其中,所述机型对象包括有所有模块的模块对象,并记录有日志文件和设备的标识信息的存放信息,以供所述模块适配层使用。
  9. 根据权利要求1所述的设备部署方法,其特征在于,还包括:
    在所述功能模块库中将所需的所述操作系统的系统功能封装为系统模块,以便所述功能模块对所述系统模块进行访问或调用。
  10. 根据权利要求1至9任一项所述的设备部署方法,其特征在于,所述操作系统为linux操作系统,所述功能模块库为动态库。
  11. 一种设备部署装置,其特征在于,包括:
    封装模块,用于封装所需的设备硬件功能在不同硬件平台下对应的功能模块,并将所述不同硬件平台下对应的功能模块均保存至预先创建的功能模块库中;
    构建模块,用于在所述功能模块库中构建接口索引和模块适配层;
    部署模块,用于将所述功能模块库部署于应用软件与操作系统之间,以便所述应用软件在调用所述接口索引所对应的功能接口时,利用所述模块适配层的适配来访问或调用相应硬件平台下的功能模块。
  12. 根据权利要求11所述的设备部署装置,其特征在于,所述封装模块还用于:将设备公用功能封装为公用模块,并将所述公用模块保存至所述功能模块库下的公用目录,以便所述功能模块基于所述公用目录对所述公用模块进行调用。
  13. 根据权利要求12所述的设备部署装置,其特征在于,所述公用模块包括I2C模块、SPI模块、UART模块、USB模块、NET模块、CRC算法模块及Log日志模块中任一项或任几项组合。
  14. 根据权利要求11所述的设备部署装置,其特征在于,所述封装所需的设备硬件功能在不同硬件平台下对应的功能模块包括:
    调用所述操作系统的接口将所述所需的设备硬件功能封装为相应的功能模块。
  15. 根据权利要求11所述的设备部署装置,其特征在于,所述接口索引为头文件,所述在所述功能模块库中构建接口索引包括:
    构建与所述所需的设备硬件功能相对应的功能接口以及与所述功能接口相对应的头文件;
    将所述头文件存放于所述功能模块库的头文件目录中,以便所述应用软件基于所述头文件目录中的头文件的接口声明,调用所述接口声明所对应的功能接口。
  16. 根据权利要求11所述的设备部署装置,其特征在于,所述在所述功能模块库中构建模块适配层包括:
    构建设备的标识信息与相应硬件平台下的功能模块之间的对应关系,以便所述模块适配层基于所述设备的标识信息找到相应硬件平台下的功能模块的模块对象。
  17. 根据权利要求16所述的设备部署装置,其特征在于,所述标识信息预先为所述目标设备设置的标识号。
  18. 根据权利要求11所述的设备部署装置,其特征在于,所述构建模块还用于:
    在所述功能模块库中构建用于存放设备具体机型对象的指针的全局对象;其中,所述机型对象包括有所有模块的模块对象,并记录有日志文件和设备的标识信息的存放信息,以供所述模块适配层使用。
  19. 根据权利要求11所述的设备部署方法,其特征在于,所述封装模块还用于:
    在所述功能模块库中将所需的所述操作系统的系统功能封装为系统模块,以便所述功能模块对所述系统模块进行访问或调用。
  20. 根据权利要求1至19任一项所述的设备部署装置,其特征在于,所述操作系统为linux操作系统,所述功能模块库为动态库。
  21. 一种设备运行方法,其特征在于,所述设备包括应用软件、操作系统和功能模块库,所述功能模块库设置于所述应用软件和操作系统之间,所述功能模块库内封装有所需的设备硬件功能在不同硬件平台下对应的功能模块,且所述功能模块库内设置有接口索引和模块适配层,所述运行方法包括:
    所述应用软件调用所述接口索引所对应的功能接口;
    所述功能接口基于所述模块适配层的适配来访问或调用相应硬件平台下的功能模块。
  22. 根据权利要求21所述的设备运行方法,其特征在于,所述接口索引为头文件,所述头文件存放于所述功能模块库的头文件目录中;所述应用软件调用所述接口索引所对应的功能接口包括:
    所述应用软件基于所述头文件目录中的头文件的接口声明,调用所述接口声明所对应的功能接口。
  23. 根据权利要求21所述的设备运行方法,其特征在于,所述模块适配层保存有设备的标识信息与相应硬件平台下的功能模块之间的对应关系;所述模块适配层的适配包括:
    所述模块适配层基于所述设备的标识信息找到相应硬件平台下的功能模块的模块对象。
  24. 根据权利要求23所述的设备运行方法,其特征在于,当所述设备的标识信息与相应硬件平台下的可实现相同设备硬件功能的不同功能模块均相对应时,由所述应用软件指定所需要访问或调用的功能模块。
  25. 根据权利要求24所述的设备运行方法,其特征在于,所述应用软件指定所需要访问或调用的功能模块之后还包括:
    所述应用软件利用所述功能模块库的初始化接口对所述相应硬件平台下的可实现相同设备硬件功能的不同功能模块都进行初始化。
  26. 根据权利要求23所述的设备运行方法,其特征在于,所述标识信息为预先为所述目标设备设置的标识号。
  27. 根据权利要求21所述的设备运行方法,其特征在于,所述功能模块库的公用目录中封装有与设备公用功能相对应的公用模块;所述运行方法还包括:
    所述功能模块基于所述公用目录对所述公用模块进行访问或调用。
  28. 根据权利要求27所述的设备运行方法,其特征在于,所述公用模块包括I2C模块、SPI模块、UART模块、USB模块、NET模块、CRC算法模块及Log日志模块中任一项或任几项组合。
  29. 根据权利要求21所述的设备运行方法,其特征在于,所述功能模块库中封装有与所需的所述操作系统的系统功能相对应的系统模块;所述运行方法还包括:
    所述功能模块对所述系统模块进行访问或调用。
  30. 根据权利要求21所述的设备运行方法,其特征在于,所述功能接口基于所述模块适配层的适配来访问或调用相应硬件平台下的功能模块之后,还包括:
    所述模块适配层在完成适配后将所述访问或调用的操作信息记录于日志文件中。
  31. 根据权利要求21所述的设备运行方法,其特征在于,所述调用所述接口索引所对应的功能接口之前,还包括:
    所述应用软件利用所述功能模块库所提供的初始化接口对所述设备的所有模块对象进行初始化。
  32. 根据权利要求31所述的设备运行方法,其特征在于,所述初始化接口基于设备的标识信息对所述设备的所有模块的模块对象进行初始化。
  33. 根据权利要求21至32任一项所述的设备运行方法,其特征在于,所述操作系统为linux操作系统,所述功能模块库为动态库。
  34. 一种电子设备,其特征在于,包括:
    存储器,用于存储计算机程序;
    处理器,用于执行所述计算机程序时实现如权利要求1至10任一项所述设备部署方法的步骤。
  35. 一种电子设备,其特征在于,包括:
    存储器,用于存储计算机程序;
    处理器,用于执行所述计算机程序时实现如权利要求21至33任一项所述设备运行方法的步骤。
  36. 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质上存储有计算机程序,所述计算机程序被处理器执行时实现如权利要求1至10任一项所述设备部署方法的步骤。
  37. 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质上存储有计算机程序,所述计算机程序被处理器执行时实现如权利要求21至33任一项所述设备运行方法的步骤。
PCT/CN2020/092020 2019-06-27 2020-05-25 设备部署方法及装置、设备运行方法及电子设备 WO2020259163A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910569174.2A CN110275716A (zh) 2019-06-27 2019-06-27 设备部署方法及装置、设备运行方法及电子设备
CN201910569174.2 2019-06-27

Publications (1)

Publication Number Publication Date
WO2020259163A1 true WO2020259163A1 (zh) 2020-12-30

Family

ID=67962477

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/092020 WO2020259163A1 (zh) 2019-06-27 2020-05-25 设备部署方法及装置、设备运行方法及电子设备

Country Status (2)

Country Link
CN (1) CN110275716A (zh)
WO (1) WO2020259163A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110275716A (zh) * 2019-06-27 2019-09-24 深圳开立生物医疗科技股份有限公司 设备部署方法及装置、设备运行方法及电子设备
CN111198766B (zh) * 2020-01-06 2021-02-05 中科驭数(北京)科技有限公司 数据库访问操作部署方法、数据库访问方法及装置
CN112346715A (zh) * 2020-11-19 2021-02-09 中国北方车辆研究所 一种嵌入式软件模块化设计方法
CN114527983A (zh) * 2020-11-23 2022-05-24 中移互联网有限公司 一种基于中间件的接口适配方法、装置及电子设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6738829B1 (en) * 2000-10-16 2004-05-18 Wind River Systems, Inc. System and method for implementing a generic enhanced network driver
CN102662842A (zh) * 2012-04-11 2012-09-12 贵州航天风华精密设备有限公司 一种基于Java平台的航天器测试软件构架及其测试方法
CN104333808A (zh) * 2014-11-14 2015-02-04 复旦大学 用于Android及Linux智能电视机上的通用播放器
CN106649164A (zh) * 2016-12-29 2017-05-10 南威软件股份有限公司 一种硬件接口管理方法
CN110275716A (zh) * 2019-06-27 2019-09-24 深圳开立生物医疗科技股份有限公司 设备部署方法及装置、设备运行方法及电子设备

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6907482B2 (en) * 2001-12-13 2005-06-14 Microsoft Corporation Universal graphic adapter for interfacing with hardware and means for encapsulating and abstracting details of the hardware
CN101193260A (zh) * 2007-03-23 2008-06-04 深圳市同洲电子股份有限公司 Ip机顶盒通用软件平台系统及基于此系统的ip机顶盒
CN101986694A (zh) * 2010-10-29 2011-03-16 广东星海数字家庭产业技术研究院有限公司 一种基于linux系统的数字电视系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6738829B1 (en) * 2000-10-16 2004-05-18 Wind River Systems, Inc. System and method for implementing a generic enhanced network driver
CN102662842A (zh) * 2012-04-11 2012-09-12 贵州航天风华精密设备有限公司 一种基于Java平台的航天器测试软件构架及其测试方法
CN104333808A (zh) * 2014-11-14 2015-02-04 复旦大学 用于Android及Linux智能电视机上的通用播放器
CN106649164A (zh) * 2016-12-29 2017-05-10 南威软件股份有限公司 一种硬件接口管理方法
CN110275716A (zh) * 2019-06-27 2019-09-24 深圳开立生物医疗科技股份有限公司 设备部署方法及装置、设备运行方法及电子设备

Also Published As

Publication number Publication date
CN110275716A (zh) 2019-09-24

Similar Documents

Publication Publication Date Title
WO2020259163A1 (zh) 设备部署方法及装置、设备运行方法及电子设备
CN107943485B (zh) 一种补丁编译平台及补丁编译方法
WO2021018005A1 (zh) 一种跨进程通信方法、装置及设备
US10929149B2 (en) Method and system for updating firmware
JP2005182809A (ja) ストレージ技術抽象化方式におけるファイル内でのファイルシステムの生成
WO2018090529A1 (zh) 一种镜像包制作、应用运行方法及系统
US20140372977A1 (en) Modifying a Middleware
JP7012074B2 (ja) 仮想ディスクの拡張方法及び機器
WO2018040270A1 (zh) 在Windows系统中加载Linux系统ELF文件的方法及装置
CN109753347B (zh) 一种实现驱动的系统及方法
WO2018090528A1 (zh) 一种镜像包制作、应用运行方法及系统
CN106909441B (zh) 一种基于jvm的磁盘直接i/o访问的方法
CN108614702A (zh) 字节码优化方法及装置
US10635504B2 (en) API versioning independent of product releases
WO2023213263A1 (zh) 程序编译和启动方法、设备及存储介质
US20120203735A1 (en) Dynamic configuration of a persistence provider
CN105556461A (zh) 用于预os镜像重写以提供跨架构支持、安全性自省和性能优化的技术
CN116107669B (zh) 深度学习框架的算子注册方法、装置、设备及存储介质
CN111290740A (zh) 应用程序的开发方法、装置、计算机设备和存储介质
CN108334453B (zh) 一种文件调试方法、装置、终端设备及存储介质
EP4350507A1 (en) Data processing system, method and apparatus
CN109254856A (zh) 智能pos服务端提供接口给客户端的方法
CN109542437A (zh) 一种基于Linux嵌入式浏览器的HMI开发方法
TWI640869B (zh) 配置一積體電路無線電通訊裝置的方法及積體電路無線電通訊裝置
WO2019157891A1 (zh) 应用安装方法、应用安装包的生成方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20830913

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20830913

Country of ref document: EP

Kind code of ref document: A1