WO2017211141A1 - 资源释放方法、系统、装置及计算机存储介质 - Google Patents

资源释放方法、系统、装置及计算机存储介质 Download PDF

Info

Publication number
WO2017211141A1
WO2017211141A1 PCT/CN2017/082057 CN2017082057W WO2017211141A1 WO 2017211141 A1 WO2017211141 A1 WO 2017211141A1 CN 2017082057 W CN2017082057 W CN 2017082057W WO 2017211141 A1 WO2017211141 A1 WO 2017211141A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
flow
flow release
service function
release message
Prior art date
Application number
PCT/CN2017/082057
Other languages
English (en)
French (fr)
Inventor
井惟栋
蔡洪波
王军
高申存
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2017211141A1 publication Critical patent/WO2017211141A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/76—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements

Definitions

  • the present invention relates to the field of mobile communication technologies, and in particular, to a resource release method, system, device, and computer storage medium in a service function chain.
  • a service function chain includes multiple function nodes, including a classifier, a service function forwarder (SFF), a service function (SF), and a service function agent (SFC). Proxy).
  • the packet is encapsulated according to the SFC encapsulation information, so that the packet can be flexibly forwarded between the SFC nodes without changing the basic network device.
  • the packets can be forwarded independently of the destination address.
  • the packets can be flexibly transmitted between SFC nodes.
  • the SF or SFC Proxy will establish a context for each flow that passes through and save the relevant context information. These context information should be kept until the end of the stream. An SF or SFC Proxy will serve a large number of streams, so storing relevant context information for each stream will consume a lot of memory resources.
  • the SF and the SFC Proxy cannot detect the end of the flow in a timely manner, and the resources corresponding to the end of the flow cannot be released in time, and the resource occupancy rate is high.
  • the resource occupancy rate is high.
  • the embodiments of the present invention provide a resource release method, system, device, and computer storage medium in a service function chain.
  • a method for releasing resources in a service function chain comprising:
  • the classifier constructs a flow release message packet when the flow is in the end state, and the flow release message message carries the link information of the flow release identifier and the flow;
  • the classifier sends the flow release message to the corresponding service function forwarder according to the link information
  • the function node After receiving the flow release message, the function node releases the corresponding resource according to the flow release identifier carried in the flow release message.
  • a resource release system in a business function chain comprising:
  • a classifier configured to construct a flow release message message when detecting that the flow is in an end state, the flow release message message carrying link information with a flow release identifier and a flow; and the flow according to the link information
  • the release message packet is sent to the corresponding service function forwarder;
  • the service function forwarder is configured to forward the flow release message to the corresponding function node according to the link information
  • the at least one function node is configured to release the corresponding resource according to the flow release identifier carried in the flow release message packet after receiving the flow release message message.
  • the resource release method and system in the foregoing service function chain after detecting that the flow is in an end state, the classifier constructs a flow release message carrying the link release identifier and the link information of the flow, and sends the message to the service function forwarder to the service function forwarder.
  • Function node After receiving the flow release message, the function node releases the corresponding resource according to the flow release identifier carried in the flow release message.
  • the method and system monitor the state of the flow, and construct and send a flow release message message when the flow is in an end state, so that the function node releases the corresponding resource in time, and can timely sense the end of the flow and release the resource.
  • the operation avoids the problem of degraded service quality due to the inability to release resources in time, and improves the quality of business services.
  • a method for releasing resources in a service function chain comprising:
  • the flow release message When the flow is in the end state, the flow release message is constructed, and the flow release message carries the link information of the flow release identifier and the flow;
  • a resource release device in a service function chain comprising:
  • a packet construction module configured to: when the flow is in the end state, construct a flow release message, where the flow release message carries the link information of the flow release identifier and the flow;
  • the packet sending module is configured to send the flow release message according to the link information, so that the function node that receives the flow release message receives the flow release identifier according to the flow release message in the flow release message Release the corresponding resource.
  • a computer storage medium having stored thereon a computer program, the computer program being executed by a processor to implement the steps of a resource release method in the business function chain.
  • the resource release method, the device, and the computer storage medium in the foregoing service function chain after detecting that the flow is in an end state, construct a flow release message message carrying the link release information and the link information of the flow, and send the message to be received.
  • the function node of the flow release message packet releases the corresponding resource according to the flow release identifier carried in the flow release message packet.
  • the method and the device monitor the state of the flow, and construct and send a flow release message message when the flow is in the end state, so that the function node releases the corresponding resource in time, and can timely sense the end of the flow and perform the resource release operation, thereby avoiding the cause
  • the problem of failure to release resources in time leads to a decline in service quality and improves the quality of business services.
  • a method for releasing resources in a service function chain comprising:
  • a resource release device in a service function chain comprising:
  • the packet receiving module is configured to receive a flow release message that is forwarded by the service function forwarder, where the flow release message carries a flow release identifier;
  • the resource release module is configured to release the corresponding resource according to the flow release identifier carried in the flow release message packet.
  • a computer storage medium having stored thereon a computer program, the computer program being executed by a processor to implement the steps of a resource release method in the business function chain.
  • the resource release method, the device, and the computer storage medium in the service function chain receive the flow release message forwarded by the service function forwarder, and release the corresponding resource according to the flow release identifier carried in the flow release message.
  • the corresponding resource is released, and the resource release operation can be performed in time, thereby avoiding the problem that the service quality is degraded due to the inability to release the resource in time, and improving the service quality of the service.
  • FIG. 1 is a flowchart of a resource release method in a service function chain in an embodiment
  • FIG. 2 is a schematic diagram of a format of an NSH basic header in which an F bit is extended in an embodiment
  • FIG. 3 is a schematic diagram of a format of an FRI in which a mandatory context is extended in an embodiment
  • FIG. 4 is a schematic diagram of a format of an FRI of a variable length context header according to an embodiment
  • FIG. 5 is a flowchart of a resource release method in a service function chain in another embodiment
  • FIG. 6 is a sequence diagram of a resource release method in a service function chain in an embodiment
  • FIG. 7 is a sequence diagram of a resource release method in a service function chain in another embodiment
  • FIG. 8 is a sequence diagram of a resource release method in a service function chain in still another embodiment
  • FIG. 9 is a sequence diagram of a resource release method in a service function chain in still another embodiment.
  • FIG. 10 is a sequence diagram of a resource release method in a service function chain in still another embodiment
  • FIG. 11 is a flowchart of a resource release method in a service function chain in still another embodiment
  • FIG. 13 is a flowchart of a resource release method in a service function chain in still another embodiment
  • FIG. 14 is a schematic structural diagram of a resource release system in a service function chain according to an embodiment
  • 15 is a schematic structural diagram of a resource release system in a service function chain in another embodiment
  • 16 is a schematic structural diagram of a resource release system in a service function chain in still another embodiment
  • 17 is a schematic structural diagram of a resource release system in a service function chain in still another embodiment
  • FIG. 18 is a schematic structural diagram of a resource release apparatus in a service function chain according to an embodiment
  • 19 is a schematic structural diagram of a resource release apparatus in a service function chain in another embodiment
  • FIG. 20 is a schematic structural diagram of a resource release apparatus in a service function chain in still another embodiment.
  • Step S110 The classifier constructs a stream release message message when it detects that the stream is in an end state.
  • the English of the classifier can be expressed as a Classifier, which is a node in the SFC, and the nodes of the SFC further include SFF, SF, and SFC Proxy.
  • the number of classifiers, SFFs, and SFs may be one or more, and the number of SFC Proxys may be zero, one, or multiple.
  • the SFC encapsulation of the packets is performed so that the encapsulated packets can be forwarded independently of the destination address, and the packets are flexibly transmitted between the nodes of the SFC.
  • the classifier is responsible for identifying the stream and associating the stream with the SFC, and sending the stream to the corresponding SFC for processing.
  • the flow release (FR) message carries the flow release indicator (FRI) and the link information of the flow.
  • the FR message is a packet carrying the flow-related information encapsulated in the SFC and forwarded along the SFC path.
  • the FRI is an identifier indicating the flow release information, and is used for subsequent identification of the FR message.
  • the link information is used to indicate the processing path of the flow in the SFC, and the SFC forwards the flow according to the link information.
  • the link information may include a Service Path Identifier (SPI) and a Service Index (SI).
  • SPI Service Path Identifier
  • SI Service Index
  • the initial packet (original packet) part of the FR message packet can be constructed by using the corresponding IP quintuple (source address, source port number, protocol number, destination address, destination port number) in the stream.
  • the payload part of the initial message is not required, and the FR message carrying the IP quintuple can indicate the corresponding stream.
  • the classifier When it is detected that the flow is in the end state, the resource occupied by the flow in the SFC needs to be released, and the classifier obtains the link information of the corresponding flow, and performs SFC encapsulation according to the link information to obtain the FR carrying the FRI and the link information.
  • Message message The specific manner in which the classifier detects that the flow is in the end state is not unique. It may be the state detection of the direct convection, or the detection of the Transmission Control Protocol (TCP) connection by the Deep Packet Inspection (DPI) technology. End signaling to sense the end of the stream.
  • TCP Transmission Control Protocol
  • DPI Deep Packet Inspection
  • the specific manner of carrying the FRI in the FR message is not unique. It can be carried in the basic header of the FR packet or in the context header of the FR packet.
  • Step S120 The classifier sends a flow release message (which can be understood as an FR message) to the corresponding service function forwarder (which can be understood as SFF) according to the link information.
  • a flow release message (which can be understood as an FR message)
  • SFF service function forwarder
  • the classifier can directly send the FR message to the subsequent node on the corresponding SFC according to the link information, that is, the corresponding SFF.
  • Step S130 The service function forwarder (which can be understood as SFF) forwards the flow release message (which can be understood as an FR message) to the corresponding function node according to the link information.
  • SFF service function forwarder
  • the SFF is responsible for forwarding the encapsulated packets according to the information contained in the packets. After receiving the FR message, the SFF forwards the FR message to the corresponding function node according to the carried link information.
  • the number of function nodes can be one or more. When the number of the function nodes is multiple, the SFF may directly send the FR message to all the corresponding function nodes according to the link information, so that the function node performs the resource release operation. The SFF may also forward the FR message to the function node corresponding to the next hop SFC node according to the link information.
  • the FR message may be sent to a function node, and after receiving the FR message returned by the function node, the FR message is continuously sent.
  • the message is sent to the next function node; after the FR message message is sent to a function node for a preset period of time, the FR message message is continuously sent to the next function node, and the specific form is not limited.
  • Step S140 After receiving the flow release message, the function node releases the corresponding resource according to the flow release identifier carried in the flow release message.
  • the function node After receiving the FR message, the function node releases the FRI carried in the FR message. Putting the corresponding resources to avoid the problem of the quality of service caused by the inability to release resources in time.
  • the resource release method in the foregoing service function chain after detecting that the flow is in an end state, the classifier constructs a flow release message carrying the link release identifier and the link information of the flow, and sends the message to the function node via the service function forwarder. .
  • the function node releases the corresponding resource according to the flow release identifier carried in the flow release message.
  • the function node releases the corresponding resource in time, and can sense the end of the flow and perform the resource release operation in time to avoid the failure to release the resource in time.
  • the problem of degrading service quality has improved the quality of business services.
  • the stream release identifier (which may be understood as FRI) is a reserved bit located in the base header of the FR message message.
  • the FRI can select one reserved bit of the basic header of the NSH as the FRI, which is defined as the F bit. As shown in FIG. 2, the F bit is 1 to identify the message that releases the stream. By selecting the reserved bit of the basic header of the FR message as the FRI, the operation is simple and easy to identify.
  • the flow release message carries a flow release identifier (which can be understood as FRI), including: if the service function chain encapsulation format is a fixed length format, the mandatory context header of the flow release message packet is selected. The bit is used as a stream release identifier (which can be understood as FRI). If the service function chain encapsulation format is a variable length format, a variable length context header is generated in the flow release message packet as a flow release identifier (which can be understood as FRI).
  • FRI flow release identifier
  • the NSH encapsulation is taken as an example. Referring to FIG. 3 and FIG. 4, if the NSH encapsulation format is a fixed-length format, the MD type represents the encapsulation format of the NSH, and the MD type is 1 indicating that the encapsulation format of the NSH is a fixed-length format, and the MD type is 2
  • the NSH encapsulation format is a variable length format.
  • a bit of the mandatory context header of the NSH is selected as the FRI, and is defined as the F bit. As shown in FIG. 3, the F bit is 1 to identify the message that releases the stream. If the MD type is 2, a new variable length context header is defined as the FRI. As shown in FIG. 4, if the FRI is 1, the identifier is a message that releases the stream.
  • the TLV Class and Type fields can be determined according to the specific situation, and the C bit is set to 1.
  • the above is to provide two different FRI settings according to the SFC package format. According to the actual situation, the FRI is set correspondingly.
  • the functional node includes a business function (which may be understood as SF) that identifies the encapsulation type of the business function chain.
  • SF business function
  • the number of SFs may be one or more, and the SF may directly identify the encapsulation type of the SFC.
  • the SF supports the packets of the NSH encapsulated flow, and can directly call the corresponding resources to process the flow and save the context information.
  • the SFF sends the FR message to the SF
  • the SF can directly identify the FR message and release the corresponding resource to prevent the end of the stream from continuing to occupy resources.
  • the SF after receiving the FR message that is forwarded by the SFF and releasing the corresponding resource, the SF also detects whether it is located in the last hop on the SFC, and if yes, the resource is released, and the SF may not return the FR message to the SFF; If not, the SF returns a FR message message to the SFF, so that the SFF sends the FR message message to the next SF. It can be understood that in other embodiments, the SFF may also send the FR message message to all SFs simultaneously.
  • the functional node includes a business function agent (which can be understood as an SFC Proxy).
  • the SFC Proxy can be one or more.
  • the SFC Proxy acts as a proxy for the SF that does not support the SFC encapsulation type.
  • the SFC Proxy sends the packet to the SF after being encapsulated and sent to the SF.
  • the incoming message, the SFC Proxy is responsible for encapsulation and then sends it to other nodes.
  • the SFC Proxy acts as a proxy for the SF that does not recognize the encapsulation type of the SFC. It also needs to save the context information when processing the stream.
  • the SFC proxy directly identifies the FR message and releases the corresponding resource to prevent the end of the stream from continuing to occupy resources.
  • the SFC Proxy after receiving the FR message that is forwarded by the SFF and releasing the corresponding resource, the SFC Proxy also detects whether it is located in the last hop of the SFC. If the resource is released, the SFC Proxy may not return the FR message to the SFC Proxy. SFF; if not, the SFC Proxy returns a FR message to the SFF, so that the SFF sends the FR message to the next SFC Proxy. It can be understood that in other embodiments, the SFF may also send the FR message message to all SFC Proxys simultaneously.
  • the function node includes a service function agent (which can be understood as an SFC Proxy) and a service function that can identify the package type of the service function chain (can be understood as SF).
  • a service function agent which can be understood as an SFC Proxy
  • a service function that can identify the package type of the service function chain can be understood as SF.
  • the number of the SF and the SFC Proxy may also be one or more.
  • the SF and the SFC Proxy may release the corresponding resource according to the FR message.
  • the SF and the SFC Proxy may perform resource release at the same time, or may not release the resources at the same time, and the sequence is not unique, and the SFF determines the manner in which the FR message is forwarded according to the link information. If the SFF forwards the FR message to the SF and the SFC Proxy, the resource is released at the same time. If the SFF first forwards the FR message to one of the function nodes, the function node that receives the FR message first releases the resource. . After the SFF forwards the FR message to another function node, the other function node releases the resource.
  • the SFF first forwards the FR message to the SF, and then forwards it to the SFC proxy. After the SFF forwards the FR message to the SF, the SF releases the corresponding resource, and returns the FR message to the SFF when it detects that it is not the last hop on the SFC. The SFF forwards the FR message to the SFC Proxy. The SFC Proxy also releases the corresponding resource and detects whether it is the last hop on the SFC. If the resource is released, the SFC Proxy does not return the FR message to the SFF. If no, the SFC Proxy returns the FR message to the SFF, so that the SFF forwards the FR message again.
  • the SFF may forward the FR message to the SFC Proxy, and then forward the FR message to the SF after receiving the FR message returned by the SFC Proxy.
  • the above provides a corresponding resource release manner for different forms of the function node, and can perform resource adjustment according to different structures of the function node, thereby improving the convenience and comprehensiveness of the resource release operation. It can be understood that the specific form of the function node and the corresponding resource release manner include, but are not limited to, the above embodiments.
  • the foregoing method may further include:
  • Step S150 The function node determines whether it is the last hop on the service function chain according to the link information in the flow release message packet (which can be understood as an FR message packet).
  • the link information in the FR message can indicate the path of the corresponding stream in the SFC.
  • the function node can determine whether it is the last hop on the SFC according to the link information. If yes, the corresponding stream is terminated in the SFC processing path. , the message may not be returned to SFF; if not, step S160 is performed.
  • Step S160 The function node returns the flow release message message to the service function forwarder (which can be understood as SFF).
  • the function node returns the FR message, which can be processed according to the packet of the stream, and the link information in the FR message is modified and then returned to the SFF.
  • the function node When detecting that the last hop is not located on the SFC, the function node returns the FR message message to the SFF, so that the SFF forwards the FR message message to the next function node for resource release operation.
  • Step S170 The service function forwarder (which can be understood as FRI) receives the returned flow release message message (which can be understood as an FR message message), and sends the flow release message message to the next function node according to the link information.
  • FRI service function forwarder
  • next function node After releasing the corresponding resource, if the next function is still not the last hop on the SFC, the next function node continues to return the FR message to the SFF until the function node located at the last hop of the SFC also releases the corresponding Resources.
  • step S150 if the function node is located in the last hop on the SFC, the FR message can also be returned to the SFF. Since the resource release has ended, SFF will not forward the message again.
  • the function node when it detects that it is not the last hop on the SFC, it also returns the FR message to the SFF, so that the next function node also releases the corresponding occupied resources, and releases the functions according to the link information. Corresponding resources in the node to avoid omissions and improve the reliability and comprehensiveness of SFC resource release.
  • the function node does not need to determine the corresponding stream in the SFC after releasing the corresponding resource. Whether the processing path is terminated or not, and the FR message packet is not returned.
  • FIG. 6 is a timing diagram of a resource release method in a service function chain in an embodiment.
  • a service function chain SPI1 including the service function SF1 and the service function SF1 supports the NSH.
  • the Classifier senses that the flow Flow1 has ended.
  • the purpose of this process is Classifier.
  • the SF1 message is sent to help the service function SF1 release the resources corresponding to the flow Flow1 in time.
  • the specific implementation includes steps 601 to 603.
  • Step 601 The Classifier detects the end of the flow, constructs a FR message, and uses the SPI/SI that is consistent with the flow Flow1. The Classifier sends FR messages to the SFF.
  • Step 602 The SFF receives the FR message without special distinction, and forwards it to the corresponding next hop according to the SPI and the SI. In this embodiment, the SFF forwards the FR message to the service function SF1.
  • Step 603 The service function SF1 receives the FR message and, according to the information carried in the FR message, knows that the flow Flow1 has ended, and then releases the resource corresponding to the flow Flow1. If the SPI and the SI in the FR message are the SFs of the last hop on the service function chain, the packets are not sent to the SFF.
  • the FR message is a packet that extends the NSH part based on the NSH-encapsulated packet.
  • Extended NSH refers to an NSH that adds FRI.
  • FRI is an indication of the flow release information added in the NSH.
  • the initial packet part of the FR message packet can be constructed by using the corresponding IP quintuple (source address, source port number, protocol number, destination address, destination port number) in the stream.
  • the payload portion of the initial message is not required, and may or may not be available. Carrying the IP quintuple can indicate the corresponding stream.
  • FIG. 7 is a timing diagram of a resource release method in a service function chain in another embodiment.
  • a service function chain SPI1 that includes the service function SF2, and the service function SF2 does not support the NSH, and the SFC Proxy is deployed as an agent of the service function SF2 to the SFC network.
  • the Classifier is aware that Flow1 has been terminated. The purpose of this process is to enable the SFC proxy to release the resources corresponding to Flow1 in a timely manner by sending FR messages.
  • the specific implementation includes steps 701 to 703.
  • Step 701 The Classifier detects the end of the flow, constructs a FR message, and uses the SPI/SI that is consistent with the flow Flow1. The Classifier sends FR messages to the SFF.
  • Step 702 The SFF receives the FR message without special distinction, and forwards the corresponding next hop according to the SPI and the SI. In this embodiment, the SFF forwards the FR message to the SFC Proxy.
  • Step 703 The SFC Proxy receives the FR message and, according to the information carried in the FR message, knows that the flow Flow1 has ended, and then releases the resource corresponding to the flow Flow1. If the SPI and the SI of the FR message are known to be the SF of the last hop on the service function chain, the packet is not sent to the SFF.
  • the FR message is a packet that extends the NSH part based on the NSH-encapsulated packet.
  • Extended NSH refers to an NSH that adds FRI.
  • FRI is an indication of the flow release information added in the NSH.
  • the initial packet part of the FR message packet can be constructed by using the corresponding IP quintuple in the stream.
  • the payload portion of the initial message is not required, and may or may not be available. Carrying the IP quintuple can indicate the corresponding stream.
  • FIG. 8 is a timing diagram of a resource release method in a service function chain in still another embodiment.
  • a service function chain SPI1 including the service function SF1 and the service function SF2
  • the service function SF1 supports the NSH
  • the service function SF2 does not support the NSH
  • the SFC Proxy is deployed as an agent of the service function SF2 to the SFC network.
  • the Classifier has been configured to receive the flow of Flow1.
  • the purpose of this process is to enable the service function SF1 and SFC Proxy to release the resources corresponding to Flow1 in a timely manner by sending FR messages.
  • the specific implementation includes steps 801 to 806.
  • Step 801 The Classifier detects the end of the flow, constructs a FR message, and uses the SPI/SI that is consistent with the flow Flow1. The Classifier sends FR messages to the SFF.
  • Step 802 The SFF receives the FR packet, and does not make a special distinction.
  • the SF and the SI are forwarded to the corresponding next hop according to the SPI and the SI.
  • the SFF forwards the FR message to the service function SF1.
  • Step 803 The service function SF1 receives the FR message packet. According to the information carried in the FR message, if it is known that the flow Flow1 has ended, the resource corresponding to the flow Flow1 is released. If the SPI and the SI of the FR message are not the SF of the last hop of the service function chain, the packet is processed according to the normal flow Flow1 message (ie, the value of the SI is modified).
  • Step 804 The service function SF1 sends an FR message to the SFF.
  • Step 805 Similar to step S802, the SFF sends the FR message to the SFC Proxy.
  • Step 806 The SFC Proxy receives the FR message. According to the information carried in the FR message, if it is known that the flow Flow1 has ended, the resource corresponding to the flow Flow1 is released. If the SPI and SI of the FR message are known to be the last hop on the service function chain, the packet is no longer sent to the SFF.
  • the FR message is a packet that extends the NSH part based on the NSH-encapsulated packet.
  • Extended NSH refers to an NSH that adds FRI.
  • FRI is an indication of the flow release information added in the NSH.
  • the initial packet part of the FR message packet can be constructed by using the corresponding IP quintuple in the stream.
  • the payload portion of the initial message is not required, and may or may not be available. Carrying the IP quintuple can indicate the corresponding stream.
  • FIG. 9 is a timing diagram of a resource release method in a service function chain in still another embodiment.
  • a service function chain SPI1 including a service function SF1 and a service function SF2, and both the service function SF1 and the service function SF2 support the NSH.
  • the Classifier has been configured to receive the flow of Flow1. The purpose of this process is to enable the service function SF1 and service function SF2 to release the resources corresponding to Flow1 in time.
  • the specific implementation includes steps 901 to 906.
  • Step 901 The Classifier detects the end of the flow, constructs a FR message, and uses the SPI/SI that is consistent with the flow Flow1. The Classifier sends FR messages to the SFF.
  • Step 902 The SFF receives the FR message and does not make a special distinction. It can be forwarded to the corresponding next hop according to the SPI and the SI. In this embodiment, the SFF forwards the FR message to the service function SF1.
  • Step 903 The service function SF1 receives the FR message packet. According to the information carried in the FR message, if it is known that the flow Flow1 has ended, the resource corresponding to the flow Flow1 is released. If the SPI and the SI of the FR message are not the SF of the last hop in the service function chain, the packet is processed according to the normal Flow1 packet (that is, the value of the SI is modified).
  • Step 904 The service function SF1 sends an FR message to the SFF.
  • Step 905 Similar to step S902, the SFF sends the FR message message to the service function SF2.
  • Step 906 The service function SF2 receives the FR message packet. According to the information carried in the FR message, if it is known that the flow Flow1 has ended, the resource corresponding to the flow Flow1 is released. According to FR If the SPI and SI of the message learn that they are the last hop of the service function chain, the message is no longer sent to the SFF.
  • the FR message is a packet that extends the NSH part based on the NSH-encapsulated packet.
  • Extended NSH refers to an NSH that adds FRI.
  • FRI is an indication of the flow release information added in the NSH.
  • the initial packet part of the FR message packet can be constructed by using the corresponding IP quintuple in the stream.
  • the payload portion of the initial message is not required, and may or may not be available. Carrying the IP quintuple can indicate the corresponding stream.
  • FIG. 10 is a timing diagram of a resource release method in a service function chain in still another embodiment.
  • a service function chain SPI1 including the service function SF1 and the service function SF2.
  • the service function SF1 and the service function SF2 do not support the NSH, and the service function proxy SFC Proxy1 and the service function proxy SFC Proxy2 are respectively used as service functions.
  • the agent of SF1 and service function SF2 is deployed in the SFC network.
  • the Classifier has been configured to receive the flow of Flow1.
  • the purpose of this process is to send the FR message to help the service function proxy SFC Proxy1 and the service function proxy SFC Proxy2 release the resources corresponding to Flow1 in time.
  • the specific implementation includes steps 1001 to 1006.
  • Step 1001 The Classifier detects the end of the flow, constructs a FR message, and uses the SPI/SI that is consistent with the flow Flow1. The Classifier sends FR messages to the SFF.
  • Step 1002 The SFF receives the FR message and does not make a special distinction. It can be forwarded to the corresponding next hop according to the SPI and the SI. In this embodiment, the SFF forwards the FR message to the service function proxy SFC Proxy1.
  • Step 1003 The service function proxy SFC Proxy1 receives the FR message, and according to the information carried in the FR packet, it is known that the flow Flow1 has ended, and the resource corresponding to the flow Flow1 is released. According to the SPI and SI of the FR message, if it is not the last hop on the service function chain, the packet is processed according to the normal flow Flow1 message (ie, the value of the SI is modified).
  • Step 1004 The service function proxy SFC Proxy1 sends an FR message to the SFF.
  • Step 1005 Similar to step S1002, the SFF sends the FR message to the service function proxy SFC Proxy2.
  • Step 1006 The service function proxy SFC Proxy2 receives the FR message, and according to the information carried in the FR message, it is known that the flow Flow1 has ended, and the resource corresponding to the flow Flow1 is released. If the SPI and SI of the FR message are known to be the last hop on the service function chain, the packet is no longer sent to the SFF.
  • the resource release method in the service function chain in one embodiment, as shown in FIG. 11, includes the following steps:
  • Step S220 Construct a flow release message message (which can be understood as a FR message message) when the flow is in the end state.
  • the FR message carries the link information of the FRI and the stream.
  • the specific manner of carrying the FRI in the FR message is not unique. It can be carried in the basic header of the FR packet or in the context header of the FR packet.
  • Step S240 Send a flow release message according to the link information (which can be understood as an FR message), so that the function node that receives the flow release message receives the corresponding release according to the flow release identifier carried in the flow release message. Resources.
  • the FR message can be directly sent to the subsequent node on the corresponding SFC according to the link information.
  • the function node of the SFC can release the corresponding resource according to the FRI carried in the FR message, so as to avoid the problem that the service quality is degraded due to the inability to release the resource in time.
  • the resource release method in the foregoing service function chain by monitoring the state of the flow, and constructing and sending a flow release message message (which can be understood as a FR message message) when the flow is in an end state, so that the function node releases the corresponding resource in time. It can timely detect the end of the flow and perform the resource release operation, avoiding the problem of degraded service quality due to the inability to release resources in time, and improving the service quality of the service.
  • the flow release identifier is located in a reserved bit of the base header of the flow release message message.
  • the flow release message carries a flow release identifier, including: if the service function chain encapsulation format is a fixed length format, selecting a mandatory context header of the flow release message packet The bit is used as the stream release identifier. If the service function chain encapsulation format is a variable length format, the variable length context header is generated as a flow release identifier in the flow release message packet.
  • the SFC package format may specifically include a fixed length format and a variable length format. Two different FRI settings are provided according to the SFC package format, and the FRI can be set according to the actual situation.
  • Step S320 Receive a flow release message (which can be understood as a FR message) forwarded by the service function forwarder.
  • the FR message carries a flow release identifier (which can be understood as FRI) and is used to identify the FR message.
  • the FR message can also carry the link information of the flow, and the service function forwarder (which can be understood as SFF) forwards the flow release message according to the link information.
  • the specific manner of carrying the FRI in the FR message is not unique. It can be carried in the basic header of the FR packet or in the context header of the FR packet.
  • Step S340 Release the corresponding resource according to the flow release identifier carried in the flow release message packet (which can be understood as an FR message packet).
  • the corresponding resource is released according to the FRI carried in the FR message, so as to avoid the problem that the service quality is degraded due to the inability to release the resource in time.
  • the resource release method in the service function chain releases the corresponding resource when receiving the flow release message, and can perform the resource release operation in time, thereby avoiding the problem that the service quality is degraded due to the inability to release the resource in time, and improving the service service. quality.
  • the FR message packet also carries the link information of the stream.
  • the method further includes the following steps:
  • Step S360 Determine whether the link is the last hop on the service function chain according to the link information in the flow release message packet (which can be understood as an FR message packet).
  • the link information it can be determined whether it is the last hop on the SFC. If yes, the corresponding flow is terminated in the SFC processing path, and the message is not returned to the SFF; if not, the process proceeds to step S380.
  • Step S380 Return the flow release message message to the service function forwarder.
  • the FR message message is returned to the SFF, so that the SFF forwards the FR message to the next function node for resource release operation.
  • the FR message message is returned to the SFF, so that the next function node also releases the corresponding occupied resources, and the function nodes are sequentially released according to the link information. Corresponding resources, avoiding omissions, and improving the reliability and comprehensiveness of SFC resource release.
  • the system includes a classifier 110, a service function forwarder 120, and at least one function node 130. among them:
  • the classifier 110 is configured to construct a flow release message message when detecting that the flow is in an end state, and is further configured to send the flow release message message to the corresponding service function forwarder according to the link information.
  • a flow release message (which can be understood as an SR message) carries a flow release identifier (which can be understood as FRI) and link information of the flow.
  • FRI flow release identifier
  • the specific manner of carrying the FRI in the FR message is not unique. It may be carried in the basic header of the FR message or in the context header of the FR message.
  • the service function forwarder 120 is configured to forward the flow release message message to the corresponding function node according to the link information.
  • the SFF forwards the FR message to the corresponding function node according to the carried link information.
  • the function node 130 is configured to release the corresponding resource according to the flow release identifier carried in the flow release message packet after receiving the flow release message message.
  • the function node After receiving the FR message, the function node releases the corresponding resource according to the FRI carried in the FR message, thereby avoiding the problem that the service quality is degraded due to the inability to release the resource in time.
  • the resource release system in the foregoing service function chain after detecting that the flow is in the end state, the classifier 110 constructs a flow release message carrying the link information of the flow release identifier and the flow, and sends the message to the service function forwarder 120 to Function node.
  • the function node 130 releases the corresponding resource according to the flow release identifier carried in the flow release message.
  • the function node releases the corresponding resource in time, and can sense the end of the flow and perform the resource release operation in time. The problem of degraded service quality due to the inability to release resources in time is avoided, and the quality of business services is improved.
  • the flow release identifier is located in a reserved bit of the base header of the flow release message message.
  • the flow release message carries a flow release identifier, including: if the service function chain encapsulation format is a fixed length format, the bit of the mandatory context header of the flow release message packet is selected as the flow release identifier. If the service function chain encapsulation format is a variable length format, a variable length context header is generated in the flow release message packet as a flow release identifier.
  • the above is to provide two different FRI setting modes according to the SFC package format, and the FRI can be set correspondingly according to the actual situation.
  • functional node 130 includes a business function 132 that identifies the encapsulation type of the business function chain.
  • the service function can be understood as SF, and the number of SFs can be one or more, and the SF can directly identify the encapsulation type of the SFC. After the SFF sends the FR message to the SF, the SF can directly identify the FR message and release the corresponding resource to prevent the end of the stream from continuing to occupy resources.
  • the SF after receiving the FR message that is forwarded by the SFF and releasing the corresponding resource, the SF also detects whether it is located in the last hop on the SFC, and if yes, the resource is released, and the SF may not return the FR message to the SFF; If not, the SF returns a FR message message to the SFF, so that the SFF sends the FR message message to the next SF. It can be understood that in other embodiments, the SFF may also send the FR message to all SFs simultaneously.
  • functional node 130 includes a business function agent 134.
  • the number of SFC Proxys can be one or more. After the SFF sends the FR message to the SFC proxy, the SFC proxy directly identifies the FR message and releases the corresponding resource to prevent the end of the stream from continuing to occupy resources.
  • the SFC proxy receives the FR message forwarded by the SFF and releases the corresponding resource. After the source, it also detects whether it is located on the last hop of the SFC. If yes, the resource release is complete, the SFC Proxy may not return the FR message to the SFF; if not, the SFC Proxy returns the FR message to the SFF, so that the SFF will The FR packet is sent to the next SFC Proxy. It can be understood that in other embodiments, the SFF may also send the FR message message to all SFC Proxys simultaneously.
  • the function node 130 includes a service function agent 134 and a service function 132 that can identify the package type of the service function chain.
  • the number of the SF and the SFC Proxy may also be one or more. After receiving the FR message carrying the FRI, the SF and the SFC Proxy may release the corresponding resource according to the FR message. The SF and the SFC Proxy may perform resource release at the same time, or may not release the resources at the same time, and the sequence is not unique, and the SFF determines the manner in which the FR message is forwarded according to the link information.
  • the SFF first forwards the FR message to the SF, and then forwards it to the SFC proxy. After the SFF forwards the FR message to the SF, the SF releases the corresponding resource, and returns the FR message to the SFF when it detects that it is not the last hop on the SFC. The SFF forwards the FR message to the SFC Proxy. The SFC Proxy also releases the corresponding resource and detects whether it is the last hop on the SFC. If the resource is released, the SFC Proxy does not return the FR message to the SFF. If no, the SFC Proxy returns the FR message to the SFF, so that the SFF forwards the FR message again.
  • the SFF may forward the FR message to the SFC Proxy, and then forward the FR message to the SF after receiving the FR message returned by the SFC Proxy.
  • the above provides a corresponding resource release manner for different forms of the function node, and can perform resource adjustment according to different structures of the function node, thereby improving the convenience and comprehensiveness of the resource release operation. It can be understood that the specific form of the function node and the corresponding resource release manner include, but are not limited to, the above embodiments.
  • the function node 130 is further configured to determine, according to the link information in the received flow release message message, whether it is the last hop on the service function chain; if not, the flow release message message Return to the business function forwarder 120.
  • the service function forwarder 120 is further configured to receive the returned flow release message, and send the flow release message to the next functional node 130 according to the link information.
  • the function node 130 also returns when it detects that it is not the last hop on the service function chain.
  • the FR message is sent to the service function forwarder 120, so that the next function node 130 releases the corresponding resource, and the corresponding resources in each function node 130 are sequentially released according to the link information, thereby avoiding omission, improving the reliability and comprehensiveness of the SFC resource release. Sex.
  • the function node 130 releases the corresponding resources. It is not necessary to determine whether the processing path of the corresponding stream in the SFC is terminated, and it is not necessary to return a FR message.
  • the resource release device in the service function chain in one embodiment, as shown in FIG. 18, includes a message construction module 220 and a message transmission module 240.
  • the message construction module 220 is configured to construct a flow release message message (which can be understood as a FR message message) when the flow is in the end state.
  • the FR message carries the link information of the FRI and the stream.
  • the specific manner of carrying the FRI in the FR message is not unique. It may be carried in the basic header of the FR message or in the context header of the FR message.
  • the message sending module 240 is configured to send a flow release message according to the link information, so that the function node that receives the flow release message releases the corresponding resource according to the flow release identifier carried in the flow release message.
  • the FR message can be directly sent to the subsequent node on the corresponding SFC according to the link information.
  • the function node of the SFC can release the corresponding resource according to the FRI carried in the FR message, so as to avoid the problem that the service quality is degraded due to the inability to release the resource in time.
  • the message construction module 220 may be a processor in a resource release device in a service function chain, such as a central processing unit (CPU), a microprocessor (Micro Control Unit), a digital signal processor (MCU). DSP, Digital Signal Processor, or Field-Programmable Gate Array (FPGA).
  • the message sending module 240 can be implemented by a communication interface in a resource release device in a service function chain.
  • the resource release device in the foregoing service function chain monitors the state of the flow, and constructs and sends a flow release message packet when the flow is in an end state, so that the function node releases the corresponding resource in time.
  • the source can detect the end of the flow and perform the resource release operation in time, avoiding the problem that the service quality is degraded due to the inability to release the resources in time, and improving the service quality of the service.
  • the flow release identifier is located in a reserved bit of the base header of the flow release message message.
  • the flow release message carries a flow release identifier, including: if the service function chain encapsulation format is a fixed length format, the bit of the mandatory context header of the flow release message packet is selected as the flow release identifier. If the service function chain encapsulation format is a variable length format, a variable length context header is generated in the flow release message packet as a flow release identifier.
  • the SFC package format may specifically include a fixed length format and a variable length format. Two different FRI settings are provided according to the SFC package format, and the FRI can be set according to the actual situation.
  • the resource release device in the service function chain in one embodiment, as shown in FIG. 19, includes a message receiving module 320 and a resource release module 340.
  • the message receiving module 320 is configured to receive a flow release message (for example, a FR message) forwarded by the service function forwarder.
  • a flow release message for example, a FR message
  • the FR message carries the FRI and is used to identify the FR message.
  • the FR message packet may also carry the link information of the flow, and the service function forwarder forwards the flow release message according to the link information.
  • the specific manner of carrying the FRI in the FR message is not unique, and may be carried in the basic header of the FR message or in the context header of the FR message.
  • the resource release module 340 is configured to release the corresponding resource according to the flow release identifier carried in the flow release message packet.
  • the corresponding resource is released according to the FRI carried in the FR message, so as to avoid the problem that the service quality is degraded due to the inability to release the resource in time.
  • the resource release device in the service function chain releases the corresponding resource when receiving the flow release message, and can perform the resource release operation in time, thereby avoiding the problem that the service quality is degraded due to the inability to release the resource in time, and improving the service service. quality.
  • the FR message also carries the link information of the stream.
  • the apparatus also includes a message return module 360.
  • the message returning module 360 is configured to determine, according to the link information in the received stream release message, that the resource release module 340 releases the corresponding resource according to the flow release identifier carried in the flow release message, and determines whether it is a service function. The last hop on the chain; if not, the flow release message message is returned to the service function forwarder.
  • the link information it can be determined whether it is the last hop on the SFC. If not, the FR message message is returned to the SFF, so that the SFF forwards the FR message to the next function node for resource release operation.
  • the FR message message is returned to the SFF, so that the next function node also releases the corresponding occupied resources, and the function nodes are sequentially released according to the link information. Corresponding resources, avoiding omissions, and improving the reliability and comprehensiveness of SFC resource release.
  • the message receiving module 320 may be implemented by a communication interface in the resource release device in the service function chain; the resource release module 340 may be implemented by a processor in the service function chain, such as a CPU, an MCU, a DSP, or an FPGA. achieve.
  • the message return module 360 can be implemented by a processor in the resource release device in the service function chain in conjunction with the communication interface.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).
  • an embodiment of the present invention further provides a computer storage medium, where the computer program is stored, and when the computer program is executed by the processor, the steps of the method in the embodiment of the present invention are implemented.
  • the solution provided by the embodiment of the present invention by monitoring the state of the flow, and constructing and sending the flow release message packet when the flow is in the end state, so that the function node releases the corresponding resource in time, and can timely sense the end of the flow and perform the resource release operation.
  • the problem of degraded service quality due to the inability to release resources in time is avoided, and the quality of business services is improved.

Landscapes

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

Abstract

本发明涉及一种业务功能链中的资源释放方法、系统、装置和计算机存储介质。方法包括：分类器在检测到流处于结束状态时构造流释放消息报文；流释放消息报文携带有流释放标识和流的链路信息；分类器根据链路信息将流释放消息报文发送至对应的业务功能转发器；业务功能转发器根据链路信息将流释放消息报文转发至对应的功能节点；功能节点在接收到流释放消息报文后，根据流释放消息报文中携带的流释放标识释放对应的资源。

Description

资源释放方法、系统、装置及计算机存储介质
相关申请的交叉引用
本申请基于申请号为201610399169.8、申请日为2016年06月06日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本发明涉及移动通信技术领域，特别是涉及一种业务功能链中的资源释放方法、系统、装置及计算机存储介质。
背景技术
随着社会不断发展，增值业务(Value-Added Service，VAS)越来越丰富。为了解决增值业务的灵活部署，引入了业务功能链的技术。业务功能链(Service Function Chain，SFC)包括多个功能节点，具体包括分类器(Classifier)、业务功能转发器(Service Function Forwarder，SFF)、业务功能(Service Function，SF)和业务功能代理(SFC Proxy)。
为了使报文能够在各个SFC节点之间灵活转发而不需要改动基础网络设备，会根据SFC封装信息对报文进行封装。报文经过SFC封装后可以不依赖于目的地址进行转发，可在SFC节点之间灵活传输报文。SF或SFC Proxy会为经过的每一个流(Flow)建立上下文，保存相关的上下文信息。这些上下文信息要一直保存，直到该流结束才能够清除。一个SF或SFC Proxy会为很多个流服务，因而为每一个流要保存相关的上下文信息，就会占用很多的内存资源。
传统的业务功能链中SF和SFC Proxy都无法及时感知到流结束，导致已经结束的流对应的资源无法及时释放，资源占有率高。当新的流到来的时候，无法申请到资源，因而无法对新的流提供服务，造成业务服务质量 下降。
发明内容
为解决现有存在的技术问题，本发明实施例提供一种业务功能链中的资源释放方法、系统、装置及计算机存储介质。
一种业务功能链中的资源释放方法，所述方法包括：
分类器在检测到流处于结束状态时构造流释放消息报文，所述流释放消息报文携带有流释放标识和流的链路信息；
所述分类器根据所述链路信息将所述流释放消息报文发送至对应的业务功能转发器；
所述业务功能转发器根据所述链路信息将所述流释放消息报文转发至对应的功能节点；
所述功能节点在接收到所述流释放消息报文后，根据所述流释放消息报文中携带的流释放标识释放对应的资源。
一种业务功能链中的资源释放系统，包括：
分类器，配置为在检测到流处于结束状态时构造流释放消息报文，所述流释放消息报文携带有流释放标识和流的链路信息；以及根据所述链路信息将所述流释放消息报文发送至对应的业务功能转发器；
业务功能转发器，配置为根据所述链路信息将所述流释放消息报文转发至对应的功能节点；
至少一个功能节点，配置为在接收到所述流释放消息报文后，根据所述流释放消息报文中携带的流释放标识释放对应的资源。
上述业务功能链中的资源释放方法和系统，在检测到流处于结束状态后，分类器构造携带有流释放标识和流的链路信息的流释放消息报文，并经业务功能转发器发送至功能节点。功能节点在接收到流释放消息报文后，根据流释放消息报文中携带的流释放标识释放对应的资源。该方法和系统通过监测流的状态，并在流处于结束状态时构造并发送流释放消息报文，使得功能节点及时释放对应的资源，能够及时感知流结束并进行资源释放 操作，避免了出现因无法及时释放资源造成服务质量下降的问题，提高了业务服务质量。
一种业务功能链中的资源释放方法，所述方法包括：
检测到流处于结束状态时构造流释放消息报文，所述流释放消息报文携带有流释放标识和流的链路信息；
根据所述链路信息发送所述流释放消息报文，以使接收到所述流释放消息报文的功能节点根据所述流释放消息报文中携带的流释放标识释放对应的资源。
一种业务功能链中的资源释放装置，包括：
报文构造模块，配置为检测到流处于结束状态时构造流释放消息报文，所述流释放消息报文携带有流释放标识和流的链路信息；
报文发送模块，配置为根据所述链路信息发送所述流释放消息报文，以使接收到所述流释放消息报文的功能节点根据所述流释放消息报文中携带的流释放标识释放对应的资源。
一种计算机存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现上述业务功能链中的资源释放方法的步骤。
上述业务功能链中的资源释放方法、装置和计算机存储介质，在检测到流处于结束状态后，构造携带有流释放标识和流的链路信息的流释放消息报文并发送，以使接收到流释放消息报文的功能节点根据流释放消息报文中携带的流释放标识释放对应的资源。该方法和装置通过监测流的状态，并在流处于结束状态时构造并发送流释放消息报文，使得功能节点及时释放对应的资源，能够及时感知流结束并进行资源释放操作，避免了出现因无法及时释放资源造成服务质量下降的问题，提高了业务服务质量。
一种业务功能链中的资源释放方法，所述方法包括：
接收业务功能转发器转发的流释放消息报文，所述流释放消息报文携带有流释放标识；
根据所述流释放消息报文中携带的流释放标识释放对应的资源。
一种业务功能链中的资源释放装置，包括：
报文接收模块，配置为接收业务功能转发器转发的流释放消息报文，所述流释放消息报文携带有流释放标识；
资源释放模块，配置为根据所述流释放消息报文中携带的流释放标识释放对应的资源。
一种计算机存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现上述业务功能链中的资源释放方法的步骤。
上述业务功能链中的资源释放方法、装置和计算机存储介质，接收业务功能转发器转发的流释放消息报文，根据流释放消息报文中携带的流释放标识释放对应的资源。在接收到流释放消息报文时释放对应的资源，能够及时进行资源释放操作，避免了出现因无法及时释放资源造成服务质量下降的问题，提高了业务服务质量。
附图说明
图1为一实施例中业务功能链中的资源释放方法的流程图；
图2为一实施例中扩展了F比特位的NSH基本头部的格式示意图；
图3为一实施例中扩展了必选上下文的FRI的格式示意图；
图4为一实施例种可变长度上下文头部的FRI的格式示意图；
图5为另一实施例中业务功能链中的资源释放方法的流程图；
图6为一实施例中业务功能链中的资源释放方法的时序图；
图7为另一实施例中业务功能链中的资源释放方法的时序图；
图8为又一实施例中业务功能链中的资源释放方法的时序图；
图9为又一实施例中业务功能链中的资源释放方法的时序图；
图10为再一实施例中业务功能链中的资源释放方法的时序图；
图11为又一实施例中业务功能链中的资源释放方法的流程图；
图12为再一实施例中业务功能链中的资源释放方法的流程图；
图13为再一实施例中业务功能链中的资源释放方法的流程图；
图14为一实施例中业务功能链中的资源释放系统的结构示意图；
图15为另一实施例中业务功能链中的资源释放系统的结构示意图；
图16为又一实施例中业务功能链中的资源释放系统的结构示意图；
图17为再一实施例中业务功能链中的资源释放系统的结构示意图；
图18为一实施例中业务功能链中的资源释放装置的结构示意图；
图19为另一实施例中业务功能链中的资源释放装置的结构示意图；
图20为又一实施例中业务功能链中的资源释放装置的结构示意图。
具体实施方式
在一个实施例中的业务功能链中的资源释放方法，如图1所示，该方法包括：
步骤S110：分类器在检测到流处于结束状态时构造流释放消息报文。
这里，所述分类器的英文可以表述为Classifier，为SFC中的一个节点，SFC的节点还包括SFF、SF和SFC Proxy。在一个SFC系统中，分类器、SFF和SF的数量可以是一个或多个，SFC Proxy的数量可以是零个、一个或多个。对报文进行SFC封装，以使封装后的报文可以不依赖于目的地址进行转发，在SFC的节点之间灵活传输报文。分类器负责识别流并且将流和SFC进行关联，将流送到对应的SFC上去处理。
流释放(Flow Release，FR)消息报文携带有流释放标识(Flow Release Indicator，FRI)和流的链路信息。FR消息报文是采用SFC封装的携带有流相关信息的报文，沿着SFC路径进行转发。FRI为指示流释放信息的标识，用于后续识别FR报文。链路信息用于指示流在SFC的处理路径，SFC根据链路信息对流进行转发。本实施例中，链路信息可包括业务路径标识(Service Path Identifier，SPI)和业务标识(Service Index，SI)。在FR消息报文中携带链路信息，以便发送给流对应的SFC上后续的节点。FR消息报文的初始报文(Original Packet)部分可使用流中对应的IP五元组(源地址，源端口号，协议号，目的地址，目的端口号)构造一个报文即可。初始报文的净荷部分不做要求，携带了IP五元组的FR报文可以指明对应的流。
当检测到流处于结束状态时，则需要释放SFC中该流所占的资源，分类器获取对应流的链路信息，并根据链路信息进行SFC封装，得到携带有FRI和链路信息的FR消息报文。分类器检测流处于结束状态的具体方式并不唯一，可以是直接对流进行状态检测，也可以是通过深度包检测(Deep Packet Inspection，DPI)技术检测传输控制协议(Transmission Control Protocol，TCP)连接的结束信令来感知流的结束。当分类器检测到需要释放SFC某一个流的资源时，构造FR消息报文发给该流对应的SFC上后续的节点。
在FR消息报文中携带FRI的具体方式也并不唯一，可以是携带在FR报文的基本头部中，也可以是携带在FR报文的上下文头部中。
步骤S120：分类器根据链路信息将流释放消息报文(可以理解为FR消息报文)发送至对应的业务功能转发器(可以理解为SFF)。
分类器在封装得到携带有FRI和链路信息的FR消息报文后，可直接根据链路信息将FR消息报文发送至对应的SFC上后续的节点，即对应的SFF。
步骤S130：业务功能转发器(可以理解为SFF)根据链路信息将流释放消息报文(可以理解为FR消息报文)转发至对应的功能节点。
SFF负责对封装的报文，根据报文包含的信息进行转发。SFF接收到FR消息报文后，按照携带的链路信息将FR消息报文转发至对应的功能节点。功能节点的数量可以是一个或多个。当功能节点的数量为多个时，SFF可以是根据链路信息直接将FR报文同时发送到所有对应的功能节点，以便功能节点进行资源释放操作。SFF也可以是根据链路信息将FR消息报文转发到下一跳SFC节点对应的功能节点。若是SFF根据链路信息按先后顺序将FR报文转发至各个功能节点，可以是发送FR消息报文至一功能节点，并在接收到该功能节点返回的FR消息报文后，继续发送FR消息报文至下一功能节点；也可以是在发送FR消息报文至一功能节点预设时长后，继续发送FR消息报文至下一功能节点，具体形式不限。
步骤S140：功能节点在接收到流释放消息报文后，根据流释放消息报文中携带的流释放标识释放对应的资源。
功能节点在接收到FR消息报文后，根据FR消息报文中携带的FRI释 放对应的资源，避免出现因而无法及时释放资源造成服务质量下降问题。
上述业务功能链中的资源释放方法，在检测到流处于结束状态后，分类器构造携带有流释放标识和流的链路信息的流释放消息报文，并经业务功能转发器发送至功能节点。功能节点在接收到流释放消息报文后，根据流释放消息报文中携带的流释放标识释放对应的资源。通过监测流的状态，并在流处于结束状态时构造并发送流释放消息报文，使得功能节点及时释放对应的资源，能够及时感知流结束并进行资源释放操作，避免了出现因无法及时释放资源造成服务质量下降的问题，提高了业务服务质量。
在一个实施例中，流释放标识(可以理解为FRI)位于FR消息报文的基本头部的保留比特位。
SFC封装的类型可以有多种，包括网络服务报头(Network Service header，NSH)封装等类型，同一封装类型的封装格式也有多种可供选择。以NSH封装为例，FRI可以选取NSH的基本头部的一个保留比特位作为FRI，定义为F比特，如图2所示，F比特为1则标识是释放流的报文。通过选取FR消息报文的基本头部的保留比特位作为FRI，操作简便且易识别。
在一个实施例中，流释放消息报文携带有流释放标识(可以理解为FRI)，包括：若业务功能链封装格式为定长格式，则选取流释放消息报文的必选上下文头部的比特位作为流释放标识(可以理解为FRI)；若业务功能链封装格式为变长格式，则在流释放消息报文中生成变长上下文头部作为流释放标识(可以理解为FRI)。
同样以NSH封装为例，参照图3和图4，若NSH封装格式为定长格式，MD type表征NSH的封装格式，MD type为1表示NSH的封装格式为定长格式，MD type为2表示NSH的封装格式为变长格式。
若MD type为1，选取NSH的必选上下文头部的一个比特位作为FRI，定义为F比特，如图3所示，F比特为1则标识是释放流的报文。若MD type为2，定义一个新的变长上下文头部作为FRI，如图4所示，FRI为1则标识是释放流的报文。TLV Class、Type字段可根据具体情况确定，C比特位设置为1。
以上即是根据SFC封装格式对应提供两种不同的FRI设置方式，可根 据实际情况来对应设置FRI。
在一个实施例中，功能节点包括可识别业务功能链的封装类型的业务功能(可以理解为SF)。
SF的数量可以是一个或多个，SF可直接识别SFC的封装类型。以NSH封装为例，SF支持NSH封装的流的报文，可直接调用相应资源对流进行处理，并保存上下文信息。当SFF将FR消息报文发给SF后，SF同样可直接识别FR消息报文，并释放对应的资源，避免结束的流继续占用资源。
具体地，SF在接收到SFF转发的FR消息报文并释放对应的资源后，还检测自身是否位于SFC上的最后一跳，若是，则资源释放完成，SF可不返回FR消息报文至SFF；若否，则SF返回FR消息报文至SFF，以便SFF将FR消息报文发送至下一SF。可以理解，在其他实施例中，SFF也可以是将FR消息报文同时发送至所有的SF。
在一个实施例中，功能节点包括业务功能代理(可以理解为SFC Proxy)。
SFC Proxy的数量可以是一个或多个，SFC Proxy作为不支持SFC封装类型的SF的代理，对应需要发送给SF的报文，SFC Proxy将报文解掉封装后发送至SF；对从SF收到的报文，SFC Proxy负责进行封装，再发给其他节点。SFC Proxy作为不能识别SFC的封装类型的SF的代理，在对流进行处理时同样需要保存上下文信息。当SFF将FR消息报文发给SFC Proxy后，SFC Proxy直接识别FR消息报文，并释放对应的资源，避免结束的流继续占用资源。
具体地，SFC Proxy在接收到SFF转发的FR消息报文并释放对应的资源后，还检测自身是否位于SFC上的最后一跳，若是，则资源释放完成，SFC Proxy可不返回FR消息报文至SFF；若否，则SFC Proxy返回FR消息报文至SFF，以便SFF将FR消息报文发送至下一SFC Proxy。可以理解，在其他实施例中，SFF也可以是将FR消息报文同时发送至所有的SFC Proxy。
进一步地，在一个实施例中，功能节点包括业务功能代理(可以理解为SFC Proxy)和可识别业务功能链的封装类型的业务功能(可以理解为 SF)。
SF和SFC Proxy的数量也可以是一个或多个，SF和SFC Proxy都可在接收到携带FRI的FR消息报文后，根据FR消息报文释放对应的资源。SF和SFC Proxy可以是同时进行资源释放，也可不是同时进行资源释放，且先后顺序并不唯一，具体由SFF根据链路信息转发FR消息报文的方式决定。若SFF同时将FR消息报文转发给SF和SFC Proxy，则同时进行资源释放；若SFF先将FR消息报文转发至其中一个功能节点，则接收到FR报文的该功能节点先进行资源释放。在SFF将FR消息报文转发至另一功能节点后，另一功能节点再进行资源释放。
以SFF先将FR消息报文转发至SF，再转发至SFC Proxy为例。SFF在将FR消息报文转发至SF后，SF释放对应的资源，并在检测到自身不是位于SFC上的最后一跳时，返回FR消息报文至SFF。SFF将FR消息报文转发至SFC Proxy，SFC Proxy同样释放对应的资源，并检测自身是否是SFC上的最后一跳，若是，则资源释放完成，SFC Proxy不返回FR消息报文至SFF；若否，则SFC Proxy返回FR消息报文至SFF，以便SFF再次转发FR报文。
可以理解，在其他实施例中，SFF也可以是先将FR消息报文转发至SFC Proxy，在接收到SFC Proxy返回的FR消息报文后再转发至SF。
以上即是针对功能节点的不同形式提供了对应的资源释放方式，可根据功能节点的不同结构对应进行资源调整，提高资源释放操作的便利性和全面性。可以理解，功能节点的具体形式以及对应的资源释放方式包括但并不限于以上实施例。
在一个实施例中，如图5所示，步骤S140之后，上述方法还可包括：
步骤S150：功能节点根据流释放消息报文(可以理解为FR消息报文)中的链路信息，判断自身是否是业务功能链上的最后一跳。
由于FR消息报文中的链路信息可指示对应流在SFC中的路径，功能节点根据链路信息可判断自身是否是SFC上的最后一跳，若是，则说明对应流在SFC的处理路径终止，可不返回报文至SFF；若否，则进行步骤S160。
步骤S160：功能节点将流释放消息报文返回至业务功能转发器(可以理解为SFF)。
功能节点返回FR消息报文，具体可按照流的报文处理，修改FR消息报文中的链路信息后返回至SFF。功能节点在检测到不是位于SFC上最后一跳时，将FR消息报文返回至SFF，以便SFF将FR消息报文转发至下一功能节点进行资源释放操作。
步骤S170：业务功能转发器(可以理解为FRI)接收返回的流释放消息报文(可以理解为FR消息报文)，根据链路信息将流释放消息报文发送至下一功能节点。
可以理解，下一功能节点在释放对应的资源之后，若仍检测到自身不是SFC上的最后一跳，则继续返回FR消息报文至SFF，直至位于SFC最后一跳的功能节点也释放对应的资源。
此外，步骤S150中，若功能节点位于SFC上最后一跳，同样也可返回FR报文至SFF。由于资源释放已经结束，SFF不会再进行报文转发。
本实施例中，功能节点在检测到自身不是SFC上的最后一跳时，还返回FR消息报文至SFF，以使下一功能节点同样释放对应的占资源，根据链路信息依次释放各功能节点中对应的资源，避免出现遗漏，提高SFC资源释放可靠性和全面性。
可以理解，在其他实施例中，若功能节点的数量只有一个，或者SFF同时将FR消息报文发送至对应的所有功能节点，则功能节点在释放对应的资源后，不需判断对应流在SFC的处理路径是否终止，也不需返回FR消息报文。
为便于对上述方法进行进一步理解，以下提供几种具体实施例进行解释说明。
如图6所示为一实施例中业务功能链中的资源释放方法的时序图。本实施例中，有某一个包含业务功能SF1的业务功能链SPI1，业务功能SF1支持NSH。有一个流Flow1在路径SPI1上进行转发，现在这个流Flow1已经结束。Classifier感知到流Flow1已经结束，本流程的目的是Classifier 通过发送FR消息报文，帮助业务功能SF1及时释放掉流Flow1对应的资源。具体实施方式包括步骤601至步骤603。
步骤601：Classifier检测到流结束，构造FR消息报文，使用和流Flow1一致的SPI/SI。Classifier发送FR消息报文给SFF。
步骤602：SFF收到FR消息报文不进行特殊区分，根据SPI和SI转发给对应的下一跳即可。本实施例中，SFF将FR消息报文转发给业务功能SF1。
步骤603：业务功能SF1收到FR消息报文，根据FR消息报文携带的信息，知道是流Flow1已经结束，则释放流Flow1对应的资源。根据FR消息报文中的SPI和SI得知自己是业务功能链上最后一跳的SF，则不再将报文发给SFF。
其中，FR消息报文是在NSH封装的报文基础上进行扩展NSH部分的报文。扩展NSH是指增加了FRI的NSH。FRI是在NSH中增加的指示流释放信息的标识。FR消息报文的初始报文部分使用流中对应的IP五元组(源地址，源端口号，协议号，目的地址，目的端口号)构造一个报文即可。初始报文的净荷部分不做要求，可有可无。携带了IP五元组便可以指明对应的流。
如图7所示为另一实施例中业务功能链中的资源释放方法的时序图。本实施例中，有某一个包含业务功能SF2的业务功能链SPI1，业务功能SF2不支持NSH，使用SFC Proxy作为业务功能SF2的代理部署到SFC网络中。有一个流Flow1在路径SPI1上进行转发，现在这个流Flow1已经结束。Classifier感知到Flow1已经结束，本流程的目的是Classifier通过发送FR消息报文，帮助SFC Proxy及时释放掉流Flow1对应的资源。具体实施方式包括步骤701至步骤703。
步骤701：Classifier检测到流结束，构造FR消息报文，使用和流Flow1一致的SPI/SI。Classifier发送FR消息报文给SFF。
步骤702：SFF收到FR消息报文并不进行特殊区分，根据SPI和SI转发给对应的下一跳即可。本实施例中，SFF将FR消息报文转发给SFC Proxy。
步骤703：SFC Proxy收到FR消息报文，根据FR消息报文携带的信息，知道是流Flow1已经结束，则释放流Flow1对应的资源。根据FR消息报文的SPI和SI得知自己是业务功能链上最后一跳的SF，则不再将报文发给SFF。
其中，FR消息报文是在NSH封装的报文基础上进行扩展NSH部分的报文。扩展NSH是指增加了FRI的NSH。FRI是在NSH中增加的指示流释放信息的标识。FR消息报文的初始报文部分使用流中对应的IP五元组构造一个报文即可。初始报文的净荷部分不做要求，可有可无。携带了IP五元组便可以指明对应的流。
如图8所示为又一实施例中业务功能链中的资源释放方法的时序图。本实施例中，有某一个包含业务功能SF1和业务功能SF2的业务功能链SPI1，业务功能SF1支持NSH，业务功能SF2不支持NSH，使用SFC Proxy作为业务功能SF2的代理部署到SFC网络中。有一个流Flow1在路径SPI1上进行转发，现在这个流Flow1已经结束。Classifier已经感知到流Flow1已经结束，本流程的目的是Classifier通过发送FR消息报文，帮助业务功能SF1和SFC Proxy及时释放掉流Flow1对应的资源。具体实施方式包括步骤801至步骤806。
步骤801：Classifier检测到流结束，构造FR消息报文，使用和流Flow1一致的SPI/SI。Classifier发送FR消息报文给SFF。
步骤802：SFF收到FR报文，并不进行特殊区分，根据SPI和SI转发给对应的下一跳即可。本实施例中，SFF将FR消息报文转发给业务功能SF1。
步骤803：业务功能SF1收到FR消息报文。根据FR消息报文携带的信息，知道是流Flow1已经结束，则释放流Flow1对应的资源。根据FR消息报文的SPI和SI得知自己不是业务功能链上最后一跳的SF，则将报文按照正常的流Flow1的报文处理(即：修改SI的值)。
步骤804：业务功能SF1发送FR消息报文给SFF。
步骤805：类似步骤S802，SFF将FR消息报文给SFC Proxy。
步骤806：SFC Proxy收到FR消息报文。根据FR消息报文携带的信息，知道是流Flow1已经结束，则释放流Flow1对应的资源。根据FR消息报文的SPI和SI得知自己是业务功能链上最后一跳，则不再将报文发给SFF。
其中，FR消息报文是在NSH封装的报文基础上进行扩展NSH部分的报文。扩展NSH是指增加了FRI的NSH。FRI是在NSH中增加的指示流释放信息的标识。FR消息报文的初始报文部分使用流中对应的IP五元组构造一个报文即可。初始报文的净荷部分不做要求，可有可无。携带了IP五元组便可以指明对应的流。
如图9所示为又一实施例中业务功能链中的资源释放方法的时序图。本实施例中，有某一个包含业务功能SF1和业务功能SF2的业务功能链SPI1，业务功能SF1和业务功能SF2都支持NSH。有一个流Flow1在路径SPI1上进行转发，现在这个流Flow1已经结束。Classifier已经感知到流Flow1已经结束，本流程的目的是Classifier通过发送FR消息报文，帮助业务功能SF1和业务功能SF2及时释放掉流Flow1对应的资源。具体实施方式包括步骤901至步骤906。
步骤901：Classifier检测到流结束，构造FR消息报文，使用和流Flow1一致的SPI/SI。Classifier发送FR消息报文给SFF。
步骤902：SFF收到FR消息报文，并不进行特殊区分，根据SPI和SI转发给对应的下一跳即可。本实施例中，SFF将FR消息报文转发给业务功能SF1。
步骤903：业务功能SF1收到FR消息报文。根据FR消息报文携带的信息，知道是流Flow1已经结束，则释放流Flow1对应的资源。根据FR消息报文的SPI和SI得知自己不是业务功能链上最后一跳的SF，则将报文按照正常的Flow1的报文处理(即：修改SI的值)。
步骤904：业务功能SF1发送FR消息报文给SFF。
步骤905：类似步骤S902，SFF将FR消息报文给业务功能SF2。
步骤906：业务功能SF2收到FR消息报文。根据FR消息报文携带的信息，知道是流Flow1已经结束，则释放流Flow1对应的资源。根据FR消 息报文的SPI和SI得知自己是业务功能链上最后一跳的SF，则不再将报文发给SFF。
其中，FR消息报文是在NSH封装的报文基础上进行扩展NSH部分的报文。扩展NSH是指增加了FRI的NSH。FRI是在NSH中增加的指示流释放信息的标识。FR消息报文的初始报文部分使用流中对应的IP五元组构造一个报文即可。初始报文的净荷部分不做要求，可有可无。携带了IP五元组便可以指明对应的流。
如图10所示为又一实施例中业务功能链中的资源释放方法的时序图。本实施例中，有某一个包含业务功能SF1和业务功能SF2的业务功能链SPI1，业务功能SF1和业务功能SF2都不支持NSH，使用业务功能代理SFC Proxy1和业务功能代理SFC Proxy2分别作为业务功能SF1和业务功能SF2的代理部署到SFC网络中。有一个流Flow1在路径SPI1上进行转发，现在这个流Flow1已经结束。Classifier已经感知到流Flow1已经结束，本流程的目的是Classifier通过发送FR消息报文，帮助业务功能代理SFC Proxy1和业务功能代理SFC Proxy2及时释放掉流Flow1对应的资源。具体实施方式包括步骤1001至步骤1006。
步骤1001：Classifier检测到流结束，构造FR消息报文，使用和流Flow1一致的SPI/SI。Classifier发送FR消息报文给SFF。
步骤1002：SFF收到FR消息报文，并不进行特殊区分，根据SPI和SI转发给对应的下一跳即可。本实施例中，SFF将FR消息报文转发给业务功能代理SFC Proxy1。
步骤1003：业务功能代理SFC Proxy1收到FR消息报文，根据FR报文携带的信息，知道是流Flow1已经结束，则释放流Flow1对应的资源。根据FR消息报文的SPI和SI得知自己不是业务功能链上最后一跳，则将报文按照正常的流Flow1的报文处理(即：修改SI的值)。
步骤1004：业务功能代理SFC Proxy1发送FR消息报文给SFF。
步骤1005：类似步骤S1002，SFF将FR消息报文给业务功能代理SFC Proxy2。
步骤1006：业务功能代理SFC Proxy2收到FR消息报文，根据FR消息报文携带的信息，知道是流Flow1已经结束，则释放流Flow1对应的资源。根据FR消息报文的SPI和SI得知自己是业务功能链上最后一跳，则不再将报文发给SFF。
在一个实施例中的业务功能链中的资源释放方法，如图11所示，包括以下步骤：
步骤S220：检测到流处于结束状态时构造流释放消息报文(可以理解为FR消息报文)。
FR消息报文携带有FRI和流的链路信息。在FR消息报文中携带FRI的具体方式并不唯一，可以是携带在FR报文的基本头部中，也可以是携带在FR报文的上下文头部中。
步骤S240：根据链路信息发送流释放消息报文(可以理解为FR消息报文)，以使接收到流释放消息报文的功能节点根据流释放消息报文中携带的流释放标识释放对应的资源。
在构造FR消息报文后，可直接根据链路信息将FR消息报文发送至对应的SFC上后续的节点。当SFC的功能节点接收到FR消息报文后，可根据FR消息报文中携带的FRI释放对应的资源，避免出现因而无法及时释放资源造成服务质量下降问题。
上述业务功能链中的资源释放方法，通过监测流的状态，并在流处于结束状态时构造并发送流释放消息报文(可以理解为FR消息报文)，使得功能节点及时释放对应的资源，能够及时感知流结束并进行资源释放操作，避免了出现因无法及时释放资源造成服务质量下降的问题，提高了业务服务质量。
在一个实施例中，流释放标识位于流释放消息报文的基本头部的保留比特位。通过选取FR消息报文的基本头部的保留比特位作为FRI，操作简便且易识别。
在一个实施例中，流释放消息报文携带有流释放标识，包括：若业务功能链封装格式为定长格式，则选取流释放消息报文的必选上下文头部的 比特位作为流释放标识；若业务功能链封装格式为变长格式，则在流释放消息报文中生成变长上下文头部作为流释放标识。
SFC封装的类型可以有多种，同一封装类型的封装格式也有多种可供选择。SFC封装格式具体可包括定长格式和变长格式。根据SFC封装格式对应提供两种不同的FRI设置方式，可根据实际情况来对应设置FRI。
在一个实施例中的业务功能链中的资源释放方法，如图12所示，该方法包括：
步骤S320：接收业务功能转发器转发的流释放消息报文(可以理解为FR消息报文)。
FR消息报文携带有流释放标识(可以理解为FRI)，用作识别FR消息报文。FR消息报文还可携带有流的链路信息，业务功能转发器(可以理解为SFF)根据链路信息对流释放消息报文进行转发。在FR消息报文中携带FRI的具体方式并不唯一，可以是携带在FR报文的基本头部中，也可以是携带在FR报文的上下文头部中。
步骤S340：根据流释放消息报文(可以理解为FR消息报文)中携带的流释放标识释放对应的资源。
在接收到FR消息报文后，根据FR消息报文中携带的FRI释放对应的资源，避免出现因而无法及时释放资源造成服务质量下降问题。
上述业务功能链中的资源释放方法，在接收到流释放消息报文时释放对应的资源，能够及时进行资源释放操作，避免了出现因无法及时释放资源造成服务质量下降的问题，提高了业务服务质量。
在一个实施例中，FR消息报文中还携带有流的链路信息。如图13所示，步骤S340之后，该方法还包括以下步骤：
步骤S360：根据流释放消息报文(可以理解为FR消息报文)中的链路信息，判断自身是否是业务功能链上的最后一跳。
根据链路信息可判断自身是否是SFC上的最后一跳，若是，则说明对应流在SFC的处理路径终止，可不返回报文至SFF；若否，则进行步骤S380。
步骤S380：将流释放消息报文返回至业务功能转发器。
返回FR消息报文至SFF，以便SFF将FR消息报文转发至下一功能节点进行资源释放操作。
本实施例中，在检测到自身不是SFC上的最后一跳时，还返回FR消息报文至SFF，以使下一功能节点同样释放对应的占资源，根据链路信息依次释放各功能节点中对应的资源，避免出现遗漏，提高SFC资源释放可靠性和全面性。
在一实施例中的业务功能链中的资源释放系统，如图14所示，该系统包括分类器110、业务功能转发器120和至少一个功能节点130。其中：
分类器110配置为在检测到流处于结束状态时构造流释放消息报文，还配置为根据链路信息将流释放消息报文发送至对应的业务功能转发器。
流释放消息报文(可以理解为SR消息报文)携带有流释放标识(可以理解为FRI)和流的链路信息。在FR消息报文中携带FRI的具体方式并不唯一，可以是携带在FR消息报文的基本头部中，也可以是携带在FR消息报文的上下文头部中。
业务功能转发器120配置为根据链路信息将流释放消息报文转发至对应的功能节点。
具体地，SFF接收到FR消息报文后，按照携带的链路信息将FR消息报文转发至对应的功能节点。
功能节点130配置为在接收到流释放消息报文后，根据流释放消息报文中携带的流释放标识释放对应的资源。
功能节点在接收到FR消息报文后，根据FR消息报文中携带的FRI释放对应的资源，避免出现因而无法及时释放资源造成服务质量下降问题。
上述业务功能链中的资源释放系统，在检测到流处于结束状态后，分类器110构造携带有流释放标识和流的链路信息的流释放消息报文，并经业务功能转发器120发送至功能节点。功能节点130在接收到流释放消息报文后，根据流释放消息报文中携带的流释放标识释放对应的资源。通过监测流的状态，并在流处于结束状态时构造并发送流释放消息报文，使得功能节点及时释放对应的资源，能够及时感知流结束并进行资源释放操作， 避免了出现因无法及时释放资源造成服务质量下降的问题，提高了业务服务质量。
在一个实施例中，流释放标识位于流释放消息报文的基本头部的保留比特位。
SFC封装的类型可以有多种，包括NSH封装等类型，同一封装类型的封装格式也有多种可供选择。通过选取FR消息报文的基本头部的基本头部的保留比特位作为FRI，操作简便且易识别。
在一个实施例中，流释放消息报文携带有流释放标识，包括：若业务功能链封装格式为定长格式，则选取流释放消息报文的必选上下文头部的比特位作为流释放标识；若业务功能链封装格式为变长格式，则在流释放消息报文中生成变长上下文头部作为流释放标识。
以上即是根据SFC封装格式对应提供两种不同的FRI设置方式，可根据实际情况来对应设置FRI。
在一个实施例中，如图15所示，功能节点130包括可识别业务功能链的封装类型的业务功能132。
业务功能可以理解为SF，SF的数量可以是一个或多个，SF可直接识别SFC的封装类型。当SFF将FR消息报文发给SF后，SF同样可直接识别FR消息报文，并释放对应的资源，避免结束的流继续占用资源。
具体地，SF在接收到SFF转发的FR消息报文并释放对应的资源后，还检测自身是否位于SFC上的最后一跳，若是，则资源释放完成，SF可不返回FR消息报文至SFF；若否，则SF返回FR消息报文至SFF，以便SFF将FR消息报文发送至下一SF。可以理解，在其他实施例中，SFF也可以是将FR报文同时发送至所有的SF。
在一个实施例中，如图16所示，功能节点130包括业务功能代理134。
SFC Proxy的数量可以是一个或多个。当SFF将FR消息报文发给SFC Proxy后，SFC Proxy直接识别FR消息报文，并释放对应的资源，避免结束的流继续占用资源。
具体地，SFC Proxy在接收到SFF转发的FR消息报文并释放对应的资 源后，还检测自身是否位于SFC上的最后一跳，若是，则资源释放完成，SFC Proxy可不返回FR消息报文至SFF；若否，则SFC Proxy返回FR消息报文至SFF，以便SFF将FR报文发送至下一SFC Proxy。可以理解，在其他实施例中，SFF也可以是将FR消息报文同时发送至所有的SFC Proxy。
进一步地，在其中一个实施例中，如图17所示，功能节点130包括业务功能代理134和可识别业务功能链的封装类型的业务功能132。
SF和SFC Proxy的数量也可以是一个或多个，SF和SFC Proxy都可在接收到携带FRI的FR消息报文后，根据FR消息报文释放对应的资源。SF和SFC Proxy可以是同时进行资源释放，也可不是同时进行资源释放，且先后顺序并不唯一，具体由SFF根据链路信息转发FR报文的方式决定。
以SFF先将FR消息报文转发至SF，再转发至SFC Proxy为例。SFF在将FR消息报文转发至SF后，SF释放对应的资源，并在检测到自身不是位于SFC上的最后一跳时，返回FR消息报文至SFF。SFF将FR消息报文转发至SFC Proxy，SFC Proxy同样释放对应的资源，并检测自身是否是SFC上的最后一跳，若是，则资源释放完成，SFC Proxy不返回FR消息报文至SFF；若否，则SFC Proxy返回FR消息报文至SFF，以便SFF再次转发FR消息报文。
可以理解，在其他实施例中，SFF也可以是先将FR消息报文转发至SFC Proxy，在接收到SFC Proxy返回的FR消息报文后再转发至SF。
以上即是针对功能节点的不同形式提供了对应的资源释放方式，可根据功能节点的不同结构对应进行资源调整，提高资源释放操作的便利性和全面性。可以理解，功能节点的具体形式以及对应的资源释放方式包括但并不限于以上实施例。
在其中一个实施例中，功能节点130还配置为根据接收的流释放消息报文中的链路信息，判断自身是否是业务功能链上的最后一跳；若否，则将流释放消息报文返回至业务功能转发器120。业务功能转发器120还配置为接收返回的流释放消息报文，根据链路信息将流释放消息报文发送至下一功能节点130。
功能节点130在检测到自身不是业务功能链上的最后一跳时，还返回 FR报文至业务功能转发器120，以使下一功能节点130同样释放对应的资源，根据链路信息依次释放各功能节点130中对应的资源，避免出现遗漏，提高SFC资源释放可靠性和全面性。
可以理解，在其他实施例中，若功能节点130的数量只有一个，或者业务功能转发器120同时将FR消息报文发送至对应的所有功能节点130，则功能节点130在释放对应的资源后，不需判断对应流在SFC的处理路径是否终止，也不需返回FR消息报文。
在一个实施例中的业务功能链中的资源释放装置，如图18所示，包括报文构造模块220和报文发送模块240。
报文构造模块220配置为检测到流处于结束状态时构造流释放消息报文(可以理解为FR消息报文)。
FR消息报文携带有FRI和流的链路信息。在FR消息报文中携带FRI的具体方式并不唯一，可以是携带在FR消息报文的基本头部中，也可以是携带在FR报文的上下文头部中。
报文发送模块240配置为根据链路信息发送流释放消息报文，以使接收到流释放消息报文的功能节点根据流释放消息报文中携带的流释放标识释放对应的资源。
在构造FR消息报文后，可直接根据链路信息将FR消息报文发送至对应的SFC上后续的节点。当SFC的功能节点接收到FR消息报文后，可根据FR消息报文中携带的FRI释放对应的资源，避免出现因而无法及时释放资源造成服务质量下降问题。
实际应用时，报文构造模块220可由业务功能链中的资源释放装置中的处理器比如中央处理器(CPU，Central Processing Unit)、微处理器(MCU，Micro Control Unit)、数字信号处理器(DSP，Digital Signal Processor)或可编程逻辑阵列(FPGA，Field－Programmable Gate Array)等实现。所述报文发送模块240可由业务功能链中的资源释放装置中的通信接口实现。
上述业务功能链中的资源释放装置，通过监测流的状态，并在流处于结束状态时构造并发送流释放消息报文，使得功能节点及时释放对应的资 源，能够及时感知流结束并进行资源释放操作，避免了出现因无法及时释放资源造成服务质量下降的问题，提高了业务服务质量。
在一个实施例中，流释放标识位于流释放消息报文的基本头部的保留比特位。通过选取FR报文的基本头部的保留比特位作为FRI，操作简便且易识别。
在一个实施例中，流释放消息报文携带有流释放标识，包括：若业务功能链封装格式为定长格式，则选取流释放消息报文的必选上下文头部的比特位作为流释放标识；若业务功能链封装格式为变长格式，则在流释放消息报文中生成变长上下文头部作为流释放标识。
SFC封装的类型可以有多种，同一封装类型的封装格式也有多种可供选择。SFC封装格式具体可包括定长格式和变长格式。根据SFC封装格式对应提供两种不同的FRI设置方式，可根据实际情况来对应设置FRI。
在一个实施例中的业务功能链中的资源释放装置，如图19所示，包括报文接收模块320和资源释放模块340。
报文接收模块320配置为接收业务功能转发器转发的流释放消息报文(可以理解为FR消息报文)。
FR消息报文携带有FRI，用作识别FR消息报文。FR消息报文还可携带有流的链路信息，业务功能转发器根据链路信息对流释放消息报文进行转发。在FR消息报文中携带FRI的具体方式并不唯一，可以是携带在FR报文的基本头部中，也可以是携带在FR消息报文的上下文头部中。
资源释放模块340配置为根据流释放消息报文中携带的流释放标识释放对应的资源。
在接收到FR消息报文后，根据FR消息报文中携带的FRI释放对应的资源，避免出现因而无法及时释放资源造成服务质量下降问题。
上述业务功能链中的资源释放装置，在接收到流释放消息报文时释放对应的资源，能够及时进行资源释放操作，避免了出现因无法及时释放资源造成服务质量下降的问题，提高了业务服务质量。
在一个实施例中，FR报文中还携带有流的链路信息。如图20所示， 该装置还包括报文返回模块360。
报文返回模块360配置为在资源释放模块340根据流释放消息报文中携带的流释放标识释放对应的资源之后，根据接收的流释放消息报文中的链路信息，判断自身是否是业务功能链上的最后一跳；若否，则将流释放消息报文返回至业务功能转发器。
根据链路信息可判断自身是否是SFC上的最后一跳，若否，返回FR消息报文至SFF，以便SFF将FR消息报文转发至下一功能节点进行资源释放操作。
本实施例中，在检测到自身不是SFC上的最后一跳时，还返回FR消息报文至SFF，以使下一功能节点同样释放对应的占资源，根据链路信息依次释放各功能节点中对应的资源，避免出现遗漏，提高SFC资源释放可靠性和全面性。
实际应用时，报文接收模块320可由业务功能链中的资源释放装置中的通信接口实现；资源释放模块340可由业务功能链中的资源释放装置中的处理器比如CPU、MCU、DSP或FPGA等实现。报文返回模块360可由业务功能链中的资源释放装置中的处理器结合通信接口实现。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，所述程序可存储于一计算机可读取存储介质中，如本发明实施例中，该程序可存储于计算机系统的存储介质中，并被该计算机系统中的至少一个处理器执行，以实现包括如上述各方法的实施例的流程。其中，所述存储介质可为磁碟、光盘、只读存储记忆体(Read-Only Memory，ROM)或随机存储记忆体(Random Access Memory，RAM)等。
基于此，本发明实施例还提供了一种计算机存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现本发明实施例所述方法的步骤。
以上所述实施例的各技术特征可以进行任意的组合，为使描述简洁， 未对上述实施例中的各个技术特征所有可能的组合都进行描述，然而，只要这些技术特征的组合不存在矛盾，都应当认为是本说明书记载的范围。
以上所述实施例仅表达了本发明的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对发明专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本发明构思的前提下，还可以做出若干变形和改进，这些都属于本发明的保护范围。因此，本发明专利的保护范围应以所附权利要求为准。
工业实用性
本发明实施例提供的方案，通过监测流的状态，并在流处于结束状态时构造并发送流释放消息报文，使得功能节点及时释放对应的资源，能够及时感知流结束并进行资源释放操作，避免了出现因无法及时释放资源造成服务质量下降的问题，提高了业务服务质量。

