WO2018214965A1 - 无线网络功能虚拟化方法及装置 - Google Patents

无线网络功能虚拟化方法及装置 Download PDF

Info

Publication number
WO2018214965A1
WO2018214965A1 PCT/CN2018/088446 CN2018088446W WO2018214965A1 WO 2018214965 A1 WO2018214965 A1 WO 2018214965A1 CN 2018088446 W CN2018088446 W CN 2018088446W WO 2018214965 A1 WO2018214965 A1 WO 2018214965A1
Authority
WO
WIPO (PCT)
Prior art keywords
virtual
dedicated hardware
virtual network
information
resource
Prior art date
Application number
PCT/CN2018/088446
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 中兴通讯股份有限公司
Priority to EP18805298.9A priority Critical patent/EP3633956B1/en
Publication of WO2018214965A1 publication Critical patent/WO2018214965A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • 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
    • 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/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/02—Resource partitioning among network components, e.g. reuse partitioning
    • H04W16/10—Dynamic resource partitioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/02—Resource partitioning among network components, e.g. reuse partitioning
    • H04W16/12—Fixed resource partitioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities

Definitions

  • the present disclosure relates to a wireless communication access network system side device, and in particular, to a wireless network function virtualization method and apparatus.
  • NFV Network Function Virtualization
  • computing hardware such as Central Processing Unit (CPU)
  • storage hardware disk
  • general hardware resources usually referred to as general-purpose processors based on the X86 architecture), such as the magnetic array
  • network hardware such as the Internet
  • virtualization technology such as Intel VT
  • dedicated hardware can be incorporated into the NFV reference model as a virtualized or non-virtualized acceleration resource, using the virtualization foundation of the Management and Orchestration (MANO) domain in the NFV reference model.
  • Management and distribution of Virtualization Infrastructure Management (VIM) In this case, the characteristics of various dedicated devices of the radio access network are completely exposed to the MANO domain, which may result in a significant increase in the complexity of the MANO domain.
  • An embodiment of the present disclosure provides a method for virtualizing a wireless network function, including: determining a virtual dedicated hardware resource corresponding to a wireless access device; and instantiating a plurality of virtual network services of the wireless access network to obtain the virtual Virtual private hardware resource information corresponding to the network service and information for cell coverage processing; and according to the virtual dedicated hardware resource information and information for cell coverage processing, for each virtual network service, using each virtual network service module to execute operating.
  • the embodiment of the present disclosure provides a wireless network function virtualization device, including: a determining module, configured to determine a virtual dedicated hardware resource corresponding to the wireless access device; and an instantiation processing module configured to be more for the wireless access network Virtual network services are instantiated to obtain virtual private hardware resource information corresponding to the virtual network service and information for cell coverage processing; and an execution module configured to be based on the virtual dedicated hardware resource information and The information of the cell coverage processing is performed for each virtual network service using each virtual network service module.
  • Embodiments of the present disclosure also provide a computer readable medium storing computer readable instructions that, when executed by a processor, cause the processor to perform a wireless network function virtualization method in accordance with the present disclosure.
  • FIG. 1 is a flowchart of a method for virtualizing a wireless network function according to an embodiment of the present disclosure
  • FIG. 2 is a schematic diagram of a wireless network function virtualization device according to an embodiment of the present disclosure
  • FIG. 3 is a schematic diagram of virtualization of a network function of a radio access network of dedicated hardware provided by an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram of a virtualized network function access MANO of a radio access network of dedicated hardware provided by an embodiment of the present disclosure
  • FIG. 5 is a schematic diagram of a network function virtualization device of a radio access network with dedicated hardware provided by an embodiment of the present disclosure.
  • the wireless communication access network usually includes: a Radio Resource Control (RRC) unit, and a second layer L2 (including a Packet Data Convergence Protocol (PDCP)/Radio Link Control (Radio Link Control).
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • Radio Link Control Radio Link Control
  • RLC Packet Data Convergence Protocol
  • MAC Multiple Access Control
  • PHY Physical Layer
  • RF Radio Frequency
  • ASIC Application Specific Integrated Circuit
  • dedicated hardware can be incorporated into the NFV reference model as a virtualized or non-virtualized acceleration resource.
  • the Guest OS and the deployed software system are unaware of whether the hardware used is physical or virtual, and the usual network functional units (for example, IP Multimedia Subsystem (IMS), mobility management Entity (Mobile Management Entity, MME), etc. can be implemented using this Guest OS environment to save hardware investment and improve hardware efficiency.
  • IMS IP Multimedia Subsystem
  • MME Mobile Management Entity
  • FIG. 1 is a flowchart of a method for virtualizing a wireless network function according to an embodiment of the present disclosure.
  • the wireless network function virtualization method includes steps S101-S103.
  • a virtual dedicated hardware resource corresponding to the wireless access device is determined.
  • a plurality of virtual network services of the radio access network are instantiated to obtain virtual dedicated hardware resource information corresponding to the virtual network service and information for cell coverage processing.
  • step S103 operations are performed for each virtual network service using respective virtual network service modules based on the virtual dedicated hardware resource information and information for cell coverage processing.
  • the wireless access device is a device for virtualizing a network function of the wireless access network, and wherein the step S101 of determining a virtual dedicated hardware resource corresponding to the wireless access device includes Determining a virtual dedicated hardware resource for the virtualization corresponding to a dedicated hardware resource of the wireless access device.
  • the step S101 of determining a virtual dedicated hardware resource corresponding to the wireless access device further includes: a used attribute of the sector antenna entity and the antenna unit according to a dedicated hardware topology planned in the wireless access device, and each The radio frequency connection of the Radio Remote Unit (RRU), combined with the abstract model description file of the dedicated hardware, abstracts the virtual sector resources used to complete the RF network function; according to the dedicated hardware topology planning in the wireless access device Baseband Processing Unit (BPU) of the baseband processing pool, combined with abstract model description files of dedicated hardware, abstracting virtual baseband processing pool resources for completing PHY network functions and partial network functions of L2; according to wireless access
  • the general processing unit (GPU) of the general processing pool of the dedicated hardware topology planning in the device combined with the abstract model description file of the dedicated hardware, abstracts the virtual general processing for completing the RRC network function and part of the network function of the L2. Pool resources; and according to dedicated hardware topology rules in wireless access devices Sector, BPU, GPU and chassis type, and binding dedicated hardware abstraction model description file
  • the step S102 of performing instantiation processing on multiple virtual network services of the radio access network to obtain virtual dedicated hardware resource information corresponding to the virtual network service and information for cell coverage processing includes : using an abstract model description file of the dedicated hardware of the wireless access device and a model description file of the virtual network function service, instantiating a plurality of virtual network services of the wireless access network to obtain a virtual corresponding to the virtual network service Dedicated hardware resource information and information for cell coverage processing.
  • the abstract model description file of the dedicated hardware may include: a dedicated hardware model, standardized usage interface metadata, dedicated hardware capability description information, and version number information
  • the model description file of the virtual network function service may include: virtual network function The service name, standardized access interface definition metadata, service capability description information, and version number information.
  • the step of instantiating a plurality of virtual network services of the radio access network to obtain virtual private hardware resource information corresponding to the virtual network service and information for cell coverage processing includes: Applying resources to be used by the virtual network service, and returning a resource allocation result, where the resource allocation result includes virtual dedicated hardware resource information corresponding to the virtual network service and information used for cell coverage processing.
  • step S103 of using each virtual network service module to perform operations for each virtual network service includes: using each virtual network service The module initiates a cell resource change process, or uses each virtual network service module to initiate a cell resource release process, or uses each virtual network service module to initiate a fault resource self-healing process.
  • FIG. 2 is a schematic diagram of a wireless network function virtualization apparatus according to an embodiment of the present disclosure.
  • the wireless network function virtualization device includes a determining module 201, an instantiation processing module 202, and an execution module 203.
  • the determining module 201 is configured to determine a virtual dedicated hardware resource corresponding to the wireless access device.
  • the instantiation processing module 202 is configured to instantiate a plurality of virtual network services of the radio access network to obtain virtual dedicated hardware resource information corresponding to the virtual network service and information for cell coverage processing.
  • the execution module 203 is configured to perform operations using the respective virtual network service modules for each virtual network service according to the virtual dedicated hardware resource information and information for cell coverage processing.
  • the wireless access device is a device for virtualizing a network function of the wireless access network, and wherein the determining module 201 is further configured to determine a dedicated use of the wireless access device A virtual dedicated hardware resource for the virtualization corresponding to the hardware resource.
  • the instantiation processing module 202 is further configured to utilize the abstract model description file of the dedicated hardware of the wireless access device and the model description file of the virtual network function service to serve multiple virtual networks of the wireless access network.
  • the instantiation processing is performed to obtain virtual dedicated hardware resource information corresponding to the virtual network service and information for cell coverage processing.
  • the abstract model description file of the dedicated hardware may include: a dedicated hardware model, standardized usage interface metadata, dedicated hardware capability description information, and version number information
  • the model description file of the virtual network function service may include: a virtual network The function service name, the standardized access interface definition metadata, the service capability description information, and the version number information.
  • the instantiation processing module 202 is further configured to apply for a resource to be used by the virtual network service, and return a resource allocation result, where the resource allocation result includes a virtual private corresponding to the virtual network service.
  • the execution module 203 is further configured to initiate a cell resource change procedure using each virtual network service module, or initiate a cell resource release procedure using each virtual network service module, or initiate using a respective virtual network service module.
  • the fault resource self-healing process is further configured to initiate a cell resource change procedure using each virtual network service module, or initiate a cell resource release procedure using each virtual network service module, or initiate using a respective virtual network service module.
  • FIG. 3 is a schematic diagram of virtualization of network functions of a radio access network of dedicated hardware provided by an embodiment of the present disclosure.
  • the dedicated hardware of the radio access network device of the embodiment of the present disclosure includes an antenna (Antenna), an RRU, a BPU, and a GPU and a chassis (including a backplane of a high-speed communication bus), wherein the RRU mainly performs the RF function.
  • the BPU mainly performs PHY and/or L2 functions.
  • the GPU performs the functions of RRC and/or L2 part network functions and operation and maintenance, and the chassis mainly completes the high-speed communication function.
  • a wireless access network device has only a small amount of storage functions for operation and maintenance, and does not have a function of a service storage (except for a disk, a random access memory (RAM)).
  • a number of antennas and a number of RRUs may be abstracted into virtual sector vSector resources, providing coverage-related attribute sets including power, frequency bands, channel numbers, etc., to complete RF network functions.
  • a set of available overlay virtual connectors vCoverage with the same vSector resource tag can be used directly by the cell/carrier.
  • a plurality of BPUs may be abstracted into a virtual baseband processing pool vBPPool resource, and a set of attributes related to a baseband protocol, such as a number of connected users, a number of carriers, and a number of channels, may be provided to complete a PHY network function and a partial network of L2.
  • a set of baseband computing resources vBCP with the same vBPPool resource tag can be used directly by the cell/carrier.
  • a plurality of GPUs may be abstracted into a virtual general-purpose processing pool vGPPool resource, and a set of attributes related to a high-level protocol, such as a number of connected users, a number of bearers, and a number of cells/carriers, may be provided to complete the RRC network function and the L2. Part of the network function.
  • a set of higher layer computing resources vHCP with the same vGPPool resource label can be used directly by the cell/carrier.
  • the high-speed communication interface of the chassis backplane can be abstracted into a vConnector resource, providing a set of attributes related to high-speed communication including connection topology, bandwidth, delay, priority, reliability, etc., to complete high-speed communication functions.
  • a set of communication connection path resources vPath with the same vConnector resource label can be used directly by the cell/carrier.
  • the vSector, vBPPool, vGPPool, and vConnector respectively provide standard usage interfaces and capability description information by an abstraction layer of their dedicated hardware. At the abstraction level, the differences in dedicated hardware are normalized to standard usage interfaces and capability description information.
  • the capability description information includes resource attributes, resource architecture, deployment constraints, affinity relationships, and resource capability version numbers.
  • the extended VIM can be accessed into the MANO common platform conforming to the ETSI specification to provide a standard management interface to the upper layer virtualized network function manager (VNF Manager, VNFM).
  • VNF Manager VNF Manager
  • the virtual network function services of the wireless access network include: virtual radio resource control (vRRCs), virtual baseband processing (vBPs), and virtual radio frequency quantification (vRFs).
  • the network function service provides standardized access interface definitions and service capability description information by a dedicated hardware resource allocation module.
  • the service capability description information includes the type/quantity/architecture requirement, affinity relationship, deployment constraint, and service capability version number of the resource.
  • FIG. 4 is a schematic diagram of a virtualized network function accessing MANO of a radio access network of dedicated hardware provided by an embodiment of the present disclosure.
  • the VNFM interface can be used to access the MANO common platform conforming to the ETSI plan, and the dedicated hardware and network function service instances are provided.
  • the relationship can be accessed through the VIM interface to the MANO common platform conforming to the ETSI plan to provide a standard management interface for the upper layer NFV Orchestrator (NFVO).
  • NFVO NFV Orchestrator
  • FIG. 5 is a schematic diagram of a network function virtualization device of a radio access network with dedicated hardware provided by an embodiment of the present disclosure.
  • the network function virtualization device may include a network management module, a MANO universal platform, a hardware BIOS, a dedicated hardware abstraction layer, and a dedicated hardware manager.
  • the network management module is configured to initiate an instantiation process and a de-instantiation process to the MANO universal platform; send cell radio parameters to vRRCs, vBPs, and vRFs; import dedicated hardware planning data; import abstract model description files of dedicated hardware, and virtual network functions. Model description file for the service.
  • the MANO universal platform is a management domain platform conforming to the ETSI reference model framework of ETSI, which mainly includes VIM, VNFM and NFVO.
  • the hardware BIOS is configured to download a specific hardware abstraction layer software of a specified version number and a version of vRRCs, vBPs, and vRFs from a specified software repository to a local cache; receive an abstract layer software version of the dedicated hardware resource module, and vRRCs, vBPs, and vRFs. Version load instruction.
  • the dedicated hardware abstraction layer is arranged to provide a normalized standardized software runtime environment to the virtual network functions vRRCs, vBPs, vRFs.
  • the dedicated hardware manager includes a dedicated hardware resource pool management module and a dedicated hardware resource allocation module.
  • the dedicated hardware resource pool management module is configured to: generate, manage, and maintain detailed information of instantiation and de-instantiation status of the vSector, vBPPool, vGPPool, and vConnector resources and usage by the cell.
  • the dedicated hardware resource allocation module is configured to reasonably allocate vCoverage, vBPC, vHPC, and vPath for the cells in the vRRCs, vBPs, and vRFs instances during instantiation, cell resource change, or dedicated hardware failure.
  • the network function virtualization implementation process of the dedicated hardware based radio access network may include the following steps 1-12.
  • step 1 the user plans the connection relationship of the dedicated hardware, the Sector component (including the used attributes of the antenna entity and the antenna unit, the merge and split attributes of the RRU, and the RF port connection relationship between the antenna port and the RRU), and the BPPool and GPPool.
  • the dedicated hardware range (which can be assigned to a single board, multiple boards, or the entire chassis), the physical connection relationship between the RRU and the dedicated hardware, and the planning data is imported into the dedicated hardware resource pool management module through the network management module.
  • the abstract model description file (including hardware model, standardized usage interface metadata, hardware capability description information, and version number information) of the dedicated hardware is imported into the dedicated hardware resource pool management module by the network management module.
  • the model description file (including the virtual network function service name, the standardized access interface definition metadata, the service capability description information, and the version number information) of the virtual network function service is imported into the dedicated hardware resource allocation module by the network management module.
  • step 4 the dedicated hardware BIOS is powered on; the hardware BIOS discovers the specification model and physical location information and reports it to the dedicated hardware resource pool management module; the dedicated hardware resource pool management module uses physical location information and planning data to redraw the complete dedicated hardware. Topology.
  • the dedicated hardware resource pool management module performs operations abstracted into vSector, vBPPool, vGPPool, and vConnector according to the planned Sector, BPPool, GPPool, and complete dedicated hardware topology, waiting for the virtual network service instantiation process.
  • vSector vBPPool
  • vGPPool vGPPool
  • vConnector vConnector
  • vSector tag For vSector, according to the antenna entity of the sector and the used attributes of the antenna unit and the RF connection of each RRU according to the dedicated hardware topology, combined with the abstract model description file of the dedicated hardware, the following items are generated: vSector tag, frequency band, uplink channel and The downlink channel uses the bitmap and the coverage location details (including the SectorID and the Sector planning location string); the uplink channel and the downlink channel of each RRU use the bitmap, the carrier number pool, and the carrier aggregation type; each channel of each RRU Frequency range, power headroom. If all RRUs in the Sector support multiple bands, then one vSector is generated for each band.
  • the BPPool BPU For vBPPool, the BPPool BPU according to the dedicated hardware topology, combined with the abstract model description file of the dedicated hardware, generates the label, type, and system list of the minimum deployment unit of vBPPool (usually as small as the chip of the computing chip, such as CPU, DSP or FPGA). .
  • the minimum deployment unit may be a virtual baseband processing unit vBPUnit.
  • the GPPool GPU For vGPPool, the GPPool GPU according to the dedicated hardware topology, combined with the abstract model description file of the dedicated hardware, generates the label, type, and system list of the minimum deployment unit of vGPPool (usually as small as the computing chip, including RAM).
  • the minimum deployment unit may be a virtual central processing unit vCPU.
  • vConnector For vConnector, according to the Sector, BPU, GPU, and chassis type of the dedicated hardware topology, combined with the abstract model description file of the dedicated hardware, the vConnector label, the out-of-frame topology, the inter-board topology, and the intra-chip inter-layer topology details are generated.
  • the detailed information includes an atomic computing node (such as RRU, vBPUnit, vCPU, etc.), a number of a connection node (such as a switch chip, an optical port, etc.), a transmission type (including a serial port, an optical port, an Ethernet, etc.), Transmission bandwidth.
  • the user initiates a virtual network service instantiation process using the MANO Universal Platform.
  • the instantiation process carries a model description file version number of the virtual network function service and an abstract model description file version number of the dedicated hardware.
  • the VNFM requests the VIM to apply for the resource used by the service, and the VIM then delegates the dedicated hardware resource allocation module to initiate the virtual network function service resource application, and the dedicated hardware resource allocation module returns the resource allocation result, wherein the resource
  • the allocation result includes the vGPPool resource tag used by the vRRCs instance, the vBPPool resource tag used by the vBPs instance, and the vSector resource tag used by the vRFs instance.
  • the VIM periodically queries the dedicated hardware resource allocation module to obtain status information of the vGPPool, vBPPool, and vSector.
  • the dedicated hardware resource allocation module notifies the hardware BIOS to download the specified version number of the dedicated hardware abstraction layer software and the versions of vRRCs, vBPs, vRFs from the specified depot to the local cache.
  • the network management module initiates a cell resource change procedure application to the dedicated hardware resource allocation module, or releases the dedicated hardware resource and updates to the dedicated hardware resource pool management module.
  • the radio parameters of the cell may be carried in the application for allocating the specific vCoverage, vBPC, vHPC, and vPath used by the cell, or may not carry the radio parameters of the cell, but use the cell in the subsequent process.
  • the resource change process to apply for or release specific vCoverage, vBPC, vHPC, and vPath.
  • the VNFM periodically queries the dedicated hardware resource allocation module for status information of vRRCs, vBPs, and vRFs.
  • the dedicated hardware resource allocation module can perform the operations described in detail below.
  • the virtual network service instantiation process or the cell resource change process carries a cell list, where the cell list includes the number, format, frequency band, uplink and downlink frequency, bandwidth, power, number of connected users, bearer number, and logical port of each cell. Number and cell coverage location (SectorID or Sector planning location string).
  • Error a The coverage location was not found and the next cell is continued.
  • Error b RRU channel allocation failed, proceed to the next cell.
  • vCoverage find the out-of-frame topology of the atomic computing node in the vConnector as the RRU in the current vSector to find a list of available BPUs. If a list of available BPUs is found, then operations 7) and 8) are performed. If the available BPU list is empty or the number of BPUs is smaller than the number of BPUs required by the cell, then operation 6) is performed.
  • the vCoverage is used to find the out-of-frame topology and the inter-board topology of the RRU in the current vSector in order to find the available BPU list, if the available BPU is found. For the BPU list, perform operations 7) and 9). If the available BPU list is empty or the available BPU list is not empty, but the number of BPUs is smaller than the number of BPUs required by the cell or the available BPU list is not empty and the number of BPUs is greater than or equal to the number of BPUs required by the cell but remaining If the number of vBPUnits is smaller than the number of vBPUnits required by the cell, the cell number is recorded and error c is recorded. An example of the error c is as follows.
  • the inter-board topology or inter-frame topology of the BPU and the GPU combined with the currently selected BPU, find a list of available GPUs.
  • the available GPU list is empty or the available GPU list is not empty but less than the number of GPUs required by the cell or the available GPU list is not empty and the number of GPUs is greater than or equal to the number of GPUs required by the cell but the number of remaining vCPUs
  • the cell number is recorded and an error e is recorded.
  • An example of the error e is as follows.
  • Error e GP resource allocation failed, proceed to the next cell.
  • the dedicated hardware resource allocation module notifies the hardware BIOS to load the abstraction layer software version and the versions of vRRCs, vBPs, vRFs by the dedicated hardware used by vCoverage, vBPC, and vHPC.
  • the dedicated hardware resource allocation module notifies the detailed parameters of the dedicated hardware abstraction layer software vCoverage, vBPC, vHPC, and vPath, wherein the main parameters of the vCoverage include the cell number, bandwidth, channel power, band frequency, carrier number, and the like.
  • the main parameters of vBPC include cell number, bandwidth, logical port number, power and number of connected users.
  • the main parameters of vHPC include cell number, bandwidth, and number of connected users, and the main parameters of vPath include vCoverage, vBPC and vHPC. High-speed communication path, bandwidth, delay, priority, and reliability.
  • the network management module sends the wireless service parameters to vRRCs, vBPs, and vRFs to initiate a cell initialization process.
  • the dedicated hardware resource allocation module may be notified to release the specific vCoverage, vBPC, vHPC, and vPath used by a certain cell, and the situation is updated to dedicated hardware. Resource pool management module.
  • the dedicated hardware resource pool management module analyzes the serving cell affected by the failure, and notifies the dedicated hardware resource allocation module as the affected The serving cell reassigns vCoverage, vBPC, vHPC, and vPath.
  • the present disclosure also provides a computer readable medium storing computer readable instructions that, when executed by a processor, cause the processor to perform wireless in accordance with the present disclosure A method of virtualizing network functions.
  • the MANO domain of the NFV provides static or dynamic mapping of the VNF instance and the dedicated hardware resource pool, and the management and allocation of the dedicated resources used by the service at the site. Internally completed. Thus, various dedicated hardware of the radio access network are managed and allocated by the MANO domain, so that the complexity of the MANO domain can be solved.
  • the benefits of using dedicated hardware can be obtained in the case of NFV.
  • the benefits include, for example, the operator can flexibly adjust the virtualized operating environment according to the requirements of the software, greatly improve the use efficiency of the hardware, and change the business model of the traditional system equipment vendor software and hardware binding sales. This allows a large number of software developers to participate, greatly reducing software investment and risk, while using a standardized MANO domain management platform, reducing system integration costs and improving the level of operation and maintenance automation; for equipment suppliers, can reduce development Cost, reducing the impact of hardware updates on software systems and reducing time to market.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开公开了一种无线网络功能虚拟化方法及装置，所述方法包括：确定无线接入设备对应的虚拟专用硬件资源；对无线接入网的多个虚拟网络服务进行实例化处理，以得到所述虚拟网络服务对应的虚拟专用硬件资源信息以及用于小区覆盖处理的信息；以及根据所述虚拟专用硬件资源信息以及用于小区覆盖处理的信息，针对各虚拟网络服务，使用各个虚拟网络服务模块来执行操作。

