CN111488357A

CN111488357A - Method and device for realizing digital account of service data block chain

Info

Publication number: CN111488357A
Application number: CN202010271070.6A
Authority: CN
Inventors: 吉建勋; 杨慧
Original assignee: Beijing Ruice Technology Co Ltd
Current assignee: Beijing Ruice Technology Co Ltd
Priority date: 2020-04-08
Filing date: 2020-04-08
Publication date: 2020-08-04

Abstract

The application discloses a method and a device for realizing a digital account of a service data block chain, wherein the method comprises the following steps: the block chain node stores the state after the user operation in a tree structure mode; the tree structure comprises a state tree and a relation tree, wherein the state tree stores states after user operation, and the relation tree stores incidence relations among the states after user operation. According to the method and the device, the user digital account is arranged on the business data block chain, and after business data are linked, the user can manage digital assets on the block chain through the digital account, so that the use experience of a business data block chain system of the user is improved.

Description

Method and device for realizing digital account of service data block chain

Technical Field

The invention relates to the technical field of internet big data, and discloses a method and a device for realizing a digital account of a service data block chain.

Background

Currently, the blockchain technology is a distributed stored ledger that uses technologies such as encryption algorithm and consensus mechanism. With the use of blockchain technology, more and more internet data is stored on the blockchain.

In the existing block chain, only transaction data can be stored, wherein the transaction data comprises a transfer party address, a receiving party address and a transfer amount; for various service data (such as evidence storage data, traceability data, financial data, travel data, search data, self-media data, research data, advertisement data, e-commerce data, community data, knowledge question and answer data, knowledge payment data, shared bicycle data, recruitment data, living service data, renting data, voting data, OTO data (also called online to offline data), social data, praise data, evaluation data, internet appointment data and other internet related data), not only the data per se but also the association relationship between the data on the block chain need to be expressed.

In addition, the current blockchain account mainly expresses user assets, namely various point balances owned by the user; for the above-mentioned business data after uplink, the user's assets are not just point balances.

The foregoing description is merely for convenience in understanding and is not to be construed as limiting the prior art to the present application.

Disclosure of Invention

Based on the above problems, the present application discloses a method and an apparatus for implementing a digital account of a service data block chain, in which a user digital account is set on the service data block chain, and after chaining service data, a user can manage digital assets on the block chain through the digital account, thereby improving user experience of a service data block chain system.

The first aspect of the present application discloses a method for implementing a digital account of a service data block chain, where the method includes:

the block chain node stores the state after the user operation in a tree structure mode;

the tree structure comprises a state tree and a relation tree, wherein the state tree stores states after user operation, and the relation tree stores incidence relations among the states after user operation.

In one possible implementation, the value of a leaf node in the state tree stores one or more of an integration state, an entity state, a user state, and a message state.

In one possible implementation, leaf nodes in the relational tree store a tree root of a relational sub-tree, and values of leaf nodes of the relational sub-tree store one or more of a user state-user operation state, a user state-integral state, a user state-entity state, and a user state-message state; or

The value of the leaf node in the relation tree stores one or more of user state-user operation state, user state-integral state, user state-entity state and user state-message state in an array or hash table mode.

In a possible implementation manner, any one of the information of the user state, the entity state, the integration state, the user state-user operation state, the user state-integration state, the user state-entity state, and the user state-message state is stored in a database supporting attribute query in a form of a data table, so that a user can query according to an attribute field in the data table; the information corresponds to a data table, any line in any data table corresponds to a piece of state information, and the information comprises a plurality of lines of state information; the database supporting attribute query comprises a relational database and a memory database; or

And any one of the user state, the entity state, the integral state, the user state-user operation state, the user state-integral state, the user state-entity state and the user state-message state is stored by adopting a KV database and is stored in a key value pair mode.

In one possible implementation, in the relationship tree of the user status-the message status, the message status includes one or both of an advertisement message and a product coupon; wherein the content of the first and second substances,

the advertisement message responds to the click operation of a user, and the user state-point state relation tree stores the point state corresponding to the advertisement message;

and the commodity discount roll responds to the pickup operation of a user, and the user state-entity state relation tree stores the entity state corresponding to the commodity discount roll.

In one possible implementation, the relationship tree and the state tree use a merkel tree or an MPT tree, the MPT tree is a merkel tree variation of a tree structure fused with a prefix tree, and the merkel tree is a Merkle PatriciaTree.

A second aspect of the present application discloses a device for implementing a digital account of a service data block chain, which is characterized in that the device is a block chain node; wherein the content of the first and second substances,

the block chain node stores the state after the user operation in a tree structure mode; the tree structure comprises a state tree and a relation tree, wherein the state tree stores states after user operation, and the relation tree stores incidence relations among the states after user operation.

In one possible implementation, the user operation data is operation data of a user on the internet, and the user operation data includes one or more of evidence storage data, traceability data, financial data, travel data, search data, self-media data, research data, advertisement data, e-commerce data, community data, knowledge question and answer data, knowledge payment data, shared bicycle data, recruitment data, living service data, rentals data, voting data, online-to-offline data, social data, praise data, evaluation data and online booking data.

In one possible implementation, the user operation data includes one or more of a timestamp, an operation user address, an operated address, an operation type, a value of an operation, a credit address, a signature of the user on the user operation data, and a hash value of the user operation data; the operation type comprises an operation of a user on an entity and an operation on the credit, and the operated address comprises an operation address on the entity and addresses of other operation users.

In one possible implementation manner, the attributes of the user operation data include an associated attribute and a non-associated attribute; wherein the attribute value of the associated attribute is automatically increased or decreased according to the data state after the user operation.

A third aspect of the present application provides a computer-readable storage medium, which stores computer instructions, and when the computer instructions are executed by a processor, the computer instructions implement any one of the above-mentioned technical solutions.

A fourth aspect of the present application provides an electronic device, which includes a processor configured to execute any one of the above technical solutions.

According to the method and the device, the user digital account is arranged on the business data block chain, and after business data are linked, the user can manage digital assets on the block chain through the digital account, so that the use experience of a business data block chain system of the user is improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a schematic flow chart illustrating a method for implementing a digital account of a service data block chain according to the present application;

fig. 2 is a schematic block head structure diagram of a service data block chain according to the present application;

fig. 3 is a schematic structural diagram of a digital account implementing device of a service data blockchain disclosed in the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The terms "first" and "second" in this application are used for convenience of understanding only, and are not to be construed as sequential or limiting in any way.

For the purpose of facilitating understanding of the embodiments of the present invention, the following description will be further explained with reference to specific embodiments, which are not to be construed as limiting the embodiments of the present invention.

Blockchains are generally divided into three types: public chain (Public Blockchain), private chain (PrivateBlockchain) and alliance chain (Consortium Blockchain). In addition, there are various types of combinations, such as private chain + federation chain, federation chain + public chain, and other different combinations. The most decentralized of these is the public chain. The public chain is represented by bitcoin and ether house, and the participators joining the public chain can read the data record on the chain, participate in transaction, compete for accounting right of new blocks, and the like.

Furthermore, each participant (i.e., node) is free to join and leave the network and perform related operations. Private chains are the opposite, with the network's write rights controlled by an organization or organization and the data read rights specified by the organization. Briefly, a private chain can be a weakly centralized system with strictly limited and few participating nodes. This type of blockchain is more suitable for use within a particular establishment.

Based on the basic characteristics of a blockchain, a blockchain is usually composed of several blocks. The time stamps corresponding to the creation time of the block are recorded in the blocks respectively, and all the blocks form a time-ordered data chain according to the time stamps recorded in the blocks strictly.

The real data generated by the physical world can be constructed into a standard transaction (transaction) format supported by a block chain, then is issued to the block chain, is identified by node equipment in the block chain, and is packed into a block by the node equipment serving as an accounting node in the block chain after the identification is achieved, and is subjected to persistent evidence storage in the block chain.

In the field of blockchain, an important concept is Account (Account); taking an ether house as an example, the ether house generally divides an account into an external account and a contract account; the external account is an account directly controlled by the user; and the contract account is created by the user through an external account, the account containing the contract code (i.e. the smart contract).

Of course, for some blockchain items derived based on the ethernet framework, the account types supported by the blockchain may be further expanded, and are not particularly limited in this specification.

For accounts in a blockchain, the account status of the account is usually maintained through a structure. When a transaction in a block is executed, the status of the account associated with the transaction in the block chain is also typically changed.

Taking etherhouses as an example, the structure of an account usually includes fields such as Balance, Nonce, Code, and storage. Wherein:

a Balance field for maintaining the current account Balance of the account;

a Nonce field for the number of transactions for the account; the counter is used for guaranteeing that each transaction can be processed only once, and replay attack is effectively avoided.

A code field for maintaining a contract code for the account; in practical applications, only the hash value of the contract code is typically maintained in the code field; thus, the code field is also commonly referred to as a codehash field. For external accounts, this field is null.

storage field to maintain the storage of the account (default to empty). In practical application, the storage field only maintains the root node of an MPT (Merkle Patricia Trie) tree constructed based on the storage content of the account; thus, the storage field is also commonly referred to as the storageRoot field.

Wherein, for the external account, the code field and storage field shown above are null values.

Most blockchain items typically use Merkle trees; alternatively, the data is stored and maintained based on the data structure of the Merkle tree. Taking etherhouses as an example, the etherhouses use MPT tree (a Merkle tree variation) as a data organization form for organizing and managing important data such as account status, transaction information, and the like.

The Etherhouse designs three MPT trees, namely an MPT state tree, an MPT transaction tree and an MPT receipt tree, aiming at data needing to be stored and maintained in a block chain.

The MPT state tree is an MPT tree organized by account state data (state) of all accounts in the block chain; the MPT transaction tree is transaction data (transaction) in a block and is organized into the MPT tree; the MPT receipt tree is an MPT tree organized by transaction receipts (receipts) corresponding to each transaction generated after the transaction in the block is completed. The hash values of the root nodes of the MPT state tree, MPT transaction tree, and MPT receipt tree shown above are all added to the block header.

Wherein the MPT transaction tree and the MPT receipt tree correspond to tiles, each tile having its own MPT transaction tree and MPT receipt tree. The MPT state tree is a global MPT tree, which does not correspond to a specific tile, but covers account state data of all accounts in the tile chain.

The present specification discloses a method for implementing a digital account of a service data block chain, as shown in fig. 1, where the service data block chain system includes a plurality of block chain nodes; the method includes S101-S102.

The entity information in the present specification refers to abstraction of objective objects and also refers to specific objective objects, the entity information includes associated attributes and non-associated attributes, and the associated attributes refer to that attribute values can be increased or decreased; the user information refers to description information of a user, and the user information comprises a user address; the point information is point information issued by the user, and is point information other than the original points on the block chain, and the point information includes the name and the total amount of the point.

S101, storing the state after the user operates the block chain link point in a tree structure mode.

S102, the tree structure comprises a state tree and a relation tree, the state tree stores states after user operation, and the relation tree stores incidence relations among the states after user operation.

In one example, the value of a leaf node in the state tree stores one or more of an integration state, an entity state, a user state, and a message state.

For example, the entity is a commodity of an internet e-commerce platform, and the user can initiate an operation of purchasing the commodity, namely, a point transfer operation (point is transferred from the address of the operating user to the address of the operated user) for a point corresponding to the commodity entity; the user can also initiate a comment or a praise operation for the commodity, namely a user operation for the commodity entity.

Associated attributes in an attribute type, for example: the number of praise is automatically increased for the same commodity or the self-media (such as pictures, texts and small videos circled by WeChat friends) after praise is performed by different users. Non-associated attributes, such as: and after different users comment the comment content, the user searches the commodity on the block chain and can see the comments of the different users.

