Information management method and device, equipment and medium

Abstract

The embodiment of the invention relates to an information management method and device, equipment and a medium, and the method comprises the steps: receiving an information display request, and obtaining at least one target field identifier corresponding to the information display request; generating a target query statement based on the target field identifier, and determining a target interface based on the target query statement and the plurality of interface metadata; the target interface is called to obtain a target information field corresponding to the target field identifier from a corresponding data source, and the number of the data source is at least one; and displaying the target information field. According to the embodiment of the invention, unified configuration, acquisition and display management of the information fields of different data sources is realized through the unique field identifier, the use cost of the information is greatly reduced, the management processes of the information fields are mutually independent and do not influence each other, and the information management isolation is improved.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and in particular to an information management method, apparatus, device and medium. Background Technology

[0002] For information platforms with complex data sources, information integration typically requires data users to interface with different data sources through coding or configuration. However, information from different data sources is difficult to manage uniformly, resulting in high information usage costs and poor management isolation. Summary of the Invention

[0003] To address the aforementioned technical problems, this disclosure provides an information management method, apparatus, device, and medium.

[0004] This disclosure provides an information management method, the method comprising:

[0005] Receive an information display request and obtain the target field identifier corresponding to the information display request, wherein the number of target field identifiers is at least one;

[0006] A target query statement is generated based on the target field identifier, and the target interface is determined based on the target query statement and multiple interface metadata.

[0007] The target interface is invoked to obtain the target information field corresponding to the target field identifier from the corresponding data source, wherein the number of data sources is at least one;

[0008] Display the target information field.

[0009] This disclosure also provides an information management device, the device comprising:

[0010] The identification module is used to receive an information display request and obtain the target field identifier corresponding to the information display request, wherein the number of the target field identifiers is at least one;

[0011] The interface module is used to generate a target query statement based on the target field identifier, and to determine the target interface based on the target query statement and multiple interface metadata.

[0012] The acquisition module is used to call the target interface to obtain the target information field corresponding to the target field identifier from the corresponding data source, wherein the number of the data source is at least one;

[0013] The display module is used to display the target information fields.

[0014] This disclosure also provides an electronic device, the electronic device comprising: a processor; a memory for storing executable instructions of the processor; the processor being configured to read the executable instructions from the memory and execute the instructions to implement the information management method provided in this disclosure.

[0015] This disclosure also provides a computer-readable storage medium storing a computer program for executing the information management method provided in this disclosure.

[0016] Compared with the prior art, the technical solution provided in this disclosure has the following advantages: The information management solution provided in this disclosure receives an information display request and obtains the target field identifier corresponding to the information display request, wherein the number of target field identifiers is at least one; generates a target query statement based on the target field identifier, and determines the target interface based on the target query statement and multiple interface metadata; calls the target interface to obtain the target information field corresponding to the target field identifier from the corresponding data source, wherein the number of data sources is at least one; and displays the target information field. By adopting the above technical solution, the query statement can be determined through the unique field identifier corresponding to the information field, and the interface where the corresponding information field is located can be determined based on the query statement and multiple interface metadata. Calling this interface to obtain the information field from the corresponding data source and displaying it achieves unified configuration, acquisition, and display management of information fields from different data sources through the unique field identifier, greatly reducing the cost of information use. Furthermore, the management processes of each information field are independent and do not affect each other, improving the isolation of information management. Attached Figure Description

[0017] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0018] Figure 1 A flowchart illustrating an information management method provided in an embodiment of this disclosure;

[0019] Figure 2 A schematic diagram of an information management platform provided in an embodiment of this disclosure;

[0020] Figure 3 A flowchart illustrating another information management method provided in this embodiment of the disclosure;

[0021] Figure 4 A schematic diagram illustrating an information display process provided in an embodiment of this disclosure;

[0022] Figure 5 This is a schematic diagram of the structure of an information management device provided in an embodiment of the present disclosure;

[0023] Figure 6 A schematic structural diagram of an electronic device provided in an embodiment of the present disclosure. Detailed Implementation

[0024] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

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

[0026] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.

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

[0028] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0029] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0030] In many information-related fields, such as e-commerce customer service, information is often stored in different data sources and maintained independently by different teams. Information integration typically requires data users to interface with different data providers (i.e., data sources) through coding. Data users can build an information display platform, including a front-end presentation layer and a back-end integration layer. The back-end integration layer is responsible for uniformly connecting to different data sources, extracting, transforming, and integrating data. The front-end presentation layer is responsible for obtaining directly displayable data from the back-end integration layer and rendering it on the page. To improve information access efficiency, the code for the front-end presentation layer and the back-end integration layer can be maintained and developed in parallel by multiple people, which can meet development efficiency requirements to some extent. However, since information access is entirely dependent on development, each new piece of information requires the joint intervention of front-end and back-end development and testing teams, resulting in significant manpower investment, high communication and integration costs, and overall low efficiency. Related technologies can achieve information access from different data sources through configuration operations, solving the problem of low information access efficiency. However, because information from different data sources cannot be managed uniformly, information management remains problematic, leading to high information usage costs and poor management isolation.

[0031] To address the aforementioned problems, this disclosure provides an information management method, which will be described below with reference to specific embodiments.

[0032] Figure 1 This is a flowchart illustrating an information management method provided in an embodiment of the present disclosure. The method can be executed by an information management device, which can be implemented using software and / or hardware, and is generally integrated into an electronic device. Figure 1 As shown, the method includes:

[0033] Step 101: Receive an information display request and obtain the target field identifier corresponding to the information display request, wherein the number of target field identifiers is at least one.

[0034] The information display request can be a request to display a page and the information fields within that page, and this request may include a page identifier. The target field identifier can be a field identifier of a target information field included in the target page of the information display request. An information field can represent information at the smallest granularity; for example, an information field can be an order number or a product name, etc. The field identifier can uniquely represent an information field. The field identifier can uniquely represent an information field. In this embodiment, a corresponding unique identifier can be constructed for each information field to obtain the corresponding field identifier. The field identifier can be constructed based on multiple pieces of information from the information field using multi-segment rules to obtain at least one target information field corresponding to the information display request, thus corresponding to at least one target field identifier.

[0035] The information management method of this disclosure can be applied to an information management platform, which can be a platform for configuring, acquiring, and displaying information from different data sources. The information management platform may include a field management platform, a data center, and a presentation layer. The field management platform can be used to record all supported information fields and the field identifier corresponding to each information field; the data center can be used to aggregate data interfaces from different data sources and provide interface configuration capabilities; the data center can be built based on a graph-based data query language; the presentation layer can be used to display information fields on a page. For example, Figure 2 This is a schematic diagram of an information management platform provided in an embodiment of the present disclosure, such as... Figure 2 As shown in the figure, the INFO key represents the field identifier. The information management platform in the figure may include the field management platform 201, the data center 202, and the presentation layer 203. The data center 202 can connect to the four data sources in the figure. The field management platform 201, the data center 202, and the presentation layer 203 can interact and link information based on the field identifier.

[0036] A data source includes multiple namespaces, which can refer to the services included in the data source. A namespace includes multiple interfaces, which can define the methods included in the services of the data source. An interface encapsulates multiple information fields, meaning that multiple information fields can be retrieved through a single interface. In this embodiment, the field identifier can be constructed by combining the interface path, namespace, and interface name.

[0037] Specifically, in response to a user's trigger operation to display a target page, the information management device can receive an information display request. Then, based on the page identifier in the information display request, it can determine the associated target field identifier by querying. Specifically, the target field identifier is the field identifier associated with the page identifier queried in the field management platform of the information display platform.

[0038] Step 102: Generate a target query statement based on the target field identifier, and determine the target interface based on the target query statement and multiple interface metadata.

[0039] The target query statement can conform to the query statement structure definition of the graph data query language. The data center is built based on the graph data query language, and this target query statement can be parsed and read by the data center. Since the information management platform's data center cannot read the information in the field identifiers, the field identifiers need to be converted into readable query statements. Interface metadata can be data describing an interface, which can be pre-configured and registered in the information display platform's data center based on the interface information provided by the data source. Because it connects to multiple interfaces from multiple data sources, the number of interface metadata entries is multiple. The target interface can be the specific interface in the data source corresponding to the target information field identified by the target field identifier. Different information fields can correspond to different interfaces, or multiple information fields can correspond to the same interface.

[0040] After the information management device determines the target field identifier, it can decompose the target field identifier through the data center to obtain the target query statement, and determine the corresponding target interface based on the target query statement and the matching results of multiple interface metadata.

[0041] For example, Figure 3 A flowchart illustrating another information management method provided in this disclosure embodiment is shown below. Figure 3 As shown, in some embodiments, generating a target query statement based on the target field identifier may include:

[0042] Step 301: Obtain the original input parameters bound to the target field identifier, and extract the target interface path, target namespace, and target interface name from the target field identifier.

[0043] The original input parameters can be the parameters required to retrieve the corresponding information field. Specifically, they can be obtained when constructing the field identifier of the information field and stored in association with that field identifier. These parameters can be stored in the aforementioned field management platform. The original input parameters can come from the data source where the information field resides; for example, they could be an order number or a logistics number. The interface path represents the management path of an information field within the corresponding interface. The information field can be retrieved through this interface path. For example, for {

[0044]

[0045]

[0046] The interface path for the "Department Store" information field can be `order_detail.product_detail.category.name`, which is just an example. The target interface path can be the interface path corresponding to the target information field. The namespace represents the specific service of an information field in the corresponding data source, and the target namespace can be the namespace corresponding to the target information field. The interface name represents the specific interface of an information field in the namespace of the corresponding data source, and the target interface name can be the interface name corresponding to the target information field. In the Remote Procedure Call (RPC) protocol, the namespace and interface name can be used to locate the unique interface to be called. In this embodiment, the combination of the namespace and interface name can be combined with the above interface path to obtain the field identifier. For example, the combination of the namespace and interface name can be used as the prefix of the interface path, and the field identifier can be represented as `#{namespace}_#{method}.interface path`.

[0047] When the information management device generates a target query statement based on the target field identifier through the data center, it can first obtain the original input parameters bound to the target field identifier from the field management platform, and then perform reverse parsing on the target field identifier to extract the target interface path, target namespace, and target interface name included therein.

[0048] Step 302: Construct the target query statement based on the original input parameters, target interface path, target namespace, target interface name, and the query statement structure definition of the graph data query language.

[0049] The information management device can construct the target query statement by filling the original input parameters, target interface path, target namespace, and target interface name into the response position of the query statement according to the query statement structure definition of the graphical data query language.

[0050] For example, when the query language for graph data is GraphQL, the target query statement can be represented as follows:

[0051]

[0052]

[0053] In the first line of the target query statement, `query` indicates that this is a query statement named `Get`. The parameter `request` following `Get` is the input parameter that the downstream data source interface depends on. In the second line, `namespace_method` is a prefix field we construct to create a unique structure for the inner field. The input parameter that this field depends on is brought in by the upper-level query statement, which is the namespace and interface name in the field identifier. The fields in the third to sixth lines are the target interface paths of the target field identifier, indicating the specific location of the information field in the structure. By breaking it down, we can see that the information in the second to sixth lines of the target query statement already exists in the target field identifier, while the `request` required in the first line will be dynamically passed in when the presentation layer calls the data center. The other two keywords, `query` and `Get`, can be regarded as fixed values. Therefore, the target query statement can be obtained by reversing the target field identifier.

[0054] In some embodiments, determining the target interface based on the target query statement and multiple interface metadata may include: reading the target namespace and target interface name in the target query statement; matching the target namespace and target interface name in multiple interface metadata, and determining the interface corresponding to the successfully matched target interface metadata as the target interface.

[0055] When the information management device determines the target interface by executing a target query statement and multiple interface metadata through the data center, it can read the target namespace and target interface name in the target query statement. For example, the target query statement mentioned above can be read in the prefix field of the second line. Then, the target namespace and target interface name can be matched with the namespace and interface name in each pre-registered interface metadata. If the namespace of an interface metadata is the same as the target namespace and the interface name is the same as the target interface name, then the interface metadata is the successfully matched target interface metadata, and the interface corresponding to the target interface metadata can be determined as the target interface.

[0056] Step 103: Call the target interface to obtain the target information field corresponding to the target field identifier from the corresponding data source, wherein there is at least one data source.

[0057] The data source can be used to store specific information fields. The number of data sources in this embodiment of the disclosure can be one or more. A data source includes multiple namespaces, a namespace includes multiple interfaces, and an interface encapsulates multiple information fields.

[0058] The information management device can call the target interface through the data center to obtain the interface response value corresponding to the target interface from the corresponding data source. The interface response value includes multiple information fields. Then, the target information field in the interface response value can be located according to the target field identifier and the target information field can be returned to the presentation layer.

[0059] In some embodiments, calling the target interface to obtain the target information field corresponding to the target field identifier from the corresponding data source may include: constructing target input parameters based on the original input parameters corresponding to the target field identifier and the input parameter information structure corresponding to the target interface; calling the target interface based on the target input parameters and obtaining the interface response value from the data source where the target interface is located; and extracting the target information field from the interface response value based on the target interface path in the target field identifier.

[0060] The input parameter information structure can be the specific information structure of the input parameters that an interface call depends on. It is a piece of information in the interface metadata, meaning that the input parameters are packaged in the form of an input parameter information structure. The target input parameter is the input parameter obtained after packaging the original input parameter corresponding to the target field identifier according to the input parameter information structure. The interface response value can be the return value obtained from calling an interface. This interface response value aggregates multiple information fields. The data structure of the interface response value is different for different interfaces. The interface path is the specific path of an information field in the interface response value. The corresponding information field can be located in the interface response value through the interface path.

[0061] When the information management device calls the target interface through the data center to obtain the target information field corresponding to the target field identifier from the corresponding data source, it can package the original input parameter corresponding to the target field identifier into the input parameter information structure in the interface metadata of the target interface to obtain the target input parameter. Then, it can call the target interface based on the target input parameter, obtain the interface response value from the data source where the target interface is located, and determine the specific position of the target information field in the interface response value through the target interface path in the target field identifier. The target information field can be extracted from the specific position and returned to the presentation layer.

[0062] Step 104: Display the target information fields.

[0063] The information management device can display target information fields through the presentation layer. Specifically, the target information field can be displayed at the placeholder preset position corresponding to the target field identifier on the target page corresponding to the information display request. The target page is the page corresponding to the aforementioned information display request. The placeholder preset position can be configured by the user of the target information field as a placeholder on the target page. The presentation layer first displays the target page and then displays the target information field at the placeholder preset position on the target page.

[0064] In the above solution, the information management platform can reverse-parse the multi-segment unique field identifier to obtain the query statement for the subsequent scale. Based on the query statement, it can determine the interface of the data source corresponding to the information field by matching it with the pre-registered interface metadata. Then, it calls the interface to obtain the target information field. By using the unique field identifier, it achieves unified acquisition and display management of information fields from different data sources, which improves information management efficiency. It simplifies and standardizes the information rendering process that originally relied on front-end coding, and achieves page rendering of information without front-end intervention. This greatly reduces the cost of using information and allows non-development personnel to quickly learn and easily place information on their desired pages.

[0065] The information management solution provided in this disclosure receives an information display request and obtains the target field identifier corresponding to the information display request, wherein the number of target field identifiers is at least one; generates a target query statement based on the target field identifier, and determines a target interface based on the target query statement and multiple interface metadata; calls the target interface to obtain the target information field corresponding to the target field identifier from the corresponding data source, wherein the number of data sources is at least one; and displays the target information field. By adopting the above technical solution, a query statement can be determined through the unique field identifier corresponding to the information field, and the interface where the corresponding information field is located can be determined based on the query statement and multiple interface metadata. Calling this interface to obtain and display the information field from the corresponding data source achieves unified configuration, acquisition, and display management of information fields from different data sources through the unique field identifier, greatly reducing the cost of information use. Furthermore, the management processes of each information field are independent and do not affect each other, improving the isolation of information management.

[0066] In some embodiments, the information management method provided in this disclosure may further include: for multiple information fields in multiple data sources, constructing a corresponding field identifier based on the interface path, namespace and interface name of each information field in its respective data source according to a multi-segment rule, wherein the field identifier is used to uniquely represent the corresponding information field.

[0067] This disclosure embodiment is not limited to the type of data source. For example, in an e-commerce scenario, the data source may include order data sources, logistics data sources, etc. The information management device can register fields through a field management platform. The specific process may include, for each information field in multiple data sources, obtaining the interface path, namespace, and interface name of the information field in its respective data source, and combining them according to a multi-segment rule. For example, the combination of namespace and interface name can be used as the prefix of the interface path, and the field identifier can be represented as #{namespace}_#interface name}.interface path to obtain the corresponding field identifier. Each information field constructs a corresponding field identifier, and the association between the information field and the field identifier is stored.

[0068] Optionally, the above field registration process may also include: obtaining relevant information for each information field through the field management platform and binding it with the corresponding field identifier, then storing the relevant information. This relevant information may include system information, business information, and a meaning description. System information may include the structure and type of the input parameters required to obtain the information field; business information may include the business to which the information field belongs, used for business isolation (e.g., business information may include domestic and international); and the meaning description explains the field identifier, assisting relevant personnel in better understanding the meaning of the information field and its identifier during configuration. When configuring the display of information fields, users can configure the corresponding field identifier as a placeholder in a preset position on a specific page to complete the configuration.

[0069] See Figure 2 The field management platform 201 stores the association between information fields and field identifiers, as well as related information bound to field identifiers, through a database storing field metadata. Field metadata can be a general term for information associated with or bound to an information field, and operations such as adding, deleting, and modifying can be performed through the field management module to manage the field metadata of information fields.

[0070] In some embodiments, the information management method provided in this disclosure may further include: obtaining multiple interface information from multiple data sources; parsing and determining multiple corresponding interface metadata based on the multiple interface information and storing them, wherein each interface metadata includes a namespace to which an interface belongs, an interface name, an input parameter information structure, and an output parameter information structure.

[0071] The interface information can be all interface-related information obtained from the data source, and the specific data structure is the data structure in the data source. The information management device can obtain multiple interface information from multiple data sources through the interface management module of the data center and register the interfaces. The interface registration process can include: parsing each interface information to determine the namespace and interface name of the corresponding interface, analyzing the corresponding input parameter information structure and output parameter information structure, combining them to obtain the corresponding interface metadata, and then determining the corresponding interface metadata for each interface and storing multiple interface metadata.

[0072] See Figure 2 Data Center 202 obtains interface information and registers interfaces through the inoculation management module. Then, it stores multiple interface metadata in the database of interface metadata storage. The parsing execution engine periodically pulls interface metadata from this database and stores it locally for later use.

[0073] In the above solution, field registration can be achieved through the field management platform of the information display platform, and interface registration can be achieved through the data center. During the information field access process, no code needs to be written, and it can be completed solely through configuration, thereby significantly improving the efficiency of information access.

[0074] The following example further illustrates the display process of information fields. For instance, Figure 4 This is a schematic diagram illustrating an information display process provided in an embodiment of the present disclosure, such as... Figure 4 As shown in the figure, it illustrates the situation in... Figure 2 The information display platform, through the linkage between its field management platform and data center, achieves the display of information fields on a single page via a series of calls within the presentation layer. Figure 2 The middle arrow indicates the registration process and the display process. The registration process includes the registration interface and registration fields.

[0075] See Figure 2 and Figure 4 The specific process includes:

[0076] 1. Registration Interface

[0077] Assuming the interface uses the Thrift protocol, it is defined as follows:

[0078]

[0079]

[0080] For the aforementioned interfaces, interface registration is performed through the interface management module of the data center. Specifically, the interface information is broken down, and its required input parameters, output parameters that can be provided, namespace and interface name are analyzed and stored in their respective data tables.

[0081] 2. Registration fields

[0082] Based on the interface registration, and using the information fields that the interface can return, register the information fields to be displayed through the field management platform. Taking DepartmentName as an example, the interface path of this information field can be represented by StaffDetailResp.Department.DepartmentName. Based on the multi-segment rule, an INFO key (i.e., field identifier) ​​will be generated here as: test.thrift.idl_GetStaffDetail.StaffDetailResp.Department.DepartmentName; the user then uses this INFO key as a placeholder to configure the expected position in the display layer to complete the configuration.

[0083] 3. Information Display Process

[0084] a. During the startup phase, the presentation layer first calls the field management platform to request the INFO key contained in this page, obtains the current INFO key and its preset placeholder position on the page, and collects the original input parameters associated with the INFO key. The INFO key and the original input parameters are then passed to the data center. In this example, the original input parameters should include the StaffID field.

[0085] b. After the data center obtains the INFO key, taking GraphQL query language as an example, it can first reverse-engineer the GraphQL query statement (i.e., the target query statement mentioned above), and hand it over to the execution engine to perform the operation of obtaining information fields. Based on the GraphQL query statement and multiple interface metadata, the execution engine determines the target interface bound to the information field. In this example, it is found that the GetStaffDetail interface in the test.thrift.idl space needs to be called. Based on the input parameter StaffDetailReq that GetStaffDetail depends on, it can be determined that the downstream interface depends on the StaffID field. Since the StaffID field is the original input parameter that has been passed by the presentation layer, it can be used directly.

[0086] c. After the data center's execution engine successfully calls the target interface, it obtains the interface response value. The INFO key indicates that the information field is located in the interface response value as StaffDetailResp.Department.DepartmentName. The data center retrieves the specific value of the information field from the corresponding position in the interface response value and then returns it to the presentation layer.

[0087] d. After the presentation layer obtains the specific value of the information field, it renders it to the specified position on the page, which is the placeholder preset position mentioned above.

[0088] To address the integration challenges of information fields in information display platforms dealing with numerous complex data sources, this solution builds a field-level information configuration integration scheme based on a developer-friendly pre-defined query language (e.g., a graph data query language). This solution provides a multi-segment unique identifier generation rule that uses namespaces and interface names as prefixes combined with field paths; a parsing scheme that reverse-parses pre-defined query language statements based on multi-segment unique identifiers; and a configuration scheme that retrieves information field values ​​based on a multi-segment unique identifier and a pre-defined query language execution engine.

[0089] This solution enables purely configuration-based operations for basic field integration, requiring no coding whatsoever. Even for more complex field integration, only a small amount of script code is needed, significantly reducing code maintenance. This solution simplifies and standardizes the field rendering process, which previously relied on front-end coding, enabling page rendering of fields without front-end intervention. This greatly reduces the cost of using information fields, allowing non-developers to quickly learn and easily deploy fields to their desired pages. With this solution, field integration can be fully parallelized. Whether configuring, validating, publishing, or decommissioning, each information field's process is independent and unaffected, maximizing information integration efficiency.

[0090] Figure 5 This is a schematic diagram of the structure of an information management device provided in an embodiment of this disclosure. The device can be implemented by software and / or hardware and is generally integrated into an electronic device. Figure 5 As shown, the device includes:

[0091] The identification module 501 is used to receive an information display request and obtain the target field identifier corresponding to the information display request, wherein the number of the target field identifiers is at least one;

[0092] Interface module 502 is used to generate a target query statement based on the target field identifier, and to determine the target interface based on the target query statement and multiple interface metadata.

[0093] The acquisition module 503 is used to call the target interface to obtain the target information field corresponding to the target field identifier from the corresponding data source, wherein the number of the data source is at least one;

[0094] Display module 504 is used to display the target information field.

[0095] Optionally, the identification module 501 is used for:

[0096] Based on the page identifier in the information display request, the associated target field identifier is determined by querying.

[0097] Optionally, the apparatus further includes a field registration module for:

[0098] For multiple information fields in multiple data sources, a corresponding field identifier is constructed based on the interface path, namespace, and interface name of each information field in its respective data source according to a multi-segment rule. The field identifier is used to uniquely represent the corresponding information field.

[0099] Optionally, a data source may include multiple namespaces, a namespace may include multiple interfaces, and an interface may encapsulate multiple information fields.

[0100] The interface path represents the management path of an information field in the corresponding interface, the namespace represents the specific service of an information field in the corresponding data source, and the interface name represents the specific interface of an information field in the namespace to which the corresponding data source belongs.

[0101] Optionally, interface module 502 includes a first unit for:

[0102] Obtain the original input parameters bound to the target field identifier, and extract the target interface path, target namespace, and target interface name from the target field identifier;

[0103] Based on the original input parameters, the target interface path, the target namespace, the target interface name, and the query statement structure definition of the graph data query language, the target query statement is constructed.

[0104] Optionally, interface module 502 includes a second unit for:

[0105] Read the target namespace and target interface name from the target query statement;

[0106] Based on the target namespace and the target interface name, the target interface is determined as the target interface by matching the target interface metadata of the multiple interfaces.

[0107] Optionally, module 503 is used for:

[0108] Based on the original input parameters corresponding to the target field identifier and the input parameter information structure corresponding to the target interface, construct the target input parameters;

[0109] Based on the target input parameters, the target interface is invoked, and the interface response value is obtained from the data source where the target interface is located.

[0110] The target information field is extracted from the interface response value based on the target interface path in the target field identifier.

[0111] Optionally, display module 504 is used for:

[0112] The target information field is displayed at the placeholder preset position corresponding to the target field identifier on the target page corresponding to the information display request.

[0113] Optionally, the device further includes an interface registration module for:

[0114] Retrieve information from multiple interfaces across multiple data sources;

[0115] Based on the parsing of the multiple interface information, the corresponding multiple interface metadata are determined and stored. Each interface metadata includes the namespace to which the interface belongs, the interface name, the input parameter information structure, and the output parameter information structure.

[0116] The information management device provided in this disclosure can execute the information management method provided in any embodiment of this disclosure, and has the corresponding functional modules and beneficial effects of executing the method.

[0117] This disclosure also provides a computer program product, including a computer program / instruction that, when executed by a processor, implements the information management method provided in any embodiment of this disclosure.

[0118] Figure 6 A schematic structural diagram of an electronic device provided in an embodiment of the present disclosure.

[0119] The following is a detailed reference. Figure 6 The diagram illustrates a structural schematic suitable for implementing the electronic device 600 in the embodiments of this disclosure. The electronic device 600 in the embodiments of this disclosure may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 6 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

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

[0121] Typically, the following devices can be connected to I / O interface 605: input devices 606 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 607 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 608 including, for example, magnetic tapes, hard disks, etc.; and communication devices 609. Communication device 609 allows electronic device 600 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 6 An electronic device 600 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0122] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 609, or installed from a storage device 608, or installed from a ROM 602. When the computer program is executed by the processing device 601, it performs the functions defined in the information management method of embodiments of this disclosure.

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

[0124] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0125] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0126] The aforementioned computer-readable medium carries one or more programs. When the aforementioned one or more programs are executed by the electronic device, the electronic device causes the electronic device to: receive an information display request and obtain a target field identifier corresponding to the information display request, wherein the number of target field identifiers is at least one; generate a target query statement based on the target field identifier and determine a target interface based on the target query statement and multiple interface metadata; call the target interface to obtain a target information field corresponding to the target field identifier from a corresponding data source, wherein the number of data sources is at least one; and display the target information field.

[0127] Computer program code for performing the operations of this disclosure can 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, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0128] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0129] The units described in the embodiments of this disclosure can be implemented in software or hardware. The names of the units are not, in some cases, intended to limit the specific unit.

[0130] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

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

[0132] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, users should be informed of the types, scope of use, and usage scenarios of the information involved in this disclosure in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0133] The above description is merely a preferred embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features disclosed in this disclosure that have similar functions.

[0134] Furthermore, while the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. In certain environments, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0135] Although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims.

Claims

1. An information management method, characterized in that, include: Receive an information display request and obtain the target field identifier corresponding to the information display request, wherein the number of target field identifiers is at least one; A target query statement is generated based on the target field identifier, and the target interface is determined based on the target query statement and multiple interface metadata. The target interface is invoked to obtain the target information field corresponding to the target field identifier from the corresponding data source, wherein the number of data sources is at least one; Display the target information field.

2. The method according to claim 1, characterized in that, The step of obtaining the field identifier corresponding to the information display request includes: Based on the page identifier in the information display request, the associated target field identifier is determined by querying.

3. The method according to claim 1, characterized in that, The method further includes: For multiple information fields in multiple data sources, a corresponding field identifier is constructed based on the interface path, namespace, and interface name of each information field in its respective data source according to a multi-segment rule. The field identifier is used to uniquely represent the corresponding information field.

4. The method according to claim 3, characterized in that, A data source includes multiple namespaces, a namespace includes multiple interfaces, and an interface encapsulates multiple information fields; The interface path represents the management path of an information field in the corresponding interface, the namespace represents the specific service of an information field in the corresponding data source, and the interface name represents the specific interface of an information field in the namespace to which the corresponding data source belongs.

5. The method according to claim 1, characterized in that, The step of generating the target query statement based on the target field identifier includes: Obtain the original input parameters bound to the target field identifier, and extract the target interface path, target namespace, and target interface name from the target field identifier; Based on the original input parameters, the target interface path, the target namespace, the target interface name, and the query statement structure definition of the graph data query language, the target query statement is constructed.

6. The method according to claim 1, characterized in that, The process of determining the target interface based on the target query statement and multiple interface metadata includes: Read the target namespace and target interface name from the target query statement; Based on the target namespace and the target interface name, the target interface is determined as the target interface by matching the target interface metadata of the multiple interfaces.

7. The method according to claim 1, characterized in that, The step of calling the target interface to obtain the target information field corresponding to the target field identifier from the corresponding data source includes: Based on the original input parameters corresponding to the target field identifier and the input parameter information structure corresponding to the target interface, construct the target input parameters; Based on the target input parameters, the target interface is invoked, and the interface response value is obtained from the data source where the target interface is located. The target information field is extracted from the interface response value based on the target interface path in the target field identifier.

8. The method according to claim 1, characterized in that, The fields for displaying the target information include: The target information field is displayed at the placeholder preset position corresponding to the target field identifier on the target page corresponding to the information display request.

9. The method according to claim 1, characterized in that, The method further includes: Retrieve information from multiple interfaces across multiple data sources; Based on the parsing of the multiple interface information, the corresponding multiple interface metadata are determined and stored. Each interface metadata includes the namespace to which the interface belongs, the interface name, the input parameter information structure, and the output parameter information structure.

10. An information management device, characterized in that, include: The identification module is used to receive an information display request and obtain the target field identifier corresponding to the information display request, wherein the number of the target field identifiers is at least one; The interface module is used to generate a target query statement based on the target field identifier, and to determine the target interface based on the target query statement and multiple interface metadata. The acquisition module is used to call the target interface to obtain the target information field corresponding to the target field identifier from the corresponding data source, wherein the number of the data source is at least one; The display module is used to display the target information fields.

11. An electronic device, characterized in that, The electronic device includes: processor; Memory used to store the processor's executable instructions; The processor is configured to read the executable instructions from the memory and execute the instructions to implement the information management method according to any one of claims 1-9.

12. A computer-readable storage medium, characterized in that, The storage medium stores a computer program for executing the information management method according to any one of claims 1-9.

Images