Description

无线网络功能虚拟化方法及装置 技术领域
概括地说，本公开涉及无线通讯接入网***侧设备，并且具体地说，涉及一种无线网络功能虚拟化方法及装置。
背景技术
根据欧洲电信标准协会(European Telecommunications Sdandards Institute，ETSI)的网络功能虚拟化(Network Function Virtualization，NFV)参考模型，使用包括计算硬件(如中央处理器(Central Processing Unit，CPU))、存储硬件(磁盘、磁阵)和网络硬件(以太网)等常规的通用硬件资源(通常指基于X86架构的通用处理器)，采用虚拟化技术(如Intel VT)来提供供客机操作***(Guest Operating System，Guest OS)及部署的软件***使用的虚拟计算资源、虚拟存储资源和虚拟网络资源。
在一些情况下，可以将专用硬件当作一种虚拟化或非虚拟化的加速资源纳入到NFV参考模型中，由NFV参考模型中使用管理与编排(Management and Orchestration，MANO)域的虚拟化基础设施管理(Virtualization infrastructure management，VIM)进行管理和分配。在这种情况下，无线接入网的各种专用设备的特性对MANO域完全暴露，可能导致MANO域的复杂度大幅提升。
发明内容
本公开实施例提供了一种无线网络功能虚拟化方法，包括：确定无线接入设备对应的虚拟专用硬件资源；对无线接入网的多个虚拟网络服务进行实例化处理，以得到所述虚拟网络服务对应的虚拟专用硬件资源信息以及用于小区覆盖处理的信息；以及根据所述虚拟专用硬件资源信息以及用于小区覆盖处理的信息，针对各虚拟网络服务，使用各个虚拟网络服务模块来执行操作。
本公开实施例提供了一种无线网络功能虚拟化装置，包括：确 定模块，其设置为确定无线接入设备对应的虚拟专用硬件资源；实例化处理模块，其设置为对无线接入网的多个虚拟网络服务进行实例化处理，以得到所述虚拟网络服务对应的虚拟专用硬件资源信息以及用于小区覆盖处理的信息；以及执行模块，其设置为根据所述虚拟专用硬件资源信息以及用于小区覆盖处理的信息，针对各虚拟网络服务，使用各个虚拟网络服务模块来执行操作。
本公开实施例还提供了一种计算机可读介质，其存储有计算机可读指令，当所述指令被处理器执行时，使得所述处理器执行根据本公开的无线网络功能虚拟化方法。
附图说明
图1是本公开实施例提供的一种无线网络功能虚拟化方法的流程图；
图2是本公开实施例提供的一种无线网络功能虚拟化装置的示意图；
图3是本公开实施例提供的专用硬件的无线接入网的网络功能虚拟化抽象示意图；
图4是本公开实施例提供的专用硬件的无线接入网的虚拟化网络功能接入MANO示意图；以及
图5是本公开实施例提供的专用硬件的无线接入网的网络功能虚拟化装置示意图。
具体实施方式
无线通讯接入网通常包括：无线资源控制(Radio Resource Control，RRC)单元、第二层L2(包括分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)/无线链路层控制协议(Radio Link Control，RLC)/多路访问控制(Multiple Access Control，MAC))、物理层(Physical Layer，PHY)、无线射频(Radio Frequency，RF)功能单元。
传统的***设备商采用专用的硬件来提供以上接入网的网络功 能。在一些情况下，接入网的大量网络功能有严格的时延及传输流量要求，通过采用专用硬件，可以降低处理时延及提高吞吐量。此外，专用集成电路(Application Specific Integrated Circuits，ASIC)硬件可以进行专业的优化设计以提高能源效率，从而降低硬件运行功耗。而且，针对明确的网络功能，选用适合的专用硬件可以大大降低硬件成本。可见，使用专用硬件来实现网络功能可以具有诸多益处。
在一些情况下，可以将专用硬件当作一种虚拟化或非虚拟化的加速资源纳入到NFV参考模型中。在NFV参考模型中，Guest OS及部署的软件***对使用的硬件是物理的还是虚拟化的没有感知，并且通常的网络功能单元(例如，IP多媒体子***(IP Multimedia Subsystem，IMS)、移动管理实体(Mobile Management Entity，MME)等)可以使用这个Guest OS环境来实施，以达到节约硬件投资和提高硬件使用效率的目的。
然而，在这种情况下，无线接入网的各种专用硬件由MANO域进行管理和分配，使得MANO域的复杂度较高。
对此，以下结合附图来详细描述本公开的示例性实施例。应当理解，以下所描述的示例性实施例仅用于说明和解释本公开，并不用于限定本公开。
图1是本公开实施例提供的一种无线网络功能虚拟化方法的流程图。
如图1所示，所述无线网络功能虚拟化方法包括步骤S101-S103。
在步骤S101处，确定无线接入设备对应的虚拟专用硬件资源。
在步骤S102处，对无线接入网的多个虚拟网络服务进行实例化处理，以得到所述虚拟网络服务对应的虚拟专用硬件资源信息以及用于小区覆盖处理的信息。
在步骤S103处，根据所述虚拟专用硬件资源信息以及用于小区覆盖处理的信息，针对各虚拟网络服务，使用各个虚拟网络服务模块来执行操作。
在一个实施例中，所述无线接入设备是用于将所述无线接入网的网络功能虚拟化的设备，并且其中，所述确定无线接入设备对应的 虚拟专用硬件资源的步骤S101包括：确定所述无线接入设备的专用硬件资源对应的用于所述虚拟化的虚拟专用硬件资源。
在一个实施例中，所述确定无线接入设备对应的虚拟专用硬件资源的步骤S101还包括：根据无线接入设备中专用硬件拓扑规划的扇区天线实体及天线单元的被使用属性和每个射频拉远单元(Radio Remote Unit，RRU)的射频连接，并结合专用硬件的抽象模型描述文件，抽象出用于完成RF网络功能的虚拟扇区资源；根据无线接入设备中专用硬件拓扑规划的基带处理池的基带处理单元(Baseband Processing Unit，BPU)，并结合专用硬件的抽象模型描述文件，抽象出用于完成PHY网络功能和L2的部分网络功能的虚拟基带处理池资源；根据无线接入设备中专用硬件拓扑规划的通用处理池的通用处理单元(General Processing Unit，GPU)，并结合专用硬件的抽象模型描述文件，抽象出用于完成RRC网络功能和L2的部分网络功能的虚拟通用处理池资源；以及根据无线接入设备中专用硬件拓扑规划的扇区、BPU、GPU以及机框类型，并结合专用硬件的抽象模型描述文件，抽象出用于完成高速通讯功能的虚拟连接器资源。
在一个实施例中，所述对无线接入网的多个虚拟网络服务进行实例化处理，以得到所述虚拟网络服务对应的虚拟专用硬件资源信息以及用于小区覆盖处理的信息的步骤S102包括：利用无线接入设备的专用硬件的抽象模型描述文件和虚拟网络功能服务的模型描述文件，对无线接入网的多个虚拟网络服务进行实例化处理，以得到所述虚拟网络服务对应的虚拟专用硬件资源信息以及用于小区覆盖处理的信息。所述专用硬件的抽象模型描述文件可以包括：专用硬件型号、标准化的使用接口元数据、专用硬件能力描述信息及版本号信息，并且所述虚拟网络功能服务的模型描述文件可以包括：虚拟网络功能服务名、标准化的接入接口定义元数据、服务能力描述信息及版本号信息。
在一个实施例中，所述对无线接入网的多个虚拟网络服务进行实例化处理，以得到所述虚拟网络服务对应的虚拟专用硬件资源信息以及用于小区覆盖处理的信息的步骤包括：申请所述虚拟网络服务要 使用的资源，并返回资源分配结果，其中，所述资源分配结果包括所述虚拟网络服务对应的虚拟专用硬件资源信息以及用于小区覆盖处理的信息。
在一个实施例中，所述根据所述虚拟专用硬件资源信息以及用于小区覆盖处理的信息，针对各虚拟网络服务，使用各个虚拟网络服务模块来执行操作的步骤S103包括；使用各个虚拟网络服务模块来发起小区资源变更流程，或使用各个虚拟网络服务模块来发起小区资源释放流程，或使用各个虚拟网络服务模块来发起故障资源自愈流程。
图2是本公开实施例提供的一种无线网络功能虚拟化装置的示意图。
如图2所示，所述无线网络功能虚拟化装置包括确定模块201、实例化处理模块202和执行模块203。确定模块201设置为确定无线接入设备对应的虚拟专用硬件资源。实例化处理模块202设置为对无线接入网的多个虚拟网络服务进行实例化处理，以得到所述虚拟网络服务对应的虚拟专用硬件资源信息以及用于小区覆盖处理的信息。执行模块203设置为根据所述虚拟专用硬件资源信息以及用于小区覆盖处理的信息，针对各虚拟网络服务，使用各个虚拟网络服务模块来执行操作。
在一个实施例中，所述无线接入设备是用于将所述无线接入网的网络功能虚拟化的设备，并且其中，所述确定模块201还设置为确定所述无线接入设备的专用硬件资源对应的用于所述虚拟化的虚拟专用硬件资源。
在一个实施例中，所述实例化处理模块202还设置为利用无线接入设备的专用硬件的抽象模型描述文件和虚拟网络功能服务的模型描述文件，对无线接入网的多个虚拟网络服务进行实例化处理，以得到所述虚拟网络服务对应的虚拟专用硬件资源信息以及用于小区覆盖处理的信息。所述专用硬件的抽象模型描述文件可以包括：专用硬件型号、标准化的使用接口元数据、专用硬件能力描述信息及版本号信息，并且，所述虚拟网络功能服务的模型描述文件可以包括：虚拟网络功能服务名、标准化的接入接口定义元数据、服务能力描述信 息及版本号信息。
在一个实施例中，所述实例化处理模块202还设置为申请所述虚拟网络服务要使用的资源，并返回资源分配结果，其中，所述资源分配结果包括所述虚拟网络服务对应的虚拟专用硬件资源信息以及用于小区覆盖处理的信息。
在一个实施例中，所述执行模块203还设置为使用各个虚拟网络服务模块来发起小区资源变更流程，或使用各个虚拟网络服务模块来发起小区资源释放流程，或使用各个虚拟网络服务模块来发起故障资源自愈流程。
图3是本公开实施例提供的专用硬件的无线接入网的网络功能虚拟化抽象示意图。
如图3所示，本公开实施例无线接入网设备的专用硬件包括天线(Antenna)、RRU、BPU和GPU及机框(包括高速通讯总线的背板)，其中，RRU主要完成RF的功能，BPU主要完成PHY和/或L2部分功能，GPU完成RRC和/或L2部分网络功能和操作维护的功能,而机框主要完成高速通讯功能。无线接入网设备只具有少量的用于操作维护的存储功能，而不具有业务存储(磁盘，随机存取存储器(Random-Access Memory，RAM)除外)功能。
在一个实施例中，可以将若干个天线和若干个RRU抽象为虚拟扇区vSector资源，提供包括功率、频段、通道数等与覆盖有关的属性集合，以完成RF网络功能。具有相同vSector资源标签的一组可用覆盖虚拟连接器vCoverage可以由小区/载波直接使用。
在一个实施例中，可以将若干个BPU抽象为虚拟基带处理池vBPPool资源，提供包括连接用户数、载波数、通道数等与基带协议有关的属性集合，以完成PHY网络功能和L2的部分网络功能。具有相同vBPPool资源标签的一组基带计算资源vBCP可以由小区/载波直接使用。
在一个实施例中，可以将若干个GPU抽象为虚拟通用处理池vGPPool资源，提供包括连接用户数、承载数、小区/载波数等与高层协议有关的属性集合，以完成RRC网络功能和L2的部分网络功能。 具有相同vGPPool资源标签的一组高层计算资源vHCP可以由小区/载波直接使用。
在一个实施例中，可以将机框背板的高速通讯接口抽象为vConnector资源，提供包括连接拓扑、带宽、时延、优先级、可靠性等与高速通讯有关的属性集合，以完成高速通讯功能。具有相同vConnector资源标签的一组通讯连接路径资源vPath可以由小区/载波直接使用。
所述vSector、vBPPool、vGPPool、vConnector分别由其专用硬件的抽象层来提供标准的使用接口及能力描述信息。在抽象层，专用硬件的差异都要归一化为标准的使用接口及能力描述信息。能力描述信息包括资源的属性、资源架构、部署约束、亲和关系及资源能力版本号。
关于对专用硬件抽象层的管理，可以将经扩展的VIM接入到符合ETSI规范的MANO通用平台中，以对上层虚拟化网络功能管理器(VNF Manager，VNFM)提供标准管理接口。
无线接入网虚拟的网络功能服务包括：虚拟无线资源控制(virtual Radio Resource Control,vRRCs)、虚拟基带处理(virtual baseband processing，vBPs)、虚拟基带处理(virtual radio frquency，vRFs)。网络功能服务由专用硬件资源分配模块提供标准化的接入接口定义和服务能力描述信息。服务能力描述信息包括对资源的类型/数量/架构要求、亲和关系、部署约束及服务能力版本号。
图4是本公开实施例提供的专用硬件的无线接入网的虚拟化网络功能接入MANO示意图。
如图4所示，对于虚拟的网络功能服务的实例化管理及服务之间需要的依赖关系，可以采用VNFM接口接入到符合ETSI规划的MANO通用平台中，而对于专用硬件和网络功能服务实例的关系，可以采用VIM接口接入到符合ETSI规划的MANO通用平台中，以对上层网络功能虚拟化编排器(NFV Orchestrator，NFVO)提供标准的管理接口。
图5是本公开实施例提供的专用硬件的无线接入网的网络功能虚拟化装置示意图。
如图5所示，所述网络功能虚拟化装置可以包括网管模块、MANO通用平台、硬件BIOS、专用硬件抽象层和专用硬件管理器。
所述网管模块设置为向MANO通用平台发起实例化过程和去实例化过程；向vRRCs、vBPs、vRFs下发小区无线参数；导入专用硬件规划数据；导入专用硬件的抽象模型描述文件、虚拟网络功能服务的模型描述文件。
所述MANO通用平台是符合ETSI的NFV参考模型框架的管理域平台，其主要包括VIM、VNFM和NFVO。
所述硬件BIOS设置为从指定的软件仓库下载指定版本号的专用硬件抽象层软件及vRRCs、vBPs、vRFs的版本到本地缓存；接收专用硬件资源模块的抽象层软件版本及vRRCs、vBPs、vRFs的版本加载指令。
所述专用硬件抽象层设置为向虚拟网络功能vRRCs、vBPs、vRFs提供一个归一化标准化的软件运行环境。
所述专用硬件管理器包括专用硬件资源池管理模块和专用硬件资源分配模块。
所述专用硬件资源池管理模块设置为：生成、管理和维护vSector、vBPPool、vGPPool和vConnector资源的实例化和去实例化状态及被小区使用情况的详细信息。
所述专用硬件资源分配模块设置为在实例化时、小区资源变更时或专用硬件故障时，为vRRCs、vBPs、vRFs实例中的小区合理分配vCoverage、vBPC、vHPC及vPath。
在一个实施例中，基于专用硬件的无线接入网的网络功能虚拟化实施过程可以包括以下步骤1-12。
在步骤1处，用户规划专用硬件的连接关系、Sector组成(包括天线实体及天线单元的被使用属性、RRU的合并与***属性和天线端口和RRU的射频端口连接关系)、BPPool和GPPool包含的专用硬件范围(可以指定到一个单板、多个单板或整个机框)、RRU和专用硬件的物理连接关系，并将规划数据通过网管模块导入到专用硬件资源池管理模块。
在步骤2处，通过网管模块将专用硬件的抽象模型描述文件(包括硬件型号、标准化的使用接口元数据、硬件能力描述信息及版本号信息)导入到专用硬件资源池管理模块。
在步骤3处，通过网管模块将虚拟网络功能服务的模型描述文件(包括虚拟网络功能服务名、标准化的接入接口定义元数据、服务能力描述信息及版本号信息)导入到专用硬件资源分配模块。
在步骤4处，专用硬件BIOS上电；硬件BIOS发现规格型号及物理位置信息并上报到专用硬件资源池管理模块；专用硬件资源池管理模块使用物理位置信息及规划数据来重绘完整的专用硬件拓扑。专用硬件资源池管理模块根据规划的Sector、BPPool、GPPool和完整的专用硬件拓扑，执行抽象成vSector、vBPPool、vGPPool和vConnector的操作，等待虚拟网络服务实例化过程。
所述抽象成vSector、vBPPool、vGPPool和vConnector的操作。可以如下所详细描述地来实施
对于vSector，根据专用硬件拓扑的Sector的天线实体及天线单元的被使用属性和每个RRU的射频连接，结合专用硬件的抽象模型描述文件，生成以下各项：vSector的标签、频段、上行通道和下行通道使用位图、覆盖位置详细信息(含SectorID和Sector规划位置字符串)；每个RRU的上行通道和下行通道使用位图、载波编号池、载波聚合类型；每个RRU的每个通道的频段范围、功率余量。如果Sector中的所有RRU支持多频段，则每个频段生成一个vSector。
对于vBPPool，根据专用硬件拓扑的BPPool的BPU，结合专用硬件的抽象模型描述文件，生成vBPPool的最小部署单元(通常小至计算芯片，如CPU、DSP或FPGA的片)的标签、类型、制式列表。所述最小部署单元可以是虚拟基带处理单元vBPUnit。
对于vGPPool，根据专用硬件拓扑的GPPool的GPU，结合专用硬件的抽象模型描述文件，生成vGPPool的最小部署单元(通常小至计算芯片，包含RAM)的标签、类型、制式列表。所述最小部署单元可以是虚拟中央处理单元vCPU。
对于vConnector，根据专用硬件拓扑的Sector、BPU、GPU及机 框类型，结合专用硬件的抽象模型描述文件，生成vConnector的标签、框外拓扑、框内板间拓扑、板内片间拓扑详细信息，其中，所述详细信息包括原子计算节点(如RRU、vBPUnit、vCPU等)、连接节点(如交换芯片、光端口等)的编号、传输类型(包括串行口、光口、以太网等)、传输带宽。
在步骤5处，用户使用MANO通用平台发起虚拟网络服务实例化过程。所述实例化过程携带虚拟网络功能服务的模型描述文件版本号、专用硬件的抽象模型描述文件版本号。在所述实例化过程期间，VNFM向VIM申请服务使用的资源，VIM再委托专用硬件资源分配模块发起虚拟网络功能服务资源申请，而专用硬件资源分配模块则返回资源分配结果，其中，所述资源分配结果包括vRRCs实例使用的vGPPool资源标签、vBPs实例使用的vBPPool资源标签、vRFs实例使用的vSector资源标签。VIM定期向专用硬件资源分配模块查询获取vGPPool、vBPPool和vSector的状态信息。
在步骤6处，专用硬件资源分配模块通知硬件BIOS从指定的软件仓库下载指定版本号的专用硬件抽象层软件及vRRCs、vBPs、vRFs的版本到本地缓存中。
在步骤7处，由网管模块向专用硬件资源分配模块发起小区资源变更流程申请，或释放专用硬件资源并更新到专用硬件资源池管理模块。虚拟网络服务实例化过程中，可以携带小区的无线参数以用于申请分配所述小区使用的具体的vCoverage、vBPC、vHPC及vPath，也可以不携带小区的无线参数，而在后续过程中使用小区资源变更流程来申请或释放具体的vCoverage、vBPC、vHPC及vPath。VNFM定期向专用硬件资源分配模块查询vRRCs、vBPs和vRFs的状态信息。
在一个实施例中，专用硬件资源分配模块可以进行如下详细描述的操作。
1)虚拟网络服务实例化过程或小区资源变更流程携带小区列表，所述小区列表包括每个小区的编号、制式、频段、上下行频点、带宽、功率、连接用户数、承载数、逻辑端口数及小区覆盖位置(SectorID或Sector规划位置字符串)。
2)循环读取根据小区列表，根据每个覆盖位置、制式、频段查找唯一的vSector。如果成功查找到唯一的vSector，则执行操作3)；如果没有查找到唯一的vSector，则记录小区编号并记录错误a。所述错误a的示例如下所示。
错误a：未找到覆盖位置，继续下一个小区。
3)从vSector中分配每个RRU的通道的上下行频点、带宽、功率及载波号。如果vSector中的所有RRU的通道均分配成功，则这可以被记录为vCoverage并执行操作4)；如果没有成功，则记录小区编号并记录错误b。所述错误b的示例如下所示。
错误b：RRU通道分配失败，继续下一个小区。
4)根据每个小区的制式、带宽、vSector通道数、连接用户数、承载数来计算需要的CPU数量和vCPU数量及亲和要求、BPU个数和vBPUnit个数及亲和要求。
5)根据vCoverage来查找vConnector中原子计算节点为当前vSector中的RRU的框外拓扑，以找到可用的BPU列表。如果找到了可用的BPU列表，则执行操作7)和操作8)。如果可用的BPU列表为空或BPU的个数小于小区需要的BPU个数，则执行操作6)。
6)如果存在框内板间交换连接，则根据vCoverage来查找vConnector中原子计算节点为当前vSector中的RRU的框外拓扑和框内板间拓扑，以找到可用的BPU列表，如果找到了可用的BPU列表，则执行操作7)和操作9)。如果可用的BPU列表为空或可用的BPU列表不为空但BPU的个数小于小区需要的BPU个数或可用的BPU列表不为空且BPU的个数大于等于小区需要的BPU个数但剩余的vBPUnit个数小于小区需要的vBPUnit个数，则记录小区编号并记录错误c。所述错误c的示例如下所示。
错误c：BP资源分配失败，继续下一个小区。
7)根据策略来选择BPU。当策略为负荷均衡时，从可用BPU列表中负荷最轻的若干个BPU，并且当策略为节约资源时，选择负荷最重且有空余资源的若干个BPU。
8)根据vCoverage的业务带宽和每个RRU通道数来计算需要的 路径带宽，从框外拓扑和板内片间拓扑为每个RRU找到若干个带宽足够的路径vPath和可用的vBPUnit以组成vBPUnit组vBPUnitGroup。如果带宽不足，则将当前的BPU从可用的BPU列表中排除，并重新执行操作7)，直到可用的BPU列表为空或小于小区需要的BPU个数。在可用的BPU列表为空或小于小区需要的BPU个数时，记录小区编号并记录错误d。所述错误d的示例如下所示。
错误d：无BPU连接路径可用，继续下一个小区。
9)根据vCoverage的业务带宽和每个RRU通道数来计算需要的路径带宽，从框外拓扑、框内板间拓扑和板内片间拓扑为每个RRU找到一个带宽足够的路径vPath和可用的vBPUnit以组成vBPUnitGroup。如果带宽不足，则将当前的BPU从可用的BPU列表中排除，并重新执行操作7)，直到可用的BPU列表为空或小于小区需要的BPU个数。在可用的BPU列表为空或小于小区需要的BPU个数时记录小区编号并记录错误d。所述错误d的示例如下所示。
错误d：无BPU连接路径可用，继续下一个小区。
10)从vBPUnitGroup中分配一份vBPC给当前Cell，并标记每个vBPUnit的使用情况。
11)根据BPU和GPU的框内板间拓扑或框间拓扑结构，结合当前已经选定的BPU，找到可用的GPU列表。当可用的GPU列表为空或可用的GPU列表不为空但小于小区需要的GPU个数或可用的GPU列表不为空且GPU个数大于等于小区需要的GPU个数但剩余的vCPU的个数小于小区需要的vCPU的个数时，记录小区编号并记录错误e。所述错误e的示例如下所示。
错误e：GP资源分配失败，继续下一个小区。
12)根据策略来选择GPU。当策略为负荷均衡时，从可用GPU列表中选择负荷最轻的若干个GPU，并且当策略为时延优先时，从可用GPU列表中选择链路时延最小的若干个GPU。根据小区的vCPU需求来分配vCPU并标记为vHPC。
13)根据小区的业务带宽为BPU和GPU分配连接并记录到小区的vPath中。当BPU和GPU的连接带宽小于业务带宽时，将当前GPU 从GPU列表中删除，重新执行操作12)，直到可用的GPU列表为空或GPU的个数小于小区需要的GPU个数。在GPU列表为空或GPU的个数小于小区需要的GPU个数时，记录小区编号并记录错误f。所述错误f的示例如下所示。
错误f：无GPU连接路径可用，继续下一个小区。
在步骤8处，专用硬件资源分配模块通知硬件BIOS被vCoverage、vBPC和vHPC使用的专用硬件加载抽象层软件版本及vRRCs、vBPs、vRFs的版本。
在步骤9处，专用硬件资源分配模块通知专用硬件抽象层软件vCoverage、vBPC、vHPC和vPath的详细参数，其中，vCoverage的主要参数包括小区编号、带宽、通道功率、频段频点、载波号等，vBPC的主要参数包括小区编号、带宽、逻辑端口号、功率及连接用户数等，vHPC的主要参数包括小区编号、带宽、及连接用户数等,并且vPath的主要参数包括了vCoverage、vBPC和vHPC之间的高速通讯路径、带宽、时延、优先级和可靠性等。
在步骤10处，网管模块下发无线业务参数到vRRCs、vBPs、vRFs，以发起小区初始化流程。
在步骤11处，小区资源释放流程。在其所述流程期间，在由网管发起的小区资源变更流程中，可以通知专用硬件资源分配模块释放某个小区使用的具体的vCoverage、vBPC、vHPC及vPath，并将这一情况更新到专用硬件资源池管理模块。
在步骤12处，故障资源自愈流程。在所述流程期间，当由硬件BIOS检测到某一专用硬件发生故障因而不可用时，专用硬件资源池管理模块分析所述故障影响的服务小区，并通知专用硬件资源分配模块为所述被影响的服务小区重新分配vCoverage、vBPC、vHPC及vPath。
虽然未在附图中示出，但是本公开还提供一种计算机可读介质，其存储有计算机可读指令，当所述指令被处理器执行时，使得所述处理器执行根据本公开的无线网络功能虚拟化的方法。
通过以上描述的各实施例和技术方案，在NFV参考模型框架下，对NFV的MANO域提供了VNF实例和专用硬件资源池的静态或动态映 射，对业务使用的专用资源的管理和分配在站点内部完成。从而，无线接入网的各种专用硬件由MANO域进行管理和分配，使得MANO域的复杂度较高这一问题可以得以解决。
由此，通过以上描述的各实施例和技术方案，能够在NFV的情况下获得使用专用硬件的益处。所述益处包括，例如，对运营商来说，能够根据软件的需求灵活调整虚拟化的运行环境，极大的提高硬件的使用效率，改变传统的***设备商软硬件绑定销售的商业模式，使得大量的软件开发商可以参与进来，大大降低了软件投资及风险，同时使用标准化的MANO域管理平台，降低了***集成成本，提高运维自动化水平；而对设备供应商来说，能够降低开发成本，减少硬件更新对软件***的影响，并且缩短产品上市时间。
尽管上文对本公开进行了详细说明，但是本公开不限于此。在不脱离本公开的精神和范围的情况下，本领域技术人员可以对本公开进行各种修改和替换，并且，所作的修改和替换应认为落入本公开的保护范围内。

