CN114518924B - Page display method, device and equipment of mobile client and storage medium - Google Patents
Page display method, device and equipment of mobile client and storage medium Download PDFInfo
- Publication number
- CN114518924B CN114518924B CN202210112613.9A CN202210112613A CN114518924B CN 114518924 B CN114518924 B CN 114518924B CN 202210112613 A CN202210112613 A CN 202210112613A CN 114518924 B CN114518924 B CN 114518924B
- Authority
- CN
- China
- Prior art keywords
- user
- login
- target
- page
- current
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 51
- 238000009877 rendering Methods 0.000 claims abstract description 24
- 230000006870 function Effects 0.000 claims description 50
- 230000000007 visual effect Effects 0.000 claims description 16
- 230000008569 process Effects 0.000 claims description 12
- 230000004083 survival effect Effects 0.000 claims description 5
- 238000004590 computer program Methods 0.000 claims description 4
- 230000000694 effects Effects 0.000 abstract description 23
- 238000012545 processing Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 5
- 230000003993 interaction Effects 0.000 description 5
- 238000001514 detection method Methods 0.000 description 3
- 230000002452 interceptive effect Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000006399 behavior Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001427 coherent effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000010408 sweeping Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
- G06F16/986—Document structures and storage, e.g. HTML extensions
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Human Computer Interaction (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a page display method, a device, equipment and a storage medium of a mobile client, wherein the method comprises the following steps: when the target client is detected to be in a login state and the current foreground running state is not awakened from the background to the foreground, acquiring a first user permission corresponding to each function control of a first target page according to a first user login role matched with a current login user; and updating the control layout matched with the first target page according to each first user permission, and rendering and displaying the first target page according to the updated control layout. According to the technical scheme, the user authority corresponding to the login user is determined by configuring the login role of the user, and the exclusive client page is displayed to the login user according to the user authority, so that the client page can be updated in real time, the client page can be displayed in a differentiated mode, and the differentiated display effect of the client page can be improved.
Description
Technical Field
The embodiment of the invention relates to a mobile application development technology, in particular to a page display method, device and equipment of a mobile client and a storage medium.
Background
Along with the continuous development of mobile application technology, different page contents are displayed for users without using the application program in the display page of the application program, and the method has important significance for improving the page display effect of the application program and improving the application program use experience of the user.
At present, the existing page display method of the application program generally configures corresponding rights for different users manually, and further displays corresponding functional modules to the users according to the rights corresponding to the users when the users are detected to log in the application program. However, in the prior art, once the manual configuration of the user permission is completed, the corresponding page display content and page display effect are fixed, and when the page display content and page display effect need to be updated, the user permission needs to be reconfigured, so that the update instantaneity of the page display content and page display effect is poor; in addition, the prior art can only adjust the number or types of the functional modules which can be displayed in the page by configuring different user rights, but cannot dynamically adjust the display effect of the functional modules, so that the display effect of the page which can be realized is limited and single.
Disclosure of Invention
The invention provides a page display method, device, equipment and storage medium of a mobile client, which can realize real-time update of the client page, realize differentiated display of the client page and improve the differentiated display effect of the client page.
In a first aspect, an embodiment of the present invention provides a page display method of a mobile client, including:
when detecting that a target client starts running in the foreground currently, judging whether the target client is in a login state or not;
if so, acquiring a first user login role matched with the current login user when detecting that the foreground running state is not awakened from the background to the foreground;
responding to a viewing request of a first target page in the target client, and acquiring first user permission corresponding to each function control in the first target page according to the first user login role;
and updating the control layout matched with the first target page according to the first user permission corresponding to each function control in the first target page, and rendering and displaying the first target page according to the updated control layout matched with the first target page.
In a second aspect, an embodiment of the present invention further provides a page display device of a mobile client, including:
the login state judging module is used for judging whether the target client is in a login state or not when detecting that the target client is currently started to run in the foreground;
the first user login role acquisition module is used for acquiring a first user login role matched with a current login user when detecting that the foreground running state is not awakened from the background to the foreground if the first user login role acquisition module is used for acquiring the first user login role matched with the current login user;
the first user permission acquisition module is used for responding to a viewing request of a first target page in the target client and acquiring first user permissions corresponding to all function controls in the first target page according to the first user login role;
and the first control layout updating module is used for updating the control layout matched with the first target page according to the first user permission corresponding to each functional control in the first target page, and rendering and displaying the first target page according to the updated control layout matched with the first target page.
In a third aspect, an embodiment of the present invention further provides a client device, where the client device includes:
One or more processors;
a memory for storing one or more programs;
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the page presentation method for a mobile client according to any embodiment of the present invention.
In a fourth aspect, an embodiment of the present invention further provides a computer storage medium, where a computer program is stored, where the program when executed by a processor implements the page presentation method of the mobile client provided in any embodiment of the present invention.
According to the technical scheme provided by the embodiment of the invention, the login state of the target client and the foreground running state are detected, so that frequent and unnecessary requests of the client to the user login role can be avoided, the number of requests to the corresponding interface of the background server is reduced, and the data processing pressure of the background server is reduced; in the interaction process of the user and the target client, the user login role matched with the current login user is given to configure the user authority corresponding to the current login user, and the control layout corresponding to the page is updated according to the user authority, so that the exclusive client page is displayed to the current login user, the real-time updating of page display content and page display effect can be realized, the differentiated display of the client page can be realized by updating the control layout matched with the client page, and the differentiated display effect of the client page can be improved.
Drawings
FIG. 1A is a flow chart of a page display method of a mobile client according to a first embodiment of the invention;
FIG. 1B is a diagram of a mobile client page according to a first embodiment of the present invention;
FIG. 2 is a flow chart of a page display method of a mobile client according to a second embodiment of the present invention;
FIG. 3 is a flow chart of a page display method of a mobile client in a third embodiment of the present invention;
FIG. 4 is a block diagram showing a mobile client page display device according to a fourth embodiment of the present invention;
fig. 5 is a block diagram of a client device in a fifth embodiment of the present invention.
Detailed Description
The invention is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting thereof. It should be further noted that, for convenience of description, only some, but not all of the structures related to the present invention are shown in the drawings.
Example 1
Fig. 1A is a flowchart of a mobile client page display method according to an embodiment of the present invention, where the embodiment may be adapted to configure different user rights for different login users of a client, and further display customized client pages to the login users according to the user rights.
S110, judging whether the target client is in a login state when detecting that the target client is currently started to run in the foreground.
The target client may be an Application (APP) client of a mobile terminal (e.g., a mobile phone, a tablet computer, etc.); in this embodiment, the APP may support an android operating system or an IOS operating system, which is not specifically limited in this embodiment. Alternatively, both the "foreground" and "background" are relative to the operating system of the mobile terminal. Taking an android operating system as an example, when an application program is determined to be in a running state, if the application program has a corresponding user visible view component, has a running foreground service or has another application program associated with the application program, the application program can be determined to run in the foreground of the android operating system; correspondingly, if the conditions are not met, the application program can be determined to run in the background of the android operating system.
In this embodiment, when it is detected that the target client is currently turned on, it may be determined that the target client is currently started to run in the foreground; or when it is detected that a view component corresponding to a page of the target client is created, it may be determined that the target client is currently started to run in the foreground. Further, when the target client is determined to start running in the foreground, whether the target client is in a login state currently is judged.
And S120, if so, acquiring a first user login role matched with the current login user when the foreground operation state is detected not to wake up from the background to the foreground.
The user login role is associated with the user permission corresponding to each function control contained in the target client; the background server can configure the user authority corresponding to each function control for the user by endowing the user of the target client with the user login role corresponding to the user. The background server may be a remote device that communicates with the target client.
The functionality controls refer to program entities for implementing specific functions, for example, the functionality controls may include a interview duty registration control, a member off-office list control, a code-sweeping sub-control, and the like. Correspondingly, the user permissions may include behavior permissions (e.g., whether it may be selected and whether it may jump after being selected, etc.) and status permissions (e.g., whether it is visible) corresponding to the functionality controls.
In this embodiment, the corresponding user authority is configured for the user of the target client by assigning the matched user login roles, so that when different users correspond to the same user authority, only one user login role corresponding to the same user authority needs to be configured. At this time, by giving each user the user login role, the corresponding same user authority can be configured for each user, so that manual and repeated configuration of the same user authority can be avoided, and the configuration efficiency of the user authority can be greatly improved; in addition, in the interaction process of the user and the target client, when the user authority is required to be updated, the latest user login role of the current user is only required to be given, and the real-time performance of the user authority update can be improved.
It should be noted that if the target client wakes up from the background to the foreground, it indicates that the target client has been turned on before a short time and is not currently exited; at this time, since the interval time is short, the user login role corresponding to the current login user is not changed. If the target client requests the user login role from the background server again, repeated requests of the same user login role in a short time are caused, the effectiveness of acquiring the user login role is reduced, the number of requests of the corresponding interface of the background server is increased, and the data processing pressure of the background server is increased.
In view of the above, in this embodiment, after determining that the target client is in the login state, it is further determined whether the target client wakes up from the background to the foreground, that is, whether the target client has been previously turned on and has not been exited. If it is determined that the current foreground operating state is not awakened from the background to the foreground, a user login role acquisition request may be sent to the background server. After receiving the user login role obtaining request, the background server may find a corresponding relationship between a pre-established user identifier and a user login role according to a user identifier (for example, a user name or a user account number) of a current login user, obtain a first user login role matched with the current login user, and send the first user login role to the target client. If the current foreground running state is determined to be awakened from the background to the foreground, the locally cached user login role can be used continuously.
The advantages of the above arrangement are that: by judging the current foreground running state of the target client to determine whether to request the matched user login roles from the background server, repeated requests of the same user login roles can be avoided, the effectiveness of acquiring the user login roles can be improved, in addition, frequent and unnecessary requests of the background server on the user login roles can be avoided, the number of requests of the background server on the corresponding interfaces can be reduced, and the data processing pressure of the server is reduced.
In an alternative implementation of this embodiment, detecting that the foreground operating state is not awakened from the background to the foreground may include: detecting whether a view component corresponding to a homepage of the target client exists in a view component manager of the target client; if not, determining that the foreground running state is not awakened from the background to the foreground.
The view component is a software entity for realizing the display of the client page and corresponds to the client page one by one; and the view component manager is used for recording and managing the view components. In this embodiment, a view component manager with a history view component recording function may be locally configured to store view components corresponding to pages displayed by the target client in a certain time. Notably, when the target client is completely shut down, killed by the operating system background, or a restart occurs at the terminal where the target client is installed, the view component manager corresponding to the target client will be completely emptied.
It should be noted that, after the client is opened, the user will enter the main page of the client by default, that is, the default main page is the 1 st page displayed after the client is opened. Therefore, if the target client is previously opened and not completely closed, the user must open the main page passing through the target client, so that the view component manager must have a view component for displaying the main page of the target client; therefore, the view component corresponding to the main page can be searched in the view component manager of the target client to judge whether the target client wakes up from the background to the foreground.
In a specific example, when the target client corresponds to the android operating system, the corresponding view component may be an Activity component; the Activity component is an inherent component of the android system and is used for providing an interactive interface between the program and a user; specifically, the Activity component can realize all processes of creating, displaying and ending the interactive interface through a series of pre-configured controls. Specifically, in an Activity component manager of the target client, detecting whether an Activity component corresponding to a homepage of the target client exists; if it is determined that there is, it may be determined that the target client is awakened from the background to the foreground.
It should be noted that, at present, the login state of many APPs will be cached locally, even if the APP is completely closed or the mobile phone is restarted, if the APP is restarted within the validity period, the APP will still be in the login state, and no re-login is needed, for example, after the WeChat is closed, no re-login is needed when the WeChat is opened again. However, the validity period of APP settings may be 1 week or longer, during which time the backend server may update the matching user login roles. Therefore, if only the login state of the target client is detected, the latest user login role matched with the current login user cannot be timely acquired.
In this embodiment, after the target client is detected to be in the login state, whether to request to acquire the current user login role from the background server is determined according to whether a view component corresponding to the homepage exists in the view component manager, so that timely acquisition of the latest user login role can be realized, frequent and unnecessary requests to the user login role caused by the condition that the target client wakes up from the background to the foreground can be avoided, the number of requests of the corresponding interface of the background server can be reduced, and the data processing pressure of the background server is reduced.
In another optional implementation of this embodiment, detecting that the foreground operating state is not awakened from the background to the foreground may include: judging whether the process of the target client is in a survival state or not; if so, determining that the foreground running state is not awakened from the background to the foreground when detecting that no view component corresponding to the homepage of the target client exists in the view component manager of the target client.
In this embodiment, when detecting whether the foreground running state wakes up from the background to the foreground, it may also be detected whether the background process of the target client is in a surviving state; if yes, the target client can be determined not to be thoroughly killed by the background of the operating system; further, if it is determined that the view component corresponding to the main page exists in the view component manager, it may be determined that the current foreground running state of the target client wakes up from the background to the foreground.
The advantages of the above arrangement are that: by combining whether the process corresponding to the target client is in a survival state and whether the view component corresponding to the main page is included in the view component manager or not, whether the foreground operation state is awakened from the background to the foreground or not is finally judged, and the judgment accuracy of the foreground operation state of the target client can be improved.
S130, responding to a viewing request of a first target page in the target client, and acquiring first user permission corresponding to each function control in the first target page according to the first user login role.
It should be noted that, in this embodiment, an association relationship between each user login role and a user authority corresponding to each function control in each page may be pre-established; specifically, a corresponding layout configuration file may be preset for each page of the target client, where the layout configuration file may include layout data corresponding to each functional control included in the corresponding page, and user permissions corresponding to each functional control and each user login role respectively; or, a corresponding layout configuration file may be set in advance for the target client, where the layout configuration file may include layout data corresponding to all the functional controls included in the target client, page identifiers of pages corresponding to the functional controls, and user permissions corresponding to the functional controls and the user login roles respectively.
Therefore, when detecting that the current login user clicks to select the first target page, the target client can acquire the first user permission corresponding to each function control in the first target page according to the first user login role matched with the current login user and the pre-established association relationship between the user login role and the user permission corresponding to each function control in the first target page.
And S140, updating a control layout matched with the first target page according to the first user permission corresponding to each function control in the first target page, and rendering and displaying the first target page according to the updated control layout matched with the first target page.
In this embodiment, each functional page of the target client has a matched initial control layout; for example, the initial control layout may be in a list form as shown in fig. 1B, and may include all the functional controls that may be displayed in the corresponding functional page, where each row corresponds to one functional control, and an initial sequence of the functional controls is preset. Therefore, after the first user permission corresponding to each functional control in the first target page is obtained, the initial control layout can be updated according to the first user permission corresponding to each functional control, namely, the number of the displayable functional controls and the display effect (such as display positions, clicking events and the like) of each functional control are updated.
Taking the "code scanning collar quilt control" as an example, for the function control, if the user authority corresponding to the first user login role is "visible and operable", the code scanning collar quilt control can be displayed at a corresponding position in the current page and is in a selectable state (for example, after being clicked, the code scanning collar quilt control jumps to a set page); or if the user authority corresponding to the first user login role is visual but not operable, the code scanning collar sub-control can still be displayed at the corresponding position in the current functional page but is in a non-selectable state (for example, after being clicked, only pop up preset alarm information and not jump to a set page); for another example, if the user authority corresponding to the first user login role is invisible, the code scanning collar quilt sub-control is hidden and becomes invisible.
Optionally, when detecting that the user authority corresponding to the first user login role is invisible for a certain functional control, the functional control is changed into a hidden state, and in the functional control with the visible authority corresponding to the first user login role, determining the nearest functional control below the functional control, and automatically moving the nearest functional control upwards to replace the position of the detected functional control in the current page for display. Taking the client page shown in fig. 1B as an example, for the current login user, when the user authority corresponding to the code scanning sub-control is invisible and the user authority corresponding to the provider bill control is visible, the provider bill control will automatically move upwards to replace the position where the code scanning sub-control is located.
The advantages of the above arrangement are that: if the current login user only has the visual permission of part of the functional controls, the appearance of a blank display area among the functional controls in the client page can be avoided when the client page is displayed, the differentiated display effect of the client page can be more natural, the display of the functional controls is more coherent, and the use experience of different users in the process of viewing the client page can be improved.
In this embodiment, after updating the control layout corresponding to the first target page is completed, the layout code of each functional control corresponding to the updated control layout may be executed according to the updated control layout corresponding to the first target page, so as to render and display the first target page of the target client in the interactive interface of the target client.
In this embodiment, when the control layout of the client page needs to be updated, the background server may be used to give the latest user login role of the target client for the user to update the user authority corresponding to the user, and further update the control layout of the client page according to the updated user authority corresponding to the user. Through the setting, when the user login role corresponding to the user changes, the real-time performance of the client page update can be improved.
Optionally, each page of the target client may be set to support page presentations of different user login roles. Or, only partial pages of the target client side can be set to support page display of different user login roles; at the moment, for the functional pages which do not support the page display of different user login roles, the page layout seen by the users corresponding to the different user login roles is the same; and for the functional pages supporting the page display of different user login roles, the page layout seen by the users corresponding to the different user login roles is different. Through the arrangement, flexibility of target client page display can be further improved.
According to the technical scheme provided by the embodiment of the invention, the login state of the target client and the foreground running state are detected, so that frequent and unnecessary requests of the client to the user login role can be avoided, the number of requests to the corresponding interface of the background server is reduced, and the data processing pressure of the background server is reduced; in the interaction process of the user and the target client, the user login role matched with the current login user is given to configure the user authority corresponding to the current login user, and the control layout corresponding to the page is updated according to the user authority, so that the exclusive client page is displayed to the current login user, the real-time updating of page display content and page display effect can be realized, the differentiated display of the client page can be realized by updating the control layout matched with the client page, and the differentiated display effect of the client page can be improved.
In another optional implementation manner of this embodiment, the technical solution of this embodiment may further include: according to a configuration request aiming at user login roles, at least one user login role is pre-established, user rights corresponding to all the functional controls of all the pages in the target client are configured for each user login role, and all the configured user login roles are obtained; generating a corresponding relation between a user identifier corresponding to a target user and the configured user login role according to a user login role allocation request aiming at the target user, and storing the corresponding relation in a server; correspondingly, the obtaining the first user login role matched with the current login user may include: and acquiring a first user login role matched with the current login user from the server according to the user identification corresponding to the current login user.
In a specific example, three user login roles, namely a user login role a, a user login role B and a user login role C, can be pre-established through a server; assume that a page 1 of a target client comprises a code scanning collar quilt sub-control, and authority options corresponding to the code scanning collar quilt sub-control comprise visible, invisible, operable and inoperable; wherein visible and invisible cannot coexist, and operable and inoperable cannot coexist. At this time, the user authority corresponding to the code scanning collar quilt control can be configured to be visible and operable for the user login role a, the user authority corresponding to the code scanning collar quilt control can be configured to be visible but not operable for the user login role B, and the user authority corresponding to the code scanning collar quilt control can be configured to be invisible for the user login role C. Furthermore, the mapping relation between the configured user login roles and the user rights corresponding to the function controls can be stored, so that the configuration of the user login roles is realized.
Secondly, after completing the configuration of the user login roles, the matched user login roles can be configured for each user; for example, if user 1, user 2, and user 3 currently exist, user 1 may be assigned user login role a, user 2 may be assigned user login role B, and user 3 may be assigned user login role C. Therefore, when the user login role matched with the current login user is obtained, the first user login role matched with the current login user can be searched according to the user identification of the current login user; for example, if the user identifier is user 1, the matched first user login role is user login role a.
The user identifier may be a user name or a user login account, which is not specifically limited in this embodiment. Note that different user login roles may be allocated to different users, or the same user login role may be allocated to different users, so that flexible allocation of the user login roles may be realized.
Example two
Fig. 2 is a flowchart of a page display method of a mobile client according to a second embodiment of the present invention, where the technical solution in this embodiment may be combined with one or more of the foregoing embodiments. Specifically, referring to fig. 2, the method specifically includes the following steps:
s210, judging whether the target client is in a login state when detecting that the target client is currently started to run in the foreground.
And S220, if not, displaying the login page of the target client to the current access user.
S230, acquiring user login information input by the current access user in the login page, and acquiring a second user login role corresponding to the current access user according to the user login information.
In one scenario, when the target client is opened, the target client is in an unregistered state; at this time, the target client may provide a login page to the current access user at the human-computer interaction interface. The current access user can input user login information such as a user account number, a user password and the like in a login page, and click a login button. When the target client detects clicking of the login button, user login information input by a user is sent to the background server, and a user login interface of the background server is requested to check the user login information. When the background server detects a request of a target client to a user login interface, checking the received user login information; if the user identity verification is successful, a second user login role matched with the current access user can be searched and obtained, and the second user login role is sent to the target client side for caching.
It can be understood that if the target client has cached a history user login role corresponding to the current access user, the target client may update the locally cached history user login role with the second user login role after receiving the latest second user login role corresponding to the current access user.
S240, responding to a viewing request of a second target page in the target client, and acquiring second user rights corresponding to each function control in the second target page according to the second user login role.
S250, updating a control layout matched with the second target page according to second user rights corresponding to each function control in the second target page, and rendering and displaying the second target page according to the updated control layout matched with the second target page.
In an optional implementation manner of this embodiment, after determining whether the target client is in the login state, the method may further include: if not, displaying a preset page of the target client to the current access user; and responding to a viewing request of the current access user for a third target page in the target client, acquiring a standard control layout of the third target page, and rendering and displaying the third target page according to the standard control layout.
The standard control layout can be a preset control layout corresponding to each page of the target client. In this embodiment, for each page of the target client, a corresponding standard control layout may be preset, and a correspondence between the page identifier and the standard control layout may be stored.
In another scenario, when the target client is in an unregistered state, a preset page may be displayed to the current access user, that is, the current access user is allowed to access the target client in a guest mode. The preset page may be any functional page of the target client specified in advance, for example, the preset page may be a main page. Further, when the click view instruction of the current access user for the third target page is detected, the corresponding relation between the pre-established page identifier and the standard control layout can be searched according to the page identifier of the third target page, so that the standard control layout matched with the third target page is obtained, and further the third target page can be rendered and displayed according to the standard control layout.
According to the technical scheme provided by the embodiment of the invention, when the fact that the target client side is currently started to run in the foreground is detected, whether the target client side is in a login state is judged; when the target client is determined not to be in the login state, displaying a login page of the target client to the current access user; further, user login information input in a login page by a current access user is obtained, and a second user login role corresponding to the current access user is obtained according to the user login information; further, responding to a viewing request of a second target page in the target client, and acquiring second user rights corresponding to each function control in the second target page according to a second user login role; finally, according to the second user permission corresponding to each function control in the second target page, updating the control layout matched with the second target page, and rendering and displaying the second target page according to the updated control layout matched with the second target page; when the user does not log in, the matched user login roles are acquired according to the user login information, so that the user login roles can be acquired in time, and further, the user authority can be dynamically configured in real time.
Example III
Fig. 3 is a flowchart of a page display method of a mobile client according to a third embodiment of the present invention, where the technical solution in this embodiment may be combined with one or more of the foregoing embodiments. Specifically, referring to fig. 3, the method specifically includes the following steps:
s310, start, and execute S320.
And S320, judging whether the target client is in a login state when detecting that the target client is currently started to run in the foreground.
If yes, executing S330; otherwise, S360 is performed. In this embodiment, if it is determined that the target client is in the login state, it may be further determined whether the target client wakes up from the background to the foreground, so as to determine whether to request the server to obtain the latest first user login role matching the current login user. If the target client is not in the login state, a login page can be provided for the user so that the user inputs user login information, and the target client can acquire a second user login role corresponding to the current login user according to the user login information.
S330, when the foreground running state is detected not to wake up from the background to the foreground, a first user login role matched with the current login user is acquired, and S340 is executed.
S340, responding to a viewing request of a first target page in the target client, acquiring first user permission corresponding to each function control in the first target page according to the first user login role, and executing S350.
And S350, updating a control layout matched with the first target page according to the first user permission corresponding to each function control in the first target page, rendering and displaying the first target page according to the updated control layout matched with the first target page, and executing S3100.
In an optional implementation manner of this embodiment, the user permission includes a visual permission and an operation permission, and updating, according to a first user permission corresponding to each function control in the first target page, a control layout matched with the first target page may include: judging whether the current login user has visual permission for the current functional control, if not, carrying out hidden layout on the current functional control; if yes, judging whether the current login user has operation authority on the current function control; if the current login user is determined to have the operation authority on the current function control, configuring an operation event corresponding to the current function control; and if the current login user is determined to not have the operation authority on the current functional control, configuring alarm prompt information corresponding to the current functional control.
In this embodiment, when the user permission is a visual permission and an operation permission, display control may be performed on the first target page according to the visual permission and the operation permission corresponding to each function control in the first target page by the first user login role. Specifically, for the current functional control, firstly judging whether the current login user has visual permission or not, and if the current login user does not have the visual permission, directly hiding the current functional control; for example, the current functionality control is set to invisible and does not occupy any display area; alternatively, the current functionality control is set to invisible but occupies the display area.
If the visual permission is determined to be provided, whether the current functional control is provided with the operation permission is further judged, and if the visual permission is determined to be provided with the operation permission, an operation event corresponding to the current functional control can be configured; for example, click event logic (e.g., jump to a specified page) upon clicking by the user is configured. However, if it is determined that the operation authority is not possessed, the corresponding warning prompt information (for example, "no operation authority") may be configured. The operation event and the alarm prompt information can be predefined, and are automatically configured when the corresponding configuration condition is detected to be met.
Correspondingly, after rendering and displaying the first target page according to the updated control layout, if the click operation of the current login user on a certain functional control is detected, if the current login user has the corresponding operation authority, directly executing a preconfigured operation event; if the corresponding operation authority is not provided, the corresponding alarm prompt information is popped up.
In another optional implementation manner of this embodiment, rendering and displaying the first target page according to the updated control layout matched with the first target page may include: according to the updated control layout matched with the first target page, adjusting a basic layout file corresponding to the first target page, and obtaining an adjusted basic layout file; rendering and displaying the first target page according to the adjusted basic layout file; the basic layout file comprises picture layout data and text layout data corresponding to each function control in the first target page.
The basic layout file may include a basic frame code (for example, page length, width, etc.) of the current page, and layout codes of all the functional controls that can be displayed (for example, display positions, display lengths and widths of the functional controls, corresponding pictures, characters, etc.). In this embodiment, the basic layout file may be adjusted according to the updated control layout matched with the first target page, for example, the layout code of the functional control of the hidden layout is deleted or hidden; and then the first target page can be rendered and displayed according to the adjusted basic layout file.
In a specific example, as shown in fig. 1B, the display effect of each function control is a left picture, a middle text and a right picture, taking the code scanning collar quilt control as an example, the left picture is a set icon, the middle text is a code scanning collar quilt, and the right picture is a right arrow icon. Therefore, the basic layout file comprises picture layout data and text layout data corresponding to each functional control; the picture layout data may be a storage path of the picture.
The advantages of the above arrangement are that: by adjusting the matched basic layout file, the client pages containing different functional controls can be displayed to users corresponding to different user login roles, so that the differential display of the client pages can be realized, and the differential display effect of the client pages is further improved.
S360, showing a login page of the target client to the current access user, and executing S370.
S370, obtaining user login information input by the current access user in the login page, obtaining a second user login role corresponding to the current access user according to the user login information, and executing S380.
And S380, responding to a viewing request of a second target page in the target client, acquiring second user permission corresponding to each function control in the second target page according to the second user login role, and executing S390.
And S390, updating a control layout matched with the second target page according to the second user permission corresponding to each function control in the second target page, rendering and displaying the second target page according to the updated control layout matched with the second target page, and executing S3100.
S3100, ending.
According to the technical scheme provided by the embodiment of the invention, when the target client is detected to start running in the foreground, whether the target client is in a login state is judged; if the target client is determined to be in the login state, when the foreground running state is determined not to be awakened from the background to the foreground, acquiring a first user login role matched with the current login user; if the target client is in the unregistered state, the login page is provided for the current access user to acquire the user login information, and then the second user login role matched with the current access user is acquired according to the user login information, so that timely acquisition of the latest user login role corresponding to the user can be realized, timely acquisition of the latest user login role can be ensured, repeated and unnecessary requests for the same user login role in a short time can be avoided, validity of the acquired user login role can be ensured, and balance of timely acquisition and validity of the user login role can be realized through the setting.
Example IV
Fig. 4 is a block diagram of a page display device of a mobile client according to a fourth embodiment of the present invention, where the device specifically includes: a login status determination module 410, a first user login role acquisition module 420, a first user authority acquisition module 430, and a first control layout update module 440; wherein;
a login state judging module 410, configured to judge whether a target client is in a login state when detecting that the target client is currently running in the foreground;
the first user login role obtaining module 420 is configured to obtain a first user login role that matches the current login user when it is detected that the foreground running state is not awakened from the background to the foreground if it is yes;
the first user permission obtaining module 430 is configured to obtain, according to the first user login role, a first user permission corresponding to each function control in the first target page in response to a request for viewing the first target page in the target client;
and the first control layout updating module 440 is configured to update a control layout matched with the first target page according to a first user right corresponding to each function control in the first target page, and render and display the first target page according to the updated control layout matched with the first target page.
According to the technical scheme provided by the embodiment of the invention, the login state of the target client and the foreground running state are detected, so that frequent and unnecessary requests of the client to the user login role can be avoided, the number of requests to the corresponding interface of the background server is reduced, and the data processing pressure of the background server is reduced; in the interaction process of the user and the target client, the user login role matched with the current login user is given to configure the user authority corresponding to the current login user, and the control layout corresponding to the page is updated according to the user authority, so that the exclusive client page is displayed to the current login user, the real-time updating of page display content and page display effect can be realized, the differentiated display of the client page can be realized by updating the control layout matched with the client page, and the differentiated display effect of the client page can be improved.
Optionally, on the basis of the above technical solution, the first user login role obtaining module 420 includes:
a view component detecting unit, configured to detect, in a view component manager of the target client, whether a view component corresponding to a home page of the target client exists;
And the first foreground running state detection unit is used for determining that the foreground running state is not awakened from the background to the foreground if the first foreground running state is not awakened from the background to the foreground.
Optionally, on the basis of the above technical solution, the first user login role obtaining module 420 includes:
the process survival judging unit is used for judging whether the process of the target client is in a survival state or not;
and the second foreground running state detection unit is used for determining that the foreground running state is not awakened from the background to the foreground when detecting that the view component corresponding to the homepage of the target client does not exist in the view component manager of the target client if the second foreground running state detection unit is used for judging that the view component corresponding to the homepage of the target client exists.
Optionally, on the basis of the above technical solution, the page display device of the mobile client further includes:
the login page display module is used for displaying a login page of the target client to the current access user if not;
the second user login role acquisition module is used for acquiring user login information input by the current access user in the login page and acquiring a second user login role corresponding to the current access user according to the user login information;
the second user permission acquisition module is used for responding to a viewing request of a second target page in the target client and acquiring second user permissions corresponding to all the functional controls in the second target page according to the second user login role;
And the second control layout updating module is used for updating the control layout matched with the second target page according to the second user permission corresponding to each functional control in the second target page, and rendering and displaying the second target page according to the updated control layout matched with the second target page.
Optionally, on the basis of the above technical solution, the page display device of the mobile client further includes:
the preset page display module is used for displaying a preset page of the target client to the current access user if not;
the standard control layout acquisition module is used for responding to the viewing request of the current access user for the third target page in the target client, acquiring the standard control layout of the third target page, and rendering and displaying the third target page according to the standard control layout.
Optionally, on the basis of the above technical solution, the user rights include a visual right and an operation right; the first control layout update module 440 includes:
the control hiding layout unit is used for judging whether the current login user has visual permission for the current functional control, and if not, hiding layout is carried out on the current functional control;
The operation authority judging unit is used for judging whether the current login user has operation authority to the current function control or not if yes;
the information configuration unit is used for configuring an operation event corresponding to the current functional control if the current login user is determined to have operation authority on the current functional control; and if the current login user is determined to not have the operation authority on the current functional control, configuring alarm prompt information corresponding to the current functional control.
Optionally, based on the above technical solution, the first control layout update module 440 includes:
the basic layout file adjusting unit is used for adjusting the basic layout file corresponding to the first target page according to the updated control layout matched with the first target page, and acquiring an adjusted basic layout file;
the target page rendering display unit is used for rendering and displaying the first target page according to the adjusted basic layout file; the basic layout file comprises picture layout data and text layout data corresponding to each function control in the first target page.
Optionally, on the basis of the above technical solution, the page display device of the mobile client further includes:
The user permission configuration module is used for pre-establishing at least one user login role according to a configuration request aiming at the user login role, configuring the user permission corresponding to each functional control of each page in the target client for each user login role, and acquiring each configured user login role;
the corresponding relation generating module is used for generating a corresponding relation between the user identification corresponding to the target user and the configured user login role according to the user login role allocation request aiming at the target user, and storing the corresponding relation into the server;
the first user login role obtaining module 420 is specifically configured to obtain, from the server, a first user login role that matches the current login user according to a user identifier corresponding to the current login user.
The device can execute the page display method of the mobile client provided by the embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method. Technical details not described in detail in this embodiment can be found in the methods provided in the previous embodiments of the present invention.
Example five
Fig. 5 is a schematic structural diagram of a client device according to a fifth embodiment of the present invention, where, as shown in fig. 5, the client device includes a processor 510, a memory 520, an input device 530, and an output device 540; the number of processors 510 in the client device may be one or more, one processor 510 being taken as an example in fig. 5; the processor 510, memory 520, input means 530, and output means 540 in the client device may be connected by a bus or other means, for example by a bus connection in fig. 5. The memory 520 is a computer readable storage medium, and may be used to store a software program, a computer executable program, and modules, such as program instructions/modules corresponding to a page display method of a mobile client in any embodiment of the present invention (for example, a login status determination module 410, a first user login role obtaining module 420, a first user authority obtaining module 430, and a first control layout update module 440 in a page display device of a mobile client). The processor 510 executes various functional applications of the client device and data processing by running software programs, instructions and modules stored in the memory 520, i.e., implements a mobile client page presentation method as described above. That is, the program, when executed by the processor, implements:
When detecting that a target client starts running in the foreground currently, judging whether the target client is in a login state or not;
if so, acquiring a first user login role matched with the current login user when detecting that the foreground running state is not awakened from the background to the foreground;
responding to a viewing request of a first target page in the target client, and acquiring first user permission corresponding to each function control in the first target page according to the first user login role;
and updating the control layout matched with the first target page according to the first user permission corresponding to each function control in the first target page, and rendering and displaying the first target page according to the updated control layout matched with the first target page.
Memory 520 may include primarily a program storage area and a data storage area, wherein the program storage area may store an operating system, at least one application program required for functionality; the storage data area may store data created according to the use of the terminal, etc. In addition, memory 520 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device. In some examples, memory 520 may further include memory located remotely from processor 510, which may be connected to the client device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input means 530 may be used to receive input numeric or character information and to generate key signal inputs related to user settings and function control of the client device, which may include a keyboard, a mouse, and the like. The output 540 may include a display device such as a display screen.
Example six
The sixth embodiment of the present invention further provides a computer readable storage medium having a computer program stored thereon, where the computer program when executed by a processor implements the method according to any embodiment of the present invention. Of course, the computer readable storage medium provided by the embodiments of the present invention may perform the related operations in the page display method of the mobile client provided by any embodiment of the present invention. That is, the program, when executed by the processor, implements:
when detecting that a target client starts running in the foreground currently, judging whether the target client is in a login state or not;
if so, acquiring a first user login role matched with the current login user when detecting that the foreground running state is not awakened from the background to the foreground;
responding to a viewing request of a first target page in the target client, and acquiring first user permission corresponding to each function control in the first target page according to the first user login role;
And updating the control layout matched with the first target page according to the first user permission corresponding to each function control in the first target page, and rendering and displaying the first target page according to the updated control layout matched with the first target page.
From the above description of embodiments, it will be clear to a person skilled in the art that the present invention may be implemented by means of software and necessary general purpose hardware, but of course also by means of hardware, although in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a computer readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, etc., and include several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the embodiments of the present invention.
It should be noted that, in the embodiment of the page display device of the mobile client, each unit and module included are only divided according to the functional logic, but not limited to the above-mentioned division, so long as the corresponding functions can be implemented; in addition, the specific names of the functional units are also only for distinguishing from each other, and are not used to limit the protection scope of the present invention.
Note that the above is only a preferred embodiment of the present invention and the technical principle applied. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, while the invention has been described in connection with the above embodiments, the invention is not limited to the embodiments, but may be embodied in many other equivalent forms without departing from the spirit or scope of the invention, which is set forth in the following claims.
Claims (10)
1. The page display method of the mobile client is characterized by comprising the following steps of:
when detecting that a target client starts running in the foreground currently, judging whether the target client is in a login state or not;
If so, acquiring a first user login role matched with the current login user when detecting that the foreground running state is not awakened from the background to the foreground;
responding to a viewing request of a first target page in the target client, and acquiring first user permission corresponding to each function control in the first target page according to the first user login role;
updating a control layout matched with the first target page according to a first user permission corresponding to each function control in the first target page, and rendering and displaying the first target page according to the updated control layout matched with the first target page;
the user permission comprises a visual permission and an operation permission, and the control layout matched with the first target page is updated according to the first user permission corresponding to each function control in the first target page, and the method comprises the following steps:
judging whether the current login user has visual permission for the current functional control, if not, carrying out hidden layout on the current functional control;
if yes, judging whether the current login user has operation authority on the current function control;
If the current login user is determined to have the operation authority on the current function control, configuring an operation event corresponding to the current function control; and if the current login user is determined to not have the operation authority on the current functional control, configuring alarm prompt information corresponding to the current functional control.
2. The method of claim 1, wherein detecting that the foreground operational state is not awakened from background to foreground comprises:
detecting whether a view component corresponding to a homepage of the target client exists in a view component manager of the target client;
if not, determining that the foreground running state is not awakened from the background to the foreground.
3. The method of claim 1, wherein detecting that the foreground operational state is not awakened from background to foreground comprises:
judging whether the process of the target client is in a survival state or not;
if so, determining that the foreground running state is not awakened from the background to the foreground when detecting that no view component corresponding to the homepage of the target client exists in the view component manager of the target client.
4. The method of claim 1, further comprising, after determining whether the target client is in a login state:
If not, displaying a login page of the target client to the current access user;
acquiring user login information input by the current access user in the login page, and acquiring a second user login role corresponding to the current access user according to the user login information;
responding to a viewing request of a second target page in the target client, and acquiring second user rights corresponding to all the functional controls in the second target page according to the second user login role;
and updating the control layout matched with the second target page according to the second user permission corresponding to each function control in the second target page, and rendering and displaying the second target page according to the updated control layout matched with the second target page.
5. The method of claim 1, further comprising, after determining whether the target client is in a login state:
if not, displaying a preset page of the target client to the current access user;
and responding to a viewing request of the current access user for a third target page in the target client, acquiring a standard control layout of the third target page, and rendering and displaying the third target page according to the standard control layout.
6. The method of claim 1, wherein rendering the first target page according to the updated control layout that matches the first target page comprises:
according to the updated control layout matched with the first target page, adjusting a basic layout file corresponding to the first target page, and obtaining an adjusted basic layout file;
rendering and displaying the first target page according to the adjusted basic layout file;
the basic layout file comprises picture layout data and text layout data corresponding to each function control in the first target page.
7. The method as recited in claim 1, further comprising:
according to a configuration request aiming at user login roles, at least one user login role is pre-established, user rights corresponding to all the functional controls of all the pages in the target client are configured for each user login role, and all the configured user login roles are obtained;
generating a corresponding relation between a user identifier corresponding to a target user and the configured user login role according to a user login role allocation request aiming at the target user, and storing the corresponding relation in a server;
The method for acquiring the first user login role matched with the current login user comprises the following steps:
and acquiring a first user login role matched with the current login user from the server according to the user identification corresponding to the current login user.
8. A page display device of a mobile client, comprising:
the login state judging module is used for judging whether the target client is in a login state or not when detecting that the target client is currently started to run in the foreground;
the first user login role acquisition module is used for acquiring a first user login role matched with a current login user when detecting that the foreground running state is not awakened from the background to the foreground if the first user login role acquisition module is used for acquiring the first user login role matched with the current login user;
the first user permission acquisition module is used for responding to a viewing request of a first target page in the target client and acquiring first user permissions corresponding to all function controls in the first target page according to the first user login role;
the first control layout updating module is used for updating the control layout matched with the first target page according to the first user permission corresponding to each function control in the first target page, and rendering and displaying the first target page according to the updated control layout matched with the first target page;
The user rights comprise visual rights and operation rights; the first control layout updating module comprises:
the control hiding layout unit is used for judging whether the current login user has visual permission for the current functional control, and if not, hiding layout is carried out on the current functional control;
the operation authority judging unit is used for judging whether the current login user has operation authority to the current function control or not if yes;
the information configuration unit is used for configuring an operation event corresponding to the current functional control if the current login user is determined to have operation authority on the current functional control; and if the current login user is determined to not have the operation authority on the current functional control, configuring alarm prompt information corresponding to the current functional control.
9. A client device, the client device comprising:
one or more processors;
a memory for storing one or more programs;
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the mobile client page presentation method of any of claims 1-7.
10. A computer storage medium having stored thereon a computer program, which when executed by a processor implements a page presentation method of a mobile client according to any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210112613.9A CN114518924B (en) | 2022-01-29 | 2022-01-29 | Page display method, device and equipment of mobile client and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210112613.9A CN114518924B (en) | 2022-01-29 | 2022-01-29 | Page display method, device and equipment of mobile client and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114518924A CN114518924A (en) | 2022-05-20 |
| CN114518924B true CN114518924B (en) | 2024-02-02 |
Family
ID=81596463
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210112613.9A Active CN114518924B (en) | 2022-01-29 | 2022-01-29 | Page display method, device and equipment of mobile client and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114518924B (en) |
Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2339807A1 (en) * | 2009-12-27 | 2011-06-29 | Polska Wytwornia Papierow Wartosciowych S.A. | Method for generating within a mobile phone application a time-limited client password |
| CN103065074A (en) * | 2012-12-14 | 2013-04-24 | 北京思特奇信息技术股份有限公司 | Uniform Resource Locator (URL) authority control method based on fine granularity |
| CN103500298A (en) * | 2013-10-12 | 2014-01-08 | 彩虹集团公司 | Method for achieving authorization distribution based on rule management |
| KR20140136854A (en) * | 2013-05-21 | 2014-12-01 | 삼성전자주식회사 | Application operating method and electronic device implementing the same |
| CN104335523A (en) * | 2014-04-15 | 2015-02-04 | 华为技术有限公司 | Access control method, client and server |
| CN105337967A (en) * | 2015-10-16 | 2016-02-17 | 晶赞广告（上海）有限公司 | Method and system for achieving target server logging by user and central server |
| CN108416199A (en) * | 2018-03-07 | 2018-08-17 | 北京恒华伟业科技股份有限公司 | A kind of user authority control method of application, device and server |
| CN108600177A (en) * | 2018-03-27 | 2018-09-28 | 北京明朝万达科技股份有限公司 | A kind of authority control method and device |
| CN109302388A (en) * | 2018-09-19 | 2019-02-01 | 平安科技（深圳）有限公司 | Access authority filter method, system, computer equipment and storage medium |
| CN109992380A (en) * | 2017-12-29 | 2019-07-09 | 广东欧珀移动通信有限公司 | Applied program processing method and device, electronic equipment, computer readable storage medium |
| CN110928595A (en) * | 2018-08-31 | 2020-03-27 | 北京搜狗科技发展有限公司 | Permission operation method and device |
| CN111079104A (en) * | 2019-11-21 | 2020-04-28 | 腾讯科技（深圳）有限公司 | Authority control method, device, equipment and storage medium |
| CN111159738A (en) * | 2019-12-26 | 2020-05-15 | 维沃移动通信有限公司 | Permission configuration method, application login method and device |
| WO2020233039A1 (en) * | 2019-05-22 | 2020-11-26 | 深圳壹账通智能科技有限公司 | User operation permission control method and apparatus, device, and medium |
| CN112181529A (en) * | 2020-10-12 | 2021-01-05 | Oppo广东移动通信有限公司 | Application program control method and device and electronic equipment |
-
2022
- 2022-01-29 CN CN202210112613.9A patent/CN114518924B/en active Active
Patent Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2339807A1 (en) * | 2009-12-27 | 2011-06-29 | Polska Wytwornia Papierow Wartosciowych S.A. | Method for generating within a mobile phone application a time-limited client password |
| CN103065074A (en) * | 2012-12-14 | 2013-04-24 | 北京思特奇信息技术股份有限公司 | Uniform Resource Locator (URL) authority control method based on fine granularity |
| KR20140136854A (en) * | 2013-05-21 | 2014-12-01 | 삼성전자주식회사 | Application operating method and electronic device implementing the same |
| CN103500298A (en) * | 2013-10-12 | 2014-01-08 | 彩虹集团公司 | Method for achieving authorization distribution based on rule management |
| CN104335523A (en) * | 2014-04-15 | 2015-02-04 | 华为技术有限公司 | Access control method, client and server |
| CN105337967A (en) * | 2015-10-16 | 2016-02-17 | 晶赞广告（上海）有限公司 | Method and system for achieving target server logging by user and central server |
| CN109992380A (en) * | 2017-12-29 | 2019-07-09 | 广东欧珀移动通信有限公司 | Applied program processing method and device, electronic equipment, computer readable storage medium |
| CN108416199A (en) * | 2018-03-07 | 2018-08-17 | 北京恒华伟业科技股份有限公司 | A kind of user authority control method of application, device and server |
| CN108600177A (en) * | 2018-03-27 | 2018-09-28 | 北京明朝万达科技股份有限公司 | A kind of authority control method and device |
| CN110928595A (en) * | 2018-08-31 | 2020-03-27 | 北京搜狗科技发展有限公司 | Permission operation method and device |
| CN109302388A (en) * | 2018-09-19 | 2019-02-01 | 平安科技（深圳）有限公司 | Access authority filter method, system, computer equipment and storage medium |
| WO2020233039A1 (en) * | 2019-05-22 | 2020-11-26 | 深圳壹账通智能科技有限公司 | User operation permission control method and apparatus, device, and medium |
| CN111079104A (en) * | 2019-11-21 | 2020-04-28 | 腾讯科技（深圳）有限公司 | Authority control method, device, equipment and storage medium |
| CN111159738A (en) * | 2019-12-26 | 2020-05-15 | 维沃移动通信有限公司 | Permission configuration method, application login method and device |
| CN112181529A (en) * | 2020-10-12 | 2021-01-05 | Oppo广东移动通信有限公司 | Application program control method and device and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114518924A (en) | 2022-05-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10877826B2 (en) | Message processing method and apparatus, storage medium, and computer device | |
| US11711670B2 (en) | Method for activating service based on user scenario perception, terminal device, and system | |
| CN108182060B (en) | Hybrid application point burying method, mobile terminal and system | |
| US20170351531A1 (en) | Information processing method and electronic apparatus thereof | |
| CN102918484A (en) | Web application pinning including task bar pinning | |
| CN102918540A (en) | Creating and launching a web application with credentials | |
| CN111177613A (en) | Page processing method, device, equipment and storage medium | |
| KR102413396B1 (en) | Method for providing push service using webpush and electronic device supporting the same | |
| CN115309470B (en) | Method, device, equipment and storage medium for loading widget | |
| CN111367518A (en) | Page layout method and device, computing equipment and computer storage medium | |
| CN107408004A (en) | A kind of graphic user interface on method, information processor, portable electric appts and the portable electric appts that information is presented in locking screen interface | |
| CN114385124A (en) | Independent page jumping method, device and equipment based on Vue framework | |
| CN114443200B (en) | Page display method, device and equipment of mobile client and storage medium | |
| CN114518924B (en) | Page display method, device and equipment of mobile client and storage medium | |
| CN111866557A (en) | Configuration method and device of large-screen display equipment, storage medium and electronic equipment | |
| JP2020177655A5 (en) | ||
| CN108279827B (en) | Method for controlling hiding and displaying of navigation bar of intelligent terminal | |
| CN115767112A (en) | Information processing method and device | |
| CN112416374B (en) | Data processing method, device, terminal and storage medium | |
| CN114895815A (en) | Data processing method and electronic equipment | |
| CN111625736B (en) | Link skip control method and related device | |
| CN111443907A (en) | Method and device for calling SDK function | |
| CN114265661B (en) | Page display method, device, equipment and storage medium for mobile client | |
| US20210326009A1 (en) | Method of presenting user interface, apparatus for presenting user interface, and computer-program product | |
| CN113885861B (en) | Method and device for multiplexing components of cross-system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |