CN117348950A - Service interface calling method and system based on scene engine - Google Patents
Service interface calling method and system based on scene engine Download PDFInfo
- Publication number
- CN117348950A CN117348950A CN202311231355.7A CN202311231355A CN117348950A CN 117348950 A CN117348950 A CN 117348950A CN 202311231355 A CN202311231355 A CN 202311231355A CN 117348950 A CN117348950 A CN 117348950A
- Authority
- CN
- China
- Prior art keywords
- scene
- module
- interface
- service
- unit
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 33
- 238000012545 processing Methods 0.000 claims abstract description 26
- 238000000605 extraction Methods 0.000 claims abstract description 8
- 238000004806 packaging method and process Methods 0.000 claims description 30
- 238000012856 packing Methods 0.000 claims description 3
- 230000033772 system development Effects 0.000 abstract description 3
- 230000018109 developmental process Effects 0.000 description 4
- 210000001503 joint Anatomy 0.000 description 3
- 238000003032 molecular docking Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 238000005538 encapsulation Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000009466 transformation Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
Classifications
-
- 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/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4488—Object-oriented
- G06F9/449—Object-oriented method invocation or resolution
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a service interface calling method and a service interface calling system based on a scene engine, wherein the service interface calling method comprises the following steps: the system comprises a control unit, a micro-service system, a scene registration unit and a scene service unit; the control unit is connected with the micro-service system and comprises a micro-service system resource extraction module and a resource processing module; the resource extraction module is connected with the resource processing module and is used for reading the interface unit information and sending the information to the resource processing module, and the resource processing module packages the interface unit into a corresponding scene unit; the control unit is connected with the scene registration unit, the scene registration unit is connected with the scene service unit, and the scene registration unit registers the packaged scene unit information to the scene service unit; by carrying out operation processing such as serial connection and the like on all the interface information which is already in scene in the scene service unit, the original micro service system is not changed, meanwhile, the operation is convenient and fast, and the difficulty of system development is reduced; in addition, the invention sets the judging module, and the same dependency attribute or path information in the interface module is processed and managed in a unified way, thereby saving system resources.
Description
Technical Field
The invention relates to the field of micro-service architecture of software systems, in particular to a service interface calling method and a service interface calling system for a scene engine.
Background
In a typical software system microservice architecture system, a relatively large complex software application system is composed of one or a plurality of microservices, the plurality of microservices in the software application system can be deployed independently, and the microservices are mutually matched in a loose coupling manner, wherein each microservice is used for completing a task or realizing a function. Each system mainly uses the way the interface calls access other resources. When the system is called with other external systems, the system also mainly depends on the modes such as an API interface or an SDK provided by the external systems to directly call.
An API (Application programming interface ) is a manner of accessing and exchanging information between software systems, and defines a manner of calling one application (or service) in another application (or service), and the API interface can enable an developer to interact only through the interface without knowing specific implementation details inside the program, so that the reusability of software is improved, and typically, the API interface includes functions, protocols, data interfaces, tools, and the like. The API may be accessed by calling http, and typically the API interface includes the following steps, namely: acquiring an API key, determining a request terminal address of an API (acquiring an API document), writing codes according to the API document to call the API, and analyzing an API response to meet service requirements. SDK (Software Development Kit) refers to a software development kit, generally refers to a collection of development tools when a software developer builds application software for a purpose-built software package, software framework, hardware platform, operating system, or the like. In particular, an API is a functional interface that cannot run independently, and can only function if connected to a server. And the SDK is a software development tool, and comprises functions and function interfaces, and can independently run.
In the prior art, no matter the micro-service system is called by adopting an API interface or an SDK interface mode, the butt joint between different micro-service systems depends on the transformation of a certain system, even the transformation of a plurality of systems, and the original system cannot be maintained. As shown in the conventional system docking mode of FIG. 1, two systems are respectively a system A and a system B, wherein the system A is provided with three interfaces of an interface a1, an interface a2 and an interface a3, and the system B is provided with three interfaces of an interface B1, an interface B2 and an interface B3. In the conventional docking mode, if the interface b is intended to be used while the interface a is used, the interface a needs to be modified to be changed into the interface a 'so that the interface b can be called in the interface a', and at this time, the system a has been changed. Therefore, when different micro-service systems are in butt joint each time, the modification of interfaces of the micro-service systems is involved, the workload and the operation complexity of the butt joint are increased, the difficulty of system development is also increased, and the change of system requirements cannot be flexibly dealt with.
Disclosure of Invention
In order to reduce inter-dependencies between internal systems and between internal and external systems. The new design thought is provided, and a new scheme is provided for the series connection of different systems by using a scene engine.
Aiming at the technical problems, the invention provides a service interface calling method based on a scene engine, which can integrate scenes in different micro-service systems into one scene service to realize the purpose of conveniently processing a plurality of micro-service systems through one scene service.
S01: determining the type of an interface unit in the micro-service system;
the first micro service system may have a plurality of interface units, and the number of the interface units may be three, namely an a interface unit, a B interface unit and a C interface unit;
s02: packaging interface units in the micro-service system into different scene units through an abstract method, wherein the scene units are in one-to-one correspondence with the interface units;
the three scene units are a first scene unit, a second scene unit and a third scene unit respectively, specifically, an interface unit A is packaged into an A scene unit, an interface unit B is packaged into a B scene unit, and an interface unit C is packaged into a C scene unit;
s03: packaging the scene units to form a plug-in module, wherein the plug-in module corresponds to the micro-service system;
packaging the first scene unit, the second scene unit and the third scene unit to form a plug-in module, wherein the first plug-in module corresponds to the micro-service system;
s04: judging whether a plurality of scene units needing packing exist or not, if yes, executing the steps S01-S03, and if no, executing the step S05;
the method comprises the steps that a plurality of scene units in one micro-service system are packed to form a plug-in module, scene units in different micro-service systems cannot be mixed and packed, and preferably, a first micro-service system, a second micro-service system and a third micro-service system can be packed to form a first plug-in module, a first plug-in module and a first plug-in module respectively;
packaging, namely packaging an A interface unit in a first micro-service system into an A scene unit, packaging a B interface unit into a B scene unit, and packaging a C interface unit into a C scene unit; packaging an A 'interface unit in the second micro-service system into an A' scene unit, packaging a B 'interface unit into a B' scene unit, and packaging a C 'interface unit into a C' scene unit; packaging an A interface unit in a third micro-service system into an A scene unit, packaging a B interface unit into a B scene unit, and packaging a C interface unit into a C scene unit;
s05: registering the plug-in module into a scene service module, wherein the scene service module can analyze and record scene contents in the plug-in module;
s06: the scene service module outputs the recorded and parsed plug-in module scene content to the operation logic module;
the operation logic module can perform logic operation on the scene contents in the plug-in module, and judge the logic sequence relation of the scene contents;
s07: and according to the judgment result of the operation logic module, connecting a plurality of scenes in the plug-in module in series so as to meet the actual service requirement.
Further, if the second micro service system needs to be executed after the first micro service system, the a 'scene unit may be executed after the a scene unit is executed according to the above-mentioned encapsulation correspondence, so that the a' interface unit may be executed simultaneously when the a interface unit is executed. Because the system flow is created and executed in the scene service module, the original first micro service system and second micro service system are not affected.
In order to achieve the above object, according to another aspect of the present invention, a service interface calling method based on a scene engine is provided, which can further save system call resources.
S01': determining the type of an interface unit in a micro-service system, and determining an interface template of each interface unit through an abstract method;
the micro service system may have a plurality of interface units, and the abstracted interface template includes dependency attribute and path information of the interface units, preferably, the interface units may be three.
S02': after abstracting the first interface unit into the first interface template, abstracting the second interface unit and judging whether the dependency attribute and path information of the second interface unit are included in the first interface template, if so, executing the step S03', and repeatedly executing the step S01', until all the interface units are abstracted into several interface templates;
s03': packaging the interface modules into different scene units through an abstract method, wherein the scene units are in one-to-one correspondence with the interface modules;
s04': packaging the scene units to form a plug-in module, wherein the plug-in module corresponds to the micro-service system;
s05': judging whether a plurality of scene units needing to be packaged exist or not, if yes, executing the steps S01' to S04', if no, executing the step S06';
s06': registering the plug-in module into a scene service module 07, wherein the scene service module can analyze and record scene contents in the plug-in module;
s07': the scene service module outputs the recorded and parsed plug-in module scene content to the operation logic module;
the operation logic module can perform logic operation on the scene contents in the plug-in module, and judge the logic sequence relation of the scene contents;
s08: and according to the judgment result of the operation logic module, connecting a plurality of scenes in the plug-in module in series so as to meet the actual service requirement.
To achieve the above object, according to one aspect of the present invention, there is provided a service interface call system based on a scene engine, the system comprising:
the system comprises a control unit, a micro-service system, a scene registration unit and a scene service unit;
the control unit is connected with the micro-service system and comprises a micro-service system resource extraction module and a resource processing module; the resource extraction module is connected with the resource processing module and is used for reading the interface unit information and sending the information to the resource processing module, and the resource processing module packages the interface unit into a corresponding scene unit;
the control unit is connected with the scene registration unit, the scene registration unit is connected with the scene service unit, and the scene registration unit registers the packaged scene unit information to the scene service unit;
further, the control unit may include an operation logic module, where the operation logic module is connected with the resource processing module, and is configured to extract scene unit information in the resource processing module, and determine which scene units need to be processed in series;
further, the control unit may include a judging module and an interface abstract module, where the interface abstract module is configured to abstract the interface unit to form an interface template, and the interface module includes dependency attribute and path information of the interface unit, and the judging module is connected with the interface abstract module and is configured to judge whether the interface template information generated by the interface abstract module is included in an existing interface module.
The beneficial technical effects of the invention are as follows:
according to the invention, interfaces in different micro-service systems are packaged to form corresponding scenes, and the scenes in all the micro-service systems are registered into the scene service unit through the scene registration function, so that operation processing such as serial connection and the like is performed on all the interface information which is already in the scene service unit, thus the original micro-service system is not changed, the operation is convenient and fast, and the difficulty of system development is reduced; in addition, the invention sets the judging module, and the same dependency attribute or path information in the interface module is processed and managed in a unified way, thereby saving system resources.
Drawings
FIG. 1 is a schematic diagram of a prior art docking of different microservice systems
FIG. 2 is a flow chart of a method of service interface invocation based on a scene engine
FIG. 3 is a flow chart of another method of context engine based service interface invocation
FIG. 4 is a system diagram of a scene engine based service interface call
Detailed Description
The present invention will be described in detail with reference to specific embodiments and the accompanying drawings so that those skilled in the art can clearly and accurately understand the technical solutions of the present invention.
It should be clear that features between embodiments of the invention may be combined with each other without constituting a technical conflict. It should be understood that the described embodiments are merely some, but not all, embodiments of the invention. Meanwhile, all other embodiments obtained by those skilled in the art without making any creative effort based on the embodiments of the present invention are within the protection scope of the present invention.
First embodiment:
a service interface call method flowchart based on a scene engine as shown in fig. 2, comprising the steps of:
s01: determining the type of an interface unit in the micro-service system;
wherein the first micro service system 01 may have a plurality of interface units, which may be three, an a interface unit 011, a B interface unit 012, and a C interface unit 013;
s02: packaging interface units in the micro-service system into different scene units through an abstract method, wherein the scene units are in one-to-one correspondence with the interface units;
the number of the scene units may be three, namely a first scene unit 041, a second scene unit 042 and a third scene unit 043, specifically, an a interface unit 011 is encapsulated as an a scene unit 041, a B interface unit 012 is encapsulated as a B scene unit 042, and a C interface unit 013 is encapsulated as a C scene unit 043;
s03: packaging the scene units to form a plug-in module, wherein the plug-in module corresponds to the micro-service system;
packaging a first scene unit 041, a second scene unit 042 and a third scene unit 043 to form a plug-in module 04, wherein the first plug-in module 04 corresponds to the micro-service system 01;
s04: judging whether a plurality of scene units needing packing exist or not, if yes, executing the steps S01-S03, and if no, executing the step S05;
wherein, a plurality of scene units in one micro service system are packed to form a plug-in module, the scene units in different micro service systems cannot be mixed and packed, preferably, the first micro service system 01, the second micro service system 02 and the third micro service system 03 can be respectively packed to form a first plug-in module 04, a first plug-in module 05 and a first plug-in module 06;
packaging, namely packaging an A interface unit 011 in the first micro service system 01 into an A scene unit 041, packaging a B interface unit 012 into a B scene unit 042 and packaging a C interface unit 013 into a C scene unit 043; packaging an A 'interface unit 021 in the second micro service system 02 into an A' scene unit 051, a B 'interface unit 022 into a B' scene unit 052, and a C 'interface unit 023 into a C' scene unit 053; packaging an A interface unit 031 in the third micro service system 03 as an A scene unit 061, a B interface unit 032 as a B scene unit 062, and a C interface unit 033 as a C scene unit 063;
s05: registering the plug-in module into a scene service module 07, wherein the scene service module can analyze and record scene contents in the plug-in module;
s06: the scene service module outputs the recorded and parsed plug-in module scene content to the operation logic module;
the operation logic module can perform logic operation on the scene contents in the plug-in module, and judge the logic sequence relation of the scene contents;
s07: and according to the judgment result of the operation logic module, connecting a plurality of scenes in the plug-in module in series so as to meet the actual service requirement.
Wherein, the scene service module 07 includes an a scene unit 041, a B scene unit 042, a C scene unit 043, an a ' scene unit 051, a B ' scene unit 052, a C ' scene unit 053, an a "scene unit 061, a B" scene unit 062 and a C "scene unit 063; in this way, the series micro service flow can be directly created by the scene service module 07, preferably, if the second micro service system 02 needs to be executed after the first micro service system 01, the a 'scene unit 051 can be executed after the a scene unit 041 is executed according to the above-mentioned encapsulation correspondence, so that the a' interface unit 021 can be executed simultaneously when the a interface unit 011 is executed. Because the system flow is created and executed in the scene service module, the original first micro service system 01 and the second micro service system 02 are not affected.
Specific embodiment II:
based on the same inventive concept, the invention provides another service interface calling method based on a scene engine, as shown in fig. 3, comprising the following steps:
s01': determining the type of an interface unit in a micro-service system, and determining an interface template of each interface unit through an abstract method;
the micro service system may have a plurality of interface units, and the abstracted interface template includes dependency attribute and path information of the interface units, preferably, the interface units may be three.
S02': after abstracting the first interface unit into the first interface template, abstracting the second interface unit and judging whether the dependency attribute and path information of the second interface unit are included in the first interface template, if so, executing the step S03', and repeatedly executing the step S01', until all the interface units are abstracted into several interface templates;
s03': packaging the interface modules into different scene units through an abstract method, wherein the scene units are in one-to-one correspondence with the interface modules;
s04': packaging the scene units to form a plug-in module, wherein the plug-in module corresponds to the micro-service system;
s05': judging whether a plurality of scene units needing to be packaged exist or not, if yes, executing the steps S01' to S04', if no, executing the step S06';
s06': registering the plug-in module into a scene service module 07, wherein the scene service module can analyze and record scene contents in the plug-in module;
s07': the scene service module outputs the recorded and parsed plug-in module scene content to the operation logic module;
the operation logic module can perform logic operation on the scene contents in the plug-in module, and judge the logic sequence relation of the scene contents;
s08: and according to the judgment result of the operation logic module, connecting a plurality of scenes in the plug-in module in series so as to meet the actual service requirement.
Third embodiment:
based on the same inventive concept, the present embodiment provides a service interface calling system based on a scene engine, which corresponds to the service interface calling method based on the scene engine. As shown in fig. 4, the system specifically includes:
the system comprises a control unit, a micro-service system, a scene registration unit and a scene service unit;
the control unit is connected with the micro-service system and comprises a micro-service system resource extraction module and a resource processing module; the resource extraction module is connected with the resource processing module and is used for reading the interface unit information and sending the information to the resource processing module, and the resource processing module packages the interface unit into a corresponding scene unit;
the control unit is connected with the scene registration unit, the scene registration unit is connected with the scene service unit, and the scene registration unit registers the packaged scene unit information to the scene service unit;
further, the control unit may include an operation logic module, where the operation logic module is connected with the resource processing module, and is configured to extract scene unit information in the resource processing module, and determine which scene units need to be processed in series;
further, the control unit may include a judging module and an interface abstract module, where the interface abstract module is configured to abstract the interface unit to form an interface template, and the interface module includes dependency attribute and path information of the interface unit, and the judging module is connected with the interface abstract module and is configured to judge whether the interface template information generated by the interface abstract module is included in an existing interface module.
In the above embodiments of the present invention, it should be clear that the division of the units or modules in the disclosed system and method is only one logical function division, and there may be other division manners.
The functional units or modules in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone in physical form, or may exist as multiple units integrated together. The above-described manner of integration may be implemented in hardware or in hardware plus software. If the unit is integrated in the form of a software functional unit, it can be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes instructions for causing a computer device or processor to perform some of the steps of the methods described in the various embodiments of the present invention.
What has been described above is only a preferred embodiment of the present application, and the present invention is not limited to the above examples. It is to be understood that other modifications and variations which may be directly derived or contemplated by those skilled in the art without departing from the spirit and concepts of the present invention are deemed to be included within the scope of the present invention.
Claims (10)
1. A service interface calling method based on a scene engine, which is characterized by comprising the following steps:
s01: determining the type of an interface unit in the micro-service system;
s02: packaging interface units in the micro-service system into different scene units through an abstract method, wherein the scene units are in one-to-one correspondence with the interface units;
s03: packaging the scene units to form a plug-in module, wherein the plug-in module corresponds to the micro-service system;
s04: judging whether a plurality of scene units needing packing exist or not, if yes, executing the steps S01-S03, and if no, executing the step S05;
s05: registering the plug-in module into a scene service module, wherein the scene service module can analyze and record scene contents in the plug-in module;
s06: the scene service module outputs the recorded and parsed plug-in module scene content to the operation logic module;
s07: and according to the judgment result of the operation logic module, connecting a plurality of scenes in the plug-in module in series so as to meet the actual service requirement.
2. The service interface calling method based on the scene engine according to claim 1, wherein the number of interface units in the micro service system is three, and the number of corresponding scene units is also three.
3. The service interface calling method based on the scene engine according to claim 2, wherein a plurality of scene units in one micro-service system are packed to form a plug-in module, and scene units in different micro-service systems cannot be mixed and packed.
4. The service interface calling method based on the scene engine according to claim 3, wherein the operation logic module can perform logic operation on the scene contents in the plug-in module, and determine the logic sequence relation of the plurality of scene contents.
5. A service interface calling method based on a scene engine, which is characterized by comprising the following steps:
s01': determining the type of an interface unit in a micro-service system, and determining an interface template of each interface unit through an abstract method;
s02': after abstracting the first interface unit into the first interface template, abstracting the second interface unit and judging whether the dependency attribute and path information of the second interface unit are already included in the first interface template, if so, executing step S03', and repeatedly executing S01', until all the interface units are abstracted into the interface template;
s03': packaging the interface modules into different scene units through an abstract method, wherein the scene units are in one-to-one correspondence with the interface modules;
s04': packaging the scene units to form a plug-in module, wherein the plug-in module corresponds to the micro-service system;
s05': judging whether a plurality of scene units needing to be packaged exist or not, if yes, executing the steps S01' to S04', if no, executing the step S06';
s06': registering the plug-in module into a scene service module 07, wherein the scene service module can analyze and record scene contents in the plug-in module;
s07': the scene service module outputs the recorded and parsed plug-in module scene content to the operation logic module;
s08: and according to the judgment result of the operation logic module, connecting a plurality of scenes in the plug-in module in series so as to meet the actual service requirement.
6. The service interface calling method based on the scene engine according to claim 5, wherein the number of interface units in the micro service system is three, and the number of corresponding scene units is also three.
7. The service interface calling method based on the scene engine according to claim 6, wherein the operation logic module can perform logic operation on the scene contents in the plug-in module, and determine the logic sequence relation of the plurality of scene contents.
8. A service interface calling system adopting the service interface method comprises a control unit, a micro service system, a scene registration unit and a scene service unit; it is characterized in that the method comprises the steps of,
the control unit is connected with the micro-service system and comprises a micro-service system resource extraction module and a resource processing module; the resource extraction module is connected with the resource processing module and is used for reading the interface unit information and sending the information to the resource processing module, and the resource processing module packages the interface unit into a corresponding scene unit;
the control unit is connected with the scene registration unit, the scene registration unit is connected with the scene service unit, and the scene registration unit registers the packaged scene unit information to the scene service unit.
9. The service interface calling system according to claim 8, wherein the control unit includes an arithmetic logic module, and the arithmetic logic module is connected to the resource processing module, and is configured to extract scene unit information in the resource processing module, and determine which scene units need to be processed in series.
10. The service interface calling system according to claim 9, wherein the control unit includes a judging module and an interface abstract module, the interface abstract module is used for abstracting the interface unit to form an interface template, the interface module includes dependency attribute and path information of the interface unit, and the judging module is connected with the interface abstract module and is used for judging whether the interface template information generated by the interface abstract module is included in an existing interface module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311231355.7A CN117348950A (en) | 2023-09-22 | 2023-09-22 | Service interface calling method and system based on scene engine |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311231355.7A CN117348950A (en) | 2023-09-22 | 2023-09-22 | Service interface calling method and system based on scene engine |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117348950A true CN117348950A (en) | 2024-01-05 |
Family
ID=89356659
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311231355.7A Pending CN117348950A (en) | 2023-09-22 | 2023-09-22 | Service interface calling method and system based on scene engine |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117348950A (en) |
-
2023
- 2023-09-22 CN CN202311231355.7A patent/CN117348950A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108255545B (en) | Function calling method and device between components and modular architecture system | |
| CN110601880A (en) | Cloud platform, service processing method, command interface and computer equipment | |
| CN113407362A (en) | SOMEIP communication intermediate layer implementation method and system based on SOA architecture of vehicle-mounted Android system | |
| CN110727581B (en) | Crash positioning method and electronic equipment | |
| CN112667305A (en) | Page display method and device | |
| CN114579194B (en) | Exception handling method and system based on Spring remote call | |
| CN111338716A (en) | Data processing method and device based on rule engine and terminal equipment | |
| CN111045746B (en) | Code expansion method and framework | |
| EP3640805A1 (en) | Method and apparatus for implementing white-box otn hardware device, and storage medium | |
| CN112905271A (en) | Calling method and device of application program interface API and electronic equipment | |
| CN117348950A (en) | Service interface calling method and system based on scene engine | |
| CN113900633A (en) | Low-code development method and device for scene of Internet of things, storage medium and development platform | |
| CN112579212A (en) | Cross-language calling method, calling party device and called party device | |
| CN116302808A (en) | Method, device, equipment and storage medium for capturing and processing abnormal information | |
| CN113961194B (en) | Flutter cross-application-based engineering construction method, system, terminal and medium | |
| CN115269040A (en) | Tenant business application expanding method, device and system | |
| CN109254856A (en) | Intelligent POS server-side provides interface to the method for client | |
| CN114936368A (en) | Java memory Trojan detection method, terminal device and storage medium | |
| CN113282541A (en) | File calling method and device and electronic equipment | |
| CN113094086A (en) | Component integration method and device, computer-readable storage medium and electronic equipment | |
| CN114237758B (en) | Communication connection method, device, electronic equipment and computer readable storage medium | |
| CN115878282A (en) | Cross-platform interaction method, device and equipment | |
| CN113468893B (en) | Semantic-based sharing collaboration method and device | |
| CN114816385B (en) | Integration method, device and equipment of heterogeneous system and storage medium | |
| CN114757149B (en) | Data dictionary processing method and device, medium and electronic equipment |
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 |