Claims (17)

  1. 一种无线网络功能虚拟化方法，包括：
    确定无线接入设备对应的虚拟专用硬件资源；
    对无线接入网的多个虚拟网络服务进行实例化处理，以得到所述虚拟网络服务对应的虚拟专用硬件资源信息以及用于小区覆盖处理的信息；以及
    根据所述虚拟专用硬件资源信息以及用于小区覆盖处理的信息，针对各虚拟网络服务，使用各个虚拟网络服务模块来执行操作。
  2. 根据权利要求1所述的方法，其中，所述确定无线接入设备对应的虚拟专用硬件资源的步骤包括：
    根据无线接入设备中专用硬件拓扑规划的扇区天线实体及天线单元的被使用属性和每个射频拉远单元RRU的射频连接，并结合专用硬件的抽象模型描述文件，抽象出用于完成无线射频RF网络功能的虚拟扇区资源。
  3. 根据权利要求1所述的方法，其中，所述确定无线接入设备对应的虚拟专用硬件资源的步骤包括：
    根据无线接入设备中专用硬件拓扑规划的基带处理池的基带处理单元BPU，并结合专用硬件的抽象模型描述文件，抽象出用于完成物理层PHY网络功能和第二层L2的部分网络功能的虚拟基带处理池资源。
  4. 根据权利要求1所述的方法，其中，所述确定无线接入设备对应的虚拟专用硬件资源的步骤包括：
    根据无线接入设备中专用硬件拓扑规划的通用处理池的通用处理单元GPU，并结合专用硬件的抽象模型描述文件，抽象出用于完成无线资源控制RRC网络功能和第二层L2的部分网络功能的虚拟通用处理池资源。
  5. 根据权利要求1所述的方法，其中，所述确定无线接入设备对应的虚拟专用硬件资源的步骤包括：
    根据无线接入设备中专用硬件拓扑规划的扇区、基带处理单元BPU、通用处理单元GPU以及机框类型，并结合专用硬件的抽象模型描述文件，抽象出用于完成高速通讯功能的虚拟连接器资源。
  6. 根据权利要求1所述的方法，其中，所述无线接入设备是用于将所述无线接入网的网络功能虚拟化的设备，并且其中，所述确定无线接入设备对应的虚拟专用硬件资源的步骤包括：
    确定所述无线接入设备的专用硬件资源对应的用于所述虚拟化的虚拟专用硬件资源。
  7. 根据权利要求2-6任一所述的方法，其中，所述对无线接入网的多个虚拟网络服务进行实例化处理，以得到所述虚拟网络服务对应的虚拟专用硬件资源信息以及用于小区覆盖处理的信息的步骤包括：
    利用无线接入设备的专用硬件的抽象模型描述文件和虚拟网络功能服务的模型描述文件，对无线接入网的多个虚拟网络服务进行实例化处理，以得到所述虚拟网络服务对应的虚拟专用硬件资源信息以及用于小区覆盖处理的信息。
  8. 根据权利要求7所述的方法，其中，所述专用硬件的抽象模型描述文件包括专用硬件型号、标准化的使用接口元数据、专用硬件能力描述信息及版本号信息，并且所述虚拟网络功能服务的模型描述文件包括虚拟网络功能服务名、标准化的接入接口定义元数据、服务能力描述信息及版本号信息。
  9. 根据权利要求7所述的方法，其中，所述对无线接入网的多个虚拟网络服务进行实例化处理，以得到所述虚拟网络服务对应的虚 拟专用硬件资源信息以及用于小区覆盖处理的信息的步骤包括：
    申请所述虚拟网络服务要使用的资源，并返回资源分配结果，其中，所述资源分配结果包括所述虚拟网络服务对应的虚拟专用硬件资源信息以及用于小区覆盖处理的信息。
  10. 根据权利要求1所述的方法，其中，所述根据所述虚拟专用硬件资源信息以及用于小区覆盖处理的信息，针对各虚拟网络服务，使用各个虚拟网络服务模块来执行操作的步骤包括：
    使用各个虚拟网络服务模块来发起小区资源变更流程，或
    使用各个虚拟网络服务模块来发起小区资源释放流程，或
    使用各个虚拟网络服务模块来发起故障资源自愈流程。
  11. 一种无线网络功能虚拟化装置，包括：
    确定模块，其设置为确定无线接入设备对应的虚拟专用硬件资源；
    实例化处理模块，其设置为对无线接入网的多个虚拟网络服务进行实例化处理，以得到所述虚拟网络服务对应的虚拟专用硬件资源信息以及用于小区覆盖处理的信息；以及
    执行模块，其设置为根据所述虚拟专用硬件资源信息以及用于小区覆盖处理的信息，针对各虚拟网络服务，使用各个虚拟网络服务模块来执行操作。
  12. 根据权利要求11所述的装置，其中，所述无线接入设备是用于将所述无线接入网的网络功能虚拟化的设备，并且其中，所述确定模块还设置为：确定所述无线接入设备的专用硬件资源对应的用于所述虚拟化的虚拟专用硬件资源。
  13. 根据权利要求11所述的装置，其中，所述实例化处理模块还设置为：
    利用无线接入设备的专用硬件的抽象模型描述文件和虚拟网络 功能服务的模型描述文件，对无线接入网的多个虚拟网络服务进行实例化处理，以得到所述虚拟网络服务对应的虚拟专用硬件资源信息以及用于小区覆盖处理的信息。
  14. 根据权利要求12所述的装置，其中，所述专用硬件的抽象模型描述文件包括专用硬件型号、标准化的使用接口元数据、专用硬件能力描述信息及版本号信息，并且所述虚拟网络功能服务的模型描述文件包括虚拟网络功能服务名、标准化的接入接口定义元数据、服务能力描述信息及版本号信息。
  15. 据权利要求13所述的装置，其中，所述实例化处理模块还设置为：
    申请所述虚拟网络服务要使用的资源，并返回资源分配结果，其中，所述资源分配结果包括所述虚拟网络服务对应的虚拟专用硬件资源信息以及用于小区覆盖处理的信息。
  16. 据权利要求11所述的装置，其中，所述执行模块还设置为：
    使用各个虚拟网络服务模块来发起小区资源变更流程，或
    使用各个虚拟网络服务模块来发起小区资源释放流程，或
    使用各个虚拟网络服务模块来发起故障资源自愈流程。
  17. 一种计算机可读介质，其存储有计算机可读指令，当所述指令被处理器执行时，使得所述处理器执行如权利要求1-10中任一项所述的无线网络功能虚拟化方法。
PCT/CN2018/088446 2017-05-26 2018-05-25 无线网络功能虚拟化方法及装置 WO2018214965A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP18805298.9A EP3633956B1 (en) 2017-05-26 2018-05-25 Wireless network function virtualization method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710395408.7A CN108934013B (zh) 2017-05-26 2017-05-26 一种无线网络功能虚拟化方法及装置
CN201710395408.7 2017-05-26

Publications (1)

Publication Number Publication Date
WO2018214965A1 true WO2018214965A1 (zh) 2018-11-29

Family

ID=64396253

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/088446 WO2018214965A1 (zh) 2017-05-26 2018-05-25 无线网络功能虚拟化方法及装置

Country Status (3)

Country Link
EP (1) EP3633956B1 (zh)
CN (1) CN108934013B (zh)
WO (1) WO2018214965A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111865630B (zh) * 2019-04-26 2023-03-24 北京达佳互联信息技术有限公司 拓扑信息获取方法、装置、终端及存储介质
CN111352787B (zh) * 2020-03-13 2023-08-18 浪潮商用机器有限公司 一种gpu拓扑连接检测方法、装置、设备及存储介质
CN112468325B (zh) * 2020-11-11 2023-07-11 广州鲁邦通物联网科技股份有限公司 一种可复用的vpn架构和vpn调度方法
CN116457757A (zh) 2020-11-12 2023-07-18 三星电子株式会社 用于将gpu分配给软件包的方法和设备
CN114828038A (zh) * 2021-01-19 2022-07-29 维沃移动通信有限公司 接入网***
CN115514657B (zh) * 2022-11-15 2023-03-24 阿里云计算有限公司 网络建模方法、网络问题分析方法及相关设备

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104050045A (zh) * 2014-06-27 2014-09-17 华为技术有限公司 基于磁盘io的虚拟资源分配方法及装置
CN105049293A (zh) * 2015-08-21 2015-11-11 中国联合网络通信集团有限公司 监控的方法及装置
CN105703927A (zh) * 2014-11-25 2016-06-22 华为软件技术有限公司 一种资源分配方法、网络设备和网络***
CN105812434A (zh) * 2014-12-30 2016-07-27 华为技术有限公司 用户手持设备虚拟化后的业务链控制方法及装置
US20160234077A1 (en) * 2015-02-09 2016-08-11 Mellanox Technologies Ltd. Time-efficient network function virtualization architecture
WO2017051172A1 (en) * 2015-09-22 2017-03-30 Vodafone Ip Licensing Limited Network services roaming in nfv environment

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9146785B2 (en) * 2011-09-14 2015-09-29 Microsoft Technology Licensing, Llc Application acceleration in a virtualized environment
WO2015187965A1 (en) * 2014-06-05 2015-12-10 Huawei Technologies Co., Ltd System and method for real time virtualization
EP2955631B1 (en) * 2014-06-09 2019-05-01 Nokia Solutions and Networks Oy Controlling of virtualized network functions for usage in communication network
JP6686910B2 (ja) * 2015-01-23 2020-04-22 日本電気株式会社 ネットワーク機能仮想化管理およびオーケストレーション方法と装置とプログラム
CN105429780B (zh) * 2015-10-30 2019-04-23 南京优速网络科技有限公司 一种虚拟化网络服务业务自动生成和动态监控的方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104050045A (zh) * 2014-06-27 2014-09-17 华为技术有限公司 基于磁盘io的虚拟资源分配方法及装置
CN105703927A (zh) * 2014-11-25 2016-06-22 华为软件技术有限公司 一种资源分配方法、网络设备和网络***
CN105812434A (zh) * 2014-12-30 2016-07-27 华为技术有限公司 用户手持设备虚拟化后的业务链控制方法及装置
US20160234077A1 (en) * 2015-02-09 2016-08-11 Mellanox Technologies Ltd. Time-efficient network function virtualization architecture
CN105049293A (zh) * 2015-08-21 2015-11-11 中国联合网络通信集团有限公司 监控的方法及装置
WO2017051172A1 (en) * 2015-09-22 2017-03-30 Vodafone Ip Licensing Limited Network services roaming in nfv environment

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3633956A4 *

