CN112817688A - Network slice template generation method and device - Google Patents
Network slice template generation method and device Download PDFInfo
- Publication number
- CN112817688A CN112817688A CN201911121915.7A CN201911121915A CN112817688A CN 112817688 A CN112817688 A CN 112817688A CN 201911121915 A CN201911121915 A CN 201911121915A CN 112817688 A CN112817688 A CN 112817688A
- Authority
- CN
- China
- Prior art keywords
- class
- object list
- network
- network element
- creating
- 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.)
- Granted
Links
Images
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
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
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 table data according to the service characteristics, wherein the template configuration table data comprises abstract categories and corresponding parameters; and generating a network slice template in a JSON format according to the abstract category and the corresponding parameters. By editing the service characteristics of the network slice into template configuration table data containing sampling categories and corresponding parameters and converting the template configuration table data into the network slice template in the JSON format, the readability of the network slice template planning is improved, the step of the network slice template planning is simplified, and the efficiency of the network slice template planning is improved.
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
A network slice is a virtual network that creates a particular network topology over a pool of network resources, based on the demands of typical traffic on the network's functionality and the resource demands on the network. The core network of the 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, network resources, computing resources and storage resources planned for running are informed to a cloud platform, so that the cloud platform can establish the deployment and running of the virtual machine and a network element program.
At present, a network slicing template based on a JSON format (JavaScript Object Notation), which is easy to read and write by a human, and is also easy to analyze and generate by a machine, and effectively improves network transmission efficiency) is generally established based on an OpenStack (an open source cloud management system) native cloud management system to realize the planning of network slicing data. The data are defined in a JSON format template in a template form and a key value pair format, and a core network slice usually comprises a plurality of network elements, so that planning data of the core network slice is various. OpenStack is generally formed by planning three types of template data, namely a slice template, a network service template and a virtualized network function template, wherein the slice template defines data of the network service template, and the network service template defines data of the virtualized network function template and the virtualized network function template defines data of a 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 the template planning of the network slice is reduced, and the readability is poor due to the fact that the planning mode is directly edited based on the JSON format.
Disclosure of Invention
In view of the above, the present application is proposed to provide a network slice template generating method and apparatus that solve the above problems or at least partially solve the above problems.
According to a first aspect of the present application, there is provided a method for generating a network slice template, including:
receiving a network slice template generation request, wherein the network slice template generation request comprises service characteristics;
generating template configuration table data according to the service characteristics, wherein the template configuration table data comprises abstract categories and corresponding parameters;
and generating a network slice template in a JSON format according to the abstract category and the corresponding parameters.
Optionally, the abstract categories at least include: the method comprises the following steps of shared deployment unit class, network element subinstance class, network element function class, virtual machine parameter class, connection class, mirror image parameter class, mirror image monitoring class, private network class, public subnetwork class, private subnetwork class, network element monitoring class and link class.
Optionally, the step of generating a JSON-formatted network slice template according to the abstract category and the corresponding parameter 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 subinstance object list according to the network element subinstance class and the corresponding parameters;
creating a virtual machine object list according to the virtual machine parameter classes and the corresponding parameters;
creating a connection relation list according to the connection classes and the corresponding parameters;
creating a service relation list according to the link classes and the corresponding parameters;
and 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 step of obtaining a JSON-formatted network slice template according to the network element description file, the network element monitoring object list, the mirror 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 relationship list, and the service relationship list includes:
packaging the connection relation list and the virtual machine object list into a network element sub-instance list;
packaging the packaged network element sub-instance object list into a virtual deployment unit object list;
packaging the mirror image monitoring file and the packaged virtual deployment unit object list into a mirror image description file;
and packaging 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 packaged 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 a JSON-format network slice template according to the abstract category and the corresponding parameter, the method further includes:
and a network function virtualization orchestrator is configured to generate a network slice 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 table data according to the service features includes:
and filling various abstract categories in the network slice configuration table template according to the service characteristics to obtain template configuration table 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 generating apparatus, including:
the system comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving a network slice template generation request which comprises service characteristics;
the first generation module is used for generating template configuration table data according to the service characteristics, wherein the template configuration table data comprises abstract categories and corresponding parameters;
and the second generation module is used for generating the network slice template in the JSON format according to the abstract category and the corresponding parameters.
Optionally, the abstract categories at least include: the method comprises the following steps of shared deployment unit class, network element subinstance class, network element function class, virtual machine parameter class, connection class, mirror image parameter class, mirror image monitoring class, private network class, public subnetwork class, private subnetwork class, network element monitoring class and link class.
Optionally, the second generating module includes:
the first creating submodule is used for creating a network element description file according to the network element function class and the corresponding parameters;
the second creating submodule is used for creating a network element monitoring object list according to the network element monitoring class and the corresponding parameters;
the third creating submodule is used for creating a mirror image object list according to the mirror image parameter class and the corresponding parameters;
the fourth creating submodule is used for creating a mirror image monitoring object list according to the mirror image monitoring class and the corresponding parameters;
a fifth creating submodule, configured to create a public subnet object list according to the public subnet class and the corresponding parameter;
a sixth creating submodule, configured to create a private network object list according to the private network class and the corresponding parameter;
a seventh creating sub-module, configured to create a private subnet object list according to the private subnet class and the corresponding parameter;
an eighth creating submodule, configured to create a deployment unit object list according to the shared deployment unit class and the corresponding parameter;
a ninth creating sub-module, configured to create a network element sub-instance object list according to the network element sub-instance class and the corresponding parameter;
a tenth creating submodule, configured to create a virtual machine object list according to the virtual machine parameter class and the corresponding parameter;
an eleventh creating submodule, configured to create a connection relation list according to the connection class and the corresponding parameter;
a twelfth creating submodule, configured to create a service relationship list according to the link class and the corresponding parameter;
and the generation submodule is used for obtaining a 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.
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 packaging unit is used for packaging the packaged 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 a mirror image description file;
and the fourth packaging unit is used for packaging 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 packaged mirror image description file into the network element description file to obtain the network slice template in the JOSN format.
Optionally, the apparatus further includes:
and the third generation module is used for 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 first generating module includes:
and the filling submodule is used for filling various abstract categories in the network slice configuration table template according to the service characteristics to obtain template configuration table 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 table data according to the service characteristics, wherein the template configuration table data comprises abstract categories and corresponding parameters; and generating a network slice template in a JSON format according to the abstract category and the corresponding parameters. By editing the service characteristics of the network slice into template configuration table data containing sampling categories and corresponding parameters and converting the template configuration table data into the network slice template in the JSON format, the readability of the network slice template planning is improved, the step of the network slice template planning is simplified, and the efficiency of the network slice template planning is improved.
The foregoing description is only an overview of the technical solutions of the present application, and the present application can be implemented according to the content of the description in order to make the technical means of the present application more clearly understood, and the following detailed description of the present application is given in order to make the above and other objects, features, and advantages of the present application more clearly understandable.
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 refer to like parts throughout the drawings. In the drawings:
FIG. 1 is a flow chart illustrating the steps of a method of network slice template generation according to the present application;
FIG. 2 is a flow chart illustrating the steps of a method of generating a network slice template in JSON format according to the present application;
FIG. 3 is a flow chart illustrating the steps of another method of generating a JSON formatted network slice template according to the present application;
FIG. 4 illustrates a network slice template encapsulation logic diagram in a network slice template generation method according to the present application;
FIG. 5 is a flow chart illustrating the steps of a method of network slice generation 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 disclosure to those skilled in the art.
Example one
Referring to fig. 1, a flowchart illustrating steps of a network slice template generation method according to the present application is shown, which may specifically include the following steps:
In the embodiment of the invention, a user can generate a network slicing template generation request through a user interface, and can input the service characteristics including the network slicing template required to be generated according to the self requirement, wherein the service characteristics can include information related to the basic planning requirement of the network slicing template, such as network function type, mirror image requirement, interface parameters, connection relation, network performance requirement and the like.
And 102, generating template configuration table data according to the service characteristics, wherein the template configuration table data comprises abstract categories and corresponding parameters.
Optionally, the abstract categories at least include: the method comprises the following steps of shared deployment unit class, network element subinstance class, network element function class, virtual machine parameter class, connection class, mirror image parameter class, mirror image monitoring class, private network class, public subnetwork class, private subnetwork class, network element monitoring class and link class.
In the embodiment of the invention, the related data related to the network slicing template is divided into a plurality of abstract categories, and the input area corresponding to each abstract category is displayed through the user interface so that a user can fill in the business characteristics according to the actual requirements, so that the input business characteristics generate template configuration table data in an EXCEL format, the operability of input configuration of the network slicing template in the planning process is improved, and the template configuration table data obtained in the mode is more intuitive compared with the mode of directly configuring the JSON format file in the past, the readability of the network slicing template in the planning process is improved, and the query and the change of the planned network slicing template by the user are facilitated.
Specifically, the abstract categories included in the template configuration table data at least include:
1. a shared deployment unit class (vdu) (Virtual deployment unit), wherein users define image types, resource requirements and the like of network elements of different classes, and the shared deployment unit class at least corresponds to 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-affanity (virtual machine affinity), if _ numa (whether or not to span numa), CPU _ affanity (CPU affinity), vm-flag-name (virtual machine specification name), vm-flag-disk (virtual machine specification disk size), vm-flag-vcpu (virtual machine specification CPU number), and vm-flag-mem (virtual machine specification memory size).
2. A network element subinstance class (vnfc) (VNF Component) for defining resource deployment requirements of network element template instances, such as aggregation groups, compute nodes, etc., the network element subinstance class corresponding to at least the following parameters:
parameters are vnfc-id (net element sub-instance id), vnfc-name (net element sub-instance name), vim _ id (text editor id), aggregate _ name, host _ name (host file name).
3. A Network element Function (vnf) (Virtual Network Function) for defining private information such as a Network and a version to which a virtualized Network belongs, where the Network element Function corresponds to at least 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 subinstance, and the like of a virtual machine, where the virtual machine parameter class corresponds to at least the following parameters:
vnfc-ID (ID of vnfc), vm _ hostname (host name of virtual machine), hostname (physical host name), global _ type, vnf _ ID (ID of vnf), glboarm _ IP (global operation maintenance IP address), rest _ IP (common 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 (machine frame), shelf, slot, VNFM _ rest (common network IP of VNFM), disk _ off (disk set switch), omc _ IP (operation maintenance center IP address), monitor _ agent, and NRF network element IP address.
5. A VNF-level network information set (connection-point-ref) for defining network addresses, network types, relationships between ports and network cards, and the like of network element subinstances, where the connection types at least correspond to the following parameters:
vnfc-id (index value of vnfc), value (ip of which connection point supports manual class), refcp (network name connected to), type-bandwidth (connection mode and bandwidth), SR _ IOV (whether a pass-through network card is set), port name, and priority.
6. A mirror parameter class (vnf-mirrors) for defining a type, an attribute, a virtual deployment unit to which a mirror image belongs in a virtualized network, and the like, where the mirror parameter class at least corresponds to the following parameters:
vnfd-ID (primary key index value of VNF), VNF-flag-ID (virtual machine specification ID of VNF), VNF-flag-name (virtual machine specification name of VNF), vdunanme (virtual deployment unit name), vnfcnumber (number of VNFCs).
7. The mirror image monitoring class (vnf-mirrors-installation-params) is used for defining trust parameters, left values, right values and the like of the mirror image, and at least corresponds to the following parameters:
VNF-flavour-ID (virtual machine specification ID of VNF), leftvalue (left threshold), rightvalue (right threshold), param-ID (primary key of parameter).
8. A private network class (private-network) for defining a private network of a network slice and a cloud platform, the private network class corresponding to at least the following parameters:
vnfd-ID (primary key index value of VNF), networkType, connect-point-name (network name of connection), provider-network (provider network name), SegmentationID (ID value of virtual local area network).
9. Public subnet classes (public-subnet) for defining public subnets, network segment addresses, masks and the like of the network slice and the cloud platform, wherein the public subnet classes at least correspond to the following parameters:
vnfd-id (primary key index value of VNF), subnet name (subnet name), startip (subnet mask), start (start ip), end (end ip).
10. A private subnet class (private-subnet) for defining a private subnet, a network segment address, a mask, etc. of the network slice and the cloud platform, where the private subnet class corresponds to at least the following parameters:
vnfd-id (primary key index value of VNF), subnet name (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, and the like of a virtualized network, where 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 (available or not), 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 the virtual link and the network element, the link class corresponding to at least the following parameters:
vnfd-id (primary key index value of VNF), frompoint (start point), toPoint (target point).
And 103, generating a network slice template in a JSON format according to the abstract type and the corresponding parameters.
In the embodiment of the invention, the template configuration table data is called by establishing a function model for converting the data in the EXCEL format into the JSON format, corresponding codes are generated according to abstract types in the template configuration table data, and the abstract types are loaded by using parameters corresponding to the abstract types so as to compile and generate the network slice template in the JSON format. The calling function in the function model can set the execution sequence and the sequence relation among 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 sequence of the slices, the virtual network function and the network service.
Optionally, referring to fig. 2, the step 103 includes:
step A1, creating a network element description file according to the network element function class and the corresponding parameters.
Step A2, creating a network element monitoring object list according to the network element monitoring class and the corresponding parameters.
Step A3, creating a mirror object list according to the mirror parameter class and the corresponding parameters.
Step A4, creating a mirror image monitoring object list according to the mirror image monitoring class and the corresponding parameters.
And A5, creating a public subnet object list according to the public subnet class and the corresponding parameters.
Step A6, creating a private network object list according to the private network class and the corresponding parameters.
Step a7, creating a private subnet object list according to the private subnet class and the corresponding parameters.
Step A8, creating a deployment unit object list according to the shared deployment unit class and the corresponding parameters.
Step A9, creating a network element subinstance object list according to the network element subinstance class and the corresponding parameters.
Step A10, creating a virtual machine object list according to the virtual machine parameter classes and the corresponding parameters.
Step A11, creating a connection relation list according to the connection classes and the corresponding parameters.
Step a12, a service relationship list is created according to the link class and the corresponding parameters.
Step A13, obtaining a 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.
In the embodiment of the present invention, the shared deployment unit class, the network element subinstance 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 subnetwork class, the private subnetwork class, the network element monitoring class, the link class and the corresponding parameters are converted into the JSON-formatted network element description file, the network element monitoring object list, the mirror image monitoring object list, the public subnetwork object list, the private network object list, the private subnetwork object list, the deployment unit object list, the network element subinstance object list, the virtual machine object list, the connection relation list and the service relation list through the pre-established function model, and the network slice templates are encapsulated into JSON format network slice templates according to the preset hierarchical sequence, so that the steps required for planning the network slice templates are simplified, and the efficiency of network slice template planning is improved.
Specifically, the function model may include the following calling 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 function of the call function is detailed 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 the network element sub-instance list.
Step B2, the packaged network element sub-instance object list is packaged into the 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 relationship 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 JSON-formatted network element description file, network element monitoring object list, mirror 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 are encapsulated according to the logical relationship described in fig. 4, so as to obtain a JSON-formatted network slice template. The function in table 1 is used to generate each data in fig. 4 to form a network slice template in the JOSN format, specifically, a createvnfs function is used to generate the VNF, a create _ monitoring _ params function is used to generate the VNF-monitoring-params, and the create _ VNF _ transporting function is used to generate the transporting: a small, the create _ vnf _ transporting _ association _ param function is used to generate the vnf-transporting-associating-params, the create _ Private _ networks function is used to generate the Private-networks, the create _ Public _ networks function is used to generate the Private-networks, the create _ Private _ networks function is used to generate the Private-networks, the create _ vdus function is used to generate the vdu, the create _ vnfcs function is used to generate the vnfc, the create _ vnfc _ data function is used to generate the matate, the create _ vls function is used to generate the vls, and the create _ connection-point function is used to generate the connection-ref.
Optionally, referring to fig. 5, on the basis of the method for generating a network slice template described in fig. 1, the step 102 includes:
and a substep 1021, filling all abstract types in the network slice configuration table template according to the service characteristics to obtain template configuration table data, wherein the abstract types and the service characteristics are corresponding to each other.
In the embodiment of the present invention, the network slice configuration form template is in a form of an EXCEL format, rows or columns of the network slice configuration form template may correspond to abstract categories, and after a user inputs a service feature, a filling area corresponding to each abstract category in the network slice configuration form template may be filled according to a correspondence between each service feature and each abstract category, and after the filling is completed, the template configuration form data may be obtained.
Optionally, referring to fig. 5, on the basis of the method for generating a network slice template illustrated in fig. 1, after step 103, the method further includes:
and 104, enabling the network function virtualization orchestrator to generate a network slice according to the network slice template.
In the 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 an NFVO (Network Function Virtualization editor) of a MANO (Management and architecture, 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 method for generating a network slice template, 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 table data according to the service characteristics, wherein the template configuration table data comprises abstract categories and corresponding parameters; and generating a network slice template in a JSON format according to the abstract category and the corresponding parameters. By editing the service characteristics of the network slice into template configuration table data containing sampling categories and corresponding parameters and converting the template configuration table data into the network slice template in the JSON format, the readability of the network slice template planning is improved, the step of the network slice template planning is simplified, and the efficiency of the network slice template planning is improved.
Example two
Referring to fig. 6, there is shown a network slice template generation apparatus according to the present application, including:
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.
The first generating 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:
the filling submodule 2021 is configured to fill, according to the service features, each abstract category in the network slice configuration table template to obtain template configuration table data, where the abstract category corresponds to the service features.
And the second generating module 203 is configured to generate a JSON-format network slice template according to the abstract category and the corresponding parameter.
Optionally, the abstract categories at least include: the method comprises the following steps of shared deployment unit class, network element subinstance class, network element function class, virtual machine parameter class, connection class, mirror image parameter class, mirror image monitoring class, private network class, public subnetwork class, private subnetwork class, network element monitoring class and 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 parameter.
And the second creating sub-module C2 is configured to create a network element monitoring object list according to the network element monitoring class and the corresponding parameter.
And a third creating sub-module C3, configured to create a mirror object list according to the mirror parameter class and the corresponding parameter.
And a fourth creating sub-module C4, configured to create a mirror monitoring object list according to the mirror monitoring class and the corresponding parameter.
And a fifth creating submodule C5, configured to create a public subnet object list according to the public subnet class and the corresponding parameter.
A sixth creating sub-module C6, configured to create a private network object list according to the private network class and the corresponding parameter.
A seventh creating sub-module C7, configured to create a private subnet object list according to the private subnet class and the corresponding parameter.
An eighth creating submodule C8, configured to create a deployment unit object list according to the shared deployment unit class and the corresponding parameters.
A ninth creating sub-module C9, configured to create a network element subinstance object list according to the network element subinstance class and the corresponding parameter.
A tenth creating submodule C10, configured to create a virtual machine object list according to the virtual machine parameter class and the corresponding parameter.
An eleventh creating sub-module C11, configured to create a connection relation list according to the connection class and the corresponding parameter.
And a twelfth creating sub-module C12, configured to create a service relationship list according to the link class and the corresponding parameter.
And the generation submodule C13 is configured to obtain a JSON-formatted network slice template according to the network element description file, the network element monitoring object list, the mirror 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 subinstance object list, the virtual machine object list, the connection relationship list, and the service relationship list.
Optionally, the generating sub-module C13 includes:
and a first encapsulating unit D1, configured to encapsulate the connection relationship list and the virtual machine object list into the network element sub-instance list.
And a second encapsulating unit D2, configured to encapsulate the encapsulated network element sub-instance object list into a virtual deployment unit object list.
And a third packaging unit D3, configured to package the image monitoring file and the packaged virtual deployment unit object list into an image description file.
A fourth encapsulating 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, so as to obtain a network slice template in the JOSN format.
A third generating module 204, configured to virtualize the orchestrator to the network function according to the network slice template, so that the network function virtualization orchestrator generates the network slice according to the network.
An embodiment of the present application provides a network slice generation apparatus, where the apparatus includes: the system comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving a network slice template generation request which comprises service characteristics; the first generation module is used for generating template configuration table data according to the service characteristics, wherein the template configuration table data comprises abstract categories and corresponding parameters; and the second generation module is used for generating the 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 template configuration table data containing sampling categories and corresponding parameters and converting the template configuration table data into the network slice template in the JSON format, the readability of the network slice template planning is improved, the step of the network slice template planning is simplified, and the efficiency of the network slice template planning is improved.
For the device embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.
The algorithms and displays presented herein are not inherently related to any particular computer, virtual machine, or other apparatus. Various general purpose systems may also be used with this teaching. The required structure for constructing such a system will be apparent from the description above. In addition, this application is not directed to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the present application as described herein, and any descriptions of specific languages are provided above to disclose the best modes 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 foregoing 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 application and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: this application is intended to cover such departures from the present disclosure as come within known or customary practice in the art to which this invention pertains. 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 device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. 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. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements 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 included in other embodiments, rather than other features, 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 may be used in any combination.
The various component embodiments of the present 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 a microprocessor or Digital Signal Processor (DSP) may be used in practice to implement some or all of the functions of some or all of the components in a network slice generation apparatus according to embodiments of the present application. The present application may also be embodied as apparatus or base station programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing the present application may be stored on a computer readable medium or may be in the form of one or more signals. Such a signal may be downloaded from an internet website or provided on a carrier signal or 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 claim enumerating several base stations, several of these base stations may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names.
Claims (10)
1. A method for generating a network slice template is characterized by comprising the following steps:
receiving a network slice template generation request, wherein the network slice template generation request comprises service characteristics;
generating template configuration table data according to the service characteristics, wherein the template configuration table data comprises abstract categories and corresponding parameters;
and generating a network slice template in a JSON format according to the abstract category and the corresponding parameters.
2. The method of claim 1, wherein the abstract categories include at least: the method comprises the following steps of shared deployment unit class, network element subinstance class, network element function class, virtual machine parameter class, connection class, mirror image parameter class, mirror image monitoring class, private network class, public subnetwork class, private subnetwork class, network element monitoring class and link class.
3. The method of claim 2, wherein the step of generating a JSON-formatted network slice template from the abstract class and corresponding parameters comprises:
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 subinstance object list according to the network element subinstance class and the corresponding parameters;
creating a virtual machine object list according to the virtual machine parameter classes and the corresponding parameters;
creating a connection relation list according to the connection classes and the corresponding parameters;
creating a service relation list according to the link classes and the corresponding parameters;
and 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.
4. The method according to claim 3, wherein the step of obtaining the network slice template in the JSON format according to the network element description file, the network element monitoring object list, the mirror 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 relationship list, and the service relationship list comprises:
packaging the connection relation list and the virtual machine object list into a network element sub-instance list;
packaging the packaged network element sub-instance object list into a virtual deployment unit object list;
packaging the mirror image monitoring file and the packaged virtual deployment unit object list into a mirror image description file;
and packaging 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 packaged mirror image description file into a network element description file to obtain a network slice template in a JOSN format.
5. The method according to claim 1, wherein the step of generating a JSON-formatted network slice template from the abstract class and corresponding parameters further comprises:
and a network function virtualization orchestrator is configured to generate a network slice according to the network slice template, so that the network function virtualization orchestrator generates the network slice according to the network.
6. The method of claim 1, wherein the step of generating template configuration form data according to the business features comprises:
and filling various abstract categories in the network slice configuration table template according to the service characteristics to obtain template configuration table data, wherein the abstract categories correspond to the service characteristics.
7. A network slice template generation apparatus, comprising:
the system comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving a network slice template generation request which comprises service characteristics;
the first generation module is used for generating template configuration table data according to the service characteristics, wherein the template configuration table data comprises abstract categories and corresponding parameters;
and the second generation module is used for generating the network slice template in the JSON format according to the abstract category and the corresponding parameters.
8. The apparatus of claim 7, wherein the abstract classes comprise at least: the method comprises the following steps of shared deployment unit class, network element subinstance class, network element function class, virtual machine parameter class, connection class, mirror image parameter class, mirror image monitoring class, private network class, public subnetwork class, private subnetwork class, network element monitoring class and link class.
9. The apparatus of claim 8, wherein the second generating module comprises:
the first creating submodule is used for creating a network element description file according to the network element function class and the corresponding parameters;
the second creating submodule is used for creating a network element monitoring object list according to the network element monitoring class and the corresponding parameters;
the third creating submodule is used for creating a mirror image object list according to the mirror image parameter class and the corresponding parameters;
the fourth creating submodule is used for creating a mirror image monitoring object list according to the mirror image monitoring class and the corresponding parameters;
a fifth creating submodule, configured to create a public subnet object list according to the public subnet class and the corresponding parameter;
a sixth creating submodule, configured to create a private network object list according to the private network class and the corresponding parameter;
a seventh creating sub-module, configured to create a private subnet object list according to the private subnet class and the corresponding parameter;
an eighth creating submodule, configured to create a deployment unit object list according to the shared deployment unit class and the corresponding parameter;
a ninth creating sub-module, configured to create a network element sub-instance object list according to the network element sub-instance class and the corresponding parameter;
a tenth creating submodule, configured to create a virtual machine object list according to the virtual machine parameter class and the corresponding parameter;
an eleventh creating submodule, configured to create a connection relation list according to the connection class and the corresponding parameter;
a twelfth creating submodule, configured to create a service relationship list according to the link class and the corresponding parameter;
and the generation submodule is used for obtaining a 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.
10. The apparatus of claim 9, 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 packaging unit is used for packaging the packaged 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 a mirror image description file;
and the fourth packaging unit is used for packaging 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 packaged 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 true CN112817688A (en) | 2021-05-18 |
| CN112817688B 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) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023050313A1 (en) * | 2021-09-30 | 2023-04-06 | 新华三技术有限公司 | Message processing method and apparatus, and network device and medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080126410A1 (en) * | 2006-09-21 | 2008-05-29 | Frank Brunswig | Business object templates |
| 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 |
-
2019
- 2019-11-15 CN CN201911121915.7A patent/CN112817688B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080126410A1 (en) * | 2006-09-21 | 2008-05-29 | Frank Brunswig | Business object templates |
| 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 |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023050313A1 (en) * | 2021-09-30 | 2023-04-06 | 新华三技术有限公司 | Message processing method and apparatus, and network device and medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112817688B (en) | 2023-10-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9703660B2 (en) | Testing a virtualized network function in a network | |
| US10628276B2 (en) | Unit test framework for testing code in a gateway service | |
| CN111079047B (en) | Web-oriented page construction system | |
| CN109725901A (en) | Development approach, device, equipment and the computer storage medium of front-end code | |
| CN108449418A (en) | A kind of mixed cloud platform management system and method | |
| CN110795148A (en) | Method and device for generating layout file and electronic equipment | |
| US10834022B2 (en) | Resource configuration using topology diagram | |
| US10887414B2 (en) | Theme-based push notifications | |
| US20190208404A1 (en) | Method and arrangement for on-boarding network service descriptions from various sources in a common service catalogue of NFV orchestration platform | |
| CN109683892B (en) | Page display method and device, computer equipment and storage medium | |
| EP2854348A1 (en) | Interface display method and system of home gateway applicable to multiple display types | |
| CN110347383A (en) | The front end development approach and device of cross-platform desktop application | |
| CN109814863A (en) | A kind of processing method, device, computer equipment and computer storage medium for requesting returned data | |
| CN106371846A (en) | Rapid development method and business system based on network data and message-oriented middleware | |
| US11025500B2 (en) | Provisioning infrastructure from visual diagrams | |
| 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 | |
| CN117112510A (en) | Report template configuration method, device, equipment and storage medium | |
| CN108363574A (en) | Front end method for customizing, device, terminal device and storage medium based on SDK | |
| CN110460456B (en) | Method and device for synchronously generating network topology by Management Information Base (MIB) | |
| US10168999B2 (en) | Software object definition and integration | |
| CN116048517A (en) | API (application program interface) generating method, system and device based on B/S (browser/Server) architecture application system | |
| CN115715389A (en) | Method and apparatus for edge-enabled server lifecycle management | |
| CN110891239B (en) | PNF configuration and PNFD TOSCA implementation method and device |
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 |