CN116842963A

CN116842963A - Text data processing method and device, electronic equipment and computer storage equipment

Info

Publication number: CN116842963A
Application number: CN202310850260.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: 2023-07-12
Filing date: 2023-07-12
Publication date: 2023-10-03

Abstract

The disclosure provides a text data processing method, a text data processing device, electronic equipment and computer storage equipment, which can be applied to the technical fields of big data, financial science and technology and business architecture. The method comprises the following steps: carrying out semantic processing on the acquired text data to obtain capability text data, wherein the capability text data comprises capability requirement information, the acquired text data is used for describing the service behavior to be implemented of the mechanism, and the capability text data is used for describing capability limitation information for completing the service behavior to be implemented; determining service execution link information of text data according to the capability requirement information and the component definition text of the flow component; determining at least one business entity information matched with the business execution link information in the entity assembly; and determining the data table information of each of the at least one business entity information so that the Internet technical architecture forms a business system corresponding to the business behavior to be implemented by utilizing the data table information.

Description

Text data processing method and device, electronic equipment and computer storage equipment

Technical Field

The present disclosure relates to the technical field of big data, financial science and technology, and business architecture, and more particularly, to a text data processing method, apparatus, electronic device, and computer storage device.

Background

The random internet technology is continuously developed, and the internet service is rapidly developed. To accommodate the rapidly evolving and expanding internet services, enterprises need to continually upgrade system architecture, add system functionality, and add new business services.

In the related art, business personnel typically analyze the enterprise planning or policy text updated in real time, and comb out the operation of adapting to the business system architecture. And then, realizing the landing of the enterprise planning or strategy text by interfacing the business personnel with the developer so as to expand or upgrade the system architecture and provide business services.

In the process of realizing the above inventive concept, the inventor finds that the related art has at least the following technical problems: the labor cost required for analyzing the enterprise planning or policy texts is high, the time cost and communication cost for the business and development docking are high, and the landing efficiency of the business system is affected.

Disclosure of Invention

In view of the above, the present disclosure provides a text data processing method, apparatus, electronic device, and computer storage device.

According to a first aspect of the present disclosure, there is provided a text data processing method, including:

carrying out semantic processing on the acquired text data to obtain capability text data, wherein the capability text data comprises capability requirement information, the acquired text data is used for describing the service behavior to be implemented of the mechanism, and the capability text data is used for describing capability limitation information for completing the service behavior to be implemented;

Determining service execution link information of text data according to the capability requirement information and the component definition text of the flow component;

determining at least one business entity information matched with the business execution link information in the entity assembly; and

and determining the data table information of each of the at least one service entity information so that the Internet technical architecture forms a service system corresponding to the service behavior to be implemented by utilizing the data table information.

According to the embodiment of the disclosure, the capability text data comprises first capability requirement information of a first level and N pieces of second capability requirement information related to the first capability requirement information in a last level, wherein the first capability requirement information corresponds to a first capability definition text, the N pieces of second capability requirement information respectively correspond to a second capability definition text, and N is more than or equal to 1; the process component comprises a value chain sub-component, a task sub-component and an execution step sub-component, wherein the value chain sub-component corresponds to a first component definition text, the execution step sub-component corresponds to a second component definition text, and the task sub-component corresponds to a third component definition text.

According to an embodiment of the present disclosure, determining service execution link information corresponding to text data according to capability requirement information and a component definition text of a flow component includes:

Determining a target value chain sub-component according to a first text similarity between the first capability definition text and the first component definition text;

s execution step subassemblies related to the target value chain subassembly are determined, wherein S is more than or equal to N is more than or equal to 1;

according to the second text similarity between the second capability definition text and the second component definition text, determining N target execution step sub-components from the S execution step sub-components, wherein the target execution step sub-components uniquely correspond to the second capability requirement information;

determining P target task sub-components according to respective third text similarity of the third component definition text and N second capability definition texts, wherein P is more than or equal to N is more than or equal to 1;

and determining service execution link information corresponding to the text data based on the target value chain sub-component, the P target task sub-components and the N target execution step sub-components.

According to an embodiment of the present disclosure, wherein the second component definition text includes an execution step name and a step rule name;

determining N target execution step sub-components from the S execution step sub-components according to a second text similarity between the second capability definition text and the second component definition text, including:

determining the respective combined text of S execution step sub-components according to the execution step names and the step rule names;

And calculating second text similarity between the S combined texts and the second capability definition texts aiming at the second capability definition texts of the nth second capability requirement information, and determining an execution step sub-component corresponding to the second text similarity with the highest similarity as a target execution step sub-component corresponding to the nth second capability requirement information, wherein N is more than or equal to N is more than or equal to 1.

According to an embodiment of the present disclosure, wherein the capability text data further includes third capability requirement information between the first capability requirement information and the second capability requirement information; the flow component also comprises a business field sub-component, a value flow sub-component and an activity sub-component;

based on the target value chain sub-component, at least P target task sub-components and N target execution step sub-components, determining the business execution link information corresponding to the text data includes:

determining at least P target activity subassemblies according to the P target task subassemblies based on a first association relationship, wherein the first association relationship is used for representing the association relationship between the task subassemblies and the activity subassemblies;

determining at least P target business field subassemblies and at least P value flow subassemblies according to at least P target activity subassemblies based on a second association relationship, wherein the second association relationship is used for representing a hierarchical association relationship between the third capability requirement information and the second capability requirement; and

And determining service execution link information corresponding to the text data according to the target value chain sub-component, at least P target service field sub-components, at least P value stream sub-components, at least P target activity sub-components, at least P target task sub-components and N target execution step sub-components based on the hierarchical association relation between the capability requirement information.

According to an embodiment of the present disclosure, determining at least one business entity information in the entity component that matches the business execution link information includes:

acquiring N target execution step sub-components in service execution link information; and

and determining the business entity information corresponding to each target execution step sub-assembly according to the mapping relation between each target execution step sub-assembly and the business entity, and obtaining at least N pieces of business entity information.

According to an embodiment of the present disclosure, the business entity information includes a business entity name and a business entity attribute;

determining respective data table information of at least one business entity information, comprising: for each of the business entity information,

determining an object code entity according to the mapping relation between the service entity name and the code entity; and

And determining the data table information of the target code entity according to the target code entity.

According to an embodiment of the present disclosure, further comprising:

in response to receiving the first display instruction, analyzing the first display instruction to obtain target capacity requirement information;

displaying target capability requirement information and a plurality of capability requirement information under the layer to which the target capability requirement information belongs in a layer form, simultaneously displaying service execution link information in a first display area and data table information in a second display area;

