WO2018213991A1 - 网络切片创建的方法、装置以及通信系统 - Google Patents

网络切片创建的方法、装置以及通信系统 Download PDF

Info

Publication number
WO2018213991A1
WO2018213991A1 PCT/CN2017/085368 CN2017085368W WO2018213991A1 WO 2018213991 A1 WO2018213991 A1 WO 2018213991A1 CN 2017085368 W CN2017085368 W CN 2017085368W WO 2018213991 A1 WO2018213991 A1 WO 2018213991A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
service
entity
network function
network slice
Prior art date
Application number
PCT/CN2017/085368
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 PCT/CN2017/085368 priority Critical patent/WO2018213991A1/zh
Priority to JP2019564046A priority patent/JP6823203B2/ja
Priority to EP17911014.3A priority patent/EP3609161B1/en
Priority to CN201780089288.6A priority patent/CN110476402B/zh
Publication of WO2018213991A1 publication Critical patent/WO2018213991A1/zh
Priority to US16/680,991 priority patent/US11146453B2/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/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • 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/0894—Policy-based network configuration management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • 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
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1073—Registration or de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances

Definitions

  • the present application relates to the field of communications and, more particularly, to a method, apparatus, and communication system for network slice creation.
  • Future communication systems can support a variety of different service types, such as enhanced mobile broadband (eMBB), ultra-reliable ultra-low latency connection (uRLLC), and massive machine type connectivity ( Massive machine type connection, mMTC), and so on.
  • eMBB enhanced mobile broadband
  • uRLLC ultra-reliable ultra-low latency connection
  • mMTC massive machine type connectivity
  • Different business types have different characteristics and network requirements.
  • applications such as eMBB's virtual reality (VR) and augmented reality (AR) technologies have extremely high bandwidth requirements, and uRLLC's automatic driving applications are timely.
  • the sensitivity is extended, while the connection density of mMTC is extremely high. Therefore, in order to improve network communication efficiency and meet different communication service requirements, the network may be divided into multiple network slice instances, and respective network slice instances are respectively provided with corresponding network services.
  • VNF instances can be deployed in a physical network slicing instance, and each VNF instance can provide one type of network service.
  • Each network slice instance has its corresponding service configuration script, and the service configuration script corresponding to the network slice is related to the infrastructure it is in, and is also related to the configuration of the surrounding network to be connected and the network planning of the operator.
  • a network slice management function (NSMF) entity prepares a template of a network slice in advance, and generates a script file for creating a network slice instance according to a network slice order issued by the user.
  • This script file contains resource deployment scripts and business configuration scripts.
  • the resource deployment script describes the infrastructure resources allocated by the network function, the software image of the loaded network function, and the connection between the network functions.
  • the service configuration script contains the service deployment commands of the network function entity.
  • NSMF sends resource deployment scripts to the network functions virtualization management and orchestration (NFV-MANO) functional entity, and NFV-MANO allocates resources on the NFV Infrastructure based on resource deployment scripts. And deploy the corresponding VNF entity in the network slice and connect the VNF.
  • NFV-MANO network functions virtualization management and orchestration
  • the NSMF then sends the service configuration script to the element management system (EMS) entity.
  • EMS element management system
  • the EMS executes the relevant service deployment commands on the VNF and the physical network function (PNF) of the network slice according to the script, so that the client makes the client The business required by the order can be run normally on the slice. This way the network slice is created.
  • the service configuration script needs to be adjusted according to the deployment plan and coupled with the resource deployment script.
  • the deployment of slices is often closely related to the planning of the site, which further leads to the coupling of the service configuration script and the specific planning of each site.
  • the invention provides a method, device and system for creating a network slice, so that the system can automatically combine the planning of the network slice of each office and the registration information of the network function entity according to the model and strategy of the pre-designed network slice. Generate a corresponding network slicing service configuration scheme to automate the network slicing creation process and achieve multiple deployments in one design.
  • the present application provides a method and apparatus for creating a network slice and a communication system, which can realize the requirement of multiple deployments in one design.
  • the first aspect provides a network control method, including: a network slice control function (NSCF) entity receives a service deployment command sent by a network slice management function entity, and the NSCF entity obtains a service related according to a service deployment command.
  • a network slice control function (NSCF) entity receives a service deployment command sent by a network slice management function entity, and the NSCF entity obtains a service related according to a service deployment command.
  • Demand parameters, network slice models, policies and plans, and registration information for network functional entities service-related demand parameters, network slice models, policies, and plans from NSMF entities, registration information from network functional entities, NSCF entities Generating a service configuration scheme of the network function entity according to the model and policy of the network slice, and one or more of the service-related requirement parameter, the registration information of the network function entity, and the network slice plan; and sending the service configuration plan to The network function entity, so that the network function entity can directly configure the service according to the service configuration scheme, thereby eliminating the need to manually configure the network function entity
  • the network function entity may be a virtual network function VNF entity, a physical network function PNF entity or a network function service instance running on the VNF service framework.
  • the registration information may be different.
  • the registration information includes the network location, connection topology, and resource information of the network function entity.
  • the registration information can be the network location and connection topology of the network functional entity.
  • the resource information may include the resources of the virtual machine occupied by the VNF entity and the bandwidth of the allocated network interface, or the resources of the virtual machine occupied by the VNF service framework and the bandwidth of the allocated network interface. Due to the registration information reported by the network function entity, the NSCF entity can obtain information about the current network function entity, so that the service configuration can be automated.
  • the model of the network slice includes one or more of a network model, a resource model, and a service model, where the network model is used to indicate a network function entity required for each service in the network slice instance, and a network function entity a logical connection relationship between the service size and the resource quantity and a corresponding relationship between the service size and the network bandwidth; the service model is used to indicate the service configuration of the network function entity, and the network function The related cooperation relationship between the entities in the service configuration; the network slice policy includes one or more of a network policy, a resource policy, and a service policy, where the network policy includes various network function entities in the network slice instance.
  • the principle of performing service configuration on the network function entity; the planning of the network slice includes one or more of the following: a connection plan of the network slice instance and the surrounding network, and an internet protocol (IP) address of the network slice instance. Planning.
  • IP internet protocol
  • the NSCF entity generates a service configuration of the network function entity according to the model and policy of the network slice, and one or more of the service-related requirement parameter, the registration information of the network function entity, and the network slice plan.
  • the solution specifically includes: determining, by the NSCF entity, between the network function entities after the deployment, according to the network model, and the service related requirement parameter, the registration information of the network function entity, and the network slice plan.
  • Network configuration relationship in order to satisfy the network policy; according to the service model and the network configuration relationship, and one or more of the service-related demand parameters, network function entity registration information, and network slice planning Determining a service configuration relationship between the network function entities after the deployment is completed, so as to satisfy the service policy; according to the resource model, and the service-related demand parameters and the registration of the network function entity
  • the resource configuration relationship between the network function entities after the deployment is determined, so as to satisfy the resource policy; and obtain specific service deployments of the network function entities respectively.
  • Configuration The NSCF entity performs configuration processing corresponding to the network function entity model for different models and information, thereby enabling the deployment of the configuration relationship and satisfying the corresponding strategy, and further realizing the automatic deployment of the service configuration.
  • the method further includes: the NSCF entity generating a basic network configuration scheme for the virtualization or cloud infrastructure carried by the VNF entity, where the basic network configuration scheme includes the switching network configuration of the infrastructure, and the routing configuration And configuration of the virtual interface; sending the basic network configuration scheme to the orchestration entity.
  • the orchestration entity can perform an automated basic network configuration of the network functional entity according to the basic network configuration scheme.
  • the method further includes: receiving, by the NSCF entity, a service deployment command, acquiring the service-related requirement parameter, the network slice model, policy, and plan; and according to the service-related requirement parameter, the network slice Model, policy, and planning, and registration information of the VNF service framework, generating a network function service configuration scheme, wherein the network service configuration scheme includes types of network function services that need to be deployed on each of the VNF service frameworks, and each type of network The number of functional service instances; a network function service deployment message containing the network function service configuration scheme is sent to the VNF service framework.
  • the VNF service framework can perform automated network function service configuration according to the network function service configuration scheme.
  • the present invention provides another method for network slice creation, including: a service deployment command sent by an NSMF entity to an NSCF; and an NSMF entity receiving a network slice creation completion indication sent by the NSCF entity.
  • the NSCF entity instructs the NSCF entity to perform service configuration, thereby realizing the automation of network slice creation.
  • the method further includes: the NSMF entity sends the service related requirement parameter, the network slice model, the policy, and the plan to the NSCF entity.
  • the method further includes: the NSMF entity sends the service-related requirement parameter, the network slice model, and the deployment template to the orchestration entity.
  • the present invention provides another method for network slice creation, including: the scheduling entity receives a resource deployment command sent by the NSMF entity, and deploys a VNF entity and a network configuring the VNF entity on the infrastructure according to the resource deployment command. Connect; or deploy the VNF service framework and the network connection configuring the VNF service framework on the infrastructure according to the resource deployment command.
  • the orchestration entity can deploy the VNF entity or the VNF service framework according to the resource deployment command, thereby realizing the automation of the VNF deployment in the network slice creation process.
  • a device for network slice creation that is, an NSCF entity, for performing the method in any of the above first aspect or any possible implementation of the first aspect.
  • the network slice control entity comprises means for performing the method of any of the above-described first aspect or any of the possible implementations of the first aspect.
  • a network slice management entity is provided for performing the method of any of the foregoing second aspect or any of the possible implementations of the second aspect.
  • the network slice management entity comprises means for performing the method of any of the above-described second or second aspects of the second aspect.
  • an orchestration entity is provided for performing the method of the third aspect above.
  • the orchestration entity comprises means for performing the method of the third aspect above.
  • an NSCF entity comprising: a memory and a processor, the memory for storing instructions for executing instructions stored by the memory, and when the processor executes The execution of the memory, the execution causes the processor to perform any of the first aspect or the first aspect The method in the implementation.
  • another network slice management entity comprising: a memory and a processor for storing instructions for executing instructions stored by the memory, and when the processor executes the instructions stored by the memory The execution causes the processor to perform the method of the second aspect or any possible implementation of the second aspect.
  • another network slice management entity comprising: a memory for storing instructions for executing instructions stored in the memory, and a processor for executing the instructions stored by the memory The execution causes the processor to perform the method of the third aspect.
  • a communication system comprising an NSMF entity and an NSCF entity.
  • the NSCF entity may be the device in any possible implementation manner of the fourth aspect or the fourth aspect, or the NSCF entity may be the device in any possible implementation manner of the seventh aspect or the seventh aspect.
  • the NSMF entity may be the device in any possible implementation manner of the fifth aspect or the fifth aspect, or the NSMF entity may be the device in any possible implementation manner of the eighth aspect or the eighth aspect.
  • the communication system further includes an orchestration entity, where the orchestration entity may be the device in any possible implementation manner of the sixth aspect or the sixth aspect, or the programming entity may be any of the ninth aspect or the ninth aspect The device in the implementation.
  • orchestration entity may be the device in any possible implementation manner of the sixth aspect or the sixth aspect
  • programming entity may be any of the ninth aspect or the ninth aspect The device in the implementation.
  • a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of the first aspect or any of the possible implementations of the first aspect.
  • a computer readable medium for storing a computer program comprising instructions for performing the method of any of the second aspect or any of the possible implementations of the second aspect.
  • a thirteenth aspect a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of the third aspect.
  • FIG. 1 is a schematic diagram of an architectural example of a communication system to which an embodiment of the present invention is applied.
  • FIG. 2 is a schematic diagram of another architectural example of a communication system to which the embodiment of the present invention is applied.
  • FIG. 3 is a schematic diagram of another architecture example of a communication system according to an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of a method for creating a network slice according to an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of another method for creating a network slice according to an embodiment of the present invention.
  • FIG. 6 is a schematic block diagram of a network slice control entity according to an embodiment of the present invention.
  • FIG. 7 is a schematic block diagram of an orchestration entity provided by an embodiment of the present invention.
  • FIG. 8 is a schematic block diagram of another network slice control entity according to an embodiment of the present invention.
  • FIG. 9 is a schematic block diagram of another arrangement entity provided by an embodiment of the present invention.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • PRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • PLMN Public Land Mobile Network
  • FIG. 1 shows a communication system 100 to which an embodiment of the present invention is applied.
  • the communication system 100 can include an NSMF entity 110, a virtualization or clouding orchestration entity 120, an NSCF entity 130, and a network slice instance 160.
  • the network slice instance 160 may have one or more (not illustrated in the figure), and each network slice instance 160 may include creating a deployed VNF entity 140 on the virtualization or cloud infrastructure 170, in a network.
  • Slice instance 160 may include one or more VNF entities 140 (as in Figure 1).
  • network tile instance 160 may also include one or more VNF service frameworks (as in FIG. 2 or FIG. 3).
  • network slice instance 160 may also include one or more PNF entities 150 (as in FIG. 1 or FIG. 3).
  • network slice instance 160 may also not include PNF entity 150 (FIG. 2).
  • the NSMF entity 110 may also be referred to as a network slice management device.
  • the virtualization or clouding orchestration entity 120 may also be referred to as an orchestration device, or a virtualization or clouding orchestration device.
  • the NSCF entity 130 may also be referred to as a network slice creation device or a network control device.
  • the plurality of VNF entities 140 in the same network slice instance 160 may be independent of each other (as in FIG. 1), and one or more VNF entities 140 in the same network slice instance 160 may jointly own a VNF service framework 180 (as shown in the figure). 2)
  • a network slice instance 160 may contain one or more VNF service frameworks 180.
  • the virtual network function adopts a serviced architecture, and the network function is integrated in the VNF service framework in the form of a VNF service, that is, each VNF entity 140 includes one or more network function service instances 190, and
  • the VNF service framework 180 that provides support is run, as shown in Figures 2 and 3.
  • the VNF Service Framework 180 provides generalized computational invocation, storage access, network access, and hardware acceleration capabilities for a serviced VNF.
  • the network configuration of the deployed network function instance is performed on the VNF service framework 180, and the service configuration of the deployed network function instance is passed to the network function service instance 190 through the VNF service framework 180.
  • the VNF service framework 180 is uniformly controlled by the NSCF entity 130.
  • the VNF service framework 180 deployed on a virtualized or clouded infrastructure 170 at a location may also run multiple network functional service instances 190 simultaneously, such as UPF and APP at mobile edge computing (MEC) locations. Share a VNF service framework.
  • the VNF entity 140, the PNF entity 150, or the network function service instance 180 running on the VNF service framework 180 may also be referred to as a network function entity.
  • the network function entity may carry some network and service functions, and the specific network function entity may be a user plane function entity and/or a control plane function entity, but the embodiment of the present invention is not limited thereto.
  • the network and service functions carried by the network function entity may be specifically an access management function (AMF), a session management function (SMF), a policy control function (PCF), and a user plane.
  • AMF access management function
  • SMF session management function
  • PCF policy control function
  • UPF User plane function
  • APP application server
  • the NSMF entity 110 can be used for the lifecycle management of the network sharding instance 160.
  • the NSMF entity 110 manages the process of creating, activating, running, deactivating, or deleting the network sharding instance 160.
  • the management operation of the NSMF entity 110 during the creation of the network slice instance 160 For example, the NSMF entity 110 receives the network slice order of the client, and drives the orchestration entity 120 and the NSCF entity 130 to create a network slice instance 160 according to the stored network slice template, and completes resource deployment and service configuration of the network slice instance 160.
  • the network slice template is a template for the NSMF entity 110 to create a network slice instance 160 pre-designed for a certain type of service.
  • the network slice template includes a workflow, a deployment template, a network slice model and a policy.
  • Programming The body 120 can be an NFV-MANO entity or a management and orchestration entity of the PasS cloud platform itself.
  • the orchestration entity 120 can be responsible for the allocation of the infrastructure 170 resources required by the network slice instance 160 based on the workflow in the network slice template, and complete the deployment of the VNF entity 140 on the virtualization or cloud infrastructure 170, and complete with other A network connection between the VNF entity 140 or the PNF entity 150.
  • the NSCF entity 130 automatically generates a service configuration scheme of the network slice according to the model of the network slice in the network slice template, the policy and the planning in the network slice order, and the service-related requirement parameters, and the registration information of each network function entity.
  • the corresponding network function entity (including the VNF entity 140 and/or the PNF entity 150) in the network slice instance 160 is executed to complete the service configuration of the network slice.
  • the PNF entity 150 may be a physical device dedicated to the communication network that the operator pre-built and deployed.
  • the virtualization or cloud infrastructure 170 can be a pre-configured common physical device of an operator or cloud service provider that provides computing, memory, storage, network resources, and the orchestration entity 120 controls the virtualization or cloud infrastructure 170 to use the above resources.
  • the deployment of the VNF instance, virtualization or cloud infrastructure implementation 170 may also be referred to simply as the base implementation 170.
  • the above network slice model is also a model required for automatically generating a service configuration, which may be simply referred to as a model, and the model includes one or more of the following types: a resource model, a network model, and a business model.
  • the network model is used to indicate the network function entities required for each service in the network sharding instance, and the logical connection relationship between the network function entities.
  • an IoT service needs to deploy network functional entities such as UPF, SMF, and eNodeB;
  • the UF is connected to the wireless eNodeB through the service network, and the UPF is connected to the SMF through the signaling network.
  • the resource model is used to indicate the correspondence between the service size and the amount of resources and the correspondence between the service size and the network bandwidth.
  • the amount of network bandwidth used For example, when each UPF instance supports 500,000 sessions, it requires 4 core CPUs, 16G memory and 200G hard disks.
  • the UPF service network interface requires 10Gbps bandwidth.
  • the service model is used to indicate the service configuration of the network function entity and the related cooperation relationship between the network function entities in the service configuration.
  • AMF service configuration should be able to support the service that belongs to the network slice instance shown, please send the signaling to the SMF, and the SMF can find a suitable one.
  • UPF to establish a user plane session connection for the user.
  • the UPF entity needs to configure the signaling connection address of the SMF entity responsible for managing the session establishment.
  • the UPF entity When the UPF entity functions normally, the UPF entity initiates a signaling connection to the SMF entity.
  • the above-mentioned network slicing policy is also a policy required for automatically generating a service configuration, and may be simply referred to as a policy.
  • the policy includes one or more of the following types: a network policy, a resource policy, and a service policy.
  • a policy includes a trigger event or timing (hereinafter referred to as an event) for performing an operation scheme, a condition for performing an action (hereinafter referred to as a condition), and a specific content of the action, wherein the condition may be derived from a relationship included in the model, or may be Customized for the strategy.
  • the network policy includes the location requirement principle of the network function entity in the network slice instance, and the performance requirement principle of the network bandwidth and the delay between the network function entities.
  • the UPF ie LBO UPF
  • APP responsible for the local exit need to be set at the same site to avoid user-side transmission and return, while meeting the stricter delay requirements.
  • the network policy may be specifically: when the workflow is executed to the LBO (local egress function) of the configuration UPF, it is determined that all the UPFs that have been deployed satisfy the conditions of the same site as the APP, and the action performed on the UPF that satisfies the condition is to open the UPF.
  • the LBO function configuration switch when the workflow is executed to the LBO (local egress function) of the configuration UPF, it is determined that all the UPFs that have been deployed satisfy the conditions of the same site as the APP, and the action performed on the UPF that satisfies the condition is to open the UPF.
  • the LBO function configuration switch when the workflow is executed to
  • the resource policy includes the resource occupancy principle of the network functional entity and the bandwidth usage principle of the link of the physical network entity. For example, ensure that the total link bandwidth of all network functional entities on the MEC does not exceed the data center's egress network bandwidth.
  • the resource policy is specifically: when the workflow is configured to configure the network egress bandwidth limit for the UPF entity deployed in the MEC, it is determined whether the sum of the allocated UPF network egress bandwidths in the current MEC exceeds 100G, if If the value exceeds 100G, the action performed is to select the UPF of other MECs. If the device does not exceed 100G, the action performed is that the UPF allows the network egress to be configured, and the maximum allowable bandwidth is limited to 100G minus the sum of the configured bandwidths. value.
  • the service policy includes the principle of determining how to configure the service of the network functional entity according to the planning of the network slice and the registration information of the network function entity.
  • the MEC's UPF enables LBO (local breakout) and stream identification functions; the LBO cascades the APP and sends it to the anchor UPF; the flow identification rule and the tandem APP rule are configured in the PCF, and so on.
  • the service policy is specifically: when the workflow is executed to enable the LBO function to be configured on the UPF, it is determined whether the LBO service of the UPF needs to be deployed in the APP of the MEC.
  • the action includes: The UPF configures the flow identification function; (2) the corresponding rule of the flow identification is configured in the PCF; (3) the service flow rule configured by the PCF also specifies that the user session data packet is sent by the UPF to the anchor UPF functional entity after being processed by the APP.
  • All the policies may be described in the following form: when a certain step of the workflow is executed, it is determined whether the specific content or the specific value of the current basic attribute satisfies one or more conditions, and whether the corresponding operation plan is executed according to whether the condition is satisfied.
  • the operation scheme is one or more actions automatically generated according to the model and combined with the specific information of the currently created network slice when the specific content or the specific value of the above basic attribute satisfies the condition of the policy. This operation will meet the principles described in the above strategy.
  • Policies are stored in an easy-to-manage and easy-to-adjust way, such as using XML to describe events, conditions or sets of conditions, and the operational scenarios that are performed. Models can be described and stored in a manner consistent with TOSCA standards.
  • the deployment template is determined by the network slicing design.
  • the deployment template includes a description of the functional requirements of the service that the network slicing instance created by the deployment template can support, and a description of the non-functional requirements such as performance and reliability.
  • the functional requirements description includes optional service functions.
  • the performance includes delay, service capacity, and bandwidth of a single connection. Reliability can be the recovery time of the fault.
  • the workflow specifically includes abstraction and general description of the following workflows: obtaining and parsing orders, obtaining business-related demand parameters and network slice plans included in the order, and transmitting business-related demand parameters, network slice planning and deployment templates to
  • the entity 120 is arranged to perform NFV deployment, and to transmit to the NSCF entity 130 the service-related demand parameters of the network slice, the model of the network slice, the policy, and the plan to perform the service configuration.
  • the planning of the network slice may include a docking plan of the perimeter network of the network slice instance or a plan of the IP address of the network slice instance.
  • Service related demand parameters may include performance and reliability requirements for network slicing instances. For example, taking the auto-driving service provided by the network slicing example as an example, the demand parameters related to the service include the connection of the network slice capacity to support how many vehicles are connected, the delay is less than 10 milliseconds, and the bandwidth of a single connection is 100 megabytes;
  • the docking plan of the perimeter network of the slice instance is the connection of the perimeter network to the connection to the vehicle networking control server.
  • the planning of the network slice specifically includes the network slice instance supporting the topological connection of the 100,000 user scale and the radio access network, the IP address planning of the control plane, the IP address planning of the user plane, and the IP address planning of the APP.
  • the communication system 100 described above may also include a database (not shown) that stores models, policies, and plans for the network slice, which may also store registration information for the VNF, PNF, or VNF service framework.
  • the database may be inherited in the NSCF 130, or in other network elements in the communication system 100, such as NSMF 110, and the database may also exist as a separate network element.
  • the database can be either a centralized database or a distributed database. The number of databases is not limited and can be one or more. If the communication system 100 includes multiple databases, different information can be stored in different databases, for example, the resource information and the network location are stored in the resource database, The connection topology is stored in the topology database.
  • the solution relates to a system for creating a network slice, which can automatically perform resource deployment on a virtualized or clouded infrastructure 170 according to a pre-designed network slice template, combined with a network slice plan in a network slice order, and a virtual network function and The physical network function performs network connection; then automatically generates a service configuration scheme of the network slice (which may include a service-related network configuration according to service requirements), performs execution on the virtual network function and the physical network function, and implements the network slice creation process automation.
  • a network slice instance can be automatically created.
  • the network splicing instance is an end-to-end logically isolated network sharding instance generated by the foregoing system according to the network sharding template, which is generated in the physical network of the network virtualization or clouding infrastructure 170, and performs service configuration. Provide customers with network services in the order.
  • FIG. 4 shows a method for creating a network slice according to an embodiment of the present invention.
  • the method can be applied to the above communication system, and the method comprises the following steps:
  • the NSMF entity 110 receives a network slice order of the customer from the commercial support system.
  • the network slice order includes an index of the network slice template, a network slice plan, and a service-related demand parameter.
  • the planning of the network slice and the service-related requirement parameters have been described in the related embodiments in FIG. 1-3, and details are not described herein again.
  • the operator may have designed a series of slice templates in advance and may generate customizable products for each slice template.
  • the operator can also release the customized product through the commercial support system.
  • the customer orders the customized product through the commercial support system, the customer obtains the network slicing order.
  • the NSMF entity 110 also stores the correspondence between the index of the network slice template and the network slice template.
  • the NSMF entity 110 can obtain the index of the network slice template from the network slice order, and combines the index of the stored network slice template and the network slice.
  • the corresponding relationship of the template is obtained by obtaining a network slice template.
  • the index of the network slice template here is an identifier, which can be composed of a series of numbers or letters.
  • the NSMF entity 110 can obtain models, policies, workflows, and deployment templates from the network slice template.
  • the NSMF entity 110 parses the detailed content of the network slice order according to the workflow, and obtains the service-related demand parameters and the network slice plan included in the network slice order.
  • the models, strategies, and workflows described above have been described in the previous sections and will not be repeated here.
  • the NSMF entity 110 sends the service-related requirement parameters of the network slice, the model, policy, and plan of the network slice to the NSCF entity 130.
  • the NSCF entity 130 receives and stores the service related requirement parameters, models, policies, and plans of the network slice sent by the NSMF entity 110.
  • the NSCF entity 130 may store the service-related demand parameters, models, policies, and plans of the network slice in the NSCF entity 130 itself, or store the service-related demand parameters, models, policies, and plans of the network slice in the database.
  • the NSMF entity 110 sends the service related requirement parameters, the network slice planning and the deployment template to the orchestration entity 120.
  • the scheduling entity 120 receives the service-related requirement parameters, the network slice planning and deployment template, fills in the service-related requirement parameters and the network slice plan into the deployment template, generates the NFV-NSD file, and according to the NFV-NSD The file deploys the VNF entity 140 on the virtualization or cloud infrastructure 170.
  • the NFV-NSD file also contains a description file of the VNF entity to be deployed, in the description file of the VNF entity. Contains the number of VNF entities that carry each type of network functional entity, and the number and requirements for allocating CPU, memory, disk, and network interfaces to VNF entities.
  • the orchestration entity 120 deploys a corresponding number of VNF entities on the virtualization or cloud infrastructure based on the description file of the VNF entity.
  • the NFV-NSD file also includes a description of which network plane each type of network interface of each VNF entity is connected to, and the orchestration entity 120 connects the network interfaces of the deployed VNF entities to the respective network planes according to the description to implement the VNF entity.
  • the network connection between the VNF entity and the PNF entity For the PNF, the physical deployment is done manually and connected to the planned network plane. It has been fixedly described in the deployment template.
  • the automatically generated NFV-NSD file directly uses the fixed description in the deployment template.
  • the orchestration entity 120 configures a network connection for the VNF entity 140 that has been successfully created according to the NFV-NSD file.
  • the orchestration entity 120 also implements a network connection between the VNF entity 140 and other VNF entities, as well as a network connection between the VNF entity 140 and the PNF entity. It should be noted that other VNF entities and PNF entities herein may belong to the network slice instance together with the VNF entity 140, and may belong to different network slice instances of the VNF entity 140.
  • the orchestration entity 120 can also assign an IP address to the VNF entity 140 and send the IP address of the NSCF entity 130 corresponding to the VNF entity 140 to the VNF entity 140.
  • the orchestration entity 120 also configures the network connection between the VNF entity 140 and the PNF entity 150 according to the NFV-NSD file.
  • the orchestration entity 120 also implements a network connection between the PNF entity 150 and other PNF entities, as well as a network connection between the PNF entity 150 and the VNF entity. It should be noted that other VNF entities and PNF entities herein may belong to the same network slice instance together with the PNF entity 150, and may belong to different network slice instances of the PNF entity 150.
  • the orchestration entity 120 can also assign an IP address to the PNF entity 150 and send the IP address of the NSCF entity 130 corresponding to the PNF entity 150 to the PNF entity 150.
  • the VNF entity 140 sends a registration request including registration information to the NSCF entity 130 according to the received IP address of the NSCF entity 130.
  • the registration information includes resource information, a network location, and a connection topology of the VNF entity 140.
  • the NSCF entity 130 receives the registration request and stores the registration information in the database.
  • the resource information may be the resources (including CPU, memory, and disk) of the virtual machine occupied by the VNF entity 140 and the bandwidth of the allocated network interface.
  • the network location is the location information of the data center where the VNF entity 140 is located.
  • the connection topology may be an IP address of the VNF entity 140, and a connection relationship between the VNF entity 140 and other VNF entities, PNF entities.
  • the PNF entity 150 may further send a registration request including the registration information to the NSCF entity 130 according to the received IP address of the NSCF entity 130, where the registration information includes the PNF entity. 150 network location and connection topology.
  • the NSCF entity 130 receives the registration request and stores the registration information in the database.
  • the network location is the location information of the data center where the PNF entity 150 is located.
  • the connection topology may be an IP address of the PNF entity 150 and a connection relationship between the PNF entity 150 and other VNF entities and PNF entities.
  • the orchestration entity 120 notifies the NSMF entity 110 to complete resource deployment according to the content of the NFV-NSD file. This step is performed after completion of S407, and can be processed in parallel with S408 or S409.
  • the NSMF entity 110 After receiving the notification that the resource deployment is complete, the NSMF entity 110 sends the service department to the NSCF entity 130. Order of the Department.
  • the NSCF entity 130 after receiving the service deployment command, the NSCF entity 130 generates a service configuration scheme of the network slice according to the service-related requirement parameters, the model, the policy, and the plan, and the registration information of the network function entity (including the VNF140 and/or the PNF150).
  • the specific method is as follows:
  • the NSCF entity 130 determines the service configuration relationship between the network function entities according to the registration information of the model, the policy, the plan, and the network function entity, and then inputs the plan input of the network slice and the service according to the policy, the service-related demand parameter, and the plan.
  • the requirements are configured in the service configuration relationship between the network function entities to meet the rules specified by the network segmentation policy, and the specific service configuration scheme of each network function entity is generated.
  • the policy includes the network policy, the resource policy, and the business policy. These models and policies are common for each network slice instance creation, so that the NSCF entity 130 Common models and strategies are available.
  • the NSCF entity 130 further determines the performance and reliability requirements of the network slice instance included in the service-related requirement parameters, and the network slice created this time according to the planning of the interconnection plan and IP address of the surrounding network that the network slice instance is created.
  • the registration information of the network function entity deployed by the instance can generate a specific service configuration scheme for each network function entity included in the created network slice instance.
  • the content contained in the model is a relatively stable abstract description.
  • the content contained in the strategy is an operation principle that is easy to modify and adjust. If necessary, it is allowed to modify the default policy in the network slice before creating the slice.
  • the NSCF entity 130 obtains relevant information required by the conditions and actions included in the policy from the planning of the network slice, the service-related requirement parameter and the registration information, and then determines whether the related information satisfies the conditions included in the network policy, according to the judgment result and the foregoing. Relevant information, determine the actions performed, and ultimately generate a specific operational plan.
  • the operation scheme makes the configuration of the network slice, the service-related requirement parameter, and the registration information of the network function entity obtain the configuration parameter corresponding to the corresponding model description, and also enables the final generation of the specific operation plan to meet the corresponding Strategy.
  • the NSCF entity 130 determines the network between the deployed network functional entities according to the network model, and the service-related requirement parameters, the registration information of the network function entity, and the network slice plan. Configuring a relationship to satisfy the network policy; according to the service model and the network configuration relationship, and one or more of the service related requirement parameter, the registration information of the network function entity, and the network slice plan, Determining a service configuration relationship between the network function entities after the deployment is completed, so as to satisfy the service policy; according to the resource model, and the service-related demand parameters, network function entity registration information, and network slice One or more of the planned, the resource configuration relationship between the network function entities after the deployment is determined, so as to satisfy the resource policy; respectively, obtaining specific service deployment configuration plans of the network function entities.
  • the NSCF entity 130 sends a service configuration message including the service configuration scheme to the VNF entity 140, and the VNF entity 140 completes the corresponding service configuration according to the service configuration scheme.
  • the NSCF entity 130 may send one or more service configuration messages, and the service configuration messages sent to different VNF entities 140 may be the same or different, if the service configuration If the message is the same, the service configuration message may include a service configuration scheme of the multiple VNF entities 140 of the network slice instance, or the service configuration message may further include multiple VNF entities 140 and 1 of the network slice instance. Or multiple PNF150 service configuration schemes. If the service configuration message is different, the service configuration message may only include the service configuration scheme of the VNF entity 140.
  • the NSCF entity 130 sends a service configuration message including a service configuration scheme to the PNF entity 150, the PNF.
  • the entity 150 completes the corresponding service configuration according to the service configuration scheme, and the process is similar to that of S413.
  • S413 and S414 have no sequential order.
  • the NSCF entity 130 may also generate an relevant basic network configuration scheme in S411, and the basic network configuration scheme. Sent to the orchestration entity 120.
  • the basic network configuration scheme includes a switched network configuration, a routing configuration, and a virtual interface of the virtualization or cloud infrastructure 170.
  • Steps S415 and S413, S414 have no sequential requirements, and may also be performed simultaneously.
  • the orchestration entity 120 receives the configuration information sent by the NSCF entity 130. After receiving the command of S415, the orchestration entity 120 performs service-related network configuration on the infrastructure 170 of the VNF entity 140. For example, configuring the virtual network interface of the VNF to the IP routing between the service processing interfaces of the VNF.
  • the NSCF entity 130 After completing all the service configurations, the NSCF entity 130 sends a notification that the network slice creation is completed to the NSMF entity 110.
  • the network slice control function entity can automatically generate a corresponding network slice service configuration plan according to the pre-designed network slice model and strategy, and combine the network slice plan and resource deployment information in the order, thereby enabling flexible implementation at different sites.
  • Autocomplete slice creation Before creating a network slice instance, the prior art needs to manually modify and adjust the service configuration plan according to the order requirements before creating a network slice.
  • the network slice control function entity of the solution can automatically generate a service configuration plan for the network segment instance to be deployed, and automatically create a network slice, and no need to manually modify the service configuration plan.
  • the orchestration entity 120 deploys the VNF service framework 180 on the virtualization or cloud infrastructure 170 in accordance with the NFV-NSD file.
  • the orchestration entity 120 notifies the creation of a successful VNF service framework 180 to configure the network connection according to the NFV-NSD file.
  • the orchestration entity 120 can implement a network connection between the VNF service framework 180 and other VNF service frameworks, as well as a network connection between the VNF service framework 180 and the PNF entity. It should be noted that other VNF service frameworks and PNF entities herein may belong to the network slice instance together with the VNF service framework 180, and may belong to different network slice instances of the VNF service framework 180.
  • the orchestration entity 120 can also assign an IP address to the VNF service framework 180 and send the IP address of the NSCF entity 130 to which the VNF service framework 180 needs to connect to the VNF service framework 180.
  • the VNF service framework 180 sends a registration request including registration information to the NSCF entity 130 according to the IP address of the NSCF entity, where the registration information includes resource information, network location, and connection topology of the VNF service framework 180.
  • the NSCF entity 130 receives the registration request and stores the registration information in the database.
  • the resource information may be the resources (including CPU, memory, and disk) of the virtual machine occupied by the VNF service framework 180 and the bandwidth of the allocated network interface.
  • the network location is the location information of the data center where the VNF service framework 180 is located.
  • the connection topology may be the IP address of the VNF service framework 180, and the connection relationship between the VNF service framework 180 and other VNF service frameworks, PNF entities.
  • the orchestration entity 120 notifies the NSMF entity 110 to complete resource deployment. This step is completed after S505 is completed. Line, can be processed in parallel with S506.
  • the NSCF entity After receiving the service deployment command, the NSCF entity obtains, from the network model, which network function services need to be deployed in the network slice, and the connection relationship between them; and then, according to the service-related requirement parameters and the resource model, the NSCF It can be calculated that each network function service needs to configure several service instances and how much network connection bandwidth is needed between them; then, the NSCF entity further combines the available resources and network continuous topology data from the registration information of the VNF service framework. Calculate the network function configuration scheme that conforms to the resource policy, that is, determine which VNF service frameworks are deployed on which VNF service frameworks. The available resources of the VNF service framework and the network connection between them can support such deployment.
  • the NSCF entity 130 generates a network function service configuration scheme according to the service-related demand parameters, the network slice model, the policy, and the plan, and the registration information of the VNF service framework 180, and the network service configuration scheme is included in each VNF service framework 180.
  • the network service configuration scheme may also include the address of the software image of each type of network function service.
  • the orchestration entity 120 can send the address of the software image of each type of network function service to the VNF service framework when deploying the VNF service framework.
  • the network service configuration scheme may not include the address of the software image of each type of network function service.
  • the NSCF entity 130 determines which network function service instances 190 are deployed in which VNF service frameworks 180. For example, the NSCF entity 130 calculates the required number of network function services and deployed instances according to the service-related demand parameters, resource models, and plans, and then according to the network slice resource policy, according to the available resources and VNF of each VNF service framework 180.
  • the connection topology between the service frameworks 180 determines the network function service instances 190 that each VNF service framework 180 needs to deploy.
  • the types of network function services can include service types such as mobility management and session management. For example: AMF, SMF, PCF, UPF, APP.
  • the NSCF entity 130 includes a network function service deployment message of the network function service configuration scheme to the VNF service framework 180.
  • the VNF service framework 180 receives the network function service deployment message, and the VNF service framework 180 installs the software image of the network function service to be deployed according to the address of the network function software image, loads the network function service to be deployed, and enables the network function service.
  • the instance runs on the VNF service framework 180.
  • each VNF service framework 180 deploys corresponding network function services according to the above process according to the network function service deployment message.
  • the network function registration request may be initiated to the NSCF entity 130 according to the IP address of the NSCF entity 130 provided by the VNF service framework 180.
  • the network function service instance 190 may also be monitored by the VNF service framework 160 until the network function service instance runs and then initiates a network function registration to the NSCF entity 130.
  • S514 The NSCF entity 130 sends a service configuration message including a service configuration scheme to the running network function service instance 190, and the running network function service instance 190 completes the corresponding service configuration according to the service configuration scheme.
  • the process by which the NSCF entity 130 determines the service configuration scheme is as follows:
  • the NSCF entity 130 obtains the network from the planning of the network slice, the service related requirement parameters and the registration information.
  • the conditions and actions required in the policy are related information, and then it is judged whether the related information satisfies the conditions included in the network policy, and the executed action is determined according to the judgment result and the related information, and finally a specific operation plan is generated.
  • the operation scheme configures the network connection and the connection bandwidth between the network function services, so that the network slice planning, the service-related requirement parameters, and the registration information obtain the corresponding parameters in the network model according to the network configuration relationship described by the corresponding network model. At the same time, it also enables the final generation of specific operational solutions to meet the corresponding network strategy.
  • the NSCF entity 130 obtains relevant information required by the conditions and actions included in the service policy from the planning of the network slice, the service-related requirement parameters, and the registration information, and then determines whether the related information meets the conditions included in the service policy, according to the judgment result and The above related information determines the action performed and finally generates a specific operation plan.
  • the operation scheme is to complete the service configuration relationship between each network function entity after the deployment of each network function service instance on the VNF service framework, so that the network slice planning, service-related requirement parameters, and registration information are obtained in the service model.
  • the parameters conform to the service configuration relationship described by the corresponding service model, and also enable the final generation of a specific operation plan to meet the corresponding network policy network configuration relationship network configuration relationship.
  • the service chain between the UPC and the APP of the MEC requires the NSCF entity 130 to complete the corresponding network configuration on the virtual switch implemented by the virtualization or cloud infrastructure 170 through the orchestration entity 120.
  • the PNF entity 150 can also be installed and configured in a network slice instance, the process being the same as the processes of S409 and S412.
  • the network slice control function entity not only automatically controls the service configuration of the network slice, but also controls the deployment and connection topology of the virtual network function according to the policy, so that the virtual network function can be flexibly adjusted according to the information of the network slice plan.
  • the deployment location and connection topology, the automatically generated network segmentation service configuration is better and the resource deployment is coordinated, which can better adapt to the service distribution difference of the network slice in different locations.
  • An enterprise subscribes to a network segment of a mobile office at an operator, and requires the operator to configure a data network name (DNN) named "ABC" to connect to the enterprise mobile office server.
  • the address of the enterprise mobile office server is AA. :BB::CC.
  • the enterprise will specify the following service-related demand parameters in the order for ordering the network slice: 1.
  • Slice service range city A, 2, service capacity requirement: 300Mbps connection bandwidth, 3, DNN name: “ABC”, 4, docking Address: AA: BB::CC, 5, optional function: Enable anti-attack filtering.
  • the operator has the ability to provide such network slicing.
  • the operator can implement network slicing for this type of network slicing.
  • the planning content is as follows:
  • the available service address pool of city A is: AA: BB::1 ⁇ 100, DC-
  • the internal network address of the outgoing router Router-A is CC: DD::111, and the external network address is AA: BB::101.
  • the available service address pool of the city B is: AA: BB:: 501 to 600, DC-B.
  • the internal network address of the router Router-B is EE: FF::111, and the external network address is AA: BB::601.
  • the NSMF entity When the NSMF entity receives the network slice order, the NSMF entity can obtain the network slice plan, the service-related demand parameter, and the index of the network slice template from the network slice order. The NSMF entity can obtain a network slice template according to the index of the network slice template. And obtaining the deployment template and the workflow, and sending the service-related requirement parameters, the deployment template, and the network plan to the orchestration entity according to the workflow, and sending the relevant requirement parameters, the network slice model, the policy, and the plan to the In the NSCF entity.
  • the resource model here describes that the maximum traffic supported by each service address is 500 Mbps.
  • the network model includes the following contents: (1) Each service processing virtual machine of the virtual mobile gateway needs to configure each service address; (2) the address of the docked enterprise mobile office server is in the "dock address" field in the service requirement parameter. Inside and configured from Each service address is routed through the interface address to the connection address; (3) The router in the data center configures a route through each interface address to each service address.
  • the business model describes the following information: (1) configuring the DNN specified by the order in the virtual mobile gateway; (2) associating the route of the service address to the docking address to the DNN specified by the order on the virtual mobile gateway; (3) opening the DNN for the order Optional features specified by the order.
  • the resource policy here includes the following: the timing of the resource policy execution (also referred to as the trigger event of the resource policy execution): when the service address is configured; the condition of the resource policy execution: determining the connection bandwidth of the virtual mobile gateway to the enterprise mobile office server Whether the "service capacity requirement" field in the order is greater than the maximum service traffic supported by each service address in the model; the operation plan of the resource policy execution: if the "service capacity requirement" field is not greater than the support of each service address in the model For the maximum service traffic, two unassigned service addresses are taken from the IP address included in the plan. Otherwise, the service addresses are allocated (the maximum service traffic of the single service IP in the service capacity requirement/resource model + 2).
  • the network policy includes the following: the timing of the execution of the network policy (also referred to as the triggering event of the network policy execution): after the completion of the service address configuration; the conditions for the execution of the network policy: whether the network slice planning exists and the data of the same network segment as the service address Central router; operation scheme of network policy execution: if the network slice plan exists and the data center router with the service address on the same network segment, the interface IP address is obtained from each virtual machine after the NFV deployment, according to the network model (2) Describe the outbound route for configuring service traffic for each service address assigned; and obtain the router of the data center where the NFV deployment is located from the network slice plan, and configure the service for each service address allocated according to the description in (3) of the network model. The incoming route of traffic. If it does not exist, try to reassign the business address.
  • the business policy includes the following: the timing of the execution of the business policy: the service configuration when the network function is executed; the condition 1 of the business policy execution: whether the network slice order contains the DNN name; the operation plan of the corresponding business policy 1: If the network is in the slice order Containing the DNN name, the name of the DNN determines the above DNN name, and configures the DNN and the docking route association according to the business model (2). If the DNN name is not included in the network slice order, the DNN name is set to "default DNN", And add the associated configuration of the connected route to the default DNN.
  • Condition 2 of the execution of the service policy Whether the anti-attack filtering function needs to be enabled, and the operation policy 2: The anti-attack filtering function is enabled, then the function is enabled in the DNN according to the model (3). If the anti-attack filtering function is not available. Is turned on, no operation.
  • Condition 3 of the business policy execution Whether the traffic forcing restriction function is enabled. If the traffic forcing restriction function is enabled, configure the DNN traffic enforcement limit according to the model. The upper limit is the “service capacity requirement” field in the order. Not turned on, no operation.
  • the orchestration entity generates the NFV-NSD file, and deploys the virtual mobile gateway GW-A in the city A according to the NFV-NSD file, and allocates two load-sharing service processing virtual machines according to the service capacity, and is the GW.
  • -A's two service processing virtual machines allocate the available interface IP addresses CC:DD::1 and CC:DD::2 in the data center DC-A, and the interface and the internal network port CC of the router A :DD::111 connects to the same VLAN to complete the NFV deployment.
  • the NSCF entity obtains the above-mentioned model, policy, planning, service-related demand parameters, and registration information reported by the virtual mobile gateway GW-A.
  • the NSCF entity reads the resource policy, and when the service address is configured, it is determined that the service capacity requirement of the service-related demand parameter is greater than the maximum service traffic supported by each service address included in the resource model, and then two of the planned address pools are selected.
  • the unassigned service addresses are the two service addresses of the virtual mobile gateway.
  • the NSCF entity reads the network policy, and after determining the service address configuration, determines the network segmentation plan and the data center router with the service address on the same network segment, and obtains the interface IP address from each virtual machine after the NFV deployment, according to the network model.
  • the description of (2) configures the outgoing route of the enterprise mobile office server for each service address allocated; obtains the router of the data center where the NFV is deployed from the network slice plan, and allocates according to the description in (3) of the network model.
  • Each service address configures the incoming route of the enterprise mobile office server.
  • the NSCF entity reads the service policy, determines whether the network slice order contains the DNN name when performing the service configuration of the network function, and configures the DNN and the connection route association according to the service model (2). And because the anti-attack filtering function needs to be enabled, the anti-attack filtering function is enabled.
  • FIG. 6 shows a network slice control entity 600 according to an embodiment of the present invention, including:
  • the transceiver unit 610 is configured to receive a service deployment command sent by the NSMF entity.
  • the obtaining unit 620 is configured to obtain, according to the service deployment command, a service related requirement parameter, a network slice model, a policy, and a plan, and a registration information of the network function entity;
  • a generating unit 630 configured to generate a service configuration scheme of the network function entity according to one or more of a model and a policy of the network slice, and the service related requirement parameter, the registration information of the network function entity, and the network slice plan.
  • the transceiver unit 610 is further configured to send the service configuration scheme to the network function entity.
  • the network slice control entity 600 further includes: a storage unit 640, configured to store a service-related demand parameter, a model of a network slice, a policy, and a plan, or store registration information of the network function entity.
  • the transceiver unit 610 is further configured to receive a service-related demand parameter sent by the NSMF entity, a model, a policy, and a plan of the network slice, or a registration request that the receiving network function entity includes the registration information.
  • the generating unit 630 is further configured to generate a basic network configuration scheme for the virtualization or cloud infrastructure carried by the VNF entity, where the basic network configuration scheme includes the virtualization Or the switching network configuration of the cloud infrastructure, the routing configuration, and the configuration of the virtual interface; at this time, the transceiver unit 610 is further configured to send the basic network configuration scheme to the orchestration entity.
  • the generating unit 630 is further configured to generate a network function service configuration scheme according to the model, policy, and plan of the network slice and the registration information of the VNF service framework, where the network service configuration solution is included in each The type of the network function service, the number of each type of the network function service instance, and the address of the software image of the network function service, and the transceiver unit 610 is further configured to provide the VNF service framework. Sending a network function service deployment message containing the network function service configuration scheme.
  • the network slice control entity 600 herein is embodied in the form of functional units.
  • the network slice control entity 600 may be specifically the network slice control entity in the foregoing embodiment, and the network slice control entity may be used to perform the network slice control entity in the foregoing method embodiment. Corresponding processes and/or steps are not repeated here to avoid repetition.
  • FIG. 7 shows an orchestration entity 700 provided by an embodiment of the present invention, including:
  • the transceiver unit 710 is configured to receive a resource deployment command sent by the NSMF entity.
  • a deployment and configuration unit 720 for deploying a VNF entity and configuring a network connection of the VNF entity on the virtualized or clouded infrastructure; or deploying the VNF service framework and configuration on the virtualized or clouded infrastructure described above according to resource deployment commands The network connection of the VNF service framework.
  • the orchestration entity 700 herein is embodied in the form of a functional unit.
  • the orchestration entity 700 may be specifically an orchestration entity in the foregoing embodiment, and the orchestration entity 700 may be configured to perform various processes and/or corresponding to the orchestration entity in the foregoing method embodiments. Steps, to avoid repetition, will not be repeated here.
  • unit may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor for executing one or more software or firmware programs (eg, sharing). Processors, proprietary processors or group processors, etc.) and memory, merge logic, and/or other suitable components that support the described functionality.
  • ASIC application specific integrated circuit
  • FIG. 8 and FIG. 9 are schematic diagrams of a computer device according to an embodiment of the present invention.
  • Computer device 800 includes at least one processor 801, a communication bus 802, a memory 803, and at least one communication interface 804.
  • Processor 801 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present invention.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • Communication bus 802 can include a path for communicating information between the components described above.
  • the communication interface 804 uses devices such as any transceiver for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), and the like.
  • RAN Radio Access Network
  • WLAN Wireless Local Area Networks
  • the memory 803 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device can also be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • the memory can exist independently and be connected to the processor via a bus.
  • the memory can also be integrated with the processor.
  • the memory 803 is used to store application code for executing the solution of the present invention, and is controlled by the processor 801 for execution.
  • the processor 801 is configured to execute application code stored in the memory 803.
  • the processor 801 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • computer device 800 can include multiple processors, such as processor 801 and processor 808 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • computer device 800 may also include an output device 805 and an input device 806.
  • Output device 805 is in communication with processor 801 and can display information in a variety of ways.
  • the output device 805 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait.
  • Input device 806 is in communication with processor 801 and can accept user input in a variety of ways.
  • input device 806 can be a mouse, keyboard, touch screen device, or sensing device, and the like.
  • the computer device 800 described above can be a general purpose computer device or a special purpose computer device.
  • the computer device 800 can be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, a communication device, an embedded device, or the like in FIG. Structured equipment.
  • PDA personal digital assistant
  • Embodiments of the invention do not limit the type of computer device 800.
  • the network slice control entity in Figures 1-6 may be the device shown in Figure 8, in which one or more software modules are stored in the memory of the network slice control entity.
  • the network slice control entity can implement the network slice creation by implementing the software module through the processor and the program code in the memory.
  • the orchestration entities in Figures 1-5 and 7 may be the devices shown in Figure 9, in which one or more software modules are stored in the memory of the orchestration entity.
  • the orchestration entity can implement the network slice creation by implementing the software module through the processor and the program code in the memory.
  • the processor may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital uplink signal processors (DSPs), and application specific integrated circuits ( ASIC), off-the-shelf programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and more.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory can include read only memory and random access memory and provides instructions and data to the processor.
  • a portion of the memory may also include a non-volatile random access memory.
  • the memory can also store information of the device type.
  • the processor can be used to execute instructions stored in the memory, and when the processor executes the instructions, the processor can perform the steps corresponding to the terminal device in the above method embodiments.
  • each step of the above method may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in a memory, and the processor executes instructions in the memory, in combination with hardware to perform the steps of the above method. To avoid repetition, it will not be described in detail here.
  • the embodiment of the present invention further provides a communication system, which may include any of the policy control function entities in the foregoing embodiments and any of the policy execution function entities in the foregoing embodiments.
  • the communication system may further comprise a data storage function entity for storing at least one of the following information: at least one deployed instance of each of the one or more network function entities Information, information of each physical location in at least one physical location of the deployable network functional entity, wherein the information of each deployed instance may include at least one of the following information: deployment location information, occupied resource information, enabled Information of processing capabilities and capacity utilization information, the information of each physical location including location information and/or available resource information for each physical location.
  • a data storage function entity for storing at least one of the following information: at least one deployed instance of each of the one or more network function entities Information, information of each physical location in at least one physical location of the deployable network functional entity, wherein the information of each deployed instance may include at least one of the following information: deployment location information, occupied resource information, enabled Information of processing capabilities and capacity utilization information, the information of each physical location including location information and/or available resource information for each physical location.
  • the communication system may be specifically the communication system shown in FIG. 1, but the embodiment of the present invention is not limited thereto.
  • system and “network” are used interchangeably herein.
  • the term “and/or” in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and / or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations.
  • the character "/" in this article generally indicates that the contextual object is an "or" relationship.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only divided into one logical functional entity.
  • there may be another division manner for example, multiple units or components may be combined. Or it can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional entity unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functional entities if implemented in the form of software functional entity units and sold or used as separate products, may be stored in a computer readable storage medium.
  • the technical solution of the present invention which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

