WO2022110944A1 - 网络切片规划的方法以及相关设备 - Google Patents

网络切片规划的方法以及相关设备 Download PDF

Info

Publication number
WO2022110944A1
WO2022110944A1 PCT/CN2021/115219 CN2021115219W WO2022110944A1 WO 2022110944 A1 WO2022110944 A1 WO 2022110944A1 CN 2021115219 W CN2021115219 W CN 2021115219W WO 2022110944 A1 WO2022110944 A1 WO 2022110944A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
slice
network device
requirement information
configuration information
Prior art date
Application number
PCT/CN2021/115219
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 华为技术有限公司
Publication of WO2022110944A1 publication Critical patent/WO2022110944A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/18—Network planning tools
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Definitions

  • the embodiments of the present application relate to the field of communications, and in particular, to a network slice planning method and related devices.
  • the fifth generation mobile networks (5G) slicing technology refers to the flexible allocation of network resources, networking on demand, and virtualized multiple logical subnets with different characteristics and isolated from each other based on the 5G network. Differentiated requirements of the application on the network.
  • Each network slice is composed of wireless network, transmission network, and core network slice subnet, and is managed uniformly through the slice management system.
  • the planning results of the core network slice subnet include creating and validating the network slice template, the go-live of the template, the necessary network environment, and other required content.
  • An actual planning method for core network slicing subnets is to use manual research to determine the planning results of core network slicing subnets, which consumes a lot of manpower and time, resulting in a long online time for services running on core network slicing subnets. And the high cost reduces the flexibility of operators to deploy services.
  • the embodiments of the present application provide a network slicing planning method and related equipment, which can enable the slicing planning of core network slicing subnets to be automatically completed online through slicing configuration information, saving a lot of manpower and time, and speeding up the operation based on slicing.
  • the online speed of services greatly improves the flexibility of operators to deploy slicing services.
  • the first network device is connected to the second network device, and the first network device can also be installed inside the second network device.
  • the first network device receives a topology planning request from the second network device, and the topology planning
  • the request carries slice configuration information, and the slice configuration information includes requirement information for creating core network slice subnet instances.
  • the first network device After the first network device receives the topology planning request sent by the second network device, the first network device determines, according to the slice configuration information that is carried in the topology planning request, that it can be used to create the core network slice subnet instance for actual implementation. Deployed slice plan configuration information.
  • the first network device After the first network device generates the slicing plan configuration information, the first network device sends a topology planning response to the second network device in response to the received topology planning request, where the topology planning response carries a slicing plan that can be used for core network slicing subnet deployment configuration information.
  • the first network device generates a slice for actual deployment of the core network slice subnet according to the slice configuration information that is carried in the topology planning request from the second network device and represents the deployment requirement of the core network slice subnet.
  • the plan configuration information is sent, and the slice plan configuration information is responded to by the topology plan, and then the core network slice subnet instance is deployed after being sent to the second network device.
  • the slicing planning of core network slicing subnets can be automatically completed online through slicing configuration information, saving a lot of manpower and time, speeding up the launch of services based on slicing operations, and greatly improving operators' flexibility in slicing service deployment.
  • the embodiments of the present application provide a first implementation manner of the first aspect:
  • the slicing plan configuration information may include a variety of information used for the deployment of core network slice subnet instances.
  • the slicing plan configuration information includes a target network function (network function, NF) set or a target data center (data center, DC) set
  • the first A network device determines, according to the slice configuration information representing the requirements of the slice subnet instance, the service requirement information that each NF or DC included in the slice subnet instance can provide services, and the service requirement information includes geographic range requirement information, geographic level requirement information, At least one of NF performance requirement information, newly added capacity requirement information, newly added data center gateway (DCGW) bandwidth requirement information, and NF requirement quantity.
  • DCGW data center gateway
  • the first network device selects a set of target NFs or a set of target DCs that meet the service requirements from the set of deployed NFs or the set of deployed DCs according to the demand that each NF or DC can provide services indicated by the service demand information.
  • the first network device can automatically screen online and automatically select target NF sets or target DC sets for core network slice subnet instance deployment that meet service requirements according to service requirement information, which improves the accuracy of screening and the efficiency of resource utilization. Efficient, automated screening process increases the ease of screening.
  • the embodiments of the present application provide a second implementation manner of the first aspect:
  • the slice configuration information representing the requirement for creating a slice subnet instance may include a variety of requirement information.
  • the slice configuration information includes slice service area information
  • the service requirement information includes the geographic range requirement information
  • the first network device can perform the slice service area information according to the slice service area information.
  • the indicated slice subnet instance needs to provide the geographic scope of the service, and determines the geographic scope requirement information representing the coverage requirement of the NF or DC in the slice subnet instance.
  • the first network device can automatically generate online and automatically based on the slicing service area information, the geographic scope requirement information for the target NF set or target DC set screening in the core network slicing subnet instance deployment, which improves the accuracy of screening and automates the process.
  • the screening process improves the convenience of screening.
  • the embodiment of the present application provides a third implementation manner of the first aspect:
  • the slice configuration information representing the requirement for creating a slice subnet instance may include a variety of requirement information.
  • the slice configuration information includes the NF deployment location, and the service requirement information includes the geographic-level requirement information
  • the first network device will perform the required information according to the NF deployment location.
  • the geographic level where the NF is located and determines the geographic level requirement information of the NF or the corresponding DC where the NF is located.
  • the first network device can automatically generate online and automatically generate geographic-level requirement information for screening the target NF set or target DC set in the core network slice subnet instance deployment according to the NF deployment location, which improves the accuracy of screening and automates the process.
  • the screening process improves the convenience of screening.
  • the embodiment of the present application provides a fourth implementation manner of the first aspect:
  • the slice configuration information representing the requirement for creating a slice subnet instance may include various requirement information.
  • the slice configuration information includes slice performance requirement information
  • the service requirement information includes NF performance requirement information
  • the first network device shall perform the required information according to the slice performance requirement information.
  • the performance requirements of the slicing subnet instance determine the NF performance requirement information of each NF in the target NF set used to deploy the slicing subnet instance.
  • the first network device can automatically generate online NF performance requirement information for screening the target NF set or target DC set in the core network slice subnet instance deployment according to the slice performance requirement information, which improves the accuracy of screening and resources. Effectiveness of use.
  • the embodiment of the present application provides a fifth implementation manner of the first aspect:
  • the slice configuration information that represents the requirement for creating a slice subnet instance can include various requirement information.
  • the slice configuration information includes service availability information, reliability information, and capacity requirement information
  • the service requirement information includes new capacity requirement information and NF requirement quantity
  • the first network device determines an NF with a fixed networking collocation relationship according to the transmission performance requirement between NFs and the networking redundancy relationship indicated by the service availability information and the failure index of a single NF indicated by the reliability information, and determines the NF requirement quantity.
  • the first network device determines, according to the total static capacity requirement of the slicing subnet instance and the NF requirement quantity indicated by the capacity requirement information, the newly added capacity requirement information of each NF in the NF group having the fixed networking collocation relationship with the quantity of the NF requirement quantity.
  • the first network device can determine the fixed networking collocation relationship of discrete NFs according to the service availability information and the reliability information, and determine the required number of NFs with the fixed networking collocation relationship, and determine the required number of NFs according to the capacity demand information and the required number of NFs.
  • the newly added capacity requirement information is used to generate the slice plan configuration information required for the deployment of slice subnet instances, complete the online automatic planning of slice subnet instances, and improve the screening efficiency. Accuracy and effectiveness of resource utilization, the automated screening process improves the convenience of screening.
  • the embodiments of the present application provide the sixth implementation manner of the first aspect:
  • the first network device determines the newly added virtual resource requirement information and the newly added DCGW bandwidth requirement information according to the newly added capacity requirement information.
  • the first network device can generate the newly added virtual resource requirement information and the newly added DCGW bandwidth requirement information for screening the target NF set or the target DC set according to the newly added capacity requirement information, so as to complete the online automatic slicing subnet instance. planning to achieve resource assessment with high accuracy and high utilization efficiency.
  • the embodiment of the present application provides the seventh implementation manner of the first aspect:
  • the first network device After the target NF set or target DC set is determined, the first network device will allocate the service requirement information for each NF to each NF or DC in the target NF set or target DC set, and generate a slice plan configuration information, the slicing plan configuration information may contain a variety of information, when the slicing plan configuration information includes planned new capacity information, the first network device determines the planned new capacity according to the new capacity requirement information and the target NF set or target DC set. Capacity increase information.
  • the first network device can generate planned new capacity information for the deployment of the slicing subnet instance according to the new capacity requirement information, so as to complete the online automatic planning of the slicing subnet instance.
  • the embodiments of the present application provide the eighth implementation manner of the first aspect:
  • the first network device determines the planned new virtual resource information according to the newly added virtual resource requirement information and the target NF set or the target DC set.
  • the first network device determines the planned newly added DCGW information according to the newly added DCGW bandwidth requirement information and the target NF set or the target DC set.
  • the first network device can generate the planned new virtual resource information and the planned new DCGW information for the deployment of the slicing subnet instance according to the newly added virtual resource requirement information and the newly added DCGW bandwidth requirement information, so as to complete the slicing subnet. Online automatic planning of instances.
  • the embodiment of the present application provides the ninth implementation manner of the first aspect:
  • the target NF set includes access and mobility management function (AMF), session management function (SMF), policy control function (PCF), network slice selection function (network slice) selection function (NSSF), charging function (CHF), network data analytics function (NWDAF), authentication server function (AUSF), unified data management (UDM) , any one of a network service presentation function (Network Exposure Function, NEF) and a user plane function (user plane function, UPF).
  • AMF access and mobility management function
  • SMF session management function
  • PCF policy control function
  • NSF network slice selection function
  • CHF charging function
  • NWF network data analytics function
  • AUSF authentication server function
  • UDM unified data management
  • the second network device sends a topology planning request to the first network device, where the topology planning request indicates that the second network device needs to obtain the topology structure of the NF required for the deployment of the slicing subnet instance, and the topology planning request carries the slicing subnet instance deployment requirement.
  • Slice configuration information includes at least one of slice service area information, NF deployment location, slice performance requirement information, service availability information, reliability information, and capacity requirement information.
  • the second network device After the second network device sends the topology planning request, it will receive the topology planning response sent by the first network device.
  • the topology planning response carries the slicing plan configuration information including the topology planning result and the resource evaluation result required for the deployment of the slicing subnet instance.
  • the slicing plan configuration information includes at least one of target NF set or target DC set, planned new capacity information, planned new virtual resource information and planned new DCGW information.
  • the second network device sends a topology planning request indicating the deployment requirement of the slice subnet instance to the first network device, and receives the topology planning result and resource evaluation sent by the first network device for the deployment of the slice subnet instance.
  • the resulting slice plan configuration information completes the online automatic planning of slice subnet instances, improves the accuracy of screening and the effectiveness of resource utilization, and the automated screening process improves the convenience of screening.
  • a third aspect of the embodiments of the present application provides a first network device, where the first network device has the function of implementing the first network device in the foregoing first aspect.
  • This function can be implemented by hardware, or by executing corresponding software in hardware, and the hardware or software includes one or more modules corresponding to the above functions.
  • a fourth aspect of the embodiments of the present application provides a second network device, where the second network device has the function of implementing the second network device in the foregoing second aspect.
  • This function can be implemented by hardware, or by executing corresponding software in hardware, and the hardware or software includes one or more modules corresponding to the above functions.
  • a fifth aspect of the embodiments of the present application provides a first network device, including a processor, a memory, an input and output device, and a bus;
  • the processor, the memory, and the input and output devices are connected to the bus;
  • the processor is configured to execute the method described in the foregoing first aspect.
  • a sixth aspect of the embodiments of the present application provides a second network device, including a processor, a memory, an input and output device, and a bus;
  • the processor, the memory, and the input and output devices are connected to the bus;
  • the processor is configured to execute the method described in the foregoing second aspect.
  • a seventh aspect of an embodiment of the present application provides a computer-readable storage medium, where a program is stored in the computer-readable storage medium, and when the computer executes the program, the method in any one of the foregoing first to second aspects is executed. process.
  • An eighth aspect of the embodiments of the present application provides a computer program product.
  • the computer program product When the computer program product is executed on a computer, the computer executes the process of the method in any one of the foregoing first to second aspects.
  • a ninth aspect of an embodiment of the present application provides a network slice planning system, where the system includes the first network device described in any one of the first aspect, the third aspect, and the fifth aspect, and the second aspect, the third aspect The second network device according to any one of the fourth aspect to the sixth aspect.
  • a tenth aspect of the embodiments of the present application provides a network slice planning method, and the method is applied to a network slice planning system, where the network slice planning system includes a first network device and a second network device;
  • the first network device receives a topology planning request from the second network device, where the topology planning request carries slice configuration information, and the slice configuration information includes requirement information for creating a core network slice subnet instance.
  • the first network device After the first network device receives the topology planning request sent by the second network device, the first network device determines, according to the slice configuration information that is carried in the topology planning request, that it can be used to create the core network slice subnet instance for actual implementation. Deployed slice plan configuration information.
  • the first network device After the first network device generates the slicing plan configuration information, the first network device sends a topology planning response to the second network device in response to the received topology planning request, where the topology planning response carries a slicing plan that can be used for core network slicing subnet deployment configuration information.
  • the embodiments of the present application have the following advantages:
  • the first network device receives the topology planning request from the second network device, and determines the slicing plan configuration for actual deployment of the core network slicing subnet according to the slicing configuration information that is carried in the topology planning request and represents the deployment requirement of the core network slicing subnet information, the first network device sends a topology planning response to the second network device, where the topology planning response carries slice plan configuration information.
  • the slicing plan configuration information includes the topology planning information and resource evaluation information required for core network slicing subnet deployment, so that the slicing planning of core network slicing subnets can be automatically completed online through the slicing configuration information, saving a lot of manpower and time, and speeding up It improves the online speed of services based on slice operation, and greatly improves the flexibility of operators to deploy slice services.
  • Figure 1 is the 5G core network architecture diagram
  • FIG. 2 is a schematic diagram of an embodiment of a method for network slice planning according to an embodiment of the present application
  • FIG. 3 is a schematic diagram of another embodiment of a method for network slice planning according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of another embodiment of a method for network slice planning according to an embodiment of the present application.
  • FIG. 5 is a schematic diagram of another embodiment of a method for network slice planning according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of another embodiment of a method for network slice planning according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of another embodiment of a method for network slice planning according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a first network device according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a second network device according to an embodiment of the present application.
  • FIG. 10 is another schematic structural diagram of a first network device according to an embodiment of the present application.
  • FIG. 11 is another schematic structural diagram of a second network device according to an embodiment of the present application.
  • the embodiment of the present application provides a method for network slice planning, which can automatically complete the slice planning of core network slice subnets online, generate the planned configuration information of the target NF, save a lot of manpower and time, and speed up the operation based on slice operation.
  • the online speed of services greatly improves the flexibility of operators to deploy slicing services.
  • 5G networks need to provide ultra-low latency, ultra-high bandwidth, and ultra-large connections;
  • 5G networks need to provide network isolation capabilities, and the networks are independent of each other;
  • 5G networks need to provide higher reliability and security to meet industrial-grade application requirements
  • 5G networks need to have automatic life cycle management and automatic operation and maintenance capabilities
  • 5G networks need to be more open, open network capabilities, and provide the ultimate experience and richer services together with applications.
  • the 5G network slicing technology uses a unified cloud infrastructure to flexibly allocate network resources and network on demand. Based on the 5G network, multiple logical subsystems with different characteristics and isolated from each other are virtualized. The network can meet the differentiated requirements of different applications on the network.
  • Each network slice is composed of wireless network, transmission network, and core network slice subnets, and is managed uniformly through the slice management system to reduce network construction costs.
  • SLA service level agreement
  • the 5G core network is a separate architecture. Traditional network elements are split into multiple NFs, and the network is constructed in a software-based, modular, and service-based manner. Because it conforms to the SBA service-oriented architecture, each NF is independent and autonomous, and no matter it is added, upgraded or transformed, it will not hinder other NFs.
  • the methods of creating 5G core network slice subnet instances include shared NF or new NF.
  • Shared NF refers to selecting an NF that meets the requirements among the deployed NFs, and dividing resources on each NF to create a new NF.
  • Core network slice subnet instance; the new NF method means that a new NF is created on the data center as required, and the new NF is used to create a new core network slice subnet instance.
  • the 5G core network builds the network in a software-based, modular, and service-based manner, in which traditional network elements are split into multiple network functions.
  • Network function refers to a single communication network function after the functions of traditional network elements in a communication network are split. Each network function is independent and autonomous, and no matter it is added, upgraded or transformed, it will not interfere with other network functions.
  • Access and mobility management function (AMF):
  • Session management function (SMF):
  • It mainly supports functions such as session establishment, modification and release. In addition, it is also responsible for UE IP address allocation and management, UPF selection and control, and tunnel maintenance between UPF and AN nodes.
  • AUSF Authentication server function
  • PCF Policy control function
  • NSSF Network slice selection function
  • the following functions may be provided: (1) select the set of network slice instances serving the UE; (2) determine the NSSAIs allowed, and if needed, determine the mapping to the subscribed S-NSSAIs; (3) determine the configured NSSAIs, And determine the mapping to the subscribed S-NSSAI when needed; (4) determine the set of AMFs that may be used to query the UE, or a list of candidate AMFs based on the configuration (perhaps by querying the NRF).
  • AUSF Authentication server function
  • CHF supports online charging, offline charging and converged charging.
  • NWDAF Network data analytics function
  • the network analysis logic function managed by the operator provides load level analysis.
  • the embodiments of the present application may apply the 5G core network architecture shown in FIG. 1 :
  • the 5G core network architecture includes network warehousing function 101, network function virtualization orchestrator 102, communication service management function 103, network slice management function 104, network planning and design function 105, network slice subnet management function 106, and network function management function 107 and Virtualized Network Function Manager 108.
  • the network repository function (NRF) 101 supports the service discovery function, receives NF discovery requests from NF instances, and provides the information of the discovered NF instances (discovered) to the NF instances; maintains available NF instances and their supported services NF configuration file.
  • the network functions virtualization orchestrator (NFVO) 102 is responsible for the overall management of network services, VNFs and resources, and is the control core of the entire NFV architecture.
  • the communication service management function (CSMF) 103 is responsible for the slice management logic function that translates the communication service requirements into the network slice requirements.
  • a network slice management function (NSMF) 104 is responsible for managing and orchestrating network slice instances, and decomposing slice management logic functions required by network slice subnets.
  • the network planning & design function (NPDF) 105 provides the functions of NSSI planning and network and service parameter design, and the NSSI planning function of NPDF is embedded in the process of creating slices.
  • the NSSI planning function includes the NSSI topology planning function and the NSSI resource evaluation function.
  • the NSSI planning function takes the slicing subnet instance requirements as input, combines the NF and DC information collected on the existing network, and provides the NSSI planning results through the automatic planning process, that is, the NSSI topology definition, deployability assessment results, and resource requirements.
  • a network slice subnet management function (NSSMF) 106 is responsible for managing and orchestrating slice management logic functions for network slice subnet instances.
  • the network function management function (NFMF) 107 is responsible for fault management, configuration management, billing management, performance management, and security management of network functions.
  • a virtualized network function manager (VNFM) 108 is responsible for the related management of the resources and life cycle of the VNF, such as the instantiation of network elements, capacity expansion and capacity reduction and other functions.
  • NPDF105 obtains the deployed NF set and deployed NF configuration information from NRF101 in advance
  • NPDF105 obtains the deployed DC set and deployed DC configuration information from NFVO102 in advance
  • CSMF103 sends a network function (network slice instance, NSI) request for creating a logical network to NSMF104, and the creation NSI request carries service configuration information ServiceProfile;
  • NSI network slice instance
  • the NSMF104 After the NSMF104 receives the request to create an NSI, it parses the ServiceProfile parameter of the service configuration information and obtains the requirements of the NSSI, and initiates a request to create an NSSI that carries the SliceProfile parameter of the slice configuration information;
  • NSSMF106 initiates a network slice subnet instance (NSSI) planning request to NPDF105, carrying NSSI requirements, and NSSI requirements can carry network and service parameter design requests;
  • NSSI network slice subnet instance
  • NPDF105 generates NSSI planning results, and generates slice topology and related service parameter configurations based on the NSSI planning results;
  • NSSMF106 sends plan configuration information of shared NF to NFMF107, which is managed by NFMF107;
  • NSSMF106 sends NS creation request to NFVO102, carrying NSD/VNFD;
  • NSSMF106 initiates a slice configuration request to NFMF107 to complete the process of slice opening;
  • NFVO102 initiates a VNF instantiation request to VNFM108 to complete the process of slice provisioning.
  • NPDF determines the service requirement information
  • NPDF selects the target NF set that meets the requirements from the deployed NF set
  • resource sharing level information in the service demand information indicates that the slice creation method is shared NF
  • NPDF selects the target DC set that meets the requirements from the deployed DC set, and creates the target NF set on the target DC set.
  • NPDF determines the target NF set from the deployed NF set:
  • NPDF selects the target NF set that meets the requirements from the deployed NF set according to the service requirement information, and then determines the slicing plan configuration information of the target NF set according to the service requirement information and the target NF set.
  • the target NF set includes a control plane NF set, and may also include other types of NF sets, such as a user plane NF set, which is not specifically limited here.
  • the target NF set includes the control plane NF set and the user plane NF set.
  • the selection of the control plane NF set and the user plane NF set that meets the requirements from the deployed NF set can be performed in different ways. The following descriptions are respectively:
  • NPDF determines the control plane NF set from the deployed NF set and determines the slicing plan configuration information:
  • the NPDF determines the target NF set belonging to the control plane according to the slice service area information and the NF actual load information, and generates plan configuration information of the slice subnet based on the target NF set.
  • the target NF set is the control plane NF set.
  • an embodiment of the method for network slice planning in the embodiment of the present application includes:
  • 201 Receive a topology planning request, where the topology planning request carries slice configuration information, where the slice configuration information includes slice service area information, resource sharing level information, and slice capacity requirement information.
  • the NPDF receives topology planning requests sent by other network devices.
  • the topology planning requests carry slice configuration information.
  • the slice configuration information includes slice service area information, resource sharing level information, and slice capacity requirement information.
  • the definitions of slice service area information, resource sharing level information and slice capacity requirement information are shown in Table 1 below:
  • Attributes definition Slicing service area The geographic extent to which a sliced subnet instance can serve Slice capacity requirement information Total demand for static capacity by sliced subnet instances resource sharing level information The isolation of NF, that is, the resources of NF are shared by several slice subnet instances.
  • the resource sharing level information is used to indicate that the creation method of the core network slice subnet is the shared NF method or the newly created NF method.
  • the resource sharing level information indicates that the creation method of the core network slice subnet is the shared NF method.
  • the NPDF receives the deployed NF set and deployed NF set configuration information sent by other network devices, and the deployed NF set configuration information includes NF service area information and NF actual load information.
  • the definitions of NF service area information and NF actual load information are shown in Table 2 below:
  • Attributes definition NF service area information Geographical range of services that the deployed NF can provide NF actual load information Actual load per NF in deployed NFs
  • NPDF determines, according to the slice service area information, the geographic scope requirement information that the slice to be created can provide services, and selects the first NF set that meets the geographic scope requirement from the deployed NF set according to the geographic scope requirement information.
  • the deployed NF set configuration information includes an NF type identifier, and the NF type identifier indicates the specific type of each NF in the deployed NF set.
  • the NPDF filters the first control plane NF set belonging to the control plane in the first NF set according to the NF type identifier.
  • control plane NF includes AMF, and may also include other control plane NFs, such as SMF, PCF, NSSF, CHF, NWDAF, AUSF, UDM or NEF, which is not specifically limited here.
  • a fixed networking relationship is set between the control plane NFs during the deployment process, forming a fixed collocation.
  • the first set of control plane NFs is actually a group-based control plane NF with a fixed collocation relationship.
  • the NF actual load information indicates the actual load of each NF.
  • the total actual load of each group of control plane NFs with a fixed connection relationship can also be obtained by calculation.
  • NPDF determines the total actual load of each group of control plane NFs in the first control plane NF set. After the information is obtained, a set of lightly loaded control plane NFs is filtered as the target NF set.
  • Attributes definition Scheduled new capacity information The additional static capacity planned for each NF in the target NF set Plan to add new virtual resource information New virtual resources in the slice subnet instance plan based on the target NF set Plan to add DCGW bandwidth information The newly added DCGW bandwidth of the slice subnet instance plan based on the target NF set
  • NPDF decomposes the total static capacity requirement of the slicing subnet instance indicated by the capacity requirement information into each NF in the target NF set, and considers a certain percentage of redundant capacity to obtain the planned new capacity information of the target NF set.
  • NPDF obtains the atomic resource overhead of the business process, that is, the capacity, virtual resources and DCGW bandwidth required by each business process, by thoroughly testing a large number of business processes generated by each end user during the running process.
  • the NPDF determines the business process corresponding to the capacity according to the capacity indicated by the planned new capacity information, and then determines the planned new virtual resource information and the planned new DCGW bandwidth information of the target NF set through the business process.
  • slice capacity requirement is decomposed to each NF in the control plane NF set, which can be decomposed on average or in other decomposition methods, such as weight decomposition, which is not limited here.
  • the deployed NF set configuration information includes the NF instance ID, DC ID, and DCGW ID corresponding to each NF.
  • NPDF filters the target NF set from the deployed NF set, it needs to determine the NF instance ID, DC ID, and NF instance ID corresponding to the target NF set.
  • DCGW logo After NPDF filters the target NF set from the deployed NF set, it needs to determine the NF instance ID, DC ID, and NF instance ID corresponding to the target NF set.
  • the NPDF sends a topology planning response to other network devices.
  • the topology planning response carries the configuration information of the slicing plan.
  • the configuration information of the slicing plan includes the target NF set, NF instance ID, DC ID, DCGW ID, planned new capacity information, and planned new virtual resources. Information and plans to add DCGW bandwidth information.
  • NPDF determines the target NF set belonging to the control plane through the slicing service area information and the NF actual load information, and generates plan configuration information of the slicing subnet based on the target NF set, completing the plan required by the slicing subnet instance Online automatic planning of configuration information.
  • NPDF determines the user plane NF set from the deployed NF set and determines the slicing plan configuration information:
  • NPDF determines the target NF set belonging to the user plane according to the slice service area information, slice capacity requirement information, NF deployment location, service availability information, reliability information, and NF actual load information, and generates slice sub-slices based on the target NF set The planned configuration information for the network.
  • the target NF set is the user plane NF set.
  • an embodiment of the method for network slice planning in the embodiment of the present application includes:
  • 301 Receive a topology planning request, carrying slice service area information, slice capacity requirement information, NF deployment location, slice performance requirement information, service availability information, reliability information, and resource sharing level information.
  • the NPDF receives topology planning requests sent by other network devices.
  • the topology planning request carries slice configuration information.
  • the slice configuration information includes slice service area information, resource sharing level information, slice capacity requirement information, NF deployment location, slice performance requirement information, and service availability. information and reliability information.
  • the definitions of slice service area information, resource sharing level information, and slice capacity requirement information are shown in Table 1; the definitions of NF deployment location, slice performance requirement information, service availability information, and reliability information are shown in Table 4 below:
  • Table 5 The information included in the network performance indicated by the slice performance requirement information is shown in Table 5 below. It should be noted that Table 4 in Table 4 is only an example of the information included in the network performance. In practical applications, the network performance also includes Other information, such as end-to-end delay or jitter does not exist, which is not limited here:
  • the resource sharing level information indicates that the creation mode of the core network slice subnet is the shared NF mode.
  • the NPDF receives deployed NF set and deployed NF set configuration information sent by other network devices.
  • the deployed NF set configuration information includes NF service area information, NF geographic level information, NF measurement performance information, NF specification information and NF actual load information.
  • NF service area information and NF actual load information are shown in Table 2; the definitions of NF geographic level information, NF measurement performance information and NF specification information are shown in Table 6 below:
  • Step 303 in this embodiment is similar to step 203 in the aforementioned embodiment shown in FIG. 2 , and details are not described herein again.
  • the NPDF filters the first user plane NF set belonging to the user plane in the first NF set according to the NF type identifier.
  • the user plane NF includes the UPF, and may also include a new user plane NF that will appear in the future, which is not specifically limited here.
  • NPDF determines the geographical level to which the deployment position of the user plane NF belongs, and selects the second user plane NF that meets the requirements of the geographical level from the first user plane NF set according to the requirements of the geographical level. gather.
  • NPDF determines the network performance requirements of each NF in the slicing subnet instance according to the network performance requirements of the slicing subnet instance indicated by the slicing performance requirement information, and selects the NFs that meet the network performance requirements from the second user plane NF set according to the NF performance requirement information.
  • the third user plane NF set The third user plane NF set.
  • User plane NFs do not have a predetermined fixed network collocation relationship and are discrete. It is necessary to determine a set of user plane NF sets with fixed collocation relationships that can form a logical network from a group of discrete user plane NF sets.
  • NPDF determines the fixed networking collocation relationship between the NFs in the third user plane NF set according to the service availability information and reliability information. While determining the fixed networking collocation relationship, it also determines a set of NF requirements that meet the fixed networking collocation relationship. quantity.
  • NPDF determines the newly added capacity requirement information of each NF when the number of NFs in the slicing subnet instance is the required NF quantity.
  • NPDF selects the fourth user plane NF set whose NF specification meets the new capacity requirement from the third user plane NF set according to the NF demand quantity and the newly added capacity demand information.
  • Step 310 in this embodiment is similar to step 206 in the aforementioned embodiment shown in FIG. 2 , and details are not repeated here.
  • the NPDF selects the fifth user plane NF set that meets the virtual resource requirement from the fourth user plane NF set.
  • Steps 312 to 315 in this embodiment are similar to steps 205 to 208 in the foregoing embodiment shown in FIG. 2 , and details are not described herein again.
  • NPDF determines the target NF set belonging to the user plane according to the slice service area information, slice capacity requirement information, NF deployment location, service availability information, reliability information, and NF actual load information, and generates slice sub-slices based on the target NF set
  • the plan configuration information of the network is completed, and the online automatic planning of the plan configuration information required by the slicing subnet instance is completed.
  • NPDF determines the target DC set from the deployed DC set, and determines the target NF set according to the target DC set:
  • the NPDF selects the target DC set that meets the requirements from the deployed DC set according to the service requirement information, and then determines the target NF set and slice plan configuration information according to the service requirement information.
  • the target DC set includes a central area DC set, and may also include other types of DC sets, such as an edge area DC set, which is not specifically limited here.
  • the target DC set includes the central area DC set and the edge area DC set.
  • the selection of the central area DC set and the edge area DC set that meet the needs of the deployed DC set can be performed in different ways. The following descriptions are respectively:
  • NPDF determines the central area DC set from the deployed DC set and determines the control plane NF set and slice plan configuration information corresponding to the central area DC set:
  • NPDF determines the target DC set belonging to the central area according to the slice service area information, capacity requirement information, service availability information, and reliability information, generates a target NF set belonging to the control plane according to the target DC set, and generates a target NF based on the target NF Schedule configuration information for the collection's slice subnets.
  • the target NF set is the control plane NF set
  • the target DC set is the central area DC set
  • an embodiment of the method for network slice planning in the embodiment of the present application includes:
  • 401. Receive a topology planning request, carrying slice service area information, slice capacity requirement information, service availability information, reliability information, and resource sharing level information.
  • Step 401 in this embodiment is similar to step 301 in the aforementioned embodiment shown in FIG. 3 , and details are not described herein again.
  • the resource sharing level information indicates that the creation mode of the core network slice subnet is the newly created NF mode.
  • the NPDF receives the deployed DC set and deployed DC set configuration information sent by other network devices.
  • the deployed DC set configuration information includes DC service area information, DC resource usage information, DC specification capability information, anti-affinity requirement information, and DC geographic level information.
  • the definitions of DC service area information, DC resource usage information and DC geographic level information are shown in Table 7 below:
  • Step 403 in this embodiment is similar to step 303 in the aforementioned embodiment shown in FIG. 3 , and details are not described herein again.
  • Each DC has a geographic level, and DCs at different geographic levels have different levels of capabilities.
  • DCs at the provincial or municipal level are called central DCs, and DCs at district or county level or client rooms are called edge DCs.
  • District DC but the division of central area DC and edge area DC is not absolute, and needs to be defined according to actual needs.
  • the first central area DC set is determined from the first DC set according to the geographic level at which the DC indicated by the DC geographic level information is located.
  • Steps 405 to 409 in this embodiment are similar to steps 307 to 311 in the aforementioned embodiment shown in FIG. 3 , and details are not repeated here.
  • NPDF selects a set of lightly loaded DCs from the third central area DC set, and combines the anti-affinity requirements between DCs to select a set of lightly loaded DCs from the lightly loaded DCs. Determine the set of target DCs with higher security.
  • NPDF determines the target DC set, it determines the capacity that needs to be created for each DC set in the target DC set according to the capacity requirement of each NF indicated by the newly added capacity requirement, and obtains the target NF set and the target NF set of each NF in the target NF set. Information on planned new capacity requirements.
  • Steps 412 to 414 in this embodiment are similar to steps 313 to 315 in the aforementioned embodiment shown in FIG. 3 , and details are not repeated here.
  • NPDF selects the target DC set that meets the requirements from the deployed DC set according to the service demand information, and then determines the target NF set and the slicing plan configuration information according to the service demand information, and completes the plan configuration required by the slicing subnet instance Online automatic planning of information.
  • NPDF determines the edge area DC set from the deployed DC set and determines the user plane NF set and slice plan configuration information corresponding to the edge area DC set:
  • NPDF determines the target DC set belonging to the edge zone according to the slice service area information, slice capacity requirement information, NF deployment location, slice performance requirement information, service availability information, and reliability information, and generates a target DC set belonging to the user plane according to the target DC set.
  • the target NF set is generated, and the plan configuration information of the slice subnet based on the target NF set is generated.
  • the target NF set is the user plane NF set
  • the target DC set is the edge area DC set
  • an embodiment of the method for network slice planning in the embodiment of the present application includes:
  • 501. Receive a topology planning request, carrying slice service area information, slice capacity requirement information, NF deployment location, slice performance requirement information, service availability information, reliability information, and resource sharing level information.
  • Step 501 in this embodiment is similar to step 301 in the aforementioned embodiment shown in FIG. 3 , and details are not described herein again.
  • the NPDF receives the deployed DC set and deployed DC set configuration information sent by other network devices.
  • the deployed DC set configuration information includes DC service area information, DC resource usage information, DC specification capability information, anti-affinity requirement information, and DC measurement performance. information and DC geo-level information.
  • the definitions of DC service area information, DC resource usage information, DC specification capability information, anti-affinity requirement information and DC geographic level information are shown in Table 7; the definitions of DC measurement performance information are shown in Table 8 below:
  • Steps 503 to 504 in this embodiment are similar to steps 403 to 404 in the foregoing embodiment shown in FIG. 4 , and details are not described herein again.
  • Steps 505 to 506 in this embodiment are similar to steps 305 to 306 in the foregoing embodiment shown in FIG. 3 , and details are not described herein again.
  • Steps 507 to 516 in this embodiment are similar to steps 405 to 414 in the aforementioned embodiment shown in FIG. 4 , and details are not described herein again.
  • NPDF determines the target DC set belonging to the edge zone according to the slice service area information, slice capacity requirement information, NF deployment location, slice performance requirement information, service availability information, and reliability information, and generates a target DC set belonging to the user plane according to the target DC set.
  • the target NF set is generated, and the plan configuration information of the slice subnet based on the target NF set is generated, and the online automatic planning of the plan configuration information required by the slice subnet instance is completed.
  • the NPDF may be configured as a network element independently, or may be configured in other manners, for example, the NPDF is configured in the NSSMF, which is not specifically limited here.
  • This embodiment only takes NPDF configured as one network element as an example for introduction:
  • the NPDF receives the deployed NF list sent by the NRF.
  • the NPDF receives the deployed NF list sent by the NRF.
  • the deployed NF list includes the deployed NF set and deployed NF configuration information.
  • the information included in the deployed NF configuration information is shown in Table 9 below:
  • the following table 9 is only an example of the information contained in the deployed NF list.
  • the deployed NF list also includes other information, such as the absence of NF geographic level information or NF status information. There is no specific limitation here.
  • the NPDF receives the deployed DC list sent by the NFVO.
  • the NPDF receives the deployed DC list sent by NFVO.
  • the deployed DC list includes the deployed DC set and deployed DC configuration information.
  • the information included in the deployed DC configuration information is shown in Table 11 below:
  • the following table 11 is only an example of the information contained in the deployed DC list.
  • the deployed DC list also includes other information, for example, the first DC identifier or DC service area information does not exist. , which is not specifically limited here.
  • step 602 may be executed after step 601, or may be executed before step 601, which is not specifically limited here.
  • the NSMF sends an NSSI creation request to the NSSMF.
  • the NSMF initiates an NSSI creation request to the NSSMF, carrying the slice subnet instance identifier, slice configuration information, and slice service area information.
  • the information included in the slice configuration information is shown in Table 12 below:
  • the slice configuration information also includes other information, such as the coverage tracking area list information or the absence of the NF deployment location. There is no specific limitation here.
  • the NSSMF sends a topology planning request to the NPDF.
  • NSSMF initiates a slice topology planning request to NPDF, carrying slice configuration information and slice service area information.
  • the slice service area may be configured independently, or may be configured in other ways, for example, in the slice configuration information, which is not specifically limited here.
  • NPDF determines the deployment type.
  • NPDF performs NF selection or DC selection according to the deployment type.
  • NPDF performs capacity decomposition according to the slice capacity requirement information.
  • the topology planning unit of the NPDF sends a resource assessment request to the resource assessment unit of the NPDF.
  • NPDF conducts resource assessment according to the information on newly added capacity requirements.
  • the resource evaluation unit of NPDF sends the resource evaluation result to the topology planning unit of NPDF.
  • steps 605 to 610 are similar to those in the embodiments shown in FIG. 2 to FIG. 4 , and details are not repeated here.
  • the NPDF sends a topology planning response to the NSSMF.
  • NPDF After NPDF completes topology planning and resource evaluation according to the slice configuration information, NPDF sends a topology planning response to NSSMF, where the topology planning response carries the slice plan configuration information used for the deployment of slice subnet instances.
  • the information contained in the slice plan configuration information is shown in Table 13 below:
  • NSSMF 612
  • NPDF 612
  • NFVO NFVO
  • NRF 612
  • NSSMF, NPDF, NFVO, and NRF perform NSSI deployment based on the planning configuration information carried in the topology planning response.
  • the NSSMF sends an NSSI creation response to the NSMF.
  • the NSSMF sends an NSSI creation response to the NSMF, and the NSSI creation response carries the configuration information of the newly created NSSI.
  • FIG. 7 An application scenario of the embodiment of the present application is introduced below, please refer to FIG. 7 :
  • the NPDF judges the deployment mode of the slice network subnet according to the resource sharing level information contained in the slice configuration information.
  • the resource sharing level information is used to indicate whether the created NSSI needs to have an exclusive NF or share the NF with other NSSIs.
  • NPDF determines that the creation mode of the slice subnet instance is the shared NF mode or the newly created NF mode.
  • step 603 is executed; when the creation mode of the slice subnet instance is the newly created NF mode, Step 612 is performed.
  • the NPDF receives the coverage tracking area list information sent by the network device, and performs matching according to the coverage tracking area list information. If the matching is successful, step 605 is performed; if the matching fails, step 604 is performed.
  • the deployed NF data stored in the NRF contains the tracking area list information configured by each NF, which is used to represent the user equipment served by each NF.
  • the NSMF receives the service configuration information carried in the request to create a sliced network sent by the CSMF, where the service configuration information includes coverage information. After NSMF parses the coverage information, the coverage tracking area list information is obtained by deriving the coverage information and the tracking area list information. There are two methods for NSMF to deduce the tracking area list information of the coverage area. One is that NSMF reuses the tracking area list information already allocated on the existing network for derivation, and the other is that NSMF superimposes the tracking area list information on the existing network.
  • the existing network multiplexing coverage tracking area list information If the coverage tracking area list information obtained by the derivation method of multiplexing the existing network is called the existing network multiplexing coverage tracking area list information, if the coverage tracking area list information is obtained by superimposing the tracking area list information on the existing network It is called the tracking area list information of the existing network overlay coverage. Using the existing network multiplexing coverage tracking area list information to match the first NF set in the deployed NF set, but using the existing network overlay coverage tracking area list information to match will result in a matching failure.
  • Step 604 in this embodiment is similar to step 204 in the aforementioned embodiment shown in FIG. 2 , and details are not described herein again.
  • steps 605 to 607 in this embodiment are similar to those in the foregoing embodiment shown in FIG. 2 , and are not repeated here.
  • steps 608 to 611 in this embodiment are similar to those in the foregoing embodiment shown in FIG. 3 , and are not repeated here.
  • steps 608 to 611 are an iterative cycle process in practical applications, that is, multiple screenings can be performed from different angles according to different requirements to achieve the optimal selection.
  • cyclic filtering can be performed based on the number of NFs, information on newly added capacity of NFs, information on newly added capacity requirements, and information on actual load of NFs.
  • steps 712 to 715 in this embodiment are similar to those in the foregoing embodiment shown in FIG. 4 , and are not repeated here.
  • 714 to 715 is an iterative cycle process in practical applications, that is, it can be screened multiple times from different angles according to different needs to achieve the optimal selection.
  • cyclic screening can be performed based on anti-affinity requirement information, NF quantity, new capacity requirement information, and DC resource usage information.
  • steps 716 to 719 in this embodiment are similar to those in the foregoing embodiment shown in FIG. 5 , and are not repeated here.
  • 716 to 719 is an iterative cycle process in practical applications, that is, it can be screened multiple times from different angles according to different needs to achieve the optimal selection.
  • cyclic screening can be performed based on anti-affinity requirement information, NF quantity, new capacity requirement information, and DC resource usage information.
  • step 720 in this embodiment are similar to those in the foregoing embodiments shown in FIG. 2 to FIG. 4 , and details are not repeated here.
  • the first network device in the embodiment of the present application is described below, referring to FIG. 8 .
  • the first network device in the embodiment of the present application includes a receiving unit 801 , a determining unit 802 , and a sending unit 803 .
  • a receiving unit 801 configured to receive a topology planning request from a second network device, where the topology planning request carries slice configuration information;
  • a determining unit 802 configured to determine slice plan configuration information according to slice configuration information
  • the sending unit 803 is configured to send a topology planning response to the second network device, where the topology planning response carries slice plan configuration information.
  • the determining unit 802 is specifically configured to determine service requirement information according to the slice configuration information when the slice plan configuration information includes a target NF set or a target DC set, and the service requirement information includes geographic range requirement information, geographic level requirement information, NF performance requirement information, at least one of newly added capacity requirement information, newly added data center gateway DCGW bandwidth requirement information and NF requirement quantity;
  • the determining unit 802 is further configured to determine the target NF set or the target DC set according to the service requirement information.
  • the determining unit 802 is specifically configured to determine the geographic scope requirement information according to the slice service area information when the slice configuration information includes slice service area information and the service requirement information includes geographic scope requirement information.
  • the determining unit 802 is specifically configured to determine the geographic-level requirement information according to the NF deployment position when the slice configuration information includes the NF deployment location and the service requirement information includes geographic-level requirement information.
  • the determining unit 802 is specifically configured to determine the NF performance requirement information according to the slice performance requirement information when the slice configuration information includes slice performance requirement information and the service requirement information includes NF performance requirement information.
  • the determining unit 802 is specifically configured to determine the NF requirement according to the service availability information and the reliability information when the slice configuration information includes service availability information, reliability information and capacity requirement information, and the service requirement information includes newly added capacity requirement information and NF requirement quantity quantity;
  • the determining unit 802 is further configured to determine the newly added capacity requirement information according to the capacity requirement information and the NF requirement quantity.
  • the determining unit 802 is specifically configured to, when the slice configuration information includes service availability information, reliability information and capacity requirement information, and the service requirement information includes newly added capacity requirement information, newly added virtual resource requirement information and newly added DCGW bandwidth requirement information, according to the The newly added capacity requirement information determines the newly added virtual resource requirement information and the newly added DCGW bandwidth requirement information.
  • the determining unit 802 is specifically configured to determine the planned new capacity information according to the new capacity requirement information and the target NF set or the target DC set when the slice plan configuration information includes the planned new capacity information.
  • the determining unit 802 is specifically configured to determine the plan according to the newly added virtual resource demand information and the target NF set or the target DC set when the slice plan configuration information includes the planned new capacity information, the planned new virtual resource information and the planned new DCGW information Add virtual resource information;
  • the determining unit 802 is further configured to determine the planned newly added DCGW information according to the newly added DCGW bandwidth requirement information and the target NF set or the target DC set.
  • the second network device in the embodiment of the present application is described below, referring to FIG. 9 .
  • the second network device in the embodiment of the present application includes a sending unit 901 and a receiving unit 902 .
  • a sending unit 901 is configured to send a topology planning request to a first network device, where the topology planning request carries slice configuration information, and the slice configuration information includes slice service area information, NF deployment location, slice performance requirement information, service availability information, and reliability information and at least one of capacity requirement information;
  • the receiving unit 902 is configured to receive a topology planning response sent by the first network device, where the topology planning response carries slicing plan configuration information, where the slicing plan configuration information includes a target NF set or a target DC set, planned new capacity information, planned new virtual At least one of resource information and planned new DCGW information.
  • FIG. 10 is a schematic structural diagram of a first network device provided by an embodiment of the present application.
  • the first network device 1000 may include one or more central processing units (CPUs) 1001 and a memory 1005.
  • the memory 1005 stores There is one or more applications or data.
  • the memory 1005 may be volatile storage or persistent storage.
  • a program stored in memory 1005 may include one or more modules, each of which may include a series of instructions to operate on the server.
  • the central processing unit 1001 may be configured to communicate with the memory 1005 to execute a series of instruction operations in the memory 1005 on the first network device 1000 .
  • the first network device 1000 may also include one or more power supplies 1002, one or more wired or wireless network interfaces 1003, one or more input and output interfaces 1004, and/or, one or more operating systems, such as Windows Server TM , Mac OS X TM , Unix TM , Linux TM , FreeBSD TM and so on.
  • one or more operating systems such as Windows Server TM , Mac OS X TM , Unix TM , Linux TM , FreeBSD TM and so on.
  • the central processing unit 1001 can perform the operations performed by the first network device in the foregoing embodiments shown in FIG. 2 to FIG. 7 , and details are not described herein again.
  • the second network device 1100 may include one or more central processing units (central processing units, CPU) 1101 and a memory 1105.
  • the memory 1105 stores There is one or more applications or data.
  • the memory 1105 may be volatile storage or persistent storage.
  • a program stored in memory 1105 may include one or more modules, each of which may include a series of instructions to operate on the server.
  • the central processing unit 1101 may be configured to communicate with the memory 1105 to execute a series of instruction operations in the memory 1105 on the second network device 1100 .
  • the second network device 1100 may also include one or more power supplies 1102, one or more wired or wireless network interfaces 1103, one or more input and output interfaces 1104, and/or, one or more operating systems, such as Windows Server TM , Mac OS X TM , Unix TM , Linux TM , FreeBSD TM and so on.
  • one or more operating systems such as Windows Server TM , Mac OS X TM , Unix TM , Linux TM , FreeBSD TM and so on.
  • the central processing unit 1101 may perform the operations performed by the second network device in the foregoing embodiments shown in FIG. 2 to FIG. 7 , and details are not described herein again.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and 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 in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as an independent product, may be stored in a computer-readable storage medium.
  • the technical solution of the present application or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium and includes several instructions to make a computer device ( It may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes .

Landscapes

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

Abstract

本申请实施例公开了一种网络切片规划的方法以及相关设备，用于通过切片配置信息在线自动生成核心网切片子网实例部署所需要的切片计划配置信息，加快了基于切片运营的业务的上线速度，大幅提高了运营商进行切片业务部署的灵活性。本申请实施例方法包括：第一网络设备接收来自于第二网络设备的拓扑规划请求，根据拓扑规划请求中携带的切片配置信息确定切片计划配置信息，将切片计划配置信息通过拓扑规划响应发送给第二网络设备。

Description

网络切片规划的方法以及相关设备
本申请要求于2020年11月24日提交中国专利局、申请号为202011332093.X、发明名称为“网络切片规划的方法以及相关设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，尤其涉及一种网络切片规划的方法以及相关设备。
背景技术
第五代移动通信网络(fifth generation mobile networks，5G)切片技术是指将网络资源灵活分配，按需组网，基于5G网络虚拟出多个具有不同特点且互相隔离的逻辑子网，可以满足不同应用对网络的差异化需求。每个网络切片均由无线网、传输网、核心网切片子网组合而成，并通过切片管理系统进行统一的管理。
核心网切片子网的规划结果包括创建和验证网络切片模板、模板的上线、必要的网络环境以及其他所需内容。一种核心网切片子网的实际规划方法中是采用人工调研的方式确定核心网切片子网的规划结果，消耗大量的人力和时间，造成基于核心网切片子网运行的业务上线时间较长，并且高昂的成本降低了运营商进行业务部署的灵活性。
发明内容
本申请实施例提供了一种网络切片规划的方法以及相关设备，能够使核心网切片子网的切片规划可以通过切片配置信息在线自动完成，节约了大量的人力和时间，加快了基于切片运营的业务的上线速度，大幅提高了运营商进行切片业务部署的灵活性。
本申请实施例第一方面提供了一种网络切片规划的方法：
在5G核心网架构中，第一网络设备和第二网络设备相连，第一网络设备也可以安装在第二网络设备内部，第一网络设备接收来自于第二网络设备的拓扑规划请求，拓扑规划请求中携带切片配置信息，切片配置信息中包括创建核心网切片子网实例的需求信息。
第一网络设备在接收第二网络设备发送的拓扑规划请求之后，第一网络设备根据拓扑规划请求中携带的表示需求的切片配置信息，确定可以用于创建核心网切片子网实例过程中进行实际部署的切片计划配置信息。
当第一网络设备生成切片计划配置信息之后，第一网络设备针对接收的拓扑规划请求，向第二网络设备发送拓扑规划响应，拓扑规划响应中携带可以用于核心网切片子网部署的切片计划配置信息。
可以理解的是，第一网络设备根据来自于第二网络设备的拓扑规划请求中携带的表示核心网切片子网部署需求的切片配置信息，生成了用于进行核心网切片子网实际部署的切片计划配置信息，并将切片计划配置信息通过拓扑规划响应，向第二网络设备发送后进行核心网切片子网实例的部署。核心网切片子网的切片规划可以通过切片配置信息在线自动完成，节约了大量的人力和时间，加快了基于切片运营的业务的上线速度，大幅提高了运营商进行切片业务部署的灵活性。
基于第一方面，本申请实施例提供了第一方面的第一种实施方式：
切片计划配置信息可以包括多种用于核心网切片子网实例部署的信息，当切片计划配置信息包括目标网络功能(network function，NF)集合或目标数据中心(data center，DC)集合时，第一网络设备根据表示切片子网实例需求的切片配置信息，确定切片子网实例中包括的每一个NF或DC能够提供服务的服务需求信息，服务需求信息包括地理范围需求信息、地理层级需求信息、NF性能需求信息、新增容量需求信息、新增数据中心网关(data center gateway，DCGW)带宽需求信息和NF需求数量中的至少一种。
第一网络设备根据服务需求信息指示的每一个NF或DC能够提供服务的需求，从已部署NF集合或已部署DC集合中筛选满足服务需求的目标NF集合或目标DC集合。
可以理解的是，第一网络设备可以根据服务需求信息在线自动筛选满足服务需求的，用于核心网切片子网实例部署的目标NF集合或目标DC集合，提高了筛选的精准性和资源利用的有效性，自动化的筛选过程提高了筛选的便捷性。
基于第一方面和第一方面的第一种实施方式，本申请实施例提供了第一方面的第二种实施方式：
表示切片子网实例创建需求的切片配置信息中可以包括多种需求信息，当切片配置信息包括切片服务区域信息，服务需求信息包括所述地理范围需求信息时，第一网络设备根据切片服务区域信息指示的切片子网实例需要提供服务的地理范围，确定表示切片子网实例中对NF或DC覆盖范围需求的地理范围需求信息。
可以理解的是，第一网络设备可以根据切片服务区域信息在线自动生成用于核心网切片子网实例部署中目标NF集合或目标DC集合筛选的地理范围需求信息，提高了筛选的精准性，自动化的筛选过程提高了筛选的便捷性。
基于第一方面至第一方面的第二种实施方式中任一种，本申请实施例提供了第一方面的第三种实施方式：
表示切片子网实例创建需求的切片配置信息中可以包括多种需求信息，当切片配置信息包括NF部署位置，服务需求信息包括所述地理层级需求信息时，第一网络设备根据NF部署位置指示的NF所处的地理层级，确定NF或NF对应DC所处的地理层级需求信息。
可以理解的是，第一网络设备可以根据NF部署位置在线自动生成用于核心网切片子网实例部署中目标NF集合或目标DC集合筛选的地理层级需求信息，提高了筛选的精准性，自动化的筛选过程提高了筛选的便捷性。
基于第一方面至第一方面的第三种实施方式中任一种，本申请实施例提供了第一方面的第四种实施方式：
表示切片子网实例创建需求的切片配置信息中可以包括多种需求信息，当切片配置信息包括切片性能需求信息，服务需求信息包括NF性能需求信息时，第一网络设备根据切片性能需求信息指示的切片子网实例的性能需求，确定用于部署切片子网实例的目标NF集合中每个NF的NF性能需求信息。
可以理解的是，第一网络设备可以根据切片性能需求信息在线自动生成用于核心网切片子网实例部署中目标NF集合或目标DC集合筛选的NF性能需求信息，提高了筛选的精准性和资源利用的有效性。
基于第一方面至第一方面的第四种实施方式中任一种，本申请实施例提供了第一方面的第五种实施方式：
表示切片子网实例创建需求的切片配置信息中可以包括多种需求信息，当切片配置信息包括业务可用性信息、可靠性信息和容量需求信息，服务需求信息包括新增容量需求信息和NF需求数量时，第一网络设备根据业务可用性信息指示的NF之间的传输性能要求和组网冗余关系以及可靠性信息指示的单个NF的故障指标，确定具有固定组网搭配关系的NF，并确定NF需求数量。
第一网络设备根据容量需求信息指示的切片子网实例静态容量总需求和NF需求数量确定数量为NF需求数量的具有固定组网搭配关系的NF组中每个NF的新增容量需求信息。
可以理解的是，第一网络设备可以根据业务可用性信息和可靠性信息确定离散NF的固定组网搭配关系，并确定具有固定组网搭配关系的NF的需求数量，根据容量需求信息和NF需求数量确定具有固定组网搭配关系的NF的新增容量需求信息，新增容量需求信息用于生成切片子网实例部署需要的切片计划配置信息，完成切片子网实例的在线自动规划，提高了筛选的精准性和资源利用的有效性，自动化的筛选过程提高了筛选的便捷性。
基于第一方面的第五种实施方式，本申请实施例提供了第一方面的第六种实施方式：
第一网络设备根据新增容量需求信息确定新增虚拟资源需求信息和新增DCGW带宽需求信息。
可以理解的是，第一网络设备可以根据新增容量需求信息生成用于目标NF集合或目标DC集合筛选的新增虚拟资源需求信息和新增DCGW带宽需求信息，完成切片子网实例的在线自动规划，实现了高精确度和高利用效率的资源评估。
基于第一方面至第一方面的第六种实施方式中任一种，本申请实施例提供了第一方面的第七种实施方式：
当确定了目标NF集合或目标DC集合之后，第一网络设备会将服务需求信息对每个NF的需求，分配到目标NF集合或目标DC集合中的每一个NF或DC上，生成切片计划配置信息，切片计划配置信息可以包含多种信息，当切片计划配置信息包括计划新增容量信息时，第一网络设备根据新增容量需求信息和所述目标NF集合或目标DC集合确定所述计划新增容量信息。
可以理解的是，第一网络设备可以根据新增容量需求信息生成用于切片子网实例部署的计划新增容量信息，完成切片子网实例的在线自动规划。
基于第一方面的第七种实施方式，本申请实施例提供了第一方面的第八种实施方式：
第一网络设备根据新增虚拟资源需求信息和目标NF集合或目标DC集合确定计划新增虚拟资源信息。
第一网络设备根据新增DCGW带宽需求信息和目标NF集合或目标DC集合确定所述计划新增DCGW信息。
可以理解的是，第一网络设备可以根据新增虚拟资源需求信息和新增DCGW带宽需求信息生成用于切片子网实例部署的计划新增虚拟资源信息和计划新增DCGW信息，完成切片子网实例的在线自动规划。
基于第一方面至第一方面的第八种实施方式中任一种，本申请实施例提供了第一方面的第九种实施方式：
目标NF集合包括接入和移动性管理功能(access and mobility management function，AMF)、会话管理功能(session management function，SMF)、策略控制功能(policy control function，PCF)、网络切片选择功能(network slice selection function，NSSF)、计费功能(charging function，CHF)、网络数据分析功能(network data analytics function，NWDAF)、认证服务器功能(authentication server function，AUSF)、统一数据管理(unified data management，UDM)、网络业务呈现功能(Network Exposure Function，NEF)和用户平面功能(user plane function，UPF)中任一种。
本申请实施例第二方面提供了一种网络切片规划的方法：
第二网络设备向第一网络设备发送拓扑规划请求，拓扑规划请求表示第二网络设备需要获取切片子网实例部署所需要的NF的拓扑结构，拓扑规划请求中携带表示切片子网实例部署需求的切片配置信息，切片配置信息包括切片服务区域信息、NF部署位置、切片性能需求信息、业务可用性信息、可靠性信息和容量需求信息中的至少一种。
第二网络设备在发送拓扑规划请求之后，会接收第一网络设备发送的拓扑规划响应，拓扑规划响应中携带包含切片子网实例部署所需要的表示拓扑规划结果和资源评估结果的切片计划配置信息，切片计划配置信息包括目标NF集合或目标DC集合，计划新增容量信息、计划新增虚拟资源信息和计划新增DCGW信息中的至少一种。
可以理解的是，第二网络设备向第一网络设备发送表示切片子网实例部署需求的拓扑规划请求，收到第一网络设备发送的用于切片子网实例部署的表示拓扑规划结果和资源评估结果的切片计划配置信息，完成切片子网实例的在线自动规划，提高了筛选的精准性和资源利用的有效性，自动化的筛选过程提高了筛选的便捷性。
本申请实施例第三方面提供了一种第一网络设备，该第一网络设备具有实现前述第一方面中第一网络设备的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现，该硬件或软件包括一个或多个与上述功能相对应的模块。
本申请实施例第四方面提供了一种第二网络设备，该第二网络设备具有实现前述第二方面中第二网络设备的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现，该硬件或软件包括一个或多个与上述功能相对应的模块。
本申请实施例第五方面提供了一种第一网络设备，包括处理器、存储器、输入输出设备以及总线；
处理器、存储器、输入输出设备与总线相连；
处理器用于执行前述第一方面所述的方法。
本申请实施例第六方面提供了一种第二网络设备，包括处理器、存储器、输入输出设备以及总线；
处理器、存储器、输入输出设备与总线相连；
处理器用于执行前述第二方面所述的方法。
本申请实施例第七方面提供了一种计算机可读存储介质，该计算机可读存储介质中保 有程序，当计算机执行程序时，执行前述第一方面至第二方面中任一项所述方法中的流程。
本申请实施例第八方面提供了一种计算机程序产品，当该计算机程序产品在计算机上执行时，计算机执行前述第一方面至第二方面中任一项所述方法中的流程。
本申请实施例第九方面提供了一种网络切片规划的系统，该系统包括上述第一方面、第三方面和第五方面中任一种所述的第一网络设备，以及第二方面、第四方面至第六方面中任一种所述的第二网络设备。
本申请实施例第十方面提供了一种网络切片规划的方法，该方法应用于网络切片规划的系统，该网络切片规划系统包括第一网络设备和第二网络设备；
第一网络设备接收来自于第二网络设备的拓扑规划请求，拓扑规划请求中携带切片配置信息，切片配置信息中包括创建核心网切片子网实例的需求信息。
第一网络设备在接收第二网络设备发送的拓扑规划请求之后，第一网络设备根据拓扑规划请求中携带的表示需求的切片配置信息，确定可以用于创建核心网切片子网实例过程中进行实际部署的切片计划配置信息。
当第一网络设备生成切片计划配置信息之后，第一网络设备针对接收的拓扑规划请求，向第二网络设备发送拓扑规划响应，拓扑规划响应中携带可以用于核心网切片子网部署的切片计划配置信息。
从以上技术方案可以看出，本申请实施例具有以下优点：
第一网络设备接收来自于第二网络设备的拓扑规划请求，根据拓扑规划请求中携带的表示核心网切片子网部署需求的切片配置信息确定用于进行核心网切片子网实际部署的切片计划配置信息，第一网络设备向第二网络设备发送拓扑规划响应，拓扑规划响应中携带切片计划配置信息。切片计划配置信息包含了核心网切片子网部署所需要的拓扑规划信息和资源评估信息，使核心网切片子网的切片规划可以通过切片配置信息在线自动完成，节约了大量的人力和时间，加快了基于切片运营的业务的上线速度，大幅提高了运营商进行切片业务部署的灵活性。
附图说明
图1为5G核心网架构图；
图2为本申请实施例网络切片规划的方法的一个实施例示意图；
图3为本申请实施例网络切片规划的方法的另一实施例示意图；
图4为本申请实施例网络切片规划的方法的另一实施例示意图；
图5为本申请实施例网络切片规划的方法的另一实施例示意图；
图6为本申请实施例网络切片规划的方法的另一实施例示意图；
图7为本申请实施例网络切片规划的方法的另一实施例示意图；
图8为本申请实施例第一网络设备的一个结构示意图；
图9为本申请实施例第二网络设备的一个结构示意图；
图10为本申请实施例第一网络设备的另一结构示意图；
图11为本申请实施例第二网络设备的另一结构示意图。
具体实施方式
本申请实施例提供了一种网络切片规划的方法，能够使核心网切片子网的切片规划在线自动完成，生成目标NF的计划配置信息，节约了大量的人力和时间，加快了基于切片运营的业务的上线速度，大幅提高了运营商进行切片业务部署的灵活性。
在数字化转型的需求下，各行各业产生的各种丰富的应用对网络性能提出了新的挑战，需要网络具有超低时延、超高带宽、超大连接以及敏捷性、可靠性、自动化的运维能力和开放性：
(1)网络能力：5G网络需要提供超低时延、超高带宽、超大连接；
(2)敏捷性：5G网络需要更加的敏捷，根据业务的需求提供差异化的网络能力；
(3)网络隔离：5G网络需要提供网络隔离的能力，网络之间互相独立；
(4)可靠性：5G网络需要提供更高的可靠性和安全性来满足工业级的应用需求；
(5)运维能力：5G网络需要具备自动化生命周期管理，自动化的运维能力；
(6)开放性：5G网络需要更加的开放，开放网络能力，与应用一起提供极致的体验和更加丰富的业务。
然而，建设能满足所有性能需求的网络无疑要付出巨额的成本，并且不同的应用对网络性能的需求也不尽相同，高性能的网络无法充分发挥出作用也是一种资源的浪费。
为了满足5G网络服务与成本效益的平衡，5G网络切片技术通过统一的云化基础设施，将网络资源灵活分配，按需组网，基于5G网络虚拟出多个具有不同特点且互相隔离的逻辑子网，可以满足不同应用对网络的差异化需求。每个网络切片均由无线网、传输网、核心网切片子网组合而成，并通过切片管理系统进行统一的管理，降低网络建设成本。通过灵活的资源调度组合，为不同租户提供差异化的服务级别协议(service level agreement，SLA)保障，通过切片的独立运营运维能力，帮助租户实现业务的独立管理。
5G核心网是一种分离式的架构，传统网元被拆分为多个NF，以软件化、模块化和服务化的方式构建网络。因为符合SBA服务化架构，各个NF是独立自治的，无论是新增、升级和改造都不会妨碍其他NF。
创建5G核心网切片子网实例的方式包括共享NF方式或新建NF方式，共享NF方式是指在已经部署的NF中选择满足需求的NF，在每个NF上切分出资源用于创建新的核心网切片子网实例；新建NF方式是指在数据中心上，按照需求创建新的NF，新的NF用于创建新的核心网切片子网实例。
为了便于理解本申请，下面将对本申请涉及到的一些术语定义进行介绍：
1、网络功能(network function，NF)：
5G核心网络以软件化、模块化、服务化的方式构建网络，其中，传统网元被拆分为多个网络功能。网络功能就是指通信网络中传统网元的功能被拆分后的单一通信网络功能，各个网络功能是独立自治的，无论是新增、升级还是改造都不会妨碍其他网络功能。
2、接入和移动性管理功能(access and mobility management function，AMF)：
主要支持终端的注册管理、连接性管理以及移动性管理等功能。
3、会话管理功能(session management function，SMF)：
主要支持会话建立，修改和释放等功能，此外还负责UE IP地址分配和管理、UPF选择和控制、UPF和AN节点之间的隧道维护等功能。
4、用户平面功能(user plane function，UPF)：
主要负责数据报文的分组路由和转发。
5、认证服务器功能(authentication server function，AUSF)：
支持用户的接入认证。
6、统一数据管理(unified data management，UDM)：
主要支持用户的签约管理、UE的NF的注册管理以及3GPP AKA认证的证书处理等功能。
7、策略控制功能(policy control function，PCF)：
支持统一的策略框架来管理网络行为。
8、网络切片选择功能(network slice selection function，NSSF)：
可以提供以下功能：(1)选择为UE服务的网络切片实例集；(2)确定允许的NSSAI，以及在需要时确定到签约阅的S-NSSAI的映射；(3)确定已配置的NSSAI，以及在需要时确定到签约的S-NSSAI的映射；(4)确定可能用于查询UE的AMF集，或基于配置确定候选AMF的列表(可能通过查询NRF)。
9、认证服务器功能(authentication server function，AUSF)：
负责用户鉴权数据相关的处理。
10、计费功能(charging function，CHF)：
CHF支持在线计费、离线计费和融合计费。
11、网络数据分析功能(network data analytics function，NWDAF)：
运营商管理的网络分析逻辑功能，提供负载级别分析。
12、网络业务呈现功能(network exposure function，NEF)：
负责对外开放网络数据。
本申请实施例可以应用如图1所示的5G核心网架构：
5G核心网架构包括网络仓储功能101、网络功能虚拟化编排器102、通信业务管理功能103、网络切片管理功能104、网络规划与设计功能105、网络切片子网管理功能106、网络功能管理功能107和虚拟化网络功能管理器108。
下面介绍本申请实施例5G核心网架构中每个网元的功能：
网络仓储功能(network repository function，NRF)101支持服务发现功能，从NF实例接收NF发现请求，并将发现的NF实例(被发现)的信息提供给NF实例；维护可用NF实例及其支持的服务的NF配置文件。
网络功能虚拟化编排器(network functions virtualization orchestrator，NFVO)102负责网络业务、VNF与资源的总体管理，是整个NFV架构的控制核心。
通信业务管理功能(communication service management function，CSMF)103负责翻译通信业务需求到网络切片需求的切片管理逻辑功能。
网络切片管理功能(network slice management function，NSMF)104负责管理和编 排网络切片实例，分解网络切片子网需求的切片管理逻辑功能。
网络规划与设计功能(network planning&design function，NPDF)105提供了NSSI规划和网络及业务参数设计的功能，NPDF的NSSI规划功能嵌入在切片创建的流程中。其中NSSI规划功能包括NSSI拓扑规划功能和NSSI资源评估功能。NSSI规划功能以切片子网实例需求为输入，结合现网收集的NF和DC信息，通过自动规划过程，给出NSSI的规划结果，即NSSI拓扑定义、可部署性评估结果、资源需求等。
网络切片子网管理功能(network slice subnet management function，NSSMF)106负责管理和编排网络切片子网实例的切片管理逻辑功能。
网络功能管理功能(network function management function，NFMF)107负责网络功能的故障管理、配置管理、计费管理、性能管理和安全管理。
虚拟化网络功能管理器(virtualize network function manager，VNFM)108负责VNF的资源及生命周期等相关管理，如网元的实例化、扩容与缩容等功能。
基于上述对5G核心网架构中网元功能的介绍，下面对各个网元之间的交互过程进行介绍：
(1)NPDF105预先从NRF101获取已部署NF集合和已部署NF配置信息；
(2)NPDF105预先从NFVO102获取已部署DC集合和已部署DC配置信息；
(3)CSMF103向NSMF104发送创建逻辑网络的网络功能(network slice instance，NSI)请求，创建NSI请求中携带服务配置信息ServiceProfile；
(4)NSMF104收到创建NSI请求后，解析服务配置信息ServiceProfile参数并获得NSSI的需求，并发起创建NSSI请求，携带切片配置信息SliceProfile参数；
(5)NSSMF106向NPDF105发起逻辑网络子网的网络功能(network slice subnet instance，NSSI)规划请求，携带NSSI的需求，NSSI需求中可以携带网络及业务参数设计请求；
(6)NPDF105生成NSSI规划结果，基于NSSI规划结果生成切片的拓扑构成和相关的业务参数配置；
(7)NSSMF106向NFMF107发送共享NF的计划配置信息，由NFMF107进行管理；
(8)NSSMF106向NFVO102发送NS创建请求，携带NSD/VNFD；
(9)如果是共享NF方式，NSSMF106向NFMF107发起切片配置请求，完成切片开通的过程；
(10)如果是新建NF方式，NFVO102向VNFM108发起VNF实例化请求，完成切片开通的过程。
基于上述5G核心网架构，首先对本申请实施例中NPDF逻辑单元的内部处理方法进行介绍：
本申请实施例中，NPDF在确定了服务需求信息后，需要根据不同的需求选择目标NF或目标DC，并且根据目标NF和目标DC确定切片计划配置信息。
需要说明的是，当服务需求信息中的资源共享等级信息指示切片创建方式为共享NF时，NPDF从已部署NF集合中筛选满足需求的目标NF集合，当服务需求信息中的资源共享 等级信息指示切片创建方式为新建NF时，NPDF从已部署DC集合中筛选满足需求的目标DC集合，在目标DC集合上创建目标NF集合，下面分别进行说明：
一、当切片创建方式为共享NF时，NPDF从已部署NF集合中确定目标NF集合：
本实施例中，NPDF根据服务需求信息从已部署NF集合中筛选满足需求的目标NF集合，再根据服务需求信息和目标NF集合确定目标NF集合的切片计划配置信息。
需要说明的是，目标NF集合包括控制面NF集合、也可以包括其他类型的NF集合，例如用户面NF集合，具体此处不做限定。
在实际应用中，目标NF集合包括控制面NF集合和用户面NF集合，在已部署NF集合中筛选满足需求的控制面NF集合和用户面NF集合可以通过不同的方式进行，下面分别进行说明：
1、NPDF从已部署NF集合中确定控制面NF集合并确定切片计划配置信息：
本实施例中，NPDF根据切片服务区域信息和NF实际负载信息确定属于控制面的目标NF集合并生成基于目标NF集合的切片子网的计划配置信息。
需要说明的是，本实施例中，目标NF集合为控制面NF集合。
请参阅图2，本申请实施例中网络切片规划的方法实施例包括：
201、接收拓扑规划请求，拓扑规划请求中携带切片配置信息，切片配置信息包括切片服务区域信息、资源共享等级信息和切片容量需求信息。
NPDF接收其他网络设备发送的拓扑规划请求，拓扑规划请求中携带切片配置信息，切片配置信息包括切片服务区域信息、资源共享等级信息和切片容量需求信息。切片服务区域信息、资源共享等级信息和切片容量需求信息的定义如下表1所示：
表1
属性 定义
切片服务区域 切片子网实例能够提供服务的地理范围
切片容量需求信息 切片子网实例对静态容量的总需求
资源共享等级信息 NF的隔离性，即NF的资源由几个切片子网实例共享。
资源共享等级信息用于指示核心网切片子网的创建方式是共享NF方式或新建NF方式，本实施例中，资源共享等级信息指示核心网切片子网的创建方式是共享NF方式。
202、接收已部署NF集合和已部署NF集合配置信息。
NPDF接收其他网络设备发送的已部署NF集合和已部署NF集合配置信息，已部署NF集合配置信息包括NF服务区域信息和NF实际负载信息。NF服务区域信息和NF实际负载信息的定义如下表2所示：
表2
属性 定义
NF服务区域信息 已部署NF能够提供服务的地理范围
NF实际负载信息 已部署NF中每个NF的实际负载
203、根据切片服务区域信息确定第一NF集合。
NPDF根据切片服务区域信息确定需要创建的切片能够提供服务的地理范围需求信息， 根据地理范围需求信息从已部署NF集合中选择满足地理范围需求的第一NF集合。
204、根据NF类型从第一NF集合中确定第一控制面NF集合。
已部署NF集合配置信息中包括NF类型标识，NF类型标识表示已部署NF集合中每个NF的具体类型。NPDF根据NF类型标识在第一NF集合中筛选属于控制面的第一控制面NF集合。
需要说明的是，控制面NF包括AMF，也可以包括其他控制面NF，例如SMF、PCF、NSSF、CHF、NWDAF、AUSF、UDM或NEF，具体此处不做限定。
205、根据NF实际负载信息从第一控制面NF集合中确定目标NF集合。
控制面NF之间在部署的过程中就设置了固定的组网关系，形成了固定搭配，第一控制面NF集合中实际是以组为单位的具有固定搭配关系的控制面NF。
NF实际负载信息指示每个NF的实际负载，也可以通过计算得到固定连接关系的每一组控制面NF的总实际负载，NPDF确定第一控制面NF集合中每组控制面NF的总实际负载信息后，筛选一组轻载的控制面NF作为目标NF集合。
206、根据容量需求信息确定目标NF集合的计划新增容量信息、计划新增虚拟资源信息和计划新增DCGW带宽信息。
计划新增容量信息、计划新增虚拟资源信息和计划新增DCGW带宽信息的定义如下表3所示：
表3
属性 定义
计划新增容量信息 目标NF集合中每个NF计划新增的静态容量
计划新增虚拟资源信息 基于目标NF集合的切片子网实例计划新增的虚拟资源
计划新增DCGW带宽信息 基于目标NF集合的切片子网实例计划新增的DCGW带宽
NPDF将容量需求信息指示的切片子网实例的静态容量总需求分解到目标NF集合中的每个NF上，考虑一定比例的冗余容量，得到目标NF集合的计划新增容量信息。
NPDF通过对每个终端用户在运行过程中产生的大量业务流程进行摸底测试，得到业务流程的原子资源开销，即每个业务流程需要的容量、虚拟资源和DCGW带宽。
NPDF根据计划新增容量信息指示的容量确定该容量对应的业务流程，再通过业务流程确定目标NF集合的计划新增虚拟资源信息和计划新增DCGW带宽信息。
需要说明的是，将切片容量需求分解到控制面NF集合中的每个NF上，可以按照平均分解的方式，也可以按照其他的分解方式，例如权重分解，具体此处不做限定。
207、根据已部署NF集合配置信息确定目标NF集合的NF实例标识、DC标识和DCGW标识。
已部署NF集合配置信息包括每个NF对应的NF实例标识、DC标识和DCGW标识，NPDF从已部署NF集合中筛选了目标NF集合后，需要确定目标NF集合对应的NF实例标识、DC标识和DCGW标识。
208、发送拓扑规划响应，携带切片计划配置信息。
NPDF向其他网络设备发送拓扑规划响应，拓扑规划响应中携带切片计划配置信息，切 片计划配置信息包括目标NF集合、NF实例标识、DC标识、DCGW标识、计划新增容量信息、计划新增虚拟资源信息和计划新增DCGW带宽信息。
本实施例中，NPDF通过切片服务区域信息和NF实际负载信息确定属于控制面的目标NF集合，并生成基于目标NF集合的切片子网的计划配置信息，完成了切片子网实例所需要的计划配置信息的在线自动规划。
2、NPDF从已部署NF集合中确定用户面NF集合并确定切片计划配置信息：
本实施例中，NPDF根据切片服务区域信息、切片容量需求信息、NF部署位置、业务可用性信息、可靠性信息和NF实际负载信息确定属于用户面的目标NF集合并生成基于目标NF集合的切片子网的计划配置信息。
需要说明的是，本实施例中，目标NF集合为用户面NF集合。
请参阅图3，本申请实施例中网络切片规划的方法实施例包括：
301、接收拓扑规划请求，携带切片服务区域信息、切片容量需求信息、NF部署位置、切片性能需求信息、业务可用性信息、可靠性信息和资源共享等级信息。
NPDF接收其他网络设备发送的拓扑规划请求，拓扑规划请求中携带切片配置信息，切片配置信息包括切片服务区域信息、资源共享等级信息、切片容量需求信息、NF部署位置、切片性能需求信息、业务可用性信息和可靠性信息。其中，切片服务区域信息、资源共享等级信息和切片容量需求信息的定义见表1；NF部署位置、切片性能需求信息、业务可用性信息和可靠性信息的定义如下表4所示：
表4
Figure PCTCN2021115219-appb-000001
其中，切片性能需求信息指示的网络性能包括的信息如下表5所示，需要说明的是，下表4中仅为网络性能所包含信息的一种例子，在实际应用中，网络性能中也包括其他信息，例如端到端时延或抖动不存在，具体此处不做限定：
表5
属性 定义
e2eLatency 端到端时延(ms)
jitter 抖动(us)
expDataRate 用户体验速率(Kbps)
本实施例中，资源共享等级信息指示核心网切片子网的创建方式是共享NF方式。
302、接收已部署NF集合和已部署NF集合配置信息。
NPDF接收其他网络设备发送的已部署NF集合和已部署NF集合配置信息，已部署NF集合配置信息包括NF服务区域信息、NF地理层级信息、NF测量性能信息、NF规格信息和NF实际负载信息。其中，NF服务区域信息和NF实际负载信息的定义见表2；NF地理层级信息、NF测量性能信息和NF规格信息的定义如下表6所示：
表6
Figure PCTCN2021115219-appb-000002
303、根据切片服务区域信息确定第一NF集合。
本实施例中的步骤303与前述图2所示实施例中的步骤203类似，此处不再赘述。
304、根据NF类型从第一NF集合中确定第一用户面NF集合。
NPDF根据NF类型标识在第一NF集合中筛选属于用户面的第一用户面NF集合。
需要说明的是，用户面NF包括UPF，还可以包括未来出现的新的用户面NF，具体此处不做限定。
305、根据NF部署位置从第一用户面NF集合中确定第二用户面NF集合。
NPDF根据NF部署位置指示的用户面NF的部署位置，确定用户面NF的部署位置所属的地理层级，根据地理层级需求从第一用户面NF集合中筛选出满足地理层级需求的第二用户面NF集合。
306、根据切片性能需求信息从第二用户面NF集合中确定第三用户面NF集合。
NPDF根据切片性能需求信息指示的切片子网实例的网络性能需求，确定切片子网实例中每个NF的网络性能需求，根据NF性能需求信息从第二用户面NF集合中筛选满足网络性能需求的第三用户面NF集合。
307、根据业务可用性信息和可靠性信息确定NF需求数量。
用户面NF没有既定的固定组网搭配关系，是离散的，需要从一堆离散的用户面NF集合中确定可以组成逻辑网路的以组为单位的具有固定搭配关系的用户面NF集合。
NPDF根据业务可用性信息和可靠性信息确定第三用户面NF集合中NF之间的固定组网搭配关系，在确定固定组网搭配关系的同时，确定了一组符合固定组网搭配关系的NF需求数量。
308、根据容量需求信息和NF需求数量确定新增容量需求信息。
NPDF根据容量需求信息指示的切片子网实例的总静态容量需求和NF需求数量，确定当切片子网实例中NF的数量为NF需求数量时，每个NF的新增容量需求信息。
309、根据NF需求数量和新增容量需求信息从第三用户面NF集合中确定第四用户面NF集合。
NPDF根据NF需求数量和新增容量需求信息，从第三用户面NF集合中筛选出NF规格满足新增容量需求的第四用户面NF集合。
310、根据新增容量需求信息确定新增虚拟资源需求信息和新增DCGW带宽需求信息。
本实施例中的步骤310与前述图2所示实施例中的步骤206类似，此处不再赘述。
311、根据新增虚拟资源需求信息和新增DCGW带宽需求信息从第四用户面NF集合中确定第五用户面NF集合。
NPDF根据新增虚拟资源需求信息指示的每个NF对应的DC所需要的虚拟资源，从第四用户面NF集合筛选满足虚拟资源需求的第五用户面NF集合。
312、根据NF实际负载信息确定目标NF集合。
313、根据新增容量需求信息、新增虚拟资源需求信息、新增DCGW带宽需求信息确定目标NF集合的计划新增容量信息、计划新增虚拟资源信息、计划新增DCGW带宽信息。
314、根据已部署NF集合配置信息确定目标NF集合的NF实例标识、DC标识和DCGW标识。
315、发送拓扑规划响应，携带切片计划配置信息。
本实施例中的步骤312至315与前述图2所示实施例中的步骤205至208类似，此处不再赘述。
本实施例中，NPDF根据切片服务区域信息、切片容量需求信息、NF部署位置、业务可用性信息、可靠性信息和NF实际负载信息确定属于用户面的目标NF集合并生成基于目标NF集合的切片子网的计划配置信息，完成了切片子网实例所需要的计划配置信息的在线自动规划。
二、当切片创建方式为新建NF时，NPDF从已部署DC集合中确定目标DC集合，根据目标DC集合确定目标NF集合：
本实施例中，NPDF根据服务需求信息从已部署DC集合中筛选满足需求的目标DC集合，再根据服务需求信息确定目标NF集合和切片计划配置信息。
需要说明的是，目标DC集合包括中心区DC集合、也可以包括其他类型的DC集合，例如边缘区DC集合，具体此处不做限定。
在实际应用中，目标DC集合包括中心区DC集合和边缘区DC集合，在已部署DC集合中筛选满足需求的中心区DC集合和边缘区DC集合可以通过不同的方式进行，下面分别进行说明：
1、NPDF从已部署DC集合中确定中心区DC集合并确定中心区DC集合对应的控制面NF集合和切片计划配置信息：
本实施例中，NPDF根据切片服务区域信息、容量需求信息、业务可用性信息和可靠性信息确定属于中心区的目标DC集合，根据目标DC集合生成属于控制面的目标NF集合，并生成基于目标NF集合的切片子网的计划配置信息。
需要说明的是，本实施例中，目标NF集合为控制面NF集合，目标DC集合为中心区DC集合。
请参阅图4，本申请实施例中网络切片规划的方法实施例包括：
401、接收拓扑规划请求，携带切片服务区域信息、切片容量需求信息、业务可用性信息、可靠性信息和资源共享等级信息。
本实施例中的步骤401与前述图3所示实施例中的步骤301类似，此处不再赘述。
本实施例中，资源共享等级信息指示核心网切片子网的创建方式是新建NF方式。
402、接收已部署DC集合和已部署DC集合配置信息。
NPDF接收其他网络设备发送的已部署DC集合和已部署DC集合配置信息，已部署DC集合配置信息包括DC服务区域信息、DC资源使用信息、DC规格能力信息、反亲和要求信息和DC地理层级信息。DC服务区域信息、DC资源使用信息和DC地理层级信息的定义如下表7所示：
表7
Figure PCTCN2021115219-appb-000003
403、根据切片服务区域信息确定第一DC集合。
本实施例中的步骤403与前述图3示实施例中的步骤303类似，此处不再赘述。
404、根据DC地理层级信息从第一DC集合中确定第一中心区DC集合。
每个DC都有所处的地理层级，处于不同地理层级的DC具有不同级别的能力，一般处于省级或市级的DC称为中心区DC，处于区县级或客户机房的DC称为边缘区DC，但中心区DC和边缘区DC的划分不是绝对的，需要根据实际需求进行定义。
根据DC地理层级信息指示的DC所处的地理层级从第一DC集合中确定第一中心区DC集合。
405、根据业务可用性信息和可靠性信息确定NF需求数量。
406、根据容量需求信息和NF需求数量确定新增容量需求信息。
407、根据NF需求数量和新增容量需求信息从第一中心区DC集合中确定第二中心区DC集合。
408、根据新增容量需求信息确定新增虚拟资源需求信息和新增DCGW带宽需求信息。
409、根据新增虚拟资源需求信息和新增DCGW带宽需求信息从第二中心区DC集合中确定第三中心区DC集合。
本实施例中的步骤405至409与前述图3示实施例中的步骤307至311类似，此处不再赘述。
410、根据DC资源使用信息和反亲和要求信息确定目标DC集合。
NPDF根据DC资源使用信息指示的每个DC上已经分配的容量，从第三中心区DC集合 中筛选一组轻载的DC，并结合DC之间的反亲和要求，从轻载的DC中确定安全性较高的目标DC集合。
411、根据新增容量需求信息和目标DC集合确定目标NF集合和计划新增容量信息。
NPDF在确定了目标DC集合后，根据新增容量需求指示的每个NF的容量需求，确定目标DC集合中每个DC集合需要创建的容量，得到目标NF集合和目标NF集合中每个NF的计划新增容量需求信息。
412、根据新增虚拟资源需求信息和新增DCGW带宽需求信息确定目标NF集合的计划新增虚拟资源信息和计划新增DCGW带宽信息。
413、根据已部署NF集合配置信息确定目标NF集合的NF实例标识、DC标识和DCGW标识。
414、发送拓扑规划响应，携带切片计划配置信息。
本实施例中的步骤412至414与前述图3示实施例中的步骤313至315类似，此处不再赘述。
本实施例中，NPDF根据服务需求信息从已部署DC集合中筛选满足需求的目标DC集合，再根据服务需求信息确定目标NF集合和切片计划配置信息，完成了切片子网实例所需要的计划配置信息的在线自动规划。
2、NPDF从已部署DC集合中确定边缘区DC集合并确定边缘区DC集合对应的用户面NF集合和切片计划配置信息：
本实施例中，NPDF根据切片服务区域信息、切片容量需求信息、NF部署位置、切片性能需求信息、业务可用性信息和可靠性信息确定属于边缘区的目标DC集合，根据目标DC集合生成属于用户面的目标NF集合，并生成基于目标NF集合的切片子网的计划配置信息。
需要说明的是，本实施例中，目标NF集合为用户面NF集合，目标DC集合为边缘区DC集合。
请参阅图5，本申请实施例中网络切片规划的方法实施例包括：
501、接收拓扑规划请求，携带切片服务区域信息、切片容量需求信息、NF部署位置、切片性能需求信息、业务可用性信息、可靠性信息和资源共享等级信息。
本实施例中的步骤501与前述图3所示实施例中的步骤301类似，此处不再赘述。
502、接收已部署DC集合和已部署DC集合配置信息。
NPDF接收其他网络设备发送的已部署DC集合和已部署DC集合配置信息，已部署DC集合配置信息包括DC服务区域信息、DC资源使用信息、DC规格能力信息、反亲和要求信息、DC测量性能信息和DC地理层级信息。DC服务区域信息、DC资源使用信息、DC规格能力信息、反亲和要求信息和DC地理层级信息的定义见表7；DC测量性能信息的定义如下表8所示：
表8
Figure PCTCN2021115219-appb-000004
503、根据切片服务区域信息确定第一DC集合。
504、根据地理层级信息从第一DC集合中确定第一边缘区DC集合。
本实施例中的步骤503至504与前述图4所示实施例中的步骤403至404类似，此处不再赘述。
505、根据NF部署位置从第一边缘区DC集合中确定第二边缘区DC集合。
506、根据切片性能需求信息从第二边缘区DC集合中确定第三边缘区DC集合。
本实施例中的步骤505至506与前述图3所示实施例中的步骤305至306类似，此处不再赘述。
507、根据业务可用性信息和可靠性信息确定NF需求数量。
508、根据容量需求信息和NF需求数量确定新增容量需求信息。
509、根据NF需求数量和新增容量需求信息从第三边缘区DC集合中确定第四边缘区DC集合。
510、根据新增容量需求信息确定新增虚拟资源需求信息和新增DCGW带宽需求信息。
511、根据新增虚拟资源需求信息和新增DCGW带宽需求信息从第四边缘区DC集合中确定第五边缘区DC集合。
512、根据DC资源使用信息确定目标DC集合。
513、根据新增容量需求信息和目标DC集合确定目标NF集合和计划新增容量信息。
514、根据新增虚拟资源需求信息和新增DCGW带宽需求信息确定目标NF集合的计划新增虚拟资源信息和计划新增DCGW带宽信息。
515、根据已部署NF集合配置信息确定目标NF集合的NF实例标识、DC标识和DCGW标识。
516、发送拓扑规划响应，携带切片计划配置信息。
本实施例中的步骤507至516与前述图4所示实施例中的步骤405至414类似，此处不再赘述。
本实施例中，NPDF根据切片服务区域信息、切片容量需求信息、NF部署位置、切片性能需求信息、业务可用性信息和可靠性信息确定属于边缘区的目标DC集合，根据目标DC集合生成属于用户面的目标NF集合，并生成基于目标NF集合的切片子网的计划配置信息，完成了切片子网实例所需要的计划配置信息的在线自动规划。
基于上述5G核心网架构和NPDF逻辑单元的内部实现方法，接下来对本申请实施例中网元之间的交互过程进行介绍，请参阅图6：
本实施例中，NPDF可以单独配置为一个网元，也可以按照其他方式配置，例如NPDF配置在NSSMF中，具体此处不做限定。本实施例仅以NPDF单独配置为一个网元为例进行介绍：
601、NPDF接收NRF发送的已部署NF列表。
NPDF接收NRF发送的已部署NF列表，已部署NF列表包括已部署NF集合和已部署NF配置信息，已部署NF配置信息中包括的信息如下表9所示：
需要说明的是，下表9中仅为已部署NF列表所包含信息的一种例子，在实际应用中，已部署NF列表中也包括其他信息，例如NF地理层级信息或NF状态信息不存在，具体此处不做限定。
表9
Figure PCTCN2021115219-appb-000005
其中，NF所属NSSI信息中包含的信息如下表10所示：
表10
参数中文名称 参数英文名称 定义
NSSI标识 nSSIId 请求创建的NSSI的唯一标识
NF静态容量信息 sliceCapacity NF为切片子网实例分配的静态容量值
602、NPDF接收NFVO发送的已部署DC列表。
NPDF接收NFVO发送的已部署DC列表，已部署DC列表包括已部署DC集合和已部署DC配置信息，已部署DC配置信息中包括的信息如下表11所示：
需要说明的是，下表11中仅为已部署DC列表所包含信息的一种例子，在实际应用 中，已部署DC列表中也包括其他信息，例如第一DC标识或DC服务区域信息不存在，具体此处不做限定。
表11
Figure PCTCN2021115219-appb-000006
需要说明的是，步骤602可以在步骤601之后执行，也可以在步骤601之前执行，具体此处不做限定。
603、NSMF向NSSMF发送NSSI创建请求。
NSMF向NSSMF发起创建NSSI请求，携带切片子网实例标识、切片配置信息及切片服务区域信息。切片配置信息中包括的信息如下表12所示：
需要说明的是，下表12中仅为切片配置信息所包含信息的一种例子，在实际应用中，切片配置信息中也包括其他信息，例如覆盖范围跟踪区列表信息或NF部署位置不存在，具体此处不做限定。
表12
Figure PCTCN2021115219-appb-000007
604、NSSMF向NPDF发送拓扑规划请求。
NSSMF向NPDF发起切片拓扑规划请求，携带切片配置信息和切片服务区域信息。
需要说明的是，切片服务区域可以单独配置，也可以按其他方式配置，例如配置在切片配置信息中，具体此处不做限定。
605、NPDF判断部署类型。
606、NPDF根据部署类型进行NF选择或DC选择。
607、NPDF根据切片容量需求信息进行容量分解。
608、NPDF的拓扑规划单元向NPDF的资源评估单元发送资源评估请求。
609、NPDF根据新增容量需求信息进行资源评估。
610、NPDF的资源评估单元向NPDF的拓扑规划单元发送资源评估结果。
本实施例中，步骤605至步骤610中的详细内容与图2至图4所示实施例中的内容类似，此处不再赘述。
611、NPDF向NSSMF发送拓扑规划响应。
在NPDF根据切片配置信息完成拓扑规划和资源评估后，NPDF向NSSMF发送拓扑规划响应，拓扑规划响应中携带用于切片子网实例部署的切片计划配置信息。切片计划配置信息中包含的信息如下表13所示：
表13
Figure PCTCN2021115219-appb-000008
612、NSSMF、NPDF、NFVO和NRF进行NSSI部署。
NSSMF、NPDF、NFVO和NRF基于拓扑规划响应中携带的计划配置信息进行NSSI部署。
613、NSSMF向NSMF发送NSSI创建响应。
NSSMF向NSMF发送NSSI创建响应，NSSI创建响应中携带了新创建NSSI的配置信息。
结合上述介绍，下面介绍本申请实施例的一个应用场景，请参阅图7：
基于上述对NPDF在共享NF方式和新建NF方式下对控制面NF、用户面NF、中心区DC 和边缘区DC的选择以及生成切片计划配置信息的过程的介绍，在实际应用中，可以对以上方式进行组合以达到最优效果。请参阅图7，下面对本申请实施例提供的网络切片规划的方法的一个应用场景进行介绍：
701、根据隔离性确定部署方式。
NPDF根据切片配置信息中包含的资源共享等级信息判断切片网络子网的部署方式，资源共享等级信息用于指示，创建的NSSI是需要独占NF，或是与其他NSSI共享NF。
702、判断切片子网实例的创建方式是共享NF方式或新建NF方式。
NPDF判断切片子网实例的创建方式是共享NF方式或新建NF方式，当切片子网实例的创建方式是共享NF方式时，执行步骤603；当切片子网实例的创建方式是新建NF方式时，执行步骤612。
703、根据TAIList匹配NF/NF Set。
NPDF接收网络设备发送的覆盖范围跟踪区列表信息，根据覆盖范围跟踪区列表信息进行匹配，如果匹配成功，则执行步骤605；如果匹配失败，则执行步骤604。
本实施例中，在NRF中存储的已部署NF数据中，含有每个NF配置的跟踪区列表信息，用于表示每个NF服务的用户设备。NSMF接收由CSMF发送创建切片网络请求中携带的服务配置信息，该服务配置信息中包含覆盖范围信息。NSMF解析覆盖范围信息后，将覆盖范围信息和跟踪区列表信息进行推导得到了覆盖范围跟踪区列表信息。NSMF推导覆盖范围跟踪区列表信息的方法分为两种，一种是NSMF复用现网已经分配的跟踪区列表信息进行推导，另一种是NSMF在现网上叠加跟踪区列表信息。如果是采用复用现网的推导方式得到的覆盖范围跟踪区列表信息称为现网复用覆盖范围跟踪区列表信息，如果是采用在现网上叠加跟踪区列表信息得到的覆盖范围跟踪区列表信息称为现网叠加覆盖范围跟踪区列表信息。使用现网复用覆盖范围跟踪区列表信息在已部署NF集合中匹配到第一NF集合，而使用现网叠加覆盖范围跟踪区列表信息进行匹配则会导致匹配失败。
704、根据服务区域匹配NF/NF Set。
本实施例中的步骤604与前述图2所示实施例中的步骤204类似，此处不再赘述。
705、判断是控制面NF还是用户面NF。
706、根据资源均衡优选具有固定组网关系的NF组。
707、根据NF Set分解规格。
本实施例中的步骤605至607的详细内容与前述图2所示实施例中的内容类似，此处不再赘述。
708、根据UPF部署位置筛选UPF。
709、根据perfReq筛选UPF。
710、根据可靠性确定UPF数量和规格。
711、根据资源均衡优选具有固定组网关系的UPF组。
本实施例中的步骤608至611的详细内容与前述图3所示实施例中的内容类似，此处不再赘述。
需要说明的是，步骤608至611在实际应用中是一个迭代循环的过程，即可以根据不 同的需求从不同的角度多次筛选以达到最优选择。例如，可以根据NF数量、NF新增容量信息、新增容量需求信息和NF实际负载信息进行循环筛选。
712、根据服务区域匹配DC集合。
713、判断是控制面NF还是用户面NF。
714、根据可靠性确定NF数量和规格。
715、根据资源均衡优选DC集合。
本实施例中的步骤712至715的详细内容与前述图4所示实施例中的内容类似，此处不再赘述。
需要说明的是，714至715在实际应用中是一个迭代循环的过程，即可以根据不同的需求从不同的角度多次筛选以达到最优选择。例如，可以根据反亲和性要求信息、NF数量、新增容量需求信息和DC资源使用信息等方面进行循环筛选。
716、根据UPF部署位置筛选DC集合。
717、根据perfReq筛选UPF。
718、根据可靠性确定NF数量和规格。
719、根据资源均衡优选DC集合。
本实施例中的步骤716至719的详细内容与前述图5所示实施例中的内容类似，此处不再赘述。
需要说明的是，716至719在实际应用中是一个迭代循环的过程，即可以根据不同的需求从不同的角度多次筛选以达到最优选择。例如，可以根据反亲和性要求信息、NF数量、新增容量需求信息和DC资源使用信息等方面进行循环筛选。
720、确定切片计划配置信息。
本实施例中步骤720的详细内容与前述图2至图4所示实施例中的内容类似，此处不再赘述。
下面对本申请实施例中的第一网络设备进行描述，请参阅图8，本申请实施例中第一网络设备包括接收单元801、确定单元802以及发送单元803。
接收单元801，用于接收来自于第二网络设备的拓扑规划请求，拓扑规划请求携带切片配置信息；
确定单元802，用于根据切片配置信息确定切片计划配置信息；
发送单元803，用于向第二网络设备发送拓扑规划响应，拓扑规划响应中携带切片计划配置信息。
在上述图8所示的第一网络设备的基础上，
确定单元802，具体用于当切片计划配置信息包括目标NF集合或目标DC集合时，根据切片配置信息确定服务需求信息，服务需求信息包括地理范围需求信息、地理层级需求信息、NF性能需求信息、新增容量需求信息、新增数据中心网关DCGW带宽需求信息和NF需求数量中的至少一种；
确定单元802，还用于根据服务需求信息确定目标NF集合或目标DC集合。
确定单元802，具体用于当切片配置信息包括切片服务区域信息，服务需求信息包括 地理范围需求信息时，根据切片服务区域信息确定地理范围需求信息。
确定单元802，具体用于当切片配置信息包括NF部署位置，服务需求信息包括地理层级需求信息时，根据NF部署位置确定地理层级需求信息。
确定单元802，具体用于当切片配置信息包括切片性能需求信息，服务需求信息包括NF性能需求信息时，根据切片性能需求信息确定NF性能需求信息。
确定单元802，具体用于当切片配置信息包括业务可用性信息、可靠性信息和容量需求信息，服务需求信息包括新增容量需求信息和NF需求数量时，根据业务可用性信息和可靠性信息确定NF需求数量；
确定单元802，还用于根据容量需求信息和NF需求数量确定新增容量需求信息。
确定单元802，具体用于当切片配置信息包括业务可用性信息、可靠性信息和容量需求信息，服务需求信息包括新增容量需求信息、新增虚拟资源需求信息和新增DCGW带宽需求信息时，根据新增容量需求信息确定新增虚拟资源需求信息和新增DCGW带宽需求信息。
确定单元802，具体用于当切片计划配置信息包括计划新增容量信息时，根据新增容量需求信息和目标NF集合或目标DC集合确定计划新增容量信息。
确定单元802，具体用于当切片计划配置信息包括计划新增容量信息、计划新增虚拟资源信息和计划新增DCGW信息时，根据新增虚拟资源需求信息和目标NF集合或目标DC集合确定计划新增虚拟资源信息；
确定单元802，还用于根据新增DCGW带宽需求信息和目标NF集合或目标DC集合确定计划新增DCGW信息。
下面对本申请实施例中的第二网络设备进行描述，请参阅图9，本申请实施例中第二网络设备包括发送单元901和接收单元902。
发送单元901，用于向第一网络设备发送拓扑规划请求，拓扑规划请求中携带切片配置信息，切片配置信息包括切片服务区域信息、NF部署位置、切片性能需求信息、业务可用性信息、可靠性信息和容量需求信息中的至少一种；
接收单元902，用于接收第一网络设备发送的拓扑规划响应，拓扑规划响应中携带切片计划配置信息，切片计划配置信息包括目标NF集合或目标DC集合，计划新增容量信息、计划新增虚拟资源信息和计划新增DCGW信息中的至少一种。
图10是本申请实施例提供的一种第一网络设备结构示意图，该第一网络设备1000可以包括一个或一个以上中央处理器(central processing units，CPU)1001和存储器1005，该存储器1005中存储有一个或一个以上的应用程序或数据。
其中，存储器1005可以是易失性存储或持久存储。存储在存储器1005的程序可以包括一个或一个以上模块，每个模块可以包括对服务器中的一系列指令操作。更进一步地，中央处理器1001可以设置为与存储器1005通信，在第一网络设备1000上执行存储器1005中的一系列指令操作。
第一网络设备1000还可以包括一个或一个以上电源1002，一个或一个以上有线或无线网络接口1003，一个或一个以上输入输出接口1004，和/或，一个或一个以上操作系 统，例如Windows Server TM，Mac OS X TM，Unix TM,Linux TM，FreeBSD TM等。
该中央处理器1001可以执行前述图2至图7所示实施例中第一网络设备所执行的操作，具体此处不再赘述。
图11是本申请实施例提供的一种第二网络设备结构示意图，该第二网络设备1100可以包括一个或一个以上中央处理器(central processing units，CPU)1101和存储器1105，该存储器1105中存储有一个或一个以上的应用程序或数据。
其中，存储器1105可以是易失性存储或持久存储。存储在存储器1105的程序可以包括一个或一个以上模块，每个模块可以包括对服务器中的一系列指令操作。更进一步地，中央处理器1101可以设置为与存储器1105通信，在第二网络设备1100上执行存储器1105中的一系列指令操作。
第二网络设备1100还可以包括一个或一个以上电源1102，一个或一个以上有线或无线网络接口1103，一个或一个以上输入输出接口1104，和/或，一个或一个以上操作系统，例如Windows Server TM，Mac OS X TM，Unix TM,Linux TM，FreeBSD TM等。
该中央处理器1101可以执行前述图2至图7所示实施例中第二网络设备所执行的操作，具体此处不再赘述。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者该技术方案的全部或部分可以体现为软件产品的形式，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。

Claims (26)

  1. 一种网络切片规划的方法，其特征在于，包括：
    第一网络设备接收来自于第二网络设备的拓扑规划请求，所述拓扑规划请求携带切片配置信息；
    所述第一网络设备根据所述切片配置信息确定切片计划配置信息；
    所述第一网络设备向所述第二网络设备发送拓扑规划响应，所述拓扑规划响应中携带所述切片计划配置信息。
  2. 根据权利要求1所述的网络切片规划的方法，其特征在于，所述切片计划配置信息包括目标网络功能NF集合或目标数据中心DC集合；
    所述第一网络设备根据所述切片配置信息确定切片计划配置信息，包括：
    所述第一网络设备根据所述切片配置信息确定服务需求信息，所述服务需求信息包括地理范围需求信息、地理层级需求信息、NF性能需求信息、新增容量需求信息、新增数据中心网关DCGW带宽需求信息和NF需求数量中的至少一种；
    所述第一网络设备根据所述服务需求信息确定所述目标NF集合或所述目标DC集合。
  3. 根据权利要求2所述的网络切片规划的方法，其特征在于，所述切片配置信息包括切片服务区域信息，所述服务需求信息包括所述地理范围需求信息；
    所述第一网络设备根据所述切片配置信息确定服务需求信息，包括：
    所述第一网络设备根据所述切片服务区域信息确定所述地理范围需求信息。
  4. 根据权利要求2所述的网络切片规划的方法，其特征在于，所述切片配置信息包括NF部署位置，所述服务需求信息包括所述地理层级需求信息；
    所述第一网络设备根据所述切片配置信息确定服务需求信息，包括：
    所述第一网络设备根据所述NF部署位置确定所述地理层级需求信息。
  5. 根据权利要求2所述的网络切片规划的方法，其特征在于，所述切片配置信息包括切片性能需求信息，所述服务需求信息包括所述NF性能需求信息；
    所述第一网络设备根据所述切片配置信息确定服务需求信息，包括：
    所述第一网络设备根据所述切片性能需求信息确定所述NF性能需求信息。
  6. 根据权利要求2所述的网络切片规划的方法，其特征在于，所述切片配置信息包括业务可用性信息、可靠性信息和容量需求信息，所述服务需求信息包括所述新增容量需求信息和所述NF需求数量；
    所述第一网络设备根据所述切片配置信息确定服务需求信息，包括：
    所述第一网络设备根据所述业务可用性信息和所述可靠性信息确定所述NF需求数量；
    所述第一网络设备根据所述容量需求信息和所述NF需求数量确定所述新增容量需求信息。
  7. 根据权利要求6所述的网络切片规划的方法，其特征在于，所述切片配置信息包括业务可用性信息、可靠性信息和容量需求信息，所述服务需求信息包括所述新增容量需求信息、所述新增虚拟资源需求信息和所述新增DCGW带宽需求信息，所述方法还包括：
    所述第一网络设备根据所述新增容量需求信息确定所述新增虚拟资源需求信息和所述 新增DCGW带宽需求信息。
  8. 根据权利要求2或6或7所述的网络切片规划的方法，其特征在于，所述切片计划配置信息包括计划新增容量信息；
    所述方法还包括：
    所述第一网络设备根据所述新增容量需求信息和所述目标NF集合或目标DC集合确定所述计划新增容量信息。
  9. 根据权利要求2或7所述的网络切片规划的方法，其特征在于，所述切片计划配置信息包括计划新增容量信息、计划新增虚拟资源信息和计划新增DCGW信息；
    所述方法还包括：
    所述第一网络设备根据所述新增虚拟资源需求信息和所述目标NF集合或目标DC集合确定所述计划新增虚拟资源信息；
    所述第一网络设备根据所述新增DCGW带宽需求信息和所述目标NF集合或目标DC集合确定所述计划新增DCGW信息。
  10. 一种网络切片规划的方法，其特征在于，包括：
    第二网络设备向第一网络设备发送拓扑规划请求，所述拓扑规划请求中携带切片配置信息，所述切片配置信息包括切片服务区域信息、NF部署位置、切片性能需求信息、业务可用性信息、可靠性信息和容量需求信息中的至少一种；
    所述第二网络设备接收所述第一网络设备发送的拓扑规划响应，所述拓扑规划响应中携带切片计划配置信息，所述切片计划配置信息包括目标NF集合或目标DC集合，计划新增容量信息、计划新增虚拟资源信息和计划新增DCGW信息中的至少一种。
  11. 一种第一网络设备，其特征在于，包括：
    接收单元，用于接收来自于第二网络设备的拓扑规划请求，所述拓扑规划请求携带切片配置信息；
    确定单元，用于根据所述切片配置信息确定切片计划配置信息；
    发送单元，用于向所述第二网络设备发送拓扑规划响应，所述拓扑规划响应中携带所述切片计划配置信息。
  12. 根据权利要求11所述的第一网络设备，其特征在于，所述切片计划配置信息包括目标网络功能NF集合或目标数据中心DC集合；
    所述确定单元，具体用于根据所述切片配置信息确定服务需求信息，所述服务需求信息包括地理范围需求信息、地理层级需求信息、NF性能需求信息、新增容量需求信息、新增数据中心网关DCGW带宽需求信息和NF需求数量中的至少一种；
    所述确定单元，还用于根据所述服务需求信息确定所述目标NF集合或所述目标DC集合。
  13. 根据权利要求12所述的第一网络设备，其特征在于，所述切片配置信息包括切片服务区域信息，所述服务需求信息包括所述地理范围需求信息；
    所述确定单元，具体用于根据所述切片服务区域信息确定所述地理范围需求信息。
  14. 根据权利要求12所述的第一网络设备，其特征在于，所述切片配置信息包括NF部 署位置，所述服务需求信息包括所述地理层级需求信息；
    所述确定单元，具体用于根据所述NF部署位置确定所述地理层级需求信息。
  15. 根据权利要求12所述的第一网络设备，其特征在于，所述切片配置信息包括切片性能需求信息，所述服务需求信息包括所述NF性能需求信息；
    所述确定单元，具体用于根据所述切片性能需求信息确定所述NF性能需求信息。
  16. 根据权利要求12所述的第一网络设备，其特征在于，所述切片配置信息包括业务可用性信息、可靠性信息和容量需求信息，所述服务需求信息包括所述新增容量需求信息和所述NF需求数量；
    所述确定单元，具体用于根据所述业务可用性信息和所述可靠性信息确定所述NF需求数量；
    所述确定单元，还用于根据所述容量需求信息和所述NF需求数量确定所述新增容量需求信息。
  17. 根据权利要求16所述的第一网络设备，其特征在于，所述切片配置信息包括业务可用性信息、可靠性信息和容量需求信息，所述服务需求信息包括所述新增容量需求信息、所述新增虚拟资源需求信息和所述新增DCGW带宽需求信息，
    所述确定单元，具体用于根据所述新增容量需求信息确定所述新增虚拟资源需求信息和所述新增DCGW带宽需求信息。
  18. 根据权利要求12或16或17所述的第一网络设备，其特征在于，所述切片计划配置信息包括计划新增容量信息；
    所述确定单元，具体用于根据所述新增容量需求信息和所述目标NF集合或目标DC集合确定所述计划新增容量信息。
  19. 根据权利要求12或17所述的第一网络设备，其特征在于，所述切片计划配置信息包括计划新增容量信息、计划新增虚拟资源信息和计划新增DCGW信息；
    所述确定单元，具体用于根据所述新增虚拟资源需求信息和所述目标NF集合或目标DC集合确定所述计划新增虚拟资源信息；
    所述确定单元，还用于根据所述新增DCGW带宽需求信息和所述目标NF集合或目标DC集合确定所述计划新增DCGW信息。
  20. 一种第二网络设备，其特征在于，包括：
    发送单元，用于向第一网络设备发送拓扑规划请求，所述拓扑规划请求中携带切片配置信息，所述切片配置信息包括切片服务区域信息、NF部署位置、切片性能需求信息、业务可用性信息、可靠性信息和容量需求信息中的至少一种；
    接收单元，用于接收所述第一网络设备发送的拓扑规划响应，所述拓扑规划响应中携带切片计划配置信息，所述切片计划配置信息包括目标NF集合或目标DC集合，计划新增容量信息、计划新增虚拟资源信息和计划新增DCGW信息中的至少一种。
  21. 一种第一网络设备，其特征在于，包括：
    处理器、存储器、输入输出设备以及总线；
    所述处理器、存储器、输入输出设备与所述总线相连；
    所述处理器用于执行权利要求1至9中任一项所述的方法。
  22. 一种第二网络设备，其特征在于，包括：
    处理器、存储器、输入输出设备以及总线；
    所述处理器、存储器、输入输出设备与所述总线相连；
    所述处理器用于执行权利要求10所述的方法。
  23. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中保存有程序，当所述计算机执行所述程序时，执行如权利要求1至10中任一项所述的方法。
  24. 一种计算机程序产品，其特征在于，当所述计算机程序产品在计算机上执行时，所述计算机执行如权利要求1至10中任一项所述的方法。
  25. 一种网络切片规划的系统，其特征在于，所述网络切片规划系统包括第一网络设备和第二网络设备；
    所述第一网络设备用于执行如上述权利要求1至9中任一项所述的方法，所述第二网络设备用于执行如上述权利要求10所述的方法。
  26. 一种网络切片规划的方法，其特征在于，所述方法应用于网络切片规划的系统，所述网络切片规划系统包括第一网络设备和第二网络设备；
    所述第一网络设备，用于接收来自于第二网络设备的拓扑规划请求，所述拓扑规划请求携带切片配置信息；
    所述第一网络设备，用于根据所述切片配置信息确定切片计划配置信息；
    所述第一网络设备，用于向所述第二网络设备发送拓扑规划响应，所述拓扑规划响应中携带所述切片计划配置信息。
PCT/CN2021/115219 2020-11-24 2021-08-30 网络切片规划的方法以及相关设备 WO2022110944A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011332093.XA CN114554504A (zh) 2020-11-24 2020-11-24 网络切片规划的方法以及相关设备
CN202011332093.X 2020-11-24

Publications (1)

Publication Number Publication Date
WO2022110944A1 true WO2022110944A1 (zh) 2022-06-02

Family

ID=81659886

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/115219 WO2022110944A1 (zh) 2020-11-24 2021-08-30 网络切片规划的方法以及相关设备

Country Status (2)

Country Link
CN (1) CN114554504A (zh)
WO (1) WO2022110944A1 (zh)

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107707381A (zh) * 2017-08-04 2018-02-16 北京天元创新科技有限公司 虚拟网元智能切片管理系统及方法
US20180227871A1 (en) * 2017-02-06 2018-08-09 Industrial Technology Research Institute User equipment registration method for network slice selection and network controller and network communication system using the same
CN109218047A (zh) * 2017-06-30 2019-01-15 中国移动通信有限公司研究院 网络切片处理方法及装置、通信系统及存储介质
CN109560955A (zh) * 2017-09-27 2019-04-02 华为技术有限公司 网络的部署信息确定方法及设备
CN109600755A (zh) * 2017-09-30 2019-04-09 华为技术有限公司 网络资源部署及评估的方法、和设备
CN109787803A (zh) * 2017-11-15 2019-05-21 华为技术有限公司 管理共享网络功能的方法及装置
CN109842906A (zh) * 2017-11-28 2019-06-04 华为技术有限公司 一种通信的方法、装置及系统
EP3496465A1 (en) * 2017-12-08 2019-06-12 Comcast Cable Communications, LLC User plane function selection for isolated network slice
CN110324164A (zh) * 2018-03-29 2019-10-11 华为技术有限公司 一种网络切片的部署方法及装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109600768B (zh) * 2017-09-30 2022-06-07 华为技术有限公司 网络切片的管理方法、设备及系统
US10708143B2 (en) * 2017-11-17 2020-07-07 Huawei Technologies Co., Ltd. Method and apparatus for the specification of a network slice instance and underlying information model
CN110896355B (zh) * 2018-09-12 2022-04-05 华为技术有限公司 一种网络切片的选择方法及装置

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180227871A1 (en) * 2017-02-06 2018-08-09 Industrial Technology Research Institute User equipment registration method for network slice selection and network controller and network communication system using the same
CN109218047A (zh) * 2017-06-30 2019-01-15 中国移动通信有限公司研究院 网络切片处理方法及装置、通信系统及存储介质
CN107707381A (zh) * 2017-08-04 2018-02-16 北京天元创新科技有限公司 虚拟网元智能切片管理系统及方法
CN109560955A (zh) * 2017-09-27 2019-04-02 华为技术有限公司 网络的部署信息确定方法及设备
CN109600755A (zh) * 2017-09-30 2019-04-09 华为技术有限公司 网络资源部署及评估的方法、和设备
CN109787803A (zh) * 2017-11-15 2019-05-21 华为技术有限公司 管理共享网络功能的方法及装置
CN109842906A (zh) * 2017-11-28 2019-06-04 华为技术有限公司 一种通信的方法、装置及系统
EP3496465A1 (en) * 2017-12-08 2019-06-12 Comcast Cable Communications, LLC User plane function selection for isolated network slice
CN110324164A (zh) * 2018-03-29 2019-10-11 华为技术有限公司 一种网络切片的部署方法及装置

Also Published As

Publication number Publication date
CN114554504A (zh) 2022-05-27

Similar Documents

Publication Publication Date Title
CN108293004B (zh) 用于网络切片管理的系统和方法
CN109952796B (zh) 可共享切片实例的创建及修改
US11283684B2 (en) Network slice deployment method and apparatus
US10298439B2 (en) Network functions virtualization network system and data processing method, and apparatus
US11051183B2 (en) Service provision steps using slices and associated definitions
US11146462B2 (en) Network slice management method, device, and system
CN110832827B (zh) 网络切片方法及系统
US9999030B2 (en) Resource provisioning method
US20180317134A1 (en) Nssmf nsmf interaction connecting virtual 5g networks and subnets
CN109600246B (zh) 网络切片管理方法及其装置
RU2643451C2 (ru) Система и способ виртуализации функции мобильной сети
CN107924383B (zh) 用于网络功能虚拟化资源管理的系统和方法
CN111587601A (zh) 网络切片供应及操作
EP3657861B1 (en) Deploying a network slice
CN109391490B (zh) 网络切片的管理方法和装置
CN111183614B (zh) 5g和非5g管理功能实体间的交互
WO2020036156A1 (ja) 通信制御装置、通信制御システム、通信制御方法および通信制御プログラム
WO2018210075A1 (zh) 网络控制方法、装置及网络设备
WO2023185428A1 (zh) 一种重构用户面功能网元关键服务能力的方法及通信装置
WO2022110944A1 (zh) 网络切片规划的方法以及相关设备
US10743173B2 (en) Virtual anchoring in anchorless mobile networks
Nguyen et al. Location-aware dynamic network provisioning

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21896448

Country of ref document: EP

Kind code of ref document: A1