Aggregation method, device and equipment for similar functions in different applications and medium

Abstract

The invention provides an aggregation method and device for similar functions in different applications, equipment and a medium, relates to the field of big data, and can be applied to the financial field or other fields. The method can be applied to an aggregation platform server, and comprises the following steps: receiving a transaction request sent based on an operation of a user on an aggregation platform client; sending the transaction request and the user information to N application servers in communication connection with the aggregation platform server; receiving feedback information of each application server; wherein each application server side matches a user of the application server side according to the user information: if the matching is successful, the feedback information comprises first feedback information of the application server side responding to the transaction request; if the matching fails, the feedback information comprises second feedback information that the application server side cannot respond to the transaction request; and sending the first feedback information to the aggregation platform client, and displaying one piece of first feedback information in each secondary page in the aggregation platform client.

Description

Technical Field

[0001] The present disclosure relates to the field of big data and can be used in the financial field or other fields. More specifically, it relates to a method, device, equipment, medium and program product for aggregating similar functions in different applications. Background Art

[0002] There are many mobile applications (Application, APP) at present, and even similar functions have many competitors. When users want to obtain a certain service from different APPs, since each APP is completely independent and unrelated, users can only perform similar repetitive operations in each APP. At the same time, if users need to compare the results in each APP, they can only initiate the same transaction in each APP, and then manually switch the APP interface to compare the differences by eye movement. In this way, not only is it necessary to initiate the same transaction multiple times through repeated operations, which is time-consuming and troublesome, but it is also very inconvenient when comparing the results. If there are many results that need to be compared, it is even more difficult to deal with. In addition, after initiating similar transactions from different APPs, it is necessary to manually cancel the unnecessary transactions one by one from different APPs, which may lead to redundant transactions due to the simultaneous completion of similar transactions on different APPs or forgetting to cancel, causing unnecessary losses. Summary of the invention

[0003] In view of the above problems, the present disclosure provides a method, apparatus, device, medium and program product for aggregating similar functions in different applications.

[0004] In the first aspect of the disclosed embodiment, a method for aggregating similar functions in different applications is provided, which is applied to an aggregation platform server. The method includes: receiving a transaction request sent based on a transaction initiation operation by a user in a primary page of an aggregation platform client; sending the transaction request and the user information of the user to N application servers that are communicatively connected to the aggregation platform server, where N is an integer greater than 1; receiving feedback information from each of the application servers; wherein each of the application servers matches its own user according to the user information: if the match is successful, the feedback information includes first feedback information that the application server responds to the transaction request; if the match fails, the feedback information includes second feedback information that the application server cannot respond to the transaction request; and sending the first feedback information to the aggregation platform client, wherein the aggregation platform client is used to display the first feedback information in a secondary page.

[0005] According to an embodiment of the present disclosure, when m first feedback information are received, m is an integer greater than 1 and less than or equal to N, then after sending the first feedback information to the aggregation platform client, the method also includes: obtaining transaction confirmation information determined based on the m first feedback information; the transaction confirmation information is used to instruct the user to obtain services from a first application server, wherein the first application server is one of the m application servers corresponding to the m first feedback information; forwarding the transaction confirmation information to the first application server to provide services to the user through the first application server; and notifying other application servers among the m application servers except the first application server that the transaction is completed.

[0006] According to an embodiment of the present disclosure, the acquisition of transaction confirmation information determined based on m first feedback information includes: receiving the transaction confirmation information sent based on the transaction confirmation operation of the user in one of the secondary pages, wherein the application server corresponding to the secondary page where the user performs the transaction confirmation operation is the first application server.

[0007] According to an embodiment of the present disclosure, the obtaining of transaction confirmation information determined based on m first feedback information includes: when the first feedback information belongs to a situation where the transaction is refreshed over time and automatically confirmed, the first feedback information of the automatically confirmed transaction is sorted according to a predetermined sorting method, and the transaction confirmation information is obtained based on the transaction confirmed in the first feedback information sorted first.

[0008] According to an embodiment of the present disclosure, the notifying other application server terminals among the m application server terminals except the first application server terminal of the completion of the transaction includes: receiving a polling request from the other application server terminals; querying the transaction confirmation information based on the polling request; and when the transaction confirmation information is queried, notifying the other application server terminals of the completion of the transaction.

[0009] According to an embodiment of the present disclosure, the method also includes: after receiving the second feedback information, sending a registration request for registration based on the user information to the second application server that sends the second feedback information; receiving registration feedback information from the second application server; and when the registration feedback information includes registration response information allowing registration based on the user information, sending the registration response information to the aggregation platform client, wherein the aggregation platform client is used to display a registration page obtained based on the registration response information to the user.

[0010] According to an embodiment of the present disclosure, before sending the transaction request and the user information of the user to N application servers that are communicatively connected to the aggregation platform server, the method further includes: configuring to communicate with the N application servers respectively through standardized application program interfaces.

[0011] The second aspect of the disclosed embodiment provides a method for aggregating similar functions in different applications, which is applied to an aggregation platform client. The method includes: sending a transaction request to an aggregation platform server based on a transaction initiation operation by a user in a primary page; receiving a first feedback message sent by the aggregation platform server; and displaying one of the first feedback messages in each secondary page. The aggregation platform server is used to: send the transaction request and the user information of the user to N application servers that are communicatively connected to the aggregation platform server, where N is an integer greater than 1; receive feedback information from each of the application servers, where each of the application servers matches its own user according to the user information, and if the match is successful, the feedback information includes the first feedback information of the application server responding to the transaction request; if the match fails, the feedback information includes the second feedback information that the application server cannot respond to the transaction request; and send the first feedback information to the aggregation platform client.

[0012] According to an embodiment of the present disclosure, displaying the first feedback information in each secondary page includes: determining a standard plug-in for rendering the first feedback information based on information of the application server that sends the first feedback information; and rendering the first feedback information in the secondary page using the standard plug-in.

[0013] According to an embodiment of the present disclosure, the receiving of the first feedback information sent by the aggregation platform server includes: receiving m first feedback information, where m is an integer greater than 1 and less than or equal to N. The method also includes: sending transaction confirmation information to the aggregation platform server based on the transaction confirmation operation of the user in one of the secondary pages; and closing the secondary pages other than the secondary page that receives the transaction confirmation operation.

