CN112817688B - Network slice template generation method and device - Google Patents
Network slice template generation method and device Download PDFInfo
- Publication number
- CN112817688B CN112817688B CN201911121915.7A CN201911121915A CN112817688B CN 112817688 B CN112817688 B CN 112817688B CN 201911121915 A CN201911121915 A CN 201911121915A CN 112817688 B CN112817688 B CN 112817688B
- Authority
- CN
- China
- Prior art keywords
- class
- object list
- network
- network element
- corresponding parameters
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45562—Creating, deleting, cloning virtual machine instances
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
Abstract
The embodiment of the application provides a method and a device for generating a network slice template, wherein the method comprises the following steps: receiving a network slice template generation request, wherein the network slice template generation request comprises service characteristics; generating template configuration form data according to the service characteristics, wherein the template configuration form data comprises abstract categories and corresponding parameters; and generating a network slice template in the JSON format according to the abstract category and the corresponding parameters. By editing the service characteristics of the network slice into the template configuration form data containing sampling types and corresponding parameters and converting the template configuration form data into the network slice template in the JSON format, the method simplifies the step of planning the network slice template and improves the planning efficiency of the network slice template while improving the readability of planning the network slice template.
Description
Technical Field
The present application relates to the field of network virtualization technologies, and in particular, to a method and an apparatus for generating a network slice template.
Background
Network slicing is the creation of virtual networks of a particular network topology on a pool of network resources based on the demands of typical traffic for network functions and the resource demands for the network. The core network of mobile communication is an application, the running environment of the virtualized core network is actually a universal virtual machine, and the deployment of a set of core network slices is opened, namely, the running planned network resources, computing resources and storage resources are informed to the cloud platform, so that the virtual machine and the deployment and running of network element programs can be established.
At present, a network slice template based on a JSON format (JavaScript Object Notation, a lightweight data exchange format) is generally established based on an OpenStack (an open source cloud management system) so as to be easy for people to read and write, and easy for a machine to analyze and generate, and effectively improve network transmission efficiency, so that planning of network slice data is realized. These data are defined in the form of templates in the JSON format in the format of key-value pairs, and often a core network slice contains multiple network elements, resulting in a lot of planning data. The OpenStack is usually formed by planning three types of template data, namely a slicing template, a network service template and a virtualized network function template, wherein the data of the network service template is defined in the slicing template, the data of the virtualized network function template is defined in the network service template, and the data of the virtualized network function template defines the data of the virtual network function component.
Obviously, the template planning mode has a complex structure, when the planned network slice is large, the actual operation steps are very complicated, the efficiency of planning the network slice template is reduced, and the planning mode is poor in readability because the planning mode is directly edited based on the JSON format.
Disclosure of Invention
In view of the foregoing, the present application has been made to provide a network slice template generation method and apparatus that solve or at least partially solve the foregoing problems.
According to a first aspect of the present application, there is provided a network slice template generation method, including:
receiving a network slice template generation request, wherein the network slice template generation request comprises service characteristics;
generating template configuration form data according to the service characteristics, wherein the template configuration form data comprises abstract categories and corresponding parameters;
and generating a network slice template in the JSON format according to the abstract category and the corresponding parameters.
Optionally, the abstract category includes at least: the method comprises the steps of sharing a deployment unit class, a network element sub-instance class, a network element function class, a virtual machine parameter class, a connection class, a mirror image parameter class, a mirror image monitoring class, a private network class, a public subnet class, a private subnet class, a network element monitoring class and a link class.
Optionally, the step of generating the JSON-format network slice template according to the abstract category and the corresponding parameters includes:
creating a network element description file according to the network element function class and the corresponding parameters;
Creating a network element monitoring object list according to the network element monitoring class and the corresponding parameters;
creating a mirror image object list according to the mirror image parameter class and the corresponding parameters;
creating a mirror image monitoring object list according to the mirror image monitoring class and the corresponding parameters;
creating a public subnet object list according to the public subnet class and the corresponding parameters;
creating a private network object list according to the private network class and the corresponding parameters;
creating a private subnet object list according to the private subnet class and the corresponding parameters;
creating a deployment unit object list according to the shared deployment unit class and the corresponding parameters;
creating a network element sub-instance object list according to the network element sub-instance class and the corresponding parameters;
creating a virtual machine object list according to the virtual machine parameter class and the corresponding parameters;
creating a connection relation list according to the connection class and the corresponding parameters;
creating a service relation list according to the link class and the corresponding parameters;
and obtaining a network slice template in the JSON format according to the network element description file, the network element monitoring object list, the mirror image monitoring object list, the public subnet object list, the private network object list, the private subnet object list, the deployment unit object list, the network element sub-instance object list, the virtual machine object list, the connection relation list and the service relation list.
Optionally, the step of obtaining the network slice template in JSON format according to the network element description file, the network element monitoring object list, the mirror image monitoring object list, the public subnet object list, the private network object list, the private subnet object list, the deployment unit object list, the network element sub-instance object list, the virtual machine object list, the connection relation list and the service relation list includes:
encapsulating the connection relation list and the virtual machine object list into a network element sub-instance list;
encapsulating the encapsulated network element sub-instance object list into a virtual deployment unit object list;
encapsulating the mirror image monitoring file and the encapsulated virtual deployment unit object list into a mirror image description file;
and encapsulating the monitoring description file, the service relation list, the public subnet object list, the private network object list, the private subnet object list and the encapsulated mirror image description file into a network element description file to obtain a network slice template in a JOSN format.
Optionally, after the step of generating the JSON-format network slice template according to the abstract class and the corresponding parameters, the method further includes:
And generating a network slice to a network function virtualization orchestrator according to the network slice template, so that the network function virtualization orchestrator generates the network slice according to the network.
Optionally, the step of generating template configuration form data according to the service features includes:
filling each abstract category in the network slice configuration form template according to the service characteristics to obtain template configuration form data, wherein the abstract categories correspond to the service characteristics.
According to a second aspect of the present application, there is provided a network slice template generation apparatus comprising:
the receiving module is used for receiving a network slice template generation request, wherein the network slice template generation request comprises service characteristics;
the first generation module is used for generating template configuration form data according to the service characteristics, wherein the template configuration form data comprises abstract categories and corresponding parameters;
and the second generation module is used for generating a network slice template in the JSON format according to the abstract category and the corresponding parameters.
Optionally, the abstract category includes at least: the method comprises the steps of sharing a deployment unit class, a network element sub-instance class, a network element function class, a virtual machine parameter class, a connection class, a mirror image parameter class, a mirror image monitoring class, a private network class, a public subnet class, a private subnet class, a network element monitoring class and a link class.
Optionally, the second generating module includes:
a first creation sub-module, configured to create a network element description file according to the network element function class and the corresponding parameters;
a second creating sub-module, configured to create a network element monitoring object list according to the network element monitoring class and the corresponding parameters;
a third creation sub-module for creating a mirror image object list according to the mirror image parameter class and the corresponding parameters;
a fourth creation sub-module, configured to create a mirror image monitoring object list according to the mirror image monitoring class and the corresponding parameters;
a fifth creation sub-module, configured to create a public subnet object list according to the public subnet class and the corresponding parameters;
a sixth creation sub-module, configured to create a private network object list according to the private network class and the corresponding parameters;
a seventh creation sub-module, configured to create a private subnet object list according to the private subnet class and the corresponding parameters;
an eighth creation sub-module, configured to create a deployment unit object list according to the shared deployment unit class and the corresponding parameters;
a ninth creation sub-module, configured to create a network element sub-instance object list according to the network element sub-instance class and the corresponding parameters;
A tenth creation sub-module, configured to create a virtual machine object list according to the virtual machine parameter class and the corresponding parameters;
an eleventh creation sub-module, configured to create a connection relationship list according to the connection class and the corresponding parameter;
a twelfth creation sub-module for creating a service relationship list according to the link class and the corresponding parameters;
and the generation sub-module is used for obtaining a network slice template in a JSON format according to the network element description file, the network element monitoring object list, the mirror image monitoring object list, the public subnet object list, the private network object list, the private subnet object list, the deployment unit object list, the network element sub-example object list, the virtual machine object list, the connection relation list and the business relation list.
Optionally, the generating sub-module includes:
the first encapsulation unit is used for encapsulating the connection relation list and the virtual machine object list into a network element sub-instance list;
the second encapsulation unit is used for encapsulating the encapsulated network element sub-instance object list into the virtual deployment unit object list;
the third encapsulation unit is used for encapsulating the mirror image monitoring file and the encapsulated virtual deployment unit object list into the mirror image description file;
And the fourth encapsulation unit is used for encapsulating the monitoring description file, the service relation list, the public subnet object list, the private network object list, the private subnet object list and the encapsulated mirror image description file into the network element description file to obtain a network slice template in a JOSN format.
Optionally, the apparatus further includes:
and the third generation module is used for virtualizing the orchestrator to the network function according to the network slice template, so that the network function virtualizing orchestrator generates the network slice according to the network.
Optionally, the first generating module includes:
and the filling sub-module is used for filling each abstract category in the network slice configuration form template according to the service characteristics to obtain template configuration form data, wherein the abstract categories correspond to the service characteristics.
The embodiment of the application has the following advantages:
the embodiment of the application provides a method and a device for generating a network slice template, wherein the method comprises the following steps: receiving a network slice template generation request, wherein the network slice template generation request comprises service characteristics; generating template configuration form data according to the service characteristics, wherein the template configuration form data comprises abstract categories and corresponding parameters; and generating a network slice template in the JSON format according to the abstract category and the corresponding parameters. By editing the service characteristics of the network slice into the template configuration form data containing sampling types and corresponding parameters and converting the template configuration form data into the network slice template in the JSON format, the method simplifies the step of planning the network slice template and improves the planning efficiency of the network slice template while improving the readability of planning the network slice template.
The foregoing description is only an overview of the present application, and is intended to be implemented in accordance with the teachings of the present application in order that the same may be more clearly understood and to make the same and other objects, features and advantages of the present application more readily apparent.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the application. Also, like reference numerals are used to designate like parts throughout the figures. In the drawings:
FIG. 1 shows a flow chart of steps of a network slice template generation method according to the present application;
FIG. 2 shows a flow chart of steps of a method of generating a network slice template in JSON format in accordance with the present application;
FIG. 3 shows a flow chart of steps of another method of generating a network slice template in JSON format in accordance with the present application;
FIG. 4 illustrates a network slice template encapsulation logic diagram in a network slice template generation method in accordance with the present application;
FIG. 5 shows a flow chart of steps of a network slice generation method according to the present application;
fig. 6 shows a block diagram of a network slice template generation apparatus according to the present application.
Detailed Description
Exemplary embodiments of the present application will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the application to those skilled in the art.
Example 1
Referring to fig. 1, a flowchart illustrating steps of a network slice template generation method according to the present application may specifically include the following steps:
step 101, receiving a network slice template generation request, wherein the network slice template generation request comprises service characteristics.
In the embodiment of the application, a user can generate a network slice template generation request through a user interface, and can input service characteristics containing the network slice template to be generated according to own requirements, wherein the service characteristics can contain information related to basic planning requirements of the network slice template, such as network function types, mirror image requirements, interface parameters, connection relations, network performance requirements and the like.
And 102, generating template configuration form data according to the service characteristics, wherein the template configuration form data comprises abstract categories and corresponding parameters.
Optionally, the abstract category includes at least: the method comprises the steps of sharing a deployment unit class, a network element sub-instance class, a network element function class, a virtual machine parameter class, a connection class, a mirror image parameter class, a mirror image monitoring class, a private network class, a public subnet class, a private subnet class, a network element monitoring class and a link class.
In the embodiment of the invention, the relevant data related to the network slicing template is divided into a plurality of abstract types, the input area corresponding to each abstract type is displayed through the user interface for users to fill in business features according to actual demands, so that the input business features are generated into the template configuration form data in the EXCEL format, the operability of the input configuration of the network slicing template in the planning process is improved, the template configuration form data is more visual compared with the conventional mode of directly configuring the file in the JSON format, the readability of the network slicing template in the planning process is improved, and the user is facilitated to search and change the planned network slicing template.
Specifically, the abstract categories included in the template configuration table data may at least include:
1. a shared deployment unit class (vdu) (Virtual deploy unit) that a user defines mirror types, resource requirements, etc. of network elements of different classes, the shared deployment unit class corresponding to at least the following parameters:
vnfd-id (virtualized network function module descriptor id), vdu-id (shared deployment unit id), vdu-name (shared deployment unit name), vm-image-name (virtual machine image name), vm-affinity if_num (whether or not it is across numa), CPU-affinity, vm-flag-name (name of virtual machine specification), vm-flag-disk (disk size of virtual machine specification), vm-flag-vcpu (number of CPUs of virtual machine specification), vm-flag-mem (memory size of virtual machine specification).
2. A network element sub-instance class (VNF Component) for defining resource deployment requirements of a network element template instance, such as an aggregation group, a computing node, etc., where the network element sub-instance class corresponds to at least the following parameters:
the parameters include vnfc-id (network element sub-instance id), vnfc-name (network element sub-instance name), vim_id (text editor id), aggregate_name (aggregation group name), host_name (host file name).
3. A network element function class (vnf) (Virtual Network Function) for defining private information such as a network, a version, etc. to which the virtualized network belongs, where the network element function class at least corresponds to the following parameters:
vnfd-id (virtualized network function module descriptor id), vnfd-name (virtualized network function module descriptor name), vnfd_no (vnfd number), provider, version.
4. A virtual machine parameter class (metadata) for defining a network address, a name, location information of a network element sub-instance, etc. of a virtual machine, where the virtual machine parameter class corresponds to at least the following parameters:
vnfc-ID (ID of vnfc), vm_hostname (hostname of virtual machine), hostname (hostname of physical machine), global_type (global type), vnf_id (ID of vnnf), glboam_ip (global operation maintenance IP address), rest_ip (public network IP address), oam _ip (operation maintenance IP address), ctrl_ip (control plane IP address), sig_ip (signaling plane IP address), glb_ip (global board IP address), db_ip (database IP address), slice_id (slice ID), frame (frame), slot (slot), vnfm_rest (public network IP of VNFM), disk_on off (set switch), omc _ip (operation maintenance center IP address), monitor_agent (monitoring agent), nrf_ip (IP address of NRF network element).
5. A VNF-level network information set (connection-point-ref) for defining a network address, a network type, a port-network card relationship, etc. of a network element sub-instance, where the connection type at least corresponds to the following parameters:
vnfc-id (index value of vnfc), value (ip of connection point supporting manual class), refcp (network name connected to), type-bandwidth (connection mode and bandwidth), sr_iov (whether pass-through network card is set), portname (port name), priority (priority).
6. The mirror image parameter class (vnf-characteristics) is used for defining the type, attribute, belonging virtual deployment unit and the like of a corresponding mirror image in the virtualized network, and the mirror image parameter class at least corresponds to the following parameters:
vnfd-ID (primary key index value of VNF), VNF-flavour-ID (virtual machine specification ID of VNF), VNF-flavour-name (virtual machine specification name of VNF), vnname (virtual deployment unit name), vnfcnumber (number of VNFCs).
7. Mirror monitoring class (vnf-rotations-tasks-parameters) for defining trust parameters, left values, right values, etc. of the mirror, said mirror monitoring class corresponding to at least the following parameters:
VNF-flavor-ID (virtual machine specification ID of VNF), leftvalue (left threshold), lightvalue (right threshold), param-ID (primary key of parameter).
8. Private network class (private-network) for defining private networks of network slices and cloud platforms, the private network class corresponding to at least the following parameters:
vnfd-ID (primary key index value of VNF), nettype (network type), connect-point-name (network name of connection), provider-network name, segment ID (ID value of virtual local area network).
9. Public-subnet class (public-subnet) for defining public subnets, network segment addresses, masks, etc. of the network slice and the cloud platform, wherein the public subnet class rarely corresponds to the following parameters:
vnfd-id (primary key index value of VNF), subnet name, startip (subnet mask), start (start ip), end (end ip).
10. Private subnet class (private-subnet) for defining private subnets, network segment addresses, masks, etc. of the network slice and the cloud platform, the private subnet class corresponding to at least the following parameters:
vnfd-id (primary key index value of VNF), subnetname (subnet name), startip subnet mask), start (start ip), end (end ip).
11. A network element monitoring class (vnf-monitoring-params) for defining monitoring parameters, thresholds, etc. of the virtualized network, wherein the network element monitoring class at least corresponds to the following parameters:
vnfd-id (primary key index value of VNF), param-id (primary key of parameter), enable (whether available), target (target object), left-value (left value), right-value (right value), vnfc-number (number of vnfcs).
12. A link class (vls) for defining a connection relationship between a virtual link and a network element, said link class corresponding to at least the following parameters:
vnfd-id (primary key index value of VNF), from point, toPoint.
And step 103, generating a network slice template in the JSON format according to the abstract category and the corresponding parameters.
In the embodiment of the invention, the template configuration table data is called by establishing a function model which converts the data in the EXCEL format into the JSON format, corresponding codes are generated according to abstract categories in the template configuration table data, and the abstract categories are loaded by utilizing parameters corresponding to the abstract categories so as to compile and generate the network slice template in the JSON format. The calling functions in the function model can set the execution sequence and the sequence relation between the calling functions according to the logic relation of the network slices, and the network slice template in the JSON format can be gradually constructed by adopting the sequences of the slices, the virtual network functions and the network services.
Optionally, referring to fig. 2, the step 103 includes:
and step A1, a network element description file is created according to the network element function class and the corresponding parameters.
And step A2, a network element monitoring object list is created according to the network element monitoring class and the corresponding parameters.
And step A3, creating a mirror image object list according to the mirror image parameter class and the corresponding parameters.
And step A4, creating a mirror image monitoring object list according to the mirror image monitoring class and the corresponding parameters.
And step A5, creating a public subnet object list according to the public subnet class and the corresponding parameters.
And step A6, creating a private network object list according to the private network class and the corresponding parameters.
And step A7, creating a private subnet object list according to the private subnet class and the corresponding parameters.
And step A8, creating a deployment unit object list according to the shared deployment unit class and the corresponding parameters.
And step A9, a network element sub-instance object list is created according to the network element sub-instance class and the corresponding parameters.
And step A10, creating a virtual machine object list according to the virtual machine parameter class and the corresponding parameters.
And step A11, creating a connection relation list according to the connection class and the corresponding parameters.
And step A12, creating a service relation list according to the link class and the corresponding parameters.
And step A13, according to the network element description file, the network element monitoring object list, the mirror image monitoring object list, the public subnet object list, the private network object list, the private subnet object list, the deployment unit object list, the network element sub-instance object list, the virtual machine object list, the connection relation list and the business relation list, obtaining a network slice template in a JSON format.
In the embodiment of the invention, the shared deployment unit class, the network element sub-instance class, the network element function class, the virtual machine parameter class, the connection class, the mirror image parameter class, the mirror image monitoring class, the private network class, the public sub-network class, the private sub-network class, the network element monitoring class, the link class and the corresponding parameters are converted into the network element description file, the network element monitoring object list, the mirror image monitoring object list, the public sub-network object list, the private sub-network object list, the deployment unit object list, the network element sub-instance object list, the virtual machine object list, the connection relation list and the service relation list in a preset hierarchical order to be packaged into the network slicing template in the JSON format, so that the steps required for planning the network slicing template are simplified, and the planning efficiency of the network slicing template is improved.
Specifically, the function model may include the following call functions:
1→createvnfs()
2→create_monitoring_params()
3→create_vnf_flavours()
3.1→create_vnf_flavours_assurance_params()
4→create_public_subnets()
5→create_private_subnets()
6→create_private_subnets()
7→create_vdus()
8→create_vnfcs()
8.1→create_vnfc_matadata()
9→create_connection-point()
10→create_vls()
specifically, the calling function is shown in Table 1 below
TABLE 1
Optionally, referring to fig. 3, the step a13 includes:
and step B1, packaging the connection relation list and the virtual machine object list into a network element sub-instance list.
And step B2, encapsulating the encapsulated network element sub-instance object list into a virtual deployment unit object list.
And step B3, encapsulating the mirror image monitoring file and the encapsulated virtual deployment unit object list into a mirror image description file.
And step B4, packaging the monitoring description file, the service relation list, the public subnet object list, the private network object list, the private subnet object list and the packaged mirror image description file into a network element description file to obtain a network slice template in a JOSN format.
In the embodiment of the present invention, referring to fig. 4, the generated network element description file, network element monitoring object list, mirror image monitoring object list, public subnet object list, private network object list, private subnet object list, deployment unit object list, network element sub-instance object list, virtual machine object list, connection relationship list, and service relationship list in JSON format are encapsulated according to the logical relationship described in fig. 4, so as to obtain the network slice template in JSON format. The function functions in table 1 above are used to generate the data in fig. 4 to construct a network slice template in JOSN format, in particular, the createsnfs function is used to generate the VNF, the create_monitoring_parameters function is used for generating the VNF-monitoring-parameters, and the create_vnf_parameters function is used for generating the parameters: the method comprises the steps that small, the create_vnf_flat_assurface_parameters function is used for generating the vnf-flat_assurface_parameters, the create_private_networks function is used for generating the private_networks, the create_public_networks function is used for generating the Public-networks, the create_private_networks function is used for generating the Private-networks, the create_reduce function is used for generating the vdu, the create_vnfc function is used for generating the vnfc, the create_vnfc_matata function is used for generating the matadate, the create_vls function is used for generating the Public-networks, and the create_connection-point function is used for generating the Private-networks.
Optionally, referring to fig. 5, on the basis of a network slice template generating method described in fig. 1, the step 102 includes:
sub-step 1021, filling each abstract category in the network slice configuration form template according to the service characteristics to obtain template configuration form data, wherein the abstract categories correspond to the service characteristics.
In the embodiment of the invention, the network slice configuration form template is in a form of an EXCEL format, wherein rows or columns can correspond to abstract categories, and after a user inputs service features, filling areas corresponding to the abstract categories in the network slice configuration form template can be filled according to the corresponding relation between the service features and the abstract categories, and the template configuration form data can be obtained after filling is completed.
Optionally, referring to fig. 5, after the step 103, on the basis of a network slice template generating method described in fig. 1, the method further includes:
step 104, according to the network slice template, the network function virtualization orchestrator is configured to generate a network slice according to the network.
In an embodiment of the present invention, a user may select a generated network slice template through an input interface to create a network slice generation instruction, and send the network slice generation instruction to a NFVO (Network Function Virtualization Orchestrator, virtual network function orchestrator) of a MANO (Management and Orchestration, an architecture framework for managing and coordinating virtualized network functions and other software components), so that the MANO issues the network slice template to a cloud platform to generate a network slice.
The embodiment of the application provides a network slice template generation method, which comprises the following steps: receiving a network slice template generation request, wherein the network slice template generation request comprises service characteristics; generating template configuration form data according to the service characteristics, wherein the template configuration form data comprises abstract categories and corresponding parameters; and generating a network slice template in the JSON format according to the abstract category and the corresponding parameters. By editing the service characteristics of the network slice into the template configuration form data containing sampling types and corresponding parameters and converting the template configuration form data into the network slice template in the JSON format, the method simplifies the step of planning the network slice template and improves the planning efficiency of the network slice template while improving the readability of planning the network slice template.
Example two
Referring to fig. 6, there is shown a network slice template generating apparatus according to the present application, comprising:
the receiving module 201 is configured to receive a network slice template generation request, where the network slice template generation request includes a service feature.
A first generation module 202 is configured to generate template configuration table data according to the service features, where the template configuration table data includes abstract categories and corresponding parameters.
Optionally, the first generating module 202 includes:
and a filling submodule 2021, configured to fill each abstract category in the network slice configuration form template according to the service feature, so as to obtain template configuration form data, where the abstract category corresponds to the service feature.
And the second generation module 203 is configured to generate a JSON-format network slice template according to the abstract class and the corresponding parameters.
Optionally, the abstract category includes at least: the method comprises the steps of sharing a deployment unit class, a network element sub-instance class, a network element function class, a virtual machine parameter class, a connection class, a mirror image parameter class, a mirror image monitoring class, a private network class, a public subnet class, a private subnet class, a network element monitoring class and a link class.
Optionally, the second generating module 203 includes:
a first creating sub-module C1, configured to create a network element description file according to the network element function class and the corresponding parameters.
And the second creating sub-module C2 is used for creating a network element monitoring object list according to the network element monitoring class and the corresponding parameters.
And a third creation sub-module C3, configured to create a mirror image object list according to the mirror image parameter class and the corresponding parameter.
And a fourth creation sub-module C4, configured to create a mirror image monitoring object list according to the mirror image monitoring class and the corresponding parameters.
And a fifth creation sub-module C5, configured to create a public subnet object list according to the public subnet class and the corresponding parameters.
And a sixth creation sub-module C6, configured to create a private network object list according to the private network class and the corresponding parameters.
And a seventh creation sub-module C7, configured to create a private subnet object list according to the private subnet class and the corresponding parameters.
An eighth creation sub-module C8 is configured to create a deployment unit object list according to the shared deployment unit class and the corresponding parameters.
And a ninth creating sub-module C9, configured to create a network element sub-instance object list according to the network element sub-instance class and the corresponding parameters.
A tenth creation sub-module C10, configured to create a virtual machine object list according to the virtual machine parameter class and the corresponding parameters.
An eleventh creating sub-module C11 is configured to create a connection relationship list according to the connection class and the corresponding parameters.
A twelfth creation sub-module C12 is configured to create a service relationship list according to the link class and the corresponding parameters.
And the generation sub-module C13 is used for obtaining a network slice template in a JSON format according to the network element description file, the network element monitoring object list, the mirror image monitoring object list, the public subnet object list, the private network object list, the private subnet object list, the deployment unit object list, the network element sub-instance object list, the virtual machine object list, the connection relation list and the service relation list.
Optionally, the generating sub-module C13 includes:
the first encapsulation unit D1 is configured to encapsulate the connection relationship list and the virtual machine object list into a network element sub-instance list.
And the second encapsulation unit D2 is configured to encapsulate the encapsulated network element sub-instance object list into the virtual deployment unit object list.
And the third encapsulation unit D3 is used for encapsulating the image monitoring file and the encapsulated virtual deployment unit object list into the image description file.
And a fourth encapsulation unit D4, configured to encapsulate the monitoring description file, the service relationship list, the public subnet object list, the private network object list, the private subnet object list, and the encapsulated mirror image description file into a network element description file, to obtain a network slice template in the JOSN format.
A third generating module 204 is configured to virtualize the orchestrator to a network function according to the network slice template, so that the network function virtualizing orchestrator generates a network slice according to the network.
The embodiment of the application provides a network slice generation device, which comprises: the receiving module is used for receiving a network slice template generation request, wherein the network slice template generation request comprises service characteristics; the first generation module is used for generating template configuration form data according to the service characteristics, wherein the template configuration form data comprises abstract categories and corresponding parameters; and the second generation module is used for generating a network slice template in the JSON format according to the abstract category and the corresponding parameters. By editing the service characteristics of the network slice into the template configuration form data containing sampling types and corresponding parameters and converting the template configuration form data into the network slice template in the JSON format, the method simplifies the step of planning the network slice template and improves the planning efficiency of the network slice template while improving the readability of planning the network slice template.
For the device embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference is made to the description of the method embodiments for relevant points.
The algorithms and displays presented herein are not inherently related to any particular computer, virtual system, or other apparatus. Various general-purpose systems may also be used with the teachings herein. The required structure for a construction of such a system is apparent from the description above. In addition, the present application is not directed to any particular programming language. It will be appreciated that the teachings of the present application described herein may be implemented in a variety of programming languages, and the above description of specific languages is provided for disclosure of enablement and best mode of the present application.
In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the application may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the above description of exemplary embodiments of the application, various features of the application are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be construed as reflecting the intention that: i.e., the claimed application requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this application.
Those skilled in the art will appreciate that the modules in the apparatus of the embodiments may be adaptively changed and disposed in one or more apparatuses different from the embodiments. The modules or units or components of the embodiments may be combined into one module or unit or component and, furthermore, they may be divided into a plurality of sub-modules or sub-units or sub-components. Any combination of all features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or units of any method or apparatus so disclosed, may be used in combination, except insofar as at least some of such features and/or processes or units are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings), may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features but not others included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the application and form different embodiments. For example, in the following claims, any of the claimed embodiments can be used in any combination.
Various component embodiments of the application may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that some or all of the functions of some or all of the components in a network slice generating apparatus according to embodiments of the present application may be implemented in practice using a microprocessor or Digital Signal Processor (DSP). The present application can also be implemented as an apparatus or a base station program (e.g., a computer program and a computer program product) for performing a part or all of the methods described herein. Such a program embodying the present application may be stored on a computer readable medium, or may have the form of one or more signals. Such signals may be downloaded from an internet website, provided on a carrier signal, or provided in any other form.
It should be noted that the above-mentioned embodiments illustrate rather than limit the application, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The application may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several base stations, several of these base stations can be embodied by one and the same item of hardware. The use of the words first, second, third, etc. do not denote any order. These words may be interpreted as names.
Claims (5)
1. A network slice template generation method, comprising:
receiving a network slice template generation request, wherein the network slice template generation request comprises service characteristics;
generating template configuration form data according to the service characteristics, wherein the template configuration form data comprises abstract categories and corresponding parameters;
generating a network slice template in a JSON format according to the abstract class and the corresponding parameters;
wherein the abstract categories include at least: a shared deployment unit class, a network element sub-instance class, a network element function class, a virtual machine parameter class, a connection class, a mirror image parameter class, a mirror image monitoring class, a private network class, a public subnet class, a private subnet class, a network element monitoring class and a link class;
the step of generating template configuration form data according to the service characteristics comprises the following steps:
filling each abstract category in the network slice configuration form template according to the service characteristics to obtain template configuration form data, wherein the abstract categories correspond to the service characteristics;
the step of generating the network slice template in the JSON format according to the abstract category and the corresponding parameters comprises the following steps:
creating a network element description file according to the network element function class and the corresponding parameters;
Creating a network element monitoring object list according to the network element monitoring class and the corresponding parameters;
creating a mirror image object list according to the mirror image parameter class and the corresponding parameters;
creating a mirror image monitoring object list according to the mirror image monitoring class and the corresponding parameters;
creating a public subnet object list according to the public subnet class and the corresponding parameters;
creating a private network object list according to the private network class and the corresponding parameters;
creating a private subnet object list according to the private subnet class and the corresponding parameters;
creating a deployment unit object list according to the shared deployment unit class and the corresponding parameters;
creating a network element sub-instance object list according to the network element sub-instance class and the corresponding parameters;
creating a virtual machine object list according to the virtual machine parameter class and the corresponding parameters;
creating a connection relation list according to the connection class and the corresponding parameters;
creating a service relation list according to the link class and the corresponding parameters;
and obtaining a network slice template in the JSON format according to the network element description file, the network element monitoring object list, the mirror image monitoring object list, the public subnet object list, the private network object list, the private subnet object list, the deployment unit object list, the network element sub-instance object list, the virtual machine object list, the connection relation list and the service relation list.
2. The method according to claim 1, wherein the step of obtaining the JSON-format network slice template according to the network element description file, the network element monitoring object list, the mirror image monitoring object list, the public subnet object list, the private network object list, the private subnet object list, the deployment unit object list, the network element sub-instance object list, the virtual machine object list, the connection relation list, and the service relation list includes:
encapsulating the connection relation list and the virtual machine object list into a network element sub-instance list;
encapsulating the encapsulated network element sub-instance object list into a virtual deployment unit object list;
encapsulating the mirror image monitoring file and the encapsulated virtual deployment unit object list into a mirror image description file;
and encapsulating the monitoring description file, the service relation list, the public subnet object list, the private network object list, the private subnet object list and the encapsulated mirror image description file into the network element description file to obtain a network slice template in a JOSN format.
3. The method of claim 1, further comprising, after the step of generating a JSON-formatted web slice template from the abstract categories and corresponding parameters:
And sending a network slice generation instruction to a network function virtualization orchestrator according to the network slice template, so that the network function virtualization orchestrator generates a network slice according to the network.
4. A network slice template generation apparatus, comprising:
the receiving module is used for receiving a network slice template generation request, wherein the network slice template generation request comprises service characteristics;
the first generation module is used for generating template configuration form data according to the service characteristics, wherein the template configuration form data comprises abstract categories and corresponding parameters; the step of generating template configuration form data according to the service characteristics comprises the following steps:
filling each abstract category in the network slice configuration form template according to the service characteristics to obtain template configuration form data, wherein the abstract categories correspond to the service characteristics;
the second generation module is used for generating a network slice template in a JSON format according to the abstract category and the corresponding parameters;
wherein the abstract categories include at least: a shared deployment unit class, a network element sub-instance class, a network element function class, a virtual machine parameter class, a connection class, a mirror image parameter class, a mirror image monitoring class, a private network class, a public subnet class, a private subnet class, a network element monitoring class and a link class;
The second generation module includes:
a first creation sub-module, configured to create a network element description file according to the network element function class and the corresponding parameters;
a second creating sub-module, configured to create a network element monitoring object list according to the network element monitoring class and the corresponding parameters;
a third creation sub-module for creating a mirror image object list according to the mirror image parameter class and the corresponding parameters;
a fourth creation sub-module, configured to create a mirror image monitoring object list according to the mirror image monitoring class and the corresponding parameters;
a fifth creation sub-module, configured to create a public subnet object list according to the public subnet class and the corresponding parameters;
a sixth creation sub-module, configured to create a private network object list according to the private network class and the corresponding parameters;
a seventh creation sub-module, configured to create a private subnet object list according to the private subnet class and the corresponding parameters;
an eighth creation sub-module, configured to create a deployment unit object list according to the shared deployment unit class and the corresponding parameters;
a ninth creation sub-module, configured to create a network element sub-instance object list according to the network element sub-instance class and the corresponding parameters;
A tenth creation sub-module, configured to create a virtual machine object list according to the virtual machine parameter class and the corresponding parameters;
an eleventh creation sub-module, configured to create a connection relationship list according to the connection class and the corresponding parameter;
a twelfth creation sub-module for creating a service relationship list according to the link class and the corresponding parameters;
and the generation sub-module is used for obtaining a network slice template in a JSON format according to the network element description file, the network element monitoring object list, the mirror image monitoring object list, the public subnet object list, the private network object list, the private subnet object list, the deployment unit object list, the network element sub-example object list, the virtual machine object list, the connection relation list and the business relation list.
5. The apparatus of claim 4, wherein the generating sub-module comprises:
the first encapsulation unit is used for encapsulating the connection relation list and the virtual machine object list into a network element sub-instance list;
the second encapsulation unit is used for encapsulating the encapsulated network element sub-instance object list into the virtual deployment unit object list;
the third encapsulation unit is used for encapsulating the mirror image monitoring file and the encapsulated virtual deployment unit object list into the mirror image description file;
And the fourth encapsulation unit is used for encapsulating the monitoring description file, the service relation list, the public subnet object list, the private network object list, the private subnet object list and the encapsulated mirror image description file into the network element description file to obtain the network slice template in the JOSN format.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911121915.7A CN112817688B (en) | 2019-11-15 | 2019-11-15 | Network slice template generation method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911121915.7A CN112817688B (en) | 2019-11-15 | 2019-11-15 | Network slice template generation method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112817688A CN112817688A (en) | 2021-05-18 |
| CN112817688B true CN112817688B (en) | 2023-10-20 |
Family
ID=75851877
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911121915.7A Active CN112817688B (en) | 2019-11-15 | 2019-11-15 | Network slice template generation method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112817688B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20240022456A (en) * | 2021-09-30 | 2024-02-20 | 뉴 에이치3씨 테크놀로지스 코., 엘티디. | Message processing methods, devices, network devices and media |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102130958A (en) * | 2011-03-22 | 2011-07-20 | 宋健 | Method and system for video live broadcasting in small file slice mode based on hypertext transport protocol (HTTP) |
| WO2018089634A1 (en) * | 2016-11-11 | 2018-05-17 | Intel IP Corporation | Network slice management |
| CN108092789A (en) * | 2016-11-21 | 2018-05-29 | 华为技术有限公司 | The management method and device of network section template |
| CN108632058A (en) * | 2017-03-18 | 2018-10-09 | 华为技术有限公司 | The management method and device of network slice |
| CN108770016A (en) * | 2018-06-04 | 2018-11-06 | 北京邮电大学 | 5G end to end network slice generation method based on template and device |
| CN109600246A (en) * | 2017-09-30 | 2019-04-09 | 华为技术有限公司 | Network is sliced management method and its device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7900190B2 (en) * | 2006-09-21 | 2011-03-01 | Sap Ag | Business object templates |
-
2019
- 2019-11-15 CN CN201911121915.7A patent/CN112817688B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102130958A (en) * | 2011-03-22 | 2011-07-20 | 宋健 | Method and system for video live broadcasting in small file slice mode based on hypertext transport protocol (HTTP) |
| WO2018089634A1 (en) * | 2016-11-11 | 2018-05-17 | Intel IP Corporation | Network slice management |
| CN108092789A (en) * | 2016-11-21 | 2018-05-29 | 华为技术有限公司 | The management method and device of network section template |
| CN108632058A (en) * | 2017-03-18 | 2018-10-09 | 华为技术有限公司 | The management method and device of network slice |
| CN109600246A (en) * | 2017-09-30 | 2019-04-09 | 华为技术有限公司 | Network is sliced management method and its device |
| CN108770016A (en) * | 2018-06-04 | 2018-11-06 | 北京邮电大学 | 5G end to end network slice generation method based on template and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112817688A (en) | 2021-05-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9703660B2 (en) | Testing a virtualized network function in a network | |
| US10448242B2 (en) | Method and arrangement for on-boarding network service descriptions from various sources in a common service catalogue of NFV orchestration platform | |
| US10628276B2 (en) | Unit test framework for testing code in a gateway service | |
| CN108449418A (en) | A kind of mixed cloud platform management system and method | |
| US10291462B1 (en) | Annotations for intelligent data replication and call routing in a hierarchical distributed system | |
| US20160134487A1 (en) | Reconfiguring interrelationships between components of virtual computing networks | |
| CN107222324B (en) | Service configuration method and device of network service | |
| US10887414B2 (en) | Theme-based push notifications | |
| US10764242B2 (en) | Providing network address translation in a software defined networking environment | |
| CN108509254A (en) | The monitoring method and system of Docker Container | |
| CN109743205B (en) | Cloud platform OS network management method and device and server | |
| US20230254215A1 (en) | Method and system for edge data network (edn) lifecycle management | |
| US11005718B2 (en) | Determining capabilities of cognitive entities in a distributed network based on application of cognitive protocols | |
| US20140325077A1 (en) | Command management in a networked computing environment | |
| CN109814863A (en) | A kind of processing method, device, computer equipment and computer storage medium for requesting returned data | |
| US11025500B2 (en) | Provisioning infrastructure from visual diagrams | |
| Nkenyereye et al. | MEIX: Evolving multi-access edge computing for industrial Internet-of-Things services | |
| US10917478B2 (en) | Cloud enabling resources as a service | |
| CN112817688B (en) | Network slice template generation method and device | |
| EP4083795A1 (en) | Method for deploying virtual machine, and related apparatus | |
| CN106331024A (en) | Method and device for accessing cloud data | |
| CN116828035A (en) | Data integration system based on cloud computing | |
| US10168999B2 (en) | Software object definition and integration | |
| CN107404410B (en) | Method and device for constructing virtual network function platform in cloud environment | |
| US11570042B2 (en) | Software-defined network controller communication flow |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |