Information query method and device, equipment, storage medium and program product
By receiving user query requests in the media storage platform, passing probe requests along the call chain, and splicing component information, the problem of low efficiency during testing is solved, enabling fast and accurate function configuration query and chain output, thus improving testing efficiency.
Patent Information
- Application Number
- CN202511757572.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-27
- Publication Date
- 2026-02-24
AI Technical Summary
During the functional testing of the media storage platform, testers need to review a large number of historical documents to obtain process and configuration information, which is inefficient and prone to component omissions or configuration errors, affecting testing efficiency.
An information query method is provided, which receives user query requests, passes probe requests along the call chain of the target functional characteristics, carries query trigger parameters and keyword parameters, obtains and concatenates component identifiers and configuration information, and outputs the call chain and configuration table.
It enables quick query functionality for configuration tables and call chains, saving test preparation time, avoiding missing components or configuration errors, and improving test efficiency.
Smart Images
Figure CN121560918A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of software testing technology, and in particular to an information retrieval method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Technology
[0002] To meet customer needs, the media storage console (also known as the media storage middle platform) interfaces with many functionalities of the underlying storage system. Some of these functionalities are logically complex, requiring the addition of edge components to implement their logic. Furthermore, given the numerous production storage resource pools, a pool-agent module is deployed for each resource pool to manage edge components uniformly and host edge component information. Requests from the media storage middle platform are first sent to the pool-agent, then forwarded to the corresponding edge component, which then interacts with the underlying storage system. This results in a relatively long call chain for each functionality, requiring interaction with at least four modules, each of which needs appropriate configuration to correctly forward requests and process logic.
[0003] Due to the numerous steps and complex configurations involved, testers often have to sift through a large number of historical documents to determine the exact steps and configuration information during the testing of functional features. This process is extremely inefficient. Furthermore, because each functional feature involves many modules and configurations, it is common for missing or incorrectly configured components to be found, which severely impacts testing efficiency. Summary of the Invention
[0004] Therefore, it is necessary to provide a method, apparatus, computer device, computer-readable storage medium, and computer program product that can support fast querying of information from the underlying functional configuration table and call chain of the storage layer, in response to the above-mentioned technical problems.
[0005] Firstly, this application provides an information retrieval method, including:
[0006] Receive a query request initiated by a user for a target functional feature; the query request carries query trigger parameters and keyword parameters;
[0007] Based on the query request, a corresponding probe request is initiated to the storage system; the probe request is configured to be passed along the call chain of the target functional characteristics, and carries the query trigger parameters and the keyword parameters;
[0008] Receive response information from the storage system; the response information is generated by one or more components in the call chain based on the query trigger parameters and the keyword parameters, and includes the component identifiers of one or more components and configuration information in each component that matches the keyword parameters; and
[0009] Based on the response information, the call chain and configuration information of the target functional feature are output.
[0010] In one embodiment, initiating a corresponding probe request to the storage system based on the query request includes:
[0011] If the query trigger parameter in the query request is a target value, a corresponding probe request is initiated to the storage system. The probe request carries the query trigger parameter and the keyword parameter, and the query trigger parameter in the probe request is a target value. The keyword parameter in the probe request is a keyword that is uniformly set for all configuration variables corresponding to the target functional feature during the solution design phase.
[0012] In one embodiment, the components in the call chain include an edge pool proxy and one or more edge function components, wherein the edge pool proxy is used to receive and forward the probe request to the corresponding edge function component;
[0013] The step of initiating a corresponding probe request to the storage system based on the query request includes:
[0014] If the query trigger parameter in the query request is a target value, the probe request is initiated to the edge pool proxy.
[0015] In one embodiment, the step of generating the response information includes:
[0016] When each component in the call chain receives the probe request, if it identifies that the value of the query trigger parameter is true, it performs the following operations:
[0017] Retrieve local configuration variables;
[0018] Filter out configuration variables and variable values whose names match the values of the keyword parameters from the local configuration variables;
[0019] Generate response information containing the component identifier, the selected configuration variables, and their values, and return the response information to the downstream component in the call chain. The downstream component is another functional component, an edge pool proxy, or a media storage platform.
[0020] In one embodiment, in receiving response information from the storage system, the response information of the upstream component in the call chain of the target functional feature is located before the response information of the downstream component.
[0021] The step of generating the response information further includes:
[0022] After generating response information containing the component identifier and the selected configuration variables and variable values, the component concatenates the response information received from the upstream component in the call chain with its own response information, and returns the concatenated response information to the downstream component in the call chain.
[0023] In one embodiment, receiving a query request initiated by a user regarding a target functional feature includes:
[0024] In response to a user's operation on a pre-set interface for requesting the complete chain, obtain the input parameter information for the query trigger parameters and keyword parameters;
[0025] Based on the operation of the interface and the input parameter information, a query request initiated by the user for the target functional characteristics is received.
[0026] Secondly, this application also provides an information query device, the device comprising:
[0027] The request receiving module is used to receive query requests initiated by users for target functional features; the query request carries query trigger parameters and keyword parameters;
[0028] The request forwarding module is used to initiate a corresponding probe request to the storage system based on the query request; the probe request is configured to be passed along the call chain of the target functional characteristics, and carries the query trigger parameters and the keyword parameters;
[0029] An information receiving module is used to receive response information from the storage system; the response information is generated by one or more components in the call chain based on the query trigger parameters and the keyword parameters, and includes component identifiers of one or more components and configuration information in each component that matches the keyword parameters; and
[0030] The information display module is used to output the call chain information and complete configuration information of the target functional characteristics based on the response information.
[0031] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the method of any of the above embodiments.
[0032] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the methods of any of the above embodiments.
[0033] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the methods of any of the above embodiments.
[0034] The aforementioned information query methods, devices, computer equipment, computer-readable storage media, and computer program products, when designing functional feature schemes, define keywords for all configuration variables of the functional feature. All components involved in the functional feature must support matching query trigger parameters and keyword parameters. Based on the request, when the component corresponding to the functional feature determines that the current matching parameter value is the target value, it returns the component name and the variable name and value matching the keyword parameter value. If the upstream provides a returned component name and configuration variable table, these are concatenated and returned downstream in sequence. Finally, the middle platform can output the call chain and complete configuration table of the functional feature based on the request response. This method enables rapid querying of the functional configuration table and call chain without needing to search through documentation or consult relevant personnel, saving test preparation time. Furthermore, based on the configuration table and call chain corresponding to the functional feature, the test environment can be deployed quickly and accurately, avoiding test blocking caused by missing components or configuration errors, thus improving test efficiency. Attached Figure Description
[0035] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.
[0036] Figure 1 This is a diagram illustrating the application environment of an information query method in one embodiment.
[0037] Figure 2 This is a flowchart illustrating an information query method in one embodiment;
[0038] Figure 3 This is a flowchart illustrating the information query method for the bucket copy function in one embodiment;
[0039] Figure 4 This is a structural block diagram of an information query device in one embodiment;
[0040] Figure 5 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation
[0041] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.
[0042] It should be noted that the terms "first," "second," etc., used in this application can be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish the first element from the second element. The terms "comprising" and "having," and any variations thereof, used in this application, are intended to cover non-exclusive inclusion. The term "multiple" used in this application refers to two or more. The term "and / or" used in this application refers to one of the embodiments, or any combination of multiple embodiments.
[0043] A media storage platform provides users with a unified, user-friendly, and operable management interface, packaging complex underlying storage functions into simple and clear operations. Specifically, the media storage platform provides the underlying storage functionality and an interactive interface, allowing users (developers, operations personnel, or other customers) to use various underlying storage functions. For user operation requests through the interactive interface, the media storage platform converts them into one or more standard backend API requests and sends them to the backend. Furthermore, the media storage platform processes the data returned from the backend (such as operation success or failure, file lists, configuration information, etc.) and displays it to the user in an intuitive format such as charts, lists, or status prompts.
[0044] To meet customer needs, the media storage platform integrates with many functionalities of the underlying storage layer. Some of these functionalities are logically complex, requiring the addition of edge components to implement their logic. Furthermore, given the numerous production storage resource pools, a pool-agent module is deployed for each resource pool to manage edge components uniformly and host edge component information. Requests from the media storage platform are first sent to the pool-agent, then forwarded to the corresponding edge component, which then interacts with the underlying storage layer. This results in a relatively long call chain for each functionality, requiring interaction with at least four modules. Each module needs corresponding configuration (e.g., the media storage platform needs to know which pool-agent to send requests to, the pool-agent needs to know which edge component to send requests to, the edge component needs to know which underlying storage layer to send requests to, and the underlying storage layer's own tools and processes must be prepared) to correctly forward requests and process logic.
[0045] Due to the numerous steps and complex configurations involved, testers often have to sift through a large number of historical documents to determine the specific steps / modules and configuration information required for testing certain functionalities of the storage layer. This process is extremely inefficient. Furthermore, because each functionality involves many modules and configurations, missing or incorrectly configured components are frequently encountered, which severely impacts testing efficiency.
[0046] The information query method provided in this application embodiment can be applied to, for example... Figure 1 The application environment shown is as follows. The media storage platform can communicate with the storage system, which may include multiple storage resource pools. The media storage platform, acting as the system center and also known as the media storage console, has a global perspective, sets rules, and uniformly receives all requests. Each storage resource pool acts as the edge of the system; these pools are located far from the system center, at the end of the system topology. Edge components can be understood as functional modules deployed in these edge resource pools; they are deployed at the specific execution site to handle specific complex tasks.
[0047] The storage resource pool can be deployed on a web server. The media storage platform provides an interactive interface and receives user query requests. It transforms these requests into corresponding backend query requests and forwards them layer by layer to the edge components of the storage resource pool according to the corresponding links. Each edge component responds to the query request, returns its own configuration information, and concatenates it with the configuration information returned by other components in the link. Finally, the information is returned to the media storage platform and displayed to the user through the platform's interactive interface. This allows users to easily obtain the complete call chain and configuration information of a specific feature through a simple query request, improving the efficiency and accuracy of information retrieval.
[0048] The media storage platform can run on terminals, which can be, but are not limited to, various personal computers, laptops, smartphones, tablets, drones, low-altitude aircraft, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, and projection equipment. Portable wearable devices can include smartwatches, smart bracelets, and head-mounted displays. Head-mounted displays can be virtual reality (VR) devices, augmented reality (AR) devices, and smart glasses. The storage resource pool can be deployed on servers, which can be independent physical servers, server clusters or distributed systems composed of multiple physical servers, or cloud servers providing cloud computing services.
[0049] In one exemplary embodiment, such as Figure 2 As shown, an information retrieval method is provided, which can be applied to... Figure 1Taking the media storage platform as an example, the explanation includes the following steps 201 to 204. Among them:
[0050] Step 201: Receive a query request from the user regarding the target functional characteristics; the query request carries keyword parameters and query trigger parameters.
[0051] The media storage platform can provide users with corresponding interfaces to initiate query requests targeting specific functionalities. For example, this interface can be an operation option within the interactive interface or webpage provided by the media storage platform. This interface is used to request the complete query chain and supports input parameter operations for keyword parameters and query trigger parameters.
[0052] The query trigger parameter can be a preset parameter used to indicate the current request type. When the value of the query trigger parameter is a preset target value, the media storage platform can determine that the current request is a request that triggers the complete chain of querying the corresponding functional characteristics, and then forward the request to the backend to request the backend to return the corresponding response information.
[0053] For example, the query trigger parameter can be returnConf. When the media storage platform recognizes that returnConf=true in the currently received operation request, it can determine that the current request is a request to query the complete link and configuration information of the corresponding functional features, and then forward the query request to the backend storage system.
[0054] In one embodiment, the process of receiving a query request initiated by a user for a target functional feature includes: in response to the user's operation on a pre-set interface for requesting the complete link, obtaining input parameter information for the query trigger parameters and keyword parameters; and receiving the query request initiated by the user for the target functional feature based on the request operation and input parameter information of the interface.
[0055] Step 202: Based on the query request, initiate a corresponding probe request to the storage system; the probe request is configured to be passed along the call chain of the target functional characteristics, and carries the query trigger parameters and the keyword parameters.
[0056] The storage system can be a distributed storage system, which may include multiple edge components, which may be located on local storage devices or on the server side.
[0057] In this embodiment, the probe request can be understood as a query request. To distinguish it from the query requests received by the user from the media storage platform, it is referred to as a probe request. Similarly, the probe request carries query trigger parameters and keyword parameters, the values of which are the values input by the user based on the media storage platform parameters.
[0058] The probe request is configured to be passed along the call chain of the target functional feature. This can be understood as follows: after receiving the probe request, if any component in the call chain of the target functional feature identifies that the value of the query trigger parameter is the target value, it forwards the probe request to the next level target component. The target component is the component whose component name contains the value of the keyword parameter. In this way, the probe request is passed sequentially along the call chain of the target functional feature.
[0059] Step 203: Receive response information from the storage system; the response information is generated by one or more components in the call chain of the target functional feature based on the query trigger parameters and the keyword parameters, and includes the component identifiers of one or more components and the configuration information of each component that matches the keyword parameters.
[0060] In this scenario, with an edge pool agent (pool-agent) deployed in the resource pool of the storage system to manage edge component information, the media storage platform receives response information from the storage system through the edge pool agent.
[0061] In cases where the call chain of the target feature contains multiple components, the response information returned by the edge pool proxy may include the call hierarchy relationship of the multiple components, as well as the configuration information of the target feature in each component.
[0062] For example: the call chain of the target functional feature includes edge pool proxy – component A – component B. The probe request is passed sequentially along the edge pool proxy – component A – component B. The response information returned by the edge pool proxy can be {identifier and variable information of component B; identifier and variable information of component A; identifier and variable information of the edge pool proxy}. Through this response information, it can be reflected that the call chain of the target functional feature is edge pool proxy – component A – component B (or media storage platform – edge pool proxy – component A – component B, where component B is the upstream component of component A, component A is the downstream component of component B, component A is the upstream component of the edge pool proxy, and the edge pool proxy is the downstream component of component A).
[0063] Step 204: Based on the response information, output the call chain information and complete configuration information of the target functional characteristics.
[0064] In this embodiment, the media storage platform can directly output the response information of the edge pool proxy, allowing users to obtain the call chain information and configuration information of the target functional characteristics based on the edge pool proxy. In other embodiments, the media storage platform can also parse the response information of the edge pool proxy to output the call chain information and configuration information of the target functional characteristics to the user in a more intuitive way, such as outputting the call chain information and configuration information of the target functional characteristics in a table or graphical format.
[0065] It should be noted that a prerequisite for the information retrieval method in this application is that, when designing each functional feature scheme, the keyword for all configuration variables of that functional feature must be agreed upon. This uniformly set keyword can be at the beginning, end, or other position of the configuration variable name, as long as the unified keyword is included in the configuration variable name. Furthermore, to uniquely identify different functional features, different functional features correspond to different keywords.
[0066] Furthermore, another prerequisite for the information query method in this application is that all components involved in the functional features must support matching the aforementioned query trigger parameters and key (i.e., the aforementioned keyword parameters). That is, all components involved in the functional features can identify the type of request based on the query trigger parameters, and determine which information needs to be returned based on the keyword parameters, namely, the component name, the configuration variable name matching the key parameter value, and the variable value.
[0067] In the aforementioned information query method, when designing the functional feature scheme, keywords for all configuration variables of that functional feature are defined. All components involved in that functional feature must support matching query trigger parameters and keyword parameters. When a component involved in that functional feature determines that the parameter value of the query trigger parameter in the current request is the target value, it returns the component name and the variable name and value that match the keyword parameter value. If the upstream provides a returned component name and configuration variable table, these are concatenated and returned downstream in sequence. Finally, the middle platform can output the call chain and complete configuration table of that functional feature based on the request response. This method enables rapid querying of the functional configuration table and call chain without needing to search through documentation or consult relevant personnel, saving test preparation time. Furthermore, based on the configuration table and call chain corresponding to the functional feature, the test environment can be deployed quickly and accurately, avoiding test blocking caused by missing components or configuration errors, and improving test efficiency.
[0068] In one embodiment, the aforementioned initiation of a corresponding probe request to the storage system based on the query request includes:
[0069] If the query trigger parameter in the query request is a target value, a corresponding probe request is initiated to the storage system. The probe request carries the query trigger parameter and the keyword parameter. The query trigger parameter in the probe request is a target value, and the keyword parameter in the probe request is a keyword that is uniformly set for all configuration variables corresponding to the target functional feature during the solution design phase.
[0070] For example, when the query trigger parameter in the query request is True, the media storage platform initiates a probe request to the edge pool proxy. This probe request is passed sequentially along the edge pool proxy – component A – component B. Correspondingly, the call chain reflecting the target functional characteristics is edge pool proxy – component A – component B. Upon receiving the probe request, if the component determines that the query trigger parameter carried in the request is the target value and that the next-level component name contains the value corresponding to the keyword parameter, it forwards the probe request to that next-level component name. Simultaneously, it also generates corresponding response information based on the received probe request. This response information includes its own component identifier and configuration information matching the keyword parameter.
[0071] It is understandable that the call chain levels may be different for different target functional characteristics. In other words, the length of the call chain may be different for different target functional characteristics. When the call chain is edge pool proxy - component A - component B, it can be understood that the call chain level of the target call chain is 3 levels.
[0072] Since the probe request carries the query trigger parameter and the keyword parameter, and all components involved in the functional feature need to support matching the query trigger parameter and keyword parameter, the user only needs to issue a simple query request in the middle platform, and the request can be automatically transmitted on the call chain of the target functional feature, thereby collecting the complete call chain and complete configuration information of the target functional feature, avoiding information omissions or errors.
[0073] In one embodiment, the components in the call chain include an edge pool proxy and one or more edge function components. The edge pool proxy is used to receive and forward the probe request to the corresponding edge function component. The aforementioned initiation of a corresponding probe request to the storage system based on the query request may include:
[0074] If the query trigger parameter in the query request is the target value, the middle platform initiates a probe request to the edge pool proxy. Upon receiving the probe request, each component in the call chain for the target feature, if it matches the query trigger parameter as true, performs the following operations:
[0075] Obtain local configuration variables; filter out configuration variables and variable values whose names match the values of the keyword parameters from the local configuration variables; generate response information containing the identifier of this component and the filtered configuration variables and variable values, and return the response information to the downstream component in the call chain, wherein the downstream component is other functional components, edge pool proxy or media storage platform.
[0076] In another embodiment, in the response information received by the middle platform, the response information of the upstream component in the call chain of the target functional feature is located before the response information of the downstream component; correspondingly, the response information generation step may include:
[0077] A component in the call chain for the target functional characteristics, after generating response information containing its own identifier and the selected configuration variables and variable values, concatenates the response information received from the upstream component in the call chain with its own response information, so that the upstream component's response information is placed before its own response information, and returns the concatenated response information to the downstream component in the call chain.
[0078] In other embodiments, the response information of the upstream component in the call chain of the target functional feature can also be located after the response information of the downstream component. As long as the information splicing method of each component in the entire call chain remains consistent, the call chain information of the target functional feature can be reflected.
[0079] By using this method of concatenating response information, more accurate call chain information can be obtained, avoiding confusion between the call chain information and configuration information when the call chain of functional features is complex, which would affect testing efficiency.
[0080] The following is for reference. Figure 3 Taking bucket replication as an example, the information query method of the above embodiments of this application will be further explained.
[0081] For the bucket copy feature, first set the keyword of all configuration variables for the bucket copy feature to "copy" in all components. Optionally, the configuration variable names for all components involved in the bucket copy feature should begin with "copy".
[0082] Under this premise, the information query method for the bucket replication function includes the following steps:
[0083] 1. The user requests the bucket copy function interface in the media storage platform and inputs the parameters returnConf=true,key=copy.
[0084] 2. After receiving a user's query request, the media storage platform forwards the request to the pool-agent. After receiving the request, the pool-agent forwards the request to the edge component copy (an edge component of the bucket replication function) and inputs the parameters returnConf=true, key=copy.
[0085] 3. After receiving the request, the edge component copy forwards the request to rgw (another edge component for bucket copying), with the input parameters returnConf=true and key=copy.
[0086] 4. After receiving the request, rgw checks the request parameter returnConf=true&key=copy, and returns its own component name and configuration variable names and values that start with copy. The specific format can be modules:[{module:rgw,conf:{copyRgwConf:...}}]; rgw returns this response information to its downstream edge component copy.
[0087] 5. After receiving the response from the upstream component rgw, the edge component copy returns its own component name and configuration variable names and values that begin with copy. At the same time, it concatenates the response information returned by the upstream component rgw. Based on this, the final response information obtained by the edge component copy is modules:[{module:rgw,conf:{copyRgwConf:...}}, {module:copy,conf:{copyCopyConf:...}}].
[0088] The edge component copy then returns this response information to its downstream component pool-agent.
[0089] 6. After receiving the response information from the upstream edge component copy, pool-agent returns its own component name and configuration variable names and values that begin with copy, along with the response information returned by the upstream edge component copy. Based on this, the specific response information obtained is as follows:
[0090] modules:[{module:rgw,conf:{copyRgwConf:...}},{module:copy,conf:{copyCopyConf:...}},{module:poolagent,conf:{copyPoolAgentConf:...}}].
[0091] Afterwards, pool-agent returns the response information to the middleware platform.
[0092] 7. The middle platform outputs the call chain and complete configuration table of the bucket replication function based on the request and response information of pool-agent. The complete chain of the bucket replication function is: middle platform --> pool-agent --> edge component copy --> rgw. Here, rgw can be understood as the upstream component.
[0093] It should be noted that in other embodiments, the edge component of the target functional characteristic can also generate its own response information after receiving the probe request, and then splice it after its upstream component returns the response information. It does not necessarily have to wait for its upstream component to return the response information before generating its own response information and splicing it, thereby improving the efficiency of returning response information.
[0094] The information query method in this application embodiment defines the keywords for all configuration variables of a functional feature when designing the feature scheme. For example, if the functional feature is bucket replication, the keyword for all configuration variables of bucket replication in each component can be set to "copy". Furthermore, all components involved in the functional feature must support matching parameters (i.e., query trigger parameters) and keys (i.e., keyword parameters). Under this premise, the component corresponding to the functional feature, based on the request, determines that the current matching parameter value is true, and returns the component name and the configuration variable name and value matching the key parameter value. If the previous level of the request returned the component name and configuration variable table, these are concatenated and returned to the next level in sequence. Finally, the middle platform can output the call chain and complete configuration table of the functional feature based on the request response. This method enables rapid querying of the functional configuration table and call chain without needing to search through documentation or consult relevant personnel, saving test preparation time. Furthermore, based on the configuration table and call chain corresponding to the functional feature, the test environment can be deployed quickly and accurately, avoiding test blocking caused by missing components or configuration errors, and improving test efficiency.
[0095] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps. It is understood that the steps in different embodiments can be freely combined as needed, and all non-contradictory solutions formed by such combinations are within the scope of protection of this application.
[0096] Based on the same inventive concept, this application also provides an information query device for implementing the information query method described above. The solution provided by this device is similar to the solution described in the above method; therefore, the specific limitations in one or more information query device embodiments provided below can be found in the limitations of the information query method described above, and will not be repeated here.
[0097] In one exemplary embodiment, such as Figure 4 As shown, an information query device is provided, comprising:
[0098] The request receiving module 401 is used to receive a query request initiated by a user for a target functional feature; the query request carries query trigger parameters and keyword parameters.
[0099] The request forwarding module 402 is used to initiate a corresponding probe request to the storage system based on the query request; the probe request is configured to be passed along the call chain of the target functional characteristics and carries the query trigger parameters and the keyword parameters;
[0100] Information receiving module 403 is used to receive response information from the storage system; the response information is generated by one or more components in the call chain based on the query trigger parameters and the keyword parameters, and includes component identifiers of one or more components and configuration information in each component that matches the keyword parameters; and
[0101] The information display module 404 is used to output the call chain information and complete configuration information of the target functional characteristics based on the response information.
[0102] In some embodiments, the request forwarding module 402 is specifically used to: when the query trigger parameter in the query request is a target value, initiate a corresponding probe request to the storage system; the probe request carries the query trigger parameter and the keyword parameter, and the query trigger parameter in the probe request is a target value, and the keyword parameter in the probe request is a keyword uniformly set for all configuration variables corresponding to the target functional characteristic during the scheme design stage.
[0103] In some embodiments, the components in the call chain include an edge pool proxy and one or more edge function components, wherein the edge pool proxy is used to receive and forward the probe request to the corresponding edge function component;
[0104] The request forwarding module 402 is specifically used to: initiate the probe request to the edge pool proxy when the query trigger parameter in the query request is a target value.
[0105] In some embodiments, the step of generating the response information includes:
[0106] When each component in the call chain receives the probe request, if it identifies that the value of the query trigger parameter is true, it performs the following operations:
[0107] Retrieve local configuration variables;
[0108] Filter out configuration variables and variable values whose names match the values of the keyword parameters from the local configuration variables;
[0109] Generate response information containing the component identifier, the selected configuration variables, and their values, and return the response information to the downstream component in the call chain. The downstream component is another functional component, an edge pool proxy, or a media storage platform.
[0110] In some embodiments, in receiving response information from the storage system, the response information of the upstream component in the call chain of the target functional feature precedes the response information of the downstream component.
[0111] The step of generating the response information further includes:
[0112] After generating response information containing the component identifier and the selected configuration variables and variable values, the component concatenates the response information received from the upstream component in the call chain with its own response information, and returns the concatenated response information to the downstream component in the call chain.
[0113] In some embodiments, the request receiving module 401 is specifically used for:
[0114] In response to a user's operation on a pre-set interface for requesting the complete link, the system obtains input parameter information for the query trigger parameters and keyword parameters; based on the interface operation and the input parameter information, the system receives a query request initiated by the user for the target functional characteristics.
[0115] Each module in the aforementioned information query device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.
[0116] In one exemplary embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 5As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, Near Field Communication (NFC), or other technologies. When the computer program is executed by the processor, it implements an information retrieval method. The display unit is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.
[0117] Those skilled in the art will understand that Figure 5 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.
[0118] In one exemplary embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the method of any of the above embodiments.
[0119] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of the method of any of the above embodiments.
[0120] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps of the method of any of the above embodiments.
[0121] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.
[0122] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.
[0123] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.
Claims
1. An information retrieval method, characterized in that, The method includes: Receive a query request initiated by a user for a target functional feature; the query request carries query trigger parameters and keyword parameters; Based on the query request, a corresponding probe request is initiated to the storage system; the probe request is configured to be passed along the call chain of the target functional characteristics, and carries the query trigger parameters and the keyword parameters; Receive response information from the storage system; the response information is generated by one or more components in the call chain based on the query trigger parameters and the keyword parameters, and includes the component identifiers of one or more components and configuration information in each component that matches the keyword parameters; and Based on the response information, the call chain and configuration information of the target functional feature are output.
2. The information query method as described in claim 1, characterized in that, The step of initiating a corresponding probe request to the storage system based on the query request includes: If the query trigger parameter in the query request is a target value, a corresponding probe request is initiated to the storage system. The probe request carries the query trigger parameter and the keyword parameter, and the query trigger parameter in the probe request is a target value. The keyword parameter in the probe request is a keyword that is uniformly set for all configuration variables corresponding to the target functional feature during the solution design phase.
3. The information query method as described in claim 1, characterized in that, The components in the call chain include an edge pool proxy and one or more edge function components. The edge pool proxy is used to receive and forward the probe request to the corresponding edge function component. The step of initiating a corresponding probe request to the storage system based on the query request includes: If the query trigger parameter in the query request is a target value, the probe request is initiated to the edge pool proxy.
4. The information query method as described in claim 1, characterized in that, The steps for generating the response information include: When each component in the call chain receives the probe request, if it identifies that the value of the query trigger parameter is the target value, it performs the following operations: Retrieve local configuration variables; Filter out configuration variables and variable values whose names match the values of the keyword parameters from the local configuration variables; Generate response information containing the component identifier, the selected configuration variables, and their values, and return the response information to the downstream component in the call chain. The downstream component is another functional component, an edge pool proxy, or a media storage platform.
5. The information query method as described in claim 4, characterized in that, In the response information received from the storage system, the response information of the upstream component in the call chain of the target functional feature is located before the response information of the downstream component; The step of generating the response information further includes: After generating response information containing the component identifier and the selected configuration variables and variable values, the component concatenates the response information received from the upstream component in the call chain with its own response information, and returns the concatenated response information to the downstream component in the call chain.
6. The information query method according to any one of claims 1-5, characterized in that, Receiving a query request initiated by a user regarding a target functional feature includes: In response to a user's operation on a pre-set interface for requesting the complete chain, obtain the input parameter information for the query trigger parameters and keyword parameters; Based on the operation of the interface and the input parameter information, a query request initiated by the user for the target functional characteristics is received.
7. An information query device, characterized in that, The device includes: The request receiving module is used to receive query requests initiated by users for target functional features; the query request carries query trigger parameters and keyword parameters; The request forwarding module is used to initiate a corresponding probe request to the storage system based on the query request; the probe request is configured to be passed along the call chain of the target functional characteristics, and carries the query trigger parameters and the keyword parameters; An information receiving module is used to receive response information from the storage system; the response information is generated by one or more components in the call chain based on the query trigger parameters and the keyword parameters, and includes component identifiers of one or more components and configuration information in each component that matches the keyword parameters; and The information display module is used to output the call chain and configuration information of the target functional characteristics based on the response information.
8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.
10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.