CN111897883A

CN111897883A - Entity model construction method and device, electronic equipment and medium

Info

Publication number: CN111897883A
Application number: CN202010681450.7A
Authority: CN
Inventors: 方红; 李娜; 王欢; 李曼
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2020-07-15
Filing date: 2020-07-15
Publication date: 2020-11-06
Anticipated expiration: 2040-07-15
Also published as: CN111897883B

Abstract

The disclosure provides a method, a device, a system and an electronic device for constructing an entity model, wherein the method comprises the following steps: acquiring an entity information set and an entity relation information set from text information aiming at a specified field based on a preset rule; for each entity information in the entity information set, determining core entity information from the entity information set based on the quantity of the entity relationship information associated with the entity information in the entity relationship information set; and constructing an entity model consisting of business objects based on the core entity information, the entity relation information and the entity information, wherein the entity model comprises at least one business object, and each business object comprises core entity information and entity information related to the core entity information.

Description

Entity model construction method and device, electronic equipment and medium

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a method and an apparatus for building an entity model, an electronic device, and a medium.

Background

At present, with the continuous development of enterprise-level business architecture, a business model of the enterprise-level business architecture is constructed based on entities, processes and products, and the business model can provide guiding significance for enterprise decision from multiple angles.

In carrying out the presently disclosed concept, the inventors have found that there are at least the following problems in the related art. In the related technology, some data problems exist to restrict the development of enterprises, for example, data of different departments are difficult to correlate, and the data is confused, misunderstood and redundant due to the fact that standards of multiple data sources are not uniform, so that enterprise resources are wasted.

Disclosure of Invention

In view of the above, the present disclosure provides a method, an apparatus, an electronic device, and a medium for building a solid model for unifying standards of multiple data sources.

One aspect of the present disclosure provides a solid model construction method, including: acquiring an entity information set and an entity relation information set from text information aiming at a specified field based on a preset rule; for each entity information in the entity information set, determining core entity information from the entity information set based on the quantity of the entity relationship information associated with the entity information in the entity relationship information set; and constructing an entity model consisting of business objects based on the core entity information, the entity relation information and the entity information, wherein the entity model comprises at least one business object, and each business object comprises core entity information and entity information related to the core entity information.

The entity model construction method provided by the embodiment of the disclosure determines the core entity information based on the entity relationship information associated with each entity information, and further constructs the business object based on the core entity information to generate the entity model composed of a plurality of business objects, thereby realizing that a uniform entity model is provided for an enterprise by adopting a structured and standardized language. The generated entity model is generated based on the text information of the designated field, and the entity model and the field have a corresponding relation so as to be used for determining entity information and the like in the required entity model based on the field, thereby realizing the sharing of the entity model among departments in an enterprise, being beneficial to reducing the communication cost among the departments and facilitating the asset management of the enterprise based on the entity model.

One aspect of the present disclosure provides an entity model construction apparatus including a set acquisition module, a core entity determination module, and a model construction module. The set acquisition module is used for acquiring an entity information set and an entity relation information set from the text information aiming at the specified field based on a preset rule. The core entity determining module is used for determining core entity information from the entity information set based on the number of entity relationship information associated with the entity information in the entity relationship information set for each entity information in the entity information set. The model building module is used for building an entity model composed of business objects based on the core entity information, the entity relation information and the entity information, wherein the entity model comprises at least one business object, and each business object comprises core entity information and entity information related to the core entity information.

Another aspect of the present disclosure provides a solid model building system, including: a business entity module and a business object module. The business entity module is used for determining entity associated information, and the entity associated information comprises entity information and entity relation information. The business object module is used for determining the business object based on the entity information and the entity relation information so as to build the entity model based on the business object.

Another aspect of the present disclosure provides an electronic device comprising one or more processors and a storage for storing executable instructions that, when executed by the processors, implement the method as described above.

Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions for implementing the method as described above when executed.

Another aspect of the disclosure provides a computer program comprising computer executable instructions for implementing the method as described above when executed.

Drawings

The above and other objects, features and advantages of the present disclosure will become more apparent from the following description of embodiments of the present disclosure with reference to the accompanying drawings, in which:

FIG. 1 schematically illustrates an application scenario of a mockup construction method, apparatus, electronic device and medium according to an embodiment of the disclosure;

FIG. 2 schematically illustrates an exemplary system architecture to which mockup construction methods, apparatus, electronic devices and media may be applied, according to embodiments of the disclosure;

FIG. 3 schematically shows a flow chart of a solid model construction method according to an embodiment of the present disclosure;

fig. 4 schematically shows a schematic diagram of entity information according to an embodiment of the present disclosure;

FIG. 5 schematically illustrates a schematic diagram of a business object according to an embodiment of the disclosure;

FIG. 6 schematically illustrates a display interface diagram for editing business objects according to an embodiment of the disclosure;

FIG. 7 schematically illustrates a standardized schematic of a mockup according to an embodiment of the disclosure;

FIG. 8 schematically shows an instantiation diagram of a mockup in accordance with an embodiment of the present disclosure;

FIG. 9 schematically shows a block diagram of a mockup construction apparatus according to an embodiment of the disclosure;

FIG. 10 schematically illustrates a block diagram of a mockup construction system according to an embodiment of the disclosure;

FIG. 11 schematically illustrates a logical diagram of a mockup construction process according to an embodiment of the disclosure; and

FIG. 12 schematically shows a block diagram of an electronic device according to an embodiment of the disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.

Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a convention analogous to "A, B or at least one of C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B or C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). The terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more features.

