A method and device for acquiring sub-application data based on a unified management platform

Abstract

The embodiment of the present application discloses a method and device for acquiring sub-application data based on a unified management platform, including: receiving access request information sent by a client, the access request information including user identity information and access address; determining the user's access permission level according to the set unified permission verification rules and user identity information, and when the access permission level is the preset access permission level, querying the loading address matching the access address in the set routing table, and loading the application data of the sub-application based on the queried loading address; calling the application data based on the preset communication mechanism, and sending the application data to the client, for the client to perform management operations of the sub-application based on the application data, and the application data is the public component data obtained based on the public component development of each sub-application. It can improve the efficiency of sub-application management, reduce the management cost of sub-applications, and also ensure the security of sub-application data.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computer technology, and in particular to a method and device for acquiring sub-application data based on a unified management platform. Background Art

[0002] With the development and application of computer technology, many companies use a large number of sub-applications to manage the company's various businesses. These sub-applications have decentralized and independent operating systems. Each sub-application also has independent management permissions and development and deployment environments. Developers log in to the corresponding sub-applications through the recorded account and password of each sub-application and manage each sub-application.

[0003] In the prior art, when managing multiple sub-applications, it is usually necessary to switch between the sub-application entrances, which increases the operational complexity of sub-application management and reduces the sub-application management efficiency. In addition, in the process of developing or maintaining each sub-application, each sub-application needs to be operated separately, which will involve a large amount of repeated development and maintenance work, thereby reducing the sub-application development and maintenance efficiency and correspondingly increasing the sub-application development and maintenance costs. In addition, due to the inconsistency of the login permissions of each sub-application, the data security of each sub-application cannot be guaranteed. Summary of the invention

[0004] The embodiments of the present application provide a sub-application data acquisition method and device based on a unified management platform, which solves the problems of low sub-application management efficiency, high management cost and lack of sub-application data security caused by the high operational complexity of sub-application management. It can improve the efficiency of sub-application management, reduce the management cost of sub-applications, and ensure the security of sub-application data.

[0005] In a first aspect, an embodiment of the present application provides a method for acquiring sub-application data based on a unified management platform, comprising:

[0006] Receive access request information sent by the client, wherein the access request information includes user identity information and access address;

[0007] Determine the user's access permission level according to the set unified permission verification rule and the user identity information, and when the access permission level is the preset access permission level, query the set routing table for a loading address that matches the access address, and load the application data of the sub-application based on the queried loading address;

[0008] The application data is called based on a preset communication mechanism and sent to the client, so that the client can perform management operations on sub-applications based on the application data. The application data is common component data developed based on common components of each sub-application.

[0009] Optionally, after the application data of the sub-application is loaded based on the queried loading address, the method further includes:

[0010] Determine the amount of shared data identified in the application data, and if the amount of shared data is greater than a preset sharing threshold, send the shared data to each sub-application based on a message queue communication mechanism;

[0011] When the amount of the shared data is less than or equal to a preset sharing threshold, the shared data is sent to each sub-application based on a full-duplex communication mechanism.

[0012] Optionally, the preset access permission levels include level one access permission, level two access permission and level three access permission, and determining the user's access permission level according to the set unified permission verification rule and the user identity information includes:

[0013] When the user identity information is a mobile phone number and a verification code, and the mobile phone number and the verification code meet the security verification conditions, determining that the user's access authority level is a first-level access authority, and the first-level access authority includes a login authority;

[0014] When the user identity information is a login account and a login password, and the login account and the login password match the login account and the login password stored in the database, determining that the user's access permission level is a secondary access permission, and the secondary access permission includes a sub-application loading permission;

[0015] When the user identity information is biometric information and the biometric information matches the biometric information stored in the database, it is determined that the user's access permission level is a third-level access permission, and the third-level access permission includes a sub-application loading permission and a development and deployment permission.

[0016] Optionally, after calling the application data based on a preset communication mechanism, the method further includes:

[0017] Counting the number of times each application data is received within a preset time interval, and determining whether the number of times each application data is received exceeds a preset access number;

[0018] When the number of times the application data is received exceeds the preset number of accesses, the corresponding user operation record is queried based on the application data, the most recent operation data in the user operation record is bound to the user's historical identity information, and marked in the user operation record.

[0019] Optionally, after counting the number of times each application data is received within the preset time interval, the method further includes:

[0020] A user access statistics table is generated according to the number of times each application data is received, and the user access statistics table is sent to the client.

[0021] Optionally, after receiving the access request information sent by the client, the method further includes:

[0022] A query is made in the user operation record table as to whether there is historical identity information matching the user identity information. If there is historical identity information matching the user identity information, the operation data corresponding to the historical identity information is loaded based on the binding relationship between the historical identity information and the most recent operation data.

[0023] Optionally, before receiving the access request information sent by the client, the method further includes:

[0024] A plurality of sub-application identifiers are set on a client page according to the access address exposed by the sub-application, so that the client can send access request information by selecting the sub-application identifier, wherein the sub-application identifier is associated with the access address of the sub-application.

[0025] In a second aspect, an embodiment of the present application provides a sub-application data acquisition device based on a unified management platform, including:

[0026] A routing module, used to receive access request information sent by a client, wherein the access request information includes user identity information and an access address;

[0027] A permission module, used to determine the user's access permission level according to the set unified permission verification rules and the user identity information;

[0028] The routing module is further configured to query a set routing table for a loading address matching the access address when the access permission level is a preset access permission level;

[0029] An application loading module, used to load application data of a sub-application based on the queried loading address;

[0030] A communication module is used to call the application data based on a preset communication mechanism and send the application data to the client, so that the client can perform management operations on sub-applications based on the application data. The application data is public component data developed based on public components of each sub-application.

[0031] In the third aspect, an embodiment of the present application provides a sub-application data acquisition device based on a unified management platform, the device comprising: one or more processors; a storage device configured to store one or more programs, when the one or more programs are executed by the one or more processors, the one or more processors implement the sub-application data acquisition method based on the unified management platform described in the first aspect.

[0032] In a fourth aspect, an embodiment of the present application provides a storage medium comprising computer executable instructions, which, when executed by a computer processor, are used to execute the sub-application data acquisition method based on a unified management platform as described in the first aspect.

[0033] The embodiment of the present application receives access request information sent by the client, and the access request information includes user identity information and access address; determines the user's access permission level according to the set unified permission verification rules and user identity information, and when the access permission level is the preset access permission level, queries the loading address matching the access address in the set routing table, and loads the application data of the sub-application based on the queried loading address; calls the application data based on the preset communication mechanism, and sends the application data to the client, which is used for the client to perform sub-application management operations based on the application data, and the application data is the public component data obtained based on the public component development of each sub-application. The user's authority can be verified according to the set unified permission verification rules, which improves the management efficiency of the access permissions of each sub-application and ensures the security of the data of each sub-application. After the user's authority verification is passed, the loading address is matched according to the routing table, so as to load the corresponding sub-application data based on the loading address, and the unified management platform can be realized. Unified management of each sub-application can be achieved, avoiding the developer from switching between the various sub-application entrances when managing each sub-application, reducing the complexity of application management, and correspondingly improving the management efficiency of the application, and reducing the development and maintenance costs of each sub-application. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 is a flowchart of a method for acquiring sub-application data based on a unified management platform provided in an embodiment of the present application;

[0035] Figure 2 is a flow chart of an application data sharing method provided in an embodiment of the present application;

[0036] Figure 3 is a flow chart of a method for determining a user access rights level provided in an embodiment of the present application;

[0037] Figure 4 is a flow chart of a historical data binding method provided by an embodiment of the present application;

[0038] Figure 5 It is a structural diagram of a sub-application data acquisition device based on a unified management platform provided in an embodiment of the present application;

[0039] Figure 6 It is a structural diagram of a sub-application data acquisition device based on a unified management platform provided in an embodiment of the present application. DETAILED DESCRIPTION

[0040] In order to make the purpose, technical scheme and advantages of the present application clearer, the specific embodiments of the present application are further described in detail below in conjunction with the accompanying drawings. It is understood that the specific embodiments described herein are only used to explain the present application, rather than to limit the present application. It should also be noted that, for the convenience of description, only part of the present application is shown in the accompanying drawings, but not all of the content. Before discussing the exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flow charts. Although the flow chart describes each operation (or step) as a sequential process, many of the operations therein can be implemented in parallel, concurrently or simultaneously. In addition, the order of the operations can be rearranged. The process can be terminated when its operation is completed, but it can also have additional steps not included in the accompanying drawings. The process can correspond to a method, a function, a procedure, a subroutine, a subprogram, etc.

[0041] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the present application belong to the scope of protection of this application.

[0042] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0043] The following, in conjunction with the accompanying drawings, describes in detail the sub-application data acquisition method and device based on the unified management platform provided by the embodiment of the present application through specific embodiments and their application scenarios.

[0044] The embodiments of the present application can be applied to the scenario of managing multiple remote sub-applications. By designing a unified application management platform, after logging into the unified management platform, developers can obtain the data of remote sub-applications by clicking the corresponding sub-application identification component on the terminal page, and develop, deploy and maintain the corresponding sub-applications through the obtained application data. Based on the above usage scenarios, it can be understood that the execution subject of this solution can be the unified management platform.

[0045] Figure 1 is a flowchart of a method for acquiring sub-application data based on a unified management platform provided in an embodiment of the present application, such as Figure 1 As shown, including:

[0046] Step S101: receiving access request information sent by a client, wherein the access request information includes user identity information and an access address.

[0047] The access request information may be a request message sent by a developer by clicking on a corresponding sub-application identifier on a client page, and the access request message may be used to request application data of a remote sub-application. The access request message may include an identifier of the sub-application, which may be a graphic identifier or an ID. Optionally, the access request message includes user identity information and an access address. The user identity information may be a login account and account password used by a developer when logging into the unified management platform, or may be the developer's face recognition information and an input login password. The access address may be the current location information of the sub-application, such as the name of a folder storing sub-application data.

[0048] Step S102: determine the user's access permission level based on the set unified permission verification rules and the user identity information. When the access permission level is the preset access permission level, query the loading address matching the access address in the set routing table, and load the application data of the sub-application based on the queried loading address.

[0049] Among them, the unified permission verification rule is a rule for judging the management authority of the sub-application based on the user identity information after the unified management platform is built. The developer needs to comply with the unified permission verification rule when obtaining any sub-application data. The unified permission verification rule may include permission rules for reading sub-application data, permission rules for rewriting sub-application data, and permission rules for deleting sub-application data. The access permission level can be used to indicate the executable scope of the developer to the sub-application data. The higher the access permission level, the greater the executable scope of the developer to the sub-application data. Exemplarily, if it is the first permission level, the developer can read the sub-application data, if it is the second permission level, the developer can read the sub-application data, and can also rewrite the sub-application data, if it is the third permission level, the developer can read the sub-application data, and can also rewrite and delete the sub-application data. The preset access permission level is a pre-set access permission level that includes the sub-application loading permission. The routing table is a table for recording the mapping relationship between the sub-application loading address and the sub-application identifier, where the sub-application identifier can be the name of the sub-application. The loading address is used to indicate the current location of the sub-application. The application data of the sub-application may include the content data of the sub-application, application storage data, application configuration data, and application platform data, etc.

[0050] In one embodiment, the developer's access permission level is determined based on a preset unified permission verification rule and the received user identity information, and it is determined whether the access permission level includes the sub-application loading permission. If the access permission level includes the sub-application loading permission, the address that is the same as the received access address is searched in a preset routing table, and the found address is determined as the sub-application loading address. The sub-application data in the loading address is loaded through the loading module in the unified management platform.

[0051] Step S103, calling the application data based on a preset communication mechanism, and sending the application data to the client, so that the client can perform management operations of sub-applications based on the application data, wherein the application data is common component data developed based on common components of each sub-application.

[0052] The communication mechanism can realize a method of transmitting information or sharing data between different hosts or between different modules of the same host. The communication mechanism may include shared memory and semaphores, etc. Among them, shared memory is an efficient communication method that can realize data sharing between multiple processes. Semaphores are a mechanism for synchronization or mutual exclusion between processes, which can be used for shared resource management between multiple processes, and can be used to synchronize processes, avoid competition and conflict between processes, and thus ensure the correctness and consistency between processes. In one embodiment, the loaded sub-application data is called by the communication module in the unified management platform, and the sub-application data obtained by the call is sent to the client, so that the developer can perform operations such as development, deployment or maintenance of the sub-application according to the application data received by the client. Optionally, the application data is the public component data obtained by the development of the public components of each sub-application. The public component data includes the components of the application interface and the storage data, configuration data, etc. associated with each component. Exemplarily, the developer can obtain the data associated with the component by clicking on the component displayed on the client page, and realize the development or maintenance of the sub-application by managing the associated data. In one embodiment, since the component type of each sub-application is a unified component type developed by the language according to the same component rule, the component type loaded into each application data is the same, but the data associated with each component in different sub-applications is different. In one possible embodiment, after the unified application management platform is built, the developer extracts the common components of each sub-application, and develops a set of unified common components based on the extracted common components, and applies the unified common components to each sub-application, so as to achieve a consistent page style for each sub-application, facilitate the management operation of each sub-application by the developer, and thus improve the management efficiency of the sub-application.

[0053] In the above, by receiving the access request information sent by the client, the access request information includes the user identity information and the access address; determining the user's access permission level according to the set unified permission verification rules and the user identity information, when the access permission level is the preset access permission level, querying the loading address matching the access address in the set routing table, and loading the application data of the sub-application based on the queried loading address; calling the application data based on the preset communication mechanism, sending the application data to the client, for the client to perform sub-application management operations based on the application data, and the application data is the public component data obtained based on the public component development of each sub-application. The user's authority can be verified according to the set unified permission verification rules, which improves the management efficiency of the access permissions of each sub-application and ensures the security of the data of each sub-application. After the user's authority verification is passed, the loading address is matched according to the routing table, so as to load the corresponding sub-application data based on the loading address, which can realize the unified management of each sub-application by the unified management platform, avoid the developer needing to switch between the various sub-application entrances to obtain the data of each sub-application when managing the entry of each sub-application, reduce the complexity of application management, and correspondingly improve the management efficiency of the application, and reduce the development and maintenance cost of each sub-application.

[0054] In one embodiment, after receiving the access request information sent by the client, the method further includes:

[0055] A query is made in the user operation record table as to whether there is historical identity information matching the user identity information. If there is historical identity information matching the user identity information, the operation data corresponding to the historical identity information is loaded based on the binding relationship between the historical identity information and the most recent operation data.

[0056] Among them, the user operation record table is used to record the management operation data and corresponding operation time of each developer on the sub-application through the client in history. The user operation record table may include historical user identity information and the sub-application identifier and sub-application operation data corresponding to the historical user identity information. Among them, the sub-application operation data may include the development data and maintenance data of the sub-application. The most recent operation data is the data generated by the developer's most recent operation on a sub-application recorded in the user operation record table. In one embodiment, after receiving the user identity information and access address sent by the client, the operation record table is searched to see whether there is historical identity information that is the same as the user identity information. If so, all operation data and operation time bound to the historical identity information found are searched in the user operation record table, and the operation data closest to the current time is determined according to the operation time, and the operation data closest to the current time is loaded through the loading module.

[0057] As described above, by querying whether there is historical identity information matching the user identity information in the user operation record table, if there is historical identity information matching the user identity information, then based on the binding relationship between the historical identity information and the most recent operation data, the operation data corresponding to the historical identity information is loaded. Based on the binding relationship between the historical identity information and the operation data in the user operation record, the data that the developer may need can be quickly loaded, thereby improving the efficiency of obtaining application data and correspondingly improving the developer's experience.

[0058] In one embodiment, before receiving the access request information sent by the client, the method further includes:

[0059] A plurality of sub-application identifiers are set on a client page according to the access address exposed by the sub-application, so that the client can send access request information by selecting the sub-application identifier, wherein the sub-application identifier is associated with the access address of the sub-application.

[0060] The sub-application identifier can be an icon displayed on the client page. In one embodiment, the unified management platform predetermines the sub-applications that need to be managed, sets application icons for different sub-applications, and associates the application icons with the access addresses of the corresponding sub-applications. The developer obtains the access address associated with the application icon by clicking the corresponding application icon on the client page, and sends the access address to the unified management platform together with the user identity information used when logging into the unified management platform, requesting the unified management platform to return the sub-application data corresponding to the access address.

[0061] As described above, setting multiple sub-application identifiers on the client page according to the access addresses exposed by the sub-applications enables developers to directly select the sub-applications that need to be managed on the terminal page after logging into the unified management platform, avoiding obtaining the data of each sub-application by switching between the various sub-application entrances, reducing the complexity of application management and improving application management efficiency.

[0062] Figure 2 is a flow chart of an application data sharing method provided in an embodiment of the present application, such as Figure 2 As shown, including:

[0063] Step S201: determine the amount of shared data identified in the application data, and when the amount of shared data is greater than a preset sharing threshold, send the shared data to each sub-application based on a message queue communication mechanism.

[0064] Among them, shared data is non-sensitive data that can be shared with other sub-applications. Shared data can be determined by querying the data marked with a shared identifier in the application data, or a shared data file can be established during the development of the sub-application, and the shared data is stored separately in the shared data file. The preset sharing threshold is determined based on the historical data transmission rate. The higher the historical data transmission rate, the larger the preset sharing threshold. Conversely, the lower the historical data transmission rate, the smaller the preset sharing threshold. By setting the sharing threshold, it is possible to ensure that all loaded application data are called in a shorter time. The message queue communication mechanism can realize asynchronous message transmission through a storage and forwarding mechanism, allowing various parts of the system to process messages at different times, and can balance the load in high concurrency situations to prevent system overload. In one embodiment, the amount of shared data is determined by obtaining the data marked with a shared identifier in the application, and the amount of shared data is compared with the preset sharing threshold. If the amount of shared data is greater than the sharing threshold, the loaded application data is called based on the message queue communication mechanism and the application data is sent to other sub-applications to avoid system overload affecting the efficiency of calling application data.

[0065] Step S202: When the amount of the shared data is less than or equal to a preset sharing threshold, the shared data is sent to each sub-application based on a full-duplex communication mechanism.

[0066] Among them, the full-duplex communication mechanism can be WebSocket, which is used for real-time notification and real-time data push, but due to its characteristic of maintaining continuous connection, it will face greater pressure when a large amount of data needs to be transmitted at the same time. In one embodiment, the data volume of the shared data is determined after obtaining the data marked by the shared identifier in the application, and the data volume of the shared data is compared with the preset shared threshold. If the data volume of the shared data is less than or equal to the shared threshold, the loaded application data is called based on the full-duplex communication mechanism and the application data is sent to other sub-applications, which can reduce network delay and ensure the calling efficiency of loading application data.

