A data processing method and device

Abstract

The present application provides a data processing method and apparatus. The middleware can expose, through the front-end page, the tag value input controls corresponding to the tags involved in each data system docked by the middleware to the upper-layer users. The middleware hands over the underlying query logics of each data system for each type of query index to the upper-layer users for specification, and the middleware does not need to care about the underlying query logics of each data system for each type of query index. The upper-layer users can input a target tag value through the target tag value input control corresponding to the target tag among the multiple tags involved in the data system in the front-end page, so as to indirectly specify the underlying query logic of the data system for this time. Through the present application, the decoupling between the middleware and the underlying query logics of each data system docked by the middleware for each type of query index is achieved, reducing the complexity of the middleware.

Description

Technical Field

[0001] This application relates to the field of computer technology, and particularly to a data processing method and apparatus. Background Art

[0002] Currently, many manufacturers with service-providing capabilities use data systems to provide services to internal employees and external customers. The data systems have functions such as data storage, data query, and data processing. Summary of the Invention

[0003] This application discloses a data processing method and apparatus.

[0004] In a first aspect, this application discloses a data processing method. The method is applied to a terminal and includes: displaying a front-end page provided by a middleware, where the front-end page at least includes a plurality of tag value input controls, and the middleware is docked with a plurality of data systems; obtaining a target tag value input through a target tag value input control among the plurality of tag value input controls, and obtaining a system identifier of a data system specified for the target tag value input control; sending at least the target tag value and the system identifier to the middleware; so that the middleware generates a data query statement, the data query statement at least carries the target tag value, and sends the data query statement to the data system according to the system identifier; and enabling the data system to find a target data identifier set corresponding to target tag information in a correspondence relationship between tag information and a data identifier set set in the data system, the target tag information at least includes the target tag value, finding data corresponding to each data identifier in the target data identifier set in the data system, and sending at least part of the found data to the middleware; and further enabling the middleware to receive at least part of the found data and send at least part of the found data to the terminal; receiving at least part of the found data sent by the middleware.

[0005] Second aspect, the present application discloses a data processing method, which is applied to middleware that is docked with multiple data systems; the method includes: receiving a target tag value and a system identifier sent by at least a terminal; the target tag value is input through a target tag value input control among multiple tag value input controls included at least in a front-end page displayed by the terminal, and the system identifier includes the system identifier of the data system specified for the target tag value input control; the front-end page is provided by the middleware; generating a data query statement that carries at least the target tag value; sending the data query statement to the data system according to the system identifier; and enabling the data system to find a target data identifier set corresponding to target tag information in a correspondence relationship between tag information and a data identifier set set in the data system, the target tag information includes at least the target tag value, finding data corresponding to each data identifier in the target data identifier set in the data system, and sending at least some of the found data to the middleware; receiving at least some of the found data sent by the data system; and sending at least some of the found data to the terminal so that the terminal receives at least some of the found data.

[0006] Third aspect, the present application discloses a data processing method, which is applied to a data system; the method includes: receiving a data query statement; the data query statement is generated by the middleware and sent to the data system according to the system identifier of the data system, the data query statement carries at least a target tag value, the target tag value and the system identifier are sent by the terminal to the middleware; the target tag value is input through a target tag value input control among multiple tag value input controls included at least in a front-end page displayed by the terminal, and the system identifier includes the system identifier of the data system specified for the target tag value input control; the front-end page is provided by the middleware that is docked with multiple data systems; finding a target data identifier set corresponding to target tag information in a correspondence relationship between tag information and a data identifier set set in the data system, the target tag information includes at least the target tag value in the data query statement; finding data corresponding to each data identifier in the target data identifier set in the data system; sending at least some of the found data to the middleware so that the middleware receives at least some of the found data and sends at least some of the found data to the terminal, and enabling the terminal to receive at least some of the found data.

[0007] Fourth aspect, the present application discloses a data processing device, which is applied to a terminal. The device includes: a display module for displaying a front-end page provided by a middleware, where the front-end page at least includes a plurality of tag value input controls, and the middleware is docked with a plurality of data systems; a first acquisition module for acquiring a target tag value input according to a target tag value input control among the plurality of tag value input controls, and a second acquisition module for acquiring a system identifier of a data system specified for the target tag value input control; a first sending module for sending at least the target tag value and the system identifier to the middleware; so that the middleware generates a data query statement, the data query statement at least carries the target tag value, and sends the data query statement to the data system according to the system identifier; and enables the data system to find a target data identifier set corresponding to target tag information in the established correspondence between tag information and data identifier sets in the data system, the target tag information at least includes the target tag value, finds the data corresponding to each data identifier in the target data identifier set in the data system, and sends at least part of the found data to the middleware; and further enables the middleware to receive at least part of the found data and send at least part of the found data to the terminal; a first receiving module for receiving at least part of the found data sent by the middleware.

[0008] Fifth aspect, the present application discloses a data processing device, which is applied to a middleware, and the middleware is docked with a plurality of data systems; the device includes: a second receiving module for receiving at least the target tag value and the system identifier sent by the terminal; the target tag value is input according to a target tag value input control among the plurality of tag value input controls at least included in the front-end page displayed by the terminal, and the system identifier includes the system identifier of the data system specified for the target tag value input control; the front-end page is provided by the middleware; a generation module for generating a data query statement, the data query statement at least carries the target tag value; a third sending module for sending the data query statement to the data system according to the system identifier; and enables the data system to find a target data identifier set corresponding to target tag information in the established correspondence between tag information and data identifier sets in the data system, the target tag information at least includes the target tag value, finds the data corresponding to each data identifier in the target data identifier set in the data system, and sends at least part of the found data to the middleware; a third receiving module for receiving at least part of the found data sent by the data system; a fourth sending module for sending at least part of the found data to the terminal, so that the terminal receives at least part of the found data.

[0009] Sixth aspect, the present application discloses a data processing device, which is applied to a data system. The device includes: a fifth receiving module, configured to receive a data query statement; the data query statement is generated by middleware and sent to the data system according to the system identifier of the data system, and the data query statement carries at least a target tag value. The target tag value and the system identifier are sent by a terminal to the middleware; the target tag value is input through a target tag value input control among a plurality of tag value input controls included in at least the front-end page displayed by the terminal, and the system identifier includes the system identifier of the data system specified for the target tag value input control; the front-end page is provided by the middleware, and the middleware is docked with a plurality of data systems; a first searching module, configured to search, in the correspondence relationship between the tag information and the data identifier set already set in the data system, for the target data identifier set corresponding to the target tag information, where the target tag information includes at least the target tag value in the data query statement; a second searching module, configured to search, in the data system, for the data corresponding to each data identifier in the target data identifier set; a fifth sending module, configured to send at least part of the searched data to the middleware, so that the middleware receives at least part of the searched data and sends at least part of the searched data to the terminal, and the terminal receives at least part of the searched data.

[0010] Seventh aspect, the present application discloses an electronic device, which includes: a processor; a memory for storing processor-executable instructions; wherein, the processor is configured to execute the method shown in any of the foregoing aspects.

[0011] Eighth aspect, the present application discloses a non-transitory computer-readable storage medium. When the instructions in the storage medium are executed by a processor of an electronic device, the electronic device can execute the method shown in any of the foregoing aspects.

[0012] Ninth aspect, the present application discloses a computer program product. When the instructions in the computer program product are executed by a processor of an electronic device, the electronic device can execute the method shown in any of the foregoing aspects.

[0013] Compared with the prior art, the present application has the following advantages:

[0014] In the present application, the fields involved in each data system docked by the middleware can be counted, the fields involved in each data system docked by the middleware are respectively converted into the form of tags, and at least tag value input controls corresponding to each tag are set in the front-end page provided by the middleware. In this way, through the front-end page, the middleware can expose the tag value input controls corresponding to the tags involved in each data system docked by the middleware to the upper-layer users.

[0015] The middleware returns the underlying query logic of each data system for each type of query index to the upper-layer user for specification, and the middleware does not need to care about the underlying query logic of each data system for each type of query index. For example, for the data system of manufacturer A, the middleware does not need to care about the underlying query logic of the data system of manufacturer A for the query index field "name of the creator" (its query logic is to query not only the data created by the creator "Zhang San", but also the data created by the subordinate employees of the creator "Zhang San").

[0016] When the upper-layer user needs to query data in a certain data system, the upper-layer user can input the target tag value through the target tag value input control corresponding to the target tag among the multiple tags related to the data system in the front-end page, so as to indirectly specify the underlying query logic of this time for the data system.

[0017] Through this application, the underlying query logics of the middleware and the data systems of each manufacturer docked with the middleware for each type of query index are decoupled, reducing the complexity of the middleware.

[0018] Enables the developers of the middleware not to perceive the underlying query logics of the data systems of each manufacturer docked with the middleware for various types of query indexes, and not to deploy the underlying query logics of the data systems of each manufacturer docked with the middleware for each type of query index in the middleware.

[0019] In addition, in this application, the data system does not match the data in each data index in the data system with the "field and the corresponding field value" according to the field and the corresponding field value. In this way, the middleware does not need to have the ability to "generate the computer data query statements supported by the data systems of each manufacturer docked with the middleware (such as perceiving the form and syntax of the computer data query statements, etc.)", so that the developers of the middleware do not need to master and understand the computer data query statements supported by the data systems of each manufacturer docked with the middleware.

[0020] The data system is to "at least find the data identification set corresponding to the label information according to the label value corresponding to the label involved in the data system in the corresponding relationship between the label information and the data identification set, where the label information at least includes the label value corresponding to the label involved in the data system" and "find the data corresponding to each data identification in the data identification set in the data system". The above two search actions are unified for each data system docked with the middleware and there is no difference for each data system.

[0021] Thus, the present application can reduce the technical ability requirements of developers for the middleware developed to interface with the data systems of various manufacturers, and further reduce the technical difficulty, workload, and development cost of the middleware developed to interface with the data systems of various manufacturers.

[0022] Secondly, after the middleware is put into application, for any data system of a manufacturer interfaced by the middleware, even if the upper-layer user has an update requirement for the underlying query logic of the data system of this manufacturer, since the middleware and the data systems of various manufacturers interfaced by the middleware are strongly coupled respectively between the underlying query logics for various types of query indexes, therefore, the developers of the middleware can be unaware of the updated underlying query logics for various types of query indexes of the data system of this manufacturer interfaced by the middleware, and can not deploy the updated underlying query logics for various types of query indexes of the data systems of various manufacturers interfaced by the middleware in the middleware. Thus, it can reduce the technical difficulty, workload, and maintenance cost of maintaining the middleware developed to interface with the data systems of various manufacturers. Description of the Drawings

[0023] Figure 1 is a structural block diagram of a data processing architecture of the present application.

[0024] Figure 2 is a step flow chart of a data processing method of the present application.

[0025] Figure 3 is a structural block diagram of a data processing device of the present application.

[0026] Figure 4 is a structural block diagram of a data processing device of the present application.

[0027] Figure 5 is a structural block diagram of a data processing device of the present application.

[0028] Figure 6 is a structural block diagram of a device of the present application. Detailed Embodiments

[0029] To make the above objects, features, and advantages of the present application more obvious and understandable, the present application will be further described in detail below with reference to the drawings and specific embodiments.

[0030] For any service provider, data can be stored in the data system of the service provider. And for the convenience of subsequent upper-layer users to query data in the data system, for any piece of data stored in the data system of the service provider, the provider can pre-set the fields related to the data system of the provider for this piece of data in the data system of the provider. In this way, this piece of data has each field related to the data system of the provider. The fields can include the generation time of the data, the update time of the data, the name of the creator of the data, the number of the data, etc. The provider can also set the field values respectively corresponding to each field for this piece of data in the data system of the provider (the field values can be manually input or automatically obtained by the data system, etc.). The same applies to each other piece of data stored in the data system of the service provider. In this way, each piece of data in the data system of the provider is bound with each field related to the provider and the field values respectively corresponding to each field, so that in the case where subsequent upper-layer users need to query data in the data system of the provider, data can be queried in the data system of the provider according to at least some of the fields related to the data system of the provider and the field values specified by the upper-layer users for at least some of the fields.

[0031] For example, the data system of the provider provides a front-end page for upper-layer users to use. In the case where upper-layer users need to query data in the data system of the provider, the upper-layer users can enter the front-end page provided by the data system of the provider. In the front-end page provided by the data system of the provider, each field related to the data system of the provider and the input boxes for the field values respectively corresponding to each field are displayed. The upper-layer users can input the target field values respectively corresponding to at least some of the fields in the input boxes for the field values respectively corresponding to at least some of the fields in the front-end page provided by the data system of the provider, and control the front-end page provided by the data system of the provider to generate a query request. The query request carries at least some of the fields related to the data system of the provider and the target field values respectively corresponding to at least some of the fields input by the upper-layer users. For example, the query request can be an SQL data query statement including "carrying at least some of the fields related to the data system of the provider and the target field values respectively corresponding to at least some of the fields input by the upper-layer users", etc. The data system of the provider can recognize the SQL data query statement. Then the front-end page provided by the data system of the provider can transmit the query request to the data system of the provider, so that the data system of the provider can query data in the data system of the provider according to at least some of the fields and the target field values respectively corresponding to at least some of the fields in the query request, and return the queried data to the upper-layer users.

[0032] For example, an upper-layer user needs to query data in the data system of this manufacturer based on the field "creator's name" and the target field value "Zhang San" corresponding to the field "creator's name". Thus, the upper-layer user can input the target field value "Zhang San" in the field value input box corresponding to the field "creator's name" on the front-end page provided by the data system of this manufacturer, and manipulate the front-end page provided by the data system of this manufacturer to generate a query request. The query request carries the field "creator's name" involved in the data system of this manufacturer and the target field value "Zhang San" of the field "creator's name" input by the upper-layer user. For example, the query request may include an SQL data query statement, and the SQL data query statement may include: WHERE (creatorUid = ${Zhang San}). Subsequently, the front-end page provided by the data system of this manufacturer can transmit the query request to the data system of this manufacturer, so that the data system of this manufacturer can query the data created by the creator "Zhang San", that is, so that the data system of this manufacturer can query data in the data system of this manufacturer based on the field "creator's name" and the target field value "Zhang San" corresponding to the field "creator's name", and return the queried data to the upper-layer user. In one example, the queried data may include the data created by the creator "Zhang San", etc.

[0033] Among them, sometimes, multiple different manufacturers belong to the same group, and each manufacturer in the same group has its own data system. Sometimes, according to actual needs, the upper-layer user may need to query data in the data systems of two or more manufacturers in the same group respectively.

[0034] In a scenario where an upper-layer user needs to query data separately in the data systems of two or more manufacturers within the same group, in one approach, for any one of the two or more manufacturers, the upper-layer user can enter the front-end page provided by the data system of that manufacturer. In the front-end page provided by the data system of that manufacturer, various fields involved in the data system of that manufacturer and the corresponding field-value input boxes for each field are displayed. The upper-layer user can enter the target field values corresponding to at least some of the fields in the corresponding field-value input boxes for at least some of the fields in the front-end page provided by the data system of that manufacturer, and control the front-end page provided by the data system of that manufacturer to generate a query request. The query request carries at least some of the fields involved in the data system of that manufacturer and the target field values corresponding to at least some of the fields entered by the upper-layer user. For example, the query request may include an SQL data query statement carrying at least some of the fields involved in the data system of that manufacturer and the target field values corresponding to at least some of the fields entered by the upper-layer user. The data system of that manufacturer can recognize the SQL data query statement. Subsequently, the front-end page provided by the data system of that manufacturer can pass the query request to the data system of that manufacturer, enabling the data system of that manufacturer to query the data required by the upper-layer user in the data system of that manufacturer based on at least some of the fields and the target field values corresponding to at least some of the fields in the query request, and return the queried data to the upper-layer user. The same applies to each of the other manufacturers among the two or more manufacturers.

[0035] However, the inventors found that in the scenario of "an upper-layer user needs to query data separately in the data systems of two or more manufacturers within the same group", there are some defects in the above approach:

[0036] For example, in the scenario of "an upper-layer user needs to query data separately in the data systems of two or more manufacturers within the same group", the upper-layer user needs to enter the front-end pages provided by the data systems of each of the two or more manufacturers separately in sequence, and enter the target field values corresponding to at least one field in the front-end pages provided by the data systems of each of the two or more manufacturers separately. And usually, the upper-layer user enters the front-end pages provided by the data systems of each of the two or more manufacturers in sequence. In this way, for the upper-layer user, the overall query work of "querying data separately in the data systems of two or more manufacturers within the same group" is a sequential serial query from one data system to another. It can be seen that this will result in cumbersome operations and low query efficiency for the upper-layer user.

[0037] Thus, there is a need to simplify the operations of the upper-layer user and improve the query efficiency.

[0038] In order to achieve the purpose of "simplifying the operations of upper-layer users and improving query efficiency", the inventor came up with another method: for example, developing a middleware that can serve as a middleware between upper-layer users and the data systems of various manufacturers. The middleware is respectively connected to the data systems of various manufacturers. Moreover, developers can count the fields involved in the data systems of various manufacturers respectively and set the fields involved in the data systems of various manufacturers in the middleware. The middleware can provide a front-end page for upper-layer users, and the front-end page can display the fields involved in the data systems of various manufacturers and the field value input boxes corresponding to each field respectively.

[0039] In this way, when an upper-layer user needs to query data in the data systems of two or more manufacturers in the same group respectively, the upper-layer user can enter the front-end page provided by the middleware. The front-end page provided by the middleware is divided into areas for various manufacturers, and in any area of a manufacturer, the fields involved in the data system of that manufacturer and the field value input boxes corresponding to each field are displayed.

[0040] For any one of the two or more manufacturers, the upper-layer user can input the target field values corresponding to at least some of the fields in the field value input boxes corresponding to at least some of the fields in the area of that manufacturer in the front-end page provided by the middleware, and transmit at least some of the fields and the target field values corresponding to at least some of the fields to the middleware through the front-end page. Then, the middleware can generate a query request including at least some of the fields and the target field values corresponding to at least some of the fields, and pass the query request including at least some of the fields and the target field values corresponding to at least some of the fields to the data system of that one manufacturer. After that, the data system of that one manufacturer can query the data that the upper-layer user needs to query in the data system of that one manufacturer according to the query request including at least some of the fields and the target field values corresponding to at least some of the fields, and return the data queried in the data system of that one manufacturer to the middleware. Then, the middleware can return the data queried in the data system of that one manufacturer to the upper-layer user through the front-end page. The same applies to each of the other manufacturers among the two or more manufacturers.

[0041] In this way, the upper-layer user can achieve the purpose of querying data in the data systems of two or more manufacturers in the same group respectively through one page, avoiding entering the front-end pages provided by two or more manufacturers respectively, thereby simplifying the operations of the upper-layer users and improving query efficiency.

[0042] In one example, an upper-layer user needs to query data separately in more than two data systems according to the name of the creator. For example, the upper-layer user needs to query data in the data system of manufacturer A and the data system of manufacturer B according to the name of the creator, "Zhang San".

[0043] In this way, the upper-layer user can enter the target field value "Zhang San" in the field value input box corresponding to the field "Name of the Creator" in the area of manufacturer A on the front-end page provided by the middleware. And the upper-layer user can enter the target field value "Zhang San" in the field value input box corresponding to the field "Name of the Creator" in the area of manufacturer B on the front-end page provided by the middleware, and transmit the transmission field "Name of the Creator" and the target field value "Zhang San" for manufacturer A to the middleware through the front-end page. And transmit the transmission field "Name of the Creator" and the target field value "Zhang San" for manufacturer B to the middleware through the front-end page.

[0044] The middleware will receive the transmission field "Name of the Creator" and the target field value "Zhang San" for manufacturer A, and receive the transmission field "Name of the Creator" and the target field value "Zhang San" for manufacturer B.

[0045] In this way, the middleware can generate a data query statement adapted to manufacturer A according to the transmission field "Name of the Creator" and the target field value "Zhang San" for manufacturer A, then transmit the data query statement adapted to manufacturer A to the data system of manufacturer A. After that, the data system of manufacturer A can query data in the data system of manufacturer A according to the data query statement adapted to manufacturer A, and return the data queried in the data system of manufacturer A to the middleware. Then the middleware can return the data queried in the data system of manufacturer A to the upper-layer user through the front-end page.

[0046] And the middleware can generate a data query statement adapted to manufacturer B according to the transmission field "Name of the Creator" and the target field value "Zhang San" for manufacturer B, then transmit the data query statement adapted to manufacturer B to the data system of manufacturer B. After that, the data system of manufacturer B can query data in the data system of manufacturer B according to the data query statement adapted to manufacturer B, and return the data queried in the data system of manufacturer B to the middleware. Then the middleware can return the data queried in the data system of manufacturer B to the upper-layer user through the front-end page.

[0047] However, the inventor also found some situations:

[0048] On the one hand, sometimes, the types of data systems of each manufacturer are different, and the underlying query logics supported by different types of data systems are different. Thus, the underlying query logics supported by the data systems of each manufacturer are different.

[0049] For example, the underlying query logics of data systems of different manufacturers for the same type of query index (the query index can be differentiated by fields, such as the field "creator's name" mentioned above) sometimes vary, which requires the middleware to be aware of the underlying query logics of each manufacturer for the same type of query index. In this way, the middleware can generate data query statements adapted to different manufacturers based on the underlying query logics of the manufacturers for the same type of query index.

[0050] For example, for the data system of manufacturer A, if the upper-layer user inputs the target field value "Zhang San" in the field value input box corresponding to the field "creator's name" in the front-end page of the data system of manufacturer A, the query index at this time involves the field "creator's name". The underlying query logic of the data system of manufacturer A for the query index field "creator's name" is: not only query the data created by the creator "Zhang San", but also query the data created by the subordinate employees of the creator "Zhang San". It can be seen that in this underlying query logic, there are actually two query indexes. Each piece of data in the data system of manufacturer A also involves the field "subordinate employee's name" and the field values corresponding to the field "subordinate employee's name".

[0051] Again, for example, for the data system of manufacturer B, if the upper-layer user inputs the target field value "Zhang San" in the field value input box corresponding to the field "creator's name" in the front-end page of the data system of manufacturer B, the query index at this time involves the field "creator's name". The underlying query logic of the data system of manufacturer B for the query index field "creator's name" is: only query the data created by the creator "Zhang San". It can be seen that in this underlying query logic, there is actually one query index.

[0052] Thus, it can be seen that the middleware needs to be able to adapt to the underlying query logics of different manufacturers' data systems for the same type of query index. For this purpose, when developing the middleware in advance, it is necessary to develop the function of "the middleware respectively adapting to the underlying query logics of each manufacturer's data system for the same type of query index" so that the middleware has the ability to "respectively adapt to the underlying query logics of each manufacturer's data system for the same type of query index".

[0053] On the other hand, sometimes, the types of data systems of each manufacturer are different, and the computer data query statements supported by different types of data systems are different, resulting in different computer data query statements supported by the data systems of each manufacturer. Moreover, computer data query statements involve syntax and parameter configuration, etc. For example, for a data system, the data system supports a computer data query statement (computer program code). For example, the computer data query statement is an SQL data query statement in a specific form and syntax, etc., and the parameter configuration in the computer data query statement is also in a specific form.

[0054] Thus, for any one of more than two manufacturers, when the middleware obtains the target field values corresponding to at least some of the fields entered by the upper-layer user in the area of this manufacturer in the front-end page provided by the middleware, the middleware can generate a computer data query statement supported by the data system of this manufacturer based on "the target field values corresponding to at least some of the fields entered by the upper-layer user in the area of this manufacturer in the front-end page provided by the middleware and at least some of the fields", so that the data system of this manufacturer can query the data that the upper-layer user needs to query in the data system of this manufacturer according to this computer data query statement and return the queried data to the middleware. Among them, in order to enable the middleware to have the ability to "generate a computer data query statement supported by the data system of this manufacturer based on 'the target field values corresponding to at least some of the fields entered by the upper-layer user in the area of this manufacturer in the front-end page provided by the middleware and at least some of the fields'", developers need to perform adaptability settings on the middleware in advance. For example, write computer program code in the middleware that can implement the function of "generating a computer data query statement supported by the data system of this manufacturer based on 'the target field values corresponding to at least some of the fields entered by the upper-layer user in the area of this manufacturer in the front-end page provided by the middleware and at least some of the fields'", so that the middleware can achieve the purpose of "generating a computer data query statement supported by the data system of this manufacturer based on 'the target field values corresponding to at least some of the fields entered by the upper-layer user in the area of this manufacturer in the front-end page provided by the middleware and at least some of the fields'" when executing the written computer program code. The same applies to each of the other manufacturers among more than two manufacturers.

[0055] In actual situations, for each data system docked by the middleware, adaptability work needs to be carried out in the middleware.

[0056] Thus, it can be seen that there are some problems in the above-mentioned another way, such as:

[0057] 1. The data systems of each manufacturer that the middleware interfaces with are strongly coupled with the underlying query logics of each type of query index respectively. The developers of the middleware need to be aware of the underlying query logics of the data systems of each manufacturer that the middleware interfaces with for various types of query indexes, deploy the underlying query logics of the data systems of each manufacturer that the middleware interfaces with for each type of query index in the middleware, and master and understand the computer data query statements supported by the data systems of each manufacturer that the middleware interfaces with (such as perceiving the forms and grammars of computer data query statements, etc.), and deploy the ability to "generate computer data query statements supported by the data systems of each manufacturer that the middleware interfaces with" in the middleware. In summary, for any one of the data systems of the manufacturers that the middleware interfaces with, the developers need to write computer program code for the function of "generating computer data query statements that are supported by the data system of this manufacturer and respectively adapted to the underlying query logics of the data system of this manufacturer for various types of query indexes" in the middleware. It can be seen that developing middleware for interfacing with the data systems of each manufacturer requires high technical capabilities of the developers, resulting in high technical difficulty, large workload, and high development cost for developing middleware for interfacing with the data systems of each manufacturer.

[0058] 2. After the middleware is put into application, for any one of the data systems of the manufacturers that the middleware interfaces with, sometimes the upper-layer users have update requirements for the underlying query logic of the data system of this manufacturer.

[0059] For example, assuming the data system of manufacturer B, if the upper-layer user inputs the target field value "Zhang San" in the field value input box corresponding to the field "creator's name" in the front-end page of the data system of manufacturer B, then the query index at this time involves the field "creator's name", and the underlying query logic of the data system of manufacturer B for the query index field "creator's name" is: only query the data created by the creator "Zhang San". It can be seen that in this underlying query logic, there is actually one query index.

[0060] However, according to the actual requirements, the upper-layer user needs to update the underlying query logic of the data system of manufacturer B for this query index. For example, if the upper-layer user inputs the target field value "Zhang San" in the field value input box corresponding to the field "creator's name" in the front-end page of the data system of manufacturer B, then the query index at this time involves the field "creator's name", and the underlying query logic of the data system of manufacturer B for the query index field "creator's name" is: not only query the data created by the creator "Zhang San", but also query the data in the projects participated by the creator "Zhang San". It can be seen that in this underlying query logic, there are actually two query indexes.

[0061] In order for the middleware to "generate computer data query statements that are supported by the data system of the manufacturer and adapted to the updated underlying query logic of the query index of the data system of the manufacturer for this type of query", the developers of the middleware need to write computer program code for the function of "generating computer data query statements that are supported by the data system of the manufacturer and adapted to the updated underlying query logic of the query index of the data system of the manufacturer for this type of query" in the middleware, and use the computer program code for the function of "generating computer data query statements that are supported by the data system of the manufacturer and adapted to the updated underlying query logic of the query index of the data system of the manufacturer for this type of query" to replace the computer program code for the function of "generating computer data query statements that are supported by the data system of the manufacturer and adapted to the underlying query logic of the query index of the data system of the manufacturer before the update for this type of query".

[0062] It can be seen that the underlying query logics of the middleware and the data systems of each manufacturer docked with the middleware for each type of query index are strongly coupled respectively. Developers need to be aware of the underlying query logics of the data systems of each manufacturer docked with the middleware for the updated query indexes of various types, and deploy the underlying query logics of the data systems of each manufacturer docked with the middleware for the updated query indexes of various types in the middleware, resulting in high technical difficulty, large workload, and high maintenance cost for maintaining the middleware used to dock with the data systems of each manufacturer in the later stage.

[0063] Thus, there is a need to "reduce the technical difficulty, workload, and development cost of developing middleware for docking with the data systems of each manufacturer, and reduce the technical difficulty, workload, and maintenance cost of maintaining middleware for docking with the data systems of each manufacturer in the later stage".

[0064] In order to achieve the purpose of "reducing the technical difficulty, workload, and development cost of developing middleware for docking with the data systems of each manufacturer, and reducing the technical difficulty, workload, and maintenance cost of maintaining middleware for docking with the data systems of each manufacturer in the later stage", the inventor thought of another way:

[0065] Specifically, referring to Figure 1 , a structural block diagram of a data processing architecture of the present application is shown. The architecture includes a terminal 01, a middleware 02, and multiple data systems 03. Communication connections can be established between the terminal and the middleware. Communication connections can be established between the middleware and multiple data systems respectively, that is, the middleware is docked with multiple data systems.

[0066] The terminal may include terminals used by upper-layer users, etc. For example, it may include mobile phones, tablet computers, laptop computers, or desktop computers, etc.

[0067] The middleware can exist in the form of a physical machine, etc. The physical machine can include a server, etc. Alternatively, the middleware can also exist in the form of software, which can be an application, etc. In one example, the middleware can include: DataSet Management Service, which realizes the unified management of data sets in each data system, and then realizes the data query requirements of upper-layer users through the combined query of tags.

[0068] Each data system can respectively include a data engine, and each data system stores its own data, etc.

[0069] Secondly, referring to Figure 2 , a schematic flowchart of a data processing method according to the present application is shown. This method is applied to Figure 1 the data processing architecture shown, where the method includes:

[0070] In step S101, the terminal displays the front-end page provided by the middleware. The front-end page at least includes a plurality of tag value input controls.

[0071] In another embodiment, the front-end page may further include tags corresponding to each tag value input control respectively. There is a one-to-one correspondence between the multiple tags and the multiple tag value input controls, and there is a one-to-one correspondence between the multiple tags and each field involved in the multiple data systems respectively. Different tag value input controls correspond to different tags respectively. So that it is easier for upper-layer users to know which tag each tag value input control identifies.

[0072] In one example, the tag value input control includes a tag value input box. The tag value input boxes corresponding to different tags in the front-end page are different. For any one tag, the tag value input box uniquely corresponding to this tag is used for upper-layer users to input the tag value corresponding to this tag. The tag can be regarded as "key", and the tag value corresponding to the tag can be regarded as "value". In this way, the tag and the tag value corresponding to the tag can be regarded as a "key-value" relationship.

[0073] The middleware can provide a front-end page to the upper layer (the upper layer can be the upper layer logically. For example, logically, the terminal is the upper layer of the middleware, and the data processing system is the lower layer of the middleware, etc.). The multiple tag value input controls in the front-end page are respectively set according to the tags statistically obtained in advance. For example, the fields involved in each data system among the multiple data systems docked by the middleware are statistically obtained in advance, and then the statistically obtained fields are used as tags, and the tag value input controls corresponding to the tags are set in the middleware. The front-end page can be used as an interface for communication between the terminal and the middleware, etc.

[0074] In addition, one of the purposes of the front-end page is for upper-layer users. For example, it is convenient for upper-layer users to query data in multiple data systems. Thus, the fields involved in each data system can have field values (the field values can be empty or be strings with specific meanings, etc.). Accordingly, the tags can also have tag values. As mentioned above, the relationship between a tag and its corresponding tag value can be regarded as a "key-value" relationship. Any field involved in a data system can correspond to a tag, and the tag value corresponding to the tag can be input by the upper-layer user through the tag value input control corresponding to the tag in the front-end page. For example, the tag value corresponding to the tag can be input by the upper-layer user in the tag value input box corresponding to the tag in the front-end page.

[0075] Therefore, in order to enable upper-layer users to query data in the data system according to actual needs, the front-end page can also have tag value input controls (such as tag value input boxes, etc.) that correspond one by one to multiple tags, for the upper-layer users to input the tag values corresponding to the tags through the tag value input controls corresponding to the tags, so that data can be queried in the data system at least according to the tag values later.

[0076] Among them, when the upper-layer user needs to query data in the data system, the upper-layer user can control the terminal to obtain the front-end page from the middleware and display the front-end page. In this way, the upper-layer user can see the front-end page and input the tag value according to the required tag value input control. For example, input the tag value in the required tag value input box, etc.

[0077] In one example, the tags include: the name of the creator, the number of the creator, the creation time, the update time, the ID (Identity Document) of the engineering project to which it belongs, the name of the holder of the project engineering, and the publicly available domain, etc.

[0078] In step S102, the terminal obtains the target tag value input through the target tag value input control among the multiple tag value input controls in the front-end page, and obtains the system identifier of the data system specified for the target tag value input control.

[0079] The target tag value input control is at least part of the multiple tag value input boxes in the front-end page.

[0080] Whichever tag value input control among the multiple tag value input controls displayed in the front-end page the upper-layer user inputs the tag value through, this tag value input control is the target tag value input control, the tag value input through this tag value input control is the target tag value, and the tag corresponding to this tag value input control is the target tag.

[0081] The upper-layer user can input a target tag value according to the target tag value input control in the front-end page (for example, input the target tag value "Zhang San" in the tag value input box corresponding to the tag "creator's name"), and input a query operation in the front-end page. The query operation can include manipulation operations on the query button displayed in the front-end page, etc.

[0082] In this way, when the terminal receives the query operation, it can obtain the target tag value input by the upper-layer user in the target tag value input control in the front-end page, and generate a data query request at least based on the target tag value. For example, if the target tag corresponding to the target tag value is also obtained, a data query request can be generated based on the target tag value and the target tag corresponding to the target tag value, and then step S103 is executed.

[0083] In one embodiment, the target tag value input control has multiple candidate tag values for the upper-layer user to select. The user can input a trigger operation on the target tag value input control in the upper-layer page, such as a click operation, etc. The terminal can receive the trigger operation on the target tag value input control; obtain multiple candidate tag values for input in the target tag value input box according to the trigger operation; and then display the multiple candidate tag values; the user can select a candidate tag value from the displayed multiple candidate tag values. In this way, the terminal can obtain the target tag value according to the selected candidate tag value among the displayed multiple candidate tag values. In this way, it can be avoided that the user manually inputs the target tag value character by character, which can simplify the user operation and improve the efficiency.

[0084] Among them, for "obtaining the system identifier of the data system specified for the target tag value input control", it can be implemented through the following embodiments.

[0085] In one embodiment of the present application, the front-end page includes multiple regions, and different regions are bound to the system identifiers of different data systems. Each data system's region has its own involved tag value input control; for example, for any data system docked with the middleware, there is a region of this data system in the front-end page, that is, this region is bound to the system identifier of this data system, and the region of this data system has the tag value input control involved in this data system. The same is true for each other data system docked with the middleware.

[0086] In this way, the region where the target tag value input control is located can be determined among the multiple regions; and the system identifier bound to the region where the target tag value input control is located can be obtained and used as the system identifier of the data system specified for the target tag value input control.

[0087] For example, for any data system docked with middleware, if an upper-layer user inputs a target tag value through a target tag value input control in the area of the data system (such as inputting a target tag value in the target tag value input box in the area of the data system), the target tag value (or the target tag corresponding to the target tag value input box) can be determined to be for the data system. In this way, the system identifier bound to the area where the target tag value input control is located can be obtained and used as the system identifier of the data system. That is, it can be determined that the upper-layer user needs to query data in the data system corresponding to the system identifier at least according to the target tag value. Among them, each tag value input control involved in the data system in the area of the front-end page corresponds one-to-one to each field involved in the data system. The same applies to each of the other data systems docked with middleware.

[0088] Among them, the system identifiers of different data systems are different, and the system identifier of a data system can include the name or IP (Internet Protocol) address of the data system, etc.

[0089] Or, in another embodiment, in addition to including the tag value input box controls involved in each data system docked with middleware, the front-end page can also include a system identifier option control, and the system identifier option control includes the system identifiers of each data system docked with middleware for the upper-layer user to select.

[0090] For example, after the upper-layer user inputs a target tag value through the target tag value input control in the front-end page, the upper-layer user can also select at least one system identifier according to the system identifier option control. The terminal can obtain at least one system identifier selected according to the system identifier option control (such as obtaining the at least one system identifier selected by the upper-layer user according to the system identifier option control) and use it as the system identifier of the data system specified for the target tag value input control. That is, it can be determined that the upper-layer user needs to query data in the data system corresponding to the system identifier at least according to the target tag value.

[0091] Or, in yet another embodiment, each of the data systems docked with middleware is respectively involved with its own fields, one field corresponds to one tag, and one tag corresponds to one tag value input control. In this way, each of the data systems docked with middleware is respectively involved with its own tags, and the tags involved in any two systems may be the same, may not be completely the same, or may be completely different, etc.

[0092] For example, the tags involved in data system A include: "creator's name", "creator's ID", and "creation time", and the tags involved in data system B include: "creator's name", "creator's ID", and "update time".

[0093] For any data system, the data system involves some tags. Thus, in the scenario of querying data in the data system, at least the data to be queried can be indexed in the data system according to the tag values corresponding to at least one tag involved in the data system, while the data to be queried cannot be indexed in the data system according to the tag values corresponding to the tags not involved in the data system. The same applies to every other data system.

[0094] In addition, since there are many data systems docked by the middleware, and not all the data systems docked by the middleware necessarily involve the target tag. Thus, data can be queried in the data systems involving the target tag at least according to the target tag value corresponding to the target tag, while data does not need to be queried in the data systems not involving the target tag according to the target tag value corresponding to the target tag (no data can be queried in the data systems not involving the target tag according to the target tag value corresponding to the target tag, so unnecessary operations can be reduced and computing resources of the data system can be saved). Therefore, the middleware needs to determine the data systems involving the target tag.

[0095] In one example, the tag can be embodied in the form of a string. For any data system docked by the middleware, after counting the tags involved in the data system and setting the tag value input control corresponding to the tag in the middleware, the control identifier of the tag value input control involved in the data system and the system identifier of the data system can be composed into a corresponding table entry and stored in the corresponding relationship between the control identifier of the tag value input control involved in the data system and the system identifier of the data system. The same operation is performed for every other data system docked by the middleware.

[0096] Thus, after the terminal obtains the target tag value input through the target tag value input control corresponding to the target tag in the multiple tag value input boxes on the front-end page, the system identifier corresponding to the control identifier of the target tag value input control can be found in the corresponding relationship between the control identifier of the tag value input control involved in the data system and the system identifier of the data system, and used as the system identifier of the data system specified for the target tag value input control.

[0097] The control identifiers of different tag value input controls are different.

[0098] In step S103, the terminal sends at least the target tag value and the system identifier to the middleware.

[0099] The terminal can send at least the target tag value and the system identifier to the middleware through the communication connection between the terminal and the middleware.

[0100] In another embodiment, the terminal may also send the target tag corresponding to the target tag value input control to the middleware.

[0101] In step S104, the middleware receives at least the target tag value and the system identifier sent by the terminal.

[0102] The middleware may receive at least the target tag value and the system identifier sent by the terminal through the communication connection between the middleware and the terminal.

[0103] In another embodiment, the middleware may also receive the target tag corresponding to the target tag value input control sent by the terminal.

[0104] In step S105, the middleware generates a data query statement, and the data query statement carries at least the target tag value.

[0105] In another embodiment, the data query statement may also carry the target tag corresponding to the target tag value input control.

[0106] The data query statement may include an SQL data query statement, etc. The data query statement includes at least two sub - statements.

[0107] One of the sub - statements is used to: according to the target tag value involved in the data system, in the established correspondence between the label information and the data identifier set in the data system, find the target data identifier set corresponding to the target label information, and the target label information includes at least the target tag value. The data identifier set includes at least one data identifier.

[0108] In another embodiment, the target label information may also include the target tag corresponding to the target tag value input box, etc.

[0109] Another sub - statement is used to: find the data corresponding to each data identifier in the target data identifier set.

[0110] In step S106, the middleware sends the data query statement to the data system according to the system identifier.

[0111] The middleware may send the data query statement to the data system through the communication connection with the data system.

[0112] In step S107, the data system receives the data query statement.

[0113] The data system may receive the data query statement sent by the middleware through the communication connection with the middleware.

[0114] In step S108, the data system searches for a target data identifier set corresponding to target label information in the established correspondence relationship between label information and data identifier sets in the data system, where the target label information includes at least the target label value in the data query statement.

[0115] In this application, for any data system docked with middleware, multiple data are stored in the data system, each data has its own data identifier, and different data have different data identifiers. The data identifier can include the ID of the data, etc.

[0116] In this application, the fields of each data in the data system may not be modified or updated, and the field values corresponding to the fields of each data in the data system may not be modified or updated. Instead, outside the data and the fields of the data, the data identifier of the data can be bound to the label information of the data.

[0117] For example, for one of the data in the data system, the data identifier of the data can be obtained, and each field involved in the data system and the field value corresponding to each field can be obtained and used as each label involved in the data system and the label value corresponding to each label respectively. Then, each label of the data and the label value corresponding to each label of the data can be obtained.

[0118] After that, for any label involved in the data system, the label information of the data can be generated at least based on the label value corresponding to the label of the data. For example, the label of the data and the label value corresponding to the label of the data can be combined to obtain the label information of the data. Or, the label information of the data can be generated based on the label value corresponding to the label of the data. For example, the label value corresponding to the label of the data can be used as the label information of the data. Then, a data identifier set including the data identifier of the data can be generated. After that, the label information of the data and the generated data identifier set can be combined into a corresponding table entry and stored in the established correspondence relationship between label information and data identifier sets in the data system. The same applies to each of the other labels involved in the system.

[0119] Secondly, for another data in the data system, the data identifier of the other data can be obtained, and each field involved in the data system and the field value corresponding to each field can be obtained and used as each label involved in the data system and the label value corresponding to each label respectively. Then, each label of the other data and the label value corresponding to each label of the other data can be obtained.

[0120] After that, for any one of the tags involved in the data system, the tag information of another data can be generated at least according to the tag value corresponding to the tag of another data. For example, the tag of another data and the tag value corresponding to the tag of another data are combined to obtain the tag information of another data. Or, the tag information of another data can be generated according to the tag value corresponding to the tag of another data. For example, the tag value corresponding to the tag of another data is used as the tag information of another data. Then, it is determined whether there is tag information identical to the tag information of another data in the established correspondence between the tag information and the data identifier set in the data system. If there is tag information identical to the tag information of another data in the correspondence, the data identifier of another data can be added to the data identifier set corresponding to the tag information identical to the tag information of another data in the correspondence. If there is no tag information identical to the tag information of another data in the correspondence, a data identifier set including the data identifier of another data can be generated. After that, the tag information of another data and the generated data identifier set can be combined into a corresponding table entry and stored in the established correspondence between the tag information and the data identifier set in the data system.

[0121] And the same applies to all other data in the data system.

[0122] Thus, as for this data system, there is an established correspondence between the tag information and the data identifier set in the data system. Thus, target tag information can be generated. The target tag information includes at least the target tag value in the data query statement. For example, the target tag value in the data query statement can be used as the target tag information. Or, in another embodiment, the target tag information can further include the target tag corresponding to the target tag value. For example, the target tag value in the data query statement and the target tag corresponding to the target tag value can be combined into the target tag information. Then, in the established correspondence between the tag information and the data identifier set in the data system, the target data identifier set corresponding to the target tag information is searched. The target data identifier set found includes at least one data identifier. The tag value corresponding to the target tag of the data corresponding to at least one data identifier is the target tag value, or the tag value corresponding to the target tag of the data corresponding to at least one data identifier meets the target tag value (for example, there are two target tag values, one large and one small, forming an interval, and the tag value corresponding to the target tag of the data corresponding to at least one data identifier is within the interval, that is, it meets the target tag value). After that, step S109 can be executed.

[0123] In step S109, the data system searches for the data corresponding to each data identifier in the target data identifier set in the data system.

[0124] In step S110, the data system sends at least part of the found data to the middleware.

[0125] The data system can send at least part of the found data to the middleware through the communication connection between the data system and the middleware.

[0126] In step S111, the middleware receives at least part of the found data.

[0127] The middleware can receive at least part of the found data through the communication connection between the middleware and the data system.

[0128] In step S112, the middleware sends at least part of the found data to the terminal.

[0129] The middleware can send at least part of the found data to the terminal through the communication connection between the middleware and the terminal.

[0130] In step S113, the terminal receives at least part of the found data.

[0131] The terminal can receive at least part of the found data through the communication connection between the terminal and the middleware.

[0132] Furthermore, the terminal can display at least part of the found data for the upper-layer user to view, etc.

[0133] In this application, the fields involved in each data system docked by the middleware can be counted, the fields involved in each data system docked by the middleware are respectively converted into the form of labels, and at least label value input controls corresponding to each label are set in the front-end page provided by the middleware. In this way, through the front-end page, the middleware can expose the label value input controls corresponding to the labels involved in each data system docked by the middleware to the upper-layer user.

[0134] The middleware hands over the underlying query logic of each data system for each type of query index to the upper-layer user to specify, and the middleware does not need to care about the underlying query logic of each data system for each type of query index. For example, for the data system of manufacturer A, the middleware does not need to care about the underlying query logic of the data system of manufacturer A for the query index field "creator's name" (its query logic is to query not only the data created by the creator "Zhang San" but also the data created by the subordinate employees of the creator "Zhang San").

[0135] In the case where an upper-layer user needs to query data in a certain data system, the upper-layer user can input a target tag value through an input control corresponding to the target tag among multiple tags related to the data system in the front-end page, so as to indirectly specify the underlying query logic of this time for the data system.

[0136] Through the present application, the underlying query logics of the data systems of each manufacturer docked with the middleware for each type of query index are decoupled from each other, reducing the complexity of the middleware.

[0137] Enable the developers of the middleware not to be aware of the underlying query logics of the data systems of each manufacturer docked with the middleware for various types of query indexes, and not to deploy the underlying query logics of the data systems of each manufacturer docked with the middleware for each type of query index in the middleware.

[0138] In addition, in the present application, the data system does not match the data in each data index in the data system with the "field and the field value corresponding to the field" respectively. In this way, the middleware does not need to have the ability to "generate computer data query statements supported by the data systems of each manufacturer docked with the middleware (such as perceiving the form and syntax of computer data query statements, etc.)", so that the developers of the middleware do not need to master and understand the computer data query statements supported by the data systems of each manufacturer docked with the middleware.

[0139] The data system is to "at least find the data identification set corresponding to the label information according to the label value corresponding to the label involved in the data system in the corresponding relationship between the label information and the data identification set, where the label information at least includes the label value corresponding to the label involved in the data system" and "find the data corresponding to each data identification in the data identification set in the data system". The above two search actions are unified for each data system docked with the middleware and there is no difference for each data system.

[0140] In this way, the present application can reduce the technical ability requirements of the developers for the middleware developed for docking the data systems of each manufacturer, and further reduce the technical difficulty, workload and development cost of the middleware developed for docking the data systems of each manufacturer.

[0141] Secondly, after the middleware is applied online, for any data system of a vendor that the middleware is docked with, even if the upper-layer user has an update requirement for the underlying query logic of the data system of this vendor, since the underlying query logics of the middleware and the data systems of the respective vendors docked by the middleware for each type of query index are strongly coupled respectively, therefore, the developers of the middleware can be unaware of the updated underlying query logic of the data system of this vendor docked by the middleware for various types of query indexes, and can not deploy the updated underlying query logics of the data systems of the respective vendors docked by the middleware for each type of query index in the middleware. Thus, the technical difficulty, workload and maintenance cost of maintaining the middleware for docking the data systems of the respective vendors in the later stage can be reduced.

[0142] In another embodiment of the present application, the front-end page further includes a logical combination mode setting control; there are at least two target label value input controls, there are at least two target label values, and there is a one-to-one correspondence between the at least two target label value input controls and the at least two target label values; the logical combination modes include logical AND, logical OR, etc.

[0143] Logical AND: The symbol is "&&", and the result is true only when both operands are true. The logical AND operation is a short-circuit operation, that is, if the first operand can determine the result, then the second operand will not be evaluated. For the logical AND operation, if the first operand is false, then no matter what value the second operand is, the result cannot be true, which is equivalent to short-circuiting the right side.

[0144] Logical OR: If one or more operands are true, the logical OR operator returns the boolean value true; the result is false only when all operands are false.

[0145] Thus, after the upper-layer user inputs the target label values respectively according to the at least two target label value input controls, the logical combination mode between the at least two target label values can also be set according to the logical combination mode setting control. Thus, the terminal can also obtain the logical combination mode between the at least two target label values set according to the logical combination mode setting control, and then can also send the logical combination mode between the at least two target label values to the middleware.

[0146] Correspondingly, the middleware can also receive the logical combination mode between the at least two target label values, and the data query statement can also carry the logical combination mode between the at least two target label values.

[0147] For this data system, for any target tag value in the data query statement, the data system can search for data in the data system at least according to the target tag value in the manner of steps S108 and S109. For each of the other target tag values in the data query statement, the above operations are also performed. Then, according to the logical combination method between at least two target tag values, at least part of the retrieved data (including the data retrieved in the data system according to each target tag value, etc.) is logically summarized, etc., and the logically summarized data is sent to the middleware. The middleware receives the logically summarized data and sends the logically summarized data to the terminal. Then the terminal can receive the logically summarized data.

[0148] It should be noted that for the method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that the present application is not limited by the described action sequence, because according to the present application, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all optional embodiments, and the actions involved are not necessarily essential to the present application.

[0149] Referring to Figure 3 , a structural block diagram of a data processing device according to the present application is shown. The device is applied to a terminal. The device includes: a display module 11 for displaying a front-end page provided by the middleware, where the front-end page at least includes a plurality of tag value input controls, and the middleware is docked with a plurality of data systems; a first acquisition module 12 for acquiring a target tag value input according to a target tag value input control among the plurality of tag value input controls, and a second acquisition module 13 for acquiring a system identifier of a data system specified for the target tag value input control; a first sending module 14 for sending at least the target tag value and the system identifier to the middleware; so that the middleware generates a data query statement, the data query statement at least carries the target tag value, and sends the data query statement to the data system according to the system identifier; and enables the data system to search for a target data identifier set corresponding to the target tag information in the correspondence between the tag information and the data identifier set set in the data system, where the target tag information at least includes the target tag value, searches for the data corresponding to each data identifier in the target data identifier set in the data system, and sends at least part of the retrieved data to the middleware; thereby enabling the middleware to receive at least part of the retrieved data and send at least part of the retrieved data to the terminal; a first receiving module 15 for receiving at least part of the retrieved data sent by the middleware.

[0150] In an optional implementation manner, the first obtaining module includes: a receiving unit, configured to receive a triggering operation on a target tag value input control; a first obtaining unit, configured to obtain a plurality of candidate tag values for input in a target tag value input box according to the triggering operation; a display unit, configured to display the plurality of candidate tag values; and a second obtaining unit, configured to obtain a target tag value according to a selected candidate tag value among the displayed plurality of candidate tag values.

[0151] In an optional implementation manner, the front-end page further includes a logical combination mode setting control; there are at least two target tag value input controls, and there are at least two target tag values, and there is a one-to-one correspondence between the at least two target tag value input controls and the at least two target tag values; the apparatus further includes: a third obtaining module, configured to obtain a logical combination mode between at least two target tag values set according to the logical combination mode setting control; a second sending module, configured to send the logical combination mode between at least two target tag values to the middleware; so that the middleware receives the logical combination mode between at least two target tag values, and further enables a data query statement generated by the middleware to also carry the logical combination mode between at least two target tag values; and further enables the data system to perform logical summarization on the found data according to the logical combination mode between at least two target tag values after respectively finding data in the data system according to at least two target tag values, and send the logically summarized data to the middleware, so that the middleware receives the logically summarized data and sends the logically summarized data to the terminal; correspondingly, the first receiving module includes: a first receiving unit, configured to receive the logically summarized data sent by the middleware.

[0152] In an optional implementation manner, the second obtaining module includes: a searching unit, configured to search for a system identifier corresponding to the control identifier of the target tag value input control in the correspondence between the control identifiers of the tag value input controls involved in the data system and the system identifier of the data system, and use it as the system identifier of the data system specified for the target tag value input control.

[0153] In an optional implementation manner, the front-end page further includes a system identifier option control, and the system identifier option control includes the system identifiers of each data system docked with the middleware; the second obtaining module includes: a third obtaining unit, configured to obtain at least one system identifier selected according to the system identifier option control, and use it as the system identifier of the data system specified for the target tag value input control.

[0154] In an alternative implementation, the front-end page includes multiple regions, different regions are bound to the system identifiers of different data systems, and each region in each data system has a tag value input control involved therein; the second acquisition module includes: a determination unit configured to determine the region where the target tag value input control is located among the multiple regions; a fourth acquisition unit configured to acquire the system identifier bound to the region where the target tag value input control is located, and use it as the system identifier of the data system specified for the target tag value input control.

[0155] Refer to Figure 4 , a structural block diagram of a data processing device according to the present application is shown. The device is applied to middleware, and the middleware is docked with multiple data systems; the device includes: a second receiving module 21 configured to receive at least a target tag value and a system identifier sent by a terminal; the target tag value is input according to a target tag value input control among at least multiple tag value input controls included in a front-end page displayed by the terminal, and the system identifier includes the system identifier of the data system specified for the target tag value input control; the front-end page is provided by the middleware; a generation module 22 configured to generate a data query statement, the data query statement carrying at least the target tag value; a third sending module 23 configured to send the data query statement to the data system according to the system identifier; and cause the data system to search for a target data identifier set corresponding to target tag information in a correspondence relationship between tag information and a data identifier set set in the data system, the target tag information including at least the target tag value, search for data corresponding to each data identifier in the target data identifier set in the data system, and send at least part of the searched data to the middleware; a third receiving module 24 configured to receive at least part of the searched data sent by the data system; a fourth sending module 25 configured to send at least part of the searched data to the terminal, so that the terminal receives at least part of the searched data.

[0156] In an alternative implementation, the front-end page further includes a control for setting the logical combination method; there are at least two target label value input controls, and there are at least two target label values, and there is a one-to-one correspondence between the at least two target label value input controls and the at least two target label values; the device further includes: a fourth receiving module, configured to receive the logical combination method between at least two target label values sent by the terminal, and the logical combination method is set according to the control for setting the logical combination method; further, the data query statement also carries the logical combination method between at least two target label values; so that after the data system finds data in the data system according to at least two target label values respectively, according to the logical combination method between at least two target label values, logically summarize the found data, and send the logically summarized data to the middleware; correspondingly, the third receiving module includes: a second receiving unit, configured to receive the logically summarized data sent by the data system; correspondingly, the fourth sending module includes: a first sending unit, configured to send the logically summarized data to the terminal.

[0157] Referring to Figure 5 , a structural block diagram of a data processing device according to the present application is shown. The device is applied to a data system. The device includes: a fifth receiving module 31, configured to receive a data query statement; the data query statement is generated by the middleware and sent to the data system according to the system identifier of the data system. The data query statement carries at least a target label value, and the target label value and the system identifier are sent by the terminal to the middleware; the target label value is input according to a target label value input control among at least a plurality of label value input controls included in the front-end page displayed by the terminal, and the system identifier includes the system identifier of the data system specified for the target label value input control; the front-end page is provided by the middleware, and the middleware is docked with a plurality of data systems; a first searching module 32, configured to search, in the correspondence between the label information and the data identifier set already set in the data system, for the target data identifier set corresponding to the target label information, where the target label information includes at least the target label value in the data query statement; a second searching module 33, configured to search, in the data system, for the data corresponding to each data identifier in the target data identifier set; a fifth sending module 34, configured to send at least some of the found data to the middleware, so that the middleware receives at least some of the found data and sends at least some of the found data to the terminal, and the terminal receives at least some of the found data.

[0158] In an alternative implementation, the front-end page further includes a control for setting the logical combination method; there are at least two target label value input controls, and there are at least two target label values. There is a one-to-one correspondence between the at least two target label value input controls and the at least two target label values; the data query statement also carries the logical combination method between the at least two target label values; the logical combination method is set according to the control for setting the logical combination method; and it is sent by the terminal to the middleware. Correspondingly, the fifth sending module includes: a logical summarization unit for logically summarizing the retrieved data according to the logical combination method between the at least two target label values; a second sending unit for sending the logically summarized data to the middleware, so that the middleware receives the logically summarized data and sends the logically summarized data to the terminal; and enabling the terminal to receive the logically summarized data.

[0159] For Figures 3 - 5 For any one of the embodiments, the fields involved in each data system docked by the middleware can be counted, and the fields involved in each data system docked by the middleware are respectively converted into the form of labels. At least the label value input controls corresponding to each label are set in the front-end page provided by the middleware. In this way, the middleware can expose the label value input controls corresponding to the labels involved in each data system docked by the middleware to the upper-layer users through the front-end page.

[0160] The middleware hands over the underlying query logic of each data system for each type of query index to the upper-layer users for specification, and the middleware does not need to care about the underlying query logic of each data system for each type of query index. For example, for the data system of manufacturer A, the middleware does not need to care about the underlying query logic of the data system of manufacturer A for the query index field "creator's name" (its query logic is to query not only the data created by the creator "Zhang San" but also the data created by the subordinate employees of the creator "Zhang San").

[0161] When the upper-layer user needs to query data in a certain data system, the upper-layer user can input the target label value according to the target label value input control corresponding to the target label among the multiple labels involved in the data system in the front-end page, so as to indirectly specify the underlying query logic of this time for the data system.

[0162] Through the present application, the underlying query logic of each data system of each manufacturer docked by the middleware for each type of query index is decoupled, reducing the complexity of the middleware.

[0163] Enable the middleware developers to be unaware of the underlying query logics of the data systems of each vendor docked by the middleware for various types of query indexes, and the underlying query logics of the data systems of each vendor docked by the middleware for each type of query index do not need to be deployed in the middleware.

[0164] In addition, in this application, the data system does not match the data in each data index in the data system according to the field and the field value corresponding to the field. Thus, the middleware does not need to have the ability to "generate the computer data query statements supported by the data systems of each vendor docked by the middleware (such as perceiving the form and syntax of the computer data query statements, etc.)", enabling the middleware developers to not master and understand the computer data query statements supported by the data systems of each vendor docked by the middleware.

[0165] The data system is to "at least find the data identifier set corresponding to the label information according to the label value corresponding to the label involved in the data system in the correspondence between the label information and the data identifier set, where the label information at least includes the label value corresponding to the label involved in the data system" and "find the data corresponding to each data identifier in the data identifier set in the data system". The above two finding actions are unified for each data system docked by the middleware and there is no difference for each data system.

[0166] Thus, this application can reduce the technical ability requirements of the developers for the middleware used to dock the data systems of each vendor, and further reduce the technical difficulty, workload and development cost of the middleware used to dock the data systems of each vendor.

[0167] Secondly, after the middleware is put into application, for any data system of a vendor docked by the middleware, even if the upper-layer user has an update requirement for the underlying query logic of the data system of this vendor, since the middleware and the underlying query logics of the data systems of each vendor docked by the middleware for each type of query index are strongly coupled respectively, the middleware developers can be unaware of the updated underlying query logics of the data system of this vendor docked by the middleware for various types of query indexes, and the underlying query logics of the data systems of each vendor docked by the middleware for each type of updated query index do not need to be deployed in the middleware. In this way, the technical difficulty, workload and maintenance cost of the middleware used to dock the data systems of each vendor for later maintenance can be reduced.

[0168] Embodiments of the present application also provide a non - volatile readable storage medium, in which one or more modules (programs) are stored. When the one or more modules are applied to a device, the device can be caused to execute instructions for each method step in the embodiments of the present application.

[0169] Embodiments of the present application provide one or more machine - readable media, on which instructions are stored. When executed by one or more processors, the instructions cause an electronic device to execute one or more of the methods as in the above - mentioned embodiments. In the embodiments of the present application, the electronic device includes a server, a gateway, a sub - device, etc., and the sub - device is a device such as an Internet of Things device.

[0170] Embodiments of the present disclosure can be implemented as a device configured with any suitable hardware, firmware, software, or any combination thereof. The device may include a server (cluster), terminal devices such as IoT devices and other electronic devices.

[0171] Figure 6 Exemplary device 1300 that can be used to implement various embodiments in the present application is schematically shown.

[0172] For one embodiment, Figure 6 Exemplary device 1300 is shown, which has one or more processors 1302, a control module (chipset) 1304 coupled to at least one of the one or more processors 1302, a memory 1306 coupled to the control module 1304, a non - volatile memory (NVM) / storage device 1308 coupled to the control module 1304, one or more input / output devices 1310 coupled to the control module 1304, and a network interface 1312 coupled to the control module 1304.

[0173] Processor 1302 may include one or more single - core or multi - core processors. Processor 1302 may include any combination of general - purpose processors or dedicated processors (such as graphics processors, application processors, baseband processors, etc.). In some embodiments, device 1300 can act as a server device such as a gateway in the embodiments of the present application.

[0174] In some embodiments, device 1300 may include one or more computer - readable media (e.g., memory 1306 or NVM / storage device 1308) having instructions 1314 and one or more processors 1302 combined with the one or more computer - readable media and configured to execute the instructions 1314 to implement modules so as to perform the actions in the present disclosure.

[0175] For one embodiment, the control module 1304 may include any suitable interface controller to provide any suitable interface to at least one of the processor(s) 1302 and / or any suitable device or component communicating with the control module 1304.

[0176] The control module 1304 may include a memory controller module to provide an interface to the memory 1306. The memory controller module may be a hardware module, a software module, and / or a firmware module.

[0177] The memory 1306 may be used, for example, to load and store data and / or instructions 1314 for the device 1300. For one embodiment, the memory 1306 may include any suitable volatile memory, e.g., suitable DRAM. In some embodiments, the memory 1306 may include double data rate four synchronous dynamic random access memory (DDR4 SDRAM).

[0178] For one embodiment, the control module 1304 may include one or more input / output controllers to provide an interface to the NVM / storage device 1308 and the input / output device(s) 1310.

[0179] For example, the NVM / storage device 1308 may be used to store data and / or instructions 1314. The NVM / storage device 1308 may include any suitable non-volatile memory (e.g., flash memory) and / or may include any suitable non-volatile storage device(s) (e.g., one or more hard disk drives (HDDs), one or more compact discs (CDs) drives, and / or one or more digital versatile discs (DVDs) drives).

[0180] The NVM / storage device 1308 may include storage resources that are physically part of a device on which the device 1300 is mounted, or it may be accessible by the device without being part of the device. For example, the NVM / storage device 1308 may be accessed via the input / output device(s) 1310 over a network.

[0181] The input / output device(s) 1310 may provide an interface for the device 1300 to communicate with any other suitable device. The input / output device 1310 may include communication components, speech components, sensor components, etc. The network interface 1312 may provide an interface for the device 1300 to communicate over one or more networks. The device 1300 may wirelessly communicate with one or more components of a wireless network according to any of one or more wireless network standards and / or protocols, e.g., access a wireless network based on a communication standard such as WiFi, 2G, 3G, 4G, 5G, etc., or a combination thereof for wireless communication.

[0182] For one embodiment, at least one of the (one or more) processors 1302 may be logically packaged together with the logic of one or more controllers (e.g., memory controller modules) of the control module 1304. For one embodiment, at least one of the (one or more) processors 1302 may be logically packaged together with the logic of one or more controllers of the control module 1304 to form a system-in-package (SiP). For one embodiment, at least one of the (one or more) processors 1302 may be logically integrated on the same die with the logic of one or more controllers of the control module 1304. For one embodiment, at least one of the (one or more) processors 1302 may be logically integrated on the same die with the logic of one or more controllers of the control module 1304 to form a system-on-chip (SoC).

[0183] In various embodiments, the device 1300 may be, but is not limited to: a server, a desktop computing device, or a mobile computing device (e.g., a laptop computing device, a handheld computing device, a tablet computer, a netbook, etc.) and other terminal devices. In various embodiments, the device 1300 may have more or fewer components and / or a different architecture. For example, in some embodiments, the device 1300 includes one or more cameras, a keyboard, a liquid crystal display (LCD) screen (including a touch screen display), a non-volatile memory port, multiple antennas, a graphics chip, an application specific integrated circuit (ASIC), and a speaker.

[0184] An embodiment of the present application provides an electronic device, including: one or more processors; and one or more machine-readable media storing instructions thereon, which when executed by the one or more processors, cause the electronic device to execute a method as in one or more of the present application.

[0185] For the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple. For the relevant parts, refer to the partial description of the method embodiment.

[0186] Each embodiment in this specification is described in a progressive manner. The key point of each embodiment is to illustrate the differences from other embodiments. For the same or similar parts among the embodiments, reference can be made to each other.

[0187] Embodiments of the present application are described with reference to the flowcharts and / or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the present application. It should be understood that each process and / or block in the flowchart and / or block diagram, and the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable information processing terminal device to generate a machine, such that the instructions executed by the processor of the computer or other programmable information processing terminal device generate a device for implementing the functions specified in one process Figure 1 one process or multiple processes and / or blocks Figure 1 or multiple blocks.

[0188] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable information processing terminal device to work in a specific manner, such that the instructions stored in the computer-readable memory generate a manufactured article including an instruction device, and the instruction device implements the functions specified in one process Figure 1 one process or multiple processes and / or blocks Figure 1 or multiple blocks.

[0189] These computer program instructions can also be loaded onto a computer or other programmable information processing terminal device, such that a series of operation steps are executed on the computer or other programmable terminal device to generate a computer-implemented process, and thus the instructions executed on the computer or other programmable terminal device provide steps for implementing the functions specified in one process Figure 1 one process or multiple processes and / or blocks Figure 1 or multiple blocks.

[0190] Although the preferred embodiments of the embodiments of the present application have been described, those skilled in the art can make additional changes and modifications to these embodiments once they learn the basic creative concepts. Therefore, the appended claims are intended to be construed to include the preferred embodiments and all changes and modifications falling within the scope of the embodiments of the present application.

[0191] Finally, it should also be noted that in this text, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, such that a process, method, article or terminal device comprising a series of elements not only includes those elements but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or terminal device. Without further limitation, an element defined by the statement "comprising an..." does not exclude the presence of additional identical elements in the process, method, article or terminal device comprising the element.

[0192] The above has introduced in detail the data processing method and device provided by this application. Specific examples are used in this text to elaborate on the principle and implementation manner of this application. The description of the above embodiments is only used to help understand the method and its core idea of this application; at the same time, for those of ordinary skill in the art, according to the idea of this application, there will be changes in the specific implementation manner and application scope. In summary, the content of this specification should not be construed as a limitation to this application.

Claims

1. A data processing method, characterized in that, The method is applied to a terminal, and the method includes: Display a front-end page provided by a middleware. The front-end page at least includes a plurality of tag value input controls, and the middleware is docked with a plurality of data systems; Obtain a target tag value input through a target tag value input control among the plurality of tag value input controls, and obtain a system identifier of a data system specified for the target tag value input control; Send at least the target tag value and the system identifier to the middleware; so that the middleware generates a data query statement, the data query statement at least carries the target tag value, and sends the data query statement to the data system according to the system identifier; and enables the data system to find a target data identifier set corresponding to target tag information in a correspondence relationship between tag information and a data identifier set set in the data system, the target tag information at least includes the target tag value, find data corresponding to each data identifier in the target data identifier set in the data system, and send at least part of the found data to the middleware; and further enable the middleware to receive at least part of the found data and send at least part of the found data to the terminal; Receive at least part of the found data sent by the middleware.

2. The method according to claim 1, wherein The obtaining the target tag value input through the target tag value input control among the plurality of tag value input controls includes: Receive a trigger operation on the target tag value input control; Obtain a plurality of candidate tag values for input in the target tag value input box according to the trigger operation; Display the plurality of candidate tag values; Obtain the target tag value according to the selected candidate tag value among the displayed plurality of candidate tag values.

3. The method according to claim 1, wherein The front-end page further includes a logical combination mode setting control; there are at least two target tag value input controls, there are at least two target tag values, and there is a one-to-one correspondence between the at least two target tag value input controls and the at least two target tag values; The method further includes: Obtain a logical combination mode between at least two target tag values set according to the logical combination mode setting control; Send the logical combination mode between at least two target tag values to the middleware; so that the middleware receives the logical combination mode between at least two target tag values, and further enables the data query statement generated by the middleware to also carry the logical combination mode between at least two target tag values; and further enables the data system to perform logical summarization on the found data according to the logical combination mode between at least two target tag values after finding data according to at least two target tag values respectively in the data system, and send the logically summarized data to the middleware, so that the middleware receives the logically summarized data and sends the logically summarized data to the terminal; Correspondingly, the receiving at least part of the found data sent by the middleware includes: Receive the logically summarized data sent by the middleware.

4. The method according to claim 1, characterized in that, The obtaining the system identifier of the data system specified for the target tag value input control includes: In the correspondence relationship between the control identifier of the label value input control involved in the data system and the system identifier of the data system, search for the system identifier corresponding to the control identifier of the target label value input control, and use it as the system identifier of the data system specified for the target label value input control.

5. The method according to claim 1, wherein The front-end page further includes a system identifier option control, and the system identifier option control includes the system identifiers of each data system docked with the middleware; The obtaining of the system identifier of the data system specified for the target label value input control includes: Obtain at least one system identifier selected according to the system identifier option control, and use it as the system identifier of the data system specified for the target label value input control.

6. The method according to claim 1, wherein The front-end page includes multiple regions, different regions are bound to the system identifiers of different data systems, and each data system has the label value input controls involved in its respective region; The obtaining of the system identifier of the data system specified for the target label value input control includes: Determine the region where the target label value input control is located among the multiple regions; Obtain the system identifier bound to the region where the target label value input control is located, and use it as the system identifier of the data system specified for the target label value input control.

7. A data processing method, characterized in that The method is applied to middleware, and the middleware is docked with multiple data systems; the method includes: Receive the target label value and the system identifier sent by the terminal at least; the target label value is input according to the target label value input control among at least multiple label value input controls included in the front-end page displayed by the terminal, and the system identifier includes the system identifier of the data system specified for the target label value input control; the front-end page is provided by the middleware; Generate a data query statement, and the data query statement carries at least the target label value; Send the data query statement to the data system according to the system identifier; and enable the data system to search for the target data identifier set corresponding to the target label information in the correspondence relationship between the label information and the data identifier set already set in the data system, the target label information includes at least the target label value, search for the data corresponding to each data identifier in the target data identifier set in the data system, and send at least part of the data found to the middleware; Receive at least part of the data found sent by the data system; Send at least part of the data found to the terminal, so that the terminal receives at least part of the data found.

8. The method according to claim 7, characterized in that The front-end page further includes a logical combination mode setting control; there are at least two target label value input controls, there are at least two target label values, and there is a one-to-one correspondence between at least two target label value input controls and at least two target label values; The method further includes: The logical combination method between at least two target tag values sent by the receiving terminal, where the logical combination method is set according to the control for setting the logical combination method; further, the data query statement also carries the logical combination method between at least two target tag values; so that after the data system finds data in the data system according to at least two target tag values respectively, it logically summarizes the found data according to the logical combination method between at least two target tag values, and sends the logically summarized data to the middleware; Correspondingly, the receiving at least part of the found data sent by the data system includes: Receiving the logically summarized data sent by the data system; Correspondingly, the sending at least part of the found data to the terminal includes: Sending the logically summarized data to the terminal.

9. A data processing method, characterized in that The method is applied to a data system, and the method includes: Receiving a data query statement; the data query statement is generated by the middleware and sent to the data system according to the system identifier of the data system, and the data query statement carries at least a target tag value, the target tag value and the system identifier are sent by the terminal to the middleware; the target tag value is input according to the target tag value input control among at least a plurality of tag value input controls included in the front-end page displayed by the terminal, and the system identifier includes the system identifier of the data system specified for the target tag value input control; the front-end page is provided by the middleware, and the middleware is docked with a plurality of data systems; In the corresponding relationship between the tag information and the data identifier set already set in the data system, finding the target data identifier set corresponding to the target tag information, where the target tag information includes at least the target tag value in the data query statement; Finding the data corresponding to each data identifier in the target data identifier set in the data system; Sending at least part of the found data to the middleware, so that the middleware receives at least part of the found data and sends at least part of the found data to the terminal, and enables the terminal to receive at least part of the found data.

10. The method according to claim 9, wherein The front-end page further includes a control for setting the logical combination method; there are at least two target tag value input controls, there are at least two target tag values, and there is a one-to-one correspondence between at least two target tag value input controls and at least two target tag values; The data query statement also carries the logical combination method between at least two target tag values; the logical combination method is set according to the control for setting the logical combination method; And it is sent by the terminal to the middleware; Correspondingly, the sending at least part of the found data to the middleware includes: Logically summarizing the found data according to the logical combination method between at least two target tag values; Sending the logically summarized data to the middleware, so that the middleware receives the logically summarized data and sends the logically summarized data to the terminal; and enables the terminal to receive the logically summarized data.

11. An electronic device, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps of the method according to any one of claims 1 to 10.

12. A computer-readable storage medium, characterized in that, A computer-readable storage medium stores a computer program, and when the computer program is executed by the processor, it implements the steps of the method according to any one of claims 1 to 10.

Images