WO2018072612A1 - 一种切片实例的管理方法及装置 - Google Patents

一种切片实例的管理方法及装置 Download PDF

Info

Publication number
WO2018072612A1
WO2018072612A1 PCT/CN2017/104408 CN2017104408W WO2018072612A1 WO 2018072612 A1 WO2018072612 A1 WO 2018072612A1 CN 2017104408 W CN2017104408 W CN 2017104408W WO 2018072612 A1 WO2018072612 A1 WO 2018072612A1
Authority
WO
WIPO (PCT)
Prior art keywords
management
slice instance
node
management node
network element
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2017/104408
Other languages
English (en)
French (fr)
Inventor
李卓明
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP17862941.6A priority Critical patent/EP3503472B1/en
Publication of WO2018072612A1 publication Critical patent/WO2018072612A1/zh
Priority to US16/385,419 priority patent/US10819592B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5077—Network service management, e.g. ensuring proper service fulfilment according to agreements wherein the managed service relates to simple transport services, i.e. providing only network infrastructure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • 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/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/78—Architectures of resource allocation

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a management method and apparatus for a slice instance.
  • Network Slice is an end-to-end logical network that includes individual network functions that are shared by customers or shared between customers, and the network connections between these network functions.
  • the slice management node 11 can instantiate the customized network slice by calling the virtualization management orchestration node 12 to obtain different network slice instances 13 (referred to as slices).
  • the operator 14 and the client 15 can send a service request for managing the slice instance 13 to the slice management node 11, and the service request can carry the identifier of the corresponding slice instance, so that the slice management node 11 can be based on the service.
  • a request is made to manage each of the network functional entities within the corresponding slice instance 13.
  • the management rights of the tiering instance 13 are different between the operator 14 and the client 15. Therefore, complex control logic needs to be set in the snippet management node 11 to determine the delivery of the sharding instance 13 by the operator 14 or the client 15. Whether the service request is reasonable to ensure that the operations of different slice instances 13 are logically isolated from each other. For example, slice instance A and slice instance B jointly use the same network function entity 1 to implement different service functions, when the operator 14 requests to change the slice. When a certain operating parameter of the network function entity 1 in the instance A may affect the slice instance B, the network function entity 1 cannot be used to implement the corresponding service function.
  • the corresponding control logic needs to be preset in the slice management node 11 to make
  • the slice management node 11 can determine whether the service request is reasonable in time when receiving the service request sent by the operator 14 or the client 15, which undoubtedly increases the implementation complexity of the slice management node 11 and aggravates the slice management node. 11 load.
  • Embodiments of the present invention provide a management method and apparatus for a slice instance, which can simplify the management complexity when managing a slice instance and reduce the load of the slice management node.
  • an embodiment of the present invention provides a management method of a slice instance, including: a slice instance management node receives a first service request from an operator system, where the first service request includes: the carrier system is configured to a first network The management information of the element, the first network element is a network element in a slice instance managed by the slice instance management node; if the first service request is within the first management authority, the instance management node uses the carrier system The management operation information of the first network element is sent to the first network element, where the first management authority is the carrier system included in the description file of the instance management node. The administrative rights of the instance.
  • the management method of the slice instance replaces the traditional slice management node to manage the slice instance by introducing the slice instance management node, which is already sliced in the process of instantiating the slice instance management node.
  • the first management authority of the trajectory instance is configured in the instance management node. Therefore, each of the network elements in the shard instance can be directly configured according to the configured first management privilege. Management operations can be performed without the need to set up complex control logic to determine whether the service requests issued by the operator system are reasonable, and the isolation between different slice instances is ensured, while the management during the management of the slice instances is reduced. Complexity and load consumption.
  • the method further includes: the slice instance management node receives a second service request from the client system, where the second service request includes: management operation information of the first network element by the client system; If the second service request is in the second management authority, the instance management node sends the management operation information of the first network element to the first network element, where the second management authority is in the description file.
  • the client system included includes administrative rights to the instance of the slice.
  • the second management authority of the client system to the slice instance has been configured in the slice instance management node during the process of instantiating the slice instance management node. Therefore, when the slice instance is actually run, the above configuration may be directly performed.
  • the second management authority can perform various management operations on each network element in the sharding instance without additional complicated control logic to determine whether the service request sent by the client system is reasonable, and further reduces the management during the management of the tiling instance. Complexity and load consumption.
  • the method further includes: the slice instance management node acquiring the operation information of the first network element according to the third management authority, where the third management authority is the allowed slice included in the description file The operation information required by the operator system and the client system obtained by the instance management node; the slice instance management node sends the operation information required by the operator system in the operation information to the operator system according to the fourth management authority, the The fourth management authority is the operation information included in the description file that allows the slice instance management node to report to the operator system.
  • the slice instance management node when the above-mentioned slice instance management node is instantiated, it is possible to define in advance in the description file which operation information of the network elements can be obtained by the slice instance management node, and the operation information includes the operation required by the operator system and the client system respectively. Information, then, after instantiating the slice instance management node according to the above description file, the slice instance management node has a third management authority for obtaining the above operation information and a fourth management authority for transmitting the required operation information to the operator system, and further, In the running process of the snippet instance, the snippet instance management node can directly obtain the related running information of the first network element in the snippet instance, and send the running information required by the operator system in the running information to the operator system.
  • the method further includes: the slice instance management node according to the fifth management authority, the running information The operation information required by the client system is sent to the client system, and the fifth management authority is the operation information included in the description file that allows the slice instance management node to report to the client system.
  • the slice instance management node has a fifth management right to send the required running information to the client system.
  • the slice instance management node can directly The operational information required by the client system in the operational information is sent to the customer system.
  • the method further includes: the virtualization management orchestration node acquiring a description file of the slice instance management node, where the description file includes the a software image of the slice instance management node, and a connection relationship between the slice instance management node and the N network elements in the slice instance, N ⁇ 1; the virtualization management orchestration node deploys the slice instance management node according to the software image; The virtualization management orchestration node establishes a management channel between the slice instance management node and the N network elements according to the connection relationship.
  • each slice is instantiated in the embodiment of the present invention, as compared with the prior art, which requires artificially deploying a slice management node and configuring a management policy within the slice management node to implement management of each slice instance.
  • the slice instance management node that manages the slice instance can be automatically deployed according to the corresponding description file.
  • the slice instance management node can automatically manage the slice instance in which it is configured according to the configured management rights during the instantiation process.
  • the automatic management process of the slice instance is realized, which greatly reduces the management cost and operation cost when managing the slice instance.
  • the description file further includes northbound interface information and southbound interface information;
  • the northbound interface information includes: an interface between the operator system and the client system, and the operator system and the client system pair.
  • the southbound interface information includes: an interface of each network element in the slice instance; wherein the virtualization management orchestration node establishes the slice instance management node and the slice instance according to the connection relationship After the management channel between the network elements, the virtualization management orchestration node configures the southbound interface and the northbound interface for the slice instance management node according to the southbound interface information and the northbound interface information.
  • the slice instance management node is deployed in the slice instance, or the slice instance management node is deployed in the carrier system, or the slice instance management node is deployed in the slice instance and the Outside the carrier system.
  • an embodiment of the present invention provides a method for instantiating a slice instance management node, including: a virtualization management orchestration node acquiring a description file of a slice instance management node, where the description file includes: software of the slice instance management node Mirroring, and a connection relationship between the node instance management node and the N network elements, where the N network elements are network elements in the slice instance managed by the slice instance management node, N ⁇ 1; the virtualization management orchestration node The slice instance management node is deployed according to the software image; the virtualization management orchestration node establishes a management channel between the slice instance management node and the N network elements according to the connection relationship.
  • the description file further includes northbound interface information and southbound interface information;
  • the northbound interface information includes: an interface to the operator system and the client system, and the carrier system and the client system The management authority of the slice instance;
  • the southbound interface information includes: an interface of each network element in the slice instance; wherein the virtualization management orchestration node establishes the slice instance management node and the N network elements according to the connection relationship After the management of the channel, the virtualization management orchestration node configures the southbound interface and the northbound interface for the slice instance management node according to the southbound interface information and the northbound interface information.
  • an embodiment of the present invention provides a slice instance management node, which has a function of implementing a behavior of a slice instance management node in the above method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • an embodiment of the present invention provides a virtualization management orchestration node, which has a function of implementing the virtualized management orchestration node behavior in the foregoing method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • an embodiment of the present invention provides a slice instance management node, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor is connected to the memory through the bus.
  • the processor executes the computer-executed instructions stored by the memory to cause the slice instance to manage a node row management method of the slice instance of any of the first aspects.
  • an embodiment of the present invention provides a virtualization management orchestration node, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor is connected to the memory through the bus.
  • the processor executes the computer-executed instruction stored in the memory to enable the
  • the virtualized management orchestration node row is an instantiation method of a slice instance management node according to any one of the second aspects.
  • an embodiment of the present invention provides a slice instance management system, including a slice instance management node and a virtualization management orchestration node.
  • the virtualization management orchestration node is configured to: obtain a description file of the slice instance management node, where the description file includes: a software image of the slice instance management node, and a connection relationship between the slice instance management node and the N network elements
  • the N network elements are the network elements in the slice instance managed by the slice instance management node, N ⁇ 1; the slice instance management node is deployed according to the software image; and the slice instance management node is established according to the connection relationship. Management channel between N network elements.
  • the first instance service request includes: And managing the network element in the snippet instance managed by the node; if the first service request is in the first management privilege, sending the management operation information of the first network element to the first network element,
  • An administrative authority is an administrative right of the carrier system included in the description file of the instance management node to the slice instance.
  • an embodiment of the present invention provides a computer storage medium, configured to store computer software instructions used by the slice instance management node, and includes a program designed to execute the above-described aspect for a slice instance management node.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions for the virtualization management orchestration node, which includes a program designed to perform the above aspects for a virtualization management orchestration node.
  • FIG. 1 is a schematic structural diagram of a management system of a network slice in the prior art
  • FIG. 2 is a schematic structural diagram 1 of a slicing instance management system according to an embodiment of the present invention
  • FIG. 3 is a schematic structural diagram 2 of a slice instance management system according to an embodiment of the present disclosure
  • FIG. 4 is a schematic structural diagram 3 of a slicing instance management system according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of a computer device according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic flowchart of a method for instantiating a slice instance management node according to an embodiment of the present disclosure
  • FIG. 7 is a schematic diagram of interaction of a management method of a slice instance according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram 1 of a slice instance management node according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram 1 of a virtualization management orchestration node according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram 2 of a slicing instance management node according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram 2 of a virtualization management orchestration node according to an embodiment of the present invention.
  • first and second are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or The implied indicates the number of technical features indicated. Thus, features defining “first” and “second” may include one or more of the features either explicitly or implicitly. In the description of the present invention, “a plurality” means two or more unless otherwise stated.
  • Embodiments of the present invention provide a management method of a slice instance, which can be applied to a slice instance management system 100 as shown in FIG. 2, which includes a virtualized management orchestration node 25 and a slice instance management that can communicate with each other.
  • Node 21 wherein the slice instance management node 21 can be deployed within any slice instance, and the slice instance management node 21 can communicate with the operator system 22 and the client system 23, respectively.
  • the virtualization management orchestration node 25 can deploy the slice instance management node 21 as a network element having the function of managing the slice instance in the slice instance, and establish the slice instance management node 21.
  • the virtualization management orchestration node 25 performs an instantiation operation on the slice instance management node 21 while instantiating the above-described slice instance.
  • the operator system 22 when the operator system 22 sends a corresponding service request to the network element 24 in the slice instance to manage the slice instance, it needs to first pass between the carrier system 22 and the slice instance management node 21.
  • the interface sends the service request to the slice instance management node 21, and the service request is authenticated by the slice instance management node 21, if the service request is deployed for the operator system 22 when the instance management node 21 is instantiated Within the management authority, the corresponding management operation can be performed according to the service request; otherwise, the service request can be directly ignored.
  • the service request is sent to the interface between the client system 23 and the slice instance management node 21 first.
  • the slice instance management node 21, and further, the service request is authenticated by the slice instance management node 21, and if the service request is within the management authority deployed by the client system 23 when the instance management node 21 is instantiated, the service request may be followed. Perform the corresponding management operation, otherwise, the service request can be directly ignored.
  • the slice instance management node 21 is introduced, and the slice instance is managed instead of the traditional slice management node, because in the process of instantiating the slice instance management node 21
  • the management rights of the operator instance 22 and the client system 23 for the slice instance are already configured in the slice instance management node 21. Therefore, when the slice instance is actually run, the above-mentioned management authority can be directly configured in the slice instance.
  • Each network element can perform various management operations without additional complicated control logic to determine whether the service request sent by the operator system 22 or the client system 23 is reasonable, and the isolation between different slice instances is ensured. At the same time, the management complexity and load consumption during the management of the slice instance are reduced.
  • the sharding instance management node 21 may also have the functions of performing statistics and reporting on the running information of the tiling instance, which will be described in detail in subsequent embodiments, and therefore will not be described again here.
  • the slice instance management node 21 may be deployed at any position other than the slice instance, for example, as shown in FIG.
  • the instance management node 21 may be deployed in a separate device configuration outside the slice instance.
  • the slice instance management node 21 may be integrated into the operator system 22 or the client system 23 as a functional unit.
  • the embodiment of the present invention does not impose any limitation on this.
  • any one of the function nodes or network elements involved in the above-described slice instance management system 100 may be By one
  • the physical device implementation may also be implemented by multiple physical devices.
  • the multiple functional nodes in the slice instance management system 100 may be implemented by different physical devices, or may be implemented by the same physical device.
  • any one of the function nodes in the slice instance management system 100 may be a logical function module in the physical device, or may be a logical function module composed of multiple physical devices.
  • the virtualization management orchestration node 25 and the slice instance management node 21 of FIGS. 2 through 4 can be implemented in the manner of the computer device (or system) in FIG.
  • FIG. 5 is a schematic diagram of a computer device according to an embodiment of the present invention.
  • the computer device 200 includes at least one processor 51, a communication bus 52, a memory 53, and at least one communication interface 54.
  • the processor 51 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present invention.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • Communication bus 52 can include a path for communicating information between the components described above.
  • the communication interface 54 uses devices such as any transceiver for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), and the like.
  • RAN Radio Access Network
  • WLAN Wireless Local Area Networks
  • the memory 53 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device can also be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • the memory can exist independently and be connected to the processor via a bus.
  • the memory can also be integrated with the processor.
  • the memory 53 is used to store application code for executing the solution of the present invention, and is controlled by the processor 51 for execution.
  • the processor 51 is configured to execute application code stored in the memory 53.
  • processor 51 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • computer device 200 can include multiple processors, such as processor 51 and processor 58 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • computer device 200 may also include an output device 55 and an input device 56.
  • Output device 55 is in communication with processor 51 and can display information in a variety of ways.
  • the output device 55 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait.
  • Input device 56 is in communication with processor 51 and can accept user input in a variety of ways.
  • input device 56 can be a mouse, keyboard, touch screen device, or sensing device, and the like.
  • the computer device 200 described above can be a general purpose computer device or a special purpose computer device.
  • the computer device 200 can be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet, a wireless terminal device, a communication device, an embedded device, or have FIG. A device of similar structure.
  • Embodiments of the invention do not limit the type of computer device 200.
  • the virtualization management orchestration node 25 in FIG. 2 to FIG. 4 may be the device shown in FIG. 5, and one or more software modules are stored in the memory of the virtualization management orchestration node 25.
  • the virtualization management orchestration node 25 can implement the software module by using the processor and the program code in the memory to implement the instantiation process of the slice instance management node 21.
  • the middle slice instance management node 21 of FIGS. 2-4 may be the device shown in FIG. 5, and one or more software modules are stored in the memory of the slice instance management node 21.
  • the slice instance management node 21 can implement the software module by using the processor and the program code in the memory to implement the management process of the slice instance.
  • the following describes the logical function module as an execution subject, and the technology in the field Personnel can understand that the logic function module depends on the hardware resources on the physical device where it is implemented.
  • the above-described slice instance management system 100 can be applied to a future fifth-generation mobile communication (English: 5rd-Generation, abbreviated: 5G) system, long-term evolution (English: long term evolution, abbreviation: LTE
  • 5G fifth-generation mobile communication
  • LTE long-term evolution
  • WCDMA third-generation mobile communication
  • 3G 3rd-Generation, Abbreviation: 3G
  • an embodiment of the present invention provides an instantiation method of a sharding instance management node 21, as shown in FIG.
  • the virtualization management orchestration node acquires a description file of the slice instance management node.
  • the operator system 22 will define different slice blueprints for different slice instances during the design phase prior to instantiating the slice instances.
  • the relevant parameter information of the slice instance is generally set in the slice blueprint, for example, network topology information, functional component information, interactive protocol information, performance indicator information, and/or hardware requirement information.
  • the connection relationship between the slice instance management node 21 and each network element in the slice instance may be defined in the slice blueprint.
  • the management authority of the slice instance management node 21 for example, the permission scope of the service operation of the slice instance management node 21 at the network resource layer, the network function layer, and/or the network control layer, and the operation information of which services or network elements are collected, and the like .
  • the operator system 22 can generate the description file of the slice instance and the description file of the slice instance management node 21 according to the above blueprint, and send the description files to the virtualization management orchestration node 25, which is managed by virtualization.
  • the orchestration node 25 completes the instantiation operation of the slice instance and the slice instance management node 21.
  • the description file of the above-mentioned sharding instance may specifically include an NSD (Network Service Descriptor) defined by an NFV (Network Function Virtualization) standard, and a VLD (Virtual Link Descriptor). And at least one of VNFFGD (VNF Forwarding Graph Descriptor).
  • NSD Network Service Descriptor
  • NFV Network Function Virtualization
  • VLD Virtual Link Descriptor
  • VNFFGD VNF Forwarding Graph Descriptor
  • the description file of the above-mentioned slice instance management node 21 may include: a software image of the slice instance management node 21, and a connection relationship between the slice instance management node 21 and N (N ⁇ 1) network elements, the N network elements The network element in the slice instance managed by the node instance management node.
  • the description file of the above-mentioned slice instance management node 21 is a new description file of the embodiment of the present invention.
  • the software image of the slice instance management node 21 may be: VNFD (VNF Descriptor, virtual network function) of the slice instance management node 21 itself.
  • VNFD VNF Descriptor, virtual network function
  • the descriptor relationship between the slice instance management node 21 and the N network elements may be: a virtual link descriptor of the management channel between the slice instance management node 21 and the N network elements.
  • the virtualization management orchestration node deploys the slice instance management node according to the foregoing software image.
  • the virtualization management orchestration node establishes a management channel between the slice instance management node and the N network elements in the slice instance managed by the slice according to the foregoing connection relationship.
  • the virtualization management orchestration node 25 may further allocate resources for the slice instance on the virtualization infrastructure, and follow the above slice instance.
  • the description file is used to deploy the network elements in the slice instance. Then, the connection between the network elements is established according to the description file of the above-mentioned slice instance, and the instantiation operation of the slice instance is completed.
  • the virtualization management orchestration node 25 may further allocate resources for the slice instance management node 21 on the virtualization infrastructure.
  • the software image of the slice instance management node 21 may be installed in the above-described slice instance to deploy the slice instance management node 21; and, as described in step 103, the node 21 is managed according to the slice instance. Establish a management channel between the slice instance management node 21 and the N network elements, and the connection relationship between the N network elements.
  • the description file of the slice instance management node 21 obtained in step 101 may further include: southbound interface information and northbound interface information.
  • the information of the northbound interface includes: an interface between the slice instance management node 21 and the operator system 22 and the client system 23, and management rights of the operator system 22 and the client system 23 to the slice instance; the southbound interface information includes: a slice instance.
  • the management node 21 interfaces with each network element in the above-mentioned slice instance.
  • the northbound interface information may be: a northbound interface configuration description between the slice instance management node 21 and the carrier system 22, and a northbound interface configuration description between the slice instance management node 21 and the client system 23, the configuration The management authority of the operator system 22 and the client system 23 for the above-described slice instance is defined in the description.
  • the southbound interface information may be: a description of the southbound interface configuration between the slice instance management node 21 and each network element.
  • the northbound interface between the client system 23 and the slicing instance management node 21 may include a client-customized API (Application Programming Interface), so that the APIs provided for different client systems 23 are not globally unified.
  • client-customized API Application Programming Interface
  • the virtualization management orchestration node 25 can also perform the following step 104, namely:
  • the virtualization management orchestration node configures the southbound interface and the northbound interface for the slice instance management node according to the southbound interface information and the northbound interface information.
  • the slice instance management node 21 can communicate with each network element in the slice instance through the southbound interface, for example, collecting memory of each network element at runtime.
  • the operation information of the size and the like; and the slice instance management node 21 can also communicate with the operator system and the client system through the northbound interface respectively, wherein the northbound interface between the slice instance management node 21 and the operator system, and the slice instance management node
  • the northbound interface between the client and the client system may be the same or different, and the embodiment of the present invention does not impose any limitation.
  • the virtualization management orchestration node 25 configures the northbound interface for the slice instance management node 21 according to the northbound interface information
  • the management rights of the operator instance 22 and the client system 23 for the slice instance are respectively configured.
  • the slice instance management node 21 can directly manage the network elements in the slice instance by the operator system 22 and the client system 23 according to the configured management rights, without additionally setting complicated control logic. It is determined whether the service request issued by the operator system 22 or the client system 23 is reasonable, thereby reducing the management complexity and load consumption in managing the slice instance.
  • each slice is instantiated in the embodiment of the present invention, as compared with the prior art, which requires artificially deploying a slice management node and configuring a management policy within the slice management node to implement management of each slice instance.
  • the slice instance management node 21 that manages the slice instance can be automatically deployed according to the corresponding description file. Subsequently, the slice instance management node 21 can automatically manage the location according to the configured management rights during the instantiation process.
  • the slicing instance realizes the automated management process of the slicing instance, which greatly reduces the management cost and operating cost when managing the slicing instance.
  • the above step 102 is performed (ie, the slice instance management node is deployed according to the software image above). 21) Afterwards, the deployed slice instance management node 21 already has the southbound interface and the northbound interface. In this case, the above step 104 need not be performed.
  • the virtualization management orchestration node 25 deploys the slice instance management node 21 in the slice instance in the process of deploying the slice instance, and completes the instantiation operation on the slice instance management node 21.
  • the operation of the virtualization management orchestration node 25 in the above steps 101-104 can be performed by the virtualization management orchestration node 25 according to the corresponding software module in the memory mentioned in FIG. 5, which is not limited in this embodiment of the present invention. .
  • the slice instance management node 21 can manage the slice instance in which it is located.
  • an embodiment of the present invention provides a method for managing a slice instance, where the method includes:
  • the slice instance management node 21 receives the first service request from the operator system 22, where the first service request includes: management operation information of the first network element by the operator system 22.
  • the first network element is a network element in a slice instance managed by the slice instance management node 21, and the slice instance management system 100 shown in FIG. 2 is taken as an example, and the slice instance managed by the slice instance management node 21 is The slice instance deployed by the slice instance management node 21, that is, the slice instance obtained after the instantiation operation is performed simultaneously with the slice instance management node 21 in steps 101-104.
  • the first service request may be sent to the slice instance management node 21 of the management slice instance 1.
  • the first service request may be a request to perform a capacity expansion operation on the first network element.
  • the first service request includes the management operation information of the first network element by the operator system 22, that is, the specific operation content of the first service request, for example, the specific expansion strategy when the first network element is expanded. .
  • the operator system 22 may send the first service request to the slice instance management node 21 by instantiating the southbound interface defined by the above-described slice instance management node 21 in step 104.
  • the instance management node 21 sends the management operation information of the first network element by the operator system 22 to the first network element.
  • the first management authority is included in the description file of the instance management node 21: the management authority of the operator system 22 to the slice instance.
  • the management rights of the snippet instance management node 21 are configured by the operator system 22, and the management privilege includes the first management privilege.
  • the first admin privilege may be:
  • the carrier system 22 performs the capacity expansion operation and the capacity reduction operation on the network element 1 and the network element 2.
  • step 202 if the first service request is within the first management authority, the instance management node 21 sends the management operation information of the first network element by the operator system 22 in the first service request to the first network. Yuan, by the first network element Perform the corresponding operation content according to the management operation information, for example, expand according to the above expansion strategy.
  • the instance management node 21 and the operator may be different from the protocol used by the instance management node 21 and the first network element.
  • the protocol used by the system 22 for communication may be different from the protocol used by the instance management node 21 and the first network element.
  • the instance management node 21 needs to parse and convert the received first service request.
  • the carrier system 22 in the first service request converts the management operation information of the first network element into a format that can be identified by the first network element, and sends the information to the first network element.
  • the slice instance management node 21 may also perform a management operation on the slice instance by using the service request sent by the client system 23 (ie, the second service request).
  • the embodiment of the present invention does not limit the logical relationship between the steps 203-204 and the steps 201-202, that is, the steps 203-204 may be performed after or before the execution of the steps 201-202, or the slice instance management node 21 can also perform steps 203-204 and steps 201-202 simultaneously.
  • the slice instance management node 21 receives the second service request from the client system 23, where the second service request includes: management operation information of the first network element by the client system 23.
  • the instance management node 21 sends the management operation information of the first network element by the client system 23 to the first network element.
  • the second service request may be sent to the slice instance management node 21 of the management slice instance 1.
  • the second service request may be the same as or different from the first service request.
  • the second service request includes management operation information of the first network element by the client system 23, and the management operation information of the first network element by the client system 23 and the management operation information of the first network element by the carrier system 22 may be Same or different.
  • step 104 the management authority of the client instance 23 to the slice instance management node 21 is also configured by the southbound interface information, and the second administrative authority is included in the management authority.
  • step 204 if the second service request is within the second management authority, the instance management node 21 sends the management operation information of the first network element by the client system 23 in the second service request to the first network element.
  • the first network element may perform the corresponding operation content according to the management operation information.
  • the slice instance management node 21 also obtains the operation information of the relevant network element in the required slice instance for the operator system 22 and/or the client system 23.
  • the embodiment of the present invention does not limit the logical relationship between steps 205-206b, steps 203-204, and steps 201-202.
  • the sharding instance management node 21 obtains the running information of the first network element according to the third management privilege.
  • the third management authority is the operation information included in the description file that allows the operator system 22 and the client system 23 acquired by the slice instance management node 21.
  • the slice instance management node 21 when the above-mentioned slice instance management node 21 is instantiated, it is possible to define in advance in the description file which operation information of which network elements the slice instance management node 21 can acquire, the operation information including the operator system 22 and the client system 23
  • the slice instance management node 21 has the third management authority for obtaining the above-mentioned operation information. Further, in the slice instance operation phase, the slice instance management node 21 may follow the third The management authority is used to obtain related operation information of the first network element in the slice instance through the southbound interface.
  • the slice instance management node 21 performs the operation required by the carrier system 22 in the operation information according to the fourth management authority.
  • the line information is sent to the carrier system 22.
  • the fourth management authority is the operation information included in the description file that allows the slice instance management node 21 to report to the operator system 22.
  • the management authority of the slice instance management node 21 by the operator system 22 is configured by using the southbound interface information, where the management authority includes the fourth management authority, for example, the fourth management authority is specific.
  • the carrier system 22 is allowed to obtain the CPU usage and memory usage of the first network element during the running process.
  • the slice instance management node 21 can directly send the operation information required by the operator system 22 in the operation information acquired in step 205 to the operator system 22 according to the fourth management authority.
  • the slice instance management node 21 transmits the operation information required by the client system 23 in the operation information to the client system 23 according to the fifth management authority.
  • the fifth management authority is the operation information included in the description file that allows the slice instance management node 21 to report to the client system 23.
  • the management authority of the slice instance management node 21 by the client system 23 is configured by the southbound interface information, and the management authority includes the fifth management authority, for example, the fifth management authority may specifically To allow the client system 23 to obtain the memory usage of the first network element during the running process.
  • the slice instance management node 21 can directly send the operation information required by the client system 23 in the operation information acquired in step 205 to the client system 23 according to the fifth management authority.
  • the operator system 22 and the client system 23 can determine the running status of the slice instance according to the obtained running information, and perform corresponding management operations on the slice instance, for example, the operator system 22 goes to the slice instance management node 21.
  • the client system 23 delivers the second service request as described in step 203 to the slice instance management node 21 to ensure normal operation of each service in the slice instance.
  • the slice instance management node 21 manages the first network element as an example, and the slice instance management node 21 manages other network elements in the slice instance, and the slice instance management node 21 manages The method of the first network element is similar, so it will not be described here.
  • the action of the slice instance management node 21 in the above steps 201-206b may be performed by the slice instance management node 21 according to the corresponding software module in the memory mentioned in FIG. 5, which is not limited in this embodiment of the present invention.
  • the embodiment of the present invention provides a management method for a slice instance, which introduces a slice instance management node, and replaces the traditional slice management node to manage the slice instance.
  • the slice instance is The management node and the client system have been configured with the management rights of the slice instance. Therefore, when the slice instance is run, the slice instance management node can directly manage the network elements in the slice instance according to the configured management rights. It is possible to determine whether the service request sent by the operator system or the client system is reasonable, and to ensure the isolation between different slice instances while reducing the management during the management of the slice instance. Complexity and load consumption.
  • the solution provided by the embodiment of the present invention is mainly introduced from the perspective of interaction between the network elements.
  • the virtualization management orchestration node 25 and the slice instance management node 21 and the like include hardware structures and/or software modules corresponding to the execution of the respective functions in order to implement the above functions.
  • the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. Professionals can implement different methods for each specific application. The described functionality, but such implementation should not be considered to be outside the scope of the present invention.
  • the embodiment of the present invention may divide the functional modules of the virtualization management orchestration node 25, the slice instance management node 21, and the like according to the foregoing method examples.
  • each functional module may be divided according to each function, or two or more of the functional modules may be divided.
  • the functions are integrated in one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 8 is a schematic diagram showing a possible structure of the slice instance management node 21 involved in the foregoing embodiment, and the slice instance management node 21 may be FIG. 2 A possible example of a slice instance management node 21 shown in FIG.
  • the slice instance management node 21 includes: an obtaining module 31, a determining module 32, and a sending module 33.
  • the obtaining module 31 is configured to receive a first service request from the operator system, where the first service request includes: management operation information of the first network element by the operator system, where the first network element is the slice The network element in the slice instance managed by the instance management node;
  • a determining module 32 configured to determine whether the first service request is within the first management authority, where the first management authority is the carrier system included in the description file of the instance management node Administrative authority;
  • the sending module 33 is configured to send, to the first network element, management operation information of the first network element by the operator system, if the first service request is within the first management authority.
  • the obtaining module 31 is further configured to receive a second service request from the client system, where the second service request includes: management operation information of the first network element by the client system;
  • the determining module 32 is further configured to determine whether the second service request is within the second management authority, where the second management authority is an administrative right of the client system included in the description file to the slice instance. ;
  • the sending module 33 is further configured to: if the second service request is in the second management authority, send the management operation information of the first network element to the first network element.
  • the obtaining module 31 is further configured to acquire, according to the third management authority, operation information of the first network element, where the third management authority is a permission for the slice instance management node included in the description file. Obtaining operational information required by the operator system and the customer system;
  • the sending module 33 is further configured to: send, according to the fourth management authority, operation information required by the operator system in the operation information to the operator system, where the fourth management authority is in the description file.
  • the operating information that is allowed to be reported by the slice instance management node to the operator system is included.
  • the sending module 33 is further configured to send operation information required by the client system in the operation information to the client system according to the fifth management authority, where the fifth management authority is the description file.
  • the operation information included in the client system is allowed to be reported by the slice instance management node.
  • FIG. 9 is a schematic diagram of a possible structure of the virtualization management orchestration node 25 involved in the foregoing embodiment, and the slice instance management node 21 may be as shown in FIG. 2 .
  • the virtualization management orchestration node 25 includes an acquisition module 41, a deployment module 42, and an establishment module 43.
  • the obtaining module 41 is configured to acquire a description file of the slice instance management node, where the description file includes: the slice a software image of the instance management node, and a connection relationship between the slice instance management node and the N network elements, where the N network elements are network elements in the slice instance managed by the slice instance management node, N ⁇ 1;
  • a deployment module 42 configured to deploy the slice instance management node according to the software image
  • the establishing module 43 is configured to establish, according to the connection relationship, a management channel between the slice instance management node and the N network elements.
  • the virtualization management orchestration node 25 may further include:
  • the configuration module 44 is configured to configure a southbound interface and a northbound interface for the slice instance management node according to the southbound interface information and the northbound interface information.
  • FIG. 10 shows a possible structural diagram of the slice instance management node 21 involved in the above embodiment.
  • the slice instance management node 21 includes a processing module 1002 and a communication module 1003.
  • the processing module 1002 is configured to control and manage the actions of the slice instance management node 21, for example, the processing module 1002 is configured to support the slice instance management node 21 to perform the processes 201-206b in FIG. 7, and/or for the techniques described herein. Other processes.
  • the communication module 1003 is configured to support communication between the slice instance management node 21 and other network entities, such as with the functional modules or network entities shown in Figures 2-4.
  • the slice instance management node 21 may further include a storage module 1001 for storing program codes and data of the slice instance management node 21.
  • FIG. 11 shows a possible structural diagram of the virtualization management orchestration node 25 involved in the above embodiment.
  • the virtualization management orchestration node 25 includes a processing module 1102 and a communication module 1103.
  • the processing module 1102 is configured to control and manage the actions of the virtualization management orchestration node 25, for example, the processing module 1102 is configured to support the virtualization management orchestration node 25 to perform the processes 101-104 of FIG. 6, and/or for the purposes described herein. Other processes of technology.
  • the communication module 1103 is for supporting communication between the virtualization management orchestration node 25 and other network entities, such as communication with the functional modules or network entities shown in Figures 2-4.
  • the virtualization management orchestration node 25 may further include a storage module 1101 for storing program codes and data of the virtualization management orchestration node 25.
  • the processing module 1002/1102 may be a processor or a controller, and may be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application specific integrated circuit (Application). -Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication module 1003/1103 may be a transceiver, a transceiver circuit, a communication interface, or the like.
  • the storage module 1001/1101 may be a memory.
  • the processing module 1002/1102 is a processor
  • the communication module 1003/1103 is a communication interface
  • the storage module 1001/1101 is a memory
  • the slice instance management node 21 or the virtualization management orchestration node 25 according to the embodiment of the present invention may be a figure.
  • the functions described herein can be implemented in hardware, software, firmware, or any combination thereof.
  • the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium.
  • the computer readable medium includes a computer storage medium and a communication medium, wherein the communication medium includes a convenient transfer from one place to another Any medium that sends a computer program.
  • a storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

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)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明的实施例提供一种切片实例的管理方法及装置，涉及通信技术领域，可简化管理切片实例时的管理复杂度，降低切片管理节点的负载。该方法包括：切片实例管理节点接收来自运营商系统的第一业务请求，该第一业务请求包括：该运营商系统对第一网元的管理操作信息，该第一网元为该切片实例管理节点所管理的切片实例中的网元；若该第一业务请求在第一管理权限内，则该实例管理节点将该运营商系统对第一网元的管理操作信息发送至该第一网元，该第一管理权限为该实例管理节点的描述文件中包括的该运营商系统对该切片实例的管理权限。

Description

一种切片实例的管理方法及装置
本申请要求于2016年10月18日提交中国专利局、申请号为201610908985.7、发明名称为“一种切片实例的管理方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，尤其涉及一种切片实例的管理方法及装置。
背景技术
网络切片(Network Slice)是一个端到端的逻辑网络，它包括客户专用的或客户之间共享的各个网络功能，以及这些网络功能之间的网络连接关系。
目前，网络切片的管理系统如图1所示，切片管理节点11可以通过调用虚拟化管理编排节点12，对客户定制的网络切片进行实例化操作，以得到不同的网络切片实例13(简称为切片实例)，后续，运营商14和客户15均可以向切片管理节点11发送用于管理切片实例13的业务请求，业务请求中可携带相应的切片实例的标识，这样，切片管理节点11可以根据业务请求对相应的切片实例13内的各个网络功能实体进行管理。
但是，通常运营商14和客户15对切片实例13的管理权限是不相同的，因此，切片管理节点11内需要设置复杂的控制逻辑，来确定运营商14或客户15对切片实例13下发的业务请求是否合理，以保证不同切片实例13的操作在逻辑上是互相隔离，例如，切片实例A和切片实例B共同使用相同的网络功能实体1实现不同的业务功能，当运营商14要求更改切片实例A中网络功能实体1的某一运行参数时，可能会影响切片实例B无法继续使用网络功能实体1实现相应的业务功能，因此，切片管理节点11内需要预先设置相应的控制逻辑，以使得切片管理节点11可以在接收到上述运营商14或客户15发送的业务请求时，能够及时确定该业务请求是否合理，而这无疑增加了切片管理节点11的实现复杂度，且加重了切片管理节点11的负载。
发明内容
本发明的实施例提供一种切片实例的管理方法及装置，可简化管理切片实例时的管理复杂度，降低切片管理节点的负载。
为达到上述目的，本发明的实施例采用如下技术方案：
第一方面，本发明的实施例提供一种切片实例的管理方法，包括：切片实例管理节点接收来自运营商系统的第一业务请求，该第一业务请求包括：该运营商系统对第一网元的管理操作信息，该第一网元为该切片实例管理节点所管理的切片实例中的网元；若该第一业务请求在第一管理权限内，则该实例管理节点将该运营商系统对第一网元的管理操作信息发送至该第一网元，该第一管理权限为该实例管理节点的描述文件中包括的该运营商系统对该切片 实例的管理权限。也就是说，本发明的实施例提供的切片实例的管理方法通过引入切片实例管理节点，替代传统的切片管理节点对切片实例进行管理，由于在实例化切片实例管理节点的过程中，已经在切片实例管理节点内配置了运营商系统对切片实例的第一管理权限，因此，在实际运行该切片实例时，可直接按照配置好的上述第一管理权限对切片实例内的各个网元进行各项管理操作即可，而无需额外设置复杂的控制逻辑，来确定运营商系统下发的业务请求是否合理，在保证了不同切片实例之间的隔离性的同时，降低了管理切片实例过程中的管理复杂度和负载消耗。
在一种可能的设计方式中，该方法还包括：该切片实例管理节点接收来自客户系统的第二业务请求，该第二业务请求包括：该客户系统对该第一网元的管理操作信息；若该第二业务请求在第二管理权限内，则该实例管理节点将该客户系统对该第一网元的管理操作信息发送至该第一网元，该第二管理权限为该描述文件中包括的该客户系统对该切片实例的管理权限。由于在实例化切片实例管理节点的过程中，已经在切片实例管理节点内配置了客户系统对切片实例的第二管理权限，因此，在实际运行该切片实例时，可直接按照配置好的上述第二管理权限对切片实例内的各个网元进行各项管理操作即可，而无需额外设置复杂的控制逻辑，来确定客户系统下发的业务请求是否合理，进一步降低了管理切片实例过程中的管理复杂度和负载消耗。
在一种可能的设计方式中，该方法还包括：该切片实例管理节点按照第三管理权限，获取该第一网元的运行信息，该第三管理权限为该描述文件中包括的允许该切片实例管理节点获取的该运营商系统和客户系统需要的运行信息；该切片实例管理节点按照第四管理权限，将该运行信息中该运营商系统需要的运行信息发送至该运营商系统，该第四管理权限为该描述文件中包括的允许该切片实例管理节点上报至该运营商系统的运行信息。也就是说，在实例化上述切片实例管理节点时，可以预先在描述文件中定义切片实例管理节点可以获取哪些网元的哪些运行信息，这些运行信息包括了运营商系统和客户系统分别需要的运行信息，那么，按照上述描述文件实例化切片实例管理节点之后，切片实例管理节点便具有获取上述运行信息的第三管理权限以及向运营商系统发送其需要的运行信息的第四管理权限，进而，在切片实例运行阶段，切片实例管理节点可以直接获取切片实例内第一网元的相关运行信息，并将运行信息中运营商系统需要的运行信息发送至运营商系统。
在一种可能的设计方式中，在该切片实例管理节点按照第三管理权限，获取该第一网元的运行信息之后，还包括：该切片实例管理节点按照第五管理权限，将该运行信息中该客户系统需要的运行信息发送至该客户系统，该第五管理权限为该描述文件中包括的允许该切片实例管理节点上报至该客户系统的运行信息。类似的，按照上述描述文件实例化切片实例管理节点之后，切片实例管理节点便具有向客户系统发送其需要的运行信息的第五管理权限，进而，在切片实例运行阶段，切片实例管理节点可以直接将运行信息中客户系统需要的运行信息发送至客户系统。
在一种可能的设计方式中，在切片实例管理节点接收来自运营商系统的第一业务请求之前，还包括：虚拟化管理编排节点获取该切片实例管理节点的描述文件，该描述文件中包括该切片实例管理节点的软件镜像，以及该切片实例管理节点与该切片实例内N个网元之间的连接关系，N≥1；该虚拟化管理编排节点按照该软件镜像部署该切片实例管理节点；该虚拟化管理编排节点按照该连接关系，建立该切片实例管理节点与该N个网元之间的管理通道。 这样，相比于现有技术中需要人为部署切片管理节点，并配置切片管理节点内的管理策略，以实现对各个切片实例的管理而言，在本发明实施例中，在实例化每个切片实例的过程中，便可以根据相应的描述文件自动部署得到管理该切片实例的切片实例管理节点，后续，切片实例管理节点可自动按照实例化过程中已配置好的管理权限管理其所在的切片实例，实现了切片实例的自动化管理过程，大大降低了管理切片实例时的管理成本和操作成本。
在一种可能的设计方式中，该描述文件中还包括北向接口信息和南向接口信息；该北向接口信息包括：对该运营商系统和客户系统的接口，以及该运营商系统和客户系统对该切片实例的管理权限；该南向接口信息包括：对该切片实例内各个网元的接口；其中，在该虚拟化管理编排节点按照该连接关系，建立该切片实例管理节点与该切片实例内各个网元之间的管理通道之后，还包括：该虚拟化管理编排节点按照该南向接口信息和该北向接口信息，为该切片实例管理节点配置南向接口和北向接口。
在一种可能的设计方式中，该切片实例管理节点部署在该切片实例内，或者，该切片实例管理节点部署在该运营商系统内，或者，该切片实例管理节点部署在该切片实例和该运营商系统之外。
第二方面，本发明的实施例提供一种切片实例管理节点的实例化方法，包括：虚拟化管理编排节点获取切片实例管理节点的描述文件，该描述文件中包括：该切片实例管理节点的软件镜像，以及该切片实例管理节点与N个网元之间的连接关系，该N个网元为该切片实例管理节点所管理的切片实例内的网元，N≥1；该虚拟化管理编排节点按照该软件镜像部署该切片实例管理节点；该虚拟化管理编排节点按照该连接关系，建立该切片实例管理节点与该N个网元之间的管理通道。
在一种可能的设计方式中，该描述文件中还包括北向接口信息和南向接口信息；该北向接口信息包括：对运营商系统和客户系统的接口，以及该运营商系统和客户系统对该切片实例的管理权限；该南向接口信息包括：对该切片实例内各个网元的接口；其中，在该虚拟化管理编排节点按照该连接关系，建立该切片实例管理节点与该N个网元之间的管理通道之后，还包括：该虚拟化管理编排节点按照该南向接口信息和该北向接口信息，为该切片实例管理节点配置南向接口和北向接口。
第三方面，本发明的实施例提供一种切片实例管理节点，该切片实例管理节点具有实现上述方法实际中切片实例管理节点行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
第四方面，本发明的实施例提供一种虚拟化管理编排节点，该虚拟化管理编排节点具有实现上述方法实际中虚拟化管理编排节点行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
第五方面，本发明的实施例提供一种切片实例管理节点，包括：处理器、存储器、总线和通信接口；该存储器用于存储计算机执行指令，该处理器与该存储器通过该总线连接，当该切片实例管理节点运行时，该处理器执行该存储器存储的该计算机执行指令，以使该切片实例管理节点行如第一方面中任意一项的切片实例的管理方法。
第六方面，本发明的实施例提供一种虚拟化管理编排节点，包括：处理器、存储器、总线和通信接口；该存储器用于存储计算机执行指令，该处理器与该存储器通过该总线连接，当该虚拟化管理编排节点运行时，该处理器执行该存储器存储的该计算机执行指令，以使该 虚拟化管理编排节点行如第二方面中任意一项的切片实例管理节点的实例化方法。
第七方面，本发明的实施例提供一种切片实例管理系统，包括切片实例管理节点和虚拟化管理编排节点。该虚拟化管理编排节点，用于：获取切片实例管理节点的描述文件，该描述文件中包括：该切片实例管理节点的软件镜像，以及该切片实例管理节点与N个网元之间的连接关系，该N个网元为该切片实例管理节点所管理的切片实例内的网元，N≥1；按照该软件镜像部署该切片实例管理节点；按照该连接关系，建立该切片实例管理节点与该N个网元之间的管理通道。该切片实例管理节点，用于：接收来自运营商系统的第一业务请求，该第一业务请求包括：该运营商系统对第一网元的管理操作信息，该第一网元为该切片实例管理节点所管理的切片实例中的网元；若该第一业务请求在第一管理权限内，则将该运营商系统对第一网元的管理操作信息发送至该第一网元，该第一管理权限为该实例管理节点的描述文件中包括的该运营商系统对该切片实例的管理权限。
第八方面，本发明实施例提供了一种计算机存储介质，用于储存为上述切片实例管理节点所用的计算机软件指令，其包含用于执行上述方面为切片实例管理节点所设计的程序。
第九方面，本发明实施例提供了一种计算机存储介质，用于储存为上述虚拟化管理编排节点所用的计算机软件指令，其包含用于执行上述方面为虚拟化管理编排节点所设计的程序。
另外，第二方面至第九方面中任一种设计方式所带来的技术效果可参见第一方面中不同设计方式所带来的技术效果，此处不再赘述。
本发明的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍。
图1为现有技术中网络切片的管理系统的架构示意图；
图2为本发明实施例提供的一种切片实例管理系统的架构示意图一；
图3为本发明实施例提供的一种切片实例管理系统的架构示意图二；
图4为本发明实施例提供的一种切片实例管理系统的架构示意图三；
图5为本发明实施例提供的一种计算机设备的结构示意图；
图6为本发明实施例提供的一种切片实例管理节点的实例化方法的流程示意图；
图7为本发明实施例提供的一种切片实例的管理方法的交互示意图；
图8为本发明实施例提供的一种切片实例管理节点的结构示意图一；
图9为本发明实施例提供的一种虚拟化管理编排节点的结构示意图一；
图10为本发明实施例提供的一种切片实例管理节点的结构示意图二；
图11为本发明实施例提供的一种虚拟化管理编排节点的结构示意图二。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。
另外，术语“第一”、“第二”仅用于描述目的，而不能理解为指示或暗示相对重要性或 者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”的特征可以明示或者隐含地包括一个或者更多个该特征。在本发明的描述中，除非另有说明，“多个”的含义是两个或两个以上。
本发明的实施例提供一种切片实例的管理方法，可应用于如图2所示的切片实例管理系统100，该切片实例管理系统100包括可互相通信的虚拟化管理编排节点25和切片实例管理节点21，其中，切片实例管理节点21可部署在任意切片实例内，并且，该切片实例管理节点21可与运营商系统22和客户系统23分别通信。
具体的，虚拟化管理编排节点25在实例化上述切片实例的同时，可以将切片实例管理节点21作为一个具有管理切片实例功能的网元部署在上述切片实例内，并且，建立切片实例管理节点21与该切片实例内的各个网元24之间的管理通道，切片实例管理节点21对运营商系统22的接口和管理权限，以及切片实例管理节点21对客户系统23的接口和管理权限，即：虚拟化管理编排节点25在实例化上述切片实例的同时，对切片实例管理节点21进行实例化操作。
这样，在实际运行上述切片实例时，当运营商系统22向切片实例内的网元24发出相应的业务请求来管理上述切片实例时，需要先通过运营商系统22与切片实例管理节点21之间的接口，将该业务请求发送至切片实例管理节点21，进而，由切片实例管理节点21对该业务请求进行鉴权，如果该业务请求在实例管理节点21实例化时为运营商系统22部署的管理权限内，则可按照该业务请求进行相应的管理操作，否则，可直接忽略该业务请求。
类似的，当客户系统23向切片实例内的网元24发出相应的业务请求来管理上述切片实例时，需要先通过客户系统23与切片实例管理节点21之间的接口，将该业务请求发送至切片实例管理节点21，进而，由切片实例管理节点21对该业务请求进行鉴权，如果该业务请求在实例管理节点21实例化时为客户系统23部署的管理权限内，则可按照该业务请求进行相应的管理操作，否则，可直接忽略该业务请求。
可以看出，在本发明的实施例提供的切片实例的管理方法中，引入切片实例管理节点21，替代传统的切片管理节点对切片实例进行管理，由于在实例化切片实例管理节点21的过程中，已经在切片实例管理节点21内配置了运营商系统22和客户系统23对切片实例的管理权限，因此，在实际运行该切片实例时，可直接按照配置好的上述管理权限对切片实例内的各个网元进行各项管理操作即可，而无需额外设置复杂的控制逻辑，来确定运营商系统22或客户系统23下发的业务请求是否合理，在保证了不同切片实例之间的隔离性的同时，降低了管理切片实例过程中的管理复杂度和负载消耗。
进一步地，切片实例管理节点21还可以具有对切片实例运行时的运行信息进行统计和上报等功能，后续实施例中将详细阐述，故此处不再赘述。
另外，在本发明实施例提供的切片实例管理系统100的另一种可能的设计方案，上述切片实例管理节点21可以部署在切片实例之外的任意位置，例如，如图3所示，上述切片实例管理节点21可以以独立的设备形态部署在切片实例外，又或者，如图4所示，上述切片实例管理节点21还可以作为一个功能单元集成在上述运营商系统22或客户系统23内，本发明实施例对此不作任何限制。
需要说明的是，在本发明实例中，上述切片实例管理系统100中所涉及的任意一种功能节点或网元，例如，切片实例管理节点21、虚拟化管理编排节点25和网元24，可能由一个 实体设备实现，也可能由多个实体设备共同实现，切片实例管理系统100中的多个功能节点可能分别由不同的实体设备实现，也可能都由同一个实体设备实现。可以理解的是，切片实例管理系统100中的任意一种功能节点都可能是实体设备内的一个逻辑功能模块，也可能是由多个实体设备组成的一个逻辑功能模块。
如图5所示，图2-图4中的虚拟化管理编排节点25和切片实例管理节点21可以以图5中的计算机设备(或系统)的方式来实现。
图5所示为本发明实施例提供的计算机设备示意图。计算机设备200包括至少一个处理器51，通信总线52，存储器53以及至少一个通信接口54。
处理器51可以是一个通用中央处理器(CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本发明方案程序执行的集成电路。
通信总线52可包括一通路，在上述组件之间传送信息。所述通信接口54，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(RAN)，无线局域网(Wireless Local Area Networks，WLAN)等。
存储器53可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、只读光盘(Compact Disc Read-Only Memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过总线与处理器相连接。存储器也可以和处理器集成在一起。
其中，所述存储器53用于存储执行本发明方案的应用程序代码，并由处理器51来控制执行。所述处理器51用于执行所述存储器53中存储的应用程序代码。
在具体实现中，作为一种实施例，处理器51可以包括一个或多个CPU，例如图5中的CPU0和CPU1。
在具体实现中，作为一种实施例，计算机设备200可以包括多个处理器，例如图5中的处理器51和处理器58。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中，作为一种实施例，计算机设备200还可以包括输出设备55和输入设备56。输出设备55和处理器51通信，可以以多种方式来显示信息。例如，输出设备55可以是液晶显示器(liquid crystal display，LCD),发光二级管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备56和处理器51通信，可以以多种方式接受用户的输入。例如，输入设备56可以是鼠标、键盘、触摸屏设备或传感设备等。
上述的计算机设备200可以是一个通用计算机设备或者是一个专用计算机设备。在具体实现中，计算机设备200可以是台式机、便携式电脑、网络服务器、掌上电脑(Personal Digital Assistant，PDA)、移动手机、平板电脑、无线终端设备、通信设备、嵌入式设备或有图5中 类似结构的设备。本发明实施例不限定计算机设备200的类型。
示例性的，图2-图4中的虚拟化管理编排节点25可以为图5所示的设备，虚拟化管理编排节点25的存储器中存储了一个或多个软件模块。虚拟化管理编排节点25可以通过处理器以及存储器中的程序代码来实现软件模块，实现切片实例管理节点21的实例化过程。
又或者，图2-4的中切片实例管理节点21可以为图5所示的设备，切片实例管理节点21的存储器中存储了一个或多个软件模块。切片实例管理节点21可以通过处理器以及存储器中的程序代码来实现软件模块，实现切片实例的管理过程。
在下述的本发明实施例中，为了更清楚地介绍本发明提供的切片实例管理节点21的实例化方法和切片实例的管理方法，下文中均以逻辑功能模块作为执行主体进行说明，本领域技术人员可以理解，逻辑功能模块在具体实现时需依赖于其所在的实体设备上的硬件资源。
另外，在本发明实施例中，上述切片实例管理系统100可以应用于未来的第五代移动通信(英文：5rd-Generation，缩写：5G)系统，长期演进(英文：long term evolution，缩写：LTE)通信系统中，也可以应用于LTE的演进通信系统中，如LTE-A(英文全称：long term evolution advanced)系统中，还可以应用于WCDMA等第三代移动通信(英文：3rd-Generation，缩写：3G)系统中等，本发明不作限制。
以下，基于图2所示的切片实例管理系统100，本发明的实施例提供一种切片实例管理节点21的实例化方法，如图6所示，该方法包括：
101、虚拟化管理编排节点获取切片实例管理节点的描述文件。
通常，在对切片实例进行实例化操作之前的设计阶段，运营商系统22会为不同的切片实例定义不同的切片蓝图(blueprint)。切片蓝图中一般设置了切片实例的相关参数信息，例如，网络拓扑信息、功能组件信息、交互协议信息、性能指标信息和/或硬件要求信息等。
而在本发明实施例中，除了在上述切片蓝图中定义上述切片实例的相关参数信息之外，还可以在上述切片蓝图中定义切片实例管理节点21与切片实例内各个网元之间的连接关系，以及切片实例管理节点21的管理权限，例如，切片实例管理节点21在网络资源层、网络功能层和/或网络控制层的业务操作的权限范围，以及收集哪些业务或网元的运行信息等。
这样，在切片实例化阶段，运营商系统22可以根据上述蓝图生成切片实例的描述文件和切片实例管理节点21的描述文件，并将这些描述文件发送给虚拟化管理编排节点25，由虚拟化管理编排节点25完成切片实例和切片实例管理节点21的实例化操作。
其中，上述切片实例的描述文件具体可以包括NFV(Network Function Virtualization，网络功能虚拟化)标准所定义的NSD(Network Service Descriptor，网络业务描述符)，VLD(Virtual Link Descriptor，虚拟链路描述符)以及VNFFGD(VNF Forwarding Graph Descriptor，虚拟网络功能转发图描述符)中的至少一项。
而上述切片实例管理节点21的描述文件中可以包括：切片实例管理节点21的软件镜像，以及切片实例管理节点21与N(N≥1)个网元之间的连接关系，这N个网元为切片实例管理节点所管理的切片实例内的网元。
上述切片实例管理节点21的描述文件是本发明实施例新增的描述文件，其中，上述切片实例管理节点21的软件镜像具体可以为：切片实例管理节点21自身的VNFD(VNF Descriptor，虚拟网络功能描述符)，而切片实例管理节点21与N个网元之间的连接关系具体可以为：切片实例管理节点21和上述N个网元之间管理通道的虚拟链路描述符。
102、虚拟化管理编排节点按照上述软件镜像部署切片实例管理节点。
103、虚拟化管理编排节点按照上述连接关系，建立切片实例管理节点与其管理的切片实例内的N个网元之间的管理通道。
与现有的切片实例的实例化过程类似的，虚拟化管理编排节点25在接收到上述切片实例的描述文件后，可进一步在虚拟化基础设施上为该切片实例分配资源，并按照上述切片实例的描述文件，部署切片实例内的各个网元，然后，根据上述切片实例的描述文件建立各个网元之间的连接，完成切片实例的实例化操作。
与现有的切片实例的实例化过程不同的是，虚拟化管理编排节点25在接收到上述切片实例管理节点21的描述文件后，可进一步在虚拟化基础设施上为切片实例管理节点21分配资源，并且，如步骤102所述，可在上述切片实例中安装上述切片实例管理节点21的软件镜像，以部署上述切片实例管理节点21；进而，如步骤103所述，按照上述切片实例管理节点21与N个网元之间的连接关系，建立切片实例管理节点21与上述N个网元之间的管理通道。
进一步地，步骤101中获取到的切片实例管理节点21的描述文件中还可以包括：南向接口信息和北向接口信息。
其中，北向接口信息包括：切片实例管理节点21分别与运营商系统22和客户系统23的接口，以及运营商系统22和客户系统23对上述切片实例的管理权限；南向接口信息包括：切片实例管理节点21与上述切片实例内各个网元的接口。
示例性的，上述北向接口信息具体可以为：切片实例管理节点21和运营商系统22之间的北向接口配置描述，以及切片实例管理节点21和客户系统23之间的北向接口配置描述，该配置描述中定义了运营商系统22和客户系统23分别对上述切片实例的管理权限。而上述南向接口信息具体可以为：切片实例管理节点21和各个网元之间的南向接口配置描述。
另外，客户系统23与切片实例管理节点21之间的北向接口中，可以包含客户定制的API(Application Programming Interface，应用程序编程接口)，这样，为不同的客户系统23提供的API并不是全局统一的，而是可以通过北向接口信息为不同的客户系统23定制不同的API，实现对切片实例的灵活管理。
此时，在执行步骤101-103之后，虚拟化管理编排节点25还可以执行下述步骤104，即：
104、虚拟化管理编排节点按照上述南向接口信息和北向接口信息，为切片实例管理节点配置南向接口和北向接口。
为切片实例管理节点21配置完南向接口和北向接口之后，切片实例管理节点21便可以通过南向接口，与切片实例内的各个网元进行通信，例如，收集各个网元在运行时的内存大小等运行信息；并且，切片实例管理节点21还可以通过北向接口分别与运营商系统和客户系统进行通信，其中，切片实例管理节点21与运营商系统之间的北向接口，与切片实例管理节点21与客户系统之间的北向接口可以相同或不同，本发明实施例对此不作任何限制。
进一步地，由于虚拟化管理编排节点25根据北向接口信息为切片实例管理节点21配置北向接口时，分别配置了运营商系统22和客户系统23对切片实例的管理权限，因此，在后续实际运行上述切片实例时，切片实例管理节点21可直接按照配置好的上述管理权限，完成运营商系统22和客户系统23对切片实例内的各个网元进行管理即可，而无需额外设置复杂的控制逻辑，来确定运营商系统22或客户系统23下发的业务请求是否合理，从而降低了管理切片实例过程中的管理复杂度和负载消耗。
另外，相比于现有技术中需要人为部署切片管理节点，并配置切片管理节点内的管理策略，以实现对各个切片实例的管理而言，在本发明实施例中，在实例化每个切片实例的过程中，便可以根据相应的描述文件自动部署得到管理该切片实例的切片实例管理节点21，后续，切片实例管理节点21可自动按照实例化过程中已配置好的管理权限管理其所在的切片实例，实现了切片实例的自动化管理过程，大大降低了管理切片实例时的管理成本和操作成本。
又或者，如果切片实例管理节点21的软件镜像中，已经为切片实例管理节点21定义了南向接口信息和北向接口信息，则在执行完成上述步骤102(即按照上述软件镜像部署切片实例管理节点21)之后，部署得到的切片实例管理节点21便已经具备了南向接口和北向接口，此时，无需执行上述步骤104。
至此，虚拟化管理编排节点25在部署切片实例的过程中，同时在该切片实例内部署了切片实例管理节点21，完成了对切片实例管理节点21的实例化操作。
其中，上述步骤101-104中虚拟化管理编排节点25的动作，可以由虚拟化管理编排节点25根据图5中提及的存储器中的相应软件模块来执行，本发明实施例对此不作任何限制。
进一步地，基于图2所示的切片实例管理系统100，在实例化上述切片实例管理节点21之后，便可以由切片实例管理节点21对其所在的切片实例进行管理。
具体的，如图7所示，为本发明的实施例提供一种切片实例的管理方法，该方法包括：
201、切片实例管理节点21接收来自运营商系统22的第一业务请求，该第一业务请求包括：运营商系统22对第一网元的管理操作信息。
其中，该第一网元为切片实例管理节点21所管理的切片实例中的网元，以图2中所示的切片实例管理系统100为例，切片实例管理节点21所管理的切片实例即为：切片实例管理节点21所部署的切片实例，即步骤101-104中，与切片实例管理节点21同时进行实例化操作后得到的切片实例。
具体的，当运营商系统22需要对某个切片实例，例如，切片实例1内的第一网元进行相应的管理时，可以向管理切片实例1的切片实例管理节点21发送第一业务请求，例如，该第一业务请求具体可以为请求对第一网元进行扩容操作。
此时，第一业务请求中包括运营商系统22对第一网元的管理操作信息，即执行该第一业务请求的具体操作内容，例如，对第一网元进行扩容操作时的具体扩容策略。
示例性的，运营商系统22可以通过步骤104中实例化上述切片实例管理节点21时定义的南向接口，向切片实例管理节点21发送该第一业务请求。
202、若第一业务请求在第一管理权限内，则实例管理节点21将运营商系统22对第一网元的管理操作信息发送至第一网元。
其中，第一管理权限为实例管理节点21的描述文件中包括的：运营商系统22对切片实例的管理权限。
在执行步骤104时，已经通过南向接口信息配置了运营商系统22对切片实例管理节点21的管理权限，该管理权限包括上述第一管理权限，例如，该第一管理权限具体可以为：允许运营商系统22对网元1和网元2进行扩容操作以及缩容操作，当进行扩容操作时，允许进行扩容的大小为100G(其中，1G＝1024MB，1MB＝1024KB，1KB＝1024字节)以内。
那么，在步骤202中，若上述第一业务请求在第一管理权限内，则实例管理节点21将第一业务请求中上述运营商系统22对第一网元的管理操作信息发送至第一网元，由第一网元按 照该管理操作信息执行相应的操作内容，例如，按照上述扩容策略进行扩容。
需要说明的是，由于实例管理节点21和运营商系统22之间的北向接口，与实例管理节点21和第一网元之间的南向接口可能不相同，因此，实例管理节点21和运营商系统22通信时使用的协议，与实例管理节点21和第一网元通信时使用的协议可能不相同，此时，实例管理节点21需要对接收到的第一业务请求进行相应的解析和转换，将第一业务请求中的上述运营商系统22对第一网元的管理操作信息转换为第一网元可以识别的格式发送至第一网元。
可选的，如下述步骤203-204所示，切片实例管理节点21还可以客户系统23发送的业务请求(即第二业务请求)，对切片实例进行管理操作。
需要说明的是，本发明实施例并不限定步骤203-204与步骤201-202之间的逻辑关系，即步骤203-204可以在执行步骤201-202之后或之前执行，或者，切片实例管理节点21还可以同时执行步骤203-204和步骤201-202。
203、切片实例管理节点21接收来自客户系统23的第二业务请求，该第二业务请求包括：客户系统23对第一网元的管理操作信息。
204、若第二业务请求在第二管理权限内，则实例管理节点21将客户系统23对第一网元的管理操作信息发送至第一网元。
与步骤201类似的，当客户系统23需要对某个切片实例，例如切片实例1内的第一网元进行相应的管理时，可以向管理切片实例1的切片实例管理节点21发送第二业务请求，该第二业务请求可以与上述第一业务请求可以相同或不同。
类似的，第二业务请求中包括客户系统23对第一网元的管理操作信息，该客户系统23对第一网元的管理操作信息与运营商系统22对第一网元的管理操作信息可以相同或不同。
并且，在执行步骤104时，也同样通过南向接口信息配置了客户系统23对切片实例管理节点21的管理权限，该管理权限中包括了上述第二管理权限。
那么，在步骤204中，若上述第二业务请求在第二管理权限内，则实例管理节点21将第二业务请求中客户系统23对第一网元的管理操作信息发送至第一网元，由第一网元按照该管理操作信息执行相应的操作内容即可。
可选的，如下述步骤205-206b所示，切片实例管理节点21还为运营商系统22和/或客户系统23获取其所需的切片实例内相关网元的运行信息。类似的，本发明实施例并不限定步骤205-206b、步骤203-204以及步骤201-202之间的逻辑关系。
205、切片实例管理节点21按照第三管理权限，获取第一网元的运行信息。
其中，该第三管理权限为描述文件中包括的：允许切片实例管理节点21获取的运营商系统22和客户系统23需要的运行信息。
也就是说，在实例化上述切片实例管理节点21时，可以预先在描述文件中定义切片实例管理节点21可以获取哪些网元的哪些运行信息，这些运行信息包括了运营商系统22和客户系统23分别需要的运行信息，例如，运营商系统22需要获知第一网元在运行过程中的CPU占用率和内存占用率，而客户系统23需要获知第一网元在运行过程中的内存占用率，那么，按照上述描述文件实例化切片实例管理节点21之后，切片实例管理节点21便具有获取上述运行信息的第三管理权限，进而，在切片实例运行阶段，切片实例管理节点21可以按照上述第三管理权限，通过南向接口获取切片实例内第一网元的相关运行信息。
206a、切片实例管理节点21按照第四管理权限，将运行信息中运营商系统22需要的运 行信息发送至运营商系统22。
其中，第四管理权限为描述文件中包括的：允许切片实例管理节点21上报至运营商系统22的运行信息。
具体的，在执行步骤104时，已经通过南向接口信息配置了运营商系统22对切片实例管理节点21的管理权限，该管理权限包括了上述第四管理权限，例如，该第四管理权限具体可以为：允许运营商系统22获取第一网元在运行过程中的CPU占用率和内存占用率。
那么，在步骤206a中，切片实例管理节点21可以直接按照第四管理权限，将步骤205中获取到的运行信息中运营商系统22需要的运行信息发送至运营商系统22。
206b、切片实例管理节点21按照第五管理权限，将运行信息中客户系统23需要的运行信息发送至客户系统23。
其中，第五管理权限为描述文件中包括的：允许切片实例管理节点21上报至客户系统23的运行信息。
类似的，在执行步骤104时，已经通过南向接口信息配置了客户系统23对切片实例管理节点21的管理权限，该管理权限包括了上述第五管理权限，例如，该第五管理权限具体可以为：允许客户系统23获取第一网元在运行过程中内存占用率。
那么，在步骤206b中，切片实例管理节点21可以直接按照第五管理权限，将步骤205中获取到的运行信息中客户系统23需要的运行信息发送至客户系统23。
后续，运营商系统22和客户系统23可以根据获取到的运行信息，确定上述切片实例的运行状态，进而对上述切片实例进行相应的管理操作，例如，运营商系统22向切片实例管理节点21下发如步骤201中所述的第一业务请求，客户系统23向切片实例管理节点21下发如步骤203中所述的第二业务请求，以保障切片实例内的各项业务正常运行。
可以理解的是，上述实施例中仅以切片实例管理节点21管理第一网元为例进行说明，而切片实例管理节点21对切片实例内其他网元的管理方法，与切片实例管理节点21管理第一网元的方法类似，故此处不再赘述。
另外，上述步骤201-206b中切片实例管理节点21的动作，可以由切片实例管理节点21根据图5中提及的存储器中的相应软件模块来执行，本发明实施例对此不作任何限制。
至此，本发明的实施例提供一种切片实例的管理方法，引入了切片实例管理节点，替代传统的切片管理节点对切片实例进行管理，由于在实例化切片实例管理节点的过程中，在切片实例管理节点内已经配置了运营商系统和客户系统对切片实例的管理权限，因此，在运行切片实例时，切片实例管理节点可直接按照配置好的上述管理权限对切片实例内的各个网元进行管理即可，而无需额外设置复杂的控制逻辑，来确定运营商系统或客户系统下发的业务请求是否合理，在保证不同切片实例之间的隔离性的同时，降低了管理切片实例过程中的管理复杂度和负载消耗。
上述主要从各个网元之间交互的角度对本发明实施例提供的方案进行了介绍。可以理解的是，虚拟化管理编排节点25和切片实例管理节点21等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现 所描述的功能，但是这种实现不应认为超出本发明的范围。
本发明实施例可以根据上述方法示例对虚拟化管理编排节点25和切片实例管理节点21等进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本发明实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下，图8示出了上述实施例中所涉及的切片实例管理节点21的一种可能的结构示意图，该切片实例管理节点21可以为图2-图4中所示的切片实例管理节点21的一种可能的设计方案。
具体的，该切片实例管理节点21包括：获取模块31，确定模块32，发送模块33。
获取模块31，用于接收来自运营商系统的第一业务请求，所述第一业务请求包括：所述运营商系统对第一网元的管理操作信息，所述第一网元为所述切片实例管理节点所管理的切片实例中的网元；
确定模块32，用于确定所述第一业务请求是否在第一管理权限内，所述第一管理权限为所述实例管理节点的描述文件中包括的所述运营商系统对所述切片实例的管理权限；
发送模块33，用于若所述第一业务请求在第一管理权限内，则将所述运营商系统对第一网元的管理操作信息发送至所述第一网元。
进一步地，所述获取模块31，还用于接收来自客户系统的第二业务请求，所述第二业务请求包括：所述客户系统对所述第一网元的管理操作信息；
所述确定模块32，还用于确定所述第二业务请求是否在第二管理权限内，所述第二管理权限为所述描述文件中包括的所述客户系统对所述切片实例的管理权限；
所述发送模块33，还用于若所述第二业务请求在第二管理权限内，则将所述客户系统对所述第一网元的管理操作信息发送至所述第一网元。
进一步地，所述获取模块31，还用于按照第三管理权限，获取所述第一网元的运行信息，所述第三管理权限为所述描述文件中包括的允许所述切片实例管理节点获取的所述运营商系统和客户系统需要的运行信息；
所述发送模块33，还用于按照第四管理权限，将所述运行信息中所述运营商系统需要的运行信息发送至所述运营商系统，所述第四管理权限为所述描述文件中包括的允许所述切片实例管理节点上报至所述运营商系统的运行信息。
进一步地，所述发送模块33，还用于按照第五管理权限，将所述运行信息中所述客户系统需要的运行信息发送至所述客户系统，所述第五管理权限为所述描述文件中包括的允许所述切片实例管理节点上报至所述客户系统的运行信息。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在采用对应各个功能划分各个功能模块的情况下，图9示出了上述实施例中所涉及的虚拟化管理编排节点25的一种可能的结构示意图，该切片实例管理节点21可以为图2-图4中所示的切片实例管理节点21的一种可能的设计方案。
具体的，该虚拟化管理编排节点25包括：获取模块41，部署模块42，和建立模块43。
获取模块41，用于获取切片实例管理节点的描述文件，所述描述文件中包括：所述切片 实例管理节点的软件镜像，以及所述切片实例管理节点与N个网元之间的连接关系，所述N个网元为所述切片实例管理节点所管理的切片实例内的网元，N≥1；
部署模块42，用于按照所述软件镜像部署所述切片实例管理节点；
建立模块43，用于按照所述连接关系，建立所述切片实例管理节点与所述N个网元之间的管理通道。
进一步地，仍如图9所示，该虚拟化管理编排节点25还可以包括：
配置模块44，用于按照南向接口信息和所述北向接口信息，为所述切片实例管理节点配置南向接口和北向接口。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在采用集成的单元的情况下，图10示出了上述实施例中所涉及的切片实例管理节点21的一种可能的结构示意图。切片实例管理节点21包括：处理模块1002和通信模块1003。处理模块1002用于对切片实例管理节点21的动作进行控制管理，例如，处理模块1002用于支持切片实例管理节点21执行图7中的过程201-206b，和/或用于本文所描述的技术的其它过程。通信模块1003用于支持切片实例管理节点21与其他网络实体的通信，例如与图2-图4中示出的功能模块或网络实体之间的通信。切片实例管理节点21还可以包括存储模块1001，用于存储切片实例管理节点21的程序代码和数据。
类似的，在采用集成的单元的情况下，图11示出了上述实施例中所涉及的虚拟化管理编排节点25的一种可能的结构示意图。虚拟化管理编排节点25包括：处理模块1102和通信模块1103。处理模块1102用于对虚拟化管理编排节点25的动作进行控制管理，例如，处理模块1102用于支持虚拟化管理编排节点25执行图6中的过程101-104，和/或用于本文所描述的技术的其它过程。通信模块1103用于支持虚拟化管理编排节点25与其他网络实体的通信，例如与图2-图4中示出的功能模块或网络实体之间的通信。虚拟化管理编排节点25还可以包括存储模块1101，用于存储虚拟化管理编排节点25的程序代码和数据。
其中，处理模块1002/1102可以是处理器或控制器，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块1003/1103可以是收发器、收发电路或通信接口等。存储模块1001/1101可以是存储器。
当处理模块1002/1102为处理器，通信模块1003/1103为通信接口，存储模块1001/1101为存储器时，本发明实施例所涉及的切片实例管理节点21或虚拟化管理编排节点25可以为图5所示的计算机设备200。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传 送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本发明的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明的具体实施方式而已，并不用于限定本发明的保护范围，凡在本发明的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明的保护范围之内。

Claims (19)

  1. 一种切片实例的管理方法，其特征在于，包括：
    切片实例管理节点接收来自运营商系统的第一业务请求，所述第一业务请求包括：所述运营商系统对第一网元的管理操作信息，所述第一网元为所述切片实例管理节点所管理的切片实例中的网元；
    若所述第一业务请求在第一管理权限内，则所述实例管理节点将所述运营商系统对第一网元的管理操作信息发送至所述第一网元，所述第一管理权限为所述实例管理节点的描述文件中包括的所述运营商系统对所述切片实例的管理权限。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述切片实例管理节点接收来自客户系统的第二业务请求，所述第二业务请求包括：所述客户系统对所述第一网元的管理操作信息；
    若所述第二业务请求在第二管理权限内，则所述实例管理节点将所述客户系统对所述第一网元的管理操作信息发送至所述第一网元，所述第二管理权限为所述描述文件中包括的所述客户系统对所述切片实例的管理权限。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述切片实例管理节点按照第三管理权限，获取所述第一网元的运行信息，所述第三管理权限为所述描述文件中包括的允许所述切片实例管理节点获取的所述运营商系统和客户系统需要的运行信息；
    所述切片实例管理节点按照第四管理权限，将所述运行信息中所述运营商系统需要的运行信息发送至所述运营商系统，所述第四管理权限为所述描述文件中包括的允许所述切片实例管理节点上报至所述运营商系统的运行信息。
  4. 根据权利要求3所述的方法，其特征在于，在所述切片实例管理节点按照第三管理权限，获取所述第一网元的运行信息之后，还包括：
    所述切片实例管理节点按照第五管理权限，将所述运行信息中所述客户系统需要的运行信息发送至所述客户系统，所述第五管理权限为所述描述文件中包括的允许所述切片实例管理节点上报至所述客户系统的运行信息。
  5. 根据权利要求1-4中任一项所述的方法，其特征在于，在切片实例管理节点接收来自运营商系统的第一业务请求之前，还包括：
    虚拟化管理编排节点获取所述切片实例管理节点的描述文件，所述描述文件中包括所述切片实例管理节点的软件镜像，以及所述切片实例管理节点与所述切片实例内N个网元之间的连接关系，N≥1；
    所述虚拟化管理编排节点按照所述软件镜像部署所述切片实例管理节点；
    所述虚拟化管理编排节点按照所述连接关系，建立所述切片实例管理节点与所述N个网元之间的管理通道。
  6. 根据权利要求5所述的方法，其特征在于，所述描述文件中还包括北向接口信息和南向接口信息；所述北向接口信息包括：对所述运营商系统和客户系统的接口，以及所述运营商系统和客户系统对所述切片实例的管理权限；所述南向接口信息包括：对所述切片实例内各个网元的接口；
    其中，在所述虚拟化管理编排节点按照所述连接关系，建立所述切片实例管理节点与所 述切片实例内各个网元之间的管理通道之后，还包括：
    所述虚拟化管理编排节点按照所述南向接口信息和所述北向接口信息，为所述切片实例管理节点配置南向接口和北向接口。
  7. 根据权利要求1-6中任一项所述的方法，其特征在于，
    所述切片实例管理节点部署在所述切片实例内，或者，
    所述切片实例管理节点部署在所述运营商系统内，或者，
    所述切片实例管理节点部署在所述切片实例和所述运营商系统之外。
  8. 一种切片实例管理节点的实例化方法，其特征在于，包括：
    虚拟化管理编排节点获取切片实例管理节点的描述文件，所述描述文件中包括：所述切片实例管理节点的软件镜像，以及所述切片实例管理节点与N个网元之间的连接关系，所述N个网元为所述切片实例管理节点所管理的切片实例内的网元，N≥1；
    所述虚拟化管理编排节点按照所述软件镜像部署所述切片实例管理节点；
    所述虚拟化管理编排节点按照所述连接关系，建立所述切片实例管理节点与所述N个网元之间的管理通道。
  9. 根据权利要求8所述的方法，其特征在于，所述描述文件中还包括北向接口信息和南向接口信息；所述北向接口信息包括：对运营商系统和客户系统的接口，以及所述运营商系统和客户系统对所述切片实例的管理权限；所述南向接口信息包括：对所述切片实例内各个网元的接口；
    其中，在所述虚拟化管理编排节点按照所述连接关系，建立所述切片实例管理节点与所述N个网元之间的管理通道之后，还包括：
    所述虚拟化管理编排节点按照所述南向接口信息和所述北向接口信息，为所述切片实例管理节点配置南向接口和北向接口。
  10. 一种切片实例管理节点，其特征在于，包括：
    获取模块，用于接收来自运营商系统的第一业务请求，所述第一业务请求包括：所述运营商系统对第一网元的管理操作信息，所述第一网元为所述切片实例管理节点所管理的切片实例中的网元；
    确定模块，用于确定所述第一业务请求是否在第一管理权限内，所述第一管理权限为所述实例管理节点的描述文件中包括的所述运营商系统对所述切片实例的管理权限；
    发送模块，用于若所述第一业务请求在第一管理权限内，则将所述运营商系统对第一网元的管理操作信息发送至所述第一网元。
  11. 根据权利要求10所述的切片实例管理节点，其特征在于，
    所述获取模块，还用于接收来自客户系统的第二业务请求，所述第二业务请求包括：所述客户系统对所述第一网元的管理操作信息；
    所述确定模块，还用于确定所述第二业务请求是否在第二管理权限内，所述第二管理权限为所述描述文件中包括的所述客户系统对所述切片实例的管理权限；
    所述发送模块，还用于若所述第二业务请求在第二管理权限内，则所述实例管理节点将所述客户系统对所述第一网元的管理操作信息发送至所述第一网元。
  12. 根据权利要求10或11所述的切片实例管理节点，其特征在于，
    所述获取模块，还用于按照第三管理权限，获取所述第一网元的运行信息，所述第三管理权限为所述描述文件中包括的允许所述切片实例管理节点获取的所述运营商系统和客户系 统需要的运行信息；
    所述发送模块，还用于按照第四管理权限，将所述运行信息中所述运营商系统需要的运行信息发送至所述运营商系统，所述第四管理权限为所述描述文件中包括的允许所述切片实例管理节点上报至所述运营商系统的运行信息。
  13. 根据权利要求12所述的切片实例管理节点，其特征在于，
    所述发送模块，还用于按照第五管理权限，将所述运行信息中所述客户系统需要的运行信息发送至所述客户系统，所述第五管理权限为所述描述文件中包括的允许所述切片实例管理节点上报至所述客户系统的运行信息。
  14. 一种虚拟化管理编排节点，其特征在于，包括：
    获取模块，用于获取切片实例管理节点的描述文件，所述描述文件中包括：所述切片实例管理节点的软件镜像，以及所述切片实例管理节点与N个网元之间的连接关系，所述N个网元为所述切片实例管理节点所管理的切片实例内的网元，N≥1；
    部署模块，用于按照所述软件镜像部署所述切片实例管理节点；
    建立模块，用于按照所述连接关系，建立所述切片实例管理节点与所述N个网元之间的管理通道。
  15. 根据权利要求14所述的虚拟化管理编排节点，其特征在于，所述描述文件中还包括北向接口信息和南向接口信息；所述北向接口信息包括：对运营商系统和客户系统的接口，以及所述运营商系统和客户系统对所述切片实例的管理权限；所述南向接口信息包括：对所述切片实例内各个网元的接口；
    其中，所述虚拟化管理编排节点还包括：
    配置模块，用于按照所述南向接口信息和所述北向接口信息，为所述切片实例管理节点配置南向接口和北向接口。
  16. 一种切片实例管理节点，其特征在于，包括：处理器、存储器、总线和通信接口；
    所述存储器用于存储计算机执行指令，所述处理器与所述存储器通过所述总线连接，当所述切片实例管理节点运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述切片实例管理节点行如权利要求1-7中任意一项所述的切片实例的管理方法。
  17. 一种虚拟化管理编排节点，其特征在于，包括：处理器、存储器、总线和通信接口；
    所述存储器用于存储计算机执行指令，所述处理器与所述存储器通过所述总线连接，当所述虚拟化管理编排节点运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述虚拟化管理编排节点行如权利要求8或9所述的切片实例管理节点的实例化方法。
  18. 一种切片实例的管理方法，其特征在于，包括：
    切片实例管理节点接收来自客户系统的第二业务请求，所述第二业务请求包括：所述客户系统对第一网元的管理操作信息，所述第一网元为所述切片实例管理节点所管理的切片实例中的网元；
    若所述第二业务请求在第二管理权限内，则所述实例管理节点将所述客户系统对所述第一网元的管理操作信息发送至所述第一网元，所述第二管理权限为描述文件中包括的所述客户系统对所述切片实例的管理权限。
  19. 一种切片实例管理节点，其特征在于，包括：
    获取模块，接收来自客户系统的第二业务请求，所述第二业务请求包括：所述客户系统对第一网元的管理操作信息，所述第一网元为切片实例管理节点所管理的切片实例中的网元；
    确定模块，用于确定所述第二业务请求是否在第二管理权限内，所述第二管理权限为所述实例管理节点的描述文件中包括的所述客户系统对所述切片实例的管理权限；
    发送模块，用于若所述第二业务请求在第二管理权限内，则所述实例管理节点将所述客户系统对所述第一网元的管理操作信息发送至所述第一网元。
PCT/CN2017/104408 2016-10-18 2017-09-29 一种切片实例的管理方法及装置 Ceased WO2018072612A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP17862941.6A EP3503472B1 (en) 2016-10-18 2017-09-29 Method for managing slice instance and apparatus
US16/385,419 US10819592B2 (en) 2016-10-18 2019-04-16 Slice instance management method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610908985.7A CN107959582B (zh) 2016-10-18 2016-10-18 一种切片实例的管理方法及装置
CN201610908985.7 2016-10-18

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/385,419 Continuation US10819592B2 (en) 2016-10-18 2019-04-16 Slice instance management method and apparatus

Publications (1)

Publication Number Publication Date
WO2018072612A1 true WO2018072612A1 (zh) 2018-04-26

Family

ID=61954278

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/104408 Ceased WO2018072612A1 (zh) 2016-10-18 2017-09-29 一种切片实例的管理方法及装置

Country Status (4)

Country Link
US (1) US10819592B2 (zh)
EP (1) EP3503472B1 (zh)
CN (1) CN107959582B (zh)
WO (1) WO2018072612A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021022966A1 (zh) * 2019-08-08 2021-02-11 华为技术有限公司 一种管理数据的获取方法及装置
US11265210B2 (en) * 2017-03-24 2022-03-01 Huawei Technologies Co., Ltd. Network slice configuration method, apparatus, and system
US12621204B2 (en) 2019-08-08 2026-05-05 Huawei Technologies Co., Ltd. Method and apparatus for obtaining management data

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11010352B2 (en) 2017-01-23 2021-05-18 Hysolate Ltd. Unified file system on air-gapped endpoints
US11150936B2 (en) * 2017-01-23 2021-10-19 Hysolate Ltd. Techniques for binding user identities to appropriate virtual machines with single sign-on
US10699003B2 (en) 2017-01-23 2020-06-30 Hysolate Ltd. Virtual air-gapped endpoint, and methods thereof
US11153322B2 (en) * 2017-01-23 2021-10-19 Hysolate Ltd. Techniques for seamlessly launching applications in appropriate virtual machines
CN114174999B (zh) 2019-07-23 2026-03-20 华为技术有限公司 存储系统中实现存储业务连续性的方法、前端接口卡和存储系统
CN113031536B (zh) * 2019-12-24 2022-07-05 大唐高鸿信息通信研究院（义乌）有限公司 一种基于5g架构的柔性制造产品加工系统
CN114691547B (zh) * 2019-12-31 2023-05-12 华为云计算技术有限公司 部署实例的方法、实例管理节点、计算节点和计算设备
CN111897543B (zh) * 2020-01-16 2024-12-17 中兴通讯股份有限公司 一种软件管理方法、装置、管理设备及存储介质
US12615609B2 (en) 2020-05-25 2026-04-28 Qualcomm Incorporated Network slicing traffic descriptor encoding
CN113766532B (zh) * 2020-06-03 2023-08-18 中国移动通信集团浙江有限公司 网络切片实例的隔离评估方法及装置
CN116032759B (zh) * 2021-10-22 2025-08-26 中移（杭州）信息技术有限公司 一种用于切片管理的方法、装置、存储介质和网络设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140086177A1 (en) * 2012-09-27 2014-03-27 Interdigital Patent Holding, Inc. End-to-end architecture, api framework, discovery, and access in a virtualized network
CN103905523A (zh) * 2013-12-23 2014-07-02 浪潮(北京)电子信息产业有限公司 一种基于sdn的云计算网络虚拟化实现方法及系统
CN104363159A (zh) * 2014-07-02 2015-02-18 北京邮电大学 一种基于软件定义网络的开放虚拟网络构建系统和方法
CN105634782A (zh) * 2014-11-06 2016-06-01 华为技术有限公司 一种实例化vnf的方法及网元管理设备
CN105900518A (zh) * 2013-08-27 2016-08-24 华为技术有限公司 用于移动网络功能虚拟化的系统及方法

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101268440B1 (ko) 2011-10-31 2013-06-04 한국과학기술정보연구원 글로벌 네트워크 슬라이스 관리 시스템 및 그 방법
JP5788294B2 (ja) 2011-11-08 2015-09-30 株式会社日立製作所 ネットワークシステムの管理方法
US9515875B2 (en) * 2014-03-14 2016-12-06 Cisco Technology, Inc. Zero touch deployment of multi-tenant services in a home network environment
US20150358399A1 (en) * 2014-06-09 2015-12-10 Cisco Technology, Inc. Provisioning and managing slices of a consumer premises equipment device
US10284495B2 (en) * 2015-03-20 2019-05-07 Ntt Docomo, Inc. Slice management system and slice management method for dynamically adjusting resources allocated to a slice based on a resource utilization status
WO2017218849A1 (en) * 2016-06-15 2017-12-21 Convida Wireless, Llc Network slice discovery and selection

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140086177A1 (en) * 2012-09-27 2014-03-27 Interdigital Patent Holding, Inc. End-to-end architecture, api framework, discovery, and access in a virtualized network
CN105900518A (zh) * 2013-08-27 2016-08-24 华为技术有限公司 用于移动网络功能虚拟化的系统及方法
CN103905523A (zh) * 2013-12-23 2014-07-02 浪潮(北京)电子信息产业有限公司 一种基于sdn的云计算网络虚拟化实现方法及系统
CN104363159A (zh) * 2014-07-02 2015-02-18 北京邮电大学 一种基于软件定义网络的开放虚拟网络构建系统和方法
CN105634782A (zh) * 2014-11-06 2016-06-01 华为技术有限公司 一种实例化vnf的方法及网元管理设备

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11265210B2 (en) * 2017-03-24 2022-03-01 Huawei Technologies Co., Ltd. Network slice configuration method, apparatus, and system
US20220150116A1 (en) * 2017-03-24 2022-05-12 Huawei Technologies Co., Ltd. Network slice configuration method, apparatus, and system
US11750453B2 (en) 2017-03-24 2023-09-05 Huawei Technologies Co., Ltd. Network slice configuration method, apparatus, and system
US12113667B2 (en) 2017-03-24 2024-10-08 Huawei Technologies Co., Ltd. Network slice configuration method, apparatus, and system
WO2021022966A1 (zh) * 2019-08-08 2021-02-11 华为技术有限公司 一种管理数据的获取方法及装置
US12621204B2 (en) 2019-08-08 2026-05-05 Huawei Technologies Co., Ltd. Method and apparatus for obtaining management data

Also Published As

Publication number Publication date
EP3503472A1 (en) 2019-06-26
CN107959582B (zh) 2020-12-01
EP3503472A4 (en) 2019-06-26
US20190245758A1 (en) 2019-08-08
CN107959582A (zh) 2018-04-24
US10819592B2 (en) 2020-10-27
EP3503472B1 (en) 2020-02-05

Similar Documents

Publication Publication Date Title
WO2018072612A1 (zh) 一种切片实例的管理方法及装置
US12294585B2 (en) Techniques for automatically configuring minimal cloud service access rights for container applications
US11429408B2 (en) System and method for network function virtualization resource management
JP7105930B2 (ja) 警報方法および警報装置
US11937103B1 (en) Enhancing availability of radio-based applications using multiple compute instances and virtualized network function accelerators at cloud edge locations
WO2018024059A1 (zh) 一种虚拟化网络中业务部署的方法和装置
US20230412507A1 (en) Enabling isolated virtual network configuration options for network function accelerators
WO2019179453A1 (zh) 虚拟机创建方法及装置
WO2017107018A1 (zh) 应用拓扑关系发现的方法、装置和系统
US12307283B2 (en) Managing network function accelerators for radio-based applications from virtualized computing service control plane
EP3584998A1 (en) Method for virtual machine capacity expansion and reduction and virtual management device
JP2024508473A (ja) コンテナフレームワークのネットワークポリシーを検証するための技術
JP2019149187A (ja) ローカルまたは分散型コンピュータ・システムにおける柔軟なノード構成方法およびシステム
EP3567803A1 (en) Strategy management method, device, and system
WO2017066931A1 (zh) 网络功能虚拟化架构中证书的管理方法及装置
US20140359127A1 (en) Zero touch deployment of private cloud infrastructure
CN111443985A (zh) 实例化虚拟网络功能的方法及设备
CN109799998A (zh) OpenStack集群配置及批量部署方法及系统
CN111327447A (zh) 一种分布式系统、仲裁方法、节点设备及存储介质
US12581392B2 (en) Access control in a RAN
CN109905258B (zh) PaaS的管理方法、装置及存储介质
WO2017070963A1 (zh) 一种虚拟资源的部署方法、装置及系统
WO2016192011A1 (zh) 一种拥塞控制的方法及网元设备
US20220179712A1 (en) System and method for unified infrastructure architecture
KR20250012640A (ko) 가상화된 컴퓨팅 서비스 제어 평면으로부터 라디오-기반 애플리케이션들에 대한 네트워크 기능 가속기들 관리

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017862941

Country of ref document: EP

Effective date: 20190319

NENP Non-entry into the national phase

Ref country code: DE