A webpage interface loading method, an electronic device, and a storage medium

Abstract

The application discloses a webpage interface loading method, an electronic device and a storage medium, and the method comprises the following steps: acquiring at least one user contained in a target project, and configuring a binding relationship between each user and at least one corresponding role, and then configuring a binding relationship between each role and at least one corresponding workbench in a workbench warehouse; a plurality of workbenches stored in the workbench warehouse are obtained by prearranging a plurality of business widgets according to preset business requirements, and each workbench is configured to be bound with part of the roles; in response to a login request of a target user in the target project, a target workbench of the target user is determined by using the binding relationship, and then the loading of the webpage interface is completed by using the target workbench; in the application, the user and the workbench realize a many-to-many relationship, the differentiated requirements of a mass business scene on the webpage interface are met, the project is quickly delivered, the development cost is reduced, and the work efficiency is improved.

Description

Technical Field

[0001] This application relates to the technical field of differentiated user interfaces, and in particular to a web page interface loading method, electronic device, and storage medium. Background Technology

[0002] With the explosive growth of computer applications, the Internet of Things (IoT) has entered a stage of rapid development of full-scenario IoT, with more and more multi-dimensional sensing devices and rich services being loaded onto IoT management platforms, such as video, access control, parking, facial recognition, attendance, fire protection, and alarm control panels.

[0003] However, in the process of implementing the baseline IoT management platform across various industries, significant differences exist in the usage scenarios and concerns of different industries, positions, users, and projects. Firstly, different industries differ due to variations in perception methods and business scenarios. Secondly, different users have different concerns and display style requirements. Furthermore, different projects differ due to varying management standards and the scope of business managed by users. Moreover, IoT platform vendors typically employ custom development to address deviations between projects and the baseline, which is time-consuming, labor-intensive, and costly, while failing to address the pain point of different industries and users wanting a core working interface more suited to their specific scenarios. Therefore, how to meet the differentiated needs of massive business scenarios for core working interfaces, achieve rapid project delivery, reduce development costs, and ultimately improve work efficiency is a technical problem that needs to be solved. Summary of the Invention

[0004] This application mainly addresses the current technical problems through the following technical solutions, providing a web page interface loading method, electronic device, and storage medium. By binding each user in the target project to at least one role, and configuring each role to be bound to at least one workbench, a many-to-many relationship between users and workbench is achieved. This meets the differentiated needs of web page interfaces in a large number of business scenarios, effectively enables rapid project delivery, reduces development costs, and improves work efficiency.

[0005] To address the aforementioned technical problems, this application provides a webpage interface loading method, comprising: acquiring at least one user included in a target project, configuring a binding relationship between each user and at least one corresponding role, and further configuring a binding relationship between each role and at least one corresponding workbench in a workbench repository; wherein, the workbench repository stores a plurality of workbenches pre-arranged using preset business requirements, and each workbench is configured to be bound to a subset of roles; the roles are used to represent the identity or function of a set of related permissions; in response to a login request from a target user in the target project, the target workbench of the target user is determined using the binding relationship, and the webpage interface is loaded using the target workbench.

[0006] In some embodiments, obtaining at least one user included in the target project and configuring the binding relationship between each user and at least one corresponding role, and then configuring the binding relationship between each role and at least one corresponding workbench in the workbench repository, includes: obtaining at least one user included in the target project; configuring a first binding relationship between each user and at least one corresponding role; using the role, selecting at least one bindable workbench from the workbench repository, and then configuring a second binding relationship between each role and at least one workbench; using the first binding relationship and the second binding relationship, determining the binding relationship between each user and at least one workbench through each role, and setting it as a first type of binding relationship.

[0007] In some embodiments, the method further includes: using preset business requirements, pre-selecting a plurality of corresponding business widgets from a business widget library for arrangement, generating a workbench that matches the preset business requirements, and thereby obtaining a plurality of workbench stored in the workbench warehouse, wherein the arranged workbench includes at least: workbench basic information, workbench layout information, and business widget list information.

[0008] In some embodiments, the binding relationship is determined through a first binding relationship and a second binding relationship, and the binding relationship is a first type binding relationship, wherein the first binding relationship represents the binding between the user and the role, and the second binding relationship represents the binding between the role and at least one workbench in the workbench repository; the step of determining the target workbench of the target user using the binding relationship in response to a login request of the target user in the target project includes: in response to the login request, determining the target user in the target project corresponding to the login request; determining the target role corresponding to the target user using the first binding relationship; determining the target workbench corresponding to the target role using the second binding relationship, and then using the target workbench corresponding to the target role as the target workbench of the target user.

[0009] In some embodiments, before determining the target role corresponding to the target user using the first binding relationship, the method further includes: in response to the existence of a third binding relationship for the user, selecting at least one workbench from the workbench repository as the target workbench for the user using the third binding relationship, and setting it as a second type of binding relationship, wherein the third binding relationship represents the binding of the user to at least one workbench in the workbench repository; and in response to a login request, loading the web page interface using the target workbench.

[0010] In some embodiments, the method further includes: the workbench includes a first type of workbench and a second type of workbench, wherein the priority of the first type of workbench is greater than the priority of the second type of workbench; determining the target role corresponding to the target user using the first binding relationship includes: in response to the target user not having a second type of binding relationship, determining the target role corresponding to the target user using the first binding relationship; determining the target workbench corresponding to the target role using the second binding relationship includes: in response to the target role being bound to multiple workbenches, determining the target workbench corresponding to the target role using loading priority and the second binding relationship, wherein the loading priority represents the current business focus of the target user; or in response to the target role being bound to only one workbench, the target role is associated with the workbench, and the associated workbench is loaded as the target workbench, wherein the workbench bound to the target role is a second type of workbench, and the target workbench of the user determined by the second type of binding relationship is a first type of workbench.

[0011] In some embodiments, the method further includes customizing a workbench for a target user or target role and directly binding it, wherein the workbench customized for the target user is a first type of workbench.

[0012] In some embodiments, the workbench further includes: the workbench also includes a third type of workbench, the third type of workbench being the base workbench, wherein the priority of the second type of workbench is greater than the priority of the third type of workbench; the user can also use the business module entry of the third type of workbench to enter the function menu and perform specific business operations.

[0013] In some embodiments, the method further includes: acquiring operation information of business widgets by a target user during the operation of a target workbench, wherein the operation information includes at least click count information, dwell time information, and click order information; using the click count information, the dwell time information, and the click order information to determine the value score and relevance of each business widget; dividing different areas of the target workbench according to the value score to obtain different value score areas; using the value score, the relevance, and the different value score areas to adjust the areas of the business widgets on the target workbench, and loading the adjusted target workbench in response to the user's confirmation of the adjusted target workbench.

[0014] To solve the above-mentioned technical problems, another technical solution adopted in this application is to provide an electronic device, which includes a memory and a processor coupled to the memory. The memory stores at least one computer program, which, when loaded and executed by the processor, is used to implement the web page interface loading method described above.

[0015] To solve the above-mentioned technical problems, another technical solution adopted in this application is to provide a computer-readable storage medium having at least one program, which, when loaded and executed by a processor, is used to implement the web page interface loading method described above.

[0016] Unlike current technologies, the webpage interface loading method provided in this application includes: obtaining at least one user included in the target project, configuring the binding relationship between each user and at least one corresponding role, and then configuring the binding relationship between each role and at least one corresponding workbench in the workbench repository; wherein, the workbench stored in the workbench repository is obtained by pre-arranging multiple business widgets using preset business requirements, and each workbench is configured to be bound to some users; in response to the login request of the target user in the target project, the target workbench of the target user is determined using the binding relationship, and then the webpage interface is loaded using the target workbench; that is, in this application, each user in the target project is bound to at least one role, and each role is bound to at least one workbench, thereby realizing a many-to-many relationship between users and workbench, meeting the differentiated needs of webpage interfaces for massive business scenarios, effectively achieving rapid project delivery, reducing development costs, and improving work efficiency for different projects. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. Wherein:

[0018] Figure 1 This is a flowchart illustrating an embodiment of the webpage interface loading method in this application;

[0019] Figure 2 This is a schematic diagram of the structure of an embodiment of the physical management platform in this application;

[0020] Figure 3 This is a schematic diagram of the structure of an embodiment of the association model in this application;

[0021] Figure 4 This is a schematic flowchart of an embodiment of workbench loading in this application;

[0022] Figure 5 This is a schematic diagram of the structure of an embodiment of the web page loading system in this application;

[0023] Figure 6 This is a schematic diagram of the structure of an embodiment of the electronic device in this application;

[0024] Figure 7 This is a schematic diagram of an embodiment of a computer-readable storage medium in this application. Detailed Implementation

[0025] The present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be particularly noted that the following embodiments are for illustrative purposes only and do not limit the scope of the invention. Similarly, the following embodiments are only some, not all, embodiments of the present invention, and all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0026] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of the invention. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0027] IoT management platform vendors typically adopt a project-based custom development approach to address the discrepancies between baseline products and specific projects. This involves custom development tailored to the different scenarios and concerns of various industries, users, and projects. However, this approach is time-consuming, labor-intensive, and costly, and it also fails to address the pain point of different industries and users using a work interface that is more suitable for their specific scenarios.

[0028] Therefore, a web page interface loading method is provided, in which each user in the target project is bound to at least one role, and each role is bound to at least one workbench, thereby realizing a many-to-many relationship between users and workbench, meeting the differentiated needs of web page interfaces for massive business scenarios, and effectively enabling rapid project delivery, reducing development costs, and improving work efficiency for different projects.

[0029] Please see Figure 1 , Figure 1 This is a flowchart illustrating an embodiment of the webpage interface loading method in this application; it should be noted that, if there are substantial results, the method of this application does not necessarily reflect the actual webpage interface loading method. Figure 1 The sequence of processes shown is limited.

[0030] like Figure 1 As shown, the web page loading method may include the following steps.

[0031] S10. Obtain at least one user included in the target project, and configure the binding relationship between each user and at least one corresponding role, and then configure the binding relationship between each role and at least one corresponding workbench in the workbench repository; wherein, the workbench stored in the workbench repository is obtained by pre-arranging multiple business widgets using preset business requirements; each workbench is configured to be bound to some roles; the role is used to represent the identity or function of a set of related permissions.

[0032] Here, "target project" refers to a specific implementation project. For example, the baseline IoT management platform product can be implemented in projects in the industrial park sector or in the financial sector. "User" refers to the users corresponding to different management scopes under a specific project. For example, the industrial park management platform project can include administrative users, security users, and operation and maintenance users. "Role" refers to an abstract concept in the platform that has a set of related permissions, representing the user's identity or function in a specific context. For example, the administrative role has permissions for access control, attendance services, and equipment, while the security role has permissions for monitoring, alarm services, and equipment. "Workbench" refers to the page that integrates the entry points of commonly used modules of the platform, which is the core working interface after the user logs in. Users can perform common business operations on the workbench.

[0033] Specifically, obtain at least one user included in the target project and configure the binding relationship between each user and at least one corresponding role; then traverse the workbenches stored in the workbench repository and configure the binding relationship between each role in the target project and at least one workbench.

[0034] In some embodiments, the workbench repository pre-stores several workbenches. Each workbench is determined by pre-arranging multiple business widgets according to preset business requirements. When binding is required, each workbench can be configured to be bound to at least one role. That is, the number of roles bound to each workbench is less than the total number of roles in the target project. Here, a business widget refers to a functional module integrated to implement a certain function. Different business requirements correspond to different business widgets and arrangement layouts, thus forming several different workbenches.

[0035] Among them, the preset business requirements can be business needs in a specific scenario, and the relevant content of the business needs can be transformed into the arrangement requirements of business widgets.

[0036] It is understandable that users can bind to the workbench through roles, which is the first type of binding relationship. Users can also bind directly to the workbench, which is the second type of binding relationship. That is, each project can have at least one user, and each user can be configured to bind at least one corresponding role. Therefore, if a user is indirectly bound to the workbench through a role, there is an indirect first type of binding relationship. If a user is directly bound to the workbench, there is a direct second type of binding relationship.

[0037] S20. In response to the login request of the target user in the target project, determine the target user's target workbench using the binding relationship, and then use the target workbench to load the web page interface.

[0038] Specifically, after determining the binding relationship between the role bound to each user in the target project and at least one corresponding workbench in the workbench repository, a login request is received, the target user in the target project is identified, and in response to the login request, the binding relationship can be used to determine the target workbench corresponding to the target user, and then the target workbench can be used to complete the loading of the current web page interface so as to provide the workbench matched to the user to perform relevant tasks.

[0039] In this application, each user in the target project is bound to at least one workbench through a bound role, thereby realizing a many-to-many relationship between users and workbench, meeting the differentiated needs of web interface for massive business scenarios, and effectively enabling rapid project delivery, reducing development costs, and improving work efficiency for different projects.

[0040] In some embodiments, the above-described steps for loading the web interface can be performed through an IoT management platform. The IoT management platform may include modules such as a platform gateway, basic resource management, business subsystems, and high-frequency analysis management.

[0041] See Figure 2 , Figure 2 This is a schematic diagram of the structure of an embodiment of the physical management platform in this application.

[0042] like Figure 2 As shown, the IoT management platform includes modules such as a platform gateway, basic resource management, business subsystems, high-frequency analysis management, and a workbench engine. The platform gateway serves as the unified entry point for the platform, primarily responsible for routing and distributing business requests. Basic resource management provides the IoT management platform's basic data management services, mainly responsible for the unified management of basic data such as devices, organizations, departments, personnel, cards, vehicles, roles, and permissions. Business subsystems are collections of services that implement specific business domain functions, such as video subsystems, access control subsystems, and facial recognition subsystems. High-frequency analysis management is a service that aggregates and analyzes user click and dwell time information. The workbench engine provides workbench management and orchestration services, possessing capabilities such as workbench orchestration, workbench rendering, user binding, business widget development, business widget management, and authorization management.

[0043] Furthermore, the workbench engine also includes a workbench repository, which stores multiple workbenches; and a widget repository, which stores multiple business widgets.

[0044] The IoT management platform can perform the following operations: Workbench orchestration and application: Using business widgets from the business widget repository in the workbench engine, the workbench is orchestrated. Then, the user list is obtained through the basic resource management service interface to complete the binding and associated data storage of the workbench with users or roles; High-frequency information reporting: User clicks and dwell times in business subsystems are reported to the high-frequency analysis management service, which performs data statistics and correlation analysis; Workbench optimization: The workbench engine obtains high-frequency analysis results through the high-frequency analysis management service interface and performs workbench optimization.

[0045] The workbench orchestration module is responsible for functions such as adding, importing / exporting, deleting, copying, and viewing workbenches. A well-organized workbench should include basic workbench information, workbench layout information, and a list of business widgets. This allows for the unified packaging and export of the workbench layout based on the referenced business widget information during export.

[0046] In some embodiments, step S10 obtains at least one user included in the target project and configures the binding relationship between each user and at least one corresponding role, and then configures the binding relationship between each role and at least one corresponding workbench in the workbench repository; wherein, the workbench stored in the workbench repository is obtained by pre-arranging multiple business components using preset business requirements, and each workbench is configured to be bound to some roles, which may include the following operations.

[0047] First, the users included in the target project are identified. In some embodiments, each project may have one or more users; therefore, at least one user included in the target project can be identified.

[0048] Next, assign at least one role to each user.

[0049] Here, "user" refers to an account created on the platform for specific personnel involved in a project, while "role" refers to an abstract concept on the platform with a set of related permissions, representing the user's identity or function in a specific context. A user can be associated with multiple roles, and a role can also be associated with multiple users.

[0050] Then, bind the character to at least one workbench in the workbench inventory.

[0051] The workbench can be pre-arranged from multiple business widgets according to specific business requirements; each role can establish a binding relationship with one or more workbenches and store the binding relationship in the database.

[0052] Understandably, when binding is required, each workbench can be bound to at least one character.

[0053] In this embodiment, a binding relationship is established between the role and the workbench, that is, the user forms an indirect binding relationship with the workbench through the role, which is the first type of binding relationship. This allows the user to directly use the first type of binding relationship to select the corresponding workbench for loading, thereby improving work efficiency.

[0054] Furthermore, the following operations may also be included.

[0055] First, configure the initial binding relationship between each user and the corresponding role.

[0056] Here, "user" refers to an account created on the platform for specific personnel involved in a project, while "role" refers to an abstract concept on the platform with a set of related permissions, representing the user's identity or function in a specific context. A user can be associated with multiple roles, and a role can also be associated with multiple users.

[0057] Specifically, for each user, a primary binding relationship is configured between each user and the corresponding role.

[0058] Next, select at least one bindable workbench from the workbench inventory and configure a second binding relationship between the character and at least one bindable workbench.

[0059] Each character can establish a binding relationship with at least one workbench.

[0060] Specifically, select a workbench from the workbench repository that can be bound to a character to configure the binding between the character and the workbench, i.e., establish a second binding relationship, where each character can establish a binding relationship with one or more workbenches.

[0061] Then, using the first binding relationship and the second binding relationship, the binding relationship between each user and at least one workbench is determined, and the indirect binding relationship between the user and the workbench through the role is set as the first type of binding relationship.

[0062] Specifically, since the first binding relationship represents the binding relationship between a user and a role, and the second binding relationship represents the binding relationship between a role and a workbench, the binding relationship between each user and at least one workbench can be determined using the first and second binding relationships.

[0063] In some embodiments, users can also customize their own workbench. In this case, the user can directly select at least one workbench that can be bound from the workbench repository, modify it according to the user's operating habits, and configure the corresponding binding relationship, i.e., the third binding relationship. The third binding relationship can be used to determine the target workbench corresponding to the target user, and the direct binding relationship between the user and the workbench is set as the second type of binding relationship. Then, in response to the login request, the second type of binding relationship is used to determine the user's target workbench, and the target workbench is used to complete the loading of the web page interface.

[0064] The following diagram illustrates the relationship model of products, projects, users, roles, workbenches, and business widgets.

[0065] See Figure 3 , Figure 3 This is a schematic diagram of the structure of an embodiment of the association model in this application.

[0066] like Figure 3As shown, there can be multiple products, such as Product 1, Product 2, Product 3, Product T, etc., and each product can have one or more projects; there can be multiple projects, such as Project 1, Project 2, Project 3, Project 4, Project N; each project has one or more users, and each user can be associated with one or more roles; the workbench repository can have multiple workbenches, such as Workbench 1, Workbench 2, Workbench 3, Workbench 4, Workbench 5, Workbench M; the business widget repository can have multiple business widgets, such as Widget 1, Widget 2, Widget 3, Widget 4, Widget 5, Widget 6, Widget 7, Widget Y; therefore, the first The product comprises a first project and a second project. The second product contains a third project, the third product contains a fourth project, and the Tth product contains an Nth project. The first project includes a first user and a second user. The first user is bound to a first role, and the first role can be bound to the first workbench referenced by the first product. The second user is bound to a second role, and the second role can be bound to the second workbench referenced by the first product. The second project includes a third user, a fourth user, and a fifth user. The third user is bound to a third role, and the fourth and fifth users can be bound to the fourth role. The third role can be bound to the second workbench referenced by the first product, and the third role can also be bound to the third workbench referenced by the first product. The fourth role can be bound to the sixth workbench created through the workbench engine on the project; that is, the sixth workbench is customized for the project and bound to the role. The third project includes a sixth user and a seventh user. The sixth user is bound to the fifth and sixth roles. The fifth role can be bound to the third workbench referenced by the second product. The sixth role can be bound to the fourth workbench referenced by the second product. The seventh user is bound to the seventh role. The seventh role can be bound to both the fourth and fifth workbench referenced by the second product. The fourth project includes an eighth user and a ninth user. The eighth user is bound to the eighth role. The eighth role can be bound to the fifth workbench referenced by the third product. The ninth user can be bound to the eighth role, and the ninth user can also be bound to the ninth role. Users can bind to the fifth workbench referenced by the third product through the eighth role. The ninth user can also use a customized workbench, that is, the seventh workbench newly created by the workbench engine on the project bound to the ninth user. In other words, the seventh workbench is customized for the project and bound to the user. The Nth project contains a user X, which is bound to a role Z. This role Z is bound to the Mth workbench. That is, user X in the Nth project can be indirectly bound to the Mth workbench referenced by the baseline product of the project through role Z. This is the first type of binding relationship. User X can also be directly bound to the Mth workbench. This is the second type of binding relationship. Each workbench consists of one or more business widgets.

[0067] Users can associate with multiple workstations and switch between them. For example, a third user can bind to the second and third workstations through a third role and switch between them. Workstations can also be cross-industry. The aforementioned third and fifth workstations are cross-industry general workstations, such as general workstations for parking fees and visitor management. In addition to binding with workstations through roles, users can also bind directly to workstations. For example, a ninth user can associate with both the fifth and seventh workstations.

[0068] During baseline development, the workbench can reuse widgets from the business widget repository as needed, avoiding redundant development of identical atomic business functions or integrated business function components. During product release, different industry platform products can reference workbenches from the workbench repository as needed. When an industry platform product is implemented in a project, the workbench used to introduce that product can be associated with the created platform role, allowing users to access available workbenches through the associated role. Users can also customize workbenches for their own use, achieving differentiated workbenches for different industries, projects, and users. Through the optimization of the associated data model, the IoT management platform has developed a flexible and adaptable baseline product and project implementation mechanism, greatly improving the compatibility of the platform's core user interface with massive business scenarios.

[0069] In this embodiment, by establishing a first binding relationship between each user and a role, and a second binding relationship between each role and a workbench, each user is bound to at least one corresponding workbench, clarifying the business focus of each user, and thus clarifying the first type of indirect binding relationship between users and workbench, improving the workbench's adaptability to users; if a user needs to customize their own workbench, a third binding relationship can be established between the user and the workbench, thus clarifying the second type of direct binding relationship between users and workbench, and improving the applicability.

[0070] Furthermore, the following operations may also be included:

[0071] Using preset business requirements, multiple corresponding business widgets are selected from the business widget library in advance and arranged to generate a workbench that matches the preset business requirements, thereby obtaining several workbenches stored in the workbench warehouse.

[0072] First, develop multiple business widgets and store them in a widget repository. These business widgets can be reused in different workbenches.

[0073] Among them, a business widget refers to a functional module integrated to implement a certain function, which can be reused in different workbenches. Here, reuse means copying a business widget to a corresponding workbench without affecting other workbenches; for example, a visitor information business widget is used for visitor information management; a vehicle charging business widget is used for vehicle charging information management.

[0074] Specifically, business widget development tools can be used to develop business widgets to obtain multiple business widgets, which can then be stored in a widget repository.

[0075] Next, based on professional experience, the web page interface is laid out according to different business requirements, and the multiple pre-selected business widgets are arranged to complete the workbench corresponding to each type of business requirement, thereby obtaining several workbenches stored in the workbench warehouse.

[0076] Specifically, based on the characteristics of each type of business, the placement of the pre-selected business components is determined, and then multiple pre-selected business components are arranged to obtain a workbench that satisfies that type of business. The workbench is then stored in a workbench warehouse to obtain several workbench in the workbench warehouse.

[0077] In some embodiments, when a suitable workbench matching the specific scenario of the project cannot be found in the existing workbench repository, a corresponding workbench can be created according to the user's specific arrangement requirements to meet the user's specific needs for the workbench.

[0078] In this embodiment, by developing business widgets in advance and then arranging multiple workbenches according to specific business requirements, several workbenches are prepared in advance for the workbench warehouse, so that a suitable workbench can be selected directly from the workbench warehouse for loading in the future, thereby improving work efficiency.

[0079] In some embodiments, step S20, in response to a login request from a target user in a target project, determines the target user's target workbench using the binding relationship, and then uses the target workbench to load the web page interface, may include the following operations.

[0080] First, in response to the login request, determine the target user in the target project corresponding to the login request.

[0081] The login request refers to the request to log in to the current webpage interface. It can be directed to a specific user in a specific project, and the target user refers to the user that the login request asks to log in.

[0082] Specifically, when a login request is received on the current webpage, the system responds to the login request by parsing the target user in the login request, and then determines the target user corresponding to the login request.

[0083] Next, the role corresponding to the target user is determined using the first binding relationship.

[0084] Specifically, since each user has a corresponding first binding relationship, it is possible to obtain the roles that each user has a first binding relationship with.

[0085] Furthermore, in response to the absence of a second type of binding relationship for the target user, the target role corresponding to the target user is determined using the first binding relationship.

[0086] Then, the target workbench corresponding to the role is determined using the second binding relationship.

[0087] Specifically, since each role has a corresponding second binding relationship, the target workbench with the second binding relationship for each role can be determined.

[0088] In some embodiments, each role can be bound to multiple workbenches. When a user logs in, they can select one of the workbenches as the target workbench for loading. Each workbench can also be bound to multiple roles, realizing a many-to-many relationship between roles and workbenches.

[0089] Furthermore, the following operations may also be included:

[0090] Before using the first binding relationship to determine the role corresponding to the target user, it is also possible to first determine whether the target user has a second type of binding relationship, that is, whether there is a third binding relationship. Then, using the third binding relationship, the workbench bound to the target user is determined to be the target workbench and set as the second type of binding relationship. At this time, the workbench bound to the target user is the first type of workbench.

[0091] Specifically, first determine whether the target user has a third binding relationship. If the target user does not have a third binding relationship, then determine whether the target user has a first binding relationship. If a third binding relationship exists, the workbench bound to the target user is determined by the third binding relationship as the target workbench. If the target user does not have a third binding relationship, the first binding relationship of the target user is determined, the role bound to the target user is determined by the first binding relationship, and the workbench corresponding to the second binding relationship is taken as the target workbench.

[0092] In some embodiments, the workbench can be divided into a first type of workbench, a second type of workbench, and a third type of workbench. The loading priority of the first type of workbench is higher than that of the second type of workbench, and the loading priority of the second type of workbench is higher than that of the third type of workbench. For example, the third type of workbench is the basic workbench, which can be used in different projects. The second type of workbench is a role-based workbench, set up for a specific role. The first type of workbench is a personal workbench, set up for a specific user; a customized personal workbench is a first type of workbench. In some embodiments, the second type of workbench can also be customized for a specific role; that is, a customized workbench can be either a first type of workbench or a second type of workbench, depending on whether it is customized for a specific user or a specific role.

[0093] The first type of workbench is the personal workbench: a workbench associated with platform users, focusing on customization based on user operating habits, and has the highest loading priority. The second type of workbench is the role-based workbench: a workbench associated with roles in the platform's RBAC (Role-Based Access Control) mode, focusing on professional experience and guiding corresponding roles in standardized and quick operations, with a medium loading priority. If a user is associated with multiple role-based workbenches, they can switch between them. The third type of workbench is the basic workbench: equivalent to the original unified work homepage, focusing on a full directory of capabilities. Users can access specific business operations through the business module entry points of the basic workbench, and has a low loading priority.

[0094] Furthermore, the following operations may also be included:

[0095] When a target role is bound to multiple workbenches, the target workbench corresponding to the target user is determined by loading priority and the second binding relationship.

[0096] The target role refers to the role that the user requested to log in to is bound to.

[0097] Specifically, each role can have one or more bound workbenches. Therefore, when logging in, the second binding relationship can be used to determine which workbenches are bound, and then the workbench with the highest priority can be determined as the target workbench by using the loading priority of the workbenches. In some embodiments, users can also be allowed to select one of the workbenches as the target workbench, and the workbench selected by the user will be loaded by default when the user logs in again.

[0098] Alternatively, if a character is bound to only one workbench, this workbench can be directly used as the target workbench for loading, where the workbench in this case is considered a second type of workbench.

[0099] Among them, loading priority represents the user's current business focus. If there are multiple businesses, the user's current business focus may be one of them, and the corresponding business will have the highest loading priority.

[0100] In some embodiments, the focus of the workbench may also be included, with the first type of workbench focusing on the user's personal operating habits, the second type of workbench focusing on professional experience, and the third type of workbench focusing on full catalog coverage.

[0101] In some embodiments, the first type of workbench and the second type of workbench can be converted. For example, after the second type of workbench is customized by the user, it can be converted into the first type of workbench corresponding to the user, and the first type of workbench can also be restored to the second type of workbench.

[0102] In some embodiments, a fourth type of workbench may also be included, which is a professional workbench built into the product release, or a workbench customized by a client with industry experience in a project according to its own business characteristics. It can be used as a professional workbench resource pool built into the product release, or a workbench created by industry experts of the project client, without loading priority.

[0103] In some embodiments, a workbench can be defined for the target user and directly bound to it; in this case, the workbench is a first type of workbench.

[0104] See Figure 4 , Figure 4 This is a schematic flowchart of an embodiment of workbench loading in this application.

[0105] like Figure 4 As shown, after logging into the platform and passing authentication, users will enter the workbench page. At this point, the workbench engine will retrieve the user's workbench. Upon retrieving the user's workbench, it checks if the user has a configured workbench. If so, the configured workbench is opened directly. If not, it checks if the user's role has a bound workbench. If so, it checks if the number of bound workbenches for the role is greater than one. If it is greater than one, a pop-up window prompts the role to select a workbench, and the selected workbench is loaded. If it is not greater than one, the corresponding workbench is loaded directly. If no workbench is bound, the basic workbench is loaded. After loading, the instantiation of the business widget is completed.

[0106] In some embodiments, the target worktable can also be adjusted, specifically including the following operations.

[0107] First, obtain the operation information of the target workbench on the business widgets during the operation process. The operation information includes at least the number of clicks, the dwell time, and the click order.

[0108] Specifically, when a user works through the target workbench, the system obtains information on the number of clicks, dwell time, and click order of each business widget during the work process, which is used as click information.

[0109] Next, by using click count information, dwell time information, and click order information, the value score and relevance of each business widget are determined.

[0110] Among them, the value score refers to the evaluation of the business widget under the click information in the current target workbench, and the relevance refers to the operational relevance between various business widgets.

[0111] Specifically, by using the click count, dwell time, and click order information from the acquired operation information, the value score corresponding to each business widget in the target workbench can be determined, thereby obtaining the value score ranking of the business widgets in the target workbench and the correlation between the business widgets.

[0112] Then, the different areas of the target workbench are divided according to the value score to obtain different value score areas.

[0113] Specifically, based on the different regional concerns, the target workbench is divided into different areas with value scores, thereby determining the different value score areas of the target workbench.

[0114] Then, by utilizing value scores, relevance, and different value score regions, the business widgets of the target workbench are regionally adjusted, and the adjusted target workbench is then loaded.

[0115] Specifically, by utilizing the value score ranking of business widgets, the relevance of business widgets, and the different value score ranges of the target workbench, the business widgets existing in the target workbench are adjusted to make the adjusted target workbench more suitable for users, i.e. easier to operate. In response to the user's confirmation of the adjusted target workbench, an optimization message is pushed to the user. After the user confirms, the adjusted target workbench is loaded to obtain the final target workbench, which is the final operable web page interface for the user.

[0116] The adjustment principle is as follows: Click events and dwell time of business widgets used by project users in the workbench are reported to the project platform's high-frequency analysis management service. The high-frequency analysis management service first cleans the data, then calculates the total number of times business widgets are used and the total dwell time for each workbench, and analyzes the order of operations to calculate the correlation between business widgets. The workbench engine periodically pulls user usage statistics and correlation analysis data from the high-frequency analysis management service and automatically optimizes the workbench layout. The overall principle is: based on different weighting coefficients for frequency and duration, the value score of all business widgets is calculated, with higher-value widgets at the top of the layout having higher scores than those at the bottom, and vice versa; widgets with high correlation are placed closer together. For important business widgets primarily for data display, such as notifications and announcements, a fixed value is set. After the workbench optimization is completed, it is pushed to the user, and the workbench update takes effect after user confirmation.

[0117] In this embodiment, each user in the target project is bound to at least one role, and each role is configured to be bound to at least one workbench, thereby realizing a many-to-many relationship between users and workbench. This meets the differentiated needs of web page interfaces for massive business scenarios, effectively enables rapid project delivery, reduces development costs, and improves work efficiency.

[0118] In some embodiments, a web page interface loading system is also provided.

[0119] See Figure 5 , Figure 5 This is a schematic diagram of the structure of an embodiment of the web page loading system in this application.

[0120] like Figure 5 As shown, the web page loading system 400 includes a configuration module 410 and a determination module 420. The configuration module 410 is used to obtain at least one user included in the target project, configure the binding relationship between each user and at least one corresponding role, and then configure the binding relationship between each role and at least one corresponding workbench in the workbench repository. The workbench repository stores several workbenches, which are pre-arranged from multiple business components using preset business requirements, and each workbench is configured to be bound to some roles. The determination module 420 responds to the login request of the target user in the target project, uses the binding relationship to determine the target workbench of the target user, and then uses the target workbench to complete the loading of the web page.

[0121] In some embodiments, an electronic device is also provided.

[0122] See Figure 6 , Figure 6This is a schematic diagram of an embodiment of the electronic device in this application. This electronic device can perform the webpage loading step in the above method.

[0123] The electronic device 500 includes a memory 520, a processor 510 coupled to the memory, and at least one computer program stored in the memory 520 and executable on the processor 510. When the processor 510 loads and executes the at least one computer program, it implements the web page interface loading step in the above method. For related details, please refer to the detailed description in the above method; it will not be repeated here.

[0124] In some embodiments, a computer-readable storage medium is also included.

[0125] Please see Figure 7 , Figure 7 This is a schematic diagram of an embodiment of a computer-readable storage medium in this application.

[0126] The computer-readable storage medium 600 stores at least one program 610, which, when loaded and executed by a processor, is used to implement the web page interface loading step in the above method. For related details, please refer to the detailed description in the above method; it will not be repeated here.

[0127] In the above solution, each user in the target project is bound to at least one workbench through an associated role, or the user is directly bound to a workbench, thereby realizing a many-to-many relationship between users and workbench. This meets the differentiated needs of web page interfaces for massive business scenarios, effectively achieves rapid project delivery, reduces development costs, and improves work efficiency.

[0128] In the several embodiments provided by this invention, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, indirect coupling or communication connection of apparatuses or units, and may be electrical, mechanical, or other forms.

[0129] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment, depending on actual needs.

[0130] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0131] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0132] The above description is merely an embodiment of the present invention and does not limit the patent scope of the present invention. Any equivalent structural or procedural transformations made based on the content of the present invention specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of the present invention.

Claims

1. A method for loading a web page interface, characterized in that, The application is applied to an Internet of Things management platform, and the Internet of Things management platform at least includes associated basic resource management and a workbench engine, the basic resource management includes at least one user and at least one role corresponding to each user, and the workbench engine includes a workbench warehouse and a widget warehouse, comprising: At least one user included in a target project is acquired, and a binding relationship between each user and at least one corresponding role is configured, and then a binding relationship between each role and at least one corresponding workbench in the workbench warehouse is configured; wherein a plurality of workbenches stored in the workbench warehouse are obtained by pre-arranging a plurality of business widgets according to a preset business requirement, and each business widget can be reused in different workbenches, each workbench is configured to be bound with part of the roles, and the number of roles bound by each workbench is less than the total number of roles in the target project; the role is used to represent the identity or function of a group of related permissions; In response to a login request of a target user in the target project, the target workbench of the target user is determined by using the binding relationship, and then the loading of the web page interface is completed by using the target workbench; wherein the binding relationship includes a first type binding relationship and a second type binding relationship, the first type binding relationship represents that the target user is bound with at least one workbench through the corresponding role, and the second type binding relationship represents that the target user is bound with at least one workbench; Operation information of the business widget of the target workbench is acquired, the value score and the association degree of each business widget are determined by using the operation information, the business widget of the target workbench is adjusted in different value score regions in combination with the different value score regions of the target workbench, and the loading of the web page interface is completed by using the adjusted target workbench, wherein the operation information at least includes click frequency information, stay time information and click order information; Wherein, in response to the fact that the target user has a plurality of bound workbenches, the workbench with the highest loading priority is determined as the target workbench by using the loading priority of the workbench, and the loading priority represents the current business focus of the target user.

2. The method of claim 1, wherein: the at least one user included in the target project is acquired, and a binding relationship between each user and at least one corresponding role is configured, and then a binding relationship between each role and at least one corresponding workbench in the workbench warehouse is configured, comprising: at least one user included in the target project is acquired; a first binding relationship between each user and at least one corresponding role is configured; at least one workbench that can be bound is selected from the workbench warehouse by using the role, and then a second binding relationship between each role and at least one workbench is configured; the binding relationship between each user and at least one workbench through each role is determined by using the first binding relationship and the second binding relationship, and is set as a first type binding relationship.

3. The method of claim 1, wherein, Further comprising: The corresponding multiple business widgets are selected from the business widget library in advance according to preset business requirements, and a workbench matched with the preset business requirements is generated, and then a plurality of workbenches stored in the workbench warehouse are obtained, wherein the arranged workbench at least includes: workbench basic information, workbench layout information, and business widget list information.

4. The method of claim 1, wherein, The binding relationship is determined by a first binding relationship and a second binding relationship, and the binding relationship is a first type binding relationship, wherein the first binding relationship represents the binding between the user and the role, and the second binding relationship represents the binding between the role and at least one workbench in the workbench warehouse; The target workbench of the target user is determined by using the binding relationship in response to the login request of the target user in the target project, comprising: In response to the login request, determining the target user in the target project corresponding to the login request; The target role corresponding to the target user is determined by using the first binding relationship; The target workbench corresponding to the target role is determined by using the second binding relationship, and the target workbench corresponding to the target role is used as the target workbench of the target user.

5. The method of claim 4, wherein, Before determining the target role corresponding to the target user by using the first binding relationship, further comprising: In response to the user having a third binding relationship, at least one workbench in the workbench warehouse is selected as the target workbench of the user by using the third binding relationship, and is set as a second type binding relationship, wherein the third binding relationship represents the binding between the user and at least one workbench in the workbench warehouse; In response to the login request, the target workbench is used to complete the loading of the web page interface.

6. The method of claim 5, wherein, Further comprising: The workbench includes a first type workbench and a second type workbench, and the priority of the first type workbench is higher than that of the second type workbench; The target role corresponding to the target user is determined by using the first binding relationship, comprising: In response to the target user not having the second type binding relationship, the target role corresponding to the target user is determined by using the first binding relationship; The target workbench corresponding to the target role is determined by using the second binding relationship, comprising: In response to the target role being bound to multiple workbenches, the target workbench corresponding to the target role is determined by using a loading priority and the second binding relationship, wherein the loading priority represents the current business focus of the target user; Or in response to the target role being bound to only one workbench, the target role is associated with the workbench, and the associated workbench is loaded as the target workbench, wherein the workbench bound by the target role is a second type workbench, and the target workbench of the user determined by the second type binding relationship is a first type workbench.

7. The method of claim 6, wherein, Further comprising, The workbench is customized for the target user or target role and is directly bound, and the workbench customized for the target user is a first type of workbench.

8. The method of claim 6, wherein, Further comprising: The workbench further comprises a third type of workbench, and the third type of workbench is a basic workbench, wherein the priority of the second type of workbench is higher than that of the third type of workbench. The user can also enter a function menu to perform a specific business operation by using a business module entry of the third type of workbench.

9. The method of claim 4, wherein, The operation information of the business widgets of the target workbench is obtained, the value score and the correlation degree of each business widget are determined by using the operation information, the business widgets of the target workbench are adjusted in regions in combination with different value score regions of the target workbench, and the loading of the webpage interface is completed by using the adjusted target workbench, and the method comprises: Obtaining operation information of the business widgets of the target workbench in a working process, wherein the operation information at least comprises click frequency information, stay time information, and click sequence information; Determining the value score and the correlation degree of each business widget by using the click frequency information, the stay time information, and the click sequence information; Dividing different regions of the target workbench according to the value score to obtain different value score regions; Adjusting the business widgets of the target workbench in regions by using the value score, the correlation degree, and the different value score regions, and loading the target workbench in response to the confirmation of the user to the adjusted target workbench.

10. An electronic device, comprising: The electronic device comprises a memory and a processor coupled with the memory, the memory stores at least one computer program, and the at least one computer program is loaded and executed by the processor to implement the webpage interface loading method of any one of claims 1-9.

11. A computer readable storage medium, characterized in that, The computer readable storage medium has at least one program, and the at least one program is loaded and executed by the processor to implement the webpage interface loading method of any one of claims 1-9.

Images