WO2015154393A1 - 业务节点能力处理方法、装置、业务分类器及业务控制器 - Google Patents

业务节点能力处理方法、装置、业务分类器及业务控制器 Download PDF

Info

Publication number
WO2015154393A1
WO2015154393A1 PCT/CN2014/087355 CN2014087355W WO2015154393A1 WO 2015154393 A1 WO2015154393 A1 WO 2015154393A1 CN 2014087355 W CN2014087355 W CN 2014087355W WO 2015154393 A1 WO2015154393 A1 WO 2015154393A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
processing
exchange information
capabilities
capability
Prior art date
Application number
PCT/CN2014/087355
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 JP2017506290A priority Critical patent/JP6420462B2/ja
Priority to EP14888913.2A priority patent/EP3166273B1/en
Priority to US15/501,938 priority patent/US10284426B2/en
Priority to KR1020177006089A priority patent/KR101952187B1/ko
Publication of WO2015154393A1 publication Critical patent/WO2015154393A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0866—Checking the configuration
    • H04L41/0869—Validating the configuration within one network element
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63—Routing a service request depending on the request content or context
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/26—Route discovery packet

Definitions

  • the present invention relates to the field of communications, and in particular, to a service node capability processing method, apparatus, service classifier, and service controller.
  • Service Function Chaining is a network technology currently being researched and standardized. Since the development of the data center network to the Overlay network, the network edge has become the demarcation point between the virtual network and the physical network, where the network edge is a server or a ToR, and possibly a gateway.
  • Overlay technology does not solve all the problems. There are many middlewares in the data center, such as firewall/load balancer. These devices are processed based on user services. If you tunnel through these devices, it is obviously No way.
  • This deployment model of the data center requires that the virtual firewall/load balancer can be deployed arbitrarily in the network, that is, independent of the network topology.
  • the new question is how to handle traffic through the virtual firewall/load balancer flexibly.
  • New middleware such as virtual firewalls/load balancers are created. These virtual firewalls/load balancers are deployed at the edge of the network and can be implemented by standard servers.
  • a service processing function such as a virtual firewall/load balancer/gateway is called a service function (Service Function, referred to as SF), and traffic is processed through a series of Service Functions to form a service function chain (Service Function).
  • SF service function
  • Service Function Service Function
  • Chaining referred to as SFC
  • 1 is a schematic diagram of a service function chain in the related art. As shown in FIG. 1, the solid line and the dotted line with arrows respectively represent two service function chains.
  • Service Overlay that is, Overlay technology that each network edge node needs to communicate
  • the Generic Service Control Plane is the controller that forms the Service Function Chaining.
  • Service Classifier that is, need to identify the stream, and then perform a specific Service Function Chaining process
  • Control plane metadata (Dataplane Metadata), which is a major feature, Metadata (metadata) allows between Service Classifier and SF, between SF and SF, and between SF and external systems, each edge business processing node, Ability to communicate and share exchange information with each other for a certain business processing purpose.
  • FIG. 2 is an example diagram of a service function path in the related art. As shown in FIG. 2, the SFP starts from the service classifier and passes through several service function instances to achieve the purpose. A business processing path of the ground.
  • the network device service function and the forwarding are separated, thereby implementing independent operation and processing of the service function, and improving the forwarding performance of the network device.
  • Dataplane Metadata is a data area that can store exchange information between nodes. Therefore, in addition to the delivery of the message, the service information SF in the service function chain can be placed in the Dataplane Metadata, so that the next node can conveniently obtain the calculation result of the previous node and avoid double calculation. Metadata will be sent along with the message to the next processing unit.
  • FIG. 3 is a diagram showing an example of packet content encapsulated in Dataplane Metadata in the related art. As shown in FIG. 3, Dataplane Metadata can be encapsulated in a packet to be sent in a message;
  • FIG. 4 is a diagram of a related image in the related art. As shown in Figure 4, Dataplane Metadata can also be sent in parallel as a separate message body and message.
  • the classifier->SF1->SF2 is a component of a service function path (SFP).
  • SFP service function path
  • the message is processed first by SF1 and then by SF2.
  • Both SF1 and SF2 need to find the same ACL table, so the process of searching for ACL entries will be performed once on SF1 and SF2, which causes the problem of SF2 repeated lookup.
  • the SF1 looks up the ACL and encapsulates the result with the packet and sends it to the SF2.
  • the SF2 After receiving the Metadata, the SF2 directly takes the ACL lookup in the Metadata. The result is used to avoid the process of repeatedly searching for the ACL table, thus improving the forwarding performance of the message in the SFC.
  • SF1 does not know whether SF2 needs ACL lookup results.
  • SF1 searches for entries not only one type of ACL, but also other types, and thus is not targeted when exchanging information. , causing blind exchanges to create a waste of resources.
  • the present invention provides a service node capability processing method, apparatus, service classifier and service controller, so as to at least solve the related art, since the information exchanged between nodes is not targeted, there is a problem that blind exchange generates resource waste.
  • a service node capability processing method comprising: determining an exchange information set of a service node on a service function chain for processing a data message, wherein the exchange information set includes the service An intersection of the capabilities of the service nodes on the function chain; the set of exchange information is encapsulated in the data message, wherein the exchange information set is used by the service node to read the datagram encapsulated in the datagram.
  • determining the set of exchange information of the service node on the service function chain for processing the data message comprises: determining capabilities of each service node on the service function chain; selecting at least two The same ability of a service node is the intersection of the capabilities of the service node.
  • the exchange information set is encapsulated in the data packet by using at least one of the following manners: a bitmap format is adopted, and a queue format is adopted.
  • a service node capability processing method comprising: receiving a data message carrying a set of exchange information of a service node on a service function chain, wherein the exchange information set includes the service An intersection of capabilities between the service nodes on the function chain; processing for obtaining the capability corresponding to the intersection of the capabilities of the service nodes encapsulated in the data message according to the exchange information set result.
  • the method further includes: determining the The service node includes an intermediate node capability that is not encapsulated in the data packet, but the intermediate node capability exists in the exchange information set; processing the intermediate node capability to obtain an intermediate node capability processing result;
  • the intermediate node capability processing result is encapsulated in a data packet forwarded by a next service node.
  • the method further includes: The ability to exchange information sets performs at least one of the following: add, delete, modify.
  • a service node capability processing apparatus including: a first determining module, configured to determine an exchange information set of a service node on a service function chain for processing a data message, where The set of exchange information includes an intersection of capabilities between the service nodes on the service function chain; the first encapsulation module is configured to encapsulate the exchange information set in the data message, wherein the exchange information And a set of processing results obtained after the capability processing by the service node reads the intersection of the capabilities of the service nodes encapsulated in the data message.
  • the first determining module includes: a determining unit, configured to determine capabilities of each service node on the service function chain; and a selecting unit configured to select at least two service nodes with the same capability as the service node The intersection of abilities.
  • a service classifier is provided, comprising the device of any of the above.
  • a service controller comprising the apparatus of any of the above.
  • a service node capability processing apparatus comprising: a receiving module, configured to receive a data message carrying a set of exchange information of a service node on a service function chain, wherein the exchange information The set includes an intersection of the capabilities of the service nodes on the service function chain; the reading module is configured to read, between the service nodes, encapsulated in the data packet according to the exchange information set The intersection of capabilities corresponds to the ability to process the results obtained after processing.
  • the apparatus further comprises: a second determining module, configured to determine that the service node includes an intermediate node capability that is not encapsulated in the data packet, but the intermediate node capability exists in the exchange information set
  • the processing module is configured to process the intermediate node capability to obtain an intermediate node capability processing result
  • the second encapsulating module is configured to encapsulate the intermediate node capability processing result in a data packet forwarded by the next service node .
  • the apparatus further comprises: an execution module configured to perform at least one of: adding, deleting, modifying, to the capabilities in the set of exchange information.
  • a service node comprising the apparatus of any of the above.
  • an exchange information set for determining a service node on a service function chain for processing a data message, wherein the exchange information set includes an intersection of capabilities between the service nodes on the service function chain;
  • the set of exchange information is encapsulated in the data message, wherein the exchange information set is used by the service node to read an intersection of capabilities of the service nodes that have been encapsulated in the data message.
  • FIG. 1 is a schematic diagram of a service function chain in the related art
  • FIG. 2 is a diagram showing an example of a service function path in the related art
  • FIG. 3 is a diagram showing an example of packet content encapsulated by Dataplane Metadata in the related art
  • FIG. 4 is a diagram showing an example of a Dataplane Metadata as an independent message in the related art
  • FIG. 5 is a flowchart of a method for processing a service node capability according to an embodiment of the present invention
  • FIG. 6 is a flowchart of a second method for processing a service node capability according to an embodiment of the present invention.
  • FIG. 7 is a structural block diagram of a service node capability processing apparatus 1 according to an embodiment of the present invention.
  • FIG. 8 is a block diagram showing a preferred structure of the determining module 72 in the service node capability processing apparatus 1 according to an embodiment of the present invention.
  • FIG. 9 is a structural block diagram of a traffic classifier according to an embodiment of the present invention.
  • FIG. 10 is a structural block diagram of a service controller according to an embodiment of the present invention.
  • FIG. 11 is a structural block diagram of a service node capability processing apparatus 2 according to an embodiment of the present invention.
  • FIG. 12 is a block diagram 1 of a preferred structure of a service node capability processing apparatus 2 according to an embodiment of the present invention
  • FIG. 13 is a block diagram 2 of a preferred structure of a service node capability processing apparatus 2 according to an embodiment of the present invention
  • FIG. 14 is a structural block diagram of a service node according to an embodiment of the present invention.
  • FIG. 15 is a schematic diagram of a bitmap format in a metadata format in accordance with an embodiment of the present invention.
  • 16 is a schematic diagram of a queue format in which metadata is encapsulated in Metadata according to an embodiment of the present invention
  • FIG. 17 is a diagram of an SFP1-based deployment scenario according to a preferred embodiment of the present invention.
  • FIG. 18 is a diagram of an SFP2-based deployment scenario according to a preferred embodiment of the present invention.
  • FIG. 5 is a flowchart of a service node capability processing method 1 according to an embodiment of the present invention. As shown in FIG. 5, the process includes the following steps:
  • Step S502 determining an exchange information set of a service node on a service function chain for processing a data message, where the exchange information set includes an intersection of capabilities between service nodes on the service function chain;
  • Step S504 the exchange information set is encapsulated in a data message, wherein the exchange information set is used by the service node to read the processing result obtained after the capability corresponding to the intersection of the capabilities of the service nodes encapsulated in the data message.
  • the exchange information set including the intersection of the capabilities of the service nodes on the service function chain is encapsulated in the data packet, so that the service node can directly read the capability between the service nodes encapsulated in the data packet.
  • the processing result obtained after the intersection of the corresponding capability processing, that is, the exchange information set is stored in the data message, so that the effective exchange information is transmitted between the service nodes, and the related technology is solved, because the information exchanged between the nodes is not targeted, and thus there is blindness.
  • the exchange generates the problem of waste of resources, thereby achieving the effect of effectively avoiding waste of field resources caused by invalid information exchange.
  • the capability of the service node may include multiple types, for example, the capability of processing the entry of the service node, the capability of processing a parameter in the entry, or the service.
  • the ability of a node to perform parameter configuration for a specific service is not specifically limited herein.
  • the capability of each service node on the service function chain may be determined first; then, at least two are selected.
  • the same ability of the service nodes is the intersection of the capabilities of the service nodes. It should be noted that, when specifically selecting the intersection, the number of service nodes having the same capability may be determined. For example, two service nodes may have the same capability to determine the intersection, or may be three. Or more than three business nodes have the same ability to determine the intersection. Due to specific needs.
  • the data information can be encapsulated in the datagram manner in a plurality of manners.
  • the data packet can be encapsulated in at least one of the following manners: using a bitmap format, using a queue The way the format is.
  • FIG. 6 is a flowchart of a service node capability processing method 2 according to an embodiment of the present invention. As shown in FIG. 6, the process includes the following steps:
  • Step S602 receiving a data packet carrying an exchange information set of a service node on a service function chain, where the exchange information set includes an intersection of capabilities between service nodes on the service function chain;
  • Step S604 read the processing result obtained after the capability processing corresponding to the intersection of the capabilities of the service nodes encapsulated in the data message.
  • the processing result obtained after the capability corresponding to the intersection of the capabilities of the service nodes encapsulated in the data packet is read, so that the service nodes are between the service nodes.
  • the effective exchange of information is transmitted, and in the related art, since the information exchanged between the nodes is not targeted, there is a problem that the blind exchange generates waste of resources, thereby achieving the effect of effectively avoiding waste of field resources caused by invalid information exchange.
  • the following processing may also be performed: first determining whether the service node exists The capability of self-processing is required.
  • the service node includes the intermediate node capability that the processing result is not encapsulated in the data packet, but the intermediate node capability exists in the exchange information set;
  • the processing is performed to obtain the intermediate node capability processing result;
  • the intermediate node capability processing result is encapsulated in the data packet forwarded by the next service node, and the processing efficiency of the subsequent service node can be facilitated by the subsequent processing, that is, subsequent
  • the node only needs to read the result of processing the capability from the received message.
  • the capability in the exchange information set can also be performed. At least one of the following operations: add, delete, modify, flexible changes according to demand.
  • a service node capability processing device is also provided, which is used to implement the foregoing embodiments and preferred embodiments, and has not been described again.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 7 is a structural block diagram of a service node capability processing apparatus 1 according to an embodiment of the present invention. As shown in FIG. 7, the apparatus includes: a first determining module 72 and a first encapsulating module 74, which will be described below.
  • the determining module 72 is configured to determine a set of exchange information of the service nodes on the service function chain for processing the data message, wherein the exchange information set includes an intersection of the capabilities between the service nodes on the service function chain; the encapsulation module 74 is connected to The determining module 72 is configured to encapsulate the exchange information set in the data packet, wherein the exchange information set is used by the service node to read the capability corresponding to the intersection of the capabilities of the service nodes encapsulated in the data message. The processing result obtained.
  • FIG. 8 is a block diagram showing a preferred structure of the first determining module 72 in the service node capability processing apparatus 1 according to the embodiment of the present invention.
  • the first determining module 72 includes: a determining unit 82 and a selecting unit 84. The first determining module 72 will be described.
  • the determining unit 82 is configured to determine the capabilities of the respective service nodes on the service function chain; the selecting unit 84 is coupled to the determining unit 82, and is configured to select an intersection of the capabilities of the at least two service nodes that are the same as the capabilities of the service nodes.
  • FIG. 9 is a structural block diagram of a service classifier according to an embodiment of the present invention. As shown in FIG. 9, the service classifier 90 includes the service node capability processing device 92 of any of the above.
  • FIG. 10 is a structural block diagram of a service controller according to an embodiment of the present invention. As shown in FIG. 10, the service controller 100 includes the service node capability processing device 92 of any of the above.
  • FIG. 11 is a structural block diagram of a service node capability processing apparatus 2 according to an embodiment of the present invention. As shown in FIG. 11, the apparatus includes a receiving module 112 and a reading module 114, which will be described below.
  • the receiving module 112 is configured to receive a data packet carrying a set of exchange information of the service node on the service function chain, where the exchange information set includes an intersection of capabilities between the service nodes on the service function chain; the reading module 114 is connected to The receiving module 112 is configured to read the processing result obtained after the capability processing corresponding to the intersection of the capabilities of the service nodes encapsulated in the data packet according to the exchange information set.
  • FIG. 12 is a block diagram of a preferred structure of a service node capability processing apparatus 2 according to an embodiment of the present invention. As shown in FIG. 12, the apparatus includes: second determining module 122, processing, in addition to all the structures shown in FIG. Module 124 and second package module 126, the device will be described below.
  • the second determining module 122 is connected to the reading module 114, and is configured to determine that the service node includes an intermediate node capability that is not encapsulated in the data packet, but the intermediate node capability exists in the exchange information set; the processing module 124, the connection The second determining module 122 is configured to process the intermediate node capability to obtain the intermediate node capability processing result; the second encapsulating module 126 is connected to the processing module 124, and is configured to encapsulate the intermediate node capability processing result in the next service. The data packet forwarded by the node.
  • FIG. 13 is a block diagram of a preferred structure of a service node capability processing apparatus 2 according to an embodiment of the present invention. As shown in FIG. 13, the apparatus includes, in addition to all the structures shown in FIG. 11, an execution module 132. The execution module 132 is described.
  • the execution module 132 is configured to perform at least one of the following operations on the capabilities in the exchange information set: add, delete, modify.
  • FIG. 14 is a structural block diagram of a service node according to an embodiment of the present invention. As shown in FIG. 14, the service node 140 includes a data packet entry processing device 142 of any of the above.
  • the validity of the node information exchange is realized by how to notify the SF1 here of what parameters or what results are added to the metadata.
  • a scheme for exchanging information types is stored in metadata to solve the above drawbacks.
  • the type of the exchange information may refer to what information is exchanged between the nodes.
  • the ACL number is an exchange information type
  • the user ID is an exchange information type
  • the DPI processing result is an exchange information type.
  • the related art can solve the problem that the effective information is transmitted between the SFP nodes, and the Metadata field space is wasted due to the possibility of transmitting some invalid exchange information.
  • the method will be described below.
  • the service classifier classifier After receiving the external packet, the service classifier classifier classifies the field according to the field information of the packet, and determines a service function path (SFP); the service classifier or controller analyzes all the service function paths.
  • the node and summarizes the intersection of all the entries when all its nodes are processed.
  • the intersection of the entries refers to all the nodes in the SFP: a number of entries to be queried when the node 1 processes the packet, a number of entries to be queried when the node 2 processes the packet, and a node 3 needs to process the packet.
  • Several entries of the query ... the number of entries that the node N needs to query when processing the message, and then select the set of the same entries that need to be processed when any two nodes of the nodes 1, 2, 3, ... N process the message. .
  • the service classifier or controller summarizes the set of exchange information types (ie, the above-mentioned exchange information set) necessary for the service function path according to the intersection of all the node entries on the SFP; the service classifier encapsulates the set of the exchange information types in the metadata. In the middle, the encapsulation required by the SFC is continued and sent to the next processing node in the SFP.
  • FIG. 15 is a schematic diagram of a bitmap information format encapsulation in Metadata according to an embodiment of the present invention, as shown in FIG.
  • the bitmap format can be used in Metadata, that is, each bit in the bitmap represents a type of exchange information.
  • FIG. 16 is a schematic diagram of a queue format of a set of exchange information types encapsulated in Metadata according to an embodiment of the present invention.
  • the set of exchange information types is encapsulated in Metadata and uses a queue format, that is, each of the queues.
  • the item represents a type of exchange information.
  • the packet After the packet arrives at the next processing node, it searches for related entries according to the service characteristics of the node and parses the set of exchange information types in the Metadata. If the type to which the entry belongs is in the set of exchange information types, the following table is recorded. The result of the item is searched, and the result is encapsulated in Metadata for use by the subsequent processing node; if the type to which the item belongs is not in the set of exchange information types, the result of the lookup table item is not recorded in the metadata.
  • the node can add or delete one or more types of exchange information in the metadata.
  • FIG. 17 is a schematic diagram of an SFP1 (SF1-SF2) based deployment scenario according to a preferred embodiment of the present invention. As shown in FIG. 17, the embodiment includes the following processing:
  • the SF1 and SF2 are processed.
  • the user sends a message to access the external network.
  • the classifier After receiving the packet, the classifier performs classification according to the configuration policy of step 101, and generates SFP1, where SFP1 passes through two service function instances of SF1 and SF2.
  • SF1 needs to process three entries of the entry 1, the entry 2, and the entry 3 for the processing of the packet; the SF2 needs to perform the entry of the entry 1, the entry 2, and the entry 4 in the processing of the packet. Processing
  • the classifier obtains the exchange information type of the entire service function chain according to the analysis result of the step 104, and includes the entry 1 and the entry 2;
  • the classifier allocates a field of a 128-bit bitmap, and sets the 0th bit and the first position of the bitmap to 1, and the other positions to 0; wherein the 0th bit of the bitmap represents the entry 1 and the first bit represents Entry 2;
  • the classifier encapsulates the field of the 128-bit bitmap in the packet, and sends the field to the SF1 service function instance.
  • the SF1 service function instance performs the processing of the entry 1, the entry 2, and the entry 3, and reads the field of the 128-bit bitmap, and finds that the 0th bit and the 1st bit are set to 1. Therefore, the SF1 service adds the result of the entry 1 and the result of the entry 2 to the metadata and sends it to the SF2 service function instance;
  • the SF2 service function instance After receiving the packet sent by the SF1 service function instance, the SF2 service function instance reads the field of the 128-bit bitmap and finds that the 0th bit and the 1st bit are set to 1. The SF2 service function instance directly reads the result of the entry 1 and the result of the entry 2 in the metadata, thereby avoiding the duplicate search of the two, and improving the processing efficiency of the firewall service function instance;
  • the packet is sent to the network.
  • FIG. 18 is a schematic diagram of an SFP2 (SF3-SF4-SF5)-based deployment scenario according to a preferred embodiment of the present invention. As shown in FIG. 18, the embodiment includes the following processing:
  • the network management user needs to perform SF3, SF4, and SF5 processing when the user processes the gateway;
  • the SF3 needs to process the three entries of the entry 10, the entry 11, and the entry 12 for the processing of the packet; the SF4 needs to access the three entries of the entry 10, the entry 11, and the 13 The processing of the item; the processing of the packet by the SF5 requires the processing of two entries of the entry 10 and the entry 11.
  • the SFC controller according to the analysis result of the step 202, the exchange information type of the entire service function chain includes the entry 10, the entry 11;
  • the SFC controller sends the SFP2 of the user and exchanges the information type to the classifier.
  • the user sends a message to access the external network.
  • the classifier After receiving the message, the classifier allocates a field of two bytes, and sets the 0th byte of the field to 8; the first byte is set to 13; and the field value of 8 indicates that the exchange information type is Entry 10; a field value of 13 indicates that the exchange information type is entry 11; the classifier repackages the field into a new Metadata message according to the IP address of the next node.
  • the classifier sends the packet and the Metadata packet to the SF3 service function instance in sequence.
  • the SF3 service function instance performs the processing of the entry 10, the entry 11, and the entry 12, and reads the Metadata packet, and finds that the 0th byte is 8, and the first byte is 13. Therefore, the SF3 service adds the result of the entry 10 and the result of the entry 11 to the Metadata packet, and sends the result to the SF4 service function instance together with the packet;
  • the SF4 service function instance After receiving the packet sent by the SF3 service function instance, the SF4 service function instance reads the Metadata packet and finds that the 0th byte is 8, and the first byte is 13. The SF4 service function instance directly reads the result of the entry 10 and the result of the entry 11 in the metadata, and then performs the search and processing of the entry 13. Then, the packet and the Metadata packet are sent to the SF5 service function instance.
  • the SF5 service function instance After receiving the packet sent by the SF4 service function instance, the SF5 service function instance reads the Metadata packet and finds that the 0th byte is 8, and the first byte is 13. The SF5 service function instance directly reads the result of the entry 10 and the result of the entry 11 in the metadata, and completes the corresponding SF5 process;
  • the packet is sent to the network.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the above-mentioned embodiments and the preferred embodiments solve the problem in the related art that the information exchanged between the nodes is not targeted, so that there is a waste of resources caused by blind exchange, thereby achieving field resources effectively avoiding invalid information exchange. The effect of wasting.

