CN110750322B - Page management method in terminal equipment and related device - Google Patents
Page management method in terminal equipment and related device Download PDFInfo
- Publication number
- CN110750322B CN110750322B CN201911012970.2A CN201911012970A CN110750322B CN 110750322 B CN110750322 B CN 110750322B CN 201911012970 A CN201911012970 A CN 201911012970A CN 110750322 B CN110750322 B CN 110750322B
- Authority
- CN
- China
- Prior art keywords
- page
- target button
- target
- display
- triggered
- 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
- 238000007726 management method Methods 0.000 title abstract description 52
- 238000000034 method Methods 0.000 claims abstract description 65
- 230000001960 triggered effect Effects 0.000 claims abstract description 39
- 238000001514 detection method Methods 0.000 claims description 13
- 238000004590 computer program Methods 0.000 claims description 3
- 230000000977 initiatory effect Effects 0.000 claims description 3
- 230000008569 process Effects 0.000 abstract description 27
- 238000010586 diagram Methods 0.000 description 12
- 238000012545 processing Methods 0.000 description 5
- 238000012795 verification Methods 0.000 description 5
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 239000000725 suspension Substances 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012856 packing Methods 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000006467 substitution reaction 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
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
-
- 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/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Human Computer Interaction (AREA)
- Computer Hardware Design (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The application discloses a page management method and a related device, wherein a current display page is determined to be a first page; when the feature element is triggered, a second page is called; generating a target button when the user authentication is not passed; and when the target button is triggered within a preset time period, calling the target flow to display a corresponding page. Because the first page can be switched to the background and can be associated through the convenient target button, the user clicks the target button to fill in the relevant page after searching the relevant real-name information, the filled content is ensured not to be lost, the convenience of the real-name authentication process is improved, and the user experience is improved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and a related device for page management in a terminal device.
Background
Along with the development of mobile technology, more and more intelligent devices are in life of people, meanwhile, people increasingly start to use a mobile payment function, and in the payment process, real-name authentication is often required to ensure the safety of the payment process.
Generally, when a transaction page clicks to submit or purchase, a real-name authentication page is popped up, and a user can complete the next transaction operation after inputting corresponding information.
However, in some scenarios, the user may not remember the relevant real-name information, and cannot timely fill in the relevant information, and the user needs to log out of the payment page and then inquire, so that the user cannot timely and immediately process the payment page, and the information of the filled order is lost, so that convenience in the real-name authentication process is reduced, and user experience is affected.
Disclosure of Invention
In view of the foregoing, a first aspect of the present application provides a method for page management, which is applicable to a mobile transaction system or a program process, and specifically includes: determining a current display page as a first page, wherein the first page comprises a plurality of characteristic elements interacted with by a user;
If the feature element is triggered, a second page is called, wherein the second page is used for user authentication, and the second page and the first page are pages in a target flow;
if the user authentication is not passed, generating a target button, wherein the target button is used for indicating the call of the target flow, the target button is positioned at the uppermost layer in the display page, and other elements in the display page can be operated by a user;
and if the target button is triggered within a preset time period, invoking the target flow to display a corresponding page.
Preferably, in some possible implementations of the present application, the calling the second page if the feature element is triggered includes:
if the characteristic element is triggered, initiating blank detection, wherein the blank detection is used for detecting whether information indicated by a target element is blank or not;
and if the information indicated by the target element is not blank, calling a second page.
Preferably, in some possible implementations of the present application, the generating the target button if the user authentication is not passed includes:
if the user authentication is not passed, the first page is saved;
Associating the first page with the target button;
And generating the target button in the display page.
Preferably, in some possible implementations of the present application, the associating the first page with the target button includes:
Determining identification information of the first page, wherein the identification information is determined based on characteristic elements indicating operation information in the first page;
And associating the target button with the identification information, and displaying characteristic pixels on the target button, wherein the characteristic pixels correspond to the identification information.
Preferably, in some possible implementations of the present application, if the user authentication is not passed, saving the first page includes:
If the user authentication is not passed, traversing the input field in the second page;
if the input field reaches the preset length, the input field is saved and is associated with the first page;
the first page associated with the input field is saved.
Preferably, in some possible implementations of the present application, before the generating the target button, the method further includes:
Displaying a third page, wherein the third page is used for indicating the association relation between the target button and the first page;
and if the characteristic elements in the third interface are triggered, canceling the display of the third page.
Preferably, in some possible implementations of the present application, the method of page management is applied to a terminal device, where the terminal device is a block node device in a block chain node.
A second aspect of the present application provides an apparatus for page management, including: the determining unit is used for determining the current display page as a first page, wherein the first page comprises a plurality of characteristic elements interacted with by a user;
the calling unit is used for calling a second page if the characteristic element is triggered, the second page is used for user authentication, and the second page and the first page are pages in a target flow;
The generating unit is used for generating a target button if the user authentication is not passed, wherein the target button is used for indicating the call of the target flow, the target button is positioned at the uppermost layer in the display page, and other elements in the display page can be operated by a user;
And the triggering unit is used for calling the target flow to display the corresponding page if the target button is triggered within the preset time period.
Preferably, in some possible implementations of the present application, the calling unit is specifically configured to initiate a blank detection if the feature element is triggered, where the blank detection is used to detect whether the information indicated by the target element is blank;
the calling unit is specifically configured to call the second page if the information indicated by the target element is not blank.
Preferably, in some possible implementations of the present application, the generating unit is specifically configured to save the first page if the user authentication is not passed;
The generation unit is specifically configured to associate the first page with the target button;
The generating unit is specifically configured to generate the target button in the display page.
Preferably, in some possible implementations of the present application, the generating unit is specifically configured to determine identification information of the first page, where the identification information is determined based on a feature element indicating operation information in the first page;
the generating unit is specifically configured to associate the target button with the identification information, and display a feature pixel on the target button, where the feature pixel corresponds to the identification information.
Preferably, in some possible implementations of the present application, the generating unit is specifically configured to traverse the input field in the second page if the user authentication is not passed;
The generating unit is specifically configured to save the input field and associate the input field with the first page if the input field reaches a preset length;
The generating unit is specifically configured to store the first page associated with the input field.
Preferably, in some possible implementations of the present application, the generating unit is further configured to display a third page, where the third page is used to indicate an association relationship between the target button and the first page;
The generating unit is further configured to cancel display of the third page if the feature element in the third interface is triggered.
A third aspect of the present application provides a computer apparatus comprising: a memory, a processor, and a bus system; the memory is used for storing program codes; the processor is configured to perform the method of page management of the first aspect or any of the first aspects according to instructions in the program code.
A fourth aspect of the application provides a computer readable storage medium having instructions stored therein which, when run on a computer, cause the computer to perform the method of page management of the first aspect or any of the first aspects above.
From the above technical solutions, the embodiment of the present application has the following advantages:
determining the current display page as a first page; when the feature element is triggered, a second page is called, wherein the second page is used for user authentication, and the second page and the first page are pages in a target flow; when the user authentication is not passed, generating a target button, wherein the target button is used for indicating the call of the target flow, the target button is positioned at the uppermost layer in the display page, and other elements in the display page can be operated by a user; and when the target button is triggered within a preset time period, calling the target flow to display a corresponding page. Because the first page can be switched to the background and can be associated through the convenient target button, the user clicks the target button to fill in the relevant page after searching the relevant real-name information, the filled content is ensured not to be lost, the convenience of the real-name authentication process is improved, and the user experience is improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present application, and that other drawings can be obtained according to the provided drawings without inventive effort for a person skilled in the art.
FIG. 1 is a diagram of a network architecture in which a page management system operates;
FIG. 2 is a flow diagram of page management;
FIG. 3 is a flowchart of a method for page management according to an embodiment of the present application;
FIG. 4 is a schematic view of a page management scenario according to an embodiment of the present application;
FIG. 5 is a flowchart of another method for page management according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a page management device according to an embodiment of the present application;
Fig. 7 is a schematic structural diagram of another page management apparatus according to an embodiment of the present application;
FIG. 8A is a schematic diagram of a data sharing system according to an embodiment of the present application;
FIG. 8B is a block diagram illustrating a data sharing system according to an embodiment of the present application;
fig. 8C is a schematic diagram of a data transmission response of a blockchain node according to an embodiment of the present application.
Detailed Description
The embodiment of the application provides a page management method and a related device, which can be applied to a transaction system or the operation process of a related transaction program, and particularly, the method and the related device can be used for determining that the current displayed page is a first page; when the feature element is triggered, a second page is called, wherein the second page is used for user authentication, and the second page and the first page are pages in a target flow; when the user authentication is not passed, generating a target button, wherein the target button is used for indicating the call of the target flow, the target button is positioned at the uppermost layer in the display page, and other elements in the display page can be operated by a user; and when the target button is triggered within a preset time period, calling the target flow to display a corresponding page. Because the first page can be switched to the background and can be associated through the convenient target button, the user clicks the target button to fill in the relevant page after searching the relevant real-name information, the filled content is ensured not to be lost, the convenience of the real-name authentication process is improved, and the user experience is improved.
The terms "first," "second," "third," "fourth" and the like in the description and in the claims and in the above drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the application described herein may be implemented, for example, in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "includes" and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or apparatus.
It should be understood that the page management method provided by the application can be applied to the operation process of the page management system, specifically, the page management system can be operated in a network architecture shown in fig. 1, as shown in fig. 1, which is a network architecture diagram operated by the page management system, as can be known in the figure, the page management system can provide page management with a plurality of information sources, and real-name authentication results can be obtained by collecting transaction information of different users and comparing the transaction information with characteristic information in a server, so as to ensure the transaction; it will be appreciated that, in fig. 1, there are a plurality of terminal devices interacted by a user, and in an actual scene, there may be more or less terminal devices participating in the transaction, and the specific number and types depend on the actual scene, which is not limited herein; in addition, one server is shown in fig. 1, but in an actual scenario, there may also be multiple servers involved, especially in a scenario of multi-information source interaction, the specific number of servers depends on the actual scenario.
It can be understood that the above-mentioned page management system can be run on a personal mobile terminal, can also run on a server, can also be used as a third party device to provide page management, so as to obtain the result of page management; the specific page management system may be in a program form, may also be operated as a system component in the device, and may also be used as a cloud service program, where a specific operation mode is determined according to an actual scenario, and is not limited herein.
Along with the development of mobile technology, more and more intelligent devices are in life of people, meanwhile, people increasingly start to use a mobile payment function, and in the payment process, real-name authentication is often required to ensure the safety of the payment process.
Generally, when a transaction page clicks to submit or purchase, a real-name authentication page is popped up, and a user can complete the next transaction operation after inputting corresponding information.
However, in some scenarios, the user may not remember the relevant real-name information, and cannot timely fill in the relevant information, and the user needs to log out of the payment page and then inquire, so that the user cannot timely and immediately process the payment page, and the information of the filled order is lost, so that convenience in the real-name authentication process is reduced, and user experience is affected.
In order to solve the above problems, the present application provides a method for managing a page, which is applied to a flow frame of page management shown in fig. 2, and is a flow frame diagram of page management shown in fig. 2, wherein the diagram shows a logic process of page management, firstly, page information is filled in, then real name authentication is performed, if authentication is completed, page hosting is performed, if not completed, the filled information is stored, then, after the user is ready, real name authentication is performed, and if authentication is passed, the operation of page submitting is continued.
It will be appreciated that the page may be an order, specifically, may be another page that interacts with the user, and the specific page form depends on the actual scenario and is not limited herein.
It can be understood that the method provided by the application can be a program writing method, which is used as a processing logic in a hardware system, and can also be used as a page management device, and the processing logic can be realized in an integrated or external mode. As one implementation, the page management device determines the currently displayed page as the first page; when the feature element is triggered, a second page is called, wherein the second page is used for user authentication, and the second page and the first page are pages in a target flow; when the user authentication is not passed, generating a target button, wherein the target button is used for indicating the call of the target flow, the target button is positioned at the uppermost layer in the display page, and other elements in the display page can be operated by a user; and when the target button is triggered within a preset time period, calling the target flow to display a corresponding page. Because the first page can be switched to the background and can be associated through the convenient target button, the user clicks the target button to fill in the relevant page after searching the relevant real-name information, the filled content is ensured not to be lost, the convenience of the real-name authentication process is improved, and the user experience is improved.
With reference to fig. 3, fig. 3 is a flowchart of a method for managing pages according to an embodiment of the present application, where the method includes at least the following steps:
301. And determining the current display page as a first page.
In this embodiment, the first page includes a plurality of feature elements that interact with the user, for example, if the first page is a transaction order page, the feature elements may be a real-name authentication button or a later authentication button, and a submit button for performing a next process, and further, the feature elements may also be other interface elements including transaction details, which is not limited herein.
302. And if the characteristic element is triggered, calling a second page.
In this embodiment, the second page is used for user authentication, and the second page and the first page are pages in the target flow.
It can be understood that, after the first page and the second page both complete the determination of the related logic, the next operation of the target flow may be performed, for example, in the transaction scenario, the first page may be an order page, the second page may be a real-name authentication page, and the target flow is an order submitting flow, and the order submitting flow may be performed only after the real-name authentication and the completion of the filling of the order, where the specific page form is determined by the actual scenario, and is not limited herein.
Optionally, for the completed part of the first page, blank detection may be implemented, that is, it is ensured that the relevant operation of the second page is performed after the information in the first page is filled. Specifically, if the feature element is triggered, blank detection is initiated, wherein the blank detection is used for detecting whether information indicated by a target element is blank or not; and if the information indicated by the target element is not blank, calling a second page.
303. And if the user authentication is not passed, generating a target button.
In this embodiment, the target button is used to indicate the call of the target flow, where the target button is located at the uppermost layer in the display page, and other elements in the display page may be operated by the user.
It can be understood that the target button can be round, square or other simple shapes, and is positioned at the uppermost layer of the displayed page to conveniently find and rapidly return to the previous page, so that the normal use of the terminal is ensured, and the normal operation of the target flow is ensured.
Optionally, before generating the target button, a prompt of closing first may be performed, that is, a third page is displayed, where the third page is used to indicate an association relationship between the target button and the first page; when the feature element in the third interface is triggered, canceling the display of the third page, for example: the third page is to indicate that the first page has been collapsed into the target button.
The process of packing up the first page can be understood as the association process of the first page and the target button, namely, if the user authentication is not passed, the first page is saved; associating the first page with the target button; and generating the target button in the display page.
Specifically, the association process of the first page and the target button can be determined by determining identification information of the first page, wherein the identification information is determined based on characteristic elements indicating operation information in the first page; and then, associating the target button with the identification information, and displaying characteristic pixels on the target button, wherein the characteristic pixels correspond to the identification information, for example, a target button with a larger pixel value is adopted for an order page, and a target button with a smaller pixel value is adopted for a general text page.
In one possible scenario, the user may fill in a part of the information, and may perform partial saving at this time, specifically, if the user authentication is not passed, traversing the input field in the second page; if the input field reaches the preset length, the input field is saved and is associated with the first page; the first page associated with the input field is saved.
304. And if the target button is triggered within a preset time period, invoking the target flow to display a corresponding page.
In this embodiment, the preset period of time may be a fixed period of time or until the user collects the related authentication information, and the page corresponding to the call target flow may be a first page or a second page.
Optionally, if part of the information is filled in the second page, displaying the second page so as to continuously fill in the authentication information; if the second page is not filled with information, the first page is displayed so as to facilitate the continuation of the target flow.
As can be seen from the above embodiments, the current display page is determined to be the first page; when the feature element is triggered, a second page is called, wherein the second page is used for user authentication, and the second page and the first page are pages in a target flow; when the user authentication is not passed, generating a target button, wherein the target button is used for indicating the call of the target flow, the target button is positioned at the uppermost layer in the display page, and other elements in the display page can be operated by a user; and when the target button is triggered within a preset time period, calling the target flow to display a corresponding page. Because the first page can be switched to the background and can be associated through the convenient target button, the user clicks the target button to fill in the relevant page after searching the relevant real-name information, the filled content is ensured not to be lost, the convenience of the real-name authentication process is improved, and the user experience is improved.
The following describes an embodiment of the present application with reference to a specific scenario, as shown in fig. 4, fig. 4 is a schematic view of a scenario of page management provided by the embodiment of the present application, in which a first page indicated in the figure is an order page, a feature element is an order submitting button, and after clicking the order submitting button, a second page, namely a real name authentication page, is popped up; if the user cannot fill in temporarily, clicking for later authentication; and at the moment, a third page is popped up, namely the user is reminded that the order is hosted, the target button is in a circular display form in the display interface, and when the target button is triggered again, the order page is popped up so as to facilitate the continuation of the transaction flow.
The above process may also be illustrated by a flowchart shown in fig. 5, where fig. 5 is a schematic flowchart of another page management provided in an embodiment of the present application, and the terminal device may determine according to the logic shown in fig. 5, and the related description is similar to that of fig. 4, and is not repeated herein.
Specifically, for the terminal equipment, the interaction process of the front end and the back end is included, namely when the finger clicks the button for submitting an order at the front end, the front end detects a clicking event of the button, a verification result of an incomplete real-name authentication field is read from the server end, and an interface of real-name authentication is displayed; when a user points to a later authentication button of the real name authentication interface, the front end detects a clicking event of the button, hides the real name authentication interface, and displays a suspension button of an unfinished order on a front page; when the hover button for an "unfinished" order is clicked, the front end detects a click event for the button, and re-reads the completed and unfinished order information data from the server. And redisplaying the order page so as to continuously complete unfinished order information filling and real-name authentication.
When a finger clicks an order submitting button, the back end of the terminal equipment performs field verification on order filling information data of a front end interface and verifies whether writing of all field data is completed or not, if the verification of a real-name authentication field is not completed, a result of the verification of the incomplete real-name authentication field is returned to the front end, and the front end makes real-name authentication interface display; after the user clicks the 'later authentication' on the front-end real-name authentication interface, the server receives the writing of the completed and unfinished order information data; after clicking the 'unfinished' order round suspension button on the front end interface, the server sends the finished and unfinished order information data to the front end to redisplay the order page, so that unfinished order information filling and real-name authentication are continuously finished.
Therefore, through interaction between the front end and the rear end of the terminal equipment and switching of related pages, normal operation of a target flow is guaranteed, a real-name authentication process is enabled to be more convenient, and user experience is improved.
In order to better implement the above-described aspects of the embodiments of the present application, the following provides related apparatuses for implementing the above-described aspects. Referring to fig. 6, fig. 6 is a schematic structural diagram of a page management device according to an embodiment of the present application, and a page management device 600 includes:
A determining unit 601, configured to determine a current display page as a first page, where the first page includes a plurality of feature elements that interact with a user;
A calling unit 602, configured to call a second page if the feature element is triggered, where the second page is used to perform user authentication, and the second page and the first page are pages in a target flow;
A generating unit 603, configured to generate a target button if the user authentication does not pass, where the target button is used to indicate the invocation of the target procedure, the target button is located at the uppermost layer in the display page, and other elements in the display page can be operated by the user;
And the triggering unit 604 is configured to invoke the target procedure to display a corresponding page if the target button is triggered within a preset time period.
Preferably, in some possible implementations of the present application, the calling unit 602 is specifically configured to initiate a blank detection if the feature element is triggered, where the blank detection is used to detect whether the information indicated by the target element is blank;
The calling unit 602 is specifically configured to call the second page if the information indicated by the target element is not blank.
Preferably, in some possible implementations of the present application, the generating unit 603 is specifically configured to save the first page if the user authentication is not passed;
The generating unit 603 is specifically configured to associate the first page with the target button;
the generating unit 603 is specifically configured to generate the target button in the display page.
Preferably, in some possible implementations of the present application, the generating unit 603 is specifically configured to determine identification information of the first page, where the identification information is determined based on a feature element indicating operation information in the first page;
The generating unit 603 is specifically configured to associate the target button with the identification information, and display a feature pixel on the target button, where the feature pixel corresponds to the identification information.
Preferably, in some possible implementations of the present application, the generating unit 603 is specifically configured to traverse the input field in the second page if the user authentication is not passed;
The generating unit 603 is specifically configured to save the input field and associate the input field with the first page if the input field reaches a preset length;
the generating unit 603 is specifically configured to store the first page associated with an input field.
Preferably, in some possible implementations of the present application, the generating unit 603 is further configured to display a third page, where the third page is used to indicate an association relationship between the target button and the first page;
the generating unit 603 is further configured to cancel display of the third page if a feature element in the third interface is triggered.
Determining the current display page as a first page; when the feature element is triggered, a second page is called, wherein the second page is used for user authentication, and the second page and the first page are pages in a target flow; when the user authentication is not passed, generating a target button, wherein the target button is used for indicating the call of the target flow, the target button is positioned at the uppermost layer in the display page, and other elements in the display page can be operated by a user; and when the target button is triggered within a preset time period, calling the target flow to display a corresponding page. Because the first page can be switched to the background and can be associated through the convenient target button, the user clicks the target button to fill in the relevant page after searching the relevant real-name information, the filled content is ensured not to be lost, the convenience of the real-name authentication process is improved, and the user experience is improved.
Referring to fig. 7, fig. 7 is a schematic structural diagram of another page management apparatus according to an embodiment of the present application, where the page management apparatus 700 may have a relatively large difference due to different configurations or performances, and may include one or more central processing units (central processing units, CPU) 722 (e.g., one or more processors) and a memory 732, and one or more storage mediums 730 (e.g., one or more mass storage devices) storing application programs 742 or data 744. Wherein memory 732 and storage medium 730 may be transitory or persistent. The program stored in the storage medium 730 may include one or more modules (not shown), each of which may include a series of instruction operations in the page management device. Still further, the central processor 722 may be configured to communicate with the storage medium 730 and execute a series of instruction operations in the storage medium 730 on the page management device 700.
The page management device 700 may also include one or more power supplies 726, one or more wired or wireless network interfaces 750, one or more input/output interfaces 758, and/or one or more operating systems 741, such as Windows Server, mac OS XTM, unixTM, linuxTM, freeBSDTM, and the like.
The steps performed by the page management apparatus in the above-described embodiments may be based on the page management apparatus structure shown in fig. 6.
Embodiments of the present application also provide a computer readable storage medium having stored therein page management instructions that, when executed on a computer, cause the computer to perform the steps performed by the page management apparatus in the method described in the embodiments of fig. 2 to 5.
There is also provided in an embodiment of the application a computer program product comprising page management instructions which, when run on a computer, cause the computer to perform the steps performed by the page management apparatus in the method described in the embodiments of figures 2 to 5, as described above.
The embodiment of the application also provides a page management system, which can comprise the page management device in the embodiment shown in fig. 6 or the page management device shown in fig. 7.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.
In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in whole or in part in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a page management apparatus, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
In addition, the method and apparatus for page management described above may also be applied to a data sharing system, see the data sharing system shown in fig. 8A, where the data sharing system 800 refers to a system for performing data sharing between nodes, where the data sharing system may include multiple nodes 801, and the multiple nodes 801 may be respective clients in the data sharing system, where each client runs on a terminal device corresponding to the method according to the present application. Each node 801 may receive input information during normal operation and maintain shared data within the data sharing system based on the received input information. In order to ensure the information intercommunication in the data sharing system, information connection can exist between each node in the data sharing system, and the nodes can transmit information through the information connection. For example, when any node in the data sharing system receives input information, other nodes in the data sharing system acquire the input information according to a consensus algorithm, and store the input information as data in the shared data, so that the data stored on all nodes in the data sharing system are consistent.
Each node in the data sharing system has a node identifier corresponding to the node identifier, and each node in the data sharing system can store the node identifiers of other nodes in the data sharing system, so that the generated block can be broadcast to other nodes in the data sharing system according to the node identifiers of other nodes. Each node can maintain a node identification list shown in the following table, and the node names and the node identifications are correspondingly stored in the node identification list. The node identifier may be an IP (Internet Protocol, protocol interconnected between networks) address and any other information that can be used to identify the node, and the IP address is only illustrated in table 1.
Table 1 correspondence between nodes and node identifiers
| Node name | Node identification |
| Node 1 | 117.114.151.174 |
| Node 2 | 117.116.189.145 |
| … | … |
| Node N | 119.123.789.258 |
Each node in the data sharing system stores one and the same blockchain. The blockchain is composed of a plurality of blocks, referring to fig. 8B, the blockchain is composed of a plurality of blocks, the starting block comprises a block header and a block main body, the block header stores an input information characteristic value, a version number, a time stamp and a difficulty value, and the block main body stores input information; the next block of the starting block takes the starting block as a father block, the next block also comprises a block head and a block main body, the block head stores the input information characteristic value of the current block, the block head characteristic value of the father block, the version number, the timestamp and the difficulty value, and the like, so that the block data stored in each block in the block chain are associated with the block data stored in the father block, and the safety of the input information in the block is ensured.
When each block in the blockchain is generated, referring to fig. 8C, when the node where the blockchain is located receives the input information, checking the input information, storing the input information into the memory pool after the checking is completed, and updating the hash tree used for recording the input information; then, updating the update time stamp to the time of receiving the input information, trying different random numbers, and calculating the characteristic value for a plurality of times, so that the calculated characteristic value can meet the following formula:
SHA256(SHA256(version+prev_hash+merkle_root+ntime+nbits+x))<TARGET
Wherein SHA256 is a eigenvalue algorithm used to calculate eigenvalues; version (version number) is version information of the related block protocol in the block chain; the prev_hash is the block header characteristic value of the parent block of the current block; merkle _root is a characteristic value of input information; ntime is the update time of the update timestamp; the nbits is the current difficulty, is a fixed value in a period of time, and is determined again after exceeding a fixed period of time; x is a random number; TARGET is a eigenvalue threshold that can be determined from nbits.
Thus, when the random number meeting the formula is calculated, the information can be correspondingly stored to generate the block head and the block main body, and the current block is obtained. And then, the node where the blockchain is located sends the newly generated blocks to other nodes in the data sharing system where the newly generated blocks are located according to the node identification of other nodes in the data sharing system, the other nodes verify the newly generated blocks, and the newly generated blocks are added into the blockchain stored in the newly generated blocks after the verification is completed.
The above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application.
Claims (16)
1. A method for page management in a terminal device, comprising:
determining a current display page as a first page, wherein the first page comprises a plurality of characteristic elements interacted with by a user;
If the feature element is triggered, a second page is called, wherein the second page is used for user authentication, and the second page and the first page are pages in a target flow;
if the user authentication is not passed, generating a target button, wherein the target button is used for indicating the call of the target flow, the target button is positioned at the uppermost layer in the display page, and other elements in the display page can be operated by a user;
and if the target button is triggered within a preset time period, invoking the target flow to display a corresponding page.
2. The method of claim 1, wherein invoking the second page if the feature element is triggered comprises:
if the characteristic element is triggered, initiating blank detection, wherein the blank detection is used for detecting whether information indicated by a target element is blank or not;
and if the information indicated by the target element is not blank, calling a second page.
3. The method of claim 1, wherein generating the target button if the user authentication is not passed comprises:
if the user authentication is not passed, the first page is saved;
Associating the first page with the target button;
And generating the target button in the display page.
4. The method of claim 3, wherein the associating the first page with the target button comprises:
Determining identification information of the first page, wherein the identification information is determined based on characteristic elements indicating operation information in the first page;
And associating the target button with the identification information, and displaying characteristic pixels on the target button, wherein the characteristic pixels correspond to the identification information.
5. The method of claim 3, wherein the saving the first page if the user authentication is not passed comprises:
If the user authentication is not passed, traversing the input field in the second page;
if the input field reaches the preset length, the input field is saved and is associated with the first page;
the first page associated with the input field is saved.
6. The method of any one of claims 1-5, wherein prior to the generating the target button, the method further comprises:
Displaying a third page, wherein the third page is used for indicating the association relation between the target button and the first page;
And if the characteristic elements in the third page are triggered, canceling the display of the third page.
7. The method of claim 1, wherein the method of page management is applied to a terminal device, the terminal device being a block node device in a block chain node.
8. A page management apparatus in a terminal device, comprising:
The determining unit is used for determining the current display page as a first page, wherein the first page comprises a plurality of characteristic elements interacted with by a user;
the calling unit is used for calling a second page if the characteristic element is triggered, the second page is used for user authentication, and the second page and the first page are pages in a target flow;
The generating unit is used for generating a target button if the user authentication is not passed, wherein the target button is used for indicating the call of the target flow, the target button is positioned at the uppermost layer in the display page, and other elements in the display page can be operated by a user;
And the triggering unit is used for calling the target flow to display the corresponding page if the target button is triggered within the preset time period.
9. The apparatus according to claim 8, wherein the calling unit is specifically configured to:
if the characteristic element is triggered, initiating blank detection, wherein the blank detection is used for detecting whether information indicated by a target element is blank or not;
and if the information indicated by the target element is not blank, calling a second page.
10. The apparatus according to claim 8, wherein the generating unit is specifically configured to:
if the user authentication is not passed, the first page is saved;
Associating the first page with the target button;
And generating the target button in the display page.
11. The apparatus according to claim 10, wherein the generating unit is specifically configured to:
Determining identification information of the first page, wherein the identification information is determined based on characteristic elements indicating operation information in the first page;
And associating the target button with the identification information, and displaying characteristic pixels on the target button, wherein the characteristic pixels correspond to the identification information.
12. The apparatus according to claim 10, wherein the generating unit is specifically configured to:
If the user authentication is not passed, traversing the input field in the second page;
if the input field reaches the preset length, the input field is saved and is associated with the first page;
the first page associated with the input field is saved.
13. The apparatus according to any one of claims 8-12, wherein the generating unit is further configured to:
Displaying a third page, wherein the third page is used for indicating the association relation between the target button and the first page;
And if the characteristic elements in the third page are triggered, canceling the display of the third page.
14. A computer device, the computer device comprising a processor and a memory:
The memory is used for storing program codes; the processor is configured to perform the method of page management in a terminal device according to any of claims 1 to 7 according to instructions in the program code.
15. A computer readable storage medium having instructions stored therein which, when run on a computer, cause the computer to perform the method of page management in a terminal device according to any of the preceding claims 1 to 7.
16. A computer program product, characterized in that the computer program product comprises page management instructions which, when run on a computer, cause the computer to perform the method of page management in a terminal device according to any of the preceding claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911012970.2A CN110750322B (en) | 2019-10-23 | 2019-10-23 | Page management method in terminal equipment and related device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911012970.2A CN110750322B (en) | 2019-10-23 | 2019-10-23 | Page management method in terminal equipment and related device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110750322A CN110750322A (en) | 2020-02-04 |
| CN110750322B true CN110750322B (en) | 2024-04-26 |
Family
ID=69279586
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911012970.2A Active CN110750322B (en) | 2019-10-23 | 2019-10-23 | Page management method in terminal equipment and related device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110750322B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104267893A (en) * | 2014-09-30 | 2015-01-07 | 珠海市君天电子科技有限公司 | Floating-window pushing adjusting method and device |
| CN106228353A (en) * | 2016-07-21 | 2016-12-14 | 北京三快在线科技有限公司 | A kind of method for processing payment information, device and system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140101045A1 (en) * | 2012-10-09 | 2014-04-10 | Bank Of America Corporation | Payment Action Page Queue for a Mobile Device |
-
2019
- 2019-10-23 CN CN201911012970.2A patent/CN110750322B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104267893A (en) * | 2014-09-30 | 2015-01-07 | 珠海市君天电子科技有限公司 | Floating-window pushing adjusting method and device |
| CN106228353A (en) * | 2016-07-21 | 2016-12-14 | 北京三快在线科技有限公司 | A kind of method for processing payment information, device and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110750322A (en) | 2020-02-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10348809B2 (en) | Naming of distributed business transactions | |
| US10097623B2 (en) | Method and device for displaying information flows in social network, and server | |
| US8838679B2 (en) | Providing state service for online application users | |
| US20160337462A1 (en) | Method and system for pushing web application message | |
| TWI615792B (en) | Session content combining method and system | |
| US9736225B2 (en) | Information processing method, and priority information sending method and device | |
| CN107592237B (en) | Resource monitoring method and system of hybrid cloud | |
| US10873640B2 (en) | Information exchange method and server | |
| CN111400482B (en) | Method and device for establishing question-answer pairs | |
| CN113807538A (en) | Federal learning method and device, electronic equipment and storage medium | |
| US20170017527A1 (en) | Contention and selection of controlling work coordinator in a distributed computing environment | |
| US20130347004A1 (en) | Correlating messages | |
| US10997569B2 (en) | Method and device for processing virtual cards | |
| WO2015065852A2 (en) | User information classification method and apparatus, and user group information acquistion method and apparatus | |
| CN107357890A (en) | A kind of web page files processing method, apparatus and system and storage device | |
| WO2017041681A1 (en) | Method and terminal for acquiring and presenting information | |
| CN114328132A (en) | Method, device, equipment and medium for monitoring state of external data source | |
| WO2022111169A1 (en) | User identity identification method, computing device and computer storage medium | |
| CN107517188A (en) | A kind of data processing method and device based on Android system | |
| CN110750322B (en) | Page management method in terminal equipment and related device | |
| CN107220818B (en) | Online payment method and device | |
| US20150288770A1 (en) | System and Computer Implemented Method of Personal Monitoring | |
| CN111047362A (en) | Statistical management method and system for use activity of intelligent sound box | |
| CN110119334B (en) | Page script monitoring method and device | |
| CN114331446B (en) | Method, device, equipment and medium for realizing out-of-chain service of block chain |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40021057 Country of ref document: HK |
|
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |