CN116662025A - Request response method, device, equipment and storage medium - Google Patents

Abstract

The disclosure provides a request response method, a request response device, request response equipment and a storage medium, and the request response method, the request response device, the request response equipment and the storage medium can be applied to the technical field of information security and the technical field of finance. The method comprises the following steps: responding to an access request initiated by a first node to a second node, and acquiring first interface information of the first node and second interface information of the second node, wherein the first interface information represents interface information required to be called by the first node for sending the access request to the second node, and the second interface information represents interface information required to be called by the second node for receiving the access request of the first node; acquiring target interface calling authority information from a management platform according to the first interface information and the second interface information, wherein the target interface calling authority information is configured according to the data interaction requirement between the first node and the second node; and executing the processing operation of the access request according to the permission information of the target interface.

Description

Request response method, device, equipment and storage medium

Technical Field

The present disclosure relates to the field of information security technology and the field of financial technology, and in particular, to a request response method, apparatus, device, medium, and program product.

Background

With the development of digitization technology, micro-service architecture has gradually become the mainstream architecture of applications. In the related art, based on the application of the micro-service architecture, maintainability, testability and deployability of the service can be improved by splitting the service.

In the process of realizing the inventive concept, the inventor discovers that identification of interface call authorities among micro-service internal nodes mostly needs to write authority identification codes into node codes in a development stage, so that the problem that the coupling of the codes is high and real-time dynamic change is difficult to realize exists.

Disclosure of Invention

In view of the foregoing, the present disclosure provides a request response method, apparatus, device, medium, and program product.

According to a first aspect of the present disclosure, there is provided a request response method, including: responding to an access request initiated by a first node to a second node, and acquiring first interface information of the first node and second interface information of the second node, wherein the first interface information represents interface information required to be called by the first node for sending the access request to the second node, and the second interface information represents interface information required to be called by the second node for receiving the access request of the first node; acquiring target interface calling authority information from a management platform according to the first interface information and the second interface information, wherein the target interface calling authority information is configured according to the data interaction requirement between the first node and the second node; and executing the processing operation of the access request according to the permission information of the target interface.

According to an embodiment of the present disclosure, the target interface call permission information includes interface interaction node information; and executing the processing operation of the access request according to the permission information of the target interface, wherein the processing operation comprises the following steps: according to the interface interaction node information, carrying out interface calling authority identification on the access request to obtain an identification result; and executing the processing operation of the access request according to the identification result.

According to an embodiment of the disclosure, the interface interaction node information includes interface interaction period information, and the interface interaction period information characterizes period information of which the first interface information and the second interface information have interaction rights; according to the interface interaction node information, carrying out interface calling authority identification on the access request to obtain an identification result, wherein the method comprises the following steps: determining calling period information of calling the first interface information and the second interface information by the access request according to the access request; and carrying out interface calling authority identification on the access request according to the interface interaction time period information and the calling time period information to obtain an identification result.

According to an embodiment of the present disclosure, the request response method further includes: generating request processing notification information under the condition that the identification result characterizes that the access request is abnormal; and sending the request processing notification information to the management platform.

According to an embodiment of the present disclosure, the request response method further includes: and changing the node attribute information of the first node and the second node according to the interface calling authority information to obtain changed node attribute information.

According to an embodiment of the present disclosure, the request response method further includes: obtaining node attribute information according to the first node and the second node; and sending the node attribute information to a management platform.

According to an embodiment of the present disclosure, the node attribute information includes node identification information, node interface information, and node operation state information; sending node attribute information to a management platform, including: and sending node identification information, node interface information and node running state information to the management platform, wherein the node interface information and the node running state information are used for determining the data interaction requirement between the first node and the second node, and the node identification information is used for determining the first node and the second node from a plurality of nodes under the condition that the management platform sends target interface calling authority information to the first node and the second node.

A second aspect of the present disclosure provides a request response device, including: the first acquisition module is used for responding to the received access request initiated by the first node to the second node and acquiring first interface information of the first node and second interface information of the second node, wherein the first interface information represents interface information required to be called by the first node for sending the access request to the second node, and the second interface information represents interface information required to be called by the second node for receiving the access request of the first node; the second acquisition module is used for acquiring target interface calling authority information from the management platform according to the first interface information and the second interface information, wherein the target interface calling authority information is configured according to the data interaction requirement between the first node and the second node; and the execution module is used for executing the processing operation of the access request according to the interface calling authority information.

A third aspect of the present disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method described above.

A fourth aspect of the present disclosure also provides a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the above-described method.

A fifth aspect of the present disclosure also provides a computer program product comprising a computer program which, when executed by a processor, implements the above method.

According to the request response method, the device, the equipment, the medium and the program product, under the condition that an access request is received, the target interface calling authority information is dynamically acquired from the management platform according to the first interface information of the first node and the second interface information of the second node, so that timeliness of the acquired target interface calling authority information is improved, processing operation on the access request is executed according to the target interface calling authority information, therefore, the interface calling authorities of the first node and the second node are dynamically determined according to the target interface calling authority information, timely adjustment of the interface calling authorities of the first node and the second node can be realized, the adjustment of the interface calling authorities of the first node and the second node through modifying codes is avoided, flexibility of determining the first node and the second node calling authorities is improved, efficiency is improved, the condition that the first node and the second node are difficult to identify the access request due to abnormality is avoided, and the safety of the node is improved.

Drawings

The foregoing and other objects, features and advantages of the disclosure will be more apparent from the following description of embodiments of the disclosure with reference to the accompanying drawings, in which:

FIG. 1 schematically illustrates an application scenario diagram of a request response method according to an embodiment of the present disclosure;

FIG. 2 schematically illustrates a flow chart of a request response method according to an embodiment of the disclosure;

FIG. 3 schematically illustrates a schematic diagram of a management platform according to an embodiment of the present disclosure;

FIG. 4 schematically illustrates a schematic diagram of a control module according to an embodiment of the disclosure;

FIG. 5 schematically illustrates a flow chart of an access request processing method according to an embodiment of the disclosure;

FIG. 6 schematically illustrates a block diagram of a request response device according to an embodiment of the disclosure; and

fig. 7 schematically illustrates a block diagram of an electronic device adapted to implement a request response method according to an embodiment of the disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is only exemplary and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the present disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and/or the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It should be noted that the terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly formal manner.

Where expressions like at least one of "A, B and C, etc. are used, the expressions should generally be interpreted in accordance with the meaning as commonly understood by those skilled in the art (e.g.," a system having at least one of A, B and C "shall include, but not be limited to, a system having a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

In the technical scheme of the disclosure, the related data (such as including but not limited to personal information of a user) are collected, stored, used, processed, transmitted, provided, disclosed, applied and the like, all conform to the regulations of related laws and regulations, necessary security measures are adopted, and the public welcome is not violated.

For an access request from a client, a gateway is generally arranged between a node and the client, so that the gateway is used as a control point for the client to access an internal service, the client is prevented from directly calling the node, and the security is improved.

However, access control management is often lacking between nodes within the microservice, resulting in the interfaces of the nodes being more freely callable. In the case that one node is abnormal and access among the nodes is difficult to control, other nodes which are not abnormal may also be abnormal due to the access of the abnormal node. For the identification of interface call authorities among the nodes in the micro-service, technicians are mostly required to write authority identification codes into node codes in the development stage of the nodes, so that the problems of high code coupling and difficulty in real-time dynamic change exist.

In view of this, an embodiment of the present disclosure provides a request response method, including: and responding to the access request initiated by the first node to the second node, acquiring first interface information of the first node and second interface information of the second node, wherein the first interface information represents interface information required to be called by the first node for sending the access request to the second node, and the second interface information represents interface information required to be called by the second node for receiving the access request of the first node. And acquiring target interface calling authority information from the management platform according to the first interface information and the second interface information, wherein the target interface calling authority information is configured according to the data interaction requirement between the first node and the second node. And executing the processing operation of the access request according to the permission information of the target interface.

Fig. 1 schematically illustrates an application scenario diagram of a request response method according to an embodiment of the present disclosure.

As shown in fig. 1, an application scenario 100 according to this embodiment may include a terminal device 101, a first node 102, a second node 103, a management platform 104, and a network 105. The network 105 serves as a medium for providing a communication link between the terminal device 101, the first node 102, the second node 103 and the management platform 104. The network 105 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

A user may interact with at least one of the first node 102, the second node 103, the management platform 104, via the network 104 using the terminal device 101, to receive or send messages, etc. Various communication client applications, such as shopping class applications, web browser applications, search class applications, instant messaging tools, mailbox clients, social platform software, etc., may be installed on the terminal device 101 (by way of example only).

The terminal device 101 may be a variety of electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.

The first node 102, the second node 103, and the management platform 104 may be servers providing various services, such as a background management server (by way of example only) providing support for websites browsed by the user using the terminal device 101. The background management server may analyze and process the received data such as the user request, and feed back the processing result (e.g., the web page, information, or data obtained or generated according to the user request) to the terminal device.

It should be noted that, the request response method provided by the embodiments of the present disclosure may be generally performed by at least one of the first node 102, the second node 103, and the management platform 104. Accordingly, the request response device provided by the embodiments of the present disclosure may be generally disposed in at least one of the first node 102, the second node 103, and the management platform 104. The request response method provided by the embodiments of the present disclosure may also be performed by a server or a server cluster that is different from the first node 102, the second node 103, or the management platform 104 and is capable of communicating with the terminal device 101, the first node 102, the second node 103, and/or the management platform 104. Accordingly, the request response apparatus provided by the embodiments of the present disclosure may also be provided in a server or a server cluster that is different from the first node 102, the second node 103, or the management platform 104 and is capable of communicating with the terminal device 101, the first node 102, the second node 103, and/or the management platform 104.

It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

The request response method of the disclosed embodiment will be described in detail below with reference to fig. 2 to 5 based on the scenario described in fig. 1.

Fig. 2 schematically illustrates a flow chart of a request response method according to an embodiment of the disclosure.

As shown in fig. 2, the request response method of this embodiment includes operations S210 to S230.

In operation S210, in response to receiving an access request initiated by the first node to the second node, first interface information of the first node and second interface information of the second node are obtained, where the first interface information characterizes interface information required to be invoked by the first node to send the access request to the second node, and the second interface information characterizes interface information required to be invoked by the second node to receive the access request of the first node.

According to an embodiment of the present disclosure, both the first node and the second node may be micro-service nodes. The first node and the second node may each have a plurality of services deployed thereon, and the access request may be generated based on the first node making a service call to the second node, but is not limited thereto.

According to an embodiment of the present disclosure, the access request may include, but is not limited to, interface identification information of an interface required to be invoked for data interaction between the first node and the second node. The first interface information may be determined from all interface information of the first node and the second interface information may be determined from all interface information of the second node according to the interface identification information.

In operation S220, target interface call permission information is obtained from the management platform according to the first interface information and the second interface information, wherein the target interface call permission information is configured according to the data interaction requirement between the first node and the second node.

According to the embodiment of the disclosure, the management platform may be used for managing the first node and the second node, may store information of the nodes managed by the management platform, may include interface call authority information of call interfaces between the nodes, but is not limited thereto, and may also store node identification information of the nodes, node interface information, node running state information, and the like, but is not limited thereto.

According to an embodiment of the disclosure, the target interface call permission information may be used to determine permission of the access request, and may include call permission information of the first node to initiate the request to the second node, where the call permission information of the interface information is required to be called, that is, the target interface call permission information may include call permission information of the first interface information and call permission information of the second interface information.

Acquiring target interface calling authority information from the management platform according to the first interface information and the second interface information, wherein the target interface calling authority information corresponding to the first interface identification information and the second interface identification information can be determined from a plurality of interface calling authority information stored in the management platform according to the first interface identification information in the first interface information and the second interface identification information in the second interface information; the target interface call authority information corresponding to the node identification information of the first node and the node identification information of the second node may be determined from the plurality of interface call authority information stored in the management platform according to the node identification information of the first node and the node identification information of the second node in the first interface information.

According to the embodiment of the disclosure, the data interaction requirement between the first node and the second node may be that the service of the first node needs to be called together in the case of calling the service of the first node, so that the service of the first node can be completely executed, but is not limited to the method.

According to the embodiment of the disclosure, the security problem caused by modifying the permission identification code of the node under the condition that the node is abnormal can be avoided by dynamically acquiring the target interface call permission information from the management platform according to the first interface information and the second interface information.

In operation S230, a processing operation for the access request is performed according to the target interface call permission information.

According to the embodiment of the disclosure, the call authority between the first node and the second node can be determined according to the call authority information of the target interface. The access request may be blocked without call rights between the first node and the second node.

Under the condition that the calling authority is provided between the first node and the second node, the first interface information and the second interface information can be called according to the access request to realize the access of the first node to the second node.

Based on the method, when the first node is in an abnormal condition and an access request is initiated to the second node, the access request can be identified through the permission information called by the target interface, and the processing operation of the access request is executed, so that the security of the node is improved.

According to the embodiment of the disclosure, the target interface calling authority information is dynamically acquired from the management platform according to the first interface information of the first node and the second interface information of the second node under the condition that the access request is received, so that timeliness of the acquired target interface calling authority information is improved, and then the processing operation of the access request is executed according to the target interface calling authority information.

According to the embodiment of the disclosure, in the case that the target interface call permission information is modified, the modified target interface call permission information can be automatically sent to the first node and the second node by the management platform. The timeliness of determining the interface calling authority of the first node and the second node can be improved.

According to an embodiment of the present disclosure, the target interface call permission information includes interface interaction node information. And executing the processing operation of the access request according to the permission information of the target interface, wherein the processing operation comprises the following steps: and carrying out interface calling permission identification on the access request according to the interface interaction node information to obtain an identification result. And executing the processing operation of the access request according to the identification result.

According to embodiments of the present disclosure, the interface interaction node information may be used to determine that the first node invokes information of a node capable of transmitting an access request with the first interface information, and that the second node is capable of receiving an access request with the second interface information.

According to the embodiment of the disclosure, according to the interface interaction node information, interface calling authority identification is performed on the access request to obtain an identification result, wherein the identification result can be used for indicating that the access request is a normal request when the interface interaction node information indicates that the first node has the authority to call the first interface information to send the access request to the second node and the second node has the authority to call the second interface information to receive the access request; and under the condition that the interface interaction node information characterizes that the first node does not have the authority to call the first interface information to send the access request to the second node, and the second node does not have the authority to call the second interface information to receive the access request, the identification result can characterize that the access request is an abnormal request.

According to the embodiment of the disclosure, in the case that the identification result characterizes that the access request is an abnormal request, the first node and the second node are prevented from accessing;

and under the condition that the identification result represents that the access request is a normal request, the first interface of the first node corresponding to the first interface information and the second interface of the second node corresponding to the second interface information can be called according to the access request to realize the access of the first node to the second node.

For example: node a may call interface information A1 to send an access request to node B, node C and node D, and node B may call interface information B1 only to receive the access request from node C and node D, whereby in the case where node a sends an access request to node B, the access request may be identified as an abnormal request and the sending of the access request may be prevented.

Also for example: node a may invoke interface information A1 to send an access request to node B, node C and node D, and node B may invoke interface information B1 to receive an access request from node a, whereby in case node a sends an access request to node B, the access request may be identified as a normal request and invoke interface information A1 and interface information B1 to complete data interaction between node a and node B.

According to the embodiment of the disclosure, the dynamic acquisition of the interface interaction node information can be realized by dynamically acquiring the target interface call permission information from the management platform, and the flexibility of acquiring the interface interaction node information is improved, so that the node of which the first node can send the access request by calling the first interface information can be dynamically adjusted, and the node of which the second node can receive the access request by calling the second interface information can be dynamically adjusted. Furthermore, when the first node is abnormal, the second node can be timely adjusted to have no authority for calling the second interface information to receive the access request from the first node, so that the security of the second node is improved.

According to the embodiment of the disclosure, the accuracy of identifying the access request is improved because the access request is identified by the interface calling authority according to the interface interaction node information.

According to an embodiment of the present disclosure, the target interface call permission information may further include an enabling state of the first interface information of the first node and the second interface information of the second node of the interface enabling state information. The interface enabling state information may include first enabling state information of the first interface information and second enabling state information of the second interface information, and the interface call permission identification may be performed on the access request according to the first enabling state information and the second interface state information. The first enabling information may be used to characterize the enabling state of the first interface information and the second enabling information may be used to characterize the enabling state of the second interface information.

The interface call permission identification is performed on the access request according to the first enabling state information and the second enabling state information, the enabling state of the first interface can be determined according to the first enabling state information, the enabling state of the second interface can be determined according to the second enabling state information, and the access request can be identified as an abnormal request under the condition that at least one of the first enabling state information and the second enabling state information represents that the interface is not enabled, so that the identification result can represent that the access request is the abnormal request.

In the case where the first enabling state information and the second enabling state information both characterize the enabling of the interface information, the access request may be identified as a normal request, whereby the identification result may characterize the access request as a normal request.

According to an embodiment of the present disclosure, in a case where the recognition result characterizes the access request as an abnormal request, the first node is prevented from transmitting the access request;

and under the condition that the identification result characterizes that the access request is a normal request, the first interface information and the second interface information can be called according to the access request to realize the access of the first node to the second node.

According to the embodiment of the disclosure, the target interface calling authority information is dynamically acquired from the management platform, so that the starting states of the first interface information and the second interface information can be timely adjusted. And when the abnormal node exists, the starting state of the interface information of other nodes related to the abnormal node can be adjusted to be not started, so that the influence of the abnormal node on the other nodes is avoided, and the node safety is improved.

According to an embodiment of the present disclosure, the interface interaction node information includes interface interaction period information, and the interface interaction period information characterizes period information of which the first interface information and the second interface information have interaction rights. According to the interface interaction node information, carrying out interface calling authority identification on the access request to obtain an identification result, wherein the method comprises the following steps: and determining calling period information of calling the first interface information and the second interface information by the access request according to the access request. And carrying out interface calling authority identification on the access request according to the interface interaction time period information and the calling time period information to obtain an identification result.

According to an embodiment of the present disclosure, the interface interaction period information may include first interface interaction period information of the first interface information and second interface interaction period information of the second interface information. The first interface interaction time period information can be characterized, and the first interface information has time period information of authority for sending an access request to the second node; the second interface interaction period information may be characterized as period information having authority to receive an access request from the first node.

The call period information may characterize period information of the first interface information and the second interface information required for the first node to access the second node. The access request may be interface-invoked for permission identification based on the interface interaction period information.

For example: the first interface interaction time period information of the node A can be 3 to 5 hours, namely the node A has the authority of calling the interface information A1 to send an access request to the node B, the node C and the node D when the node A is 3 to 5 hours; the second interface interaction period information of the node B may correspond to 3 to 5 hours, that is, the node B has the right to receive the access request from the node a by calling the interface information B1 at 3 to 5 hours. In the case where the call period information is 4 hours 5 minutes to 4 hours 10 minutes, the access request may be identified as a normal request, and the interface information A1 and the interface information B1 may be called to complete data interaction between the node a and the node B.

And in the case where the call period information is 6 to 7, the access request may be identified as an abnormal request, and the transmission of the access request may be prevented.

According to the embodiment of the disclosure, the target interface calling authority information is dynamically acquired from the management platform, so that the dynamic acquisition of interface interaction time period information can be realized, and the flexibility of acquiring interface interaction node information is fully utilized, so that the time period of the first interface information with the access request sending authority can be dynamically adjusted, and the time period of the second interface information with the access request sending authority can be dynamically adjusted. Even if the permission is invalid due to the end of the period, the management platform can send new interface interaction period information to the first node and the second node again, and the interaction period of the first interface information and the interaction period of the second interface information are redetermined, so that the flexibility of access between the first node and the second node is improved, and the security of access between the first node and the second node is improved.

According to the embodiment of the disclosure, the time period that the first interface information and the second interface information have the interaction permission is determined according to the interface interaction time period information, so that timeliness of interface interaction is improved, flexibility of interface interaction is improved, and further interface calling permission identification can be performed on the access request according to the interface interaction time period information and the calling time period information, an identification result is obtained, and safety is improved.

According to embodiments of the present disclosure, the target interface call permission information may further include interface enable period information. The interface enable period information may include an enable period of the first interface information and an enable period of the second interface information. The access request can be identified according to the interface enabling time period information and the calling time period information, and an identification result is obtained.

For example: the first enabling period information may include 3 to 5 times, and the second enabling period information may include 4 to 6 times, and thus, a period in which the first interface information and the second interface information are simultaneously enabled may include 4 to 5 times. The call period information may be 5 to 6 hours, and thus it may be determined that the access time information does not belong to a period in which the first interface information and the second interface information are simultaneously enabled, and thus the access request may be identified as an abnormal request, and the identification result may characterize the access request as an abnormal request.

And in the case that the calling period information is 4 hours 30 minutes to 4 hours 40 minutes, the access request can be identified as a normal request, and the identification result can characterize that the access request is identified as the normal request.

According to an embodiment of the present disclosure, in a case where the recognition result characterizes the access request as an abnormal request, the first node is prevented from transmitting the access request;

and under the condition that the identification result characterizes that the access request is a normal request, the first interface information and the second interface information can be called according to the access request to realize the access of the first node to the second node.

According to an embodiment of the present disclosure, the request response method further includes: and generating request processing notification information when the identification result indicates that the access request is abnormal. And sending the request processing notification information to the management platform.

According to embodiments of the present disclosure, the request processing notification information may include a processing result for the access request, which may characterize that the access request is blocked. The request processing notification information may further include access time information, first interface information, second interface information, node identification information of the first node, second node identification information, and the like of the access request, so that the management platform manages the access request.

According to the embodiment of the disclosure, the request processing notification information is generated under the condition that the identification result characterizes that the access request is abnormal, and then the request processing notification information is sent to the management platform, so that the management platform can manage the first node and the second node aiming at the access request in time, and the safety of the first node and the second node is improved.

According to an embodiment of the present disclosure, the request response method further includes: and changing the node attribute information of the first node and the second node according to the interface calling authority information to obtain changed node attribute information.

According to an embodiment of the present disclosure, the node attribute information of the first node may include original interface call authority information. The original interface calling authority information can be changed according to the target interface calling authority information, so that the interface calling authority of the first node can be changed in time.

According to an embodiment of the present disclosure, the node attribute information of the second node may include original interface call authority information. The original interface calling authority information can be changed according to the target interface calling authority information, so that the interface calling authority of the second node can be changed in time.

According to an embodiment of the present disclosure, the node attribute information of the first node may include node identification information, node interface information, node operation state information, and the like of the first node; the node attribute information of the second node may include node identification information, node interface information, node operation state information, and the like of the second node.

According to the embodiment of the disclosure, the node attribute information of the first node and the second node is changed according to the target interface call permission information, so that the changed node attribute information is obtained, and therefore, the interface call permission of the first node and the second node can be adjusted without modifying codes, the dynamic change of the interface call permission of the first node and the second node is realized, the flexibility of determining the interface call permission of the first node and the second node is improved, and the safety of the first node and the second node is further improved.

According to an embodiment of the present disclosure, the request response method further includes: and obtaining node attribute information according to the first node and the second node. And sending the node attribute information to a management platform.

According to the embodiment of the disclosure, the node attribute information is sent to the management platform, so that the management platform can store the node attribute information, and the data interaction requirement between the first node and the second node can be determined according to the node attribute information.

According to the embodiment of the disclosure, the node attribute information is obtained according to the first node and the second node, and the node attribute information is sent to the management platform, so that the management platform can manage the first node and the second node according to the node attribute information, and the flexibility, timeliness and safety of managing the first node and the second node are improved.

According to an embodiment of the present disclosure, the node attribute information includes node identification information, node interface information, and node operation state information. Sending node attribute information to a management platform, including: and sending node identification information, node interface information and node running state information to the management platform, wherein the node interface information and the node running state information are used for determining the data interaction requirement between the first node and the second node, and the node identification information is used for determining the first node and the second node from a plurality of nodes under the condition that the management platform sends target interface calling authority information to the first node and the second node.

According to the embodiment of the disclosure, the interface information of the first node and the interface information of the second node can be determined according to the node interface information. And, the operational state of the first node may be determined, and the operational state of the second node may be determined, based on the node operational state information. And further, the data interaction requirement between the first node and the second node can be determined according to the running state of the first node and the interface information of the first node, and the running state of the second node and the interface information of the second node, so that the interface calling authorities of the first node and the second node can be configured according to the data interaction requirement, and the target interface calling authority information is obtained.

And then determining the first node and the second node from a plurality of nodes managed by the management platform according to the node identification information, and sending target interface calling authority information to the first node and the second node by using the management platform.

According to the embodiment of the disclosure, the node interface information and the node running state information are used for determining the data interaction requirement between the first node and the second node, so that the interface calling authorities of the first node and the second node can be configured according to the data interaction requirement to obtain the target interface calling authority information, then the first node and the second node can be determined from a plurality of nodes by utilizing the node identification information, and therefore, the target interface calling authority information can be sent to the first node and the second node by utilizing the management platform, the flexibility of the interface calling authorities of the first node and the second node is improved, and the safety of the first node and the second node is further improved.

According to an embodiment of the present disclosure, the node attribute information may further include node address information, which may be used to determine addresses of the first node and the second node. In the case that the first node and the second node are determined according to the node identification information, the management platform may be utilized to send the target interface call authority information to the first node and the second node according to the node address information.

Fig. 3 schematically illustrates a schematic diagram of a management platform according to an embodiment of the present disclosure.

As shown in fig. 3, the management platform 310 may include a management sub-module 311 and a presentation sub-module 311. The management sub-module 311 may be configured to record node attribute information, so as to manage the first node and the second node; the presentation sub-module 312 may be used to present the management page at the client so that the technician invokes the rights information at the management page adjustment interface.

According to the embodiment of the disclosure, the first node and the second node can be respectively provided with a control module, and the first node and the second node can respectively use the control modules to collect node attribute information such as node identification information, node interface information, node running state information and the like and then send the node attribute information to the management platform. And under the condition that the first node and the second node receive the target interface calling authority information from the management platform, the control module carries out interface calling authority identification on the access request according to the target interface calling authority information.

Fig. 4 schematically illustrates a schematic diagram of a control module according to an embodiment of the disclosure.

As shown in fig. 4, the control module 410 may include an adjustment sub-module 411, an acquisition sub-module 412, and a rights identification sub-module 413, where the adjustment sub-module 411 may be configured to adjust the first node and the second node interface call rules according to the target interface call rights information; the collecting sub-module 412 may be configured to collect node attribute information such as node identification information, node interface information, and node running state information; the rights identification sub-module 413 may be configured to perform interface call rights identification on the access request according to the target interface call rights information.

Fig. 5 schematically illustrates a flow chart of an access request processing method according to an embodiment of the present disclosure.

As shown in fig. 5, the access request processing method includes operations S510 to S560.

In operation S510, node attribute information is collected.

In operation S520, node attribute information is transmitted to the management platform.

In operation S530, the target interface call authority information is received.

Is the access request satisfying the target interface call permission information? If yes, operation S550 is performed; if not, operation S560 is performed.

In operation S550, the first interface information and the second interface information are called according to the access request.

In operation S560, the access request is blocked.

Based on the request response method, the disclosure further provides a request response device. The device will be described in detail below in connection with fig. 6.

Fig. 6 schematically shows a block diagram of a request response device according to an embodiment of the present disclosure.

As shown in fig. 6, the request response device 600 of this embodiment includes a first acquisition module 610, a second acquisition module 620, and an execution module 630.

The first obtaining module 610 is configured to obtain, in response to receiving an access request initiated by a first node to a second node, first interface information of the first node and second interface information of the second node, where the first interface information characterizes interface information that needs to be invoked by the first node to send the access request to the second node, and the second interface information characterizes interface information that needs to be invoked by the second node to receive the access request of the first node. In an embodiment, the first obtaining module 610 may be configured to perform the operation S210 described above, which is not described herein.

The second obtaining module 620 is configured to obtain, from the management platform, target interface call permission information according to the first interface information and the second interface information, where the target interface call permission information is configured according to a data interaction requirement between the first node and the second node. In an embodiment, the second obtaining module 620 may be configured to perform the operation S220 described above, which is not described herein.

The execution module 630 is configured to execute a processing operation for the access request according to the interface call permission information. In an embodiment, the execution module 630 may be configured to execute the operation S230 described above, which is not described herein.

According to an embodiment of the present disclosure, the execution module 630 includes an identification sub-module and an execution sub-module. The identification sub-module is used for carrying out interface calling permission identification on the access request according to the interface interaction node information to obtain an identification result; and the execution submodule is used for executing the processing operation of the access request according to the identification result.

According to an embodiment of the present disclosure, the identification sub-module comprises a determination unit and an identification unit. The determining unit is used for determining calling time period information of the first interface information and the second interface information called by the access request according to the access request; and the identification unit is used for carrying out authority identification on the access request according to the interface interaction time period information and the calling time period information to obtain the identification result.

According to an embodiment of the present disclosure, the execution module 630 further includes a generation sub-module and a first transmission sub-module. The generation sub-module is used for generating request processing notification information under the condition that the identification result represents that the access request is abnormal; the first sending sub-module is used for sending request processing notification information to the management platform.

According to an embodiment of the present disclosure, the request response device further includes a change module. The change module is used for changing the node attribute information of the first node and the second node according to the interface calling authority information to obtain changed node attribute information.

According to an embodiment of the present disclosure, the request response device further includes a third obtaining module and a sending module. The third acquisition module is used for acquiring node attribute information according to the first node and the second node; the sending module is used for sending the node attribute information to the management platform, wherein the node attribute information is used for determining the data interaction requirement between the first node and the second node.

According to an embodiment of the present disclosure, the transmitting module comprises a second transmitting sub-module. The second sending sub-module is configured to send the node identification information, the node interface information, and the node running state information to the management platform, where the node interface information and the node running state information are used to determine a data interaction requirement between the first node and the second node, and the node identification information is used to determine the first node and the second node from multiple nodes when the management platform sends the target interface calling permission information to the first node and the second node.

Any of the first acquisition module 610, the second acquisition module 620, and the execution module 630 may be combined in one module to be implemented, or any of the modules may be split into a plurality of modules, according to embodiments of the present disclosure. Alternatively, at least some of the functionality of one or more of the modules may be combined with at least some of the functionality of other modules and implemented in one module. According to embodiments of the present disclosure, at least one of the first acquisition module 610, the second acquisition module 620, and the execution module 630 may be implemented at least in part as hardware circuitry, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in hardware or firmware in any other reasonable way of integrating or packaging circuitry, or in any one of or a suitable combination of any of the three. Alternatively, at least one of the first acquisition module 610, the second acquisition module 620, and the execution module 630 may be at least partially implemented as a computer program module, which when executed, may perform the corresponding functions.

Fig. 7 schematically illustrates a block diagram of an electronic device adapted to implement a request response method according to an embodiment of the disclosure.

As shown in fig. 7, an electronic device 700 according to an embodiment of the present disclosure includes a processor 701 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 702 or a program loaded from a storage section 708 into a Random Access Memory (RAM) 703. The processor 701 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or an associated chipset and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. The processor 701 may also include on-board memory for caching purposes. The processor 701 may comprise a single processing unit or a plurality of processing units for performing different actions of the method flows according to embodiments of the disclosure.

In the RAM 703, various programs and data necessary for the operation of the electronic apparatus 700 are stored. The processor 701, the ROM 702, and the RAM 703 are connected to each other through a bus 704. The processor 701 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 702 and/or the RAM 703. Note that the program may be stored in one or more memories other than the ROM 702 and the RAM 703. The processor 701 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in the one or more memories.

According to an embodiment of the present disclosure, the electronic device 700 may further include an input/output (I/O) interface 705, the input/output (I/O) interface 705 also being connected to the bus 704. The electronic device 700 may also include one or more of the following components connected to an input/output (I/O) interface 705: an input section 706 including a keyboard, a mouse, and the like; an output portion 707 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, a speaker, and the like; a storage section 708 including a hard disk or the like; and a communication section 709 including a network interface card such as a LAN card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. The drive 710 is also connected to an input/output (I/O) interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read therefrom is mounted into the storage section 708 as necessary.

The present disclosure also provides a computer-readable storage medium that may be embodied in the apparatus/device/system described in the above embodiments; or may exist alone without being assembled into the apparatus/device/system. The computer-readable storage medium carries one or more programs which, when executed, implement methods in accordance with embodiments of the present disclosure.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example, but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, the computer-readable storage medium may include ROM 702 and/or RAM 703 and/or one or more memories other than ROM 702 and RAM 703 described above.

Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowcharts. The program code, when executed in a computer system, causes the computer system to implement the item recommendation method provided by embodiments of the present disclosure.

The above-described functions defined in the system/apparatus of the embodiments of the present disclosure are performed when the computer program is executed by the processor 701. The systems, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.

In one embodiment, the computer program may be based on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted, distributed over a network medium in the form of signals, downloaded and installed via the communication section 709, and/or installed from the removable medium 711. The computer program may include program code that may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

In such an embodiment, the computer program may be downloaded and installed from a network via the communication portion 709, and/or installed from the removable medium 711. The above-described functions defined in the system of the embodiments of the present disclosure are performed when the computer program is executed by the processor 701. The systems, devices, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.

According to embodiments of the present disclosure, program code for performing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, such computer programs may be implemented in high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. Programming languages include, but are not limited to, such as Java, c++, python, "C" or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Those skilled in the art will appreciate that the features recited in the various embodiments of the disclosure and/or in the claims may be provided in a variety of combinations and/or combinations, even if such combinations or combinations are not explicitly recited in the disclosure. In particular, the features recited in the various embodiments of the present disclosure and/or the claims may be variously combined and/or combined without departing from the spirit and teachings of the present disclosure. All such combinations and/or combinations fall within the scope of the present disclosure.

The embodiments of the present disclosure are described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the embodiments cannot be used advantageously in combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be made by those skilled in the art without departing from the scope of the disclosure, and such alternatives and modifications are intended to fall within the scope of the disclosure.

Claims (11)

1. A request response method, comprising:

in response to receiving an access request initiated by a first node to a second node, acquiring first interface information of the first node and second interface information of the second node, wherein the first interface information characterizes interface information required to be called by the first node for sending the access request to the second node, and the second interface information characterizes interface information required to be called by the second node for receiving the access request of the first node;

Acquiring target interface calling authority information from a management platform according to the first interface information and the second interface information, wherein the target interface calling authority information is configured according to the data interaction requirement between the first node and the second node;

and executing the processing operation of the access request according to the target interface calling authority information.

2. The method of claim 1, wherein the target interface invocation permission information includes interface interaction node information;

and the processing operation of the access request is executed according to the target interface calling authority information, and the processing operation comprises the following steps:

according to the interface interaction node information, carrying out interface calling authority identification on the access request to obtain an identification result;

and executing the processing operation of the access request according to the identification result.

3. The method of claim 2, wherein the interface interaction node information includes interface interaction period information, the interface interaction period information characterizing period information for which the first interface information and the second interface information have interaction rights;

and carrying out interface calling authority identification on the access request according to the interface interaction node information to obtain an identification result, wherein the method comprises the following steps of:

Determining calling period information of the access request for calling the first interface information and the second interface information according to the access request;

and carrying out interface calling authority identification on the access request according to the interface interaction time period information and the calling time period information to obtain the identification result.

4. The method of claim 2, further comprising:

generating request processing notification information under the condition that the identification result characterizes that the access request is abnormal;

and sending request processing notification information to the management platform.

5. The method of claim 1, further comprising:

and changing the node attribute information of the first node and the second node according to the target interface calling authority information to obtain changed node attribute information.

6. The method of claim 1, further comprising:

obtaining node attribute information according to the first node and the second node;

and sending the node attribute information to the management platform.

7. The method of claim 6, wherein the node attribute information includes node identification information, node interface information, and node operational state information;

The sending the node attribute information to the management platform includes:

the node identification information, the node interface information and the node running state information are sent to the management platform, wherein the node interface information and the node running state information are used for determining data interaction requirements between the first node and the second node, and the node identification information is used for determining the first node and the second node from a plurality of nodes under the condition that the management platform sends the target interface calling authority information to the first node and the second node.

8. A request response device comprising:

the first acquisition module is used for responding to the received access request initiated by a first node to a second node and acquiring first interface information of the first node and second interface information of the second node, wherein the first interface information characterizes the interface information required to be called by the access request sent by the first node to the second node, and the second interface information characterizes the interface information required to be called by the access request received by the second node;

The second acquisition module is used for acquiring target interface calling authority information from the management platform according to the first interface information and the second interface information, wherein the target interface calling authority information is configured according to the data interaction requirement between the first node and the second node;

and the execution module is used for executing the processing operation of the access request according to the target interface calling authority information.

9. An electronic device, comprising:

one or more processors;

storage means for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-7.

10. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the method according to any of claims 1-7.

11. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 7.