Component linkage configuration method, device, computer equipment and storage medium

Abstract

The present invention discloses a component linkage configuration method, a computer equipment and a storage medium. The method comprises: obtaining demand data of a component to be configured, creating a plurality of attributes of the component to be configured according to the demand data, and generating attribute data, configuring linkage configuration data between the plural attributes according to the demand data, wherein the linkage configuration data includes linkage data and linkage relation, matching the linkage configuration data with the attribute data according to a preset rule, and obtaining valid association data, calculating to obtain an association data object to be processed according to the valid association data and the linkage data, employing a preset rendering mechanism to perform linkage rendering on the association data object to be processed, and generating a target component.

Description

COMPONENT LINKAGE CONFIGURATION METHOD, DEVICE, COMPUTER EQUIPMENT AND STORAGE MEDIUM BACKGROUND OF THE INVENTION Technical Field

[0001] The present invention relates to the field of configuration technology, and more particularly to a component linkage configuration method, device, computer equipment and storage medium. Description of Related Art

[0002] In the currently available visual construction platforms, almost all construction components as supplied are custom-developed, while there lacks open component construction. The difficulty of open component construction rests in the attributes of the components and complexity of events. The attributes of a component can be randomly collocated and combined, different values assigned to attributes also render different the other attributes and events associated therewith, so it is required to well process the restraint between different attributes and events, and the linkage restraint between infinite hierarchies.

[0003] Accordingly, there is an urgent need to propose a novel component linkage configuration method, so as to solve the above problems. SUMMARY OF THE INVENTION

[0004] In order to solve the problems pending in the state of the art, embodiments of the present invention provide a method of and a device for configuring a component in linkage, a computer equipment and a storage medium, so as to overcome prior-art problems in which there is restraint between attributes and there is restraint between attributes and events in component configuration.

[0005] To solve one or more of the aforementioned technical problems, the present invention employs the following technical solutions.

[0006] According to the first aspect, a component linkage configuration method is provided, and the method comprises the following steps:

[0007] obtaining demand data of a component to be configured, creating a plurality of attributes of the component to be configured according to the demand data, and generating attribute data;

[0008] configuring linkage configuration data between the plural attributes according to the demand data, wherein the linkage configuration data includes linkage data and linkage relation;

[0009] matching the linkage configuration data with the attribute data according to a preset rule, and obtaining valid association data;

[0010] calculating to obtain an association data object to be processed according to the valid association data and the linkage data; and

[0011] employing a preset rendering mechanism to perform linkage rendering on the association data object to be processed, and generating a target component.

[0012] Further, the step of configuring linkage configuration data between the plural attributes according to the demand data includes:

[0013] configuring linkage data between the plural attributes according to the demand data, and determining linkage relation between the plural attributes according to the linkage data.

[0014] Further, the step of matching the linkage configuration data with the attribute data according to a preset rule, and obtaining valid association data includes:

[0015] obtaining a data type of the linkage configuration data, and matching a corresponding target preset rule out of the preset rule according to the data type; and

[0016] matching the linkage configuration data with the attribute data according to the target preset rule, and obtaining valid association data.

[0017] Further, the data type includes a single element type and a list element type.

[0018] Further, when the data type is the list element type, the step of matching the linkage configuration data with the attribute data according to the target preset rule, and obtaining valid association data includes:

[0019] after multi-dimension to one-dimension conversion of attribute fields in the linkage configuration data according to hierarchical relation of the attributes, matching the converted linkage configuration data with the attribute data according to the target preset rule, and obtaining valid association data.

[0020] Moreover, the method further comprises:

[0021] creating an event of the component to be configured according to the demand data, and configuring event data of the event and binding relation of the event with a corresponding attribute according to the attribute data.

[0022] Moreover, the method further comprises:

[0023] determining event configuration information with which the attribute is associated according to the attribute data, the event data and the binding relation, and rendering the event according to the event configuration information.

[0024] According to the second aspect, a device is provided, and the device comprises:

[0025] an attribute creating module, for obtaining demand data of a component to be configured, creating a plurality of attributes of the component to be configured according to the demand data, and generating attribute data;

[0026] a linkage configuring module, for configuring linkage configuration data between the plural attributes according to the demand data, wherein the linkage configuration data includes linkage data and linkage relation;

[0027] a data matching module, for matching the linkage configuration data with the attribute data according to a preset rule, and obtaining valid association data;

[0028] an object obtaining module, for calculating to obtain an association data object to be processed according to the valid association data and the linkage data; and

[0029] a linkage rendering module, for employing a preset rendering mechanism to perform linkage rendering on the association data object to be processed, and generating a target component.

[0030] According to the third aspect, a computer equipment is provided, which comprises a memory, a processor and a computer program stored on the memory and operable on the processor, and the following steps are realized when the processor executes the computer program:

[0031] obtaining demand data of a component to be configured, creating a plurality of attributes of the component to be configured according to the demand data, and generating attribute data;

[0032] configuring linkage configuration data between the plural attributes according to the demand data, wherein the linkage configuration data includes linkage data and linkage relation;

[0033] matching the linkage configuration data with the attribute data according to a preset rule, and obtaining valid association data;

[0034] calculating to obtain an association data object to be processed according to the valid association data and the linkage data; and

[0035] employing a preset rendering mechanism to perform linkage rendering on the association data object to be processed, and generating a target component.

[0036] According to the fourth aspect, further provided is a computer-readable storage medium storing a computer program thereon, and the following steps are realized when the computer program is executed by a processor:

[0037] obtaining demand data of a component to be configured, creating a plurality of attributes of the component to be configured according to the demand data, and generating attribute data;

[0038] configuring linkage configuration data between the plural attributes according to the demand data, wherein the linkage configuration data includes linkage data and linkage relation;

[0039] matching the linkage configuration data with the attribute data according to a preset rule, and obtaining valid association data;

[0040] calculating to obtain an association data object to be processed according to the valid association data and the linkage data; and

[0041] employing a preset rendering mechanism to perform linkage rendering on the association data object to be processed, and generating a target component.

[0042] Technical solutions provided by the embodiments of the present invention bring about the following advantageous effects:

[0043] In the component linkage configuration method, device, computer equipment and storage medium provided by the embodiments of the present invention, by obtaining demand data of a component to be configured, creating a plurality of attributes of the component to be configured according to the demand data, and generating attribute data, configuring linkage configuration data between the plural attributes according to the demand data, wherein the linkage configuration data includes linkage data and linkage relation, matching the linkage configuration data with the attribute data according to a preset rule, obtaining valid association data, calculating to obtain an associated data object to be processed according to the valid association data and the linkage data, employing a preset rendering mechanism to perform linkage rendering on the association data object to be processed, and generating a target component, the present invention has solved the problems concerning restraint between attributes and restraint between attributes and events in component configuration, so as to realize the configuring capability that can be provided by the component itself, whereby the configuration effect is immediately displayed in accordance with the configuration and component per se, and products with such auxiliary applications become more open and smart. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] To more clearly explain the technical solutions in the embodiments of the present invention, drawings required for use in the following explanation of the embodiments are briefly described below. Apparently, the drawings described below are merely directed to some embodiments of the present invention, while it is further possible for persons ordinarily skilled in the art to base on these drawings to acquire other drawings, and no creative effort will be spent in the process.

[0045] Fig. 1 is a view illustrating the framework of a component configuring system according to an exemplary embodiment;

[0046] Fig. 2 is a flowchart schematically illustrating a component configuring process according to an exemplary embodiment;

[0047] Fig. 3 is a flowchart schematically illustrating a component rendering process according to an exemplary embodiment;

[0048] Fig. 4 is a flowchart illustrating a method of configuring a component in linkage according to an exemplary embodiment;

[0049] Fig. 5 is a view schematically illustrating the structure of a device for configuring a component in linkage according to an exemplary embodiment; and

[0050] Fig. 6 is a view schematically illustrating the internal structure of a computer equipment according to an exemplary embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0051] To make more lucid and clear the objectives, technical solutions and advantages of the present invention, technical solutions in the embodiments of the present invention will be described more clearly and completely below with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the embodiments described below are merely partial, rather than the entire, embodiments of the present invention. All other embodiments achievable 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.

[0052] As noted in the Description of Related Art, due to such factors as attributes of component and complexity of events existent in open component construction, component constructing functions in some visual construction platforms in the state of the art usually support customized development, and cannot support open component construction.

[0053] To address such problem, a component linkage configuration method is creatively proposed in the embodiments of the present invention. This method combines individuality and commonality of each technology stack, takes the component as an independent module by loading the component, inputs data thereto via configuration and linkage rendering, so as to adapt to components output by different technology stacks, to realize configuration linkage of such inherent attributes as attributes, events and slots in multiple states and multiple dimensions, to hence exhibit to users a closely knit configuration of attributes and events. A system architecture that realizes the aforementioned method is as shown in Fig. 1, it mainly consists of an application layer, a logical layer and a foundation support, of which the application layer includes a configuration end and a rendering end for supplying the user with configuration and rendering of the component, the logical layer includes data and a processor for storing relevant data and processing the relevant data, and the foundation support includes data type and control type for defining the data type and control type supported by the system. Embodiment 1

[0054] Specifically, the aforementioned system mainly includes two sections when it executes the component linkage configuration method.

[0055] Section One: Component Configuration

[0056] Specifically, as shown in Fig. 2, plural attributes are firstly created at the configuration end according to user demand, and attribute data is stored in a preset format. As a preferred example, the attribute data can be stored in JSON format. The linkage between the attributes is subsequently configured, that is to say, linkage configuration data between the attributes is configured, and the linkage configuration data is likewise stored in a preset format. As a preferred example, the linkage configuration data can be stored in JSON Schema format. The linkage configuration data includes linkage data and linkage relation. During specific implementation, it is possible to base on the types of the attribute and control thereof to divide the linkage data in terms of data type into a simple structure (including, but not limited to, numerical value, character string, Boolean value, etc.) and a complex structure (including, but not limited to, object, array, etc.), and to divide the linkage relation into character string matching, numerical value interval matching, and Boolean value matching, etc. As should be noted here, in the embodiments of the present invention, it is achievable to configure linkage restraint under different data types on the basis of the JavaScript data type in combination with the JSON schema specification. To subsequently enhance execution efficiency of the matching algorithm, it is possible to convert the attributes from multi-dimension to one-dimension according to hierarchical relation of the attributes.

[0057] If the component to be configured in the user demand further includes events, it is further required to create the events, and to configure a binding relation of each event with a corresponding attribute and event data of each event on the basis of the stored attribute data, and to store the binding relation and the event data in a preset format. As a preferred example, the binding relation and the event data can likewise be stored in the JSON format.

[0058] Section Two: Component Rendering

[0059] Specifically, with reference to Fig. 3, in the embodiments of the present invention, as regards component rendering, considering the problem of page rendering performance so as to reduce the circumstance in which sequential processing of data would trigger doubled component rendering to thereby cause waste of thread occupation, the problem concerning linkage data matching is hence firstly dealt with, and an intersection of data is finally output, to thereby render the component.

[0060] During specific implementation, the rendering end firstly analyzes the configuration data structure obtained from the configuration end to split the configuration data structure in at least three sets of data, namely attribute data, event data, and linkage configuration data.

[0061] The linkage configuration data is firstly matched with the attribute data according to a preset rule to obtain valid association data. In order to enhance the execution efficiency of the matching algorithm, it is possible to, on the basis of element data types in a linkage configuration data list, divide the linkage configuration data into single element type (for instance, the data is a numerical value, a character string, a Boolean value, an object to which element cannot be added) and list element type (such as an object to which element can be added, an array object, etc.). Different matching rules are set for linkage configuration data of different types. As a preferred example, with respect to linkage configuration data of the single element type, it can be directly matched with the values of the attribute data to output the valid association data. With respect to linkage configuration data of the list element type, it is required to firstly convert the attributes from multi-dimension to one-dimension on the basis of the hierarchical relation of the attributes, namely to convert its attribute fields from multi-dimension to one-dimension, and subsequently to recursively process each element value, and to match according to the values of the attribute data to output the valid association data.

[0062] Specifically, since the attribute data configured by the configuration end in the embodiments of the present invention is of a tree structure that has infinite hierarchies, the time complexity of such data is relatively high during technical processing, as recursion of hierarchies is required for search, and the efficiency is low, so its conversion from multi-dimensional array to one-dimensional (that is to say, all attributes pertain to the same hierarchy) array enables quick search of the data object to be processed. During specific implementation, since the multi-dimensional array realizes the hierarchical relation according to the children fields in each attribute object data, and each attribute has a corresponding key under its current hierarchy, recursion is performed once through children and key to add a temporary index field in each attribute object, whereby firstly the uniqueness of each attribute object is guaranteed, and secondly it is made possible to quickly locate to its location in the multi-dimensional array through this field, so as to facilitate logic processing.

[0063] An example is taken below to explain the process of matching linkage configuration data of list element type with the attribute data according to a preset rule and obtaining the valid association data.

[0064] Suppose attribute A of the component is of a numerical value type, attribute B is a Boolean value, and attribute C is a character string. The linkage data of the configuration is that, when the value of attribute A equals to 0, the content of attribute C is cleared, when the value of attribute B is false, the configuration control of attribute C is hidden and the value of attribute C is removed. It is matched through attribute value data that the value of A is 0 and value of B is false, the intersection of the two is taken and the configuration control of attribute C is hidden and the value of C is removed according to weights.

[0065] Finally, the association data object to be processed is distributed to each of the corresponding attribute control, and attribute linkage rendering is realized via the rendering mechanism.

[0066] With respect to a component that contains an event, it is further required to perform event logic processing. During specific implementation, the attribute data and event data obtained by analysis are combined, with the event data as a starting point, the numerical value of the attribute is matched according to the attribute bound to the event (including the attribute whose data type is array or object), and the associated event configuration list information is finally output. Event configuration is rendered through the event configuration list information, and event codes can be output according to the combination of event template, slot and event type, etc. Embodiment 2

[0067] Fig. 4 is a flowchart illustrating a method of configuring a component in linkage according to an exemplary embodiment, with reference to Fig. 4, the method comprises the following steps.

[0068] S1 - obtaining demand data of a component to be configured, creating a plurality of attributes of the component to be configured according to the demand data, and generating attribute data.

[0069] Specifically, in this embodiment, the component to be configured includes, but is not limited to include, a page, etc. Plural attributes are pre-created according to demand data proposed by the user, and corresponding attribute data is generated, wherein the attributes are divided in terms of data type into character string, numerical value, Boolean value, object, array, etc., and the generated attribute data also has different data structures corresponding to the different data types, for instance, the array further covers therein corresponding list data and default values, etc. The attribute data is stored in a preset format, such as the JSON format, to facilitate subsequent loading and use.

[0070] S2 - configuring linkage configuration data between the plural attributes according to the demand data, wherein the linkage configuration data includes linkage data and linkage relation.

[0071] Specifically, after the attributes have been created, it is further required to base on the demand data proposed by the user to configure linkage configuration data between the attributes, and the linkage configuration data includes linkage data and linkage relation. The linkage data includes, but is not limited to include, optional values of attributes as configured. When the value assigned to an attribute with linkage relation is changed, the values of other attributes and events associated with the attribute are also changed therewith.

[0072] S3 - matching the linkage configuration data with the attribute data according to a preset rule, and obtaining valid association data.

[0073] Specifically, while a rendering process is being performed, the configuration data obtained from the configuration end is firstly analyzed through the rendering end, to extract therefrom attribute data and linkage configuration data, if the component includes an event, it is further required to extract event data. The linkage configuration data is subsequently matched with the attribute data according to a preset rule, and valid association data is obtained. As should be noted here, in the embodiments of the present invention, there may be many association data configured by one component, while during the process of rendering, in combination with the actual attribute data and event data etc., the data that actually triggers an association condition is referred to as the valid association data. For instance, in the association data and association relation configured for attribute A, when the value is true, attribute B is hidden, when the value is false, attribute C is hidden, at this time the value of A is false in the actual attribute data, then attribute C being hidden in the case of false is the valid association data.

[0074] S4 - calculating to obtain an association data object to be processed according to the valid association data and the linkage data.

[0075] Specifically, after the valid association data has been obtained, key in the association data is valuated in combination with the type of the associated attribute and the hierarchical relation with the associated attribute; if the association data contains an event, association data objects to which the event corresponds are further required to be extracted in combination with the data of the event, and the association data objects are finally implanted into corresponding attributes in the attribute configuration data and into corresponding events in the event data.

[0076] S5 - employing a preset rendering mechanism to perform linkage rendering on the associated data object to be processed, and generating a target component.

[0077] As a preferred embodiment in the embodiments of the present invention, the step of configuring linkage configuration data between the plural attributes according to the demand data includes:

[0078] configuring linkage data between the plural attributes according to the demand data, and determining linkage relation between the plural attributes according to the linkage data.

[0079] As a preferred embodiment in the embodiments of the present invention, the step of matching the linkage configuration data with the attribute data according to a preset rule, and obtaining valid association data includes:

[0080] obtaining a data type of the linkage configuration data, and matching a corresponding target preset rule out of the preset rule according to the data type; and

[0081] matching the linkage configuration data with the attribute data according to the target preset rule, and obtaining valid association data.

[0082] As a preferred embodiment in the embodiments of the present invention, the data type includes a single element type and a list element type.

[0083] As a preferred embodiment in the embodiments of the present invention, when the data type is the list element type, the step of matching the linkage configuration data with the attribute data according to the target preset rule, and obtaining valid association data includes:

[0084] after multi-dimension to one-dimension conversion of attribute fields in the linkage configuration data according to hierarchical relation of the attributes, matching the converted linkage configuration data with the attribute data according to the target preset rule, and obtaining valid association data.

[0085] As a preferred embodiment in the embodiments of the present invention, the method further comprises:

[0086] creating an event of the component to be configured according to the demand data, and configuring event data of the event and binding relation of the event with a corresponding attribute according to the attribute data.

[0087] As a preferred embodiment in the embodiments of the present invention, the method further comprises:

[0088] determining event configuration information with which the attribute is associated according to the attribute data, the event data and the binding relation, and rendering the event according to the event configuration information.

[0089] As a preferred embodiment in the embodiments of the present invention, the method further comprises:

[0090] monitoring attribute value of the attribute, if the attribute value varies, outputting rendering data again according to corresponding data, and reloading the component. Embodiment 3

[0091] Fig. 5 is a view schematically illustrating the structure of a device for configuring a component in linkage according to an exemplary embodiment, and the device comprises:

[0092] an attribute creating module, for obtaining demand data of a component to be configured, creating a plurality of attributes of the component to be configured according to the demand data, and generating attribute data;

[0093] a linkage configuring module, for configuring linkage configuration data between the plural attributes according to the demand data, wherein the linkage configuration data includes linkage data and linkage relation;

[0094] a data matching module, for matching the linkage configuration data with the attribute data according to a preset rule, and obtaining valid association data;

[0095] an object obtaining module, for calculating to obtain an associated data object to be processed according to the valid association data and the linkage data; and

[0096] a linkage rendering module, for employing a preset rendering mechanism to perform linkage rendering on the associated data object to be processed, and generating a target component.

[0097] As a preferred embodiment in the embodiments of the present invention, the linkage configuring module is specifically employed for:

[0098] configuring linkage data between the plural attributes according to the demand data, and determining linkage relation between the plural attributes according to the linkage data.

[0099] As a preferred embodiment in the embodiments of the present invention, the data matching module is specifically employed for:

[0100] obtaining a data type of the linkage configuration data, and matching a corresponding target preset rule out of the preset rule according to the data type; and

[0101] matching the linkage configuration data with the attribute data according to the target preset rule, and obtaining valid association data.

[0102] As a preferred embodiment in the embodiments of the present invention, the data type includes a single element type and a list element type.

[0103] As a preferred embodiment in the embodiments of the present invention, the data matching module is further employed for:

[0104] after multi-dimension to one-dimension conversion of attribute fields in the linkage configuration data according to hierarchical relation of the attributes, matching the converted linkage configuration data with the attribute data according to the target preset rule, and obtaining valid association data.

[0105] As a preferred embodiment in the embodiments of the present invention, the device further comprises:

[0106] an event creating module, for creating an event of the component to be configured according to the demand data, and configuring event data of the event and binding relation of the event with a corresponding attribute according to the attribute data.

[0107] As a preferred embodiment in the embodiments of the present invention, the device further comprises:

[0108] an event rendering module, for determining event configuration information with which the attribute is associated according to the attribute data, the event data and the binding relation, and rendering the event according to the event configuration information.

[0109] Fig. 6 is a view schematically illustrating the internal structure of a computer equipment according to an exemplary embodiment, with reference to Fig. 6, the computer equipment comprises a processor, a memory, and a network interface connected to each other via a system bus. The processor of the computer equipment is employed to provide computing and controlling capabilities. The memory of the computer equipment includes a nonvolatile storage medium and an internal memory. The nonvolatile storage medium stores therein an operating system, a computer program and a database. The internal memory provides environment for the running of the operating system and the computer program in the nonvolatile storage medium. The network interface of the computer equipment is employed to connect to an external terminal via network for communication. The computer program realizes component linkage configuration method when it is executed by a processor.

[0110] As understandable to persons skilled in the art, the structure illustrated in Fig. 6 is merely a block diagram of partial structure relevant to the solution of the present application, and does not constitute any restriction to the computer equipment on which the solution of the present application is applied, as the specific computer equipment may comprise component parts that are more than or less than those illustrated in Fig. 6, or may combine certain component parts, or may have different layout of component parts.

[0111] As a preferred embodiment in the embodiments of the present invention, the computer equipment comprises a memory, a processor and a computer program stored on the memory and operable on the processor, and the following steps are realized when the processor executes the computer program:

[0112] obtaining demand data of a component to be configured, creating a plurality of attributes of the component to be configured according to the demand data, and generating attribute data;

[0113] configuring linkage configuration data between the plural attributes according to the demand data, wherein the linkage configuration data includes linkage data and linkage relation;

[0114] matching the linkage configuration data with the attribute data according to a preset rule, and obtaining valid association data;

[0115] calculating to obtain an associated data object to be processed according to the valid association data and the linkage data; and

[0116] employing a preset rendering mechanism to perform linkage rendering on the association data object to be processed, and generating a target component.

[0117] As a preferred embodiment in the embodiments of the present invention, when the processor executes the computer program, the following step is further realized:

[0118] configuring linkage data between the plural attributes according to the demand data, and determining linkage relation between the plural attributes according to the linkage data.

[0119] As a preferred embodiment in the embodiments of the present invention, when the processor executes the computer program, the following steps are further realized:

[0120] obtaining a data type of the linkage configuration data, and matching a corresponding target preset rule out of the preset rule according to the data type; and

[0121] matching the linkage configuration data with the attribute data according to the target preset rule, and obtaining valid association data.

[0122] As a preferred embodiment in the embodiments of the present invention, the data type includes a single element type and a list element type.

[0123] As a preferred embodiment in the embodiments of the present invention, when the processor executes the computer program, the following step is further realized:

[0124] after multi-dimension to one-dimension conversion of attribute fields in the linkage configuration data according to hierarchical relation of the attributes, matching the converted linkage configuration data with the attribute data according to the target preset rule, and obtaining valid association data.

[0125] As a preferred embodiment in the embodiments of the present invention, when the processor executes the computer program, the following step is further realized:

[0126] creating an event of the component to be configured according to the demand data, and configuring event data of the event and binding relation of the event with a corresponding attribute according to the attribute data.

[0127] As a preferred embodiment in the embodiments of the present invention, when the processor executes the computer program, the following step is further realized:

[0128] determining event configuration information with which the attribute is associated according to the attribute data, the event data and the binding relation, and rendering the event according to the event configuration information.

[0129] In the embodiments of the present invention, there is further provided a computer- readable storage medium storing a computer program thereon, and the following steps are realized when the computer program is executed by a processor:

[0130] obtaining demand data of a component to be configured, creating a plurality of attributes of the component to be configured according to the demand data, and generating attribute data;

[0131] configuring linkage configuration data between the plural attributes according to the demand data, wherein the linkage configuration data includes linkage data and linkage relation;

[0132] matching the linkage configuration data with the attribute data according to a preset rule, and obtaining valid association data;

[0133] calculating to obtain an associated data object to be processed according to the valid association data and the linkage data; and

[0134] employing a preset rendering mechanism to perform linkage rendering on the associated data object to be processed, and generating a target component.

[0135] As a preferred embodiment in the embodiments of the present invention, when the computer program is executed by a processor, the following step is further realized:

[0136] configuring linkage data between the plural attributes according to the demand data, and determining linkage relation between the plural attributes according to the linkage data.

[0137] As a preferred embodiment in the embodiments of the present invention, when the computer program is executed by a processor, the following steps are further realized:

[0138] obtaining a data type of the linkage configuration data, and matching a corresponding target preset rule out of the preset rule according to the data type; and

[0139] matching the linkage configuration data with the attribute data according to the target preset rule, and obtaining valid association data.

[0140] As a preferred embodiment in the embodiments of the present invention, when the computer program is executed by a processor, the following step is further realized:

[0141] after multi-dimension to one-dimension conversion of attribute fields in the linkage configuration data according to hierarchical relation of the attributes, matching the converted linkage configuration data with the attribute data according to the target preset rule, and obtaining valid association data.

[0142] As a preferred embodiment in the embodiments of the present invention, when the computer program is executed by a processor, the following step is further realized:

[0143] creating an event of the component to be configured according to the demand data, and configuring event data of the event and binding relation of the event with a corresponding attribute according to the attribute data.

[0144] As a preferred embodiment in the embodiments of the present invention, when the computer program is executed by a processor, the following step is further realized:

[0145] determining event configuration information with which the attribute is associated according to the attribute data, the event data and the binding relation, and rendering the event according to the event configuration information.

[0146] In summary, technical solutions provided by the embodiments of the present invention bring about the following advantageous effects.

[0147] In the method of and device for configuring a component in linkage, computer equipment and storage medium provided by the embodiments of the present invention, by obtaining demand data of a component to be configured, creating a plurality of attributes of the component to be configured according to the demand data, and generating attribute data, configuring linkage configuration data between the plural attributes according to the demand data, wherein the linkage configuration data includes linkage data and linkage relation, matching the linkage configuration data with the attribute data according to a preset rule, obtaining valid association data, calculating to obtain an associated data object to be processed according to the valid association data and the linkage data, employing a preset rendering mechanism to perform linkage rendering on the associated data object to be processed, and generating a target component, the present invention has solved the problems concerning restraint between attributes and restraint between attributes and events in component configuration, so as to realize the configuring capability that can be provided by the component itself, whereby the configuration effect is immediately displayed in accordance with the configuration and component per se, and products with such auxiliary applications become more open and smart.

[0148] As should be noted, when the device for configuring a component in linkage provided by the aforementioned embodiment triggers a configuring business, it is merely exemplarily described with its division into the aforementioned various functional modules, whereas in actual application it is possible to base on requirements to assign the aforementioned functions to different functional modules for completion, that is to say, the internal structure of the device is divided into different functional modules to complete the entire or partial functions as described above. In addition, the device for configuring a component in linkage provided by the aforementioned embodiment pertains to the same inventive conception as the method of configuring a component in linkage, in other words, the device is based on the method of configuring a component in linkage – see the method embodiment for its specific implementation process, while no repetition will be made in this context.

[0149] As comprehensible to persons ordinarily skilled in the art, the entire or partial steps in the aforementioned embodiments can be completed via hardware, or via a program instructing relevant hardware, the program can be stored in a computer-readable storage medium, and the storage medium can be a read-only memory, a magnetic disk or an optical disk, etc.

[0150] The foregoing embodiments are merely preferred embodiments of the present invention, and they are not to be construed as restrictive to the present invention. Any amendment, equivalent substitution, and improvement makeable within the spirit and principle of the present invention shall all fall within 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 device for component linkage configuration, the device comprises: an attribute creating module, configured to obtain demand data of a component to be configured, create a plurality of attributes of the component to be configured according to the demand data, and generate attribute data; a linkage configuring module, configured to configure linkage configuration data between the plurality of attributes according to the demand data, wherein the linkage configuration data includes linkage data and linkage relation regarding the plurality of attributes, wherein the linkage data is divided in terms of data type into a simple structure and a complex structure in the data type based on types of the attribute and control thereof, wherein the simple structure includes numerical values and wherein the complex structure includes objects and arrays, and wherein the linkage relation is divided into character string matching, numerical value interval matching, and Boolean value matching based on the types of the attribute and control thereof; a data matching module, configured to match the linkage configuration data with the attribute data according to at least one preset rule, and obtain valid association data, wherein matching further includes: obtaining the data type of the linkage configuration data, and matching a corresponding target preset rule out of the preset rule according to the data type; and matching the linkage configuration data with the attribute data according to the target preset rule, and obtaining the valid association data; wherein the data type includes a single element type and a list element type, wherein the linkage configuration data is divided into the single element type and the list element type on the basis of element data types in a linkage configuration data list, wherein the single element type includes a numerical value, a character string and a Boolean value, wherein the list element type includes an object of an increasable element and an array object; when the linkage configuration data is the list element type, converting the linkage configuration data attribute fields from multi-dimension to one- dimension; recursively processing each element value; and matching according to the values of the attribute data to output the valid association data; an object obtaining module, configured to calculate to obtain an association data object to be processed according to the valid association data and the linkage data; and a linkage rendering module, configured to employ a preset rendering mechanism to perform linkage rendering on the association data object to be processed, and generate a target component. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00002"> <pat:ClaimNumber>2< / pat:ClaimNumber> <pat:ClaimText>2. The device of claim 1, wherein the device is configured to: configure the linkage data between the plurality of attributes according to the demand data, and determine the linkage relation between the plurality of attributes according to the linkage data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00003"> <pat:ClaimNumber>3< / pat:ClaimNumber> <pat:ClaimText>3. The device of any one of claims 1 to 2, wherein the device further comprises: an event creating module, configured to create an event of the component to be configured according to the demand data, and configure event data of the event and binding relation of the event with a corresponding attribute according to the attribute data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00004"> <pat:ClaimNumber>4< / pat:ClaimNumber> <pat:ClaimText>4. The device of any one of claims 1 to 3, wherein the device further comprises: an event rendering module, configured to determine event configuration information with which the attribute is associated according to the attribute data, the event data and binding relation of the event, and render the event according to the event configuration information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00005"> <pat:ClaimNumber>5< / pat:ClaimNumber> <pat:ClaimText>5. The device of any one of claims 1 to 4, wherein the plurality of attributes are created at a configuration end according to user demand. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00006"> <pat:ClaimNumber>6< / pat:ClaimNumber> <pat:ClaimText>6. The device of any one of claims 1 to 5, wherein the attribute data is stored in a preset format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00007"> <pat:ClaimNumber>7< / pat:ClaimNumber> <pat:ClaimText>7. The device of any one of claims 1 to 6, wherein the attribute data is stored in JSON format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00008"> <pat:ClaimNumber>8< / pat:ClaimNumber> <pat:ClaimText>8. The device of any one of claims 1 to 7, wherein the linkage configuration data is stored in a preset format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00009"> <pat:ClaimNumber>9< / pat:ClaimNumber> <pat:ClaimText>9. The device of any one of claims 1 to 8, wherein the linkage configuration data is stored in JSON Schema format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00010"> <pat:ClaimNumber>10< / pat:ClaimNumber> <pat:ClaimText>10. The device of any one of claims 1 to 9, wherein a linkage restraint is configured under different data types on the basis of the JavaScript data type in combination with JSON schema specification. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00011"> <pat:ClaimNumber>11< / pat:ClaimNumber> <pat:ClaimText>11. The device of any one of claims 1 to 10, wherein the attributes are converted from multi- dimension to one-dimension according to hierarchical relation of the attributes. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00012"> <pat:ClaimNumber>12< / pat:ClaimNumber> <pat:ClaimText>12. The device of any one of claims 1 to 11, wherein the component to be configured in user demand further includes events. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00013"> <pat:ClaimNumber>13< / pat:ClaimNumber> <pat:ClaimText>13. The device of any one of claims 1 to 12, wherein the device is further configured to create events and configure binding relation of each event with a corresponding attribute and event data of each event based on the attribute data stored, and to store the binding relation of each event and the event data in a preset format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00014"> <pat:ClaimNumber>14< / pat:ClaimNumber> <pat:ClaimText>14. The device of claim 13, wherein the binding relation of each event is stored in JSON format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00015"> <pat:ClaimNumber>15< / pat:ClaimNumber> <pat:ClaimText>15. The device of claim 4, wherein the event data is stored in JSON format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00016"> <pat:ClaimNumber>16< / pat:ClaimNumber> <pat:ClaimText>16. The device of any one of claims 1 to 15, wherein a rendering end analyzes configuration data structure obtained from a configuration end to split the configuration data structure into at least three sets of data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00017"> <pat:ClaimNumber>17< / pat:ClaimNumber> <pat:ClaimText>17. The device of claim 16, wherein the configuration data structure is split into the attribute data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00018"> <pat:ClaimNumber>18< / pat:ClaimNumber> <pat:ClaimText>18. The device of any one of claims 16 to 17, wherein the configuration data structure is split into event data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00019"> <pat:ClaimNumber>19< / pat:ClaimNumber> <pat:ClaimText>19. The device of any one of claims 16 to 18, wherein the configuration data structure is split into the linkage configuration data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00020"> <pat:ClaimNumber>20< / pat:ClaimNumber> <pat:ClaimText>20. The device of any one of claims 1 to 19, wherein different matching rules are set for the linkage configuration data of different types. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00021"> <pat:ClaimNumber>21< / pat:ClaimNumber> <pat:ClaimText>21. The device of any one of claims 1 to 20, wherein the linkage configuration data of the single element type is directly matched with the values of the attribute data to output the valid association data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00022"> <pat:ClaimNumber>22< / pat:ClaimNumber> <pat:ClaimText>22. The device of any one of claims 1 to 21, wherein the attribute data configured by the configuration end is of a tree structure that has infinite hierarchies. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00023"> <pat:ClaimNumber>23< / pat:ClaimNumber> <pat:ClaimText>23. The device of any one of claims 1 to 22, wherein a multi-dimensional array realizes hierarchical relation according to the children fields in each attribute object data, and each attribute has a corresponding key under its current hierarchy. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00024"> <pat:ClaimNumber>24< / pat:ClaimNumber> <pat:ClaimText>24. The device of any one of claims 1 to 23, wherein recursion is performed through children and key to add a temporary index field in each attribute object. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00025"> <pat:ClaimNumber>25< / pat:ClaimNumber> <pat:ClaimText>25. The device of any one of claims 1 to 24, wherein the association data object to be processed is distributed to each of the corresponding attribute control, and attribute linkage rendering is realized via the rendering mechanism. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00026"> <pat:ClaimNumber>26< / pat:ClaimNumber> <pat:ClaimText>26. The device of any one of claims 1 to 25, wherein the device is further configured to perform an event logic processing including that the attribute data and event data are combined, with the event data as a starting point, the numerical value of the attribute is matched according to the attribute bound to the event, and the associated event configuration list information is output. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00027"> <pat:ClaimNumber>27< / pat:ClaimNumber> <pat:ClaimText>27. The device of any one of claims 1 to 26, wherein a type of the attribute data is an array. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00028"> <pat:ClaimNumber>28< / pat:ClaimNumber> <pat:ClaimText>28. The device of any one of claims 1 to 27, wherein a type of the attribute data is an object. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00029"> <pat:ClaimNumber>29< / pat:ClaimNumber> <pat:ClaimText>29. The device of any one of claims 4 to 28, wherein the event configuration information is rendered through information of an event configuration list. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00030"> <pat:ClaimNumber>30< / pat:ClaimNumber> <pat:ClaimText>30. The device of any one of claims 1 to 29, wherein event codes are outputted according to the combination of event template, slot and event type. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00031"> <pat:ClaimNumber>31< / pat:ClaimNumber> <pat:ClaimText>31. The device of any one of claims 1 to 30, wherein the component to be configured includes a page. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00032"> <pat:ClaimNumber>32< / pat:ClaimNumber> <pat:ClaimText>32. The device of any one of claims 1 to 31, wherein the attributes are divided in terms of the data type into character string, numerical value, Boolean value, object, or array. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00033"> <pat:ClaimNumber>33< / pat:ClaimNumber> <pat:ClaimText>33. The device of any one of claims 1 to 32, wherein the attribute data generated has different data structures corresponding to the different data types. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00034"> <pat:ClaimNumber>34< / pat:ClaimNumber> <pat:ClaimText>34. The device of any one of claims 1 to 33, wherein the data structure is an array which further covers corresponding list data and default values. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00035"> <pat:ClaimNumber>35< / pat:ClaimNumber> <pat:ClaimText>35. The device of any one of claims 1 to 34, wherein the linkage data includes optional values of attributes as configured. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00036"> <pat:ClaimNumber>36< / pat:ClaimNumber> <pat:ClaimText>36. The device of any one of claims 1 to 35, wherein the values of other attributes and events associated with the attribute are changed when the value assigned to an attribute with the linkage relation is changed. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00037"> <pat:ClaimNumber>37< / pat:ClaimNumber> <pat:ClaimText>37. The device of any one of claims 1 to 36, wherein, while a rendering process is being performed, configuration data obtained from the configuration end is analyzed through the rendering end, to extract therefrom the attribute data and the linkage configuration data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00038"> <pat:ClaimNumber>38< / pat:ClaimNumber> <pat:ClaimText>38. The device of any one of claims 1 to 37, wherein, while a rendering process is being performed, event data is extracted if the component includes an event. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00039"> <pat:ClaimNumber>39< / pat:ClaimNumber> <pat:ClaimText>39. The device of any one of claims 1 to 38, wherein the component to be configured includes a plurality of association data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00040"> <pat:ClaimNumber>40< / pat:ClaimNumber> <pat:ClaimText>40. The device of any one of claims 1 to 39, wherein, during the process of rendering, the valid association data triggers an association condition. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00041"> <pat:ClaimNumber>41< / pat:ClaimNumber> <pat:ClaimText>41. The device of any one of claims 1 to 40, wherein a key in the association data is valuated in combination with the type of the associated attribute and hierarchical relation with the associated attribute. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00042"> <pat:ClaimNumber>42< / pat:ClaimNumber> <pat:ClaimText>42. The device of any one of claims 1 to 41, wherein, if the association data contains an event, association data objects to which the event corresponds are extracted in combination with the data of the event, and the association data objects are implanted into corresponding attributes in the attribute configuration data and into corresponding events in the event data. < / 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 1 to 42, wherein a value of the attribute data is monitored. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00044"> <pat:ClaimNumber>44< / pat:ClaimNumber> <pat:ClaimText>44. The device of claim 43, wherein if the value of the attribute data varies, a rendering data is outputted according to corresponding data, and a component is reloaded. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00045"> <pat:ClaimNumber>45< / pat:ClaimNumber> <pat:ClaimText>45. A computer-readable storage medium storing computer-executable instructions thereon that, when executed by a computer, perform the following operations of: obtain demand data of a component to be configured, create a plurality of attributes of the component to be configured according to the demand data, and generate attribute data; configure linkage configuration data between the plurality of attributes according to the demand data, wherein the linkage configuration data includes linkage data and linkage relation regarding the plurality of attributes, wherein the linkage data is divided in terms of data type into a simple structure and a complex structure in the data type based on types of the attribute and control thereof, wherein the simple structure includes numerical values and wherein the complex structure includes objects and arrays, and wherein the linkage relation is divided into character string matching, numerical value interval matching, and Boolean value matching based on the types of the attribute and control thereof; match the linkage configuration data with the attribute data according to at least one preset rule, and obtain valid association data, wherein matching further includes: obtaining the data type of the linkage configuration data, and matching a corresponding target preset rule out of the preset rule according to the data type; and matching the linkage configuration data with the attribute data according to the target preset rule, and obtaining the valid association data; wherein the data type includes a single element type and a list element type, wherein the linkage configuration data is divided into the single element type and the list element type on the basis of element data types in a linkage configuration data list, wherein the single element type includes a numerical value, a character string and a Boolean value, wherein the list element type includes an object of an increasable element and an array object; when the linkage configuration data is the list element type, converting the linkage configuration data attribute fields from multi-dimension to one- dimension; recursively processing each element value; and matching according to the values of the attribute data to output the valid association data; calculating to obtain an association data object to be processed according to the valid association data and the linkage data; and employing a preset rendering mechanism to perform linkage rendering on the association data object to be processed, and generate a target component. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00046"> <pat:ClaimNumber>46< / pat:ClaimNumber> <pat:ClaimText>46. The computer-readable storage medium of claim 45, wherein the computer-readable storage medium storing computer-executable instructions thereon that, further configured to: configure the linkage data between the plurality of attributes according to the demand data, and determine the linkage relation between the plurality of attributes according to the linkage data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00047"> <pat:ClaimNumber>47< / pat:ClaimNumber> <pat:ClaimText>47. The computer-readable storage medium of any one of claims 45 to 46, wherein the computer- readable storage medium storing computer-executable instructions thereon that, further configured to: create an event of the component to be configured according to the demand data, and configuring event data of the event and binding relation of the event with a corresponding attribute according to the attribute data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00048"> <pat:ClaimNumber>48< / pat:ClaimNumber> <pat:ClaimText>48. The computer-readable storage medium of any one of claims 45 to 47, wherein the computer- readable storage medium storing computer-executable instructions thereon that, further configured to: determine event configuration information with which the attribute is associated according to the attribute data, the event data and the binding relation of the event, and rendering the event according to the event configuration information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00049"> <pat:ClaimNumber>49< / pat:ClaimNumber> <pat:ClaimText>49. The computer-readable storage medium of any one of claims 45 to 48, wherein the plurality of attributes are created at a configuration end according to user demand. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00050"> <pat:ClaimNumber>50< / pat:ClaimNumber> <pat:ClaimText>50. The computer-readable storage medium of any one of claims 45 to 49, wherein the attribute data is stored in a preset format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00051"> <pat:ClaimNumber>51< / pat:ClaimNumber> <pat:ClaimText>51. The computer-readable storage medium of any one of claims 45 to 50, wherein the attribute data is stored in JSON format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00052"> <pat:ClaimNumber>52< / pat:ClaimNumber> <pat:ClaimText>52. The computer-readable storage medium of any one of claims 45 to 51, wherein the linkage configuration data is stored in a preset format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00053"> <pat:ClaimNumber>53< / pat:ClaimNumber> <pat:ClaimText>53. The computer-readable storage medium of any one of claims 45 to 52, wherein the linkage configuration data is stored in JSON Schema format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00054"> <pat:ClaimNumber>54< / pat:ClaimNumber> <pat:ClaimText>54. The computer-readable storage medium of any one of claims 45 to 53, wherein a linkage restraint is configured under different data types on the basis of the JavaScript data type in combination with JSON schema specification. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00055"> <pat:ClaimNumber>55< / pat:ClaimNumber> <pat:ClaimText>55. The computer-readable storage medium of any one of claims 45 to 54, wherein the attributes are converted from multi-dimension to one-dimension according to hierarchical relation of the attributes. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00056"> <pat:ClaimNumber>56< / pat:ClaimNumber> <pat:ClaimText>56. The computer-readable storage medium of any one of claims 45 to 55, wherein the component to be configured in user demand further includes events. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00057"> <pat:ClaimNumber>57< / pat:ClaimNumber> <pat:ClaimText>57. The computer-readable storage medium of any one of claims 45 to 56, wherein the computer- readable storage medium storing computer-executable instructions thereon that, further configured to create events and configures binding relation of each event with a corresponding attribute and event data of each event based on the attribute data stored, and to store the binding relation of each event and the event data in a preset format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00058"> <pat:ClaimNumber>58< / pat:ClaimNumber> <pat:ClaimText>58. The computer-readable storage medium of claim 57, wherein the binding relation of each event is stored in JSON format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00059"> <pat:ClaimNumber>59< / pat:ClaimNumber> <pat:ClaimText>59. The computer-readable storage medium of claim 57, wherein the event data is stored in JSON format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00060"> <pat:ClaimNumber>60< / pat:ClaimNumber> <pat:ClaimText>60. The computer-readable storage medium of any one of claims 45 to 59, wherein a rendering end analyzes configuration data structure obtained from a configuration end to split the configuration data structure into at least three sets of data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00061"> <pat:ClaimNumber>61< / pat:ClaimNumber> <pat:ClaimText>61. The computer-readable storage medium of claim 60, wherein the configuration data structure is split into the attribute data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00062"> <pat:ClaimNumber>62< / pat:ClaimNumber> <pat:ClaimText>62. The computer-readable storage medium of any one of claims 60 to 61, wherein the configuration data structure is split into event data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00063"> <pat:ClaimNumber>63< / pat:ClaimNumber> <pat:ClaimText>63. The computer-readable storage medium of any one of claims 60 to 62, wherein the configuration data structure is split into the linkage configuration data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00064"> <pat:ClaimNumber>64< / pat:ClaimNumber> <pat:ClaimText>64. The computer-readable storage medium of any one of claims 45 to 63, wherein different matching rules are set for the linkage configuration data of different types. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00065"> <pat:ClaimNumber>65< / pat:ClaimNumber> <pat:ClaimText>65. The computer-readable storage medium of any one of claims 45 to 64, wherein the linkage configuration data of the single element type is directly matched with the values of the attribute data to output the valid association data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00066"> <pat:ClaimNumber>66< / pat:ClaimNumber> <pat:ClaimText>66. The computer-readable storage medium of any one of claims 45 to 65, wherein the attribute data configured by the configuration end is of a tree structure that has infinite hierarchies. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00067"> <pat:ClaimNumber>67< / pat:ClaimNumber> <pat:ClaimText>67. The computer-readable storage medium of any one of claims 45 to 66, wherein multi- dimensional array realizes hierarchical relation according to the children fields in each attribute object data, and each attribute has a corresponding key under its current hierarchy. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00068"> <pat:ClaimNumber>68< / pat:ClaimNumber> <pat:ClaimText>68. The computer-readable storage medium of any one of claims 45 to 67, wherein recursion is performed through children and key to add a temporary index field in each attribute object. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00069"> <pat:ClaimNumber>69< / pat:ClaimNumber> <pat:ClaimText>69. The computer-readable storage medium of any one of claims 45 to 68, wherein the association data object to be processed is distributed to each of the corresponding attribute control, and attribute linkage rendering is realized via the rendering mechanism. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00070"> <pat:ClaimNumber>70< / pat:ClaimNumber> <pat:ClaimText>70. The computer-readable storage medium of any one of claims 45 to 69, wherein the computer- readable storage medium storing computer-executable instructions thereon that, further configured to perform an event logic processing including that the attribute data and event data are combined, with the event data as a starting point, the numerical value of the attribute is matched according to the attribute bound to the event, and the associated event configuration list information is output. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00071"> <pat:ClaimNumber>71< / pat:ClaimNumber> <pat:ClaimText>71. The computer-readable storage medium of any one of claims 45 to 70, wherein a type of the attribute data is an array. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00072"> <pat:ClaimNumber>72< / pat:ClaimNumber> <pat:ClaimText>72. The computer-readable storage medium of any one of claims 45 to 71, wherein the a type of the attribute data is an object. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00073"> <pat:ClaimNumber>73< / pat:ClaimNumber> <pat:ClaimText>73. The computer-readable storage medium of any one of claims 48 to 72, wherein the event configuration information is rendered through information of an event configuration list. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00074"> <pat:ClaimNumber>74< / pat:ClaimNumber> <pat:ClaimText>74. The computer-readable storage medium of any one of claims 45 to 73, wherein event codes are outputted according to the combination of event template, slot and event type. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00075"> <pat:ClaimNumber>75< / pat:ClaimNumber> <pat:ClaimText>75. The computer-readable storage medium of any one of claims 45 to 74, wherein the component to be configured includes a page. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00076"> <pat:ClaimNumber>76< / pat:ClaimNumber> <pat:ClaimText>76. The computer-readable storage medium of any one of claims 45 to 75, wherein the attributes are divided in terms of the data type into character string, numerical value, Boolean value, object, or array. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00077"> <pat:ClaimNumber>77< / pat:ClaimNumber> <pat:ClaimText>77. The computer-readable storage medium of any one of claims 45 to 76, wherein the attribute data generated has different data structures corresponding to the different data types. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00078"> <pat:ClaimNumber>78< / pat:ClaimNumber> <pat:ClaimText>78. The computer-readable storage medium of any one of claims 45 to 77, wherein the data structure is an array which further covers corresponding list data and default values. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00079"> <pat:ClaimNumber>79< / pat:ClaimNumber> <pat:ClaimText>79. The computer-readable storage medium of any one of claims 45 to 78, wherein the linkage data includes optional values of attributes as configured. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00080"> <pat:ClaimNumber>80< / pat:ClaimNumber> <pat:ClaimText>80. The computer-readable storage medium of any one of claims 45 to 79, wherein the values of other attributes and events associated with the attribute are changed when the value assigned to an attribute with the linkage relation is changed. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00081"> <pat:ClaimNumber>81< / pat:ClaimNumber> <pat:ClaimText>81. The computer-readable storage medium of any one of claims 45 to 80, wherein, while a rendering process is being performed, configuration data obtained from the configuration end is analyzed through the rendering end, to extract therefrom the attribute data and the linkage configuration data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00082"> <pat:ClaimNumber>82< / pat:ClaimNumber> <pat:ClaimText>82. The computer-readable storage medium of any one of claims 45 to 81, wherein, while a rendering process is being performed, event data is extracted if the component includes an event. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00083"> <pat:ClaimNumber>83< / pat:ClaimNumber> <pat:ClaimText>83. The computer-readable storage medium of any one of claims 45 to 82, wherein the component to be configured includes a plurality of association data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00084"> <pat:ClaimNumber>84< / pat:ClaimNumber> <pat:ClaimText>84. The computer-readable storage medium of any one of claims 45 to 83, wherein, during the process of rendering, the valid association data triggers an association condition. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00085"> <pat:ClaimNumber>85< / pat:ClaimNumber> <pat:ClaimText>85. The computer-readable storage medium of any one of claims 45 to 84, wherein a key in the association data is valuated in combination with the type of the associated attribute and hierarchical relation with the associated attribute. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00086"> <pat:ClaimNumber>86< / pat:ClaimNumber> <pat:ClaimText>86. The computer-readable storage medium of any one of claims 45 to 85, wherein, if the association data contains an event, association data objects to which the event corresponds are extracted in combination with the data of the event, and the association data objects are implanted into corresponding attributes in the attribute configuration data and into corresponding events in the event data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00087"> <pat:ClaimNumber>87< / pat:ClaimNumber> <pat:ClaimText>87. The computer-readable storage medium of any one of claims 45 to 86, wherein a value of the attribute data is monitored. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00088"> <pat:ClaimNumber>88< / pat:ClaimNumber> <pat:ClaimText>88. The computer-readable storage medium of claim 87, wherein if the value of the attribute data varies, a rendering data is outputted according to corresponding data, and a component is reloaded. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00089"> <pat:ClaimNumber>89< / pat:ClaimNumber> <pat:ClaimText>89. The computer-readable storage medium of any one of claims 45 to 88, wherein the computer- readable storage medium is a read-only memory. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00090"> <pat:ClaimNumber>90< / pat:ClaimNumber> <pat:ClaimText>90. The computer-readable storage medium of any one of claims 45 to 89, wherein the computer- readable storage medium is a magnetic disk. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00091"> <pat:ClaimNumber>91< / pat:ClaimNumber> <pat:ClaimText>91. The computer-readable storage medium of any one of claims 45 to 90, wherein the computer- readable storage medium is an optical disk. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00092"> <pat:ClaimNumber>92< / pat:ClaimNumber> <pat:ClaimText>92. A computer equipment, comprising: a processor configured to: obtain demand data of a component to be configured, create a plurality of attributes of the component to be configured according to the demand data, and generate attribute data; configure linkage configuration data between the plurality of attributes according to the demand data, wherein the linkage configuration data includes linkage data and linkage relation regarding the plurality of attributes, wherein the linkage data is divided in terms of data type into a simple structure and a complex structure in the data type based on types of the attribute and control thereof, wherein the simple structure includes numerical values and wherein the complex structure includes objects and arrays, and wherein the linkage relation is divided into character string matching, numerical value interval matching, and Boolean value matching based on the types of the attribute and control thereof,; match the linkage configuration data with the attribute data according to at least one preset rule, and obtain valid association data, wherein matching further includes: obtaining the data type of the linkage configuration data, and matching a corresponding target preset rule out of the preset rule according to the data type; and matching the linkage configuration data with the attribute data according to the target preset rule, and obtaining the valid association data; wherein the data type includes a single element type and a list element type, wherein the linkage configuration data is divided into the single element type and the list element type on the basis of element data types in a linkage configuration data list, wherein the single element type includes a numerical value, a character string and a Boolean value, wherein the list element type includes an object of an increasable element and an array object; when the linkage configuration data is the list element type, converting the linkage configuration data attribute fields from multi-dimension to one- dimension; recursively processing each element value; and matching according to the values of the attribute data to output the valid association data; calculate to obtain an association data object to be processed according to the valid association data and the linkage data; and employ a preset rendering mechanism to perform linkage rendering on the association data object to be processed, and generate a target component; a memory, storing therein a computer program, a network interface, and a system bus. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00093"> <pat:ClaimNumber>93< / pat:ClaimNumber> <pat:ClaimText>93. The computer equipment of claim 92, wherein the computer equipment is further configured to: configure the linkage data between the plurality of attributes according to the demand data, and determine the linkage relation between the plurality of attributes according to the linkage data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00094"> <pat:ClaimNumber>94< / pat:ClaimNumber> <pat:ClaimText>94. The computer equipment of any one of claims 92 to 93, wherein the computer equipment is further configured to: create an event of the component to be configured according to the demand data, and configure event data of the event and binding relation of the event with a corresponding attribute according to the attribute data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00095"> <pat:ClaimNumber>95< / pat:ClaimNumber> <pat:ClaimText>95. The computer equipment of any one of claims 92 to 94, wherein the computer equipment is further configured to: determine event configuration information with which the attribute is associated according to the attribute data, the event data and binding relation of the event, and render the event according to the event configuration information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00096"> <pat:ClaimNumber>96< / pat:ClaimNumber> <pat:ClaimText>96. The computer equipment of any one of claims 92 to 95, wherein the plurality of attributes are created at a configuration end according to user demand. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00097"> <pat:ClaimNumber>97< / pat:ClaimNumber> <pat:ClaimText>97. The computer equipment of any one of claims 92 to 96, wherein the attribute data is stored in a preset format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00098"> <pat:ClaimNumber>98< / pat:ClaimNumber> <pat:ClaimText>98. The computer equipment of any one of claims 92 to 97, wherein the attribute data is stored in JSON format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00099"> <pat:ClaimNumber>99< / pat:ClaimNumber> <pat:ClaimText>99. The computer equipment of any one of claims 92 to 98, wherein the linkage configuration data is stored in a preset format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00100"> <pat:ClaimNumber>100< / pat:ClaimNumber> <pat:ClaimText>100. The computer equipment of any one of claims 92 to 99, wherein the linkage configuration data is stored in JSON Schema format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00101"> <pat:ClaimNumber>101< / pat:ClaimNumber> <pat:ClaimText>101. The computer equipment of any one of claims 92 to 100, wherein a linkage restraint is configured under different data types on the basis of the JavaScript data type in combination with JSON schema specification. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00102"> <pat:ClaimNumber>102< / pat:ClaimNumber> <pat:ClaimText>102. The computer equipment of any one of claims 92 to 101, wherein the attributes are converted from multi-dimension to one-dimension according to hierarchical relation of the attributes. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00103"> <pat:ClaimNumber>103< / pat:ClaimNumber> <pat:ClaimText>103. The computer equipment of any one of claims 92 to 102, wherein the component to be configured in user demand further includes events. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00104"> <pat:ClaimNumber>104< / pat:ClaimNumber> <pat:ClaimText>104. The computer equipment of any one of claims 92 to 103, wherein the computer equipment is further configured to create events and configures binding relation of each event with a corresponding attribute and event data of each event on based on the attribute data stored, and to store the binding relation of each event and the event data in a preset format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00105"> <pat:ClaimNumber>105< / pat:ClaimNumber> <pat:ClaimText>105. The computer equipment of claim 104, wherein the binding relation of each event is stored in JSON format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00106"> <pat:ClaimNumber>106< / pat:ClaimNumber> <pat:ClaimText>106. The computer equipment of claim 104, wherein the event data is stored in JSON format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00107"> <pat:ClaimNumber>107< / pat:ClaimNumber> <pat:ClaimText>107. The computer equipment of any one of claims 92 to 106, wherein a rendering end analyzes configuration data structure obtained from a configuration end to split the configuration data structure into at least three sets of data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00108"> <pat:ClaimNumber>108< / pat:ClaimNumber> <pat:ClaimText>108. The computer equipment of claim 107, wherein the configuration data structure is split into the attribute data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00109"> <pat:ClaimNumber>109< / pat:ClaimNumber> <pat:ClaimText>109. The computer equipment of any one of claims 107 to 108, wherein the configuration data structure is split into event data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00110"> <pat:ClaimNumber>110< / pat:ClaimNumber> <pat:ClaimText>110. The computer equipment of any one of claims 107 to 109, wherein the configuration data structure is split into the linkage configuration data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00111"> <pat:ClaimNumber>111< / pat:ClaimNumber> <pat:ClaimText>111. The computer equipment of any one of claims 92 to 110, wherein different matching rules are set for the linkage configuration data of different types. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00112"> <pat:ClaimNumber>112< / pat:ClaimNumber> <pat:ClaimText>112. The computer equipment of any one of claims 92 to 111, wherein the linkage configuration data of the single element type is directly matched with the values of the attribute data to output the valid association data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00113"> <pat:ClaimNumber>113< / pat:ClaimNumber> <pat:ClaimText>113. The computer equipment of any one of claims 92 to 112, wherein the attribute data configured by the configuration end is of a tree structure that has infinite hierarchies. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00114"> <pat:ClaimNumber>114< / pat:ClaimNumber> <pat:ClaimText>114. The computer equipment of any one of claims 92 to 113, wherein a multi-dimensional array realizes hierarchical relation according to the children fields in each attribute object data, and each attribute has a corresponding key under its current hierarchy. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00115"> <pat:ClaimNumber>115< / pat:ClaimNumber> <pat:ClaimText>115. The computer equipment of any one of claims 92 to 114, wherein recursion is performed through children and key to add a temporary index field in each attribute object. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00116"> <pat:ClaimNumber>116< / pat:ClaimNumber> <pat:ClaimText>116. The computer equipment of any one of claims 92 to 115, wherein the association data object to be processed is distributed to each of the corresponding attribute control, and attribute linkage rendering is realized via the rendering mechanism. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00117"> <pat:ClaimNumber>117< / pat:ClaimNumber> <pat:ClaimText>117. The computer equipment of any one of claims 92 to 116, wherein the computer equipment is further configured to perform an event logic processing including that the attribute data and event data are combined, with the event data as a starting point, the numerical value of the attribute is matched according to the attribute bound to the event, and the associated event configuration list information is output. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00118"> <pat:ClaimNumber>118< / pat:ClaimNumber> <pat:ClaimText>118. The computer equipment of any one of claims 92 to 117, wherein a type of the attribute data is an array. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00119"> <pat:ClaimNumber>119< / pat:ClaimNumber> <pat:ClaimText>119. The computer equipment of any one of claims 92 to 118, wherein a type of the attribute data is an object. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00120"> <pat:ClaimNumber>120< / pat:ClaimNumber> <pat:ClaimText>120. The computer equipment of any one of claims 95 to 119, wherein the event configuration information is rendered through information of an event configuration list. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00121"> <pat:ClaimNumber>121< / pat:ClaimNumber> <pat:ClaimText>121. The computer equipment of any one of claims 92 to 120, wherein event codes are outputted according to the combination of event template, slot and event type. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00122"> <pat:ClaimNumber>122< / pat:ClaimNumber> <pat:ClaimText>122. The computer equipment of any one of claims 92 to 121, wherein the component to be configured includes a page. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00123"> <pat:ClaimNumber>123< / pat:ClaimNumber> <pat:ClaimText>123. The computer equipment of any one of claims 92 to 122, wherein the attributes are divided in terms of the data type into character string, numerical value, Boolean value, object, or array. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00124"> <pat:ClaimNumber>124< / pat:ClaimNumber> <pat:ClaimText>124. The computer equipment of any one of claims 92 to 123, wherein the attribute data generated has different data structures corresponding to the different data types. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00125"> <pat:ClaimNumber>125< / pat:ClaimNumber> <pat:ClaimText>125. The computer equipment of any one of claims 92 to 124, wherein the data structure is an array which further covers corresponding list data and default values. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00126"> <pat:ClaimNumber>126< / pat:ClaimNumber> <pat:ClaimText>126. The computer equipment of any one of claims 92 to 125, wherein the linkage data includes optional values of attributes as configured. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00127"> <pat:ClaimNumber>127< / pat:ClaimNumber> <pat:ClaimText>127. The computer equipment of any one of claims 92 to 126, wherein the values of other attributes and events associated with the attribute are changed when the value assigned to an attribute with the linkage relation is changed. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00128"> <pat:ClaimNumber>128< / pat:ClaimNumber> <pat:ClaimText>128. The computer equipment of any one of claims 92 to 127, wherein, while a rendering process is being performed, configuration data obtained from the configuration end is analyzed through the rendering end, to extract therefrom the attribute data and the linkage configuration data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00129"> <pat:ClaimNumber>129< / pat:ClaimNumber> <pat:ClaimText>129. The computer equipment of any one of claims 92 to 128, wherein, while a rendering process is being performed, event data is extracted if the component includes an event. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00130"> <pat:ClaimNumber>130< / pat:ClaimNumber> <pat:ClaimText>130. The computer equipment of any one of claims 92 to 129, wherein the component to be configured includes a plurality of association data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00131"> <pat:ClaimNumber>131< / pat:ClaimNumber> <pat:ClaimText>131. The computer equipment of any one of claims 92 to 130, wherein, during the process of rendering, the valid association data triggers an association condition. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00132"> <pat:ClaimNumber>132< / pat:ClaimNumber> <pat:ClaimText>132. The computer equipment of any one of claims 92 to 131, wherein a key in the association data is valuated in combination with the type of the associated attribute and hierarchical relation with the associated attribute. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00133"> <pat:ClaimNumber>133< / pat:ClaimNumber> <pat:ClaimText>133. The computer equipment of any one of claims 92 to 132, wherein, if the association data contains an event, association data objects to which the event corresponds are extracted in combination with the data of the event, and the association data objects are implanted into corresponding attributes in the attribute configuration data and into corresponding events in the event data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00134"> <pat:ClaimNumber>134< / pat:ClaimNumber> <pat:ClaimText>134. The computer equipment of any one of claims 92 to 133, wherein a value of the attribute data is monitored. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00135"> <pat:ClaimNumber>135< / pat:ClaimNumber> <pat:ClaimText>135. The computer equipment of claim 134, wherein if the value of the attribute data varies, a rendering data is outputted according to corresponding data, and a component is reloaded. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00136"> <pat:ClaimNumber>136< / pat:ClaimNumber> <pat:ClaimText>136. The computer equipment of any one of claims 92 to 135, wherein the system bus connects the processor, memory, and network interface. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00137"> <pat:ClaimNumber>137< / pat:ClaimNumber> <pat:ClaimText>137. The computer equipment of any one of claims 92 to 136, wherein the processor is employed to provide computing and controlling capabilities. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00138"> <pat:ClaimNumber>138< / pat:ClaimNumber> <pat:ClaimText>138. The computer equipment of any one of claims 92 to 137, wherein the memory includes a nonvolatile storage medium and an internal memory. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00139"> <pat:ClaimNumber>139< / pat:ClaimNumber> <pat:ClaimText>139. The computer equipment of claim 138, wherein the nonvolatile storage medium stores therein an operating system. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00140"> <pat:ClaimNumber>140< / pat:ClaimNumber> <pat:ClaimText>140. The computer equipment of any one of claims 138 to 139, wherein the nonvolatile storage medium stores therein a computer program. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00141"> <pat:ClaimNumber>141< / pat:ClaimNumber> <pat:ClaimText>141. The computer equipment of any one of claims 138 to 140, wherein the nonvolatile storage medium stores therein a database. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00142"> <pat:ClaimNumber>142< / pat:ClaimNumber> <pat:ClaimText>142. The computer equipment of any one of claims 138 to 141, wherein the internal memory provides environment for running of an operating system and the computer program in the nonvolatile storage medium. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00143"> <pat:ClaimNumber>143< / pat:ClaimNumber> <pat:ClaimText>143. The computer equipment of any one of claims 92 to 142, wherein the network interface is employed to connect to an external terminal via network for communication. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00144"> <pat:ClaimNumber>144< / pat:ClaimNumber> <pat:ClaimText>144. The computer equipment of any one of claims 92 to 143, wherein the computer equipment realizes component linkage configuration method when it is executed by a processor. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00145"> <pat:ClaimNumber>145< / pat:ClaimNumber> <pat:ClaimText>145. The computer equipment of any one of claims 92 to 144, wherein the memory is a read-only memory. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00146"> <pat:ClaimNumber>146< / pat:ClaimNumber> <pat:ClaimText>146. The computer equipment of any one of claims 92 to 145, wherein the memory is a magnetic disk. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00147"> <pat:ClaimNumber>147< / pat:ClaimNumber> <pat:ClaimText>147. The computer equipment of any one of claims 92 to 146, wherein the memory is an optical disk. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00148"> <pat:ClaimNumber>148< / pat:ClaimNumber> <pat:ClaimText>148. A computer system, comprising: a device configured to: obtain demand data of a component to be configured, create a plurality of attributes of the component to be configured according to the demand data, and generate attribute data; configure linkage configuration data between the plurality of attributes according to the demand data, wherein the linkage configuration data includes linkage data and linkage relation regarding the plurality of attributes, wherein the linkage data is divided in terms of data type into a simple structure and a complex structure in the data type based on types of the attribute and control thereof, wherein the simple structure includes numerical values and wherein the complex structure includes objects and arrays, and wherein the linkage relation is divided into character string matching, numerical value interval matching, and Boolean value matching based on the types of the attribute and control thereof; match the linkage configuration data with the attribute data according to at least one preset rule, and obtain valid association data, wherein matching further includes: obtaining the data type of the linkage configuration data, and matching a corresponding target preset rule out of the preset rule according to the data type; and matching the linkage configuration data with the attribute data according to the target preset rule, and obtaining the valid association data; wherein the data type includes a single element type and a list element type, wherein the linkage configuration data is divided into the single element type and the list element type on the basis of element data types in a linkage configuration data list, wherein the single element type includes a numerical value, a character string and a Boolean value, wherein the list element type includes an object of an increasable element and an array object; when the linkage configuration data is the list element type, converting the linkage configuration data attribute fields from multi-dimension to one- dimension; recursively processing each element value; and matching according to the values of the attribute data to output the valid association data; calculate to obtain an association data object to be processed according to the valid association data and the linkage data; and employ a preset rendering mechanism to perform linkage rendering on the association data object to be processed, and generate a target component; a processor, a memory, storing therein a computer program, a network interface, and a system bus. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00149"> <pat:ClaimNumber>149< / pat:ClaimNumber> <pat:ClaimText>149. The computer system of claim 148, wherein the computer system is further configured to: configure the linkage data between the plurality of attributes according to the demand data, and determine the linkage relation between the plurality of attributes according to the linkage data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00150"> <pat:ClaimNumber>150< / pat:ClaimNumber> <pat:ClaimText>150. The computer system of any one of claims 148 to 149, wherein the computer system is further configured to: create an event of the component to be configured according to the demand data, and configure event data of the event and binding relation of the event with a corresponding attribute according to the attribute data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00151"> <pat:ClaimNumber>151< / pat:ClaimNumber> <pat:ClaimText>151. The computer system of any one of claims 148 to 150, wherein the computer system is further configured to: determine event configuration information with which the attribute is associated according to the attribute data, the event data and binding relation of the event, and render the event according to the event configuration information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00152"> <pat:ClaimNumber>152< / pat:ClaimNumber> <pat:ClaimText>152. The computer system of any one of claims 148 to 151, wherein the plurality of attributes are created at a configuration end according to user demand. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00153"> <pat:ClaimNumber>153< / pat:ClaimNumber> <pat:ClaimText>153. The computer system of any one of claims 148 to 152, wherein the attribute data is stored in a preset format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00154"> <pat:ClaimNumber>154< / pat:ClaimNumber> <pat:ClaimText>154. The computer system of any one of claims 148 to 153, wherein the attribute data is stored in JSON format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00155"> <pat:ClaimNumber>155< / pat:ClaimNumber> <pat:ClaimText>155. The computer system of any one of claims 148 to 154, wherein the linkage configuration data is stored in a preset format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00156"> <pat:ClaimNumber>156< / pat:ClaimNumber> <pat:ClaimText>156. The computer system of any one of claims 148 to 155, wherein the linkage configuration data is stored in JSON Schema format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00157"> <pat:ClaimNumber>157< / pat:ClaimNumber> <pat:ClaimText>157. The computer system of any one of claims 148 to 156, wherein a linkage restraint is configured under different data types on the basis of the JavaScript data type in combination with JSON schema specification. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00158"> <pat:ClaimNumber>158< / pat:ClaimNumber> <pat:ClaimText>158. The computer system of any one of claims 148 to 157, wherein the attributes are converted from multi-dimension to one-dimension according to hierarchical relation of the attributes. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00159"> <pat:ClaimNumber>159< / pat:ClaimNumber> <pat:ClaimText>159. The computer system of any one of claims 148 to 158, wherein the component to be configured in user demand further includes events. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00160"> <pat:ClaimNumber>160< / pat:ClaimNumber> <pat:ClaimText>160. The computer system of any one of claims 148 to 159, wherein the computer system is further configured to create events and configures binding relation of each event with a corresponding attribute and event data of each event based on the attribute data stored, and to store the binding relation of each event and the event data in a preset format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00161"> <pat:ClaimNumber>161< / pat:ClaimNumber> <pat:ClaimText>161. The computer system of claim 160, wherein the binding relation of each event is stored in JSON format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00162"> <pat:ClaimNumber>162< / pat:ClaimNumber> <pat:ClaimText>162. The computer system of claim 160, wherein the event data is stored in JSON format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00163"> <pat:ClaimNumber>163< / pat:ClaimNumber> <pat:ClaimText>163. The computer system of any one of claims 148 to 162, wherein a rendering end analyzes configuration data structure obtained from a configuration end to split the configuration data structure into at least three sets of data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00164"> <pat:ClaimNumber>164< / pat:ClaimNumber> <pat:ClaimText>164. The computer system of claim 163, wherein the configuration data structure is split into the attribute data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00165"> <pat:ClaimNumber>165< / pat:ClaimNumber> <pat:ClaimText>165. The computer system of any one of claims 163 to 164, wherein the configuration data structure is split into event data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00166"> <pat:ClaimNumber>166< / pat:ClaimNumber> <pat:ClaimText>166. The computer system of any one of claims 163 to 165, wherein the configuration data structure is split into the linkage configuration data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00167"> <pat:ClaimNumber>167< / pat:ClaimNumber> <pat:ClaimText>167. The computer system of any one of claims 148 to 166, wherein different matching rules are set for the linkage configuration data of different types. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00168"> <pat:ClaimNumber>168< / pat:ClaimNumber> <pat:ClaimText>168. The computer system of any one of claims 148 to 167, wherein the linkage configuration data of the single element type is directly matched with the values of the attribute data to output the valid association data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00169"> <pat:ClaimNumber>169< / pat:ClaimNumber> <pat:ClaimText>169. The computer system of any one of claims 148 to 168, wherein the attribute data configured by a configuration end is of a tree structure that has infinite hierarchies. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00170"> <pat:ClaimNumber>170< / pat:ClaimNumber> <pat:ClaimText>170. The computer system of any one of claims 148 to 169, wherein a multi-dimensional array realizes hierarchical relation according to the children fields in each attribute object data, and each attribute has a corresponding key under its current hierarchy. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00171"> <pat:ClaimNumber>171< / pat:ClaimNumber> <pat:ClaimText>171. The computer system of any one of claims 148 to 170, wherein recursion is performed through children and key to add a temporary index field in each attribute object. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00172"> <pat:ClaimNumber>172< / pat:ClaimNumber> <pat:ClaimText>172. The computer system of any one of claims 148 to 171, wherein the association data object to be processed is distributed to each of the corresponding attribute control, and attribute linkage rendering is realized via the rendering mechanism. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00173"> <pat:ClaimNumber>173< / pat:ClaimNumber> <pat:ClaimText>173. The computer system of any one of claims 148 to 172, wherein the computer system is further configured to perform an event logic processing including that the attribute data and event data are combined, with the event data as a starting point, the numerical value of the attribute is matched according to the attribute bound to the event, and the associated event configuration list information is output. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00174"> <pat:ClaimNumber>174< / pat:ClaimNumber> <pat:ClaimText>174. The computer system of any one of claims 148 to 173, wherein a type of the attribute data is an array. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00175"> <pat:ClaimNumber>175< / pat:ClaimNumber> <pat:ClaimText>175. The computer system of any one of claims 148 to 174, wherein a type of the attribute data is an object. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00176"> <pat:ClaimNumber>176< / pat:ClaimNumber> <pat:ClaimText>176. The computer system of any one of claims 151 to 175, wherein the event configuration information is rendered through information of an event configuration list. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00177"> <pat:ClaimNumber>177< / pat:ClaimNumber> <pat:ClaimText>177. The computer system of any one of claims 148 to 176, wherein event codes are outputted according to the combination of event template, slot and event type. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00178"> <pat:ClaimNumber>178< / pat:ClaimNumber> <pat:ClaimText>178. The computer system of any one of claims 148 to 177, wherein the component to be configured includes a page. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00179"> <pat:ClaimNumber>179< / pat:ClaimNumber> <pat:ClaimText>179. The computer system of any one of claims 148 to 178, wherein the attributes are divided in terms of the data type into character string, numerical value, Boolean value, object, or array. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00180"> <pat:ClaimNumber>180< / pat:ClaimNumber> <pat:ClaimText>180. The computer system of any one of claims 148 to 179, wherein the attribute data generated has different data structures corresponding to the different data types. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00181"> <pat:ClaimNumber>181< / pat:ClaimNumber> <pat:ClaimText>181. The computer system of any one of claims 148 to 180, wherein the data structure is an array which further covers corresponding list data and default values. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00182"> <pat:ClaimNumber>182< / pat:ClaimNumber> <pat:ClaimText>182. The computer system of any one of claims 148 to 181, wherein the linkage data includes optional values of attributes as configured. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00183"> <pat:ClaimNumber>183< / pat:ClaimNumber> <pat:ClaimText>183. The computer system of any one of claims 148 to 182, wherein the values of other attributes and events associated with the attribute are changed when the value assigned to an attribute with the linkage relation is changed. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00184"> <pat:ClaimNumber>184< / pat:ClaimNumber> <pat:ClaimText>184. The computer system of any one of claims 148 to 183, wherein, while a rendering process is being performed, configuration data obtained from the configuration end is analyzed through the rendering end, to extract therefrom the attribute data and the linkage configuration data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00185"> <pat:ClaimNumber>185< / pat:ClaimNumber> <pat:ClaimText>185. The computer system of any one of claims 148 to 184, wherein, while a rendering process is being performed, event data is extracted if the component includes an event. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00186"> <pat:ClaimNumber>186< / pat:ClaimNumber> <pat:ClaimText>186. The computer system of any one of claims 148 to 185, wherein the component to be configured includes a plurality of association data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00187"> <pat:ClaimNumber>187< / pat:ClaimNumber> <pat:ClaimText>187. The computer system of any one of claims 148 to 186, wherein, during the process of rendering, the valid association data triggers an association condition. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00188"> <pat:ClaimNumber>188< / pat:ClaimNumber> <pat:ClaimText>188. The computer system of any one of claims 148 to 187, wherein a key in the association data is valuated in combination with the type of the associated attribute and hierarchical relation with the associated attribute. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00189"> <pat:ClaimNumber>189< / pat:ClaimNumber> <pat:ClaimText>189. The computer system of any one of claims 148 to 188, wherein, if the association data contains an event, association data objects to which the event corresponds are extracted in combination with the data of the event, and the association data objects are implanted into corresponding attributes in the attribute configuration data and into corresponding events in the event data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00190"> <pat:ClaimNumber>190< / pat:ClaimNumber> <pat:ClaimText>190. The computer system of any one of claims 148 to 189, wherein a value of the attribute data is monitored. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00191"> <pat:ClaimNumber>191< / pat:ClaimNumber> <pat:ClaimText>191. The computer system of claim 190, wherein if the value of the attribute data varies, a rendering data is outputted according to corresponding data, and a component is reloaded. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00192"> <pat:ClaimNumber>192< / pat:ClaimNumber> <pat:ClaimText>192. The computer system of any one of claims 148 to 191, wherein the system bus connects the processor, memory, and network interface. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00193"> <pat:ClaimNumber>193< / pat:ClaimNumber> <pat:ClaimText>193. The computer system of any one of claims 148 to 192, wherein the processor is employed to provide computing and controlling capabilities. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00194"> <pat:ClaimNumber>194< / pat:ClaimNumber> <pat:ClaimText>194. The computer system of claim 193, wherein the memory includes a nonvolatile storage medium and an internal memory. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00195"> <pat:ClaimNumber>195< / pat:ClaimNumber> <pat:ClaimText>195. The computer system of claim 194, wherein the nonvolatile storage medium stores therein an operating system. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00196"> <pat:ClaimNumber>196< / pat:ClaimNumber> <pat:ClaimText>196. The computer system of any one of claims 194 to 195, wherein the nonvolatile storage medium stores therein a computer program. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00197"> <pat:ClaimNumber>197< / pat:ClaimNumber> <pat:ClaimText>197. The computer system of any one of claims 194 to 196, wherein the nonvolatile storage medium stores therein a database. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00198"> <pat:ClaimNumber>198< / pat:ClaimNumber> <pat:ClaimText>198. The computer system of any one of claims 194 to 197, wherein the internal memory provides environment for running of an operating system and the computer program in the nonvolatile storage medium. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00199"> <pat:ClaimNumber>199< / pat:ClaimNumber> <pat:ClaimText>199. The computer system of any one of claims 148 to 198, wherein the network interface is employed to connect to an external terminal via network for communication. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00200"> <pat:ClaimNumber>200< / pat:ClaimNumber> <pat:ClaimText>200. The computer system of any one of claims 148 to 199, wherein the computer system realizes component linkage configuration method when it is executed by a processor. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00201"> <pat:ClaimNumber>201< / pat:ClaimNumber> <pat:ClaimText>201. The computer system of any one of claims 148 to 200, wherein the memory is a read-only memory. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00202"> <pat:ClaimNumber>202< / pat:ClaimNumber> <pat:ClaimText>202. The computer system of any one of claims 148 to 201, wherein the memory is a magnetic disk. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00203"> <pat:ClaimNumber>203< / pat:ClaimNumber> <pat:ClaimText>203. The computer system of any one of claims 148 to 202, wherein the memory is an optical disk. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00204"> <pat:ClaimNumber>204< / pat:ClaimNumber> <pat:ClaimText>204. A component linkage configuration method, the method comprises: obtaining demand data of a component to be configured, creating a plurality of attributes of the component to be configured according to the demand data, and generating attribute data; configuring linkage configuration data between the plurality of attributes according to the demand data, wherein the linkage configuration data includes linkage data and linkage relation regarding the plurality of attributes, wherein the linkage data is divided in terms of data type into a simple structure and a complex structure in the data type based on types of the attribute and control thereof, wherein the simple structure includes numerical values and wherein the complex structure includes objects and arrays, and wherein the linkage relation is divided into character string matching, numerical value interval matching, and Boolean value matching based on the types of the attribute and control thereof; matching the linkage configuration data with the attribute data according to at least one preset rule, and obtaining valid association data, wherein matching further includes: obtaining the data type of the linkage configuration data, and matching a corresponding target preset rule out of the preset rule according to the data type; and matching the linkage configuration data with the attribute data according to the target preset rule, and obtaining the valid association data; wherein the data type includes a single element type and a list element type, wherein the linkage configuration data is divided into the single element type and the list element type on the basis of element data types in a linkage configuration data list, wherein the single element type includes a numerical value, a character string and a Boolean value, wherein the list element type includes an object of an increasable element and an array object; when the linkage configuration data is the list element type, converting the linkage configuration data attribute fields from multi-dimension to one- dimension; recursively processing each element value; and matching according to the values of the attribute data to output the valid association data; calculating to obtain an association data object to be processed according to the valid association data and the linkage data; and employing a preset rendering mechanism to perform linkage rendering on the association data object to be processed, and generating a target component. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00205"> <pat:ClaimNumber>205< / pat:ClaimNumber> <pat:ClaimText>205. The method of claim 204, the method further comprises: configuring the linkage data between the plurality of attributes according to the demand data, and determining the linkage relation between the plurality of attributes according to the linkage data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00206"> <pat:ClaimNumber>206< / pat:ClaimNumber> <pat:ClaimText>206. The method of any one of claims 204 to 205, the method further comprises: creating an event of the component to be configured according to the demand data, and configuring event data of the event and binding relation of the event with a corresponding attribute according to the attribute data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00207"> <pat:ClaimNumber>207< / pat:ClaimNumber> <pat:ClaimText>207. The method of any one of claims 204 to 206, the method further comprises: determining event configuration information with which the attribute is associated according to the attribute data, the event data and binding relation of the event, and rendering the event according to the event configuration information. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00208"> <pat:ClaimNumber>208< / pat:ClaimNumber> <pat:ClaimText>208. The method of any one of claims 204 to 207, wherein the plurality of attributes are created at the configuration end according to user demand. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00209"> <pat:ClaimNumber>209< / pat:ClaimNumber> <pat:ClaimText>209. The method of any one of claims 204 to 208, wherein the attribute data is stored in a preset format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00210"> <pat:ClaimNumber>210< / pat:ClaimNumber> <pat:ClaimText>210. The method of any one of claims 204 to 209, wherein the attribute data is stored in JSON format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00211"> <pat:ClaimNumber>211< / pat:ClaimNumber> <pat:ClaimText>211. The method of any one of claims 204 to 210, wherein the linkage configuration data is stored in a preset format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00212"> <pat:ClaimNumber>212< / pat:ClaimNumber> <pat:ClaimText>212. The method of any one of claims 204 to 211, wherein the linkage configuration data is stored in JSON Schema format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00213"> <pat:ClaimNumber>213< / pat:ClaimNumber> <pat:ClaimText>213. The method of any one of claims 204 to 212, wherein a linkage restraint is configured under different data types on the basis of the JavaScript data type in combination with JSON schema specification. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00214"> <pat:ClaimNumber>214< / pat:ClaimNumber> <pat:ClaimText>214. The method of any one of claims 204 to 213, wherein the attributes are converted from multi- dimension to one-dimension according to hierarchical relation of the attributes. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00215"> <pat:ClaimNumber>215< / pat:ClaimNumber> <pat:ClaimText>215. The method of any one of claims 204 to 214, wherein the component to be configured in user demand further includes events. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00216"> <pat:ClaimNumber>216< / pat:ClaimNumber> <pat:ClaimText>216. The method of any one of claims 204 to 215, wherein the method further creates events and configures binding relation of each event with a corresponding attribute and event data of each event based on the attribute data stored, and to store the binding relation of each event and the event data in a preset format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00217"> <pat:ClaimNumber>217< / pat:ClaimNumber> <pat:ClaimText>217. The method of claim 216, wherein the binding relation of each event is stored in JSON format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00218"> <pat:ClaimNumber>218< / pat:ClaimNumber> <pat:ClaimText>218. The method of claim 216, wherein the event data is stored in JSON format. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00219"> <pat:ClaimNumber>219< / pat:ClaimNumber> <pat:ClaimText>219. The method of any one of claims 204 to 218, wherein a rendering end analyzes configuration data structure obtained from a configuration end to split the configuration data structure into at least three sets of data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00220"> <pat:ClaimNumber>220< / pat:ClaimNumber> <pat:ClaimText>220. The method of claim 219, wherein the configuration data structure is split into the attribute data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00221"> <pat:ClaimNumber>221< / pat:ClaimNumber> <pat:ClaimText>221. The method of any one of claims 219 to 220, wherein the configuration data structure is split into event data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00222"> <pat:ClaimNumber>222< / pat:ClaimNumber> <pat:ClaimText>222. The method of any one of claims 219 to 221, wherein the configuration data structure is split into the linkage configuration data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00223"> <pat:ClaimNumber>223< / pat:ClaimNumber> <pat:ClaimText>223. The method of any one of claims 204 to 222, wherein different matching rules are set for the linkage configuration data of different types. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00224"> <pat:ClaimNumber>224< / pat:ClaimNumber> <pat:ClaimText>224. The method of any one of claims 204 to 223, wherein the linkage configuration data of the single element type is directly matched with the values of the attribute data to output the valid association data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00225"> <pat:ClaimNumber>225< / pat:ClaimNumber> <pat:ClaimText>225. The method of any one of claims 204 to 225, wherein the attribute data configured by the configuration end is of a tree structure that has infinite hierarchies. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00226"> <pat:ClaimNumber>226< / pat:ClaimNumber> <pat:ClaimText>226. The method of any one of claims 204 to 225, wherein a multi-dimensional array realizes hierarchical relation according to the children fields in each attribute object data, and each attribute has a corresponding key under its current hierarchy. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00227"> <pat:ClaimNumber>227< / pat:ClaimNumber> <pat:ClaimText>227. The method of any one of claims 204 to 226, wherein recursion is performed through children and key to add a temporary index field in each attribute object. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00228"> <pat:ClaimNumber>228< / pat:ClaimNumber> <pat:ClaimText>228. The method of any one of claims 204 to 227, wherein the association data object to be processed is distributed to each of the corresponding attribute control, and attribute linkage rendering is realized via the rendering mechanism. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00229"> <pat:ClaimNumber>229< / pat:ClaimNumber> <pat:ClaimText>229. The method of any one of claims 204 to 228, wherein the method further includes performing an event logic processing including that the attribute data and event data are combined, with the event data as a starting point, the numerical value of the attribute is matched according to the attribute bound to the event, and the associated event configuration list information is output. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00230"> <pat:ClaimNumber>230< / pat:ClaimNumber> <pat:ClaimText>230. The method of any one of claims 204 to 229, wherein a type of the attribute data is an array. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00231"> <pat:ClaimNumber>231< / pat:ClaimNumber> <pat:ClaimText>231. The method of any one of claims 204 to 230, wherein a type of the attribute data is an object. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00232"> <pat:ClaimNumber>232< / pat:ClaimNumber> <pat:ClaimText>232. The method of any one of claims 207 to 231, wherein the event configuration information is rendered through information of an event configuration list. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00233"> <pat:ClaimNumber>233< / pat:ClaimNumber> <pat:ClaimText>233. The method of any one of claims 204 to 232, wherein event codes are outputted according to the combination of event template, slot and event type. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00234"> <pat:ClaimNumber>234< / pat:ClaimNumber> <pat:ClaimText>234. The method of any one of claims 204 to 233, wherein the component to be configured includes a page. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00235"> <pat:ClaimNumber>235< / pat:ClaimNumber> <pat:ClaimText>235. The method of any one of claims 204 to 234, wherein the plurality of attributes are pre-created according to demand data proposed by the user, and corresponding attribute data is generated. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00236"> <pat:ClaimNumber>236< / pat:ClaimNumber> <pat:ClaimText>236. The method of any one of claims 204 to 235, wherein the attributes are divided in terms of the data type into character string, numerical value, Boolean value, object, or array. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00237"> <pat:ClaimNumber>237< / pat:ClaimNumber> <pat:ClaimText>237. The method of any one of claims 204 to 236, wherein the attribute data generated has different data structures corresponding to the different data types. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00238"> <pat:ClaimNumber>238< / pat:ClaimNumber> <pat:ClaimText>238. The method of any one of claims 204 to 237, wherein the data structure is an array which further covers corresponding list data and default values. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00239"> <pat:ClaimNumber>239< / pat:ClaimNumber> <pat:ClaimText>239. The method of any one of claims 204 to 238, wherein the linkage data includes optional values of attributes as configured. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00240"> <pat:ClaimNumber>240< / pat:ClaimNumber> <pat:ClaimText>240. The method of any one of claims 204 to 239, wherein the values of other attributes and events associated with the attribute are changed when the value assigned to an attribute with the linkage relation is changed. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00241"> <pat:ClaimNumber>241< / pat:ClaimNumber> <pat:ClaimText>241. The method of any one of claims 204 to 240, wherein, while a rendering process is being performed, configuration data obtained from the configuration end is analyzed through the rendering end, to extract therefrom the attribute data and the linkage configuration data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00242"> <pat:ClaimNumber>242< / pat:ClaimNumber> <pat:ClaimText>242. The method of any one of claims 204 to 241, wherein, while a rendering process is being performed, event data is extracted if the component includes an event. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00243"> <pat:ClaimNumber>243< / pat:ClaimNumber> <pat:ClaimText>243. The method of any one of claims 204 to 242, wherein the component to be configured includes a plurality of association data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00244"> <pat:ClaimNumber>244< / pat:ClaimNumber> <pat:ClaimText>244. The method of any one of claims 204 to 243, wherein, during the process of rendering, the valid association data triggers an association condition. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00245"> <pat:ClaimNumber>245< / pat:ClaimNumber> <pat:ClaimText>245. The method of any one of claims 204 to 244, wherein a key in the association data is valuated in combination with the type of the associated attribute and hierarchical relation with the associated attribute. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00246"> <pat:ClaimNumber>246< / pat:ClaimNumber> <pat:ClaimText>246. The method of any one of claims 204 to 245, wherein, if the association data contains an event, association data objects to which the event corresponds are extracted in combination with the data of the event, and the association data objects are implanted into corresponding attributes in the attribute configuration data and into corresponding events in the event data. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00247"> <pat:ClaimNumber>247< / pat:ClaimNumber> <pat:ClaimText>247. The method of any one of claims 204 to 246, wherein a value of the attribute data is monitored. < / pat:ClaimText> < / pat:Claim> <pat:Claim com:id="CLM-00248"> <pat:ClaimNumber>248< / pat:ClaimNumber> <pat:ClaimText>248. The method of claim 247, wherein if the value of the attribute data varies, a rendering data is outputted according to corresponding data, and a component is reloaded. < / pat:ClaimText> < / pat:Claim> < / pat:Claims>