CN104993906B - A kind of method and system of message transmission - Google Patents

Abstract

The invention discloses a method and system for message transmission, belonging to the technical field of communication. The method includes: the source system and the target system set their data structure format to a common format; the source system creates a data object; the source system encodes the created data object according to the JSON format; the source system sends the encoded data to the target system object; the target system decodes the received data object according to the JSON format; the target system obtains data from the decoded data object; wherein, the source system and the target system are heterogeneous systems. In the present invention, by setting the data structure formats of the source system and the target system to a common format, both the source system and the target system can accurately and effectively identify the messages carried in the common format, and the operating systems or dependencies of the source system and the target system It has nothing to do with the programming development platform, and realizes the message transmission of heterogeneous systems.

Description

Method and system for message transmission

technical field

The present invention relates to the field of communication technology, in particular to a method and system for message transmission.

Background technique

Heterogeneous systems refer to at least two systems with different operating systems or different dependent programming development platforms. Due to different operating systems or programming development platforms, the standards followed by message transmission (including data structures carrying messages, etc.) Middleware can be realized.

Existing message middleware usually only targets two specified types of mutually heterogeneous systems, such as .NET system and JAVA system. When the .NET system transmits a message to the JAVA system, it receives the message that conforms to the standard of the .NET system sent by the .NET system; according to the set standard, converts the format of the message conforming to the standard of the .NET system to obtain a message conforming to the JAVA system Standard message; send a message that conforms to the standard of the JAVA system to the JAVA system. When the JAVA system transmits a message to the .NET system, the operation objects of the above process can be exchanged.

In the process of realizing the present invention, the inventor finds that there are at least the following problems in the prior art:

Message middleware is only for two specified types of heterogeneous systems, if a heterogeneous system includes more than two specified types of heterogeneous systems, such as .NET system, JAVA system, C++ system Such a system requires, for example, message middleware for .NET system and JAVA system, and message middleware for JAVA system and C++ system to realize message transmission of heterogeneous systems. However, the standard for format conversion of message middleware is set by each company in order to promote its own products, and it has not been unified. As a result, there are differences in the interface of each message middleware, and it is difficult for each message middleware to Effective matching and fusion are realized, which leads to the impossibility of message transmission in heterogeneous systems.

Contents of the invention

In order to solve the problem that the message transmission of heterogeneous systems cannot be realized in the prior art, the embodiment of the present invention provides a method and system for message transmission. Described technical scheme is as follows:

In the first aspect, an embodiment of the present invention provides a method for message transmission, which is suitable for message transmission between heterogeneous systems, and the method includes:

The source system sets the data structure format of the source system as a common format;

Create the data object, and the created data object meets the requirements of the general format for the data object;

Encoding the created data object according to JSON format;

sending the encoded data object to a target system;

Wherein, the source system and the target system are mutually heterogeneous systems, and the common format is a data structure format commonly adopted by the source system and the target system.

Optionally, the requirements of the general format for data objects include:

The characters and case of the data structure name are consistent in the system to which the data structure belongs;

The characters and capitalization of member names in the data structure are consistent in the system to which the data structure belongs;

The description method of the member type in the data structure is consistent in the system to which the data structure belongs;

The nesting relationship in the data structure is consistent in the system to which the data structure belongs;

The name of the data structure and the member names in the data structure are not repeated in the system to which the data structure belongs.

In the second aspect, an embodiment of the present invention provides a method for message transmission, which is suitable for message transmission between heterogeneous systems, and the method includes:

The target system sets the data structure format of the target system as a common format;

receiving said data object sent by the source system;

Decoding the received data object according to the JSON format based on the requirements of the general format for the data object;

obtaining data from the decoded data object;

Wherein, the source system and the target system are mutually heterogeneous systems, and the common format is a data structure format commonly adopted by the source system and the target system.

Optionally, the requirements of the general format for data objects include:

The characters and case of the data structure name are consistent in the system to which the data structure belongs;

The characters and capitalization of member names in the data structure are consistent in the system to which the data structure belongs;

The description method of the member type in the data structure is consistent in the system to which the data structure belongs;

The nesting relationship in the data structure is consistent in the system to which the data structure belongs;

The name of the data structure and the member names in the data structure are not repeated in the system to which the data structure belongs.

In a third aspect, an embodiment of the present invention provides a source system, where the source system and the target system are heterogeneous systems, and the source system includes:

A setting module, configured to set the data structure format of the source system to a common format, and the common format is a data structure format commonly adopted by the source system and the target system;

A creating module, configured to create the data object, and the created data object meets the requirements of the general format for the data object;

An encoding module, configured to encode the created data object in JSON format;

A sending module, configured to send the encoded data object to the target system.

Optionally, the requirements of the general format for data objects include:

The characters and case of the data structure name are consistent in the system to which the data structure belongs;

The characters and capitalization of member names in the data structure are consistent in the system to which the data structure belongs;

The description method of the member type in the data structure is consistent in the system to which the data structure belongs;

The nesting relationship in the data structure is consistent in the system to which the data structure belongs;

The name of the data structure and the member names in the data structure are not repeated in the system to which the data structure belongs.

In a fourth aspect, an embodiment of the present invention provides a target system, where the target system and the source system are heterogeneous systems, and the target system includes:

A setting module, configured to set the data structure format of the target system as a common format, and the common format is a data structure format commonly adopted by the source system and the target system;

a receiving module, configured to receive the data object sent by the source system;

A decoding module, configured to decode the received data object in JSON format based on the requirements of the general format for the data object;

An acquisition module, configured to acquire data from the decoded data object.

Optionally, the requirements of the general format for data objects include:

The characters and case of the data structure name are consistent in the system to which the data structure belongs;

The characters and capitalization of member names in the data structure are consistent in the system to which the data structure belongs;

The description method of the member type in the data structure is consistent in the system to which the data structure belongs;

The nesting relationship in the data structure is consistent in the system to which the data structure belongs;

The name of the data structure and the member names in the data structure are not repeated in the system to which the data structure belongs.

In a fifth aspect, an embodiment of the present invention provides a message transmission system, the system includes a source system and a target system that are heterogeneous systems,

The source system is used to set the data structure format of the source system to a general format; create a data object, and the created data object meets the requirements of the general format for the data object; The data object is encoded according to the JSON format; the encoded data object is sent to the target system;

The target system is configured to set the data structure format of the target system to a common format; receive the data object sent by the source system; The data object is decoded according to the JSON format; data is obtained from the decoded data object;

Wherein, the common format is a data structure format commonly adopted by the source system and the target system.

Optionally, the requirements of the general format for data objects include:

The characters and case of the data structure name are consistent in the system to which the data structure belongs;

The characters and capitalization of member names in the data structure are consistent in the system to which the data structure belongs;

The description method of the member type in the data structure is consistent in the system to which the data structure belongs;

The nesting relationship in the data structure is consistent in the system to which the data structure belongs;

The name of the data structure and the member names in the data structure are not repeated in the system to which the data structure belongs.

The beneficial effects brought by the technical solution provided by the embodiments of the present invention are:

By setting the data structure format of the source system and the target system to a common format, both the source system and the target system can accurately and effectively identify the messages carried in the common format, and the operating systems or dependent programming of the source system and the target system The development platform is independent, and the message transmission of heterogeneous systems is realized.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings that need to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention. For those skilled in the art, other drawings can also be obtained based on these drawings without creative effort.

FIG. 1 is an application scenario diagram of a method for message transmission provided by an embodiment of the present invention;

FIG. 2 is an interaction flowchart of a method for message transmission provided by Embodiment 1 of the present invention;

FIG. 3 is a schematic structural diagram of a source system provided by Embodiment 2 of the present invention;

FIG. 4 is a schematic structural diagram of a target system provided by Embodiment 3 of the present invention;

FIG. 5 is a schematic structural diagram of a message transmission system provided by Embodiment 4 of the present invention.

Detailed ways

In order to make the object, technical solution and advantages of the present invention clearer, the implementation manner of the present invention will be further described in detail below in conjunction with the accompanying drawings.

The application scenario (that is, heterogeneous system) of the method for message transmission provided by the embodiment of the present invention will be briefly introduced below with reference to FIG. 1 . As shown in Figure 1, the four systems of system A, system B, system C, and system D, which are heterogeneous systems, are respectively connected to an intermediate device E (such as a message agent), so as to realize system A, system B, system C, System D Message transmission between the four systems.

It should be noted that the number of systems included in the heterogeneous system and the specific connection manner between the systems are only examples, and the present invention is not limited thereto.

Embodiment one

An embodiment of the present invention provides a method for message transmission, which is suitable for message transmission between heterogeneous systems. Referring to FIG. 2, the method includes:

Step 101: the source system sets the data structure format of the source system as a common format, and the target system sets the data structure format of the target system as a common format.

Wherein, the sender of the message is the source system, and the receiver of the message is the target system. The source system and the target system are heterogeneous systems. Specifically, the operating systems of the source system and the target system are different or the programming platforms used for development are different. For example (different operating systems), the source system is a Linux system, and the target system is a Windows system. Another example (different programming platforms are used for development), the source system is the .NET system, and the target system is the JAVA system.

The common format is the data structure format commonly adopted by the source system and the target system. Further, the requirements of the universal format on data objects satisfy all types of systems, that is, the universal format is applicable to all types of systems. For example, system A's requirement for data objects is requirement 1, system B's requirement for data objects is requirement 2, and the requirement for data objects in the general format is to meet requirements 1 and 2 at the same time. When the data formats of system A and system B are both set to a common format, system A and system B have the same requirements for data objects, and this requirement applies to both system A and system B. Similarly, after step 101 is executed, the data formats of the source system and the target system are set to a common format, so the data formats of the source system and the target system are the same, and the requirements for data objects are the same, and the requirements can be It is applicable to the source system and the target system at the same time, so that the messages transmitted between the source system and the target system can be effectively identified, and the message transmission between the source system and the target system is realized.

Specifically, the type may be an operating system, or a programming platform used for development. More specifically, when the type is an operating system, the general format is applicable to systems of all operating systems, such as Linux systems and Windows systems. When the type is a programming platform, the general format is applicable to systems developed by all programming platforms, such as .NET system, JAVA system, C system, C++ system, etc.

Specifically, the general format requirements for data objects may include:

The characters and case of the data structure name are consistent in the system to which the data structure belongs. For example, DataStructName1 cannot be written as datastructname1;

The characters and case of the member names in the data structure are consistent in the system to which the data structure belongs. For example, MemberName1 cannot be written as membername1;

The description method of the member type in the data structure is consistent in the system to which the data structure belongs, for example, a string is defined by string, and an integer is described by int;

The nesting relationship in the data structure is consistent in the system to which the data structure belongs. For example, the member MemberName1 in the data structure DataStructName1 cannot be written as the member MemberName1 in the data structure datastructname1, or the member membername1 in the data structure DataStructName1;

The name of the data structure and the member names in the data structure are not duplicated in the system to which the data structure belongs. For example, the name of the data structure and the member names in the data structure cannot both be Name1.

For example, the data structure format that meets the requirements of the general format for data objects can be as follows:

Public class DataStructName1

{

MemberType MemberName1;

…

MemberType MemberNameN;

}

Among them, DataStructName1 represents the name of the data structure, MemberType represents the type of members in the data structure, and MemberName1, ..., MemberNameN represent the names of members in the data structure.

It can be understood that when step 101 is executed, the source system and the target system can set their data structure formats to a common format at the same time, or set their data structure formats to a common format respectively, which is not limited in the present invention.

After step 101 is executed, since the data structure format of the source system and the target system are both set to a general format, the requirements of the general format on data objects meet all types of systems, so the transmission of messages between heterogeneous systems is closely related to the operation of each system Regardless of the different systems or the programming platform used for development, both the source system and the target system can accurately and effectively identify messages carried in a common format, realizing the uniformity of message transmission between heterogeneous systems.

In particular, when a heterogeneous system includes more than two types of systems, since the data structure formats of all systems are set to a common format, all systems can recognize messages carried in a common format, and there is no need for system-specific The number of types of message middleware increases, resulting in cumbersome heterogeneous systems, and there is no problem that various message middleware cannot cooperate.

Step 102: the source system creates a data object, and the created data object meets the requirements of the common format for the data object.

Specifically, the creation of the data object in step 102 may be the same as the specific implementation of creating the data object in the prior art, and the present application may only change the requirements followed during the creation of the data object, which will not be described in detail here.

For example, the data object created can be as follows:

DataStructName dataSample = new DataStructName();

dataSample.MemberName1 = "MemberValue1";

…

dataSample.MemberNameN = "MemberValueN";

Among them, dataSample represents the name of the data structure, MemberName1, ..., MemberNameN represent the member names in the data structure, and MemberValue1, ..., MemberValueN represent the values corresponding to the member names in the data structure.

Step 103: Encode the created data object according to the JSON format.

Among them, encoding is serialization, which writes multiple data objects expressed in the form of a data structure into a series of sequences. A data object includes a member name and corresponding value in the data structure, and the sequence is in turn each member name and the corresponding value.

For example, the encoded data object can be as follows:

{"MemberName1": "MemberValue1", ..., "MemberNameN": "MemberValueN"}

Among them, MemberName1, ..., MemberNameN represent the member names in the data structure, and MemberValue1, ..., MemberValueN represent the values corresponding to the member names in the data structure.

It is easy to know that JSON is a lightweight data exchange format, using a text format completely independent of language, easy to read and write for humans, and easy for machines to parse and generate. In particular, compared with the currently commonly used lightweight XML, JSON not only has comparable readability, extensibility, and low encoding difficulty as XML, but also has good decoding difficulty, so the performance of JSON is better than XML. Moreover, XML has many structural characters, which greatly occupy the transmission bandwidth. Therefore, the transmission efficiency of JSON is higher and the bandwidth of the communication channel is smaller.

Step 104: the source system sends the encoded data object to the target system.

Optionally, a message agent (Transform Agent, TA for short) may be set between the source system and the target system. During the execution of step 104, the source system first sends the encoded data object to the message broker, and then the message broker sends the encoded data object to the target system.

Specifically, this step 104 may include:

The message broker receives the data objects sent by the source system;

Cache the received data object;

Send the cached data object to the target system.

Understandably, the message agent caches the encoded data object and then sends it to the target system instead of sending it to the target system immediately, so as to prevent the target system from not receiving the data object due to the busy system and improve the reliability of data object transmission. Preferably, the message agent can delete the cached data object after receiving a confirmation message from the target system indicating that the data object has been received.

Step 105: The target system decodes the received data object according to the JSON format based on the requirements of the common format for the data object.

Among them, decoding is the inverse process of encoding, that is, deserialization, which converts each member name and corresponding value represented by a string of sequences into a data structure form, and a member name and corresponding value in the data structure represent a data object .

Understandably, since both the source system and the target system set their data structure format as a common format, and encode and decode based on the JSON format, after the target system decodes the received data object, it can obtain data object.

For example, the decoded data object is as follows:

dataSample.MemberName1 = "MemberValue1";

…

dataSample.MemberNameN = "MemberValueN";

Among them, dataSample represents the name of the data structure, MemberName1, ..., MemberNameN represent the member names in the data structure, and MemberValue1, ..., MemberValueN represent the values corresponding to the member names in the data structure.

Step 106: The target system obtains data from the decoded data object.

Specifically, since both the source system and the target system set their data structure formats to a common format, the target system can obtain data from the decoded data object.

For example, obtained from the decoded data object, there is a data structure dataSample including N members, respectively MemberName1, ..., MemberNameN, and the corresponding values of each member are MemberValue1, ..., MemberValueN.

In the embodiment of the present invention, by setting the data structure format of the source system and the target system to a common format, both the source system and the target system can accurately and effectively identify the messages carried in the common format, and the operating systems of the source system and the target system It has nothing to do with the programming and development platform it depends on, and realizes the message transmission of heterogeneous systems.

Embodiment two

An embodiment of the present invention provides a source system, see Figure 3, the source system includes:

The setting module 201 is used to set the data structure format of the source system to a common format, and the common format is a data structure format commonly adopted by the source system and the target system;

The creation module 202 is used to create a data object, and the created data object meets the requirements of the general format for the data object;

An encoding module 203, configured to encode the created data object in JSON format;

The sending module 204 is configured to send the encoded data object to the target system.

Specifically, the general format requirements for data objects may include:

The characters and case of the data structure name are consistent in the system to which the data structure belongs;

The characters and capitalization of member names in the data structure are consistent in the system to which the data structure belongs;

The description method of the member type in the data structure is consistent in the system to which the data structure belongs;

The nesting relationship in the data structure is consistent in the system to which the data structure belongs;

The name of the data structure and the member names in the data structure are not duplicated in the system to which the data structure belongs.

In the embodiment of the present invention, by setting the data structure format of the source system and the target system to a common format, both the source system and the target system can accurately and effectively identify the messages carried in the common format, and the operating systems of the source system and the target system It has nothing to do with the programming and development platform it depends on, and realizes the message transmission of heterogeneous systems.

Embodiment Three

The embodiment of the present invention provides a kind of target system, referring to Fig. 4, this target system comprises:

The setting module 301 is used to set the data structure format of the target system as a common format, and the common format is a data structure format commonly adopted by the source system and the target system;

A receiving module 302, configured to receive the data object sent by the source system;

The decoding module 303 is used to decode the received data object according to the JSON format based on the requirements of the general format for the data object;

An acquisition module 304, configured to acquire data from the decoded data object.

Specifically, the general format requirements for data objects may include:

The characters and case of the data structure name are consistent in the system to which the data structure belongs;

The characters and capitalization of member names in the data structure are consistent in the system to which the data structure belongs;

The description method of the member type in the data structure is consistent in the system to which the data structure belongs;

The nesting relationship in the data structure is consistent in the system to which the data structure belongs;

The name of the data structure and the member names in the data structure are not duplicated in the system to which the data structure belongs.

In the embodiment of the present invention, by setting the data structure format of the source system and the target system to a common format, both the source system and the target system can accurately and effectively identify the messages carried in the common format, and the operating systems of the source system and the target system It has nothing to do with the programming and development platform it depends on, and realizes the message transmission of heterogeneous systems.

Embodiment Four

An embodiment of the present invention provides a message transmission system. Referring to FIG. 5 , the system includes a source system 501 and a target system 502 that are heterogeneous systems.

The source system 501 is used to set the data structure format of the source system to a general format; create a data object, and the created data object meets the requirements of the general format for the data object; encode the created data object according to the JSON format; Send the encoded data object;

The target system 502 is used to set the data structure format of the target system to a general format; receive the data object sent by the source system; based on the requirements of the general format for the data object, decode the received data object according to the JSON format; Get data from the data object;

Among them, the common format is a data structure format commonly adopted by the source system and the target system.

Specifically, the general format requirements for data objects may include:

The characters and case of the data structure name are consistent in the system to which the data structure belongs;

The characters and capitalization of member names in the data structure are consistent in the system to which the data structure belongs;

The description method of the member type in the data structure is consistent in the system to which the data structure belongs;

The nesting relationship in the data structure is consistent in the system to which the data structure belongs;

The name of the data structure and the member names in the data structure are not duplicated in the system to which the data structure belongs.

Optionally, the system can also include:

The message agent 503 is configured to receive the data object sent by the source system; cache the received data object; and send the cached data object to the target system.

In the embodiment of the present invention, by setting the data structure format of the source system and the target system to a common format, both the source system and the target system can accurately and effectively identify the messages carried in the common format, and the operating systems of the source system and the target system It has nothing to do with the programming and development platform it depends on, and realizes the message transmission of heterogeneous systems.

It should be noted that: the source system, target system, and message transmission system provided by the above embodiments only use the division of the above-mentioned functional modules as an example for illustration during message transmission. In practical applications, the above-mentioned functions can be allocated by Completion of different functional modules means that the internal structure of the system is divided into different functional modules to complete all or part of the functions described above. In addition, the source system, target system, message transmission system and message transmission method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process thereof is detailed in the method embodiments, and will not be repeated here.

The serial numbers of the above embodiments of the present invention are for description only, and do not represent the advantages and disadvantages of the embodiments.

Those of ordinary skill in the art can understand that all or part of the steps for implementing the above embodiments can be completed by hardware, and can also be completed by instructing related hardware through a program. The program can be stored in a computer-readable storage medium. The above-mentioned The storage medium mentioned may be a read-only memory, a magnetic disk or an optical disk, and the like.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included in the protection of the present invention. within range.

Claims (5)

1. a kind of method of message transmission, is transmitted, which is characterized in that the method packet suitable for the message between heterogeneous system It includes：

The data structure format of the source system is set as general format by source system；

Data object is created, the data object of establishment meets requirement of the general format to the data object；

The data object of establishment is encoded according to JSON forms；

The data object after encoding is sent to goal systems；

Wherein, the source system and the goal systems heterogeneous system each other, the general format are the source system and described The data structure format that goal systems uses jointly；

The general format requires to include data object：

The character and capital and small letter of data structure title are consistent in the system belonging to the data structure；

The character of member Name and capital and small letter are consistent in the system belonging to the data structure in data structure；

The describing mode of member type is consistent in the system belonging to the data structure in data structure；

Nest relation is consistent in the system belonging to the data structure in data structure；

Data structure title is not repeated with member Name in data structure in the system belonging to the data structure.

2. a kind of method of message transmission, is transmitted, which is characterized in that the method packet suitable for the message between heterogeneous system It includes：

The data structure format of the goal systems is set as general format by goal systems；

The data object that reception source system is sent；

Requirement based on the general format to the data object carries out the data object of reception according to JSON forms Decoding；

Data are obtained from the decoded data object；

Wherein, the source system and the goal systems heterogeneous system each other, the general format are the source system and described The data structure format that goal systems uses jointly；

The general format requires to include data object：

The character and capital and small letter of data structure title are consistent in the system belonging to the data structure；

The character of member Name and capital and small letter are consistent in the system belonging to the data structure in data structure；

The describing mode of member type is consistent in the system belonging to the data structure in data structure；

Nest relation is consistent in the system belonging to the data structure in data structure；

Data structure title is not repeated with member Name in data structure in the system belonging to the data structure.

3. an introduces a collection system, the source system and goal systems heterogeneous system each other, which is characterized in that the source system includes：

Setting module, for the data structure format of the source system to be set as general format, the general format is described The data structure format that source system and the goal systems use jointly；

Creation module, for creating data object, the data object of establishment meets the general format to the data pair The requirement of elephant；

Coding module encodes for the data object to establishment according to JSON forms；

Sending module, for sending the data object after encoding to the goal systems；

The general format requires to include data object：

The character and capital and small letter of data structure title are consistent in the system belonging to the data structure；

The character of member Name and capital and small letter are consistent in the system belonging to the data structure in data structure；

The describing mode of member type is consistent in the system belonging to the data structure in data structure；

Nest relation is consistent in the system belonging to the data structure in data structure；

Data structure title is not repeated with member Name in data structure in the system belonging to the data structure.

4. a kind of goal systems, the goal systems and source system heterogeneous system each other, which is characterized in that the goal systems packet It includes：

Setting module, for the data structure format of the goal systems to be set as general format, the general format is institute State the data structure format that source system and the goal systems use jointly；

Receiving module, for receiving the data object that the source system is sent；

Decoder module, for based on requirement of the general format to the data object, being pressed to the data object of reception It is decoded according to JSON forms；

Acquisition module, for obtaining data from the decoded data object；

The general format requires to include data object：

The character and capital and small letter of data structure title are consistent in the system belonging to the data structure；

The character of member Name and capital and small letter are consistent in the system belonging to the data structure in data structure；

The describing mode of member type is consistent in the system belonging to the data structure in data structure；

Nest relation is consistent in the system belonging to the data structure in data structure；

Data structure title is not repeated with member Name in data structure in the system belonging to the data structure.

5. a kind of system of message transmission, the system comprises the source system and goal systems of heterogeneous system each other, feature exists In,

The source system is used for, and the data structure format of the source system is set as general format；Data object is created, is created The data object meet requirement of the general format to the data object；To the data object of establishment according to JSON forms are encoded；The data object after encoding is sent to the goal systems；

The goal systems is used for, and the data structure format of the goal systems is set as general format；Receive the source system The data object that system is sent；Requirement based on the general format to the data object, to the data pair of reception As being decoded according to JSON forms；Data are obtained from the decoded data object；

Wherein, the general format is the data structure format that the source system and the goal systems use jointly；

The general format requires to include data object：

The character and capital and small letter of data structure title are consistent in the system belonging to the data structure；

The character of member Name and capital and small letter are consistent in the system belonging to the data structure in data structure；

The describing mode of member type is consistent in the system belonging to the data structure in data structure；

Nest relation is consistent in the system belonging to the data structure in data structure；

Data structure title is not repeated with member Name in data structure in the system belonging to the data structure.