wherein the first display area is related to the capability requirement information, and the second display area is related to the service execution link information.

According to an embodiment of the present disclosure, further comprising:

in response to receiving the second display instruction, analyzing the second display instruction to obtain target capacity demand information, L target data table information and Q target fields, wherein Q is more than or equal to 1, and L is more than or equal to 1;

displaying target capability requirement information and a plurality of capability requirement information under the layer to which the target capability requirement information belongs in a layer form, simultaneously displaying service execution link information in a first display area, and displaying L target data table information and Q target fields in a second display area;

A second aspect of the present disclosure provides a text data processing apparatus, comprising:

the semantic processing module is used for carrying out semantic processing on the acquired text data to obtain capability text data, wherein the capability text data comprises capability requirement information, the acquired text data is used for describing the service behavior to be implemented of the mechanism, and the capability text data is used for describing capability limiting information for completing the service behavior to be implemented;

the first determining module is used for determining service execution link information corresponding to the text data according to the capability requirement information and the component definition text of the flow component;

the second determining module is used for determining at least one business entity information matched with the business execution link information in the entity assembly; and

and the third determining module is used for determining the data table information of each at least one business entity information so that the Internet technical architecture forms a business system corresponding to the business behavior to be implemented by utilizing the data table information.

A third aspect of the present disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the text data processing method described above.

A fourth aspect of the present disclosure also provides a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the above-described text data processing method.

A fifth aspect of the present disclosure also provides a computer program product comprising a computer program which, when executed by a processor, implements the above-described text data processing method.

In the embodiment of the disclosure, the acquired text data is semantically processed to obtain the capability text data, and the capability text data is butted with the flow component to obtain the service execution link information, so that manual analysis and text data carding of service personnel are not needed, automatic analysis and service step execution butting can be realized at a service side, the cost for generating the service execution link information is reduced, and the generation efficiency is improved. In addition, after the service execution link information is determined, the butt joint of the service execution link and the IT architecture code resource is realized by determining at least one service entity information matched with the service execution link information and the data table information of the at least one service entity information, so that communication between service personnel and developers is not needed, the landing cost of the service system architecture is reduced, and the efficiency is improved.

Drawings

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

fig. 1 schematically illustrates an application scenario of a text data processing method according to an embodiment of the present disclosure;

FIG. 2 schematically illustrates a flow chart of a text data processing method according to an embodiment of the present disclosure;

FIG. 3 schematically illustrates a schematic diagram of semantically processed capability text data according to an embodiment of the present disclosure;

FIG. 4 schematically illustrates a flow chart of a method of determining traffic execution link information according to an embodiment of the disclosure;

FIG. 5 schematically illustrates a presentation interface diagram in response to receiving a first presentation instruction according to an embodiment of the present disclosure;

FIG. 6 schematically illustrates an interaction scenario diagram according to an embodiment of the present disclosure;

FIG. 7 schematically illustrates a block diagram of a text data processing apparatus according to an embodiment of the present disclosure; and

fig. 8 schematically illustrates a block diagram of an electronic device adapted for a text data processing method 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 only exemplary 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 present disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to 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/or 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 should be noted that the terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly formal manner.

Where expressions like at least one of "A, B and C, etc. are used, the expressions should generally be interpreted in accordance with the meaning as commonly understood by those skilled in the art (e.g.," a system having at least one of A, B and C "shall include, but not be limited to, a system having 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.).

In the technical scheme of the disclosure, the related data (such as including but not limited to personal information of a user) are collected, stored, used, processed, transmitted, provided, disclosed, applied and the like, all conform to the regulations of related laws and regulations, necessary security measures are adopted, and the public welcome is not violated.

In the related technology, development departments and business departments in enterprises are commonly matched to realize the expansion or upgrading of the system architecture and provide business services. In particular, updated enterprise planning or policy text in real-time is obtained by experienced business personnel and the operation of adapting the business system architecture is carded out by analysis. And then, in the business department, determining the final business side execution flow by reporting and approving layer by layer. The development department obtains the final business side execution flow from the business department, and then develops the code field adapting to the business side execution flow to construct, perfect and upgrade the business architecture system.

In the process of realizing the steps, the service level of service personnel and the scale of the equipped service personnel are required, so that the labor cost for generating the service side execution flow is high and the efficiency is low. Moreover, because the definition of different business words by business personnel and developers is different, the cost of the docking time and the labor cost of the business side and the development side are high. In summary, the related art has the technical problems of high labor cost and low development efficiency in enterprise planning or policy text landing.

The embodiment of the disclosure provides a text data processing method, which comprises the following steps: carrying out semantic processing on the acquired text data to obtain capability text data, wherein the capability text data comprises capability requirement information, the acquired text data is used for describing the service behavior to be implemented of the mechanism, and the capability text data is used for describing capability limitation information for completing the service behavior to be implemented; determining service execution link information of text data according to the capability requirement information and the component definition text of the flow component; determining at least one business entity information matched with the business execution link information in the entity assembly; and determining the data table information of each of the at least one business entity information so that the Internet technical architecture forms a business system corresponding to the business behavior to be implemented by utilizing the data table information.

Fig. 1 schematically illustrates an application scenario of a text data processing method according to an embodiment of the present disclosure.

As shown in fig. 1, an application scenario 100 according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104, and a server 105. The network 104 is a medium used to provide a communication link between the first terminal device 101, the second terminal device 102, the third terminal device 103, and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

The user may interact with the server 105 through the network 104 using at least one of the first terminal device 101, the second terminal device 102, the third terminal device 103, to receive or send messages, etc. Various communication client applications, such as a shopping class application, a web browser application, a search class application, an instant messaging tool, a mailbox client, social platform software, etc. (by way of example only) may be installed on the first terminal device 101, the second terminal device 102, and the third terminal device 103.

The first terminal device 101, the second terminal device 102, the third terminal device 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.

The server 105 may be a server providing various services, such as a background management server (by way of example only) providing support for websites browsed by the user using the first terminal device 101, the second terminal device 102, and the third terminal device 103. The background management server may analyze and process the received data such as the user request, and feed back the processing result (e.g., the web page, information, or data obtained or generated according to the user request) to the terminal device.

It should be noted that the text data processing method provided in the embodiment of the present disclosure may be generally executed by the server 105. Accordingly, the text data processing apparatus provided by the embodiments of the present disclosure may be generally provided in the server 105. The text data processing 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 105 and is capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and/or the server 105. Accordingly, the text data processing apparatus provided by the embodiments of the present disclosure may also be provided in a server or a server cluster that is different from the server 105 and is capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103 and/or the server 105.

For example, the user transmits the acquired text data to the server 105 using the first terminal apparatus 101, the second terminal apparatus 102, and the third terminal apparatus 103. The server 105 performs semantic processing on the acquired text data to obtain capability text data, wherein the capability text data comprises capability requirement information, the acquired text data is used for describing a to-be-implemented business behavior of a mechanism, and the capability text data is used for describing capability limitation information for completing the to-be-implemented business behavior; determining service execution link information of text data according to the capability requirement information and the component definition text of the flow component; determining at least one business entity information matched with the business execution link information in the entity assembly; and determining the data table information of each of the at least one business entity information so that the Internet technical architecture forms a business system corresponding to the business behavior to be implemented by utilizing the data table information.

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

The text data processing method of the disclosed embodiment will be described in detail below with reference to fig. 2 to 6 based on the scenario described in fig. 1.

Fig. 2 schematically illustrates a flow chart of a text data processing method according to an embodiment of the present disclosure.

As shown in fig. 2, the method 200 includes operations S210 to S240.

In operation S210, semantic processing is performed on the obtained text data to obtain capability text data, where the capability text data includes capability requirement information, the obtained text data is used to describe a to-be-implemented service behavior of the organization, and the capability text data is used to describe capability restriction information for completing the to-be-implemented service behavior.

According to the embodiment of the disclosure, the acquired text data is used for describing the business behavior to be implemented of the organization, and the enterprise organization can be guided to carry out adaptation improvement by describing the business behavior to be implemented.

According to an embodiment of the present disclosure, the capability text data is used to describe capability restriction information for completing a business action to be implemented. Such as capacity constraints.

According to the embodiment of the disclosure, keywords and key sentences in the acquired text data can be directly used as the capability text data. Alternatively, keywords obtained from the text data may be combined to obtain the capability text data.

According to an embodiment of the present disclosure, the capability text data includes capability requirement information of at least one hierarchy so as to form service execution link information for each hierarchy of the capability requirement information.

For example, the acquired text data may be: the enterprise needs to timely feed back the questions of the user and timely process the questions of the user while providing the consultation service for the user. In addition, for the user's questions, real-time statistics is required to realize online automatic reply. The business behavior to be implemented in the text data may be an advisory service. The capability requirement information acquired from the above text data may be "feedback doubt", "process doubt", "on-line automatic recovery".

In operation S220, service execution link information of the text data is determined according to the capability requirement information and the component definition text of the flow component.

According to an embodiment of the present disclosure, at least one hierarchy of flow sub-components is provided in the flow components, each hierarchy may include a plurality of flow sub-components. The capability requirement information of each hierarchy corresponds to at least one hierarchy's flow subcomponent.

According to the embodiment of the disclosure, the capability requirement information can be connected to the corresponding flow component or the flow sub-component by performing text matching on the capability requirement information and the component definition text of the flow component, so that the service execution link information of the text data can be obtained. Thus, the interfacing from the text data to the execution link is completed.

According to the embodiment of the disclosure, the capability requirement information of at least one hierarchy has an upper-lower hierarchy relationship, the flow sub-components of at least one hierarchy also have an upper-lower hierarchy relationship, and the formed business execution link also comprises the capability requirement information of at least one hierarchy and/or the hierarchy relationship among the flow sub-components.

According to embodiments of the present disclosure, the upper and lower hierarchical relationship may be understood as: the upper layer capability requirement information or flow sub-component may include multiple types of lower layer capability requirement information or flow sub-components; from the lower level capability requirement information or flow sub-components, at least one upper level capability requirement information or flow sub-component associated therewith may be determined.

At least one business entity information that matches the business execution link information in the entity component is determined in operation S230.

According to an embodiment of the present disclosure, the entity component includes a plurality of business entities that are pre-built, each business entity corresponding to a business entity name and at least one business entity attribute.

According to the embodiment of the disclosure, in the process of determining at least one business entity information matched with business execution link information in an entity assembly, the business execution link information is matched with a plurality of pre-built business entities in the entity assembly. Under the condition that the corresponding business entity information is not matched in the pre-constructed entity assembly, the business entity information corresponding to the business execution link information can be newly built in the entity assembly so as to enrich the resources of the entity assembly.

According to embodiments of the present disclosure, the service execution link information may correspond to at least one service entity in order to implement code resources of the entire service execution link and a service system architecture to be constructed based on the at least one service entity.

In operation S240, respective data table information of at least one service entity information is determined so that the internet technology architecture forms a service system corresponding to a service behavior to be implemented using the data table information.

According to embodiments of the present disclosure, the data table information may be code resources in an internet technology (Internet Technology, IT) architecture. The data table information comprises a data table name, and the data table comprises a plurality of fields for describing the service entity name and the service entity attribute.

According to the embodiment of the disclosure, after the data table information corresponding to the service entity is determined, a developer can directly encode and develop based on the corresponding data table information without interfacing with the service person and checking the service execution link.

For example, still taking the example that the business behavior to be implemented is a counsel service, the docked business entity may be a processing results table. The problem statistics table comprises an account number, a reply customer service number, a problem type, a problem number, a processing result, a processing duration and other fields.

According to an embodiment of the present disclosure, the capability text data may include first capability requirement information and second capability requirement information, the first capability requirement information being disposed at an upper layer of the second capability requirement information.

According to an embodiment of the present disclosure, at least one hierarchy of capability requirement information, for example, third capability requirement information and fourth capability requirement information, may be further included between the first capability requirement information and the second capability requirement information.

According to embodiments of the present disclosure, the at least one hierarchy of capability requirement information may correspond to a capability subcomponent in the capability component.

The capability text data is obtained, for example, by performing semantic processing on the acquired text data. The capability text data includes text topics under which capability requirement information corresponding to at least one hierarchy level. The first capability requirement information corresponds to a target capability sub-component, the second capability requirement information corresponds to a refined capability requirement sub-component, the third capability requirement information between the first capability requirement information and the second capability requirement information corresponds to a higher-order capability requirement sub-component, and the fourth capability requirement information corresponds to a business capability sub-component. Wherein the higher-order capability requirement sub-component includes a refine capability requirement sub-component, and the fourth capability requirement information is located at a level above the third capability requirement information.

According to an embodiment of the present disclosure, the capability requirement information corresponds to capability definition text for defining implementation conditions of the capability requirement information. The flow sub-components in the flow components each correspond to component definition text that defines the hierarchy to which each component in the flow components belongs, component processing conditions, and the like.

According to an embodiment of the present disclosure, the value chain sub-component, the task sub-component, and the execution step sub-component are arranged in a hierarchical order from top to bottom. A value chain may be understood as information defined in terms of business categories, e.g., the value chain includes funds, financing, production, manufacturing, etc. The tasks and executing steps are information which falls into a specific implementation process in the service field.

FIG. 3 schematically illustrates a schematic diagram of semantically processed capability text data according to an embodiment of the present disclosure.

As shown in FIG. 3, "run relationship XXX" in semantically processed capability text data 300 is a text topic. The text subject is respectively first capability requirement information, fourth capability requirement information, third capability requirement information and second capability requirement information according to the sequence from top to bottom of the hierarchy. Each capability requirement information may include information in at least one direction.

For example, the first capability requirement information "2. Smart XXX" includes the fourth capability requirement information "2.1 enhanced XXX" and "2.2 forged XXX".

According to the embodiment of the disclosure, after semantic processing, at least one text theme can be obtained from the acquired text data, and each text theme comprises at least one level of capability requirement information. The process of semantic processing will be explained below taking a text topic as an example.

According to an embodiment of the present disclosure, the step S210 of semantically processing the acquired text data to obtain capability text data includes: disassembling the text data and extracting text subjects; identifying a business target from the text theme to form business capability; disassembling a business target based on a preset capacity requirement to form a high-order capacity requirement, and further separating out a refinement capacity requirement according to the preset capacity requirement; the system clusters the higher-order capacity demands under the text subject to obtain the business capacity; clustering the service capabilities to form target capabilities and forming a requirement link of target capability-service capability-high-order capability requirement-refinement capability requirement.

According to an embodiment of the present disclosure, extracting text topics includes: based on the service dictionary, matching a plurality of keywords from the text data, and marking the parts of speech of the keywords; and aggregating a plurality of keywords according to the text sentence structure to obtain a text theme. Wherein, the keyword part of speech includes: the text sentence composing structure comprises a standard structure of a subject-a position-an object and further comprises an expansion structure of the subject-the predicate-the object and the like.

According to an embodiment of the present disclosure, dismantling a business objective based on a predetermined capability requirement to form a higher-order capability requirement, and further splitting a refinement capability requirement according to the predetermined capability requirement includes: and determining corresponding high-order capacity requirements or refinement capacity requirements according to the text similarity according to the definition of the preset capacity requirements or business requirements.

According to an embodiment of the present disclosure, clustering business capabilities under text topics, forming target capabilities includes: and extracting keywords with highest occurrence frequency from a plurality of business capabilities under the text theme to form target capability.

According to an embodiment of the present disclosure, a plurality of first capability requirement information may be included under the same text subject, and a plurality of second capability requirement information may be included under each of the first capability requirement information. The process of generating the service execution link information will be described below taking a single first capability requirement information as an example.

According to an embodiment of the present disclosure, operation S220 further includes the steps of:

determining a target value chain sub-component according to a first text similarity between the first capability definition text and the first component definition text; s execution step subassemblies related to the target value chain subassembly are determined, wherein S is more than or equal to N is more than or equal to 1; according to the second text similarity between the second capability definition text and the second component definition text, determining N target execution step sub-components from the S execution step sub-components, wherein the target execution step sub-components uniquely correspond to the second capability requirement information; determining P target task sub-components according to respective third text similarity of the third component definition text and N second capability definition texts, wherein P is more than or equal to N is more than or equal to 1; and determining service execution link information corresponding to the text data based on the target value chain sub-component, the P target task sub-components and the N target execution step sub-components.

According to embodiments of the present disclosure, a natural language model (Natural Language Processing, NLP) may be employed to process the first capability definition text and the first component definition text, processing the text data into semantic vectors; the similarity between the two semantic vectors is taken as the first text similarity.

According to embodiments of the present disclosure, there is a unique correspondence between the first capability requirement information and the value chain sub-component. A first text similarity between the first capability definition text and the plurality of value chain sub-components may be calculated, with the value chain sub-component having the highest first text similarity being determined to be the target value chain sub-component.

It should be noted that, for the newly added text data, the first capability requirement information and the second capability requirement information are both newly added information, and the matching needs to be performed between the capability definition text and the component definition text according to the capability definition text, so as to interface the value chain sub-component or execute the step sub-component. For non-newly added text data, because the docking is completed in the newly added process, the corresponding target value chain sub-component can be directly determined according to the established docking relationship.

According to the embodiment of the disclosure, because the corresponding S execution step sub-models are under the target value chain sub-model, the second capability requirement information and the execution step sub-models are in a unique corresponding relationship, and therefore, N execution step sub-assemblies can be screened out from the S execution step sub-assemblies according to the second text similarity to be in one-to-one correspondence with the second capability requirement information.

According to the embodiment of the disclosure, the second capability requirement information is in one-to-many relation with the task sub-components, so that one or more task sub-components with the third text similarity higher than the similarity threshold can be determined as target task sub-components by setting the similarity threshold.

According to the embodiment of the present disclosure, the process of calculating the second text similarity and the third text similarity is similar to the method of calculating the first text similarity described above, and will not be described herein.

According to the embodiment of the disclosure, since the first capability requirement information and the second capability requirement information are unique corresponding relations with the flow components, the subcomponent range of the service execution link information can be framed by utilizing the first capability requirement information located at the first level and the second capability requirement information located at the last level; and then, according to the hierarchical relation between the capability requirement information, the service execution link information can be simply obtained by aggregation, so that the complexity of the docking operation is greatly reduced, and the docking efficiency of the flow component and the capability component is improved.

According to an embodiment of the present disclosure, the second component definition text includes an execution step name and a step rule name. Determining N target execution step sub-components from the S execution step sub-components according to a second text similarity between the second capability definition text and the second component definition text, including: determining the respective combined text of S execution step sub-components according to the execution step names and the step rule names; and calculating second text similarity between the S combined texts and the second capability definition texts aiming at the second capability definition texts of the nth second capability requirement information, and determining an execution step sub-component corresponding to the second text similarity with the highest similarity as a target execution step sub-component corresponding to the nth second capability requirement information, wherein N is more than or equal to N is more than or equal to 1.

According to an embodiment of the present disclosure, the execute step name is used to uniquely identify the execute step sub-component and the step rule name is used to determine the step defined by the uniquely identify the execute step sub-component.

According to an embodiment of the present disclosure, the combined text may be obtained by randomly combining the execution step name and the step rule name. And randomly combining the execution step name and the step rule name of each execution step sub-model aiming at S execution step sub-models matched with the target value chain sub-model, so that S combined texts can be obtained.

According to an embodiment of the present disclosure, after determining the combined text, for each second capability requirement information, second text similarity between S combined texts and the second capability definition text is calculated, and an execution step sub-component corresponding to the second text similarity having the highest similarity is determined as a target execution step sub-component corresponding to the nth second capability requirement information.

According to embodiments of the present disclosure, since the step rules may be multiplexed among tasks, the second capability requirement information has a 1-to-many interfacing relationship with the task sub-components.

According to the embodiment of the disclosure, in the case that the execution step sub-assembly or the task sub-assembly fails to dock with the second capability requirement information, the second capability requirement information of the docking failure is returned to the terminal equipment of the service personnel, so that the service personnel manually selects the matched target execution step sub-assembly or the target task sub-assembly.

According to the embodiment of the disclosure, since the acquired text data may be newly added text, in case of a docking failure, the business personnel may also create a target execution step sub-component or a target task sub-component corresponding to the second capability requirement information of the docking failure in real time.

In the embodiment of the disclosure, because the number of the execution step sub-components related in the flow component is huge and the definition rule is complex, the best matched target execution step sub-components can be determined from the two aspects of the name and the content together by executing the step name step rule name, so that the target execution step sub-components can be accurately matched in a larger range.

According to an embodiment of the present disclosure, the capability text data further includes third capability requirement information between the first capability requirement information and the second capability requirement information; the flow component further comprises a business field sub-component, a value flow sub-component and an activity sub-component.

Based on the target value chain sub-component, the P target task sub-components and the N target execution step sub-components, determining the service execution link information corresponding to the text data comprises: determining at least P target activity subassemblies according to the P target task subassemblies based on a first association relationship, wherein the first association relationship is used for representing the association relationship between the task subassemblies and the activity subassemblies; determining at least P target business field subassemblies and at least P value flow subassemblies according to at least P target activity subassemblies based on a second association relationship, wherein the second association relationship is used for representing a hierarchical association relationship between third capability requirement information and second capability requirement; and determining service execution link information corresponding to the text data according to the target value chain sub-component, at least P target service domain sub-components, at least P value stream sub-components, at least P target activity sub-components, P target task sub-components and N target execution step sub-components based on the hierarchical association relation between the capability requirement information.

According to an embodiment of the present disclosure, there is at least one hierarchy of sub-components within the flow component, each hierarchy of sub-components has an association, and each hierarchy of capability requirements also has an association. The first association is used for representing the association between the task sub-component and the activity sub-component, and the second association is used for representing the hierarchical association between the task third capability requirement information and the second capability requirement. The third association is used for representing a hierarchical association between the third capability requirement information and the fourth capability requirement information.

According to the embodiment of the disclosure, the task sub-components are located at the upper layer of the active sub-components, and a fixed first association relation exists between the task sub-components and the active sub-components, and each active sub-component can comprise at least one task sub-component, so that at least P target active sub-components can be determined according to P target task sub-components.

According to the embodiment of the disclosure, since the second association relationship characterizes the relationship between the third capability requirement information and the second capability requirement, the target execution step sub-component corresponds to the second capability requirement information one by one, and therefore, after the target activity sub-component is determined according to the target execution step sub-component, the association relationship between the third capability requirement information and the activity sub-component can be established.

According to embodiments of the present disclosure, since tasks can be multiplexed among activities, the third capability requirement information has a 1-to-many interfacing relationship with the activity sub-components.

According to the embodiment of the disclosure, the service domain sub-components, the value stream sub-components and the activity sub-components are arranged from top to bottom according to the level, and the activities can be multiplexed among the value stream and the service domain. A third association exists between the fourth capability requirement information and the third capability requirement. Thus, according to the third association, the relationship between the active sub-component and the value flow sub-component, the relationship between the active sub-component and the business domain sub-component, at least P target business domain sub-components and at least P value flow sub-components that interface with the fourth capability requirement information can be determined. Wherein, since activities can be multiplexed between value flows, business domains, one activity sub-component can interface at least one business domain sub-component and at least one value flow sub-component.

According to the embodiment of the disclosure, based on the hierarchical association relationship between the capability requirement information, the determined target value chain sub-component, the target service field sub-component, the target value stream sub-component, the target activity sub-component, the target task sub-component and the target execution step sub-component can form service execution link information according to the hierarchical relationship.

According to the embodiment of the disclosure, the relationship among the components is carded through the association relationship, so that the service execution link information can be rapidly generated.

According to embodiments of the present disclosure, for sub-assemblies that fail to dock, the developer is returned and manually docked or the matching is done by the developer with the new sub-assembly.

According to an embodiment of the present disclosure, determining at least one business entity information in the entity component that matches the business execution link information includes: acquiring N target execution step sub-components in service execution link information; and determining the business entity information corresponding to each target execution step sub-assembly according to the mapping relation between each target execution step sub-assembly and the business entity, so as to obtain at least N pieces of business entity information.

According to the embodiment of the disclosure, since the minimum granularity of the service execution link information is the execution step, in order to facilitate the interfacing of the corresponding code resources, the execution step subcomponent of the minimum granularity is matched with the service entity information.

According to an embodiment of the present disclosure, the business entity information may include a business entity name for uniquely identifying the business entity and business entity attributes for describing a plurality of attribute information of the business entity. For example, the business entity may be an account, the attribute information may be an account opening time, an account level, and the like.

According to embodiments of the present disclosure, each execution step may match at least one business entity information, and thus, the N target execution step subcomponents may match at least N business entity information.

According to the embodiment of the disclosure, a mapping relationship between each target execution step sub-component and the service entity is preset and established.

For example, still taking the business action to be implemented as a counseling service as an example, the target execution step subcomponent is "step S102-2" for executing "collect account query". The business entity corresponding to the target execution step sub-component is account and problem.

According to an embodiment of the present disclosure, determining respective data table information of at least one business entity information includes: for each business entity information, determining an object code entity according to the mapping relation between the business entity name and the code entity; and determining the data table information of the target code entity according to the target code entity.

According to the embodiment of the disclosure, the service entity refers to an entity of the service side docking, and the code entity refers to an entity corresponding to the development side. The names of the service side and the development side for the same information may be different, so after the service entity is determined, the service entity of the service side can be docked to the code entity according to the mapping relationship between the service entity name and the code entity, so as to obtain the target code entity.

In the embodiment of the disclosure, as the data between the service side and the development side are not universal, the target code entity is rapidly positioned through the defined mapping relation between the service entity and the code entity, so that the data table information of the target code entity is determined, the interactive communication cost is reduced, and the efficiency is improved.

Fig. 4 schematically illustrates a flowchart of a method of determining traffic execution link information according to an embodiment of the present disclosure.

As shown in fig. 4, the first capability requirement information is a target capability, the second capability requirement information is a refined capability requirement, the third capability requirement information is high-order capability requirement information, and the fourth capability requirement information is a service capability. The target capacity and the value chain are 1:1, the service capability, the service field and the value flow are 1: the docking relationship between the higher-order capacity requirement and the activity is 1: and the butting relation of N is 1 between the refinement capability demand information and the task: the butting relation of N is 1 between the refinement capability demand information and the execution steps: 1. And all the flow components after the butt joint form service execution link information.

As shown in fig. 4, the execution steps are 1: n butt-joint relationship. The service entity and the code entity in the IT architecture are 1:1, mapping the interfacing relation, the code entity and the table are 1:1, each table may include a plurality of fields therein.

Note that, in fig. 4, 1: n represents only one-to-many interfacing, and does not represent a specific number or number.

According to embodiments of the present disclosure, there is an association between the execution step subcomponent and the entity component. And for the stored content, the system directly maps to finish the butt joint of the final service data table and the fields. And for the newly added part of the flow component due to iteration work, the newly added execution step sub-component is transferred to a development center to perform the butt joint work of the flow and the entity model, and the newly added entity completes the association of the entity component and the code entity, the data table and the field in the IT architecture by the development center. Thus, the link penetration work of the digital management of the enterprise planning floor is completed.

According to an embodiment of the present disclosure, the method further comprises: in response to receiving the first display instruction, analyzing the first display instruction to obtain target capacity requirement information; displaying target capability requirement information and a plurality of capability requirement information under the layer to which the target capability requirement information belongs in a layer form, simultaneously displaying service execution link information in a first display area and data table information in a second display area; wherein the first display area is related to the capability requirement information, and the second display area is related to the service execution link information.

According to embodiments of the present disclosure, after determining the data table information of the service execution link information and the service entity information, the information may be presented to the user at the interactive interface.

According to the embodiment of the disclosure, a user can select target capability requirement information to be displayed on the interactive interface, and a first display instruction is formed based on the target capability requirement information. After the server or the terminal equipment analyzes the target capability requirement information, the target capability requirement information and a plurality of capability requirement information under the layer to which the target capability requirement information belongs can be displayed in a layer form, meanwhile, the service execution link information is displayed in a first display area, and the data table information is displayed in a second display area; wherein the first display area is related to the capability requirement information, and the second display area is related to the service execution link information.

Fig. 5 schematically illustrates a presentation interface diagram in response to receiving a first presentation instruction according to an embodiment of the present disclosure.

As shown in FIG. 5, the user selected target capability requirement information may be a business capability "2.2 forge XXX".

To the left of the presentation interface 500 is an upper level target capability "2. Smart XXX" showing the business capability "2.2 forge XXX" in a hierarchical form, and a text topic to which the business capability belongs, and other business capabilities under the target capability "2. Smart XXX" such as business capability 2.1 are not presented. Under the business capability "2.2 forge XXX," a plurality of higher-order capability requirements, each under a refinement capability requirement, are detailed for the business capability to include.

The first display area may be an area beside the capability requirement information, and the second display area may be an area beside the service execution link information.

The first display area in the display interface 500 includes "market management (value chain)", "marketing management (business field)", "specify scheme, create campaign (activity)", "select customer group, execute contact (task)", "1, determine product from user habits, 2, determine contact from user behavior (execute step)". The second presentation area in the presentation interface 500 includes "habit table, behavior table" and "account, channel, number … (field)".

According to embodiments of the present disclosure, a user may also be able to select the table and field information to be presented at the interactive interface.

According to an embodiment of the present disclosure, the method further comprises: in response to receiving the second display instruction, analyzing the second display instruction to obtain target capacity demand information, L target data table information and Q target fields, wherein Q is more than or equal to 1, and L is more than or equal to 1; displaying target capability requirement information and a plurality of capability requirement information under the layer to which the target capability requirement information belongs in a layer form, simultaneously displaying service execution link information in a first display area, and displaying L target data table information and Q target fields in a second display area; wherein the first display area is related to the capability requirement information, and the second display area is related to the service execution link information.

According to an embodiment of the present disclosure, operations of displaying the target capability requirement information, the L target data table information, and the Q target fields are similar to those described above, and only the selected L target data table information and Q target fields are displayed in the second display area, and the unselected other data table information and fields are not displayed.

Fig. 6 schematically illustrates an interaction scenario diagram according to an embodiment of the present disclosure.

As shown in fig. 6, an interaction scenario 600 illustrates an interaction scenario of a user and a system. Wherein, the user can interact with the system by using the terminal equipment.

According to embodiments of the present disclosure, a user may select a capability to generate a first presentation instruction. The system displays capability requirement information and related data tables and fields according to the first display instruction. The user selects the capability sub-components (target capability, service capability, high-order capability requirement and refinement capability requirement) in the concerned capability components, can singly select or multiply select, and displays the whole quantity if the capability sub-components are not selected; the system automatically displays the capacity sub-components of the subordinate hierarchy of the capacity sub-components selected by the user in full, for example: the user clicks the service capability A, and then the full high-order capability requirement and the refinement capability requirement under the A are displayed; and the system automatically retrieves the data table and the fields for displaying according to the service execution link information.

The user may also select the capability, and the data table and fields of interest, to generate a second presentation instruction. The system displays capability requirement information and related data tables and fields according to the first display instruction. The user selects the concerned data table and field, the system performs service data statistics, and outputs service data statistics information, such as: the user selects the deposit amount field and the system automatically displays the deposit amount from the docking point in time to date and the same data.

The system can also output business data statistics and generate enterprise planning floor reports. For example, the system labels and displays the whole view of the capability units positioned by the user and the related business data results of each capability unit to form an enterprise planning floor report.

Fig. 7 schematically shows a block diagram of a text data processing apparatus according to an embodiment of the present disclosure.

As shown in fig. 7, the text data processing apparatus 700 of this embodiment includes a semantic processing module 710, a first determination module 720, a second determination module 730, and a third determination module 740.

The semantic processing module 710 is configured to perform semantic processing on the obtained text data to obtain capability text data, where the capability text data includes capability requirement information, the obtained text data is used to describe a to-be-implemented business behavior of the organization, and the capability text data is used to describe capability restriction information for completing the to-be-implemented business behavior. In an embodiment, the semantic processing module 710 may be configured to perform the operation S210 described above, which is not described herein.

The first determining module 720 is configured to determine service execution link information of the text data according to the capability requirement information and the component definition text of the flow component. In an embodiment, the first determining module 720 may be configured to perform the operation S220 described above, which is not described herein.

A second determining module 730, configured to determine at least one service entity information in the entity component that matches the service execution link information. In an embodiment, the second determining module 730 may be configured to perform the operation S230 described above, which is not described herein.

The third determining module 740 is configured to determine the respective data table information of the at least one service entity information, so that the internet technology architecture forms a service system corresponding to the service behavior to be implemented using the data table information. In an embodiment, the third determining module 740 may be configured to perform the operation S240 described above, which is not described herein.

According to an embodiment of the present disclosure, the first determining module 720 includes a first determining unit, a second determining unit, a third determining unit, a fourth determining unit, and a fifth determining unit.

The first determining unit is used for determining the target value chain sub-component according to a first text similarity between the first capability definition text and the first component definition text.

The second determining unit is used for determining S execution step subassemblies related to the target value chain subassembly, wherein S is more than or equal to N is more than or equal to 1.

The third determining unit is configured to determine N target execution step sub-components from the S execution step sub-components according to a second text similarity between the second capability definition text and the second component definition text, where the target execution step sub-components uniquely correspond to the second capability requirement information.

The fourth determining unit is used for determining P target task sub-components according to respective third text similarity of the third component definition text and the N second capability definition texts, wherein P is more than or equal to N is more than or equal to 1.

The fifth determining unit is configured to determine service execution link information corresponding to the text data based on the target value chain sub-component, the P target task sub-components, and the N target execution step sub-components.

According to an embodiment of the present disclosure, the second component definition text includes an execution step name and a step rule name.

According to an embodiment of the present disclosure, the third determination unit includes a first determination subunit and a second determination subunit.

The first determining subunit is configured to determine, according to the execution step name and the step rule name, a combined text of each of the S execution step subassemblies.

The second determining subunit is configured to calculate a second text similarity between the S combined texts and the second capability definition text for a second capability definition text of the nth second capability requirement information, and determine an execution step sub-component corresponding to the second text similarity with the highest similarity as a target execution step sub-component corresponding to the nth second capability requirement information, where N is greater than or equal to 1.

According to an embodiment of the present disclosure, the fifth determining unit includes a third determining subunit, a fourth determining subunit, and a fifth determining subunit.

The third determining subunit is configured to determine at least P target activity subassemblies according to the P target task subassemblies based on a first association relationship, where the first association relationship is used to characterize an association relationship between the task subassemblies and the activity subassemblies.

The fourth determining subunit is configured to determine, based on the second association relationship, at least P target service domain subassemblies and at least P value flow subassemblies according to at least P target activity subassemblies, where the second association relationship is used to characterize a hierarchical association relationship between the third capability requirement information and the second capability requirement.

The fifth determining subunit is configured to determine, based on the hierarchical association relationship between the capability requirement information, service execution link information corresponding to the text data according to the target value chain subassembly, at least P target service domain subassemblies, at least P value flow subassemblies, at least P target activity subassemblies, at least P target task subassemblies, and N target execution step subassemblies.

According to an embodiment of the present disclosure, the second determining module 730 includes an acquiring unit and a sixth determining unit.

The acquisition unit is used for acquiring N target execution step sub-components in the service execution link information.

And the sixth determining unit is used for determining the business entity information corresponding to each target execution step sub-assembly according to the mapping relation between each target execution step sub-assembly and the business entity, so as to obtain at least N pieces of business entity information.

According to an embodiment of the present disclosure, the business entity information includes a business entity name and a business entity attribute. The third determination module 740 includes a seventh determination unit and an eighth determination unit. For each of the business entity information,

and the seventh determining unit is used for determining the target code entity according to the mapping relation between the service entity name and the code entity.

The eighth determining unit is used for determining data table information of the target code entity according to the target code entity.

According to an embodiment of the present disclosure, the text data processing apparatus 700 further includes a first display module including a first parsing unit and a first display unit.

The first analysis unit is used for responding to the received first display instruction and analyzing the first display instruction to obtain the target capacity requirement information.

The second analysis unit is used for displaying the target capability requirement information and a plurality of capability requirement information under the layer of the target capability requirement information in a layer form, simultaneously displaying service execution link information in a first display area and displaying data table information in a second display area; wherein the first display area is related to the capability requirement information, and the second display area is related to the service execution link information.

According to an embodiment of the present disclosure, the text data processing apparatus 700 further includes a second display module including a second parsing unit and a second display unit.

The second analysis unit is used for responding to the second display instruction, analyzing the second display instruction to obtain target capacity demand information, L target data table information and Q target fields, wherein Q is more than or equal to 1, and L is more than or equal to 1.

The second analysis unit is used for displaying the target capability requirement information and a plurality of capability requirement information under the layer to which the target capability requirement information belongs in a layer form, simultaneously displaying service execution link information in a first display area, and displaying L target data table information and Q target fields in a second display area; wherein the first display area is related to the capability requirement information, and the second display area is related to the service execution link information.

According to an embodiment of the present disclosure, any of the plurality of modules of the semantic processing module 710, the first determining module 720, the second determining module 730, and the third determining module 740 may be combined in one module to be implemented, or any of the plurality of modules may be split into a plurality of modules. Alternatively, at least some of the functionality of one or more of the modules may be combined with at least some of the functionality of other modules and implemented in one module.

According to embodiments of the present disclosure, at least one of the semantic processing module 710, the first determination module 720, the second determination module 730, and the third determination module 740 may be implemented at least in part as hardware circuitry, 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 as hardware or firmware by any other reasonable means of integrating or packaging the circuitry, or as any one of or a suitable combination of any of the three. Alternatively, at least one of the semantic processing module 710, the first determination module 720, the second determination module 730, and the third determination module 740 may be at least partially implemented as a computer program module that, when executed, performs the corresponding functions.

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

In the RAM 803, various programs and data required for the operation of the electronic device 800 are stored. The processor 801, the ROM 802, and the RAM 803 are connected to each other by a bus 804. The processor 801 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 802 and/or the RAM 803. Note that the program may be stored in one or more memories other than the ROM 802 and the RAM 803. The processor 801 may also perform various operations of the method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.

