A method and apparatus for setting up a cloud network for financial services

By setting up independent network subnets and container network access permissions for financial business processes, the problem of poor container network isolation is solved, achieving highly secure and elastic cloud network management for financial businesses.

CN123123371APending Publication Date: 2026-11-17INDUSTRIAL AND COMMERCIAL BANK OF CHINA
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202610670460.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-05-15
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In existing technologies, container network isolation schemes are based on namespaces and labels, which makes containers within the same network segment reachable from each other. This results in limited security isolation and makes it difficult to meet the high security requirements of financial services.

Method used

Each financial business process is assigned an independent network subnet, and subnet access rules are set up through IP address ranges and network identifiers to ensure that network subnets of different business processes are unreachable from each other. At the same time, containers are assigned dedicated IP addresses and network ports, container network access permissions are set, and load balancing units are deployed within the network subnets for traffic management.

Benefits of technology

It achieves strict network isolation between different financial business processes, improves the security of containers and the elastic scalability of business processes, and ensures the high security level requirements of financial business.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123123371A_ABST
    Figure CN123123371A_ABST
Patent Text Reader

Abstract

This application provides a method and apparatus for setting up a cloud network for financial services, applicable to the field of distributed technology. The method includes: setting up a network subnet for at least one business process deployed in the cloud for financial services; setting up at least one container executing the business process according to the configuration information of the network subnet; and setting container network access permissions for the at least one container executing the business process. This application also provides an electronic device, a storage medium, and a program product.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of distributed technology, and more specifically to a method and apparatus for setting up a cloud network for financial business. Background Technology

[0002] With the rapid development of cloud computing and containerization technologies, enterprises are increasingly adopting container orchestration platforms to deploy microservice applications in cloud environments to improve elasticity and availability. However, the dynamic nature of containers also brings new security challenges: compared to traditional virtual machines, the frequent creation, destruction, and scheduling of container instances make network isolation and fine-grained segmentation more difficult.

[0003] To address this issue, "micro-segmentation" technology has emerged, enabling granular isolation of applications and data in the cloud. In existing technologies, common container network isolation schemes typically rely on namespaces and label partitioning for isolation. This results in containers providing different financial services within the same network segment being mutually reachable; if a container in one deployment is compromised, other containers may also be affected, limiting the effectiveness of security isolation.

[0004] Therefore, a new method and device for setting up a cloud network for financial services is needed. Summary of the Invention

[0005] In view of the above problems, embodiments of this application provide a method and apparatus for setting up a cloud network for financial services.

[0006] According to a first aspect of this application, a method for setting up a cloud network for financial services is provided, characterized in that the method includes: setting up a network subnet for at least one business process of the financial service deployed in the cloud; setting up at least one container for executing the business process according to the configuration information of the network subnet; and setting container network access permissions for the at least one container executing the business process.

[0007] According to an embodiment of this application, setting up a network subnet for at least one business process of financial services deployed in the cloud includes: setting configuration information for the network subnet of the business process, the configuration information including IP address ranges and network identifiers; setting subnet access rules for the network subnet based on the IP address ranges and network identifiers, the subnet access rules including that network subnets corresponding to mutually isolated services cannot communicate with each other.

[0008] According to an embodiment of this application, setting up at least one container to execute the business process based on the configuration information of the network subnet includes: allocating an IP address to the container from the IP address range; and setting the network port of the container based on the IP address.

[0009] According to an embodiment of this application, setting container network access permissions for at least one container executing the business process includes: setting access permissions for a first container executing the business process to a second container that executes the business process.

[0010] According to an embodiment of this application, the method further includes: setting up a load balancing unit for the network subnet corresponding to the business process; and when an access request to access the network subnet is received, the load balancing unit processes the access request based on the operating status of at least one container set up in the network subnet.

[0011] According to an embodiment of this application, the load balancing unit processes the access request based on the operating status of at least one container configured in the network subnet, including: obtaining the operating status of at least one container, the operating status including container abnormality and container availability; and forwarding the access request to a container whose operating status is container availability, so as to process the access request.

[0012] According to a second aspect of this application, a cloud network setup device for financial services is provided, characterized in that the device comprises: a network subnet setup module, used to set a network subnet for at least one business process of financial services deployed in the cloud; a container setup module, used to set at least one container for executing the business process according to the configuration information of the network subnet; and a container network access permission setup module, used to set container network access permissions for at least one container executing the business process.

[0013] According to a third aspect of this application, an electronic device is provided, comprising: one or more processors; and a memory for storing one or more computer programs, wherein the one or more processors execute the one or more computer programs to implement the steps of the method described above.

[0014] According to a fourth aspect of this application, a computer-readable storage medium is also provided, on which a computer program or instructions are stored, wherein the computer program or instructions, when executed by a processor, implement the steps of the above-described method.

[0015] According to a fifth aspect of this application, a computer program product is also provided, including a computer program or instructions that, when executed by a processor, implement the steps of the above-described method. Attached Figure Description

[0016] The above-mentioned contents, other objects, features and advantages of this application will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0017] Figure 1The illustration schematically depicts application scenarios of a financial business cloud network setup method, apparatus, device, medium, and program product according to embodiments of this application.

[0018] Figure 2 A flowchart illustrating a method for setting up a cloud network for financial services according to an embodiment of this application is shown schematically.

[0019] Figure 3 This schematic diagram illustrates a structural block diagram of a financial business cloud network setup device according to an embodiment of this application;

[0020] Figure 4 A block diagram schematically illustrates an electronic device suitable for implementing a cloud network setup method for financial services, according to an embodiment of this application. Detailed Implementation

[0021] The embodiments of this application will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of this application. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of this application for ease of explanation. However, it will be apparent that one or more embodiments may be implemented without these specific details. Furthermore, descriptions of well-known structures and technologies are omitted in the following description to avoid unnecessarily obscuring the concepts of this application.

[0022] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the scope of this application. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0023] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0024] When using expressions such as "at least one of A, B and C", they should generally be interpreted in accordance with the meaning that is commonly understood by those skilled in the art (e.g., "a system having at least one of A, B and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B and C, etc.).

[0025] Figure 1 This illustration schematically depicts an exemplary distributed system architecture 100 that can be applied to the financial business cloud network setup method according to embodiments of this application. It should be noted that... Figure 1 The examples shown are merely examples of the architecture that can be applied to the methods according to the embodiments of this application, in order to help those skilled in the art understand the technical content of this application, but do not imply any limitation on the application scenarios of the embodiments of this application.

[0026] like Figure 1 As shown, the distributed system architecture 100 according to an embodiment of this application may include multiple nodes N1 to N9 and a control center 110.

[0027] For example, nodes N1 to N9 can be computers or software modules, applications, or programs running on computers. Nodes N1 to N9 can communicate and connect with each other in various ways, such as, but not limited to, wired connections, wireless connections, signaling connections, and connections via the Internet. Multiple nodes N1 to N9 can be used to implement one or more services, such as, but not limited to, services related to financial business. Each service provides services for implementing one or more business processes, such as corresponding to a transaction, or corresponding to the identity authentication process or the accounting process in a transaction. Assume that service A is accessed from node N1 and processed sequentially through nodes N4 and N7. Node N7 returns the processing result to node N1 via node N4. Thus, the service link for service A is N1→N4→N7. In the service link for service A, N1 is the upstream application, and N4 and N7 are downstream applications. In a similar manner, each service is processed through corresponding nodes, which form corresponding service links. For example, the service link for service B is N2→N5→N7, the service link for service C is N3→N6→N7, the service link for service D is N2→N5→N8, and the service link for service E is N3→N6→N9.

[0028] Control center 110 is used to configure and manage each node N1 to N9. Control center 110 may include one or more computers. Control center 110 can communicate with each node N1 to N9 in various ways, including but not limited to wired connection, wireless connection, signaling connection, and Internet connection.

[0029] The method according to the embodiments of this application can be executed by the control center 110. Accordingly, the apparatus according to one aspect of the embodiments of this application can be disposed in the control center 110. Optionally, the method according to the embodiments of this application can be executed by any one of a plurality of nodes. Accordingly, the apparatus according to the embodiments of this application can be disposed in any one of the nodes.

[0030] In some embodiments, the method according to the present application can be executed by a computer or computer cluster that is different from the control center 110 and capable of communicating with nodes N1 to N9 and / or the control center 110. Accordingly, the apparatus provided in the present application can also be located in a computer or computer cluster that is different from the control center 110 and capable of communicating with nodes N1 to N9 and / or the control center 110.

[0031] It should be understood that Figure 1 The number of nodes and control centers shown is merely illustrative. Depending on implementation needs, there can be any number of nodes and control centers.

[0032] Figure 2 A flowchart illustrating a method for setting up a cloud network for financial services according to an embodiment of this application is shown. Figure 2 As shown, the financial business cloud network setup method 200 according to an embodiment of this application may include steps 210-230.

[0033] In step 210, a network subnet is set up for at least one business process of the financial business deployed in the cloud; in step 220, at least one container for executing the business process is set up according to the configuration information of the network subnet; in step 230, container network access permissions are set up for at least one container executing the business process.

[0034] According to one implementation, financial business refers to various core and auxiliary businesses carried out by financial institutions, such as core accounting processing, payment settlement, customer identity authentication, credit approval, and transaction clearing. These businesses have high requirements for security and stability. The cloud refers to a virtualized resource platform built on cloud computing technology. Enterprises can build container orchestration platforms in the cloud to deploy and run containerized business applications. The cloud provides elastic scaling and on-demand resource allocation capabilities to meet the computing power needs of financial businesses during peak transaction periods, while also supporting the rapid deployment and iteration of business systems. A business process refers to the standardized sequence of steps required to complete a financial business. A complete financial business can be broken down into multiple independent and orderly sub-processes. Taking a transfer business as an example, the business process can be divided into sub-processes such as user request initiation, pre-authentication, core accounting fund transfer, transaction log recording, and result feedback. Each sub-process can be deployed as an independent unit in the cloud as a corresponding container service cluster. A network subnet specifically refers to a dedicated virtual logical network space allocated to a single financial business process. It is the core carrier for implementing micro-segmentation isolation of containers and has independent and specific configuration information. Container instances for the same business process are connected to the same subnet, while subnets for different business processes are isolated by default. For example, the subnet for the pre-authentication process and the subnet for the core accounting process are independent of each other, which can effectively prevent unauthorized cross-process access and ensure the security of financial data.

[0035] Existing technologies lack sufficient granularity for container network isolation. Container clusters use node / namespace grouping for network isolation, allowing containers within the same network segment to reach each other, resulting in limited security isolation. This application addresses this by setting up a separate network subnet for each business process and configuring each container with resources according to the network subnet configuration information. By establishing separate network subnets for different business processes, the degree of network isolation between them is improved. Furthermore, by configuring containers under each separate network subnet, containers executing different business processes can be isolated from each other, thereby enhancing the security of each container.

[0036] According to one implementation, setting up a network subnet for at least one business process deployed in the cloud for financial services includes: setting up network subnet configuration information for the business process, the configuration information including IP address ranges and network identifiers; setting subnet access rules for the network subnet based on the IP address ranges and network identifiers, the subnet access rules including that network subnets corresponding to mutually isolated services cannot communicate with each other.

[0037] In one implementation, each independent process of a financial transaction is treated as a separate deployment task, such as a pre-approval user authentication process or a core accounting process. When setting up a network subnet, a dedicated IP address range is automatically allocated based on the unique identifier of the transaction, and a network identifier bound to the transaction attributes is generated. The IP address range and network identifier are used as the configuration information for the network subnet. The IP address range is the core network parameter of the virtual network subnet, representing a dedicated IP range allocated to each deployment task corresponding to a financial transaction. Each IP address range can include multiple IP addresses, which can be used to allocate a dedicated IP address to the container executing the transaction. The IP address range predefines the range of IP values ​​for container instances within the subnet, forming the basis for logical isolation and dedicated network resources within the subnet. IP address ranges from different subnets do not overlap.

[0038] The core of the network subnet access rules is to make isolated financial business network subnets unreachable from each other. Taking the core financial accounting system as an example, the subnet for the pre-authentication process and the subnet for the core accounting process will be configured to prevent direct communication. Even if the pre-authentication subnet is attacked, attackers will not be able to enter the core accounting subnet, thus eliminating the risk of lateral movement attacks at the network level. This application sets independent network segments and access rules for each network subnet, improving the isolation and security between different business processes.

[0039] According to one implementation, setting up at least one container for executing a business process based on the configuration information of a network subnet includes: allocating an IP address to the container from an IP address range; and setting up the network port of the container based on the IP address.

[0040] Once the network subnet corresponding to the financial business process is created, it is assigned a dedicated and unique range of IP addresses. When setting up container instances, IP addresses are allocated according to preset address allocation rules. These rules include selecting unused IP addresses from the subnet's dedicated IP address range and assigning them to the container instances to be started. By strictly limiting the range of container IP address values, it ensures that all container instances for the same business process are within the dedicated subnet, preventing IP address conflicts between container instances from different business processes.

[0041] In one implementation, a network port is an independent network identity assigned to a container instance, containing key network attributes such as IP address and MAC address. The network port is strongly bound to the container instance, enabling container-level traffic control, security auditing, and access policy configuration, supporting fine-grained network management operations. After the container IP address is allocated, an independent network port containing complete attributes such as MAC address and port identifier is generated for the container instance, using that IP address as the core. Binding the network port to the container instance gives each container instance a unique and controllable network identity. Based on this network port, operations personnel can configure fine-grained access permission policies for individual containers. Simultaneously, this network port is also used for subsequent implementation of elastic load balancing services, identification of container instance status, and traffic forwarding.

[0042] All container instances within the same financial business process are configured and bound to the network ports of that business's dedicated subnet, thus forming a complete deployment-level logical isolation domain. Within this logical domain, container instances can communicate efficiently through the network ports within the subnet; however, logical domains corresponding to different business processes are in a state of network inaccessibility by default because their respective subnets have different IP address ranges and independent network port attributes.

[0043] Taking the cloud deployment of a financial institution's core transfer business as an example, this business can be broken down into a pre-approval user authentication process and a core account fund transfer process; the pre-approval user authentication process and the core account fund transfer process need to be isolated from each other. In specific implementation, firstly, a virtual network subnet A is created for the pre-approval user authentication process, configured with an IP address range of 10.0.1.0 / 24; a virtual network subnet B is created for the core account fund transfer process, configured with an IP address range of 10.0.2.0 / 24. When starting the container instance carrying the pre-approval function, the cloud network management unit allocates IP addresses (such as 10.0.1.10, 10.0.1.11) from the 10.0.1.0 / 24 address range of subnet A, and configures an independent network port for each container; similarly, the container instance for the core account transfer process will be allocated an IP address from subnet B (such as 10.0.2.10, 10.0.2.11) and bound to a dedicated network port. Subsequently, access rules were configured for the two subnets, restricting communication between subnet A and subnet B by default.

[0044] When an attacker compromises a pre-authentication container within subnet A, the attacker cannot access the core accounting container from subnet A because the IP address ranges of subnet A and subnet B are independent and the network ports are not configured with cross-subnet access permissions. This completely eliminates the risk of bypassing pre-authentication to directly attack the core accounting system, meeting the high security requirements of financial operations. Based on the container's independent network port, operations personnel can configure an access policy for the pre-authentication container in subnet A that "only allows receiving authentication requests from the client," and configure an access policy for the core accounting container in subnet B that "only allows receiving requests authenticated by subnet A," achieving end-to-end network access control for financial business processes.

[0045] When peak transfer periods arrive, more front-end authentication containers and core accounting containers are automatically launched. New containers are automatically assigned IP addresses within their respective subnets and configured with independent network ports. The elastic load balancing service can automatically add these new ports to the backend forwarding pool by recognizing their status. The entire process requires no manual intervention, and the newly added containers fully inherit the security policies of their respective subnets, ensuring that while business expands elastically, there are no security policy gaps.

[0046] According to one implementation, setting container network access permissions for at least one container executing a business process includes: setting access permissions for a first container executing the business process to a second container that executes the business process.

[0047] According to one implementation, the first container and the second container can be specifically implemented as container instances executing the same financial business flow. They can belong to different functional modules of the same business process, or to different business processes with business interaction relationships. The first container is allowed to initiate network access requests to the second container to obtain the functional services or data resources carried by the second container. The container network access permission is a fine-grained access control policy based on the container's independent network identity configuration. This permission is used to set access permissions between different containers executing the same business process. Both the first container and the second container have dedicated network ports, including independent IP addresses, MAC addresses, and network identifiers. When setting container network access permissions, the settings can be made according to the dedicated network ports of the first and second containers. This application improves the flexibility of data flow and business access within a business process without affecting security by allowing different containers within a business process to access each other.

[0048] According to one implementation, a load balancing unit is set up for the network subnet corresponding to the business process; when an access request to access the network subnet is received, the load balancing unit processes the access request based on the operating status of at least one container set up in the network subnet.

[0049] The load balancing unit automatically deploys elastic load balancing services for each network subnet corresponding to a business process. The load balancing unit provides a unified access point to the network subnet. When access to the network subnet corresponding to a business process is needed, an access request is sent to the load balancing unit. The load balancing unit then forwards the access request to the container configured according to the network subnet. An access request refers to a service call request initiated by an external user or upstream / downstream business system for the function carried by the container within the target business process subnet, such as a transaction query request or a fund transfer request in a financial scenario.

[0050] The load balancing unit also enables intelligent traffic distribution. Upon receiving an access request, the load balancing unit retrieves the operational status of all containers within the network subnet, accurately identifying the operational status of each container to achieve intelligent and automated request forwarding. This application achieves elastic load balancing for the containers executing each business process, ensuring that each business process is always available when handling external access requests, and also efficiently processing business access requests.

[0051] According to one implementation, the load balancing unit processes access requests based on the operational status of at least one container configured in the network subnet, including: obtaining the operational status of at least one container, where the operational status includes container malfunction and container availability; and forwarding the access request to a container whose operational status is container availability, so as to process the access request.

[0052] According to one implementation, container operational status includes container anomalies and container availability, which are core status indicators for the load balancing unit to determine whether a container instance has the capacity to handle services. Container availability includes indicators such as instance health checks passing, resource load being within a reasonable range, and core business ports listening normally; container anomalies include indicators such as instance failure and shutdown, health check failure, business port congestion, or resource load exceeding limits.

[0053] The load balancing unit can obtain the operational status of all containers within the network subnet through real-time monitoring or heartbeat detection. Specifically, the load balancing unit can obtain the operational status of each container from its independent network port. For example, the load balancing unit will periodically send probe requests to the container's service port, and combine this with the container's heartbeat feedback information to determine its status as available or abnormal.

[0054] When an external access request reaches the load balancing unit, the load balancing unit performs request forwarding operations based on the obtained container running status. During forwarding, not only are requests forwarded to available containers, but containers with abnormalities are also removed from the backend target pool. Furthermore, the load balancing unit's request forwarding operations are strictly limited to its own network subnet and do not forward traffic across network subnets. This achieves network isolation between business processes and meets the needs of high-security businesses such as those in the financial sector. This application, through load balancing services, ultimately forwards traffic to healthy and available containers, thereby improving the processing efficiency of business requests.

[0055] According to one implementation, a dedicated virtual network subnet F is created for the core securities trading business process, configured with an IP address range of 10.0.6.0 / 24, and independent IP addresses and network ports are assigned to the 20 trading processing containers of this process. The system automatically deploys a load balancing unit for subnet F, assigns a VIP address of 192.168.200.10, and configures listening rules matching the business ports of the trading containers. When an external investor initiates a securities trading request (access request), the request is uniformly sent to the load balancing unit. At this time, the load balancing unit determines, through real-time monitoring or heartbeat detection, that the container with IP address 10.0.6.15 is in an abnormal state due to excessive CPU load and removes it from the backend target pool; the remaining 19 containers are in an available state, and the load balancing unit can evenly forward trading requests to these container instances. When peak trading periods arrive, 10 trading containers can be automatically added. After the new containers complete network port binding, the load balancing unit automatically identifies their availability and adds them to the backend target pool, without requiring manual configuration of other information, thus improving the efficiency of container scaling.

[0056] The mechanism of forwarding requests only to available containers by the load balancing unit completely avoids transaction request failures caused by the anomaly of a single container; the request forwarding strategy based on container operating status enables efficient resource utilization. This application can also forward access requests according to the container load. For example, for available containers with low load, the load balancing unit can allocate more requests; for containers with load approaching the threshold, request allocation can be reduced to prevent containers from entering an abnormal state due to overload, thereby achieving dynamic load balancing of container resources within the subnet.

[0057] The load balancing unit automates the entire process of container status monitoring and backend target pool updates, eliminating the need for manual adjustments to load balancing strategies by operations personnel. Furthermore, all transaction requests must pass through the load balancing unit, hiding the real IP addresses of container instances and preventing attackers from directly accessing transaction containers. Even if the load balancing unit's address is exposed, it cannot bypass the dual protection of subnet isolation and container-specific identities, further enhancing the network security level of cloud-deployed services.

[0058] By setting up a load balancing unit for each network subnet and a network interface for each container, and by monitoring the network interface of the network subnet through the load balancing unit, it is possible to monitor the traffic used by the containers and track the traffic used by each container. When security auditing or log analysis is required, the independent network identity information of each container's network interface can help to quickly locate and track container traffic.

[0059] Based on the above-described method for setting up a cloud network for financial services, embodiments of this application also provide a device for setting up a cloud network for financial services. The following will be combined with... Figure 3 The device is described in detail.

[0060] Figure 3 The diagram illustrates a structural block diagram of a financial business cloud network setup device according to an embodiment of this application.

[0061] like Figure 3 As shown, the financial business cloud network setting device 300 of this embodiment includes a network subnet setting module 310, a container setting module 320, and a container network access permission setting module 330.

[0062] The network subnet setting module 310 is used to set up a network subnet for at least one business process of financial business deployed in the cloud. In one embodiment, the network subnet setting module 310 can be used to perform step 210 described above, which will not be repeated here.

[0063] The network subnet setting module 310 includes a first setting module, which is used to set the configuration information of the network subnet for the business process. The configuration information includes IP address ranges and network identifiers. The second setting module is used to set the subnet access rules of the network subnet according to the IP address ranges and network identifiers. The subnet access rules include that network subnets corresponding to mutually isolated services cannot communicate with each other.

[0064] The container setting module 320 is used to set at least one container for executing business processes according to the configuration information of the network subnet. In one embodiment, the container setting module 320 can be used to perform step 220 described above, which will not be repeated here.

[0065] The container configuration module 320 includes a third configuration module for assigning IP addresses to the container from within the IP address range; and a fourth configuration module for configuring the container's network port based on the IP address.

[0066] The container network access permission setting module 330 is used to set container network access permissions for at least one container executing a business process. In one embodiment, the container network access permission setting module 330 can be used to perform step 230 described above, which will not be repeated here.

[0067] The container network access permission setting module 330 includes a fifth setting module for setting access permissions for a first container executing a business process to a second container executing that business process.

[0068] According to an embodiment of this application, the financial business cloud network setting device 300 further includes a load balancing unit setting module, used to set a load balancing unit for the network subnet corresponding to the business process; and a load balancing unit calling module, used to process the access request based on the running status of at least one container set in the network subnet when an access request to access the network subnet is received.

[0069] According to an embodiment of this application, the load balancing unit calling module includes a running status acquisition module for acquiring the running status of at least one container, including container abnormality and container availability; and an access request forwarding module for forwarding access requests to containers whose running status is container availability, so as to process the access requests.

[0070] According to embodiments of this application, any plurality of modules among the network subnet setting module 310, container setting module 320, and container network access permission setting module 330 can be merged into one module, or any one of these modules can be split into multiple modules. Alternatively, at least part of the functionality of one or more of these modules can be combined with at least part of the functionality of other modules and implemented in one module. According to embodiments of this application, at least one of the network subnet setting module 310, container setting module 320, and container network access permission setting module 330 can be at least partially implemented as hardware circuitry, such as field-programmable gate arrays, programmable logic arrays, systems-on-a-chip, systems-on-a-substrate, systems-on-package, application-specific integrated circuits, or any other reasonable means of integrating or packaging circuitry, or implemented in software, hardware, or firmware, or in any appropriate combination of any of these three implementation methods. Alternatively, at least one of the network subnet setting module 310, container setting module 320, and container network access permission setting module 330 can be at least partially implemented as a computer program module, which, when run, can perform corresponding functions.

[0071] Figure 4 A block diagram schematically illustrates an electronic device suitable for implementing a cloud network setup method for financial services, according to an embodiment of this application.

[0072] like Figure 4 As shown, an electronic device 400 according to an embodiment of this application includes a processor 401, which can perform various appropriate actions and processes according to a program stored in a read-only memory 402 or a program loaded from a storage portion 408 into a random access memory 403. The processor 401 may include, for example, a general-purpose microprocessor, an instruction set processor and / or an associated chipset and / or a dedicated microprocessor. The processor 401 may also include onboard memory for caching purposes. The processor 401 may include a single processing unit or multiple processing units for executing different steps of the method flow according to an embodiment of this application.

[0073] Random access memory 403 stores various programs and data required for the operation of electronic device 400. Processor 401, read-only memory 402, and random access memory 403 are interconnected via bus 404. Processor 401 executes various steps of the method flow according to embodiments of this application by executing programs stored in read-only memory 402 and / or random access memory 403. It should be noted that the programs may also be stored in one or more memories other than read-only memory 402 and random access memory 403. Processor 401 may also execute various steps of the method flow according to embodiments of this application by executing programs stored in said one or more memories.

[0074] According to embodiments of this application, the electronic device 400 may further include an input / output interface 405, which is also connected to a bus 404. The electronic device 400 may also include one or more of the following components connected to the input / output interface 405: an input section 406 including a keyboard, mouse, etc.; an output section 407 including a cathode ray tube, liquid crystal display, etc., and a speaker, etc.; a storage section 408 including a hard disk, etc.; and a communication section 409 including a network interface card, such as a local area network card, modem, etc. The communication section 409 performs communication processing via a network such as the Internet. A drive 410 is also connected to the input / output interface 405 as needed. A removable medium 411, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 410 as needed so that computer programs read from it can be installed into the storage section 408 as needed.

[0075] Embodiments of this application also provide a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs, which, when executed, implement the method according to the embodiments of this application.

[0076] According to embodiments of this application, the computer-readable storage medium can be a non-volatile computer-readable storage medium, such as including but not limited to: portable computer disks, hard disks, random access memory, read-only memory, erasable programmable read-only memory, portable compact disk read-only memory, optical storage devices, magnetic storage devices, or any suitable combination thereof. In embodiments of this application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this application, the computer-readable storage medium may include the read-only memory 402 described above, and / or random access memory 403, and / or one or more memories other than read-only memory 402 and random access memory 403.

[0077] Embodiments of this application also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to cause the computer system to implement the methods provided in the embodiments of this application.

[0078] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and downloaded and installed via communication section 409, and / or installed from removable medium 411. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0079] In embodiments of this application, the computer program can be downloaded and installed from a network via communication section 409, and / or installed from removable medium 411. When the computer program is executed by processor 401, it performs the functions defined in the system of this application embodiment. According to embodiments of this application, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0080] According to embodiments of this application, program code for executing the computer programs provided in the embodiments of this application can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. The program code can be executed entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0081] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0082] Those skilled in the art will understand that the features described in the various embodiments of this application can be combined and / or combined in various ways, even if such combinations or combinations are not explicitly described in this application. In particular, the features described in the various embodiments of this application can be combined and / or combined in various ways without departing from the spirit and teachings of this application. All such combinations and / or combinations fall within the scope of this application.

Claims

1. A method for setting up a cloud network for financial services, characterized in that, The method includes: Set up a network subnet for at least one business process of financial business deployed in the cloud; Configure at least one container to execute the business process based on the configuration information of the network subnet; Set container network access permissions for at least one container that executes the business process.

2. The method according to claim 1, characterized in that, Setting up a network subnet for at least one business process deployed in the cloud for the financial business includes: Configure network subnet information for the business process, including IP address ranges and network identifiers; The subnet access rules for the network subnet are set according to the IP address range and network identifier. The subnet access rules include that network subnets corresponding to mutually isolated services cannot communicate with each other.

3. The method according to claim 2, characterized in that, The step of setting at least one container to execute the service process according to the configuration information of the network subnet includes: Assign an IP address to the container from the IP address range; Configure the network port of the container based on the IP address.

4. The method according to claim 1, characterized in that, Setting container network access permissions for at least one container executing the business process includes: The first container executing the business process is granted access permissions to the second container executing the business process.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: Configure a load balancing unit for the network subnet corresponding to the business process; Upon receiving an access request to access the network subnet, the load balancing unit processes the access request based on the operational status of at least one container configured in the network subnet.

6. The method according to claim 5, characterized in that, The load balancing unit processes the access request based on the operational status of at least one container configured in the network subnet, including: Obtain the operational status of at least one container, including container errors and container availability; The access request is forwarded to a container that is in a container-available state to process the access request.

7. A cloud network setup device for financial services, characterized in that, The device includes: The network subnet setting module is used to set up a network subnet for at least one business process deployed in the cloud for financial services. A container setting module is used to set at least one container for executing the business process according to the configuration information of the network subnet; The container network access permission setting module is used to set container network access permissions for at least one container executing the business process.

8. An electronic device, comprising: One or more processors; Memory, used to store one or more computer programs. The characteristic feature is that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1-6.

9. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1-6.

10. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1-6.