CN112764751A - Interface generation method and device, interface request method and device and storage medium - Google Patents
Interface generation method and device, interface request method and device and storage medium Download PDFInfo
- Publication number
- CN112764751A CN112764751A CN202110111992.5A CN202110111992A CN112764751A CN 112764751 A CN112764751 A CN 112764751A CN 202110111992 A CN202110111992 A CN 202110111992A CN 112764751 A CN112764751 A CN 112764751A
- Authority
- CN
- China
- Prior art keywords
- interface
- request
- script file
- equipment
- parameter information
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 87
- 238000012795 verification Methods 0.000 claims abstract description 53
- 230000000007 visual effect Effects 0.000 claims abstract description 14
- 230000004913 activation Effects 0.000 claims description 49
- 238000004458 analytical method Methods 0.000 claims description 15
- 230000008859 change Effects 0.000 claims description 13
- 238000004590 computer program Methods 0.000 claims description 13
- 238000011161 development Methods 0.000 abstract description 6
- 238000012423 maintenance Methods 0.000 abstract description 5
- 238000001994 activation Methods 0.000 description 49
- 238000007726 management method Methods 0.000 description 10
- 238000010586 diagram Methods 0.000 description 6
- 238000003032 molecular docking Methods 0.000 description 6
- 230000006855 networking Effects 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 238000012360 testing method Methods 0.000 description 5
- 238000005406 washing Methods 0.000 description 5
- 230000001360 synchronised effect Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000011160 research Methods 0.000 description 3
- 230000003213 activating effect Effects 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 230000001976 improved effect Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 238000012512 characterization method Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 230000007935 neutral effect Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000001737 promoting effect Effects 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 230000008093 supporting effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Computer Security & Cryptography (AREA)
- Computer And Data Communications (AREA)
Abstract
The application relates to an interface generation method and device, an interface request method and device and a storage medium, wherein the interface generation method comprises the following steps: receiving configuration parameters of a user through a visual interface generation interface; the configuration parameters at least comprise a configured interface request mode, a returned content type, an interface field, an interface condition and an interface endpoint; the interface condition at least comprises an interface verification condition, and the interface verification condition is used for verifying the equipment parameter information sent by the equipment; generating a corresponding script file according to the configuration parameters and the script file template; generating an interface address associated with the script file; issuing an interface corresponding to the interface address; and storing the interface information of the issued interface in an interface information table. The method and the device have the advantages that the zero-code, rapid development, generation and maintenance of the interface are realized, the interface with the corresponding function can be customized for various different devices, and the application range is wide.
Description
Technical Field
The present application relates to the field of internet technologies, and in particular, to an interface generation method and apparatus, an interface request method and apparatus, and a storage medium.
Background
With the increasing demand for software, software developers are expensive and short of supply, the development of the software is periodic, and adjustment is carried out in the later period according to the change of the demand, so that the running and maintenance costs are high. Modern digital enterprises require a large amount of software, most of which are highly customized. For example, an interface for networking and activating a device is realized, but information of each device is different, and an activation process and a data field are different, it is impossible to develop an interface for reporting device information to meet all device scenarios, and it is obviously impossible to develop a general interface to meet online submission of all devices because device parameters are different from usage scenarios. Therefore, developing an interface for each device is a time consuming, labor intensive, and inefficient approach.
Disclosure of Invention
In order to solve the technical problem of low efficiency of developing an interface for each device, embodiments of the present application provide an interface generation method and apparatus, an interface request method and apparatus, and a storage medium.
In a first aspect, an embodiment of the present application provides an interface generation method, where the interface generation method includes:
receiving configuration parameters of a user through a visual interface generation interface;
the configuration parameters at least comprise a configured interface request mode, a returned content type, an interface field, an interface condition and an interface endpoint;
the interface field represents the equipment parameter information required to be sent by the equipment;
the interface condition at least comprises an interface verification condition, and the interface verification condition is used for verifying the equipment parameter information corresponding to the interface field;
generating a corresponding script file according to the configuration parameters and the script file template;
generating an interface address associated with the script file;
issuing an interface corresponding to the interface address;
and storing the interface information of the issued interface in an interface information table, wherein the interface information table at least comprises the interface endpoint.
Optionally, the interface generating method further includes: and synchronizing the script file of the issued interface and the interface information table to the equipment activation server of each node.
Optionally, the interface generating method further includes: and calling the equipment of each node to activate the hot loading interface of the server, so that the issued interface takes effect in real time.
Optionally, before issuing the interface corresponding to the interface address, the interface generating method further includes: and testing the interface.
Optionally, generating an interface address associated with the script file includes:
acquiring a server domain name, a current version number of an interface to be issued and an interface endpoint;
and generating an interface address associated with the script file according to the server domain name, the current version number and the interface endpoint.
Optionally, the interface generating method further includes:
receiving the configuration change parameters of a user through a visual interface generation interface;
updating the script file and the interface address corresponding to the generated interface according to the changed configuration parameters;
and re-issuing the generated interface.
In a second aspect, the present application provides an interface request method, where the interface request method includes:
receiving an interface request of a request device, wherein the interface request carries an interface endpoint of an interface to be called of the request device and a device parameter information data packet;
judging whether an interface endpoint of the interface to be called exists in the generated interface information table or not;
if the interface endpoint of the interface to be called exists in the generated interface information table, loading a script file corresponding to the interface to be called;
verifying the equipment parameter information in the equipment parameter information data packet according to the script file corresponding to the interface to be called;
if the verification is successful, returning output information to the request equipment;
the generated interface information table and the script file corresponding to the interface to be called are generated according to any one of the interface generation methods.
Optionally, the interface request method further includes:
and if the interface endpoint of the interface to be called does not exist in the generated interface information table, returning a first error prompt to the request equipment.
Optionally, verifying the device parameter information in the device parameter information data packet according to the script file corresponding to the interface to be called includes:
analyzing a script file corresponding to the interface to be called to obtain an interface request mode, a returned content type and an interface verification condition;
requesting to acquire an equipment parameter information data packet in an interface request mode;
if the request for obtaining the equipment parameter information data packet is successful, analyzing the equipment parameter information data packet in an analysis mode corresponding to the returned content type;
if the analysis is successful, the equipment parameter information in the equipment parameter information data packet is backfilled to the interface field,
and verifying the equipment parameter information of the interface field according to the interface verification condition.
In a third aspect, the present application provides an interface generating apparatus, including:
the parameter acquisition module is used for receiving configuration parameters of a user through a visual interface generation interface;
the configuration parameters at least comprise a configured interface request mode, a returned content type, an interface field, an interface condition and an interface endpoint;
the interface field represents the equipment parameter information required to be sent by the equipment;
the interface condition at least comprises an interface verification condition, and the interface verification condition is used for verifying the equipment parameter information corresponding to the interface field;
the script file generating module is used for generating a corresponding script file according to the configuration parameters and the script file template;
the interface address generating module is used for generating an interface address associated with the script file;
the issuing module is used for issuing the interface corresponding to the interface address;
and the storage module is used for storing the issued interface information of the interface in an interface information table.
In a fourth aspect, the present application provides an interface request apparatus, including:
the request receiving module is used for receiving an interface request of the request equipment, wherein the interface request carries an interface endpoint of the interface to be called of the request equipment and an equipment parameter information data packet;
the first judgment module is used for judging whether an interface endpoint of the interface to be called exists in the generated interface information table or not;
the calling module is used for loading the script file corresponding to the interface to be called if the interface endpoint of the interface to be called exists in the generated interface information table;
the verification module is used for verifying the equipment parameter information in the equipment parameter information data packet according to the script file corresponding to the interface to be called;
and the sending module is used for returning output information to the request equipment if the verification is successful.
In a fifth aspect, the present application provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, causes the processor to perform the steps of the interface generation method or the interface request method as in any one of the preceding.
In a sixth aspect, the present application provides a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor executing the program to perform the steps of the interface generation method or the interface request method according to any one of the preceding claims.
Compared with the prior art, the technical scheme provided by the embodiment of the application has the following advantages:
according to the method provided by the embodiment of the application, the configuration parameters of a user are received through a visual interface generation interface; the configuration parameters at least comprise a configured interface request mode, a returned content type, an interface field, an interface condition and an interface endpoint; the interface condition at least comprises an interface verification condition, and the interface verification condition is used for verifying the equipment parameter information sent by the equipment corresponding to the interface field; generating a corresponding script file according to the configuration parameters and the script file template; generating an interface address associated with the script file; issuing an interface corresponding to the interface address; and storing the interface information of the issued interface in an interface information table. The method and the device have the advantages that the zero-code, rapid development, generation and maintenance of the interface are realized, the interface with the corresponding function can be customized for various different devices, and the application range is wide.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
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 for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.
Fig. 1 is a schematic flowchart of an interface generation method according to an embodiment of the present application;
fig. 2 is a flowchart illustrating an interface request method according to an embodiment of the present application;
fig. 3 is a block diagram of an interface generating apparatus according to an embodiment of the present application;
fig. 4 is a block diagram of an interface request apparatus according to an embodiment of the present application;
fig. 5 is an application scenario diagram of an interface generation method and an interface request method according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Fig. 1 is a schematic flowchart of an interface generation method according to an embodiment of the present application; referring to fig. 1, the interface generation method is applied to a server side, and includes the following steps:
s100: and receiving the configuration parameters of the user through a visualized interface generation interface.
Specifically, the visualized interface generation interface is an operation interface for a user to configure relevant parameters of the interface to be generated according to actual requirements. The interface generation interface is an interface of a universal equipment report control platform developed by research personnel. The user can register the platform first, and can enter an interface generation interface of the universal equipment register control platform after successfully logging in the account. The configuration parameters are instructions for the user to operate the interface generation interface. The configuration parameters may include a drop-down box selection instruction, an input instruction, a multiple selection instruction, and the like.
The configuration parameters at least include the interface request mode, the return content type, the interface field, the interface condition and the interface endpoint of the configuration.
The interface request mode represents the mode of acquiring the data packet.
And returning the format of the data packet sent to the server by the content type characterization equipment. The analysis mode of the server side for analyzing the data packet can be determined through the returned content type.
The interface field characterizes the device parameter information that the device is required to send. For example, for a television, the required device parameter information includes screen size, model, movement, memory, serial number, online status, and the like. For the refrigerator, the required device parameter information includes refrigerator volume, noise, power consumption, energy efficiency, serial number, door structure, online state, etc. The interface field is configured according to actual requirements. The interface field comprises at least one parameter field, the equipment parameter information sent by the equipment comprises at least one equipment parameter, each equipment parameter corresponds to one parameter field, and the data of each equipment parameter can be backfilled into the corresponding parameter field.
The interface field is specifically determined by the user depending on the type of device and the purpose for which the device requests the interface.
The interface generation method can generate an interface for equipment networking activation, an interface for reporting equipment information, an interface for starting up activation, an interface for networking reporting and the like. The interface generation method can generate interfaces with different functions and interfaces with different equipment requirements.
The interface condition at least comprises an interface verification condition, the interface verification condition is used for verifying the equipment parameter information sent by the equipment, and the interface verification condition is a parameter entering rule. For example, whether the device parameter information meets the interface verification condition configured in advance is verified. Different device parameters correspond to different verification conditions.
S200: and generating a corresponding script file according to the configuration parameters and the script file template.
Specifically, the script file template is a template code of a script file which is well laid out in advance in a bottom layer code of the universal equipment report control platform.
The configuration parameters are used for configuring at least an interface request mode, a return content type and an interface condition in the script file template, and the configured script file template forms a script file.
Specifically, the script file is a grovvy file.
S300: an interface address associated with the script file is generated.
Specifically, the script files correspond to the interface addresses one to one.
The same interface may have multiple versions of interface addresses, and each version of interface address corresponds to one script file. However, when the interface is called, the latest version of the interface address and the corresponding script file which are newly issued are called by default.
S400: and issuing an interface corresponding to the interface address.
Specifically, the interface address of the interface and the corresponding script file may generate a new version due to a change of the user, and therefore, the interface corresponding to the interface address is issued to allow the currently generated latest version of the script file and the interface address to be the default interface address and script file to be called of the interface.
S500: and storing the interface information of the issued interface in an interface information table.
Specifically, the information stored in the interface information table includes at least the interface endpoint of the interface.
In one embodiment, before step S400, the interface generation method further includes the steps of: and testing the interface.
In particular, the purpose of testing an interface is to verify in advance whether the generated interface meets specifications and can be successfully invoked. The interface can be checked in advance before the interface corresponding to the interface address is released, the problem can be found and corrected as soon as possible, the interface after being released can be normally called, and the effectiveness of the interface is ensured.
In one embodiment, after issuing the interface corresponding to the interface address, the interface generation method further includes: and synchronizing the script file of the issued interface and the interface information table to the equipment activation server of each node.
In a specific embodiment, the interface generation method further includes: and calling equipment of each node to activate a hot loading API (hot loading interface) of the server so as to enable the issued interface to be effective in real time.
Specifically, the script file and the interface information table of the interface are synchronized to the device activation server of each node, and a hot load interface needs to be called to update an API (interface), so that the generated interface becomes effective in real time.
In one embodiment, the configuration parameters further include configured data warehousing rules, queue names, list storage locations, and locations of device parameter information in the data packets.
Specifically, the purpose of configuring the data storage rule is to allocate different databases to interfaces corresponding to different devices, so that the databases corresponding to the different devices are effectively isolated, and the data stability is ensured.
The interface verification condition also comprises an equipment identity verification mode, a multi-request cache setting rule and a unique KEY specifying rule.
Specifically, each device has a unique identifier, such as a MAC address, or a serial number, code, emmcId, etc. The unique KEY specifies rules for specifying a unique identification of a device.
In the aspect of traditional software development, usually, one device activation interface is developed, different device types need to be distinguished according to device _ type field parameters, different types of devices also have different parameters, and data requested by different devices needs to be isolated in an actual scene, for example, a refrigerator database is created in a background, and a washing machine database has to write logic codes for judging different device types and storing different device databases and the like.
By the method, the data storage rule is configured, so that the related data of different interfaces can be stored in different databases, namely the data between the interfaces are independently stored, and the problem of isolation of information data of different devices is solved. And the user can directly and intuitively create the database configuration writing rule in the background.
In one embodiment, the interface generation method further includes the steps of:
generating an example text corresponding to the published interface;
and displaying a download path or a download entrance of the example text on the visualized interface generation interface.
In particular, the example text is an example of docking code for a published and generated interface. The interface issuing method is used for guiding a research and development personnel at the equipment end to quickly apply the issued and generated interface to the code at the equipment end, quickly promoting development work and improving development efficiency.
In a specific embodiment, generating an example text corresponding to the published interface specifically includes:
invoking a generic instance template;
and generating corresponding example texts according to the interface verification conditions of the published interface and the universal example template.
In one particular embodiment, the generated example text includes versions of multiple code languages, including, for example: the c + + version docking code example text, the php version docking code example text, the java version docking code example text, and the like are not limited thereto.
The code may be provided to the developer in the form of an sdk download package. sdk the example text in the form of a code download package is generated and displayed at the front end, and the developer can select the example text in the desired language for download.
The example text of the embodiment has a docking assistant function, and can assist the device side or the client side to promote development work and docking work faster after an interface is created in an early stage, so that efficiency is further improved.
In one embodiment, step S300 specifically includes:
s310: and acquiring a server domain name, a current version number of an interface to be issued and an interface endpoint.
The execution main body of the interface generation method is a server side. The server side may include one server or may be a server cluster. If the server side is a server, the domain name of the server is the domain name of the server. If the server side is a server cluster, the server domain name is the domain name of the server of the device direct request interface.
In one embodiment, the server cluster includes a Web neutral management server and a device activation server. The Web middle management server is a background server of the universal equipment report control platform and is used for generating a script file and an interface address of an interface according to configuration parameters of a user and storing issued interface information of the interface in an interface information table. The Web central management server is also used for synchronizing the script files of all the generated interfaces and the interface information table to the equipment activation server. The equipment activation server is used for responding to the interface request of the equipment according to the generated script file of the interface and the interface information table which are synchronized. The interface generation method is applied to a Web middle management server.
If the server side comprises a server, the server is a background server of the universal equipment report control platform and is also a server for receiving and responding to the interface request of the equipment.
And the current version number of the interface to be issued is obtained according to the version number issued before the interface to be issued. For example, if the previously released version is V1, the current version number is V2.
S320: and generating an interface address associated with the script file according to the server domain name, the current version number and the interface endpoint.
In particular, the server domain name, current version number, and interface endpoint constitute the interface address. Of course the composition of the interface address may also include other elements.
For example, an interface of a refrigerator appliance is generated, the interface address of which is: http:// www.example.com/v 1/device/active/refrovirator.
Com is the server domain name, v1 is the current version number, and/device/active/refiector is the interface endpoint.
For another example, an interface of a washing machine is generated, and the interface address is as follows: http:// www.example.com/v 2/device/active/washingmachine.
Com is the server domain name, v2 is the current version number, and/device/active/washingma chine is the interface endpoint.
In one embodiment, the interface generation method further includes the steps of:
receiving the configuration change parameters of a user through a visual interface generation interface;
updating the script file and the interface address corresponding to the generated interface according to the changed configuration parameters;
and re-issuing the generated interface.
Specifically, after an interface is generated, a user can manage and modify the script file and the interface address of the interface. The specific method is the same as the method for newly generating the interface. Entering the interface generation interface of the generated interface, the user may re-edit the configuration modifiable options. The alterable option is an option which can be altered again and is defined by the developer according to specific situations. For example, the alterable options include one or more of interface request mode, returned content type, interface field, and interface condition.
After the generated interface is modified by changing the configuration parameters, the corresponding script file is correspondingly modified, and the interface address is correspondingly updated because the version number is updated.
The essence of re-publishing the generated interface is to take the currently generated latest version of the script file and the interface address as the default to-be-called script file and interface address of the interface.
The historical script files and the historical interface addresses of the generated interfaces in the application can be stored or recorded and cannot be covered by the script files and the interface addresses of the latest version. Thus, a rollback operation may be achieved. Thereby enabling faster rollback and faster iteration of the interface.
After the interface corresponding to the interface address is issued by the interface generation method, the user can acquire the interface address through the interface generation interface. The interface address is provided for equipment research personnel, and the equipment research personnel can embed the interface address into the equipment code of the corresponding equipment according to the rule agreed in advance with the research personnel reporting the control platform of the general equipment, so that the equipment can send an interface request to the equipment activation server to request and call the interface when the corresponding event is triggered.
The interface generation method edits the logic generated by the interface into a universal code, takes the universal code as a bottom code of the universal equipment report control platform, and then is provided with a corresponding foreground interface, so that a user can conveniently and visually configure the relevant parameters of the interface to be generated according to the interface generation interface to generate the interface. The method can directly and more intuitively operate the device interface parameter logic change in the middle management system, and when a user needs to change the interface version, the previous configuration can be directly changed so as to update the script file and the interface address of the interface. The application realizes code-free and quick interface generation.
The interface generation method can generate different types of interfaces such as log interfaces with different functions, activation interfaces and the like. According to the method and the device, the zero code generation interface is realized through the visual interface, the interface generation efficiency is improved, the difficulty in developing various interfaces is reduced, the zero code maintenance interface and the interface modification are convenient for a user, and the quick iteration of the interface is realized.
In addition, the script files and the interface addresses of all versions of all interfaces and the interface information can be stored, so that rollback and iteration can be realized more quickly.
Fig. 2 is a flowchart illustrating an interface request method according to an embodiment of the present application; referring to fig. 2, the interface request method includes the steps of:
s010: and receiving an interface request of the request equipment, wherein the interface request carries an interface endpoint of the interface to be called of the request equipment and an equipment parameter information data packet.
Specifically, the interface request method of the present application is applied to a device activation server. The device activation server synchronizes the script file and the interface information table of all the published interfaces generated by the previous interface generation method. That is, the device activation server stores script files and interface information tables for a plurality of different interfaces.
Under normal conditions, after acquiring the interface address of the requesting device, a device developer of the requesting device embeds the interface address into a device code of the requesting device, so that the requesting device can send an interface request to the device activation server to request an interface when a corresponding event is triggered.
Thus, normally, the requesting device has embedded in its device code the interface endpoint in the interface address. Therefore, the interface request sent by the requesting device to the device activation server carries the interface endpoint of the interface to be invoked.
S020: and judging whether the interface endpoint of the interface to be called exists in the generated interface information table.
Specifically, some interfaces to be called by the device may not be the interfaces managed by the device activation server of the present application, and therefore, it is necessary to determine in advance whether the interface to be called by the requesting device is the interface managed by the device activation server. The device activation server judges whether the interface to be called exists according to the interface endpoint. Because the interface information of each generated interface through the present application is synchronized to the device activation server, the interface information table stores at least the interface endpoint of each generated interface. Therefore, if the interface endpoint of the interface to be called exists in the generated interface information table, it is indicated that the interface to be called is the interface managed by the device activation server.
The interface information table may further include one or more of a current interface version, an interface field, an interface name, an interface code, and a provisioning device type.
As shown in table 1, it is an interface information table. The interface information table comprises an interface code, an interface name, an interface endpoint, an interface field, a current interface version and a backup device type.
Table 1: interface information table
The interface information for the 6 interfaces is shown in table 1. The interface names are respectively a refrigerator starting networking reporting interface, a washing machine washing interface, a television starting activation interface, a television box starting networking reporting interface, a radio and television equipment activation interface and a Philips intelligent activation interface. These 6 interfaces correspond to different devices, respectively. And the version of some interfaces is updated.
S030: and if the interface endpoint of the interface to be called exists in the generated interface information table, loading the script file corresponding to the interface to be called.
Specifically, if the interface to be called is an interface managed by the device activation server, the device activation server also synchronizes the script file of the interface to be called. The device activation server can be matched and loaded to the script file of the interface to be called through the interface endpoint.
S040: and verifying the equipment parameter information in the equipment parameter information data packet according to the script file corresponding to the interface to be called.
S050: and if the verification is successful, returning output information to the request equipment.
Specifically, in the process of generating the interface, the setting of the interface field in the script file restricts the device parameter information required to be sent by the device, and the setting of the interface verification condition restricts the rule that the device parameter information corresponding to the interface field needs to follow. Therefore, the script file corresponding to the calling interface can be used to verify whether the device parameter information in the device parameter information packet sent by the requesting device meets the preset rule.
And if the preset rule is met, the equipment activation server allows the request equipment to successfully call the interface to be called, and the equipment activation server returns corresponding output information to the request equipment.
The output information may include, for example, activation id information, etc., without limitation. The output information is specifically determined according to the device type and the application scenario.
In one embodiment, the interface request method further comprises the steps of:
and if the interface endpoint of the interface to be called does not exist in the generated interface information table, returning a first error prompt to the equipment to be reported.
Specifically, if the interface endpoint of the interface to be called does not exist in the generated interface information table, it indicates that the interface to be called does not exist or does not belong to the device activation server management. Thus, the device activation server may send a first error prompt to the requesting device. The first error prompt may be a voice prompt and/or a text display prompt, such as a prompt "endpoint is not present" or a return 404.
In one embodiment, step S040 specifically includes:
analyzing a script file corresponding to the interface to be called to obtain an interface request mode, a returned content type and an interface verification condition;
requesting to acquire an equipment parameter information data packet in an interface request mode;
if the request for obtaining the equipment parameter information data packet is successful, analyzing the equipment parameter information data packet in an analysis mode corresponding to the returned content type;
if the analysis is successful, the equipment parameter information in the equipment parameter information data packet is backfilled to the interface field,
and verifying the equipment parameter information of the interface field according to the interface verification condition.
Specifically, the interface request mode represents a data packet pulling mode, and the interface request mode may be a Get mode for requesting to obtain a data packet, a POST mode for requesting to obtain a data packet, or the like, but is not limited thereto.
An interface request mode is already defined when an interface is generated, but a data packet sent by a requesting device may not support the interface request mode, so that a device activation server fails to request to acquire a device parameter information data packet.
In a specific embodiment, if the request for obtaining the device parameter information data packet fails, a third error notification is returned to the requesting device. The third error prompt may be a voice prompt and/or a text display prompt, such as a prompt "method not supported.
The application also defines the analytic mode of the data packet. The return content type is a data type of data returned by the server to the device. The data type determines the analysis mode of the data, namely the data type is matched with the analysis mode. Therefore, it can be determined in which parsing manner the server parses the data packet according to the type of the returned content.
If the device activation server successfully analyzes the data packet in the analysis mode corresponding to the returned content type, the device activation server extracts the device parameter information in the device parameter information data packet.
And returning the analysis mode corresponding to the Content type as a Content-type.
In one embodiment, if the device activation server fails to parse the data packet in the parsing manner corresponding to the returned content type, the device activation server returns a fourth error notification to the requesting device.
The fourth error prompt may be a voice prompt and/or a text display prompt, such as a prompt "Content-type not supported.
Because the interface fields are set when the interface is customized, and each field in the interface fields corresponds to one device parameter, the device activation server backfills each device parameter in the extracted device parameter information to the corresponding field in the interface field.
The interface verification condition is a condition for constraining the content of each field, and corresponds to a constraint condition of a device parameter corresponding to each field. Thus, the interface authentication condition may be used to authenticate device parameter information of the interface field.
If the device parameter information is verified to be correct through the interface verification condition, the device activation server returns corresponding output information to the request device.
In one embodiment, if the verification fails, the device activation server returns a second error prompt to the requesting device. The second error prompt may be a voice prompt and/or a text display prompt, such as a prompt for "parameter error 400".
The method and the device can realize the request of any interface endpoint to the corresponding interface based on the http protocol.
Taking java language as an example, in order to better cope with software midway change, demand change and parameter verification change, grovvy script language is adopted as generated configuration logic core code, so that the method has the advantages of better control on generating configuration code flexibility and stronger performance than drools compared with the performance change of a drools rule engine in java industry, and the interface is suitable for an optimal solution of activating and reporting information interfaces for enterprise digital equipment networking.
The program core service logic is updated through the script language, the configuration, namely the software is released, and the 0-code maintenance is realized.
The universal equipment activation information reporting interface is suitable for all equipment to report the information activation function.
Different devices are stored in different databases, and the process and the engineering are realized.
The logic expression is generated by adopting java grovvy, and compared with other methods, the logic expression has high performance and high concurrency by adopting java grovvy.
Fig. 3 is a block diagram of an interface generating apparatus according to an embodiment of the present application; referring to fig. 3, the interface generating apparatus includes:
a parameter obtaining module 100, configured to receive configuration parameters of a user through a visual interface generation interface;
the configuration parameters at least comprise a configured interface request mode, a returned content type, an interface field, an interface condition and an interface endpoint;
the interface field represents the equipment parameter information required to be sent by the equipment;
the interface condition at least comprises an interface verification condition, and the interface verification condition is used for verifying the equipment parameter information corresponding to the interface field;
the script file generating module 200 is configured to generate a corresponding script file according to the configuration parameters and the script file template;
an interface address generating module 300, configured to generate an interface address associated with the script file;
the issuing module 400 issues the interface corresponding to the interface address;
the storage module 500 is configured to store the issued interface information of the interface in an interface information table, where the interface information table at least includes an interface endpoint.
In one embodiment, the interface generating apparatus further includes:
and the test module is used for testing the interface.
In one embodiment, the interface address generating module 300 specifically includes:
the information extraction module is used for acquiring a server domain name, a current version number of an interface to be issued and an interface endpoint;
and the generating module is used for generating an interface address associated with the script file according to the server domain name, the current version number and the interface endpoint.
In one embodiment, the interface generating apparatus further includes:
the parameter obtaining module 100 is further configured to receive a configuration parameter change of a user through a visual interface generation interface;
the updating module is used for updating the script file and the interface address of the generated interface according to the changed configuration parameters;
the publishing module 400 is further configured to republish the generated interface.
In one embodiment, the updating module is further configured to update the interface information table.
For example, the current interface version, interface field, etc. in the interface information table are updated.
Fig. 4 is a block diagram of an interface request apparatus according to an embodiment of the present application; the interface request device includes:
the request receiving module 010 is configured to receive an interface request of the device to be reported, where the interface request carries an interface endpoint of a device to be reported, and a device parameter information packet;
the first judging module 020 is used for judging whether an interface endpoint of the interface to be called exists in the generated interface information table;
the calling module 030 is configured to load a script file corresponding to the interface to be called if the interface endpoint of the interface to be called exists in the generated interface information table;
the verification module 040 is configured to verify the device parameter information in the device parameter information data packet according to the script file corresponding to the interface to be called;
and the sending module 050 is used for returning output information to the equipment to be reported if the verification is successful.
In one embodiment, the interface request device further comprises:
and the error reporting module is used for returning a first error reporting prompt to the request equipment if the interface endpoint of the interface to be called does not exist in the generated interface information table.
In one embodiment, the verification module 040 specifically includes:
the first analysis module is used for analyzing the script file corresponding to the interface to be called so as to obtain an interface request mode, a returned content type and an interface verification condition;
the data packet acquisition module is used for requesting to acquire a device parameter information data packet in an interface request mode;
the second analysis module is used for analyzing the equipment parameter information data packet in an analysis mode corresponding to the returned content type if the request for obtaining the equipment parameter information data packet is successful;
a backfill module for backfilling the device parameter information in the device parameter information data packet to the interface field if the analysis is successful,
and the sub-verification module is used for verifying the equipment parameter information of the interface field according to the interface verification condition.
Fig. 5 is an application scenario diagram of an interface generation method and an interface request method according to an embodiment of the present application. Referring to fig. 5, the Web middle management server reports the background server of the control platform for the general device of the present application. The Web middle station management server stores a script file template and codes for supporting a foreground display interface of the universal equipment report control platform. The user reports an interface generation interface in the front-end display interface of the control platform through the universal equipment, can self-define various parameters of the interface to be generated so as to generate a script file and an interface address of a new interface, and updates the information of the new interface into an interface information table. After the Web middle management server releases the interface corresponding to the interface address, the grovvy script file and the interface information table of the new interface are synchronized to the equipment activation server.
The user reports an interface generation interface in the front-end display interface of the control platform through the general equipment, and can also change a plurality of changeable parameters of the generated interface so as to update the script file and the interface address of the generated interface and store the updated information of the interface into an interface information table. The Web central management server also synchronizes the updated script file and interface information table to the device activation server again.
The device activation server may communicate with a plurality of devices (device 1, device 2, device 3, etc.) via an internet network. The device activation server may receive an interface request of any one device, and determine whether an interface endpoint of an interface to be called in the interface request exists in the generated interface information table. If the interface endpoint of the interface to be called exists in the generated interface information table, the equipment activation server loads a script file corresponding to the interface to be called; verifying the equipment parameter information in the equipment parameter information data packet according to the script file corresponding to the interface to be called; and if the verification is successful, the equipment activation server returns output information to the equipment sending the interface request.
The equipment can be various electronic equipment which can be connected with a network, such as a desktop computer, a television, a microwave oven, a refrigerator, a mobile phone, a tablet personal computer, a notebook computer, a router, a washing machine, a radio and television device, a television box and the like.
In one embodiment, a computer device is provided, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program: receiving configuration parameters of a user through a visual interface generation interface; the configuration parameters at least comprise a configured interface request mode, a returned content type, an interface field, an interface condition and an interface endpoint; the interface field represents the equipment parameter information required to be sent by the equipment; the interface condition at least comprises an interface verification condition, and the interface verification condition is used for verifying the equipment parameter information corresponding to the interface field; generating a corresponding script file according to the configuration parameters and the script file template; generating an interface address associated with the script file; issuing an interface corresponding to the interface address; and storing the issued interface information of the interface in an interface information table, wherein the interface information table at least comprises interface endpoints.
In one embodiment, the processor, when executing the computer program, further implements the steps of any of the above-described interface generation methods.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of: receiving configuration parameters of a user through a visual interface generation interface; the configuration parameters at least comprise a configured interface request mode, a returned content type, an interface field, an interface condition and an interface endpoint; the interface field represents the equipment parameter information required to be sent by the equipment; the interface condition at least comprises an interface verification condition, and the interface verification condition is used for verifying the equipment parameter information corresponding to the interface field; generating a corresponding script file according to the configuration parameters and the script file template; generating an interface address associated with the script file; issuing an interface corresponding to the interface address; and storing the issued interface information of the interface in an interface information table, wherein the interface information table at least comprises interface endpoints.
In one embodiment, the computer program, when executed by the processor, further implements the steps of any of the interface generation methods described above.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of: receiving an interface request of a request device, wherein the interface request carries an interface endpoint of an interface to be called of the request device and a device parameter information data packet; judging whether an interface endpoint of the interface to be called exists in the generated interface information table or not; if the interface endpoint of the interface to be called exists in the generated interface information table, loading a script file corresponding to the interface to be called; verifying the equipment parameter information in the equipment parameter information data packet according to the script file corresponding to the interface to be called; and if the verification is successful, returning output information to the request equipment.
In one embodiment, the computer program, when executed by the processor, further performs the steps of any of the interface request methods described above.
In one embodiment, a computer device is provided, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program: receiving an interface request of a request device, wherein the interface request carries an interface endpoint of an interface to be called of the request device and a device parameter information data packet; judging whether an interface endpoint of the interface to be called exists in the generated interface information table or not; if the interface endpoint of the interface to be called exists in the generated interface information table, loading a script file corresponding to the interface to be called; verifying the equipment parameter information in the equipment parameter information data packet according to the script file corresponding to the interface to be called; and if the verification is successful, returning output information to the request equipment.
In one embodiment, the processor, when executing the computer program, further performs the steps of any of the interface request methods described above.
It is noted that, in this document, relational terms such as "first" and "second," and the like, may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The foregoing are merely exemplary embodiments of the present invention, which enable those skilled in the art to understand or practice the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. An interface generation method, comprising:
receiving configuration parameters through a visual interface generation interface;
the configuration parameters at least comprise a configured interface request mode, a returned content type, an interface field, an interface condition and an interface endpoint;
the interface field represents equipment parameter information required to be sent by equipment;
the interface condition at least comprises an interface verification condition, and the interface verification condition is used for verifying the equipment parameter information corresponding to the interface field;
generating a corresponding script file according to the configuration parameters and the script file template;
generating an interface address associated with the script file;
issuing an interface corresponding to the interface address;
storing the interface information of the issued interface in an interface information table, wherein the interface information table at least comprises the interface endpoint.
2. The method of claim 1, wherein generating the interface address associated with the script file comprises:
acquiring a server domain name, a current version number of an interface to be issued and an interface endpoint;
and generating an interface address associated with the script file according to the server domain name, the current version number and the interface endpoint.
3. The method of claim 1, wherein the interface generation method further comprises: and synchronizing the script file of the issued interface and the interface information table to the equipment activation server of each node.
4. The method of claim 1, wherein the interface generation method further comprises:
receiving the change configuration parameters of a user through the visual interface generation interface;
updating the script file and the interface address corresponding to the generated interface according to the changed configuration parameters;
reissuing the generated interface.
5. An interface request method, characterized in that the interface request method comprises:
receiving an interface request of a request device, wherein the interface request carries an interface endpoint of an interface to be called of the request device and a device parameter information data packet;
judging whether the interface endpoint of the interface to be called exists in the generated interface information table or not;
if the interface endpoint of the interface to be called exists in the generated interface information table, loading a script file corresponding to the interface to be called;
verifying the equipment parameter information in the equipment parameter information data packet according to the script file corresponding to the interface to be called;
if the verification is successful, returning output information to the request equipment;
the generated interface information table and the script file corresponding to the interface to be called are generated according to the interface generation method of any one of claims 1 to 4.
6. The interface request method according to claim 5, further comprising:
and if the interface endpoint of the interface to be called does not exist in the generated interface information table, returning a first error prompt to the request equipment.
7. The interface request method according to claim 5, wherein verifying the device parameter information in the device parameter information packet according to the script file corresponding to the interface to be called includes:
analyzing the script file corresponding to the interface to be called to obtain an interface request mode, a returned content type and an interface verification condition;
requesting to acquire the equipment parameter information data packet in the interface request mode;
if the request for obtaining the equipment parameter information data packet is successful, analyzing the equipment parameter information data packet in an analysis mode corresponding to the returned content type;
if the analysis is successful, the equipment parameter information in the equipment parameter information data packet is backfilled to the interface field,
and verifying the equipment parameter information of the interface field according to the interface verification condition.
8. An interface generation apparatus, characterized in that the interface generation apparatus comprises:
the parameter acquisition module is used for receiving configuration parameters of a user through a visual interface generation interface;
the configuration parameters at least comprise a configured interface request mode, a returned content type, an interface field, an interface condition and an interface endpoint;
the interface field represents equipment parameter information required to be sent by equipment;
the interface condition at least comprises an interface verification condition, and the interface verification condition is used for verifying the equipment parameter information corresponding to the interface field;
the script file generating module is used for generating a corresponding script file according to the configuration parameters and the script file template;
the interface address generating module is used for generating an interface address associated with the script file;
the issuing module is used for issuing the interface corresponding to the interface address;
and the storage module is used for storing the issued interface information of the interface in an interface information table, and the interface information table at least comprises the interface endpoint.
9. An interface request apparatus, comprising:
the device comprises a request receiving module, a request processing module and a processing module, wherein the request receiving module is used for receiving an interface request of a request device, and the interface request carries an interface endpoint of an interface to be called of the request device and a device parameter information data packet;
the first judging module is used for judging whether the interface endpoint of the interface to be called exists in the generated interface information table or not;
the calling module is used for loading the script file corresponding to the interface to be called if the interface endpoint of the interface to be called exists in the generated interface information table;
the verification module is used for verifying the equipment parameter information in the equipment parameter information data packet according to the script file corresponding to the interface to be called;
and the sending module is used for returning output information to the request equipment if the verification is successful.
10. A computer-readable storage medium, having a computer program stored thereon, which, when executed by a processor, causes the processor to carry out the steps of the method according to any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110111992.5A CN112764751B (en) | 2021-01-27 | Interface generation method and device, interface request method and device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110111992.5A CN112764751B (en) | 2021-01-27 | Interface generation method and device, interface request method and device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112764751A true CN112764751A (en) | 2021-05-07 |
| CN112764751B CN112764751B (en) | 2024-05-24 |
Family
ID=
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113282457A (en) * | 2021-05-25 | 2021-08-20 | 山东浪潮通软信息科技有限公司 | Method, device and medium for maintaining heterogeneous system integration interface information |
| CN113485693A (en) * | 2021-06-21 | 2021-10-08 | 上海百秋电子商务有限公司 | Interface configuration method, device, equipment and storage medium |
| CN113779444A (en) * | 2021-11-12 | 2021-12-10 | 北京宇信科技集团股份有限公司 | Interface development method, zero code engine and zero code data interface development system |
| CN116560641A (en) * | 2023-04-19 | 2023-08-08 | 上海百秋智尚网络服务有限公司 | Automatic interface generation method, device, equipment and storage medium |
| WO2023160395A1 (en) * | 2022-02-28 | 2023-08-31 | 北京有竹居网络技术有限公司 | Permission-based interactive interface publishing method and apparatus, and electronic device |
Citations (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100312542A1 (en) * | 2009-06-09 | 2010-12-09 | Ryan Van Wyk | Method and System for an Interface Certification and Design Tool |
| CN102122247A (en) * | 2011-03-17 | 2011-07-13 | 深圳市同洲软件有限公司 | Automatic code generating system and method |
| WO2013107403A1 (en) * | 2012-01-20 | 2013-07-25 | 华为技术有限公司 | Method, device and system for using and invoking oauth api |
| CN104283919A (en) * | 2013-07-05 | 2015-01-14 | 中兴通讯股份有限公司 | Interface invocation system and method |
| US20170371937A1 (en) * | 2016-06-27 | 2017-12-28 | Verizon Patent And Licensing Inc. | Automated api publication for internet of things platform |
| US9935984B1 (en) * | 2017-07-31 | 2018-04-03 | Malwarebytes Inc. | Scalable cloud-based endpoint security system |
| CN108228173A (en) * | 2018-01-16 | 2018-06-29 | 北明软件有限公司 | A kind of visual data-interface development system and method |
| CN108446225A (en) * | 2018-03-06 | 2018-08-24 | 平安科技（深圳）有限公司 | Creating device, method and the computer readable storage medium of analog interface |
| CN109150805A (en) * | 2017-06-19 | 2019-01-04 | 亿阳安全技术有限公司 | The method for managing security and system of application programming interface |
| CN110286897A (en) * | 2019-05-22 | 2019-09-27 | 深圳壹账通智能科技有限公司 | API Visual Dynamic configuration method, device, equipment and storage medium |
| US10489224B1 (en) * | 2018-07-30 | 2019-11-26 | International Business Machines Corporation | Managing application programming interface requests |
| CN111045756A (en) * | 2019-12-10 | 2020-04-21 | 中国工商银行股份有限公司 | Method, apparatus, computing device, and medium for generating interface service |
| CN111124474A (en) * | 2018-10-31 | 2020-05-08 | 北京数聚鑫云信息技术有限公司 | API version control method and device |
| US20200183711A1 (en) * | 2018-12-05 | 2020-06-11 | Visa International Service Association | Method, System, and Computer Program Product for Dynamic Development of an Application Programming Interface |
| CN111367547A (en) * | 2020-02-27 | 2020-07-03 | 平安国际智慧城市科技股份有限公司 | Automatic interface code synchronization method, device and storage medium |
| US20200226185A1 (en) * | 2019-01-11 | 2020-07-16 | Vmware, Inc. | Publishing rest api changes based on subscriber's customized request |
| CN111459466A (en) * | 2020-03-31 | 2020-07-28 | 广州酷狗计算机科技有限公司 | Code generation method, device, equipment and storage medium |
| US20200396225A1 (en) * | 2019-06-17 | 2020-12-17 | Sap Se | Microservice Deployment |
Patent Citations (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100312542A1 (en) * | 2009-06-09 | 2010-12-09 | Ryan Van Wyk | Method and System for an Interface Certification and Design Tool |
| CN102122247A (en) * | 2011-03-17 | 2011-07-13 | 深圳市同洲软件有限公司 | Automatic code generating system and method |
| WO2013107403A1 (en) * | 2012-01-20 | 2013-07-25 | 华为技术有限公司 | Method, device and system for using and invoking oauth api |
| CN104283919A (en) * | 2013-07-05 | 2015-01-14 | 中兴通讯股份有限公司 | Interface invocation system and method |
| US20170371937A1 (en) * | 2016-06-27 | 2017-12-28 | Verizon Patent And Licensing Inc. | Automated api publication for internet of things platform |
| CN109150805A (en) * | 2017-06-19 | 2019-01-04 | 亿阳安全技术有限公司 | The method for managing security and system of application programming interface |
| US9935984B1 (en) * | 2017-07-31 | 2018-04-03 | Malwarebytes Inc. | Scalable cloud-based endpoint security system |
| CN108228173A (en) * | 2018-01-16 | 2018-06-29 | 北明软件有限公司 | A kind of visual data-interface development system and method |
| CN108446225A (en) * | 2018-03-06 | 2018-08-24 | 平安科技（深圳）有限公司 | Creating device, method and the computer readable storage medium of analog interface |
| US10489224B1 (en) * | 2018-07-30 | 2019-11-26 | International Business Machines Corporation | Managing application programming interface requests |
| CN111124474A (en) * | 2018-10-31 | 2020-05-08 | 北京数聚鑫云信息技术有限公司 | API version control method and device |
| US20200183711A1 (en) * | 2018-12-05 | 2020-06-11 | Visa International Service Association | Method, System, and Computer Program Product for Dynamic Development of an Application Programming Interface |
| US20200226185A1 (en) * | 2019-01-11 | 2020-07-16 | Vmware, Inc. | Publishing rest api changes based on subscriber's customized request |
| CN110286897A (en) * | 2019-05-22 | 2019-09-27 | 深圳壹账通智能科技有限公司 | API Visual Dynamic configuration method, device, equipment and storage medium |
| US20200396225A1 (en) * | 2019-06-17 | 2020-12-17 | Sap Se | Microservice Deployment |
| CN111045756A (en) * | 2019-12-10 | 2020-04-21 | 中国工商银行股份有限公司 | Method, apparatus, computing device, and medium for generating interface service |
| CN111367547A (en) * | 2020-02-27 | 2020-07-03 | 平安国际智慧城市科技股份有限公司 | Automatic interface code synchronization method, device and storage medium |
| CN111459466A (en) * | 2020-03-31 | 2020-07-28 | 广州酷狗计算机科技有限公司 | Code generation method, device, equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| HANSON_1999: "aliyun物联网平台搭建MQTT环境", Retrieved from the Internet <URL:https://blog.csdn.net/qq_43260665/article/details/97620834> * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113282457A (en) * | 2021-05-25 | 2021-08-20 | 山东浪潮通软信息科技有限公司 | Method, device and medium for maintaining heterogeneous system integration interface information |
| CN113485693A (en) * | 2021-06-21 | 2021-10-08 | 上海百秋电子商务有限公司 | Interface configuration method, device, equipment and storage medium |
| CN113485693B (en) * | 2021-06-21 | 2023-06-16 | 上海百秋新网商数字科技有限公司 | Interface configuration method, device, equipment and storage medium |
| CN113779444A (en) * | 2021-11-12 | 2021-12-10 | 北京宇信科技集团股份有限公司 | Interface development method, zero code engine and zero code data interface development system |
| WO2023160395A1 (en) * | 2022-02-28 | 2023-08-31 | 北京有竹居网络技术有限公司 | Permission-based interactive interface publishing method and apparatus, and electronic device |
| CN116560641A (en) * | 2023-04-19 | 2023-08-08 | 上海百秋智尚网络服务有限公司 | Automatic interface generation method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109840429B (en) | Intelligent contract deployment and calling method and device | |
| CN108829378B (en) | Application software development method and device and electronic equipment | |
| CN110324169B (en) | Interface management method and device | |
| CN109542445A (en) | A kind of method and apparatus that Android plug-in unit melts hair | |
| US20110307238A1 (en) | Methods for utilizing a javascript emulator in a web content proxy server and devices thereof | |
| CN111580820A (en) | Applet generation method and device | |
| TW201439792A (en) | System and method for accessing database | |
| CN110959165A (en) | Techniques for automatically verifying functionality of offers in a cloud service broker system | |
| CN109391673A (en) | A kind of method, system and the terminal device of management update file | |
| CN107025108B (en) | Exporting hierarchical data from a Source Code Management (SCM) system to a Product Lifecycle Management (PLM) system | |
| CN110162464A (en) | Mcok test method and system, electronic equipment and readable storage medium storing program for executing | |
| CN110262821A (en) | A kind of management method of software module, device and server | |
| CN109032620A (en) | The configuration file generation method and device of application program | |
| CN110750243A (en) | Project code development method and system | |
| CN116257438A (en) | Updating method of interface test case and related equipment | |
| CN101876998A (en) | Method and system for editing data | |
| CN113779004A (en) | Data verification method and device | |
| CN110674426B (en) | Webpage behavior reporting method and device | |
| CN116431200A (en) | Configuration method, device, equipment and storage medium for application data configuration information | |
| CN112256989A (en) | Page loading method and device based on offline package, terminal equipment and storage medium | |
| CN112764751B (en) | Interface generation method and device, interface request method and device and storage medium | |
| WO2019233454A1 (en) | Chain code upgrading method and device | |
| CN111090442A (en) | Application updating method and device and storage medium | |
| CN112764751A (en) | Interface generation method and device, interface request method and device and storage medium | |
| CN115878860A (en) | Menu generation method, device, server equipment and medium |
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 | ||
| GR01 | Patent grant |