Page loading method, apparatus, device, and storage medium

Abstract

The present disclosure relates to a page loading method, device, equipment and storage medium, and relates to the technical field of computer application, wherein the method comprises: in response to a loading request of a target page by a target user account, obtaining a page permission point set of the target page; obtaining a user permission point set of the target user account; obtaining a target permission point matched with the user permission point set from the page permission point set, and loading the target page according to the target permission point. Thus, by abstracting page functions in a page into permission points and performing multi-level loading authentication based on the permission points, the present disclosure realizes unified multi-level authentication, guarantees loading page efficiency, and flexibly meets multi-level loading authentication requirements.

Description

Technical Field

[0001] This disclosure relates to the field of computer application technology, and in particular to a page loading method, apparatus, device, and storage medium. Background Technology

[0002] With the development of computer technology, various computer-based systems are becoming increasingly common, such as the middleware, front-end, and back-end systems of various computer products. To facilitate secure system management, authentication is required.

[0003] In related technologies, authentication is based on the user account's role. For example, an administrator role has different loading permissions than a regular user role, therefore, the content displayed on the page is different.

[0004] However, the authentication method described above when loading a page binds the role to the page, and the granularity of authentication is limited by the diversity of the roles. Since the number of roles in the system is limited, the granularity of authentication is relatively coarse, which is difficult to meet the current needs of multi-level authentication. Summary of the Invention

[0005] To solve the above-mentioned technical problems, or at least partially solve them, this disclosure provides a page loading method, apparatus, device, and storage medium.

[0006] This disclosure provides a page loading method, including the following steps: in response to a loading request for a target page from a target user account, obtaining a set of page permission points for the target page; obtaining a set of user permission points for the target user account; obtaining a target permission point that matches the set of user permission points from the set of page permission points; and loading the target page according to the target permission point.

[0007] This disclosure also provides a page loading apparatus, comprising: a first acquisition module, configured to acquire a set of page permission points for the target page in response to a loading request for a target page from a target user account; a second acquisition module, configured to acquire a set of user permission points for the target user account; and a loading module, configured to acquire a target permission point matching the set of user permission points from the set of page permission points, and load the target page according to the target permission point.

[0008] This disclosure also provides an electronic device, the electronic device comprising: a processor; a memory for storing executable instructions of the processor; the processor being configured to read the executable instructions from the memory and execute the instructions to implement the page loading method provided in this disclosure.

[0009] This disclosure also provides a computer-readable storage medium storing a computer program for performing the page loading method provided in this disclosure.

[0010] The technical solution provided in this disclosure has the following advantages compared with the prior art:

[0011] In response to a loading request for a target page from a target user account, the system retrieves the page permission point set for the target page and the user permission point set for the target user account. Then, it obtains the target permission point from the page permission point set that matches the user permission point set, and loads the target page based on the target permission point. Thus, by abstracting page functions into permission points and performing multi-level loading authentication based on these permission points, a unified multi-level authentication system is achieved, flexibly meeting multi-level loading authentication requirements while ensuring page loading efficiency. Attached Figure Description

[0012] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0013] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0014] Figure 1 This is a flowchart of a page loading method according to an embodiment of the present disclosure;

[0015] Figure 2(a) is a schematic diagram of page loading according to an embodiment of the present disclosure;

[0016] Figure 2(b) is a schematic diagram of page loading according to another embodiment of this disclosure;

[0017] Figure 2(c) is a schematic diagram of page loading according to another embodiment of this disclosure;

[0018] Figure 3 This is a flowchart of a page loading method according to another embodiment of this disclosure;

[0019] Figure 4 This is a schematic diagram illustrating page loading according to another embodiment of the present disclosure;

[0020] Figure 5 This is a flowchart of a page loading method according to yet another embodiment of the present disclosure;

[0021] Figure 6This is a schematic diagram of the structure of a page loading device according to yet another embodiment of the present disclosure;

[0022] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. Detailed Implementation

[0023] To better understand the above-mentioned objectives, features, and advantages of this disclosure, the solutions disclosed herein will be further described below. It should be noted that, unless otherwise specified, the embodiments and features described herein can be combined with each other.

[0024] Numerous specific details are set forth in the following description in order to provide a full understanding of this disclosure, but this disclosure may also be implemented in other ways different from those described herein; obviously, the embodiments in the specification are only some, and not all, of the embodiments of this disclosure.