[0014] According to an embodiment of the present disclosure, the receiving of the first feedback information sent by the aggregation platform server includes: receiving m first feedback information, wherein m is an integer greater than 1 and less than or equal to N. The method further includes: when the first feedback information belongs to the situation where the transaction is refreshed over time and the transaction is automatically confirmed, if the transaction confirmation information actively sent by the aggregation platform server is received, the secondary page other than the secondary page corresponding to the transaction confirmation information is closed; wherein the aggregation platform server sorts the first feedback information of the automatically confirmed transaction according to a predetermined sorting method, and obtains the transaction confirmation information based on the transaction confirmed in the first ranked first feedback information.

[0015] According to an embodiment of the present disclosure, the method further includes: receiving the registration response information sent by the aggregation platform server, displaying the registration page obtained based on the registration response information, so as to guide the user to register in the second application server through the registration page. Wherein, the aggregation platform server is also used for: after receiving the second feedback information, sending a registration request for registration based on the user information to the second application server that sent the second feedback information, receiving the registration feedback information of the second application server, and when the registration feedback information includes the registration response information allowing registration based on the user information, sending the registration response information to the aggregation platform client; and

[0016] In a third aspect of the disclosed embodiment, there is provided an aggregation device for the same type of functions in different applications, which can be set on an aggregation platform server. The aggregation device includes a first front-end and back-end interaction module and a multi-application interaction module. The first front-end and back-end interaction module is used to receive a transaction request sent based on a transaction initiation operation of a user in a primary page of an aggregation platform client. The multi-application interaction module is used to send the transaction request and the user information of the user to N application servers that are connected to the aggregation platform server in communication, where N is an integer greater than 1; and receive feedback information from each application server; each application server matches its own user according to the user information: if the match is successful, the feedback information includes the first feedback information that the application server responds to the transaction request; if the match fails, the feedback information includes the second feedback information that the application server cannot respond to the transaction request. The first front-end and back-end interaction module is also used to send the first feedback information to the aggregation platform client, where the aggregation platform client is used to display the first feedback information in a secondary page.

[0017] According to an embodiment of the present disclosure, the aggregation device also includes a first transaction result linkage module. The first transaction result linkage module is used to: when receiving m first feedback information, obtain transaction confirmation information determined based on the m first feedback information, the transaction confirmation information is used to instruct the user to obtain services from the first application server, wherein the first application server is one of the m application servers corresponding to the m first feedback information; forward the transaction confirmation information to the first application server to provide services to the user through the first application server; and notify the other application servers among the m application servers except the first application server that the transaction is completed. Wherein, m is an integer greater than 1 and less than or equal to N.

[0018] According to an embodiment of the present disclosure, the multi-application interaction module is also used to send a registration request for registration based on the user information to the second application server that sends the second feedback information after receiving the second feedback information; and receive registration feedback information from the second application server. The first front-end and back-end interaction module is used to: when the registration feedback information includes registration response information that allows registration based on the user information, send the registration response information to the aggregation platform client, wherein the aggregation platform client is used to display a registration page obtained based on the registration response information to the user.

[0019] In a fourth aspect of the embodiments of the present disclosure, there is provided an aggregation device for the same functions in different applications, which is arranged in an aggregation platform client. The aggregation device includes a second front-end and back-end interaction module and a user interaction module. The second front-end and back-end interaction module is used to: send a transaction request to the aggregation platform server based on the transaction initiation operation of the user in the first-level page, and receive the first feedback information sent by the aggregation platform server. The user interaction module is used to display one first feedback information in each second-level page.

[0020] According to an embodiment of the present disclosure, the aggregation device may further include a second transaction result linkage module. The second transaction result linkage module is used to: when the second front-end and back-end interaction module receives m first feedback information, based on the transaction confirmation operation of the user in one of the secondary pages, send transaction confirmation information to the aggregation platform server; and close the secondary pages other than the secondary page that receives the transaction confirmation operation, wherein m is an integer greater than 1 and less than or equal to N. Alternatively, the second transaction result linkage module is used to: when the second front-end and back-end interaction module receives m first feedback information, when the first feedback information belongs to the situation of refreshing and automatically confirming the transaction over time, if the transaction confirmation information actively sent by the aggregation platform server is received, close the secondary pages other than the secondary page corresponding to the transaction confirmation information, wherein the aggregation platform server sorts the first feedback information of the automatically confirmed transaction according to a predetermined sorting method, and obtains the transaction confirmation information based on the transaction confirmed in the first-ranked first feedback information.

[0021] According to the disclosed embodiment, the second front-end and back-end interaction module is also used to receive the registration response information sent by the aggregation platform server. The user interaction module is also used to: based on the registration response information, display a registration page to guide the user to register in the second application server through the registration page. Among them, the aggregation platform server is also used to: after receiving the second feedback information, send a registration request for registration based on the user information to the second application server that sent the second feedback information, receive the registration feedback information of the second application server, and when the registration feedback information includes registration response information allowing registration based on the user information, send the registration response information to the aggregation platform client.

[0022] In a fifth aspect of the embodiments of the present disclosure, a aggregation platform is provided. The aggregation platform includes an aggregation platform client and an aggregation platform server. The aggregation platform client is used to execute the method provided in the second aspect. The aggregation platform server is used to execute the method provided in the first aspect.

[0023] In a sixth aspect of the embodiments of the present disclosure, an electronic device is provided. The electronic device includes one or more processors and a memory. The memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors execute the aggregation method of the same type of functions in different applications described in the first aspect or the second aspect.

[0024] In a seventh aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, on which executable instructions are stored. When the instructions are executed by a processor, the processor executes the method for aggregating similar functions in different applications as described in the first or second aspect above.

[0025] In an eighth aspect of an embodiment of the present disclosure, a computer program product is also provided, including a computer program, which, when executed by a processor, implements the method for aggregating similar functions in different applications as described in the first or second aspect above.

[0026] One or more of the above-mentioned embodiments have the following advantages or beneficial effects: by initiating a transaction once, the back-end services of multiple applications can be called up for service response, and the interfaces of each application can be centrally displayed in the aggregation platform client, making it convenient for users to centrally view similar functional products provided by multiple applications, greatly improving the user experience and reducing multiple repeated redundant operations on different applications when users use similar functions. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] The above contents and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0028] Figure 1 Schematically showing an application scenario diagram of a method, apparatus, device, medium, and program product for aggregating similar functions in different applications according to an embodiment of the present disclosure;

[0029] Figure 2 A flowchart schematically shows a method for aggregating similar functions in different applications according to an embodiment of the present disclosure;

[0030] Figure 3 A flowchart of transaction result linkage applied to an aggregation platform server in another embodiment of the present disclosure is schematically shown;