The embodiment of the disclosure provides a solid model construction method, a solid model construction device, electronic equipment and a medium. The entity model construction method comprises a core entity determination process and a modeling process. In the core entity determining process, firstly, an entity information set and an entity relation information set are acquired from text information aiming at a specified field based on a preset rule. Then, for each entity information in the entity information set, core entity information is determined from the entity information set based on the number of entity relationship information in the entity relationship information set that is associated with the entity information. After the core entity determining process is completed, a modeling process is carried out, and an entity model composed of business objects is constructed based on the core entity information, the entity relation information and the entity information, wherein the entity model comprises at least one business object, and each business object comprises core entity information and entity information related to the core entity information.

Fig. 1 schematically illustrates an application scenario of a mockup construction method, apparatus, electronic device, and medium according to an embodiment of the present disclosure.

The business architecture relates to aspects of value creation, business operation and internal management of a commercial bank, the asset structure is complex, systematic analysis is lacked in the value creation process of the conventional commercial bank, the business architecture and the assets of an Internet Technology (IT) architecture are rarely in systematic corresponding relation, and the IT architecture cannot reflect the requirements and changes of business in time.

As shown in FIG. 1, on the left side is a business architecture including a product model (e.g., products provided to a user in a display interface of an application, such as various financial products, financial services, etc.), a process model, and a physical model. The right side is an IT framework which comprises an interactive component (UC), A Transaction Service (ATS), A Component Service (ACS) and an object service (BOS). The business architecture relates to aspects of value creation, business operation and internal management of the commercial bank, the asset structure is complex, the value creation process of the commercial bank in the related technology lacks systematic analysis, and the business and the Internet Technology (IT) architecture assets are rarely in systematic correspondence. The entity model construction method provided by the disclosure is to provide a unified entity model for an enterprise by adopting a structure and a standardized language under the background of butt joint of a business architecture and an IT architecture, so that users of different departments can conveniently work in the standardized language, the communication cost between the departments is reduced, and the data management of the enterprise is facilitated.

N in fig. 1 is a positive integer greater than 0, wherein the values of n in fig. 1 may be the same or different, and are only used to indicate a one-to-one or one-to-many relationship. For example, the value of n in the business use case may be the same as or different from the value of n in the flow model.

In order to facilitate understanding of the technical solution of the present disclosure, a business architecture building process is first exemplified.

Firstly, the business field is divided according to a plurality of dimensions based on the value flow, and a plurality of value chains aiming at the plurality of dimensions are respectively obtained. The business mode of the commercial bank is analyzed, and the business fields are divided according to different value flows, so that the components of the business fields in various dimensions can be obtained conveniently. Specifically, the plurality of value chains for the plurality of dimensions includes: an activity value chain (also referred to as an activity model), a task flow (also referred to as a task group or a task model), and a task component (also referred to as a component model), the activity value chain including at least one task flow, the task flow including at least one task component. Wherein the activity value chain comprises an activity start point and an activity end point, the activity value chain being associated with a plurality of mockups. The task process corresponds to a business process, and the business process corresponds to at least one product and serves one entity. The task components correspond to an entity model and a product model.

The entities associated with each value chain and the products required by the entities are then obtained. The entity can be characterized by the entity model, data of the entity model can be stored in a database, and in actual use, the entity model can be refined and digitalized to obtain a C 'model, and the C' model can be operated by an object service (BOS). Specifically, for a business architecture that has been built, entities related to each value chain and products required by the entities, such as financial products, can be determined and acquired based on the business architecture.

Then, respectively aiming at the value chain, the entity and the product of a plurality of dimensions, a business model, an entity model and a product model aiming at the plurality of dimensions are constructed, wherein one-to-one or one-to-many mapping relation exists between the entity and the entity model in the business field.

FIG. 2 schematically illustrates an exemplary system architecture to which mockup construction methods, apparatus, electronic devices, and media may be applied, according to embodiments of the disclosure. It should be noted that fig. 2 is only an example of a system architecture to which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, and does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios.

As shown in fig. 2, the system architecture 200 according to this embodiment may include

terminal devices

201, 202, 203, a network 204 and a server 205. The network 204 may include a plurality of gateways, routers, hubs, network wires, etc. to provide a medium for communication links between the

end devices

201, 202, 203 and the server 205. Network 204 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.

The user may use the

terminal devices

201, 202, 203 to interact with other terminal devices and the server 205 through the network 204 to receive or send information, etc., such as sending a business object request, a core entity request, an entity model building request, an information modification instruction, receiving a processing result, etc. The

terminal devices

201, 202, 203 may be installed with various communication client applications, such as a bank application, a monitoring application, an operation and maintenance application, a web browser application, a search application, an office application, an instant messaging tool, a mailbox client, social platform software, and other applications (for example only).

The

terminal devices

201, 202, 203 include, but are not limited to, smart phones, virtual reality devices, augmented reality devices, tablets, laptop computers, and the like.

The server 205 may receive the request and process the request. For example, the server 205 may be a back office management server, a cluster of servers, or the like. The background management server can analyze and process the received service object request, model management request, etc., and feed back the processing result (such as service object information, entity model, etc.) to the terminal device.

It should be noted that the model maintenance method provided by the embodiment of the present disclosure may be generally performed by the server 205. Accordingly, the model maintenance apparatus provided by the embodiments of the present disclosure may be generally disposed in the server 205. The model maintenance method provided by the embodiment of the present disclosure may also be performed by a server or a server cluster that is different from the server 205 and is capable of communicating with the

terminal devices

201, 202, 203 and/or the server 205.

It should be understood that the number of terminal devices, networks, and servers are merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

FIG. 3 schematically shows a flow chart of a solid model construction method according to an embodiment of the disclosure.

As shown in fig. 3, the method may include operations S301 to S305.

In operation S301, an entity information set and an entity relationship information set are acquired from text information for a specified domain based on a preset rule.

