Display method and device for data query of mobile terminal

Abstract

The invention discloses a display method and device for data query of a mobile terminal, relates to the technical field of data query and financial science and technology, and mainly aims to solve the problem of poor display effect of existing data query of the mobile terminal. Comprising the following steps: acquiring node data obtained by acquiring data at different data levels in a mobile terminal; and calling at least one page component matched with the real-time data hierarchy, and outputting the page component in a front-end interface of the mobile terminal, the page component being created based on the node data and / or the data hierarchy meeting a preset query condition. The preset query condition is used for representing constraint information for performing jump query on the data hierarchy; and when it is detected that the page component is triggered, displaying target data bound with the page component.

Description

Technical Field

[0001] The present invention relates to the technical fields of data query and fintech, and particularly to a method and device for displaying mobile terminal data query. Background Art

[0002] With the rapid development of big data technology, it has become a very common technical means to obtain data and use data modeling to solve corresponding problems. For example, users can record and query the processing status of business data, transaction data, and payment data processed by various financial application programs installed on mobile devices through technologies such as big data.

[0003] Currently, in the mobile terminal, data is usually directly retrieved and viewed using visualization components. However, since the data dashboard of the visualization component drills down layer by layer according to the data organization structure to screen target data, the operation is cumbersome, the data query takes a lot of time, and the purpose of effective rollback cannot be achieved, thus greatly reducing the display effect of mobile terminal data query. Summary of the Invention

[0004] In view of this, the present invention provides a method and device for displaying mobile terminal data query, mainly aiming to solve the problem of poor display effect of existing mobile terminal data query.

[0005] According to one aspect of the present invention, there is provided a method for displaying mobile terminal data query, including:

[0006] Obtaining node data obtained by acquiring data at different data levels in the mobile terminal;

[0007] Invoking at least one page component matching the real-time data level and outputting the page component in the front-end interface of the mobile terminal, where the page component is created based on node data and / or data levels that meet preset query conditions, and the preset query conditions are used to represent constraint information for jump query of data levels;

[0008] When it is detected that the page component is triggered, displaying the target data bound to the page component.

[0009] Further, before invoking at least one page component matching the real-time data level, the method further includes:

[0010] Analyzing the constraint level and constraint data in the preset query conditions;

[0011] When the constraint level exists in the data level, and / or the constraint data exists in the node data, invoking a component generator;

[0012] Generate a first page component that matches the constraint hierarchy based on the component generator, and / or generate a second page component that matches the constraint data based on the component generator.

[0013] Further, outputting the page component in the front-end interface of the mobile device includes:

[0014] Determine the component display area of the front-end interface based on the data volume and data display method in the real-time data hierarchy, where the data display method includes list display, image display, and text display;

[0015] Determine the triggering method of the first page component and / or the second page component according to the area size and area position of the component display area, and output the first page component and / or the second page component in the front-end interface according to the triggering method.

[0016] Further, obtaining the node data obtained by obtaining data at different data levels in the mobile device includes:

[0017] Real-time record the node data generated when accessing each data level, and construct a tree-level structure of the nodes according to the data level;

[0018] Mark a tree identifier for the node data according to the tree-level structure, and create a cache space that matches the tree-level structure;

[0019] Store the node data with the tree identifier into the corresponding cache space respectively.

[0020] Further, generating a first page component that matches the constraint hierarchy based on the component generator includes:

[0021] Detect whether the data level increases;

[0022] If the data level increases, update the increased data level based on the constraint hierarchy, and generate a first page component that matches the updated data level based on the component generator;

[0023] Among them, the constraint hierarchy includes at least one of a home page hierarchy, an end page hierarchy, an intermediate page hierarchy, and a fixed page hierarchy.

[0024] Further, generating a second page component that matches the constraint data based on the component generator includes:

[0025] Detect whether the node data increases or decreases;

[0026] If the node data increases, update the increased node data based on the constraint data, and generate a second page component that matches the updated constraint data based on the component generator;

[0027] If the node data decreases, update the decreased node data based on the constraint data, and generate a second page component that matches the updated constraint data based on the component generator;

[0028] Among them, the constraint data includes at least one of a constraint value, a constraint unit, and constraint text.

[0029] Further, the method further includes:

[0030] Output a configuration box for the preset query condition to indicate input configuration of the constraint level and / or constraint data in the configuration box;

[0031] Update the preset query condition based on the constraint level and / or constraint data input in the configuration box.

[0032] According to another aspect of the present invention, there is provided a display device for mobile data query, including:

[0033] An acquisition module, configured to acquire node data obtained by acquiring data at different data levels in a mobile device;

[0034] An invocation module, configured to invoke at least one page component that matches the real-time data level, and output the page component in the front-end interface of the mobile device, where the page component is created based on node data and / or data levels that meet a preset query condition, and the preset query condition is used to represent constraint information for jump query of data levels;

[0035] A display module, configured to display target data bound to the page component when it is detected that the page component is triggered.

[0036] Further, the device further includes: a parsing module, a generating module,

[0037] The parsing module is further configured to parse the constraint level and constraint data in the preset query condition;

[0038] The invocation module is configured to invoke a component generator when the constraint level exists in the data level and / or the constraint data exists in the node data;

[0039] The generating module is configured to generate a first page component that matches the constraint level based on the component generator, and / or generate a second page component that matches the constraint data based on the component generator.

[0040] Further,

[0041] The retrieval module is specifically configured to determine the component display area of the front-end interface based on the data volume and data display mode in the real-time data hierarchy, where the data display mode includes list display, image display, and text display; determine the triggering method of the first page component and / or the second page component according to the area size and area position of the component display area, and output the first page component and / or the second page component in the front-end interface according to the triggering method.

[0042] Further, the acquisition module is specifically configured to record in real time the node data generated when accessing each data hierarchy, and construct a tree-level hierarchy structure of the nodes according to the data hierarchy; mark a tree identifier for the node data according to the tree-level hierarchy structure, and create a cache space matching the tree-level hierarchy structure; store the node data with the tree identifier into the corresponding cache space respectively.

[0043] Further, the generation module is specifically configured to detect whether the data hierarchy increases; if the data hierarchy increases, update the increased data hierarchy based on the constraint hierarchy, and generate a first page component matching the updated data hierarchy based on the component generator; where the constraint hierarchy includes at least one of a home page hierarchy, an end page hierarchy, an intermediate page hierarchy, and a fixed page hierarchy.

[0044] Further, the generation module is specifically further configured to detect whether the node data increases or decreases; if the node data increases, update the increased node data based on the constraint data, and generate a second page component matching the updated constraint data based on the component generator; if the node data decreases, update the decreased node data based on the constraint data, and generate a second page component matching the updated constraint data based on the component generator; where the constraint data includes at least one of a constraint value, a constraint unit, and a constraint text.

[0045] Further, the output module is further configured to output a configuration box for the preset query condition to indicate the input configuration of the constraint hierarchy and / or the constraint data in the configuration box; update the preset query condition based on the constraint hierarchy and / or the constraint data input in the configuration box.

[0046] According to another aspect of the present invention, there is provided a computer-readable storage medium, in which at least one executable instruction is stored, and the executable instruction causes a processor to perform operations corresponding to the above-described mobile terminal data query display method.

[0047] According to another aspect of the present invention, there is provided a computer device, including: a processor, a memory, a communication interface, and a communication bus, and the processor, the memory, and the communication interface complete communication with each other through the communication bus;

[0048] The memory is used to store at least one executable instruction, and the executable instruction causes the processor to execute the operations corresponding to the above-mentioned method for displaying mobile terminal data query.

[0049] By means of the above technical solutions, the technical solutions provided by the embodiments of the present invention have at least the following advantages:

[0050] The present invention provides a method and device for displaying mobile terminal data query. Compared with the prior art, in the embodiments of the present invention, node data obtained by obtaining data at different data levels in the mobile terminal is acquired; at least one page component matching the real-time data level is retrieved, and the page component is output in the front-end interface of the mobile terminal. The page component is created based on the node data and / or data level that meet the preset query conditions, and the preset query conditions are used to represent the constraint information for jump query of the data level; when it is detected that the page component is triggered, the target data bound to the page component is displayed, achieving the purpose of quickly querying the data of the component dashboard, reducing the data redrawing time, meeting the user's flexible page back custom requirements, and thus improving the query and display efficiency of mobile terminal data.

[0051] The above description is only an overview of the technical solutions of the present invention. In order to be able to understand the technical means of the present invention more clearly, it can be implemented according to the content of the specification. And in order to make the above and other purposes, features, and advantages of the present invention more obvious and understandable, the following specifically describes the embodiments of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] By reading the following detailed description of the preferred embodiments, various other advantages and benefits will become clear to those of ordinary skill in the art. The drawings are only for the purpose of showing the preferred embodiments and are not considered to be a limitation of the present invention. Moreover, throughout the drawings, the same reference numerals are used to represent the same components. In the drawings:

[0053] Figure 1 Shows a flowchart of a method for displaying mobile terminal data query provided by an embodiment of the present invention;

[0054] Figure 2 Shows a schematic diagram of a page area provided by an embodiment of the present invention;

[0055] Figure 3 Shows a block diagram of a device for displaying mobile terminal data query provided by an embodiment of the present invention;

[0056] Figure 4 The figure shows a schematic structural diagram of a computer device provided by an embodiment of the present invention. Detailed implementation manners

[0057] Hereinafter, exemplary embodiments of the present disclosure will be described in more detail with reference to the accompanying drawings. Although the exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided so that the present disclosure can be more thoroughly understood and the scope of the present disclosure can be fully conveyed to those skilled in the art.

[0058] It should be noted that in the description of the embodiments of the present invention, for the following defined terms, unless otherwise defined in the claims or elsewhere in this specification, these definitions shall apply. All numerical values, whether explicitly indicated or not, are hereby defined as being modified by the term "about". The term "about" generally refers to a numerical range that a person of ordinary skill in the art would consider equivalent to the stated value to produce substantially the same properties, functions, results, etc. A numerical range indicated by a low value and a high value is defined as including all the numerical values included in the numerical range and all sub-ranges included in the numerical range.

[0059] It should be noted that in the description of the embodiments of the present invention, the terms "first", "second", etc. in the specification, claims and drawings are used to distinguish similar objects and do not necessarily have to be used to describe a specific order or sequence. It should be understood that such objects can be interchanged under appropriate circumstances so that the embodiments of the embodiments of the present invention can be implemented in an order other than the following illustration or description. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, or products.

[0060] In one embodiment, the embodiments of the present invention provide a method for displaying mobile terminal data query. Taking the method applied to a computer device such as a server as an example for description, where the server can be an independent server or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, Content Delivery Network (CDN), and big data and artificial intelligence platforms, such as financial trading platforms, financial information management systems, etc.

[0061] An embodiment of the present invention provides a method for displaying mobile - end data query, as follows Figure 1 shown, the method includes:

[0062] 101. Obtain node data obtained by acquiring data at different data levels in the mobile end.

[0063] In an embodiment of the present invention, the mobile end is a client installed with a specific financial application program, including but not limited to mobile phones, tablets. The specific financial application program includes but not limited to applications such as [company A] Financial Butler, [company A] One Account, etc. At this time, as the execution subject of the method for displaying mobile - data query, it is the current mobile terminal. Therefore, first, obtain the node data obtained by the user acquiring data at each data level in the application program of the current mobile end. Among them, the data level is the number of layers of the page entered or clicked by the user for accessing the financial application program, and the node data is the data to be displayed on the page when clicking or entering this page, that is, the data generated by accessing the page, including but not limited to text data, image data, link data, chart data, and so on.

[0064] It should be noted that since multiple page levels can be accessed by different financial application programs, when obtaining data nodes, all node data generated by the user accessing different data levels can be recorded first, so as to generate matching page components and achieve the purpose of quick back - off.

[0065] 102. Invoke at least one page component matching the real - time data level and output the page component in the front - end interface of the mobile end.

[0066] In an embodiment of the present invention, after obtaining the foregoing node data, when the current execution entity retrieves the real-time data level that the user is currently browsing, this real-time data level can be the last accessed data level or the data level after a single step back. The embodiments of the present invention do not make specific limitations. Among them, when determining the real-time data level, the current execution end retrieves the page component that matches it. At this time, the page component is created based on the node data and / or data level that meet the preset query conditions. That is, the preset query conditions are used to represent the constraint information for jumping and querying the data level, including constraint data and constraint levels. The constraint data is the data that must exist in the jumping or stepping-back page. For example, the constraint data can include specific texts such as "total value" and "installment". The constraint level is the level that the jumping or stepping-back page must correspond to. For example, the constraint level can include the first page, the middle page, the last page, etc. The embodiments of the present invention do not make specific limitations. In addition, the page component in the embodiments of the present invention is a highly adaptable trigger button (the specific form of the button is not limited) generated by a component generator for jumping to the corresponding page, so as to link to the corresponding data level. The component generator can be a Vue component generator, generating the first page component or the second page component respectively. At this time, the first page component matches the constraint level, and the second page component matches the constraint data, so as to display the data of the corresponding data level.

[0067] It should be noted that after the current execution end retrieves the pre-configured page component that matches the real-time data level, in order to facilitate the user to trigger the jump, this page component is output in the front-end interface of the mobile device. At this time, a display area is pre-assigned to the page component in the front-end interface for the user to click flexibly.

[0068] 103. When it is detected that the page component is triggered, display the target data bound to the page component.

[0069] In an embodiment of the present invention, when the user selects the corresponding page component in the front-end interface to trigger it, such as clicking the page component, after it is detected that the page component is triggered, the current execution end can retrieve the target data bound to this page component. At this time, the target data is the node data that the page component can step back to. For example, display the chart data of the specified page. The embodiments of the present invention do not make specific limitations.

[0070] In addition, since the display form of the page component is diversified, for example, it can be a button or a link bar in the form of a drop-down box, etc., for the user to click and trigger.

[0071] It should be noted that when the current execution end displays the target data, in order to meet the display requirements on the chart interface, it is also possible to embed a page component on the basis of the Echarts graphic component. That is, when the user queries the data chart in the Echarts graphic component, each time a chart is formed after statistics, it can be saved as a data level so that the user can perform backward or jump operations at any time based on the page component constructed by the data level. At the same time, since the current execution end is a real-time call of the page component in the mobile terminal, it avoids the lag situation of reloading the page from the server, and greatly improves the efficiency of page backward.

[0072] In the embodiment of the present invention, the Echarts graphic component can generate images such as line charts, bar charts, pie charts, multi-bar charts, Sankey diagrams, word cloud diagrams, gradient bar charts, stacked bar charts, multi-column charts, and segmented color line charts.

[0073] The embodiment of the present invention provides a method for displaying mobile terminal data query. By obtaining node data obtained by obtaining data at different data levels in the mobile terminal; calling at least one page component matching the real-time data level, and outputting the page component in the front-end interface of the mobile terminal, the page component is created based on node data and / or data levels that meet preset query conditions, and the preset query conditions are used to represent constraint information for jump query of data levels; when it is detected that the page component is triggered, the target data bound to the page component is displayed, achieving the purpose of quickly querying data on the component dashboard, reducing the data redrawing time, meeting the user's flexible page backward customization requirements, and thus improving the query and display efficiency of mobile terminal data.

[0074] In another embodiment of the present invention, for further limitation and explanation, before the step of calling at least one page component matching the real-time data level, the method further includes:

[0075] Analyzing the constraint level and constraint data in the preset query condition;

[0076] When the constraint level exists in the data level, and / or the constraint data exists in the node data, then call the component generator;

[0077] Generating a first page component matching the constraint level based on the component generator, and / or generating a second page component matching the constraint data based on the component generator.

[0078] To make the page rollback targeted and flexible, and to make the components more adaptable to mobile devices, the current execution end first parses the constraint level and constraint data in the configured preset query conditions. Among them, the constraint data is the data that must exist in the page for limited jump or rollback. For example, the constraint data may include specific texts such as "total value" and "installment". The constraint level is the level that the page for limited jump or rollback must correspond to. For example, the constraint level may include the first page, the middle page, the last page, etc. The embodiments of the present invention do not make specific limitations. Furthermore, the current execution end first determines whether there is a constraint level in each data level accessed by the user, or it can also simultaneously determine whether there is constraint data in the node data of the page of the accessed data level. When there is a constraint level or constraint data, the current execution end invokes the component generator. The component generator can be a Vue component generator, which generates a first page component or a second page component respectively. At this time, the first page component matches the constraint level, and the second page component matches the constraint data. For example, the first page component is a home page rollback component, a last page jump component, etc., and the second page component is a total target page jump component, a block diagram page jump component, etc. The embodiments of the present invention do not make specific limitations.

[0079] It should be noted that the display form of the page component in the embodiments of the present invention can be a button or a link bar in the form of a dropdown box, etc., for the user to click and trigger. The embodiments of the present invention do not make specific limitations. In addition, when generating a page component based on the component generator, the specific appearance of the component for matching the constraint level and constraint data can be preset, including but not limited to the size, number, color, name, etc. of the button, so as to invoke the page generator to generate the corresponding first page component and second page component.

[0080] In another embodiment of the present invention, for further limitation and explanation, the step of outputting the page component in the front-end interface of the mobile device includes:

[0081] Determine the component display area of the front-end interface based on the data volume and data display method in the real-time data level;

[0082] Determine the triggering method of the first page component and / or the second page component according to the area size and area position of the component display area, and output the first page component and / or the second page component in the front-end interface according to the triggering method.

[0083] To achieve a more effective visualization effect of page components, when generating the first page component and the second page component, and when the user accesses real-time hierarchical data, first determine the data volume and data display method in the real-time hierarchical data. Among them, the data volume is the data size displayed on the page of the real-time hierarchical data, including but not limited to text data volume, number of pictures, etc., and the data display methods include list display, image display, and text display. At this time, the data volume and data display method can be determined when the page corresponding to each real-time data level is constructed, so as to determine the component display area of the front-end interface based on the obtained data volume and data display method. Specifically, the current execution end can pre-construct the mapping relationship of the component display area corresponding to different data volumes and different data display methods. For example, when the data volume is within the range of a-b and the data display method is text display, the corresponding component display area is interface display area 1. The embodiments of the present invention do not make specific limitations. At this time, when configuring the front-end interface, multiple interface display areas can be reserved, and in each area as shown in Figure 2 , including the pre-set area size, area position, etc., for subsequent flexible selection and configuration. The embodiments of the present invention do not make specific limitations.

[0084] It should be noted that after determining the component display area, determine the triggering method of the first page component and / or the second page component according to the area size and area position of the determined component display area. At this time, the triggering method is any one of the triggering buttons, triggering links, triggering dropdown boxes, etc. configured for the data display method, so as to output the first page component and / or the second page component on the front-end interface according to the triggering method. For example, if the area size of the determined component display area accounts for one-twentieth of the front-end interface and the data display method is text display, the matching triggering method can be a dropdown box, and multiple text options can be set in the dropdown box. The user can select the page to go back or jump through the dropdown box. The embodiments of the present invention do not make specific limitations.

[0085] In another embodiment of the present invention, for further limitation and explanation, the steps of obtaining the node data obtained by obtaining data at different data levels in the mobile terminal include:

[0086] Real-time record the node data generated when accessing each data level, and construct the tree-level structure of the nodes according to the data level;

[0087] Mark the tree identifier for the node data according to the tree-level structure, and create a cache space matching the tree-level structure;

[0088] Store the node data with the tree identifier into the corresponding cache space respectively.

[0089] In order to accurately and quickly achieve the purpose of backtracking or jumping, avoid complicating the operation of page backtracking, and at the same time, avoid the lag caused by reloading the page from the server. When the current execution end obtains node data, it first records in real time the node data generated by the user when accessing each data level. For example, it records all the node data generated when the user clicks to enter the home page, the second page, and finally the payment page when accessing the application. The embodiments of the present invention do not make specific limitations. At the same time, since different lower-level data levels can be accessed from one data level, the current execution end constructs a tree-level structure according to each accessed data level. At the same time, tree marking is performed on the node data obtained and accessed in the tree-level structure, and the marking content may include the upper-level page identifier, the current-level page identifier, and the connected lower-level page identifier, so as to serve as a retrieval basis for querying node data.

[0090] It should be noted that since the current execution end is a mobile device, in order to ensure compatibility and fluency, before generating page components using the VUE framework, the current execution end can also create a cache space that matches the tree-level structure to temporarily cache node data, facilitating quick page backtracking and jumping, and thus storing the node data with tree identifiers into the corresponding cache spaces respectively. The embodiments of the present invention do not make specific limitations.

[0091] In another embodiment of the present invention, for further limitation and explanation, the step of generating a first page component that matches the constraint level based on the component generator includes:

[0092] Detect whether the data level increases;

[0093] If the data level increases, update the increased data level based on the constraint level, and generate a first page component that matches the updated data level based on the component generator.

