CN110086640B

CN110086640B - Service enabling method and device

Info

Publication number: CN110086640B
Application number: CN201810076567.5A
Authority: CN
Inventors: 苏偌宇; 武绍芸; 李卓明
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-01-26
Filing date: 2018-01-26
Publication date: 2022-01-14
Anticipated expiration: 2038-01-26
Also published as: CN110086640A

Abstract

The embodiment of the application provides a method and a device for enabling service, wherein the method comprises the following steps: the virtualized or cloud orchestration management function entity sends a plurality of resource files for deploying a plurality of network entities of a target network to a network slice manager, the plurality of resource files comprising a plurality of deployment configuration items; the network slice manager generates a target data structure corresponding to each deployment configuration item, wherein the target data structure comprises the name and the configuration value of the deployment configuration item; the sub-network slice manager generates a neutral model instance according to all the target data structures and the neutral models, wherein the neutral models are network topology templates; and the network element management system generates a configuration file of at least one target network entity corresponding to the core network according to the neutral model example, wherein the configuration file is used for normal operation of a business process on the target network entity. The service enabling method of the embodiment of the application has high generation efficiency of the configuration file, and a user can obtain clear network-level topology service configuration.

Description

Service enabling method and device

Technical Field

The present application relates to the field of communications engineering technologies, and in particular, to a method and an apparatus for service enabling.

Background

Network Function Virtualization (NFV) uses a Virtualization technology to divide the functions of Network nodes into several functional blocks, which are operated in a software manner, respectively, and are not limited to a hardware architecture. NFV technology enables service providers to quickly deploy network entity, dynamically updated network service functions.

Under the NFV technology, the network functions from design to real use of users need to go through several stages of service design, network entity deployment, and service enabling. The service design refers to designing and planning a required network entity aiming at functions to be provided by a network, network link information and service configuration information required by the network entity, and the like; after the service design, calculating resources, deployment positions and the like required by the network entity, and deploying the network entity to the virtual machine according to the service design; after the network entity is deployed, a configuration file needs to be obtained according to the network deployment information, and the configuration file is sent to the corresponding network entity, so that service enabling is realized. At present, after an Operation Support System (OSS) receives network entity deployment information, a user compiles a configuration file according to the network deployment information received by the OSS, and then issues the configuration file to a corresponding network entity through an Element Management System (EMS), so that a service process on the network entity operates normally, and service enabling is achieved.

The existing user writes configuration files, the labor consumption is large, the configuration efficiency is low, and meanwhile, the configuration files can only express the configuration of a single network entity, so that the user cannot directly obtain clear network extension and service configuration.

Disclosure of Invention

The embodiment of the application provides a method and a device for enabling a service, which are used for obtaining a configuration file of the service enabling with high efficiency, and a user can directly obtain clear network extension and service configuration.

In a first aspect, an embodiment of the present application provides a service enabling method, including:

a network slice manager receives a plurality of resource files for deploying a plurality of network entities of a target network, the plurality of resource files comprising a plurality of deployment configuration items;

the network slice manager analyzes the plurality of resource files and generates a target data structure corresponding to each deployment configuration item; the target data structure comprises the name of the deployment configuration item and the configuration value of the deployment configuration item;

the network slice manager sends each target data structure to each sub-network slice manager, so that after each sub-network slice manager sends a neutral model instance obtained according to each target data structure and the neutral model to a corresponding network element management system, the network element management system generates a configuration file of at least one network entity corresponding to the corresponding sub-network according to the neutral model instance, and the configuration file is used for normal operation of a business process on the network entity; the neutral model is a network topology template.

In the process, the configuration file for service enabling is automatically generated, and the generation efficiency is high; meanwhile, the neutral model is a network topology template, and a user can directly acquire clear network topology and service configuration, namely network-level topology service configuration, without inquiring a configuration database for storing configuration files according to the neutral model instance generated by the neutral model.

In one possible design, the network slice manager receives an update request sent by the sub-network slice manager; the updating request comprises the name of a target deployment configuration item corresponding to at least one configuration item to be updated and at least one updated configuration value of the target deployment configuration item; the configuration items to be updated are the configuration items to be updated in the corresponding configuration files; the name of the target deployment configuration item and the updated configuration value of the target deployment configuration item are obtained by the sub-network slice manager according to configuration update information, and the configuration update information comprises the name of at least one configuration item to be updated and the updated configuration value;

and the network slice manager updates the corresponding resource file according to the updating request.

In a possible design, if the configuration update information includes at least one group of configuration items, each group of configuration items includes a plurality of first configuration items to be updated, and the plurality of first configuration items to be updated of the same group correspond to the same first target deployment configuration item belonging to the service level agreement SLA parameter;

the network slice manager receives a first request message sent by the sub-network slice manager; the first request message comprises names and updated configuration values of first neutral model configuration items corresponding to a plurality of first configuration items to be updated included in each group of configuration items; the first request message is used for indicating a network slice manager to acquire the updated configuration value of the first target deployment configuration item corresponding to each group of configuration items; the name of a first neutral model configuration item corresponding to a first configuration item to be updated is acquired by the sub-network slice manager according to a first corresponding relation stored in a database; the first corresponding relation is the corresponding relation between the name of the configuration item in the configuration file and the name of the neutral model configuration item;

the network slice manager acquires the updated configuration value of the first target deployment configuration item corresponding to each group of configuration items according to the first request message and the second corresponding relation stored in the database; the second corresponding relation is a relation between the configuration values of the deployment configuration items belonging to the SLA parameters and the configuration values of the neutral model configuration items;

and the network slice manager sends the updated configuration values of the first target deployment configuration items corresponding to each group of configuration items to the sub-network slice manager.

In the possible design, the network slice manager can update the resource file in real time according to the change information of the configuration file by the user, and the updating efficiency is high.

In a second aspect, an embodiment of the present application provides a service enabling method, including:

a sub-network slice manager receives a plurality of target data structures sent by a network slice manager, wherein the target data structures are obtained by the network slice manager according to a plurality of deployment configuration items related to a plurality of network entities deploying a target network, the target data structures comprise names of the deployment configuration items and configuration values of the deployment configuration items, and each deployment configuration item corresponds to one target data structure;

the sub-network slice manager generates a neutral model instance according to all target data structures and neutral models, wherein the neutral model is a network topology template;

and the sub-network slice manager sends the neutral model instance to the corresponding network element management system, so that the network element management system generates a configuration file of at least one target network entity corresponding to the sub-network according to the neutral model instance, and sends the configuration file to the corresponding target network entity, wherein the configuration file is used for normal operation of a business process on the target network entity.

In one possible design, the sub-network slice manager generates a neutral model instance from all of the target data structures and neutral models, including:

if the first deployment configuration item corresponding to the target data structure is not the service level agreement SLA parameter, the sub-network slice manager acquires the name of a second neutral model configuration item corresponding to the name of the first deployment configuration item in the target data structure in the neutral model according to a third corresponding relation stored in the database; the third corresponding relation is a corresponding relation between the name of the deployment configuration item and the name of the neutral model configuration item;

adding the configuration value of the first deployment configuration item in the target data structure to a position corresponding to the name of the second neutral model configuration item to obtain the configuration value of the second neutral model configuration item;

if the second deployment configuration item corresponding to the target data structure is the SLA parameter, the sub-network slice manager acquires the respective names of a plurality of third neutral model configuration items corresponding to the name of the second deployment configuration item in the target data structure in the neutral model according to the third corresponding relation stored in the database;

the sub-network slice manager acquires the configuration values of the third neutral model configuration items;

for each third neutral model configuration item, the sub-network slice manager adding the configuration value of the third neutral model configuration item to a location corresponding to the name of the third neutral model configuration item;

and obtaining a neutral model example according to the neutral model added with the configuration value of the neutral model configuration item.

In a possible design, if the second deployment configuration item corresponding to the target data structure is an SLA parameter, the acquiring, by the sub-network slice manager, a configuration value of each third neutral model configuration item includes:

the sub-network slice manager sends a second request message to the network slice manager, wherein the second request message includes the name of each third neutral model configuration item and the configuration value in the corresponding target data structure, and the second request message is used for instructing the network slice manager to acquire the configuration value of each third neutral model configuration item according to a second corresponding relation stored in a database; the second corresponding relation is a relation between the configuration values of the deployment configuration items belonging to the SLA parameters and the configuration values of the neutral model configuration items;

and the sub-network slice manager receives the configuration value of each third neutral model configuration item sent by the network slice manager.

In one possible design, if a fourth neutral model configuration item is included in the neutral model, the neutral model configuration item corresponding to each of the deployment configuration items does not include the fourth neutral model configuration item, and the sub-network slice manager generates a neutral model instance according to all the target data structures and the neutral models, further including:

the sub-network slice manager acquires the configuration value of a fourth neutral model configuration item from a stored database;

the sub-network slice manager adds the configuration values of the fourth neutral model configuration item to a position in the neutral model corresponding to the name of the fourth neutral model configuration item.

In one possible design, after a configuration file is generated, a sub-network slice manager receives configuration update information sent by a network element management system, where the configuration update information includes a name of at least one configuration item to be updated and an updated configuration value, and the configuration item to be updated is a configuration item in a corresponding configuration file;

the sub-network slice manager acquires the name of a first neutral model configuration item corresponding to each configuration item to be updated according to a first corresponding relation stored in a database, wherein the first corresponding relation is the corresponding relation between the name of the configuration item in the configuration file and the name of the neutral model configuration item;

the sub-network slice manager updates the neutral model instance according to the names of all the first neutral model configuration items and the corresponding updated configuration values; the updated configuration value of the first neutral model configuration item is the updated configuration value of the corresponding configuration item to be updated;

if the configuration updating information comprises at least one second configuration item to be updated which does not belong to the SLA parameter, for each second configuration item to be updated, the sub-network slice manager acquires the name of a second target deployment configuration item corresponding to each second configuration item to be updated according to the third corresponding relation;

if the configuration updating information comprises at least one group of configuration items, each group of configuration items comprises a plurality of first configuration items to be updated, the plurality of first configuration items to be updated of the same group correspond to the same first target deployment configuration item which is an SLA parameter, and for each group of configuration items, the sub-network slice manager acquires the names of the first target deployment configuration items corresponding to the plurality of first configuration items to be updated included in the group of configuration items according to the third corresponding relation, and acquires the updated configuration values of the first target deployment configuration items;

the sub-network slice manager sends an update request to the network slice manager, the update request includes a name of a second target deployment configuration item corresponding to each second configuration item to be updated and an updated configuration value of each second configuration item to be updated, and/or a name of at least one first target deployment configuration item and an updated configuration value of at least one first target deployment configuration item, and the update request is used for instructing the network slice manager to update a corresponding resource file of a network entity for deploying a target network.

In the possible design, the sub-network slice manager can update the neutral model instance in real time according to the change information of the configuration file by the user, so that the updating efficiency is high, and the user can be ensured to obtain the latest network topology information and the latest service configuration information; the network slice manager can update the resource file in real time according to the change information of the configuration file by the user, and the updating efficiency is high.

In one possible design, the obtaining, by the subnet slice manager, the updated configuration value of the first target deployment configuration item includes:

the sub-network slice manager sending a first request message to the network slice manager; the first request message comprises the names of the first neutral model configuration items corresponding to the plurality of first configuration items to be updated included in the corresponding group of configuration items and the updated configuration values corresponding to the plurality of first configuration items to be updated; the first request message is used for instructing a network slice manager to acquire the updated configuration value of the first target deployment configuration item according to the second corresponding relation;

and the sub-network slice manager receives the updated configuration value of the first target deployment configuration item sent by the network slice manager.

Third aspect an embodiment of the present application provides a service enabling method, including:

a network element management system receives a neutral model example sent by a sub-network slice manager; the neutral model instance comprises the name of a neutral model configuration item and the configuration value of the neutral model configuration item, the neutral model instance is obtained by the sub-network slice manager according to a neutral model and a plurality of target data structures, the target data structures are obtained by the network slice manager according to a plurality of deployment configuration items of a plurality of network entities of a deployment target network, each deployment configuration item corresponds to one target data structure, and the target data structures comprise the name of the deployment configuration item and the configuration value of the deployment configuration item;

the network element management system generates a configuration file of at least one target network entity corresponding to a corresponding sub-network according to the neutral model instance;

and the network element management system sends the configuration file to a corresponding target network entity, and the configuration file is used for normal operation of a service process on the target network entity.

In one possible design, the generating, by the element management system according to the neutral model instance, a configuration file of at least one target network entity corresponding to a corresponding sub-network includes:

for each target network entity, the network element management system acquires each target neutral model configuration item related to the target network entity in the neutral model instance, and acquires a configuration command and a configuration parameter corresponding to each target neutral model configuration item;

the network element management system generates a configuration model instance corresponding to the corresponding target network entity according to the configuration command, the configuration parameter and the configuration value which are respectively corresponding to all target neutral model configuration items of the corresponding target network entity; the configuration value corresponding to the target neutral model configuration item is the configuration value of the target neutral model configuration item in the neutral model instance;

and the network element management system generates a configuration file of the corresponding target network entity according to the configuration model instance corresponding to the corresponding target network entity.

In one possible design, the acquiring, by the network element management system, the configuration command and the configuration parameter corresponding to each target-neutral model configuration item includes:

the network element management system sends a query request to the sub-network slice manager, wherein the query request comprises the name of each target neutral model configuration item; the query request is used for instructing the sub-network slice manager to acquire a configuration command and a configuration parameter corresponding to each target-neutral model configuration item;

and the network element management system receives a configuration command and a configuration parameter which correspond to each target-neutral model configuration item and are sent by the sub-network slice manager.

In one possible design, the method further includes:

the network element management system receives configuration updating information sent by a network entity, wherein the configuration updating information comprises the name of at least one configuration item to be updated and an updated configuration value;

the network element management system sends the configuration updating information to a sub-network slice manager so that the sub-network slice manager updates the neutral model instance according to the configuration updating information, and sends an updating request to the network slice manager after obtaining the name of the target deployment configuration item corresponding to at least one configuration item to be updated and the updated configuration value of the at least one target deployment configuration item according to the configuration updating information, wherein the updating request is used for indicating the network slice manager to update the resource file of the network entity for deploying the target network; the update request comprises the name of the target deployment configuration item corresponding to the at least one configuration item to be updated and the updated configuration value of the at least one target deployment configuration item.

In a fourth aspect, an embodiment of the present application provides a service-enabled device, including:

a receiving module, configured to receive a plurality of resource files for deploying a plurality of network entities of a target network, where the plurality of resource files include a plurality of deployment configuration items;

a target data structure generating module, configured to analyze the plurality of resource files and generate a target data structure corresponding to each deployment configuration item; the target data structure comprises the name of the deployment configuration item and the configuration value of the deployment configuration item;

a sending module, configured to send each target data structure to each sub-network slice manager, so that after each sub-network slice manager sends a neutral model instance obtained according to each target data structure and the neutral model to a corresponding network element management system, the network element management system generates a configuration file of each network entity corresponding to a corresponding sub-network according to the neutral model instance, where the configuration file is used for normal operation of a business process on the network entity; the neutral model is a network topology template.

In one possible design, the receiving module is further configured to receive an update request sent by the sub-network slice manager; the updating request comprises the name of a target deployment configuration item corresponding to at least one configuration item to be updated and at least one updated configuration value of the target deployment configuration item; the configuration items to be updated are the configuration items to be updated in the corresponding configuration files; the name of the target deployment configuration item and the updated configuration value of the target deployment configuration item are obtained by the sub-network slice manager according to configuration update information, and the configuration update information comprises the name of at least one configuration item to be updated and the updated configuration value;

the device also comprises an updating module which is used for updating the corresponding resource file according to the updating request.

In a possible design, the receiving module is further configured to receive a first request message sent by the sub-network slice manager if the configuration update information includes at least one group of configuration items, each group of configuration items includes a plurality of first configuration items to be updated, and the plurality of first configuration items to be updated of the same group correspond to the same first target deployment configuration item belonging to the service level agreement SLA parameter; the first request message comprises names and updated configuration values of first neutral model configuration items corresponding to a plurality of first configuration items to be updated included in each group of configuration items; the first request message is used for indicating the service enabling device to acquire the updated configuration value of the first target deployment configuration item corresponding to each group of configuration items; the name of a first neutral model configuration item corresponding to a first configuration item to be updated is acquired by the sub-network slice manager according to a first corresponding relation stored in a database; the first corresponding relation is the corresponding relation between the name of the configuration item in the configuration file and the name of the neutral model configuration item;

the device further comprises an obtaining module, wherein the obtaining module is used for obtaining the updated configuration value of the first target deployment configuration item corresponding to each group of configuration items according to the first request message and the second corresponding relation stored in the database; the second corresponding relation is a relation between the configuration values of the deployment configuration items belonging to the SLA parameters and the configuration values of the neutral model configuration items;

the sending module is further configured to send the updated configuration value of the first target deployment configuration item corresponding to each group of configuration items to the subnetwork slice manager.

In a fifth aspect, an embodiment of the present application provides a service-enabled device, including:

a receiving module, configured to receive multiple target data structures sent by a network slice manager, where the multiple target data structures are obtained by the network slice manager according to multiple deployment configuration items related to multiple network entities deploying a target network, each target data structure includes a name of a deployment configuration item and a configuration value of the deployment configuration item, and each deployment configuration item corresponds to one target data structure;

the neutral model instance generation module is used for generating neutral model instances according to all target data structures and neutral models, and the neutral models are network topology templates;

and the sending module is used for sending the neutral model instance to the corresponding network element management system so that the network element management system generates a configuration file of at least one target network entity corresponding to the sub-network according to the neutral model instance and sends the configuration file to the corresponding target network entity, wherein the configuration file is used for normal operation of a business process on the target network entity.

In one possible design, the neutral model instance generation module is specifically configured to,

if the first deployment configuration item corresponding to the target data structure is not the service level agreement SLA parameter, acquiring the name of a second neutral model configuration item corresponding to the name of the first deployment configuration item in the target data structure in the neutral model according to a third corresponding relation stored in the database; the third corresponding relation is a corresponding relation between the name of the deployment configuration item and the name of the neutral model configuration item;

if the second deployment configuration item corresponding to the target data structure is the SLA parameter, acquiring the respective names of a plurality of third neutral model configuration items corresponding to the name of the second deployment configuration item in the target data structure in the neutral model according to the third corresponding relation stored in the database;

acquiring the configuration value of each third neutral model configuration item;

for each third neutral model configuration item, adding the configuration value of the third neutral model configuration item to a position corresponding to the name of the third neutral model configuration item;

In a possible design, the neutral model instance generation module is specifically configured to send a second request message to the network slice manager if a second deployment configuration item corresponding to a target data structure is an SLA parameter, where the second request message includes a name of each third neutral model configuration item and a configuration value in a corresponding target data structure, and the second request message is used to instruct the network slice manager to obtain a configuration value of each third neutral model configuration item according to a second correspondence stored in a database; the second corresponding relation is a relation between the configuration values of the deployment configuration items belonging to the SLA parameters and the configuration values of the neutral model configuration items;

and receiving the configuration value of each third neutral model configuration item sent by the network slice manager.

In a possible design, the neutral model instance generation module is further specifically configured to, if the neutral model includes a fourth neutral model configuration item, and the neutral model configuration items corresponding to the deployment configuration items do not include the fourth neutral model configuration item, obtain a configuration value of the fourth neutral model configuration item from a stored database;

adding the configuration value of the fourth neutral model configuration item to a position in the neutral model corresponding to the name of the fourth neutral model configuration item.

In a possible design, the receiving module is further configured to receive configuration update information sent by the network element management system, where the configuration update information includes a name of at least one configuration item to be updated and an updated configuration value, and the configuration item to be updated is a configuration item in a corresponding configuration file;

the device further comprises an acquisition module, wherein the acquisition module is used for acquiring the name of a first neutral model configuration item corresponding to each configuration item to be updated according to a first corresponding relation stored in the database, and the first corresponding relation is the corresponding relation between the name of the configuration item in the configuration file and the name of the neutral model configuration item;

the device further comprises an updating module, wherein the updating module is used for updating the neutral model instance according to the names of all the first neutral model configuration items and the respective corresponding updated configuration values; the updated configuration value of the first neutral model configuration item is the updated configuration value of the corresponding configuration item to be updated;

the obtaining module is further configured to, if the configuration update information includes at least one second configuration item to be updated that does not belong to the SLA parameter, obtain, for each second configuration item to be updated, a name of a second target deployment configuration item corresponding to each second configuration item to be updated according to the third correspondence;

the obtaining module is further configured to, if the configuration update information includes at least one group of configuration items, each group of configuration items includes multiple first configuration items to be updated, multiple first configuration items to be updated of the same group correspond to the same first target deployment configuration item that is an SLA parameter, for each group of configuration items, according to the third correspondence, obtain names of first target deployment configuration items corresponding to the multiple first configuration items to be updated included in the group of configuration items, and obtain an updated configuration value of the first target deployment configuration item;

the sending module is further configured to send an update request to the network slice manager, where the update request includes a name of a second target deployment configuration item corresponding to each second configuration item to be updated and an updated configuration value of each second configuration item to be updated, and/or a name of at least one first target deployment configuration item and an updated configuration value of at least one first target deployment configuration item, and the update request is used to instruct the network slice manager to update a corresponding resource file of a network entity for deploying a target network.

In one possible design, the obtaining module is specifically configured to send a first request message to the network slice manager; the first request message comprises the names of the first neutral model configuration items corresponding to the plurality of first configuration items to be updated included in the corresponding group of configuration items and the updated configuration values corresponding to the plurality of first configuration items to be updated; the first request message is used for instructing a network slice manager to acquire the updated configuration value of the first target deployment configuration item according to the second corresponding relation;

and receiving the updated configuration value of the first target deployment configuration item sent by the network slice manager.

In a sixth aspect, an apparatus for enabling a service in an embodiment of the present application includes:

the receiving module is used for receiving the neutral model examples sent by the sub-network slice manager; the neutral model instance comprises the name of a neutral model configuration item and the configuration value of the neutral model configuration item, the neutral model instance is obtained by the sub-network slice manager according to a neutral model and a plurality of target data structures, the target data structures are obtained by the network slice manager according to a plurality of deployment configuration items of a plurality of network entities of a deployment target network, each deployment configuration item corresponds to one target data structure, and the target data structures comprise the name of the deployment configuration item and the configuration value of the deployment configuration item;

the configuration file generation module is used for generating a configuration file of at least one target network entity corresponding to a corresponding sub-network according to the neutral model instance;

and the sending module is used for sending the configuration file to a corresponding target network entity, and the configuration file is used for normal operation of a business process on the target network entity.

In one possible design, the configuration file generation module is specifically configured to,

for each target network entity, acquiring each target neutral model configuration item related to the target network entity in the neutral model instance, and acquiring a configuration command and a configuration parameter corresponding to each target neutral model configuration item;

generating a configuration model instance corresponding to the corresponding target network entity according to the configuration command, the configuration parameter and the configuration value which are respectively corresponding to all the target neutral model configuration items of the corresponding target network entity; the configuration value corresponding to the target neutral model configuration item is the configuration value of the target neutral model configuration item in the neutral model instance;

and generating a configuration file of the corresponding target network entity according to the configuration model instance corresponding to the corresponding target network entity.

sending a query request to the sub-network slice manager, the query request including a name for each target-neutral model configuration item; the query request is used for instructing the sub-network slice manager to acquire a configuration command and a configuration parameter corresponding to each target-neutral model configuration item;

and receiving a configuration command and a configuration parameter which are respectively corresponding to each target-neutral model configuration item and are sent by the sub-network slice manager.

In a possible design, the receiving module is further configured to receive configuration update information sent by a network entity, where the configuration update information includes a name of at least one configuration item to be updated and an updated configuration value;

the sending module is further configured to send the configuration update information to the sub-network slice manager, so that the sub-network slice manager updates the neutral model instance according to the configuration update information, and sends an update request to the network slice manager after obtaining a name of a target deployment configuration item corresponding to at least one configuration item to be updated and an updated configuration value of the at least one target deployment configuration item according to the configuration update information, where the update request is used to instruct the network slice manager to update a resource file of a network entity for deploying a target network; the update request comprises the name of the target deployment configuration item corresponding to the at least one configuration item to be updated and the updated configuration value of the at least one target deployment configuration item.

In a seventh aspect, this embodiment of the present application further provides a computer-readable storage medium, which includes instructions that, when executed on a computer, cause the computer to perform the method described in any possible design of the first aspect.

In an eighth aspect, embodiments of the present application further provide a computer-readable storage medium, which includes instructions that, when executed on a computer, cause the computer to perform the method of any one of the possible designs of the second aspect.

In a ninth aspect, embodiments of the present application further provide a computer-readable storage medium, which includes instructions that, when executed on a computer, cause the computer to perform the method of any one of the possible designs of the third aspect.

In a tenth aspect, an embodiment of the present application further provides a network slice manager, including a processor and a memory, where the memory is used to store program instructions, and the processor is used to read the program instructions in the memory and execute the method according to any one of the possible designs in the first aspect according to the program instructions in the memory.

