WO2022183796A1 - 一种创建网络服务ns的方法及相关装置 - Google Patents

一种创建网络服务ns的方法及相关装置 Download PDF

Info

Publication number
WO2022183796A1
WO2022183796A1 PCT/CN2021/133873 CN2021133873W WO2022183796A1 WO 2022183796 A1 WO2022183796 A1 WO 2022183796A1 CN 2021133873 W CN2021133873 W CN 2021133873W WO 2022183796 A1 WO2022183796 A1 WO 2022183796A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
management device
nsd
nfvo
vpc
Prior art date
Application number
PCT/CN2021/133873
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 WO2022183796A1 publication Critical patent/WO2022183796A1/zh
Priority to US18/240,433 priority Critical patent/US20230409371A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45562—Creating, deleting, cloning virtual machine instances
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances

Definitions

  • the present application relates to the field of network function virtualization, and in particular, to a method and related device for creating a network service (NS).
  • NS network service
  • Network function virtualization (NFV) technology uses virtualization technology to virtualize the functions of dedicated devices in traditional networks into independent applications, which can be flexibly deployed on other devices such as standard-based computing hardware, storage hardware, and network hardware. built on a unified infrastructure platform.
  • the function realized by NFV technology is called network service (NS).
  • the operations support system (OSS) and/or the business support system (BSS) need to describe the network service descriptor (NSD) information Upload to the network functions virtualization orchestrator (NFVO), and let NFVO deploy NS according to the information of NSD.
  • OSS operations support system
  • BSS business support system
  • NSD network service descriptor
  • Embodiments of the present application provide a method and related apparatus for creating a network service NS, which are used to query NFVO for NSD information, and request NFVO to create an NS instance through the information of network service deployment preference in the NSD information.
  • a method for creating a network service NS is provided, and the method can be applied to a management device.
  • the management device sends a network service description NSD query request to the network function virtualization orchestrator NFVO, and then receives NSD information from NFVO. Since the NSD information includes network service deployment preference information, the management device can The information of network service deployment preferences determines the instantiation parameters, thereby requesting NFVO to create an NS instance, without the need for staff to input instantiation parameters through NFVO, thereby reducing the operational complexity of deploying NS instances through management devices, and avoiding the need for manual input instantiation. error caused by the parameter.
  • the management device receives the NSD information list sent by the NFVO, and the NSD information list includes, so that the NSD information can be selected from at least one NSD information in the NSD information list according to actual needs. For example, if the NS required by the OSS/BSS is the next-generation mobile core network (Evolved Packet Core, EPC) service, then the OSS/BSS can search the NSD information list named as the NSD information related to the EPC service (such as EPC or EPC). Next Generation Mobile Core Network Services), then select the information for that NSD.
  • EPC evolved Packet Core
  • the NSD information includes at least one network service deployment preference information, so that the management device can select the network service deployment preference information from the at least one network service deployment preference information according to the needs of the NS instance to be deployed. information. For example, if the main function of the NS instance to be deployed is to store data, if the information of a certain network service deployment preference can realize the function of storing data, then the OSS/BSS can select the information of the network service deployment preference.
  • the information of network service deployment preference includes the identification of the network service deployment preference NSDF, the identification of at least one virtualized network function description VNFD and/or the identification of at least one physical network function description PNFD, so that the management device
  • the instantiation parameters for deploying the NS instance may be acquired according to the identity of the NSDF, the identity of at least one VNFD, and/or the identity of at least one PNFD.
  • the identifier of the at least one VNFD includes the identifier of the first VNFD, so that the management device can obtain the information of the first virtual network function VNF instance according to the identifier of the first VNFD.
  • the request to instantiate the NS includes the identifier of the NSDF, the identifier of the first VNFD, and the information of the first VNF instance, so that when NFVO deploys the NS instance, the NSDF can be determined according to the identifier of the NSDF, and the information of the first VNF instance can be identified according to the identifier of the first VNFD. Determine the multiplexed first VNF instance.
  • the management device sends a VNF query request to NFVO, the VNF query request carries the identifier of the first VNFD, and the VNF query request is used to request information of the VNF instance from NFVO, so that NFVO determines the identifier according to the first VNFD
  • the information of the reusable first VNF instance after the management device receives the information list of the first VNF instance from NFVO, the information list of the first VNF instance includes the information of at least one VNF instance obtained by instantiating the first VNFD , thereby obtaining the information of the reusable first VNF instance in the information list of the first VNF instance.
  • the "reusable first VNF instance” means that the first VNF instance has been instantiated and can be selected and reused by the newly created NS instance.
  • "reuse” refers to using an existing VNF instance as the VNF instance of the NS instance to be created. That is, the to-be-created NS instance reuses the first VNF instance, indicating that the NS instance includes the first VNF instance.
  • the information of the first VNF instance may also include rules, available resources, service capabilities and/or locations of the first VNF instance, etc., and the OSS/BSS may also judge based on one or more of these information. Whether to reuse the first VNF instance in the NS instance.
  • the identifier of at least one VNFD includes the identifier of the second VNFD, and the management device obtains the information of the virtual private cloud VPC, so as to use the VPC to deploy the second VNF instance created according to the second VNFD, and then instantiate the NS request
  • the identification of the second VNFD and the information of the VPC may be further included.
  • the management device sends a VPC query request to NFVO, the VPC query request is used to request VPC information from NFVO, and receives a VPC list from NFVO, the VPC list includes information of at least one VPC, and the management device can actually The VPC information needs to be determined from the VPC list.
  • the name in the information of the VPC is usually named according to the location of the VPC, for example, Shenzhen-Luohu District-Dongxiao Street.
  • the name in the information of the VPC can also be named by its service, such as IMS.
  • the OSS/BSS can send a VPC query request to request that the VPC information list sent by the NFVO to the OSS/BSS includes the information of all available VPCs.
  • the OSS/BSS may send a VPC query request to request that the VPC information list sent by the NFVO to the OSS/BSS carry the information of the available VPCs that satisfy the specific resource or location.
  • the management device obtains the information of the PNF according to the identifier of at least one PNFD, then the instantiated NS request may further include the identifier of the PNFD and the information of the PNF indicated by the identifier of the PNFD, so that the NFVO can ID and PNF information to deploy NS instances.
  • the current NFV system can provide VNF services and PNF services.
  • PNF is a node of physical hardware, and PNF provides services of special equipment.
  • the NFV system may simultaneously provide VNF and/or PNF services for OSS/BSS to choose.
  • the management device after the management device selects the NSD information, if the NSD information indicates that the deployed NS instance includes a VNF instance, the management device needs to select a multiplexed VNF instance or create a VNF instance. If the management device chooses to reuse the VNF instance, the management device may perform the following steps to obtain the information of the reusable VNF instance from the NFVO. If the management device chooses to create a VNF instance, the management device may perform the determination of the available VPCs from the NFVO and subsequent operations. If the NSD information indicates that the deployed NS instance includes a PNF instance, the management device needs to perform the selection and multiplexing of the PNF and subsequent steps.
  • the management device needs to perform the selection of multiplexed VNF instances or the creation of VNF instances and subsequent steps, as well as the determination of available VPCs from NFVO and subsequent steps .
  • the management device sends a PNF query request to the device management system EM.
  • the EM By carrying the PNFD identifier in the PNF query request, it is used to request the NFVO for the information of the PNF associated with the PNFD, then the EM will send a request to the management system.
  • the device sends a PNF list, and the PNF list includes information of at least one PNF associated with the identifier of the PNFD, so that the management device can determine the PNF information from the PNF list according to actual needs. For example, if the management device needs to implement functions, or the city where it is located, the OSS/BSS can determine whether to select the PNF according to the name of the PNF. In some possible implementation manners, the OSS/BSS may also determine whether to select the PNF according to the manufacturer, version and type in the information of the PNF.
  • the management device is an operations support system and a business support system (Operations Support System and Business Support System, OSS/BSS) or core network slice management (core network-Network Slice Subnet Management Function, CN NSSMF), Then the management device can provide NS services for different types of users (users of OSS/BSS or users of CN NSSMF).
  • OSS/BSS Operations Support System and Business Support System
  • CN NSSMF core network-Network Slice Subnet Management Function
  • a method for creating a network service NS is provided, and the method can be applied to a network function virtualization orchestrator (NFV orchestrator, NFVO) device.
  • the NFVO receives a network service description NSD query request sent by the management device, the NSD query request is used to request the NSD information from the NFVO, and then the NFVO sends the NSD information to the management device, and the NSD information includes the network service deployment preference information , the information of the network service deployment preference indicates the user's deployment preference for the network service, and then the NFVO receives the request to instantiate the NS sent by the management device according to the information of the network service deployment preference, and creates the NS instance related to the NSD according to the request of the instantiated NS , since the information of NSD includes the information of network service deployment preferences, the management device can determine the instantiation parameters according to the information of network service deployment preferences, thereby requesting NFVO to create an NS instance, without the need for
  • the NFVO sends the NSD information list to the management device. Since the NSD information list includes at least one NSD information, the management device can determine the NSD information from the NSD information list according to actual needs. For example, if the NS required by the OSS/BSS is the next-generation mobile core network (Evolved Packet Core, EPC) service, then the OSS/BSS can search the NSD information list named as the NSD information related to the EPC service (such as EPC or EPC). Next Generation Mobile Core Network Services), then select the information for that NSD.
  • EPC evolved Packet Core
  • the information of the NSD includes at least one network service deployment preference information, so that the management device can determine the network service deployment preference information from the at least one network service deployment preference information according to the needs of the NS instance to be deployed. information. For example, if the main function of the NS instance to be deployed is to store data, if the information of a certain network service deployment preference can realize the function of storing data, then the OSS/BSS can select the information of the network service deployment preference.
  • the information of network service deployment preference includes the identification of the network service deployment preference NSDF, the identification of at least one virtualized network function description VNFD and/or the identification of at least one physical network function description PNFD, so that the management device
  • the instantiation parameters for deploying the NS instance may be acquired according to the identity of the NSDF, the identity of at least one VNFD, and/or the identity of at least one PNFD.
  • the identifier of at least one VNFD includes the identifier of the first VNFD
  • the request to instantiate the NS includes the identifier of the NSDF, the identifier of the first VNFD and the information of the first VNF instance.
  • the NFVO receives the information sent by the management device VNF query request.
  • the VNF query request carries the identifier of the first VNFD.
  • the VNF query request is used to request the information of the VNF instance from the NFVO.
  • the information list of the first VNF instance can be sent to the management device.
  • Information of at least one VNF instance obtained by instantiating a VNFD, so that when the management device receives the information list of the first VNF instance from NFVO, it obtains the information of the reusable first VNF instance in the information list of the first VNF instance. information.
  • the identifier of at least one VNFD includes the identifier of the second VNFD
  • the instantiated NS request further includes the identifier of the second VNFD and the information of the VPC.
  • the VPC list includes information of at least one VPC, so that the management device can determine the VPC information from the VPC list, and the VPC is used to deploy according to the second
  • the second VNF instance created by the VNFD so that the second VNF instance created according to the second VNFD is deployed using the VPC
  • the instantiating NS request may further include the identifier of the second VNFD and the information of the VPC.
  • the instantiated NS request further includes an identifier of the PNFD and information of the PNF indicated by the identifier of the PNFD, so that the management device may actually need to determine the information of the VPC from the VPC list.
  • the name in the information of the VPC is usually named according to the location of the VPC, for example, Shenzhen-Luohu District-Dongxiao Street.
  • the name in the information of the VPC can also be named by its service, such as IMS.
  • the OSS/BSS can send a VPC query request to request that the VPC information list sent by the NFVO to the OSS/BSS includes the information of all available VPCs.
  • the OSS/BSS may send a VPC query request to request that the VPC information list sent by the NFVO to the OSS/BSS carry the information of the available VPCs that satisfy the specific resource or location.
  • a management device for implementing the method described in the first aspect.
  • the management device can be OSS/BSS or CN NSSMF.
  • the management apparatus includes: a sending unit, a receiving unit and a processing unit.
  • a communication device for implementing the method described in the second aspect.
  • the communication device is NFVO.
  • the communication device includes: a receiving unit, a sending unit and a processing unit.
  • the functional modules of the fourth aspect and the third aspect may be implemented by hardware, and may also be implemented by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • a transceiver is used to perform the functions of the receiving unit and the transmission unit
  • a processor is used to perform the functions of the processing unit
  • a memory is used for the processor to process program instructions of the method of the present application.
  • the processor, transceiver and memory are connected and communicate with each other through the bus. Specifically, reference may be made to the function of managing the behavior of the device or the NFVO in the method of the first aspect to the method of the fourth aspect.
  • the present application further provides a management device for implementing the method described in the first aspect.
  • the management device includes a chip system.
  • the management device includes a processor for implementing the functions in the method described in the first aspect or the third aspect.
  • the management device may also include memory for storing program instructions and data.
  • the memory is coupled to the processor, and the processor can invoke and execute program instructions stored in the memory to implement the functions in the methods described in the first aspect or the third aspect.
  • the management device may also include a communication interface for the communication device to communicate with other devices.
  • the management device is OSS/BSS or CN NSSMF.
  • the communication interface may be a transceiver.
  • the communication interface may be a transceiver.
  • the present application further provides a communication device for implementing the method described in the second aspect.
  • the communication device is NFVO.
  • the communication apparatus includes a processor for implementing the functions in the method described in the second aspect above.
  • the communication apparatus may also include memory for storing program instructions and data.
  • the memory is coupled to the processor, and the processor can invoke and execute program instructions stored in the memory to implement the functions in the method described in the second aspect above.
  • the communication apparatus may also include a communication interface for the communication apparatus to communicate with other devices.
  • the communication interface may be a transceiver.
  • the processor is configured to deploy the first virtual machine on the first server according to the first virtual resource template indicated by the identifier of the first virtual resource template, or, according to the second virtual resource template indicated by the identifier of the second virtual resource template, in the first virtual resource template.
  • a second virtual machine is deployed on the second server.
  • the present application further provides a computer-readable storage medium, comprising: computer software instructions; when the computer software instructions are executed in the management device, the management device executes the method of the first aspect.
  • the present application further provides a computer-readable storage medium, comprising: computer software instructions; when the computer software instructions are executed in the communication device, the communication device is caused to execute the method of the second aspect.
  • the present application further provides a computer program product comprising instructions, when the computer program product is executed in the communication apparatus, the management device executes the method of the first aspect.
  • the present application further provides a computer program product comprising instructions, when the computer program product is executed in the communication device, the communication device causes the communication device to perform the method of the second aspect.
  • the present application provides a chip system, where the chip system includes a processor, and may also include a memory, for implementing the functions of OSS/BSS or NVFO in the above method.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • the present application further provides a communication system, where the communication system includes the management device described in the third aspect and the communication device described in the fourth aspect.
  • FIG. 1 is an example diagram of an NFV system architecture provided by an embodiment of the present application
  • FIG. 2 is a flowchart of a method for creating a network service NS provided by an embodiment of the present application
  • FIG. 3 is a schematic diagram of the composition of a management device provided by the present application.
  • FIG. 4 is a schematic diagram of the composition of a communication device provided by the present application.
  • FIG. 6 is a schematic diagram of the composition of another communication device provided by the present application.
  • words such as “exemplary” or “for example” are used to represent examples, illustrations or illustrations. Any embodiments or designs described in the embodiments of the present application as “exemplary” or “such as” should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as “exemplary” or “such as” is intended to present the related concepts in a specific manner.
  • the traditional telecommunication system is composed of various special hardware devices, and different functions use different hardware devices.
  • 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.
  • NFV Network Function Virtualization
  • IT Internet technology
  • 13 major telecom operators in the world jointly released the Network Function Virtualization (NFV) white paper, and announced that 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.
  • ETSI European Telecommunications Standards Institute
  • NFV technology uses virtualization technology to pool and virtualize 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
  • VNFs independent applications
  • NFV technology can achieve elastic scaling of applications and match virtual resources with business loads, which not only improves the utilization efficiency of virtual resources, but also improves the response rate of the NFV system.
  • FIG. 1 is an exemplary diagram of an NFV system architecture provided by an embodiment of the present application.
  • NFV systems can be used in various networks, eg implemented in a data center network, carrier network or local area network.
  • the NFV system includes an 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 management equipment 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 network elements Management
  • NFV MANO 101 is used to perform monitoring and management of NFVI 102 and VNF 103.
  • the NFV management and orchestration system 101 includes an NFV orchestrator (NFVO) 1011 , one or more VNF managers (VNF manager, VNFM) 1012 and a virtualized infrastructure manager (VIM) 1013.
  • NFVO NFV orchestrator
  • VNF manager VNF manager
  • VNFM virtualized infrastructure manager
  • NFVO 1011 is mainly responsible for the life cycle management of virtualized services, virtual infrastructure and the allocation and scheduling of virtual resources in NFVI.
  • NFVO 1011 can also receive a network service description NSD query request sent by the management device.
  • the NSD query request is used to request NSD information from NFVO, and then send NSD information to the management device.
  • the NSD information includes network service deployment preference information, network service
  • the deployment preference information indicates the user's deployment preference for the network service, and receives a request to instantiate the NS sent by the management device according to the network service deployment preference information, so that the NFVO can create an NS instance related to the NSD according to the request of the instantiated NS.
  • the VNFM 1012 is mainly responsible for the life cycle management of one or more VNFs 103. For example, instantiating, updating, querying, scaling, terminating VNF 103, etc. VNFM 1012 can communicate with VNF 103 to complete VNF 103 lifecycle management and exchange configuration and status information. In the NFV system, there can be multiple VNFMs 1012, which are responsible for life cycle management of different types of VNFs. In addition, the VNFM1012 can also send the IP address of the virtual machine or container of the VNF instance to the NFVO1011 after the VNF is instantiated.
  • the VIM 1013 may perform resource management functions such as managing the allocation of infrastructure resources (eg adding resources to virtual containers) and operational functions (eg 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, controls and manages the interaction of VNF 103 with computing hardware 1021, storage hardware 1022, network hardware 1023, virtual computing (virtual computing) 1024, virtual storage 1025, virtual network 1026.
  • NFVI 102 includes a hardware resource layer, a virtualization layer, and a virtual resource layer.
  • NFVI 102 includes hardware resources, software resources, or a combination of both to complete the deployment of the virtualized environment.
  • the hardware resources and the virtualization layer are used to provide virtualized resources, such as virtual machines and other forms of virtual containers, for the VNF 103 .
  • the hardware resource layer includes computing hardware 1021 , storage hardware 1022 and network hardware 1023 .
  • Computing hardware 1021 may be off-the-shelf hardware and/or custom-made hardware to provide processing and computing resources.
  • the storage hardware 1022 may be storage capacity provided within the network or storage capacity residing in the storage hardware 1022 itself (local storage within the server).
  • the resources of computing hardware 1021 and storage hardware 1022 may be pooled.
  • Network hardware 1023 may be a switch, router, and/or any other network device configured to have switching capabilities.
  • Network hardware 1023 may span multiple domains and may include multiple networks interconnected by one or more transport networks.
  • a virtualization layer within NFVI 102 can abstract hardware resources from the physical layer and decouple VNF 103 in order to provide VNF 103 with virtualized resources.
  • the virtual resource layer includes virtual computing 1024 , virtual storage 1025 and virtual network 1026 .
  • Virtual computing 1024 and virtual storage 1025 may be provided to VNF 103 in the form of virtual machines, and/or other virtual containers. For example, one or more VNFs 103 may be deployed on a virtual machine (VM).
  • VM virtual machine
  • the virtualization layer abstracts the network hardware 1023, thereby forming a virtual network 1026, which may include a virtual switch used to provide connections between virtual machines and other virtual machines.
  • the transport network in the network hardware 1023 can be virtualized using a centralized control plane and a separate forwarding plane (eg, a software-defined network).
  • the computing hardware 1021, the storage hardware 1022 and the network hardware 1023 may include multiple racks, or multiple racks, or even multiple computer rooms.
  • VNF 103 is a virtualized network function instance.
  • the device management system (EM) 104 is a system used to configure and manage devices in the traditional network. In the NFV system, the 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 instantiation of .
  • the management device 105 is used to face users and support various end-to-end telecommunication services.
  • the management device 105 includes an operations support system and a business support system (Operations Support System and Business Support System, OSS/BSS) and core network slice management (core network-Network Slice Subnet Management Function, CN NSSMF).
  • OSS/BSS Operations Support System and Business Support System
  • CN NSSMF core network-Network Slice Subnet Management Function
  • the management device 105 may also send an NSD query request to the NFVO, and the NSD query request is used to request the NSD information from the NFVO, and then receives the NSD information sent by the NFVO.
  • the NSD information includes the information of the network service deployment preference, and the information of the network service deployment preference.
  • the user's deployment preference for the network service is indicated, and then a request to instantiate NS is sent to the NFVO according to the information of the network service deployment preference, so as to request the NFVO to create an NS instance related to the NSD.
  • the virtualized network service can be an IP multimedia subsystem (IMS) network service, or a next-generation mobile core network (Evolved Packet Core, EPC) network service etc.
  • An NS can contain several VNFs.
  • NSD Network Service Descriptor
  • NSD mainly describes the topology information of the service and the description information of each VNF included, namely VNFD.
  • VLD virtual link descriptor
  • the virtualized service requester can be an NFVO or a sender.
  • the sender may specifically be OSS/BSS.
  • the management device 105 sends an NSD query request to the NFVO 1011, and then receives the information of the NSD from the NFVO 1011.
  • the NSD information includes the information of the network service deployment preference, then the management device 105 can according to the network service
  • the information of the deployment preference determines the instantiation parameters, thereby requesting the NFVO 1011 to create an NS instance, without requiring the staff to input the instantiation parameters through the NFVO 1011, thereby reducing the operational complexity of deploying the NS instance through the management device 105, while avoiding the need for manual input of instantiation error caused by the parameter.
  • the management device 105 is an OSS/BSS as an example for description.
  • FIG. 2 provides a method for creating a network service NS according to an embodiment of the present application. As shown in FIG. 3 , the method may include:
  • the NFVO acquires an NSD information list, where the NSD information list includes information of at least one NSD.
  • the data format of the NSD file may be a data compression file format zip, which is a file format for data compression and document storage, and usually uses the suffix ".zip".
  • the NFVO may receive the uploaded NSD file, and parse the NSD file for parsing to obtain NSD information.
  • the NFVO stores the information of the NSD as the information of one NSD in the information list of the NSD.
  • the information list of NSDs includes information of at least one NSD, and the information of each NSD may include information of network service deployment preferences.
  • the information of the NSD can be the information of network service deployment preference added on the basis of NsdInfo in the standard "ETSI GS NFV-IFA 014".
  • NsdInfo the information element of NsdInfo in the standard "ETSI GS NFV-IFA 014" (Table 1: Attributes of the NsdInfo information element).
  • the information of the NSD can be NsdInfo
  • the NsdInfo can also include NSDF (1..N), nsdInfoId (1), nsdId (0..1) and Name ( 0..1).
  • nsdInfoId represents the identifier of the nsdInfo, that is, the identifier of the information of the NSD.
  • nsdId indicates the identifier of the online NSD, the number is 0 or 1 (0..1). If the NSD is online, the number is 1, otherwise it is 0.
  • Name represents the naming of the NSD (it can be a natural language name, such as "switch", or a non-natural language name, such as " ⁇ -->"), the number is 0 or 1 (0..1), If the NSD is online, the number is 1, otherwise it is 0;
  • NSDF represents information about network service deployment preferences, then 1 or N (1..N) NSDFs represent information about at least one network service deployment preference.
  • NsdInfo can also include other information, such as version, designer, nestedNsdInfoId, artifacts and other information, here I won't go into details.
  • the information of network service deployment preference can refer to the content described in the NSDF information element attribute (Table 6.3.2.2-1: Attributes of the NSDF information element) in the standard "ETSI GS NFV-IFA 014".
  • Table 2-2 For details, please refer to Table 2-2.
  • NSDFId represents the identifier of the NSDF, the number is 1, and NSDFId is the unique identifier of the NSDF;
  • vnfProfile represents the information of the vnfProfile, and the number is 0..N, which represents the information of 0 or N vnfProfiles;
  • pnfProfile represents the information of the vnfProfile.
  • the information of pnfProfile, the number is 0..N, indicating the information of 0 or N pnfProfiles.
  • a vnfProfile corresponds to a VNFD and is used to represent a group of VNF instances.
  • the VNF instances in this group of VNF instances are all obtained by instantiating the corresponding VNFD.
  • OSS/BSS can query a set of VNF instances instantiated using the PNFD, and then select and reuse these VNF instances for the created NS instance, or create a new VNF instance according to the VNFD corresponding to the VnfProfile.
  • a pnfProfile corresponds to a PNFD and is used to represent a group of PNFs, and the PNFs in this group of PNFs are associated with the PNFD corresponding to the pnfProfile.
  • OSS/BSS can query a set of VNF instances associated with the PNFD, and then choose to reuse these PNFs for the created NS instance.
  • the information of vnfProfile can refer to the content described in the VnfProfile information element attribute (Table 6.3.3.2-1: Attributes of the VnfProfile information element) in the standard "ETSI GS NFV-IFA 014".
  • vnfProfile includes vnfProfileId and VNFDId
  • vnfProfileId is the unique identifier of vnfProfile
  • VNFDId is the unique identifier of VNFD corresponding to vnfProfile.
  • VNFD is a description of a VNF, also known as a VNF deployment template, which contains a virtual deployment unit (virtualisation deployment unit, VDU), a connection point (connection point, CP), a virtual link (virtual link) , VL) and other information, wherein the VDU may represent a virtual machine with application software installed, and the description of the VDU will include the description of all virtual resources of the virtual machine.
  • the CP represents connection information on the virtual machine, such as virtual network card information, which can be represented by an IP address or a MAC address.
  • VL is a virtual connection connecting multiple VDUs in a VNF, which can be represented by connection type and bandwidth information.
  • the information of the PnfProfile can refer to the content described in the PnfProfile information element attribute (Table 6.3.6.2-1: Attributes of the PnfProfile information element) in the standard "ETSI GS NFV-IFA 014".
  • PnfProfile includes PnfProfileId and PnfdId
  • PnfProfileId is the unique identifier of PnfProfile
  • PnfdId is the unique identifier of PNFD corresponding to PnfProfileId.
  • PNFD is a description of pnf, also called a pnf deployment template.
  • the OSS/BSS sends an NSD query request to the NFVO, where the NSD query request is used to request the NSD information from the NFVO.
  • the OSS/BSS may send an NSD query request to the NFVO through "Query NSDGET ns_descriptors" in the Os-Ma-nfvo interface.
  • Os-Ma-nfvo is a common interface of the current NFV system.
  • gs_nfv_ifa013 7.2.7Query NSD Info operation please refer to the standard gs_nfv_ifa013 7.2.7Query NSD Info operation, which will not be repeated here.
  • the NSD information can be NsdInfo as shown in Table 2-1, then the NSD query request can be as shown in Table 2-5:
  • NSD query request is sent through the "Query NSDGET ns_descriptor" in the Os-Ma-nfvo interface; and the returned parameter is "NsdInfo list", which represents the information list as NSD.
  • the incoming parameter may also be one or more identifiers of NsdInfo, indicating that the OSS/BSS requests one or more NsdInfos corresponding to the one or more identifiers of NsdInfo from NFVO.
  • the NFVO sends an NSD information list to the OSS/BSS, where the NSD information list includes information of at least one NSD.
  • the NFVO When the NFVO receives the NSD query request sent from the OSS/BSS, it returns the NSD information list according to the NSD query request, and the NSD information list includes the information of at least one NSD.
  • the NsdInfo list that NFVO can return to OSS/BSS is the information list of all NSDs obtained by NFVO in step 201, or the NSD query request can carry "one or more NsdInfo identifiers", then NFVO
  • the NsdInfo list returned to the OSS/BSS is one or more NsdInfos corresponding to the identifiers of the one or more NsdInfos in the NSD information list obtained by the NFVO in step 201 .
  • the OSS/BSS selects NSD information from the NSD information list, where the NSD information includes a network service deployment preference information list, and the network service deployment preference information list includes at least one network service deployment preference information.
  • the OSS/BSS After the OSS/BSS receives the NSD information list, it can select the required NSD information according to the actual needs of the NS instance. For example, when the OSS/BSS receives multiple NSD information lists as shown in Table 2-1, if the NS required by the OSS/BSS is the next-generation mobile core network (Evolved Packet Core, EPC) service, then the OSS/BSS The information of an NSD named EPC service-related (eg, EPC or Next Generation Mobile Core Network Service) can be searched in the information list of the NSD, and then the information of the NSD can be selected.
  • EPC service-related eg, EPC or Next Generation Mobile Core Network Service
  • the OSS/BSS can also determine whether to select the NSD information according to the network service deployment preference information in the information of each NSD in the NSD information list, which is not limited here. .
  • the OSS/BSS can select an NsdInfo according to the needs of the created NS instance, and the selected NsdInfo includes 1..N NSDFs, that is, network service deployment A list of preferred information.
  • the OSS/BSS determines the information of the network service deployment preference from at least one network service deployment preference information, where the information of the network service deployment preference indicates the user's deployment preference for the network service.
  • the OSS/BSS after the OSS/BSS acquires at least one information of network service deployment preference, it can select the information of network service deployment preference according to the needs of the NS instance to be deployed.
  • the information list of network service deployment preferences can be 1..N NSDFs as shown in Table 2-1, then OSS/BSS can according to the needs of the NS instance to be deployed, from 1..N Choose one of the NSDFs. For example, if the main function of the NS instance to be deployed is to store data, if a certain NSDF can realize the function of storing data, then OSS/BSS can select this NSDF.
  • the OSS/BSS obtains the instantiation parameters of the NS instance according to the information of the network service deployment preference.
  • instantiation parameters are required for NS instances.
  • the instantiation parameters may include the information of the multiplexed first VNF instance, the VPC required to create the second VNF instance, and/or the PNF required to create the NS instance.
  • the information of the network service deployment preference selected by the OSS/BSS may be an NSDF, and the NSDF includes the identifier of the NSDF, the contents of 0..N vnfProfiles and the 0..N vnfProfiles. .N pnfProfile information (as shown in Table 2-2), the information of each vnfProfile includes the VNFD identifier (as shown in Table 2-3), and the information of each pnfProfile includes the PNFD identifier (as shown in Table 2-4) shown).
  • OSS/BSS can choose to reuse or create one or more VNF instances for the information of each vnfProfile according to the needs of the created NS instance.
  • the OSS/BSS selects the first VNF instance to be multiplexed by the identifier of the first VNFD, and the OSS/BSS uses the The identification of the second VNFD creates a new second VNF instance as described.
  • the OSS/BSS selects the information of the multiplexed first VNF instance according to the identifier of the first VNFD.
  • the OSS/BSS sends a VNF query request to the NFVO, the VNF query request carries the identifier of the first VNFD, and the VNF query request is used to request information of the VNF instance from the NFVO.
  • the VNF query request can be sent through Query VNFGET vnfs/ ⁇ VNFDid ⁇ of the Os-Ma-nfvo interface.
  • the incoming parameter is VNFDid, which indicates the identifier of the first VNFD.
  • the returned parameter is "VnfInstance[0..N]", which indicates the information list of VNF instances, where "0..N" indicates the number of VNF instances.
  • the NFVO sends the information list of the first VNF instance to the OSS/BSS, where the information list of the first VNF instance includes information of at least one VNF instance obtained by instantiating the first VNFD.
  • the NFVO after the NFVO receives the VNF query request, it determines the information of at least one VNF instance instantiated by using the VNFD according to the identifier of the VNFD in the VNF query request, obtains the information list of the first VNF instance, and then Send the information list of the first VNF instance to the OSS/BSS.
  • the VNF instance obtained by using the identifier of the VNFD is called the first VNF instance
  • the identifier of the VNFD corresponding to the first VNF instance is called the identifier of the first VNFD.
  • NFVO when NFVO receives the VNF query request as shown in Table 2-6, it can obtain the incoming parameter VNFDid (that is, the identifier of the first VNFD) from it, and then determine the information of at least one VNF instance according to the VNFDid (VnfInstance[0..N]), the at least one VND instance is a VNF instance obtained by instantiating the VNFD corresponding to the VNFDid (that is, the first VNFD), to obtain the information of these VNF instances, that is, to obtain the information of the first VNF instance list of information. Then, the NFVO sends the information list of the first VNF instance to the OSS/BSS.
  • VNFDid that is, the identifier of the first VNFD
  • the information list of the first VNF instance includes the information of at least one VNF instance, please refer to Table 2-7:
  • vnfInstanceId represents the identifier of a VNF instance
  • vnfName represents the name of a VNF instance (it can be named in natural language, such as "switch”, or it can be named in non-natural language, such as " ⁇ -->").
  • the OSS/BSS determines the information of the first VNF instance from the information list of the first VNF instance.
  • the information of one or more VNF instances can be determined from the information list as the information of the reusable first VNF instance.
  • the "reusable first VNF instance” means that the first VNF instance has been instantiated and can be selected and reused by the newly created NS instance.
  • "reuse” refers to using an existing VNF instance as the VNF instance of the NS instance to be created. That is, the to-be-created NS instance reuses the first VNF instance, indicating that the NS instance includes the first VNF instance.
  • NS instance A is an existing NS instance
  • NS instance B is an NS instance to be created.
  • the NS instance A has the VNF instance A that has already been instantiated.
  • the VNF instance A is used as a VNF instance of the NS instance B, that is, the VNF instance A is reused.
  • NS instance B is created, there is a VNF instance B in NS instance B.
  • the VNF instance B and VNF instance A have the same parameters and the same VPC, that is, VNF instance B and VNF instance A belong to the same A VNF instance, that is, NS instance B multiplexes VNF instance A.
  • the OSS/BSS may select information of one or more VNF instances according to the requirements of the NS instance to be deployed. For example, OSS/BSS can determine whether to select the VNF instance according to the vnfName.
  • the information of the first VNF instance may also include rules, available resources, service capabilities and/or locations of the first VNF instance, etc., and the OSS/BSS may also judge based on one or more of these information. Whether to reuse the first VNF instance in the NS instance.
  • the OSS/BSS can use the identifier of the first VNFD according to the Create the first VNF instance.
  • the VNF instance to be created is referred to as the second VNF instance
  • the identifier of the VNFD for which the VNF instance has not been obtained is referred to as the identifier of the second VNFD. Therefore, the identification of the at least one VNFD includes the identification of the second VNFD.
  • the OSS/BSS can also ID to create a second VNF instance, then OSS/BSS needs to obtain a VPC, and then deploy the second VNF instance to the VPC.
  • the OSS/BSS acquires the information of the VPC according to the identifier of the second VNFD.
  • the OSS/BSS sends a VPC query request to NFVO, and the VPC query request is used to request VPC information from NFVO.
  • the VPC query request can be sent through Query VPCGET vpcs in the Os-Ma-nfvo interface as shown in Table 2-8, and the return parameter is String[0..N], indicating that its data type is String , and the number is 0..N, String[0..N] is used to represent the information list of the VPC.
  • the VPC query request may further include some qualifications (for example, resources or locations of the VPC), so as to request the NFVO for the information of the VPCs having these qualifications.
  • OSS/BSS sends a VPC query request through Query VPCGET vpcs in the Os-Ma-nfvo interface.
  • the VPC query request carries the location of the VPC (for example, Shenzhen or Nanjing), so as to request the NFVO for the VPC at the location. information.
  • the VPC query request carries a string, so as to request information from NFVO that satisfies the VPC whose name has the string.
  • the NFVO sends a VPC information list to the OSS/BSS, where the VPC information list includes information of at least one VPC.
  • the NFVO after the NFVO receives the VPC query request sent by the OSS/BSS, it can return the information list of the VPC, and the information list of the VPC includes the information of at least one VPC, wherein the information of the VPC includes the name and the identifier.
  • the name in the information of the VPC is usually named according to the location of the VPC, for example, Shenzhen-Luohu District-Dongxiao Street.
  • the name in the information of the VPC can also be named by its service, such as IMS.
  • the OSS/BSS can send a VPC query request to request that the VPC information list sent by the NFVO to the OSS/BSS includes the information of all available VPCs.
  • the OSS/BSS may send a VPC query request to request that the VPC information list sent by the NFVO to the OSS/BSS carry the information of the available VPCs that satisfy the specific resource or location.
  • the OSS/BSS determines the information of the VPC from the information list of the VPC.
  • the OSS/BSS After the OSS/BSS receives the VPC information list, it can select one or more VPC information from the list as the VPC used to create the second VNF instance.
  • the OSS/BSS can determine whether to select a VPC according to the requirements of the NS instance to be deployed. In some possible implementation manners, the OSS/BSS may determine whether to select the VPC according to the name in the information of the VPC. For example, if the OSS/BSS is located in Shenzhen and the required service is IMS, then the OSS/BSS can select a VPC with Shenzhen and/or IMS in its name.
  • the OSS/BSS acquires the information of the PNF according to the identifier of the PNFD.
  • the current NFV system can provide VNF services and PNF services.
  • PNF is a node of physical hardware, and PNF provides services of special equipment.
  • the NFV system may simultaneously provide VNF and/or PNF services for OSS/BSS to choose.
  • OSS/BSS For example, two VNFDs are provided in NSD, but PNFD is not provided. If OSS/BSS selects this NSD, OSS/BSS needs to select VNF instances for multiplexing according to the two VNFDs, or create VNF instances without selecting multiplexing. the PNF. If NSD provides one VNFD and one PNFD, if OSS/BSS selects this NSD, then OSS/BSS needs to select a multiplexed VNF instance or create a VNF instance according to one VNFD, and also needs to select a multiplexed PNF for PNFD .
  • the OSS/BSS needs to select the multiplexed PNFs according to the two PNFDs, without selecting multiplexing or creating a VNF instance.
  • the functions of the control plane are usually deployed using a VNF instance, and the functions of the user name are usually deployed using a PNF.
  • the OSS/BSS can obtain the identifier of the PNFD, and request the information of the PNF from the management system EM according to the identifier of the PNFD.
  • the information of the PNF is acquired through steps S31-S33 below.
  • the OSS/BSS sends a PNF query request to the device EM, where the PNF query request carries the identifier of the PNFD, and the PNF query request is used to request the PNF information from the NFVO.
  • the NSDF includes 0..N pnfProfiles, each pnfProfile includes pnfProfileId and pnfdId, the pnfdId is the identifier of the PNFD, that is, at least one PNFD
  • the identity of the PNFD includes the identity of the PNFD.
  • the OSS/BSS may send a PNF query request to the EM, where the PNF query request carries a PNFD identifier, and the PNF query request is used to request the NFVO for PNF information associated with the PNFD identifier.
  • the incoming parameter of the PNF query request is pnfdid (that is, the identifier of the PNFD), and the returned parameter is pnf[0..N], which is used to indicate the information list of the PNF.
  • the quantity is 0..N.
  • the EM sends a PNF information list to the OSS/BSS, where the PNF information list includes information of at least one PNF associated with the PNFD.
  • the EM After receiving the PNF query request sent by the OSS/BSS, the EM can determine the information list of the PNF associated with the first PNFD ID according to the ID of the PNFD in the PNF query request, and then send the information of the PNF to the OSS/BSS list.
  • the EM can obtain the incoming parameter pnfdid from Table 2-9, and then determine the information of at least one pnf (pnf[0..N]) according to the pnfdid.
  • the information is associated with the PNFD identified by pnfdid, and then the information of the at least one pnf is sent to the OSS/BSS.
  • the information of a PNF can be represented by the field AddPnfData in the standard "ETSI GS NFV-IFA 014", specifically, the information element attribute of AddPnfData (Table 8.3.4.32.2-1: Attributes of the AddPnfData information element). Please refer to Table 2-10:
  • pnfId represents the identifier of the PNF
  • pnfName represents the name of the PNF
  • pnfdId represents the identifier of the PNFD
  • pnfProfileId represents the identifier of the pnfProfile.
  • the information of the PNF also includes the manufacturer, version and type.
  • the OSS/BSS determines the information of the PNF from the information list of the PNF.
  • the OSS/BSS After the OSS/BSS receives the PNF information list, it can select one or more PNF information from the PNF information list according to the requirements of the deployed NS instance. Continuing the above example, in some possible implementations, the OSS/BSS may determine whether to select the information of the PNF according to the pnfName in the information of the PNF.
  • the pnfName usually carries the valid information of the PNF, such as the functions that can be implemented, or the city where it is located. Then the OSS/BSS can determine whether to select the PNF according to the pnfName. In some possible implementation manners, the OSS/BSS may also determine whether to select the PNF according to the manufacturer, version and type in the information of the PNF.
  • the instantiation parameters required for deploying an NS instance can be obtained, that is, the information of the reusable first VNF instance, the VPC required for creating the second VNF instance, and/or the information required for creating the NS instance can be obtained.
  • the required PNF does not need to be parsed by OSS/BSS, which saves computing overhead and signaling overhead, and does not require staff to manually input instantiation parameters, thus reducing the operational complexity of deploying NS instances through OSS/BSS, and avoiding the Errors caused by manually entering instantiation parameters.
  • the OSS/BSS sends a request for establishing an NS instance to the NFVO.
  • the OSS/BSS may name the NS instance, and then send an NS creation request to the NFVO.
  • the NS creation request message includes the identifier of the network service information and the name of the NS instance, and is used to request the NFVO to create an NS instance.
  • the information of the network service is nsdinfo
  • the NS creation request sent by OSS/BSS to NFVO carries nsdinfoid and nsName.
  • nsdinfoid a request to create an ID of an NS instance:
  • the create NS request message can be sent through Create NS Identifier in the Os-Ma-nfvo interface
  • nsdinfoid is the identifier of the selected NsdInfo
  • nsName is the name of the NS instance.
  • the NFVO determines the identifier of the NS instance, and sends the identifier of the NS instance to the OSS/BSS.
  • the NFVO After the NFVO receives the request to create an NS, it can determine the NSD according to the identifier of the network service information, and create an ID of the NS instance according to the NSD. Continuing the example in the above step 207, when the NFVO receives the NS creation request, it uses the identifier of the NSD as the identifier (nsInstanceId) of the NS instance, and uses nsName as the name of the NS instance. After the NFVO establishes the identity of the NS instance, it sends a response message to the OSS/BSS, where the response message carries the identity of the established NS instance (nsInstanceId) and the name of the NS instance (nsName).
  • the OSS/BSS sends a request for instantiating the NS to the NFVO, and the request for instantiating the NS carries the identifier of the NS instance and the instantiation parameters.
  • the OSS/BSS after the OSS/BSS receives the response message carrying the identifier of the NS instance, it then constructs a request to instantiate the NS by using the instantiation parameters obtained in step 206 above.
  • the instantiation parameters may include an identifier of an NSDF and at least one of the following three: an identifier of the first VNFD and information of the first VNF instance; an identifier of the second VNFD and information of the VPC, wherein , the NSDF includes the identifier of the second VNFD; the identifier of the PNFD and the information of the PNF, wherein the NSDF includes the identifier of the PNFD.
  • the request to instantiate NS can be as the input parameters of the instantiated NS operation in the standard "ETSI GS NFV-IFA 014" (Table 7.3.3.2-1:Instantiate NS operation input parameters ), please refer to Table 2-12:
  • flavorId is used to represent the identifier of the NSDF
  • addPnfData represents the information of the PNF
  • vnfInstanceData represents the information of the multiplexed first VNF instance
  • additionalParamForVnf represents the information of the created second VNF instance.
  • AddPnfData, VnfInstanceData, and additionalParamForVnf are exemplarily described below.
  • AddPnfData can be an attribute of the AddPnfData information element (Table 8.3.4.32.2-1: Attributes of the AddPnfData information element) in the standard "ETSI GS NFV-IFA 014", please refer to Table 2-13:
  • pnfId represents the identifier of the pnf
  • pnfName represents the natural language name of the selected PNF
  • pnfdId represents the identifier of the PNF associated with the PNFD
  • pnfProfileId represents the identifier of the pnfProfile corresponding to the PNF.
  • VnfInstanceData can be the attributes of the VnfInstanceData information element (Table 8.3.4.3.2-1: Attributes of the VnfInstanceData information element) in the standard "ETSI GS NFV-IFA 014", please refer to Table 2-14:
  • vnfInstanceId represents the identifier of the vnfInstance, that is, the identifier of the first VNF instance
  • vnfProfileId represents the identifier of the vnfProfile, that is, the identifier of the first vnfProfile corresponding to the first VNF instance.
  • ParamsForVnf can be the attributes of the ParamsForVnf information element (Table 8.3.4.5.2-1: Attributes of the ParamsForVnf information element) in the standard "ETSI GS NFV-IFA 014", please refer to Table 2-15:
  • vnfProfileId represents the identifier of the vnfProfile, that is, the identifier of the second VNF instance;
  • additionalParam represents the key-value pair, which can be used to carry the information representing the selected VPC.
  • NFVO instantiates the NS instance according to the instantiation parameters.
  • the NFVO When the NFVO receives the request to instantiate the NS, it determines the identity of the NS instance, and then instantiates the NS instance according to the instantiation parameters.
  • the specific instantiation process belongs to the prior art, and will not be repeated here.
  • the NFVO sends a response message that the NS instantiation is successful to the OSS/BSS.
  • the NFVO sends a response message of the successful instantiation of the NS to the OSS/BSS, so as to complete the process of deploying the NS instance on the NFVO through the OSS/BSS.
  • the OSS/BSS can use the services provided by the NS instance by interacting with the NFVO signaling.
  • the OSS/BSS sends an NSD query request to NFVO, and then receives NSD information from NFVO.
  • the NSD information includes the information of network service deployment preference, then the OSS/BSS can deploy the preferred information according to the network service deployment preference.
  • each network element such as a management device and a communication device, includes hardware structures and/or software modules corresponding to each function in order to implement the functions in the methods provided by the above embodiments of the present application.
  • a management device and a communication device includes hardware structures and/or software modules corresponding to each function in order to implement the functions in the methods provided by the above embodiments of the present application.
  • the present application can be implemented in hardware or in the form of a combination of hardware and computer software, in conjunction with the algorithm steps of the examples described in the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution.
  • the management device and the communication device can be divided into functional modules according to the above method examples.
  • each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules. It should be noted that, the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and there may be other division manners in actual implementation.
  • FIG. 3 shows a possible schematic diagram of the composition of the management device involved in the above and the embodiments, and the management device can execute the OSS/BSS in the various method embodiments of the present application. steps performed.
  • the management device 300 may include: a sending unit 301 , a receiving unit 302 and a processing unit 303 .
  • the sending unit 301 is configured to execute or support the management device 300 to execute steps 202 , S11 , S21 , S31 , 207 , and 209 executed by the OSS/BSS in the method shown in FIG. 2 .
  • the receiving unit 302 is configured to support the management device 300 to perform the method performed by the OSS/BSS described in the embodiments of the present application.
  • the receiving unit 302 is configured to perform or support the management device 300 to perform steps 203, S12, S22, S32, 208 and 211 performed by the OSS/BSS in the method shown in FIG. 2 .
  • the processing unit 303 is configured to execute or support the management device 300 to perform steps 204, 205, S13, S23, and S33 performed by the OSS/BSS in the method shown in FIG.
  • the information of the network service deployment preference in the information of the NSD, and according to the information of the network service deployment preference, a request to instantiate the NS is sent to the NFVO, so as to request the NFVO to create an NS instance related to the NSD.
  • FIG. 4 shows a possible schematic composition diagram of the communication device involved in the above and the embodiment.
  • the communication device 400 can perform the steps performed by the NFVO in each method embodiment of the present application.
  • the communication apparatus 400 may include: a receiving unit 401 , a sending unit 402 , and a processing unit 403 .
  • the receiving unit 401 is configured to support the communication apparatus 400 to perform the method performed by the NFVO described in the embodiments of the present application.
  • the receiving unit 401 is configured to execute or support the communication apparatus 400 to execute steps 202, S11, S21, S31, 207, and 209 executed by NFVO in the method shown in FIG. 2 .
  • the processing unit 403 is configured to support the communication apparatus 400 to perform the method performed by the NFVO described in the embodiments of the present application.
  • the processing unit 402 is configured to execute or support the communication device 400 to execute steps 201 and 210 performed by the NFVO in the method shown in FIG. 2 .
  • the sending unit 402 is configured to perform or to support the communication apparatus 400 to perform 203, S12, S22, S32, 208, and 211 performed by the NFVO in the method shown in FIG. 2 .
  • the management device provided by the embodiment of the present application is used to execute the method of any of the foregoing embodiments, and thus can achieve the same effect as the method of the foregoing embodiment.
  • a management device 500 provided in an embodiment of the present application is used to implement the functions of the OSS/BSS in the above method.
  • the management device 500 may be OSS/BSS or CN NSSMF, or may be a device or function in OSS/BSS or CN NSSMF.
  • the management device 500 may be a chip system.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the management device 500 includes at least one processor 501, which is configured to implement the OSS/BSS device or the apparatus or function therein in the method provided in the embodiment of the present application.
  • the processor 501 may be configured to select the information of the NSD from the information list of the NSD, etc. For details, refer to the detailed description in the method example, which will not be repeated here.
  • the management device 500 may also include at least one memory 502 for storing program instructions and/or data.
  • Memory 502 is coupled to processor 501 .
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • Processor 501 may cooperate with memory 502 .
  • Processor 501 may execute program instructions stored in memory 502 . At least one of the at least one memory may be included in the processor.
  • the processor 501 and the memory 502 may also be a virtualized processor and a virtualized memory.
  • the management device 500 may further include a communication interface 503 for communicating with other devices through a transmission medium, so that the apparatus in the management device 500 may communicate with other devices.
  • the processor 501 uses the communication interface 503 to send and receive data, and is used to implement the method performed by the OSS/BSS in the embodiment corresponding to FIG. 2 .
  • the above-mentioned management device 500 may further include a network interface for communicating with external devices.
  • the network interface is used to communicate with user equipment and the like.
  • connection medium between the communication interface 503 , the processor 501 , and the memory 502 is not limited in the embodiments of the present application.
  • the communication interface 503, the processor 501, and the memory 502 are connected through a bus 504 in FIG. 5.
  • the bus is represented by a thick line in FIG. 5.
  • the connection between other components is only for schematic illustration. , is not limited.
  • the bus can be divided into address bus, data bus, control bus and so on. For ease of presentation, only one thick line is used in FIG. 5, but it does not mean that there is only one bus or one type of bus.
  • the communication apparatus provided by the embodiment of the present application is used to execute the method of any of the foregoing embodiments, and thus can achieve the same effect as the method of the foregoing embodiment.
  • a communication apparatus 600 provided by an embodiment of the present application is used to implement the function of NFVO in the above method.
  • the communication device 600 may be NFVO, or may be a device or function in NFVO.
  • the communication apparatus 600 may be a system-on-a-chip.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the communication apparatus 600 includes at least one processor 601, configured to implement the function of NFVO in the method provided by the embodiment of the present application.
  • the processor 601 may be configured to create an NS instance related to the NSD according to the request for instantiating the NS, etc. For details, refer to the detailed description in the method example, which will not be repeated here.
  • Communication apparatus 600 may also include at least one memory 602 for storing program instructions and/or data.
  • Memory 602 is coupled to processor 601 .
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • Processor 601 may cooperate with memory 602 .
  • Processor 601 may execute program instructions stored in memory 602 . At least one of the at least one memory may be included in the processor.
  • the processor 601 and the memory 602 may also be a virtualized processor and a virtualized memory.
  • the communication apparatus 600 may also include a communication interface 603 for communicating with other devices through a transmission medium, so that the apparatus used in the communication apparatus 600 may communicate with other devices, such as the management device 500 .
  • the processor 601 uses the communication interface 603 to send and receive data, and is used to implement the method performed by the NFVO in the embodiment corresponding to FIG. 2 .
  • the above communication apparatus 600 may further include a network interface for communicating with external devices.
  • a network interface is used to communicate with the management device 500 or the like.
  • the specific connection medium among the communication interface 603 , the processor 601 , and the memory 602 is not limited in this embodiment of the present application.
  • the communication interface 603, the processor 601, and the memory 602 are connected through a bus 604 in FIG. 6.
  • the bus is represented by a thick line in FIG. 6, and the connection between other components is only for schematic illustration. , is not limited.
  • the bus can be divided into address bus, data bus, control bus and so on. For ease of presentation, only one thick line is used in FIG. 6, but it does not mean that there is only one bus or one type of bus.
  • the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, which can implement or
  • a general purpose processor may be a microprocessor or any conventional processor or the like.
  • the steps of the methods disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.
  • the memory may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or may also be a volatile memory (volatile memory), for example Random-access memory (RAM).
  • Memory is, but is not limited to, any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • the memory in this embodiment of the present application may also be a circuit or any other device capable of implementing a storage function, for storing program instructions and/or data.
  • the disclosed apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of modules or units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or May be integrated into another device, or some features may be omitted, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • Units described as separate components may or may not be physically separated, and components shown as units may be one physical unit or multiple physical units, that is, may be located in one place, or may be distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
  • the methods provided in the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software When implemented in software, it can be implemented in whole or in part in the form of a computer program product.
  • a computer program product includes one or more computer instructions.
  • the procedures or functions according to the embodiments of the present invention result in whole or in part.
  • a computer may be a general purpose computer, special purpose computer, computer network, network device, terminal, or other programmable device.
  • Computer instructions may be stored on or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server, or data center over a wire (e.g.
  • coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.) means to transmit to another website site, computer, server or data center.
  • a computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, or the like that contains an integration of one or more available media.
  • Useful media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, digital video discs (DVDs)), or semiconductor media, among others.

Abstract

本申请实施例公开了一种创建网络服务NS的方法及相关装置，用于通过向NFVO查询NSD的信息，并通过NSD的信息中的网络服务部署偏好的信息请求NFVO创建NS实例。该方法包括：管理设备通过向网络功能虚拟化编排器NFVO发送网络服务描述NSD查询请求，然后接收来自NFVO的NSD的信息，由于NSD的信息包括网络服务部署偏好的信息，那么管理设备可以根据网络服务部署偏好的信息确定实例化参数，从而请求NFVO创建NS实例，无需工作人员通过NFVO输入实例化参数，从而降低了通过管理设备部署NS实例的操作复杂度，同时避免了由于手工输入实例化参数而造成的出错。

Description

一种创建网络服务NS的方法及相关装置
本申请要求于2021年03月04日提交中国专利局、申请号为202110239645.0、发明名称为“一种创建网络服务NS的方法及相关装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及网络功能虚拟化领域，尤其涉及一种创建网络服务(network service，NS)的方法及相关装置。
背景技术
网络功能虚拟化(network function virtualization，NFV)技术是采用虚拟化技术将传统网络中专用设备的功能虚拟化为独立的应用，灵活地部署在基于标准的计算硬件、存储硬件和网络硬件等其他设备构建的统一基础设施平台上。通过NFV技术实现的功能称为网络服务(network service，NS)。
在现有技术中，为了在NFV系统中部署NS，运营支持系统(operations support system,OSS)和/或业务支持系统(business support system，BSS)需要将网络服务描述(network service descriptor，NSD)信息上传到网络功能虚拟化编排器(network functions virtualization orchestrator，NFVO)，让NFVO根据NSD的信息部署NS。
然而，当通过在OSS/BSS上操作部署NS时，现有技术需要工作人员通过NFVO输入实例化参数，导致通过OSS/BSS部署NS操作复杂，并且由于手工输入实例化参数也容易造成出错。
发明内容
本申请实施例提供了一种创建网络服务NS的方法及相关装置，用于通过向NFVO查询NSD的信息，并通过NSD的信息中的网络服务部署偏好的信息请求NFVO创建NS实例。
第一方面，提供了一种创建网络服务NS的方法，该方法可应用于管理设备。在该方法中，管理设备通过向网络功能虚拟化编排器NFVO发送网络服务描述NSD查询请求，然后接收来自NFVO的NSD的信息，由于NSD的信息包括网络服务部署偏好的信息，那么管理设备可以根据网络服务部署偏好的信息确定实例化参数，从而请求NFVO创建NS实例，无需工作人员通过NFVO输入实例化参数，从而降低了通过管理设备部署NS实例的操作复杂度，同时避免了由于手工输入实例化参数而造成的出错。
在一种可能的设计中，管理设备通过接收NFVO发送的NSD的信息列表，NSD的信息列表包括，从而可以根据实际需要从NSD的信息列表中的至少一个NSD的信息选择NSD的信息。例如，若OSS/BSS所需要的NS是下一代移动核心网络(Evolved Packet Core，EPC)服务，那么OSS/BSS可以在NSD的信息列表中搜索命名为EPC服务相关的NSD的信息(例如EPC或下一代移动核心网络服务)，然后选择该NSD的信息。
在一种可能的设计中，NSD的信息包括至少一个网络服务部署偏好的信息，从而管理设备可以根据所要部署的NS实例的需要，从至少一个网络服务部署偏好的信息中选择网络 服务部署偏好的信息。例如，若所要部署的NS实例的主要功能在于存储数据，若某个网络服务部署偏好的信息可实现存储数据的功能，那么OSS/BSS可以选择该网络服务部署偏好的信息。
在一种可能的设计中，网络服务部署偏好的信息包括网络服务部署偏好NSDF的标识、至少一个虚拟化网络功能描述VNFD的标识和/或至少一个物理网络功能描述PNFD的标识，从而使得管理设备可以根据NSDF的标识、至少一个VNFD的标识和/或至少一个PNFD的标识来获取部署NS实例的实例化参数。
在一种可能的设计中，至少一个VNFD的标识包括第一VNFD的标识，从而使得管理设备可以根据第一VNFD的标识获取第一虚拟网络功能VNF实例的信息。实例化NS的请求包括NSDF的标识、第一VNFD的标识和第一VNF实例的信息，使得NFVO部署NS实例时，可以根据NSDF的标识确定NSDF，根据第一VNFD的标识第一VNF实例的信息确定复用的第一VNF实例。
在一种可能的设计中，管理设备向NFVO发送VNF查询请求，VNF查询请求携带第一VNFD的标识，VNF查询请求用于向NFVO请求VNF实例的信息，以使得NFVO根据第一VNFD的标识确定可复用的第一VNF实例的信息，当管理设备接收来自NFVO的第一VNF实例的信息列表后，第一VNF实例的信息列表包括由第一VNFD进行实例化得到的至少一个VNF实例的信息，从而获取了第一VNF实例的信息列表中可复用的第一VNF实例的信息。
需要说明的是，“可复用的第一VNF实例”指的是第一VNF实例已经实例化，可以被新建的NS实例选择复用。具体的，“复用”指的是使用已经存在的VNF实例，作为准备创建的NS实例的VNF实例。也就是说，该准备创建的NS实例复用第一VNF实例，表示该NS实例包括该第一VNF实例。
在一些可能的实现方式中，第一VNF实例的信息还可以包括该第一VNF实例的规则、可用资源、业务能力和/或位置等，OSS/BSS也可以根据这些信息的一个或多个判断是否要在NS实例中复用该第一VNF实例。
在一种可能的设计中，至少一个VNFD的标识包括第二VNFD的标识，管理设备获取虚拟私有云VPC的信息，从而使用VPC部署根据第二VNFD创建的第二VNF实例，那么实例化NS请求可以进一步包括第二VNFD的标识和VPC的信息。
在一种可能的设计中，管理设备向NFVO发送VPC查询请求，VPC查询请求用于向NFVO请求VPC的信息，并接收来自NFVO的VPC列表，VPC列表包括至少一个VPC的信息，管理设备可以实际需要从VPC列表中确定VPC的信息。其中，VPC的信息中的名称通常根据该VPC的位置来命名，例如深圳-罗湖区-东晓街道。在一些可能的实现方式中，VPC的信息中的名称还可以通过其业务来命名，例如IMS。续上述例子，OSS/BSS可以通过发送VPC查询请求，请求NFVO向OSS/BSS发送的VPC的信息列表中包括所有可用的VPC的信息。在一些可能的实现方式中，OSS/BSS可以通过发送VPC查询请求，请求NFVO向OSS/BSS发送的VPC的信息列表中携带满足该特定资源或位置的可用的VPC的信息。
在一种可能的设计中，管理设备根据至少一个PNFD的标识获取PNF的信息，那么实例化NS请求可以进一步包括PNFD的标识和所述PNFD的标识指示的PNF的信息，使得NFVO可以根据PNFD的标识和PNF的信息部署NS实例。需要说明的是，当前的NFV系统可以提 供VNF的服务和PNF的服务。其中，PNF为实体硬件的节点，PNF提供了专用设备的服务。在本申请实施例中，NFV系统可以同时提供VNF和/或PNF的服务，以供OSS/BSS进行选择。
在一种可能的设计中，当管理设备选择了NSD的信息后，若NSD的信息中指示部署的NS实例中包括VNF实例，则管理设备需要选择复用的VNF实例或创建VNF实例。若管理设备选择复用VNF实例，则管理设备可以执行从NFVO中获取可复用的VNF实例的信息以及后续步骤。若管理设备选择创建VNF实例，则管理设备可以执行从NFVO中确定可用的VPC以及后续。若NSD的信息中指示部署的NS实例中包括PNF实例，管理设备需要执行选择复用的PNF以及后续步骤。若NSD的信息中指示部署的NS实例中包括VNF实例和PNF实例，那么管理设备需要执行选择复用的VNF实例或创建VNF实例以及后续步骤，还需要执行从NFVO中确定可用的VPC以及后续步骤。
在一种可能的设计中，管理设备向设备管理系统EM发送PNF查询请求，通过在PNF查询请求中携带PNFD的标识，用于向NFVO请求与PNFD相关联的PNF的信息，那么EM会向管理设备发送PNF列表，PNF列表包括与PNFD的标识相关联的至少一个PNF的信息，从而管理设备可以根据实际需要从PNF列表中确定PNF的信息。例如，管理设备根据需要实现的功能，或者所在的城市等，那么OSS/BSS可以根据PNF的命名确定是否要选用该PNF。在一些可能的实现方式中，OSS/BSS也可以根据PNF的信息中的厂家、版本和类型来判断是否要选用该PNF。
在一种可能的设计中，管理设备为运营支持系统和业务支持系统(Operations Support System and Business Support System，OSS/BSS)或核心网切片管理(core network-Network Slice Subnet Management Function，CN NSSMF)，那么管理设备可以面对不同类型的用户(OSS/BSS的用户或CN NSSMF的用户)提供NS的服务。
第二方面，提供了一种创建网络服务NS的方法，该方法可应用于网络功能虚拟化编排器(NFV orchestrator，NFVO)设备。在该方法中，NFVO接收管理设备发送的网络服务描述NSD查询请求，NSD查询请求用于向NFVO请求NSD的信息，然后NFVO向管理设备发送NSD的信息，NSD的信息包括网络服务部署偏好的信息，网络服务部署偏好的信息指示用户对网络服务的部署偏好，接着NFVO接收管理设备根据网络服务部署偏好的信息发送的实例化NS的请求，并根据实例化NS的请求创建与NSD相关的NS实例，由于NSD的信息包括网络服务部署偏好的信息，那么管理设备可以根据网络服务部署偏好的信息确定实例化参数，从而请求NFVO创建NS实例，无需工作人员通过NFVO输入实例化参数，从而降低了通过管理设备部署NS实例的操作复杂度，同时避免了由于手工输入实例化参数而造成的出错。
在一种可能的设计中，NFVO向管理设备发送NSD的信息列表，由于NSD的信息列表包括至少一个NSD的信息，以使得管理设备可以根据实际需要从NSD的信息列表中确定NSD的信息。例如，若OSS/BSS所需要的NS是下一代移动核心网络(Evolved Packet Core，EPC)服务，那么OSS/BSS可以在NSD的信息列表中搜索命名为EPC服务相关的NSD的信息(例如EPC或下一代移动核心网络服务)，然后选择该NSD的信息。
在一种可能的设计中，NSD的信息包括至少一个网络服务部署偏好的信息，从而管理设备可以根据所要部署的NS实例的需要，从至少一个网络服务部署偏好的信息中确定网络服务部署偏好的信息。例如，若所要部署的NS实例的主要功能在于存储数据，若某个网络 服务部署偏好的信息可实现存储数据的功能，那么OSS/BSS可以选择该网络服务部署偏好的信息。
在一种可能的设计中，网络服务部署偏好的信息包括网络服务部署偏好NSDF的标识、至少一个虚拟化网络功能描述VNFD的标识和/或至少一个物理网络功能描述PNFD的标识，从而使得管理设备可以根据NSDF的标识、至少一个VNFD的标识和/或至少一个PNFD的标识来获取部署NS实例的实例化参数。
在一种可能的设计中，至少一个VNFD的标识包括第一VNFD的标识，实例化NS的请求包括NSDF的标识、第一VNFD的标识和第一VNF实例的信息，当NFVO接收管理设备发送的VNF查询请求，VNF查询请求携带第一VNFD的标识，VNF查询请求用于向NFVO请求VNF实例的信息，可以向管理设备发送第一VNF实例的信息列表，第一VNF实例的信息列表包括由第一VNFD进行实例化得到的至少一个VNF实例的信息，使得当管理设备接收来自NFVO的第一VNF实例的信息列表后，获取了第一VNF实例的信息列表中可复用的第一VNF实例的信息。
在一种可能的设计中，至少一个VNFD的标识包括第二VNFD的标识，实例化NS请求进一步包括第二VNFD的标识和VPC的信息，当NFVO接收管理设备发送的VPC查询请求时，由于VPC查询请求用于向NFVO请求VPC的信息，那么NFVO可以向管理设备发送VPC列表，VPC列表包括至少一个VPC的信息，以使得管理设备从VPC列表中确定VPC的信息，VPC用于部署根据第二VNFD创建的第二VNF实例，从而使用VPC部署根据第二VNFD创建的第二VNF实例，那么实例化NS请求可以进一步包括第二VNFD的标识和VPC的信息。
在一种可能的设计中，实例化NS请求进一步包括PNFD的标识和PNFD的标识指示的PNF的信息，使得管理设备可以实际需要从VPC列表中确定VPC的信息。其中，VPC的信息中的名称通常根据该VPC的位置来命名，例如深圳-罗湖区-东晓街道。在一些可能的实现方式中，VPC的信息中的名称还可以通过其业务来命名，例如IMS。续上述例子，OSS/BSS可以通过发送VPC查询请求，请求NFVO向OSS/BSS发送的VPC的信息列表中包括所有可用的VPC的信息。在一些可能的实现方式中，OSS/BSS可以通过发送VPC查询请求，请求NFVO向OSS/BSS发送的VPC的信息列表中携带满足该特定资源或位置的可用的VPC的信息。
第三方面，提供了一种管理设备，用于实现上述第一方面描述的方法。管理设备可以为OSS/BSS或CN NSSMF。例如，管理装置包括：发送单元、接收单元和处理单元。
关于创建网络服务NS的方法的具体实现方式可以参考上述第一方面的阐述，不予赘述。
第四方面，提供了一种通信装置，用于实现上述第二方面描述的方法。通信装置为NFVO。例如，该通信装置包括：接收单元、发送单元和处理单元。
关于创建网络服务NS的方法的具体实现方式可以参考上述第二方面的阐述，不予赘述。
需要说明的是，上述第四方面和第三方面的功能模块可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的模块。例如，收发器，用于完成接收单元和发送单元的功能，处理器，用于完成处理单元的功能，存储器，用于处理器处理本申请的方法的程序指令。处理器、收发器和存储器通过总线连接并 完成相互间的通信。具体的，可以参考第一方面的方法至第四方面的方法中的管理设备或NFVO的行为的功能。
第五方面，本申请还提供了一种管理设备，用于实现上述第一方面描述的方法。该管理设备包括芯片系统。例如管理设备包括处理器，用于实现上述第一方面或第三方面描述的方法中的功能。管理设备还可以包括存储器，用于存储程序指令和数据。存储器与处理器耦合，处理器可以调用并执行存储器中存储的程序指令，用于实现上述第一方面或第三方面描述的方法中的功能。管理设备还可以包括通信接口，通信接口用于该通信装置与其它设备进行通信。示例性地，管理设备为OSS/BSS或CN NSSMF。
在一种可能的设备中，该通信接口可以是收发器。具体的可以参考上述各方面的阐述，不予赘述。
第六方面，本申请还提供了一种通信装置，用于实现上述第二方面描述的方法。通信装置为NFVO。例如通信装置包括处理器，用于实现上述第二方面描述的方法中的功能。通信装置还可以包括存储器，用于存储程序指令和数据。存储器与处理器耦合，处理器可以调用并执行存储器中存储的程序指令，用于实现上述第二方面描述的方法中的功能。通信装置还可以包括通信接口，通信接口用于该通信装置与其它设备进行通信。
在一种可能的设备中，该通信接口可以是收发器。处理器，用于根据第一虚拟资源模板的标识指示的第一虚拟资源模板在第一服务器上部署第一虚拟机，或者，根据第二虚拟资源模板的标识指示的第二虚拟资源模板在第二服务器上部署第二虚拟机。
第七方面，本申请还提供了一种计算机可读存储介质，包括：计算机软件指令；当计算机软件指令在管理设备中运行时，使得管理设备执行上述第一方面的方法。
第八方面，本申请还提供了一种计算机可读存储介质，包括：计算机软件指令；当计算机软件指令在通信装置中运行时，使得通信装置执行上述第二方面的方法。
第九方面，本申请还提供了一种包含指令的计算机程序产品，当计算机程序产品在通信装置中运行时，使得管理设备执行上述第一方面的方法。
第十方面，本申请还提供了一种包含指令的计算机程序产品，当计算机程序产品在通信装置中运行时，使得通信装置执行上述第二方面的方法。
第十一方面，本申请提供了一种芯片系统，该芯片系统包括处理器，还可以包括存储器，用于实现上述方法中OSS/BSS或NVFO的功能。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
第十二方面，本申请还提供了一种通信系统，通信系统包括第三方面描述的管理设备以及第四方面描述的通信设备。
另外，上述任意方面的设计方式所带来的技术效果可参见第一方面和第二方面中不同设计方式所带来的技术效果，此处不再赘述。
附图说明
图1为本申请实施例提供的一种NFV系统架构示例图；
图2为本申请实施例提供的一种创建网络服务NS的方法的流程图；
图3为本申请提供的一种管理设备的组成示意图；
图4为本申请提供的一种通信装置的组成示意图；
图5为本申请提供的另一种管理设备的组成示意图；
图6为本申请提供的另一种通信装置的组成示意图。
具体实施方式
本申请说明书和权利要求书及上述附图中的术语“第一”、“第二”和“第三”等是用于区别不同对象，而不是用于限定特定顺序。
在本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
为了下述各实施例的描述清楚简洁，首先给出相关技术的简要介绍：
传统的电信系统是通过各种专用的硬件设备组成，不同的功能采用不同的硬件设备。随着网络规模的增长，电信系统越来越复杂，带来了诸多的挑战。例如，新增业务的开发上线、系统的运维和资源利用率等。为了应对这些挑战及利用互联网(internet technology，IT)业界的虚拟化技术及云计算技术，全球主要的13个电信运营商联合发布了网络功能虚拟化(network function virtualization，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和管理设备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主要负责处理虚拟化业务的生命周期管理、虚拟基础设施及NFVI中虚拟资源的分配和调度等。NFVO 1011也可以接收管理设备发送的网络服务描述NSD查询请求，NSD查询请求用于向NFVO请求NSD的信息，然后向管理设备发送NSD的信息，NSD的信息包括网络服务部署偏好的信息，网络服务部署偏好的信息指示用户对网络服务的部署偏好， 并接收管理设备根据网络服务部署偏好的信息发送的实例化NS的请求，实现NFVO可以根据实例化NS的请求创建与NSD相关的NS实例。
VNFM 1012主要负责一个或多个VNF 103的生命周期管理。比如，实例化(instantiating)，更新(updating)，查询，弹性伸缩(scaling)，终止(terminating)VNF 103等。VNFM 1012可以与VNF 103通信以完成VNF 103生命周期管理及交换配置和状态信息。在NFV系统中VNFM 1012可以有多个，负责对不同类型的VNF进行生命周期管理。此外，VNFM1012还可以在对VNF实例化完成后，将VNF实例的虚拟机或容器的IP地址发送给NFVO1011。
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的实例化等生命周期管理操作。
管理设备105用于面对用户，支持各种端到端的电信业务。管理设备105包括运营支持系统和业务支持系统(Operations Support System and Business Support System， OSS/BSS)和核心网切片管理(core network-Network Slice Subnet Management Function，CN NSSMF)。以OSS/BSS为例。OSS支持网络配置，业务提供，故障管理等管理功能，BSS用于处理订单，付费，收入等，支持产品管理，订单管理，收益管理及客户管理等。
管理设备105也可以向NFVO发送NSD查询请求，NSD查询请求用于向NFVO请求NSD的信息，然后接收NFVO发送的NSD的信息，NSD的信息包括网络服务部署偏好的信息，网络服务部署偏好的信息指示用户对网络服务的部署偏好，接着根据网络服务部署偏好的信息向NFVO发送实例化NS的请求，以请求NFVO创建与NSD相关的NS实例。
在NFV系统中，虚拟化的网络服务(Network Service，NS)可以是一个IP多媒体子系统(IP multimedia subsystem，IMS)网络服务，或者，是一个下一代移动核心网络(Evolved Packet Core，EPC)网络服务等。一个NS中可以包含若干个VNF。在对一个NS进行虚拟化部署时，虚拟化业务提供方需要从虚拟化业务请求方获取该业务的描述信息，即网络服务模板(Network Service descriptor，NSD)。NSD主要描述了该业务的拓扑结构信息以及包含的每个VNF的描述信息，即VNFD。在拓扑结构信息中，可以使用虚拟化连接模板(virtual link descriptor，VLD)来描述VNF之间的连接。虚拟化业务请求方可以为NFVO或发送者(sender)。发送者具体可以为OSS/BSS。
使用如图1所示的系统，管理设备105通过向NFVO 1011发送NSD查询请求，然后接收来自NFVO 1011的NSD的信息，NSD的信息包括网络服务部署偏好的信息，那么管理设备105可以根据网络服务部署偏好的信息确定实例化参数，从而请求NFVO 1011创建NS实例，无需工作人员通过NFVO1011输入实例化参数，从而降低了通过管理设备105部署NS实例的操作复杂度，同时避免了由于手工输入实例化参数而造成的出错。
在下述实施例中，以管理设备105为OSS/BSS为例进行说明。
图2为本申请实施例提供的一种创建网络服务NS的方法，如图3所示，该方法可以包括：
201、NFVO获取NSD的信息列表，NSD的信息列表包括至少一个NSD的信息。
在一些可能的实现方式中，NSD文件的数据格式可以是数据压缩文件格式zip，zip是一种数据压缩和文档储存的文件格式，通常使用后缀名“.zip”。
在本申请实施例中，NFVO可以接收上传的NSD文件，并解析NSD文件进行解析，得到NSD的信息。NFVO存储该NSD的信息，作为NSD的信息列表中的一个NSD的信息。NSD的信息列表包括至少一个NSD的信息，各NSD的信息可以包括网络服务部署偏好的信息。
在一些可能的实现方式中，NSD的信息可以为在标准《ETSI GS NFV-IFA 014》中NsdInfo的基础上增加了网络服务部署偏好的信息。具体的，NsdInfo的详细内容，请参考标准《ETSI GS NFV-IFA 014》的NsdInfo的信息元素的属性(Table 1:Attributes of the NsdInfo information element)。
示例性的，请参考表2-1，该NSD的信息可以为NsdInfo，该NsdInfo还可以包括NSDF(1..N个)、nsdInfoId(1个)、nsdId(0..1个)和Name(0..1)。
表2-1
Figure PCTCN2021133873-appb-000001
其中，nsdInfoId表示该nsdInfo的标识，即该NSD的信息的标识。nsdId表示已上线的NSD的标识，数量为0或1个(0..1),若该NSD上线了，那么数量为1，否则为0。Name表示该NSD的命名(可以为自然语言的命名，例如“交换机”，也可以为非自然语言的命名，例如“<-->”)，数量为0或1个(0..1),若该NSD上线了，那么数量为1，否则为0；NSDF表示网络服务部署偏好的信息，那么1个或N个(1..N)NSDF表示至少一个网络服务部署偏好的信息。
在标准《ETSI GS NFV-IFA 014》的NsdInfo的信息元素的属性(Table 1:Attributes of the NsdInfo information element)中，NsdInfo还可以包括其他信息，例如version、designer、nestedNsdInfoId、artifacts等信息，此处不做赘述。
下面以一个网络服务部署偏好的信息进行详细说明。
示例性的，网络服务部署偏好的信息可以参考标准《ETSI GS NFV-IFA 014》中的NSDF信息元素属性(Table 6.3.2.2-1:Attributes of the NSDF information element)中所述的内容。具体的，请参考表2-2。
表2-2
Figure PCTCN2021133873-appb-000002
其中，在属性栏中，NSDFId表示该NSDF的标识，数量为1，NSDFId是NSDF的唯一标识；vnfProfile表示vnfProfile的信息，数量为0..N，表示0个或N个vnfProfile的信息；pnfProfile表示pnfProfile的信息，数量为0..N，表示0个或N个pnfProfile的信息。
需要说明的是，一个vnfProfile与一个VNFD对应，用于表示一组VNF实例，这一组VNF实例里的VNF实例都是使用由对应的VNFD进行实例化得到的。OSS/BSS可以查询使用该PNFD进行实例化的一组VNF实例，然后为创建的NS实例选择复用这些VNF实例，也可以根据VnfProfile对应的VNFD创建新的VNF实例。一个pnfProfile与一个PNFD对应，用于表示一组PNF，这一组PNF里的PNF都与该pnfProfile对应的PNFD相关联。OSS/BSS可以查询与该PNFD相关联的一组VNF实例，然后为创建的NS实例选择复用这些PNF。
示例性的，vnfProfile的信息可以参考标准《ETSI GS NFV-IFA 014》中的VnfProfile 信息元素属性(Table 6.3.3.2-1:Attributes of the VnfProfile information element)中所述的内容。具体的，如表2-3所示，vnfProfile包括vnfProfileId和VNFDId，vnfProfileId为vnfProfile的唯一标识，VNFDId即为vnfProfile对应的VNFD的唯一标识。
表2-3
Figure PCTCN2021133873-appb-000003
需要说明的是，VNFD是一个关于VNF的描述信息，也称作VNF的部署模板，其中包含的虚拟部署单元(virtualisation deployment unit，VDU)、连接点(connection point，CP)、虚拟连接(virtual link，VL)等信息，其中VDU可以代表一个安装了应用软件的虚拟机，在VDU的描述中会包含对该虚拟机的所有虚拟资源的需求描述。而CP代表虚拟机上的连接信息，比如可以是虚拟网卡信息，可以采用IP地址或MAC地址来表示。而VL是VNF内连接多个VDU的虚拟连接，可以用连接类型、带宽信息等表示。
示例性的，PnfProfile的信息可以参考标准《ETSI GS NFV-IFA 014》中的PnfProfile信息元素属性(Table 6.3.6.2-1:Attributes of the PnfProfile information element)中所述的内容。具体的，如表2-3所示，PnfProfile包括PnfProfileId和PnfdId，PnfProfileId为PnfProfile的唯一标识，PnfdId即为PnfProfileId对应的PNFD的唯一标识。
表2-4
Figure PCTCN2021133873-appb-000004
需要说明的是，PNFD是一个关于pnf的描述信息，也称作pnf的部署模板。
202、OSS/BSS向NFVO发送NSD查询请求，NSD查询请求用于向NFVO请求NSD的信息。
示例性的，OSS/BSS可以通过Os-Ma-nfvo接口中的“Query NSDGET ns_descriptors”向NFVO发送NSD查询请求。Os-Ma-nfvo是当前NFV系统的常用接口，具体请参考标准gs_nfv_ifa013 7.2.7Query NSD Info operation，此处不作赘述。
示例性的，NSD的信息可以为如表2-1所示的NsdInfo，那么NSD查询请求可以如表2-5所示：
表2-5
Figure PCTCN2021133873-appb-000005
需要说明的是，该NSD查询请求是通过Os-Ma-nfvo接口中的“Query NSDGET ns_descriptor”发送的；而返回参数为“NsdInfo列表”，表示作为NSD的信息列表。
在一些可能的实现方式中，传入参数也可以为一个或多个NsdInfo的标识，表示OSS/BSS向NFVO请求该一个或多个NsdInfo的标识所对应的一个或多个NsdInfo。
203、NFVO向OSS/BSS发送NSD的信息列表，NSD的信息列表包括至少一个NSD的信息。
当NFVO接收到来自OSS/BSS发送的NSD查询请求后，根据NSD查询请求返回NSD的信息列表，NSD的信息列表包括至少一个NSD的信息。
续上述202中的例子，NFVO可以向OSS/BSS返回的NsdInfo列表为NFVO在步骤201中获取所有的NSD的信息列表，也可以在NSD查询请求携带“一个或多个NsdInfo的标识”，那么NFVO向OSS/BSS返回的NsdInfo列表为NFVO在步骤201中获取的NSD的信息列表中，该一个或多个NsdInfo的标识所对应的一个或多个NsdInfo。
204、OSS/BSS从NSD的信息列表中选择NSD的信息，NSD的信息包括网络服务部署偏好的信息列表，网络服务部署偏好的信息列表包括至少一个网络服务部署偏好的信息。
当OSS/BSS接收到NSD的信息列表后，可以根据对NS实例的实际需要选择需要的NSD的信息。例如，当OSS/BSS接收到多个如表2-1所示的NSD的信息列表，若OSS/BSS所需要的NS是下一代移动核心网络(Evolved Packet Core，EPC)服务，那么OSS/BSS可以在NSD的信息列表中搜索命名为EPC服务相关的NSD的信息(例如EPC或下一代移动核心网络服务)，然后选择该NSD的信息。
由于NSD的信息包括至少一个网络服务部署偏好的信息，OSS/BSS还可以根据NSD的信息列表中各个NSD的信息中网络服务部署偏好的信息来判断是否选择该NSD的信息，此处不做限定。
续上述步骤203中的例子，若NSD的信息列表为NsdInfo列表，那么OSS/BSS可以根据创建的NS实例的需要，选择一个NsdInfo，所选择的NsdInfo包括1..N个NSDF，即网络服务部署偏好的信息列表。
205、OSS/BSS从至少一个网络服务部署偏好的信息确定网络服务部署偏好的信息，网络服务部署偏好的信息指示用户对网络服务的部署偏好。
在本申请实施例中，当OSS/BSS获取了至少一个网络服务部署偏好的信息后，可以根据所要部署的NS实例的需要，选择网络服务部署偏好的信息。续上述步骤204的例子，网络服务部署偏好的信息列表可以为如表2-1所示的1..N个NSDF，那么OSS/BSS可以根据所要部署的NS实例的需要，从1..N个NSDF中选择一个。例如，若所要部署的NS实例的主要功能在于存储数据，若某个NSDF可实现存储数据的功能，那么OSS/BSS可以选择该 NSDF。
206、OSS/BSS根据网络服务部署偏好的信息获取NS实例的实例化参数。
需要说明的是，对NS实例需要实例化参数。在一些可能的实现方式中，实例化参数可以包括复用的第一VNF实例的信息，创建第二VNF实例所需要的VPC，和/或创建NS实例所需的PNF。
续上述步骤204的例子，如表2-1所示，OSS/BSS所选择的网络服务部署偏好的信息可以为NSDF，该NSDF包括该NSDF的标识、0..N个vnfProfile的内容和0..N个pnfProfile的信息(如表2-2所示)，每个vnfProfile的信息包括VNFD的标识(如表2-3所示)，每个pnfProfile的信息包括PNFD的标识(如表2-4所示)。其中，OSS/BSS可以根据所创建的NS实例的需要，对于每一个vnfProfile的信息，可以选择复用或创建一个或多个VNF实例。
下面通过举例说明，假设至少一个VNFD的标识包括第一VNFD的标识和/或第二VNFD的标识，OSS/BSS通过第一VNFD的标识选择需要复用的第一VNF实例，OSS/BSS通过第二VNFD的标识创建新的第二VNF实例进行说明。
2061、OSS/BSS根据第一VNFD的标识选择复用的第一VNF实例的信息。
以下通过步骤S21-S23复用的第一VNF实例的信息。
S11、OSS/BSS向NFVO发送VNF查询请求，VNF查询请求携带第一VNFD的标识，VNF查询请求用于向NFVO请求VNF实例的信息。
示例性的，如表2-6所示，该VNF查询请求可以通过Os-Ma-nfvo接口的Query VNFGET vnfs/{VNFDid}发送。其传入参数为VNFDid，表示第一VNFD的标识。返回参数为“VnfInstance[0..N]”，表示VNF实例的信息列表，其中“0..N”表示VNF实例的数量。
表2-6
Figure PCTCN2021133873-appb-000006
S12、NFVO向OSS/BSS发送第一VNF实例的信息列表，第一VNF实例的信息列表包括由第一VNFD进行实例化得到的至少一个VNF实例的信息。
在本申请实施例中，当NFVO接收到VNF查询请求后，根据VNF查询请求中的VNFD的标识，确定使用VNFD进行实例化的至少一个VNF实例的信息，得到第一VNF实例的信息列表，然后向OSS/BSS发送该第一VNF实例的信息列表。在本申请中，使用了VNFD的标识获取到的VNF实例称为第一VNF实例，与第一VNF实例对应的VNFD的标识称为第一VNFD的标识。
续上述步骤S11中的例子，当NFVO接收到如表2-6中的VNF查询请求后，可以从中获取传入参数VNFDid(即第一VNFD的标识)，然后根据VNFDid确定至少一个VNF实例的信息(VnfInstance[0..N])，该至少一个VND实例都是由VNFDid对应的VNFD(即第一VNFD)进行实例化得到的VNF实例，获取这些VNF实例的信息，即得到第一VNF实例的信息列表。然后， NFVO向OSS/BSS发送第一VNF实例的信息列表。
需要说明的是，第一VNF实例的信息列表包括至少一个VNF实例的信息，请参考表2-7：
表2-7
属性 数量 内容 描述
vnfInstanceId 1 标识 VNF实例的标识
vnfName 1 字符串 VNF实例的命名
其中，vnfInstanceId表示一个VNF实例的标识，vnfName表示一个VNF实例的命名(可以为自然语言的命名，例如“交换机”，也可以为非自然语言的命名，例如“<-->”)。
S13、OSS/BSS从第一VNF实例的信息列表中确定第一VNF实例的信息。
当OSS/BSS接收到第一VNF实例的信息列表后，可以从中确定一个或多个VNF实例的信息，作为可复用的第一VNF实例的信息。需要说明的是，“可复用的第一VNF实例”指的是第一VNF实例已经实例化，可以被新建的NS实例选择复用。具体的，“复用”指的是使用已经存在的VNF实例，作为准备创建的NS实例的VNF实例。也就是说，该准备创建的NS实例复用第一VNF实例，表示该NS实例包括该第一VNF实例。
例如，NS实例A是已经存在的NS实例，NS实例B是准备创建的NS实例。NS实例A中的有已经实例化的VNF实例A，当创建NS实例B时，以该VNF实例A作为NS实例B的一个VNF实例，即复用了该VNF实例A。从另一个角度来说，创建NS实例B后，NS实例B中具有一个VNF实例B，该VNF实例B与VNF实例A具有相同的参数和相同的VPC，即VNF实例B与VNF实例A属于同一个VNF实例，即NS实例B复用了VNF实例A。
在一些可能的实现方式中，OSS/BSS可以根据所要部署的NS实例的要求选择一个或多个VNF实例的信息。例如，OSS/BSS可以根据vnfName判断是否要选择该VNF实例。在一些可能的实现方式中，第一VNF实例的信息还可以包括该第一VNF实例的规则、可用资源、业务能力和/或位置等，OSS/BSS也可以根据这些信息的一个或多个判断是否要在NS实例中复用该第一VNF实例。
需要说明的是，由于第一VNF实例的信息列表中的VNF实例的信息的数量是0..N，当其数量为0时，无法从中选择一个，则OSS/BSS可以根据第一VNFD的标识创建第一VNF实例。本申请为了方便，将需要创建的VNF实例称为第二VNF实例，没有获取到VNF实例的VNFD的标识被称为第二VNFD的标识。因此，至少一个VNFD的标识包括第二VNFD的标识。
需要说明的是，当第一VNF实例的信息列表中的VNF实例的信息的数量不等于0时，若第一VNF实例的信息列表中没有合适的VNF实例，OSS/BSS也可以根据第二VNFD的标识创建第二VNF实例，那么OSS/BSS需要获取VPC，然后将第二VNF实例部署到该VPC上。
2062、OSS/BSS根据第二VNFD的标识获取VPC的信息。
以下通过步骤S21-S23获取VPC的信息。
S21、OSS/BSS向NFVO发送VPC查询请求，VPC查询请求用于向NFVO请求VPC的信息。
需要说明的是，创建一个新的VNF实例需要指定VPC，因此OSS/BSS首先需要获取可用的 VPC的信息。
示例性的，该VPC查询请求可以如表2-8所示，通过Os-Ma-nfvo接口中的Query VPCGET vpcs发送，返回参数为String[0..N]，表示其数据类型为字符串String，且数量为0..N，String[0..N]用于表示VPC的信息列表。
表2-8
Figure PCTCN2021133873-appb-000007
在一些可能的实现方式中，VPC查询请求中还可以包括一些限定条件(例如，VPC的资源或位置)，以向NFVO请求具备这些限定条件的VPC的信息。续上述例子，OSS/BSS通过Os-Ma-nfvo接口中的Query VPCGET vpcs发送VPC查询请求，该VPC查询请求中携带VPC的位置(例如深圳或南京)，以向NFVO请求满足该位置的VPC的信息。在一些可能的实现方式中，该VPC查询请求中携带字符串，以向NFVO请求满足该名称具有该字符串的VPC的信息。
S22、NFVO向OSS/BSS发送VPC的信息列表，VPC的信息列表包括至少一个VPC的信息。
在本申请实施例中，当NFVO接收到OSS/BSS发送的VPC查询请求后，即可返回VPC的信息列表，VPC的信息列表包括至少一个VPC的信息，其中，VPC的信息包括名称和标识。其中，VPC的信息中的名称通常根据该VPC的位置来命名，例如深圳-罗湖区-东晓街道。在一些可能的实现方式中，VPC的信息中的名称还可以通过其业务来命名，例如IMS。
续上述例子，OSS/BSS可以通过发送VPC查询请求，请求NFVO向OSS/BSS发送的VPC的信息列表中包括所有可用的VPC的信息。在一些可能的实现方式中，OSS/BSS可以通过发送VPC查询请求，请求NFVO向OSS/BSS发送的VPC的信息列表中携带满足该特定资源或位置的可用的VPC的信息。
S23、OSS/BSS从VPC的信息列表中确定VPC的信息。
当OSS/BSS接收到VPC的信息列表后，可以从中选择一个或多个VPC的信息，作为创建第二VNF实例所使用的VPC。
在一些可能的实现方式中，OSS/BSS可以根据所要部署的NS实例的要求判断是否要选择一个VPC。在一些可能的实现方式中，OSS/BSS可以VPC的信息中的名称来确定是否要选择该VPC。例如，OSS/BSS在深圳，且需要的业务为IMS，那么OSS/BSS可以选择一个名称中有深圳和/或IMS的VPC。
2063、OSS/BSS根据PNFD的标识获取PNF的信息。
需要说明的是，当前的NFV系统可以提供VNF的服务和PNF的服务。其中，PNF为实体硬件的节点，PNF提供了专用设备的服务。在本申请实施例中，NFV系统可以同时提供VNF和/或PNF的服务，以供OSS/BSS进行选择。
例如，NSD中提供了两个VNFD，不提供PNFD，若OSS/BSS选择了该NSD，那么OSS/BSS需要根据两个VNFD分别选择复用的VNF实例，或创建VNF实例，而无需选择复用的PNF。 如果NSD中提供了1个VNFD和一个PNFD，若OSS/BSS选择了该NSD，那么OSS/BSS需要根据1个VNFD选择复用的VNF实例或创建VNF实例，对于PNFD也需要选择复用的PNF。如果NSD中提供了2个PNFD，若OSS/BSS选择了该NSD，那么OSS/BSS需要根据2个PNFD分别选择复用的PNF，而无需选择复用或创建VNF实例。一般来说，在核心网中，对于控制面的功能通常使用VNF实例来部署，对于用户名的功能通常使用PNF来部署。
在本申请实施例中，为此，若OSS/BSS选择的网络服务部署偏好的信息具有pnfprofile，那么OSS/BSS可以获取其中PNFD的标识，并根据PNFD的标识向管理系统EM请求PNF的信息。
以下通过步骤S31-S33获取PNF的信息。
S31、OSS/BSS向设备EM发送PNF查询请求，PNF查询请求携带PNFD的标识，PNF查询请求用于向NFVO请求PNF的信息。
续上述例子，假如网络服务部署偏好的信息为表2-1中的NSDF，该NSDF中包括0..N个pnfProfile，每一个pnfProfile包括pnfProfileId和pnfdId，该pnfdId为PNFD的标识，即至少一个PNFD的标识包括该PNFD的标识。
那么，OSS/BSS可以向EM发送PNF查询请求，PNF查询请求携带一个PNFD的标识，PNF查询请求用于向NFVO请求与该PNFD的标识相关联的PNF的信息。如表2-9所示，该PNF查询请求的传入参数为pnfdid(即该PNFD的标识)，返回参数为pnf[0..N]，用于表示PNF的信息列表，其PNF的信息的数量为0..N。
表2-9
传入参数 返回参数
pnfdid pnf[0..N]
S32、EM向OSS/BSS发送PNF的信息列表，PNF的信息列表包括与PNFD相关联的至少一个PNF的信息。
当EM接收到OSS/BSS发送的PNF查询请求后，可以根据PNF查询请求中PNFD的标识，确定与该第一PNFD的标识相关联的PNF的信息列表，然后向OSS/BSS发送该PNF的信息列表。
续上述例子，EM接收到PNF查询请求后，可以从如表2-9中获取传入参数pnfdid，然后根据pnfdid确定至少一个pnf的信息(pnf[0..N])，该至少一个pnf的信息与pnfdid所标识的PNFD相关联，然后向OSS/BSS发送该至少一个pnf的信息。
示例性的，可以通过标准《ETSI GS NFV-IFA 014》中的字段AddPnfData来表示一个PNF的信息，具体的，为AddPnfData的信息要素属性(Table 8.3.4.32.2-1:Attributes of the AddPnfData information element)。请参考表2-10：
表2-10
属性 数量 内容 描述
pnfId 1 标识 PNF实例的标识
pnfName 1 字符串 PNF实例的命名
pnfdId 1 PNFD的标识 与PNFD相关联的PNF的标识
pnfProfileId 1 pnfProfile的标识 可用的pnfProfile的标识
其中，pnfId表示该PNF的标识，pnfName表示该PNF的命名，pnfdId表示该PNFD的标识，pnfProfileId表示pnfProfile的标识。在一些可能的实现方式中，PNF的信息还包括厂家、版本和类型。
S33、OSS/BSS从PNF的信息列表中确定PNF的信息。
当OSS/BSS接收到PNF的信息列表后，可以根据部署的NS实例的要求，从PNF的信息列表中选择一个或多个PNF的信息。续上述例子，在一些可能的实现方式中，OSS/BSS可以根据PNF的信息中的pnfName判断是否要选择该PNF的信息。pnfName通常携带该PNF的有效信息，例如可以实现的功能，或者所在的城市等，那么OSS/BSS可以根据pnfName确定是否要选用该PNF。在一些可能的实现方式中，OSS/BSS也可以根据PNF的信息中的厂家、版本和类型来判断是否要选用该PNF。
综上所述，通过上述步骤实现了获取部署NS实例所需的实例化参数，即获取可复用的第一VNF实例的信息、创建第二VNF实例所需要的VPC和/或创建NS实例所需的PNF，无需由OSS/BSS解析，节省了计算开销和信令开销，而且无需工作人员通过手工输入实例化参数，从而降低了通过OSS/BSS部署NS实例的操作复杂度，同时避免了由于手工输入实例化参数而造成的出错。
207、OSS/BSS向NFVO发送建立NS实例的请求。
在本申请实施例中，OSS/BSS可以为NS实例命名，然后向NFVO发送创建NS请求，该创建NS请求消息包括网络服务的信息的标识和该NS实例的命名，用于向NFVO请求创建NS实例。
续上述例子，网络服务的信息为nsdinfo，那么OSS/BSS向NFVO发送的创建NS请求中携带nsdinfoid和nsName，示例性的，如表2-11所示，为建立NS实例的ID的请求：
表2-11
Figure PCTCN2021133873-appb-000008
其中，该创建NS请求消息可以通过Os-Ma-nfvo接口中的Create NS Identifier发送，nsdinfoid为选择的NsdInfo的标识，nsName为NS实例的命名。
208、NFVO确定NS实例的标识，并将NS实例的标识发送给OSS/BSS。
当NFVO接收到创建NS请求后，可以根据网络服务的信息的标识确定NSD，并根据NSD创 建NS实例的ID。续上述步骤207中的例子，当NFVO接收到创建NS请求后，将NSD的标识作为NS实例的标识(nsInstanceId)，并以nsName为该NS实例的命名。当NFVO建立NS实例的标识后，向OSS/BSS发送响应消息，该响应消息携带建立的NS实例的标识(nsInstanceId)和该NS实例的命名(nsName)。
209、OSS/BSS向NFVO发送实例化NS的请求，实例化NS的请求中携带NS实例的标识和实例化参数。
在本申请实施例中，当OSS/BSS接收到携带NS实例的标识的响应消息后，然后使用上述步骤206中获取的实例化参数构造实例化NS的请求。
在一些可能的实现方式中，实例化参数可以包括NSDF的标识，以及下述三者的至少一个：第一VNFD的标识和第一VNF实例的信息；第二VNFD的标识和VPC的信息，其中，NSDF包括第二VNFD的标识；PNFD的标识和PNF的信息，其中，NSDF包括PNFD的标识。
举例说明，续表2-1中的例子，实例化NS的请求可以如标准《ETSI GS NFV-IFA 014》中的实例化NS操作的输入参数(Table 7.3.3.2-1:Instantiate NS operation input parameters)，请参考表2-12：
表2-12
Figure PCTCN2021133873-appb-000009
其中，flavourId用于表示NSDF的标识，addPnfData表示PNF的信息，vnfInstanceData表示复用的第一VNF实例的信息，additionalParamForVnf表示创建的第二VNF实例的信息。示例性的，下面分别对AddPnfData、VnfInstanceData、additionalParamForVnf进行示例性说明。
示例性的，AddPnfData可以如标准《ETSI GS NFV-IFA 014》中的AddPnfData信息元素的属性(Table 8.3.4.32.2-1:Attributes of the AddPnfData information element)，请参考表2-13：
表2-13
Figure PCTCN2021133873-appb-000010
其中，pnfId表示pnf的标识，pnfName表示所选用的PNF的自然语言命名，pnfdId表示与该PNFD相关联的PNF的标识，pnfProfileId表示该PNF对应的pnfProfile的标识。
示例性的，VnfInstanceData可以如标准《ETSI GS NFV-IFA 014》中的VnfInstanceData信息元素的属性(Table 8.3.4.3.2-1:Attributes of the VnfInstanceData information element)，请参考表2-14：
表2-14
Figure PCTCN2021133873-appb-000011
其中，vnfInstanceId表示vnfInstance的标识，即第一VNF实例的标识；vnfProfileId表示vnfProfile的标识，即第一VNF实例对应的第一vnfProfile的标识。
示例性的，ParamsForVnf可以如标准《ETSI GS NFV-IFA 014》中的ParamsForVnf信息元素的属性(Table 8.3.4.5.2-1:Attributes of the ParamsForVnf information element)，请参考表2-15：
表2-15
Figure PCTCN2021133873-appb-000012
其中，vnfProfileId表示vnfProfile的标识，即第二VNF实例的标识；additionalParam表示键值对，可以用于携带表示所选用的VPC的信息。
210、NFVO根据实例化参数对NS实例进行实例化。
当NFVO接收到实例化NS的请求后，确定NS实例的标识，然后根据实例化参数对该NS实例进行实例化。具体的实例化过程属于现有技术，此处不做赘述。
211、NFVO向OSS/BSS发送NS实例化成功的响应消息。
本申请实施例中，NFVO在VNF实例化完成以后，向OSS/BSS发送NS实例化成功的响应消息，以完成通过OSS/BSS在NFVO上部署NS实例的过程。之后，OSS/BSS即可通过与NFVO的信令交互使用该NS实例所提供的服务。
在本申请实施例中，OSS/BSS通过向NFVO发送NSD查询请求，然后接收来自NFVO的NSD的信息，NSD的信息包括网络服务部署偏好的信息，那么OSS/BSS可以根据网络服务部署偏好的信息确定实例化参数，从而请求NFVO创建NS实例，无需工作人员通过NFVO输入实例化参数，从而降低了通过OSS/BSS部署NS实例的操作复杂度，同时避免了由于手工输入实例化参数而造成的出错。
上述本申请提供的实施例中，分别从节点(管理设备、通信装置)之间交互的角度对本申请实施例提供的方法进行了介绍。可以理解的是，各个网元，例如管理设备、通信装置为了实现上述本申请实施例提供的方法中的各功能，管理设备、通信装置包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。
本申请实施例可以根据上述方法示例对管理设备、通信装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下，图3示出了上述和实施例中涉及的管理设备的一种可能的组成示意图，该管理设备能执行本申请各方法实施例中OSS/BSS所执行的步骤。如图3所示，该管理设备300可以包括：发送单元301、接收单元302和处理单元303。
其中，发送单元301，用于执行或用于支持管理设备300执行图2所示的方法中OSS/BSS所执行的步骤202、S11、S21、S31、207、209。
接收单元302用于支持管理设备300执行本申请实施例中描述的OSS/BSS所执行的方法。例如，接收单元302，用于执行或用于支持管理设备300执行图2所示的方法中OSS/BSS所执行的步骤203、S12、S22、S32、208和211。
处理单元303用于执行或用于支持管理设备300执行图2所示的方法中OSS/BSS所执行的步骤204、205、S13、S23、S33，使得管理设备300实现选择NSD的信息以及选择该NSD的信息中的网络服务部署偏好的信息，并根据网络服务部署偏好的信息向NFVO发送实例化NS的请求，以请求NFVO创建与NSD相关的NS实例。
在采用对应各个功能划分各个功能模块的情况下，图4示出了上述和实施例中涉及的通信装置的一种可能的组成示意图。如图4所示，该通信装置400能执行本申请各方法实施例中NFVO所执行的步骤。该通信装置400可以包括：接收单元401、发送单元402、处理单元403。
其中，接收单元401用于支持通信装置400执行本申请实施例中描述的NFVO所执行的方法。例如，接收单元401，用于执行或用于支持通信装置400执行图2所示的方法中NFVO所执行的步骤202、S11、S21、S31、207、209。
处理单元403用于支持通信装置400执行本申请实施例中描述的NFVO所执行的方法。例如，处理单元402，用于执行或用于支持通信装置400执行图2所示的方法中NFVO所执行的步骤201和210。
发送单元402，用于执行或用于支持通信装置400执行图2所示的方法中NFVO所执行的203、S12、S22、S32、208、211。
需要说明的是，上述方法实施例涉及的各步骤的所有相关内容均可以对应到对应功能模块的功能描述，在此不再赘述。
本申请实施例提供的管理设备，用于执行上述任意实施例的方法，因此可以达到与上述实施例的方法相同的效果。
如图5所示为本申请实施例提供的管理设备500，用于实现上述方法中OSS/BSS的功能。该管理设备500可以是OSS/BSS或CN NSSMF，也可以是OSS/BSS或CN NSSMF中的装置或功能。此外，该管理设备500可以为芯片系统。本申请实施例中，芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
管理设备500包括至少一个处理器501，用于实现本申请实施例提供的方法中OSS/BSS的设备或其中的装置或功能。示例性地，处理器501可以用于从NSD的信息列表中选择NSD的信息等，具体参见方法示例中的详细描述，此处不做赘述。
管理设备500还可以包括至少一个存储器502，用于存储程序指令和/或数据。存储器502和处理器501耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。处理器501可能和存储器502协同操作。处理器501可能执行存储器502中存储的程序指令。至少一个存储器中的至少一个可以包括于处理器中。
其中，处理器501和存储器502也可以为虚拟化的处理器和虚拟化的存储器。
管理设备500还可以包括通信接口503，用于通过传输介质和其它设备进行通信，从而用于管理设备500中的装置可以和其它设备进行通信。处理器501利用通信接口503收发数据，并用于实现图2对应的实施例中的OSS/BSS所执行的方法。
此外，上述管理设备500中还可以包括网络接口，用于与外部设备进行通信。例如，网络接口用于和用户设备等进行通信。
本申请实施例中不限定上述通信接口503、处理器501以及存储器502之间的具体连接介质。本申请实施例在图5中以通信接口503、处理器501以及存储器502之间通过总线504连接，总线在图5中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明， 并不引以为限。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图5中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
本申请实施例提供的通信装置，用于执行上述任意实施例的方法，因此可以达到与上述实施例的方法相同的效果。
如图6所示为本申请实施例提供的通信装置600，用于实现上述方法中NFVO的功能。该通信装置600可以是NFVO，也可以是NFVO中的装置或功能。此外，该通信装置600可以为芯片系统。本申请实施例中，芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
通信装置600包括至少一个处理器601，用于实现本申请实施例提供的方法中NFVO的功能。示例性地，处理器601可以用于根据实例化NS的请求创建与NSD相关的NS实例等，具体参见方法示例中的详细描述，此处不做赘述。
通信装置600还可以包括至少一个存储器602，用于存储程序指令和/或数据。存储器602和处理器601耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。处理器601可能和存储器602协同操作。处理器601可能执行存储器602中存储的程序指令。至少一个存储器中的至少一个可以包括于处理器中。
其中，处理器601和存储器602也可以为虚拟化的处理器和虚拟化的存储器。
通信装置600还可以包括通信接口603，用于通过传输介质和其它设备进行通信，从而用于通信装置600中的装置可以和其它设备进行通信，例如管理设备500。处理器601利用通信接口603收发数据，并用于实现图2对应的实施例中的NFVO所执行的方法。
此外，上述通信装置600中还可以包括网络接口，用于与外部设备进行通信。例如，网络接口用于和管理设备500等进行通信。
本申请实施例中不限定上述通信接口603、处理器601以及存储器602之间的具体连接介质。本申请实施例在图6中以通信接口603、处理器601以及存储器602之间通过总线604连接，总线在图6中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图6中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在本申请实施例中，处理器可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
在本申请实施例中，存储器可以是非易失性存储器，比如硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)等，还可以是易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)。存储器是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。 本申请实施例中的存储器还可以是电路或者其它任意能够实现存储功能的装置，用于存储程序指令和/或数据。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个装置，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是一个物理单元或多个物理单元，即可以位于一个地方，或者也可以分布到多个不同地方。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
本申请实施例提供的方法中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本发明实施例的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、网络设备、终端或者其他可编程装置。计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机可以存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，数字视频光盘(digital video disc，DVD))、或者半导体介质等。

Claims (41)

  1. 一种创建网络服务NS的方法，其特征在于，包括：
    管理设备向网络功能虚拟化编排器NFVO发送网络服务描述NSD查询请求，所述NSD查询请求用于向所述NFVO请求NSD的信息；
    所述管理设备接收所述NFVO发送的所述NSD的信息，所述NSD的信息包括网络服务部署偏好的信息，所述网络服务部署偏好的信息指示用户对网络服务的部署偏好；
    所述管理设备根据所述网络服务部署偏好的信息向NFVO发送实例化NS的请求，以请求所述NFVO创建与所述NSD相关的NS实例。
  2. 根据权利要求1所述方法，其特征在于，所述管理设备接收所述NFVO发送的所述NSD的信息包括：所述管理设备接收所述NFVO发送的所述NSD的信息列表，所述NSD的信息列表包括至少一个NSD的信息；所述方法进一步包括：
    所述管理设备从所述NSD的信息列表中选择所述NSD的信息。
  3. 根据权利要求1或2所述方法，其特征在于，所述NSD的信息包括至少一个网络服务部署偏好的信息，所述方法还包括：
    所述管理设备从所述至少一个网络服务部署偏好的信息中选择所述网络服务部署偏好的信息。
  4. 根据权利要求1-3中任一项所述方法，其特征在于，所述网络服务部署偏好的信息包括网络服务部署偏好NSDF的标识、至少一个虚拟化网络功能描述VNFD的标识和/或至少一个物理网络功能描述PNFD的标识。
  5. 根据权利要求4所述方法，其特征在于，所述至少一个VNFD的标识包括第一VNFD的标识，所述方法进一步包括：
    所述管理设备根据所述第一VNFD的标识获取第一虚拟网络功能VNF实例的信息；
    所述实例化NS的请求包括所述NSDF的标识、所述第一VNFD的标识和所述第一VNF实例的信息。
  6. 根据权利要求5所述方法，其特征在于，所述管理设备根据所述第一VNFD的标识获取第一VNF实例的信息包括：
    所述管理设备向所述NFVO发送VNF查询请求，所述VNF查询请求携带所述第一VNFD的标识，所述VNF查询请求用于向所述NFVO请求VNF实例的信息；
    所述管理设备接收来自所述NFVO的第一VNF实例的信息列表，所述第一VNF实例的信息列表包括由所述第一VNFD进行实例化得到的至少一个VNF实例的信息；
    所述管理设备从所述第一VNF实例的信息列表中确定所述第一VNF实例的信息。
  7. 根据权利要求4-6中任一项所述方法，其特征在于，所述至少一个VNFD的标识包括第二VNFD的标识，所述方法进一步包括：
    所述管理设备获取虚拟私有云VPC的信息，所述VPC用于部署根据所述第二VNFD创建的第二VNF实例；
    所述实例化NS请求进一步包括所述第二VNFD的标识和所述VPC的信息。
  8. 根据权利要求7所述方法，其特征在于，所述管理设备获取VPC的信息包括：所述管理设备向所述NFVO发送VPC查询请求，所述VPC查询请求用于向所述NFVO请求VPC的 信息；
    所述管理设备接收来自所述NFVO的VPC列表，所述VPC列表包括至少一个VPC的信息；
    所述管理设备从所述VPC列表中确定所述VPC的信息。
  9. 根据权利要求4-8中任一项所述方法，其特征在于，所述方法进一步包括：
    所述管理设备根据所述至少一个PNFD的标识获取PNF的信息；
    所述实例化NS请求进一步包括所述PNFD的标识和所述PNFD的标识指示的所述PNF的信息。
  10. 根据权利要求9所述方法，其特征在于，所述管理设备根据所述至少一个PNFD的标识获取PNF的信息包括：
    所述管理设备向设备管理系统EM发送PNF查询请求，所述PNF查询请求携带所述PNFD的标识，所述PNF查询请求用于向所述NFVO请求与所述PNFD相关联的PNF的信息；
    所述管理设备接收来自所述EM的PNF列表，所述PNF列表包括与所述PNFD相关联的至少一个PNF的信息；
    所述管理设备从所述PNF列表中确定所述PNF的信息。
  11. 根据权利要求1-10中任一项所述方法，其特征在于，所述管理设备为运营支持系统和/或业务支持系统OSS/BSS或核心网切片管理CN NSSMF。
  12. 一种创建网络服务NS的方法，其特征在于，包括：
    网络功能虚拟化编排器NFVO接收管理设备发送的网络服务描述NSD查询请求，所述NSD查询请求用于向所述NFVO请求NSD的信息；
    所述NFVO向所述管理设备发送所述NSD的信息，所述NSD的信息包括网络服务部署偏好的信息，所述网络服务部署偏好的信息指示用户对网络服务的部署偏好；
    所述NFVO接收所述管理设备根据所述网络服务部署偏好的信息发送的实例化NS的请求；
    所述NFVO根据所述实例化NS的请求创建与所述NSD相关的NS实例。
  13. 根据权利要求12所述方法，其特征在于，所述NFVO向所述管理设备发送所述NSD的信息包括：
    所述NFVO向所述管理设备发送所述NSD的信息列表，所述NSD的信息列表包括至少一个NSD的信息，以使得所述管理设备从所述NSD的信息列表中确定所述NSD的信息。
  14. 根据权利要求12或13所述方法，其特征在于，所述NSD的信息包括至少一个网络服务部署偏好的信息，以使得所述管理设备从所述至少一个网络服务部署偏好的信息中确定所述网络服务部署偏好的信息。
  15. 根据权利要求12-14中任一项所述方法，其特征在于，所述网络服务部署偏好的信息包括网络服务部署偏好NSDF的标识、至少一个虚拟化网络功能描述VNFD的标识和/或至少一个物理网络功能描述PNFD的标识。
  16. 根据权利要求15所述方法，其特征在于，所述至少一个VNFD的标识包括第一VNFD的标识，所述方法进一步包括：
    所述NFVO接收所述管理设备发送的VNF查询请求，所述VNF查询请求携带所述第一VNFD的标识，所述VNF查询请求用于向所述NFVO请求VNF实例的信息；
    所述NFVO向所述管理设备发送第一VNF实例的信息列表，所述第一VNF实例的信息列表包括由所述第一VNFD进行实例化得到的至少一个VNF实例的信息；
    所述实例化NS的请求包括所述NSDF的标识、所述第一VNFD的标识和所述第一VNF实例的信息。
  17. 根据权利要求15或16所述方法，其特征在于，所述至少一个VNFD的标识包括第二VNFD的标识，所述方法进一步包括：
    所述NFVO接收所述管理设备发送的VPC查询请求，所述VPC查询请求用于向所述NFVO请求VPC的信息；
    所述NFVO向所述管理设备发送VPC列表，所述VPC列表包括至少一个VPC的信息，以使得所述管理设备从所述VPC列表中确定所述VPC的信息，所述VPC用于部署根据所述第二VNFD创建的第二VNF实例；
    所述实例化NS请求进一步包括所述第二VNFD的标识和所述VPC的信息。
  18. 根据权利要求15-17中任一项所述方法，其特征在于，所述实例化NS请求进一步包括所述PNFD的标识和/或所述PNFD指示的PNF的信息。
  19. 一种管理设备，其特征在于，包括：
    发送单元，用于向网络功能虚拟化编排器NFVO发送网络服务描述NSD查询请求，所述NSD查询请求用于向所述NFVO请求NSD的信息；
    接收单元，用于接收所述NFVO发送的所述NSD的信息，所述NSD的信息包括网络服务部署偏好的信息，所述网络服务部署偏好的信息指示用户对网络服务的部署偏好；
    处理单元，用于根据所述网络服务部署偏好的信息向NFVO发送实例化NS的请求，以请求所述NFVO创建与所述NSD相关的NS实例。
  20. 根据权利要求19所述管理设备，其特征在于，
    所述接收单元，具体用于接收所述NFVO发送的所述NSD的信息列表，所述NSD的信息列表包括至少一个NSD的信息；
    所述处理单元，用于从所述NSD的信息列表中选择所述NSD的信息。
  21. 根据权利要求19或20所述管理设备，其特征在于，所述NSD的信息包括至少一个网络服务部署偏好的信息，
    所述处理单元，还用于从所述至少一个网络服务部署偏好的信息中选择所述网络服务部署偏好的信息。
  22. 根据权利要求19-21中任一项所述管理设备，其特征在于，所述网络服务部署偏好的信息包括网络服务部署偏好NSDF的标识、至少一个虚拟化网络功能描述VNFD的标识和/或至少一个物理网络功能描述PNFD的标识。
  23. 根据权利要求22所述管理设备，其特征在于，所述至少一个VNFD的标识包括第一VNFD的标识，所述处理单元进一步用于，根据所述第一VNFD的标识获取第一虚拟网络功能VNF实例的信息；
    所述实例化NS的请求包括所述NSDF的标识、所述第一VNFD的标识和所述第一VNF实例的信息。
  24. 根据权利要求23所述管理设备，其特征在于，
    所述发送单元，还用于向所述NFVO发送VNF查询请求，所述VNF查询请求携带所述第一VNFD的标识，所述VNF查询请求用于向所述NFVO请求VNF实例的信息；
    所述接收单元，还用于接收来自所述NFVO的第一VNF实例的信息列表，所述第一VNF实例的信息列表包括由所述第一VNFD进行实例化得到的至少一个VNF实例的信息；
    所述处理单元，还用于从所述第一VNF实例的信息列表中确定所述第一VNF实例的信息。
  25. 根据权利要求22-24中任一项所述管理设备，其特征在于，所述至少一个VNFD的标识包括第二VNFD的标识，
    所述处理单元，还用于获取虚拟私有云VPC的信息，所述VPC用于部署根据所述第二VNFD创建的第二VNF实例；
    所述实例化NS请求进一步包括所述第二VNFD的标识和所述VPC的信息。
  26. 根据权利要求25所述管理设备，其特征在于，
    所述发送单元，还用于向所述NFVO发送VPC查询请求，所述VPC查询请求用于向所述NFVO请求VPC的信息；
    所述接收单元，还用于接收来自所述NFVO的VPC列表，所述VPC列表包括至少一个VPC的信息；
    所述处理单元，还用于从所述VPC列表中确定所述VPC的信息。
  27. 根据权利要求22-26中任一项所述管理设备，其特征在于，
    所述处理单元，还用于根据所述至少一个PNFD的标识获取PNF的信息；
    所述实例化NS请求进一步包括所述PNFD的标识和所述PNF的信息。
  28. 根据权利要求27所述管理设备，其特征在于，
    所述发送单元，还用于向设备管理系统EM发送PNF查询请求，所述PNF查询请求携带所述PNFD的标识，所述PNF查询请求用于向所述NFVO请求与所述PNFD相关联的PNF的信息；
    所述接收单元，还用于接收来自所述EM的PNF列表，所述PNF列表包括与所述PNFD相关联的至少一个PNF的信息；
    所述处理单元，还用于从所述PNF列表中确定所述PNF的信息。
  29. 根据权利要求19-28中任一项所述管理设备，其特征在于，所述管理设备为运营支持系统和/或业务支持系统OSS/BSS或核心网切片管理CN NSSMF。
  30. 一种通信装置，其特征在于，包括：
    接收单元，用于接收管理设备发送的网络服务描述NSD查询请求，所述NSD查询请求用于向所述NFVO请求NSD的信息；
    发送单元，用于向所述管理设备发送所述NSD的信息，所述NSD的信息包括网络服务部署偏好的信息，所述网络服务部署偏好的信息指示用户对网络服务的部署偏好；
    所述接收单元，还用于接收所述管理设备根据所述网络服务部署偏好的信息发送的实例化NS的请求；
    处理单元，用于根据所述实例化NS的请求创建与所述NSD相关的NS实例。
  31. 根据权利要求30所述通信装置，其特征在于，
    所述发送单元，还用于向所述管理设备发送所述NSD的信息列表，所述NSD的信息列表包括至少一个NSD的信息，以使得所述管理设备从所述NSD的信息列表中确定所述NSD的信息。
  32. 根据权利要求30或31所述通信装置，其特征在于，所述NSD的信息包括至少一个网络服务部署偏好的信息，以使得所述管理设备从所述至少一个网络服务部署偏好的信息中确定所述网络服务部署偏好的信息。
  33. 根据权利要求30-32中任一项所述通信装置，其特征在于，所述网络服务部署偏好的信息包括网络服务部署偏好NSDF的标识、至少一个虚拟化网络功能描述VNFD的标识和/或至少一个物理网络功能描述PNFD的标识。
  34. 根据权利要求33所述通信装置，其特征在于，所述至少一个VNFD的标识包括第一VNFD的标识，
    所述接收单元，还用于接收所述管理设备发送的VNF查询请求，所述VNF查询请求携带所述第一VNFD的标识，所述VNF查询请求用于向所述NFVO请求VNF实例的信息；
    所述发送单元，还用于向所述管理设备发送第一VNF实例的信息列表，所述第一VNF实例的信息列表包括由所述第一VNFD进行实例化得到的至少一个VNF实例的信息；
    所述实例化NS的请求包括所述NSDF的标识、所述第一VNFD的标识和所述第一VNF实例的信息。
  35. 根据权利要求33或34所述通信装置，其特征在于，所述至少一个VNFD的标识包括第二VNFD的标识，
    所述接收单元，还用于接收所述管理设备发送的VPC查询请求，所述VPC查询请求用于向所述NFVO请求VPC的信息；
    所述发送单元，还用于向所述管理设备发送VPC列表，所述VPC列表包括至少一个VPC的信息，以使得所述管理设备从所述VPC列表中确定所述VPC的信息，所述VPC用于部署根据所述第二VNFD创建的第二VNF实例；
    所述实例化NS请求进一步包括所述第二VNFD的标识和所述VPC的信息。
  36. 根据权利要求33-35中任一项所述通信装置，其特征在于，所述至少一个PNFD包括PNFD，所述实例化NS请求进一步包括所述PNFD的标识和PNF的信息。
  37. 一种管理设备，其特征在于，包括：至少一个处理器、存储器、总线和收发器，其中，所述存储器用于存储计算机程序，使得所述计算机程序被所述至少一个处理器执行时实现如权利要求1至11中任一项所述的方法。
  38. 一种通信装置，其特征在于，包括：至少一个处理器、存储器、总线和收发器，其中，所述存储器用于存储计算机程序，使得所述计算机程序被所述至少一个处理器执行时实现如权利要求12至18中任一项所述的方法。
  39. 一种计算机可读存储介质，其特征在于，包括：计算机软件指令；
    当所述计算机软件指令在管理设备或内置在通信装置的芯片中运行时，使得所述管理设备执行如权利要求1至11中任一项所述的方法。
  40. 一种计算机可读存储介质，其特征在于，包括：计算机软件指令；
    当所述计算机软件指令在通信装置或内置在通信装置的芯片中运行时，使得所述通信 装置执行如权利要求12至18中任一项所述的方法。
  41. 一种系统，其特征在于，包括如权利要求19-29任一所述的管理设备和30-36任一所述的通信装置。
PCT/CN2021/133873 2021-03-04 2021-11-29 一种创建网络服务ns的方法及相关装置 WO2022183796A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US18/240,433 US20230409371A1 (en) 2021-03-04 2023-08-31 Method for creating network service ns and related apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110239645.0A CN115037788A (zh) 2021-03-04 2021-03-04 一种创建网络服务ns的方法及相关装置
CN202110239645.0 2021-03-04

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/240,433 Continuation US20230409371A1 (en) 2021-03-04 2023-08-31 Method for creating network service ns and related apparatus

Publications (1)

Publication Number Publication Date
WO2022183796A1 true WO2022183796A1 (zh) 2022-09-09

Family

ID=83118208

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/133873 WO2022183796A1 (zh) 2021-03-04 2021-11-29 一种创建网络服务ns的方法及相关装置

Country Status (3)

Country Link
US (1) US20230409371A1 (zh)
CN (1) CN115037788A (zh)
WO (1) WO2022183796A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180324261A1 (en) * 2017-05-08 2018-11-08 Electronics And Telecommunications Research Institute Method of network service descriptor management in a network functions virtualization
CN110447208A (zh) * 2017-03-19 2019-11-12 华为技术有限公司 一种网络切片的管理方法、单元和系统
CN111371578A (zh) * 2018-12-26 2020-07-03 华为技术有限公司 部署虚拟化网络功能的方法和装置
CN112187545A (zh) * 2018-03-29 2021-01-05 华为技术有限公司 一种网络切片的部署方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110447208A (zh) * 2017-03-19 2019-11-12 华为技术有限公司 一种网络切片的管理方法、单元和系统
US20180324261A1 (en) * 2017-05-08 2018-11-08 Electronics And Telecommunications Research Institute Method of network service descriptor management in a network functions virtualization
CN112187545A (zh) * 2018-03-29 2021-01-05 华为技术有限公司 一种网络切片的部署方法及装置
CN111371578A (zh) * 2018-12-26 2020-07-03 华为技术有限公司 部署虚拟化网络功能的方法和装置

Also Published As

Publication number Publication date
US20230409371A1 (en) 2023-12-21
CN115037788A (zh) 2022-09-09

Similar Documents

Publication Publication Date Title
US11283684B2 (en) Network slice deployment method and apparatus
WO2018170647A1 (zh) 一种网络切片的管理方法、单元和系统
EP3291499A1 (en) Method and apparatus for network service capacity expansion
WO2017162089A1 (zh) 网络服务的业务配置方法和装置
US20210289435A1 (en) Virtualization management method and apparatus
US20220350637A1 (en) Virtual machine deployment method and related apparatus
EP4109251A1 (en) Vnf instantiation method and device
US20210326306A1 (en) Method and apparatus for deploying virtualised network function
WO2021175105A1 (zh) 连接方法、装置、设备和存储介质
US11683222B2 (en) Virtual network function VNF deployment method and apparatus
WO2022183796A1 (zh) 一种创建网络服务ns的方法及相关装置
EP4191907A1 (en) Vnf instantiation method and apparatus
WO2021022947A1 (zh) 一种部署虚拟机的方法及相关装置
CN112889247B (zh) Vnf服务实例化方法及装置
US20230105269A1 (en) Virtualized network service deployment method and apparatus
WO2021129868A1 (zh) 网络服务实例化的方法及网络功能虚拟化编排器
EP4322494A1 (en) Data transmission method, apparatus and system
US20230259387A1 (en) Data flow mirroring method and apparatus
CN112887137B (zh) 接口索引一致性的实现方法及装置
CN113098705B (zh) 网络业务的生命周期管理的授权方法及装置
US20230328535A1 (en) Data delivery automation of a cloud-managed wireless telecommunication network
US20230327959A1 (en) Method for establishing network connection and apparatus
US20230362065A1 (en) Scaling Method 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: 21928868

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: 21928868

Country of ref document: EP

Kind code of ref document: A1