CN114615242A - Data interaction method, server, terminal and computer readable storage medium - Google Patents
Data interaction method, server, terminal and computer readable storage medium Download PDFInfo
- Publication number
- CN114615242A CN114615242A CN202210231557.0A CN202210231557A CN114615242A CN 114615242 A CN114615242 A CN 114615242A CN 202210231557 A CN202210231557 A CN 202210231557A CN 114615242 A CN114615242 A CN 114615242A
- Authority
- CN
- China
- Prior art keywords
- interface
- information
- data
- aggregation
- aggregated
- 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 71
- 230000003993 interaction Effects 0.000 title claims abstract description 50
- 238000003860 storage Methods 0.000 title claims abstract description 13
- 230000002776 aggregation Effects 0.000 claims abstract description 233
- 238000004220 aggregation Methods 0.000 claims abstract description 233
- 230000004044 response Effects 0.000 claims abstract description 40
- 230000010354 integration Effects 0.000 claims description 11
- 238000004458 analytical method Methods 0.000 claims description 7
- 239000000126 substance Substances 0.000 claims description 6
- 238000001914 filtration Methods 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 18
- 230000008569 process Effects 0.000 description 9
- 238000004590 computer program Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 4
- 239000002699 waste material Substances 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000013075 data extraction Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008521 reorganization Effects 0.000 description 1
- 230000003245 working effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the invention discloses a data interaction method, a server, a terminal and a computer readable storage medium, wherein the method comprises the following steps: receiving an interface request sent by a front end; matching the first aggregation interface information carried in the interface request with the cached aggregation data cached locally to obtain a matching result; when the matching result represents that the matching is successful, generating a unified interface request based on the first aggregation interface information to call a plurality of interfaces at the back end, and obtaining access data which are fed back by the back end and correspond to the plurality of interfaces respectively; and obtaining effective access data through data response configuration based on the access data and sending the effective access data to the front end. According to the scheme, the first aggregation interface information is matched with the cached aggregation data cached locally, the multiple rear-end interfaces are called at one time by using the successfully represented matching result, the access data are obtained, the interaction times of the front end and the rear end are reduced, the front end and the rear end can be used for multiple times, and the expansibility is strong.
Description
Technical Field
The present invention relates to the field of data transmission technologies, and in particular, to a data interaction method, a server, a terminal, and a computer-readable storage medium.
Background
The front-end and back-end interaction is usually realized by remote calling through an HTTP interface, and the interaction of the front end and the back end meets the requirements on performance and the like; the staff needs to redefine the front-end and back-end interactive interfaces, the front end needs to redevelop the corresponding analysis, and the back end needs to redevelop a new interface, which consumes a lot of manpower and time to define the interfaces and develop the work, resulting in resource waste and poor expansibility.
Disclosure of Invention
In order to solve the above technical problems, embodiments of the present invention provide a data interaction method, a server, a terminal, and a computer-readable storage medium, which can solve the problems of resource waste and poor extensibility caused by multiple interactions between a front end and a back end.
The technical scheme of the invention is realized as follows:
the embodiment of the invention provides a data interaction method, which is characterized by being applied to a server and comprising the following steps:
receiving an interface request sent by a front end;
matching the first aggregation interface information carried in the interface request with the cached aggregation data cached locally to obtain a matching result;
when the matching result represents that the matching is successful, generating a unified interface request based on the first aggregation interface information to call a plurality of interfaces at the back end, and obtaining access data which are fed back by the back end and correspond to the plurality of interfaces respectively;
and obtaining effective access data through data response configuration based on the access data and sending the effective access data to the front end.
In the above scheme, the first aggregation interface information is a first aggregation interface identifier, and the aggregation interface identifier is formed by integrating identifiers of a plurality of interface information into one aggregation interface information;
the matching the first aggregation interface information carried in the interface request with the locally cached cache aggregation data to obtain a matching result includes:
if the first aggregation interface identifier exists in the cache aggregation data cached locally, obtaining a matching result which is successfully matched;
and if the first aggregation interface identifier does not exist in the cache aggregation data cached locally, obtaining a matching result of matching failure.
In the above scheme, the first aggregated interface information is a plurality of interface information;
the matching the first aggregation interface information carried in the interface request with the locally cached cache aggregation data to obtain a matching result includes:
if at least two pieces of interface information in the plurality of pieces of interface information exist in the cache aggregated data cached locally, obtaining a matching result of successful matching;
and if the interface information does not exist in the cache aggregated data cached locally, obtaining a matching result of matching failure.
In the foregoing solution, before the matching the first aggregated interface information carried in the interface request with the locally cached aggregated cached data to obtain a matching result, the method further includes:
acquiring a plurality of interface information to be aggregated;
performing aggregation interface configuration based on the plurality of interface information to be aggregated to obtain second aggregation interface information and corresponding second aggregation interface identifiers;
analyzing the second aggregation interface information to obtain the cache data; the cache data includes a second aggregation interface identifier corresponding to second aggregation interface information and the plurality of interface information to be aggregated.
In the foregoing solution, the configuring an aggregation interface based on the plurality of interface information to be aggregated to obtain second aggregation interface information and a corresponding second aggregation interface identifier includes:
based on the plurality of interface information to be aggregated, aggregation interface setting in the aggregation interface configuration is carried out to obtain setting information;
performing data response configuration in the aggregated interface configuration based on the plurality of interface information to be aggregated to obtain configuration information;
and performing data integration based on the setting information and the configuration information to obtain the second aggregation interface information and a corresponding second aggregation interface identifier.
In the foregoing scheme, the interface information to be aggregated includes:
interface paths, interface request types, interface request data and interface identifiers corresponding to a plurality of interfaces to be aggregated;
the aggregation interface setting in the aggregation interface configuration is performed based on the plurality of interface information to be aggregated to obtain setting information, including:
respectively setting aggregation interfaces based on interface paths, interface request types, interface request data and interface identifiers corresponding to the plurality of interfaces to be aggregated to obtain set interface path information, set interface request type information, set interface request data information and set interface identifier information;
and integrating data information based on the set interface path information, the set interface request type information, the set interface request data information and the set interface identification information to obtain the set information.
In the foregoing scheme, the performing, based on the interface information to be aggregated, data response configuration in the aggregated interface configuration to obtain configuration information includes:
performing data response analysis on the interface information to be aggregated to obtain return data path information corresponding to the interfaces;
and performing data integration based on the returned data path information to obtain the configuration information.
In the foregoing solution, after the matching is performed on the first aggregated interface information carried in the interface request and the locally cached aggregated cached data to obtain a matching result, the method further includes:
when the matching result represents that the matching fails, the aggregation server stops accessing and generates termination information;
and sending the termination information to the front end.
In the foregoing solution, obtaining valid access data based on the access data through data response configuration and sending the valid access data to the front end includes:
filtering the access data through the configuration information configured by the data response to obtain useful access data;
recombining the useful access data to obtain the effective access data;
and sending the effective access data to the front end.
The embodiment of the invention provides a data interaction method, which is characterized in that the method is applied to a terminal, the terminal comprises a front end and a back end, and the method comprises the following steps:
sending an interface request carrying first aggregation interface information to a server;
receiving a uniform interface request sent by the server after the server is successfully matched based on the first aggregation interface information;
acquiring access data based on the uniform interface request, and sending the access data to the server;
and receiving effective access data processed by the server based on the access data.
In the above solution, before sending the first interface request carrying the aggregated interface information to the server, the method further includes:
acquiring a plurality of interface information;
integrating the plurality of interface information into one interface information to obtain the first aggregation interface information; and the first aggregation interface information is a first aggregation interface identifier.
In the foregoing solution, before sending the interface request carrying the first aggregated interface information to the server, the method further includes:
acquiring a plurality of interface information;
using the plurality of interface information as the first aggregated interface information; the first aggregation interface information is a plurality of interface information.
The embodiment of the disclosure provides a server, which comprises a first receiving unit, a first obtaining unit and a first sending unit; wherein the content of the first and second substances,
the first receiving unit is used for receiving an interface request sent by a front end;
the first obtaining unit is configured to match the first aggregation interface information carried in the interface request with the locally cached cache aggregation data to obtain a matching result; when the matching result represents that the matching is successful, generating a unified interface request based on the first aggregation interface information to call a plurality of interfaces at the back end, and obtaining access data which are fed back by the back end and correspond to the plurality of interfaces respectively;
and the first sending unit is used for obtaining effective access data through data response configuration based on the access data and sending the effective access data to the front end.
The embodiment of the disclosure provides a terminal, which includes a second sending unit and a second receiving unit; wherein the content of the first and second substances,
the second sending unit is used for sending the interface request carrying the first aggregation interface information to the server;
the second receiving unit is configured to receive a unified interface request sent by the server after the matching based on the first aggregation interface information is successful;
the second sending unit is used for acquiring access data based on the unified interface request and sending the access data to the server;
and the second receiving unit receives effective access data processed by the server based on the access data.
An embodiment of the present disclosure provides a server, including:
a first memory to store executable data instructions;
the first processor is used for executing the executable instructions stored in the first memory, and when the executable instructions are executed, the first processor executes the data interaction method.
The embodiment of the present disclosure provides a terminal, which includes:
a second memory for storing executable data instructions;
and the second processor is used for executing the executable instructions stored in the second memory, and when the executable instructions are executed, the second processor executes the data interaction method.
Embodiments of the present invention provide a computer-readable storage medium, which stores executable instructions for causing a first processor to execute a data interaction method according to an embodiment of the present invention when the executable instructions are executed.
The embodiment of the invention provides a computer-readable storage medium, and the storage medium stores executable instructions which are used for causing a second processor to execute the data interaction method according to the embodiment of the invention when being executed.
The embodiment of the invention provides a data interaction method, a server, a terminal and a computer readable storage medium, wherein the method comprises the following steps: receiving an interface request sent by a front end; matching the first aggregation interface information carried in the interface request with the cached aggregation data cached locally to obtain a matching result; when the matching result represents that the matching is successful, generating a unified interface request based on the first aggregation interface information to call a plurality of interfaces at the back end, and obtaining access data which are fed back by the back end and correspond to the plurality of interfaces respectively; and obtaining effective access data through data response configuration based on the access data and sending the effective access data to the front end. According to the scheme, the first aggregation interface information carried by the interface request is matched with the locally cached aggregation data, the access data corresponding to the plurality of interfaces can be obtained at one time when the matching is successful, then the access data is integrated to obtain the effective access data, and finally the effective access data is sent to the front end at one time, so that the interaction times of the front end and the rear end are reduced, the system can be repeatedly used, and the expansibility is strong.
Drawings
Fig. 1 is an optional device framework diagram of a data interaction method according to an embodiment of the present invention;
fig. 2 is a first alternative flowchart of a data interaction method applied to a server according to an embodiment of the present invention;
fig. 3 is a schematic diagram illustrating an alternative flow chart of a data interaction method applied to a server according to an embodiment of the present invention;
fig. 4 is a schematic flow chart illustrating an alternative data interaction method applied to a server according to an embodiment of the present invention;
fig. 5 is a schematic diagram of an optional fourth flow chart of a data interaction method applied to a terminal according to an embodiment of the present invention;
FIG. 6 is an alternative flow chart of a data interaction method according to an embodiment of the present invention;
FIG. 7 is another alternative flow chart of a data interaction method according to an embodiment of the present invention;
fig. 8 is a first schematic structural diagram of a server according to an embodiment of the present invention;
fig. 9 is a first schematic structural diagram of a terminal according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of a server according to an embodiment of the present invention;
fig. 11 is a schematic structural diagram of a terminal according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments of the present invention without any creative work belong to the protection scope of the present invention.
In order that those skilled in the art will better understand the disclosure, reference will now be made in detail to the embodiments of the disclosure as illustrated in the accompanying drawings. Fig. 1 is an optional device framework diagram of a data interaction method according to an embodiment of the present invention. The terminal and server of fig. 1; the terminal comprises a front end and a back end. The terminal is used for sending an interface request and acquiring data; the server is used for carrying out interface request processing and data processing. The data interaction method provided by the embodiment of the invention is suitable for a data interaction scene.
Fig. 2 is an optional flowchart of a data interaction method applied to a server according to an embodiment of the present invention, which will be described with reference to the steps shown in fig. 2.
S101, receiving an interface request sent by a front end.
In some embodiments of the present invention, the interface request sent by the front end carries first aggregation interface information, where the first aggregation interface information may be aggregation information composed of multiple interface information and has a corresponding first aggregation interface identifier; the first aggregated interface information may also be a plurality of interface information.
In some embodiments of the present invention, the server is an aggregation interface server, and the server may receive an interface request carrying the first aggregation interface information sent by the front end.
S102, matching the first aggregation interface information carried in the interface request with the cached aggregation data cached locally to obtain a matching result.
In some embodiments of the present invention, the cache aggregation data includes an aggregation identifier and a plurality of interface information, where the plurality of interfaces are aggregated into one interface.
In some embodiments of the present invention, the server may match the first aggregation interface information carried in the interface request with the cache aggregation data locally cached by the server, so as to obtain two matching results, i.e., a matching success result and a matching failure result.
In some embodiments of the present invention, step S102 may be implemented by S1021 and S1022 as follows:
and S1021, if the first aggregation interface identifier exists in the cached aggregation data cached locally, obtaining a matching result of successful matching.
In some embodiments of the present invention, the first aggregation interface information is a first aggregation interface identifier, and the first aggregation interface identifier is formed by integrating identifiers of a plurality of interface information into one first aggregation interface information.
In some embodiments of the present invention, the server may find the first aggregation interface identifier carried by the interface request in the cached aggregation data cached locally, and if the first aggregation interface identifier is found, the matching is successful, so as to obtain a successful matching result.
And S1022, if the first aggregation interface identifier exists in the cached aggregation data of the local cache, obtaining a matching result of successful matching.
In some embodiments of the present invention, the server may find the first aggregation interface identifier carried by the interface request in the cached aggregation data cached locally, and if the first aggregation interface identifier is not found, it represents that the matching fails, and a matching result that fails is obtained.
It can be understood that, in some embodiments of the present invention, the server may find the first aggregation interface identifier carried by the interface request in the locally cached cache aggregation data, and if found, it represents that the matching is successful; if not, the matching is failed, so that a matching result is obtained, whether the data can be called for access or not can be further judged, and the data access efficiency is improved.
In some embodiments of the present invention, step S102 may also be implemented by S1023 and S1024 as follows:
and S1023, if at least two pieces of interface information to be aggregated in the plurality of pieces of interface information to be aggregated exist in the cached aggregated data cached locally, obtaining a matching result of successful matching.
In some embodiments of the present invention, the first aggregated interface information is a plurality of interface information, and the interface information includes: interface path, interface request type, interface request data, and interface identification.
In some embodiments of the present invention, the server may find a plurality of interface information carried by the interface request in the locally cached cache aggregated data, and if at least two interface information are found, the matching is successful, so as to obtain a successful matching result.
Illustratively, the interface request includes 6 interface information, and if the server finds 3 interface information in the locally cached cache aggregated data, the next operation is performed if the matching is successful.
And S1024, if the interface information to be aggregated does not exist in the cached aggregated data cached locally, obtaining a matching result of matching failure.
In some embodiments of the present invention, the server may find a plurality of interface information carried by the interface request in the locally cached cache aggregated data, and if the interface information is not found or is smaller than two interface information, it represents that the matching fails, and a failed matching result is obtained.
Illustratively, the interface request includes 6 pieces of interface information, and the server finds 1 piece of interface information in the locally cached cache aggregated data or finds the interface information, and if the matching is a failure, performs the next operation.
It can be understood that, in some embodiments of the present invention, the server may find a plurality of interface information carried by the interface request in the locally cached cache aggregated data, and if at least two interface information are found, it represents that the matching is successful; if the interface information is not found or one piece of interface information is found, the matching is failed, so that a matching result is obtained, whether the data can be called for access or not can be further judged, and the data access efficiency is improved.
S103, when the matching result represents that the matching is successful, generating a unified interface request based on the first aggregation interface information to call the plurality of interfaces at the back end, and obtaining access data corresponding to the plurality of interfaces fed back by the back end.
In some embodiments of the invention, the unified interface is a convention for interfacing different components of the software system. To provide a set of routines that applications and developers can access based on certain software or hardware without accessing source code or understanding the details of the internal workings.
In some embodiments of the present invention, the server may perform the next operation according to the matching result, and if the matching result represents that the matching is successful, the server may generate a unified interface request according to the first aggregated interface information, and call the multiple interfaces at the back end at the same time through the unified interface request, so as to obtain access data corresponding to the multiple interfaces fed back by the back end.
And S104, obtaining effective access data through data response configuration based on the access data and sending the effective access data to the front end.
In some embodiments of the invention, the data response configuration is primarily the orchestration of response data. By arranging the data response data structure, the data returned by the interface can be customized, the required fields can be dynamically adjusted, and the fields which are not required are filtered and not displayed. The response arrangement is a process of copying the data returned by the server through analyzing the original interface according to the configured json Path value.
In some embodiments of the present invention, the server may perform effective access data extraction on the access data through data response configuration, acquire the effective access data, and send the effective access data to the front end.
It will be appreciated that in some embodiments of the invention, the server may receive an interface request sent by the front end; matching the first aggregation interface information carried in the interface request with the cached aggregation data cached locally to obtain a matching result; when the matching result represents that the matching is successful, generating a unified interface request based on the first aggregation interface information to call a plurality of interfaces at the back end, and obtaining access data corresponding to the plurality of interfaces fed back by the back end; based on the access data, effective access data are obtained through data response configuration and are sent to the front end, interaction times of the front end and the back end are reduced, data acquisition efficiency is improved, and method expansibility is achieved.
In some embodiments of the present invention, step S104 may also be implemented by S1041, S1042, and S1043, as follows:
and S1041, filtering the access data through the configuration information configured by the data response, and acquiring useful access data.
In some embodiments of the present invention, the server may filter the access data by responding to the configured configuration information with the data, remove the useless information, and obtain useful access data.
S1042, useful access data are recombined to obtain effective access data.
In some embodiments of the invention, the server may obtain the valid access data by performing data reorganization on the obtained useful access data.
And S1043, sending the valid data to the front end.
In some embodiments of the invention, the server sends the obtained valid access data to the front-end.
It can be understood that, in some embodiments of the present invention, the server may filter the access data through the configuration information configured by the data response, and obtain useful access data; useful access data are recombined to obtain effective access data; and the effective data is sent to the front end, so that the effectiveness of the access data is improved.
In some embodiments of the present invention, fig. 3 is an optional flowchart illustrating a second method for data interaction applied to a server according to an embodiment of the present invention, and before step S102, further includes steps S105-S107. The following were used:
and S105, acquiring a plurality of interface information to be aggregated.
In some embodiments of the present invention, a server may obtain a plurality of interface information to be aggregated, where the interface information includes an interface path, an interface request type, interface request data, and an interface identifier.
In some embodiments of the invention, the interface request types include GET and POST.
S106, based on the plurality of interface information to be aggregated, aggregation interface configuration is carried out, and second aggregation interface information and corresponding second aggregation interface identifiers are obtained.
In some embodiments of the invention, the aggregation interface configuration comprises two parts, an aggregation interface setting and a data response configuration. The aggregation interface setting comprises an interface path to be aggregated, an interface request type, interface request data and an interface identifier; the data response configuration includes the orchestration of response data.
In some embodiments of the present invention, the server may perform aggregation interface configuration through a plurality of pieces of interface information to be aggregated, to obtain second aggregation interface information and a corresponding second aggregation interface identifier.
Illustratively, the interface to be aggregated getUserInfo (get user information interface), getuseradaddress (get); the two interfaces have respective data structures and interface information; the server may configure 1 new aggregation interface, getUserAll, which is a second aggregation interface identifier corresponding to the second aggregation interface information.
The following is exemplary aggregation interface configuration implementation code.
The simplified data structure after definition is as follows:
in some embodiments of the present invention, fig. 4 is a third optional flowchart of a data interaction method applied to a server according to an embodiment of the present invention, where step S106 may also be implemented by S1061-S1063, as follows:
s1061, based on the information of the plurality of interfaces to be aggregated, performing aggregation interface setting in the aggregation interface configuration to obtain setting information.
In some embodiments of the present invention, the server may perform aggregation interface setting on a plurality of interface information to be aggregated to obtain the setting information.
In some embodiments of the present invention, step S1061 may also be implemented by S10611 and S10612, as follows:
s10611, respectively setting aggregation interfaces based on interface paths, interface request types, interface request data and interface identifiers corresponding to a plurality of interfaces to be aggregated to obtain set interface path information, set interface request type information, set interface request data information and set interface identifier information.
In some embodiments of the present invention, the interface information to be aggregated includes an interface path, an interface request type, interface request data, and an interface identifier corresponding to each of the plurality of interfaces to be aggregated.
In some embodiments of the present invention, the server may perform aggregation interface setting respectively through interface paths, interface request types, interface request data, and interface identifiers corresponding to a plurality of interfaces to be aggregated, to obtain interface path setting information, interface request type setting information, interface request data setting information, and interface identifier setting information.
S10612, integrating data information based on the set interface path information, the set interface request type information, the set interface request data information and the set interface identification information to obtain set information.
In some embodiments of the present invention, the server may perform data information integration by setting the interface path information, setting the interface request type information, setting the interface request data information, and setting the interface identification information, to obtain the setting information.
Exemplary, the following is implementation code for making the aggregation interface setup.
It can be understood that, in some embodiments of the present invention, the server may perform aggregation interface setting respectively through interface paths, interface request types, interface request data, and interface identifiers corresponding to a plurality of interfaces to be aggregated, to obtain interface path setting information, interface request type setting information, interface request data setting information, and interface identifier setting information; and integrating the data information to obtain the setting information, providing conditions for acquiring data and improving the interface request expansibility.
S1062, based on the interface information to be aggregated, performing data response configuration in the aggregated interface configuration to obtain configuration information.
In some embodiments of the present invention, the server may perform data response configuration through the information of the plurality of interfaces to be aggregated, obtain return data path information corresponding to the plurality of interfaces, integrate the data path information, and obtain configuration information.
In some embodiments of the present invention, step S1062 may also be implemented by S10621-S10622 as follows:
s10621, performing data response analysis on the information of the plurality of interfaces to be aggregated to obtain return data path information corresponding to the plurality of interfaces.
In some embodiments of the present invention, the server may perform data response analysis on the information of the plurality of interfaces to be aggregated to obtain the return data path information corresponding to the plurality of interfaces.
And S10622, performing data integration based on the return data path information to obtain configuration information.
In some embodiments of the present invention, the server may perform data integration by returning data path information to obtain configuration information.
Illustratively, implementation code is configured for the data response as follows.
And S1063, performing data integration based on the setting information and the configuration information to obtain second aggregation interface information and a corresponding second aggregation interface identifier.
In some embodiments of the present invention, the server may perform data integration according to the setting information and the configuration information, and obtain the second aggregation interface information and a second aggregation interface identifier corresponding to the second aggregation interface information.
It can be understood that, in some embodiments of the present invention, the server may perform aggregation interface setting in the aggregation interface configuration through a plurality of interface information to be aggregated, to obtain setting information; performing data response configuration in the configuration of the aggregation interface through a plurality of interface information to be aggregated to obtain configuration information; and integrating data by setting information and configuration information to obtain second aggregation interface information and a corresponding second aggregation interface identifier, completing aggregation interface configuration, acquiring second aggregation interface information of a plurality of interfaces to be aggregated, and providing conditions for subsequently acquiring access data.
And S107, analyzing the second aggregation interface information to obtain cache data.
In some embodiments of the present invention, the cache data includes a second aggregation interface identifier corresponding to the second aggregation interface information and a plurality of interface information to be aggregated.
In some embodiments of the present invention, the server may perform data information parsing on the second aggregation interface information to obtain parsed data, which is used as cache data.
It can be understood that, in some embodiments of the present invention, the server performs aggregation interface configuration on a plurality of interface information to be aggregated, and obtains second aggregation interface information and a corresponding aggregation interface identifier; the second aggregation interface information is analyzed to obtain the cache data, so that the server does not need to repeatedly analyze the data, and the data access efficiency is improved.
In some embodiments of the present invention, after step S102, S108 and S109 are also performed as follows:
and S108, when the matching result represents that the matching fails, the aggregation server stops accessing and generates termination information.
In some embodiments of the present invention, the server may perform the next operation according to the matching result, and if the matching result indicates that the matching fails, the server stops accessing to generate the termination information.
And S109, sending the termination information to the front end.
In some embodiments of the invention, the server sends a termination message to the head-end, and the request ends.
It will be appreciated that in some embodiments of the invention, when the matching result characterizes a failure in matching, the aggregation server stops accessing, generating termination information; the termination information is sent to the front end, the request is finished, unnecessary access is reduced, and effective access efficiency is improved.
In some embodiments of the present invention, fig. 5 is an optional flowchart of a data interaction method applied to a terminal according to an embodiment of the present invention, which will be described with reference to the steps shown in fig. 5.
S201, sending an interface request carrying the first aggregation interface information to a server.
In some embodiments of the present invention, the first aggregated interface information is interface information processed by a plurality of interface information or is directly the plurality of interface information, and the terminal includes a front end and a back end.
In some embodiments of the present invention, the terminal may send an interface request carrying the first aggregated interface information to the server.
S202, receiving a uniform interface request sent by the server after the server is successfully matched based on the first aggregation interface information.
In some embodiments of the present invention, the terminal receives a unified interface request sent by the server after matching based on the first aggregated interface information is successful.
S203, acquiring access data based on the uniform interface request, and sending the access data to a server.
In some embodiments of the present invention, the unified interface of the terminal requests to call multiple interfaces, obtains access data, and sends the access data to the server.
And S204, receiving effective access data processed by the server based on the access data.
In some embodiments of the invention, the terminal receives valid access data sent by the server, the valid access data being data processed by the server.
It can be understood that, in some embodiments of the present invention, the terminal may send the information of the plurality of interfaces to the server at one time, so as to obtain effective access data of the plurality of interfaces at one time, reduce multiple interactions, and improve the efficiency of data access.
In some embodiments of the present invention, step S201 is preceded by performing S205 and S206 as follows:
s205, acquiring a plurality of interface information.
In some embodiments of the present invention, a terminal may obtain a plurality of interface information, where the interface information includes an interface path, an interface request type, interface request data, and an interface identification.
S206, acquiring first aggregation interface information based on the plurality of interface information; the first aggregation interface information is a first aggregation interface identifier.
In some embodiments of the present invention, the terminal may merge a plurality of interface information into one interface information, and the interface information further corresponds to the first aggregation interface identifier.
It can be understood that, in some embodiments of the present invention, the terminal may process a plurality of interface information to obtain the first aggregated interface information, so that the number of interactions may be reduced.
In some embodiments of the present invention, before step S201, S207 and S208 are also performed, as follows:
and S207, acquiring a plurality of interface information.
In some embodiments of the present invention, a terminal may obtain a plurality of interface information, where the interface information includes an interface path, an interface request type, interface request data, and an interface identification.
S208, taking the plurality of interface information as first aggregation interface information; the first aggregation interface information is a plurality of interface information.
In some embodiments of the present invention, the terminal may directly use the plurality of interface information as the first aggregated interface information.
It is understood that, in some embodiments of the present invention, the terminal may use multiple pieces of interface information as the first aggregated interface information, and may directly match the cached data in the server.
In the following, an exemplary application of the embodiments of the present invention in a practical application scenario will be described.
An alternative flowchart of a data interaction method provided by the embodiment of the present invention is shown in fig. 6.
And S1, the terminal acquires a plurality of interface information.
S2, the terminal acquires the first aggregation interface information based on the plurality of interface information.
And S3, the terminal sends the interface request carrying the first aggregation interface information to the server.
S4, the server responds to the interface request which is sent by the terminal and carries the first aggregation interface information, and matches the first aggregation interface information carried in the interface request sent by the terminal with the cached aggregation data cached locally to obtain a matching result.
S5, when the matching result represents that the matching is successful, the server generates a uniform interface request based on the first aggregation interface information; and when the matching result represents that the matching fails, the server generates termination information.
And S6, the server sends the unified interface request or the termination information to the terminal.
S7, the terminal responds to the uniform interface request sent to the server, calls a plurality of interfaces and obtains access data corresponding to the plurality of interfaces; and the terminal receives the termination information and ends the request.
And S8, the terminal sends the access data corresponding to the plurality of interfaces to the server.
And S9, the server processes the access data sent by the terminal based on the data response configuration, and obtains effective access data.
And S10, the server sends the effective access data to the terminal.
And S11, the terminal receives the effective access data returned by the server.
In the above steps, the specific implementation process is consistent with the implementation process of the steps explained above, and is not described herein again.
It can be understood that, in some embodiments of the present invention, in the prior art, the front end and the back end interact for multiple times, and the interaction interface needs to be redefined to reduce the interaction times, the front end needs to redevelop the corresponding resolution, and the back end needs to redevelop a new interface; and each time the interface request is different, a new interface needs to be reset, and the expansibility is poor. The aggregation interface server is established as the middle layer of the interaction of the front end and the back end, the front end and the back end can send the request to acquire data at one time, the interaction times are reduced, meanwhile, the aggregation interface server can process the data, the effectiveness of data access is improved, the aggregation interface server can be repeatedly used, and the expansibility is strong.
An alternative flowchart of a data interaction method is provided in the embodiment of the present invention, as shown in fig. 7.
In some embodiments of the present invention, fig. 7 includes a front end, an aggregation interface server, and a back end, both of which belong to a terminal. The front end sends an interface request to an aggregation interface server (equivalent to the server mentioned above), wherein the interface request carries a plurality of interface information; the aggregation interface server carries out aggregation interface configuration before receiving the interface request; when an interface request sent by a front end is received, the aggregation interface configuration is loaded, the configuration information is analyzed, and the analysis result is transmitted to other aggregation interface servers, so that each aggregation interface server is ensured to have the same cache aggregation data; the aggregation interface server matches a plurality of interface information carried by the interface request with the cache information, and sends a uniform interface request to the rear end when the matching is successful; after receiving the unified interface request, the rear end calls a plurality of interfaces to acquire access data; the back end sends the access data to an aggregation interface server; after receiving the access data, the aggregation interface server processes the access data to obtain effective access data; the aggregation server sends the effective access data to the front end; the front end receives valid access data.
It can be understood that, in some embodiments of the present invention, in the prior art, the front end and the back end interact for multiple times, and the interaction interface needs to be redefined to reduce the interaction times, the front end needs to redevelop the corresponding resolution, and the back end needs to redevelop a new interface; a large amount of manpower and time are consumed, interfaces are defined and development work is carried out, new interfaces need to be reset when interface requests are different every time, and expansibility is poor. The aggregation interface server is established as the middle layer of the interaction of the front end and the back end, the front end and the back end can send the request to acquire data at one time, the interaction times are reduced, meanwhile, the aggregation interface server can process the data, the effectiveness of data access is improved, the aggregation interface server can be repeatedly used, and the expansibility is strong.
An embodiment of the present invention provides a server, as shown in fig. 8, where fig. 8 is a schematic structural diagram of a server provided in an embodiment of the present invention, where the server includes: comprises a first receiving unit 801, a first acquiring unit 802 and a first sending unit 803; wherein the content of the first and second substances,
the first receiving unit 801 is configured to receive an interface request sent by a front end;
the first obtaining unit 802 is configured to match the first aggregation interface information carried in the interface request with the locally cached cache aggregation data to obtain a matching result; when the matching result represents that the matching is successful, generating a unified interface request based on the first aggregation interface information to call a plurality of interfaces at the back end, and obtaining access data which are fed back by the back end and correspond to the plurality of interfaces respectively;
the first sending unit 803 is configured to obtain valid access data through data response configuration based on the access data, and send the valid access data to the front end.
In some embodiments of the present invention, the first aggregation interface information is a first aggregation interface identifier, where the first aggregation interface identifier is formed by integrating identifiers of multiple interface information into one first aggregation interface information;
the first obtaining unit 802 is configured to obtain a matching result that is successfully matched if the first aggregation interface identifier exists in the cache aggregation data cached locally; and if the first aggregation interface identifier does not exist in the cache aggregation data cached locally, obtaining a matching result of matching failure.
In some embodiments of the present invention, the first aggregated interface information is a plurality of interface information;
the first obtaining unit 802 is configured to obtain a matching result that is successfully matched if at least two pieces of interface information in the plurality of pieces of interface information exist in the cache aggregated data cached locally; and if the interface information does not exist in the cache aggregated data cached locally, obtaining a matching result of matching failure.
In some embodiments of the present invention, the first obtaining unit 802 is configured to obtain a plurality of interface information to be aggregated; performing aggregation interface configuration based on the plurality of interface information to be aggregated to obtain second aggregation interface information and corresponding second aggregation interface identifiers; analyzing the second aggregation interface information to obtain the cache data; the cache data includes a second aggregation interface identifier corresponding to second aggregation interface information and the plurality of interface information to be aggregated.
In some embodiments of the present invention, the first obtaining unit 802 is configured to perform aggregation interface setting in the aggregation interface configuration based on the plurality of interface information to be aggregated, so as to obtain setting information; performing data response configuration in the aggregated interface configuration based on the plurality of interface information to be aggregated to obtain configuration information; and performing data integration based on the setting information and the configuration information to obtain the second aggregation interface information and a corresponding second aggregation interface identifier.
In some embodiments of the present invention, the plurality of interface information to be aggregated includes: interface paths, interface request types, interface request data and interface identifiers corresponding to a plurality of interfaces to be aggregated;
the first obtaining unit 802 is configured to perform aggregation interface setting respectively based on interface paths, interface request types, interface request data, and interface identifiers corresponding to the multiple interfaces to be aggregated, to obtain set interface path information, set interface request type information, set interface request data information, and set interface identifier information; and integrating data information based on the set interface path information, the set interface request type information, the set interface request data information and the set interface identification information to obtain the set information.
In some embodiments of the present invention, the first obtaining unit 802 is configured to perform data response analysis on the plurality of interface information to be aggregated, and obtain return data path information corresponding to a plurality of interfaces; and performing data integration based on the returned data path information to obtain the configuration information.
In some embodiments of the present invention, the terminal further comprises a first generating unit 804, wherein,
the first generating unit 804 is configured to stop accessing the aggregation server and generate termination information when the matching result represents that matching fails;
the first sending unit 803 is configured to send the termination information to the front end.
In some embodiments of the present invention, the first obtaining unit 802 is configured to perform filtering processing on the access data through the configuration information configured by the data response, and obtain useful access data; recombining the useful access data to obtain the effective access data;
the first sending unit 803 is configured to send the valid access data to the front end.
It will be appreciated that in some embodiments of the invention, the server may receive an interface request sent by the front end; matching first aggregation interface information carried in the interface request with locally cached cache aggregation data to obtain a matching result; when the matching result represents that the matching is successful, generating a unified interface request based on the first aggregation interface information to call the plurality of interfaces at the rear end, and obtaining access data corresponding to the plurality of interfaces fed back by the rear end; based on the access data, effective access data are obtained through data response configuration and are sent to the front end, interaction times of the front end and the back end are reduced, data acquisition efficiency is improved, and method expansibility is achieved.
An embodiment of the present invention provides a terminal, as shown in fig. 9, where fig. 9 is a schematic structural diagram of another terminal provided in the embodiment of the present invention, the terminal includes: comprises a second sending unit 901 and a second receiving unit 902; wherein the content of the first and second substances,
the second sending unit 901 is configured to send an interface request carrying the first aggregation interface information to the server;
the second receiving unit 902 is configured to receive a unified interface request sent by the server after the matching based on the first aggregation interface information is successful;
the second sending unit 901 is configured to obtain access data based on the unified interface request, and send the access data to the server;
the second receiving unit 902 receives valid access data processed by the server based on the access data.
In some embodiments of the present invention, the terminal further comprises a second obtaining unit 903, wherein,
the second obtaining unit 903 is configured to obtain a plurality of interface information; integrating the plurality of interface information into one interface information to obtain the first aggregation interface information; the first aggregation interface information is a first aggregation interface identifier.
In some embodiments of the present invention, the terminal further comprises a second obtaining unit 903, wherein,
the second obtaining unit 903 is configured to obtain a plurality of interface information; using the plurality of interface information as the first aggregated interface information; the first aggregation interface information is a plurality of interface information.
It can be understood that, in some embodiments of the present invention, the terminal may send the information of the plurality of interfaces to the server at one time, so as to obtain effective access data of the plurality of interfaces at one time, reduce multiple interactions, and improve the efficiency of data access.
As shown in fig. 10, fig. 10 is a schematic structural diagram of a server provided in an embodiment of the present invention, where the server 10 includes: a first processor 1001 and a first memory 1002; the first memory 1002 stores one or more programs executable by the first processor 1001, and when the one or more programs are executed, the first processor 1001 executes a data interaction method corresponding to the server according to the foregoing embodiment.
As shown in fig. 11, fig. 11 is a schematic structural diagram of a terminal provided in an embodiment of the present invention, where the terminal 11 includes: a second processor 1101 and a second memory 1102; the second memory 1102 stores one or more programs executable by the second processor 1101, and when the one or more programs are executed, the second processor 1101 executes a data interaction method corresponding to the terminal of the aforementioned embodiment.
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 a hardware embodiment, a 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, 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 flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations 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 servers and terminals 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 server and terminal 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.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.
Claims (17)
1. A data interaction method is applied to a server and comprises the following steps:
receiving an interface request sent by a front end;
matching the first aggregation interface information carried in the interface request with the cached aggregation data cached locally to obtain a matching result;
when the matching result represents that the matching is successful, generating a unified interface request based on the first aggregation interface information to call a plurality of interfaces at the back end, and obtaining access data which are fed back by the back end and correspond to the plurality of interfaces respectively;
and obtaining effective access data through data response configuration based on the access data and sending the effective access data to the front end.
2. The method of claim 1, wherein the first aggregation interface information is a first aggregation interface identifier, and the first aggregation interface identifier is formed by integrating identifiers of a plurality of interface information into one aggregation interface information;
the matching the first aggregation interface information carried in the interface request with the locally cached cache aggregation data to obtain a matching result includes:
if the first aggregation interface identifier exists in the cache aggregation data cached locally, obtaining a matching result which is successfully matched;
and if the first aggregation interface identifier does not exist in the cache aggregation data cached locally, obtaining a matching result of matching failure.
3. The method of claim 1, wherein the first aggregated interface information is a plurality of interface information;
the matching the first aggregation interface information carried in the interface request with the locally cached cache aggregation data to obtain a matching result includes:
if at least two pieces of interface information in the plurality of pieces of interface information exist in the cache aggregated data cached locally, obtaining a matching result of successful matching;
and if the interface information does not exist in the cache aggregated data cached locally, obtaining a matching result of matching failure.
4. The method according to claim 1, wherein before the matching of the first aggregated interface information carried in the interface request with the locally cached cache aggregated data to obtain the matching result, the method further comprises:
acquiring a plurality of interface information to be aggregated;
performing aggregation interface configuration based on the plurality of interface information to be aggregated to obtain second aggregation interface information and corresponding second aggregation interface identifiers;
analyzing the second aggregation interface information to obtain the cache data; the cache data includes a second aggregation interface identifier corresponding to second aggregation interface information and the plurality of interface information to be aggregated.
5. The method according to claim 4, wherein the configuring the aggregation interface based on the plurality of interface information to be aggregated to obtain the second aggregation interface information and the corresponding second aggregation interface identifier includes:
based on the plurality of interface information to be aggregated, aggregation interface setting in the aggregation interface configuration is carried out to obtain setting information;
performing data response configuration in the aggregated interface configuration based on the plurality of interface information to be aggregated to obtain configuration information;
and performing data integration based on the setting information and the configuration information to obtain the second aggregation interface information and a corresponding second aggregation interface identifier.
6. The method of claim 5, wherein the plurality of interface information to be aggregated comprises:
interface paths, interface request types, interface request data and interface identifiers corresponding to a plurality of interfaces to be aggregated;
the aggregation interface setting in the aggregation interface configuration is performed based on the plurality of interface information to be aggregated to obtain setting information, including:
respectively setting aggregation interfaces based on interface paths, interface request types, interface request data and interface identifications corresponding to the plurality of interfaces to be aggregated to obtain set interface path information, set interface request type information, set interface request data information and set interface identification information;
and integrating data information based on the set interface path information, the set interface request type information, the set interface request data information and the set interface identification information to obtain the set information.
7. The method according to claim 5, wherein the performing data response configuration in the aggregated interface configuration based on the plurality of interface information to be aggregated to obtain configuration information comprises:
performing data response analysis on the interface information to be aggregated to obtain return data path information corresponding to the interfaces;
and performing data integration based on the returned data path information to obtain the configuration information.
8. The method according to any one of claims 1 to 3, wherein after the matching of the first aggregation interface information carried in the interface request with the locally cached aggregated cached data is performed, and a matching result is obtained, the method further comprises:
when the matching result represents that the matching fails, the aggregation server stops accessing and generates termination information;
and sending the termination information to the front end.
9. The method according to any one of claims 1 to 3, wherein the obtaining and sending valid access data to the front end through data response configuration based on the access data comprises:
filtering the access data through the configuration information configured by the data response to obtain useful access data;
recombining the useful access data to obtain the effective access data;
and sending the effective access data to the front end.
10. A data interaction method is applied to a terminal, wherein the terminal comprises a front end and a back end, and the method comprises the following steps:
sending an interface request carrying first aggregation interface information to a server;
receiving a uniform interface request sent by the server after the server is successfully matched based on the first aggregation interface information;
acquiring access data based on the uniform interface request, and sending the access data to the server;
and receiving effective access data processed by the server based on the access data.
11. The method of claim 10, wherein before sending the interface request carrying the first aggregated interface information to the server, the method further comprises:
acquiring a plurality of interface information;
integrating the plurality of interface information into one interface information to obtain the first aggregation interface information; and the first aggregation interface information is a first aggregation interface identifier.
12. The method of claim 10, wherein before sending the interface request carrying the first aggregated interface information to the server, the method further comprises:
acquiring a plurality of interface information;
using the plurality of interface information as the first aggregated interface information; the first aggregation interface information is a plurality of interface information.
13. A server is characterized by comprising a first receiving unit, a first obtaining unit and a first sending unit; wherein the content of the first and second substances,
the first receiving unit receives an interface request sent by a front end;
the first obtaining unit is used for matching the first aggregation interface information carried in the interface request with the locally cached cache aggregation data to obtain a matching result; when the matching result represents that the matching is successful, generating a unified interface request based on the aggregated interface information to call a plurality of interfaces at the back end, and obtaining access data which are fed back by the back end and correspond to the plurality of interfaces respectively;
and the first sending unit is used for obtaining effective access data through data response configuration based on the access data and sending the effective access data to the front end.
14. A terminal is characterized in that the terminal comprises a second sending unit and a second receiving unit; wherein the content of the first and second substances,
the second sending unit is used for sending an interface request carrying the first aggregation interface information to the server;
the second receiving unit is configured to receive a unified interface request sent by the server after the server is successfully matched based on the aggregated interface information;
the second sending unit is used for acquiring access data based on the unified interface request and sending the access data to the server;
and the second receiving unit receives effective access data processed by the server based on the access data.
15. A server, characterized in that the server comprises:
a first memory for storing executable instructions;
a first processor, configured to implement the method of any one of claims 1 to 9 when executing executable instructions stored in the memory.
16. A terminal, characterized in that the terminal comprises:
a second memory for storing executable instructions;
a second processor, adapted to implement the method of any of claims 10 to 12 when executing executable instructions stored in the memory.
17. A computer-readable storage medium having stored thereon executable instructions for causing a first processor to perform the method of any one of claims 1 to 9 when executed; or for causing a second processor to perform the method of any of claims 10 to 12 when executed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210231557.0A CN114615242A (en) | 2022-03-10 | 2022-03-10 | Data interaction method, server, terminal and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210231557.0A CN114615242A (en) | 2022-03-10 | 2022-03-10 | Data interaction method, server, terminal and computer readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114615242A true CN114615242A (en) | 2022-06-10 |
Family
ID=81860934
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210231557.0A Pending CN114615242A (en) | 2022-03-10 | 2022-03-10 | Data interaction method, server, terminal and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114615242A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011075739A1 (en) * | 2009-12-18 | 2011-06-23 | Qualcomm Incorporated | Binding/aggregating multiple interfaces at application layer |
| CN107704582A (en) * | 2017-10-08 | 2018-02-16 | 安徽康佳电子有限公司 | A kind of closed loop Ecological feed-back catenary system based on server and webpage |
| CN111314459A (en) * | 2020-02-13 | 2020-06-19 | 北京奇艺世纪科技有限公司 | Service request method, device, electronic equipment and storage medium |
| CN111935210A (en) * | 2020-06-28 | 2020-11-13 | 平安银行股份有限公司 | Data service method, device, server and storage medium |
| CN112039896A (en) * | 2020-08-29 | 2020-12-04 | 中国平安财产保险股份有限公司 | Data processing method, equipment, server and storage medium |
| WO2021238990A1 (en) * | 2020-05-27 | 2021-12-02 | 杭州海康威视数字技术股份有限公司 | Authentication method and apparatus, electronic device, server, program, and storage medium |
| CN113900764A (en) * | 2021-12-13 | 2022-01-07 | 北京达佳互联信息技术有限公司 | Page data acquisition method, page data display method and device |
-
2022
- 2022-03-10 CN CN202210231557.0A patent/CN114615242A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011075739A1 (en) * | 2009-12-18 | 2011-06-23 | Qualcomm Incorporated | Binding/aggregating multiple interfaces at application layer |
| CN107704582A (en) * | 2017-10-08 | 2018-02-16 | 安徽康佳电子有限公司 | A kind of closed loop Ecological feed-back catenary system based on server and webpage |
| CN111314459A (en) * | 2020-02-13 | 2020-06-19 | 北京奇艺世纪科技有限公司 | Service request method, device, electronic equipment and storage medium |
| WO2021238990A1 (en) * | 2020-05-27 | 2021-12-02 | 杭州海康威视数字技术股份有限公司 | Authentication method and apparatus, electronic device, server, program, and storage medium |
| CN111935210A (en) * | 2020-06-28 | 2020-11-13 | 平安银行股份有限公司 | Data service method, device, server and storage medium |
| CN112039896A (en) * | 2020-08-29 | 2020-12-04 | 中国平安财产保险股份有限公司 | Data processing method, equipment, server and storage medium |
| CN113900764A (en) * | 2021-12-13 | 2022-01-07 | 北京达佳互联信息技术有限公司 | Page data acquisition method, page data display method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111158891B (en) | Analysis task processing method and device based on Flink technology and storage medium | |
| CN108462598B (en) | Log generation method, log analysis method and device | |
| CN107704360B (en) | Monitoring data processing method, equipment, server and storage medium | |
| CN108256118B (en) | Data processing method, device, system, computing equipment and storage medium | |
| CN111447102B (en) | SDN network device access method and device, computer device and storage medium | |
| CN107133231B (en) | Data acquisition method and device | |
| WO2020140680A1 (en) | Asynchronous callback method, device, computer apparatus, and storage medium | |
| CN106789166B (en) | Method and device for network element batch configuration | |
| CN113434396A (en) | Interface test method, device, equipment, storage medium and program product | |
| CN107229628B (en) | Distributed database preprocessing method and device | |
| CN113590433B (en) | Data management method, data management system, and computer-readable storage medium | |
| CN111367690A (en) | Method and device for supporting combined API service calling | |
| CN114615242A (en) | Data interaction method, server, terminal and computer readable storage medium | |
| CN114666411B (en) | Request processing method, device, server, storage medium and product | |
| CN108694040B (en) | Call processing method and device and communication system | |
| CN109005163A (en) | A kind of HTTP dynamic requests service calling method | |
| CN113031569B (en) | Monitoring method, system, terminal and medium of nuclear fusion control system | |
| WO2017167285A1 (en) | Remote-desktop video-encoding method and device | |
| CN110768855B (en) | Method and device for testing linkmzation performance | |
| CN110943895A (en) | Network shutdown and Linux system-based network data processing method and device | |
| US20210224272A1 (en) | Method, device, computer apparatus, and storage medium for storing data | |
| CN110569673A (en) | Data file processing method, device, equipment and storage medium | |
| CN111240690A (en) | Service processing method, device, equipment and storage medium based on policy mode | |
| CN117119078A (en) | Privacy task scheduling method and device based on Kubernetes cluster interconnection scheduling framework | |
| CN115550200B (en) | Method and device for associating server IP (Internet protocol) with service identifier |
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 |