Report generating method, device, electronic equipment, and computer-readable medium

Abstract

The present invention discloses a report generating method that comprises: receiving index configuration information input by a user at a web interface; establishing a first association relation of the index configuration information to a corresponding target data source; and generating the report through a preset model that is matched with the target data source on the basis of the index configuration information and the target data source. By establishing a first association relation of the index configuration information input by a user to a corresponding target data source, the present invention makes it possible to quickly obtain data from the corresponding data source, to avoid colossal amount of searches, to reduce computational amount, and to quicken response time; moreover, the report generating method according to the present application is a web browser data analysis product.

Description

REPORT GENERATING METHOD, DEVICE, ELECTRONIC EQUIPMENT, AND COMPUTER-READABLE MEDIUM BACKGROUND OF THE INVENTION Technical Field

[0001] The present invention relates to the field of data processing technology, and more particularly to a report generating method, and corresponding device, electronic equipment, and computer-readable medium. Description of Related Art

[0002] Business intelligence (BI) is a set of complete solving scheme employed to effectively integrate existing data in an enterprise, to quickly and accurately provide reports and propose decision bases, and to help the enterprise make advisable business operational decisions. In the traditional BI field, it is general for technical personnel to use professional BI software to construct relevant reports, but the construction period is long, total consumptions for both construction and adjustment are relatively large, the feedback period of the construction result is relatively long, and it is impossible to quickly respond to frontline requirements.

[0003] With the rapid development of the financial business, the business has expanded itself both in extent and in depth. Based on corresponding business scenarios, the requirements on data analyses have also been incessantly increasing; at the same time, due to increase in the amount of data analyses, the difficulty of analyses is increased, and a high demand is put on the construction timeliness for requirement landing by the business part.

[0004] Moreover, data analysis reports constructed by the traditional BI are confusing and not unified in indexes, support for the colossal amount of data is limited in strength, and response is extremely low or it is impossible to respond in the case there are excessive rows of data, or many analysis dimensions, or many dimension combinations, or dimensions of high cardinality.

[0005] To solve problems pending in the state of the art, embodiments of the present invention provide a report generating method, and corresponding device, electronic equipment, and computer-readable medium. The technical solutions are as follows.

[0006] According to the first aspect, there is provided a report generating method that comprises:

[0007] receiving index configuration information input by a user at a web interface;

[0008] establishing a first association relation of the index configuration information to a corresponding target data source; and

[0009] generating the report through a preset model that is matched with the target data source on the basis of the index configuration information and the target data source.

[0010] In a preferred mode of execution, the step of establishing a first association relation of the index configuration information to a corresponding target data source includes:

[0011] parsing the index configuration information to obtain at least one index name, at least one index dimension, and at least one preset model, wherein each preset model corresponds to the target data source;

[0012] establishing at least one associated group according to the at least one index name and the at least one index dimension, wherein index names and index dimensions included in any associated group are associated;

[0013] establishing a second association relation of any associated group to the preset model; and

[0014] establishing a first association relation of the associated group to the target data source on the basis of the second association relation.

[0015] In a preferred mode of execution, the step of establishing at least one associated group according to the at least one index name and the at least one index dimension, wherein index names and index dimensions included in any associated group are associated includes:

[0016] extracting an index code of each index name, and extracting a dimension code of each index dimension; and

[0017] establishing the at least one associated group according to a preconstructed correspondence relation between the index code and the dimension code.

[0018] In a preferred mode of execution, the step of establishing a second association relation of any associated group to the preset model includes:

[0019] parsing to obtain a model invoking parameter corresponding to the preset model on the basis of the associated group; and

[0020] matching a corresponding preset model and constructing a second association relation according to the model invoking parameter.

[0021] In a preferred mode of execution, the step of generating the report through a preset model that is matched with the target data source on the basis of the index configuration information and the target data source includes:

[0022] invoking the preset model that is matched with the target data source;

[0023] invoking target metadata from the target data source; and

[0024] generating the report through the preset model on the basis of the index configuration information and the target metadata.

[0025] In a preferred mode of execution, the target metadata includes target offline data, and the step of invoking target metadata from the target data source includes:

[0026] obtaining the target offline data from a preset external data warehouse according to a preset frequency and storing the same.

[0027] In a preferred mode of execution, the target metadata includes target real time data, and the step of invoking target metadata from the target data source includes:

[0028] obtaining in real time, from a message middleware, target real time data that is sent after FlinkTM performs real-time index calculation and is of a preset data format.

[0029] According to the second aspect, there is provided a report generating device that comprises:

[0030] a receiving module, for receiving index configuration information input by a user at a web interface;

[0031] an associating module, for establishing a first association relation of the index configuration information to a corresponding target data source; and

[0032] a generating module, for employing a preset model that is matched with the target data source to generate the report on the basis of the index configuration information and the target data source.

[0033] According to the third aspect, there is provided an electronic equipment that comprises:

[0034] one or more processor(s); and

[0035] a memory, associated with the one or more processor(s) and storing a program instruction that executes the method according to any one of the first aspect when it is read and executed by the one or more processor(s).

[0036] According to the fourth aspect, there is provided a computer-readable medium storing thereon a computer program that realizes the method according to any one of the first aspect when it is executed by a processor.

[0037] The technical solutions provided by the embodiments of the present invention bring about the following advantageous effects.

[0038] In the report generating method, and corresponding device, electronic equipment, and computer-readable medium provided by the embodiments of the present invention, by establishing a first association relation of the index configuration information input by a user to a corresponding target data source, it is made possible to quickly obtain data from the corresponding data source, to avoid colossal amount of searches, to reduce computational amount, and to shorten response time; moreover, the report generating method according to the present application is a web browser data analysis product, as compared with the prior-art scheme in which such products are directly connected to the target database, performance optimization of the target database is not affected; what is more important, the method is accessed to different data sources, provides services to the outside through a unified outlet, and is capable of effectively satisfying the requirement on the quick provision of unified service of heterogeneous source indexes. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] To more clearly describe the technical solutions in the embodiments of the present invention, drawings required to illustrate the embodiments will be briefly introduced below. Apparently, the drawings introduced below are merely directed to some embodiments of the present invention, while persons ordinarily skilled in the art may further acquire other drawings on the basis of these drawings without spending creative effort in the process.

[0040] Fig. 1 is a flowchart illustrating the report generating method provided by an embodiment of the present invention;

[0041] Fig. 2 is a view schematically illustrating the structure of the report generating device provided by an embodiment of the present invention; and

[0042] Fig. 3 is a view schematically illustrating the structure of a computer system provided by an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0043] To make more lucid and clear the objectives, technical solutions and advantages of the present invention, the technical solutions in the embodiments of the present invention will be clearly and comprehensively described below with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the embodiments as described are merely partial, rather than the entire, embodiments of the present invention. Any other embodiments makeable by persons ordinarily skilled in the art on the basis of the embodiments in the present invention without creative effort shall all fall within the protection scope of the present invention.

[0044] As noted in the Description of Related Art, corresponding to the development of businesses, BI data analysis requirements, processing amounts and difficulty are synchronously increased, and longer processing durations are usually required to satisfy the above requirements. At present, some analyzing engines (such real-time calculating engines as DruidTM, KylinTM, Presto / ImpalaTM, etc., and ElasticSearchTM) currently available on the market are more or less defective, and cannot satisfy all the above requirements at the same time. DruidTM employs the technique of pre-calculation, but cannot perform precise duplicate removal, there is certain error in count distinct, it is necessarily required that one dimension must be relevant to time, and the business is restricted. KylinTM employs the technique of pre-calculation, but it is so high in real timeliness, moreover, large resources are occupied when faced with a large-scale index system, and unduly long time is consumed in the pre-calculation. Such real-time calculating engines as Presto / ImpalaTM take relatively long response time in the real-time calculation, and the response time is even longer for complicated indexes, thereby making it impossible to satisfy the requirements for second-grade response. ElasticSearchTM cannot perform precise duplicate removal, there is precision error like DruidTM, and support for dimension combinations of high cardinality (high barrelage) is inferior.

[0045] To satisfy the requirement on timeliness of the business party, embodiments of the present invention provide a report generating method, and corresponding device, electronic equipment, and computer-readable medium capable of effectively solving the problem concerning timeliness in the BI field.

[0046] The technical solutions of the present application are described in greater detail below in conjunction with specific embodiments.

[0047] Embodiment 1

[0048] As shown in Fig. 1, this embodiment provides a report generating method for supplying decision bases in cooperation with a business party in the BI field. The method comprises the following steps.

[0049] S1 - receiving index configuration information input by a user at a web interface.

[0050] Specifically, the report generating method provided by this embodiment is established on the basis of a web browser, the user may directly access to a visualized design webpage through an ordinary web browser, and designs and inputs required index content at an index visualized interactor page, namely to input index content configuration information.

[0051] Exemplarily, in this embodiment, a visualized interactor is configured by configuring the index to perform human-machine interaction, index contents designed by the user are received, user operations are enabled by a visualized interface in which what you see is what you get, and design of the index and relevant cache configuration of the index are carried out. Moreover, the contents of cache configuration here include the circumstance of index definitions under various dimension combinations and corresponding caching methods.

[0052] Understandably, in order to cooperate with business requirements in the BI field, indexes are numerous and not unified, and this directly leads to the fact that the indexes are not conveniently used and even that index results are inconsistent. Indexes in this embodiment are classified according to different index dimensions.

[0053] Exemplarily, index dimensions are classified as follows: basic attributes include such information as names, codes, types, whether being public dimensions, parent dimensions, and states, etc.; business attributes include such information as business specifications and adjustment frequencies of specifications, etc.; technical attributes include such information as corresponding table names, technical specifications, fields corresponding to dimensions, fields corresponding to dimension values, and parent dimension fields, etc.; service attributes include such information as cache sources, and cache storage information, etc.

[0054] Exemplarily, based on the above classifications of index dimensions, indexes are classified as follows: basic attributes include such information as names, codes, types, and states, etc.; business attributes include such information as business specifications, adjustment frequencies of specifications, and sensitivity levels, etc.; technical attributes include such information as corresponding table names, technical specifications, and fields corresponding to indexes, etc.; service attributes include such information as cache sources, caching modes, and cache storage information, etc. What is additionally essential, the above contents are a result mapping generated under different dimension combinations, for instance, as regards the dimension of a certain statistic total value, when the dimension is respectively associated with a year dimension and a month dimension, the actual technical attributes and service attributes might be two groups of completely different information.

[0055] Accordingly, the index configuration information in this embodiment includes at least one dimension under the aforementioned different index dimensions. In this embodiment, mappings of plural groups of cache instances are generated through combined configurations of indexes and index dimensions, and contents with different features are respectively processed, so that problems based on colossal amount of data analyses, excessive amount of data analyzed, many analyzed dimensions, many combined dimensions, and dimensions with high cardinality are solved.

[0056] S2 - establishing a first association relation of the index configuration information to a corresponding target data source.

[0057] Specifically, step S2 includes the following.

[0058] S21 - parsing the index configuration information to obtain at least one index name, at least one index dimension, and at least one preset model, wherein each preset model corresponds to the target data source.

[0059] The preset model includes a massive amount batch index caching module, a precise duplicate-removal index caching module, a massive amount singular index caching module, and other modules self-defined according to functional requirements.

[0060] S22 - establishing at least one associated group according to the at least one index name and the at least one index dimension, wherein index names and index dimensions included in any associated group are associated.

[0061] Moreover, step S22 includes:

[0062] extracting an index code of each index name, and extracting a dimension code of each index dimension; and

[0063] establishing at least one associated group according to a preconstructed correspondence relation between the index code and the dimension code.

[0064] S23 - establishing a second association relation of any associated group to the preset model.

[0065] Specifically, step S23 includes:

[0066] parsing to obtain a model invoking parameter corresponding to the preset model on the basis of the associated group; and

[0067] matching a corresponding preset model and constructing a second association relation according to the model invoking parameter.

[0068] S24 - establishing a first association relation of the associated group to the target data source on the basis of the second association relation.

[0069] S3 - generating the report through a preset model that is matched with the target data source on the basis of the index configuration information and the target data source.

[0070] Specifically, step S3 includes the following.

[0071] S31 - invoking the preset model that is matched with the target data source.

[0072] S32 - invoking target metadata from the target data source.

[0073] In a preferred mode of execution, the target metadata includes at least one of target offline data and / or target real time data.

[0074] When the target metadata is target offline data, step S32 includes: obtaining the target offline data from a preset external data warehouse according to a preset frequency and storing the same.

[0075] When the target metadata is target real time data, step S32 includes:

[0076] obtaining in real time, from a message middleware, target real time data that is sent after FlinkTM performs real-time index calculation and is of a preset data format. The data format is for example table name + field names + instance data.

[0077] When data is written in, a primary key of the table is obtained according to metadata information of a data model, and data is "updated" or "inserted" according to the primary key, to avoid the recording of repetitive and invalid data; on the other hand, due to the timeliness of the message, when data is updated, the "latest" data is retained and disposed in the database while "old" data is directly discarded according to precise times in the data message.

[0078] S33 - generating the report on the basis of the index configuration information and the target metadata.

[0079] After the report has been generated, the method further comprises: outputting the generated report through a unified port to users to provide index service.

[0800] To further describe the report generating method, the following exemplary description is made in this embodiment in conjunction with a specific application scenario.

[0081] The report generating method manages and maintains indexes on the basis of an ordinary web browser, and execution is made on the basis of such functional modules as a model information administrator, an index configuration visualized interactor, an index parsing administrator, an index cache acceleration module set, and an index servicing module that are deployed on a server.

[0082] Specifically, the model information administrator is employed to administer model metadata, and to provide functions of enquiring and storing model metadata information. The model metadata includes name, code, state, and maintenance information of the model, and relevant information of all fields in the model, such as field names, field types, and field lengths, etc. On the basis thereof, the user can enquire all field information under the model by designating a unique identification of the model; by designating a unique identification of a certain field of the model, such information as the field name, field type, and field length of the field is enquired.

[0083] The index configuration visualized interactor is employed for human-machine interaction, and is specifically employed to receive index configuration information input by a user at a web interface to realize a visualized interface in which what you see is what you get for configuration by the user.

[0084] The index parsing administrator obtains the index configuration information configured by the user at the index configuration visualized interactor, and parses the same to obtain at least one index name, at least one index dimension, and at least one preset model, wherein each preset model corresponds to the target data source. At least one associated group is established according to at least one index name and at least one index dimension, and index names and index dimensions included in any associated group are associated. A second association relation of any associated group to the preset model is established, and a first association relation of the associated group to the target data source is established on the basis of the second association relation.

[0085] The index cache acceleration module set contains a set of index cache acceleration modules, the technical feature of each module is different from those of others, and service capability provided by each module is also different from those of others; the set incudes modules that at least support three scenarios, including the acceleration module of a massive amount batch index caching type, the acceleration module of a precise duplicate-removal index caching type, and the acceleration module of a massive amount singular index caching type. Scale-out is subsequently possible as required.

[0086] The acceleration module of a massive amount batch index caching type is a core and main module for storing common index cache acceleration data, most indexes can be disposed by means of this acceleration module, moreover, the indexes support reprocessing, such as summation and calculation of maximum value, etc., for supporting scenarios such as reports, etc., exemplarily, the objective is achieved by employing a PostgreSQL citus cluster, and such solving schemes as DruidTM can also be employed.

[0087] The acceleration module of a precise duplicate-removal index caching type is employed to store index cache acceleration data that should be precisely duplicate-removed (namely count distinct) within a dynamic range, few indexes can be disposed by means of this acceleration module if it is required so, exemplarily, the objective is achieved by employing the PostgreSQL citus cluster.

[8800] The acceleration module of a massive amount singular index type is employed to store massive amount of singular indexes, few indexes can be disposed by means of this acceleration module if it is required so, exemplarily, the objective is achieved by employing HBase.

[0089] The index servicing module provides the user end with unified index services, in this embodiment, batch index configuration information set up by users on the web browser can be received and processed in batches, and users are uniformly centralized through the index servicing module, so as to effectively solve the problem concerning heterogenous sources.

[0090] To sum it up, by establishing a first association relation of the index configuration information input by a user to a corresponding target data source, the report generating method provided by this embodiment makes it possible to quickly obtain data from the corresponding data source, to avoid colossal amount of searches, to reduce computational amount, and to shorten response time; moreover, the report generating method according to the present application is a web browser data analysis product, as compared with the prior-art scheme in which such products are directly connected to the target database, performance optimization of the target database is not affected.

[0091] Embodiment 2

[0092] To execute the report generating method in Embodiment 1, this embodiment provides a report generating device corresponding thereto, as shown in Fig. 2, the device comprises:

[0093] a receiving module, for receiving index configuration information input by a user at a web interface;

[0094] an associating module, for establishing a first association relation of the index configuration information to a corresponding target data source;

[0095] the associating module includes:

[0096] a parsing unit, for parsing the index configuration information to obtain at least one index name, at least one index dimension, and at least one preset model, wherein each preset model corresponds to the target data source;

[0097] a constructing unit, for establishing at least one associated group according to the at least one index name and the at least one index dimension, wherein index names and index dimensions included in any associated group are associated;

[0098] the constructing unit is further employed for extracting an index code of each index name, and extracting a dimension code of each index dimension; and establishing the at least one associated group according to a preconstructed correspondence relation between the index code and the dimension code;

[0099] a first associating unit, for establishing a second association relation of any associated group to the preset model;

[0100] the first associating unit is further employed for parsing to obtain a model invoking parameter corresponding to the preset model on the basis of the associated group; and matching a corresponding preset model and constructing a second association relation according to the model invoking parameter;

[0101] a second associating unit, for establishing a first association relation of the associated group to the target data source on the basis of the second association relation;

[0102] a generating module, for generating the report through a preset model that is matched with the target data source on the basis of the index configuration information and the target data source. The generating module includes:

[0103] a first invoking unit, for invoking the preset model that is matched with the target data source;

[0104] a second invoking unit, for invoking target metadata from the target data source; and

[0105] a generating unit, for generating the report through the preset model on the basis of the index configuration information and the target metadata.

[0106] The target metadata includes target offline data, and the second invoking unit is employed for obtaining the target offline data from a preset external data warehouse according to a preset frequency and storing the same.

[0107] The target metadata includes target real time data, and the second invoking unit is employed for obtaining in real time, from a message middleware, target real time data that is sent after FlinkTM performs real-time index calculation and is of a preset data format.

[0108] As should be noted, when the report generating device provided by the aforementioned embodiment triggers a report generating business, the division into the aforementioned various functional modules is merely by way of example, while it is possible, in actual application, to base on requirements to assign the functions to different functional modules for completion, that is to say, to divide the internal structure of the device into different functional modules to complete the entire or partial functions described above. In addition, the report generating device provided by the aforementioned embodiment pertains to the same conception as the report generating method provided by the method embodiment, that is to say, the device is based on the method <semantics>−<annotation encoding="application / x-tex">-< / annotation>< / semantics> see the corresponding method embodiment for its specific realization process, while no repetition will be made in this context.

[0109] In addition, corresponding to the aforementioned report generating method and device, this embodiment further provides an electronic equipment that comprises:

[0110] one or more processor(s); and

[0111] a memory, associated with the one or more processor(s) and storing a program instruction that executes the report generating method disclosed by the foregoing embodiment when it is read and executed by the one or more processor(s).

[0112] Fig. 3 exemplarily illustrates the framework of a computer system that can specifically include a processor 310, a video display adapter 311, a magnetic disk driver 312, an input / output interface 313, a network interface 314, and a memory 320. The processor 310, the video display adapter 311, the magnetic disk driver 312, the input / output interface 313, the network interface 314, and the memory 320 can be communicably connected with one another via a communication bus 330.

[0113] The processor 310 can be embodied as a general CPU (Central Processing Unit), a microprocessor, an ASIC (Application Specific Integrated Circuit), or one or more integrated circuit(s) for executing relevant program(s) to realize the technical solutions provided by the present application.

[0114] The memory 320 can be embodied in such a form as an ROM (Read Only Memory), an RAM (Random Access Memory), a static storage device, or a dynamic storage device. The memory 320 can store an operating system 321 for controlling the running of an electronic equipment 300, and a basic input / output system (BIOS) for controlling lower-level operations of the electronic equipment 300. In addition, the memory 320 can also store a web browser 323, a data storage management system 324, and an equipment identification information processing system 325, etc. The equipment identification information processing system 325 can be an application program that specifically realizes the aforementioned various step operations in the embodiments of the present application. To sum it up, when the technical solutions provided by the present application are to be realized via software or firmware, the relevant program codes are stored in the memory 320, and invoked and executed by the processor 310.

[0115] The input / output interface 313 is employed to connect with an input / output module to realize input and output of information. The input / output module can be equipped in the device as a component part (not shown in the drawings), and can also be externally connected with the device to provide corresponding functions. The input means can include a keyboard, a mouse, a touch screen, a microphone, and various sensors etc., and the output means can include a display screen, a loudspeaker, a vibrator, an indicator light etc.

[0116] The network interface 314 is employed to connect to a communication module (not shown in the drawings) to realize intercommunication between the current device and other devices. The communication module can realize communication in a wired mode (via USB, network cable, for example) or in a wireless mode (via mobile network, WIFI, Bluetooth, etc.).

[0117] The bus 330 includes a passageway transmitting information between various component parts of the equipment (such as the processor 310, the video display adapter 311, the magnetic disk driver 312, the input / output interface 313, the network interface 314, and the memory 320).

[0118] Additionally, the electronic equipment 300 may further obtain information of specific collection conditions from a virtual resource object collection condition information database for judgment on conditions, and so on.

[0119] As should be noted, although merely the processor 310, the video display adapter 311, the magnetic disk driver 312, the input / output interface 313, the network interface 314, the memory 320, and the bus 330 are illustrated for the aforementioned equipment, the equipment may further include other component parts prerequisite for realizing normal running during specific implementation. In addition, as can be understood by persons skilled in the art, the aforementioned device may as well only include component parts necessary for realizing the solutions of the present application, without including the entire component parts as illustrated.

[0120] Particularly, according to the embodiments of the current application, the processes described above with reference to flowcharts can be realized as computer software programs. For instance, embodiments of the present application include a computer program product that includes a computer program borne on a computer-readable medium, and the computer program contains program codes for executing the methods shown in the flowcharts. In such an embodiment, the computer program can be downloaded from the network and installed through a communication device, or installed from a storage device, or installed from an ROM. When the computer program is executed by a processor, it executes the aforementioned functions defined in the methods of the embodiments of the present application.

[0121] As should be noted, the computer-readable medium recited in the embodiments of the present application can be a computer-readable signal medium or a computer-readable storage medium or a random combination of the two. The computer-readable storage medium can for example be, but is not limited to be, an electric, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or component, or any combination of the above. A more specific example of the computer-readable storage medium can include, but is not limited to include, an electrically connectible, portable computer magnetic disk, a hard disk, a random-access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact magnetic disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device having one or more conducting wire(s), or any suitable combination of the above. In the embodiments of the present application, the computer-readable storage medium can be any tangible medium containing or storing a program usable by or in combination with an instruction executing system, device, or component. Moreover, in the embodiments of the present application, the computer-readable signal medium can include a data signal transmitted in a baseband or as part of a carrier wave, in which data signal are borne computer-readable program codes. The data signal thusly propagated can be embodied in plural forms, including, but not limited to, an electromagnetic signal, an optical signal, or any suitable combination thereof. The computer-readable signal medium can further be any other computer- readable medium than the computer-readable storage medium, and the computer-readable signal medium can transmit, propagate, or convey programs for use by or in combination with an instruction executing system, device, or component. The program codes contained in the computer-readable medium can be transmitted via any suitable medium, including, but not limited to, an electric wire, an optical fiber, radio frequency (RF) etc., or any suitable combination of the above.

[0122] The computer-readable medium can be either contained in the server, or independent of, not installed in the server. The computer-readable medium carries therewith one or more program(s), when the one or more program(s) is / are executed by the server, the server is enabled: to respond to the inactivated peripheral mode of the terminal as detected to obtain frame rate applied to the terminal; to judge whether the user is obtaining screen information of the terminal when the frame rate satisfies a screen resting condition; and to control the screen to enter an immediately darkening mode in response to a judging result that the user has not obtained the screen information.

[0123] One or more programming language(s) or a combination thereof can be employed to write the computer program codes for executing the operations of the embodiments of the present application, the programming language(s) include(s) such an object-oriented programming language as Java, Smalltalk, C++, and further include(s) such a conventional procedural programming language as "C" language or a similar programming language. The program codes can be entirely executed on a user computer, partly executed on a user computer, executed as an independent software package, partly executed on a user computer and partly executed on a remote computer, or entirely executed on a remote computer or a server. In the case a remote computer is involved, the remote computer can be connected to the user computer via a randomly typed network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (for example, internet connection can be supplied by an internet service provider).

[0124] The various embodiments are progressively described in the Description, identical or similar sections among the various embodiments can be inferred from one another, and each embodiment stresses what is different from other embodiments. Particularly, with respect to the system or system embodiment, since it is essentially similar to the method embodiment, its description is relatively simple, and the relevant sections thereof can be inferred from the corresponding sections of the method embodiment. The system or system embodiment as described above is merely exemplary in nature, units therein described as separate parts can be or may not be physically separate, parts displayed as units can be or may not be physical units, that is to say, they can be located in a single site, or distributed over a plurality of network units. It is possible to base on practical requirements to select partial modules or the entire modules to realize the objectives of the embodied solutions. It is understandable and implementable by persons ordinarily skilled in the art without spending creative effort in the process.

[0125] The terminal equipment identification information processing method, and the corresponding device, and electronic equipment provided by the present application have been described in detail above, and concrete examples are used in this paper to enunciate the principles and modes of execution of the present application; the descriptions of the foregoing embodiments are merely meant to help understand the methods and kernel conception of the present application; at the same time, persons ordinarily skilled in the art may make various modifications both in terms of the specific modes of execution and the ranges of application in accordance with the conception of the present application. In summary, the contents of this Description shall not be understood to restrict the present application.