[0031] Figure 4 A user registration flow chart applied to a aggregation platform server in yet another embodiment of the present disclosure is schematically shown;

[0032] Figure 5 A flowchart of the application of the aggregation method according to an embodiment of the present disclosure in a taxi service scenario is schematically shown;

[0033] Figure 6 A block diagram of an aggregation device disposed at an aggregation platform service end according to an embodiment of the present disclosure is schematically shown;

[0034] Figure 7 A block diagram schematically shows an aggregation device disposed on an aggregation platform client according to an embodiment of the present disclosure; and

[0035] Figure 8 The block diagram schematically shows an electronic device suitable for implementing the method for aggregating similar functions in different applications according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0036] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0037] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0038] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification, and should not be interpreted in an idealized or overly rigid manner.

[0039] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0040] The embodiments of the present disclosure provide a method, apparatus, device, system, medium and program product for aggregating similar functions in different applications. According to the embodiments of the present disclosure, similar functions in different applications can be aggregated in an aggregation platform. When the aggregation platform is connected with user information in each application, a user initiates a transaction in the aggregation platform client, and then the transaction required by the user can be called up from each application server through the communication between the aggregation platform server and each application server, thus avoiding the trouble of the user operating separately in each application.

[0041] Moreover, according to other embodiments of the present disclosure, after confirming through the aggregation platform that the user has accepted the service from a certain application, the aggregation platform can send the transaction confirmation information to the server of the corresponding application, and can correspondingly notify other application servers to end the transaction, thereby realizing the transaction linkage in different applications, so that there is no need to worry about redundant transactions due to failure to cancel transactions in other applications in time.

[0042] In the technical solution of the present invention, the user information involved (including but not limited to user personal information (such as mobile phone number), user image information, user device information, such as location information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) are all information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of relevant data comply with the relevant laws, regulations and standards of relevant countries and regions, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0043] Figure 1 An application scenario diagram schematically illustrates a method, apparatus, device, medium, and program product for aggregating similar functions in different applications according to an embodiment of the present disclosure.

[0044] like Figure 1 As shown, the application scenario 100 according to this embodiment may include an aggregation platform client 101, an aggregation platform server 102, and application servers A, B, C, and D of each APP.

[0045] The aggregation platform client 101 and the aggregation platform server 102 constitute the aggregation platform of the embodiment of the present disclosure. Users can interact with the aggregation platform server 102 through the aggregation platform client 101, such as initiating transaction requests, receiving transaction results, etc.

[0046] The aggregation platform client 101 can be an independent APP application (such as mobile banking) or a function in an APP application (such as a taxi service aggregation function in mobile banking).

[0047] The aggregation platform server 102 refers to a backend server that receives and processes user transaction requests.

[0048] The application servers A, B, C, and D of each APP are the background servers corresponding to different APP applications.

[0049] The aggregation platform server 102 may include a storage module and an execution module. The storage module may store user information, standard plug-ins corresponding to the application servers A, B, C, and D, standard API interfaces, and messages, etc. The execution module is used to interact with the aggregation platform client 101 on the one hand, and with the application servers A, B, C, and D on the other hand. Specifically, when the aggregation platform server 102 interacts with the application servers A, B, C, and D, it forwards and receives messages by calling the standard application program interface (also called "standard API interface") corresponding to the application servers A, B, C, and D.

[0050] The aggregation platform server 102 can send the feedback information of the application servers A, B, C, and D to the aggregation platform client 101. The aggregation platform client 101 can render the first feedback information (i.e., the response information to the transaction request) from each application server as the application interface of each application according to the standard plug-in corresponding to each application server, and can display it in the aggregation platform client 101 in the form of a floor page, so that the application interfaces of the application servers A, B, C, and D can be displayed in the aggregation platform client 101, so that users can centrally view or compare the products or services provided in each APP.

[0051] Similar functions in different applications in the embodiments of the present disclosure may be, but are not limited to, any one of the functions such as taxi-hailing, financial management, shopping, or fast delivery, and may be freely expanded as needed in actual applications.

[0052] It should be noted that the methods, devices, equipment, media and program products for aggregating similar functions in different applications determined in the embodiments of the present disclosure can be used in the financial field, and can also be used in any field other than the financial field. The present disclosure does not limit the application field.

[0053] Understandably, Figure 1 The examples shown are merely examples of system architectures to which the embodiments of the present invention may be applied, to help those skilled in the art understand the technical content of the present invention, but do not mean that the present invention cannot be used in other devices, systems, environments or scenarios.

[0054] The following will be based on Figure 1 The application scenario described by Figure 2 to Figure 5 The method for aggregating similar functions in different applications of the embodiments of the present disclosure is described in detail.

[0055] Figure 2 The flowchart schematically shows a method for aggregating similar functions in different applications according to an embodiment of the present disclosure.

[0056] like Figure 2As shown, in the method for aggregating similar functions in different applications according to an embodiment of the present disclosure, the aggregation platform client 101 can perform operations S211 to S213; the aggregation platform server 102 can perform operations S221 to S224.

[0057] First, the aggregation platform client 101 executes operation S211 to send a transaction request to the aggregation platform server 102 based on the transaction initiation operation of the user in the first-level page.

[0058] Then, the aggregation platform server 102 executes operations S221 to S224.

[0059] Specifically, in operation S221, a transaction request is received based on a transaction initiation operation by a user in the primary page of the aggregation platform client 101. The transaction request may include public information required when initiating a transaction of the same function from application servers A, B, C, and D. For example, when a user wants to call a taxi through multiple taxi apps, the public information may be the departure and destination entered by the user in the primary page of the aggregation platform client 101. For another example, when a user wants to filter financial products through multiple platforms, the public information may be the filtering condition information (such as rate of return, amount, etc.) of the financial products entered by the user.

[0060] In operation S222, the transaction request and the user information of the user are sent to N application servers that are communicatively connected to the aggregation platform server 102, where N is an integer greater than 1. For example, the information in the transaction request and the user information are encapsulated according to a standard application program interface corresponding to each application server to obtain a forwarding message, and then the forwarding message is sent to each application server through the standard application program interface.

[0061] In operation S223, feedback information from each application server is received. Each application server matches its own user according to the user information: if the match is successful, the feedback information includes first feedback information that the application server responds to the transaction request; if the match fails, the feedback information includes second feedback information that the application server cannot respond to the transaction request.

[0062] In the embodiment of the present disclosure, when the aggregation platform server 102 is connected to a user in an application server, the aggregation platform server 102 can call up a corresponding service for the user from the application server to form first feedback information.

[0063] The so-called user connection means that the user in the aggregation platform server 102 is also a user in the application server, and the user can be uniquely matched in the application server through the user information provided by the aggregation platform server 102. For example, when the user's mobile phone number is registered in the aggregation platform server 102, and the mobile phone number is also used in the user registration process in the application servers A, B, C, and D, the aggregation platform server 102 can forward the user's mobile phone number to the application servers A, B, C, and D to match the application servers A, B, C, and D's own users. If there are users registered with the same mobile phone number in the application servers A, B, C, and D, the match is considered successful. Registration with the user's mobile phone number can be to use the user's mobile phone number as the user's identity identifier, or to use the user's mobile phone number to authenticate and authorize the user's account or identity information.

[0064] In operation S224 , first feedback information is sent to the aggregation platform client 101 .

[0065] The first feedback information that the application server responds to the transaction request may be static information or information that is constantly and dynamically refreshed. For example, when the embodiment of the present disclosure is used to screen financial products, the first feedback information fed back by each application server may be the financial products screened out in the system of each application program according to the conditions input by the user. In this case, the first feedback information belongs to static information and is a result set. For another example, when the embodiment of the present disclosure is used to call multiple taxi-hailing software to hail a taxi, the first feedback information fed back by each application server may be the information of each taxi-hailing software calling a taxi. In this case, the first feedback information belongs to dynamically refreshed information, including the current calling time, the vehicle conditions around the user's current location, whether the vehicle has been called, and other constantly refreshed information. For the first feedback information that is dynamically refreshed, the application server may send update information to the aggregation platform server 102 at a certain frequency, or the application server may send update information to the aggregation platform server 102 when a predetermined trigger event (for example, calling a car) occurs.

[0066] Next, the aggregation platform client 101 performs operations S212 to S213 .

[0067] In operation S212 , first feedback information sent by the aggregation platform server 102 is received.

[0068] In operation S213, a first feedback information is displayed in each secondary page. For example, in each secondary page, the first feedback information is rendered as a user interface of a corresponding application program using a corresponding standard plug-in.

[0069] In the disclosed embodiment, the terms "primary page" and "secondary page" are used to distinguish between pages with two different functions in the aggregation platform client 101. The primary page refers to a page where a user needs to enter public information (such as the starting address information when taking a taxi) when initiating a transaction, and the public information entered in the primary page can be passed to multiple application servers. Each secondary page corresponds to an application server (or application), and a secondary page refers to a page in the aggregation platform client 101 for displaying the application interface of the corresponding application.

[0070] In one embodiment, when user information in multiple application servers is successfully matched, an APP user interface can be displayed in each secondary page in a floor layout or other layout methods in the aggregation platform client 101. In this way, the response results of the same functions and the same transaction request in different applications can be displayed in a centralized manner, which is convenient for users to compare and select the service content they like.

[0071] Furthermore, in addition to allowing users to display transaction response results of similar functions in different applications on the aggregation platform client 101 through a single initiation operation, the embodiments of the present disclosure can also realize the linkage of transaction response results in different applications based on the user's selection and confirmation of the transaction response results.

[0072] Figure 3 A transaction result linkage flow chart applied to the aggregation platform server 102 in another embodiment of the present disclosure is schematically shown.

[0073] like Figure 3 As shown, according to an embodiment of the present disclosure, after providing feedback information of an application server to the user through each secondary page in the aggregation platform client 101, the aggregation platform server 102 may further perform operations S225 to S227.

[0074] In operation S225, the aggregation platform server 102 obtains transaction confirmation information determined based on m (m may be greater than 1) first feedback information, and the transaction confirmation information is used to instruct the user to obtain services from the first application server (such as application server A).

[0075] Then in operation S226, the aggregation platform server 102 forwards the transaction confirmation information to the first application server to provide services to the user through the first application server.

[0076] Next, in operation S227, the aggregation platform server 102 may notify other application servers (e.g., application servers B and C) among the m application servers except the first application server that the transaction is completed. The aggregation platform server 102 may actively send a notification of the transaction completion to other application servers, or the aggregation platform server 102 may also receive a polling request from each application server, and query whether there is currently a user's transaction confirmation information according to the received polling request. If the transaction confirmation information is found, the application server that came to poll may be notified to complete the transaction. In this way, the transactions in other application servers are automatically cancelled to avoid the occurrence of redundant transactions.

[0077] The transaction confirmation information obtained by the aggregation platform server 102 in the above operation S225 may be generated by the transaction confirmation operation of the user in the aggregation platform client 101, or may be obtained by the aggregation platform server 102 after processing the first feedback information of multiple application servers.

[0078] Specifically, in some embodiments, the user can check the secondary pages of each application server in the aggregation platform client 101. When the user finds a satisfactory service or product, the transaction confirmation operation can be performed in the corresponding secondary page, and then the aggregation platform client 101 can send the transaction confirmation information generated based on the user's transaction confirmation operation to the aggregation platform server 102, so that the aggregation platform server can receive the transaction confirmation information. In this case, after the aggregation platform client 101 receives the transaction confirmation operation of the user in a certain secondary page, the other secondary pages in the aggregation platform client can be closed accordingly, thereby realizing the automation, linkage and unified management of the secondary pages of multiple application servers in the aggregation platform client 101. For example, when the user selects an express service, when the user selects an express and submits the confirmation, the secondary pages of other express services can be automatically closed. For another example, in a taxi service, when several taxi applications have called a car, if the user actively confirms the taxi call in a taxi application, other secondary pages are automatically closed. For another example, when a user selects financial products or other commodities, if the user selects the product and submits the payment on the secondary page of a certain application, other secondary pages can be automatically closed (of course, for the secondary pages of financial products or commodity purchase applications, the user can also be asked whether he wants to close other secondary pages, and then the other secondary pages can be automatically closed at once when the user agrees to close them).

[0079] In other embodiments, when the first feedback information displayed in each secondary page in the aggregation platform client 101 is refreshed over time and automatically confirms the transaction (for example, the taxi-hailing software needs to constantly search for a vehicle when calling a taxi, and will notify the user that the vehicle has been found when a vehicle accepts the order), if the user does not actively confirm in the aggregation platform client 101, the aggregation platform server 102 can also sort the first feedback information that automatically confirms the transaction in each secondary page according to a predetermined sorting method (for example, time priority, distance priority, or service score priority, etc.), and obtain the transaction confirmation information based on the transaction confirmed in the first feedback information ranked first in the above operation S250. In this case, the aggregation platform server 102 can actively send the obtained transaction confirmation information to the aggregation platform client 101, so that the aggregation platform client 102 can close the secondary pages other than the secondary page corresponding to the transaction confirmation information.