Claims (21)

  1. 一种业务功能链中的资源释放方法，所述方法包括：
    分类器在检测到流处于结束状态时构造流释放消息报文，所述流释放消息报文携带有流释放标识和流的链路信息；
    所述分类器根据所述链路信息将所述流释放消息报文发送至对应的业务功能转发器；
    所述业务功能转发器根据所述链路信息将所述流释放消息报文转发至对应的功能节点；
    所述功能节点在接收到所述流释放消息报文后，根据所述流释放消息报文中携带的流释放标识释放对应的资源。
  2. 根据权利要求1所述的方法，其中，所述流释放标识位于所述流释放消息报文的基本头部的保留比特位。
  3. 根据权利要求1所述的方法，其中，所述方法还包括：
    若业务功能链封装格式为定长格式，则选取所述流释放消息报文的必选上下文头部的比特位作为所述流释放标识；
    或者，若业务功能链封装格式为变长格式，则在所述流释放消息报文中生成变长上下文头部作为所述流释放标识。
  4. 根据权利要求1所述的方法，其中，所述功能节点包括业务功能代理和/或可识别业务功能链的封装类型的业务功能。
  5. 根据权利要求1所述的方法，其中，所述功能节点在接收到所述流释放消息报文后，根据所述流释放消息报文中携带的流释放标识释放对应的资源之后，所述方法还包括：
    所述功能节点根据所述流释放消息报文中的所述链路信息，判断自身是否是业务功能链上的最后一跳；
    若否，则所述功能节点将所述流释放消息报文返回至所述业务功能转发器；
    所述业务功能转发器接收返回的流释放消息报文，根据所述链路信息 将所述流释放消息报文发送至下一功能节点。
  6. 一种业务功能链中的资源释放方法，所述方法包括：
    检测到流处于结束状态时构造流释放消息报文，所述流释放消息报文携带有流释放标识和流的链路信息；
    根据所述链路信息发送所述流释放消息报文，以使接收到所述流释放消息报文的功能节点根据所述流释放消息报文中携带的流释放标识释放对应的资源。
  7. 根据权利要求6所述的方法，其中，所述流释放标识位于所述流释放消息报文的基本头部的保留比特位。
  8. 根据权利要求6所述的方法，其中，所述方法还包括：
    若业务功能链封装格式为定长格式，则选取所述流释放消息报文的必选上下文头部的比特位作为所述流释放标识；
    或者，若业务功能链封装格式为变长格式，则在所述流释放消息报文中生成变长上下文头部作为所述流释放标识。
  9. 一种业务功能链中的资源释放方法，所述方法包括：
    接收业务功能转发器转发的流释放消息报文，所述流释放消息报文携带有流释放标识；
    根据所述流释放消息报文中携带的流释放标识释放对应的资源。
  10. 根据权利要求9所述的业务功能链中的资源释放方法，其中，所述流释放消息报文中还携带有流的链路信息；所述根据所述流释放消息报文中携带的流释放标识释放对应的资源之后，还包括：
    根据所述流释放消息报文中的所述链路信息，判断自身是否是业务功能链上的最后一跳；
    若否，则将所述流释放消息报文返回至所述业务功能转发器。
  11. 一种业务功能链中的资源释放系统，包括：
    分类器，配置为在检测到流处于结束状态时构造流释放消息报文，所述流释放消息报文携带有流释放标识和流的链路信息；以及根据所述链路 信息将所述流释放消息报文发送至对应的业务功能转发器；
    业务功能转发器，配置为根据所述链路信息将所述流释放消息报文转发至对应的功能节点；
    至少一个功能节点，配置为在接收到所述流释放消息报文后，根据所述流释放消息报文中携带的流释放标识释放对应的资源。
  12. 根据权利要求11所述的系统，其中，所述流释放标识位于所述流释放消息报文的基本头部的保留比特位。
  13. 根据权利要求11所述的系统，其中，所述分类器还配置为：
    若业务功能链的封装格式为定长格式，则选取所述流释放消息报文的必选上下文头部的比特位作为所述流释放标识；
    或者，若业务功能链封的装格式为变长格式，则在所述流释放消息报文中生成变长上下文头部作为所述流释放标识。
  14. 根据权利要求11所述的系统，其中，所述功能节点包括业务功能代理和/或可识别业务功能链的封装类型的业务功能。
  15. 根据权利要求11所述的系统，其中，所述功能节点还配置为根据接收的流释放消息报文中的所述链路信息，判断自身是否是业务功能链上的最后一跳；若否，则将所述流释放消息报文返回至所述业务功能转发器；
    所述业务功能转发器还配置为接收返回的流释放消息报文，根据所述链路信息将所述流释放消息报文发送至下一功能节点。
  16. 一种业务功能链中的资源释放装置，包括：
    报文构造模块，配置为检测到流处于结束状态时构造流释放消息报文，所述流释放消息报文携带有流释放标识和流的链路信息；
    报文发送模块，配置为根据所述链路信息发送所述流释放消息报文，以使接收到所述流释放消息报文的功能节点根据所述流释放消息报文中携带的流释放标识释放对应的资源。
  17. 根据权利要求16所述的装置，其中，所述流释放标识位于所述流释放消息报文的基本头部的保留比特位。
  18. 根据权利要求16所述的装置，其中，所述报文构造模块还配置为：
    若业务功能链封装格式为定长格式，则选取所述流释放消息报文的必选上下文头部的比特位作为所述流释放标识；
    或者，若业务功能链封装格式为变长格式，则在所述流释放消息报文中生成变长上下文头部作为所述流释放标识。
  19. 一种业务功能链中的资源释放装置，包括：
    报文接收模块，配置为接收业务功能转发器转发的流释放消息报文，所述流释放消息报文携带有流释放标识；
    资源释放模块，配置为根据所述流释放消息报文中携带的流释放标识释放对应的资源。
  20. 根据权利要求19所述的装置，其中，所述流释放消息报文中还携带有流的链路信息；所述装置还包括：
    报文返回模块，配置为在资源释放模块根据所述流释放消息报文中携带的流释放标识释放对应的资源之后，根据接收的流释放消息报文中的所述链路信息，判断自身是否是业务功能链上的最后一跳；若否，则将所述流释放消息报文返回至所述业务功能转发器。
  21. 一种计算机存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现权利要求6至8任一项所述方法的步骤，或者实现权利要求9至10任一项所述方法的步骤。
PCT/CN2017/082057 2016-06-06 2017-04-26 资源释放方法、系统、装置及计算机存储介质 WO2017211141A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610399169.8 2016-06-06
CN201610399169.8A CN107465634A (zh) 2016-06-06 2016-06-06 业务功能链中的资源释放方法、系统及装置

Publications (1)

Publication Number Publication Date
WO2017211141A1 true WO2017211141A1 (zh) 2017-12-14

Family

ID=60543733

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/082057 WO2017211141A1 (zh) 2016-06-06 2017-04-26 资源释放方法、系统、装置及计算机存储介质

Country Status (2)

Country Link
CN (2) CN107465533A (zh)
WO (1) WO2017211141A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112491729A (zh) * 2020-09-22 2021-03-12 中兴通讯股份有限公司 一种数据处理方法、装置、存储介质及电子装置
CN114268668A (zh) * 2021-12-20 2022-04-01 中国电信股份有限公司 数据处理方法、系统、装置、电子设备及存储介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR3081644A1 (fr) * 2018-06-22 2019-11-29 Orange Procede de decouverte de fonctions intermediaires et de selection d'un chemin entre deux equipements de communication
CN109450875B (zh) * 2018-10-23 2020-02-07 清华大学 Mac层封装方法及装置
CN114826998B (zh) * 2021-01-29 2023-05-16 中国电信股份有限公司 基于业务功能链的报文转发方法、控制器以及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1716942A (zh) * 2004-06-14 2006-01-04 华为技术有限公司 一种实现端到端服务质量可靠性保证的方法
CN1798134A (zh) * 2004-12-30 2006-07-05 中兴通讯股份有限公司 一种实现带宽代理与域内路由器通信的方法
US9049148B1 (en) * 2012-09-28 2015-06-02 Juniper Networks, Inc. Dynamic forwarding plane reconfiguration in a network device
CN104954259A (zh) * 2015-04-28 2015-09-30 瑞斯康达科技发展股份有限公司 一种实现ptn业务收敛的方法及pe

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1716942A (zh) * 2004-06-14 2006-01-04 华为技术有限公司 一种实现端到端服务质量可靠性保证的方法
CN1798134A (zh) * 2004-12-30 2006-07-05 中兴通讯股份有限公司 一种实现带宽代理与域内路由器通信的方法
US9049148B1 (en) * 2012-09-28 2015-06-02 Juniper Networks, Inc. Dynamic forwarding plane reconfiguration in a network device
CN104954259A (zh) * 2015-04-28 2015-09-30 瑞斯康达科技发展股份有限公司 一种实现ptn业务收敛的方法及pe

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112491729A (zh) * 2020-09-22 2021-03-12 中兴通讯股份有限公司 一种数据处理方法、装置、存储介质及电子装置
CN114268668A (zh) * 2021-12-20 2022-04-01 中国电信股份有限公司 数据处理方法、系统、装置、电子设备及存储介质

Also Published As

Publication number Publication date
CN107465533A (zh) 2017-12-12
CN107465634A (zh) 2017-12-12

Similar Documents

Publication Publication Date Title
WO2017211141A1 (zh) 资源释放方法、系统、装置及计算机存储介质
US20210219105A1 (en) Communications method and apparatus
CN109314695B (zh) 确定用户面协议栈的方法、控制面网元和系统
EP3764732B1 (en) Packet transmission methods and apparatus using two network tunnels
JP2020109999A (ja) ユーザ装置及びその動作方法、並びにネットワーク機器及び無線通信システム
JP4430715B2 (ja) インターネットプロトコルマルチメディアサブシステムにおけるパケット呼サービスに関連する制御メッセージを送受信する方法及び装置
WO2019228214A1 (zh) 一种无线承载建立、业务流的监测方法及装置
WO2019076306A1 (zh) 数据传输通道的处理方法、装置和系统
US11343701B2 (en) Wireless communications apparatus and methods
CN109088821B (zh) 报文传输方法、业务链系统以及计算机可读存储介质
WO2021232841A1 (zh) 通信方法和装置
US9992109B2 (en) Data transmission method, apparatus and system
WO2017177753A1 (zh) 一种基于流的承载管理方法、数据传输方法及装置
WO2009009992A1 (fr) Procédé, système, extrémité de source et extrémité de destination pour indexer le trajet de commutation d'étiquettes au moyen d'une étiquette
CN111869310A (zh) 用于执行小数据快速路径通信的方法和系统
JP6826577B2 (ja) 端末装置、基地局装置、および、方法
WO2022121934A1 (zh) 重路由方法及装置、通信设备
KR100414918B1 (ko) 이동통신시스템의 서비스 품질 우선순위에 따른 호처리시스템 및 방법
JP2019180090A (ja) モバイル通信ネットワークにおける可変容量データ送信
WO2022160108A1 (zh) 无线通信方法、通信装置及通信系统
CN111373834B (zh) 用于建立数据无线承载的客户端设备、接入网设备、方法及计算机程序
US20160087934A1 (en) Communication system, communication method, and transmission apparatus
EP3783996B1 (en) Communication methods and devices for processing data packets based on a correct sequence
EP4277210A1 (en) Method for measuring packet loss rate, and communication apparatus and communication system
CN113132222B (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: 17809581

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

Country of ref document: EP

Kind code of ref document: A1