CN110780855A - Method, device and system for uniformly managing and controlling interface - Google Patents
Method, device and system for uniformly managing and controlling interface Download PDFInfo
- Publication number
- CN110780855A CN110780855A CN201910932832.XA CN201910932832A CN110780855A CN 110780855 A CN110780855 A CN 110780855A CN 201910932832 A CN201910932832 A CN 201910932832A CN 110780855 A CN110780855 A CN 110780855A
- Authority
- CN
- China
- Prior art keywords
- interface
- request
- parameters
- address
- interface request
- Prior art date
- Legal status (The legal status 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 status listed.)
- Withdrawn
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
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
The invention provides a method for uniformly managing and controlling interfaces, which comprises the following steps: receiving an interface request initiated by a front end through a request analysis module to obtain an interface request address, matching the interface request address with an actual interface address in a configuration file, converting parameters of the interface request into corresponding parameters of an actual interface based on successful matching, and recording an ID and an address of the interface request in a database; and responding to the actual interface to finish corresponding operation, acquiring the address of the interface request from the database through a result analysis module according to the ID of the interface request, and reading a configuration file according to the address of the interface request to convert the parameters to be returned into the parameters corresponding to the interface request. The invention can realize the purpose of one-time development and repeated use of the interface.
Description
Technical Field
The present invention relates to the field of computers, and in particular, to a method and an apparatus for uniformly managing and controlling an interface.
Background
In the existing storage system, the request address of the interface, the input parameters and the output parameters of the interface cannot be modified after being defined, and only the interface can be requested by using the fixed request address and the fixed parameters, so that when the interface needs to be used by using a specific link for interfacing with other systems or other modules of the storage system, the interface needs to be re-developed to redefine the request address and the parameters. This not only creates redundancy in the code, but also increases the workload on the developer.
Disclosure of Invention
In view of this, an object of the embodiments of the present invention is to provide a method for uniformly managing and controlling an interface, which can implement one-time development and reuse of the interface.
Based on the above object, an aspect of the embodiments of the present invention provides a method for unifying management and control interfaces, including the following steps:
receiving an interface request initiated by a front end through a request analysis module to obtain an interface request address, matching the interface request address with an actual interface address in a configuration file, converting parameters of the interface request into corresponding parameters of an actual interface based on successful matching, and recording an ID and an address of the interface request in a database;
and responding to the actual interface to finish corresponding operation, acquiring the address of the interface request from the database through a result analysis module according to the ID of the interface request, and reading a configuration file according to the address of the interface request to convert the parameters to be returned into the parameters corresponding to the interface request.
In some embodiments, the configuration file includes a correspondence between addresses and parameters of various request interfaces and corresponding addresses and parameters of actual interfaces.
In some embodiments, converting the parameters of the interface request into the parameters of the corresponding actual interface, and recording the ID and the address of the interface request in the database includes:
and after converting the parameters of the interface request into the parameters of the corresponding actual interface, using the timestamp as the ID of the interface request.
In some embodiments, recording the ID and address of the interface request in a database further comprises:
saving a log associated with the request to the database.
In some embodiments, the method is applied in a storage system.
Another aspect of the embodiments of the present invention provides a device for unifying management and control interfaces, including:
the system comprises a request analysis module, a database and a data processing module, wherein the request analysis module is configured to receive an interface request initiated by a front end to obtain an interface request address, match the interface request address with an actual interface address in a configuration file, convert parameters of the interface request into parameters of a corresponding actual interface based on successful matching, and record an ID and an address of the interface request in the database; and
and the result analysis module is configured to respond to the actual interface to complete corresponding operation, acquire the address of the interface request from the database according to the ID of the interface request, and read a configuration file according to the address of the interface request to convert the parameters to be returned into the parameters corresponding to the interface request.
In some embodiments, the configuration file includes a correspondence between addresses and parameters of the plurality of request interfaces and corresponding actual interface addresses and parameters.
In some embodiments, the request parsing module is configured to use a timestamp as the ID of the interface request after converting the parameters of the interface request into the parameters of the corresponding actual interface.
In some embodiments, the apparatus is applied to a storage system.
Another aspect of the embodiments of the present invention provides a system for unifying management and control interfaces, including:
at least one processor; and
a memory storing program code executable by the processor, the program code, when executed by the processor, performing the method of any of the above.
The invention has the following beneficial technical effects: the method, the device and the system for uniformly controlling the interface provided by the embodiment of the invention can realize uniform control of the interface, and can finish the output of the request and the corresponding result of the interface through the request analysis module and the result analysis module no matter how many places the single interface is used and the request address and the parameters are changed, thereby reducing the development amount and reducing the redundancy of codes.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other embodiments can be obtained by using the drawings without creative efforts.
FIG. 1 is a flow diagram of a method of unifying management and control interfaces in accordance with the present invention;
FIG. 2 is a flow diagram illustrating an apparatus implementing interface requests according to the present invention;
fig. 3 is a schematic diagram of a hardware structure of a system for unifying management and control interfaces according to the present invention.
Detailed Description
Embodiments of the present invention are described below. However, it is to be understood that the disclosed embodiments are merely examples and that other embodiments may take various and alternative forms. The figures are not necessarily to scale; certain features may be exaggerated or minimized to show details of particular components. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a representative basis for teaching one skilled in the art to variously employ the present invention. As one of ordinary skill in the art will appreciate, various features illustrated and described with reference to any one of the figures may be combined with features illustrated in one or more other figures to produce embodiments that are not explicitly illustrated or described. The combination of features shown provides a representative embodiment for a typical application. However, various combinations and modifications of the features consistent with the teachings of the present invention may be desired for certain specific applications or implementations.
In order to make the objects, technical solutions and advantages of the present invention more apparent, the following embodiments of the present invention are described in further detail with reference to the accompanying drawings.
Based on the above purpose, an embodiment of the present invention provides a method for unifying management and control interfaces, as shown in fig. 1, including the following steps:
step S101: receiving an interface request initiated by a front end through a request analysis module to obtain an interface request address, matching the interface request address with an actual interface address in a configuration file, converting parameters of the interface request into corresponding parameters of an actual interface based on successful matching, and recording an ID and an address of the interface request in a database;
step S102: and responding to the actual interface to finish corresponding operation, acquiring the address of the interface request from the database through a result analysis module according to the ID of the interface request, and reading a configuration file according to the address of the interface request to convert the parameters to be returned into the parameters corresponding to the interface request.
In some embodiments, the configuration file includes a correspondence between addresses and parameters of various request interfaces and corresponding actual interface addresses and parameters. For example, a corresponding relationship between addresses and parameters of multiple request interfaces and corresponding actual Interface addresses and parameters is written in a configuration file in advance, and the corresponding relationship is shown in table 1, where a is an Interface address in an Interface request initiated by a front end, Interface is an Interface address to be actually processed, InA1 and InA2 are request parameters (entry parameters) of the front end request a, OutA1 is a return parameter (exit parameter) required by the front end request a, and interafaceint 1, interafaceint 2, and interafaceout 1 are default entry parameters and exit parameters of the actual Interface. If other Interface requests B, C, D require the use of an Interface, they need only be configured in a configuration file.
| A | Interface |
| InA1 | InterfaceInT1 |
| InA2 | InterfaceInT2 |
| OutA1 | InterfaceOutT1 |
TABLE 1
In some embodiments, converting the parameters of the interface request into the parameters of the corresponding actual interface, and recording the ID and the address of the interface request in the database includes: and after converting the parameters of the interface request into the parameters of the corresponding actual interface, using the timestamp as the ID of the interface request.
In some embodiments, recording the ID and the address of the interface request in the database further comprises: saving a log associated with the request to the database.
In some embodiments, the method is applied in a storage system.
It can be seen from the foregoing embodiments that the method for uniformly managing and controlling interfaces according to the embodiments of the present invention can achieve uniform management and control of interfaces, and can complete output of requests and corresponding results of interfaces through the request parsing module and the result parsing module regardless of the number of places where a single interface is used and how the request address and parameters change, thereby reducing development amount and reducing redundancy of codes.
In another aspect, an embodiment of the present invention provides an apparatus for uniformly managing and controlling an interface, including: the system comprises a request analysis module, a database and a data processing module, wherein the request analysis module is configured to receive an interface request initiated by a front end to obtain an interface request address, match the interface request address with an actual interface address in a configuration file, convert parameters of the interface request into parameters of a corresponding actual interface based on successful matching, and record an ID and an address of the interface request in the database; and the result analysis module is configured to respond to the actual interface to complete corresponding operation, acquire the address of the interface request from the database according to the ID of the interface request, and read a configuration file according to the address of the interface request to convert the parameters to be returned into the parameters corresponding to the interface request.
In some embodiments, the configuration file includes a correspondence between addresses and parameters of the various request interfaces and corresponding actual interface addresses and parameters.
In some embodiments, the request parsing module is configured to use a timestamp as the ID of the interface request after converting the parameters of the interface request into the parameters of the corresponding actual interface.
In an embodiment according to the present invention, as shown in fig. 2, after the front end initiates an interface request and forwards the interface request to the middleware through nginx (server), the middleware forwards the interface request to the request parsing module, and the request parsing module receives the interface request and can obtain a specific address of the interface request; after the address of the interface request is obtained, the address is matched with the interface configuration in the configuration file of the request analysis module, the matching is converted into the entry parameter, meanwhile, the timestamp is used as the request ID of the request, and other log data such as the request ID, the request address, the time and the like are recorded in a database. After the operations are completed, the request analysis module forwards the processing task to the corresponding actual interface for operation. And the actual interface finishes corresponding operation, a result analysis module is called before the result is returned, the result analysis module reads the configuration file according to the request ID, the parameter name of the request return value (the output parameter of the request interface) is obtained, and the result is returned after the correspondence is realized.
In some embodiments, the device is applied to a storage system, and an interface request parsing module and a result parsing module are required to be added to the storage system. The request analysis module is responsible for analyzing the request addresses of all the interfaces, after the front-end request address is forwarded to the middleware through nginx, the middleware needs to forward the request to the request analysis module, and the request analysis module can analyze the interface to which the request address should be forwarded according to the interface configuration file in the module; the result analysis module is responsible for analyzing the return values of all the interfaces, the result analysis module is required to be called before the execution of all the interfaces is finished, and the result analysis module reads the configuration file according to the request ID of the interfaces and returns the result after analyzing the corresponding result return parameters. By the mode, the unified management and control of the interfaces can be realized, and the requests of the interfaces and the output of corresponding results can be completed through the request analysis module and the result analysis module no matter where the single interface is used and how the request address and the parameters change. This reduces both the amount of development and the redundancy of the code.
Where technically feasible, the technical features listed above for the different embodiments may be combined with each other or changed, added, omitted, etc. to form further embodiments within the scope of the invention.
In view of the foregoing, in another aspect of the embodiments of the present invention, an embodiment of a system for uniformly managing and controlling an interface is provided.
The system for uniformly managing and controlling the interface comprises a memory and at least one processor, wherein the memory stores a computer program capable of running on the processor, and the processor executes any one of the methods when executing the computer program.
Fig. 3 is a schematic diagram of a hardware structure of an embodiment of the system for uniformly managing an interface according to the present invention.
Taking the computer device shown in fig. 3 as an example, the computer device includes a processor 301 and a memory 302, and may further include: an input device 303 and an output device 304.
The processor 301, the memory 302, the input device 303 and the output device 304 may be connected by a bus or other means, and fig. 3 illustrates the connection by a bus as an example.
The memory 302 is a non-volatile computer-readable storage medium, and can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as program instructions/modules corresponding to the method for unified interface management in the embodiment of the present application. The processor 301 executes various functional applications of the server and data processing by running nonvolatile software programs, instructions and modules stored in the memory 302, that is, implements the method of the unified management and control interface of the above method embodiment.
The memory 302 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to a method of unifying management and control interfaces, and the like. Further, the memory 302 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some embodiments, memory 302 optionally includes memory located remotely from processor 301, which may be connected to a local module via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input device 303 may receive input numeric or character information and generate key signal inputs related to user settings and function control of the computer apparatus unifying the method of managing the interface. The output means 304 may comprise a display device such as a display screen.
Program instructions/modules corresponding to the one or more methods for uniformly managing the interface are stored in the memory 302, and when executed by the processor 301, perform the method for uniformly managing the interface in any of the above-described method embodiments.
Any embodiment of the computer device executing the method for uniformly managing and controlling the interface may achieve the same or similar effects as any corresponding method embodiment described above.
Finally, it should be noted that, as will be understood by those skilled in the art, all or part of the processes in the methods of the above embodiments may be implemented by a computer program, which may be stored in a computer-readable storage medium, and when executed, may include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), a Random Access Memory (RAM), or the like.
In addition, the apparatuses, devices and the like disclosed in the embodiments of the present invention may be various electronic terminal devices, such as a mobile phone, a Personal Digital Assistant (PDA), a tablet computer (PAD), a smart television and the like, or may be a large terminal device, such as a server and the like, and therefore the scope of protection disclosed in the embodiments of the present invention should not be limited to a specific type of apparatus, device. The client disclosed in the embodiment of the present invention may be applied to any one of the above electronic terminal devices in the form of electronic hardware, computer software, or a combination of both.
Furthermore, the method disclosed according to an embodiment of the present invention may also be implemented as a computer program executed by a CPU, and the computer program may be stored in a computer-readable storage medium. The computer program, when executed by the CPU, performs the above-described functions defined in the method disclosed in the embodiments of the present invention.
Further, the above method steps and system elements may also be implemented using a controller and a computer readable storage medium for storing a computer program for causing the controller to implement the functions of the above steps or elements.
Further, it should be appreciated that the computer-readable storage media (e.g., memory) described herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. By way of example, and not limitation, nonvolatile memory can include Read Only Memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM), which can act as external cache memory. By way of example and not limitation, RAM is available in a variety of forms such as synchronous RAM (DRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The storage devices of the disclosed aspects are intended to comprise, without being limited to, these and other suitable types of memory.
Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as software or hardware depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosed embodiments of the present invention.
The various illustrative logical blocks, modules, and circuits described in connection with the disclosure herein may be implemented or performed with the following components designed to perform the functions described herein: a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of these components. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP, and/or any other such configuration.
The steps of a method or algorithm described in connection with the disclosure herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.
In one or more exemplary designs, the functions may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes Compact Disc (CD), laser disc, optical disc, Digital Versatile Disc (DVD), floppy disk, blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
It should be understood that, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly supports the exception. It should also be understood that "and/or" as used herein is meant to include any and all possible combinations of one or more of the associated listed items.
The numbers of the embodiments disclosed in the embodiments of the present invention are merely for description, and do not represent the merits of the embodiments.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk, an optical disk, or the like.
The above-described embodiments are possible examples of implementations and are presented merely for a clear understanding of the principles of the invention. Those of ordinary skill in the art will understand that: the discussion of any embodiment above is meant to be exemplary only, and is not intended to intimate that the scope of the disclosure, including the claims, of embodiments of the invention is limited to these examples; within the idea of an embodiment of the invention, also technical features in the above embodiment or in different embodiments may be combined and there are many other variations of the different aspects of an embodiment of the invention as described above, which are not provided in detail for the sake of brevity. Therefore, any omissions, modifications, substitutions, improvements, and the like that may be made without departing from the spirit and principles of the embodiments of the present invention are intended to be included within the scope of the embodiments of the present invention.
Claims (10)
1. A method for uniformly managing and controlling interfaces is characterized by comprising the following steps:
receiving an interface request initiated by a front end through a request analysis module to obtain an interface request address, matching the interface request address with an actual interface address in a configuration file, converting parameters of the interface request into corresponding parameters of an actual interface based on successful matching, and recording an ID and an address of the interface request in a database;
and responding to the actual interface to finish corresponding operation, acquiring the address of the interface request from the database through a result analysis module according to the ID of the interface request, and reading a configuration file according to the address of the interface request to convert the parameters to be returned into the parameters corresponding to the interface request.
2. The method of claim 1, wherein the configuration file comprises a correspondence between addresses and parameters of various request interfaces and corresponding addresses and parameters of actual interfaces.
3. The method of claim 1, wherein converting the parameters of the interface request into the parameters of the corresponding actual interface, and recording the ID and the address of the interface request in a database comprises:
and after converting the parameters of the interface request into the parameters of the corresponding actual interface, using the timestamp as the ID of the interface request.
4. The method of claim 1, wherein recording the ID and address of the interface request in a database further comprises:
saving a log associated with the request to the database.
5. The method of claim 1, wherein the method is applied to a storage system.
6. The utility model provides a device of unified management and control interface which characterized in that includes:
the system comprises a request analysis module, a database and a data processing module, wherein the request analysis module is configured to receive an interface request initiated by a front end to obtain an interface request address, match the interface request address with an actual interface address in a configuration file, convert parameters of the interface request into parameters of a corresponding actual interface based on successful matching, and record an ID and an address of the interface request in the database; and
and the result analysis module is configured to respond to the actual interface to complete corresponding operation, acquire the address of the interface request from the database according to the ID of the interface request, and read a configuration file according to the address of the interface request to convert the parameters to be returned into the parameters corresponding to the interface request.
7. The apparatus of claim 6, wherein the configuration file comprises a correspondence between addresses and parameters of a plurality of request interfaces and corresponding actual interface addresses and parameters.
8. The apparatus of claim 6, wherein the request parsing module is configured to use a timestamp as the ID of the interface request after converting the parameters of the interface request into the parameters of the corresponding actual interface.
9. The apparatus of claim 8, wherein the apparatus is applied to a storage system.
10. A system for uniformly managing and controlling interfaces, comprising:
at least one processor; and
a memory storing program code executable by the processor, the program code implementing the method of any one of claims 1-5 when executed by the processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910932832.XA CN110780855A (en) | 2019-09-29 | 2019-09-29 | Method, device and system for uniformly managing and controlling interface |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910932832.XA CN110780855A (en) | 2019-09-29 | 2019-09-29 | Method, device and system for uniformly managing and controlling interface |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110780855A true CN110780855A (en) | 2020-02-11 |
Family
ID=69384715
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910932832.XA Withdrawn CN110780855A (en) | 2019-09-29 | 2019-09-29 | Method, device and system for uniformly managing and controlling interface |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110780855A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111666426A (en) * | 2020-06-10 | 2020-09-15 | 北京海致星图科技有限公司 | Method, system and equipment for acquiring knowledge graph multi-scene graph data |
| CN111857787A (en) * | 2020-06-12 | 2020-10-30 | 苏州浪潮智能科技有限公司 | Method, system, equipment and medium for burning firmware of voltage converter |
| CN113703862A (en) * | 2021-07-12 | 2021-11-26 | 新华三大数据技术有限公司 | Configuration-based interface calling method, device, equipment and storage medium |
-
2019
- 2019-09-29 CN CN201910932832.XA patent/CN110780855A/en not_active Withdrawn
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111666426A (en) * | 2020-06-10 | 2020-09-15 | 北京海致星图科技有限公司 | Method, system and equipment for acquiring knowledge graph multi-scene graph data |
| CN111857787A (en) * | 2020-06-12 | 2020-10-30 | 苏州浪潮智能科技有限公司 | Method, system, equipment and medium for burning firmware of voltage converter |
| CN113703862A (en) * | 2021-07-12 | 2021-11-26 | 新华三大数据技术有限公司 | Configuration-based interface calling method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107609156B (en) | Page construction method and device | |
| CN110780855A (en) | Method, device and system for uniformly managing and controlling interface | |
| CN111177043B (en) | Method, system, device and medium for accelerating reading of field replaceable unit information | |
| CN110929883A (en) | Method and device for supporting FPGA (field programmable gate array) training in TensorFlow | |
| CN107330028A (en) | Expansion application methods and system of a kind of Apache NiFi in terms of source data input database | |
| CN107729375B (en) | Log data sorting method and device | |
| CN110659165A (en) | Multi-node server automatic testing method and device | |
| CN114047968B (en) | Method, system, storage medium and equipment for automatic hardware adaptation | |
| CN110647423A (en) | Method, device and readable medium for creating storage volume mirror image based on application | |
| CN111078497A (en) | Data storage method, equipment and storage medium of BMC (baseboard management controller) | |
| CN110442492A (en) | A kind of System Operation Log management method and device | |
| CN111143250B (en) | Method, device and medium for accessing FPGA storage unit based on AXI-ST interface | |
| CN111309264B (en) | Method, system, device and medium for making directory quota compatible with snapshot | |
| CN111176666B (en) | BIOS + ME mirror image refreshing method, system, equipment and readable medium | |
| CN111143258B (en) | Method, system, device and medium for accessing FPGA (field programmable Gate array) by system based on Opencl | |
| CN109344082B (en) | Method and system for automatically testing register | |
| CN111078294B (en) | Instruction processing method and device of processor and storage medium | |
| CN110674505A (en) | Vulnerability scanning remaining time estimation method and device | |
| CN107562790B (en) | Method and system for realizing batch warehousing of data processing | |
| CN111045989A (en) | Method, device and medium for querying CPLD version information | |
| CN110659035A (en) | Method and device for batch mounting of mirror images based on BMC | |
| CN108628642B (en) | Method and apparatus for switching versions of system and storage medium | |
| CN110489121B (en) | Skin package file generation method and system | |
| CN114461595A (en) | Method, device, medium and electronic equipment for sending message | |
| CN109582685B (en) | Method and device for recording context request execution process |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WW01 | Invention patent application withdrawn after publication | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20200211 |