CN112306710A - Service processing system, interface calling method and device - Google Patents
Service processing system, interface calling method and device Download PDFInfo
- Publication number
- CN112306710A CN112306710A CN202011124629.9A CN202011124629A CN112306710A CN 112306710 A CN112306710 A CN 112306710A CN 202011124629 A CN202011124629 A CN 202011124629A CN 112306710 A CN112306710 A CN 112306710A
- Authority
- CN
- China
- Prior art keywords
- platform
- interface
- configuration
- service
- configuration 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 52
- 238000012545 processing Methods 0.000 title abstract description 18
- 230000008859 change Effects 0.000 claims description 15
- 238000004590 computer program Methods 0.000 claims description 15
- 238000012217 deletion Methods 0.000 claims description 7
- 230000037430 deletion Effects 0.000 claims description 7
- 230000006870 function Effects 0.000 description 14
- 238000010586 diagram Methods 0.000 description 12
- 230000006872 improvement Effects 0.000 description 9
- 230000008569 process Effects 0.000 description 9
- 238000004891 communication Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 5
- 235000010627 Phaseolus vulgaris Nutrition 0.000 description 3
- 244000046052 Phaseolus vulgaris Species 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 229920001296 polysiloxane Polymers 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
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/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/549—Remote execution
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The present specification discloses a service processing system, an interface calling method and an interface calling device, where a first platform may obtain, for each second platform, interface configuration information corresponding to a service type supported by the second platform from a configuration platform, and use the interface configuration information as target configuration information, and generate a service interface carrier corresponding to the second platform according to the target configuration information. Then, the first platform can call the service interface corresponding to the second platform to send a data request from the second platform through the generated service interface carrier, so as to acquire the service data required by the user from the second platform, thereby improving the working efficiency of developers.
Description
Technical Field
The present specification relates to the field of computer technologies, and in particular, to a service processing system, an interface calling method, and an interface calling device.
Background
In practical application, the service platform may include various other services besides the own service, for example, the service platform may include a taxi-taking service, a takeout service, and the like besides a group purchase service operated by the service platform itself, and the service platform needs to access service interfaces corresponding to the services, so that a user can execute the services in the service platform.
In the prior art, a service platform is usually separated from a system corresponding to each other service, where the service platform is referred to as a first platform, and a system corresponding to each other service is referred to as a second platform, and when the first platform needs to access a service interface of a certain second platform, not only developers of the second platform are required to implement a function of the service interface, but also developers of the first platform are required to implement a code for accessing the service interface, so that service processing related to the second platform can be completed through the service interface.
Disclosure of Invention
The present specification provides a service processing system, an interface calling method and an interface calling device, which are used for accessing a service interface through interface configuration information to further call the service interface.
The technical scheme adopted by the specification is as follows:
this specification provides a service processing system including: the method comprises the steps that a platform, a first platform and at least one second platform are configured, and different second platforms provide services with different service types;
the configuration platform receives a configuration request sent by a second platform, and performs interface data configuration on a service interface corresponding to the second platform according to the configuration request to obtain and store interface configuration information corresponding to the second platform;
the first platform acquires interface configuration information corresponding to the service type supported by the second platform from the configuration platform for each second platform, the interface configuration information is used as target configuration information, a service interface carrier corresponding to the second platform is generated according to the target configuration information, and a service interface corresponding to the second platform is called to send a data request from the second platform through the service interface carrier so as to acquire service data required by a user from the second platform;
the second platform acquires an interface configuration template from the first platform, sends a configuration request to the configuration platform according to the interface configuration template, receives a data request sent by the first platform, and returns the service data to the first platform according to the data request.
Optionally, the first platform is provided with a preset listener;
and if the first platform receives the configuration change message sent by the configuration platform according to the listener, determining a second platform with changed interface configuration information according to the configuration change message as a target platform, acquiring the changed interface configuration information of the target platform from the configuration platform, and changing a service interface carrier corresponding to the target platform according to the changed interface configuration information.
Optionally, the interface configuration information includes: a service warning identifier;
and if the first platform determines that the target configuration information acquired from the configuration platform contains the service warning identifier, the first platform does not call the service interface corresponding to the second platform through the service interface carrier.
Optionally, if receiving a configuration deletion request sent by the second platform, the configuration platform deletes interface configuration information corresponding to the second platform according to the configuration deletion request.
Optionally, the first platform generates a service interface carrier corresponding to the second platform according to the obtained target configuration information based on a preset SpringBean framework.
Optionally, the interface configuration template includes: a basic field, a service field and an extension field, wherein the basic field comprises: the service field is used for the second platform to provide basic data, and the extension field is used for the second platform to provide personalized data.
The present specification provides an interface calling method, including:
for each second platform, the first platform acquires interface configuration information corresponding to the service type supported by the second platform from a preset configuration platform, and the interface configuration information is used as target configuration information, the interface configuration information is determined by the configuration platform according to a configuration request sent by the second platform, and the configuration request is sent to the configuration platform by the second platform according to an interface configuration template acquired from the first platform;
generating a service interface carrier corresponding to the second platform according to the target configuration information;
and calling a service interface corresponding to the second platform to send a data request from the second platform through the service interface carrier so as to acquire service data required by the user from the second platform.
Optionally, the method further comprises:
if receiving a configuration change message sent by the configuration platform according to a preset listener, determining a second platform with changed interface configuration information as a target platform according to the configuration change message;
and acquiring the changed interface configuration information of the target platform from the configuration platform, and changing a service interface carrier corresponding to the target platform according to the changed interface configuration information.
Optionally, the interface configuration information includes: a service warning identifier;
the method further comprises the following steps:
and if the target configuration information acquired from the configuration platform contains the service warning identification, calling a service interface corresponding to the second platform through the service interface carrier is not carried out.
This specification provides an interface calling apparatus, including:
an obtaining module, configured to, for each second platform, obtain, by the device, interface configuration information corresponding to a service type supported by the second platform from a preset configuration platform, where the interface configuration information is determined by the configuration platform according to a configuration request sent by the second platform, and the configuration request is sent by the second platform to the configuration platform according to an interface configuration template obtained from the device;
a generating module, configured to generate a service interface bearer corresponding to the second platform according to the target configuration information;
and the calling module is used for calling the service interface corresponding to the second platform to send a data request from the second platform through the service interface carrier so as to acquire the service data required by the user from the second platform.
The present specification provides a computer-readable storage medium storing a computer program which, when executed by a processor, implements the above-described interface calling method.
The present specification provides an electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the interface calling method when executing the program.
The technical scheme adopted by the specification can achieve the following beneficial effects:
in the service processing system and the interface calling method provided in this specification, the first platform may obtain, for each second platform, interface configuration information corresponding to a service type supported by the second platform from the configuration platform, as target configuration information, and generate a service interface bearer corresponding to the second platform according to the target configuration information. And then, calling a service interface corresponding to the second platform to send a data request from the second platform through the generated service interface carrier so as to acquire service data required by a user from the second platform, wherein the configuration platform is used for configuring interface configuration information corresponding to the second platform.
It can be seen from the above system and method that, if a first platform needs to access an interface of a second platform, a service interface carrier corresponding to the second platform can be directly generated only by acquiring interface configuration information of the second platform through a configuration platform, so that a service interface corresponding to the second platform can be called for processing when a service request related to the second platform needs to be processed. Compared with the prior art that the developer of the first platform needs to realize the method for accessing the code of the service interface, the working efficiency of the developer is improved to a certain extent.
Drawings
The accompanying drawings, which are included to provide a further understanding of the specification and are incorporated in and constitute a part of this specification, illustrate embodiments of the specification and together with the description serve to explain the specification and not to limit the specification in a non-limiting sense. In the drawings:
fig. 1 is a schematic flowchart of an interface calling method in this specification;
fig. 2 is a schematic flowchart of a service interface for a first platform to access a second platform provided in this specification;
FIG. 3 is a schematic diagram of an interface invoking device provided in the present specification;
fig. 4 is a schematic diagram of an electronic device corresponding to fig. 1 provided in the present specification.
Detailed Description
In order to make the objects, technical solutions and advantages of the present disclosure more clear, the technical solutions of the present disclosure will be clearly and completely described below with reference to the specific embodiments of the present disclosure and the accompanying drawings. It is to be understood that the embodiments described are only a few embodiments of the present disclosure, and not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present specification without any creative effort belong to the protection scope of the present specification.
The technical solutions provided by the embodiments of the present description are described in detail below with reference to the accompanying drawings.
In the prior art, when a first platform needs to access a service interface of a second platform, not only developers of the second platform are required to implement a function of the service interface, but also developers of the first platform are required to implement a code for accessing the service interface, so that the function required to be implemented by the service interface is on-line to the first platform. Therefore, no matter which service interface of the second platform is accessed by the first platform, the code accessed to the service interface needs to be repeatedly realized by the developer, and the working efficiency of the developer is reduced.
In order to solve the above problems, in this specification, a service processing system and an interface calling method are provided, where a first platform may obtain, for each second platform, interface configuration information corresponding to a service type supported by the second platform from a configuration platform, and use the interface configuration information as target configuration information, and generate a service interface bearer corresponding to the second platform according to the target configuration information. And then, calling a service interface corresponding to the second platform through a service interface carrier to send a data request from the second platform so as to acquire service data required by a user from the second platform, thereby improving the working efficiency of developers.
In this specification, a service processing system includes a configuration platform, a first platform, and at least one second platform, where different second platforms provide different types of services. The configuration platform is configured to configure interface configuration information of a service interface corresponding to each second platform, and the first platform may access the service interface of the second platform, so that a user may execute a service provided by the second platform through the first platform.
Fig. 1 is a schematic flowchart of an interface calling method in this specification, which specifically includes the following steps:
s101: and for each second platform, acquiring interface configuration information corresponding to the service type supported by the second platform from a preset configuration platform as target configuration information.
In practical application, the second platform may provide the service supported by the second platform to the first platform, but the first platform needs to access the service interface provided by the second platform first, and then the user can use the service of the second platform in the first platform by calling the accessed service interface.
Based on this, the first platform may obtain, for each second platform, interface configuration information corresponding to the service type supported by the second platform from a preset configuration platform, as target configuration information. The target configuration information is used for accessing a service interface corresponding to the second platform, and the service interface corresponding to the second platform is used for executing a service under a service type supported by the second platform. For example, if the second platform is a takeout platform, the service interface corresponding to the second platform may enable the first platform to provide the takeout service of the second platform to the user.
The configuration platform may be understood as a platform for configuring interface configuration information of the second platforms and managing the interface configuration information of each second platform. The interface configuration information managed in the configuration platform needs to be generated based on the configuration request sent by the second platform. Specifically, the second platform may acquire the interface configuration module from the first platform, and send a configuration request to the configuration platform according to the interface configuration template. The configuration platform can receive a configuration request sent by the second platform, and perform interface data configuration on a service interface corresponding to the second platform according to the configuration request, so as to obtain and store interface configuration information corresponding to the second platform. In practical application, of course, the second platform may provide the interface configuration information of the service interface to the first platform, and the first platform requests the configuration platform to configure the service interface of the second platform, so that the configuration platform stores the interface configuration information of the second platform.
The interface configuration template mentioned above refers to an interface standard established by the first platform, and the second platform can implement the function of its own service interface according to the interface configuration template. The aforementioned interface configuration information may include identification information of the first platform, identification information of the second platform, an interface communication protocol on which the first platform is based, a timeout time, a port number of the second platform, identification information of the Bean (e.g., Bean name), and the like. After the first platform calls the service interface, the second platform needs to respond within the overtime, and if the second platform does not respond, the first platform does not call the service interface. The interface communication Protocol may include HyperText Transfer Protocol (HTTP), thread Protocol, Remote Method Invocation (RMI), session, and the like.
S102: and generating a service interface carrier corresponding to the second platform according to the target configuration information.
S103: and calling a service interface corresponding to the second platform to send a data request from the second platform through the service interface carrier so as to acquire service data required by the user from the second platform.
After the first platform obtains the target configuration information, a service interface carrier corresponding to the second platform can be generated according to the target configuration information. The first platform may generate a service interface carrier corresponding to the second platform based on a preset SpringBean framework. That is, the service interface bearer may be in the form of Spring Bean. The first platform can call the service interface corresponding to the second platform through the generated service interface carrier. That is, if a user views or executes a service of the second platform in the first platform through the terminal, the first platform may call a service interface corresponding to the second platform to send a data request to the second platform through the service interface carrier, and the second platform may return service data to the first platform after receiving the data request, so that the first platform obtains the service data required by the user.
For example, if a user uses a takeout service provided by the second platform in the first platform and places an order for takeout in the first platform through the terminal, the first platform may call a service interface of the second platform to send a data request to the second platform, where the data request carries order data (e.g., shop information, commodity information, and other data for placing an order) of the user that needs to be sent to the second platform. The second platform processes the takeaway order of the user through the data request, and returns a processing result (i.e., the service data required by the user mentioned above) to the first platform. Accordingly, the first platform can display all the information of the takeaway of the order made by the user to the user through the terminal.
It should be noted that, in the configuration platform, in addition to the interface configuration information, the interface configuration information corresponding to each second platform may also be modified or deleted. If the configuration platform has changed interface configuration information, that is, a certain second platform modifies the interface configuration information corresponding to the second platform through the configuration platform, the first platform may receive, according to a preset listener, a configuration change message sent by the configuration platform, and determine, according to the configuration change message, the second platform whose interface configuration information has changed, as a target platform.
And then, the first platform can acquire the changed interface configuration information of the target platform from the configuration platform, and change the service interface carrier corresponding to the target platform according to the changed interface configuration information. That is, no matter which parameter (e.g., the above-mentioned timeout time, port number, etc.) in the interface configuration information is changed, the first platform may determine the changed interface configuration information through the listener, acquire the changed interface configuration information from the configuration platform, and further change the service interface bearer corresponding to the interface configuration information.
In practical application, when determining that the interface configuration information is changed (such as being newly added, deleted, and modified), the configuration platform may send the changed interface configuration information to each worker of the second platform corresponding to the interface configuration information.
In addition to modifying the interface configuration information as mentioned above, the second platform may also delete the interface configuration information in the configuration platform. Specifically, the second platform may send a configuration deletion request to the configuration platform, and after receiving the configuration deletion request sent by the second platform, the configuration platform deletes the interface configuration information corresponding to the second platform according to the configuration deletion request. After the interface configuration information is deleted, the first platform cannot call the service interface corresponding to the interface configuration information any more.
In practical applications, if the second platform fails, the first platform may temporarily not provide the service of the second platform to the user. Based on this, the interface configuration information may include a service warning identifier, and before the first platform needs to call the service interface corresponding to the target configuration information, if it is determined that the target configuration information acquired from the configuration platform includes the service warning identifier, the service interface corresponding to the second platform of the target configuration information should not be called through the service interface carrier. The service warning flag is used to indicate that the second platform has failed.
In this specification, the first platform may formulate an interface configuration template, i.e., format the service interface. The interface configuration template may include a basic field, a service field, an extension field, and the like, where the basic field may include: the service field is used for the second platform to provide basic data for the first platform, and the extension field is used for the second platform to provide personalized data for the first platform. The basic data refers to data that each second platform needs to provide, for example, a service name of a service provided by the second platform, a service icon of the service provided by the second platform, and the like.
The personalization data mentioned here is based on different service requirements of each second platform. Therefore, the first platform can acquire the basic data of the second platform through the service interface of the second platform, and can also acquire the personalized data of the second platform based on the actual requirements of the second platform. For example, a service provided by a certain second platform has a service requirement: and adding an additional label of 'buying coupon' to the service icon corresponding to the service, wherein the service requirement is not met by other second platforms. The service interface of the second platform needs to embody the extension field of the additional tag, so that the second platform can fill the additional tag in the extension field of the interface configuration template and send a configuration request to the configuration platform, so that the configuration platform generates the interface configuration information with the extension field. Correspondingly, when the first platform calls the service interface subsequently through the generated service interface carrier, the additional label of 'buy as coupon' can be displayed on the service icon of the service corresponding to the second platform in the terminal of the user.
The first platform may obtain configuration information of each interface at one time when starting up, so as to access a service interface corresponding to the configuration information of each interface, and may also obtain configuration information of each interface managed in the configuration platform in real time (including changed configuration information of the interface), and generate a carrier of each service interface in real time, as shown in fig. 2.
Fig. 2 is a schematic flowchart of a service interface for a first platform to access a second platform provided in this specification.
As can be seen from fig. 2, after the second platform implements the service interface of the second platform according to the interface communication protocol of the first platform, the configuration platform may perform data configuration on the service interface of the second platform. And then, the configuration platform stores interface configuration information corresponding to the second platform. If the first platform is already in the running state at this time, the first platform can acquire the interface configuration information newly added in the configuration platform through the listener, and generate a service interface carrier corresponding to the second platform according to the interface configuration information, so that the first platform can call a service interface corresponding to the second platform through the service interface carrier.
Of course, if the second platform has configured the interface configuration information through the configuration platform before the first platform is started, the first platform may acquire each interface configuration information in the configuration platform at one time and generate a service interface carrier corresponding to each interface configuration information (the interface configuration information corresponding to the second platform may be acquired together). Because the service interfaces of the second platforms have substantially the same format, the first platform can call the service interfaces corresponding to the second platforms through the unified interface calling logic.
It can be seen from the above system and method that the configuration platform can be used to configure interface configuration information corresponding to each second platform, the first platform can generate a service interface carrier corresponding to the second platform by obtaining the interface configuration information in the configuration platform, so that a user can process a service of the second platform in the first platform by calling the service interface corresponding to the second platform through the service interface carrier, and in the prior art, the first platform needs a developer to access a code of the service interface and to go online, so that the first platform can call the service interface of the second platform, thereby improving the working efficiency of the developer.
Based on the same idea, the interface calling method provided above for one or more embodiments of the present specification further provides a corresponding interface calling apparatus, as shown in fig. 3.
Fig. 3 is a schematic diagram of an interface invoking device provided in this specification, which specifically includes:
an obtaining module 301, configured to, for each second platform, obtain, by the device, interface configuration information corresponding to a service type supported by the second platform from a preset configuration platform, where the interface configuration information is determined by the configuration platform according to a configuration request sent by the second platform, and the configuration request is sent by the second platform to the configuration platform according to an interface configuration template obtained from the device;
a generating module 302, configured to generate a service interface bearer corresponding to the second platform according to the target configuration information;
a calling module 303, configured to call, through the service interface carrier, a service interface corresponding to the second platform to send a data request from the second platform, so as to obtain service data required by the user from the second platform.
Optionally, the device is provided with a preset listener;
the device further comprises:
and a monitoring module 304, configured to determine, according to the configuration change message sent by the configuration platform and received by the listener, a second platform with changed interface configuration information, as a target platform, obtain, from the configuration platform, changed interface configuration information of the target platform, and change, according to the changed interface configuration information, a service interface carrier corresponding to the target platform.
Optionally, the interface configuration information includes: a service warning identifier;
the device further comprises:
the determining module 305 is configured to not invoke the service interface corresponding to the second platform through the service interface bearer if it is determined that the target configuration information acquired from the configuration platform includes the service warning identifier.
Optionally, the generating module 302 is specifically configured to generate, based on a preset SpringBean framework, a service interface carrier corresponding to the second platform according to the obtained target configuration information.
Optionally, the interface configuration template includes: a basic field, a service field and an extension field, wherein the basic field comprises: at least one of identification information of the apparatus, identification information of a second platform, and an interface communication protocol on which the apparatus is based, wherein the service field is used for the second platform to provide basic data, and the extension field is used for the second platform to provide personalized data.
This specification also provides a schematic block diagram of the electronic device shown in fig. 4. As shown in fig. 4, at the hardware level, the electronic device includes a processor, an internal bus, a network interface, a memory, and a non-volatile memory, and may also include hardware required for other services. The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs the computer program to implement the interface calling method described in fig. 1. Of course, besides the software implementation, the present specification does not exclude other implementations, such as logic devices or a combination of software and hardware, and the like, that is, the execution subject of the following processing flow is not limited to each logic unit, and may be hardware or logic devices.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the various elements may be implemented in the same one or more software and/or hardware implementations of the present description.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that 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 like elements in a process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, the description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
This description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only an example of the present specification, and is not intended to limit the present specification. Various modifications and alterations to this description will become apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present specification should be included in the scope of the claims of the present specification.
Claims (12)
1. A transaction system, comprising: the method comprises the steps that a platform, a first platform and at least one second platform are configured, and different second platforms provide services with different service types;
the configuration platform receives a configuration request sent by a second platform, and performs interface data configuration on a service interface corresponding to the second platform according to the configuration request to obtain and store interface configuration information corresponding to the second platform;
the first platform acquires interface configuration information corresponding to the service type supported by the second platform from the configuration platform as target configuration information, generates a service interface carrier corresponding to the second platform according to the target configuration information, calls a service interface corresponding to the second platform to send a data request to the second platform through the service interface carrier, and acquires service data required by a user from the second platform;
the second platform acquires an interface configuration template from the first platform, sends a configuration request to the configuration platform according to the interface configuration template, receives a data request sent by the first platform, and returns the service data to the first platform according to the data request.
2. The system of claim 1, wherein the first platform is provided with a preset listener;
and if the first platform receives the configuration change message sent by the configuration platform according to the listener, determining a second platform with changed interface configuration information according to the configuration change message as a target platform, acquiring the changed interface configuration information of the target platform from the configuration platform, and changing a service interface carrier corresponding to the target platform according to the changed interface configuration information.
3. The system of claim 1, wherein the interface configuration information comprises: a service warning identifier;
and if the first platform determines that the target configuration information acquired from the configuration platform contains the service warning identifier, the first platform does not call the service interface corresponding to the second platform through the service interface carrier.
4. The system of claim 1, wherein if the configuration platform receives a configuration deletion request sent by the second platform, the configuration platform deletes interface configuration information corresponding to the second platform according to the configuration deletion request.
5. The system according to claim 1, wherein the first platform generates a service interface bearer corresponding to the second platform according to the acquired target configuration information based on a preset SpringBean framework.
6. The system of claim 1, wherein the interface configuration template comprises: a basic field, a service field and an extension field, wherein the basic field comprises: the service field is used for the second platform to provide basic data, and the extension field is used for the second platform to provide personalized data.
7. An interface calling method, comprising:
for each second platform, the first platform acquires interface configuration information corresponding to the service type supported by the second platform from a preset configuration platform, and the interface configuration information is used as target configuration information, the interface configuration information is determined by the configuration platform according to a configuration request sent by the second platform, and the configuration request is sent to the configuration platform by the second platform according to an interface configuration template acquired from the first platform;
generating a service interface carrier corresponding to the second platform according to the target configuration information;
and calling a service interface corresponding to the second platform to send a data request to the second platform through the service interface carrier so as to acquire service data required by a user from the second platform.
8. The method of claim 1, wherein the method further comprises:
if receiving a configuration change message sent by the configuration platform according to a preset listener, determining a second platform with changed interface configuration information as a target platform according to the configuration change message;
and acquiring the changed interface configuration information of the target platform from the configuration platform, and changing a service interface carrier corresponding to the target platform according to the changed interface configuration information.
9. The method of claim 1, wherein the interface configuration information comprises: a service warning identifier;
the method further comprises the following steps:
and if the target configuration information acquired from the configuration platform contains the service warning identification, calling a service interface corresponding to the second platform through the service interface carrier is not carried out.
10. An interface invocation apparatus, comprising:
an obtaining module, configured to, for each second platform, obtain, by the device, interface configuration information corresponding to a service type supported by the second platform from a preset configuration platform, where the interface configuration information is determined by the configuration platform according to a configuration request sent by the second platform, and the configuration request is sent by the second platform to the configuration platform according to an interface configuration template obtained from the device;
a generating module, configured to generate a service interface bearer corresponding to the second platform according to the target configuration information;
and the calling module is used for calling the service interface corresponding to the second platform to send a data request from the second platform through the service interface carrier so as to acquire the service data required by the user from the second platform.
11. A computer-readable storage medium, characterized in that the storage medium stores a computer program which, when executed by a processor, implements the method of any of the preceding claims 7 to 9.
12. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of any of claims 7 to 9 when executing the program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011124629.9A CN112306710A (en) | 2020-10-20 | 2020-10-20 | Service processing system, interface calling method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011124629.9A CN112306710A (en) | 2020-10-20 | 2020-10-20 | Service processing system, interface calling method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112306710A true CN112306710A (en) | 2021-02-02 |
Family
ID=74328014
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011124629.9A Pending CN112306710A (en) | 2020-10-20 | 2020-10-20 | Service processing system, interface calling method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112306710A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113703728A (en) * | 2021-08-27 | 2021-11-26 | 支付宝(杭州)信息技术有限公司 | Development-assisted micro-component service processing method, device and equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101827302A (en) * | 2010-04-19 | 2010-09-08 | 中兴通讯股份有限公司 | Multi-service unified processing method and unified service platform |
| CN110753082A (en) * | 2019-09-06 | 2020-02-04 | 深圳平安通信科技有限公司 | Service calling method and terminal equipment |
| CN111026797A (en) * | 2019-12-02 | 2020-04-17 | 卫盈联信息技术（深圳）有限公司 | Service data processing method, server and storage medium |
| CN111400061A (en) * | 2020-03-12 | 2020-07-10 | 泰康保险集团股份有限公司 | Data processing method and system |
-
2020
- 2020-10-20 CN CN202011124629.9A patent/CN112306710A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101827302A (en) * | 2010-04-19 | 2010-09-08 | 中兴通讯股份有限公司 | Multi-service unified processing method and unified service platform |
| CN110753082A (en) * | 2019-09-06 | 2020-02-04 | 深圳平安通信科技有限公司 | Service calling method and terminal equipment |
| CN111026797A (en) * | 2019-12-02 | 2020-04-17 | 卫盈联信息技术（深圳）有限公司 | Service data processing method, server and storage medium |
| CN111400061A (en) * | 2020-03-12 | 2020-07-10 | 泰康保险集团股份有限公司 | Data processing method and system |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113703728A (en) * | 2021-08-27 | 2021-11-26 | 支付宝(杭州)信息技术有限公司 | Development-assisted micro-component service processing method, device and equipment |
| CN113703728B (en) * | 2021-08-27 | 2024-05-03 | 支付宝(杭州)信息技术有限公司 | Micro-component business processing method, device and equipment for assisting research and development |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108924029B (en) | Method and device for sending customer service data | |
| CN107070858B (en) | Service processing method and device | |
| CN107092475B (en) | Calling method and device of interactive control | |
| CN111796823A (en) | Method and device for updating page and displaying page and page maintenance system | |
| CN107045438B (en) | Application top view processing method, device and component | |
| CN108268289B (en) | Parameter configuration method, device and system for web application | |
| CN111639278A (en) | Webpage loading method and device | |
| CN107479868B (en) | Interface loading method, device and equipment | |
| CN109947643B (en) | A/B test-based experimental scheme configuration method, device and equipment | |
| CN108549562A (en) | A kind of method and device of image load | |
| CN107562496B (en) | Method and device for page configuration and page display | |
| CN111796821A (en) | Page updating method and device | |
| CN112597013A (en) | Online development and debugging method and device | |
| CN112559934A (en) | Page popup display method and device | |
| CN112163150A (en) | Information pushing method and device | |
| CN111861454A (en) | Method and device for displaying unique identifier of digital object | |
| CN109144600B (en) | Application program running method and device and computer readable medium | |
| CN112306710A (en) | Service processing system, interface calling method and device | |
| CN111949297B (en) | Block chain intelligent contract upgrading method and device and electronic equipment | |
| CN110022351B (en) | Service request processing method and device | |
| CN110837446A (en) | Equipment management method and device applied to embedded system, medium and embedded equipment | |
| CN111538667A (en) | Page testing method and device | |
| CN109597695B (en) | Data processing method, device and equipment | |
| CN111078435A (en) | Service processing method and device and electronic equipment | |
| CN112698882A (en) | Page component loading method and device |
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 |