WO2023050815A1 - 切片业务配置方法、网络设备、网络***及存储介质 - Google Patents

切片业务配置方法、网络设备、网络***及存储介质 Download PDF

Info

Publication number
WO2023050815A1
WO2023050815A1 PCT/CN2022/091257 CN2022091257W WO2023050815A1 WO 2023050815 A1 WO2023050815 A1 WO 2023050815A1 CN 2022091257 W CN2022091257 W CN 2022091257W WO 2023050815 A1 WO2023050815 A1 WO 2023050815A1
Authority
WO
WIPO (PCT)
Prior art keywords
configuration
slice
service
network element
information
Prior art date
Application number
PCT/CN2022/091257
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 WO2023050815A1 publication Critical patent/WO2023050815A1/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/02—Resource partitioning among network components, e.g. reuse partitioning
    • H04W16/10—Dynamic resource partitioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information

Definitions

  • the embodiments of the present application relate to but are not limited to the field of communication services, and in particular, relate to a slice service configuration method, network equipment, a network system, and a computer-readable storage medium.
  • the power industry realizes 5G smart grid with the help of 5G communication slicing technology, making the power network more automated and intelligent.
  • the existing 5G slice network deployment method mainly uses network slice management systems at all levels, such as Network Slice Management Function (Network Slice Management Function, NSMF), Network Slice Subnet Management Function (Network Slice Subnet Management Function, NSSMF), and network function virtualization.
  • Network Functions Virtualization Orchestrator (NFVO) and Network Function Management Function (NFMF) cooperate to complete network element resource deployment and service configuration deployment.
  • slice configuration parameters that need to be delivered from NSMF are also different. Therefore, these network elements or applications need to be arranged and managed during the application process.
  • slice data is usually manually configured on the NFMF to which network elements or applications belong, or manually organize slice configuration data on NSMF and send configuration requests to NFMF, but the configuration models of different network elements are different. This brings certain identification difficulties.
  • the error rate of configuration parameters manually obtained based on the identified configuration model will increase accordingly, which will easily lead to a decrease in the accuracy of slice service configuration.
  • Embodiments of the present application provide a slicing service configuration method, a network device, a network system, and a computer-readable storage medium.
  • the embodiment of the present application provides a slice service configuration method, including: obtaining slice configuration information corresponding to the slice service; obtaining a network element configuration template corresponding to a service network element, and the service network element and the slice Service association; obtain network element configuration data required for executing the slice service according to the slice configuration information and the network element configuration template; send the network element configuration data to the service network element.
  • the embodiment of the present application also provides a slice service configuration method, including: receiving a data acquisition instruction from the first slice management device; a network element configuration template corresponding to the service network element, so that the first slice management device obtains the network element configuration data required for executing the slice service according to the network element configuration template and the obtained slice configuration information, and Sending the network element configuration data to the service network element; wherein the slice configuration information corresponds to the slice service, and the service network element is associated with the slice service.
  • the embodiment of the present application also provides a slice service configuration method, which is applied to a network system, and the network system includes a first slice management device and a second slice management device, and the method includes: the first The slice management device obtains the slice configuration information corresponding to the slice service, and sends a data acquisition instruction to the second slice management device; the second slice management device receives the data acquisition instruction from the first slice management device, and according to The data acquisition instruction sends a network element configuration template corresponding to a service network element to the first slice management device; and the first slice management device executes according to the slice configuration information and the network element configuration template Slicing the network element configuration data required by the service, and sending the network element configuration data to the service network element.
  • the embodiment of the present application also provides a network device, including: a memory, a processor, and a computer program stored on the memory and operable on the processor, and the processor implements the above when executing the computer program.
  • a network device including: a memory, a processor, and a computer program stored on the memory and operable on the processor, and the processor implements the above when executing the computer program.
  • the embodiment of the present application also provides a network system, including: a memory, a processor, and a computer program stored in the memory and operable on the processor.
  • a network system including: a memory, a processor, and a computer program stored in the memory and operable on the processor.
  • the embodiment of the present application also provides a computer-readable storage medium, which stores computer-executable instructions, and the computer-executable instructions are used to execute the slicing service configuration method described in the first aspect and the second aspect above .
  • FIG. 1 is a schematic diagram of a network architecture for performing a slice service configuration method provided by an embodiment of the present application
  • FIG. 2 is a schematic diagram of a network architecture for performing a slice service configuration method provided by another embodiment of the present application
  • FIG. 3 is a flow chart of a slice service configuration method provided by an embodiment of the present application.
  • FIG. 4 is a flowchart of obtaining slice configuration information in a slice service configuration method provided by an embodiment of the present application
  • FIG. 5 is a flowchart of obtaining a network element configuration template in a slice service configuration method provided by an embodiment of the present application
  • FIG. 6 is a flow chart of obtaining network element configuration data in a slice service configuration method provided by an embodiment of the present application
  • FIG. 7 is a flowchart of sending network element configuration data in a slice service configuration method provided by an embodiment of the present application.
  • FIG. 8 is a flow chart of a slice service configuration method provided by another embodiment of the present application.
  • FIG. 9 is a flowchart of a slice service configuration method provided by another embodiment of the present application.
  • FIG. 10 is an execution flowchart of a slice service configuration method provided by an embodiment of the present application.
  • FIG. 11 is an execution flowchart of querying a network element configuration template provided by an embodiment of the present application.
  • FIG. 12 is an execution flowchart of querying a network element configuration template provided by another embodiment of the present application.
  • FIG. 13 is an execution flowchart of querying a network element configuration template provided by another embodiment of the present application.
  • FIG. 14 is an execution flowchart of querying a network element configuration template provided by another embodiment of the present application.
  • FIG. 15 is a flow chart of obtaining network element configuration data by the first slice management device in the slice service configuration method provided by an embodiment of the present application;
  • FIG. 16 is an execution flowchart of updating a network element configuration template provided by an embodiment of the present application.
  • Fig. 17 is an execution flowchart of updating a network element configuration template provided by another embodiment of the present application.
  • Fig. 18 is an execution flowchart of updating a network element configuration template provided by another embodiment of the present application.
  • Fig. 19 is an execution flowchart of preset configuration parameters provided by an embodiment of the present application.
  • FIG. 20 is a flow chart of sending network element configuration data by the first slice management device in the slice service configuration method provided by an embodiment of the present application;
  • Fig. 21 is an execution flowchart of returning slice configuration data provided by another embodiment of the present application.
  • Fig. 22 is an execution flow chart of reviewing slice configuration data provided by an embodiment of the present application.
  • the present application provides a slicing service configuration method, network equipment, network system, and storage medium.
  • obtaining the slicing configuration information corresponding to the slicing service and the network element configuration template corresponding to the service network element and then according to the slice configuration information and the network element
  • the configuration template obtains the network element configuration data required to execute the slicing service.
  • the slicing service is configured by using the slicing configuration information and the network element configuration template, which fully considers the relationship between the slicing service and the service network element. , which can reduce configuration errors caused by manual identification of configuration model differences, and improve the accuracy of slice service configuration.
  • FIG. 1 is a schematic diagram of a network architecture 100 for implementing a slice service configuration method provided by an embodiment of the present application.
  • the network architecture 100 includes but is not limited to: a first slice management device 110 and a second slice management device 120, wherein the first slice management device 110 and the second slice management device 120 are connected, Information exchange can be performed between the two, and through the cooperation of the two, the network element configuration data required to execute the slicing service can be sent to the corresponding service network element, so as to realize further slicing service configuration and orchestration, thereby improving the efficiency of slicing service configuration and orchestration.
  • Efficiency is mainly used for general end-to-end network slice management, and can also be applied to the slice subnet management of a certain subdomain; in another embodiment, the network architecture 100 can also be used as a general configuration function management architecture for non-slicing scenarios , applied to scenarios such as network element deployment configuration and policy configuration; in another embodiment, the network architecture 100 further includes but not limited to: a first slice service enabling device 130, wherein the first slice service enabling device 130 and In cooperation with the first slice management device 110, it can send configuration request information for the slice service to the first slice management device 110, so that the first slice management device 110 executes the configuration process related to the slice service according to the relevant configuration request information.
  • a first slice service enabling device 130 wherein the first slice service enabling device 130 and In cooperation with the first slice management device 110, it can send configuration request information for the slice service to the first slice management device 110, so that the first slice management device 110 executes the configuration process related to the slice service according to the relevant configuration request information.
  • the second slice service activation device 140 wherein the second slice service activation device 140 cooperates with the first slice management device 110, and can send configuration request information for configuring service network elements to the first slice management device 110, So that the first slice management device 110 performs operations related to the slice service delivery process according to the relevant configuration request information.
  • first slice service provisioning device 130 and the second slice service provisioning device 140 can be set in NSMF or NSSMF, but not limited to, and the two types can be the same, or they can be set separately, for example, they can be slices Life cycle management module (Network Slice Provision Management, NSPM), slice subnet life cycle management module (Network Slice Subnet Provision Management, NSSPM), etc., in specific scenarios, the two can be interoperable, that is, the first slice service opening device 130 It can be used as the second device for enabling slice services 140, and vice versa, which can reduce the cost of setting up slice services in practical applications, and at the same time achieve the technical effect of optimizing slice service configuration.
  • NSPM Network Slice Provision Management
  • NSSPM Network Slice Subnet Provision Management
  • FIG. 2 is a schematic diagram of a network architecture 100 provided by another embodiment of the present application, wherein the first slice management device 110 may be, but not limited to, a configuration center (Configuration Center, CC), as a functional module that provides slice configuration data creation, management, and delivery, CC can realize the slice service configuration function.
  • CC Configuration Center
  • CC When CC is deployed in NSMF, it can be responsible for network element data configuration of end-to-end network slicing radio access network, core network and transmission network.
  • the first slice management device 110 may be, but not limited to, a CC set in the NSSMF.
  • the CC When the CC is deployed in the NSSMF, it may be responsible for network element data configuration in the slice subnet to which the NSSMF belongs.
  • the type of service network element does not have a significant impact on the slice service configuration, so it is sufficient to consider the correlation between the slice service and the corresponding service network element, and there is no need to limit the type of service network element.
  • the following embodiments mainly illustrate the situation where the service network element is a physical network function (Physical Network Function, PNF) network element and a virtual network function (Virtual Network Function, VNF) network element, but this does not belong to the service network
  • PNF Physical Network Function
  • VNF Virtual Network Function
  • each service network element has a corresponding network function template
  • the network function template can integrate corresponding functional conditions for the service network element, for example, the network function corresponding to the PNF network element
  • the template is a physical network function template (Physical Network Function Descriptor, PNFD)
  • the network function template corresponding to the VNF network element is a virtual network function template (Virtual Network Function Descriptor, VNFD).
  • VNFD Virtual Network Function Descriptor
  • the definition of network element configuration template is added.
  • the network element configuration template is used to provide the configuration parameter model required by the service network element.
  • the service network element can provide multiple configuration templates to distinguish different service scenarios , each configuration template contains one or more atomic configuration templates, the user can directly use the configuration template according to the required business scenarios, or the service network element can also only provide multiple atomic configuration templates, and the user can use the configuration template according to the business requirements and atomic templates For the applicable scenarios, select the atomic configuration template for combination.
  • each atomic configuration template can be preset, or can be set according to the actual application scenario of the slicing service, wherein each atomic configuration template of the service network element includes at least the following content:
  • Configuration item Indicates a specific configuration item, such as Single Network Slice Selection Assistance Information (S-NSSAI) configuration, each configuration item contains at least the following information:
  • S-NSSAI Single Network Slice Selection Assistance Information
  • Configuration item name required by the user, used to identify different configuration items and distinguish business functions
  • Operation type required by the user, the operation type supported by the configuration, including adding, modifying, deleting, and querying;
  • Parameter attribute required by the user, including parameter name (required), parameter type (required), parameter meaning (required), parameter value range (optional), parameter default value (optional) and primary key parameters (optional), etc.;
  • Configuration dependency optional for users. If this configuration item depends on other configuration items, configure the name of the dependent configuration item, indicating that when delivering network element configuration data, the dependent configuration item should be delivered first, and then this configuration item should be delivered. Configuration items;
  • Configuration method Indicates the data distribution method of the configuration template, such as API interface, MML instruction, etc.;
  • Applicable scenarios Indicates the applicable business function category of the configuration template, such as slice configuration, DNN configuration, basic deployment configuration, etc.
  • NFVO when the PNF network element is directly managed by NFVO and PNFD provides a configuration template corresponding to the PNF network element, then NFVO can be used as the second slice management device 120.
  • NFVO directly manages PNFD, and import the configuration template corresponding to the PNF network element for PNFD, so that PNFD can integrate the configuration function of the configuration template corresponding to the PNF network element, and NSMF or NSSMF and NFVO can communicate and interact through the Os-ma-nfvo interface, thereby Obtain configuration template information in each PNFD.
  • the NFVO when the VNF network element is directly managed by the NFVO and the VNFD provides a configuration template corresponding to the VNF network element, the NFVO can be used as the second slice management device 120.
  • the NFVO directly manages the VNFD, and import the configuration template corresponding to the VNF network element for VNFD, so that VNFD can integrate the configuration function of the configuration template corresponding to the VNF network element, and NSMF or NSSMF and NFVO can interact through the Os-ma-nfvo interface, so as to obtain each
  • the configuration template information in a VNFD that is, the configuration template information can be queried in the output content of the Os-ma-nfvo interface;
  • the network architecture 100 can also include virtualized network function management (Virtualized Network Function Manager, VNFM) and Virtualized Infrastructure Manager (Virtualized Infrastructure Manager, VIM), wherein, VNFM and VIM are cascaded and managed by NFVO respectively,
  • NFMF can be used as the second slice management device 120.
  • NFMF can manage PNF and introduce the PNF network element
  • the corresponding configuration template makes it possible to integrate the configuration function of the configuration template corresponding to the PNF network element, and the NFMF and the CC can report the configuration template to the CC through northbound interaction, and the CC will perceive it.
  • the NFMF can be used as the second slice management device 120.
  • the NFMF can manage the VNF, and the northbound configuration imports the VNF
  • the configuration template corresponding to the network element enables the integration of the configuration function of the configuration template corresponding to the VNF network element, and the configuration template can be reported to the CC through northbound interaction between the NFMF and the CC, and the CC will perceive it.
  • NFMF can manage PNF, but NFMF will not manage PNFD, that is, when PNF is managed by NFMF, it will not involve the management of PNFD, but PNF can provide configuration templates to NFMF, but the way of providing is not through PNFD. of.
  • NSMF or NSSMF provides the CC function
  • the configuration template obtained from NFVO or NFMF query can be used as the basis for slice configuration parameter design to obtain slices that meet the requirements configuration parameters.
  • CC can form a configuration baseline library for the slice configuration templates of different network element types collected by different equipment vendors.
  • CC can compare the new template with the old template. Automatically identify differences and realize automatic update configuration baseline library.
  • the CC has stable operation and maintenance characteristics.
  • the CC can periodically query the NFMF for network element slice configuration data, and the query data items are based on the configuration template of the VNF or PNF.
  • the CC compares whether the local configuration data is consistent with the NFMF query results, audits the inconsistent data, and decides whether to update the local configuration based on the NFMF based on the audit results, or notifies the NFMF to update the service network element configuration based on the local configuration;
  • NFV Network Functions Virtualization
  • the CC can use the configuration data verification mechanism to discover the service network elements that failed to deliver the configuration and perform repair.
  • a plurality of functional modules are integrated in the CC to cooperate with the slice configuration function management process.
  • the CC includes but is not limited to:
  • Configuration Data Manager (Configuration Data Manager), used to manage two types of configuration template data and configuration instance data;
  • Configuration Collector which supports collecting configuration information related to generating slice configuration instance data
  • Configuration Controller which supports automatic generation of configuration instance data
  • Configuration Executor supports docking with NFMF to deliver configuration instance data to network element instances through NFMF, and also supports collecting network element configuration data from NFMF.
  • the CC may also include but not limited to a configuration UI (Configuration UI), which provides a user management interface for the data stored in the CC, and is used to manage configuration templates and configuration data, which is convenient for operation and maintenance personnel to perform manual review and adjust.
  • configuration UI Configuration UI
  • Both the first slice management apparatus 110 and the second slice management apparatus 120 in the network architecture 100 may respectively include a memory and a processor, where the memory and the processor may be connected through a bus or in other ways.
  • memory can be used to store non-transitory software programs and non-transitory computer-executable programs.
  • the memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid-state storage devices.
  • the memory optionally includes memory located remotely from the processor, and these remote memories may be connected to the processor via a network. Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • the network architecture 100 and application scenarios described in the embodiments of the present application are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute limitations on the technical solutions provided by the embodiments of the present application.
  • the evolution of the architecture 100 and the emergence of new application scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.
  • network architecture 100 shown in FIG. 1 and FIG. 2 does not constitute a limitation to the embodiment of the present application, and may include more or less components than those shown in the illustration, or combine certain components, or different component arrangements.
  • the first slice management device 110 and the second slice management device 120 can respectively call their stored resource sharing programs to execute the slice service configuration method.
  • FIG. 3 is a flow chart of a slice service configuration method provided by an embodiment of the present application, which can be but not limited to be applied to the first slice management device in the network architecture shown in the embodiment shown in FIG. 1.
  • the slice service configuration method includes but not limited to steps S100 to S400.
  • Step S100 Obtain slice configuration information corresponding to the slice service.
  • the relevant requirements and parameters of the slice service can be known through the slice configuration information, so as to facilitate the subsequent implementation of network element configuration data according to the slice configuration information ok.
  • step S100 includes but not limited to steps S110 to S120.
  • Step S110 receiving the first configuration request information from the first device for activating the slice service, the first configuration request information carrying the first planning information for characterizing the configuration requirements of the slice service;
  • Step S120 According to the first planning information in the first configuration request information, obtain slice configuration information meeting the configuration requirements of the slice service.
  • the first configuration request information by receiving the first configuration request information from the first device for activating the slice service, since the first configuration request information carries the first planning information, it is possible to know the configuration requirements of the slice service, and then find out the configuration requirements for the slice service.
  • the slice configuration information required for slice service configuration can be understood that the obtained slice configuration information can be adapted to the slice application, which is beneficial to improve the accuracy of the slice configuration.
  • the slice configuration information includes at least one of the following types: service configuration parameter information, or network resource topology information, or slice configuration policy information, wherein the service configuration parameter information can be determined according to actual scenarios, for example, Slice Service Type (SST), S-NSSAI, Public Land Mobile Network Identifier (PLMNID), Tracking Area Identity (TAI) list, Data Network Name (Data Network Name) , DNN), shared slices or dedicated slices, uplink and downlink rates, and other business parameters;
  • network resource topology information can be, but not limited to, information such as network element names, network element instances, network links between network elements, and gateway addresses Parameters and slice configuration policy information can be pre-set in the function template corresponding to the network element.
  • the slice configuration policy information needs to be obtained, it can be directly called from the function template corresponding to the network element, which can include but not limited to address pool planning Information, DNN routing access information, etc.
  • Step S200 Obtain a network element configuration template corresponding to a service network element, and the service network element is associated with a slice service.
  • the network element configuration template since the network element configuration template has corresponding configuration item information, and the service network element is associated with the slice service, therefore, by obtaining the network element configuration template corresponding to the service network element, the network element configuration template can be known
  • the provided configuration items are used to configure the corresponding slicing services, so as to further perform slicing data configuration according to the determined configuration items.
  • the specific content of the association between the service network element and the slicing service is not limited, for example, it may be: the service network element is a node link that executes the slicing service, or the service network element provides equipment support for the slicing service, Alternatively, the service network element serves as a node link in configuring the slicing service, which is not limited in this embodiment.
  • step S200 includes but not limited to steps S210 to S220.
  • Step S210 sending a data acquisition instruction to the second slice management device
  • Step S220 Receive the network element configuration template corresponding to the service network element sent by the second slice management device according to the data acquisition instruction.
  • the first slice management device may send a data acquisition instruction to the second slice management device, so that the second slice management device Send the network element configuration template corresponding to the service network element to the first slice management device. It can be seen that the cooperation between the second slice management device and the first slice management device can make the first slice management device stable and reliable
  • the network element configuration template can be obtained from the second slice management device.
  • the template query process of the network element configuration data is all based on the parameter range defined in the network element configuration template, which can unify the data standards of different operations and avoid different operations. Inconsistent standards in the process lead to errors in data processing.
  • the type and generation method of the data acquisition instruction are not limited, for example, it may be preset, or it may be correspondingly generated by the first slice management device according to different slice services. Examples are not limited.
  • Step S300 According to the slice configuration information and the network element configuration template, the network element configuration data required for performing the slice service is obtained.
  • the network element configuration data generated by the slice configuration information and the network element configuration template can conform to the slice service at the same time, it can also adapt to the template information of service network elements. Compared with related technologies, it fully considers the relationship between slice services and service network elements, and can reduce the configuration caused by manual identification of configuration model differences. error.
  • the specific operation of the slice service corresponding to the network element configuration data is not limited, and may be a single slice operation, such as slice deployment, slice update, etc., or multiple slice operations, such as slice deployment and update, etc. Therefore, those skilled in the art may perform setting operations according to actual scenarios, which is not limited in this embodiment.
  • step S300 includes but not limited to steps S310 to S320.
  • Step S310 according to the network element configuration template and the preset mapping rules, convert the slice configuration information into mapping parameters adapted to the network element configuration template;
  • Step S320 According to the mapping parameters, the network element configuration data required for executing the slicing service is obtained.
  • the slice configuration can be configured through the network element configuration template and the preset mapping rules.
  • the information is converted into mapping parameters adapted to the network element configuration template, that is, the slice configuration information is converted into more intuitive and reliable mapping parameters, and then based on the mapping parameters, the network element configuration data required to execute the slice service is obtained. It can be understood that, Since the slice configuration information is not converted and calculated by an external computing module or method, the accuracy of the network element configuration data obtained in this way is relatively high, and it is easier to meet the actual requirements of the slice service.
  • the mapping rule may be preset by the user according to the actual situation of the slicing service, which is not limited in this embodiment.
  • Step S400 sending the network element configuration data to the service network element.
  • the slice service configuration is performed by using the slice configuration information and the network element configuration template, fully considering Knowing the relationship between slice services and service network elements can reduce configuration errors caused by manual identification of configuration model differences and improve the accuracy of slice service configurations. It is good for slice services and service network elements. business impetus.
  • step S400 includes but not limited to steps S410 to S420.
  • Step S410 receiving the second configuration request information from the second slice service enabling device, the second slice service enabling device is associated with the service network element;
  • Step S420 Send a configuration request carrying network element configuration data to the second slice management device according to the second configuration request information, so that the second slice management device sends the network element configuration data to the service network element according to the configuration request.
  • the second slice management device when receiving the second configuration request information from the second slice service opening device, and then sending a configuration request to the second slice management device according to the second configuration request information, so that the second slice management device Send a configuration request to send network element configuration data to service network elements, that is, adopt a step-by-step confirmation method to determine the way to send network element configuration data to service network elements, so as to ensure that network element configuration data will not be sent to service network elements by mistake , or send wrong data to the service network element.
  • the purpose of sending the network element configuration data to the service network element cannot be achieved, but it can ensure that the service network element will not receive the error message.
  • the delivery process of network element configuration data is all based on the parameter range defined in the network element configuration template Standards can be used to unify the data standards of different operations, and avoid data processing errors caused by inconsistent standards of different operation processes.
  • the method for the second slice management device to send the network element configuration data to the service network element is not limited, and can be selected and set according to the actual application scenario.
  • the second slice management device can generate a configuration result according to the issued configuration request information, the configuration result information carries the network element configuration data, therefore, the second slice management device can directly send the configuration result information to the service network element, so as to realize sending the network element configuration data to the service network element.
  • FIG. 8 is a flow chart of a slice service configuration method provided by another embodiment of the present application, which can be but not limited to be applied to the second slice management device in the network architecture shown in the embodiment shown in FIG. 1.
  • the slice service configuration method includes but not limited to steps S500 to S600.
  • Step S500 receiving a data acquisition instruction from the first slice management device
  • Step S600 Send the network element configuration template corresponding to the service network element to the first slice management device according to the data acquisition instruction, so that the first slice management device obtains the execution slice according to the network element configuration template and the obtained slice configuration information Network element configuration data required by the service, and sending the network element configuration data to the service network element; wherein, the slice configuration information corresponds to the slice service, and the service network element is associated with the slice service.
  • the network element configuration template is sent to the first slice management apparatus according to the data acquisition instruction, so that the first slice management apparatus
  • the network element configuration template obtains the network element configuration data required to execute the slicing service.
  • the first slice management device uses the slice configuration information to cooperate with the network element configuration template to configure the slicing service, fully considering the slicing service.
  • the association relationship with service network elements can reduce configuration errors caused by manual identification of configuration model differences, and improve the accuracy of slice service configuration.
  • the slice configuration information is obtained by the first slice management device through the following steps: receiving the first configuration request information from the first slice service activation device, the first configuration request information carries the configuration used to characterize the slice service The first planning information required; according to the first planning information in the first configuration request information, obtain slice configuration information that meets the configuration requirements of the slice service, wherein the slice configuration information includes at least one of the following types: service configuration parameter information , or network resource topology information, or slice configuration policy information.
  • the slice service configuration method in this embodiment and the slice service configuration methods in the above-mentioned embodiments belong to the same inventive concept, the only difference is that the execution subject of the slice service configuration method in this embodiment is the network architecture
  • the second slice management device in the above-mentioned embodiments is executed by the first slice management device in the network architecture. Therefore, the implementation of the slice service configuration method in this embodiment can refer to the above-mentioned In the embodiment of the slice service configuration method in the embodiment, in order to avoid redundancy, the specific implementation manner of the slice service configuration method in this embodiment will not be repeated here.
  • FIG. 9 is a flow chart of a slice service configuration method provided by another embodiment of the present application, which can be but not limited to be applied to the network architecture shown in the embodiment shown in FIG. 1.
  • the slice service configuration method includes but not It is limited to steps S700 to S900.
  • Step S700 the first slice management device obtains the slice configuration information corresponding to the slice service, and sends a data acquisition instruction to the second slice management device;
  • Step S800 the second slice management device receives a data acquisition instruction from the first slice management device, and sends a network element configuration template corresponding to a service network element to the first slice management device according to the data acquisition instruction.
  • Step S900 the first slice management device obtains the network element configuration data required for executing the slice service according to the slice configuration information and the network element configuration template, and sends the network element configuration data to the service network element.
  • the first slice management device and the second slice management device interact with each other about data acquisition instructions, so that the first slice management device can obtain the information corresponding to the service network element from the second slice management device.
  • the network element configuration template is combined with the slice configuration information obtained by the first slice management device, so that the first slice management device can obtain the network element configuration data required to execute the slice service according to the slice configuration information and the network element configuration template, and correspondingly
  • the second slice management device cooperates with the first slice management device and provides it with a network element configuration template, without manually confirming the configuration mode, and the first slice management device uses slice configuration information to cooperate with the network element configuration template.
  • Slicing service configuration fully considers the relationship between slicing services and service network elements, which can reduce configuration errors caused by manual identification of configuration model differences and improve the accuracy of slicing service configuration.
  • Step 1 the CC receives the first configuration request information from the device for enabling the first slice service
  • Step 2 CC collects slice configuration information required for slice configuration planning, including but not limited to service configuration parameter information, network resource topology information, slice configuration policy information, etc.;
  • Step 3 the CC finds the corresponding network element configuration template from the configuration template library according to the network element information included in the slice service;
  • Step 4 CC automatically converts the collected data into parameter values in the configuration template according to the rules according to the collected parameters, network element configuration template and mapping rules, and generates network element configuration data;
  • step 5 the CC returns the slice configuration data result to the first slice service provisioning device.
  • slice configuration data can be automatically generated, which saves manpower and reduces the error probability of manual filling, thereby improving the efficiency of slice automatic provisioning and maintenance.
  • step S700 includes, but is not limited to, steps S710 to S720.
  • Step S710 the first slice management device receives the first configuration request information from the first slice service opening device, and the first configuration request information carries first planning information for characterizing the configuration requirements of the slice service;
  • Step S720 The first slice management device obtains slice configuration information meeting the configuration requirements of the slice service according to the first plan information in the first configuration request information.
  • the first slice management device receives the first configuration request information from the first slice service opening device, since the first configuration request information carries the first planning information, the first slice management device Being able to know the configuration requirements of the slice service, and then find slice configuration information meeting the configuration requirements of the slice service, is beneficial to improve the accuracy of the slice configuration.
  • Step 1 NFVO imports the configuration template for VNFD
  • Step 2 NFVO releases the designed VNFD
  • Step 3 CC queries NFVO for relevant content information of VNFD;
  • Step 4 NFVO returns the query result to CC
  • step 5 the CC obtains the configuration template information of the VNFD from the query result, and the configuration template information is the information of the network element configuration template corresponding to the VNF network element.
  • the network element configuration template can be automatically collected through the Os-ma-nfvo interface between CC and NFVO, avoiding the inefficiency and inaccuracy caused by manual collection, and improving the efficiency of slice automatic provisioning and maintenance.
  • Step 1 NFVO imports the configuration template for PNFD
  • Step 2 NFVO releases the designed PNFD
  • Step 3 CC queries NFVO for relevant content information of PNFD;
  • Step 4 NFVO returns the query result to CC
  • step 5 the CC obtains the configuration template information of the PNFD from the query result, and the configuration template information is the information of the network element configuration template corresponding to the PNF network element.
  • the network element configuration template can be automatically collected through the Os-ma-nfvo interface between CC and NFVO, avoiding the inefficiency and inaccuracy caused by manual collection, and improving the efficiency of slice automatic provisioning and maintenance.
  • Step 1 the CC queries the NFMF for the network element configuration model
  • Step 2 NFMF returns the query result to CC
  • step 3 the CC obtains the configuration template information of the network element (for example, a VNF network element or a PNF network element) from the query result.
  • the network element for example, a VNF network element or a PNF network element
  • the network element configuration template is automatically queried and collected through the northbound interface of the NFMF, and the configuration data is automatically generated, which can reduce the time and complexity of manually collecting the configuration model and configuration data, shorten the slice provisioning time, and improve the provisioning efficiency.
  • the first slice management device obtains the network element configuration data required for performing the slice service according to the slice configuration information and the network element configuration template" in step S900 includes but is not limited to step S910 .
  • Step S910 The first slice management device converts the slice configuration information into mapping parameters adapted to the network element configuration template according to the network element configuration template and the preset mapping rules, and obtains the network elements required for performing the slice service according to the mapping parameters Configuration Data.
  • the first slice management device converts the slice configuration information into more intuitive and reliable mapping parameters, and then obtains the network element configuration data required to execute the slice service based on the mapping parameters, since it does not rely on external computing modules or methods Therefore, the accuracy of the network element configuration data obtained in this way is relatively high, and it is easier to meet the actual requirements of the slice service.
  • the first slicing device can obtain the updated network element configuration template, that is, no matter how the network element configuration template evolves, the first slicing device will It has good adaptability and can obtain network element configuration templates under corresponding conditions.
  • Step 1 NFVO updates the PNF instance and associates it with the updated PNFD;
  • Step 2 the CC queries the NFVO for the relevant content information of the updated PNFD;
  • Step 3 NFVO returns the query result to CC
  • Step 4 the CC obtains the updated configuration template information of the PNFD from the query result.
  • the version coupling and dependence of the upper and lower systems can be reduced.
  • the configuration model of the lower system changes, it can be automatically sensed by the upper system, and the upper system can dynamically manage the configuration models of different versions of the lower system.
  • Step 1 NFVO updates the VNF instance and associates it with the updated VNFD;
  • Step 2 the CC queries the NFVO for the relevant content information of the updated VNFD;
  • Step 3 NFVO returns the query result to CC
  • Step 4 the CC obtains the updated configuration template information of the VNFD from the query result.
  • the version coupling and dependence of the upper and lower systems can be reduced.
  • the configuration model of the lower system changes, it can be automatically sensed by the upper system, and the upper system can dynamically manage the configuration models of different versions of the lower system.
  • Step 1 upgrade the network element management version managed by NFMF, and load the updated network element configuration template
  • Step 2 the CC queries the NFMF for the updated network element configuration model
  • Step 3 NFMF returns query result to CC
  • step 4 the CC obtains the updated configuration template information of the network element from the query result.
  • the version coupling and dependence of the upper and lower systems can be reduced.
  • the configuration model of the lower system changes, it can be automatically sensed by the upper system, and the upper system can dynamically manage the configuration models of different versions of the lower system.
  • mapping rules in the network element configuration template can be set by the operation and maintenance personnel based on the first slice management device, which is convenient for the operation and maintenance personnel to manually review and adjust.
  • the user preset parameters are taken as an example.
  • Step 1 In the CC interface, the operator chooses to set the mapping rules for the relevant parameters of the slice configuration template;
  • Step 2 CC presets corresponding parameter variables for slice configuration information required for generating slice configuration data, and provides them to the operator for selection;
  • Step 3 CC queries the managed network element configuration template and provides it to the operator for selection;
  • Step 4 CC presents a mapping rule configuration interface
  • Step 5 the operator sets the data source for the parameters in the template, including setting the mapping relationship with preset parameter variables, setting constants, and setting calculation formulas.
  • CC provides a user interface for managing configuration templates and configuration data, which is convenient for operation and maintenance personnel to manually review and adjust.
  • step S900 includes but is not limited to steps S920 to S930 .
  • Step S920 The first slice management device receives the second configuration request information from the second slice service enabling device, and sends a configuration request carrying network element configuration data to the second slice management device according to the second configuration request information , wherein, the second slice service provisioning device is associated with the service network element;
  • Step S930 the second slice management device receives the delivered configuration request, and sends network element configuration data to the service network element according to the delivered configuration request.
  • the method of sending network element configuration data to the service network element is determined by means of step-by-step confirmation, which can ensure that the network element configuration data will not be sent to the service network element by mistake, or the wrong data will not be sent to the service network element , in other words, if a problem occurs in any of the above steps, the service network element will not receive the wrong data that has the problem.
  • the delivery process of the network element configuration data is all defined in the network element configuration template
  • the parameter range of the data set shall prevail, which can unify the data standards of different operations, and avoid data processing errors caused by inconsistencies in different operation process standards.
  • the first slice management device can also review the slice configuration data in real time, and determine corresponding processing methods according to the review results, such as maintaining delivery, repairing, and updating operations, that is, it can perform slice configuration data Adaptive processing to improve the accuracy of slice configuration data.
  • step 5 the CC returns the slice configuration data result to the service network element" in Example 8 as an example.
  • Step 1 the CC receives the second configuration request information
  • Step 2 CC obtains the network element slice configuration data automatically generated during slice configuration planning
  • Step 3 the CC sends a slice configuration request to the NFMF in turn for each network element involved in the slice configuration data;
  • step 4 the NFMF completes the network element slice configuration, and returns the network element configuration result to the second slice service provisioning device.
  • the configuration data distribution process between the CC and the network element device is all based on the parameter range defined in the configuration template, which can unify the data standards of different operations and avoid the data caused by inconsistent standards in different operations. Handle issues that go wrong.
  • resource exploration and data planning can usually be done first, and then operations such as creation and modification of the slice or slice subnet can be performed.
  • resource planning and slice configuration data planning can be done.
  • the slice configuration data planning can be carried out according to the implementation mode shown in Figure 10;
  • the distribution of network element configuration data can be carried out according to the embodiment shown in Figure 21.
  • the step "obtaining automatically generated network element slice configuration data" in Figure 21 is the execution content of the embodiment shown in Figure 10, so
  • the data planning has been executed in advance (that is, the implementation shown in Figure 10 has been determined)
  • the pre-set The determined network element slice configuration data is delivered.
  • the network element slice configuration data needs to be generated in advance before delivery.
  • the CC queries the NFMF for the data information of the network element configuration template
  • the NFMF returns the configuration query result to the CC, and the query data parameters are based on the configuration template information of the network element;
  • CC compares the consistency between the local slice configuration data and the data queried from NFMF;
  • the CC will update the local slice configuration data based on the NFMF configuration data
  • the CC uses the local configuration data and sends the slice configuration data to the NFMF;
  • the slice service configuration method in this embodiment and the slice service configuration methods in the above-mentioned embodiments belong to the same inventive concept, the only difference is that the execution subject of the slice service configuration method in this embodiment is the network architecture
  • the first slice management device and the second slice management device, the executive bodies of the slice service configuration methods in the above embodiments are respectively the first slice management device in the network architecture and the second slice management device in the network architecture, Therefore, the implementation of the slice service configuration method in this embodiment can refer to the embodiments of the slice service configuration method in the above-mentioned embodiments. In order to avoid redundancy, the specific implementation of the slice service configuration method in this embodiment is not described here. Let me repeat.
  • an embodiment of the present application also provides a network system
  • the network system includes a first network device and a second network device, wherein the first network device can be applied as the first network device in the embodiment shown in Figure 1
  • the slice management apparatus 110 and the second network device may be applied as, for example, the second slice management apparatus 120 in the embodiment shown in FIG. 1 .
  • the network system in this embodiment can constitute a part of the network architecture 100 in the embodiment shown in FIG. 1, for example.
  • the first network device and the second network device can cooperate with each other to execute the slicing service configuration method applied in any embodiment of the network architecture 100, for example, the first network device and the second network device cooperate with each other to execute the method described above in FIG. 9 method steps S700 to S900 in FIG. 11 , method steps S710 to S720 in FIG. 11 , method steps S910 in FIG. 15 or method steps S920 to S930 in FIG. 20 .
  • an embodiment of the present application also provides a network device, which includes: a memory, a processor, and a computer program stored in the memory and operable on the processor.
  • the processor and memory can be connected by a bus or other means.
  • the network device in this embodiment can be applied to the first slice management device 110 or the second slice management device 120 in the network architecture 100 in the embodiment shown in FIG. Because of the same inventive concept, these embodiments have the same implementation principles and technical effects, and will not be described in detail here.
  • the non-transitory software programs and instructions required to implement the slice service configuration method of the above-mentioned embodiments are stored in the memory, and when executed by the processor, the slice service configuration methods of the above-mentioned embodiments are executed, for example, executing the above-described Figure 3 Method steps S100 to S400 in, method steps S110 to S120 in Fig. 4, method steps S210 to S220 in Fig. 5, method steps S310 to S320 in Fig. 6, method steps S410 to S420 in Fig. 7 or Fig. 8 Steps S500 to S600 in the method.
  • the device embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • an embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are executed by a processor or a controller, for example, by the above-mentioned Execution by a processor in the device embodiment can cause the processor to execute the slice service configuration method in the above embodiment, for example, execute the method steps S100 to S400 in FIG. 3 and the method steps S110 to S110 in FIG. 4 described above. S120, method steps S210 to S220 in FIG. 5 , method steps S310 to S320 in FIG. 6 , method steps S410 to S440 in FIG. 7 , method steps S500 to S600 in FIG. 8 , method steps S700 to S700 in FIG. 9 S900, method steps S710 to S720 in FIG. 11 , method steps S910 in FIG. 15 or method steps S920 to S930 in FIG. 20 .
  • the embodiment of the present application includes: obtaining the slice configuration information corresponding to the slice service; obtaining the network element configuration template corresponding to the service network element, and the service network element is associated with the slice service; The required network element configuration data; send the network element configuration data to the service network element.
  • configuration data uses slice configuration information and network element configuration templates to configure slice services, which fully considers the relationship between slice services and service network elements, and can reduce the cost caused by manual identification of configuration model differences. configuration errors, and improve the accuracy of slicing service configuration.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, tape, magnetic disk storage or other magnetic storage devices, or can Any other medium used to store desired information and which can be accessed by a computer.
  • communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media .

Landscapes

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

Abstract

一种切片业务配置方法、网络设备、网络***及存储介质，其中，切片业务配置方法包括：获取对应于切片业务的切片配置信息(S100)；获取与业务网元对应的网元配置模板，业务网元与切片业务关联(S200)；根据切片配置信息和网元配置模板得到执行切片业务所需的网元配置数据(S300)；向业务网元发送网元配置数据(S400)。

Description

切片业务配置方法、网络设备、网络***及存储介质
相关申请的交叉引用
本申请基于申请号为202111157690.8、申请日为2021年09月30日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请实施例涉及但不限于通信业务领域，尤其涉及一种切片业务配置方法、网络设备、网络***及计算机可读存储介质。
背景技术
电力行业借助5G通信的切片技术实现5G智能电网，使得电力网络更加自动化和智能化。现有的5G切片网络部署方式，主要通过各级网络切片管理***如网络切片管理功能(Network Slice Management Function，NSMF)、网络切片子网管理功能(Network Slice Subnet Management Function，NSSMF)、网络功能虚拟化编排器(Network Functions Virtualisation Orchestrator，NFVO)、网络功能管理功能(Network Function Management Function，NFMF)间的配合，完成网元资源部署和业务配置部署。
由于不同设备厂家提供的网元或应用的切片配置模型并未统一，需要从NSMF下发的切片配置参数也不尽相同，因此在应用过程中需要对这些网元或应用以及进行编排和管理，目前通常由人工在网元或应用归属的NFMF上单独或组合地配置切片数据，或者，由人工在NSMF上组织切片配置数据并且向NFMF下发配置请求，但不同网元的配置模型差异给人工带来了一定的辨识困难，相应地，人工基于所识别的配置模型而得到的配置参数的错误率则会相应增加，进而容易造成切片业务配置的准确率降低。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本申请实施例提供了一种切片业务配置方法、网络设备、网络***及计算机可读存储介质。
第一方面，本申请实施例提供了一种切片业务配置方法，包括：获取对应于切片业务的切片配置信息；获取与业务网元对应的网元配置模板，所述业务网元与所述切片业务关联；根据所述切片配置信息和所述网元配置模板得到执行所述切片业务所需的网元配置数据；向所述业务网元发送所述网元配置数据。
第二方面，本申请实施例还提供了一种切片业务配置方法，包括：接收来自第一切片管理装置的数据获取指令；根据所述数据获取指令向所述第一切片管理装置发送与业务网元对应的网元配置模板，使得所述第一切片管理装置根据所述网元配置模板和已获取到的切片配置信息，得到执行所述切片业务所需的网元配置数据，以及向所述业务网元发送所述网元配置数据；其中，所述切片配置信息对应于所述切片业务，所述业务网元与所述切片业务关联。
第三方面，本申请实施例还提供了一种切片业务配置方法，应用于网络***，所述网络***包括第一切片管理装置和第二切片管理装置，所述方法包括：所述第一切片管理装置获取对应于切片业务的切片配置信息，并向所述第二切片管理装置发送数据获取指令；所述第二切片管理装置接收来自第一切片管理装置的数据获取指令，并根据所述数据获取指令向所述第一切片管理装置发送与业务网元对应的网元配置模板；所述第一切片管理装置根据所述切片配置信息和所述网元配置模板，得到执行所述切片业务所需的网元配置数据，并向所述业务网元发送所述网元配置数据。
第四方面，本申请实施例还提供了一种网络设备，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现如上第一方面和第二方面所述的切片业务配置方法。
第五方面，本申请实施例还提供了一种网络***，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现如上第三方面所述的切片业务配置方法。
第六方面，本申请实施例还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行如上第一方面和第二方面所述的切片业务配置方法。
本申请的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本申请而了解。本申请的目的和其他优点可通过在说明书、权利要求书以及附图中所特别指出的结 构来实现和获得。
附图说明
附图用来提供对本申请技术方案的进一步理解，并且构成说明书的一部分，与本申请的实施例一起用于解释本申请的技术方案，并不构成对本申请技术方案的限制。
图1是本申请一个实施例提供的用于执行切片业务配置方法的网络架构的示意图；
图2是本申请另一个实施例提供的用于执行切片业务配置方法的网络架构的示意图；
图3是本申请一个实施例提供的切片业务配置方法的流程图；
图4是本申请一个实施例提供的切片业务配置方法中获取切片配置信息的流程图；
图5是本申请一个实施例提供的切片业务配置方法中获取网元配置模板的流程图；
图6是本申请一个实施例提供的切片业务配置方法中得到网元配置数据的流程图；
图7是本申请一个实施例提供的切片业务配置方法中发送网元配置数据的流程图；
图8是本申请另一个实施例提供的切片业务配置方法的流程图；
图9是本申请另一个实施例提供的切片业务配置方法的流程图；
图10是本申请一个实施例提供的切片业务配置方法的执行流程图；
图11是本申请一个实施例提供的查询网元配置模板的执行流程图；
图12是本申请另一个实施例提供的查询网元配置模板的执行流程图；
图13是本申请另一个实施例提供的查询网元配置模板的执行流程图；
图14是本申请另一个实施例提供的查询网元配置模板的执行流程图；
图15是本申请一个实施例提供的切片业务配置方法中第一切片管理装置得到网元配置数据的流程图；
图16是本申请一个实施例提供的更新网元配置模板的执行流程图；
图17是本申请另一个实施例提供的更新网元配置模板的执行流程图；
图18是本申请另一个实施例提供的更新网元配置模板的执行流程图；
图19是本申请一个实施例提供的预先设置配置参数的执行流程图；
图20是本申请一个实施例提供的切片业务配置方法中第一切片管理装置发送网元配置数据的流程图；
图21是本申请另一个实施例提供的返回切片配置数据的执行流程图；
图22是本申请一个实施例提供的审核切片配置数据的执行流程图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅用以解释本申请，并不用于限定本申请。
需要注意的是，虽然在装置示意图中进行了功能模块划分，在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于装置中的模块划分，或流程图中的顺序执行所示出或描述的步骤。说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
本申请提供了一种切片业务配置方法、网络设备、网络***及存储介质，通过获取对应于切片业务的切片配置信息和与业务网元对应的网元配置模板，进而根据切片配置信息和网元配置模板得到执行切片业务所需的网元配置数据，相比于相关技术，采用切片配置信息配合网元配置模板的方式进行切片业务配置，充分考虑到了切片业务与业务网元之间的关联关系，可以降低因人工辨识配置模型差异而带来的配置误差，提高切片业务配置的准确率。
下面结合附图，对本申请实施例进行阐述。
如图1所示，图1是本申请一个实施例提供的用于执行切片业务配置方法的网络架构100的示意图。
在图1的示例中，该网络架构100包括但不限于：第一切片管理装置110和第二切片管理装置120，其中，第一切片管理装置110和第二切片管理装置120相连接，两者之间可以进行信息交互，通过两者的配合能够向相应的业务网元发送执行切片业务所需的网元配置数据，以便于实现进一步地切片业务配置编排，进而提高切片业务配置编排的效率，主要用于通用的端到端网络切片管理，也可以应用于某个子域的切片子网管理；在另一实施例中，该网络架构100也可作为非切片场景的通用配置功能管理架构，应用于网元开局配置、策略配置等场景；在另一实施例中，该网络架构100还包括但不限于：第一切片业务开通装置130，其中，第一切片业务开通装置130与第一切片管理装置110相配合，可以向第一切片管理装置110发送针对切片业务的配置请求信息，以使得第一切片管理装置110根据相关配置请求信息执行与切片业务配置流程相关的操作；第二切片业务开通装置140，其中，第二切片业务开通装置140与第一切片管理装置110相配合，可以向第一切片管理装置110发送针对配置业务网元的配置请求信息，以使得第一切 片管理装置110根据相关配置请求信息执行与切片业务下发流程相关的操作。
需要说明的是，第一切片业务开通装置130和第二切片业务开通装置140可以但不限于设置在NSMF或NSSMF中，且两者的类型可以相同，也可以各自设置，例如，可以是切片生命周期管理模块(Network Slice Provision Management,NSPM)、切片子网生命周期管理模块(Network Slice Subnet Provision Management,NSSPM)等，在具体场景下两者可互用，即第一切片业务开通装置130可以作为第二切片业务开通装置140进行使用，反之亦然，这在实际应用中能够降低切片业务设置成本，同时达到优化切片业务配置的技术效果。
在一实施例中，参照图2，图2是本申请另一个实施例提供的网络架构100的示意图，其中，第一切片管理装置110可以但不限于为设置在NSMF中的配置中心(Configuration Center，CC)，CC作为提供切片配置数据制作、管理和下发的功能模块，能够实现切片业务配置功能。当CC部署在NSMF时，可负责端到端网络切片无线接入网、核心网及传输网的网元数据配置。
需要说明的是，为了更清楚地体现网络架构100的各个应用场景，在图2中同时示出了多种应用场景的情况，但这些应用场景不一定是同时存在的，具体实施方式在下方各个实施例中将逐一给出，为免引起误解，在此说明。
在一实施例中，参照图2，第一切片管理装置110可以但不限于为设置在NSSMF中的CC，当CC部署在NSSMF时，可负责NSSMF所属切片子网内的网元数据配置。
在一实施例中，业务网元的类型对于切片业务配置不会产生明显地影响，因此考虑切片业务与相应的业务网元之间的关联性即可，不用限制业务网元的类型，为了描述方便，以下各实施例主要以业务网元为物理网络功能(Physical Network Function，PNF)网元和虚拟网络功能(Virtual Network Function，VNF)网元的情况进行说明，但这并不属于对业务网元的类型进行限制。
在一实施例中，对应于切片业务场景中，每个业务网元存在与之对应的网络功能模板，网络功能模板可以为业务网元集成相应的功能条件，例如，PNF网元对应的网络功能模板为物理网络功能模板(Physical Network Function Descriptor,PNFD)，VNF网元对应的网络功能模板为虚拟网络功能模板(Virtual Network Function Descriptor,VNFD)。在VNFD、PNFD等网络功能模型中，新增网元配置模板的定义，网元配置模板用于提供业务网元所需的配置参数模型，业务网元可以提供区分不同业务场景的多个配置模板，每个配置模板中包含一个或者多个原子配置模板，用户可以根据需求的业务场景直接使用配置模板，或者，业务网元也可以仅提供多个原子配置模板，由用户根据业务需求以及原子模板的适用场景，自行挑选原子配置模板进行组合。
在一实施例中，每个原子配置模板的内容可以预先设置好，也可以根据切片业务的实际应用场景而进行设置，其中，业务网元的每个原子配置模板至少包含以下内容：
1、配置项：表示具体配置项，比如单个网络切片选择辅助信息(Single Network Slice Selection Assistance Information，S-NSSAI)配置，每个配置项至少包含以下信息：
A、配置项名称：用户必选，用于识别不同配置项，区分业务功能；
B、操作类型：用户必选，配置支持的操作类型，包括增加、修改、删除和查询等；
C、参数属性：用户必选，包括参数名(必选)、参数类型(必选)、参数含义(必选)、参数取值范围(可选)、参数默认值(可选)和是否主键参数(可选)等；
D、配置依赖：用户可选，如果本配置项依赖其他配置项，则配置被依赖的配置项名称，表示下发网元配置数据时，应先下发被依赖的配置项，再下发本配置项；
2、版本号：用于区分配置模板的不同版本；
3、配置方式：表示配置模板的数据下发方式，比如API接口、MML指令等；
4、适用场景：表示配置模板适用的业务功能类别，比如切片配置、DNN配置、基础开局配置等。
在一实施例中，参照图2，当PNF网元被NFVO直接管理且PNFD提供与PNF网元对应的配置模板，则NFVO可以作为第二切片管理装置120，在这种情况下，NFVO直接管理PNFD，并且为PNFD导入PNF网元对应的配置模板，使得PNFD能够集成PNF网元对应的配置模板的配置功能，并且，NSMF或NSSMF与NFVO间可以通过Os-ma-nfvo接口进行通信交互，从而获取每个PNFD中的配置模板信息。
在一实施例中，参照图2，当VNF网元被NFVO直接管理且VNFD提供与VNF网元对应的配置模板，则NFVO可以作为第二切片管理装置120，在这种情况下，NFVO直接管理VNFD，并且为VNFD导入VNF网元对应的配置模板，使得VNFD能够集成VNF网元对应的配置模板的配置功能，并且，NSMF或NSSMF与NFVO间可以通过Os-ma-nfvo接***互，从而获取每个VNFD中的配置模板信息，即，在Os-ma-nfvo接口的输出内容中可以查询得到配置模板信息；此外，在该实施例中，网络架构100还可以包括虚拟化网络功能管理(Virtualised Network Function Manager,VNFM)和虚拟化基础设施管理器(Virtualised Infrastructure Manager,VIM)，其中，VNFM和VIM级联且分别受到NFVO的管理，两者配合用于将VNF纳入到NFVO的管理下，可以确保NFVO对VNF实现良好稳定的编排管理。
在一实施例中，参照图2，若PNFD未提供与PNF网元对应的配置模板，则NFMF可以作为第二切片管理装置120，在这种情况下，NFMF可以管理PNF，并且引入PNF网元对应的配置模板，使得能够集成PNF网元对应的配置模板的配置功能，并且NFMF与CC间可以通过北向交互而上报配置模板至CC,由CC进行感知。
在一实施例中，参照图2，若VNFD未提供与VNF网元对应的配置模板，则NFMF可以作为第二切片管理装置120，在这种情况下，NFMF可以管理VNF，并且北向配置引入VNF网元对应的配置模板，使得能够集成VNF网元对应的配置模板的配置功能，并且NFMF与CC间可以通过北向交互而上报配置模板至CC,由CC进行感知。
需要说明的是，NFMF可以管理PNF，但是NFMF不会管理PNFD，即PNF被NFMF管理时，不会涉及对PNFD的管理，但是PNF可以向NFMF提供配置模板，只不过提供方式不是通过PNFD来实现的。
在一实施例中，在NSMF或NSSMF提供CC功能的情况下，当设计切片业务配置参数时，可以将从NFVO或NFMF查询得到的配置模板，作为切片配置参数设计的依据，得到满足要求的切片配置参数。同时，CC对于所采集的不同设备商的不同网元类型的切片配置模板，可形成配置基线库，当网元设备的配置模板版本号发生变更时，CC可通过新模板与老模板的比对自动识别差异，实现自动更新配置基线库。
在一实施例中，CC具有稳定的运维特性，在切片运维过程中，CC可以定期地向NFMF查询网元切片配置数据，查询数据项以VNF或PNF的配置模板为准。CC比较本地配置数据与NFMF查询结果是否一致，对不一致数据进行审核，根据审核结果决定是否以NFMF为准更新本地配置，或者以本地配置为准通知NFMF更新业务网元配置；在切片开通或运维时，当存在网络功能虚拟化(Network Functions Virtualisation，NFV)节点故障而导致CC向NFMF下发切片配置数据失败时，CC可以通过配置数据核查机制，发现下发配置失败的业务网元并进行修复。
在一实施例中，CC内集成多个功能模块，以配合实现切片配置功能管理流程，CC内包括但不限于设置有：
配置数据管理器(Configuration Data Manager)，用于管理配置模板数据和配置实例数据两种类型；
配置采集器(Configuration Collector)，支持采集与生成切片配置实例数据相关的配置信息；
配置控制器(Configuration Controller)，支持自动生成配置实例数据；
配置执行器(Configuration Executor)，支持与NFMF对接以将配置实例数据通过NFMF下发给网元实例，也支持从NFMF采集网元配置数据。
在又一实施例中，CC还可以包括但不限于有配置UI(Configuration UI)，其为CC所存储的数据提供用户管理界面，用于管理配置模板和配置数据，方便运维人员进行人工审核和调整。
网络架构100中的第一切片管理装置110和第二切片管理装置120均可以分别包括有存储器和处理器，其中，存储器和处理器可以通过总线或者其他方式连接。
存储器作为一种非暂态计算机可读存储介质，可用于存储非暂态软件程序以及非暂态性计算机可执行程序。此外，存储器可以包括高速随机存取存储器，还可以包括非暂态存储器，例如至少一个磁盘存储器件、闪存器件、或其他非暂态固态存储器件。在一些实施方式中，存储器可选包括相对于处理器远程设置的存储器，这些远程存储器可以通过网络连接至该处理器。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
本申请实施例描述的网络架构100以及应用场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域技术人员可知，随着网络架构100的演变和新应用场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本领域技术人员可以理解的是，图1和图2中示出的网络架构100并不构成对本申请实施例的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
在图1和图2所示的网络架构100中，第一切片管理装置110和第二切片管理装置120可以分别调用其储存的资源共享程序，以执行切片业务配置方法。
基于上述网络架构100的结构，提出本申请的切片业务配置方法的各个实施例。
如图3所示，图3是本申请一个实施例提供的切片业务配置方法的流程图，可以但不限于应用于如图1实施例所示的网络架构中的第一切片管理装置，该切片业务配置方法包括但不限于步骤S100至S400。
步骤S100：获取对应于切片业务的切片配置信息。
在一实施例中，由于获取的切片配置信息是对应于切片业务的，因此，通过切片配置信息可以了解到切片业务的相关需求和相关参数等，以便于后续根据切片配置信息实现网元配置数据的确定。
在图4的示例中，步骤S100包括但不限于步骤S110至S120。
步骤S110：接收来自第一切片业务开通装置的第一配置请求信息，第一配置请求信息携带有用于表征切片业务的配置要求的第一规划信息；
步骤S120：根据第一配置请求信息中的第一规划信息，获取符合切片业务的配置要求的切片配置信息。
在一实施例中，通过接收来自第一切片业务开通装置的第一配置请求信息，由于第一配置请求信息中携带有第一规划信息，因此能够获知切片业务的配置要求，进而查找出符合切片业务的配置要求的切片配置信息，可以理解地是，所获取得到的切片配置信息能够适配于切片应用，有利于提高切片配置的准确率。
在一实施例中，切片配置信息包括如下类型中的至少一种:业务配置参数信息、或网络资源拓扑信息、或切片配置策略信息，其中，业务配置参数信息可以根据实际场景确定，例如，可以是切片业务类型(Slice Service Type，SST)、S-NSSAI、公共陆地移动网标识(Public Land Mobile Network Identifier,PLMNID)、跟踪区标识(Tracking Area Identity，TAI)列表、数据网络名(Data Network Name，DNN)、共享切片或专用切片、上下行速率等等业务参数；网络资源拓扑信息可以但不限于为网元名称、网元实例、各个网元间的网络链接的IP地址以及网关地址等信息参数，切片配置策略信息可以预先设置在网元对应的功能模板中，当需要获取切片配置策略信息，则直接从网元对应的功能模板中调用即可，可以包括但不限于为地址池规划方式信息、DNN路由接入方式信息等。
步骤S200：获取与业务网元对应的网元配置模板，业务网元与切片业务关联。
在一实施例中，由于网元配置模板带有相应的配置项信息，且业务网元与切片业务关联，因此，通过获取与业务网元对应的网元配置模板，则可以获知网元配置模板所提供的配置项，这些配置项是用于配置相应的切片业务的，以便于后续根据所确定的配置项进行进一步地切片数据配置。
在一实施例中，业务网元与切片业务之间关联的具体内容不限定，例如，可以为：业务网元是执行切片业务的一个节点环节，或者，业务网元为切片业务提供设备支持，或者，业务网元作为配置切片业务中的一个节点环节等，本实施例并未限制。
在图5的示例中，步骤S200包括但不限于步骤S210至S220。
步骤S210：向第二切片管理装置发送数据获取指令；
步骤S220：接收由第二切片管理装置根据数据获取指令发送的与业务网元对应的网元配置模板。
在一实施例中，由于第二切片管理装置与第一切片管理装置相配合，因此，第一切片管理装置可以通过向第二切片管理装置发送数据获取指令，以使得第二切片管理装置向第一切片管理装置发送与业务网元对应的网元配置模板，可以看出，通过第二切片管理装置与第一切片管理装置的配合方式，能够使得第一切片管理装置稳定可靠地从第二切片管理装置获取网元配置模板，尤其是，网元配置数据的模板查询流程，全部以网元配置模板中定义的参数范围为准，可以统一不同操作的数据标准，避免不同操作过程中的标准不统一而导致数据处理出现错误。
在一实施例中，数据获取指令的类型和生成方式不限定，例如，可以是预先设定好的，也可以是由第一切片管理装置根据不同的切片业务而对应生成的，这在本实施例中并未限制。
步骤S300：根据切片配置信息和网元配置模板得到执行切片业务所需的网元配置数据。
在一实施例中，由于切片配置信息对应于切片业务，并且网元配置模板与业务网元对应，因此，通过切片配置信息和网元配置模板所生成的网元配置数据，既能够符合切片业务的需求，同时也能够适配于业务网元的模板信息，相比于相关技术，充分考虑到了切片业务与业务网元之间的关联关系，可以降低因人工辨识配置模型差异而带来的配置误差。
在一实施例中，网元配置数据所对应的切片业务的具体操作不限定，可以为单次切片操作，例如切片部署、切片更新等，或者，多次切片操作，例如切片部署及更新等，因此本领域技术人员可以根据实际场景进行设定操作，本实施例并未限制。
在图6的示例中，步骤S300包括但不限于步骤S310至S320。
步骤S310：根据网元配置模板和预置的映射规则，将切片配置信息转换为适配网元配置模板的映射参数；
步骤S320：根据映射参数得到执行切片业务所需的网元配置数据。
在一实施例中，由于预设了针对切片配置信息的映射规则，因此在确定切片配置信息和网元配置模板的情况下，通过网元配置模板和预置的映射规则，则能够将切片配置信息转换为适配网元配置模板的映射参数，即，将切片配置信息转化为更加直观可靠的映射参数，进而基于该映射参数得到执行切片业务所需的网元配置数据，可以理解地是，由于不依靠外部运算模块或方式来对切片配置信息进行转化计算，因此，这样获取到的网元配置数据的准确率相对较高，更容易符合切片业务的实际要求。
在一实施例中，映射规则可以由用户根据切片业务的实际情况预先设定，本实施例并未限制。
步骤S400：向业务网元发送网元配置数据。
在一实施例中，通过获取对应于切片业务的切片配置信息和与业务网元对应的网元配置模板，进而根据切片配置信息和网元配置模板得到执行切片业务所需的网元配置数据，并向业务网元发送网元配置数据，以使得业务网元针对相应的切片业务进行切片业务处理，相比于相关技术，采用切片配置信息配合网元配置模板的方式进行切片业务配置，充分考虑到了切片业务与业务网元之间的关联关系，可以降低因人工辨识配置模型差异而带来的配置误差，提高切片业务配置的准确率，无论对于切片业务还是业务网元而言， 均具有良好的业务推动作用。
在图7的示例中，步骤S400包括但不限于步骤S410至S420。
步骤S410：接收来自第二切片业务开通装置的第二配置请求信息，第二切片业务开通装置与业务网元关联；
步骤S420：根据第二配置请求信息向第二切片管理装置发送携带有网元配置数据的下发配置请求，以使第二切片管理装置根据下发配置请求向业务网元发送网元配置数据。
在一实施例中，当接收来自第二切片业务开通装置的第二配置请求信息，进而根据第二配置请求信息向第二切片管理装置发送下发配置请求，以使第二切片管理装置根据下发配置请求向业务网元发送网元配置数据，即，采用逐级确认的手段以确定向业务网元发送网元配置数据的方式，可以确保不会错误地向业务网元发送网元配置数据，或者向业务网元发送错误数据，换言之，若上述步骤中的任意一步出现问题，则无法达到向业务网元发送网元配置数据的目的，但可以确保业务网元不会接收到出现问题的错误数据，而且下发网元配置数据是根据配置请求来实现的，更能够符合实际应用场景；可以理解地是，网元配置数据的下发流程，全部以网元配置模板中定义的参数范围为准，可以统一不同操作的数据标准，避免不同操作过程标准不统一导致数据处理的错误。
需要说明的是，第二切片管理装置向业务网元发送网元配置数据的方式不限定，可以根据实际应用场景进行选择设定，例如，第二切片管理装置可以根据下发配置请求生成配置结果信息，该配置结果信息携带有网元配置数据，因此，第二切片管理装置可以直接向业务网元发送配置结果信息，即可实现向业务网元发送网元配置数据。
如图8所示，图8是本申请另一个实施例提供的切片业务配置方法的流程图，可以但不限于应用于如图1实施例所示的网络架构中的第二切片管理装置，该切片业务配置方法包括但不限于步骤S500至S600。
步骤S500：接收来自第一切片管理装置的数据获取指令；
步骤S600：根据数据获取指令向第一切片管理装置发送与业务网元对应的网元配置模板，使得第一切片管理装置根据网元配置模板和已获取到的切片配置信息，得到执行切片业务所需的网元配置数据，以及向业务网元发送网元配置数据；其中，切片配置信息对应于切片业务，业务网元与切片业务关联。
在一实施例中，通过接收来自第一切片管理装置的数据获取指令，从而根据数据获取指令向第一切片管理装置发送网元配置模板，使得第一切片管理装置根据切片配置信息和网元配置模板得到执行切片业务所需的网元配置数据，相比于相关技术，使得第一切片管理装置采用切片配置信息配合网元配置模板的方式进行切片业务配置，充分考虑到了切片业务与业务网元之间的关联关系，可以降低因人工辨识配置模型差异而带来的配置误差，提高切片业务配置的准确率。
在一实施例中，切片配置信息由第一切片管理装置通过以下步骤得到：接收来自第一切片业务开通装置的第一配置请求信息，第一配置请求信息携带有用于表征切片业务的配置要求的第一规划信息；根据第一配置请求信息中的第一规划信息，获取符合切片业务的配置要求的切片配置信息，其中，切片配置信息包括如下类型中的至少一种:业务配置参数信息、或网络资源拓扑信息、或切片配置策略信息。
值得注意的是，由于本实施例中的切片业务配置方法与上述各实施例中的切片业务配置方法属于同一发明构思，区别仅在于本实施例中的切片业务配置方法的执行主体为网络架构中的第二切片管理装置，上述各实施例中的切片业务配置方法的执行主体为网络架构中的第一切片管理装置，因此本实施例中的切片业务配置方法的实施方式，可以参照上述各实施例中的切片业务配置方法的实施例，为避免冗余，本实施例的切片业务配置方法的具体实施方式在此不再赘述。
如图9所示，图9是本申请另一个实施例提供的切片业务配置方法的流程图，可以但不限于应用于如图1实施例所示的网络架构，该切片业务配置方法包括但不限于步骤S700至S900。
步骤S700：第一切片管理装置获取对应于切片业务的切片配置信息，并向第二切片管理装置发送数据获取指令；
步骤S800：第二切片管理装置接收来自第一切片管理装置的数据获取指令，并根据数据获取指令向第一切片管理装置发送与业务网元对应的网元配置模板。
步骤S900：第一切片管理装置根据切片配置信息和网元配置模板，得到执行切片业务所需的网元配置数据，并向业务网元发送网元配置数据。
在一实施例中，第一切片管理装置与第二切片管理装置之间进行关于数据获取指令的交互，使得第一切片管理装置能够从第二切片管理装置获取到与业务网元对应的网元配置模板，结合第一切片管理装置已经获取到的切片配置信息，使得第一切片管理装置能够根据切片配置信息和网元配置模板得到执行切片业务所需的网元配置数据，相比于相关技术，第二切片管理装置配合第一切片管理装置并向其提供网元配置模板，无需人工确认配置方式，第一切片管理装置采用切片配置信息配合网元配置模板的方式进行切片业务配置，充分考虑到了切片业务与业务网元之间的关联关系，可以降低因人工辨识配置模型差异而带来的配置误差，提高切片业务配置的准确率。
为了更清楚地阐述上述各个实施例的工作原理，以下给出相关示例对各个实施例的工作流程进行说明，其中，第一切片管理装置采用CC，第二切片管理装置采用NFVO或NFMF。
示例一：
如图10所示，以CC实现切片配置全流程为例。
步骤1，CC接收到来自第一切片业务开通装置的第一配置请求信息；
步骤2，CC采集切片配置规划需要的切片配置信息，包括但不限于业务配置参数信息、网络资源拓扑信息和切片配置策略信息等；
步骤3，CC根据切片业务包含的网元信息，从配置模板库中找到对应的网元配置模板；
步骤4，CC根据采集的参数、网元配置模板以及映射规则，将采集的数据按照规则自动转换为配置模板中的参数取值，生成网元配置数据；
步骤5，CC向第一切片业务开通装置返回切片配置数据的结果。
可以理解地是，切片配置数据可以自动生成，节省人力，减少人工填写的错误概率，从而提高切片自动化开通运维的效率。
在图11的示例中，步骤S700中的“第一切片管理装置获取对应于切片业务的切片配置信息”包括但不限于步骤S710至S720。
步骤S710：第一切片管理装置接收来自第一切片业务开通装置的第一配置请求信息，第一配置请求信息携带有用于表征切片业务的配置要求的第一规划信息；
步骤S720：第一切片管理装置根据第一配置请求信息中的第一规划信息，获取符合切片业务的配置要求的切片配置信息。
在一实施例中，第一切片管理装置通过接收来自第一切片业务开通装置的第一配置请求信息，由于第一配置请求信息中携带有第一规划信息，因此第一切片管理装置能够获知切片业务的配置要求，进而查找出符合切片业务的配置要求的切片配置信息，有利于提高切片配置的准确率。
示例二：
如图12所示，以在NFVO上设计VNFD为例。
步骤1，NFVO为VNFD导入配置模板；
步骤2，NFVO对设计完成的VNFD执行发布；
步骤3，CC向NFVO查询VNFD的相关内容信息；
步骤4，NFVO向CC返回查询结果；
步骤5，CC从查询结果中获取到VNFD的配置模板信息，该配置模板信息即为VNF网元对应的网元配置模板的信息。
可以理解地是，网元配置模板可以通过CC与NFVO之间的Os-ma-nfvo接口自动采集，避免人工采集导致的低效和不准确，能够提高切片自动化开通运维的效率。
示例三：
如图13所示，以在NFVO上设计PNFD为例。
步骤1，NFVO为PNFD导入配置模板；
步骤2，NFVO对设计完成的PNFD执行发布；
步骤3，CC向NFVO查询PNFD的相关内容信息；
步骤4，NFVO向CC返回查询结果；
步骤5，CC从查询结果中获取到PNFD的配置模板信息，该配置模板信息即为PNF网元对应的网元配置模板的信息。
可以理解地是，网元配置模板可以通过CC与NFVO之间的Os-ma-nfvo接口自动采集，避免人工采集导致的低效和不准确，能够提高切片自动化开通运维的效率。
示例四:
如图14所示，以在NFMF上查询配置模板信息为例。
步骤1，CC向NFMF查询网元配置模型；
步骤2，NFMF向CC返回查询结果；
步骤3，CC从查询结果中获取网元(例如，VNF网元或PNF网元)的配置模板信息。
可以理解地是，网元配置模板通过NFMF的北向接口自动查询采集，以及配置数据自动生成，均可以减少人工采集配置模型和人工配置数据的时间和复杂度，缩短切片开通时长，提高开通效率。
在图15的示例中，步骤S900中的“第一切片管理装置根据切片配置信息和网元配置模板，得到执行切片业务所需的网元配置数据”包括但不限于步骤S910。
步骤S910：第一切片管理装置根据网元配置模板和预置的映射规则，将切片配置信息转换为适配网元配置模板的映射参数，并根据映射参数得到执行切片业务所需的网元配置数据。
在一实施例中，第一切片管理装置将切片配置信息转化为更加直观可靠的映射参数，进而基于该映射参数得到执行切片业务所需的网元配置数据，由于不依靠外部运算模块或方式来对切片配置信息进行转化计算，因此，这样获取到的网元配置数据的准确率相对较高，更容易符合切片业务的实际要求。
在一实施例中，若网元配置模板的相关信息进行更新过，则第一切片装置能够获取更新过的网元配置模板，即，无论网元配置模板如何演变，第一切片装置都具有良好的适应性，能够获取相应条件下的网元配置模板。
示例五:
如图16所示，以在NFVO上更新配置模板信息为例。
步骤1，NFVO对PNF实例执行更新，关联到更新过的PNFD；
步骤2,CC向NFVO查询更新过的PNFD的相关内容信息；
步骤3,NFVO向CC返回查询结果；
步骤4,CC从查询结果中获取更新过的PNFD的配置模板信息。
可以理解地是，通过更新模板信息，可以减少上、下级***的版本耦合和依赖，当下级***配置模型变更，可以自动被上级***感知，而上级***可以动态管理下级***不同版本的配置模型。
示例六:
如图17所示，以在NFVO上更新配置模板信息为例。
步骤1，NFVO对VNF实例执行更新，关联到更新过的VNFD；
步骤2,CC向NFVO查询更新过的VNFD的相关内容信息；
步骤3,NFVO向CC返回查询结果；
步骤4,CC从查询结果中获取更新过的VNFD的配置模板信息。
可以理解地是，通过更新模板信息，可以减少上、下级***的版本耦合和依赖，当下级***配置模型变更，可以自动被上级***感知，而上级***可以动态管理下级***不同版本的配置模型。
示例七:
如图18所示，以在NFMF上更新配置模板信息为例。
步骤1，NFMF管理的网元管理版本升级，加载更新过的网元配置模板；
步骤2,CC向NFMF查询更新过的网元配置模型；
步骤3,NFMF向CC返回查询结果；
步骤4,CC从查询结果中获取更新过的网元的配置模板信息。
可以理解地是，通过更新模板信息，可以减少上、下级***的版本耦合和依赖，当下级***配置模型变更，可以自动被上级***感知，而上级***可以动态管理下级***不同版本的配置模型。
在一实施例中，网元配置模板中的映射规则可以由运维人员基于第一切片管理装置而进行设置，方便运维人员进行人工审核和调整。
示例八:
如图19所示，以用户预设参数为例。
步骤1，操作员在CC界面中，选择对切片配置模板的相关参数设置映射规则；
步骤2,CC对用于生成切片配置数据所需的切片配置信息预置相应的参数变量，提供给操作员选择；
步骤3,CC查询已管理的网元配置模板，提供给操作员选择；
步骤4,CC呈现映射规则配置界面；
步骤5，操作员对模板中的参数设置数据来源，包括设置与预置参数变量的映射关系、设置常量以及设置计算公式等。
可以理解地是，CC提供用户界面，用于管理配置模板和配置数据，方便运维人员进行人工审核和调整。
如图20所示，步骤S900中的“第一切片管理装置向业务网元发送网元配置数据”包括但不限于步骤S920至S930。
步骤S920：第一切片管理装置接收来自第二切片业务开通装置的第二配置请求信息，并根据第二配置请求信息，向第二切片管理装置发送携带有网元配置数据的下发配置请求，其中，第二切片业务开通装置与业务网元关联；
步骤S930：第二切片管理装置接收下发配置请求，并根据下发配置请求向业务网元发送网元配置数据。
在一实施例中，采用逐级确认的手段以确定向业务网元发送网元配置数据的方式，可以确保不会错误地向业务网元发送网元配置数据，或者向业务网元发送错误数据，换言之，若上述步骤中的任意一步出现问题，则业务网元不会接收到出现问题的错误数据，可以理解地是，该网元配置数据的下发流程，全部以网元配置模板中定义的参数范围为准，可以统一不同操作的数据标准，避免不同操作过程标准不统一导致数据处理的错误。
在一实施例中，第一切片管理装置还能够实时地审核切片配置数据，并根据审核结果确定相应的处理 方式，例如维持下发、修复以及更新等操作，即，能够针对切片配置数据进行适应性地处理，从而提升切片配置数据的准确率。
示例九:
如图21所示，以示例八中的步骤5“CC向业务网元返回切片配置数据的结果”为例。
步骤1，CC接收到第二配置请求信息；
步骤2，CC获取切片配置规划时自动生成的网元切片配置数据；
步骤3，CC对切片配置数据涉及的每个网元，依次向NFMF下发切片配置请求；
步骤4，NFMF完成网元切片配置，向第二切片业务开通装置返回网元配置结果。
可以理解地是，CC与网元设备间的配置数据下发流程，全部以配置模板中定义的参数范围为准，可以统一不同操作的数据标准，避免不同操作过程中因标准不统一而导致数据处理出现错误的问题。
需要说明的是，切片或切片子网的开通或运维时，通常可以先做资源勘查和数据规划，然后再执行对切片或切片子网的创建、修改等操作。在数据规划阶段，可以做资源规划和切片配置数据规划，其中，切片配置数据规划可以按照图10所示实施方式进行；当执行对切片或切片子网的创建、修改，若需要给业务网元下发网元配置数据，则可以按照图21所示实施方式进行，实质上，图21中的步骤“获取自动生成的网元切片配置数据”即为图10所示实施方式的执行内容，因此在实际应用场景中，若预先执行了数据规划(即，已经确定了图10所示实施方式)，则在执行图21所示的下发网元配置数据的具体流程时，可以直接地采用预先确定的网元切片配置数据以进行下发，相应地，若并未预先执行数据规划，则在下发网元配置数据时需要预先自行生成网元切片配置数据，再进行下发。
示例十:
如图22所示，以CC审核切片配置数据为例。
1、CC向NFMF查询网元配置模板的数据信息；
2、NFMF向CC返回配置查询结果，查询数据参数基于网元的配置模板信息；
3、CC比较本地切片配置数据与从NFMF查询到的数据之间的一致性；
4、CC针对查找到的不一致数据进行审核，并给出审核结论和处理方式：
4.1、若审核以NFMF配置为准，则CC基于NFMF配置数据，更新本地切片配置数据；
4.2、若审核以本地配置为准，则CC采用本地配置数据，向NFMF下发切片配置数据；
4.3、若审核发现当前切片配置不合适，则CC按照上述各实施例所示的切片配置更新流程重新进行处理。
值得注意的是，由于本实施例中的切片业务配置方法与上述各实施例中的切片业务配置方法属于同一发明构思，区别仅在于本实施例中的切片业务配置方法的执行主体为网络架构中的第一切片管理装置和第二切片管理装置，上述各实施例中的切片业务配置方法的执行主体分别为网络架构中的第一切片管理装置以及网络架构中的第二切片管理装置，因此本实施例中的切片业务配置方法的实施方式，可以参照上述各实施例中的切片业务配置方法的实施例，为避免冗余，本实施例的切片业务配置方法的具体实施方式在此不再赘述。
另外，本申请的一个实施例还提供了一种网络***，该网络***包括第一网络设备和第二网络设备，其中，第一网络设备可以应用为例如图1所示实施例中的第一切片管理装置110，第二网络设备可以应用为例如图1所示实施例中的第二切片管理装置120。本实施例中的网络***能够构成例如图1所示实施例中的网络架构100的一部分，这些实施例均属于相同的发明构思，因此这些实施例具有相同的实现原理以及技术效果，此处不再详述。
第一网络设备和第二网络设备能够相互配合执行如上应用于网络架构100的任意实施例中的切片业务配置方法，例如，第一网络设备和第二网络设备相互配合执行以上描述的图9中的方法步骤S700至S900、图11中的方法步骤S710至S720、图15中的方法步骤S910或图20中的方法步骤S920至S930。
另外，本申请的一个实施例还提供了一种网络设备，该设备包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序。
处理器和存储器可以通过总线或者其他方式连接。
需要说明的是，本实施例中的网络设备，可以应用于如图1所示实施例中的网络架构100中的第一切片管理装置110或第二切片管理装置120，这些实施例均属于相同的发明构思，因此这些实施例具有相同的实现原理以及技术效果，此处不再详述。
实现上述实施例的切片业务配置方法所需的非暂态软件程序以及指令存储在存储器中，当被处理器执行时，执行上述各实施例的切片业务配置方法，例如，执行以上描述的图3中的方法步骤S100至S400、图4中的方法步骤S110至S120、图5中的方法步骤S210至S220、图6中的方法步骤S310至S320、图7中的方法步骤S410至S420或图8中的方法步骤S500至S600。
以上所描述的装置实施例仅仅是示意性的，其中作为分离部件说明的单元可以是或者也可以不是物理 上分开的，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。
此外，本申请的一个实施例还提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机可执行指令，该计算机可执行指令被一个处理器或控制器执行，例如，被上述设备实施例中的一个处理器执行，可使得上述处理器执行上述实施例中的切片业务配置方法，例如，执行以上描述的图3中的方法步骤S100至S400、图4中的方法步骤S110至S120、图5中的方法步骤S210至S220、图6中的方法步骤S310至S320、图7中的方法步骤S410至S440、图8中的方法步骤S500至S600、图9中的方法步骤S700至S900、图11中的方法步骤S710至S720、图15中的方法步骤S910或图20中的方法步骤S920至S930。
本申请实施例包括：获取对应于切片业务的切片配置信息；获取与业务网元对应的网元配置模板，业务网元与切片业务关联；根据切片配置信息和网元配置模板得到执行切片业务所需的网元配置数据；向业务网元发送网元配置数据。根据本申请实施例提供的方案，通过获取对应于切片业务的切片配置信息和与业务网元对应的网元配置模板，进而根据切片配置信息和网元配置模板得到执行切片业务所需的网元配置数据，相比于相关技术，采用切片配置信息配合网元配置模板的方式进行切片业务配置，充分考虑到了切片业务与业务网元之间的关联关系，可以降低因人工辨识配置模型差异而带来的配置误差，提高切片业务配置的准确率。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、***可以被实施为软件、固件、硬件及其适当的组合。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
以上是对本申请的实施方式进行的说明，但本申请并不局限于上述实施方式，熟悉本领域的技术人员在不违背本申请精神的前提下还可作出种种的等同变形或替换，这些等同的变形或替换均包含在本申请权利要求所限定的范围内。

Claims (17)

  1. 一种切片业务配置方法，包括：
    获取对应于切片业务的切片配置信息；
    获取与业务网元对应的网元配置模板，所述业务网元与所述切片业务关联；
    根据所述切片配置信息和所述网元配置模板得到执行所述切片业务所需的网元配置数据；以及
    向所述业务网元发送所述网元配置数据。
  2. 根据权利要求1所述的切片业务配置方法，其中，所述获取对应于切片业务的切片配置信息，包括：
    接收来自第一切片业务开通装置的第一配置请求信息，所述第一配置请求信息携带有用于表征所述切片业务的配置要求的第一规划信息；
    根据所述第一配置请求信息中的所述第一规划信息，获取符合所述切片业务的配置要求的切片配置信息。
  3. 根据权利要求1所述的切片业务配置方法，其中，所述获取与业务网元对应的网元配置模板，包括：
    向第二切片管理装置发送数据获取指令；
    接收由所述第二切片管理装置根据所述数据获取指令发送的与所述业务网元对应的网元配置模板。
  4. 根据权利要求1所述的切片业务配置方法，其中，所述根据所述切片配置信息和所述网元配置模板得到执行所述切片业务所需的网元配置数据，包括:
    根据所述网元配置模板和预置的映射规则，将所述切片配置信息转换为适配所述网元配置模板的映射参数；
    根据所述映射参数得到执行所述切片业务所需的网元配置数据。
  5. 根据权利要求1所述的切片业务配置方法，其中，所述向所述业务网元发送所述网元配置数据，包括：
    接收来自第二切片业务开通装置的第二配置请求信息，所述第二切片业务开通装置与所述业务网元关联；
    根据所述第二配置请求信息向第二切片管理装置发送携带有所述网元配置数据的下发配置请求，以使所述第二切片管理装置根据所述下发配置请求向所述业务网元发送所述网元配置数据。
  6. 根据权利要求1至4任意一项所述的切片业务配置方法，其中，所述切片配置信息包括如下类型中的至少一种:
    业务配置参数信息；或
    网络资源拓扑信息；或
    切片配置策略信息。
  7. 一种切片业务配置方法，包括：
    接收来自第一切片管理装置的数据获取指令；
    根据所述数据获取指令向所述第一切片管理装置发送与业务网元对应的网元配置模板，使得所述第一切片管理装置根据所述网元配置模板和已获取到的切片配置信息，得到执行所述切片业务所需的网元配置数据，以及向所述业务网元发送所述网元配置数据；以及
    其中，所述切片配置信息对应于所述切片业务，所述业务网元与所述切片业务关联。
  8. 根据权利要求7所述的切片业务配置方法，其中，所述切片配置信息由所述第一切片管理装置通过以下步骤得到：
    接收来自第一切片业务开通装置的第一配置请求信息，所述第一配置请求信息携带有用于表征所述切片业务的配置要求的第一规划信息；
    根据所述第一配置请求信息中的所述第一规划信息，获取符合所述切片业务的配置要求的切片配置信息。
  9. 根据权利要求7或8所述的切片业务配置方法，其中，所述切片配置信息包括如下类型中的至少一种:
    业务配置参数信息；或
    网络资源拓扑信息；或
    切片配置策略信息。
  10. 一种切片业务配置方法，应用于网络***，所述网络***包括第一切片管理装置和第二切片管理装置，所述方法包括：
    所述第一切片管理装置获取对应于切片业务的切片配置信息，并向所述第二切片管理装置发送数据获取指令；
    所述第二切片管理装置接收来自第一切片管理装置的数据获取指令，并根据所述数据获取指令向所述第一切片管理装置发送与业务网元对应的网元配置模板；以及
    所述第一切片管理装置根据所述切片配置信息和所述网元配置模板，得到执行所述切片业务所需的网元配置数据，并向所述业务网元发送所述网元配置数据。
  11. 根据权利要求10所述的切片业务配置方法，其中，所述第一切片管理装置获取对应于切片业务的切片配置信息，包括：
    所述第一切片管理装置接收来自第一切片业务开通装置的第一配置请求信息，所述第一配置请求信息携带有用于表征所述切片业务的配置要求的第一规划信息；
    所述第一切片管理装置根据所述第一配置请求信息中的所述第一规划信息，获取符合所述切片业务的配置要求的切片配置信息。
  12. 根据权利要求10所述的切片业务配置方法，其中，所述第一切片管理装置根据所述切片配置信息和所述网元配置模板，得到执行所述切片业务所需的网元配置数据，包括：
    所述第一切片管理装置根据所述网元配置模板和预置的映射规则，将所述切片配置信息转换为适配所述网元配置模板的映射参数，并根据所述映射参数得到执行所述切片业务所需的网元配置数据。
  13. 根据权利要求10所述的切片业务配置方法，其中，所述第一切片管理装置向所述业务网元发送所述网元配置数据，包括：
    所述第一切片管理装置接收来自第二切片业务开通装置的第二配置请求信息，并根据所述第二配置请求信息，向所述第二切片管理装置发送携带有所述网元配置数据的下发配置请求，其中，所述第二切片业务开通装置与所述业务网元关联；
    所述第二切片管理装置接收所述下发配置请求，并根据所述下发配置请求向所述业务网元发送所述网元配置数据。
  14. 根据权利要求10至12任意一项所述的切片业务配置方法，其中，所述切片配置信息包括如下类型中的至少一种:
    业务配置参数信息；或
    网络资源拓扑信息；或
    切片配置策略信息。
  15. 一种网络设备，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现如权利要求1至9中任意一项所述的切片业务配置方法。
  16. 一种网络***，包括：第一切片管理装置和第二切片管理装置，所述第一切片管理装置和所述第二切片管理装置相互配合执行如权利要求10至14任意一项所述的切片业务配置方法。
  17. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1至9中任意一项所述的切片业务配置方法。
PCT/CN2022/091257 2021-09-30 2022-05-06 切片业务配置方法、网络设备、网络***及存储介质 WO2023050815A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111157690.8 2021-09-30
CN202111157690.8A CN115915146A (zh) 2021-09-30 2021-09-30 切片业务配置方法、网络设备、网络***及存储介质

Publications (1)

Publication Number Publication Date
WO2023050815A1 true WO2023050815A1 (zh) 2023-04-06

Family

ID=85729448

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/091257 WO2023050815A1 (zh) 2021-09-30 2022-05-06 切片业务配置方法、网络设备、网络***及存储介质

Country Status (2)

Country Link
CN (1) CN115915146A (zh)
WO (1) WO2023050815A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105517005A (zh) * 2014-10-17 2016-04-20 中兴通讯股份有限公司 可扩展的跨网元业务配置方法及***
CN109218047A (zh) * 2017-06-30 2019-01-15 ***通信有限公司研究院 网络切片处理方法及装置、通信***及存储介质
CN110138575A (zh) * 2018-02-02 2019-08-16 中兴通讯股份有限公司 网络切片创建方法、***、网络设备及存储介质
WO2020040752A1 (en) * 2018-08-21 2020-02-27 Nokia Technologies Oy Support for enterprise network slicing and flexible sub-slicing controlled by an enterprise
CN110476402B (zh) * 2017-05-22 2021-03-30 华为技术有限公司 网络切片创建的方法、装置以及通信***

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105517005A (zh) * 2014-10-17 2016-04-20 中兴通讯股份有限公司 可扩展的跨网元业务配置方法及***
CN110476402B (zh) * 2017-05-22 2021-03-30 华为技术有限公司 网络切片创建的方法、装置以及通信***
CN109218047A (zh) * 2017-06-30 2019-01-15 ***通信有限公司研究院 网络切片处理方法及装置、通信***及存储介质
CN110138575A (zh) * 2018-02-02 2019-08-16 中兴通讯股份有限公司 网络切片创建方法、***、网络设备及存储介质
WO2020040752A1 (en) * 2018-08-21 2020-02-27 Nokia Technologies Oy Support for enterprise network slicing and flexible sub-slicing controlled by an enterprise

