A data filtering method and device, electronic equipment and storage medium

Abstract

The application discloses a data filtering method and device, electronic equipment and storage medium. The method comprises the following steps: an interface consumer generates a transmission layer object query language segment according to a required multi-level target field, and sends the transmission layer object query language segment and a data query request to an interface provider; the interface provider acquires return data according to the data query request, and sends the return data and the transmission layer object query language segment to a syntax analysis filter; the syntax analysis filter splits the transmission layer object query language segment into multiple query fields, extracts target data matched with the query fields from the return data, and returns the target data to the interface consumer. By using the technical scheme, the interface consumer can quickly and efficiently receive return data matched with the required fields, thereby saving transmission bandwidth.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a data filtering method, apparatus, electronic device, and storage medium. Background Technology

[0002] In actual network transmission, the data fields returned by the backend interface are often larger than the frontend's requirements, resulting in unnecessary waste of resources.

[0003] Currently, GraphQL (Graph Query Language) is commonly used to filter fields in data returned by backend APIs. However, GraphQL syntax is complex, has a long learning curve, and its API request style does not conform to the RESTful (Representational State Transformation) style, making it difficult to optimize websites for search engines. Furthermore, GraphQL framework configuration is cumbersome; for projects already designed with a RESTful style, modifying them to use GraphQL is extremely difficult, essentially requiring a complete rewrite of the request APIs. Summary of the Invention

[0004] This invention provides a data filtering method, apparatus, electronic device, and storage medium that can ensure that the interface consumer receives return data that matches the required fields quickly and efficiently, thereby saving transmission bandwidth.

[0005] According to one aspect of the present invention, a data filtering method is provided, comprising:

[0006] The interface consumer generates a transport layer object query language segment based on the required multi-level target fields, and sends the transport layer object query language segment and the data query request to the interface provider;

[0007] The interface provider obtains the returned data according to the data query request, and sends the returned data and the transport layer object query language segment to the syntax parsing filter;

[0008] The syntax parsing filter splits the transport layer object query language segment into multiple query fields, extracts the target data that matches the query fields from the returned data, and returns the target data to the interface consumer.

[0009] According to another aspect of the present invention, a data filtering device is provided, comprising:

[0010] The query information sending module is used by the interface consumer to generate a transport layer object query language segment based on the required multi-level target fields, and send the transport layer object query language segment and the data query request to the interface provider.

[0011] The data providing module is used by the interface provider to obtain the returned data according to the data query request, and send the returned data and the transport layer object query language segment to the syntax parsing filter;

[0012] The data filtering module is used to split the transport layer object query language segment into multiple query fields using a syntax parsing filter, extract the target data that matches the query fields from the returned data, and return the target data to the interface consumer.

[0013] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0014] At least one processor; and

[0015] A memory communicatively connected to the at least one processor; wherein,

[0016] The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the data filtering method according to any embodiment of the present invention.

[0017] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement the data filtering method described in any embodiment of the present invention.

[0018] The technical solution of this invention involves the interface consumer generating a Transport Layer Object Query Language (TLO) segment based on field requirements. This TLO segment, along with the data query request, is sent to the interface provider. The interface provider then returns data based on the query request and sends the returned data, along with the TLO segment, to a syntax parsing filter. The parsing filter retrieves the query fields required by the interface consumer based on the TLO segment and filters the returned data accordingly. Data that meets the interface consumer's field requirements is then fed back to the interface consumer. This approach allows the interface consumer to quickly and efficiently receive returned data matching its required fields without altering the existing project interfaces, thus saving transmission bandwidth.

[0019] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 This is a flowchart of a data filtering method provided in Embodiment 1 of the present invention;

[0022] Figure 2 This is a flowchart of another data filtering method provided in Embodiment 2 of the present invention;

[0023] Figure 3 This is a schematic diagram of the structure of a data filtering device according to Embodiment 3 of the present invention;

[0024] Figure 4 This is a schematic diagram of the structure of an electronic device that implements the data filtering method of this invention. Detailed Implementation

[0025] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0026] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0027] Example 1

[0028] Figure 1This is a flowchart of a data filtering method provided in Embodiment 1 of the present invention. This embodiment is applicable to situations where an interface consumer requests data for a specified field from an interface provider, the interface provider sends the full data to a syntax parser for filtering, and the syntax parser feeds back the filtered data for the specified field to the interface consumer. This method can be executed by a data filtering device, which can be implemented in hardware and / or software and can be configured in a computer or processor with data processing capabilities. Figure 1 As shown, the method includes:

[0029] S110. The interface consumer generates a transport layer object query language segment based on the required multi-level target fields, and sends the transport layer object query language segment and data query request to the interface provider.

[0030] In actual interface network transmission, the interface consumer is generally a front-end interface, and the interface provider is generally a back-end interface. The interface consumer can send data access requests and other call information to the interface provider. After receiving the data access request, the interface provider can return the data matching the data access request to the interface consumer. However, the interface consumer and interface provider are not limited to front-end interfaces and back-end interfaces, but can also be other interfaces with data processing and exchange functions.

[0031] Among them, the Transport Layer Object Query Language is a language with a concise syntax that can represent the hierarchical relationship between multiple fields used in this invention. The Transport Layer Object Query Language segment is a segment generated by the interface consumer based on the required target fields and relying on the Transport Layer Object Query Language.

[0032] The data query request is a request sent by the interface consumer to the interface provider. The data query request may include the data requirements of the interface consumer. The interface provider can return data according to the data requirements of the interface consumer. However, the returned data is generally the full data packet. But through the data filtering method proposed in this invention, the full data packet can be filtered to select the data that matches the fields required by the interface consumer and return it to the interface consumer.

[0033] To enable sending data matching the required fields to the interface consumer, in this invention, the interface consumer sends its field requirements to the interface provider in the form of a Transport Layer Object Query Language (TLO) segment. After obtaining the return data required by the interface consumer, the interface provider sends the return data and the TLO segment together to the syntax parsing filter. The syntax parsing filter obtains the fields required by the interface consumer by parsing the TLO segment, filters the return data according to the fields required by the interface consumer, and finally sends the filtered return data to the interface consumer.

[0034] It is understandable that the multiple target fields required by the interface consumer can have a certain hierarchical relationship. For example, the target fields may include id, username, and name from the tags list. In this case, id, username, and tags are target fields at the same level, and name from the tags list is a next-level field of tags.

[0035] The transport layer object query language segment may include a first identifier for separating each target field and a second identifier for specifying the value of the target field.

[0036] Furthermore, the second identifier may include a colon and square brackets. The colon can be used to indicate the connection between the target field and the next level target field that matches it, and the square brackets can be used to fill in the next level target field of the target field. The second identifier supports multi-level nesting.

[0037] Continuing the previous example, the first identifier can be a comma, i.e., ",", and the second identifier can be in the form of ":[]", where the square brackets can be filled with field information. Specifically, in the process of generating Transport Layer Object Query Language (TLJ) segments, for target fields id, username, and tags at the same level, the first identifier can be used to separate them, in the form of "id, username, tags"; for tags with hierarchical relationships and name in the tags list, the second identifier can be used to connect them, in the form of "tags:[name]", and thus, the generated TTLJ segment can be "id, username, tags:[name]". Furthermore, if there is a next-level field A of name in the tags list in the target field, since the second identifier can be applied at multiple levels, ":[A]" can be added after name in the generated TTLJ segment, and the TTLJ segment can be "id, username, tags:[name:[A]]".

[0038] The advantage of this setup is that, compared to GraphQL in the prior art, the transport layer object query language proposed in this embodiment of the invention has a more concise syntax and can transmit the field requirements of the interface consumer without compromising the original interface style.

[0039] S120. The interface provider obtains the returned data according to the data query request, and sends the returned data and the transport layer object query language segment to the syntax parsing filter.

[0040] It is understood that in the embodiments described in this invention, the interface provider itself does not have a data filtering function. After the interface provider obtains the returned data according to the data query request sent by the interface consumer, since the returned data is full data, the returned data and the transport layer object query language segment can be sent together to the syntax parsing filter so that the syntax parsing filter can parse and obtain the query field, thereby filtering the returned data.

[0041] S130. The syntax parsing filter splits the transport layer object query language segment into multiple query fields, extracts the target data that matches the query fields from the returned data, and returns the target data to the interface consumer.

[0042] The query field is the field used by the syntax parsing filter to filter the returned data, and can also be equivalent to the target field specified by the interface consumer; the target data is the data after data filtering. The target data meets the field requirements of the interface consumer and can be directly returned to the interface consumer.

[0043] Optionally, when the interface consumer generates a transport layer object query language segment, a specific identifier can be added before the transport layer object query language segment. When the syntax parsing filter parses the specific identifier, it can accurately extract the transport layer object query language segment.

[0044] Furthermore, the parsing filter can perform multiple deidentification processes on the transport layer object query language segment to ultimately obtain a query field that does not contain the first identifier and does not contain the second identifier.

[0045] Continuing the previous example, for the transport layer object query language segment "id, username, tags:[name]", the parsing filter can first split the first identifier to obtain id, username, and tags:[name]. These three fields are then stored in a list. After storage, the list elements are traversed to check for the existence of the second identifier, i.e., ":[]". In this example, "tags:[name]" exists. The filter can then check if the first identifier still exists within the square brackets. If, as in this example, the first identifier does not exist, then "name" is also stored in the list. If the first identifier exists within the square brackets, then the content within the square brackets is processed to remove the first identifier before being stored in the list. It should also be noted that after storing "name" in the list, "name" can be identified as the name in the tags list through specific identifier information.

[0046] The technical solution of this invention involves the interface consumer generating a Transport Layer Object Query Language (TLO) segment based on field requirements. This TLO segment, along with the data query request, is sent to the interface provider. The interface provider then returns data based on the query request and sends the returned data, along with the TLO segment, to a syntax parsing filter. The parsing filter retrieves the query fields required by the interface consumer based on the TLO segment and filters the returned data accordingly. Data that meets the interface consumer's field requirements is then fed back to the interface consumer. This approach allows the interface consumer to quickly and efficiently receive returned data matching its required fields without altering the existing project interfaces, thus saving transmission bandwidth.

[0047] Example 2

[0048] Figure 2 This is a flowchart of a data filtering method provided in Embodiment 2 of the present invention. Based on the above embodiments, this embodiment specifically describes the method for the interface consumer to generate transport layer object query language segments, and the method for the syntax parsing filter to obtain query fields. For example... Figure 2 As shown, the method includes:

[0049] S210, The interface consumer obtains the hierarchical relationship between each target field.

[0050] S220. The interface consumer connects each target field using the first identifier and the second identifier according to the hierarchical relationship between each target field, and generates a transport layer object query language segment based on the connection result of each target field.

[0051] Specifically, the interface consumer connects the target fields using the first and second identifiers based on the hierarchical relationship between them, and generates a transport layer object query language segment based on the connection results of the target fields. This can specifically include:

[0052] The interface consumer obtains each first-level target field from the target field, and obtains the bottom-level target field of each first-level target field according to the hierarchical relationship between the target fields;

[0053] The interface consumer uses the first identifier to separate each first-level target field, and uses the first identifier and the second identifier to connect each first-level target field with its respective lower-level target field;

[0054] The interface consumer adds Transport Layer Object Query Language (TLO) identifiers before each target field after connection to generate TLO segments.

[0055] Among them, the first-level target field can be understood as the target field at the same level, and there is no upper-level field of any first-level target field. Each first-level target field can have multiple lower-level target fields, and there can also be a hierarchical relationship between the lower-level target fields. In the process of generating transport layer object query language segments, the relationship between the first-level target field and its lower-level target fields can be expressed by multi-level nested second identifiers.

[0056] Optionally, the Transport Layer Object Query Language (TLOL) identifier can be used to mark TLOL segments. When the parser parses the TLOL identifier, it can accurately obtain the TLOL segment.

[0057] S230. The interface consumer sends the transport layer object query language segment and data query request to the interface provider.

[0058] S240. The interface provider obtains the returned data according to the data query request and sends the returned data and the transport layer object query language segment to the syntax parsing filter.

[0059] Optionally, the interface provider may obtain the returned data according to the data query request and send the returned data along with the transport layer object query language segment to the syntax parsing filter. This may further include:

[0060] When there is no matching query data in the first interface provider that is currently receiving the transport layer object query language segment and data query request, the first interface provider determines the target second interface provider among multiple second interface providers that has matching query data, and forwards the transport layer object query language segment and data query request to the target second interface provider.

[0061] The second target interface provider obtains the returned data according to the data query request, and sends the returned data and the transport layer object query language segment to the syntax parsing filter.

[0062] Among them, the first interface provider can directly transmit data with the interface consumer, the second interface provider does not directly transmit data with the interface consumer, but the first interface provider and the second interface provider can transmit data together, and the target second interface provider contains data that matches the data query request.

[0063] S250, The syntax parsing filter extracts Transport Layer Object Query Language (TLObject) segments from the data sent by the interface provider based on the TLObject Query Language identifier.

[0064] S260. The syntax parsing filter splits and extracts the transport layer object query language segment multiple times until the split fields do not contain the second identifier.

[0065] The syntax parsing filter performs multiple splits and extractions on the transport layer object query language segment until the split fields do not contain the second identifier. Specifically, this can include:

[0066] The syntax parsing filter performs an initial de-identifier split on the transport layer object query language segment and stores the resulting first fields in a list;

[0067] Iterate through the list and determine whether a second field containing a second identifier exists in the list;

[0068] If so, then the fields within the square brackets of the second field are split without the first identifier, the resulting first fields are stored in the list, and the list is traversed again;

[0069] If not, then it is determined that the fields stored in the current list do not include the second identifier.

[0070] The first field can be understood as the fields obtained after the transport layer object query language segment is initially split without the first identifier, and the first field may also include the identifier; the second field can be understood as the field containing the second identifier.

[0071] S270 The syntax parsing filter uses the fields obtained from the final split as query fields and extracts the target data that matches the query fields from the returned data.

[0072] S280, the syntax parsing filter returns the target data to the interface consumer.

[0073] The technical solution of this invention, through the interface consumer, connects each target field using the first identifier and the second identifier according to the hierarchical relationship between each target field, and generates a transport layer object query language segment based on the connection result of each target field. This method can represent the required fields and the hierarchical relationship between each field using simple identifiers, conforms to the original interface style, and does not require rewriting the interface. By using a syntax parsing filter to split and extract the transport layer object query language segment multiple times until the split fields do not contain the second identifier, the query fields can be obtained quickly and efficiently, thereby accurately filtering the returned data and improving the efficiency of data query and data filtering.

[0074] Example 3

[0075] Figure 3 This is a schematic diagram of a data filtering device provided in Embodiment 3 of the present invention. Figure 3 As shown, the device includes: a query information sending module 310, a data providing module 320, and a data filtering module 330.

[0076] The query information sending module 310 is used by the interface consumer to generate a transport layer object query language segment based on the required multi-level target fields, and send the transport layer object query language segment and the data query request to the interface provider.

[0077] The data providing module 320 is used by the interface provider to obtain the returned data according to the data query request, and send the returned data and the transport layer object query language segment to the syntax parsing filter.

[0078] The data filtering module 330 is used to split the transport layer object query language segment into multiple query fields by the syntax parsing filter, extract the target data that matches the query fields in the returned data, and return the target data to the interface consumer.

[0079] The technical solution of this invention involves the interface consumer generating a Transport Layer Object Query Language (TLO) segment based on field requirements. This TLO segment, along with the data query request, is sent to the interface provider. The interface provider then returns data based on the query request and sends the returned data, along with the TLO segment, to a syntax parsing filter. The parsing filter retrieves the query fields required by the interface consumer based on the TLO segment and filters the returned data accordingly. Data that meets the interface consumer's field requirements is then fed back to the interface consumer. This approach allows the interface consumer to quickly and efficiently receive returned data matching its required fields without altering the existing project interfaces, thus saving transmission bandwidth.

[0080] Based on the above embodiments, the transport layer object query language segment includes a first identifier for separating each target field and a second identifier for specifying the value of the target field;

[0081] The second identifier includes a colon and square brackets. The colon indicates the connection between the target field and the next-level target field that matches it, and the square brackets are used to fill in the next-level target field of the target field. The second identifier supports multi-level nesting.

