Method and apparatus for report development based on generic indicators

Abstract

A method and apparatus for report development based on generic indicators involves creating general query indicators and generic query indicators; defining data sources corresponding to the general query indicators and the generic query indicators; creating a table in which the general query indicators and the generic query indicators are expressed in different areas; orientating the generic query indicators, so as to configure a calling means to call the generic query indicators; based on contents of the indicators in the table making a data request, so as to use the pre- configured calling means to acquire query data corresponding to the general query indicators and the generic query indicators from the data sources; and summarizing and fusing the query data corresponding to the general query indicators and the generic query indicators, and feeding the summarized and fused query data back to a front end for displaying. The apparatus implements the method.

Description

METHOD AND APPARATUS FOR REPORT DEVELOPMENT BASED ON GENERIC INDICATORS BACKGROUND OF THE INVENTION Technical Field

[0001] The present invention relates to the technical field of big data, and more particularly to a method and an apparatus for report development based on generic indicators. Description of Related Art

[0002] With continuous development of data-based business concepts, businesses rely more and more on real-time comparison of industry data, comparison of data flow directions, and cross- domain data assembling analysis for their daily decision making. Given this trend, general data analysis platforms are becoming more and more incompetent to satisfy various and grotesque analysis principles of data analysts. At present, general-purpose data analysis tools usually work in the following manners to answer to requirements from data analysts: 1. Starting a new, customized report development process: in the process of generally indicatorized data construction, there are some data that are impossible or costly to be generally indicatorized. When a general-purpose data analysis platform is not readily compatible, a typical solution is to manually develop a customized report process according to practical needs. 2. Custom components iterating consistently: there are some data that even if can be defined into indicators, their business logics may be too complicated or not popular among the public. In either case, for being compatible, a general data analysis platform will turn custom needs into general needs, so as to iteratively add new components to the analysis platform. However, this ends up to increased user costs, degraded user experience, and raising late maintenance costs. 3. Many indicators with similar names increasing maintenance costs: with expansion of market data domains, different business divisions may explain the same indicators in different ways, and this can result in a huge number of indicators having similar names, such as off-line sales amount, online sales amount, or more, which disadvantageously create a huge data intermedium layer containing numerous indicators. SUMMARY OF THE INVENTION <semantics>⌈0003⌉<annotation encoding="application / x-tex">\lceil 0003 \rceil< / annotation>< / semantics> The objective of the present invention is to provide a method and apparatus for report development based on generic indicators that are capable of simplifying development of reports, reducing development costs, while enhancing development efficiency.

[0004] To achieve the foregoing objective, in a first aspect the present invention provides a method for report development based on generic indicators, which comprises:

[0005] creating general query indicators and generic query indicators;

[0006] defining data sources corresponding to the general query indicators and the generic query indicators, respectively;

[0007] creating a table in which the general query indicators and the generic query indicators are expressed in different areas;

[0008] orientating the generic query indicators, so as to configure a calling means to call the generic query indicators;

[0009] based on contents of the indicators in the table making a data request, so as to use the pre- configured calling means to acquire query data corresponding to the general query indicators and the generic query indicators from the data sources; and

[0010] summarizing and fusing the query data corresponding to the general query indicators and the generic query indicators, and feeding the summarized and fused query data back to a front end for displaying. <semantics>⌈0011⌉<annotation encoding="application / x-tex">\lceil 0011 \rceil< / annotation>< / semantics> Preferably, the step of creating general query indicators and generic query indicators comprises:

[0012] using an indicator-defining module to define the general query indicators with normal specifications and defining the generic query indicators without actual business technical specifications, wherein <semantics>⌈0013⌉<annotation encoding="application / x-tex">\lceil 0013 \rceil< / annotation>< / semantics> the generic query indicators include content descriptions of indicator names and indicator units, and the generic query indicators may be sub-indicators of the general query indicators. <semantics>⌈0014⌉<annotation encoding="application / x-tex">\lceil 0014 \rceil< / annotation>< / semantics> Preferably, the step of defining data source corresponding to the general query indicators and the generic query indicators, respectively, comprises:

[0015] using a data-source defining module to orientate the internal data sources of the general query indicators and to orientate the external data sources of the generic query indicators;

[0016] in which source routes of the external data sources include one or more of databases, API interfaces, JAR packages, KV texts and EXCEL files;

[0017] in which data source information of the databases includes services IPs, interfaces, and database names, and data source information of the API interfaces includes interface addresses, input parameter information, and return parameter information, while data source information of the JAR packages includes JAR names, interface-type full paths, and method names.

[0018] Preferably, the step of creating a table in which the general query indicators and the generic query indicators are expressed in different areas comprises:

[0019] using a visualization platform creating table to set contents of the table as analysis fields, the general query indicators, and the generic query indicators, successively.

[0020] More preferably, the step of orientating the generic query indicators, so as to configure a calling means to call the generic query indicators comprises:

[0021] using a generic orientating module to orientate the calling means of the generic query indicators and the corresponding generic query indicators, in which the generic query indicator and the calling means are of one-to-one correspondence, and performing dimension mapping on the general query indicators and the analysis fields in the calling means.

[0022] Further, the step of based on contents of the indicators in the table making a data request, so as to use the pre-configured calling means to acquire query data corresponding to the general query indicators and the generic query indicators from the data sources comprises: <semantics>⌈0023⌉<annotation encoding="application / x-tex">\lceil 0023 \rceil< / annotation>< / semantics> initiating a data request according to the generic query indicators in the table, and after indicator screening, using the corresponding calling means to access the external data sources by way of one or more of databases, API interfaces, JAR packages, KV texts, and EXCEL files to acquire the query data of the generic indicators; and

[0024] according to the general query indicators in the table, initiating a data request, and after indicator screening, using the corresponding calling means to acquire the query data of the general indicators from the internal data sources.

[0025] Preferably, the step of summarizing and fusing the query data corresponding to the general query indicators and the generic query indicators, and feeding the summarized and fused query data back to a front end for displaying comprises:

[0026] summarizing and fusing the query data of the generic indicators and the query data of the general indicators in the table according to the dimensionally mapped analysis fields, and feeding back the summarized and fused data to the front-end pages for visually displaying.

[0027] As compared to the prior art, the method for report development based on generic indicators of the present invention has the following beneficial effects:

[0028] the disclosed method for report development based on generic indicators begins with clarifying general query indicators and generic query indicators required by the report. Then data sources corresponding to the general query indicators and the generic query indicators are defined. Afterward, a table is created to contain the general query indicators and the generic query indicators in different areas. Meanwhile, the generic query indicators are orientated and configured for its calling means. A data request is made based on contents of the indicators in the table, so as to use the pre-configured calling means to acquire query data corresponding to the general query indicators and the generic query indicators from the data sources. At last, the query data corresponding to the general query indicators and the generic query indicators are summarized and fused before being fed back to the front-end pages for displaying.

[0029] It is thus clear that by introducing the concept of generic query indicator, the present invention allows one generic query indicator to represent N general query indicators, thereby realizing light-weight management of indicator clusters. In addition, as compared to report development processes of general query indicators, introduce of generic query indicators can significantly decrease the number of components to be customizedly developed for general query indicators, thereby enhancing efficiency of report development.

[0030] In a second aspect, the present invention provides an apparatus for report development based on generic indicator, which is applicable to the method for report development based on generic indicators of the foregoing technical scheme. The apparatus comprises: <semantics>⌈0031⌉<annotation encoding="application / x-tex">\lceil 0031 \rceil< / annotation>< / semantics> an indicator creating unit, for creating general query indicators and generic query indicators;

[0032] a data source defining unit, for defining data sources corresponding to the general query indicators and the generic query indicators, respectively;

[0033] a table creating unit, for creating a table in which the general query indicators and the generic query indicators are expressed in different areas;

[0034] a calling and configuring unit, for orientating the generic query indicators, so as to configure a calling means to call the generic query indicators;

[0035] a data-requesting unit, for based on contents of the indicators in the table making a data request, so as to use the pre-configured calling means to acquire query data corresponding to the general query indicators and the generic query indicators from the data sources; and

[0036] a data fusing unit, for summarizing and fusing the query data corresponding to the general query indicators and the generic query indicators, and feeding the summarized and fused query data back to a front end for displaying.

[0037] Preferably, the indicator creating unit is further for:

[0038] using an indicator-defining module to define the general query indicators with normal specifications and defining the generic query indicators without actual business technical specifications, wherein

[0039] the generic query indicators include content descriptions of indicator names and indicator units, and the generic query indicators may be sub-indicators of the general query indicators.

[0040] As compared to the prior art, the disclosed apparatus for report development based on generic indicators provides beneficial effects that are similar to those provided by the disclosed method for report development based on generic indicators as enumerated above, and thus no repetitions are made herein.

[0041] In a third aspect, the present invention provides a computer-readable storage medium, storing thereon a computer program. When the computer program is executed by a processor, it implements the steps of the method for report development based on generic indicators as described previously.

[0042] As compared to the prior art, the disclosed computer-readable storage medium provides beneficial effects that are similar to those provided by the disclosed method for report development based on generic indicators as enumerated above, and thus no repetitions are made herein. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] The accompanying drawings are provided herein for better understanding of the present invention and form a part of this disclosure. The illustrative embodiments and their descriptions are for explaining the present invention and by no means form any improper limitation to the present invention, wherein:

[0044] FIG. 1 is a flowchart of a method for report development based on generic indicators according to one embodiment of the present invention;

[0045] FIG. 2 is another flowchart of the method for report development based on generic indicators according to the embodiment of the present invention;

[0046] FIG. 3 is an exemplificative applied diagram of one embodiment of the present invention used as a widget component;

[0047] FIG. 4 shows comparison between a conventional process of report development and an exemplificative process of report development according to the embodiment of the present invention; and

[0048] FIG. 5 is an exemplificative diagram illustrating lineage tracing of report data according to one embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0049] To make the foregoing objectives, features, and advantages of the present invention clearer and more understandable, the following description will be directed to some embodiments as depicted in the accompanying drawings to detail the technical schemes disclosed in these embodiments. It is, however, to be understood that the embodiments referred herein are only a part of all possible embodiments and thus not exhaustive. Based on the embodiments of the present invention, all the other embodiments can be conceived without creative labor by people of ordinary skill in the art, and all these and other embodiments shall be embraced in the scope of the present invention. Embodiment 1

[0050] Referring to FIG. 1 and FIG. 2, the present embodiment provides a method for report development based on generic indicators, which comprises:

[0051] creating general query indicators and generic query indicators; defining data sources corresponding to the general query indicators and the generic query indicators, respectively; creating a table in which the general query indicators and the generic query indicators are expressed in different areas; orientating the generic query indicators, so as to configure a calling means to call the generic query indicators; based on contents of the indicators in the table making a data request, so as to use the pre-configured calling means to acquire query data corresponding to the general query indicators and the generic query indicators from the data sources; and summarizing and fusing the query data corresponding to the general query indicators and the generic query indicators, and feeding the summarized and fused query data back to a front end for displaying.

[0052] The disclosed method for report development based on generic indicators begins with clarifying general query indicators and generic query indicators required by the report. Then data sources corresponding to the general query indicators and the generic query indicators are defined, respectively. Afterward, a table is created to contain the general query indicators and the generic query indicators in different areas. Meanwhile, the generic query indicators are orientated and configured for its calling means. A data request is made based on contents of the indicators in the table, so as to use the pre-configured calling means to acquire query data corresponding to the general query indicators and the generic query indicators from the data sources. At last, the query data corresponding to the general query indicators and the generic query indicators are summarized and fused before being fed back to the front-end pages for displaying.

[0053] It is thus clear that by introducing the concept of generic query indicator, the present invention allows one generic query indicator to represent N general query indicators, thereby realizing light-weight management of indicator clusters. In addition, as compared to report development processes of general query indicators, introduce of generic query indicators can significantly decrease the number of components to be customizedly developed for general query indicators, thereby enhancing efficiency of report development.

[0054] It is to be explained that generic retrieval indicators are a series of indicator ranges only having indicator meanings but not supported by actual specifications and data sources, with orientation the specifications and actual data sources of these indicators deferred to the phase of creation of solid reports or to the phase of real-time analysis of data. A generic retrieval indicator is different from a general indicator for the generic indicator can be defined without being bound to actual data sources. Taking a large retail company for example, the created general sales indicators may form a cluster of indicators having specific specifications, such as the online sales amount, the off-line sales amount, and so on. By comparison, with the use of the generic version, only one indicator, namely the sales amount indicator, has to be created.

[0055] In the embodiment as described above, the step of creating general query indicators and generic query indicators comprises:

[0056] using an indicator-defining module to define the general query indicators with normal specifications and defining the generic query indicators without actual business technical specifications, wherein the generic query indicators include content descriptions of indicator names and indicator units. For example, the generic query indicators may be sub-indicators of the general query indicators.

[0057] In specific implementations, the indicator defining module defines not only general query indicators with normal specifications, but also generic query indicators without actual business technical specifications. Therein, the generic query indicators only contain descriptions about external contents such as indicator names and indicator units, and have on underlying business technical specifications that support data. Generic query indicators extensively refer to a set of indicators having similar meanings, such a small-shop sales amount, online-shop sales amount, and cloud-shop sales amount, collectively called as the sales amounts. In addition, the derived generic query indicator may also define calculation formulas among generic indicators. For example, a calculation formula may be used to determine the sum of the small-shop sales amount and the online-shop sales amount.

[0058] In the embodiment as described above, the step of defining data source corresponding to the general query indicators and the generic query indicators, respectively, comprises:

[0059] using a data-source defining module to orientate the internal data sources of the general query indicators and to orientate the external data sources of the generic query indicators; in which source routes of the external data sources include one or more of databases, API interfaces, JAR packages, KV texts and EXCEL files; in which data source information of the databases includes services IPs, interfaces, and database names, and data source information of the API interfaces includes interface addresses, input parameter information, and return parameter information, while data source information of the JAR packages includes JAR names, interface- type full paths, and method names.

[0060] In specific implementations, the data source defining module is primarily used to define information of external data sources, such as services IPs, ports, database names, etc. under the database type; interface addresses, input parameter information, return parameter information, etc. under API interface; JAR names, interface type full paths, method names, etc. introduced under JAR packages.

[0061] As everyone knows, generic query indicators typically acquire indicator data from external data sources, and general query indicators typically acquire indicator data from internal data sources. This is because that it is uncertain that actual specifications of external data sources support data sources, while the actual specifications of internal data sources generally support data source certainly. For example, if a user wants to make comparative analysis of online sales data between his / her company and a competitor, the user may define his / her company as general query indicators, and define the competitor as generic query indicators, so that he / she can acquire query data through corresponding data sources.

[0062] In the embodiment as described above, the step of creating a table in which the general query indicators and the generic query indicators are expressed in different areas comprises:

[0063] using a visualization platform creating table to set contents of the table as analysis fields, the general query indicators, and the generic query indicators, successively. For example, the analysis field is a query region.

[0064] In the embodiment as described above, the step of orientating the generic query indicators, so as to configure a calling means to call the generic query indicators comprises:

[0065] using a generic orientating module to orientate the calling means of the generic query indicators and the corresponding generic query indicators, in which the generic query indicator and the calling means are of one-to-one correspondence, and performing dimension mapping on the general query indicators and the analysis fields in the calling means, such as the region.

[0066] In the embodiment as described above, the step of based on contents of the indicators in the table making a data request, so as to use the pre-configured calling means to acquire query data corresponding to the general query indicators and the generic query indicators from the data sources comprises:

[0067] initiating a data request according to the generic query indicators in the table, and after indicator screening, using the corresponding calling means to access the external data sources by way of one or more of databases, API interfaces, JAR packages, KV texts, and EXCEL files to acquire the query data of the generic indicators; and according to the general query indicators in the table, initiating a data request, and after indicator screening, using the corresponding calling means to acquire the query data of the general indicators from the internal data sources.

[0068] In the embodiment as described above, the step of based on contents of the indicators in the table making a data request, so as to use the pre-configured calling means to acquire query data corresponding to the general query indicators and the generic query indicators from the data sources comprises:

[0069] initiating a data request according to the generic query indicators in the table, and after indicator screening, using the corresponding calling means to access the external data sources by way of one or more of databases, API interfaces, JAR packages, KV texts, and EXCEL files to acquire the query data of the generic indicators; and

[0070] according to the general query indicators in the table, initiating a data request, and after indicator screening, using the corresponding calling means to acquire the query data of the general indicators from the internal data sources.

[0071] In the embodiment as described above, the step of summarizing and fusing the query data corresponding to the general query indicators and the generic query indicators, and feeding the summarized and fused query data back to a front end for displaying comprises:

[0072] summarizing and fusing the query data of the generic indicators and the query data of the general indicators in the table according to the dimensionally mapped analysis fields, such as large-region fields, and feeding back the summarized and fused data to the front-end pages for visually displaying.

[0073] It is to be noted that the fur modules used in the scheme of the present embodiment primarily include a data source defining module, an indicator defining module, a generic orientating model, and a data-accessing module, as depicted in FIG. 2. Therein, the data source defining module and the indicator defining module are independent of each other. The generic orientating module and the data-accessing module depend on the data source defining module and the indicator defining module.

[0074] At the data source defining module, the user defines one or more implementations such as API interface of data, embedded JAR packages, KV texts, and databases like Su-Ning Data into external data source information. At the indicator defining module, the user adds his / her own new generic indicators. In a specific scene of data analysis, the external data source information is orientated to designated generic indicator, so that data query can be made through the data routing and implementing logic of the data-accessing module.

[0075] The data source defining module is primarily for defining external data source information, such as services IPs, ports, database names, etc. under the database type; interface addresses, input parameter information, return parameter information, etc. under API interface; JAR names, interface type full paths, method names, etc. introduced under JAR packages.

[0076] The indicator defining module defines not only normal specificlized general query indicators, but also generic query indicators.

[0077] The generic orientating model orientates data sources for generic query indicators. At this time, this means to specify the contents of business technical specifications of generic query indicators. The orientated contents include external data source codes, dimension-mapping KV combinations, and indicator-mapping KV combinations. To be noted, it is focused on rows of generic query indicator, but not generic indicators, because in one image, the same generic query indicator may generate multiple rows, and data sources or logics of each of these rows may be different. For example, the sales amount may be subdivided into the small-shop sales amount from small-shop interface data, the on-line shop sales amount from online-shop model data, and so on.

[0078] The data-accessing module is primarily for analyzing configuration information of generic indicator rows, and routing to different data channels according to the data source configured for the generic indicator rows. These channels may be external API interface, built-in, uploaded JAR packages, key-value pair documents, etc.

[0079] Referring to FIG. 2, for better understanding, the scheme of the foregoing embodiment is exemplary explained as below:

[0800] Step 1. A user creates general query indicators, such as the total sales amount, based on an indicator model layer and an indicator acceleration layer.

[0081] Step 2. The online sales amount (Generic Query Indicator 1) is placed in the database of Data Mart through an ETL task, and the data source defining module defines external data to identify its calling means A.

[0082] Step 3. The off-line sales amount (Generic Query Indicator 2) is provided through the API interface of the off-line data system, and the data source defining module defines external data to identify its calling means B.

[0083] Step 4. The user defines the sub-sales amounts of the generic indicator at the indicator defining module, namely the online sales amount and the off-line sales amount, respectively.

[0084] Step 5. The user creates a table in the visualization platform, and selects the indicators related to the general total sales amount, the off-line sales amount, and the off-line sales amount as the contents of the table. The contents of the table include the large sales region, the total sales amount, the online sales amount, and the offline sales amount successively.

[0085] Step 6. The generic orientating model is used to perform generic orientation, wherein the calling means A is orientated to the online sales amount row, and the calling means B is orientated to the off-line sales amount row. Then the total sales amount, the calling means A, and the larger region field of the calling means B are dimensionally mapped.

[0086] Step 7. A request is made for indicator data in the table.

[0087] Step 8. The data routing module is used to perform indicator screening, and the total sales amount is assigned to the data acceleration module to make a data request for the general indicators. The online sales amount and the offline sales amount are assigned to the data- accessing module.

[0088] Step 9. The data-accessing module is used to request the API interface and the built-in JAR method, respectively according to the orientating contents of the generic query indicators for data request.

[0089] Step 10. The query data returned by the data request interface are collected at the data-fusing module, and data fusing is made between the general query indicators and generic query indicators according to the dimensionally mapped large-region field.

[0090] Step 11. The fused data are fed back to front-end pages for displaying.

[0091] As an example, in the desktop widget component, as shown in FIG. 3, the sales amount is a generic query indicator that displays the total sales amount by default. The online sales amount and the off-line sales amount are generic orientating indicators are input in advance. The user may use the input button to define new contents for orientation. Alternatively, the currently developed JAR packages or EXCEL / CSV documents may be dragged to the display region to generate a temporary generic orientating indicator, showing the corresponding sales amount.

[0092] FIG. 4 illustrates how a customized report is embedded in a portal. At the left is a customized means as used in the prior art, wherein the customized report URL link is embedded into the portal iframe. The right part shows the representative of the present embodiment, wherein the generic query indicators and the data specifications are matched so that a user can easily implement by developing data specifications. With the scheme of the present embodiment, no matter how complicated the business logic is, to the largest extent the page component supports, the user is free from full-volume custom definition and there is no need to embed a URL link. The only thing the user has to do is to perform simple data interactive development on the generic query indicators. Meanwhile, as shown in FIG. 5, the scheme of the present embodiment also supports lineage tracing of the report data of the general query indicators and the generic query indicators.

[0093] It is thus clear that with the present embodiment the following effects can realized:

[0094] Light-weight indicator management: with introduction of the concept of generic indicators, the scheme can be said as only defining indicator meanings. For example, for the sales amount, the clarified type is placed under the specific image scene, thereby significantly reducing the number of indicator clusters having similar names.

[0095] Simplified process for customized development that reduce the costs for customized development: for report development, no repeated works for page design and data fusion have to be performed, and the only part needing development and maintenance is data orientation corresponding to generic query indicators. This part may be the external API interface, the exported JAR packages, custom KV values or EXCEL files. This significantly shortens the development cycle and reduce the costs for development and maintenance.

[0096] Reduced number of custom components to be developed: user only have to define a ser of generic query indicator design components and generic indicator orientating components, and the rest can be realized using the data-accessing module. There is no need to define different components for different business scenes. Embodiment 2

[0097] The present embodiment provides an apparatus for report development based on generic indicators, which comprises:

[0098] an indicator creating unit, for creating general query indicators and generic query indicators;

[0099] a data source defining unit, for defining data sources corresponding to the general query indicators and the generic query indicators, respectively;

[0100] a table creating unit, for creating a table in which the general query indicators and the generic query indicators are expressed in different areas; <semantics>⌈0101⌉<annotation encoding="application / x-tex">\lceil 0101 \rceil< / annotation>< / semantics> a calling and configuring unit, for orientating the generic query indicators, so as to configure a calling means to call the generic query indicators; <semantics>⌈0102⌉<annotation encoding="application / x-tex">\lceil 0102 \rceil< / annotation>< / semantics> a data-requesting unit, for based on contents of the indicators in the table making a data request, so as to use the pre-configured calling means to acquire query data corresponding to the general query indicators and the generic query indicators from the data sources; and <semantics>⌈0103⌉<annotation encoding="application / x-tex">\lceil 0103 \rceil< / annotation>< / semantics> a data fusing unit, for summarizing and fusing the query data corresponding to the general query indicators and the generic query indicators, and feeding the summarized and fused query data back to a front end for displaying.

[0104] Preferably, the indicator creating unit is further for: <semantics>⌈0105⌉<annotation encoding="application / x-tex">\lceil 0105 \rceil< / annotation>< / semantics> using an indicator-defining module to define the general query indicators with normal specifications and defining the generic query indicators without actual business technical specifications, wherein

[0106] the generic query indicators include content descriptions of indicator names and indicator units, and the generic query indicators are sub-indicators of the general query indicators.

[0107] As compared to the prior art, the disclosed computer-readable storage medium provides beneficial effects that are similar to those provided by the disclose method for report development based on generic indicators as enumerated above, and thus no repetitions are made herein. Embodiment 3 <semantics>⌈0108⌉<annotation encoding="application / x-tex">\lceil 0108 \rceil< / annotation>< / semantics> The present embodiment provides a computer-readable storage medium, storing thereon a computer program. When the computer program is executed by a processor, it implements the steps of the method for report development based on generic indicators as described previously.

[0109] As compared to the prior art, the disclosed computer-readable storage medium provides beneficial effects that are similar to those provided by the disclose method for report development based on generic indicators as enumerated above, and thus no repetitions are made herein. <semantics>⌈0110⌉<annotation encoding="application / x-tex">\lceil 0110 \rceil< / annotation>< / semantics> As will be appreciated by people of ordinary skill in the art, implementation of all or a part of the steps of the method of the present invention as described previously may be realized by having a program instruct related hardware components. The program may be stored in a computer-readable storage medium, and the program is about performing the individual steps of the methods described in the foregoing embodiments. The storage medium may be a ROM / RAM, a disk, a compact disk, a memory card or the like.

[0111] The present invention has been described with reference to the preferred embodiments and it is understood that the embodiments are not intended to limit the scope of the present invention. Moreover, as the contents disclosed herein should be readily understood and can be implemented by a person skilled in the art, all equivalent changes or modifications which do not depart from the concept of the present invention should be encompassed by the appended claims. Hence, the scope of the present invention shall only be defined by the appended claims.

Claims

<pat:ClaimStatement>Claims:< / pat:ClaimStatement> <pat:Claims com:id="claims"> <pat:Claim com:id="CLM-00001"> <pat:ClaimNumber>1< / pat:ClaimNumber> <pat:ClaimText>1. A computer-implemented method comprising: creating general query indicators and generic query indicators includes using an indicator-defining module to define the general query indicators with normal specifications and defining the generic query indicators without actual business technical specifications, wherein the generic query indicators include content descriptions of indicator names and indicator units; defining data sources corresponding to the general query indicators and the generic query indicators, respectively; creating a table in which the general query indicators and the generic query indicators are contained in different areas; orientating the generic query indicators, to configure a calling mode to call the generic query indicators; making a data request based on contents of the indicators in the table, to use the pre- configured calling mode to acquire query data corresponding to the general query indicators and the generic query indicators from the data sources; and summarizing and fusing the query data corresponding to the general query indicators and the generic query indicators, and feeding the summarized and fused query data back to a front end for visual display. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00002"> <pat:ClaimNumber>2< / pat:ClaimNumber> <pat:ClaimText>2. The computer-implemented method of claim 1, wherein one generic query indicator represents N general query indicators, where <semantics>N≥1<annotation encoding="application / x-tex">N \ge 1< / annotation>< / semantics>. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00003"> <pat:ClaimNumber>3< / pat:ClaimNumber> <pat:ClaimText>3. The computer-implemented method of any one of claims 1 to 2, wherein the generic query indicators are sub-indicators of the general query indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00004"> <pat:ClaimNumber>4< / pat:ClaimNumber> <pat:ClaimText>4. The computer-implemented method of any one of claims 1 to 3, wherein the general query indicators comprise a total sales amount. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00005"> <pat:ClaimNumber>5< / pat:ClaimNumber> <pat:ClaimText>5. The computer-implemented method of any one of claims 1 to 4, wherein the generic query indicators comprise an online sales amount and an off-line sales amount. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00006"> <pat:ClaimNumber>6< / pat:ClaimNumber> <pat:ClaimText>6. The computer-implemented method of any one of claims 1 to 4, wherein the generic query indicators comprise a calculation formula to determine a sum of one or more generic query indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00007"> <pat:ClaimNumber>7< / pat:ClaimNumber> <pat:ClaimText>7. The computer-implemented method of any one of claims 1 to 6, wherein defining the data sources corresponding to the general query indicators and the generic query indicators, respectively, comprises: using a data-source defining module to orientate internal data sources of the general query indicators and to orientate external data sources of the generic query indicators; and wherein source routes of the external data sources include one or more of databases, API interfaces, JAR packages, KV texts and EXCEL files. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00008"> <pat:ClaimNumber>8< / pat:ClaimNumber> <pat:ClaimText>8. The computer-implemented method of claim 7, wherein data source information of the databases includes services IPs, interfaces, and database names. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00009"> <pat:ClaimNumber>9< / pat:ClaimNumber> <pat:ClaimText>9. The computer-implemented method of claim 7, wherein data source information of the API interfaces includes interface addresses, input parameter information, and return parameter information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00010"> <pat:ClaimNumber>10< / pat:ClaimNumber> <pat:ClaimText>10. The computer-implemented method of claim 7, wherein data source information of the JAR packages includes JAR names, interface-type full paths, and method names. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00011"> <pat:ClaimNumber>11< / pat:ClaimNumber> <pat:ClaimText>11. The computer-implemented method of any one of claims 1 to 10, wherein creating the table in which the general query indicators and the generic query indicators are contained in different areas comprises: using a visualization platform to set contents of the table as analysis fields, the general query indicators, and the generic query indicators, successively. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00012"> <pat:ClaimNumber>12< / pat:ClaimNumber> <pat:ClaimText>12. The computer-implemented method of claim 11, wherein orientating the generic query indicators, to configure the calling mode to call the generic query indicators comprises: using a generic orientating module to orientate the calling mode of the generic query indicators and the corresponding generic query indicators, in which the generic query indicator and the calling mode are of one-to-one correspondence, and performing dimension mapping on the general query indicators and the analysis fields in the calling mode. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00013"> <pat:ClaimNumber>13< / pat:ClaimNumber> <pat:ClaimText>13. The computer-implemented method of any one of claims 7 to 12, wherein making the data request based on the contents of the indicators in the table, to use the pre-configured calling mode to acquire the query data corresponding to the general query indicators and the generic query indicators from the data sources comprises: initiating a generic data request by a data-accessing module, according to the generic query indicators in the table, and indicator screening by a data routing module, using a corresponding calling mode to access the external data sources by way of one or more of the databases, the API interfaces, the JAR packages, the KV texts, and the EXCEL files to acquire the query data of the generic indicators; and initiating a general data request by the data-accessing module, according to the general query indicators in the table, and indicator screening by the data routing module, using the corresponding calling mode to acquire the query data of a general indicators from the internal data sources. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00014"> <pat:ClaimNumber>14< / pat:ClaimNumber> <pat:ClaimText>14. The computer-implemented method of any one of claims 12 to 13, wherein summarizing and fusing the query data corresponding to the general query indicators and the generic query indicators, and feeding the summarized and fused query data back to the front end for visual display comprises: using a data-fusion module to summarize and fuse the query data of the generic indicators and the query data of the general indicators in the table according to dimensionally mapped analysis fields, and feeding back the summarized and fused data to the front-end for visual display. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00015"> <pat:ClaimNumber>15< / pat:ClaimNumber> <pat:ClaimText>15. The computer-implemented method of any one of claims 1 to 14, further comprising lineage tracing of the general query indicators and the generic query indicators to their respective data sources. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00016"> <pat:ClaimNumber>16< / pat:ClaimNumber> <pat:ClaimText>16. The computer-implemented method of any one of claims 1 to 15, wherein generic retrieval indicators are a series of indicator ranges only having indicator meanings but not supported by actual specifications and data sources, with orientation the specifications and actual data sources of these indicators deferred to the phase of creation of solid reports or to the phase of real-time analysis of data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00017"> <pat:ClaimNumber>17< / pat:ClaimNumber> <pat:ClaimText>17. The computer-implemented method of claim 16, wherein the generic retrieval indicator is different from the general indicator for the generic indicator is defined without being bound to actual data sources. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00018"> <pat:ClaimNumber>18< / pat:ClaimNumber> <pat:ClaimText>18. The computer-implemented method of claim 17, wherein created general sales indicators form a cluster of indicators having specific specifications, including an online sales amount, an off-line sales amount. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00019"> <pat:ClaimNumber>19< / pat:ClaimNumber> <pat:ClaimText>19. The computer-implemented method of any one of claims 1 to 18, wherein the use of the generic query indicators, only one indicator, a sales amount indicator, has to be created. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00020"> <pat:ClaimNumber>20< / pat:ClaimNumber> <pat:ClaimText>20. The computer-implemented method of any one of claims 1 to 19, wherein the generic query indicators are sub-indicators of the general query indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00021"> <pat:ClaimNumber>21< / pat:ClaimNumber> <pat:ClaimText>21. The computer-implemented method of any one of claims 1 to 20, wherein the generic query indicators only contain descriptions about external contents including indicator names and indicator units, and have underlying business technical specifications that support data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00022"> <pat:ClaimNumber>22< / pat:ClaimNumber> <pat:ClaimText>22. The computer-implemented method of any one of claims 1 to 21, wherein the generic query indicators refer to a set of indicators having similar meanings, including small-shop sales amount, the online shop sales amount, and cloud-shop sales amount, collectively called as the sales amounts. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00023"> <pat:ClaimNumber>23< / pat:ClaimNumber> <pat:ClaimText>23. The computer-implemented method of any one of claims 1 to 22, wherein the derived generic query indicator defines calculation formulas among generic indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00024"> <pat:ClaimNumber>24< / pat:ClaimNumber> <pat:ClaimText>24. The computer-implemented method of any one of claims 1 to 23, wherein with a data source defining module, a user defines one or more implementations including API interface of data, embedded JAR packages, KV texts, and databases into external data source information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00025"> <pat:ClaimNumber>25< / pat:ClaimNumber> <pat:ClaimText>25. The computer-implemented method of claim 24, wherein the indicator defining module, the user adds new generic indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00026"> <pat:ClaimNumber>26< / pat:ClaimNumber> <pat:ClaimText>26. The computer-implemented method of any one of claims 1 to 25, wherein a specific scene of data analysis, external data source information is orientated to designated generic indicator, wherein data query is made through data routing and implementing logic of a data-accessing module. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00027"> <pat:ClaimNumber>27< / pat:ClaimNumber> <pat:ClaimText>27. The computer-implemented method of claim 24, wherein the data source defining module is primarily for defining external data source information, including services IPs, ports, database names, under the database type and interface addresses, input parameter information, return parameter information, under API interface, and JAR names, interface type full paths, method names, introduced under JAR packages. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00028"> <pat:ClaimNumber>28< / pat:ClaimNumber> <pat:ClaimText>28. The computer-implemented method of any one of claims 1 to 27, wherein orientated contents include external data source codes, dimension-mapping KV combinations, and indicator-mapping KV combinations. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00029"> <pat:ClaimNumber>29< / pat:ClaimNumber> <pat:ClaimText>29. The computer-implemented method of any one of claims 1 to 28, wherein is focused on rows of generic query indicator, but not generic indicators, wherein in one image, the generic query indicator generates multiple rows, and data sources or logics of the rows are different. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00030"> <pat:ClaimNumber>30< / pat:ClaimNumber> <pat:ClaimText>30. The computer-implemented method of claim 13, wherein the data-accessing module is primarily for analyzing configuration information of generic indicator rows, and routing to different data channels according to the data source configured for the generic indicator rows, wherein the channels include external API interface, built-in, uploaded JAR packages, key-value pair documents. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00031"> <pat:ClaimNumber>31< / pat:ClaimNumber> <pat:ClaimText>31. The computer-implemented method of any one of claims 1 to 30, wherein the user creates general query indicators, including total sales amount, based on an indicator model layer and an indicator acceleration layer. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00032"> <pat:ClaimNumber>32< / pat:ClaimNumber> <pat:ClaimText>32. The computer-implemented method of any one of claims 1 to 31, wherein the user defines sub-sales amounts of the generic indicator at the indicator defining module, including online sales amount and off-line sales amount. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00033"> <pat:ClaimNumber>33< / pat:ClaimNumber> <pat:ClaimText>33. The computer-implemented method of any one of claims 1 to 32, wherein the contents of the table include large sales region, total sales amount, online sales amount, and off-line sales amount successively. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00034"> <pat:ClaimNumber>34< / pat:ClaimNumber> <pat:ClaimText>34. The computer-implemented method of claim 13, wherein the data routing module is performs indicator screening, and total sales amount is assigned to a data acceleration module to make a data request for the general indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00035"> <pat:ClaimNumber>35< / pat:ClaimNumber> <pat:ClaimText>35. The computer-implemented method of any one of claims 1 to 34, wherein online sales amount and off-line sales amount are assigned to the data-accessing module. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00036"> <pat:ClaimNumber>36< / pat:ClaimNumber> <pat:ClaimText>36. The computer-implemented method of any one of claims 1 to 35, wherein online sales amount and off-line sales amount are generic orientating indicators and are input in advance. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00037"> <pat:ClaimNumber>37< / pat:ClaimNumber> <pat:ClaimText>37. The computer-implemented method of any one of claims 1 to 36, wherein the user uses an input button to define new contents for orientation. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00038"> <pat:ClaimNumber>38< / pat:ClaimNumber> <pat:ClaimText>38. An apparatus comprising: an indicator creating unit, configured to create general query indicators and generic query indicators including using an indicator-defining module to define the general query indicators with normal specifications and defining the generic query indicators without actual business technical specifications, wherein the generic query indicators include content descriptions of indicator names and indicator units; a data source defining unit, configured to define data sources corresponding to the general query indicators and the generic query indicators; a table creating unit, configured to create a table in which the general query indicators and the generic query indicators are contained in different areas; a calling and configuring unit, configured to orientate the generic query indicators, to configure a calling mode to call the generic query indicators; a data-requesting unit, configured to, based on contents of the indicators in the table making a data request, to use the pre-configured calling mode to acquire query data corresponding to the general query indicators and the generic query indicators from the data sources; and a data fusing unit, configured to: summarize and fuse the query data corresponding to the general query indicators and the generic query indicators; and feed the summarized and fused query data back to a front end for displaying. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00039"> <pat:ClaimNumber>39< / pat:ClaimNumber> <pat:ClaimText>39. The apparatus of claim 38, wherein one generic query indicator represents N general query indicators, where <semantics>N≥1<annotation encoding="application / x-tex">N \ge 1< / annotation>< / semantics>. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00040"> <pat:ClaimNumber>40< / pat:ClaimNumber> <pat:ClaimText>40. The apparatus of any one of claims 38 to 39, wherein the generic query indicators are sub- indicators of the general query indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00041"> <pat:ClaimNumber>41< / pat:ClaimNumber> <pat:ClaimText>41. The apparatus of any one of claims 38 to 40, wherein the general query indicators comprise a total sales amount. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00042"> <pat:ClaimNumber>42< / pat:ClaimNumber> <pat:ClaimText>42. The apparatus of any one of claims 38 to 41, wherein the generic query indicators comprise an online sales amount and an off-line sales amount. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00043"> <pat:ClaimNumber>43< / pat:ClaimNumber> <pat:ClaimText>43. The apparatus of any one of claims 38 to 41, wherein the generic query indicators comprise a calculation formula to determine a sum of one or more generic query indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00044"> <pat:ClaimNumber>44< / pat:ClaimNumber> <pat:ClaimText>44. The apparatus of any one of claims 38 to 43, wherein defining the data sources corresponding to the general query indicators and the generic query indicators, respectively, comprises: using a data-source defining module to orientate internal data sources of the general query indicators and to orientate external data sources of the generic query indicators; and wherein source routes of the external data sources include one or more of databases, API interfaces, JAR packages, KV texts and EXCEL files. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00045"> <pat:ClaimNumber>45< / pat:ClaimNumber> <pat:ClaimText>45. The apparatus of claim 44, wherein data source information of the databases includes services IPs, interfaces, and database names. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00046"> <pat:ClaimNumber>46< / pat:ClaimNumber> <pat:ClaimText>46. The apparatus of claim 44, wherein data source information of the API interfaces includes interface addresses, input parameter information, and return parameter information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00047"> <pat:ClaimNumber>47< / pat:ClaimNumber> <pat:ClaimText>47. The apparatus of claim 44, wherein data source information of the JAR packages includes JAR names, interface-type full paths, and method names. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00048"> <pat:ClaimNumber>48< / pat:ClaimNumber> <pat:ClaimText>48. The apparatus of any one of claims 38 to 47, wherein creating the table in which the general query indicators and the generic query indicators are contained in different areas comprises: using a visualization platform to set contents of the table as analysis fields, the general query indicators, and the generic query indicators, successively. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00049"> <pat:ClaimNumber>49< / pat:ClaimNumber> <pat:ClaimText>49. The apparatus of claim 48, wherein orientating the generic query indicators, to configure the calling mode to call the generic query indicators comprises: using a generic orientating module to orientate the calling mode of the generic query indicators and the corresponding generic query indicators, in which the generic query indicator and the calling mode are of one-to-one correspondence, and performing dimension mapping on the general query indicators and the analysis fields in the calling mode. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00050"> <pat:ClaimNumber>50< / pat:ClaimNumber> <pat:ClaimText>50. The apparatus of any one of claims 44 to 49, wherein making the data request based on the contents of the indicators in the table, to use the pre-configured calling mode to acquire the query data corresponding to the general query indicators and the generic query indicators from the data sources comprises: initiating a generic data request by a data-accessing module, according to the generic query indicators in the table, and indicator screening by a data routing module, using a corresponding calling mode to access the external data sources by way of one or more of the databases, the API interfaces, the JAR packages, the KV texts, and the EXCEL files to acquire the query data of the generic indicators; and initiating a general data request by the data-accessing module, according to the general query indicators in the table, and indicator screening by the data routing module, using the corresponding calling mode to acquire the query data of a general indicators from the internal data sources. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00051"> <pat:ClaimNumber>51< / pat:ClaimNumber> <pat:ClaimText>51. The apparatus of any one of claims 49 to 50, wherein summarizing and fusing the query data corresponding to the general query indicators and the generic query indicators, and feeding the summarized and fused query data back to the front end for visual display comprises: using a data-fusion module to summarize and fuse the query data of the generic indicators and the query data of the general indicators in the table according to dimensionally mapped analysis fields, and feeding back the summarized and fused data to the front-end for visual display. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00052"> <pat:ClaimNumber>52< / pat:ClaimNumber> <pat:ClaimText>52. The apparatus of any one of claims 38 to 51, further comprising lineage tracing of the general query indicators and the generic query indicators to their respective data sources. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00053"> <pat:ClaimNumber>53< / pat:ClaimNumber> <pat:ClaimText>53. The apparatus of any one of claims 38 to 52, wherein generic retrieval indicators are a series of indicator ranges only having indicator meanings but not supported by actual specifications and data sources, with orientation the specifications and actual data sources of these indicators deferred to the phase of creation of solid reports or to the phase of real- time analysis of data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00054"> <pat:ClaimNumber>54< / pat:ClaimNumber> <pat:ClaimText>54. The apparatus of claim 53, wherein the generic retrieval indicator is different from the general indicator for the generic indicator is defined without being bound to actual data sources. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00055"> <pat:ClaimNumber>55< / pat:ClaimNumber> <pat:ClaimText>55. The apparatus of claim 54, wherein created general sales indicators form a cluster of indicators having specific specifications, including an online sales amount, an off-line sales amount. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00056"> <pat:ClaimNumber>56< / pat:ClaimNumber> <pat:ClaimText>56. The apparatus of claim any one of claims 38 to 55, wherein the use of the generic query indicators, only one indicator, a sales amount indicator, has to be created. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00057"> <pat:ClaimNumber>57< / pat:ClaimNumber> <pat:ClaimText>57. The apparatus of any one of claims 38 to 56, wherein the generic query indicators are sub- indicators of the general query indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00058"> <pat:ClaimNumber>58< / pat:ClaimNumber> <pat:ClaimText>58. The apparatus of any one of claims 38 to 57, wherein the generic query indicators only contain descriptions about external contents including indicator names and indicator units, and have underlying business technical specifications that support data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00059"> <pat:ClaimNumber>59< / pat:ClaimNumber> <pat:ClaimText>59. The apparatus of any one of claims 38 to 58, wherein the generic query indicators refer to a set of indicators having similar meanings, including small-shop sales amount, the online shop sales amount, and cloud-shop sales amount, collectively called as the sales amounts. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00060"> <pat:ClaimNumber>60< / pat:ClaimNumber> <pat:ClaimText>60. The apparatus of any one of claims 38 to 59, wherein the derived generic query indicator defines calculation formulas among generic indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00061"> <pat:ClaimNumber>61< / pat:ClaimNumber> <pat:ClaimText>61. The apparatus of any one of claims 38 to 60, wherein with a data source defining module, a user defines one or more implementations including API interface of data, embedded JAR packages, KV texts, and databases into external data source information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00062"> <pat:ClaimNumber>62< / pat:ClaimNumber> <pat:ClaimText>62. The apparatus of claim 61, wherein the indicator defining module, the user adds new generic indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00063"> <pat:ClaimNumber>63< / pat:ClaimNumber> <pat:ClaimText>63. The apparatus of any one of claims 38 to 62, wherein a specific scene of data analysis, external data source information is orientated to designated generic indicator, wherein data query is made through data routing and implementing logic of a data-accessing module. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00064"> <pat:ClaimNumber>64< / pat:ClaimNumber> <pat:ClaimText>64. The apparatus of claim 61, wherein the data source defining module is primarily for defining external data source information, including services IPs, ports, database names, under the database type and interface addresses, input parameter information, return parameter information, under API interface, and JAR names, interface type full paths, method names, introduced under JAR packages. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00065"> <pat:ClaimNumber>65< / pat:ClaimNumber> <pat:ClaimText>65. The apparatus of any one of claims 38 to 64, wherein orientated contents include external data source codes, dimension-mapping KV combinations, and indicator-mapping KV combinations. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00066"> <pat:ClaimNumber>66< / pat:ClaimNumber> <pat:ClaimText>66. The apparatus of any one of claims 38 to 65, wherein is focused on rows of generic query indicator, but not generic indicators, wherein in one image, the generic query indicator generates multiple rows, and data sources or logics of the rows are different. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00067"> <pat:ClaimNumber>67< / pat:ClaimNumber> <pat:ClaimText>67. The apparatus of claim 50, wherein the data-accessing module is primarily for analyzing configuration information of generic indicator rows, and routing to different data channels according to the data source configured for the generic indicator rows, wherein the channels include external API interface, built-in, uploaded JAR packages, key-value pair documents. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00068"> <pat:ClaimNumber>68< / pat:ClaimNumber> <pat:ClaimText>68. The apparatus of any one of claims 38 to 67, wherein the user creates general query indicators, including total sales amount, based on an indicator model layer and an indicator acceleration layer. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00069"> <pat:ClaimNumber>69< / pat:ClaimNumber> <pat:ClaimText>69. The apparatus of any one of claims 38 to 68, wherein the user defines sub-sales amounts of the generic indicator at the indicator defining module, including online sales amount and off-line sales amount. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00070"> <pat:ClaimNumber>70< / pat:ClaimNumber> <pat:ClaimText>70. The apparatus of any one of claims 38 to 69, wherein the contents of the table include large sales region, total sales amount, online sales amount, and off-line sales amount successively. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00071"> <pat:ClaimNumber>71< / pat:ClaimNumber> <pat:ClaimText>71. The apparatus of claim 50, wherein the data routing module is performs indicator screening, and total sales amount is assigned to a data acceleration module to make a data request for the general indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00072"> <pat:ClaimNumber>72< / pat:ClaimNumber> <pat:ClaimText>72. The apparatus of any one of claims 38 to 71, wherein online sales amount and off-line sales amount are assigned to the data-accessing module. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00073"> <pat:ClaimNumber>73< / pat:ClaimNumber> <pat:ClaimText>73. The apparatus of any one of claims 38 to 72, wherein online sales amount and off-line sales amount are generic orientating indicators and are input in advance. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00074"> <pat:ClaimNumber>74< / pat:ClaimNumber> <pat:ClaimText>74. The apparatus of any one of claims 38 to 73, wherein the user uses an input button to define new contents for orientation. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00075"> <pat:ClaimNumber>75< / pat:ClaimNumber> <pat:ClaimText>75. A system comprising: an indicator creating unit, configured to create general query indicators and generic query indicators including using an indicator-defining module to define the general query indicators with normal specifications and defining the generic query indicators without actual business technical specifications, wherein the generic query indicators include content descriptions of indicator names and indicator units; a data source defining unit, configured to define data sources corresponding to the general query indicators and the generic query indicators; a table creating unit, configured to create a table in which the general query indicators and the generic query indicators are contained in different areas; a calling and configuring unit, configured to orientate the generic query indicators, to configure a calling mode to call the generic query indicators; a data-requesting unit, configured to, based on contents of the indicators in the table making a data request, to use the pre-configured calling mode to acquire query data corresponding to the general query indicators and the generic query indicators from the data sources; and a data fusing unit, configured to: summarize and fuse the query data corresponding to the general query indicators and the generic query indicators; and feed the summarized and fused query data back to a front end for displaying. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00076"> <pat:ClaimNumber>76< / pat:ClaimNumber> <pat:ClaimText>76. The system of claim 75, wherein one generic query indicator represents N general query indicators, where <semantics>N≥1<annotation encoding="application / x-tex">N \ge 1< / annotation>< / semantics>. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00077"> <pat:ClaimNumber>77< / pat:ClaimNumber> <pat:ClaimText>77. The system of any one of claims 75 to 76, wherein the generic query indicators are sub- indicators of the general query indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00078"> <pat:ClaimNumber>78< / pat:ClaimNumber> <pat:ClaimText>78. The system of any one of claims 75 to 77, wherein the general query indicators comprise a total sales amount. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00079"> <pat:ClaimNumber>79< / pat:ClaimNumber> <pat:ClaimText>79. The system of any one of claims 75 to 78, wherein the generic query indicators comprise an online sales amount and an off-line sales amount. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00080"> <pat:ClaimNumber>80< / pat:ClaimNumber> <pat:ClaimText>80. The system of any one of claims 75 to 78, wherein the generic query indicators comprise a calculation formula to determine a sum of one or more generic query indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00081"> <pat:ClaimNumber>81< / pat:ClaimNumber> <pat:ClaimText>81. The system of any one of claims 75 to 80, wherein defining the data sources corresponding to the general query indicators and the generic query indicators, respectively, comprises: using a data-source defining module to orientate internal data sources of the general query indicators and to orientate external data sources of the generic query indicators; and wherein source routes of the external data sources include one or more of databases, API interfaces, JAR packages, KV texts and EXCEL files. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00082"> <pat:ClaimNumber>82< / pat:ClaimNumber> <pat:ClaimText>82. The system of claim 81, wherein data source information of the databases includes services IPs, interfaces, and database names. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00083"> <pat:ClaimNumber>83< / pat:ClaimNumber> <pat:ClaimText>83. The system of claim 81, wherein data source information of the API interfaces includes interface addresses, input parameter information, and return parameter information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00084"> <pat:ClaimNumber>84< / pat:ClaimNumber> <pat:ClaimText>84. The system of claim 81, wherein data source information of the JAR packages includes JAR names, interface-type full paths, and method names. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00085"> <pat:ClaimNumber>85< / pat:ClaimNumber> <pat:ClaimText>85. The system of any one of claims 75 to 84, wherein creating the table in which the general query indicators and the generic query indicators are contained in different areas comprises: using a visualization platform to set contents of the table as analysis fields, the general query indicators, and the generic query indicators, successively. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00086"> <pat:ClaimNumber>86< / pat:ClaimNumber> <pat:ClaimText>86. The system of claim 85, wherein orientating the generic query indicators, to configure the calling mode to call the generic query indicators comprises: using a generic orientating module to orientate the calling mode of the generic query indicators and the corresponding generic query indicators, in which the generic query indicator and the calling mode are of one-to-one correspondence, and performing dimension mapping on the general query indicators and the analysis fields in the calling mode. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00087"> <pat:ClaimNumber>87< / pat:ClaimNumber> <pat:ClaimText>87. The system of any one of claims 81 to 86, wherein making the data request based on the contents of the indicators in the table, to use the pre-configured calling mode to acquire the query data corresponding to the general query indicators and the generic query indicators from the data sources comprises: initiating a generic data request by a data-accessing module, according to the generic query indicators in the table, and indicator screening by a data routing module, using a corresponding calling mode to access the external data sources by way of one or more of the databases, the API interfaces, the JAR packages, the KV texts, and the EXCEL files to acquire the query data of the generic indicators; and initiating a general data request by the data-accessing module, according to the general query indicators in the table, and indicator screening by the data routing module, using the corresponding calling mode to acquire the query data of a general indicators from the internal data sources. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00088"> <pat:ClaimNumber>88< / pat:ClaimNumber> <pat:ClaimText>88. The system of any one of claims 86 to 87, wherein summarizing and fusing the query data corresponding to the general query indicators and the generic query indicators, and feeding the summarized and fused query data back to the front end for visual display comprises: using a data-fusion module to summarize and fuse the query data of the generic indicators and the query data of the general indicators in the table according to dimensionally mapped analysis fields, and feeding back the summarized and fused data to the front-end for visual display. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00089"> <pat:ClaimNumber>89< / pat:ClaimNumber> <pat:ClaimText>89. The system of any one of claims 75 to 88, further comprising lineage tracing of the general query indicators and the generic query indicators to their respective data sources. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00090"> <pat:ClaimNumber>90< / pat:ClaimNumber> <pat:ClaimText>90. The system of any one of claims 75 to 89, wherein generic retrieval indicators are a series of indicator ranges only having indicator meanings but not supported by actual specifications and data sources, with orientation the specifications and actual data sources of these indicators deferred to the phase of creation of solid reports or to the phase of real- time analysis of data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00091"> <pat:ClaimNumber>91< / pat:ClaimNumber> <pat:ClaimText>91. The system of claim 90, wherein the generic retrieval indicator is different from the general indicator for the generic indicator is defined without being bound to actual data sources. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00092"> <pat:ClaimNumber>92< / pat:ClaimNumber> <pat:ClaimText>92. The system of claim 91, wherein created general sales indicators form a cluster of indicators having specific specifications, including an online sales amount, an off-line sales amount. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00093"> <pat:ClaimNumber>93< / pat:ClaimNumber> <pat:ClaimText>93. The system of claim any one of claims 75 to 92, wherein the use of the generic query indicators, only one indicator, a sales amount indicator, has to be created. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00094"> <pat:ClaimNumber>94< / pat:ClaimNumber> <pat:ClaimText>94. The system of any one of claims 75 to 93, wherein the generic query indicators are sub- indicators of the general query indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00095"> <pat:ClaimNumber>95< / pat:ClaimNumber> <pat:ClaimText>95. The system of any one of claims 75 to 94, wherein the generic query indicators only contain descriptions about external contents including indicator names and indicator units, and have underlying business technical specifications that support data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00096"> <pat:ClaimNumber>96< / pat:ClaimNumber> <pat:ClaimText>96. The system of any one of claims 75 to 95, wherein the generic query indicators refer to a set of indicators having similar meanings, including small-shop sales amount, the online shop sales amount, and cloud-shop sales amount, collectively called as the sales amounts. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00097"> <pat:ClaimNumber>97< / pat:ClaimNumber> <pat:ClaimText>97. The system of any one of claims 75 to 96, wherein the derived generic query indicator defines calculation formulas among generic indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00098"> <pat:ClaimNumber>98< / pat:ClaimNumber> <pat:ClaimText>98. The system of any one of claims 75 to 97, wherein with a data source defining module, a user defines one or more implementations including API interface of data, embedded JAR packages, KV texts, and databases into external data source information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00099"> <pat:ClaimNumber>99< / pat:ClaimNumber> <pat:ClaimText>99. The system of claim 98, wherein the indicator defining module, the user adds new generic indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00100"> <pat:ClaimNumber>100< / pat:ClaimNumber> <pat:ClaimText>100. The system of any one of claims 75 to 99, wherein a specific scene of data analysis, external data source information is orientated to designated generic indicator, wherein data query is made through data routing and implementing logic of a data-accessing module. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00101"> <pat:ClaimNumber>101< / pat:ClaimNumber> <pat:ClaimText>101. The system of claim 98, wherein the data source defining module is primarily for defining external data source information, including services IPs, ports, database names, under the database type and interface addresses, input parameter information, return parameter information, under API interface, and JAR names, interface type full paths, method names, introduced under JAR packages. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00102"> <pat:ClaimNumber>102< / pat:ClaimNumber> <pat:ClaimText>102. The system of any one of claims 75 to 101, wherein orientated contents include external data source codes, dimension-mapping KV combinations, and indicator-mapping KV combinations. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00103"> <pat:ClaimNumber>103< / pat:ClaimNumber> <pat:ClaimText>103. The system of any one of claims 75 to 102, wherein is focused on rows of generic query indicator, but not generic indicators, wherein in one image, the generic query indicator generates multiple rows, and data sources or logics of the rows are different. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00104"> <pat:ClaimNumber>104< / pat:ClaimNumber> <pat:ClaimText>104. The system of claim 87, wherein the data-accessing module is primarily for analyzing configuration information of generic indicator rows, and routing to different data channels according to the data source configured for the generic indicator rows, wherein the channels include external API interface, built-in, uploaded JAR packages, key-value pair documents. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00105"> <pat:ClaimNumber>105< / pat:ClaimNumber> <pat:ClaimText>105. The system of any one of claims 75 to 104, wherein the user creates general query indicators, including total sales amount, based on an indicator model layer and an indicator acceleration layer. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00106"> <pat:ClaimNumber>106< / pat:ClaimNumber> <pat:ClaimText>106. The system of any one of claims 75 to 105, wherein the user defines sub-sales amounts of the generic indicator at the indicator defining module, including online sales amount and off-line sales amount. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00107"> <pat:ClaimNumber>107< / pat:ClaimNumber> <pat:ClaimText>107. The system of any one of claims 75 to 106, wherein the contents of the table include large sales region, total sales amount, online sales amount, and off-line sales amount successively. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00108"> <pat:ClaimNumber>108< / pat:ClaimNumber> <pat:ClaimText>108. The system of claim 87, wherein the data routing module is performs indicator screening, and total sales amount is assigned to a data acceleration module to make a data request for the general indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00109"> <pat:ClaimNumber>109< / pat:ClaimNumber> <pat:ClaimText>109. The system of any one of claims 75 to 108, wherein online sales amount and off-line sales amount are assigned to the data-accessing module. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00110"> <pat:ClaimNumber>110< / pat:ClaimNumber> <pat:ClaimText>110. The system of any one of claims 75 to 109, wherein online sales amount and off-line sales amount are generic orientating indicators and are input in advance. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00111"> <pat:ClaimNumber>111< / pat:ClaimNumber> <pat:ClaimText>111. The system of any one of claims 75 to 110, wherein the user uses an input button to define new contents for orientation. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00112"> <pat:ClaimNumber>112< / pat:ClaimNumber> <pat:ClaimText>112. An electronic equipment comprising: one or more processors; a memory, associated with the one or more processors and used for storing a program instruction; the program instruction executed by the one or more processors configured to: create general query indicators and generic query indicators including using an indicator-defining module to define the general query indicators with normal specifications and defining the generic query indicators without actual business technical specifications, wherein the generic query indicators include content descriptions of indicator names and indicator units;; define data sources corresponding to the general query indicators and the generic query indicators, respectively; create a table in which the general query indicators and the generic query indicators are contained in different areas; orientate the generic query indicators, to configure a calling mode to call the generic query indicators; make a data request based on contents of the indicators in the table, to use the pre-configured calling mode to acquire query data corresponding to the general query indicators and the generic query indicators from the data sources; and summarize and fusing the query data corresponding to the general query indicators and the generic query indicators, and feeding the summarized and fused query data back to a front end for visual display. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00113"> <pat:ClaimNumber>113< / pat:ClaimNumber> <pat:ClaimText>113. The equipment of claim 112, wherein one generic query indicator represents N general query indicators, where <semantics>N≥1<annotation encoding="application / x-tex">N \ge 1< / annotation>< / semantics>. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00114"> <pat:ClaimNumber>114< / pat:ClaimNumber> <pat:ClaimText>114. The equipment of any one of claims 112 to 113, wherein the generic query indicators are sub-indicators of the general query indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00115"> <pat:ClaimNumber>115< / pat:ClaimNumber> <pat:ClaimText>115. The equipment of any one of claims 112 to 114, wherein the general query indicators comprise a total sales amount. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00116"> <pat:ClaimNumber>116< / pat:ClaimNumber> <pat:ClaimText>116. The equipment of any one of claims 112 to 115, wherein the generic query indicators comprise an online sales amount and an off-line sales amount. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00117"> <pat:ClaimNumber>117< / pat:ClaimNumber> <pat:ClaimText>117. The equipment of any one of claims 112 to 115, wherein the generic query indicators comprise a calculation formula to determine a sum of one or more generic query indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00118"> <pat:ClaimNumber>118< / pat:ClaimNumber> <pat:ClaimText>118. The equipment of any one of claims 112 to 117, wherein defining the data sources corresponding to the general query indicators and the generic query indicators, respectively, comprises: using a data-source defining module to orientate internal data sources of the general query indicators and to orientate external data sources of the generic query indicators; and wherein source routes of the external data sources include one or more of databases, API interfaces, JAR packages, KV texts and EXCEL files. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00119"> <pat:ClaimNumber>119< / pat:ClaimNumber> <pat:ClaimText>119. The equipment of claim 118, wherein data source information of the databases includes services IPs, interfaces, and database names. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00120"> <pat:ClaimNumber>120< / pat:ClaimNumber> <pat:ClaimText>120. The equipment of claim 118, wherein data source information of the API interfaces includes interface addresses, input parameter information, and return parameter information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00121"> <pat:ClaimNumber>121< / pat:ClaimNumber> <pat:ClaimText>121. The equipment of claim 118, wherein data source information of the JAR packages includes JAR names, interface-type full paths, and method names. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00122"> <pat:ClaimNumber>122< / pat:ClaimNumber> <pat:ClaimText>122. The equipment of any one of claims 112 to 121, wherein creating the table in which the general query indicators and the generic query indicators are contained in different areas comprises: using a visualization platform to set contents of the table as analysis fields, the general query indicators, and the generic query indicators, successively. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00123"> <pat:ClaimNumber>123< / pat:ClaimNumber> <pat:ClaimText>123. The equipment of claim 122, wherein orientating the generic query indicators, to configure the calling mode to call the generic query indicators comprises: using a generic orientating module to orientate the calling mode of the generic query indicators and the corresponding generic query indicators, in which the generic query indicator and the calling mode are of one-to-one correspondence, and performing dimension mapping on the general query indicators and the analysis fields in the calling mode. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00124"> <pat:ClaimNumber>124< / pat:ClaimNumber> <pat:ClaimText>124. The equipment of any one of claims 118 to 123, wherein making the data request based on the contents of the indicators in the table, to use the pre-configured calling mode to acquire the query data corresponding to the general query indicators and the generic query indicators from the data sources comprises: initiating a generic data request by a data-accessing module, according to the generic query indicators in the table, and indicator screening by a data routing module, using a corresponding calling mode to access the external data sources by way of one or more of the databases, the API interfaces, the JAR packages, the KV texts, and the EXCEL files to acquire the query data of the generic indicators; and initiating a general data request by the data-accessing module, according to the general query indicators in the table, and indicator screening by the data routing module, using the corresponding calling mode to acquire the query data of a general indicators from the internal data sources < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00125"> <pat:ClaimNumber>125< / pat:ClaimNumber> <pat:ClaimText>125. The equipment of any one of claims 123 to 124, wherein summarizing and fusing the query data corresponding to the general query indicators and the generic query indicators, and feeding the summarized and fused query data back to the front end for visual display comprises: using a data-fusion module to summarize and fuse the query data of the generic indicators and the query data of the general indicators in the table according to dimensionally mapped analysis fields, and feeding back the summarized and fused data to the front-end for visual display. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00126"> <pat:ClaimNumber>126< / pat:ClaimNumber> <pat:ClaimText>126. The equipment of any one of claims 112 to 125, further comprising lineage tracing of the general query indicators and the generic query indicators to their respective data sources. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00127"> <pat:ClaimNumber>127< / pat:ClaimNumber> <pat:ClaimText>127. The equipment of any one of claims 112 to 126, wherein generic retrieval indicators are a series of indicator ranges only having indicator meanings but not supported by actual specifications and data sources, with orientation the specifications and actual data sources of these indicators deferred to the phase of creation of solid reports or to the phase of real- time analysis of data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00128"> <pat:ClaimNumber>128< / pat:ClaimNumber> <pat:ClaimText>128. The equipment of claim 127, wherein the generic retrieval indicator is different from the general indicator for the generic indicator is defined without being bound to actual data sources. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00129"> <pat:ClaimNumber>129< / pat:ClaimNumber> <pat:ClaimText>129. The equipment of claim 128, wherein created general sales indicators form a cluster of indicators having specific specifications, including an online sales amount, an off-line sales amount. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00130"> <pat:ClaimNumber>130< / pat:ClaimNumber> <pat:ClaimText>130. The equipment of claim any one of claims 112 to 129, wherein the use of the generic query indicators, only one indicator, a sales amount indicator, has to be created. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00131"> <pat:ClaimNumber>131< / pat:ClaimNumber> <pat:ClaimText>131. The equipment of any one of claims 112 to 130, wherein the generic query indicators are sub-indicators of the general query indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00132"> <pat:ClaimNumber>132< / pat:ClaimNumber> <pat:ClaimText>132. The equipment of any one of claims 112 to 131, wherein the generic query indicators only contain descriptions about external contents including indicator names and indicator units, and have underlying business technical specifications that support data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00133"> <pat:ClaimNumber>133< / pat:ClaimNumber> <pat:ClaimText>133. The equipment of any one of claims 112 to 132, wherein the generic query indicators refer to a set of indicators having similar meanings, including small-shop sales amount, the online shop sales amount, and cloud-shop sales amount, collectively called as the sales amounts. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00134"> <pat:ClaimNumber>134< / pat:ClaimNumber> <pat:ClaimText>134. The equipment of any one of claims 112 to 133, wherein the derived generic query indicator defines calculation formulas among generic indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00135"> <pat:ClaimNumber>135< / pat:ClaimNumber> <pat:ClaimText>135. The equipment of any one of claims 112 to 134, wherein with a data source defining module, a user defines one or more implementations including API interface of data, embedded JAR packages, KV texts, and databases into external data source information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00136"> <pat:ClaimNumber>136< / pat:ClaimNumber> <pat:ClaimText>136. The equipment of claim 135, wherein the indicator defining module, the user adds new generic indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00137"> <pat:ClaimNumber>137< / pat:ClaimNumber> <pat:ClaimText>137. The equipment of any one of claims 112 to 136, wherein a specific scene of data analysis, external data source information is orientated to designated generic indicator, wherein data query is made through data routing and implementing logic of a data-accessing module. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00138"> <pat:ClaimNumber>138< / pat:ClaimNumber> <pat:ClaimText>138. The equipment of claim 135, wherein the data source defining module is primarily for defining external data source information, including services IPs, ports, database names, under the database type and interface addresses, input parameter information, return parameter information, under API interface, and JAR names, interface type full paths, method names, introduced under JAR packages. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00139"> <pat:ClaimNumber>139< / pat:ClaimNumber> <pat:ClaimText>139. The equipment of any one of claims 112 to 138, wherein orientated contents include external data source codes, dimension-mapping KV combinations, and indicator-mapping KV combinations. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00140"> <pat:ClaimNumber>140< / pat:ClaimNumber> <pat:ClaimText>140. The equipment of any one of claims 112 to 139, wherein is focused on rows of generic query indicator, but not generic indicators, wherein in one image, the generic query indicator generates multiple rows, and data sources or logics of the rows are different. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00141"> <pat:ClaimNumber>141< / pat:ClaimNumber> <pat:ClaimText>141. The equipment of claim 124, wherein the data-accessing module is primarily for analyzing configuration information of generic indicator rows, and routing to different data channels according to the data source configured for the generic indicator rows, wherein the channels include external API interface, built-in, uploaded JAR packages, key-value pair documents. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00142"> <pat:ClaimNumber>142< / pat:ClaimNumber> <pat:ClaimText>142. The equipment of any one of claims 112 to 141, wherein the user creates general query indicators, including total sales amount, based on an indicator model layer and an indicator acceleration layer. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00143"> <pat:ClaimNumber>143< / pat:ClaimNumber> <pat:ClaimText>143. The equipment of any one of claims 112 to 142, wherein the user defines sub-sales amounts of the generic indicator at the indicator defining module, including online sales amount and the off-line sales amount. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00144"> <pat:ClaimNumber>144< / pat:ClaimNumber> <pat:ClaimText>144. The equipment of any one of claims 112 to 143, wherein the contents of the table include large sales region, total sales amount, online sales amount, and off-line sales amount successively. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00145"> <pat:ClaimNumber>145< / pat:ClaimNumber> <pat:ClaimText>145. The equipment of claim 124, wherein the data routing module is performs indicator screening, and total sales amount is assigned to a data acceleration module to make a data request for the general indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00146"> <pat:ClaimNumber>146< / pat:ClaimNumber> <pat:ClaimText>146. The equipment of any one of claims 112 to 145, wherein online sales amount and off-line sales amount are assigned to the data-accessing module. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00147"> <pat:ClaimNumber>147< / pat:ClaimNumber> <pat:ClaimText>147. The equipment of any one of claims 112 to 146, wherein online sales amount and off-line sales amount are generic orientating indicators and are input in advance. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00148"> <pat:ClaimNumber>148< / pat:ClaimNumber> <pat:ClaimText>148. The equipment of any one of claims 112 to 147, wherein the user uses an input button to define new contents for orientation. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00149"> <pat:ClaimNumber>149< / pat:ClaimNumber> <pat:ClaimText>149. A computer readable storage medium having stored thereon computer executable instructions for execution by a computer configured to: create general query indicators and generic query indicators including using an indicator-defining module to define the general query indicators with normal specifications and defining the generic query indicators without actual business technical specifications, wherein the generic query indicators include content descriptions of indicator names and indicator units;; define data sources corresponding to the general query indicators and the generic query indicators, respectively; create a table in which the general query indicators and the generic query indicators are contained in different areas; orientate the generic query indicators, to configure a calling mode to call the generic query indicators; make a data request based on contents of the indicators in the table, to use the pre-configured calling mode to acquire query data corresponding to the general query indicators and the generic query indicators from the data sources; and summarize and fusing the query data corresponding to the general query indicators and the generic query indicators, and feeding the summarized and fused query data back to a front end for visual display. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00150"> <pat:ClaimNumber>150< / pat:ClaimNumber> <pat:ClaimText>150. The storage medium of claim 149, wherein one generic query indicator represents N general query indicators, where <semantics>N≥1<annotation encoding="application / x-tex">N \ge 1< / annotation>< / semantics>. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00151"> <pat:ClaimNumber>151< / pat:ClaimNumber> <pat:ClaimText>151. The storage medium of any one of claims 149 to 150, wherein the generic query indicators are sub-indicators of the general query indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00152"> <pat:ClaimNumber>152< / pat:ClaimNumber> <pat:ClaimText>152. The storage medium of any one of claims 149 to 151, wherein the general query indicators comprise a total sales amount. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00153"> <pat:ClaimNumber>153< / pat:ClaimNumber> <pat:ClaimText>153. The storage medium of any one of claims 149 to 152, wherein the generic query indicators comprise an online sales amount and an off-line sales amount. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00154"> <pat:ClaimNumber>154< / pat:ClaimNumber> <pat:ClaimText>154. The storage medium of any one of claims 149 to 152, wherein the generic query indicators comprise a calculation formula to determine a sum of one or more generic query indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00155"> <pat:ClaimNumber>155< / pat:ClaimNumber> <pat:ClaimText>155. The storage medium of any one of claims 149 to 154, wherein defining the data sources corresponding to the general query indicators and the generic query indicators, respectively, comprises: using a data-source defining module to orientate internal data sources of the general query indicators and to orientate external data sources of the generic query indicators; and wherein source routes of the external data sources include one or more of databases, API interfaces, JAR packages, KV texts and EXCEL files. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00156"> <pat:ClaimNumber>156< / pat:ClaimNumber> <pat:ClaimText>156. The storage medium of claim 155, wherein data source information of the databases includes services IPs, interfaces, and database names. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00157"> <pat:ClaimNumber>157< / pat:ClaimNumber> <pat:ClaimText>157. The storage medium of claim 155, wherein data source information of the API interfaces includes interface addresses, input parameter information, and return parameter information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00158"> <pat:ClaimNumber>158< / pat:ClaimNumber> <pat:ClaimText>158. The storage medium of claim 155, wherein data source information of the JAR packages includes JAR names, interface-type full paths, and method names. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00159"> <pat:ClaimNumber>159< / pat:ClaimNumber> <pat:ClaimText>159. The storage medium of any one of claims 149 to 158, wherein creating the table in which the general query indicators and the generic query indicators are contained in different areas comprises: using a visualization platform to set contents of the table as analysis fields, the general query indicators, and the generic query indicators, successively. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00160"> <pat:ClaimNumber>160< / pat:ClaimNumber> <pat:ClaimText>160. The storage medium of claim 159, wherein orientating the generic query indicators, to configure the calling mode to call the generic query indicators comprises: using a generic orientating module to orientate the calling mode of the generic query indicators and the corresponding generic query indicators, in which the generic query indicator and the calling mode are of one-to-one correspondence, and performing dimension mapping on the general query indicators and the analysis fields in the calling mode. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00161"> <pat:ClaimNumber>161< / pat:ClaimNumber> <pat:ClaimText>161. The storage medium of any one of claims 155 to 160, wherein making the data request based on the contents of the indicators in the table, to use the pre-configured calling mode to acquire the query data corresponding to the general query indicators and the generic query indicators from the data sources comprises: initiating a generic data request by a data-accessing module, according to the generic query indicators in the table, and indicator screening by a data routing module, using a corresponding calling mode to access the external data sources by way of one or more of the databases, the API interfaces, the JAR packages, the KV texts, and the EXCEL files to acquire the query data of the generic indicators; and initiating a general data request by the data-accessing module, according to the general query indicators in the table, and indicator screening by the data routing module, using the corresponding calling mode to acquire the query data of a general indicators from the internal data sources. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00162"> <pat:ClaimNumber>162< / pat:ClaimNumber> <pat:ClaimText>162. The storage medium of any one of claims 160 to 161, wherein summarizing and fusing the query data corresponding to the general query indicators and the generic query indicators, and feeding the summarized and fused query data back to the front end for visual display comprises: using a data-fusion module to summarize and fuse the query data of the generic indicators and the query data of the general indicators in the table according to dimensionally mapped analysis fields, and feeding back the summarized and fused data to the front-end for visual display. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00163"> <pat:ClaimNumber>163< / pat:ClaimNumber> <pat:ClaimText>163. The storage medium of any one of claims 149 to 162, further comprising lineage tracing of the general query indicators and the generic query indicators to their respective data sources. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00164"> <pat:ClaimNumber>164< / pat:ClaimNumber> <pat:ClaimText>164. The storage medium of any one of claims 149 to 163, wherein generic retrieval indicators are a series of indicator ranges only having indicator meanings but not supported by actual specifications and data sources, with orientation the specifications and actual data sources of these indicators deferred to the phase of creation of solid reports or to the phase of real- time analysis of data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00165"> <pat:ClaimNumber>165< / pat:ClaimNumber> <pat:ClaimText>165. The storage medium of claim 164, wherein the generic retrieval indicator is different from the general indicator for the generic indicator is defined without being bound to actual data sources. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00166"> <pat:ClaimNumber>166< / pat:ClaimNumber> <pat:ClaimText>166. The storage medium of claim 165, wherein created general sales indicators form a cluster of indicators having specific specifications, including an online sales amount, an off-line sales amount. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00167"> <pat:ClaimNumber>167< / pat:ClaimNumber> <pat:ClaimText>167. The storage medium of claim any one of claims 149 to 166, wherein the use of the generic query indicators, only one indicator, a sales amount indicator, has to be created. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00168"> <pat:ClaimNumber>168< / pat:ClaimNumber> <pat:ClaimText>168. The storage medium of any one of claims 149 to 167, wherein the generic query indicators are sub-indicators of the general query indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00169"> <pat:ClaimNumber>169< / pat:ClaimNumber> <pat:ClaimText>169. The storage medium of any one of claims 149 to 168, wherein the generic query indicators only contain descriptions about external contents including indicator names and indicator units, and have underlying business technical specifications that support data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00170"> <pat:ClaimNumber>170< / pat:ClaimNumber> <pat:ClaimText>170. The storage medium of any one of claims 149 to 169, wherein the generic query indicators refer to a set of indicators having similar meanings, including small-shop sales amount, the online shop sales amount, and cloud-shop sales amount, collectively called as the sales amounts. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00171"> <pat:ClaimNumber>171< / pat:ClaimNumber> <pat:ClaimText>171. The storage medium of any one of claims 149 to 170, wherein the derived generic query indicator defines calculation formulas among generic indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00172"> <pat:ClaimNumber>172< / pat:ClaimNumber> <pat:ClaimText>172. The storage medium of any one of claims 149 to 171, wherein with a data source defining module, a user defines one or more implementations including API interface of data, embedded JAR packages, KV texts, and databases into external data source information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00173"> <pat:ClaimNumber>173< / pat:ClaimNumber> <pat:ClaimText>173. The storage medium of claim 172, wherein the indicator defining module, the user adds new generic indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00174"> <pat:ClaimNumber>174< / pat:ClaimNumber> <pat:ClaimText>174. The storage medium of any one of claims 149 to 173, wherein a specific scene of data analysis, external data source information is orientated to designated generic indicator, wherein data query is made through data routing and implementing logic of a data- accessing module. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00175"> <pat:ClaimNumber>175< / pat:ClaimNumber> <pat:ClaimText>175. The storage medium of claim 172, wherein the data source defining module is primarily for defining external data source information, including services IPs, ports, database names, under the database type and interface addresses, input parameter information, return parameter information, under API interface, and JAR names, interface type full paths, method names, introduced under JAR packages. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00176"> <pat:ClaimNumber>176< / pat:ClaimNumber> <pat:ClaimText>176. The storage medium of any one of claims 149 to 175, wherein orientated contents include external data source codes, dimension-mapping KV combinations, and indicator-mapping KV combinations. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00177"> <pat:ClaimNumber>177< / pat:ClaimNumber> <pat:ClaimText>177. The storage medium of any one of claims 149 to 176, wherein is focused on rows of generic query indicator, but not generic indicators, wherein in one image, the generic query indicator generates multiple rows, and data sources or logics of the rows are different. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00178"> <pat:ClaimNumber>178< / pat:ClaimNumber> <pat:ClaimText>178. The storage medium of claim 161, wherein the data-accessing module is primarily for analyzing configuration information of generic indicator rows, and routing to different data channels according to the data source configured for the generic indicator rows, wherein the channels include external API interface, built-in, uploaded JAR packages, key-value pair documents. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00179"> <pat:ClaimNumber>179< / pat:ClaimNumber> <pat:ClaimText>179. The storage medium of any one of claims 149 to 178, wherein the user creates general query indicators, including total sales amount, based on an indicator model layer and an indicator acceleration layer. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00180"> <pat:ClaimNumber>180< / pat:ClaimNumber> <pat:ClaimText>180. The storage medium of any one of claims 149 to 179, wherein the user defines sub-sales amounts of the generic indicator at the indicator defining module, including online sales amount and off-line sales amount. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00181"> <pat:ClaimNumber>181< / pat:ClaimNumber> <pat:ClaimText>181. The storage medium of any one of claims 149 to 180, wherein the contents of the table include large sales region, total sales amount, online sales amount, and off-line sales amount successively. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00182"> <pat:ClaimNumber>182< / pat:ClaimNumber> <pat:ClaimText>182. The storage medium of claim 161, wherein the data routing module is performs indicator screening, and total sales amount is assigned to a data acceleration module to make a data request for the general indicators. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00183"> <pat:ClaimNumber>183< / pat:ClaimNumber> <pat:ClaimText>183. The storage medium of any one of claims 149 to 182, wherein online sales amount and off- line sales amount are assigned to the data-accessing module. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00184"> <pat:ClaimNumber>184< / pat:ClaimNumber> <pat:ClaimText>184. The storage medium of any one of claims 149 to 183, wherein online sales amount and off- line sales amount are generic orientating indicators and are input in advance. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00185"> <pat:ClaimNumber>185< / pat:ClaimNumber> <pat:ClaimText>185. The storage medium of any one of claims 149 to 184, wherein the user uses an input button to define new contents for orientation. < / pat:ClaimText> < / pat:Claim> < / pat:Claims>