WO2018090191A1 - 网络功能的管理方法、管理单元及系统 - Google Patents

网络功能的管理方法、管理单元及系统 Download PDF

Info

Publication number
WO2018090191A1
WO2018090191A1 PCT/CN2016/105923 CN2016105923W WO2018090191A1 WO 2018090191 A1 WO2018090191 A1 WO 2018090191A1 CN 2016105923 W CN2016105923 W CN 2016105923W WO 2018090191 A1 WO2018090191 A1 WO 2018090191A1
Authority
WO
WIPO (PCT)
Prior art keywords
network function
management unit
network
information
shared
Prior art date
Application number
PCT/CN2016/105923
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/105923 priority Critical patent/WO2018090191A1/zh
Priority to EP16921764.3A priority patent/EP3531749B1/en
Priority to CN201680090741.0A priority patent/CN109964507B/zh
Publication of WO2018090191A1 publication Critical patent/WO2018090191A1/zh
Priority to US16/411,623 priority patent/US10848366B2/en

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/02—Standardisation; Integration
    • H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • 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/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • 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/04—Network management architectures or arrangements
    • H04L41/046—Network management architectures or arrangements comprising network management agents or mobile agents therefor
    • 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/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • 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/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • 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/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H04L41/0897—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or 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/32—Specific management aspects for broadband networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices
    • 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/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices

Definitions

  • the embodiments of the present invention relate to the field of communications, and in particular, to a network function management method, a management unit, and a system.
  • Network slicing can be understood as an on-demand network.
  • a physical network can be logically divided into multiple network slices, and different network slices can be used to carry different services.
  • power companies need to provide smart metering services that can be implemented by connecting a series of network slices of Machine-to-Machine (M2M) devices.
  • M2M Machine-to-Machine
  • a network slice can consist of at least one network function. In practice, if a network function only supports one network slice, the number of network functions will be too much, which is not easy to maintain and manage.
  • the embodiments of the present invention provide a management method, a management unit, and a system for a network function, which are used to solve the problem that the existing network function is inconvenient to manage.
  • an embodiment of the present invention provides a method for managing a network function.
  • the method includes: the second management unit acquires sharing information of the network function, where the sharing information of the network function is used to indicate whether the network function can be shared by the at least two network slices; and the second management unit sends the sharing information of the network function to the first management unit.
  • the first management unit orchestrate the network function according to the shared information of the network function.
  • the first management unit receives the sharing information of the network function from the second management unit, where the sharing information of the network function is used to indicate whether the network function can be shared by at least two network slices, and the first management unit is configured according to the network function.
  • the shared information, the network function is arranged, which gives a specific solution to choose to provide shared network functions or exclusive network functions to the network slice, which is convenient for maintenance and management of network functions.
  • the first management unit may send a query request message to the second management unit, where the query request message is used to request the shared information of the network function; then, the first management unit receives the query response message from the second management unit, The query response message carries the shared information of the network function.
  • the solution of the embodiment of the present invention provides a specific manner for the first management unit to query the second management unit for the shared information of the network function, so that the first management unit can acquire the shared information of the network function at any time as needed.
  • the query request message may carry an identifier of the network function, an identifier of the network function descriptor, or a requirement information of the network function
  • the second management unit may identify the identifier of the network function, the identifier of the network function descriptor, or
  • the demand information of the network function acquires the shared information of the network function.
  • the first management unit may send a network function instantiation request message to the second management unit; then the first management unit receives the network function instantiation response message from the second management unit, and the network function instantiation response message carries Sharing information for network functions.
  • the solution of the embodiment of the present invention provides a specific manner for the first management unit to acquire the shared information of the network function from the second management unit, and obtains the process of requesting the network function from the first management unit to the second management unit.
  • the shared information of the network function sent by the second management unit is conveniently carried in the existing network function instantiation response message because the shared information of the network function is carried in the existing network function instantiation response message.
  • the first management unit when the shared information of the network function indicates that the network function can be shared by at least two network slices, the first management unit may select the network function to form at least one network slice; or, when the network function shares information When the network function is indicated to be incapable of being shared by at least two network slices, the first management unit may select the network function to form a network slice.
  • the solution of the embodiment of the present invention provides a specific manner for the first management unit to arrange the network function according to the sharing information of the network function, and the sharing information of the network function provides the network function for selecting the network function when the first management unit creates the network slice. in accordance with.
  • the network function may include a network function module, and the second management unit may acquire the shared information of the network function module; then, the first management unit may receive the shared information of the network function module from the second management unit, and the network function
  • the shared information of the module is used to indicate whether the network function module can be shared by at least two network slices.
  • the first management unit can receive the sharing information of the network function module from the second management unit, so that the network function module can be selected for the network slice according to the shared information of the network function module.
  • the first management unit may further receive a network slice creation request message or a network slice update request message, where the network slice is created.
  • the network slice or the network slice update request message requesting the message request to be created requests the updated network slice to include the network function.
  • the solution of the embodiment of the present invention provides a triggering condition for the first management unit to arrange the network function. That is, the solution of the embodiment of the present invention can combine the arrangement of the network function in the management process of the network slice.
  • the shared information of the network function may include at least one of the following: a sharing indication information of the network function, a Key Performance Indicator (KPI) information of the network function, or a sharing condition information of the network function.
  • KPI Key Performance Indicator
  • the solution of the embodiment of the present invention provides a specific type of the shared information of the network function, and the shared information of the network function may be the shared indication information of the network function, that is, whether the network function can be directly shared by at least two network slices.
  • the shared information of the network function may also be the KPI information of the network function or the sharing condition information of the network function, so that the network function may be indirectly determined according to the KPI information of the network function or the sharing condition information of the network function. At least two network slices are shared.
  • the embodiment of the present invention provides a first management unit, which is a network function management device, and can implement the functions performed by the first management unit in the foregoing method design, and the function can be Through hardware implementation, the corresponding software implementation can also be performed 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 configured to support the first management unit to perform a corresponding function in the above method.
  • the communication interface is for supporting communication between the first management unit and the second management unit or other units.
  • 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.
  • an embodiment of the present invention provides a second management unit, which is a management device of another network function, and can implement a function performed by a second management unit in the foregoing method design, where the function is performed. It can be implemented by hardware or by software.
  • 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 configured to support the second management unit to perform a corresponding function in the above method.
  • the communication interface is for supporting communication between the second management unit and the first management unit or other units.
  • the first 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 communication system, where the system includes the first management unit and the second management unit described in the foregoing aspects.
  • 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 execute 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 execute 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.
  • the first management unit receives the sharing information of the network function from the second management unit, and the sharing information of the network function is used to indicate whether the network function can be sliced by multiple networks. Sharing, the first management unit performs network function scheduling according to the shared information of the network function, thereby providing a specific solution for selecting to provide a shared network function or an exclusive network function to the network slice.
  • 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 network function management method according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of communication of another network function management method according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of communication of another method for managing a network function according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of communication of another method for managing a network function according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of communication of another method for managing a network function according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a first management unit according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of another first management unit according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a second management unit according to an embodiment of the present disclosure.
  • FIG. 10 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 used to more clearly illustrate the technical solutions of the embodiments of the present invention, and do not constitute a limitation of 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 shows a possible network architecture provided by an embodiment of the present invention.
  • the network architecture includes: Service Orchestrator (SO) unit, Network Orchestrator (NO) unit, Operations Support System (OSS), and Network Manager (NM). Unit and Network Function Virtualization Orchestration (NFVO) unit.
  • SO Service Orchestrator
  • NO Network Orchestrator
  • OSS Operations Support System
  • NM Network Manager
  • NFVO Network Function Virtualization Orchestration
  • the above OSS may be replaced by a Business Support System (BSS) or an Operator; or the OSS may have the functions of a BSS and/or an Operator, in addition to its own functions.
  • BSS Business Support System
  • the "Operator/BSS/OSS" in FIG. 1 indicates a unit having at least one of a function of an Operator, a function of a BSS, or a function of an OSS, and the unit may have other names, which is not limited by the embodiment of the present invention.
  • the above NM unit may be replaced by an Element Manager (EM) unit; or the above NM unit may have the function of an EM unit in addition to its own function.
  • EM/NM indicates a unit having the function of the EM and/or the function of the NM, and the unit may have other names, which are not limited in the embodiment of the present invention.
  • the above NFVO unit can be understood as a network function management (NFM) unit, which can be replaced by a virtual network function management (VNFM) unit, or the NFVO unit has its own function. It can also have the function of a VNFM unit.
  • the "NFVO/VNFM" in Fig. 1 indicates a unit having the function of the NFVO unit and/or the function of the VNFM unit, and the unit may have other names, which are not limited in the embodiment of the present invention.
  • Operator/BSS/OSS Operational support system/business and service support system, whose functions may include the functions of the SO unit and/or the functions of the NO unit.
  • the SO unit which may also be referred to as a service orchestration and management unit or a service management unit, mainly includes: performing lifecycle management (eg, instantiation, update, deletion, etc.) on the service according to the service request message; service aggregation; service Management, such as service fault, configuration, billing, performance and security (Fault, Configuration, Accounting, Performance, Security, FCAPS) management; and mapping between service and network slice (network slice).
  • the service may be a set of service level agreement (SLA) communication services that the user can enjoy, such as mobile broadband (MBB) services, voice services, and the Internet of Things (IOT).
  • MBB mobile broadband
  • IOT Internet of Things
  • Business for example, smart parking business, smart meter reading business, etc.
  • the SO unit can manage the services carried by the network slice.
  • NO unit its functions mainly include: management of network slices, such as lifecycle management of network slices, management of network slice templates, etc.; mapping between network slices and network functions; coordination of different types of network resources; different operators, Coordination of network resources provided by different network providers, so that network resources provided by different network providers can meet the requirements of target services, such as SLA requirements, Key Performance Indicator (KPI) requirements, and service quality. (Quality of Service, QoS) requirements; the unified orchestration of network devices provided by different vendors; the provision of external application program interfaces (APIs), which are used to provide network functions for third parties. To achieve cross-operator deployment.
  • QoS Quality of Service
  • the SO unit and the NO unit may be in the same management entity (for example, BSS/OSS); or, the SO unit and the NO unit may be independent entities.
  • the EM/NM unit mainly includes: lifecycle management of network elements (such as instantiation, update, deletion, etc.); FCAPS management of network elements.
  • the NFVO unit is mainly responsible for the management and orchestration of infrastructure and virtualized network functions (VNF) to implement complete network service orchestration; the NFVO unit is a virtual orchestration unit, and the virtual orchestration unit can also be a resource arrangement. (Resource Orchestrator, RO) unit, network service orchestrator unit or other unit.
  • VNF infrastructure and virtualized network functions
  • RO Resource Orchestrator
  • the VNFM unit is mainly responsible for the life cycle management of VNF and the monitoring of its resource usage.
  • the functions of the VNFM unit may include instantiation, addition, deletion, and Change, query, expansion/reduction, reservation, and dynamic monitoring of resources occupied by the VNF.
  • SO unit may be described as SO, and other units are similar, and will not be described again.
  • the embodiment of the present invention provides a management method for a network function, and a management unit and system based on the method.
  • the method includes: the second management unit acquires sharing information of the network function, where the sharing information of the network function is used to indicate whether the network function can be shared by the at least two network slices; and the second management unit sends the sharing information of the network function to the first management unit.
  • the first management unit orchestrate the network function according to the shared information of the network function.
  • the first management unit before the network function is configured, can obtain the shared information of the network function, and can further know whether the network function can be shared by at least two network slices, thereby arranging the network function.
  • a shared parameter may be introduced at a network function (NF) instance level and an instance module level, where the NF instance information includes a shared parameter of the NF.
  • the shared parameter of the NF is used to define whether the network function can be used simultaneously by at least two network slices.
  • the shared parameter of the network function module is used to define whether the network function module can be used simultaneously by at least two network slices.
  • NF includes virtual network functions and physical network functions.
  • the shared parameter may also be introduced in the NF descriptor 1evel and the module descriptor 1evel, for example, may be specifically set in the functional entity deployment maintenance template or descriptor.
  • the template may refer to any one of an NF descriptor, an NF module descriptor, a link descriptor, and a node descriptor.
  • the template can be set in the deployment flavor, or it can be set in the root attribute, or it can be set in the network function module outline, link outline or node outline.
  • the network functions are connected by links, and the nodes are the contact points between the links and the network functions.
  • a rule for determining whether to allow sharing may be set, that is, whether the NF instance can continue to accept the new slice to use the NF instance.
  • the maximum slice upper limit value that the functional entity can use for sharing can be statically set, or the rule allowing sharing can be dynamically set to detect the parameters of the functional entity instance.
  • the parameter can include virtual resource performance parameters and/or application performance parameters.
  • the virtual resource performance parameter includes at least one of the following: a central processing unit (Central) Processing Unit (CPU) occupancy, storage (Storage) usage, Network bandwidth usage, etc.
  • the application performance parameters include at least one of the following: SLA performance parameters, access success rate, adhesion rate, and the like.
  • a parameter calculation rule may be set, and an inter-parameter synthesis algorithm is determined to determine the comprehensive evaluation parameter, and the sharing of the network function is determined according to the comprehensive evaluation parameter by using the dynamically set rule that allows sharing.
  • the solution of the embodiment of the present invention will be further described below with reference to FIG. 2 to FIG. 6 .
  • the network architecture shown in FIG. 1 can be applied to FIG. 2 to FIG. 6 , wherein the first management unit is the NO and the second management unit is the NFM as an example, and the solution of the embodiment of the present invention is described.
  • FIG. 2 is a schematic diagram of communication of a network function management method according to an embodiment of the present invention. Referring to Figure 2, the method includes:
  • the second management unit obtains shared information of the network function.
  • the shared information of the network function is used to indicate whether the network function can be shared by at least two network slices.
  • the second management unit can obtain sharing information of network functions from a catalog.
  • the catalog may be set in the second management unit or in the third management unit independent of the second management unit. Thereby, the second management unit may acquire the sharing information of the network function from the local, or may receive the sharing information of the network function from the third management unit.
  • the second management unit may further receive a query request message from the first management unit, where the query request message is used to request the shared information of the network function.
  • the query request message may carry an identifier of the network function, an identifier of the network function descriptor, or a requirement information of the network function, and the identifier of the network function, the identifier of the network function descriptor, or the requirement information of the network function may be used for the second management unit.
  • the second management unit may acquire the shared information of the network function according to the identifier of the network function, the identifier of the network function descriptor, or the requirement information of the network function.
  • the requirement information of the network function may specifically be a type and function of the network function.
  • the network function instantiation request message may also be received from the first management unit.
  • the sharing information of the network function may be in various forms.
  • the sharing information of the network function may include at least one of the following: sharing indication information of the network function, KPI information of the network function, and sharing condition information of the network function. .
  • the second management unit transmits the sharing information of the network function to the first management unit.
  • the foregoing network function may refer to a certain type of network function
  • the second management unit may send the sharing information of the network function and the identifier of the network function descriptor to the first management unit, and indicate the instance based on the network function descriptor.
  • the network function instance can be shared or not shared; or the network function can also refer to a certain network function instance, and the second management unit can send the network function sharing information and the network function instance identifier to the first management unit. Used to indicate whether the network function instance can be shared.
  • the foregoing network function or a certain network function instance may be arranged according to the information.
  • the second management unit may send a query response message to the first management unit, where the query response message carries the shared information of the network function.
  • the second management unit may send a network function instantiation response message, the network function instantiation response message, to the first management unit. Shared information with network features.
  • the first management unit orchestrate the network function according to the shared information of the network function.
  • the first management unit may select the network function to form at least one network slice; or when the sharing information of the network function indicates the When the network function cannot be shared by at least two network slices, the first management unit may select the network function to form a network slice.
  • the first management unit can orchestrate network functions during the process of creating or updating a network slice.
  • the first management unit may also receive a network slice creation request message or a network slice update request message before the network function is scheduled, where the network slice creation request message requests the created network slice or the network slice update request message to request the updated network.
  • the slice includes the above network functions.
  • the embodiment of the invention provides a method for managing a network function.
  • the first management unit receives the sharing information of the network function from the second management unit, and the sharing information of the network function is used to indicate whether the network function can be shared by at least two network slices.
  • the first management unit orchestrate the network function according to the shared information of the network function, thereby providing a specific solution for selecting a shared network function or an exclusive network function for the network slice, thereby facilitating maintenance and management of the network function. .
  • the network function may include a network function module
  • the embodiment of the present invention may further provide a management method of the network function module on the basis of the manner shown in FIG. 2 .
  • the management method may include: the second management unit acquires the sharing information of the network function module; then, the second management unit sends the sharing information of the network function module to the first management unit, where the sharing information of the network function module is used to indicate the network function. Whether the module can be shared by at least two network slices; after receiving the shared information of the network function module, the first management unit arranges the network function module according to the shared information of the network function module.
  • the behavior of the second management unit acquiring the shared information of the network function module may be performed in part 201; the second management unit transmitting the shared information of the network function module to the first management unit may be performed in 202; in the 203 part, the first
  • the management function unit may also arrange the network function module according to the shared information of the network function module.
  • the various parts of the management method of the foregoing network function module may also have other implementation manners or timings, which are not limited by the embodiment of the present invention.
  • FIG. 3 is a schematic diagram of communication of another network function management method according to an embodiment of the present invention.
  • the same or similar content as the method shown in FIG. 2 may be referred to the detailed description in FIG. 2 . I will not repeat them here.
  • the following takes the scenario of creating a network slice by NO as an example.
  • Operator/BSS/OSS and SO NO can be an entity or separate entities.
  • the entity requesting to create a network slice can be NO, SO or Operator/ BSS/OSS.
  • the method includes:
  • Operator/BSS/OSS sends a Service Request message to the SO.
  • a service request message is used to request to provide a service, such as a private network service military network service.
  • the SO performs service aggregation or decomposition.
  • the SO can decompose the service into specific voice traffic and real-time data traffic.
  • the SO sends a Create Slice Instance Request message to the NO.
  • the Create Tile Instance Request message is used to request to create 1 voice slice and 1 data slice, respectively.
  • the NO after receiving the Create Tile Instance Request message, the NO sends a Create Network Function Instance Request message to the NFM.
  • the network function instance request message may carry a network function identifier.
  • the NFM applies to the Catalog for Network Function Descriptor (NFD) information based on the carried network function identifier.
  • NFD Network Function Descriptor
  • Section 306 the Catalog feeds back the corresponding network function descriptor information.
  • the network function descriptor information may include a shared parameter of the network function, and further, may further include a shared parameter of the specific network function module that instantiates the network function.
  • the network function module includes but is not limited to a network function module, a link, a node; the parameter may be set in any one of a network function root directory, a network function module descriptor, a link descriptor, a node descriptor, or Set in the deployment flavor, can be set in the root directory attribute, can also be set in the network function module outline, link outline, node outline; parameters can also be allowed to share rules, including rule algorithms, monitoring parameters, thresholds, etc. .
  • the Catalog may be a functional module located inside the NFM.
  • the NFM query to the Catalog is the internal operation of the entity.
  • the exclusive attributes are set in the specific network function modules, and the sharing is allowed in the highly reliable public modules.
  • the interface, the business processing module and the corresponding links and nodes set exclusive attributes to ensure that the module runs highly reliable, high performance, etc.; and the maintenance management module settings can be shared.
  • the NFM completes the NF instance based on shared parameters of the network function and/or shared parameters of the network function module.
  • the NFM sends an Operational Response message to the NO that completes the instantiation of the NF.
  • the operation response message may carry the shared information of the NF, and the shared information may include a shared parameter of the network function and/or a shared parameter of the network function module, or a rule algorithm, a monitoring parameter, a threshold, and the like.
  • the NO determines the NF used in generating the slice based on the shared information of the NF provided by the NFM, and creates a network slice.
  • the shared information of the NF indicates that it can be shared by at least two network slices
  • the corresponding NF may be selected for multiple network slices. For example, if the NF that can be shared is currently serving a network slice, NO may also Select this NF as the network tile service currently being created.
  • the NO sends a complete slice instance creation response message to the SO.
  • the SO sends a confirmation service creation completion response message to the Operator/BSS/OSS.
  • the deployment of the virtualized network function is guided according to the network function descriptor, and the attribute of the sharing is invoked, and the network slice instance is created.
  • the network function includes the shared attribute of the module, it is convenient to operate and manage the network function. .
  • FIG. 4 is a schematic diagram of communication of another method for managing a network function according to an embodiment of the present invention.
  • the same or similar content as the method shown in FIG. 2 or FIG. 3 can be referred to the detailed description in FIG. 2 or FIG. 3, and details are not described herein.
  • the following is an example of a NO expansion network slice.
  • Operator/BSS/OSS and SO NO can be an entity or separate entities.
  • the entity requesting to expand the network slice can be NO, SO, or Operator/BSS/.
  • OSS referring to Figure 4, the method includes:
  • Operator/BSS/OSS sends an Extended Original Service Request message to the SO.
  • the request message is used to expand a service or service, for example, to expand the monitoring function meter service.
  • the SO performs service aggregation or decomposition into the corresponding service.
  • the SO sends a Capacity Slice Instance Request message to the NO.
  • the service determined in part 402 is carried by the network slice.
  • the NO after receiving the expansion slice instance request message, the NO sends a capacity expansion network function instance request message to the NFM.
  • the capacity expansion network function instance request message may carry a network function identifier.
  • the NFM applies to the catalog to obtain network function descriptor information according to the carried network function identifier.
  • the Catalog feeds back the corresponding network function descriptor information, which includes the shared parameters of the desired network function and/or the shared parameters of the specific network function module of the network function.
  • the Catalog may be a functional module located inside the NFM.
  • the NFM query to the Catalog is the internal operation of the entity.
  • the NFM completes the NF expansion based on the shared parameters of the network function and/or the shared parameters of the network function module.
  • the NFM sends an Operational Response message to the NO to complete the expansion NF.
  • new network function modules may need to be used, so it is possible to consider whether the network function module can be shared, similar to the instantiation process.
  • NO sends a Complete Slice Instance Expansion Response message to the SO.
  • the SO sends a confirmation service expansion completion response message to the Operator/BSS/OSS.
  • the network function descriptor is used to guide the deployment of the virtualized network function, and the attribute of the sharing or not is invoked, and the network slice instance is expanded and updated.
  • the network function includes the shared attribute of the module, which facilitates the operation and maintenance of the network function. And management.
  • FIG. 5 is a schematic diagram of communication of a method for managing a network function according to an embodiment of the present invention.
  • the same or similar content as the method shown in FIG. 2, FIG. 3 or FIG.
  • the detailed description in FIG. 2, FIG. 3 or FIG. 4 is not described herein.
  • the entity that queries the network function instance information may be NO, SO, or Operator/BSS/OSS. In the embodiment of the present invention, only NO is taken as an example for description. Referring to Figure 5, the method includes:
  • the NO sends a query network function instance information request message to the NFM.
  • the request message may specify shared parameter information that requires querying network functions and/or shared parameter information of the network function module, or query all of the instance information.
  • the NFM queries the Catalog for network function instance information.
  • the Catalog may be a module inside the NFM, at which point the NFM only needs to perform internal queries.
  • the Catalog returns network function instance information to the NFM, which includes shared parameters of the network function and/or shared parameters of the specific network function module.
  • the network function instance information may also carry a rule of sharing or not, and a monitoring status of the instance, such as a threshold value or a calculation formula or a monitoring parameter. For example, to find a network slice instance of a high SLA, where the service module is an exclusive feature, and the public maintenance module is allowed to share, and the shared sharing rule of the shared sharing module is that when the CPU usage exceeds the threshold of 60%, Sharing is no longer allowed.
  • the NFM sends network function instance information to the NO, the network function instance information including shared parameters of the network function and/or shared parameters of the network function module.
  • the shared parameters of the network function and/or the shared parameters of the network function module may be collectively referred to as shared information of the network function.
  • the Catalog may be a functional module located inside the NFM.
  • the NFM query to the Catalog is the internal operation of the entity.
  • NO performs network function scheduling based on shared information of network functions.
  • the network function is selected according to whether the network function can be shared.
  • the sharing parameter of the network function and/or the sharing parameter of the network function module are embodied in the network function instance information, so that the network function instance information can be queried by querying the network function instance information.
  • FIG. 6 is a schematic diagram of communication of another method for managing a network function according to an embodiment of the present invention, wherein the method shown in FIG. 6 is the same as or similar to the method shown in FIG. 2, FIG. 3, FIG. 4 or FIG.
  • the entity that changes the shared parameter in the network function descriptor may be NO, SO, or Operator/BSS/OSS.
  • NO is taken as an example for description. Referring to Figure 6, the method includes:
  • the NO sends an NF request message to the NFM, the request message including a change request for the shared parameter of the NF descriptor.
  • the request message may further include information such as a template for generating the NF.
  • the NFM generates an NF based on the request message of the NO.
  • the NFM requests the Catalog to change the shared parameters of the NF Descriptor.
  • the Catalog sends feedback information to the NFM, including the shared parameters of the NF.
  • the Catalog may be a functional module located inside the NFM.
  • the NFM query to the Catalog is the internal operation of the entity.
  • the NFM sends an NF Create Response message to the NO.
  • the NF creation response message may include a shared parameter of the NF.
  • the NO arranges the network functions according to the sharing parameters of the network function. For example, when the network slice is instantiated, the network function can be selected according to whether the network function can be shared.
  • the sharing parameter in the network function descriptor can be configured to modify and update, thereby implementing management of more flexible network functions.
  • the manner of acquiring the shared parameters is flexible and diverse.
  • the NF instance information includes a shared parameter of the NF, and the shared parameter of the NF is used to indicate whether the entity instance can be used by multiple slice instances;
  • the NF descriptor includes the shared parameter of the entity, indicating whether the entity instance generated by the entity can be Multiple Slice instances are used;
  • the entity can be any of NF, NF modules, links, nodes, or any of the NF deployment style, NF module deployment style, link deployment style, and node deployment style;
  • the request message received by the NFM may carry the shared parameter and the rule parameter.
  • the request message received by the NFM carries the shared parameter and the rule parameter.
  • the information about the NF descriptor received by the NFM includes the shared parameter of the NF module; the shared descriptor of each specific NF is set in the Slice descriptor, and is associated with the shared parameter of the slice; the slice descriptor includes the shared parameter of the network slice, and the network slice.
  • the shared parameters are mapped and associated with the shared parameters of the NF contained in the Slice descriptor; the Slice instance letter
  • the information includes a shared parameter, and forms a mapping and association with the shared parameter of the NF instance information included in the Slice instance information; the shared parameter included in the NF instance information is mapped and associated with the released shared parameter of the included NF instance information, and is released.
  • the sharing parameter is used to indicate whether the state of the NF that can be shared by the plurality of network slices is changed; the sharing parameter included in the NF descriptor forms a mapping and association with the release sharing parameter of the included NF descriptor; NF may be shared in whole or in part; NF sharing, the NF modules included may be shared in whole or in part; the shared parameters include parameters of sharing or not, or rules for sharing, including threshold values, calculation methods, monitoring parameters, etc. .
  • 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. 7 shows a possible structural diagram of the first management unit involved in the above embodiment.
  • the first 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 first management unit.
  • the processing module 702 is configured to support the first management unit to perform the process 203 in FIG. 2, the processes 304, 309, and 310 in FIG. Processes 404, 409, and 410, processes 501 and 505 in FIG. 5, process 601 in FIG. 6, and/or other processes for the techniques described herein.
  • the communication module 703 is configured to support communication between the first management unit and other network entities, such as communication with the second management unit.
  • the first management unit may further include a storage module 701 for storing program codes and data of the first management unit.
  • the processing module 702 can be a processor or a controller, for example, can be a central processing unit. (Central Processing Unit, CPU), general purpose processor, digital signal processor (DSP), 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 703 can be a communication interface, a transceiver, 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 first management unit involved in the embodiment of the present invention may be the first management unit shown in FIG.
  • the first management unit 800 includes a processor 802, a communication interface 803, and a memory 801.
  • the first management unit 800 may further include a bus 804.
  • the communication interface 803, the processor 802, and the memory 801 may be connected to each other through a bus 804.
  • the bus 804 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 804 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 8, but it does not mean that there is only one bus or one type of bus.
  • FIG. 9 shows a possible structural diagram of the second management unit involved in the above embodiment.
  • the second management unit 900 includes a processing module 902 and a communication module 903.
  • the processing module 902 is configured to control and manage the actions of the second management unit.
  • the processing module 902 is configured to support the second management unit to perform the processes 201 and 202 in FIG. 2, the processes 305, 306, 307, and 308 in FIG. Processes 405, 406, 407, and 408 in FIG. 4, processes 502, 503, and 504 in FIG. 5, processes 602, 603, 604, and 605 in FIG. 6, and/or other techniques for the techniques described herein process.
  • the communication module 903 is configured to support communication between the second management unit and other network entities, such as communication with the first management unit.
  • the second management unit may further include a storage module 901 for storing program codes and data of the second management unit.
  • the processing module 902 can be a processor or a controller, such as a CPU, a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. It can implement or perform the various aspects described in connection with the present disclosure. Exemplary logic blocks, modules and circuits.
  • 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 903 can be a communication interface, a transceiver, a transceiver circuit, etc., wherein the communication interface is a collective name and can include one or more interfaces.
  • the storage module 901 can be a memory.
  • the second management unit may be the second management unit shown in FIG.
  • the second management unit 1000 includes a processor 1002, a communication interface 1003, and a memory 1001.
  • the second management unit 1000 may further include a bus 1004.
  • the communication interface 1003, the processor 1002, and the memory 1001 may be connected to each other through a bus 1004.
  • the bus 1004 may be a PCI bus or an EISA bus.
  • the bus 1004 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 FIG. 10, 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, compact disk read only (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 a core network interface device.
  • the processor and the storage medium may also exist as discrete components in the core network interface device.
  • 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.
  • the storage medium can be any one that can be accessed by a general purpose or special purpose computer. Use the media.

Landscapes

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

Abstract

本发明实施例涉及网络功能的管理方法、管理单元及系统，该方法包括：第二管理单元获取网络功能的共享信息，网络功能的共享信息用于指示网络功能是否能够被至少两个网络切片共享；第二管理单元向第一管理单元发送网络功能的共享信息；第一管理单元根据网络功能的共享信息，对网络功能进行编排。由上可见，本发明实施例，给出了给出了选择向网络切片提供共享的网络功能或独享的网络功能的具体解决方案，便于网络功能的维护和管理。

Description

网络功能的管理方法、管理单元及系统 技术领域
本发明实施例涉及通信领域，尤其涉及网络功能的管理方法、管理单元及系统。
背景技术
在研究未来的移动通信系统时，网络切片的概念被引入。网络切片可以理解为一种按需网络。一个物理网络可以在逻辑上被划分为多个网络切片，不同的网络切片可以用来承载不同的业务。例如，电力公司需要提供智能电表的业务，这种业务可以通过连接一系列机器对机器(Machine-to-Machine，M2M)设备的网络切片来实现。
网络切片可以由至少一个网络功能组成。实践中，若一个网络功能仅支持一个网络切片，那么网络功能的数量会过多，不便于维护和管理。
发明内容
本发明实施例提供了网络功能的管理方法、管理单元及系统，用于解决现有网络功能不便于管理的问题。
一方面，本发明实施例提供了一种网络功能的管理方法。该方法包括：第二管理单元获取网络功能的共享信息，网络功能的共享信息用于指示网络功能是否能够被至少两个网络切片共享；第二管理单元向第一管理单元发送网络功能的共享信息；第一管理单元根据网络功能的共享信息，对网络功能进行编排。
本发明实施例中，第一管理单元从第二管理单元接收网络功能的共享信息，网络功能的共享信息用于指示该网络功能是否能够被至少两个网络切片共享，第一管理单元根据网络功能的共享信息，对该网络功能进行编排，从而给出了选择向网络切片提供共享的网络功能或独享的网络功能的具体解决方案，便于网络功能的维护和管理。
在一个可能的设计中，第一管理单元可以向第二管理单元发送查询请求消息，查询请求消息用于请求网络功能的共享信息；然后，第一管理单元从第二管理单元接收查询响应消息，查询响应消息携带网络功能的共享信息。本发明实施例的方案，提供了一种第一管理单元向第二管理单元查询网络功能的共享信息的具体方式，便于第一管理单元根据需要随时获取网络功能的共享信息。
在一种可能的实施方式中，查询请求消息可以携带网络功能的标识、网络功能描述符的标识或网络功能的需求信息，第二管理单元可以根据网络功能的标识、网络功能描述符的标识或网络功能的需求信息获取网络功能的共享信息。本发明实施例的方案，提供了一种查询请求消息中携带的信息的具体类型，便于第二管理单元根据上述信息获取网络功能的共享信息。
在一个可能的设计中，第一管理单元可以向第二管理单元发送网络功能实例化请求消息；然后第一管理单元从第二管理单元接收网络功能实例化响应消息，网络功能实例化响应消息携带网络功能的共享信息。本发明实施例的方案，提供了一种第一管理单元从第二管理单元获取网络功能的共享信息的具体方式，在第一管理单元向第二管理单元请求网络功能实例化的过程中，获取第二管理单元发送的网络功能的共享信息，由于网络功能的共享信息携带于现有的网络功能实例化响应消息中，便于管理。
在一个可能的设计中，当网络功能的共享信息指示该网络功能能够被至少两个网络切片共享时，第一管理单元可以选择该网络功能组成至少一个网络切片；或者，当网络功能的共享信息指示该网络功能不能被至少两个网络切片共享时，第一管理单元可以选择该网络功能组成一个网络切片。本发明实施例的方案，提供了一种第一管理单元根据网络功能的共享信息，对网络功能进行编排的具体方式，网络功能的共享信息为第一管理单元创建网络切片时选择网络功能提供了依据。
在一个可能的设计中，网络功能可以包含网络功能模块，第二管理单元可以获取网络功能模块的共享信息；然后，第一管理单元可以从第二管理单元接收网络功能模块的共享信息，网络功能模块的共享信息用于指示该网络功能模块是否能够被至少两个网络切片共享。本发明实施例中，第一管理单元能够从第二管理单元接收网络功能模块的共享信息，从而可以根据网络功能模块的共享信息为网络切片选择网络功能模块。
在一个可能的设计中，第一管理单元根据网络功能的共享信息，对该网络功能进行编排之前，第一管理单元还可以接收网络切片创建请求消息或网络切片更新请求消息，其中，网络切片创建请求消息请求创建的网络切片或网络切片更新请求消息请求更新的网络切片包括该网络功能。本发明实施例的方案，提供了一种第一管理单元对网络功能进行编排的触发条件，也就是说，本发明实施例的方案能够将网络功能的编排结合在对网络切片的管理过程中。
在一个可能的设计中，网络功能的共享信息可以包括以下至少一种：网络功能的共享指示信息、网络功能的关键性能指标(Key Performance Indicator，KPI)信息或网络功能的共享条件信息。本发明实施例的方案，提供了网络功能的共享信息的具体类型，网络功能的共享信息可以为网络功能的共享指示信息，也就是说直接给出该网络功能是否能够被至少两个网络切片共享的指示；或者，网络功能的共享信息还可以为网络功能的KPI信息或网络功能的共享条件信息，从而可以根据网络功能的KPI信息或网络功能的共享条件信息来间接确定该网络功能是否能够被至少两个网络切片共享。
另一方面，本发明实施例提供了一种第一管理单元，该第一管理单元作为一种网络功能的管理装置，可以实现上述方法设计中第一管理单元所执行的功能，所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。
在一个可能的设计中，该第一管理单元的结构中包括处理器和通信接口，该处理器被配置为支持该第一管理单元执行上述方法中相应的功能。该通信接口用于支持该第一管理单元与第二管理单元或其他单元之间的通信。该第一管理单元还可以包括存储器，该存储器用于与处理器耦合，其保存该第一管理单元必要的程序指令和数据。
又一方面，本发明实施例提供了一种第二管理单元，该第二管理单元作为另一种网络功能的管理装置，可以实现上述方法设计中第二管理单元所执行的功能，所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。
在一个可能的设计中，该第二管理单元的结构中包括处理器和通信接口，该处理器被配置为支持该第二管理单元执行上述方法中相应的功能。该通信接口用于支持该第二管理单元与第一管理单元或其他单元之间的通信。该第 二管理单元还可以包括存储器，该存储器用于与处理器耦合，其保存该第二管理单元必要的程序指令和数据。
又一方面，本发明实施例提供了一种通信系统，该系统包括上述方面所述的第一管理单元和第二管理单元。
再一方面，本发明实施例提供了一种计算机存储介质，用于储存为上述第一管理单元所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
再一方面，本发明实施例提供了一种计算机存储介质，用于储存为上述第二管理单元所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
再一方面，本发明实施例提供了一种计算机程序产品，其包含指令，当所述程序被计算机所执行时，该指令使得计算机执行上述方法设计中第一管理单元所执行的功能。
再一方面，本发明实施例提供了一种计算机程序产品，其包含指令，当所述程序被计算机所执行时，该指令使得计算机执行上述方法设计中第二管理单元所执行的功能。
相较于现有技术，本发明实施例提供的方案中，第一管理单元从第二管理单元接收网络功能的共享信息，网络功能的共享信息用于指示该网络功能是否能够被多个网络切片共享，第一管理单元根据网络功能的共享信息，进行网络功能的编排，从而给出了选择向网络切片提供共享的网络功能或独享的网络功能的具体解决方案。
附图说明
图1为本发明实施例提供的一种可能的网络架构的示意图；
图2为本发明实施例提供的一种网络功能的管理方法的通信示意图；
图3为本发明实施例提供的另一种网络功能的管理方法的通信示意图；
图4为本发明实施例提供的又一种网络功能的管理方法的通信示意图；
图5为本发明实施例提供的再一种网络功能的管理方法的通信示意图；
图6为本发明实施例提供的再一种网络功能的管理方法的通信示意图；
图7为本发明实施例提供的一种第一管理单元的结构示意图；
图8为本发明实施例提供的另一种第一管理单元的结构示意图；
图9为本发明实施例提供的一种第二管理单元的结构示意图；
图10为本发明实施例提供的另一种第二管理单元的结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行描述。
本发明实施例描述的网络架构以及业务场景是为了更加清楚的说明本发明实施例的技术方案，并不构成对于本发明实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本发明实施例提供的技术方案对于类似的技术问题，同样适用。
下面首先结合图1对本发明实施例适用的可能的网络架构进行介绍。图1示出了本发明实施例提供的一种可能的网络架构。如图1所示，该网络架构包括：业务编排(Service Orchestrator，SO)单元、网络编排(Network Orchestrator，NO)单元、运营支撑系统(Operations Support System，OSS)、网络管理(Network Manager，NM)单元和网络功能虚拟化编排(Network Function Virtualization Orchestration，NFVO)单元。
上述OSS可以由业务支撑系统(Business Support System，BSS)或操作员(Operator)所替代；或者，上述OSS除具有自身的功能外，还可以具有BSS的功能和/或Operator的功能。图1中的“Operator/BSS/OSS”表示具有Operator的功能、BSS的功能或OSS的功能中的至少一项的单元，该单元也可以有其他名称，本发明实施例不对此进行限定。
上述NM单元可以由网元管理(Element Manager，EM)单元所替代；或者，上述NM单元除具有自身的功能外，还可以具有EM单元的功能。图1中的“EM/NM”表示具有EM的功能和/或NM的功能的单元，该单元也可以有其他名称，本发明实施例不对此进行限定。
上述NFVO单元可以理解为一种网络功能管理(Network Function Management，NFM)单元，其可以由虚拟网络功能管理(Virtualization Network Function Management，VNFM)单元所替代，或者，上述NFVO单元除具有自身的功能外，还可以具有VNFM单元的功能。图1中的“NFVO/VNFM”表示具有NFVO单元的功能和/或VNFM单元的功能的单元，该单元也可以有其他名称，本发明实施例不对此进行限定。
下面对图1中所涉及的各个单元作简单介绍：
Operator/BSS/OSS：运维支撑系统/业务与服务支撑系统，其功能可能包括SO单元的功能和/或NO单元的功能。
SO单元，也可以称为业务编排和管理单元或业务管理单元，其功能主要包括：根据业务请求消息对业务(service)进行生命周期管理(例如实例化、更新、删除等)；service聚合；service的管理，例如service的故障、配置、计费、性能和安全(Fault,Configuration,Accounting,Performance,Security，FCAPS)管理；以及service和网络切片(network slice)之间的映射等。其中，service可以是一组用户能享有的指定服务水平协议(Service Level Agreement，SLA)的通信业务，例如移动宽带(Mobile Broadband，MBB)业务、语音业务、以及物联网(Internet of Things，IOT)业务(例如，智能停车业务、智能抄表业务等)等。示例性的，SO单元可以对网络切片所承载的业务进行管理。
NO单元，其功能主要包括：网络切片的管理，例如网络切片的生命周期管理、网络切片模板的管理等；网络切片和网络功能之间的映射；不同类型的网络资源的协调；不同运营商、不同网络供应商所提供的网络资源的协调，以使得不同网络供应商所提供的网络资源可以满足目标业务的需求，例如SLA的要求、关键性能指标(Key Performance Indicator，KPI)的要求、服务质量(Quality of Service，QoS)的要求等；不同供应商所提供的网络设备的统一编排；对外的应用程序接口(Application Program Interface，API)的提供，其中该API接口用于为第三方提供网络功能，以实现跨运营商的部署。
本发明实施例中，SO单元和NO单元可以处于同一个管理实体(例如BSS/OSS)中；或者，SO单元和NO单元也可以是独立的实体。
EM/NM单元，其功能主要包括：网元的生命周期管理(例如实例化、更新、删除等)；网元的FCAPS管理等。
NFVO单元，其主要负责基础设施和虚拟网络功能(Virtualized Network Function，VNF)的管理和编排，进而实现完整的网络服务编排；NFVO单元是虚拟编排单元的一种，虚拟编排单元也可以是资源编排(Resource Orchestrator，RO)单元、网络服务编排(network service orchestrator)单元或者其他单元。
VNFM单元，其主要负责VNF的生命周期管理及其资源使用情况的监控。例如，VNFM单元的功能可以包括VNF的实例化、添加、删除、 更改、查询、扩容/缩容、预留以及VNF所占用资源的动态监控等。
为了描述方便，下文中，某一单元可以仅由其英文缩写进行描述，例如，SO单元可以描述为SO，其它单元类似，后续不再赘述。
下面将基于上面所述的本发明实施例涉及的共性方面，对本发明实施例进一步详细说明。
为了便于网络功能的维护和管理，本发明实施例提供一种网络功能的管理方法，和基于这个方法的管理单元及系统。该方法包括：第二管理单元获取网络功能的共享信息，网络功能的共享信息用于指示网络功能是否能够被至少两个网络切片共享；第二管理单元向第一管理单元发送网络功能的共享信息；第一管理单元根据网络功能的共享信息，对网络功能进行编排。本发明实施例的方案中，第一管理单元在对网络功能进行编排之前，能够获得网络功能的共享信息，进而能够获知网络功能是否能够被至少两个网络切片共享，从而对网络功能进行编排，便于网络功能的维护和管理。
下面对本发明实施例提供的网络功能的管理方法及该方法将涉及的一些概念进行简要说明。
本发明实施例中，可以在网络功能(Network Function，NF)实例层级(level)和实例模块level引入共享参数，其中，NF实例信息中包含NF的共享参数。NF的共享参数，用于定义该网络功能是否可以被至少两个网络切片同时使用。网络功能模块的共享参数，用于定义该网络功能模块是否可以被至少两个网络切片同时使用。NF包括虚拟网络功能和物理网络功能。本发明实施例中，还可以在NF描述符1evel及模块描述符1evel中引入共享参数，例如可具体设置在功能实体部署维护模版或描述符中。
模版可以指NF描述符、NF模块描述符、链接描述符、结点描述符的任意一种。模板可以设置在部署风格(deployment flavor)中，或者，可设置在根目录属性，或者，还可设置在网络功能模块轮廓、链接轮廓或结点轮廓里。其中，网络功能间由链接相连，结点是链接和网络功能间的接触点。
本发明实施例中，可以设置判断是否允许共享的规则，即该类NF实例能否继续接纳新slice使用该NF实例的判断规则。例如，可以静态设置功能实体可用于共享的最大slice上限值，或者，也可以动态设置允许共享的规则，检测功能实体实例的参数。该参数可以包括虚拟资源性能参数和/或应用性能参数。其中，虚拟资源性能参数包括以下至少一项：中央处理器(Central  Processing Unit，CPU)占用率、存储(Storage)占用率、Network带宽占用率等。应用性能参数包括以下至少一项：SLA性能参数、接入成功率、附着率等。此外，还可以设置参数计算规则，设定参数间综合算法确定综合评价参数，根据该综合评价参数利用前述动态设置的允许共享的规则形成对网络功能的共享与否判断。
下面结合图2～图6，对本发明实施例的方案做进一步说明。其中，图2～图6可以应用图1所示的网络架构，其中，以第一管理单元为前述NO，第二管理单元为前述NFM为例，对本发明实施例的方案进行说明。
图2为本发明实施例提供的一种网络功能的管理方法的通信示意图。参照图2，该方法包括：
在201部分，第二管理单元获取网络功能的共享信息。
其中，网络功能的共享信息用于指示该网络功能是否能够被至少两个网络切片共享。
在一个示例中，第二管理单元可以从目录(catalog)处获取网络功能的共享信息。可选的，catalog可以设置在第二管理单元内，也可以设置在独立于第二管理单元的第三管理单元内。从而，第二管理单元可以从本地获取网络功能的共享信息，也可以从第三管理单元接收网络功能的共享信息。
在一个示例中，第二管理单元获取网络功能的共享信息之前，还可以从第一管理单元接收查询请求消息，查询请求消息用于请求网络功能的共享信息。
可选地，查询请求消息可以携带网络功能的标识、网络功能描述符的标识或网络功能的需求信息，网络功能的标识、网络功能描述符的标识或网络功能的需求信息可用于第二管理单元获取网络功能的共享信息。对应的，第二管理单元可以根据网络功能的标识、网络功能描述符的标识或网络功能的需求信息获取网络功能的共享信息。其中，网络功能的需求信息具体可以为网络功能的类型、功能等。
在另一个示例中，第二管理单元获取网络功能的共享信息之前，还可以从第一管理单元接收网络功能实例化请求消息。
本发明实施例中，网络功能的共享信息可以有多种形式，例如，网络功能的共享信息可以包括以下至少一种：网络功能的共享指示信息、网络功能的KPI信息、网络功能的共享条件信息。
在202部分，第二管理单元向第一管理单元发送网络功能的共享信息。
在一个示例中，上述网络功能可以指某一类网络功能，第二管理单元可以向第一管理单元发送网络功能的共享信息和网络功能描述符的标识，用于指示基于该网络功能描述符实例化出来的网络功能实例都可以共享或者不共享；或者，上述网络功能也可以指某个网络功能实例，第二管理单元可以向第一管理单元发送网络功能的共享信息和网络功能实例的标识，用于指示该网络功能实例是否可以被共享。当第一管理单元从第二管理单元接收网络功能的共享信息后，可以根据该信息对上述某一类网络功能或上述某个网络功能实例进行编排。
在一个示例中，若第二管理单元从第一管理单元接收上述查询请求消息，则第二管理单元可以向第一管理单元发送查询响应消息，查询响应消息携带网络功能的共享信息。
在另一个示例中，若第二管理单元从第一管理单元接收上述网络功能实例化请求消息，则第二管理单元可以向第一管理单元发送网络功能实例化响应消息，网络功能实例化响应消息携带网络功能的共享信息。
在203部分，第一管理单元根据网络功能的共享信息，对网络功能进行编排。
在一个示例中，当网络功能的共享信息指示该网络功能能够被至少两个网络切片共享时，第一管理单元可以选择该网络功能组成至少一个网络切片；或者，当网络功能的共享信息指示该网络功能不能被至少两个网络切片共享时，第一管理单元可以选择该网络功能组成一个网络切片。
在一个示例中，第一管理单元可以在创建或更新网络切片的过程中，对网络功能进行编排。例如，第一管理单元对网络功能进行编排之前，还可以接收网络切片创建请求消息或网络切片更新请求消息，其中，网络切片创建请求消息请求创建的网络切片或网络切片更新请求消息请求更新的网络切片包括上述网络功能。
本发明实施例提供了一种网络功能的管理方法，第一管理单元从第二管理单元接收网络功能的共享信息，网络功能的共享信息用于指示该网络功能是否能够被至少两个网络切片共享，第一管理单元根据网络功能的共享信息，对该网络功能进行编排，从而给出了选择向网络切片提供共享的网络功能或独享的网络功能的具体解决方案，便于网络功能的维护和管理。
在一些可能的实施方式中，网络功能可以包括网络功能模块，本发明实施例可以在图2所示方式的基础上，进一步提供网络功能模块的管理方法。例如，该管理方法可以包括：第二管理单元获取网络功能模块的共享信息；然后，第二管理单元向第一管理单元发送网络功能模块的共享信息，网络功能模块的共享信息用于指示网络功能模块是否能够被至少两个网络切片共享；第一管理单元接收网络功能模块的共享信息后，根据网络功能模块的共享信息对网络功能模块进行编排。其中，第二管理单元获取网络功能模块的共享信息的行为可以在201部分执行；第二管理单元向第一管理单元发送网络功能模块的共享信息可以在202部分执行；在203部分中，第一管理单元根据网络功能的共享信息对网络功能进行编排时，还可以根据网络功能模块的共享信息对网络功能模块进行编排。当然，上述网络功能模块的管理方法中的各个部分也可以有其他实施的方式或时机，本发明实施例并不限定。
图3为本发明实施例提供的另一种网络功能的管理方法的通信示意图，其中，图3所示的方法中，与图2所示方法相同或相似的内容可以参考图2中的详细介绍，此处不作赘述。以下以NO创建网络切片的场景为例进行说明，这里Operator/BSS/OSS和SO、NO可以是一个实体，也可以是分别独立的实体，请求创建网络切片的实体可以是NO、SO或者Operator/BSS/OSS。参照图3，该方法包括：
在301部分，Operator/BSS/OSS向SO发送服务请求消息。
例如，服务请求消息用于请求提供一项服务，例如：专网业务军网服务。
在302部分，SO进行服务聚合或分解。
在一个示例中，SO可以将服务分解到具体的语音业务和实时数据业务。
在303部分，SO向NO发送创建切片实例请求消息。
在一个示例中，该创建切片实例请求消息用于请求分别创建1个语音切片和1个数据切片。
在304部分，NO接收到创建切片实例请求消息后，向NFM发送创建网络功能实例请求消息。
其中，网络功能实例请求消息可以携带网络功能标识。
在305部分，NFM根据携带的网络功能标识向Catalog申请获得网络功能描述符(Network Function Descriptor，NFD)信息。
在306部分，Catalog反馈相应网络功能描述符信息。
其中，网络功能描述符信息可以包含网络功能的共享参数，进一步地，还可以包含实例化网络功能的具体网络功能模块的共享参数。
在一个示例中，网络功能模块包括但不限于网络功能模块、链接、结点；参数可设置在网络功能根目录、网络功能模块描述符、链接描述符、结点描述符的任意一种，或设置在部署风味中，可设置在根目录属性，也可设置在网络功能模块轮廓、链接轮廓、结点轮廓里；参数也可以是允许共享的规则，包括规则算法、监控参数、门限值等。
本部分中，Catalog可能是位于NFM内部的一个功能模块，此时NFM向Catalog查询就是实体内部操作。
针对专网的高SLA要求，在具体网络功能模块设置独享属性，而在可靠性高的公共模块允许共享。比如：接口、业务处理模块及相应的链接和结点设置独享属性，确保模块运行高可靠、高性能等；而维护管理模块设置可共享。
在307部分，NFM根据网络功能的共享参数和/或网络功能模块的共享参数完成NF实例。
在308部分，NFM向NO发送完成实例化NF的操作响应消息。
操作响应消息可以携带NF的共享信息，该共享信息可以包括网络功能的共享参数和/或网络功能模块的共享参数，或者，规则算法、监控参数、门限值等。
在309部分，NO根据NFM提供的NF的共享信息，判断在生成切片时使用的NF，创建网络切片。
例如，当NF的共享信息指示其可以被至少两个网络切片共享时，可以选用相应的NF用于多个网络切片，例如如果可以共享的NF当前已经在为一个网络切片服务，那么NO也可以选择该NF为当前正在创建的网络切片服务。
在310部分，NO在完成网络切片的创建后，NO向SO发送完成切片实例创建响应消息。
在311部分，SO向Operator/BSS/OSS发送确认服务创建完成响应消息。
本发明实施例中，根据网络功能描述符指导虚拟化网络功能的部署，调用共享与否的属性，创建网络切片实例考虑到网络功能包括其模块的共享属性，便于对网络功能的运维和管理。
图4为本发明实施例提供的又一种网络功能的管理方法的通信示意图， 其中，图4所示的方法中，与图2或图3所示方法相同或相似的内容可以参考图2或图3中的详细介绍，此处不作赘述。以下以NO扩容网络切片为例进行说明，这里Operator/BSS/OSS和SO、NO可以是一个实体，也可以是分别独立的实体，请求扩容网络切片的实体可以是NO、SO或者Operator/BSS/OSS，参照图4，该方法包括：
在401部分，Operator/BSS/OSS向SO发送扩大原始服务请求消息。
该请求消息用于扩容一项服务或业务，例如，扩容监控职能电表业务。
在402部分，SO进行服务聚合或分解到相应业务。
在403部分，SO向NO发送扩容切片实例请求消息。
其中，402部分确定的业务由网络切片承载。
在404部分，NO接收到扩容切片实例请求消息后，向NFM发送扩容网络功能实例请求消息。
扩容网络功能实例请求消息可以携带网络功能标识。
在405部分，NFM根据携带的网络功能标识向Catalog申请获得网络功能描述符信息。
在406部分，Catalog反馈相应网络功能描述符信息，网络功能描述符信息包含所需扩容网络功能的共享参数和/或该网络功能的具体网络功能模块的共享参数。
有关网络功能模块的介绍可以参考图3的306部分中的详细内容，此处不作赘述。
本部分中，Catalog可能是位于NFM内部的一个功能模块，此时NFM向Catalog查询就是实体内部操作。
针对非实时低速率要求的业务，提供允许共享的网络功能模块。
在407部分，NFM根据网络功能的共享参数和/或网络功能模块的共享参数完成NF扩容。
在408部分，NFM向NO发送完成扩容NF的操作响应消息。
在NF扩容过程中，可能需要用到新的网络功能模块，那么可以类似实例化过程考虑这个网络功能模块是否可以共享。
在409部分，NO完成扩容网络切片实例。
在410部分，NO向SO发送完成切片实例扩容响应消息。
在411部分，SO向Operator/BSS/OSS发送确认服务扩大完成响应消息。
本发明实施例中，通过网络功能描述符指导虚拟化网络功能的部署，调用共享与否的属性，扩容、更新网络切片实例考虑到网络功能包括其模块的共享属性，便于对网络功能的运维和管理。
图5为本发明实施例提供的再一种网络功能的管理方法的通信示意图，其中，图5所示的方法中，与图2、图3或图4所示方法相同或相似的内容可以参考图2、图3或图4中的详细介绍，此处不作赘述。图5所示方法中，查询网络功能实例信息的实体可以是NO、SO或者Operator/BSS/OSS，本发明实施例中仅以NO为例进行说明。参照图5，该方法包括：
在501部分，NO向NFM发送查询网络功能实例信息请求消息。
该请求消息可指定要求查询网络功能的共享参数信息和/或网络功能模块的共享参数信息，或查询所有该实例信息。
在502部分，NFM向Catalog查询网络功能实例信息。
其中，Catalog可能是NFM内部的模块，此时NFM只需要进行内部查询。
在503部分，Catalog向NFM返回网络功能实例信息，其中包含网络功能的共享参数和/或具体网络功能模块的共享参数。
网络功能实例信息还可以携带共享与否的规则和该实例的监控状况，比如门限值或计算公式或监控参数等。例如：查找某高SLA的网络切片实例，其中业务模块是独享特性，而公共维护模块是允许共享的，而该允许共享模块的限制共享规则是，当CPU占用率超过门限值60％，则不再允许共享。
在504部分，NFM向NO发送网络功能实例信息，网络功能实例信息包含网络功能的共享参数和/或网络功能模块的共享参数。
网络功能的共享参数和/或网络功能模块的共享参数可以统称为网络功能的共享信息。
本步骤中，Catalog可能是位于NFM内部的一个功能模块，此时NFM向Catalog查询就是实体内部操作。
在505部分，NO根据网络功能的共享信息进行网络功能的编排。
例如，在进行网络切片实例化时，根据网络功能是否可以共享进行网络功能的选择。
本发明实施例中，在网络功能实例信息中体现了网络功能的共享参数和/或网络功能模块的共享参数，从而可以通过查询网络功能实例信息进行网络功能的编排。
图6为本发明实施例提供的再一种网络功能的管理方法的通信示意图，其中，图6所示的方法中，与图2、图3、图4或图5所示方法相同或相似的内容可以参考图2、图3、图4或图5中的详细介绍，此处不作赘述。图6所示方法中，更改网络功能描述符中的共享参数的实体可以是NO、SO或者Operator/BSS/OSS，本发明实施例中仅以NO为例进行说明。参照图6，该方法包括：
在601部分，NO向NFM发送创建NF请求消息，该请求消息中包括针对NF描述符的共享参数的更改要求。
该请求消息中还可以包括用于生成NF的模板等信息。
在602部分，NFM根据NO的请求消息生成NF。
在603部分，NFM向Catalog请求更改该NF描述符的共享参数。
在604部分，Catalog向NFM发送反馈信息，其中包括NF的共享参数。
本部分中，Catalog可能是位于NFM内部的一个功能模块，此时NFM向Catalog查询就是实体内部操作。
在605部分，NFM向NO发送NF创建响应消息。
NF创建响应消息可以包括该NF的共享参数。NO根据网络功能的共享参数对网络功能进行编排，例如在进行网络切片实例化时，根据网络功能是否可以共享进行网络功能的选择。
本发明实施例中，网络功能描述符中的共享参数可配置修改更新，从而实现更为灵活的网络功能的管理。
本发明实施例中，共享参数的获取方式灵活多样。NF实例信息中包含NF的共享参数，NF的共享参数用于指示此实体实例能否被多个Slice实例使用；NF描述符中包含实体的共享参数，表示此类实体生成的实体实例能否被多个Slice实例使用；实体可以是NF、NF模块、链接、结点的任一一种，或NF部署风格、NF模块部署风格、链接部署风格、结点部署风格的任一一种；在创建、配置、修改、更新NF实例时，NFM收到的请求消息可以携带共享参数及规则参数；在创建、配置、修改、更新NF描述符时，NFM收到的请求消息携带共享参数及规则参数。NFM接收到NF描述符的信息中包括NF模块的共享参数；Slice描述符中设置具体各个NF的共享参数，并与Slice的共享参数相关联；Slice描述符中包括网络切片的共享参数，网络切片的共享参数与Slice描述符中所包含的NF的共享参数形成映射和关联；Slice实例信 息中包括共享参数，与Slice实例信息所包含的NF实例信息的共享参数形成映射和关联；NF实例信息中包括的共享参数，与所包含的NF实例信息的释放共享参数形成映射和关联，释放共享参数用于指示NF的可被多个网络切片共享的状态是否被改变；NF描述符中包括的共享参数，与所包含的NF描述符的释放共享参数形成映射和关联；Slice共享，所含的NF可全部或部分共享；NF共享，所含的NF模块可全部或部分共享；共享参数包括共享与否的参数或否允许共享的规则，规则中包括门限值、计算方法、监控参数等。
上述主要从各个网元之间交互的角度对本发明实施例的方案进行了介绍。可以理解的是，各个网元，例如第一管理单元，第二管理单元等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
本发明实施例可以根据上述方法示例对第一管理单元、第二管理单元等进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本发明实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用集成的模块的情况下，图7示出了上述实施例中所涉及的第一管理单元的一种可能的结构示意图。第一管理单元700包括：处理模块702和通信模块703。处理模块702用于对第一管理单元的动作进行控制管理，例如，处理模块702用于支持第一管理单元执行图2中的过程203，图3中的过程304、309和310，图4中的过程404、409和410，图5中的过程501和505，图6中的过程601，和/或用于本文所描述的技术的其它过程。通信模块703用于支持第一管理单元与其他网络实体的通信，例如与第二管理单元之间的通信。第一管理单元还可以包括存储模块701，用于存储第一管理单元的程序代码和数据。
其中，处理模块702可以是处理器或控制器，例如可以是中央处理器 (Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块703可以是通信接口、收发器、收发电路等，其中，通信接口是统称，可以包括一个或多个接口。存储模块701可以是存储器。
当处理模块702为处理器，通信模块703为通信接口，存储模块701为存储器时，本发明实施例所涉及的第一管理单元可以为图8所示的第一管理单元。
参阅图8所示，该第一管理单元800包括：处理器802、通信接口803、存储器801。可选的，第一管理单元800还可以包括总线804。其中，通信接口803、处理器802以及存储器801可以通过总线804相互连接；总线804可以是外设部件互连标准(Peripheral Component Interconnect，简称PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，简称EISA)总线等。所述总线804可以分为地址总线、数据总线、控制总线等。为便于表示，图8中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在采用集成的模块的情况下，图9示出了上述实施例中所涉及的第二管理单元的一种可能的结构示意图。第二管理单元900包括：处理模块902和通信模块903。处理模块902用于对第二管理单元的动作进行控制管理，例如，处理模块902用于支持第二管理单元执行图2中的过程201和202，图3中的过程305、306、307和308，图4中的过程405、406、407和408，图5中的过程502、503和504，图6中的过程602、603、604和605，和/或用于本文所描述的技术的其它过程。通信模块903用于支持第二管理单元与其他网络实体的通信，例如与第一管理单元之间的通信。第二管理单元还可以包括存储模块901，用于存储第二管理单元的程序代码和数据。
其中，处理模块902可以是处理器或控制器，例如可以是CPU，通用处理器，DSP，ASIC，FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各 种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块903可以是通信接口、收发器、收发电路等，其中，通信接口是统称，可以包括一个或多个接口。存储模块901可以是存储器。
当处理模块902为处理器，通信模块903为通信接口，存储模块901为存储器时，本发明实施例所涉及的第二管理单元可以为图10所示的第二管理单元。
参阅图10所示，该第二管理单元1000包括：处理器1002、通信接口1003、存储器1001。可选的，第二管理单元1000还可以包括总线1004。其中，通信接口1003、处理器1002以及存储器1001可以通过总线1004相互连接；总线1004可以是PCI总线或EISA总线等。所述总线1004可以分为地址总线、数据总线、控制总线等。为便于表示，图10中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
结合本发明实施例公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read Only Memory，ROM)、可擦除可编程只读存储器(Erasable Programmable ROM，EPROM)、电可擦可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于核心网接口设备中。当然，处理器和存储介质也可以作为分立组件存在于核心网接口设备中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明实施例所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可 用介质。
以上所述的具体实施方式，对本发明实施例的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明实施例的具体实施方式而已，并不用于限定本发明实施例的保护范围，凡在本发明实施例的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明实施例的保护范围之内。

Claims (28)

  1. 一种网络功能的管理方法，其特征在于，所述方法包括：
    第一管理单元从第二管理单元接收网络功能的共享信息，所述网络功能的共享信息用于指示所述网络功能是否能够被至少两个网络切片共享；
    所述第一管理单元根据所述网络功能的共享信息，对所述网络功能进行编排。
  2. 根据权利要求1所述的方法，其特征在于，所述第一管理单元从第二管理单元接收网络功能的共享信息之前，所述方法还包括：
    所述第一管理单元向所述第二管理单元发送查询请求消息，所述查询请求消息用于请求所述网络功能的共享信息；
    所述第一管理单元从第二管理单元接收网络功能的共享信息，包括：
    所述第一管理单元从所述第二管理单元接收查询响应消息，所述查询响应消息携带所述网络功能的共享信息。
  3. 根据权利要求2所述的方法，其特征在于，所述查询请求消息携带所述网络功能的标识、网络功能描述符的标识或所述网络功能的需求信息，所述网络功能的标识、所述网络功能描述符的标识或所述网络功能的需求信息用于所述第二管理单元获取所述网络功能的共享信息。
  4. 根据权利要求1所述的方法，其特征在于，所述第一管理单元从第二管理单元接收网络功能的共享信息之前，所述方法还包括：
    所述第一管理单元向所述第二管理单元发送网络功能实例化请求消息；
    所述第一管理单元从第二管理单元接收网络功能的共享信息，包括：
    所述第一管理单元从所述第二管理单元接收网络功能实例化响应消息，所述网络功能实例化响应消息携带所述网络功能的共享信息。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述第一管理单元根据所述网络功能的共享信息，对所述网络功能进行编排，包括：
    当所述网络功能的共享信息指示所述网络功能能够被至少两个网络切片共享时，所述第一管理单元选择所述网络功能组成至少一个网络切片；或者，
    当所述网络功能的共享信息指示所述网络功能不能被至少两个网络切片共享时，所述第一管理单元选择所述网络功能组成一个网络切片。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述网络功能包含网络功能模块，所述方法还包括：
    所述第一管理单元从所述第二管理单元接收网络功能模块的共享信息，所述网络功能模块的共享信息用于指示所述网络功能模块是否能够被至少两个网络切片共享。
  7. 根据权利要求1所述的方法，其特征在于，所述第一管理单元根据所述网络功能的共享信息，对所述网络功能进行编排之前，所述方法还包括：
    所述第一管理单元接收网络切片创建请求消息或网络切片更新请求消息，其中，所述网络切片创建请求消息请求创建的网络切片或所述网络切片更新请求消息请求更新的网络切片包括所述网络功能。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述网络功能的共享信息包括以下至少一种：所述网络功能的共享指示信息、所述网络功能的关键性能指标KPI信息或所述网络功能的共享条件信息。
  9. 一种网络功能的管理方法，其特征在于，所述方法包括：
    第二管理单元获取网络功能的共享信息，所述网络功能的共享信息用于指示所述网络功能是否能够被至少两个网络切片共享；
    所述第二管理单元向第一管理单元发送所述网络功能的共享信息，以使得所述第一管理单元对所述网络功能进行编排。
  10. 根据权利要求9所述的方法，其特征在于，所述第二管理单元获取网络功能的共享信息之前，所述方法还包括：
    所述第二管理单元从所述第一管理单元接收查询请求消息，所述查询请求消息用于请求所述网络功能的共享信息；
    所述第二管理单元向第一管理单元发送所述网络功能的共享信息，包括：
    所述第二管理单元向所述第一管理单元发送查询响应消息，所述查询响应消息携带所述网络功能的共享信息。
  11. 根据权利要求10所述的方法，其特征在于，所述查询请求消息携带所述网络功能的标识、网络功能描述符的标识或所述网络功能的需求信息；
    所述第二管理单元获取网络功能的共享信息，包括：
    所述第二管理单元根据所述网络功能的标识、所述网络功能描述符的标识或所述网络功能的需求信息获取所述网络功能的共享信息。
  12. 根据权利要求9所述的方法，其特征在于，所述第二管理单元获取 网络功能的共享信息之前，所述方法还包括：
    所述第二管理单元从所述第一管理单元接收网络功能实例化请求消息；
    所述第二管理单元向第一管理单元发送所述网络功能的共享信息，包括：
    所述第二管理单元向所述第一管理单元发送网络功能实例化响应消息，所述网络功能实例化响应消息携带所述网络功能的共享信息。
  13. 根据权利要求9至12中任一项所述的方法，其特征在于，所述网络功能包含网络功能模块，所述方法还包括：
    所述第二管理单元获取所述网络功能模块的共享信息；
    所述第二管理单元向所述第一管理单元发送所述网络功能模块的共享信息，所述网络功能模块的共享信息用于指示所述网络功能模块是否能够被至少两个网络切片共享。
  14. 根据权利要求9至13中任一项所述的方法，其特征在于，所述网络功能的共享信息包括以下至少一种：所述网络功能的共享指示信息、所述网络功能的关键性能指标KPI信息或所述网络功能的共享条件信息。
  15. 一种第一管理单元，其特征在于，包括：处理模块和通信模块；
    所述处理模块用于通过所述通信模块从第二管理单元接收网络功能的共享信息，所述网络功能的共享信息用于指示所述网络功能是否能够被至少两个网络切片共享；以及用于根据所述网络功能的共享信息，对所述网络功能进行编排。
  16. 根据权利要求15所述的第一管理单元，其特征在于，所述处理模块还用于在通过所述通信模块从第二管理单元接收网络功能的共享信息之前，通过所述通信模块向所述第二管理单元发送查询请求消息，所述查询请求消息用于请求所述网络功能的共享信息；以及所述处理模块具体用于通过所述通信模块从所述第二管理单元接收查询响应消息，所述查询响应消息携带所述网络功能的共享信息。
  17. 根据权利要求16所述的第一管理单元，其特征在于，所述查询请求消息携带所述网络功能的标识、网络功能描述符的标识或所述网络功能的需求信息，所述网络功能的标识、所述网络功能描述符的标识或所述网络功能的需求信息用于所述第二管理单元获取所述网络功能的共享信息。
  18. 根据权利要求15所述的第一管理单元，其特征在于，所述处理模块还用于在通过所述通信模块从第二管理单元接收网络功能的共享信息之前， 通过所述通信模块向所述第二管理单元发送网络功能实例化请求消息；以及所述处理模块具体用于通过所述通信模块从所述第二管理单元接收网络功能实例化响应消息，所述网络功能实例化响应消息携带所述网络功能的共享信息。
  19. 根据权利要求15至18中任一项所述的第一管理单元，其特征在于，所述处理模块具体用于当所述网络功能的共享信息指示所述网络功能能够被至少两个网络切片共享时，选择所述网络功能组成至少一个网络切片；或者，所述处理模块具体用于当所述网络功能的共享信息指示所述网络功能不能被至少两个网络切片共享时，选择所述网络功能组成一个网络切片。
  20. 根据权利要求15至19中任一项所述的第一管理单元，其特征在于，所述网络功能包含网络功能模块，所述处理模块还用于通过所述通信模块从所述第二管理单元接收网络功能模块的共享信息，所述网络功能模块的共享信息用于指示所述网络功能模块是否能够被至少两个网络切片共享。
  21. 根据权利要求15所述的第一管理单元，其特征在于，所述处理模块还用于：在根据所述网络功能的共享信息，对所述网络功能进行编排之前，通过所述通信模块接收网络切片创建请求消息或网络切片更新请求消息，其中，所述网络切片创建请求消息请求创建的网络切片或所述网络切片更新请求消息请求更新的网络切片包括所述网络功能。
  22. 根据权利要求15至21中任一项所述的第一管理单元，其特征在于，所述网络功能的共享信息包括以下至少一种：所述网络功能的共享指示信息、所述网络功能的关键性能指标KPI信息或所述网络功能的共享条件信息。
  23. 一种第二管理单元，其特征在于，包括：处理模块和通信模块；
    所述处理模块用于获取网络功能的共享信息，所述网络功能的共享信息用于指示所述网络功能是否能够被至少两个网络切片共享；以及用于通过所述通信模块向第一管理单元发送所述网络功能的共享信息，以使得所述第一管理单元对所述网络功能进行编排。
  24. 根据权利要求23所述的第二管理单元，其特征在于，所述处理模块还用于在获取网络功能的共享信息之前，通过所述通信模块从所述第一管理单元接收查询请求消息，所述查询请求消息用于请求所述网络功能的共享信息；以及所述处理模块具体用于通过所述通信模块向所述第一管理单元发送查询响应消息，所述查询响应消息携带所述网络功能的共享信息。
  25. 根据权利要求24所述的第二管理单元，其特征在于，所述查询请求消息携带所述网络功能的标识、网络功能描述符的标识或所述网络功能的需求信息；所述处理模块具体用于根据所述网络功能的标识、所述网络功能描述符的标识或所述网络功能的需求信息获取所述网络功能的共享信息。
  26. 根据权利要求23所述的第二管理单元，其特征在于，所述处理模块还用于在获取网络功能的共享信息之前，通过所述通信模块从所述第一管理单元接收网络功能实例化请求消息；以及所述处理模块具体用于通过所述通信模块向所述第一管理单元发送网络功能实例化响应消息，所述网络功能实例化响应消息携带所述网络功能的共享信息。
  27. 根据权利要求23至26中任一项所述的第二管理单元，其特征在于，所述网络功能包含网络功能模块，所述处理模块还用于通过获取所述网络功能模块的共享信息；以及用于通过所述通信模块向所述第一管理单元发送所述网络功能模块的共享信息，所述网络功能模块的共享信息用于指示所述网络功能模块是否能够被至少两个网络切片共享。
  28. 根据权利要求23至27中任一项所述的第二管理单元，其特征在于，所述网络功能的共享信息包括以下至少一种：所述网络功能的共享指示信息、所述网络功能的关键性能指标KPI信息或所述网络功能的共享条件信息。
PCT/CN2016/105923 2016-11-15 2016-11-15 网络功能的管理方法、管理单元及系统 WO2018090191A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2016/105923 WO2018090191A1 (zh) 2016-11-15 2016-11-15 网络功能的管理方法、管理单元及系统
EP16921764.3A EP3531749B1 (en) 2016-11-15 2016-11-15 Management method, management unit and system for network function
CN201680090741.0A CN109964507B (zh) 2016-11-15 2016-11-15 网络功能的管理方法、管理单元及系统
US16/411,623 US10848366B2 (en) 2016-11-15 2019-05-14 Network function management method, management unit, and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/105923 WO2018090191A1 (zh) 2016-11-15 2016-11-15 网络功能的管理方法、管理单元及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/411,623 Continuation US10848366B2 (en) 2016-11-15 2019-05-14 Network function management method, management unit, and system

Publications (1)

Publication Number Publication Date
WO2018090191A1 true WO2018090191A1 (zh) 2018-05-24

Family

ID=62146021

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/105923 WO2018090191A1 (zh) 2016-11-15 2016-11-15 网络功能的管理方法、管理单元及系统

Country Status (4)

Country Link
US (1) US10848366B2 (zh)
EP (1) EP3531749B1 (zh)
CN (1) CN109964507B (zh)
WO (1) WO2018090191A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111292570A (zh) * 2020-04-01 2020-06-16 广州爱浦路网络技术有限公司 基于项目式教学的云端5gc通信实验教学系统及教学方法
CN113438268A (zh) * 2020-03-23 2021-09-24 诺基亚技术有限公司 与存储在nrf中的scp和sepp的信息有关的装置、方法和计算机程序
US11706107B2 (en) 2018-06-15 2023-07-18 Huawei Technologies Co., Ltd. Data management method and apparatus

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10637753B1 (en) * 2019-04-09 2020-04-28 Verizon Patent And Licensing Inc. Managing a 5G network using extension information
EP3937453B1 (en) * 2020-07-09 2023-01-11 Deutsche Telekom AG Method for an improved emulation and/or interworking functionality between a first mobile communication network and a second mobile communication network, system, emulation function, program and computer program product
CN117544940A (zh) * 2022-08-02 2024-02-09 中国电信股份有限公司 注册方法、网络仓储功能网元和网络功能网元及通信系统
EP4325793A1 (en) * 2022-08-17 2024-02-21 Ntt Docomo, Inc. Communication system and method for providing a virtual network function

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105813195A (zh) * 2016-05-13 2016-07-27 电信科学技术研究院 一种按需为终端选择移动性管理机制的方法及装置
CN106060900A (zh) * 2016-05-13 2016-10-26 宇龙计算机通信科技(深圳)有限公司 网络切片的接入控制方法及装置、终端化小区和sdn控制器

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5788294B2 (ja) * 2011-11-08 2015-09-30 株式会社日立製作所 ネットワークシステムの管理方法
WO2016086214A1 (en) * 2014-11-28 2016-06-02 Huawei Technologies Co., Ltd Systems and methods for providing customized virtual wireless networks based on service oriented network auto-creation
US10129108B2 (en) * 2015-11-13 2018-11-13 Huawei Technologies Co., Ltd. System and methods for network management and orchestration for network slicing
US10028128B2 (en) * 2016-04-29 2018-07-17 Motorola Mobility Llc Procedures to support network slicing in a wireless communication system
WO2017197273A1 (en) * 2016-05-12 2017-11-16 Convida Wireless, Llc Connecting to virtualized mobile core networks

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105813195A (zh) * 2016-05-13 2016-07-27 电信科学技术研究院 一种按需为终端选择移动性管理机制的方法及装置
CN106060900A (zh) * 2016-05-13 2016-10-26 宇龙计算机通信科技(深圳)有限公司 网络切片的接入控制方法及装置、终端化小区和sdn控制器

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3531749A4 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11706107B2 (en) 2018-06-15 2023-07-18 Huawei Technologies Co., Ltd. Data management method and apparatus
CN113438268A (zh) * 2020-03-23 2021-09-24 诺基亚技术有限公司 与存储在nrf中的scp和sepp的信息有关的装置、方法和计算机程序
CN111292570A (zh) * 2020-04-01 2020-06-16 广州爱浦路网络技术有限公司 基于项目式教学的云端5gc通信实验教学系统及教学方法
CN111292570B (zh) * 2020-04-01 2021-09-17 广州爱浦路网络技术有限公司 基于项目式教学的云端5gc通信实验教学系统及教学方法

Also Published As

Publication number Publication date
US10848366B2 (en) 2020-11-24
US20190268213A1 (en) 2019-08-29
CN109964507B (zh) 2020-11-06
EP3531749A1 (en) 2019-08-28
EP3531749A4 (en) 2019-08-28
EP3531749B1 (en) 2020-11-04
CN109964507A (zh) 2019-07-02

Similar Documents

Publication Publication Date Title
US11456930B2 (en) Network resource management method, apparatus, and system
WO2018090191A1 (zh) 网络功能的管理方法、管理单元及系统
CN109845303B (zh) 网络切片的管理方法及管理单元
US11051183B2 (en) Service provision steps using slices and associated definitions
CN108370341B (zh) 资源配置方法、虚拟网络功能管理器和网元管理系统
US10924966B2 (en) Management method, management unit, and system
WO2019001421A1 (zh) 网络切片管理方法、装置及计算机可读存储介质
WO2019062456A1 (zh) 网络的部署信息确定方法及设备
WO2021093782A1 (zh) 执行意图的方法及装置
US11088924B2 (en) Network management method, device, and system
WO2020073903A1 (zh) 时延敏感网络通信方法及其装置
WO2018076547A1 (zh) 网络切片的管理方法、管理单元及系统
JP2017517170A (ja) Ｎｆｖシステムにおけるサービス実装のための方法および通信ユニット
WO2019029268A1 (zh) 网络切片的部署方法和装置
WO2018137196A1 (zh) 一种网络切片的管理方法、管理单元和系统
WO2019174000A1 (zh) 用于业务管理的方法和装置
WO2019047769A1 (zh) 一种处理网络切片实例的方法、装置及系统
WO2019062634A1 (zh) 通信方法及装置
WO2023045552A1 (zh) 服务部署方法、服务部署系统、电子设备及存储介质
CN109417501A (zh) 网络资源的编排方法和设备
WO2019100796A1 (zh) 一种网络性能保障方法及装置
WO2018082574A1 (zh) 一种信息发送方法、单元和系统
WO2021093496A1 (zh) 执行意图的方法及装置
WO2016015223A1 (zh) 一种I/O通道QoS动态均衡方法及装置
CN107005468B (zh) 一种待上载的nsd的确定方法及装置

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: 16921764

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2016921764

Country of ref document: EP

Effective date: 20190524