In an eleventh aspect, an embodiment of the present application provides a subnet slice manager, which includes a processor and a memory, where the memory is used to store program instructions, and the processor is used to read the program instructions in the memory and execute the method according to any one of the possible designs in the second aspect according to the program instructions in the memory.

In a twelfth aspect, an embodiment of the present application is a network element management system, including a processor and a memory, where the memory is used to store program instructions, and the processor is used to read the program instructions in the memory and execute the method according to any one of the possible designs in the second aspect.

Drawings

Fig. 1 is an architecture diagram of an NFV provided in an embodiment of the present application;

FIG. 2 is a diagram of a first possible system architecture provided by an embodiment of the present application;

FIG. 3 is a diagram of a second possible system architecture provided by an embodiment of the present application;

FIG. 4 is a diagram of a third possible system architecture provided by an embodiment of the present application;

fig. 5 is a first signaling flow diagram of a service enabling method according to an embodiment of the present application;

fig. 6 is a first signaling flow diagram of a method for network update according to an embodiment of the present application;

fig. 7 is a signaling flowchart of a service enabling method according to an embodiment of the present application;

fig. 8 is a signaling flowchart of a method for updating a network according to an embodiment of the present application;

fig. 9 is a signaling flow diagram of a service enabling method according to an embodiment of the present application;

fig. 10 is a signaling flow chart of a method for updating a network according to an embodiment of the present application;

fig. 11 is a first schematic structural diagram of a service-enabled device according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of a service-enabled device according to an embodiment of the present application;

fig. 13 is a third schematic structural diagram of a service-enabled device according to an embodiment of the present application;

fig. 14 is a schematic structural diagram of a service-enabled device according to an embodiment of the present application;

fig. 15 is a schematic structural diagram of a service-enabled device according to an embodiment of the present application;

fig. 16 is a schematic structural diagram of a network slice manager provided in an embodiment of the present application;

FIG. 17 is a block diagram of a subnet slice manager according to an embodiment of the present application;

fig. 18 is a schematic structural diagram of a network element management system according to an embodiment of the present application.

Detailed Description

First, terms related to the embodiments of the present application will be described.

Operation Support System (OSS): the system is a comprehensive service operation and management platform and is also a comprehensive management platform which really fuses the traditional IP data service and the mobile value-added service. The OSS is an integrated information resource sharing support system of telecommunication operators, mainly comprises parts such as network management, system management, charging, business, accounting and customer service, and the systems are organically integrated together through a unified information bus. The method can help an operator to formulate an operation support system which meets the characteristics of the operator and determine the development direction of the system, and can help a user to formulate the integration standard of the system, thereby improving and improving the service level of the user.

Network Function Virtualization (NFV for short): the functions originally running on the traditional communication network equipment are realized in a software mode by adopting a virtualization method.

Fig. 1 is an architecture diagram of an NFV provided in an embodiment of the present application; referring to fig. 1, NFV includes 3 partial entity functions: network Function Virtualization resource Infrastructure (NFVI) 11, Virtual Network Function (VNF) 12, and Management and Orchestration Function (MANO) 13.

The NFVI is a cloud data center including servers, storage hardware, a virtualization management program, an operating system, virtual machines, virtual switches, and network resources. NFVI requires virtualization of physical compute/storage/switch resources into virtual compute/storage/switch resource pools.

The VNF implements the functions of the conventional telecommunication network elements, and the resources required by the VNF need to be decomposed into virtual computing/storage/switching resources, which are carried by the NFVI.

The MANO is responsible for managing and editing the NFVI and the VNF and is a virtualized or cloud arrangement management functional entity. The MANO internally includes 3 entities of Virtual Infrastructure Management (VIM), virtual Network Function controller (VNFM) and Orchestrator, which respectively manage NFVI, VNF and NS.

Orchester: the orchestrator is the control center of the entire MANO domain, responsible for the unified management and orchestration of NFV-infrastructure resources and software resources. Typically a set 1 orchestrator is deployed throughout the network.

The VNFM is responsible for managing the lifecycle of the VNF, including instantiation/upgrade/capacity expansion/capacity reduction/termination, etc. After the VNF is instantiated, the network Entity includes a Mobility Management Entity (MME), a Packet Control Function (PCF), a Home Subscriber Server (HSS), and the like. Each network or network slice includes a plurality of network entities.

VIM: the management function comprises a resource management function, a resource pooling function, and resource management and allocation. The operation and maintenance functions comprise management and visualization of NFVI, root cause analysis of performance and faults from the NFVI level, collection and reporting of fault information, capacity planning and performance statistics.

In summary, the MANO of the NFV may receive commands from the OSS to deploy and connect network entities to the network over the virtualized resource infrastructure NFVI and manage the lifecycle of the network entities, here NVF instances.

An Element Management System (EMS) is a System that manages one or more telecommunication Network Elements (NEs) of a particular type. Generally, the EMS manages the functions and capabilities of each NE, but does not manage the communication between different NEs in the network. In order to support communication between NEs, EMS needs to communicate with a higher-level Network Management System (Network Management System), and NMS is also an element in a hierarchical model of Telecommunications Management Network (TMN). EMS is the basis of OSS framework based on TMN hierarchical model, and this framework makes the Service provider able to meet the requirement of the client on the Service developing at high speed and also able to meet the strict Quality of Service (QOS) requirement.

Network slicing: in order to meet the requirements of different applications of the internet of things, different networks are established to meet the requirements of different applications of the internet of things, and the different networks can be called network slices.

A network slice manager: the method is responsible for loading and managing the network slice template, creating a network slice instance according to the network slice template and managing the life cycle of the network slice instance. Each network slice corresponds to a network slice manager, and each network slice may include a plurality of subnetworks.

The sub-network slice manager: the subnet slice manager is responsible for loading and managing the subnet slice template, creating a subnet slice instance according to the subnet template and managing the life cycle of the subnet slice instance. Each network slice involved in the embodiments of the present application may include a sub-network including: the system comprises an access network, a transmission network and a core network, wherein each sub-network corresponds to a sub-network slice manager.

Next, a service enabling method according to an embodiment of the present application will be described.

Under the NFV technology, the network functions from design to real use of users need to go through several stages of service design, network entity deployment, and service enabling.

The service design refers to designing and planning a required network entity according to functions provided by a network, and network link information and service configuration information required by the network entity; wherein, the service configuration information includes: link information (the information required by the link itself comprises an IP address or an IP address field, a port number and the like), global basic information (for example: time zone information), license application templates, rules required by the user (for example: when the user accesses the network, 5G is preferred, 4G is selected next time) and the like. License refers to a function which can be realized by a network entity, a License application template has a plurality of functions, a user can select at least one function in the License application template, and the selected function is the function which can be realized by the network entity.

The network entity deployment means that the network entity is deployed to a server or a virtual machine according to service design according to resources, deployment positions and the like required by the network entity.

After the network entity is deployed, a service enabling stage is entered, that is, a configuration file of a corresponding network entity is obtained according to the resource file of each network entity in the deployment network, and the configuration file is sent to the network entity, so that the service running on the network entity can run normally.

FIG. 2 is a diagram of a first possible system architecture provided by an embodiment of the present application; referring to fig. 2, the system architecture includes a network slice manager 21, a sub-network slice manager 22 corresponding to a core network, a network element management system 23 corresponding to the core network, and a virtualized or clouded orchestration management function 24. The virtualized or clouded orchestration management function 24 may be a MANO function as described above.

Specifically, in conjunction with the above description of the NFV architecture, the virtualized or clouded orchestration management function entity 24 is configured to deploy multiple network entities of the network, and therefore, the network slice manager 21 receives multiple resource files sent by the virtualized or clouded orchestration management function entity 24 for deploying the multiple network entities of the target network; the plurality of resource files include the service design information and the network topology information, or a plurality of deployment configuration items in the plurality of resource files, and the virtualization or clouding orchestration management functional entity 24 deploys each network entity of the target network to the virtual machine according to the plurality of deployment configuration items, thereby completing the establishment of the target network.

After receiving the resource file, the network slice manager 21 analyzes the resource file, generates a target data structure corresponding to each deployment configuration item, and sends each target data structure to the sub-network slice manager 22 corresponding to the core network; the sub-network slice manager 22 corresponding to the core network stores a neutral model, the neutral model is a network topology template of the target network, the sub-network slice manager 22 generates a neutral model instance corresponding to the target network according to each target data structure and the neutral model, and sends the neutral model instance to the network element management system 23 corresponding to the core network, the network element management system 23 corresponding to the core network generates a configuration file of at least one target network entity corresponding to the core network in the target network according to the neutral model instance, the network element management system 23 corresponding to the core network sends the configuration file to the corresponding target network entity, and the configuration file is used for normal operation of a service process on the target network entity, so that service enabling is realized. The neutral model is a network topology template which is independent of manufacturers.

According to the embodiment of the application, the configuration file is automatically generated without manual writing, and the generation efficiency of the configuration file is high; and because the neutral model is a network topology template which is independent of manufacturers, users and operators can obtain clear network-level topology by looking at the neutral model instance.

FIG. 3 is a diagram of a second possible system architecture provided by an embodiment of the present application; referring to fig. 3, the system architecture includes an operation and maintenance support system 31, a network element management system 32 corresponding to a core network, and a virtualized or clouded orchestration management function entity 33. The virtualized or clouded orchestration management function 33 may be a MANO function as described above.

Specifically, the operation and maintenance support system 31 receives resource files of a plurality of network entities for deploying a target network, which are sent by the virtualization or clouding orchestration management functional entity 33; after receiving the resource file, the operation and maintenance support system 31 analyzes the resource file to generate a target data structure corresponding to each deployment configuration item; the operation and maintenance support system 31 stores a neutral model, the neutral model is a network topology template of the target network, then the operation and maintenance support system 31 generates a neutral model instance corresponding to the target network according to each target data structure and the neutral model, and sends the neutral model instance to the network element management system 32 corresponding to the core network, the network element management system 32 corresponding to the core network generates a configuration file of at least one target network entity corresponding to the core network in the target network according to the neutral model instance, the network element management system 32 corresponding to the core network sends the configuration file to the corresponding target network entity, and the configuration file is used for normal operation of a service process on the target network entity, so that service enabling is achieved. The neutral model is a network topology template which is independent of manufacturers.

FIG. 4 is a diagram of a third possible system architecture provided by an embodiment of the present application; referring to fig. 4, the system architecture includes a first network element 41, a second network element 42 corresponding to a core network, and a virtualization or cloud orchestration management function entity 43. The virtualized or clouded orchestration management function 43 may be a MANO function as described above.

The first network element 41 receives resource files of a plurality of network entities for deploying a target network, which are sent by the virtualization or cloud orchestration management functional entity 43; after receiving the resource file, the first network element 41 analyzes the resource file, generates a target data structure corresponding to each deployment configuration item, and sends each target data structure to the second network element 42 corresponding to the core network; the second network element 42 corresponding to the core network stores a neutral model, the neutral model is a network topology template of the target network, the second network element 42 corresponding to the core network generates a neutral model instance corresponding to the target network according to each target data structure and the neutral model, then generates a configuration file of at least one target network entity corresponding to the core network in the target network according to the neutral model instance, the second network element 42 corresponding to the core network sends the configuration file to the corresponding target network entity, and the configuration file is used for normal operation of a business process on the target network entity, so that business enabling is achieved. The neutral model is a network topology template which is independent of manufacturers.

The service enabling method of the present application is described in detail below with specific embodiments.

First, a service-enabled method using a first possible system architecture will be described in detail.

Fig. 5 is a signaling flow diagram of a service enabling method according to an embodiment of the present application, referring to fig. 5, where the method according to the embodiment may include:

step S101, a virtualized or clouded orchestration management functional entity sends a plurality of resource files of a plurality of network entities for deploying a target network to a network slice manager, wherein the plurality of resource files comprise a plurality of deployment configuration items;

step S102, a network slice manager analyzes a plurality of resource files and generates a target data structure corresponding to each deployment configuration item, wherein the target data structure comprises the name of the deployment configuration item and the configuration value of the deployment configuration item;

step S103, the network slice manager sends each target data structure to a sub-network slice manager corresponding to the core network;

s104, a sub-network slice manager corresponding to the core network generates a neutral model instance according to all target data structures and the neutral models, wherein the neutral models are network topology templates;

s105, the sub-network slice manager corresponding to the core network sends the neutral model instance to a network element management system corresponding to the core network;

step S106, generating a configuration file of at least one target network entity corresponding to the core network by a network element management system corresponding to the core network according to the neutral model example;

and S107, the network element management system corresponding to the core network sends the corresponding configuration file to the corresponding target network entity, and the configuration file is used for normal operation of the service process on the target network entity.

Specifically, the network entity involved in this embodiment is a VNF instance under the NFV technology, and at this time, the deployment of the network entity is completed by a virtualization or cloud orchestration management function entity.

For step S101, the virtualized or clouded orchestration management function entity sends a plurality of resource files for deploying a plurality of network entities of the target network to the network slice manager; and the virtualization or cloud arrangement management functional entity deploys each network entity of the target network to the virtual machine according to the plurality of resource files to complete the construction of the target network. The resource files are resource deployment template files such as NFV, Network Service Descriptor (NSD) and the like used by the Network slice instance and the sub-Network slice instance. The plurality of resource files embody network level topology and service configuration information.

Wherein, the plurality of resource files include a plurality of deployment configuration items, for example, a link in a service design corresponding to the target network is an S1 link, and then the deployment configuration items included in the plurality of resource files may be: an identifier of an evolved network base station (E-UTRAN NodeB, abbreviated eNodeB), an IP of the eNodeB, a port number corresponding to the eNodeB, an identifier of the MME, an IP of the MME, a port number corresponding to the MME, a Service IP address, a Service Level Agreement (SLA) parameter, and the like.

The service SLA parameter refers to a requirement of a communication service for a network slice, and includes a service capacity requirement parameter in a region, a charging requirement parameter, a region coverage requirement parameter, an isolation degree requirement parameter, an end-to-end delay requirement parameter, a mobility requirement parameter, a total User density requirement parameter, a priority requirement parameter, a service availability requirement parameter, a service reliability requirement parameter, a User Equipment (UE for short) mobility speed requirement parameter, and the like.

The SLA parameters are style parameters, and the deployment configuration items abstracted from the service reliability requirement parameters in the resource file comprise connection reliability deployment configuration items and connection sensitivity deployment configuration items. In fact, the connection reliability includes: the method comprises the following steps that a route index, a routing mode, a destination entity domain name, an opposite end entity index, a route name, priority and weight are abstracted into a deployment configuration item of connection reliability in a resource file; the connection sensitivity includes: the method includes a minimum value of Retransmission Timeout (RTO), a maximum value of RTO, an initial value of RTO, a heartbeat interval, a maximum number of coupled retransmissions, and a maximum number of path retransmissions, which are all abstracted as a deployment configuration item of connection sensitivity in a resource file.

For step S102, the network slice manager receives the plurality of resource files sent by the virtualized or clouded orchestration management function entity, parses the plurality of resource files, and generates a target data structure corresponding to each deployment configuration item, where the target data structure includes a name of the deployment configuration item and a configuration value of the deployment configuration item, and each deployment configuration item corresponds to one target data structure.

That is to say, the deployment configuration items in the resource file include names and configuration values of the deployment configuration items, and the network slice manager extracts the names and the configuration values of the deployment configuration items of the resource file to generate a target data structure corresponding to the deployment configuration items. For example, the deployment configuration item "eNodeB corresponding port number" may include, in its corresponding target data structure: "port number (name, although the actual name may be in other forms) corresponding to eNodeB, 2000 (configuration value)"; the deployment configuration item "connection sensitivity," whose corresponding target data structure may include: "connection sensitivity (name), high (configuration value)".

In addition, in a non-NFV scenario, the Network entity is a Physical Network Function (PNF) instance, and the deployment of the Network entity is completed by a user and is not completed by a virtualization or clouding deployment management Function entity, so that at this time, the plurality of resource files received by the Network slice manager are no longer sent by the virtualization or clouding deployment management Function entity.

For steps S103 to S104: the network slice manager sends each target data structure to a sub-network slice manager corresponding to the core network; and the sub-network slice manager corresponding to the core network generates a neutral model instance according to all the target data structures and the neutral model, wherein the neutral model is a network topology template.

Specifically, the neutral model is a network topology template, which is not relevant to the vendor implementation method, for expressing the complete network topology.

The neutral model can comprise neutral model configuration items: home terminal identification, opposite terminal identification, home terminal IP, opposite terminal IP, home terminal port, opposite terminal port, RTO maximum value, RTO minimum value, RTO initial value, heartbeat interval, coupling maximum retransmission times, path maximum retransmission times and the like. Here, since the sub-network slice manager in this embodiment is a sub-network slice manager corresponding to the core network, in a scenario where the link in the service design corresponding to the target network is the S1 link, the home terminal refers to the MME terminal.

Then, the sub-network slice manager corresponding to the core network generates a neutral model instance according to all the target data structures and the neutral models, including:

if the first deployment configuration item corresponding to the target data structure is not the SLA parameter, the sub-network slice manager corresponding to the core network acquires the name of a second neutral model configuration item corresponding to the name of the first deployment configuration item in the target data structure in the neutral model according to a third corresponding relation stored in the database; the third corresponding relation is the corresponding relation between the name of the deployment configuration item and the name of the neutral model configuration item; and adding the configuration value of the first deployment configuration item in the target data structure to the position corresponding to the name of the second neutral model configuration item by the sub-network slice manager corresponding to the core network to obtain the configuration value of the third neutral model configuration item.

Such as: the deployment configuration item "the identifier corresponding to the eNodeB" is a non-style parameter in the neutral model, and then the identifier corresponding to the deployment configuration item "eNodeB" may be referred to as a first deployment configuration item, and according to the third correspondence, the name of the second neutral model configuration item corresponding to the name of the first deployment configuration item in the neutral model is obtained as an "opposite-end identifier", and at this time, the configuration value "XX" in the target data structure corresponding to the identifier corresponding to the first deployment configuration item "eNodeB" is added to the position corresponding to the name "opposite-end identifier" of the second neutral model configuration item. Similarly, the deployment configuration item "the identifier corresponding to the MME" is also a non-style class parameter in the neutral model, so the deployment configuration item "the identifier corresponding to the MME" may be referred to as a first deployment configuration item, and according to the third correspondence, the name of the second neutral model configuration item corresponding to the name of the first deployment configuration item in the neutral model is obtained as a "home identifier", and at this time, the configuration value "YY" in the target data structure of the first deployment configuration item "the identifier corresponding to the MME" is added to the position corresponding to the name of the second neutral model configuration item "home identifier".

The deployment configuration items "IP of eNodeB", "port number corresponding to eNodeB", "IP of MME", "port number corresponding to MME", "service IP address" and the like are non-style parameters in the neutral model, and the processing method is the same as above.

If the configuration value corresponding to the deployment configuration item "eNodeB IP" in the target data structure is an IP segment, selecting one of the IP segments as the configuration value of the second neutral model configuration item "peer IP" according to the resource usage in the resource pool. The same applies for "IP of MME" in this case.

If the second deployment configuration item corresponding to the target data structure is an SLA parameter, the sub-network slice manager corresponding to the core network acquires respective names of a plurality of third neutral model configuration items corresponding to the name of the second deployment configuration item in the target data structure in the neutral model according to a third corresponding relation stored in the database; a sub-network slice manager corresponding to the core network acquires respective configuration values of the third neutral model configuration items; for each third neutral model configuration item, the sub-network slice manager corresponding to the core network adds the configuration value of the third neutral model configuration item to the location corresponding to the name of the third neutral model configuration item.

If the second deployment configuration item corresponding to the target data structure is an SLA parameter, the sub-network slice manager corresponding to the core network obtains a configuration value of each third neutral model configuration item, including:

a sub-network slice manager corresponding to the core network sends a second request message to the network slice manager, wherein the second request message comprises the name of each third neutral model configuration item and the configuration value in the corresponding target data structure, and the second request message is used for indicating the network slice manager to acquire the configuration value of each third neutral model configuration item according to a second corresponding relation stored in the database; the second corresponding relation is the relation between the configuration values of the deployment configuration items belonging to the SLA parameters and the configuration values of the neutral model configuration items; and the sub-network slice manager corresponding to the core network receives the configuration values of the third neutral model configuration items sent by the network slice manager.

For example, if the deployment configuration item "connection sensitivity" is an SLA parameter, the deployment configuration item "connection sensitivity" may be referred to as a second deployment configuration item, and the configuration value in the target data structure corresponding to the second deployment configuration item is "high", the sub-network slice manager corresponding to the core network obtains, according to the third correspondence, names of a plurality of third neutral model configuration items corresponding to the names of the second deployment configuration items in the neutral models: RTO maximum value, RTO minimum value, RTO initial value, heartbeat interval, coupling maximum retransmission times and path maximum retransmission times. A sub-network slice manager corresponding to the core network sends a second request message to the network slice manager, wherein the second request message comprises 'maximum value of RTO, minimum value of RTO, initial value of RTO, heartbeat interval, maximum coupling retransmission times, maximum path retransmission times, high'; the network slice manager acquires the configuration value of the maximum RTO value, the configuration value of the minimum RTO value, the configuration value of the initial RTO value, the configuration value of the heartbeat interval, the configuration value of the maximum coupling retransmission times and the configuration value of the maximum path retransmission times when the connection sensitivity is high according to the second request message, and transmits the configuration value of the maximum RTO value, the configuration value of the minimum RTO value, the configuration value of the initial RTO value, the configuration value of the heartbeat interval, the configuration value of the maximum coupling retransmission times and the configuration value of the maximum path retransmission times to the sub-network slice manager corresponding to the core network, and after the sub-network slice manager corresponding to the core network receives the configuration values, the configuration values of the third neutral model configuration items are added to the positions of the neutral model configuration items corresponding to the third neutral model configuration items at the positions corresponding to the names of the third neutral model configuration items, adding the configuration value of the RTO maximum value to a position corresponding to the name of the RTO maximum value of the third neutral model configuration item, adding the configuration value of the RTO minimum value to a position corresponding to the name of the RTO minimum value of the third neutral model configuration item, and adding the configuration value of the RTO initial value to a position corresponding to the name of the RTO initial value of the third neutral model configuration item; adding the configuration value of the heartbeat interval to a position corresponding to the name of the heartbeat interval of the third neutral model configuration item; the "arrangement value of the maximum number of coupled retransmissions" is added to the position corresponding to the name of the third neutral model arrangement item "the maximum number of coupled retransmissions" and the "arrangement value of the maximum number of path retransmissions" is added to the position corresponding to the name of the third neutral model arrangement item "the maximum number of path retransmissions".

Further, if the neutral model includes a fourth neutral model configuration item, and the neutral model configuration item corresponding to each of the plurality of deployment configuration items does not include the fourth neutral model configuration item, the sub-network slice manager generates a neutral model instance according to all the target data structures and the neutral models, further including:

for a fourth neutral model configuration item of the neutral model, the sub-network slice manager acquires a configuration value of the fourth neutral model configuration item from a stored database; the sub-network slice manager adds the configuration values of the fourth neutral model configuration item to a position in the neutral model corresponding to the name of the fourth neutral model configuration item.

Specifically, the neutral model configuration item corresponding to each of the plurality of deployment configuration items does not include the fourth neutral model configuration item, and it can also be understood that the deployment configuration item corresponding to the fourth neutral model configuration item is not included in the resource file; and the sub-network slice manager corresponding to the core network acquires the configuration value of the fourth neutral model configuration item from the database and adds the configuration value of the fourth neutral model configuration item to a position corresponding to the name of the fourth neutral model configuration item in the neutral model.

The neutral model added with the configuration value of the neutral model configuration item is used as a neutral model instance.

The neutral model will be further described below.

As mentioned above, the neutral model is a network topology template, which is not related to the vendor implementation method and is used to express the complete network topology, and when the configuration value of the neutral model configuration item in the neutral model is added, that is, after the neutral model instance is formed, the complete network topology and service configuration information can be expressed, which is a model open to the user. The sources of configuration values for the neutral model configuration items are as follows:

A. the arrangement values of the second, third, and fourth neutral model arrangements are obtained as described above.

B. External interface: a sub-network slice manager corresponding to a core network opens an RESTFUL interface to the outside of the system, and configuration values of a neutral model configuration item which needs to be input after opposite terminal planning and global coordination are added into the neutral model in the mode;

in summary, the neutral model has a hierarchical structure, including: the system comprises a global basic information layer, a license configuration layer, a signaling connection layer and a rule configuration layer. The global basic information layer comprises global basic information, such as time zone information; the license configuration layer comprises configured license information (not selected by the template license application template) or license application template information. The signaling connection layer contains the local IP address, port number, and the configuration information of the transmission layer. The routing information includes the type of route (dynamic or static), whether bidirectional forwarding detection is available, and the load sharing mode (round-robin, master-slave, priority weight)). The rule configuration layer includes rules issued to a rule Control Function (PCF), for example: the user prefers 5G, and selects 4G again.

