WO2021129520A1 - 网络业务的生命周期管理的授权方法及装置 - Google Patents

网络业务的生命周期管理的授权方法及装置 Download PDF

Info

Publication number
WO2021129520A1
WO2021129520A1 PCT/CN2020/137364 CN2020137364W WO2021129520A1 WO 2021129520 A1 WO2021129520 A1 WO 2021129520A1 CN 2020137364 W CN2020137364 W CN 2020137364W WO 2021129520 A1 WO2021129520 A1 WO 2021129520A1
Authority
WO
WIPO (PCT)
Prior art keywords
nfvo device
nfvo
data
authorization
perform
Prior art date
Application number
PCT/CN2020/137364
Other languages
English (en)
French (fr)
Inventor
李世涛
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2021129520A1 publication Critical patent/WO2021129520A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication
    • H04L41/342—Signalling channels for network management communication between virtual entities, e.g. orchestrators, SDN or NFV entities

Definitions

  • This application relates to the field of network function virtualization, and in particular to an authorization method and device for network service life cycle management.
  • Network function virtualization technology is the use of virtualization technology to virtualize the functions of special equipment in traditional networks into independent applications, which can be flexibly deployed on standard-based computing hardware, storage hardware, network hardware and other equipment Built on a unified infrastructure platform.
  • the NFV orchestrator NFVO
  • LCM lifecycle management
  • NS virtualized network service
  • NFV infrastructure NFV infrastructure layer
  • the NS managed by the global NFVO may include at least one nested NS (nested NS), the nested NS may be managed by a local NFVO, and the global NFVO and the local NFVO may communicate.
  • the local NFVO performs life cycle management on the nested NS
  • the local NFVO can send an authorization request to the global NFVO, and perform corresponding operations after receiving the authorization response.
  • the global NFVO recognizes whether the operation of the local NFVO on the nested NS has an impact on the NS managed by the global NFVO, and whether to authorize the operation of the local NFVO on the nested NS, there is currently no corresponding solution.
  • This application provides an authorization method and device for network service life cycle management, which solves the problem of how the global NFVO determines whether to authorize the local NFVO to operate the nested NS.
  • an authorization method for life cycle management of network services is provided, and the method can be applied to the first NFVO device.
  • the method includes: a first NFVO device receives an authorization request from a second NFVO device, the authorization request is used to request authorization to perform a first operation on the second NS, and the first operation is that the second NFVO device performs life cycle management on the second NS Operation. If the first NFVO device determines that the resources of the first NS satisfy the first operation on the second NS, it sends an authorization response to the second NFVO device to authorize the first operation on the second NS.
  • the first NFVO device determines that the resources of the first NS satisfy the life cycle management of the second NS, the first NFVO device authorizes the life cycle of the second NS. Cycle management. Therefore, the problem of management negotiation between NFVO devices when the nested NS is managed in the life cycle is solved, and the impact on the NS managed by the global NFVO is reduced.
  • the first NFVO device determines that the resources of the first NS are not sufficient to perform the first operation on the second NS, it sends a failure response to the second NFVO device, and the failure response is used to indicate that the first operation on the second NS is not allowed . Therefore, the impact on the first NS caused by the life cycle management of the second NS is avoided when the resources of the first NS are not sufficient to perform the first operation on the second NS.
  • the first operation is an expansion operation.
  • the first NFVO device determines whether the resources of the first NS are sufficient to perform the first operation on the second NS, including: the first NFVO device obtains the first data and the second NS. Data, determine whether the first data is greater than the second data; if the first data is greater than the second data, the first NFVO device determines that the resources of the first NS are sufficient to perform the first operation on the second NS; if the first data is less than or equal to the second data According to the data, the first NFVO device determines that the resources of the first NS are not sufficient to perform the first operation on the second NS.
  • the first data is the data flow related to the second NS in the first NS
  • the second data is the predicted data flow after the first operation is performed on the second NS. Since the second NS is nested within the first NS, the second NS has an association relationship with the first NS.
  • the data traffic related to the second NS in the first NS is used to determine whether the first NS supports the expansion of the second NS, so as to facilitate the expansion operation of the second NS. Therefore, the problem of management negotiation between NFVO devices when the nested NS is managed in the life cycle is solved, and the impact on the NS managed by the global NFVO is reduced.
  • the second data may be passively received by the first NFVO device.
  • the authorization request includes the second data.
  • the second data may be actively acquired by the first NFVO device.
  • the authorization request includes a first address
  • the first address is used to indicate the address where the second data is stored
  • the first NFVO device acquires the second data, including: the first NFVO device sends the first acquisition request to the second NFVO device, and the The first address included in an acquisition request receives the second data from the second NFVO device.
  • the first acquisition request is used to request the second NFVO device to feed back the second data.
  • the method further includes: the first NFVO device performs a first operation on the virtual connection connected to the second NS in the first NS.
  • the first NFVO device performs a first operation on the virtual connection connected to the second NS in the first NS.
  • the method further includes: the first NFVO device sends a first authorization policy to the second NFVO device, where the first authorization policy is used to instruct to collect data traffic of the second NS. Therefore, the second NFVO device is made to report the relevant information about the expansion operation of the second NS, so that the first NFVO device can determine whether the resources of the first NS satisfy the expansion operation of the second NS according to the related information, and whether the second NS can be authorized to perform the expansion operation.
  • NS performs expansion operations.
  • the first operation is a delete operation
  • the first NFVO device judges whether the resources of the first NS are sufficient to perform the first operation on the second NS, including: the first NFVO device judges the first NS and the second NS Whether the second NS has a dependency relationship; if the first NS has no dependency relationship with the second NS, the first NFVO device determines that the resources of the first NS satisfy the first operation on the second NS. Since the second NS is nested within the first NS, the second NS has an association relationship with the first NS. The dependency between the first NS and the second NS is used to determine whether the first NS supports the deletion of the second NS, so as to facilitate the deletion operation on the second NS. Therefore, the problem of management negotiation between NFVO devices when the nested NS is managed in the life cycle is solved, and the impact on the NS managed by the global NFVO is reduced.
  • the method further includes: if the first NS has a dependency relationship with the second NS, the first NFVO device determines that the resources of the first NS are not sufficient to perform the first operation on the second NS.
  • the method further includes: the first NFVO device determines whether the third NS is successfully deployed within the first time period, and the third NS is used to provide the second NS.
  • the first duration is the predicted duration of the service provided by the second NS. If the third NS is successfully deployed within the first time period, the first NFVO device sends an authorization response to the second NFVO device. If the deployment of the third NS fails within the first time period, the first NFVO device sends a failure response to the second NFVO device. Therefore, by deploying the third NS, the third NS replaces the second NS and continues to provide the services of the second NS, avoiding the effect of deleting the second NS on the first NS.
  • the first duration may be passively received by the first NFVO device.
  • the authorization request includes the first duration.
  • the first duration may be actively acquired by the first NFVO device.
  • the authorization request includes a second address
  • the second address is used to indicate the address for storing the first duration.
  • the method further includes: the first NFVO device sends a second acquisition request to the second NFVO device, and receives the first request from the second NFVO device. duration.
  • the second acquisition request is used to request the second NFVO device to feed back the first duration, and the second acquisition request includes the second address.
  • the method further includes: the first NFVO device sends a second authorization policy to the second NFVO device, and the second authorization policy is used to instruct the second NFVO device to predict the first duration. Therefore, the second NFVO device is caused to report related information about the deletion operation on the second NS, so that the first NFVO device can determine whether the second NS can be deleted according to the related information, and whether the deletion operation on the second NS can be authorized.
  • an authorization method for life cycle management of network services is provided, and the method can be applied to a second NFVO device.
  • the method includes: the second NFVO device sends an authorization request to the first NFVO device, the authorization request is used to request authorization to perform a first operation on the second NS, and the first operation is for the second NFVO device to perform life cycle management on the second NS. Operation: After receiving the authorization response from the first NFVO device, the second NFVO device performs the first operation on the second NS. The authorization response is used to indicate to perform the first operation on the second NS.
  • the first NFVO device determines that the resources of the first NS meet the requirements for life cycle management of the second NS Then, the first NFVO device is authorized to perform life cycle management on the second NS, and the second NFVO device performs the first operation on the second NS. Therefore, the problem of management negotiation between NFVO devices when the nested NS is managed in the life cycle is solved, and the impact on the NS managed by the global NFVO is reduced.
  • the method further includes: the second NFVO device receives a failure response from the first NFVO device, where the failure response is used to indicate that the second NFVO device is not allowed to perform the first operation on the second NS. Therefore, the impact on the first NS caused by the life cycle management of the second NS is avoided when the resources of the first NS are not sufficient to perform the first operation on the second NS.
  • the first operation is an expansion operation.
  • the method further includes: the second NFVO device collects the data traffic of the second NS, and according to the second NFVO device The data flow of the NS determines the second data, and the second data is the predicted data flow after the first operation is performed on the second NS.
  • the authorization request includes the second data.
  • the authorization request includes a first address
  • the first address is used to indicate an address for storing the second data.
  • the method further includes: the second NFVO device receives the first acquisition request from the first NFVO device, and sends The second data sent by the first NFVO device.
  • the first acquisition request is used to request the second NFVO device to feed back the second data, and the first acquisition request includes the first address.
  • the method further includes: the second NFVO device receives a first authorization policy from the first NFVO device, where the first authorization policy is used to instruct the second NFVO device to collect data traffic of the second NS. Therefore, the second NFVO device is made to report the relevant information about the expansion operation of the second NS, so that the first NFVO device can determine whether the resources of the first NS satisfy the expansion operation of the second NS according to the related information, and whether the second NS can be authorized to perform the expansion operation.
  • NS performs expansion operations.
  • the first operation is a delete operation.
  • the method further includes: the second NFVO device determines the first duration, and the first duration is the second duration. The predicted duration of the service provided by NS.
  • the authorization request includes the first duration.
  • the authorization request includes a second address
  • the second address is used to indicate the address for storing the first duration
  • the method further includes: the second NFVO device receives the second acquisition request from the first NFVO device, and The first duration and the second acquisition request sent to the first NFVO device are used to request the second NFVO device to feed back the first duration, and the second acquisition request includes the second address.
  • the method further includes: the second NFVO device receives a second authorization policy from the first NFVO device, and the second authorization policy is used to instruct the second NFVO device to predict the first duration. Therefore, the second NFVO device is caused to report related information about the deletion operation on the second NS, so that the first NFVO device can determine whether the second NS can be deleted according to the related information, and whether the deletion operation on the second NS can be authorized.
  • a communication device for implementing the method described in the first aspect.
  • the communication device may be the first NFVO device.
  • the device includes: a transceiver unit and a processing unit.
  • the transceiver unit is used to receive an authorization request from the second NFVO device, the authorization request is used to request authorization to perform a first operation on the second NS, and the first operation is an operation for the second NFVO device to perform life cycle management on the second NS. If the processing unit determines that the resources of the first NS satisfy the first operation on the second NS, the transceiver unit is further configured to send an authorization response to the second NFVO device to authorize the first operation on the second NS.
  • the transceiving unit is further configured to send a failure response to the second NFVO device, and the failure response is used to indicate that it is not allowed to perform the first operation on the second NS.
  • the second NS performs the first operation. Therefore, the impact of the life cycle management operation of the second NFVO device on the second NS on the first NS is avoided.
  • the first operation is an expansion operation
  • the processing unit is used to obtain the first data and the second data, and determine whether the first data is greater than the second data; if the first data is greater than the second data
  • the processing unit is used to determine that the resources of the first NS satisfy the first operation on the second NS; if the first data is less than or equal to the second data, the processing unit is used to determine that the resources of the first NS do not satisfy the
  • the second NS performs the first operation.
  • the first data is the data flow related to the second NS in the first NS
  • the second data is the predicted data flow after the first operation is performed on the second NS.
  • the authorization request includes the second data.
  • the authorization request includes a first address
  • the first address is used to indicate the address for storing the second data
  • the transceiver unit is also used to send the first acquisition request to the second NFVO device and receive the The second data of the second NFVO device.
  • the first acquisition request is used to request the second NFVO device to feed back the second data, and the first acquisition request includes the first address.
  • the processing unit is further configured to perform a first operation on the virtual connection connected to the second NS in the first NS.
  • the transceiver unit is further configured to send a first authorization policy to the second NFVO device, and the first authorization policy is used to instruct to collect data traffic of the second NS.
  • the first operation is a delete operation
  • the processing unit is used to determine whether the first NS has a dependency relationship with the second NS, and if the first NS does not have a dependency relationship with the second NS, determine the first NS and the second NS.
  • the resources of one NS satisfy the first operation on the second NS.
  • the processing unit is configured to determine that the resources of the first NS are not sufficient to perform the first operation on the second NS.
  • the processing unit is also used to determine whether the third NS is successfully deployed within the first time period, and the third NS is used to provide the second NS.
  • NS service the first duration is the predicted duration of the service provided by the second NS; if the third NS is successfully deployed within the first duration, the transceiver unit is used to send an authorization response to the second NFVO device; if within the first duration Deploying the third NS fails, and the transceiver unit is used to send a failure response to the second NFVO device.
  • the authorization request includes the first duration.
  • the authorization request includes a second address
  • the second address is used to indicate an address for storing the first duration
  • the transceiver unit is also used to send a second acquisition request to the second NFVO device, and receive the second address from the second NFVO device.
  • the second acquisition request is used to request the second NFVO device to feed back the first duration, and the second acquisition request includes the second address; the first NFVO device.
  • the transceiver unit is further configured to send a second authorization policy to the second NFVO device, and the second authorization policy is used to instruct the second NFVO device to predict the first duration.
  • a communication device for implementing the method described in the second aspect.
  • the communication device may be a second NFVO device.
  • the device includes: a transceiver unit and a processing unit.
  • the transceiving unit is used to send an authorization request to the first NFVO device, the authorization request is used to request authorization to perform a first operation on the second NS, and the first operation is an operation for the second NFVO device to perform life cycle management on the second NS;
  • the transceiver unit is also used to receive an authorization response from the first NFVO device, and the processing unit is used to perform a first operation on the second NS.
  • the authorization response is used to indicate to perform the first operation on the second NS.
  • the transceiving unit is further configured to receive a failure response from the first NFVO device, where the failure response is used to indicate that the second NFVO device is not allowed to perform the first operation on the second NS.
  • the first operation is an expansion operation
  • the processing unit is further configured to collect the data flow of the second NS, and determine the second data according to the data flow of the second NS, and the second data is the data flow of the second NS.
  • the authorization request includes the second data.
  • the authorization request includes a first address
  • the first address is used to indicate the address for storing the second data
  • the transceiver unit is also used to receive the first acquisition request from the first NFVO device, and send the request to the first NFVO device.
  • the second data sent by an NFVO device.
  • the first acquisition request is used to request the second NFVO device to feed back the second data, and the first acquisition request includes the first address.
  • the transceiver unit is further configured to receive a first authorization policy from the first NFVO device, and the first authorization policy is used to instruct the second NFVO device to collect data traffic of the second NS.
  • the first operation is a deletion operation
  • the processing unit is further configured to determine a first duration, and the first duration is a predicted duration for the second NS to provide services.
  • the authorization request includes the first duration.
  • the authorization request includes a second address
  • the second address is used to indicate the address for storing the first duration
  • the transceiver unit is also used to receive the second acquisition request from the first NFVO device, and send The first duration sent by the first NFVO device.
  • the second acquisition request is used to request the second NFVO device to feed back the first duration, and the second acquisition request includes the second address.
  • the transceiving unit is further configured to receive a second authorization policy from the first NFVO device, and the second authorization policy is used to instruct the second NFVO device to predict the first duration.
  • the above-mentioned functional modules of the third aspect and the fourth aspect can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the transceiver is used to complete the functions of the receiving unit and the transmitting unit
  • the processor is used to complete the function of the processing unit
  • the memory is used for the processor to process the program instructions of the method of the present application.
  • the processor, transceiver, and memory are connected through the bus and communicate with each other. Specifically, reference may be made to the function of the behavior of the NFVO device in the method described in the first aspect to the method described in the second aspect.
  • the present application also provides a communication device for implementing the method described in the first aspect.
  • the communication device includes a chip system.
  • the communication device includes a processor, configured to implement the functions in the method described in the first aspect.
  • the communication device may also include a memory for storing program instructions and data.
  • the memory is coupled with the processor, and the processor can call and execute program instructions stored in the memory to implement the functions in the method described in the first aspect.
  • the communication device may further include a communication interface, and the communication interface is used for the communication device to communicate with other devices.
  • the communication device is a first NFVO device, and the other device is a second NFVO device.
  • the communication interface may be a transceiver.
  • the transceiver is used to receive authorization requests and send authorization responses.
  • the processor is used to determine whether the resources of the first NS satisfy the first operation on the second NS.
  • the present application also provides a communication device for implementing the method described in the second aspect.
  • the communication device includes a chip system.
  • the communication device includes a processor, configured to implement the functions in the method described in the second aspect.
  • the communication device may also include a memory for storing program instructions and data.
  • the memory is coupled with the processor, and the processor can call and execute the program instructions stored in the memory to implement the functions in the method described in the second aspect.
  • the communication device may further include a communication interface, and the communication interface is used for the communication device to communicate with other devices. Exemplarily, if the communication device is the second NFVO device, the other device is the first NFVO device.
  • the communication interface may be a transceiver.
  • the transceiver is used to send authorization requests and receive authorization responses.
  • the processor is configured to perform the first operation on the second NS.
  • the present application also provides a computer-readable storage medium, including: computer software instructions; when the computer software instructions run in a communication device, the communication device executes the method described in the first or second aspect above .
  • this application also provides a computer program product containing instructions, which when the computer program product runs in a communication device, causes the communication device to execute the method described in the first or second aspect above.
  • the present application provides a chip system that includes a processor and may also include a memory for implementing the function of the NVFO device in the above method.
  • the chip system can be composed of chips, or it can include chips and other discrete devices.
  • the present application also provides a communication system.
  • the communication system includes the first NFVO device described in the third aspect and the second NFVO device described in the fourth aspect; or the communication system includes the communication system described in the fifth aspect.
  • FIG. 1 is an example diagram of an NFV system architecture provided by an embodiment of the application
  • FIG. 2A is a schematic structural diagram of a VNFD provided by an embodiment of this application.
  • FIG. 2B is a schematic diagram of the structure of the VNF obtained after the deployment of the above-mentioned VNFD;
  • Fig. 2C is a schematic diagram of the structure of NS_1 including several VNFs
  • FIG. 3 is a flowchart of an authorization method for network service life cycle management provided by an embodiment of the application
  • FIG. 5 is a flowchart of an authorization method for network service life cycle management provided by an embodiment of the application
  • FIG. 6 is a flowchart of an authorization method for network service life cycle management provided by an embodiment of the application.
  • FIG. 7 is a flowchart of an authorization method for network service life cycle management provided by an embodiment of the application.
  • FIG. 8 is a flowchart of an authorization method for network service life cycle management provided by an embodiment of the application.
  • FIG. 9 is a flowchart of an authorization method for network service life cycle management provided by an embodiment of the application.
  • FIG. 10 is a flowchart of an authorization method for network service life cycle management provided by an embodiment of the application.
  • FIG. 11 is a schematic diagram of the composition of a communication device provided by this application.
  • FIG. 12 is a schematic diagram of the composition of another communication device provided by this application.
  • words such as “exemplary” or “for example” are used as examples, illustrations, or illustrations. Any embodiment or design solution described as “exemplary” or “for example” in the embodiments of the present application should not be construed as being more preferable or advantageous than other embodiments or design solutions. To be precise, words such as “exemplary” or “for example” are used to present related concepts in a specific manner.
  • the traditional telecommunications system is composed of various dedicated hardware devices, and different hardware devices are used for different functions.
  • the telecommunication system With the growth of the network scale, the telecommunication system becomes more and more complex, which brings many challenges. For example, the development and launch of new services, system operation and maintenance, and resource utilization.
  • IT Internet
  • 13 major telecom operators around the world jointly released the NFV white paper and announced that they are in the European Telecommunications Standards Institute.
  • ETSI established the NFV industry specific group (ISG) to formulate the requirements and technical framework of NFV, and promote the development of NFV.
  • NFV technology uses virtualization technology to pool and virtualize the resources of infrastructure hardware devices (such as computing devices, storage devices, and network devices), provide virtual resources for upper-layer applications, and realize software and hardware decoupling.
  • infrastructure hardware devices such as computing devices, storage devices, and network devices
  • VNF virtualization technology
  • NFV technology uses cloud computing technology to achieve elastic scaling of applications and match virtual resources with business loads. This not only improves the utilization efficiency of virtual resources, but also improves the response rate of the NFV system.
  • FIG. 1 is an example diagram of an NFV system architecture provided by an embodiment of the application.
  • the NFV system can be used in various networks, such as a data center network, operator network or local area network.
  • NFV system includes a NFV management and orchestration system (NFV management and orchestration, NFV MANO) 101, NFV infrastructure layer (NFV infrastructure, NFVI) 102, multiple virtual network functions (Virtual Network Function, VNF) 103, multiple network elements Management (element management, EM) 104 and operation-support system/business support system (OSS/BSS) 105.
  • NFV management and orchestration NFV management and orchestration
  • NFV MANO NFV management and orchestration
  • NFV infrastructure layer NFV infrastructure layer
  • VNF Virtual Network Function
  • EM multiple network elements Management
  • OSS/BSS operation-support system/business support system
  • NFV MANO 101 is used to monitor and manage NFVI 102 and VNF 103.
  • the NFV management and orchestration system 101 includes an NFV orchestrator (NFVO) 1011, one or more VNF managers (VNFM) 1012, and a virtualized infrastructure manager (VIM) 1013.
  • NFVO NFV orchestrator
  • VNFM VNF managers
  • VIP virtualized infrastructure manager
  • NFVO 1011 is mainly responsible for the life cycle management of virtualized NS, virtual infrastructure and the allocation and scheduling of virtual resources in NFVI. NFVO 1011 can also execute resource-related requests from one or more VNFMs 1012 (e.g. request to obtain VNFD), send configuration information (e.g. VNFD, VNF information modification request and VNF instantiation request) to VNFM 1012, and collect VNF 103 Status information.
  • VNFD can be stored on NFVO or in a database managed by NFVO, so that NFVO can obtain VNFD and feed back VNFD to VNFM, and VNFM deploys VNF according to VNFD.
  • NFVO can store VNFDs corresponding to VNFs with multiple functions.
  • NFVO 1011 can communicate with VIM 1013 to realize resource allocation and/or reservation and exchange configuration and status information of virtualized hardware resources.
  • VNFM 1012 is mainly responsible for the life cycle management of one or more VNF 103. For example, instantiating (instantiating), updating (updating), query, elastic scaling (scaling), terminating (terminating) VNF 103 and so on.
  • the VNFM 1012 can communicate with the VNF 103 to complete the life cycle management of the VNF 103 and exchange configuration and status information.
  • the VIM 1013 can perform resource management functions, such as managing the allocation of infrastructure resources (for example, adding resources to virtual containers) and operating functions (for example, collecting NFVI fault information).
  • VNFM 1012 and VIM 1013 can communicate with each other for resource allocation and exchange configuration and status information of virtualized hardware resources. For example, it controls and manages the interaction of VNF 103 with computing hardware 1021, storage hardware 1022, network hardware 1023, virtual computing 1024, virtual storage 1025, and virtual network 1026.
  • NFVI 102 includes a hardware resource layer, a virtualization layer (virtualization layer), and a virtual resource layer.
  • NFVI 102 includes hardware resources, software resources, or a combination of the two to complete the deployment of a virtualized environment.
  • the hardware resources and the virtualization layer are used to provide virtualized resources, for example, as virtual machines and other forms of virtual containers for VNF 103.
  • the hardware resource layer includes computing hardware 1021, storage hardware 1022, and network hardware 1023.
  • the computing hardware 1021 may be off-the-shelf hardware on the market and/or user-customized hardware to provide processing and computing resources.
  • the storage hardware 1022 may be the storage capacity provided in the network or the storage capacity resident in the storage hardware 1022 itself (local storage in the server).
  • the resources of the computing hardware 1021 and the storage hardware 1022 may be centralized.
  • the network hardware 1023 may be a switch, a router, and/or any other network device configured to have a switching function.
  • the network hardware 1023 may span multiple domains, and may include multiple networks interconnected by one or more transmission networks.
  • the virtualization layer in NFVI 102 can abstract hardware resources from the physical layer and decouple the VNF 103 to provide virtual resources to the VNF 103.
  • the virtual resource layer includes virtual computing 1024, virtual storage 1025, and virtual network 1026.
  • the virtual computing 1024 and the virtual storage 1025 may be provided to the VNF 103 in the form of a virtual machine and/or other virtual containers.
  • one or more VNF 103 may be deployed on a virtual machine (virtual machine, VM).
  • the virtualization layer abstracts the network hardware 1023 to form a virtual network 1026.
  • the virtual network 1026 may include a virtual switch, and the virtual switch is used to provide connections between virtual machines and other virtual machines.
  • the transmission network in the network hardware 1023 can be virtualized using a centralized control plane and a separate forwarding plane (such as a software-defined network).
  • computing hardware 1021, storage hardware 1022, and network hardware 1023 may include multiple machine frames, or multiple racks, or even multiple computer rooms.
  • VNF 103 is an example of a virtualized network function.
  • the equipment management system (EM) 104 is a system used to configure and manage equipment in traditional networks. In the NFV system, EM 104 can also be used to configure and manage the VNF 103 and initiate a new VNF 103 to the VNFM 1012. Lifecycle management operations such as the instantiation of.
  • Operation Support System (Operations Support System and Business Support System, OSS/BSS) 105 supports various end-to-end telecommunication services.
  • the management functions supported by OSS include: network configuration, service provision, fault management, etc.
  • BSS handles orders, payments, income, etc., and supports product management, order management, revenue management and customer management.
  • the virtualized NS can be an IP multimedia subsystem (IMS) network service, or a next-generation mobile core network (Evolved Packet Core, EPC) network service, etc.
  • IMS IP multimedia subsystem
  • EPC Evolved Packet Core
  • One NS can contain several VNFs.
  • the party that initiates the VNF instantiation request may be referred to as the virtualization service requester.
  • the party that receives the instantiated VNF request and deploys the VNF according to the instantiated VNF request may be referred to as the virtualization service provider.
  • the virtualization service provider needs to obtain the description information of the service from the virtualization service requester, that is, the network service template (Network Service Descriptor, NSD).
  • NSD Network Service Descriptor
  • NSD mainly describes the topological structure information of the service and the description information of each VNF contained, namely VNFD.
  • a virtual link descriptor VLD
  • the virtual service requester can be NFVO or sender.
  • the sender can specifically be OSS/BSS.
  • FIG. 2A is a schematic structural diagram of a VNFD provided by this application.
  • Fig. 2B is a schematic diagram of the structure of the VNF obtained after the deployment of the above-mentioned VNFD.
  • Figure 2C is a schematic diagram of the structure of NS_1 containing several VNFs.
  • the VNFD includes virtual deployment unit (Virtualization Deployment Unit, VDU) 1, VDU2, connection point (connection point, CP)_A, CP_B, virtual connection (virtual link, VL) and other information.
  • VDU represents the application software that needs to be deployed on the virtual machine.
  • CP stands for VNF connection information, for example, it can be virtual network card information, which can be represented by an IP address or a MAC address.
  • VL is a virtual connection that connects multiple VDUs within a VNF. It can be represented by information such as connection type and bandwidth.
  • the VNFM is deployed using the above-mentioned VNFD, and the VNF obtained after deployment includes virtualized network function component (VNFC) 1, VNFC2, CP_A instance, CP_B instance, and VL instance.
  • VNFC virtualized network function component
  • VDU1 in VNFD generates VNFC1 after deployment
  • VDU2 in VNFD generates VNFC2 after deployment.
  • NS_1 includes VNF_1, VNF_2, VNF_3, VNF_4, and VNF_5.
  • VNF_1 and VNF_2 are respectively connected to VNF_3 through the VL_1 instance.
  • VNF_3 is connected to the service access point (SAP) through the VL_2 instance.
  • SAP can also be called a service connection point.
  • SAP is the external connection point of nested NS_2.
  • VNF_4 connects to SAP.
  • VNF_4 can communicate with VNFs outside the nested NS_2 through SAP.
  • VNF_4 is connected to VNF_5 through the VL_3 instance.
  • VNF_4 and VNF_5 belong to VNFs in nested NS_2.
  • the global NFVO performs life cycle management on NS_1.
  • Local NFVO performs life cycle management on nested NS_2.
  • a communication interface such as an or-or interface, is set between the global NFVO and the local NFVO.
  • the local NFVO When the local NFVO performs life cycle management on the nested NS_2, such as elastic expansion of the nested NS_2 and terminates the operation of the nested NS_2, the local NFVO sends an authorization request to the global NFVO, and the global NFVO authorizes the local NFVO to perform life cycle management on the nested NS_2 Later, the local NFVO performs life cycle management on the nested NS_2.
  • an embodiment of the present application provides an authorization method for network service life cycle management.
  • the method includes: a first NFVO device receives from a second NFVO The authorization request of the device, the authorization request is used to request authorization to perform a first operation on the second NS, and the first operation is an operation for the second NFVO device to perform life cycle management on the second NS. If the first NFVO device determines that the resources of the first NS satisfy the first operation on the second NS, it sends an authorization response to the second NFVO device to authorize the first operation on the second NS.
  • the second NFVO device After receiving the authorization response from the first NFVO device, the second NFVO device performs the first operation on the second NS.
  • the authorization response is used to indicate to perform the first operation on the second NS. Therefore, when the second NFVO device performs life cycle management on the second NS, the problem of management negotiation between the second NFVO device and the first NFVO device is solved, and the life cycle of the second NFVO device on the second NS is reduced. The impact of management on the first NS.
  • the first NFVO device is used to implement the function of a global NFVO, for example, the first NFVO device is used to perform life cycle management on the first NS.
  • the second NFVO device is used to implement the function of a local NFVO.
  • the second NFVO device is used to perform life cycle management on the second NS.
  • the first NFVO device is connected to the second NFVO device.
  • the second NS is nested within the first NS.
  • the first NS may be NS_1.
  • the second NS may be NS_2.
  • Fig. 3 is a flowchart of an authorization method for network service life cycle management provided by an embodiment of the application. As shown in Figure 3, the method may include:
  • the second NFVO device sends an authorization request to the first NFVO device, requesting authorization to perform the first operation on the second NS.
  • the first operation is that the second NFVO device performs life cycle management on the second NS.
  • the first operation may be an expansion operation of the second NS by the second NFVO device.
  • the resources of the service provided by the second NS cannot carry so many users, which may cause network congestion. Therefore, the capacity of carrying users of the second NS can be expanded to avoid network congestion.
  • the first operation may be a deletion operation of the second NS by the second NFVO device.
  • the second NFVO device can delete the second NS and release the resources used to deploy the second NS. The waste of resources managed by the second NFVO device is reduced, and the utilization rate of resources is improved.
  • the second NFVO device may send an authorization request to the first NFVO device through the or-or interface.
  • the first NFVO device receives an authorization request from the second NFVO device.
  • the authorization request is used to request authorization to perform a first operation on the second NS, and the first operation is an operation for the second NFVO device to perform life cycle management on the second NS.
  • the first operation is an operation for the second NFVO device to perform life cycle management on the second NS.
  • the second NFVO device may send an authorization request to the first NFVO device through the or-or interface.
  • the first NFVO device judges whether the resources of the first NS are sufficient to perform the first operation on the second NS.
  • the second NS Since the second NS is nested within the first NS, the second NS has an association relationship with the first NS. If the second NFVO device performs the first operation on the second NS, the first NS may affect whether the second NFVO device performs the first operation on the second NS successfully. Therefore, the first NFVO device determines whether the resources of the first NS are satisfied Perform the first operation on the second NS.
  • the first NFVO device determines that the resources of the first NS are sufficient to perform the first operation on the second NS, perform S304; if the first NFVO device determines that the resources of the first NS are not sufficient to perform the first operation on the second NS, perform S307.
  • the first NFVO device sends an authorization response to the second NFVO device to authorize the first operation on the second NS.
  • the authorization response is used to indicate to perform the first operation on the second NS.
  • the second NFVO device receives an authorization response from the first NFVO device.
  • the second NFVO device performs the first operation on the second NS.
  • the second NFVO device performs a capacity expansion operation on the second NS.
  • the second NFVO device performs a delete operation on the second NS.
  • the first NFVO device sends a failure response to the second NFVO device, and the first operation on the second NS is not allowed.
  • the failure response may also include the reason for the failure.
  • the failure response may also include the reason for the failure. For example, if the second NFVO device performs an expansion operation on the second NS, after expanding the capacity of the second NS, the data traffic on the second NS may increase. Because the second NS is nested in the first NS, the second NS It has an association relationship with the first NS, so the data traffic on the network connected to the second NS in the first NS will also increase. If the increased data traffic exceeds the processing capacity of the network connected to the second NS in the first NS, the expansion of the second NS fails. Therefore, the first NFVO device is not allowed to perform capacity expansion operations on the second NS, and the failure cause may be that the first NS does not support the capacity expansion operations on the second NS.
  • the first NFVO device does not allow the deletion operation on the second NS, and the failure reason may be that the first NS does not support the deletion operation on the second NS.
  • the second NFVO device receives a failure response from the first NFVO device.
  • the failure response is used to indicate that the first operation on the second NS is not allowed.
  • the second NFVO device does not perform capacity expansion operations on the second NS.
  • the second NFVO device does not delete the second NS.
  • the second NFVO device determines not to perform the first operation on the second NS, it may also decide whether to perform other life cycle management on the second NS.
  • the first operation may be an expansion operation of the second NS by the second NFVO device. If the second NFVO device expands the second NS, it will increase the amount of data processed by the second NS and increase the external data traffic of the second NS, because the second NS is nested in the first NS Therefore, the second NS has an association relationship with the first NS. Therefore, the first NFVO device can determine whether the resources of the first NS satisfy the capacity expansion of the second NS by judging the related data traffic in the first NS and the second NS. operating. As shown in Figure 4, S303 may include the following detailed steps S3031 and 3032.
  • the first NFVO device acquires the first data and the second data.
  • the first data is data traffic related to the second NS in the first NS.
  • the second data is the predicted data flow after the expansion operation of the second NS.
  • the first NFVO device may collect the data traffic of the network connected to the SAP in the second NS as the first data.
  • the SAP in NS_2 is connected to the VL_2 instance in NS_1, the VL_2 instance can be used as a network connected to the SAP in NS_2, and the first NFVO device can collect the data traffic on the VL_2 instance as the first data.
  • the "network" here may also be referred to as a virtual network or a virtual connection.
  • the second data may be passively received from the first NFVO device.
  • the authorization request from the second NFVO device received by the first NFVO device includes the second data.
  • the first NFVO device can obtain the second data from the authorization request.
  • the second data is the predicted data traffic on the SAP connected to the first NS after the expansion operation on the second NS.
  • the second data may be the predicted data traffic on the SAP connected to the VL_2 instance in NS_1.
  • the second data may be actively obtained from the first NFVO device.
  • the authorization request includes a first address, and the first address is used to indicate an address where the second NFVO device stores the second data.
  • the first NFVO device can obtain the second data from the second NFVO device according to the first address.
  • the first NFVO device sends a first acquisition request to the second NFVO device, where the first acquisition request includes a first address.
  • the first acquisition request is used to request the second NFVO device to feed back the second data.
  • the second NFVO device receives the first acquisition request from the first NFVO device.
  • the second NFVO device After receiving the first acquisition request, acquires the second data according to the storage location indicated by the first address, and feeds back the second data to the first NFVO device.
  • the first NFVO device receives second data from the second NFVO device.
  • the first NFVO device judges whether the first data is greater than the second data.
  • the first NFVO device determines that the resources of the first NS meet the requirements for the second NS.
  • NS performs an expansion operation and executes S304; if the first data is less than or equal to the second data, it means that the bandwidth of the network connected to the second NS in the first NS does not meet the requirements after the expansion operation on the second NS, and the first NFVO The device determines that the resources of the first NS are not sufficient to perform the capacity expansion operation on the second NS, and executes S307.
  • the first NFVO device determines that the resources of the first NS meet the capacity expansion operation of the second NS.
  • the first NFVO device determines that the resources of the first NS are not sufficient to perform the capacity expansion operation on the second NS.
  • the first NFVO device may also instruct the second NFVO device to report information required for the expansion operation. As shown in FIG. 6, before the second NFVO device sends an authorization request to the first NFVO device, that is, S301, the method further includes the following steps.
  • the first NFVO device sends a first authorization policy to the second NFVO device, instructing to collect data traffic of the second NS.
  • the first authorization policy is used to instruct to collect external data traffic of the second NS when the second NFVO device determines to perform a capacity expansion operation on the second NS.
  • the second NFVO device can collect data traffic on the SAP connected to the VL_2 instance in NS_1.
  • the first authorization policy is used to instruct to determine the predicted data flow of the second NS when the second NFVO device determines to perform a capacity expansion operation on the second NS.
  • the second NFVO device receives the first authorization policy from the first NFVO device.
  • the second NFVO device may also perform the following S603 and S604.
  • the second NFVO device collects the data traffic of the second NS.
  • the second NFVO device may send a request message to the VIM, requesting the VIM to feed back the external data traffic of the second NS.
  • the VIM may feed back the external data traffic of the second NS to the second NFVO device through the VNFM.
  • the second NFVO device determines second data according to the data flow of the second NS.
  • the second NFVO device may use artificial intelligence technology or data analysis technology (such as big data analysis technology) to analyze the external data traffic of the second NS to obtain the second NS after the expansion operation of the second NS. 2.
  • the second NFVO device may also report the external data traffic of the second NS to the first NFVO device, and the first NFVO device determines the predicted data traffic of the second NS according to the external data traffic of the second NS.
  • the first NFVO device may also perform the expansion operation on the first NS, so that the resources of the first NS meet the requirements for the second NS. Perform expansion operations. For example, as shown in FIG. 6, the method further includes S605.
  • the first NFVO device performs a first operation on the virtual connection connected to the second NS in the first NS.
  • the first NFVO device may perform a capacity expansion operation on the virtual connection connected to the second NS in the first NS according to the predicted data flow of the second NS.
  • the first NFVO device determines that the resources of the first NS are not sufficient to perform the capacity expansion operation on the second NS.
  • the first NFVO device can perform an expansion operation on the VL_2 instance, so that the data traffic on the VL_2 instance is 1GB, so that the VL_2 instance supports the expansion operation on the second NS.
  • the first operation is a shrinking operation of the second NS by the second NFVO device.
  • the first NFVO device can perform a capacity reduction operation on the virtual connection connected to the second NS in the first NS, thereby reducing the waste of resources managed by the first NFVO device.
  • the management negotiation problem between the second NFVO device and the first NFVO device is solved, and the time when the second NFVO device performs the expansion operation on the second NS is reduced. The impact on the first NS.
  • the first operation is a deletion operation of the second NS by the second NFVO device. Since the second NS is nested within the first NS, the second NS has an association relationship with the first NS. If the second NFVO device deletes the second NS, the second NS cannot provide services. For example, data transmission needs to be performed between the second NS and the first NS. If the second NFVO device deletes the second NS, data transmission cannot be performed between the second NS and the first NS. Therefore, the first NFVO device can determine whether the resources of the first NS satisfy the deletion operation of the second NS by determining whether the first NS and the second NS have a dependency relationship. As shown in Fig. 7, S303 may include the following detailed step S3033.
  • the first NFVO device judges whether the first NS and the second NS have a dependency relationship.
  • the first NFVO device determines that the resources of the first NS are sufficient to perform the first operation on the second NS, and execute S304 . If there is a dependency between the first NS and the second NS (for example, there is data transmission between the first NS and the second NS), the first NFVO device determines that the resources of the first NS are not sufficient to perform the first operation on the second NS, and execute S307.
  • the first NFVO device may deploy the third NS so that the third NS
  • the NS provides services of the second NS, the third NS establishes a connection with the first NS, and the third NS performs data transmission with the first NS.
  • the method further includes the following steps.
  • the first NFVO device judges whether the third NS is successfully deployed within the first time period, and the third NS is used to provide the service of the second NS.
  • the first duration is the predicted duration during which the second NS can continue to provide services.
  • the first NFVO device can deploy the third NS within the first time period. If the third NS is successfully deployed within the first time period, it means that the third NS can replace the second NS and continue to provide services, such as the third NS
  • the first NFVO device sends an authorization response to the second NFVO device, that is, executes S304, and the second NFVO device deletes the second NS; if the deployment of the third NS fails within the first time period, it means that there is nothing else
  • the NS can replace the second NS to continue to provide services, and the first NFVO device sends a failure response to the second NFVO device, that is, executes S307 and does not allow the second NFVO device to delete the second NS.
  • the first duration may be passively received from the first NFVO device.
  • the authorization request from the second NFVO device received by the first NFVO device includes the first duration.
  • the first NFVO device may obtain the first duration from the authorization request.
  • the first duration may be the predicted duration that NS_2 can continue to provide services.
  • the first duration may be actively obtained from the first NFVO device.
  • the authorization request includes a second address, and the second address is used to instruct the second NFVO device to store the address for the first duration.
  • the first NFVO device may obtain the first duration from the second NFVO device according to the second address.
  • the first NFVO device sends a second acquisition request to the second NFVO device, where the second acquisition request includes a second address.
  • the second acquisition request is used to request the second NFVO device to feed back the first duration.
  • the second NFVO device receives a second acquisition request from the first NFVO device.
  • the second NFVO device After receiving the second acquisition request, acquires the first duration according to the storage location indicated by the second address, and feeds back the first duration to the first NFVO device.
  • the first NFVO device receives the first duration from the second NFVO device.
  • the first NFVO device may also instruct the second NFVO device to report information required for the deletion operation. As shown in FIG. 10, before the second NFVO device sends an authorization request to the first NFVO device, that is, S301, the method further includes the following steps.
  • the first NFVO device sends a second authorization policy to the second NFVO device, instructing the second NFVO device to predict the first duration.
  • the second authorization policy is used to instruct to predict the first duration after the second NFVO device determines to delete the second NS.
  • the second NFVO device can predict the length of time that NS_2 can continue to provide services.
  • the second authorization policy may also include the reason why the second NFVO device determines to perform the deletion operation on the second NS. After the second NFVO device determines the deletion operation on the second NS, the authorization request sent to the first NFVO device may carry the reason for the deletion operation on the second NS.
  • the second NFVO device receives the second authorization policy from the first NFVO device.
  • the second NFVO device may also perform the following S1003.
  • the second NFVO device determines the first duration.
  • the second NFVO device determines the first duration after determining to delete the second NS. In some embodiments, the second NFVO device may send a request message to the VIM, requesting the VIM to feed back the first duration. Optionally, the VIM may feed back the first duration to the second NFVO device through the VNFM.
  • the management negotiation problem between the second NFVO device and the first NFVO device is solved, and the time when the second NFVO device deletes the second NS is reduced. The impact on the first NS.
  • the first NFVO device and the second NFVO device include hardware structures and/or software modules corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application scenarios and design constraints of the technical solution.
  • FIG. 11 and FIG. 12 are schematic structural diagrams of possible communication devices provided by embodiments of this application. These communication devices can be used to implement the functions of the first NFVO device or the second NFVO device in the foregoing method embodiment, and therefore can also achieve the beneficial effects of the foregoing method embodiment.
  • the communication device may be a global NFVO or a local NFVO as shown in FIG. 2C, or a module (such as a chip) applied to the first NFVO device or the second NFVO device.
  • the communication device 1100 includes a processing unit 1110 and a transceiving unit 1120.
  • the communication device 1100 is configured to implement the function of the first NFVO device or the second NFVO device in the method embodiment shown in any one of FIGS. 3 to 10.
  • the transceiver unit 1120 is used to perform S302, S304, and S307; the processing unit 1110 is used to perform S303.
  • the transceiver unit 1120 is used to perform S301, S305, and S308; the processing unit 1110 is used to perform S306.
  • the transceiver unit 1120 is used to perform S302, S304, and S307; the processing unit 1110 is used to perform S3031 and S3032.
  • the transceiver unit 1120 is used to perform S301, S305, and S308; the processing unit 1110 is used to perform S306.
  • the transceiver unit 1120 is used to perform S302, S304, S307, S501, and S504; the processing unit 1110 is used to perform S3031 and S3032.
  • the transceiver unit 1120 is used to perform S301, S305, S308, S502, and S503; the processing unit 1110 is used to perform S306.
  • the transceiver unit 1120 is used to perform S302, S304, S307, S501, S504, and S601;
  • the processing unit 1110 is used to perform S3031 S3032 and S605.
  • the transceiver unit 1120 is used to perform S301, S305, S308, S502, S503, and S602;
  • the processing unit 1110 is used to perform S306, S603 and S604.
  • the transceiver unit 1120 is used to perform S302, S304, and S307; the processing unit 1110 is used to perform S3033.
  • the transceiver unit 1120 is used to perform S301, S305, and S308; the processing unit 1110 is used to perform S306.
  • the transceiver unit 1120 is used to perform S302, S304, and S307; the processing unit 1110 is used to perform S3033 and S801.
  • the transceiver unit 1120 is used to perform S301, S305, and S308; the processing unit 1110 is used to perform S306.
  • the transceiver unit 1120 is used to perform S302, S304, S307, S901, and S904; the processing unit 1110 is used to perform S3033 and S801.
  • the transceiver unit 1120 is used to perform S301, S305, S308, S902, and S903; the processing unit 1110 is used to perform S306.
  • the transceiver unit 1120 is used to perform S302, S304, S307, S901, S904, and S1001;
  • the processing unit 1110 is used to perform S3033 and S801.
  • the transceiver unit 1120 is used to perform S301, S305, S308, S902, S903, and S1002;
  • the processing unit 1110 is used to perform S306 and S1003.
  • processing unit 1110 and the transceiver unit 1120 can be obtained directly with reference to the relevant descriptions in the method embodiments shown in FIGS. 3 to 10, and will not be repeated here.
  • the communication device 1200 includes a processor 1210 and an interface circuit 1220.
  • the processor 1210 and the interface circuit 1220 are coupled with each other.
  • the interface circuit 1220 may be a transceiver or an input/output interface.
  • the communication device 1200 may further include a memory 1230 for storing instructions executed by the processor 1210 or storing input data required by the processor 1210 to run the instructions or storing data generated after the processor 1210 runs the instructions.
  • the processor 1210 is used to perform the functions of the above-mentioned processing unit 1110
  • the interface circuit 1220 is used to perform the functions of the above-mentioned transceiving unit 1120.
  • the terminal device chip When the foregoing communication device is a chip applied to a terminal device, the terminal device chip implements the function of the terminal device in the foregoing method embodiment.
  • the terminal device chip receives information from other modules in the terminal device (such as a radio frequency module or antenna), and the information is sent by the network device to the terminal device; or, the terminal device chip sends information to other modules in the terminal device (such as a radio frequency module or antenna).
  • the antenna sends information, which is sent by the terminal device to the network device.
  • the network device chip implements the function of the network device in the foregoing method embodiment.
  • the network device chip receives information from other modules in the network device (such as radio frequency modules or antennas), and the information is sent by the terminal device to the network device; or, the network device chip sends information to other modules in the network device (such as radio frequency modules or antennas).
  • the antenna sends information, which is sent by the network device to the terminal device.
  • the processor in the embodiments of the present application may be a central processing unit (Central Processing Unit, CPU), or other general-purpose processors, digital signal processors (Digital Signal Processors, DSPs), and application specific integrated circuits. (Application Specific Integrated Circuit, ASIC), Field Programmable Gate Array (Field Programmable Gate Array, FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof.
  • the general-purpose processor may be a microprocessor or any conventional processor.
  • the method steps in the embodiments of the present application can be implemented by hardware, and can also be implemented by a processor executing software instructions.
  • Software instructions can be composed of corresponding software modules, which can be stored in random access memory (Random Access Memory, RAM), flash memory, read-only memory (Read-Only Memory, ROM), and programmable read-only memory (Programmable ROM) , PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), register, hard disk, mobile hard disk, CD-ROM or well-known in the art Any other form of storage medium.
  • RAM Random Access Memory
  • ROM read-only memory
  • PROM programmable read-only memory
  • Erasable PROM Erasable PROM
  • EPROM electrically erasable programmable read-only memory
  • register hard disk, mobile hard disk, CD-ROM or well-known in the art Any other form of storage medium.
  • An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium and write information to the storage medium.
  • the storage medium may also be an integral part of the processor.
  • the processor and the storage medium may be located in the ASIC.
  • the ASIC can be located in a network device or a terminal device.
  • the processor and the storage medium may also exist as discrete components in the network device or the terminal device.
  • the computer program product includes one or more computer programs or instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, network equipment, user equipment, or other programmable devices.
  • the computer program or instruction may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer program or instruction may be transmitted from a website, a computer, or The server or data center transmits to another website site, computer, server or data center through wired or wireless means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that integrates one or more available media.
  • the usable medium may be a magnetic medium, such as a floppy disk, a hard disk, and a magnetic tape; it may also be an optical medium, such as a digital video disc (digital video disc, DVD); and it may also be a semiconductor medium, such as a solid state drive (solid state drive). , SSD).
  • “at least one” refers to one or more, and “multiple” refers to two or more.
  • “And/or” describes the association relationship of the associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the associated object before and after is an “or” relationship; in the formula of this application, the character “/” indicates that the associated object before and after is a kind of "division" Relationship.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

