A data center-based distributed resource area deployment method and system

Abstract

The application provides a data center-based distributed resource area deployment method and system, aiming at distributed high availability, using three small data centers focusing on realizing different functions, namely a computing data center, a network data center and a control data center, to combine into a target data center capable of replacing a traditional data center architecture, and respectively deploying infrastructure resources corresponding to different sub-business systems to different small data centers, which is beneficial to realize the security isolation between different sub-business systems and different small data centers, and guarantee the high reliability and high security of the overall application of the target business system.

Description

Technical Field

[0001] This application relates to the field of information technology, and more specifically, to a method and system for deploying distributed resource zones based on data centers. Background Technology

[0002] In existing technologies, enterprises typically deploy the infrastructure resources corresponding to their business systems on a data center in their daily operations. The data center supports the normal operation of the business systems by providing them with infrastructure resources such as computing resources, network resources, and storage resources, as well as various Internet services.

[0003] Currently, the existing traditional data center architecture mainly adopts a single-data-room deployment method. In this method, the infrastructure resources of all sub-business systems in the business system are centrally deployed on the same server in the data center. This means that the computing tasks and data storage of all sub-business systems are completed on this one server. As a result, if the data processing of a single sub-business system is abnormal, the entire business system may become unavailable due to a data center failure. Summary of the Invention

[0004] In view of this, this application provides a distributed resource zone deployment method and system based on a data center. With distributed high availability as the goal, it uses three types of small data centers, namely computing data centers, network data centers, and control data centers, which focus on realizing different functions, to combine into a target data center that can replace the traditional data center architecture. The infrastructure resources corresponding to different sub-business systems are deployed to different of the above-mentioned small data centers, which is conducive to achieving secure isolation between different sub-business systems and different small data centers, and ensuring high reliability and high security of the overall application of the target business system.

[0005] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings.

[0006] In a first aspect, embodiments of this application provide a distributed resource zone deployment method based on a data center, applied in a target data center, the target data center including: a computing data center, a network data center, and a control data center; wherein, the computing data center and the control data center communicate with each other through the network data center within the target data center, and the distributed resource zone deployment method includes:

[0007] Based on the business requirements corresponding to different sub-business systems, the multiple sub-business systems that make up the target business system are grouped to obtain multiple sub-business system combinations; wherein, each sub-business system combination consists of one or more sub-business systems with similar business requirements;

[0008] For each of the sub-business system combinations, if the business requirements corresponding to the sub-business system combination match the computing data center, then the infrastructure resources corresponding to the sub-business system in the sub-business system combination are deployed on the computing data center.

[0009] If the business requirements corresponding to the sub-business system combination match the control data center, then the infrastructure resources corresponding to the sub-business systems in the sub-business system combination are deployed on the control data center.

[0010] Secondly, embodiments of this application provide a distributed resource zone deployment system based on a data center, applied in a target data center, the target data center including: a computing data center, a network data center, and a control data center; wherein, the computing data center and the control data center communicate with each other through the network data center within the target data center, and the distributed resource zone deployment system includes:

[0011] The grouping module is used to group multiple sub-business systems that make up the target business system according to the business requirements corresponding to different sub-business systems, thereby obtaining multiple sub-business system combinations; wherein, each sub-business system combination consists of one or more sub-business systems with similar business requirements;

[0012] The first deployment module is used to deploy the infrastructure resources corresponding to the sub-business systems in each sub-business system combination on the computing data center if the business requirements corresponding to the sub-business system combination match the computing data center.

[0013] The second deployment module is used to deploy the infrastructure resources corresponding to the sub-business systems in the sub-business system combination on the control data center if the business requirements corresponding to the sub-business system combination match the control data center.

[0014] The technical solutions provided by the embodiments of this application may include the following beneficial effects:

[0015] This application provides a distributed resource zone deployment method and system based on a data center. With distributed high availability as the goal, it combines three types of small data centers—computing data centers, network data centers, and control data centers—that focus on implementing different functions into a target data center that can replace the traditional data center architecture. The infrastructure resources corresponding to different sub-business systems are deployed to different of the above-mentioned small data centers, which helps to achieve secure isolation between different sub-business systems and different small data centers, and ensures high reliability and high security for the overall application of the target business system. Attached Figure Description

[0016] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1 This illustration shows a structural diagram of a target data center provided in an embodiment of this application;

[0018] Figure 2 This illustration shows a flowchart of a distributed resource zone deployment method based on a data center, as provided in an embodiment of this application.

[0019] Figure 3 This illustration shows a flowchart of an Internet cabling method applicable within a standardized distributed resource area of ​​each type of data center, as provided in an embodiment of this application.

[0020] Figure 4 This illustration shows a schematic diagram of a distributed resource zone deployment system based on a data center, as provided in an embodiment of this application. Detailed Implementation

[0021] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the accompanying drawings in this application are for illustrative and descriptive purposes only and are not intended to limit the scope of protection of this application. Furthermore, it should be understood that the schematic drawings are not drawn to scale. The flowcharts used in this application illustrate operations implemented according to some embodiments of this application. It should be understood that the operations in the flowcharts may not be implemented in sequence, and steps without logical contextual relationships may be reversed or implemented simultaneously. In addition, those skilled in the art, guided by the content of this application, may add one or more other operations to the flowcharts, or remove one or more operations from the flowcharts.

[0022] Furthermore, the described embodiments are merely some, not all, of the embodiments of this application. The components of the embodiments of this application described and illustrated herein can typically be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0023] It should be noted that the term "comprising" will be used in the embodiments of this application to indicate the presence of the features declared thereafter, but does not exclude the addition of other features.

[0024] Here, the distributed resource zone deployment method provided in this application embodiment can be applied to the target data center. Figure 1 This application provides a schematic diagram of the structure of a target data center, as shown in the embodiment of the present application. Figure 1 As shown, the target data center includes: a computing data center 101, a network data center 102, and a control data center 103. With distributed high availability as the goal, the system explores the smallest possible infrastructure resource deployment units within the data center to form a standardized distributed resource area. This standardized distributed resource area can be further categorized into three types based on function: computing (i.e., computing data center 101), network (i.e., network data center 102), and control (i.e., control data center 103). In other words, in this embodiment, with distributed high availability as the goal, the three types of small data centers—computing data center 101, network data center 102, and control data center 103—that focus on achieving different functions are combined into a target data center capable of replacing the traditional data center architecture.

[0025] like Figure 1 As shown, within the target data center, the computing data center 101 and the control data center 103 communicate via the network data center 102. For the three types of standardized distributed resource areas—computing data center 101, network data center 102, and control data center 103—each emphasizing different functions, standard hardware devices commonly found in data centers, such as servers, network devices, and security devices, can be deployed. However, based on the different functional focuses, the specific number of the same type of functional device deployed in different types of standardized distributed resource areas can vary.

[0026] Specifically, since the computing data center 101 mainly carries the business system operation functions and needs to perform a lot of computing tasks (i.e., focusing on computing functions), as an optional embodiment, in the target data center, the number of computing function devices (e.g., servers) configured in the computing data center 101 is greater than the number of computing function devices configured in the network data center 102 and the control data center 103 respectively (equivalent to the computing data center 101 having the largest number of computing function devices in the target data center).

[0027] Specifically, since the network data center 102 mainly carries the network core and security management functions (i.e., focuses on network functions), as an optional embodiment, in the target data center, the number of network devices (such as firewalls, switches, routers, etc.) configured in the network data center 102 is greater than the number of network devices configured in the computing data center 101 and the control data center 103 respectively (equivalent to the network data center 102 having the largest number of network devices in the target data center).

[0028] Specifically, since the control data center 103 mainly carries out centralized management and control functions and strengthens security management and control (i.e., focuses on control functions), as an optional embodiment, in the target data center, the number of centralized management and control function devices (such as network monitoring devices, access control devices, etc.) configured in the control data center 103 is greater than the number of centralized management and control function devices configured in the computing data center 101 and the network data center 102, respectively.

[0029] Specifically, in terms of software resource deployment, host security, monitoring, and operating system standard software can be deployed in each type of data center's standardized distributed resource area (i.e., computing data center 101, network data center 102, and control data center 103). Middleware, containers, cloud platforms, and storage-based computing software can also be deployed as needed to achieve integrated cloud management of network, computing, and storage resources within each type of data center's standardized distributed resource area, supporting distributed application deployment.

[0030] It should be noted that, in terms of data center deployment, if standardized deployment is the main approach, the same number of racks can be allocated to each type of standardized distributed resource area (i.e., computing data center 101, network data center 102, and control data center 103) in the target data center, based on the rack distribution within the data center. (For example, four rows of racks can be allocated to each type of standardized distributed resource area to form a standard data center standardized distributed resource area, with each three racks serving as a network access unit.) In addition, if standardized deployment is difficult to achieve in the actual data center, different numbers of racks can be allocated to different types of standardized distributed resource areas as needed.

[0031] It should be noted that, taking three racks as a network access unit as an example, the three racks can share one or more sets of access switches. On the access layer, aggregation layer switches can also be deployed. In general, one set of access switches can be deployed for each type of standardized distributed resource area of ​​data center (i.e., computing data center 101, network data center 102, and control data center 103). Furthermore, the internal network and external network can be distinguished in terms of the specific functions of the network access unit.

[0032] To facilitate understanding of the embodiments of this application, the following will be used as examples. Figure 1 Taking the target data center shown as an example, this application provides a detailed description of a distributed resource zone deployment method based on a data center.

[0033] Reference Figure 2 As shown, Figure 2 The illustration shows a flowchart of a data center-based distributed resource zone deployment method provided in an embodiment of this application, wherein the distributed resource zone deployment method can be applied to... Figure 1 In the target data center shown, the distributed resource zone deployment method includes steps S201-S203; specifically:

[0034] S201, based on the business requirements corresponding to different sub-business systems, group the multiple sub-business systems that make up the target business system to obtain a combination of multiple sub-business systems.

[0035] Here, the target business system refers to a complete business system composed of multiple sub-business systems that can cover the entire business processing flow. The types and number of sub-business systems corresponding to the target business system in different fields may be different, and this application embodiment does not impose any limitations on this.

[0036] For example, taking a target business system in the financial field as an example, the sub-business systems that make up the target business system may include, but are not limited to: asset management system, insurance management system, financial settlement system, customer relationship management system, risk monitoring system, automated operation and maintenance system, security management system, etc.

[0037] Specifically, when performing step S201, the similarity between the business requirements corresponding to different sub-business systems can be calculated separately. One or more sub-business systems whose similarity calculation results are less than or equal to a preset similarity threshold are grouped into a sub-business system combination, so that each sub-business system combination consists of one or more sub-business systems with similar business requirements (i.e., the similarity calculation results are less than or equal to the preset similarity threshold).

[0038] S202, for each of the sub-business system combinations, if the business requirements corresponding to the sub-business system combination match the computing data center, then the infrastructure resources corresponding to the sub-business systems in the sub-business system combination are deployed on the computing data center.

[0039] Here, since each sub-business system combination is composed of one or more sub-business systems with similar business needs, the business needs corresponding to each sub-business system combination can be determined based on the business needs corresponding to the sub-business systems that make up each sub-business system combination (equivalent to the business needs corresponding to a sub-business system combination being able to cover the business needs of each sub-business system that makes up that sub-business system combination).

[0040] Specifically, for each sub-business system combination, when the business requirements corresponding to that sub-business system combination involve massive data storage or data computing tasks, it can be determined that the business requirements corresponding to that sub-business system combination are matched with the computing data center, and the infrastructure resources (including but not limited to: computing resources, network resources, and storage resources) corresponding to the sub-business systems in that sub-business system combination are deployed on the computing data center (e.g., Figure 1 As shown, a communication connection is established between the sub-business system and the computing data center 101 to ensure data transmission and communication between the sub-business system and the computing data center 101.

[0041] S203, if the business requirements corresponding to the sub-business system combination match the control data center, then deploy the infrastructure resources corresponding to the sub-business systems in the sub-business system combination on the control data center.

[0042] Specifically, for each sub-business system combination, when the business requirements corresponding to that sub-business system combination involve centralized control tasks with various different management permissions (e.g., access permissions, monitoring management permissions, authentication permissions, etc.), it can be determined that the business requirements corresponding to that sub-business system combination are matched with the control data center, and the infrastructure resources (including but not limited to: computing resources, network resources, and storage resources, etc.) corresponding to the sub-business systems in that sub-business system combination are deployed on the control data center (e.g., ...). Figure 1 As shown, a communication connection is established between the sub-business system and the control data center 103 to ensure data transmission and communication between the sub-business system and the control data center 103.

[0043] It should be noted that, since the network data center 102 is mainly used to carry functions such as network core switching, wide area network access, Internet access, external connection access, and boundary security management, in this embodiment, the network data center 102 is used as an isolation zone between the external network and the internal network of the target data center. The computing data center 101 and the control data center 103 communicate with each other through the network data center 102 to improve the data security performance of the target data center. Furthermore, according to the different functions emphasized by the computing data center 101 and the control data center 103, the infrastructure resources corresponding to the sub-business systems with different business needs are deployed to different small data centers (i.e., computing data center 101 or control data center 103) that are adapted to the functions and business needs. This is conducive to achieving secure isolation between different sub-business systems and different small data centers, and ensuring high reliability and high security of the overall application of the target business system.

[0044] The following section provides a detailed explanation of the network security architecture design for the aforementioned target data center:

[0045] 1. Establish a full network interconnection architecture for the target data center, specifically:

[0046] In this embodiment of the application, in order to achieve full Internet access for the target data center and retain only the necessary external connections, a communication connection between the network data center and external third-party devices can be established through a hybrid cloud private line. The hybrid cloud private line is a dedicated network connection method used to connect the enterprise's local data center (i.e., the target data center) with the aforementioned external third-party devices, providing a high-speed, low-latency, and secure dedicated channel.

[0047] Here, the aforementioned external third-party devices include at least: the client of the target business system (equivalent to the terminal device of any sub-business system that may be used in the business scenario of each sub-business system in the target business system) and the terminal device corresponding to the third-party cloud service provider of the target data center.

[0048] Specifically, if the client of the aforementioned target business system belongs to a special intranet business scenario such as provincial or municipal external connections or an intranet interconnection business scenario between provinces and cities, it can access a hybrid cloud private line between the network data center and external third-party devices based on the Internet VPN or SD-WAN.

[0049] Specifically, if the aforementioned external third-party equipment belongs to the terminal equipment of the target data center's third-party cloud service provider or its headquarters partner, a hybrid cloud leased line can be used to connect the network-type data center and the external third-party equipment.

[0050] 2. Establish a multi-data center ring network architecture for the target data center, specifically:

[0051] In this embodiment of the application, a dual-network dual-plane design concept can be used to introduce multiple operators to build a dual-plane backbone network, thereby avoiding the unavailability of cross-center services due to single operator failure.

[0052] Specifically, when the target data center is a data center within the same city, the computing data center, network data center, and control data center within the target data center can be interconnected using bare fiber wavelength division multiplexing. Among them, one or more target data centers can be deployed in the same city. This application does not limit the specific number of target data centers deployed in the same city.

[0053] Specifically, in addition to deployment within the same city, to improve the regional disaster recovery capability of the target data center, multiple target data centers can be deployed across regions (for example, one target data center can be deployed in city A and another in city B) so as to use geographical separation to ensure the target data center's resilience to catastrophic events. As an optional embodiment, for any two target data centers deployed across regions, they can be interconnected using a point-to-point leased line between the network data centers contained in each of the two target data centers (equivalent to establishing a point-to-point leased line between two network data centers deployed across regions).

[0054] In addition to the hardware deployment architecture design mentioned above, when establishing a multi-data center ring network architecture for the target data center, cross-center traffic orchestration can also be achieved through a software-defined backbone network to ensure service priority and cross-center traffic load balancing.

[0055] It should be noted that the backbone network is dual-plane, with redundancy from multiple operators. In existing technologies, traffic balancing is usually achieved by manually configuring complex commands. However, this manual configuration method makes maintenance difficult and lacks flexibility due to the inability to dynamically adjust.

[0056] Based on this, in this embodiment of the application, by introducing the technology of software-defined backbone network, service channels, routing policies, and automatic distribution policies can be configured on the controller. It can also automatically adjust the service flow according to the load of the line to achieve load balancing (which can be understood as dedicated lines between different operators, through automated means to achieve load adjustment).

[0057] 3. For each type of standardized distributed resource zone in the target data center (i.e., compute data center, network data center, and control data center), deploy independent internet exits as needed on each type of standardized distributed resource zone. Within each type of standardized distributed resource zone, achieve high cohesion across the entire business scenario chain (i.e., ensure that each part of the business process completes only one clearly defined task, thereby improving the readability, reusability, maintainability, and ease of modification of the entire system or application), and low coupling between scenarios. Specifically:

[0058] In this embodiment, independent internet exits can be deployed on the computing data center, network data center, and control data center, respectively. Each of these internet exits is connected to multiple internet lines from different operators, ensuring that each internet exit is connected to at least two operators. This way, even if one operator's internet line fails, each internet exit (i.e., each internet exit) of the computing data center, network data center, and control data center can still maintain normal network communication and data transmission through the connected internet lines of other operators. This allows independent fault domains to isolate the entire business processing flow, achieving secure isolation between different sub-business systems, different business scenarios, and different internet exits. This facilitates distributed deployment, the establishment of independent fault domains, and high system availability.

[0059] Here, as an optional embodiment, Figure 3 This application provides a schematic flowchart illustrating an internet cabling method applicable within a standardized distributed resource area for each type of data center, as illustrated in this embodiment. Figure 3 As shown, the Internet cabling method includes steps S301-S302, specifically:

[0060] S301, for each of the aforementioned Internet exits, multiple optical transmission devices are interconnected with the router corresponding to that Internet exit via a fiber optic distribution frame.

[0061] Here, for each Internet exit (i.e., the Internet exit of the computing data center, network data center, and control data center respectively), the above-mentioned multiple optical transmission devices correspond to multiple different operators accessing that Internet exit. That is, each operator corresponds to one optical transmission device, and the optical transmission devices are interconnected with the router corresponding to the Internet exit through fiber optic distribution frames.

[0062] S302, for each of the optical transmission devices, the optical transmission device is dual-connected to multiple different local exchange nodes of the target operator.

[0063] Here, the target operator refers to the operator corresponding to the optical transmission equipment; each operator's multiple different central office nodes deploy optical cables to the operator access room of the target data center, and the optical transmission equipment corresponding to each operator is also deployed in the operator access room. Based on this, each optical transmission equipment can be dual-connected to multiple different central office nodes of its corresponding operator.

[0064] It should be noted that the aforementioned multiple different central office nodes include, but are not limited to: local offices, tandem offices, gateway offices, and long-distance offices. When deploying optical transmission equipment, operators can ensure network reliability and redundancy by connecting the optical transmission equipment to two different central office nodes. This deployment method provides dual protection for services, ensuring that if one node fails, services can be transmitted normally through another path, thereby maintaining the continuity of network services.

[0065] Specifically, within the target data center, the computing data center and the control data center are interconnected with the network data center via pre-connected optical cables, enabling wired interconnection between standardized distributed resource areas of different types of data centers.

[0066] In this embodiment, each type of standardized distributed resource area of ​​the aforementioned data center is used as the minimum infrastructure resource deployment unit in the target data center. When the infrastructure resources corresponding to any sub-business system in the target business system are abnormal, the target data center can identify the data center with the abnormal infrastructure resources from the computing data center and the control data center as an independent fault domain. The identified fault domain is then isolated in the target data center. This allows for the construction of standardized and modular fault isolation domains by using each type of standardized distributed resource area of ​​the aforementioned data center as a starting point. This strengthens the isolation of risk areas, enables integrated distributed deployment, and allows for module-level construction and phased delivery, providing basic capabilities that can be expanded as needed.

[0067] Based on the above-described distributed resource zone deployment method for data centers provided in this application embodiment, with distributed high availability as the goal, it uses three types of small data centers—computing data centers, network data centers, and control data centers—that focus on implementing different functions to combine into a target data center that can replace the traditional data center architecture. The infrastructure resources corresponding to different sub-business systems are deployed to different of the above-mentioned small data centers, which is conducive to achieving secure isolation between different sub-business systems and different small data centers, and ensuring high reliability and high security of the overall application of the target business system.

[0068] Based on the same inventive concept, this application also provides a distributed resource zone deployment system corresponding to the above-mentioned distributed resource zone deployment method based on data centers. Since the principle of solving the problem in the distributed resource zone deployment system in this application is similar to the above-mentioned distributed resource zone deployment method in this application, the implementation of the distributed resource zone deployment system can refer to the implementation of the above-mentioned distributed resource zone deployment method, and the repeated parts will not be described again.

[0069] Reference Figure 4 As shown, Figure 4 This illustration shows a structural diagram of a data center-based distributed resource zone deployment system provided in an embodiment of this application. The system is applied to a target data center, which includes a computing data center, a network data center, and a control data center. The computing data center and the control data center communicate via the network data center within the target data center. The distributed resource zone deployment system includes:

[0070] Grouping module 401 is used to group multiple sub-business systems that make up the target business system according to the business requirements corresponding to different sub-business systems, so as to obtain multiple sub-business system combinations; wherein, each sub-business system combination consists of one or more sub-business systems with similar business requirements;

[0071] The first deployment module 402 is used to deploy the infrastructure resources corresponding to the sub-business systems in each sub-business system combination on the computing data center if the business requirements corresponding to the sub-business system combination match the computing data center.

[0072] The second deployment module 403 is used to deploy the infrastructure resources corresponding to the sub-business systems in the sub-business system combination on the control data center if the business requirements corresponding to the sub-business system combination match the control data center.

[0073] In an optional implementation, the distributed resource zone deployment system further includes a communication module, wherein the communication module is used for:

[0074] A communication connection is established between the network-based data center and external third-party devices via a hybrid cloud leased line; wherein, the external third-party devices include at least: the client of the target business system and the terminal devices corresponding to the third-party cloud service provider of the target data center.

[0075] In an optional implementation, the distributed resource zone deployment system further includes an internet egress deployment module, wherein the internet egress deployment module is used for:

[0076] Independent Internet exits are deployed on the computing data center, the network data center, and the control data center, and each of the deployed Internet exits is connected to multiple Internet lines from different operators.

[0077] In one optional implementation, the distributed resource zone deployment system further includes a cabling module, wherein the cabling module is used for:

[0078] For each of the aforementioned Internet exits, multiple optical transmission devices are interconnected with the router corresponding to that Internet exit via a fiber optic distribution frame; wherein, the multiple optical transmission devices correspond to the multiple different operators accessing that Internet exit;

[0079] For each of the aforementioned optical transmission devices, the optical transmission device is dual-connected to multiple different central office nodes of the target operator; wherein, the target operator refers to the operator corresponding to the optical transmission device.

[0080] In one alternative implementation, when the target data center is a data center within the same city, the computing data center, the network data center, and the control data center are interconnected using bare fiber wavelength division multiplexing within the target data center.

[0081] In one alternative implementation, for any two target data centers deployed across regions, the network-type data centers contained in each of the two target data centers are interconnected using a point-to-point leased line.

[0082] In one alternative implementation, within the target data center, the computing data center and the control data center are interconnected with the network data center via pre-connected optical cables.

[0083] In an optional implementation, the distributed resource zone deployment system further includes a fault domain determination module, wherein the fault domain determination module is used for:

[0084] In response to an anomaly in the infrastructure resources corresponding to any sub-business system in the target business system, the data center with the abnormal infrastructure resources is identified as an independent fault domain from the computing data center and the control data center, and the identified fault domain is isolated in the target data center.

[0085] In one optional implementation, the number of computing functional devices configured in the computing data center is greater than the number of computing functional devices configured in the network data center and the control data center, respectively.

[0086] The number of network devices configured in the network-type data center is greater than the number of network devices configured in the computing-type data center and the control-type data center, respectively.

[0087] The number of centralized management and control functional devices configured in the control-type data center is greater than the number of centralized management and control functional devices configured in the computing-type data center and the network-type data center, respectively.

[0088] In the embodiments provided in this application, it should be understood that the disclosed systems and methods can be implemented in other ways. The system embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and there may be other division methods in actual implementation. Furthermore, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Additionally, the coupling or direct coupling or communication connection shown or discussed may be through some communication interface; the indirect coupling or communication connection between systems or units may be electrical, mechanical, or other forms.

[0089] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. In addition, the terms "first", "second", "third", etc. are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0090] Finally, it should be noted that the above-described embodiments are merely specific implementations of this application, used to illustrate the technical solutions of this application, and not to limit them. The protection scope of this application is not limited thereto. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some of the technical features, within the scope of the technology disclosed in this application; and these modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application. All should be covered within the protection scope of this application. Therefore, the protection scope of this application should be determined by the protection scope of the claims.

Claims

1. A method for deploying distributed resource zones based on a data center, characterized in that, The method is applied in a target data center, which includes a computing data center, a network data center, and a control data center; wherein the computing data center and the control data center communicate via the network data center within the target data center, and the distributed resource zone deployment method includes: Based on the business requirements corresponding to different sub-business systems, the multiple sub-business systems that make up the target business system are grouped to obtain multiple sub-business system combinations; wherein, each sub-business system combination consists of one or more sub-business systems with similar business requirements; For each of the sub-business system combinations, if the business requirements corresponding to the sub-business system combination match the computing data center, then the infrastructure resources corresponding to the sub-business system in the sub-business system combination are deployed on the computing data center. If the business requirements corresponding to the sub-business system combination match the control data center, then the infrastructure resources corresponding to the sub-business systems in the sub-business system combination are deployed on the control data center.

2. The distributed resource zone deployment method according to claim 1, characterized in that, A communication connection is established between the network-based data center and external third-party devices via a hybrid cloud leased line; wherein, the external third-party devices include at least: the client of the target business system and the terminal devices corresponding to the third-party cloud service provider of the target data center.

3. The distributed resource zone deployment method according to claim 1, characterized in that, Independent Internet exits are deployed on the computing data center, the network data center, and the control data center, and each of the deployed Internet exits is connected to multiple Internet lines from different operators.