[0067] In the above, by determining the number of shared data identified in the application data, when the number of shared data is greater than the preset sharing threshold, the shared data is sent to each sub-application based on the message queue communication mechanism; when the number of shared data is less than or equal to the preset sharing threshold, the shared data is sent to each sub-application based on the full-duplex communication mechanism. By determining the number of shared data and selecting different communication mechanisms according to the number of shared data and the characteristics of each communication mechanism, the efficiency of calling the loaded application data is guaranteed, network delays or system overloads are avoided, and the unified management platform can realize both independent management of each sub-application and data sharing between sub-applications.

[0068] Figure 3 is a flow chart of a method for determining a user access right level provided in an embodiment of the present application. Figure 3 As shown, including:

[0069] Step S301: when the user identity information is a mobile phone number and a verification code, and the mobile phone number and the verification code meet security verification conditions, determine that the user's access authority level is a first-level access authority, and the first-level access authority includes login authority.

[0070] Among them, the user identity information can be the information entered by the developer when logging into the unified management platform, and the user identity information can be a login password. Optionally, the user identity information can also be a mobile phone number and a verification code. In one embodiment, if the received user identity information is a mobile phone number and a verification code, the mobile phone number and the verification code are security verified, wherein the specific verification method is a conventional verification method, which is not described here. If the mobile phone number and the verification code meet the security verification conditions, the developer's access permission level is considered to be a login permission, that is, the developer can log in to the unified management platform, view the sub-application identifier displayed on the client page, and determine which sub-applications the unified management platform can manage.

[0071] Step S302: When the user identity information is a login account and a login password, and the login account and the login password match the login account and the login password stored in the database, determine that the user's access permission level is a secondary access permission, and the secondary access permission includes a sub-application loading permission.

[0072] Among them, the sub-application loading permission may refer to the developer being able to log in to the unified management platform and click on the corresponding sub-application logo on the client page to send access request information to the server of the unified management platform, so that the unified management platform can load the corresponding sub-application data. In one embodiment, if the received user identity information is a login account and login password, the login account and login password are matched with the data login account and login password stored in the database. If the match is successful, it is considered that the developer has the sub-application loading permission, that is, the developer can send a sub-application data acquisition request and receive the loading data returned by the server.

[0073] Step S303: when the user identity information is biometric information and the biometric information matches the biometric information stored in the database, determine that the user's access permission level is a third-level access permission, and the third-level access permission includes sub-application loading permission and development and deployment permission.

[0074] Among them, biometric information is an inherent part of a person's identity and may include fingerprints, faces, irises, and palm prints. The client can determine the identity of the developer by identifying the developer's biometric information. Development and deployment permissions may refer to the developer's ability to log in to the unified management platform and send access request information to the server of the unified management platform by clicking the corresponding sub-application logo on the client page, so that the unified management platform can load the corresponding sub-application data, and can also perform any management operations such as development, deployment, and maintenance of sub-applications on the acquired application data. In one embodiment, if the received user identity information is biometric information, the biometric information is matched with the biometric information pre-stored in the database. If the match is successful, it is considered that the developer has the development and deployment permissions for the sub-application, that is, the developer can perform any management operations such as development, deployment, and maintenance on the received sub-application data.

[0075] In the above, when the user identity information is a mobile phone number and a verification code, and when the mobile phone number and the verification code meet the security verification conditions, the user's access permission level is determined to be login permission; when the user identity information is a login account and a login password, and the login account and the login password match the login account and the login password stored in the database, the user's access permission level is determined to be sub-application loading permission; when the user identity information is biometric information, and the biometric information matches the biometric information stored in the database, the user's access permission level is determined to be sub-application development and deployment permission. The role or permission of the developer can be determined based on the type of user identity information received, which fully guarantees the security of each sub-application data. In addition, the unified management platform enables each sub-application to adopt the same permission judgment rules, which facilitates the permission management of each sub-application.

[0076] Figure 4 is a flowchart of a historical data binding method provided by an embodiment of the present application, such as Figure 4 As shown, including:

[0077] Step S401: Count the number of times each application data is received within a preset time interval, and determine whether the number of times each application data is received exceeds a preset access number.

[0078] Step S402: When the number of times the application data is received exceeds the preset number of accesses, query the corresponding user operation record based on the application data, bind the most recent operation data in the user operation record with the user's historical identity information, and mark it in the user operation record.

