Cloud computing server and cloud computing data center

Abstract

The invention discloses a cloud computing server and a cloud computing data center. The cloud computing server is applied to the field of cloud networks and comprises at least one core module, the core module at least comprises at least one first system-on-chip, the types of different first system-on-chips are different or manufacturers allow different first system-on-chips, and the interface pin definitions of the at least one core module are the same. The core module is at least used for executing a data processing function of the cloud computing server; and the data processor is connected with the at least one core module and is at least used for executing the network function of the cloud computing server. The technical problem of low efficiency of managing, operating and maintaining the cloud computing server in related technologies is solved.

Description

Technical Field

[0001] The present application relates to the field of cloud networks, and more specifically, to a cloud computing server and a cloud computing data center. Background Art

[0002] With the rapid development of edge computing technology, the trend is to migrate computing power to the cloud. However, when migrating computing power to the cloud, the current cloud infrastructure is still based on multi-core central processing units (CPUs) and graphics processing units (GPUs) for data centers. These infrastructures suffer from inconsistent specifications and capabilities, as well as inconsistent management and control standards. This leads to inefficient management and operation of cloud computing servers.

[0003] To address the above-mentioned problems, no effective solutions have been proposed so far. Summary of the Invention

[0004] The embodiments of the present application provide a cloud computing server and a cloud computing data center to at least solve the technical problem of low efficiency in managing and operating cloud computing servers in related technologies.

[0005] According to one aspect of an embodiment of the present application, a cloud computing server is provided, comprising: at least one core module, the core module comprising at least: at least one first system-level chip, different first system-level chips may be of different types or manufacturers, the interface pin definition of at least one core module is the same, the core module is at least used to execute the data processing function of the cloud computing server; a data processor, connected to the at least one core module, and at least used to execute the network function of the cloud computing server.

[0006] According to another aspect of an embodiment of the present application, a cloud computing data center is provided, comprising: any one of the cloud computing servers described above.

[0007] In an embodiment of the present application, a cloud computing server may include: at least one core module, the core module including at least one first system-on-chip (SoC), different types or manufacturers of different first SoCs may be different, the interface pin definitions of at least one core module are the same, and the core module is at least used to perform data processing functions of the cloud computing server; a data processor, connected to the at least one core module, and at least used to perform network functions of the cloud computing server. It is easy to notice that by connecting SoCs of different types or manufacturers to the core module, the same cloud computing server can support multiple different types of SoCs and SoCs from multiple manufacturers. By unifying the interface pin definitions of different core modules and using the data processor to perform the network functions of the cloud computing server, the purpose of unifying the hardware design of the cloud computing server is achieved, thereby achieving the technical effect of enabling rapid deployment of the cloud computing server, thereby solving the technical problem of low efficiency in managing and operating cloud computing servers in related technologies.

[0008] It is easy to notice that the above general description and the following detailed description are merely for the purpose of exemplifying and explaining the present application, and do not constitute a limitation of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0010] Figure 1 This is a hardware structure block diagram of a computer terminal (or mobile device) for implementing a cloud computing server according to an embodiment of the present application;

[0011] Figure 2 is a structural block diagram of a computing environment according to an embodiment of the present application;

[0012] Figure 3 This is a structural block diagram of a service grid according to an embodiment of the present application;

[0013] Figure 4 is a schematic diagram of a cloud computing server according to Example 1 of the present application;

[0014] Figure 5 This is a schematic diagram of an optional cloud computing server architecture according to Example 1 of the present application. DETAILED DESCRIPTION

[0015] In order to enable those skilled in the art to better understand the present invention, the following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.

[0016] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in a sequence other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0017] First, some nouns or terms that appear in the description of the embodiments of the present application are subject to the following interpretations:

[0018] Windows: An operating system for personal computers;

[0019] vSwtich: A high-quality virtual switch that supports multi-layer data forwarding. It plays a similar role to a physical switch in traditional network deployments and can divide LANs, build tunnels, and simulate routing.

[0020] Example 1

[0021] According to an embodiment of the present application, a cloud computing server is provided.

[0022] Figure 1 This is a hardware structure diagram of a computer terminal (or mobile device) of a cloud computing server according to an embodiment of the present application. Figure 1As shown, the computer terminal 10 (or mobile device) may include one or more (illustrated as 102a, 102b, ..., 102n in the figure) processors 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission module 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It will be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components than shown, or with Figure 1 Different configurations shown.

[0023] It should be noted that the one or more processors 102 and / or other data processing circuits described above may generally be referred to herein as "data processing circuitry". The data processing circuitry may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuitry may be a single independent processing module, or may be incorporated in whole or in part into any of the other components of the computer terminal 10 (or mobile device). As described in the embodiments of the present application, the data processing circuitry serves as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0024] The memory 104 can be used to store software programs and modules of application software. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104. The memory 104 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the aforementioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0025] The transmission device 106 is configured to receive or transmit data via a network. A specific example of the aforementioned network may include a wireless network provided by the communications provider of the computer terminal 10. In one embodiment, the transmission device 106 includes a network interface controller (NIC), which can be connected to other network devices via a base station to enable communication with the Internet. In another embodiment, the transmission device 106 may be a radio frequency (RF) module, which is configured to communicate with the Internet wirelessly.

[0026] The display may be, for example, a touch screen liquid crystal display (LCD), which enables a user to interact with a user interface of the computer terminal 10 (or mobile device).

[0027] Figure 1 The hardware structure block diagram shown can be used not only as an exemplary block diagram of the computer terminal 10 (or mobile device), but also as an exemplary block diagram of the server. In an optional embodiment, Figure 2 The block diagram shows the use of the above Figure 1 The computer terminal 10 (or mobile device) is shown as an embodiment of a computing node in the computing environment 201 . Figure 2 is a structural block diagram of a computing environment according to an embodiment of the present application, such as Figure 2 As shown, computing environment 201 includes multiple computing nodes (e.g., servers) (illustrated as 210-1, 210-2, ...) running on a distributed network. Each computing node contains local processing and memory resources, and end user 202 can remotely run applications or store data in computing environment 201. Applications can be provided as multiple services 220-1, 220-2, 220-3, and 220-4 in computing environment 201, representing services "A," "D," "E," and "H," respectively.

[0028] End user 202 can provide and access services through a web browser or other software application on a client. In some embodiments, the provisioning and / or request of end user 202 can be provided to the ingress gateway 230. The ingress gateway 230 may include a corresponding agent to handle the provisioning and / or request for services (one or more services provided in the computing environment 201).

[0029] Services are provided or deployed based on various virtualization technologies supported by the computing environment 201. In some embodiments, services can be provided based on virtual machine (VM)-based virtualization, container-based virtualization, and / or similar methods. Virtual machine-based virtualization can be to simulate a real computer by initializing a virtual machine, executing programs and applications without directly contacting any actual hardware resources. While the virtual machine virtualizes the machine, according to container-based virtualization, a container can be started to virtualize the entire operating system (OS) so that multiple workloads can run on a single operating system instance.

[0030] In an embodiment based on container virtualization, several containers of a service can be assembled into a Pod (e.g., a Kubernetes Pod). Figure 2 As shown, service 220-2 can be equipped with one or more Pods 240-1, 240-2, ..., 240-N (collectively, Pods). A Pod can include a proxy 245 and one or more containers 242-1, 242-2, ..., 242-M (collectively, containers). One or more containers in a Pod handle requests related to one or more corresponding functions of the service. Proxy 245 typically controls network functions related to the service, such as routing and load balancing. Other services can also be equipped with similar Pods.

[0031] During operation, executing a user request from the end user 202 may require calling one or more services in the computing environment 201, and executing one or more functions of a service may require calling one or more functions of another service. Figure 2 As shown, service “A” 220 - 1 receives a user request from end user 202 from ingress gateway 230 , service “A” 220 - 1 may call service “D” 220 - 2 , and service “D” 220 - 2 may request service “E” 220 - 3 to perform one or more functions.

[0032] This computing environment can be a cloud computing environment, where resource allocation is managed by the cloud service provider, allowing for feature development without having to worry about implementing, adjusting, or scaling servers. This computing environment allows developers to execute code in response to events without building or maintaining complex infrastructure. Services can be partitioned to perform a set of functions that can scale independently and automatically, rather than scaling a single hardware device to handle the potential load.

[0033] In another optional embodiment, Figure 3 The block diagram shows the use of the above Figure 1 The computer terminal 10 (or mobile device) is shown as an embodiment of the service grid. Figure 3This is a structural diagram of a service grid according to an embodiment of the present application. Figure 3 As shown, the service grid 300 is mainly used to facilitate secure and reliable communication between multiple microservices. Microservices refer to decomposing an application into multiple smaller services or instances and distributing them to run on different clusters / machines.

[0034] like Figure 3 As shown, the microservices may include application service instance A and application service instance B, which form the functional application layer of the service grid 300. In one embodiment, application service instance A runs in the form of container / process 308 on machine / workload container group 314 (Pod), and application service instance B runs in the form of container / process 310 on machine / workload container group 316 (Pod).

[0035] In one implementation, application service instance A may be a product query service, and application service instance B may be a product ordering service.

[0036] like Figure 3 As shown, application service instance A and grid proxy (sidecar) 303 coexist in machine workload container group 614, while application service instance B and grid proxy 305 coexist in machine workload container 314. Grid proxy 303 and grid proxy 305 form the data plane layer (dataplane) of service grid 300. Grid proxy 303 and grid proxy 305 run as container / process 304 and container / process 306, respectively, and can receive requests 312 for product query services. Bidirectional communication is possible between grid proxy 303 and application service instance A, and between grid proxy 305 and application service instance B. Furthermore, bidirectional communication is possible between grid proxy 303 and grid proxy 305.

[0037] In one embodiment, the traffic of application service instance A is routed to the appropriate destination via grid proxy 303, and the network traffic of application service instance B is routed to the appropriate destination via grid proxy 305. It should be noted that the network traffic mentioned herein includes, but is not limited to, Hypertext Transfer Protocol (HTTP), Representational State Transfer (REST), the high-performance, general-purpose open source framework (Google Remote Procedure Call, gRPC), the open source in-memory data structure storage system (Redis), and other forms.

[0038] In one embodiment, the data plane layer's functionality can be extended by writing custom filters for the proxy (Envoy) in service mesh 300. Service mesh proxy configuration can be designed to enable the service mesh to correctly proxy service traffic, enabling service interoperability and service governance. Mesh proxy 303 and mesh proxy 305 can be configured to perform at least one of the following functions: service discovery, health checking, routing, load balancing, authentication and authorization, and observability.

[0039] like Figure 3 As shown, the service grid 300 also includes a control plane layer. The control plane layer can be a group of services running in a dedicated namespace, and these services are hosted by a hosting control plane component 301 in a machine / workload container group (machine / Pod) 302. Figure 3 As shown, managed control plane component 301 communicates bidirectionally with mesh proxy 303 and mesh proxy 305. Managed control plane component 301 is configured to perform certain control and management functions. For example, managed control plane component 301 receives telemetry data transmitted by mesh proxy 303 and mesh proxy 305 and can further aggregate this telemetry data. Managed control plane component 301 also provides user-oriented application programming interfaces (APIs) to facilitate manipulation of network behavior and to provide configuration data to mesh proxy 303 and mesh proxy 305.

[0040] Under the above operating environment, this application provides Figure 4 Cloud computing servers are shown. Figure 4 Schematic diagram of a cloud computing server according to Example 1 of the present application. Figure 4 As shown, the cloud computing server includes: at least one core module 42 ( Figure 4 A plurality of core modules 42) and a data processor 44 are shown.

[0041] Among them, such as Figure 4As shown, the core module 42 includes at least: at least one first system-level chip 42-1, the types or manufacturers of different first system-level chips are allowed to be different, the interface pin definition of at least one core module is the same, and the core module is at least used to execute the data processing function of the cloud computing server; a data processor 44, connected to at least one core module, and at least used to execute the network function of the cloud computing server.

[0042] The above-mentioned core module may include but is not limited to: a first system-on-chip. Based on the first system-on-chip, the core module can realize the function of data processing for the cloud computing server. The above-mentioned first system-on-chip may be a system-on-chip in the core module, wherein the system-on-chip may be referred to as SoC (System on Chip). It should be noted that due to the different types and manufacturers of different first system chips, different core modules including different first system chips can support system-on-chips of different types or different manufacturers. Furthermore, the cloud computing server disclosed in this application can be applicable to different types of operating systems. The above-mentioned data processor may be referred to as DPU (Data Processing Unit), which can provide different network functions for the cloud computing server. For example, it may include but is not limited to: providing bandwidth of different networks for the cloud computing server, supporting the operation of network virtualization software of the cloud computing server, encapsulating, decapsulating, forwarding, etc. network data packets of the cloud computing server, and performing network functions for managing and controlling the cloud computing server.

[0043] In an optional embodiment, as Figure 4 As shown, the cloud computing server includes: a core module 42 and a data processor 44, and the data processor 44 is connected to at least one core module 42. The number of core modules 42 can be 1 to n, and the specific number is not limited in this embodiment and can be set according to actual needs. The interface pin definition of at least one core module 42 is the same to achieve the effect of unifying the specifications and capabilities of the cloud computing server. The data processor 44 can perform the network functions of the cloud computing server. Figure 4 As shown, core module 42 further includes at least a first system-on-chip 42-1. Different first system-on-chips can be of different types or manufacturers to support the cloud computing server in this application for different types of operating systems. It should be noted that the number of first system-on-chips 42-1 must be consistent with the number of core modules.

[0044] It should be noted that the first system-on-chip mainly adopts the same series of consumer chips, which has low power consumption and high compatibility, and the number of CPU cores can be 8-14 cores. Among them, the first system-on-chip in the embodiment of the present application can be a core chip of ARM and X86 multiple ecosystems, which can support related applications of ARM and X86 at the same time, but is not limited to this.

[0045] In an embodiment of the present application, a cloud computing server may include: at least one core module, the core module including at least: at least one first system-on-chip (SoC), different types or manufacturers of different first SoCs may be different, the interface pin definitions of at least one core module are the same, and the core module is at least used to perform the data processing function of the cloud computing server; a data processor, connected to the at least one core module, and at least used to perform the network function of the cloud computing server. It is easy to notice that by connecting SoCs of different types or manufacturers to the core module, the same cloud computing server can support multiple different types of SoCs and SoCs from multiple manufacturers. By unifying the interface pin definitions of different core modules and using the data processor to perform the network function of the cloud computing server, the purpose of unifying the hardware design of the cloud computing server is achieved, thereby achieving the technical effect of enabling rapid deployment of the cloud computing server, thereby solving the technical problem of low efficiency in managing and operating the cloud computing server in the related art.

[0046] In the above embodiments of the present application, the first system-on-chip includes: a processor, a memory and a first disk; or the first system-on-chip includes: a processor, a memory and a first disk interface, and the first disk interface is connected to the first external disk.

[0047] The above-mentioned processors may include but are not limited to: CPU and GPU. The above-mentioned first disk may be a disk in the first system-level chip. The specific disk type is not limited in this embodiment. In this embodiment, a solid-state drive (SSD) is used as an example for illustration, but is not limited to this. The above-mentioned first disk interface is used to connect to a first external disk, wherein the first external disk may be an external disk connected to the first system-level chip, and the first external disk may be an external disk located in a cloud edge server outside the first system-level chip.

[0048] In an optional embodiment, the first system-level chip may include: a processor, such as a CPU and a GPU, a memory, and multiple first disks, wherein the connection between the first disks is achieved through a patch connector (i.e., patch connection). The first disks are directly packaged in the first system-level chip using patch technology, which can make the structure of the entire system more compact, improve data transmission rate, and possibly reduce power consumption.

[0049] In another optional embodiment, the first system-on-chip may further include: a processor, a memory, and a first disk interface, wherein the first system-on-chip may be connected to the first external disk through the first disk interface.

[0050] In the above embodiments of the present application, at least one core module and a data processor are connected via a high-speed data exchange bus.

[0051] In an optional embodiment, at least one core module and a data processor can be connected via a high-speed data exchange bus. The high-speed data exchange bus is the core channel between the DPU and the core module, and the peripheral component interconnect express (PCIe) standard is uniformly adopted as the hardware connection interface standard. If the high-speed data exchange bus is implemented by a field programmable gate array (FPGA) or other methods, it must support an extensible lightweight link layer protocol (Aurora protocol) for moving data between point-to-point serial links. At the same time, the high-speed channel can be divided into a control link and a data link to meet the service and management requirements of the user plane and the control plane. It should be noted that the high-speed data exchange bus can support data transmission at the 800Gbps level.

[0052] It should be noted that the core module includes the first system-level chip, network card chip, serial port, USB and other components, which are connected to the high-speed data exchange bus with the gold finger Mini PCIe interface. Through the unified interface pin definition, different servers can mix and match different core modules, and different modules can support different first system-level chips.

[0053] In the above embodiments of the present application, the high-speed data exchange bus includes: a control link for transmitting control instructions between at least one core module and a data processor; a data link for transmitting data to be processed and data processing results between at least one core module and a data processor.

[0054] The control link is used to establish a control connection between the core module and the high-speed data exchange bus. It generally supports serial port / USB / network control instructions. These instructions are then sent to the core module and system-level chip through this channel to complete various software and hardware operations. The data link is used to establish a data connection between the module and the high-speed data exchange bus. It is usually supported by a network chip and is used to handle external and internal data exchange related to control instructions.

[0055] In an optional embodiment, the high-speed data exchange bus includes a control link and a data link, wherein the control link is used to transmit control instructions between at least one core module and a data processor, and the data link is used to transmit data to be processed and data processing results between at least one core module and the data processor. For example, the data processor can transmit the data to be processed to at least one core module via the data link, and after processing the data, the at least one core module can return the data processing results to the data processor via the data link.

[0056] In the above embodiments of the present application, the data processor includes at least a switching chip, which is used to provide multiple different network bandwidths.

[0057] The above-mentioned switching chip can provide network bandwidth including but not limited to: N*10G, N*40G, N*25G, N*100G or N*200G, where N is between [1-8].

[0058] In an optional embodiment, the data processor further includes a switching chip configured to provide multiple different network bandwidths. The switching chip also supports the operation of network virtualization software and is responsible for network data packet encapsulation, decapsulation, forwarding, routing tables, and access control lists (ACLs) and security groups.

[0059] In the above embodiment of the present application, the data processor further includes a second system-level chip and a virtual switch, and the switching chip is used to offload and manage the second system-level chip and control the operation of the virtual switch.

[0060] The second system-on-chip mentioned above may be a SoC in a data processor. The virtual switch mentioned above may be a vSwtich.

[0061] In an optional embodiment, the data processor also includes a second system-level chip and a virtual switch, wherein the switching chip is used to unload and manage the second system-level chip. For example, it can support traffic unloading to the second system-level chip, and can also deploy required management and control services to achieve full life cycle management of the hardware, software system, and instance of the second system-level chip, thereby achieving management and control unloading.

[0062] In the above embodiment of the present application, the data processor further includes a first controller, which is used to perform firmware burning and system installation on the data processor.

[0063] The first controller mentioned above may be a baseboard management controller (BMC) in a data processor.

[0064] In an optional embodiment, the data processor further includes a first controller, wherein the first controller is configured to perform firmware burning and system installation on the data processor. For example, firmware burning and system installation on the data processor can be implemented, wherein the system can support multiple operating systems, including but not limited to Windows systems, and can also enable powering on, off, and restarting the data processor.

[0065] In the above embodiment of the present application, the data processor further includes a second disk and a second disk interface. The second disk is a chip of any one of a plurality of specifications. The second disk interface is connected to a second external disk.

[0066] The above-mentioned second disk can be a disk in the data processor, wherein the second disk supports the use of an embedded Multi Media Card (eMMC) or a Universal Flash Storage (UFS) system. The above-mentioned second disk interface is used to connect the second disk, wherein the second external disk can be an external disk located in the cloud computing server and outside the data processor. It should be noted that the second disk interface can include but is not limited to: U.2 / M.2 / SATA disk interface to meet the data disk erasure security requirements.

[0067] In an optional embodiment, the data processor also includes a second disk and a second disk interface, wherein the second disk can be a chip of any one of a plurality of specifications. The specific specifications are not limited in this embodiment, and the data processor can be connected to the second external disk through the second disk interface.

[0068] In another optional embodiment, the data processor may also support compression and decompression, encryption and decryption, and other capabilities.

[0069] In the above embodiment of the present application, the cloud computing server also includes: a second controller, connected to at least one module and a data processor, for controlling the operating status of different components of the cloud computing server and generating operating logs of different components.

[0070] The second controller mentioned above may be a BMC in a cloud computing server.

[0071] In an optional embodiment, the cloud computing server further includes a second controller, wherein the second controller is connected to at least one module and a data processor, and can control the operating status of different components of the cloud computing server, for example, including device management, alarm management, Redfish management, sensor management, power consumption management, fan management, and log management, and can also generate operating logs corresponding to different components based on the control process. In addition, the second controller can also provide Intelligent Platform Management Interface (IPMI) instructions, Redfish interface, and web user interface (WebUI).

[0072] In the above embodiment of the present application, the cloud computing server also includes: a cloud operating system, including: an operating system determined based on the first system-level chip, or a pre-generated operating system.

[0073] In an optional embodiment, the cloud operating system can provide Linux and Windows operating systems based on the first system-on-chip. It can also pre-produce corresponding operating systems based on demand and provide the upper layer with the ability to run multiple instances. The cloud operating system can be based on a custom operating system from a chip company or various open-source and closed-source systems, including domestically produced systems.

[0074] In the above embodiment of the present application, the cloud computing server further includes: multiple power supplies, some of which are redundant power supplies.

[0075] In an optional embodiment, the cloud computing server may further include multiple power supplies, some of which may be redundant power supplies to provide backup power for the cloud computing server. For example, when the cloud computing server has two power supplies, the number of redundant power supplies may be one or zero. When the cloud computing server has three power supplies, the number of redundant power supplies may be one or two, but is not limited thereto. When the cloud computing server has four power supplies, the number of redundant power supplies may be two or one, but is not limited thereto.

[0076] In another optional embodiment, the cloud computing server may also include a management and control service, which provides a management interface to external users via an HTTP server or commands. This includes server module query, module management (power on, power off, power reset, restart), module configuration, image management, and system management (alarm and monitoring).

[0077] In the above embodiments of the present application, the cloud computing server is deployed in a computer room of the edge cloud infrastructure.

[0078] In an optional embodiment, the cloud computing server disclosed in the embodiment of the present application can be deployed in a computer room of the edge cloud infrastructure.

[0079] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0080] This application focuses on protecting a new server architecture and implementation method for edge cloud applications. With the rapid development of edge computing technology, the upward migration of terminal computing power has become a trend, and various products such as the cloudification of Internet of Things (IoT) devices, cloud games, cloud phones, and cloud computers are emerging in an endless stream. The terminal computing power is moved to the cloud, and the current cloud infrastructure used is still multi-core CPUs and GPUs for data centers. It does not show significant advantages in terms of functions, performance, cost, compatibility, and other aspects, which affects the scale of end customers. In order to better meet customer needs, this application proposes a new server architecture design and implementation method for edge cloud scenarios. Based on the server standards of data centers, it adopts a blade-type design, which can support multiple heights from 1U to 8U, and can meet the deployment of various operators' computer rooms at home and abroad. At the same time, this application redefines the original server solution, and unifies the design and implementation of various components and software and hardware capabilities to meet the rapid deployment of edge clouds and customer needs.

[0081] Figure 5 is a schematic diagram of an optional cloud computing server architecture according to Example 1 of the present application, such as Figure 5 As shown in FIG, the cloud computing server includes: a first SoC, a core module, a high-speed data exchange bus, a data processing unit (DPU), a second controller (BMC), multiple power supplies, control and data links and other hardware components, as well as various management and control services, network virtualization, and a cloud operating system. The core module is connected to the DPU, the second BMC, and the multiple power supplies via a high-speed data exchange bus. The functions of each component are described in detail below:

[0082] like Figure 5 As shown, the core module includes: multiple first SoCs of different types or manufacturers, for example, the first SoC of manufacturer A, the first SoC of manufacturer B, and the first SoC of manufacturer C, wherein the first SoC includes: a processor (CPU and GPU), memory (MEM), and a disk (SSD).

[0083] The SoC supports core chips from various ecosystems, including ARM and X86, and can support both ARM and X86 applications. SoCs primarily utilize chips from the same series as consumer chips, offering low power consumption and high compatibility. They feature 8-14 CPU cores and centrally integrate components such as the CPU, memory, and GPU. Disks can be surface-mounted or externally connected. A single server can support multiple different chip types and SoCs from multiple manufacturers.

[0084] Among them, the core module includes SoC, network card chip, serial port, USB and other components, which are connected to the high-speed data exchange bus with the gold finger Mini PCIe interface. Through the unified interface pin definition, a server can be mixed with different core modules, and each module can support different SoC chips.

[0085] The high-speed data exchange bus defines the core channel between the DPU, BMC, and modules, and uniformly adopts PCIe as the standard for hardware connection interfaces. If the high-speed data exchange bus is implemented using FPGA or other methods, it must support the Aurora protocol. At the same time, the high-speed channel can be divided into control links and data links to meet the service and management requirements of the user plane and control plane.

[0086] The control link is used to establish a control connection between the module and the high-speed data exchange bus. It generally supports serial port / USB / network control instructions. These instructions are then sent to the module and SoC through this channel to complete various software and hardware operations. The data link is used to establish a data connection between the module and the high-speed data exchange bus. It is usually supported by a network chip and is used to handle data exchange related to external and internal control.

[0087] The DPU consists of three core components: a switch chip, a second SoC, and the first BMC. It utilizes standard Smart NICs and customized Smart NICs using FPGAs or AISCs. The built-in switch chip can provide network bandwidths of N*10G, N*40G, N*25G, N*100G, or N*200G (N is between 1 and 8), supporting traffic offload. The second SoC supports the operation of network virtualization software and is responsible for network packet encapsulation, decapsulation, forwarding, routing tables, and ACL security groups. Based on the CPU and memory of the second SoC, required management and control services can be deployed to achieve full lifecycle management of the board SoC's hardware, software systems, and instances, enabling management and control offload. The DPU's primary BMC allows for firmware burning and system installation. Support for AliOS, Dragon Lizard, Ubuntu, BSD, and Windows operating systems allows for powering the DPU on and off, as well as rebooting. The DPU supports eMMC and UFS drives, and also provides external U.2 / M.2 / SATA drive interfaces to ensure secure data erasure. The DPU also supports compression and decompression, encryption, and decryption.

[0088] Among them, the second BMC is responsible for providing management functions for various components of the server to users, including device management, alarm management, Redfish management, sensor management, power consumption management, and log management. It can provide IPMI instructions, Redfish interface and WebUI.

[0089] Among them, multiple power supplies support partial power supply redundant power supply, and the redundancy solution supports 1+1 (redundant power supply), 2+1 (redundant power supply), 2+2 (redundant power supply), 2+0 (redundant power supply), but is not limited to this.

[0090] The unified cloud operating system can provide Linux and Windows operating systems based on SoCs, produce corresponding operating systems based on demand, and provide the upper layer with the ability to run multiple instances. The cloud operating system can be based on a custom operating system from a chip company or on various open-source and closed-source systems, including domestically produced systems.

[0091] Among them, the virtual switch vSwtich is a high-quality virtual switch that supports multi-layer data forwarding. It plays a similar role to the physical switch in traditional network deployment and can divide LANs, build tunnels, and simulate routing.

[0092] The management and control service provides a management interface to external users through an HTTP server or commands. It includes server module query, module management (power on, power off, power reset, restart), module configuration, image management, and system management (alarm and monitoring).

[0093] This application unifies the pin specification definitions of core modules to support access to multiple SoCs; introduces the concept of a high-speed data exchange bus to provide high-speed control and data channels for modules / SoCs, network chips, and various components, supporting 800Gbps-level data transmission; introduces DPUs into the new hardware infrastructure of the edge cloud, changes the structural design of existing ARM array servers and PC Farm servers, and unifies the control and data plane bases; unifies the cloud operating system, including the SoC Host OS and GuestOS systems, and the BMC operating system; unifies the management and control interfaces to implement the hardware interfaces and software protocols of the data and control planes.

[0094] This application achieves technical standardization at the hardware and software levels through the unified design of hardware specifications, operating systems, data buses, BMCs, and smart network cards, enabling servers using this patent to achieve significant improvements in performance, cost, stability, and other aspects.

[0095] Example 2

[0096] According to another aspect of an embodiment of the present application, a cloud computing data center is provided, comprising: any one of the cloud computing servers described above.

[0097] The aforementioned cloud computing data center can be a new type of infrastructure deployed at the edge of the network, located between the user end and the centralized cloud data center, and can provide a small, distributed, and user-friendly data center environment. Cloud computing data centers offer advantages such as fast processing speed, low latency, compact size, increased security, increased bandwidth, low operating costs, and ease of maintenance. A cloud computing data center can include multiple cloud computing servers, the specific number of which can be determined based on the actual usage environment and is not limited in this embodiment.

[0098] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0099] In the above embodiments of the present application, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0100] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

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

[0102] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0103] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0104] The above is only a preferred embodiment of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A cloud computing server, characterized in that: include: At least one core module, the core module at least comprising: at least one first system-level chip, the types or manufacturers of different first system-level chips are allowed to be different, at least one of the core modules has the same interface pin definition, and the core module is at least used to perform the data processing function of the cloud computing server; A data processor is connected to at least one of the core modules and is used to execute at least the network function of the cloud computing server.

2. The cloud computing server according to claim 1, characterized in that: The first system-on-chip includes: a processor, a memory and a first disk; or the first system-on-chip includes: the processor, the memory and a first disk interface, and the first disk interface is connected to a first external disk.

3. The cloud computing server according to claim 1, characterized in that: At least one of the core modules and the data processor are connected via a high-speed data exchange bus.

4. The cloud computing server according to claim 3, characterized in that: The high-speed data exchange bus comprises: A control link, used for transmitting control instructions between at least one of the core modules and the data processor; A data link is used to transmit the data to be processed and the data processing results between at least one of the core modules and the data processor.

5. The cloud computing server according to claim 1, characterized in that: The data processor at least includes a switching chip, and the switching chip is used to provide a plurality of different network bandwidths.

6. The cloud computing server according to claim 5, characterized in that: The data processor also includes a second system-level chip and a virtual switch, and the switch chip is used to unload and manage the second system-level chip and control the operation of the virtual switch.

7. The cloud computing server according to claim 5, characterized in that: The data processor further includes a first controller, and the first controller is used for performing firmware burning and system installation on the data processor.

8. The cloud computing server according to claim 5, characterized in that: The data processor further includes a second disk and a second disk interface, the second disk is a chip of any one of a plurality of specifications, and the second disk interface is connected to a second external disk.

9. The cloud computing server according to claim 1, characterized in that: Also includes: The second controller is connected to at least one of the modules and the data processor, and is used to control the operating status of different components of the cloud computing server and generate operating logs of the different components.

10. The cloud computing server according to claim 1, characterized in that: Also includes: The cloud operating system includes: an operating system determined based on the first system-level chip, or a pre-generated operating system.

11. The cloud computing server according to claim 1, characterized in that: Also includes: Multiple power supplies, some of which are redundant power supplies.

12. A cloud computing data center, characterized in that: include: The cloud computing server according to any one of claims 1 to 11.

Images