The points are user issued points, for example: after a user can pass the notarization and securitize the house, a point is issued on the block chain, and the point uniquely represents the house property on the block chain; alternatively, the house may be securitized, a predetermined number of points issued, possession of the point will have ownership of the house, and will have equal ownership of the house lease or change. In addition, the block chain is provided with native scores which can be used for restricting the operation of the user on the block chain, so that the user is prevented from using the resources of the block chain system without limit; for example: after the users on the blockchain are registered, the users are operated on the blockchain, and the native credits are required to be collated so as to uplink the user operation data.

For the message state, the message is sent by the user B to the user A, and the message can be a commodity coupon, an advertisement, a bonus red packet and the like. The commodity coupon indicates that the user A acquires the commodity entity after the user A clicks; after the user A clicks the advertisement, the user A can obtain the reward of points for watching the advertisement and also obtain the reward of entities for watching the advertisement according to the setting of the user B on the advertisement; and after the user A clicks the point red packet, the user A can obtain the points in the point red packet.

In the service data block chain of the present specification, digital assets owned by a user include entity assets, integral assets, message assets, and user operation data assets.

In one example, leaf nodes in the relational tree store a tree root of a relational sub-tree whose values store one or more of user state-user operational state, user state-integration state, user state-entity state, and user state-message state.

In one example, values of leaf nodes in the relationship tree store one or more of user state-user operation state, user state-integral state, user state-entity state, and user state-message state in an array or hash table.

At this time, the relationship between the user state and the integration state is considered. A user may have multiple points, for example: a user has both native credits on the blockchain and other types of credits. The incidence relation can describe the one-to-many relation between the user and the score, and meanwhile, the user can conveniently inquire. It should be noted that a user in the blockchain system at least has the native scores of the blockchain system; it is possible to have credits issued by other users or by themselves. The same kind of credits can be owned by a plurality of users.

For the relationship between user state-user operational state. The same user can carry out multiple operations on the service data block chain; for example: user A, conducting investigation operation a; and performing advertisement clicking operation c; at another moment, E-commerce purchase operation b is carried out, and self-media approval d is carried out; the data ownership of the user operation of the user a belongs to a, so a group of corresponding relations is needed to store the user operation. These user operations are all user operation assets of the user.

For the relationship between user state-entity state. A user may own multiple entities, and the same entity may be owned by different users. For a single user, there may be different types of electronic shop entities, there may be multiple purchased goods entities, there may be multiple questionnaire entities for answers, multiple published self-media entities, and so on: these entities are all entity data assets of the user.

For the relationship between user state-message state. As above, a user may own a plurality of messages, and a certain message may also be owned by a plurality of users. For an individual user, other merchant users can push messages such as commodity coupons, advertisements, bonus red packages and the like to the individual user, the messages belong to the message assets of the individual user, and the relationship between the user and the message state needs to be stored.

As can be seen from the above, the digital account of the user includes one or more of a user status-message status, a user status-entity status, a user status-credit status, and a user status-user operation status.

In one example, the user status-the message status relationship tree, the message status includes one or both of an advertising message and a product coupon.

In one example, any one of the user state, the entity state, the integral state, the user state-user operation state, the user state-integral state, the user state-entity state and the user state-message state is stored in a database supporting attribute query in the form of a data table, so that a user can query according to an attribute field in the data table; the information corresponds to a data table, any line in any data table corresponds to a piece of state information, and the information comprises a plurality of lines of state information; the database supporting attribute query comprises a relational database and an in-memory database.

The relational database can adopt MySql, and the memory database adopts a MongoDB database.

In one example, any one of the user status, the entity status, the integral status, the user status-user operation status, the user status-integral status, the user status-entity status, and the user status-message status is stored in a KV database, and is stored in a key value pair manner.

In one example, the state tree or the relationship tree employs a merkel tree or an MPT tree, whose root is stored in a chunk header; wherein the MPT Tree is a Mercker Tree variation of a Tree structure fused with a prefix Tree, and the Mercker Tree is a Merkle Patricia Tree Tree.

In one example, the user operation data is operation data of a user on the internet, and the user operation data comprises one or more of evidence storage data, traceability data, financial data, travel data, search data, self-media data, research data, advertisement data, e-commerce data, community data, knowledge question and answer data, knowledge payment data, shared bicycle data, recruitment data, life service data, house renting data, voting data, online-offline data, social data, praise data, evaluation data and net appointment data.

In one example, the user operation data includes one or more of a timestamp, an operation user address, an operated address, an operation type, a value of an operation, a credit address, a signature of the user on the user operation data, and a hash value of the user operation data; the operation type comprises an operation of a user on an entity and an operation on the credit, and the operated address comprises an operation address on the entity and addresses of other operation users.

As described above, any one of the user state (e.g., Account field), point state (e.g., Asset field), entity state (e.g., Object field), user state-entity state (e.g., Account-Object field), user state-point state (e.g., Account-Asset field), user state-Message state (e.g., Account-Message field), and user state-user Action state (e.g., Account-Action) may be implemented by using an MPT state tree or a Mercker tree, and the tree roots of various MPT state trees are stored in the block header. As shown in FIG. 2, the user Action of the tile store (e.g., the Action field), and the root of the MPT status tree of the Receipt status of the on-chain database store (e.g., the Recept field) are also stored in the tile header.

In the above, the states are stored in an MPT state tree manner, and a user can query through address information; directly adopting a user address, a point address and an entity address to inquire the state aiming at the user state, the point state and the entity state; and querying the state by using the user address according to the user state-entity state, the user state-user operation state, the user state-integral state and the user state-message state.

In addition, the user address can be obtained by carrying out multiple times of hash operation according to the user public key; the point address or the entity address may be obtained by a user operation of creating a point or an entity, for example: and carrying out multiple times of hash operation on the user operation, and selecting characters with preset digits from the obtained hash value as integral addresses or entity addresses.

In the application, the user digital account is arranged on the business data block chain, and after business data is linked, the user can manage digital assets on the block chain through the digital account, so that the use experience of a business data block chain system of the user is improved; and various state data in the digital account adopt a database supporting attribute query, so that the user can conveniently access the database, and the query efficiency is improved.

In addition, the present specification discloses a device for implementing a digital account of a service data blockchain, where a service data blockchain system includes a plurality of blockchain nodes, and the device is a blockchain node.

And the block chain node stores the state after the user operates in a tree structure mode.

In one example, leaf nodes in the relational tree store a tree root of a relational sub-tree, values of leaf nodes of the relational sub-tree store one or more of user state-user operational state, user state-integration state, user state-entity state, and user state-message state; or

In one example, any one of the user state, the entity state, the integral state, the user state-user operation state, the user state-integral state, the user state-entity state and the user state-message state is stored in a database supporting attribute query in the form of a data table, so that a user can query according to an attribute field in the data table; the information corresponds to a data table, any line in any data table corresponds to a piece of state information, and the information comprises a plurality of lines of state information; the database supporting attribute query comprises a relational database and a memory database; or

In one example, the attributes of the user operation data include an associated attribute and a non-associated attribute; wherein the attribute value of the associated attribute is automatically increased or decreased according to the data state after the user operation.

The same or similar parts in the above device embodiments and the above method embodiments can be referred to each other, and are not described herein again.

The present specification also discloses a computer readable storage medium storing computer instructions which, when executed by a processor, implement any one of the above-mentioned technical solutions.

The present specification also discloses an electronic device comprising a processor configured to perform any of the above-described technical solutions.

Meanwhile, the application also provides an embodiment of the entity device.

Fig. 3 shows a schematic diagram of a computer device, which may include: a processor 310, a memory 320, an input/output interface 330, a communication interface 340, and a bus 350. Wherein the processor 340, the memory 320, the input/output interface 330, and the communication interface 340 are communicatively coupled to each other within the device via a bus 350.

The processor 310 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits, and is configured to execute related programs to implement the technical solutions provided in the embodiments of the present specification.

The Memory 320 may be implemented in the form of a ROM (Read Only Memory), a RAM (Random access Memory), a static storage device, a dynamic storage device, or the like. The memory 320 may store an operating system and other application programs, and when the technical solution provided by the embodiments of the present specification is implemented by software or firmware, the relevant program codes are stored in the memory 320 and called to be executed by the processor 310.

The input/output interface 330 is used for connecting an input/output module to realize information input and output. The i/o module may be configured as a component in a device (not shown) or may be external to the device to provide a corresponding function. The input devices may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output devices may include a display, a speaker, a vibrator, an indicator light, etc.

The communication interface 340 is used for connecting a communication module (not shown in the figure) to implement communication interaction between the present device and other devices. The communication module can realize communication in a wired mode (such as USB, network cable and the like) and also can realize communication in a wireless mode (such as mobile network, WIFI, Bluetooth and the like).

Bus 350 includes a path that transfers information between the various components of the device, such as processor 310, memory 320, input/output interface 330, and communication interface 340.

It should be noted that although the above-mentioned device only shows the processor 310, the memory 320, the input/output interface 330, the communication interface 340 and the bus 350, in a specific implementation, the device may also include other components necessary for normal operation. In addition, those skilled in the art will appreciate that the above-described apparatus may also include only those components necessary to implement the embodiments of the present description, and not necessarily all of the components shown in the figures.

Those of skill would further appreciate that the various illustrative components and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied in hardware, a software module executed by a processor, or a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

The above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the present invention in further detail, and it should be understood that the above-mentioned embodiments are only illustrative of the present invention and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made within the scope of the present invention should be included in the scope of the present invention.

Claims

1. The method for realizing the digital account of the service data block chain is characterized by comprising the following steps:

2. The digital account implementation method of claim 1, wherein values of leaf nodes in the state tree store one or more of an integration state, an entity state, a user state, and a message state.

3. The method of claim 1 or 2, wherein leaf nodes in the relational tree store a tree root of a relational sub-tree, and values of leaf nodes of the relational sub-tree store one or more of user state-user operation state, user state-credit state, user state-entity state, and user state-message state; or

4. The method for implementing digital account according to claim 3, wherein any one of the user status, the entity status, the credit status, the user status-user operation status, the user status-credit status, the user status-entity status and the user status-message status is stored in a database supporting attribute query in the form of a data table, so that the user can query according to the attribute field in the data table; the information corresponds to a data table, any line in any data table corresponds to a piece of state information, and the information comprises a plurality of lines of state information; the database supporting attribute query comprises a relational database and a memory database; or

5. The method of claim 3, wherein the user status-the message status relationship tree includes one or both of advertisement messages and product coupons; wherein the content of the first and second substances,

6. The method of claim 1, wherein the relationship tree and the state tree are merkel trees or MPT trees, the MPT trees are merkel tree varieties of tree structures fused with prefix trees, and the merkel trees are MerklePatriciaTree trees.

7. The digital account implementation device of the business data block chain is characterized in that the device is a block chain node; wherein the content of the first and second substances,

8. The digital account enforcement apparatus of claim 7, wherein the values of leaf nodes in the state tree store one or more of an integration state, an entity state, a user state, and a message state.

9. The apparatus of claim 7 or 8, wherein a leaf node in the relational tree stores a root of a relational sub-tree, and wherein values of leaf nodes of the relational sub-tree store one or more of user state-user operation state, user state-credit state, user state-entity state, and user state-message state; or

10. The digital account implementing device according to claim 9, wherein any one of the user status, the entity status, the credit status, the user status-user operation status, the user status-credit status, the user status-entity status, and the user status-message status is stored in a database supporting attribute query in the form of a data table, so that a user can query according to an attribute field in the data table; the information corresponds to a data table, any line in any data table corresponds to a piece of state information, and the information comprises a plurality of lines of state information; the database supporting attribute query comprises a relational database and a memory database; or