[0080] In addition, in the embodiment of the present disclosure, when the aggregation platform server 102 receives the second feedback message sent by a certain application server because the user information does not match in the above operation S223, it also guides the user to register in the application server using the user information in the aggregation platform. Figure 4 Introduction.

[0081] Figure 4 A user registration flow chart applied to the aggregation platform server 102 in yet another embodiment of the present disclosure is schematically shown.

[0082] like Figure 4 As shown, according to this embodiment, after the aggregation platform server 102 receives the second feedback message sent by any application server, the aggregation platform server 102 can perform operations S401 to S403 to guide the user to register in the application server.

[0083] In operation S401, after receiving the second feedback information, a registration request for registering based on the user information is sent to the second application server (eg, application server D) that sends the second feedback information.

[0084] Then in operation S402, registration feedback information from the second application server is received.

[0085] Next, in operation S403 , when the registration feedback information includes registration response information that allows registration based on the user information, the registration response information is sent to the aggregation platform client 101 .

[0086] Accordingly, after receiving the registration response information sent by the aggregation platform server 102, the aggregation platform client 101 can display the registration page obtained based on the registration response information to the user, so as to guide the user to register in other applications using the user information in the aggregation platform. In this way, the user in the application program connected to the aggregation platform server 102 can quickly register, and the user information in the aggregation platform and other applications can also be connected.

[0087] The aggregation method of the disclosed embodiment can be applied in the taxi service scenario. Specifically, the taxi functions of various application APPs can be aggregated in the aggregation platform to help users call a taxi from multiple taxi apps at the same time through a one-time initiation in the aggregation platform client 101, and when the user confirms the transaction of calling a taxi in the aggregation platform client 101, the taxi service in other taxi apps is automatically terminated. Figure 5 , the implementation process of the method of the embodiment of the present disclosure is described by taking a taxi as an example. It can be understood that the taxi-hailing function can be extended to any other function.

[0088] Figure 5 The following schematically shows a flow chart of the application of the aggregation method according to an embodiment of the present disclosure in a taxi service scenario. Figure 5 As shown, the process involves three parties: the aggregation platform client 101, the aggregation platform server 102 and each application server.

[0089] Among them, after the user logs in to the aggregation platform client 101, he can enter public information, such as departure place and destination information, on the first-level page of the taxi-hailing function.

[0090] The aggregation platform server 102 is responsible for calling the standardized API interface for communicating with each taxi application server to send user information, departure point, and destination information to each taxi application server.

[0091] Each taxi-hailing application server determines the user information status based on the received user information. If normal, it returns a call success notification to the aggregation platform server 102, and displays the service page of the taxi-hailing application in the secondary page of the aggregation platform client 101, and enters the taxi-hailing process. Among them, the application interfaces of different taxi-hailing applications can be displayed in the aggregation platform server 102 in the form of secondary pages arranged in the form of floors.

[0092] The user can click any floor in the aggregation platform client 101 to enter the secondary page of a taxi-hailing application and view the details of the taxi-hailing service. The taxi-hailing information of each taxi-hailing application can be updated to the secondary page of the aggregation platform client 101 in real time, or can be updated to the secondary page at a certain frequency, or the update of the secondary page can be triggered by the event of whether a taxi is called.

[0093] In one embodiment, if a taxi-hailing application first calls a car, it can wait for a predetermined time to see whether the user confirms to accept the taxi-hailing service. If the user does not confirm, the taxi-hailing application can give up the taxi-hailing. If the user confirms to accept, the taxi-hailing application server calls the standardized API interface that communicates with the aggregation platform server 102 and notifies the aggregation platform server 102. After receiving the notification message, the aggregation platform server 102 notifies other taxi-hailing software to stop the taxi-hailing service. In this way, when multiple taxi-hailing applications call a taxi separately, they can wait for a predetermined time for the user to confirm after calling a taxi. In this way, when multiple taxi-hailing applications call a taxi, the user can choose the itinerary that he or she is most satisfied with.

[0094] In another embodiment, when each taxi-hailing application calls a taxi separately, it is not necessary to wait for the user to perform a confirmation operation on the secondary page of the taxi service. Instead, the services (if any) that have been called in multiple taxi-hailing applications can be sorted according to a predetermined sorting method (for example, distance priority, estimated price priority, or the time of calling the taxi) within a predetermined time (for example, 1 minute) from the time when the first taxi is called, and then the taxi service ranked first can be selected for confirmation, and then the other taxi applications can be notified to terminate the taxi service.

[0095] Among them, each taxi application server can be connected to the aggregation platform server 102 through a standardized API interface. The standardized API interface supports the aggregation platform server 102 to send messages encapsulating user information and transaction requests.

[0096] User information needs to be communicated between the aggregation platform and each taxi-hailing application. For example, when the aggregation platform client 101 uses the mobile phone number as the unique identifier of user information, after the user logs in to the aggregation platform client 101 through the mobile phone number to initiate a transaction, the aggregation platform server 102 calls the standardized API interface that communicates with each taxi-hailing application server to send the user information. If the taxi-hailing application also uses the mobile phone number as the user identifier, it will directly match whether the user is in the taxi-hailing application. If so, it will return a successful query and call up the taxi service; if not, it can guide the user to authorize the mobile phone number to register and log in and call up the taxi service. If the taxi-hailing application does not use the mobile phone number as the user identifier, when the mobile phone number is used for user authorization, the mobile phone number is supplemented in the secondary page returned by the taxi-hailing application and the user identifier of the taxi-hailing application is associated, and then the subsequent functions are supported to be used normally. The SM4.0 encryption algorithm can be used for the transmission of user information between the taxi-hailing application server and the aggregation platform server 102.

[0097] Among them, the aggregation platform client 101 provides an aggregation function platform page, which can be divided into multiple floors. The system automatically allocates and supports users to independently configure which taxi application service is displayed on each floor, that is, floor ID (mod ID) + application ID (AppID).

[0098] Among them, the aggregation platform client 101 can provide standard plug-ins corresponding to each taxi-hailing application, and the service content fed back by each taxi-hailing application is packaged according to the standard plug-in and displayed on the secondary page, wherein the service content includes the information of the taxi-hailing service application interface + the specified secondary page information.

