WO2019062836A1 - 网络切片管理方法及其装置 - Google Patents

网络切片管理方法及其装置 Download PDF

Info

Publication number
WO2019062836A1
WO2019062836A1 PCT/CN2018/108264 CN2018108264W WO2019062836A1 WO 2019062836 A1 WO2019062836 A1 WO 2019062836A1 CN 2018108264 W CN2018108264 W CN 2018108264W WO 2019062836 A1 WO2019062836 A1 WO 2019062836A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
network slice
slice subnet
information
subnet
Prior art date
Application number
PCT/CN2018/108264
Other languages
English (en)
French (fr)
Inventor
方海鹏
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to JP2020518532A priority Critical patent/JP7012836B2/ja
Priority to EP18860691.7A priority patent/EP3684010B1/en
Publication of WO2019062836A1 publication Critical patent/WO2019062836A1/zh
Priority to US16/832,716 priority patent/US10958525B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/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/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
    • H04L41/0843—Configuration by using pre-existing information, e.g. using templates or copying from other elements based on generic templates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • 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/12—Discovery or management of network topologies
    • H04L41/122—Discovery or management of network topologies of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
    • 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/14—Network analysis or design
    • H04L41/145—Network analysis or design involving simulating, designing, planning or modelling of a network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • 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
    • H04L41/5048—Automatic or semi-automatic definitions, e.g. definition templates
    • 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
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • 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
    • H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
    • 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/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H04L41/0897—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities

Definitions

  • the embodiment of the present invention relates to the field of communications technologies, and in particular, to a network slice management method and device thereof.
  • the fifth generation mobile communication (the 5th-generation, 5G) system introduces network slice (NS).
  • NS network slice
  • Network slicing refers to the customization of different logical networks based on different service requirements on a physical or virtual network infrastructure.
  • the network slice can be a complete end-to-end network including terminal equipment, access network, transmission network, core network and application server, which can provide complete communication services and have certain network capabilities.
  • the network slice can also be any combination of a terminal device, an access network, a transport network, a core network, and an application server.
  • a network slice instance is a real-world logical network that can meet certain network characteristics or service requirements.
  • the network slice instance can be instantiated by a network slice template (NST).
  • NST network slice template
  • a complete network sharding instance can provide complete end-to-end network services.
  • the network sharding instance can include several network slice subnet instances (NSSIs) and/or several network functions (NF). .
  • NSST network slice subnet template
  • the process of network slice management is: the communication service management function (CSMF) receives the customer's business requirements, converts the service requirements into network slice requirements, and sends the network slice requirements to the network slice management function (network slice management function, NSMF); NSMF converts received network slice requirements into network slice subnet requirements and sends network slice subnet requirements to network slice subnet management function (NSSMF); NSSMF slices network subnets
  • CSMF communication service management function
  • the technical problem to be solved by the embodiments of the present application is to provide a network slice management method and a device thereof, and use the network slice template to decompose the network slice requirement information, thereby implementing automatic management of the network slice.
  • a first aspect of the embodiments of the present application provides a network slice management method, including:
  • the network slice management function entity receives the network slice instantiation request, where the network slice instantiation request includes network slice requirement information, and the network slice requirement information includes a network slice template identifier or a network slice type, and network slice deployment requirement information;
  • the network slice management function entity obtains the network slice template according to the network slice template identifier or the network slice type information.
  • the network slice management function entity decomposes the network slice requirement information into the network slice subnet requirement information of the network slice subnet included in the network slice template and the transmission network requirement information in the network slice according to the network slice template;
  • the network slice management function entity For each network slice subnet included in the network slice, the network slice management function entity sends a network slice subnet instantiation request to the network slice subnet management function entity, and the network slice subnet instantiation request includes network slice subnet requirement information;
  • the network slice management function entity receives the network slice subnet instantiation response sent by the network slice subnet management function entity, and the network slice subnet instantiation response includes network slice subnet instantiation information, where the network slice subnet instantiation information includes the network The identifier of the sliced subnet instance, the service access point instantiation information of the network sliced subnet instance, and the network connection point instantiation information of the network sliced subnet instance;
  • the network slice management function entity sends a transport network instantiation request to the transport network manager, where the transport network instantiation request includes transport network requirement information in the network slice and network connection point information of all network sliced subnet instances;
  • the network slice management function entity triggers establishment of a service connection of each network slice subnet instance according to the service access point information obtained after the network slice subnet is instantiated.
  • the embodiment of the present application provides a network slice management function entity, including a unit or a means for performing the foregoing steps of the first aspect.
  • an embodiment of the present application provides a network slice management function entity, including at least one processing element and at least one storage element, wherein at least one storage element is used to store a program and data, and at least one processing element is used to execute the application.
  • the method provided in one aspect is not limited to.
  • an embodiment of the present application provides a network slice management function entity, including at least one processing element (or chip) for performing the method of the above first aspect.
  • an embodiment of the present application provides a program, when executed by a processor, for performing the method of the above first aspect.
  • an embodiment of the present application provides a program product, such as a computer readable storage medium, including the program of the fifth aspect.
  • the network slice request template is used to decompose the network slice requirement information, thereby realizing automatic management of the network slice.
  • the network slice template includes an identifier of the network slice subnet template, a network connection point descriptor of the network slice subnet node, a service access point descriptor of the network slice subnet node, and a network slice subnet.
  • the network connection point descriptor of the network slice subnet node is used to describe the network connection point information of the network slice subnet node
  • the service access point descriptor of the network slice subnet node is used to describe the service connection of the network slice subnet node.
  • the network connection point descriptor of the network slice subnet node is used to describe the network connection point information of the network slice subnet node
  • the network connection descriptor between the network slice subnet nodes is used to describe the network slice subnet node
  • the network connection information between the network slice subnet nodes is used to describe the service connection information between the network slice subnet nodes.
  • the network slice management function entity determines the input parameters required by each component according to the network slice requirement information.
  • the network slice subnet template corresponding to the identifier of the network slice subnet template includes a node descriptor of a network function node constituting the network slice subnet, a network connection point descriptor of the network function node, and a network function.
  • the component information required to instantiate the network slice subnet is defined, that is, the content included in the network slice subnet template is defined, so that the network slice subnet management function entity determines the input parameters required by each component according to the network slice subnet requirement information.
  • the network slice template includes information required to instantiate network functions, a network connection point descriptor of a network function node, a service access point descriptor of a network function node, and a network function node A service connection descriptor between the network connection descriptor and the network function node.
  • the network slice management function entity determines the input parameters required by each component according to the network slice requirement information.
  • the network slice template includes a network service descriptor index file corresponding to the virtual network function constituting the network slice, and the network service descriptor index file is used.
  • Virtual resource deployment for instantiating virtual network functions such that the network slice management function entity generates instantiated input parameters of the network service descriptor.
  • the network slice template further includes a service configuration file, and the service configuration file is used for network function service configuration to implement one or some services.
  • the network slice management function entity determines the deployment of the network sliced subnet instance according to the network slice requirement information.
  • the area, the network slice subnet instantiation request also includes the deployment area of the network sliced subnet instance, so that the subsequent management orchestrator can deploy the network function corresponding to the network sliced subnet instance in the data center of the correct area.
  • the network slice subnet requirement information further includes a network slice subnet template identifier or a network slice type, so that the network slice subnet management function entity obtains the network slice subnet template.
  • the network slice subnet instantiation request further includes an identifier of a network slice instance corresponding to the network slice.
  • the network slice management function entity constructs a transport network instantiation request according to the instantiated response sent by each network slice subnet management function entity, and sends a transport network instantiation request to the transport network manager.
  • the network slice management function entity sends a service access request to the corresponding network slice subnet management function entity according to the service access point information obtained after each network slice subnet is instantiated, and the service access is performed.
  • the request includes the identifier of the network slice instance, the identifier of the corresponding network slice subnet template, and the corresponding service access point information, and the service access request is used to trigger the corresponding network slice subnet association function entity to establish a service connection.
  • a seventh aspect of the embodiments of the present application provides a network slice management method, including:
  • the network slice subnet management function entity receives the network slice subnet instantiation request, and the network slice subnet instantiation request includes network slice subnet requirement information;
  • the network slice subnet management function entity acquires a network slice subnet template
  • the network slice subnet management function entity decomposes the network slice subnet requirement information into the network service requirement information, the service configuration requirement information, and the network slice subnet in the network slice subnet template according to the network slice subnet template.
  • Transmission network demand information ;
  • the network slice subnet management function entity sends a network slice subnet instantiation response to the network slice management function entity, where the network slice subnet instantiation response includes network slice subnet instantiation information, where the network slice subnet instantiation information includes the network slice
  • the network slice subnet management function entity sends a network service instantiation request to the management orchestrator, and the network service instantiation request includes network service demand information;
  • the network slice subnet management function entity sends a service configuration request to the network element management system corresponding to the network slice subnet management function entity, where the service configuration request includes service configuration requirement information;
  • the network slice subnet management function entity sends a transport network instantiation request to the transport network manager, and the transport network instantiation request includes transport network requirement information in the network slice subnet.
  • an embodiment of the present application provides a network slice subnet management function entity, including a unit or a means for performing each step of the foregoing seventh aspect.
  • the embodiment of the present application provides a network slice subnet management function entity, including at least one processing element and at least one storage element, wherein at least one storage element is used to store programs and data, and at least one processing element is used to execute the present Apply the method provided in the seventh aspect.
  • the embodiment of the present application provides a network slice subnet management function entity, including at least one processing element (or chip) for performing the method of the above seventh aspect.
  • an embodiment of the present application provides a program, when executed by a processor, for performing the method of the above seventh aspect.
  • the embodiment of the present application provides a program product, such as a computer readable storage medium, including the program of the eleventh aspect.
  • the network slice subnet sub-template is used to decompose the network slice subnet requirement information, thereby realizing automatic management of the network slice subnet.
  • the network slice subnet template includes a node descriptor of a network function node constituting the network slice subnet, a network connection point descriptor of the network function node, a service access point descriptor of the network function node, A network connection descriptor between network function nodes and a service connection descriptor between network function nodes.
  • the node descriptor of the network function node is used to describe information required for instantiating the network function
  • the network connection point descriptor of the network function node is used to describe the network connection point information of the network function node
  • the service access point of the network function node The descriptor is used to describe the service access point information of the network function node
  • the network connection descriptor between the network function nodes is used to describe the network connection information between the network function nodes
  • the service connection descriptor between the network function nodes is used for Describe the service connection information between network function nodes.
  • the content included in the network slice subnet template is described above, so that the network slice subnet management function entity determines the input parameters required by each component according to the network slice subnet requirement information.
  • the network slice subnet template further includes a network service descriptor index file corresponding to the virtual network function constituting the network slice subnet, and the network service descriptor index file is used to instantiate the virtual resource of the virtual network function. deploy.
  • the network slice subnet template further includes a first network function configuration parameter information service configuration file, where the first service configuration file is used for service deployment of the network function, and the first service configuration file is a network slice subnet.
  • the non-business access point configuration file for the instance.
  • the network slice subnet management function entity in a case where the network slice subnet template includes a network service descriptor index file corresponding to a virtual network function constituting the network slice subnet, the network slice subnet management function entity according to the network slice subnet template The input parameters of the various components included generate instantiated input parameters of the network service descriptor.
  • the network slice subnet management function entity in a case where the network slice subnet template does not include a network service descriptor index file corresponding to the virtual network function constituting the network slice subnet, the network slice subnet management function entity according to the network slice subnet template The input parameters of each component included constitute a network service descriptor file corresponding to the virtual network function of the network slice subnet instance.
  • the network slice subnet management function entity inputs according to each component included in the network slice subnet template.
  • the parameter generates an input parameter of the first service configuration file, where the first service configuration file is a non-service access point configuration file of the network sliced subnet instance.
  • the network slice subnet management function entity is configured according to each component included in the network slice subnet template.
  • the input parameter generates a first service configuration file, where the first service configuration file is used for service deployment of the network function, and the first service configuration file is a non-service access point configuration file of the network sliced subnet instance.
  • the network slice subnet management function entity obtains network connection point information and network slice subnet instances and other network slices of the network slice subnet instance and other network slice subnet instances according to the network slice subnet template. Service access point information of the subnet instance.
  • the network slice subnet management function entity sends the network slice subnet instantiation response to the network slice management function entity, receiving a service access request from the network slice management function entity, where the service access request includes the network The identifier of the subnet template, the identifier of the network snippet instance, and the service access point instantiation information.
  • the service access point instantiation information includes the local end of the service access point where the network slicing subnet instance is connected to other network slicing subnet instances.
  • the address information and the peer address information, and the gateway router address information; the network slice subnet management function entity generates a second service configuration file according to the network slice subnet template and the service access point instantiation information, where the second service configuration file is a network slice A service profile that connects a subnet instance to another network sliced subnet instance.
  • the network slice subnet instantiation request further includes a deployment area of the network slice subnet instance
  • the network service instantiation request further includes a deployment area of the network slice subnet instance
  • the network slice subnet requirement information includes a network slice subnet template identifier or a network slice type
  • the network slice subnet management function entity obtains a network slice subnet according to the network slice subnet template identifier or the network slice type. template.
  • a thirteenth aspect of the embodiments of the present disclosure provides a network slice management method, including:
  • the management orchestrator receives the transmission network instantiation request, and the transmission network instantiation request includes the transmission network requirement information;
  • the management orchestrator instantiates the transmission network according to the transmission network requirement information
  • the management orchestrator sends a transport network instantiation response.
  • the embodiment of the present application provides a management orchestrator, including a unit or means for performing the steps of the thirteenth aspect above.
  • the embodiment of the present application provides a management orchestrator, including at least one processing element and at least one storage element, wherein at least one storage element is used to store programs and data, and at least one processing element is used to execute the tenth application.
  • a management orchestrator including at least one processing element and at least one storage element, wherein at least one storage element is used to store programs and data, and at least one processing element is used to execute the tenth application.
  • the embodiment of the present application provides a management orchestrator, including at least one processing element (or chip) for performing the method of the above thirteenth aspect.
  • the embodiment of the present application provides a program for executing the method of the above thirteenth aspect when executed by a processor.
  • the embodiment of the present application provides a program product, such as a computer readable storage medium, including the program of the seventeenth aspect.
  • the management orchestrator can instantiate the transmission network according to the received transmission network requirement information, and can realize the transmission network composed of the network slice subnet instances constituting the network slice instance. Instantiation, it is also possible to instantiate a transport network consisting of network functions that make up a network slice subnet instance.
  • the embodiment of the present application further provides a network slice management system, including a network slice management function entity, a network slice subnet management function entity, and a transport network manager.
  • FIG. 1 is a schematic diagram of a network architecture to which an embodiment of the present application is applied;
  • FIG. 2 is a schematic flowchart of a network slice management method according to an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a network slice template according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a network connection and a service connection according to an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of instantiation of a network slice subnet according to an embodiment of the present disclosure
  • FIG. 6 is a schematic structural diagram of a network slice subnet template according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic flowchart of instantiation of a service connection according to an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a logical structure of a device provided by an embodiment of the present application.
  • FIG. 9 is a simplified schematic diagram of a physical structure of a device provided by an embodiment of the present application.
  • an enhanced mobile broadband (eMBB) scenario (such as virtual reality, augmented reality, etc.) requires high bandwidth and requires xGbps bandwidth.
  • massive machine type communication (mMTC) scenarios (such as wearable scenarios, smart grids, etc.) need to support massive device access, such as the need to support hundreds of millions or billions of devices.
  • ultra-reliable and low latency communications (uRLLC) scenarios (such as autopilot, remote surgery, industrial control, etc.) need to support an ultra-low latency of 1 ms. Faced with different scenarios, different requirements, and the need for extreme experience, network slicing emerges as the times require, and it can flexibly build networks with different characteristics based on 5G scenarios and needs.
  • the network slicing technology logically abstracts the network into one or more isolated network slices, each of which contains a series of logical network functions to specifically meet the differentiated requirements of different service types.
  • the network slicing technology abstracts the 5G network physical infrastructure resources into a plurality of independent parallel network slice instances according to the scene requirements. Each network segment instance performs customized tailoring of network functions and management of corresponding network functions according to the needs of the business scenario and the business model.
  • a network slice instance can be thought of as an instantiated 5G network.
  • Such a network structure allows operators to provide the network as a service to users, and can freely combine physical networks according to indicators such as rate, capacity, coverage, delay, reliability, security, and availability to meet different users. Claim.
  • Different network slices can provide different network functions. For example, for a scenario in which a mobile intelligent terminal (such as a mobile phone) communicates, a separate network slice can be used. For example, for the Internet of Vehicles scenario, due to the ultra-low latency requirement, which is mainly used for the autonomous driving service, the processing delay and reliability of the network are relatively high, and independent network slicing can also be used. For example, for the mMTC scenario, because the number of access devices is large, the packets sent by the access device are relatively small, and the network delay requirements are relatively small. Independent network slices can also be used. Different network slices can deploy different network functions because different network slices need to provide different functions and quality requirements.
  • Network slicing A network that is deployed on a physical or virtual infrastructure to support logical isolation of specific network capabilities and network characteristics, including complete access to the access network, transport network, core network, and application server.
  • the entire network of end to end (E2E), part of the network function can also be shared among multiple network slices, is the fifth generation (5th generation, which is proposed by the 3rd generation partnership project (3GPP).
  • 5G The key technology of mobile communication technology for network differentiation needs.
  • network characteristics of different network slices are not the same, and network slices are required to be isolated from each other without affecting each other.
  • network slicing of augmented reality (AR) or virtual reality (VR) services requires large bandwidth and low latency
  • network segmentation of Internet of Things (IOT) services requires massive terminal access.
  • the network slice can also be any combination of a terminal device, an access network, a transport network, a core network, and an application server.
  • a network slicing instance is a real-world logical network that meets certain network characteristics or service requirements.
  • a network slice instance may provide one or more network services.
  • a network slice instance can be created by a network slice management system, and a network slice management system may create multiple network slice instances and manage them at the same time.
  • a network slice instance can be created from a network slice template.
  • NST network slice template
  • a complete network slicing instance is capable of providing complete end-to-end network services, and the network slicing instances may be network slicing subnet instances and/or network functions.
  • the network slice subnet instance may not need to provide a complete network service end-to-end.
  • the network slice subnet instance may be a network function component set of the same device vendor in the network slice instance, or may be a collection of network functions divided by domain. For example, the core network network slice subnet instance and the access network network slice subnet instance.
  • a network sliced subnet instance may be shared by multiple network slice instances.
  • a network slice instance may consist of several network slice subnet instances, each network slice subnet instance consisting of several network functions and/or other network slice subnet instances; one network slice instance may be composed of several network slice subnet instances and none The network functions that are divided into network slice subnet instances are directly composed; a network slice instance may also consist of only a few network functions.
  • a network slice subnet template (NSST) is used to create a network slice subnet instance.
  • a network function is equivalent to providing a network service that defines functional behavior and interfaces.
  • the network function may include a session management function (SMF), a policy control function (PCF), a user plane function (UPF), and an evolved base station (evolved node B, eNB) or 5G base station (new radio (NR) nodeB, gNB), access and mobility management function (AMF) and network storage function (NRF), and so on.
  • SMF session management function
  • PCF policy control function
  • UPF user plane function
  • evolved node B evolved node B
  • NR nodeB new radio (NR) nodeB
  • gNB new radio (NR) nodeB
  • AMF access and mobility management function
  • NRF network storage function
  • the SMF is used to provide session management services
  • the PCF is used to provide policy control services
  • the UPF is used to provide user plane services
  • the AMF is used to provide access and mobility management services
  • eNB or gNB Used to provide wireless access services
  • NRF is used to provide service discovery.
  • Network functions can be implemented by dedicated hardware, by running software on dedicated hardware, or as virtual functions on a common hardware platform. Therefore, from the perspective of implementation, the network function can be divided into a physical network function (PNF) and a virtualised network function (VNF). From the perspective of use, network functions can be divided into dedicated network functions and shared network functions. Specifically, for multiple (sub)network slice instances, different network functions can be used independently. This network function is called exclusive. Network function; can also share the same network function, this network function is called shared network function. The following are collectively referred to as physical network functions and/or virtual network functions as network functions.
  • NFVI network functions virtualisation infrastructure
  • NFVI mapping to physical infrastructure is a number of geographically dispersed data centers (dates, DCs) that are connected by high-speed communication networks.
  • NFVI needs to convert physical computing/storage/switching resources into virtual compute/storage/swap resource pools through virtualization.
  • the management and orchestration is responsible for the management and orchestration of the entire NFVI resource, the mapping and association of the service network and NFVI resources, and the implementation of the operational support system (OSS) service resource flow.
  • OSS operational support system
  • Network segmentation and network slicing subnets need to be instantiated.
  • MANO needs to complete the instantiation of network service (NS).
  • the instantiation of network services is mainly required for NFVI to apply for network slicing or network slicing subnet instantiation. Virtual resources.
  • a network service descriptor that describes the network topology of the instantiated network service and the required resource information.
  • MANO can instantiate network services based on NSD.
  • An element management system is a network element management system for network functions, which is used to deliver network function service configuration to a network function.
  • FIG. 1 it is a schematic diagram of a network architecture that is applied to an embodiment of the present application, where the network architecture includes a communication service management function (CSMF), a network slice management function (NSMF), and a network slice subnet.
  • CSMF communication service management function
  • NSMF network slice management function
  • NSSMF Network slice subnet management function
  • the user can negotiate with the operator to determine the corresponding communication service requirements, such as the scope of the network service to be covered, the number of users, and the user distribution, mobility requirements, delay requirements, and whether the network slice needs to be isolated from other network slices. and many more.
  • the CSMF is primarily responsible for translating the communication service requirements of the operator and/or third party customers into network slice requirement information including network slice type/slice template identification ID and network slice deployment requirement information (eg network capacity) , the quality of service QoS requirement, etc.; sending the network slice requirement information to the NSMF through an interface with the NSMF; acquiring management data (such as performance, fault data, etc.) of the network slice from the NSMF; generating and running on the network slice instance The management data of the communication service; the subscription requirement of the management data of the network slice management data and/or the communication service received by the operator and/or the third party customer.
  • network slice requirement information including network slice type/slice template identification ID and network slice deployment requirement information (eg network capacity) , the quality of service QoS requirement, etc.
  • network slice requirement information including network slice type/slice template identification ID and network slice deployment requirement information (eg network capacity) , the quality of service QoS requirement, etc.
  • the NSMF is mainly responsible for receiving the network slice requirement information sent by the CSMF; managing the life cycle, performance, and faults of the network slice instance (hereinafter, the life cycle, performance, and fault management are referred to as management); composing the composition of the network slice instance; and decomposing the network slice
  • the demand information is demand information of each network slice subnet instance and/or network function, and a transport network (TN) requirement; sending a network slice subnet instantiation request to each NSSMF to the transport network manager (TN-manager) ) Send transmission network requirements, etc.
  • the NSSMF is mainly responsible for receiving the network slice subnet requirements sent by the NSMF; managing the network slice subnet instance; orchestrating the composition of the network slice subnet instance; and decomposing the network slice subnet instance requirements for each network function and/or nested network slice.
  • the requirements of the subnet instance may send nested network slice subnet instantiation requests to other NSSMFs, possibly managing nested network slice subnet instances, and so on.
  • the network function management entity, the network function management, and the NSMF are interchangeable in the embodiment of the present application.
  • the three words are used to describe the entity responsible for receiving the network slice request sent by the CSMF, and does not constitute an embodiment of the present application. Limited. Same as NSSMF, CSMF.
  • the embodiment of the present application provides a network slice management method and device thereof, which utilizes a network slice template to decompose network slice requirements, and can implement network slice management automatically.
  • FIG. 2 is a schematic flowchart of a network slice management method according to an embodiment of the present disclosure.
  • the method is introduced from the perspective of interaction between NSMF and NSSMF and TN-manager, where TN-manager is responsible for network slice subnet nodes.
  • the method shown in FIG. 2 is composed of two network slice subnet instances with one network slice instance, NSSMF 1 can be instantiated to obtain network slice subnet instance 1 (NSSI-1), and NSSMF 2 can be instantiated to obtain network slice subnet instance. (NSSI-2)
  • the method shown in FIG. 2 may include but is not limited to the following steps:
  • step S200 a network slice template is generated.
  • the slice involves a person (such as a slice provider) to design a network slice template, generate a network slice template, and upload (on-boarding) the network slice template to the NSMF.
  • the NSMF can record and save the correspondence between the network slice template and the network slice requirement information, where the network slice requirement information includes the identifier of the network slice template or the network slice type.
  • the network slice type is used to characterize the type of network service provided by the slice, and may be, for example, a high definition video service class, a car network class, or the like. Uploading the network slice template to the NSMF is a prerequisite for the implementation of the embodiment of the present application.
  • the network slice template is used to describe the component information required for instantiating the network slice, including the node description information of the nodes constituting the network slice and the connection description information between the nodes.
  • a node can be a network slice subnet node or a network function node.
  • the node description information includes a network sliced node descriptor (NSS node descriptor), a network connection point descriptor of the network sliced subnet node, and a service access point descriptor of the network slice subnet node, the connection description information including a service connection descriptor between the network slice subnet nodes and a network between the network slice subnet nodes Connection descriptor (network connection descriptor).
  • NSS node descriptor network sliced node descriptor
  • the connection description information including a service connection descriptor between the network slice subnet nodes and a network between the network slice subnet nodes Connection descriptor (network connection descriptor).
  • the node description information further includes a network function node descriptor (NF node descriptor), a network function point node of the network function node, and a service access point descriptor of the network function node, and the connection
  • the description information also includes a network connection descriptor between different network function nodes and a service connection descriptor between the network function nodes.
  • the network function node may be a virtual network function node (VNF node) or a physical network function node (PNF node).
  • a network slice includes two network slice subnets, and the nodes corresponding to the two network slice subnets are an access network (AN) node and a core network (CN) node, and access network nodes ( There is a network connection and a service connection between the AN node and the CN node.
  • a network connection is used to describe the physical connection between two nodes, that is, the two nodes are physically connected.
  • a service connection is required. .
  • FIG. 4 is a schematic diagram of network connection and service connection based on this assumption.
  • the gray point on the node is the service access point
  • the black point is the network connection point.
  • the network connection point 1 of the AN node and the network connection point 1 of the CN node are connected by a solid line, indicating that there is a network connection between the AN node and the CN node, that is, the solid line shown in FIG. 4 is the network between the AN node and the CN node.
  • Connection, network connection is used to carry the network connection information between AN and CN.
  • the service access point 1 of the AN node and the service access point 1 of the CN node are connected by a long dotted line, indicating that there is a service connection between the AN node and the CN node, that is, the long dotted line shown in FIG. 4 is between the AN node and the CN node.
  • the service connection is used to carry the service interworking information between the AN and the CN.
  • the service access point of the AN node depends on its network connection point, and the service access point of the CN node depends on its network connection point. It should be noted that there is a network connection point and a service access point on a node shown in FIG. 4, which does not constitute a limitation on the embodiment of the present application. In actual application, multiple network connection points and multiple nodes exist on one node. Service access points.
  • the network connection point of one node can be connected to the network connection point of other nodes, that is, the network connection point of one network slice subnet node can be connected to the network connection point of other network slice subnet nodes, or can be connected with the application server. Or the network connection point of the application software to make a network connection.
  • different nodes in a network slice instance may be connected to a connected network through a network connection point, thereby implementing a network connection of the node.
  • a service access point of one node can perform service connection with a service access point of another node, that is, a service access point of one network slice subnet node can perform service connection with a service access point of another network slice subnet node, It can be connected to the service access point of the application server or application software.
  • the network slice subnet node descriptor includes component information required to instantiate a network slice subnet, and component information required to instantiate a network slice subnet includes a node descriptor of a network function node constituting a network slice subnet, and a network function node
  • the network connection point descriptor, the service access point descriptor of the network function node, the network connection descriptor between the network function nodes, and the service connection descriptor between the network function nodes It can be understood that the network slice subnet node descriptor is used to describe the information needed to instantiate the network slice subnet.
  • the service connection information may include information such as a service connection protocol and a service connection related parameter. It can be understood that the service connection descriptor between the network slice subnet nodes is used to describe the service connection protocol between the network slice subnet nodes and the service connection related parameters, and the like.
  • the network connection information may include information such as quality of service (QoS) information of the network plane, type of Internet Protocol (IP), and the like. It can be understood that the network connection descriptor between the network slice subnet nodes is used to describe which network connection information is used between the network slice subnet nodes for network connection.
  • QoS quality of service
  • IP Internet Protocol
  • a service access point descriptor of the network slicing subnet node used to describe the service access point information of the network slicing subnet node.
  • the service access point information may be information of a service access point where the network slice subnet node is connected to a device other than the network slice, or may be a service connection between the network slice subnet node and an application server or application software. Information about the service access point.
  • the service access point information may include information such as a service IP address of the service access point. If there are multiple service access points on the network slice subnet node, each service access point may correspond to one service access point descriptor.
  • a network connection point descriptor of the network slicing subnet node that describes the network connection point information of the network slicing subnet node.
  • the network connection point information may be information of a network connection point where the network slice subnet node is connected to other network slice subnet nodes, or may be a network connection point where the network slice subnet node and the device other than the network slice are connected to the network. Information.
  • the network connection point information may include information such as a physical IP address of the network connection point. If there are multiple network connection points on the network slicing subnet node, then each network connection point may correspond to one network connection point descriptor.
  • the network slice subnet node is a node of a network slice subnet constituting a network slice.
  • the physical IP address can be understood as the physical interface IP geography, and the service IP address is an IP address for performing service interaction with other network elements. However, service IP packets are sent from the physical interface.
  • the node description information includes component information required to instantiate the network slice subnet, a network connection point descriptor of the network slice subnet node, and a network slice.
  • the service access point descriptor of the subnet node, the connection description information includes a network connection descriptor between the network slice subnet nodes and a service connection descriptor between the network slice subnet nodes.
  • the node description information may include a network function node descriptor shown by a dashed box in FIG. 3, a network connection point descriptor of the network function node, and a service access point of the network function node. Descriptor.
  • the connection description information may include a network connection descriptor between the network function nodes and a service descriptor between the network function nodes. Among them, the network function node descriptor is used to describe the information required to instantiate the network function.
  • a network connection point descriptor of the network function node a service access point descriptor of the network function node, a network connection descriptor between the network function nodes, and a service descriptor between the network function nodes and the network slice subnet node respectively
  • the network connection point descriptor, the service access point descriptor of the network slice subnet node, the network connection descriptor between the network slice subnet nodes, and the service descriptor type between the network slice subnet nodes are not described here. .
  • the network slice template may include a service profile as shown by the dotted box in FIG. 3, and the service profile is used for service configuration of the network function. It can be understood that the service profile indicates which business functions are to be implemented by the network function.
  • the network slice template may include a Network Service Descriptor (NSD) index file as shown by the dashed box in FIG. 3, which may be an NSD ID.
  • NSD Network Service Descriptor
  • the network service descriptor is used to instantiate the virtual resource deployment of the associated network function, and the associated network function is the virtual network function that constitutes the network slice.
  • the MANO can complete the virtual resource deployment of the associated network function according to the corresponding NSD file of the network service descriptor ID, and the virtual resource can include a virtual memory resource and a central processing unit. , CPU) and so on.
  • Step S201 The NSMF receives the network slice instantiation request, where the network slice instantiation request includes network slice requirement information, and the network slice requirement information includes a network slice template identifier or a network slice type.
  • Subscribers of network slices can perform network slice ordering through the operation interface of the business support system (BSS), that is, input service requirements on the operation interface of the BSS.
  • the service requirement may include a service type, and may also include a service-level agreement (SLA) requirement, and the SLA is a contract between the network service provider and the customer, and the SLA requirement may include the number of users, bandwidth requirements, and delay. Guarantee demand, etc. Understandably, business needs include business type and SLA requirements.
  • CSMF (or BSS-CSMF) converts service requirements into network slice requirement information, including service type conversion and SLA demand conversion, when receiving business requirements.
  • the service type conversion converts the service type in the service requirement into a network slice type, for example, into an eMBB network slice, a uRLLC network slice, a mMTC network slice, and the like.
  • the CSMF may further search for a network slice template identifier (NST ID) corresponding to the network slice type according to the network slice type.
  • NST ID network slice template identifier
  • the SLA demand conversion converts the SLA requirements into network slice deployment requirement information, and the network slice deployment requirement information may include requirements such as the number of users, bandwidth, and delay. In other words, the network slice deployment requirement information is used to describe the demand information such as the number of users, bandwidth, and delay.
  • the network slice requirement information includes a network slice type and a network slice deployment requirement information
  • the network slice type is used to indicate a network slice type
  • the network slice template identifier can be determined according to the network slice type; or the network slice requirement information includes a network slice template.
  • the identification and network slice deployment requirement information, and the network slice template identifier is used to indicate the network slice template.
  • the network slice requirement information can provide input parameters for the instantiation of the network slice.
  • the CSMF sends a network slice instantiation request to the NSMF.
  • the network slice instantiation request includes network slice requirement information, and the network slice requirement information includes a network slice template identifier or a network slice type, and network slice deployment requirement information.
  • the NSMF receives a network slice instantiation request from the CSMF.
  • the network slice instantiation request may be an initial instantiation request, ie, the request instantiates a network slice instance that does not exist in the current system.
  • Step S202 The NSMF acquires a network slice template according to the network slice template identifier or the network slice type.
  • the NSMF obtains a network slice template corresponding to the network slice template identifier according to the network slice template identifier, and one network slice template identifier corresponds to one network slice template.
  • the NSMF obtains a network slice template corresponding to the network slice type according to the network slice type, and one network slice type corresponds to one network slice template.
  • the network slice template identifier corresponding to the network slice type is searched according to the network slice type, and the network slice template is obtained according to the network slice template identifier.
  • the NSMF may also assign an identifier to the network slice instance corresponding to the network slice template, that is, allocate a network slice instance identifier (NSI ID).
  • NSS network slice instance identifier
  • Step S203 the NSMF decomposes the network slice requirement information into the network slice subnet requirement information 1, the network slice subnet requirement 2, and the transmission network requirement information according to the network slice template.
  • the NSMF decomposes the network slice requirement information according to the content included in the network slice template, and decomposes the network slice subnet requirement information corresponding to the node description information and the transmission network requirement information corresponding to the connection description information.
  • the network slice subnet requirement information corresponding to the node description information includes the network slice subnet requirement information 1 corresponding to the node description information of the network slice subnet node 1 and the network slice subnet requirement information corresponding to the node description information of the network slice subnet node 2 2.
  • the network slice subnet requirement information 1 includes a network slice subnet template identifier (NSST ID), an input parameter required to instantiate the network slice subnet 1, a network connection point information of the network slice subnet node 1, and a network slice subnet. Service access point information of node 1.
  • the transmission network requirement information includes network connection information between the network slice subnet node 1 and the network slice subnet node 2.
  • the network slice subnet requirement information 2 includes a network slice subnet template identifier (NSST ID), an input parameter required to instantiate the network slice subnet 2, a network connection point information of the network slice subnet node 2, and a network slice subnet node 2 Business access point information.
  • the transmission network requirement information includes network connection information between the network slice subnet node 2 and the network slice subnet node 2.
  • the network slice subnet requirement information provides input parameters for instantiation of the network slice subnet, including providing input parameters for instantiation of the network slice subnet and providing a network connection point for the network connection point of the network slice subnet node.
  • the information provides service access point information for the service access point of the network slice subnet node.
  • the transport network connection information provides input parameters for the instantiation of the transport network, including providing network connection input parameters for network connections between network slicing subnet nodes.
  • the network slice template defines which components are needed for instantiating the network slice and the input parameters required by the component, and the network slice requirement information can provide input parameters, and the NSMF can decompose the network slice requirement information according to the network slice template, that is, according to each component.
  • the required input parameters provide the corresponding input parameters for each component.
  • the NSMF determines the deployment areas of NSSI-1 and NSSI-2 according to the network slice requirement information, that is, determines the deployment place of each NSSI. This facilitates subsequent MANOs to deploy the network functions corresponding to the network slice subnet instance in the data center (DC) of the correct area.
  • DC data center
  • the NSMF decomposes the network slice requirement information into the service configuration requirement information, the network service requirement information, and the transmission network requirement information of the network function in the network slice according to the network slice template.
  • Step S204a The NSMF sends a network slice subnet instantiation request 1 to the NSSMF 1, and the network slice subnet instantiation request 1 includes the network slice subnet requirement information 1.
  • NSSMF 1 receives the network slice subnet instantiation request 1 from the NSMF.
  • Step S204b The NSMF sends a network slice subnet instantiation request 2 to the NSSMF 2, and the network slice subnet instantiation request 2 includes the network slice subnet requirement information 2.
  • NSSMF 2 receives the network slice subnet instantiation request 1 from the NSMF.
  • the NSMF sends a network slice subnet instantiation request to each NSSMF, and carries a corresponding network slice subnet requirement information in the network slice subnet instantiation request.
  • the network slice is composed of a network slice subnet 1 and a network slice subnet 2, and the NSMF sends a network slice subnet instantiation request 1 to the NSSMF 1 to carry the demand information of the network slice subnet 1; the NSMF sends the network slice to the NSSMF 2
  • the network instantiation request 2 carries the demand information of the network slice subnet 2.
  • the NSSMF1 decomposes the demand information of the network slicing subnet 1 according to the NSST 1, and obtains the network service requirement information 1, the service configuration requirement information 1 and the transmission network demand information 1, and sends the network service demand information 1 to the MANO, and the EMS 1 corresponding to the NSSMF1.
  • the NSSMF 2 decomposes the demand information of the network slicing subnet 2 according to the NSST2, and obtains the network service requirement information 2, the service configuration requirement information 2, and the transmission network demand information 2, and sends the network service demand information 2 to the MANO to the EMS 2 corresponding to the NSSMF2.
  • the service configuration requirement information 2 is sent, and the transmission network requirement information 2 is sent to the TN-manager.
  • the network slice subnet instantiation request further includes a deployment area of the corresponding network slice subnet instance, so that the subsequent MANO can deploy the network function corresponding to the network slice subnet instance in the DC of the correct area.
  • the network slice subnet instantiation request 1 also includes a deployment area of NSSI-1
  • the network slice subnet instantiation request further includes a deployment area of NSSI-2.
  • the network slice subnet instance request may also include an identification (NSI ID) of the network slice instance corresponding to the network slice.
  • NSI ID an identification of the network slice instance corresponding to the network slice.
  • the network slice subnet requirement information may further include a corresponding network slice subnet template identifier or network slice type information.
  • Step S205a the NSSMF 1 sends a network slice subnet instantiation response 1 to the NSMF, and the network slice subnet instantiation response 1 includes instantiation information 1.
  • the NSMF receives the network slice subnet instantiation response 1 from the NSSMF 1.
  • Step S205b the NSSMF 2 sends a network slice subnet instantiation response 2 to the NSMF, and the network slice subnet instantiation response 2 includes instantiation information 2.
  • the NSMF receives the network slice subnet instantiation response 2 from the NSSMF 2.
  • the NSSMF 1 sends the instantiation information 1 to the NSMF after completing the instantiation of the network service 1. After completing the instantiation of the network service 2, the NSSMF 2 sends the instantiation information 2 to the NSMF.
  • the instantiation information 1 includes an identifier of the network slice subnet instance 1 (NSSI-1ID), network connection point instantiation information of the network slice subnet instance 1, and service access point instantiation information of the network slice subnet instance 1.
  • the NSSI-1 network connection point instantiation information includes information such as the local IP address of the network connection point where the NSSI-1 and the NSSI-2 are connected, and the IP address of the network connection point where the NSSI-1 interfaces with the external access device. information. Similarly, NSSI-2 network connection point instantiation information can be defined.
  • the service access point instantiation information of the NSSI-1 includes the local IP address of the service access point where the NSSI-1 is connected to the NSSI-2, and the IP address of the service access point where the NSSI-1 is connected to the external access device. And other information. Similarly, the service access point instantiation information of NSSI-2 can be defined.
  • the access device information may be information that the gateway router in the DC deployed in the network slice subnet instance is connected to the transport switch, including the access device identifier and the port identifier.
  • the local IP address refers to the IP address on NSSI-1
  • the peer IP address refers to the IP address of NSSI-2.
  • the NSMF can record and store the instantiated information sent by each NSSMF.
  • step S204a and step S205a, step S204b and step S205b are processes for instantiating a network slice subnet. For details, refer to the description of FIG. 5.
  • Step S206a the NSMF sends a service access request 1 to the NSSMF 1, and correspondingly, the NSSMF 1 receives the service access request 1 from the NSMF.
  • Step S206b the NSMF sends a service access request 2 to the NSSMF 2, and correspondingly, the NSSMF 2 receives the service access request 2 from the NSMF.
  • Step S206a and step S206b are performed after step S205a and step S205b.
  • the service access request includes a network slice instance identifier, a network slice subnet template identifier, and a service access point information.
  • the service access point instantiation information includes information such as the local IP address of the service access point and the peer IP address, and the IP address of the gateway router, which are connected to the network slice subnet instance.
  • the gateway router IP address is also the next hop routing IP address.
  • the NSSI-1 service access point is connected to the NSSI-2 service access point.
  • the local IP address refers to the IP address of the service access point on the NSSI-1.
  • the IP address of the end refers to the IP address of the service access point on the NSSI-2.
  • the NSMF After receiving the instantiation information 1 and the instantiation information 2, the NSMF sends a service access request 1 to the NSSMF 1.
  • the service access request 1 carries the identifier of the network slice instance and the network slice subnet template corresponding to the network slice subnet instance 1. Identification and service access point information 1.
  • the NSMF After receiving the instantiation information 1 and the instantiation information 2, the NSMF sends a service access request 2 to the NSSMF 2, where the service access request carries the identifier of the network slice instance and the network slice subnet template identifier corresponding to the network slice subnet instance 2
  • the service access request 2 carries the identifier of the network slice instance, the network slice subnet template identifier corresponding to the network slice subnet instance 2, and the service access point information 2.
  • step S207a the NSSMF 1 sends a service access confirmation message 1 to the NSMF.
  • the NSMF receives the service access confirmation message 1 from the NSSMF 1.
  • step S207b the NSSMF 2 sends a service access confirmation message 2 to the NSMF. Accordingly, the NSMF receives the service access confirmation message 2 from the NSSMF 2.
  • the NSSMF After the EMS completes the service configuration, the NSSMF sends a service access confirmation message to the NSMF, and carries the network slice subnet instance identifier to notify the NSMF that the corresponding network slice subnet instance has accessed the service.
  • the service access confirmation message 1 is used.
  • the service access confirmation message 2 is used to notify the NSSI-2 that the service has been accessed.
  • step S206a and the step S207a, the step S206b and the step S207b are the flow of the service access instantiation. For details, refer to the description of FIG. 7.
  • Step S208 the NSMF sends a transport network instantiation request to the TN-manager.
  • TN-manage receives the transmission network instantiation from the NSMF.
  • step S208 is performed after step S205a and step S205b. Step S208 can be performed simultaneously with step S206a and step S206b.
  • the NSMF creates a transport network instantiation request between each network slice subnet instance according to the instantiation information sent by each NSSMF, for example, creates a transport network instantiation request between NSSI-1 and NSSI-2.
  • the transport network instantiation request includes information such as NSSI-1 and NSSI-2 for network connection IP address (ie, IP addresses at both ends) (ie, network slice subnet node 1 and network slicer) QoS information of the network connection IP address of the NSSI-1 network slice subnet instance 1 and the NSSI-2 network slice subnet instance 2 (ie, the network slice subnet node 1 and the network slicer)
  • the network node 2 performs QoS information of the network connection).
  • the transport network instantiation request further includes access device information that is connected to the NSSI-1 network slice subnet instance 1 and the NSSI-2 network slice subnet instance 2, and the access device information may be in the DC deployed by the network slice subnet instance.
  • the information that the gateway router connects to the transport switch including the access device identifier and port identifier.
  • the NSMF can search for the access device information corresponding to the deployment location according to the data center and the transport network topology map.
  • Step S209 the TN-manager performs the transmission network instantiation according to the transmission network instantiation request.
  • the TN-manager When receiving the transmission network instantiation request, the TN-manager instantiates the transmission network according to the transmission network requirement information, establishes a network connection between the network slice subnet instances, and can also establish a network slice subnet instance and an access device. Network connection between.
  • step S210 the TN-manager sends an acknowledgement message to the NSMF.
  • a confirmation message is fed back to the NSMF to inform that the instantiation of the transport network has been completed.
  • the NSMF uses the network slice template to decompose the network slice requirement information, and decomposes it into network slice subnet requirement information and transmission network requirement information, so that the NSSMF performs instantiation of the network service and an instance of the service connection. For the TN-manager to instantiate the transport network.
  • FIG. 5 is a schematic flowchart of instantiation of a network slice subnet according to an embodiment of the present application. The process is introduced from the perspective of interaction between NSMF and NSSMF and MANO, and an NSSMF is taken as an example. The process shown in FIG. 5 may include, but is not limited to, the following steps:
  • Step S300 generating a network slice subnet template.
  • the slice involves a person (such as a slice provider) to design the network slice subnet template, generate a network slice subnet template, and upload the network slice subnet template to the NSSMF.
  • the NSSMF can record and save the correspondence between the network slice subnet template and the network slice subnet requirement information, where the network slice subnet requirement information includes the identifier of the network slice subnet template or the network slice type.
  • the network slice type is used to characterize the type of network service provided by the slice, and may be, for example, a high definition video service class, a car network class, or the like.
  • the schematic diagram of the composition of the network slice subnet template can be seen in Figure 6.
  • the network slice subnet template is used to describe the component information required to instantiate the network slice subnet, including the node description information of the network function nodes that make up the network slice subnet.
  • the connection description information between the network function nodes specifically includes node description information of each network function node and connection description information between the nodes.
  • the node description information of the network function node includes a network function node descriptor, a network connection point descriptor of the network function node, and a service access point descriptor of the network function node.
  • the connection description information includes a service connection descriptor between the network function nodes and a network connection point descriptor between the network function nodes.
  • the Network Function Node Descriptor is used to describe the input parameters required to instantiate network functions.
  • connection point descriptor of the network function node a network connection point descriptor of the network function node, a service access point descriptor of the network function node, a service connection descriptor between the network function nodes, and a network connection descriptor between the network function nodes and a network of the network slice subnet node
  • the connection point descriptor, the service access point descriptor of the network slice subnet node, the service connection descriptor between the network slice subnet nodes, and the network connection descriptor type between the network slice subnet nodes are not described here. .
  • the network slice subnet template may include a service profile as shown by the dotted box in FIG. 6, and the service profile is used for service configuration of the network function. It can be understood that the service profile indicates which business functions are to be implemented by the network function.
  • the network slice subnet template may include a network service descriptor index file as shown by the dashed box in FIG. 6, which may be an NSD ID.
  • the network service descriptor is used to instantiate the virtual resource deployment of the network function, and the network function is a network function that constitutes a network slice subnet. It can be understood that, in this case, the MANO can complete the virtual resource deployment of the network function according to the network service descriptor ID indexing the corresponding NSD file, and the virtual resource can include a virtual memory resource, a virtual CPU, and the like.
  • the network slice subnet template may include the network slice subnet template corresponding to the nested network slice subnet instance, in addition to the content shown in FIG. .
  • Step S301 the NSSMF receives the network slice subnet instantiation request, and the network slice subnet instantiation request includes network slice subnet requirement information.
  • the network slice subnet requirement information is an input parameter provided by the NSMF to the NSSMF for the NSSMF to instantiate the network slice subnet.
  • the network slice subnet instantiation request also includes a deployment area of the network sliced subnet instance, so that during the instantiation process, the MANO can deploy the network function corresponding to the network sliced subnet instance in the DC of the correct area.
  • the network slice subnet instantiation request further includes an identifier of the network slice instance, so that the NSSMF manages which network slice instance the network slice subnet requirement information belongs to.
  • step S301 corresponds to step S204a and step S204b in the embodiment shown in FIG. 2.
  • Step S302 The NSSMF obtains a network slice subnet template.
  • the NSSMF obtains a network slice subnet template corresponding to the network slice subnet template identifier according to the network slice subnet template identifier, and one network slice subnet template identifier corresponds to one network slice subnet template.
  • the NSSMF obtains a network slice template corresponding to the network slice type according to the network slice type, and one network slice type corresponds to one network slice subnet template.
  • the network slice subnet template identifier corresponding to the network slice type is searched according to the network slice type, and the network slice subnet template is obtained according to the network slice subnet template identifier.
  • the NSSMF may also assign an identifier to the network slice subnet instance corresponding to the network slice subnet template, that is, assign a network slice subnet instance identifier (NSSI ID).
  • NSSI ID network slice subnet instance identifier
  • a network slice subnet template is instantiated once to get a network slice subnet instance.
  • Step S303 The NSSMF decomposes the network slice subnet requirement information into network service requirement information, service configuration requirement information, and transmission network requirement information in the network slice subnet according to the network slice subnet template.
  • the NSSMF obtains the input parameters required for instantiating the network function, the network connection point information of the network function node, the service access point information of the network function node, and the network function node according to the network slice subnet template from the network slice subnet requirement information.
  • the NSSMF is based on The five kinds of information obtained above generate the instantiated input parameters of the NSD, that is, the input parameters required for the NS instantiation, and the network service demand information is the instantiated input parameter of the NSD.
  • the NSSMF The NSD file corresponding to the VNFs constituting the NSSI is generated according to the five kinds of information obtained above, and the network service requirement information is the generated NSD file.
  • the NSSMF If the component information required to instantiate the network slice subnet further includes the index information of the first service profile, that is, the NSST includes the index information of the first service profile, the NSSMF generates the first service profile according to the five types of information obtained above.
  • the input parameter, then the service configuration requirement information is an input parameter of the first service profile.
  • the NSSMF If the component information required to instantiate the network slice subnet does not include the index information of the first service profile, that is, the NSST does not include the index information of the first service profile, the NSSMF generates the first service configuration according to the five types of information obtained above. File, then the service configuration requirement information is the first service configuration file.
  • the first service configuration file is a non-service access point configuration file of the network slice subnet instance, that is, a service access point configuration file that does not include the network slice subnet instance and other network slice subnet instances.
  • the transport network demand information provides input parameters for the instantiation of the transport network, including providing network connection input parameters for network connections between network function nodes.
  • Step S304 the NSSMF sends a network service instantiation request to the MANO, where the network service instantiation request includes network service demand information.
  • the network service instantiation request also includes a network slice subnet template identifier.
  • the network service instantiation request further includes a deployment area of the network slice subnet instance.
  • the network service instantiation request also includes an identifier (NSD ID) of the network service descriptor so that the MANO instantiates the NS corresponding to the NSD ID.
  • NSD ID an identifier
  • step S305 the MANO instantiates the network service according to the network service demand information.
  • MANO instantiates network services based on network service demand information, including deploying detailed locations of network functions.
  • the MANO instantiates the network service according to the instantiation requirement information of the NSD; if the network service requirement information is an NSD file, the MANO instantiates the network service according to the NSD file.
  • Step S306 the MANO sends a network service instantiation response to the NSSMF.
  • the MANO After completing the instantiation of the network service, the MANO sends a network service instantiation response to the NSSMF, and the network service instantiation response includes the identifier of the network sliced subnet instance (NSSI ID) and the deployment of the network function constituting the network slice subnet instance.
  • NSSI ID network sliced subnet instance
  • the location information and the network connection point instantiation information of the network connection point corresponding to the VNF, and the instantiation information of the network connection point includes information such as an IP address.
  • Step S307 The NSSMF sends a service configuration request to the corresponding EMS, where the service configuration request includes service configuration requirement information.
  • the service configuration requirement information is the first service configuration file or the requirement information of the first service configuration file.
  • Step S308 the NSSMF sends a transport network instantiation request to the TN-manager, where the transport network instantiation request includes transport network requirement information.
  • Step S308 is similar to step S208 in the embodiment shown in FIG. 2, except that one is a transmission network composed of network slice subnet nodes, and one is a transmission network composed of network functions.
  • Step S309 the TN-manager performs the transmission network instantiation according to the transmission network instantiation request.
  • the TN-manager upon receiving the transmission network instantiation request, instantiates the transmission network according to the transmission network instantiation request, and establishes a network connection between the network functions.
  • step S310 the TN-manager sends an acknowledgement message to the NSSMF.
  • a confirmation message is fed back to the NSSMF to inform that the instantiation of the transport network has been completed.
  • Step S311 The NSSMF obtains network connection point information of the network slice subnet instance and other network slice subnet instances, and service access of the network connection point information of the network slice subnet instance and other network slice subnet instances according to the network slice subnet template. Point information.
  • the network connection point of the network slice subnet node describes the network connection point information of the network connection of the network slice subnet node and other network slice subnet nodes. Therefore, the NSSMF can slice the network connection point descriptor of the subnet node according to the network.
  • the network connection point information of the network slice subnet instance and other network slice subnet instances is obtained by combining the network slice subnet requirement information.
  • the service access point of the network slicing subnet node describes the service access point information for the network slicing subnet node to connect with other network slicing subnet nodes. Therefore, the NSSMF can slice the service access point of the subnet node according to the network.
  • the descriptor in combination with the network slice subnet requirement information, obtains service access information of the network slice subnet instance and other network slice subnet instances.
  • Step S312 the NSSMF sends the instantiation information to the NSMF.
  • the instantiation information includes an identifier of the network slice subnet instance, network connection point instantiation information of the network slice subnet instance, and service access point instantiation information of the network slice subnet instance.
  • the network connection point instantiation information of the network sliced subnet instance includes the local IP address of the network connection point where the network sliced subnet instance interfaces with other network sliced subnet instances, and also includes the network sliced subnet instance and the application server or external access. Network connection point information for device docking.
  • the service access point instantiation information of the network sliced subnet instance includes the local IP address of the service access point where the network sliced subnet instance is connected to other network sliced subnet instances, and includes the network sliced subnet instance and the application server or external Service access point information that the access device is connected to.
  • NSSI-1 is connected to NSSI 2.
  • the local IP address refers to the IP address on NSSI-1
  • the peer IP address refers to the IP address of NSSI-2.
  • the NSMF can record and store the instantiated information sent by each NSSMF.
  • step S312 corresponds to step S205a and step S205b in the embodiment shown in FIG. 2.
  • step S304, step S307, and step S308 is not limited to that shown in FIG. 6, and three steps may be simultaneously performed.
  • the NSSMF in the process shown in Figure 6 can be any NSSMF. If the network slicing instance consists of multiple network slicing subnet instances, there are multiple NSSMFs.
  • the network slicing subnet instantiation process for each NSSMF can be as follows. Process execution.
  • FIG. 7 is a schematic flowchart of a service connection instantiation according to an embodiment of the present application. The process is introduced from the perspective of interaction between NSMF and NSSMF and EMS. The flow shown in FIG. 7 may include, but is not limited to, the following steps:
  • step S400 the NSMF records the instantiation information sent by the NSSMF.
  • Step S401 The NSMF sends a service access request to the NSSMF, where the service access request includes a network slice instance identifier, a network slice subnet template identifier, and a service access point information.
  • the service access point instantiation information includes local address information and peer address information of the service access point that the network slice subnet instance interfaces with other network slice subnet instances, and gateway router address information.
  • the gateway router IP address is also the next hop routing IP address.
  • the NSSI 1 service access point is connected to the NSSI 2 service access point.
  • the local IP address refers to the IP address of the service access point on NSSI 1
  • the peer IP address refers to The IP address of the service access point on NSSI 2.
  • the NSMF After receiving the instantiation information of the network slice subnet instance 1 and the network slice subnet instance 2, the NSMF sends a service access request to the NSSMF 1 , where the service access request carries the identifier of the network slice instance and the network slice subnet instance 1 corresponds to Network slice subnet template identification and service access point information 1.
  • the NSMF After receiving the instantiation information of the network slice subnet instance 1 and the network slice subnet instance 2, the NSMF sends a service access request to the NSSMF 2, where the service access request carries the identifier of the network slice instance and the network slice subnet instance 2 corresponds.
  • Network slice subnet template identification and service access point information 2 After receiving the instantiation information of the network slice subnet instance 1 and the network slice subnet instance 2, the NSMF sends a service access request to the NSSMF 2, where the service access request carries the identifier of the network slice instance and the network slice subnet instance 2 corresponds.
  • Network slice subnet template identification and service access point information 2 After receiving the instantiation information of the network slice subnet instance 1 and the network slice subnet instance 2, the NSMF sends a service access request to the NSSMF 2, where the service access request carries the identifier of the network slice instance and the network slice subnet instance 2 corresponds.
  • Network slice subnet template identification and service access point information 2 After receiving the instantiation information
  • step S401 corresponds to step S206a and step S206b in the embodiment shown in FIG. 2.
  • Step S402 The NSSMF generates a second service configuration file according to the network slice subnet template and the service access point information, where the second service configuration file is a service configuration file that is connected to the network slice subnet instance.
  • Step S403 the NSSMF sends a second service configuration file to its corresponding EMS.
  • Step S404 the EMS completes service configuration according to the first service configuration file and the second service configuration file.
  • the EMS1 corresponding to the NSSMF1 completes the service configuration according to the first service configuration file and the second service configuration file, that is, the service configuration and deployment of the network segmentation subnet instance is completed, so that the NSSI 1 can access the service and implement the service function.
  • Step S405 The NSSMF sends a service access confirmation message to the NSMF, where the service access confirmation message includes an identifier of the network slice subnet instance.
  • the NSSMF After the EMS completes the service configuration, the NSSMF sends a service access confirmation message to the NSMF, and carries the network slice subnet instance identifier to notify the NSMF that the corresponding network slice subnet instance has accessed the service. For example, the NSSI 1 has accessed the service.
  • step S405 corresponds to step S207a and step S207b in the embodiment shown in FIG. 2.
  • the NSSMF in the process shown in Figure 7 can be any NSSMF. If the network slicing instance consists of multiple network slicing subnet instances, there are multiple NSSMFs.
  • the service access instantiation process for each NSSMF can follow the above process. carried out.
  • FIG. 8 is a schematic diagram of a logical structure of a device provided by an embodiment of the present application.
  • the device 40 may include a processing unit 401 and a transceiver unit 402.
  • the device 40 can be NSMF or NSSMF or TN-manager in the embodiment shown in Figures 2, 5 and 7.
  • the transceiver unit 402 can be used to communicate with the CSMF, NSSMF and TN-manager, for example, performing step S201 in the embodiment shown in FIG. Step S312 (a or b), step S205 (a or b), step S206 (a or b), step S207 (a or b), step S209 and step S210, performing step S312 in the embodiment shown in FIG. Step S405 in the embodiment shown in FIG. 7 is executed.
  • the processing unit 401 can be used to perform an operation of controlling the NSMF, for example, performing step S202 and step S203 in the embodiment shown in FIG. 2. For details, refer to the corresponding description in the embodiment shown in FIG. 2, FIG. 5 and FIG. 7, which are not described herein again.
  • the transceiver unit 402 can be used to communicate with the NSMF, the TN-manager, the MANO, and the EMS, for example, in the embodiment shown in FIG. Step S204 (a or b), step S205 (a or b), step S206 (a or b) and step S207 (a or b), performing step S301, step S304, step S306 in the embodiment shown in FIG. 5, In step S307, step S308 and step S310, step S401, step S403 and step S405 in the embodiment shown in Fig. 7 are executed.
  • the processing unit 401 is configured to perform an operation of controlling the NSSMF, for example, performing step S302, step S303, and step S311 in the embodiment shown in FIG. 5, and performing step S402 in the embodiment shown in FIG.
  • step S302, step S303, and step S311 in the embodiment shown in FIG. 5, and performing step S402 in the embodiment shown in FIG. For details, refer to the corresponding description in the embodiment shown in FIG. 2, FIG. 5 and FIG. 7, which are not described herein again.
  • the transceiver unit 402 can be used to communicate with the NSMF and the NSSMF, for example, performing step S208 in the embodiment shown in FIG. Step S308 in the embodiment shown in FIG.
  • the processing unit 401 can be configured to perform an operation of controlling the TN-manager, for example, performing step S209 in the embodiment shown in FIG. 2, and performing step S309 in the embodiment shown in FIG.
  • FIG. 2 For details, refer to the corresponding description in the embodiment shown in FIG. 2, FIG. 5 and FIG. 7, which are not described herein again.
  • FIG. 9 is a simplified schematic diagram of a physical structure of a device according to an embodiment of the present disclosure.
  • the device 50 may be an NSMF or an NSSMF or a TN-manager in the embodiment shown in FIG. 2, FIG. 5, and FIG.
  • the device 50 includes a transceiver 501, a processor 502, and a memory 503.
  • the transceiver 501, the processor 502, and the memory 503 may be connected to one another via a bus 504, or may be connected in other manners.
  • Related functions implemented by the processing unit 401 shown in FIG. 8 may be implemented by one or more processors 502.
  • the related functions implemented by the transceiver unit 402 shown in FIG. 8 can be implemented by the transceiver 501.
  • the memory 503 includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read only memory (EPROM), or A compact disc read-only memory (CD-ROM) for use in related instructions and data.
  • RAM random access memory
  • ROM read-only memory
  • EPROM erasable programmable read only memory
  • CD-ROM compact disc read-only memory
  • the transceiver 501 is configured to transmit data and/or signaling, as well as receive data and/or signaling.
  • the processor 502 may include one or more processors, for example, including one or more central processing units (CPUs).
  • processors for example, including one or more central processing units (CPUs).
  • CPUs central processing units
  • the CPU may be a single core CPU, It can be a multi-core CPU.
  • the processor 502 is configured to support the NSMF to perform step S202 and step S203 in the embodiment shown in FIG. 2.
  • the processor 502 is configured to support the NSSMF to perform steps S302, S303, and S311 in the embodiment shown in FIG. 5 in the example shown in FIG. 2, and perform the steps in the embodiment shown in FIG. S402.
  • the processor 502 is configured to support the TN-manager to perform step S206 in the embodiment shown in FIG. 2, and perform step S309 in the embodiment shown in FIG.
  • the memory 503 is used to store program codes and data of the device 50.
  • the transceiver 501 is configured to communicate with other devices. If the device 50 is a CSMF, the transceiver 501 is configured to communicate with an NSMF entity, an operator, or a third party client; if the device is an NSMF, the transceiver 501 is configured to communicate with the CSMF, the NSSMF, and TN-manager communication; if the device is an NSSMF entity, the transceiver is used to communicate with NSMF, TN-manager, MANO, and EMS.
  • Figure 9 only shows a simplified design of the device.
  • the device may also include other necessary components, including but not limited to any number of transceivers, processors, controllers, memories, communication units, etc., and all devices that can implement the present application are in the present application. Within the scope of protection.
  • the embodiment of the present application further provides a network slice management system, including the NSMF, NSSMF, and CSMF shown in FIG. 1, and further includes TN-manager, MANO, EMS, and the like in the embodiments shown in FIG. 2, FIG. 5, and FIG. .
  • the program can be stored in a computer readable storage medium, when the program is executed
  • the flow of the method embodiments as described above may be included.
  • the foregoing storage medium includes various media that can store program codes, such as a ROM or a random access memory RAM, a magnetic disk, or an optical disk.
  • yet another embodiment of the present application provides a computer readable storage medium having instructions stored therein that, when executed on a computer, cause the computer to perform the methods described in the various aspects above.
  • Yet another embodiment of the present application also provides a computer program product comprising instructions that, when run on a computer, cause the computer to perform the methods described in the various aspects above.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in or transmitted by a computer readable storage medium.
  • the computer instructions may be from a website site, computer, server or data center via a wired (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) Another website site, computer, server, or data center for transmission.
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)) or the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例提供一种网络切片管理方法及其装置，其中方法包括：NSMF接收网络切片实例化请求，网络切片实例化请求包括网络切片需求信息；NSMF根据网络切片模板标识或网络切片类型获取网络切片模板；NSMF根据网络切片模板将网络切片需求信息分解为网络切片子网需求信息和传输网需求信息；NSMF向NSSMF发送网络切片子网实例化请求，网络切片子网实例化请求包括网络切片子网需求信息；NSMF接收网络切片子网管理功能实体发送的网络切片子网实例化响应；NSMF向TN-manager发送传输网实例化请求。本申请实施例采用网络切片模板对网络切片需求信息进行分解，可实现对网络切片的自动化管理。

Description

网络切片管理方法及其装置
本申请要求于2017年9月30日提交中国国家知识产权局、申请号为201710928212.X、发明名称为“网络切片管理方法及其装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域，具体涉及一种网络切片管理方法及其装置。
背景技术
随着多种多样的通信业务的不断涌现，不同的通信业务对网络性能的需求存在显著的区别，第五代移动通信(the 5th-generation，5G)系统引入了网络切片(network slice，NS)的概念，以应对不同通信业务对网络性能的需求的差异。
网络切片，指在物理或者虚拟的网络基础设施上，根据不同的服务需求定制化不同的逻辑网络。网络切片可以是一个包括了终端设备、接入网、传输网、核心网和应用服务器的完整的端到端网络，能够提供完整的通信服务，具有一定网络能力。网络切片也可以是终端设备、接入网、传输网、核心网和应用服务器的任意组合。
网络切片实例(network slice instance，NSI)是一个真实运行的逻辑网络，能够满足一定网络特性或服务需求。网络切片实例可以由网络切片模板(network slice template，NST)实例化得到。一个完整的网络切片实例可以提供完整的端到端的网络服务，网络切片实例的可以包括若干个网络切片子网实例(network slice subnet instance，NSSI)和/或若干个网络功能(network function，NF)。NSSI可以由网络切片子网模板(network slice subnet template，NSST)实例化得到。
网络切片管理的过程为：通信业务管理功能(communication service management function，CSMF)接收客户的业务需求，将业务需求转化成网络切片需求，将网络切片需求发送至网络切片管理功能(network slice management function，NSMF)；NSMF将接收到的网络切片需求转化为网络切片子网需求，并将网络切片子网需求发送至网络切片子网管理功能(network slice subnet management function，NSSMF)；NSSMF将网络切片子网需求转换为网络功能需求，将网络功能需求发送至管理编排器(management and orchestration，MANO)，由MANO根据网络功能的需求进行网络服务实例化。基于该管理过程，如何实现网络切片的自动化管理是亟待解决的问题。
发明内容
本申请实施例所要解决的技术问题在于，提供一种网络切片管理方法及其装置，采用网络切片模板对网络切片需求信息进行分解，可实现对网络切片的自动化管理。
本申请实施例第一方面提供一种网络切片管理方法，其特征在于，包括：
网络切片管理功能实体接收网络切片实例化请求，网络切片实例化请求包括网络切片需求信息，网络切片需求信息包括网络切片模板标识或网络切片类型，以及网络切片部署需求信息；
网络切片管理功能实体根据网络切片模板标识或网络切片类型信息获取网络切片模板；
网络切片管理功能实体根据网络切片模板将网络切片需求信息分解为网络切片模板包括的网络切片子网的网络切片子网需求信息和网络切片内的传输网需求信息；
对于网络切片包括的每一个网络切片子网，网络切片管理功能实体向网络切片子网管理功能实体发送网络切片子网实例化请求，网络切片子网实例化请求包括网络切片子网需求信息；
网络切片管理功能实体接收网络切片子网管理功能实体发送的网络切片子网实例化响应，网络切片子网实例化响应包括网络切片子网实例化信息，其中，网络切片子网实例化信息包括网络切片子网实例的标识、网络切片子网实例的业务接入点实例化信息和网络切片子网实例的网络连接点实例化信息；
网络切片管理功能实体向传输网管理器发送传输网实例化请求，传输网实例化请求包括网络切片内的传输网需求信息和所有网络切片子网实例的网络连接点信息；
网络切片管理功能实体根据各网络切片子网实例化后获得的业务接入点信息，触发建立各网络切片子网实例业务连接。
第二方面，本申请实施例提供一种网络切片管理功能实体，包括用于执行以上第一方面各个步骤的单元或手段(means)。
第三方面，本申请实施例提供一种网络切片管理功能实体，包括至少一个处理元件和至少一个存储元件，其中至少一个存储元件用于存储程序和数据，至少一个处理元件用于执行本申请第一方面中提供的方法。
第四方面，本申请实施例提供一种网络切片管理功能实体，包括用于执行以上第一方面的方法的至少一个处理元件(或芯片)。
第五方面，本申请实施例提供一种程序，该程序在被处理器执行时用于执行以上第一方面的方法。
第六方面，本申请实施例提供一种程序产品，例如计算机可读存储介质，包括第五方面的程序。
可见，在以上第一至第六方面，通过采用网络切片模板对网络切片需求信息进行分解，可实现对网络切片的自动化管理。
在一种可能实现的方式中，网络切片模板包括网络切片子网模板的标识、网络切片子网节点的网络连接点描述符、网络切片子网节点的业务接入点描述符、网络切片子网节点之间的网络连接描述符和网络切片子网节点之间的业务连接描述符。
其中，网络切片子网节点的网络连接点描述符用于描述网络切片子网节点的网络连接点信息，网络切片子网节点的业务接入点描述符用于描述网络切片子网节点的业务接入点信息，网络切片子网节点的网络连接点描述符用于描述网络切片子网节点的网络连接点信息，网络切片子网节点之间的网络连接描述符用于描述网络切片子网节点之间的网络连接信息，网络切片子网节点之间的业务连接描述符用于描述网络切片子网节点之间的业务连接信息。
在网络切片实例由网络切片子网实例构成的情况下，对网络切片模板所包括的内容进行了描述，以便网络切片管理功能实体根据网络切片需求信息确定各个组件所需的输入参数。
在一种可能实现的方式中，网络切片子网模板的标识对应的网络切片子网模板包括组成网络切片子网的网络功能节点的节点描述符、网络功能节点的网络连接点描述符、网络功能节点的业务接入点描述符、网络功能节点之间的网络连接描述符和网络功能节点之间的业务 连接描述符。定义了实例化网络切片子网所需的组件信息，即定义网络切片子网模板所包括的内容，以便网络切片子网管理功能实体根据网络切片子网需求信息确定各个组件所需的输入参数。
在一种可能实现的方式中，网络切片模板包括包括实例化网络功能所需的信息、网络功能节点的网络连接点描述符、网络功能节点的业务接入点描述符、网络功能节点之间的网络连接描述符和网络功能节点之间的业务连接描述符。
在网络切片实例由网络功能构成的情况下，对网络切片模板所包括的内容进行了描述，以便网络切片管理功能实体根据网络切片需求信息确定各个组件所需的输入参数。
在一种可能实现的方式中，在网络切片实例由网络功能构成的情况下，网络切片模板包括还包括组成网络切片的虚拟网络功能对应的网络服务描述符索引文件，网络服务描述符索引文件用于实例化虚拟网络功能的虚拟资源部署，以便网络切片管理功能实体生成网络服务描述符的实例化输入参数。
在一种可能实现的方式中，在网络切片实例由网络功能构成的情况下，网络切片模板包括还包括业务配置文件，业务配置文件用于网络功能的业务配置，以实现某个或某些业务功能。
在一种可能实现的方式中，网络切片管理功能实体向网络切片子网管理功能实体发送网络切片子网实例化请求之前，网络切片管理功能实体根据网络切片需求信息确定网络切片子网实例的部署区域，网络切片子网实例化请求还包括网络切片子网实例的部署区域，便于后续管理编排器能将网络切片子网实例对应的网络功能部署在正确区域的数据中心中。
在一种可能实现的方式中，网络切片子网需求信息还包括网络切片子网模板标识或网络切片类型，以便网络切片子网管理功能实体获取网络切片子网模板。
在一种可能实现的方式中，网络切片子网实例化请求还包括网络切片对应的网络切片实例的标识。
在一种可能实现的方式中，网络切片管理功能实体根据每个网络切片子网管理功能实体发送的实例化响应构建传输网络实例化请求，并向传输网络管理器发送传输网实例化请求。
在一种可能实现的方式中，网络切片管理功能实体根据各网络切片子网实例化后获得的业务接入点信息，向对应的网络切片子网管理功能实体发送业务接入请求，业务接入请求包括网络切片实例的标识、对应的网络切片子网模板的标识和对应的业务接入点信息，业务接入请求用于触发对应的网络切片子网关联功能实体建立业务连接。
本申请实施例第七方面提供一种网络切片管理方法，其特征在于，包括：
网络切片子网管理功能实体接收网络切片子网实例化请求，网络切片子网实例化请求包括网络切片子网需求信息；
网络切片子网管理功能实体获取网络切片子网模板；
网络切片子网管理功能实体根据网络切片子网模板将网络切片子网需求信息分解为网络切片子网模板包括的网络功能的网络服务需求信息、业务配置需求信息和所述网络切片子网内的传输网需求信息；
网络切片子网管理功能实体向网络切片管理功能实体发送网络切片子网实例化响应，网络切片子网实例化响应包括网络切片子网实例化信息，其中，网络切片子网实例化信息包括网络切片子网实例的标识、网络切片子网实例的业务接入点实例化信息和网络切片子网实例的网络连接点实例化信息；
网络切片子网管理功能实体向管理编排器发送网络服务实例化请求，网络服务实例化请求包括网络服务需求信息；
网络切片子网管理功能实体向网络切片子网管理功能实体对应的网元管理系统发送业务配置请求，业务配置请求包括业务配置需求信息；
网络切片子网管理功能实体向传输网管理器发送传输网实例化请求，传输网实例化请求包括网络切片子网内的传输网需求信息。
第八方面，本申请实施例提供一种网络切片子网管理功能实体，包括用于执行以上第七方面各个步骤的单元或手段(means)。
第九方面，本申请实施例提供一种网络切片子网管理功能实体，包括至少一个处理元件和至少一个存储元件，其中至少一个存储元件用于存储程序和数据，至少一个处理元件用于执行本申请第七方面中提供的方法。
第十方面，本申请实施例提供一种网络切片子网管理功能实体，包括用于执行以上第七方面的方法的至少一个处理元件(或芯片)。
第十一方面，本申请实施例提供一种程序，该程序在被处理器执行时用于执行以上第七方面的方法。
第十二方面，本申请实施例提供一种程序产品，例如计算机可读存储介质，包括第十一方面的程序。
可见，在以上第七至第十二方面，通过采用网络切片子网模板对网络切片子网需求信息进行分解，可实现对网络切片子网的自动化管理。
在一种可能实现的方式中，网络切片子网模板包括组成网络切片子网的网络功能节点的节点描述符、网络功能节点的网络连接点描述符、网络功能节点的业务接入点描述符、网络功能节点之间的网络连接描符和网络功能节点之间的业务连接描述符。
其中，网络功能节点的节点描述符用于描述实例化网络功能所需的信息，网络功能节点的网络连接点描述符用于描述网络功能节点的网络连接点信息，网络功能节点的业务接入点描述符用于描述网络功能节点的业务接入点信息，网络功能节点之间的网络连接描述符用于描述网络功能节点之间的网络连接信息，网络功能节点之间的业务连接描述符用于描述网络功能节点之间的业务连接信息。
上述对网络切片子网模板所包括的内容进行了描述，以便网络切片子网管理功能实体根据网络切片子网需求信息确定各个组件所需的输入参数。
在一种可能实现的方式中，网络切片子网模板还包括组成网络切片子网的虚拟网络功能对应的网络服务描述符索引文件，网络服务描述符索引文件用于实例化虚拟网络功能的虚拟资源部署。
在一种可能实现的方式中，网络切片子网模板还包括第一网络功能配置参数信息业务配置文件，第一业务配置文件用于网络功能的业务部署，第一业务配置文件为网络切片子网实例的非业务接入点配置文件。
在一种可能实现的方式，在网络切片子网模板包括组成网络切片子网的虚拟网络功能对应的网络服务描述符索引文件的情况下，网络切片子网管理功能实体根据网络切片子网模板所包括的各组件的输入参数生成网络服务描述符的实例化输入参数。
在一种可能实现的方式，在网络切片子网模板不包括组成网络切片子网的虚拟网络功能对应的网络服务描述符索引文件的情况下，网络切片子网管理功能实体根据网络切片子网模 板所包括的各组件的输入参数组成网络切片子网实例的虚拟网络功能对应的网络服务描述符文件。
在一种可能实现的方式中，在网络切片子网模板包括第一网络功能配置参数信息业务配置文件的情况下，网络切片子网管理功能实体根据网络切片子网模板所包括的各组件的输入参数生成第一业务配置文件的输入参数，第一业务配置文件为网络切片子网实例的非业务接入点配置文件。
在一种可能实现的方式中，在网络切片子网模板不包括第一网络功能配置参数信息业务配置文件的情况下，网络切片子网管理功能实体根据网络切片子网模板所包括的各组件的输入参数生成第一业务配置文件，第一业务配置文件用于网络功能的业务部署，第一业务配置文件为网络切片子网实例的非业务接入点配置文件。
在一种可能实现的方式中，网络切片子网管理功能实体根据网络切片子网模板获取网络切片子网实例与其它网络切片子网实例的网络连接点信息和网络切片子网实例与其它网络切片子网实例的业务接入点信息。
在一种可能实现的方式中，网络切片子网管理功能实体向网络切片管理功能实体发送网络切片子网实例化响应之后，从网络切片管理功能实体接收业务接入请求，业务接入请求包括网络切片子网模板的标识、网络切片实例的标识和业务接入点实例化信息，业务接入点实例化信息包括网络切片子网实例与其它网络切片子网实例对接的业务接入点的本端地址信息和对端地址信息，以及网关路由器地址信息；网络切片子网管理功能实体根据网络切片子网模板和业务接入点实例化信息生成第二业务配置文件，第二业务配置文件为网络切片子网实例与其它网络切片子网实例对接的业务配置文件。
在一种可能实现的方式中，网络切片子网实例化请求还包括网络切片子网实例的部署区域，网络服务实例化请求还包括网络切片子网实例的部署区域。
在一种可能实现的方式中，网络切片子网需求信息包括网络切片子网模板标识或网络切片类型，网络切片子网管理功能实体根据网络切片子网模板标识或网络切片类型获取网络切片子网模板。
本申请实施例第十三方面提供一种网络切片管理方法，其特征在于，包括：
管理编排器接收传输网实例化请求，传输网实例化请求包括传输网需求信息；
管理编排器根据传输网需求信息进行传输络实例化；
管理编排器发送传输网实例化响应。
第十四方面，本申请实施例提供一种管理编排器，包括用于执行以上第十三方面各个步骤的单元或手段(means)。
第十五方面，本申请实施例提供一种管理编排器，包括至少一个处理元件和至少一个存储元件，其中至少一个存储元件用于存储程序和数据，至少一个处理元件用于执行本申请第十三方面中提供的方法。
第十六方面，本申请实施例提供一种管理编排器，包括用于执行以上第十三方面的方法的至少一个处理元件(或芯片)。
第十七方面，本申请实施例提供一种程序，该程序在被处理器执行时用于执行以上第十三方面的方法。
第十八方面，本申请实施例提供一种程序产品，例如计算机可读存储介质，包括第十七方面的程序。
可见，在以上第十三至第十八方面，管理编排器可根据接收到的传输网需求信息进行传输网实例化，既可实现对构成网络切片实例的网络切片子网实例组成的传输网的实例化，也可实现对构成网络切片子网实例的网络功能组成的传输网的实例化。
本申请实施例还提供一种网络切片管理系统，包括网络切片管理功能实体、网络切片子网管理功能实体和传输网管理器。
附图说明
为了更清楚地说明本申请实施例或背景技术中的技术方案，下面将对本申请实施例或背景技术中所需要使用的附图进行说明。
图1为应用本申请实施例的网络架构示意图；
图2为本申请实施例提供的一种网络切片管理方法的流程示意图；
图3为本申请实施例提供的网络切片模板的组成示意图；
图4为本申请实施例提供的网络连接和业务连接的示意图；
图5为本申请实施例提供的一种网络切片子网实例化的流程示意图；
图6为本申请实施例提供的网络切片子网模板的组成示意图；
图7为本申请实施例提供的一种业务连接实例化的流程示意图；
图8是本申请实施例提供的设备的逻辑结构示意图；
图9是本申请实施例提供的设备的实体结构简化示意图。
具体实施方式
5G中，多样化的业务需求对网络在速度、性能、安全、可靠性、时延等方面的需求各不相同。例如，增强移动宽带(enhanced mobile broadband，eMBB)场景(例如虚拟现实，增强现实等场景)，对带宽要求较高，需要xGbps的带宽。再例如，海量机器类通信(massive machine type communication，mMTC)场景(例如可穿戴场景，智能电网等场景)，需要支持海量的设备接入，例如需要支持数亿或数十亿的设备接入。再例如，超可靠低时延(ultra-reliable and low latency communications，uRLLC)场景(例如自动驾驶，远程手术，工业控制等场景)，需要支持1ms的超低时延。面对不同的场景、不同的要求以及极致体验的需求，网络切片应运而生，它可以基于5G场景和需求灵活构建不同特征的网络。
网络切片技术是将网络在逻辑上抽象为一个或者多个相互隔离的网络切片，其中每个网络切片包含一系列的逻辑网络功能，针对性地满足不同业务类型的差异化需求。
网络切片技术将5G网络物理基础设施资源根据场景需求抽象为多个相互独立的平行的网络切片实例。每个网络切片实例按照业务场景的需要和业务模型进行网络功能的定制裁剪及相应网络功能的编排管理。一个网络切片实例可以视为一个实例化的5G网络。这样的网络结构允许运营商将网络作为一种服务提供给用户，并可以根据速率、容量、覆盖性、延迟、可靠性、安全性和可用性等指标对实体网络进行自由组合，从而满足不同用户的要求。
不同的网络切片可以提供不同的网络功能。例如，针对移动智能终端(例如手机)进行通信的场景，可以使用独立的网络切片。再例如，针对车联网场景，由于有超低时延要求，主要给自动驾驶业务使用，对网络的处理时延和可靠性有比较高的要求，也可以使用独立的网络切片。再例如，针对mMTC场景，由于接入设备数量较大，但接入设备发送的报文会比较小，对网络时延的要求也比较小，也可以采用独立的网络切片。由于不同的网络切片需要提 供的功能和业务质量要求不相同，因此不同的网络切片可以部署不同网络功能。
下面将对本申请实施例涉及的术语或名称进行介绍：
网络切片：部署在物理或者虚拟的基础设施上的，用于支持特定网络能力与网络特性的逻辑隔离的网络，可以包括接入网、传输网、核心网和应用服务器在内的完整的端到端(end to end，E2E)的整个网络，部分网络功能也可以在多个网络切片中共享，是满足第三代合作伙伴计划(3rd generation partnership project，3GPP)提出的第五代(5th generation，5G)移动通信技术关于网络差异化需求的关键技术。通常，不同网络切片的网络特征并不相同，且要求网络切片之间相互隔离，互不影响。如增强实现(augmented reality，AR)或虚拟实现(virtual reality，VR)业务的网络切片要求大带宽、低时延；物联网(internet of things，IOT)业务的网络切片要求支持海量终端接入，但带宽小，对时延没要求。网络切片也可以是终端设备、接入网、传输网、核心网和应用服务器的任意组合。
网络切片实例是一个真实运行的逻辑网络，能满足一定网络特性或服务需求。一个网络切片实例可能提供一种或多种网络服务。网络切片实例可以由网络切片管理系统创建，一个网络切片管理系统可能创建多个网络切片实例并同时对它们进行管理。网络切片实例可从网络切片模板创建。
网络切片模板(network slice template，NST)，用于创建网络切片实例。
一个完整的网络切片实例是能够提供完整的端到端的网络服务的，而组成网络切片实例的可以是网络切片子网实例和/或网络功能。其中网络切片子网实例可以不需要提供端到端的完整的网络服务，网络切片子网实例可以是网络切片实例中同一个设备商的网络功能组成集合，也可能是按域划分的网络功能的集合，例如核心网网络切片子网实例、接入网网络切片子网实例。网络切片子网实例可能被多个网络切片实例共享。一个网络切片实例可能由若干网络切片子网实例组成，每个网络切片子网实例由若干网络功能和/或其他网络切片子网实例组成；一个网络切片实例可能由若干网络切片子网实例和没有被划分为网络切片子网实例的网络功能直接组成；一个网络切片实例也可能仅由若干网络功能组成。
网络切片子网模板(network slice subnet template，NSST)，用于创建网络切片子网实例。
网络功能，一个网络功能相当于提供了一种网络服务定义了功能性的行为和接口。比如在5G网络中，网络功能可以包括会话管理功能(session management function，SMF)，策略控制功能(policy control function，PCF)，用户面功能(user plane function，UPF)，演进型基站(evolved nodeB，eNB)或5G基站(新空口(new radio，NR)nodeB，gNB)，接入和移动性管理功能(access and mobility management function，AMF)和网络存储功能(network repository function，NRF)，等等。其中，SMF用于提供会话管理服务，PCF用于提供策略控制服务，UPF用于提供用户面服务，AMF用于提供接入和移动性管理服务，eNB或gNB(以下以eNB为例进行说明)用于提供无线接入服务，NRF用于提供服务发现。网络功能可以通过专用硬件实现，也可以通过在专用硬件上运行软件实现，也可以在通用的硬件平台上以虚拟功能的形式实现。因此，从实现的角度，可以将网络功能分为物理网络功能(physical network function，PNF)和虚拟网络功能(virtualised network function，VNF)。而从使用的角度，网络功能可以分为专属网络功能和共享网络功能，具体地，对于多个(子)网络切片实例而言，可以独立地使用不同的网络功能，这种网络功能称为专属网络功能；也可以共享同一个网络功能，这种网络功能称为共享网络功能。以下统称物理网络功 能和/或虚拟网络功能为网络功能。
网络功能虚拟化基础设施(network functions virtualisation infrastructure，NFVI)，从云计算的角度看，就是一个资源池。NFVI映射到物理基础设施就是多个地理上分散的数据中心(date center，DC)，通过高速通信网连接起来。NFVI需要将物理计算/存储/交换资源通过虚拟化转换为虚拟的计算/存储/交换资源池。
管理编排器(management and orchestration，MANO)负责对整个NFVI资源的管理和编排，负责业务网络和NFVI资源的映射和关联，负责运营支撑系统(Operation support system，OSS)业务资源流程的实施等。
网络切片和网络切片子网要进行实例化部署，需要MANO完成对网络服务(network service，NS)的实例化，网络服务的实例化主要向NFVI申请网络切片或网络切片子网实例化所需要的虚拟资源。
网络服务描述符(network service descriptor，NSD)，用于描述实例化网络服务的网络拓扑以及需要的资源信息。MANO可根据NSD实例化网络服务。
网元管理系统(element management system，EMS)，是网络功能的网元管理系统，用于向网络功能下发网络功能的业务配置。
请参见图1，为应用本申请实施例的网络架构示意图，该网络架构包括通信业务管理功能(communication service management function，CSMF)、网络切片管理功能(network slice management function，NSMF)和网络切片子网管理功能(network slice subnet management function，NSSMF)。需要说明的是，网络架构所包括的CSMF、NSMF以及NSSMF的数量并不局限于图1所示，实际应用中，可能包括多个CSMF、多个NSMF、多个NSSMF。需要说明的是，上述三个管理功能可能用其他名称进行描述，本申请实施例对此不作限定。运营商通过本申请实施例提供的方案，可以为用户提供一个网络切片实例，从而为用户提供特定的通信服务，如高清视频等。
具体的，用户可以跟运营商通过协商确定相应的通信服务需求，例如网络服务需要覆盖的范围、用户的数量以及用户分布、移动性要求、时延要求以及网络切片是否需要与其他网络切片进行隔离等等。
CSMF主要负责将运营商和/或第三方客户的通信服务需求转化为对网络切片需求信息，所述网络切片需求信息包括网络切片类型/切片模板标识ID和网络切片部署需求信息(例如网络的容量、服务质量QoS需求等)；通过和NSMF之间的接口向NSMF发送所述网络切片需求信息；从NSMF获取网络切片的管理数据(例如性能、故障数据等)；生成运行于网络切片实例之上的通信业务的管理数据；接收运营商和/或第三方客户对网络切片管理数据和/或通信业务的管理数据的订阅需求等。
NSMF主要负责接收CSMF发送的网络切片需求信息；对网络切片实例的生命周期、性能、故障等进行管理(以下将生命周期、性能、故障管理简称管理)；编排网络切片实例的组成；分解网络切片需求信息为各网络切片子网实例和/或网络功能的需求信息，以及传输网(transport network，TN)需求；向各NSSMF发送网络切片子网实例化请求，向传输网管理器(TN-manager)发送传输网需求等。
NSSMF主要负责接收NSMF发送的网络切片子网需求；对网络切片子网实例进行管理；编排网络切片子网实例的组成；分解网络切片子网实例的需求为各网络功能和/或嵌套网络切片子网实例的需求；可能向其他NSSMF发送嵌套网络切片子网实例化请求，可能管理嵌套网络 切片子网实例等。
需要说明的是，网络功能管理实体、网络功能管理和NSMF在本申请实施例中可以互换，三个词均用于描述负责接收CSMF发送的网络切片需求的实体，并不构成对本申请实施例的限定。同理NSSMF、CSMF。
基于目前的网络切片管理过程，如何实现网络切片的自动化管理是亟待解决的问题。鉴于此，本申请实施例提供一种网络切片管理方法及其装置，采用网络切片模板对网络切片需求进行分解，可自动化地实现网络切片管理。
请参见图2，为本申请实施例提供的一种网络切片管理方法的流程示意图，该方法从NSMF与NSSMF、TN-manager交互的角度进行介绍，其中TN-manager用于负责网络切片子网节点间以及网络切片子网节点内不同网络功能之间的传输网的实例化管理。图2所示的方法以一个网络切片实例由两个网络切片子网实例组成，NSSMF 1可实例化得到网络切片子网实例1(NSSI-1)，NSSMF 2可实例化得到网络切片子网实例(NSSI-2)为例，图2所示的方法可以包括但不限于以下步骤：
步骤S200，生成网络切片模板。
NSMF在接收网络切片实例化请求之前，切片涉及人员(例如切片提供商)进行网络切片模板的设计，生成网络切片模板，并将网络切片模板上传(on-boarding)至NSMF。NSMF可以记录、保存网络切片模板与网络切片需求信息的对应关系，其中网络切片需求信息包括网络切片模板的标识或者网络切片类型。网络切片类型用于表征切片所提供的网络服务的类型，例如可以是高清视频服务类、车联网类等。上传网络切片模板至NSMF是本申请实施例实施的前提条件。
网络切片模板的组成示意图可参见图3所示，网络切片模板用于描述实例化网络切片所需的组件信息，包括组成网络切片的节点的节点描述信息和节点之间的连接描述信息。节点可以是网络切片子网节点或网络功能节点。
在网络切片实例由网络切片子网实例组成的情况下，节点描述信息包括网络切片子网节点描述符(NSS node descriptor)、网络切片子网节点的网络连接点描述符(network connection point descriptor)和网络切片子网节点的业务接入点描述符(service access point descriptor)，连接描述信息包括网络切片子网节点之间的业务连接描述符(service connection descriptor)和网络切片子网节点之间的网络连接描述符(network connection descriptor)。
在网络切片实例可由网络功能组成的情况下，节点描述信息还包括网络功能节点描述符(NF node descriptor)、网络功能节点的网络连接点描述符和网络功能节点的业务接入点描述符，连接描述信息还包括不同网络功能节点之间的网络连接描述符和网络功能节点之间的业务连接描述符。其中，网络功能节点可以是虚拟网络功能节点(VNF node)，也可以是物理网络功能节点(PNF node)。
假设一个网络切片包括两个网络切片子网，这两个网络切片子网对应的节点分别为接入网(access network，AN)节点和核心网(core network，CN)节点，接入网节点(AN node)与核心网节点(CN node)之间有网络连接和业务连接。网络连接用于描述两个节点之间的物理连接，即这两个节点在物理上连接，若需实现这两个节点之间的业务交互(如相互传递业务报文)，则需实现业务连接。
请参见图4，为基于这个假设所示的网络连接、业务连接的示意图。其中，节点上灰色 点为业务接入点，黑色点为网络连接点。AN node的网络连接点1与CN node的网络连接点1通过实线相连，表明AN node与CN node之间存在网络连接，即图4所示的实线为AN node与CN node之间的网络连接，网络连接用于承载AN与CN之间的网络连接信息。AN node的业务接入点1与CN node的业务接入点1通过长虚线相连，表明AN node与CN node之间存在业务连接，即图4所示的长虚线为AN node与CN node之间的业务连接，业务连接用于承载AN与CN之间的业务互通信息。
其中，AN node的业务接入点依赖于其网络连接点，CN node的业务接入点依赖于其网络连接点。需要说明的是，图4所示的一个节点上存在一个网络连接点和一个业务接入点，并不构成对本申请实施例的限定，实际应用中，一个节点上存在多个网络连接点和多个业务接入点。
一个节点的网络连接点可以与其它节点的网络连接点进行网络连接，即一个网络切片子网节点的网络连接点可以与其它网络切片子网节点的网络连接点进行网络连接，也可以与应用服务器或应用软件的网络连接点进行网络连接。
可选的，一个网络切片实例中的不同节点可以通过网络连接点连接到一个连通的网络中，从而实现节点的网络连接。
一个节点的业务接入点可以与其它节点的业务接入点进行业务连接，即一个网络切片子网节点的业务接入点可以与其它网络切片子网节点的业务接入点进行业务连接，也可以与应用服务器或应用软件的业务接入点进行业务连接。
网络切片子网节点描述符包括实例化网络切片子网所需的组件信息，实例化网络切片子网所需的组件信息包括组成网络切片子网的网络功能节点的节点描述符、网络功能节点的网络连接点描述符、网络功能节点的业务接入点描述符、网络功能节点之间的网络连接描述符和网络功能节点之间的业务连接描述符。可以理解的是，网络切片子网节点描述符用于描述实例化网络切片子网需要的信息。
网络切片子网节点之间的业务连接描述符，用于描述图4中AN node与CN node之间的业务连接信息，即用于描述网络切片子网节点之间的业务连接信息。业务连接信息可以包括业务连接协议、业务连接相关参数等信息。可以理解的是，网络切片子网节点之间的业务连接描述符用于描述网络切片子网节点之间通过何种业务连接协议、哪些业务连接相关参数等信息进行业务连接。
网络切片子网节点之间的网络连接描述符，用于描述图4中AN node与CN node之间的网络连接信息，即用于描述网络切片子网节点之间的网络连接信息。网络连接信息可以包括网络平面的服务质量(quality of service，QoS)信息、互联网协议(Internet protocol，IP)类型等信息。可以理解的是，网络切片子网节点之间的的网络连接描述符用于描述网络切片子网节点之间采用哪些网络连接信息进行网络连接。
网络切片子网节点的业务接入点描述符，用于描述该网络切片子网节点的业务接入点信息。该业务接入点信息可以是该网络切片子网节点与网络切片以外的设备进行业务连接的业务接入点的信息，还可以是该网络切片子网节点与应用服务器或应用软件进行业务连接的业务接入点的信息。其中，业务接入点信息可以包括业务接入点的业务IP地址等信息等信息。若该网络切片子网节点上有多个业务接入点，那么可以每个业务接入点对应一个业务接入点描述符。
网络切片子网节点的网络连接点描述符，用于描述该网络切片子网节点的网络连接点信 息。该网络连接点信息可以是网络切片子网节点与其它网络切片子网节点进行网络连接的网络连接点的信息，还可以是网络切片子网节点与网络切片以外的设备进行网络连接的网络连接点的信息。其中，网络连接点信息可以包括网络连接点的物理IP地址等信息等信息。若该网络切片子网节点上有多个网络连接点，那么可以每个网络连接点对应一个网络连接点描述符。
其中，网络切片子网节点为组成网络切片的网络切片子网的节点。
上述物理IP地址可以理解为物理接口IP地理，业务IP地址是同其他网元进行业务交互的IP地址。但业务IP报文要从物理接口发出。
可以理解的是，在网络切片实例由网络切片子网实例构成的场景中，节点描述信息包括实例化网络切片子网所需的组件信息、网络切片子网节点的网络连接点描述符和网络切片子网节点的业务接入点描述符，连接描述信息包括网络切片子网节点之间的网络连接描述符和网络切片子网节点之间的业务连接描述符。
在网络切片实例可由网络功能构成的场景中，节点描述信息可包括图3中虚线方框所示的网络功能节点描述符、网络功能节点的网络连接点描述符和网络功能节点的业务接入点描述符。连接描述信息可包括网络功能节点之间的网络连接描述符和网络功能节点之间的业务描述符。其中，网络功能节点描述符用于描述实例化网络功能所需的信息。网络功能节点的网络连接点描述符、网络功能节点的业务接入点描述符、网络功能节点之间的网络连接描述符和网络功能节点之间的业务描述符分别与上述网络切片子网节点的网络连接点描述符、网络切片子网节点的业务接入点描述符、网络切片子网节点之间的网络连接描述符和网络切片子网节点之间的业务描述符类型，在此不再赘述。
在网络切片实例可由网络功能构成的场景中，网络切片模板可包括图3中虚线方框所示的业务配置文件，业务配置文件用于网络功能的业务配置。可以理解的是，该业务配置文件指示网络功能要实现哪些业务功能。
若网络切片实例可由虚拟网络功能组成，则网络切片模板可包括图3中虚线方框所示的网络服务描述符(NSD)索引文件，可以是NSD ID。网络服务描述符用于实例化关联网络功能的虚拟资源部署，关联网络功能为组成所述网络切片的虚拟网络功。可以理解的是，该种情况下，MANO可根据网络服务描述符ID索引对应的NSD文件，完成关联网络功能的虚拟资源部署，该虚拟资源可以包括虚拟内存资源、虚拟中央处理器(central processing unit，CPU)等。
步骤S201，NSMF接收网络切片实例化请求，网络切片实例化请求包括网络切片需求信息，网络切片需求信息包括网络切片模板标识或网络切片类型。
网络切片的订购者，例如运营商、第三方客户等，可以通过业务支持系统(business support system，BSS)的操作界面进行网络切片订购，即在BSS的操作界面输入业务需求。该业务需求可以包括业务类型，还可以包括服务等级协议(service-level agreement，SLA)需求，SLA为网络服务供应商和客户间的一份合同，SLA需求可以包括用户数量、带宽需求和时延保障需求等。可以理解的是，业务需求包括业务类型和SLA需求。
CSMF(或BSS-CSMF)在接收到业务需求的情况下，将业务需求转换为网络切片需求信息，具体包括业务类型转换和SLA需求转换。业务类型转换即将业务需求中的业务类型转换为网络切片类型，例如，转换为eMBB网络切片、uRLLC网络切片、mMTC网络切片等。可选地，此时CSMF还可根据网络切片类型查找该网络切片类型对应的网络切片模板标识(NST ID)。SLA 需求转换即将SLA需求转换为网络切片部署需求信息，该网络切片部署需求信息可以包括用户数量、带宽和时延等需求。换言之，网络切片部署需求信息用于描述用户数量、带宽和时延等需求信息。
可以理解的是，网络切片需求信息包括网络切片类型和网络切片部署需求信息，网络切片类型用于指示网络切片类型，可根据网络切片类型确定网络切片模板标识；或网络切片需求信息包括网络切片模板标识和网络切片部署需求信息，网络切片模板标识用于指示网络切片模板。
可以理解的是，网络切片需求信息可为网络切片的实例化提供输入参数。
CSMF向NSMF发送网络切片实例化请求，网络切片实例化请求包括网络切片需求信息，网络切片需求信息包括网络切片模板标识或网络切片类型，以及网络切片部署需求信息。相应地，NSMF从CSMF接收网络切片实例化请求。网络切片实例化请求可以是初始实例化请求，即请求实例化出当前系统中不存在的网络切片实例。
步骤S202，NSMF根据网络切片模板标识或网络切片类型获取网络切片模板。
在一种实现方式中，NSMF根据网络切片模板标识获取网络切片模板标识对应的网络切片模板，一个网络切片模板标识对应一个网络切片模板。
在一种实现方式中，NSMF根据网络切片类型获取网络切片类型对应的网络切片模板，一个网络切片类型对应一个网络切片模板。具体地，根据网络切片类型查找网络切片类型对应的网络切片模板标识，再根据网络切片模板标识获取网络切片模板。
此时，NSMF还可以为网络切片模板对应的网络切片实例分配标识，即分配网络切片实例标识(NSI ID)。一个网络切片模板实例化一次即可得到一个网络切片实例。
步骤S203，NSMF根据网络切片模板将网络切片需求信息分解为网络切片子网需求信息1、网络切片子网需求2和传输网需求信息。
NSMF根据网络切片模板所包括的内容对网络切片需求信息进行分解，分解为节点描述信息对应的网络切片子网需求信息和连接描述信息对应的传输网需求信息。节点描述信息对应的网络切片子网需求信息包括网络切片子网节点1的节点描述信息对应的网络切片子网需求信息1和网络切片子网节点2的节点描述信息对应的网络切片子网需求信息2。
其中，网络切片子网需求信息1包括网络切片子网模板标识(NSST ID)、实例化网络切片子网1所需的输入参数、网络切片子网节点1的网络连接点信息和网络切片子网节点1的业务接入点信息。传输网需求信息包括网络切片子网节点1与网络切片子网节点2之间的网络连接信息。网络切片子网需求信息2包括网络切片子网模板标识(NSST ID)、实例化网络切片子网2所需的输入参数、网络切片子网节点2的网络连接点信息和网络切片子网节点2的业务接入点信息。传输网需求信息包括网络切片子网节点2与网络切片子网节点2之间的网络连接信息。
可以理解的是，网络切片子网需求信息为网络切片子网的实例化提供输入参数，包括为网络切片子网的实例化提供输入参数、为网络切片子网节点的网络连接点提供网络连接点信息、为网络切片子网节点的业务接入点提供业务接入点信息。传输网连接信息为传输网的实例化提供输入参数，包括为网络切片子网节点之间的网络连接提供网络连接输入参数。
可以理解的是，网络切片模板定义实例化网络切片需要哪些组件以及组件需要的输入参数，网络切片需求信息可以提供输入参数，NSMF可以根据网络切片模板对网络切片需求信息进行分解，即根据各个组件需要的输入参数为各个组件提供相应地输入参数。
在分解之后，NSMF根据网络切片需求信息确定NSSI-1和NSSI-2的部署区域，即确定各个NSSI的部署地方。这样便于后续MANO能将网络切片子网实例对应的网络功能部署在正确区域的数据中心(DC)中。
若网络切片实例由网络功能构成，则NSMF根据网络切片模板将网络切片需求信息分解为业务配置需求信息、网络服务需求信息和网络切片内的网络功能的传输网需求信息。这三个信息可参见图6所示实施例中的描述。
步骤S204a：NSMF向NSSMF 1发送网络切片子网实例化请求1，网络切片子网实例化请求1包括网络切片子网需求信息1。相应的，NSSMF 1从NSMF接收网络切片子网实例化请求1。
步骤S204b：NSMF向NSSMF 2发送网络切片子网实例化请求2，网络切片子网实例化请求2包括网络切片子网需求信息2。相应的，NSSMF 2从NSMF接收网络切片子网实例化请求1。
具体地，NSMF向各个NSSMF发送网络切片子网实例化请求，在网络切片子网实例化请求中携带对应的网络切片子网需求信息。例如，网络切片由网络切片子网1和网络切片子网2构成，NSMF向NSSMF 1发送网络切片子网实例化请求1，携带网络切片子网1的需求信息；NSMF向NSSMF 2发送网络切片子网实例化请求2，携带网络切片子网2的需求信息。
NSSMF1根据NSST 1对网络切片子网1的需求信息进行分解，得到网络服务需求信息1、业务配置需求信息1和传输网需求信息1，向MANO发送网络服务需求信息1，向NSSMF1对应的EMS 1发送业务配置需求信息1，向TN-manager发送传输网需求信息1。NSSMF 2根据NSST2对网络切片子网2的需求信息进行分解，得到网络服务需求信息2、业务配置需求信息2和传输网需求信息2，向MANO发送网络服务需求信息2，向NSSMF2对应的EMS 2发送业务配置需求信息2，向TN-manager发送传输网需求信息2。
网络切片子网实例化请求还包括对应的网络切片子网实例的部署区域，以便后续MANO能将该网络切片子网实例对应的网络功能部署在正确区域的DC中。例如，网络切片子网实例化请求1还包括NSSI-1的部署区域，网络切片子网实例化请求还包括NSSI-2的部署区域。
网络切片子网实例请求还可包括网络切片对应的网络切片实例的标识(NSI ID)。
网络切片子网需求信息还可包括对应的网络切片子网模板标识或网络切片类型信息。
步骤S205a，NSSMF 1向NSMF发送网络切片子网实例化响应1，网络切片子网实例化响应1包括实例化信息1，相应的，NSMF从NSSMF 1接收网络切片子网实例化响应1。
步骤S205b，NSSMF 2向NSMF发送网络切片子网实例化响应2，网络切片子网实例化响应2包括实例化信息2，相应的，NSMF从NSSMF 2接收网络切片子网实例化响应2。
NSSMF 1在完成网络服务1的实例化之后，向NSMF发送实例化信息1。NSSMF 2在完成网络服务2的实例化之后，向NSMF发送实例化信息2。
其中，实例化信息1包括网络切片子网实例1的标识(NSSI-1ID)、网络切片子网实例1的网络连接点实例化信息以及网络切片子网实例1的业务接入点实例化信息。
NSSI-1的网络连接点实例化信息包括NSSI-1与NSSI-2对接的网络连接点的本端IP地址等信息，还包括NSSI-1与外部接入设备对接的网络连接点的IP地址等信息。同理可定义NSSI-2的网络连接点实例化信息。
NSSI-1的业务接入点实例化信息包括NSSI-1与NSSI-2对接的业务接入点的本端IP地址，还包括NSSI-1与外部接入设备对接的业务接入点的IP地址等信息。同理可定义NSSI-2 的业务接入点实例化信息。
其中，接入设备信息可以是网络切片子网实例部署的DC中的网关路由器同传输交换机对接的信息，包括接入设备标识和端口标识等。
对NSSI 1而言，本端IP地址指的是NSSI-1上的IP地址，对端IP地址指的是NSSI-2的IP地址。
NSMF可对各个NSSMF发送的实例化信息进行记录、存储。
需要说明的是，步骤S204a和步骤S205a，步骤S204b和步骤S205b为网络切片子网实例化的流程，具体可参见图5的描述。
步骤S206a，NSMF向NSSMF 1发送业务接入请求1，相应的，NSSMF 1从NSMF接收业务接入请求1。
步骤S206b，NSMF向NSSMF 2发送业务接入请求2，相应的，NSSMF 2从NSMF接收业务接入请求2。
在步骤S205a和步骤S205b之后执行步骤S206a和步骤S206b。
业务接入请求包括网络切片实例标识、网络切片子网模板标识和业务接入点信息。业务接入点实例化信息包括网络切片子网实例与其它网络切片子网实例对接的业务接入点的本端IP地址等信息和对端IP地址等信息，以及网关路由器IP地址等信息。网关路由器IP地址也即下一跳路由IP地址。以NSSI-1的业务接入点与NSSI-2的业务接入点对接为例，对NSSI-1而言，本端IP地址指的是NSSI-1上的业务接入点的IP地址，对端IP地址指的是NSSI-2上的业务接入点的IP地址。
NSMF在接收到实例化信息1和实例化信息2之后，向NSSMF 1发送业务接入请求1，业务接入请求1携带网络切片实例的标识、网络切片子网实例1对应的网络切片子网模板标识和业务接入点信息1。
NSMF在接收到实例化信息1和实例化信息2之后，向NSSMF 2发送业务接入请求2，业务接入请求携带网络切片实例的标识、网络切片子网实例2对应的网络切片子网模板标识业务接入请求2携带网络切片实例的标识、网络切片子网实例2对应的网络切片子网模板标识和业务接入点信息2。
步骤S207a，NSSMF 1向NSMF发送业务接入确认消息1，相应的，NSMF从NSSMF 1接收业务接入确认消息1。
步骤S207b，NSSMF 2向NSMF发送业务接入确认消息2，相应的，NSMF从NSSMF 2接收业务接入确认消息2。
在EMS完成业务配置之后，NSSMF向NSMF发送业务接入确认消息，携带网络切片子网实例标识，以通知NSMF，相应的网络切片子网实例已接入业务，例如，业务接入确认消息1用于通知NSSI-1已接入业务，业务接入确认消息2用于通知NSSI-2已接入业务。
需要说明的是，步骤S206a和步骤S207a，步骤S206b和步骤S207b为业务接入实例化的流程，具体可参见图7的描述。
步骤S208，NSMF向TN-manager发送传输网实例化请求。相应的，TN-manage从NSMF接收发送传输网实例化。
需要说明的是，步骤S208在步骤S205a和步骤S205b之后执行。步骤S208可与步骤S206a和步骤S206b同时执行。
NSMF根据各个NSSMF发送的实例化信息创建各个网络切片子网实例之间的传输网实例化 请求，例如创建NSSI-1和NSSI-2之间的传输网实例化请求。
以两个网络切片子网实例为例，传输网实例化请求包括NSSI-1与NSSI-2进行网络连接IP地址等信息(即两端的IP地址)(即网络切片子网节点1与网络切片子网节点2对接的网络连接IP地址等信息)、NSSI-1网络切片子网实例1与NSSI-2网络切片子网实例2进行网络连接的QoS信息(即网络切片子网节点1与网络切片子网节点2进行网络连接的QoS信息)。传输网实例化请求还包括以及NSSI-1网络切片子网实例1与NSSI-2网络切片子网实例2对接的接入设备信息，接入设备信息可以是网络切片子网实例部署的DC中的网关路由器同传输交换机对接的信息，包括接入设备标识和端口标识等。
NSMF可根据导入全网数据中心和传输网拓扑图，查找部署位置对应的接入设备信息。
步骤S209，TN-manager根据传输网实例化请求进行传输网实例化。
TN-manager在接收到传输网实例化请求的情况下，根据传输网需求信息进行传输网实例化，建立网络切片子网实例之间的网络连接，还可建立网络切片子网实例与接入设备之间的网络连接。
步骤S210，TN-manager向NSMF发送确认消息。
在TN-manager完成传输网的实例化之后，向NSMF反馈确认消息，通知已完成传输网的实例化。
在图2所示的实施例中，NSMF采用网络切片模板对网络切片需求信息进行分解，分解为网络切片子网需求信息和传输网需求信息，以便NSSMF进行网络服务的实例化和业务连接的实例化，以便TN-manager进行传输网的实例化。
请参见图5，为本申请实施例提供的一种网络切片子网实例化的流程示意图，该流程从NSMF与NSSMF、MANO交互的角度进行介绍，以一个NSSMF为例进行介绍。图5所示的流程可以包括但不限于以下步骤：
步骤S300，生成网络切片子网模板；
切片涉及人员(例如切片提供商)进行网络切片子网模板的设计，生成网络切片子网模板，并将网络切片子网模板上传至NSSMF。NSSMF可以记录、保存网络切片子网模板与网络切片子网需求信息的对应关系，其中网络切片子网需求信息包括网络切片子网模板的标识或者网络切片类型。网络切片类型用于表征切片所提供的网络服务的类型，例如可以是高清视频服务类、车联网类等。
网络切片子网模板的组成示意图可参见图6所示，网络切片子网模板用于描述实例化网络切片子网所需的组件信息，包括组成网络切片子网的网络功能节点的节点描述信息和网络功能节点之间的连接描述信息，具体包括每个网络功能节点的节点描述信息和节点之间的连接描述信息。
网络功能节点的节点描述信息包括网络功能节点描述符、网络功能节点的网络连接点描述符和网络功能节点的业务接入点描述符。连接描述信息包括网络功能节点之间的业务连接描述符和网络功能节点之间的网络连接点描述符。
网络功能节点描述符用于描述实例化网络功能所需的输入参数。
网络功能节点的网络连接点描述符、网络功能节点的业务接入点描述符、网络功能节点之间的业务连接描述符和网络功能节点之间的网络连接描述符与网络切片子网节点的网络连接点描述符、网络切片子网节点的业务接入点描述符、网络切片子网节点之间的业务连接描述符和网络切片子网节点之间的网络连接描述符类型，在此不再赘述。
网络切片子网模板可包括图6中虚线方框所示的业务配置文件，业务配置文件用于网络功能的业务配置。可以理解的是，该业务配置文件指示网络功能要实现哪些业务功能。
网络切片子网模板可包括图6中虚线方框所示的网络服务描述符索引文件，可以是NSD ID。网络服务描述符用于实例化网络功能的虚拟资源部署，网络功能为组成网络切片子网的网络功能。可以理解的是，该种情况下，MANO可根据网络服务描述符ID索引对应的NSD文件，完成网络功能的虚拟资源部署，该虚拟资源可以包括虚拟内存资源、虚拟CPU等。
若网络切片子网实例可以嵌套其它网络切片子网实例，则网络切片子网模板除包括图6所示的内容外，还可包括嵌套的网络切片子网实例对应的网络切片子网模板。
步骤S301，NSSMF接收网络切片子网实例化请求，网络切片子网实例化请求包括网络切片子网需求信息。
可以理解的是，网络切片子网需求信息为NSMF向NSSMF提供的输入参数，以供NSSMF进行网络切片子网的实例化。
网络切片子网实例化请求还包括网络切片子网实例的部署区域，以便在进行实例化的过程中，MANO能将该网络切片子网实例对应的网络功能部署在正确区域的DC中。
网络切片子网实例化请求还包括网络切片实例的标识，以便于NSSMF管理该网络切片子网需求信息属于哪个网络切片实例。
需要说明的是，步骤S301对应于图2所示实施例中的步骤S204a和步骤S204b。
步骤S302，NSSMF获取网络切片子网模板。
在一种实现方式中，NSSMF根据网络切片子网模板标识获取网络切片子网模板标识对应的网络切片子网模板，一个网络切片子网模板标识对应一个网络切片子网模板。
在一种实现方式中，NSSMF根据网络切片类型获取网络切片类型对应的网络切片模板，一个网络切片类型对应一个网络切片子网模板。具体地，根据网络切片类型查找网络切片类型对应的网络切片子网模板标识，再根据网络切片子网模板标识获取网络切片子网模板。
此时，NSSMF还可以为网络切片子网模板对应的网络切片子网实例分配标识，即分配网络切片子网实例标识(NSSI ID)。一个网络切片子网模板实例化一次即可得到一个网络切片子网实例。
步骤S303，NSSMF根据网络切片子网模板将网络切片子网需求信息分解为网络服务需求信息、业务配置需求信息和网络切片子网内的传输网需求信息。
NSSMF根据网络切片子网模板从网络切片子网需求信息中获取实例化网络功能所需的输入参数、网络功能节点的网络连接点信息、网络功能节点的业务接入点信息、网络功能节点之间的网络连接信息以及网络功能节点之间的业务连接信息。
若实例化网络切片子网所需的组件信息还包括组成网络切片子网实例的虚拟网络功能对应的网络服务描述符的索引信息，即NSST包括组成NSSI的VNFs对应的NSD索引文件，则NSSMF根据上述获取的五种信息生成NSD的实例化输入参数，即生成NS实例化所需的输入参数，此时网络服务需求信息为NSD的实例化输入参数。
若实例化网络切片子网所需的组件信息不包括组成网络切片子网实例的虚拟网络功能对应的网络服务描述符的索引信息，即NSST不包括组成NSSI的VNFs对应的NSD索引文件，则NSSMF根据上述获取的五种信息生成组成NSSI的VNFs对应的NSD文件，那么网络服务需求信息为生成的NSD文件。
若实例化网络切片子网所需的组件信息还包括第一业务配置文件的索引信息，即NSST包 括第一业务配置文件的索引信息，则NSSMF根据上述获取的五种信息生成第一业务配置文件的输入参数，那么业务配置需求信息为第一业务配置文件的输入参数。
若实例化网络切片子网所需的组件信息不包括第一业务配置文件的索引信息，即NSST不包括第一业务配置文件的索引信息，则NSSMF根据上述获取的五种信息生成第一业务配置文件，那么业务配置需求信息为第一业务配置文件。
其中，第一业务配置文件为网络切片子网实例的非业务接入点配置文件，即不包括该网络切片子网实例与其它网络切片子网实例对接的业务接入点配置文件。
传输网需求信息为传输网的实例化提供输入参数，包括为网络功能节点之间的网络连接提供网络连接输入参数。
步骤S304，NSSMF向MANO发送网络服务实例化请求，网络服务实例化请求包括网络服务需求信息。
网络服务实例化请求还包括网络切片子网模板标识。
在网络切片子网实例化请求包括网络切片子网实例的部署区域的情况下，网络服务实例化请求还包括网络切片子网实例的部署区域。
网络服务实例化请求还包括网络服务描述符的标识(NSD ID)，以便MANO对NSD ID对应的NS进行实例化。
步骤S305，MANO根据网络服务需求信息实例化网络服务。
MANO根据网络服务需求信息进行网络服务的实例化，包括对网络功能的详细位置进行部署。
若网络服务需求信息为NSD的实例化需求信息，则MANO根据NSD的实例化需求信息进行网络服务的实例化；若网络服务需求信息为NSD文件，则MANO根据NSD文件进行网络服务的实例化。
步骤S306，MANO向NSSMF发送网络服务实例化响应。
MANO在完成网络服务的实例化的情况下，向NSSMF发送网络服务实例化响应，网络服务实例化响应包括网络切片子网实例的标识(NSSI ID)、构成网络切片子网实例的网络功能的部署位置信息和VNF对应的网络连接点的网络连接点实例化信息，网络连接点的实例化信息包括IP地址等信息。
步骤S307，NSSMF向其对应的EMS发送业务配置请求，业务配置请求包括业务配置需求信息。
其中，业务配置需求信息为第一业务配置文件或为第一业务配置文件的需求信息。
步骤S308，NSSMF向TN-manager发送传输网实例化请求，传输网实例化请求包括传输网需求信息。
步骤S308与图2所示实施例中的步骤S208类似，不同之处在于，一个是针对网络切片子网节点组成的传输网，一个是针对网络功能组成的传输网。
步骤S309，TN-manager根据传输网实例化请求进行传输网实例化。
TN-manager在接收到传输网实例化请求的情况下，根据传输网实例化请求进行传输网实例化，建立网络功能之间的网络连接。
步骤S310，TN-manager向NSSMF发送确认消息。
在TN-manager完成传输网的实例化之后，向NSSMF反馈确认消息，通知已完成传输网的实例化。
步骤S311，NSSMF根据网络切片子网模板获取网络切片子网实例与其它网络切片子网实例的网络连接点信息和网络切片子网实例与其它网络切片子网实例的网络连接点信息的业务接入点信息。
网络切片子网节点的网络连接点符描述了网络切片子网节点与其它网络切片子网节点进行网络连接的网络连接点信息，因此，NSSMF可根据网络切片子网节点的网络连接点描述符，结合网络切片子网需求信息，获取网络切片子网实例与其它网络切片子网实例的网络连接点信息。
网络切片子网节点的业务接入点符描述了网络切片子网节点与其它网络切片子网节点进行业务连接的业务接入点信息，因此，NSSMF可根据网络切片子网节点的业务接入点描述符，结合网络切片子网需求信息，获取网络切片子网实例与其它网络切片子网实例的业务接入信息。
步骤S312，NSSMF向NSMF发送实例化信息。
其中，实例化信息包括网络切片子网实例的标识、网络切片子网实例的网络连接点实例化信息以及网络切片子网实例的业务接入点实例化信息。
网络切片子网实例的网络连接点实例化信息包括网络切片子网实例与其它网络切片子网实例对接的网络连接点的本端IP地址，还包括网络切片子网实例与应用服务器或外部接入设备对接的网络连接点信息。
网络切片子网实例的业务接入点实例化信息包括网络切片子网实例与其它网络切片子网实例对接的业务接入点的本端IP地址，还包括网络切片子网实例与应用服务器或外部接入设备对接的业务接入点信息。
假设NSSI-1与NSSI 2对接，对NSSI-1而言，本端IP地址指的是NSSI-1上的IP地址，对端IP地址指的是NSSI-2的IP地址。
NSMF可对每个NSSMF发送的实例化信息进行记录、存储。
需要说明的是，步骤S312对应于图2所示实施例中的步骤S205a和步骤S205b。
需要说明的是，步骤S304、步骤S307以及步骤S308的执行顺序不限于图6所示，三个步骤可同时执行。
图6所示流程中的NSSMF可以为任意一个NSSMF，若网络切片实例由多个网络切片子网实例构成，则存在多个NSSMF，针对每个NSSMF的网络切片子网实例化流程均可按照上述流程执行。
请参见图7，为本申请实施例提供的一种业务连接实例化的流程示意图，该流程从NSMF与NSSMF、EMS交互的角度进行介绍。图7所示的流程可以包括但不限于以下步骤：
步骤S400，NSMF记录NSSMF发送的实例化信息。
步骤S401，NSMF向NSSMF发送业务接入请求，业务接入请求包括网络切片实例标识、网络切片子网模板标识和业务接入点信息。
业务接入点实例化信息包括网络切片子网实例与其它网络切片子网实例对接的业务接入点的本端地址信息和对端地址信息，以及网关路由器地址信息。网关路由器IP地址也即下一跳路由IP地址。以NSSI 1的业务接入点与NSSI 2的业务接入点对接为例，对NSSI 1而言，本端IP地址指的是NSSI 1上的业务接入点的IP地址，对端IP地址指的是NSSI 2上的业务接入点的IP地址。
NSMF在接收到网络切片子网实例1和网络切片子网实例2的实例化信息之后，向NSSMF 1 发送业务接入请求，业务接入请求携带网络切片实例的标识、网络切片子网实例1对应的网络切片子网模板标识和业务接入点信息1。
NSMF在接收到网络切片子网实例1和网络切片子网实例2的实例化信息之后，向NSSMF 2发送业务接入请求，业务接入请求携带网络切片实例的标识、网络切片子网实例2对应的网络切片子网模板标识和业务接入点信息2。
需要说明的是，步骤S401对应于图2所示实施例中的步骤S206a和步骤S206b。
步骤S402，NSSMF根据网络切片子网模板和业务接入点信息生成第二业务配置文件，第二业务配置文件为网络切片子网实例与其它网络切片子网实例对接的业务配置文件。
步骤S403，NSSMF向其对应的EMS发送第二业务配置文件。
步骤S404，EMS根据第一业务配置文件和第二业务配置文件完成业务配置。
NSSMF1对应的EMS1根据第一业务配置文件和第二业务配置文件完成业务配置，即完成网络切片子网实例的业务配置部署，使得NSSI 1可以接入业务，实现业务功能。
其中，第一业务配置文件的描述可参见图6所示实施例中的步骤S303中对其的描述。
步骤S405，NSSMF向NSMF发送业务接入确认消息，业务接入确认消息包括网络切片子网实例的标识。
在EMS完成业务配置之后，NSSMF向NSMF发送业务接入确认消息，携带网络切片子网实例标识，以通知NSMF，相应的网络切片子网实例已接入业务，例如，NSSI 1已接入业务。
需要说明的是，步骤S405对应于图2所示实施例中的步骤S207a和步骤S207b。
图7所示流程中的NSSMF可以为任意一个NSSMF，若网络切片实例由多个网络切片子网实例构成，则存在多个NSSMF，针对每个NSSMF的业务接入实例化流程均可按照上述流程执行。
上述详细阐述了本申请实施例的方法，下面提供了本申请实施例的装置。
请参见图8，是本申请实施例提供的设备的逻辑结构示意图，该设备40可以包括处理单元401和收发单元402。该设备40可以是图2、图5和图7所示实施例中的NSMF或NSSMF或TN-manager。
若该设备40是图2、图5和图7所示实施例中的NSMF，则收发单元402可用于与CSMF、NSSMF和TN-manager进行通信，例如执行图2所示实施例中的步骤S201、步骤S204(a或b)、步骤S205(a或b)、步骤S206(a或b)、步骤S207(a或b)、步骤S209和步骤S210，执行图5所示实施例中的步骤S312，执行图7所示实施例中的步骤S405。处理单元401可用于执行控制NSMF的操作，例如执行图2所示实施例中的步骤S202和步骤S203。具体可参见图2、图5和图7所示实施例中相应的描述，在此不再赘述。
若该设备40是图2、图5和图7所示实施例中的NSSMF，则收发单元402可用于与NSMF、TN-manager、MANO和EMS进行通信，例如执行图2所示实施例中的步骤S204(a或b)、步骤S205(a或b)、步骤S206(a或b)和步骤S207(a或b)，执行图5所示实施例中的步骤S301、步骤S304、步骤S306、步骤S307、步骤S308和步骤S310，执行图7所示实施例中的步骤S401、步骤S403和步骤S405。处理单元401可用于执行控制NSSMF的操作，例如执行图5所示实施例中的步骤S302、步骤S303和步骤S311，执行图7所示实施例中的步骤S402。具体可参见图2、图5和图7所示实施例中相应的描述，在此不再赘述。
若该设备40是图2、图5和图7所示实施例中的TN-manager，则收发单元402可用于与NSMF和NSSMF进行通信，例如执行图2所示实施例中的步骤S208，执行图5所示实施例中的 步骤S308。处理单元401可用于执行控制TN-manager的操作，例如执行图2所示实施例中的步骤S209，执行图5所示实施例中的步骤S309。具体可参见图2、图5和图7所示实施例中相应的描述，在此不再赘述。
请参见图9，是本申请实施例提供的设备的实体结构简化示意图，该设备50可以是图2、图5和图7所示实施例中的NSMF或NSSMF或TN-manager。该设备50包括收发器501、处理器502和存储器503。收发器501、处理器502和存储器503可以通过总线504相互连接，也可以通过其它方式相连接。图8所示的处理单元401所实现的相关功能可以通过一个或多个处理器502来实现。图8所示的收发单元402所实现的相关功能可以由收发器501来实现。
存储器503包括但不限于是随机存储记忆体(random access memory，RAM)、只读存储器(read-only memory，ROM)、可擦除可编程只读存储器(erasable programmable read only memory，EPROM)、或便携式只读存储器(compact disc read-only memory，CD-ROM)，该存储器503用于相关指令及数据。
收发器501用于发送数据和/或信令，以及接收数据和/或信令。
处理器502可以包括是一个或多个处理器，例如包括一个或多个中央处理器(central processing unit，CPU)，在处理器502是一个CPU的情况下，该CPU可以是单核CPU，也可以是多核CPU。
若该设备50为NSMF，则处理器502用于支持NSMF执行图2所示实施例中的步骤S202和步骤S203。
若该设备50为NSSMF，则处理器502用于支持NSSMF执行图2所示实例中的图5所示实施例中的步骤S302、步骤S303和步骤S311，执行图7所示实施例中的步骤S402。
若该设备50为TN-manager，则处理器502用于支持TN-manager执行图2所示实施例中的步骤S206，执行图5所示实施例中的步骤S309。
存储器503用于存储设备50的程序代码和数据。
收发器501用于与其它设备通信，若该设备50为CSMF，收发器501用于与NSMF实体、运行商或第三方客户通信；若该设备为NSMF，收发器501用于与CSMF、NSSMF和TN-manager通信；若该设备为NSSMF实体，收发器用于与NSMF、TN-manager、MANO和EMS通信。
关于处理器502和收发器501所执行的步骤，具体可参见可参见图2、图5和图7所示实施例的描述，在此不再赘述。
可以理解的是，图9仅仅示出了设备的简化设计。在实际应用中，设备还可以分别包含必要的其他元件，包含但不限于任意数量的收发器、处理器、控制器、存储器、通信单元等，而所有可以实现本申请的设备都在本申请的保护范围之内。
本申请实施例还提供了一种网络切片管理系统，包括图1所示的NSMF、NSSMF和CSMF，还包括图2、图5和图7所示实施例中的TN-manager、MANO、EMS等。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，该流程可以由计算机程序来指令相关的硬件完成，该程序可存储于计算机可读取存储介质中，该程序在执行时，可包括如上述各方法实施例的流程。而前述的存储介质包括：ROM或随机存储记忆体RAM、磁碟或者光盘等各种可存储程序代码的介质。因此，本申请又一实施例提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
本申请又一实施例还提供了一种包含指令的计算机程序产品，当其在计算机上运行时， 使得计算机执行上述各方面所述的方法。
本领域普通技术人员可以意识到，结合本申请中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者通过所述计算机可读存储介质进行传输。所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。

Claims (28)

  1. 一种网络切片管理方法，其特征在于，包括：
    网络切片管理功能实体接收网络切片实例化请求，所述网络切片实例化请求包括网络切片需求信息，所述网络切片需求信息包括网络切片模板标识或网络切片类型，以及网络切片部署需求信息；
    所述网络切片管理功能实体根据所述网络切片模板标识或所述网络切片类型信息获取网络切片模板；
    所述网络切片管理功能实体根据所述网络切片模板将所述网络切片需求信息分解为所述网络切片模板包括的网络切片子网的网络切片子网需求信息和所述网络切片内的传输网需求信息；
    对于所述网络切片包括的每一个网络切片子网，所述网络切片管理功能实体向网络切片子网管理功能实体发送网络切片子网实例化请求，所述网络切片子网实例化请求包括所述网络切片子网需求信息；
    所述网络切片管理功能实体接收网络切片子网管理功能实体发送的网络切片子网实例化响应，所述网络切片子网实例化响应包括网络切片子网实例化信息，其中，所述网络切片子网实例化信息包括网络切片子网实例的标识、所述网络切片子网实例的业务接入点实例化信息和所述网络切片子网实例的网络连接点实例化信息；
    所述网络切片管理功能实体向传输网管理器发送传输网实例化请求，所述传输网实例化请求包括所述网络切片内的传输网需求信息和所有网络切片子网实例的网络连接点信息；
    所述网络切片管理功能实体根据各网络切片子网实例化后获得的业务接入点信息，触发建立各网络切片子网实例业务连接。
  2. 根据权利要求1所述的方法，其特征在于，所述网络切片模板包括网络切片子网模板的标识、所述节点为网络切片子网节点，所述节点描述信息包括实例化网络切片子网所需的组件信息、所述网络切片子网节点的网络连接点描述符和、所述网络切片子网节点的业务接入点描述符、，所述连接描述信息包括所述网络切片子网节点之间的网络连接描述符和所述网络切片子网节点之间的业务连接描述符；所述网络切片子网节点的网络连接点描述符用于描述所述网络切片子网节点的网络连接点信息，所述网络切片子网节点的业务接入点描述符用于描述所述网络切片子网节点的业务接入点信息，所述网络切片子网节点的网络连接点描述符用于描述所述网络切片子网节点的网络连接点信息，所述网络切片子网节点之间的网络连接描述符用于描述所述网络切片子网节点之间的网络连接信息，所述网络切片子网节点之间的业务连接描述符用于描述所述网络切片子网节点之间的业务连接信息。
  3. 根据权利要求2所述的方法，其特征在于，所述网络切片子网模板的标识对应的网络切片子网模板包括组成所述网络切片子网的网络功能节点的节点描述符、所述网络功能节点的网络连接点描述符、所述网络功能节点的业务接入点描述符、所述网络功能节点之间的网络连接描述符和所述网络功能节点之间的业务连接描述符。
  4. 根据权利要求1所述的方法，其特征在于，所述网络切片模板包括实例化网络功能所 需的信息、所述网络功能节点的网络连接点描述符和所述网络功能节点的业务接入点描述符，所述连接描述信息包括所述网络功能节点之间的网络连接描述符和所述网络功能节点之间的业务连接描述符。
  5. 根据权利要求1-3任一项所述的方法，其特征在于，所述网络切片模板实例化所述网络切片所需的组件信息还包括组成所述网络切片的虚拟网络功能对应的网络服务描述符索引文件，所述网络服务描述符索引文件用于实例化所述虚拟网络功能的虚拟资源部署。
  6. 根据权利要求4所述的方法，其特征在于，所述网络切片模板还包括业务配置文件，所述业务配置文件用于网络功能的业务配置。
  7. 根据权利要求1-3任一项所述的方法，其特征在于，所述网络切片子网实例化请求还包括网络切片子网实例的部署区域，所述网络切片子网实例为网络切片子网对应的实例；
    所述网络切片管理功能实体向网络切片子网管理功能实体发送网络切片子网实例化请求之前，还包括：
    所述网络切片管理功能实体根据所述网络切片需求信息确定所述网络切片子网实例的部署区域。
  8. 根据权利要求7所述的方法，其特征在于，所述网络切片子网实例化请求还包括所述网络切片对应的网络切片实例的标识。
  9. 根据权利要求7所述的方法，其特征在于，所述网络切片子网需求信息还包括网络切片子网模板标识或所述网络切片类型。
  10. 根据权利要求1所述的方法，其特征在于，所述网络切片管理功能实体向传输网管理器发送传输网实例化请求，包括：
    所述网络切片管理功能实体根据每个网络切片子网管理功能实体发送的实例化响应构建传输网络实例化请求，并向传输网络管理器发送传输网实例化请求。
  11. 根据权利要求1所述的方法，其特征在于，所述网络切片管理功能实体根据各网络切片子网实例化后获得的业务接入点信息，触发建立各网络切片子网实例业务连接，包括：
    所述网络切片管理功能实体根据各网络切片子网实例化后获得的业务接入点信息，向对应的网络切片子网管理功能实体发送业务接入请求，所述业务接入请求包括所述网络切片实例的标识、对应的网络切片子网模板的标识和对应的业务接入点信息，所述业务接入请求用于触发对应的网络切片子网关联功能实体建立业务连接。
  12. 一种网络切片管理方法，其特征在于，包括：
    网络切片子网管理功能实体接收网络切片子网实例化请求，所述网络切片子网实例化请求包括网络切片子网需求信息；
    所述网络切片子网管理功能实体获取网络切片子网模板；
    所述网络切片子网管理功能实体根据所述网络切片子网模板将所述网络切片子网需求信息分解为所述网络切片子网模板包括的网络功能的网络服务需求信息、业务配置需求信息和所述网络切片子网内的传输网需求信息；
    所述网络切片子网管理功能实体向网络切片管理功能实体发送网络切片子网实例化响应，所述网络切片子网实例化响应包括网络切片子网实例化信息，其中，所述网络切片子网实例化信息包括网络切片子网实例的标识、所述网络切片子网实例的业务接入点实例化信息和所述网络切片子网实例的网络连接点实例化信息；
    所述网络切片子网管理功能实体向管理编排器发送网络服务实例化请求，所述网络服务实例化请求包括所述网络服务需求信息；
    所述网络切片子网管理功能实体向所述网络切片子网管理功能实体对应的网元管理系统发送业务配置请求，所述业务配置请求包括所述业务配置需求信息；
    所述网络切片子网管理功能实体向传输网管理器发送传输网实例化请求，所述传输网实例化请求包括所述网络切片子网内的传输网需求信息。
  13. 根据权利要求12所述的方法，其特征在于，所述网络切片子网模板包括组成所述网络切片子网的网络功能节点的节点描述符、所述网络功能节点的网络连接点描述符和、所述网络功能节点的业务接入点描述符、，所述网络功能节点之间的连接描述信息包括所述网络功能节点之间的网络连接描符和所述网络功能节点之间的业务连接描述符；所述网络功能节点的节点描述符用于描述实例化网络功能所需的信息，所述网络功能节点的网络连接点描述符用于描述所述网络功能节点的网络连接点信息，所述网络功能节点的业务接入点描述符用于描述所述网络功能节点的业务接入点信息，所述网络功能节点之间的网络连接描述符用于描述所述网络功能节点之间的网络连接信息，所述网络功能节点之间的业务连接描述符用于描述所述网络功能节点之间的业务连接信息。
  14. 根据权利要求12或13所述的方法，其特征在于，所述网络切片子网模板还包括组成所述网络切片子网的虚拟网络功能对应的网络服务描述符索引文件，所述网络服务描述符索引文件用于实例化所述虚拟网络功能的虚拟资源部署。
  15. 根据权利要求12或13所述的方法，其特征在于，所述网络切片子网模板还包括第一网络功能配置参数信息业务配置文件，所述第一业务配置文件用于网络功能的业务部署，所述第一业务配置文件为所述网络切片子网实例的非业务接入点配置文件。
  16. 根据权利要求14所述的方法，其特征在于，所述网络服务需求信息为网络服务描述符的实例化输入参数。
  17. 根据权利要求12或13所述的方法，其特征在于，所述网络服务需求信息为组成网络切片子网实例的虚拟网络功能对应的网络服务描述符文件。
  18. 根据权利要求15所述的方法，其特征在于，所述业务配置需求信息为所述第一业务配置文件的输入参数，所述第一业务配置文件为所述网络切片子网实例的非业务接入点配置文件。
  19. 根据权利要求12或13所述的方法，其特征在于，所述业务配置需求信息为第一业务配置文件，所述第一业务配置文件用于网络功能的业务部署，所述第一业务配置文件为所述网络切片子网实例的非业务接入点配置文件。
  20. 根据权利要求18或19所述的方法，其特征在于，所述网络切片子网管理功能实体根据所述网络切片子网模板将所述网络切片子网需求信息分解为业务配置需求信息、网络服 务需求信息和传输网需求信息之后，还包括：
    所述网络切片子网管理功能实体根据所述网络切片子网模板获取所述网络切片子网实例与其它网络切片子网实例的网络连接点信息和所述网络切片子网实例与其它网络切片子网实例的业务接入点信息。
  21. 根据权利要求20所述的方法，其特征在于，所述网络切片子网管理功能实体向网络切片管理功能实体发送网络切片子网实例化响应之后，还包括：
    所述网络切片子网管理功能实体从所述网络切片管理功能实体接收业务接入请求，所述业务接入请求包括所述网络切片子网模板的标识、网络切片实例的标识和业务接入点实例化信息，所述业务接入点实例化信息包括所述网络切片子网实例与其它网络切片子网实例对接的业务接入点的本端地址信息和对端地址信息，以及网关路由器地址信息；
    所述网络切片子网管理功能实体根据所述网络切片子网模板和所述业务接入点实例化信息生成第二业务配置文件，所述第二业务配置文件为所述网络切片子网实例与所述其它网络切片子网实例对接的业务配置文件。
  22. 根据权利要求12所述的方法，其特征在于，所述网络切片子网实例化请求还包括所述网络切片子网实例的部署区域，所述网络服务实例化请求还包括所述网络切片子网实例的部署区域。
  23. 根据权利要求12所述的方法，其特征在于，所述网络切片子网需求信息包括网络切片子网模板标识或网络切片类型；
    所述网络切片子网管理功能实体获取网络切片子网模板，包括：
    所述网络切片子网管理功能实体根据所述网络切片子网模板标识或所述网络切片类型获取网络切片子网模板。
  24. 一种网络切片管理方法，其特征在于，包括：
    管理编排器接收传输网实例化请求，所述传输网实例化请求包括传输网需求信息；
    所述管理编排器根据所述传输网需求信息进行传输网实例化；
    所述管理编排器发送传输网实例化响应。
  25. 一种网络切片管理功能实体，其特征在于，包括处理器、收发器和存储器，其中，所述存储器中存储一组程序代码，且所述处理器用于调用所述存储器中存储的程序代码，执行以下操作：
    接收网络切片实例化请求，所述网络切片实例化请求包括网络切片需求信息，所述网络切片需求信息包括网络切片模板标识或网络切片类型，以及网络切片部署需求信息；
    根据所述网络切片模板标识或所述网络切片类型信息获取网络切片模板；
    所述网络切片管理功能实体根据所述网络切片模板将所述网络切片需求信息分解为所述网络切片模板包括的网络切片子网的网络切片子网需求信息和所述网络切片内的传输网需求信息；
    对于所述网络切片包括的每一个网络切片子网，向网络切片子网管理功能实体发送网络 切片子网实例化请求，所述网络切片子网实例化请求包括所述网络切片子网需求信息；
    接收网络切片子网管理功能实体发送的网络切片子网实例化响应，所述网络切片子网实例化响应包括网络切片子网实例化信息，其中，所述网络切片子网实例化信息包括网络切片子网实例的标识、所述网络切片子网实例的业务接入点实例化信息和所述网络切片子网实例的网络连接点实例化信息；
    向传输网管理器发送传输网实例化请求，所述传输网实例化请求包括所述网络切片内的传输网需求信息和所有网络切片子网实例的网络连接点信息；
    根据各网络切片子网实例化后获得的业务接入点信息，触发建立各网络切片子网实例业务连接。
  26. 一种网络切片子网管理功能实体，其特征在于，包括处理器、收发器和存储器，其中，所述存储器中存储一组程序代码，且所述处理器用于调用所述存储器中存储的程序代码，执行以下操作：
    接收网络切片子网实例化请求，所述网络切片子网实例化请求包括网络切片子网需求信息；
    获取网络切片子网模板；
    根据所述网络切片子网模板将所述网络切片子网需求信息分解为所述网络切片子网模板包括的网络功能的网络服务需求信息、业务配置需求信息和所述网络切片子网内的传输网需求信息；
    向网络切片管理功能实体发送网络切片子网实例化响应，所述网络切片子网实例化响应包括网络切片子网实例化信息，其中，所述网络切片子网实例化信息包括网络切片子网实例的标识、所述网络切片子网实例的业务接入点实例化信息和所述网络切片子网实例的网络连接点实例化信息；
    向管理编排器发送网络服务实例化请求，所述网络服务实例化请求包括所述网络服务需求信息；
    向所述网络切片子网管理功能实体对应的网元管理系统发送业务配置请求，所述业务配置请求包括所述业务配置需求信息；
    向传输网管理器发送传输网实例化请求，所述传输网实例化请求包括所述网络切片子网内的传输网需求信息。
  27. 一种传输网管理器，其特征在于，包括处理器、收发器和存储器，其中，所述存储器中存储一组程序代码，且所述处理器用于调用所述存储器中存储的程序代码，执行以下操作：
    接收传输网实例化请求，所述传输网实例化请求包括传输网需求信息；
    根据所述传输网需求信息进行传输网实例化；
    发送传输网实例化响应。
  28. 一种网络切片管理系统，其特征在于，包括如权利要求25所述的网络切片管理功能实体、如权利要求26所述的网络切片子网管理功能实体和如权利要求27所述的传输网管理器。
PCT/CN2018/108264 2017-09-30 2018-09-28 网络切片管理方法及其装置 WO2019062836A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2020518532A JP7012836B2 (ja) 2017-09-30 2018-09-28 ネットワークスライス管理方法及び装置
EP18860691.7A EP3684010B1 (en) 2017-09-30 2018-09-28 Network slice management method, and device for same
US16/832,716 US10958525B2 (en) 2017-09-30 2020-03-27 Network slice management method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710928212.XA CN109600246B (zh) 2017-09-30 2017-09-30 网络切片管理方法及其装置
CN201710928212.X 2017-09-30

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/832,716 Continuation US10958525B2 (en) 2017-09-30 2020-03-27 Network slice management method and apparatus

Publications (1)

Publication Number Publication Date
WO2019062836A1 true WO2019062836A1 (zh) 2019-04-04

Family

ID=65900847

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/108264 WO2019062836A1 (zh) 2017-09-30 2018-09-28 网络切片管理方法及其装置

Country Status (5)

Country Link
US (1) US10958525B2 (zh)
EP (1) EP3684010B1 (zh)
JP (1) JP7012836B2 (zh)
CN (1) CN109600246B (zh)
WO (1) WO2019062836A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020215504A1 (zh) * 2019-04-22 2020-10-29 烽火通信科技股份有限公司 一种需求定义网络的实现方法及网络架构
CN114006818A (zh) * 2020-07-13 2022-02-01 中国电信股份有限公司 端到端网络切片对接的配置方法和系统
EP4024912A4 (en) * 2019-09-29 2022-10-26 Huawei Technologies Co., Ltd. NETWORK SLOT BILLING METHOD AND DEVICE

Families Citing this family (39)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019083843A1 (en) 2017-10-23 2019-05-02 Nokia Solutions And Networks Oy CONFIGURATION OF NETWORK SLICES
US11070997B2 (en) * 2018-02-22 2021-07-20 Intel Corporation Performance measurement job control for 5G networks and network slicing
KR102692166B1 (ko) * 2018-03-20 2024-08-05 마이크로소프트 테크놀로지 라이센싱, 엘엘씨 네트워크 슬라이싱을 위한 시스템 및 방법
EP3777034A1 (en) * 2018-04-23 2021-02-17 Huawei Technologies Co. Ltd. System, function and interface for interconnecting multi-domain network slice control and management
CN110572272B (zh) * 2018-06-06 2020-11-06 大唐移动通信设备有限公司 一种网络切片的创建方法及管理编排系统
US10993177B2 (en) * 2018-12-13 2021-04-27 Verizon Patent And Licensing Inc. Network slice instance creation
US11950151B2 (en) * 2019-02-13 2024-04-02 Apple Inc. Self-organizing networks (SON) for mobility robustness optimization (MRO) and automatic network slice creation
CN112087311B (zh) * 2019-06-14 2022-04-12 华为技术有限公司 一种虚拟网络功能vnf部署方法及装置
CN112118579B (zh) * 2019-06-21 2024-03-26 华为技术有限公司 资源分配方法以及装置
US10939267B1 (en) 2019-08-15 2021-03-02 Netsia, Inc. Apparatus and method for a unified slice manager
CN112423312A (zh) * 2019-08-20 2021-02-26 中国电信股份有限公司 信息处理方法、装置、系统以及计算机可读存储介质
CN112449315B (zh) * 2019-08-27 2022-05-24 华为技术有限公司 一种网络切片的管理方法及相关装置
CN115767452A (zh) * 2019-09-29 2023-03-07 华为技术有限公司 一种网络切片的计费方法及装置
CN110730478B (zh) * 2019-10-18 2021-12-21 腾讯科技（深圳）有限公司 切片关联方法、装置、端到端切片编排器及存储介质
WO2021089172A1 (en) * 2019-11-08 2021-05-14 Telefonaktiebolaget Lm Ericsson (Publ) Code activation management method for network slicing solutions, and corresponding entity, server and computer program
CN112817688B (zh) * 2019-11-15 2023-10-20 大唐移动通信设备有限公司 一种网络切片模板生成方法及装置
CN112910668B (zh) * 2019-11-19 2022-09-09 上海华为技术有限公司 一种业务配置方法，业务配置装置以及业务配置设备
CN111065151B (zh) * 2019-12-24 2022-04-01 亚信科技（中国）有限公司 基于bfv的网络切片处理方法及系统
CN115426267A (zh) * 2019-12-31 2022-12-02 华为技术有限公司 用于获取网络切片标识的方法和装置
US11115920B1 (en) * 2020-03-31 2021-09-07 Wipro Limited Method and system of template-based dynamic network slicing
CN113541980B (zh) * 2020-04-14 2023-07-14 中国移动通信集团浙江有限公司 网络切片故障根因定位方法、装置、计算设备及存储介质
CN111614496B (zh) * 2020-05-13 2021-12-21 北京紫光展锐通信技术有限公司 路由访问方法、装置、电子设备及存储介质
CN111817876B (zh) * 2020-06-04 2023-07-11 北京思特奇信息技术股份有限公司 基于行业客户需求的5g网络切片管理方法
CN114051279A (zh) * 2020-07-23 2022-02-15 华为技术有限公司 一种业务处理方法及网络设备
CN114071657B (zh) * 2020-07-31 2024-08-09 中移(苏州)软件技术有限公司 网络切片的处理方法、装置和存储介质
CN114079909A (zh) * 2020-08-14 2022-02-22 中国移动通信有限公司研究院 一种网络切片信息处理方法、装置及网络设备
US20220070720A1 (en) * 2020-09-02 2022-03-03 Celona, Inc. Method and Apparatus for Autoconfiguring Microslices in a Wireless Enterprise Network
CN114422342A (zh) * 2020-10-13 2022-04-29 中国移动通信有限公司研究院 传送网切片的部署方法、装置、设备及可读存储介质
CN114554540A (zh) * 2020-11-24 2022-05-27 上海中兴软件有限责任公司 网络切片接入方法、设备、系统及存储介质
CN114640588B (zh) * 2020-11-30 2024-05-31 中国移动通信有限公司研究院 一种网络切片业务的处理方法及相关设备
CN114765787A (zh) 2020-12-31 2022-07-19 阿里巴巴集团控股有限公司 服务请求与提供方法、设备及存储介质
CN115208777B (zh) * 2021-03-25 2024-07-02 中国移动通信有限公司研究院 一种信息处理方法、装置、平台设备及网络设备
CN113472595B (zh) * 2021-08-10 2023-04-18 中国联合网络通信集团有限公司 核心网子网切片创建方法、功能实体和切片管理系统
US11968274B2 (en) 2021-11-04 2024-04-23 Nokia Solutions And Networks Oy Multi-access edge computing slicing
CN116261189A (zh) * 2021-12-10 2023-06-13 华为技术有限公司 切换网络切片的方法和装置
WO2023131403A1 (en) * 2022-01-05 2023-07-13 Telefonaktiebolaget Lm Ericsson (Publ) Automated service driven virtual network function dimensioning
CN115037625B (zh) * 2022-06-14 2024-04-26 中国电信股份有限公司 网络切片处理方法、装置、电子设备及可读存储介质
FR3142853A1 (fr) * 2022-12-06 2024-06-07 Orange Procédé de gestion de la création de tranches de réseau dans un réseau de télécommunications
CN116528272B (zh) * 2023-06-29 2023-10-10 中国电信股份有限公司 非陆地业务网络切片创建方法、通信系统及相关设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016192643A1 (en) * 2015-06-01 2016-12-08 Huawei Technologies Co., Ltd. Systems and methods for managing network traffic with network operator
CN106549806A (zh) * 2016-10-26 2017-03-29 清华大学 一种网络切片管理器及其管理方法
CN106921977A (zh) * 2015-12-26 2017-07-04 华为技术有限公司 一种基于业务流的服务质量规划方法、装置及系统
CN107094127A (zh) * 2016-02-18 2017-08-25 电信科学技术研究院 安全信息的处理方法及装置、获取方法及装置
CN107113195A (zh) * 2015-06-01 2017-08-29 华为技术有限公司 用于控制平面和数据平面中的虚拟化功能的系统和方法

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10116696B2 (en) * 2012-05-22 2018-10-30 Sri International Network privilege manager for a dynamically programmable computer network
US10050868B2 (en) * 2015-01-16 2018-08-14 Sri International Multimodal help agent for network administrator
US10644955B2 (en) * 2015-08-21 2020-05-05 Huawei Technologies Co., Ltd. Method and apparatus for network slicing
US10425830B2 (en) * 2015-09-07 2019-09-24 Electronics And Telecommunications Research Institute Mobile communication network system and method for composing network component configurations
US10129108B2 (en) * 2015-11-13 2018-11-13 Huawei Technologies Co., Ltd. System and methods for network management and orchestration for network slicing
EP3456090B1 (en) * 2016-05-12 2021-03-31 Convida Wireless, Llc Connecting to virtualized mobile core networks

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016192643A1 (en) * 2015-06-01 2016-12-08 Huawei Technologies Co., Ltd. Systems and methods for managing network traffic with network operator
CN107113195A (zh) * 2015-06-01 2017-08-29 华为技术有限公司 用于控制平面和数据平面中的虚拟化功能的系统和方法
CN106921977A (zh) * 2015-12-26 2017-07-04 华为技术有限公司 一种基于业务流的服务质量规划方法、装置及系统
CN107094127A (zh) * 2016-02-18 2017-08-25 电信科学技术研究院 安全信息的处理方法及装置、获取方法及装置
CN106549806A (zh) * 2016-10-26 2017-03-29 清华大学 一种网络切片管理器及其管理方法

Non-Patent Citations (1)

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

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020215504A1 (zh) * 2019-04-22 2020-10-29 烽火通信科技股份有限公司 一种需求定义网络的实现方法及网络架构
EP4024912A4 (en) * 2019-09-29 2022-10-26 Huawei Technologies Co., Ltd. NETWORK SLOT BILLING METHOD AND DEVICE
CN114006818A (zh) * 2020-07-13 2022-02-01 中国电信股份有限公司 端到端网络切片对接的配置方法和系统
CN114006818B (zh) * 2020-07-13 2023-10-31 中国电信股份有限公司 端到端网络切片对接的配置方法和系统

Also Published As

Publication number Publication date
EP3684010B1 (en) 2022-07-27
JP2020536434A (ja) 2020-12-10
CN109600246B (zh) 2021-09-21
EP3684010A1 (en) 2020-07-22
EP3684010A4 (en) 2020-11-04
JP7012836B2 (ja) 2022-02-14
CN109600246A (zh) 2019-04-09
US10958525B2 (en) 2021-03-23
US20200228405A1 (en) 2020-07-16

Similar Documents

Publication Publication Date Title
JP7012836B2 (ja) ネットワークスライス管理方法及び装置
US11146462B2 (en) Network slice management method, device, and system
US11283684B2 (en) Network slice deployment method and apparatus
KR102436981B1 (ko) 무선 액세스 네트워크 정보 처리 방법 및 장치, 네트워크 요소 및 저장 매체
US11051183B2 (en) Service provision steps using slices and associated definitions
CN109952796B (zh) 可共享切片实例的创建及修改
EP3595244B1 (en) Network slice management method, unit and system
EP3133794B1 (en) Network function virtualization network system
US11303526B2 (en) Network slice deployment method and apparatus
EP3836577B1 (en) Session management method and device for user groups
WO2018171459A1 (zh) 网络切片的管理方法和装置
CN113596191B (zh) 一种数据处理方法、网元设备以及可读存储介质
CN110326345B (zh) 一种配置网络切片的方法、装置和系统
EP3869855A1 (en) Information transmission method and apparatus thereof
WO2019091439A1 (zh) 网络切片生成方法、装置及终端
US11558491B2 (en) Information-centric networking over 5G or later networks
CN116074896A (zh) 多接入边缘计算切片
EP4024912A1 (en) Network slice charging method and device
Nguyen et al. Location-aware dynamic network provisioning
CN112887137B (zh) 接口索引一致性的实现方法及装置
WO2023116638A1 (zh) 切片配置方法、系统、服务器和存储介质
TW202249505A (zh) 算力資源調度的方法以及相關裝置

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020518532

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018860691

Country of ref document: EP

Effective date: 20200415