[0025] To address the technical issue mentioned in the background section—where page authentication during page loading is solely role-based, resulting in coarse-grained authentication that fails to flexibly meet the authentication needs of various scenarios—this disclosed page loading method incorporates three levels of authentication: page-level permissions, function-level permissions, and data-level permissions. Page-level permissions determine whether a specific page within the system is visible to the current user; function-level permissions determine whether a specific operation within a page is visible or available to the current user; and data-level permissions determine whether a specific piece of data within a page is visible to the current user. This multi-level authentication provides technical support for meeting authentication needs across multiple scenarios.

[0026] In the embodiments of this disclosure, the various functions of the system's page are uniformly processed into a single unit called a permission point. Based on the unified representation of this permission point, authentication at different levels is further unified, which flexibly meets authentication requirements while improving authentication efficiency.

[0027] The page loading method, apparatus, device, and storage medium of this disclosure are described below with reference to specific embodiments. The page loading method of this disclosure can be applied to any page loading scenario requiring multi-level authentication, including but not limited to middleware systems.

[0028] Specifically, Figure 1 This is a flowchart of a page loading method according to an embodiment of the present disclosure. The page loading method includes the following steps:

[0029] Step 101: In response to the target user account's request to load the target page, obtain the set of page permission points for the target page.

[0030] In this embodiment, when a request to open a target page is received from a target user account, for example, when the target user account inputs routing information for the target page and triggers a redirection instruction, it is considered that a loading request for the target page from the target user account has been received, and thus, authentication of the target page begins.

[0031] The page permission point of the target page includes an abstract representation of the permissions corresponding to all executable functions on the target page. This page permission point can contain different information corresponding to the page functions in different application scenarios, which will be described in detail in subsequent embodiments and will not be repeated here.

[0032] Step 102: Obtain the set of user permission points for the target user account.

[0033] It should be understood that in this embodiment, a corresponding user permission point is assigned to each user account, wherein the user permission point corresponds to the page permission point, thereby generating a set of user permission points for each user account. For example, the correspondence between each user account and all corresponding authorized user permission points can be pre-constructed, and the set of user permission points for the target user account can be obtained by querying the correspondence.

[0034] Among them, the user permission points that a user account has permission to access can be determined based on the user account's registered role information, registration location, and other profile information.

[0035] For example, obtain profile information for each user account, and determine whether the user has the permissions for each page permission point on each page based on the profile information. For instance, if the user account is a minor, it cannot have the page permission points for functions that are not suitable for children. For example, the page permission point corresponding to the live streamer tipping function is not available to a minor account.

[0036] Step 103: Obtain the target permission point that matches the user permission point set from the page permission set, and load the target page based on the target permission point.

[0037] In this embodiment, the page permission point set includes all page permission points assigned to the target page during the development phase, and the user permission point set includes all page permission points owned by the target user account. Thus, the target permission point that matches the user permission point set can be obtained from the page permission point set. For example, the intersection of the page permission point set and the user permission point set can be calculated. The target permission points in this intersection reflect whether the target user account has the loading permission for certain page functions corresponding to certain page permission points on the target page. Then, the target page is loaded according to the target permission points.

[0038] Conversely, if no target permission point exists, it means that the target user account does not have any permission to use any page permission point of the target page. Therefore, the target page can be refused to be loaded for the target user account, or the target page can be loaded and the relevant data of the corresponding unauthorized page permission point can be rendered on the target page.

[0039] It is important to emphasize that in this embodiment, all page functions are abstracted into permission points. Therefore, based on the permission point unit, multi-level authentication from the page level to the function level to the data level can be uniformly implemented without the need for separate authentication for each level. This not only improves authentication efficiency, but also provides technical support for the opening or closing of relevant page functions at each level due to the ability to implement multi-level authentication, flexibly meeting the authentication needs of various page loading.

[0040] For example, referring to Figure 2(a), page permission points can be used to restrict user a from loading page 1, while preventing user b from loading page 1, thus achieving page-level authentication.

[0041] Referring to Figure 2(b), by using page permission points, user a can be restricted from loading control A in page 1 and providing the function of control A. However, user b is restricted from loading control A in page 1 and cannot use the function of control A, thereby achieving function-level authentication.

[0042] Referring to Figure 2(c), page permission points can restrict user a from loading control A in page 1, granting control A permission to load data 1. While user b can load control A in page 1, user b is restricted from accessing control A's data 1, thus achieving data-level authentication.

[0043] In summary, the page loading method of this disclosure, in response to a loading request for a target page from a target user account, obtains a set of page permission points for the target page and a set of user permission points for the target user account. Then, it retrieves a target permission point from the page permission set that matches the user permission point set, and loads the target page based on the target permission point. Thus, by abstracting page functions into permission points and performing multi-level loading authentication based on these permission points, it achieves unified multi-level authentication, ensuring page loading efficiency while flexibly meeting the needs of multi-level loading authentication.

[0044] As mentioned above, in actual implementation, page permission points can be any unique identifier for a function on a page. The following example illustrates this:

[0045] Example 1:

[0046] In this example, the page permission point corresponds to a function interface, so the definition of the page permission point can be:

[0047]

[0048] It is important to emphasize that, since this function interface corresponds to certain functions on the page, whether the page has the authorized functions determines whether the target user account has page-level and function-level authorization.

[0049] Page-level permission authentication determines whether a specific page within a system, such as a middle or back-end system, is visible to a user. A page may contain n (n>0) functions, and each page may contain m (m>=0) function-level interfaces. This requires the permission system to determine whether to display the page and whether to display a specific function control within the page when the user account has x (x∈{n*m}) permissions.

[0050] When performing function-level permission authentication, each function on the page may contain m (m>=0) function-level function interfaces. When a user account has permissions for y (y∈{m}) function interfaces, it is determined whether to display this function control on the page.

[0051] For example, refer to Figure 3 If the target page to be accessed is Page-1, Page-1 contains a set of functional interfaces M = {AB-1, AB-2, AB-3, ..., AB-n}, where AB-x represents a function within the target page, such as the delete function mentioned above. Each function contains multiple functional interfaces. For example, AB-x contains functional interfaces N = {api-1, api-2, api-3, ..., api-n}, where api-x represents a functional interface, which can be understood as a permission point tag. Then, the set of page permission points for the target page is P = M·N = {AB-1_api-1, AB-1_api-2, ..., AB-2_api-1, ..., AB-n_api-n}.

[0052] If the target user account's user permission point set is If It is then assumed that the user has Page-1 level permissions, and is allowed to render the target page.

[0053] In this embodiment, when the target page is the broadcaster management page, the target page is declared through a page reason. When the target user account does not have page-level permissions, the entire route is discarded and not rendered. The declaration code is as follows:

[0054]

[0055]

[0056] Furthermore, the code for function-level authentication is as follows. Taking function AB-1 containing function interfaces M = {AB-1_api-1, AB-1_api-2, ..., AB-1_api-n} as an example, during system initialization, the system requests a list of interfaces that the target user account has permission to access from the server interface. The user permission point set `user_auth_apis` determines whether at least one of the functional interfaces `apis` of the dependent AB-1 appears in `user_auth_apis`. If at least one appears, the target user account is considered to have permission to AB-1, and more controls of AB-1 are rendered. If none appear, the passed-in functional controls that do not have permission are displayed or not displayed at all.

[0057]

[0058]

[0059] In this embodiment, due to the complexity of the functions on the page, determining the corresponding function interfaces of the functions on the target page is quite complicated. For example, some custom page functions do not have traditionally meaningful function interfaces. Therefore, how to map each function that needs authentication on the page to a corresponding function interface is also a point that needs to be explained in this disclosure, as explained below.

[0060] The following example illustrates how several common functional interfaces included on a page correspond to permission points:

[0061] (1) The first functional permission point corresponding to the application interface.

[0062] In this embodiment, the application programming interface (API) can be understood as a functional interface that requests data from the system. The extraction of this functional interface is relatively intuitive. In this disclosure, the data request path of each functional interface is directly used as a first functional permission point.

[0063] For example: Deleting the next streamer in a guild. This operation corresponds to a function interface ( / anchor / delete, denoted as A). A is a function interface in this public disclosure. A user account with permission to this function interface (A) can delete the streamer currently visible to the user in the guild. A user account without permission A cannot delete the streamer currently visible to the user in the guild.

[0064] (2) Extend the second functional permission point corresponding to the business interface.

[0065] In this embodiment, the extended business interface is a more granular and infinitely expandable extension of the functions on the page. Considering the complexity of the back-end and other systems, there are functions that do not have system data requests. Therefore, in this embodiment, a fake, non-existent function interface is created as the extended business interface. For example, / fake / get is denoted as B. As an extension of the function interface, it should be noted that B still has a unique corresponding function interface and has the same authentication function and effect as A.

[0066] It should be noted that the extended business interface writes the corresponding images or advertisements and other web page data into the page code through code or other means. Therefore, having the second functional permission point of the extended business interface allows the page to display the corresponding images or advertisements; otherwise, the corresponding images or advertisements are not displayed.

[0067] (3) Data application permission points corresponding to the application programming interface.

[0068] In this embodiment, the data application permission point is mainly used for data authentication in the server layer of the middle and back-end systems. To maintain the consistency of the permission system, each application data also has a virtual data interface for request (for example, ake / data / get is denoted as C). For example, the back-end data table is split into different application data, and each application data is used as a data application permission point. The application data can correspond to a row or column in the data table, or multiple rows and columns, etc., and can be split according to the application scenario. They are not listed one by one here.

[0069] In this embodiment, a first functional permission point may include one or more data application permission points. For example, taking server-level data authentication as an example, when application interface X needs to perform data-level permission isolation, the first functional permission point corresponding to application interface X may also include M = {x-1, x-2, x-3, ... xn}, where n is a natural number greater than 3.

[0070] It should be noted that since the data application permission point is a subordinate permission point of the first function permission point, in this embodiment, when performing page-level and function-level authentication, data-level authentication can be temporarily omitted, that is, the data that the user account can view is not determined.

[0071] In other words, in the embodiments of this disclosure, when the target page contains a first functional permission point and a second functional permission point, for the preset first functional permission point, the data request path of the functional permission point is obtained, and the data request path is determined as the first functional permission point. For the preset second functional permission point, a fake functional interface is defined according to certain definition rules. Specifically, a corresponding data application permission point is set for the first functional permission point.

[0072] Example 2:

[0073] In this example, the page permission point corresponds to the function identifier of each function that needs authentication on the page. The function identifier can be the code hash value corresponding to each function, etc. Here, the functions include coarse-grained data request or loading functions, as well as fine-grained data retrieval functions.

[0074] In this embodiment, page-level loading authentication can be implemented based on the code hash value corresponding to the page, function-level loading authentication can be implemented based on the code hash value corresponding to the data request or loading, and data-level loading authentication can be implemented based on the code hash value corresponding to the data retrieval function.

[0075] In summary, the page loading method of this disclosure can flexibly abstract the page into permission points according to the needs of the scenario, further improving the flexibility of multi-level authentication when recording the page.

[0076] Based on the above embodiments, in order to make those skilled in the art more aware of the authentication process when loading the page of this disclosure, the following example, which uses page permission points corresponding to various interfaces, is used to illustrate how to load the target page.

[0077] Specifically, when the target permission point includes a first functional permission point corresponding to the application interface, the function control corresponding to the first functional permission point is obtained, the target page is loaded, and the functional control is rendered on the target page, for example, such as... Figure 4 As shown, when the first functional permission point corresponds to the anchor deletion function interface, the anchor deletion page is loaded, and the deletion control is rendered in the anchor management page.

[0078] As mentioned in the above embodiments, data application permission points are subordinate permission points to the first functional permission points. Therefore, in the embodiments of this disclosure, data-level permission verification is further performed based on data application permission points. This data-level permission verification filters data at the data level, displaying only the portion of data that the user account has permission to view. A data source or data table can have p data-level data application permission points, where each data application permission point corresponds to an application data unit in the data source (which can be obtained through page hardcoding, etc.). This requires the permission system to provide a filtering strategy for the user account having z (z∈p) data application permission points, enabling the data system to filter application data when querying it, returning only the portion of application data that the user account has permission to view to the front end for display.

[0079] Therefore, in one embodiment of this disclosure, when the target permission point includes at least one first data application permission point corresponding to the first functional permission point, the application data corresponding to the first functional permission point is loaded according to the at least one first data application permission point.

[0080] In some possible implementations, as mentioned above, a filtering strategy is used to filter application data that the target user account does not have permission for. Specifically, this involves identifying the second set of data application permission points in the page permission point set, excluding the first set of data application permission points, filtering the application data corresponding to the second set of data application permission points from the application data corresponding to other data application permission points, and loading the filtered application data. This loading can be based on the target user account's loading request or can be directly loaded into the background cache.

[0081] For example, first obtain the first set of data application permission points that the target user account has permission to access. To determine the second data application permission point set M in the page permission point set, refer to... Figure 5 ,beg Filter application data based on N.

[0082] In other possible embodiments, the application data corresponding to the first data application permission point is loaded directly. In this embodiment, the application data corresponding to the first data sub-permission point is loaded from the application data corresponding to the data application permission point in the page permission point set. The application data corresponding to other data application permission points without permissions is not loaded. Similarly, the loading here can be based on the loading request of the target user account, or it can be directly loaded into the background cache.

[0083] When the target permission point includes a second functional permission point corresponding to the extended business interface, the second functional permission point does not need to request business data from the system, but directly loads and unloads the web page data in the target page. This web page data includes, but is not limited to, images, advertising videos, etc.

[0084] In this embodiment, the webpage data corresponding to the second functional permission is obtained, the target page is loaded, and the webpage data is rendered on the target page.

[0085] In summary, the page loading method of this disclosure abstracts page permissions into permission points according to the interface. Based on the abstract permission point types, it realizes unified authentication of three levels of permissions in the system environment: page-level permission authentication, function-level permission authentication, and data-level permission authentication, thus satisfying the flexibility of authentication during page loading.

[0086] To implement the above embodiments, this disclosure also provides a page loading device. Figure 6 This is a schematic diagram of the structure of a page loading device according to an embodiment of the present disclosure, as shown below. Figure 6 As shown, the page loading device includes: a first acquisition module 610, a second acquisition module 620, and a loading module 630, wherein,

[0087] The first acquisition module 610 is used to obtain the set of page permission points of the target page in response to the target user account's request to load the target page;

[0088] The second acquisition module 620 is used to acquire the set of user permission points of the target user account;

[0089] Loading module 630 is used to obtain the target permission point that matches the user permission point set from the page permission set, and load the target page based on the target permission point.

[0090] In one embodiment of this disclosure, when the target permission point includes a first functional permission point corresponding to the application programming interface, the loading module 630 is specifically used for:

[0091] Obtain the functional control corresponding to the first functional permission point;

[0092] Load the target page and render the functional controls on the target page.

[0093] In one embodiment of this disclosure, when the target permission point includes at least one first data application permission point corresponding to the first functional permission point, the loading module 630 is specifically used for:

[0094] Load application data corresponding to the first functional permission point based on at least one first data application permission point.

[0095] In some possible embodiments, the loading module 630 is used for:

[0096] Determine the other data application permission points in the second data application permission point set, excluding the first data application permission point;

[0097] Filter the application data corresponding to the second data application permission point from the application data corresponding to other data application permission points, and load the filtered application data.

[0098] In some other possible embodiments, the loading module 630 is used to: load the application data corresponding to the first data sub-permission point from the application data corresponding to the data application permission point in the set of page permission points.

[0099] In one embodiment of this disclosure, when the target permission point includes a second functional permission point corresponding to the extended business interface, the loading module 630 is used to: obtain the web page data corresponding to the second functional permission;

[0100] Load the target page and render the web page data on the target page.

[0101] The page loading device provided in this disclosure can execute the page loading method provided in any embodiment of this disclosure, and has the corresponding functional modules and beneficial effects of the execution method. Specific execution details will not be repeated here.

[0102] To implement the above embodiments, this disclosure also proposes a computer program product, including a computer program / instructions, which are executed by a processor using the page loading method provided in any embodiment of this disclosure.

[0103] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure.

[0104] The following is a detailed reference. Figure 7 The diagram illustrates a structural schematic suitable for implementing the electronic device 700 in the embodiments of this disclosure. The electronic device 700 in the embodiments of this disclosure may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 7 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0105] like Figure 7 As shown, the electronic device 700 may include a processing unit (e.g., a central processing unit, a graphics processor, etc.) 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage device 708 into a random access memory (RAM) 703. The RAM 703 also stores various programs and data required for the operation of the electronic device 700. The processing unit 701, ROM 702, and RAM 703 are interconnected via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0106] Typically, the following devices can be connected to I / O interface 705: input devices 706 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 707 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 708 including, for example, magnetic tapes, hard disks, etc.; and communication devices 709. Communication device 709 allows electronic device 700 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 7An electronic device 700 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0107] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication device 709, or installed from storage device 708, or installed from ROM 702. When the computer program is executed by processing device 701, it performs the functions defined in the page loading method of embodiments of this disclosure.

[0108] It should be noted that the computer-readable medium described in this disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this disclosure, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0109] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0110] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0111] The aforementioned computer-readable medium carries one or more programs. When these programs are executed by the electronic device, the electronic device: in response to a target user account's request to load a target page, obtains a set of page permission points for the target page, obtains a set of user permission points for the target user account, and then obtains a target permission point from the page permission set that matches the user permission point set, and loads the target page based on the target permission point. Thus, by abstracting page functions into permission points and performing multi-level loading authentication based on these permission points, unified multi-level authentication is achieved, ensuring page loading efficiency while flexibly meeting multi-level loading authentication requirements.

[0112] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0113] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0114] The units described in the embodiments of this disclosure can be implemented in software or hardware. The names of the units are not, in some cases, intended to limit the specific unit.

[0115] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0116] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

Claims

1. A page loading method, characterized in that, Includes the following steps: In response to a target user account's request to load a target page, obtain the set of page permission points for the target page; Obtain the set of user permission points for the target user account; When there is a target permission point in the page permission set that matches the user permission point set, the target page is loaded according to the target permission point. The target permission point includes a first functional permission point corresponding to the application interface and at least one first data application permission point corresponding to the first functional permission point. There are first functional permission points that do not have a corresponding first data application permission point. If no target permission point in the set of page permissions matches the set of user permission points, the target page will not be loaded for the target user account.

2. The method as described in claim 1, characterized in that... The step of loading the target page based on the target permission point includes: Obtain the functional control corresponding to the first functional permission point; Load the target page and render the functional controls on the target page.

3. The method as described in claim 2, characterized in that, The step of loading the target page based on the target permission point includes: The application data corresponding to the first functional permission point is loaded according to the at least one first data application permission point.

4. The method as described in claim 3, characterized in that, The step of loading application data corresponding to the first functional permission point according to the at least one first data application permission point includes: Determine the other data application permission points in the second data application permission points of the page permission point set, excluding the first data application permission point; Filter the application data corresponding to the second data application permission point that corresponds to the application data corresponding to the other data application permission points, and load the filtered application data.

5. The method as described in claim 3, characterized in that, The step of loading application data corresponding to the first functional permission point according to the at least one first data application permission point includes: Load the application data corresponding to the first data sub-permission point from the application data corresponding to the application data application permission point in the set of page permission points.

6. The method as described in claim 2 or 3, characterized in that, When the target permission point includes a second functional permission point corresponding to the extended business interface, loading the target page according to the target permission point includes: Retrieve the webpage data corresponding to the second function permission; Load the target page and render the webpage data on the target page.

7. A page loading device, characterized in that, include: The first acquisition module is used to acquire the set of page permission points of the target page in response to the target user account's request to load the target page; The second acquisition module is used to acquire the set of user permission points of the target user account; A loading module is configured to load the target page according to the target permission point when there is a target permission point in the page permission set that matches the user permission point set, wherein the target permission point includes a first functional permission point corresponding to the application interface and at least one first data application permission point corresponding to the first functional permission point, wherein there are first functional permission points that do not have a corresponding first data application permission point. The loading module is further configured to refuse to load the target page to the target user account when there is no target permission point in the page permission set that matches the user permission point set.

8. The apparatus as claimed in claim 7, characterized in that, When the target permission point includes a first functional permission point corresponding to the application interface, the loading module is specifically used for: Obtain the functional control corresponding to the first functional permission point; Load the target page and render the functional controls on the target page.

9. An electronic device, characterized in that, The electronic device includes: processor; Memory used to store the processor's executable instructions; The processor is configured to read the executable instructions from the memory and execute the instructions to implement the page loading method according to any one of claims 1-6.

10. A computer-readable storage medium, characterized in that, The storage medium stores a computer program for executing the page loading method according to any one of claims 1-6.

Images