Also Published As

Publication number Publication date
EP3633956A4 (en) 2020-11-04
CN108934013B (zh) 2023-05-26
CN108934013A (zh) 2018-12-04
EP3633956A1 (en) 2020-04-08
EP3633956B1 (en) 2024-07-10

Similar Documents

Publication Publication Date Title
WO2018214965A1 (zh) 无线网络功能虚拟化方法及装置
US10701139B2 (en) Life cycle management method and apparatus
US11947697B2 (en) Method and system to place resources in a known state to be used in a composed information handling system
US10050850B2 (en) Rack awareness data storage in a cluster of host computing devices
EP3291499B1 (en) Method and apparatus for network service capacity expansion
CN110720091B (zh) 用于与托管的应用/虚拟网络功能(vnf)协调基础设施升级的方法
US20220075666A1 (en) Containerized vnf deployment method and related device
US9841988B1 (en) Updating service virtual machines using a new image that is certified
WO2017080391A1 (zh) 一种网络服务部署方法和装置
US11539582B1 (en) Streamlined onboarding of offloading devices for provider network-managed servers
WO2020103925A1 (zh) 一种容器化虚拟网络功能的部署方法和装置
US20210326306A1 (en) Method and apparatus for deploying virtualised network function
WO2014029239A1 (zh) 虚拟机放置策略的配置方法及装置
CN108737131A (zh) 网络设备虚拟化的实现方法和装置
WO2019001140A1 (zh) 一种管理vnf实例化的方法和设备
US11720425B1 (en) Multi-tenant radio-based application pipeline processing system
CN116800616B (zh) 虚拟化网络设备的管理方法及相关装置
WO2020249080A1 (zh) 一种虚拟网络功能vnf部署方法及装置
JP2024501005A (ja) コンテナクラスタのための管理方法および装置
US11937103B1 (en) Enhancing availability of radio-based applications using multiple compute instances and virtualized network function accelerators at cloud edge locations
CN112015515B (zh) 一种虚拟网络功能的实例化方法及装置
US11928515B2 (en) System and method for managing resource allocations in composed systems
WO2021129520A1 (zh) 网络业务的生命周期管理的授权方法及装置
WO2019011180A1 (zh) 一种License的发送方法和装置
US12008412B2 (en) Resource selection for complex solutions

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2018805298

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2018805298

Country of ref document: EP

Effective date: 20200102