Application plug-in cross-domain sharing method and device, electronic equipment and medium

Abstract

The invention discloses an application plug-in cross-domain sharing method and device, electronic equipment and a medium, and the method comprises the steps: carrying out the token verification and login state verification of application splitting request information, and forwarding the application splitting request information passing the verification to an application plug-in back-end service; performing application splitting on a corresponding first application according to the application splitting request information to obtain a first application plug-in, and outputting the first application plug-in to an application plug-in library; carrying out identity verification and authority verification on the platform calling request information, and forwarding the verified platform calling request information to an application plug-in back-end service; and obtaining a target application plug-in in an application plug-in library according to the platform calling request information, determining an application use area of a corresponding target application according to the target application plug-in, and further sharing the application use area with the second user. According to the method, cross-domain sharing of applications among the platforms is realized, the development efficiency of the applications and the resource utilization rate of the platforms are improved, and the method can be widely applied to the field of software development.

Description

Technical Field

[0001] The present invention relates to the technical field of software development, and in particular to an application plug-in cross-domain sharing method, device, electronic device and medium. Background Art

[0002] With the rapid development of information technology, various application systems have been widely used in all walks of life. However, traditional application systems often have the following problems:

[0003] 1) Duplicate platform construction and low resource utilization: Multiple provinces, cities, integration companies, etc. independently build the same platform, and the platform is deployed in a decentralized manner or by project;

[0004] 2) Lack of unified construction standards, inconvenient capability reuse: The deployment methods, technical architectures, data models, and authentication systems of various platforms vary greatly, and the threshold for interoperability of capabilities and applications between platforms is high;

[0005] 3) It is difficult to leverage scale advantages, and core capabilities and ecological traction are insufficient: Due to factors such as scale and cost, it is difficult for provincial and municipal platforms to fully integrate the capabilities of multiple platforms within the telecom industry, and it is difficult to attract partners to create a rich ecosystem. The core competitiveness is insufficient, and the replacement threshold is not high;

[0006] 4) Difficulty in external export: Developed applications cannot be quickly and easily decoupled and exported for use by external partners.

[0007] The above problems need to be solved urgently. Summary of the invention

[0008] The purpose of the present invention is to solve one of the technical problems existing in the prior art to at least a certain extent.

[0009] To this end, an object of an embodiment of the present invention is to provide an application plug-in cross-domain sharing method, which realizes cross-domain sharing of applications between platforms and improves application development efficiency and platform resource utilization.

[0010] Another object of an embodiment of the present invention is to provide an application plug-in cross-domain sharing device.

[0011] In order to achieve the above technical objectives, the technical solutions adopted by the embodiments of the present invention include:

[0012] On the one hand, an embodiment of the present invention provides an application plug-in cross-domain sharing method, comprising the following steps:

[0013] Obtain application splitting request information of the first user, perform token verification and login state verification on the application splitting request information, and forward the application splitting request information that passes the verification to the application plug-in backend service;

[0014] Performing application splitting on the corresponding first application according to the application splitting request information through the application plug-in backend service to obtain a first application plug-in, and outputting the first application plug-in to an application plug-in library;

[0015] Obtaining the platform call request information of the second user, performing identity verification and authority verification on the platform call request information, and forwarding the verified platform call request information to the application plug-in backend service;

[0016] The target application plug-in is obtained from the application plug-in library according to the platform call request information through the application plug-in backend service, and the application use area of ​​the corresponding target application is determined according to the target application plug-in, and then the application use area is shared with the second user.

[0017] Furthermore, in one embodiment of the present invention, token verification is performed on the application split request information through the following steps:

[0018] Extracting a first token from the application splitting request information, and verifying whether the first token has been used;

[0019] When the first token has not been used, the first token is parsed to obtain the encrypted original text, the first signature, and the token generation time, and whether the first token is within the validity period is verified according to the token generation time;

[0020] When the first token is within the validity period, the user unique identifier of the first user is obtained through the login state identifier of the first user, the hash key value of the first user is obtained according to the user unique identifier, and the encrypted original text is signed according to the hash key value to obtain a second signature, and then it is determined whether the second signature is the same as the first signature;

[0021] When the second signature is the same as the first signature, it is determined that the token verification is successful, and the login state identifier is added to the request header of the application split request information.

[0022] Further, in one embodiment of the present invention, the application splitting request information that passes the token verification is subjected to a login state verification through the following steps:

[0023] Extracting the login status identifier from the application splitting request information verified by the token, and querying the server whether the login status of the first user is valid according to the login status identifier;

[0024] When the login status of the first user is valid, the first user information of the first user is queried from the server through the login status identifier, and the first user information is added to the request header of the application splitting request information.

[0025] Further, in an embodiment of the present invention, the step of performing application splitting on the corresponding first application according to the application splitting request information to obtain a first application plug-in, and outputting the first application plug-in to an application plug-in library specifically includes:

[0026] Extracting an application identifier from the application splitting request information, and determining the first application to be split according to the application identifier;

[0027] Splitting the first application according to a preset plug-in decoupling rule to obtain a plurality of first application plug-ins;

[0028] The first application plug-in is output to a preset application plug-in transfer page, and the first application plug-in is forwarded to the application plug-in library through the application plug-in transfer page.

[0029] Furthermore, in one embodiment of the present invention, the platform call request information is generated by the following steps:

[0030] Sending the application plug-in identifier and the second user information of the second user to the application plug-in open platform through the third-party platform, and applying for interface authority and application plug-in authority from the application plug-in open platform;

[0031] Verifying, by the application plug-in open platform, whether the second user has interface authority according to the second user information, and verifying, by the second user information and the application plug-in identifier, whether the second user has application plug-in authority;

[0032] When the second user has the interface permission and the application plug-in permission, a one-time user identifier is generated, and the one-time user identifier is returned to the third-party platform;

[0033] The platform calling request information is generated by the third-party platform according to the application plug-in identifier, the user one-time identifier and a preset application plug-in calling rule.

[0034] Further, in one embodiment of the present invention, the identity verification and authority verification of the platform call request information specifically includes:

[0035] Extracting the application plug-in identifier and the user one-time identifier from the platform call request information, verifying whether the user one-time identifier matches the application plug-in identifier, and verifying whether the second user has authorized the application plug-in to access;

[0036] When the user's one-time identification matches the application plug-in identification, and the second user has authorized the application plug-in to access, the application plug-in real address of the corresponding target application plug-in is determined according to the application plug-in identification, and a business access token is generated according to the application plug-in real address, and then the page is jumped to the application plug-in front-end page, and the business access token is sent to the application plug-in front-end service;

[0037] The application plug-in front-end service requests the application plug-in back-end service for the authorized cell list of the second user, and verifies whether the second user has the authority to call the target application plug-in based on the authorized cell list and the service access token.

[0038] Furthermore, in one embodiment of the present invention, the application plug-in cross-domain sharing method further includes the following steps:

[0039] When the second user does not authorize the application plug-in to access, jump to the authorization page and prompt the second user to authorize the application plug-in to access;

[0040] When the second user completes the application plug-in access authorization, obtain the user authorization number, and verify whether the user authorization number is consistent with the second user information;

[0041] When the user authorization number is consistent with the second user information, the authorization record is saved within a preset time limit.

[0042] On the other hand, an embodiment of the present invention provides an application plug-in cross-domain sharing device, including:

[0043] A first verification module is used to obtain application splitting request information of the first user, perform token verification and login state verification on the application splitting request information, and forward the application splitting request information that passes the verification to the application plug-in backend service;

[0044] An application splitting module, configured to perform application splitting on the corresponding first application according to the application splitting request information through the application plug-in backend service, obtain a first application plug-in, and output the first application plug-in to an application plug-in library;

[0045] A second verification module is used to obtain the platform call request information of the second user, perform identity verification and authority verification on the platform call request information, and forward the verified platform call request information to the application plug-in backend service;

[0046] The plug-in calling module is used to obtain the target application plug-in in the application plug-in library according to the platform calling request information through the application plug-in backend service, and determine the application usage area of ​​the corresponding target application according to the target application plug-in, and then share the application usage area with the second user.

[0047] On the other hand, an embodiment of the present invention provides an electronic device, comprising a memory, a processor, a program stored in the memory and executable on the processor, and a data bus for realizing connection and communication between the processor and the memory, wherein the program, when executed by the processor, realizes the application plug-in cross-domain sharing method as described above.

[0048] On the other hand, an embodiment of the present invention also provides a storage medium, which is a computer-readable storage medium used for computer-readable storage, and the storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the application plug-in cross-domain sharing method as described above.

[0049] The advantages and beneficial effects of the present invention will be partly given in the following description, partly become apparent from the following description, or be understood through the practice of the present invention:

[0050] The embodiment of the present invention obtains the application splitting request information of the first user, performs token verification and login status verification on the application splitting request information, forwards the verified application splitting request information to the application plug-in backend service, performs application splitting on the corresponding first application according to the application splitting request information through the application plug-in backend service, obtains the first application plug-in, and outputs the first application plug-in to the application plug-in library, obtains the platform call request information of the second user, performs identity verification and permission verification on the platform call request information, forwards the verified platform call request information to the application plug-in backend service, obtains the target application plug-in in the application plug-in library according to the platform call request information through the application plug-in backend service, and determines the application use area of ​​the corresponding target application according to the target application plug-in, and then shares the application use area with the second user. The embodiment of the present invention realizes cross-domain sharing of applications between platforms through plug-in splitting, dynamic output and cross-domain interconnection of applications, and improves the development efficiency of applications and the resource utilization rate of the platform. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] In order to more clearly illustrate the technical solution in the embodiments of the present invention, the following introduction is made to the drawings required for use in the embodiments of the present invention. It should be understood that the drawings introduced below are only for the convenience of clearly describing some embodiments of the technical solution of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0052] Figure 1 A flowchart of a method for cross-domain sharing of application plug-ins provided in an embodiment of the present invention;

[0053] Figure 2 A step flow chart of step S101 provided in an embodiment of the present invention;

[0054] Figure 3 Another step flow chart of step S101 provided in an embodiment of the present invention;

[0055] Figure 4 A step flow chart of step S102 provided in an embodiment of the present invention;

[0056] Figure 5 A step flow chart of step S103 provided in an embodiment of the present invention;

[0057] Figure 6 Another step flow chart of step S103 provided in an embodiment of the present invention;

[0058] Figure 7 Another step flow chart of step S103 provided in an embodiment of the present invention;

[0059] Figure 8 A schematic diagram of the structure of an application plug-in cross-domain sharing device provided in an embodiment of the present invention;

[0060] Fig. 9 A schematic diagram of the hardware structure of an electronic device provided by an embodiment of the present invention;

[0061] Fig.10 A schematic diagram of the structure of a storage medium provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0062] Embodiments of the present invention are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application, and cannot be understood as limitations on the present application. It should be noted that, although the functional module division is performed in the system schematic diagram and the logical order is shown in the flow chart, in some cases, the steps shown or described may be performed in a different order from the module division in the system schematic diagram or the flow chart. For the step numbers in the following embodiments, they are only set for the convenience of explanation, and the order between the steps is not limited in any way. The execution order of each step in the embodiment can be adaptively adjusted according to the understanding of those skilled in the art.

[0063] In the description of the present invention, the meaning of "a plurality" is two or more. If there is a description of the first or the second, it is only for the purpose of distinguishing the technical features, and it cannot be understood as indicating or implying the relative importance or implicitly indicating the number of the indicated technical features or implicitly indicating the order of the indicated technical features. In addition, unless otherwise defined, all technical and scientific terms used in this document have the same meaning as those commonly understood by technicians in the technical field of this application. The terms used in this document are only for the purpose of describing the embodiments of the present application and are not intended to limit the present application.

[0064] The application plug-in cross-domain sharing method provided in the embodiment of the present application can be applied to the terminal, can also be applied to the server side, and can also be software running in the terminal or the server side. In some embodiments, the terminal can be a smart phone, a tablet computer, a laptop computer, a desktop computer, a set-top box, etc.; the server side can be configured as an independent physical server, or a server cluster or distributed system composed of multiple physical servers, and can also be configured as a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms; the software can be an application that implements the application plug-in cross-domain sharing method, etc., but is not limited to the above forms.

[0065] The present application can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronic devices, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc. The present application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application can also be practiced in distributed computing environments, in which tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.

[0066] It should be noted that in each specific implementation of the present application, when it comes to the need to perform relevant processing based on data related to user identity or characteristics such as user information, user behavior data, user historical data, and user location information, the user's permission or consent will be obtained first, and the collection, use, and processing of these data will comply with the relevant laws, regulations, and standards of the relevant countries and regions. In addition, when the embodiment of the present application needs to obtain the user's sensitive personal information, the user's separate permission or consent will be obtained through a pop-up window or by jumping to a confirmation page. After clearly obtaining the user's separate permission or consent, the necessary user-related data for the normal operation of the embodiment of the present application will be obtained.

[0067] The main purpose of the present invention is to drive the interconnection between various platforms through custom rules, realize dynamic output and cross-domain sharing of applications; adopt the plug-in splitting, dynamic output and cross-domain interconnection technology of the application system to achieve the effect of splitting the plug-in output of the full-end application at one time, which can be accessed in any scenario of provincial and municipal companies, and the provincial and municipal secondary platforms can be quickly built under the condition of ensuring user data security through the cross-domain interconnection technology of custom rules; through the plug-in design, dynamic output and cross-domain interconnection technology of the application system, on this basis, in order to support the rapid development of local applications by provincial and municipal companies, the full-end application of the intensive platform is split once to realize plug-in output for provincial and municipal companies to use or secondary development, and the custom rule engine building block combination intensive-local applications are used for integrated delivery, which reduces the development and operation costs and improves the project delivery efficiency.

[0068] like Figure 1 FIG. 1 is a flow chart showing a method for cross-domain sharing of application plug-ins provided in an embodiment of the present invention. Figure 1 The embodiment of the present invention provides an application plug-in cross-domain sharing method, which specifically includes the following steps:

[0069] S101, obtaining application splitting request information of a first user, performing token verification and login state verification on the application splitting request information, and forwarding the verified application splitting request information to an application plug-in backend service;

[0070] S102: performing application splitting on the corresponding first application according to the application splitting request information through the application plug-in backend service to obtain a first application plug-in, and outputting the first application plug-in to the application plug-in library;

[0071] S103, obtaining the platform call request information of the second user, performing identity verification and authority verification on the platform call request information, and forwarding the verified platform call request information to the application plug-in backend service;

[0072] S104: Obtain a target application plug-in from an application plug-in library according to the platform call request information through the application plug-in backend service, determine an application usage area of ​​the corresponding target application according to the target application plug-in, and then share the application usage area with the second user.

[0073] Specifically, the embodiment of the present invention has complete functions such as application plug-in on-shelf, subscription activation, call access, statistical billing, etc. If you need to export the intensive platform application plug-in, you only need to split the application into plug-ins, put it into the plug-in library for dynamic output, and provincial and municipal company developers can apply for use in the capability opening portal. The cross-domain interconnection technology based on custom rules can be used to combine building blocks and integrate local applications for integrated delivery. It can be applied to any platform. During the call process, after the platform request enters the plug-in library, it will call the application plug-in through the custom rule engine according to user information and request information.

[0074] Each end adopts unified encryption technology and secondary identity authentication token generation and verification methods through gateway transformation, so that the front-end and back-end verification methods of the application are kept consistent, providing an authentication basis for the application plug-in split. The front end formulates an application plug-in transfer page, and all external application plug-ins are forwarded to the transfer page through internal system processing. In the transfer page, the user login information is obtained through cookieid and written into the local storage to generate a one-time request token. The custom rule engine splices different link parameters for logical processing to reach the internal application, achieving the effect of application system application plug-in output.

[0075] It can be appreciated that the embodiments of the present invention achieve cross-domain sharing of applications between platforms through plug-in splitting, dynamic output, and cross-domain interconnection of applications, thereby improving application development efficiency and platform resource utilization.

[0076] like Figure 2 FIG. 1 is a flowchart of step S101 provided in an embodiment of the present invention, referring to FIG. Figure 2 As an optional implementation, token verification is performed on the application split request information through the following steps:

[0077] S1011, extracting a first token from the application splitting request information, and verifying whether the first token has been used;

[0078] S1012: When the first token has not been used, the first token is parsed to obtain the encrypted original text, the first signature, and the token generation time, and whether the first token is within the validity period is verified according to the token generation time;

[0079] S1013. When the first token is within the validity period, obtain the user unique identifier of the first user through the login state identifier of the first user, obtain the hash key value of the first user according to the user unique identifier, and sign the encrypted original text according to the hash key value to obtain a second signature, and then determine whether the second signature is the same as the first signature;

[0080] S1014: When the second signature is the same as the first signature, it is determined that the token verification is successful, and the login state identifier is added to the request header of the application split request information.

[0081] The embodiment of the present invention adopts unified encryption technology and secondary identity authentication token generation and verification, adopts Kong gateway plug-in pluggable technology, and performs multiple verifications by plug-in superposition configuration. The secondary identity authentication ensures that the request obtained by the server is initiated by a legitimate user logged in by the client. Among them, the first time is to verify that the token is generated for the logged-in user to ensure the validity of the token. The second time is the user's login state verification and user information acquisition to ensure that the user is still logged in and is a legitimate user.

[0082] Specifically, the kong gateway intercepts the request and obtains the token from the request header. It first verifies whether the token has been used (determines whether it is in the discarded pool. After the token is used, it will be placed in the discarded pool, and the validity period is the maximum validity period of the token) to prevent replay; the verification time is within the validity period to ensure that each token is recently generated to prevent token pool attacks; the user's unique identifier is obtained through the user login state, the user's new and old valid hash key values ​​hash Key are queried, the signature is polled and verified, and it is clear that the token is generated by the logged-in user to prevent data unauthorized access.

[0083] like Figure 3 FIG. 1 is another step flow chart of step S101 provided in an embodiment of the present invention, referring to FIG. Figure 3 As an optional implementation, the application split request information verified by the token is verified by performing a login state verification through the following steps:

[0084] S1015, extracting a login status identifier from the application splitting request information that passes the token verification, and querying the server whether the login status of the first user is valid according to the login status identifier;

[0085] S1016: When the login state of the first user is valid, query the server to obtain the first user information of the first user through the login state identifier, and add the first user information to the request header of the application splitting request information.

[0086] Specifically, the login status identifier accessToken and appkey are obtained from the request header, and the server is checked to see if the user's login status is valid to ensure that the request is legally initiated by the logged-in user. If it is invalid, the server will directly jump to the login page. If it is valid, the user's detailed information is obtained through the login status, including the logged-in user's id, community id, terminal type, WeChat appid, WeChat openid, mobile phone number and other information required for the back-end request. This information is added to the request header and forwarded to the specified back-end service. The back-end service can operate the logged-in user's business behavior based on the above information. In this way, the back-end service does not need to trust any user information parameters passed in by the front-end, and does not need to pay attention to the user's login status and interface permission security issues, thereby ensuring the security of third-party user data.

[0087] like Figure 4 FIG. 1 is a flow chart of step S102 provided in an embodiment of the present invention, referring to FIG. Figure 4 As an optional implementation, the corresponding first application is split according to the application splitting request information to obtain a first application plug-in, and the first application plug-in is output to the application plug-in library, which specifically includes:

[0088] S1021. Extract an application identifier from the application splitting request information, and determine a first application to be split according to the application identifier;

[0089] S1022. Split the first application according to a preset plug-in decoupling rule to obtain a plurality of first application plug-ins.

[0090] S1023: Output the first application plug-in to a preset application plug-in transfer page, and forward the first application plug-in to an application plug-in library through the application plug-in transfer page.

[0091] like Figure 5 FIG. 1 is a flow chart of step S103 provided in an embodiment of the present invention, referring to FIG. Figure 5 As an optional implementation, the platform call request information is generated by the following steps:

[0092] S1030, sending the application plug-in identifier and the second user information of the second user to the application plug-in open platform through the third-party platform, and applying for interface authority and application plug-in authority from the application plug-in open platform;

[0093] S1031. Verify, through the application plug-in open platform, whether the second user has the interface authority according to the second user information, and verify, according to the second user information and the application plug-in identifier, whether the second user has the application plug-in authority;

[0094] S1032: When the second user has the interface permission and the application plug-in permission, a one-time user identifier is generated, and the one-time user identifier is returned to the third-party platform;

[0095] S1033: Generate platform call request information according to the application plug-in identifier, the user's one-time identifier, and a preset application plug-in call rule through a third-party platform.

[0096] like Figure 6 FIG. 1 is another step flow chart of step S103 provided in an embodiment of the present invention, referring to FIG. Figure 6 As an optional implementation, identity verification and permission verification are performed on the platform call request information, which specifically includes:

[0097] S1034, extracting the application plug-in identifier and the user one-time identifier from the platform call request information, verifying whether the user one-time identifier matches the application plug-in identifier, and verifying whether the second user has authorized the application plug-in to access;

[0098] S1035. When the user's one-time identifier matches the application plug-in identifier, and the second user has authorized the application plug-in to access, the application plug-in real address of the corresponding target application plug-in is determined according to the application plug-in identifier, and a business access token is generated according to the application plug-in real address, and then the page is jumped to the application plug-in front-end page, and the business access token is sent to the application plug-in front-end service;

[0099] S1036: Request the authorized cell list of the second user from the application plug-in backend service through the application plug-in frontend service, and verify whether the second user has the authority to call the target application plug-in according to the authorized cell list and the service access token.

[0100] like Figure 7 FIG. 1 is another step flow chart of step S103 provided in an embodiment of the present invention, referring to FIG. Figure 7 As an optional implementation, the plug-in cross-domain sharing method further includes the following steps:

[0101] S1037: When the second user does not authorize the application plug-in to access, jump to the authorization page and prompt the second user to authorize the application plug-in to access;

[0102] S1038. When the second user completes the application plug-in access authorization, obtain the user authorization number, and verify whether the user authorization number is consistent with the second user information;

[0103] S1039: When the user authorization number is consistent with the second user information, the authorization record is saved within a preset time limit.

[0104] The application plug-in capabilities currently provided are all open based on single sign-on with operator accounts. Therefore, the access party is required to use the operator account to log in to the access platform if they want to use the application plug-in capabilities. However, when it is actually opened, it is found that many usage scenarios of the access party do not have access to the operator account to log in. For example, WeChat mini-programs, WeChat public accounts and other scenarios use WeChat's own authentication system. The cost of modifying the operator account login is high, resulting in the inability to use the provided application plug-in capabilities.

[0105] In order to improve the diversification and usability of application plug-in usage scenarios, the embodiment of the present invention allows the third-party platform to jump to the application plug-in according to the custom rule single sign-on specification, which is used in the scenario where the third-party platform uses the application plug-in without development power or access to the operator account login. The custom rule cross-domain interconnection technology of the embodiment of the present invention has 6 layers of protection:

[0106] 1) Perform application plug-in permission control to manage B-side platform access and data statistics.

[0107] 2) The system assigns an application ID to a specific third-party platform, which requires token verification when used, and assembles the application function dynamically output through the ID custom rule engine.

[0108] 3) Developers can use the custom single sign-on capability only after applying for interface permissions. Use mobile phone number, community ID, application ID, channel and other information to generate a one-time user identification code tokenCode (valid once every 2 minutes), which can only be used to jump to the corresponding application plug-in. The code is dedicated to prevent data unauthorized access.

[0109] 4) When the user jumps to the application plug-in with a single click, it verifies whether the user is authorized. If not authorized, it jumps to the authorization page for verification code authorization. The authorization period is 30 days to ensure that the user voluntarily authorizes the application to use the information to avoid information leakage. The authorization information is the mobile phone number + application plug-in binding, which makes the user aware and prevents third-party platforms from using any mobile phone number to jump.

[0110] 5) Allocate accessible cell ranges based on project dimensions. After jumping into the application plug-in, only authorized cell information can be viewed based on project identification, which is specific and limited to prevent data unauthorized access.

[0111] 6) If the third-party platform does not pass in the cell ID when generating the user identification, it will jump to the assigned cell selection page after the user authorizes the user to select the cell before entering the application and locating the application usage area.

[0112] The method steps of the embodiment of the present invention are described above. It can be recognized that the embodiment of the present invention realizes cross-domain sharing of applications between platforms through plug-in splitting, dynamic output and cross-domain interconnection of applications, improves application development efficiency and platform resource utilization, and can quickly output the application plug-in of the intensive platform to provincial and municipal companies for use or secondary development, so that provincial and municipal teams can focus on local application development, and combine intensive-local applications in a building block-like manner for integrated delivery, thereby reducing development and operation costs. Improve project delivery efficiency. Taking a project of an operator in Shanghai, Anhui and other countries as an example, the call to intensive capability accounts for 50%-70% of the project, which is 15-24% higher than the gross profit margin of the original traditional ICT project model, and the delivery cycle is significantly shortened.

[0113] like Figure 8 FIG. 1 is a schematic diagram of a cross-domain sharing device based on application plug-in provided in an embodiment of the present invention. Figure 8 The embodiment of the present invention provides an application plug-in cross-domain sharing device, including:

[0114] A first verification module is used to obtain application splitting request information of the first user, perform token verification and login state verification on the application splitting request information, and forward the application splitting request information that passes the verification to the application plug-in backend service;

[0115] An application splitting module, used to perform application splitting on the corresponding first application according to the application splitting request information through the application plug-in backend service, obtain the first application plug-in, and output the first application plug-in to the application plug-in library;

[0116] A second verification module is used to obtain the platform call request information of the second user, perform identity verification and authority verification on the platform call request information, and forward the verified platform call request information to the application plug-in backend service;

[0117] The plug-in calling module is used to obtain the target application plug-in in the application plug-in library according to the platform calling request information through the application plug-in backend service, and determine the application use area of ​​the corresponding target application according to the target application plug-in, and then share the application use area with the second user.

[0118] The contents of the above method embodiments are all applicable to the present device embodiments. The functions specifically implemented by the present device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0119] The embodiment of the present invention further provides an electronic device, the electronic device comprising: a memory, a processor, a program stored in the memory and executable on the processor, and a data bus for realizing connection and communication between the processor and the memory, wherein the program is executed by the processor to realize the above-mentioned application plug-in cross-domain sharing method. The electronic device may be any intelligent terminal including a tablet computer, a vehicle-mounted computer, etc.

[0120] like Fig. 9 FIG. 1 is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present invention, referring to FIG. Fig. 9 , an embodiment of the present invention provides an electronic device, including:

[0121] The processor 901 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present invention;

[0122] The memory 902 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 902 can store an operating system and other application programs. When the technical solution provided in the embodiment of this specification is implemented by software or firmware, the relevant program code is stored in the memory 902, and the processor 901 calls and executes the application plug-in cross-domain sharing method of the embodiment of the present invention;

[0123] Input / output interface 903, used to implement information input and output;

[0124] Communication interface 904, used to realize communication interaction between the device and other devices, which can be realized by wired mode (such as USB, network cable, etc.) or wireless mode (such as mobile network, WIFI, Bluetooth, etc.);

[0125] A bus 905 that transmits information between various components of the device (e.g., the processor 901, the memory 902, the input / output interface 903, and the communication interface 904);

[0126] The processor 901 , the memory 902 , the input / output interface 903 and the communication interface 904 are connected to each other in communication within the device via a bus 905 .

[0127] like Fig.10FIG. 1 is a schematic diagram of a storage medium according to an embodiment of the present invention. Fig.10 An embodiment of the present invention further provides a storage medium, which is a computer-readable storage medium used for computer-readable storage. The storage medium stores one or more programs 1001, and the one or more programs 1001 can be executed by one or more processors to implement the above-mentioned application plug-in cross-domain sharing method.

[0128] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely disposed relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0129] The embodiment of the present invention also discloses a computer program product or a computer program, wherein the computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. A processor of a computer device can read the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes Figure 1 The method shown.

[0130] In some selectable embodiments, the function / operation mentioned in the block diagram may not occur in the order mentioned in the operation diagram. For example, depending on the function / operation involved, the two boxes shown in succession can actually be executed substantially simultaneously or the above-mentioned boxes can sometimes be executed in reverse order. In addition, the embodiment presented and described in the flow chart of the present invention is provided by way of example, for the purpose of providing a more comprehensive understanding of technology. The disclosed method is not limited to the operation and logic flow presented herein. Selectable embodiments are expected, wherein the order of various operations is changed and the sub-operation of a part for which is described as a larger operation is performed independently.

[0131] In addition, although the present invention is described in the context of functional modules, it should be understood that, unless otherwise specified to the contrary, one or more of the above-mentioned functions and / or features can be integrated into a single physical device and / or software module, or one or more functions and / or features can be implemented in a separate physical device or software module. It is also understood that a detailed discussion of the actual implementation of each module is unnecessary for understanding the present invention. More specifically, in view of the properties, functions and internal relationships of the various functional modules in the device disclosed herein, the actual implementation of the module will be understood within the conventional skills of the engineer. Therefore, those skilled in the art can implement the present invention set forth in the claims without excessive experimentation using ordinary techniques. It is also understood that the specific concepts disclosed are merely illustrative and are not intended to limit the scope of the present invention, which is determined by the full scope of the appended claims and their equivalents.

[0132] If the above functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the above methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0133] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute instructions), or in conjunction with such instruction execution systems, devices or apparatuses. For the purposes of this specification, "computer-readable medium" can be any device that can contain, store, communicate, propagate or transmit a program for use by an instruction execution system, device or apparatus, or in conjunction with such instruction execution systems, devices or apparatuses.

[0134] More specific examples of computer-readable media (a non-exhaustive list) include the following: an electrical connection with one or more wires (electronic device), a portable computer disk case (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and editable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disk read-only memory (CDROM). In addition, the computer-readable medium may even be a paper or other suitable medium on which the above-mentioned program is printed, since the above-mentioned program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, deciphering or processing in other suitable ways as necessary, and then stored in a computer memory.

[0135] It should be understood that the various parts of the present invention can be implemented by hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, a plurality of steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0136] In the above description of this specification, the description with reference to the terms "one embodiment / example", "another embodiment / example" or "certain embodiments / examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0137] Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the claims and their equivalents.

[0138] The above is a specific description of the preferred implementation of the present invention, but the present invention is not limited to the above embodiments. Those skilled in the art may make various equivalent modifications or substitutions without violating the spirit of the present invention. These equivalent modifications or substitutions are all included in the scope defined by the claims of this application.

Claims

1. A method for cross-domain sharing of application plug-ins, characterized in that: The following steps are involved: Obtain application splitting request information of the first user, perform token verification and login state verification on the application splitting request information, and forward the application splitting request information that passes the verification to the application plug-in backend service; Performing application splitting on the corresponding first application according to the application splitting request information through the application plug-in backend service to obtain a first application plug-in, and outputting the first application plug-in to an application plug-in library; Obtaining the platform call request information of the second user, performing identity verification and authority verification on the platform call request information, and forwarding the verified platform call request information to the application plug-in backend service; The target application plug-in is obtained from the application plug-in library according to the platform call request information through the application plug-in backend service, and the application usage area of ​​the corresponding target application is determined according to the target application plug-in, and then the application usage area is shared with the second user.

2. The method for cross-domain sharing of application plug-ins according to claim 1, characterized in that: The token verification of the application split request information is performed through the following steps: Extracting a first token from the application splitting request information, and verifying whether the first token has been used; When the first token has not been used, the first token is parsed to obtain the encrypted original text, the first signature, and the token generation time, and whether the first token is within the validity period is verified according to the token generation time; When the first token is within the validity period, the user unique identifier of the first user is obtained through the login state identifier of the first user, the hash key value of the first user is obtained according to the user unique identifier, and the encrypted original text is signed according to the hash key value to obtain a second signature, and then it is determined whether the second signature is the same as the first signature; When the second signature is the same as the first signature, it is determined that the token verification is successful, and the login state identifier is added to the request header of the application split request information.

