Communication method and communication apparatus

Abstract

The application provides a communication method and a communication device. In the communication method, a first application corresponds to N triggers, and the N triggers have a one-to-one correspondence with N resource template information, N trigger description information and N service labels. The N triggers are used for a service requester to select a trigger corresponding to a required service label from the N triggers and request a service. When the service requester requests a first device to provide a service of the first application through a target trigger in the N triggers, the first device can create a target function instance based on target resource template information corresponding to the target trigger, based on a correspondence between the N triggers and the N resource template information, and the target function instance is used to provide a service indicated by a service label corresponding to the target trigger. According to the technical scheme, the first device can create a function instance based on different resource template information, and the utilization rate of a computing resource is improved.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly to a communication method and a communication device. Background Technology

[0002] Terminals can provide services to users through included applications. However, some applications require significant computation when providing services. If all the computation for these services were to be performed on the terminal, it could lead to overheating and a sharp reduction in the terminal's usability.

[0003] Therefore, to improve terminal lifespan, edge computing offloading (also known as computing power offloading or task offloading) has been proposed. Edge computing offloading refers to offloading the computation required by an application to provide services to another device (such as a cloud server). For example, for applications providing XR services, the cloud server can render the image and send the rendered image to the terminal for display.

[0004] However, there is currently a problem of low utilization of computing resources when the computation required by an application to provide services is performed on another device. Computing resources refer to the resources allocated for the computation, such as central processing unit (CPU) resources, graphics processing unit (GPU) resources, neural processing unit (NPU) resources, data processing unit (DPU) resources, etc. Summary of the Invention

[0005] This application provides a communication method and a communication device that can improve the utilization of computing resources when implementing end-side computing offloading.

[0006] In a first aspect, this application provides a communication method applicable to a function management (FM) module. The communication method includes: receiving first information from a network functions virtualization orchestrator (NFVO) module, the first information indicating N resource template information of a first application and N trigger description information corresponding one-to-one with the N resource template information, wherein the N resource template information indicates different computing resources and corresponds to different service labels, and N is a positive integer greater than 1; sending second information to an infrastructure management (IM) module, the second information requesting the IM module to create triggers based on the N trigger description information; receiving third information from the IM module, the third information indicating the N triggers corresponding one-to-one with the N trigger description information; and sending the third information to the NFVO module.

[0007] In this application, the device including the FM module, NFVO module and IM module is also referred to as the first device.

[0008] Service tags can be described, for example, as service identifiers. Different service tags for the first application are used to indicate the different services that the first application can provide.

[0009] The second information may include descriptions of N triggers.

[0010] The third piece of information is used to indicate the N triggers that correspond one-to-one with the N trigger description information. It can also be described as the third piece of information indicating the access information of the N triggers that correspond one-to-one with the N trigger description information. For example, the access information of a trigger is its Internet Protocol (IP) address.

[0011] In this technical solution, the IM module can create N triggers for the first application, and these N triggers have a one-to-one correspondence with N resource template information, N trigger description information, and N service tags. The N triggers created by the IM module are used by the service requester to select the trigger corresponding to the desired service tag from the N triggers and request the service. Thus, when the service requester requests the first device to provide the service of the first application through the target trigger among the N triggers, the first device can create a target function instance based on the correspondence between the N triggers and the N resource template information, and based on the target resource template information corresponding to the target trigger. This target function instance is used to provide the service indicated by the service tag corresponding to the target trigger. Based on the technical solution provided in the first aspect, when different triggers request the creation of function instances, the first device can create function instances based on different resource template information, thereby improving the utilization rate of computing resources.

[0012] Understandably, the first information can also be considered as information used to request the creation of triggers based on N trigger description information.

[0013] In one possible implementation, the above method further includes: based on the first information and the third information, retaining the correspondence between N resource template information and N triggers.

[0014] The correspondence between N resource template information and N triggers can also be described as the correspondence between retaining the access information of N resource template information and N triggers.

[0015] Based on this implementation, the first trigger among the N triggers can send fourth information to the FM module. The fourth information is used to request the creation of a function instance. Correspondingly, the FM module obtains the first resource template information corresponding to the first trigger based on the correspondence between the N resource template information and the N triggers, and instructs the first trigger to create a function instance based on the first resource template information, so as to provide the service indicated by the service tag corresponding to the first trigger.

[0016] In one scenario, if after determining the first resource template information, it is found that the IM module has not yet allocated computing resources based on the first resource template information, the FM module will first request the first computing resources that satisfy the first resource template information from the IM module before instructing the first trigger to create a function instance based on the first resource template information, so as to create a function instance in the first computing resources.

[0017] The FM module requests a first computing resource from the IM module that satisfies the first resource template information. This can also be described as: the FM module requests the IM module to allocate a first computing resource for creating a function instance based on the first resource template information.

[0018] In one possible implementation, the method further includes: receiving second resource template information indicated by the NFVO module, the second resource template information corresponding to a second trigger among N triggers, the second trigger being used to send fifth information to the NFVO module for requesting the creation of a function instance; and indicating to the second trigger the function instance created based on the second resource template information.

[0019] Understandably, the information sent by the NFVO module to the FM module indicating the second resource template information can also be considered as a request to the FM module to create a function instance. Therefore, receiving the second resource template information indicated by the NFVO module can be replaced by receiving indication information sent by the NFVO module, which is used to request the FM module to create a function instance based on the second resource template information. For example, the indication information includes the second resource template information or an identifier of the second resource template information.

[0020] Based on this implementation, the second trigger among the N triggers can send the fifth information to the NFVO module. The fifth information is used to request the creation of a function instance. Correspondingly, the NFVO module obtains the second resource template information corresponding to the second trigger based on the correspondence between the N resource template information and the N triggers, and instructs the second resource template information to the FM module. This enables the FM module to instruct the second trigger to create a function instance based on the second resource template information, thereby providing the service indicated by the service tag corresponding to the second trigger.

[0021] Secondly, this application provides a communication method applicable to an NFVO module. The communication method includes: receiving sixth information, which indicates N service tags, N resource template information, and N trigger description information of a first application, wherein the service tags, resource template information, and trigger description information have a one-to-one correspondence, and the N resource template information indicates different computing resources, where N is a positive integer greater than 1; sending first information to an FM module, which indicates the N resource template information of the first application and N trigger description information corresponding one-to-one with the N resource template information, wherein the N trigger description information is used to create N triggers; receiving third information from the FM module, which indicates the N triggers corresponding one-to-one with the N trigger description information; and sending seventh information based on the sixth and third information, which indicates the correspondence between the N service tags and the N triggers.

[0022] In this technical solution, N triggers can be created for the first application, and these N triggers have a one-to-one correspondence with N resource template information, N trigger description information, and N service tags. Thus, when a service requester requests the first device to provide the service of the first application through a target trigger among the N triggers, the first device can create a target function instance based on the correspondence between the N triggers and the N resource template information, and based on the target resource template information corresponding to the target trigger. This target function instance is used to provide the service indicated by the service tag corresponding to the target trigger. Based on the technical solution provided in the first aspect, when different triggers request the creation of function instances, the first device can create function instances based on different resource template information, thereby improving the utilization rate of computing resources.

[0023] Understandably, the first information can also be considered as information used to request the creation of triggers based on N trigger description information.

[0024] In one possible implementation, N triggers are used by the service requester to select the trigger corresponding to the desired service label from the N triggers and request the service.

[0025] In one possible implementation, sending the seventh message includes sending the seventh message to the third-generation partnership project (3GPP) system.

[0026] For example, in one scenario, after receiving a subscription request from a terminal, the 3GPP system forwards the request to a first device. Correspondingly, the first device sends the seventh information to the 3GPP system, enabling the 3GPP system to understand the correspondence between N service tags and N triggers. Further, the 3GPP system can send each service tag of the first application to the terminal with the subscription request. Thus, when the terminal needs the service of the first application, it can send the service tag of the desired service to the 3GPP system. Based on the correspondence between the N service tags and N triggers, the 3GPP system sends a request to the trigger corresponding to that service tag to request the service indicated by that service tag.

[0027] In one possible implementation, the method further includes: retaining the correspondence between N resource template information and N triggers based on third information.

[0028] Based on this implementation, the second trigger among the N triggers can send the fifth information to the NFVO module. The fifth information is used to request the creation of a function instance. Correspondingly, the NFVO module obtains the second resource template information corresponding to the second trigger based on the correspondence between the N resource template information and the N triggers, and instructs the second resource template information to the FM module. This enables the FM module to instruct the second trigger to create a function instance based on the second resource template information, thereby providing the service indicated by the service tag corresponding to the second trigger.

[0029] Thirdly, this application provides a communication method applicable to a first device. The communication method includes: an NFVO module receiving sixth information, the sixth information indicating N service tags, N resource template information, and N trigger description information of a first application, wherein there is a one-to-one correspondence between the service tags, resource template information, and trigger description information, and the N resource template information indicates different computing resources, where N is a positive integer greater than 1; the NFVO module sending first information to an FM module, the first information indicating the N resource template information of the first application and N trigger description information corresponding one-to-one with the N resource template information, the N trigger description information being used to create N triggers; an IM module sending third information to an FM module, the third information indicating the N triggers corresponding one-to-one with the N trigger description information; the NFVO module sending seventh information, the seventh information indicating the correspondence between the N service tags and the N triggers; responding to an eighth information sent by the third trigger, determining the third resource template information corresponding to the third trigger based on the correspondence between the N triggers and the N resource template information, the eighth information being used to request the creation of a function instance; and indicating to the third trigger the function instance created based on the third resource template information.

[0030] In this technical solution, the IM module can create N triggers for the first application, and these N triggers have a one-to-one correspondence with N resource template information, N trigger description information, and N service tags. The N triggers created by the IM module are used by the service requester to select the trigger corresponding to the desired service tag from the N triggers and request the service. Thus, when the service requester requests the first device to provide the service of the first application through a third trigger among the N triggers, the first device can create a function instance based on the correspondence between the N triggers and the N resource template information, and based on the third resource template information corresponding to the third trigger. This function instance is used to provide the service indicated by the service tag corresponding to the third trigger. Based on the technical solution provided in the third aspect, when different triggers request the creation of function instances, the first device can create function instances based on different resource template information, thereby improving the utilization rate of computing resources.

[0031] Understandably, the first information can also be considered as information used to request the creation of triggers based on N trigger description information.

[0032] In one possible implementation, N triggers are used by the service requester to select the trigger corresponding to the desired service tag from the N triggers and request the service.

[0033] In one possible implementation, the NFVO module receives the sixth information, which includes: the NFVO module receiving the sixth information from the operations support system and business support system (OSS / BSS).

[0034] In one possible implementation, sending the seventh message includes sending the seventh message to the 3GPP system.

[0035] Fourthly, this application provides a communication device capable of implementing any of the first to third aspects and any possible implementations of the first to third aspects of the method described. The device includes corresponding modules for performing the described methods. The modules included in the device can be implemented in software and / or hardware.

[0036] Fifthly, this application provides a communication device including a processor that can be used to execute a computer program in a memory to implement the methods described in the first to third aspects and any possible implementations of the first to third aspects.

[0037] Optionally, the device further includes a communication interface, to which the processor is coupled. The communication interface is used to receive signals from other communication devices outside the device and transmit them to the processor, or to send signals from the processor to other communication devices outside the device. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, pin, or other type of communication interface.

[0038] Optionally, the device further includes a memory, to which the processor is coupled. The memory stores program instructions and data. The memory is coupled to the processor, which, when executing the instructions stored in the memory, can implement the methods described in the preceding aspects.

[0039] Sixthly, this application provides a communication device, including a processor and a communication interface. The communication interface is used to receive signals from other communication devices besides the communication device and transmit them to the processor, or to send signals from the processor to other communication devices besides the communication device. The processor implements the methods described in the first to third aspects and any possible implementations of the first to third aspects through logic circuits or executing code instructions. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, pin, or other type of communication interface.

[0040] Optionally, the apparatus further includes a memory for storing instructions and data. The memory may be coupled to the processor, which, when executing the instructions stored in the memory, implements the methods described in the first to third aspects and any possible implementation thereof.

[0041] In a seventh aspect, this application provides a communication device including a processor and a memory, the memory being used to store instructions and data, wherein when the processor executes the instructions stored in the memory, it can implement the methods described in the first to third aspects and any possible implementation of the first to third aspects.

[0042] Optionally, the device further includes a communication interface for communicating with other communication devices. For example, the communication interface may be a transceiver, circuit, bus, module, pin, or other type of communication interface.

[0043] Eighthly, this application provides a computer-readable storage medium storing a computer program or instructions that, when executed, implement the methods described in the first to third aspects and any possible implementations of the first to third aspects.

[0044] Ninthly, this application provides a computer program product including instructions that, when executed, implement the methods described in the first to third aspects and any possible implementations of the first to third aspects.

[0045] In a tenth aspect, this application provides a chip system including at least one processor for supporting the implementation of the functions involved in the first to third aspects and any possible implementation of the first to third aspects, such as receiving or processing data involved in the above methods.

[0046] In one possible design, the chip system also includes a memory for storing program instructions and data, which may be located within or outside the processor.

[0047] The chip system can consist of chips or include chips and other discrete components. Attached Figure Description

[0048] Figure 1 A schematic diagram of the NFV architecture is shown;

[0049] Figure 2 A schematic diagram of an existing computation offloading architecture is shown;

[0050] Figure 3 This diagram illustrates the computing resources on which the FM module creates function instances and the actual computing resources required.

[0051] Figure 4 A flowchart illustrating a communication method provided in one embodiment of this application;

[0052] Figure 5 A schematic diagram of the system architecture applicable to the communication method provided in this application;

[0053] Figure 6 This diagram illustrates the correspondence between service tags, triggers, and resource template information.

[0054] Figure 7 A flowchart illustrating a communication method provided in another embodiment of this application;

[0055] Figure 8 A flowchart illustrating a communication method provided in yet another embodiment of this application;

[0056] Figure 9 This is a structural schematic diagram of a communication device provided in one embodiment of this application;

[0057] Figure 10 This is a structural schematic diagram of a communication device provided for another embodiment of this application. Detailed Implementation

[0058] For ease of understanding, some terms used in this application are explained below.

[0059] 1. Network Function Virtualization (NFV)

[0060] NFV refers to the use of virtualization technology from the information technology (IT) field by telecommunications network operators to decouple the implementation of some telecommunications network functions (such as core network functions) in software and hardware within general-purpose servers, switches, and storage. This enables the rapid and efficient deployment and operation of network services (NS), while simultaneously saving on network investment (CAPEX) and operating expenses (OPEX). By applying NFV technology, telecommunications network functions are implemented in software and can run on general-purpose server hardware. They can be migrated, instantiated, and deployed in different physical locations within the network as needed, without requiring the installation of new equipment. NFV standardization efforts primarily focus on the dynamic management and orchestration (MANO) of network services, virtualized network functions (VNFs), and virtual resources.

[0061] Figure 1 This is a schematic diagram of the architecture of an NFV system provided in an embodiment of this application. Figure 1 As shown, the NFV system includes functional components such as the operations support system and business support system (OSS / BSS) of the mobile network, the network functions virtualization orchestrator (NFVO), the virtual network function manager (VNFM), the virtual infrastructure management (VIM), the network functions virtualization infrastructure (NFVI), the equipment management system (EM), and multiple virtualized network function (VNF) modules.

[0062] OSS / BSS: refers to the operator's existing operation and maintenance system OSS / BSS.

[0063] NFVO: NFVO implements the management and processing of network service descriptors (NS descriptors, NSDs), virtual network function forwarding graphs (VNFforwarding graphs, VNFFGs), and network service lifecycle management. It works with VNFM to implement VNF ​​lifecycle management and has a global view of virtual resources.

[0064] VNFM: VNFM performs lifecycle management of Virtualized Network Functions (VNFs), including VNF descriptor (VNFD) management, VNF instantiation, VNF instance scaling, VNF instance healing, and VNF instance termination. VNFM also supports receiving scaling policies from NFVO to achieve automated scaling.

[0065] NFVI: NFVI is the infrastructure layer of NFV, encompassing hardware resources, virtual resources, and a virtualization layer to establish, deploy, manage, and implement virtualized environments (VNFs). Hardware resources include, for example, computing hardware, storage hardware, and network hardware. The virtualization layer abstracts hardware resources, decoupling VNFs from the underlying hardware resource layer. For instance, the virtualization layer includes virtual computing derived from abstracted computing hardware, virtual storage derived from abstracted storage hardware, and virtual networking derived from abstracted network hardware. From the perspective of a VNF, the virtualization layer and hardware resources appear as a single, complete entity capable of providing the required virtual resources.

[0066] VIM: Controls and manages the interaction between VNF and computing hardware, storage hardware, network hardware, virtual computing, virtual storage, and virtual networks. It is responsible for the management of infrastructure layer hardware resources and virtualized resources (including reservation and allocation), monitoring the status of virtual resources and reporting faults, and providing a virtualized resource pool for upper-layer applications. VNFM and VIM can communicate with each other, request resource allocation, and exchange virtualized hardware resource configuration and status information.

[0067] EM: Performs traditional fault management, configuration management, account management, performance management, and security management (FCAPS) functions for VNF.

[0068] VNF: Corresponds to physical network functions (PNFs) in traditional non-virtualized networks, such as virtualized evolved packet core (EPC) nodes, including mobility management entities (MMEs), serving gateways (SGWs), and packet data network gateways (PGWs). The functional behavior and state of network functions are independent of virtualization; NFV technology requirements aim for VNFs and PNFs to have the same functional behavior and external interfaces.

[0069] 2. Serverless architecture

[0070] Serverless architecture is the latest emerging business software platform architecture. It allows developers to get rid of the work of setting up and managing backend devices and focus only on designing the business logic of functions.

[0071] Serverless architecture consists of Function as a Service (FaaS) and Backend as a Service (BaaS). FaaS abstracts functions as services and provides them to developers, who can then develop, run, and manage applications using lightweight, function-level services without needing to worry excessively about the deployment of underlying cloud infrastructure resources. BaaS provides ready-to-use backend services, including databases, authentication, and file storage, and is typically managed by the cloud service provider.

[0072] Terminals can provide services to users through included applications (APPs). For example, some applications on the terminal can provide artificial intelligence (AI) intelligent assistant services, some can provide distributed rendering services, and some can provide augmented reality (AR) intelligent navigation services, etc.

[0073] Applications require computation to provide services. Computation requires resources, such as central processing unit (CPU) resources, graphics processing unit (GPU) resources, neural processing unit (NPU) resources, and data processing unit (DPU) resources. In this application, the resources allocated for computation will be referred to as computing resources or computing power resources, and the following description will use computing resources as an example.

[0074] Running all service computations on the terminal can lead to overheating, drastically reduced usage time, and ultimately, a negative user experience. Therefore, to extend terminal lifespan, on-device computation offloading (or computing power offloading) has been proposed. On-device computation offloading refers to moving the computations performed by an application to a server (such as a cloud server). For example, for applications providing extended reality (XR) services, the cloud server can render the image and send it to the terminal for display.

[0075] Below, in conjunction with Figure 2 This describes a computational unloading process. For example... Figure 2 As shown, it includes:

[0076] Step 1: OSS / BSS uploads the installation package of the target application developed based on the serverless architecture to the NFVO in the NFV system to request the NFVO to deploy the installation package of the target application.

[0077] Specifically, the installation package includes: code package, application runtime image file, resource template information, and trigger description information.

[0078] The code package contains the target application's program code. Understandably, the target application's program code typically consists of functions.

[0079] The resource template information indicates the computational resources required to create a function instance of the target application. Computational resources include, for example, the storage size required to create a function instance of the target application, and the CPU / DPU / NPU / GPU requirements.

[0080] The trigger description information is used in the NFV system to create triggers for the target application's IM. Specifically, the function of the target application's trigger is: when the trigger detects a request for services from the target application, it sends a request to the function management (FM) in the NFV system to request the creation of a function instance for the target application, thus triggering the FM to create the function instance of the target application. The requester requesting services from the target application (also called the service requester) can request the NFV system to provide the target application's services by sending a request (also called a service request) to the target application's trigger. In other words, the function of the target application's trigger is: when the trigger detects that it has been triggered, it will trigger the FM to create a function instance of the target application. For example, if the target application's program code includes program code for an image processing function, which is used to process images and is associated with data storage events, then in this scenario, when the trigger detects that a user has uploaded an image, the trigger is triggered, thereby triggering the FM to create an instance of the image processing function.

[0081] Step 2: After receiving the target application's installation package, NFVO checks the package's integrity and validity. Once the check is complete and passes, it sends a response to OSS / BSS to notify that the target application's installation package has been successfully deployed.

[0082] Step 3: NFVO sends the resource template information and trigger description information from the installation package to the function management (FM).

[0083] Step 4: FM requests the Infrastructure Management (IM) manager to create a trigger for the target application based on the trigger description information.

[0084] Specifically, FM sends the trigger description information of the target application to IM, and IM creates the trigger for the target application based on the trigger description information.

[0085] After the trigger for the target application is created, if the trigger for the target application detects a service request from the service requester, the following process is also included:

[0086] Step 5: The target application's trigger requests an FM creation function instance.

[0087] Step 6: After receiving the request, if FM determines that there is an available function instance, it will proceed to step 9; if it determines that there is no available function instance, it will proceed to step 7.

[0088] Step 7: FM sends the resource template information from the installation package of the target application to IM to request IM to allocate computing resources based on the resource template information.

[0089] Step 8: FM creates a function instance on the computing resource.

[0090] Step 9: FM sends the address of the created function instance to the trigger.

[0091] Step 10: After receiving the address of the function instance, the trigger requests the function instance to provide services. Correspondingly, the function instance returns the calculation result to the trigger.

[0092] exist Figure 2 In the computation offloading scheme shown, when multiple service requesters simultaneously trigger the target application's trigger to request the NFV system to provide the target application's services, this is also known as a concurrent request scenario. The NFV system will create a function instance for each service request to provide the target application's services to these multiple service requesters simultaneously. The specific implementation method for creating a function instance for each service request is detailed in steps 5 to 8 above, and will not be elaborated here.

[0093] However, the above implementation method suffers from low resource utilization. Specifically, when different service requesters request services from the target application, the computational load required by the target application may differ, meaning the actual required computational resources may vary. However, based on the above implementation method, when the FM in the NFV system creates function instances corresponding to different service requests, because the IM in the NFV system allocates computational resources for FM function instance creation based on the same resource template information, the IM allocates the same computational resources to function instances corresponding to different service requests. This can lead to an over-allocation of computational resources to some function instances or an under-allocation of computational resources to others, resulting in low computational resource utilization.

[0094] To facilitate understanding, let's take a digital graphics application as an example. For instance, User 1 needs a digital graphics application to process batches of images, while User 2 (an art student) needs it to complete their graduation project. That is, both User 1 and User 2 require services from the digital graphics application. Let's call the service requested by User 1 Service 1 and the service requested by User 2 Service 2. From a computational complexity perspective, the computational workload of providing Service 1 is significantly different from that of providing Service 2. Furthermore, the actual computational resources required for providing Service 1 are less than those required for providing Service 2. However, in existing technologies, the computational resources allocated to Service 1 and Service 2 are the same. For example... Figure 3As shown, there may be issues where the actual computing resources required for service request 1 are less than the computing resources created by the resource template information in the installation package of the NFV system based on the digital drawing application, and the actual computing resources required for service request 2 are greater than the computing resources created by the resource template information in the installation package of the NFV system based on the digital drawing application.

[0095] In view of this, this application provides a communication method and a communication device to improve the utilization of computing resources when implementing end-side computing offloading.

[0096] The technical solution provided in this application will now be described in conjunction with the accompanying drawings.

[0097] Figure 4 This is a flowchart illustrating a communication method provided in one embodiment of this application. The method can be applied to an NFV system, which includes an NFVO module, an FM module, and an IM module. Figure 4 As shown, the method includes:

[0098] S401, the NFVO module receives the sixth information, which is used to indicate the N service tags, N resource template information and N trigger description information of the first application. There is a one-to-one correspondence between the service tags, resource template information and trigger description information, and N is a positive integer greater than 1.

[0099] In this application, service tags can also be replaced with service identifiers. One of the N service tags is used to identify a service of the first application. These N service tags can identify the N services provided by the first application; that is, the N service tags can be considered to correspond one-to-one with the N services provided by the first application. For example, if the first application can provide service 1, service 2, service 3, and service 4, then these four services can be associated with four service tags. Different service tags among these four service tags are used to identify different services within the four services. For instance, services 1 through 4 can belong to the same type of service (e.g., batch image processing service), but each service requires different performance (e.g., different computational complexity); or services 1 through 4 can belong entirely or partially to different types of services (e.g., service 1 belongs to batch image processing service, and service 2 belongs to image design and drawing service).

[0100] In this application, each of the N resource template information pieces indicates the required computing resources, and the computing resources indicated by different resource template information pieces are different. Computing resources include, for example, the storage size required when creating a function instance of the first application, and the requirements for CPU / DPU / NPU / GPU. The concept of computing resources can be referred to the preceding description and will not be repeated here.

[0101] In this application, one of the N trigger descriptions is used to create a trigger for the first application. These N trigger descriptions can be used to create N triggers for the first application. That is, it can be understood that there is a one-to-one correspondence between the N trigger descriptions and the N triggers for the first application. For example, the trigger descriptions include the trigger conditions for each of the N triggers. When a trigger (e.g., denoted as trigger #1) detects that its corresponding trigger condition is met, trigger #1 requests the creation of a function instance. For instance, if the trigger condition for trigger #1 is a user uploading an image, then when trigger #1 detects the user-uploaded image, trigger #1 requests the creation of a function instance.

[0102] In one implementation, the sixth information also includes a code package, which includes the program code of the first application and / or the application runtime image file of the first application.

[0103] In this application, there is a one-to-one correspondence between service tags, resource template information, and trigger description information. That is, one service tag among N service tags corresponds to one resource template information among N resource template information and one trigger description information among N trigger description information, and different service tags among N service tags correspond to different resource template information among N resource template information and different trigger description information among N trigger description information.

[0104] In one implementation, the NFVO module receives the sixth information, including: the NFVO module receiving the sixth information from OSS / BSS. That is, the sixth information is sent to the NFVO module by OSS / BSS. Optionally, the NFVO module can check the sixth information from OSS / BSS, such as checking the integrity and validity of the sixth information, and send a response to OSS / BSS when the verification is successful.

[0105] S402, the NFVO module sends the first information to the FM module. The first information is used to indicate the N resource template information of the first application and the N trigger description information corresponding one-to-one with the N resource template information.

[0106] In other words, the NFVO module indicates the N resource template information and the N trigger description information corresponding one-to-one with the N resource template information to the FM module through the first information. The meaning of the trigger description information is as described in S401, and will not be repeated here.

[0107] S403, the FM module sends a second message to the IM module, which requests the IM module to create a trigger based on N trigger description information; correspondingly, the IM module creates a trigger based on the N trigger description information.

[0108] For example, the second information includes N trigger descriptions.

[0109] In this application, one trigger description is used to create one trigger, and the IM module can create N triggers based on N trigger descriptions. That is, there is a one-to-one correspondence between the N triggers created by the IM module and the N descriptions.

[0110] Understandably, since there is a one-to-one correspondence between the N triggers and the N trigger descriptions, and there is also a one-to-one correspondence between the N trigger descriptions, the N resource templates, and the N service tags, there is a one-to-one correspondence between the N triggers, the N trigger descriptions, the N resource templates, and the N service tags.

[0111] S404, the IM module sends third information to the FM module. The third information is used to indicate the N triggers that correspond one-to-one with the description information of the N triggers.

[0112] The third piece of information is used to indicate the N triggers that correspond one-to-one with the description information of the N triggers. It can also be expressed as: the third piece of information is used to indicate the access information of the N triggers that correspond one-to-one with the description information of the N triggers. For example, the access information of the N triggers includes the IP addresses of each of the N triggers.

[0113] In this application, the third information used to indicate the N triggers that correspond one-to-one with the description information of the N triggers can be implemented in different ways.

[0114] For example, in one implementation, the third information includes a correspondence between N trigger descriptions and N trigger identifiers, so that the FM module can determine which trigger description information each trigger created by the IM module is based on based on this correspondence.

[0115] For example, in another implementation, the third information includes the IP addresses of N triggers. These N trigger IP addresses are located at N positions in the third information, and the triggers indicated by the IP addresses at different positions in the third information are created based on different trigger description information. That is, in this implementation, the position of each trigger's IP address in the third information implicitly indicates the trigger description information corresponding to that trigger. Correspondingly, after receiving the third information, the FM module determines which trigger description information corresponds to each trigger based on the position of its IP address in the third information. For example, the third information includes the IP addresses of four triggers. The trigger corresponding to the first IP address is created based on the first trigger description information out of the N trigger description information; the trigger corresponding to the second IP address is created based on the second trigger description information out of the N trigger description information; the trigger corresponding to the third IP address is created based on the third trigger description information out of the N trigger description information; and the trigger corresponding to the fourth IP address is created based on the fourth trigger description information out of the N trigger description information. It is understood that this is merely an example using N equal to 4 and does not constitute a limitation of this application.

[0116] S405, the FM module sends third information to the NFVO module.

[0117] As described in S403, since there is a one-to-one correspondence between the N triggers and their descriptions, and a one-to-one correspondence between the N trigger descriptions, the N resource templates, and the N service tags, there is a one-to-one correspondence between the N triggers, their descriptions, resource templates, and service tags. Therefore, when the FM module indicates the N triggers corresponding to the N trigger descriptions to the NFVO module, the NFVO module can determine the one-to-one correspondence between the N service tags and the N triggers based on the one-to-one correspondence between the service tags, resource templates, and trigger descriptions, and between the N trigger descriptions and the N triggers. In other words, it determines which service tag from the N service tags each of the N triggers corresponds to.

[0118] For example, when the third piece of information is used to indicate the N triggers that correspond one-to-one with the N trigger description information, it indicates the IP addresses of the N triggers. Then, the NFVO module can retain the mapping between the trigger IP addresses and the N service tags.

[0119] S406, the NFVO module sends the seventh information to the service requester based on the sixth and third information. The seventh information is used to indicate the correspondence between N service tags and N triggers.

[0120] In this application, the service requester refers to the party that can trigger the NFV system to provide services by triggering a trigger in the NFV system.

[0121] For example, in one scenario, if a terminal triggers an NFV system trigger to provide services, the terminal is considered the service requester.

[0122] For example, in another scenario, if the terminal requests the NFV system to provide the service for the first application through the 3GPP system, then the 3GPP system is considered the service requester.

[0123] In this application, the NFVO module indicates the mapping between N service tags and N triggers to the service requester through the seventh information. That is, the mapping between N service tags and N triggers is exposed to the service requester through the seventh information. Thus, a service requester requesting the NFV system to provide a first application service can select the target trigger corresponding to the service tag of the desired service from the N triggers to request the required service through that target trigger. Correspondingly, the NFV system creates a function instance based on the resource template information corresponding to the target trigger to provide the service to the service requester.

[0124] In one implementation, after the NFVO module receives a subscription request from the service requester, the NFVO module exposes the correspondence between N service tags and N triggers to the service requester through the seventh information.

[0125] For example, in one scenario, when the NFVO module receives a subscription request from a terminal transmitted through the 3GPP system, the NFVO module exposes the mapping between N service tags and N triggers to the 3GPP system through the seventh information. The subscription request is used to request subscription to the service of the first application in the NFV system. Further, after receiving the seventh information, 3GPP indicates the various service tags of the first application to the terminal. Thus, for a terminal requesting the service of the first application from the NFV system, it can indicate the service tag of the service required by the first application to the 3GPP system. Correspondingly, after receiving the service tag, the 3GPP system selects the target trigger from the N triggers that corresponds to the service tag of the required service to request the required service. Correspondingly, the NFV system creates a function instance based on the resource template information corresponding to the target trigger to provide the service to the service requester.

[0126] based on Figure 4The provided communication method creates N triggers for the first application, and there is a one-to-one correspondence between the N triggers, their descriptions, resource templates, and service tags. This allows the service requester to select a target trigger from the N triggers that corresponds to the service tag of the desired service to request the required service. For the NFV system, based on the one-to-one correspondence between the N triggers and the N resource templates, when different triggers request the creation of function instances, function instances are created based on different resource templates corresponding to different triggers. This ensures that the computational resources of the created function instances are better matched to the required service, thereby improving the utilization of computational resources.

[0127] Below, in conjunction with Figure 5 This indicates that it applies to this application. Figure 4 An architecture of an NFV system is provided as an example. For example... Figure 5 As shown:

[0128] OSS / BSS or a third-party platform can send the installation package of the first application to be deployed on the NFV system to the NFV system. In this application, the installation package of the first application includes the code package of the first application, the application runtime image file of the first application, different resource template information, and service tags and trigger descriptions corresponding to each resource template. For example, service tags can be in human-readable language, such as free version, standard version, professional version, master version, etc. Specifically, after the NFV system receives the installation package of the first application:

[0129] The NFVO module sends the different resource template information from the first application's installation package and the trigger description information corresponding to each resource template information to the FM module.

[0130] After receiving different resource template information and the corresponding trigger description information, the FM module requests the IM module to create triggers corresponding to each different resource template information. The IM module is used to control and manage infrastructure resources (physical or virtual infrastructure resources), such as the allocation of computing, network, and storage resources, and the collection and reporting of infrastructure performance indicators and related events.

[0131] After receiving a request from the FM module, the IM module creates different triggers based on different trigger description information and indicates the IP address of each trigger created based on the trigger description information to the IM module.

[0132] After receiving the IP addresses of each trigger created based on the trigger description information from the IM instruction, the IM module will indicate the IP addresses of the triggers corresponding to the trigger description information to the NFVO module.

[0133] After receiving the IP address of the trigger corresponding to each trigger description information indicated by the IM, the NFVO module retains the correspondence between different triggers and service tags.

[0134] Subsequently, if the NFV system receives a request from a terminal to subscribe to the service of the first application transmitted through the 3GPP system, the NFV system can send the mapping relationship of triggers and service tags retained by the NFVO module to the terminal through the 3GPP system.

[0135] From the outside of the NFV system, different triggers are bound to different service labels. A terminal's request to 3GPP can carry the service label required by the terminal, enabling 3GPP to initiate a service request to the trigger corresponding to that service label; alternatively, the terminal can instruct 3GPP, based on the obtained mapping between service labels and triggers, to initiate a service request to a specific trigger, which corresponds to the service label required by the terminal.

[0136] From the perspective of the NFV system, different triggers are bound to different resource template information, which allows FM to create function instances that can provide the service corresponding to the service tag of the trigger through the resource template information corresponding to the trigger.

[0137] For ease of understanding, let's take four triggers as an example. These four triggers correspond to four service tags, and also to four resource template information. For example... Figure 6 As shown in (a), Request 1 from Terminal 1 includes Service Tag 1, indicating a request to the NFV system to provide Service 1 corresponding to Service Tag 1 of the first application. After receiving Request 1, the 3GPP system forwards Request 1 to the corresponding Trigger 1 based on the Service Tag. Request 2 from Terminal 2 includes Service Tag 2, indicating a request to the NFV system to provide Service 2 corresponding to Service Tag 2 of the first application. After receiving Request 2, the 3GPP system forwards Request 2 to the corresponding Trigger 2 based on the Service Tag. Request 3 from Terminal 3 includes Service Tag 3, indicating a request to the NFV system to provide Service 3 corresponding to Service Tag 3 of the first application. After receiving Request 3, the 3GPP system forwards Request 3 to the corresponding Trigger 3 based on the Service Tag. Request 4 from Terminal 4 includes Service Tag 4, indicating a request to the NFV system to provide Service 4 corresponding to Service Tag 4 of the first application. After receiving Request 4, the 3GPP system forwards Request 4 to the corresponding Trigger 4 based on the Service Tag.

[0138] like Figure 6 As shown in (b), trigger 1 corresponds to resource template information 1, trigger 2 corresponds to resource template information 2, trigger 3 corresponds to resource template information 3, and trigger 4 corresponds to resource template information 4. Therefore, when trigger 1 is triggered, the NFV system creates a function instance based on resource template information 1 that provides service 1 corresponding to service tag 1 of trigger 1. When trigger 2 is triggered, a function instance based on resource template information 2 that provides service 2 corresponding to service tag 2 of trigger 2 is created. When trigger 3 is triggered, a function instance based on resource template information 3 that provides service 3 corresponding to service tag 3 of trigger 3 is created. When trigger 4 is triggered, a function instance based on resource template information 4 that provides service 4 corresponding to service tag 4 of trigger 4 is created.

[0139] In one possible implementation, after the IM module indicates to the FM module via third-party information the N triggers that correspond one-to-one with the N trigger descriptions, the FM module can retain the correspondence between the N resource templates and the N triggers. Specifically, the FM module determines the one-to-one correspondence between the N resource templates and the N triggers based on the one-to-one correspondence between the N resource templates and the N trigger descriptions, and retains the one-to-one correspondence between the N resource templates and the N triggers.

[0140] Thus, when the first trigger among the N triggers receives a service request from the service requester, it can send four pieces of information to the FM module. The fourth piece of information is used to request the creation of a function instance. Correspondingly, the FM module can obtain the first resource template information corresponding to the first trigger based on the correspondence between the N resource template information and the N triggers. Then, it instructs the first trigger to create a function instance based on the first resource template information that can provide the service corresponding to the service tag of the first trigger. For example, instructing the first trigger to create a function instance based on the first resource template information includes: instructing the first trigger to provide the IP address of the first function instance created based on the first resource template information.

[0141] Optionally, before indicating the first trigger to create a function instance based on the first resource template information, the FM module may request a first computing resource that satisfies the first resource template information; and then create a function instance in the first computing resource that can provide the service corresponding to the service tag corresponding to the first trigger.

[0142] Below, for ease of understanding, we will combine... Figure 7 This further explains the communication method proposed in this application. For example... Figure 7 As shown, the method includes:

[0143] S701, the NFVO module receives the sixth information from OSS / BSS. The sixth information is used to indicate the N service tags, N resource template information and N trigger description information of the first application. There is a one-to-one correspondence between the service tags, resource template information and trigger description information.

[0144] S702, the NFVO module sends the first information to the FM module. The first information is used to indicate the N resource template information of the first application and the N trigger description information corresponding one-to-one with the N resource template information.

[0145] S703, the FM module sends a second message to the IM module, which requests the IM module to create a trigger based on N trigger description information; correspondingly, the IM module creates a trigger based on the N trigger description information.

[0146] S704, the IM module sends third information to the FM module. The third information is used to indicate the N triggers that correspond one-to-one with the description information of the N triggers.

[0147] After the IM module indicates the N triggers that correspond one-to-one with the N trigger description information to the FM module, the FM module can determine the one-to-one correspondence between the N resource template information and the N triggers based on the one-to-one correspondence between the resource template information and the trigger description information, and the one-to-one correspondence between the N trigger description information and the N triggers.

[0148] For a detailed description of S701-S704, please refer to Figure 4 The descriptions in S401-S404 of the embodiments will not be repeated here.

[0149] The S705 FM module retains a one-to-one correspondence between N resource template information and N triggers.

[0150] S706, the FM module sends third information to the NFVO module; correspondingly, the NFVO module receives the third information.

[0151] After the FM module indicates the N triggers that correspond one-to-one with the N trigger description information to the NFVO module, the NFVO module can determine the one-to-one correspondence between the N service tags and the N triggers based on the one-to-one correspondence between the service tags, resource template information and trigger description information, and the one-to-one correspondence between the N trigger description information and the N triggers.

[0152] For a detailed description of S706, please refer to Figure 4 The description in S405 of the embodiment will not be repeated here.

[0153] In S707, the NFV module maintains a one-to-one correspondence between N service tags and N triggers.

[0154] S708, the NFVO module sends the seventh information to the service requester based on the sixth and third information. The seventh information is used to indicate the correspondence between N service tags and N triggers.

[0155] For a detailed description of S708, please refer to Figure 4 The description in S406 of the embodiment will not be repeated here.

[0156] After the seventh piece of information indicates the correspondence between N service tags and N triggers, such as Figure 7 As shown, the method also includes:

[0157] S709, the service requesting direction sends a request to the first trigger among the N triggers. The request is used to request the service corresponding to the first service label. The first trigger and the first service label have a corresponding relationship.

[0158] For example, based on the mapping between the N service tags and the IP addresses of the N triggers indicated by the seventh information, the service requester sends a request to the first trigger among the N triggers to request the service corresponding to the first service tag, the IP address of the first trigger and the first service tag.

[0159] For example, the service requester is the 3GPP system. In one scenario, after receiving request #1 from the terminal, the 3GPP system sends a request to the first trigger among N triggers. Request #1 carries a first service tag, indicating that a first application is requested to provide the service corresponding to the first service tag. Specifically, after receiving request #1, the 3GPP system, based on the correspondence between service tags and triggers, sends a request to the first trigger among the N triggers that corresponds to the first service tag, requesting the provision of the service corresponding to the first service tag.

[0160] S710: After the first trigger detects the request from the service requester, it requests FM to create a function instance.

[0161] In this application, the information sent by the first trigger to request the creation of a function instance of FM is also referred to as the fourth information.

[0162] After receiving the request from the first trigger, the S711 FM module will indicate the function instance created based on the first resource template information to the first trigger.

[0163] The first resource template information corresponds to the first trigger. The FM module can determine the first resource template information corresponding to the first trigger based on the saved correspondence between triggers and resource template information.

[0164] Specifically, after receiving the request from the first trigger, the FM module first checks whether there is a usable first computing resource in the system that has been created based on the first resource template information (or whether there is a usable first computing resource that can satisfy the first resource template information). If there is a usable one, it executes to instruct the first trigger to create a function instance based on the first resource template information. If there is no usable one, the FM module requests the first computing resource that satisfies the first resource template information from the IM module and creates a function instance in the first computing resource.

[0165] The FM module requests the first computing resources that satisfy the first resource template information from the IM module. Alternatively, the FM module requests the IM module to allocate the first computing resources based on the first resource template information.

[0166] For example, when the FM module instructs the first trigger to create a function instance based on the first resource template information, the FM module sends the address of the created function instance to the first trigger.

[0167] S712, after receiving the address of the function instance, the first trigger requests the function instance to process it.

[0168] S713, after the function instance completes the calculation, it forwards the calculation result to the first trigger.

[0169] S714, the first trigger sends the calculation result to the service requester.

[0170] For example, the service requester is a 3GPP system. Optionally, if the 3GPP system receives request #1 from the terminal, it sends the request to the first trigger out of N triggers. The 3GPP system then forwards the calculation result sent by the first trigger to the terminal.

[0171] The above, combined with Figure 7 This paper introduces an implementation method in which, after the IM module indicates to the FM module via third information that there are N triggers corresponding one-to-one with the description information of N triggers, the FM module retains the one-to-one correspondence between the N resource template information and the N triggers, and then the triggers create function instances for the FM module.

[0172] In another implementation, when the FM module indicates to the NFVO module via third information the N triggers that correspond one-to-one with the N trigger description information, the NFVO module retains not only the one-to-one correspondence between the N service tags and the N triggers, but also the correspondence between the N resource template information and the N triggers.

[0173] In this implementation, the second trigger among the N triggers can also send a fifth message to the NFVO module. This fifth message is used to request the creation of a function instance. Correspondingly, the NFVO module, based on the reserved correspondence between the N base resource templates and the N triggers, obtains the second resource template information corresponding to the second trigger from the N resource templates, and then instructs the FM module with this second resource template information. After receiving the second resource template information from the NFVO module, the FM module instructs the second trigger to create the function instance based on the second resource template information.

[0174] Specifically, after receiving the second resource template information indicated by the NFVO module, the FM module checks whether there is a second computing resource in the system that has been created based on the second resource template information. If there is one, it indicates to the first trigger the function instance created based on the second resource template information. If there is no one, the FM module requests a second computing resource that satisfies the second resource template information from the IM module and creates a function instance in the second computing resource.

[0175] Below, for ease of understanding, we will combine... Figure 8 This further explains the communication method proposed in this application. For example... Figure 8 As shown, the method includes:

[0176] S801, the NFVO module receives the sixth information from OSS / BSS. The sixth information is used to indicate the N service tags, N resource template information and N trigger description information of the first application. There is a one-to-one correspondence between the service tags, resource template information and trigger description information.

[0177] S802, the NFVO module sends the first information to the FM module. The first information is used to indicate the N resource template information of the first application and the N trigger description information corresponding one-to-one with the N resource template information.

[0178] S803, the FM module sends a second message to the IM module, which requests the IM module to create a trigger based on N trigger description information; correspondingly, the IM module creates a trigger based on the N trigger description information.

[0179] S804, the IM module sends third information to the FM module. The third information is used to indicate the N triggers that correspond one-to-one with the description information of the N triggers.

[0180] Optionally, the FM module can determine and retain the one-to-one correspondence between N resource template information and N triggers based on the one-to-one correspondence between resource template information and trigger description information, and the one-to-one correspondence between N trigger description information and N triggers.

[0181] S805, the FM module sends third information to the NFVO module; correspondingly, the NFVO module receives the third information.

[0182] For a detailed description of S801-S805, please refer to Figure 4 The descriptions in S401-S405 of the embodiments will not be repeated here.

[0183] In S806, the NFV module maintains a one-to-one correspondence between N service tags and N triggers, as well as a one-to-one correspondence between N triggers and N resource template information.

[0184] In other words, the NFV module maintains a one-to-one correspondence between N service tags, N triggers, and N resource template information.

[0185] S807, the NFVO module sends the seventh information to the service requester based on the sixth and third information. The seventh information is used to indicate the correspondence between N service tags and N triggers.

[0186] For a detailed description of S807, please refer to Figure 4 The description in S406 of the embodiment will not be repeated here.

[0187] After the seventh piece of information indicates the correspondence between N service tags and N triggers, such as Figure 8 As shown, the method also includes:

[0188] S808, the service requesting direction sends a request to the second trigger among the N triggers. This request is used to request the service corresponding to the second service tag. The second trigger and the second service tag have a corresponding relationship.

[0189] Specifically, based on the correspondence between the N service tags and the N triggers indicated by the seventh information, the service requester sends a request to the second trigger that corresponds to the second service tag among the N triggers, in order to request the service corresponding to the second service tag.

[0190] For example, based on the mapping between the N service tags and the IP addresses of the N triggers indicated by the seventh information, the service requester sends a request to the second trigger that corresponds to the second service tag among the N triggers.

[0191] In one scenario, the service requester is a 3GPP system. In one implementation, after receiving request #2 from the terminal, the 3GPP system sends a request to the second trigger among N triggers. Request #2 carries a second service tag, indicating that the requesting first application should provide the service corresponding to the second service tag. Specifically, after receiving request #2, the 3GPP system, based on the correspondence between service tags and triggers, sends a request to the second trigger among the N triggers that corresponds to the second service tag, requesting the provision of the service corresponding to the second service tag.

[0192] S809, after the first trigger detects the service requester's request, it requests the NFVO module to request the creation of a function instance.

[0193] S810, after receiving the request from the second trigger, the NFVO module indicates the second resource template information corresponding to the second trigger to the FM module.

[0194] Specifically, the NFVO module determines the second resource template information corresponding to the second trigger based on the correspondence between the saved trigger and resource template information.

[0195] S811, the FM module will indicate the function instance created based on the second resource template information to the second trigger.

[0196] For example, in one implementation, if the FM module retains a one-to-one correspondence between N resource template information and N triggers, the FM module can determine the second trigger corresponding to the second resource template information based on the one-to-one correspondence between the N resource template information and N triggers.

[0197] For example, in another implementation, the FM module can request the NFVO module to indicate a second trigger corresponding to the second resource template information, and then indicate to the second trigger a function instance created based on the second resource template information.

[0198] Specifically, after receiving the second resource template information from the NFVO module, the FM module first checks whether there is an available function instance in the system that has been created based on the second resource template information to provide the second service. If there is an available one, the FM module indicates the function instance to the second trigger. If there is no available one, the FM module requests a second computing resource that meets the second resource template information from the IM module, creates a function instance in the second computing resource, and indicates the function instance to the second trigger.

[0199] For example, when the FM module instructs the second trigger to create a function instance based on the second resource template information, the FM module sends the address of the created function instance to the second trigger.

[0200] S812, after receiving the address of the function instance, the second trigger requests the function instance to process it.

[0201] S813, after the function instance completes the calculation, it forwards the calculation result to the second trigger.

[0202] S814, the second trigger sends the calculation result to the service requester.

[0203] For example, the service requester is the 3GPP system. Optionally, after receiving request #2 from the terminal, the 3GPP system sends the request to the second trigger out of N triggers. The 3GPP system then forwards the calculation result sent by the second trigger to the terminal.

[0204] The above describes the communication method provided in this application. It should be noted that in this application, the FM module can also be replaced by the VNFM module in the NFV architecture. The meaning of the VNFM module can be found in the preceding description and will not be repeated here.

[0205] The following is combined Figures 9-10 This describes the communication device provided in this application.

[0206] Figure 9 This is a structural schematic diagram of a communication device provided in an embodiment of this application. Specifically, as shown... Figure 9 As shown, the communication device 900 includes: a transceiver unit 901 and a processing unit 902.

[0207] In one embodiment, the transceiver unit 901 is configured to: receive first information from the NFVO module, the first information indicating N resource template information of the first application and N trigger description information corresponding one-to-one with the N resource template information, wherein the N resource template information indicates different computing resources and corresponds to different service tags, and N is a positive integer greater than 1; the transceiver unit 901 is further configured to: send second information to the IM module, the second information requesting the IM module to create triggers based on the N trigger description information; the transceiver unit 901 is further configured to: receive third information from the IM module, the third information indicating N triggers corresponding one-to-one with the N trigger description information; the transceiver unit 901 is further configured to: send the third information to the NFVO module.

[0208] In one possible implementation, N triggers are used by the service requester to select the trigger corresponding to the desired service tag from the N triggers and request the service.

[0209] In one possible implementation, the processing unit 902 is used to: retain the correspondence between N resource template information and the N triggers based on the first information and the third information.

[0210] In one possible implementation, the transceiver unit 901 is further configured to: receive fourth information from the first trigger among the N triggers, the fourth information being used to request the creation of a function instance; the processing unit 902 is configured to: obtain the first resource template information corresponding to the first trigger based on the correspondence between the N resource template information and the N triggers; the transceiver unit 901 is further configured to: indicate to the first trigger the function instance created based on the first resource template information.

[0211] In one possible implementation, the transceiver unit 901 is used to: indicate to the first trigger the IP address of the first function instance created based on the first resource template information.

[0212] In one possible implementation, the transceiver unit 901 is further configured to: request a first computing resource that satisfies the first resource template information from the IM; and the processing unit 902 is configured to: create a function instance in the first computing resource.

[0213] In one possible implementation, the transceiver unit 901 is further configured to: receive second resource template information indicated by the NFVO module, the second resource template information corresponding to the second trigger among N triggers, the second trigger being used to send fifth information to the NFVO module for requesting the creation of a function instance; the transceiver unit 901 is further configured to: indicate to the second trigger the function instance created based on the second resource template information.

[0214] In one possible implementation, the first information is used to request the creation of triggers based on N trigger description information.

[0215] In another embodiment, the transceiver unit 901 is configured to: receive sixth information, which indicates N service tags, N resource template information, and N trigger description information of the first application, wherein there is a one-to-one correspondence between the service tags, resource template information, and trigger description information, and the N resource template information indicates different computing resources, where N is a positive integer greater than 1; the transceiver unit 901 is configured to: send first information to the FM module, which indicates N resource template information of the first application and N trigger description information corresponding one-to-one with the N resource template information, wherein the N trigger description information is used to create N triggers; the transceiver unit 901 is configured to: receive third information from the FM module, which indicates N triggers corresponding one-to-one with the N trigger description information; and the transceiver unit 901 is configured to: send seventh information based on the sixth information and the third information, which indicates the correspondence between the N service tags and the N triggers.

[0216] In one possible implementation, N triggers are used by the service requester to select the trigger corresponding to the desired service tag from the N triggers and request the service.

[0217] In one possible implementation, the transceiver unit 901 is also used to send the seventh information to the 3GPP system.

[0218] In one possible implementation, the processing unit 902 is used to: retain the correspondence between N resource template information and N triggers based on the third information.

[0219] In one possible implementation, the transceiver unit 901 is further configured to: receive fifth information from the second trigger among the N triggers, the fifth information being used to request the creation of a function instance; the processing unit 902 is further configured to: obtain the second resource template information corresponding to the second trigger from the N resource template information based on the correspondence between the N resource template information and the N triggers; the transceiver unit 901 is further configured to: indicate the second resource template information to the FM module.

[0220] In one possible implementation, the first information is used to request the creation of a trigger based on the N trigger description information.

[0221] Figure 10 This is a structural schematic diagram of another communication device provided in an embodiment of this application. Figure 10 The apparatus shown can be used to perform the methods described in the foregoing embodiments.

[0222] like Figure 10 As shown, the communication device 1000 of this embodiment includes a processor 1002. When a computer program or instruction is executed by the processor 1002, the processor 1002 performs the various steps of the communication method described above. In one implementation, the device 1000 further includes a communication interface 1003 and a bus 1004. The processor 1002 and the communication interface 1003 are connected to each other via the bus 1004.

[0223] In one implementation, the device 1000 further includes a memory 1001 for storing the computer program or instructions. The memory 1001 may be a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memories 1001 can be interconnected via a bus 1004.

[0224] The processor 1002 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, used to execute relevant programs to implement the various steps of the communication method described above.

[0225] The processor 1002 can also be an integrated circuit chip with signal processing capabilities. In implementation, each step of the method provided in this application embodiment can be accomplished through integrated logic circuits in the hardware of the processor 1002 or through software instructions.

[0226] The processor 1002 described above can also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or a conventional processor, etc.

[0227] The steps of the method disclosed in the embodiments of this application can be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory 1001. The processor 1002 reads the information in memory 1001 and, in conjunction with its hardware, completes the functions required by the units included in the device of this application. For example, it can execute the various steps / functions of the communication method described above.

[0228] The communication interface 1003 can use, but is not limited to, transceivers to enable communication between the device 1000 and other devices or communication networks.

[0229] Bus 1004 may include a pathway for transmitting information between various components of device 1000 (e.g., memory 1001, processor 1002, communication interface 1003).

[0230] The above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be a usable medium accessible to a computer or a data storage device such as a server or data center containing one or more sets of usable media. The usable medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0231] This application also provides a computer program product, which includes a computer program or instructions (also referred to as code) that, when executed, can implement the methods described in the embodiments shown above.

[0232] This application also provides a computer-readable storage medium storing a computer program or instructions (also referred to as code). When the computer program or instructions are executed, the methods described in the embodiments shown above can be implemented.

[0233] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. A and B can be singular or plural. Additionally, the character " / " in this article generally indicates an "or" relationship between the preceding and following related objects, but it can also represent an "and / or" relationship. Please refer to the context for a more accurate understanding.

[0234] In this application, "at least one" means one or more, and "more than one" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0235] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not limit the implementation process of the embodiments of this application.

[0236] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0237] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

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

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

[0240] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0241] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory, random access memory, magnetic disks, or optical disks.

Claims

1. A communication method characterized by comprising: The application is applied to a function management (FM) module, comprising: receiving first information from a network function virtualization orchestrator (NFVO) module, the first information being used to indicate N resource template information of a first application and N trigger description information corresponding to the N resource template information, the N resource template information indicating different computing resources and corresponding to different service labels respectively, N being a positive integer greater than 1; the trigger description information being used to create a trigger of a target application; the trigger of the target application being used to, when the trigger detects a request for requesting the target application to provide a service, send a request for requesting to create a function instance of the target application, so as to trigger the function instance of the target application; the resource template information being used to indicate computing resources required when the function instance of the target application is created; sending second information to an infrastructure management (IM) module, the second information being used to request the IM module to create triggers based on the N trigger description information; receiving third information from the IM module, the third information being used to indicate N triggers corresponding to the N trigger description information; sending the third information to the NFVO module.

2. The method of claim 1, wherein, The N triggers are used for a service requester to select a trigger corresponding to a required service label from the N triggers and request a service.

3. The method according to claim 1 or 2, characterized in that, The method further comprises: based on the first information and the third information, maintaining a correspondence between the N resource template information and the N triggers.

4. The method of claim 3, wherein, The method further comprises: receiving fourth information from a first trigger in the N triggers, the fourth information being used to request to create a function instance; based on the correspondence between the N resource template information and the N triggers, obtaining first resource template information corresponding to the first trigger; indicating, to the first trigger, a function instance created based on the first resource template information.

5. The method of claim 4, wherein, The indication of the function instance created based on the first resource template information to the first trigger comprises: indicating, to the first trigger, an internet protocol (IP) address of a first function instance created based on the first resource template information.

6. The method according to claim 4 or 5, characterized in that, Before the indication of the function instance created based on the first resource template information to the first trigger, the method further comprises: requesting, from the IM, first computing resources satisfying the first resource template information; creating the function instance in the first computing resources.

7. The method according to claim 1 or 2, characterized in that, The method further comprises: receiving second resource template information indicated by the NFVO module, the second resource template information corresponding to a second trigger in the N triggers, the second trigger being used to send fifth information for requesting to create a function instance to the NFVO module; indicating, to the second trigger, a function instance created based on the second resource template information.

8. The method of any one of claims 1-2, 4-5, wherein, The first information is used to request to create triggers based on the N trigger description information.

9. A communication method characterized by comprising: The application is applied to a network function virtualization orchestrator (NFVO) module, comprising: receive sixth information, the sixth information being used to indicate N service labels of a first application, N resource template information and N trigger description information, the service labels, the resource template information and the trigger description information having a one-to-one correspondence relationship, the N resource template information indicating different computing resources, N being a positive integer greater than 1; the N resource template information indicating different computing resources and respectively corresponding to different service labels; the trigger description information being used to create a trigger of a target application; the trigger of the target application being used to, when the trigger detects a request for requesting the target application to provide a service, send a request for requesting to create a function instance of the target application, so as to trigger the function instance of the target application; the resource template information being used to indicate computing resources required when the function instance of the target application is created; send first information to a function management FM module, the first information being used to indicate the N resource template information of the first application and the N trigger description information corresponding to the N resource template information in a one-to-one manner, the N trigger description information being used to create N triggers; receive third information from the FM module, the third information being used to indicate the N triggers corresponding to the N trigger description information in a one-to-one manner; send seventh information according to the sixth information and the third information, the seventh information being used to indicate a correspondence relationship between the N service labels and the N triggers.

10. The method of claim 9, wherein, The N triggers are used for a service requester to select a trigger corresponding to a required service label from the N triggers and request a service.

11. The method according to claim 9 or 10, characterized in that, The sending of the seventh information comprises: sending the seventh information to a third generation partnership project 3GPP system.

12. The method of claim 9 or 10, wherein, The method further comprises: based on the third information, reserving the correspondence relationship between the N resource template information and the N triggers.

13. The method of claim 12, wherein, The method further comprises: receive fifth information from a second trigger in the N triggers, the fifth information being used to request to create a function instance; based on the correspondence relationship between the N resource template information and the N triggers, obtain second resource template information corresponding to the second trigger in the N resource template information; indicate the second resource template information to the FM module.

14. The method according to any one of claims 9-10, 13, characterized by, The first information is used to request to create a trigger based on the N trigger description information.

15. A method of communication, comprising: The method is applied to a first device, the first device comprising a network function virtualization orchestrator NFVO module, a function management FM module and an infrastructure management IM module, and the method comprises: The NFVO module receives sixth information, the sixth information being used to indicate N service labels of the first application, N resource template information, and N trigger description information, the service labels, the resource template information, and the trigger description information having a one-to-one correspondence relationship, the N resource template information indicating different computing resources, N being a positive integer greater than 1; the N resource template information indicating different computing resources and respectively corresponding to different service labels; the trigger description information being used to create a trigger of a target application; the trigger of the target application being configured to, when the trigger detects a request for requesting the target application to provide a service, send a request for requesting to create a function instance of the target application, so as to trigger the function instance of the target application; the resource template information indicating computing resources required when the function instance of the target application is created; The NFVO module sends first information to the FM module, the first information being used to indicate the N resource template information of the first application and the N trigger description information corresponding to the N resource template information, the N trigger description information being used to create N triggers; The IM module sends third information to the FM module, the third information being used to indicate the N triggers corresponding to the N trigger description information; The NFVO module sends seventh information, the seventh information being used to indicate a correspondence relationship between the N service labels and the N triggers; In response to eighth information sent by a third trigger, third resource template information corresponding to the third trigger is determined according to the correspondence relationship between the N triggers and the N resource template information, the eighth information being used to request to create a function instance; A function instance created based on the third resource template information is indicated to the third trigger.

16. The method of claim 15, wherein, The N triggers are used for a service requester to select a trigger corresponding to a required service label from the N triggers and request a service.

17. The method according to claim 15 or 16, characterized in that The NFVO module receives sixth information, including: The NFVO module receives the sixth information from an operation support system and a business support system (OSS / BSS).

18. The method of claim 15 or 16, wherein, The seventh information is sent, including: The seventh information is sent to a third generation partnership project (3GPP) system.

19. A communications device, characterized by The module for implementing the method in any one of claims 1 to 8; or, the module for implementing the method in any one of claims 9 to 14; or, the module for implementing the method in any one of claims 15 to 18.

20. A communications device, characterized by The processor is used to enable the communication device to implement the method in any one of claims 1 to 8, or to enable the communication device to implement the method in any one of claims 9 to 14; or to enable the communication device to implement the method in any one of claims 15 to 18, by executing a computer program or instructions, and / or by a logic circuit.

21. The apparatus of claim 20, wherein, The memory is further included for storing the computer program, and / or a configuration file of the logic circuit.

22. The apparatus of claim 20 or 21, wherein, The communication interface is further included for inputting and / or outputting signals.

23. A computer-readable storage medium having stored thereon a computer program, characterized in that, The computer program, which when executed by a processor, causes the method of any one of claims 1 to 8 to be performed, or the method of any one of claims 9 to 14 to be performed, or the method of any one of claims 15 to 18 to be performed.

24. A computer program product, characterised in that, A computer program product comprising a computer program which, when executed by a processor, causes the method of any one of claims 1 to 8 to be performed, or the method of any one of claims 9 to 14 to be performed, or the method of any one of claims 15 to 18 to be performed.

Images