Information transmission method and device

Abstract

An information transmission method and device, in the information transmission method, a first device determines resource demand information, the resource demand information is used for indicating a demand of the first device for a required BM resource, and the resource demand information comprises one or more of the following items: a real-time demand, a pooling demand, a sharing demand, a security demand, and a mobility demand. And the first device sends the resource demand information to the second device. And the second device allocates the BM resource satisfying the resource demand information to the BM resource instance. Therefore, the BM resource allocated by the second device for the BM resource instance meets the requirement of the first device for the BM resource. Wherein the demand indicated by the resource demand information can be the demand of the telecommunication cloud application for the BM resource, so that the method is beneficial for the second equipment to deploy the BM resource instance matched with the differentiated demand of the telecommunication cloud application for the BM resource.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to an information transmission method and device. Background Art

[0002] 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 has architectural practices with key features such as (micro)services, elastic scaling, distribution, high availability, multi-tenancy, and automation.

[0003] In the cloud-native scenario in the telecommunications field, bare metal (BM) resource instances can be deployed and lifecycle management (LCM) can be performed to allocate BM resources to network elements, so that network elements can 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. Summary of the invention

[0004] The embodiments of the present application provide an information transmission method and apparatus that can deploy BM resource instances that match the differentiated requirements of telecom cloud applications for BM resources.

[0005] In a first aspect, the present application provides an information transmission method, which can be applied to a first device, a chip in the first device, or a logic module or software that can implement all or part of the functions of the first device. The following description is taken as an example of the first device. The method includes: the first device determines resource requirement information, the resource requirement information is used to indicate the 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 sends resource requirement information to the second device, and the resource requirement information is used to allocate BM resources to BM resource instances.

[0006] It can be seen that in this method, the first device sends the demand for the required BM resources to the second device, which is conducive to the second device allocating BM resources that meet the needs of the first device to the BM resource instance. Among them, the demand indicated by the resource demand information can be the demand for BM resources by the telecom cloud application. This method is conducive to the second device deploying BM resource instances that match the differentiated demand for BM resources by the telecom cloud application.

[0007] In an optional implementation, the real-time requirement is used to indicate whether the required BM resources need to support real-time applications.

[0008] In an optional implementation, the pooling requirement is used to indicate whether the required BM resources need to be selected from the pooled resources.

[0009] In an optional implementation manner, the sharing requirement is used to indicate that the required BM resources need to be occupied by a specific tenant or need to be shared by multiple tenants.

[0010] In an optional implementation, the first device determines the resource demand information, including: the first device receives the network service lifecycle management demand information; the first device determines the resource demand information according to the network service lifecycle management demand information. It can be seen that the first device converts the network service lifecycle management demand into a demand for BM resources, which is conducive to the second device allocating BM resources to the BM resource instance to meet the differentiated resource demands of the network service.

[0011] In an optional implementation, the resource requirement information is carried in a first request message sent to the second device; the first request message also includes resource specification information, and the resource specification information is used to indicate the resource specification requirements for the BM resource instance. This method is conducive to the BM resource instance determined by the second device not only meeting the resource requirement information, but also meeting the resource specification requirements of the first device for the BM resource instance.

[0012] In an optional implementation, the first request message is sent to the second device using a declarative application program interface (API); the first request message also includes expected state information, which is used to indicate the expected state of the BM resource instance. The use of a declarative API can simplify the interoperability between the first device and the second device, thereby reducing the increased error probability due to multiple interoperations, and reducing the complexity of locating and resolving root causes of faults related to BM resources.

[0013] In an optional implementation, the first request message is sent to the second device using an imperative API; the first request message is used to request the second device to create a BM resource instance. The method also includes: the first device uses the imperative API to receive a response message from the second device, the response message including identification information of the BM resource instance created by the second device.

[0014] In an optional implementation, the first request message is sent to the second device using an imperative API; the first request message is used to request the second device to operate on the BM resource instance. The method also includes: the first device receives a response message from the second device using an imperative API.

[0015] In the second aspect, the present application provides an information transmission method, which can be applied to a second device, a chip in the second device, or a logic module or software that can realize all or part of the functions of the second device. The following description is taken as an example of the second device. The method includes: the second device receives resource demand information from the first device, and the resource demand information is used to indicate the demand of the first device for the required BM resources, and the resource demand 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 meet the resource demand information to the BM resource instance.

[0016] It can be seen that the BM resource allocated by the second device to the BM resource instance meets the demand of the first device for BM resources. The demand indicated by the resource demand information can be the demand of the telecom cloud application for BM resources, and then the second device can deploy a BM resource instance that matches the differentiated demand of the telecom cloud application for BM resources.

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

[0018] In an optional implementation manner, the pooling requirement is used to indicate whether the BM resources required by the first device need to be selected from pooled resources.

[0019] In an optional implementation manner, the sharing requirement is used to indicate that the BM resources required by the first device need to be occupied by a specific tenant or need to be shared by multiple tenants.

[0020] In an optional implementation, the resource requirement information is carried in a first request message received from the first device; the first request message also includes resource specification information, and the resource specification information is used to indicate the resource specification requirements of the first device for the BM resource instance. 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 the resource requirement information and the resource specification information to the BM resource instance.

[0021] In an optional embodiment, the first request message is received from the first device using a declarative API; the first request message also includes expected state information, and the expected state information is used to indicate the expected state of the BM resource instance of the first device. The state of the BM resource instance that is allocated with BM resources that meet the resource demand information and resource specification information is the expected state. The use of a declarative API approach can simplify the interoperability between the first device and the second device, thereby reducing the increased probability of errors due to multiple interoperations, and reducing the complexity of locating and resolving root causes of faults related to BM resources.

[0022] 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 matches the resource requirement information and the resource specification information for the BM resource instance; the second device determines to perform one or more operations of adding BM resources, reading BM resources, updating BM resources, and deleting BM resources based on the difference between the current state and the expected state of the BM resource instance for the selected template and configuration file.

[0023] In an optional embodiment, 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 a BM resource instance. The second device allocates BM resources that meet resource requirement information and resource specification information to the BM resource instance, including: the second device selects a template and configuration file that matches the resource requirement information and resource specification information; the second device creates a BM resource instance in which the allocated BM resources meet the resource requirement information and resource specification information based on the selected module and configuration file. The method also includes: the second device uses an imperative API to send a response message to the first device, and the response message includes identification information of the created BM resource instance.

[0024] In an optional implementation, 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 a BM resource instance. The second device allocates BM resources that meet resource requirement information and resource specification information to the BM resource instance, including: the second device selects a template and configuration file that matches the resource requirement information and resource specification information; the second device performs the operation requested by the first request message on the BM resource instance based on the selected module and configuration file. The method also includes: the second device sends a response message to the first device using an imperative API.

[0025] In the third aspect, the present application provides an information transmission method, which is described by taking the interaction between a first device and a second device as an example. The first device in the method can also be replaced by a chip in the first device, or a logic module or software that can implement all or part of the functions of the first device. The second device in the method can also be replaced by a chip in the second device, or a logic module or software that can implement all or part of the functions of the second device. The method includes: the first device determines resource requirement information, the resource requirement information is used to indicate 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 sends 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 that meet the resource requirement information to the BM resource instance.

[0026] It can be seen that in this method, the first device sends the demand for the required BM resources to the second device, and the second device can allocate BM resources that meet the needs of the first device to the BM resource instance. The demand indicated by the resource demand information can be the demand of the telecom cloud application for BM resources, and then the second device can deploy the BM resource instance that matches the differentiated demand of the telecom cloud application for BM resources.

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

[0028] In an optional implementation manner, the pooling requirement is used to indicate whether the BM resources required by the first device need to be selected from pooled resources.

[0029] In an optional implementation manner, the sharing requirement is used to indicate that the BM resources required by the first device need to be occupied by a specific tenant or need to be shared by multiple tenants.

[0030] In an optional implementation, the first device determines resource requirement information, including: the first device receives service requirement information; and the first device determines resource requirement information according to the service requirement information.

[0031] In an optional implementation, the 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, and the resource specification information is used to indicate the resource specification requirement for the BM resource instance. 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 the resource requirement information and the resource specification information to the BM resource instance.

[0032] In an optional 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, and the expected state information is used to indicate the expected state of the BM resource instance. The state of the BM resource instance that is allocated with BM resources that meet the resource requirement information and resource specification information is the expected state.

[0033] 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 matches the resource requirement information and the resource specification information for the BM resource instance; the second device determines to perform one or more operations of adding BM resources, reading BM resources, updating BM resources, and deleting BM resources based on the difference between the current state and the expected state of the BM resource instance for the selected template and configuration file.

[0034] In an optional implementation, the first request message is sent by the first device to the second device using an imperative 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 resource requirement information and resource specification information to the BM resource instance, including: the second device selects a template and configuration file that matches the resource requirement information and resource specification information; the second device creates a BM resource instance in which the allocated BM resources meet the resource requirement information and resource specification information based on the selected module and configuration file. The method also includes: the second device uses an imperative API to send a response message to the first device, the response message including identification information of the created BM resource instance; the first device uses an imperative API to receive a response message from the second device.

[0035] In an optional implementation, the first request message is sent to the second device using an imperative API; the first request message is used to request the second device to operate on the 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 selects a template and configuration file that matches the resource requirement information and resource specification information; the second device performs the operation requested by the first request message on the BM resource instance based on the selected module and configuration file. The method also includes: the second device uses an imperative API to send a response message to the first device; the first device uses an imperative API to receive a response message from the second device.

[0036] In addition, in this aspect, the beneficial effects of the above optional implementation manner can be found in the relevant contents of the above first and second aspects, and will not be described in detail here.

[0037] In a fourth aspect, the present application also provides a communication device. The communication device may be a first device or a second device, or a chip in the first device or a chip in the second device, or a logic module or software that can implement all or part of the functions of the first device or the second device. The communication device has the function of implementing some or all of the implementation methods described in the first aspect or the second aspect above. The functions may be implemented by hardware, or by hardware executing corresponding software implementations. The hardware or software includes one or more units or modules corresponding to the above functions.

[0038] In one possible design, the structure of the communication device may include a processing unit and a communication unit, and the processing unit is configured to support the communication device to perform the corresponding functions in the above method. The communication unit is used to support communication between the communication device and other communication devices. The communication device may also include a storage unit, which is used to couple with the processing unit and the communication unit, and store the necessary program instructions and data of the communication device. In addition, the processing unit can be used to control the communication unit to send and receive data / signaling.

[0039] In one implementation, the processing unit is configured to determine resource requirement information, the resource requirement information is used to indicate the requirement for the required BM resources, and the resource requirement information includes one or more of the following: real-time requirement, pooling requirement, sharing requirement, security requirement, and mobility requirement. The communication unit is configured to send the resource requirement information to the second device, the resource requirement information is used to allocate BM resources to the BM resource instance.

[0040] In addition, in this aspect, other optional implementations of the communication device can refer to the relevant content of the first aspect mentioned above and will not be described in detail here.

[0041] In another embodiment, the communication unit is used to receive resource demand information from the first device, the resource demand information is used to indicate the demand of the first device for the required BM resources, and the resource demand information includes one or more of the following: real-time demand, pooling demand, sharing demand, security demand, and mobility demand. The processing unit is used to allocate BM resources that meet the resource demand information to the BM resource instance.

[0042] In addition, in this aspect, other optional implementations of the communication device can refer to the relevant content of the above-mentioned second aspect and will not be described in detail here.

[0043] As an example, the communication unit may be a transceiver or a communication interface, the storage unit may be a memory, and the processing unit may be a processor. The processor is coupled to the memory, the memory is used to store a program or an instruction processor, the processor may be used to enable the communication device to execute the method described in the first aspect or the second aspect when the program or instruction is executed by the processor, and the transceiver or the communication interface may be used to send and receive signals and / or data.

[0044] In one implementation, the processor is configured to determine resource requirement information, the resource requirement information is used to indicate the requirement for the required BM resources, and the resource requirement information includes one or more of the following: real-time requirement, pooling requirement, sharing requirement, security requirement, and mobility requirement. The transceiver is configured to send the resource requirement information to the second device, the resource requirement information is used to allocate BM resources to the BM resource instance.

[0045] In addition, in this aspect, other optional implementations of the communication device can refer to the relevant content of the first aspect mentioned above and will not be described in detail here.

[0046] In another embodiment, the transceiver is used to receive resource demand information from the first device, the resource demand information is used to indicate the demand of the first device for the required BM resources, and the resource demand information includes one or more of the following: real-time demand, pooling demand, sharing demand, security demand, and mobility demand. The processor is used to allocate BM resources that meet the resource demand information to the BM resource instance.

[0047] In addition, in this aspect, other optional implementations of the communication device can refer to the relevant content of the above-mentioned second aspect and will not be described in detail here.

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

[0049] During the implementation process, the processor can be used to perform, for example, but not limited to, baseband related processing, and the transceiver or communication interface can be used to perform, for example, but not limited to, radio frequency transceiver. The above-mentioned devices can be arranged on independent chips, or at least partially or completely on the same chip. For example, the processor can be further divided into an analog baseband processor and a digital baseband processor. Among them, the analog baseband processor can be integrated with the transceiver (or communication interface) on the same chip, and the digital baseband processor can be arranged on an independent 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 a variety of application processors (such as but not limited to a graphics processor, a multimedia processor, etc.) on the same chip. Such a chip can be called a system on a chip (System on a Chip, SoC). Whether each device is independently arranged on different chips or integrated on one or more chips often depends on the needs of product design. The embodiment of the present application does not limit the implementation form of the above-mentioned devices.

[0050] In a fifth aspect, the present application also provides a processor for executing the above-mentioned various methods. In the process of executing these methods, the process of sending the above-mentioned signal and receiving the above-mentioned signal in the above-mentioned method can be understood as the process of outputting the above-mentioned signal by the processor, and the process of the above-mentioned signal input by the processor. When outputting the above-mentioned signal, the processor outputs the above-mentioned signal to the transceiver so that it is transmitted by the transceiver (or communication interface). After the above-mentioned signal is output by the processor, it may also need to be processed otherwise before it reaches the transceiver (or communication interface). Similarly, when the processor receives the above-mentioned input signal, the transceiver (or communication interface) receives the above-mentioned signal and inputs it into the processor. Furthermore, after the transceiver (or communication interface) receives the above-mentioned signal, the above-mentioned signal may need to be processed otherwise before it is input into the processor.

[0051] For the sending and receiving operations involved in the processor, unless otherwise specified, or unless they conflict with their actual function or internal logic in the relevant description, they can be more generally understood as processor output, reception, input and other operations, rather than sending and receiving operations performed directly by the RF circuit and antenna.

[0052] In the implementation process, the processor may be a processor specifically used to execute these methods, or a processor that executes computer instructions in a memory to execute these methods, such as a general-purpose processor. The memory may be a non-transitory memory, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or may be separately arranged on different chips. The embodiment of the present application does not limit the type of memory and the arrangement of the memory and the processor.

[0053] In a sixth aspect, the present application further provides a communication system, which includes the first device and the second device of the above aspect. In another possible design, the system may also include other devices that interact with the first device and / or the second device in the solution provided by the present application.

[0054] In a seventh aspect, the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is run, the method described in the first aspect or the second aspect is executed.

[0055] In an eighth aspect, the present application further provides a computer program product comprising instructions, wherein the computer program product comprises: a computer program code, and when the computer program code is run, the method described in the first aspect or the second aspect above is executed.

[0056] In a ninth aspect, the present application provides a chip system, which includes a processor and an interface, wherein the interface is used to obtain a program or instruction, and the processor is used to call the program or instruction to implement the functions involved in the first aspect or the second aspect. In a possible design, the chip system also includes a memory, which is used to store program instructions and data necessary for the terminal. The chip system can be composed of a chip, or it can include a chip and other discrete devices. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0058] Figure 2It is a structural diagram of a communication system provided in an embodiment of the present application;

[0059] Figure 3 is a schematic diagram of the structure of another communication system provided in an embodiment of the present application;

[0060] Figure 4 It is a flowchart of an information transmission method provided in an embodiment of the present application;

[0061] Figure 5 is a schematic diagram of another information transmission method provided in an embodiment of the present application;

[0062] Figure 6 is a schematic diagram of another information transmission method provided in an embodiment of the present application;

[0063] Figure 7 is a structural diagram of a communication device provided in an embodiment of the present application;

[0064] Figure 8 It is a structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0065] The embodiments of the present application are described below in conjunction with the drawings in the embodiments of the present application.

[0066] First, in order to better understand the information transmission method disclosed in the embodiment of the present application, a communication system to which the embodiment of the present application is applicable is described.

[0067] The technical solution of the embodiment of the present application can be applied to various communication systems. For example, the global mobile communication system, the long term evolution (LTE) system, the universal mobile communication system, the fourth generation mobile communication technology (4th generation, 4G) system, the fourth point five generation mobile communication technology (4.5th generation, 4.5G) system, the fifth generation mobile communication technology (5th generation mobile networks, 5G) system, and with the continuous development of communication technology, the technical solution of the embodiment of the present application can also be used for subsequent evolution of communication systems, such as the sixth generation mobile communication technology (6th generation mobile networks, 6G) system, the seventh generation mobile communication technology (7th generation mobile networks, 7G) system, and so on.

[0068] See also Figure 1 , Figure 1It is a schematic diagram of NFV architecture. NFV architecture includes operational support system (OSS) / business support system (BSS), element management (EM), virtual network function (VNF), NFV infrastructure (NFVI), NFV management and network orchestration (MANO). Among them, NFVI includes hardware resource layer, virtualization layer and virtual resource layer. Optionally, NFVI can also include container infrastructure service (CIS) / CIS cluster (ie CIS cluster) and wide area network (WAN).

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

[0070] Among them, OSS / BSS is mainly for telecommunication service operators, and is used to provide comprehensive network management and business operation functions, including network management (such as fault monitoring, network information collection, etc.), billing management, and customer service management, etc. OSS / BSS and NFVO communicate through the Os-Ma-nfvo interface.

[0071] EM is used to configure and manage VNF functions. EM and VNFM communicate through the Ve-Vnfm-em interface.

[0072] VNF is used to define network functions through software, that is, to implement various network functions through software, such as virtual firewall functions, virtual switch functions, etc. The resources required by VNF need to be decomposed into virtual computing / storage / network resources, which are carried by NFVI. VNF and VNFM communicate through the Ve-Vnfm-vnf interface.

[0073] 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 through the Or-Vnfm interface. In addition, NFVO can also communicate with VIM through the Or-Vi interface to implement resource allocation or reservation, and exchange configuration and status information of virtualized hardware resources. NFVO and WIM communicate through the Or-Wi interface.

[0074] VNFM can manage one or more VNFs. VNFM can perform various management functions, such as instantiating, updating, querying, scaling, and terminating VNFs. VNFM and VIM can communicate with each other through the Vi-Vnfm interface to implement resource allocation and exchange configuration of virtualized hardware resources.

[0075] CISM is responsible for managing the container objects called by the containerized VNF, including the creation, update and deletion of container objects, and scheduling container objects to the corresponding node resources (computing, storage and network) in the container cluster node resource pool managed by CISM. The corresponding concept of container objects in the European Telecommunications Standards Institute (ETSI) standard is managed container infrastructure object (MCIO).

[0076] CCM is responsible for managing container clusters, including the creation of node resource pools used by container clusters and node expansion and contraction. A container cluster is a collection of a monitoring and management system and a series of computing nodes (for example, physical servers, bare metal or virtual machines). A container cluster is a dynamic system in which multiple containers can be deployed. The status of these containers and the communication between containers can be monitored by the system. The corresponding concept of container cluster in the ETSI standard is CIS Cluster.

[0077] The main function of CIR is to handle operating system container image management.

[0078] VIM can perform resource management functions, for example, VIM can be used to manage the allocation of infrastructure resources (such as adding resources to virtual containers), and can also perform operational functions, such as collecting NFVI fault information. VIM and NFVI communicate through the Nf-Vi interface.

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

[0080] In one deployment, NFV MANO also includes a physical infrastructure manager (PIM). In the process of network transformation in the telecommunications field evolving from NFV to Cloud-Native, container management is introduced in NFV MANO. For example, bare metal container management requires the creation of container resource objects on the BM resources of the physical server. The NFV green energy-saving scenario requires dynamic monitoring of the status and availability of physical server hardware resources, and dynamic allocation or release of hardware resources based on the load of network element applications running on the hardware resources to achieve energy-saving effects. These new scenarios have prompted NFV MANO to add PIM functions at the infrastructure layer. The functions of the PIM northbound interface include two parts: one is to deploy logical bare metal resource (bare metal) instances on physical servers and perform LCM on them; the other is to monitor the physical infrastructure resources on the physical server and perform fault, configuration, account, performance and security management (FCAPS).

[0081] In addition, you can also Figure 1 The NFV architecture shown in the figure adds BM LCM function, and the module with BM LCM function can communicate with CCM / VNFM / Cloud Manager / NFVO. BM LCM function can be integrated in VIM. Or, Figure 2 As shown, the VIM can also be upgraded to an infrastructure manager (IM), and the BM LCM function can be integrated into the IM. Alternatively, the BM LCM function can be integrated into an independently deployed PIM.

[0082] See also Figure 3 , Figure 3It is a structural diagram of another communication system provided in an embodiment of the present application. The communication system includes a first device and a second device, and the first device and the second device can communicate with each other. Exemplarily, the first device is a consumer of BM LCM (i.e., BM LCM Consumer), and the second device is a provider of BM LCM (i.e., BM LCMProducer); specifically, the first device may be, for example, a CCM or a VNFM or a cloud manager or an NFVO, and the second device may be, for example, a module with a BM LCM function, and the second device may also be, for example, a VIM / PIM with a BM LCM function. It is understandable that when the NFV architecture changes, Figure 3 The first device and the second device shown may also be implemented by nodes or entities with corresponding functions in the new NFV architecture. Figure 3 The number and form of the devices shown are for illustrative purposes only and do not constitute a limitation on the embodiments of the present application.

[0083] The following is a detailed description of the embodiments of the present application in conjunction with the accompanying drawings. The flowchart in the present application uses the first device and the second device as the execution subject of the interactive diagram as an example to illustrate the corresponding method, but the present application does not limit the execution subject of the interactive diagram. For example, the first device in the figure can also be a chip, a chip system, or a processor that supports the first device to implement the corresponding method, or a logic module or software that can implement all or part of the functions of the first device. The second device in the figure can also be a chip, a chip system, or a processor that supports the second device to implement the corresponding method, or a logic module or software that can implement all or part of the functions of the second device.

[0084] See also Figure 4 , Figure 4 It is a flow chart of an information transmission method provided in an embodiment of the present application, and the information transmission method includes the following steps.

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

[0086] Exemplarily, the demand indicated by the resource demand information may be the demand of the telecom cloud application for BM resources. The application loads carried by the telecom cloud are diversified and differentiated, for example, real-time short videos of edge cloud applications, artificial intelligence (AI) high computing power applications of the central cloud, etc. Different applications may have different demands for BM resources, and thus the resource demand information determined by the first device may be different. The information transmission method provided in the embodiment of the present application is conducive to the second device deploying a BM resource instance that matches the differentiated demand for BM resources of the telecom cloud application, that is, it is conducive to the second device allocating BM resources to the BM resource instance to meet the differentiated demand for BM resources of the telecom cloud application.

[0087] The real-time requirement, pooling requirement, sharing requirement, security requirement, and mobility requirement are explained below, as described in the following optional implementation modes 1.1 to 1.5.

[0088] 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. Among them, real-time applications or deterministic applications may be, for example, online games, instant messaging. Optionally, the real-time requirement is also used to indicate whether it is necessary to enable the operating system (OS) real-time configuration for the BM resources required by the first device. The OS real-time configuration may include, for example, real-time information for 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.

[0089] In addition, in the embodiment of the present 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 repeated in the following text.

[0090] In addition, in the embodiment of the present application, "the resource requirement information includes xx requirement for indicating..." can be expressed as: "the resource requirement information includes a cell for indicating...", and the attribute of the cell is xx requirement. For example, the real-time requirement included in the resource requirement information is used to indicate whether the BM resources required by the first device need to support real-time applications, which can be expressed as: the resource requirement information includes a cell for indicating whether the BM resources required by the first device need to support real-time applications, and the attribute of the cell is real-time requirement. It will not be repeated in the following text.

[0091] 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, the pooling requirement is used to indicate whether the BM resources required by the first device need to be created in the pooled resources. Optionally, the data type of the pooling requirement included in the resource requirement information is a Boolean type.

[0092] In implementation 1.3, the sharing requirement is used to indicate that the BM resources required by the first device need to be occupied by a specific tenant or need to be shared by multiple tenants. The tenant may be, for example, an application, a network function, etc. Optionally, the data type of the sharing requirement included in the resource requirement information is a Boolean type.

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

[0094] Implementation 1.5, the mobility requirement is used to indicate whether the BM resources required by the first device need to support mobility applications. The mobility application may be, for example, an application executed by a vehicle-mounted base station. Optionally, the mobility requirement is also used to indicate the maximum number of interruption cycles allowed for reporting of statistical information / alarm information due to mobility by the first device. Optionally, the mobility requirement is also used to indicate the number of statistical information / alarm information allowed to be reported at one time. Optionally, the data type of the mobility requirement included in the resource requirement information is a structure type.

[0095] In addition, in an embodiment of the present application, with respect to any of the above-mentioned requirements, in addition to the content indicated by it mentioned above, it can also be used to indicate other content related to the requirement, without limitation. For example, in addition to being used to indicate whether the BM resources required by the first device need to support real-time applications or deterministic applications, to indicate whether the BM resources required for the first device need to turn on the OS real-time configuration, and to indicate whether the BM resources required by the first device need to be configured using dedicated hardware, the real-time requirement can also be used to indicate other content related to real-time, without limitation. In addition, in addition to including one or more of real-time requirements, pooling requirements, sharing requirements, security requirements, and mobility requirements, the resource requirement information can also include other requirements, without limitation.

[0096] In an optional implementation, the first device determines resource requirement information, including: the first device receives network service lifecycle management requirement information, and the first device determines resource requirement information based on the network service lifecycle management requirement information. The network service lifecycle management requirement information may be, for example, sent by OSS / BSS to the first device. Optionally, the network service lifecycle management requirement information is used to indicate one or more of the following: the type of load carried by the network service, the purpose of the load, the network service's requirements for real-time and / or security and / or mobility, etc. It is understandable that the first device, in the case of an already created network service instance, can convert the network service lifecycle management requirements into requirements for BM resources, which is conducive to the second device allocating BM resources to the BM resource instance to meet the differentiated resource requirements of the network service.

[0097] In another optional implementation, the resource requirement information is determined by the first device without an already created network service instance. It is understandable that the first device determines the resource requirement information in advance without an already created network service instance, which is conducive to the second device allocating BM resources that meet the resource requirement information to the BM resource instance in advance. Then, when the first device instantiates the network service, it can directly select BM resources from the BM resources allocated in advance to run the network service.

[0098] S102: The first device sends resource requirement information to the second device. Correspondingly, the second device receives the resource requirement information from the first device.

[0099] In an optional implementation, resource requirement information is carried in a first request message sent by a first device to a second device, and the first request message also includes resource specification information, and the resource specification information is used to indicate the resource specification requirements of the first device for the BM resource instance. The resource specification can also be understood as the resource size. Exemplarily, a description template (BM flavor) of a BM resource is used to represent the resource specification information, and the BM flavor contains information units of the following attributes: Flavor identification document (identity document, ID), name (Name), CPUs, memory (Memory), root disk (Rootdisc), ephemeral disk (Ephemeral disc), swap space (Swap), wherein the information units of the two attributes of ephemeral disk and swap space are optional information units in the BM flavor. The description of the information units of these attributes can be found in the following Table 1.

[0100] Table 1

[0101]

[0102]

[0103] In an optional manner, 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, and the expected state information is used to indicate the expected state of the BM resource instance by the first device. Exemplarily, the expected state information is specifically used to indicate that the expected state of the BM resource instance by the first device is an activated (Active) state. In addition, the first request message may be, for example, a PATCH BM request message, and the first request message is used to instruct the second device to patch the BM resource instance.

[0104] In another optional manner, the first request message is sent by the first device to the second device using an imperative API. In this case, the first request message is used to request the second device to perform an operation on a BM resource instance. Optionally, the first request message also includes some information related to the operation requested by the first request message. For example, the first request message is used to request the second device to create a BM resource instance, and the first request message also includes information related to the operation of creating a BM resource instance. The first request message is, for example, a Create BM Request message. For another example, the first request message is used to request the second device to instantiate a BM resource, and the first request message also includes information related to the operation of instantiating a BM resource.

[0105] S103: The second device allocates BM resources that meet resource requirement information to the BM resource instance.

[0106] The specific content of step S103 is explained below with respect to the real-time requirements, pooling requirements, sharing requirements, security requirements, and mobility requirements included in the resource demand information, as described in the following optional implementations 2.1 to 2.5.

[0107] In implementation 2.1, the second device determines whether to allocate BM resources supporting real-time applications or deterministic applications to the BM resource instance based on the real-time requirement. It is understandable that if the real-time requirement is used to 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 selects a computing resource type and a storage resource type of a BM resource allocated to the BM resource instance from physical resources within a data center (DC) based on real-time requirements. The computing resource type is, for example, a CPU, a graphics processing unit (GPU), a data processing unit (DPU), etc.

[0109] In implementation 2.2, the second device allocates BM resources to the BM resource instance from the physical resource pool or the independent physical server based on the pooling requirement. It is understandable that if the pooling requirement is used to indicate that the BM resources required by the first device need to be selected from the pooled resources, the second device allocates BM resources to the BM resource instance from the physical resource pool. If the pooling requirement is used to indicate that the BM resources required by the first device do not need to be selected from the pooled resources, the second device allocates BM resources to the BM resource instance from the independent physical server.

[0110] In implementation 2.3, the second device determines a tenant isolation scheme for BM resources allocated to the BM resource instance based on the sharing requirement. It is understandable that if the sharing requirement is used to indicate that the BM resources required by the first device need to be occupied by a specific tenant, the second device allocates BM resources exclusively for the specific tenant to the BM resource instance. If the sharing requirement is used to indicate that the BM resources required 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 also include: the second device determines, based on sharing requirements, which tenants can share the BM resources allocated by the second device for the BM resource instance, and / or determines 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 whether to allocate BM resources supporting security applications to the BM resource instance based on security requirements. Optionally, if the security requirements are used to 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 used for the BM resource instance.

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

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

[0115] The following describes two situations respectively, in which the first device uses a declarative API to send a first request message to the second device and the first device uses an imperative API to send a first request message to the second device, as described in the following optional implementation 3.1 and implementation 3.2.

[0116] Implementation method 3.1, the case where the first device uses a declarative API to send a first request message to the second device. In this case, the state of the BM resource instance to which the BM resources that meet the resource requirement information and resource specification information are allocated in step S103 is: the expected state indicated by the expected state information in the first request message. Then, 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. Then, the first device executes the telecom cloud application based on the deployed BM resource instance. For example, the expected state indicated by the expected state information is an activated state, and the current state of the BM resource instance is an inactive state. The second device allocates BM resources that meet the resource requirement information and resource specification information to the BM resource instance, so as to achieve the migration of the current state of the BM resource instance from an inactive state to an activated state.

[0117] Understandably, the first device uses a declarative API to send the first request message, which can simplify the interoperation between the first device and the second device, thereby reducing the error probability increased due to multiple interoperations, thereby reducing the time cost of rolling back the operation to correct the error. This method can also reduce the complexity of locating and resolving the root cause of BM resource-related faults.

[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 selects a template and configuration file that matches the resource requirement information and the resource specification information for the BM resource instance. Exemplarily, if the resource requirement information indicates a real-time requirement, and the real-time requirement further indicates that the BM resources need to be configured using dedicated hardware, the second device selects a resource description template that supports hardware acceleration or AI acceleration for the BM resources to be allocated, and 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, the second device selects a resource description template in the BM resource pool for the BM resources to be allocated, and the description of the resource specifications in the resource description template matches the resource specification information. After selecting the resource description template, the second device further searches for one or more resource configuration files that match the resource description template.

[0119] In addition, after the second device selects a template and configuration file that matches the resource requirement information and resource specification information for the BM resource instance, the method further includes: the second device determines to perform one or more operations of adding BM resources, reading BM resources, updating BM resources, and deleting BM resources based on the difference between the current state of the BM resource instance and the expected state of the BM resource instance by the first device for the selected template and configuration file. Thereby, BM resources that meet the resource requirement information and resource specification information are allocated to the BM resource instance, and the migration of the BM resource instance from the current state to the expected state is completed. Exemplarily, if the current state of the BM resource instance is an inactive state, and the expected state indicated by the expected state information in the first request message received by the second device is an active state, then the second device determines to perform the operation of adding BM resources, and allocates the 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] Implementation method 3.2, the case where the first device uses an imperative API to send a first request message to the second device. 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 selects a template and configuration file that matches the resource requirement information and resource specification information; the second device performs the operation requested by the first request message on the BM resource instance based on the selected module and configuration file. Thereby, the BM resource instance is allocated BM resources that meet the resource requirement information and resource specification information. The method also includes: the second device uses an imperative API to send a response message to the first device; accordingly, the first device uses an imperative API to receive a response message from the second device. It is understandable that the response message is sent by the second device in response to the first request message.

[0121] Exemplarily, taking the case where 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 selects a template and configuration file that matches the resource requirement information and resource specification information; the second device creates a BM resource instance in which the allocated BM resources meet the resource requirement information and resource specification information based on the selected module and configuration file. The method also includes: the second device uses an imperative API to send a response message to the first device, and the response message includes identification information of the BM resource instance created by the second device; accordingly, the first device uses an imperative API to receive a response message from the second device. Then, 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 the telecom cloud application based on the created BM resource instance.

[0122] To summarize, in the information transmission method, the first device determines resource demand information, and the resource demand information is used to indicate the demand of the first device for the required BM resources, and the resource demand information includes one or more of the following: real-time demand, pooling demand, sharing demand, security demand, and mobility demand. The first device sends resource demand information to the second device. The second device allocates BM resources that meet the resource demand information to the BM resource instance. It can be seen that the BM resources allocated by the second device to the BM resource instance meet the demand of the first device for BM resources. Among them, the demand indicated by the resource demand information can be the demand of the telecom cloud application for BM resources. This method is conducive to the second device deploying BM resource instances that match the differentiated demand of the telecom cloud application for BM resources. In other words, it is conducive to the BM resources allocated by the second device to the BM resource instance to meet the differentiated demand of the telecom cloud application for BM resources.

[0123] The embodiments of the present application also provide an exemplary description of an information transmission method that uses a declarative API to transmit a first request message and an imperative API to transmit a first request message.

[0124] Example 1: A case where a declarative API is used to transmit a first request message. An exemplary information transmission method is as follows: Figure 5 As shown, the following steps are included:

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

[0126] S202, the first device uses a declarative API to send a first request message to the second device, the first request message including resource requirement information, resource specification information and expected state information. The resource specification information is used to indicate the resource specification requirement of the first device for the BM resource instance, and the expected state information is used to indicate the expected state of the first device for the BM resource instance. Accordingly, the second device uses a declarative API to receive the first request message from the first device.

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

[0128] S204: The second device determines to perform one or more operations of adding BM resources, reading BM resources, updating BM resources, and deleting BM resources according to the difference between the current state and the expected state of the BM resource instance for the selected template and configuration file.

[0129] For details about steps S201 to S204, please refer to Figure 4 The relevant explanations in the information transmission method shown also have corresponding beneficial effects and will not be repeated here.

[0130] Example 2: A case where the first request message is transmitted using an imperative API. Taking the first request message as an example for requesting the second device to create a BM resource instance, the exemplary information transmission method is as follows: Figure 6 As shown, the following steps are included:

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

[0132] S302, the first device uses an imperative API to send a first request message to the second device, the first request message is used to request the second device to create a BM resource instance, and the first request message includes resource requirement information and resource specification information. The resource specification information is used to indicate the resource specification requirements of the first device for the BM resource instance. Correspondingly, the second device uses a declarative API to receive the first request message from the first device.

[0133] S303: The second device selects a template and a configuration file that matches the resource requirement information and the resource specification information.

[0134] S304: The second device creates a BM resource instance in which the allocated BM resource meets the resource requirement information and resource specification information based on the selected template and configuration file.

[0135] S305. The second device uses the imperative API to send a response message to the first device, where the response message includes identification information of the BM resource instance created by the second device. Correspondingly, the first device uses the imperative API to receive the response message from the second device.

[0136] For details about steps S301 to S305, please refer to Figure 4 The relevant explanations in the information transmission method shown also have corresponding beneficial effects and will not be repeated here.

[0137] In order to implement the functions of the method provided in the above embodiment of the present application, the first device or the second device may include a hardware structure and / or a software module, and implement the above functions in the form of a hardware structure, a software module, or a hardware structure plus a software module. Whether one of the above functions is executed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.

[0138] like Figure 7 As shown, an embodiment of the present application provides a communication device 700. The communication device 700 may be a first device or a second device, or may be a component of the first device (for example, an integrated circuit, a chip, etc.), or may be a component of the second device (for example, an integrated circuit, a chip, etc.). The communication device 700 may also be other communication units for implementing the method in the method embodiment of the present application. The communication device 700 may include a processing unit 701. Optionally, the communication device 700 may also include a communication unit 702, the processing unit 701 is used to control the communication unit 702 to send and receive data / signaling, and the communication unit 702 may also be referred to as a transceiver unit. Optionally, the communication unit 702 may include a sending unit and a receiving unit, the sending unit may be used to send data / signaling, and the receiving unit may be used to receive data / signaling. Optionally, the communication device 700 may also include a storage unit 703, the storage unit 703 may be used to store information and / or data and / or instructions, etc., and the storage unit 703 may interact with the processing unit 701, or may interact with the communication unit 702.

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

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

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

[0142] In an optional implementation, the real-time requirement is used to indicate whether the required BM resources need to support real-time applications.

[0143] In an optional implementation, the pooling requirement is used to indicate whether the required BM resources need to be selected from the pooled resources.

[0144] In an optional implementation manner, the sharing requirement is used to indicate that 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 resource requirement information, specifically, to determine resource requirement information according to the network service lifecycle management requirement information.

[0146] In an optional implementation, the resource requirement information is carried in a first request message sent to the second device; the first request message also includes resource specification information, and the resource specification information is used to indicate the resource specification requirement for the BM resource instance.

[0147] In an optional implementation, the first request message is sent to the second device using a declarative API; the first request message also includes expected state information, where the expected state information is used to indicate an expected state of the BM resource instance.

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

[0149] In an optional implementation, the first request message is sent to the second device using an imperative API; the first request message is used to request the second device to operate on the BM resource instance. The communication unit 702 is also used to receive a response message from the second device using an imperative API.

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

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

[0152] The processing unit 701 is configured to allocate BM resources that meet resource requirement information to the BM resource instance.

[0153] In an optional 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 an optional implementation manner, the pooling requirement is used to indicate whether the BM resources required by the first device need to be selected from pooled resources.

[0155] In an optional implementation manner, the sharing requirement is used to indicate that 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 an optional implementation, the resource requirement information is carried in a first request message received from the first device; the first request message also includes resource specification information, and the resource specification information is used to indicate the resource specification requirements of the first device for the BM resource instance. The processing unit 701 allocates BM resources that meet the resource requirement information to the BM resource instance, specifically for: allocating BM resources that meet the resource requirement information and the resource specification information to the BM resource instance.

[0157] In an optional implementation, the first request message is received from the first device using a declarative API; the first request message also includes expected state information, and the expected state information is used to indicate the expected state of the BM resource instance by the first device. The state of the BM resource instance that is allocated with BM resources that meet the resource requirement information and resource specification information is the expected state.

[0158] Optionally, the processing unit 701 allocates BM resources that meet the resource requirement information and resource specification information to the BM resource instance, and is specifically used to: select a template and configuration file that matches the resource requirement information and resource specification information for the BM resource instance; for the selected template and configuration file, determine to perform one or more operations of adding BM resources, reading BM resources, updating BM resources, and deleting BM resources based on the difference between the current state and the expected state of the BM resource instance.

[0159] In an optional embodiment, 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 a BM resource instance. The processing unit 701 allocates BM resources that meet resource requirement information and resource specification information to the BM resource instance, specifically for: selecting a template and configuration file that matches the resource requirement information and resource specification information; based on the selected module and configuration file, creating a BM resource instance in which the allocated BM resources meet the resource requirement information and resource specification information. The communication unit 702 is also used to send a response message to the first device using an imperative API, and the response message includes identification information of the created BM resource instance.

[0160] In an optional implementation, 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 a BM resource instance. The processing unit 701 allocates BM resources that meet the resource requirement information and resource specification information to the BM resource instance, specifically for: selecting a template and configuration file that matches the resource requirement information and resource specification information; based on the selected module and configuration file, performing the operation requested by the first request message on the BM resource instance. The communication unit 702 is also used to send a response message to the first device using an imperative API.

[0161] The embodiments of the present application and the method embodiments shown above are based on the same concept, and the technical effects they bring are also the same. For the specific principles, please refer to the description of the embodiments shown above, and no further details will be given.

[0162] The present application embodiment also provides a communication device 800, such as Figure 8 The communication device 800 may be a first device or a second device, or may be a chip, a chip system, or a processor that supports the first device to implement the above method, or may be a chip, a chip system, or a processor that supports the second device to implement the above method. The device may be used to implement the method described in the above method embodiment, and the details may refer to the description in the above method embodiment.

[0163] The communication device 800 may include one or more processors 801. The processor 801 may be used to implement part or all of the functions of the first device or the second device through a logic circuit or running a computer program. The processor 801 may be a general-purpose processor or a dedicated processor, etc. For example, it may be a baseband processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component or a CPU. The baseband processor may be used to process the communication protocol and the communication data, and the central processing unit may be used to control the communication device, execute the software program, and process the data of the software program, wherein the communication device is, for example, a base station, a baseband chip, a terminal, a terminal chip, a distributed unit (DU) or a centralized unit (CU), etc.

[0164] Optionally, the communication device 800 may include one or more memories 802, on which instructions 804 may be stored, and the instructions may be executed on the processor 801, so that the communication device 800 performs the method described in the above method embodiment. Optionally, data may also be stored in the memory 802. The processor 801 and the memory 802 may be provided separately or integrated together.

[0165] The memory 802 may include, but is not limited to, non-volatile memory such as a hard disk drive (HDD) or a solid-state drive (SSD), random access memory (RAM), erasable programmable ROM (EPROM), ROM or portable 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, a transceiver, or a transceiver circuit, etc., for implementing a transceiver function. The transceiver 805 may include a receiver and a transmitter, the receiver may be referred to as a receiver or a receiving circuit, etc., for implementing a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., for implementing a transmitting function.

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

[0168] Processor 801 is used to determine resource demand information, where the resource demand information is used to indicate the demand for required BM resources, and the resource demand information includes one or more of the following: real-time demand, pooling demand, sharing demand, security demand, and mobility demand.

[0169] The transceiver 805 is configured to send resource requirement information to the second device, where the resource requirement information is used to allocate BM resources to the BM resource instance.

[0170] In an optional implementation, the real-time requirement is used to indicate whether the required BM resources need to support real-time applications.

[0171] In an optional implementation, the pooling requirement is used to indicate whether the required BM resources need to be selected from the pooled resources.

[0172] In an optional implementation manner, the sharing requirement is used to indicate that 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, the transceiver 805 is further configured to receive network service lifecycle management requirement information. The processor 801 determines resource requirement information, specifically, to determine resource requirement information according to the network service lifecycle management requirement information.

[0174] In an optional implementation, the resource requirement information is carried in a first request message sent to the second device; the first request message also includes resource specification information, and the resource specification information is used to indicate the resource specification requirement for the BM resource instance.

[0175] In an optional implementation, the first request message is sent to the second device using a declarative API; the first request message also includes expected state information, where the expected state information is used to indicate an expected state of the BM resource instance.

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

[0177] In an optional implementation, the first request message is sent to the second device using an imperative API; the first request message is used to request the second device to operate on the BM resource instance. The transceiver 805 is also used to receive a response message from the second device using an imperative API.

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

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

[0180] Processor 801 is configured to allocate BM resources that meet resource requirement information to a BM resource instance.

[0181] In an optional 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 an optional implementation manner, the pooling requirement is used to indicate whether the BM resources required by the first device need to be selected from pooled resources.

[0183] In an optional implementation manner, the sharing requirement is used to indicate that 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 an optional implementation, the resource requirement information is carried in a first request message received from the first device; the first request message also includes resource specification information, and the resource specification information is used to indicate the resource specification requirements of the first device for the BM resource instance. The processor 801 allocates BM resources that meet the resource requirement information to the BM resource instance, specifically for: allocating BM resources that meet the resource requirement information and the resource specification information to the BM resource instance.

[0185] In an optional implementation, the first request message is received from the first device using a declarative API; the first request message also includes expected state information, and the expected state information is used to indicate the expected state of the BM resource instance by the first device. The state of the BM resource instance that is allocated with BM resources that meet the resource requirement information and resource specification information is the expected state.

[0186] Optionally, processor 801 allocates BM resources that meet resource requirement information and resource specification information to the BM resource instance, and is specifically used to: select a template and configuration file that matches the resource requirement information and resource specification information for the BM resource instance; for the selected template and configuration file, determine to perform one or more operations of adding BM resources, reading BM resources, updating BM resources, and deleting BM resources based on the difference between the current state and the expected state of the BM resource instance.

[0187] In an optional embodiment, 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 a BM resource instance. The processor 801 allocates BM resources that meet resource requirement information and resource specification information to the BM resource instance, specifically for: selecting a template and configuration file that matches the resource requirement information and resource specification information; based on the selected module and configuration file, creating a BM resource instance in which the allocated BM resources meet the resource requirement information and resource specification information. The transceiver 805 is also used to send a response message to the first device using an imperative API, and the response message includes identification information of the created BM resource instance.

[0188] In an optional implementation, 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 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 for: selecting a template and configuration file that matches the resource requirement information and resource specification information; based on the selected module and configuration file, performing the operation requested by the first request message on the BM resource instance. The transceiver 805 is also used to send a response message to the first device using an imperative API.

[0189] In another possible design, the processor 801 may include a transceiver for implementing the receiving and sending functions. For example, the transceiver may be a transceiver circuit, or an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and sending functions may be separate or integrated. The above-mentioned transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or the above-mentioned transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.

[0190] In another possible design, optionally, the processor 801 may store an instruction 803, and the instruction 803 runs on the processor 801, so that the communication device 800 can execute the method described in the above method embodiment. The instruction 803 may be solidified in the processor 801, in which case the processor 801 may be implemented by hardware.

[0191] In another possible design, the communication device 800 may include a circuit that can implement the functions of sending or receiving or communicating in the aforementioned method embodiment. The processor and transceiver described in the embodiments of the present application can be implemented in an integrated circuit (IC), an analog IC, a radio frequency integrated circuit (RFIC), a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0192] Those skilled in the art may also understand that the various illustrative logical blocks and steps listed in the embodiments of the present application may be implemented by electronic hardware, computer software, or a combination of the two. Whether such functions are implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement the functions described for each specific application, but such implementation should not be understood as exceeding the scope of protection of the embodiments of the present application.

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

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

[0195] The present 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] The present application also provides a computer program, which, when executed on a computer, implements the functions of any of the above method embodiments.

[0197] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of 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, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, an SSD), etc.

[0198] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. An information transmission method, characterized in that: The method comprises: Determine resource demand information, where the resource demand information is used to indicate the demand for the required bare metal BM resources, and the resource demand information includes one or more of the following: real-time demand, pooling demand, sharing demand, security demand, and mobility demand; The resource requirement information is sent to the second device, where the resource requirement information is used to allocate BM resources for 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 sharing requirement is used to indicate that 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 a first request message sent to the second device; The first request message also includes resource specification information, where the resource specification information is used to indicate 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 further includes expected state information, where the expected state information is used to indicate an expected state 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 an imperative API; The first request message is used to request the second device to create the BM resource instance; The method further includes: using an imperative API to receive a response message from the second device, wherein the response message includes 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 an imperative API; The first request message is used to request the second device to operate on the BM resource instance; The method further includes: using an imperative API to receive a response message from the second device.

9. An information transmission method, characterized in that: The method comprises: Receive resource demand information from the first device, where the resource demand information is used to indicate the demand of the first device for required bare metal BM resources, where the resource demand information includes one or more of the following: real-time demand, pooling demand, sharing demand, security demand, and mobility demand; Allocate BM resources that meet the resource requirement information to the BM resource instance.

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 pooled resources.

12. The method according to any one of claims 9 to 11, characterized in that: The sharing 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 a first request message received from the first device; The first request message further includes resource specification information, where the resource specification information is used to indicate resource specification requirements of the first device for the BM resource instance; The allocating BM resources that meet the resource requirement information to the BM resource instance includes: allocating BM resources that meet the resource requirement information and the resource specification information to the BM resource instance.

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 further includes expected state information, where the expected state information is used to indicate an expected state of the BM resource instance by the first device; The state of the BM resource instance to which the BM resource satisfying the resource requirement information and the resource specification information is allocated is the desired state.

15. The method according to claim 14, characterized in that The allocating BM resources that meet the resource requirement information and the resource specification information to the BM resource instance includes: Selecting a template and a configuration file matching the resource requirement information and the resource specification information for the BM resource instance; For the selected template and configuration file, according to the difference between the current state of the BM resource instance and the expected state, determine to perform one or more operations of adding BM resources, reading BM resources, updating BM resources and deleting BM resources.

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 allocating BM resources that meet the resource requirement information and the resource specification information to the BM resource instance includes: selecting a template and a configuration file that matches the resource requirement information and the resource specification information; creating a BM resource instance whose allocated BM resources meet 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 an imperative API, wherein the response message includes 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 allocating BM resources that meet the resource requirement information and the resource specification information to the BM resource instance includes: selecting a template and a configuration file that matches 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 also includes: sending a response message to the first device using an imperative API.

18. An information transmission method, characterized in that: The method comprises: The first device determines resource demand information, where the resource demand information is used to indicate the demand of the first device for required bare metal BM resources, and the resource demand information includes one or more of the following: real-time demand, pooling demand, sharing demand, security demand, and mobility demand; 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 that meet the resource requirement information to the BM resource instance.

19. A communication system, characterized in that: The system comprises a first device and a second device; The first device is used to determine resource demand information, where the resource demand information is used to indicate the demand of the first device for required bare metal BM resources, and the resource demand information includes one or more of the following: real-time demand, pooling demand, sharing demand, security demand, and mobility demand; The first device is further configured to send the resource requirement information to the second device; The second device is used to receive the resource requirement information from the first device; The second device is further configured to allocate BM resources that meet the resource requirement information to the BM resource instance.

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

21. A communication device, characterized in that: Including processors; The processor is used to execute a computer program or instruction in a memory so that the communication device executes the method according to any one of claims 1 to 9, or so that the communication device executes 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, and when the computer program is executed, the method according to any one of claims 1 to 9 is implemented, or the method according to any one of claims 10 to 18 is implemented.

23. A computer program product, characterized in that The computer program product comprises: a computer program code, and when the computer program code is run, the method according to any one of claims 1 to 9 is implemented, or the method according to any one of claims 10 to 18 is implemented.

Images