WO2019072033A1 - 一种网络方法和系统、及终端 - Google Patents

一种网络方法和系统、及终端 Download PDF

Info

Publication number
WO2019072033A1
WO2019072033A1 PCT/CN2018/102345 CN2018102345W WO2019072033A1 WO 2019072033 A1 WO2019072033 A1 WO 2019072033A1 CN 2018102345 W CN2018102345 W CN 2018102345W WO 2019072033 A1 WO2019072033 A1 WO 2019072033A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
slice
instance
management object
sub
Prior art date
Application number
PCT/CN2018/102345
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 中兴通讯股份有限公司
Publication of WO2019072033A1 publication Critical patent/WO2019072033A1/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/14—Network analysis or design
    • H04L41/145—Network analysis or design involving simulating, designing, planning or modelling of a network
    • 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
    • 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
    • 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

Definitions

  • the present disclosure relates to the field of network communications, and more particularly to a network method and system, and a terminal.
  • the interface between the Network Management System (NMS) and the Element Management System (EMS) is called the northbound interface (Itf-N).
  • the EMS mainly completes the network element management layer (EML) function in the ITU (International Telecommunication Union) TMN (Telecommunications Management Network), that is, completes the management functions of one or more mobile communication devices, usually different devices.
  • EMS between vendors cannot be universal.
  • the NMS mainly performs the network management layer (NML) function in the ITU TMN and is responsible for the management of all network elements in a managed network. For the case where there are multiple device vendors in the managed network (called subnet, SubNetwork, see 3GPP TS 28.622), the entire subnet can be managed through the respective EMS management.
  • subnet SubNetwork
  • the OSS Operations support system
  • the BSS Business support system
  • the NMS is generally included in the OSS and is the OSS. a part of.
  • Network Slice is an important part of 5G.
  • the so-called network slicing mainly refers to an instantiated complete logical network composed of a set of network functions (including network resources supporting the network functions) with specific network characteristics, and the logical network is used to satisfy a certain type of specific network. Service needs. Examples of network characteristics here are ultra low latency, ultra high reliability, and the like.
  • the network slice is obtained by instantiating according to the network slice blueprint (which can be called a network slice template), and is also called a network slice instance.
  • the network slice blueprint (template) refers to a complete definition, which describes the structure, configuration, and workflow of the network slice instance.
  • the Network Slicing Management Function (NSMF) completes the network slice according to the definition of the network slice blueprint. Instantiation and control of its life cycle.
  • Network Slice Subnet When a network slice is complex, network slices can be decomposed into network slices (Network Slice Subnet) for ease of management.
  • a sub-slice refers to a group of network functions and network resources supporting the network functions, and has specific network characteristics.
  • a logical network A network slice can contain zero, one or more sub-slices. The management and orchestration of sub-slices is done by the Network Slice Subnet Management Function (NSSMF).
  • NSSMF Network Slice Subnet Management Function
  • VNF Virtualized Network Function
  • EMS the EMS
  • VNF manager VNFM the VNF manager VNFM
  • VIM Virtual Infrastructure Manager
  • Network Service The specific network service (Network Service) is generally completed by one or more VNF instances.
  • the management of network services is carried out by the NFV orchestrator NFVO.
  • the network service instance described herein provides support for the corresponding network slice or sub-slice instance.
  • the management of 5G communication system focuses on the management of network slicing, and for the management of network slicing, it is necessary to provide a solution that can consider the continuity of the original communication system management while considering and virtualizing. Synchronization of network function management.
  • the present disclosure proposes a network method and system, and a terminal, which can provide a scheme for implementing management network slicing.
  • the present disclosure proposes a network management method, the method comprising:
  • the information model of the management object is used for management of the network slice;
  • the instantiation of the management object is performed according to the information model of the established management object.
  • the establishing an information model of the management object includes at least one of the following:
  • the network slice management object information model includes at least one of the following attributes: a slice unique identifier, a first network service instance identifier, where the first network service instance identifier is used to represent a network slice instance and a network service. The correspondence between instances.
  • the network sub-slice management object information model includes at least one of the following attributes: a sub-slice unique identifier, and a second network service instance identifier; wherein the second network service instance identifier is used to represent a network sub-slice instance Correspondence with network service instances.
  • the network sub-slice management object information model further includes the following attributes: a subnet identifier; and the subnet identifier is used to indicate a correspondence between the network sub-slice instance and the subnet.
  • the network sub-slice management object information model is implemented by a sub-network management object information model
  • the information model of the network sub-slice management object includes at least one of the following attributes: a second network service instance identifier, a subnet identifier, where the second network service instance identifier is used to represent the network sub-slice instance and the network service instance. Correspondence relationship; the subnet identifier is used to indicate a correspondence between a network sub-slice instance and a subnet; or
  • the information model of the network sub-slice management object includes the following attributes: an instance type identifier, where the instance type identifier is used to identify whether the subnet instance represents a subnet instance or a network sub-slice instance; or
  • the information model of the network sub-slice management object includes at least one of the following attributes: a second network service instance identifier, an instance type identifier, where the second network service instance identifier is used to represent the network sub-slice instance and the network service instance.
  • the corresponding relationship between the network sub-slice instance and the sub-network; the instance type identifier is used to identify whether the sub-network instance represents a sub-network instance or a network sub-slice instance.
  • the information model for establishing a management object includes:
  • the network slice management object information model includes at least one of the following attributes: a slice unique identifier, a first network service instance identifier, where the first network service instance identifier is used to indicate a correspondence between the network slice instance and the network service instance relationship;
  • the network slice management object information model further includes an optional attribute: a subnet identifier; wherein the subnet identifier is used to indicate that the instance created according to the network slice management object information model is a network sub-slice instance.
  • the information model for establishing a management object includes:
  • the network slice management object information model is implemented by a subnet management object information model
  • the sub-subnet management object information model includes an optional attribute: an instance type identifier, where the instance type identifier is used to identify whether the subnet instance represents a subnet instance or a network slice instance.
  • the performing the instantiation of the management object according to the information model of the established management object includes:
  • the network slice management function module NSMF establishes a network slice instance corresponding to the management object through the orchestrator NFVO;
  • the NSMF establishes a network sub-slice instance corresponding to the management object through the network sub-slice management function module NSSMF.
  • the present disclosure also proposes a network management system, the system comprising:
  • a storage unit configured to store an information model of the established management object; the information model of the management object is used for management of a network slice;
  • a management function unit configured as an information model of the management object, for management of a network slice.
  • the information model of the management object includes at least one of a network slice management object information model and a network sub-slice management object information model;
  • the management function unit includes at least one of the following modules:
  • the network slice management function module is configured to create a network slice management object instance according to the network slice management object information model
  • the network sub-slice management function module is configured to create a network sub-slice management object instance according to the network sub-slice management object information model.
  • the network slice management object information model includes at least one of the following attributes: a slice unique identifier, a first network service instance identifier, where the first network service instance identifier is used to represent a network slice instance and a network service. The correspondence between instances.
  • the network sub-slice management object information model includes at least one of the following attributes: a sub-slice unique identifier, and a second network service instance identifier; wherein the second network service instance identifier is used to represent a network sub-slice instance Correspondence with network service instances.
  • the network sub-slice management object information model further includes the following attributes: a subnet identifier; and the subnet identifier is used to indicate a correspondence between the network sub-slice instance and the subnet.
  • the network sub-slice management function module generates a network sub-slice management object instance according to the sub-network management object information model
  • the information model of the network sub-slice management object includes at least one of the following attributes: a second network service instance identifier, a subnet identifier, where the second network service instance identifier is used to represent the network sub-slice instance and the network service Corresponding relationship between the instances; the subnet identifier is used to indicate a correspondence between the network sub-slice instance and the subnet; or
  • the information model of the network sub-slice management object includes the following attributes: an instance type identifier, where the instance type identifier is used to identify whether the subnet instance represents a subnet instance or a network sub-slice instance; or
  • the information model of the network sub-slice management object includes at least one of the following attributes: a second network service instance identifier, an instance type identifier, where the second network service instance identifier is used to represent the network sub-slice instance and the network service instance.
  • the corresponding relationship between the network sub-slice instance and the sub-network; the instance type identifier is used to identify whether the sub-network instance represents a sub-network instance or a network sub-slice instance.
  • the information model of the management object includes a network slice management object information model
  • the management function unit includes: a network slice management function module, configured to create a network slice management object instance according to the network slice management object information model;
  • the network slice management object information model includes at least one of the following attributes: a slice unique identifier, a first network service instance identifier, where the first network service instance identifier is used to indicate a correspondence between the network slice instance and the network service instance relationship;
  • the network slice management object information model further includes an optional attribute: a subnet identifier; wherein the subnet identifier is used to indicate that the instance created according to the network slice management object information model is a network sub-slice instance.
  • the network slice management function module generates a network slice management object instance according to the subnet management object information model
  • the sub-subnet management object information model includes an optional attribute: an instance type identifier, where the instance type identifier is used to identify whether the subnet instance represents a subnet instance or a network slice instance.
  • the performing the instantiation of the management object according to the information model of the established management object includes:
  • the network slice management function module NSMF establishes a network slice instance corresponding to the management object through the orchestrator NFVO;
  • the NSMF establishes a network sub-slice instance corresponding to the management object through the network sub-slice management function module NSSMF.
  • the present disclosure also proposes a terminal including a memory, a processor, and a computer program stored on the memory and operable on the processor, wherein the processor executes the computer
  • the program implements the processing of any of the above network management methods.
  • the technical solution provided by the present disclosure includes: establishing an information model of a management object; the information model of the management object is used for management of a network slice; and executing an instance of the management object according to an information model of the established management object Chemical.
  • the problem of the scheme of modeling the network slice and the sub-slice management object in the background of the network slice technology is not overcome in the existing mobile network management technology, and a network slice and sub-slice management is proposed.
  • Object modeling methods and network management methods provide a solution to the above problems.
  • FIG. 1 is a relationship diagram of a slice-related management object respectively modeled by a network slice and a network sub-slice according to an embodiment of the present disclosure
  • FIG. 2 is a relationship diagram of a slice related management object of a network sub-slice and a subnet merge according to an embodiment of the present disclosure
  • FIG. 3 is a relationship diagram of a slice related management object merged by a network sub-slice and a network slice according to an embodiment of the present disclosure
  • FIG. 4 is a diagram of a slice-related management object relationship in which a network slice and a network sub-slice are both merged into a subnet according to an embodiment of the present disclosure
  • FIG. 5 is a diagram of another slice related management object relationship according to an embodiment of the present disclosure.
  • the present disclosure proposes a network management method, the method comprising:
  • Step 100 Establish an information model of the management object.
  • Step 200 Perform instantiation of the management object according to the information model of the established management object.
  • the information model of the management object includes: an information model of the network slice management object and an information model of the network sub-slice management object;
  • the network slice and the network sub-slice are separately defined to define a management object information model, and specifically refer to FIG. 1 :
  • a network slice management object that is, a network slice IOC, named NerworkSlice
  • the network slice IOC includes at least one of the following attributes: a slice unique identifier, and a corresponding network service instance identifier (networkServiceId), that is, the first Network service instance identifier;
  • the network service instance identifier is used to indicate a correspondence between a network slice instance and a network service instance.
  • NerworkSliceSubnet an information model representing the network sub-slice management object, that is, the network sub-cut IOC, named NerworkSliceSubnet
  • the network sub-slice IOC includes at least one of the following attributes: a sub-slice unique identifier, and a corresponding network service instance identifier (networkServiceId) , that is, the second network service instance identifier;
  • the network sub-slice IOC further includes a subnetwork identifier (subnetworkId); the corresponding subnet identifier is an identifier of a subnet instance corresponding to the network sub-slice, and is used to connect the network.
  • the slice or sub-slice corresponds to the subnet of the 3GPP network management layer.
  • a communication service (communication service) is supported by one or more network slice instances, and a network slice instance may include 0, one or more network sub-slice instances, one
  • the network sub-slice may include one or more network functions; the correspondence between the network slice instance and the corresponding network service instance is established by the corresponding network service instance identifier (networkServiceId) attribute value included in the network slice instance; Corresponding relationship between the network sub-slice instance and the corresponding network service instance is established by the corresponding network service instance identifier (networkServiceId) attribute value included in the network sub-slice instance; the correspondence between the network sub-slice instance and the corresponding sub-network instance is passed The subnet instance identifier (subnetworkId) attribute value contained in the network sub-slice instance is established.
  • the management object information model is defined by means of network sub-slice and sub-network merge modeling, and specifically refers to FIG. 2:
  • the network slice IOC includes but is not limited to one of the following attributes: a slice unique identifier, a corresponding network service instance identifier (networkServiceId);
  • the extended sub-network IOC adds at least but not limited to the following attributes: the corresponding network service instance identifier (networkServiceId), The corresponding subnetwork identifier; the corresponding network service instance identifier (networkServiceId) attribute and the corresponding subnetwork identifier are optional conditional attributes, and the optional condition is that the subnet instance represents a network.
  • the sub-segment instance if it is a traditional subnet instance, does not have these two attributes; optionally, the instance type identifier instanceType attribute can also be added to distinguish whether the subnet instance represents a traditional subnet or a network sub-slice;
  • one communication service (Communication Service) is supported by one or more network slice instances, and one network slice instance may contain zero or more network sub-slice instances (via subnet IOC) Instantiated), a network sub-slice may contain one or more network functions; the correspondence between the network slice instance and the corresponding network service instance is determined by the corresponding network service instance identifier (networkServiceId) included in the network slice instance.
  • NetworkServiceId network Service instance identifier
  • the correspondence between the network sub-slice instance and the corresponding network service instance is established by the corresponding network service instance identifier (networkServiceId) attribute value included in the network sub-slice instance; the correspondence between the network sub-slice instance and the corresponding sub-network instance The relationship is established by the subnetId identity (subnetworkId) attribute value contained in the network sub-slice instance.
  • networkServiceId network service instance identifier
  • the network sub-slice and sub-network merge modeling and the examples also merge to define a management object information model, as specifically shown in FIG. 2:
  • the network slice IOC includes but is not limited to the following attributes: a slice unique identifier, a corresponding network service instance identifier (networkServiceId);
  • the extended sub-network IOC adds at least but not limited to the following attributes: corresponding network service instance identifier (networkServiceId); here
  • the corresponding network service instance identifier (networkServiceId) attribute is a conditional optional attribute.
  • the optional condition is that the subnet instance represents a network sub-slice instance, and if it is a traditional subnet instance, there is no such attribute; optionally, You can also distinguish the subnet instance from the traditional subnet or the network sub-slice by adding the instance type identifier instanceType attribute.
  • one communication service (Communication Service) is supported by one or more network slice instances, and one network slice instance may contain zero or more network sub-slice instances (via subnet IOC) Instantiated), a network sub-slice may contain one or more network functions; the correspondence between the network slice instance and the corresponding network service instance is determined by the corresponding network service instance identifier (networkServiceId) included in the network slice instance.
  • NetworkServiceId network Service instance identifier
  • the correspondence between the network sub-slice instance and the corresponding network service instance is established by the corresponding network service instance identifier (networkServiceId) attribute value included in the network sub-slice instance; when a subnet instance is a traditional subnet instance It only contains the ManagedElement instance; when a subnet instance is a network sub-slice instance, it can contain both ManagedElement and Network Function instances (actually instances of the Network Function subclass).
  • networkServiceId network service instance identifier
  • the network sub-slice and the network slice merge modeling manner defines a management object information model, which is specifically referred to FIG. 3:
  • the network slice IOC includes but is not limited to the following attributes: a slice unique identifier, a corresponding network service instance identifier (networkServiceId), and an optional condition
  • the corresponding subnet identifier (subnetworkId) is that the network slice instance represents a network sub-slice instance;
  • the network slice IOC-NerworkSlice may represent a network slice instance, or may represent a network sub-slice instance, and is distinguished by a conditional optional attribute "subnetworkId" (subnetworkId); if it is a network slice instance, there is no such Attribute; if it is a network sub-slice, it has this attribute;
  • one communication service (Communication Service) is supported by one or more network slice instances, and one network slice instance may contain zero or more network sub-slice instances, one network sub-slice
  • One or more network functions may be included; the correspondence between the network slice instance and the corresponding network service instance is established by the corresponding network service instance identifier (networkServiceId) included in the network slice instance; the network sub-slice instance and Corresponding relationship of the corresponding network service instance is established by the corresponding network service instance identifier (networkServiceId) attribute value included in the network sub-slice instance; the correspondence between the network sub-slice instance and the corresponding sub-network instance is included by the network sub-slice instance The subnet instance ID (subnetworkId) attribute value is established.
  • the relationship between the various management objects is shown in Figure 3.
  • the manner of network slice, network sub-slice, and subnet merge modeling defines a management object information model, as specifically shown in FIG. 4:
  • the extended subnet IOC adds at least but not limited to the following attributes: corresponding network service instance identifiers ( networkServiceId), the corresponding subnetwork identifier.
  • the corresponding network service instance identifier (networkServiceId) attribute and the corresponding subnetwork identifier are conditional optional attributes; for the corresponding network service instance identifier (networkServiceId) attribute, the optional condition is the subnet instance.
  • NetworkServiceId networkServiceId
  • the optional condition is the subnet instance.
  • the instance type identifier instanceType attribute may be added to distinguish whether the subnet instance represents a traditional subnet or a network sub-slice or a network slice;
  • one communication service (Communication Service) is supported by one or more network slice instances, and one network slice instance may contain zero or more network sub-slice instances (via subnet IOC) Instantiated), a network sub-slice may contain one or more network functions; the correspondence between the network slice instance and the corresponding network service instance is determined by the corresponding network service instance identifier (networkServiceId) included in the network slice instance.
  • NetworkServiceId network Service instance identifier
  • the correspondence between the network sub-slice instance and the corresponding network service instance is established by the corresponding network service instance identifier (networkServiceId) attribute value included in the network sub-slice instance; the correspondence between the network sub-slice instance and the corresponding sub-network instance The relationship is established by the subnetId identity (subnetworkId) attribute value contained in the network sub-slice instance.
  • networkServiceId network service instance identifier
  • step 200 includes:
  • Step 210 The NSMF establishes, by using NFVO, a network slice instance corresponding to the management object.
  • the example of establishing a network slice corresponding to the network service includes: NSMF instantiating an instance of the management object corresponding to the slice according to an information model of the network slice management object (network slice IOC-NerworkSlice), and performing an instance of the management object
  • network slice IOC-NerworkSlice an information model of the network slice management object
  • the attribute slice unique identifier (ID), and the corresponding network service instance identifier (networkServiceId) is assigned;
  • Step 220 In the case that the network slice includes the sub-slice, the NSMF establishes a network sub-slice instance corresponding to the management object by using the NSSMF;
  • Step 220 includes:
  • Step 221 The NSSMF instantiates the network service (NS) corresponding to the sub-slice by using NFVO;
  • Step 222 The NSSMF instantiates the management object instance corresponding to the sub-slice according to the information model of the sub-slice management object (sub-slice IOC-NerworkSliceSubnet), and uniquely identifies (ID) the attribute slice of the management object instance, and corresponding The network service instance identifier (networkServiceId) and the corresponding subnetwork identifier are assigned;
  • Step 223 The NSSMF further configures the network sub-slice instance corresponding to the management object.
  • Step 230 The NSMF further configures the network slice instance corresponding to the management object, where the foregoing configuration is further configured to enable the network slice to enter a normal running state.
  • the network slice and the network sub-slice are separately modeled to define a management object information model, and the network function included in the sub-slice is represented by an enhanced managed function ManagedFunction management object, that is, may be included in
  • the network function management object of the sub-slice can be represented as a subclass of ManagedFunction, as shown in Figure 5:
  • a network slice management object that is, a network slice IOC, named NerworkSlice
  • the network slice IOC includes at least one of the following attributes: a slice unique identifier; optionally, a corresponding network service instance identifier ( networkServiceId), that is, the first network service instance identifier;
  • the network service instance identifier is used to indicate a correspondence between a network slice instance and a network service instance.
  • NerworkSliceSubnet an information model representing the network sub-slice management object, that is, the network sub-cut IOC, named NerworkSliceSubnet
  • the network sub-slice IOC includes at least one of the following attributes: a sub-slice unique identifier, and a corresponding network service instance identifier (networkServiceId) , that is, the second network service instance identifier;
  • the network sub-slice IOC further includes a subnetwork identifier (subnetworkId), where the corresponding subnet identifier refers to an identifier of a subnet instance corresponding to the network sub-slice. Used to associate a network slice or sub-slice with a subnet of the 3GPP network management layer.
  • subnetworkId subnetwork identifier
  • a communication service (communication service) is supported by one or more network slice instances, and a network slice instance may include 0, one or more network sub-slice instances, one The network sub-slice may include one or more sub-classes of managed functions (ManagedFunction); the correspondence between the network slice instance and the corresponding network service instance is determined by the corresponding network service instance identifier (networkServiceId) attribute included in the network slice instance.
  • ManagedFunction managed functions
  • network serviceId network service instance identifier
  • the value is established; the correspondence between the network sub-slice instance and the corresponding network service instance is established by the corresponding network service instance identifier (networkServiceId) attribute value included in the network sub-slice instance; the correspondence between the network sub-slice instance and the corresponding sub-network instance The relationship is established by the subnetId identity (subnetworkId) attribute value contained in the network sub-slice instance.
  • networkServiceId network service instance identifier
  • the embodiment of the present disclosure further provides a network management system, where the network management system proposed by the present disclosure includes:
  • a storage unit configured to store an information model of the established management object; the information model of the management object is used for management of a network slice;
  • a management function unit for using the information model of the management object for management of network slices.
  • the information model of the management object includes at least one of a network slice management object information model and a network sub-slice management object information model;
  • the management function unit includes at least one of the following modules:
  • a network slice management function module configured to create a network slice management object instance according to the network slice management object information model
  • the network sub-slice management function module is configured to create a network sub-slice management object instance according to the network sub-slice management object information model.
  • the network slice management object information model includes at least one of the following attributes: a slice unique identifier, a first network service instance identifier, where the first network service instance identifier is used to represent a network slice instance and a network. The correspondence between service instances.
  • the network sub-slice management object information model includes at least one of the following attributes: a sub-slice unique identifier, a second network service instance identifier, where the second network service instance identifier is used to represent a network sub-slice The correspondence between instances and network service instances.
  • the network sub-slice management object information model further includes the following attributes: a subnet identifier; the subnet identifier is used to indicate a correspondence between the network sub-slice instance and the subnet.
  • the network sub-slice management function module generates a network sub-slice management object instance according to the sub-network management object information model
  • the information model of the network sub-slice management object includes at least one of the following attributes: a second network service instance identifier, a subnet identifier, where the second network service instance identifier is used to represent the network sub-slice instance and the network service Corresponding relationship between the instances; the subnet identifier is used to indicate a correspondence between the network sub-slice instance and the subnet; or
  • the information model of the network sub-slice management object includes the following attributes: an instance type identifier, where the instance type identifier is used to identify whether the subnet instance represents a subnet instance or a network sub-slice instance; or
  • the information model of the network sub-slice management object includes at least one of the following attributes: a second network service instance identifier, an instance type identifier, where the second network service instance identifier is used to represent the network sub-slice instance and the network service instance.
  • the corresponding relationship between the network sub-slice instance and the sub-network; the instance type identifier is used to identify whether the sub-network instance represents a sub-network instance or a network sub-slice instance.
  • the information model of the management object includes a network slice management object information model
  • the management function unit includes: a network slice management function module, configured to create a network slice management object instance according to the network slice management object information model;
  • the network slice management object information model includes at least one of the following attributes: a slice unique identifier, a first network service instance identifier, where the first network service instance identifier is used to indicate a correspondence between the network slice instance and the network service instance relationship;
  • the network slice management object information model further includes an optional attribute: a subnet identifier; wherein the subnet identifier is used to indicate that the instance created according to the network slice management object information model is a network sub-slice instance.
  • the network slice management function module generates a network slice management object instance according to the subnet management object information model
  • the sub-subnet management object information model includes an optional attribute: an instance type identifier, where the instance type identifier is used to identify whether the subnet instance represents a subnet instance or a network slice instance.
  • the performing the instantiation of the management object according to the information model of the established management object includes:
  • the network slice management function module NSMF establishes a network slice instance corresponding to the management object through the orchestrator NFVO;
  • the NSMF establishes a network sub-slice instance corresponding to the management object through the network sub-slice management function module NSSMF.
  • an embodiment of the present disclosure further provides a terminal, including a memory, a processor, and a computer program stored on the memory and operable on the processor, the processor.
  • a terminal including a memory, a processor, and a computer program stored on the memory and operable on the processor, the processor.
  • the present disclosure is applicable to the field of network communication, and overcomes the problem that the existing mobile network management technology has not yet modeled the network slice and the sub-slice management object in the background of the network slice technology, and proposes a network slice. And the modeling method and network management method of the sub-slice management object provide a solution to solve the above problem.

Landscapes

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

Abstract

本公开提供一种网络方法和系统、及终端，该方法包括：建立管理对象的信息模型；所述管理对象的信息模型用于网络切片的管理；根据建立的管理对象的信息模型，执行管理对象的实例化。通过本公开的方案，克服现有移动网络管理技术中还没有在采用网络切片技术的背景下对网络切片及子切片管理对象进行建模的方案的问题，通过提出一种网络切片及子切片管理对象的建模方法和网络管理方法，为解决上述问题提供一种解决方案。 (图1)

Description

一种网络方法和系统、及终端 技术领域
本公开涉及网络通信领域，尤指一种网络方法和系统、及终端。
背景技术
目前在无线通讯系统的管理领域，网络管理系统(Network Management System,NMS)与网元管理系统(Element Management System–EMS)之间的接口称为北向接口(Itf-N)。EMS主要完成ITU(International Telecommunication Union,国际电信联盟)TMN(Telecommunications Management Network，电信管理网络)中的网元管理层(EML)功能，即完成一个或多个移动通信设备的管理功能，通常不同设备供应商之间的EMS无法通用。NMS主要完成ITU TMN中的网络管理层(NML)功能，负责一个被管网络内所有网元的管理。对于被管网络(称为子网，SubNetwork，参见3GPP TS 28.622)内存在多个设备供应商的情况，可以通过各自的EMS管理达到管理整个子网的目的。
而在运营商的整个管理系统中，一般还包含OSS(Operations support system,运营支撑系统)、BSS(Business support system,业务支撑系统)，从总体上看，一般认为NMS包含在OSS中，是OSS的一部分。
目前，业界已进一步开始了5G的研究，而网络切片(Network Slice)是5G的一个重要组成部分。所谓网络切片，主要是指由一组网络功能(包含支持所述网络功能的网络资源)组成的具有特定的网络特性的实例化的完整的逻辑网络，该逻辑网络用于满足某一类特定网络服务的需求。这里的网络特性的例子有超低延时、超高可靠性等。
网络切片是根据网络切片蓝图(可以称为网络切片模板)进行实例化而获得，故也称网络切片实例。网络切片蓝图(模板)是指一个完整的定义，用于描述网络切片实例的结构、配置、工作流，网络切片管理功能模块(Network Slicing Management Function-NSMF)根据网络切片蓝图的定义完成网络切片的实例化及其生命周期的控制管理。
当一个网络切片比较复杂时，为了便于管理，网络切片可以分解为子切片(Network Slice Subnet)，子切片是指一组网络功能及支持所述网络功能的网络资源组成的具有特定的网络特性的一个逻辑网络。一个网络切片可以包含0个、1个或多个子切片。对于子切片的管理和编排，由子切片管理功能(Network Slice Subnet Management Function-NSSMF)完成。
5G网络的一个重要特点就是采用了虚拟化技术，5G网络的网络功能可以通过运行于通用硬件平台的软件，即虚拟化网络功能(Virtualized Network Function-VNF)提供。对于VNF的管理，通过EMS对VNF实例进行传统的维护管理功能，而VNF的生命周期管理功能则通过VNF管理器VNFM完成。底层的虚拟基础架构由虚拟基础架构管理器(VIM)进行管理。而具体的网络服务(Network Service)，则一般通过一个或多个VNF实例来完成。对网络服务的管理，则通过NFV编排器NFVO来进行。实现网络功能虚拟化后，从应用层 面来看，要建立一个网络服务实例时，需要先生成网络服务需要的VNF的实例，再由一个或多个VNF实例组成一个网络服务实例，通过网络服务实例来提供网络服务。当网络切片采用虚拟化技术时，这里所述的网络服务实例为对应的网络切片或子切片实例提供支持。
因此，5G通讯系统的管理的重点在于是对网络切片的管理，而对于网络切片的管理，需要提供一种方案，既能够考虑原有通讯系统管理的延续性的同时，又要考虑与虚拟化网络功能管理的同步。
发明内容
为了解决上述问题，本公开提出了一种网络方法和系统、及终端，能够提供一种实现管理网络切片的方案。
为了解决上述技术问题，本公开提出了一种网络管理方法，所述方法包括：
建立管理对象的信息模型；所述管理对象的信息模型用于网络切片的管理；
根据建立的管理对象的信息模型，执行管理对象的实例化。
在一示例中，所述建立管理对象的信息模型包括如下内容的至少一项：
创建网络切片管理对象信息模型；
创建网络子切片管理对象信息模型；
在一示例中，所述网络切片管理对象信息模型包括如下属性的至少一个：切片唯一标识、第一网络服务实例标识；其中，所述第一网络服务实例标识用于表示网络切片实例与网络服务实例之间的对应关系。
在一示例中，所述网络子切片管理对象信息模型包括如下属性的至少一个：子切片唯一标识、第二网络服务实例标识；其中，所述第二网络服务实例标识用于表示网络子切片实例与网络服务实例之间的对应关系。
在一示例中，所述网络子切片管理对象信息模型还包括如下属性：子网标识；所述子网标识用于表示网络子切片实例与子网之间的对应关系。
在一示例中，所述网络子切片管理对象信息模型是通过子网管理对象信息模型实现的；
在子网管理对象信息模型还用于实现网络子切片管理对象信息模型时，
所述网络子切片管理对象的信息模型包括如下属性的至少一个：第二网络服务实例标识、子网标识；其中，所述第二网络服务实例标识用于表示网络子切片实例与网络服务实例之间的对应关系；所述子网标识用于表示网络子切片实例与子网之间的对应关系；或，
所述网络子切片管理对象的信息模型包括如下属性：实例类型标识，所述实例类型标识用于标识子网实例表示的是子网实例还是网络子切片实例；或，
所述网络子切片管理对象的信息模型包括如下属性的至少一个：第二网络服务实例标识、实例类型标识；其中，所述第二网络服务实例标识用于表示网络子切片实例与网络服务实例之间的对应关系；所述子网标识用于表示网络子切片实例与子网之间的对应关系；所述实例类型标识用于标识子网实例表示的是子网实例还是网络子切片实例。
在一示例中，所述建立管理对象的信息模型包括：
创建网络切片管理对象信息模型；
所述网络切片管理对象信息模型包括如下属性的至少一个：切片唯一标识、第一网络服务实例标识；其中，所述第一网络服务实例标识用于表示网络切片实例与网络服务实例之间的对应关系；
所述网络切片管理对象信息模型还包括可选属性：子网标识；其中，所述子网标识用于表示根据所述网络切片管理对象信息模型创建的实例为网络子切片实例。
在一示例中，所述建立管理对象的信息模型包括：
所述网络切片管理对象信息模型是通过子网管理对象信息模型实现的；
所述过子网管理对象信息模型包括可选属性：实例类型标识；其中，所述实例类型标识用于标识子网实例表示的是子网实例还是网络切片实例。
在一示例中，所述根据建立的管理对象的信息模型，执行管理对象的实例化包括：
网络切片管理功能模块NSMF通过编排器NFVO建立管理对象对应的网络切片实例；
在网络切片包括子切片的情况下，NSMF通过网络子切片管理功能模块NSSMF建立管理对象对应的网络子切片实例。
为了解决上述技术问题，本公开还提出了一种网络管理系统，所述系统包括：
存储单元，设置为存储建立的管理对象的信息模型；所述管理对象的信息模型用于网络切片的管理；
管理功能单元，设置为所述管理对象的信息模型用于网络切片的管理。
在一示例中，管理对象的信息模型包括网络切片管理对象信息模型和网络子切片管理对象信息模型中的至少一个；
所述管理功能单元包括如下模块的至少一个：
网络切片管理功能模块，设置为根据网络切片管理对象信息模型，创建网络切片管理对象实例；
网络子切片管理功能模块，设置为根据网络子切片管理对象信息模型，创建网络子切片管理对象实例。
在一示例中，所述网络切片管理对象信息模型包括如下属性的至少一个：切片唯一标识、第一网络服务实例标识；其中，所述第一网络服务实例标识用于表示网络切片实例与网络服务实例之间的对应关系。
在一示例中，所述网络子切片管理对象信息模型包括如下属性的至少一个：子切片唯一标识、第二网络服务实例标识；其中，所述第二网络服务实例标识用于表示网络子切片实例与网络服务实例之间的对应关系。
在一示例中，所述网络子切片管理对象信息模型还包括如下属性：子网标识；所述子网标识用于表示网络子切片实例与子网之间的对应关系。
在一示例中，在子网管理对象信息模型用于实现网络子切片管理对象信息模型时，
所述网络子切片管理功能模块根据子网管理对象信息模型生成网络子切片管理对象实例；
其中，所述网络子切片管理对象的信息模型包括如下属性的至少一个：第二网络服务实例标识、子网标识；其中，所述第二网络服务实例标识用于表示网络子切片实例与网络服务实例之间的对应关系；所述子网标识用于表示网络子切片实例与子网之间的对应关系；或，
所述网络子切片管理对象的信息模型包括如下属性：实例类型标识，所述实例类型标识用于标识子网实例表示的是子网实例还是网络子切片实例；或，
所述网络子切片管理对象的信息模型包括如下属性的至少一个：第二网络服务实例标识、实例类型标识；其中，所述第二网络服务实例标识用于表示网络子切片实例与网络服务实例之间的对应关系；所述子网标识用于表示网络子切片实例与子网之间的对应关系；所述实例类型标识用于标识子网实例表示的是子网实例还是网络子切片实例。
在一示例中，管理对象的信息模型包括网络切片管理对象信息模型；
所述管理功能单元包括：网络切片管理功能模块，用于根据网络切片管理对象信息模型，创建网络切片管理对象实例；
所述网络切片管理对象信息模型包括如下属性的至少一个：切片唯一标识、第一网络服务实例标识；其中，所述第一网络服务实例标识用于表示网络切片实例与网络服务实例之间的对应关系；
所述网络切片管理对象信息模型还包括可选属性：子网标识；其中，所述子网标识用于表示根据所述网络切片管理对象信息模型创建的实例为网络子切片实例。
在一示例中，在子网管理对象信息模型用于实现网络切片管理对象信息模型时，
所述网络切片管理功能模块根据子网管理对象信息模型生成网络切片管理对象实例；
其中，所述过子网管理对象信息模型包括可选属性：实例类型标识；其中，所述实例类型标识用于标识子网实例表示的是子网实例还是网络切片实例。
在一示例中，所述根据建立的管理对象的信息模型，执行管理对象的实例化包括：
网络切片管理功能模块NSMF通过编排器NFVO建立管理对象对应的网络切片实例；
在网络切片包括子切片的情况下，NSMF通过网络子切片管理功能模块NSSMF建立管理对象对应的网络子切片实例。
为了解决上述技术问题，本公开还提出了一种终端，包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，其中，所述处理器执行所述计算机程序时实现上述任一网络管理方法的处理。
与现有技术相比，本公开提供的技术方案包括：建立管理对象的信息模型；所述管理对象的信息模型用于网络切片的管理；根据建立的管理对象的信息模型，执行管理对象的实例化。通过本公开的方案，克服现有移动网络管理技术中还没有在采用网络切片技术的背景下对网络切片及子切片管理对象进行建模的方案的问题，通过提出一种网络切片及子切片管理对象的建模方法和网络管理方法，为解决上述问题提供一种解决方案。
附图说明
下面对本公开实施例中的附图进行说明，实施例中的附图是用于对本公开的进一步理 解，与说明书一起用于解释本公开，并不构成对本公开保护范围的限制。
图1为本公开实施例提供的网络切片和网络子切片分别建模的切片相关管理对象关系图；
图2为本公开实施例提供的网络子切片和子网合并的切片相关管理对象关系图；
图3为本公开实施例提供的网络子切片和网络切片合并的切片相关管理对象关系图；
图4为本公开实施例提供的网络切片和网络子切片都合并到子网的切片相关管理对象关系图；
图5为本公开实施例提供的另一种切片相关管理对象关系图。
具体实施方式
为了便于本领域技术人员的理解，下面结合附图对本公开作进一步的描述，并不能用来限制本公开的保护范围。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的各种方式可以相互组合。
本公开提出了一种网络管理方法，所述方法包括：
步骤100，建立管理对象的信息模型；
步骤200，根据建立的管理对象的信息模型，执行管理对象的实例化；
步骤100中，管理对象的信息模型包括：网络切片管理对象的信息模型和网络子切片管理对象的信息模型；
在本公开的一个实施例中，网络切片和网络子切片分别建模的方式定义管理对象信息模型，具体参考图1所示：
1、创建表示网络切片管理对象的信息模型，即网络切片IOC，命名为NerworkSlice,所述网络切片IOC至少包含如下属性之一：切片唯一标识，对应的网络服务实例标识(networkServiceId)，即第一网络服务实例标识；
其中，所述网络服务实例标识用于表示网络切片实例与网络服务实例之间的对应关系；
2、创建表示网络子切片管理对象的信息模型，即网络子切IOC，命名为NerworkSliceSubnet，所述网络子切片IOC至少包含如下属性之一：子切片唯一标识，对应的网络服务实例标识(networkServiceId)，即第二网络服务实例标识；；
其中，所述网络子切片IOC还包含对应的子网(subnetwork)标识(subnetworkId)；所述对应的子网标识，是指跟所述网络子切片对应的子网实例的标识，用于将网络切片或子切片跟3GPP网络管理层面的子网对应起来。
其中，在上述建模方式下，一个通讯业务(Communication Service)由1个或多个网络切片实例提供支持，而一个网络切片实例则可以包含0个、1个或多个网络子切片实例，一个网络子切片可以包含1个或多个网络功能(Network Function)；网络切片实例和相应的网络服务实例的对应关系通过所述网络切片实例包含的对应的网络服务实例标识(networkServiceId)属性值建立；网络子切片实例和相应的网络服务实例的对应关系通过所述网络子切片实例包含的对应的网络服务实例标识(networkServiceId)属性值建立；网络子 切片实例和相应的子网实例的对应关系则通过网络子切片实例包含的子网实例标识(subnetworkId)属性值建立。
在本公开的一个实施例中，通过网络子切片和子网合并建模的方式定义管理对象信息模型，具体参考图2所示：
1、创建表示网络切片管理对象的信息模型-网络切片IOC，命名为NerworkSlice,所述网络切片IOC包含但不限于如下属性之一：切片唯一标识，对应的网络服务实例标识(networkServiceId)；
2、对现有的子网IOC进行扩展，使其可以用于管理子网或网络子切片，扩展后的子网IOC增加了至少但不限于如下属性：对应的网络服务实例标识(networkServiceId)、对应的子网(subnetwork)标识；这里所述对应的网络服务实例标识(networkServiceId)属性和对应的子网(subnetwork)标识是条件可选属性，可选条件是该子网实例表示的是一个网络子切片实例，若是传统子网实例，则没有这两个属性；可选地，也可以通过增加实例类型标识instanceType属性来区分子网实例表示的是传统子网还是网络子切片；
3、在上述建模方式下，一个通讯业务(Communication Service)由1个或多个网络切片实例提供支持，而一个网络切片实例则可以包含0个或多个网络子切片实例(通过子网IOC实例化)，一个网络子切片可以包含1个或多个网络功能(Network Function)；网络切片实例和相应的网络服务实例的对应关系通过所述网络切片实例包含的对应的网络服务实例标识(networkServiceId)建立；网络子切片实例和相应的网络服务实例的对应关系通过所述网络子切片实例包含的对应的网络服务实例标识(networkServiceId)属性值建立；网络子切片实例和相应的子网实例的对应关系则通过网络子切片实例包含的子网实例标识(subnetworkId)属性值建立。各个管理对象间的关系见图2。
在本公开的一个实施例中，网络子切片和子网合并建模并且实例也合并的方式定义管理对象信息模型，具体参考图2所示：
1、创建表示网络切片管理对象的信息模型-网络切片IOC，命名为NerworkSlice,所述网络切片IOC包含但不限于如下属性：切片唯一标识，对应的网络服务实例标识(networkServiceId)；
2、对现有的子网IOC进行扩展，使其可以同时管理子网和网络子切片，扩展后的子网IOC增加了至少但不限于如下属性：对应的网络服务实例标识(networkServiceId)；这里所述对应的网络服务实例标识(networkServiceId)属性是条件可选属性，可选条件是该子网实例表示的是一个网络子切片实例，若是传统子网实例，则没有这个属性；可选地，也可以通过增加实例类型标识instanceType属性来区分子网实例表示的是传统子网还是网络子切片；
3、在上述建模方式下，一个通讯业务(Communication Service)由1个或多个网络切片实例提供支持，而一个网络切片实例则可以包含0个或多个网络子切片实例(通过子网IOC实例化)，一个网络子切片可以包含1个或多个网络功能(Network Function)；网络切片实例和相应的网络服务实例的对应关系通过所述网络切片实例包含的对应的网络服务实例标识(networkServiceId)建立；网络子切片实例和相应的网络服务实例的对应关系通过所述 网络子切片实例包含的对应的网络服务实例标识(networkServiceId)属性值建立；当一个子网实例是一个传统子网实例时，它只包含ManagedElement实例；当一个子网实例是一个网络子切片实例时，它可以同时包含ManagedElement和Network Function实例(实际为Network Function子类的实例)。各个管理对象间的关系见图2。
在本公开的一个实施例中，网络子切片和网络切片合并建模的方式定义管理对象信息模型，具体参考图3所示：
1、创建表示网络切片管理对象的信息模型-网络切片IOC，命名为NerworkSlice,所述网络切片IOC包含但不限于如下属性：切片唯一标识，对应的网络服务实例标识(networkServiceId)，条件可选的对应的子网标识(subnetworkId)，可选条件是网络切片实例表示的是一个网络子切片实例；
2、这里，网络切片IOC-NerworkSlice可以表示网络切片实例，也可以表示网络子切片实例，通过条件可选属性“对应的子网标识”(subnetworkId)来进行区分；若是网络切片实例，则没有这个属性；若是网络子切片，则有这个属性；
3、在上述建模方式下，一个通讯业务(Communication Service)由1个或多个网络切片实例提供支持，而一个网络切片实例则可以包含0个或多个网络子切片实例，一个网络子切片可以包含1个或多个网络功能(Network Function)；网络切片实例和相应的网络服务实例的对应关系通过所述网络切片实例包含的对应的网络服务实例标识(networkServiceId)建立；网络子切片实例和相应的网络服务实例的对应关系通过所述网络子切片实例包含的对应的网络服务实例标识(networkServiceId)属性值建立；网络子切片实例和相应的子网实例的对应关系则通过网络子切片实例包含的子网实例标识(subnetworkId)属性值建立。各个管理对象间的关系见图3。
在本公开的一个实施例中，网络切片、网络子切片和子网合并建模的方式定义管理对象信息模型，具体参考图4所示：
1、对现有的子网IOC进行扩展，使其可以用于管理子网、网络子切片或网络切片，扩展后的子网IOC增加了至少但不限于如下属性：对应的网络服务实例标识(networkServiceId)、对应的子网(subnetwork)标识。这里所述对应的网络服务实例标识(networkServiceId)属性和对应的子网(subnetwork)标识是条件可选属性；对于所述对应的网络服务实例标识(networkServiceId)属性，可选条件是该子网实例表示的是一个网络子切片实例或网络切片实例；对于对应的子网(subnetwork)标识属性，可选条件是该子网实例表示的是一个网络子切片实例。所以，若是传统子网实例，则没有这两个属性；若是网络切片实例，则有对应的网络服务实例标识(networkServiceId)属性；若是网络子切片实例，则同时有对应的网络服务实例标识(networkServiceId)属性和对应的子网(subnetwork)标识属性。可选地，也可以通过增加实例类型标识instanceType属性来区分子网实例表示的是传统子网还是网络子切片或网络切片；
2、在上述建模方式下，一个通讯业务(Communication Service)由1个或多个网络切片实例提供支持，而一个网络切片实例则可以包含0个或多个网络子切片实例(通过子网IOC 实例化)，一个网络子切片可以包含1个或多个网络功能(Network Function)；网络切片实例和相应的网络服务实例的对应关系通过所述网络切片实例包含的对应的网络服务实例标识(networkServiceId)建立；网络子切片实例和相应的网络服务实例的对应关系通过所述网络子切片实例包含的对应的网络服务实例标识(networkServiceId)属性值建立；网络子切片实例和相应的子网实例的对应关系则通过网络子切片实例包含的子网实例标识(subnetworkId)属性值建立。各个管理对象间的关系见图4。
本公开实施例中，步骤200包括：
步骤210，NSMF通过NFVO建立管理对象对应的网络切片实例；
其中，建立网络服务(NS)对应的网络切片实例包括：NSMF根据网络切片管理对象的信息模型(网络切片IOC--NerworkSlice)实例化所述切片对应的管理对象实例，并对所述管理对象实例的属性切片唯一标识(ID)，对应的网络服务实例标识(networkServiceId)赋值；
步骤220，在网络切片包括子切片的情况下，NSMF通过NSSMF建立管理对象对应的网络子切片实例；
步骤220包括：
步骤221，NSSMF通过NFVO对所述子切片对应的网络服务(NS)进行实例化；
步骤222，NSSMF根据子切片管理对象的信息模型(子切片IOC--NerworkSliceSubnet)实例化所述子切片对应的管理对象实例，并对所述管理对象实例的属性切片唯一标识(ID)、对应的网络服务实例标识(networkServiceId)、对应的子网(subnetwork)标识赋值；
步骤223，NSSMF对管理对象对应的网络子切片实例进行进一步配置；
步骤230、NSMF对管理对象对应的网络切片实例进行进一步配置，上述进一步配置用于使网络切片可以进入正常运行状态。
在本公开的一个实施例中，网络切片和网络子切片分别建模的方式定义管理对象信息模型，而子切片包含的网络功能则通过增强的被管功能ManagedFunction管理对象来表示，即可以包含在子切片的网络功能管理对象都可以表示为ManagedFunction的子类，具体参考图5所示：
1、创建表示网络切片管理对象的信息模型，即网络切片IOC，命名为NerworkSlice,所述网络切片IOC至少包含如下属性之一：切片唯一标识；可选地，还包含对应的网络服务实例标识(networkServiceId)，即第一网络服务实例标识；
其中，所述网络服务实例标识用于表示网络切片实例与网络服务实例之间的对应关系；
2、创建表示网络子切片管理对象的信息模型，即网络子切IOC，命名为NerworkSliceSubnet，所述网络子切片IOC至少包含如下属性之一：子切片唯一标识，对应的网络服务实例标识(networkServiceId)，即第二网络服务实例标识；
其中，可选地，所述网络子切片IOC还包含对应的子网(subnetwork)标识(subnetworkId)；所述对应的子网标识，是指跟所述网络子切片对应的子网实例的标识，用于将网络切片或子切片跟3GPP网络管理层面的子网对应起来。
其中，在上述建模方式下，一个通讯业务(Communication Service)由1个或多个网络切片实例提供支持，而一个网络切片实例则可以包含0个、1个或多个网络子切片实例，一个网络子切片可以包含1个或多个被管功能(ManagedFunction)的子类；网络切片实例和相应的网络服务实例的对应关系通过所述网络切片实例包含的对应的网络服务实例标识(networkServiceId)属性值建立；网络子切片实例和相应的网络服务实例的对应关系通过所述网络子切片实例包含的对应的网络服务实例标识(networkServiceId)属性值建立；网络子切片实例和相应的子网实例的对应关系则通过网络子切片实例包含的子网实例标识(subnetworkId)属性值建立。
基于与上述实施例相同或相似的构思，本公开实施例还提供一种网络管理系统，本公开提出的一种网络管理系统包括：
存储单元，用于存储建立的管理对象的信息模型；所述管理对象的信息模型用于网络切片的管理；
管理功能单元，用于所述管理对象的信息模型用于网络切片的管理。
本公开实施例中，管理对象的信息模型包括网络切片管理对象信息模型和网络子切片管理对象信息模型中的至少一个；
所述管理功能单元包括如下模块的至少一个：
网络切片管理功能模块，用于根据网络切片管理对象信息模型，创建网络切片管理对象实例；
网络子切片管理功能模块，用于根据网络子切片管理对象信息模型，创建网络子切片管理对象实例。
本公开实施例中，所述网络切片管理对象信息模型包括如下属性的至少一个：切片唯一标识、第一网络服务实例标识；其中，所述第一网络服务实例标识用于表示网络切片实例与网络服务实例之间的对应关系。
本公开实施例中，所述网络子切片管理对象信息模型包括如下属性的至少一个：子切片唯一标识、第二网络服务实例标识；其中，所述第二网络服务实例标识用于表示网络子切片实例与网络服务实例之间的对应关系。
本公开实施例中，所述网络子切片管理对象信息模型还包括如下属性：子网标识；所述子网标识用于表示网络子切片实例与子网之间的对应关系。
本公开实施例中，在子网管理对象信息模型用于实现网络子切片管理对象信息模型时，
所述网络子切片管理功能模块根据子网管理对象信息模型生成网络子切片管理对象实例；
其中，所述网络子切片管理对象的信息模型包括如下属性的至少一个：第二网络服务实例标识、子网标识；其中，所述第二网络服务实例标识用于表示网络子切片实例与网络服务实例之间的对应关系；所述子网标识用于表示网络子切片实例与子网之间的对应关系；或，
所述网络子切片管理对象的信息模型包括如下属性：实例类型标识，所述实例类型标识用于标识子网实例表示的是子网实例还是网络子切片实例；或，
所述网络子切片管理对象的信息模型包括如下属性的至少一个：第二网络服务实例标识、实例类型标识；其中，所述第二网络服务实例标识用于表示网络子切片实例与网络服务实例之间的对应关系；所述子网标识用于表示网络子切片实例与子网之间的对应关系；所述实例类型标识用于标识子网实例表示的是子网实例还是网络子切片实例。
本公开实施例中，管理对象的信息模型包括网络切片管理对象信息模型；
所述管理功能单元包括：网络切片管理功能模块，用于根据网络切片管理对象信息模型，创建网络切片管理对象实例；
所述网络切片管理对象信息模型包括如下属性的至少一个：切片唯一标识、第一网络服务实例标识；其中，所述第一网络服务实例标识用于表示网络切片实例与网络服务实例之间的对应关系；
所述网络切片管理对象信息模型还包括可选属性：子网标识；其中，所述子网标识用于表示根据所述网络切片管理对象信息模型创建的实例为网络子切片实例。
本公开实施例中，在子网管理对象信息模型用于实现网络切片管理对象信息模型时，
所述网络切片管理功能模块根据子网管理对象信息模型生成网络切片管理对象实例；
其中，所述过子网管理对象信息模型包括可选属性：实例类型标识；其中，所述实例类型标识用于标识子网实例表示的是子网实例还是网络切片实例。
本公开实施例中，所述根据建立的管理对象的信息模型，执行管理对象的实例化包括：
网络切片管理功能模块NSMF通过编排器NFVO建立管理对象对应的网络切片实例；
在网络切片包括子切片的情况下，NSMF通过网络子切片管理功能模块NSSMF建立管理对象对应的网络子切片实例。
基于与上述实施例相同或相似的构思，本公开实施例还提供一种终端，包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现本公开实施例提供的任一网络管理方法的处理。
需要说明的是，以上所述的实施例仅是为了便于本领域的技术人员理解而已，并不用于限制本公开的保护范围，在不脱离本公开的发明构思的前提下，本领域技术人员对本公开所做出的任何显而易见的替换和改进等均在本公开的保护范围之内。
工业实用性
本公开适用于网络通信领域，用以克服现有移动网络管理技术中还没有在采用网络切片技术的背景下对网络切片及子切片管理对象进行建模的方案的问题，通过提出一种网络切片及子切片管理对象的建模方法和网络管理方法，为解决上述问题提供一种解决方案。

