Product cross-platform interaction method, device and equipment and storage medium

Abstract

The invention discloses a product cross-platform interaction method, device and equipment and a storage medium, and relates to the technical field of data processing, and the product cross-platform interaction method comprises the following steps: receiving a user request of a platform end; based on a preset security interaction mechanism, creating login information of a product end user according to the user request; and calling a program application interface (API) of the platform end according to a pre-constructed software development kit (SDK) and login information of the product end user, and processing the user request. According to the scheme, cross-platform interaction and docking of the application products can be realized, and the implementation logic of the application products and the implementation logic of the platform are decoupled, so that the interaction difficulty between the application products and the platform is reduced, the application products are supported to be quickly put on the platform in a cross-platform manner, and the cross-platform cost of a product system is reduced.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a product cross-platform interaction method, device, equipment and storage medium. Background Art

[0002] When it comes to launching application products on different platforms, developers usually face the following problems: the basic service designs of each platform, such as users, enterprises, permissions, and processes, are different, and the API interfaces provided by the platform have functional differences; the security interaction standards of each platform are different, and although there is a certain coupling between the function implementation logic of the application product and the implementation logic of the platform function, it requires huge transformation and learning costs to launch application products on different platforms.

[0003] From the above, we can see that how to achieve cross-platform interaction and docking of application products, reduce the difficulty of interaction between application products and platforms, and reduce the cost of cross-platform listing of application products is an urgent problem to be solved.

[0004] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention

[0005] The main purpose of this application is to provide a product cross-platform interaction method, device, equipment and storage medium, aiming to solve the technical problem of how to achieve cross-platform interaction and docking of application products, reduce the difficulty of interaction between application products and platforms, and reduce the cost of cross-platform listing of application products.

[0006] To achieve the above objectives, the present application proposes a product cross-platform interaction method, the method comprising:

[0007] Receive user requests from the platform;

[0008] Based on a preset security interaction mechanism, create login information for the product end user according to the user request;

[0009] According to the pre-built software development kit SDK and the login information of the product-side user, the program application interface API of the platform side is called to process the user request.

[0010] In one embodiment, before the step of calling the platform-side program application interface API according to the pre-built software development kit SDK and the login information of the product-side user to process the user request, the step includes:

[0011] Classify the platform-side API interface according to preset categories to obtain classified platform-side API interfaces;

[0012] Based on the classified platform-side API interface, according to the pre-defined unified product flow and the SDK API interface definition, the platform-side logic implementation process is encapsulated to construct the SDK.

[0013] In one embodiment, the product end is embedded in the platform end in a page manner, and the step of creating login information of the product end user according to the user request based on the preset security interaction mechanism includes:

[0014] Based on a preset cross-window communication mechanism, obtaining login information of the platform user from the platform according to the user request;

[0015] Using the SM2 algorithm, the login information of the platform end user is SM2 decrypted to obtain the decrypted login information of the platform end user;

[0016] The login information of the product end user is created based on the decrypted login information of the platform end user.

[0017] In one embodiment, the step of calling the platform-side program application interface API to process the user request based on the pre-built software development kit SDK and the login information of the product-side user includes:

[0018] Performing permission verification on the login information of the product end user to confirm whether there is a subscription for the API interface between the product end and the platform end;

[0019] Performing a functional check on the API interface of the platform to confirm whether the API interface of the platform is in normal state;

[0020] When the API interface between the product end and the platform end is subscribed and the API interface status of the platform end is normal, according to the user request, the API interface of the SDK is called to convert the interface parameters and prepare the calling environment, and the converted interface parameters and the prepared calling environment are obtained;

[0021] According to the converted interface parameters and the prepared calling environment, the API interface of the platform is remotely called.

[0022] In one embodiment, the method further includes:

[0023] Configuring subscription permissions for the SDK according to an SDK management center, wherein the SDK management center is a microservice application deployed on a cloud platform;

[0024] The status information of the API interface between the product end and the platform end is obtained through the SDK management center to confirm whether the API interface between the product end and the platform end is normal.

[0025] In one embodiment, the method further includes:

[0026] When the SDK management center is in an abnormal state, the SDK is configured with subscription permissions using local configuration by turning on the configuration emergency switch.

[0027] In one embodiment, after the step of calling the platform-side program application interface API according to the pre-built software development kit SDK and the login information of the product-side user to process the user request, the step further includes:

[0028] In the process of calling the API interface of the platform, when the SDK returns a preset error code, the user is prompted to query the request processing result.