[0094] For the purpose of improving the precise processing of page back or jump and avoiding the solidification and redundancy of the content of the back page, when the current execution end generates the first page component based on the constraint level, it first determines whether all the data levels accessed by the user have changed, that is, determines whether the data level has increased. For example, when the user originally accessed the application and entered a page with 5 data levels and browsed on the 5th level page, the mobile backend of the current execution end calls the component generator to generate a page component. In order to avoid the user browsing a page with a new data level during the generation of the page component, therefore, it is necessary to detect whether the data level has increased or decreased. When it is detected that the data level has increased, the increased data level is updated based on the constraint level. At this time, the constraint level includes at least one of the home page level, the end page level, the intermediate page level, and the fixed page level. Updating the data level means recalculating the corresponding data levels of the end page level, the intermediate page level, etc. The embodiments of the present invention do not make specific limitations.

[0095] In another embodiment of the present invention, for further limitation and explanation, the step of generating the second page component matching the constraint data based on the component generator includes:

[0096] Detect whether the node data has increased or decreased;

[0097] If the node data increases, update the increased node data based on the constraint data, and generate a second page component matching the updated constraint data based on the component generator;

[0098] If the node data decreases, update the decreased node data based on the constraint data, and generate a second page component matching the updated constraint data based on the component generator;

[0099] For the purpose of improving the precise processing of page back or jump and avoiding the solidification and redundancy of the content of the back page, when the current execution end generates the second page component based on the constraint data, it first detects whether the node data has changed, that is, judges whether the data level has increased. For example, when originally accessing an application, after entering 5 pages, node data corresponding to the 5 pages is generated, and browsing is performed on the 5th layer page. When the mobile backend of the current execution end calls the component generator to generate a page component, in order to avoid changes in the payment amount or preferential activities on the page browsed by the user during the generation of the page component, therefore, detection is performed on whether the node data has increased or decreased. When it is detected that the node data has increased or decreased, the increased node data is updated based on the constraint data. At this time, the constraint data includes at least one of a constraint value, a constraint unit, and a constraint text, and a second page component matching the updated constraint data is generated based on the component generator, and the node data is updated, that is, re-judging whether there is corresponding constraint content in the node data according to the constraint node, which is not specifically limited in the embodiments of the present invention.

[0100] In another embodiment of the present invention, for further limitation and explanation, the steps further include:

[0101] Output a configuration box for the preset query condition to indicate the entry configuration of the constraint level and / or constraint data in the configuration box;

[0102] Update the preset query condition based on the constraint level and / or constraint data entered in the configuration box.

[0103] In order to achieve flexible back or jump of page content, the current execution end pre-outputs a configuration box for the preset query condition to meet the personalized query needs of users. At this time, the configuration box can be output on the front-end home page of the application to indicate that the user enters the constraint level or constraint data as the query condition through the configuration box. Among them, the configuration box includes multiple configuration items or configuration input boxes for the constraint level and constraint data. Preferably, the configuration box for the constraint level can be multiple configuration items, and the configuration box for the constraint data can be a configuration input box, which is not specifically limited in the embodiments of the present invention.

[0104] It should be noted that after the user enters or selects the corresponding constraint level or constraint data through the configuration box, the current execution end updates this constraint level and constraint data as the preset query condition. In another implementation scenario, the current execution end can pre-configure the default constraint level and default constraint data. If the user closes the configuration box, that is, does not customize the corresponding constraint level or constraint data, the current execution end can choose to use the default constraint level and default constraint data as the preset query condition. For example, the default constraint level is the home page and the end page, and the default constraint data is the total amount, May, etc. The embodiments of the present invention do not make specific limitations.

[0105] The embodiments of the present invention provide another method for displaying mobile terminal data query. By obtaining node data obtained by obtaining data at different data levels in the mobile terminal; calling at least one page component matching the real-time data level and outputting the page component in the front-end interface of the mobile terminal. The page component is created based on the node data and / or data level that meet the preset query condition, and the preset query condition is used to represent the constraint information for jump query of the data level; when it is detected that the page component is triggered, the target data bound to the page component is displayed, realizing the purpose of quickly querying the data of the component dashboard, reducing the data redrawing time, meeting the user's flexible page back custom needs, and thus improving the query and display efficiency of mobile terminal data.

[0106] Further, as an implementation of the above Figure 1 shown method, the embodiments of the present invention provide a display device for mobile terminal data query, as Figure 3 shown, the device includes:

[0107] An obtaining module 21, configured to obtain node data obtained by obtaining data at different data levels in the mobile terminal;

[0108] A calling module 22, configured to call at least one page component matching the real-time data level and output the page component in the front-end interface of the mobile terminal. The page component is created based on the node data and / or data level that meet the preset query condition, and the preset query condition is used to represent the constraint information for jump query of the data level;

[0109] A display module 23, configured to display the target data bound to the page component when it is detected that the page component is triggered.

[0110] Further, the device further includes: a parsing module, a generating module,

[0111] The parsing module is further configured to parse the constraint level and constraint data in the preset query condition;

[0112] The retrieval module is used to retrieve a component generator when the constraint level exists in the data level and / or the constraint data exists in the node data;

[0113] The generation module is used to generate a first page component that matches the constraint level based on the component generator and / or generate a second page component that matches the constraint data based on the component generator.

[0114] Further,

[0115] The retrieval module is specifically used to determine the component display area of the front-end interface based on the data volume and data display method in the real-time data level, where the data display method includes list display, image display, and text display; determine the triggering method of the first page component and / or the second page component according to the area size and area position of the component display area, and output the first page component and / or the second page component in the front-end interface according to the triggering method.

[0116] Further, the acquisition module is specifically used to record the node data generated when accessing each data level in real time, and construct a tree-level structure of the nodes according to the data level; mark a tree identifier for the node data according to the tree-level structure, and create a cache space that matches the tree-level structure; store the node data with the tree identifier into the corresponding cache space respectively.

[0117] Further, the generation module is specifically used to detect whether the data level increases; if the data level increases, update the increased data level based on the constraint level, and generate a first page component that matches the updated data level based on the component generator; where the constraint level includes at least one of a home page level, a last page level, an intermediate page level, and a fixed page level.

[0118] Further, the generation module is specifically further used to detect whether the node data increases or decreases; if the node data increases, update the increased node data based on the constraint data, and generate a second page component that matches the updated constraint data based on the component generator; if the node data decreases, update the decreased node data based on the constraint data, and generate a second page component that matches the updated constraint data based on the component generator; where the constraint data includes at least one of a constraint value, a constraint unit, and a constraint text.

[0119] Further, the output module is further configured to output a configuration box for the preset query condition to indicate entry configuration of the constraint level and / or constraint data in the configuration box; and update the preset query condition based on the constraint level and / or constraint data entered in the configuration box.

[0120] An embodiment of the present invention provides a display device for mobile terminal data query. Compared with the prior art, in the embodiment of the present invention, node data obtained by acquiring data at different data levels in the mobile terminal is obtained; at least one page component matching the real-time data level is retrieved and the page component is output in the front-end interface of the mobile terminal, where the page component is created based on node data and / or data levels that meet the preset query condition, and the preset query condition is used to represent constraint information for jump query of data levels; when it is detected that the page component is triggered, the target data bound to the page component is displayed, achieving the purpose of quickly querying data of the component dashboard, reducing the data redrawing time, meeting the user's flexible page back custom requirement, and thus improving the query and display efficiency of mobile terminal data.

[0121] According to an embodiment of the present invention, a storage medium stores at least one executable instruction, and the computer executable instruction can execute the mobile terminal data query display method in any of the above method embodiments.

[0122] Figure 4 FIG. shows a schematic structural diagram of a computer device according to an embodiment of the present invention. The specific implementation of the computer device is not limited in the specific embodiments of the present invention.

[0123] As Figure 4 shown, the computer device may include: a processor 302, a communication interface 304, a memory 306, and a communication bus 308.

[0124] Among them: The processor 302, the communication interface 304, and the memory 306 communicate with each other through the communication bus 308.

[0125] The communication interface 304 is used to communicate with network elements of other devices such as clients or other servers.

[0126] The processor 302 is configured to execute the program 310, and specifically may execute relevant steps in the above-mentioned mobile terminal data query display method embodiments.

[0127] Specifically, the program 310 may include program code, and the program code includes computer operation instructions.

[0128] The processor 302 may be a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention. One or more processors included in the computer device may be of the same type of processor, such as one or more CPUs; or may be of different types of processors, such as one or more CPUs and one or more ASICs.

[0129] A memory 306 for storing a program 310. The memory 306 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk memory.

[0130] The program 310 may specifically be used to cause the processor 502 to perform the following operations:

[0131] Obtain node data obtained by acquiring data at different data levels in the mobile terminal;

[0132] Retrieve at least one page component that matches the real-time data level, and output the page component in the front-end interface of the mobile terminal. The page component is created based on node data and / or data levels that meet preset query conditions, and the preset query conditions are used to represent constraint information for jumping and querying data levels;

[0133] When it is detected that the page component is triggered, display the target data bound to the page component.

[0134] Obviously, those skilled in the art should understand that the above-mentioned modules or steps of the present invention can be implemented by a general-purpose computing device. They can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices. Optionally, they can be implemented by program code executable by the computing device, so that they can be stored in a storage device and executed by the computing device. And in some cases, the steps shown or described may be executed in a different order than here, or they may be separately fabricated into individual integrated circuit modules, or multiple modules or steps among them may be fabricated into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

[0135] The above are only the preferred embodiments of the present invention and are not intended to limit the present invention. For those skilled in the art, the present invention may have various changes and modifications. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims

1. A method for displaying mobile terminal data query, characterized in that: include: Obtain node data obtained by acquiring data at different data levels in the mobile terminal; Retrieving at least one page component matching the real-time data hierarchy, and outputting the page component in the front-end interface of the mobile terminal, wherein the page component is created based on node data and / or data hierarchy that meets preset query conditions, and the preset query conditions are used to represent constraint information for jump querying the data hierarchy; When it is detected that the page component is triggered, the target data bound to the page component is displayed.

2. The method according to claim 1, characterized in that Before calling at least one page component matching the real-time data level, the method further includes: Parsing the constraint level and constraint data in the preset query condition; When the constraint level exists in the data level and / or the constraint data exists in the node data, calling a component generator; A first page component matching the constraint hierarchy is generated based on the component generator, and / or a second page component matching the constraint data is generated based on the component generator.

3. The method according to claim 2, characterized in that Outputting the page component in the front-end interface of the mobile terminal includes: Determine the component display area of ​​the front-end interface based on the amount of data in the real-time data level and the data display method, wherein the data display method includes list display, image display, and text display; The triggering method of the first page component and / or the second page component is determined according to the area size and area position of the component display area, and the first page component and / or the second page component is output in the front-end interface according to the triggering method.

4. The method according to claim 2, characterized in that: The node data obtained by acquiring data at different data levels in the mobile terminal includes: Recording in real time the node data generated when accessing each data level, and constructing a tree-like hierarchical structure of the nodes according to the data level; Marking the node data with a tree identifier according to the tree hierarchy structure, and creating a cache space matching the tree hierarchy structure; The node data with the tree type identifier are stored in the corresponding cache space respectively.

5. The method according to claim 4, characterized in that Generating a first page component matching the constraint hierarchy based on the component generator includes: detecting whether the data level increases; If the data level increases, the increased data level is updated based on the constraint level, and a first page component matching the updated data level is generated based on the component generator; The constraint level includes at least one of a home page level, a last page level, a middle page level, and a fixed page level.

6. The method according to claim 4, characterized in that Generating a second page component matching the constraint data based on the component generator includes: Detecting whether the node data increases or decreases; If the node data increases, the increased node data is updated based on the constraint data, and a second page component matching the updated constraint data is generated based on the component generator; If the node data is reduced, the reduced node data is updated based on the constraint data, and a second page component matching the updated constraint data is generated based on the component generator; The constraint data includes at least one of a constraint value, a constraint unit, and a constraint text.

7. The method according to any one of claims 1 to 6, characterized in that: The method further comprises: Outputting a configuration box of the preset query condition to instruct to enter and configure the constraint level and / or constraint data in the configuration box; The preset query condition is updated based on the constraint level and / or constraint data entered in the configuration box.

8. A display device for mobile terminal data query, characterized in that: include: An acquisition module is used to acquire node data obtained by acquiring data at different data levels in the mobile terminal; A calling module, used to call at least one page component matching the real-time data level, and output the page component in the front-end interface of the mobile terminal, wherein the page component is created based on node data and / or data levels that meet preset query conditions, and the preset query conditions are used to represent constraint information for jump query of the data level; The display module is used to display the target data bound to the page component when it is detected that the page component is triggered.

9. A computer-readable storage medium having a computer program / instruction stored thereon, characterized in that: When the computer program / instructions are executed by a processor, the steps of the method according to claim 1 are implemented.

10. A computer device comprising a memory, a processor and a computer program stored in the memory, characterized in that: The processor executes the computer program to implement the steps of the method of claim 1.

Images