WO2019029636A1 - 一种网络实例管理方法及相关设备 - Google Patents

一种网络实例管理方法及相关设备 Download PDF

Info

Publication number
WO2019029636A1
WO2019029636A1 PCT/CN2018/099683 CN2018099683W WO2019029636A1 WO 2019029636 A1 WO2019029636 A1 WO 2019029636A1 CN 2018099683 W CN2018099683 W CN 2018099683W WO 2019029636 A1 WO2019029636 A1 WO 2019029636A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
instance
request
threshold
management
Prior art date
Application number
PCT/CN2018/099683
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 WO2019029636A1 publication Critical patent/WO2019029636A1/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/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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • 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/044—Network management architectures or arrangements comprising hierarchical management structures
    • 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/06—Management of faults, events, alarms or notifications
    • H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • 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/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5009—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
    • H04L41/5012—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF] determining service availability, e.g. which services are available at a certain point in time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/20—Arrangements for monitoring or testing data switching networks the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/06—Generation of reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/16—Threshold monitoring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic

Definitions

  • the embodiments of the present invention relate to the field of communications technologies, and in particular, to a network instance management method and related devices.
  • the development of wireless communication technology is changing with each passing day.
  • wireless communication services will be ever-changing and in various forms.
  • the 5th Generation (5G) communication network will be oriented to different application scenarios, such as ultra high definition video, virtual reality, large-scale Internet of Things, car networking and so on. Different scenarios have different requirements for network mobility, security, delay, reliability, and even billing methods.
  • the future network needs to have the ability to be developed on demand, that is, to enable flexible configuration of network slicing, cutting the physical network into multiple virtual network slices, each virtual network slice facing Different application scenarios.
  • a network slice satisfies the communication service requirements of a certain class or a use case.
  • the entire 5G communication network consists of a large number of network slices that meet different service requirements.
  • network slicing is created and applied in the form of a network instance. Therefore, in a 5G network system, how to implement management of a network instance is a technical problem that needs to be solved currently.
  • the embodiment of the invention provides a network instance management method and related devices, which can flexibly manage the network instance.
  • an embodiment of the present invention provides a network instance management method, which is applied to a first network device side.
  • the method includes: the first network device receives a first management request from the second network device, the first management request is used to indicate management of the network instance, the first management request includes a parameter of the execution condition, and the parameter is related to the network instance.
  • the first network device is a network slice management function device, and the second network device is a communication service management function device.
  • the first network device is a network slice subnet management function device, and the second network device is a network slice management function device.
  • the first network device executes the first management request when the execution condition is satisfied.
  • an embodiment of the present invention provides another network instance management method, which is applied to a second network device side.
  • the method includes the second network device determining a first management request, the first management request including a parameter of an execution condition, the parameter being related to the network instance.
  • the second network device sends a first management request to the first network device, where the first management request is used to instruct the first network device to perform the first management request for the network instance when the execution condition is met.
  • the first network device is a network slice management function device
  • the second network device is a communication service management function device.
  • the first network device is a network slice subnet management function device
  • the second network device is a network slice management function device.
  • the second network device may carry the parameter of the execution condition in the first management request that is sent, so that the first network device receives the first management request, and then, when the execution condition is met, The instance executes the first management request, thereby implementing flexible management of the network instance.
  • the foregoing network instance includes at least one of the following: a network slice instance, a network slice subnet instance, and a network function.
  • the foregoing first management request includes any one of the following: a create request, a modify request, a configuration request, a final request, an activation request, a logout request, a performance measurement task request, and a performance. Threshold monitoring request and alarm information reporting request.
  • the embodiments of the present invention are applicable to management, such as creating, modifying, configuring, terminating, activating, deregistering, performing performance measurement, performance threshold monitoring, and alarming information reporting, and can manage the entire life cycle of the network instance.
  • the foregoing parameters include at least one of: a threshold number of users using a network instance, a threshold number of packet data unit sessions run by a network instance, and a traffic used by a user using the network instance.
  • the threshold, the service level protocol parameter threshold of the network instance, the QoS parameter threshold of the network instance, the key performance indicator parameter threshold of the network instance, the identifier of the third-party management module, and the average moving speed of the user using the network instance in the geographic location range of the unit The threshold, the number of cell handovers that the user using the network instance has, the number of times the cell is switched, the fault alarm type of the network instance, the fault alarm severity of the network instance, the fault event identifier of the network instance, and the resource utilization threshold of the network instance.
  • the parameters of the execution conditions that can be carried in the management request in the embodiment of the present invention are more types, wider in scope and higher in complexity.
  • the foregoing execution condition satisfies when at least one of the following is satisfied: the number of users using the network instance reaches the number of users threshold, and the number of packet data unit sessions run by the network instance reaches the grouping The threshold of the number of data unit sessions, the traffic threshold accumulated in the user unit time of the network instance reaches the traffic threshold used by the user, the service level protocol parameter of the network instance reaches the service level protocol parameter threshold, and the service quality parameter of the network instance reaches the quality of service parameter.
  • the average moving speed reaches the average moving speed threshold, the number of cell switchings that occur when the user using the network instance reaches the cell switching time reaches the threshold number of cell handovers, and the first network device receives the same as the fault alarm type identifier.
  • the first network device receives the alarm information that is consistent with the fault alarm severity identifier, the fault event corresponding to the first network device fault event identifier, the resource utilization of the network instance reaches the resource utilization threshold, and the first network device performs After the other management request identifies the corresponding management request, the execution time arrives, and the execution waiting time is reached from the time when the first network device receives the first management request.
  • the number of users using the network instance threshold includes using an upper limit of the number of users of the network instance or using a lower limit of the number of users of the network instance.
  • the threshold number of packet data unit sessions run by the network instance includes an upper limit value of the number of packet data unit sessions run by the network instance or a lower limit value of the number of packet data unit sessions run by the network instance.
  • the traffic thresholds used by users who use network instances include the traffic upper limit used by users who use the network instance or the traffic lower limit used by users who use the network instance.
  • the service level protocol parameter threshold of the network instance includes the service level protocol parameter upper limit value of the network instance or the service level protocol parameter lower limit value of the network instance.
  • the QoS parameter threshold of the network instance includes the QoS parameter upper limit of the network instance or the QoS parameter lower limit of the network instance.
  • the key performance indicator parameter threshold of the network instance includes the upper limit value of the key performance indicator parameter of the network instance or the lower limit value of the key performance indicator parameter of the network instance.
  • the average moving speed threshold of the user using the network instance in the unit geographical location interval includes the average moving speed upper limit value of the user using the network instance in the unit geographical distance interval or the average moving of the user using the network instance in the unit geographical distance interval. Lower speed limit.
  • the threshold for the number of cell handovers that occur when a user using a network instance occurs in a unit time includes the upper limit of the number of cell handovers that the user using the network instance uses per unit time or the lower limit of the number of cell handovers that the user using the network instance uses per unit time. value.
  • the resource utilization threshold of the network instance includes the resource utilization upper limit of the network instance or the resource utilization lower limit of the network instance.
  • the number of users using the network instance reaches the number of users threshold includes: the number of users using the network instance is greater than or equal to the upper limit of the number of users, or less than or equal to the user.
  • the number of packet data unit sessions run by the network instance reaches the packet data unit session number threshold, including: the number of packet data unit sessions run by the network instance is greater than or equal to the upper limit value of the number of packet data unit sessions, or less than or equal to the number of packet data unit sessions. Limit.
  • the traffic threshold used by the user in the user unit time of the network instance reaches the traffic threshold used by the user.
  • the traffic threshold accumulated in the user unit time of the network instance is greater than or equal to the traffic upper limit value used by the user, or less than or equal to The lower limit of the traffic used by the user.
  • the service level protocol parameter of the network instance reaches the service level protocol parameter threshold, including: the service level protocol parameter of the network instance is greater than or equal to the service level agreement parameter upper limit value, or is less than or equal to the service level agreement parameter lower limit value.
  • the service quality parameter of the network instance reaches the service quality parameter threshold, where the service quality parameter of the network instance is greater than or equal to the upper limit value of the service quality parameter, or is less than or equal to the lower limit value of the service quality parameter.
  • the key performance indicator parameters of the network instance reach the key performance indicator parameter thresholds, including: the key performance indicator parameter of the network instance is greater than or equal to the upper limit value of the key performance indicator parameter, or is less than or equal to the lower limit value of the key performance indicator parameter.
  • the average moving speed of the user using the network instance in the geographical interval of the unit reaches the average moving speed threshold includes: the average moving speed of the user using the network instance in the unit geographical interval is greater than or equal to the upper moving speed upper limit, or less than Or equal to the average moving speed lower limit.
  • the number of cell handovers that occur when the user using the network instance reaches the cell handover time per unit time includes: the number of cell handovers that occur when the user using the network instance is greater than or equal to the number of cell handovers generated, or , less than or equal to the lower limit of the number of cell handovers that occur.
  • the resource utilization threshold of the network instance reaches the resource utilization threshold, including: the resource utilization of the network instance is greater than or equal to the resource utilization upper limit, or is less than or equal to the resource utilization lower limit.
  • the method further includes: determining, by the first network device, the first management request Whether it is executable. If yes, the first network device performs the step of the first management request when the execution condition is met.
  • an embodiment of the present invention provides a network device, where the network device is a first network device.
  • the first network device includes a module or unit for performing the network instance management method described in the first aspect above.
  • an embodiment of the present invention provides another network device, where the network device is a second network device.
  • the second network device includes a module or unit for performing the network instance management method described in the second aspect above.
  • an embodiment of the present invention provides another network device, where the network device is a first network device.
  • the first network device includes a processor, a transceiver, and a memory.
  • the processor is configured to invoke the network instance management program code stored in the memory to execute the network instance management method provided in the first aspect.
  • an embodiment of the present invention provides another network device, where the network device is a second network device.
  • the second network device includes a processor, a transceiver, and a memory.
  • the processor is configured to invoke the network instance management program code stored in the memory to execute the network instance management method provided in the second aspect.
  • an embodiment of the present invention provides a communication system, including: a first network device and a second network device.
  • the first network device is the first network device according to the third aspect or the fifth aspect
  • the second network device is the second network device according to the fourth aspect or the sixth aspect.
  • an embodiment of the present invention provides a computer storage medium, configured to store computer software program instructions used by the first network device according to the first aspect, where the program instructions are used by the first network device.
  • the first network device is caused to perform the method as described in the first aspect above when executed.
  • the embodiment of the present invention provides another computer storage medium, configured to store computer software program instructions used by the second network device according to the second aspect, where the program instructions are used by the second network.
  • the device when executed, causes the second network device to perform the method as described in the second aspect above.
  • an embodiment of the present invention provides a computer program, where the program includes computer software program instructions, when the program instruction is executed by the first network device, causing the first network device to perform the first aspect as described above Said method.
  • an embodiment of the present invention provides another computer program, the program comprising computer software program instructions, when the program instruction is executed by the second network device, causing the second network device to perform the foregoing The method described in the two aspects.
  • FIG. 1 is a schematic structural diagram of a network system according to an embodiment of the present invention.
  • FIG. 2 is a schematic flowchart of a network instance management method according to an embodiment of the present invention.
  • FIG. 3 is a schematic structural diagram of a network device according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of another network device according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of another network device according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of another network device according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of a device according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of another apparatus according to an embodiment of the present invention.
  • the network instance described in the embodiment of the present invention includes at least one of a network slice instance, a network slice subnet instance, and a network function.
  • Network Slice refers to different logical networks customized according to different service requirements.
  • the network slice can be a complete end-to-end network including terminals, access networks, transport networks, core networks and application servers, which can provide complete telecommunication services and have certain network capabilities.
  • the network slice may also be any combination of the above terminal, access network, transport network, core network, and application server.
  • Network Slice Instance is an instantiation of NS, that is, a real-running logical network that meets certain network characteristics or service requirements.
  • a network slice instance can provide one or more services.
  • the network slice instance can be created by the network slice management function device.
  • a network slice management function device can create multiple network slice instances and manage them at the same time, including performance monitoring and fault management during the operation of the network slice instance. When multiple network slice instances coexist, some network resources and network functions can be shared between network slice instances.
  • a network slice instance can be created from a network slice template or not from a network slice template.
  • a complete network slicing instance can provide complete end-to-end network services, and the network slicing instances can be Network Slice Subnet Instance (NSSI) and/or network functions.
  • Network functions may include physical network functions and/or virtual network functions. The following are collectively referred to as physical network functions and/or virtual network functions as network functions.
  • a network slice instance can be divided into several network slice subnet instances to facilitate network management system management.
  • the network slice subnet instance may not need to provide a complete network service end-to-end.
  • the network slice subnet instance may be a network function component set of the same device vendor in the network slice instance, or may be a collection of network functions divided by domain. For example, a core network network slice subnet instance, an access network network slice subnet instance, or a collection of other ways, such as a deployment location.
  • a network sliced subnet instance can be shared by multiple network slice instances.
  • a network slice instance may consist of several network slice subnet instances, each network slice subnet instance consisting of several network functions and/or several network slice subnet instances.
  • a network slice instance can consist of several network slice subnet instances and network functions that are not partitioned into network slice subnet instances.
  • a network slice instance can also consist of only a few network functions.
  • Network function is a processing function in the network that defines functional behavior and interfaces.
  • Network functions can be implemented by dedicated hardware, by running software on dedicated hardware, or as virtual functions on a common hardware platform. Therefore, from the perspective of implementation, network functions can be divided into physical network functions and virtual network functions. From the perspective of use, network functions can be divided into exclusive network functions and shared network functions. Specifically, for multiple network slice instances/network slice subnet instances, different network functions can be used independently. This network function is called a dedicated network function, and can also share the same network function. For sharing network features.
  • FIG. 1 is a schematic structural diagram of a network system according to an embodiment of the present invention.
  • the network system 100 includes: a Communication Service Management Function (CSMF) device 101, a Network Slice Management Functio (NSMF) device 102, and a network slice subnet management function (Network Slice). Subnet Management Function, NSSMF) device 103.
  • CSMF Communication Service Management Function
  • NSMF Network Slice Management Functio
  • NSSMF Network Slice subnet management function
  • the communication service management function device 101 is mainly responsible for converting the communication service requirements of the operator and/or the third party customer into the requirements for the network slice, and performing the network slice management function through the interface with the network slice management function device 102.
  • the device 102 sends a management request for the network instance (such as creating, modifying, configuring, terminating, activating, deregistering a network slice instance request, a performance measurement task request, a performance threshold monitoring request, and an alarm information reporting request).
  • the communication service management function device 101 is further configured to acquire management data (such as performance data, fault data, and the like) of the network instance from the network slice management function device 102, and generate management data of the communication service running on the network slice instance.
  • the fault data includes the alarm data. In the embodiment of the present invention, the alarm data is equal to the alarm information.
  • the communication service management function device 101 can also receive subscription requirements of the management data of the network slice management data and/or the communication service by the operator and/or the third party customer, and the like.
  • the network slice management function device 102 is mainly responsible for receiving the network slice instance management request sent by the communication service management function device 101.
  • the network slice management function device 102 manages the life cycle, performance, faults, and the like of the network slice instance (hereinafter, the life cycle, performance, and fault management are simply referred to as management), and the composition of the network slice instance is arranged, and the requirements for decomposing the network slice instance are
  • a network slicing subnet instance and/or network function requires a network slicing subnet instance management request to be sent to each network slicing subnet management function device 103.
  • the network slice subnet management function device 103 is mainly responsible for receiving the network slice subnet instance and/or the network function management request sent by the network slice management function device 102, managing the network slice subnet instance, and compiling the network slice subnet instance.
  • the requirement to decompose the network slice subnet instance is the requirement of each network function and/or nested network slice subnet instance, and the nested network slice subnet instance management request may be sent to the other network slice subnet management function device 103.
  • Nested means that a network sliced subnet instance can consist of one or more network sliced subnet instances.
  • the communication service management function device 101 and the network slice management function device 102 have an interface 1, and the network slice management function device 102 and the network slice subnet management function device 103 have an interface 2.
  • the interface 1 is used by the communication service management function device 101 to send a network slice instance management request to the network slice management function device 102.
  • the interface 1 is also used by the network slice management function device 102 to feed back the management request execution result to the communication service management function device 101.
  • the interface 1 is also used by the network slice management function device 102 to report management data to the communication service management function device 101.
  • the interface 2 is used by the network slice management function device 102 to send a network slice subnet instance management request and/or a network function management request to the network slice subnet management function device 103.
  • the interface 2 is also used by the network slice subnet management function device 103 to feed back the management request execution result to the network slice management function device 102.
  • the interface 2 is also used by the network slice management function device 103 to report management data to the network slice management function device 102.
  • the communication service management function device 101, the network slice management function device 102, the network slice subnet management function device 103, the interface 1 and the interface 2 may have other names, which are not specifically limited in the embodiment of the present invention.
  • the communication service management function device 101, the network slice management function device 102, and the network slice subnet management function device 103 are all named according to functions.
  • the communication service management function device 101 may be provided.
  • the network slice management function device 102 may be any device having a network slice management function
  • the network slice subnet management function device 103 may be any device having a network slice subnet management function.
  • the communication architecture shown in Figure 1 is a hierarchical network instance management system architecture.
  • the following describes the management requests involved in the creation request, the modification request, the configuration request, the termination request, the activation request, the logout request, the performance measurement task request, the performance threshold monitoring request, and the alarm information reporting request.
  • the create request includes a create NSI request, a create NSSI request, and a create NF request.
  • the modification request includes a modify NSI request, a modify NSSI request, and a modify NF request.
  • Configuration requests include configuring a configure NSI request, configuring a network NMS request, and configuring a NF request.
  • the termination request includes terminating the NSI request, terminating the NSSI request, and terminating the NF request.
  • the activation request includes an activate NSI request, an activate NSSI request, and an activate NF request.
  • the logout request includes a de-activate NSI request, a de-activate NSSI request, and a de-activate NF request.
  • the performance measurement task request includes a network slice instance performance measurement job request (NSI performance measurement job request), a network slice subnet instance performance measurement job request, and a network function measurement job request (NF performance measurement job request).
  • the performance threshold monitoring request includes a network slice instance performance threshold monitoring request (NSI threshold monitoring request), a network slice subnet instance performance threshold monitoring request (NSSI threshold monitoring request), and a network function performance threshold monitoring request (NF threshold monitoring request).
  • the alarm information reporting request includes a NSI get alarm information request, a NSSI get alarm information request, and a network function alarm information request (NF get alarm information request).
  • the network slice instance request, the network slice instance request, the network slice instance request, the network slice instance request, the network slice instance request, the network slice instance request, the network slice instance request, the network slice instance performance measurement task request, and the network slice instance performance are created.
  • the threshold monitoring request and the network snippet instance alarm information reporting request are sent by the communication service management function device 101 to the network slice management function device 102, and are used to request the network slice management function device 102 to perform corresponding management on the network slice instance.
  • the subnet instance performance measurement task request, the network slice subnet instance performance threshold monitoring request, and the network slice subnet instance alarm information report request are sent by the network slice management function device 102 to the network slice subnet management function device 103 for network slice.
  • the subnet management function device 103 manages the network slice subnet instance.
  • the network slice management function device 102 sends the network slice management function to the network slice subnet management function device 103 for managing the network function.
  • a create network slice instance request is used to request the network slice management function device 102 to create a network slice instance. For example, create a network slice subnet instance and/or network function, or reuse an existing network slice subnet instance and/or network function.
  • the creation of the network slice instance request may carry a performance indicator, and the network slice management function device 102 creates a network slice instance that satisfies the performance indicator.
  • the modify network slice instance request is used to request the network slice management function device 102 to modify the network slice instance.
  • Modifying the network slice instance request may include increasing the capacity of the network slice instance, reducing the capacity of the network slice instance, changing the network function/network slice subnet instance topology in the network slice instance, and adding/deleting network functions in the network slice instance.
  • Network slicing the subnet instance updating the software version of the network features that make up the network slicing instance, and so on.
  • the identifier of the network slice instance that can be carried in the network slice instance request that is, the NSI ID, is used to indicate that the network slice management function device 102 performs corresponding modification on the network slice instance corresponding to the NSI ID.
  • a configuration network slice instance request is used to request the network slice management function device 102 to configure a network slice instance.
  • the network slice instance is an Access and Mobility Management Function (AMF)
  • AMF Access and Mobility Management Function
  • S Single Network Slice Selection Assistant Information
  • -NSSAI Single Network Slice Selection Assistant Information
  • UDM Unified Data Management
  • NRF Network Repository Function
  • the configuration involves all network functions and/or network slice subnet instances that make up the network slice instance.
  • the network sharding instance request may be configured to carry the identifier of the network sharding instance, that is, the NSI ID, to indicate that the network sharding management function device 102 performs corresponding configuration on the network snippet instance corresponding to the NSI ID.
  • the terminating network slice instance request is used to request the network slice management function device 102 to terminate the use of the network slice instance. For example, the resources occupied by the network slice instance are released, and the related information of the network slice instance is deleted.
  • the network slice instance instance may carry the identifier of the network slice instance, that is, the NSI ID, to indicate that the network slice management function device 102 terminates the network slice instance corresponding to the NSI ID, that is, the network slice instance is no longer used.
  • the activate network slice instance request is used to request the network slice management function device 102 to activate the use of the network slice instance.
  • the identifier of the network slice instance that can be carried in the network slice instance request that is, the NSI ID, is used to instruct the network slice management function device 102 to activate the network slice instance corresponding to the NSI ID, that is, to continue to use the network slice instance.
  • the logout network slice instance request is used to request the network slice management function device 102 to log out of the network slice instance.
  • the network slice instance is suspended, that is, the network resource occupied by the network slice instance is not released, and information about the network slice instance is saved.
  • the identifier of the network slice instance that can be carried in the network slice instance is used to instruct the network slice management function device 102 to log off the network slice instance corresponding to the NSI ID, that is, to suspend the use of the network slice instance.
  • the network slice instance performance measurement task request is used to request the network slice management function device 102 to measure the performance of the network slice instance.
  • the network slice instance performance measurement task request may carry an identifier of a network slice instance, that is, an NSI ID, for indicating that the network slice management function device 102 measures the performance of the network slice instance corresponding to the NSI ID.
  • the network slice instance performance measurement task request may also carry an identifier of the performance indicator, which is used to indicate that the performance indicator is measured.
  • the performance indicators may be delay, number of users, number of Packet Data Units (PDUs) sessions, bandwidth, resource utilization, and the like.
  • the network slice management function device 102 can report the measured performance data to the communication service management function device 101.
  • the network slice instance performance threshold monitoring request is used to request the network slice management function device 102 to monitor the performance threshold of the network slice instance, that is, to monitor whether the performance of the network slice instance reaches a preset threshold.
  • the network slice instance performance threshold monitoring request may carry an identifier of a network slice instance, that is, an NSI ID, to indicate that the network slice management function device 102 monitors the performance threshold of the network slice instance corresponding to the NSI ID.
  • the network slice instance performance threshold monitoring request may also carry an identifier of the performance indicator, which is used to indicate the monitored performance indicator.
  • the network slice instance performance threshold monitoring request may also carry a specific threshold, such as an upper threshold and a lower threshold.
  • the network slice instance alarm information report request is used to request the network slice management function device 102 to report the alarm information of the network slice instance.
  • the network snippet instance alarm information reporting request may carry the identifier of a network sharding instance, that is, the NSI ID, and the network snippet management function device 102 may report the alarm information of the network snippet instance corresponding to the NSI ID to the communication service management function device. 101.
  • the network snippet instance alarm information reporting request may also carry a filter to limit/filter the alarm information to be reported.
  • the Create Network Tile Subnet Instance Request is used to request the Network Slice Subnet Management function device 103 to create a network slice subnet instance. For example, create a network slice subnet instance and/or network function, or reuse an existing network slice subnet instance and/or network function.
  • the network slice subnet instance request may carry a performance indicator, and the network slice subnet management function device 103 creates a network slice subnet instance that satisfies the performance indicator.
  • the modify network slice subnet instance request is used to request the network slice subnet management function device 103 to modify the network slice subnet instance.
  • Modifying the network slice subnet instance request may include increasing the capacity of the network slice subnet instance, reducing the capacity of the network slice subnet instance, and changing the network function in the network slice subnet instance/the topology between the nested network slice subnet instances.
  • Add/delete network functions in the network slicing subnet instance/nested network slicing subnet instance update the software version of the network function that constitutes the network slicing subnet instance, and so on.
  • the identifier of the network slice subnet instance that can be carried in the network slice subnet instance request is used to indicate that the network slice subnet management function device 103 performs corresponding modification on the network slice subnet instance corresponding to the NSSI ID.
  • the Configure Network Slicing Subnet Instance Request is used to request the Network Slicing Subnet Management function device 103 to configure a network slicing subnet instance.
  • a network slicing subnet instance For example, when the network slice subnet instance is an access and mobility management function, configure its identity and configure a single network slice selection support information it supports. User subscription information is configured when the network slice subnet instance is unified data management.
  • the network slice subnet instance is a network function library, configure newly created network function information, and the like.
  • the configuration involves all network functions and/or network slice subnet instances that make up the network slice subnet instance.
  • the network slice subnet instance request may be configured to carry an identifier of a network slice subnet instance, that is, an NSSI ID, to indicate that the network slice subnet management function device 103 performs corresponding configuration on the network slice subnet instance corresponding to the NSSI ID.
  • the terminating network slice subnet instance request is used to request the network slice subnet management function device 103 to terminate the use of the network slice subnet instance. For example, the resources occupied by the network slicing subnet instance are released, and the information about the network slicing subnet instance is deleted.
  • the termination of the network slice subnet instance request may carry the identifier of the network slice subnet instance, that is, the NSSI ID, to indicate that the network slice subnet management function device 103 terminates the network slice subnet instance corresponding to the NSSI ID, that is, no longer Use this network to slice a subnet instance.
  • the Activate Network Slice Subnet Instance Request is used to request the network slice subnet management function device 103 to activate the use of the network slice subnet instance.
  • the identifier of the network slice subnet instance that can be carried in the network slice subnet instance request that is, the NSSI ID, is used to instruct the network slice subnet management function device 103 to activate the network slice subnet instance corresponding to the NSSI ID, that is, continue Use this network to slice a subnet instance.
  • the logout network slice subnet instance request is used to request the network slice subnet management function device 103 to log off the network slice subnet instance. For example, suspend the use of the network slicing subnet instance, but does not release the network resources occupied by the network slicing subnet instance, and save information about the network slicing subnet instance.
  • the identifier of the network slice subnet instance that can be carried in the network slice subnet instance can be carried, that is, the NSSI ID is used to indicate that the network slice subnet management function device 103 logs off the network slice subnet instance corresponding to the NSSI ID, that is, pauses. Use this network to slice a subnet instance.
  • the network slice subnet instance performance measurement task request is used to request the network slice subnet management function device 103 to measure the performance of the network slice subnet instance.
  • the network slice subnet instance performance measurement task request may carry an identifier of a network slice subnet instance, that is, an NSSI ID, which is used to indicate the performance of the network slice subnet management function device 103 corresponding to the network slice subnet instance corresponding to the NSSI ID. Make measurements.
  • the network slice subnet instance performance measurement task request may also carry an identifier of the performance indicator, which is used to indicate that the performance indicator is measured. Examples of performance metrics may be latency, number of users, number of packet data unit sessions, bandwidth, resource utilization, and the like.
  • the network slice management function device 103 can report the measured performance data to the network slice management function device 102.
  • the network slice subnet instance performance threshold monitoring request is used to request the network slice subnet management function device 103 to monitor the performance threshold of the network slice subnet instance, that is, to monitor whether the performance of the network slice subnet instance reaches a preset threshold.
  • the network slice subnet instance performance threshold monitoring request may carry an identifier of a network slice subnet instance, that is, an NSSI ID, and is used to indicate that the network slice subnet management function device 103 performs performance on the network slice subnet instance corresponding to the NSSI ID.
  • the threshold is monitored.
  • the network slice subnet instance performance threshold monitoring request may also carry an identifier of the performance indicator, which is used to indicate the monitored performance indicator.
  • the network slice subnet instance performance threshold monitoring request may also carry a specific threshold, such as an upper threshold and a lower threshold.
  • a specific threshold such as an upper threshold and a lower threshold.
  • the network slice subnet instance alarm information report request is used to request the network slice subnet management function device 103 to report the alarm information of the network slice subnet instance.
  • the network slice subnet instance alarm information reporting request may carry an identifier of a network slice subnet instance, that is, an NSSI ID, and is used to instruct the network slice subnet management function device 103 to notify the network slice subnet instance corresponding to the NSSI ID.
  • the information is reported to the network slice management function device 102.
  • the network slice subnet instance alarm information reporting request may also carry a filter (filter) for limiting/filtering the alarm information to be reported.
  • the create network function request is used to request the network slice subnet management function device 103 to create a network function.
  • the creation of the network function request may carry the performance indicator, and the network slice subnet management function device 103 creates a network function that satisfies the performance indicator.
  • the modify network function request is used to request the network slice subnet management function device 103 to modify the network function.
  • Modifying the network function request may specifically include increasing the capacity/resource of the network function, reducing the capacity/resource of the network function, updating the software version of the network function, and the like.
  • the identifier of the network function that can be carried in the network function request that is, the NF ID, is used to indicate that the network slice subnet management function device 103 performs corresponding modification on the network function corresponding to the NF ID.
  • the configuration network function request is used to request the network slice subnet management function device 103 to configure the network function.
  • the network function is an access and mobility management function, configure its identity and configure a single network slice selection support information it supports.
  • Configure user subscription information when the network function is unified data management.
  • the network function is a network function library, configure newly created network function information and the like.
  • the network function request may be configured to carry a network function identifier, that is, an NF ID, for indicating that the network slice subnet management function device 103 is configured for the network function corresponding to the NF ID.
  • the terminate network function request is used to request the network slice subnet management function device 103 to terminate the use of the network function. For example, the resources occupied by the network function are released, and the related information of the network function is deleted.
  • the termination network function request may carry an identifier of a network function, that is, an NF ID, for indicating that the network slice subnet management function device 103 terminates the network function corresponding to the NF ID, that is, the network function is no longer used.
  • the activate network function request is used to request the network slice subnet management function device 103 to activate the use of the network function.
  • the activation network function request may carry an identifier of a certain network function, that is, an NF ID, for indicating that the network slice subnet management function device 103 activates the network function corresponding to the NF ID, that is, continues to use the network function.
  • the logout network function request is used to request the network slice subnet management function device 103 to log out of the network function. For example, suspend the use of the network function, but does not release the network resources occupied by the network function, and save information about the network function.
  • the hangout network function request may carry an identifier of a certain network function, that is, an NF ID, for indicating that the network slice subnet management function device 103 cancels the network function corresponding to the NF ID, that is, suspends the use of the network function.
  • the network function performance measurement task request is used to request the network slice subnet management function device 103 to measure the performance of the network function.
  • the network function performance measurement task request may carry an identifier of a network function, that is, an NF ID, for indicating that the network slice subnet management function device 103 measures the performance of the network function corresponding to the NF ID.
  • the network function performance measurement task request may further carry an identifier of the performance indicator, and is used to indicate that the performance indicator is measured. Examples of performance metrics may be latency, number of users, number of packet data unit sessions, bandwidth, resource utilization, and the like.
  • the network slice management function device 103 can report the measured performance data to the network slice management function device 102.
  • the network function performance threshold monitoring request is used to request the network slice subnet management function device 103 to monitor the performance threshold of the network function, that is, to monitor whether the performance of the network function reaches a preset threshold.
  • the network function performance threshold monitoring request may carry an identifier of a network function, that is, an NF ID, for indicating that the network slice subnet management function device 103 monitors the performance threshold of the network function corresponding to the NF ID.
  • the network function performance threshold monitoring request may also carry an identifier of the performance indicator, which is used to indicate the monitored performance indicator.
  • the network function performance threshold monitoring request may also carry a specific threshold, such as an upper threshold and a lower threshold.
  • the network function alarm information reporting request is used to request the network slice subnet management function device 103 to report the alarm information of the network function.
  • the network function alarm information reporting request may carry an identifier of a network function, that is, an NF ID, for indicating that the network slice subnet management function device 103 reports the alarm information of the network function corresponding to the NF ID to the network slice management function device 102.
  • the network function alarm information reporting request may also carry a filter to limit/filter the alarm information to be reported.
  • FIG. 2 is a flowchart of a network instance management method according to an embodiment of the present invention.
  • the network instance management method includes but is not limited to the following steps S201-S203.
  • the second network device determines a first management request, where the first management request includes a parameter of an execution condition, and the parameter is related to the network instance.
  • the second network device generates or acquires a first management request from another device.
  • the network instance includes at least one of the following: a network slice instance, a network slice subnet instance, and a network function.
  • the second network device sends a first management request to the first network device, where the first management request is used to indicate that the network instance is managed.
  • the embodiments of the present invention can be applied to at least the following two scenarios.
  • Scenario 1 The first network device is a network slice management function device, and the second network device is a communication service management function device. In this scenario, the network instance may specifically be a network slice instance.
  • Scenario 2 The first network device is a network slice subnet management function device, and the second network device is a network slice management function device. In this scenario, the network instance may specifically be a network slice subnet instance and/or a network function.
  • the two scenarios are described in detail below.
  • the communication service management function device sends a first management request to the network slice management function device, where the first management request is used to instruct the network slice management function device to manage the network slice instance.
  • the first management request includes any one of the following: creating a network slice instance request, modifying a network slice instance request, configuring a network slice instance request, terminating a network slice instance request, activating a network slice instance request, deregistering a network slice instance request, a network slice instance The performance measurement task request, the network slice instance performance threshold monitoring request, and the network slice instance alarm information report request.
  • the parameters of the execution conditions carried by different management requests may be the same or different.
  • the following describes the parameters of the execution conditions carried by each of the above various management requests.
  • the parameters for creating the execution condition carried in the network slice instance request include at least one of the following: an identifier of the third-party management module, other management request identifiers, execution time, and execution wait time.
  • the third-party management module may be a network management module of the client, and a direct interface exists between the third-party management module and the network slice management function device, or interacts with the network slice management function device through a security agent.
  • the network slice instance is requested to carry another management request identifier
  • the other management request may be a management request for terminating another network slice instance, and the network slice management function device needs to perform an action of creating a network slice instance after another network slice instance is terminated. .
  • the parameter for modifying the execution condition carried in the network slice instance request includes at least one of the following: the upper limit of the number of users using the network slice instance, the lower limit of the number of users using the network slice instance, and the number of packet data unit sessions run by the network slice instance.
  • Service Level Agreement SLA
  • service level protocol lower limit value of the network slice instance
  • quality of service QoS
  • service quality parameter of the network slice instance The lower limit value, the key performance indicator (KPI) parameter upper limit value of the network slice instance, the key performance indicator parameter lower limit value of the network slice instance, the identifier of the third-party management module, and the user in the unit using the network slice instance.
  • KPI key performance indicator
  • Average moving speed limit in the geographic interval The average moving speed lower limit value of the user using the network sharding instance in the unit geographical location interval, the upper limit value of the number of cell handovers that the user using the network sharding instance uses in the unit time, and the user using the network sharding instance in the unit time.
  • the lower limit of the number of cell handovers the fault alarm type identifier of the network slice instance, the fault alarm severity identifier of the network slice instance, the fault event identifier of the network slice instance, the resource utilization upper limit of the network slice instance, and the network slice instance Resource utilization lower limit, other management request ID, execution time, and execution wait time.
  • the modified network slice instance request carries the upper limit of the number of users 200.
  • the parameter for configuring the execution condition carried in the network slice instance request includes at least one of the following: the upper limit of the number of users using the network slice instance, the lower limit of the number of users using the network slice instance, and the number of packet data unit sessions run by the network slice instance.
  • the fault alarm severity identifier of the instance carries the maximum number of users 200 and the upper limit of the number of PDU sessions 1000.
  • the parameter for terminating the execution condition carried in the network slice instance request includes at least one of the following: a lower limit of the number of users using the network slice instance, a lower limit value of the number of packet data unit sessions run by the network slice instance, an identifier of the third-party management module, Network snippet instance fault alarm type identifier, network snippet instance fault alarm severity identifier, network snippet instance fault event identifier, network snippet resource utilization lower limit value, other management request identifier, execution time, and execution wait time.
  • the terminating network slice instance request carries a lower limit of the number of users.
  • the parameter for activating the execution condition carried in the network slice instance request includes at least one of the following: an identifier of the third-party management module, another management request identifier, an execution time of activating the network slice instance request, and an execution wait time for activating the network slice instance request.
  • the activation network slice instance request carries the identifier of the third-party management module
  • the third-party management module may be a client network management module, and a direct interface exists between the third-party management module and the network slice management function device, or through a security agent and Network slice management function device interaction.
  • the parameters of the execution condition carried in the network slice instance request include at least one of the following: a lower limit of the number of users using the network slice instance, a lower limit of the number of PDU sessions running by the network slice instance, an identifier of the third-party management module, and a network slice.
  • the logout network slice instance request carries a PDU session number lower limit value of 10.
  • the parameter of the execution condition carried in the network slice instance performance measurement task request includes at least one of the following: an upper limit value of the number of users using the network slice instance, a lower limit value of the number of users using the network slice instance, and a packet data unit run by the network slice instance.
  • the upper limit of the number of sessions, the lower limit of the number of packet data unit sessions run by the network slice instance, the upper limit of the service level protocol parameters of the network slice instance, the lower limit of the service level protocol parameters of the network slice instance, and the service quality of the network slice instance The upper limit of the parameter, the lower limit of the QoS parameter of the network slice instance, the upper limit of the key performance indicator of the network slice instance, the lower limit of the key performance indicator of the network slice instance, the identifier of the third-party management module, and the use of network slices.
  • the network slice instance performance measurement task request carries an upper limit value of 200 and a maximum number of PDU sessions of 1000.
  • the parameter of the execution condition carried in the network slice instance performance threshold monitoring request includes at least one of the following: an upper limit value of the number of users using the network slice instance, a lower limit value of the number of users using the network slice instance, and a packet data unit run by the network slice instance.
  • the upper limit of the number of sessions, the lower limit of the number of packet data unit sessions run by the network slice instance, the upper limit of the service level protocol parameters of the network slice instance, the lower limit of the service level protocol parameters of the network slice instance, and the service quality of the network slice instance The upper limit of the parameter, the lower limit of the QoS parameter of the network slice instance, the upper limit of the key performance indicator of the network slice instance, the lower limit of the key performance indicator of the network slice instance, the identifier of the third-party management module, and the use of network slices.
  • the average moving speed upper limit value of the user of the instance in the unit geographical location interval, the average moving speed lower limit value of the user in the unit geographical location interval using the network slice instance, and the user switching using the network slice instance in the unit time Number of upper limits, use of the network
  • the lower limit of the number of cell handovers in the unit time the fault alarm type identifier of the network slice instance, the fault alarm severity identifier of the network slice instance, the fault event identifier of the network slice instance, and the resource utilization of the network slice instance.
  • the network slice instance performance threshold monitoring request carries the user number upper limit value 200 and the PDU session number upper limit value 1000.
  • the parameter of the execution condition carried in the network segment instance alarm information reporting request includes at least one of the following: an upper limit value of the number of users using the network slice instance, a lower limit value of the number of users using the network slice instance, and a packet data unit running by the network slice instance.
  • the upper limit of the number of sessions, the lower limit of the number of packet data unit sessions run by the network slice instance, the upper limit of the service level protocol parameters of the network slice instance, the lower limit of the service level protocol parameters of the network slice instance, and the service quality of the network slice instance The upper limit of the parameter, the lower limit of the QoS parameter of the network slice instance, the upper limit of the key performance indicator of the network slice instance, the lower limit of the key performance indicator of the network slice instance, the identifier of the third-party management module, and the use of network slices.
  • the average moving speed upper limit value of the user of the instance in the unit geographical location interval, the average moving speed lower limit value of the user in the unit geographical location interval using the network slice instance, and the user switching using the network slice instance in the unit time Number of upper limits, use of the network
  • the lower limit of the number of cell handovers in the unit time the fault alarm type identifier of the network slice instance, the fault alarm severity identifier of the network slice instance, the fault event identifier of the network slice instance, and the resource utilization of the network slice instance Rate upper limit, resource utilization lower limit of the network slice instance, other management request identifiers, execution time, and execution wait time.
  • the network slice instance alarm information report request carries a software fault identifier and a severe fault identifier.
  • the SLA/QoS/KPI parameters may be delay, throughput, dropped call rate, packet loss rate, inter-cell handover success rate, and the like.
  • a resource is a compute, storage, or network resource that is assigned to a network slice instance.
  • the fault types include board faults, software faults, and communication faults. The fault types are different and the identifiers are different.
  • Fault severity includes critical faults, major faults, and minor faults.
  • Fault events include hardware failures, overloads, and the like.
  • the upper limit of the traffic used by the user using the network sharding instance may be specifically divided into the upper limit of the traffic used by the user on the current day, the upper limit of the traffic used in the current month, or the upper limit of the traffic used in the history.
  • the traffic lower limit value used by the user using the network sharding instance can be further divided into the traffic lower limit value used by the user on the current day, the traffic lower limit value used in the current month, or the traffic lower limit value used in the historical
  • the network slice management function device sends a first management request to the network slice subnet management function device, where the first management request is used to indicate that the network slice subnet management function device pairs the network sliced subnet instance and/or network Features are managed.
  • the first management request includes any one of the following: creating a network slice subnet instance request, modifying a network slice subnet instance request, configuring a network slice subnet instance request, terminating a network slice subnet instance request, and activating a network slice subnet instance request.
  • the network slice subnet instance request, the network slice subnet instance performance measurement task request, the network slice subnet instance performance threshold monitoring request, the network slice subnet instance alarm information report request, the network function request, the network function request, and the configuration are modified.
  • the parameters of the execution conditions carried by different management requests may be the same or different.
  • the parameters of the execution conditions carried by each of the above management requests are described below.
  • the parameters for creating the execution condition carried in the network segment subnet instance request include at least one of the following: an identifier of the third-party management module, a network slice subnet instance failure alarm type identifier, a fault event identifier of the network slice subnet instance, and a network slicer. Resource utilization upper limit of the network instance, other management request identifiers, execution time, and execution wait time.
  • the network slice subnet instance failure alarm type refers to other existing network slice subnet instance failure alarms that constitute the network slice subnet instance, such as an overload alarm, and is not a network slice subnet instance failure alarm to be created.
  • the resource utilization upper limit of the network slicing subnet instance refers to the resource utilization upper limit of other existing network slicing subnet instances that constitute the network slicing subnet instance, and is not the resource utilization of the network slicing subnet instance to be created.
  • Upper limit For example, the create network slice subnet instance request carries other management request identifiers, which may be management requests to terminate/modify another network slice subnet instance.
  • the network slice subnet management function device needs to perform the action of creating a network slice subnet instance after another network slice subnet instance is terminated/modified.
  • the parameter for modifying the execution condition carried in the network slice subnet instance request includes at least one of the following: an upper limit value of the number of users accessing the network slice subnet instance, a lower limit value of the number of users accessing the network slice subnet instance, and a network slice.
  • the upper limit of the number of packet data unit sessions run by the subnet instance The upper limit of the number of packet data unit sessions run by the subnet instance, the lower limit of the number of packet data unit sessions run by the network slice subnet instance, the upper limit of the traffic used by the user accessing the network slice subnet instance, and the access network slice.
  • the lower limit of the QoS parameter of the network slicing subnet instance the upper limit of the key performance indicator of the network slicing subnet instance, the lower limit of the key performance indicator of the network slicing subnet instance, and the identifier of the third-party management module.
  • the average moving speed upper limit value and access of the user accessing the network slicing subnet instance in the geographic location range of the unit The average moving speed lower limit value of the user of the network segment subnet instance in the unit geographical location interval, the upper limit value of the number of cell handovers that the user accessing the network segment subnet instance in the unit time, and the access network slice subnet instance The number of cell handovers in the unit time, the fault alarm type identifier of the network slice subnet instance, the fault alarm severity identifier of the network slice subnet instance, the fault event identifier of the network slice subnet instance, and the network slice.
  • a resource is a computing, storage, or network resource that is assigned to an instance of a network slicing subnet.
  • the modified network slice subnet instance request carries the upper limit of the number of users 200.
  • the parameter for configuring the execution condition carried in the network slice subnet instance request includes at least one of the following: an upper limit value of the number of users accessing the network slice subnet instance, a lower limit value of the number of users accessing the network slice subnet instance, and a network slice.
  • the upper limit of the number of packet data unit sessions run by the subnet instance The upper limit of the number of packet data unit sessions run by the subnet instance, the lower limit of the number of packet data unit sessions run by the network slice subnet instance, the upper limit of the traffic used by the user accessing the network slice subnet instance, and the access network slice.
  • the lower limit of the QoS parameter of the network slicing subnet instance the upper limit of the key performance indicator of the network slicing subnet instance, the lower limit of the key performance indicator of the network slicing subnet instance, and the identifier of the third-party management module.
  • the average moving speed upper limit value and access of the user accessing the network slicing subnet instance in the geographic location range of the unit The average moving speed lower limit value of the user of the network segment subnet instance in the unit geographical location interval, the upper limit value of the number of cell handovers that the user accessing the network segment subnet instance in the unit time, and the access network slice subnet instance The number of cell handovers in the unit time, the fault alarm type identifier of the network slice subnet instance, the fault alarm severity identifier of the network slice subnet instance, the fault event identifier of the network slice subnet instance, and the network slice.
  • the configuration network slice subnet instance request carries the maximum number of users 200 and the upper limit of the number of PDU sessions 1000.
  • the parameter for terminating the execution condition carried in the network slice subnet instance request includes at least one of the following: a lower limit of the number of users accessing the network slice subnet instance, and a lower limit value of the number of packet data unit sessions run by the network slice subnet instance, ID of the third-party management module, network slice subnet instance fault alarm type identifier, network slice subnet instance fault alarm severity identifier, fault event identifier of the network slice subnet instance, and resource utilization lower limit of the network slice subnet instance , other management request identifiers, execution time, and execution wait time.
  • the terminating network slice subnet instance request carries a lower limit of the number of users.
  • the parameter for activating the execution condition carried in the network slice subnet instance request includes at least one of the following: an identifier of the third-party management module, a network slice subnet instance failure alarm type identifier, a fault event identifier of the network slice subnet instance, and a network slicer. Resource utilization upper limit of the network instance, other management request identifiers, execution time, and execution wait time.
  • the network slice subnet instance failure alarm type refers to other existing network slice subnet instance failure alarms that constitute the network slice subnet instance, such as an overload alarm, and is not a network slice subnet instance failure alarm to be created.
  • the resource utilization upper limit of the network slicing subnet instance refers to the resource utilization upper limit of other existing network slicing subnet instances that constitute the network slicing subnet instance, and is not the resource utilization of the network slicing subnet instance to be created.
  • the activation network slice subnet instance request carries the identifier of the third-party management module
  • the third-party management module may be a client network management module, and a direct interface exists between the third-party management module and the network slice sub-network management function device, or through a
  • the security agent interacts with the network slicing subnet management function device.
  • the third-party management module may also be a management device that manages another network slice instance/network slice subnet instance, and the network slice instance/network slice subnet instance and the network slice subnet instance to be managed share the network function/network slice subnet. Example.
  • the parameter for canceling the execution condition carried in the network slice subnet instance request includes at least one of the following: an identifier of the third-party management module, a network slice subnet instance failure alarm type identifier, a fault event identifier of the network slice subnet instance, and a network slicer. Resource utilization lower limit of the network instance, other management request identifiers, execution time, and execution wait time.
  • the network slice subnet instance failure alarm type refers to other existing network slice subnet instance failure alarms that constitute the network slice subnet instance, such as an overload alarm, and is not a network slice subnet instance failure alarm to be created.
  • the resource utilization lower limit of the network slicing subnet instance is the lower the resource utilization ratio of the other existing network slicing subnet instances that form the network slicing subnet instance, and is not the resource utilization of the network slicing subnet instance to be created. lower limit.
  • the logout network slice subnet instance request carries the PDU session number lower limit value of 10.
  • the parameter of the execution condition carried in the network segment subnet instance performance measurement task request includes at least one of the following: an upper limit value of the number of users accessing the network slice subnet instance, and a lower limit value of the number of users accessing the network slice subnet instance, The upper limit of the number of packet data unit sessions run by the network slice subnet instance, the lower limit of the number of packet data unit sessions run by the network slice subnet instance, the service level protocol parameter upper limit value of the network slice subnet instance, and the network slice subnet.
  • the fault alarm severity identifier of the sliced subnet instance carries an upper limit value of 200 and a maximum number of PDU sessions of 1000.
  • the parameter of the execution condition carried in the network segment subnet instance performance threshold monitoring request includes at least one of the following: an upper limit value of the number of users accessing the network slice subnet instance, and a lower limit value of the number of users accessing the network slice subnet instance, The upper limit of the number of packet data unit sessions run by the network slice subnet instance, the lower limit of the number of packet data unit sessions run by the network slice subnet instance, the service level protocol parameter upper limit value of the network slice subnet instance, and the network slice subnet.
  • the fault alarm severity identifier of the sliced subnet instance carries the user number upper limit value 200 and the PDU session number upper limit value 1000.
  • the parameter of the execution condition carried in the alarm information reporting request of the network segment subnet instance includes at least one of the following: an upper limit value of the number of users accessing the network slice subnet instance, and a lower limit value of the number of users accessing the network slice subnet instance, The upper limit of the number of packet data unit sessions run by the network slice subnet instance, the lower limit of the number of packet data unit sessions run by the network slice subnet instance, the service level protocol parameter upper limit value of the network slice subnet instance, and the network slice subnet.
  • the fault alarm severity identifier of the sliced subnet instance identifies the fault event identifier of the network sliced subnet instance, the resource utilization upper limit of the network sliced subnet instance, the resource utilization lower limit of the network sliced subnet instance, and other management requests. Identification, execution time, and execution wait time.
  • the network slice subnet instance alarm information report request carries a software fault identifier and a severe fault identifier.
  • the parameters for creating the execution condition carried in the network function request include at least one of the following: an identifier of the third-party management module, a network function fault alarm type identifier, a fault event identifier of the network function, a resource utilization upper limit value of the network function, and other management.
  • Request ID identifier of the third-party management module
  • the network function fault alarm type refers to other existing network function fault alarms that constitute the network function, such as an overload alarm, and is not a network function fault alarm to be created.
  • the resource utilization upper limit of the network function refers to the resource utilization upper limit of other existing network functions that constitute the network function, and is not the resource utilization upper limit of the network function to be created.
  • the create network function request carries other management request identifiers, which may be management requests to terminate/modify another network function.
  • the network slice subnet management function device needs to perform the action of creating a network function after another network function is terminated/modified.
  • the parameter for modifying the execution condition carried in the network function request includes at least one of the following: an upper limit value of the number of users accessing the network function, a lower limit value of the number of users accessing the network function, and an upper limit of the number of the packet data unit running by the network function.
  • service level protocol parameter lower limit value of network function service level protocol parameter lower limit value of network function, service quality parameter upper limit value of network function, service quality parameter lower limit value of network function, key performance indicator parameter upper limit value of network function, key performance indicator of network function
  • the lower limit value of the parameter, the identifier of the third-party management module, the average moving speed upper limit value of the user who accesses the network function in the geographical range of the unit, and the lower limit of the average moving speed of the user who accesses the network function in the geographic location range of the unit The value of the number of cell handovers that the user accessing the network function has in a unit time, The lower limit of the number of cell handovers in the unit time, the fault alarm type identifier of the network function, the fault alarm severity identifier of the network function, the fault event identifier of the network function, and the resource utilization upper limit of the network function.
  • a resource is a computing, storage, or network resource that is assigned to a network function.
  • the modify network function request carries the upper limit of the number of users 200.
  • the parameter for configuring the execution condition carried in the network function request includes at least one of the following: an upper limit value of the number of users accessing the network function, a lower limit value of the number of users accessing the network function, and an upper limit of the number of the packet data unit running by the network function.
  • the parameter for terminating the execution condition carried in the network function request includes at least one of the following: a lower limit value of the number of users accessing the network function, a lower limit value of the number of packet data unit sessions running the network function, an identifier of the third-party management module, and a network function. Fault alarm type identifier, network function fault alarm severity identifier, network function fault event identifier, network function resource utilization lower limit value, other management request identifier, execution time, and execution wait time.
  • the terminating network function request carries a lower limit of the number of users.
  • the parameters for activating the execution condition carried in the network function request include at least one of the following: an identifier of the third-party management module, a network function fault alarm type identifier, a fault event identifier of the network function, a resource utilization upper limit value of the network function, and other management.
  • Request ID, execution time, and execution wait time refers to other existing network function fault alarms that constitute the network function, such as an overload alarm, and is not a network function fault alarm to be created.
  • the resource utilization upper limit of the network function refers to the resource utilization upper limit of other existing network functions that constitute the network function, and is not the resource utilization upper limit of the network function to be created.
  • the activation network function request carries the identifier of the third-party management module
  • the third-party management module may be a network management module of the client, and a direct interface exists between the third-party management module and the network slice sub-network management function device, or through a security agent and The network slice subnet management function device interacts.
  • the third-party management module may also be a management device that manages another network slice instance/network slice subnet instance, and the network slice instance/network slice subnet instance managed by the management device shares the network function to be activated with the network slice subnet management device. .
  • the parameter for canceling the execution condition carried in the network function request includes at least one of the following: an identifier of the third-party management module, a network function fault alarm type identifier, a fault event identifier of the network function, a resource utilization lower limit value of the network function, and other management Request ID, execution time, and execution wait time.
  • the network function fault alarm type refers to other existing network function fault alarms that constitute the network function, such as an overload alarm, which is not a network function fault alarm to be created.
  • the resource utilization lower limit value of the network function refers to the resource utilization lower limit value of other existing network functions that constitute the network function, and is not the resource utilization lower limit value of the network function to be created.
  • the logout network function request carries a PDU session lower limit value of 10.
  • the parameter of the execution condition carried in the network function performance measurement task request includes at least one of the following: an upper limit value of the number of users accessing the network function, a lower limit value of the number of users accessing the network function, and a number of packet data unit sessions in which the network function operates.
  • the lower limit value of the service quality parameter, the upper limit value of the key performance indicator parameter of the network function, the lower limit value of the key performance indicator parameter of the network function, the identifier of the third-party management module, and the user accessing the network function are within the unit geographical interval
  • the average moving speed upper limit value, the average moving speed lower limit value of the user who accesses the network function in the unit geographical distance interval, the upper limit value of the number of cell switching that the user accessing the network function generates in a unit time, and the access network The number of users switching the number of cell handovers per unit time, network function Fault alarm type identifier, network function fault alarm severity identifier, network function fault event identifier, network function resource utilization upper limit value, network function
  • the parameter of the execution condition carried in the network function performance threshold monitoring request includes at least one of the following: an upper limit value of the number of users accessing the network function, a lower limit value of the number of users accessing the network function, and a number of packet data unit sessions in which the network function operates.
  • the lower limit value of the service quality parameter, the upper limit value of the key performance indicator parameter of the network function, the lower limit value of the key performance indicator parameter of the network function, the identifier of the third-party management module, and the user accessing the network function are within the unit geographical interval
  • the average moving speed upper limit value, the average moving speed lower limit value of the user who accesses the network function in the unit geographical distance interval, the upper limit value of the number of cell switching that the user accessing the network function generates in a unit time, and the access network The number of users switching the number of cell handovers per unit time, network function Fault alarm type identifier, network function fault alarm severity identifier, network function fault event identifier, network function resource utilization upper limit value, network function
  • the parameter of the execution condition carried in the network function alarm information reporting request includes at least one of the following: an upper limit value of the number of users accessing the network function, a lower limit value of the number of users accessing the network function, and a number of packet data unit sessions in which the network function operates.
  • the lower limit value of the service quality parameter, the upper limit value of the key performance indicator parameter of the network function, the lower limit value of the key performance indicator parameter of the network function, the identifier of the third-party management module, and the user accessing the network function are within the unit geographical interval
  • the average moving speed upper limit value, the average moving speed lower limit value of the user who accesses the network function in the unit geographical distance interval, the upper limit value of the number of cell switching that the user accessing the network function generates in a unit time, and the access network The number of users switching the number of cell handovers per unit time, network function Fault alarm type identifier, network function fault alarm severity identifier, network function fault event identifier, network function resource utilization upper limit value, network function
  • the parameter type and the parameter value may be carried in the first management request.
  • the parameter type may include at least one of the following: an upper limit of the number of users, a lower limit of the number of users, an upper limit of the number of PDU sessions, a lower limit of the number of PDU sessions, an upper limit of the traffic used by the user on the current day, and a traffic used by the user on the current day.
  • the format of the parameter type and the parameter value that can be carried in the first management request can be seen in Table 1 below.
  • the first management request carries the parameter type and the parameter value.
  • the first management request may also carry other fields, which is not specifically limited in the embodiment of the present invention.
  • the first management request may specifically carry one or more of the parameter types shown in Table 1.
  • the parameter value carried in the first management request may also be one or more, and each parameter value is associated with a certain one.
  • the parameter type corresponds.
  • the parameter values in Table 1 are only used as an example. In practical applications, the parameter values may also be other values, which are not specifically limited in the embodiment of the present invention.
  • the first network device receives the first management request from the second network device, and when the execution condition is met, the first network device executes the first management request.
  • the execution condition is met when at least one of the following conditions is met: the number of users accessing the network slice instance is greater than or equal to the upper limit of the number of users, and the number of users accessing the network slice instance is less than or equal to the number of users.
  • the limit the number of packet data unit sessions run by the network slice instance is greater than or equal to the upper limit of the number of packet data unit sessions, the number of packet data unit sessions run by the network slice instance is less than or equal to the lower limit of the number of packet data unit sessions, and the access network.
  • the traffic threshold used by the user in the unit time of the slice instance (for example, cumulative on the current day, accumulated in the current month, accumulated in history, etc.) is greater than or equal to the upper limit of the traffic used by the user, and the traffic threshold accumulated in the user unit time of the access network slice instance.
  • the service level protocol parameter of the network slice instance is greater than or equal to the service level protocol parameter upper limit value, the service level protocol parameter of the network slice instance is less than or equal to the service level protocol parameter lower limit value, and the network The quality of service parameters of the slice instance is large Or equal to the upper limit of the quality of service parameter, the quality of service parameter of the network slice instance is less than or equal to the lower limit of the quality of service parameter, the key performance indicator of the network slice instance is greater than or equal to the upper limit of the key performance indicator parameter, and the key of the network slice instance The performance indicator parameter is less than or equal to the lower limit value of the key performance indicator parameter, the network slice management function device receives the request sent by the third-party management module corresponding to the identifier of the third-party management module, and the user accessing the network slice instance is in the unit geographical location interval ( For example, the coverage of a specific cell, or the geographic range of the tracking area (TA), the average moving speed is greater than or equal to
  • the average moving speed in the geographical interval is less than or equal to the average moving speed lower limit, and the number of cell handovers in the unit time (for example, 1 day, 5 days, etc.) of the user accessing the network slice instance is greater than or equal to the cell handover.
  • the upper limit value, the user accessing the network slice instance in the unit The number of cell handovers is less than or equal to the number of cell handovers, the network slice management function device receives the alarm information that is consistent with the fault alarm type identifier, and the network slice management function device receives the fault identifier that is consistent with the fault severity identifier.
  • the alarm information, the fault event corresponding to the fault event identifier of the network slice management function device, the resource utilization of the network slice instance is greater than or equal to the resource utilization upper limit, and the resource utilization of the network slice instance is less than or equal to the resource utilization lower limit.
  • the first management request is a terminating network slice instance request
  • the terminating network slice instance request carries the identifier NSI1 of the network slice instance and the number of users lower limit value 10. Then, when the network slice management function device detects that the number of users accessing the network slice instance corresponding to the NSI1 is less than or equal to 10, the network slice management function device terminates the network slice instance corresponding to the NSI1.
  • the execution condition is met when at least one of the following conditions is met: the number of users accessing the network slice subnet instance is greater than or equal to the upper limit of the number of users, and the number of users accessing the network slice subnet instance is less than or Equivalent to the lower limit of the number of users, the number of packet data unit sessions run by the network slice subnet instance is greater than or equal to the upper limit of the number of packet data unit sessions, and the number of packet data unit sessions run by the network slice subnet instance is less than or equal to the packet data unit session.
  • the number of lower limit values, the user unit time of the access network segment subnet instance (for example, cumulative on the day, accumulated in the current month, historical total, etc.) is greater than or equal to the traffic upper limit value used by the user, and access network slice
  • the traffic threshold accumulated in the user unit time of the network instance is less than or equal to the traffic lower limit value used by the user
  • the service level protocol parameter of the network slice subnet instance is greater than or equal to the service level protocol parameter upper limit value
  • the network slice subnet instance is
  • the service level agreement parameter is less than or equal to the lower limit of the service level agreement parameter.
  • the service quality parameter of the network segment subnet instance is greater than or equal to the upper limit of the service quality parameter, the service quality parameter of the network slice subnet instance is less than or equal to the service quality parameter lower limit, and the key performance indicator parameter of the network slice subnet instance is greater than Or equal to the upper limit value of the key performance indicator parameter, the key performance indicator parameter of the network slice subnet instance is less than or equal to the lower limit value of the key performance indicator parameter, and the average moving speed of the user in the geographical location interval of the user accessing the network slice subnet instance
  • the average moving speed of the user that is greater than or equal to the upper limit of the moving speed and the access network segment subnet instance is less than or equal to the average moving speed lower limit value, and the user accessing the network slice subnet instance is in the unit.
  • the number of cell handovers in the time is greater than or equal to the upper limit of the number of cell handovers, and the number of cell handovers that occur when the user accessing the network segment subnet instance is less than or equal to the number of cell handovers.
  • the resource utilization of the sliced subnet instance is greater than or equal to the resource
  • the upper limit of the usage rate, the resource utilization of the network slice subnet instance is less than or equal to the lower limit of the resource utilization, the number of users accessing the network function is greater than or equal to the upper limit of the number of users, and the number of users accessing the network function.
  • the number of packet data unit sessions in which the network function operates is greater than or equal to the upper limit value of the number of packet data unit sessions, and the number of packet data unit sessions in which the network function operates is less than or equal to the lower limit of the number of packet data unit sessions.
  • the traffic threshold that is accumulated in the user's unit time for accessing the network function is greater than or equal to the traffic upper limit value used by the user, and the traffic threshold value accumulated during the user's unit time accessing the network function is less than or equal to the traffic lower limit value used by the user.
  • the service level protocol parameter of the network function is greater than or equal to the upper limit value of the service level protocol parameter, the service level agreement parameter of the network function is less than or equal to the lower limit value of the service level protocol parameter, and the service quality parameter of the network function is greater than or equal to the service quality parameter.
  • the service quality parameter of the limit and network function is less than Or equal to the lower limit of the quality of service parameter
  • the key performance indicator parameter of the network function is greater than or equal to the upper limit value of the key performance indicator parameter
  • the key performance indicator parameter of the network function is less than or equal to the lower limit value of the key performance indicator parameter
  • the network slice subnet management The function device receives the request sent by the third-party management module corresponding to the identifier of the third-party management module, and the average moving speed of the user in the geographical location interval of the user who accesses the network function is greater than or equal to the upper limit of the average moving speed, and the access network function.
  • the average moving speed of the user in the geographical interval of the unit is less than or equal to the lower limit of the average moving speed, and the number of cell handovers per unit time of the user accessing the network function is greater than or equal to the upper limit of the number of cell handovers.
  • the number of cell handovers in the unit time is less than or equal to the lower limit of the number of cell handovers, and the network slice subnet management function device receives the alarm information consistent with the fault alarm type identifier, and the network slice subnet management.
  • the alarm information with the same sex identifier, the fault event corresponding to the fault event identifier of the network slice subnet management function device, the resource utilization of the network function is greater than or equal to the resource utilization upper limit value, and the resource utilization of the network function is less than or equal to the resource utilization.
  • the network slice subnet management function device After the lower limit value and the network slice subnet management function device perform the management request corresponding to the other management request identifiers, the network slice subnet management function device performs the management request corresponding to the other management request identifiers successfully, and the network slice subnet management function device performs other management requests.
  • the management request corresponding to the management request fails, the execution time arrives, and the execution waiting time is reached from the time when the first management request is received by the network slice subnet management function device.
  • the network slice subnet management function device executes the first management request when the execution condition is satisfied.
  • the first management request is to create a network slice subnet instance request
  • the create network slice subnet instance request carries other management request identifiers.
  • the network slice subnet management function device creates a network slice subnet instance when the network slice subnet management function device detects that the management request corresponding to the other management request identifier is successfully executed.
  • the first management request is an activation network function request
  • the activation network function request carries an identifier of the network function NF1 and an identifier of the third-party management module. Then, when the network slice subnet management function device detects the request triggered by the third-party management module, the network slice subnet management function device activates the network function corresponding to the NF1.
  • the first network device immediately executes the first management request.
  • the first network device determines whether the first management request is executable. If the first management request is executable, the first network device feeds back to the second network device that the first management request can be executed, and executes the first management request after waiting for the execution condition to be satisfied. If the first management request cannot be executed, the first network device feeds back to the second network device that the first management request cannot be executed, and explains the reason. For example, the first network device determines whether the first management request is executable according to the resource and capability status of the managed network. If the resources required to execute the first management request are insufficient, it indicates that the first management request is not executable.
  • the first network device may further feed back the execution result to the second network device.
  • the network instance management is more flexible and automated by carrying the method for executing the condition parameter in the first management request message.
  • the embodiment of the present invention can enable the network instance management device to execute the management request according to the execution condition.
  • the technology introduced in the embodiment of the present invention can be applied to a hierarchical network slice management system, which is applicable to the creation, modification, configuration, termination, activation, deactivation, performance measurement, and performance threshold of a network slice instance/network slice subnet instance/network function.
  • Management requests such as monitoring and alarm information reporting are applicable to the lifecycle management of network slicing instances/network slicing subnet instances/network functions.
  • the parameters of the execution conditions that can be carried by the embodiment of the present invention are more types, wider in scope and higher in complexity.
  • the present invention further provides a related device for implementing the foregoing method.
  • FIG. 3 is a schematic structural diagram of a network device according to an embodiment of the present invention.
  • the first network device 30 includes a processor 301 and a transceiver 303.
  • the first network device may further include a memory 302.
  • the processor 301, the memory 302, and the transceiver 303 may be connected by a bus or other means.
  • the embodiment of the present invention may be described by connecting the processor 301, the memory 302, and the transceiver 303 via the bus 304.
  • the first network device 30 may also include a module not shown in FIG.
  • the processor 301 may be a general-purpose processor, such as a central processing unit (CPU), or may be a digital signal processing (DSP) or an application specific integrated circuit (ASIC). Or one or more integrated circuits configured to implement embodiments of the present invention.
  • the processor 301 can process the data received through the transceiver 303. Processor 301 can also process data to be sent to transceiver 303.
  • the memory 302 is used to store program instructions and/or data and to transfer the program instructions to the CPU.
  • the memory 302 can include a Volotile Memory, such as a Random Access Memory (RAM).
  • the memory 302 may also include a non-volatile memory such as a read-only memory (ROM), a flash memory, a hard disk (HDD), or a solid state hard disk ( Solid-State Drive, SSD).
  • ROM read-only memory
  • HDD hard disk
  • SSD solid state hard disk
  • Memory 302 can also include a combination of the above types of memory.
  • the memory 302 is coupled to the processor 301 via a bus.
  • the transceiver 303 is used by the first network device 30 to perform data communication with other devices, for example, with the second network device.
  • the processor 301 is configured to invoke program instructions and data stored in the memory 302, and perform the following operations:
  • the transceiver 303 Receiving, by the transceiver 303, a first management request from the second network device, where the first management request is used to indicate management of a network instance, where the first management request includes a parameter of an execution condition, the parameter and the network instance Corresponding;
  • the first network device is a network slice management function device, and the second network device is a communication service management function device; or the first network device is a network slice subnet management function device, and the second network is The device is a network slice management function device.
  • the first management request is executed when the execution condition is satisfied.
  • the network instance includes at least one of the following: a network slice instance, a network slice subnet instance, and a network function.
  • the first management request includes any one of the following: a create request, a modify request, a configuration request, a final request, an activation request, a logout request, a performance measurement task request, a performance threshold monitoring request, and an alarm information reporting request.
  • the parameter includes at least one of: a threshold number of users accessing the network instance, a threshold number of packet data unit sessions run by the network instance, a traffic threshold used by a user accessing the network instance, a service level protocol parameter threshold of the network instance, a QoS parameter threshold of the network instance, a key performance indicator parameter threshold of the network instance, an identifier of a third-party management module, and a user accessing the network instance in a unit geography
  • An average moving speed threshold in the location interval a threshold value of the number of cell handovers that the user accessing the network instance generates in a unit time, a fault alarm type identifier of the network instance, a fault alarm severity identifier of the network instance, The fault event identifier of the network instance, the resource utilization threshold of the network instance, other management request identifiers, the execution time of the first management request, and the execution wait time of the first management request.
  • the execution condition is met when at least one of the following conditions is met: the number of users accessing the network instance reaches the number of users threshold, and the number of packet data unit sessions run by the network instance reaches the packet data.
  • the unit session number threshold, the traffic threshold value accumulated in the user unit time accessing the network instance reaches the traffic threshold used by the user, the service level protocol parameter of the network instance reaches the service level protocol parameter threshold, and the The service quality parameter of the network instance reaches the service quality parameter threshold, the key performance indicator parameter of the network instance reaches the key performance indicator parameter threshold, and the first network device receives the identifier of the third-party management module.
  • the request sent by the third-party management module the average moving speed of the user accessing the network instance in the geographic location range of the device reaches the average moving speed threshold, and the user accessing the network instance generates a cell in a unit time.
  • the number of handovers reaches the threshold number of occurrences of the cell handover,
  • the first network device receives the alarm information that is consistent with the fault alarm type identifier, the first network device receives the alarm information that is consistent with the fault alarm severity identifier, and the first network device generates the fault.
  • the first network device executes the management request corresponding to the other management request identifier, the execution time arrives, and the slave station The execution waiting time is reached when the first network device receives the first management request.
  • FIG. 4 is a schematic structural diagram of another network device according to an embodiment of the present invention.
  • the second network device 40 can include a processor 401 and a transceiver 403.
  • the first network device may further include a memory 302.
  • the processor 401, the memory 402, and the transceiver 403 may be connected by a bus or other means.
  • the embodiment of the present invention may be described by taking the connection of the processor 401, the memory 402, and the transceiver 403 through the bus 404 as an example.
  • the second network device 40 may also include a module not shown in FIG.
  • the processor 401 may be a general purpose processor, such as a CPU, or may be a DSP, an ASIC, or one or more integrated circuits configured to implement embodiments of the present invention.
  • the processor 401 can process the data received through the transceiver 403.
  • Processor 401 can also process data to be sent to transceiver 403.
  • the memory 402 is used to store program instructions and/or data and to transfer the program instructions to the CPU.
  • Memory 402 can include volatile memory, such as RAM.
  • Memory 402 can also include non-volatile memory, such as ROM, flash memory, HDD, or SSD; memory 402 can also include a combination of the types of memory described above.
  • the memory 402 is coupled to the processor 401 via a bus.
  • the transceiver 403 is used by the second network device 40 to perform data communication with other devices, for example, with the first network device.
  • the processor 401 is configured to invoke program instructions and data stored in the memory 402, and perform the following operations:
  • Determining a first management request the first management request including a parameter of an execution condition, the parameter being related to a network instance;
  • the first network device is a network slice management function device, and the second network device is a communication service management function device; or the first network device is a network slice subnet management function device, and the second network device is Network slice management function device.
  • the network instance includes at least one of the following: a network slice instance, a network slice subnet instance, and a network function.
  • the first management request includes any one of the following: a create request, a modify request, a configuration request, a final request, an activation request, a logout request, a performance measurement task request, a performance threshold monitoring request, and an alarm information reporting request.
  • the parameter includes at least one of: a threshold number of users using the network instance, a threshold number of packet data unit sessions run by the network instance, a traffic threshold used by a user using the network instance, a service level protocol parameter threshold of the network instance, a QoS parameter threshold of the network instance, a key performance indicator parameter threshold of the network instance, an identifier of a third-party management module, and a user using the network instance in a unit geographic location interval
  • the average moving speed threshold, the threshold of the number of times the user of the network instance uses the cell handover in the unit time, the fault alarm type identifier of the network instance, the fault alarm severity identifier of the network instance, and the network instance A fault event identifier, a resource utilization threshold of the network instance, other management request identifiers, an execution time of the first management request, and an execution wait time of the first management request.
  • the execution condition is met when at least one of the following conditions is met: the number of users using the network instance reaches the number of users threshold, and the number of packet data unit sessions run by the network instance reaches the packet data unit
  • the quality of service parameter reaches the threshold of the quality of service parameter
  • the key performance indicator parameter of the network instance reaches the threshold of the key performance indicator parameter
  • the first network device receives the identifier corresponding to the identifier of the third-party management module.
  • the request sent by the third-party management module the average moving speed of the user using the network instance in the geographic location range of the unit reaches the average moving speed threshold, and the number of cell switchings performed by the user using the network instance in a unit time is reached.
  • the threshold number of occurrences of cell handover The first network device receives the alarm information that is consistent with the fault alarm type identifier, the first network device receives the alarm information that is consistent with the fault alarm severity identifier, and the first network device generates the fault.
  • the first network device executes the management request corresponding to the other management request identifier, the execution time arrives, and the slave station The execution waiting time is reached when the first network device receives the first management request.
  • FIG. 5 is a schematic structural diagram of another network device according to an embodiment of the present invention.
  • the first network device 50 includes a receiving unit 501 and a processing unit 502.
  • the receiving unit 501 is configured to receive, by the second network device, a first management request, where the first management request is used to indicate management of a network instance, where the first management request includes a parameter of an execution condition.
  • the parameter is related to the network instance;
  • the first network device is a network slice management function device, and the second network device is a communication service management function device; or the first network device is a network slice subnet Managing a functional device, where the second network device is a network slice management function device;
  • the processing unit 502 is configured to execute the first management request when the execution condition is met.
  • the first network device 50 is presented in the form of a functional unit.
  • a "unit” herein may refer to an ASIC, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other devices that provide the functionality described above.
  • the first network device 50 can take the form shown in FIG.
  • the receiving unit 501 can be implemented by the transceiver 303 in FIG. 3, and the processing unit 502 can be implemented by the processor 301 in FIG.
  • the network instance includes at least one of the following: a network slice instance, a network slice subnet instance, and a network function.
  • the first management request includes any one of the following: a create request, a modify request, a configuration request, a final request, an activation request, a logout request, a performance measurement task request, a performance threshold monitoring request, and an alarm information reporting request.
  • the parameter includes at least one of: a threshold number of users using the network instance, a threshold number of packet data unit sessions run by the network instance, a traffic threshold used by a user using the network instance, a service level protocol parameter threshold of the network instance, a QoS parameter threshold of the network instance, a key performance indicator parameter threshold of the network instance, an identifier of a third-party management module, and a user using the network instance in a unit geographic location interval
  • the average moving speed threshold, the threshold of the number of times the user of the network instance uses the cell handover in the unit time, the fault alarm type identifier of the network instance, the fault alarm severity identifier of the network instance, and the network instance A fault event identifier, a resource utilization threshold of the network instance, other management request identifiers, an execution time of the first management request, and an execution wait time of the first management request.
  • the execution condition is met when at least one of the following conditions is met: the number of users using the network instance reaches the number of users threshold, and the number of packet data unit sessions run by the network instance reaches the packet data unit
  • the quality of service parameter reaches the threshold of the quality of service parameter
  • the key performance indicator parameter of the network instance reaches the threshold of the key performance indicator parameter
  • the first network device receives the identifier corresponding to the identifier of the third-party management module.
  • the request sent by the third-party management module the average moving speed of the user using the network instance in the geographic location range of the unit reaches the average moving speed threshold, and the number of cell switchings performed by the user using the network instance in a unit time is reached.
  • the threshold number of occurrences of cell handover The first network device receives the alarm information that is consistent with the fault alarm type identifier, the first network device receives the alarm information that is consistent with the fault alarm severity identifier, and the first network device generates the fault.
  • the first network device executes the management request corresponding to the other management request identifier, the execution time arrives, and the slave station The execution waiting time is reached when the first network device receives the first management request.
  • FIG. 6 is a schematic structural diagram of another network device according to an embodiment of the present invention. As shown in FIG. 6, the second network device 60 includes a determining unit 601 and a transmitting unit 602.
  • the determining unit 601 is configured to determine a first management request, where the first management request includes a parameter of an execution condition, and the parameter is related to a network instance;
  • the sending unit 602 is configured to send, to the first network device, a first management request, where the first management request is used to instruct the first network device to execute the first management request for the network instance when the execution condition is met;
  • the first network device is a network slice management function device, and the second network device is a communication service management function device; or the first network device is a network slice subnet management function device, and the second network device is Network slice management function device.
  • the second network device 60 is presented in the form of a functional unit.
  • a "unit” herein may refer to an ASIC, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other devices that provide the functionality described above.
  • the second network device 60 can take the form shown in FIG.
  • the determining unit 601 can be implemented by the processor 401 in FIG. 4, and the sending unit 602 can be implemented by the transceiver 403 in FIG.
  • the network instance includes at least one of the following: a network slice instance, a network slice subnet instance, and a network function.
  • the first management request includes any one of the following: a create request, a modify request, a configuration request, a final request, an activation request, a logout request, a performance measurement task request, a performance threshold monitoring request, and an alarm information reporting request.
  • the parameter includes at least one of: a threshold number of users using the network instance, a threshold number of packet data unit sessions run by the network instance, a traffic threshold used by a user using the network instance, a service level protocol parameter threshold of the network instance, a QoS parameter threshold of the network instance, a key performance indicator parameter threshold of the network instance, an identifier of a third-party management module, and a user using the network instance in a unit geographic location interval
  • the average moving speed threshold, the threshold of the number of times the user of the network instance uses the cell handover in the unit time, the fault alarm type identifier of the network instance, the fault alarm severity identifier of the network instance, and the network instance A fault event identifier, a resource utilization threshold of the network instance, other management request identifiers, an execution time of the first management request, and an execution wait time of the first management request.
  • the execution condition is met when at least one of the following conditions is met: the number of users using the network instance reaches the number of users threshold, and the number of packet data unit sessions run by the network instance reaches the packet data unit
  • the quality of service parameter reaches the threshold of the quality of service parameter
  • the key performance indicator parameter of the network instance reaches the threshold of the key performance indicator parameter
  • the first network device receives the identifier corresponding to the identifier of the third-party management module.
  • the request sent by the third-party management module the average moving speed of the user using the network instance in the geographic location range of the unit reaches the average moving speed threshold, and the number of cell switchings performed by the user using the network instance in a unit time is reached.
  • the threshold number of occurrences of cell handover The first network device receives the alarm information that is consistent with the fault alarm type identifier, the first network device receives the alarm information that is consistent with the fault alarm severity identifier, and the first network device generates the fault.
  • the first network device executes the management request corresponding to the other management request identifier, the execution time arrives, and the slave station The execution waiting time is reached when the first network device receives the first management request.
  • FIG. 7 is a schematic structural diagram of a device according to an embodiment of the present invention.
  • apparatus 70 can include a processor 701 and one or more interfaces 702 coupled to processor 701. among them:
  • the processor 701 can be used to read and execute computer readable instructions.
  • the processor 701 can mainly include a controller, an operator, and a register.
  • the controller is mainly responsible for instruction decoding, and sends a control signal for the operation corresponding to the instruction.
  • the operator is mainly responsible for performing fixed-point or floating-point arithmetic operations, shift operations, and logic operations, as well as performing address operations and conversions.
  • the register is mainly responsible for saving the register operands and intermediate operation results temporarily stored during the execution of the instruction.
  • the hardware architecture of the processor 701 may be an Application Specific Integrated Circuits (ASIC) architecture or the like.
  • the processor 701 can be single core or multi-core.
  • the interface 702 can be used to input data to be processed to the processor 701, and can output the processing result of the processor 701 to the outside.
  • the processor 701 can be used to invoke an implementation program of the network instance management method provided by one or more embodiments of the present application on the first network device side from the memory, and execute the instructions included in the program.
  • the interface 702 can be used to output the execution result of the processor 701.
  • processor 701 and the interface 702 can be implemented by using a hardware design or a software design, and can also be implemented by a combination of software and hardware, which is not limited herein.
  • FIG. 8 is a schematic structural diagram of another apparatus according to an embodiment of the present invention.
  • device 80 can include a processor 801 and one or more interfaces 802 coupled to processor 801. among them:
  • the processor 801 can be used to read and execute computer readable instructions.
  • the processor 801 can mainly include a controller, an operator, and a register.
  • the controller is mainly responsible for instruction decoding, and sends a control signal for the operation corresponding to the instruction.
  • the operator is mainly responsible for performing fixed-point or floating-point arithmetic operations, shift operations, and logic operations, as well as performing address operations and conversions.
  • the register is mainly responsible for saving the register operands and intermediate operation results temporarily stored during the execution of the instruction.
  • the hardware architecture of the processor 801 may be an Application Specific Integrated Circuits (ASIC) architecture or the like.
  • the processor 801 can be single core or multi-core.
  • the interface 802 can be used to input data to be processed to the processor 801, and can output the processing result of the processor 801 to the outside.
  • the processor 801 can be used to invoke an implementation program of the network instance management method provided by one or more embodiments of the present application on the second network device side from the memory, and execute the instructions included in the program.
  • the interface 802 can be used to output the execution result of the processor 801.
  • processor 801 and the interface 802 can be implemented by using a hardware design or a software design, and can also be implemented by a combination of software and hardware, which is not limited herein.
  • 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 program instructions.
  • the software program instructions may be composed of corresponding software modules, which may be stored in RAM, flash memory, ROM, Erasable Programmable ROM (EPROM), and electrically erasable programmable read only memory (Electrically EPROM). , 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. Additionally, the ASIC can be located in a transceiver or relay device.
  • the processor and the storage medium may also exist as a discrete component in the first network device or the second network 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 program instructions or code on a computer readable medium.
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种网络实例管理方法及相关设备，该方法包括：第一网络设备从第二网络设备接收第一管理请求，所述第一管理请求用于指示对网络实例进行管理，所述第一管理请求包括执行条件的参数，所述参数与所述网络实例相关；所述第一网络设备为网络切片管理功能设备，所述第二网络设备为通信业务管理功能设备；或者，所述第一网络设备为网络切片子网管理功能设备，所述第二网络设备为网络切片管理功能设备；在所述执行条件满足时，所述第一网络设备执行所述第一管理请求。实施本发明实施例，可以灵活地对网络实例进行管理。

Description

一种网络实例管理方法及相关设备 技术领域
本发明实施例涉及通信技术领域，尤其涉及一种网络实例管理方法及相关设备。
背景技术
无线通信技术发展日新月异，未来无线通信业务将千变万化，形态各异。第五代(5th Generation，5G)通信网络将面向不同的应用场景，比如，超高清视频、虚拟现实、大规模物联网、车联网等等。不同的场景对网络的移动性、安全性、时延、可靠性，甚至是计费方式的要求是不一样的。为适应不同的业务对网络性能不同的要求，未来网络需要具备按需制定的能力，也就是要能实现灵活的配置网络切片，将物理网络切割成多个虚拟网络切片，每个虚拟网络切片面向不同的应用场景需求。一个网络切片满足某一类或一个用例的通信服务需求，整个5G通信网络由满足不同服务需求的大量网络切片组成。在网络系统中，网络切片是以网络实例的形式创建和应用的，因此，在5G网络系统中，如何实现对网络实例进行管理是目前需要解决的技术问题。
发明内容
本发明实施例提供了一种网络实例管理方法及相关设备，可以灵活地对网络实例进行管理。
本发明实施例具体可以通过如下技术方案实现：
第一方面，本发明实施例提供了一种网络实例管理方法，应用于第一网络设备侧。该方法包括：第一网络设备从第二网络设备接收第一管理请求，第一管理请求用于指示对网络实例进行管理，第一管理请求包括执行条件的参数，参数与网络实例相关。第一网络设备为网络切片管理功能设备，第二网络设备为通信业务管理功能设备。或者，第一网络设备为网络切片子网管理功能设备，第二网络设备为网络切片管理功能设备。在执行条件满足时，第一网络设备执行第一管理请求。
第二方面，本发明实施例提供了另一种网络实例管理方法，应用于第二网络设备侧。该方法包括：第二网络设备确定第一管理请求，第一管理请求包括执行条件的参数，该参数与网络实例相关。第二网络设备向第一网络设备发送第一管理请求，第一管理请求用于指示第一网络设备在执行条件满足时针对网络实例执行第一管理请求。第一网络设备为网络切片管理功能设备，第二网络设备为通信业务管理功能设备。或者，第一网络设备为网络切片子网管理功能设备，第二网络设备为网络切片管理功能设备。
通过实施上述网络实例管理方法，第二网络设备可以在发送的第一管理请求中携带执行条件的参数，以使得第一网络设备接收该第一管理请求后，在执行条 件满足时，再针对网络实例执行该第一管理请求，从而实现灵活地对网络实例进行管理。
结合第一方面或第二方面，在一些实现方式中，上述网络实例包括以下至少一项：网络切片实例、网络切片子网实例和网络功能。
结合第一方面或第二方面，在一些实现方式中，上述第一管理请求包括以下任一项：创建请求、修改请求、配置请求、终结请求、激活请求、注销请求、性能测量任务请求、性能阈值监测请求和告警信息上报请求。本发明实施例适用于对网络实例进行创建、修改、配置、终结、激活、注销、性能测量、性能阈值监测和告警信息上报等管理，可以实现对网络实例的整个生命周期进行管理。
结合第一方面或第二方面，在一些实现方式中，上述参数包括以下至少一项：使用网络实例的用户数量阈值、网络实例运行的分组数据单元会话数量阈值、使用网络实例的用户使用的流量阈值、网络实例的服务水平协议参数阈值、网络实例的服务质量参数阈值、网络实例的关键性能指标参数阈值、第三方管理模块的标识、使用网络实例的用户在单位地理位置区间内的平均移动速度阈值、使用网络实例的用户在单位时间内发生小区切换的数量阈值、网络实例的故障告警类型标识、网络实例的故障告警严重性标识、网络实例的故障事件标识、网络实例的资源利用率阈值、其他管理请求标识、第一管理请求的执行时间和第一管理请求的执行等待时间。相比于现有技术，本发明实施例中管理请求中可携带的执行条件的参数的类型更多，范围更广，复杂度更高。
结合第一方面或第二方面，在一些实现方式中，当满足以下至少一项时上述执行条件满足：使用网络实例的用户的数量达到用户数量阈值、网络实例运行的分组数据单元会话数量达到分组数据单元会话数量阈值、使用网络实例的用户单位时间内累积使用的流量阈值达到用户使用的流量阈值、网络实例的服务水平协议参数达到服务水平协议参数阈值、网络实例的服务质量参数达到服务质量参数阈值、网络实例的关键性能指标参数达到关键性能指标参数阈值、第一网络设备接收到第三方管理模块的标识对应的第三方管理模块发送的请求、使用网络实例的用户在单位地理位置区间内的平均移动速度达到平均移动速度阈值、使用网络实例的用户在单位时间内发生小区切换的数量达到发生小区切换的数量阈值、第一网络设备接收到与故障告警类型标识一致的告警信息、第一网络设备接收到与故障告警严重性标识一致的告警信息、第一网络设备发生故障事件标识对应的故障事件、网络实例的资源利用率达到资源利用率阈值、第一网络设备执行其他管理请求标识对应的管理请求后、执行时间到达、从第一网络设备接收到第一管理请求的时刻起计时达到执行等待时间。
结合第一方面或第二方面，在一些实现方式中，使用网络实例的用户数量阈值包括使用网络实例的用户数量上限值或使用网络实例的用户数量下限值。网络实例运行的分组数据单元会话数量阈值包括网络实例运行的分组数据单元会话数量上限值或网络实例运行的分组数据单元会话数量下限值。使用网络实例的用户使用的流量阈值包括使用网络实例的用户使用的流量上限值或使用网络实例 的用户使用的流量下限值。网络实例的服务水平协议参数阈值包括网络实例的服务水平协议参数上限值或网络实例的服务水平协议参数下限值。网络实例的服务质量参数阈值包括网络实例的服务质量参数上限值或网络实例的服务质量参数下限值。网络实例的关键性能指标参数阈值包括网络实例的关键性能指标参数上限值或网络实例的关键性能指标参数下限值。使用网络实例的用户在单位地理位置区间内的平均移动速度阈值包括使用网络实例的用户在单位地理位置区间内的平均移动速度上限值或使用网络实例的用户在单位地理位置区间内的平均移动速度下限值。使用网络实例的用户在单位时间内发生小区切换的数量阈值包括使用网络实例的用户在单位时间内发生小区切换的数量上限值或使用网络实例的用户在单位时间内发生小区切换的数量下限值。网络实例的资源利用率阈值包括网络实例的资源利用率上限值或网络实例的资源利用率下限值。
结合第一方面或第二方面，在一些实现方式中，使用网络实例的用户的数量达到用户数量阈值包括：使用网络实例的用户的数量大于或等于用户数量上限值，或，小于或等于用户数量下限值。网络实例运行的分组数据单元会话数量达到分组数据单元会话数量阈值包括：网络实例运行的分组数据单元会话数量大于或等于分组数据单元会话数量上限值，或，小于或等于分组数据单元会话数量下限值。使用网络实例的用户单位时间内累积使用的流量阈值达到用户使用的流量阈值包括：使用网络实例的用户单位时间内累积使用的流量阈值大于或等于用户使用的流量上限值，或，小于或等于用户使用的流量下限值。网络实例的服务水平协议参数达到服务水平协议参数阈值包括：网络实例的服务水平协议参数大于或等于服务水平协议参数上限值，或，小于或等于服务水平协议参数下限值。网络实例的服务质量参数达到服务质量参数阈值包括：网络实例的服务质量参数大于或等于服务质量参数上限值，或，小于或等于服务质量参数下限值。网络实例的关键性能指标参数达到关键性能指标参数阈值包括：网络实例的关键性能指标参数大于或等于关键性能指标参数上限值，或，小于或等于关键性能指标参数下限值。使用网络实例的用户在单位地理位置区间内的平均移动速度达到平均移动速度阈值包括：使用网络实例的用户在单位地理位置区间内的平均移动速度大于或等于平均移动速度上限值，或，小于或等于平均移动速度下限值。使用网络实例的用户在单位时间内发生小区切换的数量达到发生小区切换的数量阈值包括：使用网络实例的用户在单位时间内发生小区切换的数量大于或等于发生小区切换的数量上限值，或，小于或等于发生小区切换的数量下限值。网络实例的资源利用率达到资源利用率阈值包括：网络实例的资源利用率大于或等于资源利用率上限值，或，小于或等于资源利用率下限值。
结合第一方面，在一些实现方式中，第一网络设备从第二网络设备接收第一管理请求之后，第一网络设备执行第一管理请求之前，还包括：第一网络设备判断第一管理请求是否可执行。若是，则在执行条件满足时，第一网络设备执行第一管理请求的步骤。
第三方面，本发明实施例提供了一种网络设备，该网络设备为第一网络设备。 该第一网络设备包括用于执行上述第一方面所描述的网络实例管理方法的模块或单元。
第四方面，本发明实施例提供了另一种网络设备，该网络设备为第二网络设备。该第二网络设备包括用于执行上述第二方面所描述的网络实例管理方法的模块或单元。
第五方面，本发明实施例提供了另一种网络设备，该网络设备为第一网络设备。该第一网络设备包括处理器、收发器和存储器。其中，所述处理器用于调用所述存储器存储的网络实例管理程序代码执行上述第一方面所提供的网络实例管理方法。
第六方面，本发明实施例提供了另一种网络设备，该网络设备为第二网络设备。该第二网络设备包括处理器、收发器和存储器。其中，所述处理器用于调用所述存储器存储的网络实例管理程序代码执行上述第二方面所提供的网络实例管理方法。
第七方面，本发明实施例提供了一种通信系统，包括：第一网络设备和第二网络设备。其中：第一网络设备为第三方面或第五方面所述的第一网络设备，第二网络设备为第四方面或第六方面所述的第二网络设备。
第八方面，本发明实施例提供了一种计算机存储介质，用于存储为上述第一方面所述的第一网络设备所用的计算机软件程序指令，所述程序指令当被所述第一网络设备执行时使所述第一网络设备执行如上述第一方面所述的方法。
第九方面，本发明实施例提供了另一种计算机存储介质，用于存储为上述第二方面所述的第二网络设备所用的计算机软件程序指令，所述程序指令当被所述第二网络设备执行时使所述第二网络设备执行如上述第二方面所述的方法。
第十方面，本发明实施例提供了一种计算机程序，该程序包括计算机软件程序指令，所述程序指令当被所述第一网络设备执行时使所述第一网络设备执行如上述第一方面所述的方法。
第十一方面，本发明实施例提供了另一种计算机程序，该程序包括计算机软件程序指令，所述程序指令当被所述第二网络设备执行时使所述第二网络设备执行如上述第二方面所述的方法。
附图说明
图1是本发明实施例涉及的一种网络系统的架构示意图；
图2是本发明实施例提供的一种网络实例管理方法的流程示意图；
图3是本发明实施例提供的一种网络设备的结构示意图；
图4是本发明实施例提供的另一种网络设备的结构示意图；
图5是本发明实施例提供的另一种网络设备的结构示意图；
图6是本发明实施例提供的另一种网络设备的结构示意图；
图7是本发明实施例提供的一种装置的结构示意图；
图8是本发明实施例提供的另一种装置的结构示意图。
具体实施方式
首先针对本发明实施例涉及的网络切片、网络切片实例、网络切片子网实例和网络功能这几个概念进行介绍。本发明实施例中所描述的网络实例包括网络切片实例、网络切片子网实例和网络功能中的至少一项。
网络切片(Network Slice，NS)指根据不同的服务需求定制化的、不同的逻辑网络。网络切片可以是一个包括了终端、接入网、传输网、核心网和应用服务器的完整的端到端网络，能够提供完整的电信服务，具有一定网络能力。网络切片也可以是上述终端、接入网、传输网、核心网和应用服务器的任意组合。
网络切片实例(Network Slice Instance，NSI)是对NS的实例化，即是一个真实运行的逻辑网络，能满足一定网络特性或服务需求。一个网络切片实例可以提供一种或多种服务。网络切片实例可以由网络切片管理功能设备创建，一个网络切片管理功能设备可以创建多个网络切片实例并同时对它们进行管理，包括在网络切片实例运行过程中的性能监视和故障管理等。当多个网络切片实例共存时，网络切片实例之间可以共享部分网络资源和网络功能。网络切片实例可以从网络切片模板创建，也可以不从网络切片模板创建。一个完整的网络切片实例是能够提供完整的端到端的网络服务的，而组成网络切片实例的可以是网络切片子网实例(Network Slice Subnet Instance，NSSI)和/或网络功能。网络功能可以包括物理网络功能和/或虚拟网络功能。以下统称物理网络功能和/或虚拟网络功能为网络功能。
一个网络切片实例可以划分为若干个网络切片子网实例，以方便网管系统管理。网络切片子网实例可以不需要提供端到端的完整的网络服务，网络切片子网实例可以是网络切片实例中同一个设备商的网络功能组成集合，也可以是按域划分的网络功能的集合，例如核心网网络切片子网实例、接入网网络切片子网实例，或由部署位置等其他方式组成集合。网络切片子网实例可以被多个网络切片实例共享。一个网络切片实例可以由若干网络切片子网实例组成，每个网络切片子网实例由若干网络功能和/或若干网络切片子网实例组成。一个网络切片实例可以由若干网络切片子网实例和没有被划分为网络切片子网实例的网络功能组成。一个网络切片实例也可以仅由若干网络功能组成。
网络功能(Network function，NF)是网络中的一种处理功能，定义了功能性的行为和接口。网络功能可以通过专用硬件实现，也可以通过在专用硬件上运行软件实现，也可以在通用的硬件平台上以虚拟功能的形式实现。因此，从实现的角度，可以将网络功能分为物理网络功能和虚拟网络功能。而从使用的角度，网络功能可以分为专属网络功能和共享网络功能。具体地，对于多个网络切片实例/网络切片子网实例而言，可以独立地使用不同的网络功能，这种网络功能称为专属网络功能，也可以共享同一个网络功能，这种网络功能称为共享网络功能。
请参见图1，是本发明实施例涉及的一种网络系统的架构示意图。如图1所示，网络系统100包括：通信业务管理功能(Communication Service Management  Function，CSMF)设备101、网络切片管理功能(Network Slice Management Functio，NSMF)设备102和网络切片子网管理功能(Network Slice Subnet Management Function，NSSMF)设备103。
其中，通信业务管理功能设备101，主要负责将运营商和/或第三方客户的通信服务需求转化为对网络切片的需求，并通过和网络切片管理功能设备102之间的接口向网络切片管理功能设备102发送对网络实例的管理请求(如创建、修改、配置、终结、激活、注销网络切片实例请求、性能测量任务请求、性能阈值监测请求和告警信息上报请求等)。通信业务管理功能设备101还用于从网络切片管理功能设备102获取网络实例的管理数据(如性能数据、故障数据等)，生成运行于网络切片实例之上的通信业务的管理数据。其中，故障数据包括告警数据，在本发明实施例中，告警数据与告警信息等同。通信业务管理功能设备101还可以接收运营商和/或第三方客户对网络切片管理数据和/或通信业务的管理数据的订阅需求等。
网络切片管理功能设备102，主要负责接收通信业务管理功能设备101发送的网络切片实例管理请求。网络切片管理功能设备102对网络切片实例的生命周期、性能、故障等进行管理(以下将生命周期、性能、故障管理简称为管理)，编排网络切片实例的组成，分解网络切片实例的需求为各网络切片子网实例和/或网络功能的需求，向各网络切片子网管理功能设备103发送网络切片子网实例管理请求。
网络切片子网管理功能设备103，主要负责接收网络切片管理功能设备102发送的网络切片子网实例和/或网络功能管理请求，对网络切片子网实例进行管理，编排网络切片子网实例的组成，分解网络切片子网实例的需求为各网络功能和/或嵌套网络切片子网实例的需求，可以向其他网络切片子网管理功能设备103发送嵌套网络切片子网实例管理请求。嵌套的意思是指一个网络切片子网实例可以由另一个或多个网络切片子网实例组成。
通信业务管理功能设备101和网络切片管理功能设备102存在接口1，网络切片管理功能设备102和网络切片子网管理功能设备103存在接口2。其中，接口1用于通信业务管理功能设备101向网络切片管理功能设备102发送网络切片实例管理请求。接口1还用于网络切片管理功能设备102向通信业务管理功能设备101反馈管理请求执行结果。接口1还用于网络切片管理功能设备102向通信业务管理功能设备101上报管理数据。接口2用于网络切片管理功能设备102向网络切片子网管理功能设备103发送网络切片子网实例管理请求和/或网络功能管理请求。接口2还用于网络切片子网管理功能设备103向网络切片管理功能设备102反馈管理请求执行结果。接口2还用于网络切片子网管理功能设备103向网络切片管理功能设备102上报管理数据。
需要说明的是，通信业务管理功能设备101、网络切片管理功能设备102、网络切片子网管理功能设备103、接口1和接口2还可以有其他名称，本发明实施例不作具体限定。在本发明实施例中，通信业务管理功能设备101、网络切片 管理功能设备102和网络切片子网管理功能设备103均是依据功能命名的，在具体应用中，通信业务管理功能设备101可以是具备通信业务管理功能的任意设备，网络切片管理功能设备102可以是具备网络切片管理功能的任意设备，网络切片子网管理功能设备103可以是具备网络切片子网管理功能的任意设备。
图1所示的通信架构为分层次的网络实例管理系统架构。
下面针对本发明实施例中涉及的创建请求、修改请求、配置请求、终结请求、激活请求、注销请求、性能测量任务请求、性能阈值监测请求和告警信息上报请求这几种管理请求进行介绍。
创建请求包括创建网络切片实例请求(create NSI request)、创建网络切片子网实例请求(create NSSI request)和创建网络功能请求(create NF request)。修改请求包括修改网络切片实例请求(modify NSI request)、修改网络切片子网实例请求(modify NSSI request)和修改网络功能请求(modify NF request)。配置请求包括配置网络切片实例请求(configure NSI request)、配置网络切片子网实例请求(configure NSSI request)和配置网络功能请求(configure NF request)。终结请求包括终结网络切片实例请求(terminate NSI request)、终结网络切片子网实例请求(terminate NSSI request)和终结网络功能请求(terminate NF request)。激活请求包括激活网络切片实例请求(activate NSI request)、激活网络切片子网实例请求(activate NSSI request)和激活网络功能请求(activate NF request)。注销请求包括注销网络切片实例请求(de-activate NSI request)、注销网络切片子网实例请求(de-activate NSSI request)和注销网络功能请求(de-activate NF request)。性能测量任务请求包括网络切片实例性能测量任务请求(NSI performance measurement job request)、网络切片子网实例性能测量任务请求(NSSI performance measurement job request)和网络功能性能测量任务请求(NF performance measurement job request)。性能阈值监测请求包括网络切片实例性能阈值监测请求(NSI threshold monitoring request)、网络切片子网实例性能阈值监测请求(NSSI threshold monitoring request)和网络功能性能阈值监测请求(NF threshold monitoring request)。告警信息上报请求包括网络切片实例告警信息上报请求(NSI get alarm information request)、网络切片子网实例告警信息上报测请求(NSSI get alarm information request)和网络功能告警信息上报请求(NF get alarm information request)。其中，创建网络切片实例请求、修改网络切片实例请求、配置网络切片实例请求、终结网络切片实例请求、激活网络切片实例请求、注销网络切片实例请求、网络切片实例性能测量任务请求、网络切片实例性能阈值监测请求和网络切片实例告警信息上报请求是通信业务管理功能设备101发送给网络切片管理功能设备102的，用于请求网络切片管理功能设备102对网络切片实例进行相应的管理。创建网络切片子网实例请求、修改网络切片子网实例请求、配置网络切片子网实例请求、终结网络切片子网实例请求、激活网络切片子网实例请求、注销网络切片子网实例请求、网络切片子网实例性能测量任务请求、网络切片子网实例性能阈值监测请求和网络切片子网实例告警信息上报请求是网络切片管理功能设备102发送给网络切片子网管理 功能设备103的，用于网络切片子网管理功能设备103对网络切片子网实例进行管理。创建网络功能请求、修改网络功能请求、配置网络功能请求、终结网络功能请求、激活网络功能请求、注销网络功能请求、网络功能性能测量任务请求、网络功能性能阈值监测请求和网络功能告警信息上报请求是网络切片管理功能设备102发送给网络切片子网管理功能设备103的，用于网络切片子网管理功能设备103对网络功能进行管理。
创建网络切片实例请求用于请求网络切片管理功能设备102创建一个网络切片实例。例如，创建网络切片子网实例和/或网络功能，或，重用已有的网络切片子网实例和/或网络功能。该创建网络切片实例请求中可以携带性能指标，网络切片管理功能设备102创建一个满足该性能指标的网络切片实例。
修改网络切片实例请求用于请求网络切片管理功能设备102对网络切片实例进行修改。修改网络切片实例请求具体可以包括增加网络切片实例的容量、缩小网络切片实例的容量、改变网络切片实例内的网络功能/网络切片子网实例间的拓扑、增加/删除网络切片实例内的网络功能/网络切片子网实例、更新组成网络切片实例的网络功能的软件版本等。修改网络切片实例请求中可以携带某一网络切片实例的标识，即NSI ID，用于指示网络切片管理功能设备102针对该NSI ID对应的网络切片实例进行相应修改。
配置网络切片实例请求用于请求网络切片管理功能设备102配置网络切片实例。例如，当该网络切片实例是接入与移动性管理功能(Access and Mobility Management Function，AMF)时，配置其身份标识，配置其支持的单个网络切片选择支撑信息(Single Network Slice Selection Assistant Information，S-NSSAI)。当该网络切片实例是统一数据管理(Unified Data Management，UDM)时，配置用户订阅信息。当该网络切片实例是网络功能库(Network Repository Function，NRF)时，配置新创建的网络功能信息等。配置涉及所有组成该网络切片实例的网络功能和/或网络切片子网实例。配置网络切片实例请求中可以携带某一网络切片实例的标识，即NSI ID，用于指示网络切片管理功能设备102针对该NSI ID对应的网络切片实例进行相应配置。
终结网络切片实例请求用于请求网络切片管理功能设备102终结网络切片实例的使用。例如，将网络切片实例占用的资源释放，删除网络切片实例的相关信息。终结网络切片实例请求中可以携带某一网络切片实例的标识，即NSI ID，用于指示网络切片管理功能设备102终结该NSI ID对应的网络切片实例，即不再使用该网络切片实例。
激活网络切片实例请求用于请求网络切片管理功能设备102激活网络切片实例的使用。激活网络切片实例请求中可以携带某一网络切片实例的标识，即NSI ID，用于指示网络切片管理功能设备102将该NSI ID对应的网络切片实例激活，即继续使用该网络切片实例。
注销网络切片实例请求用于请求网络切片管理功能设备102注销网络切片实例。例如，暂停使用该网络切片实例，即不释放该网络切片实例占用的网络资 源，保存该网络切片实例的相关信息。注销网络切片实例请求中可以携带某一网络切片实例的标识，即NSI ID，用于指示网络切片管理功能设备102将该NSI ID对应的网络切片实例注销，即暂停使用该网络切片实例。
网络切片实例性能测量任务请求用于请求网络切片管理功能设备102对网络切片实例的性能进行测量。网络切片实例性能测量任务请求中可以携带某一网络切片实例的标识，即NSI ID，用于指示网络切片管理功能设备102对该NSI ID对应的网络切片实例的性能进行测量。网络切片实例性能测量任务请求中还可以携带性能指标的标识，用于指示对该性能指标进行测量。性能指标可以是时延、用户数、分组数据单元(Packet Data Unit，PDU)会话(session)数、带宽、资源利用率等。网络切片管理功能设备102可以将测量到的性能数据上报给通信业务管理功能设备101。
网络切片实例性能阈值监测请求用于请求网络切片管理功能设备102对网络切片实例的性能阈值进行监测，即监测网络切片实例的性能是否达到预设阈值。网络切片实例性能阈值监测请求中可以携带某一网络切片实例的标识，即NSI ID，用于指示网络切片管理功能设备102对该NSI ID对应的网络切片实例的性能阈值进行监测。网络切片实例性能阈值监测请求中还可以携带性能指标的标识，用于指示监测的性能指标。网络切片实例性能阈值监测请求中还可以携带具体的阈值，如上限阈值，下限阈值。当该网络切片实例的性能达到预设阈值时，网络切片管理功能设备102可以通知通信业务管理功能设备101。
网络切片实例告警信息上报请求用于请求网络切片管理功能设备102对网络切片实例的告警信息进行上报。网络切片实例告警信息上报请求中可以携带某一网络切片实例的标识，即NSI ID，用于指示网络切片管理功能设备102将该NSI ID对应的网络切片实例的告警信息上报给通信业务管理功能设备101。网络切片实例告警信息上报请求中还可以携带一个过滤器(filter)用于限定/过滤需要上报的告警信息。
创建网络切片子网实例请求用于请求网络切片子网管理功能设备103创建一个网络切片子网实例。例如，创建网络切片子网实例和/或网络功能，或，重用已有的网络切片子网实例和/或网络功能。该创建网络切片子网实例请求中可以携带性能指标，网络切片子网管理功能设备103创建一个满足该性能指标的网络切片子网实例。
修改网络切片子网实例请求用于请求网络切片子网管理功能设备103对网络切片子网实例进行修改。修改网络切片子网实例请求具体可以包括增加网络切片子网实例的容量、缩小网络切片子网实例的容量、改变网络切片子网实例内的网络功能/嵌套的网络切片子网实例间的拓扑、增加/删除网络切片子网实例内的网络功能/嵌套的网络切片子网实例、更新组成网络切片子网实例的网络功能的软件版本等。修改网络切片子网实例请求中可以携带某一网络切片子网实例的标识，即NSSI ID，用于指示网络切片子网管理功能设备103针对该NSSI ID对应的网络切片子网实例进行相应修改。
配置网络切片子网实例请求用于请求网络切片子网管理功能设备103配置网络切片子网实例。例如，当该网络切片子网实例是接入与移动性管理功能时，配置其身份标识，配置其支持的单个网络切片选择支撑信息。当该网络切片子网实例是统一数据管理时，配置用户订阅信息。当该网络切片子网实例是网络功能库时，配置新创建的网络功能信息等。配置涉及所有组成该网络切片子网实例的网络功能和/或网络切片子网实例。配置网络切片子网实例请求中可以携带某一网络切片子网实例的标识，即NSSI ID，用于指示网络切片子网管理功能设备103针对该NSSI ID对应的网络切片子网实例进行相应配置。
终结网络切片子网实例请求用于请求网络切片子网管理功能设备103终结网络切片子网实例的使用。例如，将网络切片子网实例占用的资源释放，删除网络切片子网实例的相关信息。终结网络切片子网实例请求中可以携带某一网络切片子网实例的标识，即NSSI ID，用于指示网络切片子网管理功能设备103终结该NSSI ID对应的网络切片子网实例，即不再使用该网络切片子网实例。
激活网络切片子网实例请求用于请求网络切片子网管理功能设备103激活网络切片子网实例的使用。激活网络切片子网实例请求中可以携带某一网络切片子网实例的标识，即NSSI ID，用于指示网络切片子网管理功能设备103将该NSSI ID对应的网络切片子网实例激活，即继续使用该网络切片子网实例。
注销网络切片子网实例请求用于请求网络切片子网管理功能设备103注销网络切片子网实例。例如，暂停使用网络切片子网实例，但不释放该网络切片子网实例占用的网络资源，保存该网络切片子网实例的相关信息。注销网络切片子网实例请求中可以携带某一网络切片子网实例的标识，即NSSI ID，用于指示网络切片子网管理功能设备103将该NSSI ID对应的网络切片子网实例注销，即暂停使用该网络切片子网实例。
网络切片子网实例性能测量任务请求用于请求网络切片子网管理功能设备103对网络切片子网实例的性能进行测量。网络切片子网实例性能测量任务请求中可以携带某一网络切片子网实例的标识，即NSSI ID，用于指示网络切片子网管理功能设备103对该NSSI ID对应的网络切片子网实例的性能进行测量。网络切片子网实例性能测量任务请求中还可以携带性能指标的标识，用于指示对该性能指标进行测量。性能指标的例子可以是时延、用户数、分组数据单元会话数、带宽、资源利用率等。网络切片子网管理功能设备103可以将测量到的性能数据上报给网络切片管理功能设备102。
网络切片子网实例性能阈值监测请求用于请求网络切片子网管理功能设备103对网络切片子网实例的性能阈值进行监测，即监测网络切片子网实例的性能是否达到预设阈值。网络切片子网实例性能阈值监测请求中可以携带某一网络切片子网实例的标识，即NSSI ID，用于指示网络切片子网管理功能设备103对该NSSI ID对应的网络切片子网实例的性能阈值进行监测。网络切片子网实例性能阈值监测请求中还可以携带性能指标的标识，用于指示监测的性能指标。网络切片子网实例性能阈值监测请求中还可以携带具体的阈值，如上限阈值，下限阈值。 当该网络切片子网实例的性能达到预设阈值时，网络切片子网管理功能设备103可以通知给网络切片管理功能设备102。
网络切片子网实例告警信息上报请求用于请求网络切片子网管理功能设备103对网络切片子网实例的告警信息进行上报。网络切片子网实例告警信息上报请求中可以携带某一网络切片子网实例的标识，即NSSI ID，用于指示网络切片子网管理功能设备103将该NSSI ID对应的网络切片子网实例的告警信息上报给网络切片管理功能设备102。网络切片子网实例告警信息上报请求中还可以携带一个过滤器(filter)用于限定/过滤需要上报的告警信息。
创建网络功能请求用于请求网络切片子网管理功能设备103创建一个网络功能。该创建网络功能请求中可以携带性能指标，网络切片子网管理功能设备103创建一个满足该性能指标的网络功能。
修改网络功能请求用于请求网络切片子网管理功能设备103对网络功能进行修改。修改网络功能请求具体可以包括增加网络功能的容量/资源、缩小网络功能的容量/资源、更新该网络功能的软件版本等。修改网络功能请求中可以携带某一网络功能的标识，即NF ID，用于指示网络切片子网管理功能设备103针对该NF ID对应的网络功能进行相应修改。
配置网络功能请求用于请求网络切片子网管理功能设备103配置网络功能。例如，当该网络功能是接入与移动性管理功能时，配置其身份标识，配置其支持的单个网络切片选择支撑信息。当该网络功能是统一数据管理时，配置用户订阅信息。当该网络功能是网络功能库时，配置新创建的网络功能信息等。配置网络功能请求中可以携带某一网络功能的标识，即NF ID，用于指示网络切片子网管理功能设备103针对该NF ID对应的网络功能进行配置。
终结网络功能请求用于请求网络切片子网管理功能设备103终结网络功能的使用。例如，将网络功能占用的资源释放，删除网络功能的相关信息。终结网络功能请求中可以携带某一网络功能的标识，即NF ID，用于指示网络切片子网管理功能设备103终结该NF ID对应的网络功能，即不再使用该网络功能。
激活网络功能请求用于请求网络切片子网管理功能设备103激活网络功能的使用。激活网络功能请求中可以携带某一网络功能的标识，即NF ID，用于指示网络切片子网管理功能设备103将该NF ID对应的网络功能激活，即继续使用该网络功能。
注销网络功能请求用于请求网络切片子网管理功能设备103注销网络功能。例如，暂停使用该网络功能，但不释放该网络功能占用的网络资源，保存该网络功能的相关信息。注销网络功能请求中可以携带某一网络功能的标识，即NF ID，用于指示网络切片子网管理功能设备103将该NF ID对应的网络功能注销，即暂停使用该网络功能。
网络功能性能测量任务请求用于请求网络切片子网管理功能设备103对网络功能的性能进行测量。网络功能性能测量任务请求中可以携带某一网络功能的标识，即NF ID，用于指示网络切片子网管理功能设备103对该NF ID对应的网 络功能的性能进行测量。网络功能性能测量任务请求中还可以携带性能指标的标识，用于指示对该性能指标进行测量。性能指标的例子可以是时延、用户数、分组数据单元会话数、带宽、资源利用率等。网络切片子网管理功能设备103可以将测量到的性能数据上报给网络切片管理功能设备102。
网络功能性能阈值监测请求用于请求网络切片子网管理功能设备103对网络功能的性能阈值进行监测，即监测网络功能的性能是否达到预设阈值。网络功能性能阈值监测请求中可以携带某一网络功能的标识，即NF ID，用于指示网络切片子网管理功能设备103对该NF ID对应的网络功能的性能阈值进行监测。网络功能性能阈值监测请求中还可以携带性能指标的标识，用于指示监测的性能指标。网络功能性能阈值监测请求中还可以携带具体的阈值，如上限阈值，下限阈值。当该网络功能的性能达到预设阈值时，网络切片子网管理功能设备103可以通知给网络切片管理功能设备102。
网络功能告警信息上报请求用于请求网络切片子网管理功能设备103对网络功能的告警信息进行上报。网络功能告警信息上报请求中可以携带某一网络功能的标识，即NF ID，用于指示网络切片子网管理功能设备103将该NF ID对应的网络功能的告警信息上报给网络切片管理功能设备102。网络功能告警信息上报请求中还可以携带一个过滤器(filter)用于限定/过滤需要上报的告警信息。
基于上述图1所述的通信架构示意图，图2为本发明实施例提供的一种网络实例管理方法的流程图。该网络实例管理方法包括但不限于如下步骤S201-S203。
S201：第二网络设备确定第一管理请求，第一管理请求包括执行条件的参数，该参数与网络实例相关。
本发明实施例中，第二网络设备生成或者从其他设备获取第一管理请求。所述网络实例包括以下至少一项：网络切片实例、网络切片子网实例和网络功能。
S202：第二网络设备向第一网络设备发送第一管理请求，第一管理请求用于指示对网络实例进行管理。
本发明实施例可以应用于至少如下两种场景。场景一、第一网络设备为网络切片管理功能设备，第二网络设备为通信业务管理功能设备。在这种场景中，网络实例具体可以是网络切片实例。场景二、第一网络设备为网络切片子网管理功能设备，第二网络设备为网络切片管理功能设备。在这种场景中，网络实例具体可以是网络切片子网实例和/或网络功能。以下针对这两种场景分别进行详细描述。
针对场景一来说，通信业务管理功能设备向网络切片管理功能设备发送第一管理请求，该第一管理请求用于指示网络切片管理功能设备对网络切片实例进行管理。该第一管理请求包括以下任一项：创建网络切片实例请求、修改网络切片实例请求、配置网络切片实例请求、终结网络切片实例请求、激活网络切片实例请求、注销网络切片实例请求、网络切片实例性能测量任务请求、网络切片实例性能阈值监测请求和网络切片实例告警信息上报请求。
在场景一中，不同的管理请求携带的执行条件的参数可以相同，也可以不同。以下针对上述各种管理请求各自携带的执行条件的参数分别进行描述。
创建网络切片实例请求中携带的执行条件的参数包括如下至少一种：第三方管理模块的标识、其他管理请求标识、执行时间和执行等待时间。第三方管理模块可以是客户的网络管理模块，第三方管理模块和网络切片管理功能设备之间存在直接接口，或者通过一个安全代理和网络切片管理功能设备交互。例如，创建网络切片实例请求携带其他管理请求标识，该其他管理请求可以是终结另一网络切片实例的管理请求，网络切片管理功能设备需要在另一网络切片实例终结后执行创建网络切片实例的动作。
修改网络切片实例请求中携带的执行条件的参数包括如下至少一种：使用网络切片实例的用户数量上限值、使用网络切片实例的用户数量下限值、网络切片实例运行的分组数据单元会话数量上限值、网络切片实例运行的分组数据单元会话数量下限值、使用网络切片实例的用户使用的流量上限值、使用网络切片实例的用户使用的流量下限值、网络切片实例的服务水平协议(Service Level Agreement，SLA)参数上限值、网络切片实例的服务水平协议参数下限值、网络切片实例的服务质量(Quality of Service，QoS)参数上限值、网络切片实例的服务质量参数下限值、网络切片实例的关键性能指标(Key Performance Indicator，KPI)参数上限值、网络切片实例的关键性能指标参数下限值、第三方管理模块的标识、使用网络切片实例的用户在单位地理位置区间内的平均移动速度上限值、使用网络切片实例的用户在单位地理位置区间内的平均移动速度下限值、使用网络切片实例的用户在单位时间内发生小区切换的数量上限值、使用网络切片实例的用户在单位时间内发生小区切换的数量下限值、网络切片实例的故障告警类型标识、网络切片实例的故障告警严重性标识、网络切片实例的故障事件标识、网络切片实例的资源利用率上限值、网络切片实例的资源利用率下限值、其他管理请求标识、执行时间和执行等待时间。例如，修改网络切片实例请求携带用户数量上限值200。
配置网络切片实例请求中携带的执行条件的参数包括如下至少一种：使用网络切片实例的用户数量上限值、使用网络切片实例的用户数量下限值、网络切片实例运行的分组数据单元会话数量上限值、网络切片实例运行的分组数据单元会话数量下限值、使用网络切片实例的用户使用的流量上限值、使用网络切片实例的用户使用的流量下限值、网络切片实例的服务水平协议参数上限值、网络切片实例的服务水平协议参数下限值、网络切片实例的服务质量参数上限值、网络切片实例的服务质量参数下限值、网络切片实例的关键性能指标参数上限值、网络切片实例的关键性能指标参数下限值、第三方管理模块的标识、使用网络切片实例的用户在单位地理位置区间内的平均移动速度上限值、使用网络切片实例的用户在单位地理位置区间内的平均移动速度下限值、使用网络切片实例的用户在单位时间内发生小区切换的数量上限值、使用网络切片实例的用户在单位时间内发生小区切换的数量下限值、网络切片实例的故障告警类型标识、网络切片实例的 故障告警严重性标识、网络切片实例的故障事件标识、网络切片实例的资源利用率上限值、网络切片实例的资源利用率下限值、其他管理请求标识、执行时间和执行等待时间。例如，配置网络切片实例请求携带用户数量上限值200和PDU session数量上限值1000。
终结网络切片实例请求中携带的执行条件的参数包括如下至少一种：使用网络切片实例的用户数量下限值、网络切片实例运行的分组数据单元会话数量下限值、第三方管理模块的标识、网络切片实例故障告警类型标识、网络切片实例故障告警严重性标识、网络切片实例的故障事件标识、网络切片实例的资源利用率下限值、其他管理请求标识、执行时间和执行等待时间。例如，终结网络切片实例请求携带用户数量下限值10。
激活网络切片实例请求中携带的执行条件的参数包括如下至少一种：第三方管理模块的标识、其他管理请求标识、激活网络切片实例请求的执行时间和激活网络切片实例请求的执行等待时间。例如，激活网络切片实例请求携带第三方管理模块的标识，该第三方管理模块可以是客户的网络管理模块，第三方管理模块和网络切片管理功能设备之间存在直接接口，或者通过一个安全代理和网络切片管理功能设备交互。
注销网络切片实例请求中携带的执行条件的参数包括如下至少一种：使用网络切片实例的用户数量下限值、网络切片实例运行的PDU session数量下限值、第三方管理模块的标识、网络切片实例故障告警类型标识、网络切片实例故障告警严重性标识、网络切片实例的故障事件标识、网络切片实例的资源利用率下限值、其他管理请求标识、执行时间和执行等待时间。例如，注销网络切片实例请求携带PDU session数量下限值10。
网络切片实例性能测量任务请求中携带的执行条件的参数包括如下至少一种：使用网络切片实例的用户数量上限值、使用网络切片实例的用户数量下限值、网络切片实例运行的分组数据单元会话数量上限值、网络切片实例运行的分组数据单元会话数量下限值、网络切片实例的服务水平协议参数上限值、网络切片实例的服务水平协议参数下限值、网络切片实例的服务质量参数上限值、网络切片实例的服务质量参数下限值、网络切片实例的关键性能指标参数上限值、网络切片实例的关键性能指标参数下限值、第三方管理模块的标识、使用网络切片实例的用户在单位地理位置区间内的平均移动速度上限值、使用网络切片实例的用户在单位地理位置区间内的平均移动速度下限值、使用网络切片实例的用户在单位时间内发生小区切换的数量上限值、使用网络切片实例的用户在单位时间内发生小区切换的数量下限值、网络切片实例的故障告警类型标识、网络切片实例的故障告警严重性标识、网络切片实例的故障事件标识、网络切片实例的资源利用率上限值、网络切片实例的资源利用率下限值、其他管理请求标识、执行时间和执行等待时间。例如，网络切片实例性能测量任务请求携带用户数量上限值200和PDU session数量上限值1000。
网络切片实例性能阈值监测请求中携带的执行条件的参数包括如下至少一 种：使用网络切片实例的用户数量上限值、使用网络切片实例的用户数量下限值、网络切片实例运行的分组数据单元会话数量上限值、网络切片实例运行的分组数据单元会话数量下限值、网络切片实例的服务水平协议参数上限值、网络切片实例的服务水平协议参数下限值、网络切片实例的服务质量参数上限值、网络切片实例的服务质量参数下限值、网络切片实例的关键性能指标参数上限值、网络切片实例的关键性能指标参数下限值、第三方管理模块的标识、使用网络切片实例的用户在单位地理位置区间内的平均移动速度上限值、使用网络切片实例的用户在单位地理位置区间内的平均移动速度下限值、使用网络切片实例的用户在单位时间内发生小区切换的数量上限值、使用网络切片实例的用户在单位时间内发生小区切换的数量下限值、网络切片实例的故障告警类型标识、网络切片实例的故障告警严重性标识、网络切片实例的故障事件标识、网络切片实例的资源利用率上限值、网络切片实例的资源利用率下限值、其他管理请求标识、执行时间和执行等待时间。例如，网络切片实例性能阈值监测请求携带用户数量上限值200和PDU session数量上限值1000。
网络切片实例告警信息上报请求中携带的执行条件的参数包括如下至少一种：使用网络切片实例的用户数量上限值、使用网络切片实例的用户数量下限值、网络切片实例运行的分组数据单元会话数量上限值、网络切片实例运行的分组数据单元会话数量下限值、网络切片实例的服务水平协议参数上限值、网络切片实例的服务水平协议参数下限值、网络切片实例的服务质量参数上限值、网络切片实例的服务质量参数下限值、网络切片实例的关键性能指标参数上限值、网络切片实例的关键性能指标参数下限值、第三方管理模块的标识、使用网络切片实例的用户在单位地理位置区间内的平均移动速度上限值、使用网络切片实例的用户在单位地理位置区间内的平均移动速度下限值、使用网络切片实例的用户在单位时间内发生小区切换的数量上限值、使用网络切片实例的用户在单位时间内发生小区切换的数量下限值、网络切片实例的故障告警类型标识、网络切片实例的故障告警严重性标识、网络切片实例的故障事件标识、网络切片实例的资源利用率上限值、网络切片实例的资源利用率下限值、其他管理请求标识、执行时间和执行等待时间。例如，网络切片实例告警信息上报请求携带软件故障标识和严重故障标识。
其中，SLA/QoS/KPI参数可以是时延、吞吐率、掉话率、丢包率、小区间切换成功率等。资源是指分配给网络切片实例的计算、存储或网络资源。故障类型包括单板故障、软件故障、通信故障等，故障类型不同，标识不同。故障严重性包括严重(critical)故障、主要(major)故障、次要(minor)故障。故障事件包括硬件故障、过载等。其中，使用网络切片实例的用户使用的流量上限值还可以具体分为用户当日使用的流量上限值、当月使用的流量上限值或历史累计使用的流量上限值。使用网络切片实例的用户使用的流量下限值还可以具体分为用户当日使用的流量下限值、当月使用的流量下限值或历史累计使用的流量下限值。
针对场景二来说，网络切片管理功能设备向网络切片子网管理功能设备发送 第一管理请求，该第一管理请求用于指示网络切片子网管理功能设备对网络切片子网实例和/或网络功能进行管理。该第一管理请求包括以下任一项：创建网络切片子网实例请求、修改网络切片子网实例请求、配置网络切片子网实例请求、终结网络切片子网实例请求、激活网络切片子网实例请求、注销网络切片子网实例请求、网络切片子网实例性能测量任务请求、网络切片子网实例性能阈值监测请求、网络切片子网实例告警信息上报请求、创建网络功能请求、修改网络功能请求、配置网络功能请求、终结网络功能请求、激活网络功能请求、注销网络功能请求、网络功能性能测量任务请求、网络功能性能阈值监测请求、网络功能告警信息上报请求。
在场景二中，不同的管理请求携带的执行条件的参数可以相同，也可以不同。以下针对上述各个管理请求各自携带的执行条件的参数分别进行描述。
创建网络切片子网实例请求中携带的执行条件的参数包括如下至少一种：第三方管理模块的标识、网络切片子网实例故障告警类型标识、网络切片子网实例的故障事件标识、网络切片子网实例的资源利用率上限值、其他管理请求标识、执行时间和执行等待时间。这里，网络切片子网实例故障告警类型指组成该网络切片子网实例的其他现有网络切片子网实例故障告警，如过载告警，不是待创建的网络切片子网实例故障告警。网络切片子网实例的资源利用率上限值指组成该网络切片子网实例的其他现有网络切片子网实例的资源利用率上限值，不是待创建的网络切片子网实例的资源利用率上限值。例如，创建网络切片子网实例请求携带其他管理请求标识，该其他管理请求可以是终结/修改另一网络切片子网实例的管理请求。网络切片子网管理功能设备需要在另一网络切片子网实例终结/修改后执行创建网络切片子网实例的动作。
修改网络切片子网实例请求中携带的执行条件的参数包括如下至少一种：接入网络切片子网实例的用户数量上限值、接入网络切片子网实例的用户数量下限值、网络切片子网实例运行的分组数据单元会话数量上限值、网络切片子网实例运行的分组数据单元会话数量下限值、接入网络切片子网实例的用户使用的流量上限值、接入网络切片子网实例的用户使用的流量下限值、网络切片子网实例的服务水平协议参数上限值、网络切片子网实例的服务水平协议参数下限值、网络切片子网实例的服务质量参数上限值、网络切片子网实例的服务质量参数下限值、网络切片子网实例的关键性能指标参数上限值、网络切片子网实例的关键性能指标参数下限值、第三方管理模块的标识、接入网络切片子网实例的用户在单位地理位置区间内的平均移动速度上限值、接入网络切片子网实例的用户在单位地理位置区间内的平均移动速度下限值、接入网络切片子网实例的用户在单位时间内发生小区切换的数量上限值、接入网络切片子网实例的用户在单位时间内发生小区切换的数量下限值、网络切片子网实例的故障告警类型标识、网络切片子网实例的故障告警严重性标识、网络切片子网实例的故障事件标识、网络切片子网实例的资源利用率上限值、网络切片子网实例的资源利用率下限值、其他管理请求标识、执行时间和执行等待时间。其中，资源是指分配给网络切片子网实例的计 算、存储或网络资源。例如，修改网络切片子网实例请求携带用户数量上限值200。
配置网络切片子网实例请求中携带的执行条件的参数包括如下至少一种：接入网络切片子网实例的用户数量上限值、接入网络切片子网实例的用户数量下限值、网络切片子网实例运行的分组数据单元会话数量上限值、网络切片子网实例运行的分组数据单元会话数量下限值、接入网络切片子网实例的用户使用的流量上限值、接入网络切片子网实例的用户使用的流量下限值、网络切片子网实例的服务水平协议参数上限值、网络切片子网实例的服务水平协议参数下限值、网络切片子网实例的服务质量参数上限值、网络切片子网实例的服务质量参数下限值、网络切片子网实例的关键性能指标参数上限值、网络切片子网实例的关键性能指标参数下限值、第三方管理模块的标识、接入网络切片子网实例的用户在单位地理位置区间内的平均移动速度上限值、接入网络切片子网实例的用户在单位地理位置区间内的平均移动速度下限值、接入网络切片子网实例的用户在单位时间内发生小区切换的数量上限值、接入网络切片子网实例的用户在单位时间内发生小区切换的数量下限值、网络切片子网实例的故障告警类型标识、网络切片子网实例的故障告警严重性标识、网络切片子网实例的故障事件标识、网络切片子网实例的资源利用率上限值、网络切片子网实例的资源利用率下限值、其他管理请求标识、执行时间和执行等待时间。例如，配置网络切片子网实例请求携带用户数量上限值200和PDU session数量上限值1000。
终结网络切片子网实例请求中携带的执行条件的参数包括如下至少一种：接入网络切片子网实例的用户数量下限值、网络切片子网实例运行的分组数据单元会话数量下限值、第三方管理模块的标识、网络切片子网实例故障告警类型标识、网络切片子网实例故障告警严重性标识、网络切片子网实例的故障事件标识、网络切片子网实例的资源利用率下限值、其他管理请求标识、执行时间和执行等待时间。例如，终结网络切片子网实例请求携带用户数量下限值10。
激活网络切片子网实例请求中携带的执行条件的参数包括如下至少一种：第三方管理模块的标识、网络切片子网实例故障告警类型标识、网络切片子网实例的故障事件标识、网络切片子网实例的资源利用率上限值、其他管理请求标识、执行时间和执行等待时间。这里，网络切片子网实例故障告警类型指组成该网络切片子网实例的其他现有网络切片子网实例故障告警，如过载告警，不是待创建的网络切片子网实例故障告警。网络切片子网实例的资源利用率上限值指组成该网络切片子网实例的其他现有网络切片子网实例的资源利用率上限值，不是待创建的网络切片子网实例的资源利用率上限值。例如，激活网络切片子网实例请求携带第三方管理模块的标识，第三方管理模块可以是客户的网络管理模块，第三方管理模块和网络切片子网管理功能设备之间存在直接接口，或者通过一个安全代理和网络切片子网管理功能设备交互。第三方管理模块还可以是管理另一个网络切片实例/网络切片子网实例的管理设备，该网络切片实例/网络切片子网实例和待管理的网络切片子网实例共享网络功能/网络切片子网实例。
注销网络切片子网实例请求中携带的执行条件的参数包括如下至少一种：第三方管理模块的标识、网络切片子网实例故障告警类型标识、网络切片子网实例的故障事件标识、网络切片子网实例的资源利用率下限值、其他管理请求标识、执行时间和执行等待时间。这里，网络切片子网实例故障告警类型指组成该网络切片子网实例的其他现有网络切片子网实例故障告警，如过载告警，不是待创建的网络切片子网实例故障告警。网络切片子网实例的资源利用率下限值指组成该网络切片子网实例的其他现有网络切片子网实例的资源利用率下限值，不是待创建的网络切片子网实例的资源利用率下限值。例如，注销网络切片子网实例请求携带PDU session数量下限值10。
网络切片子网实例性能测量任务请求中携带的执行条件的参数包括如下至少一种：接入网络切片子网实例的用户数量上限值、接入网络切片子网实例的用户数量下限值、网络切片子网实例运行的分组数据单元会话数量上限值、网络切片子网实例运行的分组数据单元会话数量下限值、网络切片子网实例的服务水平协议参数上限值、网络切片子网实例的服务水平协议参数下限值、网络切片子网实例的服务质量参数上限值、网络切片子网实例的服务质量参数下限值、网络切片子网实例的关键性能指标参数上限值、网络切片子网实例的关键性能指标参数下限值、第三方管理模块的标识、接入网络切片子网实例的用户在单位地理位置区间内的平均移动速度上限值、接入网络切片子网实例的用户在单位地理位置区间内的平均移动速度下限值、接入网络切片子网实例的用户在单位时间内发生小区切换的数量上限值、接入网络切片子网实例的用户在单位时间内发生小区切换的数量下限值、网络切片子网实例的故障告警类型标识、网络切片子网实例的故障告警严重性标识、网络切片子网实例的故障事件标识、网络切片子网实例的资源利用率上限值、网络切片子网实例的资源利用率下限值、其他管理请求标识、执行时间和执行等待时间。例如，网络切片子网实例性能测量任务请求携带用户数量上限值200和PDU session数量上限值1000。
网络切片子网实例性能阈值监测请求中携带的执行条件的参数包括如下至少一种：接入网络切片子网实例的用户数量上限值、接入网络切片子网实例的用户数量下限值、网络切片子网实例运行的分组数据单元会话数量上限值、网络切片子网实例运行的分组数据单元会话数量下限值、网络切片子网实例的服务水平协议参数上限值、网络切片子网实例的服务水平协议参数下限值、网络切片子网实例的服务质量参数上限值、网络切片子网实例的服务质量参数下限值、网络切片子网实例的关键性能指标参数上限值、网络切片子网实例的关键性能指标参数下限值、第三方管理模块的标识、接入网络切片子网实例的用户在单位地理位置区间内的平均移动速度上限值、接入网络切片子网实例的用户在单位地理位置区间内的平均移动速度下限值、接入网络切片子网实例的用户在单位时间内发生小区切换的数量上限值、接入网络切片子网实例的用户在单位时间内发生小区切换的数量下限值、网络切片子网实例的故障告警类型标识、网络切片子网实例的故障告警严重性标识、网络切片子网实例的故障事件标识、网络切片子网实例的资 源利用率上限值、网络切片子网实例的资源利用率下限值、其他管理请求标识、执行时间和执行等待时间。例如，网络切片子网实例性能阈值监测请求携带用户数量上限值200和PDU session数量上限值1000。
网络切片子网实例告警信息上报请求中携带的执行条件的参数包括如下至少一种：接入网络切片子网实例的用户数量上限值、接入网络切片子网实例的用户数量下限值、网络切片子网实例运行的分组数据单元会话数量上限值、网络切片子网实例运行的分组数据单元会话数量下限值、网络切片子网实例的服务水平协议参数上限值、网络切片子网实例的服务水平协议参数下限值、网络切片子网实例的服务质量参数上限值、网络切片子网实例的服务质量参数下限值、网络切片子网实例的关键性能指标参数上限值、网络切片子网实例的关键性能指标参数下限值、第三方管理模块的标识、接入网络切片子网实例的用户在单位地理位置区间内的平均移动速度上限值、接入网络切片子网实例的用户在单位地理位置区间内的平均移动速度下限值、接入网络切片子网实例的用户在单位时间内发生小区切换的数量上限值、接入网络切片子网实例的用户在单位时间内发生小区切换的数量下限值、网络切片子网实例的故障告警类型标识、网络切片子网实例的故障告警严重性标识、网络切片子网实例的故障事件标识、网络切片子网实例的资源利用率上限值、网络切片子网实例的资源利用率下限值、其他管理请求标识、执行时间和执行等待时间。例如，网络切片子网实例告警信息上报请求携带软件故障标识和严重故障标识。
创建网络功能请求中携带的执行条件的参数包括如下至少一种：第三方管理模块的标识、网络功能故障告警类型标识、网络功能的故障事件标识、网络功能的资源利用率上限值、其他管理请求标识、执行时间和执行等待时间。这里，网络功能故障告警类型指组成该网络功能的其他现有网络功能故障告警，如过载告警，不是待创建的网络功能故障告警。网络功能的资源利用率上限值指组成该网络功能的其他现有网络功能的资源利用率上限值，不是待创建的网络功能的资源利用率上限值。例如，创建网络功能请求携带其他管理请求标识，该其他管理请求可以是终结/修改另一网络功能的管理请求。网络切片子网管理功能设备需要在另一网络功能终结/修改后执行创建网络功能的动作。
修改网络功能请求中携带的执行条件的参数包括如下至少一种：接入网络功能的用户数量上限值、接入网络功能的用户数量下限值、网络功能运行的分组数据单元会话数量上限值、网络功能运行的分组数据单元会话数量下限值、接入网络功能的用户使用的流量上限值、接入网络功能的用户使用的流量下限值、网络功能的服务水平协议参数上限值、网络功能的服务水平协议参数下限值、网络功能的服务质量参数上限值、网络功能的服务质量参数下限值、网络功能的关键性能指标参数上限值、网络功能的关键性能指标参数下限值、第三方管理模块的标识、接入网络功能的用户在单位地理位置区间内的平均移动速度上限值、接入网络功能的用户在单位地理位置区间内的平均移动速度下限值、接入网络功能的用户在单位时间内发生小区切换的数量上限值、接入网络功能的用户在单位时间内 发生小区切换的数量下限值、网络功能的故障告警类型标识、网络功能的故障告警严重性标识、网络功能的故障事件标识、网络功能的资源利用率上限值、网络功能的资源利用率下限值、其他管理请求标识、执行时间和执行等待时间。其中，资源是指分配给网络功能的计算、存储或网络资源。例如，修改网络功能请求携带用户数量上限值200。
配置网络功能请求中携带的执行条件的参数包括如下至少一种：接入网络功能的用户数量上限值、接入网络功能的用户数量下限值、网络功能运行的分组数据单元会话数量上限值、网络功能运行的分组数据单元会话数量下限值、接入网络功能的用户使用的流量上限值、接入网络功能的用户使用的流量下限值、网络功能的服务水平协议参数上限值、网络功能的服务水平协议参数下限值、网络功能的服务质量参数上限值、网络功能的服务质量参数下限值、网络功能的关键性能指标参数上限值、网络功能的关键性能指标参数下限值、第三方管理模块的标识、接入网络功能的用户在单位地理位置区间内的平均移动速度上限值、接入网络功能的用户在单位地理位置区间内的平均移动速度下限值、接入网络功能的用户在单位时间内发生小区切换的数量上限值、接入网络功能的用户在单位时间内发生小区切换的数量下限值、网络功能的故障告警类型标识、网络功能的故障告警严重性标识、网络功能的故障事件标识、网络功能的资源利用率上限值、网络功能的资源利用率下限值、其他管理请求标识、执行时间和执行等待时间。例如，配置网络功能请求携带用户数量上限值200和PDU session数量上限值1000。
终结网络功能请求中携带的执行条件的参数包括如下至少一种：接入网络功能的用户数量下限值、网络功能运行的分组数据单元会话数量下限值、第三方管理模块的标识、网络功能故障告警类型标识、网络功能故障告警严重性标识、网络功能的故障事件标识、网络功能的资源利用率下限值、其他管理请求标识、执行时间和执行等待时间。例如，终结网络功能请求携带用户数量下限值10。
激活网络功能请求中携带的执行条件的参数包括如下至少一种：第三方管理模块的标识、网络功能故障告警类型标识、网络功能的故障事件标识、网络功能的资源利用率上限值、其他管理请求标识、执行时间和执行等待时间。这里，网络功能故障告警类型指组成该网络功能的其他现有网络功能故障告警，如过载告警，不是待创建的网络功能故障告警。网络功能的资源利用率上限值指组成该网络功能的其他现有网络功能的资源利用率上限值，不是待创建的网络功能的资源利用率上限值。例如，激活网络功能请求携带第三方管理模块的标识，第三方管理模块可以是客户的网络管理模块，第三方管理模块和网络切片子网管理功能设备之间存在直接接口，或者通过一个安全代理和所述网络切片子网管理功能设备交互。第三方管理模块还可以是管理另一个网络切片实例/网络切片子网实例的管理设备，该管理设备管理的网络切片实例/网络切片子网实例与网络切片子网管理设备共享待激活的网络功能。
注销网络功能请求中携带的执行条件的参数包括如下至少一种：第三方管理模块的标识、网络功能故障告警类型标识、网络功能的故障事件标识、网络功能 的资源利用率下限值、其他管理请求标识、执行时间和执行等待时间。网络功能故障告警类型指组成该网络功能的其他现有网络功能故障告警，如过载告警，不是待创建的网络功能故障告警。网络功能的资源利用率下限值指组成该网络功能的其他现有网络功能的资源利用率下限值，不是待创建的网络功能的资源利用率下限值。例如，注销网络功能请求携带PDU session数量下限值10。
网络功能性能测量任务请求中携带的执行条件的参数包括如下至少一种：接入网络功能的用户数量上限值、接入网络功能的用户数量下限值、网络功能运行的分组数据单元会话数量上限值、网络功能运行的分组数据单元会话数量下限值、网络功能的服务水平协议参数上限值、网络功能的服务水平协议参数下限值、网络功能的服务质量参数上限值、网络功能的服务质量参数下限值、网络功能的关键性能指标参数上限值、网络功能的关键性能指标参数下限值、第三方管理模块的标识、接入网络功能的用户在单位地理位置区间内的平均移动速度上限值、接入网络功能的用户在单位地理位置区间内的平均移动速度下限值、接入网络功能的用户在单位时间内发生小区切换的数量上限值、接入网络功能的用户在单位时间内发生小区切换的数量下限值、网络功能的故障告警类型标识、网络功能的故障告警严重性标识、网络功能的故障事件标识、网络功能的资源利用率上限值、网络功能的资源利用率下限值、其他管理请求标识、执行时间和执行等待时间。例如，网络功能性能测量任务请求携带用户数量上限值200和PDU session数量上限值1000。
网络功能性能阈值监测请求中携带的执行条件的参数包括如下至少一种：接入网络功能的用户数量上限值、接入网络功能的用户数量下限值、网络功能运行的分组数据单元会话数量上限值、网络功能运行的分组数据单元会话数量下限值、网络功能的服务水平协议参数上限值、网络功能的服务水平协议参数下限值、网络功能的服务质量参数上限值、网络功能的服务质量参数下限值、网络功能的关键性能指标参数上限值、网络功能的关键性能指标参数下限值、第三方管理模块的标识、接入网络功能的用户在单位地理位置区间内的平均移动速度上限值、接入网络功能的用户在单位地理位置区间内的平均移动速度下限值、接入网络功能的用户在单位时间内发生小区切换的数量上限值、接入网络功能的用户在单位时间内发生小区切换的数量下限值、网络功能的故障告警类型标识、网络功能的故障告警严重性标识、网络功能的故障事件标识、网络功能的资源利用率上限值、网络功能的资源利用率下限值、其他管理请求标识、执行时间和执行等待时间。例如，网络功能性能阈值监测请求携带用户数量上限值200和PDU session数量上限值1000。
网络功能告警信息上报请求中携带的执行条件的参数包括如下至少一种：接入网络功能的用户数量上限值、接入网络功能的用户数量下限值、网络功能运行的分组数据单元会话数量上限值、网络功能运行的分组数据单元会话数量下限值、网络功能的服务水平协议参数上限值、网络功能的服务水平协议参数下限值、网络功能的服务质量参数上限值、网络功能的服务质量参数下限值、网络功能的关 键性能指标参数上限值、网络功能的关键性能指标参数下限值、第三方管理模块的标识、接入网络功能的用户在单位地理位置区间内的平均移动速度上限值、接入网络功能的用户在单位地理位置区间内的平均移动速度下限值、接入网络功能的用户在单位时间内发生小区切换的数量上限值、接入网络功能的用户在单位时间内发生小区切换的数量下限值、网络功能的故障告警类型标识、网络功能的故障告警严重性标识、网络功能的故障事件标识、网络功能的资源利用率上限值、网络功能的资源利用率下限值、其他管理请求标识、执行时间和执行等待时间。例如，网络功能告警信息上报请求携带软件故障标识和严重故障标识。
具体实现中，第一管理请求中可以携带参数类型以及参数值。该参数类型可以包括以下至少一项：用户数量上限值、用户数量下限值、PDU会话数量上限值、PDU会话数量下限值、用户当日使用的流量上限值、用户当日使用的流量下限值、用户当月使用的流量上限值、用户当月使用的流量下限值、用户历史累计使用的流量上限值、用户历史累计使用的流量下限值、时延上限值、时延下限值、吞吐率上限值、吞吐率下限值、掉话率上限值、掉话率下限值、丢包率上限值、丢包率下限值、小区间切换成功率上限值、小区间切换成功率下限值、第三方管理模块的标识、用户的平均移动速度上限值、用户的平均移动速度下限值、用户发生小区切换的数量上限值、用户发生小区切换的数量下限值、故障告警类型标识、故障告警严重性标识、故障事件标识、资源利用率上限值、资源利用率下限值、其他管理请求标识、执行时间和执行等待时间。第一管理请求中可以携带参数类型以及参数值的格式可以参见如下表1所示。表1只是作为第一管理请求携带参数类型以及参数值的格式举例，第一管理请求还可以携带其他字段，本发明实施例不作具体限定。第一管理请求具体可以携带表1所示的参数类型中的一种或多种，相应地，第一管理请求中携带的参数值也可以是一种或多种，每个参数值与某一参数类型相对应。表1中的参数值只是作为一种举例，在实际应用中，参数值还可以是其他值，本发明实施例不作具体限定。
表1
参数类型 参数值
用户数量上限值 200
用户数量下限值 10
PDU会话数量上限值 1000
PDU会话数量下限值 10
用户当日使用的流量上限值 1000MB
用户当日使用的流量下限值 0.1MB
用户当月使用的流量上限值 100GB
用户当月使用的流量下限值 0.01GB
用户历史累计使用的流量上限值 1TB
用户历史累计使用的流量下限值 1GB
时延上限值 200ms
时延下限值 5ms
吞吐率上限值 1Gbps
吞吐率下限值 1Kbps
掉话率上限值 2％
掉话率下限值 0.1％
丢包率上限值 2％
丢包率下限值 0.1％
小区间切换成功率上限值 99.999％
小区间切换成功率下限值 98％
第三方管理模块的标识 某一IP地址
用户的平均移动速度上限值 100KM/h
用户的平均移动速度下限值 5KM/h
用户发生小区切换的数量上限值 10000
用户发生小区切换的数量下限值 100
故障告警类型标识 硬件故障
故障告警严重性标识 严重
故障事件标识 通信中断
资源利用率上限值 CPU利用率100％
资源利用率下限值 CPU利用率1％
其他管理请求标识 某一ID
执行时间 18:28:00
执行等待时间 10分钟
S203：第一网络设备从第二网络设备接收第一管理请求，在执行条件满足时，第一网络设备执行该第一管理请求。
针对场景一来说，当满足以下至少一项时执行条件满足：接入网络切片实例的用户的数量大于或等于用户数量上限值、接入网络切片实例的用户的数量小于或等于用户数量下限值、网络切片实例运行的分组数据单元会话数量大于或等于分组数据单元会话数量上限值、网络切片实例运行的分组数据单元会话数量小于或等于分组数据单元会话数量下限值、接入网络切片实例的用户单位时间内累积(例如当日累计、当月累计、历史累计等)使用的流量阈值大于或等于用户使用的流量上限值、接入网络切片实例的用户单位时间内累积使用的流量阈值小于或等于用户使用的流量下限值、网络切片实例的服务水平协议参数大于或等于服务水平协议参数上限值、网络切片实例的服务水平协议参数小于或等于服务水平协议参数下限值、网络切片实例的服务质量参数大于或等于服务质量参数上限值、网络切片实例的服务质量参数小于或等于服务质量参数下限值、网络切片实例的关键性能指标参数大于或等于关键性能指标参数上限值、网络切片实例的关键性能指标参数小于或等于关键性能指标参数下限值、网络切片管理功能设备接收到 第三方管理模块的标识对应的第三方管理模块发送的请求、接入网络切片实例的用户在单位地理位置区间(例如某个特定小区的覆盖范围，也可能是跟踪区(Tracking Area，TA))对应的地理范围)内的平均移动速度大于或等于平均移动速度上限值、接入网络切片实例的用户在单位地理位置区间内的平均移动速度小于或等于平均移动速度下限值、接入网络切片实例的用户在单位时间(例如1天、5天等)内发生小区切换的数量大于或等于发生小区切换的数量上限值、接入网络切片实例的用户在单位时间内发生小区切换的数量小于或等于发生小区切换的数量下限值、网络切片管理功能设备接收到与故障告警类型标识一致的告警信息、网络切片管理功能设备接收到与故障告警严重性标识一致的告警信息、网络切片管理功能设备发生故障事件标识对应的故障事件、网络切片实例的资源利用率大于或等于资源利用率上限值、网络切片实例的资源利用率小于或等于资源利用率下限值、网络切片管理功能设备执行其他管理请求标识对应的管理请求后、网络切片管理功能设备执行其他管理请求标识对应的管理请求成功、网络切片管理功能设备执行其他管理请求标识对应的管理请求失败、执行时间到达、从网络切片管理功能设备接收到第一管理请求的时刻起计时达到执行等待时间。当执行条件满足时，网络切片管理功能设备执行该第一管理请求。
例如，第一管理请求为终结网络切片实例请求，该终结网络切片实例请求携带了网络切片实例的标识NSI1和用户数量下限值10。则当网络切片管理功能设备检测到接入NSI1对应的网络切片实例的用户数量小于或等于10时，网络切片管理功能设备将NSI1对应的网络切片实例终结。
针对场景二来说，当满足以下至少一项时执行条件满足：接入网络切片子网实例的用户的数量大于或等于用户数量上限值、接入网络切片子网实例的用户的数量小于或等于用户数量下限值、网络切片子网实例运行的分组数据单元会话数量大于或等于分组数据单元会话数量上限值、网络切片子网实例运行的分组数据单元会话数量小于或等于分组数据单元会话数量下限值、接入网络切片子网实例的用户单位时间(例如当日累计、当月累计、历史累计等)内累积使用的流量阈值大于或等于用户使用的流量上限值、接入网络切片子网实例的用户单位时间内累积使用的流量阈值小于或等于用户使用的流量下限值、网络切片子网实例的服务水平协议参数大于或等于服务水平协议参数上限值、网络切片子网实例的服务水平协议参数小于或等于服务水平协议参数下限值、网络切片子网实例的服务质量参数大于或等于服务质量参数上限值、网络切片子网实例的服务质量参数小于或等于服务质量参数下限值、网络切片子网实例的关键性能指标参数大于或等于关键性能指标参数上限值、网络切片子网实例的关键性能指标参数小于或等于关键性能指标参数下限值、接入网络切片子网实例的用户在单位地理位置区间内的平均移动速度大于或等于平均移动速度上限值、接入网络切片子网实例的用户在单位地理位置区间内的平均移动速度小于或等于平均移动速度下限值、接入网络切片子网实例的用户在单位时间内发生小区切换的数量大于或等于发生小区切换的数量上限值、接入网络切片子网实例的用户在单位时间内发生小区切换的数 量小于或等于发生小区切换的数量下限值、网络切片子网实例的资源利用率大于或等于资源利用率上限值、网络切片子网实例的资源利用率小于或等于资源利用率下限值、接入网络功能的用户的数量大于或等于用户数量上限值、接入网络功能的用户的数量小于或等于用户数量下限值、网络功能运行的分组数据单元会话数量大于或等于分组数据单元会话数量上限值、网络功能运行的分组数据单元会话数量小于或等于分组数据单元会话数量下限值、接入网络功能的用户单位时间内累积使用的流量阈值大于或等于用户使用的流量上限值、接入网络功能的用户单位时间内累积使用的流量阈值小于或等于用户使用的流量下限值、网络功能的服务水平协议参数大于或等于服务水平协议参数上限值、网络功能的服务水平协议参数小于或等于服务水平协议参数下限值、网络功能的服务质量参数大于或等于服务质量参数上限值、网络功能的服务质量参数小于或等于服务质量参数下限值、网络功能的关键性能指标参数大于或等于关键性能指标参数上限值、网络功能的关键性能指标参数小于或等于关键性能指标参数下限值、网络切片子网管理功能设备接收到第三方管理模块的标识对应的第三方管理模块发送的请求、接入网络功能的用户在单位地理位置区间内的平均移动速度大于或等于平均移动速度上限值、接入网络功能的用户在单位地理位置区间内的平均移动速度小于或等于平均移动速度下限值、接入网络功能的用户在单位时间内发生小区切换的数量大于或等于发生小区切换的数量上限值、接入网络功能的用户在单位时间内发生小区切换的数量小于或等于发生小区切换的数量下限值、网络切片子网管理功能设备接收到与故障告警类型标识一致的告警信息、网络切片子网管理功能设备接收到与故障告警严重性标识一致的告警信息、网络切片子网管理功能设备发生故障事件标识对应的故障事件、网络功能的资源利用率大于或等于资源利用率上限值、网络功能的资源利用率小于或等于资源利用率下限值、网络切片子网管理功能设备执行其他管理请求标识对应的管理请求后、网络切片子网管理功能设备执行其他管理请求标识对应的管理请求成功、网络切片子网管理功能设备执行其他管理请求标识对应的管理请求失败、执行时间到达、从网络切片子网管理功能设备接收到第一管理请求的时刻起计时达到执行等待时间。当执行条件满足时，网络切片子网管理功能设备执行该第一管理请求。
例如，第一管理请求为创建网络切片子网实例请求，该创建网络切片子网实例请求携带了其他管理请求标识。则当网络切片子网管理功能设备检测到该其他管理请求标识对应的管理请求执行成功时，网络切片子网管理功能设备创建一网络切片子网实例。
又例如，第一管理请求为激活网络功能请求，该激活网络功能请求携带了网络功能的标识NF1以及第三方管理模块的标识。则当网络切片子网管理功能设备检测到该第三方管理模块触发的请求时，网络切片子网管理功能设备激活该NF1对应的网络功能。
可选的，若第一管理请求携带的参数为空，则第一网络设备会立即执行第一管理请求。
可选的，第一网络设备在接收到第二网络设备发送的第一管理请求后，判断第一管理请求是否可执行。如果第一管理请求可执行，则第一网络设备向第二网络设备反馈该第一管理请求能够执行，等待执行条件满足后执行该第一管理请求。如果该第一管理请求不能被执行，则第一网络设备向第二网络设备反馈该第一管理请求不能被执行，并说明原因。例如，第一网络设备依据所管理的网络的资源和能力情况，判断该第一管理请求是否可执行。若执行第一管理请求所需的资源不足，则表明第一管理请求不可执行。
可选的，第一网络设备执行完第一管理请求后，还可以向第二网络设备反馈执行结果。
实施本发明实施例，通过在第一管理请求消息中携带执行条件参数的方法，使得网络实例管理更加灵活、自动化。相比于未携带执行条件的技术，本发明实施例可以使网络实例管理设备能够依据执行条件来执行管理请求。本发明实施例介绍的技术可以适用于分层次的网络切片管理系统，适用于网络切片实例/网络切片子网实例/网络功能的创建、修改、配置、终结、激活、注销、性能测量、性能阈值监测和告警信息上报等管理请求，适用于网络切片实例/网络切片子网实例/网络功能的生命周期管理。同时，相比于现有技术，本发明实施例可携带的执行条件的参数的类型更多，范围更广，复杂度更高。
为了便于更好地实施本发明实施例的上述网络实例管理方法，本发明还提供了用于实现上述方法的相关设备。
请参见图3，是本发明实施例提供的一种网络设备的结构示意图。如图3所示，第一网络设备30包括处理器301和收发器303。可选的，第一网络设备还可以包括存储器302。其中处理器301、存储器302和收发器303可以通过总线或其他方式连接，本发明实施例以处理器301、存储器302和收发器303可以通过总线304连接为例进行说明。
在一些可能的实施方式中，第一网络设备30还可以包括图3未示出的模块。
其中，处理器301可以是通用处理器，例如中央处理器(Central Processing Unit，CPU)，还可以是数字信号处理器(Digital Signal Processing，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)，或者是被配置成实施本发明实施例的一个或多个集成电路。处理器301可处理通过收发器303接收到的数据。处理器301还可处理将被发送到收发器303的数据。
存储器302用于存储程序指令和/或数据，并将该程序指令传输给CPU。存储器302可以包括易失性存储器(Volatile Memory)，例如随机存取存储器(Random Access Memory，RAM)。存储器302也可以包括非易失性存储器(Non-volatile Memory)，例如只读存储器(Read-Only Memory，ROM)、快闪存储器(Flash Memory)、硬盘(Hard Disk Drive，HDD)或固态硬盘(Solid-State Drive，SSD)。存储器302还可以包括上述种类的存储器的组合。存储器302通过总线与处理器301相连接。
收发器303用于第一网络设备30与其他设备进行数据通信，例如，与第二网络设备进行数据通信。
在本发明实施例中，处理器301用于调用存储器302中存储的程序指令和数据，执行如下操作：
通过收发器303从第二网络设备接收第一管理请求，所述第一管理请求用于指示对网络实例进行管理，所述第一管理请求包括执行条件的参数，所述参数与所述网络实例相关；所述第一网络设备为网络切片管理功能设备，所述第二网络设备为通信业务管理功能设备；或者，所述第一网络设备为网络切片子网管理功能设备，所述第二网络设备为网络切片管理功能设备。
在所述执行条件满足时，执行所述第一管理请求。
可选的，所述网络实例包括以下至少一项：网络切片实例、网络切片子网实例和网络功能。
可选的，所述第一管理请求包括以下任一项：创建请求、修改请求、配置请求、终结请求、激活请求、注销请求、性能测量任务请求、性能阈值监测请求和告警信息上报请求。
可选的，所述参数包括以下至少一项：接入所述网络实例的用户数量阈值、所述网络实例运行的分组数据单元会话数量阈值、接入所述网络实例的用户使用的流量阈值、所述网络实例的服务水平协议参数阈值、所述网络实例的服务质量参数阈值、所述网络实例的关键性能指标参数阈值、第三方管理模块的标识、接入所述网络实例的用户在单位地理位置区间内的平均移动速度阈值、接入所述网络实例的用户在单位时间内发生小区切换的数量阈值、所述网络实例的故障告警类型标识、所述网络实例的故障告警严重性标识、所述网络实例的故障事件标识、所述网络实例的资源利用率阈值、其他管理请求标识、所述第一管理请求的执行时间和所述第一管理请求的执行等待时间。
可选的，当满足以下至少一项时所述执行条件满足：接入所述网络实例的用户的数量达到所述用户数量阈值、所述网络实例运行的分组数据单元会话数量达到所述分组数据单元会话数量阈值、接入所述网络实例的用户单位时间内累积使用的流量阈值达到所述用户使用的流量阈值、所述网络实例的服务水平协议参数达到所述服务水平协议参数阈值、所述网络实例的服务质量参数达到所述服务质量参数阈值、所述网络实例的关键性能指标参数达到所述关键性能指标参数阈值、所述第一网络设备接收到所述第三方管理模块的标识对应的所述第三方管理模块发送的请求、接入所述网络实例的用户在单位地理位置区间内的平均移动速度达到所述平均移动速度阈值、接入所述网络实例的用户在单位时间内发生小区切换的数量达到所述发生小区切换的数量阈值、所述第一网络设备接收到与所述故障告警类型标识一致的告警信息、所述第一网络设备接收到与所述故障告警严重性标识一致的告警信息、所述第一网络设备发生所述故障事件标识对应的故障事件、所述网络实例的资源利用率达到所述资源利用率阈值、所述第一网络设备执行所述其他管理请求标识对应的管理请求后、所述执行时间到达、从所述第一网 络设备接收到所述第一管理请求的时刻起计时达到所述执行等待时间。
需要说明的是，本发明实施例所描述的第一网络设备30中各功能模块的功能可参见上述图2所示实施例中对应第一网络设备的相关描述，此处不再赘述。
请参见图4，是本发明实施例提供的另一种网络设备的结构示意图。如图4所示，第二网络设备40可包括处理器401和收发器403。可选的，第一网络设备还可以包括存储器302。其中处理器401、存储器402和收发器403可以通过总线或其他方式连接，本发明实施例以处理器401、存储器402和收发器403可以通过总线404连接为例进行说明。
在一些可能的实施方式中，第二网络设备40还可以包括图4未示出的模块。
其中，处理器401可以是通用处理器，例如CPU，还可以是DSP、ASIC，或者是被配置成实施本发明实施例的一个或多个集成电路。处理器401可处理通过收发器403接收到的数据。处理器401还可处理将被发送到收发器403的数据。
存储器402用于存储程序指令和/或数据，并将该程序指令传输给CPU。存储器402可以包括易失性存储器，例如RAM。存储器402也可以包括非易失性存储器，例如ROM、快闪存储器、HDD或SSD；存储器402还可以包括上述种类的存储器的组合。存储器402通过总线与处理器401相连接。
收发器403用于第二网络设备40与其他设备进行数据通信，例如，与第一网络设备进行数据通信。
在本发明实施例中，处理器401用于调用存储器402中存储的程序指令和数据，执行如下操作：
确定第一管理请求，所述第一管理请求包括执行条件的参数，所述参数与网络实例相关；
通过收发器403向第一网络设备发送第一管理请求，所述第一管理请求用于指示所述第一网络设备在所述执行条件满足时针对所述网络实例执行所述第一管理请求；所述第一网络设备为网络切片管理功能设备，所述第二网络设备为通信业务管理功能设备；或者，所述第一网络设备为网络切片子网管理功能设备，所述第二网络设备为网络切片管理功能设备。
可选的，所述网络实例包括以下至少一项：网络切片实例、网络切片子网实例和网络功能。
可选的，所述第一管理请求包括以下任一项：创建请求、修改请求、配置请求、终结请求、激活请求、注销请求、性能测量任务请求、性能阈值监测请求和告警信息上报请求。
可选的，所述参数包括以下至少一项：使用所述网络实例的用户数量阈值、所述网络实例运行的分组数据单元会话数量阈值、使用所述网络实例的用户使用的流量阈值、所述网络实例的服务水平协议参数阈值、所述网络实例的服务质量参数阈值、所述网络实例的关键性能指标参数阈值、第三方管理模块的标识、使用所述网络实例的用户在单位地理位置区间内的平均移动速度阈值、使用所述网 络实例的用户在单位时间内发生小区切换的数量阈值、所述网络实例的故障告警类型标识、所述网络实例的故障告警严重性标识、所述网络实例的故障事件标识、所述网络实例的资源利用率阈值、其他管理请求标识、所述第一管理请求的执行时间和所述第一管理请求的执行等待时间。
可选的，当满足以下至少一项时所述执行条件满足：使用所述网络实例的用户的数量达到所述用户数量阈值、所述网络实例运行的分组数据单元会话数量达到所述分组数据单元会话数量阈值、使用所述网络实例的用户单位时间内累积使用的流量阈值达到所述用户使用的流量阈值、所述网络实例的服务水平协议参数达到所述服务水平协议参数阈值、所述网络实例的服务质量参数达到所述服务质量参数阈值、所述网络实例的关键性能指标参数达到所述关键性能指标参数阈值、所述第一网络设备接收到所述第三方管理模块的标识对应的所述第三方管理模块发送的请求、使用所述网络实例的用户在单位地理位置区间内的平均移动速度达到所述平均移动速度阈值、使用所述网络实例的用户在单位时间内发生小区切换的数量达到所述发生小区切换的数量阈值、所述第一网络设备接收到与所述故障告警类型标识一致的告警信息、所述第一网络设备接收到与所述故障告警严重性标识一致的告警信息、所述第一网络设备发生所述故障事件标识对应的故障事件、所述网络实例的资源利用率达到所述资源利用率阈值、所述第一网络设备执行所述其他管理请求标识对应的管理请求后、所述执行时间到达、从所述第一网络设备接收到所述第一管理请求的时刻起计时达到所述执行等待时间。
需要说明的是，本发明实施例所描述的第二网络设备40中各功能模块的功能可参见上述图2所示实施例中对应第二网络设备的相关描述，此处不再赘述。
请参见图5，是本发明实施例提供的另一种网络设备的结构示意图。如图5所示，第一网络设备50包括：接收单元501和处理单元502。
在本发明实施例中，接收单元501，用于从第二网络设备接收第一管理请求，所述第一管理请求用于指示对网络实例进行管理，所述第一管理请求包括执行条件的参数，所述参数与所述网络实例相关；所述第一网络设备为网络切片管理功能设备，所述第二网络设备为通信业务管理功能设备；或者，所述第一网络设备为网络切片子网管理功能设备，所述第二网络设备为网络切片管理功能设备；
处理单元502，用于在所述执行条件满足时，执行所述第一管理请求。
在本实施例中，第一网络设备50是以功能单元的形式来呈现。这里的“单元”可以指ASIC，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。第一网络设备50可以采用图3所示的形式。其中，接收单元501可以通过图3中的收发器303来实现，处理单元502可以通过图3中的处理器301来实现。
可选的，所述网络实例包括以下至少一项：网络切片实例、网络切片子网实例和网络功能。
可选的，所述第一管理请求包括以下任一项：创建请求、修改请求、配置请 求、终结请求、激活请求、注销请求、性能测量任务请求、性能阈值监测请求和告警信息上报请求。
可选的，所述参数包括以下至少一项：使用所述网络实例的用户数量阈值、所述网络实例运行的分组数据单元会话数量阈值、使用所述网络实例的用户使用的流量阈值、所述网络实例的服务水平协议参数阈值、所述网络实例的服务质量参数阈值、所述网络实例的关键性能指标参数阈值、第三方管理模块的标识、使用所述网络实例的用户在单位地理位置区间内的平均移动速度阈值、使用所述网络实例的用户在单位时间内发生小区切换的数量阈值、所述网络实例的故障告警类型标识、所述网络实例的故障告警严重性标识、所述网络实例的故障事件标识、所述网络实例的资源利用率阈值、其他管理请求标识、所述第一管理请求的执行时间和所述第一管理请求的执行等待时间。
可选的，当满足以下至少一项时所述执行条件满足：使用所述网络实例的用户的数量达到所述用户数量阈值、所述网络实例运行的分组数据单元会话数量达到所述分组数据单元会话数量阈值、使用所述网络实例的用户单位时间内累积使用的流量阈值达到所述用户使用的流量阈值、所述网络实例的服务水平协议参数达到所述服务水平协议参数阈值、所述网络实例的服务质量参数达到所述服务质量参数阈值、所述网络实例的关键性能指标参数达到所述关键性能指标参数阈值、所述第一网络设备接收到所述第三方管理模块的标识对应的所述第三方管理模块发送的请求、使用所述网络实例的用户在单位地理位置区间内的平均移动速度达到所述平均移动速度阈值、使用所述网络实例的用户在单位时间内发生小区切换的数量达到所述发生小区切换的数量阈值、所述第一网络设备接收到与所述故障告警类型标识一致的告警信息、所述第一网络设备接收到与所述故障告警严重性标识一致的告警信息、所述第一网络设备发生所述故障事件标识对应的故障事件、所述网络实例的资源利用率达到所述资源利用率阈值、所述第一网络设备执行所述其他管理请求标识对应的管理请求后、所述执行时间到达、从所述第一网络设备接收到所述第一管理请求的时刻起计时达到所述执行等待时间。
需要说明的是，本发明实施例所描述的第一网络设备50中各功能模块的功能可参见上述图2所示实施例中对应第一网络设备的相关描述，此处不再赘述。
请参见图6，是本发明实施例提供的另一种网络设备的结构示意图。如图6所示，第二网络设备60包括：确定单元601和发送单元602。
在本发明实施例中，确定单元601，用于确定第一管理请求，所述第一管理请求包括执行条件的参数，所述参数与网络实例相关；
发送单元602，用于向第一网络设备发送第一管理请求，所述第一管理请求用于指示所述第一网络设备在所述执行条件满足时针对网络实例执行所述第一管理请求；所述第一网络设备为网络切片管理功能设备，所述第二网络设备为通信业务管理功能设备；或者，所述第一网络设备为网络切片子网管理功能设备，所述第二网络设备为网络切片管理功能设备。
在本实施例中，第二网络设备60是以功能单元的形式来呈现。这里的“单元”可以指ASIC，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。第二网络设备60可以采用图4所示的形式。其中，确定单元601可以通过图4中的处理器401来实现，发送单元602可以通过图4中的收发器403来实现。
可选的，所述网络实例包括以下至少一项：网络切片实例、网络切片子网实例和网络功能。
可选的，所述第一管理请求包括以下任一项：创建请求、修改请求、配置请求、终结请求、激活请求、注销请求、性能测量任务请求、性能阈值监测请求和告警信息上报请求。
可选的，所述参数包括以下至少一项：使用所述网络实例的用户数量阈值、所述网络实例运行的分组数据单元会话数量阈值、使用所述网络实例的用户使用的流量阈值、所述网络实例的服务水平协议参数阈值、所述网络实例的服务质量参数阈值、所述网络实例的关键性能指标参数阈值、第三方管理模块的标识、使用所述网络实例的用户在单位地理位置区间内的平均移动速度阈值、使用所述网络实例的用户在单位时间内发生小区切换的数量阈值、所述网络实例的故障告警类型标识、所述网络实例的故障告警严重性标识、所述网络实例的故障事件标识、所述网络实例的资源利用率阈值、其他管理请求标识、所述第一管理请求的执行时间和所述第一管理请求的执行等待时间。
可选的，当满足以下至少一项时所述执行条件满足：使用所述网络实例的用户的数量达到所述用户数量阈值、所述网络实例运行的分组数据单元会话数量达到所述分组数据单元会话数量阈值、使用所述网络实例的用户单位时间内累积使用的流量阈值达到所述用户使用的流量阈值、所述网络实例的服务水平协议参数达到所述服务水平协议参数阈值、所述网络实例的服务质量参数达到所述服务质量参数阈值、所述网络实例的关键性能指标参数达到所述关键性能指标参数阈值、所述第一网络设备接收到所述第三方管理模块的标识对应的所述第三方管理模块发送的请求、使用所述网络实例的用户在单位地理位置区间内的平均移动速度达到所述平均移动速度阈值、使用所述网络实例的用户在单位时间内发生小区切换的数量达到所述发生小区切换的数量阈值、所述第一网络设备接收到与所述故障告警类型标识一致的告警信息、所述第一网络设备接收到与所述故障告警严重性标识一致的告警信息、所述第一网络设备发生所述故障事件标识对应的故障事件、所述网络实例的资源利用率达到所述资源利用率阈值、所述第一网络设备执行所述其他管理请求标识对应的管理请求后、所述执行时间到达、从所述第一网络设备接收到所述第一管理请求的时刻起计时达到所述执行等待时间。
需要说明的是，本发明实施例所描述的第二网络设备60中各功能模块的功能可参见上述图2所示实施例中对应第二网络设备的相关描述，此处不再赘述。
参见图7，图7示出了本发明实施例提供的一种装置的结构示意图。如图7所示，装置70可包括：处理器701，以及耦合于处理器701的一个或多个接口 702。其中：
处理器701可用于读取和执行计算机可读指令。具体实现中，处理器701可主要包括控制器、运算器和寄存器。其中，控制器主要负责指令译码，并为指令对应的操作发出控制信号。运算器主要负责执行定点或浮点算数运算操作、移位操作以及逻辑操作等，也可以执行地址运算和转换。寄存器主要负责保存指令执行过程中临时存放的寄存器操作数和中间操作结果等。具体实现中，处理器701的硬件架构可以是专用集成电路(Application Specific Integrated Circuits，ASIC)架构等等。处理器701可以是单核的，也可以是多核的。
接口702可用于输入待处理的数据至处理器701，并且可以向外输出处理器701的处理结果。
本申请中，处理器701可用于从存储器中调用本申请的一个或多个实施例提供的网络实例管理方法在第一网络设备侧的实现程序，并执行该程序包含的指令。接口702可用于输出处理器701的执行结果。关于本申请的一个或多个实施例提供的网络实例管理方法可参考前述各个实施例，这里不再赘述。
需要说明的，处理器701、接口702各自对应的功能既可以通过硬件设计实现，也可以通过软件设计来实现，还可以通过软硬件结合的方式来实现，这里不作限制。
参见图8，图8示出了本发明实施例提供的另一种装置的结构示意图。如图8所示，装置80可包括：处理器801，以及耦合于处理器801的一个或多个接口802。其中：
处理器801可用于读取和执行计算机可读指令。具体实现中，处理器801可主要包括控制器、运算器和寄存器。其中，控制器主要负责指令译码，并为指令对应的操作发出控制信号。运算器主要负责执行定点或浮点算数运算操作、移位操作以及逻辑操作等，也可以执行地址运算和转换。寄存器主要负责保存指令执行过程中临时存放的寄存器操作数和中间操作结果等。具体实现中，处理器801的硬件架构可以是专用集成电路(Application Specific Integrated Circuits,ASIC)架构等等。处理器801可以是单核的，也可以是多核的。
接口802可用于输入待处理的数据至处理器801，并且可以向外输出处理器801的处理结果。
本申请中，处理器801可用于从存储器中调用本申请的一个或多个实施例提供的网络实例管理方法在第二网络设备侧的实现程序，并执行该程序包含的指令。接口802可用于输出处理器801的执行结果。关于本申请的一个或多个实施例提供的网络实例管理方法可参考前述各个实施例，这里不再赘述。
需要说明的，处理器801、接口802各自对应的功能既可以通过硬件设计实现，也可以通过软件设计来实现，还可以通过软硬件结合的方式来实现，这里不作限制。
结合本发明实施例公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件程序指令的方式来实现。软件程序指令可以 由相应的软件模块组成，软件模块可以被存放于RAM、闪存、ROM、可擦除可编程只读存储器(Erasable Programmable ROM，EPROM)、电可擦可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于收发机或中继设备中。当然，处理器和存储介质也可以作为分立组件存在于第一网络设备或第二网络设备中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明实施例所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个程序指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上的具体实施方式，对本发明实施例的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上仅为本发明实施例的具体实施方式而已，并不用于限定本发明实施例的保护范围，凡在本发明实施例的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明实施例的保护范围之内。

Claims (37)

  1. 一种网络实例管理方法，其特征在于，包括：
    第一网络设备从第二网络设备接收第一管理请求，所述第一管理请求用于指示对网络实例进行管理，所述第一管理请求包括执行条件的参数，所述参数与所述网络实例相关；所述第一网络设备为网络切片管理功能设备，所述第二网络设备为通信业务管理功能设备；或者，所述第一网络设备为网络切片子网管理功能设备，所述第二网络设备为网络切片管理功能设备；
    在所述执行条件满足时，所述第一网络设备执行所述第一管理请求。
  2. 根据权利要求1所述的方法，其特征在于，所述网络实例包括以下至少一项：网络切片实例、网络切片子网实例和网络功能。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一管理请求包括以下任一项：创建请求、修改请求、配置请求、终结请求、激活请求、注销请求、性能测量任务请求、性能阈值监测请求和告警信息上报请求。
  4. 根据权利要求1至3任一项所述的方法，其特征在于，所述参数包括以下至少一项：使用所述网络实例的用户数量阈值、所述网络实例运行的分组数据单元会话数量阈值、使用所述网络实例的用户使用的流量阈值、所述网络实例的服务水平协议参数阈值、所述网络实例的服务质量参数阈值、所述网络实例的关键性能指标参数阈值、第三方管理模块的标识、使用所述网络实例的用户在单位地理位置区间内的平均移动速度阈值、使用所述网络实例的用户在单位时间内发生小区切换的数量阈值、所述网络实例的故障告警类型标识、所述网络实例的故障告警严重性标识、所述网络实例的故障事件标识、所述网络实例的资源利用率阈值、其他管理请求标识、所述第一管理请求的执行时间和所述第一管理请求的执行等待时间。
  5. 根据权利要求4所述的方法，其特征在于，当满足以下至少一项时所述执行条件满足：使用所述网络实例的用户的数量达到所述用户数量阈值、所述网络实例运行的分组数据单元会话数量达到所述分组数据单元会话数量阈值、使用所述网络实例的用户单位时间内累积使用的流量阈值达到所述用户使用的流量阈值、所述网络实例的服务水平协议参数达到所述服务水平协议参数阈值、所述网络实例的服务质量参数达到所述服务质量参数阈值、所述网络实例的关键性能指标参数达到所述关键性能指标参数阈值、所述第一网络设备接收到所述第三方管理模块的标识对应的所述第三方管理模块发送的请求、使用所述网络实例的用户在单位地理位置区间内的平均移动速度达到所述平均移动速度阈值、使用所述网络实例的用户在单位时间内发生小区切换的数量达到所述发生小区切换的数 量阈值、所述第一网络设备接收到与所述故障告警类型标识一致的告警信息、所述第一网络设备接收到与所述故障告警严重性标识一致的告警信息、所述第一网络设备发生所述故障事件标识对应的故障事件、所述网络实例的资源利用率达到所述资源利用率阈值、所述第一网络设备执行所述其他管理请求标识对应的管理请求后、所述执行时间到达、从所述第一网络设备接收到所述第一管理请求的时刻起计时达到所述执行等待时间。
  6. 一种网络实例管理方法，其特征在于，包括：
    第二网络设备确定第一管理请求，所述第一管理请求包括执行条件的参数，所述参数与网络实例相关；
    所述第二网络设备向第一网络设备发送所述第一管理请求，所述第一管理请求用于指示所述第一网络设备在所述执行条件满足时针对所述网络实例执行所述第一管理请求；所述第一网络设备为网络切片管理功能设备，所述第二网络设备为通信业务管理功能设备；或者，所述第一网络设备为网络切片子网管理功能设备，所述第二网络设备为网络切片管理功能设备。
  7. 根据权利要求6所述的方法，其特征在于，所述网络实例包括以下至少一项：网络切片实例、网络切片子网实例和网络功能。
  8. 根据权利要求6或7所述的方法，其特征在于，所述第一管理请求包括以下任一项：创建请求、修改请求、配置请求、终结请求、激活请求、注销请求、性能测量任务请求、性能阈值监测请求和告警信息上报请求。
  9. 根据权利要求6至8任一项所述的方法，其特征在于，所述参数包括以下至少一项：使用所述网络实例的用户数量阈值、所述网络实例运行的分组数据单元会话数量阈值、使用所述网络实例的用户使用的流量阈值、所述网络实例的服务水平协议参数阈值、所述网络实例的服务质量参数阈值、所述网络实例的关键性能指标参数阈值、第三方管理模块的标识、使用所述网络实例的用户在单位地理位置区间内的平均移动速度阈值、使用所述网络实例的用户在单位时间内发生小区切换的数量阈值、所述网络实例的故障告警类型标识、所述网络实例的故障告警严重性标识、所述网络实例的故障事件标识、所述网络实例的资源利用率阈值、其他管理请求标识、所述第一管理请求的执行时间和所述第一管理请求的执行等待时间。
  10. 根据权利要求9所述的方法，其特征在于，当满足以下至少一项时所述执行条件满足：使用所述网络实例的用户的数量达到所述用户数量阈值、所述网络实例运行的分组数据单元会话数量达到所述分组数据单元会话数量阈值、使用所述网络实例的用户单位时间内累积使用的流量阈值达到所述用户使用的流量 阈值、所述网络实例的服务水平协议参数达到所述服务水平协议参数阈值、所述网络实例的服务质量参数达到所述服务质量参数阈值、所述网络实例的关键性能指标参数达到所述关键性能指标参数阈值、所述第一网络设备接收到所述第三方管理模块的标识对应的所述第三方管理模块发送的请求、使用所述网络实例的用户在单位地理位置区间内的平均移动速度达到所述平均移动速度阈值、使用所述网络实例的用户在单位时间内发生小区切换的数量达到所述发生小区切换的数量阈值、所述第一网络设备接收到与所述故障告警类型标识一致的告警信息、所述第一网络设备接收到与所述故障告警严重性标识一致的告警信息、所述第一网络设备发生所述故障事件标识对应的故障事件、所述网络实例的资源利用率达到所述资源利用率阈值、所述第一网络设备执行所述其他管理请求标识对应的管理请求后、所述执行时间到达、从所述第一网络设备接收到所述第一管理请求的时刻起计时达到所述执行等待时间。
  11. 一种网络设备，其特征在于，所述网络设备为第一网络设备，所述第一网络设备包括接收单元和处理单元；
    所述接收单元，用于从第二网络设备接收第一管理请求，所述第一管理请求用于指示对网络实例进行管理，所述第一管理请求包括执行条件的参数，所述参数与所述网络实例相关；所述第一网络设备为网络切片管理功能设备，所述第二网络设备为通信业务管理功能设备；或者，所述第一网络设备为网络切片子网管理功能设备，所述第二网络设备为网络切片管理功能设备；
    所述处理单元，用于在所述执行条件满足时，执行所述第一管理请求。
  12. 根据权利要求11所述的网络设备，其特征在于，所述网络实例包括以下至少一项：网络切片实例、网络切片子网实例和网络功能。
  13. 根据权利要求11或12所述的网络设备，其特征在于，所述第一管理请求包括以下任一项：创建请求、修改请求、配置请求、终结请求、激活请求、注销请求、性能测量任务请求、性能阈值监测请求和告警信息上报请求。
  14. 根据权利要求11至13任一项所述的网络设备，其特征在于，所述参数包括以下至少一项：使用所述网络实例的用户数量阈值、所述网络实例运行的分组数据单元会话数量阈值、使用所述网络实例的用户使用的流量阈值、所述网络实例的服务水平协议参数阈值、所述网络实例的服务质量参数阈值、所述网络实例的关键性能指标参数阈值、第三方管理模块的标识、使用所述网络实例的用户在单位地理位置区间内的平均移动速度阈值、使用所述网络实例的用户在单位时间内发生小区切换的数量阈值、所述网络实例的故障告警类型标识、所述网络实例的故障告警严重性标识、所述网络实例的故障事件标识、所述网络实例的资源利用率阈值、其他管理请求标识、所述第一管理请求的执行时间和所述第一管理 请求的执行等待时间。
  15. 根据权利要求14所述的网络设备，其特征在于，当满足以下至少一项时所述执行条件满足：使用所述网络实例的用户的数量达到所述用户数量阈值、所述网络实例运行的分组数据单元会话数量达到所述分组数据单元会话数量阈值、使用所述网络实例的用户单位时间内累积使用的流量阈值达到所述用户使用的流量阈值、所述网络实例的服务水平协议参数达到所述服务水平协议参数阈值、所述网络实例的服务质量参数达到所述服务质量参数阈值、所述网络实例的关键性能指标参数达到所述关键性能指标参数阈值、所述第一网络设备接收到所述第三方管理模块的标识对应的所述第三方管理模块发送的请求、使用所述网络实例的用户在单位地理位置区间内的平均移动速度达到所述平均移动速度阈值、使用所述网络实例的用户在单位时间内发生小区切换的数量达到所述发生小区切换的数量阈值、所述第一网络设备接收到与所述故障告警类型标识一致的告警信息、所述第一网络设备接收到与所述故障告警严重性标识一致的告警信息、所述第一网络设备发生所述故障事件标识对应的故障事件、所述网络实例的资源利用率达到所述资源利用率阈值、所述第一网络设备执行所述其他管理请求标识对应的管理请求后、所述执行时间到达、从所述第一网络设备接收到所述第一管理请求的时刻起计时达到所述执行等待时间。
  16. 一种网络设备，其特征在于，所述网络设备为第二网络设备，所述第二网络设备包括确定单元和发送单元；
    所述确定单元，用于确定第一管理请求，所述第一管理请求包括执行条件的参数，所述参数与网络实例相关；
    所述发送单元，用于向第一网络设备发送所述第一管理请求，所述第一管理请求用于指示所述第一网络设备在所述执行条件满足时针对所述网络实例执行所述第一管理请求；所述第一网络设备为网络切片管理功能设备，所述第二网络设备为通信业务管理功能设备；或者，所述第一网络设备为网络切片子网管理功能设备，所述第二网络设备为网络切片管理功能设备。
  17. 根据权利要求16所述的网络设备，其特征在于，所述网络实例包括以下至少一项：网络切片实例、网络切片子网实例和网络功能。
  18. 根据权利要求16或17所述的网络设备，其特征在于，所述第一管理请求包括以下任一项：创建请求、修改请求、配置请求、终结请求、激活请求、注销请求、性能测量任务请求、性能阈值监测请求和告警信息上报请求。
  19. 根据权利要求16至18任一项所述的网络设备，其特征在于，所述参数包括以下至少一项：使用所述网络实例的用户数量阈值、所述网络实例运行的分 组数据单元会话数量阈值、使用所述网络实例的用户使用的流量阈值、所述网络实例的服务水平协议参数阈值、所述网络实例的服务质量参数阈值、所述网络实例的关键性能指标参数阈值、第三方管理模块的标识、使用所述网络实例的用户在单位地理位置区间内的平均移动速度阈值、使用所述网络实例的用户在单位时间内发生小区切换的数量阈值、所述网络实例的故障告警类型标识、所述网络实例的故障告警严重性标识、所述网络实例的故障事件标识、所述网络实例的资源利用率阈值、其他管理请求标识、所述第一管理请求的执行时间和所述第一管理请求的执行等待时间。
  20. 根据权利要求19所述的网络设备，其特征在于，当满足以下至少一项时所述执行条件满足：使用所述网络实例的用户的数量达到所述用户数量阈值、所述网络实例运行的分组数据单元会话数量达到所述分组数据单元会话数量阈值、使用所述网络实例的用户单位时间内累积使用的流量阈值达到所述用户使用的流量阈值、所述网络实例的服务水平协议参数达到所述服务水平协议参数阈值、所述网络实例的服务质量参数达到所述服务质量参数阈值、所述网络实例的关键性能指标参数达到所述关键性能指标参数阈值、所述第一网络设备接收到所述第三方管理模块的标识对应的所述第三方管理模块发送的请求、使用所述网络实例的用户在单位地理位置区间内的平均移动速度达到所述平均移动速度阈值、使用所述网络实例的用户在单位时间内发生小区切换的数量达到所述发生小区切换的数量阈值、所述第一网络设备接收到与所述故障告警类型标识一致的告警信息、所述第一网络设备接收到与所述故障告警严重性标识一致的告警信息、所述第一网络设备发生所述故障事件标识对应的故障事件、所述网络实例的资源利用率达到所述资源利用率阈值、所述第一网络设备执行所述其他管理请求标识对应的管理请求后、所述执行时间到达、从所述第一网络设备接收到所述第一管理请求的时刻起计时达到所述执行等待时间。
  21. 一种网络设备，其特征在于，所述网络设备为第一网络设备，所述第一网络设备包括处理器、存储器、接收器和发射器，所述存储器用于存储程序代码，所述处理器用于调用所述存储器中的程序代码执行如下操作：
    通过所述接收器从第二网络设备接收第一管理请求，所述第一管理请求用于指示对网络实例进行管理，所述第一管理请求包括执行条件的参数，所述参数与所述网络实例相关；所述第一网络设备为网络切片管理功能设备，所述第二网络设备为通信业务管理功能设备；或者，所述第一网络设备为网络切片子网管理功能设备，所述第二网络设备为网络切片管理功能设备；
    在所述执行条件满足时，执行所述第一管理请求。
  22. 根据权利要求21所述的网络设备，其特征在于，所述网络实例包括以下至少一项：网络切片实例、网络切片子网实例和网络功能。
  23. 根据权利要求21或22所述的网络设备，其特征在于，所述第一管理请求包括以下任一项：创建请求、修改请求、配置请求、终结请求、激活请求、注销请求、性能测量任务请求、性能阈值监测请求和告警信息上报请求。
  24. 根据权利要求21至23任一项所述的网络设备，其特征在于，所述参数包括以下至少一项：使用所述网络实例的用户数量阈值、所述网络实例运行的分组数据单元会话数量阈值、使用所述网络实例的用户使用的流量阈值、所述网络实例的服务水平协议参数阈值、所述网络实例的服务质量参数阈值、所述网络实例的关键性能指标参数阈值、第三方管理模块的标识、使用所述网络实例的用户在单位地理位置区间内的平均移动速度阈值、使用所述网络实例的用户在单位时间内发生小区切换的数量阈值、所述网络实例的故障告警类型标识、所述网络实例的故障告警严重性标识、所述网络实例的故障事件标识、所述网络实例的资源利用率阈值、其他管理请求标识、所述第一管理请求的执行时间和所述第一管理请求的执行等待时间。
  25. 根据权利要求24所述的网络设备，其特征在于，当满足以下至少一项时所述执行条件满足：使用所述网络实例的用户的数量达到所述用户数量阈值、所述网络实例运行的分组数据单元会话数量达到所述分组数据单元会话数量阈值、使用所述网络实例的用户单位时间内累积使用的流量阈值达到所述用户使用的流量阈值、所述网络实例的服务水平协议参数达到所述服务水平协议参数阈值、所述网络实例的服务质量参数达到所述服务质量参数阈值、所述网络实例的关键性能指标参数达到所述关键性能指标参数阈值、所述第一网络设备接收到所述第三方管理模块的标识对应的所述第三方管理模块发送的请求、使用所述网络实例的用户在单位地理位置区间内的平均移动速度达到所述平均移动速度阈值、使用所述网络实例的用户在单位时间内发生小区切换的数量达到所述发生小区切换的数量阈值、所述第一网络设备接收到与所述故障告警类型标识一致的告警信息、所述第一网络设备接收到与所述故障告警严重性标识一致的告警信息、所述第一网络设备发生所述故障事件标识对应的故障事件、所述网络实例的资源利用率达到所述资源利用率阈值、所述第一网络设备执行所述其他管理请求标识对应的管理请求后、所述执行时间到达、从所述第一网络设备接收到所述第一管理请求的时刻起计时达到所述执行等待时间。
  26. 一种网络设备，其特征在于，所述网络设备为第二网络设备，所述第二网络设备包括处理器、存储器、接收器和发射器，所述存储器用于存储程序代码，所述处理器用于调用所述存储器中的程序代码执行如下操作：
    确定第一管理请求，所述第一管理请求包括执行条件的参数，所述参数与网络实例相关；
    通过所述发射器向第一网络设备发送所述第一管理请求，所述第一管理请求用于指示所述第一网络设备在所述执行条件满足时针对所述网络实例执行所述第一管理请求；所述第一网络设备为网络切片管理功能设备，所述第二网络设备为通信业务管理功能设备；或者，所述第一网络设备为网络切片子网管理功能设备，所述第二网络设备为网络切片管理功能设备。
  27. 根据权利要求26所述的网络设备，其特征在于，所述网络实例包括以下至少一项：网络切片实例、网络切片子网实例和网络功能。
  28. 根据权利要求26或27所述的网络设备，其特征在于，所述第一管理请求包括以下任一项：创建请求、修改请求、配置请求、终结请求、激活请求、注销请求、性能测量任务请求、性能阈值监测请求和告警信息上报请求。
  29. 根据权利要求26至28任一项所述的网络设备，其特征在于，所述参数包括以下至少一项：使用所述网络实例的用户数量阈值、所述网络实例运行的分组数据单元会话数量阈值、使用所述网络实例的用户使用的流量阈值、所述网络实例的服务水平协议参数阈值、所述网络实例的服务质量参数阈值、所述网络实例的关键性能指标参数阈值、第三方管理模块的标识、使用所述网络实例的用户在单位地理位置区间内的平均移动速度阈值、使用所述网络实例的用户在单位时间内发生小区切换的数量阈值、所述网络实例的故障告警类型标识、所述网络实例的故障告警严重性标识、所述网络实例的故障事件标识、所述网络实例的资源利用率阈值、其他管理请求标识、所述第一管理请求的执行时间和所述第一管理请求的执行等待时间。
  30. 根据权利要求29所述的网络设备，其特征在于，当满足以下至少一项时所述执行条件满足：使用所述网络实例的用户的数量达到所述用户数量阈值、所述网络实例运行的分组数据单元会话数量达到所述分组数据单元会话数量阈值、使用所述网络实例的用户单位时间内累积使用的流量阈值达到所述用户使用的流量阈值、所述网络实例的服务水平协议参数达到所述服务水平协议参数阈值、所述网络实例的服务质量参数达到所述服务质量参数阈值、所述网络实例的关键性能指标参数达到所述关键性能指标参数阈值、所述第一网络设备接收到所述第三方管理模块的标识对应的所述第三方管理模块发送的请求、使用所述网络实例的用户在单位地理位置区间内的平均移动速度达到所述平均移动速度阈值、使用所述网络实例的用户在单位时间内发生小区切换的数量达到所述发生小区切换的数量阈值、所述第一网络设备接收到与所述故障告警类型标识一致的告警信息、所述第一网络设备接收到与所述故障告警严重性标识一致的告警信息、所述第一网络设备发生所述故障事件标识对应的故障事件、所述网络实例的资源利用率达到所述资源利用率阈值、所述第一网络设备执行所述其他管理请求标识对应的管 理请求后、所述执行时间到达、从所述第一网络设备接收到所述第一管理请求的时刻起计时达到所述执行等待时间。
  31. 一种通信系统，其特征在于，包括第一网络设备和第二网络设备，所述第一网络设备为如权利要求11-15任一项所述的第一网络设备，所述第二网络设备为如权利要求16-20任一项所述的第二网络设备；或者，所述第一网络设备为如权利要求21-25任一项所述的第一网络设备，所述第二网络设备为如权利要求26-30任一项所述的第二网络设备。
  32. 一种计算机存储介质，所述计算机存储介质上存储有计算机程序，其特征在于，所述计算机程序被处理器执行时实现权利要求1至5任一项所述的方法。
  33. 一种计算机存储介质，所述计算机存储介质上存储有计算机程序，其特征在于，所述计算机程序被处理器执行时实现权利要求6至10任一项所述的方法。
  34. 一种包含指令的计算机程序产品，其特征在于，当所述计算机程序产品在计算机上运行时，使得所述计算机执行如权利要求1至5任一项所述的方法。
  35. 一种包含指令的计算机程序产品，其特征在于，当所述计算机程序产品在计算机上运行时，使得所述计算机执行如权利要求6至10任一项所述的方法。
  36. 一种装置，其特征在于，包括处理器以及耦合于所述处理器的一个或多个接口，所述处理器用于从存储器调用程序代码，执行权利要求1至5任一项所述的方法，所述接口用于输出所述处理器的处理结果。
  37. 一种装置，其特征在于，包括处理器以及耦合于所述处理器的一个或多个接口，所述处理器用于从存储器调用程序代码，执行权利要求6至10任一项所述的方法，所述接口用于输出所述处理器的处理结果。
PCT/CN2018/099683 2017-08-11 2018-08-09 一种网络实例管理方法及相关设备 WO2019029636A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710689723.0 2017-08-11
CN201710689723.0A CN109391505B (zh) 2017-08-11 2017-08-11 网络实例管理方法及相关设备

Publications (1)

Publication Number Publication Date
WO2019029636A1 true WO2019029636A1 (zh) 2019-02-14

Family

ID=65270899

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/099683 WO2019029636A1 (zh) 2017-08-11 2018-08-09 一种网络实例管理方法及相关设备

Country Status (2)

Country Link
CN (1) CN109391505B (zh)
WO (1) WO2019029636A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113300862A (zh) * 2020-02-24 2021-08-24 中国移动通信有限公司研究院 一种告警处理方法、装置及设备
US11246088B2 (en) 2020-04-10 2022-02-08 Cisco Technology, Inc. Failover and management of multi-vendor network slices

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110086880B (zh) * 2019-05-07 2020-05-22 北京字节跳动网络技术有限公司 创建网络请求的实例的方法和装置
CN112188608B (zh) * 2019-07-04 2022-01-14 华为技术有限公司 一种同步pdu会话状态的方法、装置、系统及芯片
CN112350841B (zh) * 2019-08-08 2022-05-17 华为技术有限公司 一种管理数据的获取方法及装置
CN112838942B (zh) * 2019-11-25 2024-09-03 南京中兴新软件有限责任公司 网络运维方法、电子设备以及存储介质
CN111897543A (zh) * 2020-01-16 2020-11-06 中兴通讯股份有限公司 一种软件管理方法、装置、管理设备及存储介质
CN111552569B (zh) * 2020-04-28 2023-10-20 咪咕文化科技有限公司 系统资源调度方法、装置及存储介质
CN113595754B (zh) * 2020-04-30 2024-10-15 中国移动通信集团北京有限公司 网络切片管理装置、方法、设备以及介质
CN113993148B (zh) * 2020-07-10 2023-08-15 中国移动通信集团浙江有限公司 基于机器学习的5g网络切片容灾切换方法及装置
CN112235140B (zh) * 2020-10-13 2022-11-08 中移（杭州）信息技术有限公司 网络切片管理方法、装置、网络设备和存储介质
CN112422344A (zh) * 2020-11-18 2021-02-26 青岛海尔科技有限公司 日志异常的告警方法、装置、存储介质及电子装置
CN115277458B (zh) * 2021-04-30 2023-11-17 阿里巴巴新加坡控股有限公司 服务提供方法、设备及存储介质
CN113535359B (zh) * 2021-07-23 2023-11-10 中国科学技术大学苏州高等研究院 一种多租户云中服务请求调度方法和装置
CN116206608A (zh) * 2021-12-01 2023-06-02 中国电信股份有限公司 网络意图处理方法及相关设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170070892A1 (en) * 2015-09-07 2017-03-09 Electronics And Telecommunications Research Institute Mobile communication network system and method for composing network component configurations
CN106657194A (zh) * 2015-11-02 2017-05-10 中兴通讯股份有限公司 一种网络切片能力开放的方法、装置及系统
CN106982458A (zh) * 2017-03-09 2017-07-25 华为技术有限公司 一种网络切片的选择方法及装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106341832B (zh) * 2015-07-07 2020-11-06 中国移动通信集团公司 网络切片的管理及选择方法、系统、基站、路由交换设备
CN106549806B (zh) * 2016-10-26 2019-06-18 清华大学 一种网络切片管理器及其管理方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170070892A1 (en) * 2015-09-07 2017-03-09 Electronics And Telecommunications Research Institute Mobile communication network system and method for composing network component configurations
CN106657194A (zh) * 2015-11-02 2017-05-10 中兴通讯股份有限公司 一种网络切片能力开放的方法、装置及系统
CN106982458A (zh) * 2017-03-09 2017-07-25 华为技术有限公司 一种网络切片的选择方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
3GPP: "3rd Generation Partnership Project;Technical Specification Group Services and System Aspects;Study on security aspects of 5G network slicing management(Release 15)", 3GPP TR 33.811 V0.6.0, June 2018 (2018-06-01), XP055572010 *
SA WG5: "New WID on Management of Network Slicing in Mobile Networks, Concepts, Use Cases and Requirements", 3GPP TSG SA MEETING #76 TD SP-170491, 1 June 2017 (2017-06-01), XP051283812 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113300862A (zh) * 2020-02-24 2021-08-24 中国移动通信有限公司研究院 一种告警处理方法、装置及设备
CN113300862B (zh) * 2020-02-24 2023-03-31 中国移动通信有限公司研究院 一种告警处理方法、装置及设备
US11246088B2 (en) 2020-04-10 2022-02-08 Cisco Technology, Inc. Failover and management of multi-vendor network slices