[0029] In addition, to achieve the above-mentioned purpose, the present application also proposes a product cross-platform interaction device, the product cross-platform interaction device comprising:

[0030] A receiving module, used to receive user requests from the platform;

[0031] A creation module, used to create login information of a product end user according to the user request based on a preset security interaction mechanism;

[0032] The processing module is used to call the program application interface API of the platform side according to the pre-built software development tool kit SDK and the login information of the user of the product side, and process the user request.

[0033] In addition, to achieve the above-mentioned purpose, the present application also proposes a product cross-platform interaction device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the product cross-platform interaction method described above.

[0034] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by the processor, the steps of the product cross-platform interaction method described above are implemented.

[0035] One or more technical solutions proposed in this application have at least the following technical effects:

[0036] The cross-platform product interaction method, apparatus, device and storage medium proposed in the embodiments of the present application specifically receive a user request from the platform side; based on a preset security interaction mechanism, create login information of the user on the product side according to the user request; based on a pre-built software development kit SDK and the login information of the user on the product side, call the program application interface API on the platform side to process the user request.

[0037] This application receives user requests from the platform, and then creates user login information on the product side according to the user request on the platform side based on the preset security interaction mechanism between the platform and the product; and then remotely calls the platform API interface through the pre-built software development kit SDK and the user login information on the product side, so as to perform corresponding business processing on the user request. The above method can decouple the implementation logic of the application product from the implementation logic of the platform, realize cross-platform interaction and docking of the application product, thereby reducing the difficulty of interaction between the application product and the platform, thereby supporting the rapid cross-platform listing of the application product to reduce the cross-platform cost of the product system. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0039] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0040] Figure 1 A flowchart of the first embodiment of the cross-platform interaction method of the present application product is provided;

[0041] Figure 2 A flowchart of the second embodiment of the cross-platform interaction method of the present application product is provided;

[0042] Figure 3 A flowchart of the third embodiment of the cross-platform interaction method of the present application product is provided;

[0043] Figure 4 A flowchart diagram of the fourth embodiment of the cross-platform interaction method of the product of this application;

[0044] Figure 5 This is an example flow chart of a unified product process involved in an embodiment of the present application;

[0045] Figure 6This is an example flow chart of an interface call between an application product and a platform end involved in an embodiment of the present application;

[0046] Figure 7 This is an interactive relationship diagram of an application product, a platform end, and an SDK management center involved in an embodiment of the present application;

[0047] Figure 8 This is a schematic diagram of the module structure of the cross-platform interaction device of the product of the embodiment of the present application;

[0048] Fig. 9 This is a schematic diagram of the device structure of the hardware operating environment involved in the cross-platform product interaction method in the embodiment of the present application.

[0049] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0050] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0051] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0052] The main solution of the embodiment of the present application is: receiving user requests from the platform side; based on a preset security interaction mechanism, creating login information of the product side user according to the user request; based on the pre-built software development kit SDK and the login information of the product side user, calling the platform side program application interface API to process the user request.

[0053] Technical terms involved in this application:

[0054] SM2 algorithm (Second Generation National Cryptography Administration Commercial Cryptography Algorithm): SM2 algorithm is an asymmetric encryption algorithm based on elliptic curve cryptography (ECC) issued by the China National Cryptography Administration. It is also an elliptic curve public key cryptography algorithm specified in the Chinese national standard (GB / T32918-2016). SM2 algorithm is based on the elliptic curve discrete logarithm problem and provides higher security than traditional public key algorithms such as RSA. It can be widely used in data encryption, decryption, digital signature, identity authentication and network security.

[0055] In the development process of traditional application products being put on different platforms, it is often necessary to design and develop the interface between the application products and the platform API interface. Developers usually face the following problems: the basic service designs of each platform, such as users, enterprises, permissions, and processes, are different, and the API interfaces provided by the platform have functional differences; the security interaction standards of each platform are different, and although there is a certain coupling between the function implementation logic of the application product and the implementation logic of the platform function, it requires huge transformation costs and learning costs to implement the application products on different platforms.

[0056] From the above, we can see that how to achieve cross-platform interaction and docking of application products, reduce the difficulty of interaction between application products and platforms, and reduce the cost of cross-platform listing of application products is an urgent problem to be solved.

[0057] This application provides a solution, which receives user requests from the platform side, and then creates user login information on the product side according to the user request on the platform side based on the preset security interaction mechanism between the platform and the product; and then remotely calls the API interface on the platform side through the pre-built software development kit SDK and the login information of the product side user, so as to perform corresponding business processing on the user request. The above method can decouple the implementation logic of the application product from the implementation logic of the platform, realize cross-platform interaction and docking of the application product, thereby reducing the difficulty of interaction between the application product and the platform, thereby supporting the rapid cross-platform listing of the application product to reduce the cross-platform cost of the product system.

[0058] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or a product cross-platform interaction device that can realize the above functions, etc. The following takes the product cross-platform interaction device as an example to illustrate this embodiment and the following embodiments.

[0059] Based on this, the present application embodiment provides a product cross-platform interaction method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the cross-platform interaction method of the product of this application.

[0060] In this embodiment, the product cross-platform interaction method includes steps S110 to S130:

[0061] Step S110, receiving a user request from the platform;

[0062] Specifically, the product cross-platform interaction device first needs to receive user requests from the platform side and determine the application product requirements included in the user requests from the platform side, so that the subsequent application product can call the platform side API interface through the pre-built SDK according to the user request from the platform side, thereby meeting the application product requirements. In this application, for the convenience of expression, the product side refers to the application product side or application product.

[0063] The platform side usually refers to the backend system that provides a certain service or function, which can be a cloud service or other forms of backend components. The user request on the platform side can be any form of data request, such as login request, data query request, etc.

[0064] Step S120, based on a preset security interaction mechanism, creating login information of the product end user according to the user request;

[0065] It should be understood that the user login mechanism and identity authentication mechanism on the application product and platform side are often not interconnected. Therefore, in order to ensure that the user login status of the application product and the platform side remains consistent, this application proposes a secure interaction mechanism for transmitting the user login information on the platform side to the application product side.

[0066] It should be noted that the preset security interaction mechanism refers to a series of information interaction rules or protocols that are pre-set to ensure the security of user information, such as encrypted transmission, identity authentication, permission control, etc.

[0067] Specifically, the product cross-platform interactive device needs to use a preset security interaction mechanism to perform content analysis on the user request on the aforementioned platform side, and obtain the application product service information requested by the user and the user login information on the platform side based on the request content in the user request, including but not limited to the request path, request parameters, request header information, request service information, etc., and then verify whether the user login information on the platform side is valid or whether the current user has the authority to request the application product service, and then create the user login information on the product side based on the verification result.

[0068] It should be understood that when the verification result is that the user login information on the platform side is invalid or the current user does not have the authority to request the application product service, the login information of the user on the product side cannot be created, and the product cross-platform interactive device should provide the user with similar prompts such as invalid request or no permission to access.

[0069] In a feasible implementation manner, the product end is embedded in the platform end in a page manner, and the step S120 may include steps A01 to A03:

[0070] Step A01, based on a preset cross-window communication mechanism, obtaining the login information of the platform end user from the platform end according to the user request;

[0071] Step A02, using the SM2 algorithm, performing SM2 decryption on the login information of the platform end user to obtain the decrypted login information of the platform end user;

[0072] Step A03, creating the product end user's login information based on the decrypted platform end user's login information.

[0073] In this embodiment, in order to ensure that the application product is successfully listed on the platform side, the service of the application product is embedded in the platform side in the form of a page, that is, the function page of the application product is embedded in the page of the platform side through the iframe method, so that in the process of listing the application product on the platform side, the adaptation work of the application product and the platform front end is saved, thereby reducing the difficulty of listing the application product on different platform sides. Among them, iframe (inline frame) is a tag in HTML (Hyper Text Markup Language) used to embed a web page into another web page. iframe can display content from other pages in one page. In a web page, the iframe tag can be used to nest a web page in another web page to achieve interconnection between web pages.

[0074] Specifically, since the platform page and the product page are two independent pages, the cross-platform interactive device of the product first needs to determine the application product service requested by the user based on the received user request, and then initiate a request to the platform according to the preset cross-window communication mechanism to request the current login information of the platform user. Among them, the preset cross-window communication mechanism refers to the communication mechanism or method pre-set by relevant personnel according to the cross-window communication requirements, such as the storage sharing communication mechanism (LocalStorage or SessionStorage), the postmessage communication method, the broadcast channel (Broadcast Channel API), etc.

[0075] It should be understood that since the communication between the platform-side page and the product-side page adopts a cross-window communication mechanism, in order to improve the security of data interaction during cross-window communication, the present application proposes that during the data interaction process during cross-window communication, the sender needs to encrypt the business data before sending the business data, and the receiver needs to decrypt the received business data.

