Open developer management platform

Abstract

The invention relates to an open-type developer management platform, and the platform comprises a registration module which is used for a user to register an account number which can log in the management platform; the App registration module is used for the user to upload an App program on the management platform and set the use permission of the App; the App Key generation module is used for generating an identification ID uniquely corresponding to the App; the permission package generation module is used for packaging an application scene and a permission set for obtaining use authorization; the SDK tool is used for packaging an access request of a third-party platform and outputting a login and authentication request to the management platform; and the App key generation module is used for generating a unique corresponding key ID for each user using the App. According to the method, unified login, dynamic authorization and permission packet encryption are integrated, the development process is simplified, the development cost is reduced, meanwhile, safety and stability are ensured through application classification and a multi-layer protection system, flexibility and expandability are achieved, and an efficient and convenient development and management platform is created for developers.

Description

Technical Field

[0001] The present invention relates to the field of intelligent management technology, in particular to an open developer management platform. Background Art

[0002] With the promotion of sharing platforms (Tongfu sharing platform) for cooperative merchants within the enterprise, in the process of implementing and promoting the strategies of linking factories, tying merchants, sticking to stores and locking in customers, all links of physical transactions need to be connected in series on the sharing platform to build a new business ecology in the county.

[0003] Since the sharing platform needs to connect to the third-party platform of the cooperating merchants, the following problems are faced in the effective integration of the sharing platform and the third-party platform:

[0004] As the Tongfu Sharing Platform continues to expand, many third-party platforms seek to connect with it to achieve resource sharing and business collaboration. However, due to the different technical architectures, interface protocols and data processing methods of each third-party platform, the integration process becomes complicated and time-consuming. This diversity hinders the flow of data between platforms and affects the smoothness of the overall business process.

[0005] The current account system requires developers to register accounts and passwords on each connected platform, which not only increases the user's memory burden, but also makes the login process lengthy and cumbersome. Users need to frequently switch accounts between different platforms, which reduces work efficiency and increases the risk of password leakage.

[0006] The traditional account password system has many deficiencies in terms of security. On the one hand, passwords are easy to guess or crack, especially when users choose simple passwords or use the same password; on the other hand, there may be security loopholes in the storage and transmission of passwords, making passwords easy to be stolen.

[0007] During data transmission, plaintext data can be easily intercepted and tampered with. Once data is obtained or modified by a malicious third party during transmission, the integrity and confidentiality of the data will be seriously damaged, thus affecting the normal operation of the business.

[0008] The current application management system lacks uniformity and flexibility, which makes it difficult for developers to manage multiple applications. For example, developers need to log in to different platforms to manage their own applications, which not only increases management costs but also reduces management efficiency.

[0009] During the docking process, due to technical differences and inconsistent data formats between platforms, developers often need to repeatedly develop the same or similar functional modules, which not only increases development costs and time investment, but also leads to waste of resources and inefficiency.

[0010] The information disclosed in this background technology section is only intended to deepen the understanding of the overall background technology of the present invention, and should not be regarded as acknowledging or suggesting in any form that the information constitutes the prior art already known to those skilled in the art. Summary of the invention

[0011] In view of the defects existing in the prior art, the purpose of the present invention is to provide an open developer management platform that integrates unified login, dynamic authorization, and permission package encryption, simplifies the development process, reduces development costs, and ensures security and stability through application classification and a multi-layer protection system. It has both flexibility and scalability, creating an efficient and convenient development and management platform for developers.

[0012] In order to achieve the above purpose, the technical solution adopted by the present invention is:

[0013] An open developer management platform, characterized by comprising:

[0014] The registration module is used for users to register an account to log in to the management platform;

[0015] App registration module, which is used by users to upload App programs on the management platform and set App usage permissions;

[0016] App Key generation module, used to generate an identification ID that is unique to the uploaded App;

[0017] The permission package generation module is used to encapsulate the application scenarios and permission sets that are authorized for use;

[0018] SDK tool, used to encapsulate and encrypt access requests from third-party platforms, and output login and authentication requests including requested resource information and request parameter information to the management platform;

[0019] The App application key generation module is used to generate a unique key ID for each user using the App.

[0020] Based on the above technical solution, after the user completes the account registration through the registration module and successfully logs in to the management platform, he can upload and publish the App program through the App registration module. The App registration module maintains an App classification table to store the list of published Apps, and manages and standardizes the types of Apps through the App classification table.

[0021] Based on the above technical solution, the App classification table divides Apps by function, each App completes a single link of the entity transaction, and discloses input parameter information, output parameter information and custom information.

[0022] Based on the above technical solution, the App registration module maintains the App's usage rights by binding the third-party platform access path to the App;

[0023] During binding, the App registration module obtains the authentication code from the third-party platform through the secret key. When obtaining the third-party platform data through the access path, the third-party platform verifies the authentication code to determine whether the usage permission is valid.

[0024] Based on the above technical solution, the third-party platform can cancel the authentication code generated last time by actively refreshing the authentication code, thereby realizing dynamic authorization management;

[0025] When the management platform requests the third-party platform to refresh the authentication code, the refreshed authentication code is synchronized to the management platform and the third-party platform to realize dynamic update of the authentication code.

[0026] Based on the above technical solution, after the user successfully uploads the App program, the App Key generation module assigns a unique corresponding identification ID to the App;

[0027] For apps that have obtained identification IDs, users also need to use the permission package generation module to assign corresponding permission sets to the apps according to application scenarios, and encapsulate the permission sets into downloadable permission package files.

[0028] On the basis of the above technical solution, the encapsulation includes encrypting the permission set and embedding verification information, and the verification information at least includes the usage period and the management platform login account.

[0029] Based on the above technical solution, after the user installs the SDK tool, the SDK tool is used to obtain the list of published apps from the management platform;

[0030] After selecting an app from the list of published apps, the SDK tool initiates an access request according to the third-party platform access path corresponding to the app. The access request is used to obtain permission to use the app.

[0031] On the basis of the above technical solution, after the third-party platform registers the access request and agrees to issue the usage permission, the third-party platform notifies the management platform to send the identification ID and permission package file corresponding to the App to the account corresponding to the access request;

[0032] After the user downloads and saves the permission package file locally, the App reads the local permission package file to determine the account information and permission set when it starts, and completes App initialization based on the read information.

[0033] On the basis of the above technical solution, when the App is used for the first time, the App initialization includes binding the local client identification information of the permission package file, and the client identification information is transmitted back to the management platform for storage and filing.

[0034] The open developer management platform described in the present invention realizes refined management and dynamic authorization of App through modules such as App registration, App Key generation, and permission package generation. After registration, users can upload App and set permissions, and interact with third-party platforms through SDK tools to obtain authentication codes to ensure the validity of usage permissions. At the same time, the platform supports encryption and verification of permission packages, improves usage efficiency and management uniformity, reduces development costs, and improves security and convenience, and can provide developers with an efficient, secure, and convenient development and management environment. It has the following beneficial effects:

[0035] 1. Refined permission management: Through the App registration module and permission package generation module, users can set specific usage permissions for the App to achieve precise control over App functions.

[0036] 2. Dynamic authorization mechanism: App Key generation and dynamic update of authentication codes allow the platform and third-party platforms to flexibly manage App usage permissions and respond to permission change requirements in a timely manner.

[0037] 3. Improve usage efficiency: Users log in uniformly through the management platform, reducing the tediousness of logging in to multiple platforms. At the same time, the use of SDK tools simplifies the access request process of third-party platforms.

[0038] 4. Security enhancement: The encryption and verification mechanism of the permission package ensures the security of App use and prevents unauthorized access.

[0039] 5. Reduce development costs: The language development package and annotation function library embedded in the SDK tool provide convenience for developers, reduce development workload, and thus reduce development costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] The present invention has the following accompanying drawings:

[0041] The accompanying drawings are used to better understand the present invention and do not constitute an improper limitation of the present invention.

[0042] Figure 1 System architecture diagram of embodiment 1 of an open developer management platform described in the present invention. DETAILED DESCRIPTION

[0043] The present invention is further described in detail below in conjunction with the accompanying drawings. The detailed description is an explanation made in conjunction with the exemplary embodiments of the present invention, including various details of the embodiments of the present invention to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those skilled in the art that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for the sake of clarity and conciseness, the description of well-known functions and structures is omitted in the following description.

[0044] like Figure 1 As shown, the present invention provides an open developer management platform, including:

[0045] The registration module is used for users to register an account to log in to the management platform;

[0046] App registration module, which is used by users to upload App programs on the management platform and set App usage permissions;

[0047] App Key generation module, used to generate an identification ID that is unique to the uploaded App;

[0048] The permission package generation module is used to encapsulate the application scenarios and permission sets that are authorized for use;

[0049] SDK tool, used to encapsulate and encrypt access requests from third-party platforms, and output login and authentication requests including requested resource information and request parameter information to the management platform;

[0050] The App application key generation module is used to generate a unique key ID for each user using the App.

[0051] The platform described in this embodiment starts with user registration. Through the App registration module, developers can easily upload their own App programs and set their usage permissions in detail. The platform also integrates an App Key generation module to ensure that each App can obtain a unique identification ID for easy management and identification. In addition, the permission package generation module provides developers with the ability to flexibly define App usage permissions, further enhancing the flexibility of permission management. The platform is also equipped with SDK tools, which not only encapsulate access requests from third-party platforms, but also perform encryption processing to ensure the security of data transmission. Finally, the App application key generation module generates a unique key ID for each user using the App, enhancing the security of user authentication and authorized access.

[0052] The integrated services provided by the platform significantly improve the development efficiency of developers. From App registration, uploading, permission setting to encryption SDK integration, everything is done on one platform, which greatly reduces the repetitive work of developers. At the same time, the platform provides users with a safer and more stable usage environment through strict permission management and data encryption technology. This not only enhances users' trust in the platform, but also promotes the healthy development of the App ecosystem.

[0053] Based on the above technical solution, after the user completes the account registration through the registration module and successfully logs in to the management platform, he can upload and publish the App program through the App registration module. The App registration module maintains an App classification table to store the list of published Apps, and manages and standardizes the types of Apps through the App classification table.

[0054] After the user registers and logs in, the App registration function is provided, App uploading and publishing are supported, and an App classification table is maintained to standardize and manage App types. This solution not only simplifies the development process, but also improves the platform's organization and user experience, and helps build an orderly App ecosystem.

[0055] Based on the above technical solution, the App classification table divides Apps by function, each App completes a single link of the entity transaction, and discloses input parameter information, output parameter information and custom information.

[0056] The App classification table further subdivides Apps by function. Each App focuses on completing a specific link in the physical transaction and discloses its input and output parameters and custom information. This solution not only enhances the professionalism and flexibility of the App, but also promotes the transparency and standardization of the transaction process. Apps can be selected independently according to needs.

[0057] Based on the above technical solution, the App registration module maintains the App's usage rights by binding the third-party platform access path to the App;

[0058] During binding, the App registration module obtains the authentication code from the third-party platform through the secret key. When obtaining the third-party platform data through the access path, the third-party platform verifies the authentication code to determine whether the usage permission is valid.

[0059] The App can be disabled by deleting the authentication code and can be republished by updating the authentication code, thus achieving refined management of resources.

[0060] The App registration module manages App usage permissions by binding the third-party platform access path to the App and using the secret key to obtain the authentication code, thus achieving refined resource management. This solution not only improves the flexibility and security of permission management, but also allows the activation and re-release of the App to be controlled by simply deleting or updating the authentication code, thereby optimizing resource allocation and operation and maintenance efficiency.

[0061] Based on the above technical solution, the third-party platform can cancel the authentication code generated last time by actively refreshing the authentication code, thereby realizing dynamic authorization management;

[0062] When the management platform requests the third-party platform to refresh the authentication code, the refreshed authentication code is synchronized to the management platform and the third-party platform to realize dynamic update of the authentication code.

[0063] By introducing a mechanism for the third-party platform to actively refresh the authentication code, dynamic authorization management of App usage permissions is achieved. The authentication code that is refreshed synchronously between the management platform and the third-party platform ensures the real-time and security of the authentication code, and improves the flexibility and response speed of permission management.

[0064] Based on the above technical solution, after the user successfully uploads the App program, the App Key generation module assigns a unique corresponding identification ID to the App;

[0065] For apps that have obtained identification IDs, users also need to use the permission package generation module to assign corresponding permission sets to the apps according to application scenarios, and encapsulate the permission sets into downloadable permission package files.

[0066] After the user uploads the App, this embodiment automatically assigns a unique identification ID through the App Key generation module, and uses the permission package generation module to customize the permission set for the App according to the application scenario to form a downloadable permission package file, thereby improving the personalized configuration and flexible authorization of the App.

[0067] On the basis of the above technical solution, the encapsulation includes encrypting the permission set and embedding verification information, and the verification information at least includes the usage period and the management platform login account.

[0068] By logging into the management platform, there is no need to log in separately for each App when using it, which reduces the number of logins, improves usage efficiency, and improves unified management.

[0069] When encapsulating the permission package, this embodiment not only encrypts the permission set to enhance security, but also embeds verification information to control the usage period and verify the management platform account. This design simplifies the App login process, achieves unified management and efficient use, and improves user experience and management efficiency.

[0070] Based on the above technical solution, after the user installs the SDK tool, the SDK tool is used to obtain the list of published apps from the management platform;

[0071] After selecting an app from the list of published apps, the SDK tool initiates an access request according to the third-party platform access path corresponding to the app. The access request is used to obtain permission to use the app.

[0072] After installing the SDK tool, users can easily obtain a list of published apps from the management platform and select an app to initiate an access request through the SDK to obtain usage permissions. This process simplifies the permission acquisition process, improves user experience, and ensures the security and efficiency of access requests.

[0073] On the basis of the above technical solution, after the third-party platform registers the access request and agrees to issue the usage permission, the third-party platform notifies the management platform to send the identification ID and permission package file corresponding to the App to the account corresponding to the access request;