Also Published As

Publication number Publication date
CN115915146A (zh) 2023-04-04

Similar Documents

Publication Publication Date Title
US11296957B2 (en) Network slice management method, unit, and system
WO2019113486A1 (en) Local profile assistant and application programming interface
CN108282363B (zh) Cpe和acs的远程配置方法、装置以及***
US10148486B2 (en) Object version management
US11785121B2 (en) Selecting protocol adaptor in a communication network
CN108370329B (zh) 管理功能对象的管理方法及装置
WO2023050815A1 (zh) 切片业务配置方法、网络设备、网络***及存储介质
CN110620754B (zh) Nf所需资源的部署方法、装置、存储介质及电子装置
WO2022247420A1 (zh) 配置模板生成方法、网元配置方法及其***、存储介质
US9253022B2 (en) Managed object version identification
CN110134467B (zh) 参数配置的处理方法、装置、存储介质及处理器
WO2023061200A1 (zh) 网络切片资源编排方法、网络设备及存储介质
CN102724076A (zh) 北向全参数处理方法及装置
CN115250236B (zh) 网元指令适配方法、装置、***、电子设备及存储介质
TWI798807B (zh) 行固網整合ｉｐ位址資源管理系統、方法及電腦可讀媒介
WO2022041279A1 (zh) 物联网中的设备管理方法、装置、计算机设备及存储介质
US20230409371A1 (en) Method for creating network service ns and related apparatus
CN111581203B (zh) 信息处理方法、装置及存储介质
WO2023173939A1 (zh) 基站的配置数据迁移方法、计算机设备和存储介质
WO2021012905A1 (zh) Vnfd多版本兼容处理方法、装置、设备及存储介质
CN102546237B (zh) 设备管理服务器、客户端及目标操作对象定位方法
CN118175039A (zh) 一种网元指令的更新方法及装置
CN117956017A (zh) 一种提供业务数据的方法及相关装置
CN117411784A (zh) 一种信息处理方法、装置、设备及可读存储介质
CN115866645A (zh) 一种小基站的管理方法和***

Legal Events

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

Ref document number: 22874213

Country of ref document: EP

Kind code of ref document: A1