4. The distributed resource zone deployment method according to claim 3, characterized in that, The distributed resource zone deployment method also includes: For each of the aforementioned Internet exits, multiple optical transmission devices are interconnected with the router corresponding to that Internet exit via a fiber optic distribution frame; wherein, the multiple optical transmission devices correspond to the multiple different operators accessing that Internet exit; For each of the aforementioned optical transmission devices, the optical transmission device is dual-connected to multiple different central office nodes of the target operator; wherein, the target operator refers to the operator corresponding to the optical transmission device.

5. The distributed resource zone deployment method according to claim 1, characterized in that, When the target data center is a data center within the same city, the computing data center, the network data center, and the control data center within the target data center are interconnected using bare fiber wavelength division multiplexing.

6. The distributed resource zone deployment method according to claim 1, characterized in that, For any two target data centers deployed across regions, the network-type data centers contained in each of the two target data centers are interconnected using a point-to-point leased line.

7. The distributed resource zone deployment method according to claim 1, characterized in that, Inside the target data center, the computing data center and the control data center are interconnected with the network data center via pre-connected optical cables.

8. The distributed resource zone deployment method according to claim 1, characterized in that, The distributed resource zone deployment method also includes: In response to an anomaly in the infrastructure resources corresponding to any sub-business system in the target business system, the data center with the abnormal infrastructure resources is identified as an independent fault domain from the computing data center and the control data center, and the identified fault domain is isolated in the target data center.

9. The distributed resource zone deployment method according to claim 1, characterized in that, The distributed resource zone deployment method also includes: The number of computing functional devices configured in the computing data center is greater than the number of computing functional devices configured in the network data center and the control data center, respectively. The number of network devices configured in the network-type data center is greater than the number of network devices configured in the computing-type data center and the control-type data center, respectively. The number of centralized management and control functional devices configured in the control-type data center is greater than the number of centralized management and control functional devices configured in the computing-type data center and the network-type data center, respectively.

10. A distributed resource zone deployment system based on a data center, characterized in that, The system is applied in a target data center, which includes a computing data center, a network data center, and a control data center; wherein the computing data center and the control data center communicate via the network data center within the target data center, and the distributed resource zone deployment system includes: The grouping module is used to group multiple sub-business systems that make up the target business system according to the business requirements corresponding to different sub-business systems, thereby obtaining multiple sub-business system combinations; wherein, each sub-business system combination consists of one or more sub-business systems with similar business requirements; The first deployment module is used to deploy the infrastructure resources corresponding to the sub-business systems in each sub-business system combination on the computing data center if the business requirements corresponding to the sub-business system combination match the computing data center. The second deployment module is used to deploy the infrastructure resources corresponding to the sub-business systems in the sub-business system combination on the control data center if the business requirements corresponding to the sub-business system combination match the control data center.

Images