Abstract

本发明实施例提供了一种网络切片创建的方法，装置和系统，包括：网络切片控制功能NSCF实体接收网络切片管理功能NSMF实体发送的业务部署命令；所述NSCF实体根据所述业务部署命令，获取业务相关的需求参数、网络切片的模型、策略和规划，以及网络功能实体的注册信息；所述NSCF实体根据所述网络切片的模型和策略，以及所述业务相关的需求参数、网络功能实体的注册信息和网络切片的规划中的一个或多个，生成网络功能实体的业务配置方案；所述NSCF实体将所述业务配置方案发送到所述网络功能实体。实现了网络切片的自动化创建。

Description

网络切片创建的方法、装置以及通信系统 技术领域
本申请涉及通信领域，并且更具体地，涉及网络切片创建的方法、装置以及通信系统。
背景技术
未来的通信系统可以支持多种不同的业务类型，例如增强移动宽带(enhanced mobile broadband，eMBB)、超高可靠性超低时延连接(ultra reliability and low latency connection，uRLLC)以及海量机器类型连接(massive machine type connection，mMTC)，等等。不同的业务类型具有不同的特点和网络要求，例如，eMBB的虚拟现实(virtual reality，VR)和增强现实(augmented reality，AR)技术等应用对于带宽要求极高，uRLLC的自动驾驶等应用对于时延敏感，而mMTC的连接密度极高。因此，为了提高网络通信效率和满足不同的通信业务需求，可以将网络划分为多个网络切片实例，分别由各个网络切片实例提供相应的网络服务。
一个物理网络切片实例中可以部署多个虚拟网络功能(virtual network function，VNF)实例，每一个VNF实例可以提供一种类型的网络服务。每一个网络切片实例有其对应的业务配置脚本，且网络切片对应的业务配置脚本与其所在的基础设施相关，还与要对接的周边网络的配置，以及运营商的网络规划有关。
现有技术中网络切片管理功能(network slice management function，NSMF)实体提前准备网络切片的模板，根据用户下发的网络切片订单，生成创建网络切片实例的脚本文件。这个脚本文件包含资源部署脚本和业务配置脚本。资源部署脚本描述网络功能分配的基础设施资源，加载的网络功能的软件镜像，以及网络功能之间的连接。业务配置脚本包含网络功能实体的业务部署命令。NSMF将资源部署脚本发送到网络功能虚拟化管理和编排(network functions virtualization management and orchestration，NFV-MANO)功能实体，NFV-MANO根据资源部署脚本在网络功能虚拟化基础设施(NFV Infrastructure)上分配资源并部署网络切片内相应的VNF实体，并将VNF连接起来。然后NSMF将业务配置脚本发送到网元管理系统(element management system,EMS)实体，EMS根据脚本在网络切片的VNF和物理网络功能(physical network function，PNF)上执行相关的业务部署命令，使得客户订单要求的业务能够正常的在切片上运行起来。这样网络切片就创建起来了。
业务配置脚本需要根据部署的规划做相应的配置调整，和资源部署脚本耦合。切片的部署往往和该局点的规划密切相关，进一步造成业务配置脚本和每个局点的具体规划耦合。换一个局点位置部署，就需要重新编写业务配置脚本，非常不灵活，难以实现自动化，无法做到网络切片一次设计多次部署。
发明内容
本发明提供一种创建网络切片的方法、装置和系统，使得系统能够根据预先设计的网络切片的模型和策略，结合每个局点的网络切片的规划和网络功能实体的注册信息自动 生成相应的网络切片业务配置方案，实现网络切片创建过程自动化，做到一次设计多次部署。
本申请提供一种创建网络切片的方法和装置以及通信系统，能够实现一次设计多次部署的要求。
第一方面，提供了一种网络控制的方法，包括：网络切片控制功能(network slice control function，NSCF)实体接收网络切片管理功能实体发送的业务部署命令，NSCF实体根据业务部署命令，获取业务相关的需求参数、网络切片的模型、策略和规划，以及网络功能实体的注册信息；业务相关的需求参数、网络切片的模型、策略和规划来自于NSMF实体，注册信息来自于网络功能实体，NSCF实体根据这些网络切片的模型和策略，以及业务相关的需求参数、网络功能实体的注册信息和网络切片的规划中的一个或多个，生成网络功能实体的业务配置方案；并把业务配置方案发送到网络功能实体，这样网络功能实体就可以根据业务配置方案直接进行业务配置，从而无需对网络功能实体进行手动配置，从而实现了网络切片创建过程的自动化。
可选的，网络功能实体可以为虚拟网络功能VNF实体，物理网络功能PNF实体或运行在VNF服务框架上的网络功能服务实例。对于不同的网络功能实体而言，注册信息可能存在不同，对于VNF实体或者运行在VNF服务框架上的网络功能服务实例时而言，注册信息包括网络功能实体的网络位置、连接拓扑和资源信息。对于PNF实体，注册信息可以为网络功能实体的网络位置和连接拓扑。而资源信息可以包括VNF实体占用的虚拟机的资源和分配网络接口的带宽，或者VNF服务框架占用的虚拟机的资源和分配网络接口的带宽。由于网络功能实体上报的注册信息，NSCF实体就可以获知到当前网络功能实体的相关信息，从而可以自动化地为其进行业务配置。
可选地，网络切片的模型包括网络模型，资源模型和业务模型中的一个或多个，其中，所述网络模型用于指示网络切片实例中各业务所需的网络功能实体，以及网络功能实体之间的逻辑连接关系；所述资源模型用于指示业务规模与资源量的对应关系以及业务规模与网络带宽大小的对应关系；所述业务模型用于指示网络功能实体的业务配置，以及网络功能实体之间在业务配置上的相关配合关系；所述网络切片的策略包括网络策略、资源策略和业务策略中的一个或多个，其中，网络策略包括各种网络功能实体在网络切片实例中的位置要求原则、网络功能实体之间的网络带宽和时延的性能要求原则；资源策略包括网络功能实体的资源占用原则以及物理网络实体的链路的带宽使用原则；业务策略包括根据所述网络切片的规划和网络功能实体的注册信息确定如何对所述网络功能实体进行业务配置的原则；所述网络切片的规划包括以下一种或多种：网络切片实例与周边网络的对接规划和网络切片实例的互联网协议(internet protocol，IP)地址的规划。
可选的，NSCF实体根据所述网络切片的模型和策略，以及所述业务相关的需求参数、网络功能实体的注册信息和网络切片的规划中的一个或多个，生成网络功能实体的业务配置方案具体包括：NSCF实体根据所述网络模型，以及所述业务相关的需求参数、网络功能实体的注册信息和网络切片的规划中的一个或多个，确定部署完毕后的各个网络功能实体之间的网络配置关系，以便于满足所述网络策略；根据所述业务模型和所述网络配置关系，以及所述业务相关的需求参数、网络功能实体的注册信息和网络切片的规划中的一个或多个，确定所述部署完毕后的各个网络功能实体之间的业务配置关系，以便于满足所述业务策略；根据所述资源模型，以及所述业务相关的需求参数、网络功能实体的注册 信息和网络切片的规划中的一个或多个，确定部署完毕后的各个网络功能实体之间的资源配置关系，以便于满足所述资源策略；分别获得所述各个网络功能实体的具体的业务部署配置方案。NSCF实体通过对不同模型和信息，进行网络功能实体模型相对应的配置处理，从而使得部署好的配置关系，满足相应的策略，进一步实现了业务配置的自动化部署。
可选的，方法还包括：NSCF实体为所述VNF实体所承载的虚拟化或云化基础设施生成基础网络配置方案，其中，所述基础网络配置方案包含了基础设施的交换网络配置，路由配置和虚拟接口的配置；将所述基础网络配置方案发送到编排实体。这样编排实体就可以根据基础网络配置方案对网络功能实体进行自动化的基础网络配置。
可选的，方法还包括：NSCF实体收到业务部署命令，获取所述业务相关的需求参数、所述网络切片的模型、策略和规划；根据所述业务相关的需求参数、所述网络切片的模型、策略和规划以及VNF服务框架的注册信息，生成网络功能服务配置方案，其中，所述网络服务配置方案包括在各个所述VNF服务框架上需要部署网络功能服务的类型、每种类型的网络功能服务实例的数量；向VNF服务框架发送包含所述网络功能服务配置方案的网络功能服务部署消息。这样VNF服务框架就可以根据网络功能服务配置方案进行自动化的网络功能服务配置。
第二方面，本发明提供了另一种网络切片创建的方法，包括：NSMF实体向NSCF发送的业务部署命令；NSMF实体接收所述NSCF实体发送的网络切片创建完成指示。由NSMF实体指示NSCF实体进行业务配置，从而实现了网络切片创建的自动化。
可选的，方法还包括：NSMF实体向NSCF实体发送所述业务相关的需求参数、网络切片的模型、策略和规划。
可选的，方法还包括：NSMF实体向编排实体发送业务相关的需求参数、网络切片的模型和部署模板。
第三方面，本发明提供了另一种网络切片创建的方法，包括：编排实体接收所述NSMF实体发送的资源部署命令，根据资源部署命令，在基础设施上部署VNF实体和配置VNF实体的网络连接；或者根据资源部署命令，在基础设施上部署VNF服务框架和配置所述VNF服务框架的网络连接。编排实体可以根据资源部署命令，部署VNF实体或者VNF服务框架的，从而实现了网络切片创建过程中的VNF部署的自动化。
第四方面，提供了一种网络切片创建的装置，即NSCF实体，用于执行上述第一方面或第一方面的任意可能的实现方式中的方法。
具体地，该网络切片控制实体包括用于执行上述第一方面或第一方面的任意可能的实现方式中的方法的单元。
第五方面，提供了一种网络切片管理实体，用于执行上述第二方面或第二方面的任意可能的实现方式中的方法。
具体地，该网络切片管理实体包括用于执行上述第二方面或第二方面的任意可能的实现方式中的方法的单元。
第六方面，提供了一种编排实体，用于执行上述第三方面的方法。
具体地，该编排实体包括用于执行上述第三方面的方法的单元。
第七方面，提供了另一种网络切片创建的装置，即NSCF实体，包括：存储器和处理器，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第一方面或第一方面的任意可能的 实现方式中的方法。
第八方面，提供了另一种网络切片管理实体，包括：存储器和处理器，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第二方面或第二方面的任意可能的实现方式中的方法。
第九方面，提供了另一种网络切片管理实体，包括：存储器和处理器，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第三方面的方法。
第十方面，提供了一种通信系统，包括NSMF实体和NSCF实体。
可选地，该NSCF实体可以为第四方面或第四方面的任意可能的实现方式中的装置，或者该NSCF实体可以为第七方面或第七方面的任意可能的实现方式中的装置。
可选地，NSMF实体可以为第五方面或第五方面的任意可能的实现方式中的装置，或者该NSMF实体可以为第八方面或第八方面的任意可能的实现方式中的装置。
可选的，该通信系统还包括编排实体，该编排实体可以为第六方面或第六方面的任意可能的实现方式中的装置，或者该编排实体可以为第九方面或第九方面的任意可能的实现方式中的装置。
第十一方面，提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第一方面或第一方面的任意可能的实现方式中的方法的指令。
第十二方面，提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第二方面或第二方面的任意可能的实现方式中的方法的指令。
第十三方面，提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第三方面的方法的指令。
附图说明
图1是本发明实施例应用的通信系统的架构示例的示意图。
图2是本发明实施例应用的通信系统的另一架构示例的示意图。
图3是本发明实施例提供的通信系统的另一架构示例的示意图。
图4是本发明实施例提供的网络切片创建的方法的示意性流程图。
图5是本发明实施例提供的另一网络切片创建的方法的示意性流程图。
图6是本发明实施例提供的网络切片控制实体的示意性框图。
图7是本发明实施例提供的编排实体的示意性框图。
图8是本发明实施例提供的另一网络切片控制实体的示意性框图。
图9是本发明实施例提供的另一编排实体的示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本发明实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，PRS)、长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time  Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信系统、未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)或未来的5G系统等。
图1示出了本发明实施例应用的通信系统100。该通信系统100可以包括NSMF实体110、虚拟化或云化编排实体120、NSCF实体130和网络切片实例160。其中，网络切片实例160可以有一个或多个(图中未示例出多个)，每个网络切片实例160可以包括在虚拟化或云化基础设施170上创建部署的VNF实体140，在一个网络切片实例160可以包含一个或多个VNF实体140(如图1)。在一些情况下，网络切片实例160还可以包含一个或多个VNF服务框架(如图2或图3)。在一些情况下，网络切片实例160还可以包括一个或多个PNF实体150(如图1或图3)，在另外一些情况下，网络切片实例160也可以不包括PNF实体150(如图2)。在本发明实施例中，NSMF实体110也可以称为网络切片管理装置。虚拟化或云化编排实体120还可以称为编排装置，或者虚拟化或云化编排装置。NSCF实体130也可以称为网络切片创建的装置或者网络控制装置。
在同一个网络切片实例160的多个VNF实体140可以为相互独立的(如图1)，在同一个网络切片实例160的一个或多个VNF实体140可以共同拥有一个VNF服务框架180(如图2)，一个网络切片实例160可以包含一个或多个VNF服务框架180。在如图2的架构中，虚拟网络功能采用服务化的架构，网络功能以VNF服务形式集成在VNF服务框架上，即每个VNF实体140包含一个或多个网络功能服务实例190，以及为其运行提供支撑的VNF服务框架180，如图2和图3所示。VNF服务框架180为服务化的VNF提供通用的计算调用、存储访问、网络访问和硬件加速能力。部署的网络功能实例的网络配置是在VNF服务框架180上执行的，部署的网络功能实例的业务配置是通过VNF服务框架180传递到网络功能服务实例190的。VNF服务框架180受NSCF实体130统一控制。在某个位置的虚拟化或云化基础设施170上部署的VNF服务框架180还可以同时运行多个网络功能服务实例190，例如：在移动边缘计算(mobile edge computing，MEC)位置的UPF和APP共用一个VNF服务框架。为了描述方便，又可以将VNF实体140、PNF实体150或者运行在VNF服务框架180上的网络功能服务实例180称为网络功能实体。
网络功能实体可以承载一些网络和业务功能，具体的网络功能实体可以为用户面功能实体和/或控制面功能实体，但本发明实施例不限于此。比如：网络功能实体承载的网络和业务功能可以具体为接入管理功能(access management function，AMF)、会话管理功能(session management function，SMF)、策略控制功能(policy control function，PCF)、用户面功能(user plane function，UPF)或者应用服务器(application server，APP)。
NSMF实体110可以用于网络切片实例160的生命周期管理，例如：NSMF实体110管理网络切片实例160的创建、激活、运行、去激活或者删除等过程，在本发明实施例中，主要介绍了在网络切片实例160的创建过程中NSMF实体110的管理操作。例如：NSMF实体110接收了客户的网络切片订单，并根据存储的网络切片模板驱动编排实体120和NSCF实体130创建网络切片实例160，完成网络切片实例160的资源部署和业务配置。这里的网络切片模板是针对某类业务预先设计的供NSMF实体110创建网络切片实例160的模板，其中，网络切片模板包括了工作流、部署模板、网络切片的模型和策略。编排实 体120可以为NFV-MANO实体，也可以为PasS云平台自身的管理和编排实体。编排实体120可以根据网络切片模板中的工作流，负责网络切片实例160所需的基础设施170资源的分配，并完成VNF实体140在虚拟化或云化基础设施170上的部署，并完成与其他VNF实体140或PNF实体150之间的网络连接。NSCF实体130根据网络切片模板中的网络切片的模型、策略和网络切片订单中的规划以及业务相关的需求参数，结合各个网络功能实体的注册信息，自动生成网络切片的业务配置方案，并下发到网络切片实例160中的相应网络功能实体(包括VNF实体140和/或PNF实体150)执行，完成网络切片的业务配置。PNF实体150可以是运营商预先建设部署的通信网络专用的物理设备。虚拟化或云化基础设施170可以是运营商或云服务提供商预先部署的通用的物理设备，提供计算、内存、存储、网络资源，编排实体120控制虚拟化或云化基础设施170使用上述资源部署VNF实例，虚拟化或云化基础实施170也可以被简称为基础实施170。
上述网络切片的模型也是自动生成业务配置所需的模型，可以简称为模型，模型包括如下类型的一种或多种：资源模型、网络模型和业务模型。其中，网络模型用于指示网络切片实例中各业务所需的网络功能实体，以及网络功能实体之间的逻辑连接关系，比如：某个IoT业务需要部署UPF，SMF和eNodeB等网络功能实体；UPF通过业务网络连接到无线的eNodeB，UPF通过信令网络连接到SMF。资源模型用于指示业务规模与资源量的对应关系以及业务规模与网络带宽大小的对应关系，也就是说，网络功能实体在不同业务规模情况下占用的资源数量，以及在不同业务规模情况下需要占用的网络带宽大小。比如：每个UPF实例支撑50万会话时，需要4核CPU，16G内存和200G硬盘，UPF的业务网络接口需要10Gbps带宽。再比如：在某个具体业务中，AMF、SMF、PCF、UPF或者APP分别占用的基础设施资源数量。业务模型用于指示网络功能实体的业务配置，以及网络功能实体之间在业务配置上的相关配合关系。例如：AMF、SMF、PCF、UPF和APP业务配置上的相关配合关系，如下：AMF的业务配置要能够支持其将属于所示网络切片实例的业务请信令求发送到SMF，SMF能够找到合适的UPF来为用户建立用户面会话连接。再比如：UPF实体需要配置负责管理会话建立的SMF实体的信令连接地址，当UPF实体功能正常时，UPF实体向SMF实体发起信令连接。
上述网络切片的策略也是自动生成业务配置所需的策略，可以简称为策略，策略包括如下类型的一种或多种：网络策略、资源策略和业务策略。通常来说，策略包含了执行操作方案的触发事件或时机(以下简称事件)，执行动作的条件(以下简称条件)和动作的具体内容，其中，条件可能来自于模型中包含的关系，也可以为策略自定义的。
对于网络策略包括网络功能实体在网络切片实例中的位置要求原则，网络功能实体之间的网络带宽和时延的性能要求原则。例如：负责本地出口的UPF(即LBO UPF)和APP需要被设置在同一站点，以避免用户面传输迂回，同时满足比较严格的时延要求。其网络策略可以具体为：当工作流执行到配置UPF的LBO(本地出口功能)时，判断已经部署的所有UPF哪一个满足和APP同站点的条件，对满足条件的UPF执行的动作为打开UPF的LBO功能配置开关。
资源策略包括网络功能实体的资源占用原则，以及物理网络实体的链路的带宽使用原则。例如：确保MEC上所有网络功能实体的链路总带宽不超过数据中心的出口网络带宽。其资源策略具体为：当工作流执行到为在MEC部署的UPF实体配置网络出口带宽限制时，判断当前MEC中已经分配的UPF网络出口带宽的总和是否超过100G，如果已经 超过100G，则执行的动作为选择其他MEC的UPF进行配置；如果没有超过100G，则执行的动作为该UPF允许配置网络出口，且最大允许带宽限制为100G减去已配置带宽的总和后的差值。
业务策略包括根据网络切片的规划和网络功能实体的注册信息确定如何对网络功能实体进行业务配置的原则。例如：MEC的UPF启用LBO(local breakout，本地出口)和流识别功能；LBO串接APP后送往锚点UPF；流识别规则和串接APP规则在PCF内配置等等。其业务策略具体为：当工作流执行到对UPF进行启用LBO功能配置时，判断UPF的LBO业务是否需要部署在本MEC的APP中处理，如果判断的结果需要部署，则执行动作包括：(1)UPF配置流识别功能；(2)流识别的相应规则在PCF中配置；(3)PCF配置的业务流规则还指定用户会话数据包经过APP处理后，由UPF送往锚点UPF功能实体。
所有的策略可以以如下形式描述：执行工作流的某个步骤时，判断当前上述基本属性的具体内容或具体值是否满足一到多个条件，并根据条件是否满足执行相应的操作方案。操作方案是上述基本属性的具体内容或具体值满足策略的条件时，根据模型并结合当前创建网络切片的具体信息而自动生成的一到多个动作。这样操作方案就会满足上述策略所描述的原则。策略采用易于管理和易于调整的方式存储，比如采用XML描述事件、条件或条件组，以及执行的操作方案。模型可以采用符合TOSCA标准规范的方式进行描述和存储。
部署模板是由网络切片设计时确定的，部署模板包括了通过该部署模板创建的网络切片实例能够支撑的业务的功能性需求描述，以及性能与可靠性等非功能性需求描述。比如：功能性需求描述包含了可选的业务功能，性能包括了时延，业务容量和单个连接的带宽，可靠性可以为故障的恢复时间等。
工作流对部署网络切片实例的工作流程及其各操作步骤之间业务规则的抽象、概括描述。工作流具体包括以下工作流程的抽象、概括描述：获取和解析订单，获取订单里包含的业务相关的需求参数和网络切片的规划，将业务相关的需求参数、网络切片的规划和部署模板发送到编排实体120中，以执行NFV部署，以及向NSCF实体130发送网络切片的业务相关的需求参数、网络切片的模型、策略和规划以执行业务配置。
网络切片的规划可以包括网络切片实例的周边网络的对接规划或网络切片实例的IP地址的规划等。业务相关的需求参数可以包括网络切片实例的性能和可靠性要求。例如：以网络切片实例提供的车联网自动驾驶服务为例，该业务相关的需求参数包括了网络切片容量为支持多少辆车的连接、时延小于10毫秒和单个连接的带宽为100兆；网络切片实例的周边网络的对接规划为周边网络对接为与车联网控制服务器的连接。再比如：网络切片的规划具体包含网络切片实例支持10万用户规模和无线接入网的拓扑连接，控制面IP地址规划，用户面IP地址规划和APP的IP地址规划等。
上述通信系统100还可以包含数据库(图中未示出)，该数据库存储了网络切片的模型、策略和规划，该数据库还可以存储VNF，PNF或者VNF服务框架的注册信息。数据库可以继承在NSCF130，或者其它通信系统100中的网元中，例如：NSMF110，数据库也可以以独立网元存在。数据库可以为集中式数据库，也可以是分布式数据库。数据库的数量不做限制，可以为一个或多个。如果通信系统100包含多个数据库的话，可以将不同的信息存储到不同的数据库中，比如：将资源信息和网络位置存储到资源数据库中，将 连接拓扑存储到拓扑数据库中。
本方案涉及一种创建网络切片的系统，能够根据预先设计的网络切片模板，结合网络切片订单中的网络切片规划，自动在虚拟化或云化基础设施170上完成资源部署，对虚拟网络功能和物理网络功能进行网络连接；然后自动生成网络切片的业务配置方案(其中根据业务需求可能包括业务相关的网络配置)，在虚拟网络功能和物理网络功能上执行，实现网络切片创建过程自动化。通过本发明所述的系统和方法，可以自动创建网络切片实例。所述网络切片实例，是上述系统根据网络切片模板，通过实例化编排在网络虚拟化或云化基础设施170的物理网络中生成的一个端到端的逻辑隔离的网络切片实例，并进行业务配置，向客户提供订单中的网络服务。
图4示出了本发明实施例提供的创建网络切片的方法。该方法可以应用于上述通信系统,该方法包括如下步骤:
S401，NSMF实体110从商业支撑系统接收到客户的网络切片订单，该网络切片订单包括了网络切片模板的索引、网络切片的规划和业务相关的需求参数。其中，网络切片的规划，业务相关的需求参数在图1-3相关的实施例已经做了说明，这里不再赘述。可靠性要求
在这个步骤之前，运营商可能事先设计了一系列切片模板，并可能对每个切片模板生成了可定制化的产品。运营商还可以将该定制化的产品通过商业支撑系统发布出去，当客户通过商业支撑系统订购该定制化的产品，客户就获得了网络切片订单。NSMF实体110中还存储了网络切片模板的索引和网络切片模板的对应关系，当NSMF实体110可以从网络切片订单中获取到网络切片模板的索引，再结合存储的网络切片模板的索引和网络切片模板的对应关系，获得网络切片模板。这里的网络切片模板的索引是一个标识，可以由一串数字或者字母组成的。
NSMF实体110可以从网络切片模板中获得模型、策略、工作流和部署模板。NSMF实体110按照工作流，解析了网络切片订单的详细内容，获取到网络切片订单里包含的业务相关的需求参数和网络切片的规划。这里的模型、策略和工作流在前面部分已经描述过了，这里就不再赘述。
S402，NSMF实体110向NSCF实体130发送网络切片的业务相关的需求参数、网络切片的模型、策略和规划。
S403，NSCF实体130接收并存储NSMF实体110发送的网络切片的业务相关的需求参数、模型、策略和规划。
NSCF实体130可以将网络切片的业务相关的需求参数、模型、策略和规划存储在NSCF实体130自身，也可以将网络切片的业务相关的需求参数、模型、策略和规划存储在数据库中。
S404，NSMF实体110将业务相关的需求参数、网络切片的规划和部署模板发送到编排实体120中。
S404可以和S402之间没有先后顺序关系。
S405，编排实体120接收了业务相关的需求参数、网络切片的规划和部署模板，将业务相关的需求参数和网络切片的规划填入到部署模板中，生成NFV-NSD文件，并根据NFV-NSD文件在虚拟化或云化基础设施170上部署VNF实体140。
NFV-NSD文件中还包含需要部署的VNF实体的描述文件，VNF实体的描述文件中 包含了承载了每种类型的网络功能实体的VNF实体的数量，以及为VNF实体分配CPU、内存、磁盘和网络接口的数量和要求。编排实体120根据VNF实体的描述文件，在虚拟化或云化基础设施上部署相应数量的VNF实体。NFV-NSD文件还包含每种VNF实体的各类网络接口连接到哪个网络平面的描述，编排实体120根据这个描述将已经部署的各个VNF实体的网络接口连接到各个网络平面中，实现VNF实体之间，VNF实体和PNF实体的网络连接。对于PNF，是事先手工完成物理部署，并连接到规划的网络平面的，已经在部署模板中固定描述了，自动生成的NFV-NSD文件直接使用部署模板中的固定描述。
S406，编排实体120根据NFV-NSD文件，为已经创建成功的VNF实体140配置网络连接。
编排实体120还实现VNF实体140和其它的VNF实体之间的网络连接，以及VNF实体140和PNF实体之间的网络连接。需要说明的是：这里的其它VNF实体和PNF实体既可以和VNF实体140共同属于这个网络切片实例的，又可以和VNF实体140归属不同的网络切片实例。
编排实体120还可以为VNF实体140分配IP地址，并向VNF实体140发送该VNF实体140对应的NSCF实体130的IP地址。
S407，如果NFV-NSD文件中还存在需要在网络切片实例部署PNF实体150的工作流，那么编排实体120还根据NFV-NSD文件配置VNF实体140和PNF实体150之间的网络连接。
编排实体120还实现PNF实体150和其它的PNF实体之间的网络连接，以及PNF实体150和VNF实体之间的网络连接。需要说明的是：这里的其它VNF实体和PNF实体既可以和PNF实体150共同归属于同一个网络切片实例，又可以和PNF实体150归属不同的网络切片实例。
编排实体120还可以为PNF实体150分配IP地址，并向PNF实体150发送该PNF实体150对应的NSCF实体130的IP地址。
S408，VNF实体140根据接收到的NSCF实体130的IP地址，向NSCF实体130向发送包含注册信息的注册请求，该注册信息包含了VNF实体140的资源信息，网络位置和连接拓扑。
NSCF实体130接收了注册请求，将注册信息存储到数据库中，具体来说：资源信息可以为VNF实体140占用的虚拟机的资源(包括CPU,内存和磁盘)和分配网络接口的带宽。网络位置为VNF实体140所在的数据中心的位置信息。连接拓扑可以为VNF实体140的IP地址、以及该VNF实体140和其它VNF实体，PNF实体的连接关系。
S409，如果网络切片实例中还包含了PNF实体150，PNF实体150还可以根据接收到的NSCF实体130的IP地址，向NSCF实体130向发送包含注册信息的注册请求，该注册信息包含了PNF实体150的网络位置和连接拓扑。
NSCF实体130接收了该注册请求，将注册信息存储到数据库中，具体来说：网络位置为PNF实体150所在的数据中心的位置信息。连接拓扑可以为PNF实体150的IP地址、以及该PNF实体150和其它VNF实体、PNF实体的连接关系。
S410，编排实体120根据NFV-NSD文件的内容，通知NSMF实体110完成资源部署。该步骤在S407完成后进行，可以与S408或S409并行处理。
S411，NSMF实体110收到资源部署完成的通知后，向NSCF实体130发送业务部 署命令。
S412，NSCF实体130接收到业务部署命令后，根据业务相关的需求参数、模型、策略和规划，并结合网络功能实体(包含VNF140和/或PNF150)的注册信息，生成网络切片的业务配置方案，具体的方法如下：
NSCF实体130根据模型、策略、规划和网络功能实体的注册信息确定各个网络功能实体之间的业务配置关系，然后根据策略、业务相关的需求参数和规划，将网络切片的规划输入和业务相关的需求参数配置到网络功能实体之间的业务配置关系中，使其满足网络切片策略指定的规则，生成每个网络功能实体的具体的业务配置方案。
由于网络切片的模型中包含了网络模型，资源模型和业务模型，策略包含了网络策略、资源策略和业务策略，这些模型和策略对于每次网络切片实例创建都是通用的，这样NSCF实体130就可以得到通用的模型和策略。NSCF实体130再根据规划包含的本次创建网络切片实例的周边网络的对接规划和IP地址的规划，业务相关的需求参数包括的网络切片实例的性能和可靠性要求，以及本次创建的网络切片实例部署的网络功能实体的注册信息，就可以为本次创建的网络切片实例包含的每个网络功能实体生成具体的业务配置方案。另外，模型中包含的内容是相对稳定的抽象描述，策略中包含的内容是便于修改和调整的操作原则，如果需要，允许在创建切片前对网络切片中的默认策略进行适当的修改。
NSCF实体130从网络切片的规划，业务相关的需求参数和注册信息中获取到策略中包含的条件和动作需要的相关信息，然后判断这些相关信息是否满足网络策略包含的条件，根据判断结果和上述相关信息，确定执行的动作，最终生成具体的操作方案。这个操作方案使网络切片的规划、业务相关的需求参数和网络功能实体的注册信息中获得模型中所对应的参数符合相应的模型描述的配置关系，同时也使最终生成具体的操作方案满足相应的策略。
也就是：NSCF实体130根据网络模型，以及所述业务相关的需求参数、网络功能实体的注册信息和网络切片的规划中的一个或多个，确定部署完毕后的各个网络功能实体之间的网络配置关系，以便于满足所述网络策略；根据所述业务模型和所述网络配置关系，以及所述业务相关的需求参数、网络功能实体的注册信息和网络切片的规划中的一个或多个，确定所述部署完毕后的各个网络功能实体之间的业务配置关系，以便于满足所述业务策略；根据所述资源模型，以及所述业务相关的需求参数、网络功能实体的注册信息和网络切片的规划中的一个或多个，确定部署完毕后的各个网络功能实体之间的资源配置关系，以便于满足所述资源策略；分别获得所述各个网络功能实体的具体的业务部署配置方案。
S413，NSCF实体130向VNF实体140发送包含业务配置方案的业务配置消息，VNF实体140按照业务配置方案完成相应业务配置。
如果网络切片实例包含多个VNF实体140，NSCF实体130可以发送1条或多条业务配置消息，向不同的VNF实体140发送的业务配置消息可以是相同的，也可以是不同的，如果业务配置消息是相同的，则该条业务配置消息可以包含该网络切片实例的多个VNF实体140的业务配置方案，或者该条业务配置消息还可以包含该网络切片实例的多个VNF实体140以及1个或多个PNF150的业务配置方案。如果业务配置消息是不同的，该条业务配置消息可以只包含该VNF实体140的业务配置方案。
S414，NSCF实体130向PNF实体150发送包含业务配置方案的业务配置消息，PNF 实体150按照业务配置方案完成相应业务配置，过程同S413类似。其中S413和S414没有先后顺序要求。
S415，如果业务需要在VNF实体140的虚拟化或云化基础设施170上进行业务相关的基础网络配置方案，NSCF实体130还可以在S411中生成相关的基础网络配置方案，并将基础网络配置方案发送给编排实体120。其中，基础网络配置方案包含了虚拟化或云化基础设施170的交换网络配置，路由配置和虚拟接口。
其中步骤S415和S413，S414没有先后顺序的要求，也可以同时进行。
S416，编排实体120接收到NSCF实体130发送的配置信息，在收到S415的命令后，编排实体120对VNF实体140的基础设施170进行业务相关的网络配置。比如：配置VNF的虚拟网络接口到VNF的业务处理接口之间的IP路由等等。
S417，NSCF实体130完成所有的业务配置后向NSMF实体110发送网络切片创建完成的通知。
本方案中网络切片控制功能实体可以根据预先设计的网络切片的模型和策略，并结合订单中网络切片规划和资源部署信息，自动生成相应的网络切片业务配置方案，能够实现在不同局点灵活地自动完成切片创建。现有技术每次创建一个网络切片实例前都需要事先按照订单要求手工完成业务配置方案的修改调整，然后才能创建网络切片。而本方案网络切片控制功能实体可以自动生成待部署网络切片实例的业务配置方案，并自动创建网络切片，不再需要手工修改调整业务配置方案。
下面进一步结合图2的系统架构，介绍本发明实施例提供的创建网络切片实例的过程的例子。
S501～S504，同S401～404。
S505，编排实体120根据NFV-NSD文件在虚拟化或云化基础设施170上部署VNF服务框架180。
S506，编排实体120根据NFV-NSD文件通知创建成功的VNF服务框架180配置网络连接。
编排实体120可以实现VNF服务框架180和其它的VNF服务框架之间的网络连接，以及VNF服务框架180和PNF实体之间的网络连接。需要说明的是：这里的其它VNF服务框架和PNF实体既可以和VNF服务框架180共同属于这个网络切片实例的，又可以和VNF服务框架180归属不同的网络切片实例。
编排实体120还可以为VNF服务框架180分配IP地址，并向VNF服务框架180发送该VNF服务框架180需要连接的NSCF实体130的IP地址。
S507，VNF服务框架180根据NSCF实体的IP地址向NSCF实体130向发送包含注册信息的注册请求，该注册信息包含了VNF服务框架180的资源信息、网络位置和连接拓扑。
NSCF实体130接收了注册请求，将注册信息存储到数据库中，具体来说：资源信息可以为VNF服务框架180占用的虚拟机的资源(包括CPU,内存和磁盘)和分配网络接口的带宽。网络位置为VNF服务框架180所在的数据中心的位置信息。连接拓扑可以为VNF服务框架180的IP地址、以及VNF服务框架180和其它VNF服务框架，PNF实体的连接关系。
S508，编排实体120通知NSMF实体110完成资源部署。该步骤在S505完成后进 行，可以和S506并行处理。
S509，NSMF实体110收到资源部署完成的通知后，向NSCF实体130发送业务部署命令。
S510，NSCF实体130收到业务部署命令后，NSCF实体从网络模型中得到网络切片需要部署哪些网络功能服务，以及他们之间的连接关系；然后，NSCF根据业务相关的需求参数和资源模型，就可以计算出每一种网络功能服务需要配置几个服务实例，以及他们之间需要多大的网络连接带宽；然后，NSCF实体进一步结合从VNF服务框架的注册信息得到可用的资源和网络连续拓扑数据，计算出符合资源策略的网络功能配置方案，也就是确定好哪些网络功能服务实例部署在哪个VNF服务框架上，VNF服务框架的可用资源和他们之间的网络连接能够支持这种部署。
也就是，NSCF实体130根据业务相关的需求参数、网络切片的模型、策略和规划，并结合VNF服务框架180的注册信息，生成网络功能服务配置方案，网络服务配置方案包括在各个VNF服务框架180上需要部署网络功能服务的类型和每种类型的网络功能服务实例的数量。网络服务配置方案还可以包括各个种类的网络功能服务的软件镜像的地址。
如果VNF-NSD文件还可以包含各个种类的网络功能服务的软件镜像的地址时，可以在部署VNF服务框架时，编排实体120将该各个种类的网络功能服务的软件镜像的地址发送给VNF服务框架。此时网络服务配置方案可以不包括各个种类的网络功能服务的软件镜像的地址。
NSCF实体130确定在哪些VNF服务框架180部署哪些网络功能服务实例190。比如：NSCF实体130根据业务相关的需求参数、资源模型和规划，计算出需要的各个网络功能服务和部署的实例数量，然后按照网络切片的资源策略，依据各个VNF服务框架180的可用资源和VNF服务框架180之间的连接拓扑，确定每个VNF服务框架180需要部署的网络功能服务实例190。网络功能服务的类型可以包含移动管理，会话管理等服务类型。例如：AMF、SMF、PCF、UPF、APP。
S511，NSCF实体130向VNF服务框架180包含网络功能服务配置方案的网络功能服务部署消息。
S512，VNF服务框架180接收了网络功能服务部署消息，该VNF服务框架180根据网络功能软件镜像的地址，安装需要部署的网络功能服务的软件镜像，加载需要部署的网络功能服务，使网络功能服务实例在该VNF服务框架180上运行起来。
如果有多个VNF服务框架180的话，那么每个VNF服务框架180按照网络功能服务部署消息，按照上述过程，分别部署相应的网络功能服务。
S513，网络功能服务实例190运行起来后，可以根据VNF服务框架180提供的NSCF实体130的IP地址向NSCF实体130发起网络功能注册请求。
可选的，网络功能服务实例190也可以由VNF服务框架160监控到网络功能服务实例运行起来后待其向NSCF实体130发起网络功能注册。
S514：NSCF实体130向运行的网络功能服务实例190发送包含业务配置方案的业务配置消息，运行的网络功能服务实例190按照业务配置方案完成相应的业务配置。
NSCF实体130确定业务配置方案的过程如下：
NSCF实体130从网络切片的规划，业务相关的需求参数和注册信息中获取到网络 策略中包含的条件和动作需要的相关信息，然后判断这些相关信息是否满足网络策略包含的条件，根据判断结果和上述相关信息，确定执行的动作，最终生成具体的操作方案。这个操作方案为网络功能服务之间配置网络连接和连接带宽，使网络切片的规划、业务相关的需求参数和注册信息中获得网络模型中所对应的参数符合相应的网络模型描述的网络配置关系，同时也使最终生成具体的操作方案满足相应的网络策略。
NSCF实体130从网络切片的规划，业务相关的需求参数和注册信息中获取到业务策略中包含的条件和动作需要的相关信息，然后判断这些相关信息是否满足业务策略包含的条件，根据判断结果和上述相关信息，确定执行的动作，最终生成具体的操作方案。这个操作方案为在VNF服务框架上完成各个网络功能服务实例部署后的各个网络功能实体之间的业务配置关系，使网络切片的规划、业务相关的需求参数和注册信息中获得业务模型中所对应的参数符合相应的业务模型描述的业务配置关系，同时也使最终生成具体的操作方案满足相应的网络策略网络配置关系网络配置关系。
S515～S517：同步骤S415～S417。
例如：MEC的UPF和APP之间的业务链需要NSCF实体130通过编排实体120在虚拟化或云化基础设施170实现的虚拟交换机上完成相应的网络配置。
在该实施例中，PNF实体150也可以被安装配置在网络切片实例中，该过程同S409和S412的过程。
在本实施例中，网络切片控制功能实体不仅自动控制网络切片的业务配置，还可以根据策略控制虚拟网络功能的部署和连接拓扑，这样可以根据网络切片规划的信息，灵活调整各个虚拟网络功能的部署位置和连接拓扑，自动生成的网络切片的业务配置更好的和资源部署配合，能够更更好的适应网络切片在不同位置的业务分布差异。
下面继续举一个具体的例子来说明本发明实施例的网络切片的创建过程。
某企业在某运营商订购了移动办公的网络切片，要求运营商配置名称为“ABC”的数据网络名字(data network name，DNN)连接到企业的移动办公服务器，企业移动办公服务器的地址为AA:BB::CC。企业在订购网络切片的订单中会指定如下业务相关的需求参数：1，切片服务范围：城市A，2，业务容量需求：300Mbps的连接带宽，3，DNN的名称：“ABC”，4，对接地址：AA:BB::CC，5，可选功能：开启防攻击过滤。
运营商具备提供此类网络切片的能力，运营商可以实现对该类网络切片做网络切片的规划，规划内容如下：城市A的可用业务地址池为：AA:BB::1～100，DC-A出口路由器Router-A的内网地址CC:DD::111，外网地址为AA:BB::101；城市B的可用业务地址池为：AA:BB::501～600，DC-B出口路由器Router-B的的内网地址EE:FF::111，外网地址为AA:BB::601。
当NSMF实体收到网络切片订单时，NSMF实体可以从网络切片订单中获取到网络切片的规划，业务相关的需求参数，以及获得网络切片模板的索引。NSMF实体可以根据网络切片模板的索引，获得网络切片模板。并获取到部署模板和工作流，按照工作流的规定，将上述业务相关的需求参数、部署模板和网络规划发送到编排实体，将上述相关的需求参数，网络切片的模型、策略和规划发送到NSCF实体中。
这里的资源模型描述了每个业务地址支撑的最大业务流量为500Mbps。网络模型中包含如下内容：(1)虚拟移动网关所有业务处理虚拟机都需要配置每个业务地址；(2)对接的企业移动办公服务器的地址在业务需求参数中的“对接地址”字段的之内，并配置从 每个业务地址经过接口地址到对接地址的路由；(3)在数据中心的路由器配置经过每个接口地址到每个业务地址的路由。业务模型描述如下信息：(1)在虚拟移动网关配置订单指定的DNN；(2)在虚拟移动网关上，将业务地址到对接地址的路由关联到订单指定的DNN；(3)为该DNN开启订单指定的可选功能。
这里的资源策略包含如下内容：资源策略执行的时机(也可以称作为资源策略执行的触发事件)：配置业务地址时；资源策略执行的条件：判断虚拟移动网关配置到企业移动办公服务器的连接带宽取订单中的“业务容量需求”字段是否大于模型中的每个业务地址支撑的最大业务流量；资源策略执行的操作方案：如果“业务容量需求”字段不大于模型中的每个业务地址支撑的最大业务流量，则从规划包含的IP地址取2个未分配的业务地址，否则分配(业务容量需求/资源模型中的单个业务IP最大流量+2)个业务地址。
网络策略包含如下内容：网络策略执行的时机(也可以称作为网络策略执行的触发事件)：完成业务地址配置后；网络策略执行的条件：网络切片的规划是否存在和业务地址同网段的数据中心路由器；网络策略执行的操作方案：如果网络切片的规划存在和业务地址同网段的数据中心路由器，则从NFV部署后的每个虚拟机获得接口IP地址，按照网络模型中(2)的描述为分配的每个业务地址配置业务流量的外出路由；以及从网络切片的规划中获得NFV部署所在数据中心的路由器，并按照网络模型中(3)的描述为分配的每个业务地址配置业务流量的进入路由。如果不存在，则尝试重新分配业务地址。
业务策略包含如下内容：业务策略执行的时机：执行网络功能的业务配置时；业务策略执行的条件1：网络切片订单是否包含DNN名称；相应的业务策略执行的操作方案1：如果网络切片订单中包含了DNN名称，则DNN的名称确定上述DNN名称，并按照业务模型(2)配置DNN和对接路由关联，如果网络切片订单中没有包含了DNN名称，则将DNN名称设置为“default DNN”，并在default DNN上增加到对接路由的关联配置。业务策略执行的条件2：防攻击过滤功能是否需要被开启，业务策略执行的操作方案2：防攻击过滤功能被开启，则按照模型(3)在DNN开启配置该功能，如果防攻击过滤功能没有被开启，无操作。业务策略执行的条件3：流量强制限制功能是否被开启，如果流量强制限制功能被开启，按照模型配置DNN的流量强制限制，限制上限为订单中的“业务容量需求”字段，如果流量强制限制功能没有被开启，无操作。
编排实体按照上述流程介绍，生成NFV-NSD文件，并根据NFV-NSD文件，在城市A部署了虚拟移动网关GW-A，根据业务容量分配了两个负荷分担的业务处理虚拟机，并为GW-A的两个业务处理虚拟机分配了数据中心DC-A内可用的接口IP地址CC:DD::1和CC:DD::2，并将该他们的接口和路由器A的内网口CC:DD::111连接到同一个VLAN上，完成NFV部署。
NSCF实体获得上述的模型、策略、规划、业务相关的需求参数以及虚拟移动网关GW-A上报的注册信息。NSCF实体读取资源策略，在配置业务地址时，判断出业务相关的需求参数包含的业务容量需求大于资源模型中包含的每个业务地址支撑的最大业务流量，则从规划的地址池中选择两个未分配的业务地址作为虚拟移动网关的两个业务地址。NSCF实体读取网络策略，在完成业务地址配置后，判断网络切片的规划存在和业务地址同网段的数据中心路由器，则从NFV部署后的每个虚拟机获得接口IP地址，按照网络模型中(2)的描述为分配的每个业务地址配置企业移动办公服务器的外出路由；从网络切片的规划中获得NFV部署所在数据中心的路由器，并按照网络模型中(3)的描述为分配 的每个业务地址配置企业移动办公服务器的进入路由。NSCF实体读取业务策略，在执行网络功能的业务配置时，确定网络切片订单是否包含DNN名称，则按照业务模型(2)配置DNN和对接路由关联。并且由于防攻击过滤功能需要被开启，则打开防攻击过滤功能。应理解，上述例子是为了帮助本领域技术人员更好地理解本发明实施例，而非要限制本发明实施例的范围。本领域技术人员根据所给出的上述示例，显然可以进行各种等价的修改或变化，这样的修改或变化也落入本发明实施例的范围内。
应理解，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本发明实施例的实施过程构成任何限定。
上文中结合图1至图5，详细描述了根据本发明实施例的网络控制的方法，下面将结合图6至图9，详细描述根据本发明实施例的网络切片控制实体。
图6示出了本发明实施例提供的网络切片控制实体600，包括：
收发单元610，用于接收NSMF实体发送的业务部署命令；
获取单元620，用于根据所述业务部署命令，获取业务相关的需求参数、网络切片的模型、策略和规划，以及网络功能实体的注册信息；
生成单元630，用于根据网络切片的模型和策略，以及所述业务相关的需求参数、网络功能实体的注册信息和网络切片的规划中的一个或多个，生成网络功能实体的业务配置方案；
收发单元610，还用于将所述业务配置方案发送到所述网络功能实体。
作为一个可选实施例，该网络切片控制实体600还包括：存储单元640，用于存储业务相关的需求参数、网络切片的模型、策略和规划，或者存储网络功能实体的注册信息。此时收发单元610，还用于接收NSMF实体发送的业务相关的需求参数、网络切片的模型、策略和规划或者接收网络功能实体包含注册信息的注册请求。
作为一个可选实施例，该生成单元630，还用于为所述VNF实体所承载的虚拟化或云化基础设施生成基础网络配置方案，其中，所述基础网络配置方案包含了所述虚拟化或云化基础设施的交换网络配置，路由配置和虚拟接口的配置；此时收发单元610，还用于将所述基础网络配置方案发送到编排实体。
作为一个可选实施例，该生成单元630，还用于根据网络切片的模型、策略和规划以及VNF服务框架的注册信息，生成网络功能服务配置方案，其中，所述网络服务配置方案包括在各个所述VNF服务框架上需要部署网络功能服务的类型、每种类型的网络功能服务实例的数量，以及网络功能服务的软件镜像的地址；此时收发单元610，还用于向所述VNF服务框架发送包含所述网络功能服务配置方案的网络功能服务部署消息。
应理解，这里的网络切片控制实体600以功能单元的形式体现。在一个可选例子中，本领域技术人员可以理解，网络切片控制实体600可以具体为上述实施例中的网络切片控制实体，网络切片控制实体可以用于执行上述方法实施例中与网络切片控制实体对应的各个流程和/或步骤，为避免重复，在此不再赘述。
图7示出了本发明实施例提供的编排实体700，包括：
收发单元710，用于接收NSMF实体发送的资源部署命令；
部署和配置单元720，用于在虚拟化或云化基础设施上部署VNF实体和配置VNF实体的网络连接；或者根据资源部署命令，在上述虚拟化或云化基础设施上部署VNF服务框架和配置所述VNF服务框架的网络连接。
应理解，这里的编排实体700以功能单元的形式体现。在一个可选例子中，本领域技术人员可以理解，编排实体700可以具体为上述实施例中的编排实体，编排实体700可以用于执行上述方法实施例中与编排实体对应的各个流程和/或步骤，为避免重复，在此不再赘述。
还应理解，在本发明实施例中，术语“单元”可以指应用特有集成电路(Application Specific Integrated Circuit，ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。
图8和图9所示为本发明实施例提供的计算机设备示意图。计算机设备800包括至少一个处理器801，通信总线802，存储器803以及至少一个通信接口804。
处理器801可以是一个通用中央处理器(CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本发明方案程序执行的集成电路。
通信总线802可包括一通路，在上述组件之间传送信息。所述通信接口804，使用任何收发器一类的设备，用于与其他设备或通信网络通信，如以太网，无线接入网(RAN)，无线局域网(Wireless Local Area Networks，WLAN)等。
存储器803可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、只读光盘(Compact Disc Read-Only Memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过总线与处理器相连接。存储器也可以和处理器集成在一起。
其中，所述存储器803用于存储执行本发明方案的应用程序代码，并由处理器801来控制执行。所述处理器801用于执行所述存储器803中存储的应用程序代码。
在具体实现中，作为一种实施例，处理器801可以包括一个或多个CPU，例如图8中的CPU0和CPU1。
在具体实现中，作为一种实施例，计算机设备800可以包括多个处理器，例如图8中的处理器801和处理器808。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中，作为一种实施例，计算机设备800还可以包括输出设备805和输入设备806。输出设备805和处理器801通信，可以以多种方式来显示信息。例如，输出设备805可以是液晶显示器(liquid crystal display，LCD),发光二级管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备806和处理器801通信，可以以多种方式接受用户的输入。例如，输入设备806可以是鼠标、键盘、触摸屏设备或传感设备等。
上述的计算机设备800可以是一个通用计算机设备或者是一个专用计算机设备。在 具体实现中，计算机设备800可以是台式机、便携式电脑、网络服务器、掌上电脑(Personal Digital Assistant，PDA)、移动手机、平板电脑、无线终端设备、通信设备、嵌入式设备或有图8中类似结构的设备。本发明实施例不限定计算机设备800的类型。
如图1-6中的网络切片控制实体可以为图8所示的设备，网络切片控制实体的存储器中存储了一个或多个软件模块。网络切片控制实体可以通过处理器以及存储器中的程序代码来实现软件模块，实现网络切片创建。
如图1-5和7中的编排实体可以为图9所示的设备，编排实体的存储器中存储了一个或多个软件模块。编排实体可以通过处理器以及存储器中的程序代码来实现软件模块，实现网络切片创建。
应理解，在本发明实施例中，该处理器可以是中央处理单元(Central Processing Unit，CPU)，该处理器还可以是其他通用处理器、数字上行信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
存储器可以包括只读存储器和随机存取存储器，并向处理器提供指令和数据。存储器的一部分还可以包括非易失性随机存取存储器。例如，存储器还可以存储设备类型的信息。该处理器可以用于执行存储器中存储的指令，并且该处理器执行该指令时，该处理器可以执行上述方法实施例中与终端设备对应的各个步骤。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本发明实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器执行存储器中的指令，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
本发明实施例还提供了一种通信系统，该系统可以包括上述实施例中的任意策略控制功能实体和上述实施例中的任意策略执行功能实体。
可选地，该通信系统还可以包括数据存储功能实体，该数据存储功能实体用于存储下列信息中的至少一种：一个或多个网络功能实体中每个网络功能实体的至少一个已部署实例的信息、可部署网络功能实体的至少一个物理位置中每个物理位置的信息，其中，每个已部署实例的信息可以包括下列信息中的至少一种：部署位置信息、占用资源信息、开启的处理能力的信息和容量利用率信息，每个物理位置的信息包括该每个物理位置的位置信息和/或可用资源信息。
可选地，该通信系统可以具体为图1所示的通信系统，但本发明实施例不限于此。
应理解，上文对本发明实施例的描述着重于强调各个实施例之间的不同之处，未提到的相同或相似之处可以互相参考，为了简洁，这里不再赘述。
此外，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元 及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能实体究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能实体，但是这种实现不应认为超出本发明的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能实体划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能实体单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能实体如果以软件功能实体单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (20)

  1. 一种网络切片创建的方法，其特征在于，包括：
    接收网络切片管理功能NSMF实体发送的业务部署命令；
    根据所述业务部署命令，获取业务相关的需求参数、网络切片的模型、策略和规划，以及网络功能实体的注册信息；
    根据所述网络切片的模型和策略，以及所述业务相关的需求参数、网络功能实体的注册信息和网络切片的规划中的一个或多个，生成网络功能实体的业务配置方案；
    将所述业务配置方案发送到所述网络功能实体。
  2. 根据权利要求1所述的方法，其特征在于，在接收所述NSMF实体发送的业务部署命令之前，还包括：
    接收所述NSMF实体发送的业务相关的需求参数、网络切片的模型、策略和规划；
    存储所述业务相关的需求参数、网络切片的模型、策略和规划。
  3. 根据权利要求1所述的方法，其特征在于，所述网络切片的模型包括网络模型，资源模型和业务模型中的一个或多个，其中，所述网络模型用于指示网络切片实例中各业务所需的网络功能实体，以及网络功能实体之间的逻辑连接关系；所述资源模型用于指示业务规模与资源量的对应关系以及业务规模与网络带宽大小的对应关系；所述业务模型用于指示网络功能实体的业务配置，以及网络功能实体之间在业务配置上的相关配合关系；
    所述网络切片的策略包括网络策略、资源策略和业务策略中的一个或多个，其中，网络策略包括各种网络功能实体在网络切片实例中的位置要求原则、网络功能实体之间的网络带宽和时延的性能要求原则；资源策略包括网络功能实体的资源占用原则以及物理网络实体的链路的带宽使用原则；业务策略包括根据所述网络切片的规划和网络功能实体的注册信息确定如何对所述网络功能实体进行业务配置的原则；
    所述网络切片的规划包括以下一种或多种：网络切片实例与周边网络的对接规划和网络切片实例的互联网协议IP地址的规划。
  4. 根据权利要求1所述的方法，其特征在于，在所述接收所述NSMF实体发送的业务部署命令之前，还包括：
    所述NSCF实体接收所述网络功能实体包含注册信息的注册请求；
    存储所述网络功能实体的注册信息。
  5. 根据权利要求4所述的方法，其特征在于，所述网络功能实体具体为虚拟网络功能VNF实体，物理网络功能PNF实体或运行在VNF服务框架上的网络功能服务实例。
  6. 根据权利要求4所述的方法，其特征在于，所述注册信息包括网络功能实体的网络位置和连接拓扑，当网络功能实体具体为VNF实体或运行在VNF服务框架上的网络功能服务实例时，所述注册信息还包括资源信息。
  7. 根据权利要求6所述的方法，其特征在于，所述资源信息包括VNF实体占用的虚拟机的资源和分配网络接口的带宽，或者VNF服务框架占用的虚拟机的资源和分配网络接口的带宽。
  8. 根据权利要求3所述的方法，其特征在于，所述根据所述网络切片的模型和策略，以及所述业务相关的需求参数、网络功能实体的注册信息和网络切片的规划中的一个或多个，生成网络功能实体的业务配置方案具体包括：
    根据所述网络模型，以及所述业务相关的需求参数、网络功能实体的注册信息和网络切片的规划中的一个或多个，确定部署完毕后的各个网络功能实体之间的网络配置关系，以便于满足所述网络策略；
    根据所述业务模型和所述网络配置关系，以及所述业务相关的需求参数、网络功能实体的注册信息和网络切片的规划中的一个或多个，确定所述部署完毕后的各个网络功能实体之间的业务配置关系，以便于满足所述业务策略；
    根据所述资源模型，以及所述业务相关的需求参数、网络功能实体的注册信息和网络切片的规划中的一个或多个，确定部署完毕后的各个网络功能实体之间的资源配置关系，以便于满足所述资源策略；
    分别获得所述各个网络功能实体的具体的业务部署配置方案。
  9. 根据权利要求1所述的方法，其特征在于，还包括：为所述VNF实体所承载的虚拟化或云化基础设施生成基础网络配置方案，其中，所述基础网络配置方案包含了所述虚拟化或云化基础设施的交换网络配置，路由配置和虚拟接口的配置；
    将所述基础网络配置方案发送到编排实体。
  10. 根据权利要求5所述的方法，其特征在于，在所述收所述NSMF实体发送的业务部署命令之前，还包括：
    收到业务部署命令，获取所述业务相关的需求参数、所述网络切片的模型、策略和规划；根据所述业务相关的需求参数、所述网络切片的模型、策略和规划以及VNF服务框架的注册信息，生成网络功能服务配置方案，其中，所述网络服务配置方案包括在各个所述VNF服务框架上需要部署网络功能服务的类型、每种类型的网络功能服务实例的数量；
    向所述VNF服务框架发送包含所述网络功能服务配置方案的网络功能服务部署消息。
  11. 一种网络切片创建系统，其特征在于，包括网络切片管理NSMF实体和网络切片控制功能NSCF实体，其中：
    所述NSMF实体，用于向所述NSCF实体发送业务部署命令
    所述NSCF实体，用于接收所述NSMF实体发送的业务部署命令；根据所述业务部署命令，获取业务相关的需求参数、网络切片的模型、策略和规划，以及网络功能实体的注册信息；根据所述网络切片的模型和策略，以及所述网络功能实体的注册信息和网络切片的规划中的一个或多个，生成网络功能实体的业务配置方案；将所述业务配置方案发送到所述一个或者多个网络功能实体。
  12. 根据权利要求11所述的系统，其特征在于，所述NSMF实体，还用于向所述NSCF实体发送所述业务相关的需求参数、网络切片的模型、策略和规划；
    所述NSCF实体，还用于接收所述NSMF实体发送的所述业务相关的需求参数、所述网络切片的模型、策略和规划，存储所述业务相关的需求参数、所述网络切片的模型、策略和规划。
  13. 根据权利要求11所述的系统，其特征在于，还包括一个或多个网络功能实体，所述网络功能实体用于接收所述NSCF实体发送的业务配置方案，根据所述业务配置方案，进行业务配置。
  14. 根据权利要求13所述的系统，其特征在于，所述网络功能实体，还用于向所述 NSCF实体发送体包含注册信息的注册请求；
    所述NSCF实体，还用于接收所述网络功能实体发送的所述包含注册信息的注册请求，存储所述注册信息。
  15. 根据权利要求13所述的系统，其特征在于，所述网络功能实体具体为虚拟网络功能VNF实体，物理网络功能PNF实体或运行在VNF服务框架上的网络功能服务实例。
  16. 根据权利要求11所述的系统，其特征在于，所述NSCF实体具体用于：
    根据所述网络模型，以及所述业务相关的需求参数、网络功能实体的注册信息和网络切片的规划中的一个或多个，确定部署完毕后的各个网络功能实体之间的网络配置关系，以便于满足所述网络策略；
    根据所述业务模型和所述网络配置关系，以及所述业务相关的需求参数、网络功能实体的注册信息和网络切片的规划中的一个或多个，确定所述部署完毕后的各个网络功能实体之间的业务配置关系，以便于满足所述业务策略；
    根据所述资源模型，以及所述业务相关的需求参数、网络功能实体的注册信息和网络切片的规划中的一个或多个，确定部署完毕后的各个网络功能实体之间的资源配置关系，以便于满足所述资源策略；
    分别获得所述各个网络功能实体的具体的业务部署配置方案。
  17. 根据权利要求11所述的系统，其特征在于，还包括虚拟化或云化编排实体，用于接收所述NSMF实体发送的资源部署命令，根据所述资源部署命令，在虚拟化或云化基础设施上部署VNF实体和配置VNF实体的网络连接；或者根据资源部署命令，在上述虚拟化或云化基础设施上部署VNF服务框架和配置所述VNF服务框架的网络连接。
  18. 根据权利要求11所述的系统，其特征在于，所述NSCF实体，还用于为所述VNF实体所承载的虚拟化或云化基础设施生成基础网络配置方案，其中，所述基础网络配置方案包含了所述虚拟化或云化基础设施的交换网络配置，路由配置和虚拟接口的配置；将所述基础网络配置方案发送到所述编排实体。
  19. 根据权利要求11所述的系统，其特征在于，所述NSCF实体，还用于：接收业务部署命令，获取所述业务相关的需求参数、网络切片的模型、策略和规划；根据所述业务相关的需求参数、网络切片的模型、策略和规划以及VNF服务框架的注册信息，生成网络功能服务配置方案，其中，所述网络服务配置方案包括在各个所述VNF服务框架上需要部署网络功能服务的类型、每种类型的网络功能服务实例的数量；向所述VNF服务框架发送包含所述网络功能服务配置方案的网络功能服务部署消息；
    所述VNF服务框架，具体用于接收了所述NSCF实体发送的网络功能服务部署消息，根据网络功能软件镜像的地址，安装需要部署的网络功能服务的软件镜像，加载需要部署的网络功能服务。
  20. 一种网络切片创建的装置，其特征在于，包括处理器和存储器，所述存储器用于存储程序指令，所述处理器用于读取所述存储器中的程序指令，并根据所述存储器中的程序指令执行权利要求1-10任一项所述的方法。
PCT/CN2017/085368 2017-05-22 2017-05-22 网络切片创建的方法、装置以及通信系统 WO2018213991A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
PCT/CN2017/085368 WO2018213991A1 (zh) 2017-05-22 2017-05-22 网络切片创建的方法、装置以及通信系统
JP2019564046A JP6823203B2 (ja) 2017-05-22 2017-05-22 ネットワークスライスを作成するための方法及び装置並びに通信システム
EP17911014.3A EP3609161B1 (en) 2017-05-22 2017-05-22 Network slice creating method and apparatus, and communication system
CN201780089288.6A CN110476402B (zh) 2017-05-22 2017-05-22 网络切片创建的方法、装置以及通信系统
US16/680,991 US11146453B2 (en) 2017-05-22 2019-11-12 Method and apparatus for creating network slice, and communications system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/085368 WO2018213991A1 (zh) 2017-05-22 2017-05-22 网络切片创建的方法、装置以及通信系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/680,991 Continuation US11146453B2 (en) 2017-05-22 2019-11-12 Method and apparatus for creating network slice, and communications system

Publications (1)

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

Family

ID=64395057

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/085368 WO2018213991A1 (zh) 2017-05-22 2017-05-22 网络切片创建的方法、装置以及通信系统

Country Status (5)

Country Link
US (1) US11146453B2 (zh)
EP (1) EP3609161B1 (zh)
JP (1) JP6823203B2 (zh)
CN (1) CN110476402B (zh)
WO (1) WO2018213991A1 (zh)

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110535679A (zh) * 2019-07-09 2019-12-03 中移（杭州）信息技术有限公司 切片的管理方法、架构、网络切片销售平台和管理系统
CN111065116A (zh) * 2019-12-10 2020-04-24 中盈优创资讯科技有限公司 一种端到端切片自动化部署方法及系统
CN111416730A (zh) * 2019-01-08 2020-07-14 三星电子株式会社 在无线通信系统中控制端到端网络的管理设备和方法
CN112910668A (zh) * 2019-11-19 2021-06-04 上海华为技术有限公司 一种业务配置方法，业务配置装置以及业务配置设备
CN112910672A (zh) * 2019-12-04 2021-06-04 中盈优创资讯科技有限公司 切片组网方法、装置及系统
CN112954084A (zh) * 2019-12-11 2021-06-11 中移物联网有限公司 边缘计算的处理方法、网络功能实例及边缘服务管控中心
CN113472595A (zh) * 2021-08-10 2021-10-01 中国联合网络通信集团有限公司 核心网子网切片创建方法、功能实体和切片管理系统
CN113596922A (zh) * 2021-06-30 2021-11-02 广西东信易通科技有限公司 一种基于5g基站定制化切片能力的小范围自动通知系统及方法
CN113708948A (zh) * 2020-05-22 2021-11-26 亚信科技（中国）有限公司 切片流程的控制方法、装置、模块、以及计算机可读介质
US11516091B2 (en) 2019-04-22 2022-11-29 At&T Intellectual Property I, L.P. Cloud infrastructure planning assistant via multi-agent AI
US11576115B2 (en) * 2020-11-03 2023-02-07 Verizon Patent And Licensing Inc. Systems and methods for designing network slices using extensible components

Families Citing this family (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109219090B (zh) * 2017-06-30 2022-11-08 中兴通讯股份有限公司 商务特性数据上报方法及装置、网络切片编排方法及装置
US11382150B2 (en) * 2018-03-26 2022-07-05 Apple Inc. System and method of managing PNF connectivity in a network slice instance
WO2019199362A1 (en) * 2018-04-11 2019-10-17 Intel IP Corporation Flexible multi-access edge computing (mec) services consumption through hosts zoning
US10484911B1 (en) 2018-05-23 2019-11-19 Verizon Patent And Licensing Inc. Adaptable radio access network
DE112020001183T5 (de) * 2019-03-11 2022-03-17 Intel Corporation Multi-slice-unterstützung für mec-fähige 5g-implementierungen
WO2021038335A1 (en) * 2019-08-30 2021-03-04 Telefonaktiebolaget Lm Ericsson (Publ) Method for onboarding a network function package in onap
US11044172B2 (en) * 2019-09-25 2021-06-22 Level 3 Communications, Llc Network service activation system
KR20210101373A (ko) * 2020-02-07 2021-08-19 삼성전자주식회사 무선 통신 시스템에서 네트워크 슬라이스를 생성하기 위한 장치 및 방법
CN111343027B (zh) * 2020-03-11 2022-08-26 中国电子科技集团公司第五十四研究所 一种基于遗传算法的网络切片部署方法和装置
US11444851B2 (en) * 2020-04-13 2022-09-13 Verizon Patent And Licensing Inc. Systems and methods of using adaptive network infrastructures
CN113301587B (zh) * 2020-04-15 2022-06-03 阿里巴巴集团控股有限公司 节点管控方法、网络系统、设备及存储介质
CN113746657A (zh) * 2020-05-30 2021-12-03 华为技术有限公司 一种业务配置方法及其装置
US11202234B1 (en) 2020-06-03 2021-12-14 Dish Wireless L.L.C. Method and system for smart operating bandwidth adaptation during power outages
US11265135B2 (en) * 2020-06-03 2022-03-01 Dish Wireless Llc Method and system for slicing assigning for load shedding to minimize power consumption where gNB is controlled for slice assignments for enterprise users
CN113839796A (zh) * 2020-06-23 2021-12-24 中兴通讯股份有限公司 切片业务处理方法、装置、网络设备和可读存储介质
US11470549B2 (en) 2020-07-31 2022-10-11 Dish Wireless L.L.C. Method and system for implementing mini-slot scheduling for all UEs that only are enabled to lower power usage
US11405941B2 (en) 2020-07-31 2022-08-02 DISH Wireless L.L.C Method and system for traffic shaping at the DU/CU to artificially reduce the total traffic load on the radio receiver so that not all the TTLs are carrying data
US11412415B2 (en) 2020-08-13 2022-08-09 Dish Wireless L.L.C. Systems and methods for zero-touch interworking of network orchestration with data platform and analytics in virtualized 5G deployment
CN114423024B (zh) * 2020-09-10 2022-11-25 华为技术有限公司 Wlan驱动框架、wlan驱动框架的组件化方法及相关设备
CN114258020B (zh) * 2020-09-25 2023-12-12 中移物联网有限公司 专有云部署方法、平台及电子设备
CN112333731B (zh) * 2020-10-19 2021-07-20 广州爱浦路网络技术有限公司 网络层地址资源分配方法、计算机装置和存储介质
CN112367628B (zh) * 2020-11-12 2024-01-23 广东电网有限责任公司 一种电力物联网的智能化网络切片实例化方法及系统
CN112616124B (zh) * 2020-12-03 2023-11-24 广东电力通信科技有限公司 一种基于5g网络切片的电力物联网安全管理方法及系统
CN112636959B (zh) * 2020-12-14 2022-06-21 广西东信易通科技有限公司 一种区分业务类型的网络切片隐私号业务保障系统及方法
CN112671565B (zh) * 2020-12-16 2023-02-21 中盈优创资讯科技有限公司 一种基于信令链路的5g核心网拓扑发现方法及装置
CN114666211B (zh) * 2020-12-23 2023-11-17 上海华为技术有限公司 一种通信方法、模型处理方法及相关设备
CN112822050B (zh) * 2021-01-05 2023-05-02 北京信息科技大学 用于部署网络切片的方法和装置
CN115208747B (zh) * 2021-04-13 2024-02-23 中移(上海)信息通信科技有限公司 智能电网的网络切片管理方法及管理系统
CN113381888B (zh) * 2021-06-08 2024-03-05 广东电网有限责任公司清远供电局 控制方法、装置、设备及存储介质
CN115915146A (zh) * 2021-09-30 2023-04-04 中兴通讯股份有限公司 切片业务配置方法、网络设备、网络系统及存储介质
CN114024846A (zh) * 2021-11-18 2022-02-08 上海宝创网络科技有限公司 一种生成网关功能的方法及设备
CN114268535B (zh) * 2021-12-20 2024-01-19 杭州东方通信软件技术有限公司 一种5g切片产品开通方法及装置
WO2023131403A1 (en) * 2022-01-05 2023-07-13 Telefonaktiebolaget Lm Ericsson (Publ) Automated service driven virtual network function dimensioning
CN116939725A (zh) * 2022-04-01 2023-10-24 华为技术有限公司 通信业务保障方法及装置
CN115001976B (zh) * 2022-05-18 2023-11-17 广东省电信规划设计院有限公司 网络切片智能化订购方法、装置和计算机存储介质

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017076086A1 (zh) * 2015-11-02 2017-05-11 中兴通讯股份有限公司 一种网络切片能力开放的方法、装置及系统

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8261295B1 (en) * 2011-03-16 2012-09-04 Google Inc. High-level language for specifying configurations of cloud-based deployments
CN103269282A (zh) * 2013-04-25 2013-08-28 杭州华三通信技术有限公司 网络配置自动部署方法和装置
US9436443B2 (en) * 2014-08-28 2016-09-06 At&T Intellectual Property I, L.P. Software defined network controller
WO2016086991A1 (en) * 2014-12-04 2016-06-09 Nokia Solutions And Networks Management International Gmbh Steering of virtualized resources
JP6552130B2 (ja) * 2015-01-20 2019-07-31 ホアウェイ・テクノロジーズ・カンパニー・リミテッド Ｎｆｖの管理およびオーケストレーションのための方法および装置
WO2016121834A1 (ja) * 2015-01-29 2016-08-04 日本電気株式会社 ネットワーク機能仮想化管理方法とシステムと装置とプログラム
CN104639653B (zh) * 2015-03-05 2019-04-09 北京掌中经纬技术有限公司 基于云架构的自适应方法及系统
JP2017011467A (ja) * 2015-06-22 2017-01-12 日本電信電話株式会社 ネットワーク管理装置およびネットワーク管理プログラム
US10644955B2 (en) * 2015-08-21 2020-05-05 Huawei Technologies Co., Ltd. Method and apparatus for network slicing
JPWO2017057025A1 (ja) * 2015-09-30 2018-03-01 株式会社Ｎｔｔドコモ サービス割当決定方法
US20170163587A1 (en) * 2015-12-04 2017-06-08 Microsoft Technology Licensing, Llc Onboarding of a Service Based on Client Feedback of Task Completion

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017076086A1 (zh) * 2015-11-02 2017-05-11 中兴通讯股份有限公司 一种网络切片能力开放的方法、装置及系统

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "Update on network slice concepts", S5-171660 , 3GPP TSG SA WG5 (TELECOM MANAGEMENT) MEETING #112, 31 March 2017 (2017-03-31), XP051248756 *
ORANGE: "pCR TR 28.800 - Model of roles, use cases and architecture for network slice management", S5-166184, 3GPP TSG SA WG5 (TELECOM MANAGEMENT) MEETING #110, vol. 180, 18 November 2016 (2016-11-18), XP051186326 *
See also references of EP3609161A4 *

Cited By (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111416730A (zh) * 2019-01-08 2020-07-14 三星电子株式会社 在无线通信系统中控制端到端网络的管理设备和方法
CN111416730B (zh) * 2019-01-08 2024-02-20 三星电子株式会社 在无线通信系统中控制端到端网络的管理设备和方法
US11516091B2 (en) 2019-04-22 2022-11-29 At&T Intellectual Property I, L.P. Cloud infrastructure planning assistant via multi-agent AI
CN110535679A (zh) * 2019-07-09 2019-12-03 中移（杭州）信息技术有限公司 切片的管理方法、架构、网络切片销售平台和管理系统
CN110535679B (zh) * 2019-07-09 2022-11-29 中移（杭州）信息技术有限公司 切片的管理方法、架构、网络切片销售平台和管理系统
CN112910668A (zh) * 2019-11-19 2021-06-04 上海华为技术有限公司 一种业务配置方法，业务配置装置以及业务配置设备
CN112910672A (zh) * 2019-12-04 2021-06-04 中盈优创资讯科技有限公司 切片组网方法、装置及系统
CN112910672B (zh) * 2019-12-04 2023-04-28 中盈优创资讯科技有限公司 切片组网方法、装置及系统
CN111065116A (zh) * 2019-12-10 2020-04-24 中盈优创资讯科技有限公司 一种端到端切片自动化部署方法及系统
CN111065116B (zh) * 2019-12-10 2021-03-16 中盈优创资讯科技有限公司 一种端到端切片自动化部署方法及系统
CN112954084A (zh) * 2019-12-11 2021-06-11 中移物联网有限公司 边缘计算的处理方法、网络功能实例及边缘服务管控中心
CN113708948A (zh) * 2020-05-22 2021-11-26 亚信科技（中国）有限公司 切片流程的控制方法、装置、模块、以及计算机可读介质
US11576115B2 (en) * 2020-11-03 2023-02-07 Verizon Patent And Licensing Inc. Systems and methods for designing network slices using extensible components
US20230142350A1 (en) * 2020-11-03 2023-05-11 Verizon Patent And Licensing Inc. Systems and methods for designing network slices using extensible components
US11937178B2 (en) 2020-11-03 2024-03-19 Verizon Patent And Licensing Inc. Systems and methods for designing network slices using extensible components
CN113596922A (zh) * 2021-06-30 2021-11-02 广西东信易通科技有限公司 一种基于5g基站定制化切片能力的小范围自动通知系统及方法
CN113596922B (zh) * 2021-06-30 2023-11-21 广西东信易通科技有限公司 一种基于5g基站定制化切片能力的自动通知系统及方法
CN113472595B (zh) * 2021-08-10 2023-04-18 中国联合网络通信集团有限公司 核心网子网切片创建方法、功能实体和切片管理系统
CN113472595A (zh) * 2021-08-10 2021-10-01 中国联合网络通信集团有限公司 核心网子网切片创建方法、功能实体和切片管理系统

Also Published As

Publication number Publication date
US20200084107A1 (en) 2020-03-12
EP3609161B1 (en) 2021-08-04
JP6823203B2 (ja) 2021-01-27
CN110476402A (zh) 2019-11-19
CN110476402B (zh) 2021-03-30
US11146453B2 (en) 2021-10-12
EP3609161A1 (en) 2020-02-12
JP2020521387A (ja) 2020-07-16
EP3609161A4 (en) 2020-04-22

Similar Documents

Publication Publication Date Title
WO2018213991A1 (zh) 网络切片创建的方法、装置以及通信系统
US11354167B2 (en) Container service management method and apparatus
US11611487B2 (en) Model driven process for automated deployment of domain 2.0 virtualized services and applications on cloud infrastructure
EP3512233B1 (en) Method for managing network slice and management unit
CN107925587B (zh) 用于网络切片的方法和装置
US10999740B2 (en) Network slice management method, management unit, and system
CN109586938B (zh) 实例业务拓扑的生成方法及装置
US20190109827A1 (en) Providing a Basic Firewall Using a Virtual Networking Function
CN106921977B (zh) 一种基于业务流的服务质量规划方法、装置及系统
US10924966B2 (en) Management method, management unit, and system
US11641308B2 (en) Software defined networking orchestration method and SDN controller
CN111224821B (zh) 安全服务部署系统、方法及装置
CN107959582B (zh) 一种切片实例的管理方法及装置
US20200403970A1 (en) Providing Network Address Translation in a Software Defined Networking Environment
JP6533475B2 (ja) 管理装置、および、ネットワークサービス管理方法
CN105144110A (zh) 基于网络活动自动配置外部服务
CN106464515B (zh) 一种虚拟网管的部署方法、装置和虚拟网络系统
US11909603B2 (en) Priority based resource management in a network functions virtualization (NFV) environment
WO2016197301A1 (zh) Nfv系统中的策略协调方法和装置
EP3534578B1 (en) Resource adjustment method, device and system
KR20180029790A (ko) 네트워크 기능 가상화 운영 장치 및 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17911014

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017911014

Country of ref document: EP

Effective date: 20191104

ENP Entry into the national phase

Ref document number: 2019564046

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE