CN114518924A - Page display method, device, equipment and storage medium for mobile client - Google Patents
Page display method, device, equipment and storage medium for mobile client Download PDFInfo
- Publication number
- CN114518924A CN114518924A CN202210112613.9A CN202210112613A CN114518924A CN 114518924 A CN114518924 A CN 114518924A CN 202210112613 A CN202210112613 A CN 202210112613A CN 114518924 A CN114518924 A CN 114518924A
- Authority
- CN
- China
- Prior art keywords
- user
- page
- target
- login
- client
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 52
- 238000009877 rendering Methods 0.000 claims abstract description 24
- 230000006870 function Effects 0.000 claims description 72
- 230000000007 visual effect Effects 0.000 claims description 13
- 230000008569 process Effects 0.000 claims description 12
- 238000004590 computer program Methods 0.000 claims description 5
- 230000004083 survival effect Effects 0.000 claims description 5
- 230000002618 waking effect Effects 0.000 claims 2
- 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
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
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 operating state is not waken up from a background to a foreground, acquiring first user permissions corresponding to the functional controls of the first target page according to a first user login role matched with the current login user; and then updating the control layout matched with the first target page according to the first user permission, and rendering and displaying the first target page according to the updated control layout. According to the technical scheme, the user permission corresponding to the login user is determined in a mode of configuring the login role of the user, and then the exclusive client page is displayed to the login user according to the user permission, so that the client page can be updated in real time, the differentiated display of the client page can be realized, 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, a page display device, page display equipment and a storage medium of a mobile client.
Background
With the continuous development of the mobile application technology, in the display page of the application program, aiming at different page contents which are not displayed by a user, 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, in an existing page display method for an application program, corresponding permissions are usually configured for different users manually, and then when it is detected that a user logs in the application program, a corresponding function module is displayed to the user according to the corresponding permission of the user. However, in the prior art, once the user right is manually configured, the corresponding page display content and the page display effect are fixed, and when the page display content and the page display effect need to be updated, the user right needs to be reconfigured, so that the updating instantaneity of the page display content and the page display effect is poor; in addition, in the prior art, the number or the type of the functional modules that can be displayed in the page can be adjusted only by configuring different user permissions, but the display effect of the functional modules can not be dynamically adjusted, so that the page display effect that can be realized is limited and single.
Disclosure of Invention
The invention provides a page display method, a page display device, page display equipment and a page display storage medium of a mobile client, which can realize real-time update of a client page, can realize differentiated display of the client page and can improve the differentiated display effect of the client page.
In a first aspect, an embodiment of the present invention provides a page display method for a mobile client, including:
when detecting that a target client side starts to run in a foreground currently, judging whether the target client side is in a login state or not;
if yes, acquiring a first user login role matched with the current login user when detecting that the foreground running state is not waken from the background to the foreground;
responding to a viewing request of a first target page in the target client, and acquiring first user permissions corresponding to all functional controls 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 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 second aspect, an embodiment of the present invention further provides a page display apparatus for 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 starts to run in the foreground currently;
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 operating state is not waken 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 when the foreground operating state is detected not to be waken from the background to the foreground;
the first user permission obtaining module is used for responding to a viewing request of a first target page in the target client and obtaining first user permissions corresponding to the functional 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;
when the one or more programs are executed by the one or more processors, the one or more processors implement the page display method of the 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, on which a computer program is stored, where the computer program, when executed by a processor, implements the page display 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 and the foreground running state of the target client are detected, so that frequent and unnecessary requests of the client for the user login role can be avoided, the request times of the corresponding interface of the background server are reduced, and the data processing pressure of the background server is reduced; in the interaction process of a user and a target client, the user login role matched with the current login user is given to configure the user right corresponding to the current login user, the control layout corresponding to the page is updated according to the user right, so that the exclusive client page is displayed for the current login user, the real-time updating of the page display content and the page display effect can be realized, the control layout matched with the client page is updated, the differential display of the client page can be realized, and the differential display effect of the client page can be improved.
Drawings
Fig. 1A is a flowchart of a page display method of a mobile client according to a first embodiment of the present invention;
FIG. 1B is a diagram illustrating a mobile client page according to an embodiment of the present invention;
fig. 2 is a flowchart of a page display method of a mobile client according to a second embodiment of the present invention;
fig. 3 is a flowchart of a page display method of a mobile client according to a third embodiment of the present invention;
FIG. 4 is a block diagram of a page displaying apparatus of a mobile client according to a fourth embodiment of the present invention;
fig. 5 is a block diagram of a client device according to a fifth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Example one
Fig. 1A is a flowchart of a page display method of a mobile client according to an embodiment of the present invention, where this embodiment is applicable to configuring different user permissions for different login users of a client, and further displays a customized client page to the login user according to the user permissions, and the method may be executed by a page display device of the mobile client according to an embodiment of the present invention and is integrated on a client device, where typically, the client device may be a mobile terminal, and specifically includes the following steps:
s110, when the fact that the target client side starts to run in the foreground currently is detected, whether the target client side is in a login state or not is judged.
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. Optionally, "foreground" and "background" are both 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, it may be determined that the application program runs 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 started, it may be determined that the target client currently starts to operate in the foreground; or when the view component corresponding to a certain page of the target client is detected to be created, the target client can be determined to be currently started to run in the foreground. Further, when it is determined that the target client starts to run in the foreground, whether the target client is currently in a login state is judged.
And S120, if yes, acquiring a first user login role matched with the current login user when the foreground running state is detected not to be awakened from the background to the foreground.
The user login role is associated with user permissions corresponding to all the functional controls contained in the target client; the background server can configure user permissions corresponding to the functional controls for the user by endowing the target client with user login roles corresponding to the user. The background server may be a remote device communicating with the target client.
The function control refers to a program entity for implementing a specific function, for example, the function control may include an interview duty registration control, a member leaving list control, a code scanning sub-target control, and the like. Correspondingly, the user permissions may include behavior permissions (e.g., whether the user can be selected and jump after being selected, etc.) and state permissions (e.g., whether the user can be seen) corresponding to the functionality control.
In this embodiment, the corresponding user right is configured for the user of the target client by giving the matched user login role, so that when different users correspond to the same user right, only one user login role corresponding to the same user right needs to be configured. At the moment, the user login role is given to each user, so that the same corresponding user authority can be configured for each user, 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 permission needs to be updated, only the latest user login role of the current user needs to be given, and the real-time performance of user permission updating 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 started before a short time and is not currently logged out; at this time, the user login role corresponding to the current login user is not changed due to the short interval time. If the target client requests the user login role again from the background server, repeated requests for the same user login role in a short time can be caused, the effectiveness of obtaining the user login role can be reduced, the request times of a corresponding interface of the background server can be increased, and the data processing pressure of the background server can be increased.
In view of the above problem, in this embodiment, after determining that the target client is in the login state, it is further determined whether the target client is woken up from the background to the foreground, that is, whether the target client has been started before and has not exited. If the current foreground running state is determined not to be woken up from the background to the foreground, a user login role obtaining request can be sent to the background server. After receiving the user login role obtaining request, the background server may search a pre-established correspondence between the user identifier and the user login role according to the user identifier (e.g., a user name or a user account) of the current login user, and obtain a first user login role matched with the current login user, and send the first user login role to the target client. And 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 continuously used.
The advantages of the above arrangement are: by judging the current foreground running state of the target client, whether the matched user login role is requested to the background server or not is determined, repeated requests for the same user login role can be avoided, the effectiveness of obtaining the user login role can be improved, in addition, frequent and unnecessary requests for the user login role to the background server can be avoided, the number of requests for a corresponding interface of the background server can be reduced, and the data processing pressure of the server is reduced.
In an optional implementation manner of this embodiment, detecting that the foreground running state is not waken from the background to the foreground may include: detecting whether a view component corresponding to a main page of the target client exists in a view component manager of the target client; if not, determining that the foreground running state is not waken from the background to the foreground.
The view components are software entities for realizing the display of the client pages and correspond to the client pages one by one; correspondingly, the view component manager is a functional module for recording and managing the view components. In this embodiment, a view component manager having a history view component recording function may be locally provided to store view components corresponding to pages displayed by a target client within a certain time. It is noted that when the target client is completely closed, killed by the background of the operating system, or restarted by the terminal on which 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 user opens the client, the user defaults to enter the main page of the client, 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 is not completely closed, the user must open the main page of the target client, and thus a view component for displaying the main page of the target client must exist in the view component manager; therefore, whether the target client is awakened from the background to the foreground can be judged by searching the view component corresponding to the main page in the view component manager of the target client.
In a specific example, when the target client corresponds to an 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 a program and a user; specifically, the Activity component can realize the whole process of creating, displaying and ending the interactive interface through a series of preconfigured controls. Specifically, in an Activity component manager of a target client, detecting whether an Activity component corresponding to a main page of the target client exists or not; if the target client is determined to exist, the target client can be determined to be woken up from the background to the foreground.
It should be noted that, at present, the login states of many APPs are cached locally, and even if the APP is completely turned off or the mobile phone is restarted, if the APP is restarted within the validity period, the APP is still in the login state and does not need to be logged in again, for example, after the WeChat is turned off, the APP does not need to be logged in again when the mobile phone is turned on again. However, the validity period of the APP setting may be 1 week or more, and during this period, the background server may update the matching user login role. Therefore, if only the login status of the target client is detected, the latest user login role matched with the current login user may not be obtained in time.
In this embodiment, after the target client is detected to be in the login state, whether to request the background server to acquire the current user login role is determined according to whether the view component corresponding to the home page exists in the view component manager, so that the latest user login role can be acquired in time, frequent and unnecessary requests for the user login role caused by the situation 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 manner of this embodiment, detecting that the foreground running state is not waken 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 wakened from the background to the foreground when detecting that the view component corresponding to the main page of the target client does not exist in the view component manager of the target client.
In this embodiment, when detecting whether the foreground running state is woken up from the background to the foreground, it may also be detected whether the background process of the target client is in a live state; if so, determining that the target client is not completely killed by the background of the operating system; further, if it is determined that a view component corresponding to the home page exists in the view component manager, it may be determined that the current foreground operating state of the target client is woken up from the background to the foreground.
The advantages of the above arrangement are: whether the process corresponding to the target client is in the survival state or not and whether the view component manager comprises the view component corresponding to the main page or not are combined, whether the foreground running state is awakened from the background to the foreground or not is finally judged, and the judgment accuracy of the foreground running 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 permissions corresponding to the functional controls in the first target page according to the first user login role.
It should be noted that, in this embodiment, the association relationship between each user login role and the user right corresponding to each function control in each page may be pre-established; specifically, a corresponding layout configuration file may be set in advance 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 for the target client in advance, where the layout configuration file may include layout data corresponding to all the functional controls included in the target client, a page identifier of a page corresponding to each functional control, and user permissions corresponding to each functional control and each user login role respectively.
Therefore, when the target client detects that the current login user clicks and selects the first target page, the first user permission corresponding to each function control in the first target page can be obtained 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.
S140, updating the control layout matched with the first target page according to the first user authority 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 this embodiment, each function 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 function controls that can be displayed on the corresponding function page, each row corresponds to one function control, and the initial order of each function control is preset. Therefore, after the first user permissions corresponding to the function controls in the first target page are acquired, the initial control layout can be updated according to the first user permissions corresponding to the function controls, that is, the number of the displayable function controls and the display effects (for example, display positions, click events and the like) of the function controls are updated.
Taking the code scanning and getting sub-control as an example, for the function control, if the user right corresponding to the first user login role is visual and operable, the code scanning and getting sub-control can be displayed at a corresponding position in the current page and is in a selectable state (for example, the user jumps to a set page after being clicked); or, if the user right corresponding to the first user login role is "visible but inoperable," the code-scanning-collar sub-control may still be displayed at the corresponding position in the current function page, but is in a non-selectable state (for example, after being clicked, only preset warning information pops up, and does not jump to a set page); for another example, if the user right corresponding to the first user login role is invisible, the code scanning collar sub-control will be hidden and become invisible.
Optionally, when it is detected that, for a certain function control, the user right corresponding to the first user login role is invisible, the function control becomes a hidden state, and in the function controls having the visible right corresponding to the first user login role, the nearest function control below the function control is determined, and the nearest function control is automatically moved upwards to replace the position of the detected function 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 right corresponding to the code scanning collar sub-control is invisible and the user right corresponding to the supplier bill control is visible, the supplier bill control automatically moves up to replace the position where the code scanning collar sub-control is located.
The advantages of the above arrangement are: if the current login user only has the visual permission of part of the functional controls, the appearance of blank display areas 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 checking the client page can be improved.
In this embodiment, after the updating of the control layout corresponding to the first target page is completed, the layout codes of the functional controls corresponding to the updated control layout may be executed according to the control layout corresponding to the updated 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 give the latest user login role to the user of the target client, so as to update the user permission corresponding to the user, and then update the control layout of the client page according to the updated user permission corresponding to the user. Through the setting, when the user login role corresponding to the user is changed, the real-time performance of the client page updating can be improved.
Optionally, each page of the target client may be set to be a page display supporting different user login roles. Or only part of pages of the target client can be set as page displays supporting different user login roles; at the moment, for the functional page displayed by the page which does not support different user login roles, the page layouts seen by the users corresponding to the different user login roles are the same; for the functional pages displayed by the pages supporting different user login roles, the page layouts seen by the users corresponding to the different user login roles are different. Through the setting, the flexibility of the target client page display can be further improved.
According to the technical scheme provided by the embodiment of the invention, the login state and the foreground running state of the target client are detected, so that frequent and unnecessary requests of the client for the user login role can be avoided, the request times of the corresponding interface of the background server are reduced, and the data processing pressure of the background server is reduced; in the interaction process of a user and a target client, the user login role matched with the current login user is given to configure the user right corresponding to the current login user, the control layout corresponding to the page is updated according to the user right, so that the exclusive client page is displayed for the current login user, the real-time updating of the page display content and the page display effect can be realized, the control layout matched with the client page is updated, the differential display of the client page can be realized, and the differential 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 established in advance, user permissions corresponding to function controls of pages in a target client side are configured for each user login role, and each configured user login role is obtained; generating a corresponding relation between a user identifier 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 a server; correspondingly, the obtaining of 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 identifier 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 established in advance through the server; suppose that the page 1 of the target client comprises a code scanning and getting sub-control, and the permission options corresponding to the code scanning and getting sub-control comprise visible, invisible, operable and inoperable; wherein visible and invisible cannot exist simultaneously, operable and inoperable cannot exist simultaneously. At this time, the user login role a can be configured with the user right corresponding to the code scanning collar sub-control as visible and operable, the user login role B can be configured with the user right corresponding to the code scanning collar sub-control as visible but inoperable, and the user login role C can be configured with the user right corresponding to the code scanning collar sub-control as invisible. Furthermore, the mapping relationship between the configured user login role and the "user permission corresponding to the function control" may be stored, so as to implement configuration of the user login role.
Secondly, after the configuration of the user login roles is completed, a matched user login role can be configured for each user; for example, user 1, user 2, and user 3 are currently present, 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 first matching 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. The value is noted that different user login roles can be allocated to different users, the same user login role can also be allocated to different users, and flexible allocation of the user login roles can 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 this embodiment is a further refinement of the foregoing technical solution, and the technical solution in this embodiment may be combined with one or more of the foregoing implementations. Specifically, referring to fig. 2, the method specifically includes the following steps:
s210, when detecting that the target client side starts to operate in the foreground currently, judging whether the target client side is in a login state.
And S220, if not, displaying the login page of the target client to the current access user.
S230, obtaining user login information input by the current access user in the login page, and obtaining a second user login role corresponding to the current access user according to the user login information.
In one scenario, after a 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 accessing user at the human-computer interaction interface. The current access user can input user login information such as a user account, a user password and the like in the login page and click a login button. When the target client detects the click of the login button, the target client sends the user login information input by the user to the background server and requests a user login interface of the background server to verify the user login information. The method comprises the steps that when a background server detects a request of a target client to a user login interface, received user login information is verified; if the user identity verification is successfully passed, 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 the historical user login role corresponding to the current access user, the target client may update the locally cached historical user login role by using 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 permission corresponding to each functional control in the second target page according to the second user login role.
And S250, 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.
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 to 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 may 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 is stored.
In another scenario, when the target client is in an unregistered state, a preset page may be displayed to the current visiting user, that is, the current visiting user is allowed to visit the target client in a guest mode. The preset page may be any function page of a pre-specified target client, for example, the preset page may be a main page. Further, when a click viewing instruction of the current access user for the third target page is detected, the pre-established correspondence between the page identifier and the standard control layout can be searched according to the page identifier of the third target page, so as to obtain the standard control layout matched with the third target page, and then 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, whether the target client is in a login state or not is judged by detecting that the target client starts to run in a foreground currently; when the target client is determined not to be in the login state, displaying a login page of the target client to a current access user; further acquiring user login information input by the current access user in a login page, and acquiring a second user login role corresponding to the current access user 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 permissions corresponding to the functional controls in the second target page according to the second user login role; finally, according to the second user authority corresponding to each functional control in the second target page, updating the control layout matched with the second target page, and according to the updated control layout matched with the second target page, rendering and displaying the second target page; when the user does not log in, the matched user login role is obtained according to the user login information, so that the user login role can be obtained in time, and the real-time dynamic configuration of the user permission can be further realized.
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, which is a further refinement of the foregoing technical solution, and 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.
S320, when the target client is detected to start to operate in the foreground currently, judging whether the target client is in a login state.
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 acquire the latest first user login role matched with the current login user. And if the target client is determined not to be in the login state, providing a login page for the user so that the user inputs user login information, and then 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 be awakened from the background to the foreground, acquiring a first user login role matched with the current login user, and executing S340.
S340, responding to a viewing request of a first target page in the target client, acquiring first user permissions corresponding to the functional controls in the first target page according to the first user login role, and executing S350.
And S350, updating the control layout matched with the first target page according to the first user authority corresponding to each functional 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 permissions include a visual permission and an operation permission, and 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 may include: judging whether the current login user has visual authority on the current function control, if not, hiding and arranging the current function control; if yes, judging whether the current login user has operation authority on the current function control; if the current login user has the operation authority on the current function control, configuring an operation event corresponding to the current function control; and if the current login user does not have the operation authority on the current function control, configuring alarm prompt information corresponding to the current function control.
In this embodiment, when the user right is a visual right and an operation right, the first target page may be display-controlled according to the visual right and the operation right corresponding to each function control in the first user login role and the first target page. Specifically, for the current function control, firstly, whether the current login user has the visual authority is judged, and if the current login user does not have the visual authority, the current function control can be directly subjected to hidden layout; 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 be invisible but occupies the display area.
If the current function control is determined to have the visual authority, whether the current function control has the operation authority needs to be further judged, and if the current function control has the operation authority, an operation event corresponding to the current function control can be configured; for example, click event logic (e.g., jump to a specified page) when a user clicks is configured. However, if it is determined that the operation authority is not available, a corresponding warning prompt message (e.g., "no operation authority") may be configured. The operation event and the alarm prompt message can be predefined, and automatic configuration is carried out when the condition that the corresponding configuration condition is met is detected.
Correspondingly, after the first target page is rendered and displayed 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, the pre-configured operation event is directly executed; and if the corresponding operation authority is not provided, popping up corresponding alarm prompt information.
In another optional implementation manner of this embodiment, the 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 to obtain an adjusted basic layout file; rendering and displaying the first target page according to the adjusted basic layout file; and 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 (e.g., a page length, a page width, etc.) of the current page, and layout codes (e.g., a display position, a display length and a display width of the function control, a corresponding picture, text, etc.) of all the function controls that can be displayed. 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 function control in the hidden layout is deleted or hidden; and then rendering and displaying the first target page according to the adjusted basic layout file.
In a specific example, as shown in fig. 1B, in the client page, the display effect of each function control is a left picture, a middle text, and a right picture, taking the code scanning getting quilt control as an example, the left picture is a setting icon, the middle text is "code scanning getting 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 function control; wherein the picture layout data may be a storage path of the picture.
The advantages of the above arrangement are: by adjusting the matched basic layout file, the client pages containing different functional controls can be displayed to the users corresponding to different user login roles, the differentiated display of the client pages can be realized, and the differentiated display effect of the client pages is further improved.
And S360, displaying a login page of the target client to the current access user, and executing S370.
S370, obtaining the 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 permissions corresponding to the functional controls in the second target page according to the second user login role, and executing S390.
And S390, updating the control layout matched with the second target page according to the second user authority corresponding to each functional 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.
And S3100, ending.
According to the technical scheme provided by the embodiment of the invention, whether the target client is in a login state is judged by detecting that the target client starts to run in a foreground; if the target client is determined to be in the login state, acquiring a first user login role matched with a current login user when the foreground running state is determined not to be awakened from the background to the foreground; if the target client is determined to be in the non-login state, the login page is provided for the current access user to obtain the user login information, and then the second user login role matched with the current access user is obtained according to the user login information, so that the latest user login role corresponding to the user can be obtained in time, the timeliness of obtaining 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, the effectiveness of the obtained user login role can be ensured, and the balance of timeliness and effectiveness of obtaining the user login role can be realized through the setting.
Example four
Fig. 4 is a block diagram of a structure of a page display apparatus of a mobile client according to a fourth embodiment of the present invention, where the apparatus specifically includes: a login state judgment module 410, a first user login role acquisition module 420, a first user permission acquisition module 430 and a first control layout updating module 440; wherein;
a login state determining module 410, configured to determine whether a target client is in a login state when it is detected that the target client starts to run in a foreground currently;
a first user login role obtaining module 420, configured to, if yes, obtain a first user login role matched with a current login user when detecting that a foreground operating state is not to be woken up from a background to a foreground;
a first user permission obtaining module 430, configured to, in response to a viewing request for a first target page in the target client, obtain, according to the first user login role, first user permissions corresponding to the function controls in the first target page;
and a first control layout updating module 440, configured to update 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 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 and the foreground running state of the target client are detected, so that frequent and unnecessary requests of the client for the user login role can be avoided, the number of requests for 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 a user and a target client, the user login role matched with the current login user is given to configure the user right corresponding to the current login user, the control layout corresponding to the page is updated according to the user right, so that the exclusive client page is displayed for the current login user, the real-time updating of the page display content and the page display effect can be realized, the control layout matched with the client page is updated, the differential display of the client page can be realized, and the differential display effect of the client page can be improved.
Optionally, on the basis of the foregoing technical solution, the first user login role obtaining module 420 includes:
the view component detection unit is used for detecting whether a view component corresponding to the main page of the target client exists in a view component manager of the target client;
and the first foreground running state detection unit is used for determining that the foreground running state is not waken from the background to the foreground if the foreground running state is not waken from the background to the foreground.
Optionally, on the basis of the foregoing technical solution, the first user login role obtaining module 420 includes:
a process survival judging unit, configured to judge whether a process of the target client is in a survival state;
and the second foreground running state detection unit is used for determining that the foreground running state is not wakened from the background to the foreground when detecting that the view component corresponding to the main page of the target client does not exist in the view component manager of the target client if the foreground running state is detected to exist.
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 the login page of the target client to the current access user if the current access user does not access the target client;
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 obtaining module is used for responding to a viewing request of a second target page in the target client and obtaining second user permissions corresponding to the functional controls in the second target page according to the login role of the second user;
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 the preset page is not displayed;
and the standard control layout acquisition module is used for responding to a viewing request of the current access user for a 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 right includes a visual right and an operation right; a first control layout update module 440, comprising:
the control hiding layout unit is used for judging whether the current login user has visual permission on the current function control, and if not, hiding layout is carried out on the current function control;
an operation authority judging unit, configured to judge whether the current login user has an operation authority for the current function control if the current login user has the operation authority;
the information configuration unit is used for configuring an operation event corresponding to the current function control if the current login user is determined to have the operation authority on the current function control; and if the current login user does not have the operation authority on the current function control, configuring alarm prompt information corresponding to the current function control.
Optionally, on the basis of the foregoing technical solution, the first control layout updating module 440 includes:
a basic layout file adjusting unit, configured to adjust a basic layout file corresponding to the first target page according to the updated control layout matched with the first target page, and obtain an adjusted basic layout file;
the target page rendering and displaying unit is used for rendering and displaying the first target page according to the adjusted basic layout file; and 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 user permission corresponding to each function control of each page in a target client for each user login role, and acquiring each configured user login role;
the corresponding relation generating module is used for generating the corresponding relation between the user identification corresponding to the target user and the configured user login role according to the user login role distribution 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 matched with the current login user according to the 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 corresponding functional modules and beneficial effects of the execution method. For technical details that are not described in detail in this embodiment, reference may be made to the methods provided in the foregoing embodiments of the present invention.
EXAMPLE five
Fig. 5 is a schematic structural diagram of a client apparatus according to a fifth embodiment of the present invention, as shown in fig. 5, the client apparatus 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, and one processor 510 is taken as an example in fig. 5; the processor 510, memory 520, input device 530, and output device 540 in the client device may be connected by a bus or other means, such as by a bus connection in fig. 5. The memory 520 is used as a computer-readable storage medium, and can be used for storing software programs, computer-executable programs, 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, the login state determining module 410, the first user login role obtaining module 420, the first user permission obtaining module 430, and the first control layout updating module 440 in a page display apparatus of a mobile client). The processor 510 executes various functional applications and data processing of the client device by executing software programs, instructions and modules stored in the memory 520, so as to implement the page display method of the mobile client. That is, the program when executed by the processor implements:
when detecting that a target client side starts to run in a foreground currently, judging whether the target client side is in a login state or not;
if yes, acquiring a first user login role matched with the current login user when detecting that the foreground running state is not waken from the background to the foreground;
responding to a viewing request of a first target page in the target client, and acquiring first user permissions corresponding to all functional controls 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 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.
The memory 520 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the terminal, and the like. Further, the 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 client devices over 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 device 530 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the client device, and may include a keyboard and a mouse, etc. The output device 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, on which a computer program is stored, where the computer program is executed by a processor to implement the method according to any embodiment of the present invention. Of course, the computer-readable storage medium provided in the embodiments of the present invention may perform related operations in the page displaying method of the mobile client provided in any embodiment of the present invention. That is, the program when executed by the processor implements:
when the fact that the target client side starts to run in the foreground currently is detected, whether the target client side is in a login state or not is judged;
if yes, acquiring a first user login role matched with the current login user when detecting that the foreground running state is not waken from the background to the foreground;
responding to a viewing request of a first target page in the target client, and acquiring first user permissions corresponding to all functional controls 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 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.
From the above description of the embodiments, it is obvious for those skilled in the art that the present invention can be implemented by software and necessary general hardware, and certainly, can also be implemented by hardware, but the former is a better embodiment in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which can be stored in a computer-readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to execute the methods according to the embodiments of the present invention.
It should be noted that, in the embodiment of the page display apparatus of the mobile client, each unit and each module included in the page display apparatus are only divided according to functional logic, but are not limited to the above division as long as the corresponding function can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. 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, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (11)
1. A page display method of a mobile client is characterized by comprising the following steps:
when detecting that a target client side starts to run in a foreground currently, judging whether the target client side is in a login state or not;
if yes, acquiring a first user login role matched with the current login user when detecting that the foreground running state is not waken from the background to the foreground;
responding to a viewing request of a first target page in the target client, and acquiring first user permissions corresponding to all functional controls 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 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.
2. The method of claim 1, wherein detecting that the foreground operating state is not waking from background to foreground comprises:
detecting whether a view component corresponding to a main page of the target client exists in a view component manager of the target client;
if not, determining that the foreground running state is not waken from the background to the foreground.
3. The method of claim 1, wherein detecting that the foreground operating state is not waking 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 wakened from the background to the foreground when detecting that the view component corresponding to the main page of the target client does not exist in the view component manager of the target client.
4. The method of claim 1, after determining whether the target client is in a logged-on state, further comprising:
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 permissions corresponding to 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 authority 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.
5. The method of claim 1, after determining whether the target client is in a logged-on state, further comprising:
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 to 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 the user permissions include a visual permission and an operation permission, and updating the layout of the control matched with the first target page according to the first user permission corresponding to each functional control in the first target page comprises:
judging whether the current login user has visual permission on the current function control, and if not, hiding and arranging the current function control;
if yes, judging whether the current login user has operation authority on the current function control;
if the current login user has the operation authority on the current function control, configuring an operation event corresponding to the current function control; and if the current login user does not have the operation authority on the current function control, configuring alarm prompt information corresponding to the current function control.
7. The method of claim 6, wherein rendering and displaying the first target page according to the updated control layout matched with 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 to obtain an adjusted basic layout file;
rendering and displaying the first target page according to the adjusted basic layout file;
and the basic layout file comprises picture layout data and text layout data corresponding to each function control in the first target page.
8. The method of claim 1, further comprising:
according to a configuration request aiming at user login roles, at least one user login role is established in advance, user permissions corresponding to function controls of pages in a target client side are configured for each user login role, and each configured user login role is obtained;
generating a corresponding relation between a user identifier 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 a server;
acquiring a first user login role matched with a current login user, wherein the acquiring comprises the following steps:
and acquiring a first user login role matched with the current login user from the server according to the user identifier corresponding to the current login user.
9. A page display device of a mobile client is characterized by 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 starts to run in the foreground currently;
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 operating state is not waken 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 when the foreground operating state is detected not to be waken from the background to the foreground;
the first user permission obtaining module is used for responding to a viewing request of a first target page in the target client and obtaining first user permissions corresponding to the functional 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.
10. A client device, the client device comprising:
one or more processors;
a memory for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement the page presentation method of the mobile client according to any one of claims 1-8.
11. A computer storage medium on which a computer program is stored, which program, when executed by a processor, implements a page presentation method for a mobile client according to any one of claims 1 to 8.
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 true CN114518924A (en) | 2022-05-20 |
| CN114518924B 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 |
|---|---|
| CN114518924B (en) | 2024-02-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10877826B2 (en) | Message processing method and apparatus, storage medium, and computer device | |
| US11218842B2 (en) | Method for activating service based on user scenario perception, terminal device, and system | |
| US9130927B2 (en) | Single certificate service system and operational method thereof | |
| CN106775836B (en) | Interface display method and interface display device | |
| US20190052476A1 (en) | Smart appliance control method and smart appliance | |
| KR102448387B1 (en) | Efficient control and/or connection of smart devices | |
| CN110990741B (en) | Page display method and device, electronic equipment, server and storage medium | |
| CN108595919B (en) | Software activation method, device, system and storage medium | |
| CN108710528A (en) | Access, control method, device, equipment and the storage medium of desktop cloud virtual machine | |
| CN111177613A (en) | Page processing method, device, equipment and storage medium | |
| US20220201049A1 (en) | Systems and methods for sharing content externally from a group-based communication platform | |
| CN113342455B (en) | Layer processing method based on multiple operating systems and vehicle-mounted machine system | |
| CN113949885B (en) | Live broadcast processing method and device, electronic equipment and computer readable storage medium | |
| US20230084001A1 (en) | Video playing method, apparatus and device in map, computer-readable storage medium and computer program product | |
| CN115309470B (en) | Method, device, equipment and storage medium for loading widget | |
| CN105100203B (en) | Show the method and terminal of monitoring data | |
| CN115037970B (en) | Control validity detection method and display device | |
| CN109948332A (en) | A kind of physical machine login password remapping method and device | |
| CN114443200B (en) | Page display method, device and equipment of mobile client and storage medium | |
| CN102970207A (en) | Instant communication method, client device and instant communication system | |
| CN106201182A (en) | The method and device that application subfield is shown | |
| CN110417601B (en) | Information prompting method, device and system in client and readable storage medium | |
| CN114518924B (en) | Page display method, device and equipment of mobile client and storage medium | |
| US11442606B2 (en) | User interface interaction method and system | |
| CN114567659A (en) | Cloud mobile phone control method, device, equipment and storage medium |
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 |