[0082] Based on the above embodiments, the query information sending module 310 may include:

[0083] The hierarchical relationship retrieval unit is used by the interface consumer to obtain the hierarchical relationship between each target field;

[0084] The Transport Layer Object Query Language (TLAGL) segment generation unit is used by the interface consumer to connect each target field according to the hierarchical relationship between each target field using the first identifier and the second identifier, and generate a TLAGL segment based on the connection result of each target field.

[0085] Based on the above embodiments, the transport layer object query language segment generation unit can be specifically used for:

[0086] The interface consumer obtains each first-level target field from the target field, and obtains the bottom-level target field of each first-level target field according to the hierarchical relationship between the target fields;

[0087] The interface consumer uses the first identifier to separate each first-level target field, and uses the first identifier and the second identifier to connect each first-level target field with its respective lower-level target field;

[0088] The interface consumer adds Transport Layer Object Query Language (TLO) identifiers before each target field after connection to generate TLO segments.

[0089] Based on the above embodiments, the data filtering module 330 may include:

[0090] The Transport Layer Object Query Language (TLObject) segment extraction unit is used by the syntax parsing filter to extract TLObject segments from the data sent by the interface provider based on the TLObject identifier.

[0091] The Transport Layer Object Query Language segment splitting unit is used by the syntax parsing filter to split and extract the Transport Layer Object Query Language segment multiple times until the second identifier is not included in the fields after splitting.

[0092] The target data extraction unit is used by the syntax parsing filter to take the fields obtained from the final split as query fields and extract the target data that matches the query fields from the returned data.

[0093] Based on the above embodiments, the transport layer object query language segment splitting unit can be specifically used for:

[0094] The syntax parsing filter performs an initial de-identifier split on the transport layer object query language segment and stores the resulting first fields in a list;

[0095] Iterate through the list and determine whether a second field containing a second identifier exists in the list;

[0096] If so, then the fields within the square brackets of the second field are split without the first identifier, the resulting first fields are stored in the list, and the list is traversed again;

[0097] If not, then it is determined that the fields stored in the current list do not include the second identifier.

[0098] Based on the above embodiments, the data providing module 320 can also be specifically used for:

[0099] When there is no matching query data in the first interface provider that is currently receiving the transport layer object query language segment and data query request, the first interface provider determines the target second interface provider among multiple second interface providers that has matching query data, and forwards the transport layer object query language segment and data query request to the target second interface provider.

[0100] The second target interface provider obtains the returned data according to the data query request, and sends the returned data and the transport layer object query language segment to the syntax parsing filter.

[0101] The data filtering device provided in the embodiments of the present invention can execute the data filtering method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of executing the method.

[0102] Example 4

[0103] Figure 4 A schematic diagram of an electronic device 10 that can be used to implement embodiments of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0104] like Figure 4As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 may also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0105] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0106] Processor 11 can be various general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, central processing unit (CPU), graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, digital signal processors (DSPs), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as the data filtering method as described in the embodiments of the present invention. That is:

[0107] The interface consumer generates a transport layer object query language segment based on the required multi-level target fields, and sends the transport layer object query language segment and the data query request to the interface provider;

[0108] The interface provider obtains the returned data according to the data query request, and sends the returned data and the transport layer object query language segment to the syntax parsing filter;

[0109] The syntax parsing filter splits the transport layer object query language segment into multiple query fields, extracts the target data that matches the query fields from the returned data, and returns the target data to the interface consumer.

[0110] In some embodiments, the data filtering method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or mounted on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the data filtering method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the data filtering method by any other suitable means (e.g., by means of firmware).

[0111] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0112] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0113] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. 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 fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0114] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0115] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0116] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0117] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0118] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A data filtering method, characterized in that, include: The interface consumer generates a Transport Layer Object Query Language (TLO) segment based on the required multi-level target fields, and sends the TLO segment and data query request to the interface provider. The TLO is a language that can represent the hierarchical relationship between multiple fields, and the TLO segment is a segment generated by the interface consumer based on the required multi-level target fields and the TLO. The transport layer object query language segment includes a first identifier for separating each target field and a second identifier for specifying the value of the target field; wherein, the second identifier includes a colon and square brackets, the colon is used to indicate the connection relationship between the target field and the next level target field that matches it, the square brackets are used to fill in the next level target field of the target field, and the second identifier supports multi-level nesting; The interface provider obtains the returned data according to the data query request, and sends the returned data and the transport layer object query language segment to the syntax parsing filter; The syntax parsing filter splits the transport layer object query language segment into multiple query fields, extracts the target data that matches the query fields from the returned data, and returns the target data to the interface consumer.

2. The method according to claim 1, characterized in that, The interface consumer generates transport layer object query language segments based on the required multi-level target fields, including: The interface consumer obtains the hierarchical relationship between the target fields; The interface consumer connects the target fields using the first identifier and the second identifier according to the hierarchical relationship between them, and generates a transport layer object query language segment based on the connection results of the target fields.

3. The method according to claim 2, characterized in that, The interface consumer connects the target fields according to the hierarchical relationship between them using the first and second identifiers, and generates a transport layer object query language segment based on the connection results of the target fields, including: The interface consumer obtains each first-level target field from the target field, and obtains the bottom-level target field of each first-level target field according to the hierarchical relationship between the target fields; The interface consumer uses the first identifier to separate each first-level target field, and uses the first identifier and the second identifier to connect each first-level target field with its respective lower-level target field; The interface consumer adds Transport Layer Object Query Language (TLO) identifiers before each target field after connection to generate TLO segments.

4. The method according to claim 3, characterized in that, The parsing filter splits the transport layer object query language segment into multiple query fields and extracts target data matching the query fields from the returned data, including: The syntax parsing filter extracts Transport Layer Object Query Language (TLObject) segments from the data sent by the interface provider based on the TLObject Query Language identifier. The syntax parsing filter splits and extracts the transport layer object query language segment multiple times until the second identifier is not included in the fields after splitting. The syntax parsing filter uses the fields obtained from the final split as query fields and extracts the target data that matches the query fields from the returned data.

5. The method according to claim 4, characterized in that, The parsing filter performs multiple splits and extractions on the transport layer object query language segment until the split fields do not contain the second identifier, including: The syntax parsing filter performs an initial de-identifier split on the transport layer object query language segment and stores the resulting first fields in a list; Iterate through the list and determine whether a second field containing a second identifier exists in the list; If so, then the fields within the square brackets of the second field are split without the first identifier, the resulting first fields are stored in the list, and the list is traversed again; If not, then it is determined that the fields stored in the current list do not include the second identifier.

6. The method according to claim 1, characterized in that, The interface provider obtains the returned data according to the data query request, and sends the returned data and the transport layer object query language segment to the syntax parsing filter, which also includes: When there is no matching query data in the first interface provider that is currently receiving the transport layer object query language segment and data query request, the first interface provider determines the target second interface provider among multiple second interface providers that has matching query data, and forwards the transport layer object query language segment and data query request to the target second interface provider. The second target interface provider obtains the returned data according to the data query request, and sends the returned data and the transport layer object query language segment to the syntax parsing filter.

7. A data filtering device, characterized in that, include: The query information sending module is used by the interface consumer to generate a Transport Layer Object Query Language (TLO) segment based on the required multi-level target fields, and send the TLO segment and the data query request to the interface provider; wherein, the TLO is a language that can represent the hierarchical relationship between multiple fields, and the TLO segment is a segment generated by the interface consumer based on the required multi-level target fields and relying on the TLO; The transport layer object query language segment includes a first identifier for separating each target field and a second identifier for specifying the value of the target field; wherein, the second identifier includes a colon and square brackets, the colon is used to indicate the connection relationship between the target field and the next level target field that matches it, the square brackets are used to fill in the next level target field of the target field, and the second identifier supports multi-level nesting; The data providing module is used by the interface provider to obtain the returned data according to the data query request, and send the returned data and the transport layer object query language segment to the syntax parsing filter; The data filtering module is used to split the transport layer object query language segment into multiple query fields using a syntax parsing filter, extract the target data that matches the query fields from the returned data, and return the target data to the interface consumer.

8. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the data filtering method according to any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the data filtering method according to any one of claims 1-6.

Images