[0079] In one embodiment, after calling the application data based on a preset communication mechanism, the number of times each sub-application data is loaded within a preset time period is counted. If the number of loads exceeds the preset number of accesses, it proves that the developer frequently obtains the application data of the sub-application. The user operation record is searched for the most recent operation data corresponding to the currently received user identity information, and the most recent operation data is bound to the user's historical identity information. The binding relationship is marked in the user operation record, so that when the access request information sent by the client is received again, the most recent operation data can be directly loaded based on the marked binding relationship, thereby improving the efficiency of obtaining application data, and can also increase the operating efficiency of developers accordingly, thereby improving the developer's experience.

[0080] In one embodiment, after counting the number of times each application data is received within the preset time interval, the method further includes:

[0081] A user access statistics table is generated according to the number of times each application data is received, and the user access statistics table is sent to the client.

[0082] As mentioned above, by generating an access statistics table based on the number of times each sub-application data is obtained within a preset time interval, and sending it to the client for display, maintenance personnel can quickly understand the access status of each sub-application data, thereby checking and maintaining sub-applications with abnormal or frequent access, thereby ensuring the security of sub-application data.

[0083] Figure 5 is a structural diagram of a sub-application data acquisition device based on a unified management platform provided in an embodiment of the present application, such as Figure 5 As shown, including:

[0084] The routing module 51 is used to receive access request information sent by the client, wherein the access request information includes user identity information and access address;

[0085] The permission module 52 is used to determine the user's access permission level according to the set unified permission verification rules and the user identity information;

[0086] The routing module 51 is further configured to query a loading address matching the access address in a set routing table when the access permission level is a preset access permission level;

[0087] An application loading module 53, used to load application data of the sub-application based on the queried loading address;

[0088] The communication module 54 is used to call the application data based on a preset communication mechanism and send the application data to the client, so that the client can perform management operations on sub-applications based on the application data. The application data is public component data developed based on public components of each sub-application.

[0089] The embodiment of the present application receives access request information sent by the client, and the access request information includes user identity information and access address; determines the user's access permission level according to the set unified permission verification rules and user identity information, and when the access permission level is the preset access permission level, queries the loading address matching the access address in the set routing table, and loads the application data of the sub-application based on the queried loading address; calls the application data based on the preset communication mechanism, and sends the application data to the client, which is used for the client to perform sub-application management operations based on the application data, and the application data is the public component data obtained based on the public component development of each sub-application. The user's authority can be verified according to the set unified permission verification rules, which improves the management efficiency of the access permissions of each sub-application and ensures the security of the data of each sub-application. After the user's authority verification is passed, the loading address is matched according to the routing table, so as to load the corresponding sub-application data based on the loading address, and the unified management platform can be realized. Unified management of each sub-application can be achieved, avoiding the developer from switching between the various sub-application entrances when managing each sub-application, reducing the complexity of application management, and correspondingly improving the management efficiency of the application, and reducing the development and maintenance costs of each sub-application.

[0090] In a possible embodiment, the communication module 54 is used to:

[0091] Determine the amount of shared data identified in the application data, and if the amount of shared data is greater than a preset sharing threshold, send the shared data to each sub-application based on a message queue communication mechanism;

[0092] When the amount of the shared data is less than or equal to a preset sharing threshold, the shared data is sent to each sub-application based on a full-duplex communication mechanism.

[0093] In a possible embodiment, the permission module 52 is used to:

[0094] When the user identity information is a mobile phone number and a verification code, and the mobile phone number and the verification code meet the security verification conditions, determining that the user's access authority level is a first-level access authority, and the first-level access authority includes a login authority;

[0095] When the user identity information is a login account and a login password, and the login account and the login password match the login account and the login password stored in the database, determining that the user's access permission level is a secondary access permission, and the secondary access permission includes a sub-application loading permission;

[0096] When the user identity information is biometric information and the biometric information matches the biometric information stored in the database, it is determined that the user's access permission level is a third-level access permission, and the third-level access permission includes a sub-application loading permission and a development and deployment permission.

[0097] In a possible embodiment, the binding module is used to:

[0098] Counting the number of times each application data is received within a preset time interval, and determining whether the number of times each application data is received exceeds a preset access number;

[0099] When the number of times the application data is received exceeds the preset number of accesses, the corresponding user operation record is queried based on the application data, the most recent operation data in the user operation record is bound to the user's historical identity information, and marked in the user operation record.

[0100] In a possible embodiment, the statistical table generating module is used to:

[0101] A user access statistics table is generated according to the number of times each application data is received, and the user access statistics table is sent to the client.

[0102] In a possible embodiment, the application loading module 53 is used to:

[0103] A query is made in the user operation record table as to whether there is historical identity information matching the user identity information. If there is historical identity information matching the user identity information, the operation data corresponding to the historical identity information is loaded based on the binding relationship between the historical identity information and the most recent operation number.

[0104] In a possible embodiment, the application identification setting module is used to:

[0105] A plurality of sub-application identifiers are set on a client page according to the access address exposed by the sub-application, so that the client can send access request information by selecting the sub-application identifier, wherein the sub-application identifier is associated with the access address of the sub-application.

[0106] The embodiment of the present application also provides a sub-application data acquisition device based on a unified management platform, and the sub-application data acquisition device based on a unified management platform can be integrated with a sub-application data acquisition apparatus based on a unified management platform provided in the embodiment of the present application. Figure 6 This is a schematic diagram of the structure of a sub-application data acquisition device based on a unified management platform provided in an embodiment of the present application, with reference to Figure 6 The sub-application data acquisition device based on the unified management platform includes: an input device 63, an output device 64, a memory 62 and one or more processors 61; the memory 62 is used to store one or more programs; when one or more programs are executed by one or more processors 61, the one or more processors 61 implement the sub-application data acquisition method based on the unified management platform provided in the above embodiment. The input device 63, the output device 64, the memory 62 and the processor 61 can be connected via a bus or other means. Figure 6 The example of connecting through bus is taken in the following.

[0107] The memory 62, as a computing device readable storage medium, can be used to store software programs, computer executable programs and modules, such as the program instructions / modules corresponding to the sub-application data acquisition method based on the unified management platform provided in any embodiment of the present application. The memory 62 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the device, etc. In addition, the memory 62 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 62 may further include a memory remotely arranged relative to the processor 61, and these remote memories may be connected to the device 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.

[0108] The input device 63 may be used to receive input digital or character information and generate key signal input related to user settings and function control of the device. The output device 64 may include a display device such as a display screen.

[0109] The processor 61 executes various functional applications and data processing of the device by running the software programs, instructions and modules stored in the memory 62, that is, implements the above-mentioned sub-application data acquisition method based on the unified management platform.

[0110] The above-mentioned sub-application data acquisition device, equipment and computer based on the unified management platform can be used to execute the sub-application data acquisition method based on the unified management platform provided in any of the above-mentioned embodiments, and have corresponding functions and beneficial effects.

[0111] The present application also provides a storage medium storing computer executable instructions. When the computer executable instructions are executed by a computer processor, they are used to execute the sub-application data acquisition method based on the unified management platform provided in the above embodiment. The sub-application data acquisition method based on the unified management platform includes:

[0112] Receive access request information sent by the client, wherein the access request information includes user identity information and access address;

[0113] Determine the user's access permission level according to the set unified permission verification rule and the user identity information, and when the access permission level is the preset access permission level, query the set routing table for a loading address that matches the access address, and load the application data of the sub-application based on the queried loading address;

[0114] The application data is called based on a preset communication mechanism and sent to the client, so that the client can perform management operations on sub-applications based on the application data. The application data is common component data developed based on common components of each sub-application.

[0115] Storage medium - any of various types of memory devices or storage devices. The term "storage medium" is intended to include: installation media, such as CD-ROM, floppy disk or tape device; computer system memory or random access memory, such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory, such as flash memory, magnetic media (such as hard disk or optical storage); registers or other similar types of memory elements, etc. Storage media may also include other types of memory or combinations thereof. In addition, the storage medium may be located in the first computer system in which the program is executed, or may be located in a different second computer system, which is connected to the first computer system via a network (such as the Internet). The second computer system can provide program instructions to the first computer for execution. The term "storage medium" may include two or more storage media that may reside in different locations (for example, in different computer systems connected by a network). The storage medium may store program instructions (for example, embodied as a computer program) that can be executed by one or more processors.

[0116] Of course, the storage medium containing computer executable instructions provided in an embodiment of the present application, whose computer executable instructions are not limited to the sub-application data acquisition method based on a unified management platform as described above, can also execute related operations in the sub-application data acquisition method based on a unified management platform provided in any embodiment of the present application.

[0117] The sub-application data acquisition apparatus, device and storage medium based on a unified management platform provided in the above embodiments can execute the sub-application data acquisition method based on a unified management platform provided in any embodiment of the present application. For technical details not described in detail in the above embodiments, please refer to the sub-application data acquisition method based on a unified management platform provided in any embodiment of the present application.

[0118] The above are only preferred embodiments of the present application and the technical principles used. The present application is not limited to the specific embodiments described herein, and various obvious changes, readjustments and substitutions that can be made by those skilled in the art will not deviate from the scope of protection of the present application. Therefore, although the present application is described in more detail through the above embodiments, the present application is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present application, and the scope of the present application is determined by the scope of the claims.

Claims

1. A method for acquiring sub-application data based on a unified management platform, characterized in that: include: Receive access request information sent by a client, the access request information including user identity information and an access address, query whether there is historical identity information matching the user identity information in a user operation record table, and if there is historical identity information matching the user identity information, load operation data corresponding to the historical identity information based on a binding relationship between the historical identity information and the most recent operation data; Determine the user's access permission level according to the set unified permission verification rule and the user identity information, and when the access permission level is the preset access permission level, query the set routing table for a loading address that matches the access address, and load the application data of the sub-application based on the queried loading address; Calling the application data based on a preset communication mechanism, and sending the application data to the client, so that the client performs management operations of sub-applications based on the application data, wherein the application data is common component data developed based on common components of each sub-application; The determining of the user's access permission level based on the set unified permission verification rules and the user identity information includes: determining the first-level access permission based on the mobile phone number, verification code and unified permission verification rules, the first-level access permission includes login permission, determining the second-level access permission based on the login account, login password and the unified permission verification rules, the second-level access permission includes sub-application loading permission, and determining the third-level access permission based on biometric information and the unified permission verification rules, the third-level access permission includes sub-application loading permission and development and deployment permission.

2. The sub-application data acquisition method based on a unified management platform according to claim 1, characterized in that: After the application data of the sub-application is loaded based on the queried loading address, the method further includes: Determine the amount of shared data identified in the application data, and if the amount of shared data is greater than a preset sharing threshold, send the shared data to each sub-application based on a message queue communication mechanism; When the amount of the shared data is less than or equal to a preset sharing threshold, the shared data is sent to each sub-application based on a full-duplex communication mechanism.

3. The sub-application data acquisition method based on a unified management platform according to claim 1, characterized in that: The preset access permission levels include level one access permission, level two access permission and level three access permission, and the user's access permission level is determined according to the set unified permission verification rules and the user identity information, including: When the user identity information is a mobile phone number and a verification code, and the mobile phone number and the verification code meet security verification conditions, determining that the user's access permission level is a first-level access permission; When the user identity information is a login account and a login password, and the login account and the login password match the login account and the login password stored in the database, determining that the user's access authority level is a second-level access authority; When the user identity information is biometric information and the biometric information matches the biometric information stored in the database, it is determined that the user's access permission level is a third-level access permission.

4. The sub-application data acquisition method based on a unified management platform according to claim 1, characterized in that: After sending the application data to the client, the method further includes: Counting the number of times each application data is received within a preset time interval, and determining whether the number of times each application data is received exceeds a preset access number; When the number of times the application data is received exceeds the preset number of accesses, the corresponding user operation record is queried based on the application data, the most recent operation data in the user operation record is bound to the user's historical identity information, and marked in the user operation record.

5. The sub-application data acquisition method based on a unified management platform according to claim 4, characterized in that: After counting the number of times each application data is received within the preset time interval, the method further includes: A user access statistics table is generated according to the number of times each application data is received, and the user access statistics table is sent to the client.

6. The sub-application data acquisition method based on a unified management platform according to claim 1, characterized in that: Before receiving the access request information sent by the client, the method further includes: A plurality of sub-application identifiers are set on a client page according to the access address exposed by the sub-application, so that the client can send access request information by selecting the sub-application identifier, wherein the sub-application identifier is associated with the access address of the sub-application.

7. A sub-application data acquisition device based on a unified management platform, characterized in that: include: A routing module, used to receive access request information sent by a client, wherein the access request information includes user identity information and an access address; An application loading module, used to query whether there is historical identity information matching the user identity information in the user operation record table, and if there is historical identity information matching the user identity information, load the operation data corresponding to the historical identity information based on the binding relationship between the historical identity information and the most recent operation data; A permission module, used to determine the user's access permission level according to the set unified permission verification rules and the user identity information, the permission module is specifically used to determine the first-level access permission according to the mobile phone number, the verification code and the unified permission verification rules, the first-level access permission includes the login permission, the second-level access permission is determined according to the login account, the login password and the unified permission verification rules, the second-level access permission includes the sub-application loading permission, the third-level access permission is determined according to the biometric information and the unified permission verification rules, the third-level access permission includes the sub-application loading permission and the development and deployment permission; The routing module is further configured to query a set routing table for a loading address matching the access address when the access permission level is a preset access permission level; The application loading module is further used to load the application data of the sub-application based on the queried loading address; A communication module is used to call the application data based on a preset communication mechanism and send the application data to the client, so that the client can perform management operations on sub-applications based on the application data. The application data is public component data developed based on public components of each sub-application.

8. A sub-application data acquisition device based on a unified management platform, the device comprising: one or more processors; A storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the sub-application data acquisition method based on a unified management platform as described in any one of claims 1-6.

9. A storage medium storing computer executable instructions, wherein the computer executable instructions, when executed by a computer processor, are used to execute the sub-application data acquisition method based on a unified management platform as described in any one of claims 1 to 6.

Images