CN113190322A

CN113190322A - Page acquisition method, related equipment and medium

Info

Publication number: CN113190322A
Application number: CN202110575203.3A
Authority: CN
Inventors: 林梅贞
Original assignee: Tencent Cloud Computing Beijing Co Ltd
Current assignee: Tencent Cloud Computing Beijing Co Ltd
Priority date: 2021-05-25
Filing date: 2021-05-25
Publication date: 2021-07-30

Abstract

The embodiment of the application discloses a page acquisition method, related equipment and a medium, which can be applied to the technical field of cloud. The method comprises the following steps: and acquiring the working page configuration information corresponding to the characteristic information of the login user, so as to determine a target working page correspondingly displayed by the login user according to the working page configuration information, wherein the target working page comprises at least one navigation option of a webpage workbench, and returning the target working page corresponding to the working page configuration information to the client. Due to the fact that at least one webpage workbench is introduced into the working page, the requirement of a user for the workbench can be met, and user experience is improved. The embodiment of the application can be applied to industry application in the technical field of cloud, and particularly can be applied to government affair office application, for example, a government affair workbench page is obtained through the application. The embodiment of the present application can also be applied to the field of blockchains, for example, the configuration information of the working page corresponding to each login user in the embodiment of the present application is stored in a node of a blockchain.

Description

Page acquisition method, related equipment and medium

Technical Field

The present application relates to the field of cloud technologies, and in particular, to a page acquisition method, a related device, and a medium.

Background

With the rapid development of internet technology, various internet products for offices (such as office software, financial systems, etc.) are gradually developed. Internet products for office use typically have a native workstation, such as a government workstation for a government office application, so that each user in the collective can perform work tasks through applications in the native workstation.

However, the inventors found in practice that: the current native workstation has a fixed page display mode, cannot meet the requirements of different users, and has a too limited native application function.

Disclosure of Invention

The embodiment of the application provides a page acquisition method, related equipment and a medium, which are beneficial to expanding functions in a workbench so as to meet the requirements of different users for the workbench.

In one aspect, an embodiment of the present application provides a page obtaining method, where the method includes:

receiving a first acquisition instruction aiming at a working page sent by a client, wherein the first acquisition instruction carries characteristic information of a login user in the client;

acquiring working page configuration information corresponding to the characteristic information of the login user, wherein the working page configuration information is used for indicating a target working page correspondingly displayed by the login user, and the target working page comprises navigation options of at least one webpage workbench;

and returning the target working page corresponding to the working page configuration information to the client.

On the other hand, an embodiment of the present application provides another page obtaining method, including:

sending a first acquisition instruction aiming at a working page to a server, wherein the first acquisition instruction carries the characteristic information of a login user, and the server is used for acquiring a target working page corresponding to the characteristic information of the login user;

and receiving and displaying a target work page corresponding to the characteristic information returned by the server, wherein the target work page comprises navigation options of at least one webpage workbench.

In another aspect, an embodiment of the present application provides a page obtaining apparatus, where the apparatus includes:

the system comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving a first acquisition instruction aiming at a working page sent by a client, and the first acquisition instruction carries characteristic information of a login user in the client;

the processing module is used for acquiring working page configuration information corresponding to the characteristic information of the login user, wherein the working page configuration information is used for indicating a target working page correspondingly displayed by the login user, and the target working page comprises navigation options of at least one webpage workbench;

and the sending module is used for returning the target working page corresponding to the working page configuration information to the client.

the system comprises a sending module, a processing module and a processing module, wherein the sending module is used for sending a first acquisition instruction aiming at a working page to a server, the first acquisition instruction carries characteristic information of a login user, and the first acquisition instruction is used for requesting a target working page corresponding to the characteristic information of the login user;

the receiving module is used for receiving the target work page corresponding to the characteristic information returned by the server;

and the display module is used for displaying the target work page, and the target work page comprises navigation options of at least one webpage workbench.

In yet another aspect, an embodiment of the present application provides a server, which includes a processor and a memory, the processor and the memory being interconnected, wherein the memory is used for storing computer program instructions, and the processor is configured to perform the following steps:

In yet another aspect, an embodiment of the present application provides a client, including a processor and a memory, the processor and the memory being interconnected, wherein the memory is used for storing computer program instructions, and the processor is configured to perform the following steps:

sending a first acquisition instruction aiming at a working page to a server, wherein the first acquisition instruction carries the characteristic information of a login user, and the first acquisition instruction is used for requesting a target working page corresponding to the characteristic information of the login user;

In yet another aspect, the present application provides a computer-readable storage medium having computer program instructions stored therein, which when executed by a processor, are configured to perform the method of any aspect.

The method and the device for displaying the webpage work page receive a first obtaining instruction aiming at the work page sent by a client, obtain work page configuration information corresponding to the characteristic information of a login user, determine a target work page correspondingly displayed by the login user according to the work page configuration information, wherein the target work page comprises at least one navigation option of a webpage workbench, and return the target work page corresponding to the work page configuration information to the client. Due to the fact that at least one webpage workbench is introduced into the working page, the functions in the workbench can be expanded, the requirement of a user for the workbench can be met, and user experience is improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a schematic structural diagram of a page acquisition system provided in an embodiment of the present application;

fig. 2 is a schematic flowchart of a page acquisition method provided in an embodiment of the present application;

FIG. 3 is a schematic diagram illustrating an effect of a work page provided by an embodiment of the present application;

FIG. 4 is a schematic diagram illustrating an effect of a web workbench according to an embodiment of the present disclosure;

fig. 5 is a schematic diagram illustrating an effect obtained by a web workbench according to an embodiment of the present application;

fig. 6 is a schematic flowchart of an authority judgment provided in an embodiment of the present application;

fig. 7 is a schematic flowchart of a configuration of web application permissions according to an embodiment of the present application;

fig. 8 is a schematic flowchart of another page obtaining method provided in the embodiment of the present application;

FIG. 9 is a schematic diagram illustrating an effect of a target work page according to an embodiment of the present disclosure;

FIG. 10 is a schematic diagram illustrating an effect of a conference assistant interface provided in an embodiment of the present application;

FIG. 11 is a schematic diagram illustrating an effect of a primary workbench according to an embodiment of the present application;

FIG. 12 is a schematic diagram illustrating an effect of a configuration interface of a native workbench according to an embodiment of the present disclosure;

FIG. 13 is a schematic diagram illustrating an effect of a native workbench page template according to an embodiment of the present disclosure;

FIG. 14 is a schematic diagram illustrating an effect of a native workbench page provided in an embodiment of the present application;

fig. 15 is a schematic structural diagram of a page obtaining apparatus according to an embodiment of the present application;

fig. 16 is a schematic structural diagram of a page obtaining apparatus according to an embodiment of the present application;

fig. 17 is a schematic structural diagram of a server provided in an embodiment of the present application;

fig. 18 is a schematic structural diagram of a client according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

The embodiment of the application provides a page acquisition scheme, which can provide customized workbenches for different users through the user-defined workbench, so that the effect of 'thousands of people and thousands of faces' can be shown. For example, the data presentation may be customized at the native workbench; as another example, this may be accomplished by customizing a web workbench; as another example, this may be accomplished by the coexistence of a native workbench and a web workbench. Optionally, the target work page corresponding to the login user may be determined according to feature information of different login users, where the target work page may include information of at least one web page workbench and a native workbench, and the native workbench page may define data by itself. Therefore, the corresponding webpage workbench can be obtained according to the characteristic information of the login user, the requirement of the user for the workbench can be met, and the user experience is improved.

In the present application, the workstation may refer to a platform for performing office operations in an internet product (such as office software, financial system, etc.) used for office, for example, an approval process is performed through approval application in the workstation. The native workbench and the web page workbench such as the HTML5 workbench and the like in the application belong to a workbench.

In a possible implementation manner, the present application scheme may be applied to a page obtaining system, please refer to fig. 1, and fig. 1 is a schematic structural diagram of a page obtaining system provided in an embodiment of the present application. As shown in FIG. 1, the page retrieval system may include a client and a server. The client can send an acquisition instruction (assumed to be a first acquisition instruction) for the working page to the server, the server can receive the first acquisition instruction for the working page sent by the client, and then can acquire the working page configuration information corresponding to the feature information of the login user, and return a target working page corresponding to the working page configuration information to the client, and the client can receive and display the target working page corresponding to the feature information returned by the server. For a specific implementation process, reference may be made to the following description in the embodiments corresponding to fig. 2 and fig. 8, which is not described herein again. Optionally, the client may be a terminal, and the terminal may be a smart phone, a tablet computer, a notebook computer, a desktop computer, and the like, but is not limited thereto. The server may also be referred to as a server or other name. Optionally, the server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a network service, cloud communication, a middleware service, a domain name service, a security service, a CDN, a big data and artificial intelligence platform, and the like. The client and the server may be directly or indirectly connected through wired or wireless communication, and the application is not limited herein.

The technical scheme of the application can be applied to the field of block chains, and the block chains are novel application modes of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism and an encryption algorithm. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. For example, information such as work page configuration information and web page application permission information corresponding to each login user in the embodiment of the present application may be stored in a node of the block chain, so as to obtain corresponding information according to an instruction sent by the client.

It is to be understood that the foregoing scenarios are only examples, and do not constitute a limitation on application scenarios of the technical solutions provided in the embodiments of the present application, and the technical solutions of the present application may also be applied to other scenarios. For example, as can be known by those skilled in the art, with the evolution of system architecture and the emergence of new service scenarios, the technical solution provided in the embodiments of the present application is also applicable to similar technical problems.

Based on the above description, an embodiment of the present application provides a page acquisition method. Referring to fig. 2, fig. 2 is a schematic flowchart of a page obtaining method according to an embodiment of the present disclosure. The method can be applied to the server and executed by the server. The method may comprise steps S201-S203.

S201, receiving a first acquisition instruction aiming at a work page sent by a client.

The first obtaining instruction may be an instruction for instructing to obtain a work page, and the work page may be a page of an internet product (such as office software, financial system, and the like) for office in the client. In the following description, the internet product for office may be referred to as a target office application. For example, the target office application may be a business WeChat, a government WeChat, or the like. The work page may include a navigation bar that may include a plurality of navigation options, which may also be referred to as tab bars, options bars, menu bars, etc. in some scenarios, which may also be referred to as tab, to-be-selected, menu options. For example, referring to fig. 3, fig. 3 is a schematic diagram illustrating an effect of a work page provided by an embodiment of the present application, in which a navigation bar may be referred to as 301, and the navigation bar includes 4 navigation options (referred to as 302).

Optionally, the first obtaining instruction may carry the feature information of the login user in the client, or the server may obtain the feature information of the login user in another manner. The login user may be a user who logs in the client through an account password or a code scanning login, for example, a user who logs in the target office application. Optionally, the feature information of the logged-in user may include information such as a user's responsibility, an organization to which the user belongs, a user's position, a tag that the user has, and a user's preference, which is not limited herein. Alternatively, the logged-on user may belong to one or more groups, which may also be groups of multiple people, such as companies, businesses, institutions, classes, schools, and the like. Each person in the group can correspond to one user account, and each user account can be called a login user after being logged in the client.

S202, obtaining the work page configuration information corresponding to the characteristic information of the login user.

The work page configuration information can be used for indicating a target work page correspondingly displayed by a login user, and the target work page can comprise navigation options of at least one webpage workbench. Optionally, the configuration information of the working page may further include the number of navigation options of the web workbench in the target working page, the configuration information of the working page may further include the number of navigation options and option names in the navigation bar, the configuration information of the working page may further include location information of the navigation options in the navigation bar, and the like, which is not limited herein. The target work page may be a work page correspondingly displayed by the login user, for example, if the work page configuration information corresponding to the feature information of the login user indicates that the target work page has 1 navigation option of the web page workbench, then the target work page correspondingly displayed by the login user has 1 navigation option of the web page workbench.

The web page workbench can be a workbench formed by web pages, namely an office operation platform for realizing the work requirement of the user in the form of the web pages. For example, the Web page workbench can be an HTML5 workbench, HTML5 is a language description mode for constructing Web contents, and the HTML5 workbench is a platform for constructing a Web page through an HTML5 description language so as to perform office operations; for another example, the web page workbench may also be an applet workbench, an applet is an application that can be used without downloading and installing, and the applet workbench is a platform that jumps to an applet page for office operations, and is not limited herein. It can be understood that the page of the web page workbench can define the presentation style, User Interface (UI), product logic, etc. of the web page workbench according to the User requirement, so that the web page workbench can better meet the User requirement. For example, please refer to fig. 4, fig. 4 is a schematic diagram illustrating an effect of a web page workbench according to an embodiment of the present application, in which some web page applications may be included, as shown in 401; the web page workbench may further include a user information display area, where the user information display area may display part of user information of the login user, as shown in 402; the web page workbench may also include a top bar, as shown at 403.