[0126] All the aforementioned optional technical solutions are randomly combinable to form optional embodiments of the present invention, to which no repetition is redundantly made on a one-by-one basis. The above is merely directed to preferred embodiments of the present invention, and is not meant to restrict the present invention. Any amendment, equivalent replacement, and improvement makeable within the spirit and principle of the present invention shall all be covered by the protection scope of the present invention.

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: receiving index configuration information input by a user at a web interface, wherein the index configuration information is designed by the user; establishing a first association relation of the index configuration information to a target data source including: parsing the index configuration information to obtain at least one index name, at least one index dimension, and at least one preset model, wherein the preset model corresponds to the target data source and wherein the index dimensions are classified as one or more of basic attributes, business attributes, technical attributes and service attributes; establishing at least one associated group according to the at least one index name and the at least one index dimension, wherein the index names and the index dimensions included in the associated group are associated; establishing a second association relation of the associated group to the preset model; and establishing the first association relation of the associated group to the target data source based on the second association relation; and generating a report through the preset model that is matched with the target data source based on the index configuration information and the target data source, outputting the report to the user. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00002"> <pat:ClaimNumber>2< / pat:ClaimNumber> <pat:ClaimText>2. The method of claim 1, wherein establishing at least one associated group according to the at least one index name and the at least one index dimension, wherein the index names and the index dimensions included in the associated group are associated comprises: extracting an index code of the index name; extracting a dimension code of the index dimension; and establishing at least one associated group according to a preconstructed correspondence relation between the index code and the dimension code. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00003"> <pat:ClaimNumber>3< / pat:ClaimNumber> <pat:ClaimText>3. The method of claim 1, wherein establishing the second association relation of the associated group to the preset model comprises: parsing to obtain a model invoking parameter corresponding to the preset model based on the associated group; and matching the preset model and constructing the second association relation according to the model invoking parameter. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00004"> <pat:ClaimNumber>4< / pat:ClaimNumber> <pat:ClaimText>4. The method of claim 3, wherein generating the report through the preset model that is matched with the target data source based on the index configuration information and the target data source comprises: invoking the preset model that is matched with the target data source; invoking target metadata from the target data source; and generating the report through the preset model that is matched with the target data source based on the index configuration information and the target metadata. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00005"> <pat:ClaimNumber>5< / pat:ClaimNumber> <pat:ClaimText>5. The method of claim 4, wherein the target metadata includes target offline data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00006"> <pat:ClaimNumber>6< / pat:ClaimNumber> <pat:ClaimText>6. The method of claim 5, wherein invoking the target metadata from the target data source comprises: obtaining the target offline data from a preset external data warehouse according to a preset frequency; and storing the target offline data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00007"> <pat:ClaimNumber>7< / pat:ClaimNumber> <pat:ClaimText>7. The method of claim 4, wherein the target metadata includes target real time data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00008"> <pat:ClaimNumber>8< / pat:ClaimNumber> <pat:ClaimText>8. The method of claim 7, wherein invoking the target metadata from the target data source comprises: obtaining in real time, from a message middleware, target real time data that is sent after performing real-time index calculation and is of a preset data format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00009"> <pat:ClaimNumber>9< / pat:ClaimNumber> <pat:ClaimText>9. The method of any one of claims 1 to 8, further comprising outputting the report through a unified port to the user to provide index service. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00010"> <pat:ClaimNumber>10< / pat:ClaimNumber> <pat:ClaimText>10. The method of any one of claims 1 to 9, wherein the user directly accesses a visualized design webpage through an web browser, and designs and inputs required index content at an index visualized interactor page, to input index content configuration information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00011"> <pat:ClaimNumber>11< / pat:ClaimNumber> <pat:ClaimText>11. The method of claim 10, wherein the index visualized interactor is configured by configuring an index to perform human-machine interaction, wherein the index contents designed by the user are received. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00012"> <pat:ClaimNumber>12< / pat:ClaimNumber> <pat:ClaimText>12. The method of any one of claims 1 to 11, wherein user operations are enabled by a visualized interface and design of the index and relevant cache configuration of the index are carried out. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00013"> <pat:ClaimNumber>13< / pat:ClaimNumber> <pat:ClaimText>13. The method of claim 12, wherein contents of the cache configuration includes circumstance of index definitions under dimension combinations and corresponding caching methods. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00014"> <pat:ClaimNumber>14< / pat:ClaimNumber> <pat:ClaimText>14. The method of any one of claims 1 to 13, wherein indexes are classified according to the index dimensions. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00015"> <pat:ClaimNumber>15< / pat:ClaimNumber> <pat:ClaimText>15. The method of any one of claims 1 to 14, wherein the index dimensions are classified as the basic attributes including names, codes, types, being public dimensions, parent dimensions, and states. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00016"> <pat:ClaimNumber>16< / pat:ClaimNumber> <pat:ClaimText>16. The method of any one of claims 1 to 15, wherein the index dimensions are classified as the business attributes including business specifications, adjustment frequencies of specifications and sensitivity levels. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00017"> <pat:ClaimNumber>17< / pat:ClaimNumber> <pat:ClaimText>17. The method of any one of claims 1 to 16, wherein the index dimensions are classified as the technical attributes including table names, technical specifications, fields corresponding to dimensions, fields corresponding to dimension values, and parent dimension fields. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00018"> <pat:ClaimNumber>18< / pat:ClaimNumber> <pat:ClaimText>18. The method of any one of claims 1 to 17, wherein the index dimensions are classified as the service attributes including cache sources, caching modes, and cache storage information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00019"> <pat:ClaimNumber>19< / pat:ClaimNumber> <pat:ClaimText>19. The method of any one of claims 1 to 18, wherein the index configuration information includes at least one dimension of the index dimensions. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00020"> <pat:ClaimNumber>20< / pat:ClaimNumber> <pat:ClaimText>20. The method of any one of claims 1 to 19, wherein mappings of plural groups of cache instances are generated through combined configurations of the indexes and the index dimensions, and contents with different features are respectively processed. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00021"> <pat:ClaimNumber>21< / pat:ClaimNumber> <pat:ClaimText>21. The method of any one of claims 1 to 20, wherein the preset model includes, one or more of, a massive amount batch index caching module, a precise duplicate-removal index caching module, a massive amount singular index caching module. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00022"> <pat:ClaimNumber>22< / pat:ClaimNumber> <pat:ClaimText>22. The method of any one of claims 1 to 21, wherein the preset data format includes table name + field names + instance data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00023"> <pat:ClaimNumber>23< / pat:ClaimNumber> <pat:ClaimText>23. The method of any one of claims 1 to 22, is executed based on functional modules including a model information administrator, an index configuration visualized interactor, an index parsing administrator, an index cache acceleration module set, and an index servicing module are deployed on a server. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00024"> <pat:ClaimNumber>24< / pat:ClaimNumber> <pat:ClaimText>24. The method of claim 23, wherein the model information administrator administers model metadata, and to provide functions of enquiring and storing model metadata information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00025"> <pat:ClaimNumber>25< / pat:ClaimNumber> <pat:ClaimText>25. The method of claim 24, wherein the model metadata includes the name, the code, the state, and maintenance information of the model, and relevant information of the fields in the model, including the field names, field types, and field lengths. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00026"> <pat:ClaimNumber>26< / pat:ClaimNumber> <pat:ClaimText>26. The method of any one of claims 23 to 25, wherein the index configuration visualized interactor is for human-machine interaction, and to receive the index configuration information input by the user at the web interface to realize the visualized interface for configuration by the user. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00027"> <pat:ClaimNumber>27< / pat:ClaimNumber> <pat:ClaimText>27. The method of any one of claims 23 to 26, wherein the index parsing administrator obtains the index configuration information configured by the user at the index configuration visualized interactor, and parses the index configuration information to obtain at least one index name, at least one index dimension, and at least one preset model, wherein the preset model corresponds to the target data source. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00028"> <pat:ClaimNumber>28< / pat:ClaimNumber> <pat:ClaimText>28. The method of any one of claims 23 to 27, wherein the index cache acceleration module set contains a set of index cache acceleration modules, wherein the set incudes modules support three scenarios, including an acceleration module of massive amount batch index caching type, the acceleration module of the precise duplicate-removal index caching type, and the acceleration module of the massive amount singular index caching type. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00029"> <pat:ClaimNumber>29< / pat:ClaimNumber> <pat:ClaimText>29. The method of any one of claims 23 to 28, wherein the acceleration module of the massive amount batch index caching type is a core and main module for storing common index cache acceleration data, wherein most indexes are disposed by means of this acceleration module. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00030"> <pat:ClaimNumber>30< / pat:ClaimNumber> <pat:ClaimText>30. The method of any one of claims 23 to 29, wherein the indexes support reprocessing, including summation and calculation of maximum value. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00031"> <pat:ClaimNumber>31< / pat:ClaimNumber> <pat:ClaimText>31. The method of any one of claims 23 to 30, wherein a PostgreSQLTM citus cluster, and / or DruidTM is implemented. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00032"> <pat:ClaimNumber>32< / pat:ClaimNumber> <pat:ClaimText>32. The method of any one of claims 23 to 31, wherein the acceleration module of a precise duplicate-removal index caching type stores index cache acceleration data precisely duplicate- removed within a dynamic range, or by employing the PostgreSQLTM citus cluster. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00033"> <pat:ClaimNumber>33< / pat:ClaimNumber> <pat:ClaimText>33. The method of any one of claims 23 to 32, wherein the acceleration module of a massive amount singular index type stores massive amount of singular indexes, or by employing HBase. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00034"> <pat:ClaimNumber>34< / pat:ClaimNumber> <pat:ClaimText>34. The method of any one of claims 23 to 33, wherein the index servicing module provides the user with unified index services, batch index configuration information set up by the user on the web browser is received and processed in batches, and users are uniformly centralized through the index servicing module. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00035"> <pat:ClaimNumber>35< / pat:ClaimNumber> <pat:ClaimText>35. A device comprising: a receiving module, configured to receive index configuration information input by a user at a web interface wherein the index configuration information is designed by the user; an associating module, configured to establish a first association relation of the index configuration information to a target data source, comprising: a parsing unit configured to parse the index configuration information to obtain at least one index name, at least one index dimension, and at least one preset model, wherein the preset model corresponds to the target data source and wherein the index dimensions are classified as one or more of basic attributes, business attributes, technical attributes and service attributes; a constructing unit configured to establish at least one associated group according to at least one index name and at least one index dimension, wherein the index names and the index dimensions included in any associated group are associated; a first associating unit configured to establish a second association relation of any associated group to the preset model; and a second associating unit, configured to establish the first association relation of the associated group to the target data source based on the second association relation; and a generating module, configured to generate a report through the preset model that is matched with the target data source based on the index configuration information and the target data source outputting the report to the user. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00036"> <pat:ClaimNumber>36< / pat:ClaimNumber> <pat:ClaimText>36. The device of claim 35, wherein the constructing unit is further configured to: extract an index code of the index name; extract a dimension code of the index dimension; and establish at least one associated group according to a preconstructed correspondence relation between the index code and the dimension code. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00037"> <pat:ClaimNumber>37< / pat:ClaimNumber> <pat:ClaimText>37. The device of claim 36, wherein the first associating unit is further configured to: parse to obtain a model invoking parameter corresponding to the preset model based on the associated group; match the preset model; and construct the second association relation according to the model invoking parameter. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00038"> <pat:ClaimNumber>38< / pat:ClaimNumber> <pat:ClaimText>38. The device of claim 37, wherein generating module comprises: a first invoking unit configured to invoke the preset model that is matched with the target data source; a second invoking unit configured to invoke target metadata from the target data source; and a generating unit configured to generate the report through the preset model that is matched with the target data source based on the index configuration information and the target metadata. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00039"> <pat:ClaimNumber>39< / pat:ClaimNumber> <pat:ClaimText>39. The device of claim 38, wherein the target metadata includes target offline data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00040"> <pat:ClaimNumber>40< / pat:ClaimNumber> <pat:ClaimText>40. The device of claim 39, wherein the second invoking unit is configured to: obtain the target offline data from a preset external data warehouse according to a preset frequency; and store the target offline data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00041"> <pat:ClaimNumber>41< / pat:ClaimNumber> <pat:ClaimText>41. The device of claim 38, wherein the target metadata includes target real time data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00042"> <pat:ClaimNumber>42< / pat:ClaimNumber> <pat:ClaimText>42. The device of claim 41, wherein the second invoking unit is further configured to: obtain in real time, from a message middleware, the target real time data that is sent after performing real-time index calculation and is of a preset data format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00043"> <pat:ClaimNumber>43< / pat:ClaimNumber> <pat:ClaimText>43. The device of any one of claims 35 to 42, further comprising outputting the report through a unified port to the user to provide index service. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00044"> <pat:ClaimNumber>44< / pat:ClaimNumber> <pat:ClaimText>44. The device of any one of claims 35 to 43, wherein the user directly accesses a visualized design webpage through an web browser, and designs and inputs required index content at an index visualized interactor page, to input index content configuration information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00045"> <pat:ClaimNumber>45< / pat:ClaimNumber> <pat:ClaimText>45. The device of claim 44, wherein index visualized interactor is configured by configuring an index to perform human-machine interaction, wherein the index contents designed by the user are received. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00046"> <pat:ClaimNumber>46< / pat:ClaimNumber> <pat:ClaimText>46. The device of any one of claims 35 to 45, wherein user operations are enabled by a visualized interface and design of the index and relevant cache configuration of the index are carried out. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00047"> <pat:ClaimNumber>47< / pat:ClaimNumber> <pat:ClaimText>47. The device of claim 46, wherein contents of the cache configuration includes circumstance of index definitions under dimension combinations and corresponding caching methods. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00048"> <pat:ClaimNumber>48< / pat:ClaimNumber> <pat:ClaimText>48. The device of any one of claims 35 to 47, wherein indexes are classified according to the index dimensions. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00049"> <pat:ClaimNumber>49< / pat:ClaimNumber> <pat:ClaimText>49. The device of any one of claims 35 to 48, wherein the index dimensions are classified as the basic attributes including names, codes, types, being public dimensions, parent dimensions, and states. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00050"> <pat:ClaimNumber>50< / pat:ClaimNumber> <pat:ClaimText>50. The device of any one of claims 35 to 49, wherein the index dimensions are classified as the business attributes including business specifications, adjustment frequencies of specifications and sensitivity levels. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00051"> <pat:ClaimNumber>51< / pat:ClaimNumber> <pat:ClaimText>51. The device of any one of claims 35 to 50, wherein the index dimensions are classified as the technical attributes including table names, technical specifications, fields corresponding to dimensions, fields corresponding to dimension values, and parent dimension fields. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00052"> <pat:ClaimNumber>52< / pat:ClaimNumber> <pat:ClaimText>52. The device of any one of claims 35 to 51, wherein the index dimensions are classified as the service attributes including cache sources, caching modes, and cache storage information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00053"> <pat:ClaimNumber>53< / pat:ClaimNumber> <pat:ClaimText>53. The device of any one of claims 35 to 52, wherein the index configuration information includes at least one dimension of the index dimensions. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00054"> <pat:ClaimNumber>54< / pat:ClaimNumber> <pat:ClaimText>54. The device of any one of claims 35 to 53, wherein mappings of plural groups of cache instances are generated through combined configurations of the indexes and the index dimensions, and contents with different features are respectively processed. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00055"> <pat:ClaimNumber>55< / pat:ClaimNumber> <pat:ClaimText>55. The device of any one of claims 35 to 54, wherein the preset model includes, one or more of, a massive amount batch index caching module, a precise duplicate-removal index caching module, a massive amount singular index caching module. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00056"> <pat:ClaimNumber>56< / pat:ClaimNumber> <pat:ClaimText>56. The device of any one of claims 35 to 55, wherein the preset data format includes table name + field names + instance data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00057"> <pat:ClaimNumber>57< / pat:ClaimNumber> <pat:ClaimText>57. The device of any one of claims 35 to 56, is executed based on functional modules including a model information administrator, an index configuration visualized interactor, an index parsing administrator, an index cache acceleration module set, and an index servicing module are deployed on a server. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00058"> <pat:ClaimNumber>58< / pat:ClaimNumber> <pat:ClaimText>58. The device of claim 57, wherein the model information administrator administers model metadata, and to provide functions of enquiring and storing model metadata information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00059"> <pat:ClaimNumber>59< / pat:ClaimNumber> <pat:ClaimText>59. The device of claim 58, wherein the model metadata includes the name, the code, the state, and maintenance information of the model, and relevant information of the fields in the model, including the field names, field types, and field lengths. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00060"> <pat:ClaimNumber>60< / pat:ClaimNumber> <pat:ClaimText>60. The device of any one of claims 58 to 59, wherein the index configuration visualized interactor is for human-machine interaction, and to receive the index configuration information input by the user at the web interface to realize the visualized interface for configuration by the user. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00061"> <pat:ClaimNumber>61< / pat:ClaimNumber> <pat:ClaimText>61. The device of any one of claims 58 to 60, wherein the index parsing administrator obtains the index configuration information configured by the user at the index configuration visualized interactor, and parses the index configuration information to obtain at least one index name, at least one index dimension, and at least one preset model, wherein the preset model corresponds to the target data source. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00062"> <pat:ClaimNumber>62< / pat:ClaimNumber> <pat:ClaimText>62. The device of any one of claims 58 to 61, wherein the index cache acceleration module set contains a set of index cache acceleration modules, wherein the set incudes modules support three scenarios, including an acceleration module of massive amount batch index caching type, the acceleration module of the precise duplicate-removal index caching type, and the acceleration module of the massive amount singular index caching type. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00063"> <pat:ClaimNumber>63< / pat:ClaimNumber> <pat:ClaimText>63. The device of any one of claims 58 to 62, wherein the acceleration module of the massive amount batch index caching type is a core and main module for storing common index cache acceleration data, wherein most indexes are disposed by means of this acceleration module. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00064"> <pat:ClaimNumber>64< / pat:ClaimNumber> <pat:ClaimText>64. The device of any one of claims 58 to 63, wherein the indexes support reprocessing, including summation and calculation of maximum value. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00065"> <pat:ClaimNumber>65< / pat:ClaimNumber> <pat:ClaimText>65. The device of any one of claims 58 to 64, wherein a PostgreSQLTM citus cluster, and / or DruidTM is implemented. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00066"> <pat:ClaimNumber>66< / pat:ClaimNumber> <pat:ClaimText>66. The device of any one of claims 58 to 65, wherein the acceleration module of a precise duplicate-removal index caching type stores index cache acceleration data precisely duplicate- removed within a dynamic range, or by employing the PostgreSQLTM citus cluster. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00067"> <pat:ClaimNumber>67< / pat:ClaimNumber> <pat:ClaimText>67. The device of any one of claims 58 to 66, wherein the acceleration module of a massive amount singular index type stores massive amount of singular indexes, or by employing HBase. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00068"> <pat:ClaimNumber>68< / pat:ClaimNumber> <pat:ClaimText>68. The device of any one of claims 58 to 67, wherein the index servicing module provides the user with unified index services, batch index configuration information set up by the user on the web browser is received and processed in batches, and users are uniformly centralized through the index servicing module. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00069"> <pat:ClaimNumber>69< / pat:ClaimNumber> <pat:ClaimText>69. A system comprising: a receiving module, configured to receive index configuration information input by a user at a web interface wherein the index configuration information is designed by the user; an associating module, configured to establish a first association relation of the index configuration information to a target data source comprising a parsing unit configured to parse the index configuration information to obtain at least one index name, at least one index dimension, and at least one preset model, wherein the preset model corresponds to the target data source and wherein the index dimensions are classified as one or more of basic attributes, business attributes, technical attributes and service attributes; a constructing unit configured to establish at least one associated group according to at least one index name and at least one index dimension, wherein the index names and the index dimensions included in any associated group are associated; a first associating unit configured to establish a second association relation of any associated group to the preset model; and a second associating unit, configured to establish the first association relation of the associated group to the target data source based on the second association relation; and a generating module, configured to generate a report through the preset model that is matched with the target data source based on the index configuration information and the target data source, outputting the report to the user. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00070"> <pat:ClaimNumber>70< / pat:ClaimNumber> <pat:ClaimText>70. The system of claim 69, wherein the constructing unit is further configured to: extract an index code of the index name; extract a dimension code of the index dimension; and establish at least one associated group according to a preconstructed correspondence relation between the index code and the dimension code. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00071"> <pat:ClaimNumber>71< / pat:ClaimNumber> <pat:ClaimText>71. The system of claim 70, wherein the first associating unit is further configured to: parse to obtain a model invoking parameter corresponding to the preset model based on the associated group; match the preset model; and construct the second association relation according to the model invoking parameter. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00072"> <pat:ClaimNumber>72< / pat:ClaimNumber> <pat:ClaimText>72. The system of claim 71, wherein generating module comprises: a first invoking unit configured to invoke the preset model that is matched with the target data source; a second invoking unit configured to invoke target metadata from the target data source; and a generating unit configured to generate the report through the preset model that is matched with the target data source based on the index configuration information and the target metadata. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00073"> <pat:ClaimNumber>73< / pat:ClaimNumber> <pat:ClaimText>73. The system of claim 72, wherein the target metadata includes target offline data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00074"> <pat:ClaimNumber>74< / pat:ClaimNumber> <pat:ClaimText>74. The system of claim 73, wherein the second invoking unit is configured to: obtain the target offline data from a preset external data warehouse according to a preset frequency; and store the target offline data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00075"> <pat:ClaimNumber>75< / pat:ClaimNumber> <pat:ClaimText>75. The system of claim 72, wherein the target metadata includes target real time data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00076"> <pat:ClaimNumber>76< / pat:ClaimNumber> <pat:ClaimText>76. The system of claim 75, wherein the second invoking unit is further configured to: obtain in real time, from a message middleware, the target real time data that is sent after performing real-time index calculation and is of a preset data format. < / 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 69 to 76, further comprising outputting the report through a unified port to the user to provide index service. < / 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 69 to 77, wherein the user directly accesses a visualized design webpage through an web browser, and designs and inputs required index content at an index visualized interactor page, to input index content configuration information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00079"> <pat:ClaimNumber>79< / pat:ClaimNumber> <pat:ClaimText>79. The system of claim 78, wherein index visualized interactor is configured by configuring an index to perform human-machine interaction, wherein the index contents designed by the user are received. < / 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 69 to 79, wherein user operations are enabled by a visualized interface and design of the index and relevant cache configuration of the index are carried out. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00081"> <pat:ClaimNumber>81< / pat:ClaimNumber> <pat:ClaimText>81. The system of claim 80, wherein contents of the cache configuration includes circumstance of index definitions under dimension combinations and corresponding caching methods. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00082"> <pat:ClaimNumber>82< / pat:ClaimNumber> <pat:ClaimText>82. The system of any one of claims 69 to 81, wherein indexes are classified according to the index dimensions. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00083"> <pat:ClaimNumber>83< / pat:ClaimNumber> <pat:ClaimText>83. The system of any one of claims 69 to 82, wherein the index dimensions are classified as the basic attributes including names, codes, types, being public dimensions, parent dimensions, and states. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00084"> <pat:ClaimNumber>84< / pat:ClaimNumber> <pat:ClaimText>84. The system of any one of claims 69 to 83, wherein the index dimensions are classified as the business attributes including business specifications, adjustment frequencies of specifications and sensitivity levels. < / 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 69 to 84, wherein the index dimensions are classified as the technical attributes including table names, technical specifications, fields corresponding to dimensions, fields corresponding to dimension values, and parent dimension fields. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00086"> <pat:ClaimNumber>86< / pat:ClaimNumber> <pat:ClaimText>86. The system of any one of claims 69 to 85, wherein the index dimensions are classified as the service attributes including cache sources, caching modes, and cache storage information. < / 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 69 to 86, wherein the index configuration information includes at least one dimension of the index dimensions. < / 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 69 to 87, wherein mappings of plural groups of cache instances are generated through combined configurations of the indexes and the index dimensions, and contents with different features are respectively processed. < / 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 69 to 88, wherein the preset model includes, one or more of, a massive amount batch index caching module, a precise duplicate-removal index caching module, a massive amount singular index caching module. < / 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 69 to 89, wherein the preset data format includes table name + field names + instance data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00091"> <pat:ClaimNumber>91< / pat:ClaimNumber> <pat:ClaimText>91. The system of any one of claims 69 to 90, is executed based on functional modules including a model information administrator, an index configuration visualized interactor, an index parsing administrator, an index cache acceleration module set, and an index servicing module are deployed on a server. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00092"> <pat:ClaimNumber>92< / pat:ClaimNumber> <pat:ClaimText>92. The system of claim 91, wherein the model information administrator administers model metadata, and to provide functions of enquiring and storing model metadata information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00093"> <pat:ClaimNumber>93< / pat:ClaimNumber> <pat:ClaimText>93. The system of claim 92, wherein the model metadata includes the name, the code, the state, and maintenance information of the model, and relevant information of the fields in the model, including the field names, field types, and field lengths. < / 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 92 to 93, wherein the index configuration visualized interactor is for human-machine interaction, and to receive the index configuration information input by the user at the web interface to realize the visualized interface for configuration by the user. < / 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 92 to 94, wherein the index parsing administrator obtains the index configuration information configured by the user at the index configuration visualized interactor, and parses the index configuration information to obtain at least one index name, at least one index dimension, and at least one preset model, wherein the preset model corresponds to the target data source. < / 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 92 to 95, wherein the index cache acceleration module set contains a set of index cache acceleration modules, wherein the set incudes modules support three scenarios, including an acceleration module of massive amount batch index caching type, the acceleration module of the precise duplicate-removal index caching type, and the acceleration module of the massive amount singular index caching type. < / 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 92 to 96, wherein the acceleration module of the massive amount batch index caching type is a core and main module for storing common index cache acceleration data, wherein most indexes are disposed by means of this acceleration module. < / 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 92 to 97, wherein the indexes support reprocessing, including summation and calculation of maximum value. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00099"> <pat:ClaimNumber>99< / pat:ClaimNumber> <pat:ClaimText>99. The system of any one of claims 92 to 98, wherein a PostgreSQLTM citus cluster, and / or DruidTM is implemented. < / 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 92 to 99, wherein the acceleration module of a precise duplicate-removal index caching type stores index cache acceleration data precisely duplicate- removed within a dynamic range, or by employing the PostgreSQLTM citus cluster. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00101"> <pat:ClaimNumber>101< / pat:ClaimNumber> <pat:ClaimText>101. The system of any one of claims 92 to 100, wherein the acceleration module of a massive amount singular index type stores massive amount of singular indexes, or by employing HBase. < / 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 92 to 101, wherein the index servicing module provides the user with unified index services, batch index configuration information set up by the user on the web browser is received and processed in batches, and users are uniformly centralized through the index servicing module. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00103"> <pat:ClaimNumber>103< / pat:ClaimNumber> <pat:ClaimText>103. An electronic equipment, characterized in 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: receive index configuration information input by a user at a web interface wherein the index configuration information is designed by the user; establish a first association relation of the index configuration information to a target data source comprising: parsing the index configuration information to obtain at least one index name, at least one index dimension, and at least one preset model, wherein the preset model corresponds to the target data source and wherein the index dimensions are classified as one or more of basic attributes, business attributes, technical attributes and service attributes; establishing at least one associated group according to the at least one index name and the at least one index dimension, wherein the index names and the index dimensions included in the associated group are associated; establishing a second association relation of the associated group to the preset model; and establishing the first association relation of the associated group to the target data source based on the second association relation; and generate a report through the preset model that is matched with the target data source based on the index configuration information and the target data source, outputting the report to the user. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00104"> <pat:ClaimNumber>104< / pat:ClaimNumber> <pat:ClaimText>104. The equipment of claim 103, wherein establishing at least one associated group according to at least one index name and at least one index dimension, wherein the index names and the index dimensions included in any associated group are associated comprises: extracting an index code of the index name; extracting a dimension code of the index dimension; and establishing at least one associated group according to a preconstructed correspondence relation between the index code and the dimension code. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00105"> <pat:ClaimNumber>105< / pat:ClaimNumber> <pat:ClaimText>105. The equipment of claim 104, wherein establishing the second association relation of any associated group to the preset model comprises: parsing to obtain a model invoking parameter corresponding to the preset model based on the associated group; matching the preset model; and constructing the second association relation according to the model invoking parameter. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00106"> <pat:ClaimNumber>106< / pat:ClaimNumber> <pat:ClaimText>106. The equipment of claim 105, wherein generating the report through the preset model that is matched with the target data source based on the index configuration information and the target data source comprises: invoking the preset model that is matched with the target data source; invoking target metadata from the target data source; and generating the report through the preset model that is matched with the target data source based on the index configuration information and the target metadata. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00107"> <pat:ClaimNumber>107< / pat:ClaimNumber> <pat:ClaimText>107. The equipment of claim 106, wherein the target metadata includes target offline data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00108"> <pat:ClaimNumber>108< / pat:ClaimNumber> <pat:ClaimText>108. The equipment of claim 107, wherein invoking the target metadata from the target data source comprises: obtaining the target offline data from a preset external data warehouse according to a preset frequency; and storing the target offline data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00109"> <pat:ClaimNumber>109< / pat:ClaimNumber> <pat:ClaimText>109. The equipment of claim 106, wherein the target metadata includes target real time data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00110"> <pat:ClaimNumber>110< / pat:ClaimNumber> <pat:ClaimText>110. The equipment of claim 109, wherein invoking the target metadata from the target data source comprises: obtaining in real time, from a message middleware, the target real time data that is sent after performing real-time index calculation and is of a preset data format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00111"> <pat:ClaimNumber>111< / pat:ClaimNumber> <pat:ClaimText>111. The equipment of any one of claims 103 to 110, further comprising outputting the report through a unified port to the user to provide index service. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00112"> <pat:ClaimNumber>112< / pat:ClaimNumber> <pat:ClaimText>112. The equipment of any one of claims 103 to 111, wherein the user directly accesses a visualized design webpage through an web browser, and designs and inputs required index content at an index visualized interactor page, to input index content configuration information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00113"> <pat:ClaimNumber>113< / pat:ClaimNumber> <pat:ClaimText>113. The equipment of claim 112, wherein index visualized interactor is configured by configuring an index to perform human-machine interaction, wherein the index contents designed by the user are received. < / 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 103 to 113, wherein user operations are enabled by a visualized interface and design of the index and relevant cache configuration of the index are carried out. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00115"> <pat:ClaimNumber>115< / pat:ClaimNumber> <pat:ClaimText>115. The equipment of claim 114, wherein contents of the cache configuration including circumstance of index definitions under dimension combinations and corresponding caching methods. < / 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 103 to 115, wherein indexes are classified according to the index dimensions. < / 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 103 to 116, wherein the index dimensions are classified as the basic attributes including names, codes, types, being public dimensions, parent dimensions, and states. < / 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 103 to 117, wherein the index dimensions are classified as the business attributes including business specifications, adjustment frequencies of specifications and sensitivity levels. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00119"> <pat:ClaimNumber>119< / pat:ClaimNumber> <pat:ClaimText>119. The equipment of any one of claims 103 to 118, wherein the index dimensions are classified as the technical attributes including table names, technical specifications, fields corresponding to dimensions, fields corresponding to dimension values, and parent dimension fields. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00120"> <pat:ClaimNumber>120< / pat:ClaimNumber> <pat:ClaimText>120. The equipment of any one of claims 103 to 119, wherein the index dimensions are classified as the service attributes including cache sources, caching modes, and cache storage information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00121"> <pat:ClaimNumber>121< / pat:ClaimNumber> <pat:ClaimText>121. The equipment of any one of claims 103 to 120, wherein the index configuration information includes at least one dimension of the index dimensions. < / 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 103 to 121, wherein mappings of plural groups of cache instances are generated through combined configurations of the indexes and the index dimensions, and contents with different features are respectively processed. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00123"> <pat:ClaimNumber>123< / pat:ClaimNumber> <pat:ClaimText>123. The equipment of any one of claims 103 to 122, wherein the preset model includes, one or more of, a massive amount batch index caching module, a precise duplicate-removal index caching module, a massive amount singular index caching module. < / 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 103 to 123, wherein the preset data format includes table name + field names + instance data. < / 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 103 to 124, is executed based on functional modules including a model information administrator, an index configuration visualized interactor, an index parsing administrator, an index cache acceleration module set, and an index servicing module are deployed on a server. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00126"> <pat:ClaimNumber>126< / pat:ClaimNumber> <pat:ClaimText>126. The equipment of claim 125, wherein the model information administrator administers model metadata, and to provide functions of enquiring and storing model metadata information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00127"> <pat:ClaimNumber>127< / pat:ClaimNumber> <pat:ClaimText>127. The equipment of claim 126, wherein the model metadata includes the name, the code, the state, and maintenance information of the model, and relevant information of the fields in the model, including the field names, field types, and field lengths. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00128"> <pat:ClaimNumber>128< / pat:ClaimNumber> <pat:ClaimText>128. The equipment of any one of claims 126 to 127, wherein the index configuration visualized interactor is for human-machine interaction, and to receive the index configuration information input by the user at the web interface to realize the visualized interface for configuration by the user. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00129"> <pat:ClaimNumber>129< / pat:ClaimNumber> <pat:ClaimText>129. The equipment of any one of claims 126 to 128, wherein the index parsing administrator obtains the index configuration information configured by the user at the index configuration visualized interactor, and parses the index configuration information to obtain at least one index name, at least one index dimension, and at least one preset model, wherein the preset model corresponds to the target data source. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00130"> <pat:ClaimNumber>130< / pat:ClaimNumber> <pat:ClaimText>130. The equipment of any one of claims 126 to 129, wherein the index cache acceleration module set contains a set of index cache acceleration modules, wherein the set incudes modules support three scenarios, including an acceleration module of massive amount batch index caching type, the acceleration module of the precise duplicate-removal index caching type, and the acceleration module of the massive amount singular index caching type. < / 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 126 to 130, wherein the acceleration module of the massive amount batch index caching type is a core and main module for storing common index cache acceleration data, wherein most indexes are disposed by means of this acceleration module. < / 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 126 to 131, wherein the indexes support reprocessing, including summation and calculation of maximum value. < / 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 126 to 132, wherein a PostgreSQLTM citus cluster, and / or DruidTM is implemented. < / 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 126 to 133, wherein the acceleration module of a precise duplicate-removal index caching type stores index cache acceleration data precisely duplicate-removed within a dynamic range, or by employing the PostgreSQLTM citus cluster. < / 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 126 to 134, wherein the acceleration module of a massive amount singular index type stores massive amount of singular indexes, or by employing HBase. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00136"> <pat:ClaimNumber>136< / pat:ClaimNumber> <pat:ClaimText>136. The equipment of any one of claims 126 to 135, wherein the index servicing module provides the user with unified index services, batch index configuration information set up by the user on the web browser is received and processed in batches, and users are uniformly centralized through the index servicing module. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00137"> <pat:ClaimNumber>137< / pat:ClaimNumber> <pat:ClaimText>137. A computer readable storage medium having stored thereon computer executable instructions for execution by a computer configured to: receive index configuration information input by a user at a web interface wherein the index configuration information is designed by the user; establish a first association relation of the index configuration information to a target data source comprising: parsing the index configuration information to obtain at least one index name, at least one index dimension, and at least one preset model, wherein the preset model corresponds to the target data source and wherein the index dimensions are classified as one or more of basic attributes, business attributes, technical attributes and service attributes; establishing at least one associated group according to the at least one index name and the at least one index dimension, wherein the index names and the index dimensions included in the associated group are associated; establishing a second association relation of the associated group to the preset model; and establishing the first association relation of the associated group to the target data source based on the second association relation; and generate a report through the preset model that is matched with the target data source based on the index configuration information and the target data source, outputting the report to the user. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00138"> <pat:ClaimNumber>138< / pat:ClaimNumber> <pat:ClaimText>138. The storage medium of claim 137, wherein establishing at least one associated group according to at least one index name and at least one index dimension, wherein the index names and the index dimensions included in any associated group are associated comprises: extracting an index code of the index name; extracting a dimension code of the index dimension; and establishing at least one associated group according to a preconstructed correspondence relation between the index code and the dimension code. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00139"> <pat:ClaimNumber>139< / pat:ClaimNumber> <pat:ClaimText>139. The storage medium of claim 138, wherein establishing the second association relation of any associated group to the preset model comprises: parsing to obtain a model invoking parameter corresponding to the preset model based on the associated group; matching the preset model; and constructing the second association relation according to the model invoking parameter. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00140"> <pat:ClaimNumber>140< / pat:ClaimNumber> <pat:ClaimText>140. The storage medium of claim 139, wherein generating the report through the preset model that is matched with the target data source based on the index configuration information and the target data source comprises: invoking the preset model that is matched with the target data source; invoking target metadata from the target data source; and generating the report through the preset model that is matched with the target data source based on the index configuration information and the target metadata. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00141"> <pat:ClaimNumber>141< / pat:ClaimNumber> <pat:ClaimText>141. The storage medium of claim 140, wherein the target metadata includes target offline data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00142"> <pat:ClaimNumber>142< / pat:ClaimNumber> <pat:ClaimText>142. The storage medium of claim 141, wherein invoking the target metadata from the target data source comprises: obtaining the target offline data from a preset external data warehouse according to a preset frequency; and storing the target offline data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00143"> <pat:ClaimNumber>143< / pat:ClaimNumber> <pat:ClaimText>143. The storage medium of claim 140, wherein the target metadata includes target real time data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00144"> <pat:ClaimNumber>144< / pat:ClaimNumber> <pat:ClaimText>144. The storage medium of claim 143, wherein invoking the target metadata from the target data source comprises: obtaining in real time, from a message middleware, the target real time data that is sent after performing real-time index calculation and is of a preset data format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00145"> <pat:ClaimNumber>145< / pat:ClaimNumber> <pat:ClaimText>145. The storage medium of any one of claims 137 to 144, further comprising outputting the report through a unified port to the user to provide index service. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00146"> <pat:ClaimNumber>146< / pat:ClaimNumber> <pat:ClaimText>146. The storage medium of any one of claims 137 to 145, wherein the user directly accesses a visualized design webpage through an web browser, and designs and inputs required index content at an index visualized interactor page, to input index content configuration information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00147"> <pat:ClaimNumber>147< / pat:ClaimNumber> <pat:ClaimText>147. The storage medium of claim 146, wherein index visualized interactor is configured by configuring an index to perform human-machine interaction, wherein the index contents designed by the user are received. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00148"> <pat:ClaimNumber>148< / pat:ClaimNumber> <pat:ClaimText>148. The storage medium of any one of claims 137 to 147, wherein user operations are enabled by a visualized interface and design of the index and relevant cache configuration of the index are carried out. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00149"> <pat:ClaimNumber>149< / pat:ClaimNumber> <pat:ClaimText>149. The storage medium of claim 148, wherein contents of the cache configuration including circumstance of index definitions under dimension combinations and corresponding caching methods. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00150"> <pat:ClaimNumber>150< / pat:ClaimNumber> <pat:ClaimText>150. The storage medium of any one of claims 137 to 149, wherein indexes are classified according to the index dimensions. < / 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 137 to 150, wherein the index dimensions are classified as the basic attributes including names, codes, types, being public dimensions, parent dimensions, and states. < / 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 137 to 151, wherein the index dimensions are classified as the business attributes including business specifications, adjustment frequencies of specifications and sensitivity levels. < / 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 137 to 152, wherein the index dimensions are classified as the technical attributes including table names, technical specifications, fields corresponding to dimensions, fields corresponding to dimension values, and parent dimension fields. < / 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 137 to 153, wherein the index dimensions are classified as the service attributes including cache sources, caching modes, and cache storage information. < / 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 137 to 154, wherein the index configuration information includes at least one dimension of the index dimensions. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00156"> <pat:ClaimNumber>156< / pat:ClaimNumber> <pat:ClaimText>156. The storage medium of any one of claims 137 to 155, wherein mappings of plural groups of cache instances are generated through combined configurations of the indexes and the index dimensions, and contents with different features are respectively processed. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00157"> <pat:ClaimNumber>157< / pat:ClaimNumber> <pat:ClaimText>157. The storage medium of any one of claims 137 to 156, wherein the preset model includes, one or more of, a massive amount batch index caching module, a precise duplicate-removal index caching module, a massive amount singular index caching module. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00158"> <pat:ClaimNumber>158< / pat:ClaimNumber> <pat:ClaimText>158. The storage medium of any one of claims 137 to 157, wherein the preset data format includes table name + field names + instance data. < / 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 137 to 158, wherein is executed based on functional modules including a model information administrator, an index configuration visualized interactor, an index parsing administrator, an index cache acceleration module set, and an index servicing module are deployed on a server. < / 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 the model information administrator administers model metadata, and to provide functions of enquiring and storing model metadata information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00161"> <pat:ClaimNumber>161< / pat:ClaimNumber> <pat:ClaimText>161. The storage medium of claim 160, wherein the model metadata includes the name, the code, the state, and maintenance information of the model, and relevant information of the fields in the model, including the field names, field types, and field lengths. < / 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 the index configuration visualized interactor is for human-machine interaction, and to receive the index configuration information input by the user at the web interface to realize the visualized interface for configuration by the user. < / 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 160 to 162, wherein the index parsing administrator obtains the index configuration information configured by the user at the index configuration visualized interactor, and parses the index configuration information to obtain at least one index name, at least one index dimension, and at least one preset model, wherein the preset model corresponds to the target data source. < / 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 160 to 163, wherein the index cache acceleration module set contains a set of index cache acceleration modules, wherein the set incudes modules support three scenarios, including an acceleration module of massive amount batch index caching type, the acceleration module of the precise duplicate-removal index caching type, and the acceleration module of the massive amount singular index caching type. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00165"> <pat:ClaimNumber>165< / pat:ClaimNumber> <pat:ClaimText>165. The storage medium of any one of claims 160 to 164, wherein the acceleration module of the massive amount batch index caching type is a core and main module for storing common index cache acceleration data, wherein most indexes are disposed by means of this acceleration module. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00166"> <pat:ClaimNumber>166< / pat:ClaimNumber> <pat:ClaimText>166. The storage medium of any one of claims 160 to 165, wherein the indexes support reprocessing, including summation and calculation of maximum value. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00167"> <pat:ClaimNumber>167< / pat:ClaimNumber> <pat:ClaimText>167. The storage medium of any one of claims 160 to 166, wherein a PostgreSQLTM citus cluster, and / or DruidTM is implemented. < / 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 160 to 167, wherein the acceleration module of a precise duplicate-removal index caching type stores index cache acceleration data precisely duplicate-removed within a dynamic range, or by employing the PostgreSQLTM citus cluster. < / 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 160 to 168, wherein the acceleration module of a massive amount singular index type stores massive amount of singular indexes, or by employing HBase. < / 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 160 to 169, wherein the index servicing module provides the user with unified index services, batch index configuration information set up by the user on the web browser is received and processed in batches, and users are uniformly centralized through the index servicing module. < / pat:ClaimText> < / pat:Claim> < / pat:Claims>