WO2018170647A1 - 一种网络切片的管理方法、单元和系统 - Google Patents

一种网络切片的管理方法、单元和系统 Download PDF

Info

Publication number
WO2018170647A1
WO2018170647A1 PCT/CN2017/077202 CN2017077202W WO2018170647A1 WO 2018170647 A1 WO2018170647 A1 WO 2018170647A1 CN 2017077202 W CN2017077202 W CN 2017077202W WO 2018170647 A1 WO2018170647 A1 WO 2018170647A1
Authority
WO
WIPO (PCT)
Prior art keywords
subnet
information
network service
management unit
network
Prior art date
Application number
PCT/CN2017/077202
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 CN202011284132.3A priority Critical patent/CN112910677A/zh
Priority to JP2019572269A priority patent/JP6834033B2/ja
Priority to AU2017404864A priority patent/AU2017404864B2/en
Priority to PCT/CN2017/077202 priority patent/WO2018170647A1/zh
Priority to CN201780088363.7A priority patent/CN110447208B/zh
Priority to KR1020197029834A priority patent/KR102259679B1/ko
Priority to EP17901984.9A priority patent/EP3595244B1/en
Priority to BR112019019222A priority patent/BR112019019222A2/pt
Publication of WO2018170647A1 publication Critical patent/WO2018170647A1/zh
Priority to US16/574,565 priority patent/US11296957B2/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/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/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/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/0866—Checking the configuration
    • 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/0876—Aspects of the degree of configuration automation
    • H04L41/0886—Fully automatic configuration
    • 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
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/668—Internet protocol [IP] address subnets

Definitions

  • the present application relates to the field of communications, and in particular, to a method, a unit, and a system for managing a network slice.
  • the traditional cellular network has a one-size-fits-all network architecture with dedicated support and IT systems, making it ideal for a single-service network.
  • this vertical architecture makes it difficult to scale telecom networks, and it is difficult to adapt to changing user needs and meet the needs of new applications.
  • logic-based rather than physical resource-based technologies will be adopted, and the network will be further abstracted into Network Slices, which are defined by a number of custom software implementations that enable operations
  • the provider provides the network as a service to the user, that is, the operator can provide the connection service in the form of network-as-a-service to meet the broad needs of people for more network use cases.
  • the key to network slicing is Network Function Virtualization (NFV).
  • NFV Network Function Virtualization
  • the so-called NFV is to transfer the hardware and software functions of dedicated devices in the network to the virtual host.
  • Automated deployment is a major feature of network slicing management.
  • the so-called automated deployment of network slicing is to design and plan the network offline, generate network slicing templates, and generate network slicing instances online based on network slicing templates.
  • the network slice includes at least one Network Slice Subnet, and one network slice subnet includes at least one Network Service (NS), and one network service includes at least one virtual network function (Virtualized Network Function, VNF), so the network slice instance includes at least one Network Slice Subnet Instance (NSSI), the network slice subnet instance includes at least one network service instance (NS Instance), and the network service instance further includes at least one VNF instance.
  • the network slice and network slicing subnet are composed of two parts: application (application configuration parameter) and virtual resource.
  • the NFV management and orchestration (MANO) architecture in the prior art is shown in Figure 1A, where the network The Network Function Virtualization Orchestrator (NFVO) unit can automatically deploy and manage network services.
  • NFVO Network Function Virtualization Orchestrator
  • NFVO automatically deploys NS instances according to Network Service Descriptor (NSD), including instantiating corresponding VNF instances. And establishing a connection between VNF instances, since MANO can only instantiate the virtual resource part, the NS instance created by NFVO only includes the network slice or the virtual resource part of the network slice subnet.
  • NSD Network Service Descriptor
  • the network resource instance information is manually specified to deploy the network instance, and then the network parameter instance is used to determine how to configure the service parameter.
  • the network instance cannot be automatically deployed and service parameters are automatically configured to automatically provide services. It can be seen that the existing network instance deployment process is complex, the manual intervention is high, and the deployment efficiency is low.
  • the present invention provides a method and a device for managing a network slice template, which are used to solve the problem that the existing network instance is complicated to be deployed and requires a high degree of manual intervention.
  • the application provides a method for managing a network slice template, where the method includes:
  • the first management unit receives the subnet management request, where the subnet management request carries the indication information of the subnet template; wherein the first management network element may be a Network Slice Subnet Management Function (NSSMF), the network a slice management function (NSMF), or another management unit having an NSSMF or NSMF function; the first management unit acquires network service descriptor association information or a network service descriptor according to the indication information of the subnet template; The management unit acquires the network service instance according to the network service descriptor association information or the network service descriptor. In a specific implementation, the first management unit acquires the network service instance information according to the network service descriptor association information or the network service descriptor, and then obtains the network service instance by using the network service instance information.
  • NSSMF Network Slice Subnet Management Function
  • NSMF slice management function
  • the acquiring, by the first management unit, the network service instance according to the network service descriptor association information or the network service descriptor may refer to that the first management unit acquires the network service instance according to the network service descriptor association information or the network service descriptor. information.
  • the first management unit may acquire the subnet template according to the subnet template indication information, where the subnet template includes association information of the network service description or a network service descriptor.
  • the first management unit may also obtain the subnet template by using the following manner: for example, the first management unit locally stores the subnet template; the first management unit searches for the corresponding relationship between the local maintenance subnet template indication information and the subnet template.
  • the subnet management request further carries the subnet requirement information;
  • the subnet requirement information and the subnet template indication information acquire association information or a network service descriptor of the network service descriptor.
  • the network service descriptor association information may include one of the following information or Multiple: network service descriptor identification, deployment specifications, instantiation level, vendor information, version information.
  • the subnet template creates a management object of the subnet instance or the subnet instance; or the first management unit sends a creation request to the third management unit according to the subnet template, where the creation request is used to create a subnet instance or a subnet instance management Object.
  • the third management unit may be a network management unit (NM), an element management unit (EM), a domain management unit (DM), or an operator support system (OSS).
  • NM network management unit
  • EM element management unit
  • DM domain management unit
  • OSS operator support system
  • the second management unit may be an NSSMF.
  • the first management unit may associate the subnet instance and the network service An instance, or a management object that associates a subnet instance and a subnet instance with the first management unit.
  • the first management unit configures network service instance information in the management object, where the network service instance information may include at least one of the following information: a network service instance identifier, a network service instance specification, and a network service instance. Instantiate the level.
  • the application can enable the first management unit to automatically obtain the network service instance during the network instance creation process, thereby improving the deployment efficiency of the network slice.
  • the application provides a method for managing a network slice template, the method includes: a first management unit receives a subnet management request, where the subnet management request carries indication information of a subnet template; The indication information of the subnet template acquires the application information; the first management unit sends a subnet configuration request to the second management unit, where the subnet configuration request carries the application information.
  • the first management unit acquires a subnet template according to the indication information of the subnet template, where the subnet template includes the application information, the first management The unit thereby obtains the application information.
  • the subnet template here may also be referred to as a web service descriptor, and the application information may be an application parameter, a configuration file, a management object attribute value, or a script.
  • the network configuration instance information is also carried in the subnet configuration request.
  • the network service instance information includes one or more of the following information: a network service instance identifier, a network service instance deployment specification, a network service instance instantiation level, a virtual network function instance identifier, and a virtual network function instance deployment specification.
  • the subnet template includes the association between the performance information of the subnet template and the network service requirement information.
  • the association relationship is used to determine the network service requirement information, where the network service requirement information includes at least one of the following: a network service deployment specification, a network service instantiation level, and the network service requirement information is used to obtain The network service instance information.
  • the subnet template includes network function requirement information and association information of the application information, where the network
  • the function requirement information may include one or more of the following information: a virtualized network function descriptor (VNFD), a virtual network function requirement information (VNF Profile), and a virtual network function deployment specification ( Virtualized deployment flavor ID, VNF flavor ID).
  • VNFD virtualized network function descriptor
  • VNF Profile virtual network function requirement information
  • VNF deployment specification Virtualized deployment flavor ID, VNF flavor ID
  • the application can enable the first management unit to automatically deploy application parameters during the creation of the network service instance, thereby improving the deployment efficiency of the network slice.
  • an embodiment of the present invention provides a first management unit, where the first management unit has a function of implementing each behavior of the first management unit in the foregoing method example.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the first management unit includes a processor and a communication interface, and the processor is configured to support the first management unit to perform a corresponding function in the above method. Further, the first management unit may further include a memory for coupling with the processor, which stores program instructions and data necessary for the first management unit.
  • an embodiment of the present invention provides a communication system, where the system includes the first management order described in the foregoing aspect. Yuan and the second management unit.
  • an embodiment of the present invention provides a computer storage medium for storing the computer software instructions used by the first management unit, including a program designed to perform the above aspects.
  • the embodiment of the present application discloses a method for managing a network slice template.
  • the method includes the first management unit receiving the subnet management request, the subnet management request carrying the indication information of the subnet template, and the first management unit acquiring the network service descriptor association information or the network service description according to the indication information of the subnet template. And the first management unit acquires the network service instance according to the network service descriptor association information or the network service descriptor.
  • the management method of the network slice template provided by the application can enable the first management unit to automatically obtain the network service instance during the network instance creation process, thereby improving the deployment efficiency of the network slice.
  • FIG. 1 is a schematic diagram of a network architecture of a MANO of an NFV in the prior art
  • FIG. 2 is a schematic diagram of a possible network architecture according to an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of a method for managing a network slice template according to an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram of communication of another network slice management method according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of communication of another network slice management method according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of communication of another network slice management method according to an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of communication of another network slice management method according to an embodiment of the present invention.
  • 7-1 is a schematic diagram of a subnet template according to an embodiment of the present invention.
  • FIG. 8 is a schematic flowchart diagram of still another network slice management method according to an embodiment of the present disclosure.
  • FIG. 8-1 is a schematic flowchart diagram of still another network slice management method according to an embodiment of the present invention.
  • FIG. 9A is a schematic block diagram of a first management unit according to an embodiment of the present disclosure.
  • FIG. 9B is a schematic structural diagram of a first management unit according to an embodiment of the present disclosure.
  • FIG. 10A is a schematic block diagram of a second management unit according to an embodiment of the present disclosure.
  • FIG. 10B is a schematic structural diagram of a second management unit according to an embodiment of the present invention.
  • FIG. 1 is a schematic diagram of a possible application scenario according to an embodiment of the present invention.
  • the application scenario shown in FIG. 1 includes at least a Service Orchestrator (SO) unit, a Network Orchestrator (NO) unit, an Element Manager (EM) unit, and a Network unit/network.
  • Network Function (NF) unit Network Function Virtualization Orchestration (NFVO), Virtualized Network Function Manager (VNFM).
  • NFVO Network Function Virtualization Orchestration
  • VNFM Virtualized Network Function Manager
  • the SO unit which may also be referred to as a service orchestration and management unit or a service management unit, mainly includes: performing lifecycle management (eg, instantiation, update, deletion, etc.) on the service according to the service request message; service aggregation; service Management, such as service fault, configuration, billing, performance and security (Fault, Configuration, Accounting, Performance, Security, FCAPS) management; and mapping between service and network slice (network slice).
  • the service may be a set of service level agreement (SLA) communication services that the user can enjoy, such as mobile broadband (MBB) services, voice services, and the Internet of Things (IOT).
  • MBB mobile broadband
  • IOT Internet of Things
  • Business for example, smart parking business, smart meter reading business, etc.
  • the SO unit can manage the services carried by the network slice.
  • the NO unit which may also be called a network orchestration and management unit or a network management unit, mainly includes: network slice management, such as network slice lifecycle management, network slice template management, etc.; between network slice and network function Mapping; coordination of different types of network resources; coordination of network resources provided by different operators and different network providers, so that network resources provided by different network providers can meet the needs of target services, such as SLA requirements and key Requirements of Key Performance Indicator (KPI), requirements of Quality of Service (QoS), etc.; unified orchestration of network equipment provided by different vendors; external application program interface (API) Provided, wherein the API interface is used to provide network functions for third parties to implement deployment across operators.
  • network slice management such as network slice lifecycle management, network slice template management, etc.
  • network function Mapping between network slice and network function Mapping
  • coordination of different types of network resources coordination of network resources provided by different operators and different network providers, so that network resources provided by different network providers can meet the needs of target services, such as SLA requirements and key Require
  • the EM unit also known as the Network Function Manager (NF-M) unit, mainly includes: lifecycle management of network elements or network functions (such as instantiation, update, deletion, etc.); network element or network Functional FCAPS management, etc.
  • NF-M Network Function Manager
  • a network element which may include at least one of a core network element, an access network element, or a transport network element. It should be noted that the foregoing network unit may be replaced by a network function unit, or the network unit may have the function of a network function unit at the same time.
  • the "Network/NF" unit shown in FIG. 1 represents a unit having a function of a network unit and/or a function of a network function unit.
  • NFVO Network Function Virtualization Orchestration Unit
  • VNFM Virtual Network Function Management Unit
  • the main functions include but are not limited to: responsible for the allocation, scheduling, management, and orchestration of virtual resources; responsible for the life cycle management of virtualized network functions (VNF).
  • VNF virtual Network Function Management Unit
  • VIM can provide interfaces to upper-layer software, and manage lifecycle management, scheduling, distribution, loading and upgrading of virtual resources, and also manage dedicated hardware devices such as carrier-class data transmission, encryption and decryption.
  • NFVI Network Function Virtualization Infrastructure Solution
  • NFVI is a set of resources used to host and connect virtual functions.
  • NFVI is a cloud data center that contains servers, hypervisors, operating systems, virtual machines, virtual switches, and network resources.
  • OSS Operaations Support
  • NO unit can be deployed in the operation support system (Operations Support) In System, OSS)
  • the above SO unit or NO unit can also be deployed independently of the OSS.
  • OSS can be understood as a support system for device and network maintenance, responsible for network management of single vendors and network management of multiple vendors.
  • SO unit may be represented by SO, and the other units are similar, and will not be described again.
  • FIG. 2 illustrates a possible network architecture provided by an embodiment of the present invention.
  • the network architecture includes: a Business Support System (BSS)/Service Management Function, a cross-domain management unit (also called a network slice management unit, NSMF), and a domain management unit ( It can also be a network slicing subnet management unit.
  • the NSSMF includes a Core Network Domain Manager (CN-DM) unit, an Access Network Domain Manager (AN-DM) unit, and a transport domain management (Transport). Network Domain Manager, TN-DM) unit, etc.
  • the access network domain management unit may be a Radio Access Network Domain Manager (RAN-DM).
  • RAN-DM Radio Access Network Domain Manager
  • the domain management unit may also include any two or all of the core domain management unit, the access network domain management unit, and the transport network domain management unit.
  • BSS/SM is responsible for business-related management (including business operations, billing, customer relationship management, etc.) and providing services for terminals.
  • the BSS can also be replaced by a customer (Customer), or the BSS can have the functionality of the Customer at the same time.
  • Customer's functions include: business management, and providing corresponding services for the terminal.
  • BSS/Customer indicates a unit having a function of a BSS and/or a function of a Customer.
  • the network slice management unit may also be referred to as a Cross-Domain Slice Manager (CDSM) unit, a management function with Network Slice (NSL), and/or an NSL orchestration function.
  • CDSM Cross-Domain Slice Manager
  • NSL Management function with Network Slice
  • the NSMF may include some or all of the following functions: management of the NSL, such as lifecycle management of network slices, management of network slice templates, fault management of network slices, performance management of network slices, configuration management of network slices, etc.; NSL and Mapping between subnets, and mapping between NSL and network functions; network resources or Service Level Agreements (SLAs) provided by different subdomains (such as core, access, or transport) Coordination of information; sub-slices and network functions provided by each sub-domain are unified, which enables the sub-network slicing or network functions provided by each sub-domain to meet the requirements of the target service (for example, SLA requirements, key performance) Requirements for Key Performance Indicator (KPI) and requirements for Quality of
  • the network slice may also be referred to as an End to End (E2E) network slice, and includes at least one subnet, which may include at least a Core Network (CN) part and an Access Network (AN). a portion and a transport network (TN) portion; or, the network slice may include any one of a CN portion, an AN portion, or a TN portion; or, the network slice may represent a network slice of the CN portion, and an AN portion Network slice of the network slice or TN part.
  • the access network may be a Radio Access Network (RAN). It can be understood that the network slice involved in the embodiments of the present invention may also have other implementations. The embodiment of the invention is not limited.
  • the network slicing subnet management unit can also be a subnet management unit or a domain management unit.
  • the network slicing subnet in the text is collectively referred to as a subnet, and the network slicing subnet management unit unifies the Chen Wei subnet management unit.
  • a subnet is a logical network that is a collection of one or more network functions.
  • a subnet may only include a core network function or a network element or a subnet only includes an access network function or a subnet includes a transport network function or a network element or a subnet including an access network function. Two or all of the core network functions and the transport network functions.
  • the subnet management unit has subnet management, orchestration or design functions, including subnet lifecycle management (including creation, update, deletion, etc.), subnet fault management, subnet performance management, subnet configuration management, etc.
  • the subnet corresponds to the lifecycle management of the service, the fault management of the service, the performance management of the service, the configuration management of the service, and the coordination of the network resources in the subnet for unified orchestration.
  • the core network subnet management unit has subnet management functions in the core domain and/or subnet scheduling functions in the core domain.
  • the CN-NSSMF may include some or all of the following functions: management of subnets of network slices within the core domain, including, for example, subnet lifecycle management (including creation, update, deletion, etc.), subnet fault management, subnets Performance management, subnet configuration management, etc.; management of services in the core domain, including, for example, service lifecycle management, service fault management, service performance management, service configuration management, etc.; coordination of network resources within the core network domain, Used for unified orchestration.
  • the AN-NSSMF unit has subnet management functions within the access domain and/or subnet scheduling functions within the access domain.
  • the AN-NSSMF may include some or all of the following functions: management of subnets within the access domain, including subnet lifecycle management (including creation, update, deletion, etc.), subnet fault management, and subnet performance. Management, subnet configuration management, etc.; management of services within the access domain, including, for example, service lifecycle management, service fault management, service performance management, service configuration management, etc.; coordination of network resources within the access network domain, Used for unified orchestration.
  • the TN-NSSMF unit has a subnet management function in the transmission domain and/or a subnet scheduling function in the transmission domain.
  • the TN-NSSMF may include some or all of the following functions: management of subnets within the transport domain, including subnet lifecycle management (including creation, update, deletion, etc.), subnet fault management, and subnet performance management. Configuration management of subnets; management of services in the transport domain, including, for example, service lifecycle management, service fault management, service performance management, service configuration management, etc.; coordination of network resources in the transport domain for use in Unified arrangement.
  • the above NSMF, CN-NSSMF, AN-NSSMF, and TN-NSSMF may all be deployed in the SO or both in the NO; or, the above NSMF may be deployed in the NO, and the CN-NSSMF, AN-NSSMF, and TN-NSSMF may both be Deployed in EM; or, the above NSMF can be deployed in SO, CN-NSSMF, AN-NSSMF, and TN-NSSMF can all be deployed in NO, or NSMF, CN-NSSMF, AN-NSSMF, and TN-NSSMF are not deployed. In NO and SO.
  • the network slice subnet management unit may be a domain management unit that manages a single subnet; or may be a domain management unit that manages a hybrid subnet. In the latter case, the subnet managed by the domain management unit may include any two or all of CN, AN or TN.
  • the embodiment of the present application provides a method for managing a network slice template, including the following steps:
  • the first management unit receives a subnet management request, where the subnet management request carries the indication information of the subnet template.
  • the first management unit may be a Network Slice Subnet Management Function (NSSMF), a Network Slice Management Function, or any management unit with NSSMF or NSMF functions.
  • NSSMF Network Slice Subnet Management Function
  • the indication information of the subnet template is used to obtain the subnet template.
  • the first management unit locally stores the subnet template
  • the subnet template is stored in a database or a directory that the first management unit can access;
  • the first management unit acquires network service descriptor association information or a network service descriptor according to the indication information of the subnet template.
  • the first management unit acquires the network service instance according to the network service descriptor association information or the network service descriptor.
  • the first management unit may send a request for creating a network service instance to the NFVO, where the request carries the network service descriptor association information or the network service descriptor, and after the NFVO creates the corresponding network service instance, sends the network service instance information to the NFVO.
  • the first management network element specifically, obtaining the network service instance refers to acquiring the network service instance information.
  • the first management unit first sends a network service descriptor loading request to the NFVO, and then sends a network service creation request to the NFVO, where the request carries network service descriptor association information.
  • the first management unit sends a network service creation request to the NFVO, where the first management unit sends a network service instance identifier creation request to the NFVO, and then sends an instantiation request to the NFVO.
  • the first management unit can find out in the existing network whether there is an available network service instance, and if it is determined to be available, the network service instance can be used.
  • the first management unit determines, according to the network service descriptor or the network service instance information that the network service descriptor association information has been pre-stored locally, whether the network service instance is available;
  • the first management unit sends a network service instance information query request to the NFVO, where the request carries the network service descriptor association information or the network service description, and if the available network service instance information is returned, the network service instance that uses the information is determined.
  • the embodiment of the present invention can enable the first management unit to automatically obtain the network service instance during the network instance creation process, thereby improving the deployment efficiency of the network slice.
  • FIG. 4 to FIG. 7 are specific implementations of the network slice template provided by the present application. These specific solutions are further described below with reference to FIG. 4 to FIG. 7 .
  • Figure 4 shows an implementation of a network slice template provided by the present application.
  • the following reference numerals refer to the following network elements, NSMF, NSSMF, NFVO, and EM. It should be noted that the above-mentioned network elements are only exemplary for their functions. According to the description, in the specific process, some functions of each network element can be implemented by other network elements, for example, some functions of the NSMF can be implemented by NSSMF.
  • the NSMF receives a network slice creation/allocation/instantiation request or a service request, where the request carries network slice requirement information, where the network slice requirement information includes a service type or a network slice type (for example, enhancing mobile broadband (for example, Enhanced Mobile Broadband (eMBB), massive machine type communication (mMTC), service SLA, or network KPI (eg, latency, SLA requirements for a service or KPI for a network may include at least one of the following: Latency, report success ratio, command success ratio, coverage, capacity, reliability, or throughput.
  • the rate may refer to the proportion of successful uplink packet transmission; the delivery success rate may refer to the proportion of successful downlink packet transmission; the coverage may refer to the distribution area of the terminal; the capacity may refer to the number of terminals that can be accommodated;
  • the network slice request information further carries a network slice template identifier or a name, where the network slice template is used to deploy a network slice instance.
  • the name of the network slice template may also be a network slice descriptor or a network slice template.
  • the identifier or name of the network slice template is not limited herein.
  • the NSMF searches for a corresponding network slice template according to the network slice requirement information or the NST identifier, where the network slice template is preloaded into a database accessible by the NSMF or the NSMF.
  • the NSMF searches for a corresponding network slice template according to the network slice type, and different network slice types correspond to different network slice templates.
  • the NSMF analyzes the network slice template to obtain the identifier or name of the required subnet template NSST.
  • the network slice template includes an identifier or a name of the at least one subnet template.
  • the network slice template may further include an identifier or a name of the NSSMF corresponding to the subnet template.
  • the NSMF decomposes the network slice requirement information into each subnet requirement information.
  • the network slice requirement information may include a total-latency and a total-report success ratio, wherein, for convenience of description, a total-report success ratio is expressed below.
  • total-ratio other content related to the report success ratio can also be similarly expressed, and will not be described later.
  • total latency 10 milliseconds (ms)
  • total-ratio 96%.
  • the NSMF decomposes the network slice requirement information into each subnet requirement information, including
  • the CN subnet requirement information includes CN-latency and CN-ratio
  • the RAN subnet requirement information includes RAN-latency and RAN-ratio
  • the transport subnet requirement information includes TN-latency and TN-ratio.
  • CN-latency 3ms
  • RAN-latency 2ms
  • TN-latency 5ms
  • CN-ratio ⁇ RAN-ratio ⁇ TN-ratio 96%.
  • the NSMF sends a subnet management request to the corresponding NSSMF, where the subnet management request carries the identifier of the NSST and the corresponding subnet requirement information.
  • the subnet management request here may be a create request, an instantiation request, or a management request. Any of them.
  • the NSSMF obtains the corresponding NSST according to the identifier of the NSST, and obtains the association information of the NSD according to the subnet requirement information.
  • the association information of the NSD includes at least one of the following information:
  • Network service descriptor identifier or name (NSD Id/NSD name), network service deployment specification (NS flavor Id), network service instantiation level (nsInstantiationlevel), and the like.
  • the NSST includes the association information of the NSD corresponding to the different subnet requirement information values, and only the associated information of the NSD corresponding to the corresponding subnet requirement information needs to be matched.
  • the NSSMF obtains the association information of the NSD according to the association between the identifier of the NSST and/or the subnet requirement information and the association between the identifier of the locally maintained NSST and the association information of the NSD.
  • the NSSMF sends a request for the NS to the NFVO, where the request carries the associated information of the NSD. Specifically, the request may be sent to the NFVO by the Create NS Identifier, where the request carries the NSD ID, obtains the NS instance ID, and sends the NS to the NFVO. Instantiating a request, the request carrying NS flavor Id or nsInstantiationlevel, and the like.
  • NFVO creates the corresponding NS Instance, it returns the corresponding NS Instance Info (e.g.NS instance Id, VNF instance Id).
  • NS Instance Info e.g.NS instance Id, VNF instance Id.
  • the NSSMF maintains the association between the subnet instance ID and the NS Instance Id.
  • the NSSMF can maintain the association between the subnet instance ID and the NS flavor Id and ns Instantiationlevel.
  • the NSSMF creates a network slicing subnet instance NSSI.
  • the subnet instance in the text is equal to the network slicing subnet instance.
  • the managed object (MO) and the NS instance Id is configured in the MO.
  • the NS flavor Id needs to be configured.
  • nsInstantiationlevel and other parameters.
  • the NSSMF sends a Create NF MO request to the EM, where the request carries a VNF Instance Id.
  • the request further carries an NSSI MO Id or an NSSI Id.
  • EM creates NF MO, configures VNF instance ID in NF MO, and optionally configures NSSI MO Id. Return NF MO ID to NSSMF.
  • NSSMF configures the NF MO ID in the NSSI MO.
  • the NSSMF obtains the network service descriptor association information according to the indicated subnet requirement information and the subnet identifier, and obtains the network service instance association information by sending the network service descriptor association information to the NFVO, and simultaneously configures the service parameters to complete the automatic deployment of the subnet instance. .
  • FIG. 5 shows an implementation of another network slice template provided by the present application.
  • the NSSMF queries the current network to find out whether an available network service instance (NS) is available. Instance), if a matching network service instance is found, the existing network service instance can be used.
  • NS network service instance
  • the existing network service instance can be reused to provide utilization of virtual resources.
  • the NSSMF determines, according to the obtained association information of the NSD, whether the available NS isntance is available in the current network.
  • the network service instance information is maintained locally in the NSSMF.
  • the network service instance information may include NS instance Id, NSD Id, flavor Id, naInstantiation level, etc., and the NSSMF determines whether the match is matched, and if the match, the existing NS Instance is used.
  • step 506 is performed.
  • the NSSMF sends an NS Instance query request to the NFVO, where the request carries the NSD association information, including the NSD Id, the flavor Id, the naInstantiation level, and the NFVO determines whether the local NS Instance is available according to the NSD association information, and returns an available NS Instance. Id.
  • steps 505 and 506 have no specific order of execution. Step 505 may also be performed first. When the available NS isntance is not found locally, step 506 is performed.
  • FIG. 6 shows an implementation of a network slice template provided by the present application.
  • the main difference between this embodiment and the above embodiment is that the interaction body of the embodiment becomes an interaction between NSMF and NFVO.
  • step 401 for specific implementation steps of 603, reference may be made to step 401 in the foregoing embodiment, the difference being that the interaction subject becomes NSMF and NFVO.
  • steps 404-405 in the above embodiment, the difference being that the interaction subject changes NSMF and NFVO.
  • the NSMF sends an NSSI creation request or an NSSI MO creation request to the NSSMF, where the request carries network service instance information, where the network service instance information includes one or more of the following information: NS instance Id, NS flavor Id or nsInstantiationlevel.
  • NSMF is used to implement centralized management of NS instance information to ensure maximum utilization of network service instances.
  • FIG. 7 shows an implementation scheme of a network slice template provided by the present application, which is specifically implemented as follows:
  • the network slice subnet provider provides a subnet template NSST, where the NSST contains NSD information, and the following NSST contains an example of NSD information.
  • the subnet designer or operator loads/uploads the NSST to a database accessible by NSSMF or NSSMF or a database that NSSMF and NFVO can access simultaneously:
  • the NSSMF obtains the corresponding NSST according to the identifier of the NSST, and obtains the NSD according to the NSST subnet requirement information.
  • the NSST includes information about NSDs corresponding to different subnet requirement information values, and only needs to match the NSD corresponding to the corresponding subnet requirement information;
  • the NSD information includes at least one of the following information: a VNFD (Virtualzied Network Function Descriptor), a VLD (Virtualized Link Descriptor), and a PNFD (Physical Network Function Descriptor) function.
  • VNFD Virtualzied Network Function Descriptor
  • VLD Virtualized Link Descriptor
  • PNFD Physical Network Function Descriptor
  • the NSST further includes at least one of the following: an association between the VNFD and the application parameter, an association between the PNFD and the application parameter, an association between the VLD and the application parameter, an association between the VNFFGD and the application parameter, and a VNF profile and an application. Relationship of parameters, association between PNF profile and application parameters, VL Profile and application parameters connection relation.
  • association relationship between A and B herein refers to the same data structure in A and B, or the information of B in the data structure of A (eg flag) or the data structure of B contains A.
  • Information eg identification
  • the above application parameters may also refer to configuration scripts or files of application parameters.
  • the NSST further includes an association relationship between the performance parameter (e.g, SLA or KPI) and the Flavor ID, and/or an association between the performance parameter (e.g, SLA or KPI) and the nsInstantiationlevel.
  • the performance parameter e.g, SLA or KPI
  • the Flavor ID e.g., SLA or KPI
  • the performance parameter e.g, SLA or KPI
  • association relationship between A and B herein refers to the same data structure in A and B, or the information of B in the data structure of A (eg flag) or the data structure of B contains A.
  • Information eg identification
  • the NSSMF sends an NSD request to the NFVO, where the request carries the NSD.
  • the NSD loading request may be sent to the NFVO, and then the Create NS Identifier request is sent to the NFVO, where the request carries the NSD ID and obtains the NS instance ID.
  • the NS instantiation request is sent to the NFVO, and the request carries a flavor Id or an nsInstantiationlevel.
  • the NS instance is automatically deployed during the subnet deployment process to implement automatic network segmentation.
  • FIG. 8 shows an implementation of a network slice template provided by the present application, including the following steps:
  • the first management unit receives the subnet management request, where the subnet management request carries the indication information of the subnet template.
  • the first management unit is the NSSMF
  • the second management unit is the DM or the network function management unit. (egEM); or,
  • the second management unit is NSSMF.
  • the first management unit acquires application information according to the indication information of the subnet template.
  • An optional implementation manner is: the first management unit acquires a subnet template according to the indication information of the subnet template, the subnet template includes the application information, and the first management unit acquires the application information.
  • the application information herein may be a configuration file or a script.
  • the subnet template here may also be referred to as a network service descriptor.
  • the subnet template includes an association relationship between the at least one application information and network service requirement information (flavor Id and/or nsInstantiationLevel).
  • the subnet template includes an association relationship between at least one application information and network function information, where the network function information may be VNFD, VNF Profile, PNFD, PNF profile.
  • the network function information may be VNFD, VNF Profile, PNFD, PNF profile.
  • association relationship between A and B herein refers to the same data structure in A and B, or the information of B in the data structure of A (eg flag) or the data structure of B contains A.
  • Information for example, identification
  • the first management unit sends a subnet configuration request to the second management unit, where the subnet configuration request carries the application information.
  • the network service instance information may also be carried in the subnet configuration request.
  • the subnet template further includes at least one network function requirement information and association information of the application information.
  • the application information mentioned when talking about the subnet is for the application information of the entire subnet;
  • the network function is the application information mentioned, and it is for the application information of a given network function.
  • FIG. 8-1 is a schematic flowchart of the embodiment, where the first management unit is NFVO, and the second management unit is NSSMF, where
  • NFVO obtains NS demand information according to the NSST identifier
  • the NFVO obtains the NSST according to the identifier of the NSST, and the NSST includes the requirement information of the NS.
  • the NSST is pre-stored in a database accessible to NFVO or NFVO.
  • the requirement information of the NS is one or more of the following information: a deployment specification of the NS (NS Flavor Id), and an instantiation level of the NS (NS Instantiation level).
  • the NS requirement information further includes network function requirement information, where the network function requirement information is at least one of the following: a network function descriptor (including a virtual network function description and a physical network function descriptor), and a virtual network function requirement VNF Profile, physical network function virtual information (PNF Profile), network function deployment specification (VNF Flavor ID).
  • a network function descriptor including a virtual network function description and a physical network function descriptor
  • VNF Profile virtual network function requirement
  • PNF Profile physical network function virtual information
  • VNF Flavor ID network function deployment specification
  • the NFVO instantiates or creates an NS instance according to the NS requirement information, and obtains the NS instance information.
  • the NS instance information includes at least one of the following information: an NS instance identifier, a VNF instance identifier, and a PNF instance identifier.
  • NFVO obtains application information according to the identifier of the NSST. Specifically, the NFVO acquires the NSST according to the identity of the NSST, and the NSST is pre-stored in data accessible by the NFVO or NFVO.
  • the NFVO sends a configuration request to the NSSMF or the EM, where the request carries the NS instance information and information, where the application information may be at least one of the following information: an application parameter, an application parameter configuration script, or an application parameter file.
  • the configuration request may be at least one of the following: an NSSI configuration request, an NF configuration request, an NSSI MO creation request, an NF MO creation request, an NSSI MO configuration request, and an NF MO configuration request.
  • the NSSMF or EM configures corresponding application information according to the configuration request.
  • the NSSMF configures corresponding application information to the corresponding NSSI
  • the NSSMF when configuring the configuration request of the NF at the request, the NSSMF configures corresponding application information to the corresponding NF;
  • the NSSMF when configuring the configuration request of the NSSI MO at the request, the NSSMF configures corresponding application information to the corresponding NSSI MO;
  • the NSSMF configures corresponding application information to the corresponding NF MO
  • the NSSMF creates a corresponding NSSI MO and configures corresponding application information
  • the NSSMF creates a corresponding NF MO and configures corresponding application information
  • FIG. 9A shows a possible structural diagram of the first management unit involved in the above embodiment.
  • the first management unit 900 includes a processing module 902 and a communication module 903.
  • the processing module 902 is configured to perform control management on the action of the first management unit.
  • the processing module 902 is configured to support the first management list.
  • the elements perform the steps of Figures 3 through 8 or other steps of the steps for the techniques described herein.
  • the communication module 903 is configured to support communication between the first management unit and other network entities, such as communication with the second management unit.
  • the first management unit may further include a storage module 901 for storing program codes and data of the first management unit.
  • the processing module 902 can be a processor or a controller, and can be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication module 903 can be a communication interface, a transceiver, a transceiver circuit, etc., wherein the communication interface is a collective name and can include one or more interfaces.
  • the storage module 901 can be a memory.
  • the first management unit involved in the embodiment of the present invention may be the first management unit shown in FIG. 9B.
  • the first management unit 910 includes a processor 912, a communication interface 913, and a memory 911.
  • the first management unit 910 may further include a bus 914.
  • the communication interface 913, the processor 912, and the memory 911 may be connected to each other through a bus 914.
  • the bus 914 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (abbreviated). EISA) bus and so on.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus 914 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 9B, but it does not mean that there is only one bus or one type of bus.
  • the first management unit shown in FIG. 9A or FIG. 9B above may be a network slice subnet management function NSSMF, a network slice management function, or another management unit having NSSMF or NSMF functions.
  • FIG. 10A shows a possible structural diagram of the second management unit involved in the above embodiment.
  • the second management unit 1000 includes a processing module 1002 and a communication module 1003.
  • the processing module 1002 is configured to control the management of the actions of the second management unit.
  • the processing module 1002 is configured to support the second management unit to perform the processes of FIGS. 8-9 and/or for the techniques described herein.
  • the communication module 1003 is configured to support communication between the second management unit and the first management unit or other network entity.
  • the second management unit may further include a storage module 1001 for storing program codes and data of the second management unit.
  • the processing module 1002 may be a processor or a controller, such as a CPU, a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication module 1003 may be a communication interface, a transceiver, a transceiver circuit, etc., wherein the communication interface is a collective name and may include one or more interfaces.
  • the storage module 1001 may be a memory.
  • the second management unit may be the second management unit shown in FIG. 10B.
  • the second management unit 1010 includes: a processor 1012, a communication interface 1013, and a memory. 1011.
  • the second management unit 1010 may further include a bus 1014.
  • the communication interface 1013, the processor 1012, and the memory 1011 may be connected to each other through a bus 1014; the bus 1014 may be a PCI bus or an EISA bus or the like.
  • the bus 1014 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in FIG. 10B, but it does not mean that there is only one bus or one type of bus.
  • the second management unit shown in FIG. 10A or FIG. 10B above may be an NSSMF, DM or network function management unit (e.g. EM);
  • the steps of the method or algorithm described in connection with the disclosure of the embodiments of the present invention may be implemented in a hardware manner, or may be implemented by a processor executing software instructions.
  • the software instructions may be composed of corresponding software modules, which may be stored in a random access memory (RAM), a flash memory, a read only memory (ROM), an erasable programmable read only memory ( Erasable Programmable ROM (EPROM), electrically erasable programmable read only memory (EEPROM), registers, hard disk, removable hard disk, compact disk read only (CD-ROM) or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC.
  • the ASIC may be located in the first management unit and the second management unit.
  • the processor and the storage medium may also exist as discrete components in the first management unit and the second management unit.
  • the functions described in the embodiments of the present invention may be implemented in hardware, software, firmware, or any combination thereof.
  • the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium.
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

Abstract

本申请实施例公开了一种网络切片模板的管理方法。该方法包括第一管理单元接收子网管理请求，所述子网管理请求携带子网模板的指示信息，第一管理单元根据该子网模板的指示信息获取网络服务描述符关联信息或者网络服务描述符，第一管理单元根据所述网络服务描述符关联信息或者网络服务描述符获取网络服务实例。本申请提供的网络切片模板的管理方法，可以使第一管理单元在网络实例创建过程中自动获取网络服务实例，提高了网络切片的部署效率。

Description

一种网络切片的管理方法、单元和系统 技术领域
本申请涉及通信领域，具体涉及一种网络切片的管理方法、单元和系统。
背景技术
传统蜂窝网一刀切的网络架构，带有专用的支持和IT系统，非常适合单一服务型的网络。然而，这种垂直架构难以扩展电信网络，也很难根据不断变化的用户需求进行调整并满足新型应用的需求。在未来的移动通信系统中，将采用基于逻辑而不是基于物理资源的技术，网络将被进一步抽象为网络切片(Network Slice)，这种连接服务是通过许多定制软件实现的功能定义，可以使运营商将网络作为一种服务提供给用户，即运营商能够将实体网络以网络即服务的形式提供连接服务，满足人们对于更多网络用例的广泛需求。
网络切片的关键是网络功能的虚拟化(Network Function Virtualization，NFV)，所谓NFV就是将网络中的专用设备的软硬件功能转移到虚拟主机上。自动化部署是网络切片管理的一个主要特性，所谓网络切片的自动化部署就是线下设计和规划网络，生成网络切片模板，在线根据网络切片模板实时生成网络切片实例。由于网络切片包括至少一个网络切片子网(Network Slice Subnet)，而一个网络切片子网包括至少一个网络服务(Network Service，NS)，而一个网络服务又包括至少一个虚拟网络功能(Virtualized Network Function，VNF)，所以网络切片实例包括至少一个网络切片子网实例(Network Slice Subnet Instance,NSSI)，网络切片子网实例包括至少一个网络服务实例(NS Instance)，网络服务实例又至少包括一个VNF实例。网络切片和网络切片子网都是由应用(应用配置参数)和虚拟资源两部分组成，所现有技术中的NFV管理和编排系统(Management and Orchestration，MANO)架构如图1A所示，其中网络功能虚拟化管理(Network Function Virtualization Orchestrator，NFVO)单元能够对网络服务进行自动部署和管理，具体为NFVO根据网络服务描述符(Network Service Descriptor，NSD)自动部署NS实例，包括实例化对应的VNF实例以及建立VNF实例之间的连接，由于MANO只能对虚拟资源部分进行实例化，所以NFVO创建的NS实例仅包括网络切片或者网络切片子网的虚拟资源部分。
现有的技术中，人工指定网络的资源需求信息来部署网络实例，再根据获取的网络实例信息决定如何配置业务参数，无法自动部署网络实例并配置业务参数，进行自动提供业务。可见，现有的网络实例部署流程复杂，人工干预度高，部署效率低。
发明内容
本申请提供一种网络切片模板的管理方法、装置，用以解决现有网络实例部署复杂，需要高度人工干预的问题。
一方面，本申请提供一种网络切片模板的管理方法，该方法包括：
第一管理单元接收子网管理请求，所述子网管理请求携带子网模板的指示信息；其中，第一管理网元可以为网络切片子网管理功能(Network Slice Subnet management Function,NSSMF)，网络切片管理功能(Network Slice Management Function,NSMF)，或其他具有NSSMF或者NSMF功能的管理单元；第一管理单元根据该子网模板的指示信息获取网络服务描述符关联信息或者网络服务描述符；第一管理单元根据所述网络服务描述符关联信息或者网络服务描述符获取网络服务实例。具体实现中，第一管理单元根据网络服务描述符关联信息或者网络服务描述符获取网络服务实例信息，然后通过该网络服务实例信息来获取网络服务实例。具体实现中，第一管理单元根据所述网络服务描述符关联信息或者网络服务描述符获取网络服务实例可以指第一管理单元根据所述网络服务描述符关联信息或者网络服务描述符获取网络服务实例信息。
结合第一方面，在第一种可能的实现方式中，第一管理单元可以根据子网模板指示信息获取所述子网模板，子网模板中包含网络服务描述的关联信息或者网络服务描述符。第一管理单元还可以通过如下方式来获取子网模板，例如，第一管理单元本地存储有子网模板；第一管理单元根据本地维护的子网模板指示信息和子网模板的关联关系查找到相应的子网模板；或，第一管理单元可以访问的数据库或者目录中存储的子网模板来获取需要的子网模板。
通过查询到本地存储有匹配的子网模板，可以提高网络实例的部署效率，省去来回查询所消耗的时延。
根据第一方面或第一方面的第一种可能的实现方式，在第一方面的第二种可能的实现方式中，子网管理请求中还携带子网需求信息；第一管理单元根据所述子网需求信息和所述子网模板指示信息获取网络服务描述符的关联信息或者网络服务描述符。
根据第一方面或第一方面的第一种或第二种可能的实现方式，在第一方面的第三种可能的实现方式中，网络服务描述符关联信息可以包括以下信息中的一种或多种：网络服务描述符的标识，部署规格，实例化等级，厂商信息，版本信息。
根据第一方面或第一方面的第一种至第三种任一种可能的实现方式，在第一方面的第四种可能的实现方式中，第一管理单元接收子网管理请求后，根据子网模板创建子网实例或子网实例的管理对象；或，第一管理单元根据子网模板向第三管理单元发送创建请求，所述创建请求用于创建子网实例或者子网实例的管理对象。第三管理单元可以为网络管理单元(Network Manager，NM)，网元管理单元(Element Manager，EM)，域管理单元(Domain Manager，DM)或运营支撑系统(Operator Support System，OSS)。当第一管理单元是NSMF时，第二管理单元可以是NSSMF。
根据第一方面或第一方面的第一种至第四种任一种可能的实现方式，在第一方面的第五种可能的实现方式中，第一管理单元可以关联子网实例和网络服务实例，或第一管理单元关联子网实例和子网实例的管理对象。通过自动关联子网实例或子网实例管理对象和网络服务实例，可以部署一个完整的网络实例，并提供业务或者服务。
根据第一方面或第一方面的第一种至第五种任一种可能的实现方式，在第一方面的第 六种可能的实现方式中，第一管理单元在管理对象中配置网络服务实例信息，所述网络服务实例信息可以包括以下信息中的至少一个：网络服务实例标识、网络服务实例规格和网络服务实例实例化等级。
本申请可以使第一管理单元在网络实例创建过程中自动获取网络服务实例，提高了网络切片的部署效率。
第二方面，本申请提供一种网络切片模板的管理方法，该方法包括：第一管理单元接收子网管理请求，该子网管理请求携带子网模板的指示信息；第一管理单元根据所述子网模板的指示信息获取应用信息；第一管理单元向第二管理单元发送子网配置请求，所述子网配置请求中携带所述应用信息。
根据第二方面，在第二方面的第一种可能的实现方式中，第一管理单元根据子网模板的指示信息获取子网模板，所述子网模板包含所述应用信息,该第一管理单元由此获取该应用信息。这里的子网模板也可以称为网络服务描述符,应用信息可以是应用参数、配置文件、管理对象属性值或者脚本。
根据第二方面或第二方面的第一种可能的实现方式，在第二方面的第二种可能的实现方式中，所述子网配置请求中还携带网络服务实例信息。网络服务实例信息包括以下信息中的一种或者多种：网络服务实例标识、网络服务实例部署规格、网络服务实例实例化等级、虚拟网络功能实例标识、虚拟网络功能实例部署规格。
根据第二方面的第一或第二种可能的实现方式，在第二方面的第三种可能的实现方式中，子网模板包含所述子网模板的性能信息和网络服务需求信息的关联关系，所述关联关系用于确定所述网络服务需求信息,所述网络服务需求信息包括以下信息中的至少一种：网络服务部署规格,网络服务实例化等级，所述网络服务需求信息用于获取所述网络服务实例信息。
根据第二方面的第一至第三种任一种可能的实现方式，在第二方面的第四种可能的实现方式中，子网模板包括网络功能需求信息和应用信息的关联信息，其中网络功能需求信息可以包括以下信息中的一种或多种：虚拟网络功能描述符(Virtualized Network Function Descriptor,VNFD),虚拟网络功能需求信息(Virtualzied Network Function Profile,VNF Profile),虚拟网络功能部署规格(Virtualized deployment flavor ID，VNF flavor ID)。
相较于现有技术，本申请可以使第一管理单元在网络服务实例的创建过程中自动部署应用参数，提高了网络切片的部署效率。
另一方面，本发明实施例提供一种第一管理单元，该第一管理单元具有实现上述方法示例中第一管理单元各行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，第一管理单元的结构中包括处理器和通信接口，所述处理器被配置为支持第一管理单元执行上述方法中相应的功能。进一步的，第一管理单元还可以包括存储器，所述存储器用于与处理器耦合，其保存第一管理单元必要的程序指令和数据。
再一方面，本发明实施例提供一种通信系统，该系统包括上述方面所述的第一管理单 元和第二管理单元。
再一方面，本发明实施例提供一种计算机存储介质，用于储存为上述用于第一管理单元所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
相较于现有技术，本申请实施例公开了一种网络切片模板的管理方法。该方法包括第一管理单元接收子网管理请求，所述子网管理请求携带子网模板的指示信息，第一管理单元根据该子网模板的指示信息获取网络服务描述符关联信息或者网络服务描述符，第一管理单元根据所述网络服务描述符关联信息或者网络服务描述符获取网络服务实例。本申请提供的网络切片模板的管理方法，可以使第一管理单元在网络实例创建过程中自动获取网络服务实例，提高了网络切片的部署效率。
附图说明
图1为现有技术中的一种NFV的MANO的网络架构的示意图；
图2为本发明实施例提供的一种可能的网络架构的示意图；
图3为本发明实施例提供的一种网络切片模板的管理方法的流程示意图；
图4为本发明实施例提供的又一种网络切片管理方法的通信示意图；
图5为本发明实施例提供的再一种网络切片管理方法的通信示意图；
图6为本发明实施例提供的再一种网络切片管理方法的通信示意图；
图7为本发明实施例提供的再一种网络切片管理方法的通信示意图；
图7-1为本发明实施例提供的一种子网模板的示意图；
图8为本发明实施例提供的再一种网络切片管理方法的流程示意图；
图8-1为本发明实施例提供的再一种网络切片管理方法的流程示意图
图9A为本发明实施例提供的一种第一管理单元的示意性框图；
图9B为本发明实施例提供的一种第一管理单元的结构示意图；
图10A为本发明实施例提供的一种第二管理单元的示意性框图；
图10B为本发明实施例提供的一种第二管理单元的结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行描述。
图1为本发明实施例提供的一种可能的应用场景的示意图。其中，图1所示的应用场景中至少包括业务编排(Service Orchestrator，SO)单元、网络编排(Network Orchestrator，NO)单元、网元管理(Element Manager，EM)单元和网络(Network)单元/网络功能(Network Function，NF)单元，网络功能虚拟化编排单元(Network Function Virtualization Orchestration,NFVO)，虚拟网络功能管理单元(Virtualized Network Function Manager,VNFM)。下面对 图1中所涉及的各个单元作简单介绍：
SO单元，也可以称为业务编排和管理单元或业务管理单元，其功能主要包括：根据业务请求消息对业务(service)进行生命周期管理(例如实例化、更新、删除等)；service聚合；service的管理，例如service的故障、配置、计费、性能和安全(Fault,Configuration,Accounting,Performance,Security，FCAPS)管理；以及service和网络切片(network slice)之间的映射等。其中，service可以是一组用户能享有的指定服务水平协议(Service Level Agreement，SLA)的通信业务，例如移动宽带(Mobile Broadband，MBB)业务、语音业务、以及物联网(Internet of Things，IOT)业务(例如，智能停车业务、智能抄表业务等)等。示例性的，SO单元可以对网络切片所承载的业务进行管理。
NO单元，也可以称为网络编排和管理单元或网络管理单元，其功能主要包括：网络切片的管理，例如网络切片的生命周期管理、网络切片模板的管理等；网络切片和网络功能之间的映射；不同类型的网络资源的协调；不同运营商、不同网络供应商所提供的网络资源的协调，以使得不同网络供应商所提供的网络资源可以满足目标业务的需求，例如SLA的要求、关键性能指标(Key Performance Indicator，KPI)的要求、服务质量(Quality of Service，QoS)的要求等；不同供应商所提供的网络设备的统一编排；对外的应用程序接口(Application Program Interface，API)的提供，其中该API接口用于为第三方提供网络功能，以实现跨运营商的部署。
EM单元，也可以称为网络功能管理(Network Function Manager，NF-M)单元，其功能主要包括：网元或网络功能的生命周期管理(例如实例化、更新、删除等)；网元或网络功能的FCAPS管理等。
网络单元，其可以包括核心网单元、接入网单元或传输网单元中的至少一种。需要说明的是，上述网络单元可以由网络功能单元所替代，或者，上述网络单元可以同时具有网络功能单元的功能。图1中所示的“Network/NF”单元表示具有网络单元的功能和/或网络功能单元的功能的单元。
网络功能虚拟化编排单元(NFVO),主要功能包括但不仅限于：
负责虚拟资源的分配、调度、管理、和编排；负责网络服务(Network Service，NS)的生命周期管理、故障管理、性能管理、配置管理。
虚拟网络功能管理单元(VNFM)，主要功能包括但不仅限于：负责虚拟资源的分配、调度、管理、和编排；负责虚拟网络功能(Virtualized Network Function，VNF)的生命周期管理。
VIM，可以提供接口给上层软件，并对虚拟资源进行生命周期管理、调度、分配、加载升级等，同时也对电信级数据传输、加解密等专用硬件设备进行管理。
网络功能虚拟化基础设施解决方案(Network Function Virtualization Infrastructure Solution，NFVI)从理论层次上来讲，NFVI是用来托管和连接虚拟功能的一组资源。具体来说就是，NFVI是一种包含服务器、虚拟化管理程序(hypervisor)、操作系统、虚机、虚拟交换机和网络资源的云数据中心。
需要说明的是，上述SO单元或NO单元可以部署在运营支撑系统(Operations Support  System，OSS)中，上述SO单元或NO单元也可以独立于OSS部署。其中，OSS可以理解为面向设备和网络维护的支撑系统，负责单厂商的网络管理和多厂商的网络管理。
可以理解的是，上述对各个单元的功能介绍仅仅是一些举例说明，各个单元还可以具有其他功能，本发明实施例并不限定。
为描述方便，下文中，某一单元可以由其英文缩写所表示，例如，SO单元可以用SO表示，其它单元类似，后续不再赘述。
基于上述应用场景，图2示出了本发明实施例提供的一种可能的网络架构。如图2所示，该网络架构包括：业务支撑系统(Business Support System，BSS)/业务管理单元(Service Management Function)、跨域管理单元(也叫网络切片管理单元，NSMF)、域管理单元(也可以网络切片子网管理单元，NSSMF包括核心网域管理(Core Network Domain Manager，CN-DM)单元、接入网域管理(Access Network Domain Manager，AN-DM)单元和传输网域管理(Transport Network Domain Manager，TN-DM)单元等。示例性的，接入网域管理单元可以是无线接入网域管理单元(Radio Access Network Domain Manager，RAN-DM)。
可选，域管理单元也可以同时包含同时实现核心网域管理单元,接入网域管理单元，传输网域管理单元中的任意两个或者全部。
下面分别对BSS、NSMF、NSSMF(包括CN-NSSMF、AN-NSSMF和TN-NSSMF作简单介绍。
BSS/SM负责业务相关的管理(例如包括业务的运营、计费、客户关系管理等)，以及为终端提供业务。图2所示的网络架构中，BSS也可以由客户(Customer)所替代，或者，BSS可以同时具有Customer的功能。其中，Customer的功能包括：业务管理，以及为终端提供相应的业务。图2中，“BSS/Customer”表示具有BSS的功能和/或Customer的功能的单元。
NSMF，网络切片管理单元，也可以称为跨域的切片管理(Cross-Domain Slice Manager，CDSM)单元、具有网络切片(Network Slice，NSL)的管理功能和/或NSL的编排功能。例如，NSMF可以包括以下部分或全部功能：NSL的管理，例如网络切片的生命周期管理、网络切片模板的管理、网络切片的故障管理、网络切片的性能管理和网络切片的配置管理等；NSL与子网之间的映射，以及NSL与网络功能之间的映射；不同子域(例如核心网域、接入网域或传输网域)提供的网络资源或服务水平协议(Service Level Agreement，SLA)信息的协调；各子域所提供的子网切片和网络功能的统一编排，该统一编排能使得各子域提供的子网切片或网络功能满足目标业务的需求(例如，SLA的要求、关键性能指标(Key Performance Indicator，KPI)的要求以及服务质量(Quality of Service，QoS)的要求等)。
其中，上述网络切片也可以称为端到端(End to End，E2E)网络切片，至少包括一个子网，其可以至少包括核心网(Core Network，CN)部分、接入网(Access Network，AN)部分和传输网(Transport Network，TN)部分；或者，上述网络切片可以包括CN部分、AN部分或TN部分中的任意两项；或者，上述网络切片可以表示CN部分的网络切片、AN部分的网络切片或TN部分的网络切片。其中，上述接入网可以是无线接入网(Radio Access Network，RAN)。可以理解的是，本发明实施例所涉及的网络切片还可能具有其他实施方 式，本发明实施例并不限定。
NSSMF，网络切片子网管理单元，也可以成为子网管理单元或者域管理单元，为了简便，文中网络切片子网统一称为子网，网络切片子网管理单元统一陈伟子网管理单元。所谓子网是一个逻辑网络，是一个或者多个网络功能的集合。可选地、一个子网可以只包含核心网网络功能或者网元或者一个子网只包含接入网网络功能或者一个子网包含传输网网络功能或者网元或者一个子网包括接入网网络功能、核心网网络功能、传输网网络功能中的两中或者全部。子网管理单元具有子网管理、编排或者设计的功能，包括子网的生命周期管理(包括创建、更新、删除等)、子网的故障管理、子网的性能管理、子网的配置管理等；子网对应业务的生命周期管理、业务的故障管理、业务的性能管理、业务的配置管理等；子网内网络资源的协调，以用于统一编排。
CN-NSSMF，核心网子网管理单元，，有核心网域内子网管理功能和/或核心网域内子网编排功能。例如，CN-NSSMF可以包括以下部分或全部功能：核心网域内网络切片的子网的管理，例如包括子网的生命周期管理(包括创建、更新、删除等)、子网的故障管理、子网的性能管理、子网的配置管理等；核心网域内业务的管理，例如包括业务的生命周期管理、业务的故障管理、业务的性能管理、业务的配置管理等；核心网域内网络资源的协调，以用于统一编排。
AN-NSSMF单元，具有接入网域内子网管理功能和/或接入网域内子网编排功能。例如，AN-NSSMF可以包括以下部分或全部功能：接入网域内子网的管理，例如包括子网的生命周期管理(包括创建、更新、删除等)、子网的故障管理、子网的性能管理、子网的配置管理等；接入网域内业务的管理，例如包括业务的生命周期管理、业务的故障管理、业务的性能管理、业务的配置管理等；接入网域内网络资源的协调，以用于统一编排。
TN-NSSMF单元，具有传输网域内子网管理功能和/或传输网域内子网编排功能。例如，TN-NSSMF可以包括以下部分或全部功能：传输网域内子网的管理，例如包括子网的生命周期管理(包括创建、更新、删除等)、子网的故障管理、子网的性能管理、子网的配置管理等；传输网域内业务的管理，例如包括业务的生命周期管理、业务的故障管理、业务的性能管理、业务的配置管理等；传输网域内网络资源的协调，以用于统一编排。
上述NSMF、CN-NSSMF、AN-NSSMF和TN-NSSMF可以都部署在SO中或都部署在NO中；或者，上述NSMF可以部署在NO中，CN-NSSMF、AN-NSSMF和TN-NSSMF可以都部署在EM中；或者，上述NSMF可以部署在SO中，CN-NSSMF、AN-NSSMF和TN-NSSMF可以都部署在NO中，或者NSMF、CN-NSSMF、AN-NSSMF和TN-NSSMF都不部署在NO和SO中。
此外，上述网络切片子网管理单元可以是管理单一子网的域管理单元；也可以是管理混合子网的域管理单元。在后一种情况下，域管理单元管理的子网可以包括CN、AN或TN中的任意两个或者全部。
下面基于本申请实施例涉及的共性方面，对本申请方案进行说明。
如图3所示，本申请实施例提供一种网络切片模板的管理方法，包括如下步骤：
S301：第一管理单元接收子网管理请求，该子网管理请求携带子网模板的指示信息；
其中第一管理单元可以为网络切片子网管理功能(Network Slice Subnet management Function,NSSMF)、网络切片管理功能(Network Slice Management Function)或者任何具有NSSMF或者NSMF功能的管理单元。子网模板的指示信息用于获取所述子网模板。
可选地，第一管理单元本地存储子网模板；
可选地，第一管理单元可以访问的数据库或者目录中存储子网模板；
S302：第一管理单元根据子网模板的指示信息获取网络服务描述符关联信息或者网络服务描述符；
S303：第一管理单元根据网络服务描述符关联信息或者网络服务描述符获取网络服务实例。
第一管理单元可以向NFVO发送创建网络服务实例的请求，所述请求中携带网络服务描述符关联信息或者网络服务描述符，NFVO创建好相应的网络服务实例后，将该网络服务实例信息发给第一管理网元；具体地，获取网络服务实例指的是获取网络服务实例信息。
可选地、第一管理单元先向NFVO发送网络服务描述符加载请求，再向NFVO发送网络服务创建请求，请求中携带网络服务描述符关联信息。
可选地、第一管理单元向NFVO发送网络服务创建请求包括，第一管理单元向NFVO发送网络服务实例标识创建请求，再向NFVO发送实例化请求。
另一种可行的方案为：第一管理单元可以在现网中查找是否有可用的网络服务实例，如确定可用，则可以使用该网络服务实例。
第一管理单元根据网络服务描述符或者网络服务描述符关联信息已经本地预存的网络服务实例信息，判断是否可用的网络服务实例；
可选地、第一管理单元向NFVO发送网络服务实例信息查询请求，请求中携带网络服务描述符关联信息或者网络服务描述，如果返回可用的网络服务实例信息，则确定使用信息的网络服务实例。
所以本发明实施例可以使第一管理单元在网络实例创建过程中自动获取网络服务实例，提高了网络切片的部署效率。
图4～图7分别为本申请提供的网络切片模板的具体实现方案，下面结合图4～图7对这些具体方案做进一步说明。
图4示出了本申请提供的一种网络切片模板的实现方案，附图中涉及以下网元，NSMF，NSSMF，NFVO，EM，需要说明的是：以上涉及的网元只是对其功能示例性的进行说明，在具体过程过程中，各网元的部分功能可以通过其他网元来实现，例如NSMF的部分功能，可以通过NSSMF来实现。
具体实现如下：
401：NSMF收到网络切片创建/分配/实例化请求或者业务请求，所述请求中携带网络切片需求信息，这里的网络切片需求信息包含业务类型或者网络切片类型(例如.例如，增强移动宽带(enhanced Mobile Broadband，eMBB)、海量机器类通信(massive Machine Type Communication，mMTC)、业务SLA或者网络KPI(例如，时延(latency)，业务的SLA要求或网络的KPI可以包括以下至少一项：时延(latency)、上报成功率(report success ratio)、下发成功率(command success ratio)、覆盖(coverage)、容量(capacity)、可靠性(reliability)或吞吐量(throughput)。其中，上报成功率可以指上行包发送成功的比例；下发成功率可以指下行包发送成功的比例；覆盖可以指终端的分布区域；容量可以指可容纳的终端数量。；
可选地，网络切片需求信息中还携带网络切片模板标识或者名称，所述网络切片模板用于部署网络切片实例。网络切片模板的名字也可以是网络切片描述符或者网络切片蓝本，此处对于网络切片模板的标识或名称不做限定。
402：NSMF根据网络切片需求信息或者NST标识查找相应的网络切片模板，所述网络切片模板预先加载到NSMF或者NSMF可以访问的某个数据库里。
举个例子，NSMF根据网络切片类型查找相应的网络切片模板，不同的网络切片类型对应不同的网络切片模板。
NSMF分析所述网络切片模板，获取所需的子网模板NSST的标识或者名称。其中，网络切片模板中包含至少一个子网模板的标识或者名称，可选地，网络切片模板中还可以包括子网模板对应的NSSMF的标识或者名称。
NSMF分解所述网络切片需求信息为各子网需求信息，在一个示例中，网络切片需求信息可以包括total-latency和total-report success ratio，其中，为描述方便，下文中total-report success ratio表示为total-ratio，其它与report success ratio相关的内容也可以类似表示，后续不在赘述。例如，total latency＝10毫秒(ms)，total-ratio＝96％。
NSMF分解所述网络切片需求信息为各子网需求信息，包括
在一个示例中，CN子网需求信息包括CN-latency和CN-ratio，RAN子网需求信息包括RAN-latency和RAN-ratio，传输子网需求信息包括TN-latency和TN-ratio。例如，CN-latency＝3ms，RAN-latency＝2ms，TN-latency＝5ms；CN-ratio×RAN-ratio×TN-ratio＝96％。
403：NSMF向相应的NSSMF发送子网管理请求，所述子网管理请求中携带NSST的标识和对应的子网需求信息.这里的子网管理请求，可以是创建请求、实例化请求、管理请求中的任一个。
404:NSSMF根据NSST的标识获取相应的NSST，根据子网需求信息得到NSD的关联信息，NSD的关联信息包括如下信息中的至少一种：
网络服务描述符标识或者名称(NSD Id/NSD name)，网路服务部署规格(NS flavor Id)，网络服务实例化等级(nsInstantiationlevel)等。
具体地，如图4所述，NSST中包含了不同的子网需求信息值对应的NSD的关联信息，这里只需要匹配相应的子网需求信息对应的NSD的关联信息就可以。
可选地，NSSMF根据NSST的标识和/或子网需求信息和本地维护的NSST的标识和NSD的关联信息的关联关系获取NSD的关联信息。
405：NSSMF向NFVO发送NS的创请求，所述请求中携带NSD的关联信息.具体地，可以是向NFVO发送Create NS Identifier请求，请求中携带NSD ID，获取NS instance ID，再向NFVO发送NS实例化请求，所述请求中携带NS flavor Id或者nsInstantiationlevel等。
406：NFVO创建好相应的NS Instance之后，返回相应的网络服务实例信息(NS Instance Info)(e.g.NS instance Id，VNF instance Id)。
407：NSSMF关联子网实例和网络服务实例。
NSSMF维护子网实例标识和NS Instance Id的关联关系，可选地，除了NS Instance Id，NSSMF还可以维护子网实例标识和还有NS flavor Id、ns Instantiationlevel等的关联关系；或者
NSSMF创建网络切片子网实例NSSI，文中所说的子网实例等于网络切片子网实例)管理对象(Managed Object，MO)，在MO中配置NS instance Id，可选地，还需要配置NS flavor Id，nsInstantiationlevel等参数。
408：NSSMF向EM发送Create NF MO请求，所述请求中携带VNF Instance Id,可选地，请求中还携带NSSI MO Id或者NSSI Id。
409：EM创建NF MO，在NF MO中配置VNF instance ID，可选地，配置NSSI MO Id。返回NF MO ID到NSSMF。
410：NSSMF在NSSI MO中配置NF MO ID。
通过NSSMF根据所示子网需求信息和子网标识获取网络服务描述符关联信息，通过向NFVO发送网络服务描述符关联信息进而获取相应的网络服务实例，同时配置业务参数，完成子网实例的自动化部署。
图5示出了本申请提供的另一种网络切片模板的实现方案，本实施例在和上一实施例的主要不同在于NSSMF是通过先在现网中查询是否有可用的网络服务实例(NS instance)，如找到匹配的网络服务实例，则可以使用该现有的网络服务实例。
相比于上一实施例提供的方案，可以重用现有网络服务实例，提供虚拟资源的利用率。
下面结合图5，具体来描述，和上一实施例相同或类似的步骤，本实施例不在赘述。
501-504的具体实现可参考上一实施例中的步骤401-404。
505：NSSMF根据获取的NSD的关联信息判断现网中是否有可用的NS isntance。在NSSMF本地维护网络服务实例信息，网络服务实例信息可以包括NS instance Id，NSD Id，flavor Id，naInstantiationlevel等，NSSMF判断是否匹配，如果匹配则使用该现有的NS Instance。
例如，判断是否匹配可以根据NSD的关联信息和本地维护的NS实例信息是否一致，如果一致则认为匹配上，不一致则认为不匹配。
可选地、执行步骤506，
506：NSSMF向NFVO发送NS Instance查询请求，所述请求中携带NSD的关联信息，包括NSD Id，flavor Id，naInstantiationlevel，NFVO根据NSD的关联信息判断本地是否有可用的NS Instance，返回可用的NS Instance Id。
需要说明的是，步骤505和506无特定的先后执行顺序。也可以先执行步骤505，当在本地找不到可用的NS isntance时，执行步骤506。
507-510的具体实现可参考上一实施例中的步骤407-410，此处不在赘述。
通过重用现有网络服务实例，提供虚拟资源的利用率。
图6示出了本申请提供的一种网络切片模板的实现方案，本实施例在和上述实施例的主要不同在于本实施例的交互主体变为在NSMF和NFVO之间进行交互。
下面结合图6，具体来描述，和上一实施例相同或类似的步骤，本实施例不在赘述。
601-602的具体实现可参考上述实施例中的步骤401-402。
603的具体实现步骤可参考上述实施例中的步骤401，区别点在于交互主体变为NSMF和NFVO。
604-605的具体实现可参考上述实施例中的步骤404-405，区别点在于交互主体变化NSMF和NFVO。
606：NSMF向NSSMF发送NSSI创建请求或者NSSI MO创建请求，所述请求中携带网络服务实例信息，网络服务实例信息包括以下信息中的一个或者多个：NS instance Id,NS flavor Id或nsInstantiationlevel.
607-610的具体实现可参考上述实施例中的步骤407-410，此处不在赘述。
通过NSMF来实现对NS实例信息的集中管理，最大程度保证网络服务实例的利用率。
图7示出了本申请提供的一种网络切片模板的实现方案，具体实现如下：
网络切片子网提供者提供子网模板NSST，其中NSST中包含NSD的信息，以下NSST包含NSD信息的例子。
子网设计者或者运营商加载/上传NSST到NSSMF或者NSSMF可以访问的数据库或者NSSMF和NFVO可以同时访问的数据库：
701-703的具体实现可参考上述实施例中的步骤401-403。
704:NSSMF根据NSST的标识获取相应的NSST，根据NSST子网需求信息得到NSD.
具体地，如图1所述，NSST中包含了不同的子网需求信息值对应的NSD的信息，这里只需要匹配相应的子网需求信息对应的NSD就可以；
其中，NSD的信息包括以下信息中的至少一种：VNFD(Virtualzied Network Function Descriptor，虚拟网络功能描述符)，VLD(Virtualized Link Descriptor，虚拟链接描述符)，PNFD(Physical Network Function Descriptor，物理网络功能描述符)，VNFFGD(Virtualized Network Forward Graph Descriptor,虚拟网络功能转发表描述符)，flavor Id,nsInstantiationLevel,VNF需求信息(VNF Profile)，PNF需求信息(PNF profile)，VL链接信息(VL Profile).
可选地，NSST中还包含以下中的至少一种：VNFD和应用参数的关联关系，PNFD和应用参数的关联关系，VLD和应用参数的关联关系，VNFFGD和应用参数的关联关系，VNFprofile和应用参数的关联关系，PNF profile和应用参数的关联关系，VL Profile和应用参数的 关联关系。
具体地，这里的说的A和B的关联关系，指的是A和B中同一个数据架构中，或者A的数据架构中包含B的信息(e.g.标识)或者B的数据架构中包含A的信息(e.g.标识)
以上应用参数也可以指应用参数的配置脚本或者文件。
可选地，NSST中还包含性能参数(e.g，SLA或KPI)和Flavor ID的关联关系，和/或性能参数(e.g，SLA或KPI)和nsInstantiationlevel的关联关系.
具体地，这里的说的A和B的关联关系，指的是A和B中同一个数据架构中，或者A的数据架构中包含B的信息(e.g.标识)或者B的数据架构中包含A的信息(e.g.标识)
705：NSSMF向NFVO发送NSD的创请求，所述请求中携带NSD.具体地，可以先向NFVO发送NSD加载请求，再向NFVO发送Create NS Identifier请求，请求中携带NSD ID，获取NS instance ID，再向NFVO发送NS实例化请求，所述请求中携带flavor Id或者nsInstantiationlevel等。
706-710的具体实现可参考上述实施例中的步骤406-410，此处不在赘述。
通过在NSST中包含NSD信息，在子网的部署过程中自动部署NS实例，实现网络切片的自动部署。
图8示出了本申请提供的一种网络切片模板的实现方案，包括如下步骤：
S801:第一管理单元接收子网管理请求，该子网管理请求携带子网模板的指示信息；此处需要说明的是，第一管理单元是NSSMF，第二管理单元是DM或者网络功能管理单元(e.g.EM)；或，
第一管理单元是NFVO时，第二管理单元是NSSMF。
S802:第一管理单元根据子网模板的指示信息获取应用信息；
一种可选的实现方式为：第一管理单元根据所述子网模板的指示信息获取子网模板，所述子网模板包含所述应用信息，该第一管理单元由此获取该应用信息。
可选地这里的应用信息可以是配置文件或者脚本。
可选地，这里的子网模板也可以称为网络服务描述符。
可选地，所述子网模板包含所述至少一个应用信息和网络服务需求信息(flavor Id和/或nsInstantiationLevel)的关联关系.
可选地，所述子网模板包含至少一个应用信息和网络功能信息的关联关系，这里的网络功能信息可以是VNFD,VNF Profile，PNFD，PNF profile.
具体地，这里的说的A和B的关联关系，指的是A和B中同一个数据架构中，或者A的数据架构中包含B的信息(e.g.标识)或者B的数据架构中包含A的信息(例如，标识)
S803:第一管理单元向第二管理单元发送子网配置请求，该子网配置请求中携带所述应用信息。
可选地，子网配置请求中还可以携带网络服务实例信息(NS instance ID)。
可选的，所述子网模板还包括至少一个网络功能需求信息和应用信息的关联信息。
需要说明：当讲子网时所提到的应用信息，针对的是给整个子网的应用信息；当将网 络功能是所提到的应用信息，针对的是给定网络功能的应用信息。
图8-1为本实施例的一种流程示意图，该实施例以第一管理单元是NFVO，第二管理单元是NSSMF为例，其中，
8001-8003的具体实现可参考上述实施例中的步骤401-403。
8004：NFVO根据NSST标识获取NS的需求信息；
具体地、NFVO根据NSST的标识获取NSST，NSST中包含NS的需求信息。NSST预先存储在NFVO或者NFVO可以访问的数据库中。
可选地，NS的需求信息为以下信息中的一个或者多个：NS的部署规格(NS Flavor Id),NS的实例化等级(NS Instantiationlevel)。
可选地，NS的需求信息中还包括网络功能需求信息，网络功能需求信息为以下信息中的至少一个：网络功能描述符(包括虚拟网络功能描述和物理网络功能描述符)，虚拟网络功能需求信息(VNF Profile),物理网络功能虚拟信息(PNF Profile)，网络功能部署规格(VNF Flavor ID).
8005：NFVO根据NS的需求信息实例化或者创建NS实例，获取NS实例信息。具体地，NS实例信息包括以下信息中的至少一个：NS实例标识，VNF实例标识，PNF实例标识。
8006：NFVO根据NSST的标识获取应用信息。具体地，NFVO根据NSST的标识获取NSST，NSST预先存储在NFVO或者NFVO可以访问的数据中。
8007：NFVO向NSSMF或者EM发送配置请求,这，请求中携带NS实例信息和信息，其中应用信息可以是以下信息中的至少一种：应用参数、应用参数配置脚本或者应用参数文件.可选地，所述配置请求可以是以下中的至少一种：NSSI的配置请求，NF的配置请求，NSSI MO的创建请求，NF MO的创建请求，NSSI MO的配置请求，NF MO的配置请求。
8008：NSSMF或者EM根据配置请求配置相应的应用信息。
具体地，当配置请求是NSSI的配置请求时，NSSMF给相应的NSSI配置相应的应用信息；
可选地，当配置请求时NF的配置请求时，NSSMF给相应的NF配置相应的应用信息；
可选地，当配置请求时NSSI MO的配置请求时，NSSMF给相应的NSSI MO配置相应的应用信息；
可选地，当配置请求时NF MO的配置请求时，NSSMF给相应的NF MO配置相应的应用信息；
可选地，当配置请求时NSSI MO的创建请求时，NSSMF创建相应的NSSI MO并配置相应的应用信息；
可选地，当配置请求时NF MO的创建请求时，NSSMF创建相应的NF MO并配置相应的应用信息；
在采用集成的模块的情况下，图9A示出了上述实施例中所涉及的第一管理单元的一种可能的结构示意图。第一管理单元900包括：处理模块902和通信模块903。处理模块902用于对第一管理单元的动作进行控制管理，例如，处理模块902用于支持第一管理单 元执行图3至图8中的各步骤执行或用于本文所描述的技术的其它执行步骤过程。通信模块903用于支持第一管理单元与其他网络实体的通信间的通信，例如和第二管理单元的通信。第一管理单元还可以包括存储模块901，用于存储第一管理单元的程序代码和数据。
其中，处理模块902可以是处理器或控制器，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块903可以是通信接口、收发器、收发电路等，其中，通信接口是统称，可以包括一个或多个接口。存储模块901可以是存储器。
当处理模块902为处理器，通信模块903为通信接口，存储模块901为存储器时，本发明实施例所涉及的第一管理单元可以为图9B所示的第一管理单元。
参阅图9B所示，该第一管理单元910包括：处理器912、通信接口913、存储器911。可选的，第一管理单元910还可以包括总线914。其中，通信接口913、处理器912以及存储器911可以通过总线914相互连接；总线914可以是外设部件互连标准(Peripheral Component Interconnect，简称PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，简称EISA)总线等。所述总线914可以分为地址总线、数据总线、控制总线等。为便于表示，图9B中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
上述图9A或图9B所示的第一管理单元可以是网络切片子网管理功能NSSMF，网络切片管理功能，或其他具有NSSMF或者NSMF功能的管理单元。
在采用集成的模块的情况下，图10A示出了上述实施例中所涉及的第二管理单元的一种可能的结构示意图。第二管理单元1000包括：处理模块1002和通信模块1003。处理模块1002用于对第二管理单元的动作进行控制管理，例如，处理模块1002用于支持第二管理单元执行图8至9中的和/或用于本文所描述的技术的其它过程。通信模块1003用于支持第二管理单元与第一管理单元或其他网络实体的通信。第二管理单元还可以包括存储模块1001，用于存储第二管理单元的程序代码和数据。
其中，处理模块1002可以是处理器或控制器，例如可以是CPU，通用处理器，DSP，ASIC，FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块1003可以是通信接口、收发器、收发电路等，其中，通信接口是统称，可以包括一个或多个接口。存储模块1001可以是存储器。
当处理模块1002为处理器，通信模块1003为通信接口，存储模块1001为存储器时，本发明实施例所涉及的第二管理单元可以为图10B所示的第二管理单元。
参阅图10B所示，该第二管理单元1010包括：处理器1012、通信接口1013、存储器 1011。可选的，第二管理单元1010还可以包括总线1014。其中，通信接口1013、处理器1012以及存储器1011可以通过总线1014相互连接；总线1014可以是PCI总线或EISA总线等。所述总线1014可以分为地址总线、数据总线、控制总线等。为便于表示，图10B中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
上述图10A或图10B所示的第二管理单元可以是NSSMF，DM或者网络功能管理单元(e.g.EM)；。
结合本发明实施例公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read Only Memory，ROM)、可擦除可编程只读存储器(Erasable Programmable ROM，EPROM)、电可擦可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于第一管理单元、第二管理单元。当然，处理器和存储介质也可以作为分立组件存在于第一管理单元、第二管理单元。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明实施例所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本发明实施例的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明实施例的具体实施方式而已，并不用于限定本发明实施例的保护范围，凡在本发明实施例的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明实施例的保护范围之内。

Claims (24)

  1. 一种网络切片模板的管理方法，其特征在于，包括：
    第一管理单元接收子网管理请求，所述子网管理请求携带子网模板的指示信息；
    所述第一管理单元根据所述子网模板的指示信息获取网络服务描述符关联信息或者网络服务描述符；
    所述第一管理单元根据所述网络服务描述符关联信息或者网络服务描述符获取网络服务实例。
  2. 根据权利要求1所述的方法，其特征在于，所述第一管理单元根据所述子网模板的指示信息获取网络服务描述符关联信息或者网络服务描述符，包括：
    所述第一管理单元根据所述子网模板指示信息获取所述子网模板，所述子网模板中包含网络服务描述的关联信息或者网络服务描述符。
  3. 根据权利要求1或2所述的方法，其特征在于，所述子网管理请求中还携带子网需求信息；所述第一管理单元根据所述子网模板指示信息获取网络服务描述符的关联信息或者网络服务描述符，包括：
    所述第一管理单元根据所述子网需求信息和所述子网模板指示信息获取网络服务描述符的关联信息或者网络服务描述符。
  4. 根据权利要求1至3任一项所述的方法，其特征在于，所述网络服务描述符关联信息包括以下信息中的一种或多种：
    网络服务描述符的标识，部署规格，实例化等级，厂商信息，版本信息。
  5. 根据权利1至4任一项所述的方法，其特征在于，
    第一管理单元接收子网管理请求后，根据子网模板创建子网实例或子网实例的管理对象；或，
    根据子网模板向第三管理单元发送创建请求，所述创建请求用于创建子网实例或者子网实例的管理对象。
  6. 根据权利1至5任一项所述的方法，其特征在于，
    所述第一管理单元关联子网实例和网络服务实例，或关联子网实例和子网实例的管理对象。
  7. 根据权利1至6任一项所述的方法，其特征在于，
    所述第一管理单元在管理对象中配置网络服务实例信息，所述网络服务实例信息包括网络服务实例标识、网络服务实例规格和网络服务实例实例化等级中的至少一个。
  8. 一种网络切片模板的管理方法，其特征在于，包括：
    第一管理单元接收子网管理请求，所述子网管理请求携带子网模板的指示信息；
    所述第一管理单元根据所述子网模板的指示信息获取应用信息；
    所述第一管理单元向第二管理单元发送子网配置请求，所述子网配置请求中携带所述应用信息。
  9. 根据权利要求8所述的方法，其特征在于，所述第一管理单元根据所述子网模板的 指示信息获取应用信息包括：
    所述第一管理单元根据所述子网模板的指示信息获取子网模板，所述子网模板包含所述应用信息。
  10. 根据权利要求8或9所述的方法，其特征在于，
    所述子网配置请求中还携带网络服务实例信息。
  11. 根据权利要求9或10所述的方法，其特征在于，
    所述子网模板包含所述子网模板的性能信息和网络服务需求信息的关联关系，所述关联关系用于确定所述网络服务需求信息。
  12. 根据权利要求9至11任一项所述的方法，其特征在于，
    所述子网模板包括网络功能需求信息和应用信息的关联信息。
  13. 一种管理单元，其特征在于，包括：处理模块和通信模块，
    所述通信模块用于接收子网管理请求，所述子网管理请求携带子网模板的指示信息；
    所述处理模块根据所述子网模板的指示信息获取网络服务描述符关联信息或者网络服务描述符；
    所述处理模块根据所述网络服务描述符关联信息或者网络服务描述符获取网络服务实例。
  14. 根据权利要求13所述的管理单元，其特征在于，所述所述处理模块根据所述子网模板指示信息获取所述子网模板，所述子网模板中包含网络服务描述的关联信息或者网络服务描述符。
  15. 根据权利要求13或14所述的管理单元，其特征在于，所述子网管理请求中还携带子网需求信息；所述处理模块根据所述子网需求信息和所述子网模板指示信息获取网络服务描述符的关联信息或者网络服务描述符。
  16. 根据权利要求13至15任一项所述的管理单元，其特征在于，所述网络服务描述符关联信息包括以下信息中的一种或多种：
    网络服务描述符的标识，部署规格，实例化等级，厂商信息，版本信息。
  17. 根据权利13至16任一项所述的管理单元，其特征在于，
    所述通信模块接收子网管理请求后，所述处理模块根据子网模板创建子网实例或子网实例的管理对象；或，
    根据子网模板向第三管理单元发送创建请求，所述创建请求用于创建子网实例或者子网实例的管理对象。
  18. 根据权利13至17任一项所述的管理单元，其特征在于，
    所述处理模块关联子网实例和网络服务实例，或关联子网实例和子网实例的管理对象。
  19. 根据权利13至18任一项所述的管理单元，其特征在于，
    所述处理模块在管理对象中配置网络服务实例信息，所述网络服务实例信息包括网络服务实例标识、网络服务实例规格和网络服务实例实例化等级中的至少一个。
  20. 一种管理单元，其特征在于，包括处理模块和通信模块，
    所述通信模块接收子网管理请求，所述子网管理请求携带子网模板的指示信息；
    所述处理模块根据所述子网模板的指示信息获取应用信息；
    所述通信模块向第二管理单元发送子网配置请求，所述子网配置请求中携带所述应用信息。
  21. 根据权利要求20所述的管理单元，其特征在于，所述处理单元根据所述子网模板的指示信息获取子网模板，所述子网模板包含所述应用信息。
  22. 根据权利要求20或21所述的管理单元，其特征在于，
    所述子网配置请求中还携带网络服务实例信息。
  23. 根据权利要求21或22所述的管理单元，其特征在于，
    所述子网模板包含所述子网模板的性能信息和网络服务需求信息的关联关系，所述关联关系用于确定所述网络服务需求信息。
  24. 根据权利要求21至23任一项所述的管理单元，其特征在于，
    所述子网模板包括网络功能需求信息和应用信息的关联信息。
PCT/CN2017/077202 2017-03-19 2017-03-19 一种网络切片的管理方法、单元和系统 WO2018170647A1 (zh)

Priority Applications (9)

Application Number Priority Date Filing Date Title
CN202011284132.3A CN112910677A (zh) 2017-03-19 2017-03-19 一种网络切片模板的管理方法、单元和系统
JP2019572269A JP6834033B2 (ja) 2017-03-19 2017-03-19 ネットワークスライス管理方法、ユニット、及びシステム
AU2017404864A AU2017404864B2 (en) 2017-03-19 2017-03-19 Network slice management method, unit and system
PCT/CN2017/077202 WO2018170647A1 (zh) 2017-03-19 2017-03-19 一种网络切片的管理方法、单元和系统
CN201780088363.7A CN110447208B (zh) 2017-03-19 2017-03-19 一种网络切片的管理方法、单元和系统
KR1020197029834A KR102259679B1 (ko) 2017-03-19 2017-03-19 네트워크 슬라이스 관리 방법, 유닛 및 시스템
EP17901984.9A EP3595244B1 (en) 2017-03-19 2017-03-19 Network slice management method, unit and system
BR112019019222A BR112019019222A2 (pt) 2017-03-19 2017-03-19 método de gerenciamento de fatia de rede, unidade, e sistema
US16/574,565 US11296957B2 (en) 2017-03-19 2019-09-18 Network slice management method, unit, and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/077202 WO2018170647A1 (zh) 2017-03-19 2017-03-19 一种网络切片的管理方法、单元和系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/574,565 Continuation US11296957B2 (en) 2017-03-19 2019-09-18 Network slice management method, unit, and system

Publications (1)

Publication Number Publication Date
WO2018170647A1 true WO2018170647A1 (zh) 2018-09-27

Family

ID=63583974

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/077202 WO2018170647A1 (zh) 2017-03-19 2017-03-19 一种网络切片的管理方法、单元和系统

Country Status (8)

Country Link
US (1) US11296957B2 (zh)
EP (1) EP3595244B1 (zh)
JP (1) JP6834033B2 (zh)
KR (1) KR102259679B1 (zh)
CN (2) CN110447208B (zh)
AU (1) AU2017404864B2 (zh)
BR (1) BR112019019222A2 (zh)
WO (1) WO2018170647A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111130825A (zh) * 2018-10-31 2020-05-08 中兴通讯股份有限公司 网络切片模板生成方法、装置、设备及存储介质
WO2020233217A1 (zh) * 2019-05-17 2020-11-26 中兴通讯股份有限公司 传送网子切片的创建方法、装置、系统及存储介质
US11902109B2 (en) * 2020-04-24 2024-02-13 Samsung Electronics Co., Ltd. Method of network slice resource allocation and visualization
US11974221B2 (en) 2019-05-17 2024-04-30 Xi'an Zhongxing New Software Co., Ltd. Method and device for creating transmission network sub-slice, and system and storage medium

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018094667A1 (zh) * 2016-11-24 2018-05-31 华为技术有限公司 一种管理方法、管理单元及系统
EP3585114B1 (en) * 2017-03-24 2022-05-25 Huawei Technologies Co., Ltd. Method, device and system for configuring network slice
CN109560952B (zh) * 2017-09-27 2021-04-09 华为技术有限公司 一种网络切片管理方法及设备
KR20210101373A (ko) * 2020-02-07 2021-08-19 삼성전자주식회사 무선 통신 시스템에서 네트워크 슬라이스를 생성하기 위한 장치 및 방법
JP6945089B1 (ja) * 2020-03-31 2021-10-06 ノキア ソリューションズ アンド ネットワークス オサケ ユキチュアＮｏｋｉａ Ｓｏｌｕｔｉｏｎｓ ａｎｄ Ｎｅｔｗｏｒｋｓ Ｏｙ ネットワークスライス構成
KR20210127566A (ko) * 2020-04-14 2021-10-22 삼성전자주식회사 네트워크 슬라이스를 제공하는 방법 및 장치
CN113973047B (zh) * 2020-07-24 2024-04-09 中移(苏州)软件技术有限公司 一种信息显示方法、装置、设备及存储介质
CN114827980A (zh) * 2021-01-21 2022-07-29 中国移动通信有限公司研究院 Nssi更新方法、装置及nssmf实体
CN115037788A (zh) * 2021-03-04 2022-09-09 华为技术有限公司 一种创建网络服务ns的方法及相关装置
US11588704B2 (en) * 2021-03-08 2023-02-21 International Business Machines Corporation Broadband cellular network deployment fractal generation
WO2022226970A1 (en) * 2021-04-30 2022-11-03 Nokia Shanghai Bell Co., Ltd. Providing services in communication system
CN113612635B (zh) * 2021-07-29 2022-08-12 西安电子科技大学 基于水平和垂直伸缩结合的网络切片实例资源分配方法
CN113472595B (zh) * 2021-08-10 2023-04-18 中国联合网络通信集团有限公司 核心网子网切片创建方法、功能实体和切片管理系统
CN114125779B (zh) * 2021-11-26 2023-05-16 中国联合网络通信集团有限公司 一种应用程序实例化方法、装置、服务器及存储介质
WO2023191459A1 (en) * 2022-03-30 2023-10-05 Samsung Electronics Co., Ltd. Methods and systems for providing enhanced network slice allocation
CN114978948B (zh) * 2022-05-20 2024-02-09 中国电信股份有限公司 网元承载网络切片业务的评估方法、装置、设备及存储
CN117081945B (zh) * 2023-10-12 2024-01-09 南京中科境远科技有限公司 核心网切片子网实例部署方法及装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105282195A (zh) * 2014-06-27 2016-01-27 中兴通讯股份有限公司 网络服务提供、策略规则评估、服务组件选择方法及装置
CN106161174A (zh) * 2015-04-22 2016-11-23 中兴通讯股份有限公司 一种网关虚拟化方法及系统

Family Cites Families (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014128948A1 (ja) * 2013-02-25 2014-08-28 株式会社日立製作所 仮想サーバおよび非仮想サーバ混在環境におけるテナントネットワーク構成の管理方法
CN103269282A (zh) * 2013-04-25 2013-08-28 杭州华三通信技术有限公司 网络配置自动部署方法和装置
WO2015021629A1 (zh) * 2013-08-15 2015-02-19 华为技术有限公司 一种资源发放方法
US9363141B1 (en) * 2013-09-30 2016-06-07 Emc Corporation System and method for partitioning a network
CN104639361B (zh) * 2013-11-15 2019-04-19 中兴通讯股份有限公司 网络服务模板的管理方法和装置
US20150358399A1 (en) * 2014-06-09 2015-12-10 Cisco Technology, Inc. Provisioning and managing slices of a consumer premises equipment device
BR112017015617A2 (pt) * 2015-01-20 2018-04-10 Huawei Tech Co Ltd sistemas e métodos para sdt trabalhar interligada com nfv e sdn.
EP3249860A4 (en) * 2015-01-23 2018-01-24 Nec Corporation Method, device, and program for management and orchestration of network functions virtualization
CN104639653B (zh) * 2015-03-05 2019-04-09 北京掌中经纬技术有限公司 基于云架构的自适应方法及系统
CN106341832B (zh) * 2015-07-07 2020-11-06 中国移动通信集团公司 网络切片的管理及选择方法、系统、基站、路由交换设备
US10644955B2 (en) * 2015-08-21 2020-05-05 Huawei Technologies Co., Ltd. Method and apparatus for network slicing
EP3337094B1 (en) 2015-08-31 2019-11-06 Huawei Technologies Co., Ltd. Method and apparatus for deploying network services
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
US9961713B2 (en) * 2016-02-23 2018-05-01 Motorola Mobility Llc Procedures to support network slicing in a wireless communication system
US10819630B1 (en) * 2016-04-20 2020-10-27 Equinix, Inc. Layer three instances for a cloud-based services exchange
KR102633995B1 (ko) * 2016-08-22 2024-02-06 삼성전자 주식회사 무선 통신 시스템에서, 단말과 써드 파티 서버 간의 인증 요청 방법 및, 이를 위한 단말 및 네트워크 슬라이스 인스턴스 관리 장치
WO2018084975A1 (en) * 2016-11-02 2018-05-11 Intel IP Corporation Lifecycle management parameter modeling for virtual network functions
US10924943B2 (en) * 2017-01-05 2021-02-16 Apple Inc. Instantiation and management of physical and virtualized network functions of a radio access network node
US10761896B2 (en) * 2017-02-22 2020-09-01 Cisco Technology, Inc. System and method of lightweight decentralized NFV orchestration
CN110463139A (zh) * 2017-03-16 2019-11-15 英特尔Ip公司 在网络切片实例上支持son功能
US10841184B2 (en) * 2017-03-28 2020-11-17 Huawei Technologies Co., Ltd. Architecture for integrating service, network and domain management subsystems
US20180317134A1 (en) * 2017-04-28 2018-11-01 Huawei Technologies Co., Ltd. Nssmf nsmf interaction connecting virtual 5g networks and subnets

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105282195A (zh) * 2014-06-27 2016-01-27 中兴通讯股份有限公司 网络服务提供、策略规则评估、服务组件选择方法及装置
CN106161174A (zh) * 2015-04-22 2016-11-23 中兴通讯股份有限公司 一种网关虚拟化方法及系统

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication Management; Life Cycle Management (LCM) for Mobile Networks that Include Virtualized Network Functions; Procedures (Release 14", 3GPP TS 28.526, 9 March 2017 (2017-03-09), pages 1 - 36, XP055540867 *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Study on Management and Orchestration of Network Slicing for Next Generation Network (Release 14", 3GPP TR 28.801, 9 March 2017 (2017-03-09), pages 1 - 36, XP055540877 *
See also references of EP3595244A4 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111130825A (zh) * 2018-10-31 2020-05-08 中兴通讯股份有限公司 网络切片模板生成方法、装置、设备及存储介质
CN111130825B (zh) * 2018-10-31 2022-09-23 中兴通讯股份有限公司 网络切片模板生成方法、装置、设备及存储介质
WO2020233217A1 (zh) * 2019-05-17 2020-11-26 中兴通讯股份有限公司 传送网子切片的创建方法、装置、系统及存储介质
EP3972324A4 (en) * 2019-05-17 2022-07-27 ZTE Corporation METHOD AND DEVICE FOR TRANSMISSION NETWORK SUB-SLICE GENERATION, AS WELL AS SYSTEM AND STORAGE MEDIUM
US11974221B2 (en) 2019-05-17 2024-04-30 Xi'an Zhongxing New Software Co., Ltd. Method and device for creating transmission network sub-slice, and system and storage medium
US11902109B2 (en) * 2020-04-24 2024-02-13 Samsung Electronics Co., Ltd. Method of network slice resource allocation and visualization

Also Published As

Publication number Publication date
BR112019019222A2 (pt) 2020-04-14
EP3595244B1 (en) 2022-02-23
JP6834033B2 (ja) 2021-02-24
AU2017404864A1 (en) 2019-10-17
AU2017404864B2 (en) 2021-03-25
KR20190120833A (ko) 2019-10-24
EP3595244A4 (en) 2020-01-15
KR102259679B1 (ko) 2021-06-01
US20200014608A1 (en) 2020-01-09
CN112910677A (zh) 2021-06-04
CN110447208A (zh) 2019-11-12
CN110447208B (zh) 2020-12-08
US11296957B2 (en) 2022-04-05
EP3595244A1 (en) 2020-01-15
JP2020510384A (ja) 2020-04-02

Similar Documents

Publication Publication Date Title
WO2018170647A1 (zh) 一种网络切片的管理方法、单元和系统
US11063831B2 (en) Network slice management method and apparatus
WO2018058579A1 (zh) 网络切片的管理方法及管理单元
US11750453B2 (en) Network slice configuration method, apparatus, and system
US10924966B2 (en) Management method, management unit, and system
WO2018006381A1 (zh) 一种网络资源的管理方法、装置及系统
KR20200088470A (ko) 네트워크 슬라이스 배치 방법 및 장치
CN109391498B (zh) 网络组件的管理方法和网络设备
CN107222324B (zh) 网络服务的业务配置方法和装置
US11070989B2 (en) Network slice management method, management unit, and system
WO2019062456A1 (zh) 网络的部署信息确定方法及设备
WO2018082477A1 (zh) 用于管理网络切片实例的方法和装置
WO2018152825A1 (zh) 一种管理方法、管理单元和系统
US20210289435A1 (en) Virtualization management method and apparatus
WO2018082487A1 (zh) 管理网络切片的方法、设备和系统
WO2021129868A1 (zh) 网络服务实例化的方法及网络功能虚拟化编排器
WO2022183796A1 (zh) 一种创建网络服务ns的方法及相关装置
WO2018120227A1 (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: 17901984

Country of ref document: EP

Kind code of ref document: A1

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
ENP Entry into the national phase

Ref document number: 2019572269

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112019019222

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 20197029834

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2017404864

Country of ref document: AU

Date of ref document: 20170319

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2017901984

Country of ref document: EP

Effective date: 20191009

ENP Entry into the national phase

Ref document number: 112019019222

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20190916