In this embodiment, an organization (e.g., a business) may involve many domains, and if text information of all the domains is mixed together for entity model modeling, the constructed entity model may be inconsistent with reality. Therefore, only information required for building the solid model can be acquired from the text information of the specified domain.

The text information of the designated area is text information formed in a fixed format and a sentence pattern. For example, a user fills in information desired to be entered in a template provided by the system to form more standard structured textual information. This facilitates the system to obtain the required information from the text information based on the identifier in the template, etc. For example, the text message includes "for … …", wherein the text message may be an identifier, and the following content is a value for the purpose.

In one embodiment, obtaining the entity information set and the entity relationship information set from the text information for the specified domain based on the preset rule may include the following operations.

Firstly, the text information is divided into sentences to obtain a first sentence comprising entity information and a second sentence comprising entity relation information. For example, text information is divided into sentences based on periods. Each sentence may correspond to a topic, such as a first sentence corresponding to entity information, a second sentence corresponding to entity relationship information, a third sentence corresponding to entity attribute information, and a fourth sentence corresponding to domain and instance information. Specifically, topic-related information for each sentence may be set in the template.

And then, performing word segmentation on the first sentence and the second sentence respectively to obtain a first word segmentation result and a second word segmentation result. The word segmentation method can be the same as the prior art, such as the word segmentation of sentences based on a dictionary, the dictionary can be a general dictionary, and can also be a special dictionary aiming at different fields, such as a financial dictionary, so as to improve the accuracy of the word segmentation result.

Then, entity information is extracted from the first segmentation result based on a first identification corresponding to the entity information, and entity relation information is extracted from the second segmentation result based on a second identification corresponding to the entity relation information. For example, an "entity" may serve as an identifier for entity information. "relationship entities," "relationships between," and the like may be identifiers of entity relationships.

For example, entity information can be extracted from "entity order-receiving user": "order receiving user". For another example, the entity information "entity order receiving user" and "entity order receiving organization" may be extracted from the "relation entity between the entity order receiving user and the entity order receiving organization" and the "entity relation information" order receiving user and order receiving organization ".

Further, the entity information may be classified based on relationships between the entities and the core entity, e.g., the entity types may include core entities, subordinate entities, and relational entities. The subordinate entity and the core entity are in subordinate relationship, and the relationship entity and the core entity can be in business relationship, etc.

In one embodiment, the user enters the following information in the system interface: an entity order receiving user determines the main legal identity of user service in the order receiving field in order to manage and identify each platform user of each channel under the order receiving system; describing each participant of the receipt in each channel of the receipt service of an organization (such as a bank), and automatically registering or giving the identity to the user by the bank when enjoying the service agreement according to the service agreement; the scope includes platform users. The relation entity between the entity order receiving user and the entity order receiving mechanism is the relation entity between the order receiving user and the order receiving mechanism. The entity attribute comprises the creation time of the order receiving user, the name of the order receiving user, the user authority, the user certificate, the verification mode and the user password; the creation time and the user name of the order receiving user are called identifiers; attribute order user creation time to register the date and time at which the order user was created, the time of creation by the acquirer user is described, ranging from the date 1900-01-01 to 9999-12-31, and the time from 00:00:00 to 23:59: 59; the attribute order receiving user name is used for determining the legal identity of a main body of user service in the order receiving field and describing the identity of a user; the attribute user authority describes different user authorities in order to limit role authorities possessed by users of the acquiring mechanism, wherein the range of the different user authorities comprises the authorities of users such as merchants, cashiers and the like; the attribute user certificate describes a certificate or a secret key file which is issued to a user for ensuring the safety management of the order receiving user, and the range; in order to verify the identity of a user, an attribute verification mode describes a verification mode used when the user logs in or executes operation, and the range of the attribute verification mode comprises all verification modes supported by a system; the attribute user password describes a ciphertext when the user is authenticated by the static password in order to verify that the user uses the static password to log in or execute the true identity of the operation, and the range is the user password. The attribute order receiving user creates a time domain name as time; the name field name of the order receiving user is a Chinese text; the user authority domain name is the user authority; the user certificate domain is a certificate; the authentication mode domain is an identity authentication mode; the user password field name is a number. According to the character'. ' sentence break, the sentence break result is: an entity order receiving user, which is used for determining the main body legal identity of user service in the order receiving field in order to manage and identify each platform user of each channel under the order receiving system; describing each participant of the receipt in each channel of the receipt service in the I's bank, and automatically registering or giving the I's bank user identity when enjoying the service agreement according to the service agreement; the scope includes platform users. The relation entity of the entity order receiving user and the entity order receiving mechanism is the relation entity of the order receiving user and the order receiving mechanism. The entity attribute comprises the creation time of the order receiving user, the name of the order receiving user, the user authority, the user certificate, the verification mode and the user password; the creation time and the user name of the order receiving user are called identifiers; attribute order user creation time to register the date and time at which the order user was created, the time of creation by the acquirer user is described, ranging from the date 1900-01-01 to 9999-12-31, and the time from 00:00:00 to 23:59: 59; the attribute order receiving user name is used for determining the legal identity of a main body of user service in the order receiving field and describing the identity of a user; the attribute user authority describes different user authorities in order to limit role authorities possessed by users of the acquiring mechanism, wherein the range of the different user authorities comprises the authorities of users such as merchants, cashiers and the like; the attribute user certificate describes a certificate or a secret key file which is issued to a user for ensuring the safety management of the order receiving user, and the range; in order to verify the identity of a user, an attribute verification mode describes a verification mode used when the user logs in or executes operation, and the range of the attribute verification mode comprises all verification modes supported by a system; the attribute user password describes a ciphertext when the user is authenticated by the static password in order to verify that the user uses the static password to log in or execute the true identity of the operation, and the range is the user password. V/attribute order receiving user creates time domain as time; the name field name of the order receiving user is a Chinese text; the user authority domain name is the user authority; the user certificate domain is a certificate; the authentication mode domain is an identity authentication mode; the user password field name is a number. The theme of the first sentence is entity information, the theme of the second sentence is entity relationship information, the theme of the third sentence is entity attribute information, and the theme of the fourth sentence is domain and instance information. Specifically, topic-related information for each sentence may be set in the template. The word segmentation result of the second sentence// the relation entity of the entity order receiving user and the entity order receiving mechanism as the relation entity// of the order receiving user and the order receiving mechanism can be: entity/order taker/and/entity/order taker/relational entity/is/order taker/and/order taker/relational entity, so that on the basis of the identifier: entity relationships (entity relationships between "order taker" and "order taker").

In operation S303, for each entity information in the entity information set, core entity information is determined from the entity information set based on the number of entity relationship information associated with the entity information in the entity relationship information set.

In this embodiment, the number of entity relationship information associated with the entity information is used as a basis for determining the core entity. For example, if there are 2 entity information items having an entity relationship with the entity information 1 and 5 entity information items having an entity relationship with the entity information 2, the probability that the entity information 2 is more important than the entity information 1 is higher, and the probability that the entity information 2 is a core entity is higher.

Fig. 4 schematically shows a schematic diagram of entity information according to an embodiment of the present disclosure.

As shown in fig. 4, two entity information are shown, one of which is core entity information and one of which is entity information. And core entity information: and the entity information related to the account opening time is more than the entity information: the entity information related to the account type is more. The identifier of the "account type" entity is the account type. The attribute of the entity is a special account mark and a trade area type. In addition, an "account" entity having an association with "account type" is also presented. The identifier of the entity and the attribute information of the entity will be described in the following section.

In operation S305, an entity model composed of business objects is constructed based on the core entity information, the entity relationship information, and the entity information.

In this embodiment, the entity model includes at least one business object, and each business object includes core entity information and entity information associated with the core entity information.

In one embodiment, building an entity model composed of business objects based on core entity information, entity relationship information, and entity information may include the following operations.

First, an entity network is constructed based on entity information and entity relationship information. The entity network includes entity information and entity relationship information between entities. In addition, in order to facilitate the user to visually view the entity model, the entity information and the entity relationship information may be graphical.

Then, the entity network is divided based on the core entity to obtain the service object, so as to construct an entity model composed of the service object. For example, the entity network may be divided based on the entity relationship between each entity and each core entity in the entity network, if the same service object is divided in a manner that a direct relationship exists between the entity network and the same core entity, when a direct relationship exists between one entity and two core entities, the service object to which the entity network belongs may be determined based on the similarity between the name of the entity and the name of the core entity. For another example, when the attribute information of an entity is also obtained, the business object to which the entity belongs may also be divided based on the attribute similarity of the entity. Thus, a normalized, hierarchical and structured entity model can be obtained.

In one embodiment, the method may further include the following operations.

First, entity associated information is acquired from text information for a specified field, and the entity associated information includes entity attributes, attribute fields, and instances. For example, the entity attribute is determined based on the entity identifier, and the attribute field is determined based on the similarity between the sentence related to the attribute in the text information and the preset domain name. The attribute domain is an optional range of the attribute of the entity in the service object determined by the user, and the normalization of the entity attribute is increased. There is a mapping between the attribute domain and the instance of the entity, which may be stored in a database. If a mapping exists between an attribute and at least one instance, the system or user may determine the instance corresponding to the attribute based on the mapping.

The entity attributes, attribute domains, and instances are then associated with entity information corresponding to the entity attributes. Therefore, the information included by the entity model is more comprehensive, and various requirements of users are met.

In one embodiment, the method may further include the following operations.

Firstly, determining the graphic representation forms corresponding to the core entity information, the entity relation information, the entity information and the business object respectively. For example, the business object area is outlined with a red dashed box

Frame selection, yellow frame for core entity

Indicating, for other non-core entities, white boxes

Indicating one-to-many special arrows in entity-to-entity relationships

And (4) showing.

The mockup is then output, which is presented in a graphical representation. Therefore, the intuition degree of the entity model can be effectively improved.

In one embodiment, the method may further include the following operations.

First, a graphic symbol corresponding to entity-associated information is determined. For example, the entities are represented by solid boxes, and the core entities are represented by solid boxes with shading (e.g., shading, pictures, stripes, etc.). Entity relationships are represented by arrows. The entity information may include an identifier and attribute information of the entity, and may be represented by an image such as a box. In addition, in order to increase the intuitiveness, key information such as the value of the identifier, the attribute name and the like can be displayed in a box.

And then outputting the entity model, wherein the entity model comprises a standardized graph and an instantiation graph, the standardized graph represents entity associated information by graphic symbols, and the instantiation graph comprises images corresponding to at least one of entity attributes, attribute domains and instances. The standardized graph can visually check the layering and structural information of the entity model, and the instantiated graph can check more comprehensive information of the entity model. The two different granularities can meet the requirements of users in different scenes.

FIG. 5 schematically shows a schematic diagram of a business object according to an embodiment of the disclosure.

As shown in fig. 5, the name of the business object can be expressed by the name of the core entity: the participant agreement. The business object includes a core entity: the entity comprises a participant agreement service entity, the identifier of the entity comprises a participant agreement type and a participant agreement signing time, and the attribute information of the entity comprises a marketing teller, an agreement description, an opening mechanism, an agreement name and the like. In addition, the business object may also include the following entities: the participant attraction life cycle, the participant agreement and participant relation, the participant external information, the participant agreement rate, the participant agreement and product agreement relation, the participant agreement and collateral relation, the participant agreement and channel type relation, etc. Wherein, each entity can be composed of an entity name, an identifier of the entity, attribute information of the entity, and the like. Therefore, the user can visually check the business object and the core entity information, the entity information and the constituent parts thereof and the like included in the business object.

After entity type classification is carried out on the entity information, the following information can be obtained; the core entity of the 'participant agreement' business object is the participant agreement, and the relationship entity is the relationship between the participant agreement and the participant, the relationship between the participant agreement and the participant agreement, the relationship between the participant agreement and the channel, the relationship between the participant agreement and the product agreement, the relationship between the participant agreement application and the participant agreement, and the relationship between the participant agreement and the proof. The subordinate entities are participant agreement life cycle, participant external information type, participant agreement rate and participant agreement application.

In one embodiment, in order to improve the accuracy of at least one of the determined entity information, the entity relationship information, the core entity information, and the business object, so as to improve the accuracy of the constructed entity model, the information may be reviewed by human assistance.

Specifically, the above method may further include the following operations.

Firstly, at least one of an entity information set, an entity relationship information set, a business object and entity association information is output.

Then, at least one of the entity information set, the entity relationship information set, the business object and the entity association information is updated in response to a modification instruction from the client.

For example, when a user inputs text information in a display interface and sends the text information to a server, the server acquires a core entity or a service object from the text information, and then sends the core entity information and the service object information to a client for display, and the user performs recheck. The user can edit the information at the client when finding that the part needs to be modified, and then the edited information is fed back to the server.

FIG. 6 schematically shows a display interface diagram for editing business objects according to an embodiment of the disclosure.

For example, after the server side acquires the business object of the participant agreement, the server side may send information of the business object to the client side so that the client side can display the information. When the user finds that the attribute information of the core entity also comprises the attribute of the protocol name during rechecking, the attribute information of the core entity can be edited at the client, the attribute of the protocol name is added, and then the attribute is sent to the server so that the server can update the service object information.

In one embodiment, outputting the mockup may include the following operations.

First, the normalized graph is sent to the client. The image information included in the standardized graph is less than that included in the instantiation graph, and only the standardized graph is sent, so that occupation of network resources is reduced, and response speed is improved.

The instantiation graph is then sent to the client in response to a user viewing operation from the client on the graphical symbol on the normalization graph. If the user wants to view more comprehensive information such as attribute information, the server side can respond to the received user viewing operation and send the image of the entity, the core entity or the business object targeted by the user viewing operation to the client side so as to be displayed on the client side.

FIG. 7 schematically shows a standardized schematic of a mockup according to an embodiment of the disclosure.

In the field of agent payment (paying), a paying client and a bank sign an entrusted withholding protocol, the bank actively finishes withholding based on the bill of the client, and the entity model standardized graph is loaded under the business scene. Therefore, the core entity, the subordinate entity, the relation entity and the entity relation included in the agent payment field are visual, and all the employees of the bank can perform business-related operations based on the entity model. For example, the business objects in FIG. 7 include participant agreements, proof of execution, product agreements and accounts, and the like. The business objects of the participant agreement comprise: the core entity is a participant agreement, the relation entity is the relation between the participant agreement and the product agreement, and the subordinate entity is a principal, and the relation between the agreement and the principal deduction agreement and the product agreement of the personal settlement account. It should be noted that only some of the entities in the participant agreement, proof of execution, product agreement and account are shown in fig. 7.

FIG. 8 schematically shows an instantiation diagram of a mockup according to an embodiment of the disclosure.

As shown in fig. 8, in the field of proxy payment (payment), a payment client and a bank sign a proxy deduction agreement, and the bank actively completes the deduction based on the client's bill, and for this service scenario, the entity model instantiates a bearer. Information such as identifiers and attributes of some entities in fig. 8 is not shown.

In another embodiment, the method may further include the following operations. And after the entity models aiming at different specified fields are obtained, the entity models aiming at the different specified fields are fused to obtain a global entity model.

Because a mechanism, such as a bank design, has a plurality of fields, after one or more entity models aiming at one or more fields are constructed based on the scheme, the plurality of entity models can be fused to obtain an entity model suitable for the whole mechanism. As for banking institutions, aspects relating to the financial field, the physical model constructed is hundreds, thousands or more times the scale of the portion shown in fig. 8. The entity model constructed may serve the entire organization, suitable for use in the scenario shown in FIG. 1.

The entity model building method provided by the embodiment of the disclosure defines entity identifiers, identifies and refines attributes by identifying candidate entities, defining business entities, identifying entity relations and identifying entity relation cardinality, and by defining entity identifiers, identifying and refining attributes for all entities identified by the business entity identification submodule, and defines domains corresponding to the domains, the definition instances and the associated attributes. Thus, entity models of different business fields are established. And data sharing of entity models in different business fields is established through a unified platform.

One aspect of the present disclosure provides a solid model building apparatus. FIG. 9 schematically shows a block diagram of a mockup construction apparatus according to an embodiment of the disclosure.

As shown in fig. 9, the solid model building apparatus 900 includes: a set acquisition module 910, a core entity determination module 920 and a model construction module 930.

The set obtaining module 910 is configured to obtain an entity information set and an entity relationship information set from text information for a specific domain based on a preset rule.

The core entity determining module 920 is configured to determine, for each entity information in the entity information set, core entity information from the entity information set based on the number of entity relationship information associated with the entity information in the entity relationship information set.

The model construction module 930 is configured to construct an entity model composed of business objects based on the core entity information, the entity relationship information and the entity information, where the entity model includes at least one business object, and each business object includes one core entity information and entity information associated with the core entity information.

Operations that can be performed by each module in the entity model building device can be related operations in the above method, and are not described herein again.

Another aspect of the present disclosure provides a solid model building system. FIG. 10 schematically shows a block diagram of a mockup construction system according to an embodiment of the disclosure.

As shown in fig. 10, the solid model building system 1000 includes: business entity module 1010 and business object module 1020.

The business entity module 1010 is configured to determine entity association information, where the entity association information includes entity information and entity relationship information.

Business object module 1020 is to determine a business object based on the entity information and the entity relationship information to build an entity model based on the business object.

In addition, the system 1000 may also include a business domain module and a data standard module.

Specifically, the business entity module 1010 is responsible for creating business entities, including 1) entity naming, purpose, definition, scope; 2) entity relationships, entity relationship cardinalities; 3) entity identifier: including identifier naming, purpose, definition, scope; 4) entity attributes: including attribute naming, purpose, definition, scope; 5) domains and instances of entity attributes; 6) and (5) entity imaging.

The business field module is responsible for creating field graphics, including field instantiation graphs and field standardization graphs.

Business object module 1020 is responsible for the creation of business objects, including business object naming, purpose, definition, scope, core entities, subordinate entities, relational entities, and graphing.

The data standard module is responsible for storing enterprise-level data standards, including enterprise-level domain standards and instance standards.

In one embodiment, the business entity module 1010 includes: the system comprises a data preprocessing submodule, a business entity identifying submodule, an entity relation submodule, an identifier and attribute submodule, a domain and instance identifying submodule and an entity imaging submodule. The business entities are enterprise-level assets, are not unique to a certain domain, and each entity can be reused by any domain.

The data preprocessing submodule is responsible for cutting off the Chinese text input by the user according to the fixed format and the sentence pattern according to the sentence number. The sentence with the sentence interruption is sent to a plurality of sub-modules of the business entity module 1010 for processing.

The business entity identification submodule is responsible for creating the business entity, including entity naming, purpose, definition and scope.

The entity relationship submodule is responsible for entity relationship creation, and comprises an entity relationship and an entity relationship cardinality.

The identifier and attribute submodule is responsible for creating an entity identifier and attribute, including identifier naming, purpose, definition and range; attribute naming, purpose, definition, scope.

The domain and instance identification submodule is responsible for domain and instance association of entity attributes.

The entity graphic sub-module is responsible for entity graphic creation of the entity. The identifier is located above the entity box and the other attributes are located below.

In one embodiment, the business object module 1020 includes: a business object identification submodule, a core entity identification submodule, a subordinate entity and relationship entity identification submodule and a business object graphical submodule. The business objects are enterprise-level assets and are not unique to a certain field, and each business object can be reused by any field.

And the business object identification submodule is responsible for creating the business objects, including the naming, purpose, definition and range of the business objects.

And the core entity identification submodule is responsible for identifying the core entity of the service object.

And the subordinate entity and relation entity identification submodule is responsible for identifying the subordinate entity and the relation entity of the business object.

And the business object graphical submodule is responsible for graphical creation of the business object.

In one embodiment, the business segment module includes: and the service field entity instantiation graph sub-module and the service field entity standardization graph sub-module.

The business field entity instantiation graph sub-module is responsible for creating a field entity instantiation graph.

And the business field entity standardization graph submodule is responsible for creating a business field entity standardization graph.

In one embodiment, the data criteria module includes: an enterprise-level domain standard submodule and an enterprise-level instance standard submodule.

The enterprise-level domain standard submodule is responsible for storing data standards of the domain, including storage domain groups, sub-domain group names, domain names, data types, lengths, data types, data styles and the like. For example: the legal name domain name is stored as: the field group "text class", the sub-field group name ", the data type" character type ", the length" 300 ", and the data type" text format ".

The enterprise level instance criteria submodule is responsible for storing data criteria for the instance. Including storage instance group, instance number, instance name. Example set is "days of interest rate conversion": numbered "1", the instance name "360"; numbered "2", the instance name "365"; numbered "3" and the instance name "actual days".

FIG. 11 schematically shows a logical diagram of a mockup construction process according to an embodiment of the disclosure.

As shown in fig. 11, the business entity module 1010 identifies the business entities, identifies the entity relationships and the relationship bases, and the business object module 1020 creates the business objects including the business objects, the core entities, the subordinate entities and the relationship entities. Entity identifiers, entity attributes, domains and instances of entity attributes, entity graphing are created by the business entity module 1010. And creating a domain graphic including a domain instantiation graph and a domain standardization graph through a business domain module, thereby completing entity modeling of different domains.

As shown in fig. 11, first, the business entity module 1010 and the data preprocessing module receive the chinese text input by the user in the fixed format and sentence pattern, and according to the character'. 'sentence break,' a sentence with a broken sentence is sent to different sub-modules. For example, the first sentence after being divided is sent to the business entity identification submodule. And the second sentence is sent to the entity relation submodule. The third sentence is sent to the identifier and attribute submodule. The fourth sentence is sent to the domain and instance identification submodule.

Then, the sub-module business entity identification sub-module of the business entity module 1010 receives the relevant sentences of the business entity of the data preprocessing module, carries out word segmentation on the sentences, completes identification of business entity names, entity purposes, definitions and ranges, and displays the business entity names, the entity purposes, the entity definitions and the range types in an input box for a user to simply modify. Where the purpose explains why this entity is important for the business, the definition explains what this entity is, the scope explains the limitations of the entity and the coverage of the constraints.

Next, the sub-module entity relationship sub-module of the service entity module 1010 receives the related statements of the service entity relationship of the data preprocessing module, performs word segmentation on the statements, and completes the identification of the relationship between the service entity and other entities and the entity relationship cardinality, where the entity relationship cardinality (1:1, 1: M, M: N) is a service rule and represents how many possible value relationships between the entities occur.

The business object module 1020 then creates a business object including the name, purpose, definition, scope, core entity, subordinate entity, relational entity, etc. of the business object. Each completed by the following sub-modules. The business object identification submodule is used as an object name according to the entity name which has more relations with other entities in the business entity module 1010, and the purpose, definition and range of the core entity are used as the purpose, definition and range of the business object. And (5) displaying the data back in the input box according to the category for the user to simply modify. The core entity identification submodule identifies an entity with more entity relation with other entities as a core entity of the business object. The subordinate entity and relation entity identification submodule identifies subordinate entities and relation entities of the business object according to name characteristics of the entities in other entities related to the core entity, for example, the relation between the order receiving user and the order receiving mechanism is a relation entity, and the other entities are subordinate entities.

Next, the business object module 1020 creates a business object that includes the naming, purpose, definition, scope, core entity, subordinate entity, relational entity, etc. of the business object. Each completed by the following sub-modules. The business object identification submodule is used as an object name according to the entity name which has more relations with other entities in the business entity module 1010, and the purpose, definition and range of the core entity are used as the purpose, definition and range of the business object. And (5) displaying the data back in the input box according to the category for the user to simply modify. The core entity identification submodule identifies an entity with more entity relation with other entities as a core entity of the business object. The subordinate entity and relation entity identification submodule identifies subordinate entities and relation entities of the business object according to name characteristics of the entities in other entities related to the core entity, for example, the relation between the order receiving user and the order receiving mechanism is a relation entity, and the other entities are subordinate entities.

Then, the business entity module 1010 creates entity-related content, receives the data preprocessing module identifier and the attribute-related statement, and performs word segmentation on the statement to complete the following recognition: 1) entity identifier: including identifier naming, purpose, definition, scope; 2) entity attributes: including attribute naming, purpose, definition, scope; 3) domains and instances of entity attributes; 4) and the entity imaging is respectively completed by the following sub-modules. The identifier and attribute submodule receives the data preprocessing module identifier and attribute related statements, carries out word segmentation on the statements, extracts the identifier, and displays the identifier in an input box according to the identifier name, the purpose, the definition and the range category for a user to simply modify. And extracting the attributes of the non-identifiers, and displaying the attributes in the input box according to the identifier name, purpose, definition and range categories for the user to modify simply. And the domain and instance identification submodule compares the similarity of the received data preprocessing module identifier and the attribute related statement with the domain name of the data standard of the statement and the data standard module, and selects three statements with the highest similarity for the user to select. For example, time attribute is created, and date and time domain names, date and time, are automatically selected in the data standard module for selection by a user. After the domain name is selected, the instance is automatically associated according to the value range of the attribute, for example, if the attribute of the 'payment state' is associated with the domain name of the 'state', the associated instance is 'to be paid', 'payment success', 'payment failure'. The entity imaging submodule displays entity names in the business entity identification submodule, identifiers and attribute names in the identifier and attribute submodule and other entities which have the association relation with the entity in the entity relation submodule in an imaging mode. For example, where the identifier is located above the entity and other attributes are located below, the entity-to-entity relationship is one-to-many

The representation can click on the entity from the graphical page, and see the details of the purpose, definition, scope, attributes and the like of the entity.

Then, the business object graphical sub-module in the business object module 1020 graphically displays the business object name, the core entity name, the subordinate entity and the relationship entity. And the entity under the business object can be clicked from the graphical page, and the details of the purpose, definition, range, attribute and the like of the entity can be checked.

Then, the business domain module creates domain graphics, including a domain instantiation graph and a domain standardization graph. The domain instantiation graph is completed by the business domain entity instantiation graph submodule, and the domain standardization graph is completed by the business domain entity standardization graph submodule. The business field entity instantiation graph sub-module is based on the business field entity standardization graph sub-module, and the instantiation of the entity is used according to the input instantiation of all the entities in the field

And (4) showing. Any entity can be clicked on the graphical page, and the purpose, definition, range, attribute and other details of the entity can be viewed.

The entity model construction system provided by the embodiment of the disclosure forms entity graphs in different fields by abstracting services in different fields, and realizes linkage check of graphs and entity details, thereby realizing unified management of entity models, reducing data sharing difficulty and reducing department communication cost. In addition, a unified entity model view is provided for the enterprise by adopting a structural and standardized language, for example, data is classified, abstracted and associated to realize data sharing of the whole enterprise, so that the enterprise can conveniently manage the data.

It should be noted that the implementation, solved technical problems, implemented functions, and achieved technical effects of each module/unit and the like in the apparatus part embodiment are respectively the same as or similar to the implementation, solved technical problems, implemented functions, and achieved technical effects of each corresponding step in the method part embodiment, and are not described in detail herein.

Any of the modules, units, or at least part of the functionality of any of them according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules and units according to the embodiments of the present disclosure may be implemented by being split into a plurality of modules. Any one or more of the modules, units according to the embodiments of the present disclosure may be implemented at least partially as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented by any other reasonable means of hardware or firmware by integrating or packaging the circuits, or in any one of three implementations of software, hardware and firmware, or in any suitable combination of any of them. Alternatively, one or more of the modules, units according to embodiments of the present disclosure may be implemented at least partly as computer program modules, which, when executed, may perform the respective functions.

For example, any of the set obtaining module 910, the core entity determining module 920 and the model constructing module 930 may be combined and implemented in one module, or any one of them may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of the other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the set obtaining module 910, the core entity determining module 920 and the model building module 930 may be implemented at least partially as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented by hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or may be implemented by any one of three implementations of software, hardware and firmware, or any suitable combination of any of them. Alternatively, at least one of the set obtaining module 910, the core entity determining module 920 and the model building module 930 may be at least partly implemented as a computer program module, which when executed may perform the respective functions.

One aspect of the present disclosure provides an electronic device. FIG. 12 schematically shows a block diagram of an electronic device according to an embodiment of the disclosure. The electronic device shown in fig. 12 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 12, an electronic apparatus 1200 according to an embodiment of the present disclosure includes a processor 1201, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)1202 or a program loaded from a storage section 1208 into a Random Access Memory (RAM) 1203. The processor 1201 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 1201 may also include on-board memory for caching purposes. The processor 1201 may include a single processing unit or multiple processing units for performing the different actions of the method flows according to embodiments of the present disclosure.

In the RAM1203, various programs and data necessary for the operation of the electronic apparatus 1200 are stored. The processor 1201, the ROM 1202, and the RAM1203 are communicatively connected to each other by a bus 1204. The processor 1201 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 1202 and/or the RAM 1203. Note that the programs may also be stored in one or more memories other than the ROM 1202 and the RAM 1203. The processor 1201 may also perform various operations of method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.

Electronic device 1200 may also include input/output (I/O) interface 1205, according to an embodiment of the disclosure, input/output (I/O) interface 1205 also connected to bus 1204. The electronic device 1200 may also include one or more of the following components connected to the I/O interface 1205: an input section 1206 including a keyboard, a mouse, and the like; an output portion 1207 including a display device such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 1208 including a hard disk and the like; and a communication section 1209 including a network interface card such as a LAN card, a modem, or the like. The communication section 1209 performs communication processing via a network such as the internet. A driver 1210 is also connected to the I/O interface 1205 as needed. A removable medium 1211, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like, is mounted on the drive 1210 as necessary, so that a computer program read out therefrom is mounted into the storage section 1208 as necessary.

According to embodiments of the present disclosure, method flows according to embodiments of the present disclosure may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 1209, and/or installed from the removable medium 1211. The computer program, when executed by the processor 1201, performs the above-described functions defined in the system of the embodiments of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, a computer-readable storage medium may include the ROM 1202 and/or the RAM1203 and/or one or more memories other than the ROM 1202 and the RAM1203 described above.

Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. These examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.

Claims

1. A solid model construction method executed by a server side comprises the following steps:

acquiring an entity information set and an entity relation information set from text information aiming at a specified field based on a preset rule;

for each entity information in an entity information set, determining core entity information from the entity information set based on the number of entity relationship information associated with the entity information in the entity relationship information set; and

and constructing an entity model consisting of business objects based on the core entity information, the entity relation information and the entity information, wherein the entity model comprises at least one business object, and each business object comprises core entity information and entity information associated with the core entity information.

2. The method of claim 1, further comprising:

acquiring entity associated information from the text information aiming at the specified field, wherein the entity associated information comprises entity attributes, attribute fields and instances; and

and associating the entity attribute, the attribute domain and the instance with entity information corresponding to the entity attribute.

3. The method of claim 2, further comprising:

determining a graphic symbol corresponding to the entity associated information;

outputting the entity model, wherein the entity model comprises a standardized graph and an instantiated graph, the standardized graph represents the entity associated information by the graphic symbol, and the instantiated graph comprises an image corresponding to at least one of the entity attribute, the attribute field and the instance.

4. The method of claim 3, the outputting the solid model comprising:

sending the standardized graph to a client; and

and sending the instantiation graph to a client in response to a user viewing operation from the client for the graphic symbols on the normalization graph.

5. The method of claim 2, wherein:

the entity attribute is determined based on an entity identifier; and

the attribute field is determined based on the similarity between the sentence related to the attribute in the text information and a preset domain name.

6. The method of claim 1, further comprising:

respectively determining the graphic representation forms corresponding to the core entity information, the entity relation information, the entity information and the business object; and

outputting the solid model, wherein the solid model is displayed in the graphic representation form.

7. The method of claim 1, wherein the obtaining the entity information set and the entity relationship information set from the text information for the specified domain based on the preset rule comprises:

sentence dividing is carried out on the text information to obtain a first sentence comprising the entity information and a second sentence comprising the entity relation information;

performing word segmentation on the first sentence and the second sentence respectively to obtain a first word segmentation result and a second word segmentation result;

extracting the entity information from the first segmentation result based on a first identification corresponding to the entity information, and extracting the entity relationship information from the second segmentation result based on a second identification corresponding to the entity relationship information.

8. The method of claim 2, further comprising:

outputting at least one of the entity information set, the entity relationship information set, the business object and the entity association information; and

and updating at least one of the entity information set, the entity relation information set, the business object and the entity association information in response to a modification instruction from a client.

9. The method of claim 1, wherein the building an entity model composed of business objects based on the core entity information, the entity relationship information, and the entity information comprises:

constructing an entity network based on the entity information and the entity relationship information; and

and dividing the entity network based on the core entity to obtain service objects so as to construct an entity model consisting of the service objects.

10. The method of claim 1, further comprising:

and after the entity models aiming at different specified fields are obtained, the entity models aiming at the different specified fields are fused to obtain a global entity model.

11. An apparatus for constructing a solid model executed by a server side, comprising:

the set acquisition module is used for acquiring an entity information set and an entity relation information set from the text information aiming at the specified field based on a preset rule;

a core entity determining module, configured to determine, for each entity information in an entity information set, core entity information from the entity information set based on the number of entity relationship information associated with the entity information in the entity relationship information set;

and the model construction module is used for constructing an entity model consisting of business objects based on the core entity information, the entity relation information and the entity information, wherein the entity model comprises at least one business object, and each business object comprises core entity information and entity information related to the core entity information.

12. A solid model building system comprising:

the business entity module is used for determining entity associated information, and the entity associated information comprises entity information and entity relation information; and

and the business object module is used for determining a business object based on the entity information and the entity relation information so as to construct an entity model based on the business object.

13. An electronic device, comprising:

one or more processors;

a storage device for storing executable instructions which, when executed by the processor, implement a method according to any one of claims 1 to 10.

14. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, implement a method according to any one of claims 1 to 10.