[go: up one dir, main page]

WO2016197395A1 - 一种释放连接的方法、装置及系统 - Google Patents

一种释放连接的方法、装置及系统 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)
French (fr)
Inventor
季莉
周彦
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2015/081398 priority Critical patent/WO2016197395A1/zh
Priority to CN201580080506.0A priority patent/CN107615872B/zh
Publication of WO2016197395A1 publication Critical patent/WO2016197395A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/30Connection 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

本发明实施例提供一种释放连接的方法、装置及系统,涉及通信技术领域,能够使得节点合理地释放与其他节点之间已经建立的连接。该方法包括:第一节点从多个第二节点中确定允许释放连接的第二节点,并删除第一节点中保存的允许释放连接的第二节点的信息,其中,该多个第二节点为已经与第一节点建立连接的节点。该方法应用于NFV系统中。

Description

一种释放连接的方法、装置及系统 技术领域
本发明涉及通信技术领域,尤其涉及一种释放连接的方法、装置及系统。
背景技术
随着虚拟化技术的飞速发展,在通用的物理设备上,实现网络中专用的网元设备的功能的网络功能虚拟化(英文:network function virtualization,缩写:NFV)系统逐渐受到人们的重视。
在NFV系统中存在网络功能虚拟化调度节点(英文:network function virtualization orchestrator,缩写:NFVO)、虚拟机基础设施管理节点(英文:virtualized infrastructure manager,缩写:VIM)、虚拟网络功能管理节点(英文:virtualized network function manager,VNFM)以及虚拟网络功能(英文:virtualized network function,缩写:VNF)等功能节点。其中,VIM负责管理VNF所需的虚拟资源,VNFM负责管理VNF,NFVO负责对所有的VIM所管理的资源进行调度。当VNFM需要请求NFVO指定的VIM为该VNFM管理的VNF分配资源时,若该VNFM和该VIM之间还未建立连接,则该VNFM需先建立与该VIM之间的连接,从而由该VIM为该VNF分配资源。
然而,上述VNFM请求NFVO指定的VIM为该VNFM管理的VNF分配资源的过程中,由于能够与该VNFM建立连接的VIM的个数有限,因此当已经与该VNFM建立连接的VIM的个数达到能够与该VNFM建立连接的VIM的个数的门限值时,若该VNFM还未与NFVO指定的VIM之间建立连接,则会导致该VNFM由于没有空闲的连接资源,而无法建立与NFVO指定的VIM之间的连接,从而使得该VNFM无法请求NFVO指定的VIM为该VNF分配资源。
发明内容
本发明提供一种释放连接的方法、装置及系统,使得节点通过 合理地释放与其他节点之间已经建立的连接,以保证该节点具有空闲的连接资源来建立新的连接。
为达到上述目的,本发明采用如下技术方案:
第一方面,本发明提供一种释放连接的方法,包括:
第一节点从多个第二节点中确定允许释放连接的第二节点,所述多个第二节点为已经与所述第一节点建立连接的节点;
所述第一节点删除所述第一节点中保存的所述允许释放连接的第二节点的信息。
在第一方面的第一种可能的实现方式中,所述第一节点从多个第二节点中确定允许释放连接的第二节点,包括:
所述第一节点接收管理节点发送的第一连接释放通知消息,所述第一连接释放通知消息中携带所述允许释放连接的第二节点的标识:
所述第一节点根据所述允许释放连接的第二节点的标识,确定所述允许释放连接的第二节点。
结合第一方面的第一种可能的实现方式,在第二种可能的实现方式中,所述第一节点接收管理节点发送的第一连接释放通知消息之前,所述方法还包括:
所述第一节点向所述管理节点发送连接释放请求消息,所述连接释放请求消息用于请求所述管理节点确定所述允许释放连接的第二节点。
结合前述的第一方面或第一方面的第一种可能的实现方式至第一方面的第二种可能的实现方式中的任一种实现方式,在第三种可能的实现方式中,
所述第一节点为虚拟网络功能管理节点VNFM,所述多个第二节点为多个虚拟机基础设施管理节点VIM;或者,
所述第一节点为VIM,所述多个第二节点为多个VNFM。
结合前述的第一方面,在第四种可能的实现方式中,所述第一节点为VNFM,所述多个第二节点为多个VIM,
若所述多个VIM中存在与所述VNFM没有资源管理关系的VIM,则所述允许释放连接的第二节点为所述多个VIM中与所述VNFM没有资源管理关系的VIM;或者,
若所述多个VIM中不存在与所述VNFM没有资源管理关系的VIM,则所述允许释放连接的第二节点为满足第一条件的第一VIM,
其中,所述第一条件为所述多个VIM中的第一VIM为所述VNFM所管理的虚拟网络功能VNF分配的资源,允许由所述多个VIM中的另一个VIM为所述VNF分配。
结合前述的第一方面或第一方面的第一种可能的实现方式至第一方面的第四种可能的实现方式中的任一种实现方式,在第五种可能的实现方式中,所述第一节点从多个第二节点中确定允许释放连接的第二节点之后,所述第一节点删除所述第一节点中保存的所述允许释放连接的第二节点的信息之前,所述方法还包括:
所述第一节点向所述允许释放连接的第二节点发送第二连接释放通知消息,所述第二连接释放通知消息中携带所述第一节点的标识,所述第二连接释放通知消息用于通知所述允许释放连接的第二节点,删除所述允许释放连接的第二节点中保存的所述第一节点的标识指示的所述第一节点的信息。
第二方面,本发明提供一种释放连接的方法,包括:
管理节点从多个第二节点中确定允许释放连接的第二节点,所述多个第二节点为已经与第一节点建立连接的节点;
所述管理节点向所述第一节点发送第一连接释放通知消息,所述第一连接释放通知消息中携带所述允许释放连接的第二节点的标识,所述第一连接释放通知消息用于通知所述第一节点,删除所述第一节点中保存的所述允许释放连接的第二节点的信息。
在第二方面的第一种可能的实现方式中,
若所述多个第二节点中存在与所述第一节点没有资源管理关系的第二节点,则所述允许释放连接的第二节点为所述多个第二节点中与所述第一节点没有资源管理关系的第二节点。
结合前述的第二方面或第二方面的第一种可能的实现方式,在第二种可能的实现方式中,所述管理节点从多个第二节点中确定允许释放连接的第二节点之前,所述方法还包括:
所述管理节点接收所述第一节点发送的连接释放请求消息,所述连接释放请求消息用于请求所述管理节点确定所述允许释放连接的第二节点;
所述管理节点从多个第二节点中确定允许释放连接的第二节点,包括:
所述管理节点根据所述连接释放请求消息,从所述多个第二节点中确定所述允许释放连接的第二节点。
结合前述的第二方面或第二方面的第一种可能的实现方式至第二方面的第二种可能的实现方式中的任一种实现方式,在第三种可能的实现方式中,
所述第一节点为VNFM,所述多个第二节点为多个VIM;或者,
所述第一节点为VIM,所述多个第二节点为多个VNFM。
结合第二方面的第二种可能的实现方式,在第四种可能的实现方式中,所述第一节点为VNFM,所述多个第二节点为多个VIM,
若所述多个VIM中不存在与所述VNFM没有资源管理关系的VIM,则所述允许释放连接的第二节点为满足第一条件的第一VIM,
其中,所述第一条件为所述多个VIM中的第一VIM为所述VNFM所管理的虚拟网络功能VNF分配的资源,允许由所述多个VIM中的另一个VIM为所述VNF分配。
结合第二方面的第二种可能的实现方式,在第五种可能的实现方式中,所述第一节点为VIM,所述多个第二节点为多个VNFM,
若所述多个VNFM中不存在与所述VIM没有资源管理关系的VNFM,则所述允许释放连接的第二节点为满足第二条件的第一VNFM,
其中,所述第二条件为所述VIM为所述多个VNFM中的第一VNFM所管理的VNF分配的资源,允许由已经与所述第一VNFM建 立连接的另一个VIM为所述VNF分配。
结合前述的第二方面或第二方面的第一种可能的实现方式至第二方面的第五种可能的实现方式中的任一种实现方式,在第六种可能的实现方式中,所述管理节点从多个第二节点中确定允许释放连接的第二节点之后,所述方法还包括:
所述管理节点向所述允许释放连接的第二节点发送第二连接释放通知消息,所述第二连接释放通知消息中携带所述第一节点的标识,所述第二连接释放通知消息用于通知所述允许释放连接的第二节点,删除所述允许释放连接的第二节点中保存的所述第一节点的标识指示的所述第一节点的信息。
第三方面,本发明提供一种释放连接的装置,包括:
确定单元,用于从多个第二节点中确定允许释放连接的第二节点,所述多个第二节点为已经与第一节点建立连接的节点;
删除单元,用于删除所述第一节点中保存的所述确定单元确定的所述允许释放连接的第二节点的信息。
在第三方面的第一种可能的实现方式中,
所述确定单元,具体用于接收管理节点发送的第一连接释放通知消息,所述第一连接释放通知消息中携带所述允许释放连接的第二节点的标识;
所述确定单元,具体用于根据所述允许释放连接的第二节点的标识,确定所述允许释放连接的第二节点。
结合第三方面的第一种可能的实现方式,在第二种可能的实现方式中,所述释放连接的装置还包括发送单元,
所述发送单元,用于在所述确定单元接收管理节点发送的第一连接释放通知消息之前,向所述管理节点发送连接释放请求消息,所述连接释放请求消息用于请求所述管理节点确定所述允许释放连接的第二节点。
结合前述的第三方面或第三方面的第一种可能的实现方式至第三方面的第二种可能的实现方式中的任一种实现方式,在第三种可 能的实现方式中,
所述第一节点为VNFM,所述多个第二节点为多个VIM;或者,
所述第一节点为VIM,所述多个第二节点为多个VNFM。
结合前述的第三方面,在第四种可能的实现方式中,所述第一节点为VNFM,所述多个第二节点为多个VIM,
若所述多个VIM中存在与所述VNFM没有资源管理关系的VIM,则所述确定单元确定的所述允许释放连接的第二节点为所述多个VIM中与所述VNFM没有资源管理关系的VIM;或者,
若所述多个VIM中不存在与所述VNFM没有资源管理关系的VIM,则所述确定单元确定的所述允许释放连接的第二节点为满足第一条件的第一VIM,
其中,所述第一条件为所述多个VIM中的第一VIM为所述VNFM所管理的VNF分配的资源,允许由所述多个VIM中的另一个VIM为所述VNF分配。
结合前述的第三方面的第二种可能的实现方式至第三方面的第四种可能的实现方式中的任一种实现方式,在第五种可能的实现方式中,
所述发送单元,还用于在所述确定单元从多个第二节点中确定允许释放连接的第二节点之后,所述删除单元删除所述第一节点中保存的所述允许释放连接的第二节点的信息之前,向所述允许释放连接的第二节点发送第二连接释放通知消息,所述第二连接释放通知消息中携带所述第一节点的标识,所述第二连接释放通知消息用于通知所述允许释放连接的第二节点,删除所述允许释放连接的第二节点中保存的所述第一节点的标识指示的所述第一节点的信息。
第四方面,本发明提供一种释放连接的装置,包括:
确定单元,用于从多个第二节点中确定允许释放连接的第二节点,所述多个第二节点为已经与第一节点建立连接的节点;
发送单元,用于向所述第一节点发送第一连接释放通知消息,所述第一连接释放通知消息中携带所述确定单元确定的所述允许释 放连接的第二节点的标识,所述第一连接释放通知消息用于通知所述第一节点,删除所述第一节点中保存的所述允许释放连接的第二节点的信息。
在第四方面的第一种可能的实现方式中,
若所述多个第二节点中存在与所述第一节点没有资源管理关系的第二节点,则所述确定单元确定的所述允许释放连接的第二节点为所述多个第二节点中与所述第一节点没有资源管理关系的第二节点。
结合前述的第四方面或第四方面的第一种可能的实现方式,在第二种可能的实现方式中,所述释放连接的装置还包括接收单元,
所述接收单元,用于在所述确定单元从多个第二节点中确定允许释放连接的第二节点之前,接收所述第一节点发送的连接释放请求消息,所述连接释放请求消息用于请求所述确定单元确定所述允许释放连接的第二节点;
所述确定单元,具体用于根据所述接收单元接收的所述连接释放请求消息,从多个第二节点中确定允许释放连接的第二节点。
结合前述的第四方面或第四方面的第一种可能的实现方式至第四方面的第二种可能的实现方式中的任一种实现方式,在第三种可能的实现方式中,
所述第一节点为VNFM,所述多个第二节点为多个VIM;或者,
所述第一节点为VIM,所述多个第二节点为多个VNFM。
结合第四方面的第二种可能的实现方式,在第四种可能的实现方式中,所述第一节点为VNFM,所述多个第二节点为多个VIM,
若所述多个VIM中不存在与所述VNFM没有资源管理关系的VIM,则所述确定单元确定的所述允许释放连接的第二节点为满足第一条件的第一VIM,
其中,所述第一条件为所述多个VIM中的第一VIM为所述VNFM所管理的VNF分配的资源,允许由所述多个VIM中的另一个VIM为所述VNF分配。
结合第四方面的第二种可能的实现方式,在第五种可能的实现方式中,所述第一节点为VIM,所述多个第二节点为多个VNFM,
若所述多个VNFM中不存在与所述VIM没有资源管理关系的VNFM,则所述确定单元确定的所述允许释放连接的第二节点为满足第二条件的第一VNFM,
其中,所述第二条件为所述VIM为所述多个VNFM中的第一VNFM所管理的VNF分配的资源,允许由已经与所述第一VNFM建立连接的另一个VIM为所述VNF分配。
结合前述的第四方面或第四方面的第一种可能的实现方式至第四方面的第五种可能的实现方式中的任一种实现方式,在第六种可能的实现方式中,
所述发送单元,还用于在所述确定单元从多个第二节点中确定允许释放连接的第二节点之后,向所述允许释放连接的第二节点发送第二连接释放通知消息,所述第二连接释放通知消息中携带所述第一节点的标识,所述第二连接释放通知消息用于通知所述允许释放连接的第二节点,删除所述允许释放连接的第二节点中保存的所述第一节点的标识指示的所述第一节点的信息。
第五方面,本发明提供一种释放连接的装置,包括:
处理器,用于从多个第二节点中确定允许释放连接的第二节点,所述多个第二节点为已经与第一节点建立连接的节点;
所述处理器,还用于删除所述第一节点中保存的所述允许释放连接的第二节点的信息。
在第五方面的第一种可能的实现方式中,
所述处理器,具体用于接收管理节点发送的第一连接释放通知消息,所述第一连接释放通知消息中携带所述允许释放连接的第二节点的标识;
所述处理器,具体用于根据所述允许释放连接的第二节点的标识,确定所述允许释放连接的第二节点。
结合第五方面的第一种可能的实现方式,在第二种可能的实现 方式中,
所述处理器,还用于在接收管理节点发送的第一连接释放通知消息之前,向所述管理节点发送连接释放请求消息,所述连接释放请求消息用于请求所述管理节点确定所述允许释放连接的第二节点。
结合前述的第五方面或第五方面的第一种可能的实现方式至第五方面的第二种可能的实现方式中的任一种实现方式,在第三种可能的实现方式中,
所述第一节点为虚拟网络功能管理节点VNFM,所述多个第二节点为多个虚拟机基础设施管理节点VIM;或者,
所述第一节点为VIM,所述多个第二节点为多个VNFM。
结合前述的第五方面,在第四种可能的实现方式中,所述第一节点为VNFM,所述多个第二节点为多个VIM,
若所述多个VIM中存在与所述VNFM没有资源管理关系的VIM,则所述处理器确定的所述允许释放连接的第二节点为所述多个VIM中与所述VNFM没有资源管理关系的VIM;或者,
若所述多个VIM中不存在与所述VNFM没有资源管理关系的VIM,则所述处理器确定的所述允许释放连接的第二节点为满足第一条件的第一VIM,
其中,所述第一条件为所述多个VIM中的第一VIM为所述VNFM所管理的虚拟网络功能VNF分配的资源,允许由所述多个VIM中的另一个VIM为所述VNF分配。
结合前述的第五方面或第五方面的第一种可能的实现方式至第五方面的第四种可能的实现方式中的任一种实现方式,在第五种可能的实现方式中,
所述处理器,还用于在从多个第二节点中确定允许释放连接的第二节点之后,删除所述第一节点中保存的所述允许释放连接的第二节点的信息之前,向所述允许释放连接的第二节点发送第二连接释放通知消息,所述第二连接释放通知消息中携带所述第一节点的 标识,所述第二连接释放通知消息用于通知所述允许释放连接的第二节点,删除所述允许释放连接的第二节点中保存的所述第一节点的标识指示的所述第一节点的信息。
第六方面,本发明提供一种释放连接的装置,包括:
处理器,用于从多个第二节点中确定允许释放连接的第二节点,所述多个第二节点为已经与第一节点建立连接的节点;
所述处理器,还用于向所述第一节点发送第一连接释放通知消息,所述第一连接释放通知消息中携带所述允许释放连接的第二节点的标识,所述第一连接释放通知消息用于通知所述第一节点,删除所述第一节点中保存的所述允许释放连接的第二节点的信息。
在第六方面的第一种可能的实现方式中,
若所述多个第二节点中存在与所述第一节点没有资源管理关系的第二节点,则所述处理器确定的所述允许释放连接的第二节点为所述多个第二节点中与所述第一节点没有资源管理关系的第二节点。
结合前述的第六方面或第六方面的第一种可能的实现方式,在第二种可能的实现方式中,
所述处理器,还用于在所述确定单元从多个第二节点中确定允许释放连接的第二节点之前,接收所述第一节点发送的连接释放请求消息,所述连接释放请求消息用于请求所述确定单元确定所述允许释放连接的第二节点;
所述处理器,具体用于根据所述连接释放请求消息,从多个第二节点中确定允许释放连接的第二节点。
结合前述的第六方面或第六方面的第一种可能的实现方式至第六方面的第二种可能的实现方式中的任一种实现方式,在第三种可能的实现方式中,所述第一节点为VNFM,所述多个第二节点为多个VIM;或者,
所述第一节点为VIM,所述多个第二节点为多个VNFM。
结合第六方面的第二种可能的实现方式,在第四种可能的实现 方式中,所述第一节点为VNFM,所述多个第二节点为多个VIM,
若所述多个VIM中不存在与所述VNFM没有资源管理关系的VIM,则所述处理器确定的所述允许释放连接的第二节点为满足第一条件的第一VIM,
其中,所述第一条件为所述多个VIM中的第一VIM为所述VNFM所管理的虚拟网络功能VNF分配的资源,允许由所述多个VIM中的另一个VIM为所述VNF分配。
结合第六方面的第二种可能的实现方式,在第五种可能的实现方式中,所述第一节点为VIM,所述多个第二节点为多个VNFM,
若所述多个VNFM中不存在与所述VIM没有资源管理关系的VNFM,则所述处理器确定的所述允许释放连接的第二节点为满足第二条件的第一VNFM,
其中,所述第二条件为所述VIM为所述多个VNFM中的第一VNFM所管理的VNF分配的资源,允许由已经与所述第一VNFM建立连接的另一个VIM为所述VNF分配。
结合前述的第六方面或第六方面的第一种可能的实现方式至第六方面的第五种可能的实现方式中的任一种实现方式,在第六种可能的实现方式中,
所述处理器,还用于在从多个第二节点中确定允许释放连接的第二节点之后,向所述允许释放连接的第二节点发送第二连接释放通知消息,所述第二连接释放通知消息中携带所述第一节点的标识,所述第二连接释放通知消息用于通知所述允许释放连接的第二节点,删除所述允许释放连接的第二节点中保存的所述第一节点的标识指示的所述第一节点的信息。
第七方面,本发明提供一种通信系统,包括:
如上述第三方面或第三方面的任一种可能的实现方式所述的释放连接的装置,以及如上述第四方面或第四方面的任一种可能的实现方式所述的释放连接的装置;或者,如上述第五方面或第五方面的任一种可能的实现方式所述的释放连接的装置,以及如上述第六 方面或第六方面的任一种可能的实现方式所述的释放连接的装置。
本发明提供一种释放连接的方法、装置及系统,包括第一节点从多个第二节点中确定允许释放连接的第二节点,并删除第一节点中保存的允许释放连接的第二节点的信息,其中,该多个第二节点为已经与第一节点建立连接的节点。通过本发明提供的释放连接的方法,第一节点能够释放与允许释放连接的第二节点之间的连接,以节省第一节点的连接资源,从而使得第一节点具有空闲的连接资源来建立与其他第二节点之间的新的连接,进而使得第一节点能够与该其他第二节点进行通信。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案,下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本发明的一些实施例,而不是本发明的全部实施例。
图1为一种现有的NFV系统的架构图;
图2为本发明实施例提供的一种释放连接的方法的流程图一;
图3为本发明实施例提供的一种释放连接的方法的流程图二;
图4为本发明实施例提供的一种释放连接的方法的交互图一;
图5为本发明实施例提供的一种释放连接的方法的交互图二;
图6为本发明实施例提供的一种释放连接的方法的交互图三;
图7为本发明实施例提供的一种释放连接的方法的交互图四;
图8为本发明实施例提供的一种释放连接的方法的交互图五;
图9为本发明实施例提供的一种释放连接的方法的交互图六;
图10为本发明实施例提供的一种释放连接的方法的交互图七;
图11为本发明实施例提供的一种释放连接的装置的结构示意图一;
图12为本发明实施例提供的一种释放连接的装置的结构示意图二;
图13为本发明实施例提供的一种释放连接的装置的结构示意 图三;
图14为本发明实施例提供的一种释放连接的装置的结构示意图四;
图15为本发明实施例提供的一种释放连接的装置的硬件结构示意图一;
图16为本发明实施例提供的一种释放连接的装置的硬件结构示意图二;
图17为本发明实施例提供的一种通信系统的框图。
具体实施方式
下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例仅仅是本发明一部分实施例,而不是全部的实施例。
如图1所示,为一种NFV系统的架构图。该NFV系统包括:NFVO、VNFM、VIM、运营支撑系统(英文:operations support system,缩写:OSS)或业务支撑系统(英文:business support system,缩写:BSS)、网元管理节点(英文:element manager,缩写:EM)、VNF节点、虚拟网络功能基础设施(英文:network function virtualization infrastructure,缩写:NFVI)等功能节点,其中,OSS/BSS,或者是OSS/BSS的用户操作界面可以称为网络管理节点(英文:network manager,缩写:NM)。
在NFV系统中,NFVO、VNFM以及VIM构成了NFV系统的管理编排(英文:NFV management and orchestration,缩写:NFV-MANO)域,其中,NFVO也可以称为网络功能虚拟化编排者。
其中,NFVO可以对NFV系统中的VIM进行操作,管理及协调,即NFVO负责调度该NFV系统中所有VIM所管理的资源。NFVO与NFV系统中的所有VIM以及VNFM均相连。
VIM是基础设施和资源的管理入口,为VNF提供资源管理,具体指为VNF提供NFVI资源管理,包括为VNF提供基础设施相关硬件和虚拟化资源的配置维护、资源监控、告警、性能管理等功能。
VNFM负责VNF的生命周期管理,具体通过向NFVO申请资源或者释放资源来实现对VNF的生命周期管理,包括对VNF进行实例化、扩容/缩容、查询、更新及终止等。
在现有技术中,当VNFM需要请求NFVO指定的VIM为该VNFM管理的VNF分配资源时,若该VNFM和该VIM之间还未建立连接,则该VNFM需先建立与该VIM之间的连接,从而由该VIM为该VNF分配资源。
然而,在NFV系统中,能够与VNFM建立连接的VIM的个数有限,能够与VIM建立连接的VNFM的个数也有限。
那么,在某个VNFM请求NFVO指定的VIM为该VNFM管理的VNF分配资源的过程中,一方面,当已经与该VNFM建立连接的VIM的个数达到门限值时,若该VNFM还未与NFVO指定的VIM之间建立连接,则会导致该VNFM由于没有空闲的连接资源,而与该NFVO指定的VIM之间无法建立连接,从而使得该VNFM无法请求该NFVO指定的VIM为该VNF分配资源。
另一方面,当已经与某个VIM建立连接的VNFM的个数达到门限值时,若该VIM还未与向其请求资源分配的新的VNFM之间建立连接,则会导致该VIM由于没有空闲的连接资源,而与该VNFM之间无法建立连接,从而即使该VIM的剩余资源能够满足该VNFM为该VNF请求的资源,该VIM也无法为该VNF分配资源。
本发明提供的一种释放连接的方法、装置及系统,使得节点通过合理地释放与其他节点之间已经建立的连接,以保证该节点具有空闲的连接资源来建立新的连接。
需要说明的是,在本发明实例中,上述NFV系统中的任意一种功能节点可能由一个实体设备实现,也可能由多个实体设备共同实现,NFV系统中的多个功能节点可能分别由不同的实体设备实现,也可能都由同一个实体设备实现。可以理解的是,NFV系统中的任意一种功能节点都可能是实体设备内的一个逻辑功能模块,也可能是由多个实体设备组成的一个逻辑功能模块。
因此,在下述的本发明实施例中,可以由一个实体设备执行本发明实施例提供的方法中的各个步骤,可以由多个实体设备协作执行本发明实施例提供的方法中的各个步骤,对此本发明不作限定。
进一步地,为了更清楚地介绍本发明提供的一种释放连接的方法,下文中均以逻辑功能模块(即NFV系统中的功能节点)作为执行主体进行说明,本领域技术人员可以理解,逻辑功能模块在具体实现时需依赖于其所在的实体设备上的硬件资源。
在本发明实施例中,NFV系统可以应用于长期演进(英文:long term evolution,缩写:LTE)通信系统中,也可以应用于LTE的演进通信系统中,如LTE-A(英文全称:long term evolution advanced)系统中,还可以应用于WCDMA等第三代移动通信(英文:3rd-Generation,缩写:3G)系统中等,本发明不作限制。
实施例一
本发明实施例提供一种释放连接的方法,如图2所示,该方法包括:
S101、第一节点从多个第二节点中确定允许释放连接的第二节点,该多个第二节点为已经与第一节点建立连接的节点。
需要说明的是,在本发明实施例中,第一节点可以为VNFM,也可以为VIM。具体的,当第一节点为VNFM时,该多个第二节点为多个VIM,且该多个VIM均已经与该VNFM建立连接;当第一节点为VIM时,该多个第二节点为多个VNFM,且该多个VNFM均已经与该VIM建立连接。
进一步地,第一节点可以根据管理节点的指示,从多个第二节点中确定允许释放连接的第二节点。例如,当管理节点确定该多个第二节点中,存在允许释放连接的第二节点后,管理节点会将该允许释放连接的第二节点的标识携带在第一连接释放通知消息中,并向第一节点发送,从而第一节点在接收到第一连接释放通知消息后,可以根据该允许释放连接的第二节点的标识,从该多个第二节点中确定允许释放连接的第二节点。
可选的,当第一节点具体为VNFM,多个第二节点具体为VIM时,VNFM也可以自行从该多个VIM中确定允许释放连接的VIM。
在本发明实施例中,上述允许释放连接的第二节点可以为该多个第二节点中,与第一节点没有资源管理关系的第二节点,或者为该多个第二节点中满足预设条件的第二节点。其中,该预设条件可以根据实际的网络维护需求进行设置,以使得第一节点能够选择合适的第二节点,以释放与该第二节点之间的连接。
S102、第一节点删除第一节点中保存的该允许释放连接的第二节点的信息。
其中,允许释放连接的第二节点的信息包括允该许释放连接的第二节点的标识和连接信息。该允许释放连接的第二节点的连接信息至少可以包括该允许释放连接的第二节点的IP地址、统一资源定位符(英文:uniform resource locator,缩写:URL)、用户名、认证密码等信息。
需要说明的是,第一节点删除其保存的该允许释放连接的第二节点的信息后,即表征第一节点成功释放了与该允许释放连接的第二节点之间的连接。
本发明实施例提供一种释放连接的方法,包括第一节点从多个第二节点中确定允许释放连接的第二节点,并删除第一节点中保存的允许释放连接的第二节点的信息,其中,该多个第二节点为已经与第一节点建立连接的节点。通过该方法,第一节点能够释放与允许释放连接的第二节点之间的连接,以节省第一节点的连接资源,从而使得第一节点具有空闲的连接资源来建立与其他第二节点之间的新的连接,进而使得第一节点能够与该其他第二节点进行通信。
本发明实施例提供一种释放连接的方法,如图3所示,该方法包括:
S201、管理节点从多个第二节点中确定允许释放连接的第二节点,该多个第二节点为已经与第一节点建立连接的节点。
其中,第一节点可以为VNFM,也可以为VIM。具体的,当第 一节点为VNFM时,该多个第二节点为多个VIM,且该多个VIM均已经与该VNFM建立连接;当第一节点为VIM时,该多个第二节点为多个VNFM,且该多个VNFM均已经与该VIM建立连接。
在本发明实施例中,管理节点可以为第一节点和该多个第二节点所在的NFV系统中的NFVO,也可以为该NFV系统中具有NFVO的功能的其他功能节点,即管理节点可以为能够调度该NFV系统中所有VIM所管理的资源的功能节点,对此本发明不作限制。
管理节点可以直接从该多个第二节点中选择与第一节点没有资源管理关系的第二节点,作为允许释放连接的第二节点。管理节点也可以从该多个第二节点中选择满足预设条件的第二节点,作为允许释放连接的第二节点。其中,该预设条件可以根据实际的网络维护需求进行设置,以使得管理节点能够根据该预设条件选择合适第二节点作为允许释放连接的第二节点。
S202、管理节点向第一节点发送第一连接释放通知消息,第一连接释放通知消息中携带该允许释放连接的第二节点的标识,第一连接释放通知消息用于通知第一节点,删除第一节点中保存的该允许释放连接的第二节点的信息。
当管理节点从该多个第二节点中确定允许释放连接的第二节点后,管理节点可以将该允许释放连接的第二节点的标识,携带在第一连接释放通知消息中,并向第一节点发送,以使得第一节点接收到第一连接释放通知消息后,删除第一节点中保存的该允许释放连接的第二节点的信息,即通知第一节点自动释放与该允许释放连接的第二节点之间的连接。
本发明实施例提供一种释放连接的方法,包括管理节点从多个第二节点中确定允许释放连接的第二节点,并向第一节点发送第一连接释放通知消息,该第一连接释放通知消息中携带允许释放连接的第二节点的标识,该第一连接释放通知消息用于通知第一节点,删除第一节点中保存的允许释放连接的第二节点的信息,该多个第二节点为已经与第一节点建立连接的节点。
通过该方法,管理节点能够在已经与第一节点建立连接的多个第二节点中选择合适的第二节点,并及时通知第一节点释放与该第二节点之间的连接,以节省第一节点的连接资源,从而使得第一节点具有空闲的连接资源来建立与其他第二节点之间的新的连接,进而使得第一节点能够与该其他第二节点进行通信。
实施例二
本发明实施例提供一种释放连接的方法,可以用于多种应用场景中,下面将在如下三种可能的应用场景中,对本发明实施例提供的一种释放连接的方法进行示例性说明。
在第一种可能的应用场景中,由管理节点发起释放连接流程。其中,管理节点可以为NFV系统中的NFVO,也可以为具有NFVO的功能的其他功能节点,即管理节点可以为能够调度该NFV系统中所有VIM所管理的资源的功能节点,对此本发明不作限制。
在管理节点中,设置有资源映射表,该资源映射表中记录了NFV系统中各个VNFM的资源申请情况、各个VIM的资源分配情况,以及VNFM与VIM之间的连接情况等。例如,某个VNFM与哪些VIM之间建立了连接,这些VIM分别为该VNFM所管理的VNF分配的资源量以及资源类型等。从而管理节点能够通过查询该资源映射表,获知NFV系统中的每个VNFM分别与哪些VIM之间建立了连接,每个VIM分别与哪些VNFM之间建立了连接,以及已经建立连接的VIM与VNFM之间有没有资源管理关系等。
需要说明的是,已经建立连接的某个VNFM和某个VIM之间有资源管理关系,是指该VIM为该VNFM管理的至少一个VNF预留了或者分配了资源;已经建立连接的某个VNFM和某个VIM之间没有资源管理关系,是指该VIM没有为该VNFM管理的任何一个VNF预留或者分配资源。
可以理解的是,由于能够与VNFM建立连接的VIM的个数有限,能够与VIM建立连接的VNFM也有限,因此,若已经建立连接的某个VNFM和某个VIM之间没有资源管理关系,则可以释放该 VNFM和该VIM之间的连接,以节省该VNFM和该VIM的连接资源。那么在第一种可能的应用场景中,当管理节点通过对该资源映射表的查询,发现已经与某个第一节点建立连接的多个第二节点中,存在与该第一节点没有资源管理关系的第二节点时,管理节点需发起连接释放流程。
在第一种可能的应用场景中,第一节点可以为VNFM,也可以为VIM。具体的,当第一节点为VNFM时,该多个第二节点为多个VIM,且该多个VIM均已经与该VNFM建立连接;当第一节点为VIM时,该多个第二节点为多个VNFM,且该多个VNFM均已经与该VIM建立连接。
进一步地,在第一种可能的应用场景的第一种可能的方式中,如图4所示,该方法可以包括:
S301、管理节点从多个第二节点中确定允许释放连接的第二节点,该多个第二节点为已经与第一节点建立连接的节点。
具体的,在第一种可能的应用场景中,管理节点确定的允许释放连接的第二节点,具体为该多个第二节点中与该第一节点没有资源管理关系的第二节点。
可以理解的是,当管理节点通过查询该资源映射表,发现该多个第二节点中存在与该第一节点没有资源管理关系的第二节点时,管理节点即可确定该第一节点和与该第一节点没有资源管理关系的第二节点之间的连接允许被释放。
需要说明的是,在本发明实施例中,管理节点可以在对VNF进行生命周期管理的过程中,判断多个第二节点中是否存在与第一节点没有资源管理关系的第二节点。
示例性的,例如,当需要对某个VNF进行扩容时,管理节点通过对该资源映射表进行查询,以选择合适的VIM为该VNF分配资源。在这一过程中,当管理节点对该资源映射表进行查询时,管理节点可以对已经与管理该VNF的VNFM之间建立了连接的多个VIM进行查询,确定该多个VIM中是否存在与该VNFM没有资源管理关 系的VIM。
可选的,管理节点也可以周期性地对该资源映射表进行查询。具体的,若第一节点为VNFM,第二节点为VIM,则管理节点可以周期性地在该资源映射表中查询该NFV系统中的每个VNFM的相关信息,判断已经与某个VNFM之间建立连接的多个VIM中,是否存在与该VNFM没有资源管理关系的VIM;若第一节点为VIM,第二节点为VNFM,则管理节点可以周期性地在该资源映射表中查询该NFV系统中的每个VIM的相关信息,判断已经与某个VIM建立连接的多个VNFM中,是否存在与该VIM没有资源管理关系的VNFM,此时。
S302、管理节点向第一节点发送第一连接释放通知消息,该第一连接释放通知消息中携带该允许释放连接的第二节点的标识。
在本发明实施例中,当管理节点从多个第二节点中确定允许释放连接的第二节点后,管理节点即可通知第一节点可以释放与该允许释放连接的第二节点之间的连接,即该第一连接释放通知消息用于通知第一节点删除其保存的该允许释放连接的第二节点的信息。
S303、第一节点接收到第一连接释放通知消息后,根据该允许释放连接的第二节点的标识,确定该允许释放连接的第二节点。
可以理解的是,第一节点接收到第一连接释放通知消息后,根据该第一连接释放通知消息中携带的允许释放连接的第二节点的标识,第一节点即可确定其与该允许释放连接的第二节点之间的连接允许被释放,即第一节点确定可以删除其保存的该允许释放连接的第二节点信息。
S304、第一节点向该允许释放连接的第二节点发送第二连接释放通知消息,该第二连接释放通知消息中携带第一节点的标识。
在本发明实施例中,当第一节点确定可以删除其保存的该允许释放连接的第二节点信息后,第一节点首先需要通过与该允许释放连接的第二节点之间的连接,向该允许释放连接的第二节点发送第二连接释放通知消息,以通知该允许释放连接的第二节点也删除其 保存该第一节点的信息。
S305、第一节点删除第一节点中保存的该允许释放连接的第二节点的信息。
其中,该允许释放连接的第二节点的信息与如图2所示实施例中的允许释放连接的第二节点的信息的含义相同,此处不做赘述。
至此,第一节点成功释放了第一节点与该允许释放连接的第二节点之间的连接。
S306、该允许释放连接的第二节点接收到第二连接释放通知消息后,根据第一节点的标识确定第一节点。
可以理解的是,该允许释放连接的第二节点接收到第二连接释放通知消息后,根据该第二连接释放通知消息中携带的该第一节点的标识,即可确定其与该第一节点的连接允许被释放。
S307、该允许释放连接的第二节点删除该允许释放连接的第二节点中保存的第一节点的信息。
其中,第一节点的信息包括允该第一节点的标识和连接信息。该第一节点的连接信息至少可以包括该第一节点的IP地址、统一资源定位符(英文:uniform resource locator,缩写:URL)、用户名、认证密码等信息。
至此,该允许释放连接的第二节点也成功释放了与第一节点之间的连接。
需要说明的是,上述S305和上述S306与S307之间的执行顺序本发明实施例不作限制。
在第一种可能的应用场景的第二种可能的方式中,如图5所示,该方法可以包括:
S401、管理节点从多个第二节点中确定允许释放连接的第二节点,该多个第二节点为已经与第一节点建立连接的节点。
S402、管理节点向第一节点发送第一连接释放通知消息,所述第一连接释放通知消息中携带该允许释放连接的第二节点的标识。
S403、第一节点接收到第一连接释放通知消息后,根据该允许 释放连接的第二节点的标识,确定该允许释放连接的第二节点。
其中,上述S401-S403的具体实现方式,与如图4所示实施例中的S301-S303的具体实现方式相同,上述S401-S403的具体实现方式可以参见如图4所示实施例中的相关描述,此处不再赘述。
S404、第一节点删除第一节点中保存的该允许释放连接的第二节点的信息。
至此,第一节点成功释放了与该允许释放连接的第二节点之间的连接。
S405、管理节点向该允许释放连接的第二节点发送第二连接释放通知消息,该第二连接释放通知消息中携带第一节点的标识。
需要说明的是,在第一种可能的应用场景的第二种可能的实现方式中,当管理节点从多个第二节点中确定允许释放连接的第二节点后,管理节点可以直接向该允许释放连接的第二节点发送第二连接释放通知消息,以通知该允许释放连接的第二节点也删除其保存该第一节点的信息。
S406、该允许释放连接的第二节点接收到第二连接释放通知消息后,根据第一节点的标识确定第一节点。
S407、该允许释放连接的第二节点删除该允许释放连接的第二节点中保存的第一节点的信息。
其中,上述S406-S407的具体实现方式,与如图4所示实施例中的S306-S307的具体实现方式相同,上述S406-S407的具体实现方式可以参见如图4所示实施例中的相关描述,此处不再赘述。
至此,该允许释放连接的第二节点也成功释放了与第一节点之间的连接。
需要说明的是,上述S402-S404和上述S405-S407的先后执行顺序本发明实施例不作具体限制。
可选的,在本发明实施例中,当第一节点和该允许释放连接的第二节点均成功释放了它们之间的连接后,该第一节点和该允许释放连接的第二节点还可以向管理节点发送确认消息,以使得管理节 点确定该第一节点与该允许释放连接的第二节点之间的连接已经被成功释放,进而管理节点可以对该资源映射表进行更新。
在第一种可能的应用场景中,通过本发明实施例提供的释放连接的方法,管理节点能够在确定已经与第一节点建立连接的多个第二节点中,存在与第一节点没有资源管理关系的第二节点后,及时地通知第一节点和该与第一节点没有资源管理关系的第二节点,释放第一节点和该和该与第一节点没有资源管理关系的第二节点之间的连接,避免了第一节点和该和该与第一节点没有资源管理关系的第二节点之间的连接,继续占用第一节点和该与第一节点没有资源管理关系的第二节点的连接资源,从而节省了该第一节点和该与第一节点没有资源管理关系的第二节点的连接资源。
在第二种可能的应用场景中,由VNFM发起连接释放流程。在NFV系统中,由于能够与VNFM建立连接的VIM的个数有限,因此,当VNFM确定已经与其建立连接的VIM的个数达到门限值时,VNFM需要发起连接释放流程。那么,在第二种可能的应用场景中,第一节点为VNFM,多个第二节点为VIM,且该多个VIM均为已经与该VNFM建立连接的VIM。
具体的,在第二可能的应用场景的第一种可能的方式中,如图6所示,该方法可以包括:
S501、VNFM确定多个VIM的个数达到预设门限值。
其中,预设门限值可以为能够与该VNFM建立连接的VIM的最大个数,也可以为根据实际中网络维护的需求设置的一个小于该最大个数的门限值。
具体的,在本发明实施例中,VNFM可以周期性地判断已经与其建立连接的VIM的个数是否达到预设门限值。VNFM也可以在每次建立与新的VIM之间的连接之后,判断已经与其建立连接的VIM的个数是否达到预设门限值。
S502、VNFM向管理节点发送连接释放请求消息,该连接释放请求消息用于请求管理节点确定允许释放连接的VIM。
具体的,当VNFM判断该多个VIM的个数达到门限值时,VNFM可以向管理节点发送连接释放请求消息,以请求管理节点从该多个VIM中确定允许释放连接的VIM。
S503、管理节点根据该连接释放请求消息,从该多个VIM中确定允许释放连接的VIM。
在本发明实施例中,当管理节点接收到该VNFM发送的连接释放请求消息后,管理节点确定需要从已经与该VNFM建立连接的多个VIM中,确定允许释放连接的VIM。
具体的,管理节点可以先通过查询该管理节点中设置的资源映射表,判断该多个VIM中是否存在与该VNFM没有资源管理关系的VIM。
若管理节点确定该多个VIM中存在与该VNFM没有资源管理关系的VIM,则管理节点将该多个VIM中与该VNFM没有资源管理关系的VIM确定为允许释放连接的VIM。
若管理节点确定该多个VIM中不存在与该VNFM没有资源管理关系的VIM,则管理节点将该多个VIM中满足第一条件的第一VIM确定为允许释放连接的VIM。
其中,该第一条件为该多个VIM中的第一VIM为该VNFM所管理的VNF分配的资源,允许由该多个VIM中的另一个VIM为该VNF分配。
为了更好的说明管理节点将该多个VIM中满足第一条件的第一VIM确定为允许释放连接的VIM,下面将以VIM1、VIM2以及VIM3为例,进行示例性的说明。
假设,已经与VNFM建立连接的多个VIM包括VIM1、VIM2以及VIM3,当管理节点确定VIM1、VIM2以及VIM3中不存在与该VNFM没有资源管理关系的VIM时,管理节点至少可以通过如下两种方式,从VIM1、VIM2以及VIM3中确定允许释放连接的VIM。
方式一、管理节点分别获取VIM1、VIM2以及VIM3的剩余资源的信息和为该VNFM所管理的VNF分配的资源的信息。
其中,VIM的剩余资源的信息至少包括该VIM的剩余资源量和剩余资源的类型。VIM为该VNFM所管理的VNF分配的资源的信息至少包括,VIM为该VNFM所管理的VNF分配的资源量,和VIM为该VNFM所管理的VNF分配的资源的类型。
示例性的,VIM1的剩余资源的信息为:2个A类型的VM,1个B类型的VM;VIM1为该VNFM分配的资源的信息包括:1个A类型的VM。
VIM2的剩余资源的信息为:1个A类型的VM,2个C类型的VM;VIM2为该VNFM分配的资源的信息包括:2个C类型的VM。
VIM3的剩余资源的信息为:2个A类型的VM,2个C类型的VM;VIM3为该VNFM分配的资源的信息包括:2个B类型的VM。
具体的,以VIM1为例,管理节点可以直接从资源映射表中获取VIM1的剩余资源的信息和VIM1为该VNFM分配的资源的信息。
管理节点还可以通过向VIM1查询的方式获取VIM1的剩余资源的信息。具体的,管理节点向VIM1发送剩余资源查询消息,当VIM1接收到该剩余资源查询消息后,会将VIM1的剩余资源的信息携带在响应消息中发送至管理节点,以使得管理节点根据该响应消息,获取VIM1的剩余资源的信息。
进一步的,管理节点获取到VIM1、VIM2以及VIM3的剩余资源的信息和为该VNFM所管理的VNF分配的资源的信息后,根据VIM1、VIM2以及VIM3的剩余资源的信息和为该VNFM所管理的VNF分配的资源的信息,判断VIM1、VIM2以及VIM3中是否存在满足第一条件的第一VIM。
具体的,管理节点可以先将VIM1为该VNFM所管理的VNF分配的资源的信息,分别与VIM2和VIM3的剩余资源的信息进行比较,若VIM2和VIM3中存在至少一个VIM的剩余资源信息能够满足VIM1为该VNFM所管理的VNF分配的资源的信息,则管理节点确定VIM1为满足第一条件的第一VIM。
例如,VIM1为该VNFM所管理的VNF1分配了1个A类型的 VM,由于VIM2的剩余资源中包括1个A类型的VM,VIM3的剩余资源中包括2个A类型的VM,因此,VIM2和VIM3的剩余资源的信息都能够满足VIM1为VNF1分配的资源的信息,即VIM1为VNF1分配的资源,可以由VIM2或者VIM3为VNF1分配。从而管理节点可以确定VIM1为满足第一条件的第一VIM。
进一步地,管理节点采用上述判断VIM1是否为满足第一条件的第一VIM的方式,逐一对VIM2和VIM3进行判断,并确定VIM2也为满足第一条件的第一VIM,即VIM2为该VNFM所管理的VNF2和VNF3分配的资源,可以由VIM3为VNF2和VNF3分配。
需要说明的是,若在管理节点中设置只需确定一个允许释放连接的VIM即可,则当管理节点确定VIM1为第一VIM后,则管理节点可以直接将VIM1确定为允许释放连接的VIM,无需进一步对VIM2和VIM3进行判断;或者当管理节点对VIM1、VIM2以及VIM3逐一进行判断,确定VIM1和VIM2为第一VIM后,管理节点可以在VIM1或者VIM2中随机选择一个作为允许释放连接的VIM,也可以在VIM1或者VIM3中选择一个与该VNFM之间的数据传输质量较差的VIM作为允许释放连接的VIM,对比本发明不作限制。
若在管理节点中设置可以确定多个允许释放连接的VIM,则由于VIM3在能够为VNF1分配由VIM1为VNF1分配的资源的情况下,还能为VNF2和VNF3分配由VIM2为VNF2和VNF3分配的资源,因此,管理节点可以将VIM1和VIM2均确定为允许释放连接的VIM。
可以理解的是,若VIM3不能同时分配由VIM1和VIM2为该VNFM所管理的VNF分配的资源,则管理节点可以在VIM1和VIM2中选择一个作为允许释放连接的VIM。
方式二、为了保证VIM和VNFM之间的数据传输质量,还可以在管理节点中设置一个筛选条件。管理节点可以先从VIM1、VIM2以及VIM3中选择满足该筛选条件的VIM,进而判断该满足筛选条件的VIM是否为满足第一条件的第一VIM。
其中,筛选条件可以包括但不限于:为该VNFM所管理的VNF分配的资源量最少的VIM,时延最大的VIM,故障率最高的VIM等中的一项或多项条件。
示例性的,假设在管理节点中设置的筛选条件包括为VNFM所管理的VNF分配的资源量最少的VIM。
管理节点先通过查询该资源映射表,分别获取VIM1、VIM2以及VIM3为该VNFM所管理的VNF分配的资源的信息,管理节点将VIM1、VIM2以及VIM3为该VNFM所管理的VNF分配的资源量进行比较,确定为该VNFM所管理的VNF分配的资源量最少的VIM。
例如,VIM1为VNF1分配了1个VM,VIM2为VNF2和VNF3各分配了1个VM,VIM3为该VNFM所管理的VNF4分配了2个VM,因此,VIM1为VIM1、VIM2以及VIM3中为该VNFM所管理的VNF分配的资源量最少的VIM。
进一步的,管理节点获取VIM2以及VIM3的剩余资源信息,并根据VIM1为VNF1分配的资源的信息,和VIM2以及VIM3的剩余资源信息,判断VIM1是否为满足第一条件的第一VIM。
其中,管理节点判断VIM1是否为满足第一条件的第一VIM的方式,与方式一中管理节点判断VIM1是否为满足第一条件的第一VIM的方式相同,此处不再赘述。
可以理解的是,在方式二中,若VIM1为第一节点,则管理节点即可确定VIM1为允许释放链接的VIM。若VIM1不为第一节点,则管理节点即可确定VIM1、VIM2以及VIM3中没有允许释放链接的VIM,进而管理节点可以不响应该VNFM发送的连接释放请求消息。
S504、管理节点向VNFM发送第一连接释放通知消息,所述第一连接释放通知消息中携带该允许释放连接的VIM的标识。
S505、VNFM接收到第一连接释放通知消息后,根据该允许释放连接的VIM的标识,确定该允许释放连接的VIM。
可以理解的是,VNFM接收到第一连接释放通知消息后,根据 该第一连接释放通知消息中携带的允许释放连接的VIM的标识,即可确定其与该允许释放连接的VIM之间的连接允许被释放,即第一连接释放通知消息用于通知该VNFM删除其保存的该允许释放连接的VIM的信息。
S506、VNFM向该允许释放连接的VIM发送第二连接释放通知消息,该第二连接释放通知消息中携带该VNFM的标识。
在本发明实施例中,当VNFM确定可以删除其保存的该允许释放连接的VIM的信息后,该VNFM首先需要通过与该允许释放连接的VIM之间的连接,向该允许释放连接的VIM发送第二连接释放通知消息,以通知该允许释放连接的VIM也删除其保存该VNFM的信息。
S507、VNFM删除该VNFM中保存的该允许释放连接的VIM的信息。
其中,该允许释放连接的VIM的信息包括该允许释放连接的VIM的标识和连接信息,其中,连接信息中包括该允许释放连接的VIM的IP地址、URL、用户名、认证密码等信息。
至此,VNFM成功释放了该VNFM与该允许释放连接的VIM的连接。
S508、该允许释放连接的VIM接收到第二连接释放通知消息后,根据该VNFM的标识确定该VNFM。
可以理解的是,该允许释放连接的VIM接收到第二连接释放通知消息后,根据该第二连接释放通知消息中携带的该VNFM的标识,即可确定其与该VNFM之间的连接允许被释放,即该允许释放连接的VIM可以删除其保存的该VNFM的信息。
S509、该允许释放连接的VIM删除该允许释放连接的VIM中保存的该VNFM的信息。
其中,该VNFM的信息包括该VNFM的标识和连接信息,该VNFM的连接信息包括该VNFM的IP地址、URL、用户名、认证密码等信息。
至此,该允许释放连接的VIM也成功释放了与该VNFM之间的连接。
需要说明的是,上述S507和上述S508与S509之间的执行顺序,本发明实施例不作限制。
在第二可能的应用场景的第二种可能的方式中,如图7所示,该方法可以包括:
S601、VNFM确定多个VIM的个数达到预设门限值。
S602、VNFM向管理节点发送连接释放请求消息,该连接释放请求消息用于请求管理节点确定允许释放连接的VIM。
S603、管理节点根据该连接释放请求消息,从该多个VIM中确定允许释放连接的VIM。
S604、管理节点向VNFM发送第一连接释放通知消息,所述第一连接释放通知消息中携带该允许释放连接的VIM的标识。
S605、VNFM接收到第一连接释放通知消息后,根据该允许释放连接的VIM的标识,确定该允许释放连接的VIM。
具体的,上述S601-S605的具体实现方式,如图6所示的实施例中S501-S505的具体实现方式相同,上述S601-S605的具体实现方式可以参见如图6所示实施例中的相关描述,此处不再赘述。
S606、VNFM删除该VNFM中保存的该允许释放连接的VIM的信息。
至此,VNFM成功释放了该VNFM与该允许释放连接的VIM之间的连接。
S607、管理节点向该允许释放连接的VIM发送第二连接释放通知消息,该第二连接释放通知消息中携带该VNFM的标识。
需要说明的是,在第二种可能的应用场景的第二种可能的实现方式中,当管理节点从多个VIM中确定允许释放连接的VIM后,管理节点可以直接向该允许释放连接的VIM发送第二连接释放通知消息,以通知该允许释放连接的VIM也删除其保存该VNFM的信息。
S608、该允许释放连接的VIM接收到第二连接释放通知消息 后,根据该VNFM的标识确定该VNFM。
S609、该允许释放连接的VIM删除该允许释放连接的VIM中保存的该VNFM的信息。
其中,上述S608-S609的具体实现方式,与如图4所示实施例中的S508-S509的具体实现方式相同,上述S608-S609的具体实现方式可以参见如图6所示实施例中的相关描述,此处不再赘述。
至此,该允许释放连接的VIM也成功释放了与该VNFM之间的连接。
需要说明的是,上述S604-S606和上述S607-S609的先后执行顺序本发明实施例不作具体限制。
可选的,在本发明实施例中,当VNFM和该允许释放连接的VIM均成功释放了它们之间的连接后,该VNFM和该允许释放连接的VIM还可以向管理节点发送确认消息,以使得管理节点确定该VNFM与该允许释放连接的VIM之间的连接已经被成功释放,进而管理节点可以对该资源映射表进行更新。
在第二种可能的应用场景中,通过本发明实施例提供的释放连接的方法,使得VNFM在确定已经与其建立连接的多个VIM的个数达到预设门限值后,及时向管理节点发送连接释放请求消息,以请求管理节点从该多个VIM中确定允许释放连接的VIM。当管理节点从该多个VIM中确定允许释放连接的VIM后,管理节点会通知该VNFM和该允许释放连接的VIM释放该VNFM和该允许释放连接的VIM之间的连接,从而节省该VNFM和该允许释放连接的VIM的连接资源,进而当该VNFM需要请求还未与其建立连接的其他VIM为该VNFM管理的VNF分配资源时,该VNFM有空闲的连接资源来建立与该其他VIM之间的连接,以使得该VNFM能够请求该其他VIM为该VNF分配资源。
在第二可能的应用场景的第三种可能的方式中,VNFM能够自行从该多个VIM中确定允许释放连接的VIM。具体的,如图8所示,该方法可以包括:
S701、VNFM确定多个VIM的个数达到预设门限值。
S702、VNFM从该多个VIM中确定允许释放连接的VIM。
具体的,在VNFM中记录有该VNFM的资源申请情况,以及与VIM之间的连接建立情况,因此,VNFM可以先判断该多个VIM中是否存在与其没有资源管理关系的VIM。
若VNFM确定该多个VIM中存在与其没有资源管理关系的VIM,则VNFM将与其没有资源管理关系的VIM确定为允许释放连接的VIM。
若VNFM确定该多个VIM中不存在与其没有资源管理关系的VIM,则VNFM将该多个VIM中满足第一条件的第一VIM确定为允许释放连接的VIM。
其中,该第一条件为该多个VIM中的第一VIM为该VNFM所管理的VNF分配的资源,允许由该多个VIM中的另一个VIM为该VNF分配。
具体的,VNFM将该多个VIM中满足第一条件的第一VIM确定为允许释放连接的VIM的具体实施方式,与如图6所示实施例中管理节点将该多个VIM中满足第一条件的第一VIM确定为允许释放连接的VIM的具体实施方式类似,VNFM将该多个VIM中满足第一条件的第一VIM确定为允许释放连接的VIM的具体实施方式可以参加如图6所示实施例中的相关描述,此处不再赘述。
需要说明的是,VNFM将该多个VIM中满足第一条件的第一VIM确定为允许释放连接的VIM的过程中,VNFM需要获取该多个VIM的剩余资源的信息和为该VNFM所管理的VNF分配的资源的信息。在本发明实施例中,由于VNFM中记录有该VNFM向该多个VIM请求资源的情况,因此,VNFM可以直接获取其保存的该多个VIM为该VNFM所管理的VNF分配的资源的信息。
进一步的,VNFM需要通过向该多个VIM发送剩余资源查询消息的方式获取该多个VIM的剩余资源信息。具体的,VNFM通过向该多个VIM发送剩余资源查询消息以获取该多个VIM的剩余资源 信息的方式,与如图6所示的实施例中管理节点向VIM1发送剩余资源查询消息以获取VIM1的剩余资源信息的方式相同,具体可参见如图6所示实施例中的相关描述。
S703、VNFM向该允许释放连接的VIM发送第二连接释放通知消息,该第二连接释放通知消息中携带该VNFM的标识。
S704、VNFM删除该VNFM中保存的该允许释放连接的VIM的信息。
S705、该允许释放连接的VIM接收到第二连接释放通知消息后,根据该VNFM的标识确定该VNFM。
S706、该允许释放连接的VIM删除该允许释放连接的VIM中保存的该VNFM的信息。
具体的,上述S703-S706的具体实现方式,与如图6所示实施例中S506-S509的实现方式相同,上述S703-S706的具体实现方式可以参见如图6所示实施例中的相关描述,此处不再赘述。
在第二种可能的应用场景中,通过本发明实施例提供的释放连接的方法,使得VNFM在确定已经与其建立连接的多个VIM的个数达到预设门限值后,自动对该多个VIM进行判断,从该多个VIM中选择允许释放连接的VIM,并释放与该允许释放连接的VIM之间的连接,从而节省该VNFM的连接资源,进而当该VNFM需要请求还未与其建立连接的其他VIM为该VNFM管理的VNF分配资源时,该VNFM有空闲的连接资源来建立与该其他VIM之间的连接,以使得该VNFM能够请求该其他VIM为该VNF分配资源。
另一方面,该VNFM释放与该允许释放连接的VIM之间的连接之前,还会通知该允许释放连接的VIM也释放该VNFM与该允许释放连接的VIM之间的连接,也节省了该允许释放连接的VIM的连接资源。
在第三种可能的应用场景中,由VIM发起连接释放流程。在NFV系统中,由于能够与VIM建立连接的VNFM的个数有限,因此,当VIM确定已经与其建立连接的VNFM的个数达到门限值时, 需要发起连接释放流程。那么,在第二种可能的应用场景中,第一节点为VIM,多个第二节点为VNFM,且该多个VNFM均为已经与该VIM建立连接的VNFM。
具体的,在第三可能的应用场景的第一种可能的方式中,如图9所示,该方法可以包括:
S801、VIM确定多个VNFM的个数达到预设门限值。
其中,预设门限值可以为能够与该VIM建立连接的VNFM的最大个数,也可以为根据实际中网络维护的需求进行设置的一个小于该最大个数的门限值。
具体的,在本发明实施例中,VIM可以周期性地判断与其建立连接的VNFM的个数是否达到预设门限值。VIM也可以在每次建立与新的VNFM之间的连接之后,判断已经与其建立连接的VNFM的个数是否达到预设门限值。
S802、VIM向管理节点发送连接释放请求消息,该连接释放请求消息用于请求管理节点确定允许释放连接的VNFM。
具体的,当VIM判断该多个VNFM的个数达到门限值时,VIM可以向管理节点发送连接释放请求消息,以请求管理节点从该多个VNFM中确定允许释放连接的VNFM。
S803、管理节点根据该连接释放请求消息,从该多个VNFM中确定允许释放连接的VNFM。
在本发明实施例中,当管理节点接收到该VIM发送的连接释放请求消息后,管理节点确定需要从已经与该VIM建立连接的多个VNFM中,确定允许释放连接的VNFM。
具体的,管理节点可以先通过查询该管理节点中设置的资源映射表,判断该多个VNFM中是否存在与该VIM没有资源管理关系的VNFM。
若管理节点确定该多个VNFM中存在与该VIM没有资源管理关系的VNFM,则管理节点将该多个VNFM中与该VIM没有资源管理关系的VNFM确定为允许释放连接的VNFM。
若管理节点确定该多个VNFM中不存在与该VIM没有资源管理关系的VNFM,则管理节点将该多个VNFM中满足第二条件的第一VNFM确定为允许释放连接的VNFM。
其中,该第二条件为该VIM为该多个VNFM中的第一VNFM所管理的VNF分配的资源,允许由已经与该第一VNFM建立连接的另一个VIM为该VNF分配。
为了更好的说明管理节点将该多个VNFM中满足第二条件的第一VNFM确定为允许释放连接的VNFM,下面将以VIM4、VNFM1、VNFM2以及VNFM3为例,进行示例性的说明。
假设,已经与VIM4建立连接的多个VNFM包括VNFM1、VNFM2以及VNFM3,当管理节点确定VNFM1、VNFM2以及VNFM3中不存在与VIM4没有资源管理关系的VNFM时,管理节点可以通过如下两种方式,从VNFM1、VNFM2以及VNFM3中确定允许释放连接的VNFM。
方式一、管理节点首先判断VNFM1是否为满足第二条件的第一VNFM,假设除VIM4外,VNFM1还与VIM5和VIM6之间建立了连接。
管理节点获取VIM4为VNFM1所管理的VNF分配的资源的信息,以及VIM5和VIM6的剩余资源的信息。
具体的,管理节点获取VIM4为VNFM1所管理的VNF分配的资源的信息的方式,可以参见如图6所示实施例中,管理节点分别获取VIM1为VNFM所管理的VNF分配的资源的信息的方式;管理节点获取VIM5和VIM6的剩余资源的信息的方式,可以参见如图6所示实施例中,管理节点分别获取VIM1的剩余资源的信息的方式,此处不再赘述。
管理节点可以先将VIM4为VNFM1所管理的VNF分配的资源的信息,分别与VIM5和VIM6的剩余资源的信息进行比较,若VIM5和VIM6中存在至少一个VIM的剩余资源信息能够满足VIM4为VNFM1所管理的VNF分配的资源的信息,则管理节点确定VNFM1 为满足第二条件的第一VNFM。
示例性的,假设,VIM4为VNFM1所管理的VNF5分配了1个A类型的VM,VIM5的剩余资源中包括1个A类型的VM,VIM6的剩余资源中包括2个A类型的VM。由于VIM5和VIM6的剩余资源的信息都能够满足VIM4为VNF5分配的资源的信息,即VIM4为VNF5分配的资源,可以由VIM5或者VIM6为VNF5分配,因此,管理节点可以确定VNFM1为满足第二条件的第一VNFM。
进一步地,管理节点采用上述判断VNFM1是否为满足第二条件的第一VNFM的方式,逐一对VNFM2和VNFM3进行判断,确定VIM4为VNFM2所管理的VNF分配的资源,也可以由于已经与VNFM2建立连接的其他VIM为VNFM2所管理的VNF分配,即管理节点确定VNFM2也为满足第二条件的第一VNFM。
需要说明的是,当该多个VNFM中不存在与该VIM没有资源管理关系的VNFM时,若在管理节点设置了只需确定一个允许释放连接的VNFM即可,则当管理节点确定VNFM1为第一VNFM后,则管理节点可以直接将VNFM1确定为允许释放连接的VNFM,无需进一步对VNFM2和VNFM3进行判断;或者当管理节点对VNFM1、VNFM2以及VNFM3逐一进行判断,确定VNFM1和VNFM2为第一VNFM后,管理节点可以在VNFM1或者VNFM2中随机选择一个作为允许释放连接的VNFM,也可以在VNFM1或者VNFM2中选择一个与VIM4的数据传输质量较差的作为允许释放连接的VNFM,对比本发明不作限制。
若在管理节点中设置了可以确定多个允许释放连接的VNFM,则管理节点可以将VNFM1和VNFM2均确定为允许释放连接的VNFM。
方式二、为了保证VIM和VNFM之间的数据传输质量,还可以在管理节点中设置一个筛选条件。管理节点可以先从VNFM1、VNFM2以及VNFM3中选择满足该筛选条件的VNFM,进而判断该满足筛选条件的VNFM是否为满足第二条件的第一VNFM。
其中,筛选条件可以包括但不限于:占用资源量最少的VNFM,时延最大的VNFM等中的一项或多项条件。
例如,假设在管理节点中设置的筛选条件包括占用资源量最少的VNFM。
管理节点先通过查询该资源映射表,获取VIM4分别为VNFM1、VNFM2以及VNFM3所管理的VNF分配的资源的信息,确定VNFM1、VNFM2以及VNFM3的占用资源量,即确定VIM4分别为VNFM1、VNFM2以及VNFM3所管理的VNF分配的资源量。管理节点将VNFM1、VNFM2以及VNFM3的占用资源量进行比较,确定占用资源量最少的VNFM。
例如,VIM4为VNFM1所管理的VNF分配了1个VM,为VNFM2和VNFM3所管理的VNF都分配了2个VM,因此,管理节点确定VNFM1为占用资源量最少的VNFM。
进一步地,管理节点获取已经与VNFM1建立了连接的VIM5和VIM6的剩余资源的信息,并将VIM4为VNFM1所管理的VNF分配的资源的信息,分别与VIM5和VIM6的剩余资源的信息进行比较,若VIM5和VIM6中存在至少一个VIM的剩余资源信息能够满足VIM4为VNFM1所管理的VNF分配的资源的信息,则管理节点确定VNFM1为满足第二条件的第一VNFM。
需要说明的是,若VNFM1为满足第二条件的第一VNFM,则管理节点确定VNFM1为允许释放连接的VNFM;若VNFM1不为满足第二条件的第一VNFM,则管理节点确定VNFM1、VNFM2以及VNFM3中没有允许释放连接的VNFM,管理节点可以不响应VIM4发送的连接释放请求消息。
进一步地,在方式二中,满足筛选条件的VNFM可能有多个,该多个满足筛选条件的VNFM中也可能存在多个第一VNFM,管理节点可以将该多个第一VNFM均作为允许释放连接的VNFM,也可以随机选择一个第一VNFM作为允许释放连接的VNFM,对此本发明实施例不作限制。
S804、管理节点向VIM发送第一连接释放通知消息,所述第一连接释放通知消息中携带该允许释放连接的VNFM的标识。
在本发明实施例中,当管理节点从多个VNFM中确定允许释放连接的VNFM后,管理节点即可通知VIM可以释放与该允许释放连接的VNFM之间的连接,即该第一连接释放通知消息用于通知该VIM删除其保存的该允许释放连接的VNFM的信息。
S805、VIM接收到第一连接释放通知消息后,根据该允许释放连接的VNFM的标识,确定该允许释放连接的VNFM。
可以理解的是,VIM接收到第一连接释放通知消息后,根据该第一连接释放通知消息中携带的允许释放连接的VNFM的标识,即可确定其与该允许释放连接的VNFM之间的连接允许被释放,即VIM确定可以删除其保存的该允许释放连接的VNFM的信息。
S806、VIM向该允许释放连接的VNFM发送第二连接释放通知消息,该第二连接释放通知消息中携带该VIM的标识。
在本发明实施例中,当VIM确定可以删除其保存的该允许释放连接的VNFM的信息后,该VIM首先需要通过与该允许释放连接的VNFM之间的连接,向该允许释放连接的VNFM发送第二连接释放通知消息,以通知该允许释放连接的VNFM,也删除其保存该VIM的信息。
S807、VIM删除该VIM中保存的该允许释放连接的VNFM的信息。
至此,VIM成功释放了该VIM与该允许释放连接的VNFM的连接。
S808、该允许释放连接的VNFM接收到第二连接释放通知消息后,根据该VIM的标识确定该VIM。
可以理解的是,该允许释放连接的VNFM接收到第二连接释放通知消息后,根据该第二连接释放通知消息中携带的该VIM的标识,即可确定其与该VIM之间的连接允许被释放,即该允许释放连接的VNFM可以删除其保存的该VIM的信息。
S809、该允许释放连接的VNFM删除该允许释放连接的VNFM中保存的该VIM的信息。
至此,该允许释放连接的VNFM也成功释放了与该VIM之间的连接。
需要说明的是,上述S807和上述S808与S809之间的执行顺序,本发明实施例不作限制。
在第三可能的应用场景的第二种可能的方式中,如图10所示,该方法可以包括:
S901、VIM确定多个VNFM的个数达到预设门限值。
S902、VIM向管理节点发送连接释放请求消息,该连接释放请求消息用于请求管理节点确定允许释放连接的VNFM。
S903、管理节点根据该连接释放请求消息,从该多个VNFM中确定允许释放连接的VNFM。
S904、管理节点向VIM发送第一连接释放通知消息,所述第一连接释放通知消息中携带该允许释放连接的VNFM的标识。
S905、VIM接收到第一连接释放通知消息后,根据该允许释放连接的VNFM的标识,确定该允许释放连接的VNFM。
具体的,上述S901-S905的具体实现方式,如图9所示的实施例中S801-S805的具体实现方式相同,上述S901-S905的具体实现方式可以参见如图9所示实施例中的相关描述,此处不再赘述。
S906、VIM删除该VIM中保存的该允许释放连接的VNFM的信息。
至此,VIM成功释放了该VIM与该允许释放连接的VNFM的连接。
S907、管理节点向该允许释放连接的VNFM发送第二连接释放通知消息,该第二连接释放通知消息中携带该VIM的标识。
需要说明的是,在第三种可能的应用场景的第二种可能的实现方式中,当管理节点从多个VNFM中确定允许释放连接的VNFM后,管理节点可以直接向该允许释放连接的VNFM发送第二连接释放通 知消息,以通知该允许释放连接的VNFM也删除其保存该VIM的信息。
S908、该允许释放连接的VNFM接收到第二连接释放通知消息后,根据该VIM的标识确定该VIM。
S909、该允许释放连接的VNFM删除该允许释放连接的VNFM中保存的该VIM的信息。
至此,该允许释放连接的VNFM也成功释放了与该VIM之间的连接。
需要说明的是,需要说明的是,上述S904-S906和上述S907-S909的先后执行顺序本发明实施例不作具体限制。
可选的,在本发明实施例中,当VIM和该允许释放连接的VNFM均成功释放了它们之间的连接后,该VIM和该允许释放连接的VNFM还可以向管理节点发送确认消息,以使得管理节点确定该VIM与该允许释放连接的VNFM之间的连接已经被成功释放,进而管理节点可以对该资源映射表进行更新。
在第三种可能的应用场景中,通过本发明实施例提供的释放连接的方法,使得VIM在确定已经与其建立连接的多个VNFM的个数达到预设门限值后,及时向管理节点发送连接释放请求消息,以请求管理节点从该多个VNFM中确定允许释放连接的VNFM。当管理节点从该多个VNFM中确定允许释放连接的VNFM后,管理节点会通知该VIM和该允许释放连接的VNFM释放该VIM和该允许释放连接的VNFM之间的连接,从而节省该VIM和该允许释放连接的VNFM的连接资源,进而当还未与该VIM建立连接的其他VNFM,请求该VIM为该其他VNFM所管理的VNF分配资源时,该VIM有空闲的连接资源来建立与该其他VNFM之间的连接,以使得该VIM能够为该VNF分配资源。
本发明实施例提供一种释放连接的方法,包括第一节点从多个第二节点中确定允许释放连接的第二节点,并删除第一节点中保存的允许释放连接的第二节点的信息,其中,该多个第二节点为已经 与第一节点建立连接的节点。通过该方法,第一节点释放与允许释放连接的第二节点之间的连接,以节省第一节点的连接资源,从而使得第一节点具有空闲的连接资源来建立与其他第二节点之间的新的连接,进而使得第一节点能够与该其他第二节点进行通信。
实施例三
如图11所示,本发明实施例提供一种释放连接的装置,所述释放连接的装置可以是如图2,或如图4至如图10中的任一附图所示的实施例中所述的第一节点的实体装置,也可以是NFV系统中能够执行所述第一节点能够执行的方法流程的一个逻辑功能模块所在的实体装置,该实体装置可以独立安装在所述第一节点的实体装置内,也可以为一个能够与所述第一节点的实体装置通信的实体装置。该装置还可以通过芯片的形式呈现,该芯片中承载了能够实现所述第一节点能够执行的方法流程的应用程序。
所述释放连接的装置可以包括:
确定单元10,用于从多个第二节点中确定允许释放连接的第二节点,所述多个第二节点为已经与第一节点建立连接的节点。
删除单元11,用于删除所述第一节点中保存的所述确定单元10确定的所述允许释放连接的第二节点的信息。
可选的,所述确定单元10,具体用于接收管理节点发送的第一连接释放通知消息,所述第一连接释放通知消息中携带所述允许释放连接的第二节点的标识。
所述确定单元10,具体用于根据所述允许释放连接的第二节点的标识,确定所述允许释放连接的第二节点。
可选的,结合图11,如图12所示,所述释放连接的装置还包括发送单元12。
所述发送单元12,用于在所述确定单元10接收管理节点发送的第一连接释放通知消息之前,向所述管理节点发送连接释放请求消息,所述连接释放请求消息用于请求所述管理节点确定所述允许释放连接的第二节点。
可选的,所述第一节点为VNFM,所述多个第二节点为多个VIM;或者,所述第一节点为VIM,所述多个第二节点为多个VNFM。
可选的,所述第一节点为VNFM,所述多个第二节点为多个VIM。
若所述多个VIM中存在与所述VNFM没有资源管理关系的VIM,则所述确定单元10确定的所述允许释放连接的第二节点为所述多个VIM中与所述VNFM没有资源管理关系的VIM。
或者,若所述多个VIM中不存在与所述VNFM没有资源管理关系的VIM,则所述确定单元10确定的所述允许释放连接的第二节点为满足第一条件的第一VIM。
其中,所述第一条件为所述多个VIM中的第一VIM为所述VNFM所管理的VNF分配的资源,允许由所述多个VIM中的另一个VIM为所述VNF分配。
可选的,所述发送单元12,还用于在所述确定单元10从多个第二节点中确定允许释放连接的第二节点之后,所述删除单元11删除所述第一节点中保存的所述允许释放连接的第二节点的信息之前,向所述允许释放连接的第二节点发送第二连接释放通知消息,所述第二连接释放通知消息中携带所述第一节点的标识,所述第二连接释放通知消息用于通知所述允许释放连接的第二节点,删除所述允许释放连接的第二节点中保存的所述第一节点的标识指示的所述第一节点的信息。
本发明实施例提供一种释放连接的装置,能够从多个第二节点中确定允许释放连接的第二节点,并删除第一节点中保存的允许释放连接的第二节点的信息,其中,该多个第二节点为已经与第一节点建立连接的节点。通过本发明实施例提供的装置,第一节点能够释放与允许释放连接的第二节点之间的连接,以节省第一节点的连接资源,从而使得第一节点具有空闲的连接资源来建立与其他第二节点之间的新的连接,进而使得第一节点能够与该其他第二节点进行通信。
如图13所示,本发明实施例提供一种释放连接的装置,所述释放连接的装置可以是如图3至如图7或者如图9至如图10中的任一附图所示的实施例中所述的管理节点的实体装置,也可以是NFV系统中能够执行所述管理节点能够执行的方法流程的一个逻辑功能模块所在的实体装置,该实体装置可以独立安装在所述管理节点的实体装置内,也可以为一个能够与所述管理节点的实体装置通信的实体装置。该装置还可以通过芯片的形式呈现,该芯片中承载了能够实现所述管理节点能够执行的方法流程的应用程序。
所述释放连接的装置可以包括:
确定单元20,用于从多个第二节点中确定允许释放连接的第二节点,所述多个第二节点为已经与第一节点建立连接的节点。
发送单元21,用于向所述第一节点发送第一连接释放通知消息,所述第一连接释放通知消息中携带所述确定单元20确定的所述允许释放连接的第二节点的标识,所述第一连接释放通知消息用于通知所述第一节点删除所述第一节点中保存的所述允许释放连接的第二节点的信息。
可选的,若所述多个第二节点中存在与所述第一节点没有资源管理关系的第二节点,则所述确定单元20确定的所述允许释放连接的第二节点为所述多个第二节点中与所述第一节点没有资源管理关系的第二节点。
可选的,结合图13,如图14所示,所述释放连接的装置还包括接收单元22。
所述接收单元22,用于在所述确定单元20从多个第二节点中确定允许释放连接的第二节点之前,接收所述第一节点发送的连接释放请求消息,所述连接释放请求消息用于请求所述确定单元确定所述允许释放连接的第二节点。
所述确定单元20,具体用于根据所述接收单元22接收的所述连接释放请求消息,从多个第二节点中确定允许释放连接的第二节点。
可选的,所述第一节点为VNFM,所述多个第二节点为多个VIM;或者,所述第一节点为VIM,所述多个第二节点为多个VNFM。
可选的,所述第一节点为VNFM,所述多个第二节点为多个VIM。
若所述多个VIM中不存在与所述VNFM没有资源管理关系的VIM,则所述确定单元20确定的所述允许释放连接的第二节点为满足第一条件的第一VIM。
其中,所述第一条件为所述多个VIM中的第一VIM为所述VNFM所管理的VNF分配的资源,允许由所述多个VIM中的另一个VIM为所述VNF分配。
可选的,所述第一节点为VIM,所述多个第二节点为多个VNFM.
若所述多个VNFM中不存在与所述VIM没有资源管理关系的VNFM,则所述确定单元20确定的所述允许释放连接的第二节点为满足第二条件的第一VNFM。
其中,所述第二条件为所述VIM为所述多个VNFM中的第一VNFM所管理的VNF分配的资源,允许由已经与所述第一VNFM建立连接的另一个VIM为所述VNF分配。
可选的,所述发送单元21,还用于在所述确定单元20从多个第二节点中确定允许释放连接的第二节点之后,向所述允许释放连接的第二节点发送第二连接释放通知消息,所述第二连接释放通知消息中携带所述第一节点的标识,所述第二连接释放通知消息用于通知所述允许释放连接的第二节点,删除所述允许释放连接的第二节点中保存的所述第一节点的标识指示的所述第一节点的信息。
本发明实施例提供一种释放连接的装置,能够从多个第二节点中确定允许释放连接的第二节点,并向第一节点发送第一连接释放通知消息,该第一连接释放通知消息中携带允许释放连接的第二节点的标识,该第一连接释放通知消息用于通知第一节点,删除第一节点中保存的允许释放连接的第二节点的信息,该多个第二节点为 已经与第一节点建立连接的节点。
通过本发明实施例提供的释放连接的装置,管理节点能够在已经与第一节点建立连接的多个第二节点中选择合适的第二节点,并及时通知第一节点释放与该第二节点之间的连接,以节省第一节点的连接资源,从而使得第一节点具有空闲的连接资源来建立与其他第二节点之间的新的连接,进而使得第一节点能够与该其他第二节点进行通信。
实施例四
如图15所示,本发明实施例提供一种释放连接的装置,所述释放连接的装置可以是上述实施例中所述的第一节点所在的实体装置,也可以为一个能够与所述第一节点所在的实体装置通信的实体装置。所述释放连接的装置能够执行所述第一节点能够执行的方法流程,具体的,所述释放连接的装置可以包括:处理器30、存储器31、通信接口32、以及系统总线33。所述处理器30、所述存储器31以及通信接口32之间通过所述系统总线33连接并完成相互间的通信。
所述处理器30可以是一个中央处理器(英文:central processing unit,缩写:CPU),或者是特定集成电路(英文:application specific integrated circuit,缩写:ASIC),或者是被配置成实施本发明实施例的一个或多个集成电路。
所述存储器31可以包括易失性存储器(英文:volatile memory),例如随机存取存储器(英文:random-access memory,缩写:RAM);所述存储器31也可以包括非易失性存储器(英文:non-volatile memory),例如只读存储器(英文:read-only memory,缩写:ROM),快闪存储器(英文:flash memory),硬盘(英文:hard disk drive,缩写:HDD)或固态硬盘(英文:solid-state drive,缩写:SSD);所述存储器31还可以包括上述种类的存储器的组合。
所述通信接口32用于与其他节点进行交互,例如与第二节点、管理节点等功能节点进行交互。
当所述释放连接的装置运行时,所述处理器30和所述存储器31可以执行图2、或如图4至如图10中的任一附图所述的方法流程,具体包括:
所述处理器30,用于从多个第二节点中确定允许释放连接的第二节点,并删除所述第一节点中保存的所述允许释放连接的第二节点的信息,所述多个第二节点为已经与第一节点建立连接的节点;所述存储器31,用于存储所述允许释放连接的第二节点的信息的代码,以及控制所述处理器30完成上述过程的软件程序,从而所述处理器30通过执行所述软件程序并调用所述允许释放连接的第二节点的信息的代码,以完成上述过程。
可选的,所述处理器30,具体用于接收管理节点发送的第一连接释放通知消息,所述第一连接释放通知消息中携带所述允许释放连接的第二节点的标识。
所述处理器30,具体用于根据所述允许释放连接的第二节点的标识,确定所述允许释放连接的第二节点。
可选的,所述处理器30,还用于在接收管理节点发送的第一连接释放通知消息之前,向所述管理节点发送连接释放请求消息,所述连接释放请求消息用于请求所述管理节点确定所述允许释放连接的第二节点。
可选的,所述第一节点为VNFM,所述多个第二节点为多个虚拟机基础设施管理节点VIM;或者,所述第一节点为VIM,所述多个第二节点为多个VNFM。
可选的,所述第一节点为VNFM,所述多个第二节点为多个VIM。
若所述多个VIM中存在与所述VNFM没有资源管理关系的VIM,则所述处理器30确定的所述允许释放连接的第二节点为所述多个VIM中与所述VNFM没有资源管理关系的VIM。
或者,若所述多个VIM中不存在与所述VNFM没有资源管理关系的VIM,则所述处理器30确定的所述允许释放连接的第二节点 为满足第一条件的第一VIM。
其中,所述第一条件为所述多个VIM中的第一VIM为所述VNFM所管理的虚拟网络功能VNF分配的资源,允许由所述多个VIM中的另一个VIM为所述VNF分配。
可选的,所述处理器30,还用于在从多个第二节点中确定允许释放连接的第二节点之后,删除所述第一节点中保存的所述允许释放连接的第二节点的信息之前,向所述允许释放连接的第二节点发送第二连接释放通知消息,所述第二连接释放通知消息中携带所述第一节点的标识,所述第二连接释放通知消息用于通知所述允许释放连接的第二节点,删除所述允许释放连接的第二节点中保存的所述第一节点的标识指示的所述第一节点的信息。
本发明实施例提供一种释放连接的装置,能够从多个第二节点中确定允许释放连接的第二节点,并删除第一节点中保存的允许释放连接的第二节点的信息,其中,该多个第二节点为已经与第一节点建立连接的节点。通过本发明实施例提供的装置,第一节点能够释放与允许释放连接的第二节点之间的连接,以节省第一节点的连接资源,从而使得第一节点具有空闲的连接资源来建立与其他第二节点之间的新的连接,进而使得第一节点能够与该其他第二节点进行通信。
如图16所示,本发明实施例提供一种释放连接的装置,所述释放连接的装置可以是上述实施例中所述的管理节点所在的实体装置,也可以为一个能够与所述管理节点所在的实体装置通信的实体装置。所述释放连接的装置能够执行所述管理节点能够执行的方法流程,具体的,所述释放连接的装置可以包括:处理器40、存储器41、通信接口42、以及系统总线43。所述处理器40、所述存储器41以及通信接口42之间通过所述系统总线43连接并完成相互间的通信。
所述处理器40可以是一个CPU,或者是ASIC,或者是被配置成实施本发明实施例的一个或多个集成电路。
所述存储器41可以包括易失性存储器,例如RAM;所述存储器41也可以包括非易失性存储器,例如ROM,快闪存储器,HDD或SSD;所述存储器41还可以包括上述种类的存储器的组合。
所述通信接口42用于与其他节点进行交互,例如与第一节点等功能节点进行交互。
当所述释放连接的装置运行时,所述处理器40和所述存储器41可以执行图3至图7或如图9至如图10中的任一附图所述的方法流程,具体包括:
处理器40,用于从多个第二节点中确定允许释放连接的第二节点,并向所述第一节点发送第一连接释放通知消息,所述第一连接释放通知消息中携带所述允许释放连接的第二节点的标识,所述第一连接释放通知消息用于通知所述第一节点,删除所述第一节点中保存的所述允许释放连接的第二节点的信息,所述多个第二节点为已经与第一节点建立连接的节点;所述存储器41,用于存储所述第一连接释放通知消息的代码、所述允许释放连接的第二节点的标识的代码,以及控制所述处理器40完成上述过程的软件程序,从而所述处理器40通过执行所述软件程序并调用所述第一连接释放通知消息的代码、所述允许释放连接的第二节点的标识的代码,以完成上述过程。
可选的,若所述多个第二节点中存在与所述第一节点没有资源管理关系的第二节点,则所述处理器40确定的所述允许释放连接的第二节点为所述多个第二节点中与所述第一节点没有资源管理关系的第二节点。
可选的,所述处理器40,还用于在所述确定单元从多个第二节点中确定允许释放连接的第二节点之前,接收所述第一节点发送的连接释放请求消息,所述连接释放请求消息用于请求所述确定单元确定所述允许释放连接的第二节点。
所述处理器40,具体用于根据所述连接释放请求消息,从多个第二节点中确定允许释放连接的第二节点。
可选的,所述第一节点为VNFM,所述多个第二节点为多个VIM;或者,所述第一节点为VIM,所述多个第二节点为多个VNFM。
可选的,所述第一节点为VNFM,所述多个第二节点为多个VIM。
若所述多个VIM中不存在与所述VNFM没有资源管理关系的VIM,则所述处理器40确定的所述允许释放连接的第二节点为满足第一条件的第一VIM。
其中,所述第一条件为所述多个VIM中的第一VIM为所述VNFM所管理的虚拟网络功能VNF分配的资源,允许由所述多个VIM中的另一个VIM为所述VNF分配。
可选的,所述第一节点为VIM,所述多个第二节点为多个VNFM。
若所述多个VNFM中不存在与所述VIM没有资源管理关系的VNFM,则所述处理器40确定的所述允许释放连接的第二节点为满足第二条件的第一VNFM。
其中,所述第二条件为所述VIM为所述多个VNFM中的第一VNFM所管理的VNF分配的资源,允许由已经与所述第一VNFM建立连接的另一个VIM为所述VNF分配。
可选的,所述处理器40,还用于在从多个第二节点中确定允许释放连接的第二节点之后,向所述允许释放连接的第二节点发送第二连接释放通知消息,所述第二连接释放通知消息中携带所述第一节点的标识,所述第二连接释放通知消息用于通知所述允许释放连接的第二节点,删除所述允许释放连接的第二节点中保存的所述第一节点的标识指示的所述第一节点的信息。
本发明实施例提供一种释放连接的装置,能够从多个第二节点中确定允许释放连接的第二节点,并向第一节点发送第一连接释放通知消息,该第一连接释放通知消息中携带允许释放连接的第二节点的标识,该第一连接释放通知消息用于通知第一节点,删除第一节点中保存的允许释放连接的第二节点的信息,该多个第二节点为 已经与第一节点建立连接的节点。
通过本发明实施例提供的释放连接的装置,管理节点能够在已经与第一节点建立连接的多个第二节点中选择合适的第二节点,并及时通知第一节点释放与该第二节点之间的连接,以节省第一节点的连接资源,从而使得第一节点具有空闲的连接资源来建立与其他第二节点之间的新的连接,进而使得第一节点能够与该其他第二节点进行通信。
实施例五
如图17所示,本发明实施例提供一种通信系统,该通信系统可以包括如图11或如图12所示的释放连接的装置,如图13或如图14所示的释放连接的装置,以及第二节点;或者,该通信系统可以包括如图15所示的释放连接的装置,如图16所示的释放连接的装置,以及第二节点。
其中,如图11所示的释放连接的装置、如图12所示的释放连接的装置,以及如图15所示的释放连接的装置,都可以称为第一节点;如图13所示的释放连接的装置、如图14所示的释放连接的装置,以及如图16所示的释放连接的装置,都可以称为管理节点。
在本发明实施例提供的通信系统中的第一节点能够从多个第二节点中确定允许释放连接的第二节点,并删除第一节点中保存的允许释放连接的第二节点的信息;管理节点能够从多个第二节点中确定允许释放连接的第二节点,并向第一节点发送第一连接释放通知消息,该第一连接释放通知消息中携带允许释放连接的第二节点的标识,该第一连接释放通知消息用于通知第一节点,删除第一节点中保存的允许释放连接的第二节点的信息。其中,该多个第二节点为已经与第一节点建立连接的节点。
需要说明的是,在本发明实施例中第一节点可以为VNFM,也可以为VIM。具体的,当第一节点为VNFM时,第二节点为VIM,且该VIM已经与该VNFM建立连接;当第一节点为VIM时,该第二节点为VNFM,且该VNFM已经与该VIM建立连接。
可以理解的是,本发明实施例提供的通信系统中的第一节点,能够执行如图2至如图10中的任一幅图所述的释放连接的方法,该对第一节点内的各模块或器件的具体功能和执行方法的流程可以参照如图2至如图10中的任一幅图所示的实施例中的描述,此处不再赘述。
本发明实施例提供的通信系统中的管理节点,能够执行如图3至如图7或如图9至如图10中的任一幅图所述的释放连接的方法,该对管理节点内的各模块或器件的具体功能和执行方法的流程可以参照如图3至如图7或如图9至如图10中的任一幅图所示的实施例中的描述,此处不再赘述。
通过本发明实施例提供的通信系统,管理节点能够在已经与第一节点建立连接的多个第二节点中选择合适的第二节点,并及时通知第一节点释放与该第二节点之间的连接,以节省第一节点的连接资源,从而使得第一节点具有空闲的连接资源来建立与其他第二节点之间的新的连接,进而使得第一节点能够与该其他第二节点进行通信。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,仅以上述各功能模块的划分进行举例说明,实际应用中,可以根据需要而将上述功能分配由不同的功能模块完成,即将装置的内部结构划分成不同的功能模块,以完成以上描述的全部或者部分功能。上述描述的系统,装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的系统,装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述模块或单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信 连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本发明各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)或处理器执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(英文全称:Read-Only Memory,英文缩写:ROM)、随机存取存储器(英文全称:Random Access Memory,英文缩写:RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述,仅为本发明的具体实施方式,但本发明的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本发明揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本发明的保护范围之内。因此,本发明的保护范围应所述以权利要求的保护范围为准。

Claims (27)

  1. 一种释放连接的方法,其特征在于,包括:
    第一节点从多个第二节点中确定允许释放连接的第二节点,所述多个第二节点为已经与所述第一节点建立连接的节点;
    所述第一节点删除所述第一节点中保存的所述允许释放连接的第二节点的信息。
  2. 根据权利要求1所述的方法,其特征在于,所述第一节点从多个第二节点中确定允许释放连接的第二节点,包括:
    所述第一节点接收管理节点发送的第一连接释放通知消息,所述第一连接释放通知消息中携带所述允许释放连接的第二节点的标识;
    所述第一节点根据所述允许释放连接的第二节点的标识,确定所述允许释放连接的第二节点。
  3. 根据权利要求2所述的方法,其特征在于,所述第一节点接收管理节点发送的第一连接释放通知消息之前,所述方法还包括:
    所述第一节点向所述管理节点发送连接释放请求消息,所述连接释放请求消息用于请求所述管理节点确定所述允许释放连接的第二节点。
  4. 根据权利要求1-3任一项所述的方法,其特征在于,
    所述第一节点为虚拟网络功能管理节点VNFM,所述多个第二节点为多个虚拟机基础设施管理节点VIM;或者,
    所述第一节点为VIM,所述多个第二节点为多个VNFM。
  5. 根据权利要求1所述的方法,其特征在于,所述第一节点为VNFM,所述多个第二节点为多个VIM,
    若所述多个VIM中存在与所述VNFM没有资源管理关系的VIM,则所述允许释放连接的第二节点为所述多个VIM中与所述VNFM没有资源管理关系的VIM;或者,
    若所述多个VIM中不存在与所述VNFM没有资源管理关系的VIM,则所述允许释放连接的第二节点为满足第一条件的第一VIM,
    其中,所述第一条件为所述多个VIM中的第一VIM为所述 VNFM所管理的虚拟网络功能VNF分配的资源,允许由所述多个VIM中的另一个VIM为所述VNF分配。
  6. 根据权利要求1-5任一项所述的方法,其特征在于,所述第一节点从多个第二节点中确定允许释放连接的第二节点之后,所述第一节点删除所述第一节点中保存的所述允许释放连接的第二节点的信息之前,所述方法还包括:
    所述第一节点向所述允许释放连接的第二节点发送第二连接释放通知消息,所述第二连接释放通知消息中携带所述第一节点的标识,所述第二连接释放通知消息用于通知所述允许释放连接的第二节点,删除所述允许释放连接的第二节点中保存的所述第一节点的标识指示的所述第一节点的信息。
  7. 一种释放连接的方法,其特征在于,包括:
    管理节点从多个第二节点中确定允许释放连接的第二节点,所述多个第二节点为已经与第一节点建立连接的节点;
    所述管理节点向所述第一节点发送第一连接释放通知消息,所述第一连接释放通知消息中携带所述允许释放连接的第二节点的标识,所述第一连接释放通知消息用于通知所述第一节点,删除所述第一节点中保存的所述允许释放连接的第二节点的信息。
  8. 根据权利要求7所述的方法,其特征在于,
    若所述多个第二节点中存在与所述第一节点没有资源管理关系的第二节点,则所述允许释放连接的第二节点为所述多个第二节点中与所述第一节点没有资源管理关系的第二节点。
  9. 根据权利要求7或8所述的方法,其特征在于,所述管理节点从多个第二节点中确定允许释放连接的第二节点之前,所述方法还包括:
    所述管理节点接收所述第一节点发送的连接释放请求消息,所述连接释放请求消息用于请求所述管理节点确定所述允许释放连接的第二节点;
    所述管理节点从多个第二节点中确定允许释放连接的第二节点, 包括:
    所述管理节点根据所述连接释放请求消息,从所述多个第二节点中确定所述允许释放连接的第二节点。
  10. 根据权利要求7-9任一项所述的方法,其特征在于,
    所述第一节点为虚拟网络功能管理节点VNFM,所述多个第二节点为多个虚拟机基础设施管理节点VIM;或者,
    所述第一节点为VIM,所述多个第二节点为多个VNFM。
  11. 根据权利要求9所述的方法,其特征在于,所述第一节点为VNFM,所述多个第二节点为多个VIM,
    若所述多个VIM中不存在与所述VNFM没有资源管理关系的VIM,则所述允许释放连接的第二节点为满足第一条件的第一VIM,
    其中,所述第一条件为所述多个VIM中的第一VIM为所述VNFM所管理的虚拟网络功能VNF分配的资源,允许由所述多个VIM中的另一个VIM为所述VNF分配。
  12. 根据权利要求9所述的方法,其特征在于,所述第一节点为VIM,所述多个第二节点为多个VNFM,
    若所述多个VNFM中不存在与所述VIM没有资源管理关系的VNFM,则所述允许释放连接的第二节点为满足第二条件的第一VNFM,
    其中,所述第二条件为所述VIM为所述多个VNFM中的第一VNFM所管理的VNF分配的资源,允许由已经与所述第一VNFM建立连接的另一个VIM为所述VNF分配。
  13. 根据权利要求7-12任一项所述的方法,其特征在于,所述管理节点从多个第二节点中确定允许释放连接的第二节点之后,所述方法还包括:
    所述管理节点向所述允许释放连接的第二节点发送第二连接释放通知消息,所述第二连接释放通知消息中携带所述第一节点的标识,所述第二连接释放通知消息用于通知所述允许释放连接的第二节点,删除所述允许释放连接的第二节点中保存的所述第一节点的标识 指示的所述第一节点的信息。
  14. 一种释放连接的装置,其特征在于,包括:
    确定单元,用于从多个第二节点中确定允许释放连接的第二节点,所述多个第二节点为已经与第一节点建立连接的节点;
    删除单元,用于删除所述第一节点中保存的所述确定单元确定的所述允许释放连接的第二节点的信息。
  15. 根据权利要求14所述的释放连接的装置,其特征在于,
    所述确定单元,具体用于接收管理节点发送的第一连接释放通知消息,所述第一连接释放通知消息中携带所述允许释放连接的第二节点的标识;
    所述确定单元,具体用于根据所述允许释放连接的第二节点的标识,确定所述允许释放连接的第二节点。
  16. 根据权利要求15所述的释放连接的装置,其特征在于,所述释放连接的装置还包括发送单元,
    所述发送单元,用于在所述确定单元接收管理节点发送的第一连接释放通知消息之前,向所述管理节点发送连接释放请求消息,所述连接释放请求消息用于请求所述管理节点确定所述允许释放连接的第二节点。
  17. 根据权利要求14-16任一项所述的释放连接的装置,其特征在于,
    所述第一节点为虚拟网络功能管理节点VNFM,所述多个第二节点为多个虚拟机基础设施管理节点VIM;或者,
    所述第一节点为VIM,所述多个第二节点为多个VNFM。
  18. 根据权利要求14所述的释放连接的装置,其特征在于,所述第一节点为VNFM,所述多个第二节点为多个VIM,
    若所述多个VIM中存在与所述VNFM没有资源管理关系的VIM,则所述确定单元确定的所述允许释放连接的第二节点为所述多个VIM中与所述VNFM没有资源管理关系的VIM;或者,
    若所述多个VIM中不存在与所述VNFM没有资源管理关系的 VIM,则所述确定单元确定的所述允许释放连接的第二节点为满足第一条件的第一VIM,
    其中,所述第一条件为所述多个VIM中的第一VIM为所述VNFM所管理的虚拟网络功能VNF分配的资源,允许由所述多个VIM中的另一个VIM为所述VNF分配。
  19. 根据权利要求16-18任一项所述的释放连接的装置,其特征在于,
    所述发送单元,还用于在所述确定单元从多个第二节点中确定允许释放连接的第二节点之后,所述删除单元删除所述第一节点中保存的所述允许释放连接的第二节点的信息之前,向所述允许释放连接的第二节点发送第二连接释放通知消息,所述第二连接释放通知消息中携带所述第一节点的标识,所述第二连接释放通知消息用于通知所述允许释放连接的第二节点,删除所述允许释放连接的第二节点中保存的所述第一节点的标识指示的所述第一节点的信息。
  20. 一种释放连接的装置,其特征在于,包括:
    确定单元,用于从多个第二节点中确定允许释放连接的第二节点,所述多个第二节点为已经与第一节点建立连接的节点;
    发送单元,用于向所述第一节点发送第一连接释放通知消息,所述第一连接释放通知消息中携带所述确定单元确定的所述允许释放连接的第二节点的标识,所述第一连接释放通知消息用于通知所述第一节点,删除所述第一节点中保存的所述允许释放连接的第二节点的信息。
  21. 根据权利要求20所述的释放连接的装置,其特征在于,
    若所述多个第二节点中存在与所述第一节点没有资源管理关系的第二节点,则所述确定单元确定的所述允许释放连接的第二节点为所述多个第二节点中与所述第一节点没有资源管理关系的第二节点。
  22. 根据权利要求20或21所述的释放连接的装置,其特征在于,所述释放连接的装置还包括接收单元,
    所述接收单元,用于在所述确定单元从多个第二节点中确定允许 释放连接的第二节点之前,接收所述第一节点发送的连接释放请求消息,所述连接释放请求消息用于请求所述确定单元确定所述允许释放连接的第二节点;
    所述确定单元,具体用于根据所述接收单元接收的所述连接释放请求消息,从多个第二节点中确定允许释放连接的第二节点。
  23. 根据权利要求20-22任一项所述的释放连接的装置,其特征在于,
    所述第一节点为虚拟网络功能管理节点VNFM,所述多个第二节点为多个虚拟机基础设施管理节点VIM;或者,
    所述第一节点为VIM,所述多个第二节点为多个VNFM。
  24. 根据权利要求22所述的释放连接的装置,其特征在于,所述第一节点为VNFM,所述多个第二节点为多个VIM,
    若所述多个VIM中不存在与所述VNFM没有资源管理关系的VIM,则所述确定单元确定的所述允许释放连接的第二节点为满足第一条件的第一VIM,
    其中,所述第一条件为所述多个VIM中的第一VIM为所述VNFM所管理的虚拟网络功能VNF分配的资源,允许由所述多个VIM中的另一个VIM为所述VNF分配。
  25. 根据权利要求22所述的释放连接的装置,其特征在于,所述第一节点为VIM,所述多个第二节点为多个VNFM,
    若所述多个VNFM中不存在与所述VIM没有资源管理关系的VNFM,则所述确定单元确定的所述允许释放连接的第二节点为满足第二条件的第一VNFM,
    其中,所述第二条件为所述VIM为所述多个VNFM中的第一VNFM所管理的VNF分配的资源,允许由已经与所述第一VNFM建立连接的另一个VIM为所述VNF分配。
  26. 根据权利要求20-25任一项所述的释放连接的装置,其特征在于,
    所述发送单元,还用于在所述确定单元从多个第二节点中确定允 许释放连接的第二节点之后,向所述允许释放连接的第二节点发送第二连接释放通知消息,所述第二连接释放通知消息中携带所述第一节点的标识,所述第二连接释放通知消息用于通知所述允许释放连接的第二节点,删除所述允许释放连接的第二节点中保存的所述第一节点的标识指示的所述第一节点的信息。
  27. 一种通信系统,其特征在于,包括:
    如权利要求14-19任一项所述的释放连接的装置,和如权利要求20-26任一项所述的释放连接的装置。
PCT/CN2015/081398 2015-06-12 2015-06-12 一种释放连接的方法、装置及系统 WO2016197395A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2015/081398 WO2016197395A1 (zh) 2015-06-12 2015-06-12 一种释放连接的方法、装置及系统
CN201580080506.0A CN107615872B (zh) 2015-06-12 2015-06-12 一种释放连接的方法、装置及系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/081398 WO2016197395A1 (zh) 2015-06-12 2015-06-12 一种释放连接的方法、装置及系统

Publications (1)

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

Family

ID=57503150

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/081398 WO2016197395A1 (zh) 2015-06-12 2015-06-12 一种释放连接的方法、装置及系统

Country Status (2)

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

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 (zh) * 2009-11-06 2011-05-12 华为技术有限公司 负载控制方法和设备及通信系统

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 Kddi株式会社 光クロスコネクト装置と伝送装置の連係方式
WO2013064170A1 (en) * 2011-10-31 2013-05-10 Telefonaktiebolaget L M Ericsson (Publ) Discovery and disconnection of client addresses in an access node for an ip network
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 (zh) * 2009-11-06 2011-05-12 华为技术有限公司 负载控制方法和设备及通信系统

Also Published As

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

Similar Documents

Publication Publication Date Title
RU2681371C1 (ru) Система и способ управления ресурсами
EP3468151B1 (en) Acceleration resource processing method and apparatus
EP3382939B1 (en) Troubleshooting method, apparatus, and system based on network function virtualization
JP6636142B2 (ja) スケールアウト関連付けの方法および装置、ならびにシステム
CN107113193B (zh) 一种确定vnf的处理策略的方法、装置及系统
US20180146031A1 (en) Life Cycle Management Method and Apparatus
CN110221918B (zh) 一种ns与vnf的关联方法、装置及系统
EP3470984B1 (en) Method, device, and system for managing disk lock
WO2018171392A1 (zh) 一种虚拟机扩缩容方法及虚拟管理设备
CN110086681A (zh) 虚拟网络策略的配置方法、系统及其虚拟网元和网管系统
WO2017148249A1 (zh) 配置资源的方法及其网络设备
EP4220396B1 (en) Acceleration resource scheduling method and acceleration system
CN107005452B (zh) 一种网络功能虚拟化资源处理方法及虚拟网络功能管理器
WO2016082078A1 (zh) 路径管理的系统、装置和方法
WO2016197395A1 (zh) 一种释放连接的方法、装置及系统
CN107534678B (zh) 建立vnfm与vim之间的连接的方法、装置及系统
WO2017041650A1 (zh) 用于扩展分布式一致性服务的方法和设备
WO2018196651A1 (zh) 资源管理的方法和设备
WO2017070963A1 (zh) 一种虚拟资源的部署方法、装置及系统
CN107431634B (zh) 一种建立vnfm之间的接口的方法、装置及系统
WO2018036310A1 (zh) 一种管理网络功能虚拟化管理编排实体的方法和装置
WO2016192102A1 (zh) 一种组通信方法、装置及设备
WO2016107135A1 (zh) 内存管理方法及系统和计算机存储介质
CN108182104A (zh) 一种分配虚拟处理器的方法、设备及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 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