Claims (12)

  1. 一种网络管理方法，包括：
    建立管理对象的信息模型；所述管理对象的信息模型用于网络切片的管理；
    根据建立的管理对象的信息模型，执行管理对象的实例化。
  2. 根据权利要求1所述的网络管理方法，其中，所述建立管理对象的信息模型包括如下内容的至少一项：
    创建网络切片管理对象信息模型；
    创建网络子切片管理对象信息模型。
  3. 根据权利要求2所述的网络管理方法，其中，
    所述网络切片管理对象信息模型包括如下属性的至少一个：切片唯一标识、第一网络服务实例标识；其中，所述第一网络服务实例标识用于表示网络切片实例与网络服务实例之间的对应关系。
  4. 根据权利要求2所述的网络管理方法，其中，
    所述网络子切片管理对象信息模型包括如下属性的至少一个：子切片唯一标识、第二网络服务实例标识；其中，所述第二网络服务实例标识用于表示网络子切片实例与网络服务实例之间的对应关系。
  5. 根据权利要求4所述的网络管理方法，其中，
    所述网络子切片管理对象信息模型还包括如下属性：子网标识；所述子网标识用于表示网络子切片实例与子网之间的对应关系。
  6. 根据权利要求2所述的网络管理方法，其中，
    所述网络子切片管理对象信息模型是通过子网管理对象信息模型实现的；
    在子网管理对象信息模型还用于实现网络子切片管理对象信息模型时，
    所述网络子切片管理对象的信息模型包括如下属性的至少一个：第二网络服务实例标识、子网标识；其中，所述第二网络服务实例标识用于表示网络子切片实例与网络服务实例之间的对应关系；所述子网标识用于表示网络子切片实例与子网之间的对应关系；或，所述网络子切片管理对象的信息模型包括如下属性：实例类型标识，所述实例类型标识用于标识子网实例表示的是子网实例还是网络子切片实例；或，
    所述网络子切片管理对象的信息模型包括如下属性的至少一个：第二网络服务实例标识、实例类型标识；其中，所述第二网络服务实例标识用于表示网络子切片实例与网络服务实例之间的对应关系；所述子网标识用于表示网络子切片实例与子网之间的对应关系；所述实例类型标识用于标识子网实例表示的是子网实例还是网络子切片实例。
  7. 根据权利要求1所述的网络管理方法，其中，所述建立管理对象的信息模型包括：
    创建网络切片管理对象信息模型；
    所述网络切片管理对象信息模型包括如下属性的至少一个：切片唯一标识、第一网络服务实例标识；其中，所述第一网络服务实例标识用于表示网络切片实例与网络服务实例 之间的对应关系；
    所述网络切片管理对象信息模型还包括可选属性：子网标识；其中，所述子网标识用于表示根据所述网络切片管理对象信息模型创建的实例为网络子切片实例。
  8. 根据权利要求7所述的网络管理方法，其中，所述建立管理对象的信息模型包括：
    所述网络切片管理对象信息模型是通过子网管理对象信息模型实现的；
    所述过子网管理对象信息模型包括可选属性：实例类型标识；其中，所述实例类型标识用于标识子网实例表示的是子网实例还是网络切片实例。
  9. 根据权利要求1～8中任一项所述的网络管理方法，其中，
    所述根据建立的管理对象的信息模型，执行管理对象的实例化包括：
    网络切片管理功能模块NSMF通过编排器NFVO建立管理对象对应的网络切片实例；
    在网络切片包括子切片的情况下，NSMF通过网络子切片管理功能模块NSSMF建立管理对象对应的网络子切片实例。
  10. 一种网络管理系统，包括：
    存储单元，设置为存储建立的管理对象的信息模型；所述管理对象的信息模型用于网络切片的管理；
    管理功能单元，设置为所述管理对象的信息模型用于网络切片的管理。
  11. 根据权利要求10所述的网络管理系统，其中，管理对象的信息模型包括网络切片管理对象信息模型和网络子切片管理对象信息模型中的至少一个；
    所述管理功能单元包括如下模块的至少一个：
    网络切片管理功能模块，设置为根据网络切片管理对象信息模型，创建网络切片管理对象实例；
    网络子切片管理功能模块，设置为根据网络子切片管理对象信息模型，创建网络子切片管理对象实例。
  12. 一种终端，包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，其中，所述处理器执行所述计算机程序时实现如权利要求1至9中任一权利要求所述的方法的处理。
PCT/CN2018/102345 2017-10-12 2018-08-24 一种网络方法和系统、及终端 WO2019072033A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710949373.7A CN109660379B (zh) 2017-10-12 2017-10-12 一种网络方法和系统、及终端
CN201710949373.7 2017-10-12

Publications (1)

Publication Number Publication Date
WO2019072033A1 true WO2019072033A1 (zh) 2019-04-18

Family

ID=66101248

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/102345 WO2019072033A1 (zh) 2017-10-12 2018-08-24 一种网络方法和系统、及终端

Country Status (2)

Country Link
CN (1) CN109660379B (zh)
WO (1) WO2019072033A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110457412A (zh) * 2019-07-12 2019-11-15 中航物业管理有限公司 一种实现智慧物业的项目对象标准实例化方法
CN114666221A (zh) * 2020-12-07 2022-06-24 中兴通讯股份有限公司 网络切片子网运维管理方法、装置、系统、设备及介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101621814A (zh) * 2009-05-11 2010-01-06 中兴通讯股份有限公司 一种ip多媒体子系统业务及网络管理方法与系统
CN106792739A (zh) * 2016-11-17 2017-05-31 北京邮电大学 网络切片方法、装置和设备
CN107222318A (zh) * 2016-03-21 2017-09-29 中兴通讯股份有限公司 一种网元的性能数据处理方法及装置和nms
WO2017166148A1 (zh) * 2016-03-31 2017-10-05 华为技术有限公司 一种数据传输的方法和相关设备

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106550410B (zh) * 2015-09-17 2020-07-07 华为技术有限公司 一种通信控制方法和控制器、用户设备、相关装置
US10129108B2 (en) * 2015-11-13 2018-11-13 Huawei Technologies Co., Ltd. System and methods for network management and orchestration for network slicing

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101621814A (zh) * 2009-05-11 2010-01-06 中兴通讯股份有限公司 一种ip多媒体子系统业务及网络管理方法与系统
CN107222318A (zh) * 2016-03-21 2017-09-29 中兴通讯股份有限公司 一种网元的性能数据处理方法及装置和nms
WO2017166148A1 (zh) * 2016-03-31 2017-10-05 华为技术有限公司 一种数据传输的方法和相关设备
CN106792739A (zh) * 2016-11-17 2017-05-31 北京邮电大学 网络切片方法、装置和设备

Also Published As

Publication number Publication date
CN109660379B (zh) 2022-04-05
CN109660379A (zh) 2019-04-19

Similar Documents

Publication Publication Date Title
US11611487B2 (en) Model driven process for automated deployment of domain 2.0 virtualized services and applications on cloud infrastructure
US11296957B2 (en) Network slice management method, unit, and system
US11108653B2 (en) Network service management method, related apparatus, and system
WO2018024059A1 (zh) 一种虚拟化网络中业务部署的方法和装置
US10917294B2 (en) Network function instance management method and related device
US10924966B2 (en) Management method, management unit, and system
US20190261186A1 (en) Network Slice Management Method, Management Unit, and System
US20170373931A1 (en) Method for updating network service descriptor nsd and apparatus
WO2018072503A1 (zh) 软件修改的发起方法、发布元数据的方法及装置
WO2017148326A1 (zh) 一种资源管理方法和装置
CN111245634B (zh) 一种虚拟化管理方法及装置
WO2019233124A1 (zh) 一种网络切片的创建方法及管理编排系统
CN109964507A (zh) 网络功能的管理方法、管理单元及系统
WO2019085999A1 (zh) 网元管理方法和装置
WO2019072033A1 (zh) 一种网络方法和系统、及终端
US20230342183A1 (en) Management method and apparatus for container cluster
CN113342456A (zh) 一种连接方法、装置、设备和存储介质
US20220350637A1 (en) Virtual machine deployment method and related apparatus
US20190068449A1 (en) Extending a virtual local area network across a layer 2 data center interconnect
CN112889247A (zh) Vnf服务实例化方法及装置
EP4224332A1 (en) Data stream mirroring method and device
CN115189995A (zh) Kubernetes环境下多集群网络联邦通信建立方法、设备及存储介质
CN117118927A (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: 18866495

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 08/09/2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18866495

Country of ref document: EP

Kind code of ref document: A1