For the sub-network slice manager corresponding to the core network in the steps S105 to S107, sending the obtained neutral model instance to a network element management system corresponding to the core network; and after receiving the neutral model instance, the network element management system corresponding to the core network generates a configuration file of at least one target network entity corresponding to the core network according to the neutral model instance.

Specifically, since the sub-network slice manager is a sub-network slice manager corresponding to the core network and the network element management system is a network element management system corresponding to the core network, the configuration file generated by the network element management system is at least one target network entity on the core network side included in the target network.

The network element management system corresponding to the core network generates a configuration file of at least one target network entity corresponding to the core network according to the neutral model instance, and the configuration file comprises the following steps:

for each target network entity, the network element management system corresponding to the core network acquires each target neutral model configuration item related to the target network entity in the neutral model instance, and acquires a configuration command and a configuration parameter corresponding to each target neutral model configuration item; a network element management system corresponding to a core network generates a configuration model instance corresponding to a corresponding network entity according to configuration commands, configuration parameters and configuration values which are respectively corresponding to all target neutral model configuration items of the corresponding target network entity; the corresponding configuration value of the target neutral model configuration item is the configuration value of the target neutral model configuration item in the neutral model instance; and the network element management system corresponding to the core network generates a configuration file of the target network entity according to the configuration model example.

Specifically, for example, two S1 links are designed in the target network, and each S1 link corresponds to one MME, at this time, there are two target network entities; if two S1 links designed in the target network correspond to one MME, or there is only one MME, there is only one target network entity.

And for each target network entity, the network element management system corresponding to the core network acquires the configuration file corresponding to the target network entity according to the neutral model example. The following describes an acquisition process of a configuration file by taking an acquisition process of acquiring a configuration file of a target network entity as an example.

The network element management system corresponding to the core network acquires each target neutral model configuration item related to a target network entity in the neutral model instance, and then the network element management system corresponding to the core network sends a query request to a sub-network slice manager of the core network, wherein the query request comprises the name of each target neutral model configuration item; the query request is used for instructing a sub-network slice manager of the core network to acquire a configuration command and a configuration parameter corresponding to each target neutral model configuration item; a network element management system corresponding to a core network receives a configuration command and a configuration parameter corresponding to a target neutral model configuration item sent by a sub-network slice manager corresponding to the core network; a network element management system corresponding to a core network generates a configuration model instance corresponding to a corresponding network entity according to configuration commands, configuration parameters and configuration values which are respectively corresponding to all target neutral model configuration items of the target network entity; the corresponding configuration value of the target neutral model configuration item is the configuration value of the target neutral model configuration item in the neutral model instance; and the network element management system corresponding to the core network generates a configuration file of the target network entity according to the configuration model example.

The configuration command and the configuration parameter acquisition process are described below as an example.

Such as: when the name of the Service IP configuration item in the neutral model is 'Service _ IP' in the neutral model and the configuration command and the configuration parameters of the Service IP configuration item are acquired, the query request sent to the sub-network slice manager of the core network comprises 'Service _ IP', and after the sub-network slice manager of the core network receives the query request, the sub-network slice manager acquires the configuration command corresponding to the 'Service _ IP': "S1 APLE" and configuration parameters: "localIP", will "configure command: s1APLE and configuration parameters: and sending the localIP to a network element management system corresponding to the core network.

And after the configuration file corresponding to each target network entity is generated, the network element management system corresponding to the core network sends the configuration file to the corresponding target network entity, and the configuration file is used for normal operation of a service process on the target network entity.

In the embodiment of the application, the resource file of the network entity of the deployment target network is used as input, and the configuration file of the network entity at the core network side is finally obtained through the processing of the network slice manager, the sub-network slice manager corresponding to the core network and the network element management system corresponding to the core network, so that the service enablement of the network entity at the core network side is realized, that is, the generation process of the configuration file is an automatic generation process, and the generation efficiency is high. In addition, before the configuration file is generated, the neutral model instance is generated firstly, and the neutral model instance embodies the network topology information and the service configuration information, so that a user can know clear network topology information and service configuration information by looking up the neutral model instance.

The service enabling method of the embodiment includes: the virtualized or cloud orchestration management function entity sends a plurality of resource files for deploying a plurality of network entities of a target network to a network slice manager, the plurality of resource files comprising a plurality of deployment configuration items; the network slice manager analyzes the plurality of resource files and generates a target data structure corresponding to each deployment configuration item, the target data structure comprises the name of the deployment configuration item and the configuration value of the deployment configuration item, and each deployment configuration item corresponds to one target data structure; the network slice manager sends each target data structure to a sub-network slice manager corresponding to the core network; a sub-network slice manager corresponding to the core network generates a neutral model instance according to all target data structures and neutral models, wherein the neutral model is a network topology template; the sub-network slice manager corresponding to the core network sends the neutral model instance to a network element management system corresponding to the core network; a network element management system corresponding to the core network generates a configuration file of at least one target network entity corresponding to the core network according to the neutral model example; and the network element management system corresponding to the core network sends the configuration file to a corresponding target network entity, and the configuration file is used for normal operation of a service process on the target network entity. The service enabling method of the embodiment has high generation efficiency of the configuration file, and the user can obtain clear network topology information and service configuration information.

In practical applications, sometimes it is necessary to re-plan a network, for example, delete a link or change an IP of a network entity in the network, and the following describes a method for updating a network corresponding to the embodiment shown in fig. 5 in this application with reference to a specific embodiment.

Fig. 6 is a first signaling flowchart of a method for network update according to an embodiment of the present invention, and referring to fig. 6, the method according to the embodiment may include:

step S201, a network entity receives configuration updating information input by a user; the configuration updating information comprises the name of at least one configuration item to be updated and an updated configuration value; the configuration item to be updated is a configuration item in the configuration file, and the name of the configuration item to be updated is the configuration item of the configuration item to be updated in the configuration file;

step S202, the network entity sends the configuration updating information to a network element management system;

step S203, the network element management system sends the configuration updating information to the sub-network slice manager;

step S204, the sub-network slice manager acquires the name of a first neutral model configuration item corresponding to each configuration item to be updated according to a first corresponding relation stored in a database, wherein the first corresponding relation is the corresponding relation between the name of the configuration item in the configuration file and the name of the neutral model configuration item;

step S205, the subnet slice manager updates the neutral model instance according to the names of all the first neutral model configuration items and the configuration values which are respectively and correspondingly updated; the configuration value of the first neutral model configuration item after being updated is the configuration value of the corresponding configuration item to be updated after being updated;

step S206, if the configuration updating information includes a second configuration item to be updated which does not belong to the SLA parameter, for each second configuration item to be updated, the sub-network slice manager acquires the name of a second target deployment configuration item corresponding to each second configuration item to be updated according to the third corresponding relation; the third corresponding relation is the corresponding relation between the name of the deployment configuration item and the name of the neutral model configuration item;

step S207, if the configuration update information includes at least one group of configuration items, each group of configuration items includes a plurality of first configuration items to be updated, the plurality of first configuration items to be updated of the same group correspond to the same first target deployment configuration item belonging to the SLA parameter, for each group of configuration items, the sub-network slice manager obtains, according to the third corresponding relationship, names of first target deployment configuration items corresponding to the plurality of first configuration items to be updated included in the group of configuration items, and obtains configuration values after the first target deployment configuration items are updated;

step S208, the sub-network slice manager sends an update request to the network slice manager, and the sub-network slice manager sends an update request to the network slice manager, where the update request includes a name of a target deployment configuration item corresponding to each second configuration item to be updated and an updated configuration value of each second configuration item to be updated, and/or a name of at least one first target deployment configuration item and an updated configuration value of at least one first target deployment configuration item.

Step S209, the network slice manager updates the corresponding resource file according to the update request.

Specifically, this embodiment corresponds to the previous embodiment, and therefore, the network entity in this embodiment may be a network entity corresponding to a core network included in the target network, and accordingly, the network element management system is a network element management system corresponding to the core network and a sub-network slice manager corresponding to the sub-network slice manager core network.

The meanings of the deployment configuration item, the neutral model configuration item, the neutral model instance, the resource file, and the configuration file in this embodiment are the same as those in the previous embodiment, and are not described again in this embodiment.

The updating in this embodiment includes: modify, add, delete.

For step S201 to step S203, the network entity receives configuration updating information input by a user; the configuration updating information comprises the name of the configuration item to be updated and the updated configuration value;

for example, if the user wants to change the IP address of the MME 1 corresponding to the S1 link with the link number 1, the user may input an instruction to change the IP address of the MME 1 through a user interface corresponding to the network entity, where the method for inputting the instruction to change the IP address of the MME 1 may be as follows: and the user clicks a configuration icon modification button on the user interface to display a configuration file modification interface, each configuration item included in the configuration file is displayed in the configuration file modification interface, and the user deletes the original IP address of the MME 1 in the configuration file and inputs a new IP address. The network entity receives the instruction for changing the IP address of the MME 1, and updates the configuration database for storing the configuration file, namely, the IP address of the MME 1 in the corresponding configuration file stored in the configuration database is updated to the new IP address input by the user.

If a certain S1 link is to be deleted, the user can input the number of the S1 link, the configuration items to be updated in the configuration update information at this time may be multiple items, that is, all configuration items corresponding to the S1 link, and the updated configuration values of the configuration items may be null.

If a certain S1 link is to be added, the user may input the configuration values of all the configuration items corresponding to the S1 link on the configuration file modification interface, where the configuration items to be updated in the configuration update information are multiple items, that is, all the configuration items corresponding to the S1 link, and the updated configuration values of the configuration items may be values input by the user.

The network entity sends a configuration update message to the network element management system, wherein the configuration update message comprises: the name of the configuration item to be updated and the updated configuration value, that is, the name of the IP address of the MME 1 in the configuration file and the new IP address.

And the network element management system receives the configuration updating message and sends the configuration updating message to the sub-network slice manager.

For step S204 to step S205, the sub-network slice manager obtains the name of the first neutral model configuration item corresponding to each configuration item to be updated according to the first corresponding relationship stored in the database, where the first corresponding relationship is the corresponding relationship between the name of the configuration item in the configuration file and the name of the neutral model configuration item; the sub-network slice manager updates the neutral model instance according to the names of all the first neutral model configuration items and the corresponding updated configuration values; and the configuration value of the first neutral model configuration item after being updated is the configuration value of the corresponding configuration item to be updated after being updated.

For example, for the configuration item to be updated "IP address of MME 1", the sub-network slice manager obtains the name of the first neutral model configuration item corresponding to the configuration item to be updated "IP address of MME 1" according to the first corresponding relationship stored in the database, and replaces the original IP address at the name position of the corresponding first neutral model configuration item with the updated configuration value of the configuration item to be updated "IP address of MME 1" -new IP address ".

Therefore, users except the user for changing the configuration file can obtain new network topology information and service configuration information by checking the updated neutral model instance without inquiring a configuration database. However, in the current method for manually writing configuration files, if a certain user changes a certain configuration item of a certain configuration file, other users must obtain the updated configuration file by querying the configuration database where the corresponding configuration file is located, and only the configuration information of a single network entity can be obtained, and the network-level topology service configuration of the network cannot be obtained. Especially, under the condition of deleting a link or adding a link, namely under the condition of replanning the network, the updated neutral model instance has more prominent effect, can display the latest network topology information and service configuration information to a user, and the user can acquire the network topology information and the service configuration information after replanning.

For step S206: if the configuration updating information comprises second configuration items to be updated which do not belong to the SLA parameters, for each second configuration item to be updated, the sub-network slice manager acquires the name of a second target deployment configuration item corresponding to each second configuration item to be updated according to the third corresponding relation; the third correspondence is a correspondence between the name of the deployment configuration item and the name of the neutral model configuration item.

Specifically, for second configuration items to be updated which do not belong to SLA parameters, each of the second configuration items to be updated corresponds to one neutral model configuration item (referred to as a first neutral model configuration item herein) and one deployment configuration item (referred to as a second target deployment configuration item herein).

For step S207, if the configuration update information includes at least one group of configuration items, each group of configuration items includes multiple first configuration items to be updated, the multiple first configuration items to be updated of the same group correspond to the same first target deployment configuration item belonging to the SLA parameter, and for each group of configuration items, the subnet slice manager acquires, according to the third corresponding relationship, names of the first target deployment configuration items corresponding to the multiple first configuration items to be updated included in the group of configuration items, and acquires configuration values after the first target deployment configuration items are updated.

