WO2016197395A1 - Procédé, dispositif et système de libération de connexion - Google Patents

Procédé, dispositif et système de libération de connexion Download PDF

Info

Publication number
WO2016197395A1
WO2016197395A1 PCT/CN2015/081398 CN2015081398W WO2016197395A1 WO 2016197395 A1 WO2016197395 A1 WO 2016197395A1 CN 2015081398 W CN2015081398 W CN 2015081398W WO 2016197395 A1 WO2016197395 A1 WO 2016197395A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
connection
release
vim
vnfm
Prior art date
Application number
PCT/CN2015/081398
Other languages
English (en)
Chinese (zh)
Inventor
季莉
周彦
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201580080506.0A priority Critical patent/CN107615872B/zh
Priority to PCT/CN2015/081398 priority patent/WO2016197395A1/fr
Publication of WO2016197395A1 publication Critical patent/WO2016197395A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method, device, and system for releasing a connection.
  • NFV network function virtualization
  • NFV network function virtualization scheduling node
  • NFVO network function virtualization orchestrator
  • VIM virtual machine infrastructure management node
  • VNFM Virtualized network function manager
  • VNF virtual network function management node
  • VNF virtualized network function manager
  • VNF virtualized network function
  • the VNFM needs to request the VIM specified by the NFVO to allocate resources for the VNF managed by the VNFM, if the connection between the VNFM and the VIM is not established, the VNFM needs to establish a connection with the VIM, so that the VIM is The VNF allocates resources.
  • the VNFM requesting the VIM specified by the NFVO to allocate resources for the VNF managed by the VNFM
  • the number of VIMs that can establish a connection with the VNFM is limited, the number of VIMs that have established a connection with the VNFM can be achieved. If the VNFM has not established a connection with the VIM specified by the NFVO, the VNFM cannot establish a connection with the NFVO because there is no free connection resource. The connection between the VIMs, such that the VNFM cannot request the VIM specified by the NFVO to allocate resources for the VNF.
  • the invention provides a method, device and system for releasing a connection, so that a node passes Reasonably release the established connection with other nodes to ensure that the node has free connection resources to establish a new connection.
  • the present invention provides a method of releasing a connection, comprising:
  • the first node determines, from the plurality of second nodes, a second node that allows the connection to be released, the plurality of second nodes being nodes that have established a connection with the first node;
  • the first node deletes information about the second node that is allowed to release the connection saved in the first node.
  • the first node determines, from the plurality of second nodes, the second node that is allowed to release the connection, including:
  • the first node receives a first connection release notification message sent by the management node, where the first connection release notification message carries the identifier of the second node that allows the release connection:
  • the method before the first node receives the first connection release notification message sent by the management node, the method further includes:
  • the first node sends a connection release request message to the management node, where the connection release request message is used to request the management node to determine the second node that is allowed to release the connection.
  • the first node is a virtual network function management node VNFM, and the plurality of second nodes are multiple virtual machine infrastructure management nodes VIM; or
  • the first node is a VIM
  • the plurality of second nodes are multiple VNFMs.
  • the first node is a VNFM
  • the multiple second nodes are multiple VIMs.
  • the second node that is allowed to release the connection is a VIM that has no resource management relationship with the VNFM among the multiple VIMs;
  • the second node that is allowed to release the connection is the first VIM that meets the first condition
  • the first condition is that the first VIM of the multiple VIMs allocates resources for the virtual network function VNF managed by the VNFM, and allows the VNF to be allocated by the other VIM of the multiple VIMs. .
  • the method After the first node determines, from the plurality of second nodes, the second node that is allowed to release the connection, the first node deletes the information of the second node that is allowed to release the connection saved in the first node, the method Also includes:
  • the first node sends a second connection release notification message to the second node that is allowed to release the connection, where the second connection release notification message carries the identifier of the first node, and the second connection release notification message is used by And notifying the second node that is allowed to release the connection, deleting the information of the first node indicated by the identifier of the first node saved in the second node that is allowed to release the connection.
  • the present invention provides a method of releasing a connection, comprising:
  • the management node determines, from the plurality of second nodes, a second node that allows the connection to be released, the plurality of second nodes being nodes that have established a connection with the first node;
  • the management node sends a first connection release notification message to the first node, where the first connection release notification message carries the identifier of the second node that allows the release connection, and the first connection release notification message is used for Notifying the first node, deleting information of the second node that is allowed to release the connection saved in the first node.
  • the second node that has no resource management relationship with the first node exists in the multiple second nodes, the second node that is allowed to release the connection is the first node and the first node The second node has no resource management relationship.
  • the method further includes:
  • connection release request message sent by the first node, where the connection release request message is used to request the management node to determine the second node that is allowed to release the connection;
  • the management node determines, from the plurality of second nodes, a second node that allows the connection to be released, including:
  • the management node determines, according to the connection release request message, the second node that is allowed to release the connection from the plurality of second nodes.
  • the first node is a VNFM, and the plurality of second nodes are multiple VIMs; or
  • the first node is a VIM
  • the plurality of second nodes are multiple VNFMs.
  • the first node is a VNFM
  • the multiple second nodes are multiple VIMs.
  • the second node that is allowed to release the connection is the first VIM that meets the first condition
  • the first condition is that the first VIM of the multiple VIMs allocates resources for the virtual network function VNF managed by the VNFM, and allows the VNF to be allocated by the other VIM of the multiple VIMs. .
  • the first node is a VIM
  • the multiple second nodes are multiple VNFMs.
  • the second node that is allowed to release the connection is the first VNFM that satisfies the second condition
  • the second condition is that the VIM allocates resources for the VNF managed by the first VNFM of the plurality of VNFMs, and is allowed to be built by the first VNFM. Another VIM of the connection is assigned to the VNF.
  • the method further includes:
  • the management node sends a second connection release notification message to the second node that is allowed to release the connection, where the second connection release notification message carries the identifier of the first node, and the second connection release notification message is used for Notifying the second node that is allowed to release the connection, and deleting the information of the first node indicated by the identifier of the first node saved in the second node that is allowed to release the connection.
  • the present invention provides an apparatus for releasing a connection, comprising:
  • a determining unit configured to determine, from the plurality of second nodes, a second node that allows the connection to be released, the plurality of second nodes being nodes that have established a connection with the first node;
  • a deleting unit configured to delete information about the second node that is allowed to release the connection determined by the determining unit saved in the first node.
  • the determining unit is configured to receive, by the management node, a first connection release notification message, where the first connection release notification message carries an identifier of the second node that is allowed to release the connection;
  • the determining unit is specifically configured to determine, according to the identifier of the second node that is allowed to release the connection, the second node that is allowed to release the connection.
  • the apparatus for releasing the connection further includes a sending unit
  • the sending unit is configured to send a connection release request message to the management node before the determining unit receives the first connection release notification message sent by the management node, where the connection release request message is used to request the management node to determine The second node that allows the connection to be released.
  • the first node is a VNFM, and the plurality of second nodes are multiple VIMs; or
  • the first node is a VIM
  • the plurality of second nodes are multiple VNFMs.
  • the first node is a VNFM
  • the multiple second nodes are multiple VIMs.
  • the second node that is determined to be released by the determining unit is that the VNFM has no resource management relationship among the multiple VIMs. VIM; or,
  • the second node that is determined to be released by the determining unit is the first VIM that meets the first condition
  • the first condition is that the first VIM of the multiple VIMs allocates resources for the VNF managed by the VNFM, and allows the VNF to be allocated by the other VIM of the multiple VIMs.
  • the sending unit is further configured to: after the determining unit determines, from the plurality of second nodes, the second node that is allowed to release the connection, the deleting unit deletes the first release of the allowed release connection saved in the first node Before the information of the two nodes, the second connection release notification message is sent to the second node that is allowed to release the connection, where the second connection release notification message carries the identifier of the first node, and the second connection release notification message And a second node for notifying the release of the connection, deleting the information of the first node indicated by the identifier of the first node saved in the second node that is allowed to release the connection.
  • the present invention provides a device for releasing a connection, comprising:
  • a determining unit configured to determine, from the plurality of second nodes, a second node that allows the connection to be released, the plurality of second nodes being nodes that have established a connection with the first node;
  • a sending unit configured to send a first connection release notification message to the first node, where the first connection release notification message carries the permission release determined by the determining unit An identifier of the connected second node, where the first connection release notification message is used to notify the first node to delete information about the second node that is allowed to release the connection saved in the first node.
  • the second node that has no resource management relationship with the first node exists in the multiple second nodes, the second node that is determined to be released by the determining unit is the plurality of second nodes. A second node having no resource management relationship with the first node.
  • the device for releasing the connection further includes a receiving unit
  • the receiving unit is configured to receive, after the determining unit determines, from the plurality of second nodes, the connection release request message sent by the first node, where the connection release request message is used, Requesting the determining unit to determine the second node that is allowed to release the connection;
  • the determining unit is specifically configured to determine, according to the connection release request message received by the receiving unit, a second node that is allowed to release the connection from the plurality of second nodes.
  • the first node is a VNFM, and the plurality of second nodes are multiple VIMs; or
  • the first node is a VIM
  • the plurality of second nodes are multiple VNFMs.
  • the first node is a VNFM
  • the multiple second nodes are multiple VIMs.
  • the second node that is determined to be released by the determining unit is the first VIM that meets the first condition
  • the first condition is that the first VIM of the multiple VIMs allocates resources for the VNF managed by the VNFM, and allows the VNF to be allocated by the other VIM of the multiple VIMs.
  • the first node is a VIM
  • the multiple second nodes are multiple VNFMs.
  • the second node that is determined to be released by the determining unit is the first VNFM that satisfies the second condition
  • the second condition is that the VIM allocates resources for a VNF managed by a first one of the plurality of VNFMs, and allows the VNF to be allocated by another VIM that has established a connection with the first VNFM. .
  • the sending unit is further configured to: after the determining unit determines, from the plurality of second nodes, the second node that is allowed to release the connection, send a second connection release notification message to the second node that is allowed to release the connection, where
  • the second connection release notification message carries the identifier of the first node, where the second connection release notification message is used to notify the second node that is allowed to release the connection, and deletes the saved in the second node that is allowed to release the connection.
  • the present invention provides a device for releasing a connection, comprising:
  • a processor configured to determine, from among the plurality of second nodes, a second node that allows the connection to be released, where the plurality of second nodes are nodes that have established a connection with the first node;
  • the processor is further configured to delete information about the second node that is allowed to release the connection saved in the first node.
  • the processor is specifically configured to receive, by the management node, a first connection release notification message, where the first connection release notification message carries an identifier of the second node that is allowed to release the connection;
  • the processor is specifically configured to determine, according to the identifier of the second node that is allowed to release the connection, the second node that is allowed to release the connection.
  • the processor is further configured to: before receiving the first connection release notification message sent by the management node, send a connection release request message to the management node, where the connection release request message is used to request the management node to determine the permission Release the second node of the connection.
  • the first node is a virtual network function management node VNFM, and the plurality of second nodes are multiple virtual machine infrastructure management nodes VIM; or
  • the first node is a VIM
  • the plurality of second nodes are multiple VNFMs.
  • the first node is a VNFM
  • the multiple second nodes are multiple VIMs.
  • the second node that is determined by the processor to release the connection is that the VNFM has no resource management relationship among the multiple VIMs. VIM; or,
  • the second node that is determined by the processor to release the connection is the first VIM that meets the first condition
  • the first condition is that the first VIM of the multiple VIMs allocates resources for the virtual network function VNF managed by the VNFM, and allows the VNF to be allocated by the other VIM of the multiple VIMs. .
  • the processor is further configured to: after determining, from the plurality of second nodes, the second node that is allowed to release the connection, deleting the information of the second node that is allowed to release the connection saved in the first node, The second node that is allowed to release the connection sends a second connection release notification message, where the second connection release notification message carries the first node And the second connection release notification message is used to notify the second node that is allowed to release the connection, and delete the first node indicated by the identifier of the first node saved in the second node that is allowed to release the connection. Information.
  • the present invention provides an apparatus for releasing a connection, comprising:
  • a processor configured to determine, from among the plurality of second nodes, a second node that allows the connection to be released, where the plurality of second nodes are nodes that have established a connection with the first node;
  • the processor is further configured to send a first connection release notification message to the first node, where the first connection release notification message carries an identifier of the second node that is allowed to release the connection, and the first connection is released.
  • the notification message is used to notify the first node to delete the information of the second node that is allowed to release the connection saved in the first node.
  • the second node that has no resource management relationship with the first node exists in the multiple second nodes, the second node that is determined by the processor to release the connection is the plurality of second nodes. A second node having no resource management relationship with the first node.
  • the processor is further configured to: before the determining unit determines, from the plurality of second nodes, the second node that is allowed to release the connection, receive a connection release request message sent by the first node, where the connection release request message is used by Determining, by the determining unit, the second node that is allowed to release the connection;
  • the processor is specifically configured to determine, according to the connection release request message, a second node that is allowed to release the connection from the plurality of second nodes.
  • the first node is a VNFM, and the plurality of second nodes are multiple VIMs; or
  • the first node is a VIM
  • the plurality of second nodes are multiple VNFMs.
  • the first node is a VNFM
  • the multiple second nodes are multiple VIMs.
  • the second node that is determined by the processor to release the connection is the first VIM that meets the first condition
  • the first condition is that the first VIM of the multiple VIMs allocates resources for the virtual network function VNF managed by the VNFM, and allows the VNF to be allocated by the other VIM of the multiple VIMs. .
  • the first node is a VIM
  • the multiple second nodes are multiple VNFMs.
  • the second node that is determined by the processor to release the connection is the first VNFM that meets the second condition
  • the second condition is that the VIM allocates resources for a VNF managed by a first one of the plurality of VNFMs, and allows the VNF to be allocated by another VIM that has established a connection with the first VNFM. .
  • the processor is further configured to: after determining, from the plurality of second nodes, the second node that is allowed to release the connection, send a second connection release notification message to the second node that is allowed to release the connection, where the second connection is released
  • the notification message carries the identifier of the first node, where the second connection release notification message is used to notify the second node that is allowed to release the connection, and delete the first saved in the second node that is allowed to release the connection.
  • the present invention provides a communication system, including:
  • the present invention provides a method, apparatus and system for releasing a connection, comprising: a first node determining, from a plurality of second nodes, a second node that allows a connection to be released, and deleting a second node of the first node that is allowed to release the connection saved in the first node Information, wherein the plurality of second nodes are nodes that have established a connection with the first node.
  • the first node can release the connection between the second node that is allowed to release the connection, so as to save connection resources of the first node, so that the first node has idle connection resources to establish and A new connection between the other second nodes, thereby enabling the first node to communicate with the other second node.
  • FIG. 1 is an architectural diagram of an existing NFV system
  • FIG. 2 is a flowchart 1 of a method for releasing a connection according to an embodiment of the present invention
  • FIG. 3 is a second flowchart of a method for releasing a connection according to an embodiment of the present invention
  • FIG. 4 is an interaction diagram 1 of a method for releasing a connection according to an embodiment of the present invention.
  • FIG. 5 is an interaction diagram 2 of a method for releasing a connection according to an embodiment of the present invention.
  • FIG. 6 is an interaction diagram 3 of a method for releasing a connection according to an embodiment of the present invention.
  • FIG. 7 is an interaction diagram 4 of a method for releasing a connection according to an embodiment of the present invention.
  • FIG. 8 is an interaction diagram 5 of a method for releasing a connection according to an embodiment of the present invention.
  • FIG. 9 is an interaction diagram 6 of a method for releasing a connection according to an embodiment of the present invention.
  • FIG. 10 is an interaction diagram 7 of a method for releasing a connection according to an embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram 1 of a device for releasing a connection according to an embodiment of the present invention.
  • FIG. 12 is a schematic structural diagram 2 of a device for releasing a connection according to an embodiment of the present invention.
  • FIG. 13 is a schematic structural diagram of an apparatus for releasing a connection according to an embodiment of the present invention.
  • Figure III is a schematic structural diagram of an apparatus for releasing a connection according to an embodiment of the present invention.
  • FIG. 14 is a schematic structural diagram 4 of a device for releasing a connection according to an embodiment of the present invention.
  • FIG. 15 is a first schematic structural diagram of a hardware structure of an apparatus for releasing a connection according to an embodiment of the present invention.
  • FIG. 16 is a second schematic structural diagram of a hardware structure of a device for releasing a connection according to an embodiment of the present disclosure
  • FIG. 17 is a block diagram of a communication system according to an embodiment of the present invention.
  • the NFV system includes: NFVO, VNFM, VIM, operation support system (English: operations support system, abbreviation: OSS) or business support system (English: business support system, abbreviation: BSS), network element management node (English: element manager , abbreviations: EM), VNF nodes, virtual network function infrastructure (English: network function virtualization infrastructure, abbreviation: NFVI) and other functional nodes, where OSS/BSS, or OSS/BSS user interface can be called network management Node (English: network manager, abbreviation: NM).
  • NFVO In the NFV system, NFVO, VNFM and VIM form the NFV management and orchestration (NFV-MANO) domain. Among them, NFVO can also be called network function virtualization orchestrator.
  • NFVO can operate, manage and coordinate VIM in the NFV system, that is, NFVO is responsible for scheduling resources managed by all VIMs in the NFV system.
  • NFVO is connected to all VIMs and VNFMs in the NFV system.
  • VIM is the management portal for infrastructure and resources. It provides resource management for VNF. It specifically provides NFVI resource management for VNF, including configuration maintenance, resource monitoring, alarm, and performance management for infrastructure-related hardware and virtualization resources for VNF. .
  • the VNFM is responsible for the lifecycle management of the VNF, and specifically implements lifecycle management of the VNF by applying for resources or releasing resources to the NFVO, including instantiating, expanding/reducing, querying, updating, and terminating the VNF.
  • the VNFM needs to request the VIM specified by the NFVO to allocate resources for the VNF managed by the VNFM, if the connection between the VNFM and the VIM is not established, the VNFM needs to establish a connection with the VIM. Thus, the VIM allocates resources for the VNF.
  • the number of VIMs that can establish a connection with the VNFM is limited, and the number of VNFMs that can establish a connection with the VIM is also limited.
  • a VNFM requests a NFVO to allocate resources to the VNF managed by the VNFM
  • the number of VIMs that have established a connection with the VNFM reaches a threshold
  • a connection between the VIMs specified by the NFVO may cause the VNFM to fail to establish a connection with the VIM specified by the NFVO because there is no free connection resource, so that the VNFM cannot request the VIM specified by the NFVO to allocate resources for the VNF.
  • the VIM when the number of VNFMs that have established a connection with a VIM reaches the threshold, if the VIM has not established a connection with the new VNFM to which the resource allocation is requested, the VIM will not be An idle connection resource cannot establish a connection with the VNFM, so that even if the remaining resources of the VIM can satisfy the VNFM requesting resources of the VNF, the VIM cannot allocate resources for the VNF.
  • the present invention provides a method, apparatus and system for releasing a connection such that a node establishes a new connection by reasonably releasing an established connection with other nodes to ensure that the node has idle connection resources.
  • any one of the foregoing NFV systems may be implemented by one physical device, or may be implemented by multiple physical devices, and multiple functional nodes in the NFV system may be different.
  • the physical device implementations may also be implemented by the same physical device. It can be understood that any functional node in the NFV system may be a logical functional module in the physical device, or may be a logical functional module composed of multiple physical devices.
  • each step in the method provided by the embodiment of the present invention may be performed by an entity device, and each step in the method provided by the embodiment of the present invention may be performed by multiple entity devices. This invention is not limited.
  • a logical function module ie, a function node in an NFV system
  • the logic function The module depends on the hardware resources on the physical device it is in.
  • the NFV system can be applied to a long term evolution (English: long term evolution, abbreviation: LTE) communication system, and can also be applied to an LTE evolved communication system, such as LTE-A (English full name: long term In the evolution advanced system, it can also be applied to third-generation mobile communication (English: 3rd-Generation, 3G) system such as WCDMA, and the present invention is not limited.
  • LTE long term evolution
  • LTE-A English full name: long term In the evolution advanced system
  • 3G Third-generation mobile communication
  • WCDMA Wideband Code Division Multiple Access
  • An embodiment of the present invention provides a method for releasing a connection. As shown in FIG. 2, the method includes:
  • the first node determines, from the plurality of second nodes, a second node that is allowed to release the connection, where the multiple second nodes are nodes that have established a connection with the first node.
  • the first node may be a VNFM or a VIM.
  • the multiple second nodes are multiple VIMs, and the multiple VIMs have established a connection with the VNFM;
  • the multiple second nodes are A plurality of VNFMs, and the plurality of VNFMs have established a connection with the VIM.
  • the first node may determine, from the plurality of second nodes, the second node that is allowed to release the connection according to the indication of the management node. For example, when the management node determines that the second node that is allowed to release the connection exists in the plurality of second nodes, the management node carries the identifier of the second node that allows the connection to be released in the first connection release notification message, and The first node sends, so that after receiving the first connection release notification message, the first node may determine, from the plurality of second nodes, the second node that is allowed to release the connection according to the identifier of the second node that is allowed to release the connection.
  • the VNFM may also determine, from the multiple VIMs, the VIMs that are allowed to release the connection.
  • the second node that is allowed to release the connection may be a second node of the plurality of second nodes that has no resource management relationship with the first node, or meets a preset for the multiple second nodes.
  • the preset condition may be set according to actual network maintenance requirements, so that the first node can select a suitable second node to release the connection with the second node.
  • the first node deletes information about the second node that is allowed to release the connection saved in the first node.
  • the information of the second node that is allowed to release the connection includes the identifier and connection information of the second node that allows the connection to be released.
  • the connection information of the second node that is allowed to release the connection may include at least the IP address of the second node that allows the connection to be released, a uniform resource locator (abbreviation: URL), a username, an authentication password, and the like.
  • the first node after the first node deletes the information of the second node that is allowed to release the connection, the first node is successfully characterized that the connection between the second node and the second node that is allowed to release the connection is successfully released.
  • An embodiment of the present invention provides a method for releasing a connection, where the first node determines, from a plurality of second nodes, a second node that is allowed to release the connection, and deletes information of the second node that is saved in the first node and allows the connection to be released.
  • the plurality of second nodes are nodes that have established a connection with the first node.
  • the first node can release the connection between the second node that is allowed to release the connection to save the connection resources of the first node, so that the first node has idle connection resources to establish between the other nodes. a new connection, which in turn enables the first node to communicate with the other second node.
  • An embodiment of the present invention provides a method for releasing a connection. As shown in FIG. 3, the method includes:
  • the management node determines, from the plurality of second nodes, a second node that is allowed to release the connection, where the multiple second nodes are nodes that have established a connection with the first node.
  • the first node may be a VNFM or a VIM. Specifically, when a node is a VNFM, the plurality of second nodes are multiple VIMs, and the multiple VIMs have established a connection with the VNFM; when the first node is a VIM, the multiple second nodes are multiple VNFMs, and The plurality of VNFMs have already established a connection with the VIM.
  • the management node may be the NFVO in the NFV system where the first node and the plurality of second nodes are located, or other functional nodes in the NFV system having the function of NFVO, that is, the management node may be A functional node capable of scheduling resources managed by all VIMs in the NFV system is not limited in this invention.
  • the management node may directly select a second node having no resource management relationship with the first node from the plurality of second nodes as the second node that allows the connection to be released.
  • the management node may also select a second node that satisfies the preset condition from among the plurality of second nodes as the second node that allows the connection to be released.
  • the preset condition may be set according to actual network maintenance requirements, so that the management node can select a suitable second node as the second node that allows the connection to be released according to the preset condition.
  • the management node sends a first connection release notification message to the first node, where the first connection release notification message carries the identifier of the second node that is allowed to release the connection, and the first connection release notification message is used to notify the first node to delete the first node.
  • the management node may carry the identifier of the second node that is allowed to release the connection in the first connection release notification message, and Sending, so that the first node receives the first connection release notification message, deletes the information of the second node that is allowed to release the connection saved in the first node, that is, notifies the first node to automatically release the connection with the allow release connection.
  • the connection between the two nodes may carry the identifier of the second node that is allowed to release the connection in the first connection release notification message, and Sending, so that the first node receives the first connection release notification message, deletes the information of the second node that is allowed to release the connection saved in the first node, that is, notifies the first node to automatically release the connection with the allow release connection.
  • An embodiment of the present invention provides a method for releasing a connection, including: a management node determining, from a plurality of second nodes, a second node that is allowed to release a connection, and sending a first connection release notification message to the first node, the first connection release notification The message carries an identifier of the second node that is allowed to release the connection, and the first connection release notification message is used to notify the first node to delete the information of the second node that is saved in the first node and that is allowed to release the connection, the multiple second node A node that has established a connection with the first node.
  • the management node can select a suitable second node among the plurality of second nodes that have established a connection with the first node, and notify the first node to release the connection with the second node in time to save the first
  • the connection resources of the nodes such that the first node has idle connection resources to establish a new connection with other second nodes, thereby enabling the first node to communicate with the other second nodes.
  • the embodiment of the present invention provides a method for releasing a connection, which can be used in various application scenarios.
  • the following describes the method for releasing a connection provided by the embodiment of the present invention in the following three possible application scenarios.
  • the management node initiates a release connection process.
  • the management node may be an NFVO in the NFV system, or may be another functional node having the function of the NFVO, that is, the management node may be a function node capable of scheduling resources managed by all VIMs in the NFV system, and the present invention does not limit.
  • a resource mapping table is set, which records the resource application status of each VNFM in the NFV system, the resource allocation status of each VIM, and the connection between the VNFM and the VIM. For example, a VNFM establishes a connection with which VIMs, and the VIMs are allocated resources and resource types of the VNFs managed by the VNFM. Therefore, the management node can query the resource mapping table to know which VIMs in the NFV system are respectively connected with which VIMs, and which VNFMs are connected to each VIM, and the VIMs and VNFMs that have established connections. There is no resource management relationship between them.
  • a resource management relationship between a VNFM and a VIM that has established a connection means that the VIM reserves or allocates resources for at least one VNF managed by the VNFM; a VNFM that has established a connection. There is no resource management relationship with a VIM, which means that the VIM does not reserve or allocate resources for any VNF managed by the VNFM.
  • the VNFM that can establish a connection with the VIM is also limited. Therefore, if there is no resource management relationship between a VNFM and a VIM that have established a connection, Can release this A connection between the VNFM and the VIM to save connection resources between the VNFM and the VIM.
  • the management node queries the resource mapping table to find that multiple second nodes that have established a connection with a certain first node, there is no resource management with the first node. When the second node of the relationship, the management node needs to initiate a connection release process.
  • the first node may be a VNFM or a VIM.
  • the multiple second nodes are multiple VIMs, and the multiple VIMs have established a connection with the VNFM;
  • the multiple second nodes are A plurality of VNFMs, and the plurality of VNFMs have established a connection with the VIM.
  • the method may include:
  • the management node determines, from the plurality of second nodes, a second node that is allowed to release the connection, where the multiple second nodes are nodes that have established a connection with the first node.
  • the second node that is determined by the management node to allow the connection to be released is specifically the second node of the plurality of second nodes that has no resource management relationship with the first node.
  • the management node finds that there is a second node in the plurality of second nodes that has no resource management relationship with the first node by querying the resource mapping table, the management node can determine the first node and The connection between the second node of the first node without the resource management relationship is allowed to be released.
  • the management node may determine, in the process of lifecycle management of the VNF, whether there is a second node in the plurality of second nodes that has no resource management relationship with the first node.
  • the management node queries the resource mapping table to select a suitable VIM to allocate resources for the VNF.
  • the management node may query multiple VIMs that have established a connection with the VNFM that manages the VNF, and determine whether the multiple VIMs exist or not.
  • the VNFM has no resource management Department of VIM.
  • the management node may also periodically query the resource mapping table. Specifically, if the first node is a VNFM and the second node is a VIM, the management node may periodically query the resource mapping table for information about each VNFM in the NFV system, and determine that it is already associated with a VNFM. If there is a VIM with no resource management relationship with the VNFM, if the first node is a VIM and the second node is a VNFM, the management node can periodically query the NFV system in the resource mapping table. In the information about each VIM in the medium, it is determined whether there is a VNFM that has no resource management relationship with the VIM in the plurality of VNFMs that have established a connection with a certain VIM.
  • the management node sends a first connection release notification message to the first node, where the first connection release notification message carries the identifier of the second node that allows the connection to be released.
  • the management node may notify the first node that the connection with the second node that is allowed to release the connection may be released. That is, the first connection release notification message is used to notify the first node to delete the information of the second node of the saved release connection that it saves.
  • the first node After receiving the first connection release notification message, the first node determines, according to the identifier of the second node that is allowed to release the connection, the second node that is allowed to release the connection.
  • the first node can determine the release and the release according to the identifier of the second node that is allowed to release the connection carried in the first connection release notification message.
  • the connection between the connected second nodes is allowed to be released, ie the first node determines that the second node information of the allowed release connection that it holds can be deleted.
  • the first node sends a second connection release notification message to the second node that is allowed to release the connection, where the second connection release notification message carries the identifier of the first node.
  • the first node after the first node determines that the second node information of the allowed release connection that can be saved is deleted, the first node first needs to connect to the second node that is connected to the release release.
  • the second node that is allowed to release the connection sends a second connection release notification message to notify the second node that is allowed to release the connection also deletes Save the information of the first node.
  • the first node deletes information about the second node that is allowed to release the connection saved in the first node.
  • the information of the second node that is allowed to release the connection is the same as the information of the second node that is allowed to release the connection in the embodiment shown in FIG. 2, and details are not described herein.
  • the first node successfully released the connection between the first node and the second node that is allowed to release the connection.
  • the second node that is allowed to release the connection determines the first node according to the identifier of the first node.
  • the second node that is allowed to release the connection can determine the first node and the first node according to the identifier of the first node carried in the second connection release notification message.
  • the connection is allowed to be released.
  • the second node that is allowed to release the connection deletes the information of the first node saved in the second node that allows the connection to be released.
  • the information of the first node includes the identifier and connection information of the first node.
  • the connection information of the first node may include at least an IP address of the first node, a uniform resource locator (English: universal resource locator, abbreviation: URL), a user name, an authentication password, and the like.
  • the second node that is allowed to release the connection also successfully released the connection with the first node.
  • the method may include:
  • the management node determines, from the plurality of second nodes, a second node that is allowed to release the connection, where the multiple second nodes are nodes that have established a connection with the first node.
  • the management node sends a first connection release notification message to the first node, where the identifier of the second node that is allowed to release the connection is carried in the first connection release notification message.
  • the first node deletes information about the second node that is allowed to release the connection saved in the first node.
  • the management node sends a second connection release notification message to the second node that is allowed to release the connection, where the second connection release notification message carries the identifier of the first node.
  • the management node may directly grant the The second node that releases the connection sends a second connection release notification message to notify the second node that is allowed to release the connection and also deletes the information that holds the first node.
  • the second node that is allowed to release the connection determines the first node according to the identifier of the first node.
  • the second node that is allowed to release the connection deletes the information of the first node saved in the second node that allows the connection to be released.
  • the second node that is allowed to release the connection also successfully released the connection with the first node.
  • the first node and the second node that is allowed to release the connection may also be Send a confirmation message to the management node to make the management section
  • the point determines that the connection between the first node and the second node that is allowed to release the connection has been successfully released, and the management node can update the resource mapping table.
  • the management node is able to determine that there is no resource management with the first node among the plurality of second nodes that have established a connection with the first node. After the second node of the relationship, the first node and the second node having no resource management relationship with the first node are notified in time, and the first node and the second node having no resource management relationship with the first node are released.
  • the connection avoids the connection between the first node and the second node that has no resource management relationship with the first node, and continues to occupy the connection between the first node and the second node that has no resource management relationship with the first node. Resources, thereby saving connection resources of the first node and the second node having no resource management relationship with the first node.
  • the connection release process is initiated by the VNFM.
  • the VNFM since the number of VIMs that can establish a connection with the VNFM is limited, when the VNFM determines that the number of VIMs that have established a connection with it reaches a threshold, the VNFM needs to initiate a connection release procedure.
  • the first node is a VNFM
  • the multiple second nodes are VIMs
  • the multiple VIMs are VIMs that have established a connection with the VNFM.
  • the method may include:
  • the VNFM determines that the number of the multiple VIMs reaches a preset threshold.
  • the preset threshold may be a maximum number of VIMs that can establish a connection with the VNFM, or a threshold that is less than the maximum number according to actual network maintenance requirements.
  • the VNFM can periodically determine whether the number of VIMs that have established a connection with the preset threshold is reached.
  • the VNFM can also determine whether the number of VIMs that have been connected to it reaches a preset threshold after each connection is established with the new VIM.
  • the VNFM sends a connection release request message to the management node, where the connection release request message is used to request the management node to determine to allow the connection of the VIM to be released.
  • the VNFM may send a connection release request message to the management node to request the management node to determine, from the plurality of VIMs, the VIM that allows the connection to be released.
  • the management node determines, according to the connection release request message, a VIM that allows the connection to be released from the plurality of VIMs.
  • the management node determines that it is required to release the connected VIM from the plurality of VIMs that have established a connection with the VNFM.
  • the management node may first query the resource mapping table set in the management node to determine whether there is a VIM in the plurality of VIMs that has no resource management relationship with the VNFM.
  • the management node determines that there is a VIM in the plurality of VIMs that has no resource management relationship with the VNFM, the management node determines that the VIMs in the plurality of VIMs that have no resource management relationship with the VNFM are allowed to release the connected VIMs.
  • the management node determines that there is no VIM in the plurality of VIMs that has no resource management relationship with the VNFM, the management node determines the first VIM that satisfies the first condition among the plurality of VIMs as a VIM that allows the connection to be released.
  • the first condition is that the first VIM of the plurality of VIMs allocates resources for the VNF managed by the VNFM, and allows the VNF to be allocated by the other VIM of the multiple VIMs.
  • VIM1, VIM2, and VIM3 will be taken as an example for exemplary description.
  • VIM1, VIM2, and VIM3 a plurality of VIMs that have established a connection with the VNFM.
  • the management node determines that there is no VIM in the VIM1, VIM2, and VIM3 that has no resource management relationship with the VNFM.
  • the VIM that allows the connection to be released is determined from VIM1, VIM2, and VIM3.
  • the management node obtains information about remaining resources of VIM1, VIM2, and VIM3, and information of resources allocated for VNFs managed by the VNFM.
  • the information about the remaining resources of the VIM includes at least the remaining resources of the VIM and the types of the remaining resources.
  • the information of the resources allocated by the VIM to the VNF managed by the VNFM includes at least the amount of resources allocated by the VIM for the VNF managed by the VNFM, and the type of resources allocated by the VIM for the VNF managed by the VNFM.
  • the information of the remaining resources of the VIM1 is: 2 A type VMs, 1 B type VMs; the VIM1 resource information allocated to the VNFM includes: 1 type A VM.
  • VIM2 information for the VNFM allocated resources includes: 2 C type VMs.
  • the information about the remaining resources of the VIM3 is: 2 types of VMs, 2 types of VMs; and the information of the resources allocated by the VIM3 to the VNFM includes: 2 B-type VMs.
  • the management node may directly obtain information about remaining resources of VIM1 and information of resources allocated by VIM1 for the VNFM from the resource mapping table.
  • the management node can also obtain information about the remaining resources of VIM1 by querying VIM1. Specifically, the management node sends a residual resource query message to the VIM1. After receiving the remaining resource query message, the VIM1 carries the information of the remaining resources of the VIM1 in the response message to the management node, so that the management node responds according to the response message. , get information about the remaining resources of VIM1.
  • the management node acquires information about the remaining resources of the VIM1, the VIM2, and the VIM3, and the information of the resources allocated to the VNF managed by the VNFM, the information of the remaining resources of the VIM1, the VIM2, and the VIM3 is managed by the VNFM.
  • the information of the resources allocated by the VNF determines whether there is a first VIM that satisfies the first condition in VIM1, VIM2, and VIM3.
  • the management node may first compare the information of the resources allocated by the VIM1 to the VNF managed by the VNFM, and compare the information of the remaining resources of the VIM2 and the VIM3, respectively, if the remaining resource information of the at least one VIM in the VIM2 and the VIM3 can satisfy.
  • the VIM1 is information about resources allocated by the VNF managed by the VNFM, and the management node determines that the VIM1 is the first VIM that satisfies the first condition.
  • VIM1 assigns an A type to the VNF1 managed by the VNFM.
  • VM because the remaining resources of VIM2 include one type A VM, and the remaining resources of VIM3 include two types of VMs of type A. Therefore, the information of the remaining resources of VIM2 and VIM3 can satisfy the information of resources allocated by VIM1 to VNF1. That is, VIM1 allocates resources for VNF1, which can be allocated by VIM1 or VIM3 for VNF1. Thereby the management node can determine that VIM1 is the first VIM that satisfies the first condition.
  • the management node determines whether the VIM1 is the first VIM that satisfies the first condition, determines the VIM2 and the VIM3 one by one, and determines that the VIM2 is also the first VIM that satisfies the first condition, that is, the VIM2 is the VNFM.
  • the resources allocated by the managed VNF2 and VNF3 can be allocated by VIM3 for VNF2 and VNF3.
  • the management node may directly determine that the VIM1 is allowed to release the connected VIM. There is no need to further judge VIM2 and VIM3; or when the management node judges VIM1, VIM2, and VIM3 one by one, and determines that VIM1 and VIM2 are the first VIM, the management node can randomly select one of VIM1 or VIM2 as the VIM that allows the connection to be released. It is also possible to select a VIM with poor data transmission quality between the VNFM and the VIMM as a VIM that allows the connection to be released, which is not limited in comparison with the present invention.
  • VIM3 can allocate resources allocated by VIM1 to VNF1 for VNF1, VNF2 and VNF3 can also be allocated by VIM2 for VNF2 and VNF3. Resources, therefore, the management node can determine both VIM1 and VIM2 to allow the connection of the VIM to be released.
  • VIM3 cannot simultaneously allocate resources allocated by VIM1 and VIM2 for the VNF managed by the VNFM, the management node can select one of VIM1 and VIM2 as the VIM that allows the connection to be released.
  • a filtering condition can also be set in the management node.
  • the management node may first select a VIM that satisfies the screening condition from VIM1, VIM2, and VIM3, and determine whether the VIM that satisfies the screening condition is the first VIM that satisfies the first condition.
  • the screening conditions may include, but are not limited to, one or more conditions of a VIM that allocates the least amount of resources for the VNF managed by the VNFM, a VIM with the largest delay, and a VIM with the highest failure rate.
  • the filter conditions set in the management node include the VIM allocated the least amount of resources for the VNF managed by the VNFM.
  • the management node first obtains the information of the resources allocated by the VNF, the VIM2, and the VIM3 to the VNF managed by the VNFM by querying the resource mapping table, and the management node allocates the resources allocated by the VIM, VIM2, and VIM3 to the VNF managed by the VNFM.
  • the comparison determines the VIM allocated the least amount of resources for the VNF managed by the VNFM.
  • VIM1 allocates 1 VM for VNF1
  • VIM2 allocates 1 VM for VNF2 and VNF3
  • VIM3 allocates 2 VMs for VNF4 managed by the VNFM. Therefore, VIM1 is VIMM for VIM1, VIM2, and VIM3.
  • the managed VNF allocates the least amount of resources to the VIM.
  • the management node acquires the remaining resource information of the VIM2 and the VIM3, and determines whether the VIM1 is the first VIM that satisfies the first condition, according to the information of the resource allocated by the VIM1 to the VNF1, and the remaining resource information of the VIM2 and the VIM3.
  • the management node determines whether the VIM1 is the first VIM that satisfies the first condition, and the manner in which the management node determines whether the VIM1 is the first VIM that meets the first condition is the same as that in the first mode, and details are not described herein again.
  • the management node can determine that the VIM1 is a VIM that allows the link to be released. If VIM1 is not the first node, the management node may determine that there is no VIM in VIM1, VIM2, and VIM3 that allows the link to be released, and the management node may not respond to the connection release request message sent by the VNFM.
  • the management node sends a first connection release notification message to the VNFM, where the first connection release notification message carries the identifier of the VIM that allows the connection to be released.
  • the VNFM After receiving the first connection release notification message, the VNFM determines, according to the identifier of the VIM that is allowed to release the connection, the VIM that allows the connection to be released.
  • the VNFM is based on Determining, by the first connection release notification message, the identifier of the VIM that allows the connection to be released, that is, the connection between the VIM and the VIM that is allowed to release the connection is allowed to be released, that is, the first connection release notification message is used to notify the VNFM to delete It saves the information of the VIM that allows the connection to be released.
  • the VNFM sends a second connection release notification message to the VIM that is allowed to release the connection, where the second connection release notification message carries the identifier of the VNFM.
  • the VNFM after the VNFM determines that the information of the VIM that is allowed to release the connection can be deleted, the VNFM first needs to send the VIM to the VIM that is allowed to release the connection through the connection with the VIM that is allowed to release the connection.
  • the second connection release notification message notifies that the VIM that is allowed to release the connection also deletes the information that holds the VNFM.
  • the VNFM deletes the information about the VIM that is allowed to release the connection saved in the VNFM.
  • the information about the VIM that allows the connection to be released includes the identifier and the connection information of the VIM that allows the connection to be released, wherein the connection information includes information such as an IP address, a URL, a username, an authentication password, and the like of the VIM that allows the connection to be released.
  • the VNFM successfully releases the connection of the VNFM to the VIM that is allowed to release the connection.
  • the VIM that is allowed to release the connection determines the VNFM according to the identifier of the VNFM.
  • the VIM that allows the release of the connection can determine that the connection between the VNFM and the VNFM is permitted according to the identifier of the VNFM carried in the second connection release notification message. Release, ie the VIM that allows the connection to be released, can delete the information of the VNFM it holds.
  • the VIM that allows the connection to be released deletes the information of the VNFM saved in the VIM that allows the connection to be released.
  • the information of the VNFM includes the identifier and connection information of the VNFM, and the connection information of the VNFM includes information such as an IP address, a URL, a username, an authentication password, and the like of the VNFM.
  • the VIM that allows the connection to be released also successfully releases the connection with the VNFM.
  • the method may include:
  • the VNFM determines that the number of the multiple VIMs reaches a preset threshold.
  • the VNFM sends a connection release request message to the management node, where the connection release request message is used to request the management node to determine to allow the connection of the VIM to be released.
  • the management node determines, according to the connection release request message, a VIM that allows the connection to be released from the plurality of VIMs.
  • the management node sends a first connection release notification message to the VNFM, where the first connection release notification message carries the identifier of the VIM that allows the connection to be released.
  • the VNFM determines, according to the identifier of the VIM that is allowed to release the connection, the VIM that is allowed to release the connection.
  • the VNFM deletes the information about the VIM that is allowed to release the connection saved in the VNFM.
  • the VNFM successfully releases the connection between the VNFM and the VIM that is allowed to release the connection.
  • the management node sends a second connection release notification message to the VIM that is allowed to release the connection, where the second connection release notification message carries the identifier of the VNFM.
  • the management node may directly directly release the VIM to the connection.
  • a second connection release notification message is sent to notify the VIM that is allowed to release the connection and also deletes the information that holds the VNFM.
  • the VIM that allows the connection to be released receives the second connection release notification message. Thereafter, the VNFM is determined based on the identity of the VNFM.
  • the VIM that allows the connection to be released deletes the information of the VNFM saved in the VIM that allows the connection to be released.
  • the VIM that allows the connection to be released also successfully releases the connection with the VNFM.
  • the VNFM and the VIM that allows the connection may also send an acknowledgement message to the management node, to The management node determines that the connection between the VNFM and the VIM that is allowed to release the connection has been successfully released, and the management node can update the resource mapping table.
  • the method for releasing a connection causes the VNFM to send the number of the VIMs that have been connected to the preset threshold to the management node in time.
  • a connection release request message is requested to request the management node to determine from the plurality of VIMs a VIM that allows the connection to be released.
  • the management node After the management node determines from the plurality of VIMs that the VIM is allowed to release the connection, the management node notifies the VNFM and the VIM that allows the release of the connection to release the connection between the VNFM and the VIM that allows the connection to be released, thereby saving the VNFM and The connection resource of the VIM is allowed to be released, and when the VNFM needs to request another VIM that has not established a connection with the VNF to allocate resources for the VNFM-managed VNF, the VNFM has idle connection resources to establish a connection with the other VIM. Connected to enable the VNFM to request the other VIM to allocate resources for the VNF.
  • the VNFM is able to determine from itself the VIMs that allow the connection to be released.
  • the method may include:
  • the VNFM determines that the number of the multiple VIMs reaches a preset threshold.
  • the VNFM determines, from the plurality of VIMs, a VIM that allows the connection to be released.
  • the VNFM records the resource application status of the VNFM and the connection establishment relationship with the VIM. Therefore, the VNFM may first determine whether there are VIMs in the multiple VIMs that have no resource management relationship with the VIM.
  • the VNFM determines that there are VIMs in the plurality of VIMs that have no resource management relationship with them, the VNFM determines that the VIMs with which there is no resource management relationship are allowed to release the connected VIMs.
  • the VNFM determines that there is no VIM in the plurality of VIMs that has no resource management relationship, the VNFM determines that the first VIM that satisfies the first condition among the plurality of VIMs is a VIM that allows the connection to be released.
  • the first condition is that the first VIM of the plurality of VIMs allocates resources for the VNF managed by the VNFM, and allows the VNF to be allocated by the other VIM of the multiple VIMs.
  • the VNFM determines the first VIM that satisfies the first condition in the multiple VIMs as a specific implementation manner of allowing the connected VIM to be released, and the management node in the embodiment shown in FIG. 6 satisfies the first one of the multiple VIMs.
  • the specific implementation of the condition that the first VIM is determined to allow the release of the connected VIM is similar.
  • the VNFM determines that the first VIM that satisfies the first condition in the plurality of VIMs is determined to allow the release of the connected VIM.
  • the related description in the embodiment is shown, and details are not described herein again.
  • the VNFM determines that the first VIM that satisfies the first condition in the multiple VIMs is to allow the connected VIM to be released, the VNFM needs to obtain information about the remaining resources of the multiple VIMs and is managed by the VNFM. Information about the resources allocated by the VNF.
  • the VNFM since the VNFM records the resource requesting the VNFM to the multiple VIMs, the VNFM can directly obtain the information of the resources allocated by the multiple VIMs for the VNF managed by the VNFM.
  • the VNFM needs to obtain remaining resource information of the multiple VIMs by sending a residual resource query message to the multiple VIMs. Specifically, the VNFM obtains the remaining resources of the multiple VIMs by sending a remaining resource query message to the multiple VIMs.
  • the manner of the information is the same as the manner in which the management node sends the remaining resource query message to the VIM1 to obtain the remaining resource information of the VIM1 in the embodiment shown in FIG. 6. For details, refer to the related description in the embodiment shown in FIG. 6.
  • the VNFM sends a second connection release notification message to the VIM that allows the connection to be released.
  • the second connection release notification message carries the identifier of the VNFM.
  • the VNFM deletes the information about the VIM that is allowed to release the connection saved in the VNFM.
  • the VIM that is allowed to release the connection determines the VNFM according to the identifier of the VNFM.
  • the VIM that allows the connection to be released deletes the information of the VNFM saved in the VIM that allows the connection to be released.
  • the specific implementation manners of the foregoing S703-S706 are the same as the implementation manners of the S506-S509 in the embodiment shown in FIG. 6.
  • the method for releasing a connection causes the VNFM to automatically determine the number of multiple VIMs that have been connected to the VNFM after the preset threshold is reached.
  • the VIM determines that a VIM that allows the connection to be released is selected from the plurality of VIMs, and releases the connection with the VIM that is allowed to release the connection, thereby saving connection resources of the VNFM, and then the VNFM needs to establish a connection with the request.
  • the VNFM allocates resources for the VNF managed by the VNFM
  • the VNFM has idle connection resources to establish a connection with the other VIM, so that the VNFM can request the other VIM to allocate resources for the VNF.
  • the VIM that allows the release of the connection is also notified to also release the connection between the VNFM and the VIM that allows the connection to be released, and the permission is also saved. Release the connection resources of the connected VIM.
  • the connection release process is initiated by the VIM.
  • the VIM since the number of VNFMs that can establish a connection with the VIM is limited, when the VIM determines that the number of VNFMs that have established a connection with it reaches a threshold value, Need to initiate a connection release process.
  • the first node is a VIM
  • the multiple second nodes are VNFMs
  • the multiple VNFMs are VNFMs that have established a connection with the VIM.
  • the method may include:
  • the VIM determines that the number of the multiple VNFMs reaches a preset threshold.
  • the preset threshold value may be a maximum number of VNFMs that can establish a connection with the VIM, or a threshold value smaller than the maximum number that is set according to actual network maintenance requirements.
  • the VIM can periodically determine whether the number of VNFMs connected to the VIMM reaches a preset threshold.
  • the VIM can also determine whether the number of VNFMs that have established a connection with the new VNFM reaches a preset threshold value each time it establishes a connection with the new VNFM.
  • the VIM sends a connection release request message to the management node, where the connection release request message is used to request the management node to determine the VNFM that is allowed to release the connection.
  • the VIM may send a connection release request message to the management node to request the management node to determine, from the multiple VNFMs, the VNFM that is allowed to release the connection.
  • the management node determines, according to the connection release request message, a VNFM that is allowed to release the connection from the plurality of VNFMs.
  • the management node determines that it is necessary to determine the VNFM that is allowed to release the connection from the plurality of VNFMs that have established a connection with the VIM.
  • the management node may first query the resource mapping table set in the management node to determine whether there is a VNFM in the plurality of VNFMs that has no resource management relationship with the VIM.
  • the management node determines that there is a VNFM in the plurality of VNFMs that has no resource management relationship with the VIM, the management node determines the VNFM in the plurality of VNFMs that have no resource management relationship with the VIM as the VNFM that allows the connection to be released.
  • the management node determines that there is no VNFM in the plurality of VNFMs that does not have a resource management relationship with the VIM, the management node determines the first VNFM that satisfies the second condition among the plurality of VNFMs as a VNFM that allows the connection to be released.
  • the second condition is that the VIM allocates resources for the VNF managed by the first VNFM of the plurality of VNFMs, and allows the VNF to be allocated by another VIM that has established a connection with the first VNFM.
  • the management node determines the first VNFM that satisfies the second condition in the plurality of VNFMs as the VNFM that allows the connection to be released, VIM4, VNFM1, VNFM2, and VNFM3 will be exemplified below.
  • VNFM1, VNFM2, and VNFM3 are determined to allow release of the linked VNFM.
  • Method 1 The management node first determines whether VNFM1 is the first VNFM that satisfies the second condition, and assumes that in addition to VIM4, VNFM1 also establishes a connection with VIM5 and VIM6.
  • the management node obtains information about resources allocated by VIM4 for the VNF managed by VNFM1, and information about remaining resources of VIM5 and VIM6.
  • the manner in which the management node obtains the information of the resource allocated by the VNF that is managed by the VNFM1 by the VIMM1, and the manner in which the management node obtains the information of the resource allocated by the VNF managed by the VNFM by the management node respectively is as shown in FIG.
  • the management node obtains the information about the remaining resources of the VIM5 and the VIM6 refer to the manner in which the management node obtains the information about the remaining resources of the VIM1 in the embodiment shown in FIG. 6, and details are not described herein again.
  • the management node may first compare the information of the resources allocated by the VIM4 to the VNF managed by the VNFM1, and compare the information of the remaining resources of the VIM5 and the VIM6 respectively. If the remaining resource information of the VIM in the VIM5 and the VIM6 is satisfied, the VIM4 is satisfied by the VNFM1. Management information of the VNF allocated resources, then the management node determines VNFM1 The first VNFM is to satisfy the second condition.
  • VIM4 allocates one A-type VM to VNF5 managed by VNFM1, and one of the remaining resources of VIM5 includes one A-type VM, and the remaining resources of VIM6 include two A-type VMs.
  • the information about the remaining resources of VIM5 and VIM6 can satisfy the information of the resources allocated by VIM4 to VNF5, that is, the resources allocated by VIM4 to VNF5, which can be allocated by VIM5 or VIM6 for VNF5. Therefore, the management node can determine that VNFM1 meets the second condition. The first VNFM.
  • the management node determines whether the VNFM1 is the first VNFM that satisfies the second condition, and determines the VNFM2 and the VNFM3, and determines that the VIM4 is a resource allocated by the VNF managed by the VNFM2, and may also establish a connection with the VNFM2.
  • the other VIMs are VNFs managed by VNFM2, ie the management node determines that VNFM2 is also the first VNFM that satisfies the second condition.
  • the management node determines that the VNFM1 is the first. After a VNFM, the management node can directly determine that VNFM1 is allowed to release the connected VNFM without further judgment on VNFM2 and VNFM3; or when the management node judges VNFM1, VNFM2, and VNFM3 one by one, and determines that VNFM1 and VNFM2 are the first VNFM.
  • the management node may randomly select one of VNFM1 or VNFM2 as the VNFM that allows the connection to be released, or select one of VNFM1 or VNFM2 that has poor data transmission quality with VIM4 as the VNFM that allows the connection to be released, which is not limited by the present invention.
  • the management node can determine both VNFM1 and VNFM2 as VNFMs that are allowed to release the connection.
  • a filtering condition can also be set in the management node.
  • the management node may first select the VNFM that satisfies the screening condition from the VNFM1, the VNFM2, and the VNFM3, and further determine whether the VNFM that satisfies the screening condition is the first VNFM that satisfies the second condition.
  • the screening conditions may include, but are not limited to, one or more conditions of VNFM occupying the least amount of resources, VNFM having the largest delay, and the like.
  • the filter conditions set in the management node include the VNFM that occupies the least amount of resources.
  • the management node first obtains the resource allocation information of the VNFs managed by VNFM1, VNFM2, and VNFM3 by querying the resource mapping table, and determines the occupied resources of VNFM1, VNFM2, and VNFM3, that is, determining that VIM4 is VNFM1, VNFM2, and VNFM3, respectively.
  • the amount of resources allocated by the managed VNF The management node compares the occupied resources of VNFM1, VNFM2, and VNFM3 to determine the VNFM that occupies the least amount of resources.
  • VIM4 allocates 1 VM for the VNF managed by VNFM1, and 2 VMs for VNF managed by VNFM2 and VNFM3. Therefore, the management node determines that VNFM1 is the VNFM with the least resources.
  • the management node acquires information about the remaining resources of the VIM5 and the VIM6 that have been connected to the VNFM1, and compares the information of the resources allocated by the VIM4 to the VNF managed by the VNFM1, and compares the information of the remaining resources of the VIM5 and the VIM6, respectively. If the remaining resource information of the at least one VIM in the VIM5 and the VIM6 can satisfy the information of the resource allocated by the VIM4 to the VNF managed by the VNFM1, the management node determines that the VNFM1 is the first VNFM that satisfies the second condition.
  • the management node determines that the VNFM1 is a VNFM that allows the connection to be released; if the VNFM1 is not the first VNFM that satisfies the second condition, the management node determines the VNFM1, the VNFM2, and There is no VNFM in VNFM3 that allows the connection to be released, and the management node may not respond to the connection release request message sent by VIM4.
  • the plurality of first VNFMs may also exist in the plurality of VNFMs that meet the screening conditions, and the management node may use the plurality of first VNFMs as the allowed release.
  • the connected VNFM may also randomly select a first VNFM as a VNFM that allows the connection to be released, which is not limited in this embodiment of the present invention.
  • the management node sends a first connection release notification message to the VIM, where the first connection release notification message carries the identifier of the VNFM that allows the connection to be released.
  • the management node may notify the VIM that the connection between the VNFM and the VNFM that is allowed to release the connection may be released, that is, the first connection release notification.
  • the message is used to notify the VIM to delete the information of the VNFM that it holds to allow the connection to be released.
  • the VIM determines, according to the identifier of the VNFM that is allowed to release the connection, the VNFM that is allowed to release the connection.
  • the VIM can determine the connection between the VNFM and the VNFM that is allowed to release the connection according to the identifier of the VNFM that is allowed to release the connection carried in the first connection release notification message.
  • the release is allowed, ie the VIM determines that it can delete the information of the VNFM that it holds to allow the connection to be released.
  • the VIM sends a second connection release notification message to the VNFM that is allowed to release the connection, where the second connection release notification message carries the identifier of the VIM.
  • the VIM after the VIM determines that the information of the VNFM that is allowed to release the connection can be deleted, the VIM first needs to send the VNFM to the VNFM that is allowed to release the connection through the connection with the VNFM that is allowed to release the connection.
  • the second connection release notification message notifies the VNFM that is allowed to release the connection, and also deletes the information for saving the VIM.
  • the VIM deletes the information of the VNFM that is allowed to release the connection saved in the VIM.
  • the VIM successfully releases the connection of the VIM to the VNFM that is allowed to release the connection.
  • the VNFM that is allowed to release the connection determines the VIM according to the identifier of the VIM.
  • the VNFM that is allowed to release the connection can determine that the connection between the VIM and the VIM is allowed according to the identifier of the VIM carried in the second connection release notification message. Release, ie the VNFM that allows the connection to be released, can delete the information of the VIM it holds.
  • the VNFM that allows the connection to be released deletes the information of the VIM saved in the VNFM that allows the connection to be released.
  • the VNFM that allows the connection to be released also successfully releases the connection with the VIM.
  • the method may include:
  • the VIM determines that the number of the multiple VNFMs reaches a preset threshold.
  • the VIM sends a connection release request message to the management node, where the connection release request message is used to request the management node to determine the VNFM that is allowed to release the connection.
  • the management node determines, according to the connection release request message, a VNFM that is allowed to release the connection from the plurality of VNFMs.
  • the management node sends a first connection release notification message to the VIM, where the first connection release notification message carries the identifier of the VNFM that allows the connection to be released.
  • the VIM After receiving the first connection release notification message, the VIM determines, according to the identifier of the VNFM that is allowed to release the connection, the VNFM that is allowed to release the connection.
  • the specific implementation manners of the foregoing S901-S905 are the same as the specific implementation manners of the S801-S805 in the embodiment shown in FIG. 9.
  • the specific implementation manner of the foregoing S901-S905 refer to the related embodiments in the embodiment shown in FIG. Description, no longer repeat here.
  • the VIM deletes the information of the VNFM that is allowed to release the connection saved in the VIM.
  • the VIM successfully releases the connection of the VIM to the VNFM that is allowed to release the connection.
  • the management node sends a second connection release notification message to the VNFM that is allowed to release the connection, where the second connection release notification message carries the identifier of the VIM.
  • the management node may directly directly release the VNFM to the connection.
  • Send the second connection release Knowing the message to notify the VNFM that is allowed to release the connection also deletes the information that holds the VIM.
  • the VNFM that is allowed to release the connection determines the VIM according to the identifier of the VIM.
  • the VNFM that allows the connection to be released deletes the information of the VIM saved in the VNFM that allows the connection to be released.
  • the VNFM that allows the connection to be released also successfully releases the connection with the VIM.
  • the VIM and the VNFM that are allowed to release the connection may further send an acknowledgement message to the management node, to The management node is determined that the connection between the VIM and the VNFM that is allowed to release the connection has been successfully released, and the management node can update the resource mapping table.
  • the method for releasing a connection causes the VIM to send the number of the multiple VNFMs that have established a connection with the management node after determining that the number of the multiple VNFMs that have established a connection with the preset threshold is reached.
  • a connection release request message is requested to request the management node to determine from the plurality of VNFMs a VNFM that allows the connection to be released.
  • the management node After the management node determines from the plurality of VNFMs that the VNFM is allowed to release the connection, the management node notifies the VIM and the VNFM that is allowed to release the connection to release the connection between the VIM and the VNFM that allows the connection to be released, thereby saving the VIM and The VIMM connection resource is allowed to be released, and when another VNFM that has not established a connection with the VIM requests the VIM to allocate resources for the VNF managed by the other VNFM, the VIM has idle connection resources to establish with the other A connection between VNFMs to enable the VIM to allocate resources for the VNF.
  • An embodiment of the present invention provides a method for releasing a connection, where the first node determines, from a plurality of second nodes, a second node that is allowed to release the connection, and deletes information of the second node that is saved in the first node and allows the connection to be released.
  • the plurality of second nodes are already A node that establishes a connection with the first node.
  • the first node releases the connection between the second node that is allowed to release the connection, to save the connection resource of the first node, so that the first node has an idle connection resource to establish a relationship with the other second node.
  • a new connection which in turn enables the first node to communicate with the other second node.
  • an embodiment of the present invention provides a device for releasing a connection, which may be in the embodiment shown in FIG. 2 or as shown in any of FIGS. 4 to 10 .
  • the physical device of the first node may also be a physical device in the NFV system, where a logical function module capable of executing the method flow that the first node can execute, where the physical device can be independently installed on the first node Within the physical device, it may also be a physical device capable of communicating with the physical device of the first node.
  • the apparatus can also be presented in the form of a chip carrying an application capable of implementing a method flow that the first node can execute.
  • the means for releasing the connection may include:
  • the determining unit 10 is configured to determine, from the plurality of second nodes, a second node that allows the connection to be released, the plurality of second nodes being nodes that have established a connection with the first node.
  • the deleting unit 11 is configured to delete information about the second node that is allowed to release the connection determined by the determining unit 10 saved in the first node.
  • the determining unit 10 is configured to receive, by the management node, a first connection release notification message, where the first connection release notification message carries an identifier of the second node that is allowed to release the connection.
  • the determining unit 10 is specifically configured to determine, according to the identifier of the second node that is allowed to release the connection, the second node that is allowed to release the connection.
  • the device for releasing the connection further includes a transmitting unit 12.
  • the sending unit 12 is configured to send a connection release request message to the management node before the determining unit 10 receives the first connection release notification message sent by the management node, where the connection release request message is used to request the management
  • the node determines the second node that is allowed to release the connection.
  • the first node is a VNFM, and the multiple second nodes are multiple VIMs; or the first node is a VIM, and the multiple second nodes are multiple VNFMs.
  • the first node is a VNFM
  • the multiple second nodes are multiple VIMs.
  • the second node that is determined to be released by the determining unit 10 is that the VNFM has no resource management in the multiple VIMs.
  • the relationship of VIM is that the VNFM has no resource management in the multiple VIMs.
  • the second node that is determined to be released by the determining unit 10 is the first VIM that satisfies the first condition.
  • the first condition is that the first VIM of the multiple VIMs allocates resources for the VNF managed by the VNFM, and allows the VNF to be allocated by the other VIM of the multiple VIMs.
  • the sending unit 12 is further configured to: after the determining unit 10 determines, from the plurality of second nodes, the second node that is allowed to release the connection, the deleting unit 11 deletes the saved in the first node.
  • the second connection release notification message is sent to the second node that is allowed to release the connection, where the second connection release notification message carries the identifier of the first node, where The second connection release notification message is used to notify the second node that is allowed to release the connection, and delete the information of the first node indicated by the identifier of the first node saved in the second node that allows the connection to be released.
  • An embodiment of the present invention provides a device for releasing a connection, which is capable of determining, from a plurality of second nodes, a second node that is allowed to release the connection, and deleting information of the second node that is allowed to release the connection saved in the first node, where
  • the plurality of second nodes are nodes that have established a connection with the first node.
  • the first node can release the connection between the second node that is allowed to release the connection, so as to save the connection resource of the first node, so that the first node has idle connection resources to establish and other A new connection between the second nodes, thereby enabling the first node to communicate with the other second node.
  • an embodiment of the present invention provides a device for releasing a connection, which may be as shown in any of FIG. 3 to FIG. 7 or as shown in FIG. 9 to FIG. 10 .
  • the physical device of the management node described in the embodiment may also be a physical device in the NFV system capable of executing a logical function module of the method flow that the management node can execute, and the physical device may be independently installed on the management node. Within the physical device, it may also be a physical device capable of communicating with the physical device of the management node.
  • the apparatus can also be presented in the form of a chip carrying an application capable of implementing a method flow that the management node can execute.
  • the means for releasing the connection may include:
  • the determining unit 20 is configured to determine, from the plurality of second nodes, a second node that is allowed to release the connection, where the plurality of second nodes are nodes that have established a connection with the first node.
  • the sending unit 21 is configured to send, to the first node, a first connection release notification message, where the first connection release notification message carries an identifier of the second node that is allowed to release the connection determined by the determining unit 20, where The first connection release notification message is used to notify the first node to delete the information of the second node that is allowed to release the connection saved in the first node.
  • the second node that is determined to be released by the determining unit 20 is the multiple A second node in the second node that has no resource management relationship with the first node.
  • the device for releasing the connection further includes a receiving unit 22.
  • the receiving unit 22 is configured to receive, after the determining unit 20 determines, from the plurality of second nodes, the connection release request message sent by the first node, the connection release request message And configured to request the determining unit to determine the second node that is allowed to release the connection.
  • the determining unit 20 is specifically configured to determine, according to the connection release request message received by the receiving unit 22, a second node that is allowed to release the connection from the plurality of second nodes.
  • the first node is a VNFM, and the multiple second nodes are multiple VIMs; or the first node is a VIM, and the multiple second nodes are multiple VNFMs.
  • the first node is a VNFM
  • the multiple second nodes are multiple VIMs.
  • the second node that is determined to be released by the determining unit 20 is the first VIM that satisfies the first condition.
  • the first condition is that the first VIM of the multiple VIMs allocates resources for the VNF managed by the VNFM, and allows the VNF to be allocated by the other VIM of the multiple VIMs.
  • the first node is a VIM
  • the multiple second nodes are multiple VNFMs.
  • the second node that is determined to be released by the determining unit 20 is the first VNFM that satisfies the second condition.
  • the second condition is that the VIM allocates resources for a VNF managed by a first one of the plurality of VNFMs, and allows the VNF to be allocated by another VIM that has established a connection with the first VNFM. .
  • the sending unit 21 is further configured to: after the determining unit 20 determines, from the plurality of second nodes, the second node that is allowed to release the connection, send the second connection to the second node that is allowed to release the connection. Release a notification message, where the second connection release notification message carries the identifier of the first node, and the second connection release notification message is used to notify the second node that is allowed to release the connection, and delete the release-allowed connection. Information of the first node indicated by the identifier of the first node saved in the second node.
  • An embodiment of the present invention provides a device for releasing a connection, which is capable of determining, from a plurality of second nodes, a second node that is allowed to release the connection, and sending a first connection release notification message to the first node, where the first connection release notification message is Carrying an identifier of the second node that is allowed to release the connection, the first connection release notification message is used to notify the first node, deleting information of the second node saved in the first node that is allowed to release the connection, where the plurality of second nodes are A node that has established a connection with the first node.
  • the management node can select a suitable second node among the plurality of second nodes that have established a connection with the first node, and notify the first node to release the second node in time. Interconnection to save connection resources of the first node, so that the first node has idle connection resources to establish a new connection with other second nodes, thereby enabling the first node to perform with the other second node Communication.
  • an embodiment of the present invention provides a device for releasing a connection, where the device for releasing a connection may be a physical device where the first node is located in the foregoing embodiment, or may be A physical device in which a physical device in which a node is located communicates.
  • the device for releasing the connection is capable of executing a method flow that the first node can execute.
  • the device for releasing the connection may include: a processor 30, a memory 31, a communication interface 32, and a system bus 33.
  • the processor 30, the memory 31, and the communication interface 32 are connected by the system bus 33 and complete communication with each other.
  • the processor 30 may be a central processing unit (English: central processing unit, abbreviated as CPU), or an application specific integrated circuit (ASIC), or configured to implement the implementation of the present invention.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • the memory 31 may include a volatile memory (English: volatile memory), such as a random access memory (English: random-access memory, abbreviation: RAM); the memory 31 may also include a non-volatile memory (English: Non-volatile memory, such as read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviation: HDD) or solid state drive (English) : solid-state drive, abbreviated: SSD); the memory 31 may also include a combination of the above types of memories.
  • a volatile memory such as a random access memory (English: random-access memory, abbreviation: RAM)
  • the memory 31 may also include a non-volatile memory (English: Non-volatile memory, such as read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviation: HDD) or solid state drive (English)
  • the communication interface 32 is configured to interact with other nodes, for example, with a function node such as a second node or a management node.
  • the processor 30 and the memory 31 may perform the method flow described in FIG. 2 or any one of FIG. 4 to FIG. 10, specifically including:
  • the processor 30 is configured to determine, from a plurality of second nodes, a second node that is allowed to release the connection, and delete information about the second node that is allowed to release the connection saved in the first node, where the multiple The second node is a node that has established a connection with the first node; the memory 31 is configured to store a code of the information of the second node that allows the connection to be released, and a software program that controls the processor 30 to complete the above process, The processor 30 thus completes the above process by executing the software program and invoking the code that allows the information of the connected second node to be released.
  • the processor 30 is configured to receive a first connection release notification message sent by the management node, where the first connection release notification message carries an identifier of the second node that is allowed to release the connection.
  • the processor 30 is specifically configured to determine, according to the identifier of the second node that is allowed to release the connection, the second node that is allowed to release the connection.
  • the processor 30 is further configured to: before receiving the first connection release notification message sent by the management node, send a connection release request message to the management node, where the connection release request message is used to request the management The node determines the second node that is allowed to release the connection.
  • the first node is a VNFM
  • the multiple second nodes are multiple virtual machine infrastructure management nodes VIM; or the first node is a VIM, and the multiple second nodes are multiple VNFM.
  • the first node is a VNFM
  • the multiple second nodes are multiple VIMs.
  • the second node that is determined by the processor 30 to release the connection is that the VNFM has no resource management in the multiple VIMs.
  • the relationship of VIM is that the VNFM has no resource management in the multiple VIMs.
  • the second node that is allowed to release the connection determined by the processor 30 The first VIM to satisfy the first condition.
  • the first condition is that the first VIM of the multiple VIMs allocates resources for the virtual network function VNF managed by the VNFM, and allows the VNF to be allocated by the other VIM of the multiple VIMs. .
  • the processor 30 is further configured to: after determining, from the plurality of second nodes, the second node that is allowed to release the connection, deleting the second node of the allow release connection saved in the first node Before the information, the second connection release notification message is sent to the second node that is allowed to release the connection, where the second connection release notification message carries the identifier of the first node, and the second connection release notification message is used to notify The second node that is allowed to release the connection deletes the information of the first node indicated by the identifier of the first node saved in the second node that is allowed to release the connection.
  • An embodiment of the present invention provides a device for releasing a connection, which is capable of determining, from a plurality of second nodes, a second node that is allowed to release the connection, and deleting information of the second node that is allowed to release the connection saved in the first node, where
  • the plurality of second nodes are nodes that have established a connection with the first node.
  • the first node can release the connection between the second node that is allowed to release the connection, so as to save the connection resource of the first node, so that the first node has idle connection resources to establish and other A new connection between the second nodes, thereby enabling the first node to communicate with the other second node.
  • an embodiment of the present invention provides a device for releasing a connection, where the device for releasing a connection may be a physical device where a management node is located in the foregoing embodiment, or may be capable of interacting with the management node.
  • the device for releasing the connection is capable of executing a method flow that the management node can execute.
  • the device for releasing the connection may include: a processor 40, a memory 41, a communication interface 42, and a system bus 43.
  • the processor 40, the memory 41, and the communication interface 42 are connected by the system bus 43 and complete communication with each other.
  • the processor 40 can be a CPU, or an ASIC, or one or more integrated circuits configured to implement embodiments of the present invention.
  • the memory 41 may include a volatile memory such as a RAM; the memory 41 may also include a non-volatile memory such as a ROM, a flash memory, an HDD or an SSD; the memory 41 may also include a memory of the above kind combination.
  • a volatile memory such as a RAM
  • the memory 41 may also include a non-volatile memory such as a ROM, a flash memory, an HDD or an SSD
  • the memory 41 may also include a memory of the above kind combination.
  • the communication interface 42 is used to interact with other nodes, for example, with functional nodes such as the first node.
  • the processor 40 and the memory 41 may perform the method flow described in any one of FIG. 3 to FIG. 7 or FIG. 9 to FIG. 10, and specifically includes:
  • the processor 40 is configured to determine, from the plurality of second nodes, a second node that is allowed to release the connection, and send a first connection release notification message to the first node, where the first connection release notification message carries the permission And releasing the identifier of the connected second node, where the first connection release notification message is used to notify the first node, deleting information about the second node that is allowed to release the connection saved in the first node, where the information is
  • the second node is a node that has established a connection with the first node; the memory 41 is configured to store a code of the first connection release notification message, a code of the identifier of the second node that allows the connection to be released, and control
  • the processor 40 completes the software program of the above process, so that the processor 40 executes the software program and invokes the code of the first connection release notification message, the code of the identifier of the second node that allows the connection to be released. To complete the above process.
  • the second node that is determined by the processor 40 to allow the connection to be released is the multiple A second node in the second node that has no resource management relationship with the first node.
  • the processor 40 is further configured to: before the determining unit determines, from the plurality of second nodes, the connection release request message sent by the first node, The connection release request message is used to request the determining unit to determine the second node that is allowed to release the connection.
  • the processor 40 is specifically configured to determine, according to the connection release request message, a second node that is allowed to release the connection from the plurality of second nodes.
  • the first node is a VNFM, and the multiple second nodes are multiple VIMs; or the first node is a VIM, and the multiple second nodes are multiple VNFMs.
  • the first node is a VNFM
  • the multiple second nodes are multiple VIMs.
  • the second node that is determined by the processor 40 to allow the connection to be released is the first VIM that satisfies the first condition.
  • the first condition is that the first VIM of the multiple VIMs allocates resources for the virtual network function VNF managed by the VNFM, and allows the VNF to be allocated by the other VIM of the multiple VIMs. .
  • the first node is a VIM
  • the multiple second nodes are multiple VNFMs.
  • the second node that is determined by the processor 40 to allow the connection to be released is the first VNFM that satisfies the second condition.
  • the second condition is that the VIM allocates resources for a VNF managed by a first one of the plurality of VNFMs, and allows the VNF to be allocated by another VIM that has established a connection with the first VNFM. .
  • the processor 40 is further configured to: after determining, from the plurality of second nodes, the second node that is allowed to release the connection, send a second connection release notification message to the second node that is allowed to release the connection, where
  • the second connection release notification message carries the identifier of the first node, where the second connection release notification message is used to notify the second node that is allowed to release the connection, and deletes the second node that is allowed to release the connection.
  • the identifier of the first node indicates the information of the first node.
  • An embodiment of the present invention provides a device for releasing a connection, which is capable of determining, from a plurality of second nodes, a second node that is allowed to release the connection, and sending a first connection release notification message to the first node, where the first connection release notification message is Carrying an identifier of the second node that is allowed to release the connection, the first connection release notification message is used to notify the first node, deleting information of the second node saved in the first node that is allowed to release the connection, where the plurality of second nodes are A node that has established a connection with the first node.
  • the management node can select a suitable second node among the plurality of second nodes that have established a connection with the first node, and notify the first node to release the second node in time. Interconnection to save connection resources of the first node, so that the first node has idle connection resources to establish a new connection with other second nodes, thereby enabling the first node to perform with the other second node Communication.
  • the embodiment of the present invention provides a communication system, which may include a device for releasing a connection as shown in FIG. 11 or as shown in FIG. 12, and a device for releasing a connection as shown in FIG. 13 or FIG. And the second node; or, the communication system may include a device for releasing the connection as shown in FIG. 15, a device for releasing the connection as shown in FIG. 16, and a second node.
  • the device for releasing the connection as shown in FIG. 11, the device for releasing the connection as shown in FIG. 12, and the device for releasing the connection as shown in FIG. 15 may be referred to as a first node; as shown in FIG.
  • the device that releases the connection, the device that releases the connection as shown in FIG. 14, and the device that releases the connection as shown in FIG. 16 may be referred to as a management node.
  • the first node in the communication system is capable of determining, from the plurality of second nodes, the second node that is allowed to release the connection, and deleting the information of the second node that is saved in the first node and allowing the connection to be released;
  • the node is configured to determine, from the plurality of second nodes, the second node that is allowed to release the connection, and send a first connection release notification message to the first node, where the first connection release notification message carries an identifier of the second node that allows the connection to be released,
  • the first connection release notification message is used to notify the first node to delete the information of the second node saved in the first node that allows the connection to be released.
  • the plurality of second nodes are nodes that have established a connection with the first node.
  • the first node may be a VNFM or a VIM.
  • the second node is a VIM, and the VIM has established a connection with the VNFM;
  • the first node is a VIM, the second node is a VNFM, and the VNFM has established with the VIM. connection.
  • the first node in the communication system provided by the embodiment of the present invention can perform the method for releasing the connection as described in any one of FIG. 2 to FIG. 10, and the pair of nodes in the first node
  • the specific functions of the module or device and the flow of the execution method can be referred to the description in the embodiment shown in any one of FIG. 2 to FIG. 10, and details are not described herein again.
  • the management node in the communication system provided by the embodiment of the present invention can perform the method for releasing the connection as shown in any one of FIG. 3 to FIG. 7 or FIG. 9 to FIG. 10, in the pair of management nodes.
  • the specific function of each module or device and the flow of the method for performing the method can be referred to the description in the embodiment shown in any one of FIG. 3 to FIG. 7 or FIG. 9 to FIG. 10, and details are not described herein again.
  • the management node can select a suitable second node among the plurality of second nodes that have established a connection with the first node, and notify the first node to release the relationship with the second node in time.
  • the connection is saved to save the connection resources of the first node, so that the first node has idle connection resources to establish a new connection with other second nodes, thereby enabling the first node to communicate with the other second nodes.
  • the disclosed system, apparatus, and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the modules or units is only a logical function division.
  • there may be another division manner for example, multiple units or components may be used. Combinations can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication through some interface, device or unit. Connections can be in electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • the technical solution of the present invention which is essential or contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product stored in a storage medium.
  • a number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read only memory (English full name: Read-Only Memory, English abbreviation: ROM), a random access memory (English full name: Random Access Memory, English abbreviation: RAM), magnetic A variety of media that can store program code, such as a disc or a disc.