According to an embodiment of the present disclosure, the electronic device 800 may also include an input/output (I/O) interface 805, the input/output (I/O) interface 805 also being connected to the bus 804. The electronic device 800 may also include one or more of the following components connected to the input/output I/O interface 805: an input portion 806 including a keyboard, mouse, etc.; an output portion 807 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage section 808 including a hard disk or the like; and a communication section 809 including a network interface card such as a LAN card, a modem, or the like. The communication section 809 performs communication processing via a network such as the internet. The drive 810 is also connected to the I/O interface 805 as needed. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as needed so that a computer program read out therefrom is mounted into the storage section 808 as needed.

The present disclosure also provides a computer-readable storage medium that may be embodied in the apparatus/device/system described in the above embodiments; or may exist alone without being assembled into the apparatus/device/system. The computer-readable storage medium carries one or more programs which, when executed, implement methods in accordance with embodiments of the present 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 context of this 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, the computer-readable storage medium may include ROM 802 and/or RAM 803 and/or one or more memories other than ROM 802 and RAM 803 described above.

Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowcharts. The program code, when executed in a computer system, causes the computer system to perform the methods provided by embodiments of the present disclosure.

The above-described functions defined in the system/apparatus of the embodiments of the present disclosure are performed when the computer program is executed by the processor 801. The systems, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.

In one embodiment, the computer program may be based on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted, distributed, and downloaded and installed in the form of a signal on a network medium, and/or from a removable medium 811 via a communication portion 809. The computer program may include program code that may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

In such an embodiment, the computer program may be downloaded and installed from a network via the communication section 809, and/or installed from the removable media 811. The above-described functions defined in the system of the embodiments of the present disclosure are performed when the computer program is executed by the processor 801. The systems, devices, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.

According to embodiments of the present disclosure, program code for performing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, such computer programs may be implemented in high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. Programming languages include, but are not limited to, such as Java, c++, python, "C" or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Those skilled in the art will appreciate that the features recited in the various embodiments of the disclosure and/or in the claims may be provided in a variety of combinations and/or combinations, even if such combinations or combinations are not explicitly recited in the disclosure. In particular, the features recited in the various embodiments of the present disclosure and/or the claims may be variously combined and/or combined without departing from the spirit and teachings of the present disclosure. All such combinations and/or combinations fall within the scope of the present disclosure.

While the foregoing is directed to embodiments of the present disclosure, other and further details of the invention may be had by the present application, it is to be understood that the foregoing description is merely exemplary of the present disclosure and that no limitations are intended to the scope of the disclosure, except insofar as modifications, equivalents, improvements or modifications may be made without departing from the spirit and principles of the present disclosure.

Claims

1. A text data processing method, comprising:

carrying out semantic processing on the acquired text data to obtain capability text data, wherein the capability text data comprises capability requirement information, the acquired text data is used for describing service behaviors to be implemented of a mechanism, and the capability text data is used for describing capability limiting information for completing the service behaviors to be implemented;

determining service execution link information of the text data according to the capability requirement information and a component definition text of a flow component;

determining at least one business entity information matched with the business execution link information in an entity assembly; and

and determining the data table information of each at least one business entity information so that the Internet technical architecture forms a business system corresponding to the business behavior to be implemented by utilizing the data table information.

2. The method of claim 1, wherein the capability text data includes first capability requirement information of a first hierarchy and N pieces of second capability requirement information related to the first capability requirement information in a last hierarchy, the first capability requirement information corresponding to a first capability definition text, the N pieces of second capability requirement information each corresponding to a second capability definition text, N being equal to or greater than 1; the process component comprises a value chain sub-component, a task sub-component and an execution step sub-component, wherein the value chain sub-component corresponds to a first component definition text, the execution step sub-component corresponds to a second component definition text, and the task sub-component corresponds to a third component definition text.

3. The method of claim 2, wherein the determining the service execution link information corresponding to the text data according to the capability requirement information and the component definition text of the flow component comprises:

s execution step sub-components related to the target value chain sub-component are determined, wherein S is more than or equal to N is more than or equal to 1;

Determining N target execution step sub-components from S execution step sub-components according to second text similarity between the second capability definition text and the second component definition text, wherein the target execution step sub-components uniquely correspond to the second capability requirement information;

determining P target task sub-components according to respective third text similarity between the third component definition text and N second capability definition texts, wherein P is more than or equal to N is more than or equal to 1;

4. The method of claim 3, wherein the second component definition text includes an execution step name and a step rule name;

the determining N target execution step sub-components from S execution step sub-components according to a second text similarity between the second capability definition text and the second component definition text includes:

determining the combined text of each of S execution step subassemblies according to the execution step names and the step rule names;

And calculating second text similarity between S combined texts and the second capability definition texts aiming at second capability definition texts of the nth second capability requirement information, and determining an execution step sub-component corresponding to the second text similarity with the highest similarity as a target execution step sub-component corresponding to the nth second capability requirement information, wherein N is more than or equal to 1.

5. The method of claim 3, wherein the capability text data further includes third capability requirement information between the first capability requirement information and the second capability requirement information; the flow component also comprises a business field sub-component, a value flow sub-component and an activity sub-component;

the determining, based on the target value chain sub-component, the P target task sub-components, and the N target execution step sub-components, service execution link information corresponding to the text data includes:

6. The method according to any one of claims 1-5, wherein determining at least one business entity information in the determining entity component that matches the business execution link information comprises:

acquiring N target execution step sub-components in the service execution link information; and

and determining service entity information corresponding to each target execution step sub-assembly according to the mapping relation between each target execution step sub-assembly and the service entity, and obtaining at least N pieces of service entity information.

7. The method of claim 6, wherein the business entity information comprises a business entity name and a business entity attribute;

the determining the data table information of each of the at least one business entity information comprises the following steps: for each of the business entity information,

and determining data table information of the target code entity according to the target code entity.

8. The method of claim 1, further comprising:

in response to receiving a first display instruction, analyzing the first display instruction to obtain target capacity demand information;

displaying the target capability requirement information and a plurality of capability requirement information under the layer of the target capability requirement information in a layer form, simultaneously displaying the service execution link information in a first display area and the data sheet information in a second display area;

9. The method of claim 1, further comprising:

in response to receiving a second display instruction, analyzing the second display instruction to obtain target capacity demand information, L target data table information and Q target fields, wherein Q is more than or equal to 1, and L is more than or equal to 1;

displaying the target capability requirement information and a plurality of capability requirement information under the layer of the target capability requirement information in a layer form, simultaneously displaying the service execution link information in a first display area, and displaying L target data table information and Q target fields in a second display area;

10. A text data processing apparatus comprising:

a second determining module, configured to determine at least one service entity information that matches the service execution link information in the entity component; and

11. An electronic device, comprising:

One or more processors;

storage means for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-9.

12. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the method according to any of claims 1 to 9.