[0099] The aggregation platform server 102 provides a standardized API interface for connecting with various taxi-hailing application servers, supports the service content returned by each taxi-hailing application, and can receive taxi-hailing results obtained by each taxi-hailing application through polling. After confirming that the user accepts the service of a taxi-hailing application to call a car, the aggregation platform server 102 can notify other taxi-hailing applications to end the taxi-hailing.

[0100] In one embodiment, the transaction process for a user to hail a taxi using multiple taxi-hailing applications APPs through the aggregation platform client 101 may include the following steps S1 to S18.

[0101] S1: A user registers or logs in to the aggregation platform client 101 using a user ID (eg, mobile phone number).

[0102] S2: The aggregation platform server 102 verifies and stores the user's mobile phone number.

[0103] S3: The user selects a desired function on the aggregation platform client 101, such as taking a taxi.

[0104] S4: The user enters the requested information, such as the departure point and the destination;

[0105] S5: The aggregation platform server 102 sends transaction request information such as user mobile phone number, departure place and destination to each taxi application through the standardized API interface corresponding to each taxi application.

[0106] S6: Each taxi-hailing application server queries whether there is a user registered or authorized with the mobile phone number in each taxi-hailing application. If there is, jump to S11, if not, continue to S7.

[0107] S7: If not, the user is prompted whether to register with the mobile phone number.

[0108] S8: If the user does not register, only the registered taxi-hailing application is called. If there is no registered taxi-hailing application, the transaction is terminated.

[0109] S9: If the user registers, the aggregation platform server 102 sends an instruction to guide the user to register.

[0110] S10: The user completes registration on the aggregation platform client 101.

[0111] S11: Each taxi-hailing application server generates service content in response to the transaction request and completes standard plug-in integration;

[0112] S12: The aggregation platform server 102 receives and stores the service content and the specification plug-in;

[0113] S13: assigning an application ID to each taxi-hailing application, and summarizing and arranging each result item;

[0114] S14: Matching an application ID to each secondary page in the aggregation platform client 101, and displaying the service content rendered by using the standard plug-in in the corresponding secondary page;

[0115] S15: The user selects one or more taxi-hailing applications through comparison in the aggregation platform client 101 to complete the taxi-hailing process;

[0116] S16: If a taxi-hailing application first calls a car and the user confirms;

[0117] S17: The aggregation platform server 102 calls the standardized API interface to notify the user of the confirmed taxi-hailing application;

[0118] S17.1: The aggregation platform server 102 calls the standardized API interface to notify other taxi applications to stop the taxi service;

[0119] S17.2: The taxi-hailing application confirmed by the user completes the subsequent service;

[0120] S18: After S14, users can click on the secondary page of any taxi-hailing application and enter the interface of the taxi-hailing application to view more taxi-hailing services.

[0121] In the above embodiment, S11-S14 are the transaction processes of each taxi application server end accessing the aggregation platform server end 102. Among them, for the application that has been connected to the aggregation platform server end 102, S11-S14 are no longer involved in the transaction process, that is, there is no need to integrate the standard plug-ins and generate the service pages of each application on each floor. The aggregation platform server end 102 can directly call the existing standard plug-ins to complete the transaction. The user can directly click on the secondary page of each taxi application and click on any secondary page to enter the interface of the taxi application.

[0122] According to the above introduction, it can be seen that the embodiments of the present disclosure reduce the multiple repeated redundant operations of users on different applications when using similar functions by aggregating similar functions in different applications in the aggregation platform. Moreover, according to the embodiments of the present disclosure, the back-end services of multiple applications can be called through a single transaction initiation, and the interfaces of each application can be centrally displayed through a secondary page in the aggregation platform client 101, so that users can centrally view similar functional products provided by multiple applications, greatly improving the user experience. Moreover, when the user confirms the service or function to be received through a secondary page, other applications can be notified in time to terminate the transaction or provide the service, thereby realizing the linkage between the applications.

[0123] Based on the aggregation method of the same type of functions in different applications of the above embodiments, the embodiment of the present disclosure also provides an aggregation device set on the aggregation platform server and an aggregation device set on the aggregation platform client. Figure 6 and 7 The corresponding devices are described in detail.

[0124] Figure 6 A block diagram of an aggregation device 600 disposed at an aggregation platform service end according to an embodiment of the present disclosure is schematically shown.

[0125] like Figure 6 As shown, the aggregation device 600 may include a first front-end and back-end interaction module 610, a multi-application interaction module 620 and a first transaction result linkage module 630. The aggregation device 600 may be arranged at the aggregation platform server 102.

[0126] The first front-end and back-end interaction module 610 is used to receive a transaction request sent based on a transaction initiation operation of a user in a primary page of the aggregation platform client 1. In one embodiment, the first front-end and back-end interaction module 610 may perform the aforementioned operation S221.

[0127] The multi-application interaction module 620 is used to: send the transaction request and the user information of the user to N application servers that are connected to the aggregation platform server, where N is an integer greater than 1; and receive feedback information from each application server; wherein each application server matches its own user according to the user information: if the match is successful, the feedback information includes first feedback information that the application server responds to the transaction request; if the match fails, the feedback information includes second feedback information that the application server cannot respond to the transaction request. In one embodiment, the multi-application interaction module 620 can perform the aforementioned operations S222 and S223.

[0128] The first front-end and back-end interaction module 610 is further used to send the first feedback information to the aggregation platform client, wherein the aggregation platform client is used to display the first feedback information in a secondary page. In one embodiment, the first front-end and back-end interaction module 610 can also perform the aforementioned operation S224.

[0129] The first transaction result linkage module 630 is used to: when receiving m first feedback information, obtain transaction confirmation information determined based on the m first feedback information, the transaction confirmation information is used to instruct the user to obtain services from the first application server, wherein the first application server is one of the m application servers corresponding to the m first feedback information; forward the transaction confirmation information to the first application server, so as to provide services to the user through the first application server; and notify the other application servers except the first application server of the end of the transaction among the m application servers, wherein m is an integer greater than 1 and less than or equal to N. In one embodiment, the first transaction result linkage module 630 can perform operations S225 to S227 described above.

[0130] In some other embodiments, the multi-application interaction module 620 is further used to send a registration request for registration based on user information to the second application server that sent the second feedback information after receiving the second feedback information; and receive registration feedback information from the second application server. Accordingly, the first front-end and back-end interaction module 610 is also used to: when the registration feedback information includes registration response information that allows registration based on user information, send registration response information to the aggregation platform client, wherein the aggregation platform client is used to display a registration page obtained based on the registration response information to the user.