Also Published As

Publication number Publication date
CN109391505A (zh) 2019-02-26
CN109391505B (zh) 2022-03-11

Similar Documents

Publication Publication Date Title
WO2019029636A1 (zh) 一种网络实例管理方法及相关设备
US11070989B2 (en) Network slice management method, management unit, and system
US11418410B2 (en) Communication method, apparatus, and system
JP2021526768A (ja) 警報方法および警報装置
US20180338278A1 (en) Wi-fi roaming management
WO2016115371A1 (en) System and method for elastic scaling using a container-based platform
WO2016054922A1 (zh) 决策协调方法、执行装置和决策协调器
CN108206764B (zh) 网络设备配置信息的配置方法、服务器和计算机可读介质
US9503317B2 (en) Method and device for processing communication path
US11144423B2 (en) Dynamic management of monitoring tasks in a cloud environment
WO2018103665A1 (zh) 基于l2tp的设备管理方法、设备及系统
KR20220103796A (ko) 노드 관리 방법, 장치, 디바이스, 저장 매체 및 시스템
JP2016511451A (ja) ネットワーク機能を開くためのシステムおよび方法、ならびに関連するネットワーク要素
CN106302028B (zh) 流量监控方法以及装置
EP2953295A1 (en) Automatic delta event synchronization in multiple manager-agent environments
US20220278905A1 (en) Intent execution method and apparatus
WO2018177003A1 (zh) 一种计费方法、相关设备和系统
US9172596B2 (en) Cross-network listening agent for network entity monitoring
WO2024024106A1 (ja) ネットワーク負荷の予測開始タイミングの制御
WO2024024107A1 (ja) ネットワーク負荷の予測開始タイミングの制御
WO2024004102A1 (ja) キューに格納されている性能指標値データに基づく通信システムの状態判定
WO2024004104A1 (ja) 通信システムに含まれる要素の適切なスケールアウトの実行
US20240372891A1 (en) Automated remediation of denial-of-service attacks in cloud-based 5g networks
WO2024047774A1 (ja) 通信システムに係る所与の予測目的で用いられる機械学習モデルの決定
WO2024069948A1 (ja) 通信システムに含まれるハードウェアリソースの管理

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18843587

Country of ref document: EP

Kind code of ref document: A1