In one possible implementation, the work page configuration information may be configuration information for the work page configured by an administrator (developer) in the target collective. For example, by receiving a work page configuration instruction for each user account sent by the management client, the work page configuration information corresponding to each user account is extracted according to the work page configuration instruction. And each user account is a user account in the target collective, and the working page configuration instruction is used for indicating an instruction for configuring a working page of each user account. For example, the number and the option name of the navigation options in the navigation bar corresponding to each user account are configured, the location information of the navigation options in each navigation bar is configured, and the like, which is not limited herein.

Optionally, the user account under the target group may be further divided into a plurality of user groups, a work page configuration instruction for each user group sent by the management client is received, and work page configuration information corresponding to each user group is extracted according to the work page configuration instruction. The user accounts under the target group are divided into a plurality of user groups, and the user groups can be grouped according to information such as responsibility of each user account, organization to which the user accounts belong, posts corresponding to the user accounts, labels corresponding to the user accounts, preferences corresponding to the user accounts and the like. The working page configuration instruction for each user group is used for indicating an instruction for configuring for each user group in the management client, so that the same working page information can be configured for the user accounts in each user group, and the workload of the management client is reduced. Optionally, the same work page configuration information may be configured for all user accounts in the target group.

And S203, returning a target work page corresponding to the work page configuration information to the client.

The target work page corresponding to the work page configuration information returned to the client may be page data of the target work page returned to the client, such as data of an option name of a navigation option in a page navigation bar of the target work page, location information of the navigation option in the navigation bar, image information of the target work page, and the like, so that when the client receives the page data of the target work page, the client displays the target work page.

It can be understood that, in a set, the work configuration information corresponding to each person may be the same or different, and the target work page corresponding to the login user may be determined by obtaining the web workbench configuration information corresponding to the feature information of the login user. In some scenarios, one or more web workstations may also be fixedly configured for each user in a certain group, so that after receiving a first acquisition instruction for a work page sent by a client, a work page corresponding to information of the fixedly configured web workstation may be directly fed back to the client.

In a possible implementation, the at least one web page workbench in the target work page may include a target web page workbench, it is understood that the target web page workbench may be any one of the at least one web page workbench, and then the server may further perform the following steps: receiving a second acquisition instruction which is sent by the client and aims at the target webpage workbench, and acquiring identity information of a login user in the second acquisition instruction; when the identity information of the login user passes the verification, acquiring webpage workbench configuration information corresponding to the characteristic information of the login user; and returning a target webpage workbench page corresponding to the webpage workbench configuration information to the client.

The second acquiring instruction may be an instruction for instructing to acquire a target web page workbench. The identity information of the logged-in user is the unique identification of the logged-in user in a collective, and the identity information can also be called UserID or other names. The web page workbench configuration information may be used to indicate information corresponding to the feature information of the login User and specific to a web page of the web page workbench, the web page workbench configuration information may include information of a web page application in the web page workbench, for example, a name of the web page application configured in the web page workbench, a display mode of the configured web page application, an icon of the web page application, and the like, the web page workbench configuration information may further include a User Interface (UI) of the web page workbench, for example, the web page workbench may include a region for displaying information of the login User (such as a name of the login User) and color information of the Interface of the login User (such as a background color, a color of a target region, and the like, which is not limited herein). The target webpage workbench page is used for indicating a page which is correspondingly displayed after the navigation option of the target webpage workbench is selected in the target webpage. It can be understood that, in a set, the configuration information of the web workbench corresponding to each person may be the same or different, and the configuration information of the web workbench corresponding to the feature information of the login user needs to be acquired, so as to determine the target web workbench page corresponding to the login user.

Optionally, the identity information of the login user in the second obtaining instruction may be obtained through an open authorization 2.0(oauth2.0) verification interface, so that the login process is avoided in the process of obtaining the target web page workbench through the client. Optionally, the second obtaining instruction indicates that an obtained Uniform Resource Locator (URL) of the target web page workbench should be consistent with a preset trusted domain name, where the trusted domain name is used to indicate a safe and trusted domain name set corresponding to a target group to which the login user belongs, if a redirected callback link address (redirect _ uri) in the second obtaining instruction has a port number, the port number should also be set when the trusted domain name is set, and if the trusted domain name is inconsistent with the redirect _ uri, after receiving the second obtaining instruction, sending a prompt message to the client that sends the second obtaining instruction to prompt that domain name verification fails (redirect _ uri parameter is wrong).

Optionally, verifying the identity information of the login user may include receiving the validity of information such as a uniform resource identifier (uri), a device id (device id), and the like of the client for the target web page workbench, and may also include verifying whether the identity information of the login user belongs to a target group, and may also include verifying whether the login user has a right to acquire the target web page workbench, and the like. Optionally, after receiving the second obtaining instruction, the authorization CODE may be generated according to the URL of the target web page workbench in the second obtaining instruction, and the authorization CODE is returned to the client, so that the target web page workbench background obtains the identity information (UserID) of the login user according to the CODE, and thus the server returns the data returned by the target web page workbench background to the client, the target web page workbench is a module or a program capable of managing, setting, and modifying the data, and the web page workbench may be applied to the server, or may be applied to a server different from the server, which is not limited herein. For example, please refer to fig. 5, and fig. 5 is a schematic diagram illustrating an effect obtained by a web workbench according to an embodiment of the present application. The acquisition process may include a client, a target office application back-office, an API interface, a target web page workbench background, etc., where a user initiates an acquisition instruction for the target web page workbench through the client (i.e., step S501), and then the target office application back-office may verify the validity of the information such as URI, Deviceid, etc. in the second acquisition instruction (i.e., step S502), and when the verification is passed, the target office application back-office verifies the URI and generates an authorization CODE (CODE) (i.e., step S503), and then returns a REDIRECT jump address (i.e., step S504), such as https: REDIRECT _ URI & CODE, to which the client jumps in a 302 jump manner (i.e., step S505), thereby initiating an access request into the target web page workbench background, and the target web page workbench requests to verify the CODE through the API interface (i.e., step S506), and when the verification is successful, and returning the identity information (userid) and the device id (deviceid) of the login user to the target web page workbench background (step S507), so that the target web page workbench background finally returns the data of the target web page workbench page to the client (step S508).

