Information transmission method and apparatus

Abstract

An information transmission method and apparatus. The information transmission method comprises: a first device determines resource requirement information, the resource requirement information being used for indicating a requirement of the first device for a required BM resource, and the resource requirement information comprising one or more of the following: a real-time performance requirement, a pooling requirement, a sharing requirement, a security requirement, and a mobility requirement; the first device sends the resource requirement information to a second device; and the second device allocates to a BM resource instance a BM resource meeting the resource requirement information. Therefore, the BM resource allocated by the second device to the BM resource instance meets the requirement of the first device for the BM resource. The requirement indicated by the resource requirement information may be a requirement of a telecommunication cloud application for the BM resource. Therefore, the method facilitates the second device to deploy a BM resource instance meeting a requirement of the telecommunication cloud application for differentiation of BM resources.

Description

Information transmission method and device

[0001] This application claims priority to Chinese Patent Application No. 202311348112.1, filed on October 16, 2023, entitled "Information Transmission Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to an information transmission method and apparatus. Background Technology

[0003] Cloud-native is a system implementation paradigm for building, running, and managing software in a cloud environment. It makes full use of cloud infrastructure and platform services, adapts to the cloud environment, and is an architectural practice with key characteristics such as (micro)services, elastic scaling, distributed architecture, high availability, multi-tenancy, and automation.

[0004] In cloud-native scenarios within the telecommunications sector, bare metal (BM) resource instances can be deployed and their lifecycle management (LCM) performed to allocate BM resources to network elements. These network elements can then use the allocated BM resources to execute telecommunications cloud applications. How to deploy BM resource instances is a technical problem that needs to be solved.

[0005] Summary of the Invention

[0006] This application provides an information transmission method and apparatus that can deploy BM resource instances that match the differentiated needs of telecom cloud applications for BM resources.

[0007] Firstly, this application provides an information transmission method. This method can be applied to a first device, a chip within the first device, or a logic module or software capable of implementing all or part of the functions of the first device. The following description uses a first device as an example. The method includes: the first device determining resource requirement information, which indicates a demand for required BM resources. The resource requirement information includes one or more of the following: real-time requirements, pooling requirements, sharing requirements, security requirements, and mobility requirements. The first device sends the resource requirement information to a second device, which is used to allocate BM resources for BM resource instances.

[0008] As can be seen, in this method, the first device sends its required BM resource needs to the second device, which facilitates the second device in allocating BM resources to BM resource instances that meet the first device's needs. The resource requirement information can indicate the BM resource needs of a telecom cloud application, and this method allows the second device to deploy BM resource instances that match the differentiated BM resource needs of the telecom cloud application.

[0009] In one alternative implementation, real-time requirements are used to indicate whether the required BM resources need to support real-time applications.

[0010] In one alternative implementation, pooling requirements are used to indicate whether the required BM resources need to be selected from pooled resources.

[0011] In one alternative implementation, shared requirements are used to indicate whether the required BM resources need to be occupied by a specific tenant or need to be shared by multiple tenants.

[0012] In one optional implementation, the first device determines resource requirement information, including: the first device receiving network service lifecycle management requirement information; and the first device determining resource requirement information based on the network service lifecycle management requirement information. It is evident that the first device converts network service lifecycle management requirements into requirements for BM resources, which helps the second device allocate BM resources to BM resource instances to meet the differentiated resource requirements of network services.

[0013] In one optional implementation, resource requirement information is carried in a first request message sent to the second device; the first request message also includes resource specification information, which indicates the resource specification requirements for the BM resource instance. This approach is advantageous because the BM resource instance determined by the second device not only meets the resource requirement information but also satisfies the resource specification requirements of the first device for the BM resource instance.

[0014] In one alternative implementation, the first request message is sent to the second device using a declarative application programming interface (API); the first request message also includes expected status information indicating the expected status of the BM resource instance. Using a declarative API simplifies interoperability between the first and second devices, thereby reducing the probability of errors due to multiple interoperations and reducing the complexity of root cause localization and resolution of BM resource-related faults.

[0015] In one optional implementation, the first request message is sent to the second device via a command API; the first request message is used to request the second device to create a BM resource instance. The method further includes: the first device receiving a response message from the second device via a command API, the response message including identification information of the BM resource instance created by the second device.

[0016] In one alternative implementation, the first request message is sent to the second device via a command API; the first request message is used to request the second device to perform an operation on the BM resource instance. The method further includes: the first device receiving a response message from the second device via a command API.

[0017] Secondly, this application provides an information transmission method. This method can be applied to a second device, a chip within the second device, or a logic module or software capable of implementing all or part of the functions of the second device. The following description uses a second device as an example. The method includes: the second device receiving resource requirement information from a first device. The resource requirement information indicates the first device's demand for necessary BM resources. The resource requirement information includes one or more of the following: real-time requirements, pooling requirements, sharing requirements, security requirements, and mobility requirements. The second device allocates BM resources that satisfy the resource requirement information to BM resource instances.

[0018] It is evident that the BM resources allocated by the second device to the BM resource instance satisfy the BM resource requirements of the first device. The resource requirement information indicates the BM resource needs of the telecom cloud application, enabling the second device to deploy BM resource instances that match the differentiated BM resource needs of the telecom cloud application.

[0019] In one alternative implementation, the real-time requirement is used to indicate whether the BM resources required by the first device need to support real-time applications.

[0020] In one alternative implementation, pooling requirements are used to indicate whether the BM resources required by the first device need to be selected from pooled resources.

[0021] In one alternative implementation, the shared requirement is used to indicate whether the BM resources required by the first device need to be occupied by a specific tenant or need to be shared by multiple tenants.

[0022] In one optional implementation, resource requirement information is carried in a first request message received from a first device; the first request message also includes resource specification information, which indicates the resource specification requirements of the first device for the BM resource instance. The second device allocates BM resources that satisfy the resource requirement information to the BM resource instance, including: the second device allocating BM resources that satisfy both the resource requirement information and the resource specification information to the BM resource instance.

[0023] In one alternative implementation, the first request message is received from a first device via a declarative API; the first request message also includes expected state information, which indicates the first device's desired state for the BM resource instance. The desired state is the state of the BM resource instance that has been allocated BM resources that meet the resource requirement information and resource specification information. Using a declarative API simplifies interoperability between the first and second devices, thereby reducing the increased probability of errors due to multiple interoperations, and reducing the complexity of root cause localization and resolution of BM resource-related faults.

[0024] Optionally, the second device allocates BM resources that meet the resource requirement information and resource specification information to the BM resource instance, including: the second device selects a template and configuration file that match the resource requirement information and resource specification information for the BM resource instance; the second device, based on the difference between the current state and the expected state of the BM resource instance, determines to perform one or more of the following operations: add BM resources, read BM resources, update BM resources, and delete BM resources.

[0025] In one optional implementation, the first request message is received from a first device via a command API; the first request message is used to request the creation of a BM resource instance. The second device allocates BM resources that meet the resource requirement information and resource specification information to the BM resource instance, including: the second device selecting a template and configuration file that match the resource requirement information and resource specification information; and the second device creating a BM resource instance that meets the allocated BM resources based on the selected template and configuration file. The method further includes: the second device sending a response message to the first device via a command API, the response message including identification information of the created BM resource instance.

[0026] In one optional implementation, the first request message is received from a first device via a command API; the first request message requests an operation for a BM resource instance. The second device allocates BM resources to the BM resource instance that meet the resource requirement information and resource specification information, including: the second device selecting a template and configuration file that match the resource requirement information and resource specification information; and the second device performing the operation requested by the first request message for the BM resource instance based on the selected template and configuration file. The method further includes: the second device sending a response message to the first device via a command API.

[0027] Thirdly, this application provides an information transmission method, which is described using the interaction between a first device and a second device as an example. The first device in this method can also be replaced by a chip in the first device, or a logic module or software capable of implementing all or part of the functions of the first device. The second device in this method can also be replaced by a chip in the second device, or a logic module or software capable of implementing all or part of the functions of the second device. The method includes: the first device determining resource requirement information, which indicates the first device's demand for required BM resources, and the resource requirement information includes one or more of the following: real-time requirements, pooling requirements, sharing requirements, security requirements, and mobility requirements; the first device sending the resource requirement information to the second device; the second device receiving the resource requirement information from the first device; and the second device allocating BM resources that satisfy the resource requirement information to BM resource instances.

[0028] As can be seen, in this method, the first device sends its requirement for BM resources to the second device, and the second device can allocate BM resources to BM resource instances that meet the requirements of the first device. The resource requirement information can indicate the BM resource requirements of a telecom cloud application, thus enabling the second device to deploy BM resource instances that match the differentiated BM resource requirements of the telecom cloud application.

[0029] In one alternative implementation, the real-time requirement is used to indicate whether the BM resources required by the first device need to support real-time applications.

[0030] In one alternative implementation, pooling requirements are used to indicate whether the BM resources required by the first device need to be selected from pooled resources.

[0031] In one alternative implementation, the shared requirement is used to indicate whether the BM resources required by the first device need to be occupied by a specific tenant or need to be shared by multiple tenants.

[0032] In one optional implementation, the first device determines resource requirement information, including: the first device receiving service requirement information; and the first device determining resource requirement information based on the service requirement information.

[0033] In one optional implementation, resource requirement information is carried in a first request message sent by the first device to the second device; the first request message also includes resource specification information, which indicates the resource specification requirements for the BM resource instance. The second device allocates BM resources that satisfy the resource requirement information to the BM resource instance, including: the second device allocating BM resources that satisfy both the resource requirement information and the resource specification information to the BM resource instance.

[0034] In one alternative implementation, the first request message is sent by the first device to the second device using a declarative API; the first request message also includes expected state information, which indicates the expected state of the BM resource instance. The expected state is the state of the BM resource instance that has been allocated BM resources that meet the resource requirement information and resource specification information.

[0035] Optionally, the second device allocates BM resources that meet the resource requirement information and resource specification information to the BM resource instance, including: the second device selects a template and configuration file that match the resource requirement information and resource specification information for the BM resource instance; the second device, based on the difference between the current state and the expected state of the BM resource instance, determines to perform one or more of the following operations: add BM resources, read BM resources, update BM resources, and delete BM resources.

[0036] In one optional implementation, the first request message is sent by the first device to the second device using a command API; the first request message is used to request the second device to create a BM resource instance. The second device allocates BM resources that meet the resource requirement information and resource specification information to the BM resource instance, including: the second device selecting a template and configuration file that match the resource requirement information and resource specification information; and the second device creating a BM resource instance that meets the allocated BM resources based on the selected template and configuration file. The method further includes: the second device sending a response message to the first device using a command API, the response message including the identification information of the created BM resource instance; and the first device receiving the response message from the second device using a command API.

[0037] In one optional implementation, the first request message is sent to the second device via a command API; the first request message requests the second device to perform an operation on the BM resource instance. The second device allocates BM resources to the BM resource instance that meet the resource requirement information and resource specification information, including: the second device selecting a template and configuration file that match the resource requirement information and resource specification information; and the second device performing the operation requested by the first request message on the BM resource instance based on the selected template and configuration file. The method further includes: the second device sending a response message to the first device via a command API; and the first device receiving the response message from the second device via a command API.

[0038] Furthermore, the beneficial effects of the above-mentioned optional embodiments can be found in the relevant content of the first and second aspects above, and will not be described in detail here.

[0039] Fourthly, this application also provides a communication device. This communication device can be a first device or a second device, or a chip in the first device or the second device, or a logic module or software capable of implementing all or part of the functions of the first device or the second device. This communication device has the function of implementing some or all of the embodiments described in the first or second aspect above. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0040] In one possible design, the communication device may include a processing unit and a communication unit. The processing unit is configured to support the communication device in performing the corresponding functions described in the above-described method. The communication unit supports communication between the communication device and other communication devices. The communication device may also include a storage unit coupled to the processing unit and the communication unit, which stores necessary program instructions and data for the communication device. Additionally, the processing unit may be used to control the communication unit to transmit and receive data / signaling.

[0041] In one embodiment, a processing unit is configured to determine resource requirement information, which indicates the need for required BM resources. The resource requirement information includes one or more of the following: real-time requirements, pooling requirements, sharing requirements, security requirements, and mobility requirements. A communication unit is configured to send the resource requirement information to a second device, which is used to allocate BM resources to BM resource instances.

[0042] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the first aspect above, and will not be described in detail here.

[0043] In another embodiment, a communication unit is configured to receive resource requirement information from a first device. This resource requirement information indicates the first device's need for required BM resources. The resource requirement information includes one or more of the following: real-time requirements, pooling requirements, sharing requirements, security requirements, and mobility requirements. A processing unit is configured to allocate BM resources that satisfy the resource requirement information to BM resource instances.

[0044] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the second aspect above, and will not be described in detail here.

[0045] As an example, the communication unit can be a transceiver or a communication interface, the storage unit can be a memory, and the processing unit can be a processor. The processor is coupled to the memory, which stores programs or instructions for the processor. The processor can be used to cause the communication device to perform the methods described in the first or second aspect above when the program or instructions are executed by the processor. The transceiver or communication interface can be used to send and receive signals and / or data.

[0046] In one implementation, a processor is configured to determine resource requirement information, which indicates a need for required BM resources. The resource requirement information includes one or more of the following: real-time requirements, pooling requirements, sharing requirements, security requirements, and mobility requirements. A transceiver is configured to send the resource requirement information to a second device, which is used to allocate BM resources for BM resource instances.

[0047] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the first aspect above, and will not be described in detail here.

[0048] In another implementation, a transceiver is used to receive resource requirement information from a first device. This resource requirement information indicates the first device's need for required BM resources, and includes one or more of the following: real-time requirements, pooling requirements, sharing requirements, security requirements, and mobility requirements. A processor is used to allocate BM resources that satisfy the resource requirement information to BM resource instances.

[0049] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the second aspect above, and will not be described in detail here.

[0050] In another embodiment, the communication device is a chip or chip system. The processing unit may also be a processing circuit or logic circuit; the transceiver unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system.

[0051] In implementation, the processor can be used for, but is not limited to, baseband-related processing, and the transceiver or communication interface can be used for, but is not limited to, radio frequency transceiver. The aforementioned devices can be disposed on separate chips, or at least partially or entirely on the same chip. For example, the processor can be further divided into analog baseband processors and digital baseband processors. The analog baseband processor can be integrated with the transceiver (or communication interface) on the same chip, while the digital baseband processor can be disposed on a separate chip. With the continuous development of integrated circuit technology, more and more devices can be integrated on the same chip. For example, a digital baseband processor can be integrated with multiple application processors (e.g., but not limited to graphics processors, multimedia processors, etc.) on the same chip. Such a chip can be called a System on a Chip (SoC). Whether the various devices are disposed independently on different chips or integrated on one or more chips often depends on the needs of the product design. This application does not limit the implementation form of the aforementioned devices.

[0052] Fifthly, this application also provides a processor for executing the various methods described above. In executing these methods, the processes of sending and receiving the signals described above can be understood as the process of the processor outputting the signals and the process of the processor inputting the signals. When outputting the signals, the processor outputs the signals to a transceiver for transmission by the transceiver (or communication interface). After being output by the processor, the signals may require further processing before reaching the transceiver (or communication interface). Similarly, when the processor receives the input signals, the transceiver (or communication interface) receives the signals and inputs them to the processor. Furthermore, after the transceiver (or communication interface) receives the signals, the signals may require further processing before being input to the processor.

[0053] Unless otherwise specified, or unless it contradicts its actual function or internal logic in the relevant description, the transmission and reception operations involved by the processor can be more generally understood as processor output and reception, input and other operations, rather than transmission and reception operations directly performed by radio frequency circuits and antennas.

[0054] In implementation, the processor can be a dedicated processor for executing these methods, or it can be a processor that executes computer instructions stored in memory to execute these methods, such as a general-purpose processor. The memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same chip or disposed on different chips. This application does not limit the type of memory or the arrangement of the memory and the processor.

[0055] Sixthly, this application also provides a communication system comprising the first and second devices described above. In another possible design, the system may further include other devices that interact with the first and / or second devices as provided in this application.

[0056] In a seventh aspect, this application provides a computer-readable storage medium storing a computer program that, when run, causes the methods described in the first or second aspect above to be executed.

[0057] Eighthly, this application also provides a computer program product including instructions, the computer program product comprising: computer program code, which, when executed, causes the methods described in the first or second aspect above to be performed.

[0058] Ninthly, this application provides a chip system including a processor and an interface. The interface is used to acquire programs or instructions, and the processor is used to invoke the programs or instructions to implement the functions involved in the first or second aspect. In one possible design, the chip system further includes a memory for storing program instructions and data necessary for the terminal. This chip system may be composed of chips or may include chips and other discrete devices. Attached Figure Description

[0059] Figure 1 is a schematic diagram of a network function virtualization (NFV) architecture;

[0060] Figure 2 is a schematic diagram of the structure of a communication system provided in an embodiment of this application;

[0061] Figure 3 is a schematic diagram of another communication system provided in an embodiment of this application;

[0062] Figure 4 is a flowchart illustrating an information transmission method provided in an embodiment of this application;

[0063] Figure 5 is a schematic diagram of another information transmission method provided in an embodiment of this application;

[0064] Figure 6 is a schematic diagram of another information transmission method provided in an embodiment of this application;

[0065] Figure 7 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0066] Figure 8 is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0067] The embodiments of this application are described below with reference to the accompanying drawings.

[0068] First, in order to better understand the information transmission method disclosed in the embodiments of this application, the communication system applicable to the embodiments of this application will be described.

[0069] The technical solutions of this application can be applied to various communication systems. For example, the Global System for Mobile Communications (GSMA), Long Term Evolution (LTE) system, Universal Mobile Communications System (UMS), 4th generation (4G) system, 4.5th generation (4.5G) system, 5th generation mobile networks (5G) system, and with the continuous development of communication technology, the technical solutions of this application can also be used in subsequent evolved communication systems, such as 6th generation (6G) system, 7th generation (7G) system, and so on.

[0070] Please refer to Figure 1, which is a schematic diagram of an NFV architecture. The NFV architecture includes an operational support system (OSS) / business support system (BSS), element management (EM), virtual network function (VNF), NFV infrastructure (NFVI), and NFV management and orchestration (MANO). NFVI includes a hardware resource layer, a virtualization layer, and a virtual resource layer. Optionally, NFVI may also include a container infrastructure service (CIS) / CIS cluster and a wide area network (WAN).

[0071] The NFV MANO includes the NFV orchestrator (NFVO), VNF manager (VNFM), container infrastructure service management (CISM), container cluster management (CIS cluster management (CCM), container image registry (CIR), virtualized infrastructure manager (VIM), WAN infrastructure manager (WIM), as well as descriptions of network services, VNFs, and infrastructure.

[0072] OSS / BSS is primarily geared towards telecommunications service operators, providing comprehensive network management and service operation functions, including network management (such as fault monitoring and network information collection), billing management, and customer service management. OSS / BSS communicates with NFVO via the Os-Ma-nfvo interface.

[0073] The EM is used to configure and manage the functionality of the VNF. The EM communicates with the VNFM through the Ve-Vnfm-em interface.

[0074] Virtual Network Functions (VNFs) are used to implement various network functions through software, such as virtual firewalls and virtual switches. The resources required by a VNF are decomposed into virtual compute / storage / network resources, which are carried by NFVIs. VNFs communicate with VNFMs via the Ve-Vnfm-vnf interface.

[0075] NFVO can be used to implement network services (NS), execute resource-related requests from VNFM, send configuration information to VNFM, and collect VNF ​​status information. NFVO and VNFM communicate via the Or-Vnfm interface. Additionally, NFVO can communicate with VIM via the Or-Vi interface to allocate or reserve resources and exchange configuration and status information of virtualization hardware resources. NFVO and WIM communicate via the Or-Wi interface.

[0076] A VNFM can manage one or more VNFs. The VNFM can perform various management functions, such as instantiating, updating, querying, scaling, and terminating VNFs. The VNFM and VIM can communicate with each other through the Vi-Vnfm interface to allocate resources and exchange virtualization hardware resource configurations.

[0077] CISM is responsible for managing the container objects invoked by containerized VNFs, including the creation, updating, and deletion of container objects, and scheduling container objects to the appropriate node resources (compute, storage, and network) within the container cluster node resource pool managed by CISM. In the European Telecommunications Standards Institute (ETSI) standard, the corresponding concept for container objects is managed container infrastructure object (MCIO).

[0078] The Container Management Center (CCM) is responsible for managing the container cluster, including creating the node resource pool used by the cluster and scaling up or down the nodes. A container cluster is a collection of monitoring and management systems and a series of compute nodes (e.g., physical servers, bare metal, or virtual machines). A container cluster is a dynamic system in which multiple containers can be deployed, and the status of these containers and the communication between them can be monitored by the system. The corresponding concept for a container cluster in the ETSI standard is CIS Cluster.

[0079] The primary function of CIR is to handle the management of operating system container images.

[0080] VIM can perform resource management functions, such as managing the allocation of infrastructure resources (e.g., adding resources to virtual containers), and can also perform operational functions, such as collecting NFVI fault information. VIM communicates with NFVI through the NF-Vi interface.

[0081] WIM is a functional module that provides management of multi-site connectivity services (MSCS).

[0082] In one deployment, NFV MANO also includes a Physical Infrastructure Manager (PIM). As network transformation in the telecommunications sector evolves from NFV to Cloud-Native, container management is introduced into NFV MANO. For example, bare-metal container management requires creating container resource objects on top of the physical server's BM resources. NFV's energy-efficient scenarios require dynamic monitoring of the status and availability of physical server hardware resources, and determining the dynamic allocation or release of hardware resources based on the load of network element applications running on those resources to achieve energy savings. These new scenarios have prompted NFV MANO to add PIM functionality to the infrastructure layer. The PIM northbound interface has two functions: first, deploying logical bare-metal resource (bare-metal) instances on the physical server and performing LCM on them; second, monitoring physical infrastructure resources on the physical server and performing fault, configuration, account, performance, and security management (FCAPS).

[0083] Additionally, BM LCM functionality can be added to the NFV architecture shown in Figure 1. Modules with BM LCM functionality can communicate with CCM / VNFM / Cloud Manager / NFVO. BM LCM functionality can be integrated into VIM. Alternatively, as shown in Figure 2, VIM can be upgraded to an Infrastructure Manager (IM), and BM LCM functionality can be integrated into the IM. Alternatively, BM LCM functionality can be integrated into a standalone PIM deployment.

[0084] Please refer to Figure 3, which is a schematic diagram of another communication system provided in an embodiment of this application. This communication system includes a first device and a second device, which can communicate with each other. For example, the first device is a BM LCM consumer, and the second device is a BM LCM producer. Specifically, the first device can be, for example, a CCM, VNFM, cloud manager, or NFVO, and the second device can be, for example, a module with BM LCM functionality, or a VIM / PIM with BM LCM functionality. It is understood that when the NFV architecture changes, the first and second devices shown in Figure 3 can also be implemented by nodes or entities with corresponding functions in the new NFV architecture. Furthermore, the number and form of the devices shown in Figure 3 are for illustrative purposes and do not constitute a limitation on the embodiments of this application.

[0085] The embodiments of this application are described in detail below with reference to the accompanying drawings. The flowcharts in this application illustrate the corresponding methods using a first device and a second device as the execution entities in the interaction illustration, but this application does not limit the execution entities in the interaction illustration. For example, the first device in the figures can also be a chip, chip system, or processor that supports the first device in implementing the corresponding method, or it can be a logic module or software that can implement all or part of the functions of the first device. Similarly, the second device in the figures can also be a chip, chip system, or processor that supports the second device in implementing the corresponding method, or it can be a logic module or software that can implement all or part of the functions of the second device.

[0086] Please refer to Figure 4, which is a flowchart illustrating an information transmission method provided in an embodiment of this application. The information transmission method includes the following steps.

[0087] S101. The first device determines resource requirement information, which is used to indicate the first device's demand for the required BM resources. The resource requirement information includes one or more of the following: real-time requirements, pooling requirements, sharing requirements, security requirements, and mobility requirements.

[0088] For example, the resource requirement information may indicate the demand for BM resources by a telecom cloud application. The application workloads carried by the telecom cloud are diverse and differentiated, such as real-time short video applications on the edge cloud and high-computing-power applications for artificial intelligence (AI) on the central cloud. Different applications may have different demands for BM resources, and consequently, the resource requirement information determined by the first device may differ. The information transmission method provided in this application embodiment facilitates the deployment of BM resource instances by the second device that match the differentiated demands of the telecom cloud application for BM resources. In other words, it facilitates the allocation of BM resources by the second device to the BM resource instances to meet the differentiated demands of the telecom cloud application for BM resources.

[0089] The following sections elaborate on the requirements for real-time performance, pooling, sharing, security, and mobility, as described in optional implementation methods 1.1 to 1.5.

[0090] In implementation 1.1, the real-time requirement is used to indicate whether the BM resources required by the first device need to support real-time applications or deterministic applications. Real-time applications or deterministic applications may be, for example, online games or instant messaging. Optionally, the real-time requirement is also used to indicate whether the BM resources required by the first device need to enable real-time configuration of the operating system (OS). OS real-time configuration may include, for example, real-time information about configuring the kernel. Optionally, the real-time requirement is also used to indicate whether the BM resources required by the first device need to be configured using dedicated hardware. Optionally, the data type of the real-time requirement included in the resource requirement information is a structure type.

[0091] Furthermore, in the embodiments of this application, "BM resources support xx application" can also be understood as "BM resources carry xx application". For example, whether the BM resources required by the first device need to support real-time applications can also be understood as: whether the BM resources required by the first device need to carry real-time applications. This will not be elaborated further below.

[0092] Furthermore, in the embodiments of this application, "the resource requirement information includes xx requirement for indicating..." can be expressed as: "the resource requirement information includes a data element for indicating..., and the attribute of this data element is xx requirement." For example, the real-time requirement included in the resource requirement information for indicating whether the BM resources required by the first device need to support real-time applications can be expressed as: the resource requirement information includes a data element for indicating whether the BM resources required by the first device need to support real-time applications, and the attribute of this data element is real-time requirement. This will not be elaborated further below.

[0093] In implementation 1.2, the pooling requirement is used to indicate whether the BM resources required by the first device need to be selected from the pooled resources. Alternatively, it can be stated that the pooling requirement is used to indicate whether the BM resources required by the first device need to be created from the pooled resources. Optionally, the data type of the pooling requirement included in the resource requirement information is Boolean.

[0094] In implementation 1.3, the shared requirement indicates whether the BM resources needed by the first device need to be occupied by a specific tenant or shared by multiple tenants. A tenant can be, for example, an application, a network function, etc. Optionally, the data type of the shared requirement included in the resource requirement information is Boolean.

[0095] In implementation 1.4, security requirements are used to indicate whether the BM resources required by the first device need to support security applications. Optionally, when security requirements are used to indicate that the BM resources required by the first device need to support security applications, the security requirements are also used to indicate the security groups and / or security rule information that need to be used. Optionally, the data type of the security requirements included in the resource requirement information is a structure type.

[0096] In implementation 1.5, mobility requirements are used to indicate whether the BM resources required by the first device need to support mobile applications. These mobile applications may be, for example, applications executed by a vehicle-mounted base station. Optionally, mobility requirements may also indicate the maximum number of interruption cycles allowed for the first device to report statistical / alarm information due to mobility. Optionally, mobility requirements may also indicate the number of statistical / alarm information items allowed to be reported at once. Optionally, the data type of the mobility requirements included in the resource requirement information is a structure type.

[0097] Furthermore, in this embodiment of the application, any of the above-mentioned requirements, in addition to the content indicated by them as mentioned above, can also be used to indicate other content related to the requirement, without limitation. For example, real-time requirements can be used to indicate whether the BM resources required by the first device need to support real-time applications or deterministic applications, whether the BM resources required by the first device need to enable OS real-time configuration, or whether the BM resources required by the first device need to be configured using dedicated hardware, and can also be used to indicate other content related to real-time, without limitation. In addition, resource requirement information can include one or more of real-time requirements, pooling requirements, sharing requirements, security requirements, and mobility requirements, and can also include other aspects of requirements, without limitation.

[0098] In one optional implementation, the first device determines resource requirement information, including: the first device receiving network service lifecycle management (WRM) requirement information, and the first device determining resource requirement information based on the WRM requirement information. The WRM requirement information may, for example, be sent to the first device by OSS / BSS. Optionally, the WRM requirement information indicates one or more of the following: the type of load carried by the network service, the purpose of the load, and the network service's requirements for real-time performance and / or security and / or mobility. Understandably, if the first device has already created network service instances, it can convert the WRM requirement into a requirement for BM resources, which helps the second device allocate BM resources to BM resource instances to meet the differentiated resource requirements of the network service.

[0099] In another alternative implementation, the resource requirement information is determined by the first device even when no network service instance has been created. Understandably, determining the resource requirement information in advance, even without an existing network service instance, allows the second device to pre-allocate BM resources that meet the resource requirement information for the BM resource instance. Therefore, when the first device instantiates the network service, it can directly select BM resources from the pre-allocated BM resources to run the network service.

[0100] S102, the first device sends resource request information to the second device. Correspondingly, the second device receives the resource request information from the first device.

[0101] In one optional implementation, resource requirement information is carried in a first request message sent by the first device to the second device. This first request message also includes resource specification information, which indicates the first device's resource specification requirements for the BM resource instance. Here, resource specification can also be understood as resource size. For example, a BM resource description template (BM flavor) is used to represent the resource specification information. A BM flavor contains information units with the following attributes: Flavor ID, Name, CPUs, Memory, Root disk, Ephemeral disk, and Swap. The information units for the Ephemeral disk and Swap attributes are optional information units in the BM flavor. A description of these attribute information units is shown in Table 1 below.

[0102] Table 1

[0103] In one alternative approach, the first request message is sent by the first device to the second device using a declarative API. In this case, the first request message also includes expected state information, which indicates the expected state of the BM resource instance by the first device. For example, the expected state information specifically indicates that the first device expects the BM resource instance to be in an active state. Alternatively, the first request message may be, for example, a patch BM request message, which instructs the second device to patch the BM resource instance.

[0104] In an alternative approach, the first request message is sent by the first device to the second device using a command-line API. In this case, the first request message requests the second device to perform an operation on the BM resource instance. Optionally, the first request message may also include information related to the operation requested by the first request message. For example, if the first request message requests the second device to create a BM resource instance, it may include information related to this operation; the first request message may be, for example, a Create BM Request message. Or, for another example, if the first request message requests the second device to instantiate a BM resource, it may include information related to this operation.

[0105] S103. The second device allocates BM resources that meet the resource requirements information for the BM resource instance.

[0106] The following describes the specific content of step S103, which includes real-time requirements, pooling requirements, sharing requirements, security requirements, and mobility requirements, as described in optional implementation methods 2.1 to 2.5 below.

[0107] In implementation 2.1, the second device determines, based on real-time requirements, whether to allocate BM resources supporting real-time applications or deterministic applications to the BM resource instance. Understandably, if real-time requirements indicate that the BM resources required by the first device need to support real-time applications, the second device allocates BM resources supporting real-time applications to the BM resource instance.

[0108] Optionally, the method further includes: the second device selecting the computing resource type and storage resource type of the BM resource allocated to the BM resource instance from the physical resources within the data center (DC) based on real-time requirements. The computing resource type may be, for example, a CPU, a graphics processing unit (GPU), or a data processing unit (DPU).

[0109] In implementation 2.2, the second device allocates BM resources to the BM resource instance from a physical resource pool or a separate physical server based on pooling requirements. Understandably, if the pooling requirement indicates that the BM resources needed by the first device need to be selected from pooled resources, the second device allocates BM resources to the BM resource instance from the physical resource pool. If the pooling requirement indicates that the BM resources needed by the first device do not need to be selected from pooled resources, the second device allocates BM resources to the BM resource instance from a separate physical server.

[0110] In implementation 2.3, the second device determines the tenant isolation scheme for the BM resources allocated to the BM resource instance based on the sharing requirement. Understandably, if the sharing requirement indicates that the BM resources needed by the first device need to be occupied by a specific tenant, the second device allocates BM resources exclusively for that specific tenant to the BM resource instance. If the sharing requirement indicates that the BM resources needed by the first device need to be shared by multiple tenants, the second device allocates BM resources shared by multiple tenants to the BM resource instance.

[0111] Optionally, the method may further include: the second device determining, based on sharing requirements, which tenants can share the BM resources allocated by the second device for the BM resource instance, and / or determining which tenants cannot share the BM resources allocated by the second device for the BM resource instance.

[0112] In implementation 2.4, the second device determines, based on security requirements, whether to allocate BM resources that support security applications to the BM resource instance. Optionally, if the security requirements indicate that the BM resources required by the first device need to support security applications, the second device also determines security group and / or security rule information for the BM resource instance.

[0113] In implementation 2.5, the second device determines whether to allocate BM resources that support mobile applications to the BM resource instance based on mobility requirements.

[0114] In one optional implementation, when resource requirement information is carried in a first request message sent by the first device to the second device (the first request message also includes resource specification information), the second device allocates BM resources that meet the resource requirement information to the BM resource instance, including: the second device allocates BM resources that meet both the resource requirement information and the resource specification information to the BM resource instance.

[0115] The following describes two scenarios: the first device sends a first request message to the second device using a declarative API, and the first device sends a first request message to the second device using a command API, as described in optional implementation methods 3.1 and 3.2.

[0116] In implementation method 3.1, the first device sends a first request message to the second device using a declarative API. In this case, the state of the BM resource instance allocated with BM resources that meet the resource requirement information and resource specification information in step S103 is the expected state indicated by the expected state information in the first request message. Therefore, when the first device detects that the state of the BM resource instance is the expected state, it determines that the second device has completed the deployment of the BM resource instance. The first device then executes the telecom cloud application based on the deployed BM resource instance. For example, if the expected state indicated by the expected state information is active, and the current state of the BM resource instance is inactive, the second device allocates BM resources that meet the resource requirement information and resource specification information to the BM resource instance, thus transitioning the current state of the BM resource instance from inactive to active.

[0117] Understandably, the first device's use of a declarative API to send the first request message simplifies interoperability between the first and second devices, thereby reducing the probability of errors caused by multiple interoperations and thus reducing the time cost of rollback error correction. This approach also reduces the complexity of locating and resolving root cause faults related to BM resources.

[0118] Optionally, the second device allocates BM resources that meet the resource requirement information and resource specification information to the BM resource instance, including: the second device selecting a template and configuration file that match the resource requirement information and resource specification information for the BM resource instance. For example, if the resource requirement information indicates a real-time requirement, and further indicates that the BM resource needs to be configured using dedicated hardware, then the second device selects a resource description template that supports hardware acceleration or AI acceleration for the BM resource to be allocated, where the description of the resource specifications in the resource description template matches the resource specification information. If the resource requirement information indicates a pooling requirement, then the second device selects a resource description template from the BM resource pool for the BM resource to be allocated, where the description of the resource specifications in the resource description template matches the resource specification information. After selecting a resource description template, the second device further searches for one or more resource configuration files that match that resource description template.

[0119] Furthermore, after the second device selects a template and configuration file that match the resource requirement information and resource specification information for the BM resource instance, the method further includes: the second device, based on the selected template and configuration file, determines to perform one or more operations among adding BM resources, reading BM resources, updating BM resources, and deleting BM resources, according to the difference between the current state of the BM resource instance and the expected state of the BM resource instance received by the first device. This achieves the allocation of BM resources that meet the resource requirement information and resource specification information to the BM resource instance, completing the migration of the BM resource instance from its current state to its expected state. For example, if the current state of the BM resource instance is inactive, and the expected state indicated by the expected state information in the first request message received by the second device is active, then the second device determines to perform the operation of adding BM resources, allocating BM resources that meet the resource requirement information and resource specification information to the BM resource instance according to the selected template and configuration file.

[0120] In implementation method 3.2, the first device sends a first request message to the second device using a command-line API. In this case, the second device allocates BM resources that meet the resource requirement information and resource specification information to the BM resource instance, including: the second device selecting a template and configuration file that match the resource requirement information and resource specification information; and the second device performing the operation requested by the first request message on the BM resource instance based on the selected template and configuration file. This achieves the allocation of BM resources that meet the resource requirement information and resource specification information to the BM resource instance. The method further includes: the second device sending a response message to the first device using a command-line API; correspondingly, the first device receiving the response message from the second device using a command-line API. It is understood that this response message is sent by the second device in response to the first request message.

[0121] For example, taking a first request message used to request a second device to create a BM resource instance as an example, the second device allocates BM resources that meet the resource requirement information and resource specification information to the BM resource instance. This includes: the second device selecting a template and configuration file that match the resource requirement information and resource specification information; and the second device creating a BM resource instance that meets the allocated BM resources based on the selected template and configuration file. The method further includes: the second device sending a response message to the first device using a command API, the response message including the identification information of the BM resource instance created by the second device; correspondingly, the first device receiving the response message from the second device using a command API. Therefore, the first device can determine the BM resource instance created by the second device based on the identification information in the response message, and then the first device executes a telecom cloud application based on the created BM resource instance.

[0122] In summary, in this information transmission method, the first device determines resource requirement information, which indicates the first device's need for required BM resources. This resource requirement information includes one or more of the following: real-time requirements, pooling requirements, sharing requirements, security requirements, and mobility requirements. The first device sends the resource requirement information to the second device. The second device allocates BM resources to the BM resource instance that meet the resource requirement information. Therefore, the BM resources allocated by the second device to the BM resource instance satisfy the first device's need for BM resources. The requirement indicated by the resource requirement information can be the need for BM resources by a telecom cloud application. This method facilitates the deployment of BM resource instances by the second device that match the differentiated needs of the telecom cloud application for BM resources; in other words, it facilitates the allocation of BM resources by the second device to the BM resource instance to meet the differentiated needs of the telecom cloud application for BM resources.

[0123] This application also provides exemplary descriptions of information transmission methods that respectively use declarative APIs to transmit the first request message and imperative APIs to transmit the first request message.

[0124] Example 1: The case of transmitting the first request message using a declarative API. An exemplary information transmission method is shown in Figure 5, including the following steps:

[0125] S201. The first device determines resource requirement information, which is used to indicate the first device's demand for the required BM resources. The resource requirement information includes one or more of the following: real-time requirements, pooling requirements, sharing requirements, security requirements, and mobility requirements.

[0126] S202. The first device sends a first request message to the second device using a declarative API. The first request message includes resource requirement information, resource specification information, and expected status information. The resource specification information indicates the first device's resource specification requirements for the BM resource instance, and the expected status information indicates the first device's expected status for the BM resource instance. Correspondingly, the second device receives the first request message from the first device using a declarative API.

[0127] S203. The second device selects a template and configuration file that matches the resource requirement information and resource specification information for the BM resource instance.

[0128] S204. The second device, based on the selected template and configuration file, determines to perform one or more of the following operations: add BM resources, read BM resources, update BM resources, and delete BM resources, according to the difference between the current state and the expected state of the BM resource instance.

[0129] For a detailed explanation of steps S201 to S204, please refer to the relevant explanation in the information transmission method shown in Figure 4. They also have corresponding beneficial effects, so they will not be repeated here.

[0130] Example 2: Case where the first request message is transmitted using an imperative API. Taking the first request message as an example of requesting the second device to create a BM resource instance, an exemplary information transmission method is shown in Figure 6, including the following steps:

[0131] S301. The first device determines resource requirement information, which is used to indicate the first device's demand for the required BM resources. The resource requirement information includes one or more of the following: real-time requirements, pooling requirements, sharing requirements, security requirements, and mobility requirements.

[0132] S302. The first device sends a first request message to the second device using a command-line API. The first request message requests the second device to create a BM resource instance. The first request message includes resource requirement information and resource specification information. The resource specification information indicates the first device's resource specification requirements for the BM resource instance. Correspondingly, the second device receives the first request message from the first device using a declarative API.

[0133] S303, The second equipment selects templates and configuration files that match resource requirements and resource specifications.

[0134] S304. The second device creates a BM resource instance that satisfies the resource requirement information and resource specification information based on the selected template and configuration file.

[0135] S305. The second device sends a response message to the first device using a command API. The response message includes the identification information of the BM resource instance created by the second device. Correspondingly, the first device receives the response message from the second device using a command API.

[0136] For a detailed explanation of steps S301 to S305, please refer to the relevant explanation in the information transmission method shown in Figure 4, which also has corresponding beneficial effects, and will not be repeated here.

[0137] To achieve the functions of the methods provided in the embodiments of this application, the first device or the second device may include hardware structures and / or software modules, implementing the functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0138] As shown in Figure 7, this application embodiment provides a communication device 700. The communication device 700 can be a first device or a second device, or a component of the first device (e.g., an integrated circuit, a chip, etc.), or a component of the second device (e.g., an integrated circuit, a chip, etc.). The communication device 700 can also be other communication units used to implement the methods in the method embodiments of this application. The communication device 700 may include a processing unit 701. Optionally, the communication device 700 may further include a communication unit 702, where the processing unit 701 controls the communication unit 702 to transmit and receive data / signaling. The communication unit 702 may also be called a transceiver unit. Optionally, the communication unit 702 may include a sending unit and a receiving unit. The sending unit can be used to send data / signaling, and the receiving unit can be used to receive data / signaling. Optionally, the communication device 700 may further include a storage unit 703, which can be used to store information and / or data and / or instructions, etc. The storage unit 703 can interact with the processing unit 701 and also with the communication unit 702.

[0139] In one possible design, regarding the case where the communication device 700 is used to implement the function of the first device in the above method embodiment:

[0140] Processing unit 701 is used to determine resource requirement information, which indicates the demand for required BM resources. The resource requirement information includes one or more of the following: real-time requirements, pooling requirements, sharing requirements, security requirements, and mobility requirements.

[0141] The communication unit 702 is used to send resource requirement information to the second device. The resource requirement information is used to allocate BM resources to BM resource instances.

[0142] In one alternative implementation, real-time requirements are used to indicate whether the required BM resources need to support real-time applications.

[0143] In one alternative implementation, pooling requirements are used to indicate whether the required BM resources need to be selected from pooled resources.

[0144] In one alternative implementation, shared requirements are used to indicate whether the required BM resources need to be occupied by a specific tenant or need to be shared by multiple tenants.

[0145] In an optional implementation, the communication unit 702 is further configured to receive network service lifecycle management requirement information. The processing unit 701 determines the resource requirement information, specifically by: determining the resource requirement information based on the network service lifecycle management requirement information.

[0146] In one alternative implementation, resource requirement information is carried in a first request message sent to the second device; the first request message also includes resource specification information, which indicates the resource specification requirements for the BM resource instance.

[0147] In one alternative implementation, the first request message is sent to the second device using a declarative API; the first request message also includes expected status information, which indicates the expected status of the BM resource instance.

[0148] In one optional implementation, the first request message is sent to the second device via a command API; the first request message is used to request the second device to create a BM resource instance. The communication unit 702 is also configured to receive a response message from the second device via a command API, the response message including identification information of the BM resource instance created by the second device.

[0149] In one alternative implementation, the first request message is sent to the second device using a command API; the first request message is used to request the second device to perform an operation on the BM resource instance. The communication unit 702 is also configured to receive a response message from the second device using a command API.

[0150] In another possible design, regarding the case where the communication device 700 is used to implement the function of the second device in the above method embodiments:

[0151] The communication unit 702 is used to receive resource requirement information from the first device. The resource requirement information is used to indicate the first device's requirement for the required BM resources. The resource requirement information includes one or more of the following: real-time requirements, pooling requirements, sharing requirements, security requirements, and mobility requirements.

[0152] Processing unit 701 is used to allocate BM resources that meet the resource requirement information to BM resource instances.

[0153] In one alternative implementation, the real-time requirement is used to indicate whether the BM resources required by the first device need to support real-time applications.

[0154] In one alternative implementation, pooling requirements are used to indicate whether the BM resources required by the first device need to be selected from pooled resources.

[0155] In one alternative implementation, the shared requirement is used to indicate whether the BM resources required by the first device need to be occupied by a specific tenant or need to be shared by multiple tenants.

[0156] In one optional implementation, resource requirement information is carried in a first request message received from the first device; the first request message also includes resource specification information, which indicates the resource specification requirements of the first device for the BM resource instance. The processing unit 701 allocates BM resources that satisfy the resource requirement information to the BM resource instance, specifically configured to: allocate BM resources that satisfy both the resource requirement information and the resource specification information to the BM resource instance.

[0157] In one alternative implementation, the first request message is received from a first device via a declarative API; the first request message also includes expected state information, which indicates the expected state of the BM resource instance by the first device. The expected state is the state of the BM resource instance that has been allocated BM resources that satisfy the resource requirement information and resource specification information.

[0158] Optionally, the processing unit 701 allocates BM resources that meet the resource requirement information and resource specification information to the BM resource instance. Specifically, it is used to: select a template and configuration file that match the resource requirement information and resource specification information for the BM resource instance; and, based on the difference between the current state and the expected state of the BM resource instance, determine to perform one or more of the following operations: add BM resources, read BM resources, update BM resources, and delete BM resources.

[0159] In one optional implementation, the first request message is received from the first device via a command API; the first request message is used to request the creation of a BM resource instance. Processing unit 701 allocates BM resources that meet the resource requirement information and resource specification information to the BM resource instance, specifically by: selecting a template and configuration file that match the resource requirement information and resource specification information; and creating a BM resource instance that meets the allocated BM resources based on the selected template and configuration file. Communication unit 702 is further configured to send a response message to the first device via a command API, the response message including the identification information of the created BM resource instance.

[0160] In one optional implementation, the first request message is received from the first device via a command API; the first request message requests an operation for a BM resource instance. Processing unit 701 allocates BM resources to the BM resource instance that meet the resource requirement information and resource specification information, specifically configured to: select a template and configuration file matching the resource requirement information and resource specification information; and, based on the selected template and configuration file, execute the operation requested by the first request message for the BM resource instance. Communication unit 702 is further configured to send a response message to the first device via a command API.

[0161] The embodiments of this application and the method embodiments shown above are based on the same concept and have the same technical effects. For the specific principles, please refer to the description of the embodiments shown above, which will not be repeated here.

[0162] This application also provides a communication device 800, as shown in FIG8. The communication device 800 can be a first device or a second device, or it can be a chip, chip system, or processor that supports the first device in implementing the above methods, or it can be a chip, chip system, or processor that supports the second device in implementing the above methods. This device can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0163] The communication device 800 may include one or more processors 801. The processor 801 can be used to implement some or all of the functions of the first or second device through logic circuits or by running computer programs. The processor 801 may be a general-purpose processor or a special-purpose processor, such as a baseband processor, digital signal processor, application-specific integrated circuit, field-programmable gate array or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or CPU. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device, execute software programs, and process data from the software programs. The communication device may be, for example, a base station, a baseband chip, a terminal, a terminal chip, a distributed unit (DU), or a centralized unit (CU).

[0164] Optionally, the communication device 800 may include one or more memories 802, which may store instructions 804 that can be executed on the processor 801, causing the communication device 800 to perform the methods described in the above method embodiments. Optionally, the memories 802 may also store data. The processor 801 and the memories 802 may be provided separately or integrated together.

[0165] The memory 802 may include, but is not limited to, non-volatile memory such as hard disk drive (HDD) or solid-state drive (SSD), random access memory (RAM), erasable programmable read-only memory (EPROM), ROM or compact disc read-only memory (CD-ROM), etc.

[0166] Optionally, the communication device 800 may further include a transceiver 805 and an antenna 806. The transceiver 805 may be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to implement the transmission and reception functions. The transceiver 805 may include a receiver and a transmitter. The receiver may be referred to as a receiver or receiving circuit, etc., and is used to implement the receiving function; the transmitter may be referred to as a transmitter or transmitting circuit, etc., and is used to implement the transmitting function.

[0167] In one possible design, regarding the case where the communication device 800 is used to implement the function of the first device in the above method embodiment:

[0168] Processor 801 is used to determine resource requirement information, which indicates the need for required BM resources. The resource requirement information includes one or more of the following: real-time requirements, pooling requirements, sharing requirements, security requirements, and mobility requirements.

[0169] Transceiver 805 is used to send resource requirement information to the second device. The resource requirement information is used to allocate BM resources to BM resource instances.

[0170] In one alternative implementation, real-time requirements are used to indicate whether the required BM resources need to support real-time applications.

[0171] In one alternative implementation, pooling requirements are used to indicate whether the required BM resources need to be selected from pooled resources.

[0172] In one alternative implementation, shared requirements are used to indicate whether the required BM resources need to be occupied by a specific tenant or need to be shared by multiple tenants.

[0173] In an optional implementation, transceiver 805 is further configured to receive network service lifecycle management requirement information. Processor 801 determines the resource requirement information, specifically by: determining the resource requirement information based on the network service lifecycle management requirement information.

[0174] In one alternative implementation, resource requirement information is carried in a first request message sent to the second device; the first request message also includes resource specification information, which indicates the resource specification requirements for the BM resource instance.

[0175] In one alternative implementation, the first request message is sent to the second device using a declarative API; the first request message also includes expected status information, which indicates the expected status of the BM resource instance.

[0176] In one alternative implementation, the first request message is sent to the second device via a command API; the first request message is used to request the second device to create a BM resource instance. The transceiver 805 is also configured to receive a response message from the second device via a command API, the response message including identification information of the BM resource instance created by the second device.

[0177] In one alternative implementation, the first request message is sent to the second device via a command API; the first request message is used to request the second device to perform an operation on the BM resource instance. The transceiver 805 is also configured to receive a response message from the second device via a command API.

[0178] In another possible design, regarding the case where the communication device 800 is used to implement the function of the second device in the above method embodiments:

[0179] Transceiver 805 is used to receive resource requirement information from the first device. The resource requirement information is used to indicate the first device's requirement for the required BM resources. The resource requirement information includes one or more of the following: real-time requirement, pooling requirement, sharing requirement, security requirement, and mobility requirement.

[0180] Processor 801 is used to allocate BM resources that meet the resource requirement information to BM resource instances.

[0181] In one alternative implementation, the real-time requirement is used to indicate whether the BM resources required by the first device need to support real-time applications.

[0182] In one alternative implementation, pooling requirements are used to indicate whether the BM resources required by the first device need to be selected from pooled resources.

[0183] In one alternative implementation, the shared requirement is used to indicate whether the BM resources required by the first device need to be occupied by a specific tenant or need to be shared by multiple tenants.

[0184] In one optional implementation, resource requirement information is carried in a first request message received from the first device; the first request message also includes resource specification information, which indicates the resource specification requirements of the first device for the BM resource instance. The processor 801 allocates BM resources that satisfy the resource requirement information to the BM resource instance, specifically by: allocating BM resources that satisfy both the resource requirement information and the resource specification information to the BM resource instance.

[0185] In one alternative implementation, the first request message is received from a first device via a declarative API; the first request message also includes expected state information, which indicates the expected state of the BM resource instance by the first device. The expected state is the state of the BM resource instance that has been allocated BM resources that satisfy the resource requirement information and resource specification information.

[0186] Optionally, the processor 801 allocates BM resources that meet the resource requirement information and resource specification information for the BM resource instance. Specifically, it is used to: select a template and configuration file that match the resource requirement information and resource specification information for the BM resource instance; and, based on the difference between the current state and the expected state of the BM resource instance, determine to perform one or more of the following operations: add BM resources, read BM resources, update BM resources, and delete BM resources.

[0187] In one optional implementation, the first request message is received from the first device via a command API; the first request message is used to request the creation of a BM resource instance. The processor 801 allocates BM resources that meet the resource requirement information and resource specification information to the BM resource instance, specifically by: selecting a template and configuration file that match the resource requirement information and resource specification information; and creating a BM resource instance that meets the resource requirement information and resource specification information based on the selected template and configuration file. The transceiver 805 is also used to send a response message to the first device via a command API, the response message including the identification information of the created BM resource instance.

[0188] In one alternative implementation, the first request message is received from the first device via a command API; the first request message requests an operation for a BM resource instance. The processor 801 allocates BM resources to the BM resource instance that satisfy the resource requirement information and resource specification information, specifically by: selecting a template and configuration file that match the resource requirement information and resource specification information; and, based on the selected template and configuration file, performing the operation requested by the first request message for the BM resource instance. The transceiver 805 is also configured to send a response message to the first device via a command API.

[0189] In another possible design, the processor 801 may include a transceiver for implementing receive and transmit functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receive and transmit functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit can be used for reading and writing code / data, or it can be used for transmitting or relaying signals.

[0190] In another possible design, the processor 801 may optionally store instructions 803, which, when executed on the processor 801, cause the communication device 800 to perform the methods described in the above method embodiments. Instructions 803 may be embedded in the processor 801; in this case, the processor 801 may be implemented in hardware.

[0191] In another possible design, the communication device 800 may include circuitry that can perform the functions of transmitting, receiving, or communicating as described in the foregoing method embodiments. The processor and transceiver described in this application embodiment can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductors (CMOS), n-metal-oxide-semiconductor (NMOS), positive-channel metal oxide semiconductors (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0192] Those skilled in the art will also understand that the various illustrative logical blocks and steps listed in the embodiments of this application can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented through hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can implement the described functionality using various methods for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of this application.

[0193] The embodiments of this application and the above-described method embodiments are based on the same concept and have the same technical effects. For the specific principles, please refer to the description in the above-described method embodiments, which will not be repeated here.

[0194] This application also provides a computer-readable storage medium for storing computer software instructions that, when executed by a communication device, implement the functions of any of the above method embodiments.

[0195] This application also provides a computer program product for storing computer software instructions, which, when executed by a communication device, implement the functions of any of the above method embodiments.

[0196] This application also provides a computer program that, when run on a computer, implements the functions of any of the above method embodiments.

[0197] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., SSDs), etc.

[0198] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. An information transmission method, characterized in that, The method includes: Determine resource requirement information, which is used to indicate the demand for the required bare metal (BM) resources. The resource requirement information includes one or more of the following: real-time requirements, pooling requirements, sharing requirements, security requirements, and mobility requirements. The resource requirement information is sent to the second device, and the resource requirement information is used to allocate BM resources to the BM resource instance.

2. The method according to claim 1, characterized in that, The real-time requirement is used to indicate whether the required BM resources need to support real-time applications.

3. The method according to claim 1 or 2, characterized in that, The pooling requirement is used to indicate whether the required BM resources need to be selected from the pooled resources.

4. The method according to any one of claims 1 to 3, characterized in that, The shared requirement is used to indicate whether the required BM resources need to be occupied by a specific tenant or need to be shared by multiple tenants.

5. The method according to any one of claims 1 to 4, characterized in that, The resource requirement information is carried in the first request message sent to the second device; The first request message also includes resource specification information, which is used to indicate the resource specification requirements for the BM resource instance.

6. The method according to claim 5, characterized in that, The first request message is sent to the second device using a declarative application programming interface (API); The first request message also includes expected status information, which indicates the expected status of the BM resource instance.

7. The method according to claim 5, characterized in that, The first request message is sent to the second device using a command API; The first request message is used to request the second device to create the BM resource instance; The method further includes: receiving a response message from the second device using a command API, the response message including identification information of the BM resource instance created by the second device.

8. The method according to claim 5 or 7, characterized in that, The first request message is sent to the second device using a command API; The first request message is used to request the second device to perform an operation on the BM resource instance; The method further includes: receiving a response message from the second device using a command API.

9. An information transmission method, characterized in that, The method includes: Receive resource requirement information from a first device, the resource requirement information being used to indicate the first device's requirement for the required bare metal (BM) resources, the resource requirement information including one or more of the following: real-time requirement, pooling requirement, sharing requirement, security requirement, mobility requirement; Allocate BM resources that meet the resource requirements information to BM resource instances.

10. The method according to claim 9, characterized in that, The real-time requirement is used to indicate whether the BM resources required by the first device need to support real-time applications.

11. The method according to claim 9 or 10, characterized in that, The pooling requirement is used to indicate whether the BM resources required by the first device need to be selected from the pooled resources.

12. The method according to any one of claims 9 to 11, characterized in that, The shared requirement is used to indicate whether the BM resources required by the first device need to be occupied by a specific tenant or need to be shared by multiple tenants.

13. The method according to any one of claims 9 to 12, characterized in that, The resource requirement information is carried in the first request message received from the first device; The first request message also includes resource specification information, which is used to indicate the resource specification requirements of the first device for the BM resource instance; The step of allocating BM resources that meet the resource requirement information to BM resource instances includes: allocating BM resources that meet the resource requirement information and the resource specification information to BM resource instances.

14. The method according to claim 13, characterized in that, The first request message is received from the first device using a declarative application programming interface (API); The first request message also includes expected status information, which is used to indicate the expected status of the first device for the BM resource instance; The state of a BM resource instance that has been allocated BM resources that satisfy the resource requirement information and the resource specification information is the desired state.

15. The method according to claim 14, characterized in that, The process of allocating BM resources to BM resource instances that satisfy the resource requirement information and the resource specification information includes: Select a template and configuration file that match the resource requirement information and the resource specification information for the BM resource instance; For the selected template and configuration file, based on the difference between the current state and the desired state of the BM resource instance, determine to perform one or more of the following operations: add BM resource, read BM resource, update BM resource, and delete BM resource.

16. The method according to claim 13, characterized in that, The first request message is received from the first device using an imperative API; The first request message is used to request the creation of the BM resource instance; The step of allocating BM resources to BM resource instances that satisfy the resource requirement information and the resource specification information includes: selecting a template and configuration file that match the resource requirement information and the resource specification information; and creating BM resource instances that satisfy the resource requirement information and the resource specification information based on the selected template and configuration file. The method further includes: sending a response message to the first device using a command API, the response message including the identification information of the created BM resource instance.

17. The method according to claim 13 or 16, characterized in that, The first request message is received from the first device using an imperative API; The first request message is used to request an operation on the BM resource instance; The step of allocating BM resources to a BM resource instance that satisfy the resource requirement information and the resource specification information includes: selecting a template and configuration file that match the resource requirement information and the resource specification information; and performing the operation requested by the first request message on the BM resource instance based on the selected template and configuration file. The method further includes sending a response message to the first device using a command API.

18. An information transmission method, characterized in that, The method includes: The first device determines resource requirement information, which is used to indicate the first device's demand for the required bare metal (BM) resources. The resource requirement information includes one or more of the following: real-time requirements, pooling requirements, sharing requirements, security requirements, and mobility requirements. The first device sends the resource requirement information to the second device; The second device receives the resource requirement information from the first device; The second device allocates BM resources to the BM resource instance that meet the resource requirement information.

19. A communication system, characterized in that, The system includes a first device and a second device; The first device is used to determine resource requirement information, which indicates the first device's requirement for the required bare metal (BM) resources. The resource requirement information includes one or more of the following: real-time requirements, pooling requirements, sharing requirements, security requirements, and mobility requirements. The first device is also used to send the resource requirement information to the second device; The second device is configured to receive the resource demand information from the first device; The second device is also used to allocate BM resources that meet the resource requirement information to BM resource instances.

20. A communication device, characterized in that, The apparatus includes a module or unit for implementing the method of any one of claims 1 to 9, or the apparatus includes a module or unit for implementing the method of any one of claims 10 to 18.

21. A communication device, characterized in that, Including the processor; The processor is configured to execute a computer program or instructions in a memory to cause the communication device to perform the method according to any one of claims 1 to 9, or to cause the communication device to perform the method according to any one of claims 10 to 18.

22. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed, implements the method as described in any one of claims 1 to 9, or implements the method as described in any one of claims 10 to 18.

23. A computer program product, characterized in that, The computer program product includes: computer program code, which, when the computer program code is executed, implements the method as described in any one of claims 1 to 9, or implements the method as described in any one of claims 10 to 18.

Images