[0074] After the user downloads and saves the permission package file locally, the App reads the local permission package file to determine the account information and permission set when it starts, and completes App initialization based on the read information.

[0075] After the third-party platform confirms the access request and authorizes it, the management platform sends the App identification ID and permission package file to the user. The user downloads and saves the permission package. When the App starts, it reads the permission package information to complete initialization. The permission management is accurate and efficient, which improves the App startup speed and user experience.

[0076] On the basis of the above technical solution, when the App is used for the first time, the App initialization includes binding the local client identification information of the permission package file, and the client identification information is transmitted back to the management platform for storage and filing.

[0077] After logging in to the management platform, as long as there is a permission package file corresponding to the account locally and the permission package file is bound to the client in the management platform, you can use the App safely and efficiently afterwards.

[0078] When the App is used for the first time, the permission package file is bound to the local client identification information, and the information is sent back to the management platform for filing, thus realizing the precise association between the permission package and the user. After that, the user can log in to the management platform to use the bound App safely and efficiently without repeated authorization, which improves the convenience of use and management efficiency.

[0079] Based on the above technical solution, the SDK tool has an embedded language development kit, which supports development codes of Java, Go or PHP. The language development kit has an embedded annotated function library for calling, which reduces the development workload and reduces development costs.

[0080] The contents not described in detail in this specification belong to the prior art known to professional and technical personnel in this field.

[0081] The above description is only a preferred embodiment of the present invention, and the protection scope of the present invention is not limited to the above embodiment. Any equivalent modifications or changes made by those skilled in the art based on the contents disclosed by the present invention should be included in the protection scope recorded in the claims.

Claims

1. An open developer management platform, characterized in that: include: The registration module is used for users to register an account to log in to the management platform; App registration module, which is used by users to upload App programs on the management platform and set App usage permissions; App Key generation module, used to generate an identification ID that is unique to the uploaded App; The permission package generation module is used to encapsulate the application scenarios and permission sets that are authorized for use; SDK tool, used to encapsulate and encrypt access requests from third-party platforms, and output login and authentication requests including requested resource information and request parameter information to the management platform; The App application key generation module is used to generate a unique key ID for each user using the App.

2. An open developer management platform as claimed in claim 1, characterized in that: After the user completes the account registration through the registration module and successfully logs in to the management platform, the App program can be uploaded and published through the App registration module. The App registration module maintains an App classification table to store the list of published Apps, and manages and standardizes the types of Apps through the App classification table.

3. An open developer management platform as claimed in claim 2, characterized in that: The App classification table divides Apps by function. Each App completes a single link of an entity transaction and discloses input parameter information, output parameter information, and custom information.

4. An open developer management platform as claimed in claim 2, characterized in that: The App registration module maintains the App's usage permissions by binding the third-party platform access path to the App; During binding, the App registration module obtains the authentication code from the third-party platform through the secret key. When obtaining the third-party platform data through the access path, the third-party platform verifies the authentication code to determine whether the usage permission is valid.

5. An open developer management platform as claimed in claim 4, characterized in that: The third-party platform can actively refresh the authentication code to cancel the authentication code generated last time and realize dynamic authorization management; When the management platform requests the third-party platform to refresh the authentication code, the refreshed authentication code is synchronized to the management platform and the third-party platform to realize dynamic update of the authentication code.

6. An open developer management platform as claimed in claim 1, characterized in that: After the user successfully uploads the App program, the App Key generation module assigns a unique corresponding identification ID to the App; For apps that have obtained identification IDs, users also need to use the permission package generation module to assign corresponding permission sets to the apps according to application scenarios, and encapsulate the permission sets into downloadable permission package files.

7. An open developer management platform as claimed in claim 6, characterized in that: The encapsulation includes encrypting the permission set and embedding verification information, and the verification information at least includes the usage period and the management platform login account.

8. An open developer management platform as claimed in claim 1, characterized in that: After the user installs the SDK tool, he or she can obtain the list of published apps from the management platform through the SDK tool; After selecting an app from the list of published apps, the SDK tool initiates an access request according to the third-party platform access path corresponding to the app. The access request is used to obtain permission to use the app.

9. An open developer management platform as claimed in claim 8, characterized in that: After the third-party platform registers the access request and agrees to issue the usage permission, the third-party platform notifies the management platform to send the identification ID and permission package file corresponding to the App to the account corresponding to the access request; After the user downloads and saves the permission package file locally, the App reads the local permission package file to determine the account information and permission set when it starts, and completes App initialization based on the read information.

10. An open developer management platform as claimed in claim 9, characterized in that: When the App is used for the first time, the App initialization includes binding the local client identification information of the permission package file, and the client identification information is sent back to the management platform for storage and filing.

Images