A service data calling method, system, device, equipment and medium

Abstract

This application relates to the field of information processing technology, specifically to a service data retrieval method, system, apparatus, device, and medium, used to solve the problem that service data retrieval between network areas relies on manually configured routing paths. The method includes: responding to a first request for first service data received by an external interface of a first network area; based on the correspondence between service data and network areas, searching for a target network area providing the first service data, wherein the target network area represents the network area publishing the first service data; if the target network area is not the first network area, then sending the first request for the first service data to the external interface of the target network area; if the target network area is the first network area, then sending the first service data to an external interface of a second network area, wherein the second network area is the network area that sent the first request.

Description

Technical Field

[0001] This application relates to the field of information processing technology, specifically to a service data retrieval method, system, apparatus, device, and medium. Background Technology

[0002] With the increasing demand for enhanced system security, existing electronic systems can include multiple network zones, with services isolated between these zones. Each network zone supports its own services and provides these services to clients belonging to that zone, thus possessing service data specific to its clients. For example, client 1 belongs to network zone 1, and network zone 1 provides services to client 1. Client 2 belongs to network zone 2, and network zone 2 provides services to client 2. However, in some scenarios, network zone 2 needs to access client 1's service information, requiring network zone 2 to request client 1's service data from network zone 1. This method of service data retrieval across multiple network zones is classified as cross-network zone service data retrieval.

[0003] Currently, when service data is requested across multiple network zones, such as when network zone 2 requests service data from client 1 in network zone 1, technicians need to manually configure the routing path between network zone 2 and network zone 1. This method makes the process of network zone 2 requesting service data from network zone 1 take a long time. Summary of the Invention

[0004] This application provides a service data retrieval method, system, apparatus, device, and medium to solve the problem that service data retrieval between network areas relies on manually configured routing paths.

[0005] In a first aspect, embodiments of this application provide a service data invocation method, the method comprising:

[0006] In response to a first request for first service data received by the external interface of the first network region, based on the correspondence between service data and network regions, the target network region that provides the first service data is located, wherein the target network region represents the network region that publishes the first service data;

[0007] If the target network region is not the first network region, then the first request for the first service data is sent to the external interface of the target network region;

[0008] If the target network region is the first network region, then the first service data is sent to the external interface of the second network region, which is the network region that sent the first request.

[0009] In this embodiment, the network areas interact with each other through external interfaces. That is, the external interfaces of each network area are publicly accessible to each other. The first network area can receive service data requests from other network areas, and can forward the request or provide the service data to the corresponding network area's external interface. This enables automated service data invocation, eliminating the need for technical personnel to configure routing paths between network areas.

[0010] In one possible embodiment, the method further includes: the external interface of the first network area receiving at least one service configuration information, wherein the at least one service configuration information includes service publishing configuration information; the service publishing configuration information includes an identifier of target service data and an identifier of a third network area providing the target service data;

[0011] Based on the service publishing configuration information, the correspondence between the service data and the network region is determined.

[0012] In one possible embodiment, the method further includes: the at least one service configuration information includes service invocation configuration information; the service invocation configuration information includes an identifier of a fourth network area requesting the one service data, and the message types supported by the fourth network area;

[0013] The external interface for sending the first request for the first service data to the target network area further includes:

[0014] The first request is sent to the external interface of the target network area using the message type supported by the target network area.

[0015] The external interface for sending the first service data to the second network area further includes:

[0016] The first request is sent to the external interface of the second network area using the message type supported by the second network area.

[0017] In one possible embodiment, the method further includes: the at least one service configuration information includes service invocation configuration information. The service invocation configuration information includes an identifier of the requested fifth network area and the encryption / decryption methods supported by the fifth network area;

[0018] The external interface for sending the first service data to the second network area further includes:

[0019] The first service data is encrypted using the encryption / decryption method supported by the second network area.

[0020] In one possible embodiment, the method further includes: in response to a second request for second service data received by the internal interface of the first network area, sending the second service data to a target client through the internal interface of the first network area, wherein the target client is the client that sent the second request.

[0021] Secondly, this application provides service invocation data, the method of which may include:

[0022] A request to receive first service data is received, the request being sent by the target client;

[0023] Based on the correspondence between service data and network regions, the target network region that provides the first service data is located, and the target network region represents the network region that publishes the first service data;

[0024] If the target network area is not the second network area, then the request for the first service data is sent to the external interface of the first network area;

[0025] If the target network area is the second network area, then the first service data is sent to the target client.

[0026] In one possible embodiment, the method further includes:

[0027] The external interface of the second network area receives at least one service configuration information, wherein the at least one service configuration information includes service publishing configuration information, the service publishing configuration information includes the identifier of the first service data, and the identifier of the network area providing the first service data;

[0028] Based on the service publishing configuration information, the correspondence between the service data and the network region is determined.

[0029] Thirdly, embodiments of this application provide a service data retrieval system, wherein a first network region searches for a target network region that provides the first service data based on the correspondence between service data and network regions, and the target network region represents the network region of the first service data;

[0030] The target network area sends the first service data to the external interface of the second network area, or the target network area sends the first service data to the target client; wherein the second network area is the network area that initiated the request for the first service data; and the target client is the client that initiated the request for the first service data.

[0031] Fourthly, embodiments of this application provide a service data retrieval apparatus, the apparatus comprising:

[0032] The external interface is used to receive the first request for the first service data.

[0033] Processing unit, used for:

[0034] In response to a first request for the first service data, based on the correspondence between service data and network regions, a target network region providing the first service data is located, wherein the target network region represents the network region that publishes the first service data;

[0035] If the target network area is not the first network area, then the request for the first service data is sent to the external interface of the target network area;

[0036] If the target network region is the first network region, then the first service data is sent to the external interface of the second network region, which is the network region that sent the first request.

[0037] In one possible embodiment, the external interface in the device is further configured to: receive at least one service configuration information, wherein the at least one service configuration information includes service publishing configuration information; the service publishing configuration information includes an identifier of target service data and an identifier of a third network area providing the target service data;

[0038] The processing unit is further configured to: determine the correspondence between the service data and the network region based on the service publishing configuration information.

[0039] In one possible embodiment, the at least one service configuration information in the device includes service invocation configuration information; the service invocation configuration information includes an identifier of a fourth network area requesting the one service data, and the message types supported by the fourth network area;

[0040] The processing unit sends the first request for the first service data to the external interface of the target network area, and is also used for:

[0041] The first request is sent to the external interface of the target network area using the message type supported by the target network area.

[0042] The processing unit, which sends the first service data to the external interface of the second network area, is further configured to:

[0043] The first request is sent to the external interface of the second network area using the message type supported by the second network area.

[0044] In one possible embodiment, the at least one service configuration information in the apparatus includes service invocation configuration information. The service invocation configuration information includes an identifier of the requested fifth network area and the encryption / decryption methods supported by the fifth network area.

[0045] The processing unit, which sends the first service data to the external interface of the second network area, is further configured to:

[0046] The first service data is encrypted using the encryption / decryption method supported by the second network area.

[0047] In one possible embodiment, the device further includes:

[0048] An internal interface for receiving a second request for second service data, wherein the second request is sent by the target client;

[0049] The processor is also used to send the second service data to the target client through the internal interface.

[0050] Fifthly, embodiments of this application also provide a service data retrieval device, the device comprising:

[0051] An internal interface is used to receive a request for first service data, the request being sent by the target client;

[0052] Processing unit, used for:

[0053] Based on the correspondence between service data and network regions, the target network region that provides the first service data is located, and the target network region represents the network region that publishes the first service data;

[0054] If the target network area is not the second network area, then the request for the first service data is sent to the external interface of the first network area;

[0055] If the target network area is the second network area, then the first service data is sent to the target client through the internal interface.

[0056] In one possible embodiment, the device further includes an external interface;

[0057] The external interface is used for:

[0058] Receive at least one service configuration information, wherein the at least one service configuration information includes service publishing configuration information, the service publishing configuration information includes an identifier of the first service data, and an identifier of the network area providing the first service data;

[0059] The processing unit is also used for:

[0060] Based on the service publishing configuration information, the correspondence between the service data and the network region is determined.

[0061] In one possible embodiment, the processing unit is specifically configured to: send a request for the first service data to the external interface of the first network area via the external interface in the device.

[0062] Sixthly, this application provides an electronic device, comprising:

[0063] Memory, used to store program instructions;

[0064] A processor is configured to invoke program instructions stored in the memory and execute the steps included in the method described in any one of the first aspects, or execute the steps included in the method described in any one of the second aspects, according to the obtained program instructions.

[0065] In a seventh aspect, this application provides a computer-readable storage medium storing a computer program, the computer program including program instructions, which, when executed by a computer, cause the computer to perform the method described in any one of the first aspects, or to perform the steps included in the method described in any one of the second aspects.

[0066] Eighthly, this application provides a computer program product comprising: computer program code, which, when executed on a computer, causes the computer to perform the method described in any one of the first aspects, or to perform the steps included in the method described in any one of the second aspects. Attached Figure Description

[0067] Figure 1 This is a schematic diagram of an application scenario provided by an embodiment of this application;

[0068] Figure 2 A flowchart illustrating a service data invocation method provided in this application embodiment;

[0069] Figure 3 This application provides a schematic diagram illustrating the relationship between multiple network regions in an embodiment.

[0070] Figure 4 A flowchart illustrating another service data invocation method provided in this application embodiment;

[0071] Figure 5 A flowchart illustrating a service data invocation method provided in this application embodiment;

[0072] Figure 6 A flowchart illustrating a service data invocation method provided in this application embodiment;

[0073] Figure 7 This application provides a schematic diagram illustrating the relationship between multiple network regions in an embodiment.

[0074] Figure 8 This is a functional diagram of a network region provided in an embodiment of this application;

[0075] Figure 9 A structural diagram of a service data retrieval device provided in an embodiment of this application;

[0076] Figure 10 A structural diagram of a service data retrieval device provided in an embodiment of this application;

[0077] Figure 11 A structural diagram of an electronic device provided in an embodiment of this application;

[0078] Figure 12 This is a structural diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0079] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application. Unless otherwise specified, the embodiments and features in the embodiments of this application can be arbitrarily combined with each other. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than that shown here.

[0080] The terms "first" and "second" in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the term "comprising" and any variations thereof are intended to cover non-exclusive protection. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices. The term "multiple" in this application can mean at least two, for example, two, three, or more, and the embodiments of this application do not impose limitations.

[0081] The data collection, dissemination, and use in this application all comply with relevant national laws and regulations.

[0082] Before introducing the service data calling method provided in the embodiments of this application, the technical background of the embodiments of this application will be described in detail below for ease of understanding.

[0083] With the increasing demand for enhanced system security, existing electronic systems can include multiple network zones, with services isolated between these zones. Each network zone supports its own services and provides these services to clients belonging to that zone, thus possessing service data specific to its clients. For example, client 1 belongs to network zone 1, and network zone 1 provides services to client 1. Client 2 belongs to network zone 2, and network zone 2 provides services to client 2. However, in some scenarios, network zone 2 needs to access client 1's service information, requiring network zone 2 to request client 1's service data from network zone 1. This method of service data retrieval across multiple network zones is classified as cross-network zone service data retrieval.

[0084] Currently, when service data is requested across multiple network zones, such as when network zone 2 requests service data from client 1 in network zone 1, technicians need to manually configure the routing path between network zone 2 and network zone 1. This method makes the process of network zone 2 requesting service data from network zone 1 take a long time.

[0085] In one possible scenario, the number of network zones can be a positive integer greater than or equal to 2. Each network zone has clients belonging to that network zone. Each network zone can provide business services to its own clients, and each network zone can store business service data (hereinafter referred to as service data) belonging to its own clients. The service data can be configured according to the actual application scenario. Optionally, the service data can be verification data, such as image data, audio data, video data, etc. This application does not specifically limit this.

[0086] In this embodiment, the affiliation between the client and the network area can be determined through client registration, pre-configuration by technical personnel, or maintaining a communication connection. This application does not impose specific limitations on this.

[0087] For example, see Figure 1 Multiple network areas can include network area 1, network area 2, network area 3, and network area 4. Clients a1 to an belong to network area 1, clients b1 to bm belong to network area 2, clients c1 to cp belong to network area 3, and clients d1 to dq belong to network area 4. It should be noted that... Figure 1The number of network zones and clients mentioned are for illustrative purposes only and are not intended to be specific limits on the number of network zones or clients.

[0088] Client A1 can request service data from network zone 1, or it can be understood as client A1 calling a service data within network zone 1. Network zone 1 can provide the requested service data to client A1. This method is called a service data call, or a service call, within a network zone.

[0089] In some possible scenarios, client b1 requests service data A from network zone 2, but network zone 2 does not have service data A. Service data A is data that network zone 1 possesses. Therefore, network zone 2 needs to request service data A from network zone 1. Network zone 1 provides service data A to network zone 2, thus network zone 2 can provide service data A to client b1. Service data is provided by other network zones; this method is called a cross-network zone service data call, or service invocation.

[0090] Due to security requirements, no communication interfaces are exposed between network zones. For cross-network zone service data invocation, such as network zone 2 requesting service data A from network zone 1, technicians typically need to manually configure the communication path between network zone 2 and network zone 1. Based on this communication path, network zone 1 provides service data A to network zone 2. This process relies on technician intervention, making cross-network zone service data invocation cumbersome and time-consuming.

[0091] In view of this, this application implements a service invocation method to simplify the service data invocation process across network regions and improve the efficiency of service data invocation.

[0092] Figure 2 An exemplary service invocation method is shown, which can be executed by a first network zone among multiple network zones. The method may include the following steps:

[0093] Step 201: In response to the first request for first service data received by the external interface of the first network area, based on the correspondence between service data and network areas, find the target network area that provides the first service data. The target network area represents the network area that publishes the first service data.

[0094] In specific implementation, in this embodiment, each of the multiple network areas is configured with internal interfaces and external interfaces. The external interfaces are isolated from the internal interfaces. The external interfaces can be implemented as gateways, routers, or other modules. The network segment of the external interface is different from that of the internal interface, thus achieving isolation between the external and internal interfaces of the network area.

[0095] Please combine Figure 3Internal interfaces are used to exchange data with clients belonging to that network zone. External interfaces of a network zone are used to exchange data with other network zones. Data exchange between two network zones occurs through their respective external interfaces.

[0096] An external interface of a network area can exchange data with at least one external interface of another network area. For example, please combine... Figure 3 The external interface of the third network area can only exchange data with the external interface of the first network area. The external interface of the first network area can exchange data with external interfaces of multiple network areas, such as the external interfaces of the second, third, and fourth network areas. The external interface of the second network area can exchange data with the external interfaces of the first and fourth network areas. The external interface of the fourth network area can exchange data with the external interfaces of both the second and first network areas.

[0097] The first network area's external interface receives a first request for first service data, which is sent by the second network area. Specifically, the second network area's external interface sends the first request for first service data to the first network area's external interface.

[0098] In response to a first request, the first network region can locate a network region capable of providing the first service data based on the correspondence between service data and network regions, and this network region is designated as the target network region. In this embodiment, the target network region can represent a network region that publishes (is capable of providing) the first service data. The correspondence between service data and network regions can be predetermined or pre-configured by the first network region.

[0099] Step 202: If the target network area is not the first network area, then send the request for the first service data to the external interface of the target network area.

[0100] In practice, in one possible scenario, the target network area found is not the first network area itself. The first network area can forward the first request to the target network area's external interface through the first network area's external interface.

[0101] Assume, please combine Figure 3 Suppose that the target network region found by the first network region is the third network region. The first network region can send the first request to the external interface of the third network region through the external interface of the first network region.

[0102] In one possible design, the third network area can send service data to the external interface of the first network area through its own interface. After receiving the first service data, the first network area then forwards it to the external interface of the second network area through its own external interface. This enables the second network area to access the first service data, i.e., to access the service published by the third network area. Optionally, the second network area can send the first service data to the client requesting the data, such as client b1, through its internal interface.

[0103] Step 203: If the target network area is the first network area, then the first service data is sent to the external interface of the second network area, which is the network area that sent the first request.

[0104] In a specific implementation, another possible scenario is that the target network area found is the first network area itself. The first network area can forward the first service data to the second network area's external interface through its own external interface. This enables the second network area to call the first service data, that is, the second network area to call the service published by the first network area. Optionally, the second network area can send the first service data to the client requesting the first service data, such as client b1, through its internal interface.

[0105] In one possible implementation, each network area can inform other network areas of the service data it can provide by publishing services.

[0106] Taking the service publication of a first network area as an example, the first network area can provide service publication configuration information to the external interface of a second network area through an external interface. This service publication configuration information may include the identifier of the first service data provided by the first network area, and the identifier of the network area providing the first service data (i.e., the identifier of the first network area). After receiving the service publication configuration information, the second network area can determine that the network area providing the first service data is the second network area, and thus can update the aforementioned correspondence between the service data and the network area.

[0107] Similarly, the external interface of the first network area can receive service publishing configuration information provided by other network areas, including an identifier for service data and an identifier for the network area providing the service data. Thus, the first network area can learn about the service publishing situation of other network areas based on the service publishing configuration information. The first network area can determine the correspondence between the aforementioned service data and network areas based on the service publishing configuration information. In the service data-network area correspondence on the first network area side, the first network area corresponds to the service data that the first network area can provide.

[0108] In one possible application scenario, among multiple network areas, two network areas support different message types. For example, the first network area supports a first message type, and the second network area supports a second message type. The network area publishing service data can provide the service data according to the message types supported by the network area calling the service data.

[0109] In one possible implementation, each network area can inform other network areas of the message types it can support by providing service call configuration information.

[0110] Each network area can provide service invocation configuration information, which may include the identifier of the network area and the message types supported by the network area. For example, a second network area can send service invocation configuration information to the external interface of a first network area through its own external interface. This service invocation configuration information may include the identifier of the second network area and the message types supported by the second network area, so that the first network area can know the message types supported by the second network area. In some examples, in step 203, the first network area may use the message types supported by the second network area to send the first service data to its external interface. In some examples, in step 202, the first network area may use the message types supported by the target network area to send the first request to its external interface.

[0111] In some examples, for any one of multiple network areas, the service invocation configuration information for that network area may include the network area's identifier and the message types it supports. Any network area can send its own service invocation configuration information to other network areas. This allows each network area to know the message types supported by other network areas.

[0112] In one possible application scenario, among multiple network areas, two network areas support different encryption and decryption methods. For example, the first network area supports a first encryption and decryption method, while the second network area supports a second encryption and decryption method. The network area publishing service data can encrypt the provided service data according to the encryption and decryption method supported by the network area calling the service data.

[0113] In one possible implementation, each network area can inform other network areas of the encryption and decryption methods it supports by providing service call configuration information.

[0114] Each network region can provide service invocation configuration information, which may include the identifier of the network region and the encryption / decryption methods supported by the network region. For example, a second network region can send service invocation configuration information to the external interface of a first network region through its own external interface. This configuration information may include the identifier of the second network region and the encryption / decryption methods supported by the second network region, so that the first network region can know the encryption / decryption methods supported by the second network region. In some examples, in step 203, the first network region may use the encryption / decryption methods supported by the second network region to encrypt the first service data and send the encrypted first service data to the external interface of the second network region. In some examples, in step 202, the first network region may use the encryption / decryption methods supported by the target network region to send the first request to the external interface of the target network region.

[0115] In one possible application scenario, among multiple network areas, two network areas support different encryption methods, and two network areas support different message types. In one possible approach, the service call configuration information provided by each network area may include the network area's identifier, the message types it supports, and the encryption / decryption methods it supports. The network area publishing service data can provide the service data to the calling network area after performing message conversion and encryption processing according to the message types and encryption methods supported by the network area calling the service data.

[0116] For example, a second network area can send service call configuration information to the external interface of a first network area through its own external interface. This configuration information may include the identifier of the second network area, the message types supported by the second network area, and the encryption / decryption methods supported by the second network area. This allows the first network area to know the message types and encryption / decryption methods supported by the second network area. In some examples, in step 203, the first network area may encrypt the first service data using the encryption / decryption methods supported by the second network area, and then send the encrypted first service data to the external interface of the second network area using the message types supported by the second network area. In some examples, in step 202, the first network area may send the first request to the external interface of the target network area using the encryption / decryption methods and message types supported by the target network area.

[0117] In one possible implementation, the internal interface of the first network area can receive a second request from the client for second service data. In response to the second request, the first network area can send the second service data to the client through its internal interface. In one example, in response to the client's second request for second service data, the first network area can locate the network area providing the second service data based on the correspondence between service data and network areas. If the network area providing the second service data is the first network area, then the first network area can provide the second service data to the client through its internal interface. If the network area providing the second service data is not the first network area, then the first network area sends a request for the second service data to the network area providing the second service data, that is, it retrieves the second service data from the network area providing the second service data.

[0118] Figure 4 The service data invocation method provided in this application embodiment is illustrated by way of example and can be applied to the second network area side. The method may include the following steps:

[0119] Step 401: Receive the request for the first service data, which is sent by the target client.

[0120] In practice, clients belonging to the second network area can send requests for first service data to the internal interface of the second network area. The second network area can then receive these requests through its internal interface.

[0121] Step 402: Based on the correspondence between service data and network regions, find the target network region that provides the first service data. The target network region represents the network region that publishes the first service data.

[0122] Step 403: If the target network area is not the second network area, then the request for the first service data is sent to the external interface of the first network area.

[0123] In practice, one possible scenario is that the second network zone is unable to provide the service data requested by the target client. The second network zone can then request the service data from the network zone that provides it.

[0124] Step 404: If the target network area is the second network area, then the first service data is sent to the target client.

[0125] In practice, one possible scenario is that the second network area can provide the service data requested by the target client. The second network area can send the requested service data to the target client through an internal interface.

[0126] In one possible implementation, the external interface of the second network area can receive at least one service configuration information. The at least one service configuration information may include service publishing configuration information. The service publishing configuration information may include an identifier for service data and an identifier for the network area providing the service data. The second network area can determine the aforementioned service data and the identifier of the network area based on the service publishing configuration information. The service publishing configuration information can be found in the relevant descriptions in the foregoing embodiments, and will not be repeated here.

[0127] In one possible implementation, at least one service configuration information may include service invocation configuration information. In some examples, the service invocation configuration information may include an identifier of a network area and the message types supported by that network area. In some examples, the service invocation configuration information may include an identifier of a network area and the encryption / decryption methods supported by that network area. In some examples, the service invocation configuration information may include an identifier of a network area, the encryption / decryption methods supported by that network area, and the message types supported by that network area. The service invocation configuration information can be found in the relevant descriptions in the foregoing embodiments, and will not be repeated here.

[0128] Figure 5 An exemplary method for invoking service data is shown, which can be implemented through interaction between a first network area and a second network area. The method may include the following steps:

[0129] Step 501: The second network area receives a request for the first service data.

[0130] In this example, the request for the first service data received by the second network area can come from a client belonging to the second network area. The first network area is used as an example of the network area that publishes the first service data.

[0131] Step 502: The second network region finds the target network region that provides the first service data as the first network region based on the correspondence between service data and network regions.

[0132] Step 503: The second network area sends a request for the first service data to the external interface of the first network area.

[0133] Step 504: In response to the request for first service data received by the external interface of the first network region, the first network region determines the target network region providing the first service data as the first network region based on the correspondence between the service data and the network region.

[0134] Step 505: The first network area sends the first service data to the external interface of the second network area through the external interface of the first network area.

[0135] Optionally, the first network area may use the encryption method and message type of the second network area to send the first service data to the external interface of the second network area.

[0136] Step 506: The second network area sends the first service data to the target client through the internal interface of the second network area.

[0137] Figure 6 An exemplary method for invoking service data is shown, which can be provided by... Figure 3 The interaction between the first, second, and third network regions is achieved. The method may include the following steps:

[0138] Step 601: The third network area receives a request for the second service data.

[0139] In this example, the request for the second service data received by the third network area can come from a client belonging to the third network area. The second network area is used as an example of a network area that publishes the second service data.

[0140] Step 602: Based on the correspondence between service data and network regions, the third network region finds the target network region that provides the second service data as the second network region.

[0141] In this embodiment, the external interface of the third network area can only interact with the external interface of the first network area. The third network area can send requests for second service data to the external interface of the first network area.

[0142] Step 603: The third network area sends a request for second service data to the external interface of the first network area.

[0143] Step 604: In response to the request for second service data received by the external interface of the first network area, the first network area determines the target network area for providing the second service data as the second network area based on the correspondence between service data and network areas.

[0144] Step 605: The first network area sends a request for second service data to the external interface of the second network area through the external interface of the first network area.

[0145] Step 606: In response to the request for second service data received by the external interface of the second network area, the second network area determines the target network area for providing the second service data as the second network area based on the correspondence between the service data and the network area.

[0146] Step 607: The second network area can send the second service data to the external interface of the first network area through the external interface of the second network area.

[0147] Optionally, the second network area may use the encryption method and message type of the first network area to send the second service data to the external interface of the first network area.

[0148] Step 608: The first network area can send the second service data to the external interface of the third network area through the external interface of the first network area.

[0149] Optionally, the first network area may use the encryption method and message type of the third network area to send the second service data to the external interface of the third network area.

[0150] Step 609: The third network area sends the second service data to the target client through the internal interface of the third network area.

[0151] In this application embodiment, a network area may include at least one electronic device, which enables the network area to execute the service data invocation method provided in this application embodiment.

[0152] Furthermore, this application embodiment also provides a service data invocation system, which can implement the service data invocation method provided in this application embodiment. In one possible implementation, the service data publishing method may include the aforementioned multiple network regions. Specifically, a first network region can locate a target network region providing the first service data based on the correspondence between service data and network regions, where the target network region represents the network region providing the first service data. The target network region can send the first service data to an external interface of a second network region, or the target network region can send the first service data to a target client; wherein the second network region is the network region initiating the request for the first service data; and the target client is the client initiating the request for the first service data.

[0153] In one possible application scenario, please combine... Figure 7 The service data retrieval system can be implemented as an electronic system with a high level of security, such as enterprise systems serving the financial sector, including banking, securities, and insurance companies. Electronic systems are divided into internal network zones. For example, an electronic system can be divided into a private cloud zone, a group domain zone, a standard domain zone, and an internet zone. The private cloud zone primarily handles service calls from internal clients, the group domain zone primarily handles service calls from all clients within the parent company, the internet zone primarily handles service calls from clients accessing the service via the internet, and the standard domain zone primarily handles service calls from the internet. When a client in one network zone needs to call a service from another network zone, it may need to make a service call across two or more network zones.

[0154] In one possible design, each network zone can have a technology platform module. This module handles service publishing and service configuration information publishing. Each network zone can have internal and external interfaces. Internal interfaces within each network zone are strictly isolated from other network zones. Each network zone interacts with other network zones through its external interfaces. In one possible implementation, clients or other network zones can invoke services published by the standard domain zone via domain names. Clients or other network zones can access the CLB address via HTTP requests to invoke services published by the group domain zone. Clients or other network zones can invoke services published by the private cloud domain zone using a service bus approach, as required by the private cloud architecture.

[0155] In some examples, in scenarios where the internet region calls services from the private cloud region, the technical platform module of the private cloud region configures the service. This configuration allows configuring decryption methods based on the encryption method of the service requester, and message conversion methods based on the message structure (JSON or XML) between the service requester and the publisher. The private cloud-side external interface is configured with transaction routing, i.e., configuring the routing path connecting to the external interface of the internet region. The internet region's external interface can also be configured with transaction routing, i.e., configuring the routing path to the external interface of the private cloud region. The technical platform module of the internet region configures requests entering via the domain name to be routed to the internet region's external interface. This request then reaches the private cloud region's external interface through the configured transaction routing, enabling the internet region to call services published by the private cloud region. For service publication verification, the service caller needs to directly request the technical platform via the internet, or technical personnel need to initiate the service request using a green light test script through the internet region's technical platform module.

[0156] In one possible design, the technical platform module in each network area includes a configuration center unit. Services published in each network area need to be dynamically registered through the configuration center, which can ensure that the online / offline status of servers in the network area publishing services can be achieved without manual intervention when changes occur (addition, offline, anomalies, etc.).

[0157] The network path configuration direction for service calls between different network zones can be configured based on the network environment of the service publisher and the service caller. Inter-network zones interact through external interfaces. The configuration center in the technology platform module and the routing on the web component of the external interface enable the configuration of the network path direction for service calls between network zones.

[0158] Optionally, the technical platform modules of each network region can support message conversion functions, such as conversion between XML and JSON. Optionally, the technical platform modules of each network region can configure encryption and decryption according to the encryption and decryption methods supported by the network region calling the service. In this embodiment, the encryption and decryption methods may include, but are not limited to, symmetric, asymmetric, and key negotiation encryption and decryption forms. Optionally, after configuration, the technical platform module of the network region calling the service prepares a green light test script to execute the business or perform green light verification.

[0159] Figure 8 A functional block diagram of a network area is shown according to an exemplary embodiment. Network area A may include a technology platform module A, an internal interface A, and an external interface A. The internal interface A may include multiple interface units, which may include an XML access (without security technology) unit A, an XML access (with security technology) unit A, a JSON access (without security technology) unit A, and a JSON access (with security technology) unit A.

[0160] Network area B may include a technology platform module B, an internal interface B, and an external interface B. The internal interface B may include multiple interface units, which may include an XML access (without security technology) unit B, an XML access (with security technology) unit B, a JSON access (without security technology) unit B, and a JSON access (with security technology) unit B.

[0161] When a client in network area A requests service data published by network area B, the client can initiate a service data request through the access unit in internal interface A. The technical platform module A of network area A can send the service data request to the technical platform module B of network area B through external interfaces A and B. The technical platform module B of network area B can process the requested service data according to the message types and encryption / decryption methods supported by network area A, and then provide the service data to the technical platform module A via external interfaces B and A. The technical platform module A can then provide the service data to the client through the access unit in internal interface A.

[0162] When a client in network zone B requests service data published by network zone B, the client can send a service data request to the technology platform module B through the access unit in internal interface B. The technology platform module B can then provide the service data to the client through the access unit in internal interface B.

[0163] In one possible implementation, service configuration information can be stored in multiple network zones. Optional service configuration information may include a service identifier, the network zone publishing the service, the encryption / decryption method of the network zone, and the message conversion format of the network zone. In some examples, the service configuration information may conform to a preset interface URI naming rule. Optionally, the service configuration information may be in the format: service identifier / network zone publishing the service / encryption / decryption method of the network zone / message conversion format of the network zone. For example, http: / / localhost:8101 / A (exposed through zone A) / AES (accessed via AES encryption algorithm) / J2X (message conversion format is JSON to XML); or http: / / localhost:8101 / B (exposed through zone B) / SA (accessed via SA encryption algorithm) / X2J (message conversion format is XML to JSON).

[0164] Optionally, the technical platform module of the network region that calls the service can use the integrated SDK to execute service calls using curl and other methods to simulate the actual service call scenarios of various regions and types for testing, so as to ensure the correctness of service calls and the availability of services after the service is published.

[0165] Based on the same inventive concept, embodiments of this application provide a service data retrieval device, please refer to... Figure 9 The device includes:

[0166] The device includes:

[0167] External interface 901 is used to receive the first request for the first service data;

[0168] Processing unit 902 is used for:

[0169] In response to a first request for the first service data, based on the correspondence between service data and network regions, a target network region providing the first service data is located, wherein the target network region represents the network region that publishes the first service data;

[0170] If the target network area is not the first network area, then the request for the first service data is sent to the external interface 901 of the target network area;

[0171] If the target network area is the first network area, then the first service data is sent to the external interface 901 of the second network area, which is the network area that sent the first request.

[0172] In one possible implementation, the external interface 901 is further configured to: receive at least one service configuration information, wherein the at least one service configuration information includes service publishing configuration information; the service publishing configuration information includes an identifier of target service data and an identifier of a third network area providing the target service data;

[0173] The processing unit 902 is further configured to: determine the correspondence between the service data and the network area based on the service publishing configuration information.

[0174] In one possible implementation, the at least one service configuration information includes service invocation configuration information; the service invocation configuration information includes an identifier of a fourth network area requesting the one service data, and the message types supported by the fourth network area;

[0175] The processing unit 902 sends the first request for the first service data to the external interface 901 of the target network area, and is also used for:

[0176] Using the message types supported by the target network area, the first request is sent to the external interface 901 of the target network area;

[0177] The processing unit 902, which sends the first service data to the external interface 901 of the second network area, is further configured to:

[0178] The first request is sent to the external interface 901 of the second network area using the message type supported by the second network area.

[0179] In one possible implementation, the at least one service configuration information includes service invocation configuration information. The service invocation configuration information includes an identifier of the requested fifth network area and the encryption / decryption methods supported by the fifth network area.

[0180] The processing unit 902, which sends the first service data to the external interface 901 of the second network area, is further configured to:

[0181] The first service data is encrypted using the encryption / decryption method supported by the second network area.

[0182] In one possible implementation, the device further includes:

[0183] Internal interface 903 is used to receive a second request for second service data, wherein the second request is sent by the target client;

[0184] The processing unit 902 is also used to send the second service data to the target client through the internal interface 903.

[0185] Based on the same inventive concept, embodiments of this application provide a service data retrieval device, please refer to... Figure 10 The device includes:

[0186] Internal interface 1001 is used to receive a request for first service data, the request being sent by the target client;

[0187] Processing unit 1002 is used for:

[0188] Based on the correspondence between service data and network regions, the target network region that provides the first service data is located, and the target network region represents the network region that publishes the first service data;

[0189] If the target network area is not the second network area, then the request for the first service data is sent to the external interface 1003 of the first network area;

[0190] If the target network area is the second network area, then the first service data is sent to the target client through the internal interface 1001.

[0191] In one possible design, the device also includes an external interface 1003;

[0192] The external interface 1003 is used for:

[0193] Receive at least one service configuration information, wherein the at least one service configuration information includes service publishing configuration information, the service publishing configuration information includes an identifier of the first service data, and an identifier of the network area providing the first service data;

[0194] The processing unit 1002 is further configured to:

[0195] Based on the service publishing configuration information, the correspondence between the service data and the network region is determined.

[0196] In one possible design, the processing unit 1002 is specifically used to: send a request for the first service data to the external interface 1003 of the first network area through the external interface 1003 in the device.

[0197] Based on the same inventive concept, this application provides an electronic device that can implement the service invocation method described above. Please refer to... Figure 11 The device includes a processor 1101 and a memory 1102.

[0198] The processor 1101, memory 1102, and communication interface 1103 are connected via a bus. The communication interface 1103 is used to communicate with external and internal interfaces, including but not limited to sending and receiving data. The memory 1102 stores a computer program. The processor 1101 executes all or part of the steps of the service data calling method in the above embodiments according to the computer program.

[0199] Examples of this application Figure 11 The processor involved can be a central processing unit (CPU), a general-purpose processor, a graphics processing unit (GPU), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof.

[0200] In one possible implementation, the processor 1101 may respond to a first request for first service data received by the external interface of the first network region, and search for a target network region that provides the first service data based on the correspondence between the service data and the network region, wherein the target network region represents the network region that publishes the first service data.

[0201] If the target network region is not the first network region, then the first request for the first service data is sent to the external interface of the target network region;

[0202] If the target network region is the first network region, then the first service data is sent to the external interface of the second network region, which is the network region that sent the first request.

[0203] In one possible design, the external interface of the first network area receives at least one service configuration information, wherein the at least one service configuration information includes service publishing configuration information; the service publishing configuration information includes an identifier of the target service data and an identifier of the third network area providing the target service data; the processor 1101 can determine the correspondence between the service data and the network area based on the service publishing configuration information.

[0204] In one possible design, the at least one service configuration information includes service invocation configuration information; the service invocation configuration information includes an identifier of a fourth network area requesting the service data, and the message types supported by the fourth network area;

[0205] The processor 1101, which sends the first request for the first service data to the external interface of the target network area, is further configured to:

[0206] The first request is sent to the external interface of the target network area using the message type supported by the target network area.

[0207] The external interface for sending the first service data to the second network area is further used for:

[0208] The first request is sent to the external interface of the second network area using the message type supported by the second network area.

[0209] In one possible design, the at least one service configuration information includes service invocation configuration information. The service invocation configuration information includes an identifier of the requested fifth network area and the encryption / decryption methods supported by the fifth network area.

[0210] The processor 1101, which sends the first service data to the external interface of the second network area, is further configured to:

[0211] The first service data is encrypted using the encryption / decryption method supported by the second network area.

[0212] In one possible design, processor 1101 is also used for:

[0213] In response to a second request for second service data received from the internal interface of the first network area, the second service data is sent to the target client through the internal interface of the first network area, wherein the target client is the client that sent the second request.

[0214] Based on the same inventive concept, this application provides an electronic device that can implement the service invocation method described above. Please refer to... Figure 12 The device includes a processor 1201 and a memory 1202. A second network area may include the electronic device.

[0215] The processor 1201, memory 1202, and communication interface 1203 are connected via a bus. The communication interface 1203 is used to communicate with external and internal interfaces, including but not limited to sending and receiving data. The memory 1202 stores a computer program. The processor 1201 executes all or part of the steps of the service data calling method in the above embodiments according to the computer program.

[0216] In one possible implementation, the processor 1201 is further configured to receive a request for first service data, the request being sent by the target client;

[0217] Based on the correspondence between service data and network regions, the target network region that provides the first service data is located, and the target network region represents the network region that publishes the first service data;

[0218] If the target network area is not the second network area, then the request for the first service data is sent to the external interface of the first network area;

[0219] If the target network area is the second network area, then the first service data is sent to the target client.

[0220] In one possible design, the external interface of the second network area receives at least one service configuration information, wherein the at least one service configuration information includes service publishing configuration information, the service publishing configuration information includes an identifier of the first service data, and an identifier of the network area providing the first service data;

[0221] The processor 1201 can determine the correspondence between the service data and the network area based on the service publishing configuration information.

[0222] Based on the same inventive concept, embodiments of this application provide a computer-readable storage medium. The computer program product includes computer program code, which, when executed on a computer, causes the computer to perform any of the service data invocation methods described above. Since the principle by which the computer-readable storage medium solves the problem is similar to that of the service data invocation method, the implementation of the computer-readable storage medium can be found in the implementation of the method; repeated details will not be elaborated further.

[0223] Based on the same inventive concept, this application also provides a computer program product, which includes computer program code. When the computer program code is run on a computer, it causes the computer to execute any of the service data invocation methods described above. Since the principle by which the above computer program product solves the problem is similar to that of the service data invocation method, the implementation of the above computer program product can be referred to the implementation of the method, and repeated details will not be repeated.

[0224] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0225] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0226] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0227] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of user-operated steps to be executed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0228] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method of service data invocation, characterized by, The application is applied to a first network area side in multiple network areas, the first network area has an external interface and an internal interface, the external interface is isolated from the internal interface, and the internal interface is used for interacting data with a client belonging to the first network area; wherein the multiple network areas include the first network area, a second network area, a third network area and a fourth network area; the external interface of the first network area is in communication with the external interface of each network area; the first network area interacts through the external interface of the first network area and the external interface of each network area; the external interface of the second network area interacts data with the external interface of the first network area and the external interface of the fourth network area; the external interface of the fourth network area interacts data with the external interface of the second network area and the external interface of the first network area; the external interface of the third network area interacts data with the external interface of the first network area; Each network area informs other network areas of service data provided by itself through a service publishing manner; The method comprises: Receiving service configuration information provided by each network area, the service configuration information includes service publishing configuration information, the service publishing configuration information includes an identifier of service data provided by each network area and an identifier of a network area providing the service data; the service configuration information further includes service calling configuration information, the service calling configuration information includes an identifier of each network area, and an encryption mode supported by each network area and a message type; Determining a service data and network area correspondence relationship based on the service publishing configuration information provided by each network area; In response to a first request of first service data received by the external interface of the first network area, finding a target network area providing the first service data based on the service data and network area correspondence relationship, the target network area represents a network area publishing the first service data; wherein the second network area is a network area sending the first request; If the target network area is not the first network area, sending the first request of the first service data to the external interface of the target network area by using a message type supported by the target network area, receiving the first service data provided by the external interface of the target network area, and performing encryption processing on the first service data by using an encryption mode supported by the second network area, and sending the first service data to the external interface of the second network area by using a message type supported by the second network area; If the target network area is the first network area, sending the first service data to the external interface of the second network area.

2. The method of claim 1, wherein, The method further comprises: In response to a second request of second service data received by the internal interface of the first network area, sending the second service data to a target client through the internal interface of the first network area, wherein the target client is a client sending the second request.

3. A method of service data invocation, characterized by, The application is applied to a second network area side in multiple network areas, an external connection interface of the second network area is connected with an external connection interface of a first network area, the first network area has an external connection interface and an internal interface, the external connection interface of the first network area is isolated from the internal interface, and the internal interface is used for interacting data with a client belonging to the first network area; wherein the multiple network areas include the first network area, a second network area, a third network area and a fourth network area; the external connection interface of the first network area is connected with external connection interfaces of each network area; the first network area interacts with external connection interfaces of each network area through the external connection interface of the first network area; the external connection interface of the second network area interacts with the external connection interface of the first network area and the external connection interface of the fourth network area; the external connection interface of the fourth network area interacts with the external connection interface of the second network area and the external connection interface of the first network area; and the external connection interface of the third network area interacts with the external connection interface of the first network area; Each network area in the multiple network areas informs service data provided by itself to other network areas through a service publishing mode; The method comprises: Receiving service configuration information provided by each network area capable of interacting data with the external connection interface of the second network area, the service configuration information including service publishing configuration information, the service publishing configuration information including an identification of service data provided by each network area and an identification of a network area providing the service data; the service configuration information further including service calling configuration information, the service calling configuration information including an identification of each network area, an encryption mode supported by each network area and a message type; Determining a service data and network area corresponding relationship based on the service publishing configuration information provided by each network area; Receiving a request of first service data, the request being sent by a target client; Based on the service data and network area corresponding relationship, searching for a target network area providing the first service data, the target network area representing a network area publishing the first service data; If the target network area is not the second network area, sending the request of the first service data to the external connection interface of the first network area by using a message type supported by the first network area, and receiving the first service data processed by using an encryption mode and a message type supported by the second network area and provided by the external connection interface of the first network area; If the target network area is the second network area, sending the first service data to the target client.

4. A service data calling apparatus, characterized by comprising: The application is applied to a first network area side in multiple network areas; The plurality of network regions comprise the first network region, a second network region, a third network region and a fourth network region; the external interface of the first network region is in communication with the external interfaces of the network regions; the first network region interacts with the external interfaces of the network regions through the external interface of the first network region; the external interface of the second network region interacts with the external interface of the first network region and the external interface of the fourth network region; the external interface of the fourth network region interacts with the external interface of the second network region and the external interface of the first network region; the external interface of the third network region interacts with the external interface of the first network region; Each network region informs other network regions of service data provided by itself through a service publishing manner; The device comprises: An external interface configured to receive a first request for first service data and configured to receive service configuration information provided by the network regions, wherein the service configuration information comprises service publishing configuration information, the service publishing configuration information comprises an identifier of service data provided by the network regions and an identifier of a network region providing the service data, the service configuration information further comprises service calling configuration information, the service calling configuration information comprises an identifier of the network regions, encryption manners supported by the network regions and message types supported by the network regions; The external interface of the device is in communication with the external interfaces of the network regions in the plurality of network regions; the external interface of the device interacts with the external interfaces of the network regions; A processing unit configured to: Determine a service data and network region correspondence relationship based on the service publishing configuration information provided by the network regions; In response to the first request for the first service data, find a target network region providing the first service data based on the service data and network region correspondence relationship, wherein the target network region represents a network region publishing the first service data; the second network region is a network region sending the first request; If the target network region is not the first network region, send the first request for the first service data to the external interface of the target network region in a message type supported by the target network region, receive the first service data provided by the external interface of the target network region, perform encryption processing on the first service data in an encryption manner supported by the second network region and send the first service data to the external interface of the second network region in a message type supported by the second network region; If the target network region is the first network region, send the first service data to the external interface of the second network region, wherein the second network region is a network region sending the first request.

5. The apparatus of claim 4, wherein, The device further comprises: An internal interface configured to receive a second request for second service data, wherein the second request is sent by a target client; The processor is further configured to send the second service data to the target client through the internal interface.

6. A service data calling apparatus characterized by comprising: Be applied to second network area side in multiple network areas; The multiple network areas include a first network area, a second network area, a third network area and a fourth network area; the external connection interface of the first network area is in communication with the external connection interface of each network area; the first network area interacts with the external connection interface of each network area through the external connection interface of the first network area; the external connection interface of the second network area interacts data with the external connection interface of the first network area and the external connection interface of the fourth network area; the external connection interface of the fourth network area interacts data with the external connection interface of the second network area and the external connection interface of the first network area; the external connection interface of the third network area interacts data with the external connection interface of the first network area; Each network area informs other network areas of service data provided by itself through a service publishing manner; The device comprises: An external connection interface is used to receive service configuration information provided by each network area capable of interacting data with the external connection interface of the second network area, the service configuration information includes service publishing configuration information, the service publishing configuration information includes the identification of service data provided by each network area and the identification of the network area providing the service data; the service configuration information further includes service calling configuration information, the service calling configuration information includes the identification of each network area, the encryption mode supported by each network area and the message type; An internal interface is used to receive a request of first service data, the request is sent by a target client; A processing unit is used to: Determine the service data and network area correspondence relationship based on the service publishing configuration information provided by each network area; Find a target network area providing the first service data based on the service data and network area correspondence relationship, the target network area represents a network area publishing the first service data; If the target network area is not the second network area, send the request of the first service data to the external connection interface of the first network area using the message type supported by the first network area, and receive the first service data processed by the encryption mode and the message type supported by the second network area provided by the external connection interface of the first network area; If the target network area is the second network area, send the first service data to the target client through the internal interface.

7. An electronic device, comprising: Comprise: A memory is used to store program instructions; A processor is used to call the program instructions stored in the memory, and execute the steps included in the method according to the obtained program instructions.

8. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a computer program, the computer program includes program instructions, and the program instructions make the computer execute the method when the computer executes the program instructions.

9. A computer program product, characterised in that, The computer program product comprises: computer program code, when the computer program code runs on the computer, so that the computer executes the above-mentioned method as claimed in any one of claims 1-3. The computer program product comprises: computer program code, when the computer program code runs on the computer, so that the computer executes the above-mentioned method as claimed in any one of claims 1-3.

Images