3. The method for cross-domain sharing of application plug-ins according to claim 2, characterized in that: The application splitting request information that passes the token verification is verified by performing a login state verification through the following steps: Extracting the login status identifier from the application splitting request information verified by the token, and querying the server whether the login status of the first user is valid according to the login status identifier; When the login state of the first user is valid, the first user information of the first user is queried from the server through the login state identifier, and the first user information is added to the request header of the application splitting request information.

4. The method for cross-domain sharing of application plug-ins according to claim 1, characterized in that: The step of performing application splitting on the corresponding first application according to the application splitting request information to obtain a first application plug-in, and outputting the first application plug-in to an application plug-in library specifically includes: Extracting an application identifier from the application splitting request information, and determining the first application to be split according to the application identifier; Splitting the first application according to a preset plug-in decoupling rule to obtain a plurality of first application plug-ins; The first application plug-in is output to a preset application plug-in transfer page, and the first application plug-in is forwarded to the application plug-in library through the application plug-in transfer page.

5. The method for cross-domain sharing of application plug-ins according to claim 1, characterized in that: The platform call request information is generated by the following steps: Sending the application plug-in identifier and the second user information of the second user to the application plug-in open platform through the third-party platform, and applying for interface authority and application plug-in authority from the application plug-in open platform; Verifying, by the application plug-in open platform, whether the second user has interface authority according to the second user information, and verifying, by the second user information and the application plug-in identifier, whether the second user has application plug-in authority; When the second user has the interface permission and the application plug-in permission, a one-time user identifier is generated, and the one-time user identifier is returned to the third-party platform; The platform calling request information is generated by the third-party platform according to the application plug-in identifier, the user one-time identifier and a preset application plug-in calling rule.

6. The method for cross-domain sharing of application plug-ins according to claim 5, characterized in that: The identity verification and authority verification of the platform call request information specifically includes: Extracting the application plug-in identifier and the user one-time identifier from the platform call request information, verifying whether the user one-time identifier matches the application plug-in identifier, and verifying whether the second user has authorized the application plug-in to access; When the user's one-time identification matches the application plug-in identification, and the second user has authorized the application plug-in to access, the application plug-in real address of the corresponding target application plug-in is determined according to the application plug-in identification, and a business access token is generated according to the application plug-in real address, and then the page is jumped to the application plug-in front-end page, and the business access token is sent to the application plug-in front-end service; The application plug-in front-end service requests the application plug-in back-end service for the authorized cell list of the second user, and verifies whether the second user has the authority to call the target application plug-in based on the authorized cell list and the service access token.

7. The method for cross-domain sharing of application plug-ins according to claim 6, characterized in that: The application plug-in cross-domain sharing method also includes the following steps: When the second user does not authorize the application plug-in to access, jump to the authorization page and prompt the second user to authorize the application plug-in to access; When the second user completes the application plug-in access authorization, obtain the user authorization number, and verify whether the user authorization number is consistent with the second user information; When the user authorization number is consistent with the second user information, the authorization record is saved within a preset time limit.

8. An application plug-in cross-domain sharing device, characterized in that: include: A first verification module is used to obtain application splitting request information of the first user, perform token verification and login state verification on the application splitting request information, and forward the application splitting request information that passes the verification to the application plug-in backend service; An application splitting module, configured to perform application splitting on the corresponding first application according to the application splitting request information through the application plug-in backend service, obtain a first application plug-in, and output the first application plug-in to an application plug-in library; A second verification module is used to obtain the platform call request information of the second user, perform identity verification and authority verification on the platform call request information, and forward the verified platform call request information to the application plug-in backend service; The plug-in calling module is used to obtain the target application plug-in in the application plug-in library according to the platform calling request information through the application plug-in backend service, and determine the application usage area of ​​the corresponding target application according to the target application plug-in, and then share the application usage area with the second user.

9. An electronic device, characterized in that: The electronic device includes a memory, a processor, a program stored in the memory and executable on the processor, and a data bus for realizing connection and communication between the processor and the memory. When the program is executed by the processor, the steps of the application plug-in cross-domain sharing method as described in any one of claims 1 to 7 are realized.

10. A storage medium, the storage medium being a computer-readable storage medium, used for computer-readable storage, characterized in that: The storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the steps of the application plug-in cross-domain sharing method as described in any one of claims 1 to 7.

Images