公开了一种网络业务的生命周期管理的授权方法及装置，涉及网络功能虚拟化领域，解决了全局NFVO如何确定是否授权局部NFVO对嵌套NS的操作的问题。第一NFVO设备接收来自第二NFVO设备的授权请求，若第一NFVO设备确定第一NS的资源满足对第二NS进行第一操作，向第二NFVO设备发送授权响应，以授权对第二NS进行第一操作。第二NFVO设备接收来自第一NFVO设备的授权响应后，对第二NS进行第一操作。授权响应用于指示对第二NS进行第一操作。

Description

网络业务的生命周期管理的授权方法及装置
本申请要求于2019年12月23日提交中国国家知识产权局、申请号为201911342710.1、发明名称为“网络业务的生命周期管理的授权方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及网络功能虚拟化领域，尤其涉及一种网络业务的生命周期管理的授权方法及装置。
背景技术
网络功能虚拟化(network function virtualization，NFV)技术是采用虚拟化技术将传统网络中专用设备的功能虚拟化为独立的应用，灵活地部署在基于标准的计算硬件、存储硬件和网络硬件等其他设备构建的统一基础设施平台上。在NFV系统中，NFV编排器(NFV orchestrator，NFVO)主要负责处理虚拟化的网络业务(Network Service，NS)的生命周期管理(Lifecycle Management，LCM)、虚拟基础设施和NFV基础设施层(NFV infrastructure，NFVI)中虚拟资源的分配和调度等。在一些实施例中，全局NFVO所管理的NS可以包含至少一个嵌套NS(nested NS)，嵌套NS可以由局部NFVO管理，全局NFVO与局部NFVO可以进行通信。当局部NFVO对嵌套NS进行生命周期管理时，局部NFVO可以向全局NFVO发送授权请求，在接收到授权响应后执行相应的操作。但是，全局NFVO如何识别局部NFVO对嵌套NS的操作是否对全局NFVO所管理的NS有影响，是否授权局部NFVO对嵌套NS的操作，目前还没有相应的解决方案。
发明内容
本申请提供了一种网络业务的生命周期管理的授权方法及装置，解决了全局NFVO如何确定是否授权局部NFVO对嵌套NS的操作的问题。
为达到上述目的，本申请采用如下技术方案：
第一方面，提供了一种网络业务的生命周期管理的授权方法，该方法可应用于第一NFVO设备。所述方法包括：第一NFVO设备接收来自第二NFVO设备的授权请求，授权请求用于请求授权对第二NS进行第一操作，第一操作为第二NFVO设备对第二NS进行生命周期管理的操作。若第一NFVO设备确定第一NS的资源满足对第二NS进行第一操作，向第二NFVO设备发送授权响应，以授权对第二NS进行第一操作。
本申请提供的网络业务的生命周期管理的授权方法，在第一NFVO设备确定第一NS的资源满足对第二NS进行生命周期管理的情况下，第一NFVO设备才授权对第二NS进行生命周期管理。从而，解决了对嵌套的NS进行生命周期管理时，NFVO设备间的管理协商问题，降低了对全局NFVO管理的NS的影响。
可选的，若第一NFVO设备确定第一NS的资源不满足对第二NS进行第一操作，向第二NFVO设备发送失败响应，失败响应用于指示不允许对第二NS进行第一操作。从而，避免第一NS的资源不满足对第二NS进行第一操作的情况下，再对第二NS进行生命周期管理产生的对第一NS的影响。
在一种可能的实现方式中，第一操作为扩容操作，第一NFVO设备判断第一NS的资源是否满足对第二NS进行第一操作，包括：第一NFVO设备获取第一数据和第二数据，判断第一数据是否大于第二数据；若第一数据大于第二数据，第一NFVO设备确定第一NS的资源满足对第二NS进行第一操作；若第一数据小于或等于第二数据，第一NFVO设备确定第一NS的资源不满足对第二NS进行第一操作。其中，第一数据为第一NS内与第二NS相关的数据流量，第二数据为对第二NS进行第一操作后的预测数据流量。由于第二NS是嵌套在第一NS内的，所以第二NS与第一NS具有关联关系。利用第一NS内与第二NS相关的数据流量确定第一NS是否支持对第二NS进行扩容，以便于对第二NS进行扩容操作。从而，解决了对嵌套的NS进行生命周期管理时，NFVO设备间的管理协商问题，降低了对全局NFVO管理的NS的影响。
在一种可能的设计中，第二数据可以是第一NFVO设备被动接收的。例如，授权请求包括第二数据。
在另一种可能的设计中，第二数据可以是第一NFVO设备主动获取的。例如，授权请求包括第一地址，第一地址用于指示存储第二数据的地址，第一NFVO设备获取第二数据，包括：第一NFVO设备向第二NFVO设备发送第一获取请求，通过第一获取请求包括的第一地址接收来自第二NFVO设备的第二数据。第一获取请求用于请求第二NFVO设备反馈第二数据。
在另一种可能的实现方式中，方法还包括：第一NFVO设备对第一NS内与第二NS相连接的虚连接进行第一操作。从而，以便于第一NS支持对第二NS进行扩容操作。
在另一种可能的实现方式中，方法还包括：第一NFVO设备向第二NFVO设备发送第一授权策略，第一授权策略用于指示采集第二NS的数据流量。从而，使得第二NFVO设备上报对第二NS进行扩容操作的相关信息，以便于第一NFVO设备根据相关信息确定第一NS的资源是否满足对第二NS进行扩容操作，是否可以授权对第二NS进行扩容操作。
在另一种可能的实现方式中，第一操作为删除操作，第一NFVO设备判断第一NS的资源是否满足对第二NS进行第一操作，包括：第一NFVO设备判断第一NS与第二NS是否有依赖关系；若第一NS与第二NS无依赖关系，第一NFVO设备确定第一NS的资源满足对第二NS进行第一操作。由于第二NS是嵌套在第一NS内的，所以第二NS与第一NS具有关联关系。利用第一NS与第二NS间的依赖关系确定第一NS是否支持删除第二NS，以便于对第二NS进行删除操作。从而，解决了对嵌套的NS进行生命周期管理时，NFVO设备间的管理协商问题，降低了对全局NFVO管理的NS的影响。
可选的，方法还包括：若第一NS与第二NS有依赖关系，第一NFVO设备确定第一NS的资源不满足对第二NS进行第一操作。
在另一种可能的实现方式中，若第一NS与第二NS有依赖关系，方法还包括：第一NFVO设备判断在第一时长内是否成功部署第三NS，第三NS用于提供第二NS的服务，第一时长为第二NS提供服务的预测时长。若在第一时长内成功部署第三NS，第一NFVO设备向第二NFVO设备发送授权响应。若在第一时长内部署第三NS失败，第一NFVO设备向第二NFVO设备发送失败响应。从而，通过部署第三NS，使第三NS替代第二NS，继续提供第二NS的服务，避免 删除第二NS，对第一NS的影响。
在一种可能的设计中，第一时长可以是第一NFVO设备被动接收的。例如，授权请求包括第一时长。
在另一种可能的设计中，第一时长可以是第一NFVO设备主动获取的。例如，授权请求包括第二地址，第二地址用于指示存储第一时长的地址，方法还包括：第一NFVO设备向第二NFVO设备发送第二获取请求，接收来自第二NFVO设备的第一时长。第二获取请求用于请求第二NFVO设备反馈第一时长，第二获取请求包括第二地址。
在另一种可能的实现方式中，方法还包括：第一NFVO设备向第二NFVO设备发送第二授权策略，第二授权策略用于指示第二NFVO设备预测第一时长。从而，使得第二NFVO设备上报对第二NS进行删除操作的相关信息，以便于第一NFVO设备根据相关信息确定是否可以删除第二NS，是否可以授权对第二NS进行删除操作。
第二方面，提供了一种网络业务的生命周期管理的授权方法，该方法可应用于第二NFVO设备。所述方法包括：第二NFVO设备向第一NFVO设备发送授权请求，授权请求用于请求授权对第二NS进行第一操作，第一操作为第二NFVO设备对第二NS进行生命周期管理的操作；第二NFVO设备接收来自第一NFVO设备的授权响应后，对第二NS进行第一操作。授权响应用于指示对第二NS进行第一操作。
本申请提供的网络业务的生命周期管理的授权方法，第二NFVO设备向第一NFVO设备发送授权请求后，使得第一NFVO设备确定第一NS的资源满足对第二NS进行生命周期管理的情况下，第一NFVO设备才授权对第二NS进行生命周期管理，第二NFVO设备对第二NS进行第一操作。从而，解决了对嵌套的NS进行生命周期管理时，NFVO设备间的管理协商问题，降低了对全局NFVO管理的NS的影响。
可选的，方法还包括：第二NFVO设备接收来自第一NFVO设备的失败响应，失败响应用于指示不允许第二NFVO设备对第二NS进行第一操作。从而，避免第一NS的资源不满足对第二NS进行第一操作的情况下，再对第二NS进行生命周期管理产生的对第一NS的影响。
在一种可能的实现方式中，第一操作为扩容操作，第二NFVO设备向第一NFVO设备发送授权请求之前，方法还包括：第二NFVO设备采集第二NS的数据流量，并根据第二NS的数据流量确定第二数据，第二数据为对第二NS进行第一操作后的预测数据流量。
在一种可能的设计中，授权请求包括第二数据。
在一种可能的设计中，授权请求包括第一地址，第一地址用于指示存储第二数据的地址，方法还包括：第二NFVO设备接收来自第一NFVO设备的第一获取请求，并向第一NFVO设备发送的第二数据。第一获取请求用于请求第二NFVO设备反馈第二数据，第一获取请求包括第一地址。
在另一种可能的实现方式中，方法还包括：第二NFVO设备接收来自第一NFVO设备的第一授权策略，第一授权策略用于指示第二NFVO设备采集第二NS的数据流量。从而，使得第二NFVO设备上报对第二NS进行扩容操作的相关信息，以便于第一NFVO设备根据相关信息确定第一NS的资源是否满足对第二NS进行扩容操作，是否可以授权对第二NS进行扩容操作。
在另一种可能的实现方式中，第一操作为删除操作，第二NFVO设备向第一NFVO设备发送授权请求之前，方法还包括：第二NFVO设备确定第一时长，第一时长为第二NS提供服务的预测时长。
在一种可能的设计中，授权请求包括第一时长。
在另一种可能的设计中，授权请求包括第二地址，第二地址用于指示存储第一时长的地址，方法还包括：第二NFVO设备接收来自第一NFVO设备的第二获取请求，并向第一NFVO设备发送的第一时长，第二获取请求用于请求第二NFVO设备反馈第一时长，第二获取请求包括第二地址。
在另一种可能的实现方式中，方法还包括：第二NFVO设备接收来自第一NFVO设备的第二授权策略，第二授权策略用于指示第二NFVO设备预测第一时长。从而，使得第二NFVO设备上报对第二NS进行删除操作的相关信息，以便于第一NFVO设备根据相关信息确定是否可以删除第二NS，是否可以授权对第二NS进行删除操作。
第三方面，提供了一种通信装置，用于实现上述第一方面描述的方法。通信装置可以为第一NFVO设备。例如，装置包括：收发单元和处理单元。所述收发单元用于接收来自第二NFVO设备的授权请求，授权请求用于请求授权对第二NS进行第一操作，第一操作为第二NFVO设备对第二NS进行生命周期管理的操作。若所述处理单元确定第一NS的资源满足对第二NS进行第一操作，所述收发单元还用于向第二NFVO设备发送授权响应，以授权对第二NS进行第一操作。
可选的，若所述处理单元确定第一NS的资源不满足对第二NS进行第一操作，所述收发单元还用于向第二NFVO设备发送失败响应，失败响应用于指示不允许对第二NS进行第一操作。从而，避免第二NFVO设备对第二NS进行生命周期管理的操作对第一NS的影响。
在一种可能的实现方式中，第一操作为扩容操作，所述处理单元用于获取第一数据和第二数据，并判断第一数据是否大于第二数据；若第一数据大于第二数据，所述处理单元用于确定第一NS的资源满足对第二NS进行第一操作；若第一数据小于或等于第二数据，所述处理单元用于确定第一NS的资源不满足对第二NS进行第一操作。其中，第一数据为第一NS内与第二NS相关的数据流量，第二数据为对第二NS进行第一操作后的预测数据流量。
在一种可能的设计中，授权请求包括第二数据。
在另一种可能的设计中，授权请求包括第一地址，第一地址用于指示存储第二数据的地址，所述收发单元还用于向第二NFVO设备发送第一获取请求，并接收来自第二NFVO设备的第二数据。第一获取请求用于请求第二NFVO设备反馈第二数据，第一获取请求包括第一地址。
在另一种可能的实现方式中，所述处理单元还用于对第一NS内与第二NS相连接的虚连接进行第一操作。
在另一种可能的实现方式中，所述收发单元还用于向第二NFVO设备发送第一授权策略，第一授权策略用于指示采集第二NS的数据流量。
在另一种可能的实现方式中，第一操作为删除操作，所述处理单元用于判断第一NS与第二NS是否有依赖关系，若第一NS与第二NS无依赖关系，确定第一NS的资源满足对第二NS进行第一操作。
可选的，若第一NS与第二NS有依赖关系，所述处理单元用于确定第一NS的资源不满足对第二NS进行第一操作。
在另一种可能的实现方式中，若第一NS与第二NS有依赖关系，所述处理单元还用于判断在第一时长内是否成功部署第三NS，第三NS用于提供第二NS的服务，第一时长为第二NS提供服务的预测时长；若在第一时长内成功部署第三NS，所述收发单元用于向第二NFVO设 备发送授权响应；若在第一时长内部署第三NS失败，所述收发单元用于向第二NFVO设备发送失败响应。
在一种可能的设计中，授权请求包括第一时长。
在另一种可能的设计中，授权请求包括第二地址，第二地址用于指示存储第一时长的地址，所述收发单元还用于向第二NFVO设备发送第二获取请求，接收来自第二NFVO设备的第一时长。第二获取请求用于请求第二NFVO设备反馈第一时长，第二获取请求包括第二地址；第一NFVO设备。
在另一种可能的实现方式中，所述收发单元还用于向第二NFVO设备发送第二授权策略，第二授权策略用于指示第二NFVO设备预测第一时长。
第四方面，提供了一种通信装置，用于实现上述第二方面描述的方法。通信装置可以为第二NFVO设备。例如，装置包括：收发单元和处理单元。所述收发单元用于向第一NFVO设备发送授权请求，授权请求用于请求授权对第二NS进行第一操作，第一操作为第二NFVO设备对第二NS进行生命周期管理的操作；所述收发单元还用于接收来自第一NFVO设备的授权响应，所述处理单元用于对第二NS进行第一操作。授权响应用于指示对第二NS进行第一操作。
可选的，所述收发单元还用于接收来自第一NFVO设备的失败响应，失败响应用于指示不允许第二NFVO设备对第二NS进行第一操作。
在一种可能的实现方式中，第一操作为扩容操作，所述处理单元还用于采集第二NS的数据流量，并根据第二NS的数据流量确定第二数据，第二数据为对第二NS进行第一操作后的预测数据流量。
在一种可能的设计中，授权请求包括第二数据。
在一种可能的设计中，授权请求包括第一地址，第一地址用于指示存储第二数据的地址，所述收发单元还用于接收来自第一NFVO设备的第一获取请求，并向第一NFVO设备发送的第二数据。第一获取请求用于请求第二NFVO设备反馈第二数据，第一获取请求包括第一地址。
在另一种可能的实现方式中，所述收发单元还用于接收来自第一NFVO设备的第一授权策略，第一授权策略用于指示第二NFVO设备采集第二NS的数据流量。
在另一种可能的实现方式中，第一操作为删除操作，所述处理单元还用于确定第一时长，第一时长为第二NS提供服务的预测时长。
在一种可能的设计中，授权请求包括第一时长。
在另一种可能的设计中，授权请求包括第二地址，第二地址用于指示存储第一时长的地址，所述收发单元还用于接收来自第一NFVO设备的第二获取请求，并向第一NFVO设备发送的第一时长。第二获取请求用于请求第二NFVO设备反馈第一时长，第二获取请求包括第二地址。
在另一种可能的实现方式中，所述收发单元还用于接收来自第一NFVO设备的第二授权策略，第二授权策略用于指示第二NFVO设备预测第一时长。
需要说明的是，上述第三方面和第四方面的功能模块可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的模块。例如，收发器，用于完成接收单元和发送单元的功能，处理器，用于完成处理单元的功能，存储器，用于处理器处理本申请的方法的程序指令。处理器、收发器和存储器通过总线连接并完成相互 间的通信。具体的，可以参考第一方面所述的方法至第二方面所述的方法中的NFVO设备的行为的功能。
第五方面，本申请还提供了一种通信装置，用于实现上述第一方面描述的方法。该通信装置包括芯片系统。例如所述通信装置包括处理器，用于实现上述第一方面描述的方法中的功能。所述通信装置还可以包括存储器，用于存储程序指令和数据。所述存储器与所述处理器耦合，所述处理器可以调用并执行所述存储器中存储的程序指令，用于实现上述第一方面描述的方法中的功能。所述通信装置还可以包括通信接口，所述通信接口用于该通信装置与其它设备进行通信。示例性地，所述通信装置为第一NFVO设备，该其它设备为第二NFVO设备。
在一种可能的设备中，该通信接口可以是收发器。收发器，用于接收授权请求和发送授权响应。处理器，用于判断第一NS的资源是否满足对第二NS进行第一操作，具体的可以参考上述各方面的阐述，不予赘述。
第六方面，本申请还提供了一种通信装置，用于实现上述第二方面描述的方法。该通信装置包括芯片系统。例如所述通信装置包括处理器，用于实现上述第二方面描述的方法中的功能。所述通信装置还可以包括存储器，用于存储程序指令和数据。所述存储器与所述处理器耦合，所述处理器可以调用并执行所述存储器中存储的程序指令，用于实现上述第二方面描述的方法中的功能。所述通信装置还可以包括通信接口，所述通信接口用于该通信装置与其它设备进行通信。示例性地，若所述通信装置为第二NFVO设备，该其它设备为第一NFVO设备。
在一种可能的设备中，该通信接口可以是收发器。收发器，用于发送授权请求和接收授权响应。处理器，用于对第二NS进行所述第一操作，具体的可以参考上述各方面的阐述，不予赘述。
第七方面，本申请还提供了一种计算机可读存储介质，包括：计算机软件指令；当计算机软件指令在通信装置中运行时，使得通信装置执行上述第一方面或第二方面所述的方法。
第八方面，本申请还提供了一种包含指令的计算机程序产品，当计算机程序产品在通信装置中运行时，使得通信装置执行上述第一方面或第二方面所述的方法。
第九方面，本申请提供了一种芯片系统，该芯片系统包括处理器，还可以包括存储器，用于实现上述方法中NVFO设备的功能。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
第十方面，本申请还提供了一种通信系统，所述通信系统包括第三方面描述的第一NFVO设备以及第四方面描述的第二NFVO设备；或所述通信系统包括第五方面描述的第一NFVO设备，以及第六方面描述的第二NFVO设备。
另外，上述任意方面的设计方式所带来的技术效果可参见第一方面和第二方面中不同设计方式所带来的技术效果，此处不再赘述。
附图说明
图1为本申请一实施例提供的一种NFV系统架构示例图；
图2A为本申请一实施例提供的一种VNFD的结构示意图；
图2B为根据上述VNFD部署后得到的VNF的结构示意图；
图2C为包含若干个VNF的NS_1的结构示意图；
图3为本申请一实施例提供的一种网络业务的生命周期管理的授权方法的流程图；
图4为本申请一实施例提供的一种网络业务的生命周期管理的授权方法的流程图；
图5为本申请一实施例提供的一种网络业务的生命周期管理的授权方法的流程图；
图6为本申请一实施例提供的一种网络业务的生命周期管理的授权方法的流程图；
图7为本申请一实施例提供的一种网络业务的生命周期管理的授权方法的流程图；
图8为本申请一实施例提供的一种网络业务的生命周期管理的授权方法的流程图；
图9为本申请一实施例提供的一种网络业务的生命周期管理的授权方法的流程图；
图10为本申请一实施例提供的一种网络业务的生命周期管理的授权方法的流程图；
图11为本申请提供的一种通信装置的组成示意图；
图12为本申请提供的另一种通信装置的组成示意图。
具体实施方式
本申请说明书和权利要求书及上述附图中的术语“第一”、“第二”和“第三”等是用于区别不同对象，而不是用于限定特定顺序。
在本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
为了下述各实施例的描述清楚简洁，首先给出相关技术的简要介绍：
传统的电信系统是通过各种专用的硬件设备组成，不同的功能采用不同的硬件设备。随着网络规模的增长，电信系统越来越复杂，带来了诸多的挑战。例如，新增业务的开发上线、系统的运维和资源利用率等。为了应对这些挑战及利用互联网(internet technology，IT)业界的虚拟化技术及云计算技术，全球主要的13个电信运营商联合发布了NFV白皮书，并宣布在欧洲电信标准协会(europe telecommunications standards institute，ETSI)成立NFV行业规范组(industry specific group，ISG)，制定NFV的需求及技术框架，推动NFV的发展。
NFV技术利用虚拟化技术对基础设施硬件设备(如计算设备、存储设备、网络设备)资源池化及虚拟化，对上层应用提供虚拟资源，实现软件和硬件解耦。开发新业务时，不需要单独部署硬件设备，只需要采用虚拟化技术将业务虚拟化为独立的应用(如VNF)，从而，大大缩短新业务上线时间，且使得虚拟资源供给速度大大增加。
NFV技术利用云计算技术，可以实现应用的弹性伸缩，实现虚拟资源与业务负荷相匹配，不仅提升了虚拟资源的利用效率，而且改善了NFV系统的响应速率。
图1为本申请实施例提供的一种NFV系统架构示例图。NFV系统可以在各种网络中使用，例如在一个数据中心网络、运营商网络或局域网来实现。NFV系统包括一个NFV管理和编排系统(NFV management and orchestration，NFV MANO)101、NFV基础设施层(NFV infrastructure，NFVI)102、多个虚拟网络功能(Virtual Network Function，VNF)103、 多个网元管理(element management，EM)104和运营支持系统/业务支持系统(operation-support system/business support system，OSS/BSS)105。
其中，NFV MANO 101用于执行对NFVI 102和VNF 103的监视和管理。NFV管理和编排系统101包括NFV编排器(NFV orchestrator，NFVO)1011，一个或多个VNF管理器(VNF manager，VNFM)1012和虚拟化基础设施管理器(virtualized infrastructure manager，VIM)1013。
NFVO 1011主要负责处理虚拟化的NS的生命周期管理、虚拟基础设施及NFVI中虚拟资源的分配和调度等。NFVO 1011也可以执行来自一个或多个VNFM 1012的资源相关请求(如：请求获取VNFD)，发送配置信息(如：VNFD、修改VNF信息请求和VNF实例化请求)到VNFM 1012，并收集VNF 103的状态信息。VNFD可以存储在NFVO上，也可以存储在NFVO所管理的数据库，以便NFVO可以获取到VNFD，将VNFD反馈给VNFM，VNFM根据VNFD部署VNF。NFVO可以存储多种功能的VNF对应的VNFD。另外，NFVO 1011可以与VIM 1013通信，以实现资源的分配和/或预留以及交换虚拟化硬件资源的配置和状态信息。
VNFM 1012主要负责一个或多个VNF 103的生命周期管理。比如，实例化(instantiating)，更新(updating)，查询，弹性伸缩(scaling)，终止(terminating)VNF 103等。VNFM 1012可以与VNF 103通信以完成VNF 103生命周期管理及交换配置和状态信息。在NFV系统中VNFM1012可以有多个，负责对不同类型的VNF进行生命周期管理。
VIM 1013可以执行资源管理的功能，例如管理基础设施资源的分配(例如增加资源到虚拟容器)和操作功能(如收集NFVI故障信息)。VNFM 1012和VIM 1013可以相互通信进行资源分配和交换虚拟化硬件资源的配置和状态信息。例如，控制和管理VNF 103与计算硬件1021，存储硬件1022，网络硬件1023，虚拟计算(virtual computing)1024，虚拟存储1025，虚拟网络1026的交互。
NFVI 102包括硬件资源层、虚拟化层(virtualization layer)和虚拟资源层。NFVI 102包括的硬件资源、软件资源或两者的组合来完成虚拟化环境的部署。换句话说，硬件资源和虚拟化层用于提供虚拟化的资源，例如作为虚拟机和其它形式的虚拟容器，用于VNF 103。硬件资源层包括计算硬件1021、存储硬件1022和网络硬件1023。计算硬件1021可以是市场上现成的硬件和/或用户定制的硬件，用来提供处理和计算资源。存储硬件1022可以是网络内提供的存储容量或驻留在存储硬件1022本身的存储容量(位于服务器内的本地存储器)。在一个实现方案中，计算硬件1021和存储硬件1022的资源可以被集中在一起。网络硬件1023可以是交换机、路由器和/或配置成具有交换功能的任何其他网络设备。网络硬件1023可以横跨多个域，并且可以包括多个由一个或一个以上传输网络互连的网络。NFVI 102里面的虚拟化层可以从物理层抽象硬件资源和解耦VNF 103，以便向VNF 103提供虚拟化资源。虚拟资源层包括虚拟计算1024、虚拟存储1025和虚拟网络1026。虚拟计算1024和虚拟存储1025可以以虚拟机、和/或其他虚拟容器的形式提供给VNF 103。例如，一个或一个以上的VNF 103可以部署在一个虚拟机(virtual machine，VM)上。虚拟化层抽象网络硬件1023，从而形成虚拟网络1026，虚拟网络1026可以包括虚拟交换机(virtual switch)，虚拟交换机用来提供虚拟机和其他虚拟机之间的连接。此外，网络硬件1023中的传输网络，可以采用集中式控制平面和一个单独的转发平面(如软件定义网络)虚拟化。
硬件上，计算硬件1021、存储硬件1022和网络硬件1023可能包含多个机框，或多个机架，甚至多个机房。软件上，可能存在一个VIM 1013，也可能存在多个VIM，分别管理不同 的硬件资源。
VNF 103为虚拟化的网络功能实例。
设备管理系统(EM)104是传统网络中用于对设备进行配置，管理的系统，在NFV系统中，EM 104也可以用于对VNF 103进行配置和管理，以及向VNFM 1012发起新的VNF 103的实例化等生命周期管理操作。
运营支持系统和业务支持系统(Operations Support System and Business Support System，OSS/BSS)105，支持各种端到端电信业务。OSS支持的管理功能包括：网络配置，业务提供，故障管理等。BSS处理订单，付费，收入等，支持产品管理，订单管理，收益管理及客户管理。
在NFV系统中，虚拟化的NS可以是一个IP多媒体子系统(IP multimedia subsystem，IMS)网络服务，或者，是一个下一代移动核心网络(Evolved Packet Core，EPC)网络服务等。一个NS中可以包含若干个VNF。发起实例化VNF请求的一方可以称为虚拟化业务请求方。接收实例化VNF请求，并根据实例化VNF请求部署VNF的一方可以称为虚拟化业务提供方。在对一个NS进行虚拟化部署时，虚拟化业务提供方需要从虚拟化业务请求方获取该业务的描述信息，即网络服务模板(Network Service descriptor，NSD)。NSD主要描述了该业务的拓扑结构信息以及包含的每个VNF的描述信息，即VNFD。在拓扑结构信息中，可以使用虚拟化连接模板(virtual link descriptor，VLD)来描述VNF之间的连接。虚拟化业务请求方可以为NFVO或发送者(sender)。发送者具体可以为OSS/BSS。
图2A为本申请提供的一种VNFD的结构示意图。图2B是根据上述VNFD部署后得到的VNF的结构示意图。图2C是包含若干个VNF的NS_1的结构示意图。
如图2A所示，VNFD包含虚拟部署单元(Virtualisation Deployment Unit，VDU)1、VDU2、连接点(connection point，CP)_A、CP_B、虚拟连接(virtual link，VL)等信息。VDU代表需要部署到虚拟机上的应用软件。CP代表VNF的连接信息，比如可以是虚拟网卡信息，可以采用IP地址或MAC地址来表示。VL是VNF内连接多个VDU的虚拟连接，可以用连接类型，带宽等信息来表示。
如图2B所示，VNFM使用上述VNFD进行部署，部署后得到的VNF包括虚拟化网络功能组件(virtualized network function component，VNFC)1、VNFC2、CP_A实例、CP_B实例和VL实例。其中，VNFD中的VDU1部署后生成VNFC1，VNFD中的VDU2部署后生成VNFC2。
如图2C所示，NS_1包括VNF_1、VNF_2、VNF_3、VNF_4和VNF_5。其中，VNF_1和VNF_2分别通过VL_1实例与VNF_3连接。VNF_3通过VL_2实例与服务接入点(Service access point，SAP)连接。SAP也可以称为服务连接点。SAP是嵌套的NS_2的对外连接点。VNF_4与SAP连接。VNF_4可以通过SAP与嵌套的NS_2外界的VNF进行通信。VNF_4通过VL_3实例与VNF_5连接。VNF_4和VNF_5属于嵌套NS_2内的VNF。全局NFVO对NS_1进行生命周期管理。局部NFVO对嵌套的NS_2进行生命周期管理。全局NFVO与局部NFVO之间设置有通信接口，例如or-or接口。
当局部NFVO对嵌套的NS_2进行生命周期管理，比如弹性扩容嵌套NS_2，终止嵌套NS_2运行时，局部NFVO向全局NFVO发送授权请求，全局NFVO授权局部NFVO对嵌套的NS_2进行生命周期管理后，局部NFVO对嵌套的NS_2进行生命周期管理。
为了解决全局NFVO如何确定是否授权局部NFVO对嵌套NS的操作的问题，本申请实施例 提供了一种网络业务的生命周期管理的授权方法，该方法包括：第一NFVO设备接收来自第二NFVO设备的授权请求，授权请求用于请求授权对第二NS进行第一操作，第一操作为第二NFVO设备对第二NS进行生命周期管理的操作。若第一NFVO设备确定第一NS的资源满足对第二NS进行第一操作，向第二NFVO设备发送授权响应，以授权对第二NS进行第一操作。第二NFVO设备接收来自第一NFVO设备的授权响应后，对第二NS进行第一操作。授权响应用于指示对第二NS进行第一操作。从而，在第二NFVO设备对第二NS进行生命周期管理的情况下，解决了第二NFVO设备与第一NFVO设备之间的管理协商问题，降低了第二NFVO设备对第二NS进行生命周期管理时对第一NS的影响。
在本文中，假设第一NFVO设备用于实现全局NFVO的功能，例如，第一NFVO设备用于对第一NS进行生命周期管理。第二NFVO设备用于实现局部NFVO的功能，例如，第二NFVO设备用于对第二NS进行生命周期管理。第一NFVO设备与第二NFVO设备连接。第二NS嵌套于第一NS内。示例的，如图2C所示，第一NS可以是NS_1。第二NS可以是NS_2。
接下来，结合附图对本申请实施例的实施方式进行详细描述。
图3为本申请实施例提供的一种网络业务的生命周期管理的授权方法的流程图。如图3所示，该方法可以包括：
S301、第二NFVO设备向第一NFVO设备发送授权请求，请求授权对第二NS进行第一操作。
可理解的，第一操作为第二NFVO设备对第二NS进行生命周期管理。
在一些实施例中，第一操作可以是第二NFVO设备对第二NS的扩容操作。例如，由于使用第二NS提供的服务的用户增多，第二NS提供的服务的资源无法承载如此多的用户，可能导致网络拥塞，因此，可以扩大第二NS的承载用户容量，避免网络拥塞。
在另一些实施例中，第一操作可以是第二NFVO设备对第二NS的删除操作。例如，由于使用第二NS提供的服务的用户减少了很多或其他无需提供第二NS提供的服务等原因，因此，第二NFVO设备可以删除第二NS，释放部署第二NS所使用的资源，减少了第二NFVO设备所管理的资源浪费，提高了资源的利用率。
可选的，第二NFVO设备可以通过or-or接口向第一NFVO设备发送授权请求。
S302、第一NFVO设备接收来自第二NFVO设备的授权请求。
授权请求用于请求授权对第二NS进行第一操作，第一操作为第二NFVO设备对第二NS进行生命周期管理的操作。关于第一操作的具体解释可以参考S301的阐述，不予赘述。可选的，第二NFVO设备可以通过or-or接口向第一NFVO设备发送授权请求。
S303、第一NFVO设备判断第一NS的资源是否满足对第二NS进行第一操作。
由于第二NS是嵌套在第一NS内的，所以第二NS与第一NS具有关联关系。如果第二NFVO设备对第二NS进行第一操作，第一NS可能会影响到第二NFVO设备对第二NS进行第一操作是否成功，因此，第一NFVO设备判断第一NS的资源是否满足对第二NS进行第一操作。
若第一NFVO设备确定第一NS的资源满足对第二NS进行第一操作，执行S304；若第一NFVO设备确定第一NS的资源不满足对第二NS进行第一操作，执行S307。
S304、第一NFVO设备向第二NFVO设备发送授权响应，以授权对第二NS进行第一操作。
授权响应用于指示对第二NS进行第一操作。
S305、第二NFVO设备接收来自第一NFVO设备的授权响应。
S306、第二NFVO设备对第二NS进行第一操作。
例如，第二NFVO设备对第二NS进行扩容操作。又例如，第二NFVO设备对第二NS进行删除操作。
S307、第一NFVO设备向第二NFVO设备发送失败响应，不允许对第二NS进行第一操作。
可选的，失败响应还可以包括失败原因。例如，如果第二NFVO设备对第二NS进行扩容操作，扩大第二NS的容量后，第二NS上的数据流量可能增加，由于第二NS是嵌套在第一NS内的，第二NS与第一NS具有关联关系，因此第一NS内与第二NS连接的网络上的数据流量也会增加。若增加的数据流量超过第一NS内与第二NS连接的网络上自身的处理能力，导致对第二NS进行扩容失败。因此，第一NFVO设备不允许对第二NS进行扩容操作，失败原因可以是第一NS不支持对第二NS进行扩容操作。
又例如，如果第二NFVO设备对第二NS进行删除操作，第一NS与第二NS还存在依赖关系，导致对第二NS进行删除失败。因此，第一NFVO设备不允许对第二NS进行删除操作，失败原因可以是第一NS不支持对第二NS进行删除操作。
S308、第二NFVO设备接收来自第一NFVO设备的失败响应。
失败响应用于指示不允许对第二NS进行第一操作。例如，第二NFVO设备不对第二NS进行扩容操作。又例如，第二NFVO设备不对第二NS进行删除操作。可选的，第二NFVO设备确定不对第二NS进行第一操作的情况下，还可以决策是否对第二NS进行其他生命周期管理。
在第一种可能的实现方式中，第一操作可以为第二NFVO设备对第二NS的扩容操作。若第二NFVO设备对第二NS进行了扩容操作，就会增加第二NS处理的数据的数据量，提高了第二NS对外的数据流量，由于第二NS是嵌套在第一NS内的，所以第二NS与第一NS具有关联关系，因此，第一NFVO设备可以通过判断第一NS和第二NS内的相关的数据流量来判断第一NS的资源是否满足对第二NS进行扩容操作。如图4所示，S303可以包括以下详细步骤S3031和3032。
S3031、第一NFVO设备获取第一数据和第二数据。
其中，第一数据为第一NS内与第二NS相关的数据流量。第二数据为对第二NS进行扩容操作后的预测数据流量。
在一些实施例中，第一NFVO设备可以采集与第二NS内的SAP相连接的网络的数据流量，作为第一数据。例如，如图2C所示，NS_2中的SAP与NS_1中的VL_2实例连接，VL_2实例可以作为与NS_2内的SAP相连接的网络，第一NFVO设备可以采集VL_2实例上的数据流量，作为第一数据。可选的，这里的“网络”也可以称为虚拟网络或虚拟连接。
在一种可能的设计中，第二数据可以是从第一NFVO设备被动接收的。例如第一NFVO设备接收到的来自第二NFVO设备的授权请求中包括第二数据。第一NFVO设备可以从授权请求中获取第二数据。第二数据为对第二NS进行扩容操作后的与第一NS连接的SAP上的预测数据流量。例如，如图2C所示，第二数据可以是与NS_1中的VL_2实例相连接的SAP上的预测数据流量。
在另一种可能的设计中，第二数据可以是从第一NFVO设备主动获取的。例如，授权请求包括第一地址，第一地址用于指示第二NFVO设备存储第二数据的地址。如图5所示，第一NFVO设备可以根据第一地址从第二NFVO设备获取第二数据。
S501、第一NFVO设备向第二NFVO设备发送第一获取请求，第一获取请求包括第一地址。
第一获取请求用于请求第二NFVO设备反馈第二数据。
S502、第二NFVO设备接收来自第一NFVO设备的第一获取请求。
S503、第二NFVO设备向第一NFVO设备发送的第二数据。
第二NFVO设备接收到第一获取请求后，根据第一地址指示的存储位置获取第二数据，并向第一NFVO设备反馈第二数据。
S504、第一NFVO设备接收来自第二NFVO设备的第二数据。
在第一NFVO设备获取到第一数据和第二数据后，执行S3032。
S3032、第一NFVO设备判断第一数据是否大于第二数据。
若第一数据大于第二数据，表示第一NS内与第二NS相连接的网络的带宽满足对第二NS进行扩容操作后的需求，第一NFVO设备确定第一NS的资源满足对第二NS进行扩容操作，执行S304；若第一数据小于或等于第二数据，表示第一NS内与第二NS相连接的网络的带宽不满足对第二NS进行扩容操作后的需求，第一NFVO设备确定第一NS的资源不满足对第二NS进行扩容操作，执行S307。
例如，假设VL_2实例上的数据流量为1吉字节(Gigabyte，GB)，SAP上的预测数据流量为400千字节(Kilobyte，KB)。400KB小于1GB，因此，第一NFVO设备确定第一NS的资源满足对第二NS进行扩容操作。
又例如，假设VL_2实例上的数据流量为600KB，SAP上的预测数据流量为1GB。600KB小于1GB，因此，第一NFVO设备确定第一NS的资源不满足对第二NS进行扩容操作。
在另一些实施例中，第一NFVO设备还可以指示第二NFVO设备上报扩容操作所需的信息。如图6所示，在第二NFVO设备向第一NFVO设备发送授权请求，即S301之前，该方法还包括以下步骤。
S601、第一NFVO设备向第二NFVO设备发送第一授权策略，指示采集第二NS的数据流量。
可选的，第一授权策略用于指示在第二NFVO设备确定对第二NS进行扩容操作时采集第二NS对外的数据流量。例如，如图2C所示，第二NFVO设备可以采集与NS_1中的VL_2实例相连接的SAP上的数据流量。
可选的，第一授权策略用于指示在第二NFVO设备确定对第二NS进行扩容操作时确定第二NS的预测数据流量。
S602、第二NFVO设备接收来自第一NFVO设备的第一授权策略。
在一种可能的实现方式中，在第二NFVO设备向第一NFVO设备发送授权请求之前，第二NFVO设备还可以执行以下S603和S604。
S603、第二NFVO设备采集第二NS的数据流量。
在一些实施例中，第二NFVO设备可以向VIM发送请求消息，请求VIM反馈第二NS对外的数据流量。可选的，VIM可以通过VNFM向第二NFVO设备反馈第二NS对外的数据流量。
S604、第二NFVO设备根据第二NS的数据流量确定第二数据。
在一些实施例中，第二NFVO设备可以采用人工智能(Artificial Intelligence)技术或数据分析技术(如：大数据分析技术)分析第二NS对外的数据流量得到对第二NS进行扩容操作后的第二NS的预测数据流量。
可选的，第二NFVO设备也可以向第一NFVO设备上报第二NS对外的数据流量，第一NFVO设备根据第二NS对外的数据流量确定第二NS的预测数据流量。
可选的，若第一NFVO设备确定第一NS的资源不满足对第二NS进行扩容操作，第一NFVO 设备也可以对第一NS进行扩容操作，使得第一NS的资源满足对第二NS进行扩容操作。示例的，如图6所示，所述方法还包括S605。
S605、第一NFVO设备对第一NS内与第二NS相连接的虚连接进行第一操作。
可选的，第一NFVO设备可以根据第二NS的预测数据流量对第一NS内与第二NS相连接的虚连接进行扩容操作。
例如，假设VL_2实例上的数据流量为600KB，SAP上的预测数据流量为1GB。600KB小于1GB，因此，第一NFVO设备确定第一NS的资源不满足对第二NS进行扩容操作。第一NFVO设备可以对VL_2实例进行扩容操作，使得VL_2实例上的数据流量为1GB，以便于VL_2实例支持对第二NS的扩容操作。
可选的，若第一操作是第二NFVO设备对第二NS的缩容操作。第一NFVO设备可以对第一NS内与第二NS相连接的虚连接进行缩容操作，从而，减少第一NFVO设备所管理的资源浪费。
从而，在第二NFVO设备对第二NS进行扩容操作的情况下，解决了第二NFVO设备与第一NFVO设备之间的管理协商问题，降低了第二NFVO设备对第二NS进行扩容操作时对第一NS的影响。
在第二种可能的实现方式中，第一操作为第二NFVO设备对第二NS的删除操作。由于第二NS是嵌套在第一NS内的，所以第二NS与第一NS具有关联关系。若第二NFVO设备对第二NS进行了删除操作，第二NS无法提供服务。例如，第二NS和第一NS之间还需要进行数据传输，如果第二NFVO设备删除了第二NS，第二NS和第一NS之间无法进行数据传输。因此，第一NFVO设备可以通过判断第一NS和第二NS是否有依赖关系来判断第一NS的资源是否满足对第二NS进行删除操作。如图7所示，S303可以包括以下详细步骤S3033。
S3033、第一NFVO设备判断第一NS与第二NS是否有依赖关系。
若第一NS与第二NS无依赖关系(如：第一NS与第二NS之间无数据传输)，第一NFVO设备确定第一NS的资源满足对第二NS进行第一操作，执行S304。若第一NS与第二NS有依赖关系(如：第一NS与第二NS之间有数据传输)，第一NFVO设备确定第一NS的资源不满足对第二NS进行第一操作，执行S307。
可选的，若第一NS与第二NS有依赖关系，第一NFVO设备确定第一NS的资源不满足对第二NS进行第一操作，第一NFVO设备可以部署第三NS，使第三NS提供第二NS的服务，第三NS与第一NS建立连接，第三NS与第一NS进行数据传输。如图8所示，所述方法还包括以下步骤。
S801、第一NFVO设备判断在第一时长内是否成功部署第三NS，第三NS用于提供第二NS的服务。
可理解的，第一时长为第二NS可以继续提供服务的预测时长。在一些实施例中，第一NFVO设备可以在第一时长内部署第三NS，若在第一时长内成功部署第三NS，表示第三NS可以替代第二NS继续提供服务，如第三NS与第一NS进行数据传输，则第一NFVO设备向第二NFVO设备发送授权响应，即执行S304，第二NFVO设备删除第二NS；若在第一时长内部署第三NS失败，表示没有其他NS可以替代第二NS继续提供服务，第一NFVO设备向第二NFVO设备发送失败响应，即执行S307，不允许第二NFVO设备删除第二NS。
在一种可能的设计中，第一时长可以是从第一NFVO设备被动接收的。例如第一NFVO设备接收到的来自第二NFVO设备的授权请求中包括包括第一时长。第一NFVO设备可以从授权 请求中获取第一时长。例如，如图2C所示，第一时长可以是NS_2可以继续提供服务的预测时长。
在另一种可能的设计中，第一时长可以是从第一NFVO设备主动获取的。例如，授权请求包括第二地址，第二地址用于指示第二NFVO设备存储第一时长的地址。如图9所示，在第一NFVO设备判断在第一时长内是否成功部署第三NS，即S801之前，第一NFVO设备可以根据第二地址从第二NFVO设备获取第一时长。
S901、第一NFVO设备向第二NFVO设备发送第二获取请求，第二获取请求包括第二地址。
第二获取请求用于请求第二NFVO设备反馈第一时长。
S902、第二NFVO设备接收来自第一NFVO设备的第二获取请求。
S903、第二NFVO设备向第一NFVO设备发送的第一时长。
第二NFVO设备接收到第二获取请求后，根据第二地址指示的存储位置获取第一时长，并向第一NFVO设备反馈第一时长。
S904、第一NFVO设备接收来自第二NFVO设备的第一时长。
在另一些实施例中，第一NFVO设备还可以指示第二NFVO设备上报删除操作所需的信息。如图10所示，在第二NFVO设备向第一NFVO设备发送授权请求，即S301之前，该方法还包括以下步骤。
S1001、第一NFVO设备向第二NFVO设备发送第二授权策略，指示第二NFVO设备预测第一时长。
可选的，第二授权策略用于指示在第二NFVO设备确定对第二NS进行删除操作后预测第一时长。例如，如图2C所示，第二NFVO设备可以预测NS_2可以继续提供服务的时长。
可选的，第二授权策略还可以包括第二NFVO设备确定对第二NS进行删除操作的原因。第二NFVO设备确定对第二NS的删除操作后，向第一NFVO设备发送的授权请求中可以携带对第二NS进行删除操作的原因。
S1002、第二NFVO设备接收来自第一NFVO设备的第二授权策略。
在一种可能的实现方式中，在第二NFVO设备向第一NFVO设备发送授权请求之前，第二NFVO设备还可以执行以下S1003。
S1003、第二NFVO设备确定第一时长。
在一些实施例中，第二NFVO设备确定对第二NS进行删除操作后，确定第一时长。在一些实施例中，第二NFVO设备可以向VIM发送请求消息，请求VIM反馈第一时长。可选的，VIM可以通过VNFM向第二NFVO设备反馈第一时长。
从而，在第二NFVO设备对第二NS进行删除操作的情况下，解决了第二NFVO设备与第一NFVO设备之间的管理协商问题，降低了第二NFVO设备对第二NS进行删除操作时对第一NS的影响。
可以理解的是，为了实现上述实施例中功能，第一NFVO设备和第二NFVO设备包括了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本申请中所公开的实施例描述的各示例的单元及方法步骤，本申请能够以硬件或硬件和计算机软件相结合的形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用场景和设计约束条件。
图11和图12为本申请的实施例提供的可能的通信装置的结构示意图。这些通信装置可 以用于实现上述方法实施例中第一NFVO设备或第二NFVO设备的功能，因此也能实现上述方法实施例所具备的有益效果。在本申请的实施例中，该通信装置可以是如图2C所示的全局NFVO或局部NFVO，也可以是应用于第一NFVO设备或第二NFVO设备的模块(如芯片)。
如图11所示，通信装置1100包括处理单元1110和收发单元1120。通信装置1100用于实现上述图3至图10中任一个所示的方法实施例中第一NFVO设备或第二NFVO设备的功能。
当通信装置1100用于实现图3所示的方法实施例中第一NFVO设备的功能时：收发单元1120用于执行S302、S304和S307；处理单元1110用于执行S303。
当通信装置1100用于实现图3所示的方法实施例中第二NFVO设备的功能时：收发单元1120用于执行S301、S305和S308；处理单元1110用于执行S306。
当通信装置1100用于实现图4所示的方法实施例中第一NFVO设备的功能时：收发单元1120用于执行S302、S304和S307；处理单元1110用于执行S3031和S3032。
当通信装置1100用于实现图4所示的方法实施例中第二NFVO设备的功能时：收发单元1120用于执行S301、S305和S308；处理单元1110用于执行S306。
当通信装置1100用于实现图5所示的方法实施例中第一NFVO设备的功能时：收发单元1120用于执行S302、S304、S307、S501和S504；处理单元1110用于执行S3031和S3032。
当通信装置1100用于实现图5所示的方法实施例中第二NFVO设备的功能时：收发单元1120用于执行S301、S305、S308、S502和S503；处理单元1110用于执行S306。
当通信装置1100用于实现图6所示的方法实施例中第一NFVO设备的功能时：收发单元1120用于执行S302、S304、S307、S501、S504和S601；处理单元1110用于执行S3031、S3032和S605。
当通信装置1100用于实现图6所示的方法实施例中第二NFVO设备的功能时：收发单元1120用于执行S301、S305、S308、S502、S503和S602；处理单元1110用于执行S306、S603和S604。
当通信装置1100用于实现图7所示的方法实施例中第一NFVO设备的功能时：收发单元1120用于执行S302、S304和S307；处理单元1110用于执行S3033。
当通信装置1100用于实现图7所示的方法实施例中第二NFVO设备的功能时：收发单元1120用于执行S301、S305和S308；处理单元1110用于执行S306。
当通信装置1100用于实现图8所示的方法实施例中第一NFVO设备的功能时：收发单元1120用于执行S302、S304和S307；处理单元1110用于执行S3033和S801。
当通信装置1100用于实现图8所示的方法实施例中第二NFVO设备的功能时：收发单元1120用于执行S301、S305和S308；处理单元1110用于执行S306。
当通信装置1100用于实现图9所示的方法实施例中第一NFVO设备的功能时：收发单元1120用于执行S302、S304、S307、S901和S904；处理单元1110用于执行S3033和S801。
当通信装置1100用于实现图9所示的方法实施例中第二NFVO设备的功能时：收发单元1120用于执行S301、S305、S308、S902和S903；处理单元1110用于执行S306。
当通信装置1100用于实现图10所示的方法实施例中第一NFVO设备的功能时：收发单元1120用于执行S302、S304、S307、S901、S904和S1001；处理单元1110用于执行S3033和S801。
当通信装置1100用于实现图10所示的方法实施例中第二NFVO设备的功能时：收发单元 1120用于执行S301、S305、S308、S902、S903和S1002；处理单元1110用于执行S306和S1003。
有关上述处理单元1110和收发单元1120更详细的描述可以直接参考图图3至图10所示的方法实施例中相关描述直接得到，这里不加赘述。
如图12所示，通信装置1200包括处理器1210和接口电路1220。处理器1210和接口电路1220之间相互耦合。可以理解的是，接口电路1220可以为收发器或输入输出接口。可选的，通信装置1200还可以包括存储器1230，用于存储处理器1210执行的指令或存储处理器1210运行指令所需要的输入数据或存储处理器1210运行指令后产生的数据。
当通信装置1200用于实现图3至图10所示的方法时，处理器1210用于执行上述处理单元1110的功能，接口电路1220用于执行上述收发单元1120的功能。
当上述通信装置为应用于终端设备的芯片时，该终端设备芯片实现上述方法实施例中终端设备的功能。该终端设备芯片从终端设备中的其它模块(如射频模块或天线)接收信息，该信息是网络设备发送给终端设备的；或者，该终端设备芯片向终端设备中的其它模块(如射频模块或天线)发送信息，该信息是终端设备发送给网络设备的。
当上述通信装置为应用于网络设备的芯片时，该网络设备芯片实现上述方法实施例中网络设备的功能。该网络设备芯片从网络设备中的其它模块(如射频模块或天线)接收信息，该信息是终端设备发送给网络设备的；或者，该网络设备芯片向网络设备中的其它模块(如射频模块或天线)发送信息，该信息是网络设备发送给终端设备的。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(Central Processing Unit，CPU)，还可以是其它通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
本申请的实施例中的方法步骤可以通过硬件的方式来实现，也可以由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于网络设备或终端设备中。当然，处理器和存储介质也可以作为分立组件存在于网络设备或终端设备中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序或指令。在计算机上加载和执行所述计算机程序或指令时，全部或部分地执行本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、用户设备或者其它可编程装置。所述计算机程序或指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输， 例如，所述计算机程序或指令可以从一个网站站点、计算机、服务器或数据中心通过有线或无线方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，例如，软盘、硬盘、磁带；也可以是光介质，例如，数字视频光盘(digital video disc，DVD)；还可以是半导体介质，例如，固态硬盘(solid state drive，SSD)。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A,B可以是单数或者复数。在本申请的文字描述中，字符“/”，一般表示前后关联对象是一种“或”的关系；在本申请的公式中，字符“/”，表示前后关联对象是一种“相除”的关系。
可以理解的是，在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。

Claims (20)

  1. 一种网络业务NS的生命周期管理的授权方法，其特征在于，包括：
    第一网络功能虚拟化编排器NFVO设备接收来自第二NFVO设备的授权请求，所述授权请求用于请求授权对第二NS进行第一操作，所述第一操作为所述第二NFVO设备对所述第二NS进行生命周期管理的操作；
    所述第一NFVO设备判断第一NS的资源是否满足对所述第二NS进行所述第一操作；
    若所述第一NFVO设备确定所述第一NS的资源满足对所述第二NS进行所述第一操作，向所述第二NFVO设备发送授权响应，以授权对所述第二NS进行所述第一操作。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    若所述第一NFVO设备确定所述第一NS的资源不满足对所述第二NS进行所述第一操作，向所述第二NFVO设备发送失败响应，所述失败响应用于指示不允许对所述第二NS进行所述第一操作。
  3. 根据权利要求2所述的方法，其特征在于，所述第一操作为扩容操作，所述第一NFVO设备判断所述第一NS的资源是否满足对所述第二NS进行第一操作，包括：
    所述第一NFVO设备获取第一数据和第二数据，所述第一数据为所述第一NS内与所述第二NS相关的数据流量，所述第二数据为对所述第二NS进行所述第一操作后的预测数据流量；
    所述第一NFVO设备判断所述第一数据是否大于所述第二数据；
    若所述第一数据大于所述第二数据，所述第一NFVO设备确定所述第一NS的资源满足对所述第二NS进行第一操作；
    若所述第一数据小于或等于所述第二数据，所述第一NFVO设备确定所述第一NS的资源不满足对所述第二NS进行第一操作。
  4. 根据权利要求3所述的方法，其特征在于，所述授权请求包括所述第二数据。
  5. 根据权利要求3所述的方法，其特征在于，所述授权请求包括第一地址，所述第一地址用于指示存储所述第二数据的地址，所述第一NFVO设备获取所述第二数据，包括：
    所述第一NFVO设备向所述第二NFVO设备发送第一获取请求，所述第一获取请求用于请求所述第二NFVO设备反馈所述第二数据，所述第一获取请求包括所述第一地址；
    所述第一NFVO设备接收来自所述第二NFVO设备的所述第二数据。
  6. 根据权利要求2-5中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一NFVO设备对所述第一NS内与所述第二NS相连接的虚连接进行所述第一操作。
  7. 根据权利要求1-6中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一NFVO设备向所述第二NFVO设备发送第一授权策略，所述第一授权策略用于指示采集所述第二NS的数据流量。
  8. 根据权利要求2所述的方法，其特征在于，所述第一操作为删除操作，所述第一NFVO设备判断所述第一NS的资源是否满足对所述第二NS进行第一操作，包括：
    所述第一NFVO设备判断所述第一NS与所述第二NS是否有依赖关系；
    若所述第一NS与所述第二NS无依赖关系，所述第一NFVO设备确定所述第一NS的资源满足对所述第二NS进行第一操作。
  9. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    若所述第一NS与所述第二NS有依赖关系，所述第一NFVO设备确定所述第一NS的资源 不满足对所述第二NS进行第一操作。
  10. 根据权利要求9所述的方法，其特征在于，若所述第一NS与所述第二NS有依赖关系，所述方法还包括：
    所述第一NFVO设备判断在第一时长内是否成功部署第三NS，所述第三NS用于提供所述第二NS的服务，所述第一时长为所述第二NS提供服务的预测时长；
    所述第一NFVO设备向所述第二NFVO设备发送授权响应，包括：
    若在第一时长内成功部署所述第三NS，所述第一NFVO设备向所述第二NFVO设备发送授权响应；
    所述第一NFVO设备向所述第二NFVO设备发送失败响应，包括：
    若在第一时长内部署所述第三NS失败，所述第一NFVO设备向所述第二NFVO设备发送失败响应。
  11. 一种网络业务的生命周期管理的授权方法，其特征在于，所述方法包括：
    第二NFVO设备向第一NFVO设备发送授权请求，所述授权请求用于请求授权对第二NS进行第一操作，所述第一操作为所述第二NFVO设备对所述第二NS进行生命周期管理的操作；
    所述第二NFVO设备接收来自所述第一NFVO设备的授权响应，所述授权响应用于指示对所述第二NS进行所述第一操作；
    所述第二NFVO设备对所述第二NS进行所述第一操作。
  12. 根据权利要求11所述的方法，其特征在于，所述方法还包括：
    所述第二NFVO设备接收来自所述第一NFVO设备的失败响应，所述失败响应用于指示不允许对所述第二NS进行所述第一操作。
  13. 根据权利要求11或12所述的方法，其特征在于，所述第一操作为扩容操作，所述第二NFVO设备向所述第一NFVO设备发送授权请求之前，所述方法还包括：
    所述第二NFVO设备采集所述第二NS的数据流量；
    所述第二NFVO设备根据所述第二NS的数据流量确定第二数据，所述第二数据为对所述第二NS进行所述第一操作后的预测数据流量。
  14. 根据权利要求13所述的方法，其特征在于，所述授权请求包括所述第二数据。
  15. 根据权利要求13所述的方法，其特征在于，所述授权请求包括第一地址，所述第一地址用于指示存储所述第二数据的地址，所述方法还包括：
    所述第二NFVO设备接收来自所述第一NFVO设备的第一获取请求，所述第一获取请求用于请求所述第二NFVO设备反馈所述第二数据，所述第一获取请求包括所述第一地址；
    所述第二NFVO设备向所述第一NFVO设备发送的所述第二数据。
  16. 根据权利要求11-15中任一项所述的方法，其特征在于，所述方法还包括：
    所述第二NFVO设备接收来自所述第一NFVO设备的第一授权策略，所述第一授权策略用于指示采集所述第二NS的数据流量。
  17. 根据权利要求11或12所述的方法，其特征在于，所述第一操作为删除操作，所述第二NFVO设备向所述第一NFVO设备发送授权请求之前，所述方法还包括：
    所述第二NFVO设备确定第一时长，所述第一时长为所述第二NS提供服务的预测时长。
  18. 一种通信装置，其特征在于，包括：至少一个处理器、存储器、总线和接口电路，其中，所述存储器用于存储计算机程序，使得所述计算机程序被所述至少一个处理器执行时实现如权利要求1至10中任一项所述的方法，或者实现如权利要求11至17中任一项所述的 方法。
  19. 一种计算机可读存储介质，其特征在于，包括：计算机软件指令；
    当所述计算机软件指令在通信装置或内置在通信装置的芯片中运行时，使得所述通信装置执行如权利要求1至10中任一项所述的方法，或者实现如权利要求11至17中任一项所述的方法。
  20. 一种通信系统，其特征在于，包括第一网络功能虚拟化编排器NFVO设备和第二NFVO设备，所述第一NFVO设备配置于执行权利要求1至10中任一项所述的方法。
PCT/CN2020/137364 2019-12-23 2020-12-17 网络业务的生命周期管理的授权方法及装置 WO2021129520A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911342710.1 2019-12-23
CN201911342710.1A CN113098705B (zh) 2019-12-23 2019-12-23 网络业务的生命周期管理的授权方法及装置

Publications (1)

Publication Number Publication Date
WO2021129520A1 true WO2021129520A1 (zh) 2021-07-01

Family

ID=76573672

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/137364 WO2021129520A1 (zh) 2019-12-23 2020-12-17 网络业务的生命周期管理的授权方法及装置

Country Status (2)

Country Link
CN (1) CN113098705B (zh)
WO (1) WO2021129520A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107135192A (zh) * 2016-02-26 2017-09-05 中国移动通信集团公司 部署vnf的资源授权方法、vnfm和nfvo
WO2018006401A1 (en) * 2016-07-08 2018-01-11 Telefonaktiebolaget Lm Ericsson (Publ) Methods and devices for selective network service deployment in the cloud environment
CN108885564A (zh) * 2016-02-08 2018-11-23 诺基亚通信公司 网络虚拟化场景中的资源放置控制

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10116571B1 (en) * 2015-09-18 2018-10-30 Sprint Communications Company L.P. Network Function Virtualization (NFV) Management and Orchestration (MANO) with Application Layer Traffic Optimization (ALTO)
EP3430509B1 (en) * 2016-03-15 2022-06-22 Nokia Solutions and Networks Oy Conflict resolution in network virtualization scenarios
CN108156095B (zh) * 2016-12-02 2020-07-14 中兴通讯股份有限公司 资源确定方法及装置、nfvo
CN108347343B (zh) * 2017-01-25 2020-07-14 华为技术有限公司 一种策略管理方法、装置和系统
CN109587024B (zh) * 2017-09-29 2020-12-22 华为技术有限公司 一种资源处理的方法以及相关装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108885564A (zh) * 2016-02-08 2018-11-23 诺基亚通信公司 网络虚拟化场景中的资源放置控制
CN107135192A (zh) * 2016-02-26 2017-09-05 中国移动通信集团公司 部署vnf的资源授权方法、vnfm和nfvo
WO2018006401A1 (en) * 2016-07-08 2018-01-11 Telefonaktiebolaget Lm Ericsson (Publ) Methods and devices for selective network service deployment in the cloud environment

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NIE WEILING, WANG LIQIU: "The key strategy of MANO resource scheduling and deployment in the next generation network", TELECOMMUNICATIONS TECHNOLOGY, 1 January 2017 (2017-01-01), pages 67 - 70, XP055824624, DOI: 10.3969/j.issn.1000-1247.2017.05.020 *

Also Published As

Publication number Publication date
CN113098705A (zh) 2021-07-09
CN113098705B (zh) 2022-08-26

Similar Documents

Publication Publication Date Title
US11429408B2 (en) System and method for network function virtualization resource management
WO2018024059A1 (zh) 一种虚拟化网络中业务部署的方法和装置
CN107209710B (zh) 节点系统、服务器设备、缩放控制方法和程序
US20180210752A1 (en) Accelerator virtualization method and apparatus, and centralized resource manager
US20220075666A1 (en) Containerized vnf deployment method and related device
WO2017080391A1 (zh) 一种网络服务部署方法和装置
US11871280B2 (en) VNF instantiation method, NFVO, VIM, VNFM, and system
WO2019179301A1 (zh) 一种管理虚拟资源的方法及装置
US11301284B2 (en) Method for managing VNF instantiation and device
WO2021109750A1 (zh) 节点管理方法、装置、设备、存储介质和系统
WO2019047835A1 (zh) 虚拟网络功能的实例化方法
US20210326306A1 (en) Method and apparatus for deploying virtualised network function
WO2021143183A1 (zh) 一种部署虚拟机的方法及相关装置
CN112448833A (zh) 一种多管理域的通信方法和装置
CN113342456A (zh) 一种连接方法、装置、设备和存储介质
WO2021022947A1 (zh) 一种部署虚拟机的方法及相关装置
WO2021129520A1 (zh) 网络业务的生命周期管理的授权方法及装置
WO2020249080A1 (zh) 一种虚拟网络功能vnf部署方法及装置
WO2021004320A1 (zh) 服务资源许可管理方法和相关设备
WO2020077585A1 (zh) Vnf服务实例化方法及装置
US20230409371A1 (en) Method for creating network service ns and related apparatus
WO2018120222A1 (zh) 一种管理vnffg的方法、装置和系统
WO2022141293A1 (zh) 一种弹性伸缩的方法及装置
WO2024114645A1 (zh) 一种虚拟化网络功能vnf的实例化方法及装置
US20230327959A1 (en) Method for establishing network connection and apparatus

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20904912

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20904912

Country of ref document: EP

Kind code of ref document: A1