Specifically, the acquiring, by the subnet slice manager, the updated configuration value of each first target deployment configuration item includes: the sub-network slice manager sends a first request message to the network slice manager, wherein the first request message comprises names and updated configuration values of first neutral model configuration items corresponding to a plurality of first configuration items to be updated included in each group of configuration items; after receiving the first request message, the network slice manager acquires updated configuration values of first target deployment configuration items corresponding to a plurality of first to-be-updated configuration items included in each group of configuration items according to the first request message and a second corresponding relation stored in the database, and sends the updated configuration values of each first target deployment configuration item to the sub-network slice manager. And the second corresponding relation is the relation between the configuration value of the neutral model configuration item corresponding to the SLA parameter and the configuration value of the deployment configuration item.

For example, the user updates the configuration value of the maximum RTO value, the configuration value of the minimum RTO value, the configuration value of the initial RTO value, the configuration value of the heartbeat interval, the configuration value of the maximum coupling retransmission times, and the configuration value of the maximum path retransmission times, where the maximum RTO value, the minimum RTO value, the initial RTO value, the heartbeat interval, the maximum coupling retransmission times, and the maximum path retransmission times belong to the same group of configuration items, each of which may be referred to as a second configuration item to be updated, and the name of the first target deployment configuration item corresponding to the second configuration item is connection sensitivity. The sub-network slice manager sends the names of the first neutral models corresponding to the RTO maximum value, the RTO minimum value, the RTO initial value, the heartbeat interval, the coupling maximum retransmission times and the path maximum retransmission times and the updated configuration value of the RTO minimum value, the updated configuration value of the RTO maximum value, the updated configuration value of the RTO initial value, the updated configuration value of the heartbeat interval, the updated configuration value of the coupling maximum retransmission times and the updated configuration value of the path maximum retransmission times to the network slice manager, and the network slice manager obtains the updated configuration value of the RTO minimum value, the configuration value of the RTO initial value, the configuration value of the heartbeat interval, the configuration value of the coupling maximum retransmission times, the configuration value of the path maximum retransmission times and the corresponding relationship between the configuration values of the connection sensitivity according to the stored configuration value of the RTO maximum value, the configuration value of the RTO minimum value, the updated configuration value of the path maximum retransmission times and the stored configuration value of the connection sensitivity, The configuration value after the update of the maximum RTO value, the configuration value after the update of the initial RTO value, the configuration value after the update of the heartbeat interval, the configuration value after the update of the maximum retransmission number of the coupling, and the configuration value of the connection sensitivity corresponding to the configuration value after the update of the maximum retransmission number of the path are, for example, "medium", that is, the configuration value after the update of the "connection sensitivity" of the first target deployment configuration item is "medium"; and the network slice manager sends the acquired updated configuration value of the first target deployment configuration item, namely 'connection sensitivity', to the sub-network slice manager.

For step S208 to step S209, the sub-network slice manager sends an update request to the network slice manager, and the sub-network slice manager sends an update request to the network slice manager, where the update request includes a name of a target deployment configuration item corresponding to each second configuration item to be updated and an updated configuration value of each second configuration item to be updated, and/or a name of at least one first target deployment configuration item and an updated configuration value of at least one first target deployment configuration item. And the network slice manager updates the corresponding resource file according to the updating request.

In this embodiment, when the user updates the configuration file, the neutral model instance and the resource file can be updated at the same time, so that other users can also acquire the service configuration information of the updated network topology without querying a corresponding configuration database.

Second, a service-enabled method employing a second possible system architecture is described.

Fig. 7 is a signaling flowchart of a service enabling method according to an embodiment of the present application, and referring to fig. 7, the method according to the embodiment may include:

step S301, a virtualized or clouded orchestration management functional entity sends a plurality of resource files of a plurality of network entities for deploying a target network to an operation and maintenance support system, wherein the plurality of resource files comprise a plurality of deployment configuration items;

step S302, the operation and maintenance support system analyzes a plurality of resource files and generates a target data structure corresponding to each deployment configuration item, wherein the target data structure comprises the name of the deployment configuration item and the configuration value of the deployment configuration item;

s303, generating a neutral model instance by the operation and maintenance support system according to all target data structures and neutral models, wherein the neutral model is a network topology template;

s304, the operation and maintenance support system sends the neutral model instance to a network element management system corresponding to the core network;

step S305, a network element management system corresponding to the core network generates a configuration file of at least one target network entity corresponding to the core network according to the neutral model example;

step S306, the network element management system corresponding to the core network sends the corresponding configuration file to the corresponding target network entity, and the configuration file is used for normal operation of the business process on the target network entity.

Specifically, the specific implementation method of the service enablement in this embodiment is the same as the specific implementation method of the service enablement in the embodiment shown in fig. 5, but the execution subject is different, and the specific implementation thereof is not described again in this embodiment.

In practical applications, sometimes it is necessary to re-plan a network, for example, delete a link or change an IP of a network entity in the network, and the following describes a method for updating a network corresponding to the embodiment shown in fig. 7 of the present application with reference to a specific embodiment.

Fig. 8 is a signaling flowchart of a method for network update according to an embodiment of the present invention, and referring to fig. 8, the method according to the embodiment may include:

step S401, a network entity receives configuration updating information input by a user; the configuration updating information comprises the name of at least one configuration item to be updated and an updated configuration value; the configuration item to be updated is a configuration item in the configuration file, and the name of the configuration item to be updated is the configuration item of the configuration item to be updated in the configuration file;

step S402, the network entity sends the configuration updating information to the network element management system;

step S403, the network element management system sends the configuration updating information to the operation and maintenance support system;

step S404, the operation and maintenance support system obtains the name of a first neutral model configuration item corresponding to each configuration item to be updated according to a first corresponding relation stored in the database, wherein the first corresponding relation is the corresponding relation between the name of the configuration item in the configuration file and the name of the neutral model configuration item;

s405, the operation and maintenance support system updates the neutral model instance according to the names of all the first neutral model configuration items and the configuration values which are respectively corresponding to the updated neutral model configuration items; the configuration value of the first neutral model configuration item after being updated is the configuration value of the corresponding configuration item to be updated after being updated;

step S406, if the configuration updating information includes a second configuration item to be updated which does not belong to the SLA parameter, the operation and maintenance support system obtains the name of a second target deployment configuration item corresponding to each second configuration item to be updated according to the third corresponding relation for each second configuration item to be updated; the third corresponding relation is the corresponding relation between the name of the deployment configuration item and the name of the neutral model configuration item;

step S407, if the configuration update information includes at least one group of configuration items, each group of configuration items includes a plurality of first configuration items to be updated, the plurality of first configuration items to be updated of the same group correspond to the same first target deployment configuration item belonging to the SLA parameter, for each group of configuration items, the operation and maintenance support system obtains names of the first target deployment configuration items corresponding to the plurality of first configuration items to be updated included in the group of configuration items according to the third corresponding relationship, and obtains configuration values after the first target deployment configuration items are updated;

step S408, the operation and maintenance support system updates the corresponding resource file according to the name of the target deployment configuration item corresponding to each second configuration item to be updated and the updated configuration value of each second configuration item to be updated, and/or the name of at least one first target deployment configuration item and the updated configuration value of at least one first target deployment configuration item.

Specifically, the specific implementation method of the service enablement in this embodiment is the same as the specific implementation method of the service enablement in the embodiment shown in fig. 6, but the execution subject is different, and the specific implementation thereof is not described again in this embodiment.

Next, a service-enabled method using a third possible system architecture will be described.

Fig. 9 is a signaling flowchart of a service enabling method according to an embodiment of the present application, and referring to fig. 9, the method according to the embodiment may include:

step S501, a virtualized or clouded orchestration management functional entity sends a plurality of resource files of a plurality of network entities for deploying a target network to a first network element, wherein the plurality of resource files comprise a plurality of deployment configuration items;

step S502, the first network element analyzes a plurality of resource files and generates a target data structure corresponding to each deployment configuration item, wherein the target data structure comprises the name of the deployment configuration item and the configuration value of the deployment configuration item;

step S503, the first network element sends each target data structure to the second network element;

step S504, the second network element generates a neutral model instance according to all the target data structures and the neutral models, wherein the neutral models are network topology templates;

step S505, the second network element generates a configuration file of at least one target network entity corresponding to the core network according to the neutral model instance;

step S506, the second network element sends the corresponding configuration file to the corresponding target network entity, and the configuration file is used for normal operation of the service process on the target network entity.

In practical applications, sometimes it is necessary to re-plan a network, for example, delete a link or change an IP of a network entity in the network, and the following describes a method for updating a network corresponding to the embodiment shown in fig. 9 of the present application with reference to a specific embodiment.

Fig. 10 is a signaling flowchart of a method for network update according to an embodiment of the present invention, referring to fig. 10, the method according to this embodiment may include:

step S601, a network entity receives configuration updating information input by a user; the configuration updating information comprises the name of at least one configuration item to be updated and an updated configuration value; the configuration item to be updated is a configuration item in the configuration file, and the name of the configuration item to be updated is the configuration item of the configuration item to be updated in the configuration file;

step S602, the network entity sends the configuration updating information to the second network element;

step S603, the second network element obtains the name of a first neutral model configuration item corresponding to each configuration item to be updated according to a first corresponding relation stored in the database, wherein the first corresponding relation is the corresponding relation between the name of the configuration item in the configuration file and the name of the neutral model configuration item;

step S604, the second network element updates the neutral model instance according to the names of all the first neutral model configuration items and the configuration values which are respectively corresponding to the updated neutral model configuration items; the configuration value of the first neutral model configuration item after being updated is the configuration value of the corresponding configuration item to be updated after being updated;

step S605, if the configuration updating information includes a second configuration item to be updated which does not belong to the SLA parameter, for each second configuration item to be updated, the second network element obtains the name of a second target deployment configuration item corresponding to each second configuration item to be updated according to the third corresponding relation; the third corresponding relation is the corresponding relation between the name of the deployment configuration item and the name of the neutral model configuration item;

step S606, if the configuration updating information includes at least one group of configuration items, each group of configuration items includes a plurality of first configuration items to be updated, the plurality of first configuration items to be updated of the same group correspond to the same first target deployment configuration item belonging to the SLA parameter, for each group of configuration items, the sub-network slice manager acquires names of the first target deployment configuration items corresponding to the plurality of first configuration items to be updated included in the group of configuration items according to the third corresponding relationship, and acquires configuration values after the first target deployment configuration items are updated;

step S607, the second network element sends an update request to the first network element, where the update request includes the name of the target deployment configuration item corresponding to each second configuration item to be updated and the updated configuration value of each second configuration item to be updated, and/or the name of at least one first target deployment configuration item and the updated configuration value of at least one first target deployment configuration item.

Step S608, the first network element updates the corresponding resource file according to the update request.

Fig. 11 is a first schematic structural diagram of a service-enabled device according to an embodiment of the present application; the service-enabled device may be provided in a network slice manager, see fig. 11, the service-enabled device comprising: a receiving module 51, a target data structure generating module 52 and a sending module 53.

The receiving module 51 is configured to receive a plurality of resource files for deploying a plurality of network entities of a target network, where the resource files include a plurality of deployment configuration items;

the target data structure generating module 52 is configured to analyze the plurality of resource files and generate a target data structure corresponding to each deployment configuration item; the target data structure comprises the name of the deployment configuration item and the configuration value of the deployment configuration item;

the sending module 53 is configured to send each target data structure to each sub-network slice manager, so that after each sub-network slice manager sends a neutral model instance obtained according to each target data structure and the neutral model to a corresponding network element management system, the network element management system generates a configuration file of each network entity corresponding to a corresponding sub-network according to the neutral model instance, where the configuration file is used for normal operation of a business process on the network entity; the neutral model is a network topology template.

The service-enabled device provided in the present application may implement the technical solution shown in the foregoing method embodiment, and the implementation principle and the beneficial effect thereof are similar, which are not described herein again.

Fig. 12 is a schematic structural diagram of a service-enabled device according to an embodiment of the present application; on the basis of the embodiment described in fig. 11, referring to fig. 12, the service enabling apparatus includes: an update module 54 and an acquisition module 55.

The receiving module is further configured to receive an update request sent by the sub-network slice manager; the updating request comprises the name of a target deployment configuration item corresponding to at least one configuration item to be updated and at least one updated configuration value of the target deployment configuration item; the configuration items to be updated are the configuration items to be updated in the corresponding configuration files; the name of the target deployment configuration item and the updated configuration value of the target deployment configuration item are obtained by the sub-network slice manager according to configuration update information, and the configuration update information comprises the name of at least one configuration item to be updated and the updated configuration value;

and the updating module is used for updating the corresponding resource file according to the updating request.

The receiving module 51 is further configured to receive a first request message sent by the subnet slice manager if the configuration update information includes at least one group of configuration items, each group of configuration items includes a plurality of first configuration items to be updated, and the plurality of first configuration items to be updated of the same group correspond to the same first target deployment configuration item belonging to the service level agreement SLA parameter; the first request message comprises names and updated configuration values of first neutral model configuration items corresponding to a plurality of first configuration items to be updated included in each group of configuration items; the first request message is used for indicating the service-enabled device to acquire the updated configuration value of the first target deployment configuration item corresponding to each group of configuration items; the name of a first neutral model configuration item corresponding to a first configuration item to be updated is acquired by the sub-network slice manager according to a first corresponding relation stored in a database; the first corresponding relation is the corresponding relation between the name of the configuration item in the configuration file and the name of the neutral model configuration item;

the obtaining module 55 is configured to obtain, according to the first request message and the second correspondence stored in the database, the updated configuration value of the first target deployment configuration item corresponding to each group of configuration items; the second corresponding relation is a relation between the configuration values of the deployment configuration items belonging to the SLA parameters and the configuration values of the neutral model configuration items;

the sending module 53 is further configured to send the updated configuration value of the first target deployment configuration item corresponding to each group of configuration items to the subnetwork slice manager.

Fig. 13 is a third schematic structural diagram of a service-enabled device according to an embodiment of the present application; the service enabled device may be provided in a sub-network slice manager, see fig. 13, the service enabled device comprising: a receiving module 61, a neutral model instance generating module 62 and a sending module 63.

A receiving module 61, configured to receive a plurality of target data structures sent by a network slice manager, where the plurality of target data structures are obtained by the network slice manager according to a plurality of deployment configuration items related to a plurality of network entities deploying a target network, and each target data structure includes a name of a deployment configuration item and a configuration value of the deployment configuration item, and each deployment configuration item corresponds to one target data structure;

a neutral model instance generation module 62, configured to generate a neutral model instance according to all target data structures and neutral models, where the neutral model is a network topology template;

a sending module 63, configured to send the neutral model instance to a corresponding network element management system, so that the network element management system generates, according to the neutral model instance, a configuration file of at least one target network entity corresponding to the subnetwork, and sends the configuration file to the corresponding target network entity, where the configuration file is used for normal operation of a business process on the target network entity.

In one possible implementation, the neutral model instance generation module 62 is specifically configured to,

if a second deployment configuration item corresponding to a target data structure is an SLA parameter, sending a second request message to the network slice manager, where the second request message includes a name of each third neutral model configuration item and a configuration value in a corresponding target data structure, and the second request message is used to instruct the network slice manager to obtain a configuration value of each third neutral model configuration item according to a second correspondence stored in a database; the second corresponding relation is a relation between the configuration values of the deployment configuration items belonging to the SLA parameters and the configuration values of the neutral model configuration items;

Fig. 14 is a schematic structural diagram of a service-enabled device according to an embodiment of the present application; on the basis of the embodiment described in fig. 13, referring to fig. 14, the service enabling apparatus includes: an update module 64 and an acquisition module 65.

The receiving module 61 is further configured to receive configuration update information sent by the network element management system, where the configuration update information includes a name of at least one configuration item to be updated and an updated configuration value, and the configuration item to be updated is a configuration item in a corresponding configuration file;

the obtaining module 65 is configured to obtain a name of a first neutral model configuration item corresponding to each configuration item to be updated according to a first corresponding relationship stored in the database, where the first corresponding relationship is a corresponding relationship between the name of the configuration item in the configuration file and the name of the neutral model configuration item;

the updating module 64 is configured to update the neutral model instance according to the names of all the first neutral model configuration items and the updated configuration values corresponding to the first neutral model configuration items; the updated configuration value of the first neutral model configuration item is the updated configuration value of the corresponding configuration item to be updated;

the obtaining module 65 is further configured to, if the configuration update information includes at least one second configuration item to be updated that does not belong to the SLA parameter, for each second configuration item to be updated, obtain, according to the third corresponding relationship, a name of a second target deployment configuration item corresponding to each second configuration item to be updated;

the obtaining module 65 is further configured to, if the configuration update information includes at least one group of configuration items, each group of configuration items includes multiple first configuration items to be updated, where the multiple first configuration items to be updated of the same group correspond to the same first target deployment configuration item that is an SLA parameter, and for each group of configuration items, according to the third corresponding relationship, obtain names of the first target deployment configuration items corresponding to the multiple first configuration items to be updated included in the group of configuration items, and obtain an updated configuration value of the first target deployment configuration item;

the sending module 63 is further configured to send an update request to the network slice manager, where the update request includes a name of a second target deployment configuration item corresponding to each second configuration item to be updated and an updated configuration value of each second configuration item to be updated, and/or a name of at least one first target deployment configuration item and an updated configuration value of at least one first target deployment configuration item, and the update request is used to instruct the network slice manager to update a corresponding resource file of a network entity for deploying a target network.

In a possible implementation manner, the obtaining module 65 is specifically configured to send a first request message to the network slice manager; the first request message comprises the names of the first neutral model configuration items corresponding to the plurality of first configuration items to be updated included in the corresponding group of configuration items and the updated configuration values corresponding to the plurality of first configuration items to be updated; the first request message is used for instructing a network slice manager to acquire the updated configuration value of the first target deployment configuration item according to the second corresponding relation; and receiving the updated configuration value of the first target deployment configuration item sent by the network slice manager.

Fig. 15 is a schematic structural diagram of a service-enabled device according to an embodiment of the present application; the service enabling apparatus may be disposed in a network element management system, and referring to fig. 15, the service enabling apparatus includes: a receiving module 71, a configuration file generating module 72 and a sending module 73.

A receiving module 71, configured to receive the neutral model instance sent by the sub-network slice manager; the neutral model instance comprises the name of a neutral model configuration item and the configuration value of the neutral model configuration item, the neutral model instance is obtained by the sub-network slice manager according to a neutral model and a plurality of target data structures, the target data structures are obtained by the network slice manager according to a plurality of deployment configuration items of a plurality of network entities of a deployment target network, each deployment configuration item corresponds to one target data structure, and the target data structures comprise the name of the deployment configuration item and the configuration value of the deployment configuration item;

a configuration file generating module 72, configured to generate a configuration file of at least one target network entity corresponding to a corresponding sub-network according to the neutral model instance;

and a sending module 73, configured to send the configuration file to a corresponding target network entity, where the configuration file is used for normal operation of a service process on the target network entity.

In one possible implementation, the configuration file generation module 72 is specifically configured to,

In a possible implementation manner, the receiving module 71 is further configured to receive configuration update information sent by a network entity, where the configuration update information includes a name of at least one configuration item to be updated and an updated configuration value;

the sending module 73 is further configured to send the configuration update information to the sub-network slice manager, so that the sub-network slice manager updates the neutral model instance according to the configuration update information, and sends an update request to the network slice manager after obtaining, according to the configuration update information, a name of a target deployment configuration item corresponding to at least one configuration item to be updated and a configuration value after the at least one target deployment configuration item is updated, where the update request is used to instruct the network slice manager to update a resource file of a network entity for deploying a target network; the update request comprises the name of the target deployment configuration item corresponding to the at least one configuration item to be updated and the updated configuration value of the at least one target deployment configuration item.

Fig. 16 is a schematic structural diagram of a network slice manager according to an embodiment of the present application. Referring to fig. 16, the network slice manager may include a receiver 81, a processor 82, a memory 83, a transmitter 84, and a communication bus 85, where the memory 83 is used to store program instructions, the communication bus 85 is used to implement connections between components, the processor 82 is used to read the program instructions in the memory 83 and execute operations corresponding to the program instructions, where,

the receiver 81 is configured to receive a plurality of resource files of a plurality of network entities for deploying a target network, where the plurality of resource files include a plurality of deployment configuration items;

the processor 82 is configured to parse the plurality of resource files, and generate a target data structure corresponding to each deployment configuration item; the target data structure comprises the name of the deployment configuration item and the configuration value of the deployment configuration item;

the sender 84 is configured to send each target data structure to each sub-network slice manager, so that after each sub-network slice manager sends a neutral model instance obtained according to each target data structure and the neutral model to a corresponding network element management system, the network element management system generates a configuration file of each network entity corresponding to a corresponding sub-network according to the neutral model instance, where the configuration file is used for normal operation of a business process on the network entity; the neutral model is a network topology template.

The network slice manager provided by the present application can execute the technical solutions shown in the above method embodiments, and the implementation principles and beneficial effects thereof are similar, and are not described herein again.

In a possible implementation, the receiver 81 is further configured to receive an update request sent by the sub-network slice manager; the updating request comprises the name of a target deployment configuration item corresponding to at least one configuration item to be updated and at least one updated configuration value of the target deployment configuration item; the configuration items to be updated are the configuration items to be updated in the corresponding configuration files; the name of the target deployment configuration item and the updated configuration value of the target deployment configuration item are obtained by the sub-network slice manager according to configuration update information, and the configuration update information comprises the name of at least one configuration item to be updated and the updated configuration value;

the processor 82 is further configured to update the corresponding resource file according to the update request.

In a possible implementation manner, the receiver 81 is further configured to receive a first request message sent by the sub-network slice manager if the configuration update information includes at least one group of configuration items, each group of configuration items includes a plurality of first configuration items to be updated, and the plurality of first configuration items to be updated of the same group correspond to the same first target deployment configuration item belonging to the service level agreement SLA parameter; the first request message comprises names and updated configuration values of first neutral model configuration items corresponding to a plurality of first configuration items to be updated included in each group of configuration items; the first request message is used for indicating the network slice manager to acquire the updated configuration value of the first target deployment configuration item corresponding to each group of configuration items; the name of a first neutral model configuration item corresponding to a first configuration item to be updated is acquired by the sub-network slice manager according to a first corresponding relation stored in a database; the first corresponding relation is the corresponding relation between the name of the configuration item in the configuration file and the name of the neutral model configuration item;

the processor 82 is further configured to obtain, according to the first request message and a second corresponding relationship stored in the database, an updated configuration value of the first target deployment configuration item corresponding to each group of configuration items; the second corresponding relation is a relation between the configuration values of the deployment configuration items belonging to the SLA parameters and the configuration values of the neutral model configuration items;

the transmitter 84 is further configured to transmit the updated configuration value of the first target deployment configuration item corresponding to each group of configuration items to the subnetwork slice manager.

Fig. 17 is a schematic structural diagram of a subnet slice manager according to an embodiment of the present application. Referring to fig. 16, the sub-network slice manager may include a receiver 91, a processor 92, a memory 93, a transmitter 94, and a communication bus 95, where the memory 93 is used to store program instructions, the communication bus 95 is used to implement connections between components, the processor 93 is used to read the program instructions in the memory 93 and execute operations corresponding to the program instructions, where,

the receiver 91 is configured to receive a plurality of target data structures sent by a network slice manager, where the plurality of target data structures are obtained by the network slice manager according to a plurality of deployment configuration items related to a plurality of network entities deploying a target network, each target data structure includes a name of a deployment configuration item and a configuration value of the deployment configuration item, and each deployment configuration item corresponds to one target data structure;

the processor 92 is configured to generate a neutral model instance according to all target data structures and neutral models, where the neutral model is a network topology template;

the sender 93 is configured to send the neutral model instance to a corresponding network element management system, so that the network element management system generates a configuration file of at least one target network entity corresponding to the sub-network according to the neutral model instance, and sends the configuration file to the corresponding target network entity, where the configuration file is used for normal operation of a business process on the target network entity.

In one possible implementation, the processor 92, in particular for,

In a possible implementation manner, the receiving module 91 is further configured to receive configuration update information sent by the network element management system, where the configuration update information includes a name of at least one configuration item to be updated and an updated configuration value, and the configuration item to be updated is a configuration item in a corresponding configuration file;

the processor 92 is further configured to obtain a name of a first neutral model configuration item corresponding to each configuration item to be updated according to a first corresponding relationship stored in the database, where the first corresponding relationship is a corresponding relationship between the name of the configuration item in the configuration file and the name of the neutral model configuration item;

the processor 92 is further configured to update the neutral model instance according to the names of all the first neutral model configuration items and the respective corresponding updated configuration values; the updated configuration value of the first neutral model configuration item is the updated configuration value of the corresponding configuration item to be updated;

the processor 92 is further configured to, if the configuration update information includes at least one second configuration item to be updated that does not belong to the SLA parameter, for each second configuration item to be updated, obtain, according to the third correspondence, a name of a second target deployment configuration item corresponding to each second configuration item to be updated;

the processor 92 is further configured to, if the configuration update information includes at least one group of configuration items, each group of configuration items includes multiple first configuration items to be updated, where the multiple first configuration items to be updated of the same group correspond to the same first target deployment configuration item that is an SLA parameter, and for each group of configuration items, according to the third corresponding relationship, obtain names of the first target deployment configuration items corresponding to the multiple first configuration items to be updated included in the group of configuration items, and obtain an updated configuration value of the first target deployment configuration item;

the sender 93 is further configured to send an update request to the network slice manager, where the update request includes a name of a second target deployment configuration item corresponding to each second configuration item to be updated and an updated configuration value of each second configuration item to be updated, and/or a name of at least one first target deployment configuration item and an updated configuration value of at least one first target deployment configuration item, and the update request is used to instruct the network slice manager to update a corresponding resource file of a network entity for deploying a target network.

In a possible implementation, the processor 93 is specifically configured to send a first request message to the network slice manager; the first request message comprises the names of the first neutral model configuration items corresponding to the plurality of first configuration items to be updated included in the corresponding group of configuration items and the updated configuration values corresponding to the plurality of first configuration items to be updated; the first request message is used for instructing a network slice manager to acquire the updated configuration value of the first target deployment configuration item according to the second corresponding relation; and receiving the updated configuration value of the first target deployment configuration item sent by the network slice manager.

The sub-network slice manager provided by the present application can execute the technical solutions shown in the above method embodiments, and the implementation principles and beneficial effects thereof are similar, and are not described herein again.

Fig. 18 is a schematic structural diagram of a network element management system according to an embodiment of the present application. Referring to fig. 18, the network element management system may include a receiver 1001, a processor 1002, a memory 1003, a transmitter 1004, and a communication bus 1005, where the memory 1003 is used to store program instructions, the communication bus 1005 is used to implement connections between components, the processor 1003 is used to read the program instructions in the memory 1003 and execute operations corresponding to the program instructions, where,

the receiver 1001 is configured to receive a neutral model instance sent by a sub-network slice manager; the neutral model instance comprises the name of a neutral model configuration item and the configuration value of the neutral model configuration item, the neutral model instance is obtained by the sub-network slice manager according to a neutral model and a plurality of target data structures, the target data structures are obtained by the network slice manager according to a plurality of deployment configuration items of a plurality of network entities of a deployment target network, each deployment configuration item corresponds to one target data structure, and the target data structures comprise the name of the deployment configuration item and the configuration value of the deployment configuration item;

the processor 1002 is configured to generate a configuration file of at least one target network entity corresponding to a corresponding sub-network according to the neutral model instance;

the sender 1003 is configured to send the configuration file to a corresponding target network entity, where the configuration file is used for normal operation of a service process on the target network entity.

The network element management system provided in the present application may execute the technical solutions shown in the above method embodiments, and the implementation principles and beneficial effects thereof are similar, and are not described herein again.

In one possible implementation, the processor 1002 is specifically configured to,

In a possible implementation manner, the receiver 1001 is further configured to receive configuration update information sent by a network entity, where the configuration update information includes a name of at least one configuration item to be updated and an updated configuration value;

the transmitter 1003 is further configured to send the configuration update information to the sub-network slice manager, so that the sub-network slice manager updates the neutral model instance according to the configuration update information, and sends an update request to the network slice manager after obtaining, according to the configuration update information, a name of a target deployment configuration item corresponding to at least one configuration item to be updated and a configuration value after the at least one target deployment configuration item is updated, where the update request is used to instruct the network slice manager to update a resource file of a network entity for deploying a target network; the update request comprises the name of the target deployment configuration item corresponding to the at least one configuration item to be updated and the updated configuration value of the at least one target deployment configuration item.

Claims

1. A service enabled method, comprising:

the network slice manager receives a plurality of resource files which are sent by a virtualization or cloud orchestration management function entity and used for deploying a plurality of network entities of a target network, wherein the resource files comprise a plurality of deployment configuration items;

the network slice manager analyzes the resource files and generates a plurality of target data structures corresponding to the deployment configuration items; the target data structure comprises the name of the deployment configuration item and the configuration value of the deployment configuration item;

2. The method of claim 1, further comprising:

the network slice manager receives an update request sent by the sub-network slice manager; the updating request comprises the name of a target deployment configuration item corresponding to at least one configuration item to be updated and at least one updated configuration value of the target deployment configuration item; the configuration items to be updated are the configuration items to be updated in the corresponding configuration files; the name of the target deployment configuration item and the updated configuration value of the target deployment configuration item are obtained by the sub-network slice manager according to configuration update information, and the configuration update information comprises the name of at least one configuration item to be updated and the updated configuration value;

3. The method according to claim 2, wherein if the configuration update information includes at least one group of configuration items, each group of configuration items includes a plurality of first configuration items to be updated, and the plurality of first configuration items to be updated of the same group correspond to the same first target deployment configuration item belonging to the service level agreement SLA parameter, the method further includes:

4. A service enabled method, comprising:

the sub-network slice manager generates a neutral model instance according to a plurality of target data structures and a neutral model sent by the network slice manager, wherein the neutral model is a network topology template;

5. The method of claim 4, wherein the sub-network slice manager generates a neutral model instance from all of the target data structures and the neutral models, comprising:

6. The method according to claim 5, wherein if the second deployment configuration item corresponding to the target data structure is an SLA parameter, the acquiring, by the sub-network slice manager, a configuration value of each third neutral model configuration item includes:

7. The method according to claim 5 or 6, wherein if a fourth neutral model configuration item is included in the neutral model, the neutral model configuration item corresponding to each of the deployment configuration items does not include the fourth neutral model configuration item, and the sub-network slice manager generates the neutral model instance according to all the target data structures and the neutral models, further comprising:

8. The method of claim 5, further comprising:

a sub-network slice manager receives configuration update information sent by a network element management system, wherein the configuration update information comprises the name of at least one configuration item to be updated and an updated configuration value, and the configuration item to be updated is a configuration item in a corresponding configuration file;

9. The method of claim 8, wherein obtaining the updated configuration value of the first target deployment configuration item by the subnet slice manager comprises:

the sub-network slice manager sending a first request message to the network slice manager; the first request message comprises the names of the first neutral model configuration items corresponding to the plurality of first configuration items to be updated included in the corresponding group of configuration items and the updated configuration values corresponding to the plurality of first configuration items to be updated; the first request message is used for indicating a network slice manager to acquire the updated configuration value of the first target deployment configuration item according to a second corresponding relation;

10. A service enabled method, comprising:

a network element management system receives a neutral model example sent by a sub-network slice manager; the neutral model instance comprises the name of a neutral model configuration item and the configuration value of the neutral model configuration item, the neutral model instance is obtained by the sub-network slice manager according to a neutral model and a plurality of target data structures, the target data structures are obtained by the network slice manager according to a plurality of deployment configuration items of a plurality of network entities of a deployment target network, each deployment configuration item corresponds to one target data structure, and the target data structures comprise the name of the deployment configuration item and the configuration value of the deployment configuration item; the neutral model is a network topology template;

11. The method of claim 10, wherein the network element management system generates a profile of at least one target network entity corresponding to a corresponding sub-network according to the neutral model instance, comprising:

12. The method of claim 11, wherein the acquiring, by the element management system, the configuration command and the configuration parameter corresponding to each target-neutral model configuration item comprises:

13. The method of claim 10, further comprising:

14. A service enabled device, comprising:

the system comprises a receiving module, a configuration module and a management module, wherein the receiving module is used for receiving a plurality of resource files of a plurality of network entities for deploying a target network, which are sent by a virtualization or cloud deployment management function entity, and the resource files comprise a plurality of deployment configuration items;

a target data structure generating module, configured to parse the plurality of resource files and generate a plurality of target data structures corresponding to the deployment configuration items; the target data structure comprises the name of the deployment configuration item and the configuration value of the deployment configuration item;

15. The apparatus of claim 14, wherein the receiving module is further configured to receive an update request sent by the subnet slice manager; the updating request comprises the name of a target deployment configuration item corresponding to at least one configuration item to be updated and at least one updated configuration value of the target deployment configuration item; the configuration items to be updated are the configuration items to be updated in the corresponding configuration files; the name of the target deployment configuration item and the updated configuration value of the target deployment configuration item are obtained by the sub-network slice manager according to configuration update information, and the configuration update information comprises the name of at least one configuration item to be updated and the updated configuration value;

16. The apparatus of claim 15, wherein the receiving module is further configured to receive a first request message sent by the subnet slice manager if the configuration update information includes at least one group of configuration items, each group of configuration items includes a plurality of first configuration items to be updated, and the plurality of first configuration items to be updated of the same group correspond to the same first target deployment configuration item belonging to a Service Level Agreement (SLA) parameter; the first request message comprises names and updated configuration values of first neutral model configuration items corresponding to a plurality of first configuration items to be updated included in each group of configuration items; the first request message is used for indicating the service enabling device to acquire the updated configuration value of the first target deployment configuration item corresponding to each group of configuration items; the name of a first neutral model configuration item corresponding to a first configuration item to be updated is acquired by the sub-network slice manager according to a first corresponding relation stored in a database; the first corresponding relation is the corresponding relation between the name of the configuration item in the configuration file and the name of the neutral model configuration item;

17. A service enabled device, comprising:

the neutral model instance generation module is used for generating a neutral model instance according to a plurality of target data structures and a neutral model sent by the network slice manager, and the neutral model is a network topology template;

18. The apparatus according to claim 17, characterized in that the neutral model instance generation module is specifically configured to,

for each third neutral model configuration item, the configuration value of the third neutral model configuration item is added to the position corresponding to the name of the third neutral model configuration item.

19. The apparatus according to claim 18, wherein the neutral model instance generation module is specifically configured to send a second request message to the network slice manager if a second deployment configuration item corresponding to a target data structure is an SLA parameter, where the second request message includes a name of each third neutral model configuration item and a configuration value in a corresponding target data structure, and the second request message is used to instruct the network slice manager to obtain a configuration value of each third neutral model configuration item according to a second correspondence stored in a database; the second corresponding relation is a relation between the configuration values of the deployment configuration items belonging to the SLA parameters and the configuration values of the neutral model configuration items;

20. The apparatus according to claim 18 or 19, wherein the neutral model instance generation module is further specifically configured to, if a fourth neutral model configuration item is included in the neutral model and the neutral model configuration item corresponding to each of the deployment configuration items does not include the fourth neutral model configuration item, obtain a configuration value of the fourth neutral model configuration item from a stored database;

21. The apparatus of claim 18, wherein the receiving module is further configured to receive configuration update information sent by a network element management system, where the configuration update information includes a name of at least one configuration item to be updated and an updated configuration value, and the configuration item to be updated is a configuration item in a corresponding configuration file;

22. The apparatus according to claim 21, wherein the obtaining module is specifically configured to send a first request message to the network slice manager; the first request message comprises the names of the first neutral model configuration items corresponding to the plurality of first configuration items to be updated included in the corresponding group of configuration items and the updated configuration values corresponding to the plurality of first configuration items to be updated; the first request message is used for indicating a network slice manager to acquire the updated configuration value of the first target deployment configuration item according to a second corresponding relation;

23. A service enabled device, comprising:

the receiving module is used for receiving the neutral model examples sent by the sub-network slice manager; the neutral model instance comprises the name of a neutral model configuration item and the configuration value of the neutral model configuration item, the neutral model instance is obtained by the sub-network slice manager according to a neutral model and a plurality of target data structures, the target data structures are obtained by the network slice manager according to a plurality of deployment configuration items of a plurality of network entities of a deployment target network, each deployment configuration item corresponds to one target data structure, and the target data structures comprise the name of the deployment configuration item and the configuration value of the deployment configuration item; the neutral model is a network topology template;

the configuration file generation module is used for generating a configuration file of at least one target network entity corresponding to a corresponding sub-network according to the neutral model instance; and the sending module is used for sending the configuration file to a corresponding target network entity, and the configuration file is used for normal operation of a business process on the target network entity.

24. The apparatus according to claim 23, wherein the configuration file generation module is specifically configured to,

25. The apparatus according to claim 24, wherein the configuration file generation module is specifically configured to,

26. The apparatus of claim 23, wherein the receiving module is further configured to receive configuration update information sent by a network entity, where the configuration update information includes a name of at least one configuration item to be updated and an updated configuration value;

27. A network slice manager comprising a processor and a memory, the memory storing program instructions, the processor being configured to read the program instructions from the memory and to perform the method of any of claims 1 to 3 in accordance with the program instructions from the memory.

28. A subnet slice manager comprising a processor and a memory, the memory storing program instructions, the processor reading the program instructions in the memory and executing the method of any of claims 4-9 according to the program instructions in the memory.

29. A network element management system comprising a processor and a memory, the memory being configured to store program instructions, the processor being configured to read the program instructions from the memory and to perform the method of any one of claims 10 to 13 according to the program instructions from the memory.