In a possible implementation manner, if there is a certain time overhead in acquiring the identity information of the logged-in user through (oauth2.0), the identity information of the logged-in user may be acquired through the following steps: detecting a uniform resource identifier (URL) preset for a target webpage working page as a page address corresponding to the target group; when a second acquisition instruction for a target webpage workbench page is received, checking whether data (cookie) which identifies the identity information of the login user and is stored on the client exists; if no matched cookie exists, the OAuth2.0 verification link is redirected, after the identity information of the login user is obtained, cookie information for identifying the identity information of the login user is stored in the server, after the identity information of the login user is obtained according to the cookie, the identity information of the login user is verified, and when the verification is passed, a target webpage workbench page corresponding to the login user is returned to the client. Therefore, time consumption can be reduced in a scene of frequently acquiring identity information of a login user.

In a possible implementation manner, the target web page workbench may include at least one web page application, and before returning the target web page workbench page corresponding to the web page workbench configuration information to the client, web page application permission information for the login user may also be obtained, where the web page application permission information is used to indicate a permission that the login user has for each web page application, and then returning the target web page workbench page corresponding to the web page workbench configuration information to the client may include: and returning a target webpage of the webpage workbench corresponding to the webpage application permission information and the webpage workbench configuration information to the client.

The web application is used to indicate an application in the web workbench for providing office functions to the user, for example, the web application may be linked to the web workbench through an API interface. Optionally, the web application may be a collective customized application to which the login user belongs. The webpage application permission information is used for indicating the permission of a login user for each webpage application, the permission can comprise access permission, operation permission, data permission and the like, and the access permission is used for indicating whether the login user can access the webpage application; the operation authority is used for indicating which operations can be performed by the login user in the webpage application, for example, in the approval application, the login user can submit an approval application but cannot approve the application of others; the data authority is used for indicating which data in the webpage can be acquired by the login user, such as the data that the login user can acquire the contact information of the client, but cannot acquire the account information of all the people in the group. Then returning the web application permission information and the target web workbench page corresponding to the web workbench configuration information to the client, when determining the corresponding target web workbench page according to the web workbench configuration information, determining the display permission of each web application in the target web workbench according to the web user permission information, if detecting that the login user does not have the access permission for the target web application (the target web application can be any web application in the target web workbench), hiding the target web application from the target web workbench so as not to display, and displaying the icon or identifier of the target web application in the target web workbench, but the login user can not access, such as displaying the icon or identifier of the target web application in gray or dark color, or to indicate no access with text at an icon or logo of the target web application. The method comprises the steps of obtaining information of a target webpage workbench page based on webpage workbench configuration information of a login user, determining a display method of each webpage application in the target webpage workbench according to webpage application authority information of the login user, determining the target webpage workbench, and returning the target webpage workbench page to a client.

In a possible implementation manner, when a third obtaining instruction for a target webpage application sent by a client is received, webpage application permission information of the login user for the target webpage application is obtained, and a corresponding target webpage application page is returned to the client according to the webpage application permission information for the target webpage application. The third obtaining instruction for the target web application may be an operation performed after entering the target web application. For example, the target web application is an application for querying information of user accounts in the target group (user information query), if the third acquisition instruction indicates to acquire information of all user accounts in the target group, the server may determine, according to the web application permission information of the user, whether a login user carried in the third acquisition instruction has permission to acquire the information of all user accounts in the target group, if so, return the information of all user accounts to the client, if not, return a prompt message to prompt that the login user has no permission, if the login user only has permission to query information of a part of user accounts, correspondingly return information of the part of user accounts to the client, and prompt that the login user only has permission to query information of a part of user accounts.

Optionally, the judgment of the authority of the login user may be implemented through an authority judgment interface, for example, the authority judgment is performed through a rights/check interface, a process of the authority judgment may refer to fig. 6, and fig. 6 is a schematic flow chart of the authority judgment provided in the embodiment of the present application. As shown in fig. 6, in the permission determination process, the web application calls a permission determination interface to perform permission check through an Access Control System (ACS) 3A, where the authority 3A refers to an account (account), a permission (authority), and an authentication (authorization). For example, the interface ^ right/check is called, and the authority judgment basic information in the third acquisition instruction is acquired (step S601), namely the user code (account), the specific object (resource) which wants to acquire the authority, the action (action) and other information; then, the 3A access control system filters a hit principle (Policy) according to the authority judgment basic information (account, resource, action) (i.e., step S602), so as to obtain an authority judgment result according to the hit Policy (i.e., step S603). For example, if the hit Policy includes a plurality of conditions (conditions), the relationship between the conditions is an and relationship, and the effectiveness of the deny (deny) is prior to the allow (allow), if one of the conditions is deny, the permission determination result is no permission (facele); as another example, if there is no condition in the hit Policy, if the policies are all allowed (allow), then the result is right (true); if the Policy contains the effectiveness, the result is that the authority (false) is not available, and finally the authority judgment result is determined to be that the authority (true) or the authority (false) is available. After the permission judgment result is obtained, the permission judgment result is returned to the server (i.e., step S604). Wherein the basic element of the Policy is the basic composition layer part of the authority determination process, for example, as shown in table 1 below, the basic element may include one or more of the following.

Table 1:

element name	Description of the invention
		Effect (Effect)	Authorization effectiveness includes two types, permit (low) and Deny (Deny).
Behavior (Action)	Behavior refers to operations on a particular resource.
		Resource (Resource)	A resource refers to a specific object that is authorized.
Limitation (Condition)	The constraint refers to a constraint that the authorization takes effect.

Optionally, the user account under the target group may be further divided into a plurality of user groups, a web application permission configuration instruction for each user group sent by the management client is received, and the web application permission corresponding to each user group is extracted according to the web application permission configuration instruction. The user accounts under the target group are divided into a plurality of user groups, and the user groups can be grouped according to information such as responsibility of each user account, organization to which the user accounts belong, posts corresponding to the user accounts, labels corresponding to the user accounts, preferences corresponding to the user accounts and the like. The web page application authority information may include access authority, operation authority, or data authority. For example, please refer to fig. 7, and fig. 7 is a schematic flowchart of a process for configuring a web application permission provided in an embodiment of the present application, where a user account may be divided into a plurality of user groups according to information such as organization, position, and label of the user account, that is, the user account belongs to a user group, so that the same or different permissions may be assigned to each user group, so that the user group has the permission, and permission management in a target group is implemented.

In a possible implementation, the web workbench can also be regarded as an application in a target office application, and a developer (manager) is required to have application development capability when constructing the web workbench, for example, the web development technology with HTML5 can customize a web page presentation style, UI and product logic, and the like; for another example, oauth2.0 webpage authorization can be used to obtain the information of the login user; as another example, with front-end page JSSDK capability provided using target office applications; as another example, the option call to "open application" in JSSDK is used to reuse the application management hierarchy in the target office application; as another example, a < title > tag in an html page is used as a display name of a workbench page, and the like, without limitation. Therefore, developers can design the webpage workbench meeting the user requirements according to the user requirements of the target set, and the user experience is improved.

In one possible implementation, when a user logs in a user account in a target office application, it may be determined whether the logged-in user has a web workbench visible right, and if the logged-in user has the web workbench visible right, a target work interface with a web client is returned to the client. Optionally, in order to improve efficiency of obtaining the web workbench at the client, when the user logs in the target office application, a user account with a visible right of the web workbench is obtained, and the configuration information of the web workbench corresponding to the user account is written into the cache region, when a second obtaining instruction, which is sent by the client of the login user with the right of the web workbench and is directed to the target web workbench, is detected, the cache region is read, if the configuration information of the web workbench corresponding to the user account exists in the cache region, the page of the target web workbench is directly returned, and if the cache region does not have the configuration information of the web workbench corresponding to the user account, a loading interface (loading interface) is returned, so that the server consumes time to obtain the page of the target web workbench and returns the page of the target web workbench to the client.

The method and the device for displaying the webpage work page receive a first obtaining instruction aiming at the work page sent by a client, obtain work page configuration information corresponding to the characteristic information of a login user, determine a target work page correspondingly displayed by the login user according to the work page configuration information, wherein the target work page comprises at least one navigation option of a webpage workbench, and return the target work page corresponding to the work page configuration information to the client. Due to the fact that at least one webpage workbench is introduced into the working page, the requirement of a user for the workbench can be met, and user experience is improved.

Referring to fig. 8, fig. 8 is a schematic flowchart of another page obtaining method according to an embodiment of the present disclosure. The method can be applied to the client and executed by the terminal. The method may comprise steps S801-S802.

S801, sending a first acquisition instruction for the working page to a server.

The first obtaining instruction carries feature information of the login user, and the specific description may refer to the description related to the first obtaining instruction in step S201, which is not described herein again. The server may be the server for executing steps S201 to S203, and the server may be configured to obtain a target work page corresponding to the feature information of the login user.

In a possible implementation manner, the timing of sending the first obtaining instruction to the server may be that, when the user needs to obtain the target work page from the server after logging in the target office application through the account password or the code scanning, the client sends the first obtaining instruction for the work page to the server after detecting that the user logs in the target office application successfully. The timing of sending the first obtaining instruction to the server may also be that, after the user logs in the target office application, if the user does not perform an operation in the obtained target work page beyond the preset time and needs to refresh the target work page, the client detects that there is no operation instruction for the target work page beyond the preset time, and sends the first obtaining instruction to the server. The timing of sending the first obtaining instruction to the server may also be that, after the user logs in the target office application, if the target office application is opened again in the client, the first obtaining instruction is sent to the server.

And S802, receiving and displaying a target work page corresponding to the characteristic information returned by the server.

Wherein, the target work page comprises navigation options of at least one web page workbench. The target work page is a work page corresponding to the characteristic information of the login user. The related description of the feature information and the target workbench can refer to the related description in fig. 2, and is not described herein again.

In a possible implementation manner, after receiving the page data of the target work page returned by the server, the client may render according to the page data of the target work page and display in the client. For example, referring to fig. 9, fig. 9 is a schematic diagram illustrating an effect of a target work page provided by an embodiment of the present application, in which a navigation bar may be included, the navigation bar includes a plurality of navigation options, and the plurality of navigation options includes at least one navigation option of a web page workbench, for example, 901 in fig. 9 is a navigation option of a web page workbench.

In one possible embodiment, the navigation options of the at least one web page workbench may include a navigation option of a target web page workbench, and it is understood that the target web page workbench may be any one of the at least one web page workbench. Then, after step S802, the following steps may also be performed: when the selection operation of the navigation option aiming at the target webpage workbench in the target working page is detected, sending a second acquisition instruction aiming at the target webpage workbench to the server; and receiving and displaying the target webpage worktable page returned by the server. The selection operation of the navigation option for the target web page workbench may be to click the navigation option of the target web page workbench in the navigation bar for the user, or to obtain the target web page workbench page through the voice instruction, which is not limited herein. The target web page workbench page is determined by the web application permission information and the web page workbench configuration information corresponding to the login user, and the target web page workbench includes at least one web application, and the method for acquiring the target web page workbench page may refer to step S203 described above, which is not described herein again.

In a possible implementation manner, the target web page workbench may be an HTML5 workbench, and the adjustment of the HTML5 workbench page may be performed according to the page operation instruction of the login user, which may specifically include the following steps: receiving a page operation instruction of a user for an HTML5 workbench; adjusting the HTML5 workbench page according to the page setting operation indicated by the page operation instruction; the page setting operation indicated by the page operation instruction comprises one or more of the following operations: the location of the navigation options configuring the HTML5 workstation, the color of the target location in the HTML5 workstation, the option name of the navigation options configuring the HTML5 workstation. The page operation instruction may be a page operation instruction for the HTML5 workstation initiated by the login user in the setting interface for the HTML5 workstation page, and the page operation instruction may indicate a page setting operation for the HTML5 workstation. The position of the navigation option of the HTML5 workbench is configured to indicate the position of the navigation option of the HTML5 workbench in the navigation bar, and the position of the navigation option in the navigation bar can be used to indicate the relative position relationship (such as left-right relationship, top-bottom relationship) between a plurality of navigation options, and can also be used to indicate the spacing distance between a plurality of navigation options, which is not limited herein. For example, 4 navigation options in the navigation bar are sequentially called navigation option 1, navigation option 2, navigation option 3, and navigation option 4 from left to right, and if the position of the navigation option of the HTML5 workstation is navigation option 4 when the target work page is acquired, and if the page operation command for the HTML5 workstation is received to instruct to adjust the position of the navigation option of the HTML5 workstation to navigation option 3, the client configures the position of the navigation option of the HTML5 workstation to navigation option 3 according to the page operation command, and then the position of the navigation option of the HTML5 workstation is changed from navigation option 4 to navigation option 3. The color of the target position in the HTML5 workbench is configured to indicate the color for adjusting the target position in the HTML5 workbench, the target position may be any position in the HTML5 workbench, such as the top column of the HTML5 workbench (i.e. the top position in the page of the HTML workbench), the user information display area, and the like, the color may be any one of WEB standard color, CMYK color, RGB color, without limitation, and the color configured by the page operation command is displayed as a default color if the color is not the above standard color. For example, if the top column of the HTML5 workbench is red when the target work page is acquired, when the page operation command for the HTML5 workbench is received to adjust the top column of the HTML5 workbench to yellow, the client configures the top column of the HTML5 workbench to yellow according to the page operation command, and the color of the top column of the HTML5 workbench changes from red to yellow. The option names of the navigation options of the configuration HTML5 workstation are used to indicate the names of the navigation options of the adjustment HTML5 workstation. For example, when the option name of the navigation option of the HTML5 workstation is "workstation" when the target workstation is acquired, and when the page operation command for the HTML5 workstation is received to instruct to adjust the option name of the HTML5 workstation to "common workstation", and the option name of the navigation option of the HTML5 workstation configured by the client according to the page operation command is "common workstation", the option name of the navigation option of the HTML5 workstation configured by the client according to the page operation command is "common workstation", and the option name of the navigation option of the HTML5 workstation is changed from "workstation" to "common workstation".

Optionally, the client may further detect an operation instruction for the target work page, where the page operation instruction is used to indicate an initial navigation option for configuring the target work page, or determine initial access positioning of the target work page, that is, when the client accesses the target office application, the navigation option focused by the target work page and a page corresponding to the navigation option. The initial navigation option may be any one of the navigation options in the navigation bar.

Optionally, the page setting operation of the page operation execution instruction for the target working page and the HTML5 workbench may also be set by the management user end, that is, the page setting operation may be set by an administrator in the target group through the management client, for example, the administrator may customize, through the management client, whether to open the web workbench (default to on or off), and if a web workbench is to be opened, an application may be selected to be added in the "navigation bar application management" in the management page, and the application is the target web workbench; the administrator can configure the initial navigation option of the target work page through the management client, the default is navigation option 1, and the initial navigation option can be changed to other positions (such as navigation option 2, navigation option 3 and the like); the administrator can configure the position of the navigation option of the target webpage workbench through the management client, defaults to be at the position of the navigation option 4, and can change the position into other positions; the administrator can configure the color of the target position in the web workbench through the management client, and if the color is not adjusted, the color is displayed as a default color, and the default color can be any color.

Optionally, the configuration information for the HTML5 workbench may be stored in the working page configuration information and the web workbench configuration information corresponding to the feature information of the login user, so that when the target working page and the target web workbench page are obtained next time, the target working page and the target web workbench page corresponding to the page setting operation configuration indicated by the page operation instruction can be obtained.

In a possible implementation manner, a web application in a web workbench may substitute interfaces such as a message notification interface and an address book interface of a target office application to implement deep integration of the web application to the target office application, taking a conference assistant as an example, in the web workbench, a user may enter an interface corresponding to the conference assistant after clicking the conference assistant, so as to obtain conference information in the conference assistant interface, please refer to fig. 10, and fig. 10 is an effect schematic diagram of a conference assistant interface provided in an embodiment of the present application.

In a possible implementation manner, the target work page returned from the server may further include a navigation option of a native workbench, where the native workbench includes a plurality of native applications, and then after performing step S802, the following steps may be further performed: when the selection operation of the navigation option aiming at the native workbench in the target work page is detected, displaying a plurality of native applications in the native workbench in a target form; wherein the target form may include any one or more of: key data type, picture type, list type, and web page view. The native workstation may be a workstation originally owned by the target office application, wherein a plurality of native applications included therein are some basic office applications, and web page jumping is not required when the native web page workstation page is acquired. The selection operation of the navigation option for the native web page workbench can be performed by clicking the navigation option of the native web page workbench in the navigation bar for the user, and can also be performed by indicating and acquiring the native web page workbench page through a voice instruction, which is not limited herein. When the selection operation of the navigation option for the native workbench is detected, the native workbench page may be displayed, and a plurality of native applications in the native workbench page are presented in a target form, such as a key data type, a picture type, a list type, and a web page view, please refer to fig. 11, where fig. 11 is a schematic diagram of an effect of the native workbench according to an embodiment of the present application. The form of the key data type may be to display key data in a native application of a native workbench page, and is suitable for a native application that needs to disclose the key data in time, as shown in (1) in fig. 11, the native workbench page may display data of example 1 as 2, for example, the number of people waiting for approval (to be approved) is 2, data of example 2 as 4, for example, the number of jobs to be approved (to be approved) is 4, data of example 3 as 45, for example, the number of people with recorded achievements (recorded) is 45, data of example 4 as 98, and for example, the comprehensive evaluation and itemization (comprehensive evaluation) of a logged-in user as 98. The picture type may be a picture in a native application for displaying a native workbench page, which is suitable for notifying or promoting the displayed native application, as shown in (2) in fig. 11, for example, the native application may be an information push application, and a matching picture of the picture or article for preferentially displaying the information pushed in the information push application is provided, so that a login user can quickly obtain the latest information pushed by the application from the picture. The list type may be in the form of data in the native application showing the native workbench page in the form of a list, as shown in (3) in fig. 11, and the information or data in the plurality of native applications (e.g., example 1, example 2, and example 3) are shown in the form of a list, which is suitable for the native application with a plurality of pieces of parallel content. The form of the webpage view pattern can be used for displaying the data of the native application in the native workbench by the view of the webpage, and is suitable for displaying the native application with complex content; as shown in (4) in fig. 11, for example, the native application may be an information push application, and then a title of information in the information push application is preferentially shown, so that the login user can quickly obtain the latest information pushed by the application from the title.

In a possible implementation manner, the target form displayed for the native workbench page may be set through the management client, for example, an administrator may configure the target form displayed for the native workbench through a native workbench configuration interface in the management client, please refer to fig. 12, where fig. 12 is an effect schematic diagram of a native workbench configuration interface provided in an embodiment of the present application, in which the target form of the current native workbench may be included, an option for the target form may also be included, an example when displaying according to a different target form may also be included, and so on.

Optionally, the management client may further set one or more page templates for the native workbench page in response to a template setting operation of the administrator for the native workbench. For example, the administrator may set a page template of the raw workbench page in the target office application through a template interface provided by the target office application, where the template interface may be: an interface (interface 1) for setting a display template for in-situ application in the native workbench, an interface (interface 2) for acquiring the display template for in-situ application in the native workbench, and an interface (interface 3) for setting a display template for data for in-situ application in the native workbench. A display template of the native application in the native workstation may be set through the interface 1, for example, the native application in the native workstation is set to be displayed according to the target form, and a default template of a target group may also be set through the interface 1, so that when a page template is not set for a certain user account (for example, when a new person is added to the target group), a page of the native workstation corresponding to the user account is displayed as a page of the native workstation corresponding to the default template. Display templates for in-situ applications in the native workbench can also be obtained through the interface 2. A display template for data of the native application in the native workbench may also be determined through the interface 3. Optionally, when the template interface is called by the management client, the request may be made in a POST or GET manner. Therefore, the display page of the native workbench can be configured according to the user requirements, so that the native workbench can better meet the user requirements. Referring to fig. 13, fig. 13 is a schematic diagram illustrating an effect of a native workbench page template according to an embodiment of the present application.

Optionally, the native work application of the native work middle platform may also display the native application in the form of an icon, and when the native application is displayed in the form of an icon, the native application may be displayed in the form of a squared or sixteen squared or a list, and the like, which is not limited herein. The applications in the native workbench can also be displayed corresponding to various groups, such as displaying common native applications under common groups, displaying native applications for management under management applications, and the like. Optionally, the native workbench may also have banner advertising pages (banner pages) for advertising display, or to enhance the aesthetic appearance of the workbench, or to display targeted collective important notifications, etc. Referring to fig. 14, fig. 14 is a schematic diagram illustrating an effect of a native workbench page according to an embodiment of the present application.

In a possible implementation manner, after a selection instruction for the target webpage workbench is detected, a second acquisition instruction is sent to the server, and if the server fails to return the target webpage workbench page, the native workbench is displayed. Optionally, the failure of the server to return to the target web page workbench may be that the server does not return to the target web page workbench page within a preset time. The failure of the server to return to the target webpage workbench may also be that, after the client sends the first second obtaining instruction, the client does not return to the target webpage workbench page within a preset time, and sends the second obtaining instruction again, the second obtaining instruction sent again does not need to be selected by the user, and the client sends the second obtaining instruction again to the server if detecting that the client does not return to the target webpage workbench page within the preset time, and so on, and if the second obtaining instruction sent is greater than the preset number and the target webpage workbench page is still not obtained, the native workbench is displayed.

As can be understood from the above description, the following situations can be included in the navigation bar of the target work page: only at least one web page workbench is included, at least one web page workbench and a native workbench are included, or only a native workbench is included. For the display of a specific web page or native page, reference may be made to the above description, which is not repeated herein.

The method and the device for obtaining the webpage navigation options send a first obtaining instruction aiming at the webpage to the server, the first obtaining instruction carries the characteristic information of a login user, and a target webpage corresponding to the characteristic information returned by the server is received and displayed, wherein the target webpage comprises the navigation options of at least one webpage workbench. Due to the fact that at least one webpage workbench is introduced into the working page, the requirement of a user for the workbench can be met, and user experience is improved.

Referring to fig. 15, fig. 15 is a schematic structural diagram of a page acquisition device according to an embodiment of the present application. Alternatively, the page acquiring means may be provided in the server. As shown in fig. 15, the page acquiring apparatus described in this embodiment may include:

a receiving module 1501, configured to receive a first obtaining instruction for a work page sent by a client, where the first obtaining instruction carries feature information of a login user in the client;

a processing module 1502, configured to obtain work page configuration information corresponding to the feature information of the login user, where the work page configuration information is used to indicate a target work page correspondingly displayed by the login user, and the target work page includes a navigation option of at least one web workbench;

the sending module 1503 is configured to return the target work page corresponding to the work page configuration information to the client.

In an implementation manner, the at least one web page workbench includes a target web page workbench, and the receiving module 1501 is further configured to receive a second obtaining instruction, which is sent by a client and is specific to the target web page workbench, and obtain the identity information of the login user in the second obtaining instruction;

the processing module 1502 is further configured to, when the identity information of the login user passes verification, obtain webpage workbench configuration information corresponding to the feature information of the login user;

the sending module 1503 is further configured to return a target web workbench page corresponding to the web workbench configuration information to the client.

In one implementation, the target web workbench includes at least one web application, and the processing module 1502 is further configured to: acquiring webpage application permission information aiming at the login user; the webpage application permission information is used for indicating the permission of the login user for each webpage application;

the sending module 1503 returns, to the client, a target web workbench page corresponding to the web workbench configuration information, which is specifically configured to:

and returning a target webpage workbench page corresponding to the webpage application permission information and the webpage workbench configuration information to the client.

Referring to fig. 16, fig. 16 is a schematic structural diagram of another page acquiring apparatus according to an embodiment of the present disclosure. Optionally, the page acquiring device may be a client. As shown in fig. 16, the page obtaining apparatus described in this embodiment includes:

a sending module 1601, configured to send a first obtaining instruction for a working page to a server, where the first obtaining instruction carries feature information of a login user, and the first obtaining instruction is used to request a target working page corresponding to the feature information of the login user;

a receiving module 1602, configured to receive a target work page corresponding to the feature information returned by the server;

a display module 1603, configured to display the target work page, where the target work page includes at least one navigation option of a web workbench.

In an implementation manner, the at least one web page workbench includes a target web page workbench, and the sending module 1601 is further configured to send, to the server, a second obtaining instruction for the target web page workbench when a selection operation of a navigation option for the target web page workbench in the target web page is detected;

