Integrated access method for multiple mobile applications
By registering basic capabilities in the capability registration center and unifying the encapsulation access method, a variety of mobile application integrated access methods are provided, which solves the problems of high mobile application development costs and poor user experience, and achieves higher security and stability And rich integration methods.
Patent Information
- Application Number
- CN202310696810.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-06-13
- Publication Date
- 2024-12-13
AI Technical Summary
The existing technology is difficult to effectively solve the problems of high development costs and poor user experience in complex business scenarios. Especially when the data volume of multiple business modules increases, traditional APP native development methods cannot meet system performance and stability. Require.
By registering a basic capability collection in the capability registration center and unifying the different access methods through the system management layer, a variety of integrated access methods are provided, including native access to this application, third-party mobile application access, and cloud H5 application access Input, local H5 application access and UniApp applet access to achieve diversified integration methods.
It reduces development costs and cycles, improves application security and stability, enhances user experience, and provides rich integration methods to adapt to complex business scenarios.
Smart Images

Figure CN119135751A_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the technical field of APP software, and in particular relates to a method for integrated access of multiple mobile applications. Background Art
[0002] In the era of mobile Internet and the interconnection of all things, businesses are becoming more and more complex, terminals are becoming more and more intelligent, and the volume of APPs is increasing, and the corresponding system performance experience requirements are also increasing. Taking ilink as an example, the business volume and the number of users are constantly increasing, and the amount of data in each business module is constantly increasing, and the requirements for the performance, experience, and stability of the mobile client are becoming higher and higher.
[0003] For example, Chinese patent CN115268996A discloses a mobile application migration method and device based on a mobile portal App, which is used to solve the huge workload of the existing mobile portal in the new framework, which seriously slows down the migration speed of mobile applications to mobile portals. It includes: the mobile portal obtains the components encapsulated by the security interaction platform and integrates them into the SDK file; based on the SDK file, the mobile application completes the connection with the security interaction platform by calling the API; the security interaction platform assigns a dynamic and unique port number to each mobile application that establishes a connection; the mobile application initiates a request to the security interaction platform through the ajax call port number, so that the security interaction platform can complete the mobile application by encrypting and encapsulating the request and forwarding it to the business server to complete the mobile application sending the request to the business service background. The above method greatly reduces the workload in the migration process and speeds up the application migration. For example, Chinese patent CN113824691A provides a method for implementing a silent login strategy for a third-party H5 application on a mobile terminal, which has the following steps: S1. The third-party Server B provides the corresponding Cookie and login information interface for the third-party H5APP application; S2. The mobile backend Server A requests the proxy forwarding function; S3. The mobile client A initiates the application to enter the third-party H5APP; S4. The third-party H5APP application determines whether it can enter through Cookie and LocalStorage login information. The third-party application access is realized and the silent and imperceptible H5 application login is realized by spending less resources on the mobile platform, reducing the labor cost of development and providing a better user experience.
[0004] In summary, current mobile applications are no longer just APPs. They already include all kinds of business application scenarios in various industries, large and small. If only APP native development is used, it will greatly increase the development cost and is not suitable for ecosystem creation. Driven by actual usage scenarios, a mobile application multiple integration solution came into being. Summary of the invention
[0005] The purpose of the present invention is to provide a method for integrated access of multiple mobile applications, which solves the existing problems through various platform access methods and provides more advantages and new features for these docking. The current method is mainly used for docking access to any other business scenarios in APP, providing more possibilities for the development of APP ecology.
[0006] In order to solve the above technical problems, the present invention is achieved through the following technical solutions:
[0007] The present invention is a method for integrated access of multiple mobile applications, comprising the following steps:
[0008] Register the underlying basic capability set in the capability registration center, and provide the basic capability set to the upper system management layer through the capability registration center;
[0009] The upper system management layer centrally encapsulates different access methods to form a system management function block;
[0010] Register the system management function block to the application capability registration center in different access modes, encapsulate the basic capabilities of each application through the upper layer of the App, form an application portal for the App to open to the outside world and use for system integration. At this point, the App has multiple access capabilities.
[0011] The access methods include: the mobile native access method of this application that embeds the native business module of this application in this application app, the access method of App integrating third-party mobile applications, the access method of App integrating H5 applications deployed in the cloud, the access method of App integrating local H5 applications, and the access method of App integrating UniApp mini-programs.
[0012] Furthermore, the method for the management layer to encapsulate the mobile native access mode of the application in which the native service module of the application is nested in the application app to form a system management function block includes:
[0013] Encapsulate the native function Module management class, and distinguish the entry categories of different functions through the function Key of the Module management class;
[0014] Use the Switch function to select the key entry corresponding to the type type. Different entries correspond to different native code function blocks.
[0015] The function Key is a custom string.
[0016] Furthermore, the method for the management layer to encapsulate the access mode of the App integrated with the third-party mobile application to form a system management function block includes:
[0017] Provide an open entrance through a third-party mobile application, and the platform App calls the corresponding cross-application calling method to invoke the third-party mobile application;
[0018] The method to invoke a third-party mobile application is:
[0019] Launch the application by specifying an Activity name, a Package name, or a Scheme.
[0020] Furthermore, the method for the management layer to encapsulate the access mode of the H5 application integrated with the App and deployed in the cloud to form a system management function block includes:
[0021] Deploy the H5 application address of the third-party cloud to the platform App, and access the H5 application on the cloud through the Internet (by accessing the third-party application access address), thereby realizing the access and use of the H5 application;
[0022] The method for deploying the H5 application address is: through the management platform App service, pull the H5 application access address of the third-party cloud under the corresponding authority.
[0023] Furthermore, the method for the management layer to encapsulate the access mode of the App integrated with the local H5 application to form a system management function block includes:
[0024] By embedding the resource package of the local H5 application into the platform App, the platform App can access the local H5 application resources and use the business application.
[0025] The method of embedding a resource package into a platform App is as follows: through the platform App file service, pull the corresponding resource package from the server, download it to the local mobile phone, and decompress it.
[0026] Furthermore, the method for the management layer to encapsulate the access mode of the App integrated UniApp applet to form a system management function block includes:
[0027] Integrate the UniApp applet SDK through the platform App to form the UniApp container base;
[0028] The platform App downloads the remote UniApp applet wgt package through remote download;
[0029] Use the UniApp container base locally to decompress and start it.
[0030] Furthermore, when docking with systems corresponding to different access methods, login-free use is performed. The method of login-free use is as follows: the platform App provides a user session, which is passed to the corresponding system session through five docking methods, and the corresponding system calls to obtain user information, thereby realizing single sign-on;
[0031] There are five docking methods: this mobile native application passes values through intent, third-party apps pass values through intent, local / remote H5 docking applications pass values through URL, and UniApp passes values through DCUniMPSDK.getInstance().openUniMP(mContext,Appid,configuration).
[0032] Furthermore, the docking methods all use Devlops technology to dock with cloud service pipeline deployment.
[0033] Furthermore, the platform App provides a native interaction mode for all docking modes, and the native interaction mode is a Cordova plug-in interaction mode.
[0034] Furthermore, the method for the capability registration center to register includes:
[0035] Create a new basic capability factory class;
[0036] Use HashMap structure to dynamically manage basic capability factory classes;
[0037] Through the registration center class, the App basic capability set, such as network request class, log tool class, DB management class, Log log printing class, etc., are added to the HashMap structure for unified management and use.
[0038] The present invention has the following beneficial effects:
[0039] The present invention enhances the development of the mobile application usage ecology by providing multiple mobile application access methods, and provides rich and diverse integration methods including mobile native applications, third-party mobile applications, remote H5 applications, local H5 applications, and UniApp mini-program applications. The value of this invention is to reduce development costs and cycles, improve application security and stability, and increase user experience.
[0040] Of course, any product implementing the present invention does not necessarily need to achieve all of the advantages described above at the same time. BRIEF DESCRIPTION OF THE DRAWINGS
[0041] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for describing the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying creative work.
[0042] Figure 1 This is a diagram of the architecture for integrating other applications into the mobile App of the present invention;
[0043] Figure 2 This is an architecture diagram of the mobile native access mode of this application in which the native business module of this application is embedded in this application App of the present invention;
[0044] Figure 3 This is an architecture diagram of the integration method of the platform App of the present invention into third-party mobile applications;
[0045] Figure 4 This is an architecture diagram of the integration mode of the H5 application integrated with the platform App of the present invention and deployed in the cloud;
[0046] Figure 5 This is the architecture diagram of the platform App of the present invention integrating local H5 application;
[0047] Figure 6 This is an architecture diagram of the integration method of the platform App of the present invention integrating the UniApp applet. DETAILED DESCRIPTION
[0048] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.
[0049] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.
[0050] It should also be understood that the term “and / or” used in the specification and appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.
[0051] As used in the specification and appended claims of this application, the term "if" can be interpreted as "when" or "uponce" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "uponce it is determined" or "in response to determining" or "uponce [described condition or event] is detected" or "in response to detecting [described condition or event]", depending on the context.
[0052] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.
[0053] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.
[0054] Embodiment 1:
[0055] See also Figure 1 As shown, the present invention is a method for integrated access of multiple mobile applications, comprising the following steps:
[0056] Register the underlying basic capability set in the capability registration center, and provide the basic capability set to the upper system management layer through the capability registration center;
[0057] The management layer centrally encapsulates different access methods to form a system management function block;
[0058] Register the system management function blocks to the application capability registration center in different access modes, encapsulate the access capabilities of each application through the upper layer of the App, and form an application portal for the App to be opened to the outside world and used for system integration. At this point, the App has multiple access capabilities.
[0059] The access methods include: the mobile native access method of this application that embeds the native business module of this application in this application app, the access method of App integrating third-party mobile applications, the access method of App integrating H5 applications deployed in the cloud, the access method of App integrating local H5 applications, and the access method of App integrating UniApp mini-programs.
[0060] As an embodiment provided by the present invention, preferably, the present application provides multiple mobile application access methods to enhance the use ecological development of mobile applications, specifically including:
[0061] This application is mobile native: the native function module / application developed for the specified function / business in the current mobile application;
[0062] Third-party mobile applications: third-party App mobile applications;
[0063] Remote H5 application: an H5 application deployed on a server and freely accessible on the Internet;
[0064] Local H5 application: a local H5 application that packages H5 resources and embeds them in the current mobile application;
[0065] UniApp mini program application: UniApp mini program application based on the current popular mini program framework.
[0066] Embodiment 2:
[0067] like Figure 1 As shown, Figure 1 The mobile application App access application framework diagram is a graphical introduction to the hierarchical structure of accessing other applications in the App for various integration implementation methods of other applications in the mobile App. The underlying basic capabilities are registered in the basic capability registration center, and the basic capabilities are provided to the upper system management layer. The management layer centrally encapsulates different access methods to form a system management layer, and registers the system management function blocks with the system management application capability registration center according to different access methods. At this point, the App has multiple access capabilities. The upper layer of the App encapsulates the access capabilities of each application to form an application entrance, which is provided to the App for external opening and system integration.
[0068] As an embodiment provided by the present invention, preferably, the underlying basic capability set is registered in the basic capability registration center, and the main algorithm is as follows:
[0069] Registration: Create a new basic capability factory class and use the HashMap structure to dynamically manage basic capability classes and methods. Through the registration center class, add App basic functions, such as network request class, log tool class, DB management class, Log log printing class, etc., to the HashMap structure for unified management.
[0070]
[0071]
[0072] like Figure 2 As shown, Figure 2 The mobile native access mode of the application in which the native business module of the application is nested in the application App is a native development function of the App. As an embodiment provided by the present invention, preferably, the management layer encapsulates the mobile native access mode of the application in which the native business module of the application is nested in the application App to form a system management function block, including:
[0073] Encapsulate the native function Module management class, and distinguish the entry categories of different functions through the function Key of the Module management class;
[0074] Use the Switch function to select the key entry corresponding to the type type. Different entries correspond to different native code function blocks (Modules). Use different function modules through App native code development. Advantages of this method: safe, better user experience, and unified App usage;
[0075] The function Key is a custom string.
[0076] As an embodiment provided by the present invention, preferably, the main algorithm for native application access encapsulation is:
[0077]
[0078]
[0079] like Figure 3 As shown, Figure 3 As an embodiment of the present invention, the method for the management layer to encapsulate the access method of the third-party mobile application integrated by the platform App to form a system management function block preferably includes:
[0080] Provide an open entrance through a third-party mobile application, and the platform App calls the corresponding cross-application calling method to invoke the third-party mobile application;
[0081] The method to invoke a third-party mobile application is:
[0082] It is launched by specifying the Activity name, Package name or Scheme. Advantages: fast, simple and low investment; Disadvantages: requires a third-party App to provide capabilities and data communication between the two Apps is difficult.
[0083] As an embodiment provided by the present invention, preferably, the main method of invoking the third-party mobile application is:
[0084] Three ways to launch third-party apps:
[0085] ①拉起指定Activity名称:
[0086] / / 方式1:
[0087] Intent intent = new Intent(Intent.ACTION_VIEW);
[0088] ComponentName componentName = new ComponentName("com.tencent.morris.activity",
[0089] "com.tencent.morris.activity.MainProxyActivity");
[0090] intent.setComponent(componentName);
[0091] this.startActivity(intent);
[0092] / / 方式2:
[0093] Intent intent = new Intent(Intent.ACTION_VIEW);
[0094] intent.setClassName("com.tencent.morris.activity",
[0095] "com.tencent.morris.activity.MainProxyActivity");
[0096] this.startActivity(intent);
[0097] ②拉起指定Package名称
[0098] Intent intent = getPackageManager().getLaunchIntentForPackage("com.tencent.morris.activity");
[0099] this.startActivity(intent);
[0100] ③通过Scheme拉起
[0101] Intent intent=new Intent(Intent.ACTION_VIEW);
[0102] Uri data=Uri.parse("mytest: / / hello.world:1024 / test?name=zhangsan&age=27");
[0103] intent.setData(data);
[0104] this.startActivity(intent); 1
[0106] <a href="mytest: hello.world:1024 test?name=zhangsan&age=27"> Open the App page .
[0107] like Figure 4 As shown, Figure 4 The integration method of the H5 application deployed in the cloud for platform App integration deploys the third-party cloud application address (by managing the platform service, pulling the third-party application access address under the corresponding authority) to the platform App, and accessing the cloud application through the Internet (by accessing the third-party application access address), thereby realizing the access and use of the application. Advantages: low cost, quick access, remote update platform App is not affected; Disadvantages: the user experience is greatly affected by the network.
[0108] As an embodiment provided by the present invention, preferably, the method for the management layer to encapsulate the access mode of the H5 application integrated and deployed in the cloud by the App to form a system management function block includes: deploying the H5 application address of the third-party cloud to the platform App, accessing the H5 application in the cloud through the Internet (by accessing the third-party application access address), thereby realizing the access and use of the H5 application;
[0109] The method for deploying the H5 application address is: through the management platform App service, pull the H5 application access address of the third-party cloud under the corresponding authority.
[0110] like Figure 5 As shown, Figure 5 Integrate local H5 applications for platform apps. By embedding local H5 resource packages into platform apps (pull the corresponding resource packages from the server through the platform file service, download them to the local phone, and decompress them), platform apps can access local resources and use business applications. Advantages: Better experience for using super-large H5 applications; Disadvantages: Local resource occupation caused by resource localization.
[0111] As an embodiment provided by the present invention, preferably, the method in which the management layer encapsulates the access mode of the App integrated with the local H5 application to form a system management function block includes:
[0112] By embedding the resource package of the local H5 application into the platform App, the platform App can access the local H5 application resources and use the business application;
[0113] The method of embedding a resource package into a platform App is as follows: through the platform App file service, pull the corresponding resource package from the server, download it to the local mobile phone, and decompress it.
[0114] like Figure 6 As shown, Figure 6 The platform app integrates the UniApp applet by integrating the UniApp applet SDk, forming the UniApp container base. The platform app downloads the remote UniApp applet wgt package through the remote download method, and uses the UniApp container base to decompress and start related operations locally. Advantages: unlimited use after one access, good user experience; Disadvantages: high network requirements, and current compatibility defects.
[0115] As an embodiment provided by the present invention, preferably, the method in which the management layer encapsulates the access mode of the App integrated UniApp applet to form a system management function block includes:
[0116] Integrate the UniApp applet SDK through the platform App to form the UniApp container base;
[0117] The platform App downloads the remote UniApp applet wgt package through remote download;
[0118] Use the UniApp container base locally to decompress and start it.
[0119] Embodiment three:
[0120] This embodiment is the production accumulation of actual projects. Facing the complex business system, as a platform, it is necessary to have a strong basic stability and a variety of access methods, which should be more convenient to use (no login required) and more convenient and smoother to use (providing more native interaction methods). This embodiment focuses on the platform's diverse access methods and provides more advantages and new features for these docking.
[0121] As an embodiment provided by the present invention, preferably, when docking with systems corresponding to different access methods, login-free use is performed, and the method of login-free use is: the platform App provides a user session, which is respectively passed to the corresponding system session through five docking methods, and the corresponding system calls to obtain user information, thereby realizing single sign-on;
[0122] There are five docking methods: this mobile native application passes values through intent, third-party apps pass values through intent, local / remote H5 docking applications pass values through URL, and UniApp passes values through DCUniMPSDK.getInstance().openUniMP(mContext,Appid,configuration).
[0123] As an embodiment provided by the present invention, preferably, all docking methods are docked with this cloud service pipeline deployment (specifically using Devlops technology).
[0124] As an embodiment provided by the present invention, preferably, we provide native interaction methods for all docking methods, the platform provides Cordova plug-in interaction methods, and has provided dozens of available methods, providing native interaction methods, so that the use of access application functions is no longer restricted by technology, and the native platform directly provides convenience.
[0125] As an embodiment provided by the present invention, preferably, the method for the capability registration center to register includes:
[0126] Create a new basic capability factory class;
[0127] Use HashMap structure to dynamically manage basic capability factory classes and methods;
[0128] Through the registration center class, the App basic capability set, such as network request class, log tool class, DB management class, Log log printing class, etc., are added to the HashMap structure for unified management and use.
[0129] A method for integrated access of multiple mobile applications, which enhances the development of the mobile application usage ecology by providing multiple mobile application access methods, and provides rich and diverse integration methods including native mobile applications, third-party mobile applications, remote H5 applications, local H5 applications, and UniApp mini-program applications. Its value is to reduce development costs and cycles, improve application security and stability, and increase user experience.
[0130] In the description of this specification, the description with reference to the terms "one embodiment", "example", "specific example", 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 can be combined in any one or more embodiments or examples in a suitable manner.
[0131] The preferred embodiments of the present invention disclosed above are only used to help illustrate the present invention. The preferred embodiments do not describe all the details in detail, nor do they limit the invention to the specific implementation methods described. Obviously, many modifications and changes can be made according to the content of this specification. This specification selects and specifically describes these embodiments in order to better explain the principles and practical applications of the present invention, so that those skilled in the art can understand and use the present invention well. The present invention is limited only by the claims and their full scope and equivalents.
Claims
1. A method for integrated access of multiple mobile applications, characterized in that: The following steps are involved: Register the underlying basic capability set in the capability registration center, and provide the basic capability set to the management layer through the capability registration center; The management layer centrally encapsulates different access methods to form a system management function block; Register the system management function blocks to the application capability registration center according to different access methods, encapsulate the basic capabilities of each application through the upper layer of the App, and provide the formed application entrance to the App for external opening and system integration; The access methods include: the mobile native access method of this application that embeds the native business module of this application in this application app, the access method of App integrating third-party mobile applications, the access method of App integrating H5 applications deployed in the cloud, the access method of App integrating local H5 applications, and the access method of App integrating UniApp mini-programs.
2. A method for integrated access of multiple mobile applications according to claim 1, characterized in that: The method for the management layer to encapsulate the mobile native access mode of the application in which the native service module of the application is embedded in the application app to form a system management function block includes: Encapsulate the native function Module management class, and distinguish the entry categories of different functions through the function Key of the Module management class; Use the Switch function to select the key entry corresponding to the type type. Different entries correspond to different native code function blocks. The function Key is a custom string.
3. The method for integrated access of multiple mobile applications according to claim 1, characterized in that: The method for the management layer to encapsulate the access mode of the App integrated with the third-party mobile application to form a system management function block includes: Provide an open entrance through a third-party mobile application, and the platform App calls the corresponding cross-application calling method to invoke the third-party mobile application; The method to invoke a third-party mobile application is: Launch the application by specifying an Activity name, a Package name, or a Scheme.
4. The method for integrated access of multiple mobile applications according to claim 1, characterized in that: The method for the management layer to encapsulate the access mode of the H5 application integrated and deployed in the cloud by the App to form a system management function block includes: Deploy the H5 application address of the third-party cloud to the platform App, access the H5 application on the cloud through the Internet, and realize the access and use of the H5 application; The method for deploying the H5 application address is: through the management platform App service, pull the H5 application access address of the third-party cloud under the corresponding authority.
5. The method for integrated access of multiple mobile applications according to claim 1, characterized in that: The method for the management layer to encapsulate the access mode of the App integrated with the local H5 application to form a system management function block includes: By embedding the resource package of the local H5 application into the platform App, the platform App can access the local H5 application resources and use the business application. The method of embedding a resource package into a platform App is as follows: through the platform App file service, pull the corresponding resource package from the server, download it to the local mobile phone, and decompress it.
6. The method for integrated access of multiple mobile applications according to claim 1, characterized in that: The method for the management layer to encapsulate the access mode of the App integrated UniApp applet to form a system management function block includes: Integrate the UniApp applet SDK through the platform App to form the UniApp container base; The platform App downloads the remote UniApp applet wgt package through remote download; Use the UniApp container base locally to decompress and start it.
7. The method for integrated access of multiple mobile applications according to claim 1, characterized in that: When docking with systems corresponding to different access methods, login-free use is performed. The method of login-free use is as follows: the platform App provides a user session, which is passed to the corresponding system session through different docking methods. The corresponding system calls to obtain user information to achieve single sign-on; The connection method is: passing values through intent, passing values through url, and UniApp passing values through DCUniMPSDK.getInstance().openUniMP(mContext,Appid,configuration).
8. A method for integrated access of multiple mobile applications according to claim 7, characterized in that: The docking methods described above all use Devlops technology to dock with the cloud service pipeline for deployment.
9. A method for integrated access of multiple mobile applications according to claim 7, characterized in that: The platform App provides a native interaction mode for all docking modes, and the native interaction mode is a Cordova plug-in interaction mode.
10. The method for integrated access of multiple mobile applications according to claim 1, characterized in that: The method for the capability registration center to register includes: Create a new basic capability factory class; Use HashMap structure to dynamically manage basic capability factory classes; Through the registration center class, the App basic capability set is added to the HashMap structure for unified management and use.