Landscapes

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

Abstract

本发明提供了一种业务节点能力处理方法、装置、业务分类器及业务控制器，其中，该方法包括：确定用于处理数据报文的业务功能链上的业务节点的交换信息集合，其中，该交换信息集合包括业务功能链上业务节点间的能力的交集；将交换信息集合封装在数据报文中，其中，交换信息集合用于业务节点读取已封装在数据报文中的对业务节点间的能力的交集对应的能力处理后获得的处理结果，通过本发明，解决了相关技术中，由于节点间交换信息没有针对性，因而存在盲目交换产生资源浪费的问题，进而达到了有效避免无效信息交换造成的字段资源浪费的效果。

Description

业务节点能力处理方法、装置、业务分类器及业务控制器 技术领域
本发明涉及通信领域，具体而言，涉及一种业务节点能力处理方法、装置、业务分类器及业务控制器。
背景技术
业务功能链(Service Function Chaining，简称为SFC)是目前正在研究和标准化的一种网络技术。自从数据中心网络向Overlay(叠加)网络发展以后，网络边缘成为了虚拟网络与物理网络的分界点，其中网络边缘为服务器(Server)或者ToR，以及可能为网关(Gateway)。然而Overlay技术并没有解决所有问题，数据中心中还有很多中间件(Middleware)，如防火墙/负载均衡器等，这些设备都是基于用户业务来处理的，如果通过隧道而穿越这些设备，显然是不行的。
数据中心的这种部署模型，要求虚拟防火墙/负载均衡器可以在网络中任意部署，也就是与网络拓扑无关。这样新问题就是，如何将流量能够灵活的通过虚拟防火墙/负载均衡器进行处理？于是产生了虚拟防火墙/负载均衡器等新型中间件，这些虚拟防火墙/负载均衡器，部署在网络的边缘，可以由标准服务器来实现。
在相关技术中，把虚拟防火墙/负载均衡器/网关等业务处理功能，称为业务功能(Service Function，简称为SF)，而流量经过一系列的Service Function的处理，形成业务功能链(Service Function Chaining，简称为SFC)即。图1是相关技术中业务功能链的示意图，如图1所示，其中的带箭头的实线与虚线分别代表两条业务功能链。
SFC的框架，目前，现有技术中基本可以分为如下组件：
1.业务叠加(Service Overlay)，即各个网络边缘节点需要通信的Overlay(叠加)技术；
2.通用业务控制平面(Generic Service Control Plane，简称为GSCP)，就是形成Service Function Chaining的控制器；
3.业务分类器(Service Classifier)，即需要进行流识别，然后特定的流，进行特定的Service Function Chaining处理；
4.控制平面元数据(Dataplane Metadata)，这是一大特点，Metadata(元数据)允许Service Classifier和SF之间，SF和SF之间，以及SF和外部***之间，各个边缘业务处理节点，能够互相传递和共享交换信息，达到某种业务处理目的。
5.业务功能路径(service function path，简称为SFP)，图2是相关技术中业务功能路径的示例图，如图2所示，SFP是从业务分类器开始，经过若干业务功能实例，达到目的地的一条业务处理路径。
因此，在相关技术中，将网络设备业务功能和转发分离开来，从而实现了业务功能的独立运算和处理，提升网络设备的转发性能。
另外，在相关的SFC技术中，Dataplane Metadata是一个数据区域，可以存放节点之间的交换信息。因此业务功能链中的业务功能SF之间除了传递报文以外，其各自的交换信息可以放在Dataplane Metadata中，以使得下一节点可以方便获取前一节点的计算结果，避免重复计算。Metadata将和报文一起发送到下一处理单元。图3是相关技术中Dataplane Metadata封装在报文内容示例图，如图3所示，Dataplane Metadata可以封装在报文内部随报文发送；图4是相关技术中Dataplane Metadata作为独立消息示例图，如图4所示，Dataplane Metadata也可以作为独立的消息体和报文并行发送。
例如，分类器->SF1->SF2是一个业务功能路径(service function path，简称为SFP)的组成部分，报文首先通过SF1处理后然后再通过SF2处理。SF1和SF2都需要查找相同的ACL表，因此查找ACL表项的过程将在SF1和SF2上分别被执行一次，这样就造成了SF2重复查找的问题。如果用交换信息放在Metadata中的方式，当SF1查找完ACL后，将查找的结果放在Metadata中并和报文封装在一起发送给SF2；SF2收到该Metadata之后，直接取Metadata中ACL查找结果并使用，避免了重复查找ACL表的过程，因此提高了报文在SFC中转发性能。
然而在相关技术中，SF1并不知道SF2是否需要ACL查表结果，另外，SF1查找的表项并不仅仅ACL一种类型，还可能存在其它多种类型，因而在交换信息时并没有针对性，导致盲目交换产生资源浪费的问题。
因此，在相关技术中，由于节点间交换信息没有针对性，因而存在盲目交换产生资源浪费的问题。
发明内容
本发明提供了一种业务节点能力处理方法、装置、业务分类器及业务控制器，以至少解决相关技术中，由于节点间交换信息没有针对性，因而存在盲目交换产生资源浪费的问题。
根据本发明的一个方面，提供了一种业务节点能力处理方法，包括：确定用于处理数据报文的业务功能链上的业务节点的交换信息集合，其中，所述交换信息集合包括所述业务功能链上所述业务节点间的能力的交集；将所述交换信息集合封装在所述数据报文中，其中，所述交换信息集合用于所述业务节点读取已封装在所述数据报文中的对所述业务节点间的能力的交集对应的能力处理后获得的处理结果。
优选地，确定用于处理所述数据报文的所述业务功能链上的所述业务节点的所述交换信息集合包括：确定所述业务功能链上的各个业务节点的能力；选取至少两个业务节点相同的能力为所述业务节点的能力的交集。
优选地，通过以下方式至少之一，将所述交换信息集合封装在所述数据报文中：采用位图格式的方式，采用队列格式的方式。
根据本发明的另一方面，提供了一种业务节点能力处理方法，包括：接收携带有业务功能链上的业务节点的交换信息集合的数据报文，其中，所述交换信息集合包括所述业务功能链上所述业务节点间的能力的交集；依据所述交换信息集合，读取已封装在所述数据报文中的对所述业务节点间的能力的交集对应的能力处理后获得的处理结果。
优选地，在依据所述交换信息集合，读取已封装在所述数据报文中的对所述业务节点间的能力的交集对应的能力处理后获得的处理结果之后，还包括：确定所述业务节点包括处理结果没有封装在所述数据报文中的中间节点能力，但所述中间节点能力存在于所述交换信息集合中；对所述中间节点能力进行处理获取中间节点能力处理结果；将所述中间节点能力处理结果封装在向下一业务节点转发的数据报文中。
优选地，在依据所述交换信息集合，读取已封装在所述数据报文中的对所述业务节点间的能力的交集对应的能力处理后获得的处理结果之后，还包括：对所述交换信息集合中的能力执行以下操作至少之一：添加、删除、修改。
根据本发明的还一方面，提供了一种业务节点能力处理装置，包括：第一确定模块，设置为确定用于处理数据报文的业务功能链上的业务节点的交换信息集合，其中， 所述交换信息集合包括所述业务功能链上所述业务节点间的能力的交集；第一封装模块，设置为将所述交换信息集合封装在所述数据报文中，其中，所述交换信息集合用于所述业务节点读取已封装在所述数据报文中的对所述业务节点间的能力的交集对应的能力处理后获得的处理结果。
优选地，所述第一确定模块包括：确定单元，设置为确定所述业务功能链上的各个业务节点的能力；选取单元，设置为选取至少两个业务节点相同的能力为所述业务节点的能力的交集。根据本发明的又一方面，提供了一种业务分类器，包括上述任一项所述的装置。
根据本发明的还一方面，提供了一种业务控制器，包括上述任一项所述的装置。
根据本发明的再一方面，提供了一种业务节点能力处理装置，包括：接收模块，设置为接收携带有业务功能链上的业务节点的交换信息集合的数据报文，其中，所述交换信息集合包括所述业务功能链上所述业务节点间的能力的交集；读取模块，设置为依据所述交换信息集合，读取已封装在所述数据报文中的对所述业务节点间的能力的交集对应的能力处理后获得的处理结果。
优选地，该装置还包括：第二确定模块，设置为确定所述业务节点包括处理结果没有封装在所述数据报文中的中间节点能力，但所述中间节点能力存在于所述交换信息集合中；处理模块，设置为对所述中间节点能力进行处理获取中间节点能力处理结果；第二封装模块，设置为将所述中间节点能力处理结果封装在向下一业务节点转发的数据报文中。
优选地，该装置还包括：执行模块，设置为对所述交换信息集合中的能力执行以下操作至少之一：添加、删除、修改。
根据本发明的还又一方面，提供了一种业务节点，包括上述任一项所述的装置。
通过本发明，采用确定用于处理数据报文的业务功能链上的业务节点的交换信息集合，其中，所述交换信息集合包括所述业务功能链上所述业务节点间的能力的交集；将所述交换信息集合封装在所述数据报文中，其中，所述交换信息集合用于所述业务节点读取已封装在所述数据报文中的对所述业务节点间的能力的交集对应的能力处理后获得的处理结果，解决了相关技术中，由于节点间交换信息没有针对性，因而存在盲目交换产生资源浪费的问题，进而达到了有效避免无效信息交换造成的字段资源浪费的效果。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是相关技术中业务功能链的示意图；
图2是相关技术中业务功能路径的示例图；
图3是相关技术中Dataplane Metadata封装在报文内容示例图；
图4是相关技术中Dataplane Metadata作为独立消息示例图；
图5是根据本发明实施例的业务节点能力处理方法一的流程图；
图6是根据本发明实施例的业务节点能力处理方法二的流程图；
图7是根据本发明实施例的业务节点能力处理装置一的结构框图；
图8是根据本发明实施例的业务节点能力处理装置一中确定模块72的优选结构框图；
图9是根据本发明实施例的业务分类器的结构框图；
图10是根据本发明实施例的业务控制器的结构框图；
图11是根据本发明实施例的业务节点能力处理装置二的结构框图；
图12是根据本发明实施例的业务节点能力处理装置二的优选结构框图一；
图13是根据本发明实施例的业务节点能力处理装置二的优选结构框图二；
图14是根据本发明实施例的业务节点的结构框图；
图15是根据本发明实施例的交换信息类型集合封装在Metadata中采用位图格式的示意图；
图16是根据本发明实施例的交换信息类型集合封装在Metadata中采用队列格式的示意图；
图17是根据本发明优选实施例一的基于SFP1的部署场景实施例图；
图18是根据本发明优选实施例二的基于SFP2的部署场景实施例图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
在本实施例中提供了一种业务节点能力处理方法，图5是根据本发明实施例的业务节点能力处理方法一的流程图，如图5所示，该流程包括如下步骤：
步骤S502，确定用于处理数据报文的业务功能链上的业务节点的交换信息集合，其中，该交换信息集合包括业务功能链上业务节点间的能力的交集；
步骤S504，将交换信息集合封装在数据报文中，其中，交换信息集合用于业务节点读取已封装在数据报文中的对业务节点间的能力的交集对应的能力处理后获得的处理结果。
通过上述步骤，将包括业务功能链上业务节点间的能力的交集的交换信息集合封装在数据报文中，使得业务节点能够直接读取已封装在数据报文中的对业务节点间的能力的交集对应的能力处理后获得的处理结果，即将交换信息集合存放在数据报文中，使得业务节点间传递有效的交换信息，解决了相关技术中，由于节点间交换信息没有针对性，因而存在盲目交换产生资源浪费的问题，进而达到了有效避免无效信息交换造成的字段资源浪费的效果。
需要说明的是，该业务节点的能力可以包括多种，例如，可以是对业务节点的表项进行处理的能力，也可以是对表项中某个参数进行处理的能力，还可以是对业务节点针对具体业务进行参数配置的能力，在此不进行具体限定。
在确定用于处理数据报文的业务功能链上的业务节点的交换信息集合时，可以采用多种方式，例如，可以先确定业务功能链上的各个业务节点处理的能力；之后，选取至少两个业务节点相同的能力为业务节点的能力的交集。其中，需要说明的是，在具体选择交集的时候可以依据具有相同能力的业务节点的个数而定，例如，可以是两个业务节点具有相同的能力就可以确定为交集，也可以是三个或三个以上的业务节点具有相同的能力才确定为交集。因具体需求而定。
另外，将用于记录能力的交集的交换信息集合封装在数据报方式也可以采用多种方式，例如，可以通过以下方式至少之一来封装上述数据报文：采用位图格式的方式，采用队列格式的方式。
在本实施例中提供了一种业务节点能力处理方法，图6是根据本发明实施例的业务节点能力处理方法二的流程图，如图6所示，该流程包括如下步骤：
步骤S602，接收携带有业务功能链上的业务节点的交换信息集合的数据报文，其中，该交换信息集合包括业务功能链上业务节点间的能力的交集；
步骤S604，依据交换信息集合，读取已封装在数据报文中的对业务节点间的能力的交集对应的能力处理后获得的处理结果。
通过上述步骤，对于业务节点而言，依据接收到的交换信息集合，读取已封装在数据报文中的对业务节点间的能力的交集对应的能力处理后获得的处理结果，使得业务节点间传递有效的交换信息，解决了相关技术中，由于节点间交换信息没有针对性，因而存在盲目交换产生资源浪费的问题，进而达到了有效避免无效信息交换造成的字段资源浪费的效果。
优选地，在依据交换信息集合，读取已封装在数据报文中的对业务节点间的能力的交集对应的能力处理后获得的处理结果之后，还可以执行以下处理：先判断业务节点是否存在需要自身亲自处理的能力，在判断结果为是的情况下，即确定业务节点包括处理结果没有封装在数据报文中的中间节点能力，但中间节点能力存在于交换信息集合中；对中间节点能力进行处理获取中间节点能力处理结果；将中间节点能力处理结果封装在向下一业务节点转发的数据报文中，通过这样的处理，可以方便后续业务节点对该相同的能力的处理效率，即后续节点只需要从接收到的报文中读取对该能力处理的结果就行。
需要指出的是，在依据交换信息集合，读取已封装在数据报文中的对业务节点间的能力的交集对应的能力处理后获得的处理结果之后，还可以对交换信息集合中的能力执行以下操作至少之一：添加、删除、修改，依据需求灵活变动。
在本实施例中还提供了一种业务节点能力处理装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图7是根据本发明实施例的业务节点能力处理装置一的结构框图，如图7所示，该装置包括：第一确定模块72和第一封装模块74，下面对该装置进行说明。
确定模块72，设置为确定用于处理数据报文的业务功能链上的业务节点的交换信息集合，其中，交换信息集合包括业务功能链上业务节点间的能力的交集；封装模块74，连接至上述确定模块72，设置为将交换信息集合封装在数据报文中，其中，交换信息集合用于业务节点读取已封装在数据报文中的对业务节点间的能力的交集对应的能力处理后获得的处理结果。
图8是根据本发明实施例的业务节点能力处理装置一中第一确定模块72的优选结构框图，如图8所示，该第一确定模块72包括：确定单元82和选取单元84，下面对该第一确定模块72进行说明。
确定单元82，设置为确定业务功能链上的各个业务节点的能力；选取单元84，连接至上述确定单元82，设置为选取至少两个业务节点相同的能力为业务节点的能力的交集。
图9是根据本发明实施例的业务分类器的结构框图，如图9所示，该业务分类器90包括上述任一项的业务节点能力处理装置一92。
图10是根据本发明实施例的业务控制器的结构框图，如图10所示，该业务控制器100包括上述任一项的业务节点能力处理装置一92。
图11是根据本发明实施例的业务节点能力处理装置二的结构框图，如图11所示，该装置包括接收模块112和读取模块114，下面对该装置进行说明。
接收模块112，设置为接收携带有业务功能链上的业务节点的交换信息集合的数据报文，其中，交换信息集合包括业务功能链上业务节点间的能力的交集；读取模块114，连接至上述接收模块112，设置为依据交换信息集合，读取已封装在数据报文中的对业务节点间的能力的交集对应的能力处理后获得的处理结果。
图12是根据本发明实施例的业务节点能力处理装置二的优选结构框图一，如图12所示，该装置除包括图11所示的所有结构外，还包括：第二确定模块122、处理模块124和第二封装模块126，下面对该装置进行说明。
第二确定模块122，连接至上述读取模块114，设置为确定业务节点包括处理结果没有封装在数据报文中的中间节点能力，但中间节点能力存在于交换信息集合中；处理模块124，连接至上述第二确定模块122，设置为对中间节点能力进行处理获取中间节点能力处理结果；第二封装模块126，连接至上述处理模块124，设置为将中间节点能力处理结果封装在向下一业务节点转发的数据报文中。
图13是根据本发明实施例的业务节点能力处理装置二的优选结构框图二，如图13所示，该装置除包括图11所示的所有结构外，还包括：执行模块132，下面对该执行模块132进行说明。
执行模块132，设置为对交换信息集合中的能力执行以下操作至少之一：添加、删除、修改。
图14是根据本发明实施例的业务节点的结构框图，如图14所示，该业务节点140包括上述任一项的数据报文表项处理装置二142。
针对相关技术中，由于节点间交换信息没有针对性，因而存在盲目交换产生资源浪费的问题。需要指出的是，由于业务节点能力的种类很多，在此仅以业务节点对表项的处理能力为例进行说明。其它的能力也可以采用本发明实施例及优选实施方式来实现。例如，如果SF2的处理并不需要进行ACL表的查找，则SF1把ACL查表结果放在metadata里就没有任何意义。此外，SF1查找的表项并不仅仅ACL一种类型，还有QoS表、隧道表、标签表等等多种类型的表项，以及SF1处理后的结果，SF1需要决定将上述哪些表项查找结果以及处理结果放在Metadata内并发送给SF2。如果全部放在metadata中，此时有可能会导致Metadata空间无法满足上述多个表项查找结果的存储要求，并导致信息丢失。
在本实施例中，通过如何通知此处的SF1把什么参数或者什么结果添加到metadata中的处理来实现节点信息交换的有效性。例如，在metadata中存放交换信息类型的方案来解决上述缺陷。该交换信息类型，可以是指节点之间交换的是什么信息，例如，ACL序号为一种交换信息类型，用户ID为一种交换信息类型，DPI处理结果为一种交换信息类型……。
通过在metadata中存放交换信息类型的方法，解决相关技术中，SFP节点之间传递有效信息，避免可能传递一些无效的交换信息而造成Metadata字段空间的浪费的问题。下面对该方法进行说明。
业务分类器classifer接收到外部报文之后，根据该报文的字段信息进行分类，并确定一条业务功能路径(service function path，简称为SFP)；业务分类器或控制器分析业务功能路径上所有的节点，并归纳其所有节点业务处理时，所有表项的交集。其中，该表项的交集，是指在SFP中的所有节点：节点1处理报文时需要查询的若干表项、节点2处理报文时需要查询的若干表项、节点3处理报文时需要查询的若干表项，……节点N处理报文时需要查询的若干表项，然后，选取节点1、2、3……N中任意两个节点处理报文时需要处理的相同表项的集合。
业务分类器或控制器根据该SFP上所有节点表项的交集，归纳出业务功能路径上必需的交换信息类型集合(即上述的交换信息集合)；业务分类器将上述交换信息类型集合封装在Metadata中，继续进行SFC所需要的封装，发送到SFP中下一处理节点。
其中，交换信息类型集合封装可以采用多种方式，例如，图15是根据本发明实施例的交换信息类型集合封装在Metadata中采用位图格式的示意图，如图15所示，交换信息类型集合封装在Metadata中可以采用位图格式，即位图中的每一位代表一种交换信息类型。
又例如，图16是根据本发明实施例的交换信息类型集合封装在Metadata中采用队列格式的示意图，如图16所示，交换信息类型集合封装在Metadata中采用队列格式，即队列中的每一项代表一种交换信息类型。
报文到达下一处理节点后，根据节点的业务特性查找相关的表项，同时解析Metadata中的交换信息类型集合；若该表项所归属的类型在交换信息类型集合中时，则记录下表项的查找结果，并将该结果封装在Metadata中，供后续处理节点使用；若表项所归属的类型不在交换信息类型集合中时，则不将查找表项的结果记录在Metadata中。
报文经过SFP中每一个处理节点进行处理时，节点都可以增加或者删除Metadata中的一个或多个交换信息类型。
通过上述处理，解决了相关技术中SFP节点之间传递有效信息，避免有可能传递一些无效的交换信息而造成Metadata字段空间的浪费的问题。
下面结合优选实施例进行说明。
优选实施例一
图17是根据本发明优选实施例一的基于SFP1(SF1—SF2)的部署场景实施例图，如图17所示，该实施例包括以下处理：
101，网管配置用户经过网关处理时，需要进行SF1和SF2的处理；
102，用户发出一个访问外网的报文；
103，分类器收到该报文后，根据101步骤的配置策略进行分类，并生成SFP1，其中SFP1经过SF1和SF2两个业务功能实例；
104，SF1对报文处理需要进行表项1、表项2、表项3三个表项的处理；SF2对报文的处理需要进行表项1、表项2、表项4三个表项的处理；
105，分类器根据104步骤的分析计算结果，得出整个业务功能链的交换信息类型包括表项1、表项2；
106，分类器分配一个128位位图的字段，并将该位图的第0位和第一位置为1，其他位置为0；其中该位图第0位代表表项1，第1位代表表项2；
107，分类器将上述128位位图的字段封装在报文内，发送到SF1业务功能实例；
108，SF1业务功能实例进行表项1、表项2、表项3处理，并读取上述128位位图的字段，发现第0位和第1位被置为1。因此SF1业务将表项1结果和表项2结果追加放在Metadata内，并发送到SF2业务功能实例；
109，SF2业务功能实例收到SF1业务功能实例发出的报文后，读取上述128位位图的字段，发现第0位和第1位被置为1。SF2业务功能实例直接读取Metadata中的表项1结果和表项2结果，避免了这两者重复查找，提升的防火墙业务功能实例处理效率；
110，报文经过SF1业务功能实例和SF2业务功能实例的处理后，发送到网络中。
优选实施例二
图18是根据本发明优选实施例二的基于SFP2(SF3—SF4—SF5)的部署场景实施例图，如图18所示，该实施例包括以下处理：
201，网管配置用户经过网关处理时，需要进行SF3和SF4和SF5的处理；
202，SF3对报文处理需要进行表项10、表项11、表项12三个表项的处理；SF4对报文的处理需要进行访问表项10、表项11、表项13三个表项的处理；SF5对报文的处理需要进行表项10、表项11二个表项的处理。
203，SFC控制器根据202步骤的分析计算结果，得出整个业务功能链的交换信息类型包括表项10、表项11；
204，SFC控制器下发该用户的SFP2和交换信息类型到分类器；
205，用户发出一个访问外网的报文；
206，分类器收到该报文后，分配两个字节的字段，并将该字段第0个字节设置为8；第1个字节设置为13；字段值为8表示交换信息类型是表项10；字段值为13表示交换信息类型是表项11；分类器根据下一节点的IP地址，将该字段重新封装为新的Metadata报文。
207，分类器将报文和Metadata报文，顺序发送到SF3业务功能实例；
208，SF3业务功能实例进行表项10、表项11、表项12的处理，并读取上述Metadata报文，发现第0个字节为8，第1个字节为13。因此SF3业务将表项10结果和表项11结果追加放在Metadata报文内，并和报文一起发送到SF4业务功能实例；
209，SF4业务功能实例收到SF3业务功能实例发出的报文后，读取上述Metadata报文，发现第0个字节为8，第1个字节为13。SF4业务功能实例直接读取Metadata中的表项10结果和表项11结果，再进行表项13的查找和处理。接着将报文和Metadata报文发送到SF5业务功能实例；
210，SF5业务功能实例收到SF4业务功能实例发出的报文后，读取上述Metadata报文，发现第0个字节为8，第1个字节为13。SF5业务功能实例直接读取Metadata中的表项10结果和表项11结果，并完成相应的SF5处理；
211，报文经过SF3业务功能实例、SF4业务功能实例和SF5业务功能实例的处理后，发送到网络中。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
如上所述，通过上述实施例及优选实施方式，解决了相关技术中，由于节点间交换信息没有针对性，因而存在盲目交换产生资源浪费的问题，进而达到了有效避免无效信息交换造成的字段资源浪费的效果。

Claims (14)

  1. 一种业务节点能力处理方法，包括：
    确定用于处理数据报文的业务功能链上的业务节点的交换信息集合，其中，所述交换信息集合包括所述业务功能链上所述业务节点间的能力的交集；
    将所述交换信息集合封装在所述数据报文中，其中，所述交换信息集合用于所述业务节点读取已封装在所述数据报文中的对所述业务节点间的能力的交集对应的能力处理后获得的处理结果。
  2. 根据权利要求1所述的方法，其中，确定用于处理所述数据报文的所述业务功能链上的所述业务节点的所述交换信息集合包括：
    确定所述业务功能链上的各个业务节点的能力；
    选取至少两个业务节点相同的能力为所述业务节点的能力的交集。
  3. 根据权利要求1或2所述的方法，其中，通过以下方式至少之一，将所述交换信息集合封装在所述数据报文中：
    采用位图格式的方式，采用队列格式的方式。
  4. 一种业务节点能力处理方法，包括：
    接收携带有业务功能链上的业务节点的交换信息集合的数据报文，其中，所述交换信息集合包括所述业务功能链上所述业务节点间的能力的交集；
    依据所述交换信息集合，读取已封装在所述数据报文中的对所述业务节点间的能力的交集对应的能力处理后获得的处理结果。
  5. 根据权利要求4所述的方法，其中，在依据所述交换信息集合，读取已封装在所述数据报文中的对所述业务节点间的能力的交集对应的能力处理后获得的处理结果之后，还包括：
    确定所述业务节点包括处理结果没有封装在所述数据报文中的中间节点能力，但所述中间节点能力存在于所述交换信息集合中；
    对所述中间节点能力进行处理获取中间节点能力处理结果；
    将所述中间节点能力处理结果封装在向下一业务节点转发的数据报文中。
  6. 根据权利要求4所述的方法，其中，在依据所述交换信息集合，读取已封装在所述数据报文中的对所述业务节点间的能力的交集对应的能力处理后获得的处理结果之后，还包括：
    对所述交换信息集合中的能力执行以下操作至少之一：添加、删除、修改。
  7. 一种业务节点能力处理装置，包括：
    第一确定模块，设置为确定用于处理数据报文的业务功能链上的业务节点的交换信息集合，其中，所述交换信息集合包括所述业务功能链上所述业务节点间的能力的交集；
    第一封装模块，设置为将所述交换信息集合封装在所述数据报文中，其中，所述交换信息集合用于所述业务节点读取已封装在所述数据报文中的对所述业务节点间的能力的交集对应的能力处理后获得的处理结果。
  8. 根据权利要求7所述的装置，其中，所述第一确定模块包括：
    确定单元，设置为确定所述业务功能链上的各个业务节点的能力；
    选取单元，设置为选取至少两个业务节点相同的能力为所述业务节点的能力的交集。
  9. 一种业务分类器，包括权利要求7或8所述的装置。
  10. 一种业务控制器，包括权利要求7或8所述的装置。
  11. 一种业务节点能力处理装置，包括：
    接收模块，设置为接收携带有业务功能链上的业务节点的交换信息集合的数据报文，其中，所述交换信息集合包括所述业务功能链上所述业务节点间的能力的交集；
    读取模块，设置为依据所述交换信息集合，读取已封装在所述数据报文中的对所述业务节点间的能力的交集对应的能力处理后获得的处理结果。
  12. 根据权利要求11所述的装置，其中，还包括：
    第二确定模块，设置为确定所述业务节点包括处理结果没有封装在所述数据报文中的中间节点能力，但所述中间节点能力存在于所述交换信息集合中；
    处理模块，设置为对所述中间节点能力进行处理获取中间节点能力处理结果；
    第二封装模块，设置为将所述中间节点能力处理结果封装在向下一业务节点转发的数据报文中。
  13. 根据权利要求11所述的装置，其中，还包括：
    执行模块，设置为对所述交换信息集合中的能力执行以下操作至少之一：添加、删除、修改。
  14. 一种业务节点，包括权利要求11至13中任一项所述的装置。
PCT/CN2014/087355 2014-08-05 2014-09-24 业务节点能力处理方法、装置、业务分类器及业务控制器 WO2015154393A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2017506290A JP6420462B2 (ja) 2014-08-05 2014-09-24 サービスノード能力処理方法、装置、サービス分類器及びサービスコントローラ
EP14888913.2A EP3166273B1 (en) 2014-08-05 2014-09-24 Method and system for processing service node ability
US15/501,938 US10284426B2 (en) 2014-08-05 2014-09-24 Method and apparatus for processing service node ability, service classifier and service controller
KR1020177006089A KR101952187B1 (ko) 2014-08-05 2014-09-24 서비스 노드 능력 처리 방법, 장치, 서비스 분류기 및 서비스 제어기

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410382759.0 2014-08-05
CN201410382759.0A CN105323234B (zh) 2014-08-05 2014-08-05 业务节点能力处理方法、装置、业务分类器及业务控制器

Publications (1)

Publication Number Publication Date
WO2015154393A1 true WO2015154393A1 (zh) 2015-10-15

Family

ID=54287173

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/087355 WO2015154393A1 (zh) 2014-08-05 2014-09-24 业务节点能力处理方法、装置、业务分类器及业务控制器

Country Status (6)

Country Link
US (1) US10284426B2 (zh)
EP (1) EP3166273B1 (zh)
JP (1) JP6420462B2 (zh)
KR (1) KR101952187B1 (zh)
CN (1) CN105323234B (zh)
WO (1) WO2015154393A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106130894B (zh) * 2016-06-03 2019-04-19 上海华为技术有限公司 一种业务功能链的创建方法及***
CN108200207A (zh) * 2018-02-11 2018-06-22 中国联合网络通信集团有限公司 云计算***安全服务的方法和***、安全云管理平台
US20220353348A1 (en) * 2021-04-28 2022-11-03 Arris Enterprises Llc Common-framework controller for multiple device types

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101127713A (zh) * 2007-09-05 2008-02-20 华为技术有限公司 通用流量控制装置及流量控制方法
US20100165985A1 (en) * 2008-12-29 2010-07-01 Cisco Technology, Inc. Service Selection Mechanism In Service Insertion Architecture Data Plane
CN103905447A (zh) * 2014-04-01 2014-07-02 华为技术有限公司 业务链路选择控制方法以及设备
CN103929492A (zh) * 2014-04-28 2014-07-16 华为技术有限公司 业务链负载均衡方法及其装置、***

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4104011B2 (ja) * 2005-03-03 2008-06-18 株式会社エヌ・ティ・ティ・ドコモ トラヒック制御システム、及び、トラヒック制御処理実行方法
US9253274B2 (en) 2007-01-19 2016-02-02 Cisco Technology, Inc. Service insertion architecture
CN101471860B (zh) * 2007-12-27 2011-04-13 华为技术有限公司 一种软交换设备选择呼叫仲裁节点的方法、***和设备
US8396929B2 (en) * 2008-07-02 2013-03-12 Sap Portals Israel Ltd. Method and apparatus for distributed application context aware transaction processing
US9106508B2 (en) * 2012-04-30 2015-08-11 International Business Machines Corporation Providing services to virtual overlay network traffic
CN104883266B (zh) * 2014-02-28 2018-10-12 新华三技术有限公司 网络配置访问方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101127713A (zh) * 2007-09-05 2008-02-20 华为技术有限公司 通用流量控制装置及流量控制方法
US20100165985A1 (en) * 2008-12-29 2010-07-01 Cisco Technology, Inc. Service Selection Mechanism In Service Insertion Architecture Data Plane
CN103905447A (zh) * 2014-04-01 2014-07-02 华为技术有限公司 业务链路选择控制方法以及设备
CN103929492A (zh) * 2014-04-28 2014-07-16 华为技术有限公司 业务链负载均衡方法及其装置、***

Also Published As

Publication number Publication date
JP2017523721A (ja) 2017-08-17
KR101952187B1 (ko) 2019-02-26
US20170230246A1 (en) 2017-08-10
CN105323234A (zh) 2016-02-10
EP3166273A1 (en) 2017-05-10
EP3166273A4 (en) 2017-06-28
US10284426B2 (en) 2019-05-07
JP6420462B2 (ja) 2018-11-07
CN105323234B (zh) 2019-03-15
EP3166273B1 (en) 2019-07-17
KR20170040325A (ko) 2017-04-12

Similar Documents

Publication Publication Date Title
US11792046B2 (en) Method for generating forwarding information, controller, and service forwarding entity
US10122629B2 (en) Systems and methods for externalizing network functions via packet trunking
TWI744359B (zh) 一種資料傳輸的方法及網路設備
EP2676411B1 (en) Method and system for classification and management of inter-blade network traffic in a blade server
US10439931B2 (en) Data packet processing method, service node, and delivery node
CN106878194B (zh) 一种报文处理方法和装置
WO2016192686A1 (zh) 数据报文转发
JP5993817B2 (ja) キャリア網における経路制御システム及び方法
US11102133B2 (en) Service packet processing method, apparatus, and system
CN105991387A (zh) 虚拟扩展局域网的报文传输方法和装置
WO2022001835A1 (zh) 发送报文的方法、装置、网络设备、***及存储介质
CN111801911B (zh) 业务功能链拥塞跟踪
WO2018036254A1 (zh) 报文转发方法及装置
WO2015184771A1 (zh) 一种业务功能链操作、管理和维护方法及节点设备
CN108353022A (zh) 一种数据报文的处理方法、装置及***
JP2018518925A (ja) パケット転送
WO2015154393A1 (zh) 业务节点能力处理方法、装置、业务分类器及业务控制器
US10177935B2 (en) Data transfer system, data transfer server, data transfer method, and program recording medium
WO2024104007A1 (zh) 报文发送方法、装置、存储介质及电子装置
WO2016115913A1 (zh) 一种数据处理方法及装置
CN105874755A (zh) 数据包转发处理方法及装置
CN116264514A (zh) 使用基于网络设备的区域将安全策略应用于网络业务
CN115842876A (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: 14888913

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2014888913

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2014888913

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2017506290

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20177006089

Country of ref document: KR

Kind code of ref document: A