[0131] The aggregation device 600 can be used to perform reference Figure 2 to Figure 5 The method executed by the aggregation platform server 102 can be specifically referred to in the previous description and will not be repeated here.

[0132] Figure 7 The block diagram of an aggregation device 700 disposed on an aggregation platform client according to an embodiment of the present disclosure is schematically shown.

[0133] like Figure 7 As shown, the aggregation device 700 includes a second front-end and back-end interaction module 710, a user interaction module 720 and a second transaction result linkage module 730. The aggregation device 700 can be set in the aggregation platform client 101.

[0134] The second front-end and back-end interaction module 710 is used to: send a transaction request to the aggregation platform server based on the transaction initiation operation of the user in the first-level page, and receive the first feedback information sent by the aggregation platform server. In one embodiment, the second front-end and back-end interaction module 710 can perform operations S211 and S212.

[0135] The user interaction module 720 is used to display a first feedback information in each secondary page. In one embodiment, the user interaction module 720 may perform operation S213.

[0136] In other embodiments, the second front-end and back-end interaction module 710 is further used to receive registration response information sent by the aggregation platform server. Accordingly, the user interaction module 720 is further used to: display a registration page based on the registration response information to guide the user to register in the second application server through the registration page.

[0137] The second transaction result linkage module 730 is used to send transaction confirmation information to the aggregation platform server based on the user's transaction confirmation operation in a secondary page when the second front-end and back-end interaction module receives m first feedback information; and close the secondary pages other than the secondary page that receives the transaction confirmation operation, where m is an integer greater than 1 and less than or equal to N.

[0138] Or in another embodiment, the second transaction result linkage module 730 is used for: when the second front-end and back-end interaction module receives m first feedback information, when the first feedback information is refreshed over time and automatically confirms the transaction, if the transaction confirmation information actively sent by the aggregation platform server is received, close the secondary pages other than the secondary page corresponding to the transaction confirmation information, wherein the aggregation platform server sorts the first feedback information of the automatic confirmation transaction according to a predetermined sorting method, and obtains the transaction confirmation information based on the transaction confirmed in the first feedback information ranked first.

[0139] Aggregation device 700 can be used to perform reference Figure 2 to Figure 5 The operations performed by the aggregation platform client described in the previous section can be found in detail in the previous section and will not be repeated here.

[0140] According to an embodiment of the present disclosure, any multiple modules among the first front-end and back-end interaction module 610, the multi-application interaction module 620, the first transaction result linkage module 630, the second front-end and back-end interaction module 710, the user interaction module 720, and the second transaction result linkage module 730 can be combined in one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the first front-end and back-end interaction module 610, the multi-application interaction module 620, the first transaction result linkage module 630, the second front-end and back-end interaction module 710, the user interaction module 720, and the second transaction result linkage module 730 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware, and firmware or in a suitable combination of any of them. Alternatively, at least one of the first front-end and back-end interaction module 610, the multi-application interaction module 620, the first transaction result linkage module 630, the second front-end and back-end interaction module 710, the user interaction module 720 and the second transaction result linkage module 730 can be at least partially implemented as a computer program module, which can execute corresponding functions when the computer program module is executed.

[0141] Figure 8 A block diagram of an electronic device 800 suitable for implementing a method for aggregating similar functions in different applications according to an embodiment of the present disclosure is schematically shown.

[0142] like Figure 8 As shown, the electronic device 800 according to an embodiment of the present disclosure includes a processor 801, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 802 or a program loaded from a storage part 808 to a random access memory (RAM) 803. The processor 801 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 801 may also include an onboard memory for caching purposes. The processor 801 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0143] In RAM 803, various programs and data required for the operation of electronic device 800 are stored. Processor 801, ROM 802 and RAM 803 are connected to each other via bus 804. Processor 801 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 802 and / or RAM 803. It should be noted that the program can also be stored in one or more memories other than ROM 802 and RAM 803. Processor 801 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in one or more memories.

[0144] According to an embodiment of the present disclosure, the electronic device 800 may further include an input / output (I / O) interface 805, which is also connected to the bus 804. The electronic device 800 may further include one or more of the following components connected to the I / O interface 805: an input portion 806 including a keyboard, a mouse, etc.; an output portion 807 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 808 including a hard disk, etc.; and a communication portion 809 including a network interface card such as a LAN card, a modem, etc. The communication portion 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to the I / O interface 805 as needed. A removable medium 811, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 810 as needed, so that a computer program read therefrom is installed into the storage portion 808 as needed.

[0145] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0146] According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus or a device. For example, according to an embodiment of the present disclosure, a computer-readable storage medium may include the ROM 802 and / or RAM 803 described above and / or one or more memories other than ROM 802 and RAM 803.

[0147] The embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program contains program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the method provided by the embodiment of the present disclosure.

[0148] The above functions defined in the system / device of the embodiment of the present disclosure are executed when the computer program is executed by the processor 801. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0149] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 809, and / or installed from a removable medium 811. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0150] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 809, and / or installed from the removable medium 811. When the computer program is executed by the processor 801, the above functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the system, device, means, module, unit, etc. described above can be implemented by a computer program module.

[0151] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

[0152] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0153] It will be appreciated by those skilled in the art that the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations and / or combinations are not explicitly described in the present disclosure. In particular, the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways without departing from the spirit and teachings of the present disclosure. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0154] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. The scope of the present disclosure is defined by the attached claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A method for aggregating similar functions in different applications, applied to an aggregation platform server, comprising: Receiving a transaction request sent based on a transaction initiation operation by a user in a primary page of an aggregation platform client; Sending the transaction request and the user information of the user to N application servers that are in communication with the aggregation platform server, where N is an integer greater than 1; receiving feedback information from each of the application servers; wherein each of the application servers matches its own user according to the user information; if the match is successful, the feedback information includes first feedback information that the application server responds to the transaction request; if the match fails, the feedback information includes second feedback information that the application server cannot respond to the transaction request; and The first feedback information is sent to the aggregation platform client, wherein the aggregation platform client is used to display one piece of the first feedback information in each secondary page.