the receiving module 1602 is further configured to receive a target web page workbench page returned by the server, where the target web page workbench page is determined by the web application permission information and the web page workbench configuration information corresponding to the login user, and the target web page workbench includes at least one web application;

the display module 1603 is further configured to display a target web page returned by the server, where the target web page is determined by web application permission information and web page workbench configuration information corresponding to the login user, and the target web page workbench includes at least one web application.

In one implementation, the target work page further includes a navigation option of a native workstation, the native workstation includes a plurality of native applications, and the display module 1603 is further configured to display the plurality of native applications in the native workstation in a target form when a selection operation of the navigation option of the native workstation in the target work page is detected;

wherein the target form may include any one or more of: key data type, picture type, list type, and web page view.

In one implementation, the target web page workbench is an HTML5 workbench, and the receiving module 1602 is further configured to:

receiving a page operation instruction of the login user for the HTML5 workbench; adjusting the HTML5 workbench page according to the page setting operation indicated by the page operation instruction;

the page setting operation indicated by the page operation instruction comprises one or more of the following operations: the location of the navigation options configuring the HTML5 workstation, the color of the target location configuring the HTML5 workstation, the option names of the navigation options configuring the HTML5 workstation.

It is understood that the division of the units in the embodiments of the present application is illustrative, and is only one logical function division, and there may be another division manner in actual implementation. Each functional unit in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

Referring to fig. 17, fig. 17 is a schematic structural diagram of a server according to an embodiment of the present disclosure. The client described in this embodiment includes: a processor 1701, a memory 1702, and a network interface 1703. Data may be exchanged between the processor 1701, the memory 1702 and the network interface 1703.

The Processor 1701 may be a Central Processing Unit (CPU), and may be other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 1702, which may include both read-only memory and random-access memory, provides program instructions and data to the processor 1701. A portion of the memory 1702 may also include non-volatile random access memory. Wherein the processor 1701, when calling the program instructions, is configured to perform:

In one implementation, the at least one web page workbench includes a target web page workbench, and the processor 1701 is further to:

receiving a second acquisition instruction which is sent by a client and aims at the target webpage workbench, and acquiring the identity information of the login user in the second acquisition instruction;

when the identity information of the login user passes the verification, acquiring webpage workbench configuration information corresponding to the characteristic information of the login user;

and returning a target webpage workbench page corresponding to the webpage workbench configuration information to the client.

In one implementation, the target web page workbench includes at least one web page application, and the processor 1701 is further configured to:

acquiring webpage application permission information aiming at the login user; the webpage application permission information is used for indicating the permission of the login user for each webpage application;

the returning of the target webpage workbench page corresponding to the webpage workbench configuration information to the client comprises:

Referring to fig. 18, fig. 18 is a schematic structural diagram of a client according to an embodiment of the present disclosure. In this embodiment, the client may also be referred to as a client device, and may be a terminal, such as a personal computer, a tablet computer, a mobile phone, and so on, which are not described herein again. The client described in this embodiment includes: a processor 1801, a memory 1802, and a network interface 1803. Data may be exchanged between the processor 1801, the memory 1802, and the network interface 1803.

The Processor 1801 may be a Central Processing Unit (CPU), and the Processor may also be other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, a discrete hardware component, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 1802, which may include both read-only memory and random access memory, provides program instructions and data to the processor 1801. A portion of memory 1802 may also include non-volatile random access memory. The processor 1801, when calling the program instruction, is configured to perform:

In one implementation, the at least one web page workbench includes a target web page workbench, and the processor 1801 is further configured to:

when the selection operation of the navigation option of the target webpage workbench in the target working page is detected, sending a second acquisition instruction of the target webpage workbench to the server;

and receiving and displaying a target webpage workbench page returned by the server, wherein the target webpage workbench page is determined by webpage application permission information and webpage workbench configuration information corresponding to the login user, and the target webpage workbench comprises at least one webpage application.

In one implementation, the target work page further includes navigation options of a native workbench including a plurality of native applications, and the processor 1801 is further configured to:

displaying the plurality of native applications in the native workbench in a target form when a selection operation of a navigation option for the native workbench in the target work page is detected;

In one implementation, the target web page workbench is an HTML5 workbench, and the processor 1801 is further configured to:

The embodiment of the present application further provides a computer storage medium, where program instructions are stored in the computer storage medium, and when the program is executed, part or all of the steps of the page obtaining method in the foregoing method embodiment may be implemented, which is not described herein again.

It should be noted that, for simplicity of description, the above-mentioned embodiments of the method are described as a series of acts or combinations, but those skilled in the art should understand that the present application is not limited by the order of acts described, as some steps may be performed in other orders or simultaneously according to the present application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.

Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by associated hardware instructed by a program, which may be stored in a computer-readable storage medium, and the storage medium may include: flash disks, Read-Only memories (ROMs), Random Access Memories (RAMs), magnetic or optical disks, and the like.

Embodiments of the present application also provide a computer program product or computer program comprising computer instructions stored in a computer-readable storage medium. The computer instructions are read from the computer-readable storage medium by a processor of the server, and the processor executes the computer instructions to cause the server to perform the steps performed in the embodiments of the methods described above.

The traffic scheduling method, apparatus, device and storage medium provided in the embodiments of the present application are described in detail above, and a specific example is applied in the present application to explain the principle and the implementation of the present application, and the description of the above embodiments is only used to help understand the method and the core idea of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims

1. A page acquisition method is characterized by comprising the following steps:

2. The method of claim 1, wherein the at least one web page workbench comprises a target web page workbench, the method further comprising:

3. The method of claim 2, wherein the target web workbench comprises at least one web application, the method further comprising:

4. A page acquisition method is characterized by comprising the following steps:

5. The method of claim 4, wherein the at least one web page workbench comprises a target web page workbench, the method further comprising:

6. The method of claim 4, wherein the target work page further includes navigation options for a native workbench including a plurality of native applications therein, the method further comprising:

7. The method of claim 5, wherein the target web page workbench is an HTML5 workbench, and the method further comprises:

8. A page acquisition apparatus, comprising:

9. A page acquisition apparatus, comprising:

10. A computer-readable storage medium, having stored thereon computer program instructions, which, when executed by a processor, are adapted to perform the method of any one of claims 1-7.