WO2019137516A1 - 网络切片部署方法及其装置 - Google Patents

网络切片部署方法及其装置 Download PDF

Info

Publication number
WO2019137516A1
WO2019137516A1 PCT/CN2019/071540 CN2019071540W WO2019137516A1 WO 2019137516 A1 WO2019137516 A1 WO 2019137516A1 CN 2019071540 W CN2019071540 W CN 2019071540W WO 2019137516 A1 WO2019137516 A1 WO 2019137516A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
network slice
slice
instance
coexistence
Prior art date
Application number
PCT/CN2019/071540
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 EP19738338.3A priority Critical patent/EP3735043B1/en
Publication of WO2019137516A1 publication Critical patent/WO2019137516A1/zh
Priority to US16/924,487 priority patent/US11303526B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H04W48/06—Access restriction performed under specific conditions based on traffic conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service

Definitions

  • the embodiment of the present invention relates to the field of communications technologies, and in particular, to a network slice deployment method and device thereof.
  • the fifth generation mobile communication (the 5th-generation, 5G) system introduces the concept of network slice. To cope with the difference in network performance requirements of different communication services.
  • Network slicing refers to the customization of different logical networks based on different service requirements on a physical or virtual network infrastructure. Network slicing is to meet the network function set and resource combination required by a certain type of user or certain services.
  • a network slicing is a complete logical network, capable of providing communication services and having certain network capabilities.
  • the network slice may include a radio access network (RAN) and a core network (CN).
  • Basic network slice types include enhanced mobile broadband (eMBB) network slicing, massive machine type communication (mMTC) network slicing and low latency, high latency communications (ultra-reliable and low latency communications) , uRLLC) network slicing.
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communication
  • uRLLC ultra-reliable and low latency communications
  • a network slice instance is a real-world logical network that can meet certain network characteristics or service requirements.
  • a complete network sharding instance can provide complete end-to-end network services.
  • the network sharding instance can include several network slice subnet instances (NSSIs) and/or several network functions (NF). .
  • a terminal device such as a user equipment (UE) accesses a network slice.
  • a terminal device can access only one network slice according to the subscription information. See FIG. 1a.
  • the access and mobility management functions (AMF) included in multiple network slices can be deployed independently, that is, without sharing, or shared deployment.
  • AMF access and mobility management functions
  • a terminal device accesses multiple network slices. For example, in a car networking scenario, an in-vehicle terminal needs to be able to simultaneously access an eMBB network slice and a uRLLC network slice, and access to the eMBB network slice is mainly used.
  • the AMF instance in the network slice instance can be shared with other network slices, or the exclusive AMF instance can be exclusively used.
  • the AMF instances in multiple network slice instances must be shared, that is, multiple network slice instances must provide access services for the terminal devices through the same AMF instance.
  • the technical problem to be solved by the embodiments of the present application is to provide a network slice deployment method and a device thereof.
  • a terminal device accesses multiple network slices simultaneously, it is clear how to deploy multiple network function entities shared by network slices. Therefore, it is convenient to improve the efficiency of network slice management.
  • a first aspect of the embodiments of the present application provides a network slice deployment method, including:
  • the network functional entity required to deploy the first network slice according to the determined deployment mode is the network functional entity required to deploy the first network slice according to the determined deployment mode.
  • the first network slice may be any one of the plurality of coexistence slices, and the method for deploying the network function entity required by the first network slice is determined by the slice coexistence relationship information of the first network slice, and according to the determined Deploying the network function entity in the deployment mode, in a scenario where multiple coexisting slices exist, that is, in a scenario where one terminal device accesses multiple network slices at the same time, it is clear how to deploy network function entities shared by multiple network slices, and then It is convenient to improve the efficiency of network slice management.
  • the network function entity required for the first network slice is a network function entity that needs to be shared by multiple network slices that are accessed by one terminal device at the same time, and may be a mobility management network.
  • the mobility management network element is used to provide access and mobility management services, and the mobility management network element may be an access and mobility management function entity in a 5G system, or may be mobility management in a 4G system.
  • the entity may also be a mobility management network element in a future communication system.
  • the method provided by the first aspect in a scenario in which a terminal device simultaneously accesses multiple network slices, it is clear how to deploy a mobility management network element shared by multiple network slices. It can be understood that the mobility management network element is instantiated, that is, a mobility management instance.
  • the execution body of the method provided by the first aspect is a network slice management function entity, and the network slice management function entity receives the first network slice by using a communication service management function entity or other entity.
  • the slice coexistence relationship information is used to obtain the slice coexistence relationship information of the first network slice, and is deployed according to the determined deployment mode when the network slice management function entity determines the deployment mode of the mobility management network element required for the first network slice.
  • the mobility management network element That is, the network slice management function entity determines the deployment mode of the mobility management network element.
  • the mobility management network element needs to be instantiated, and the network slice management function entity sends a network slice subnet instantiation requirement to the network slice subnet management function entity, and the network slice subnet management function entity receives the When the network slice subnet instantiates the requirement, it sends the network service instantiation requirement to the management and orchestration entity.
  • This process is the process of instantiating an existing network slice.
  • the network slice management function entity searches for the instantiation information (including the instance identifier) of the mobility management network element.
  • the network slice subnet management function entity sends a network slice subnet instantiation requirement, where the network slice subnet instantiation requirement carries the instantiation information of the mobility management network element, and the network slice subnet management function entity receives the network sliced subnet instance
  • the network service instantiation requirement is sent to the management and orchestration entity, and the network service instantiation requirement carries the instantiation information of the mobility management network element, and the management and orchestration entity can search for the mobility according to the instance identifier of the mobility management network element.
  • the management network element does not need to instantiate the virtual resources of the mobility management network element.
  • the first network slice requires the network function entity A, the network function entity B, and the mobility management network element, and the management and orchestration entity performs virtual resource instantiation, instantiates the network function entity A and the network function entity B, and according to the mobility
  • the instance identifier of the management network element searches for the mobility management network element, and then feeds back the network function entity A, the network function entity B, and the instance identifier of the mobility management network element and the virtual network function descriptor to the network slice subnet management function entity, and the network slice
  • the subnet management function entity establishes a network topology between the network function entity A, the network function entity B, and the mobility management network element according to the virtual network function descriptor. That is, there is no need to create a new mobility management network element in the process, which can improve the utilization of the network function entity, and is beneficial to improve the efficiency of network slice management.
  • the execution body of the method provided by the first aspect is a network slice subnet management function entity, and the network slice subnet management function entity receives the first network by using a network slice management function entity.
  • the sliced slice coexistence relationship information is used to obtain the slice coexistence relationship information of the first network slice, and in the case that the network slice subnet management function entity determines the deployment mode of the mobility management network element required by the first network slice, according to the determined The mobility management network element is deployed in the deployment mode. That is, the network slice subnet management function entity determines the deployment mode of the mobility management network element.
  • the mobility management network element needs to be instantiated, and the network slice subnet management function entity sends the network slice subnet instantiation requirement sent by the network slice management function entity to the management and orchestration entity.
  • Network business instantiation requirements This process is the process of instantiating a network slicing subnet.
  • the network slice subnet management function entity searches for the instantiation information (including the instance identifier) of the mobility management network element, and sends the network service instantiation to the management and orchestration entity.
  • the network service instantiation requirement carries the instantiation information of the mobility management network element, and the management and orchestration entity can search for the mobility management network element according to the instance identifier of the mobility management network element, and does not need to perform the virtual resource of the mobility management network element. Instantiation.
  • the first network slice requires the network function entity A, the network function entity B, and the mobility management network element, and the management and orchestration entity performs virtual resource instantiation, instantiates the network function entity A and the network function entity B, and according to the mobility
  • the instance identifier of the management network element searches for the mobility management network element, and then feeds back the network function entity A, the network function entity B, and the instance identifier of the mobility management network element and the virtual network function descriptor to the network slice subnet management function entity, and the network slice
  • the subnet management function entity establishes a network topology between the network function entity A, the network function entity B, and the mobility management network element according to the virtual network function descriptor. That is, there is no need to create a new mobility management network element in the process, which can improve the utilization of the network function entity, and is beneficial to improve the efficiency of network slice management.
  • the foregoing slice coexistence relationship information includes a coexistence network slice type list, where the coexistence network slice type list includes a slice type of a second network slice that is a coexistence slice with the first network slice .
  • the slice types can be divided into eMBB network slices, mMTC network slices, and uRLLC network slices.
  • the slice coexistence relationship information carries a coexistence network slice type list, so as to find out whether there is a network slice instance corresponding to the slice type of the second network slice in the network, and further determines a deployment mode of the mobility management network element required for the first network slice.
  • the foregoing coexistence network slice type list further includes a tenant identifier of the second network slice, where the subscriber of the second network slice is identified, and the coexistence network slice type list includes the second
  • the network slice deployment apparatus may perform a finer-grained lookup in combination with the slice type and the tenant identifier of the second network slice, and search for a network slice instance corresponding to the slice type of the second network slice, and The tenant ID of the network slice instance is the same as the tenant ID in the coexistence network slice type list.
  • the deployment manner of the mobility management network element required for the first network slice is determined by determining whether there is a network slice instance corresponding to the slice type of the second network slice.
  • the network slice deployment device may determine whether the network slice instance corresponding to the slice type of the second network slice exists on the local end, or determine whether there is a network slice instance corresponding to the slice type of the second network slice in the network.
  • the deployment mode of the mobility management network element required to determine the first network slice is shared.
  • the deployment mode of the mobility management network element required to determine the first network slice is newly created.
  • the foregoing slice coexistence relationship information includes a coexistence network slice type list and a coexistence network slice instance list, where the coexistence network slice instance list includes a coexistence slice with the first network slice.
  • the network slice instance identifier corresponding to the second network slice is used to identify the network slice instance corresponding to the second network slice that exists.
  • the slice coexistence relationship information carries a coexistence network slice type list and a coexistence network slice instance list, so as to find whether there is a network slice instance that is available for sharing by the first network slice in the network, thereby determining a mobility management network element required for the first network slice. Deployment method.
  • the coexistence network slice instance list is empty, it can be understood that the first network slice is the first network slice among the multiple coexistence slices, and the network slice
  • the deployment device determines whether there is a coexistence network slice instance according to the coexistence network slice type list.
  • the network slice deployment device can determine whether there is a coexistence network slice instance on the local end, or can determine whether a coexistence network slice instance exists in the network.
  • the coexistence network slice instance can support the first network slice sharing mobility management network element.
  • the deployment mode of the mobility management network element required to determine the first network slice is shared.
  • the deployment mode of the mobility management network element required to determine the first network slice is newly created.
  • the number of the default coexisting network segment instances is one. If the number of coexisting network segment instances is two or more, it is necessary to determine whether the coexisting network slice instances share the mobility management network element. The instance shares the mobility management network element, and the deployment mode of the mobility management network element required for the first network slice is determined to be shared.
  • the network slice deployment device determines whether the at least two network slice instances corresponding to the at least two network slice instance identifiers share the mobility management network element, that is, whether the mobility management network element of the at least two network slice instances is determined For the same one.
  • the at least two network slice instances share the mobility management network element, determine whether the mobility management network element shared by the at least two network slice instances supports the slice type of the first network slice, and supports the first network slice. In the case of the slice type, the deployment mode of the mobility management network element required to determine the first network slice is shared.
  • a failure message carrying the cause of the failure is sent.
  • the network slice deployment device determines whether the mobility management network element of the network slice instance corresponding to the network slice instance identifier supports the slice type of the first network slice, and if the slice type of the first network slice is supported, determines the first The mobility management NEs required for network slicing are deployed in a shared manner.
  • a failure message carrying the failure cause is sent.
  • the communication service management function entity sends a failure message carrying the failure reason, so that the communication service management function entity obtains the failure reason.
  • the network slice deployment device is a network slice subnet management function entity, sending a failure message carrying the failure reason to the network slice management function entity, and the network slice management function entity sends the failure message to the communication service management function entity when receiving the failure message A failure message for the communication service management function entity to obtain the reason for the failure.
  • the network slice deployment apparatus may further obtain a network slice isolation identifier of the first network slice, where the network slice isolation identifier is used to indicate a mobility management network that constitutes the first network slice instance.
  • Other network function instances other than the meta need to be created to create other network function instances.
  • a second aspect of the embodiments of the present application provides a network slice deployment apparatus, where the network slice deployment apparatus has a function of implementing the method provided by the first aspect.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the network slice deployment apparatus includes: a transceiver unit, configured to acquire slice coexistence relationship information of the first network slice, where the slice coexistence relationship information is used to indicate that the first network slice is mutually coexistent sliced And a processing unit, configured to determine, according to the slice coexistence relationship information, a deployment manner of the network function entity required by the first network slice; the processing unit is further configured to deploy the network function entity according to the deployment manner.
  • the network slice deployment apparatus includes: a processor, a transceiver, and a memory, wherein the memory stores a computer program, the computer program includes program instructions, and the processor is configured to invoke the program code to execute the following Operation: the control transceiver obtains the slice coexistence relationship information of the first network slice, where the slice coexistence relationship information is used to indicate information of the second network slice that is mutually coexistent with the first network slice; and determine the first network according to the slice coexistence relationship information The deployment mode of the network function entities required for the slice; deploy the network function entities according to the deployment mode.
  • the principle and the beneficial effects of the device can be referred to the method described in the first aspect and the beneficial effects thereof. Therefore, the implementation of the device can be referred to the implementation of the method, and the repeated description is not repeated.
  • a third aspect of embodiments of the present application provides a computer readable storage medium having instructions stored therein that, when executed on a computer, cause the computer to perform the method of the first aspect described above.
  • a fourth aspect of an embodiment of the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the first aspect described above.
  • FIG. 1a is a diagram showing an example of a manner in which a terminal device accesses a network slice
  • FIG. 1b is an exemplary diagram of another manner in which a terminal device accesses a network slice
  • FIG. 2 is a schematic diagram of a network architecture to which an embodiment of the present application is applied;
  • FIG. 3 is a schematic diagram of a basic architecture of virtual network function management and orchestration shown in FIG. 2;
  • FIG. 4 is a schematic flowchart of a network slice deployment method according to an embodiment of the present application.
  • FIG. 5 is a schematic diagram 1 of an interaction process of a network slice deployment method according to an embodiment of the present application
  • FIG. 6 is a second schematic diagram of an interaction process of a network slice deployment method according to an embodiment of the present disclosure
  • FIG. 7 is a third schematic diagram of an interaction process of a network slice deployment method according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic diagram 4 of an interaction process of a network slice deployment method according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic diagram of a logical structure of a network slice deployment apparatus according to an embodiment of the present application.
  • FIG. 10 is a simplified schematic diagram of a physical structure of a network slice deployment apparatus according to an embodiment of the present application.
  • eMBB scenarios such as virtual reality, augmented reality, etc.
  • mMTC scenarios such as wearable scenarios, smart grids, etc.
  • uRLLC scenarios such as autopilot, telesurgery, industrial control, etc.
  • network slicing emerges as the times require, and it can flexibly build networks with different characteristics based on 5G scenarios and needs.
  • the network slicing technology logically abstracts the network into one or more isolated network slices, each of which contains a series of logical network functions to specifically meet the differentiated requirements of different service types.
  • the network slicing technology abstracts the 5G network physical infrastructure resources into a plurality of independent parallel network slice instances according to the scene requirements. Each network segment instance performs customized tailoring of network functions and management of corresponding network functions according to the needs of the business scenario and the business model.
  • a network slice instance can be thought of as an instantiated 5G network.
  • Such a network structure allows operators to provide the network as a service to users, and can freely combine physical networks according to indicators such as rate, capacity, coverage, delay, reliability, security, and availability to meet different users. Claim.
  • Different network slices can provide different network functions. For example, for a scenario in which a mobile intelligent terminal (such as a mobile phone) communicates, a separate network slice can be used. For example, for the Internet of Vehicles scenario, due to the ultra-low latency requirement, which is mainly used for the autonomous driving service, the processing delay and reliability of the network are relatively high, and independent network slicing can also be used. For example, for the mMTC scenario, because the number of access devices is large, the packets sent by the access device are relatively small, and the network delay requirements are relatively small. Independent network slices can also be used. Different network slices can deploy different network functions because different network slices need to provide different functions and quality requirements. In view of this, the slice type of the network slice can be divided into an eMBB network slice, a mMTC network slice, and a uRLLC network slice.
  • Network slicing A network that is deployed on a physical or virtual infrastructure to support logical isolation of specific network capabilities and network characteristics, including complete access to the access network, transport network, core network, and application server.
  • the entire network of end to end (E2E) is a key technology to meet the requirements of network differentiation of 5G mobile communication technology proposed by the 3rd generation partnership project (3GPP).
  • 3GPP 3rd generation partnership project
  • network characteristics of different network slices are not the same, and network slices are required to be isolated from each other without affecting each other.
  • network slicing of augmented reality (AR) or virtual reality (VR) services requires large bandwidth and low latency
  • network segmentation of Internet of Things (IOT) services requires massive terminal access.
  • the network slice can also be any combination of a terminal device, an access network, a transport network, a core network, and an application server.
  • a network slicing instance is a real-world logical network that meets certain network characteristics or service requirements.
  • a network slice instance may provide one or more network services.
  • a network slice instance can be created by a network slice management system, and a network slice management system may create multiple network slice instances and manage them at the same time.
  • a network slice instance can be created from a network slice template.
  • NST network slice template
  • a complete network slicing instance is capable of providing complete end-to-end network services, and the network slicing instances may be network slicing subnet instances and/or network functions.
  • the network slice subnet instance may not need to provide a complete network service end-to-end.
  • the network slice subnet instance may be a network function component set of the same device vendor in the network slice instance, or may be a collection of network functions divided by domain. For example, the core network network slice subnet instance and the access network network slice subnet instance.
  • a network sliced subnet instance may be shared by multiple network slice instances.
  • a network slice instance may consist of several network slice subnet instances, each network slice subnet instance consisting of several network functions and/or other network slice subnet instances; one network slice instance may be composed of several network slice subnet instances and none The network functions that are divided into network slice subnet instances are directly composed; a network slice instance may also consist of only a few network functions.
  • a network slice subnet template (NSST) is used to create a network slice subnet instance.
  • the network function may include a session management function (SMF), a policy control function (PCF), a user plane function (UPF), and an evolved base station (evolved node B, eNB) or 5G base station (new radio (NR) nodeB, gNB), access and mobility management function (AMF) and network storage function (NRF), and so on.
  • SMF session management function
  • PCF policy control function
  • UPF user plane function
  • NR nodeB new radio (NR) nodeB
  • gNB new radio (NR) nodeB
  • AMF access and mobility management function
  • NRF network storage function
  • the SMF is used to provide session management services
  • the PCF is used to provide policy control services
  • the UPF is used to provide user plane services
  • the AMF is used to provide access and mobility management services
  • eNB or gNB Used to provide wireless access services
  • NRF is used to provide service discovery.
  • Network functions can be implemented by dedicated hardware, by running software on dedicated hardware, or as virtual functions on a common hardware platform. Therefore, from the perspective of implementation, the network function can be divided into a physical network function (PNF) and a virtualised network function (VNF). From the perspective of use, network functions can be divided into dedicated network functions and shared network functions. Specifically, for multiple (sub)network slice instances, different network functions can be used independently. This network function is called exclusive. Network function; can also share the same network function, this network function is called shared network function. The following are collectively referred to as physical network functions and/or virtual network functions as network functions.
  • the network function entity which is a network function instance, is instantiated and can provide network services with functional behaviors and interfaces.
  • the network function entity corresponding to the AMF is an AMF instance.
  • the network function entity and the network function instance are common in the embodiment of the present application.
  • the multiple network slices are referred to as “coexisting slices”, and vice versa.
  • network slice 1 and network slice 2 need to share AMF
  • network slice 1 and network slice 2 are referred to as “coexistence slices”
  • network slice 1 and network slice 2 do not share AMF
  • network slice 1 and network slice 2 are called Is "mutually exclusive slice”.
  • a plurality of network slices that need to share a network function entity are described as a coexistence slice, which does not constitute a limitation on the embodiment of the present application.
  • Other words used to describe the essence of the coexistence slice should fall into the present application. protected range.
  • the mobility management network element is used to provide access and mobility management services, and may be an AMF entity in a 5G network, a mobility management entity (MME) in a 4G network, or a future communication. Mobility management network elements in the network.
  • the embodiment of the present application introduces an AMF entity as an example.
  • the slice coexistence relationship information is a slice coexistence relationship information of a network slice, and is used to indicate information about other network slices that are mutually coexisting slices with the network slice, and the information may include a slice type of other network slices, and the information may include other The network slice instance ID of the network slice and the slice type of other network slices. It should be noted that the word slice coexistence relationship information does not constitute a limitation on the embodiment of the present application, and other words for describing the essence of the slice coexistence relationship information should fall within the protection scope of the present application.
  • the deployment mode can be divided into new creation and sharing.
  • the new configuration instantiates an instance.
  • the sharing uses the existing instances in the system or network.
  • FIG. 2 is a schematic diagram of a network architecture of an embodiment of the present application, where the network architecture includes a communication service management function (CSMF), a network slice management function (NSMF), and a network slice subnet.
  • CSMF communication service management function
  • NSMF network slice management function
  • NFV-MANO network functions virtualisation management and orchestration
  • the CSMF may be referred to as a CSMF entity
  • the NSMF entity may be referred to as an NSMF entity.
  • the operator can provide a network slice instance for the user, thereby providing the user with a specific communication service, such as high-definition video.
  • the user can negotiate with the operator to determine the corresponding communication service requirements, such as the scope of the network service to be covered, the number of users, and the user distribution, mobility requirements, delay requirements, and whether the network slice needs to be isolated from other network slices. and many more.
  • the CSMF is primarily responsible for translating the communication service requirements of the operator and/or third party customers into network slice requirement information including network slice type/slice template identification ID and network slice deployment requirement information (eg network capacity) , the quality of service QoS requirement, etc.; sending the network slice requirement information to the NSMF through an interface with the NSMF; acquiring management data (such as performance, fault data, etc.) of the network slice from the NSMF; generating and running on the network slice instance The management data of the communication service; the subscription requirement of the management data of the network slice management data and/or the communication service received by the operator and/or the third party customer.
  • network slice requirement information including network slice type/slice template identification ID and network slice deployment requirement information (eg network capacity) , the quality of service QoS requirement, etc.
  • network slice requirement information including network slice type/slice template identification ID and network slice deployment requirement information (eg network capacity) , the quality of service QoS requirement, etc.
  • the NSMF is mainly responsible for receiving the network slice requirement information sent by the CSMF; managing the life cycle, performance, and faults of the network slice instance (hereinafter, the life cycle, performance, and fault management are referred to as management); composing the composition of the network slice instance; and decomposing the network slice
  • the demand information is demand information of each network slice subnet instance and/or network function; a network slice subnet instantiation request is sent to each NSSMF. It should be noted that the NSMF is not limited to receiving information from the CSMF as shown in FIG. 2, and may also receive information from other entities or devices.
  • the NSSMF is mainly responsible for receiving the network slice subnet requirements sent by the NSMF; managing the network slice subnet instance; orchestrating the composition of the network slice subnet instance; and decomposing the network slice subnet instance requirements for each network function and/or nested network slice.
  • the requirements of the subnet instance may send nested network slice subnet instantiation requests to other NSSMFs, possibly managing nested network slice subnet instances, and so on.
  • the network function management entity, the network function management, and the NSMF are interchangeable in the embodiment of the present application.
  • the three words are used to describe the entity responsible for receiving the network slice request sent by the CSMF, and does not constitute an embodiment of the present application. Limited. Same as NSSMF, CSMF.
  • NFV-MANO is mainly used for the management and orchestration of virtual network functions. It is responsible for the mapping and association of service network and network functions virtualisation infrastructure (NFVI) resources, and is responsible for the operation support system (OSS) service. Implementation of resource processes, etc.
  • NFV-MANO includes functional modules such as network functions virtualisation orchestration (NFVO), virtualised network function manager (VNFM), and virtualised infrastructure manager (VIM). 3 shows the basic structure of NFV-MANO. In the embodiment of the present application, MANO is used instead of NFV-MANO for convenience of description.
  • NFVO is mainly used to implement lifecycle management of network services (such as deployment/expansion/reduction/downline, etc.), as well as NFVI resource scheduling and policy management.
  • NFVO can decompose the requirements of each VNF according to the network service descriptor (NSD), and implement VNF deployment with VNFM.
  • NSD network service descriptor
  • NSD is used to describe the network topology of the instantiated network service and the required resource information.
  • VNFM is mainly used to implement VNF lifecycle management, such as deployment/expansion/reduction/downline, and other automation capabilities.
  • VNFD virtualised network function descriptor
  • VNF capacity requirements the virtual machine is decomposed. Wait for the requirements of virtual resources, and cooperate with NFVO and VIM to complete the instantiation of VNF.
  • VIM enables management and monitoring of infrastructure layer resources, including computing, storage, and network resources.
  • the NFVI in Figure 3 is a resource pool from the perspective of cloud computing.
  • NFVI mapping to physical infrastructure is a number of geographically dispersed data centers (dates, DCs) that are connected by high-speed communication networks.
  • NFVI needs to convert physical computing/storage/switching resources into virtual compute/storage/swap resource pools through virtualization.
  • NFV-MANO needs to complete the instantiation of network service (NS).
  • the instantiation of network services is mainly applied to NFVI for network slicing or network slicing subnet instantiation.
  • the embodiment of the present application provides a network slice deployment method and a device thereof, which are applicable to a scenario in which a terminal device accesses multiple network slices at the same time, and can conveniently and clearly deploy multiple networks.
  • the required network function entities are sliced, thereby improving the management efficiency of the network slice.
  • FIG. 4 is a schematic flowchart of a method for deploying a network segment according to Embodiment 1 of the present application.
  • the method may include, but is not limited to, the following steps:
  • Step S401 Acquire slice coexistence relationship information of the first network slice, where the slice coexistence relationship information is used to indicate information of the second network slice that is a coexistence slice with the first network slice.
  • the network slice deployment device acquires slice coexistence relationship information of the first network slice.
  • the network slice deployment device may be NSMF or NSSMF. If the network slice deployment device is NSMF, the NSMF receives the slice coexistence relationship information of the first network slice from the CSMF; if the network slice deployment device is the NSSMF, the NSSMF receives the slice coexistence relationship information of the first network slice from the NSMF.
  • the first network slice is a network slice to be instantiated.
  • the slice coexistence relationship information includes a coexistence network slice type list, and is used to indicate a slice type of the second network slice that is a coexistence slice with the first network slice, that is, the coexistence network slice type list includes the second.
  • the slice type of the network slice It can be understood that the first network slice and the second network slice need to access the same AMF, that is, the AMF is the AMF shared by the first network slice and the second network slice.
  • the number of second network slices may be one, possibly two or even more.
  • the coexistence network slice type list may further include a tenant identifier. For example, the tenant identifier corresponding to the first network slice is 1 and the tenant identifiers corresponding to the two second network slices are 2 and 3.
  • the slice coexistence relationship information includes a coexistence network slice type list and a coexistence network slice instance list, and is used to indicate a slice type of the second network slice that is a coexistence slice with the first network slice and an existing one.
  • the coexistence network slice type list is the same as the coexistence network slice type list in the previous mode.
  • the coexistence network slice instance list includes a network slice instance identifier corresponding to the existing second network slice, and is used to indicate a network slice instance corresponding to the second network slice that is already present, and a network slice instance identifier is used to identify a network slice instance.
  • the network slice deployment device may further receive a network slice isolation identifier of the first network slice, and the network slice isolation identifier may be sent together with the slice coexistence relationship information.
  • Step S402 determining, according to the slice coexistence relationship information, a deployment manner of the network function entity required for the first network slice.
  • the network slice deployment device determines, according to the coexistence network slice type list, whether there is a network slice instance corresponding to the slice type of the second network slice, that is, whether the second network exists in the system.
  • the network slice instance corresponding to the slice type of the slice for example, the slice type of the second network slice is B, determines whether there is a network slice instance corresponding to the slice type B in the system.
  • the network slice deployment device determines that the deployment mode of the AMF instance required for the first network slice is shared.
  • the network slice deployment device determines that the deployment mode of the AMF instance required for the first network slice is new.
  • the first network slice may be determined as long as there is a network slice instance corresponding to the slice type of the second network slice.
  • the required AMF instance is deployed in a shared mode.
  • the network slice deployment apparatus determines whether there is a slice type of the second network slice and a network slice instance corresponding to the tenant identity. In the case that there is a slice type of the second network slice and a network slice instance corresponding to the tenant identifier, the deployment mode of the AMF instance required to determine the first network slice is shared. The deployment mode of the AMF instance required for the first network slice is the new one.
  • the network slice deployment device determines the deployment manner of the AMF required for the first network slice in the following three cases.
  • the coexistence network slice instance list is empty, and the network slice deployment device determines whether there is a coexistence network slice instance according to the coexistence network slice type list, that is, whether there is a coexistence network slice instance in the retrieval system. It can be understood that the AMF instance of the coexisting network slice instance can support the first network slice sharing. In the case where there is a coexistence network slice instance, the network slice deployment device determines that the deployment mode of the AMF instance required for the first network slice is shared; in the case where there is no coexistence network slice instance, the network slice deployment device determines the first network slice The required AMF instance is deployed in a new way.
  • the number of the default coexisting network slice instances is one. If the number of the coexisting network slice instances is two or more, the network slice deployment device needs to determine whether the coexisting network slice instances share the AMF instance. In the case that the coexisting network slice instances share the AMF instance, the network slice deployment device determines that the deployment mode of the AMF instance required for the first network slice is shared.
  • the coexistence network slice instance list includes at least two network slice instance identifiers, that is, at least two network slice instances are identified.
  • the network slice deployment device determines whether the at least two network slice instances share the AMF instance, that is, whether the AMF instances of the at least two network slice instances are the same AMF instance. In the case that the at least two network slice instances share the AMF instance, it is determined whether the AMF instance shared by the at least two network slice instances supports the slice type of the first network slice. In the case that the AMF instances shared by the at least two network slice instances support the slice type of the first network slice, the deployment mode of the AMF required for the first network slice may be determined to be shared.
  • the coexistence network slice instance list includes a network slice instance identifier, that is, identifies a network slice instance.
  • the network slice deployment device determines whether the AMF instance of the network slice instance supports the slice type of the first network slice, and if the AMF instance of the network slice instance supports the slice type of the first network slice, determining the first network slice required The way AMF is deployed is shared.
  • a failure message carrying the cause of the failure is sent. If the network slice deployment device is an NSMF, the failure message is sent to the CSMF; if the network slice deployment device is an NSSMF, the failure message is sent to the NSMF, and the NSMF sends the failure message to the CSMF.
  • Step S403 deploying the network function entity according to the deployment mode.
  • the network slice deployment device instantiates the AMF. If the network slice isolation identifier of the first network slice is received, the network slice deployment device simultaneously instantiates other network functions constituting the first network slice.
  • the network slice deployment device uses the existing AMF instance, and the existing AMF instance may be the AMF instance shared by the at least two network slice instances, or The AMF instance of one of the above network slice instances, or the AMF instance of the above-mentioned coexisting network slice instance. If the network slice isolation identifier of the first network slice is received, the network slice deployment device instantiates other network functions that constitute the first network slice. It can be understood that the network slice deployment device uses the existing AMF instance to deploy the AMF instance required for the first network slice without newly creating an AMF instance.
  • the network slice deployment device obtains the slice coexistence relationship information of the first network slice, and determines the deployment mode of the AMF instance required for the first network slice according to the slice coexistence relationship information, thereby determining according to the determination
  • the deployment method deploys the AMF instances required for the first network slice.
  • FIG. 5 is a schematic diagram 1 of an interaction process of a network slice deployment method according to an embodiment of the present disclosure.
  • the method may include, but is not limited to, the following steps:
  • Step S501 The CSMF sends the slice coexistence relationship information of the first network slice to the NSMF, where the slice coexistence relationship information includes a coexistence network slice type list and a coexistence network slice instance list (empty). Accordingly, the NSMF receives the slice coexistence relationship information from the CSMF.
  • the tenant/subscriber of the network slice can perform network slice ordering through the operation interface of the business support system (BSS), that is, input the service requirement on the operation interface of the BSS.
  • BSS business support system
  • the service requirement may include a service type, and may also include a service-level agreement (SLA) requirement, and the SLA is a contract between the network service provider and the customer, and the SLA requirement may include the number of users, bandwidth requirements, and delay. Guarantee demand, etc. Understandably, business needs include business type and SLA requirements.
  • CSMF (or BSS) transforms business requirements, including business type conversion and SLA demand conversion, when receiving business needs.
  • the service type conversion converts the service type in the service requirement into a network slice type, for example, into an eMBB network slice, a uRLLC network slice, a mMTC network slice, and the like.
  • the CSMF may further search for a network slice template identifier (NST ID) corresponding to the network slice type according to the network slice type.
  • NST ID network slice template identifier
  • the SLA demand conversion converts the SLA demand into network slice demand information, which may include the number of users, bandwidth, and delay.
  • the network slice requirement information is used to describe the demand information such as the number of users, bandwidth, and delay required for the network slice.
  • the CSMF After the service demand is converted, the CSMF sends the slice type and network slice requirement information of the first network slice to the NSMF.
  • the network slice requirement information further includes slice coexistence relationship information of the first network slice, that is, the slice coexistence relationship information of the first network slice is sent to the NSMF by using the network slice requirement information.
  • the slice type of the first network slice may be one of an eMBB network slice, a uRLLC network slice, a mMTC network slice, or other types of network types.
  • the CSMF further sends a tenant identifier of the first network slice to the NSMF for identifying the subscriber of the first network slice.
  • the CSMF may send the tenant identity of the first network slice to the NSMF.
  • the CSMF may not need to send the tenant identity of the first network slice to the NSMF.
  • the instance needs to be created.
  • the first network slice of the slice type A and the second network slice of the slice type B and the slice type C are mutually coexisting slices, and the information sent by the CSMF to the NSMF may include the slice of the first network slice.
  • Step S502 the NSMF sends the slice coexistence relationship information of the first network slice to the NSSMF, where the slice coexistence relationship information includes a coexistence network slice type list and a coexistence network slice instance list (empty). Accordingly, the NSSMF receives the slice coexistence relationship information from the NSMF.
  • the NSMF Before sending the slice coexistence relationship information of the first network slice to the NSSMF, the NSMF generates an identifier of the first network slice instance corresponding to the first network slice, and decomposes the network slice requirement information into network slice subnet requirement information.
  • a network slice instance may be composed of multiple network slice subnet instances, and NSMF may decompose the network slice requirement information into multiple network slice subnet requirement information, the number of multiple network slice subnet requirement information and multiple network slice subnets.
  • the number of instances is the same, that is, the network slice requirement information decomposition is performed in a targeted manner.
  • the network slice subnet requirement information is used to describe the required number of users, bandwidth, and delay required for the corresponding network slice subnet.
  • the NSMF separately sends the network slice subnet instantiation requirement to the multiple NSSMFs, and the network slice subnet instantiation requirement includes the slice coexistence relationship information of the first network slice, and the slice coexistence relationship information is step S501.
  • the slice coexistence relationship information is the slice coexistence relationship information.
  • the NSMF also sends the slice type and network slice subnet requirement information of the first network slice to the NSSMF.
  • the slice type of the first network slice may be one of an eMBB network slice, a uRLLC network slice, a mMTC network slice, or other types of network types.
  • the NSMF further sends, to the NSSMF, an identifier of the tenant that further includes the first network slice, the network slice isolation identifier, and the identifier of the first network slice instance.
  • Step S503 The NSSMF determines, according to the slice coexistence relationship information, a deployment mode (new or shared) of the AMF instance required for the first network slice.
  • the NSSMF may allocate a network slice subnet instance identifier (NSSI ID), and determine the deployment mode of the AMF instance required for the first network slice according to the slice coexistence relationship information.
  • NSSI ID network slice subnet instance identifier
  • the NSSMF determines whether the coexistence network slice instance list is empty. If it is empty, the coexistence network slice type list is used to retrieve whether there is a coexistence network slice instance in the system. If not, the case will be introduced in the embodiment shown in FIG. 6. . It can be understood that the AMF instance of the coexisting network slice instance can support the first network slice to share with it. If there is a coexistence network slice instance in the system, the NSSMF determines that the AMF instance required for the first network slice is deployed in a shared mode, that is, an AMF instance that utilizes the coexistence network slice instance.
  • the NSSMF determines that the AMF instance required for the first network slice is deployed in a new mode, that is, an AMF instance is instantiated to support the first network slice and the at least one second network slice at the same time.
  • an AMF instance can be instantiated to support network slice types A, B, and C at the same time.
  • Step S504 If the deployment mode is new, the NSSMF sends a network service instantiation requirement to the MANO, where the network service instantiation requirement includes a network service descriptor identifier and a network service instantiation parameter. Accordingly, MANO receives the network service instantiation requirement from the NSSMF.
  • the NSSMF can instantiate the AMF according to the network slice subnet requirement information to obtain an AMF instance, and the AMF instance can support the first network slice or the coexistence slice with the first network slice. At least one second network slice.
  • the NSSMF sends a network service instantiation requirement to the MANO, and the network service instantiation requirement includes a network service description identifier (NSD ID) and a network service instantiation parameter.
  • NSD ID network service description identifier
  • Steps S504-S508 are procedures for instantiating AMF and other network functions other than AMF.
  • step S505 the MANO instantiates the AMF and other network functions.
  • MANO Upon receiving the network service instantiation requirement, MANO can instantiate AMF and other network functions according to the NSD ID and network service instantiation parameters, and specifically instantiate virtual resources of AMF and other network functions.
  • the network service instance identifier, the multiple virtual network function descriptor identifiers (VNFD IDs), and the virtual network function descriptor identifiers corresponding to the virtual network function descriptor identifiers (VNF instance IDs) may be obtained. .
  • the VNFD is used to describe the network topology that instantiates the virtual network function and the required resource information.
  • Step S506 The MANO sends the network service instantiation information to the NSSMF, where the network service instantiation information includes a network service instance identifier, a virtual network function descriptor identifier, and a virtual network function descriptor identifier corresponding to the virtual network function descriptor identifier. Accordingly, the NSSMF receives the network slice subnet instantiation information from the MANO.
  • the MANO After completing the virtual resource instantiation, the MANO sends the network service instantiation information to the NSSMF, where the network service instantiation information is used to respond to the network service instantiation requirement, including the network service instance identifier, multiple VNFD IDs, and corresponding VNFD IDs.
  • the VNF instance ID The VNF instance ID.
  • Step S507 the NSSMF records the network service instantiation information.
  • the NSSMF records the network service instantiation information, and records all the virtual network function instance identifiers included in the identifier of the network slice subnet instance, that is, records all the virtual network function instance identifiers included in the network slice subnet instance, that is, establishes a network slice subnet.
  • the NSSMF establishes a network topology between each virtual network function instance according to each virtual network function descriptor.
  • Step S508 The NSSMF sends the network slice subnet instantiation information to the NSMF, where the network slice subnet instantiation information includes an identifier of the first network slice instance and an identifier of the network slice subnet instance. Accordingly, the NSMF receives the network slice instantiation information from the NSSMF.
  • the NSSMF Upon receiving the network service instantiation information, the NSSMF sends the network slice subnet instantiation information to the NSMF, where the network slice subnet instantiation information is used to respond to the network slice subnet instantiation requirement, including the first network slice instance. Identification and NSSI ID.
  • the network slice subnet instantiation information further includes a virtual network function type and a virtual network function instance identifier.
  • the network slice subnet instantiation information further includes an AMF type and a virtual network function instance identifier of the AMF type.
  • Step S509 the NSMF records the network slice subnet instantiation information.
  • the NSMF records the network slice subnet instantiation information, records the identifier of the first network slice instance, and records the identifier of the corresponding network slice subnet instance, that is, establishes the first network slice.
  • the correspondence between the instance and its network segment subnet instance is specifically established.
  • the correspondence between the first network slice instance and multiple network slice subnet instances is specifically established.
  • the NSMF also records the virtual network function type and the virtual network function instance identifier included in the network slice subnet instance, so that the NSMF can find the AMF instance according to the coexistence relationship information.
  • Step S510 The NSMF sends network slice instantiation information to the CSMF, where the network slice instantiation information includes a tenant identifier of the first network slice and an identifier of the first network slice instance.
  • the NSMF Upon receiving the network slice subnet instance information, the NSMF sends the network slice instantiation information to the CSMF, where the network slice instantiation information is used to respond to the network slice instantiation requirement, including the tenant identifier of the first network slice and the first network. The ID of the slice instance.
  • the CSMF records the identity of the first network slice instance when receiving the network slice instantiation information.
  • the process of deploying the first network slice in the plurality of coexisting network slices is described.
  • the deployment mode of the AMF instance required for the first network slice is determined according to the slice coexistence relationship information.
  • the subsequent coexistence network slice can directly utilize the AMF instance included in the first network slice instance during deployment.
  • FIG. 6 is a schematic diagram of an interaction process of a network slice deployment method according to an embodiment of the present disclosure. The method may include, but is not limited to, the following steps:
  • Step S601 The CSMF sends the slice coexistence relationship information of the first network slice to the NSMF, where the slice coexistence relationship information includes a coexistence network slice type list and a coexistence network slice instance list (not null). Accordingly, the NSMF receives the slice coexistence relationship information from the CSMF.
  • Step S601 is different from step S501 in that the first network slice in step S501 is the first network slice of the plurality of coexisting network slices, and the coexistence network slice instance list is empty; the first network slice in step S601 is multiple. Subsequent network slices of the coexisting network slice, that is, not the first network slice, the coexistence network slice instance list is not empty, and includes a network slice instance corresponding to the existing at least one second network slice coexisting with the first network slice instance And, the slice type of the first network slice in step S601 is different from the slice type of the first network slice in step S501.
  • the coexistence network slice instance list in step S601 includes the network slice instance identifier corresponding to the second network slice that has been deployed in the system. If two network slice instances have been deployed, the coexistence network slice instance list includes the two. The identifier of the network slice instance; if a network slice instance has been deployed, the coexistence network slice instance list includes the identifier of the network slice instance.
  • Step S602 the NSMF sends the slice coexistence relationship information of the first network slice to the NSSMF, where the slice coexistence relationship information includes a coexistence network slice type list and a coexistence network slice instance list (not empty). Accordingly, the NSSMF receives the slice coexistence relationship information from the NSMF.
  • steps S601 and S602 shown in FIG. 6 are different from the steps S501 and S502 shown in FIG. 5, in which the coexistence network slice instance list in FIG. 6 is not empty, and the other identical parts can be referred to FIG.
  • the specific description of the steps S501 and S502 is not described herein.
  • Step S603 the NSSMF determines, according to the slice coexistence relationship information, a deployment mode (new or shared) of the AMF instance required for the first network slice.
  • the NSSMF searches for the network slice instance corresponding to each second network slice according to the coexistence network slice instance list.
  • the coexistence network slice instance list includes the network slice instance identifier 1 and the NSSMF finds the network slice instance 1; for example, the coexistence network slice instance list includes the network slice.
  • the instance identifier is 1 and the network slice instance identifier is 2, and the NSSMF searches for the network slice instance 1 and the network slice instance 2.
  • the coexistence network slice instance list includes at least two network slice instance identifiers, for example, including a network slice instance identifier 1 and a network slice instance identifier 2.
  • the NSSMF determines whether the at least two network slice instances share the AMF instance. For example, the NSSMF determines whether the AMF instance of the network slice instance 1 and the AMF instance of the network slice instance 2 are the same. If the same, the network slice instance 1 and the network may be determined. The slice instance 2 shares the AMF instance; if not the same one, it can be determined that the network slice instance 1 and the network slice instance 2 do not share the AMF instance.
  • the NSSMF determines whether the AMF instance shared by the at least two network slice instances supports the slice type of the first network slice, for example, the slice type of the network slice instance 1 is A, and the network slice instance 2 The slice type is B, and the slice type of the first network slice is C. The NSSMF determines whether the AMF instance shared by the network slice instance 1 and the network slice instance 2 supports the slice type C. If the slice type of the first network slice is supported, the NSSMF determines that the deployment mode of the AMF instance required for the first network slice is shared, that is, the AMF instance shared by the network slice instance 1 and the network slice instance 2 can be directly used. If at least two network slice instances do not share the AMF instance, the NSSMF determines that the AMF instance required for the first network slice is deployed in the new mode.
  • the coexistence network slice instance list includes a network slice instance identifier, for example, including a network slice instance identifier 1.
  • the NSSMF determines whether the AMF instance of the one network slice instance supports the slice type of the first network slice, for example, the slice type of the network slice instance 1 is A, the slice type of the first network slice is B, and the NSSMF determines the AMF instance of the network slice instance 1. Whether to support slice type B. If the slice type of the first network slice is supported, the NSSMF determines that the deployment mode of the AMF instance required for the first network slice is shared, that is, the AMF instance of the network slice instance 1 can be directly used.
  • the NSSMF sends the NSMF to the NSMF.
  • a failure message including the identity of the first network slice instance and the reason for the failure.
  • the NSMF upon receiving the failure message, sends the failure message to the CSMF so that the CSMF knows the reason for the failure.
  • Step S604 If the deployment mode is the shared mode, the NSSMF searches for the instantiation information of the AMF instance, and the instantiation information of the AMF instance includes the virtual network function descriptor identifier corresponding to the AMF and the identifier of the AMF instance.
  • the first network slice can be deployed by using the AMF instance shared by the at least two network snippet instances or the AMF instance of the network sharding instance, and no need to create another AMF instance, which can save resources and improve network function instances. Utilization.
  • the NSSMF directly utilizes the existing AMF instance by searching for the instantiation information of the AMF instance.
  • the instantiation information of the AMF instance includes the VNFD ID corresponding to the AMF and the identifier of the AMF instance.
  • Step S605 The NSSMF sends a network service instantiation requirement to the MANO, where the network service instantiation requirement includes a network service descriptor identifier and an instantiation information of the AMF instance. Accordingly, MANO receives the network service instantiation requirement from the NSSMF.
  • the network service instantiation requirement is used to request MANO to perform virtual resource instantiation of other network functions than AMF.
  • step S606 the MANO instantiates other network functions than the AMF.
  • the MANO After receiving the network service instantiation requirement, the MANO performs virtual resource instantiation on other network functions except AMF.
  • Step S607 The MANO sends network service instantiation information to the NSSMF, where the network service instantiation information includes a network service instance identifier, a virtual network function descriptor identifier, and a virtual network function instance identifier corresponding to the virtual network function descriptor. Accordingly, the NSSMF receives the network slice subnet instantiation information from the MANO.
  • the MANO After completing the virtual resource instantiation, the MANO sends the network service instantiation information to the NSSMF, where the network service instantiation information is used to respond to the network service instantiation requirement, including the network service instance identifier, multiple VNFD IDs, and corresponding VNFD IDs.
  • the VNF instance ID The VNF instance ID.
  • Step S608 the NSSMF records network service instantiation information, where the network service instantiation information includes a network service instance identifier, a virtual network function descriptor identifier, and a virtual network function descriptor identifier corresponding to the virtual network function descriptor identifier.
  • the NSSMF records the network service instantiation information, where the network service instantiation information includes the network service instance identifier, each VNFD ID, and the VNF instance ID corresponding to each VNFD ID.
  • the NSSMF establishes a network topology between each virtual network function instance according to each virtual network function descriptor, that is, establishes a network topology between the AMF instance and other network function instances.
  • step S609 the NSSMF determines whether the AMF instance needs to be modified.
  • the NSSMF determines whether the AMF instance shared by the at least two network slice instances or the AMF instance of a network slice instance needs to be modified.
  • the NSSMF can determine whether the AMF instance needs to be modified according to the performance function of the AMF instance and the performance function of the AMF required for the first network slice.
  • performance functions can include the number of users that can be accommodated, bandwidth and latency, and so on. If the performance function of the AMF instance cannot satisfy the performance function of the AMF required by the first network slice, it may be determined that the AMF instance needs to be modified.
  • the AMF instance of the network slice instance 1 can accommodate 18 users, and the number of accommodating users of the AMF required for the first network slice is 60,000, then the AMF instance deployment using the network slice instance 1 can be determined. In the case of a network slice, the number of accommodating users of the AMF instance needs to be modified to 60,000.
  • Step S610 If the modification is needed, the NSSMF sends a network service modification request to the MANO, where the network service modification request is used to request the MANO to modify the resources of the AMF instance. Accordingly, MANO receives the network service modification request from the NSSMF.
  • the NSSMF sends a network service modification request to the MANO.
  • the MANO modifies the resources of the AMF instance when receiving the network service modification request.
  • step S610a the MANO sends a network service modification response to the NSSMF.
  • the MANO may feed back the network service modification response to the NSSMF to notify the NSSMF that the resources of the AMF instance have been modified in response to the network service modification request.
  • Step S611 The NSSMF sends a configuration modification request to the AMF network element, where the configuration modification request is used to request the AMF network element to modify the configuration of the AMF instance.
  • the NSSMF In addition to sending a network service modification request to the MANO, the NSSMF also sends a configuration modification request to the AMF network element.
  • the AMF network element is the AMF instance, that is, the AMF instance that the first network slice needs to share. After receiving the configuration modification request, the AMF network element modifies the configuration of the AMF instance, so that its performance function can meet the AMF requirement of the first network slice.
  • Step S611a the AMF network element sends a configuration modification response to the NSSMF.
  • the AMF network element feeds back the configuration modification response to the NSSMF in response to the configuration modification of the AMF instance, and responds to the configuration modification request to inform the NSSMF that the configuration of the AMF instance has been modified.
  • Step S612 in the case that the AMF instance completes the modification, the NSSMF sends the network slice subnet instantiation information to the NSMF, where the network slice subnet instantiation information includes the identifier of the first network slice instance and the identifier of the network slice subnet instance. Accordingly, the NSMF receives the network slice subnet instantiation information from the NSSMF.
  • the NSSMF sends the network slice subnet instantiation information to the NSMF in response to the network slice.
  • the network slice subnet instance information includes an identifier of the first network slice instance and an identifier of the network slice subnet instance.
  • the network slice subnet instantiation information further includes a virtual network function type and a virtual network function instance identifier.
  • Step S613 the NSMF records the network slice subnet instantiation information.
  • the NSMF records the identifier of the first network slice instance and records the identifier of the corresponding network slice subnet instance, that is, between the first network slice instance and the network slice subnet instance thereof. Correspondence.
  • the NSMF also records the virtual network function type and the virtual network function instance identifier included in the network slice subnet instance.
  • Step S614 the NSMF sends the network slice instantiation information to the CSMF, where the network slice instantiation information includes the tenant identifier of the first network slice and the identifier of the first network slice instance.
  • the NSMF Upon receiving the network slice subnet instance information, the NSMF sends the network slice instantiation information to the CSMF, where the network slice instantiation information is used to respond to the network slice instantiation requirement, including the tenant identifier of the first network slice and the first network. The ID of the slice instance.
  • the CSMF records the identity of the first network slice instance when receiving the network slice instantiation information.
  • a process of deploying a subsequent network slice in a plurality of coexisting network slices is described.
  • the deployment mode of the AMF required for the first network slice is determined to be shared according to the coexistence relationship information.
  • the existing AMF instance deploys the first network slice to improve the utilization of network functions, thereby improving network slice management efficiency.
  • FIG. 7 is a third schematic diagram of an interaction process of a network slice deployment method according to an embodiment of the present disclosure.
  • the method may include, but is not limited to, the following steps:
  • Step S701 the CSMF sends a coexistence network slice type list of the first network slice to the NSMF. Accordingly, the NSMF receives a list of coexisting network slice types from the CSMF.
  • Step 701 is different from step S601 in that the coexistence relationship information in step S601 includes an empty coexistence network slice instance list, and the coexistence relationship information in step S701 does not include the coexistence network slice instance list.
  • Step S702 the NSMF sends a coexistence network slice type list of the first network slice to the NSSMF. Accordingly, the NSSMF receives a list of coexisting network slice types from the NSMF.
  • Step S703 The NSSMF determines, according to the coexistence network slice type list, a deployment mode (new or shared) of the AMF instance required by the first network slice.
  • the NSSMF determines that the deployment mode of the AMF instance required for the first network slice is shared. For example, if there is a network slice instance corresponding to the slice type B and a network slice instance corresponding to the slice type C, the NSSMF determines that the deployment mode of the AMF instance required for the first network slice is shared.
  • the NSSMF determines that the deployment mode of the AMF instance required for the first network slice is new.
  • Step S704 If the deployment mode is new, the NSSMF instantiates the AMF and other network functions except the AMF.
  • the NSF is required to instantiate the AMF required by the first network slice and other network functions except the AMF. For details, refer to step S504-step 508 in the embodiment shown in FIG. Let me repeat.
  • Step S705 If the deployment mode is sharing, the NSSMF instantiates other network functions except the AMF.
  • the NSSMF searches for the instantiation information of the AMF instance, and instantiates other network functions except the AMF required for the first network slice. For details, refer to step S604 in the embodiment shown in FIG. - Step S612, which will not be described again.
  • the coexistence network slice instance list is not carried, and the NSSMF directly determines the deployment mode of the AMF instance required for the first network slice according to the coexistence network slice type list, which is beneficial to improving the network slice management efficiency.
  • FIG. 8 is a schematic diagram of an interaction process of a network slice deployment method according to an embodiment of the present disclosure. The method may include, but is not limited to, the following steps:
  • Step S801 the CSMF sends the slice coexistence relationship information of the first network slice to the NSMF, where the slice coexistence relationship information includes a coexistence network slice type list and a coexistence network slice instance list. Accordingly, the NSMF receives the slice coexistence relationship information from the CSMF.
  • the coexistence network slice instance list is empty; if the first network slice is a subsequent network slice in multiple coexisting network slices, the coexistence network The slice instance list is not empty. It is assumed that the first network slice in the embodiment shown in FIG. 8 is a subsequent network slice in a plurality of coexisting network slices.
  • Step S802 the NSMF searches for the instantiation information of the AMF instance required by the first network slice according to the slice coexistence relationship information, and the instantiation information of the AMF instance includes the identifier of the AMF instance corresponding to the AMF.
  • the NSMF combines the coexistence network slice type list, the coexistence network slice instance list, and the slice type of the first network slice to find instantiation information of the AMF instance required by the first network slice.
  • the instantiation information of the AMF instance includes the identity of the AMF instance.
  • the NSMF records the identifier of the first network slice instance and the identifier of the corresponding network slice subnet instance, and also records the virtual network function type and the virtual network function instance identifier. Therefore, NSMF can find the AMF instance identifier based on the coexistence relationship information.
  • Step S803 the NSMF sends a network slice subnet instantiation requirement to the NSSMF, where the network slice subnet instantiation requirement includes a slice type of the first network slice, a network slice subnet requirement information, and an identifier of the AMF instance. Accordingly, the NSSMF receives the network slice subnet instantiation requirement from the NSMF.
  • the network slice subnet instantiation requirement further includes a tenant identity of the first network slice, an identifier of the first network slice instance, and a slice isolation flag.
  • Step S804 the NSSMF determines whether the AMF instance supports the slice type of the first network slice.
  • the NSSMF determines whether the AMF instance supports the slice type of the first network slice when receiving the network slice subnet instantiation requirement.
  • Step S805 If the slice type of the first network slice is supported, the NSSMF sends a network service instantiation requirement to the MANO, where the network slice service instantiation requirement includes a network service descriptor, a virtual network function descriptor corresponding to the AMF, and an identifier of the AMF instance. . Accordingly, MANO receives the network service instantiation requirement from the NSSMF.
  • the NSSMF sends a failure message to the NSMF, where the failure message includes the identifier of the first network slice instance and the reason for the failure, and the failure reason is that the AMF instance does not support the slice type of the first network slice. .
  • step S806 MANO instantiates other network functions than AMF.
  • Step S807 the MANO sends the network service instantiation information to the NSSMF, where the network service instantiation information includes a network service instance identifier, a virtual network function descriptor identifier, and a virtual network function instance identifier corresponding to the virtual network function descriptor. Accordingly, the NSSMF receives the network service instantiation information from the MANO.
  • Step S808 The NSSMF records network service instantiation information, where the network service instantiation information includes a network service instance identifier, a virtual network function descriptor identifier, and a virtual network function descriptor identifier corresponding to the virtual network function descriptor identifier.
  • Step S809 the NSSMF determines whether the AMF instance needs to be modified.
  • Step S810 if the modification is needed, the NSSMF sends a network service modification request to the MANO, where the network service modification request is used to request the MANO to modify the resources of the AMF instance.
  • step S810a the MANO sends a network service modification response to the NSSMF.
  • Step S811 The NSSMF sends a configuration modification request to the AMF network element, where the configuration modification request is used to request the AMF network element to modify the configuration of the AMF instance.
  • step S811a the AMF network element sends a configuration modification response to the NSSMF.
  • Step S812 In the case that the AMF instance completes the modification, the NSSMF sends the network slice subnet instantiation information to the NSMF, where the network slice subnet instantiation information includes the identifier of the first network slice instance and the identifier of the network slice subnet instance. Accordingly, the NSMF receives the network slice subnet instantiation information from the NSSMF.
  • the network slice subnet instantiation information further includes a virtual network function type and a virtual network function instance identifier.
  • Step S813 the NSMF records the network slice subnet instantiation information.
  • Step S814 the NSMF sends network slice instantiation information to the CSMF, where the network slice instantiation information includes a tenant identifier of the first network slice and an identifier of the first network slice instance.
  • step S806-step S81 For the specific implementation process of step S806-step S814, refer to the detailed description of step S606-step S614 in the embodiment shown in FIG. 6, and details are not described herein again.
  • the NSMF finds the instantiation information of the AMF instance, and if found, determines that the deployment mode of the AMF instance required for the first network slice is shared, and the NSFMF determines that the AMF instance supports the first In the case of a slice type of a network slice, the first network slice is deployed by using the AMF instance, thereby improving the utilization of the network function, which is beneficial to improving network slice management efficiency.
  • FIG. 9 is a schematic diagram of a logical structure of a network slice deployment apparatus according to an embodiment of the present disclosure.
  • the network slice deployment apparatus 90 may include a transceiver unit 901 and a processing unit 902.
  • the transceiver unit 901 is configured to acquire slice coexistence relationship information of the first network slice, where the slice coexistence relationship information is used to indicate information of the second network slice that is a coexistence slice with the first network slice.
  • the processing unit 902 is configured to determine, according to the slice coexistence relationship information, a deployment manner of a network function entity required by the first network slice.
  • the processing unit 902 is further configured to deploy the network function entity according to the deployment manner.
  • the transceiver unit 901 is configured to perform step S401 in the embodiment shown in FIG. 4, and the processing unit 902 is configured to perform step S402 and step S403 in the embodiment shown in FIG.
  • the network slice deployment device 90 may be the NSMF or NSSMF in the embodiment shown in Figures 5-8.
  • the transceiver unit 901 can be used to communicate with the CSMF and the NSSMF, for example, performing step S501 and step S502 in the embodiment shown in FIG. Step S508 and step S510, step S601, step S602, step S612 and step S614 in the embodiment shown in FIG. 6 are executed, and step S701 and step S702 in the embodiment shown in FIG. 7 are executed to execute the embodiment shown in FIG. Step S801, step S802, step S812, and step S814.
  • the processing unit 902 is configured to perform an operation of controlling the NSMF, for example, performing step S509 in the embodiment shown in FIG.
  • the transceiver unit 901 can be used to communicate with the NSMF, MANO, and AMF network elements, for example, performing step S502 in the embodiment shown in FIG. Step S504, step S506, and step S508, performing step S602, step S605, step S607, step S610, step S610a, step S611, step S611a, and step S612 in the embodiment shown in FIG. 6 to execute the embodiment shown in FIG.
  • step S702, step S802, step S805, step S807, step S810, step S810a, step S811, step S811a and step S812 in the embodiment shown in Fig. 8 are executed.
  • the processing unit 902 is configured to perform an operation of controlling the NSSMF, for example, performing step S503 and step S507 in the embodiment shown in FIG. 5, and performing step S603, step S604, step S608, and step S609 in the embodiment shown in FIG. Step S703, step S704, and step S705 in the embodiment shown in Fig. 7 executes step S804, step S808, and step S809 in the embodiment shown in Fig. 8.
  • step S804 step S809 in the embodiment shown in Fig. 8.
  • FIG. 10 is a simplified schematic diagram showing the structure of a network slice deployment apparatus according to an embodiment of the present application.
  • the network slice deployment apparatus 100 includes a transceiver 1001, a processor 1002, and a memory 1003.
  • the transceiver 1001, the processor 1002, and the memory 1003 may be connected to one another via a bus 1004 or may be connected in other manners.
  • the related functions implemented by the transceiver unit 901 shown in FIG. 9 can be implemented by the transceiver 1001.
  • Related functions implemented by processing unit 902 shown in FIG. 9 may be implemented by one or more processors 1002.
  • the memory 1003 includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read only memory (EPROM), or A compact disc read-only memory (CD-ROM) for storing related instructions and data.
  • RAM random access memory
  • ROM read-only memory
  • EPROM erasable programmable read only memory
  • CD-ROM compact disc read-only memory
  • the transceiver 1001 is configured to transmit data and/or signaling, as well as receive data and/or signaling.
  • the transceiver 1001 is configured to perform step S401 in the embodiment shown in FIG.
  • the transceiver 1001 can be used to communicate with the CSMF and the NSSMF, for example, performing step S501 and step S502 in the embodiment shown in FIG. Step S508 and step S510, step S601, step S602, step S612 and step S614 in the embodiment shown in FIG. 6 are executed, and step S701 and step S702 in the embodiment shown in FIG. 7 are executed to execute the embodiment shown in FIG. Step S801, step S802, step S812, and step S814.
  • the transceiver 1001 can be used to communicate with the NSMF, MANO, and AMF network elements, for example, performing step S502 in the embodiment shown in FIG. Step S504, step S506, and step S508, performing step S602, step S605, step S607, step S610, step S610a, step S611, step S611a, and step S612 in the embodiment shown in FIG. 6 to execute the embodiment shown in FIG.
  • step S702, step S802, step S805, step S807, step S810, step S810a, step S811, step S811a and step S812 in the embodiment shown in Fig. 8 are executed.
  • the processor 1002 may include one or more processors, for example, including one or more central processing units (CPUs).
  • CPUs central processing units
  • the processor 1002 is a CPU
  • the CPU may be a single core CPU, It can be a multi-core CPU.
  • the processor 1002 is configured to perform step S402 and step S403 in the embodiment shown in FIG.
  • the processor 1002 can be used to perform an operation of controlling the NSMF, for example, performing step S509 in the embodiment shown in FIG. In step S613 in the embodiment, step S802 and step S813 in the embodiment shown in FIG. 8 are performed.
  • step S509 in the embodiment shown in FIG.
  • step S802 and step S813 in the embodiment shown in FIG. 8 are performed.
  • the processor 1002 can be used to perform operations for controlling the NSSMF, for example, performing step S503 and step S507 in the embodiment shown in FIG. Step S603, step S604, step S608, and step S609 in the embodiment shown in FIG. 6 are executed, and step S703, step S704, and step S705 in the embodiment shown in FIG. 7 are executed, and step S804 in the embodiment shown in FIG. 8 is executed. Step S808 and step S809.
  • the memory 1003 is for storing program codes and data of the network slice deployment device 100.
  • Figure 10 only shows a simplified design of a network slice deployment device.
  • the network slice deployment device may also include other necessary components, including but not limited to any number of transceivers, processors, controllers, memories, communication units, etc., and all devices that can implement the present application are Within the scope of protection of this application.
  • the embodiment of the present application further provides a network slice deployment system, including the NSMF, NSSMF, CSMF, and NFV-MANO shown in FIG. 2, and the AMF network element in the embodiment shown in FIG. 6 and FIG.
  • the program can be stored in a computer readable storage medium, when the program is executed
  • the flow of the method embodiments as described above may be included.
  • the foregoing storage medium includes various media that can store program codes, such as a ROM or a random access memory RAM, a magnetic disk, or an optical disk.
  • yet another embodiment of the present application provides a computer readable storage medium having instructions stored therein that, when executed on a computer, cause the computer to perform the methods described in the various aspects above.
  • Yet another embodiment of the present application also provides a computer program product comprising instructions that, when executed on a computer, cause the computer to perform the methods described in the various aspects above.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in or transmitted by a computer readable storage medium.
  • the computer instructions may be from a website site, computer, server or data center via a wired (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) Another website site, computer, server, or data center for transmission.
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)) or the like.

Abstract

本申请实施例提供一种网络切片部署方法及其装置，其中方法包括如下步骤：获取第一网络切片的切片共存关系信息，所述切片共存关系信息用于指示与所述第一网络切片互为共存网络切片的第二网络切片的信息；根据所述切片共存关系信息确定所述第一网络切片所需的网络功能实体的部署方式；按照所述部署方式部署所述网络功能实体。采用本申请实施例，在一个终端设备同时接入多个网络切片的场景下，可以清楚如何部署多个网络切片共享的网络功能实体，进而便于提高网络切片管理效率。

Description

网络切片部署方法及其装置
本申请要求于2018年1月12日提交中国国家知识产权局、申请号为201810033638.3、发明名称为“网络切片部署方法及其装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域，具体涉及一种网络切片部署方法及其装置。
背景技术
随着多种多样的通信业务的不断涌现，不同的通信业务对网络性能的需求存在显著的区别，第五代移动通信(the 5th-generation，5G)系统引入了网络切片(network slice)的概念，以应对不同通信业务对网络性能的需求的差异。
网络切片，指在物理或者虚拟的网络基础设施上，根据不同的服务需求定制化不同的逻辑网络。网络切片是为了满足某一类用户或者某些业务所需的网络功能集以及资源的组合，一个网络切片是一个完整的逻辑网络，能够提供通信服务，具有一定网络能力。网络切片可以包括无线接入网(radio access network，RAN)和核心网(core network，CN)。基本的网络切片类型包括增强型移动宽带(enhanced mobile broadband，eMBB)网络切片、海量机器类通信(massive machine type communication，mMTC)网络切片和低时延、高可靠通信(ultra-reliable and low latency communications，uRLLC)网络切片。
网络切片实例(network slice instance，NSI)是一个真实运行的逻辑网络，能够满足一定网络特性或服务需求。一个完整的网络切片实例可以提供完整的端到端的网络服务，网络切片实例的可以包括若干个网络切片子网实例(network slice subnet instance，NSSI)和/或若干个网络功能(network function，NF)。
实际应用中，会存在一个终端设备(例如用户终端(user equipment，UE))接入一个网络切片的场景，一个终端设备根据签约信息同时只接入一个网络切片的方式可参见图1a所示的示例图，此时多个网络切片包含的接入和移动性管理功能(access and mobility management function，AMF)可以独立部署，即不需要共享，也可以共享部署。实际应用中也会存在一个终端设备接入多个网络切片的场景，例如在车联网场景中，一个车载终端需要能同时接入eMBB网络切片和uRLLC网络切片，接入eMBB网络切片主要是使用大宽带的娱乐业务，接入uRLLC网络切片可以进行辅助自动驾驶等业务。一个终端设备同时接入多个网络切片的方式可参见图1b所示的示例图，此时该终端设备同时接入的多个网络切片包含的AMF必须共享。
对于一个终端设备接入一个网络切片的场景，网络切片实例内的AMF实例可以同其他网络切片共享，也可以独享专属AMF实例。对于一个终端设备同时接入多个网络切片的场景，多个网络切片实例内的AMF实例必须为共享，即多个网络切片实例必须通过相同的AMF实例为终端设备提供接入服务。
对于一个终端设备同时接入多个网络切片的场景，如何部署多个网络切片共享的网络功能实体(例如AMF实例)是亟待解决的问题。
发明内容
本申请实施例所要解决的技术问题在于，提供一种网络切片部署方法及其装置，在一个终端设备同时接入多个网络切片的场景下，可以清楚如何部署多个网络切片共享的网络功能实体，进而便于提高网络切片管理效率。
本申请实施例第一方面提供一种网络切片部署方法，包括：
获取第一网络切片的切片共存关系信息，该切片共存关系信息用于指示与第一网络切片互为共存切片的第二网络切片的信息；
根据切片共存关系信息确定第一网络切片所需的网络功能实体的部署方式；
根据确定的部署方式部署第一网络切片所需的网络功能实体。
在第一方面中，第一网络切片可以为多个共存切片中的任意一个，通过第一网络切片的切片共存关系信息确定第一网络切片所需的网络功能实体的部署方式，并按照确定的部署方式部署该网络功能实体，从而在存在多个共存切片的场景中，即在一个终端设备同时接入多个网络切片的场景下，可以清楚如何部署多个网络切片共享的网络功能实体，进而便于提高网络切片管理效率。
结合第一方面，在一种可能的实现方式中，上述第一网络切片所需的网络功能实体是一个终端设备同时接入的多个网络切片需要共享的网络功能实体，可以为移动性管理网元，该移动性管理网元用于提供接入和移动性管理服务，该移动性管理网元可以是5G系统中的接入和移动性管理功能实体，也可以是4G系统中的移动性管理实体，还可以是未来通信系统中的移动性管理网元。按照第一方面提供的方法，在一个终端设备同时接入多个网络切片的场景下，可以清楚如何部署多个网络切片共享的移动性管理网元。可以理解的是，移动性管理网元是实例化得到的，即为移动性管理实例。
结合第一方面，在一种可能的实现方式中，第一方面提供的方法的执行主体为网络切片管理功能实体，网络切片管理功能实体通过从通信业务管理功能实体或其它实体接收第一网络切片的切片共存关系信息来获取第一网络切片的切片共存关系信息，在网络切片管理功能实体确定出第一网络切片所需的移动性管理网元的部署方式的情况下，按照确定的部署方式部署该移动性管理网元。即由网络切片管理功能实体确定移动性管理网元的部署方式。
若部署方式为新建，即需实例化该移动性管理网元，则网络切片管理功能实体向网络切片子网管理功能实体发送网络切片子网实例化需求，网络切片子网管理功能实体在接收到网络切片子网实例化需求时，向管理与编排实体发送网络业务实例化需求。该流程即为现有的实例化网络切片的流程。
若部署方式为共享，即无需新建该移动性管理网元，可使用已存在的移动性管理网元，则网络切片管理功能实体查找移动性管理网元的实例化信息(包括实例标识)，向网络切片子网管理功能实体发送网络切片子网实例化需求，该网络切片子网实例化需求携带移动性管理网元的实例化信息，网络切片子网管理功能实体在接收到网络切片子网实例化需求时，向管理与编排实体发送网络业务实例化需求，该网络业务实例化需求携带移动性管理网元的实例化信息，管理与编排实体可根据移动性管理网元的实例标识查找移动性管理网元，无需进行移动性管理网元的虚拟资源实例化。例如，第一网络切片需要网络功能实体A、网络功能实体B和移动性管理网元，管理与编排实体进行虚拟资源 实例化，实例化出网络功能实体A和网络功能实体B，并根据移动性管理网元的实例标识查找移动性管理网元，然后向网络切片子网管理功能实体反馈网络功能实体A、网络功能实体B和移动性管理网元的实例标识和虚拟网络功能描述符，网络切片子网管理功能实体根据虚拟网络功能描述符建立网络功能实体A、网络功能实体B和移动性管理网元之间的网络拓扑。即该流程中无需新建移动性管理网元，可提高网络功能实体的利用率，有利于提高网络切片管理效率。
结合第一方面，在一种可能的实现方式中，第一方面提供的方法的执行主体为网络切片子网管理功能实体，网络切片子网管理功能实体通过从网络切片管理功能实体接收第一网络切片的切片共存关系信息来获取第一网络切片的切片共存关系信息，在网络切片子网管理功能实体确定出第一网络切片所需的移动性管理网元的部署方式的情况下，按照确定的部署方式部署该移动性管理网元。即由网络切片子网管理功能实体确定移动性管理网元的部署方式。
若部署方式为新建，即需实例化该移动性管理网元，则网络切片子网管理功能实体在接收到网络切片管理功能实体发送的网络切片子网实例化需求时，向管理与编排实体发送网络业务实例化需求。该流程即为现有的实例化网络切片子网的流程。
若部署方式为共享，即无需新建该移动性管理网元，则网络切片子网管理功能实体查找移动性管理网元的实例化信息(包括实例标识)，向管理与编排实体发送网络业务实例化需求，该网络业务实例化需求携带移动性管理网元的实例化信息，管理与编排实体可根据移动性管理网元的实例标识查找移动性管理网元，无需进行移动性管理网元的虚拟资源实例化。例如，第一网络切片需要网络功能实体A、网络功能实体B和移动性管理网元，管理与编排实体进行虚拟资源实例化，实例化出网络功能实体A和网络功能实体B，并根据移动性管理网元的实例标识查找移动性管理网元，然后向网络切片子网管理功能实体反馈网络功能实体A、网络功能实体B和移动性管理网元的实例标识和虚拟网络功能描述符，网络切片子网管理功能实体根据虚拟网络功能描述符建立网络功能实体A、网络功能实体B和移动性管理网元之间的网络拓扑。即该流程中无需新建移动性管理网元，可提高网络功能实体的利用率，有利于提高网络切片管理效率。
结合第一方面，在一种可能的实现方式中，上述切片共存关系信息包括共存网络切片类型列表，该共存网络切片类型列表包括与第一网络切片互为共存切片的第二网络切片的切片类型。切片类型可分为eMBB网络切片、mMTC网络切片和uRLLC网络切片。切片共存关系信息携带共存网络切片类型列表，以便查找网络中是否存在第二网络切片的切片类型对应的网络切片实例，进而确定第一网络切片所需的移动性管理网元的部署方式。
结合第一方面，在一种可能的实现方式中，上述共存网络切片类型列表还包括第二网络切片的租户标识，用于标识第二网络切片的订购者，在共存网络切片类型列表包括第二网络切片的切片类型和租户标识的情况下，网络切片部署装置可结合第二网络切片的切片类型和租户标识进行更细粒度的查找，查找第二网络切片的切片类型对应的网络切片实例，并且该网络切片实例的租户标识与共存网络切片类型列表中的租户标识相同。
结合第一方面，在一种可能的实现方式中，通过判断是否存在第二网络切片的切片类型对应的网络切片实例来确定第一网络切片所需的移动性管理网元的部署方式。网络切片部署装置可判断本端是否存在第二网络切片的切片类型对应的网络切片实例，或可 判断网络中是否存在第二网络切片的切片类型对应的网络切片实例。
在存在第二网络切片的切片类型对应的网络切片实例的情况下，确定第一网络切片所需的移动性管理网元的部署方式为共享。
在不存在第二网络切片的切片类型对应的网络切片实例的情况下，确定第一网络切片所需的移动性管理网元的部署方式为新建。
结合第一方面，在一种可能的实现方式中，上述切片共存关系信息包括共存网络切片类型列表和共存网络切片实例列表，该共存网络切片实例列表包括与第一网络切片互为共存切片的已存在的第二网络切片对应的网络切片实例标识，用于标识已存在的第二网络切片对应的网络切片实例。切片共存关系信息携带共存网络切片类型列表和共存网络切片实例列表，以便查找网络中是否存在可供第一网络切片共享的网络切片实例，进而确定第一网络切片所需的移动性管理网元的部署方式。
结合第一方面，在一种可能的实现方式中，在共存网络切片实例列表为空的情况下，可以理解的是，第一网络切片为多个共存切片中的第一个网络切片，网络切片部署装置根据共存网络切片类型列表确定是否存在共存网络切片实例。网络切片部署装置可判断本端是否存在共存网络切片实例，或可判断网络中是否存在共存网络切片实例。共存网络切片实例可支持第一网络切片共享移动性管理网元。
在存在共存网络切片实例的情况下，确定第一网络切片所需的移动性管理网元的部署方式为共享。
在不存在共存网络切片实例的情况下，确定第一网络切片所需的移动性管理网元的部署方式为新建。
默认共存网络切片实例的数量为一个，若共存网络切片实例的数量为两个或两个以上，则需要判断这几个共存网络切片实例是否共享移动性管理网元，若这几个共存网络切片实例共享移动性管理网元，则确定第一网络切片所需的移动性管理网元的部署方式为共享。
结合第一方面，在一种可能的实现方式中，在共存网络切片实例列表包括至少两个网络切片实例标识的情况下，可以理解的是，第一网络切片不为多个共存切片中的第一个网络切片，网络切片部署装置判断这至少两个网络切片实例标识对应的至少两个网络切片实例是否共享移动性管理网元，即判断这至少两个网络切片实例的移动性管理网元是否为同一个。
在这至少两个网络切片实例共享移动性管理网元的情况下，判断这至少两个网络切片实例共享的移动性管理网元是否支持第一网络切片的切片类型，在支持第一网络切片的切片类型的情况下，确定第一网络切片所需的移动性管理网元的部署方式为共享。
在这至少两个网络切片实例共享的移动性管理网元不支持第一网络切片的切片类型的情况下，发送携带失败原因的失败消息。
结合第一方面，在一种可能的实现方式中，在共存网络切片实例列表包括一个网络切片实例标识的情况下，可以理解的是，第一网络切片不为多个共存切片中的第一个网络切片，网络切片部署装置判断这个网络切片实例标识对应的网络切片实例的移动性管理网元是否支持第一网络切片的切片类型，在支持第一网络切片的切片类型的情况下，确定第一网络切片所需的移动性管理网元的部署方式为共享。
在这个网络切片实例的移动性管理网元不支持第一网络切片的切片类型的情况下， 发送携带失败原因的失败消息。
结合第一方面，在一种可能的实现方式中，若网络切片部署装置为网络切片管理功能实体，则向通信业务管理功能实体发送携带失败原因的失败消息，以便通信业务管理功能实体获取失败原因。若网络切片部署装置为网络切片子网管理功能实体，则向网络切片管理功能实体发送携带失败原因的失败消息，网络切片管理功能实体在接收到该失败消息时，向通信业务管理功能实体发送该失败消息，以便通信业务管理功能实体获取失败原因。
结合第一方面，在一种可能的实现方式中，网络切片部署装置还可获取第一网络切片的网络切片隔离标识，网络切片隔离标识用于指示构成第一网络切片实例的除移动性管理网元之外的其它网络功能实例需要新建，以便新建其它网络功能实例。
本申请实施例第二方面提供一种网络切片部署装置，该网络切片部署装置具有实现第一方面提供方法的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能实现的方式中，该网络切片部署装置包括：收发单元，用于获取第一网络切片的切片共存关系信息，该切片共存关系信息用于指示与第一网络切片互为共存切片的第二网络切片的信息；处理单元，用于根据切片共存关系信息确定第一网络切片所需的网络功能实体的部署方式；处理单元还用于按照部署方式部署网络功能实体。
在一种可能实现的方式中，该网络切片部署装置包括：处理器、收发器和存储器，其中，存储器中存储计算机程序，计算机程序包括程序指令，处理器被配置用于调用程序代码，执行以下操作：控制收发器获取第一网络切片的切片共存关系信息，该切片共存关系信息用于指示与第一网络切片互为共存切片的第二网络切片的信息；根据切片共存关系信息确定第一网络切片所需的网络功能实体的部署方式；按照部署方式部署网络功能实体。
基于同一发明构思，由于该装置解决问题的原理以及有益效果可以参见第一方面所述的方法以及所带来的有益效果，因此该装置的实施可以参见方法的实施，重复之处不再赘述。
本申请实施例第三方面提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
本申请实施例第四方面提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
附图说明
为了更清楚地说明本申请实施例或背景技术中的技术方案，下面将对本申请实施例或背景技术中所需要使用的附图进行说明。
图1a为终端设备接入网络切片的一种方式的示例图；
图1b为终端设备接入网络切片的另一种方式的示例图；
图2为应用本申请实施例的网络架构示意图；
图3为图2所示虚拟网络功能管理与编排的基本架构示意图；
图4为本申请实施例提供的网络切片部署方法的流程示意图；
图5为本申请实施例提供的网络切片部署方法的交互流程示意图一；
图6为本申请实施例提供的网络切片部署方法的交互流程示意图二；
图7为本申请实施例提供的网络切片部署方法的交互流程示意图三；
图8为本申请实施例提供的网络切片部署方法的交互流程示意图四；
图9为本申请实施例提供的网络切片部署装置的逻辑结构示意图；
图10为本申请实施例提供的网络切片部署装置的实体结构简化示意图。
具体实施方式
5G中，多样化的业务需求对网络在速度、性能、安全、可靠性、时延等方面的需求各不相同。例如，eMBB场景(例如虚拟现实，增强现实等场景)，对带宽要求较高，需要xGbps的带宽。再例如，mMTC场景(例如可穿戴场景，智能电网等场景)，需要支持海量的设备接入，例如需要支持数亿或数十亿的设备接入。再例如，uRLLC场景(例如自动驾驶，远程手术，工业控制等场景)，需要支持1ms的超低时延。面对不同的场景、不同的要求以及极致体验的需求，网络切片应运而生，它可以基于5G场景和需求灵活构建不同特征的网络。
网络切片技术是将网络在逻辑上抽象为一个或者多个相互隔离的网络切片，其中每个网络切片包含一系列的逻辑网络功能，针对性地满足不同业务类型的差异化需求。
网络切片技术将5G网络物理基础设施资源根据场景需求抽象为多个相互独立的平行的网络切片实例。每个网络切片实例按照业务场景的需要和业务模型进行网络功能的定制裁剪及相应网络功能的编排管理。一个网络切片实例可以视为一个实例化的5G网络。这样的网络结构允许运营商将网络作为一种服务提供给用户，并可以根据速率、容量、覆盖性、延迟、可靠性、安全性和可用性等指标对实体网络进行自由组合，从而满足不同用户的要求。
不同的网络切片可以提供不同的网络功能。例如，针对移动智能终端(例如手机)进行通信的场景，可以使用独立的网络切片。再例如，针对车联网场景，由于有超低时延要求，主要给自动驾驶业务使用，对网络的处理时延和可靠性有比较高的要求，也可以使用独立的网络切片。再例如，针对mMTC场景，由于接入设备数量较大，但接入设备发送的报文会比较小，对网络时延的要求也比较小，也可以采用独立的网络切片。由于不同的网络切片需要提供的功能和业务质量要求不相同，因此不同的网络切片可以部署不同网络功能。鉴于此，可将网络切片的切片类型分为eMBB网络切片、mMTC网络切片和uRLLC网络切片。
下面将对本申请实施例涉及的术语或名称进行介绍：
网络切片：部署在物理或者虚拟的基础设施上的，用于支持特定网络能力与网络特性的逻辑隔离的网络，可以包括接入网、传输网、核心网和应用服务器在内的完整的端到端(end to end，E2E)的整个网络，是满足第三代合作伙伴计划(3rd generation partnership project，3GPP)提出的5G移动通信技术关于网络差异化需求的关键技术。通常，不同网络切片的网络特征并不相同，且要求网络切片之间相互隔离，互不影响。如增强实现(augmented reality，AR)或虚拟实现(virtual reality，VR)业务的网络切片要求大带宽、低时延；物联网(internet of things，IOT)业务的网络切片要求支持海量终端接入，但带宽小，对时延没要求。网络切片也可以是终端设备、接入网、传输网、核心网和应用服务器的任意组合。
网络切片实例是一个真实运行的逻辑网络，能满足一定网络特性或服务需求。一个网络切片实例可能提供一种或多种网络服务。网络切片实例可以由网络切片管理系统创建，一个网络切片管理系统可能创建多个网络切片实例并同时对它们进行管理。网络切片实例可从网络切片模板创建。
网络切片模板(network slice template，NST)，用于创建网络切片实例。
一个完整的网络切片实例是能够提供完整的端到端的网络服务的，而组成网络切片实例的可以是网络切片子网实例和/或网络功能。其中网络切片子网实例可以不需要提供端到端的完整的网络服务，网络切片子网实例可以是网络切片实例中同一个设备商的网络功能组成集合，也可能是按域划分的网络功能的集合，例如核心网网络切片子网实例、接入网网络切片子网实例。网络切片子网实例可能被多个网络切片实例共享。一个网络切片实例可能由若干网络切片子网实例组成，每个网络切片子网实例由若干网络功能和/或其他网络切片子网实例组成；一个网络切片实例可能由若干网络切片子网实例和没有被划分为网络切片子网实例的网络功能直接组成；一个网络切片实例也可能仅由若干网络功能组成。
网络切片子网模板(network slice subnet template，NSST)，用于创建网络切片子网实例。
网络功能，具有明确定义的各个外部接口以及明确定义的功能性行为。比如在5G网络中，网络功能可以包括会话管理功能(session management function，SMF)，策略控制功能(policy control function，PCF)，用户面功能(user plane function，UPF)，演进型基站(evolved nodeB，eNB)或5G基站(新空口(new radio，NR)nodeB，gNB)，接入和移动性管理功能(access and mobility management function，AMF)和网络存储功能(network repository function，NRF)，等等。其中，SMF用于提供会话管理服务，PCF用于提供策略控制服务，UPF用于提供用户面服务，AMF用于提供接入和移动性管理服务，eNB或gNB(以下以eNB为例进行说明)用于提供无线接入服务，NRF用于提供服务发现。网络功能可以通过专用硬件实现，也可以通过在专用硬件上运行软件实现，也可以在通用的硬件平台上以虚拟功能的形式实现。因此，从实现的角度，可以将网络功能分为物理网络功能(physical network function，PNF)和虚拟网络功能(virtualised network function，VNF)。而从使用的角度，网络功能可以分为专属网络功能和共享网络功能，具体地，对于多个(子)网络切片实例而言，可以独立地使用不同的网络功能，这种网络功能称为专属网络功能；也可以共享同一个网络功能，这种网络功能称为共享网络功能。以下统称物理网络功能和/或虚拟网络功能为网络功能。
网络功能实体，即为网络功能实例，是经过实例化得到的，能够提供网络服务，具有功能性的行为和接口。例如，AMF对应的网络功能实体为AMF实例。本申请实施例中网络功能实体与网络功能实例通用。
为了方便描述，若多个网络切片需要共享网络功能实体(例如AMF实例)，则将这多个网络切片称为“共存切片”，反之称为“互斥切片”。例如，网络切片1和网络切片2需要共享AMF，则将网络切片1和网络切片2称为“共存切片”，网络切片1和网络切片2不共享AMF，则将网络切片1和网络切片2称为“互斥切片”。需要说明的是，本申请实施例将需要共享网络功能实体的多个网络切片描述为共存切片，并不构成对本申请实施例的限定，其它用于描述共存切片本质的词语理应落入本申请的保护范围。
移动性管理网元，用于提供接入和移动性管理服务，可以为5G网络中的AMF实体，也可以为4G网络中的移动性管理实体(mobility management entity，MME)，还可以是未来通信网络中的移动性管理网元。本申请实施例以AMF实体为例进行介绍。
切片共存关系信息，为某个网络切片的切片共存关系信息，用于指示与该网络切片互为共存切片的其它网络切片的信息，该信息可以包括其它网络切片的切片类型，该信息可以包括其它网络切片的网络切片实例标识和其它网络切片的切片类型。需要说明的是，切片共存关系信息这个词并不构成对本申请实施例的限定，其它用于描述切片共存关系信息本质的词语理应落入本申请的保护范围。
部署方式，可分为新建和共享，新建即实例化出一个实例，共享即利用系统或网络中已经存在的实例。
请参见图2，为应用本申请实施例的网络架构示意图，该网络架构包括通信业务管理功能(communication service management function，CSMF)、网络切片管理功能(network slice management function，NSMF)、网络切片子网管理功能(network slice subnet management funct ion，NSSMF)和虚拟网络功能管理与编排(network functions virtualisation management and orchestration，NFV-MANO)。需要说明的是，网络架构所包括的CSMF、NSMF、NSSMF和NFV-MANO的数量并不局限于图2所示，实际应用中，可能包括多个CSMF、多个NSMF、多个NSSMF、多个NFV-MANO。需要说明的是，上述三个管理功能可能用其他名称进行描述，本申请实施例对此不作限定，例如CSMF可称为CSMF实体，NSMF实体可称为NSMF实体等。运营商通过本申请实施例提供的方案，可以为用户提供一个网络切片实例，从而为用户提供特定的通信服务，如高清视频等。
具体的，用户可以跟运营商通过协商确定相应的通信服务需求，例如网络服务需要覆盖的范围、用户的数量以及用户分布、移动性要求、时延要求以及网络切片是否需要与其他网络切片进行隔离等等。
CSMF主要负责将运营商和/或第三方客户的通信服务需求转化为对网络切片需求信息，所述网络切片需求信息包括网络切片类型/切片模板标识ID和网络切片部署需求信息(例如网络的容量、服务质量QoS需求等)；通过和NSMF之间的接口向NSMF发送所述网络切片需求信息；从NSMF获取网络切片的管理数据(例如性能、故障数据等)；生成运行于网络切片实例之上的通信业务的管理数据；接收运营商和/或第三方客户对网络切片管理数据和/或通信业务的管理数据的订阅需求等。
NSMF主要负责接收CSMF发送的网络切片需求信息；对网络切片实例的生命周期、性能、故障等进行管理(以下将生命周期、性能、故障管理简称管理)；编排网络切片实例的组成；分解网络切片需求信息为各网络切片子网实例和/或网络功能的需求信息；向各NSSMF发送网络切片子网实例化请求等。需要说明的是，NSMF不限定于如图2所示从CSMF接收信息，还可以从其它实体或设备接收信息。
NSSMF主要负责接收NSMF发送的网络切片子网需求；对网络切片子网实例进行管理；编排网络切片子网实例的组成；分解网络切片子网实例的需求为各网络功能和/或嵌套网络切片子网实例的需求；可能向其他NSSMF发送嵌套网络切片子网实例化请求，可能管理嵌套网络切片子网实例等。
需要说明的是，网络功能管理实体、网络功能管理和NSMF在本申请实施例中可以互换，三个词均用于描述负责接收CSMF发送的网络切片需求的实体，并不构成对本申请实 施例的限定。同理NSSMF、CSMF。
NFV-MANO主要用于虚拟网络功能的管理和编排，负责业务网络和网络功能虚拟化基础设施(network functions virtualisation infrastructure，NFVI)资源的映射和关联，负责运营支撑系统(Operation support system，OSS)业务资源流程的实施等。NFV-MANO包括网络功能虚拟化调度(network functions virtualisation orchestration，NFVO)、虚拟网络功能管理(virtualised network function manager，VNFM)和虚拟化基础设施管理(virtualised infrastructure manager，VIM)等功能模块，可参见图3所示的NFV-MANO的基本结构示意图。本申请实施例中，为了描述方便，用MANO来代替NFV-MANO。
其中，NFVO主要用于实现网络业务(network service)的生命周期管理(例如部署/扩容/缩容/下线等)，以及NFVI资源编排、策略管理等功能。NFVO可根据网络业务描述符(network service descriptor，NSD)分解出对各VNF的需求，配合VNFM实现VNF的部署。NSD用于描述实例化网络服务的网络拓扑以及需要的资源信息。
VNFM主要用于实现VNF的生命周期管理，例如部署/扩容/缩容/下线等自动化能力；根据虚拟网络功能描述符(virtualised network function descriptor，VNFD)模板及VNF容量需求，分解出对虚拟机等虚拟资源的需求，与NFVO、VIM配合完成VNF的实例化。
VIM实现基础设施层资源(包括计算、存储、网络资源)的管理和监控。
图3中的NFVI，从云计算的角度看，就是一个资源池。NFVI映射到物理基础设施就是多个地理上分散的数据中心(date center，DC)，通过高速通信网连接起来。NFVI需要将物理计算/存储/交换资源通过虚拟化转换为虚拟的计算/存储/交换资源池。
网络切片和网络切片子网要进行实例化部署，需要NFV-MANO完成对网络服务(network service，NS)的实例化，网络服务的实例化主要向NFVI申请网络切片或网络切片子网实例化所需要的虚拟资源。
在图2所示网络架构的基础上，本申请实施例提供一种网络切片部署方法及其装置，适应于一个终端设备同时接入多个网络切片的场景，可以方便、清楚地部署多个网络切片所需的网络功能实体，进而提高网络切片的管理效率。
请参见图4，为本申请实施例一提供的网络切片部署方法的流程示意图，该方法可以包括但不限于如下步骤：
步骤S401，获取第一网络切片的切片共存关系信息，切片共存关系信息用于指示与第一网络切片互为共存切片的第二网络切片的信息。
网络切片部署装置获取第一网络切片的切片共存关系信息。网络切片部署装置可以是NSMF，也可以是NSSMF。若网络切片部署装置为NSMF，则NSMF从CSMF接收第一网络切片的切片共存关系信息；若网络切片部署装置为NSSMF，则NSSMF从NSMF接收第一网络切片的切片共存关系信息。
其中，第一网络切片为待实例化的网络切片。
在一种可能实现的方式中，切片共存关系信息包括共存网络切片类型列表，用于指示与第一网络切片互为共存切片的第二网络切片的切片类型，即共存网络切片类型列表包括第二网络切片的切片类型。可以理解的是，第一网络切片与第二网络切片需接入同一AMF，即该AMF为第一网络切片与第二网络切片共享的AMF。其中，第二网络切片的数 量可能为一个，可能为两个，甚至更多。
例如，第一网络切片的切片类型为A，存在两个第二网络切片，切片类型分别为B和C，则共存网络切片类型列表可以表示Co-existenceSlicetypelists＝(A,B,C)，或表示为Co-existenceSlicetypelists＝(B,C)。共存网络切片类型列表还可包括租户标识，例如第一网络切片对应的租户标识为1，两个第二网络切片对应的租户标识为2和3，则共存网络切片类型列表可以表示Co-existenceSlicetypelists＝((Tenant ID1,A),(tenant ID2,B),(tenant ID3,C))，或表示为Co-existenceSlicetypelists＝((tenant ID2,B),(tenant ID3,C))。可以理解的是，在共存网络切片类型列表不包括租户标识的情况下，例如Co-existenceSlicetypelists＝(A,B,C)或Co-existenceSlicetypelists＝(B,C)表示共存切片的判断在同一个租户内，该租户不会与其他租户共存切片。
在一种可能实现的方式中，切片共存关系信息包括共存网络切片类型列表和共存网络切片实例列表，用于指示与第一网络切片互为共存切片的第二网络切片的切片类型以及已存在的第二网络切片对应的网络切片实例。共存网络切片类型列表与上一种方式中的共存网络切片类型列表相同。
共存网络切片实例列表包括已存在的第二网络切片对应的网络切片实例标识，用于指示已存在的第二网络切片对应的网络切片实例，一个网络切片实例标识用于标识一个网络切片实例。例如共存网络切片实例列表可以表示为Co-existenceNSI lists＝{NSI ID}。若第一网络切片为待实例化的多个共存切片中的第一个网络切片，则共存网络切片实例列表为空，可表示为Co-existenceNSI lists＝{NSI ID}＝NULL；若第一网络切片不为待实例化的多个共存切片中的第一个网络切片，即为第二个网络切片或者第三个网络切片或之后的网络切片，则共存网络切片实例列表不为空，包括已实例化的第二网络切片对应的网络切片实例标识，例如包括网络切片实例标识B，可表示为Co-existenceNSI lists＝{NSI B}或Co-existenceNSI lists＝{NSI-B ID}。
网络切片部署装置还可接收第一网络切片的网络切片隔离标识，网络切片隔离标识可与切片共存关系信息一同发送。网络切片隔离标识，可以表示为Sliceisolationflag或其它名称，用于指示构成第一网络切片实例的除移动性管理网元之外的其它网络功能实例需要新建。若构成第一网络切片实例的除移动性管理网元之外的其它网络功能实例需要新建，可表示为Sliceisolationflag＝1或Sliceisolationflag＝yes。反之，Sliceisolationflag＝0或Sliceisolationflag＝no可用于指示构成第一网络切片实例的除移动性管理网元之外的其它网络功能实例可以共享。
步骤S402，根据切片共存关系信息确定第一网络切片所需的网络功能实体的部署方式。
在切片共存关系信息包括共存网络切片类型列表的情况下，网络切片部署装置根据共存网络切片类型列表判断是否存在第二网络切片的切片类型对应的网络切片实例，即判断系统中是否存在第二网络切片的切片类型对应的网络切片实例，例如第二网络切片的切片类型为B，则判断系统中是否存在切片类型B对应的网络切片实例。在存在第二网络切片的切片类型对应的网络切片实例的情况下，网络切片部署装置确定第一网络切片所需的AMF实例的部署方式为共享。在不存在第二网络切片的切片类型对应的网络切片实例的情况下，网络切片部署装置确定第一网络切片所需的AMF实例的部署方式为新 建。
需要说明的是，在共存网络切片类型列表包括多个第二网络切片的切片类型的情况下，只要存在其中一个第二网络切片的切片类型对应的网络切片实例，便可确定第一网络切片所需的AMF实例的部署方式为共享。
在共存网络切片类型列表还包括第二网络切片的租户标识的情况下，网络切片部署装置判断是否存在第二网络切片的切片类型和租户标识对应的网络切片实例。在存在第二网络切片的切片类型和租户标识对应的网络切片实例的情况下，确定第一网络切片所需的AMF实例的部署方式为共享。在不存在第一网络切片所需的AMF实例的部署方式为共享，确定第一网络切片所需的AMF实例的部署方式为新建。
在切片共存关系信息包括共存网络切片类型列表和共存网络切片实例列表的情况下，网络切片部署装置分以下三种情况确定第一网络切片所需的AMF的部署方式。
情况一，共存网络切片实例列表为空，网络切片部署装置根据共存网络切片类型列表确定是否存在共存网络切片实例，即检索系统中是否存在共存网络切片实例。可以理解的是，共存网络切片实例的AMF实例可支持第一网络切片共享。在存在共存网络切片实例的情况下，网络切片部署装置确定第一网络切片所需的AMF实例的部署方式为共享；在不存在共存网络切片实例的情况下，网络切片部署装置确定第一网络切片所需的AMF实例的部署方式为新建。
需要说明的是，默认共存网络切片实例的数量为一个，在共存网络切片实例的数量为两个或两个以上的情况下，网络切片部署装置需要判断这几个共存网络切片实例是否共享AMF实例，在这几个共存网络切片实例共享AMF实例的情况下，网络切片部署装置确定第一网络切片所需的AMF实例的部署方式为共享。
情况二，共存网络切片实例列表包括至少两个网络切片实例标识，即标识至少两个网络切片实例。网络切片部署装置判断这至少两个网络切片实例是否共享AMF实例，即判断这至少两个网络切片实例的AMF实例是否为同一个AMF实例。在这至少两个网络切片实例共享AMF实例的情况下，判断这至少两个网络切片实例共享的AMF实例是否支持第一网络切片的切片类型。在这至少两个网络切片实例共享的AMF实例支持第一网络切片的切片类型的情况下，可确定第一网络切片所需的AMF的部署方式为共享。
情况三，共存网络切片实例列表包括一个网络切片实例标识，即标识一个网络切片实例。网络切片部署装置判断这个网络切片实例的AMF实例是否支持第一网络切片的切片类型，并在这个网络切片实例的AMF实例支持第一网络切片的切片类型的情况下，确定第一网络切片所需的AMF的部署方式为共享。
针对上述情况二和情况三，在AMF实例不支持第一网络切片的切片类型的情况下，即至少两个网络切片实例所共享的AMF实例不支持第一网络切片的切片类型的情况下或这个网络切片实例的AMF实例不支持第一网络切片的切片类型的情况下，发送携带失败原因的失败消息。若网络切片部署装置为NSMF，则向CSMF发送该失败消息；若网络切片部署装置为NSSMF，则向NSMF发送该失败消息，NSMF再向CSMF发送该失败消息。
步骤S403，按照部署方式部署网络功能实体。
若确定出第一网络切片所需的AMF实例的部署方式为新建，则网络切片部署装置实例化AMF。若接收到第一网络切片的网络切片隔离标识，则网络切片部署装置同时实例化构成第一网络切片的其它网络功能。
若确定出第一网络切片所需的AMF实例的部署方式为共享，则网络切片部署装置使用已存在的AMF实例，已存在的AMF实例可为上述至少两个网络切片实例共享的AMF实例，或上述一个网络切片实例的AMF实例，或上述共存网络切片实例的AMF实例。若接收到第一网络切片的网络切片隔离标识，则网络切片部署装置实例化构成第一网络切片的其它网络功能。可以理解的是，网络切片部署装置利用已存在的AMF实例部署第一网络切片所需的AMF实例，无需再次新建AMF实例。
在图4所示的实施例中，网络切片部署装置通过获取第一网络切片的切片共存关系信息，并根据切片共存关系信息来确定第一网络切片所需的AMF实例的部署方式，从而根据确定的部署方式部署第一网络切片所需的AMF实例。
下面将结合图5-图8对本申请实施例提供的网络切片部署方法的交互流程进行介绍。
请参见图5，为本申请实施例提供的网络切片部署方法的交互流程示意图一，该方法可以包括但不限于如下步骤：
步骤S501，CSMF向NSMF发送第一网络切片的切片共存关系信息，该切片共存关系信息包括共存网络切片类型列表和共存网络切片实例列表(空)。相应地，NSMF从CSMF接收该切片共存关系信息。
在图5所示的实施例中，第一网络切片为待实例化的多个共存切片中的第一个网络切，因此共存网络切片实例列表为空，可表示为Co-existenceNSI lists＝{NSI ID}＝NULL。若第一网络切片实例对应于共存切片实例的第二个或者第三个或之后的网络切片的实例，则共存网络切片实例列表不为空。
网络切片的租户/订购者，例如运营商、第三方客户等，可以通过业务支持系统(business support system，BSS)的操作界面进行网络切片订购，即在BSS的操作界面输入业务需求。该业务需求可以包括业务类型，还可以包括服务等级协议(service-level agreement，SLA)需求，SLA为网络服务供应商和客户间的一份合同，SLA需求可以包括用户数量、带宽需求和时延保障需求等。可以理解的是，业务需求包括业务类型和SLA需求。
CSMF(或BSS)在接收到业务需求的情况下，对业务需求进行转换，具体包括业务类型转换和SLA需求转换。业务类型转换即将业务需求中的业务类型转换为网络切片类型，例如，转换为eMBB网络切片、uRLLC网络切片、mMTC网络切片等。可选地，此时CSMF还可根据网络切片类型查找该网络切片类型对应的网络切片模板标识(NST ID)。SLA需求转换即将SLA需求转换为网络切片需求信息，该网络切片需求信息可以包括用户数量、带宽和时延等需求。换言之，网络切片需求信息用于描述该网络切片所需的用户数量、带宽和时延等需求信息。
在业务需求转换之后，CSMF向NSMF发送第一网络切片的切片类型和网络切片需求信息。
在一种可能的实现方式中，上述网络切片需求信息还包括第一网络切片的切片共存关系信息，即通过上述网络切片需求信息向NSMF发送第一网络切片的切片共存关系信息。
第一网络切片的切片类型可以是eMBB网络切片、uRLLC网络切片、mMTC网络切片中 的一种，也可以是其它类型的网络类型。例如，第一网络切片的切片类型为A，那么可表示为slicetype＝A或用其名称表示。若网络切片实例化需求不携带第一网络切片的切片类型，则可以携带第一网络切片的切片类型对应的网络切片模板标识，通过该网络切片模板标识对第一网络切片的切片类型进行指示。
在一种可能的实现方式中，CSMF还向NSMF发送第一网络切片的租户标识，用于标识第一网络切片的订购者。在共存网络切片类型列表不包括第一网络切片的租户标识的情况下，CSMF可向NSMF发送第一网络切片的租户标识。在共存网络切片类型包括第一网络切片的租户标识的情况下，CSMF可无需向NSMF发送第一网络切片的租户标识。
在一种可能的实现方式中，CSMF还向NSMF发送第一网络切片的网络切片隔离标识，可表示为Sliceisolationflag＝yes，用于指示构成第一网络切片实例的除AMF实例之外的其它网络功能实例需要新建。
综合上述几种实现方式，以切片类型A的第一网络切片与切片类型B、切片类型C的第二网络切片互为共存切片为例，CSMF向NSMF发送的信息可包括第一网络切片的切片类型(slicetype＝A)、共存网络切片类型列表(Co-existenceSlicetypelists＝((Tenant ID1,A),(tenant ID2,B),(tenant ID3,C)))、共存网络切片实例列表(Co-existenceNSI lists＝{NSI ID}、第一网络切片的租户标识(Tenant ID1)、网络切片需求信息和网络切片隔离标识(Sliceisolationflag)。
步骤S502，NSMF向NSSMF发送第一网络切片的切片共存关系信息，该切片共存关系信息包括共存网络切片类型列表和共存网络切片实例列表(空)。相应地，NSSMF从NSMF接收该切片共存关系信息。
NSMF在向NSSMF发送第一网络切片的切片共存关系信息之前，生成第一网络切片对应的第一网络切片实例的标识，并将网络切片需求信息分解为网络切片子网需求信息。
一个网络切片实例可由多个网络切片子网实例组成，那么NSMF可将网络切片需求信息分解为多个网络切片子网需求信息，多个网络切片子网需求信息的数量与多个网络切片子网实例的数量相同，即针对性地进行网络切片需求信息分解。网络切片子网需求信息用于描述对应的网络切片子网所需的用户数量、带宽和时延等需求信息。
NSMF在对网络切片需求信息分解之后，向多个NSSMF分别发送网络切片子网实例化需求，网络切片子网实例化需求包括第一网络切片的切片共存关系信息，切片共存关系信息即为步骤S501中的切片共存关系信息。
在一种可能实现的方式中，NSMF还向NSSMF发送第一网络切片的切片类型和网络切片子网需求信息。
其中，第一网络切片的切片类型可以是eMBB网络切片、uRLLC网络切片、mMTC网络切片中的一种，也可以是其它类型的网络类型。例如，第一网络切片的切片类型为A，那么可表示为slicetype＝A。若网络切片子网实例化需求不携带第一网络切片的切片类型，则可以携带第一网络切片的切片类型对应的网络切片子网模板标识，通过该网络切片子网模板标识对第一网络切片的切片类型进行指示。
在一种可能实现的方式中，NSMF还向NSSMF发送还包括第一网络切片的租户标识、网络切片隔离标识和第一网络切片实例的标识。
举例来说，NSMF向NSSMF发送的信息可包括slicetype＝A、Co-existenceSlicetypelists＝((Tenant ID1,A),(tenant ID2,B),(tenant ID3,C))、 Co-existenceNSI lists＝{NSI ID}、Tenant ID1、网络切片实例标识(NSI ID)、网络切片子网需求信息和网络切片隔离标识(Sliceisolationflag)。
步骤S503，NSSMF根据切片共存关系信息确定第一网络切片所需的AMF实例的部署方式(新建or共享)。
NSSMF可分配网络切片子网实例标识(NSSI ID)，根据切片共存关系信息确定第一网络切片所需的AMF实例的部署方式。
NSSMF判断共存网络切片实例列表是否为空，若为空，则根据共存网络切片类型列表检索系统中是否存在共存网络切片实例，若不为空的情况将在图6所示的实施例中进行介绍。可以理解的是，该共存网络切片实例的AMF实例可以支持第一网络切片与其共享。若系统中存在共存网络切片实例，则NSSMF确定第一网络切片所需的AMF实例的部署方式为共享，即利用共存网络切片实例的AMF实例。若系统中不存在共存网络切片实例，则NSSMF确定第一网络切片所需的AMF实例的部署方式为新建，即实例化出一个AMF实例可以同时支持第一网络切片和至少一个第二网络切片，按照上述举例，实例化出一个AMF实例可以同时支持网络切片类型A、B和C。
步骤S504，若部署方式为新建，则NSSMF向MANO发送网络业务实例化需求，该网络业务实例化需求包括网络业务描述符标识和网络业务实例化参数。相应地，MANO从NSSMF接收该网络业务实例化需求。
若确定出部署方式为新建，则NSSMF可根据网络切片子网需求信息实例化AMF，得到AMF实例，该AMF实例既可以支持第一网络切片，也可以支持与第一网络切片互为共存切片的至少一个第二网络切片。
NSSMF向MANO发送网络业务实例化需求，该网络业务实例化需求包括网络业务描述标识(NSD ID)和网络业务实例化参数。
步骤S504-步骤S508为实例化AMF以及除AMF之外的其它网络功能的过程。
步骤S505，MANO实例化AMF和其它网络功能。
MANO在接收到网络业务实例化需求的情况下，可根据NSD ID和网络业务实例化参数进行AMF和其它网络功能的实例化，具体进行AMF和其它网络功能的虚拟资源实例化。在MANO完成虚拟资源实例化的情况下，可以得到网络业务实例标识、多个虚拟网络功能描述符标识(VNFD ID)和各个虚拟网络功能描述符标识对应的虚拟网络功能实例标识(VNF实例ID)。
其中，VNFD用于描述实例化虚拟网络功能的网络拓扑以及需要的资源信息。
步骤S506，MANO向NSSMF发送网络业务实例化信息，该网络业务实例化信息包括网络业务实例标识、虚拟网络功能描述符标识以及虚拟网络功能描述符标识对应的虚拟网络功能实例标识。相应地，NSSMF从MANO接收该网络切片子网实例化信息。
MANO在完成虚拟资源实例化的情况下，向NSSMF发送网络业务实例化信息，该网络业务实例化信息用于响应网络业务实例化需求，包括网络业务实例标识、多个VNFD ID和各个VNFD ID对应的VNF实例ID。
步骤S507，NSSMF记录网络业务实例化信息。
NSSMF记录网络业务实例化信息，记录网络切片子网实例的标识包括的所有虚拟网络功能实例标识，即记录该网络切片子网实例所包括的所有虚拟网络功能实例标识，也即建立网络切片子网实例与其所包括的虚拟网络功能实例之间的对应关系。
NSSMF根据各个虚拟网络功能描述符建立各个虚拟网络功能实例之间的网络拓扑。
步骤S508，NSSMF向NSMF发送网络切片子网实例化信息，该网络切片子网实例化信息包括第一网络切片实例的标识和网络切片子网实例的标识。相应地，NSMF从NSSMF接收该网络切片实例化信息。
NSSMF在接收到网络业务实例化信息的情况下，向NSMF发送网络切片子网实例化信息，该网络切片子网实例化信息用于响应网络切片子网实例化需求，包括第一网络切片实例的标识和NSSI ID。
该网络切片子网实例化信息还包括虚拟网络功能类型和虚拟网络功能实例标识。例如，该网络切片子网实例化信息还包括AMF类型以及该AMF类型的虚拟网络功能实例标识。
步骤S509，NSMF记录网络切片子网实例化信息。
NSMF在接收网络切片子网实例信息的情况下，记录网络切片子网实例化信息，记录第一网络切片实例的标识，并记录其对应的网络切片子网实例的标识，即建立第一网络切片实例与其网络切片子网实例之间的对应关系，具体建立第一网络切片实例与多个网络切片子网实例之间的对应关系。
NSMF还记录网络切片子网实例所包括的虚拟网络功能类型和虚拟网络功能实例标识，以便NSMF可以根据共存关系信息查找AMF实例。
步骤S510，NSMF向CSMF发送网络切片实例化信息，该网络切片实例化信息包括第一网络切片的租户标识和第一网络切片实例的标识。
NSMF在接收到网络切片子网实例信息的情况下，向CSMF发送网络切片实例化信息，该网络切片实例化信息用于响应网络切片实例化需求，包括第一网络切片的租户标识和第一网络切片实例的标识。
CSMF在接收到该网络切片实例化信息的情况下，记录第一网络切片实例的标识。
图5所示的实施例中，介绍了多个共存网络切片中的第一个网络切片部署的过程，该过程中根据切片共存关系信息确定出第一个网络切片所需的AMF实例的部署方式为新建，以便后续共存网络切片在部署时可以直接利用第一个网络切片实例所包括的AMF实例，有利于提高网络切片管理效率。
请参见图6，为本申请实施例提供的网络切片部署方法的交互流程示意图二，该方法可以包括但不限于如下步骤：
步骤S601，CSMF向NSMF发送第一网络切片的切片共存关系信息，该切片共存关系信息包括共存网络切片类型列表和共存网络切片实例列表(不为空)。相应地，NSMF从CSMF接收该切片共存关系信息。
步骤S601与步骤S501的不同之处在于，步骤S501中的第一网络切片为多个共存网络切片的第一个网络切片，共存网络切片实例列表为空；步骤S601中的第一网络切片为多个共存网络切片的后续网络切片，即不为第一个网络切片，共存网络切片实例列表不为空，包括与第一网络切片实例共存的已存在的至少一个第二网络切片对应的网络切片实例；并且，步骤S601中的第一网络切片的切片类型与步骤S501中的第一网络切片的切片类型不同。
可以理解的是，步骤S601中的共存网络切片实例列表包括系统中已经部署的第二网 络切片对应的网络切片实例标识，若已经部署了两个网络切片实例，则共存网络切片实例列表包括这两个网络切片实例的标识；若已经部署了一个网络切片实例，则共存网络切片实例列表包括这个网络切片实例的标识。
举例来说，网络切片1、2和3互为共存切片，若网络切片1和2已经部署，即存在网络切片实例1和网络切片实例2，则共存网络切片实例列表包括网络切片实例1和网络切片实例2，可表示为Co-existenceNSI_Lists＝{NSI ID1,NSI ID2}。若网络切片1已经部署，即存在网络切片实例1，则共存网络切片实例列表包括网络切片1，可表示为Co-existenceNSI_Lists＝{NSI ID1}。
步骤S602，NSMF向NSSMF发送第一网络切片的切片共存关系信息，该切片共存关系信息包括共存网络切片类型列表和共存网络切片实例列表(不为空)。相应地，NSSMF从NSMF接收该切片共存关系信息。
需要说明的是，图6所示的步骤S601和步骤S602与图5所示的步骤S501和步骤S502，区别在于图6中共存网络切片实例列表不为空，其余相同的部分可参见图5所示的步骤S501和步骤S502的具体描述，在此不再赘述。
步骤S603，NSSMF根据切片共存关系信息确定第一网络切片所需的AMF实例的部署方式(新建or共享)。
NSSMF根据共存网络切片实例列表查找各个第二网络切片对应的网络切片实例，例如共存网络切片实例列表包括网络切片实例标识为1，NSSMF查找网络切片实例1；再例如共存网络切片实例列表包括网络切片实例标识为1和网络切片实例标识为2，NSSMF查找网络切片实例1以及网络切片实例2。
情况一：共存网络切片实例列表包括至少两个网络切片实例标识，例如包括网络切片实例标识1和网络切片实例标识2。
NSSMF判断至少两个网络切片实例是否共享AMF实例，例如NSSMF判断网络切片实例1的AMF实例以及网络切片实例2的AMF实例是否为同一个，若为同一个，则可确定网络切片实例1和网络切片实例2共享AMF实例；若不为同一个，则可确定网络切片实例1和网络切片实例2不共享AMF实例。
若至少两个网络切片实例共享AMF实例，则NSSMF判断至少两个网络切片实例所共享的AMF实例是否支持第一网络切片的切片类型，例如网络切片实例1的切片类型为A，网络切片实例2的切片类型为B，第一网络切片的切片类型为C，NSSMF判断网络切片实例1和网络切片实例2所共享的AMF实例是否支持切片类型C。若支持第一网络切片的切片类型，则NSSMF确定第一网络切片所需的AMF实例的部署方式为共享，即可以直接使用网络切片实例1和网络切片实例2所共享的AMF实例。若至少两个网络切片实例不共享AMF实例，则NSSMF确定第一网络切片所需的AMF实例的部署方式为新建。
情况二：共存网络切片实例列表包括一个网络切片实例标识，例如包括网络切片实例标识1。
NSSMF判断这一个网络切片实例的AMF实例是否支持第一网络切片的切片类型，例如网络切片实例1的切片类型为A，第一网络切片的切片类型为B，NSSMF判断网络切片实例1的AMF实例是否支持切片类型B。若支持第一网络切片的切片类型，则NSSMF确定第一网络切片所需的AMF实例的部署方式为共享，即可以直接使用网络切片实例1的AMF实例。
上述两种情况中，若至少两个网络切片实例所共享的AMF实例不支持第一网络切片的切片类型或一个网络切片实例的AMF实例不支持第一网络切片的切片类型，则NSSMF向NSMF发送失败消息，该失败消息包括第一网络切片实例的标识和失败原因。NSMF在接收到该失败消息的情况下，向CSMF发送该失败消息，以便CSMF获知失败原因。
步骤S604，若部署方式为共享，则NSSMF查找AMF实例的实例化信息，AMF实例的实例化信息包括AMF对应的虚拟网络功能描述符标识和AMF实例的标识。
若部署方式为共享，则可以利用上述至少两个网络切片实例所共享的AMF实例或一个网络切片实例的AMF实例部署第一网络切片，无需再新建一个AMF实例，可以节省资源，提高网络功能实例的利用率。
NSSMF通过查找AMF实例的实例化信息来直接利用现有的AMF实例，该AMF实例的实例化信息包括AMF对应的VNFD ID和AMF实例的标识。
步骤S605，NSSMF向MANO发送网络业务实例化需求，该网络业务实例化需求包括网络业务描述符标识和AMF实例的实例化信息。相应地，MANO从NSSMF接收该网络业务实例化需求。
该网络业务实例化需求用于请求MANO进行除AMF之外的其它网络功能的虚拟资源实例化。
步骤S606，MANO实例化除AMF之外的其它网络功能。
MANO在接收到该网络业务实例化需求的情况下，对除AMF之外的其它网络功能进行虚拟资源实例化。
步骤S607，MANO向NSSMF发送网络业务实例化信息，该网络业务实例化信息包括网络业务实例标识、虚拟网络功能描述符标识以及虚拟网络功能描述符对应的虚拟网络功能实例标识。相应地，NSSMF从MANO接收该网络切片子网实例化信息。
MANO在完成虚拟资源实例化的情况下，向NSSMF发送网络业务实例化信息，该网络业务实例化信息用于响应网络业务实例化需求，包括网络业务实例标识、多个VNFD ID和各个VNFD ID对应的VNF实例ID。
步骤S608，NSSMF记录网络业务实例化信息，该网络业务实例化信息包括网络业务实例标识、虚拟网络功能描述符标识以及虚拟网络功能描述符标识对应的虚拟网络功能实例标识。
NSSMF在接收到网络业务实例化信息的情况下，记录网络业务实例化信息，该网络业务实例化信息包括网络业务实例标识、各个VNFD ID和各个VNFD ID对应的VNF实例ID。
NSSMF根据各个虚拟网络功能描述符建立各个虚拟网络功能实例之间的网络拓扑，即建立AMF实例与其它网络功能实例之间的网络拓扑。
步骤S609，NSSMF判断AMF实例是否需要修改。
NSSMF判断上述至少两个网络切片实例所共享的AMF实例或一个网络切片实例的AMF实例是否需要修改。
NSSMF可根据该AMF实例的性能功能以及第一网络切片所需的AMF的性能功能判断该AMF实例是否需要修改。其中，性能功能可以包括可容纳用户数量、带宽和时延等等。若该AMF实例的性能功能不能满足第一网络切片所需的AMF的性能功能，则可以确定该AMF实例需要修改。
举例来说，网络切片实例1的AMF实例可容纳用户数量为18个，第一网络切片所需的AMF的可容纳用户数量为6万，那么可以确定在使用网络切片实例1的AMF实例部署第一网络切片的情况下，该AMF实例的可容纳用户数量需要修改为6万。
步骤S610，若需要修改，则NSSMF向MANO发送网络业务修改请求，该网络业务修改请求用于请求MANO修改AMF实例的资源。相应地，MANO从NSSMF接收该网络业务修改请求。
在确定该AMF实例需要修改的情况下，NSSMF向MANO发送网络业务修改请求。MANO在接收到该网络业务修改请求的情况下，对该AMF实例的资源进行修改。
步骤S610a，MANO向NSSMF发送网络业务修改响应。
MANO在完成AMF实例的资源修改的情况下，可向NSSMF反馈网络业务修改响应，以响应网络业务修改请求，告知NSSMF该AMF实例的资源已完成修改。
步骤S611，NSSMF向AMF网元发送配置修改请求，该配置修改请求用于请求AMF网元修改AMF实例的配置。
NSSMF除向MANO发送网络业务修改请求之外，还向AMF网元发送配置修改请求。AMF网元即AMF实例，即第一网络切片需共享的AMF实例。AMF网元在接收到该配置修改请求的情况下，对该AMF实例的配置进行修改，使其性能功能可以满足第一网络切片的AMF的需求。
步骤S611a，AMF网元向NSSMF发送配置修改响应。
AMF网元在完成AMF实例的配置修改的情况下，向NSSMF反馈配置修改响应，以响应配置修改请求，告知NSSMF该AMF实例的配置已完成修改。
步骤S612，在AMF实例完成修改的情况下，NSSMF向NSMF发送网络切片子网实例化信息，该网络切片子网实例化信息包括第一网络切片实例的标识和网络切片子网实例的标识。相应地，NSMF从NSSMF接收该网络切片子网实例化信息。
在AMF实例完成修改的情况下，即NSSMF接收到MANO反馈的网络业务修改响应和AMF网元反馈的配置修改响应的情况下，NSSMF向NSMF发送网络切片子网实例化信息，以响应网络切片子网实例化需求。该网络切片子网实例信息包括第一网络切片实例的标识和网络切片子网实例的标识。该网络切片子网实例化信息还包括虚拟网络功能类型和虚拟网络功能实例标识。
步骤S613，NSMF记录网络切片子网实例化信息。
NSMF在接收网络切片子网实例信息的情况下，记录第一网络切片实例的标识，并记录其对应的网络切片子网实例的标识，即建立第一网络切片实例与其网络切片子网实例之间的对应关系。
NSMF还记录网络切片子网实例所包括的虚拟网络功能类型和虚拟网络功能实例标识。
步骤S614，NSMF向CSMF发送网络切片实例化信息，该网络切片实例化信息包括第一网络切片的租户标识和第一网络切片实例的标识。
NSMF在接收到网络切片子网实例信息的情况下，向CSMF发送网络切片实例化信息，该网络切片实例化信息用于响应网络切片实例化需求，包括第一网络切片的租户标识和第一网络切片实例的标识。
CSMF在接收到该网络切片实例化信息的情况下，记录第一网络切片实例的标识。
图6所示的实施例中，介绍了多个共存网络切片中的后续网络切片部署的过程，该过程中根据共存关系信息确定出第一网络切片所需的AMF的部署方式为共享，以利用现有的AMF实例部署第一网络切片，提高网络功能的利用率，进而提高网络切片管理效率。
请参见图7，为本申请实施例提供的网络切片部署方法的交互流程示意图三，该方法可以包括但不限于如下步骤：
步骤S701，CSMF向NSMF发送第一网络切片的共存网络切片类型列表。相应地，NSMF从CSMF接收共存网络切片类型列表。
步骤701与步骤S601的不同之处在于，步骤S601中的共存关系信息包括为空的共存网络切片实例列表，而步骤S701中的共存关系信息不包括共存网络切片实例列表。
步骤S702，NSMF向NSSMF发送第一网络切片的共存网络切片类型列表。相应地，NSSMF从NSMF接收共存网络切片类型列表。
步骤S703，NSSMF根据共存网络切片类型列表确定第一网络切片所需的AMF实例的部署方式(新建or共享)。
NSSMF根据共存网络切片类型列表判断是否存在第二网络切片的切片类型对应的网络切片实例。例如，Co-existenceSlicetypelists＝((Tenant ID1,A),(tenant ID2,B),(tenant ID3,C))，第一网络切片的切片类型为A，那么NSSMF判断是否存在切片类型B对应的网络切片实例，以及是否切片类型C对应的网络切片实例。
若存在第二网络切片的切片类型对应的网络切片实例，则NSSMF确定第一网络切片所需的AMF实例的部署方式为共享。例如存在切片类型B对应的网络切片实例以及切片类型C对应的网络切片实例，则NSSMF确定第一网络切片所需的AMF实例的部署方式为共享。
若不存在第二网络切片的切片类型对应的网络切片实例，则NSSMF确定第一网络切片所需的AMF实例的部署方式为新建。
步骤S704，若部署方式为新建，则NSSMF实例化AMF以及除AMF之外的其它网络功能。
若确定出的部署方式为新建，则NSSMF实例化第一网络切片所需的AMF以及除AMF之外的其它网络功能，具体参见图5所示实施例中的步骤S504-步骤508，在此不再赘述。
步骤S705，若部署方式为共享，则NSSMF实例化除AMF之外的其它网络功能。
若确定出的部署方式为共享，则NSSMF查找AMF实例的实例化信息，并实例化第一网络切片所需的除AMF之外的其它网络功能，具体参见图6所示实施例中的步骤S604-步骤S612，在此不再赘述。
在图7所示的实施例中，不携带共存网络切片实例列表，NSSMF直接根据共存网络切片类型列表确定第一网络切片所需的AMF实例的部署方式，有利于提高网络切片管理效率。
请参见图8，为本申请实施例提供的网络切片部署方法的交互流程示意图四，该方法可以包括但不限于如下步骤：
步骤S801，CSMF向NSMF发送第一网络切片的切片共存关系信息，该切片共存关系信息包括共存网络切片类型列表和共存网络切片实例列表。相应地，NSMF从CSMF接收 该切片共存关系信息。
其中，若第一网络切片为多个共存网络切片中的第一个网络切片，则共存网络切片实例列表为空；若第一网络切片为多个共存网络切片中的后续网络切片，则共存网络切片实例列表不为空。假设图8所示的实施例中的第一网络切片为多个共存网络切片中的后续网络切片。
步骤S802，NSMF根据切片共存关系信息查找第一网络切片所需的AMF实例的实例化信息，AMF实例的实例化信息包括AMF对应的AMF实例的标识。
NSMF结合共存网络切片类型列表、共存网络切片实例列表和第一网络切片的切片类型查找第一网络切片所需的AMF实例的实例化信息。AMF实例的实例化信息包括AMF实例的标识。
由于在图5所示的实施例中的步骤S508，NSMF记录了第一个网络切片实例的标识以及其对应的网络切片子网实例的标识，还记录了虚拟网络功能类型和虚拟网络功能实例标识，因此NSMF可根据共存关系信息查找AMF实例标识。
步骤S803，NSMF向NSSMF发送网络切片子网实例化需求，该网络切片子网实例化需求包括第一网络切片的切片类型、网络切片子网需求信息和AMF实例的标识。相应地，NSSMF从NSMF接收该网络切片子网实例化需求。
其中，该网络切片子网实例化需求还包括虚拟网络功能类型，该虚拟网络功能类型为AMF，即VNF type＝AMF，即指示共享网络功能的类型为AMF。
该网络切片子网实例化需求还包括第一网络切片的租户标识、第一网络切片实例的标识和网络切片隔离标识(Slice isolation flag)。
步骤S804，NSSMF判断AMF实例是否支持第一网络切片的切片类型。
NSSMF在接收到网络切片子网实例化需求的情况下，判断AMF实例是否支持第一网络切片的切片类型。
步骤S805，若支持第一网络切片的切片类型，则NSSMF向MANO发送网络业务实例化需求，该网络切片业务实例化需求包括网络业务描述符、AMF对应的虚拟网络功能描述符和AMF实例的标识。相应地，MANO从NSSMF接收该网络业务实例化需求。
若不支持第一网络切片的切片类型，则NSSMF向NSMF发送失败消息，该失败消息包括第一网络切片实例的标识和失败原因，该失败原因为该AMF实例不支持第一网络切片的切片类型。
步骤S806，MANO实例化除AMF之外的其它网络功能。
步骤S807，MANO向NSSMF发送网络业务实例化信息，该网络业务实例化信息包括网络业务实例标识、虚拟网络功能描述符标识以及虚拟网络功能描述符对应的虚拟网络功能实例标识。相应地，NSSMF从MANO接收该网络业务实例化信息。
步骤S808，NSSMF记录网络业务实例化信息，该网络业务实例化信息包括网络业务实例标识、虚拟网络功能描述符标识以及虚拟网络功能描述符标识对应的虚拟网络功能实例标识。
步骤S809，NSSMF判断AMF实例是否需要修改；
步骤S810，若需要修改，则NSSMF向MANO发送网络业务修改请求，该网络业务修改请求用于请求MANO修改AMF实例的资源。
步骤S810a，MANO向NSSMF发送网络业务修改响应。
步骤S811，NSSMF向AMF网元发送配置修改请求，该配置修改请求用于请求AMF网元修改AMF实例的配置。
步骤S811a，AMF网元向NSSMF发送配置修改响应。
步骤S812，在AMF实例完成修改的情况下，NSSMF向NSMF发送网络切片子网实例化信息，该网络切片子网实例化信息包括第一网络切片实例的标识和网络切片子网实例的标识。相应地，NSMF从NSSMF接收该网络切片子网实例化信息。
该网络切片子网实例化信息还包括虚拟网络功能类型和虚拟网络功能实例标识。
步骤S813，NSMF记录网络切片子网实例化信息。
步骤S814，NSMF向CSMF发送网络切片实例化信息，该网络切片实例化信息包括第一网络切片的租户标识和第一网络切片实例的标识。
步骤S806-步骤S814的具体实现过程可参见图6所示实施例中的步骤S606-步骤S614的具体描述，在此不再赘述。
在图8所示的实施例中，由NSMF查找AMF实例的实例化信息，若查找到，则确定第一网络切片所需的AMF实例的部署方式为共享，由NSSMF在判断出AMF实例支持第一网络切片的切片类型的情况下，使用该AMF实例部署第一网络切片，从而提高网络功能的利用率，有利于提高网络切片管理效率。
上述详细阐述了本申请实施例的方法，下面提供了本申请实施例的装置。
请参见图9，是本申请实施例提供的网络切片部署装置的逻辑结构示意图，该网络切片部署装置90可以包括收发单元901和处理单元902。
收发单元901用于获取第一网络切片的切片共存关系信息，所述切片共存关系信息用于指示与所述第一网络切片互为共存切片的第二网络切片的信息。
处理单元902用于根据所述切片共存关系信息确定所述第一网络切片所需的网络功能实体的部署方式。
处理单元902还用于按照所述部署方式部署所述网络功能实体。
其中，收发单元901用于执行图4所示实施例中的步骤S401，处理单元902用于执行图4所示实施例中的步骤S402和步骤S403。
网络切片部署装置90可以是图5-图8所示实施例中的NSMF或NSSMF。
若该网络切片部署装置90是图5-图8所示实施例中的NSMF，则收发单元901可用于与CSMF和NSSMF进行通信，例如执行图5所示实施例中的步骤S501、步骤S502、步骤S508和步骤S510，执行图6所示实施例中的步骤S601、步骤S602、步骤S612和步骤S614，执行图7所示实施例中的步骤S701和步骤S702，执行图8所示实施例中的步骤S801、步骤S802、步骤S812和步骤S814。处理单元902可用于执行控制NSMF的操作，例如执行图5所示实施例中的步骤S509，执行图6所示实施例中的步骤S613，执行图8所示实施例中的步骤S802和步骤S813。具体可参见图5-图8所示实施例中相应的描述，在此不再赘述。
若该网络切片部署装置90是图5-图8所示实施例中的NSSMF，则收发单元901可用于与NSMF、MANO和AMF网元进行通信，例如执行图5所示实施例中的步骤S502、步骤S504、步骤S506和步骤S508，执行图6所示实施例中的步骤S602、步骤S605、步骤S607、步骤S610、步骤S610a、步骤S611、步骤S611a和步骤S612，执行图7所示实施例中的步骤S702，执行图8所示实施例中的步骤S802、步骤S805、步骤S807、步骤S810、步 骤S810a、步骤S811、步骤S811a和步骤S812。处理单元902可用于执行控制NSSMF的操作，例如执行图5所示实施例中的步骤S503和步骤S507，执行图6所示实施例中的步骤S603、步骤S604、步骤S608和步骤S609，执行图7所示实施例中的步骤S703、步骤S704和步骤S705，执行图8所示实施例中的步骤S804、步骤S808和步骤S809。具体可参见图5-图8所示实施例中相应的描述，在此不再赘述。
请参见图10，是本申请实施例提供的网络切片部署装置的结构简化示意图。该网络切片部署装置100包括收发器1001、处理器1002和存储器1003。收发器1001、处理器1002和存储器1003可以通过总线1004相互连接，也可以通过其它方式相连接。图9所示的收发单元901所实现的相关功能可以由收发器1001来实现。图9所示的处理单元902所实现的相关功能可以通过一个或多个处理器1002来实现。
存储器1003包括但不限于是随机存储记忆体(random access memory，RAM)、只读存储器(read-only memory，ROM)、可擦除可编程只读存储器(erasable programmable read only memory，EPROM)、或便携式只读存储器(compact disc read-only memory，CD-ROM)，该存储器1003用于相关指令及数据。
收发器1001用于发送数据和/或信令，以及接收数据和/或信令。收发器1001用于执行图4所示实施例中的步骤S401。
若该网络切片部署装置100是图5-图8所示实施例中的NSMF，则收发器1001可用于与CSMF和NSSMF进行通信，例如执行图5所示实施例中的步骤S501、步骤S502、步骤S508和步骤S510，执行图6所示实施例中的步骤S601、步骤S602、步骤S612和步骤S614，执行图7所示实施例中的步骤S701和步骤S702，执行图8所示实施例中的步骤S801、步骤S802、步骤S812和步骤S814。
若该网络切片部署装置100是图5-图8所示实施例中的NSSMF，则收发器1001可用于与NSMF、MANO和AMF网元进行通信，例如执行图5所示实施例中的步骤S502、步骤S504、步骤S506和步骤S508，执行图6所示实施例中的步骤S602、步骤S605、步骤S607、步骤S610、步骤S610a、步骤S611、步骤S611a和步骤S612，执行图7所示实施例中的步骤S702，执行图8所示实施例中的步骤S802、步骤S805、步骤S807、步骤S810、步骤S810a、步骤S811、步骤S811a和步骤S812。
处理器1002可以包括是一个或多个处理器，例如包括一个或多个中央处理器(central processing unit，CPU)，在处理器1002是一个CPU的情况下，该CPU可以是单核CPU，也可以是多核CPU。处理器1002用于执行图4所示实施例中的步骤S402和步骤S403。
若该网络切片部署装置100是图5-图8所示实施例中的NSMF，则处理器1002可用于执行控制NSMF的操作，例如执行图5所示实施例中的步骤S509，执行图6所示实施例中的步骤S613，执行图8所示实施例中的步骤S802和步骤S813。具体可参见图5-图8所示实施例中相应的描述，在此不再赘述。
若该网络切片部署装置100是图5-图8所示实施例中的NSSMF，则则处理器1002可用于执行控制NSSMF的操作，例如执行图5所示实施例中的步骤S503和步骤S507，执行图6所示实施例中的步骤S603、步骤S604、步骤S608和步骤S609，执行图7所示实施例中的步骤S703、步骤S704和步骤S705，执行图8所示实施例中的步骤S804、步骤S808和步骤S809。
存储器1003用于存储网络切片部署装置100的程序代码和数据。
关于处理器1002和收发器1001所执行的步骤，具体可参见图5-图8所示实施例的 描述，在此不再赘述。
可以理解的是，图10仅仅示出了网络切片部署装置的简化设计。在实际应用中，网络切片部署装置还可以分别包含必要的其他元件，包含但不限于任意数量的收发器、处理器、控制器、存储器、通信单元等，而所有可以实现本申请的设备都在本申请的保护范围之内。
本申请实施例还提供了一种网络切片部署系统，包括图2所示的NSMF、NSSMF、CSMF和NFV-MANO，还包括图6和图7所示实施例中的AMF网元等。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，该流程可以由计算机程序来指令相关的硬件完成，该程序可存储于计算机可读取存储介质中，该程序在执行时，可包括如上述各方法实施例的流程。而前述的存储介质包括：ROM或随机存储记忆体RAM、磁碟或者光盘等各种可存储程序代码的介质。因此，本申请又一实施例提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
本申请又一实施例还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
本领域普通技术人员可以意识到，结合本申请中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者通过所述计算机可读存储介质进行传输。所述计算机指令可以从一个 网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。

Claims (21)

  1. 一种网络切片部署方法，其特征在于，包括：
    获取第一网络切片的切片共存关系信息，所述切片共存关系信息用于指示与所述第一网络切片互为共存切片的第二网络切片的信息；
    根据所述切片共存关系信息确定所述第一网络切片所需的网络功能实体的部署方式；按照所述部署方式部署所述网络功能实体。
  2. 根据权利要求1所述的方法，其特征在于，所述第一网络切片所需的网络功能实体为移动性管理网元。
  3. 根据权利要求2所述的方法，其特征在于，所述切片共存关系信息包括共存网络切片类型列表，所述共存网络切片类型列表包括所述第二网络切片的切片类型。
  4. 根据权利要求3所述的方法，其特征在于，所述根据所述切片共存关系信息确定所述第一网络切片所需的网络功能实体的部署方式，包括：
    判断是否存在所述第二网络切片的切片类型对应的网络切片实例；
    在存在所述第二网络切片的切片类型对应的网络切片实例的情况下，确定所述第一网络切片所需的移动性管理网元的部署方式为共享；
    在不存在所述第二网络切片的切片类型对应的网络切片实例的情况下，确定所述第一网络切片所需的移动性管理网元的部署方式为新建。
  5. 根据权利要求2所述的方法，其特征在于，所述切片共存关系信息包括共存网络切片类型列表和共存网络切片实例列表，所述共存网络切片类型列表包括所述第二网络切片的切片类型，所述共存网络切片实例列表包括已存在的所述第二网络切片对应的网络切片实例标识。
  6. 根据权利要求5所述的方法，其特征在于，所述根据所述切片共存关系信息确定所述第一网络切片所需的网络功能实体的部署方式，包括：
    在所述共存网络切片实例列表为空的情况下，根据所述共存网络切片类型列表确定是否存在共存网络切片实例；
    在存在所述共存网络切片实例的情况下，确定所述第一网络切片所需的移动性管理实体的部署方式为共享；
    在不存在所述共存网络切片实例的情况下，确定所述第一网络切片所需的移动性管理实体的部署方式为新建。
  7. 根据权利要求5所述的方法，其特征在于，所述根据所述切片共存关系信息确定所述第一网络切片所需的网络功能实体的部署方式，包括：
    在所述共存网络切片实例列表包括至少两个网络切片实例标识的情况下，判断所述至少两个网络切片实例标识对应的至少两个网络切片实例是否共享移动性管理网元；
    在所述至少两个网络切片实例共享移动性管理网元的情况下，判断所述至少两个网络切片实例共享的移动性管理网元是否支持所述第一网络切片的切片类型；
    在支持所述第一网络切片的切片类型的情况下，确定所述第一网络切片所需的移动性管理网元的部署方式为共享。
  8. 根据权利要求5所述的方法，其特征在于，所述根据所述切片共存关系信息确定所述第一网络切片所需的网络功能实体的部署方式，包括：
    在所述共存网络切片实例列表包括一个网络切片实例标识的情况下，判断所述一个网 络切片实例标识对应的网络切片实例的移动性管理网元是否支持所述第一网络切片的切片类型；
    在支持所述第一网络切片的切片类型的情况下，确定所述第一网络切片所需的移动性管理网元的部署方式为共享。
  9. 根据权利要求7所述的方法，其特征在于，所述判断所述至少两个网络切片实例共享的移动性管理网元是否支持所述第一网络切片的切片类型之后，还包括：
    在所述至少两个网络切片实例共享的移动性管理网元不支持所述第一网络切片的切片类型的情况下，发送携带失败原因的失败消息。
  10. 根据权利要求2或5所述的方法，其特征在于，所述共存网络切片类型列表还包括所述第二网络切片的租户标识。
  11. 一种网络切片部署装置，其特征在于，包括处理器和收发器，
    所述收发器，用于获取第一网络切片的切片共存关系信息，所述切片共存关系信息用于指示与所述第一网络切片互为共存切片的第二网络切片的信息；
    所述处理器，用于根据所述切片共存关系信息确定所述第一网络切片所需的网络功能实体的部署方式；
    所述处理器，还用于按照所述部署方式部署所述网络功能实体。
  12. 根据权利要求11所述的装置，其特征在于，所述第一网络切片所需的网络功能实体为移动性管理网元。
  13. 根据权利要求12所述的装置，其特征在于，所述切片共存关系信息包括共存网络切片类型列表，所述共存网络切片类型列表包括所述第二网络切片的切片类型。
  14. 根据权利要求13所述的装置，其特征在于，所述处理器用于根据所述切片共存关系信息确定所述第一网络切片所需的网络功能实体的部署方式时，具体用于判断是否存在所述第二网络切片的切片类型对应的网络切片实例；在存在所述第二网络切片的切片类型对应的网络切片实例的情况下，确定所述第一网络切片所需的移动性管理网元的部署方式为共享；在不存在所述第二网络切片的切片类型对应的网络切片实例的情况下，确定所述第一网络切片所需的移动性管理网元的部署方式为新建。
  15. 根据权利要求12所述的装置，其特征在于，所述切片共存关系信息包括共存网络切片类型列表和共存网络切片实例列表，所述共存网络切片类型列表包括所述第二网络切片的切片类型，所述共存网络切片实例列表包括已存在的所述第二网络切片对应的网络切片实例标识。
  16. 根据权利要求15所述的装置，其特征在于，所述处理器用于根据所述切片共存关系信息确定所述第一网络切片所需的网络功能实体的部署方式时，具体用于在所述共存网络切片实例列表为空的情况下，根据所述共存网络切片类型列表确定是否存在共存网络切片实例；在存在所述共存网络切片实例的情况下，确定所述第一网络切片所需的移动性管理实体的部署方式为共享；在不存在所述共存网络切片实例的情况下，确定所述第一网络切片所需的移动性管理实体的部署方式为新建。
  17. 根据权利要求15所述的装置，其特征在于，所述处理器用于根据所述切片共存关系信息确定所述第一网络切片所需的网络功能实体的部署方式时，具体用于在所述共存网络切片实例列表包括至少两个网络切片实例标识的情况下，判断所述至少两个网络切片实例标识对应的至少两个网络切片实例是否共享移动性管理网元；在所述至少两个网络切片实例共享移动性管理网元的情况下，判断所述至少两个网络切片实例共享的移动 性管理网元是否支持所述第一网络切片的切片类型；在支持所述第一网络切片的切片类型的情况下，确定所述第一网络切片所需的移动性管理网元的部署方式为共享。
  18. 根据权利要求15所述的装置，其特征在于，所述处理器用于根据所述切片共存关系信息确定所述第一网络切片所需的网络功能实体的部署方式时，在所述共存网络切片实例列表包括一个网络切片实例标识的情况下，判断所述一个网络切片实例标识对应的网络切片实例的移动性管理网元是否支持所述第一网络切片的切片类型；在支持所述第一网络切片的切片类型的情况下，确定所述第一网络切片所需的移动性管理网元的部署方式为共享。
  19. 根据权利要求17所述的装置，其特征在于，所述处理器用于判断所述至少两个网络切片实例共享的移动性管理网元是否支持所述第一网络切片的切片类型之后，还用于在所述至少两个网络切片实例共享的移动性管理网元不支持所述第一网络切片的切片类型的情况下，发送携带失败原因的失败消息。
  20. 根据权利要求12或15所述的装置，其特征在于，所述共存网络切片类型列表还包括所述第二网络切片的租户标识。
  21. 一种计算机可读存储介质，其特征在于，所述计算机存储介质存储有计算机程序，所述计算机程序包括程序指令，所述程序指令当被处理器执行时使所述处理器执行如权利要求1-10任一项所述的方法。
PCT/CN2019/071540 2018-01-12 2019-01-14 网络切片部署方法及其装置 WO2019137516A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP19738338.3A EP3735043B1 (en) 2018-01-12 2019-01-14 Network slice deployment method and apparatus
US16/924,487 US11303526B2 (en) 2018-01-12 2020-07-09 Network slice deployment method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810033638.3 2018-01-12
CN201810033638.3A CN110034944B (zh) 2018-01-12 2018-01-12 网络切片部署方法及其装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/924,487 Continuation US11303526B2 (en) 2018-01-12 2020-07-09 Network slice deployment method and apparatus

Publications (1)

Publication Number Publication Date
WO2019137516A1 true WO2019137516A1 (zh) 2019-07-18

Family

ID=67219228

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/071540 WO2019137516A1 (zh) 2018-01-12 2019-01-14 网络切片部署方法及其装置

Country Status (4)

Country Link
US (1) US11303526B2 (zh)
EP (1) EP3735043B1 (zh)
CN (1) CN110034944B (zh)
WO (1) WO2019137516A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112492629A (zh) * 2020-12-15 2021-03-12 中国联合网络通信集团有限公司 网络切片部署方法、切片管理平台及网络侧设备

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110048872A (zh) * 2018-01-16 2019-07-23 中兴通讯股份有限公司 一种网络告警方法、装置、系统及终端
WO2021089172A1 (en) * 2019-11-08 2021-05-14 Telefonaktiebolaget Lm Ericsson (Publ) Code activation management method for network slicing solutions, and corresponding entity, server and computer program
CN116097760A (zh) 2020-08-03 2023-05-09 上海诺基亚贝尔股份有限公司 用于e2e网络切片的cn-nss域中的细粒度隔离的方法和装置
CN114079909A (zh) * 2020-08-14 2022-02-22 中国移动通信有限公司研究院 一种网络切片信息处理方法、装置及网络设备
CN113490279B (zh) * 2021-06-18 2024-02-06 北京邮电大学 一种网络切片配置方法及装置
CN114158078B (zh) * 2021-12-15 2023-06-16 中国联合网络通信集团有限公司 网络切片管理方法、装置及计算机可读存储介质

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106982458A (zh) * 2017-03-09 2017-07-25 华为技术有限公司 一种网络切片的选择方法及装置

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10129108B2 (en) * 2015-11-13 2018-11-13 Huawei Technologies Co., Ltd. System and methods for network management and orchestration for network slicing
WO2017096606A1 (zh) 2015-12-11 2017-06-15 华为技术有限公司 资源分配的方法和切片分配单元
CN106936619B (zh) * 2015-12-31 2020-10-09 华为技术有限公司 部署网络服务的方法和装置
WO2017175715A1 (ja) * 2016-04-05 2017-10-12 シャープ株式会社 端末装置、基地局装置、ＭＭＥ（Ｍｏｂｉｌｉｔｙ Ｍａｎａｇｅｍｅｎｔ Ｅｎｔｉｔｙ）及び通信制御方法
US10142994B2 (en) * 2016-04-18 2018-11-27 Electronics And Telecommunications Research Institute Communication method and apparatus using network slicing
CN112165424B (zh) * 2016-04-29 2021-07-13 华为技术有限公司 一种业务部署方法、装置以及网元
CN109845303B (zh) * 2016-09-30 2021-02-12 华为技术有限公司 网络切片的管理方法及管理单元
CN106549806B (zh) * 2016-10-26 2019-06-18 清华大学 一种网络切片管理器及其管理方法
KR20190082897A (ko) * 2016-11-18 2019-07-10 엘지전자 주식회사 무선 통신 시스템에서의 네트워크 노드 선택 방법 및 이를 위한 장치
JP6737729B2 (ja) * 2017-03-22 2020-08-12 株式会社Ｎｔｔドコモ 情報通知方法及び移動通信システム
CN110959276A (zh) * 2017-06-13 2020-04-03 诺基亚技术有限公司 通过以太网传送非接入层消息
WO2019096586A1 (en) * 2017-11-20 2019-05-23 Telefonaktiebolaget Lm Ericsson (Publ) Protection of traffic between network functions

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106982458A (zh) * 2017-03-09 2017-07-25 华为技术有限公司 一种网络切片的选择方法及装置

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
MEDIATEK INC.: "On co-existence rules for network slices", SA WG2 MEETING #124 S 2-178847, 1 December 2017 (2017-12-01), XP051379922 *
NOKIA: "TS 23.501 OI:4f Coexistence and isolation among network slices", 3GPP TSG SA WG2 MEETING #124 S 2-178541, 1 December 2017 (2017-12-01), XP051379553 *
SAMSUNG; INTERDIGITAL: "TS 23.501: Slice coexistence - isolated slices", SA WG2 MEETING #122 S 2-174649, 30 June 2017 (2017-06-30), XP051303492 *
See also references of EP3735043A4

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112492629A (zh) * 2020-12-15 2021-03-12 中国联合网络通信集团有限公司 网络切片部署方法、切片管理平台及网络侧设备
CN112492629B (zh) * 2020-12-15 2023-12-22 中国联合网络通信集团有限公司 网络切片部署方法、切片管理平台及网络侧设备

Also Published As

Publication number Publication date
EP3735043A1 (en) 2020-11-04
US20200344126A1 (en) 2020-10-29
EP3735043A4 (en) 2021-03-10
EP3735043B1 (en) 2024-03-06
CN110034944A (zh) 2019-07-19
CN110034944B (zh) 2022-09-23
US11303526B2 (en) 2022-04-12

Similar Documents

Publication Publication Date Title
WO2019137516A1 (zh) 网络切片部署方法及其装置
JP7012836B2 (ja) ネットワークスライス管理方法及び装置
US11036536B2 (en) Method, apparatus, and system for deploying virtualized network function using network edge computing
JP6798667B2 (ja) 動的仮想化ネットワーク機能記述子管理のためのシステムおよび方法
US11051183B2 (en) Service provision steps using slices and associated definitions
CN109952796B (zh) 可共享切片实例的创建及修改
US10824454B2 (en) 5G dynamic slice and network identity instantiation, termination, and access management system and method
EP2922238B1 (en) Resource allocation method
WO2016029821A1 (zh) 一种虚拟网络实例的创建方法以及设备
US11646939B2 (en) Network function NF management method and NF management device
US20170373931A1 (en) Method for updating network service descriptor nsd and apparatus
WO2020186911A1 (zh) 一种容器化虚拟网络功能vnf的资源管理方法及装置
CN107710196B (zh) 一种管理资源对象的方法和系统
CN109600769B (zh) 通信方法及装置
WO2019091439A1 (zh) 网络切片生成方法、装置及终端
WO2019056954A1 (zh) 管理网络切片的方法和装置
US20220350637A1 (en) Virtual machine deployment method and related apparatus
CN114301914B (zh) 一种云边协同方法、装置及存储介质
EP3712768B1 (en) Management of services in an edge computing system
CN112087311B (zh) 一种虚拟网络功能vnf部署方法及装置
WO2018120222A1 (zh) 一种管理vnffg的方法、装置和系统
US20230336482A1 (en) Overcoming limitations of a virtual private cloud (vpc) implemented on a public cloud in a cloud-native fifth generation (5g) wireless telecommunication network
Nakamura Overview of ETSI NFV Network Slicing Report: Network Slicing Support with ETSI NFV Architectural Framework
CN116016229A (zh) 一种部署容器服务的方法及装置
CN114428620A (zh) 一种数据流镜像方法及装置

Legal Events

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

Ref document number: 19738338

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019738338

Country of ref document: EP

Effective date: 20200727