Landscapes

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

Abstract

L'invention concerne un procédé, un dispositif et un système de libération de connexion, qui concernent le domaine technique des communications et peuvent permettre à un nœud de libérer de manière raisonnable une connexion qui a été établie entre celui-ci et d'autres nœuds. Le procédé comprend les étapes suivantes : un premier nœud détermine, à partir d'une pluralité de seconds nœuds, un second nœud qui est autorisé à libérer une connexion et efface des informations concernant le second nœud qui est autorisé à libérer une connexion stockées dans le premier nœud, la pluralité de seconds nœuds étant des nœuds qui ont établi une connexion avec le premier nœud. Le procédé s'applique à un système NFV.
PCT/CN2015/081398 2015-06-12 2015-06-12 Procédé, dispositif et système de libération de connexion WO2016197395A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201580080506.0A CN107615872B (zh) 2015-06-12 2015-06-12 一种释放连接的方法、装置及系统
PCT/CN2015/081398 WO2016197395A1 (fr) 2015-06-12 2015-06-12 Procédé, dispositif et système de libération de connexion

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/081398 WO2016197395A1 (fr) 2015-06-12 2015-06-12 Procédé, dispositif et système de libération de connexion

Publications (1)

Publication Number Publication Date
WO2016197395A1 true WO2016197395A1 (fr) 2016-12-15

Family

ID=57503150

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/081398 WO2016197395A1 (fr) 2015-06-12 2015-06-12 Procédé, dispositif et système de libération de connexion

Country Status (2)

Country Link
CN (1) CN107615872B (fr)
WO (1) WO2016197395A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112000429A (zh) * 2020-08-06 2020-11-27 北京浪潮数据技术有限公司 一种云平台管理平台的连接跟踪删除方法、装置及设备
CN113453360B (zh) * 2021-06-22 2022-11-22 联想(北京)有限公司 一种数据传输方法和装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090133115A1 (en) * 2007-11-19 2009-05-21 Heninger Ivan M VPN Management
CN101854734A (zh) * 2009-03-30 2010-10-06 华为技术有限公司 释放接入连接的方法、装置、策略控制实体及系统
WO2011054149A1 (fr) * 2009-11-06 2011-05-12 华为技术有限公司 Procédé, dispositif et système de communication pour la régulation de charge

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4562081B2 (ja) * 2005-02-09 2010-10-13 Ｋｄｄｉ株式会社 光クロスコネクト装置と伝送装置の連係方式
WO2013064170A1 (fr) * 2011-10-31 2013-05-10 Telefonaktiebolaget L M Ericsson (Publ) Recherche et déconnexion d'adresses clients dans un nœud d'accès pour un réseau ip
CN104349387B (zh) * 2013-08-08 2018-08-14 上海诺基亚贝尔股份有限公司 在支持双/多连接的系统中用于下行链路传输的方法和设备
CN104410672B (zh) * 2014-11-12 2017-11-24 华为技术有限公司 网络功能虚拟化应用升级的方法、转发业务的方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090133115A1 (en) * 2007-11-19 2009-05-21 Heninger Ivan M VPN Management
CN101854734A (zh) * 2009-03-30 2010-10-06 华为技术有限公司 释放接入连接的方法、装置、策略控制实体及系统
WO2011054149A1 (fr) * 2009-11-06 2011-05-12 华为技术有限公司 Procédé, dispositif et système de communication pour la régulation de charge

Also Published As

Publication number Publication date
CN107615872B (zh) 2020-06-26
CN107615872A (zh) 2018-01-19

Similar Documents

Publication Publication Date Title
RU2681371C1 (ru) Система и способ управления ресурсами
US10701139B2 (en) Life cycle management method and apparatus
EP3468151B1 (fr) Procédé et appareil de traitement de ressources d'accélération
EP3119034B1 (fr) Procédé, dispositif et système de traitement de défauts sur la base d'une virtualisation d'une fonction de réseau
WO2017054197A1 (fr) Procédé, dispositif et système de mise à l'échelle
CN110221918B (zh) 一种ns与vnf的关联方法、装置及系统
WO2016123794A1 (fr) Procédé, dispositif et système de détermination de politique de traitement de vnf
EP3470984B1 (fr) Procédé, dispositif et système de gestion d'un verrou de disque
WO2017148249A1 (fr) Procédé de configuration de ressource et dispositif de réseau l'utilisant
WO2018036103A1 (fr) Procédé et système de création d'une machine virtuelle et ordinateur hôte
WO2018171392A1 (fr) Procédé d'expansion et de réduction de capacité de machine virtuelle et dispositif de gestion virtuelle
EP3160084A1 (fr) Procédé et appareil de configuration de réseau dédié au stockage "fiber channel"
WO2016082078A1 (fr) Système, dispositif et procédé de gestion de trajet
WO2016155291A1 (fr) Procédé et appareil de gestion de mise à l'échelle de fonction de réseau virtualisé
US9917740B2 (en) Reducing internodal communications in a clustered system
WO2019001140A1 (fr) Procédé et dispositif de gestion d'instanciation de fonction de réseau virtualisée
WO2016197395A1 (fr) Procédé, dispositif et système de libération de connexion
WO2017041650A1 (fr) Procédé et dispositif d'extension de service de cohérence distribué
WO2016179803A1 (fr) Procédé, dispositif et système d'établissement de connexion entre vnfm et vim
WO2017070963A1 (fr) Procédé, appareil et système pour déployer des ressources virtuelles
WO2018196651A1 (fr) Procédé et dispositif de gestion de ressources
WO2016192102A1 (fr) Procédé, appareil et dispositif de communication de groupe
WO2016107135A1 (fr) Procédé et système de gestion de mémoire et support d'enregistrement d'ordinateur

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15894664

Country of ref document: EP

Kind code of ref document: A1