2. The method according to claim 1, wherein: When m first feedback information is received, and m is an integer greater than 1 and less than or equal to N, after sending the first feedback information to the aggregation platform client, the method further includes: Acquire transaction confirmation information determined based on the m first feedback information; the transaction confirmation information is used to instruct the user to obtain services from a first application server, wherein the first application server is one of the m application servers corresponding to the m first feedback information; forwarding the transaction confirmation information to the first application server to provide services to the user through the first application server; and Notify the other application servers among the m application servers except the first application server that the transaction is completed.

3. The method according to claim 2, wherein: The acquiring of transaction confirmation information determined based on the m first feedback information includes: The transaction confirmation information sent based on the transaction confirmation operation performed by the user in one of the secondary pages is received, wherein the application server corresponding to the secondary page on which the user performs the transaction confirmation operation is the first application server.

4. The method according to claim 2, wherein: The acquiring of transaction confirmation information determined based on the m first feedback information includes: When the first feedback information belongs to the situation where the transaction is refreshed over time and automatically confirmed, the first feedback information of the automatically confirmed transaction is sorted according to a predetermined sorting method, and the transaction confirmation information is obtained based on the transaction confirmed in the first feedback information sorted first.

5. The method according to claim 2, wherein: The notifying other application servers among the m application servers except the first application server of the completion of the transaction comprises: Receiving a polling request from the other application server; Based on the polling request, query the transaction confirmation information; and When the transaction confirmation information is found, the other application server is notified that the transaction is completed.

6. The method according to claim 1, wherein: The method further comprises: After receiving the second feedback information, sending a registration request for registration based on the user information to the second application server that sent the second feedback information; receiving registration feedback information from the second application server; and When the registration feedback information includes registration response information allowing registration based on the user information, the registration response information is sent to the aggregation platform client, wherein the aggregation platform client is used to display a registration page obtained based on the registration response information to the user.

7. The method according to claim 1, wherein: Before sending the transaction request and the user information of the user to the N application servers that are communicatively connected to the aggregation platform server, the method further includes: The N application servers are configured to communicate with each other through a standardized application program interface.

8. A method for aggregating similar functions in different applications, applied to an aggregation platform client, comprising: Based on the transaction initiation operation of the user in the first-level page, a transaction request is sent to the aggregation platform server; wherein the aggregation platform server is used to: send the transaction request and the user information of the user to N application servers that are communicatively connected to the aggregation platform server, wherein N is an integer greater than 1; receive feedback information from each of the application servers, wherein each of the application servers matches its own user according to the user information, and if the match is successful, the feedback information includes first feedback information that the application server responds to the transaction request; if the match fails, the feedback information includes second feedback information that the application server cannot respond to the transaction request; and send the first feedback information to the aggregation platform client; and receiving the first feedback information sent by the aggregation platform server; and The first feedback information is displayed in each secondary page.

9. The method according to claim 8, wherein: The displaying of the first feedback information in each secondary page includes: Determining, according to information of the application server that sends the first feedback information, a standard plug-in for rendering the first feedback information; and The first feedback information is rendered in the secondary page using the specification plug-in.

10. The method according to claim 8, wherein: The receiving the first feedback information sent by the aggregation platform server includes: receiving m pieces of the first feedback information, where m is an integer greater than 1 and less than or equal to N; The method further includes: sending transaction confirmation information to the aggregation platform server based on the transaction confirmation operation of the user in one of the secondary pages; and closing the secondary pages other than the secondary page that receives the transaction confirmation operation.

11. The method according to claim 8, wherein: The receiving the first feedback information sent by the aggregation platform server includes: receiving m pieces of the first feedback information, where m is an integer greater than 1 and less than or equal to N; The method also includes: when the first feedback information belongs to the situation where the transaction is refreshed over time and automatically confirmed, if the transaction confirmation information actively sent by the aggregation platform server is received, closing the secondary pages other than the secondary page corresponding to the transaction confirmation information; wherein the aggregation platform server sorts the first feedback information of the automatically confirmed transaction according to a predetermined sorting method, and obtains the transaction confirmation information based on the transaction automatically confirmed in the first feedback information ranked first.

12. The method according to claim 8, wherein: The method further comprises: receiving registration response information sent by the aggregation platform server, wherein the aggregation platform server is further used to: after receiving the second feedback information, send a registration request for registration based on the user information to the second application server that sent the second feedback information, receive registration feedback information from the second application server, and when the registration feedback information includes registration response information allowing registration based on the user information, send the registration response information to the aggregation platform client; and Based on the registration response information, a registration page is displayed to guide the user to register in the second application server through the registration page.

13. An aggregation device for similar functions in different applications, arranged at an aggregation platform server, comprising a first front-end and back-end interaction module and a multi-application interaction module; in, The first front-end and back-end interaction module is used to: receive a transaction request sent based on a transaction initiation operation by a user in a primary page of the aggregation platform client; Wherein, the multi-application interaction module is used for: Sending the transaction request and the user information of the user to N application servers that are communicatively connected to the aggregation platform server, where N is an integer greater than 1; and receiving feedback information from each of the application servers; wherein each of the application servers matches its own user according to the user information; if the match is successful, the feedback information includes first feedback information that the application server responds to the transaction request; if the match fails, the feedback information includes second feedback information that the application server cannot respond to the transaction request; The first front-end and back-end interaction module is further used to: send the first feedback information to the aggregation platform client, wherein the aggregation platform client is used to display one first feedback information in each secondary page.

14. An aggregation device for similar functions in different applications, arranged on an aggregation platform client, comprising a second front-end and back-end interaction module and a user interaction module; in, The second front-end and back-end interaction module is used for: Based on the transaction initiation operation of the user in the first-level page, a transaction request is sent to the aggregation platform server; wherein the aggregation platform server is used to: send the transaction request and the user information of the user to N application servers that are communicatively connected to the aggregation platform server, wherein N is an integer greater than 1; receive feedback information from each of the application servers, wherein each of the application servers matches its own user according to the user information, and if the match is successful, the feedback information includes first feedback information that the application server responds to the transaction request; if the match fails, the feedback information includes second feedback information that the application server cannot respond to the transaction request; and send the first feedback information to the aggregation platform client; and Receiving the first feedback information sent by the aggregation platform server; The user interaction module is used to display the first feedback information in each secondary page.

15. A aggregation platform comprising: Aggregation platform client, used to execute the method described in any one of claims 8 to 12; as well as The aggregation platform server is used to execute the method described in any one of claims 1 to 7.

16. An electronic device, comprising: one or more processors; a memory for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors are enabled to execute the method according to any one of claims 1 to 12.

17. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to execute the method according to any one of claims 1 to 12.

Images