Information transfer method and apparatus, medium, and electronic device

Abstract

The present disclosure relates to the technical field of electronics, and relates to an information transfer method and apparatus, a medium, and an electronic device. The information transfer method comprises: importing a PRD into a PRD layer, importing IDL information into an IDL method layer and an IDL structure layer, and importing a database table structure into a data layer; using the name of a structure in the IDL structure layer and the name of a field in the structure as keywords for searching, and matching a data structure in the data layer with the structure in the IDL structure layer to obtain a first matching result; using the name of the matched structure in the first matching result and the name of the field in the structure as keywords for searching, and matching the matched structure in the IDL structure layer with an entity in the PRD layer to obtain a second matching result; and transmitting a primary key and unique key information in the data layer to a front-end code layer on the basis of the first and second matching results.

Description

Information flow method, device, medium and electronic equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is based on and claims priority to the Chinese patent application with application number 202310876892.0 and application date July 17, 2023. The disclosed content of the Chinese patent application is hereby introduced as a whole into this application. Technical Field

[0003] The present disclosure relates to the field of electronic technology, and in particular to an information flow method, device, medium and electronic device. Background Art

[0004] For front-end product development, low-code development is usually used to improve efficiency in the process of building a new platform. Low-code development refers to a development method that requires little or no code to quickly develop a system.

[0005] Summary of the Invention

[0006] This summary is provided to briefly introduce concepts that will be described in detail in the detailed description below. This summary is not intended to identify key features or essential features of the claimed technical solution, nor is it intended to limit the scope of the claimed technical solution.

[0007] In a first aspect, the present disclosure provides an information flow method, comprising: importing a product requirement document into a product requirement document layer, importing interface description language information into an interface description language method layer and an interface description language structure layer, and importing a library table structure into a data layer; searching by using the name of the structure in the interface description language structure layer and the name of the field in the structure as keywords, matching the data structure in the data layer with the structure in the interface description language structure layer to obtain a first matching result; searching by using the name of the structure matched in the first matching result and the name of the field in the structure as keywords, matching the structure matched in the interface description language structure layer with the entity in the product requirement document layer to obtain a second matching result; and based on the first matching result and the second matching result, passing the primary key and unique key information in the data layer to the front-end code layer.

[0008] In the second aspect, the present disclosure provides an information flow device, including: an import module, used to import a product requirement document into the product requirement document layer, import the interface description language information into the interface description language method layer and the interface description language structure layer, and import the library table structure into the data layer; a first matching module, used to search by using the name of the structure in the interface description language structure layer and the name of the field in the structure as keywords, and match the data structure in the data layer with the structure in the interface description language structure layer to obtain a first matching result; a second matching module, used to search by using the name of the structure matched in the first matching result and the name of the field in the structure as keywords, and match the structure matched in the interface description language structure layer with the entity in the product requirement document layer to obtain a second matching result; and a transfer module, used to transfer the primary key and unique key information in the data layer to the front-end code layer based on the first matching result and the second matching result.

[0009] In a third aspect, the present disclosure provides a computer-readable medium having a computer program stored thereon, which, when executed by a processing device, implements the steps of any one of the methods described in the first aspect.

[0010] In a fourth aspect, the present disclosure provides an electronic device, comprising: a storage device on which a computer program is stored; and a processing device for executing the computer program in the storage device to implement the steps of any one of the methods described in the first aspect.

[0011] Other features and advantages of the present disclosure will be described in detail in the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The above and other features, advantages and aspects of the various embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and that the originals and elements are not necessarily drawn to scale. In the drawings:

[0013] FIG1 is a hierarchical framework diagram of a business system according to an embodiment of the present disclosure.

[0014] FIG2 is a flowchart of an information transfer method according to an embodiment of the present disclosure.

[0015] FIG3 is another flowchart of an information transfer method according to an embodiment of the present disclosure.

[0016] FIG4 is a schematic block diagram of an information flow device according to an embodiment of the present disclosure.

[0017] FIG5 is another schematic block diagram of an information flow device according to an embodiment of the present disclosure.

[0018] FIG6 shows a schematic structural diagram of an electronic device suitable for implementing the embodiments of the present disclosure. DETAILED DESCRIPTION

[0019] The following describes embodiments of the present disclosure in more detail with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure.

[0020] It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this respect.

[0021] As used herein, the term "including" and its variations are open-ended, i.e., "including but not limited to." The term "based on" means "based, at least in part, on." The term "one embodiment" means "at least one embodiment," the term "another embodiment" means "at least one additional embodiment," and the term "some embodiments" means "at least some embodiments." Other terms are defined in the following description.

[0022] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0023] It should be noted that the modifications of "one" and "multiple" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, they should be understood as "one or more".

[0024] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0025] It is understandable that before using the technical solutions disclosed in the various embodiments of this disclosure, the type, scope of use, usage scenarios, etc. of the personal information involved in this disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0026] For example, in response to a user's active request, a prompt message is sent to the user to clearly inform the user that the operation requested will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the electronic device, application, server, storage medium, or other software or hardware that performs the operations of the disclosed technical solution based on the prompt message.

[0027] As an optional but non-limiting implementation, in response to receiving a user's active request, the prompt information may be sent to the user in the form of a pop-up window, in which the prompt information may be presented in text form. Furthermore, the pop-up window may also contain a selection control for the user to select "agree" or "disagree" to provide personal information to the electronic device.

[0028] It is understandable that the above notification and user authorization process are merely illustrative and do not limit the implementation of the present disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of the present disclosure.

[0029] At the same time, it is understandable that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) must comply with the requirements of relevant laws, regulations and relevant provisions.

[0030] Figure 1 is a layered framework diagram of a business system according to an embodiment of the present disclosure. As shown in Figure 1, a typical business can be generally divided into a front-end code layer, a product requirement document (PRD) layer, an interface description language (IDL) method layer, an IDL structure layer, and a data layer. It should be noted that Figure 1 uses the order business as an example, and this disclosure does not limit the specific type of business.

[0031] Front-end code layer: This is the code that front-end developers actually come into contact with, and the part of the content that is presented to users after final processing. For example, the front-end code can be presented to users after being rendered using a rendering tool.

[0032] PRD layer: PRD is the product manager's (PM) description of each platform's requirements. It is written in accordance with standard documents and can be used to parse the information that the product wants to display.

[0033] IDL method layer: In order to distinguish requests from structures, this disclosure abstracts the content that is strongly related to methods into a layer to describe the interface actually used.

[0034] IDL structure layer: IDL is written by the server. The general file content is thrift. For general structures, it can be considered to represent different business meanings.

[0035] Data layer: The "data" in the data layer does not refer to the actual stored content, but rather to the description of the data structure. By parsing the library table information, the corresponding data structure can be obtained.

[0036] After obtaining the hierarchical structure shown in Figure 1, we actually obtain the content layer by layer and the association relationship between the content within each layer, for example, the association relationship between CreateOrder and CreateOrderRequest in the IDL method layer, and the association relationship between Order and OrderResponse, CreateOrRequest, etc. in the IDL structure layer.

[0037] In order to build the entire system, relationships between layers are also required, such as the relationship between Order in the IDL structure layer and table_order in the data layer. How to establish relationships between layers to build the entire system is the problem to be solved by this disclosure.

[0038] Figure 2 is a flow chart of an information flow method according to an embodiment of the present disclosure. As shown in Figure 2, the information flow method includes the following steps S21 to S24.

[0039] In step S21, the product requirement document is imported into the PRD layer, the IDL information is imported into the IDL method layer and the IDL structure layer, and the library table structure is imported into the data layer.

[0040] In step S22 , the data structure in the data layer is matched with the structure in the IDL structure layer by using the name of the structure in the IDL structure layer and the name of the field in the structure as keywords for searching, thereby obtaining a first matching result.

[0041] Taking the order business in Figure 1 as an example, by searching for "order" as a keyword, we can match table_order in the data layer with Order in the IDL structure layer, and table_order_production in the data layer with OrderProductItem in the IDL structure layer. The reason for matching the data layer data structure with the IDL structure layer structure first is that both the data structure and the IDL structure layer structure are designed by the server. Research has shown that in most scenarios, their designs are very similar, making it easy to quickly locate the correct association.

[0042] In step S23, the structure matched in the IDL structure layer is matched with the entity in the PRD layer by using the name of the structure matched in the first matching result and the name of the field in the structure as keywords for search, thereby obtaining a second matching result.

[0043] Taking the order business in Figure 1 as an example, by searching with "order" as the keyword, it is possible to match the "Order" entity in the IDL structure layer with the "Order" entity in the PRD layer.

[0044] In step S24, based on the first matching result and the second matching result, the primary key and unique key information in the data layer is transferred to the front-end code layer.

[0045] That is, through the matching operations in steps S22 and S23, the basic association relationships between the data in the data layer, the data in the IDL structure layer, and the data in the PRD layer are obtained. With the help of these association relationships, the primary key and unique key relationships in the data layer can be directly passed to the front-end code layer, so that the unique entry can be determined during subsequent page rendering operations, avoiding user input during creation.

[0046] By adopting the above technical solution, since the data structure in the data layer can be matched with the structure in the IDL structure layer according to the keyword, and the matched structure in the IDL structure layer can be matched with the entity in the PRD layer, and then the primary key and unique key information in the data layer can be passed to the front-end code layer based on the matching result, the global data can be automatically connected in series to build a relational model of the entire system, instead of only having the front-end independent view display drag and drop capability, and there is no need to manually confirm the correspondence between fields, which greatly reduces the overall R&D cost. Through the method disclosed in the present invention, a panoramic view of the entire system can be obtained, that is, the overall data map relationship and the associated information in the front-end and back-end interaction process of the business storage, which is very helpful for error diagnosis. Moreover, as an information integration tool, it can connect upstream and downstream systems, provide one-click page generation capabilities, support the data association information export and view connection of the content required by the front-end perspective, and at the application level, it can serve internal data information collection and association. In addition, it has strong scalability and can process the business incrementally. For example, every time a new entity is added, or an old system is old, the required part of the information can be directly entered for use without replacing it all. This solves the problem of only being able to improve the efficiency of front-end development but not being able to achieve overall efficiency improvement during development.

[0047] FIG3 is another flowchart of an information transfer method according to an embodiment of the present disclosure.

[0048] As shown in FIG3 , in step S31 , the product requirement document is imported into the PRD layer, the IDL information is imported into the IDL method layer and the IDL structure layer, and the library table structure is imported into the data layer.

[0049] In step S32, synonyms are entered and the keywords are unified into the same language. This step is optional.

[0050] By configuring synonyms, you can improve the accuracy of data association in subsequent matching steps. For example, "tomato," "tomato," "persimmon," and "tomato" can be considered the same word. In business scenarios, some words that are not directly related can have the same business meaning. For example, "agency," "agent," "supplier," and "partner" can be considered synonyms.

[0051] Furthermore, IDL information may be in English, while PRD content may be in Chinese. To improve the search and matching performance in subsequent matching steps, field names and structures can be translated to a common language, such as English or Chinese. The translated results can then be stored to improve matching accuracy during queries.

[0052] In step S33, the data structure in the data layer is matched with the structure in the IDL structure layer by using the name of the structure in the IDL structure layer and the names of the fields in the structure as keywords to obtain a first matching result. The implementation of this step has been described above and will not be repeated here.

[0053] In step S34, the structure matched in the IDL structure layer is matched with the entity in the PRD layer by using the name of the structure matched in the first matching result and the name of the field in the structure as a keyword search to obtain a second matching result. The implementation of this step has been described above and will not be repeated here.

[0054] In step S35, based on the first and second matching results, the primary key and unique key information in the data layer are transferred to the front-end code layer. The implementation of this step has been described above and will not be repeated here.

[0055] In step S36, the foreign keys are marked according to the reference relationship in the IDL structure layer.

[0056] Since the matching process in steps S33 and S34 may have strict restrictions on type processing, for example, the int type in the data layer can only match the i32Keyword type in the IDL structure layer, which may result in the loss of some complex type relationships. However, step S36 can mark these complex type relationships. For example, for the i32order_id row field, step S36 can determine that this field is not just a simple ID field, but is associated with the order_id primary key from the Order, thereby establishing an association.

[0057] In step S37 , the action type of the method in the IDL method layer is determined.

[0058] Methods in the IDL layer operate on specific entities. Method names generally follow the following pattern: [action][entity][unit], with [action] usually placed first. This feature allows you to identify and label the action type (i.e., the data operation performed by the method) of methods in the IDL method layer. For example, the GetSuppilerList method retrieves a list of suppliers, while the DeleteUserRecord method deletes specific records.

[0059] In step S38, the paging fields are marked according to the action type.

[0060] In addition to the relationships between primary fields, it's also important to focus on the relationships between key functional fields. For example, for paging fields, you can search for subfields in the request body marked as a query list that contain paging-related keywords. This allows you to understand how to manage paging operations during the request process and automate this process in front-end component development.

[0061] In step S39, the entity associated with the method is determined according to the action type, that is, the entity affected by the method in the IDL method layer is found.

[0062] Since the action type of the method has been known in step S37, different action types will have different features. For example, the return value of the method for obtaining a list includes list <entity>, where Entity is the entity affected by this method. Additionally, features such as keywords in the method name can be used as parameters to assist in inferring the entities affected by the method. Step S39 determines which entities, among the entities matched in step S34, are affected by the method in the IDL method layer.

[0063] In step S40, based on the association relationship between the method and its associated entity, the information lost during the data transfer process is supplemented in the IDL method layer and the IDL structure layer. This step can also be called type diffusion.

[0064] During the data flow, it is very likely that some information will be lost. For example, the timestamp field in the data layer is of type timestamp, which can be directly identified as a timestamp type, and it is very clear how to format and display it. However, in the IDL method layer and the IDL structure layer, the thrift structure type is used, and there is no timestamp type in the thrift structure type, so the timestamp information will be lost. Therefore, in step S40, based on the association relationship between the method and its associated entity, this part of the data in the data layer can be passed up to the IDL method layer and the IDL structure layer, so that this part of the data can be supplemented in the IDL method layer and the IDL structure layer.

[0065] In step S41 , based on the association relationship between the method and its associated entity, the entity is associated with the request body and its derivatives in the PRD layer.

[0066] For PM, the query and creation of the same field are consistent under the screening conditions and creation conditions, but they are often different fields in implementation. For example, when creating, only one Name is allowed to be filled in, while when querying, multiple-selection queries are supported. Therefore, a new round of matching operations is required for the query body in order to associate it with the configuration in the PRD layer. The front end can reuse some of the checks and configurations made when creating the form. Since the method in the IDL method layer links the entity affected by the method and the specific request structure in the middle, that is, the method acts as a bridge between the entity it affects and the specific request structure, so through step S41, the association relationship between the entity and the request body can be established.

[0067] By adopting the above technical solution, it is possible to automatically connect all global data in series to build a relational model for the entire system, instead of only having the front-end independent view display and dragging capabilities, and there is no need to manually confirm the correspondence between fields, which greatly reduces the overall R&D cost. Through the method disclosed in the present invention, it is possible to obtain a complete panoramic view describing the system, that is, the overall data map relationship and the associated information in the front-end and back-end interaction process of the business storage, which is of great help for error diagnosis; as an information integration tool, it can link upstream and downstream systems, provide one-click page generation capabilities, support the export of data association information and view concatenation of content required by the front-end perspective, and at the application level, it can serve internal data information collection and association. In addition, it has strong scalability and can process business incrementally. For example, every time a new entity is added, or an old system is added, part of the required information can be directly entered for use without replacing all of it.

[0068] FIG4 is a schematic block diagram of an information flow device according to an embodiment of the present disclosure. As shown in FIG4 , the information flow device includes: an import module 41 for importing PRD into the PRD layer, importing IDL information into the IDL method layer and the IDL structure layer, and importing the library table structure into the data layer; a first matching module 42 for matching the data structure in the data layer with the structure in the IDL structure layer by using the name of the structure in the IDL structure layer and the name of the field in the structure as keywords to obtain a first matching result; a second matching module 43 for matching the structure in the IDL structure layer with the entity in the PRD layer by using the name of the structure matched in the first matching result and the name of the field in the structure as keywords to obtain a second matching result; and a transfer module 44 for transferring the primary key and unique key information in the data layer to the front-end code layer based on the first matching result and the second matching result.

[0069] By adopting the above technical solution, since the data structure in the data layer can be matched with the structure in the IDL structure layer according to the keyword, and the matched structure in the IDL structure layer can be matched with the entity in the PRD layer, and then the primary key and unique key information in the data layer can be passed to the front-end code layer based on the matching result, the global data can be automatically connected in series to build a relational model of the entire system, instead of only having the front-end independent view display drag and drop capability, and there is no need to manually confirm the correspondence between fields, which greatly reduces the overall R&D cost. Through the method disclosed in the present invention, a panoramic view of the entire system can be obtained, that is, the overall data map relationship and the associated information in the front-end and back-end interaction process of the business storage, which is very helpful for error diagnosis; as an information integration tool, it can connect upstream and downstream systems, provide one-click page generation capabilities, support the data association information export and view connection of the content required by the front-end perspective, and at the application level, it can serve internal data information collection and association. In addition, it has strong scalability and can process business incrementally. For example, every time a new entity is added, or an old system is old, the required part of the information can be directly entered for use without replacing it all.

[0070] Figure 5 is another schematic block diagram of an information flow device according to an embodiment of the present disclosure. As shown in Figure 5, the information flow device further includes a foreign key marking module 45 for marking foreign keys according to the reference relationship in the interface description language structure layer.

[0071] As shown in FIG5 , the information flow device further includes an action type determination module 46 for determining the action type of the method in the interface description language method layer.

[0072] As shown in FIG5 , the information flow device further includes a page marking module 47 for marking the page fields according to the action type.

[0073] As shown in FIG5 , the information flow device further includes a first determining module 48 for determining, according to the action type, an entity associated with the method among the entities.

[0074] As shown in FIG5 , the information flow device further includes a supplement module 49 for supplementing information lost during data flow in the interface description language method layer and the interface description language structure layer based on the association relationship between the method and its associated entity.

[0075] As shown in FIG5 , the information flow device further includes an association module 50 for associating the entity with the request body and its derivatives in the product requirement document layer based on the association relationship between the method and the entity associated with it.

[0076] As shown in FIG5 , the information flow device further includes a pre-processing module 51 for inputting synonyms and unifying the keywords into the same language before performing the matching operation.

[0077] The specific implementation of the operations performed by each module in the information flow device of the present disclosure has been described in detail in the relevant methods and will not be repeated here.

[0078] The present disclosure also provides a computer-readable medium having a computer program stored thereon, which implements the steps of any method in the present disclosure when the program is executed by a processing device.

[0079] The present disclosure further provides an electronic device, comprising: a storage device on which a computer program is stored; and a processing device for executing the computer program in the storage device to implement the steps of any method in the present disclosure.

[0080] Reference is now made to FIG6 , which illustrates a schematic diagram of the structure of an electronic device 600 suitable for implementing embodiments of the present disclosure. Terminal devices in embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, personal digital assistants (PDAs), tablet computers (PADs), portable multimedia players (PMPs), vehicle-mounted terminals (e.g., vehicle-mounted navigation terminals), and fixed terminals such as digital televisions (TVs) and desktop computers. The electronic device illustrated in FIG6 is merely an example and should not limit the functionality and scope of use of embodiments of the present disclosure.

[0081] As shown in Figure 6, the electronic device 600 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage device 608 into a random access memory (RAM) 603. Various programs and data required for the operation of the electronic device 600 are also stored in the RAM 603. The processing device 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0082] Typically, the following devices may be connected to the I / O interface 605: an input device 606 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 607 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 608 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 609. The communication device 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. Although FIG. 6 shows the electronic device 600 with various devices, it should be understood that not all of the devices shown are required to be implemented or present. More or fewer devices may alternatively be implemented or present.

[0083] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication device 609, or installed from the storage device 608, or installed from the ROM 602. When the computer program is executed by the processing device 601, the above-mentioned functions defined in the method of the embodiment of the present disclosure are performed.

[0084] It should be noted that the computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or component, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, device, or component. In the present disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any suitable medium, including but not limited to wires, optical cables, RF (radio frequency), etc., or any suitable combination thereof.

[0085] In some embodiments, the client and server can communicate using any currently known or later developed network protocol, such as HTTP (HyperText Transfer Protocol), and can be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or later developed network.

[0086] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0087] The above-mentioned computer-readable medium carries one or more programs. When the above-mentioned one or more programs are executed by the electronic device, the electronic device: imports the product requirement document into the product requirement document layer, imports the interface description language information into the interface description language method layer and the interface description language structure layer, and imports the library table structure into the data layer; searches by using the name of the structure in the interface description language structure layer and the name of the field in the structure as keywords, matches the data structure in the data layer with the structure in the interface description language structure layer, and obtains a first matching result; searches by using the name of the structure matched in the first matching result and the name of the field in the structure as keywords, matches the structure matched in the interface description language structure layer with the entity in the product requirement document layer, and obtains a second matching result; and based on the first matching result and the second matching result, passes the primary key and unique key information in the data layer to the front-end code layer.

[0088] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages, or a combination thereof, including, but not limited to, object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on the remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0089] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or a part of code, and the module, program segment, or a part of code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of the boxes in the block diagram and / or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0090] The modules described in the embodiments of this disclosure may be implemented via software or hardware. In some cases, the name of a module does not necessarily define the module itself. For example, an import module may be described as "a module for importing product requirement documents into the product requirement document layer, importing interface description language information into the interface description language method layer and interface description language structure layer, and importing library table structures into the data layer."

[0091] The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, and without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chip (SOCs), complex programmable logic devices (CPLDs), and the like.

[0092] In the context of the present disclosure, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in conjunction with an instruction execution system, device or equipment. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium can include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0093] According to one or more embodiments of the present disclosure, Example 1 provides an information flow method, including: importing a product requirement document into a product requirement document layer, importing interface description language information into an interface description language method layer and an interface description language structure layer, and importing a library table structure into a data layer; searching by using the name of the structure in the interface description language structure layer and the name of the field in the structure as keywords, matching the data structure in the data layer with the structure in the interface description language structure layer to obtain a first matching result; searching by using the name of the structure matched in the first matching result and the name of the field in the structure as keywords, matching the structure matched in the interface description language structure layer with the entity in the product requirement document layer to obtain a second matching result; and based on the first matching result and the second matching result, passing the primary key and unique key information in the data layer to the front-end code layer.

[0094] According to one or more embodiments of the present disclosure, Example 2 provides the method of Example 1, wherein the method further comprises: marking the foreign key according to the reference relationship in the interface description language structure layer.

[0095] According to one or more embodiments of the present disclosure, Example 3 provides the method of Example 1, wherein the method further comprises: determining an action type of the method in the interface description language method layer.

[0096] According to one or more embodiments of the present disclosure, Example 4 provides the method of Example 3, wherein the method further includes: marking a paging field according to the action type.

[0097] According to one or more embodiments of the present disclosure, Example 5 provides the method of Example 1, wherein the method further includes: determining, based on the action type, an entity among the entities that is associated with the method.

[0098] According to one or more embodiments of the present disclosure, Example 6 provides the method of Example 5, wherein the method further includes: based on the association relationship between the method and its associated entity, supplementing information lost during data flow in the interface description language method layer and the interface description language structure layer.

[0099] According to one or more embodiments of the present disclosure, Example 7 provides the method of Example 5, wherein the method further includes: based on the association relationship between the method and the entity associated with it, associating the entity with the request body and its derivatives in the product requirement document layer.

[0100] According to one or more embodiments of the present disclosure, Example 8 provides the method of any one of Examples 1 to 7, wherein the method further includes: before performing the matching operation, entering synonyms and unifying the keywords into the same language.

[0101] According to one or more embodiments of the present disclosure, Example 9 provides an information flow device, including: an import module, used to import a product requirement document into a product requirement document layer, import interface description language information into an interface description language method layer and an interface description language structure layer, and import a library table structure into a data layer; a first matching module, used to search by using the name of the structure in the interface description language structure layer and the name of the field in the structure as keywords, and match the data structure in the data layer with the structure in the interface description language structure layer to obtain a first matching result; a second matching module, used to search by using the name of the structure matched in the first matching result and the name of the field in the structure as keywords, and match the structure matched in the interface description language structure layer with the entity in the product requirement document layer to obtain a second matching result; and a transfer module, used to transfer the primary key and unique key information in the data layer to the front-end code layer based on the first matching result and the second matching result.

[0102] According to one or more embodiments of the present disclosure, Example 10 provides a computer-readable medium having a computer program stored thereon, which implements the steps of the method described in any one of Examples 1-8 when executed by a processing device.

[0103] According to one or more embodiments of the present disclosure, Example 11 provides an electronic device, comprising: a storage device on which a computer program is stored; and a processing device for executing the computer program in the storage device to implement the steps of any one of the methods described in Examples 1-8.

[0104] The above description is merely a preferred embodiment of the present disclosure and an illustration of the technical principles employed. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by the specific combination of the above-mentioned technical features, but also includes other technical solutions formed by any combination of the above-mentioned technical features or their equivalents without departing from the above-mentioned disclosed concepts. For example, a technical solution formed by replacing the above-mentioned features with (but not limited to) technical features with similar functions disclosed in this disclosure.

[0105] In addition, although each operation is described in a specific order, this should not be understood as requiring these operations to be performed in the specific order shown or in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although some specific implementation details have been included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Some features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination mode.

[0106] Although the subject matter has been described using language specific to structural features and / or methodological logical acts, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are merely example forms of implementing the claims. Regarding the apparatus in the above-described embodiments, the specific manner in which each module performs operations has been described in detail in the embodiments related to the method and will not be elaborated upon here.< / entity>

Claims

1. An information circulation method, comprising: Import the product requirement document into the product requirement document layer, import the interface description language information into the interface description language method layer and the interface description language structure layer, and import the library table structure into the data layer; By using the name of the structure in the interface description language structure layer and the name of the field in the structure as keywords for searching, the data structure in the data layer is matched with the structure in the interface description language structure layer to obtain a first matching result; By using the name of the structure matched in the first matching result and the name of the field in the structure as keywords for searching, the structure matched in the interface description language structure layer is matched with the entity in the product requirement document layer to obtain a second matching result; as well as Based on the first matching result and the second matching result, the primary key and unique key information in the data layer is transferred to the front-end code layer.

2. The method according to claim 1, further comprising: The foreign keys are marked according to the reference relationship in the interface description language structure layer.

3. The method according to claim 1 or 2, further comprising: The action type of the method in the interface description language method layer is determined.

4. The method according to claim 3, further comprising: Depending on the action type, the paging fields are marked.

5. The method according to claim 3 or 4, further comprising: According to the action type, an entity among the entities associated with the method is determined.

6. The method according to claim 5, further comprising: Based on the association relationship between the method and its associated entity, the information lost in the data flow process is supplemented in the interface description language method layer and the interface description language structure layer.

7. The method according to claim 5, further comprising: Based on the association relationship between the method and the entity associated with it, the entity is associated with the request body and its derivatives in the product requirement document layer.

8. The method according to any one of claims 1 to 7, further comprising: Before performing the matching operation, synonyms are entered and the keywords are unified into the same language.

9. An information flow device, comprising: The import module is used to import the product requirement document into the product requirement document layer, import the interface description language information into the interface description language method layer and the interface description language structure layer, and import the library table structure into the data layer; A first matching module is used to match the data structure in the data layer with the structure in the interface description language structure layer by using the name of the structure in the interface description language structure layer and the name of the field in the structure as keywords to obtain a first matching result; A second matching module is used to match the structure matched in the interface description language structure layer with the entity in the product requirement document layer by using the name of the structure matched in the first matching result and the name of the field in the structure as keywords for searching, so as to obtain a second matching result; as well as A transfer module is used to transfer the primary key and unique key information in the data layer to the front-end code layer based on the first matching result and the second matching result.

10. A computer readable medium having a computer program stored thereon, wherein when the program is executed by a processing device, the steps of the method according to any one of claims 1 to 8 are implemented.

11. An electronic device, comprising: a storage device having a computer program stored thereon; A processing device, configured to execute the computer program in the storage device to implement the steps of the method according to any one of claims 1 to 8.

12. A computer program product having a computer program stored thereon, wherein when the program is executed by a processing device, the steps of the method according to any one of claims 1 to 8 are implemented.

13. A computer program, which, when executed by a processing device, implements the steps of the method according to any one of claims 1 to 8.

Images