WO2018098624A1 - 一种管理方法、管理单元及系统 - Google Patents

一种管理方法、管理单元及系统 Download PDF

Info

Publication number
WO2018098624A1
WO2018098624A1 PCT/CN2016/107690 CN2016107690W WO2018098624A1 WO 2018098624 A1 WO2018098624 A1 WO 2018098624A1 CN 2016107690 W CN2016107690 W CN 2016107690W WO 2018098624 A1 WO2018098624 A1 WO 2018098624A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
instance
management
management unit
configuration parameters
Prior art date
Application number
PCT/CN2016/107690
Other languages
English (en)
French (fr)
Inventor
季莉
许瑞岳
邹兰
张凯
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2016/107690 priority Critical patent/WO2018098624A1/zh
Publication of WO2018098624A1 publication Critical patent/WO2018098624A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5077—Network service management, e.g. ensuring proper service fulfilment according to agreements wherein the managed service relates to simple transport services, i.e. providing only network infrastructure

Definitions

  • the embodiments of the present invention relate to the field of communications technologies, and in particular, to a management method, a management unit, and a system.
  • Network Slicing is the core technology of the 5th-Generation (5G) mobile communication system.
  • NS cuts a physical network into multiple virtual end-to-end networks.
  • Each virtual network including devices, access, transmission, and core networks in the network, is logically independent. Any virtual network fails. Will affect other virtual networks.
  • NS enables operators to provide a service-based network and meet more application scenarios, such as high-speed network access anytime, anywhere, and a large number of inter-machine communication.
  • Each application instance has different requirements for the network and different parameter configurations.
  • Each application instance requires a specific NS.
  • the network sharding instance may be composed of at least one virtualized network function (VNF) and/or at least one physical network function (PNF), and the network administrator may compose the NS according to functions required by the application instance.
  • VNF virtualized network function
  • PNF physical network function
  • the VNF instance and/or PNF instance of the instance is configured and activated with corresponding parameters.
  • the parameter management process of the NS instance is: after the NS instance is instantiated by the Network Slice Orchestration And Management (NSOAM) unit, the initial configuration parameter or the update configuration parameter is directly sent to the NS instance.
  • the NS instance configures and activates a network function (NF) instance (for example, a VNF instance and/or a PNF instance) corresponding to the NS instance or the NS instance according to the set of initial configuration parameters or a set of updated configuration parameters.
  • NF network function
  • the network function instance corresponding to the NS instance or the NS instance implements the corresponding entity function.
  • the network function instance corresponding to the NS instance or the NS instance is passively configured and activated according to a set of configuration parameters sent by the NSOAM unit, and cannot be configured and activated in real time according to the network condition. This way of managing NS instances or network function instances is less flexible.
  • the embodiment of the invention provides a management method, a management unit and a system, so as to improve the flexibility of managing a network slice instance or a network function instance.
  • an embodiment of the present invention provides a management method, where the method includes: a first management unit sends a management request for a network slice instance or a network function instance to a second management unit, where the management request carries at least one set of configuration parameters and indications And the indication information is used to indicate whether the at least one set of configuration parameters is activated immediately; the second management unit receives the management request from the first management unit, and manages the network slice instance or the network function instance according to the management request.
  • the at least one set of configuration parameters carried in the foregoing management request is configured by the second management unit, where the indication information carried by the management request is used to indicate when the second management unit activates the configuration parameter, thereby activating the network slice instance or
  • the second management unit can manage the network slice instance or the network function instance in real time according to the network condition, so as to improve the flexibility of managing the network slice instance or the network function instance.
  • the foregoing, by the second management unit, managing the network slice instance or the network function instance according to the at least one set of configuration parameters may be one of the following situations:
  • the foregoing second management unit The network slice instance or the network function instance described above is configured according to the at least one set of configuration parameters.
  • the foregoing second management unit configured to configure the at least one set of configuration parameters, for the network fragment instance or the network function instance, may be a prerequisite for activating the network slice instance or the network function instance.
  • the foregoing second management unit activates the network slice instance or the network function instance according to the foregoing management request.
  • the at least one set of configuration parameters may be considered to have been configured, and the at least one set of configuration parameters may not be configured by the second management unit.
  • the foregoing second management unit configures and activates the network slice instance or the network function instance according to the foregoing management request. At this time, the configuration and activation are performed by the second management unit described above.
  • the foregoing management request may further carry an activation trigger condition of each of the at least one set of configuration parameters.
  • the activation trigger condition can be used to measure the actual situation of the network, so the second management unit can determine when to activate the configuration parameter of the corresponding group according to the actual situation of the network, thereby activating the network slice instance or the network function instance.
  • the activation trigger condition may include a user distribution threshold and/or a load balancing threshold.
  • the actual network condition may be specifically measured by the user distribution threshold and/or the load balancing threshold, so that the second management unit determines when the configuration parameters of the corresponding group are activated.
  • the at least one set of configuration parameters includes a target group configuration parameter, and an activation trigger condition of the target group configuration parameter is a target activation trigger condition, where the second management unit root
  • the specific process of managing the foregoing network slice instance or the foregoing network function instance according to the foregoing management request may be: the second management unit acquires a network parameter, and activates the target group if the network parameter satisfies the target activation trigger condition.
  • the configuration parameters are activated to activate the above network slice instance or the above network function instance.
  • the configuration parameter of the corresponding group is activated, thereby activating a network slice instance or a network function instance. Therefore, in the solution of the embodiment of the present invention, the second management unit can manage the network slice instance or the network function instance according to the actual situation of the network, so as to improve management flexibility.
  • the foregoing management request may further carry a group identifier of each of the at least one set of configuration parameters.
  • the group identifier can be used to distinguish different sets of configuration parameters, so that the second management unit can be configured and activated in a targeted manner for different groups of configuration parameters.
  • the management request may be an initial instance management request, the at least one set of configuration parameters being at least one set of initial configuration parameters; or the management request may be an update instance management request, At least one set of configuration parameters is at least one set of updated configuration parameters.
  • the embodiment of the present invention provides a first management unit, which can implement the functions performed by the first management unit in the foregoing method instance, and the functions can be implemented by hardware or by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the first management unit includes a processor and a communication interface, and the processor is configured to support the first management unit to perform a corresponding function in the foregoing method.
  • the communication interface is used to support communication between the first management unit and the second management unit or other network elements.
  • the first management unit can also include a memory for coupling with the processor that holds program instructions and data necessary for the first management unit.
  • the embodiment of the present invention provides a second management unit, which can implement the functions performed by the second management unit in the foregoing method instance, and the functions can be implemented by hardware or by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the second management unit includes a processor and a communication interface, and the processor is configured to support the second management unit to perform a corresponding function in the foregoing method.
  • the communication interface is used to support communication between the second management unit and the first management unit or other network elements.
  • the second management unit can also include a memory for coupling with the processor that holds the program instructions and data necessary for the second management unit.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions used by the first management unit, which includes a program designed to perform the above aspects.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions used by the second management unit, which includes a program designed to perform the above aspects.
  • embodiments of the present invention provide a computer program product comprising instructions that, when executed by a computer, cause a computer to perform functions performed by a first management unit in the method design described above.
  • embodiments of the present invention provide a computer program product comprising instructions that, when executed by a computer, cause a computer to perform functions performed by a second management unit in the method design described above.
  • an embodiment of the present invention provides a communication system, where the system includes the first management unit and the second management unit described in the foregoing aspects.
  • a management request for a network slice instance or a network function instance is sent to the second management unit by using the first management unit, where the management request includes at least one set of configuration parameters and is used to indicate whether at least one set of configuration parameters is immediate
  • the second management unit receives the management request, and manages the network slice instance or the network function instance according to the management request, so that the management can be performed in real time according to the network condition, so as to improve the network slice instance or the network function instance. Management flexibility.
  • FIG. 1 is a schematic diagram of a possible network architecture according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of communication of a management method according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of communication of another management method according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of communication according to still another management method according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of communication according to still another management method according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of a first management unit according to an embodiment of the present disclosure.
  • FIG. 6B is a schematic structural diagram of another first management unit according to an embodiment of the present disclosure.
  • FIG. 7A is a schematic structural diagram of a second management unit according to an embodiment of the present invention.
  • FIG. 7B is a schematic structural diagram of another second management unit according to an embodiment of the present invention.
  • the network architecture and the service scenario described in the embodiments of the present invention are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present invention, and are not limited to the technical solutions provided by the embodiments of the present invention.
  • the technical solutions provided by the embodiments of the present invention are equally applicable to similar technical problems.
  • FIG. 1 is a schematic diagram of a possible network architecture according to an embodiment of the present invention.
  • Figure 1 shows a possible implementation of the 5G virtual network architecture.
  • the network architecture shown in FIG. 1 includes: a Network Slice Orchestration and Management (NSOAM) unit, a Common Network Function (Common NF) unit, and a network slicing unit.
  • the Common NF unit can be replaced by a Network Function Controller (NF Controller) unit; or, the Common NF unit can have the function of the NF Controller unit in addition to its own function.
  • the "general network function/network function control unit" in Fig. 1 represents a unit having a function of a Common NF unit and/or a function of an NF Controller unit. The following briefly introduces the various units involved in Figure 1.
  • the NSOAM unit can be used to create, manage, and revoke network slices.
  • the operator first generates a network slice template according to the requirements of the service scenario.
  • the slice template includes network function modules required by the service scenario, interfaces between the network function modules, and network resources required by the function modules.
  • the NSOAM unit according to the slice template Apply for network resources and instantiate the interface for creating virtual network function modules on the applied resources.
  • the NSOAM unit can supervise and manage the formed network slice, and allow the network resource allocation to be expanded, reduced, and dynamically adjusted according to the actual traffic volume, and the network slice is revoked after the life cycle expires.
  • the NSOAM unit can optimize the network slice partitioning and network resource allocation through big data-driven network optimization, realize automatic operation and maintenance, respond to network and service changes in time, ensure user experience and improve network resource utilization.
  • the Common NF/NF controller unit can be used to control the configuration and activation of an NS instance or NF instance.
  • the prerequisite for the activation is that the NS instance or the NF instance has been configured with the corresponding configuration parameters.
  • the network slicing unit may include at least one network slice instance, each network slice instance including at least one network function instance.
  • Common NF/NF controller unit may be set as a separate network entity, or may be set as a functional module in the network slicing unit, as the case may be.
  • the parameter management process for the NS instance is as follows: the NSOAM unit instantiates an NS instance, and the instantiated NS instance is located in the network slicing unit; the NSOAM unit directly sends initial configuration parameters or updates to the NS instance in the network slicing unit.
  • the configuration parameter, the NS instance configures and activates the NS instance or the network function instance corresponding to the NS instance (including, for example, a VNF instance and/or a PNF instance) according to the set of initial configuration parameters or a set of updated configuration parameters, thereby
  • the NS instance or the network function instance corresponding to the NS instance implements the corresponding entity function.
  • the network function instance corresponding to the NS instance or the NS instance is passively configured and activated according to a set of configuration parameters sent by the NSOAM unit, and cannot be configured and activated in real time according to the network condition.
  • This way of managing NS instances or network function instances is less flexible and reduces the efficiency of network operations.
  • the embodiment of the present invention provides a management method, and a second management unit, a first management unit, and a system based on the method, so as to improve flexibility in managing a network slice instance or a network function instance, thereby improving the network.
  • the efficiency of the operation the first management unit sends a management request for the network slice instance or the network function instance to the second management unit, where the management request carries at least one set of configuration parameters and indication information, where the indication information is used to indicate the at least one set of configuration parameters Whether to activate immediately; after receiving the management request from the first management unit, the second management unit manages the network slice instance or the network function instance according to the management request.
  • the network segment instance in the embodiment of the present invention may be any network slice instance selected in the network slice unit shown in FIG. 1.
  • the network function instance in the embodiment of the present invention may be a selected network slice instance.
  • the corresponding network function instance may also be any network function instance selected in the network slicing unit shown in FIG. 1 , wherein the network function instance may be a VNF instance or a PNF instance, and the specific type and the specific quantity are determined according to the situation. , not limited here.
  • the management request sent by the first management unit to the second management unit, in addition to carrying at least one set of configuration parameters, is carried to indicate whether the at least one set of configuration parameters is activated immediately
  • the indication information enables the second management unit to manage the network slice instance or the network function instance according to the management request, so as to improve the flexibility of managing the network slice instance or the network function instance.
  • the foregoing management request may be an initial instance management request, where the initial instance management request is used to instruct the second management unit to manage the initially instantiated network slice instance or the network function instance; or the foregoing management request may be an update instance management request, The update instance management request is used to instruct the second management unit to perform update management on the activated network slice instance or network function instance.
  • the first management unit is one end that sends a management request, and may be, for example, an NSOAM unit as shown in FIG.
  • Operation Support System (OSS)/Business Support System (BSS) is a support system for telecom operators' integration and information resource sharing. It is mainly composed of network management, system management, and billing. The business, accounting, and customer business are partially composed, and the systems are integrated through a unified information bus.
  • the second management unit is a receiving management request, and may be a configuration unit and/or a functional unit. For example, the common NF/NF controller unit or the network slicing unit shown in FIG.
  • EMS network element management system
  • NF Manager Network Function Management
  • the EMS is a system that manages one or more telecommunication network elements (NEs) of a specific type.
  • NEs network elements
  • the network function management unit is mainly responsible for configuration management, performance management, fault management, security management, and billing management.
  • FIG. 2 shows a management method provided by an embodiment of the present invention.
  • the method shown in FIG. 2 can be applied to the network architecture shown in FIG. 1, wherein the first management unit can be an NSOAM unit, and the second management unit can be a Common NF/NF controller unit or a network slicing unit.
  • the first management unit can be an NSOAM unit
  • the second management unit can be a Common NF/NF controller unit or a network slicing unit.
  • the first management unit sends a management request for the network slice instance or the network function instance to the second management unit, where the management request carries at least one set of configuration parameters and indication information, where the indication information is used to indicate the at least one set of configuration parameters Whether to activate immediately.
  • the first management unit may instantiate a network slice instance before the first management unit sends the above management request to the second management unit.
  • the first management unit may instantiate the network slice instance according to the instantiation request sent by the OSS/BSS, or the first management unit may instantiate the network slice instance according to the requirement information input by the administrator.
  • the process of instantiating a network slice instance may include: the first management unit instantiates a network function instance corresponding to the network slice instance, thereby instantiating a network slice instance; the first management unit establishes a connection between different network function instances corresponding to the network slice instance, and establishes a network slice instance and The connection between the other network slice instances; the first management unit allocates the network resources required by the network slice instance or the network function instance corresponding to the network slice instance.
  • the network segment instance corresponding to the network segment instance or the network segment instance is not a functional entity that can be run.
  • the function entity can be converted into a functional entity.
  • Application instance features, such as service gateway functionality.
  • the network function instance corresponding to the instantiated network slice instance or network slice instance may be managed by the second management unit.
  • the first management unit may instantiate the network function instance before the first management unit sends the foregoing management request to the second management unit.
  • the first management unit may instantiate the network function instance according to the instantiation request sent by the OSS/BSS, or the first management unit may instantiate the network function instance according to the demand information input by the administrator.
  • the process of instantiating a network function instance is similar to the process of instantiating a network slice instance, and may be implemented by referring to the process of instantiating a network slice instance, which is not described herein.
  • the network function instance needs to be configured and activated to become a network function entity that can be run.
  • the instantiated network function instance can be managed by the second management unit.
  • the number of instantiated network function instances is not limited herein.
  • the management request for the network slice instance or the network function instance may be sent to the second management unit through the communication interface between the first management unit and the second management unit.
  • the network function instance may be a network function instance corresponding to the network slice instance, or may be a network function instance that is not related to the network slice instance.
  • the network slice instance or the network function instance may also be configured according to the at least one set of configuration parameters.
  • the foregoing indication information may be specifically used to indicate whether the second management unit activates the at least one set of configuration parameters immediately after configuring at least one set of configuration parameters.
  • the indication information may be indicated by a certain field, for example, a field is “0”, indicating that it is activated immediately; otherwise, the field is “1”, indicating that it is not activated immediately.
  • the indication information may be a pair of configuration parameters of each of at least one set of configuration parameters.
  • the indication information should be used to indicate whether the configuration parameters of the corresponding group are activated immediately. For example, if the indication information corresponding to a certain group of configuration parameters indicates immediate activation, the second management unit may activate the group configuration parameter immediately after configuring the group configuration parameter, thereby activating a network slice instance or a network function instance.
  • the indication information may be indication information corresponding to all group configuration parameters of the at least one group of configuration parameters, and is used to indicate whether all group configuration parameters are activated immediately.
  • each of the at least one set of configuration parameters may be identical, partially the same, or completely different.
  • Each set of configuration parameters may include at least one of a capacity parameter, a quality of service (QoS) parameter, a specification parameter, and the like.
  • QoS quality of service
  • Each set of configuration parameters may also include other parameters.
  • the configuration parameter may be a handover parameter, such as a Cell Specific Offset (CIO).
  • CIO Cell Specific Offset
  • the management request may also carry an activation trigger condition for each of the at least one set of configuration parameters.
  • the activation trigger condition may include a user distribution threshold and/or a load balancing threshold.
  • the user distribution threshold and load balancing threshold may be different for different group configuration parameters. The specific values are not limited here.
  • the user distribution threshold is used to describe the distribution of users in the current network
  • the load balancing threshold is used to describe the amount of user access in the current network.
  • the activation condition can reflect the actual situation of the current network, so that the second management unit can activate the configuration parameters of the corresponding group according to the actual needs of the network, thereby activating the network slice instance or the network function instance.
  • the management request may further carry a group identifier of each of the at least one set of configuration parameters for distinguishing different sets of configuration parameters, so that the second management unit can target different sets of configuration parameters. Configure and activate.
  • the foregoing management request may be an initial instance management request or an update instance management request.
  • at least one set of configuration parameters is at least one set of initial configuration parameters, ie, at least one set of configuration parameters required for initial configuration of the network slice instance or network function instance.
  • the at least one set of configuration parameters is at least one set of updated configuration parameters, that is, at least one set of configuration parameters required to update the network slice instance or the network function instance.
  • the network slice instance may be composed of multiple functional entities.
  • the first management unit may separately send configuration parameters to multiple functional entities.
  • the second management unit manages the network slice instance or the network function instance according to the management request.
  • the second management unit configures a network slice instance or a network function instance according to the at least one set of configuration parameters. At this time, the second management unit configures the at least one set of configuration parameters for the network slice instance or the network function instance, which is a prerequisite for activating the network slice instance or the network function instance. It can be understood that at this time, the second management unit is only configured, and no activation is performed, and the activation may be performed by other units.
  • the second management unit activates the network slice instance or the network function instance according to the foregoing management request, and at this time, the at least one set of configuration parameters may be considered to be configured, and may not be configured by the second management unit.
  • the second management unit configures and activates a network slice instance or a network function instance according to the above management request, at which time both configuration and activation are performed by the second management unit.
  • the indication information indicates that the at least one set of configuration parameters is activated immediately, and the second management unit may activate the configuration parameter of the corresponding group according to the indication information, thereby activating a network slice instance or a network function instance.
  • a network slice instance or a network function instance may have some or several functions and capabilities, and an activated network slice instance or network function instance may be used.
  • the foregoing indication information indicates that the at least one set of configuration parameters are not immediately activated, and the second management unit may determine when to activate the at least one set of configuration parameters according to actual network conditions.
  • the at least one set of configuration parameters may include a target group configuration parameter, the activation trigger condition of the target group configuration parameter is a target activation trigger condition, and the second management unit may acquire a network parameter; when the network parameter satisfies the target When the trigger condition is activated, the second management unit can activate the network slice instance or the network function instance according to the target group configuration parameter.
  • the second management unit may acquire network parameters, which may include user distribution parameters and/or load balancing parameters; if the network parameters meet the target activation trigger condition, the second management unit activates the target group configuration parameters, thereby activating the network slice.
  • An instance or network function instance such that the network slice instance or network function instance has the function and performance corresponding to the target group configuration parameter.
  • the second management unit may acquire network parameters in real time in the network architecture, and detect in real time whether the obtained network parameters meet the activation trigger condition corresponding to a certain set of configuration parameters, and when satisfied, activate the group configuration parameters.
  • the second management unit may further feed back the group identifier of the target group configuration parameter to the first management unit, to notify the first management unit that the target group configuration parameter is activated, and the network slice instance or The network function instance already has the function and performance corresponding to the target group configuration parameter.
  • the first management unit sends a management request for the network slice instance or the network function instance to the second management unit, where the management request carries at least one set of configuration parameters and is used to indicate whether at least one set of configuration parameters is activated immediately
  • the second management unit manages the network slice instance or the network function instance according to the management request, so that management can be performed in real time according to the network condition, so as to improve management of the network slice instance or the network function instance. Flexibility.
  • FIGS. 3 to 5 The embodiments of the present invention will be further described below with reference to FIGS. 3 to 5.
  • the same or similar content as the method shown in FIG. 2 can be referred to the detailed description in FIG. 2, and details are not described herein again.
  • FIG. 3 is a schematic diagram of communication of another management method provided by an embodiment of the present invention.
  • the method shown in FIG. 3 can be applied to the network architecture shown in FIG. 1.
  • the first management unit is an NSOAM unit
  • the second management unit is a Common NF/NF controller unit or
  • the network slicing unit is used as an example to introduce the solution of the embodiment of the present invention, and the Common NF/NF controller unit and the network slicing unit are independent of each other.
  • the NSOAM unit sends a management request for the network slice instance to the network slicing unit, the management request including at least one set of configuration parameters and indication information, the indication information being used to indicate whether the at least one set of configuration parameters is immediately activated.
  • the NSOAM unit sends a management request for the network slice instance or network function instance to the network slice unit through the communication interface between the NSOAM unit and the network slice unit after instantiating the network slice instance or the network function instance.
  • the network function instance may be a network function instance corresponding to the network slice instance, or may be a network function instance that is not related to the network slice instance.
  • the network slicing unit configures the network slice instance according to at least one set of configuration parameters.
  • the network slicing unit configures the network slice instance according to the at least one set of configuration parameters to facilitate subsequent activation of the configuration parameters.
  • the network slicing unit activates the configuration parameter of the corresponding group according to the indication information.
  • the network slicing unit sends a first response message to the NSOAM unit.
  • the network slicing unit may send a first response message to the NSOAM unit by using a communication interface between the network slicing unit and the NSOAM unit, to notify the NSOAM unit, the network.
  • the slice instance is configured with the at least one set of configuration parameters. If the network slice unit activates the configuration parameter of a certain group, the first response message further carries the group identifier of the activated configuration parameter. It should be noted that part 303 is an optional part.
  • the NSOAM unit sends a configuration parameter table to the Common NF/NF controller unit, the configuration parameter table including an activation trigger condition.
  • the NSOAM unit can send a configuration parameter table to the Common NF/NF controller unit through a communication interface between the NSOAM unit and the Common NF/NF controller unit.
  • the configuration parameter table includes an identifier of the network slice instance, a group identifier of each group of configuration parameters of the at least one set of configuration parameters, and an activation trigger condition of each group of configuration parameters.
  • the group identification of each set of configuration parameters may also include an activated identification so that the Common NF/NF controller unit is aware of the activation.
  • the Common NF/NF controller unit configures a network slice instance.
  • the Common NF/NF controller unit configures the network slice instance described above based on the at least one set of configuration parameters described above.
  • the Common NF/NF controller unit obtains network parameters.
  • the Common NF/NF controller unit detects if the network parameters meet the target activation trigger condition.
  • the at least one set of configuration parameters includes a target group configuration parameter, and the activation trigger condition of the target group configuration parameter is a target activation trigger condition.
  • the above target group configuration parameter may be any set of configuration parameters that are not activated.
  • the Common NF/NF controller unit sends an activation indication message to the network slicing unit.
  • the Common NF/NF controller unit When the network parameter meets the target activation triggering condition, the Common NF/NF controller unit sends the activation indication information to the network slicing unit through the communication interface between the Common NF/NF controller unit and the network slicing unit.
  • the activation indication information includes a group identifier of the target group configuration parameter, so that the network slice unit activates the group configuration parameter.
  • the controller unit may also send a query message to the NSOAM unit to notify the NSOAM unit that a certain network slicing unit satisfies the specific condition, and the Common NF/NF controller unit sends the activation indication to the network slicing unit after receiving the confirmation message of the NSOAM unit. information.
  • the network slicing unit activates the configuration parameters of the corresponding group according to the activation indication information.
  • the network slicing unit sends a second response message to the Common NF/NF controller unit.
  • the network slicing unit sends a second response message to the Common NF/NF controller unit through a communication interface between the network slicing unit and the Common NF/NF controller unit.
  • the second response message is used to notify the Common NF/NF controller unit, which group configuration parameter is activated by the network slice instance, and the second response message may carry the group identifier of the activated configuration parameter.
  • part 310 is an optional part.
  • the network slicing unit sends an activation notification message to the NSOAM unit.
  • the network slicing unit transmits an activation notification message to the NSOAM unit through a communication interface between the network slicing unit and the NSOAM unit.
  • the activation notification message is used to notify the NSOAM unit, which group configuration parameters are activated by the network slice instance, and the activation notification message may carry the group identifier of the activated configuration parameter, including the group identifier of the configuration parameter activated according to the indication information and according to the network parameter.
  • the group ID of the activated configuration parameter may be noted that part 311 is an optional part.
  • the Common NF/NF controller unit determines when to activate the configuration parameter according to the network parameter, and the Common NF/NF controller unit controls the network slicing unit to activate, realizing activation in real time according to the network condition, thereby improving the pair. Network slicing instances for management flexibility.
  • FIG. 4 is a schematic diagram of communication of still another management method according to an embodiment of the present invention.
  • the method shown in FIG. 4 can be applied to the network architecture shown in FIG. 1.
  • the first management unit is an NSOAM unit
  • the second management unit is a network slicing unit.
  • the embodiment shown in FIG. 4 is the same as the embodiment shown in FIG. 2 or FIG. 3, and details are not described herein again.
  • the NSOAM unit sends a management request for the network slice instance to the network slice unit, the management request including at least one set of configuration parameters, indication information, and an activation trigger condition, the indication information being used to indicate whether the at least one set of configuration parameters is activated immediately .
  • the management request includes at least one set of configuration parameters.
  • the description of the activation triggering condition of the group configuration parameter can be referred to the specific description of the embodiment shown in FIG. 2, and details are not described herein again.
  • the network slicing unit configures a network slice instance based on at least one set of configuration parameters.
  • the network slicing unit sends a first response message to the NSOAM unit.
  • part 403 is an optional part.
  • the network slicing unit obtains network parameters.
  • the network slicing unit detects whether the network parameter satisfies the target activation trigger condition.
  • the at least one set of configuration parameters includes a target group configuration parameter, and the activation trigger condition of the target group configuration parameter is a target activation trigger condition.
  • the above target group configuration parameter may be any set of configuration parameters that are not activated.
  • the network slicing unit activates the target group configuration parameters.
  • the network slicing unit activates the target group configuration parameter to activate the network slice instance.
  • the network slicing unit sends a second response message to the NSOAM unit.
  • the second response message is used to notify the NSOAM unit, which group configuration parameters are activated by the network slice instance, and the second response message may carry the group identifier of the activated configuration parameter, including the group identifier of the configuration parameter activated according to the indication information.
  • the network slicing unit determines when to activate the configuration parameter according to the network parameter and activates, realizing activation in real time according to the network condition, thereby improving flexibility in managing the network slice instance.
  • FIG. 5 is a schematic diagram of communication of another management method provided by an embodiment of the present invention.
  • the method shown in FIG. 5 can be applied to the network architecture shown in FIG. 1.
  • the first management unit is an NSOAM unit
  • the second management unit is a Common NF/NF controller unit.
  • the Common NF/NF controller unit can be a network function or a configuration unit
  • the network slicing unit is a network element.
  • the embodiment shown in FIG. 5 is the same as the embodiment shown in FIG. 2, FIG. 3 or FIG. 4, and details are not described herein again.
  • the NSOAM unit sends a management request to the Common NF/NF controller unit, the management request including at least one set of configuration parameters, indication information, and an activation trigger condition, the indication information being used to indicate whether the at least one set of configuration parameters is activated immediately.
  • the management request may be a management request (configuration request) in the embodiment shown in FIG. 3 or FIG. 4, or may be a management object creation request or a management object configuration request.
  • the Common NF/NF controller unit is configured according to at least one set of configuration parameters.
  • the Common NF/NF controller unit maintains the at least one set of configuration parameters described above and/or is configured according to at least one of the set of configuration parameters described above.
  • the Common NF/NF controller unit can be configured with parameters for the corresponding management object, or can directly configure parameters for the corresponding network slice instance or network function entity.
  • the Common NF/NF controller unit obtains network parameters.
  • the Common NF/NF controller unit detects if the network parameter satisfies the target activation trigger condition.
  • the at least one set of configuration parameters includes a target group configuration parameter, and the activation trigger condition of the target group configuration parameter is a target activation trigger condition.
  • the above target group configuration parameter may be any set of configuration parameters that are not activated.
  • the Common NF/NF controller unit sends an activation indication message to the network slicing unit.
  • the network slicing unit activates the configuration parameters of the respective group based on the activation indication information.
  • the network slicing unit sends a response message to the Common NF/NF controller unit.
  • the response message is used to inform the Common NF/NF controller unit, which group of configuration parameters are activated by the network slicing unit, and the response message may carry the group identifier of the activated configuration parameter. It should be noted that part 507 is an optional part.
  • the network slicing unit sends an activation notification message to the NSOAM unit.
  • the activation notification message is used to inform the NSOAM unit of which group configuration parameters are activated by the network slicing unit, and the activation notification message may carry the group identifier of the activated configuration parameter. It should be noted that part 508 is an optional part.
  • the configuration is performed by the Common NF/NF controller unit, and when the configuration parameters are activated according to the network parameters, and the Common NF/NF controller unit controls the network slicing unit to activate, realizing activation according to the network condition in real time. , thereby improving the flexibility of managing network slice instances.
  • the difference from the embodiment shown in FIG. 3 is that the embodiment shown in FIG. 3 consists of The network slicing unit is configured, and the embodiment shown in FIG. 5 is configured by the Common NF/NF controller unit.
  • the management request in the embodiment shown in FIG. 3, FIG. 4 or FIG. 5 is an initial instance management request, and the embodiment for updating the instance management request is similar to the embodiment shown in FIG. 3, FIG. 4 or FIG. , will not repeat them here.
  • the embodiment shown in FIG. 3, FIG. 4 or FIG. 5 introduces the management of the network slice instance, and the management of the network function instance is similar, and details are not described herein again.
  • each network element for example, the first management unit, the second management unit, and the like, in order to implement the above functions, includes hardware structures and/or software modules corresponding to each function.
  • the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
  • the embodiment of the present invention may divide the function module by using the first management unit, the second management unit, and the like according to the foregoing method example.
  • each function module may be divided according to each function, or two or more functions may be integrated in the function.
  • a processing module In a processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 6A shows a possible structural diagram of the first management unit involved in the above embodiment.
  • the first management unit 600 includes a processing module 602 and a communication module 603.
  • the processing module 602 is configured to control and manage the actions of the first management unit.
  • the processing module 602 is configured to support the first management unit to perform the process 201 in FIG. 2, the processes 301 and 304 in FIG. 3, and the process in FIG. 401, process 501 in FIG. 5, and/or other processes for the techniques described herein.
  • the communication module 603 is configured to support communication between the first management unit and the second management unit or other network entity, such as communication with the Common NF/NF controller unit or network slicing unit shown in FIG.
  • the first management unit may further include a storage module 601 for storing program codes and data of the first management unit.
  • the processing module 602 can be a processor or a controller, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit, ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication module 603 can be a communication interface, a transceiver or a transceiver circuit, etc., wherein the communication interface is a collective name and can include one or more interfaces.
  • the storage module 601 can be a memory.
  • the first management unit involved in the embodiment of the present invention may be the first management unit shown in FIG. 6B.
  • the first management unit 610 includes a processor 612, a communication interface 613, and a memory 611.
  • the first management unit 610 may further include a bus 614.
  • the communication interface 613, the processor 612, and the memory 611 may be connected to each other through a bus 614.
  • the bus 614 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (abbreviated). EISA) bus and so on.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus 614 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 6B, but it does not mean that there is only one bus or one type of bus.
  • FIG. 7A shows a possible structural diagram of the second management unit involved in the above embodiment.
  • the second management unit 700 includes a processing module 702 and a communication module 703.
  • the processing module 702 is configured to perform control management on the actions of the second management unit.
  • the processing module 702 is configured to support the second management unit to perform the process 202 in FIG. 2, the processes 302, 303, and 305-311 in FIG. Processes 402-407 in 4, processes 502-508 in Figure 5, and/or other processes for the techniques described herein.
  • the communication module 703 is configured to support communication between the second management unit and the first management unit or other network entity, such as communication with the NSOAM unit shown in FIG.
  • the second management unit may further include a storage module 701 for storing program codes and data of the second management unit.
  • the processing module 702 can be a processor or a controller, such as a central processing unit, a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a transistor logic device, or a hardware. A component or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication module 703 can be a communication interface, a transceiver or a transceiver circuit, etc., wherein the communication interface is a collective name and can include one or more interfaces.
  • the storage module 701 can be a memory.
  • the second management unit involved in the embodiment of the present invention may be the second management unit shown in FIG. 7B.
  • the second management unit 710 includes a processor 712, a communication interface 713, and a memory 711.
  • the second management unit 710 may further include a bus 714.
  • the communication interface 713, the processor 712, and the memory 711 may be connected to each other through a bus 714; the bus 714 may be a peripheral component interconnection standard bus or an extended industry standard structure bus or the like.
  • the bus 714 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 7B, but it does not mean that there is only one bus or one type of bus.
  • the steps of the method or algorithm described in connection with the disclosure of the embodiments of the present invention may be implemented in a hardware manner, or may be implemented by a processor executing software instructions.
  • the software instructions may be composed of corresponding software modules, which may be stored in a random access memory (RAM), a flash memory, a read only memory (ROM), an erasable programmable read only memory ( Erasable Programmable ROM (EPROM), Electrically Erasable Programmable Read Only Memory (EEPROM), registers, hard disk, removable hard disk, read-only optical disk (CD-ROM) or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC.
  • the ASIC can be located in the first management unit or the second management unit.
  • the processor and the storage medium may also exist as discrete components in the first management unit or the second management unit.
  • the functions described in the embodiments of the present invention may be implemented in hardware, software, firmware, or any combination thereof.
  • the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium.
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

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

Abstract

本发明实施例提供一种管理方法、管理单元及系统，其中方法包括：第一管理单元向第二管理单元发送针对网络切片实例或网络功能实例的管理请求，所述管理请求携带至少一组配置参数和指示信息，所述指示信息用于指示所述至少一组配置参数是否立即激活；所述第二管理单元从所述第一管理单元接收所述管理请求，并根据所述管理请求对所述网络切片实例或所述网络功能实例进行管理。本发明实施例能够提高对网络切片实例或网络功能实例进行管理的灵活性。

Description

一种管理方法、管理单元及系统 技术领域
本发明实施例涉及通信技术领域，尤其涉及一种管理方法、管理单元及系统。
背景技术
网络切片(Network Slicing，NS)是第五代(5th-Generation，5G)移动通信系统的核心技术。NS将一个物理网络切割成多个虚拟的端到端的网络，每个虚拟网络之间，包括网络内的设备、接入、传输和核心网，是逻辑独立的，任何一个虚拟网络发生故障都不会影响到其它虚拟网络。NS使得运营商可以提供一种基于服务的网络，并满足更多的应用案例，例如随时随地的高速网络接入，大量的机器间的通信等。每个应用实例都对网络提出了不同的需求以及不同的参数配置，每个应用实例都需要特定的NS。
网络切片实例可以由至少一个虚拟网络功能(Virtualized Network Function，VNF)和/或至少一个物理网络功能(Physical Network Function，PNF)组成，网络管理者可以根据应用实例所需实现的功能来对组成NS实例的VNF实例和/或PNF实例进行相应的参数配置并激活。
目前，对NS实例进行参数管理的过程为：网络切片编排和管理(Network Slice Orchestration And Management，NSOAM)单元实例化一个NS实例后，直接向该NS实例下发初始配置参数或更新配置参数，该NS实例根据下发的一组初始配置参数或一组更新配置参数配置并激活该NS实例或该NS实例对应的网络功能(Network Function，NF)实例(例如包括VNF实例和/或PNF实例)，从而使得该NS实例或该NS实例对应的网络功能实例实现对应的实体功能。由此可见，该NS实例或该NS实例对应的网络功能实例被动地根据NSOAM单元下发的一组配置参数进行配置、激活，无法根据网络情况实时进行配置、激活。这种对NS实例或网络功能实例进行管理的方式灵活性较低。
发明内容
本发明实施例提供了一种管理方法、管理单元及系统，以期提高对网络切片实例或网络功能实例进行管理的灵活性。
一方面，本发明实施例提供一种管理方法，该方法包括：第一管理单元向第二管理单元发送针对网络切片实例或网络功能实例的管理请求，该管理请求携带至少一组配置参数和指示信息，该指示信息用于指示该至少一组配置参数是否立即激活；第二管理单元从第一管理单元接收该管理请求，并根据该管理请求对网络切片实例或网络功能实例进行管理。
其中，上述管理请求携带的至少一组配置参数用于上述第二管理单元进行配置，上述管理请求携带的指示信息用于指示上述第二管理单元何时激活配置参数，从而激活上述网络切片实例或上述网络功能实例，因此本发明实施例中，第二管理单元可根据网络情况实时对网络切片实例或网络功能实例进行管理，以提高对网络切片实例或网络功能实例进行管理的灵活性。
在一种可能实现的方式中，上述第二管理单元根据上述至少一组配置参数对上述网络切片实例或上述网络功能实例进行管理可以为如下情形之一：第一种情形，上述第二管理单元根据上述至少一组配置参数配置上述网络切片实例或上述网络功能实例。此时上述第二管理单元为上述网络切片实例或上述网络功能实例配置上述至少一组配置参数，可以是对上述网络切片实例或上述网络功能实例进行激活的前提条件。第二种情形，上述第二管理单元根据上述管理请求激活上述网络切片实例或上述网络功能实例。此时可认为上述至少一组配置参数已配置，该至少一组配置参数可能不是由上述第二管理单元配置的。第三种情形，上述第二管理单元根据上述管理请求配置并激活上述网络切片实例或上述网络功能实例。此时配置和激活均由上述第二管理单元执行。
在一种可能实现的方式中，上述管理请求还可以携带上述至少一组配置参数中每组配置参数的激活触发条件。其中，激活触发条件可用于衡量网络实际情况，因此第二管理单元能够根据网络实际情况确定何时激活相应组的配置参数，从而激活网络切片实例或网络功能实例。
在一种可能实现的方式中，上述激活触发条件可以包括用户分布门限和/或负载均衡门限。在这种情况下，具体可以由用户分布门限和/或负载均衡门限来衡量网络实际情况，以使得第二管理单元确定何时激活相应组的配置参数。
在一种可能实现的方式中，上述至少一组配置参数包括目标组配置参数，该目标组配置参数的激活触发条件为目标激活触发条件，上述第二管理单元根 据上述管理请求激活上述网络切片实例或上述网络功能实例进行管理的具体过程可为：上述第二管理单元获取网络参数，并在该网络参数满足上述目标激活触发条件的情况下，激活上述目标组配置参数，从而激活上述网络切片实例或上述网络功能实例。该种可能实现的方式中，在网络参数满足某个激活触发条件时，激活对应组的配置参数，从而激活网络切片实例或网络功能实例。因此本发明实施例的方案中，第二管理单元能够根据网络实际情况对网络切片实例或网络功能实例进行管理，以提高管理的灵活性。
在一种可能实现的方式中，上述管理请求还可以携带上述至少一组配置参数中每组配置参数的组标识。其中，组标识可用于区分不同组的配置参数，以使得上述第二管理单元能够对不同组的配置参数针对性地配置、激活。
在一种可能实现的方式中，所述管理请求可以为初始实例管理请求，所述至少一组配置参数为至少一组初始配置参数；或者，所述管理请求可以为更新实例管理请求，所述至少一组配置参数为至少一组更新后的配置参数。
另一方面，本发明实施例提供了一种第一管理单元，该第一管理单元可以实现上述方法实例中第一管理单元所执行的功能，所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。
在一种可能的实现方式中，该第一管理单元的结构中包括处理器和通信接口，该处理器被配置为支持该第一管理单元执行上述方法中相应的功能。该通信接口用于支持该第一管理单元与第二管理单元或其他网元之间的通信。该第一管理单元还可以包括存储器，该存储器用于与处理器耦合，其保存该第一管理单元必要的程序指令和数据。
另一方面，本发明实施例提供了一种第二管理单元，该第二管理单元可以实现上述方法实例中第二管理单元所执行的功能，所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。
在一种可能的实现方式中，该第二管理单元的结构中包括处理器和通信接口，该处理器被配置为支持该第二管理单元执行上述方法中相应的功能。该通信接口用于支持该第二管理单元与第一管理单元或其他网元之间的通信。该第二管理单元还可以包括存储器，该存储器用于与处理器耦合，其保存该第二管理单元必要的程序指令和数据。
又一方面，本发明实施例提供了一种计算机存储介质，用于储存为上述第一管理单元所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
又一方面，本发明实施例提供了一种计算机存储介质，用于储存为上述第二管理单元所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
又一方面，本发明实施例提供一种计算机程序产品，其包含指令，当所述程序被计算机所执行时，该指令使得计算机执行上述方法设计中第一管理单元所执行的功能。
又一方面，本发明实施例提供一种计算机程序产品，其包含指令，当所述程序被计算机所执行时，该指令使得计算机执行上述方法设计中第二管理单元所执行的功能。
又一方面，本发明实施例提供了一种通信系统，该系统包括上述方面所述的第一管理单元和第二管理单元。
在本发明实施例中，通过第一管理单元向第二管理单元发送针对网络切片实例或网络功能实例的管理请求，该管理请求包括至少一组配置参数和用于指示至少一组配置参数是否立即激活的指示信息，第二管理单元接收该管理请求，并根据该管理请求对网络切片实例或网络功能实例进行管理，从而能够根据网络情况实时进行管理，以提高对网络切片实例或网络功能实例进行管理的灵活性。
附图说明
图1为本发明实施例提供的一种可能的网络架构的示意图；
图2为本发明实施例提供的一种管理方法的通信示意图；
图3为本发明实施例提供的另一种管理方法的通信示意图；
图4为本发明实施例提供的又一种管理方法的通信示意图；
图5为本发明实施例提供的再一种管理方法的通信示意图；
图6A为本发明实施例提供的一种第一管理单元的结构示意图；
图6B为本发明实施例提供的另一种第一管理单元的结构示意图；
图7A为本发明实施例提供的一种第二管理单元的结构示意图；
图7B为本发明实施例提供的另一种第二管理单元的结构示意图。
具体实施方式
说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四”等(如果存在)是用于区别类似的部分，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本申请的实施例能够以除了在这里图示的以外的顺序实施。
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行描述。
本发明实施例描述的网络架构以及业务场景是为了更加清楚的说明本发明实施例的技术方案，并不构成对本发明实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本发明实施例提供的技术方案对于类似的技术问题，同样适用。
下面首先结合图1对本发明实施例可能使用的网络架构进行介绍。
请参见图1，图1为本发明实施例提供的一种可能的网络架构的示意图。图1为5G虚拟网络架构中的一种可能的实现方式，随着通信技术的发展，图1所示的网络结构图可能会有所变化，因此图1所示的网络架构图并不构成对本发明实施例的限定。图1所示的网络架构包括：网络切片编排和管理(Network Slice Orchestration and Management，NSOAM)单元、通用网络功能(Common Network Function，Common NF)单元和网络切片单元。其中，Common NF单元可以由网络功能控制(Network Function Controller，NF Controller)单元替代；或者，Common NF单元除具有自身的功能外，还可以具有NF Controller单元的功能。图1中的“通用网络功能/网络功能控制单元”表示具有Common NF单元的功能和/或NF Controller单元的功能的单元。下面对图1中涉及到的各个单元做简单介绍。
NSOAM单元可用于实现网络切片的创建、管理和撤销。运营商首先根据业务场景需求生成网络切片模板，切片模板包括该业务场景所需的网络功能模块、各网络功能模块之间的接口以及这些功能模块所需的网络资源；然后NSOAM单元根据该切片模版申请网络资源，并在申请到的资源上实例化创建虚拟网络功能模块的接口。NSOAM单元能够对形成的网络切片进行监督管理，允许根据实际业务量，对网络资源的分配进行扩容、缩容和动态调整，并在生命周期到期后撤销网络切片。NSOAM单元可以通过大数据驱动的网络优化来促使网络切片划分和网络资源分配更为合理，并实现自动化运维，及时响应网络和业务的变化，保证用户体验和提高网络资源利用率。
Common NF/NF controller单元可用于控制NS实例或NF实例的配置和激活。其中，激活的前提条件是NS实例或NF实例已配置相应的配置参数。
网络切片单元可以包括至少一个网络切片实例，每个网络切片实例包括至少一个网络功能实例。
需要说明的是，上述Common NF/NF controller单元可以设置为单独的网络实体，也可以设置为网络切片单元中的一个功能模块，视具体情况而定。
下面将基于上面所述的本发明实施例涉及的共性方面，对本发明实施例进一步详细说明。
目前，对NS实例进行参数管理的过程为：NSOAM单元实例化一个NS实例，实例化后的NS实例位于网络切片单元；NSOAM单元直接向网络切片单元中的该NS实例下发初始配置参数或更新配置参数，该NS实例根据下发的一组初始配置参数或一组更新配置参数配置并激活该NS实例或该NS实例对应的网络功能实例(例如包括VNF实例和/或PNF实例)，从而使得该NS实例或该NS实例对应的网络功能实例实现对应的实体功能。由此可见，该NS实例或该NS实例对应的网络功能实例被动地根据NSOAM单元下发的一组配置参数进行配置、激活，无法根据网络情况实时进行配置、激活。这种对NS实例或网络功能实例进行管理的方式灵活性较低，降低了网络运行的效率。
有鉴于此，本发明实施例提供一种管理方法，和基于这个方法的第二管理单元、第一管理单元和系统，以提高对网络切片实例或网络功能实例进行管理的灵活性，从而提高网络运行的效率。在该方法中，第一管理单元向第二管理单元发送针对网络切片实例或网络功能实例的管理请求，管理请求携带至少一组配置参数和指示信息，指示信息用于指示该至少一组配置参数是否立即激活；第二管理单元从第一管理单元接收管理请求后，根据该管理请求对网络切片实例或网络功能实例进行管理。可选的，本发明实施例中的网络切片实例可以为在图1所示的网络切片单元中选定的任意网络切片实例，本发明实施例中的网络功能实例可以为选定的网络切片实例对应的网络功能实例，也可以为在图1所示的网络切片单元中选定的任意网络功能实例，其中，网络功能实例可以为VNF实例或PNF实例，其具体类型以及具体数量视情况而定，在此不做限定。本发明实施例中，第一管理单元向第二管理单元发送的管理请求中，除携带至少一组配置参数外，还携带用于指示该至少一组配置参数是否立即激活 的指示信息，使得第二管理单元可以根据该管理请求对网络切片实例或网络功能实例进行管理，以提高对网络切片实例或网络功能实例进行管理的灵活性。
其中，上述管理请求可以为初始实例管理请求，初始实例管理请求用于指示第二管理单元对初始实例化的网络切片实例或网络功能实例进行管理；或者，上述管理请求可以为更新实例管理请求，更新实例管理请求用于指示第二管理单元对已激活的网络切片实例或网络功能实例进行更新管理。
需要说明的是，本发明实施例的方案可以应用于图1所示的网络架构中，上述第一管理单元为发送管理请求的一端，例如可以为图1所示的NSOAM单元，还可以为运营支撑系统(Operation Support System，OSS)/业务支撑系统(Business Support System，BSS)，OSS/BSS是电信运营商的一体化、信息资源共享的支持系统，其主要由网络管理、系统管理、计费、营业、账务和客户业务等部分组成，而系统间则通过统一的信息总线有机整合在一起。上述第二管理单元为接收管理请求的一端，可以为配置单元和/或功能单元，例如可以为图1所示的Common NF/NF controller单元或网络切片单元，还可以为网元管理系统(Entity Management System，EMS)或网络功能管理(NF Manager)单元。其中，EMS是管理特定类型的一个或多个电信网络单元(Network Element，NE)的系统。一般来说，EMS管理着每个NE的功能和容量，但并不理会网络中不同NE之间的交流。网络功能管理单元主要负责配置管理、性能管理、故障管理、安全管理和计费管理。
下面结合附图2～图4对本发明实施例提供的方案进行详细说明。
图2示出了本发明实施例提供的一种管理方法。图2所示的方法可以应用于图1所示的网络架构，其中，第一管理单元可以为NSOAM单元，第二管理单元可以为Common NF/NF controller单元或网络切片单元。
在201部分，第一管理单元向第二管理单元发送针对网络切片实例或网络功能实例的管理请求，该管理请求携带至少一组配置参数和指示信息，指示信息用于指示该至少一组配置参数是否立即激活。
在一个示例中，第一管理单元向第二管理单元发送上述管理请求之前，第一管理单元可以实例化一个网络切片实例。例如，第一管理单元可根据OSS/BSS发送的实例化请求实例化网络切片实例，或第一管理单元可根据管理员输入的需求信息实例化网络切片实例。其中，实例化网络切片实例的过程 可以包括：第一管理单元实例化网络切片实例对应的网络功能实例，从而实例化网络切片实例；第一管理单元建立网络切片实例对应的不同网络功能实例之间的连接，并建立网络切片实例与其它网络切片实例之间的连接；第一管理单元为网络切片实例或网络切片实例对应的网络功能实例分配各自所需的网络资源。在实例化过程完成后，上述网络切片实例或上述网络切片实例对应的网络功能实例并不是可以运行的功能实体，需要配置并激活相应的配置参数之后才能变成可以运行的功能实体，以实现对应的应用实例功能，例如服务网关功能等。实例化的网络切片实例或网络切片实例对应的网络功能实例可由第二管理单元进行管理。
在另一个示例中，第一管理单元向第二管理单元发送上述管理请求之前，第一管理单元可以实例化网络功能实例。例如，第一管理单元可根据OSS/BSS发送的实例化请求实例化网络功能实例，或第一管理单元可根据管理员输入的需求信息实例化网络功能实例。其中，实例化网络功能实例的过程与上述实例化网络切片实例的过程类似，可以参照上述实例化网络切片实例的过程进行实施，此处不作赘述。实例化网络功能实例的过程完成后，上述网络功能实例需要配置并激活相应的配置参数之后才能变成可以运行的网络功能实体。实例化的网络功能实例可由第二管理单元进行管理。其中，实例化的网络功能实例的数量在此不做限定。
第一管理单元在实例化网络切片实例或网络功能实例之后，可以通过第一管理单元与第二管理单元之间的通信接口向第二管理单元发送针对网络切片实例或网络功能实例的管理请求。其中，上述网络功能实例可以是上述网络切片实例对应的网络功能实例，也可以是与上述网络切片实例无关的网络功能实例。
在一个示例中，第二管理单元根据管理请求对网络切片实例或网络功能实例进行管理之前，还可以根据至少一组配置参数配置网络切片实例或网络功能实例。可选的，本发明实施例中，上述指示信息具体可以用于指示第二管理单元在配置至少一组配置参数后是否立即激活该至少一组配置参数。示例性的，指示信息可以用某个字段来指示，例如，某个字段为“0”，表示立即激活；反之，该字段为“1”，表示不立即激活。
在一个示例中，上述指示信息可以为至少一组配置参数中每组配置参数对 应的指示信息，用于指示对应组的配置参数是否立即激活。例如，若某组配置参数对应的指示信息指示立即激活，则第二管理单元可以在配置该组配置参数后立即激活该组配置参数，从而激活网络切片实例或网络功能实例。或者，上述指示信息可以为至少一组配置参数中所有组配置参数对应的指示信息，用于指示所有组配置参数是否立即激活。
其中，上述至少一组配置参数中每组配置参数所包括的参数可以完全相同，也可以部分相同，还可以完全不相同。每组配置参数可以包括容量参数、服务质量(Quality of Service，QoS)参数、规格参数等参数中的至少一种。每组配置参数还可以包括其他参数，例如，当网络功能实体是移动性管理实体时，配置参数可以是切换参数，如小区特定偏置(Cell Individual Offset，CIO)。
在一个示例中，管理请求还可以携带至少一组配置参数中每组配置参数的激活触发条件。其中，该激活触发条件可以包括用户分布门限和/或负载均衡门限。对于不同组配置参数，其用户分布门限、负载均衡门限可能会有所不同，具体数值在此不做限定。其中，上述用户分布门限用于描述当前网络中用户分布情况，上述负载均衡门限用于描述当前网络中用户接入量。通过激活触发条件可以反映当前网络的实际情况，以使得第二管理单元能够根据网络实际需求激活相应组的配置参数，从而激活网络切片实例或网络功能实例。
在一个示例中，管理请求还可以携带至少一组配置参数中每组配置参数的组标识(identifier)，用于区分不同组的配置参数，以使得第二管理单元能够对不同组的配置参数针对性地配置、激活。
其中，上述管理请求可以为初始实例管理请求，也可以为更新实例管理请求。例如，若管理请求为初始实例管理请求，则至少一组配置参数为至少一组初始配置参数，即网络切片实例或网络功能实例初始配置所需的至少一组配置参数。又例如，若管理请求为更新实例管理请求，则至少一组配置参数为至少一组更新后的配置参数，即更新网络切片实例或网络功能实例所需的至少一组配置参数。
上述网络切片实例可能是由多个功能实体组成的，在这种情况下，第一管理单元可以向多个功能实体分别发送配置参数。
在202部分，第二管理单元根据管理请求对网络切片实例或网络功能实例进行管理。
在一个示例中，第二管理单元根据上述至少一组配置参数配置网络切片实例或网络功能实例。此时第二管理单元为网络切片实例或网络功能实例配置上述至少一组配置参数，是对网络切片实例或网络功能实例进行激活的前提条件。可以理解的是，此时第二管理单元只进行配置，不进行激活，激活可能由其它单元执行。
在一个示例中，第二管理单元根据上述管理请求激活网络切片实例或网络功能实例，此时可认为上述至少一组配置参数已配置，可能不是由第二管理单元配置。
在一个示例中，第二管理单元根据上述管理请求配置并激活网络切片实例或网络功能实例，此时配置和激活均由第二管理单元执行。
在一个示例中，上述指示信息指示上述至少一组配置参数立即激活，第二管理单元可以根据该指示信息，激活对应组的配置参数，从而激活网络切片实例或网络功能实例。网络切片实例或网络功能实例可以具有某种或某几种功能和性能，激活后的网络切片实例或网络功能实例可以得以使用。或者，上述指示信息指示上述至少一组配置参数不立即激活，第二管理单元可以根据网络实际情况来确定何时激活该至少一组配置参数。
在一种可能的实施方式中，上述至少一组配置参数可以包括目标组配置参数，目标组配置参数的激活触发条件为目标激活触发条件，第二管理单元可以获取网络参数；当网络参数满足目标激活触发条件时，第二管理单元可以根据目标组配置参数激活网络切片实例或网络功能实例。例如，第二管理单元可以获取网络参数，该网络参数可以包括用户分布参数和/或负载均衡参数；若网络参数满足目标激活触发条件，则第二管理单元激活目标组配置参数，从而激活网络切片实例或网络功能实例，使得网络切片实例或网络功能实例具有目标组配置参数对应的功能和性能。示例性的，第二管理单元可以在网络架构中实时获取网络参数，并实时检测获取到的网络参数是否满足某组配置参数对应的激活触发条件，并在满足时，激活该组配置参数。
进一步地，第二管理单元在激活目标组配置参数之后，还可向第一管理单元反馈目标组配置参数的组标识，用于通知第一管理单元目标组配置参数已激活，以及网络切片实例或网络功能实例已具有目标组配置参数对应的功能和性能。
在本发明实施例中，第一管理单元向第二管理单元发送针对网络切片实例或网络功能实例的管理请求，该管理请求携带至少一组配置参数和用于指示至少一组配置参数是否立即激活的指示信息；第二管理单元接收该管理请求后，根据该管理请求对网络切片实例或网络功能实例进行管理，从而能够根据网络情况实时进行管理，以提高对网络切片实例或网络功能实例进行管理的灵活性。
下面结合图3～图5对本发明实施例进行进一步说明。图3～图5所示方法中，与图2所示方法相同或类似的内容，可以参考图2中的详细描述，后续不再赘述。
图3示出了本发明实施例提供的另一种管理方法的通信示意图。图3所示的方法可以应用于图1所示的网络架构，需要说明的是，图3中，以上述第一管理单元为NSOAM单元，以上述第二管理单元为Common NF/NF controller单元或网络切片单元为例对本发明实施例的方案进行介绍，并且Common NF/NF controller单元与网络切片单元相互独立。
在301部分，NSOAM单元向网络切片单元发送针对网络切片实例的管理请求，该管理请求包括至少一组配置参数和指示信息，指示信息用于指示该至少一组配置参数是否立即激活。
在一个示例中，NSOAM单元在实例化网络切片实例或网络功能实例之后，通过NSOAM单元与网络切片单元之间的通信接口向网络切片单元发送针对网络切片实例或网络功能实例的管理请求。其中，上述网络功能实例可以是上述网络切片实例对应的网络功能实例，也可以是与上述网络切片实例无关的网络功能实例。
其中，上述至少一组配置参数以及上述指示信息的描述可参见图2所示实施例中对这两者的具体描述，在此不再赘述。
在302部分，网络切片单元根据至少一组配置参数配置网络切片实例。
在一个示例中，网络切片单元根据上述至少一组配置参数配置网络切片实例，便于后续激活配置参数。
若上述至少一组配置参数中存在指示立即激活的指示信息，则网络切片单元根据该指示信息激活相应组的配置参数。
在303部分，网络切片单元向NSOAM单元发送第一响应消息。
具体的，网络切片单元在根据上述至少一组配置参数配置上述网络切片实例之后，可通过网络切片单元与NSOAM单元之间的通信接口向NSOAM单元发送第一响应消息，用于告知NSOAM单元，网络切片实例配置了上述至少一组配置参数，若网络切片单元激活了某个组的配置参数，则第一响应消息还携带激活的配置参数的组标识。需要说明的是，303部分为可选的部分。
在304部分，NSOAM单元向Common NF/NF controller单元发送配置参数表，该配置参数表包括激活触发条件。
具体的，NSOAM单元可以通过NSOAM单元与Common NF/NF controller单元之间的通信接口向Common NF/NF controller单元发送配置参数表。其中，配置参数表包括上述网络切片实例的标识，上述至少一组配置参数中每组配置参数的组标识，以及每组配置参数的激活触发条件。
在一个示例中，每组配置参数的组标识还可以包括是否已激活的标识，以便Common NF/NF controller单元获知激活情况。
在305部分，Common NF/NF controller单元配置网络切片实例。
在一个示例中，Common NF/NF controller单元根据上述至少一组配置参数配置上述网络切片实例。
在306部分，Common NF/NF controller单元获取网络参数。
在307部分，Common NF/NF controller单元检测网络参数是否满足目标激活触发条件。
其中，上述至少一组配置参数包括目标组配置参数，目标组配置参数的激活触发条件为目标激活触发条件。上述目标组配置参数可以是未激活的任意一组配置参数。网络参数以及激活触发条件的描述可参见图2所示实施例中对这两者的具体描述，在此不再赘述。
在308部分，若满足，则Common NF/NF controller单元向网络切片单元发送激活指示信息。
当上述网络参数满足上述目标激活触发条件时，Common NF/NF controller单元通过Common NF/NF controller单元与网络切片单元之间的通信接口向网络切片单元发送激活指示信息。其中，激活指示信息包括上述目标组配置参数的组标识，以便网络切片单元激活该组配置参数。
这里，当上述网络参数满足上述目标激活触发条件时，Common NF/NF  controller单元还可以先向NSOAM单元发送查询消息，通知NSOAM单元某个网络切片单元满足了特定条件，Common NF/NF controller单元在接收到NSOAM单元的确认消息后，再向网络切片单元发送上述激活指示信息。
在309部分，网络切片单元根据激活指示信息激活相应组的配置参数。
在310部分，网络切片单元向Common NF/NF controller单元发送第二响应消息。
网络切片单元通过网络切片单元与Common NF/NF controller单元之间的通信接口向Common NF/NF controller单元发送第二响应消息。其中，第二响应消息用于告知Common NF/NF controller单元，上述网络切片实例激活了哪组配置参数，上述第二响应消息可携带激活的配置参数的组标识。需要说明的是，310部分为可选的部分。
在311部分，网络切片单元向NSOAM单元发送激活通知消息。
网络切片单元通过网络切片单元与NSOAM单元之间的通信接口向NSOAM单元发送激活通知消息。其中，激活通知消息用于告知NSOAM单元，网络切片实例激活了哪些组的配置参数，激活通知消息可携带激活的配置参数的组标识，包括根据指示信息激活的配置参数的组标识和根据网络参数激活的配置参数的组标识。需要说明的是，311部分为可选的部分。
在本发明实施例中，由Common NF/NF controller单元根据网络参数确定何时激活配置参数，并由Common NF/NF controller单元控制网络切片单元进行激活，实现根据网络情况实时进行激活，进而提高对网络切片实例进行管理的灵活性。
图4示出了本发明实施例提供的又一种管理方法的通信示意图。图4所示的方法可以应用于图1所示的网络架构，需要说明的是，图4中，以上述第一管理单元为NSOAM单元，以上述第二管理单元为网络切片单元为例进行介绍。其中，图4所示实施例与图2或图3所示实施例相同的地方，在此不再赘述。
在401部分，NSOAM单元向网络切片单元发送针对网络切片实例的管理请求，该管理请求包括至少一组配置参数、指示信息和激活触发条件，指示信息用于指示该至少一组配置参数是否立即激活。
与图3所示实施例不同之处在于，该管理请求包括至少一组配置参数中每 组配置参数的激活触发条件，激活触发条件的描述可参见图2所示实施例对其的具体描述，在此不再赘述。
在402部分，网络切片单元根据至少一组配置参数配置网络切片实例。
在403部分，网络切片单元向NSOAM单元发送第一响应消息。
需要说明的是，403部分为可选的部分。
在404部分，网络切片单元获取网络参数。
在405部分，网络切片单元检测网络参数是否满足目标激活触发条件。
上述至少一组配置参数包括目标组配置参数，目标组配置参数的激活触发条件为目标激活触发条件。上述目标组配置参数可以是未激活的任意一组配置参数。
在406部分，若满足，则网络切片单元激活目标组配置参数。
当上述网络参数满足上述目标激活触发条件时，网络切片单元激活目标组配置参数，以激活网络切片实例。
在407部分，网络切片单元向NSOAM单元发送第二响应消息。
其中，第二响应消息用于告知NSOAM单元，网络切片实例激活了哪些组的配置参数，该第二响应消息可携带激活的配置参数的组标识，包括根据指示信息激活的配置参数的组标识和根据网络参数激活的配置参数的组标识。需要说明的是，407部分为可选的部分。
在本发明实施例中，由网络切片单元根据网络参数确定何时激活配置参数并进行激活，实现根据网络情况实时进行激活，进而提高对网络切片实例进行管理的灵活性。
图5示出了本发明实施例提供的再一种管理方法的通信示意图。图5所示的方法可以应用于图1所示的网络架构，需要说明的是，图5中，以上述第一管理单元为NSOAM单元，以上述第二管理单元为Common NF/NF controller单元为例进行介绍，此时Common NF/NF controller单元可以是网络功能或配置单元，网络切片单元为网元。其中，图5所示实施例与图2、图3或图4所示实施例相同的地方，在此不再赘述。
在501部分，NSOAM单元向Common NF/NF controller单元发送管理请求，该管理请求包括至少一组配置参数、指示信息和激活触发条件，指示信息用于指示所述至少一组配置参数是否立即激活。
其中，管理请求可以是图3或图4所示实施例中的管理请求(配置请求)，也可以是管理对象创建请求或管理对象配置请求。
在502部分，Common NF/NF controller单元根据至少一组配置参数进行配置。
在一个示例中，Common NF/NF controller单元保存上述至少一组配置参数和/或根据上述至少一组配置参数进行配置。Common NF/NF controller单元可以是对相应的管理对象配置参数，也可以是直接对相应的网络切片实例或网络功能实体配置参数。
在503部分，Common NF/NF controller单元获取网络参数。
在504部分，Common NF/NF controller单元检测所述网络参数是否满足目标激活触发条件。
其中，上述至少一组配置参数包括目标组配置参数，目标组配置参数的激活触发条件为目标激活触发条件。上述目标组配置参数可以是未激活的任意一组配置参数。
在505部分，若满足，则Common NF/NF controller单元向网络切片单元发送激活指示信息。
在506部分，网络切片单元根据激活指示信息激活相应组的配置参数。
在507部分，网络切片单元向Common NF/NF controller单元发送响应消息。
其中，响应消息用于告知Common NF/NF controller单元，网络切片单元激活了哪组的配置参数，该响应消息可携带激活的配置参数的组标识。需要说明的是，507部分为可选的部分。
在508部分，网络切片单元向NSOAM单元发送激活通知消息。
其中，激活通知消息用于告知NSOAM单元，网络切片单元激活了哪些组的配置参数，该激活通知消息可携带激活的配置参数的组标识。需要说明的是，508部分为可选的部分。
在本发明实施例中，由Common NF/NF controller单元进行配置，并根据网络参数确定何时激活配置参数，并由Common NF/NF controller单元控制网络切片单元进行激活，实现根据网络情况实时进行激活，进而提高对网络切片实例进行管理的灵活性。与图3所示实施例不同之处在于，图3所示实施例由 网络切片单元进行配置，图5所示实施例由Common NF/NF controller单元进行配置。
需要说明的是，图3、图4或图5所示的实施例中的管理请求为初始实例管理请求，对于更新实例管理请求的实施例与图3、图4或图5所示实施例类似，在此不再赘述。并且，图3、图4或图5所示的实施例对网络切片实例的管理进行介绍，对网络功能实例的管理类似，在此不再赘述。
上述主要从各个网元之间交互的角度对本发明实施例的方案进行了介绍。可以理解的是，各个网元，例如第一管理单元，第二管理单元等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
本发明实施例可以根据上述方法示例对第一管理单元，第二管理单元等进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本发明实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用集成的模块的情况下，图6A示出了上述实施例中所涉及的第一管理单元的一种可能的结构示意图。第一管理单元600包括：处理模块602和通信模块603。处理模块602用于对第一管理单元的动作进行控制管理，例如，处理模块602用于支持第一管理单元执行图2中的过程201，图3中的过程301和304，图4中的过程401，图5中的过程501，和/或用于本文所描述的技术的其它过程。通信模块603用于支持第一管理单元与第二管理单元或其他网络实体的通信，例如与图1中示出的Common NF/NF controller单元或网络切片单元之间的通信。第一管理单元还可以包括存储模块601，用于存储第一管理单元的程序代码和数据。
其中，处理模块602可以是处理器或控制器，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)， 现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块603可以是通信接口、收发器或收发电路等，其中通信接口是统称，可以包括一个或多个接口。存储模块601可以是存储器。
当处理模块602为处理器，通信模块603为通信接口，存储模块601为存储器时，本发明实施例所涉及的第一管理单元可以为图6B所示的第一管理单元。
参阅图6B所示，该第一管理单元610包括：处理器612、通信接口613、存储器611。可选的，第一管理单元610还可以包括总线614。其中，通信接口613、处理器612以及存储器611可以通过总线614相互连接；总线614可以是外设部件互连标准(Peripheral Component Interconnect，简称PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，简称EISA)总线等。所述总线614可以分为地址总线、数据总线、控制总线等。为便于表示，图6B中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在采用集成的模块的情况下，图7A示出了上述实施例中所涉及的第二管理单元的一种可能的结构示意图。第二管理单元700包括：处理模块702和通信模块703。处理模块702用于对第二管理单元的动作进行控制管理，例如，处理模块702用于支持第二管理单元执行图2中的过程202，图3中的过程302、303和305～311，图4中的过程402～407，图5中的过程502～508，和/或用于本文所描述的技术的其它过程。通信模块703用于支持第二管理单元与第一管理单元或其他网络实体的通信，例如与图1中示出的NSOAM单元之间的通信。第二管理单元还可以包括存储模块701，用于存储第二管理单元的程序代码和数据。
其中，处理模块702可以是处理器或控制器，例如可以是中央处理器，通用处理器，数字信号处理器，专用集成电路，现场可编程门阵列或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块703可以是通信接口、收发器或收发电路等，其中通信接口是统称，可以包括一个或多个接口。存储模块701可以是存储器。
当处理模块702为处理器，通信模块703为通信接口，存储模块701为存储器时，本发明实施例所涉及的第二管理单元可以为图7B所示的第二管理单元。
参阅图7B所示，该第二管理单元710包括：处理器712、通信接口713、存储器711。可选的，第二管理单元710还可以包括总线714。其中，通信接口713、处理器712以及存储器711可以通过总线714相互连接；总线714可以是外设部件互连标准总线或扩展工业标准结构总线等。所述总线714可以分为地址总线、数据总线、控制总线等。为便于表示，图7B中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
结合本发明实施例公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read Only Memory，ROM)、可擦除可编程只读存储器(Erasable Programmable ROM，EPROM)、电可擦可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD～ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于第一管理单元或第二管理单元中。当然，处理器和存储介质也可以作为分立组件存在于第一管理单元或第二管理单元中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明实施例所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本发明实施例的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明实施例的具体实施方式而已，并不用于限定本发明实施例的保护范围，凡在本发明实施例的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明实施例的保护范围之内。

Claims (15)

  1. 一种管理方法，其特征在于，包括：
    第二管理单元从第一管理单元接收针对网络切片实例或网络功能实例的管理请求，所述管理请求携带至少一组配置参数和指示信息，所述指示信息用于指示所述至少一组配置参数是否立即激活；
    所述第二管理单元根据所述管理请求对所述网络切片实例或所述网络功能实例进行管理。
  2. 根据权利权要1所述的方法，其特征在于，所述第二管理单元根据所述管理请求对所述网络切片实例或所述网络功能实例进行管理，包括：
    所述第二管理单元根据所述至少一组配置参数配置所述网络切片实例或所述网络功能实例；或者，
    所述第二管理单元根据所述管理请求激活所述网络切片实例或所述网络功能实例；或者，
    所述第二管理单元根据所述管理请求配置并激活所述网络切片实例或所述网络功能实例。
  3. 根据权利权要1或2所述的方法，其特征在于，所述管理请求还携带所述至少一组配置参数中每组配置参数的激活触发条件。
  4. 根据权利权要3所述的方法，其特征在于，所述激活触发条件包括用户分布门限和/或负载均衡门限。
  5. 根据权利要求3或4所述的方法，其特征在于，所述至少一组配置参数包括目标组配置参数，所述目标组配置参数的激活触发条件为目标激活触发条件；所述第二管理单元根据所述管理请求激活所述网络切片实例或所述网络功能实例，包括：
    所述第二管理单元获取网络参数；
    当所述网络参数满足所述目标激活触发条件时，所述第二管理单元根据所述目标组配置参数激活所述网络切片实例或所述网络功能实例。
  6. 根据权利权要1-5任一项所述的方法，其特征在于，所述管理请求还携带所述至少一组配置参数中每组配置参数的组标识。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，所述管理请求为 初始实例管理请求，所述至少一组配置参数为至少一组初始配置参数；或者，所述管理请求为更新实例管理请求，所述至少一组配置参数为至少一组更新后的配置参数。
  8. 一种第二管理单元，其特征在于，包括处理模块和通信模块，
    所述处理模块用于通过所述通信模块从第一管理单元接收针对网络切片实例或网络功能实例的管理请求，所述管理请求携带至少一组配置参数和指示信息，所述指示信息用于指示所述至少一组配置参数是否立即激活；以及用于根据所述管理请求对所述网络切片实例或所述网络功能实例进行管理。
  9. 根据权利权要8所述的第二管理单元，其特征在于，所述处理模块具体用于根据所述至少一组配置参数配置所述网络切片实例或所述网络功能实例；或者，所述处理模块具体用于根据所述管理请求激活所述网络切片实例或所述网络功能实例；或者，所述处理模块具体用于根据所述管理请求配置并激活所述网络切片实例或所述网络功能实例。
  10. 根据权利权要8或9所述的第二管理单元，其特征在于，所述管理请求还携带所述至少一组配置参数中每组配置参数的激活触发条件。
  11. 根据权利权要10所述的第二管理单元，其特征在于，所述激活触发条件包括用户分布门限和/或负载均衡门限。
  12. 根据权利要求10或11所述的第二管理单元，其特征在于，所述至少一组配置参数包括目标组配置参数，所述目标组配置参数的激活触发条件为目标激活触发条件；所述处理模块具体用于：获取网络参数；以及当所述网络参数满足所述目标激活触发条件时，根据所述目标组配置参数激活所述网络切片实例或所述网络功能实例。
  13. 根据权利权要8-12任一项所述的第二管理单元，其特征在于，所述管理请求还携带所述至少一组配置参数中每组配置参数的组标识。
  14. 根据权利要求8-13任一项所述的第二管理单元，其特征在于，所述管理请求为初始实例管理请求，所述至少一组配置参数为至少一组初始配置参数；或者，所述管理请求为更新实例管理请求，所述至少一组配置参数为至少一组更新后的配置参数。
  15. 一种通信系统，其特征在于，包括如权利要求8-14任一项所述的第 二管理单元和第一管理单元，其中，所述第一管理单元用于向所述第二管理单元发送针对网络切片实例或网络功能实例的管理请求。
PCT/CN2016/107690 2016-11-29 2016-11-29 一种管理方法、管理单元及系统 WO2018098624A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/107690 WO2018098624A1 (zh) 2016-11-29 2016-11-29 一种管理方法、管理单元及系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/107690 WO2018098624A1 (zh) 2016-11-29 2016-11-29 一种管理方法、管理单元及系统

Publications (1)

Publication Number Publication Date
WO2018098624A1 true WO2018098624A1 (zh) 2018-06-07

Family

ID=62241045

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/107690 WO2018098624A1 (zh) 2016-11-29 2016-11-29 一种管理方法、管理单元及系统

Country Status (1)

Country Link
WO (1) WO2018098624A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105376083A (zh) * 2014-08-25 2016-03-02 华为技术有限公司 节能控制方法、管理服务器和网络设备
CN105429780A (zh) * 2015-10-30 2016-03-23 南京优速网络科技有限公司 一种虚拟化网络服务业务自动生成和动态监控的方法
WO2016048430A1 (en) * 2014-09-25 2016-03-31 Intel IP Corporation Network functions virtualization

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105376083A (zh) * 2014-08-25 2016-03-02 华为技术有限公司 节能控制方法、管理服务器和网络设备
WO2016048430A1 (en) * 2014-09-25 2016-03-31 Intel IP Corporation Network functions virtualization
CN105429780A (zh) * 2015-10-30 2016-03-23 南京优速网络科技有限公司 一种虚拟化网络服务业务自动生成和动态监控的方法

Similar Documents

Publication Publication Date Title
US11456930B2 (en) Network resource management method, apparatus, and system
US10999740B2 (en) Network slice management method, management unit, and system
US20190230004A1 (en) Network slice management method and management unit
EP3800926B1 (en) Alarm method and device
US10924966B2 (en) Management method, management unit, and system
KR101245213B1 (ko) 개방 가상화 형식 메타데이터 기반 네트워크 구성 및/또는 프로비저닝을 위한 방법 및 시스템
WO2021093782A1 (zh) 执行意图的方法及装置
US10848366B2 (en) Network function management method, management unit, and system
US20200280493A1 (en) Network Service Management Method, Device, and System
TWI722145B (zh) 網路功能虛擬化
US11088924B2 (en) Network management method, device, and system
US20190199582A1 (en) Alarm information reporting method and apparatus
CN109565447A (zh) 网络功能处理方法及相关设备
CN109417501A (zh) 网络资源的编排方法和设备
WO2018153355A1 (zh) 控制信息传递方法、服务器和系统
EP3402121A1 (en) Method and device for policy transmission in nfv system
WO2018098624A1 (zh) 一种管理方法、管理单元及系统
WO2020220937A1 (zh) 一种安全策略管理方法及装置
KR20170057770A (ko) 가상 스위치의 패킷 전송 제어 방법
WO2018014351A1 (zh) 一种资源配置方法及装置
WO2022126389A1 (zh) 建立网络连接的方法及装置
WO2023035777A1 (zh) 网络配置方法、代理组件、控制器、电子设备和存储介质
CN116185552A (zh) 一种内存带宽服务质量的控制方法、装置及系统

Legal Events

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

Ref document number: 16922884

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16922884

Country of ref document: EP

Kind code of ref document: A1