Method and system for processing remote invocation request, and electronic device

Abstract

The application discloses a kind of processing method and system of remote call request, electronic equipment. Among them, the method includes: receiving cascaded remote call request and the platform information of target lower-level platform;Platform information is based on finding target cascade channel, wherein, target cascade channel refers to the channel used for the information transmission between upper-level platform and target lower-level platform;Cascade remote call request is sent to target lower-level platform through target cascade channel, and cascade remote call response is generated based on request execution result;Cascade remote call response is transmitted by target lower-level platform through target cascade channel and received. The present application solves the technical problem that the upper level cannot quickly and timely obtain the relevant data of the lower level in the related art for the upper and lower cascade scene.

Description

Technical Field

[0001] This invention relates to the field of distributed processing, and more specifically, to a method and system for processing remote call requests, as well as an electronic device. Background Technology

[0002] In sectors such as administration, healthcare, and education, hierarchical relationships exist within organizations / enterprises / companies. As a higher-level regulatory body or the headquarters of a company, it's necessary to view information such as security incidents generated by subordinate departments to effectively supervise and guide their security operations. Furthermore, with the increasing emphasis on cybersecurity in recent years, higher-level units need to obtain real-time information on security incidents and the results of subordinate departments' handling of these incidents. This process introduces cascading queries: higher-level departments remotely call lower-level interfaces to query; or, the called lower-level interfaces themselves implement HTTP (Hypertext Transfer Protocol) queries.

[0003] In related technologies, for cascading application scenarios, the relevant information is often sent to the superior department by having the subordinate department upload the security events that occur. However, this method usually has a large delay due to network bandwidth limitations, and it is difficult to reflect the subordinate's follow-up handling of the corresponding security events in a timely manner.

[0004] There is currently no effective solution to the above problems. Summary of the Invention

[0005] This invention provides a method, system, and electronic device for processing remote call requests, in order to at least solve the technical problem in related technologies where the upper level cannot quickly and timely obtain relevant data from the lower level in cascading scenarios.

[0006] According to one aspect of the present invention, a method for processing remote call requests is provided, applied to a cascading remote call server deployed in an upper-level platform, wherein the upper-level platform interfaces with at least one lower-level platform, comprising: receiving a cascading remote call request and platform information of a target lower-level platform, wherein the cascading remote call request includes at least: a request link, query parameters, and data service to be queried; finding a target cascading channel based on the platform information, wherein the target cascading channel refers to a channel used for transmitting information between the upper-level platform and the target lower-level platform; sending the cascading remote call request to the target lower-level platform through the target cascading channel, wherein the target lower-level platform queries a target controller according to the request link, so that the target controller executes the data service to be queried based on the query parameters, and generates a cascading remote call response based on the request execution result; and receiving the cascading remote call response transmitted by the target lower-level platform through the target cascading channel.

[0007] Optionally, the upper-level platform further includes: a first network server, a first front-end controller, a cascading query interceptor, a request converter, and a first type of controller set; each lower-level platform further includes: a cascading remote call client, a second network server, a second front-end controller, a cascading query front-end controller, a second type of controller set, and a response converter, wherein the cascading remote call client interfaces with the cascading remote call server, the first network server is connected to the first front-end controller, the first front-end controller is connected to the cascading query interceptor, the second network server is connected to the second front-end controller, and the second type of controller set includes at least the target controller.

[0008] Optionally, before receiving the cascaded remote call request and the platform information of the target lower-level platform, the method further includes: receiving specified platform information and data to be queried input from an external device; determining the platform information of the target lower-level platform based on the specified platform information; determining the data type and query parameters of the data to be queried based on the data to be queried; generating a data query request based on the platform information, the data type, and the query parameters, and sending the data query request to the first network server of the upper-level platform, wherein the first network server transmits the data query request to the first front-end controller, the first front-end controller queries a first mapping table to obtain a first execution controller, and the first execution controller is a controller of the first type of controller set.

[0009] Optionally, after the first front-end controller queries the first mapping table to obtain the first execution controller, the method further includes: the cascading query interceptor intercepts the data query request and parses the data query request to obtain the request link, the query parameters, and the platform information; after verifying that the target lower-level platform indicated by the platform information meets the platform's legality conditions, the cascading query interceptor queries whether the cascading query function is configured in the request link; if the cascading query function is not configured in the request link, the cascading query interceptor determines that the data query request is a local query request and calls the first execution controller; if the cascading query function is configured in the request link, the cascading query interceptor determines that the data query request is a cascading query request; if the data query request is a cascading query request, the cascading query interceptor transmits the request link, the query parameters, and the platform information to the request converter.

[0010] Optionally, after the cascading query interceptor transmits the request link, the query parameters, and the platform information to the request converter, the method further includes: the request converter creating a new cascading remote call request; the request converter generating a request identifier and filling the request identifier into the unique identifier field of the cascading remote call request; the request converter filling the request link into the unique identifier field of the target interface of the cascading remote call request; the request converter filling the query parameters into the call parameter field of the cascading remote call request; and the request converter sending the cascading remote call request with the information in each field filled and the platform information to the cascading remote call server.

[0011] Optionally, the cascading remote call request includes the following fields: action type field, message type field, request unique identifier field, request details field, target interface unique identifier field, and call parameter field; the cascading remote call response includes the following fields: action type field, message type field, response unique identifier field corresponding to the cascading remote call request, execution result field, remote call result data field, call failure reason field, and controller execution time field.

[0012] Optionally, after sending the cascading remote call request to the target lower-level platform through the target cascading channel, the method further includes: the cascading remote call client receiving the cascading remote call request transmitted by the cascading remote call server; and the cascading remote call client transmitting the cascading remote call request to the cascading query front-end controller.

[0013] Optionally, after the cascading remote call client transmits the cascading remote call request to the cascading query front-end controller, the method further includes: the cascading query front-end controller parsing the cascading remote call request to obtain the request link, the query parameters, and the data service to be queried; the cascading query front-end controller querying a second mapping table based on the request link to obtain the target controller; the cascading query front-end controller using the target controller to execute the data service to be queried based on the query parameters to obtain the request execution result; and generating the cascading remote call response based on the request execution result and the request link.

[0014] Optionally, the step of generating the cascading remote call response based on the request execution result and the request link includes: the response converter creating a new cascading remote call response; the response converter filling the unique response identifier from the request execution result into the unique response identifier field of the cascading remote call response, wherein the unique response identifier refers to the response identifier corresponding to the cascading remote call request; the response converter filling the remote call result data from the request execution result into the remote call result data field of the cascading remote call response; the response converter filling the controller execution time from the request execution result into the controller execution time field of the cascading remote call response; and the response converter sending the cascading remote call response with the information filled in each field to the cascading remote call client.

[0015] Optionally, after receiving the cascaded remote call response transmitted by the target lower-level platform through the target cascaded channel, the method further includes: the cascaded remote call server parsing the cascaded remote call response to obtain the request execution result; the cascaded remote call server extracting remote call result data if the request execution result indicates successful execution; the cascaded remote call server transmitting the remote call result data to the cascaded query interceptor, and returning the remote call result data to the first network server of the upper-level platform through the cascaded query interceptor, wherein the first network server displays the remote call result data on the user terminal interface.

[0016] According to another aspect of the present invention, a method for processing remote call requests is also provided, applied to a cascading query front-end controller deployed in a target lower-level platform, wherein the cascading query front-end controller is connected to a cascading remote call client, and the cascading remote call client interfaces with a cascading remote call server of an upper-level platform, comprising: receiving a cascading remote call request transmitted by the cascading remote call client, wherein the cascading remote call request is received by the cascading remote call client through a target cascading channel; parsing the cascading remote call request to obtain a request link, query parameters, and data service to be queried; querying a target controller based on the request link, wherein the target controller executes the data service to be queried based on the query parameters to obtain a request execution result; generating a cascading remote call response based on the request execution result; and sending the cascading remote call response to the cascading remote call client, wherein the cascading remote call client transmits the cascading remote call response to the cascading remote call server of the upper-level platform through the target cascading channel.

[0017] Optionally, the target lower-level platform is further deployed with a response converter. The step of generating a cascading remote call response based on the request execution result includes: the response converter creating a new cascading remote call response; the response converter filling the unique response identifier from the request execution result into the unique response identifier field of the cascading remote call response, wherein the unique response identifier refers to the response identifier corresponding to the cascading remote call request; the response converter filling the remote call result data from the request execution result into the remote call result data field of the cascading remote call response; the response converter filling the controller execution time from the request execution result into the controller execution time field of the cascading remote call response; and the response converter sending the cascading remote call response with the filled fields to the cascading remote call client.

[0018] According to another aspect of the present invention, a remote call request processing system is also provided, comprising: an upper-level platform, including: a first network server, a first front-end controller, a cascading query interceptor, a request converter, a first type of controller set, and a cascading remote call server, wherein the cascading remote call server executes any one of the remote call request processing methods; at least one lower-level platform, each lower-level platform including: a cascading remote call client, a second network server, a second front-end controller, a cascading query front-end controller, a second type of controller set, and a response converter, wherein the cascading query front-end controller executes any one of the remote call request processing methods; the cascading remote call client interfaces with the cascading remote call server, the first network server is connected to the first front-end controller, the first front-end controller is connected to the cascading query interceptor, the first front-end controller is connected to the request converter, the request converter is connected to the cascading remote call server, the second network server is connected to the second front-end controller, and the cascading query front-end controller is connected to the cascading remote call client.

[0019] Optionally, the upper-level platform and the lower-level platform communicate via a cascading channel. The data exchange format for information transmission in the cascading channel is JSON format, and the message transmission format includes: cascading remote call request and cascading remote call response. The cascading remote call request includes the following fields: action type field, message type field, request unique identifier field, request details field, target interface unique identifier field, and call parameter field. The cascading remote call response includes the following fields: action type field, message type field, response unique identifier field corresponding to the cascading remote call request, execution result field, remote call result data field, call failure reason field, and controller execution time field.

[0020] According to another aspect of the present invention, an electronic device is also provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform a remote call request processing method as described in any one of the present invention by executing the executable instructions.

[0021] This disclosure employs the following steps: receiving a cascading remote call request and platform information of the target lower-level platform, wherein the cascading remote call request includes at least: a request link, query parameters, and the data service to be queried; then, finding the target cascading channel based on the platform information, wherein the target cascading channel refers to the channel used for transmitting information between the upper-level platform and the target lower-level platform; sending the cascading remote call request to the target lower-level platform through the target cascading channel; wherein the target lower-level platform queries the target controller according to the request link, so that the target controller executes the data service to be queried based on the query parameters; generating a cascading remote call response based on the request execution result; and finally receiving the cascading remote call response transmitted by the target lower-level platform through the target cascading channel.

[0022] In this disclosure, the remote invocation method is applied to the cascading scenario. Data is queried and uploaded through remote invocation requests and cascading channels, avoiding network latency caused by bandwidth limitations. This allows the upper-level platform to quickly obtain relevant data information from the lower-level platform and query relevant information from the lower-level platform in real time. This solves the technical problem in related technologies where the upper-level platform cannot quickly and timely obtain relevant data from the lower-level platform in the cascading scenario. Attached Figure Description

[0023] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:

[0024] Figure 1 This is a flowchart of an optional remote call request processing method according to an embodiment of the present invention;

[0025] Figure 2 This is an optional remote call request processing system architecture diagram according to an embodiment of the present invention;

[0026] Figure 3 This is a schematic diagram of a hierarchical interaction logic in existing technology;

[0027] Figure 4 This is a schematic diagram of an optional remote call request processing apparatus according to an embodiment of the present invention;

[0028] Figure 5 This is a hardware structure block diagram of an electronic device (or mobile device) according to an embodiment of the present invention for processing a remote call request. Detailed Implementation

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

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

[0031] To facilitate understanding of the present invention by those skilled in the art, some terms or nouns involved in the various embodiments of the present invention are explained below:

[0032] Full-duplex communication protocol is a communication method in which both parties can send and receive information simultaneously.

[0033] JSON, or JavaScript Object Notation for short, is a lightweight data-interchange format that uses a text format completely independent of programming languages ​​to store and represent data.

[0034] GRPC, a high-performance open-source software framework based on the HTTP 2.0 transport layer protocol, provides methods for configuring and managing network devices that support multiple programming languages.

[0035] Thrift, a remote procedure call framework, is used for developing scalable and cross-language services.

[0036] Simple Object Access Protocol (SOAP) is a lightweight, simple, XML-based data exchange protocol.

[0037] Interface Definition Language (IDL) is a language for data analysis and graphical applications and programming.

[0038] Uniform Resource Locator (URL) is a method of representing the location of information on the Internet.

[0039] The protobuf format is a data exchange format that is internally a pure binary format.

[0040] Thrift format is a data exchange format.

[0041] XML, or Extensible Markup Language, is a simple data storage language format.

[0042] avro format, a row-based storage format.

[0043] It should be noted that this embodiment of the invention applies the remote invocation process to cascading scenarios with upper and lower level platforms, enabling cascading queries and reducing implementation workload. In related technologies, there are many remote invocation frameworks, such as gRPC, Thrift, and SOAP. Existing remote invocation methods often employ specific Interface Definition Language (IDL) and code generation methods to generate client and server code. The generated server code includes two parts: network transmission-related code and a controller code skeleton for handling specific remote invocations. Specific business logic needs to be added to the controller code skeleton to implement the specific business logic. This approach can automatically generate the core code for remote invocation, allowing users to write only their own business logic, significantly improving development efficiency.

[0044] However, existing remote invocation methods cannot be applied to cascading query scenarios due to the following drawbacks: First, existing remote invocation methods are typically initiated by the client. In cascading query scenarios, the upper-level platform usually provides a public IP address, and the security devices of each lower-level platform register through this address. However, lower-level units may not be able to provide a public IP address, making it impossible to directly use existing remote invocation methods. Second, the IDL file writing language strictly defines the type of each parameter for each interface, which requires a lot of work when there are many interfaces. Third, the code generation method cannot reuse existing controllers corresponding to HTTP queries; only automatically generated controllers can be used to handle remote invocations, resulting in wasted memory and requiring additional adaptation work.

[0045] This invention improves upon existing remote invocation methods, making it applicable to various remote invocation request processing systems / products / equipment / devices. It applies remote invocation methods / software to hierarchical queries, addressing situations where there are hierarchical structures within a company or enterprise. By using remote invocation requests and cascading channels to query and upload data, the upper-level platform can quickly and promptly query the operational processing data of the lower-level platform and view the lower-level platform's handling methods for events in real time.

[0046] The present invention will now be described in detail with reference to various embodiments.

[0047] Example 1

[0048] According to an embodiment of the present invention, an embodiment of a method for processing remote call requests is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0049] Figure 1 This is a flowchart of an optional remote call request processing method according to an embodiment of the present invention, such as... Figure 1 As shown, the method includes the following steps:

[0050] Step S102: Receive the cascading remote call request and the platform information of the target lower-level platform. The cascading remote call request includes at least: the request link, query parameters, and the data service to be queried.

[0051] Step S104: Locate the target cascading channel based on platform information, where the target cascading channel refers to the channel used to transmit information between the upper-level platform and the target lower-level platform;

[0052] Step S106: The cascading remote call request is sent to the target lower-level platform through the target cascading channel. The target lower-level platform queries the target controller according to the request link, so that the target controller executes the data service to be queried based on the query parameters and generates a cascading remote call response based on the request execution result.

[0053] Step S108: Receive the cascaded remote call response transmitted by the target lower-level platform through the target cascade channel.

[0054] Through the above steps, a cascading remote call request and platform information of the target lower-level platform are received. The cascading remote call request includes at least a request link, query parameters, and the data service to be queried. Then, based on the platform information, the target cascading channel is located. The target cascading channel is the channel used for information transmission between the upper-level platform and the target lower-level platform. The cascading remote call request is sent to the target lower-level platform through the target cascading channel. The target lower-level platform queries the target controller according to the request link, so that the target controller executes the data service to be queried based on the query parameters. A cascading remote call response is generated based on the request execution result. Finally, the cascading remote call response transmitted by the target lower-level platform through the target cascading channel is received. In this embodiment, the remote call method is applied to an upper-lower cascading scenario. Data querying and uploading are performed through remote call requests and cascading channels, avoiding network latency caused by bandwidth limitations. This allows the upper-level platform to quickly obtain relevant data information from the lower-level platform and query relevant information from the lower-level platform in real time, thus solving the technical problem in related technologies where the upper-level platform cannot quickly and timely obtain relevant data from the lower-level platform in an upper-lower cascading scenario.

[0055] The embodiments of the present invention will be described in detail below with reference to the above implementation steps. The method for processing remote call requests is applied to a cascading remote call server deployed in the upper-level platform. The cascading remote call server can receive connections from lower-level platforms, send cascading query requests, and receive cascading query responses.

[0056] It should be noted that, for cascading scenarios involving upper and lower level platforms within an enterprise / company, this embodiment of the invention proposes to apply remote invocation technology to this scenario. The remote invocation request processing method of this embodiment of the invention is applied to a cascading remote invocation server deployed in the upper level platform. The upper level platform interfaces with at least one lower level platform, and the upper level platform can query and invoke data information from the lower level platform through remote invocation technology, thereby completing the upper level platform's supervision and technical guidance of the lower level platform.

[0057] It should be noted that the prerequisite for implementing cascading queries is that a network channel is set up between the upper-level platform and each corresponding lower-level platform. Remote calls are completed by transmitting protocol messages on this network channel. In this embodiment of the invention, this network channel is referred to as the cascading channel.

[0058] In this embodiment of the invention, when establishing a cascading channel, the server-side network service of the upper-level platform is enabled based on a pre-specified full-duplex communication protocol, and the network service address and port number are determined; based on the network service address and port number, the upper-level platform is controlled to establish a cascading channel with each lower-level platform.

[0059] Specifically, no specific limitation is made on the type of full-duplex communication protocol. This embodiment of the invention uses the WebSocket protocol for illustration. The cascading channel is based on the WebSocket protocol. The upper-level platform enables the WebSocket network service, and the lower-level platform connects to the upper-level platform according to the network address and the opened port number of the upper-level platform, establishing a cascading channel based on the WebSocket protocol. After the cascading channel is successfully established, messages can be exchanged between them through the cascading channel. Once the cascading channel connection is established, the upper-level platform will retain the connection in memory and bind the connection with the corresponding lower-level platform information so that the corresponding connection can be queried later based on the lower-level platform information.

[0060] In this embodiment of the invention, after establishing cascading channels between the upper-level platform and each lower-level platform, the method further includes: obtaining the lower-level unit information of the lower-level platform corresponding to the cascading channel; establishing a third mapping relationship based on the lower-level unit information and the corresponding cascading channel; and storing the third mapping relationship and the channel information of the cascading channel in a target memory. The third mapping relationship is used to characterize the relationship between the cascading channel and the corresponding lower-level unit. Storing the third mapping relationship and the cascading channel information in a designated location allows for direct retrieval of this stored information when querying the corresponding cascading channel based on the unit information later.

[0061] In this embodiment of the invention, the upper-level platform further includes: a first network server, a first front-end controller, a cascading query interceptor, a request converter, and a first type of controller set; each lower-level platform further includes: a cascading remote call client, a second network server, a second front-end controller, a cascading query front-end controller, a second type of controller set, and a response converter, wherein the cascading remote call client interfaces with the cascading remote call server, the first network server is connected to the first front-end controller, the first front-end controller is connected to the cascading query interceptor, the second network server is connected to the second front-end controller, and the second type of controller set includes at least a target controller.

[0062] It should be noted that the aforementioned first network server can receive data query requests (e.g., HTTP requests) initiated by user terminals (terminals used by higher-level entities within an enterprise / company). Upon receiving this data query request, the first front-end controller queries the specific controller through the request-controller mapping table and distributes the cascading query request to the specific controller (corresponding to the aforementioned first and second type of controller sets). The aforementioned cascading query interceptor is used to intercept cascading queries based on the URL (request link) and parameters of the data query request (e.g., HTTP request); the aforementioned request converter is used to convert the data query request (e.g., HTTP request) into a corresponding cascading remote call request; the cascading remote call client is used to connect to the upper-level cascading remote call server and return the cascading remote call response; and the response converter is used to convert the controller's execution result into a cascading query response.

[0063] It should be noted that after establishing the cascading channel between the upper and lower level platforms, data format processing is also required to enable data transmission between them. All data transmitted over a network exists as a byte stream. Therefore, before the message sender transmits data to the network, the data structure in memory needs to be converted into a byte stream, while the receiving end needs to convert the received byte stream data into a specific data structure in memory. Data exchange formats define how to convert data structures in memory into byte streams over the network, and how to convert byte streams over the network into data structures in memory. Many commonly used data exchange formats exist, such as protobuf used by gRPC, thriift used by thriift, XML used by SOAP, and others such as Avro and JSON. In this invention, messages transmitted between the upper and lower level platforms use JSON format. This JSON format is easy to read and write, easy to generate and parse, and can be directly converted to and from data structures in memory, resulting in small file size and high transmission efficiency.

[0064] After establishing the cascading channel and processing the data format, resource information and working data of the lower-level platform can be remotely accessed. The following is a illustrative explanation of a specific implementation method.

[0065] Step S102: Receive the cascading remote call request and the platform information of the target lower-level platform.

[0066] In this embodiment of the invention, before receiving the cascading remote call request and the platform information of the target lower-level platform, the process includes: receiving specified platform information and data information to be queried input from an external device; determining the platform information of the target lower-level platform based on the specified platform information; determining the data type and query parameters of the data to be queried based on the data information to be queried; generating a data query request based on the platform information, data type, and query parameters, and sending the data query request to the first network server of the upper-level platform, wherein the first network server transmits the data query request to the first front-end controller, the first front-end controller queries a first mapping table to obtain a first execution controller, and the first execution controller is a controller of a first type of controller set.

[0067] It should be noted that users on the upper-level platform can view one or more manageable lower-level platforms through the network service page of the upper-level platform. Users on the upper-level platform can specify to view information of a certain lower-level platform through selectable buttons / keys / virtual buttons on the page, and call the third mapping relationship mapping table through the platform information to establish a connection with the lower-level platform through the specific cascading channel corresponding to that lower-level platform, thereby remotely calling data from that lower-level platform.

[0068] When a user on the upper-level platform opens a web service page and specifies a lower-level platform, the request will be sent to the upper-level platform's first web server via HTTP (data query request). The request will include the data type to be queried (in URL format), query parameters, and information about the target lower-level platform (in request body or query string format). The web server will then pass the request to the cascading query front controller. The front controller will then query the URL-controller mapping table and pass the request to the controller. However, in this invention, there is a cascading query interceptor between the front controller and the specific controller, so the request will first pass through the cascading query interceptor.

[0069] In this embodiment of the invention, after the first front-end controller queries the first mapping table to obtain the first execution controller, the process includes: a cascading query interceptor intercepting a data query request and parsing the data query request to obtain a request link, query parameters, and platform information; after verifying that the target lower-level platform indicated by the platform information meets the platform's legal conditions, the cascading query interceptor queries whether the request link is configured with a cascading query function; if the request link is not configured with a cascading query function, the cascading query interceptor determines that the data query request is a local query request and calls the first execution controller; if the request link is configured with a cascading query function, the cascading query interceptor determines that the data query request is a cascading query request; and if the data query request is a cascading query request, the cascading query interceptor transmits the request link, query parameters, and platform information to the request converter.

[0070] After intercepting a data query request, the cascading query interceptor parses the request to determine the request link (which may be a URL), query parameters, and platform information of the associated target lower-level platform. If the target lower-level platform is valid and the request link is configured with cascading query functionality, the query is determined to be a cascading query; otherwise, it is a local query. If the query is a cascading query, the request link, platform information, and request parameters are passed to the request transformer; if it is a local query, the local controller is executed.

[0071] In this embodiment of the invention, after the cascading query interceptor transmits the request link, query parameters, and platform information to the request converter, the method further includes: the request converter creating a new cascading remote call request; the request converter generating a request identifier and filling the request identifier into the unique identifier field of the cascading remote call request; the request converter filling the request link into the unique identifier field of the target interface of the cascading remote call request; the request converter filling the query parameters into the call parameter field of the cascading remote call request; and the request converter sending the cascading remote call request with the information filled in each field and the platform information to the cascading remote call server.

[0072] The request converter creates a new cascading remote call request, assigns values ​​to each field of the cascading remote call request, and then sends it to the cascading remote call server.

[0073] In this embodiment of the invention, the fields included in the cascading remote call request are: action type field, message type field, request unique identifier field, request details field, target interface unique identifier field, and call parameter field; the fields included in the cascading remote call response are: action type field, message type field, response unique identifier field of the corresponding cascading remote call request, execution result field, remote call result data field, call failure reason field, and controller execution time field.

[0074] It should be noted that the above-mentioned cascading remote call request is generated through the upper-level platform terminal / web page, etc. The number of such cascading remote call requests can be one or more. This embodiment of the invention does not limit the request type (such as HTTP request). The cascading remote call request includes multiple fields such as "action" (corresponding to the above-mentioned action type field), "type" (corresponding to the above-mentioned message type field), "id" (corresponding to the above-mentioned request unique identifier field), "call" (corresponding to the above-mentioned request details field), "stub" (corresponding to the above-mentioned target interface unique identifier field), and "args" (corresponding to the above-mentioned call parameter field). The description of each field is illustrated in Table 1.

[0075] Table 1. Description of Fields in Cascaded Remote Call Request

[0076]

[0077]

[0078] The following is an example of a cascading remote call request message:

[0079]

[0080] Step S104: Locate the target cascading channel based on platform information. The target cascading channel refers to the channel used to transmit information between the upper-level platform and the target lower-level platform.

[0081] It should be noted that after the lower-level platform information and the cascading remote call request are passed to the cascading remote call server, the cascading remote call server finds the corresponding network communication connection based on the lower-level platform information, and then finds the corresponding cascading channel based on the network communication connection.

[0082] Step S106: The cascading remote call request is sent to the target lower-level platform through the target cascading channel. The target lower-level platform queries the target controller according to the request link, so that the target controller executes the data service to be queried based on the query parameters and generates a cascading remote call response based on the request execution result.

[0083] In this embodiment of the invention, after sending the cascading remote call request to the target lower-level platform through the target cascading channel, the method further includes: the cascading remote call client receiving the cascading remote call request transmitted by the cascading remote call server; and the cascading remote call client transmitting the cascading remote call request to the cascading query front-end controller.

[0084] In this embodiment of the invention, after the cascading remote call client transmits the cascading remote call request to the cascading query front-end controller, the method further includes: the cascading query front-end controller parsing the cascading remote call request to obtain the request link, query parameters, and the data service to be queried; the cascading query front-end controller querying the second mapping table based on the request link to obtain the target controller; the cascading query front-end controller using the target controller to execute the data service to be queried based on the query parameters to obtain the request execution result; and generating the cascading remote call response based on the request execution result and the request link.

[0085] In this embodiment of the invention, the step of generating a cascading remote call response based on the request execution result and the request link includes: the response converter creating a new cascading remote call response; the response converter filling the unique response identifier from the request execution result into the unique response identifier field of the cascading remote call response, wherein the unique response identifier refers to the response identifier corresponding to the cascading remote call request; the response converter filling the remote call result data from the request execution result into the remote call result data field of the cascading remote call response; the response converter filling the controller execution time from the request execution result into the controller execution time field of the cascading remote call response; and the response converter sending the cascading remote call response with the information filled in each field to the cascading remote call client.

[0086] The cascading remote call client receives the remote call response from the response converter and sends the response to the cascading remote call server in the upper-level platform via a WebSocket connection.

[0087] Step S108: Receive the cascaded remote call response transmitted by the target lower-level platform through the target cascade channel.

[0088] In this embodiment of the invention, after executing step S108, the method further includes: the cascading remote call server parsing the cascading remote call response to obtain the request execution result; the cascading remote call server extracting the remote call result data when the request execution result indicates successful execution; the cascading remote call server transmitting the remote call result data to the cascading query interceptor, and returning the remote call result data to the first network server of the upper-level platform through the cascading query interceptor, wherein the first network server displays the remote call result data on the user terminal interface.

[0089] Optionally, after receiving the cascading remote call response from the lower-level platform, the cascading remote call server checks the `status` field in the response to determine if the remote call was successful, obtaining the request execution result. Here, 0 indicates success and 1 indicates failure. For successfully executed requests, the remote call result data is extracted from the response. Finally, the request execution result and the remote call result data are passed to the cascading query interceptor. The cascading query interceptor receives the information from the cascading remote call server and passes the remote call result data to the front controller. The result can then be returned to the user terminal interface using traditional web application methods.

[0090] Current application systems may contain hundreds or even thousands of controllers. Using existing remote invocation methods, it is necessary to develop a separate set of controllers for each remote invocation request. However, this invention solves this problem. The specific controller used to handle cascading remote invocations and the controller handling HTTP are actually shared. Data is queried from the front controller's URL-controller mapping table. Therefore, it is not necessary to develop a separate set of controllers for cascading remote invocations, which can significantly reduce development costs and improve efficiency.

[0091] Example 2

[0092] The present invention will now be described in detail with reference to another embodiment. This remote call request processing method is applied to a cascading query front-end controller deployed in a target lower-level platform. The cascading query front-end controller is connected to a cascading remote call client, and the cascading remote call client interfaces with a cascading remote call server on a higher-level platform. The cascading remote call server on the higher-level platform executes the remote call request processing method described in Embodiment 1 above.

[0093] The cascading remote call server of the upper-level platform sends a cascading remote call request, which is received by the lower-level cascading remote call client and immediately passed to the lower-level cascading query front controller.

[0094] In this embodiment of the invention, the steps for the target lower-level platform to respond to the cascading call request of the upper-level platform include:

[0095] Receive cascading remote call requests transmitted by the cascading remote call client, wherein the cascading remote call request is received by the cascading remote call client through the target cascading channel;

[0096] Parse the cascading remote call request to obtain the request link, query parameters, and the data to be queried (parse the unique identifier and parameters of the target interface in the request);

[0097] Based on the request link, the target controller is queried. The target controller executes the data business to be queried based on the query parameters and obtains the request execution result (by querying the URL-controller mapping table in the front controller according to the request link (also known as the unique identifier of the target interface, i.e., URL) to find the controller corresponding to the request).

[0098] Generate a cascading remote call response based on the request execution result;

[0099] The cascading remote call response is sent to the cascading remote call client, which then transmits the cascading remote call response to the cascading remote call server of the upper-level platform through the target cascading channel.

[0100] In this embodiment, the success of the remote call is determined by checking the status field in the remote call response, thus obtaining the request execution result. 0 indicates success, and 1 indicates failure. For successfully executed requests, the remote call result data is extracted from the response. Finally, the request execution result and the remote call result data are passed to the cascading query interceptor. Upon receiving the information from the cascading remote call server, the cascading query interceptor transmits the remote call result data to the front-end controller. The result can then be returned to the user terminal interface using traditional web application methods.

[0101] In this embodiment of the invention, the target lower-level platform is further deployed with a response converter. The step of generating a cascading remote call response based on the request execution result includes: the response converter creating a new cascading remote call response; the response converter filling the unique response identifier from the request execution result into the unique response identifier field of the cascading remote call response, wherein the unique response identifier refers to the response identifier corresponding to the cascading remote call request; the response converter filling the remote call result data from the request execution result into the remote call result data field of the cascading remote call response; the response converter filling the controller execution time from the request execution result into the controller execution time field of the cascading remote call response; and the response converter sending the cascading remote call response with the information filled in each field to the cascading remote call client.

[0102] It should be noted that the cascading remote call response, like the cascading remote call request, contains multiple fields: "action" (corresponding to the action type field mentioned above), "type" (corresponding to the message type field mentioned above), "id" (corresponding to the unique identifier field of the request mentioned above), "call" (corresponding to the request details field mentioned above), "stub" (corresponding to the unique identifier field of the target interface mentioned above), and "args" (corresponding to the call parameter field mentioned above).

[0103] The specific response message example is as follows:

[0104] {

[0105] "act ion":"rpc"

[0106] "type": "response",

[0107] "id":"xxx"

[0108] "status":0,

[0109] “data”:{…},

[0110] “durat ion”:100

[0111] “message”:“

[0112] }

[0113] The above implementation applies the remote invocation method to cascading scenarios. By querying and uploading data through remote invocation requests and cascading channels, network latency caused by bandwidth limitations is avoided. This allows the upper-level platform to quickly obtain relevant data information from the lower-level platform and query relevant information from the lower-level platform in real time. Furthermore, in this embodiment, the specific controller for handling cascading remote invocations and the controller for handling network response requests are shared, eliminating the need to develop a separate controller for cascading remote invocations. This significantly reduces development costs and improves work efficiency.

[0114] The invention will now be described in conjunction with another alternative embodiment.

[0115] Example 3

[0116] This embodiment provides a remote call request processing system, wherein each implementation unit included in the remote call request processing system corresponds to each implementation step in Embodiment 1.

[0117] Figure 2 This is an optional remote call request processing system architecture diagram according to an embodiment of the present invention, such as... Figure 2 As shown, the system for processing this remote call request includes:

[0118] The upper-level platform includes: a first network server, a first front-end controller, a cascading query interceptor, a request converter, and a first-class controller set. Figure 2 The diagram illustrates controller 1, controller 2... controller N, each controller having corresponding business logic), and a cascaded remote call server, wherein the cascaded remote call server executes any one of the remote call request processing methods in Embodiment 1;

[0119] At least one subordinate platform, each subordinate platform comprising: a cascading remote call client, a second network server, a second front-end controller, a cascading query front-end controller, and a set of second-class controllers ( Figure 2The diagram illustrates controllers 1, 2, ..., N, each executing corresponding business logic and a response converter. The cascading query front-end controller handles any remote call request. The cascading remote call client interfaces with the cascading remote call server; the first network server connects to the first front-end controller; the first front-end controller connects to the cascading query interceptor; the first front-end controller connects to the request converter; the request converter connects to the cascading remote call server; the second network server connects to the second front-end controller; and the cascading query front-end controller connects to the cascading remote call client.

[0120] In this embodiment of the invention, the upper-level platform and the lower-level platform communicate using a cascading channel. The data exchange format for information transmission in the cascading channel is JSON format, and the message transmission format includes: cascading remote call request and cascading remote call response. The cascading remote call request includes the following fields: action type field, message type field, request unique identifier field, request details field, target interface unique identifier field, and call parameter field. The cascading remote call response includes the following fields: action type field, message type field, response unique identifier field of the corresponding cascading remote call request, execution result field, remote call result data field, call failure reason field, and controller execution time field.

[0121] like Figure 2 As shown, the first front controller queries the URL-controller mapping table to find controllers that can handle data processing; for example... Figure 2 As shown, the cascading query front controller can also query another URL-controller mapping table, which can query controllers that can handle data business.

[0122] Before performing cascading queries, a cascading channel needs to be established between the upper-level platform and the lower-level platform. In this embodiment of the invention, the cascading channel is based on the WebSocket protocol. The upper-level platform enables WebSocket network services, and the lower-level platform connects to the upper-level platform based on its network address and the opened port number, thus establishing a cascading channel based on the WebSocket protocol. After the channel is successfully established, messages can be exchanged between them through this channel. Once the channel connection is established, the upper-level platform will retain the connection in memory and bind the connection to the corresponding lower-level unit information to facilitate subsequent queries of the corresponding connection based on the lower-level information.

[0123] It should be noted that all data exists in the form of byte streams during network transmission. Therefore, before the message sender sends the data to the network, it needs to convert the data structure in memory into the form of a byte stream, while the receiving end needs to convert the received byte stream data into a specific data structure in memory.

[0124] Data exchange formats define how to convert in-memory data structures into byte streams over a network, and vice versa. Many commonly used data exchange formats exist, such as protobuf used by gRPC, thriift used by thriift, XML used by SOAP, and others like Avro and JSON. In this invention, messages transmitted between upper and lower level platforms use JSON format, which is easy to read, write, generate, and parse. It can be directly converted to and from in-memory data structures, is small in size, and has high transmission efficiency.

[0125] In this embodiment of the invention, the entire cascading remote call process includes three parts: the upper-level platform triggering the remote call, the lower-level platform processing the remote call, and the upper-level platform receiving the response from the lower-level platform.

[0126] The upper-level platform triggers a remote call: When a user on the upper-level platform opens a page and specifies a lower-level platform, the data type to be queried (in URL form), query parameters, and information about the target lower-level platform (in request body or query string form) are sent to the web server of the upper-level platform (corresponding to the first network server mentioned above) via HTTP. The web server passes the request to the front controller (corresponding to the first front controller mentioned above), and then the front controller queries the URL-controller mapping table and passes the request to the cascading query interceptor.

[0127] When the cascading query interceptor receives a call request, it performs the following operations: parses the query data URL (corresponding to the above request connection), query parameters, and target lower-level platform; if the lower-level platform is valid and the URL is configured with cascading query functionality, it determines that the query is a cascading query; otherwise, it is a local query; if the query is a cascading query, it passes the URL, lower-level platform, and request parameters to the request converter; if it is a local query, it executes the local controller.

[0128] After receiving the request URL, lower-level platform, and request parameters from the cascading query interceptor, the request converter performs the following operations: Create a new cascading remote call request; generate a unique identifier for the request (corresponding to the request identifier mentioned above) and fill it into the id field (corresponding to the unique identifier field mentioned above); fill the URL as the unique identifier of the target interface into the stub field of the request (corresponding to the unique identifier field of the target interface mentioned above); fill the query parameters into the args field of the request (corresponding to the call parameter field mentioned above); and pass the lower-level platform and the cascading remote call request to the cascading remote call server. Upon receiving the lower-level platform and the corresponding cascading remote call request, the cascading remote call server performs the following operations: locate the corresponding WebSocket connection based on the lower-level platform information; send the remote call request to the target lower-level platform through the found WebSocket connection; and wait for the target lower-level platform to process the remote call and return the corresponding remote call response.

[0129] The lower-level platform handles remote calls: The upper-level cascaded remote call server sends a cascaded remote call request. The lower-level platform's cascaded remote call client receives the request and immediately passes it to the lower-level platform's cascaded query front controller: parses the unique identifier and parameters of the target interface in the request; queries the URL-controller mapping table in the front controller based on the unique identifier of the target interface (i.e., URL) to find the controller corresponding to the request; executes the corresponding controller using the parameters in the request; monitors whether the controller execution is successful; records the time consumed by the controller execution; and passes the request's ID field, whether the controller execution was successful, the controller execution time, and the controller execution result to the response transformer.

[0130] After receiving the information from the cascading query front controller, the response converter performs the following operations: Creates a new remote call response; fills the success / failure status information into the response's status field (0 for success, 1 for failure); if successful, fills the controller execution result into the response's data field (corresponding to the remote call result data field mentioned above); fills the corresponding request ID into the response's id field (corresponding to the response's unique identifier field mentioned above); fills the controller execution time into the response's duration field (corresponding to the controller execution time field mentioned above); and passes the response to the cascading remote call client. The cascading remote call client receives the remote call response from the response converter and sends it to the server via a WebSocket connection.

[0131] The upper level receives the response from the lower level: When the upper level cascaded remote call server receives the remote call response sent by the lower level, it performs the following operations: It checks the status field of the response to determine whether the remote call was successful, with 0 indicating success and otherwise failure; if the execution is successful, it extracts the execution result information (data field value) from the response; and it passes the success status and execution result to the cascaded query interceptor.

[0132] The cascading query interceptor receives information from the cascading remote call server, passes the results to the front controller, and then returns the results to the upper-level platform user interface via the web server.

[0133] Figure 3 This is a schematic diagram of a cascaded interaction logic in existing technology, such as... Figure 3 As shown, in the prior art, when a user accesses a page on this platform via HTTP, the HTTP request is received by the web server and passed to the front controller. The front controller receives the HTTP request from the web server, parses the URL and request parameters, finds the corresponding controller through the URL carried in the request, and passes the parameters to that controller. The controller will use the received parameters to execute the corresponding business logic operation, complete the request processing, obtain the processing result, and return the result to the user interface in the opposite direction.

[0134] This invention, based on the cascading interaction method in related technologies, adds the following components: a cascading query interceptor, a request converter, a cascading remote call server, a cascading query front-end controller, a response converter, and a cascading remote call client. Data is queried and uploaded through remote call requests and cascading channels, avoiding network latency caused by bandwidth limitations. This allows the upper-level platform to quickly obtain relevant data information from the lower-level platform and simultaneously query relevant information from the lower-level platform in real time. Furthermore, in this invention, the specific controller for handling cascading remote calls and the controller for handling network response requests are shared, eliminating the need for developing a separate controller for cascading remote calls, significantly reducing development costs and improving work efficiency.

[0135] The invention will now be described in conjunction with another alternative embodiment.

[0136] Example 4

[0137] This application also provides a remote call request processing apparatus. It should be noted that this remote call request processing apparatus can be used to execute the remote call request processing method in Embodiment 1 above. Each implementation unit included in this processing apparatus corresponds to each implementation step in Embodiment 1 above.

[0138] Figure 4 This is a schematic diagram of an optional remote call request processing apparatus according to an embodiment of the present invention. This apparatus is applied to a cascaded remote call server deployed in a higher-level platform, such as... Figure 4 As shown, the remote call request processing device includes: a first receiving unit 40, a search unit 42, a first sending unit 44, and a second receiving unit 46, wherein,

[0139] The first receiving unit 40 is used to receive cascaded remote call requests and platform information of the target lower-level platform. The cascaded remote call request includes at least: a request link, query parameters, and data service to be queried.

[0140] The lookup unit 42 is used to look up the target cascade channel based on platform information, wherein the target cascade channel refers to the channel used to transmit information between the upper-level platform and the target lower-level platform.

[0141] The first sending unit 44 is used to send the cascaded remote call request to the target lower-level platform through the target cascade channel. The target lower-level platform queries the target controller according to the request link, so that the target controller executes the data service to be queried based on the query parameters and generates a cascaded remote call response based on the request execution result.

[0142] The second receiving unit 46 is used to receive the cascaded remote call response transmitted by the target lower-level platform through the target cascade channel.

[0143] The aforementioned remote call request processing device receives the cascaded remote call request and the platform information of the target lower-level platform through the first receiving unit 40. The cascaded remote call request includes at least: a request link, query parameters, and the data service to be queried. The lookup unit 42 searches for the target cascaded channel based on the platform information. The target cascaded channel refers to the channel used for transmitting information between the upper-level platform and the target lower-level platform. The first sending unit 44 sends the cascaded remote call request to the target lower-level platform through the target cascaded channel. The target lower-level platform queries the target controller based on the request link, causing the target controller to execute the data service to be queried based on the query parameters and generate a cascaded remote call response based on the request execution result. The second receiving unit 46 receives the cascaded remote call response transmitted by the target lower-level platform through the target cascaded channel. In this embodiment, the remote invocation method is applied to the cascading scenario. Data is queried and uploaded through remote invocation requests and cascading channels, avoiding network latency caused by bandwidth limitations. This allows the upper-level platform to quickly obtain relevant data information from the lower-level platform and query relevant information from the lower-level platform in real time. This solves the technical problem in related technologies where the upper-level platform cannot quickly and timely obtain relevant data from the lower-level platform in the cascading scenario.

[0144] Optionally, the upper-level platform further includes: a first network server, a first front-end controller, a cascading query interceptor, a request converter, and a first-class controller set; each lower-level platform further includes: a cascading remote call client, a second network server, a second front-end controller, a cascading query front-end controller, a second-class controller set, and a response converter, wherein the cascading remote call client interfaces with the cascading remote call server, the first network server is connected to the first front-end controller, the first front-end controller is connected to the cascading query interceptor, the second network server is connected to the second front-end controller, and the second-class controller set includes at least the target controller.

[0145] Optionally, the remote call request processing device further includes: a first receiving module, used to receive specified platform information and query data information input by an external device; a first determining module, used to determine the platform information of the target lower-level platform based on the specified platform information; a second determining module, used to determine the data type and query parameters of the query data based on the query data information; and a first generating module, used to generate a data query request based on the platform information, data type, and query parameters, and send the data query request to a first network server of the upper-level platform, wherein the first network server transmits the data query request to a first front-end controller, the first front-end controller queries a first mapping table to obtain a first execution controller, and the first execution controller is a controller of a first type of controller set.

[0146] Optionally, the remote call request processing device further includes: a first interception module, used for the cascading query interceptor to intercept the data query request and parse the data query request to obtain the request link, query parameters, and platform information; a first query module, used for the cascading query interceptor to query whether the request link is configured with cascading query function after verifying that the target lower-level platform indicated by the platform information meets the platform's legal conditions; a first call module, used for the cascading query interceptor to determine that the data query request is a local query request and call the first execution controller when the cascading query interceptor does not configure cascading query function in the request link; a third determination module, used for the cascading query interceptor to determine that the data query request is a cascading query request when the cascading query interceptor configures cascading query function in the request link; and a first transmission module, used for the cascading query interceptor to transmit the request link, query parameters, and platform information to the request converter when the data query request is a cascading query request.

[0147] Optionally, the remote call request processing device further includes: a first creation module, used to request the converter to create a new cascading remote call request; a first filling module, used to request the converter to generate a request identifier and fill the request identifier into the unique identifier field of the cascading remote call request; a second filling module, used to request the converter to fill the request link into the unique identifier field of the target interface of the cascading remote call request; a third filling module, used to request the converter to fill the query parameters into the call parameter field of the cascading remote call request; and a first sending module, used to request the converter to send the cascading remote call request with the information of each field filled and the platform information to the cascading remote call server.

[0148] Optionally, the fields included in the cascading remote call request are: action type field, message type field, request unique identifier field, request details field, target interface unique identifier field, and call parameter field; the fields included in the cascading remote call response are: action type field, message type field, response unique identifier field of the corresponding cascading remote call request, execution result field, remote call result data field, call failure reason field, and controller execution time field.

[0149] Optionally, the first sending unit includes: a second receiving module, used for the cascading remote call client to receive the cascading remote call request transmitted by the cascading remote call server; and a second transmitting module, used for the cascading remote call client to transmit the cascading remote call request to the cascading query front-end controller.

[0150] Optionally, the first sending unit further includes: a first parsing module, used for cascading query front-end controller parsing cascading remote call requests to obtain request links, query parameters, and data services to be queried; a second query module, used for cascading query front-end controller querying a second mapping table based on the request links to obtain the target controller; a first execution module, used for cascading query front-end controller using the target controller to execute the data services to be queried based on the query parameters to obtain the request execution result; and a second generation module, used for generating cascading remote call responses based on the request execution result and the request links.

[0151] Optionally, the second generation module includes: a first creation submodule, used by the response converter to create a new cascading remote call response; a first filling submodule, used by the response converter to fill the response unique identifier from the request execution result into the response unique identifier field of the cascading remote call response, wherein the response unique identifier refers to the response identifier of the corresponding cascading remote call request; a second filling submodule, used by the response converter to fill the remote call result data from the request execution result into the remote call result data field of the cascading remote call response; a third filling submodule, used by the response converter to fill the controller execution time from the request execution result into the controller execution time field of the cascading remote call response; and a first sending submodule, used by the response converter to send the cascading remote call response with the information filled in each field to the cascading remote call client.

[0152] Optionally, the remote call request processing device further includes: a second parsing module, used by the cascading remote call server to parse the cascading remote call response and obtain the request execution result; a first extraction module, used by the cascading remote call server to extract the remote call result data when the request execution result indicates successful execution; and a first return module, used by the cascading remote call server to transmit the remote call result data to the cascading query interceptor, and to return the remote call result data to the first network server of the upper-level platform through the cascading query interceptor, wherein the first network server displays the remote call result data on the user terminal interface.

[0153] Optionally, the remote call request processing device further includes: a first activation module, used to activate the server network service of the upper-level platform based on a pre-specified full-duplex communication protocol, and determine the network service address and the activation port number; and a second activation module, used to control the upper-level platform to establish a cascading channel with each lower-level platform based on the network service address and the activation port number.

[0154] Optionally, the remote call request processing device further includes: a first acquisition module, used to acquire the lower-level unit information of the lower-level platform corresponding to the cascaded channel; a first establishment module, used to establish a third mapping relationship based on the lower-level unit information and the corresponding cascaded channel; and a first storage module, used to store the third mapping relationship and the channel information of the cascaded channel in the target memory.

[0155] According to another aspect of the present invention, a remote call request processing apparatus is also provided, applied to a cascading query front-end controller deployed in a target lower-level platform, wherein the cascading query front-end controller is connected to a cascading remote call client, and the cascading remote call client interfaces with a cascading remote call server of an upper-level platform, comprising: a third receiving unit, configured to receive a cascading remote call request transmitted by the cascading remote call client, wherein the cascading remote call request is received by the cascading remote call client through a target cascading channel; a parsing unit, configured to parse the cascading remote call request to obtain a request link, query parameters, and data service to be queried; a query unit, configured to query the target controller based on the request link, wherein the target controller executes the data service to be queried based on the query parameters to obtain a request execution result; a generating unit, configured to generate a cascading remote call response based on the request execution result; and a second sending unit, configured to send the cascading remote call response to the cascading remote call client, wherein the cascading remote call client transmits the cascading remote call response to the cascading remote call server of the upper-level platform through the target cascading channel.

[0156] Optionally, the target lower-level platform also deploys a response converter, the generation unit including: a second creation module, used by the response converter to create a new cascading remote call response; a fourth filling module, used by the response converter to fill the response unique identifier in the request execution result into the response unique identifier field of the cascading remote call response, wherein the response unique identifier refers to the response identifier of the corresponding cascading remote call request; a fifth filling module, used by the response converter to fill the remote call result data in the request execution result into the remote call result data field of the cascading remote call response; a sixth filling module, used by the response converter to fill the controller execution time in the request execution result into the controller execution time field of the cascading remote call response; and a second sending module, used by the response converter to send the cascading remote call response with the information of each field filled to the cascading remote call client.

[0157] The aforementioned remote call request processing device may further include a processor and a memory. The aforementioned first receiving unit 40, search unit 42, first sending unit 44, second receiving unit 46, etc., are all stored in the memory as program units, and the processor executes the aforementioned program units stored in the memory to realize the corresponding functions.

[0158] The aforementioned processor contains a kernel, which retrieves the corresponding program units from memory. One or more kernels can be configured, and cascading remote call requests can be processed by adjusting kernel parameters.

[0159] The aforementioned memory may include non-permanent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash memory, and the memory includes at least one memory chip.

[0160] According to another aspect of the present invention, an electronic device is also provided, including: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to a processing method for executing a remote call request of any one of the executable instructions.

[0161] According to another aspect of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored computer program, wherein a method for processing a remote call request that controls the device where the computer-readable storage medium is located to execute any one of the following when the computer program is running is provided.

[0162] Figure 5 This is a hardware structure block diagram of an electronic device (or mobile device) according to an embodiment of the present invention for processing a remote call request. Figure 5 As shown, the electronic device may include one or more processors 502 (shown as 502a, 502b, ..., 502n in the figure) 502 (processor 502 may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 504 for storing data. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, a keyboard, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 5 The structure shown is for illustrative purposes only and does not limit the structure of the electronic device described above. For example, the electronic device may also include components that are more... Figure 5 The more or fewer components shown, or having the same Figure 5 The different configurations shown.

[0163] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0164] In the above embodiments of the present invention, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0165] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between units or modules may be electrical or other forms.

[0166] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0167] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0168] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0169] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method for processing remote invocation requests, characterized in that, A cascading remote call server deployed in a higher-level platform, wherein the higher-level platform interfaces with at least one lower-level platform, including: Receive cascading remote call requests and platform information of the target lower-level platform, wherein the cascading remote call request includes at least: a request link, query parameters, and data service to be queried; The target cascading channel is located based on the platform information, wherein the target cascading channel refers to the channel used for transmitting information between the upper-level platform and the target lower-level platform; The cascading remote call request is sent to the target lower-level platform through the target cascading channel. The target lower-level platform queries the target controller according to the request link, so that the target controller executes the data service to be queried based on the query parameters, and generates a cascading remote call response based on the request execution result, so that the controller used to process the cascading remote call request and the controller used to process the network response request are shared. Receive the cascaded remote call response transmitted by the target lower-level platform through the target cascaded channel; The upper-level platform further includes: a first network server, a first front-end controller, a cascading query interceptor, a request converter, and a first-class controller set; each lower-level platform further includes: a cascading remote call client, a second network server, a second front-end controller, a cascading query front-end controller, a second-class controller set, and a response converter; Before receiving the cascading remote call request and the platform information of the target lower-level platform, it also includes: Receive specified platform information and data to be queried from external devices; Based on the specified platform information, determine the platform information of the target subordinate platform; Based on the data to be queried, determine the data type and query parameters of the data to be queried; Based on the platform information, the data type, and the query parameters, a data query request is generated and sent to the first network server of the upper-level platform. The first network server transmits the data query request to the first front-end controller. The first front-end controller queries the first mapping table to obtain the first execution controller. The first execution controller is a controller of the first type of controller set. After the first front-end controller queries the first mapping table to obtain the first execution controller, the process further includes: The cascading query interceptor intercepts the data query request and parses the data query request to obtain the request link, the query parameters, and the platform information; After verifying that the target lower-level platform indicated by the platform information meets the platform's legality conditions, the cascading query interceptor checks whether the cascading query function is configured in the request link. If the cascading query interceptor does not configure the cascading query function in the request link, it determines that the data query request is a local query request and calls the first execution controller. When the cascading query interceptor is configured with the cascading query function in the request link, it determines that the data query request is a cascading query request. When the data query request is a cascading query request, the cascading query interceptor transmits the request link, the query parameters, and the platform information to the request converter.

2. The processing method according to claim 1, characterized in that, The cascading remote call client interfaces with the cascading remote call server, the first network server is connected to the first front-end controller, the first front-end controller is connected to the cascading query interceptor, the second network server is connected to the second front-end controller, and the second type of controller set includes at least the target controller.

3. The processing method according to claim 2, characterized in that, After sending the cascaded remote call request to the target lower-level platform through the target cascaded channel, the method further includes: The cascading remote call client receives the cascading remote call request transmitted by the cascading remote call server; The cascading remote call client transmits the cascading remote call request to the cascading query front-end controller.

4. The processing method according to claim 3, characterized in that, After the cascading remote call client transmits the cascading remote call request to the cascading query front-end controller, the method further includes: The cascading query front-end controller parses the cascading remote call request to obtain the request link, the query parameters, and the data service to be queried. The cascading query front-end controller queries the second mapping table based on the request link to obtain the target controller; The cascading query front-end controller uses the target controller to execute the data service to be queried based on the query parameters to obtain the request execution result; Based on the request execution result and the request link, the cascading remote call response is generated.

5. The processing method according to claim 4, characterized in that, The step of generating the cascading remote call response based on the request execution result and the request link includes: The response converter creates a new cascaded remote call response; The response converter fills the unique response identifier in the request execution result into the unique response identifier field of the cascaded remote call response, wherein the unique response identifier refers to the response identifier corresponding to the cascaded remote call request; The response converter fills the remote call result data from the request execution result into the remote call result data field of the cascaded remote call response; The response converter fills the controller execution time in the request execution result into the controller execution time field of the cascaded remote call response; The response converter sends the cascaded remote call response, with all fields filled in, to the cascaded remote call client.

6. A method for processing remote invocation requests, characterized in that, A cascading query front-end controller deployed in a target lower-level platform, wherein the cascading query front-end controller is connected to a cascading remote call client, and the cascading remote call client interfaces with a cascading remote call server of the upper-level platform, including: Receive a cascading remote call request transmitted by the cascading remote call client, wherein the cascading remote call request is received by the cascading remote call client through the target cascading channel; Parse the cascading remote call request to obtain the request link, query parameters, and the data service to be queried; Based on the requested link, the target controller is queried, wherein the target controller executes the data service to be queried based on the query parameters to obtain the request execution result; Based on the result of the request execution, a cascading remote call response is generated to share the controller used to process the cascading remote call request and the controller used to process the network response request. The cascading remote call response is sent to the cascading remote call client, wherein the cascading remote call client transmits the cascading remote call response to the cascading remote call server of the upper-level platform through the target cascading channel; The upper-level platform further includes: a first network server, a first front-end controller, a cascading query interceptor, a request converter, and a first-class controller set; each lower-level platform further includes: a cascading remote call client, a second network server, a second front-end controller, a cascading query front-end controller, a second-class controller set, and a response converter; Receiving the cascading remote call request transmitted by the cascading remote call client also includes: Receive specified platform information and data to be queried from external devices; Based on the specified platform information, determine the platform information of the target subordinate platform; Based on the data to be queried, determine the data type and query parameters of the data to be queried; Based on the platform information, the data type, and the query parameters, a data query request is generated and sent to the first network server of the upper-level platform. The first network server transmits the data query request to the first front-end controller. The first front-end controller queries the first mapping table to obtain the first execution controller. The first execution controller is a controller of the first type of controller set. After the first front-end controller queries the first mapping table to obtain the first execution controller, the process further includes: The cascading query interceptor intercepts the data query request and parses the data query request to obtain the request link, the query parameters, and the platform information; After verifying that the target lower-level platform indicated by the platform information meets the platform's legality conditions, the cascading query interceptor checks whether the cascading query function is configured in the request link. If the cascading query interceptor does not configure the cascading query function in the request link, it determines that the data query request is a local query request and calls the first execution controller. When the cascading query interceptor is configured with the cascading query function in the request link, it determines that the data query request is a cascading query request. When the data query request is a cascading query request, the cascading query interceptor transmits the request link, the query parameters, and the platform information to the request converter.

7. A remote call request processing system, characterized in that, include: The upper-level platform includes: a first network server, a first front-end controller, a cascading query interceptor, a request converter, a first type of controller set, and a cascading remote call server, wherein the cascading remote call server executes the remote call request processing method according to any one of claims 1 to 5; At least one lower-level platform, each of the lower-level platforms comprising: a cascading remote call client, a second network server, a second front-end controller, a cascading query front-end controller, a second set of controllers, and a response converter, wherein the cascading query front-end controller executes the remote call request processing method of claim 6; The cascading remote call client interfaces with the cascading remote call server. The first network server is connected to the first front-end controller. The first front-end controller is connected to the cascading query interceptor. The first front-end controller is connected to the request converter. The request converter is connected to the cascading remote call server. The second network server is connected to the second front-end controller. The cascading query front-end controller is connected to the cascading remote call client.

8. An electronic device, characterized in that, include: processor; as well as Memory for storing the executable instructions of the processor; The processor is configured to execute the remote call request processing method according to any one of claims 1 to 5 by executing the executable instructions.

Images