WO2019238004A1 - 一种告警的方法及装置 - Google Patents
一种告警的方法及装置 Download PDFInfo
- Publication number
- WO2019238004A1 WO2019238004A1 PCT/CN2019/090525 CN2019090525W WO2019238004A1 WO 2019238004 A1 WO2019238004 A1 WO 2019238004A1 CN 2019090525 W CN2019090525 W CN 2019090525W WO 2019238004 A1 WO2019238004 A1 WO 2019238004A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- instance
- identification information
- service entity
- alarm
- request
- Prior art date
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/06—Management of faults, events, alarms or notifications
- H04L41/0604—Management of faults, events, alarms or notifications using filtering, e.g. reduction of information by using priority, element types, position or time
- H04L41/0627—Management of faults, events, alarms or notifications using filtering, e.g. reduction of information by using priority, element types, position or time by acting on the notification or alarm source
-
- 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/0686—Additional information in the notification, e.g. enhancement of specific meta-data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- 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/0604—Management of faults, events, alarms or notifications using filtering, e.g. reduction of information by using priority, element types, position or time
- H04L41/0618—Management of faults, events, alarms or notifications using filtering, e.g. reduction of information by using priority, element types, position or time based on the physical or logical position
-
- 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/34—Signalling channels for network management communication
- H04L41/342—Signalling channels for network management communication between virtual entities, e.g. orchestrators, 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/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/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/04—Arrangements for maintaining operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/18—Service support devices; Network management devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
Definitions
- the present application relates to the field of communication technologies, and in particular, to a method and a device for alarming.
- the 5th-generation (5G) system introduces network slice (NS) technology.
- the network slice refers to a logical network that is customized on the physical or virtual network infrastructure according to different service requirements. After being instantiated into a specific network slice instance (NSI), the network slice becomes a real-running logical network that meets certain network characteristics or service requirements.
- NSI can be created through network function virtualization (NFV) technology.
- NFV network function virtualization
- a network slice needs to meet one or more network functions.
- NSI created by NFV technology can include one or more network functions.
- An instance network function instance, NFI
- NFI network function instance
- VNF virtual network function
- NFVI NFV infrastructure
- NFI is composed of multiple VNF instances and connections between VNF instances.
- Composition since one NSI can include one or more NFIs, it can be understood that one NSI can include multiple VNF instances and connections between VNF instances, so the deployment of NSI is achieved by deploying NFI.
- a VNF instance usually consists of multiple VNF component (VNF component) instances.
- each NFI belongs to the entire network, so the VNF instances included in each NFI also belong to the entire network.
- NFI deployed resources in NFVI such as the virtual machine where NFI is deployed
- the following types of alarms may be generated.
- One type is the alarm generated by the failure of the resource deployed by NFI in NFVI. The following is to distinguish other alarms.
- Virtual resource alarms are another type of alarms caused by the failure of a VNF instance deployed on the failed resource caused by the failure of a resource deployed with NFI in NFVI. This type of alarm is referred to as a VNF alarm below.
- Management and orchestration (MANO) network elements in the NFV architecture can associate virtual resource alarms with corresponding VNF alarms, and element management system (EMS) entities can perform network function instances carried in VNF alarms Associated with the virtual resource alert to the corresponding NFI.
- EMS element management system
- NFI Network slicing technology
- multiple network slices may need to implement the same network function, so the same NFI may be shared by multiple NSIs.
- the NFI deployment resource in NFVI fails, if NFI is unique to a network slice, it will only cause one network slice instance to fail. However, if NFI is shared by multiple network slices, it will cause deployment to the failure. Multiple network slice instances on the resource failed.
- a method for associating a virtual resource alarm to a corresponding NFI is provided, and there is no method for associating a virtual resource alarm to a corresponding network slice instance. Therefore, the prior art cannot analyze the cause of the failure of the network slice instance.
- the embodiments of the present application provide an alarm method and device, which are used to solve the problem that the cause of the failure of the network slice instance cannot be analyzed in the prior art.
- an alarm method may be executed by a first service entity or a chip within the first service entity, where the first service entity may be a network slice management function (NSMF) entity or A network subslice management function (NSSMF) entity, the first service entity is used to manage a network slice instance.
- the method includes: first, a first service entity sends a first request to a second service entity, the second service entity is used to manage an alarm of a network function instance, the first request includes identification information of the VNF instance, and the first request is used for Requesting a virtual resource alarm carrying the identification information, the VNF instance has a corresponding relationship with the first network slice instance managed by the first service entity.
- the second service entity determines, from at least one virtual resource alarm received from the MANO network element, a virtual resource alarm carrying identification information of the VNF instance. Then, the second service entity sends the virtual resource alarm to the first service entity in a first response.
- the first service entity sends a first request carrying the identification information of the VNF instance to the second service entity, requesting the second service entity to send it a virtual resource alarm carrying the identification information of the VNF instance, and the second service entity Among the at least one virtual resource alarm received from the MANO network element, a virtual resource alarm carrying identification information of the VNF instance is determined, and the virtual resource alarm is sent to a first service entity. Because the VNF instance has a corresponding relationship with the first network slice instance, the first service entity can associate the virtual resource alarm to the first network slice instance according to the corresponding relationship, so that when a failure occurs in the network slice instance, the The virtual resource alarm associated with the network slice instance analyzes the cause of the failure of the network slice instance.
- the identification information of the VNF instance included in the first request may be one or multiple, which is not limited in this application.
- the identification information of the VNF instance may be carried in an alarm filtering list included in the first request, and the alarm filtering list has a corresponding relationship with the first network slice instance.
- the first request further includes a first correspondence relationship, where the first correspondence relationship is a correspondence relationship between the alarm filtering list and the first network slice instance.
- the second service entity may further store the alarm filtering list and the first correspondence relationship. In this way, the second service entity can use the stored alarm filtering list and the first correspondence relationship to associate the virtual resource alarm received from the MANO network element with the corresponding network slice instance, so that when a fault occurs in the network slice instance, it can The virtual resource alarm to the network slice instance analyzes the cause of the failure of the network slice instance.
- the first service entity may further associate the virtual resource alarm carried in the first response with the first network slice instance.
- the virtual resource alarm may be associated with the first network slice instance at the first service entity, and of course, the virtual resource alarm may be associated with the first network slice instance at the second service entity.
- the first service entity after receiving the virtual resource alarm from the second service entity, the first service entity associates the virtual resource alarm to a pre-stored, including all resources according to the identification information of the VNF instance carried in the virtual resource alarm.
- the alarm filter list of the identification information of the VNF instance is described, and the virtual resource alarm is associated with the first network slice instance that has a corresponding relationship with the alarm filter list according to the pre-stored first correspondence relationship, and the first correspondence relationship is Correspondence between the first network slice instances.
- the identification information of the VNF instance will be carried.
- the virtual resource alarm is associated with an alarm filter list including identification information of the VNF instance, and according to a first correspondence relationship, the virtual resource alarm is associated with a first network slice instance that has a correspondence relationship with the alarm filter list.
- the second service entity may send the association to the first network slice instance to the first service entity (ie, the entity that manages the first network slice instance).
- Virtual resource alarm The second service entity may send actively or passively. In one implementation manner, the second service entity passively sends a virtual resource alarm associated with the first network slice instance to the first service entity.
- the second service entity receives a second request from the first service entity, the second request carries identification information of the first network slice instance, the second request is used to request a virtual resource alarm associated with the first network slice instance, and the second service The entity sends a second response to the first service entity, and the second response carries a virtual resource alarm associated with the first network slice instance.
- the first service entity may request the second service entity to carry the identifier of the VNF instance included in the alarm filtering list.
- Informational virtual resource alert if the second service entity does not associate the virtual resource alarm to the first network slice instance, the first service entity may request the second service entity to carry the identifier of the VNF instance included in the alarm filtering list.
- Informational virtual resource alert if the second service entity does not associate the virtual resource alarm to the first network slice instance, the first service entity may request the second service entity to carry the identifier of the VNF instance included in the alarm filtering list.
- Informational virtual resource alert Informational virtual resource alert.
- the first service entity sends a second request to the second service entity, the second request carries identification information of the first network slice instance, and the second request is used to request to carry the VNF included in the alarm filtering list
- the first service entity receives a second response from the second service entity, and the second response carries the virtual resource alarm.
- the identification information of the VNFC instance may also be carried in the first request, and the VNFC instance is a VNFC instance included in the VNF instance and belonging to the first network slice instance, so that the VNF instance can be carried.
- the virtual resource alert of the identification information of the VNFC instance and the identification information of the VNFC instance is more accurately associated with the network slice instance.
- the identification information of the VNFC instance is carried in the first request, the first request is used to request a virtual resource alarm that carries the identification information of the VNF instance and the identification information of the VNFC instance.
- the first service entity sends a third request to the third service entity.
- the third request carries the identification information of the first network slice instance, and the third request is used to request a correspondence with the first network slice instance.
- the third service entity receives the third request, according to the identification information of the related VNF instance, according to the correspondence between the identification information of the first network slice instance and the identification information of multiple network slice instances stored in advance and the identification information of the VNF instance.
- the first The service entity further generates an alarm filtering list according to the identification information of the VNF instance, and generates a first correspondence relationship according to the alarm filtering list and the identification information of the first network slice instance.
- the alarm filtering list in addition to the identification information of the VNF instance, also carries identification information of the VNFC instance belonging to the first network slice instance included in the VNF instance.
- the third request sent by the first service entity to the third service entity is also used to request the identification information of the VNFC instance belonging to the first network slice instance included in the VNF instance. Accordingly, the third service After receiving the third request, the entity searches for the correspondence between the first network slice instance identification information and the pre-stored identification information of multiple network slice instances and the VNF instance identification information and the VNFC instance identification information.
- the identification information of the VNF instance and the VNFC instance that have a corresponding relationship in the network slice instance, and the identification information of the VNF instance and the VNFC instance that have a corresponding relationship with the first network slice instance are carried in the third response and sent to The first service entity.
- the first service entity After receiving the identification information of the VNF instance and the identification information of the VNFC instance sent by the third service entity, the first service entity generates an alarm filter according to the identification information of the VNF instance and the identification information of the VNFC instance. List, and generate a first corresponding threshold according to the alarm filtering list and the identification information of the first network slice instance .
- an alarm method is provided.
- the method may be executed by a second service entity or a chip in the second service entity, where the second service entity may be a network function management function (NFMF) entity or EMS entity, the second service entity is used to manage the alarm of the network function instance.
- the method includes: a second service entity receives a first request from a first service entity, the first service entity is used to manage a network slice instance, and the first request includes identification information of the first network slice instance managed by the first service entity, The first request is used to request a virtual resource alarm associated with the first network slice instance.
- the second service entity sends a second request to the third service entity.
- the third service entity is used to manage the network function instance.
- the second request carries the identification information of the first network slice instance.
- the second request is used to request that the network slice belongs to the first network slice.
- Identification information of the VNF instance of the instance the VNF instance is used to deploy a network function instance belonging to the first network slice instance
- the second service entity receives a second response from the third service entity, and the second response carries the VNF instance Identification information.
- the second service entity determines, from at least one virtual resource alarm received from the MANO network element, a virtual resource alarm carrying identification information of the VNF instance, and sends the virtual resource alarm carrying the identification information of the VNF instance and the first Network slice instance association.
- the second service entity sends a first response to the first service entity, and the first response includes a virtual resource alarm associated with the first network slice instance.
- the second service entity may, based on the identification information of the first network slice instance included in the received first request and the identification information of the VNF instance belonging to the first network slice instance, receive at least one message from the MANO network element.
- a virtual resource alarm a virtual resource alarm carrying identification information of the VNF instance is determined, and the virtual resource alarm carrying identification information of the VNF instance is associated with the first network slice instance.
- the cause of the failure in the network slice instance can be analyzed according to the virtual resource alarm associated with the first network slice instance.
- the second service entity may also send the second request to the third service entity before receiving the first request from the first service entity, which is not limited in this application.
- the second request is further used for requesting identification information of the VNFC instance.
- the VNFC instance is a VNFC instance included in the VNF instance and belonging to the first network slice instance.
- the second response also carries the The identification information of the VNFC instance is described.
- the second service entity determines, in at least one virtual resource alarm received from the MANO network element, a virtual resource alarm that carries the identification information of the VNF instance and the identification information of the VNFC instance, and carries the VNF instance.
- the virtual resource alarm of the identification information of the VNFC instance and the identification information of the VNFC instance is associated with the first network slice instance. When a failure occurs in the first network slice instance, the cause of the failure in the network slice instance can be analyzed according to the virtual resource alarm associated with the first network slice instance.
- the second request may also carry identification information of the first network function instance, where the first network function instance is one of the network function instances included in the first network slice instance, and the VNF instance is used
- the VNFC instance is a VNFC instance included in the VNF instance and belonging to the first network function instance.
- the second service entity can request the third service entity to deploy a VNF instance of a part of the network function instance included in the network slice instance.
- the second service entity may generate and combine the identification information of the VNF instance and the identification information of the VNFC instance carried in the second response.
- the alarm filtering list includes identification information of the VNF instance and identification information of the VNFC instance, and generates and stores a first correspondence relationship according to the alarm filtering list and identification information of the first network slice instance.
- the corresponding relationship is the corresponding relationship between the alarm filtering list and the first network slice instance.
- the second service entity may also determine, in at least one virtual resource alarm received from the MANO network element, a virtual resource alarm that carries the identification information of the VNF instance and the identification information of the VNFC instance included in the alarm filtering list, and According to the first correspondence, the virtual resource alarm carrying the identification information of the VNF instance and the identification information of the VNFC instance is associated with the first network slice instance.
- an alarm device has a function of implementing the first service entity in the foregoing method embodiment.
- This function can be realized by hardware, and can also be implemented by hardware executing corresponding software.
- the hardware or software includes one or more modules corresponding to the above functions.
- the device includes: a processor, a transceiver, and a memory; the memory is used to store computer execution instructions; the transceiver is used to enable the device to communicate with other communication entities; the processor communicates with the memory through The bus is connected.
- the processor executes the computer execution instructions stored in the memory, so that the device executes the method of the first aspect or the second aspect.
- the device includes: a processing unit, a transceiver unit, and a storage unit; the storage unit is configured to store computer execution instructions; the transceiver unit is configured to enable the device to communicate with other communication entities; and the processing unit and The storage unit is connected through a bus.
- the processing unit executes the computer execution instructions stored by the storage unit, so that the device executes the method of the first aspect or the second aspect.
- an alarm device has a function of implementing the second service entity in the foregoing method embodiment.
- This function can be realized by hardware, and can also be implemented by hardware executing corresponding software.
- the hardware or software includes one or more modules corresponding to the above functions.
- the device includes: a processor, a transceiver, and a memory; the memory is used to store computer execution instructions; the transceiver is used to enable the device to communicate with other communication entities; the processor communicates with the memory through The bus is connected.
- the processor executes the computer execution instructions stored in the memory, so that the device executes the method of the first aspect or the second aspect.
- the device includes: a processing unit, a transceiver unit, and a storage unit; the storage unit is configured to store computer execution instructions; the transceiver unit is configured to enable the device to communicate with other communication entities; and the processing unit and The storage unit is connected through a bus.
- the processing unit executes the computer execution instructions stored by the storage unit, so that the device executes the method of the first aspect or the second aspect.
- an alarm device has a function of implementing the third service entity in the foregoing method embodiment.
- This function can be realized by hardware, and can also be implemented by hardware executing corresponding software.
- the hardware or software includes one or more modules corresponding to the above functions.
- the device includes: a processor, a transceiver, and a memory; the memory is used to store computer execution instructions; the transceiver is used to enable the device to communicate with other communication entities; the processor communicates with the memory through The bus is connected.
- the processor executes the computer execution instructions stored in the memory, so that the device executes the method of the first aspect or the second aspect.
- the device includes: a processing unit, a transceiver unit, and a storage unit; the storage unit is configured to store computer execution instructions; the transceiver unit is configured to enable the device to communicate with other communication entities; and the processing unit and The storage unit is connected through a bus.
- the processing unit executes the computer execution instructions stored by the storage unit, so that the device executes the method of the first aspect or the second aspect.
- an embodiment of the present application provides a computer storage medium for storing computer software instructions used by the first service entity, which includes a program designed to execute the foregoing aspect for the first service entity.
- an embodiment of the present application provides a computer storage medium for storing computer software instructions used by the second service entity, which includes a program designed to execute the foregoing aspect for the second service entity.
- an embodiment of the present application provides a computer program product.
- the computer program product includes computer software instructions, and the computer software instructions can be loaded by a processor to implement the processes in the first aspect or the second aspect of the method.
- an embodiment of the present application provides a chip, which includes a processor, a transceiver component, and optionally, a memory, which is configured to execute the foregoing method of the first aspect or the second aspect.
- FIG. 1 is a schematic diagram of an overall architecture of a NFV system applicable to an embodiment of the present application
- FIG. 2 is a schematic diagram of a network architecture composed of network slice instances
- FIG. 3 is a flowchart of a method for associating a virtual resource alarm with a network function instance
- FIG. 5 is a schematic diagram of a first correspondence relationship according to an embodiment of the present application.
- FIG. 6 is a schematic diagram of a correspondence between identification information of a network slice instance and identification information of a VNF instance according to an embodiment of the present application
- FIG. 7 is a schematic diagram of an alarm filtering list according to an embodiment of the present application.
- FIG. 8 is a schematic diagram of a first correspondence relationship according to an embodiment of the present application.
- FIG. 9 is a flowchart of generating an alarm filtering list and a first correspondence relationship according to an embodiment of the present application.
- FIG. 10 is a flowchart of another alarm method according to an embodiment of the present application.
- FIG. 11 is a flowchart of another alarm method according to an embodiment of the present application.
- FIG. 12 is a schematic structural diagram of an alarm device according to an embodiment of the present application.
- FIG. 13 is a schematic structural diagram of another alarm device according to an embodiment of the present application.
- the network slice can be an end-to-end logical network including terminal equipment, access network, transmission network, core network, and application server, which can provide complete communication services.
- the network slice can also be a logical network composed of any combination of terminal equipment, access network, transmission network, core network, and application server.
- Network slices can be created through a variety of technologies, for example, through NFV technology and software-defined network (SDN) technology. This embodiment of the present application is described based on only creating a network slice through the NFV technology.
- SDN software-defined network
- FIG. 1 is a schematic diagram of an overall architecture of a NFV system applicable to an embodiment of the present application.
- the NFV system 100 includes: management and orchestration (MANO) network element 101, NFV infrastructure (NFV infrastructure) layer 130, multiple virtual network functions (VNF) ) 108 (VNF1, VNF2, and VNF3), a network function management function (NFMF) network element 122, and an operation-support system / business support system (OSS / BSS) 124.
- the MANO 101 includes a NFV orchestrator (NFVO) 102, one or more VNF managers (VNFM) 104, and a virtualized infrastructure manager (VIM) 106.
- NFVO NFV orchestrator
- VNFM VNF managers
- VIP virtualized infrastructure manager
- the OSS / BSS 124 may include communication service management function (CSMF) network elements, network slice management function (NSMF) network elements, and network subnet slice management function. function (NSSMF) network element.
- An end-to-end network slice can include various parts such as the radio access network, transmission network, and core network. Each part is called a subnet slice.
- the NSSMF function is responsible for managing subnet slices.
- NSMF is responsible for managing end-to-end network slicing.
- NSSMF and NSMF have similar functions. The difference is that NSSMF accepts the service requirements of subnets (for example, core network, transmission network, and access network), and creates subnet slice instances (network substances, NSSI).
- NFVI 130 includes a hardware resource layer, a virtualization layer, and a virtual resource layer.
- the hardware resource layer includes computing hardware 112, storage hardware 114, and network hardware 116.
- the virtual resource layer includes virtual computing 110, virtual Storage 118 and virtual network 120.
- FIG. 1 is only an example of a possible architecture.
- the NSMF network element can also directly manage network functions, that is, it has related functions of the NFMF network element.
- the NFMF network element 122 is set separately.
- the NFMF network element 122 may be replaced with an element management system (EMS) entity.
- the EMS entity is an entity used to configure and manage equipment in a traditional telecommunications system.
- the EMS entity can also be used to configure and manage VNF108, and can also be used to initiate VNFM104 lifecycle management operations such as the instantiation of a new VNF.
- the foregoing network element in the embodiment of the present application may be a physical physical network element or a virtual network element, which is not limited herein.
- NSMF network elements may also be referred to as NSMF functions or NSMF functional entities
- NFMF network elements may also be referred to as NFMF functions or NFMF functional entity.
- the names of the various network elements are not limited in this application. Those skilled in the art can change the names of the above network elements to other names to perform the same functions, which all fall within the scope of protection of this application.
- each network element included in the NFV system 100 The functions of each network element included in the NFV system 100 are described below.
- MANO101 is used to allocate the infrastructure resources required for network slicing, complete the deployment of virtual network functions on the virtualized infrastructure, and complete the network connection between network function entities according to the NFV deployment requirements of network slice management functions.
- NFVO102 is mainly responsible for the life cycle management of virtualized services, and the allocation and scheduling of virtual resources in virtual infrastructure and NFVI.
- NFVO 102 can communicate with one or more VNFM 104 to execute resource related requests, send configuration information to VNFM 104, and collect VNF 108 status information.
- NFVO 102 can also communicate with VIM 106, perform resource allocation, and / or reservation, and exchange virtual hardware resource configuration and status information.
- VNFM104 is mainly responsible for the life cycle management of one or more VNFs, such as instantiating, updating, querying, scaling, and terminating VNF108. VNFM104 can also communicate with VNF108 to complete VNF lifecycle management and exchange configuration and status information. There can be multiple VNFMs in the NFV architecture, which are responsible for life cycle management of different types of VNFs.
- VIM 106 is mainly responsible for controlling and managing the interaction between VNF 108 and computing hardware 112, storage hardware 114, network hardware 116, virtual computing 110, virtual storage 118, and virtual network 120.
- VIM 106 performs resource management functions, including managing infrastructure resources, allocating (such as adding resources to virtual containers), and running functions (such as collecting NFVI failure information).
- VNFM104 and VIM106 can communicate with each other, request resource allocation, and exchange virtual hardware resource configuration and status information.
- NFVI130 is the infrastructure layer of NFV. It can include hardware components, software components, or a combination of both to establish a virtualized environment, deploy, manage, and implement VNF108.
- the hardware resources and virtualization layer are used to provide VNF108 with virtualization resources, such as virtual machines and other forms of virtual containers.
- the hardware resources include computing hardware 112, storage hardware 114, and network hardware 116. As an implementation, the resources of the computing hardware 112 and the storage hardware 114 may be centralized.
- the virtualization layer in NFVI can abstract hardware resources and decouple VNF108 from the underlying physical network layer.
- Each VNF 108 runs in one or more virtual containers, corresponding to a set of network functions belonging to one or more physical devices.
- OSS / BSS124 supports various end-to-end telecommunication services.
- the management functions supported by OSS can include: network configuration, service provision, fault management, etc.
- the management functions supported by BSS can include: order processing, payment, product management, order management, revenue management, and customer management.
- CSMF is responsible for sending network slice order requests to NSMF according to the customer's communication service requirements. After the network slice instance is created, it is also responsible for managing the communication services carried by the network slice instance.
- NSMF is responsible for the entire life cycle management of network slice instance creation, activation, operation, deactivation, and deletion.
- NSMF accepts customers' network slicing orders and drives virtual orchestration and management functional entities and slice control functional entities to create network slicing instances based on the stored network slicing templates.
- NFMF122 can indirectly manage these network function entities through the NFMF network elements of each manufacturer.
- NSMF network elements implement NFV deployment of network slice instances through interfaces between MANO's NFVO network elements.
- a method for deploying a network slice instance is as follows: After a user orders a network slice, CSMF receives the user's business requirements, converts the business requirements into network slice requirements, and sends the network slice requirements to NSMF; NSMF translates the received network slice requirements into network slice subnet requirements, and sends the network slice subnet requirements to NSSMF; NSSMF converts the network slice subnet requirements into network function instance requirements that need to be deployed, and converts network function instance requirements Sent to MANO101.
- MANO101 performs NFV deployment of network function instances according to the received network function instance requirements.
- VNF instance The network function entity formed at this time can be referred to as a VNF instance. If there are multiple VNF instances generated by the software image of the network function ordered by the user, multiple VNF instances are connected. Generate a complete example of network functions. Among them, a VNF instance usually consists of multiple VNF component (VNFC) instances.
- VNFC VNF component
- a network slice instance can include multiple network function instances. Therefore, when all network function instances included in the network slice instance are deployed, that is, the corresponding VNF instance in the network slice instance is deployed, it can be understood that the network slice instance is deployed. .
- NSMF sends the service configuration script to NFMF122 directly or indirectly through the EMS entity.
- NFMF122 executes the relevant service configuration commands on the VNF instance where the network slice instance is deployed according to the script, so that the services required by the user order can normally run on the network slice stand up.
- the network slice After being instantiated into a specific network slice instance (NSI), the network slice becomes a real running logical network, which can meet certain network characteristics or service requirements.
- the network architecture may include a terminal device, an access network, a core network, and a data network (DN).
- the access network may include access network equipment (such as a base station), and the core network includes multiple core network subnet slice instances (network slice instance 1, network slice instance 2, and network slice instance 3), and network slice selection.
- Function network slice selection function (NSSF) entity, access and mobility management function (AMF) entity.
- the subnet slice instance of each core network can include session management (SMF) entities, network repository function (NRF) entities, policy control function (PCF) entities, and user plane functions (user plane function (UPF)) and other network function entities, and the network function entity in each network slice instance can be deployed through one or more VNF instances.
- the DN can include an application server, which can provide application services to the terminal device, such as: application services can be provided to the terminal device through an application client on the terminal device; the application server can include application layer business processing service module and application functions (application) function (AF) entity.
- the AF entity may be deployed in an application server or independently deployed in a DN for sharing by one or more application servers.
- FIG. 3 is a flowchart of a method for associating a virtual resource alarm with a network function instance in the prior art.
- a VNF instance fails, a network function instance deployed on the VNF instance will fail, and a VNF alarm X will be generated.
- the VNF will report the VNF alarm X carrying the network function instance ID and the VNF instance ID to EMS entity.
- the VNF instance fails, the virtual resources of the VNF instance deployed in the NFVI will fail.
- VNFM determines the VNF instance to which the VM that triggered the virtual resource alarm belongs, adds the identity of the VNF instance to the virtual resource alarm, generates a VNF alarm related to the virtual resource, and reports it to the EMS.
- the EMS correlates the VNF alarm X carrying the same VNF instance ID and the VNF alarm related to the virtual resource to obtain the VNF alarm Y , And according to the network function instance identifier carried in the VNF alarm X, the VNF alarm Y is associated with the corresponding network function instance, and then the virtual resource alarm is associated with the corresponding network function instance.
- the same network function instance may be shared by multiple network slice instances.
- the AMF entity (which can be understood as a network function instance) in Figure 2 Shared by network slice instance 2 and network slice instance 3.
- the resource failure of the AMF entity deployed in NFVI (a virtual resource alarm is generated) will cause network slice instance 2 and network slice instance 3 to fail.
- only virtual resource alarms can be associated with corresponding network function instances. , Can not be accurately associated with the network slice instance, and can not analyze the cause of the network slice instance failure.
- the embodiments of the present application provide an alarm method for the foregoing problem, so as to associate a virtual resource alarm to a corresponding network slice instance, and then analyze the cause of the failure of the network slice instance.
- a flowchart of an alarm method provided for this application includes the following steps:
- S101 The first service entity sends a first request to the second service entity.
- the first service entity is used to manage a network slice instance.
- the alarms of the network slice instances can be managed.
- the alarms can be generated according to the running status of the network slice instances, and the management service consumer entity can be provided with alarm display, alarm notification, alarm confirmation, and alarm clearing services of the network slice.
- the first service entity and the management service consumer entity may be NSMF entities or NSSMF entities. It should be noted that when the first service entity and the management service consumer entity are the same entity, the first service entity will no longer provide the above services to the management service consumer entity.
- the second service entity is used to manage the alarm of the network function instance.
- an alarm may be generated according to the running status of the network function instance, and the management service consumer entity may be provided with alarm display, alarm notification, alarm confirmation, and alarm clearing services of the network function instance.
- the second service entity may be an NFMF entity or an EMS entity.
- the network slice instances involved in the embodiments of the present application may include end-to-end network slice instances and / or subnet slice instances.
- the subnet slice instances may include core network slice instances, access network slice instances, and transmission network slice instances. Wait.
- End-to-end network slicing can provide end devices with end-to-end network services from the access network to the core network, which can include core network slicing, access network slicing, and transmission network slicing.
- the network slice included in the end network slice is referred to as a subnet slice for short. Without specific limitation, the network slice in this article may be an end-to-end network slice or a subnet slice.
- the first request includes identification information of the VNF instance
- the first request is used to request a virtual resource alarm carrying the identification information of the VNF instance
- the VNF instance and a first network managed by the first service entity The slice instances have a corresponding relationship.
- the correspondence between the VNF instance and the first network slice instance means that the VNF instance is a VNF instance in which a network function instance included in the first network slice instance is deployed, and can also be understood as the VNF instance The VNF instance contained in the first network slice instance.
- the VNF instance has a corresponding relationship with the first network slice instance, and the first network slice instance includes the VNF instance, which has the same meaning, and will not be distinguished in the following description.
- the virtual resource alarm may include an alarm generated by a resource failure of a network function instance deployed in NFVI.
- the virtual resource alarm may be a virtual machine and / or a virtual deployment unit (VDU) of a network function instance. Alarms generated by faults.
- the resources for deploying network function instances in NFVI may include virtual CPU, virtual memory, and virtual storage, and may also include the bandwidth used to connect to the virtual network used by each VNF instance.
- the virtual resource alarms referred to in this application refer to virtual resource alarms related to a VNF instance or to a VNFC instance included in a VNF instance.
- the virtual resource alarm related to the VNF instance refers to the virtual resource alarm carrying the identification information of the VNF instance
- the virtual resource alarm related to the VNFC instance included in the VNF instance refers to the identification information carrying the VNF instance and the identification information of the VNFC instance.
- the virtual resource alarm related to the VNF instance or related to the VNFC instance included in the VNF instance is the same as the VNF alarm related to the virtual resource involved in FIG. 3.
- the name of this type of alarm is not limited in this application. The following description applies for uniformly referring to this type of alarm as a virtual resource alarm.
- the VNF instance may be a separate instance that does not include a VNFC instance, and of course, it may also be a VNF instance that includes a VNFC instance, which is not limited in this application.
- VNF instance that includes multiple VNFC instances although it is shared by multiple network slice instances as a whole, in some scenarios, in order to isolate the services of different network slice instances, different VNFC instances included in it are usually used for deployment.
- Network function instances that belong to different network slice instances can be understood as, in this scenario, different VNFC instances included in a VNF instance belong to different network slice instances.
- the identification information of the VNFC instance may also be carried in the first request, and the VNFC instance is a VNFC instance included in the VNF instance and belonging to the first network slice instance, so that the identification information of the VNF instance can be carried
- the virtual resource alarm of the identification information of the VNFC instance is more accurately related to the network slice instance.
- the first request is used to request a virtual resource alarm that carries the identification information of the VNF instance and the identification information of the VNFC instance.
- the first request may further include identification information of the virtual machine deployed by the VNF instance or the VNFC instance and / or identification information of the VDU.
- the second service entity determines, from at least one virtual resource alarm received from the MANO network element, a virtual resource alarm that carries identification information of the VNF instance.
- the MANO network element may be responsible for generating and collecting virtual resource alarms related to the network slice instance during the operation of the network slice instance, and then may periodically or in real time send the generated virtual resource to the second service entity. Resource alert.
- the virtual resource alarm sent by the MANO network element can carry the identification information of the VNF instance, of course, it can also carry the identification information of the VNF instance and the identification information of the VNFC instance.
- the following uses the virtual resource alarm to carry the identification information of the VNF instance as an example. It is explained that the processing procedure of the virtual resource alarm that carries the identification information of the VNF instance and the identification information of the VNFC instance is similar to that of the virtual resource alarm that only carries the identification information of the VNF instance.
- the second service entity may first store it in the second service entity, and after receiving the request message requesting the virtual resource alarm, send it to the entity requesting the virtual resource alarm. Virtual resource alarm.
- This embodiment of the present application does not limit how the second service entity determines the virtual resource alarm carrying the identification information of the VNF instance in at least one virtual resource alarm received from the MANO network element, and a possibility is given below. Implementation.
- the second service entity may compare the identification information of the VNF instance carried in the at least one virtual resource alarm sent by the MANO network element with the VNF instance included in the first request sent by the first service entity.
- the identification information of the virtual resource alarm is determined in the at least one virtual resource alarm received from the MANO network element and carries the identification information of the VNF instance included in the first request. For example, assume that the second service entity receives three virtual resource alarms from the MANO network element, namely virtual resource alarm A, virtual resource alarm B, and virtual resource alarm C, and the identification information of the VNF instance carried in virtual resource alarm A is ID1.
- the identification information of the VNF instance carried in the virtual resource alarm B is ID2
- the identification information of the VNF instance carried in the virtual resource alarm C is ID3
- the identification information of the VNF instance included in the first request is ID2
- the first The two service entities may compare the identification information of the VNF instance carried by the virtual resource alarm A, virtual resource alarm B, and virtual resource alarm C with the identification information of the VNF instance included in the first request as ID2.
- a virtual resource alarm B carrying ID2 is determined.
- the first service entity receives a first response from the second service entity.
- the first response includes a virtual resource alarm carrying identification information of the VNF instance.
- the second service entity determines that there is no virtual resource alarm requested by the first service entity at this time, it waits for the MANO network element to It sends the virtual resource alarm requested by the first service entity. After receiving the virtual resource alarm sent by the MANO network element to the first service entity, it sends the virtual resource alarm to the first service in the first response. entity. If the second service entity receives the first request from the first service entity and determines that the virtual resource alarm requested by the first service entity is stored in the second service entity at this time, the virtual resource alarm may be immediately carried in the first service entity. The response is sent to the first service entity.
- the first service entity sends the first request carrying the identification information of the VNF instance to the second service entity, and requests the second service entity to send it a virtual resource alarm carrying the identification information of the VNF instance.
- the two service entities determine the virtual resource alarm carrying the identification information of the VNF instance in at least one virtual resource alarm received from the MANO network element, and send the virtual resource alarm to the first service entity. Because the VNF instance has a corresponding relationship with the first network slice instance, the first service entity can associate the virtual resource alarm to the first network slice instance according to the corresponding relationship. Specifically, the first service entity can use the virtual resource according to the virtual resource.
- the identification information of the VNF instance carried in the alarm determines the corresponding VNF instance, and then the virtual resource alarm is correctly associated with the first network slice instance according to the correspondence between the VNF instance and the first network slice instance, so that the network slice instance is generated.
- the identification information of the VNF instance included in the first request may be one or multiple, which is not limited in the present application.
- the identification information of the VNF instance may be carried in an alarm filtering list included in the first request, and the alarm filtering list has a corresponding relationship with the first network slice instance.
- the alarm filtering list may further carry identification information of the VNFC instance belonging to the first network slice instance among the multiple VNFC instances, and belongs to the first network slice instance.
- the VNFC instance refers to the VNFC instance used to deploy the network function instance included in the first network slice instance, and no distinction is made in the following description.
- the correspondence between the alarm filtering list and the first network slice instance means that the VNF instance corresponding to the identification information of the VNF instance included in the alarm filtering list is the VNF instance included in the first network slice instance.
- the first request may further include a first correspondence relationship, where the first correspondence relationship is a correspondence relationship between the alarm filtering list and the first network slice instance.
- the first correspondence relationship may be in the form of a list, and of course, it may also be in other forms.
- FIG. 5 is a schematic diagram of a first correspondence relationship provided by an embodiment of the present application.
- the second service entity may further store the alarm filtering list and the first correspondence relationship included in the first request for subsequent use.
- the first service entity may further request the second service entity to send a virtual carrying identification information of all VNF instances included in the alarm filtering list.
- Resource alert the alarm information of the virtual resource alarm may also be requested, and the alarm information includes at least one of alarm identification information and alarm content.
- the first service entity sends a second request to the second service entity, the second request carries identification information of the first network slice instance, and the second request is used to request that the VNF instance included in the alarm filtering list be carried.
- the virtual resource alarm of the identification information so that the second service entity searches for a stored alarm filtering list having a corresponding relationship with the first network slice instance according to the identification information of the first network slice instance and the stored first correspondence relationship, and
- the virtual resource alarm carrying the identification information of the VNF instance included in the alarm filter list is determined according to the alarm filter list, and the virtual resource alarm is carried in the second response and sent to the first service entity.
- the first service entity sends a third request to the third service entity, and the third request carries identification information of the first network slice instance, and the third request is used to request a correspondence with the first network slice instance.
- the third service entity After the third service entity receives the third request, according to the identification information of the related VNF instance, according to the correspondence between the identification information of the first network slice instance and the identification information of multiple network slice instances stored in advance and the identification information of the VNF instance To find the identification information of the VNF instance that has a corresponding relationship with the first network slice instance, and carry the identification information of the VNF instance that has a corresponding relationship to the first network slice instance to the third response and send it to the first service entity, the first The service entity further generates an alarm filtering list according to the identification information of the VNF instance, and generates a first correspondence relationship according to the alarm filtering list and the identification information of the first network slice instance.
- the alarm filtering list in addition to the identification information of the VNF instance, also carries identification information of the VNFC instance belonging to the first network slice instance included in the VNF instance.
- the third request sent by the first service entity to the third service entity is further used to request the identification information of the VNFC instance included in the VNF instance that belongs to the first network slice instance. Accordingly, the third The third response sent by the service entity to the first service entity carries the identification information of the VNFC instance in addition to the identification information of the VNF instance.
- the first service entity receives the identification of the VNF instance sent by the third service entity.
- an alarm filtering list is generated according to the identification information of the VNF instance and the identification information of the VNFC instance, and a first correspondence relationship is generated according to the alarm filtering list and the identification information of the first network slice instance.
- the third service entity may also be used to manage a network function instance.
- the management service consumer entity can be provided with services such as creation, modification, deployment, and business configuration enablement of network function instances.
- the third service entity can allocate virtual resources to the network function instances included in the network function instance by calling a MANO network element, and then can create a virtual machine and / or VDU based on the allocated virtual resources. Generate a VNF instance and make the network function instance run on the VNF instance.
- the third service entity may be an NFMF entity or an EMS entity.
- the following example takes the identification information of the VNF instance and the identification information of the VNFC instance in the alarm filtering list as an example to describe in detail how to generate the alarm filtering list and the first correspondence relationship.
- FIG. 6 it is assumed that a correspondence relationship between identification information of multiple network slice instances and VNF instance identification information stored in advance in a third service entity is shown in FIG. 6, and the correspondence relationship is displayed in the form of a list. Of course, it is not limited, and may be in other forms. And, it is assumed that the identification information of the first network slice instance is ID13. Based on the corresponding relationship in FIG. 6, after receiving the third request for the identification information of the VNF instance and the identification information of the VNFC instance, the third service entity searches for the first network slice instance according to the correspondence between ID13 and FIG. 6. The identification information of the corresponding VNF instance and the identification information of the VNFC instance can be seen from FIG. 6.
- the identification information of the VNF instance and the identification information of the VNFC instance that have a corresponding relationship with the first network slice instance are ID21 and ID33, respectively.
- the ID21 and ID33 are carried in the third response and sent to the first service entity.
- the first service entity further generates an alarm filtering list according to the received identification information of the VNF instance and the identification information (ID21 and ID33) of the VNFC instance.
- FIG. 7 which is a schematic diagram of the generated alarm filtering list and the alarm filtering list
- the first correspondence relationship is generated by the identification information of the first network slice instance.
- FIG. 8 which is a schematic diagram of the generated first correspondence relationship.
- the first network slice instance may include multiple network function instances, and the first service entity may request the third service entity to deploy identification information of VNF instances of all network function instances included in the multiple network function instances.
- the first service entity only requests the third service entity for the identification information of the VNF instance and the identification information of the VNFC instance where the first network function instance is deployed, where the first network function instance is one of the plurality of network function instances. Instance, the identification information of the first network function instance may also be carried in the third request.
- the first service entity does not send the alarm filtering list and the first correspondence to the second service entity.
- the second service entity may generate the alarm filtering list and the first correspondence relationship by itself.
- the following description uses the alarm filtering list to include only identification information of the VNF instance as an example. Refer to FIG. 9, which is a flowchart of generating an alarm filtering list and a first correspondence relationship according to an embodiment of the present application, including the following steps:
- the second service entity sends a fourth request to the third service entity.
- the fourth request carries the identification information of the first network slice instance, and the fourth request is used to request the identification information of the VNF instance included in the first network slice instance.
- the second service entity before sending the fourth request to the third service entity, the second service entity needs to obtain the identification information of the first network slice instance.
- the second service entity obtains the identification information of the first network slice instance from the first service entity.
- S202 The third service entity searches for a VNF instance that has a corresponding relationship with the first network slice instance according to the correspondence between the identification information of the first network slice instance and the stored identification information of multiple network slice instances and the identification information of the VNF instance. Identification information.
- S202 For specific implementation steps of S202, reference may be made to the foregoing description of the embodiment in FIG. 6, and details are not described herein again.
- the second service entity receives a fourth response from the third service entity.
- the fourth response carries identification information of the VNF instance.
- the second service entity generates and stores an alarm filtering list according to the identification information of the VNF instance, the alarm filtering list has a corresponding relationship with the first network slice instance, and according to the alarm filtering list and the identifier of the first network slice instance The information generates and stores a first correspondence relationship.
- the first correspondence is a correspondence between the alarm filtering list and the first network slice instance.
- the first service entity may further associate the virtual resource alarm carried in the first response with the first network slice instance.
- the following uses the first service entity to send the identification information of the VNF instance to the second service entity through the alarm filtering list as an example to describe the first service entity's association of the virtual resource alarm to the first network slice instance.
- the first service entity associates the virtual resource alarm to a pre-stored, including, based on the identification information of the VNF instance carried in the virtual resource alarm.
- An alarm filter list of the identification information of the VNF instance and according to a first correspondence relationship stored in advance, a virtual resource alarm is associated with a first network slice instance having a correspondence relationship with the alarm filter list, and the first correspondence relationship is an alarm filter list Correspondence with the first network slice instance.
- the virtual resource alarm may be associated with the first network slice instance at the first service entity, and of course, the virtual resource alarm may be associated with the first network slice instance at the second service entity.
- the second service entity after the second service entity receives the first request from the first service entity, according to the identification information of the VNF instance carried in the alarm filtering list, the second service entity will carry the virtual information of the identification information of the VNF instance.
- the resource alarm is associated with an alarm filtering list including identification information of the VNF instance, and the virtual resource alarm is associated with a first network slice instance having a corresponding relationship with the alarm filtering list according to a first correspondence.
- the second service entity after the second service entity associates the virtual resource alarm with the first network slice instance, it may further send all or part of the virtual resource alarm associated with the first network slice instance to the first service entity, and the second service The entity may actively send a virtual resource alarm associated with the first network slice instance to the first service entity.
- the entity after receiving a request from the first service entity, the entity may also send an alert associated with the first network slice instance to the first service entity. Virtual resource alarm.
- the second service entity receives a fifth request from the first service entity, the fifth request carries identification information of the first network slice instance, and the fifth request is used to request a virtual connection to the first network slice instance.
- the second service entity sends a fifth response to the first service entity, and the fifth response carries the alarm information of the virtual resource alarm associated with the first network slice instance.
- the alarm filtering list carries the identification information of the VNF instance and the identification information of the VNFC instance
- the first service entity requests the identification information of the VNF instance and the identification information of the VNFC instance from the third service entity.
- a flowchart of another alarm method provided for this application includes the following steps:
- the first service entity sends a sixth request to the third service entity.
- the sixth request carries the identification information of the first network slice instance, and the sixth request is used to request the identification information of the VNF instance and the identification information of the VNFC instance that have a corresponding relationship with the first network slice instance, and the VNFC instance is the VNF
- the VNFC instance included in the instance belongs to the first network slice instance.
- the VNF instance having a corresponding relationship with the first network slice instance refers to a VNF instance in which a network function instance included in the first network slice instance is deployed.
- S302 After the third service entity receives the third request, according to the correspondence between the identification information of the first network slice instance and the identification information of multiple network slice instances that are stored in advance, and the identification information of the VNF instance and the identification information of the VNFC instance. To find the identification information of the VNF instance and the identification information of the VNFC instance that have a corresponding relationship with the first network slice instance. For specific implementation steps of S302, reference may be made to the foregoing description of the embodiment in FIG. 6, and details are not described herein again.
- the first service entity receives a sixth response from the third service entity.
- the sixth response carries the identification information of the VNF instance and the identification information of the VNFC instance that have a corresponding relationship with the first network slice instance.
- S304 The first service entity generates an alarm filtering list according to the identification information of the VNF instance and the identification information of the VNFC instance, and generates a first correspondence relationship according to the alarm filtering list and the identification information of the first network slice instance.
- the first service entity sends a seventh request to the second service entity.
- the seventh request carries the alarm filtering list generated above.
- the seventh request may further carry the first correspondence generated above.
- the seventh request may further include identification information of the virtual machine deployed by the VNF instance or the VNFC instance and / or identification information of the VDU.
- identification information of the virtual machine and / or the identification information of the VDU may also be carried in the alarm filtering list.
- the second service entity receives at least one virtual resource alarm from the MANO network element.
- the at least one virtual resource alarm may carry identification information of the VNF instance, and may also carry identification information of the VNF instance and identification information of the VNFC instance.
- the second service entity carries the identification of the VNF instance in at least one virtual resource alarm from a MANO network element according to the identification information of the VNF instance and the identification information of the VNFC instance carried in the received alarm filtering list.
- Information and the virtual resource alarm of the identification information of the VNFC instance are associated with the alarm filtering list including the identification information of the VNF instance, and the virtual resource alarm is associated with the alarm according to the first correspondence. And filtering the first network slice instance with a corresponding relationship.
- S307 is an optional step.
- the virtual resource alarm may be associated with the network slice instance at the second service entity, or the virtual resource alarm may be associated with the network slice instance at the first service entity. If the second service entity executes S307, the seventh request in S305 includes the first correspondence.
- the second service entity sends a seventh response to the first service entity.
- the seventh response includes a virtual resource alarm carrying identification information of the VNF instance and identification information of the VNFC instance.
- the first service entity may further request the second service entity to send a virtual carrying identification information of all VNF instances included in the alarm filtering list. Resource alert.
- the first service entity sends an eighth request to the second service entity.
- the eighth request carries identification information of the first network slice instance.
- the eighth request is used to request a virtual resource alarm that carries the identification information of the VNF instance and the identification information of the VNFC instance included in the alarm filtering list.
- the eighth request may also carry the alarm filtering list and the first correspondence. If the second service entity has stored the alarm filtering list and the first correspondence relationship sent by the first service entity, the eighth request may only carry identification information of the first network slice instance.
- the second service entity searches for a stored alarm filtering list that has a corresponding relationship with the first network slice instance, and determines to carry the alarm filtering list according to the alarm filtering list.
- the virtual resource alarm of the identification information of the VNF instance and the identification information of the VNFC instance included in the alarm filtering list is not limited to the alarm filtering list.
- the first service entity receives an eighth response from the second service entity.
- the eighth response is a virtual resource alarm that carries the identification information of the VNF instance and the identification information of the VNFC instance.
- the alarm filtering list carries the identification information of the VNF instance and the identification information of the VNFC instance
- the second service entity requests the identification information of the VNF instance and the identification information of the VNFC instance from the third service entity.
- This method is also applicable to the scenario where the alarm filtering list only carries the identification information of the VNF instance, and is not limited to this.
- a flowchart of another alarm method provided for this application includes the following steps:
- the second service entity receives a ninth request from the first service entity.
- the ninth request includes identification information of the first network slice instance, and the ninth request is used to request a virtual resource alarm associated with the first network slice instance.
- the second service entity sends a tenth request to the third service entity.
- the tenth request carries identification information of the first network slice instance.
- the tenth request is used to request identification information of the VNF instance and VNFC identification information belonging to the first network slice instance, and the VNF instance is used to deploy the first network slice instance.
- Network function instance of the instance, the VNFC instance is a VNFC instance included in the VNF instance and belonging to the first network slice instance.
- the tenth request may also be used to request identification information of the VNF instance or a virtual machine deployed by the VNFC instance and / or identification information of a VDU.
- S401 and S402 are not performed in the order of execution. S401 may be executed first, or S402 may be executed first.
- S403 After the third service entity receives the tenth request, according to the correspondence between the identification information of the first network slice instance and the identification information of the multiple network slice instances stored in advance, and the identification information of the VNF instance and the identification information of the VNFC instance To find the identification information of the VNF instance and the identification information of the VNFC instance that have a corresponding relationship with the first network slice instance.
- S403 For specific execution steps of S403, refer to the foregoing description of the embodiment in FIG. 6, and details are not described herein again.
- the second service entity receives a tenth response from the third service entity.
- the tenth response carries the identification information of the VNF instance and the identification information of the VNFC instance that have a corresponding relationship with the first network slice instance.
- S405 The second service entity stores the identification information of the VNF instance and the identification information of the VNFC instance. S405 is an optional step.
- the second service entity sends a ninth response to the first service entity.
- the ninth response may carry a subscription result.
- the subscription result may include a successful subscription or a failed subscription.
- the successful subscription is used to instruct the second service entity to send the first service entity to the first service entity after receiving the virtual resource alarm associated with the first network slice instance.
- the virtual resource alarm is described above.
- the subscription failure is used to indicate that the request of the first service entity fails, and it can carry information such as the cause of the failure.
- the second service entity receives at least one virtual resource alarm from the MANO network element.
- the at least one virtual resource alarm may carry identification information of the VNF instance, and may also carry identification information of the VNF instance and identification information of the VNFC instance.
- the second service entity determines, in at least one virtual resource alarm received from the MANO network element, a virtual resource alarm that carries the identification information of the VNF instance and the identification information of the VNFC instance included in the tenth response, and will carry the The virtual resource alarm of the identification information of the VNF instance is associated with the first network slice instance.
- the second service entity sends a ninth response to the first service entity.
- the ninth response includes a virtual resource alarm associated with the first network slice instance.
- the first service entity sends an eleventh request to the second service entity.
- the eleventh request carries identification information of the first network slice instance.
- the eleventh request is used to request a virtual resource alarm associated with the first network slice instance.
- the first service entity receives an eleventh response from the second service entity.
- the eleventh response carries a virtual resource alarm associated with the first network slice instance.
- the second service entity may further perform S402 to S405 multiple times in advance to obtain the identification information of the VNF instance and the identification information of the VNFC instance for all known network slice instances one by one.
- the second service entity receives the ninth request sent by the first service entity, the second service entity confirms that the identification information of the VNF instance and the identification information of the VNFC instance of the first network slice instance correspondence have been stored, and directly returns to S406 or The ninth response of S406a.
- the foregoing network elements include hardware structures and / or software modules corresponding to performing the functions.
- the foregoing network elements include hardware structures and / or software modules corresponding to performing the functions.
- this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is performed by hardware or computer software-driven hardware depends on the specific application and design constraints of the technical solution. A professional technician can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
- FIG. 12 shows a possible exemplary block diagram of a device involved in the embodiment of the present application.
- the device 1200 may exist in the form of software, or may be a first service entity or a first service entity.
- the second service entity or the third service entity may also be a chip in the first service entity or a chip in the second service entity or a chip in the third service entity.
- the device 1200 includes a processing unit 1202 and a transceiving unit 1203.
- the processing unit 1202 is configured to control and manage the actions of the device 1200. For example, when the device 1200 is a first service entity, the processing unit 1202 is configured to perform association of a virtual resource alarm to a first network slice instance, and S304 in FIG. 10, etc. Technical process.
- the processing unit 1202 is configured to execute the technical processes such as S102 in FIG. 4, S203 in FIG. 9, S307 in FIG. 10, and S405 and S408 in FIG. 11.
- the processing unit 1202 is configured to execute technical processes such as S302 in FIG. 10 and S403 in FIG. 11.
- the transceiver unit 1203 is configured to support communication between the device 1200 and other network entities.
- the transceiver unit 1203 may be used to support the device 1200 to execute S101 and S103 in FIG. 4, S301, S303, S305, S308, S309, and S310 in FIG.
- the transceiver unit 1203 can be used to support the device 1200 to execute S101 and S103 in FIG. 4, S201 and S202 in FIG. 9, S305, S306, S308, S309, and S310 in FIG. 10, and S401 in FIG. 11. , S402, S404, S406, S406a, S407, S409 and S410.
- the transceiver unit 1203 may be used to support the device 1200 to perform technical processes such as S201 and S202 in FIG. 9, S301 and S303 in FIG. 10, and S402 and S404 in FIG. 11.
- the device 1200 may further include a storage unit 1201 for storing program code and data of the device 1200.
- the processing unit 1202 may be a processor or a controller.
- the processing unit 1202 may be a general-purpose central processing unit (CPU), a general-purpose processor, digital signal processing (DSP), or an application-specific integrated circuit. circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the disclosure of this application.
- the processor may also be a combination that realizes computing functions, for example, a combination including one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
- the transceiver unit 1203 may be a communication interface, a transceiver, or a transceiver circuit.
- the storage unit 1201 may be a memory.
- the processing unit 1202 is a processor
- the transceiver unit 1203 is a transceiver
- the storage unit 1201 is a memory
- the device 1200 involved in this embodiment of the present application may be the device shown in FIG. 13.
- FIG. 13 is a schematic diagram of a possible logical structure of a device involved in the foregoing embodiment provided by an embodiment of the present application.
- the apparatus 1300 may include at least one processor 1301.
- the processor 1301 is configured to control and manage the action of the device.
- the device may further include a memory 1302 and a transceiver 1303.
- the processor 1301, the transceiver 1303, and the memory 1302 may be connected to each other or to each other through a bus 1304.
- the memory 1302 is configured to store code and data of the device.
- the transceiver 1303 is used to support the device for communication.
- the processor 1301 is a control center of the device, and may be a processor or a collective name of multiple processing elements.
- the processor 1301 is a CPU, and may also be implemented in an ASIC manner, or configured to implement one or more integrated circuits in the embodiments of the present application, for example, one or more DSPs, or one or more FPGA.
- the processor 1301 may execute various functions of the device 1300 by running or executing a software program stored in the memory 1302 and calling data stored in the memory 1302.
- the memory 1302 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (random access memory, RAM), or other types that can store information and instructions
- the dynamic storage device can also be Electrically Erasable Programmable Read-Only Memory (EEPROM), Compact Disc (Read-Only Memory, CD-ROM) or other optical disk storage, optical disk storage (Including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be used by a computer Any other media accessed, but not limited to this.
- the memory 1302 may exist independently, and is connected to the processor 1301 through a communication bus 1304.
- the memory 1302 may also be integrated with the processor 1301.
- the transceiver 1303 uses any device such as a transceiver for communication with other nodes, such as a first network element. It can also be used to communicate with communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), and so on.
- the transceiver 1203 may include a receiving unit to implement a receiving function, and a transmitting unit to implement a transmitting function.
- the communication bus 1304 may be an Industry Standard Architecture (ISA) bus, an External Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus.
- ISA Industry Standard Architecture
- PCI External Component Interconnect
- EISA Extended Industry Standard Architecture
- the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used in FIG. 13, but it does not mean that there is only one bus or one type of bus.
- the device structure shown in FIG. 13 does not constitute a limitation on the device, and may include more or fewer parts than shown, or some parts may be combined, or different parts may be arranged.
- An embodiment of the present application further provides a computer storage medium for storing computer software instructions used by the apparatus shown in FIG. 12 and FIG. 13, which includes program code designed to execute the foregoing method embodiments.
- the above method can be implemented by executing stored program code.
- the embodiments of the present application also provide a computer program product.
- the computer program product includes computer software instructions, and the computer software instructions can be loaded by a processor to implement the method in the foregoing method embodiment.
- An embodiment of the present application further provides a chip, which includes a processor and a transceiver component, and optionally a storage unit, which can be used to execute the method in the foregoing embodiment of the application.
- the computer program product includes one or more computer instructions.
- the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
- the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be from a website site, a computer, a server, or a data center.
- the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, or the like that includes one or more available medium integration.
- the available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (Solid State Disk, SSD)), and the like.
- Various illustrative logic units and circuits described in the embodiments of the present application may be implemented by a general-purpose processor, a digital signal processor, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices. Discrete gate or transistor logic, discrete hardware components, or any combination of the above are designed to implement or operate the described functions.
- the general-purpose processor may be a microprocessor. Alternatively, the general-purpose processor may also be any conventional processor, controller, microcontroller, or state machine.
- the processor may also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration. achieve.
- a software unit may be stored in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium in the art.
- the storage medium may be connected to the processor, so that the processor can read information from the storage medium and can write information to the storage medium.
- the storage medium may be integral to the processor.
- the processor and the storage medium may be provided in an ASIC, and the ASIC may be provided in a terminal device. Alternatively, the processor and the storage medium may also be provided in different components in the terminal device.
- These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of steps can be performed on the computer or other programmable device to produce a computer-implemented process, which can be executed on the computer or other programmable device.
- the instructions provide steps for implementing the functions specified in one or more flowcharts and / or one or more blocks of the block diagrams.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (45)
- 一种告警的方法,其特征在于,包括:第一服务实体向第二服务实体发送第一请求,所述第一服务实体用于管理网络切片实例,所述第二服务实体用于管理网络功能实例的告警;其中,所述第一请求中包括虚拟网络功能VNF实例的标识信息,所述第一请求用于请求携带所述标识信息的虚拟资源告警,所述VNF实例与所述第一服务实体管理的第一网络切片实例具有对应关系;所述第一服务实体接收来自所述第二服务实体的第一响应,所述第一响应中携带所述虚拟资源告警。
- 如权利要求1所述的方法,其特征在于,所述VNF实例的标识信息携带在所述第一请求包括的告警过滤列表中,所述告警过滤列表与所述第一网络切片实例具有对应关系;所述第一服务实体接收到来自所述第二服务实体的第一响应之后,还包括:所述第一服务实体根据所述虚拟资源告警中携带的所述VNF实例的标识信息,将所述虚拟资源告警关联到预先存储的、包括所述VNF实例的标识信息的所述告警过滤列表,并根据预先存储的第一对应关系,将所述虚拟资源告警关联到与所述告警过滤列表具有对应关系的所述第一网络切片实例,所述第一对应关系为所述告警过滤列表与所述第一网络切片实例的对应关系。
- 如权利要求2所述的方法,其特征在于,所述第一请求中还包括所述第一对应关系;所述第一服务实体向第二服务实体发送第一请求之后,还包括:所述第一服务实体向所述第二服务实体发送第二请求,其中,所述第二请求中携带所述第一网络切片实例的标识信息,所述第二请求用于请求携带所述告警过滤列表中包括的所述VNF实例的标识信息的虚拟资源告警,以使所述第二服务实体根据所述第一网络切片实例的标识信息以及所述第一对应关系,查找与所述第一网络切片实例具有对应关系的所述告警过滤列表,并根据所述告警过滤列表,确定携带所述告警过滤列表中包括的所述VNF实例的标识信息的虚拟资源告警;所述第一服务实体接收来自所述第二服务实体的第二响应,所述第二响应中携带所述虚拟资源告警。
- 如权利要求1至3任一项所述的方法,其特征在于,所述第一请求中还包括虚拟网络功能组件VNFC实例的标识信息,所述VNFC实例为所述VNF实例中包括的属于所述第一网络切片实例的VNFC实例,所述第一请求用于请求携带所述VNF实例的标识信息和所述VNFC实例的标识信息的虚拟资源告警。
- 如权利要求4所述的方法,其特征在于,所述第一服务实体向第二服务实体发送第一请求之前,还包括:所述第一服务实体向第三服务实体发送第三请求,所述第三请求中携带所述第一网络切片实例的标识信息,所述第三请求用于请求与所述第一网络切片实例具有对应关系的所述VNF实例的标识信息;所述第一服务实体接收来自所述第三服务实体的第三响应,所述第三响应中携带所述VNF实例的标识信息,所述VNF实例为部署所述第一网络切片实例包括的网络功能实例的VNF实例;所述第一服务实体根据所述VNF实例的标识信息生成所述告警过滤列表,并根据所述告警过滤列表以及所述第一网络切片实例的标识信息生成所述第一对应关系。
- 如权利要求5所述的方法,其特征在于,所述VNFC实例的标识信息携带在所述告警过滤列表中,所述第三请求还用于请求所述VNF实例中包括的属于所述第一网络切片实例的VNFC实例的标识信息,所述第三响应中还携带所述VNFC实例的标识信息;所述第一服务实体根据所述VNF实例的标识信息和所述VNFC实例的标识信息生成所述告警过滤列表,并根据所述告警过滤列表以及所述第一网络切片实例的标识信息生成所述第一对应关系。
- 一种告警的方法,其特征在于,包括:第二服务实体接收来自第一服务实体的第一请求,所述第一服务实体用于管理网络切片实例,所述第二服务实体用于管理网络功能实例的告警;其中,所述第一请求中包括所述第一服务实体管理的第一网络切片实例包含的虚拟网络功能VNF实例的标识信息,所述第一请求用于请求携带所述标识信息的虚拟资源告警;所述第二服务实体在从管理和编排MANO网元接收到的至少一个虚拟资源告警中,确定携带所述VNF实例的标识信息的虚拟资源告警;所述第二服务实体向所述第一服务实体发送第一响应,所述第一响应中包括携带所述VNF实例的标识信息的虚拟资源告警。
- 如权利要求7所述的方法,其特征在于,所述VNF实例的标识信息携带在所述第一请求包括的告警过滤列表中,所述告警过滤列表与所述第一网络切片实例具有对应关系,所述第一请求中还包括第一对应关系,所述第一对应关系为所述告警过滤列表与所述第一网络切片实例的对应关系;所述第二服务实体接收来自第一服务实体的第一请求之后,还包括:所述第二服务实体存储所述告警过滤列表和所述第一对应关系。
- 如权利要求8所述的方法,其特征在于,所述第二服务实体存储所述告警过滤列表和所述第一对应关系之后,还包括:所述第二服务实体根据所述告警过滤列表中携带的所述VNF实例的标识信息,将携带所述VNF实例的标识信息的虚拟资源告警,关联到包括所述VNF实例的标识信息的所述告警过滤列表,并根据所述第一对应关系,将所述虚拟资源告警关联到与所述告警过滤列表具有对应关系的所述第一网络切片实例。
- 如权利要求9所述的方法,其特征在于,所述第二服务实体接收来自第一服务实体的第一请求之后,还包括:所述第二服务实体接收来自所述第一服务实体的第二请求,所述第二请求中携带所述第一网络切片实例的标识信息,所述第二请求用于请求关联到所述第一网络切片实例的虚拟资源告警;所述第二服务实体向所述第一服务实体发送第二响应,所述第二响应中携带所述关联到所述第一网络切片实例的虚拟资源告警。
- 如权利要求7至10任一项所述的方法,其特征在于,所述第一请求中还包括虚拟网络功能组件VNFC实例的标识信息,所述VNFC实例为所述VNF实例中包括的属于所述第一网络切片实例的VNFC实例,所述第一请求用于请求携带所述VNF实例的标识信息和所述VNFC实例的标识信息的虚拟资源告警。
- 一种告警的方法,其特征在于,包括:第二服务实体接收来自第一服务实体的第一请求,所述第一服务实体用于管理网络切片实例,所述第二服务实体用于管理网络功能实例的告警;其中,所述第一请求中包括所述第一服务实体管理的第一网络切片实例的标识信息,所述第一请求用于请求和所述第一网络切片实例关联的虚拟资源告警;所述第二服务实体向第三服务实体发送第二请求,所述第三服务实体用于管理网络功能实例,所述第二请求中携带所述第一网络切片实例的标识信息,所述第二请求用于请求属于所述第一网络切片实例的VNF实例的标识信息,所述VNF实例用于部署属于所述第一网络切片实例的网络功能实例;所述第二服务实体接收来自所述第三服务实体的第二响应,所述第二响应中携带所述VNF实例的标识信息;所述第二服务实体在从管理和编排MANO网元接收到的至少一个虚拟资源告警中,确定携带所述VNF实例的标识信息的虚拟资源告警,并将所述携带所述VNF实例的标识信息的虚拟资源告警和所述第一网络切片实例关联;所述第二服务实体向所述第一服务实体发送第一响应,所述第一响应中包括与所述第一网络切片实例关联的虚拟资源告警。
- 如权利要求12所述的方法,其特征在于,所述第二请求还用于请求VNFC实例的标识信息,所述VNFC实例为所述VNF实例中包括的属于所述第一网络切片实例的VNFC实例,所述第二响应中还携带所述VNFC实例的标识信息;所述第二服务实体在从MANO网元接收到的至少一个虚拟资源告警中,确定携带所述VNF实例的标识信息和所述VNFC实例的标识信息的虚拟资源告警,并将所述携带所述VNF实例的标识信息和所述VNFC实例的标识信息的虚拟资源告警与所述第一网络切片实例关联。
- 如权利要求13所述的方法,其特征在于,所述第二请求中还携带第一网络功能实例的标识信息,所述第一网络功能实例为所述第一网络切片实例包括的其中一个网络功能实例,所述VNF实例用于部署所述第一网络功能实例,所述VNFC实例为所述VNF实例中包括的属于所述第一网络功能实例的VNFC实例。
- 如权利要求13或14所述的方法,其特征在于,所述第二服务实体接收来自所述第三服务实体的第二响应之后,还包括:所述第二服务实体根据所述第二响应中携带的所述VNF实例的标识信息和所述VNFC实例的标识信息生成并存储告警过滤列表,所述告警过滤列表中包括所述VNF实例的标识信息和所述VNFC实例的标识信息,并根据所述告警过滤列表以及所述第一网络切片实例的标识信息生成并存储第一对应关系,所述第一对应关系为所述告警过滤列表与所述第一网络切片实例的对应关系;所述第二服务实体在从MANO网元接收到的至少一个虚拟资源告警中,确定携带所述告警过滤列表中包括的所述VNF实例的标识信息和所述VNFC实例的标识信息的虚拟资源告警,并根据所述第一对应关系,将携带所述VNF实例的标识信息和所述VNFC实例的标识信息的虚拟资源告警以及所述第一网络切片实例关联。
- 一种告警的装置,其特征在于,包括收发单元、存储单元和处理单元;所述存储单元,存储有计算机程序;所述处理单元,用于调用所述存储单元中存储的计算机程序执行:控制所述收发单元向第二服务实体发送第一请求,所述装置用于管理网络切片实例,所述第二服务实体用于管理网络功能实例的告警;其中,所述第一请求中包括虚拟网络功能VNF实例的标识信息,所述第一请求用于请求携带所述标识信息的虚拟资源告警,所述VNF实例与所述装置管理的第一网络切片实例具有对应关系;接收来自所述第二服务实体的第一响应,所述第一响应中携带所述虚拟资源告警。
- 如权利要求16所述的装置,其特征在于,所述VNF实例的标识信息携带在所述第一请求包括的告警过滤列表中,所述告警过滤列表与所述第一网络切片实例具有对应关系;所述处理单元还用于:根据所述虚拟资源告警中携带的所述VNF实例的标识信息,将所述虚拟资源告警关联到预先存储的、包括所述VNF实例的标识信息的所述告警过滤列表,并根据预先存储的第一对应关系,将所述虚拟资源告警关联到与所述告警过滤列表具有对应关系的所述第一网络切片实例,所述第一对应关系为所述告警过滤列表与所述第一网络切片实例的对应关系。
- 如权利要求17所述的装置,其特征在于,所述第一请求中还包括所述第一对应关系;所述处理单元,还用于控制所述收发单元:向所述第二服务实体发送第二请求,其中,所述第二请求中携带所述第一网络切片实例的标识信息,所述第二请求用于请求携带所述告警过滤列表中包括的所述VNF实例的标识信息的虚拟资源告警,以使所述第二服务实体根据所述第一网络切片实例的标识信息以及所述第一对应关系,查找与所述第一网络切片实例具有对应关系的所述告警过滤列表,并根据所述告警过滤列表,确定携带所述告警过滤列表中包括的所述VNF实例的标识信息的虚拟资源告警;接收来自所述第二服务实体的第二响应,所述第二响应中携带所述虚拟资源告警。
- 如权利要求16至18任一项所述的装置,其特征在于,所述第一请求中还包括虚拟网络功能组件VNFC实例的标识信息,所述VNFC实例为所述VNF实例中包括的属于所述第一网络切片实例的VNFC实例,所述第一请求用于请求携带所述VNF实例的标识信息和所述VNFC实例的标识信息的虚拟资源告警。
- 如权利要求19所述的装置,其特征在于,所述处理单元,还用于控制所述收发单元:向第三服务实体发送第三请求,所述第三请求中携带所述第一网络切片实例的标识信息,所述第三请求用于请求与所述第一网络切片实例具有对应关系的所述VNF实例的标识信息;接收来自所述第三服务实体的第三响应,所述第三响应中携带所述VNF实例的标识信息,所述VNF实例为部署所述第一网络切片实例包括的网络功能实例的VNF实例;所述处理单元,还用于根据所述VNF实例的标识信息生成所述告警过滤列表,并根据所述告警过滤列表以及所述第一网络切片实例的标识信息生成所述第一对应关系。
- 如权利要求20所述的装置,其特征在于,所述VNFC实例的标识信息携带在所述告警过滤列表中,所述第三请求还用于请求所述VNF实例中包括的属于所述第一网络切片实例的VNFC实例的标识信息,所述第三响应中还携带所述VNFC实例的标识信息;所述处理单元,还用于根据所述VNF实例的标识信息和所述VNFC实例的标识信息生成所述告警过滤列表,并根据所述告警过滤列表以及所述第一网络切片实例的标识信息生成所述第一对应关系。
- 一种告警的装置,其特征在于,包括收发单元、存储单元和处理单元;所述存储单元,存储有计算机程序;所述处理单元,用于调用所述存储单元中存储的计算机程序执行:控制所述收发单元接收来自第一服务实体的第一请求,所述第一服务实体用于管理网络切片实例,所述装置用于管理网络功能实例的告警;其中,所述第一请求中包括所述第一服务实体管理的第一网络切片实例包含的虚拟网络功能VNF实例的标识信息,所述第一请求用于请求携带所述标识信息的虚拟资源告警,在从管理和编排MANO网元接收到的至少一个虚拟资源告警中,确定携带所述VNF实例的标识信息的虚拟资源告警,向所述第一服务实体发送第一响应,所述第一响应中包括携带所述VNF实例的标识信息的虚拟资源告警。
- 如权利要求22所述的装置,其特征在于,所述VNF实例的标识信息携带在所述第一请求包括的告警过滤列表中,所述告警过滤列表与所述第一网络切片实例具有对应关系,所述第一请求中还包括第一对应关系,所述第一对应关系为所述告警过滤列表与所述第一网络切片实例的对应关系;所述存储单元,还用于存储所述告警过滤列表和所述第一对应关系。
- 如权利要求23所述的装置,其特征在于,所述处理单元还用于:根据所述告警过滤列表中携带的所述VNF实例的标识信息,将携带所述VNF实例的标识信息的虚拟资源告警,关联到包括所述VNF实例的标识信息的所述告警过滤列表,并根据所述第一对应关系,将所述虚拟资源告警关联到与所述告警过滤列表具有对应关系的所述第一网络切片实例。
- 如权利要求24所述的装置,其特征在于,所述处理单元,还用于控制所述收发单元:接收来自所述第一服务实体的第二请求,所述第二请求中携带所述第一网络切片实例的标识信息,所述第二请求用于请求关联到所述第一网络切片实例的虚拟资源告警;向所述第一服务实体发送第二响应,所述第二响应中携带所述关联到所述第一网络切片实例的虚拟资源告警。
- 如权利要求22至25任一项所述的装置,其特征在于,所述第一请求中还包括虚拟网络功能组件VNFC实例的标识信息,所述VNFC实例为所述VNF实例中包括的属于所述第一网络切片实例的VNFC实例,所述第一请求用于请求携带所述VNF实例的标识信息和所述VNFC实例的标识信息的虚拟资源告警。
- 一种告警的装置,其特征在于,包括收发单元、存储单元和处理单元;所述存储单元,存储有计算机程序;所述处理单元,用于调用所述存储单元中存储的计算机程序执行:控制所述收发单元接收来自第一服务实体的第一请求,所述第一服务实体用于管理网络切片实例,所述装置用于管理网络功能实例的告警,其中,所述第一请求中包括所述第一服务实体管理的第一网络切片实例的标识信息,所述第一请求用于请求和所述第一网络切片实例关联的虚拟资源告警;控制所述收发单元向第三服务实体发送第二请求,所述第三服务实体用于管理网络功能实例,所述第二请求中携带所述第一网络切片实例的标识信息,所述第二请求用于请求属于所述第一网络切片实例的VNF实例的标识信息,所述VNF实例用于部署属于所述第一网络切片实例的网络功能实例;控制所述收发单元接收来自所述第三服务实体的第二响应,所述第二响应中携带所述VNF实例的标识信息;在从管理和编排MANO网元接收到的至少一个虚拟资源告警中,确定携带所述VNF实例的标识信息的虚拟资源告警,并将所述携带所述VNF实例的标识信息的虚拟资源告警和所述第一网络切片实例关联;控制所述收发单元向所述第一服务实体发送第一响应,所述第一响应中包括与所述第一网络切片实例关联的虚拟资源告警。
- 如权利要求27所述的装置,其特征在于,所述第二请求还用于请求VNFC实例的标识信息,所述VNFC实例为所述VNF实例中包括的属于所述第一网络切片实例的VNFC实例,所述第二响应中还携带所述VNFC实例的标识信息;所述处理单元还用于:在从MANO网元接收到的至少一个虚拟资源告警中,确定携带所述VNF实例的标识信息和所述VNFC实例的标识信息的虚拟资源告警,并将所述携带所述VNF实例的标识信息和所述VNFC实例的标识信息的虚拟资源告警与所述第一网络切片实例关联。
- 如权利要求28所述的装置,其特征在于,所述第二请求中还携带第一网络功能实例的标识信息,所述第一网络功能实例为所述第一网络切片实例包括的其中一个网络功能实例,所述VNF实例用于部署所述第一网络功能实例,所述VNFC实例为所述VNF实例中包括的属于所述第一网络功能实例的VNFC实例。
- 如权利要求28或29所述的装置,其特征在于,所述处理单元还用于:根据所述第二响应中携带的所述VNF实例的标识信息和所述VNFC实例的标识信息生成并存储告警过滤列表,所述告警过滤列表中包括所述VNF实例的标识信息和所述VNFC实例的标识信息,并根据所述告警过滤列表以及所述第一网络切片实例的标识信息生成并存储第一对应关系,所述第一对应关系为所述告警过滤列表与所述第一网络切片实例的对应关系;在从MANO网元接收到的至少一个虚拟资源告警中,确定携带所述告警过滤列表中包括的所述VNF实例的标识信息和所述VNFC实例的标识信息的虚拟资源告警,并根据所述第一对应关系,将携带所述VNF实例的标识信息和所述VNFC实例的标识信息的虚拟资源告警以及所述第一网络切片实例关联。
- 一种告警的方法,其特征在于,包括:第一服务实体向第二服务实体发送第一请求,所述第一服务实体用于管理网络切片实例,所述第二服务实体用于管理网络功能实例的告警;其中,所述第一请求中包括虚拟网络功能VNF实例的标识信息,所述第一请求用于请求携带所述标识信息的虚拟资源告警,所述VNF实例与所述第一服务实体管理的第一网络切片实例具有对应关系;所述第二服务实体接收所述第一请求;所述第二服务实体根据所述第一请求,在从管理和编排MANO网元接收到的至少一个虚拟资源告警中,确定携带所述VNF实例的标识信息的虚拟资源告警;所述第二服务实体向所述第一服务实体发送第一响应,所述第一响应中包括携带所述VNF实例的标识信息的虚拟资源告警。
- 如权利要求31所述的方法,其特征在于,所述VNF实例的标识信息携带在所述第一请求包括的告警过滤列表中,所述告警过滤列表与所述第一网络切片实例具有对应关系;所述第一服务实体接收到所述第一响应之后,还包括:所述第一服务实体根据所述虚拟资源告警中携带的所述VNF实例的标识信息,将所述虚拟资源告警关联到预先存储的、包括所述VNF实例的标识信息的所述告警过滤列表,并根据预先存储的第一对应关系,将所述虚拟资源告警关联到与所述告警过滤列表具有对应关系的所述第一网络切片实例,所述第一对应关系为所述告警过滤列表与所述第一网络切片实例的对应关系。
- 如权利要求32所述的方法,其特征在于,所述第一请求中还包括所述第一对应关系;所述第一服务实体向第二服务实体发送所述第一请求之后,还包括:所述第一服务实体向所述第二服务实体发送第二请求,其中,所述第二请求中携带所述第一网络切片实例的标识信息,所述第二请求用于请求携带所述告警过滤列表中包括的所述VNF实例的标识信息的虚拟资源告警;所述第二服务实体根据所述第一网络切片实例的标识信息以及所述第一对应关系,查找与所述第一网络切片实例具有对应关系的所述告警过滤列表,并根据所述告警过滤列表,确定携带所述告警过滤列表中包括的所述VNF实例的标识信息的虚拟资源告警;所述第二服务实体向所述第一服务实体发送第二响应,所述第二响应中携带所述虚拟资源告警。
- 如权利要求31至33任一项所述的方法,其特征在于,所述第一请求中还包括虚拟网络功能组件VNFC实例的标识信息,所述VNFC实例为所述VNF实例中包括的属于所述第一网络切片实例的VNFC实例,所述第一请求用于请求携带所述VNF实例的标识信息和所述VNFC实例的标识信息的虚拟资源告警。
- 如权利要求34所述的方法,其特征在于,所述第一服务实体向第二服务实体发送第一请求之前,还包括:所述第一服务实体向第三服务实体发送第三请求,所述第三请求中携带所述第一网络切片实例的标识信息,所述第三请求用于请求与所述第一网络切片实例具有对应关系的所述VNF实例的标识信息;所述第三服务实体向所述第一服务实体发送第三响应,所述第三响应中携带所述VNF实例的标识信息,所述VNF实例为部署所述第一网络切片实例包括的网络功能实例的VNF实例;所述第一服务实体根据所述VNF实例的标识信息生成所述告警过滤列表,并根据所述告警过滤列表以及所述第一网络切片实例的标识信息生成所述第一对应关系。
- 如权利要求35所述的方法,其特征在于,所述VNFC实例的标识信息携带在所述告警过滤列表中,所述第三请求还用于请求所述VNF实例中包括的属于所述第一网络切片实例的VNFC实例的标识信息,所述第三响应中还携带所述VNFC实例的标识信息;所述第一服务实体根据所述VNF实例的标识信息和所述VNFC实例的标识信息生成所述告警过滤列表,并根据所述告警过滤列表以及所述第一网络切片实例的标识信息生成所述第一对应关系。
- 一种用于告警的***,其特征在于,包括:第一服务实体和第二服务实体;所述第一服务实体,用于向第二服务实体发送第一请求,所述第一服务实体用于管理网 络切片实例,所述第二服务实体用于管理网络功能实例的告警;其中,所述第一请求中包括虚拟网络功能VNF实例的标识信息,所述第一请求用于请求携带所述标识信息的虚拟资源告警,所述VNF实例与所述第一服务实体管理的第一网络切片实例具有对应关系;所述第二服务实体,用于接收所述第一请求;所述第二服务实体还用于根据所述第一请求,在从管理和编排MANO网元接收到的至少一个虚拟资源告警中,确定携带所述VNF实例的标识信息的虚拟资源告警;所述第二服务实体,还用于向所述第一服务实体发送第一响应,所述第一响应中包括携带所述VNF实例的标识信息的虚拟资源告警。
- 如权利要求37所述的***,其特征在于,所述VNF实例的标识信息携带在所述第一请求包括的告警过滤列表中,所述告警过滤列表与所述第一网络切片实例具有对应关系;所述第一服务实体,用于在接收到所述第一响应之后,根据所述虚拟资源告警中携带的所述VNF实例的标识信息,将所述虚拟资源告警关联到预先存储的、包括所述VNF实例的标识信息的所述告警过滤列表,并根据预先存储的第一对应关系,将所述虚拟资源告警关联到与所述告警过滤列表具有对应关系的所述第一网络切片实例,所述第一对应关系为所述告警过滤列表与所述第一网络切片实例的对应关系。
- 如权利要求38所述的***,其特征在于,所述第一请求中还包括所述第一对应关系;所述第一服务实体,还用于在向第二服务实体发送所述第一请求之后,向所述第二服务实体发送第二请求,其中,所述第二请求中携带所述第一网络切片实例的标识信息,所述第二请求用于请求携带所述告警过滤列表中包括的所述VNF实例的标识信息的虚拟资源告警;所述第二服务实体,还用于根据所述第一网络切片实例的标识信息以及所述第一对应关系,查找与所述第一网络切片实例具有对应关系的所述告警过滤列表,并根据所述告警过滤列表,确定携带所述告警过滤列表中包括的所述VNF实例的标识信息的虚拟资源告警;所述第二服务实体,还用于向所述第一服务实体发送第二响应,所述第二响应中携带所述虚拟资源告警。
- 如权利要求37至39任一项所述的***,其特征在于,所述第一请求中还包括虚拟网络功能组件VNFC实例的标识信息,所述VNFC实例为所述VNF实例中包括的属于所述第一网络切片实例的VNFC实例,所述第一请求用于请求携带所述VNF实例的标识信息和所述VNFC实例的标识信息的虚拟资源告警。
- 如权利要求40所述的***,其特征在于,还包括第三服务实体;所述第一服务实体,还用于在向第二服务实体发送第一请求之前,向第三服务实体发送第三请求,所述第三请求中携带所述第一网络切片实例的标识信息,所述第三请求用于请求与所述第一网络切片实例具有对应关系的所述VNF实例的标识信息;所述第三服务实体,用于向所述第一服务实体发送第三响应,所述第三响应中携带所述VNF实例的标识信息,所述VNF实例为部署所述第一网络切片实例包括的网络功能实例的VNF实例;所述第一服务实体,还用于根据所述VNF实例的标识信息生成所述告警过滤列表,并根据所述告警过滤列表以及所述第一网络切片实例的标识信息生成所述第一对应关系。
- 如权利要求41所述的***,其特征在于,所述VNFC实例的标识信息携带在所述告警过滤列表中,所述第三请求还用于请求所述VNF实例中包括的属于所述第一网络切片实 例的VNFC实例的标识信息,所述第三响应中还携带所述VNFC实例的标识信息;所述第一服务实体根据所述VNF实例的标识信息和所述VNFC实例的标识信息生成所述告警过滤列表,并根据所述告警过滤列表以及所述第一网络切片实例的标识信息生成所述第一对应关系。
- 一种计算机可读存储介质,包括指令,当其在计算机上运行时,使得计算机执行如权利要求1-15,或31-36任意一项所述的方法。
- 一种包含指令的计算机程序产品,当其在计算机上运行时,使得计算机执行如权利要求1-15,或31-36任意一项所述的方法。
- 一种装置,包括处理器和存储器;所述存储器用于存储计算机执行指令,所述处理器与所述存储器相连,当所述装置运行时,所述处理器执行所述存储器存储的计算机执行指令,以使所述装置执行如权利要求1-15,或31-36任意一项所述的方法。
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2020569909A JP7105930B2 (ja) | 2018-06-15 | 2019-06-10 | 警報方法および警報装置 |
KR1020217000763A KR102439559B1 (ko) | 2018-06-15 | 2019-06-10 | 경보 방법 및 디바이스 |
BR112020025410-0A BR112020025410A2 (pt) | 2018-06-15 | 2019-06-10 | Método e aparelho de alarme |
EP19818927.6A EP3800926B1 (en) | 2018-06-15 | 2019-06-10 | Alarm method and device |
US17/122,431 US20210099335A1 (en) | 2018-06-15 | 2020-12-15 | Alarm Method and Apparatus |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201810621708.7 | 2018-06-15 | ||
CN201810621708.7A CN110611926B (zh) | 2018-06-15 | 2018-06-15 | 一种告警的方法及装置 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/122,431 Continuation US20210099335A1 (en) | 2018-06-15 | 2020-12-15 | Alarm Method and Apparatus |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019238004A1 true WO2019238004A1 (zh) | 2019-12-19 |
Family
ID=68842699
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2019/090525 WO2019238004A1 (zh) | 2018-06-15 | 2019-06-10 | 一种告警的方法及装置 |
Country Status (7)
Country | Link |
---|---|
US (1) | US20210099335A1 (zh) |
EP (1) | EP3800926B1 (zh) |
JP (1) | JP7105930B2 (zh) |
KR (1) | KR102439559B1 (zh) |
CN (1) | CN110611926B (zh) |
BR (1) | BR112020025410A2 (zh) |
WO (1) | WO2019238004A1 (zh) |
Families Citing this family (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11240135B1 (en) * | 2018-05-23 | 2022-02-01 | Open Invention Network Llc | Monitoring VNFCs that are composed of independently manageable software modules |
US10812337B2 (en) | 2018-06-15 | 2020-10-20 | Vmware, Inc. | Hierarchical API for a SDDC |
US10942788B2 (en) | 2018-06-15 | 2021-03-09 | Vmware, Inc. | Policy constraint framework for an sddc |
US11784884B2 (en) * | 2019-11-08 | 2023-10-10 | Telefonaktiebolaget Lm Ericsson (Publ) | Code activation management method for network slicing solutions, and corresponding entity, server and computer program |
CN115380514B (zh) | 2020-04-01 | 2024-03-01 | 威睿有限责任公司 | 为异构计算元件自动部署网络元件 |
CN113543180B (zh) * | 2020-04-15 | 2024-06-14 | 大唐移动通信设备有限公司 | 一种告警处理方法和装置 |
CN113973047B (zh) * | 2020-07-24 | 2024-04-09 | 中移(苏州)软件技术有限公司 | 一种信息显示方法、装置、设备及存储介质 |
US11803408B2 (en) | 2020-07-29 | 2023-10-31 | Vmware, Inc. | Distributed network plugin agents for container networking |
US11863352B2 (en) | 2020-07-30 | 2024-01-02 | Vmware, Inc. | Hierarchical networking for nested container clusters |
CN114071518A (zh) * | 2020-07-31 | 2022-02-18 | 中移(苏州)软件技术有限公司 | 一种信息处理方法、装置、设备及计算机存储介质 |
WO2022204941A1 (en) * | 2021-03-30 | 2022-10-06 | Vmware Information Technology (China) Co., Ltd. | Efficient trouble shooting on container network bycorrelating kubernetesresources and underlying resources |
US11880791B2 (en) * | 2021-08-27 | 2024-01-23 | Oracle International Corporation | Attachment and detachment of compute instances owned by different tenancies |
US11902245B2 (en) | 2022-01-14 | 2024-02-13 | VMware LLC | Per-namespace IP address management method for container networks |
US11848910B1 (en) | 2022-11-11 | 2023-12-19 | Vmware, Inc. | Assigning stateful pods fixed IP addresses depending on unique pod identity |
US11831511B1 (en) | 2023-01-17 | 2023-11-28 | Vmware, Inc. | Enforcing network policies in heterogeneous systems |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105847025A (zh) * | 2015-01-16 | 2016-08-10 | 中兴通讯股份有限公司 | 告警处理方法及装置 |
WO2017080517A1 (en) * | 2015-11-13 | 2017-05-18 | Huawei Technologies Co., Ltd. | Systems and methods for network slice management |
CN108024270A (zh) * | 2016-11-03 | 2018-05-11 | 华为技术有限公司 | 一种信息发送方法、单元和*** |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105337758A (zh) * | 2014-08-15 | 2016-02-17 | 中兴通讯股份有限公司 | 告警处理方法、装置、nms、oss及ems |
ES2876311T3 (es) * | 2014-09-29 | 2021-11-12 | Koninklijke Kpn Nv | Replicación de estado de instancias de función de red virtual |
CN107113195B (zh) * | 2015-06-01 | 2019-12-06 | 华为技术有限公司 | 用于控制平面和数据平面中的虚拟化功能的***和方法 |
US10536946B2 (en) * | 2015-12-08 | 2020-01-14 | Huawei Technologies Co., Ltd. | Method and system for performing network slicing in a radio access network |
US11509544B2 (en) * | 2016-07-15 | 2022-11-22 | Telefonaktiebolaget Lm Ericsson (Publ) | Determining a service level in a communication network |
CN109565446B (zh) * | 2016-08-31 | 2020-12-25 | 华为技术有限公司 | 一种告警信息上报方法及装置 |
CN106506201A (zh) * | 2016-10-31 | 2017-03-15 | 中国联合网络通信集团有限公司 | Vnf迁移方法、mano和*** |
CN108023749A (zh) * | 2016-11-03 | 2018-05-11 | 华为技术有限公司 | 管理网络切片的方法、设备和*** |
CN108024256B (zh) * | 2016-11-03 | 2020-04-03 | 华为技术有限公司 | 一种收缩网络切片实例的方法、装置和*** |
US10827366B2 (en) * | 2016-11-07 | 2020-11-03 | Huawei Technologies Co., Ltd. | System and methods for monitoring performance of slices |
EP3804224A1 (en) * | 2018-06-08 | 2021-04-14 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and network nodes for managing actions occurring in a network slice of a communication network |
-
2018
- 2018-06-15 CN CN201810621708.7A patent/CN110611926B/zh active Active
-
2019
- 2019-06-10 BR BR112020025410-0A patent/BR112020025410A2/pt unknown
- 2019-06-10 KR KR1020217000763A patent/KR102439559B1/ko active IP Right Grant
- 2019-06-10 WO PCT/CN2019/090525 patent/WO2019238004A1/zh unknown
- 2019-06-10 JP JP2020569909A patent/JP7105930B2/ja active Active
- 2019-06-10 EP EP19818927.6A patent/EP3800926B1/en active Active
-
2020
- 2020-12-15 US US17/122,431 patent/US20210099335A1/en active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105847025A (zh) * | 2015-01-16 | 2016-08-10 | 中兴通讯股份有限公司 | 告警处理方法及装置 |
WO2017080517A1 (en) * | 2015-11-13 | 2017-05-18 | Huawei Technologies Co., Ltd. | Systems and methods for network slice management |
CN108024270A (zh) * | 2016-11-03 | 2018-05-11 | 华为技术有限公司 | 一种信息发送方法、单元和*** |
Non-Patent Citations (2)
Title |
---|
HUAWEI: "28.545 Add Requirements for VNF Alarm Correlation", 3GPP TSG SA WG5 (TELECOM MANAGEMENT) MEETING #118, 13 April 2018 (2018-04-13), pages 5 - 182407, XP051433938 * |
See also references of EP3800926A4 |
Also Published As
Publication number | Publication date |
---|---|
JP7105930B2 (ja) | 2022-07-25 |
EP3800926A4 (en) | 2021-08-04 |
KR102439559B1 (ko) | 2022-09-05 |
CN110611926A (zh) | 2019-12-24 |
EP3800926A1 (en) | 2021-04-07 |
BR112020025410A2 (pt) | 2021-03-09 |
CN110611926B (zh) | 2021-06-01 |
EP3800926B1 (en) | 2023-06-07 |
JP2021526768A (ja) | 2021-10-07 |
KR20210020084A (ko) | 2021-02-23 |
US20210099335A1 (en) | 2021-04-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2019238004A1 (zh) | 一种告警的方法及装置 | |
EP3291499B1 (en) | Method and apparatus for network service capacity expansion | |
EP3455728B1 (en) | Orchestrator for a virtual network platform as a service (vnpaas) | |
US20210326167A1 (en) | Vnf service instantiation method and apparatus | |
US20190230004A1 (en) | Network slice management method and management unit | |
JP6834033B2 (ja) | ネットワークスライス管理方法、ユニット、及びシステム | |
JP6466003B2 (ja) | Vnfフェイルオーバの方法及び装置 | |
US10719348B2 (en) | Network function virtualization management and orchestration apparatus, method, and program | |
WO2018024059A1 (zh) | 一种虚拟化网络中业务部署的方法和装置 | |
US10924966B2 (en) | Management method, management unit, and system | |
US20190261186A1 (en) | Network Slice Management Method, Management Unit, and System | |
WO2019174000A1 (zh) | 用于业务管理的方法和装置 | |
US10848366B2 (en) | Network function management method, management unit, and system | |
WO2019179301A1 (zh) | 一种管理虚拟资源的方法及装置 | |
WO2017185251A1 (zh) | Vnfm的确定方法和网络功能虚拟化编排器 | |
CN109428764B (zh) | 虚拟网络功能的实例化方法 | |
US11301284B2 (en) | Method for managing VNF instantiation and device | |
EP4177742A1 (en) | Multitenancy management method and apparatus | |
WO2019228220A1 (zh) | 一种网络切片的管理方法及装置 | |
CN112889247B (zh) | Vnf服务实例化方法及装置 | |
CN113098705B (zh) | 网络业务的生命周期管理的授权方法及装置 | |
WO2022267995A1 (zh) | 通信方法、装置、相关设备及存储介质 | |
US20230105269A1 (en) | Virtualized network service deployment method and apparatus | |
CN110417568B (zh) | Nfv策略协商方法及*** | |
WO2018120227A1 (zh) | 一种资源管理方法及装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 19818927 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2020569909 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112020025410 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 20217000763 Country of ref document: KR Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2019818927 Country of ref document: EP Effective date: 20201228 |
|
ENP | Entry into the national phase |
Ref document number: 112020025410 Country of ref document: BR Kind code of ref document: A2 Effective date: 20201211 |