[0076] In this embodiment, preferably, the preset cross-window communication mechanism is a postmessage communication method. The data encryption communication between cross-window communications adopts the SM2 (second-generation National Cryptography Administration commercial encryption algorithm) asymmetric encryption algorithm. The product cross-platform interactive device uses the SM2 algorithm to perform SM2 decryption processing on the current login information of the platform-side user obtained, thereby obtaining the decrypted login information of the platform-side user. Once it is found that the current login information of the platform-side user cannot be decrypted or the decrypted message body is wrong, it is determined that the request to obtain the current login information of the platform-side user is illegal, and the product end has no authority to obtain the current platform-side user login information.

[0077] Finally, based on the successfully decrypted platform user's login information, create the product user's login information, thereby transferring the platform user's login status to the product side.

[0078] Through the above implementation method, the iframe method is used to implement page embedding of the platform-side page and the product-side page, and the postmessage cross-window communication method and SM2 algorithm are used to achieve the adaptation of the application product and the platform front end, thereby reducing the difficulty of putting the application product on different platform ends.

[0079] Step S130, calling the program application interface API of the platform side according to the pre-built software development kit SDK and the login information of the product side user to process the user request.

[0080] It should be noted that the pre-built software development kit SDK refers to the jar package pre-built by relevant personnel based on the actual product function implementation requirements. The SDK can provide callable API interfaces, which can be used to implement the functions or services of application products. At the same time, the SDK encapsulates the specific implementation process of the functions of these API interfaces, where the function implementation process of the API interface refers to the specific logical interaction with the platform end according to the API interface definition.

[0081] In this embodiment, the product cross-platform interactive device obtains the application product service requested by the user according to the user request, and then uses the pre-built SDK and the login information of the product-side user to first authenticate the product-side user. When the product-side user has the authority to use or request the application product service, the SDK is used to remotely call the platform-side API interface to realize the business processing of the user request.

[0082] This embodiment provides a product cross-platform interaction method, which receives a user request from the platform side; based on a preset security interaction mechanism, creates login information of the product side user according to the user request; based on a pre-built software development kit SDK and the login information of the product side user, calls the platform side program application interface API to process the user request.

[0083] This application receives user requests from the platform, and then creates user login information on the product side according to the user request on the platform side based on the preset security interaction mechanism between the platform and the product; and then remotely calls the platform API interface through the pre-built software development kit SDK and the user login information on the product side, so as to perform corresponding business processing on the user request. The above method can decouple the implementation logic of the application product from the implementation logic of the platform, realize cross-platform interaction and docking of the application product, thereby reducing the difficulty of interaction between the application product and the platform, thereby supporting the rapid cross-platform listing of the application product to reduce the cross-platform cost of the product system.

[0084] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can refer to the above introduction, and will not be repeated later. Figure 2 , before the above step S130, it also includes steps S210 to S220:

[0085] Step S210, classifying the platform-side API interface according to preset categories to obtain the classified platform-side API interface;

[0086] Step S220, based on the classified platform-side API interface, according to the pre-defined unified product flow and the SDK API interface definition, the platform-side logic implementation process is encapsulated to construct the SDK.

[0087] Specifically, this application takes into account that in the process of application products being listed on the platform, the application product side only focuses on the legality of the platform side's users' queries, transactions, authorizations, and other operations on the platform side. Therefore, it considers clarifying the boundary between the application product and the platform side by building an SDK.

[0088] First of all, the basic capabilities provided by the API interface on the platform side can often be abstracted into a three-layer infrastructure, namely the management unit and user layer, the data resource permission layer, and the business process layer. Among them, the management unit and user layer include roles (user groups), virtual users (users), and management units (enterprises or institutions, etc.). The data resource permission layer includes data resource units and user permission units. The process includes basic modules such as approval chain and business process control. In this embodiment, the preset category is the three-layer infrastructure category.

[0089] It can be understood that by classifying the API interfaces of each platform according to different infrastructures, the API interfaces included in different infrastructures can be obtained, so that the underlying functions of the platform can be mapped to the above three-layer architecture.

[0090] Then, a unified process for the interaction between application products and the platform end is built on the above three-layer architecture for different businesses, that is, a unified product process, including but not limited to the user account acquisition process, transaction handling process, transaction approval process, etc. For example Figure 5 Unified product process standards shown.

[0091] Then, according to the classified API interface of the platform end, according to the pre-defined unified product process, the API interface involved in each step of the unified product process can be determined, and then the API interface definition of the SDK pre-built by relevant personnel according to the functional requirements of the actual application product is combined, and the functional implementation process of each SDK API interface is encapsulated, so as to construct the SDK. Among them, the SDK API interface implementation process is the call logic implementation process of multiple platform ends according to the SDK API interface definition, and by mapping and converting the platform API interface field with the SDK API interface field, the SDK API interface definition has the platform end adaptation capability, so that the SDK is adapted to different platform ends, and provides a unified function calling method for the application end. In the process of building the SDK, it is necessary to determine the specific function of the API interface according to the step implementation in the unified product process, and at the same time, the functional implementation of the API interface can be completed by interacting with the API interface involved in each step of the unified product process. In this embodiment, the SDK API interface may include interfaces such as user basic information, user authority, account list, handling, approval, pending approval query, cancellation, and system reconciliation.

[0092] It should be understood that after the SDK is built, the SDK can be packaged into a jar package and an API call service class can be provided to the application product.

[0093] Through the above scheme, this embodiment classifies the API interface on the platform side according to preset categories, and based on the classified API interface on the platform side, encapsulates the logical implementation process on the platform side according to the pre-defined unified product process and the API interface definition of the SDK, thereby constructing an SDK, so that the API interface on the platform side can be remotely called according to the constructed SDK in the future, so as to perform corresponding business processing on the user request. The constructed SDK can decouple the implementation logic of the application product from the implementation logic of the platform, reduce the difficulty of interaction between the application product and the platform, thereby supporting the rapid cross-platform listing of the application product, so as to reduce the cross-platform cost of the product system.

[0094] Based on the first embodiment and / or the second embodiment of the present application, in the third embodiment of the present application, the same or similar contents as those in the first embodiment and / or the second embodiment can refer to the above description, and will not be described in detail later. Figure 3 The step S130 includes steps S310 to S340:

[0095] Step S310, performing permission verification on the login information of the product end user to confirm whether there is a subscription between the API interface between the product end and the platform end;

[0096] Step S320, performing a function check on the API interface of the platform to confirm whether the API interface of the platform is in a normal state;

[0097] Step S330: when the API interface between the product end and the platform end is subscribed and the API interface status of the platform end is normal, according to the user request, the API interface of the SDK is called to convert the interface parameters and prepare the calling environment, and the converted interface parameters and the prepared calling environment are obtained;

[0098] Specifically, first, the product cross-platform interaction device needs to perform permission verification on the product-side user's login information to confirm whether the current product side has a subscription relationship with the platform-side API interface, that is, to confirm whether the application product requested by the current user has the authority to call the platform-side API interface.

[0099] At the same time, the cross-platform interactive device of the product needs to further perform functional verification on the API interface of the platform to be called to confirm whether the API interface of the platform is in normal operation. Then, the request is processed based on the above permission verification results and function verification results.

[0100] When the permission check result shows that there is a subscription between the API interface on the product side and the platform side, and the function check result shows that the API interface on the platform side is in normal status, the product cross-platform interactive device needs to call the API interface on the platform side through the SDK based on the application product service determined by the user request.

[0101] First, determine the SDK API interface and interface parameters that need to be called according to the user's request, and then use the SDK to convert the interface parameters. It is understandable that since the definition, format and naming rules of API interface parameters may be different on each platform, the cross-platform interactive device of the product needs to convert the SDK API interface parameters into API interface parameters that can be recognized by the platform, including field name mapping, data type conversion, enumeration value mapping, and merging of duplicate parameters.

[0102] Due to different authentication standards or regulations on different platforms, SDK needs to pass the authentication of the platform before calling the API interface on the platform. Therefore, the cross-platform interactive device of the product needs to prepare the user signature required for the calling environment according to the platform requirements and rules. Specifically, the user signature is generated through the SDK, so as to prepare the calling environment of the API interface on the platform, and obtain the converted interface parameters and the prepared calling environment. It should be understood that the specific generation process of user signatures on different platform ends has been encapsulated by the SDK, so the cross-platform interactive device of the product only needs to use the built SDK to prepare the calling environment of the API interface to be called.

[0103] It is understandable that when the result of the permission check is that there is no subscription between the API interface on the product side and the platform side, or the result of the function check is that the API interface on the platform side is abnormal, for example, the API interface is disabled, it is necessary to stop processing the user request and provide the user with similar warning prompts such as access denied and access error.

[0104] Step S340: remotely call the API interface of the platform according to the converted interface parameters and the prepared calling environment.

[0105] Finally, the converted interface parameters and the prepared calling environment are used to call the API interface on the platform to implement business processing of user requests.

[0106] It should be understood that when processing the application product functions required by user requests, there may be multiple calls to the platform API interface to implement the corresponding business processing.

[0107] In this embodiment, Figure 6 The figure shows a flow chart of interface calls between an application product and a platform.

[0108] exist Figure 6 In the process, the application side, that is, the application product side, first calls the SDK's API interface through the Java module in the program, and then initiates a remote call to the platform's API interface through permission check, interface definition conversion, and calling environment preparation.

[0109] The present embodiment provides a product cross-platform interaction method, which receives a user request from the platform side; creates login information of the product side user according to the user request based on a preset security interaction mechanism; performs permission verification on the login information of the product side user to confirm whether a subscription exists between the API interface of the product side and the platform side; performs function verification on the API interface of the platform side to confirm whether the API interface of the platform side is in a normal state; when a subscription exists between the API interface of the product side and the platform side, and the API interface of the platform side is in a normal state, calls the API interface of the SDK according to the user request to perform interface parameter conversion and call environment preparation to obtain converted interface parameters and a prepared calling environment; remotely calls the API interface of the platform side according to the converted interface parameters and the prepared calling environment.

[0110] This embodiment uses the above scheme to verify the user's login information on the product side and to verify the functionality of the API interface on the platform side, ensuring that the API interface call on the platform side is legal and valid; at the same time, based on the user's request, the SDK's API interface is called to convert the interface parameters and prepare the calling environment, so as to remotely call the API interface on the platform side, thereby performing corresponding business processing on the user's request. The above method can decouple the implementation logic of the application product from the implementation logic of the platform, realize cross-platform interaction and docking of the application product, thereby reducing the difficulty of interaction between the application product and the platform, thereby supporting the rapid cross-platform listing of the application product to reduce the cross-platform cost of the product system.

[0111] Based on the third embodiment of the present application, in the fourth embodiment of the present application, the same or similar contents as those in the third embodiment can be referred to the above description, and will not be described in detail later. Figure 4 , after the above step S130, further comprising steps S410 to S420:

[0112] Step S410, configuring subscription permissions for the SDK according to the SDK management center, wherein the SDK management center is a microservice application deployed on a cloud platform;

[0113] Specifically, in the actual cross-platform listing process of application products, since there are multiple application products and multiple platform terminals, in order to facilitate the management of the subscription relationship between application products and platform terminals, microservice applications can be deployed on the cloud platform to manage the subscription rights of the SDK. Among them, subscription rights refer to the calling rights of the API interface between application products and platform terminals.

[0114] Reference Figure 7 , Figure 7 It shows the interactive relationship between application products, platform and SDK management center. Figure 7 In the SDK management center, the application instance on the business side can be accessed and configured by the SDK management center. The subscription rights of the SDK in the application instance can be modified by configuring the application instance through the SDK management center.

[0115] The SDK Management Center can manage the subscription rights of the SDK by managing the configuration of multiple application instances. When the SDK Management Center dynamically modifies the configuration information of an application instance, it will immediately affect the subscription rights of the corresponding SDK, thereby affecting the API interface calling rights of the platform included in the application instance.

[0116] Step S420: Obtain the status information of the API interface between the product end and the platform end through the SDK management center to confirm whether the API interface between the product end and the platform end is normal.

[0117] Specifically, during the operation of the application product, the SDK management center can also obtain the operating status information of the product side and the operating status information of the API interface on the platform side, where the operating status information includes survival status, operating time, call count information, etc.

[0118] The SDK Management Center performs data analysis based on the obtained operating status information of the product side and the operating status information of the API interface on the platform side, and refers to previous historical data to confirm whether the current application product and the API interface on the platform side have too few calls, too long running time, abnormal survival status, etc., so as to determine whether the current application product and the API interface on the platform side are providing services normally.

[0119] Furthermore, in order to improve the robustness of the interaction between the application product and the platform, after the above step S420, step B01 is further included:

[0120] Step B01, when the SDK management center is in an abnormal state, the SDK is configured with subscription permissions using local configuration by turning on the configuration emergency switch.

[0121] Specifically, when the SDK Management Center is in an abnormal state, that is, the SDK Management Center is unavailable, it is impossible to manage the SDK subscription permissions for multiple application instances. You can turn on the configuration emergency switch, refer to Figure 7 , use the local configuration of the SDK to configure the SDK subscription permissions so that the SDK call does not depend on the management center.

[0122] This embodiment provides a product cross-platform interaction method, which receives a user request from the platform side; creates login information of the product side user according to the user request based on a preset security interaction mechanism; calls the platform side program application interface API according to a pre-built software development kit SDK and the login information of the product side user to process the user request; configures subscription permissions for the SDK according to an SDK management center, wherein the SDK management center is a microservice application deployed on a cloud platform; obtains status information of the API interface between the product side and the platform side through the SDK management center to confirm whether the API interface between the product side and the platform side is normal.

[0123] Through the above scheme, this embodiment configures the subscription permissions of the SDKs of multiple application instances through the SDK management center, thereby realizing unified management of the subscription relationship between application products and the platform side; at the same time, by obtaining the status information of the API interfaces between the product side and the platform side, it ensures the smooth completion of the interaction between the application product and the platform, and ensures the effectiveness of the interaction between the application product and the platform.

[0124] Based on the first embodiment and / or the second embodiment and / or the third embodiment and / or the fourth embodiment of the present application, in the fifth embodiment of the present application, the same or similar contents as those in the first embodiment, the second embodiment, the third embodiment and / or the fourth embodiment can be referred to the above description, and will not be described in detail later. On this basis, after the above step S140, step S510 is also included:

[0125] Step S510, during the process of calling the API interface of the platform, when the SDK returns a preset error code, the user is prompted to query the request processing result.

[0126] Since the application product interacts with the platform through the SDK, the application product does not directly perceive the connection network status of the platform. In order to solve the transaction consistency problem, the SDK return code specification is pre-defined in the SDK.

[0127] It should be noted that the preset error code refers to the error code pre-set by relevant personnel to solve the transaction consistency problem, and is not specifically limited here.

[0128] However, when the error code returned by the product's cross-platform interactive device based on the user's request to call the SDK contains a specific error code, it means that the SDK cannot perceive the correct return from the platform. This may be a system abnormality on the platform or a network abnormality on the platform. In this case, in order to ensure the consistency of the transaction, the user needs to be prompted to query the request processing result and confirm whether the request processing result is incorrect.

[0129] This embodiment provides a product cross-platform interaction method, which receives a user request from the platform side; creates login information of the product side user according to the user request based on a preset security interaction mechanism; calls the platform side program application interface API according to a pre-built software development tool kit SDK and the login information of the product side user to process the user request; in the process of calling the platform side API interface, when the SDK returns a preset error code, prompts the user to query the request processing result.

[0130] Through the above scheme, this embodiment pre-sets the preset error code in the API interface call process on the platform side, prompting the user to query the request processing results, thereby solving the transaction consistency problem between the interaction between the application product and the platform and improving the accuracy of the interaction between the application product and the platform.

[0131] This application also provides a product cross-platform interaction device, please refer to Figure 8 , the product cross-platform interaction device includes:

[0132] Receiving module 10, used to receive user requests from the platform end;

[0133] A creation module 20, configured to create login information of a product end user according to the user request based on a preset security interaction mechanism;

[0134] The processing module 30 is used to call the program application interface API of the platform side according to the pre-built software development kit SDK and the login information of the user of the product side to process the user request.

[0135] The cross-platform product interaction device provided by the present application adopts the cross-platform product interaction method in the above-mentioned embodiment, which can solve the technical problem of how to realize cross-platform interaction and docking of application products, reduce the difficulty of interaction between application products and platforms, and reduce the cost of cross-platform listing of application products. Compared with the prior art, the beneficial effects of the cross-platform product interaction device provided by the present application are the same as the beneficial effects of the cross-platform product interaction method provided by the above-mentioned embodiment, and other technical features in the cross-platform product interaction device are the same as the features disclosed in the above-mentioned embodiment method, which will not be repeated here.

[0136] The present application provides a product cross-platform interaction device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the product cross-platform interaction method in the above-mentioned implementation example.

[0137] Reference below Fig. 9, which shows a schematic diagram of the structure of a product cross-platform interaction device suitable for implementing the embodiment of the present application. The product cross-platform interaction device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Fig. 9 The product cross-platform interactive device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0138] like Fig. 9 As shown, the product cross-platform interactive device may include a processing device 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the product cross-platform interactive device are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the product cross-platform interaction device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows a product cross-platform interaction device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or have alternatively.

[0139] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0140] The cross-platform product interaction device provided by the present application adopts the cross-platform product interaction method in the above embodiment, which can solve the technical problem of how to realize cross-platform interaction and docking of application products, reduce the difficulty of interaction between application products and platforms, and reduce the cost of cross-platform listing of application products. Compared with the prior art, the beneficial effects of the cross-platform product interaction device provided by the present application are the same as the beneficial effects of the cross-platform product interaction method provided by the above embodiment, and the other technical features in the cross-platform product interaction device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0141] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0142] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0143] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, wherein the computer-readable program instructions are used to execute the product cross-platform interaction method in the above-mentioned embodiment.

[0144] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, 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), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0145] The computer-readable storage medium may be included in the product cross-platform interaction device; or may exist independently without being assembled into the product cross-platform interaction device.

[0146] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the product cross-platform interaction device, the product cross-platform interaction device: receives the user request on the platform side; creates the login information of the product side user according to the user request based on the preset security interaction mechanism; calls the program application interface API of the platform side according to the pre-built software development kit SDK and the login information of the product side user to process the user request.

[0147] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0148] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the 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 square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square 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 square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / 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.

[0149] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0150] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned cross-platform product interaction method, and can solve the technical problems of how to achieve cross-platform interaction and docking of application products, reduce the difficulty of interaction between application products and platforms, and reduce the cost of cross-platform listing of application products. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the cross-platform product interaction method provided by the above-mentioned embodiment, and will not be repeated here.

[0151] An embodiment of the present application provides a computer program product, including a computer program, which implements the steps of the above-mentioned product cross-platform interaction method when executed by a processor.

[0152] The computer program product provided by the present application can solve the technical problem of how to achieve cross-platform interaction and docking of application products, reduce the difficulty of interaction between application products and platforms, and reduce the cost of cross-platform listing of application products. Compared with the prior art, the beneficial effects of the computer program product provided by the embodiment of the present application are the same as the beneficial effects of the product cross-platform interaction method provided by the above embodiment, and will not be repeated here.

[0153] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent processing scope of the present application.

Claims

1. A product cross-platform interaction method, characterized in that: The method comprises: Receive user requests from the platform; Based on a preset security interaction mechanism, create login information for the product end user according to the user request; According to the pre-built software development kit SDK and the login information of the product-side user, the program application interface API of the platform side is called to process the user request.

2. The method according to claim 1, characterized in that Before the step of calling the platform-side program application interface API according to the pre-built software development kit SDK and the login information of the product-side user to process the user request, the step includes: Classify the platform-side API interface according to preset categories to obtain classified platform-side API interfaces; Based on the classified platform-side API interface, according to the pre-defined unified product flow and the SDK API interface definition, the platform-side logic implementation process is encapsulated to construct the SDK.

3. The method according to claim 1, characterized in that The product end is embedded in the platform end in a page manner, and the step of creating login information of the product end user according to the user request based on the preset security interaction mechanism includes: Based on a preset cross-window communication mechanism, obtaining login information of the platform user from the platform according to the user request; Using the SM2 algorithm, the login information of the platform end user is SM2 decrypted to obtain the decrypted login information of the platform end user; The login information of the product end user is created based on the decrypted login information of the platform end user.

4. The method according to claim 3, characterized in that The step of calling the platform-side program application interface API according to the pre-built software development kit SDK and the login information of the product-side user to process the user request includes: Performing permission verification on the login information of the product user to confirm whether there is a subscription for the API interface between the product and the platform; Performing a functional check on the API interface of the platform to confirm whether the API interface of the platform is in a normal state; When the API interface between the product end and the platform end is subscribed and the API interface status of the platform end is normal, according to the user request, the API interface of the SDK is called to convert the interface parameters and prepare the calling environment, and the converted interface parameters and the prepared calling environment are obtained; According to the converted interface parameters and the prepared calling environment, the API interface of the platform is remotely called.

5. The method according to claim 2, characterized in that The method further comprises: Configuring subscription permissions for the SDK according to an SDK management center, wherein the SDK management center is a microservice application deployed on a cloud platform; The status information of the API interface between the product end and the platform end is obtained through the SDK management center to confirm whether the API interface between the product end and the platform end is normal.

6. The method according to claim 5, characterized in that The method further comprises: When the SDK management center is in an abnormal state, the SDK is configured with subscription permissions using local configuration by turning on the configuration emergency switch.

7. The method according to any one of claims 2 to 6, characterized in that After the step of calling the platform-side program application interface API according to the pre-built software development kit SDK and the login information of the product-side user to process the user request, the method further includes: In the process of calling the API interface of the platform, when the SDK returns a preset error code, the user is prompted to query the request processing result.

8. A product cross-platform interaction device, characterized in that: The product cross-platform interaction device includes: A receiving module, used to receive user requests from the platform; A creation module, used to create login information of a product end user according to the user request based on a preset security interaction mechanism; The processing module is used to call the program application interface API of the platform side according to the pre-built software development tool kit SDK and the login information of the user of the product side, and process the user request.

9. A product cross-platform interactive device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the product cross-platform interaction method according to any one of claims 1 to 7.

10. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the product cross-platform interaction method according to any one of claims 1 to 7 are implemented.

Images