Request response method and device of aggregation SDK based on application docking channel, equipment and medium
Through the aggregation of SDK, unified access standards are formulated for each channel, which solves the problem of multi-channel access complexity faced by application developers, simplifies development and operation processes, and improves issuance efficiency and data statistics capabilities.
Patent Information
- Application Number
- CN202410990034.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-23
- Publication Date
- 2024-11-29
AI Technical Summary
In the prior art, application developers need to conduct separate access and maintenance for each channel, resulting in increased development and operational complexity and cost, while being detrimental to the unified management and statistics of user data and affecting the maintenance and optimization of applications.
Through the aggregation SDK, unified access standards are formulated for each channel, simplify development and operation processes, and realize unified management and data collection of each channel.
It reduces development and operation costs, improves application issuance efficiency, and facilitates the statistics and analysis of user data.
Smart Images

Figure CN119045881A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of Internet technology, and specifically relates to an application request processing method, device, equipment and medium. Background Art
[0002] With the rapid development of applications, various distribution and promotion channels have also increased significantly, bringing more user acquisition channels for application developers.
[0003] However, each channel has its own unique access method and technical specifications. For application developers, they need to access and maintain each channel separately, which greatly increases the complexity and cost of development and operation. In addition, the separate operation of each channel is not conducive to application developers to collect and count user data, which brings inconvenience to the maintenance and optimization of the application.
[0004] Therefore, how to uniformly manage the operation of various channels and improve the development efficiency of developers is a technical problem that needs to be urgently solved by technical personnel in this field. Summary of the invention
[0005] The embodiments of the present application provide a request response method, apparatus, device and medium based on an aggregate SDK of an application docking channel, with the purpose of formulating a unified access standard for the access methods and technical specifications of each docking channel through an aggregate SDK, which is conducive to simplifying the development and operation process of the application, reducing costs and improving the distribution efficiency of the application.
[0006] In a first aspect, this embodiment provides a request response method of an aggregated SDK based on an application docking channel, the method comprising:
[0007] Receive user operation requests;
[0008] Determine at least one channel SDK connected to the aggregation SDK, call an interface corresponding to the operation request to send the operation request to the channel SDK, so that the channel SDK generates response information;
[0009] Obtaining response information of the channel SDK, and sending the response information to the aggregation server, so that the aggregation server sends the response information to the channel server for response verification;
[0010] The account information fed back by the receiving channel server after verification is passed, and the operation request is responded to according to the account information.
[0011] Further, receiving the user's operation request includes:
[0012] Receive a user's login operation request;
[0013] Correspondingly, obtaining the response information of the channel SDK, and sending the response information to the aggregation server, so as to send the response information to the channel server through the aggregation server for response verification, includes:
[0014] Get the TOKEN returned by the channel SDK;
[0015] The TOKEN is sent to the aggregation server, which forwards the TOKEN to the channel server for response verification.
[0016] Furthermore, it is characterized in that the account information fed back by the channel server after verification is received, and the operation request is responded to according to the account information, including:
[0017] After the channel server verifies that the TOKEN is valid, the login account information is returned to the aggregation server;
[0018] Mapping the login account information to a platform account through the aggregation server;
[0019] Obtain the platform account, and determine the login account information corresponding to the platform account through the aggregation SDK;
[0020] The login account information is provided to the application program for performing a login operation.
[0021] Further, receiving the user's operation request includes:
[0022] Receive a user's recharge request;
[0023] Correspondingly, after receiving the recharge operation request from the user, the method further includes:
[0024] Send the recharge operation request to the channel SDK;
[0025] Displaying the recharge interface generated by the channel SDK;
[0026] Execute the user's recharge operation through the channel SDK, obtain the recharge result, and report the recharge result to the channel server for verification;
[0027] After the channel server successfully verifies, the recharge status is obtained from the channel SDK, and the recharge status is returned to the application.
[0028] Furthermore, after the channel server successfully verifies, the method further includes:
[0029] Sending a shipment request to the aggregation server through the channel server;
[0030] The aggregation server executes a response to the shipment request.
[0031] Further, receiving the user's operation request includes:
[0032] Receive data reporting operation requests from users;
[0033] After receiving the data reporting operation request from the user, the method further includes:
[0034] Obtaining data information corresponding to the data reporting operation request;
[0035] The data information is reported to the aggregation server through the aggregation SDK, and the data information is reported to the channel SDK by calling the reporting interface through the aggregation SDK, so as to report the data information to the channel server through the channel SDK.
[0036] Furthermore, the method further comprises:
[0037] If there is an update to the channel, receive the new channel SDK file;
[0038] Replace the original channel SDK file with the new channel SDK file.
[0039] In a second aspect, this embodiment provides a request response device for an aggregated SDK based on an application docking channel, the device comprising:
[0040] An operation request receiving module, used for receiving an operation request from a user;
[0041] A response information generation module, used to determine at least one channel SDK connected to the aggregation SDK, call the interface corresponding to the operation request to send the operation request to the channel SDK, so that the channel SDK generates response information;
[0042] A response information verification module, used to obtain the response information of the channel SDK, and send the response information to the aggregation server, so as to send the response information to the channel server through the aggregation server for response verification;
[0043] The operation request response module is used to receive the account information fed back by the channel server after verification, and respond to the operation request according to the account information.
[0044] In a third aspect, an embodiment of the present application provides an electronic device, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect.
[0045] In a fourth aspect, an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.
[0046] In a fifth aspect, an embodiment of the present application provides a chip, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect.
[0047] In an embodiment of the present application, a user's operation request is received; at least one channel SDK that is connected to the aggregation SDK is determined, and the interface corresponding to the operation request is called to send the operation request to the channel SDK so that the channel SDK can generate response information; the response information of the channel SDK is obtained, and the response information is sent to the aggregation server, so that the response information is sent to the channel server through the aggregation server for response verification; the account information fed back by the channel server after verification is passed, and the operation request is responded to according to the account information. Through the above-mentioned method of request response of the aggregation SDK based on the channel of application docking, a unified access standard can be formulated for the access method and technical specifications of each docking channel through the aggregation SDK, which is conducive to simplifying the development and operation process of the application, reducing costs and improving the distribution efficiency of the application. BRIEF DESCRIPTION OF THE DRAWINGS
[0048] Figure 1 It is a flowchart of a request response method of an aggregate SDK based on an application docking channel provided in Example 1 of the present application;
[0049] Figure 2 This is a schematic diagram of the login request response process of the aggregation SDK of the game APP docking channel provided in Example 1 of the present application;
[0050] Figure 3 It is a flowchart of a request response method of an aggregate SDK based on an application docking channel provided in Embodiment 2 of the present application;
[0051] Figure 4 This is a schematic diagram of the recharge request response process of the aggregation SDK of the game APP docking channel provided in Example 2 of the present application;
[0052] Figure 5 It is a flowchart of a request response method of an aggregate SDK based on an application docking channel provided in Example 3 of the present application;
[0053] Figure 6 This is a schematic diagram of the data reporting response process of the aggregation SDK of the game APP docking channel provided in Example 3 of the present application;
[0054] Figure 7 It is a flowchart of a request response method of an aggregate SDK based on an application docking channel provided in Embodiment 4 of the present application;
[0055] Figure 8 It is a structural diagram of a request response device of an aggregate SDK based on an application docking channel provided in Embodiment 5 of the present application;
[0056] Fig. 9 It is a structural diagram of an electronic device provided in Example 6 of the present application. DETAILED DESCRIPTION
[0057] In order to make the purpose, technical scheme and advantages of the present application clearer, the specific embodiments of the present application are further described in detail below in conjunction with the accompanying drawings. It is understood that the specific embodiments described herein are only used to explain the present application, rather than to limit the present application. It should also be noted that, for the convenience of description, only the part related to the present application but not all the contents are shown in the accompanying drawings. Before discussing the exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flow charts. Although the flow chart describes each operation (or step) as a sequential process, many of the operations therein can be implemented in parallel, concurrently or simultaneously. In addition, the order of each operation can be rearranged. The process can be terminated when its operation is completed, but it can also have additional steps not included in the accompanying drawings. The process can correspond to a method, a function, a procedure, a subroutine, a subprogram, etc.
[0058] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the present application belong to the scope of protection of this application.
[0059] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.
[0060] In combination with the accompanying drawings, the request response method, device, equipment and medium of an aggregate SDK based on an application docking channel provided by an embodiment of the present application are described in detail through specific embodiments and their application scenarios.
[0061] Embodiment 1
[0062] Figure 1 It is a flow chart of a request response method of an aggregated SDK based on an application docking channel provided in Example 1 of the present application.
[0063] like Figure 1 As shown, the specific steps include:
[0064] S101, receiving an operation request from a user;
[0065] The application scenario of this solution may be a scenario of responding to user requests from different channels.
[0066] Based on the above scenario, it can be understood that the execution entity of this scenario can be an application for receiving and responding to user requests, which is deployed with an aggregation SDK (Software Development Kit) and a channel SDK, such as a computer or software component that provides services in a network environment, etc., and no excessive limitations are made here.
[0067] An operation request may be an operation request such as registration, login, or recharge performed by a user in an application, which requires a response from the application.
[0068] The method of receiving user operation requests can be that the user launches the application through a terminal device such as a mobile phone or tablet, and performs operations such as clicking and inputting in the interface displayed by the application. The terminal device generates a corresponding request instruction based on the user's specific operation content, such as the click location, input content, etc., and sends it to the aggregation SDK for processing.
[0069] The aggregate SDK can be developed by collecting the access methods and technical specifications of various application channels to form a unified access standard. The aggregate SDK can enable application developers to access various channels by accessing the SDK once.
[0070] S102: Determine at least one channel SDK connected to the aggregation SDK, call an interface corresponding to the operation request, and send the operation request to the channel SDK, so that the channel SDK generates response information;
[0071] Channel SDK can be a software development kit owned by a company or platform. Channel SDK usually includes a series of functional modules, such as user entry, payment logic, and data statistics. Channel SDK is mainly used for channel management during the release and distribution of mobile applications or games.
[0072] The response information may be the processing result obtained by the channel SDK after processing the user's operation request. For example, if the user's operation request is to log in to the application, the channel SDK generates user login status verification information as the response information after processing the received user login operation request.
[0073] A method for determining at least one channel SDK that is connected to the aggregation SDK may be to analyze the user's operation request, obtain the platform information of the user's authorized login, determine the corresponding channel SDK based on the platform information, and obtain the interface address of the channel SDK.
[0074] The operation request can be sent to the channel SDK by calling the request transmission function, writing the obtained interface address into the function, and executing the complete function, thereby sending the operation request to the channel SDK through the specified interface. After receiving the operation request, the channel SDK interprets the content of the operation request, calls the relevant functional module to process the operation request, and generates response information based on the processing result.
[0075] S103, obtaining response information of the channel SDK, and sending the response information to the aggregation server, so that the aggregation server sends the response information to the channel server for response verification;
[0076] The response verification method may be that the aggregation SDK obtains the response information of the channel SDK to the operation request, calls the API (Application Programming Interface) to send it to the aggregation server, and the aggregation server acts as a transit to forward the response information to the channel server. The channel server verifies whether the response information is valid, for example, whether the response information is expired, whether the response information has been tampered with, etc., and the user's identity information and authorization status can be determined based on the response information.
[0077] S104: Receive the account information fed back by the channel server after verification, and respond to the operation request according to the account information.
[0078] Account information may be the user's account in the channel platform and the archive storage records of the account in the application, for example, records of props, virtual currencies, and stored plot development nodes owned by the account.
[0079] The way to respond to the operation request is that after the channel server verifies that the response information is valid, it will feedback the current user's account information to the aggregation SDK. The aggregation SDK will log in to the current application based on the account information and read the archive storage record of the account for display to the user.
[0080] Based on the above embodiment, optionally, receiving an operation request from a user includes:
[0081] Receive a user's login operation request;
[0082] Correspondingly, obtaining the response information of the channel SDK, and sending the response information to the aggregation server, so as to send the response information to the channel server through the aggregation server for response verification, includes:
[0083] Get the TOKEN returned by the channel SDK;
[0084] The TOKEN is sent to the aggregation server, which forwards the TOKEN to the channel server for response verification.
[0085] The method of receiving the user's login operation request can be that after the user launches the application, the aggregation SDK generates a login interface and the user clicks the login option, or performs automatic login based on the user's pre-authorized information. After the user's terminal device recognizes the login operation, it generates a login operation request and sends it to the aggregation SDK, which receives it.
[0086] TOKEN can be a string of characters generated by the server, which is used as a token for the client to make requests. After the first login, the server generates a TOKEN and returns it to the client. In the future, the client only needs to bring this TOKEN to request data without having to bring the username and password again.
[0087] The method of obtaining the TOKEN returned by the channel SDK is that after the channel SDK obtains the user's login operation request, it generates a login information filling interface for display, and obtains the unique TOKEN corresponding to the user based on the login information such as the user name and password entered by the user.
[0088] The way to verify the response of TOKEN is to send the TOKEN generated by the channel SDK to the aggregation SDK, which sends it to the aggregation server. The aggregation server then calls the channel API to verify the TOKEN on the channel server. The channel server matches the currently received TOKEN with the TOKEN generated when the user logs in for the first time. If the match is consistent, the response verification is determined to be successful and the user can log in; if the match is inconsistent, the response verification is determined to be failed and the login information entered by the user is incorrect.
[0089] The benefit of this scheme is that the user's login information can be verified through TOKEN, which is conducive to improving the security of application login, reducing the probability of user login information being stolen, and improving the user experience.
[0090] Based on the above embodiment, optionally, receiving the account information fed back by the channel server after verification, and responding to the operation request according to the account information includes:
[0091] After the channel server verifies that the TOKEN is valid, the login account information is returned to the aggregation server;
[0092] Mapping the login account information to a platform account through the aggregation server;
[0093] Obtain the platform account, and determine the login account information corresponding to the platform account through the aggregation SDK;
[0094] The login account information is provided to the application program for performing a login operation.
[0095] The platform account information may be the account information of the application generated for the user by the application developer when the user registers.
[0096] The method of mapping the login account information to the platform account is that when the channel server responds to successful verification, it can determine that the TOKEN is valid, obtain the login account information corresponding to the TOKEN, and send the login account information to the aggregation server. The aggregation server obtains the platform account information corresponding to the current login account information based on the mapping relationship between the pre-stored login account information and the platform account.
[0097] The way to provide the login account information to the application is that the aggregation server sends the platform account to the aggregation SDK, and the aggregation SDK obtains the login account information corresponding to the current platform account information based on the mapping relationship between the pre-stored login account information and the platform account, and then feeds the login account information back to the application, so that the application performs the login operation according to the user's login account information.
[0098] The benefit of this arrangement is that while the channel server can record the user's login data, the aggregation server can collect the user's login data from various channels, which is conducive to statistics and analysis of the user's login data, and further provides data support for subsequent analysis of the application's usage effect.
[0099] For example, taking the game APP (Application) as an example, Figure 2 This is a schematic diagram of the login request response process of the aggregation SDK of the game APP docking channel provided in Example 1 of the present application, such as Figure 2 As shown, when the user starts the game APP, the SDK initialization program is triggered, and the aggregation SDK and channel SDK are adjusted to the initial state. At this time, the user clicks the login or registration option, or the application sends a login or registration operation request to the aggregation SDK through the login interface after detecting the user's authorization information. The aggregation SDK sends the login or registration operation request to the corresponding channel SDK in the specified format. The channel SDK responds to the login or registration operation request and generates the corresponding login or registration interface. The user fills in the user name and password and other information in the interface. The channel SDK obtains or generates the corresponding TOKEN based on the information filled in by the user and sends it to the aggregation SDK. The aggregation SDK sends the TOKEN to the aggregation server, which forwards it to the channel server for verification. The channel server compares the received TOKEN with the recorded TOKEN (if it is a registration request, the information entered by the user and its corresponding TOKEN are recorded). If the comparison is consistent, the verification is successful and the user's account information is returned to the aggregation server. The aggregation server maps the user's account information to the account information registered by the user on the platform and sends it to the aggregation SDK. The aggregation SDK obtains the user's account information corresponding to the platform account information and returns the account information to the game APP for display.
[0100] In an embodiment of the present application, a user's operation request is received; at least one channel SDK that is connected to the aggregation SDK is determined, and the interface corresponding to the operation request is called to send the operation request to the channel SDK so that the channel SDK can generate response information; the response information of the channel SDK is obtained, and the response information is sent to the aggregation server, so that the response information is sent to the channel server through the aggregation server for response verification; the account information fed back by the channel server after verification is passed, and the operation request is responded to according to the account information. Through the above-mentioned method of request response of the aggregation SDK based on the channel of application docking, a unified access standard can be formulated for the access method and technical specifications of each docking channel through the aggregation SDK, which is conducive to simplifying the development and operation process of the application, reducing costs and improving the distribution efficiency of the application.
[0101] Embodiment 2
[0102] Figure 3 This is a flow chart of a request response method based on an aggregate SDK for application-to-channel connection provided in Example 2 of the present application. This solution makes a better improvement on the above-mentioned embodiment, and the specific improvement is as follows: it is characterized in that receiving the user's operation request includes: receiving the user's recharge operation request; correspondingly, after receiving the user's recharge operation request, the method also includes: sending the recharge operation request to the channel SDK; displaying the recharge interface generated by the channel SDK; executing the user's recharge operation through the channel SDK, obtaining the recharge result, and reporting the recharge result to the channel server for verification; after the channel server successfully verifies, obtaining the recharge status from the channel SDK, and returning the recharge status to the application.
[0103] like Figure 3 As shown, specifically including the following:
[0104] S301, receiving a recharge operation request from a user;
[0105] The method of receiving the user's recharge operation request can be that the user clicks the recharge option in the specified interface of the application, and the application records the user's click operation and generates a corresponding recharge operation request, which is sent to the aggregation SDK and received by the aggregation SDK.
[0106] S302, sending the recharge operation request to the channel SDK;
[0107] The method of sending the recharge operation request to the channel SDK is that after the aggregation SDK obtains the user's recharge operation request, it determines the corresponding channel SDK according to the user's authorization information and sends the recharge operation request to the corresponding channel SDK interface.
[0108] S303, displaying the recharge interface generated by the channel SDK;
[0109] The way to display the recharge interface generated by the channel SDK is that after receiving the recharge operation request, the channel SDK generates a recharge interface including recharge information such as the recharge amount and payment method, and displays it to the user to obtain the recharge information content entered by the user.
[0110] S304, executing the user's recharge operation through the channel SDK, obtaining the recharge result, and reporting the recharge result to the channel server for verification;
[0111] The method of executing the user's recharge operation through the channel SDK can be that the user enters the specific amount he wants to recharge through the displayed recharge interface and pays according to the payment channel. The channel SDK extracts the recharge amount entered by the user and uses the specific recharge amount as the recharge result.
[0112] The method of reporting the recharge result to the channel server for verification may be that the channel SDK sends the recharge result to the channel server, and after receiving the recharge result, the channel server identifies the real-time amount of the current user in the channel server account, and compares the received recharge result with the real-time amount. If the real-time amount is consistent with the recharge result, the channel server verification is successful; if the real-time amount is inconsistent with the recharge result, the channel server verification is unsuccessful.
[0113] S305: After the channel server successfully verifies, the recharge status is obtained from the channel SDK, and the recharge status is returned to the application.
[0114] The method of obtaining the recharge status from the channel SDK and returning the recharge status to the application can be that after successful verification on the channel server, the recharge status is set to successful recharge and sent to the channel SDK. The aggregation SDK sends a recharge status acquisition request to the channel SDK, and after the channel SDK responds, the recharge status of successful recharge is sent to the aggregation SDK, and then the aggregation SDK returns a prompt message of successful recharge to the application.
[0115] The benefit of this solution is that when a user performs a recharge operation, the recharge request execution standards of each channel SDK can be unified through the aggregation SDK, and the recharge verification can be performed to the channel SDK, which is conducive to identifying malicious recharge operations of users and avoiding economic losses.
[0116] Based on the above embodiment, optionally, after the channel server successfully verifies, the method further includes:
[0117] Sending a shipment request to the aggregation server through the channel server;
[0118] The aggregation server executes a response to the shipment request.
[0119] The method of sending a shipping request to the aggregation server through the channel server can be that after the channel server verifies that the user's recharge is successful, the virtual props corresponding to the application are determined according to the user's specific recharge amount, the virtual props are written into the shipping request, and the shipping request is sent to the aggregation server.
[0120] The way to respond to the delivery request through the aggregation server may be that after receiving the delivery request, the aggregation server interprets the delivery request and distributes the virtual props recorded in the delivery request to the user's recharge account.
[0121] The advantage of this arrangement is that after verifying that the user has successfully recharged, the corresponding virtual props can be issued to the user's account through the aggregation server, which is conducive to the virtual props reaching the user's account as soon as possible to avoid delays in arrival affecting the user's experience.
[0122] For example, taking the game APP as an example, Figure 4 This is a schematic diagram of the recharge request response process of the aggregation SDK of the game APP docking channel provided in Example 2 of this application, such as Figure 4 As shown, the user clicks on the recharge option in the game APP, and the game APP sends a recharge operation request to the aggregation SDK through the login interface. The aggregation SDK sends the recharge operation request to the corresponding channel SDK in the specified format. The channel SDK responds to the recharge operation request and generates a corresponding recharge interface. The user fills in the recharge amount and other information in the interface and makes a payment. The channel SDK generates the corresponding recharge result based on the information filled in by the user and sends it to the channel server. The channel server verifies whether the recharge result is consistent with the actual amount received. After verifying that the recharge is successful, the recharge status of the successful recharge is returned to the channel SDK, which is sent to the aggregation SDK through the channel SDK and then fed back to the game APP. At the same time, the aggregation server sends the delivery request to the aggregation server, and the aggregation server issues virtual props to the corresponding game account.
[0123] Embodiment 3
[0124] Figure 5 This is a flowchart of a request response method of an aggregation SDK based on an application docking channel provided in Example 3 of the present application. This solution makes a better improvement on the above-mentioned embodiment, and the specific improvement is: it is characterized in that receiving a user's operation request includes: receiving a user's data reporting operation request; after receiving the user's data reporting operation request, the method also includes: obtaining data information corresponding to the data reporting operation request; reporting the data information to the aggregation server through the aggregation SDK, and reporting the data information to the channel SDK by calling the reporting interface through the aggregation SDK, so as to report the data information to the channel server through the channel SDK.
[0125] like Figure 5 As shown, specifically including the following:
[0126] S501, receiving a data reporting operation request from a user;
[0127] The method of receiving the user's data reporting operation request can be to generate a corresponding data reporting operation request when the user selects the application running server, implements the required functions in the application, etc. during the running of the application, so as to report the relevant data involved in the user's operation. For example, when the user upgrades his own level in the application, the user's level upgrade operation is obtained to generate a data reporting operation request and sent to the aggregation SDK.
[0128] S502, obtaining data information corresponding to the data reporting operation request;
[0129] The data information corresponding to the data reporting operation request may be the operation content performed by the user to achieve various functional requirements and the corresponding operation result data.
[0130] The method for obtaining the data information corresponding to the data reporting operation request is to record the corresponding data information when recording the user's operations in the application, write it into the corresponding data reporting operation request, and send it to the aggregation SDK. After receiving the data reporting operation request, the aggregation SDK interprets it and extracts the data information therein.
[0131] S503: reporting the data information to the aggregation server through the aggregation SDK, and reporting the data information to the channel SDK by calling the reporting interface through the aggregation SDK, so as to report the data information to the channel server through the channel SDK.
[0132] The method of reporting the data information to the aggregation server can be that the aggregation SDK directly sends the extracted data information to the aggregation server, and the aggregation server receives it.
[0133] The method of reporting data information to the channel server is that after the aggregation SDK extracts the data information, the corresponding channel SDK reporting interface is obtained according to the user's authorization platform, and the reporting interface is called to send the data information to the channel SDK, which is then forwarded to the channel server.
[0134] For example, taking the game APP as an example, Figure 6 This is a schematic diagram of the data reporting response process of the aggregation SDK of the game APP docking channel provided in Example 3 of the present application, such as Figure 6 As shown, when the user selects a server, creates a character, and performs other operations in the game APP, the game APP calls the data reporting interface and sends the user operation data to the aggregation SDK, which then sends the data to the channel SDK and the aggregation server respectively. The channel SDK reports the acquired user operation data to the channel server, thereby achieving data synchronization between the aggregation server and the channel server.
[0135] The benefit of this solution is that the relevant data of users in the application can be reported to the aggregation server and the channel server, thereby achieving information synchronization between the aggregation server and the channel server, which is beneficial to the statistics and analysis of user data by the application development background and the distribution background.
[0136] Embodiment 4
[0137] Figure 7 This is a flowchart of a request response method for an aggregated SDK based on an application docking channel provided in Example 4 of the present application. This solution makes a better improvement on the above-mentioned embodiment, and the specific improvement is: it is characterized in that the method also includes: receiving a new channel SDK file when there is an update to the channel; replacing the original channel SDK file with the new channel SDK file.
[0138] like Figure 7 As shown, specifically including the following:
[0139] S701, receiving an operation request from a user;
[0140] S702: Determine at least one channel SDK connected to the aggregation SDK, call an interface corresponding to the operation request, and send the operation request to the channel SDK, so that the channel SDK generates response information;
[0141] S703, obtaining response information of the channel SDK, and sending the response information to the aggregation server, so that the aggregation server sends the response information to the channel server for response verification;
[0142] S704, receiving the account information fed back by the channel server after verification, and responding to the operation request according to the account information;
[0143] S705. If there is an update to the channel, receive the new channel SDK file;
[0144] It is understandable that this method can be executed before or after any of the above steps, that is, the response to the user request does not affect the update of the channel SDK, and after the channel SDK is updated, the subsequent user request responses are executed by the updated channel SDK.
[0145] The way to receive the new channel SDK file is that when the docking channel of the application changes, the developer uploads the new channel file through the aggregation SDK, and the aggregation SDK receives the new channel file and sends it to the aggregation server for processing.
[0146] S706. Replace the original channel SDK file with the new channel SDK file.
[0147] The way to replace the original channel SDK file with the new channel SDK file is that after the aggregation server receives the new channel SDK, it traverses all channel SDKs connected to the aggregation server, obtains the original channel SDK file that needs to be modified according to the new channel SDK, deletes the original channel SDK file, and adds the new channel SDK file to the original location. After configuring the updated docking channel, the channel update is completed.
[0148] The advantage of this setting is that when the docking channel needs to be updated, you only need to replace the channel SDK file to complete the update of the docking channel, which is conducive to improving the channel update efficiency and reducing the update workload of developers.
[0149] Embodiment 5
[0150] Figure 8 It is a structural diagram of a request response device of an aggregate SDK based on an application docking channel provided in Example 5 of the present application.
[0151] like Figure 8 As shown, specifically including the following:
[0152] The operation request receiving module 801 is used to receive the operation request of the user;
[0153] A response information generating module 802 is used to determine at least one channel SDK connected to the aggregation SDK, call the interface corresponding to the operation request to send the operation request to the channel SDK, so that the channel SDK generates response information;
[0154] The response information verification module 803 is used to obtain the response information of the channel SDK and send the response information to the aggregation server, so that the response information is sent to the channel server through the aggregation server for response verification;
[0155] The operation request response module 804 is used to receive the account information fed back by the channel server after verification, and respond to the operation request according to the account information.
[0156] In an embodiment of the present application, an operation request receiving module is used to receive an operation request from a user; a response information generating module is used to determine at least one channel SDK that is connected to an aggregation SDK, and to call an interface corresponding to the operation request to send the operation request to the channel SDK so that the channel SDK can generate response information; a response information verification module is used to obtain the response information of the channel SDK, and to send the response information to the aggregation server, so that the response information is sent to the channel server through the aggregation server for response verification; an operation request response module is used to receive the account information fed back by the channel server after verification, and to respond to the operation request according to the account information. Through the above-mentioned device for request response of the aggregation SDK based on the application connection channel, a unified access standard can be formulated for the access method and technical specifications of each connection channel through the aggregation SDK, which is conducive to simplifying the development and operation process of the application, reducing costs and improving the distribution efficiency of the application.
[0157] In the embodiment of the present application, a request response device of an aggregate SDK based on an application docking channel can be a device, or a component, an integrated circuit, or a chip in a terminal. The device can be a mobile electronic device or a non-mobile electronic device. Exemplarily, the mobile electronic device can be a mobile phone, a tablet computer, a laptop computer, a PDA, an in-vehicle electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook or a personal digital assistant (PDA), etc., and the non-mobile electronic device can be a server, a network attached storage (NAS), a personal computer (PC), a television (TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.
[0158] In the embodiment of the present application, a device for responding to a request of an aggregate SDK based on an application docking channel may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.
[0159] The device for request response of an aggregate SDK based on an application docking channel provided in an embodiment of the present application can implement each process implemented in the above-mentioned method embodiments. To avoid repetition, it will not be described here.
[0160] Embodiment 6
[0161] like Fig. 9 As shown, an embodiment of the present application also provides an electronic device 900, including a processor 901, a memory 902, and a program or instruction stored in the memory 902 and executable on the processor 901. When the program or instruction is executed by the processor 901, each process of the device embodiment for responding to a request of an aggregated SDK based on an application docking channel is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be described here.
[0162] It should be noted that the electronic devices in the embodiments of the present application include the mobile electronic devices and non-mobile electronic devices mentioned above.
[0163] Embodiment 7
[0164] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned device embodiment for responding to requests of an aggregated SDK based on an application docking channel are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
[0165] The processor is a processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0166] Embodiment 8
[0167] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned device embodiment for request response of an aggregated SDK based on an application docking channel, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0168] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
[0169] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.
[0170] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM / RAM, a disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application.
[0171] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.
[0172] The above are only preferred embodiments of the present application and the technical principles used. The present application is not limited to the specific embodiments described herein, and various obvious changes, readjustments and substitutions that can be made by those skilled in the art will not deviate from the scope of protection of the present application. Therefore, although the present application is described in more detail through the above embodiments, the present application is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present application, and the scope of the present application is determined by the scope of the claims.
Claims
1. A request response method for an aggregated SDK based on an application docking channel, characterized in that: The method comprises: Receive user operation requests; Determine at least one channel SDK connected to the aggregation SDK, call an interface corresponding to the operation request to send the operation request to the channel SDK, so that the channel SDK generates response information; Obtaining response information of the channel SDK, and sending the response information to the aggregation server, so that the aggregation server sends the response information to the channel server for response verification; The account information fed back by the receiving channel server after verification is passed, and the operation request is responded to according to the account information.
2. The request response method of the aggregate SDK based on the application docking channel according to claim 1 is characterized in that: Receive user operation requests, including: Receive a user's login operation request; Correspondingly, obtaining the response information of the channel SDK, and sending the response information to the aggregation server, so as to send the response information to the channel server through the aggregation server for response verification, includes: Get the TOKEN returned by the channel SDK; The TOKEN is sent to the aggregation server, which forwards the TOKEN to the channel server for response verification.
3. The request response method of the aggregate SDK based on the application docking channel according to claim 2 is characterized in that: Receiving the account information fed back by the channel server after verification, and responding to the operation request according to the account information, including: After the channel server verifies that the TOKEN is valid, the login account information is returned to the aggregation server; Mapping the login account information to a platform account through the aggregation server; Obtain the platform account, and determine the login account information corresponding to the platform account through the aggregation SDK; The login account information is provided to the application program for performing a login operation.
4. The request response method of the aggregate SDK based on the application docking channel according to claim 1 is characterized in that: Receive user operation requests, including: Receive a user's recharge request; Correspondingly, after receiving the recharge operation request from the user, the method further includes: Send the recharge operation request to the channel SDK; Displaying the recharge interface generated by the channel SDK; Execute the user's recharge operation through the channel SDK, obtain the recharge result, and report the recharge result to the channel server for verification; After the channel server successfully verifies, the recharge status is obtained from the channel SDK, and the recharge status is returned to the application.
5. The request response method of the aggregate SDK based on the application docking channel according to claim 4 is characterized in that: After the channel server successfully verifies, the method further includes: Sending a shipment request to the aggregation server through the channel server; The aggregation server executes a response to the shipment request.
6. The request response method of the aggregate SDK based on the application docking channel according to claim 1 is characterized in that: Receive user operation requests, including: Receive data reporting operation requests from users; After receiving the data reporting operation request from the user, the method further includes: Obtaining data information corresponding to the data reporting operation request; The data information is reported to the aggregation server through the aggregation SDK, and the data information is reported to the channel SDK by calling the reporting interface through the aggregation SDK, so as to report the data information to the channel server through the channel SDK.
7. The request response method of the aggregate SDK based on the application docking channel according to claim 1 is characterized in that: The method further comprises: If there is an update to the channel, receive the new channel SDK file; Replace the original channel SDK file with the new channel SDK file.
8. A request response device based on an aggregate SDK of an application docking channel, characterized in that: The device comprises: An operation request receiving module, used for receiving an operation request from a user; A response information generation module, used to determine at least one channel SDK connected to the aggregation SDK, call the interface corresponding to the operation request to send the operation request to the channel SDK, so that the channel SDK generates response information; A response information verification module, used to obtain the response information of the channel SDK, and send the response information to the aggregation server, so as to send the response information to the channel server through the aggregation server for response verification; The operation request response module is used to receive the account information fed back by the channel server after verification, and respond to the operation request according to the account information.
9. An electronic device, characterized in that: It includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor. When the program or instruction is executed by the processor, the steps of a request response method of an aggregated SDK based on an application docking channel as described in any one of claims 1 to 7 are implemented.
10. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the steps of a request response method of an aggregate SDK based on an application docking channel as described in any one of claims 1-7 are implemented.
Citation Information
Cited By
Aggregate game SDK (Software Development Kit) method and system oriented to multiple channels and multiple customer groups
CN121116416A
