[go: up one dir, main page]

WO2014059873A1 - 链路聚合组中流量路径的协商方法及装置 - Google Patents

链路聚合组中流量路径的协商方法及装置 Download PDF

Info

Publication number
WO2014059873A1
WO2014059873A1 PCT/CN2013/084522 CN2013084522W WO2014059873A1 WO 2014059873 A1 WO2014059873 A1 WO 2014059873A1 CN 2013084522 W CN2013084522 W CN 2013084522W WO 2014059873 A1 WO2014059873 A1 WO 2014059873A1
Authority
WO
WIPO (PCT)
Prior art keywords
aggregation
port
services
sessions
aggregation port
Prior art date
Application number
PCT/CN2013/084522
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 US14/437,051 priority Critical patent/US9736060B2/en
Priority to EP13847072.9A priority patent/EP2911353B1/en
Publication of WO2014059873A1 publication Critical patent/WO2014059873A1/zh

Links

Classifications

    • 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/24—Multipath
    • H04L45/245—Link aggregation, e.g. trunking
    • 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/14—Session management
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and an apparatus for negotiating a traffic path in a link aggregation group.
  • BACKGROUND With the rapid development of broadband services, more and more interconnections between networks and networks are used, and more services are carried. Within the network, depending on the technology used, there are multiple ways to protect the link and the nodes on it. As the demand for protection of traffic becomes stronger and stronger, and the requirements are higher and higher, operators have also raised the need for protection of network interconnection.
  • the protection can be implemented by using port aggregation.
  • the common method can be port aggregation or loop protection.
  • Link aggregation Currently, the common standard supports port aggregation on a node, so it can only be used for link protection.
  • FIG. 1 is a schematic diagram of a network interconnection node connection according to the related art. As shown in FIG.
  • LAG link aggregation group
  • two endpoints A and B of a link aggregation group have two nodes, and two nodes of the LAG endpoint A are system 1.
  • System 2 the two nodes of LAG Endpoint B are System 3 and System 4.
  • the multiple links of the four systems are aggregated to form an aggregation group LAG.
  • Double protection of links and nodes can be achieved.
  • System 1 and system 2 in LAG endpoint A communicate via an internal link connection
  • system 3 and system 4 of LAG endpoint B also communicate via an internal link.
  • DRNI protects and load-sharing the packet service.
  • traffic of the same service cannot be transmitted on the same aggregation link.
  • the present invention provides a method and apparatus for negotiating traffic paths in a link aggregation group to solve at least the above problems.
  • a method for negotiating a traffic path in a link aggregation group includes: an aggregation port obtaining indication information, where the indication information includes one or more groups that are required to be carried by the aggregation port.
  • each group of services or sessions includes one or more services or sessions;
  • the aggregation port determines multiple groups of services or sessions that are required to be carried by the port, and/or determines the currently carried service or session;
  • the aggregation group endpoint where the aggregation port is located distributes traffic according to the service or session currently carried by each aggregation port.
  • the currently carried service or session is a group of services or sessions with the highest priority among the multiple groups of services or sessions.
  • each of the foregoing services or sessions corresponds to an aggregation port sequence
  • the aggregation port sequence is composed of an aggregation port arrangement in the aggregation group endpoint.
  • the multiple groups of services or sessions that are required to be carried by the aggregation port are determined according to the sequence of the aggregation port corresponding to each of the foregoing services or sessions in the foregoing aggregation group endpoint.
  • the multiple aggregation ports in the foregoing aggregation port sequence are sorted according to a preference level that carries the service or session.
  • the multiple groups of services or sessions that are required to be carried by the aggregation port are formed according to services or sessions corresponding to the aggregation ports of different priorities in the aggregation port sequence.
  • the aggregation group endpoint to which the aggregation port belongs is configured to modify or set the multiple groups of services or sessions that are required to be carried by the aggregation port according to a predetermined policy, and/or determine the currently carried service or session.
  • the foregoing aggregation port determines that the multiple groups of services or sessions to be carried by the local port include: the foregoing aggregation group endpoint to which the aggregation port belongs to modify the multiple groups of services or sessions that are required to be carried by the aggregation port according to the foregoing predetermined policy;
  • the port determines the multiple groups of services or sessions to be carried by the port according to the foregoing multiple groups of services or sessions modified by the foregoing aggregation group endpoint.
  • the foregoing aggregation group endpoints modify the multiple groups of services or sessions to be carried by the aggregation port according to the foregoing predetermined policy, including: the foregoing multiple groups of services or sessions currently carried by the aggregation group endpoint to which the aggregation port belongs If the service or the session in the specified information is inconsistent, the priority of the aggregation group is compared with the priority of the aggregation group to which the aggregation port of the peer is located. Or the session; or the aggregation group to which the aggregation port belongs, according to the master/slave relationship, whether to modify the multiple groups of services or sessions currently carried by the aggregation port according to the foregoing indication information.
  • the aggregation group to which the aggregation port belongs is based on its own priority relationship; or, according to its own active/standby relationship, whether to modify the multiple groups of services or sessions currently carried by the aggregation port according to the foregoing indication information: If the priority of the aggregation group is lower than that of the aggregation group to which the aggregation port of the peer belongs, or if the endpoint of the aggregation group belongs to the aggregation group endpoint to which the aggregation port of the peer belongs, the endpoint of the aggregation group modifies the current aggregation port according to the preceding information.
  • the aggregation group endpoint to which the aggregation port belongs is configured to set the multiple groups of services or sessions to be carried by the aggregation port according to the foregoing predetermined policy: if the aggregation port does not form a service or session currently carried by the aggregation port, the aggregation is performed.
  • the aggregation group endpoint to which the port belongs sets the multiple groups of services or sessions currently carried by the aggregation port according to the foregoing indication information.
  • the method further includes: when the aggregation link corresponding to the aggregation port is faulty or unavailable, or is detached from the aggregation link group, the aggregation group endpoint where the aggregation port is located is currently carried on the aggregation port.
  • the aggregation port corresponding to the foregoing aggregation link is blocked in the foregoing aggregation port sequence corresponding to the service or the session.
  • the method further includes: when the aggregation link corresponding to the one or more aggregation ports is restored or rejoined to the aggregation link group, the aggregation group endpoint determines the protection mode: if the protection mode is non-inversion In the mode, the aggregation port corresponding to the foregoing aggregation link is added to the foregoing aggregation port sequence.
  • the method further includes: when the aggregation link corresponding to the one or more aggregation ports is restored or rejoined to the aggregation link group, the aggregation group endpoint determines a protection mode; if the protection mode is a reverse mode And recovering the aggregation port corresponding to the foregoing aggregation link in the foregoing aggregation port sequence.
  • the protection mode is the reverse mode
  • the change of the aggregation port sequence triggers a change of the currently carried service or session on the aggregation port.
  • the indication information may be a type length value TLV field.
  • the indication information may be carried in a link aggregation control protocol LACP packet.
  • a device for negotiating a traffic path in a link aggregation group includes: an aggregation port, and an aggregation group endpoint where the aggregation port is located, where the aggregation port includes: The module is configured to obtain the indication information, where the foregoing indication information includes multiple groups of services or sessions that are required to be carried by the foregoing aggregation port, where each group of services or sessions includes one or more services or sessions; Determining the multiple groups of services or sessions to be carried by the foregoing aggregation port, and/or determining the currently carried service or session; the foregoing aggregation group endpoints include: a distribution module, configured to perform services or sessions currently carried according to each of the foregoing aggregation ports Distribute traffic.
  • the currently carried service or session is a group of services or sessions with the highest priority among the multiple groups of services or sessions.
  • each of the foregoing services or sessions corresponds to an aggregation port sequence, and the aggregation port sequence is composed of an aggregation port arrangement in the aggregation group endpoint.
  • the multiple groups of services or sessions that are required to be carried by the aggregation port are determined according to the sequence of the aggregation port corresponding to each of the foregoing services or sessions in the foregoing aggregation group endpoint.
  • the multiple aggregation ports in the foregoing aggregation port sequence are sorted according to a preference level that carries the service or session.
  • the multiple groups of services or sessions that are required to be carried by the aggregation port are formed according to services or sessions corresponding to the aggregation ports of different priorities in the aggregation port sequence.
  • the aggregation group endpoint to which the aggregation port belongs is configured to modify or set the multiple groups of services or sessions that are required to be carried by the aggregation port according to a predetermined policy, and/or determine the currently carried service or session.
  • the foregoing aggregation group endpoint further includes: a modification module, configured to modify the multiple groups of services or sessions that are required to be carried by the aggregation port according to the foregoing predetermined policy;
  • the determining module includes: a determining unit, configured to be modified according to the modifying module The foregoing multiple groups of services or sessions determine multiple groups of services or sessions that are required to be carried by the port.
  • the modifying module includes: a modification determining unit, configured to: when the multiple groups of services or sessions currently carried by the aggregation port are inconsistent with the services or sessions in the indication information, by using the priority of the aggregation group endpoint The priority of the aggregation group to which the aggregation port of the peer end belongs is compared with the priority of the aggregation group to determine whether the multi-group service or the session currently carried by the aggregation port needs to be modified; or the modification judgment unit is configured to determine whether the indication is required according to the active/standby relationship. The information is modified by the foregoing multiple groups of services or sessions currently carried by the aggregation port.
  • the modifying module further includes: a first modifying unit, configured to: the aggregation group end point has a lower priority than the aggregation group end to which the aggregation port of the peer end belongs, or the aggregation group end point belongs to the aggregation port of the peer end.
  • a first modifying unit configured to: the aggregation group end point has a lower priority than the aggregation group end to which the aggregation port of the peer end belongs, or the aggregation group end point belongs to the aggregation port of the peer end.
  • the modifying module further includes: a second modifying unit, configured to: if the aggregation port does not form a service or a session currently carried by the aggregation port, set the multiple groups of services currently carried by the aggregation port according to the indication information Or a conversation.
  • the foregoing aggregation group endpoint further includes: a masking module, configured to: when the aggregation link corresponding to the aggregation port is faulty or unavailable, or if the aggregation link group is detached, the current aggregation port is currently carried The aggregation terminal ⁇ corresponding to the foregoing aggregation link is masked in the foregoing aggregation port sequence corresponding to the service or the session.
  • the foregoing aggregation group endpoint further includes: a first mode determining module, configured to determine a protection mode when the aggregation link corresponding to the one or more aggregation ports is restored or rejoined into the aggregation link group;
  • the adding module is configured to add the aggregation port corresponding to the aggregated link to the aggregation port sequence when the protection mode is the non-inversion mode.
  • the foregoing aggregation group endpoint further includes: a second mode determining module, configured to determine a protection mode when the aggregation link corresponding to the one or more aggregation ports is restored or rejoined into the aggregation link group;
  • the recovery module is configured to restore the aggregation port corresponding to the aggregation link in the aggregation port sequence when the protection mode is the reverse mode.
  • the protection mode is the reverse mode
  • the change of the aggregation port sequence triggers a change of the currently carried service or session on the aggregation port.
  • the aggregation port obtains indication information, where the indication information includes multiple groups of services or sessions that are required to be carried by the aggregation port, and each group of services or sessions includes one or more services or sessions, and the foregoing aggregation port is determined.
  • the aggregation group endpoints of the aggregation ports are distributed according to the services or sessions currently carried by the aggregation ports.
  • FIG. 1 is a schematic diagram of a network interconnection node connection according to the related art
  • FIG. 2 is a flowchart of a method for negotiating a traffic path in a link aggregation group according to an embodiment of the present invention
  • FIG. 3 is a diagram according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a fault according to an embodiment of the present invention.
  • FIG. 5 is a structural block diagram of a device for negotiating a traffic path in a link aggregation group according to an embodiment of the present invention.
  • BEST MODE FOR CARRYING OUT THE INVENTION the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.
  • the embodiment of the invention provides a method and a device for negotiating a traffic path in a link aggregation group, which are described in detail below through an embodiment. This embodiment provides a method for negotiating a traffic path in a link aggregation group.
  • Step S202 the aggregation port obtains the indication information, where the indication information includes one or more groups of services or sessions that are required to be carried by the aggregation port, where each group of services or sessions includes One or more services or sessions;
  • Step S204 the aggregation port determines the multiple groups of services or sessions that the port needs to carry, and/or determines the currently carried service or session;
  • Step S206 the aggregation group endpoint where the aggregation port is located The traffic or the session currently carried by each of the foregoing aggregation ports performs traffic distribution.
  • the aggregation port obtains the indication information, where the indication information includes multiple groups of services or sessions that are required to be carried by the aggregation port, and each group of services or sessions includes one or more services or sessions, and the aggregation port determines the port. Multiple sets of services or sessions to be carried, and/or, determining the currently carried services or sessions, The aggregation group endpoints in which the ports are located are distributed according to the services or sessions currently carried by the foregoing aggregation ports, which solves the problem that the same service or session cannot perform the bidirectional same path transmission in the related art, and the protection on the interconnection interface is realized. .
  • the currently carried service or session is generally a group of services or sessions with the highest priority among multiple groups of services or sessions.
  • this embodiment provides a preferred implementation manner, that is, two ends or one end of the aggregation group has its own service allocation port table, and multiple services or sessions correspond to multiple Aggregate links, which are ranked according to the priority of the service priority distribution.
  • the foregoing indication information may be, but not limited to, a type length value TLV field.
  • the foregoing indication information may be carried in the link aggregation control protocol LACP packet.
  • This embodiment provides a preferred implementation manner for implementing a method for negotiating a traffic path in a link aggregation group provided in this embodiment.
  • the specific steps are as follows: 1.
  • the two ends or one end of the aggregation group has its own service distribution port table, and multiple aggregation links corresponding to different services or sessions.
  • the priority of the multiple aggregation links is preferentially distributed according to the service. Level arrangement.
  • this embodiment provides a preferred implementation manner, that is, in an aggregation group endpoint to which an aggregation port belongs, each service or session corresponds to an aggregation port sequence, and the aggregation port sequence is arranged by an aggregation port in the aggregation group endpoint. Composition.
  • the plurality of aggregate ports in the aggregated port sequence are sorted according to a preference level for carrying the service or session.
  • the aggregated port sequence can be embodied in the form of a service allocation port table.
  • the service bearer priority sequence table is obtained according to each priority port in the service allocation port table.
  • the embodiment provides a preferred implementation manner, that is, determining, according to each of the foregoing service or session, an aggregation port sequence in the aggregation group endpoint, the multiple groups of services or sessions that are required to be carried by the aggregation port.
  • the multiple groups of services or sessions to be carried by the aggregation port are formed according to services or sessions corresponding to the aggregation ports of different priorities in the aggregation port sequence.
  • the correspondence between the aggregation port and the multiple groups of services or sessions that it needs to carry can be embodied in the form of a service bearer priority sequence table.
  • a new service negotiation TLV field is defined.
  • the service negotiation TLV carries the service carried by each aggregation port according to different priorities, that is, the service bearer priority sequence table.
  • the aggregation port will generate a peer service allocation port table after receiving the service negotiation TLV. If the local end also has a service bearer table, it compares with its own service allocation port.
  • both ends are according to such a
  • the service allocates a port table to distribute traffic, so that each aggregated link of the aggregation group carries the same service/session traffic, ensuring that the traffic of the same service can be in the same path. If the local end does not have a service allocation port table, the local service allocation port table is constructed according to the received service negotiation TLV.
  • the embodiment provides a preferred implementation manner, that is, the aggregation group endpoint to which the aggregation port belongs changes or sets the multiple groups of services or sessions that are required to be carried by the aggregation port according to a predetermined policy, and/or determines the currently carried Business or conversation.
  • the aggregation port determines the number of services or sessions that the port needs to carry: the aggregation group to which the aggregation port belongs changes the multiple groups of services or sessions to be carried by the aggregation port according to the foregoing predetermined policy; Multiple groups of services or sessions determine the multiple groups of services or sessions that this port needs to carry.
  • the aggregation group endpoints modify the aggregation group to carry the multiple groups of services or sessions according to the predetermined policy.
  • the aggregation group endpoints to which the aggregation port belongs are in the case that the services or sessions in the group are inconsistent with the services or sessions in the indication information. If the priority of the endpoint of the aggregation group is compared with the priority of the aggregation group to which the aggregation port of the peer end belongs, determine whether the service group or session to be carried by the aggregation port needs to be modified.
  • the master/slave relationship determines whether the multiple groups of services or sessions currently carried by the aggregation port need to be modified according to the preceding information.
  • the aggregation group endpoint to which the aggregation port belongs is based on its own priority relationship. Whether it is required to modify the multiple groups of services or sessions currently carried by the aggregation port according to the indication information. If the aggregation group endpoint to which the peer aggregation port belongs, or the aggregation group endpoint belongs to the aggregation group endpoint to which the aggregation port belongs to the peer end, the aggregation group endpoint modifies the multiple groups of services or sessions currently carried by the aggregation port according to the indication information. The aggregation group endpoint to which the aggregation port belongs sets the multiple groups of services or sessions to be carried by the aggregation port according to the predetermined policy.
  • the aggregation group endpoint to which the aggregation port belongs is set according to the indication information.
  • the service allocation port table changes at both ends of the aggregation group are triggered, and the service allocation port table is deleted. The unavailable aggregate port.
  • the aggregated link is restored or the aggregated link is rejoined into the aggregation group, if the protection is in the reverse mode, the location of the aggregated link in the original service allocation port table is restored.
  • the change of the first priority port in the service allocation port table will trigger the aggregator to distribute the change of traffic on the aggregation port, thereby restoring the The service on the aggregated link of the original fault. If it is a non-revertive mode, the original failed aggregated link is only added to the port sequence of the current service allocation port table. Based on the foregoing process, the foregoing embodiment provides a preferred implementation manner.
  • the foregoing method provided by the embodiment further includes: when the aggregation link corresponding to the aggregation port is faulty or unavailable, or is detached from the aggregation link group, The aggregation group endpoint where the aggregation port is located shields the aggregation port corresponding to the aggregation link in the aggregation port sequence corresponding to the service or session currently carried by the aggregation port.
  • the aggregation group endpoint determines the protection mode: If the protection mode is non-reverse mode, the aggregation port corresponding to the aggregation link is used. Add to the aggregate port sequence.
  • FIG. 3 is a schematic diagram of networking according to an embodiment of the present invention. As shown in FIG.
  • endpoint 1 is composed of node A and node B
  • endpoint 2 is composed of node C
  • Node D is composed.
  • Endpoint 1 has port a, port b, port c, and port d participating in aggregation.
  • Endpoint 2 has port x, port y, port z, and port w participating in aggregation.
  • Port a and port w are interconnected as aggregated link 1;
  • port b and port y are interconnected as aggregated link 2;
  • port c and port X are interconnected as aggregated link 3;
  • port d and port z are interconnected as aggregated link 4.
  • the aggregation link 1, the aggregation link 2, the aggregation link 3, and the aggregation link 4 form an aggregation group.
  • the node A and the node B in the endpoint 1 are negotiated to obtain a service distribution port table, and the service allocation port table of the endpoint 1 is as shown in Table 1.
  • Table 1 Table 1
  • Each entry in the service assignment port table can be identified by a set of variable identifiers: Aggregator_Vlan_XXXXXX_Oper_Porto, wherein the first sequence of the port sequence is the first priority port of the corresponding service, and the second service corresponding to the second service. Priority port, and so on.
  • each system of the aggregation group has a system management Aggregator_Vlan_XXXXXX_Admin_Port, which is used to save the original configuration and system settings of the local end.
  • the initial value of Aggregator_Vlan_XXXXXX_Oper_Port is derived from Aggregator_Vlan_XXXXXX_Admin_Port .
  • Aggregator_Vlan_XXXXXX_Oper_Port resolves, the aggregator distributes different traffic to different aggregation ports.
  • each aggregation port obtains its own service bearer priority sequence table, and the service bearer priority sequence table is obtained according to each priority port in the service allocation port table.
  • the table is identified by a series of Port_Oper_Vlan_List_X variables, where X identifies the priority level.
  • the aggregation port a and the aggregation port w are used as an example.
  • Table 3 shows the service bearer priority sequence table of the aggregation port a. table 3
  • Table 4 shows the service bearer priority sequence table of the aggregated port w.
  • the service negotiation TLV field in the LACP protocol packet carries the service bearer priority sequence table information corresponding to the aggregation port that sends the packet.
  • the format of the service negotiation TLV is shown in Table 5. 3 ⁇ 4 5
  • Service_List_X is also a subtype TLV, and each Service_List_X contains Port_Oper_Vlan_List_X information.
  • the format of the Service_List_X TLV is shown in Table 6. Table 6
  • Sub-TLV Type Service List
  • the LACP packets sent from port a and port w carry the service negotiation TLV.
  • the format of the TLV carried in the LACP packets sent by port a is shown in Table 7. 3 ⁇ 4 7
  • Sub-TLV Type Service List
  • Table 8 shows the format of the TLV carried in the LACP packets sent by the End TLV port. 3 ⁇ 4 8
  • Sub-TLV Type Service List
  • the port A and the port w at both ends of the end of the TLV are mutually negotiated with the TLV, and a service bearer priority sequence table is generated according to the received service negotiation TLV, and the service bearer priority sequence table is also The end of the service bearer priority sequence table is compared.
  • the initial bearer services of each port are different, and then according to a specific policy, such as system priority (System Priority), or system ID (System ID), or aggregation group
  • system priority System Priority
  • System ID System ID
  • aggregation group The master-slave relationship of the terminal, here assumes that the system priority of endpoint 1 is higher than the system priority of endpoint 2, or endpoint 1 is the master (Master), and endpoint 2 is the slave (Slave), so the port w of endpoint 2 Compliance with the service carried by port a of endpoint 1, modifying its own service bearer priority sequence table, after LACP Negotiation, the service bearer priority sequence table of port w is modified as shown in Table 3, and is consistent with the service bearer priority sequence table of port a.
  • the information in the service negotiation TLV in the LACP packet sent by port w is as shown in Table 7, and the service negotiation TLV sent by port a is the same. If the service negotiation TLV information in the LACP packet received by the aggregation port is the same as the content of the service bearer table, the two services are in agreement. The service starts to be transmitted from the aggregation link. State), two-way traffic of the same service can guarantee two-way same path. If one of the aggregation links is faulty or is isolated from the aggregation group, assuming that the aggregation link 1 is faulty, the port change in the service port allocation table will be triggered. FIG.
  • FIG. 4 is a schematic diagram of the fault according to the embodiment of the present invention, as shown in FIG.
  • the aggregate port is set to unavailable in the service port assignment table.
  • the service bearer priority sequence table of each aggregation port is triggered, and the data traffic is re-distributed according to the newly received service bearer priority sequence table.
  • the aggregated link is restored, the restored aggregated port is reset and available in the service port allocation table, and then the protection mode needs to be determined first. If the protection mode of the protection system is the reverse mode, the service port allocation table is modified to trigger the service bearer priority sequence table of each aggregation port, and the service bearer priority sequence table is restored to the content before the fault, thereby restoring the traffic.
  • the aggregate link is the aggregate link.
  • the second embodiment is similar to the first embodiment except that the endpoint 1 and the endpoint 2 in the first embodiment have their own service port allocation table, and generate a service bearer table of each aggregation port, so according to the service bearer table.
  • the service negotiation TLV is sent, and the two ends are agreed by the negotiation at both ends. In this embodiment, only one end is configured with its own service port allocation table. It is assumed here that Endpoint 1 has its own service port allocation table, as shown in Table 1 above.
  • each aggregation port of the endpoint 1 generates its own service bearer priority sequence table according to the service port allocation table.
  • the service bearer priority sequence table of the port a is the LACP packet sent from the port a.
  • the service negotiation TLV carried in is as shown in Table 5 above.
  • the port w of the endpoint 2 connected to the port a after receiving the service negotiation TLV sent by the port a, does not have a service bearer priority sequence table, so it constructs its own according to the received peer service negotiation TLV.
  • the service bearer table of the port carries the priority sequence table.
  • the service bearer priority sequence table of port w is consistent with the service bearer priority sequence table of port a.
  • the endpoint 2 constructs its own service port assignment according to the service bearer priority sequence table of each port. table. Once each port has built its own service bearer priority sequence table, it will also begin to pass the information of its own service bearer table through the service negotiation TLV, so that both ends can always maintain the consistency of service transmission and maintain the same direction with the service. path.
  • the third embodiment differs from the first embodiment and the second embodiment in that the embodiment is a stream identifier, which is identified by a stream id.
  • the negotiation involved in the embodiment of the present invention may be not only the negotiation of the service in the packet, such as the customer virtual local area network identifier (Custom VL AN ID, C-VID for short) or the service virtual local area network identifier (Service VLAN ID, S-VID for short).
  • the backbone VLAN ID (B-VID) and the Backbone Service Instance Identifier (I-SID) are also negotiated.
  • the flow identifier is a definition of a type of data flow.
  • the data flow may be a media access control (MAC), the source MAC is the same set of MAC pairs, and may be a destination network protocol (Internet). Protocol, referred to as IP), source IP is the same set of IP pairs, can also have the same service identifier, and so on.
  • the flow identifiers are defined as shown in Table 9. Table 9
  • Each entry of the corresponding table of the aggregated port and the flow can be identified by a set of variables:
  • Aggregator_Stream_XXXXXX_Oper_Port Among the port sequences, the first priority port corresponding to the data stream, the second priority port corresponding to the second data stream, and so on.
  • a system management Aggregator_Stream_XXXXXX_Admin_Port which is used to save the original configuration and system settings of the local end.
  • the initial value of Aggregator_Stream_XXXXXX_Oper_Port is derived from Aggregator_Stream_XXXXXX_Admin_Port .
  • Aggregator_Stream_XXXXXX_Oper_Port resolves, the aggregator distributes different traffic to different aggregation ports.
  • each aggregation port obtains its own data flow bearer priority sequence table, and the data flow bearer priority sequence table is obtained according to each priority port in the data flow allocation port table.
  • the table is identified by a series of Port_Oper_Stream_List_X variables, where X identifies the priority level.
  • the aggregation port a and the aggregation port w are taken as an example.
  • Table 12 shows the data flow bearing priority sequence table of the aggregation port a. Table 12
  • Table 13 shows the data flow bearer priority sequence table for the aggregated port w.
  • the data flow negotiation TLV field in the LACP protocol packet carries the priority sequence table information of the data flow corresponding to the aggregation port that sends the packet.
  • the format of the data stream negotiation TLV is shown in Table 14. 3 ⁇ 4 M
  • Sub-TLV Type Stream_ID List
  • the LACP protocol packets sent from port a and port w carry the data stream negotiation TLV.
  • the format of the TLV carried in the LACP protocol packets sent by port a is shown in Table 16. Table 16
  • Sub-TLV Type Stream_ID List
  • Table 17 shows the format of the TLV carried in the LACP packets sent by the End TLV port w.
  • Sub-TLV Type Stream_ID List
  • the port A and the port w at both ends of the aggregation link negotiate the TLV, and generate a peer data flow bearer priority sequence table according to the received data stream negotiation TLV, and carry the own data stream bearer priority sequence table.
  • the data stream bearer priority sequence table is also compared on the end. As can be seen from Tables 7 and 8 above, the initial bearer traffic of each port is different, and then according to a specific policy, for example, according to the system priority, it is assumed that the system priority of endpoint 1 is higher than the endpoint. The system priority of 2, so port w follows the traffic carried by port a, and modifies its own data stream bearer priority sequence table. After LACP negotiation, the data stream bearer priority sequence table of port w is modified to Table 12.
  • the information in the data stream negotiation TLV in the LACP packet sent by the port w is as shown in Table 16 above, and the data stream sent by the port a is negotiated with the TLV.
  • the data flow negotiation TLV information in the LACP packet received by the aggregation port is the same as the data flow table of the data flow, the two devices agree that the specific data traffic starts to be transmitted from the aggregation link.
  • the state of the aggregator enters the distributing state.
  • the two-way traffic of the same session can guarantee the bidirectional same path.
  • the operation process is similar to that in the first embodiment except that the service identifier is changed to the flow identifier.
  • the flow identifier is used to distribute the packet and the negotiation with the same path, which can be used to identify the traffic of the same session, reduce the granularity of identifying different traffic, and enhance the load balancing of the aggregation group. More even hooks.
  • this embodiment provides a device for negotiating the traffic path in the link aggregation group, which is used to implement the foregoing embodiment.
  • FIG. 5 is a structural block diagram of a device for negotiating a traffic path in a link aggregation group according to an embodiment of the present invention.
  • the device includes: an aggregation port 10, and an aggregation group endpoint 20 where the aggregation port is located.
  • FIG. 5 shows the relationship between the two in the aggregation group end point 20, and FIG. 5 is only a schematic illustration. The relationship between the two is actually that the aggregation port 10 is subordinate to the aggregation group endpoint 20.
  • the aggregation port 10 includes: an indication information obtaining module 12, configured to acquire indication information, where the indication information includes multiple groups of services or sessions that are required to be carried by the aggregation port, where each group of services or sessions includes one Or a plurality of services or sessions; determining module 14, connected to the indication information obtaining module 12, And determining, by the distribution module 22, that the aggregation port 22 is currently carried according to each of the foregoing aggregation ports, and is configured to determine a service or a session that is required to be carried by the aggregation port.
  • the distribution of traffic for a business or session configured to acquire indication information, where the indication information includes multiple groups of services or sessions that are required to be carried by the aggregation port, where each group of services or sessions includes one Or a plurality of services or sessions.
  • the aggregation port obtains the indication information, where the indication information includes multiple groups of services or sessions that are required to be carried by the aggregation port, and each group of services or sessions includes one or more services or sessions, and the aggregation port determines the port.
  • the multiple groups of services or sessions to be carried, and/or the current services or sessions are determined.
  • the aggregation group endpoints in which the aggregation ports are located are distributed according to the services or sessions currently carried by the aggregation ports. In the technology, the problem that the service or the session cannot be transmitted in the bidirectional path is realized, and the protection on the interconnection interface is realized.
  • the currently carried service or session is a group of services or sessions with the highest priority among the multiple groups of services or sessions.
  • each of the foregoing services or sessions corresponds to an aggregation port sequence
  • the aggregation port sequence is formed by arranging aggregation ports in the aggregation group endpoints. Determining, according to the foregoing one of the foregoing service or the session, an aggregation port sequence, the foregoing multiple groups of services or sessions that are required to be carried by the aggregation port.
  • the plurality of aggregate ports in the aggregated port sequence are sorted according to a preference level for carrying the service or session.
  • the multiple groups of services or sessions to be carried by the aggregation port are formed according to services or sessions corresponding to the aggregation ports of different priorities in the aggregation port sequence.
  • the aggregation group endpoint to which the aggregation port belongs may modify or set the multiple groups of services or sessions that are required to be carried by the aggregation port according to a predetermined policy, and/or determine the currently carried service or session.
  • the embodiment provides a preferred implementation manner, that is, the aggregation group endpoint further includes: a modification module, configured to be configured according to the foregoing The policy is modified to modify the foregoing multiple groups of services or sessions that are required to be carried by the foregoing aggregation port.
  • the determining module includes: a determining unit, configured to determine, according to the multiple groups of services or sessions modified by the modifying module, Conversation.
  • the modifying module includes: a modification determining unit, configured to: if the multiple groups of services or sessions currently carried by the aggregation port are inconsistent with services or sessions in the indication information, The comparison between the priority of the aggregation group endpoint and the priority of the aggregation group endpoint to which the aggregation port of the peer end belongs is used to determine whether the multiple groups of services or sessions currently carried by the aggregation port need to be modified; or, the modification judgment unit is set as the basis.
  • the master/slave relationship determines whether the multiple groups of services or sessions currently carried by the aggregation port are modified according to the foregoing indication information.
  • the modifying module further includes: a first modifying unit, configured to: the aggregation group endpoint has a lower priority than the aggregation group endpoint to which the aggregation port of the peer end belongs, or the aggregation group endpoint In the case of the aggregation group endpoint to which the aggregation port belongs to the peer end, the multiple groups of services or sessions currently carried by the aggregation port are modified according to the foregoing indication information.
  • the modifying module further includes: a second modifying unit, configured to: if the aggregation port does not form a service or session currently carried by the aggregation port, set the foregoing according to the foregoing indication information
  • the foregoing aggregation group endpoint further includes: a shielding module, configured to: when the aggregation link corresponding to the aggregation port is faulty or unavailable, or when the aggregation link group is detached, the service currently carried on the aggregation port or The aggregation port corresponding to the foregoing aggregation link is blocked in the foregoing aggregation port sequence corresponding to the session.
  • the foregoing aggregation group endpoint further includes: a first mode determining module, configured to determine a protection mode when the aggregation link corresponding to the one or more aggregation ports is restored or rejoined to the aggregation link group; When the protection mode is the non-inversion mode, the aggregation port corresponding to the aggregation link is added to the aggregation port sequence.
  • the foregoing aggregation group endpoint further includes: a second mode determining module, configured to determine a protection mode when the aggregation link corresponding to the one or more aggregation ports is restored or rejoined to the aggregation link group; When the protection mode is the reverse mode, the aggregation port corresponding to the aggregation link is restored in the aggregation port sequence. If the protection mode is the reverse mode, the change of the aggregation port sequence will trigger the change of the currently carried service or session on the aggregation port.
  • the present invention is based on the LACP protocol, and provides a method for ensuring the same path in the same direction as the service, which can effectively ensure that the same service is selected in the bidirectional manner on both ends of the aggregation group. Traffic of the service/same session selects the same aggregation link at both ends of the aggregation group to meet the protection requirements and implement protection on the interconnection interface.
  • the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices.
  • the computing device 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 are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

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)

Abstract

本发明公开了一种链路聚合组中流量路径的协商方法及装置。其中，该方法包括：聚合端口获取指示信息；其中，该指示信息中包括聚合端口所需承载的多组业务或会话，其中，每组业务或会话中包括一个或多个业务或会话；上述聚合端口确定本端口所需承载的多组业务或会话，和/或，确定当前所承载的业务或会话；上述聚合端口所在的聚合组端点依据各个上述聚合端口当前所承载的业务或会话进行流量的分发。通过本发明，解决了相关技术中同业务或会话无法进行双向同路径传输的问题，实现了互连接口上的保护。

Description

链路聚合组中流量路径的协商方法及装置
技术领域 本发明涉及通信领域， 具体而言， 涉及一种链路聚合组中流量路径的协商方法及 装置。 背景技术 随着宽带业务的飞速发展， 网络与网络之间的互连使用的越来越多， 承载了更多 的业务。 网络内部根据其所采用的技术， 均可有多种方法对链路及其上的节点实现保 护。 随着对流量的保护需求越来越强烈， 要求越来越高， 有运营商也提出了需要对网 络互连进行保护的需求。 这里的保护可以通过采用端口聚合的方式来实现， 常用的方 式可以是端口聚合， 也可以是环路保护。 链路聚合目前常用标准支持的是一个节点上 的端口聚合， 因此仅能用于链路保护上。 在网络边缘接口上如果需要对节点保护， 在 当前的链路聚合技术中无法实现。 因此， 为了适用于网络与网络互连区域组网方式更加多样化， 并能实现不仅对链 路的保护， 而且实现对边缘节点的保护， 美国电气和电子工程师协会 （IEEE) 标准组 织提出了扩展链路聚合， 通过一种分布式的链路聚合组分布式弹性网络（DRNI)来实 现链路和节点双冗余的网络互连保护需求， 即聚合组的端点处由多个节点组成， 这些 多个节点的聚合链路组成一个聚合链路组。 图 1是根据相关技术的网络互连节点连接示意图，如图 1所示，链路聚合组 (LAG) 的两个端点 A、 B都有 2个节点， LAG端点 A的两个节点是系统 1和系统 2， LAG端 点 B的两个节点是系统 3和系统 4。 这 4个系统的多条链路聚合在一起， 形成了一个 聚合组 LAG。 通过这个分布式的 LAG, 能够实现链路和节点的双重保护。 LAG端点 A中的系统 1、 系统 2之间通过内链链路连接进行通信， LAG端点 B的系统 3、 系统 4之间也通过内链链路进行通信。 目前， DRNI 是通过对报文业务的区分来进行保护、 负载分担的， 但由于两端分 别对流量进行分发， 因此无法保证同业务的流量能够在同一条聚合链路上传输。 这对 于 DRNI是用于网络接口的保护来说是相矛盾的， 不符合城域以太网论坛 （MEF) 对 网络接口保护的需求。 针对相关技术中同业务或会话无法进行双向同路径传输的问题， 目前尚未提出有 效的解决方案。 发明内容 针对相关技术中同业务或会话无法进行双向同路径传输的问题， 本发明提供了一 种链路聚合组中流量路径的协商方法及装置， 以至少解决上述问题。 根据本发明的一个方面， 提供了一种链路聚合组中流量路径的协商方法， 该方法 包括： 聚合端口获取指示信息； 其中， 该指示信息中包括聚合端口所需承载的一组或 多组业务或会话， 其中， 每组业务或会话中包括一个或多个业务或会话； 上述聚合端 口确定本端口所需承载的多组业务或会话， 和 /或， 确定当前所承载的业务或会话； 上 述聚合端口所在的聚合组端点依据各个上述聚合端口当前所承载的业务或会话进行流 量的分发。 优选地， 上述当前所承载的业务或会话是上述多组业务或会话中优先级最高的一 组业务或会话。 优选地， 在上述聚合端口所属的聚合组端点中， 每个上述业务或会话对应一个聚 合端口序列， 上述聚合端口序列由上述聚合组端点中的聚合端口排列构成。 优选地， 依据上述聚合组端点中的每个上述业务或会话对应一个聚合端口序列， 确定上述聚合端口所需承载的上述多组业务或会话。 优选地， 上述聚合端口序列中的上述多个聚合端口按照承载上述业务或会话的优 选级进行排序。 优选地， 上述聚合端口所需承载的多组业务或会话是根据各个聚合端口序列中不 同优先级的聚合端口所对应的业务或会话形成的。 优选地， 上述聚合端口所属的聚合组端点依据预定策略修改或设置聚合端口所需 承载的上述多组业务或会话， 和 /或， 确定当前所承载的业务或会话。 优选地， 上述聚合端口确定本端口所需承载的多组业务或会话包括： 上述聚合端 口所属的上述聚合组端点依据上述预定策略修改上述聚合端口所需承载的上述多组业 务或会话； 上述聚合端口根据上述聚合组端点修改后的上述多组业务或会话确定本端 口所需承载的多组业务或会话。 优选地， 上述聚合组端点依据上述预定策略修改上述聚合端口所需承载的上述多 组业务或会话包括： 上述聚合端口所属的聚合组端点在上述聚合端口当前承载的上述 多组业务或会话与上述指示信息中的业务或会话不一致的情况下， 通过对该聚合组端 点的优先级与对端的聚合端口所属聚合组端点的优先级进行比较， 确定是否需要修改 上述聚合端口当前承载的上述多组业务或会话； 或者， 上述聚合端口所属的聚合组端 点依据主备关系判断是否需要按照上述指示信息修改上述聚合端口当前承载的上述多 组业务或会话。 优选地， 上述聚合端口所属的聚合组端点依据自身的优先级关系； 或者， 依据自 身的主备关系判断是否需要按照上述指示信息修改上述聚合端口当前承载的上述多组 业务或会话包括： 如果上述聚合组端点的优先级低于对端的聚合端口所属的聚合组端 点， 或者上述聚合组端点从属于上述对端的聚合端口所属的聚合组端点， 则上述聚合 组端点按照上述指示信息修改上述聚合端口当前承载的上述多组业务或会话。 优选地， 上述聚合端口所属的聚合组端点依据上述预定策略设置上述聚合端口所 需承载的上述多组业务或会话包括： 如果上述聚合端口未形成上述聚合端口当前承载 的业务或会话， 则上述聚合端口所属的聚合组端点按照上述指示信息设置上述聚合端 口当前承载的上述多组业务或会话。 优选地， 上述方法还包括： 当上述聚合端口所对应的聚合链路发生故障或不可用， 或者， 从上述聚合链路组脱离时， 上述聚合端口所在的聚合组端点在上述聚合端口当 前承载的业务或会话对应的上述聚合端口序列中，屏蔽上述聚合链路对应的聚合端口。 优选地， 上述方法还包括： 当上述一个或多个聚合端口所对应的聚合链路恢复使 用或者重新加入上述聚合链路组时， 上述聚合组端点确定保护模式： 如果上述保护模 式为非反转模式， 则将上述聚合链路对应的聚合端口添加到上述聚合端口序列中。 优选地， 上述方法还包括： 当上述一个或多个聚合端口所对应的聚合链路恢复使 用或者重新加入上述聚合链路组时， 上述聚合组端点确定保护模式； 如果上述保护模 式为反转模式， 则在上述聚合端口序列中恢复上述聚合链路对应的聚合端口。 优选地， 如果上述保护模式为反转模式， 则聚合端口序列的变化将触发上述聚合 端口上当前所承载的业务或会话的变化。 优选地， 上述指示信息可以为类型长度值 TLV字段。 优选地， 上述指示信息可以携带在链路汇聚控制协议 LACP报文中。 根据本发明的另一方面， 提供了一种链路聚合组中流量路径的协商装置， 该装置 包括： 聚合端口， 以及上述聚合端口所在的聚合组端点， 其中， 上述聚合端口包括： 指示信息获取模块， 设置为获取指示信息； 其中， 上述指示信息中包括上述聚合端口 所需承载的多组业务或会话， 其中， 每组业务或会话中包括一个或多个业务或会话； 确定模块， 设置为确定上述聚合端口所需承载的多组业务或会话， 和 /或， 确定当前所 承载的业务或会话； 上述聚合组端点包括： 分发模块， 设置为依据各个上述聚合端口 当前所承载的业务或会话进行流量的分发。 优选地， 上述当前所承载的业务或会话是上述多组业务或会话中优先级最高的一 组业务或会话。 优选地， 在上述聚合端口所属的聚合组端点中， 每个上述业务或会话对应一个聚 合端口序列， 上述聚合端口序列由上述聚合组端点中的聚合端口排列构成。 优选地， 依据上述聚合组端点中的每个上述业务或会话对应一个聚合端口序列， 确定上述聚合端口所需承载的上述多组业务或会话。 优选地， 上述聚合端口序列中的上述多个聚合端口按照承载上述业务或会话的优 选级进行排序。 优选地， 上述聚合端口所需承载的多组业务或会话是根据各个聚合端口序列中不 同优先级的聚合端口所对应的业务或会话形成的。 优选地， 上述聚合端口所属的聚合组端点依据预定策略修改或设置聚合端口所需 承载的上述多组业务或会话， 和 /或， 确定当前所承载的业务或会话。 优选地， 上述聚合组端点还包括： 修改模块， 设置为依据上述预定策略修改上述 聚合端口所需承载的上述多组业务或会话； 上述确定模块包括： 确定单元， 设置为根 据上述修改模块修改的上述多组业务或会话，确定该端口所需承载的多组业务或会话。 优选地， 上述修改模块包括： 修改确定单元， 设置为在上述聚合端口当前承载的 上述多组业务或会话与上述指示信息中的业务或会话不一致的情况下， 通过对该聚合 组端点的优先级与对端的聚合端口所属聚合组端点的优先级进行比较， 确定是否需要 修改上述聚合端口当前承载的上述多组业务或会话； 或者， 修改判断单元， 设置为依 据主备关系判断是否需要按照上述指示信息修改上述聚合端口当前承载的上述多组业 务或会话。 优选地， 上述修改模块还包括： 第一修改单元， 设置为在上述聚合组端点的优先 级低于对端的聚合端口所属的聚合组端点， 或者上述聚合组端点从属于上述对端的聚 合端口所属的聚合组端点的情况下， 按照上述指示信息修改上述聚合端口当前承载的 上述多组业务或会话。 优选地， 上述修改模块还包括： 第二修改单元， 设置为在上述聚合端口未形成上 述聚合端口当前承载的业务或会话的情况下， 按照上述指示信息设置上述聚合端口当 前承载的上述多组业务或会话。 优选地， 上述聚合组端点还包括： 屏蔽模块， 设置为在上述聚合端口所对应的聚 合链路发生故障或不可用， 或者， 从上述聚合链路组脱离的情况下， 在上述聚合端口 当前承载的业务或会话对应的上述聚合端口序列中， 屏蔽上述聚合链路对应的聚合端 π。 优选地， 上述聚合组端点还包括： 第一模式确定模块， 设置为在上述一个或多个 聚合端口所对应的聚合链路恢复使用或者重新加入上述聚合链路组的情况下， 确定保 护模式； 添加模块， 设置为在上述保护模式为非反转模式的情况下， 将上述聚合链路 对应的聚合端口添加到上述聚合端口序列中。 优选地， 上述聚合组端点还包括： 第二模式确定模块， 设置为在上述一个或多个 聚合端口所对应的聚合链路恢复使用或者重新加入上述聚合链路组的情况下， 确定保 护模式； 恢复模块， 设置为在上述保护模式为反转模式的情况下， 在上述聚合端口序 列中恢复上述聚合链路对应的聚合端口。 优选地， 如果上述保护模式为反转模式， 则聚合端口序列的变化将触发上述聚合 端口上当前所承载的业务或会话的变化。 在本发明的实施例中， 聚合端口获取指示信息， 该指示信息中包括聚合端口所需 承载的多组业务或会话， 每组业务或会话中包括一个或多个业务或会话， 上述聚合端 口确定本端口所需承载的多组业务或会话， 和 /或， 确定当前所承载的业务或会话， 上 述聚合端口所在的聚合组端点依据各个上述聚合端口当前所承载的业务或会话进行流 量的分发， 解决了相关技术中同业务或会话无法进行双向同路径传输的问题， 实现了 互连接口上的保护。 附图说明 此处所说明的附图用来提供对本发明的进一步理解， 构成本申请的一部分， 本发 明的示意性实施例及其说明用于解释本发明， 并不构成对本发明的不当限定。 在附图 中- 图 1是根据相关技术的网络互连节点连接示意图； 图 2是根据本发明实施例的链路聚合组中流量路径的协商方法的流程图； 图 3是根据本发明实施例的组网示意图； 图 4是根据本发明实施例的故障示意图； 以及 图 5是根据本发明实施例的链路聚合组中流量路径的协商装置的结构框图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是， 在不冲突的 情况下， 本申请中的实施例及实施例中的特征可以相互组合。 本发明实施例提供了一种链路聚合组中流量路径的协商方法及装置， 下面通过实 施例进行详细介绍。 本实施例提供了一种链路聚合组中流量路径的协商方法， 图 2是根据本发明实施 例的链路聚合组中流量路径的协商方法的流程图， 如图 2所示， 该方法包括以下步骤 (步骤 S202-步骤 S206): 步骤 S202， 聚合端口获取指示信息； 其中， 该指示信息中包括聚合端口所需承载 的一组或多组业务或会话， 其中， 每组业务或会话中包括一个或多个业务或会话； 步骤 S204， 聚合端口确定本端口所需承载的多组业务或会话， 和 /或， 确定当前所 承载的业务或会话； 步骤 S206，聚合端口所在的聚合组端点依据各个上述聚合端口当前所承载的业务 或会话进行流量的分发。 通过上述实施例， 聚合端口获取指示信息， 该指示信息中包括聚合端口所需承载 的多组业务或会话， 每组业务或会话中包括一个或多个业务或会话， 上述聚合端口确 定本端口所需承载的多组业务或会话， 和 /或， 确定当前所承载的业务或会话， 上述聚 合端口所在的聚合组端点依据各个上述聚合端口当前所承载的业务或会话进行流量的 分发， 解决了相关技术中同业务或会话无法进行双向同路径传输的问题， 实现了互连 接口上的保护。 在本实施例中， 为了保证业务或会话的处理效果， 上述当前所承载的业务或会话 一般是多组业务或会话中优先级最高的一组业务或会话。 对于聚合端口承载的多组业务或会话， 本实施例提供了一种优选实施方式， 即， 聚合组的两端或者其中一端都有自己的业务分配端口表， 不同的业务或会话对应的多 个聚合链路， 这多个聚合链路按该业务优先分发的优先级排列。 在优选实施过程中， 上述指示信息可以为但不限于： 类型长度值 TLV字段。 上述 指示信息可以携带在链路汇聚控制协议 LACP报文中。 本实施例提供了一种优选实施方式， 用于实现本实施例提供的链路聚合组中流量 路径的协商方法。 具体步骤如下： 第一. 聚合组的两端或者其中一端都有自己的业务分配端口表， 不同的业务或会 话对应的多个聚合链路， 这多个聚合链路按该业务优先分发的优先级排列。 基于此， 本实施例提供了一种优选实施方式， 即在聚合端口所属的聚合组端点中， 每个业务或 会话对应一个聚合端口序列， 该聚合端口序列由上述聚合组端点中的聚合端口排列构 成。聚合端口序列中的上述多个聚合端口按照承载上述业务或会话的优选级进行排序。 优选地， 该聚合端口序列能够以业务分配端口表的形式体现。 第二. 依据业务分配端口表， 获取各个端口的业务承载优先级序列表。 该业务承 载优先级序列表是依据业务分配端口表中各个优先级别端口获取的。 基于此， 本实施 例提供了一种优选实施方式， 即依据上述聚合组端点中的每个上述业务或会话对应一 个聚合端口序列， 确定上述聚合端口所需承载的上述多组业务或会话。 上述聚合端口 所需承载的多组业务或会话是根据各个聚合端口序列中不同优先级的聚合端口所对应 的业务或会话形成的。 该聚合端口与其所需承载的多组业务或会话的对应关系能够以 业务承载优先级序列表的形式体现。 第三. 定义一个新的业务协商 TLV字段， 该业务协商 TLV中携带的是各个聚合 端口按优先级不同所承载业务， 即业务承载优先级序列表。 第四.聚合端口在收到携带有业务协商 TLV后，将生成一个对端业务分配端口表， 如果本端也有业务承载表， 则和自身的业务分配端口相比较。 根据策略， 例如系统的 优先级或系统的主备关系来决定是否按对端业务分配端口表的信息修改自己的业务分 配端口表， 确保聚合组的两端其业务分配端口表是一致的， 两端均是按照这样一个业 务分配端口表来进行流量的分发， 从而保证该聚合组的每条聚合链路承载相同的业务 / 会话流量， 保证同业务的流量能双向同路径。 如果本端没有业务分配端口表， 则根据 收到的业务协商 TLV， 构建本端的业务分配端口表。 基于上述流程， 本实施例提供了一种优选实施方式， 即聚合端口所属的聚合组端 点依据预定策略修改或设置聚合端口所需承载的上述多组业务或会话， 和 /或， 确定当 前所承载的业务或会话。 聚合端口确定本端口所需承载的多组业务或会话包括： 聚合 端口所属的聚合组端点依据上述预定策略修改聚合端口所需承载的多组业务或会话； 聚合端口根据聚合组端点修改后的上述多组业务或会话确定本端口所需承载的多组业 务或会话。 聚合组端点依据预定策略修改聚合端口所需承载的多组业务或会话包括： 聚合端 口所属的聚合组端点在聚合端口当前承载的多组业务或会话与指示信息中的业务或会 话不一致的情况下， 通过对该聚合组端点的优先级与对端的聚合端口所属聚合组端点 的优先级进行比较， 确定是否需要修改聚合端口当前承载的多组业务或会话； 或者， 聚合端口所属的聚合组端点依据主备关系判断是否需要按照上述指示信息修改聚合端 口当前承载的多组业务或会话。 聚合端口所属的聚合组端点依据自身的优先级关系； 或者， 依据自身的主备关系 判断是否需要按照指示信息修改聚合端口当前承载的多组业务或会话包括： 如果聚合 组端点的优先级低于对端的聚合端口所属的聚合组端点， 或者聚合组端点从属于对端 的聚合端口所属的聚合组端点， 则聚合组端点按照指示信息修改聚合端口当前承载的 多组业务或会话。 聚合端口所属的聚合组端点依据预定策略设置聚合端口所需承载的多组业务或会 话包括： 如果聚合端口未形成聚合端口当前承载的业务或会话， 则聚合端口所属的聚 合组端点按照指示信息设置聚合端口当前承载的多组业务或会话。 第五. 当某条聚合链路不可用时， 例如该聚合链路故障、 或者该聚合链路从聚合 组中脱离出来， 则触发聚合组两端的业务分配端口表变化， 在业务分配端口表中删除 该不可用的聚合端口。 当该聚合链路恢复时或该聚合链路重新加入到该聚合组中时， 如果该保护是反转 (Revertive) 模式， 则恢复该聚合链路在原业务分配端口表中的位置。 业务分配端口 表中第一优先级端口的变化将触发聚合器在聚合端口上分发流量的变化， 从而恢复所 述原故障的聚合链路上的业务。 如果是非反转 （Non-revertive) 模式， 则所述原故障 的聚合链路仅是添加到当前业务分配端口表的端口序列中。 基于上述流程， 本实施例提供了一种优选实施方式， 本实施例提供的上述方法还 包括： 当聚合端口所对应的聚合链路发生故障或不可用， 或者， 从聚合链路组脱离时， 聚合端口所在的聚合组端点在聚合端口当前承载的业务或会话对应的聚合端口序列 中， 屏蔽聚合链路对应的聚合端口。 当一个或多个聚合端口所对应的聚合链路恢复使用或者重新加入聚合链路组时， 聚合组端点确定保护模式： 如果上述保护模式为非反转模式， 则将聚合链路对应的聚 合端口添加到聚合端口序列中。 当一个或多个聚合端口所对应的聚合链路恢复使用或 者重新加入聚合链路组时，聚合组端点确定保护模式； 如果上述保护模式为反转模式， 则在合端口序列中恢复聚合链路对应的聚合端口。 此外， 如果上述保护模式为反转模 式， 则聚合端口序列的变化将触发聚合端口上当前所承载的业务或会话的变化。 下面通过实施例和附图对本发明实施例进一步说明。 实施例一 图 3是根据本发明实施例的组网示意图， 如图 3所示， 聚合组的两端分别均由多 节点组成， 端点 1由节点 A、 节点 B组成， 端点 2由节点 C、 节点 D组成。 端点 1有 端口 a、 端口 b、 端口 c、 端口 d参与聚合， 端点 2有端口 x、 端口 y、 端口 z、 端口 w 参与聚合。 端口 a和端口 w互连为聚合链路 1 ; 端口 b和端口 y互连为聚合链路 2; 端口 c和端口 X互连为聚合链路 3; 端口 d和端口 z互连为聚合链路 4。 聚合链路 1、 聚合链路 2、 聚合链路 3、 聚合链路 4形成聚合组。 端点 1中的节点 A、 节点 B经协 商后得到一个业务分配端口表， 端点 1的业务分配端口表如表 1所示。 表 1
Figure imgf000011_0001
端点 2中的节点〔、 节点 D经协商后得到一个业务分配表， 端点 2的业务分配端 口表如表 2所示。 表 2
Figure imgf000012_0001
上述业务分配端口表的每条表项可以通过一组变量标识得到： Aggregator_Vlan_XXXXXX_Oper_Porto其中端口序列中，排在第一位的是对应业务的 第一优先端口， 排在第二位的对应业务的第二优先端口， 依次类推。 另 外 ， 聚 合 组 的 每 端 都 有 一 个 系 统 管 理 的 Aggregator_Vlan_XXXXXX_Admin_Port， 用于保存本端的原始配置和系统设置。 Aggregator_Vlan_XXXXXX_Oper_Port 的 初 始 值 来 源 于 Aggregator_Vlan_XXXXXX_Admin_Port 。 通 过 对
Aggregator_Vlan_XXXXXX_Oper_Port 的解析， 聚合器将不同的业务流量分发到不同 的聚合端口上。 依据业务分配端口表， 各个聚合端口获取自己的业务承载优先级序列表， 该业务 承载优先级序列表是依据业务分配端口表中各个优先级别端口获取的。 该表用一系列 的 Port_Oper_Vlan_List_X变量来标识， 这里的 X标识优先等级。 下面以聚合端口 a和聚合端口 w为例， 表 3表示了聚合端口 a的业务承载优先级 序列表。 表 3
Figure imgf000012_0002
表 4表示了聚合端口 w的业务承载优先级序列表。 表 4
Figure imgf000013_0001
LACP协议报文中的业务协商 TLV字段携带发送该报文的聚合端口对应的业务承 载优先级序列表信息。 该业务协商 TLV的格式如表 5所示。 ¾ 5
TLV_Type=Service information
Service lnformation Length
Service—List— 1
Service_List_2
Service_List_3
End TLV 其中， Service_List_X 也是一种子类型 TLV， 每个 Service_List_X 包含了 Port_Oper_Vlan_List_X信息。 Service_List_X TLV的格式如表 6所示。 表 6
Sub-TLV Type=Service List
List Number
Priority
List Length
Service List 因此， 从端口 a、 端口 w发出的 LACP协议报文携带有业务协商 TLV， 端口 a发 出的 LACP协议报文携带的 TLV的格式如表 7所示。 ¾ 7
TLV_Type=Service information
Service lnformation Length
Sub-TLV Type=Service List
List Number=4
Priority: 1
List Length=100
~ {002、 005、 010、 } Priority=2
List Length= 100
― {003、 006、 00A、 }
Priority=3
List Length= 100
― {004、 007 00B、 }
Priority=4
List Length= 100
― {002、 008 00C、 }
End TLV 端口 w发出的 LACP协议报文携带的 TLV的格式如表 8所示。 ¾ 8
TLV_Type=Service information
S ervice lnformation Length
Sub-TLV Type=Service List
List Number=4
Priority: 1
List Length= 100
― {001、 005、 009、 }
Priority=2
List Length= 100
― {004、 006、 00A、 }
Priority=3
List Length= 100
{003 007 00B、 }
Priority=4
List Length= 100
― {001 008、 00C、 }
End TLV 聚合链路两端的端口 a和端口 w互发业务协商 TLV，并根据收到的业务协商 TLV 生成一张对端的业务承载优先级序列表， 并将自己的业务承载优先级序列表也对端的 业务承载优先级序列表进行比较。 从表 7和表 8中可以看出， 各个端口最初的承载业务是有差异的， 然后依据某特 定策略， 例如依据系统优先级 （System Priority), 或者系统 ID ( System ID), 或者聚 合组两端的主从关系， 这里假设端点 1的系统优先级要高于端点 2的系统优先级， 或 者端点 1是主设备端 （Master), 端点 2是从设备端 （Slave), 因此端点 2的端口 w遵 从于端点 1的端口 a所承载的业务，修改其自身的业务承载优先级序列表，经过 LACP 的协商， 端口 w的业务承载优先级序列表修改为表 3所示， 和端口 a的业务承载优先 级序列表一致。 一旦修改成功， 则端口 w发送的 LACP报文中其业务协商 TLV中的 信息如表 7所示， 和端口 a发送的业务协商 TLV—致。 当聚合端口收到的 LACP报文中业务协商 TLV信息和自身的业务承载表内容一致 时， 则表示两者协商达成了一致， 业务开始从该聚合链路上进行传输 （聚合器的状态 进入 distributing状态）， 同一业务的双向的流量能保证双向同路径了。 当其中一条聚合链路故障或者从聚合组中隔离出来， 假设聚合链路 1故障， 此时 将触发业务端口分配表中的端口变化， 图 4是根据本发明实施例的故障示意图， 如图 4所示， 在业务端口分配表中将该聚合端口设置为不可用。 业务端口分配表修改后触 发各个聚合端口的业务承载优先级序列表， 数据流量重新依据新到的业务承载优先级 序列表进行分发。 当该聚合链路恢复时， 在业务端口分配表中将该恢复的聚合端口重新设置可用， 然后需要先对保护模式进行判断。 如果该保护系统的保护模式为反转模式， 则业务端 口分配表修改后触发各个聚合端口的业务承载优先级序列表， 业务承载优先级序列表 又恢复成故障之前的内容， 从而将流量重新恢复该聚合链路上。 如果该保护系统的保 护模式为非反转模式， 则业务端口分配表修改不会触发各个聚合端口的业务承载优先 级序列表， 因此各个聚合端口的业务承载优先级序列表保持当前的内容不变， 从而不 会对现行流量做出切换。 实施例二 实施例二与实施例一类似， 不同的是实施例一中端点 1和端点 2都有自己的业务 端口分配表， 并生成自己各个聚合端口的业务承载表， 从而根据这个业务承载表发送 业务协商 TLV， 并通过两端的协商达到两端的一致。 在本实施例中， 只有一端配置有自己的业务端口分配表。 这里假设端点 1有自己 的业务端口分配表， 如上述表 1所示。 因此端点 1的各个聚合端口会依据该业务端口 分配表生成自己的业务承载优先级序列表， 假设端口 a的业务承载优先级序列表如上 述表 3所示， 则从端口 a发送的 LACP报文中携带的业务协商 TLV如上述表 5所示。 和端口 a连接的端点 2的端口 w， 收到端口 a发来的业务协商 TLV后， 由于自身 还没有业务承载优先级序列表， 因此会根据收到的对端业务协商 TLV， 构建自己的本 端口的业务承载表业务承载优先级序列表。端口 w的业务承载优先级序列表将和端口 a的业务承载优先级序列表保持一致。 依次类推， 当端点 2的所有聚合端口， 端口 w、 x、 y、 z都建立了自己的业务承 载优先级序列表后， 端点 2依据各个端口的业务承载优先级序列表建构自己的业务端 口分配表。 一旦各个端口构建了自己的业务承载优先级序列表后， 也将开始通过业务协商 TLV传递自己业务承载表的信息， 从而两端能够始终保持业务传输上的一致性， 并保 持同业务的双向同路径。 实施例三 实施例三与实施例一、 二不同的是， 本实施例是对流的标识， 这里用 stream id标 识。 本发明实施例所涉及的协商不仅可以是报文中业务的协商， 例如客户虚拟局域网 标识 （ Custom VL AN ID， 简称为 C-VID)、 业务虚拟局域网标识 （Service VLAN ID， 简称为 S-VID)、 骨干虚拟局域网标识 （Backbone VLAN ID， 简称为 B-VID)、 骨干业 务实例标识（Backbone Service Instance Identifier, 简称为 I-SID)等， 也可以是两端定 义好的流标识的协商。 该流标识是对一类数据流的定义， 一类数据流可以是目的媒体 接入控制（Media Access Control, 简称为 MAC)、 源 MAC是相同一组 MAC对的， 可 以是目的网络协议 （Internet Protocol, 简称为 IP)、 源 IP是相同一组 IP对的， 也可以 是具有相同业务标识的， 等等。 假设对一些特定数据流进行定义标识， 流标识定义如表 9所示。 表 9
Figure imgf000016_0001
上述流标识是需要聚合组的双方都协商定义好的， 即对同一类的数据流具有相同 的流标识 Stream ID。 这时， 聚合端口之间交互的不再是业务协商 TLV， 而是流标识 TLV。 假设在端点 1这一端， 端点 1的聚合端口与流的对应关系如表 10所示。 表 10
Figure imgf000017_0001
假设在端点 2这一端， 端点 2的聚合端口与流的对应关系如表 11所示。
表 11
Figure imgf000017_0002
上述聚合端口与流的对应表的每条表项可以通过一组变量标识得到：
Aggregator_Stream_XXXXXX_Oper_Port。其中端口序列中， 排在第一位的是对应数据 流的第一优先端口， 排在第二位的对应数据流的第二优先端口， 依次类推。 另 外 聚 合 组 的 每 端 都 有 一 个 系 统 管 理 的 Aggregator_Stream_XXXXXX_Admin_Port , 用于保存本端的原始配置和系统设置。 Aggregator_Stream_XXXXXX_Oper_Port 的 初 始 值 来 源 于 Aggregator_Stream_XXXXXX_Admin_Port 。 通 过 对
Aggregator_Stream_XXXXXX_Oper_Port 的解析， 聚合器将不同的数据流流量分发到 不同的聚合端口上。 依据流量分配端口表， 各个聚合端口获取自己的数据流承载优先级序列表， 该数 据流承载优先级序列表是依据数据流分配端口表中各个优先级别端口获取的。 该表用 一系列的 Port_Oper_Stream_List_X变量来标识， 这里的 X标识优先等级。 下面以聚合端口 a和聚合端口 w为例， 表 12表示了聚合端口 a的数据流承载优 先级序列表。 表 12
优先级 承载数据流 1 000001 、 000005 、
000009
2 000004 、 000006 、
00000A
3 000003 、 000007 、
00000B
4 000002 、 000008 、
00000C
表 13表示了聚合端口 w的数据流承载优先级序列表。 表 13
优先级 承载数据流
1 000002 、 000005 、
000010、
2 000003 、 000006 、
00000A
3 000004 、 000007 、
00000B
4 000001 、 000008 、
00000C
LACP协议报文中的数据流协商 TLV字段， 携带发送该报文的聚合端口对应的数 据流承载优先级序列表信息。 该数据流协商 TLV的格式为表 14所示。 ¾ M
TLV_Type=Stream ID
Stream ID Length
Stream_ID_List_ 1
Stream_ID_List_2
Stream_ID_List_3
End TLV 其中， Stream_ID_List_X也是一种子类型 TLV， 每个 Stream_ID_List_X包含了 Port Oper Stream List X信息。 Stream_ID_List_X TLV的格式如表 15所示。 表 15
Sub-TLV Type=Stream_ID List
List Number
Priority
List Length I Stream—ID List | 因此， 从端口 a、 端口 w发出的 LACP协议报文携带有数据流协商 TLV， 端口 a 发出的 LACP协议报文携带的 TLV的格式如表 16所示。 表 16
TLV_Type=Stream information
Stream ID Length
Sub-TLV Type=Stream_ID List
List Number=4
Priority: 1
List Length=100
{000002 000005 000010、 }
Priority=2
List Length=100
{000003 000006 00000A }
Priority=3
List Length=100
{000004 000007 00000B }
Priority=4
List Length=100
{000002 000008 00000C }
End TLV 端口 w发出的 LACP协议报文携带的 TLV的格式如表 17所示。 表 17
TLV_Type=Stream information
Stream ID Length
Sub-TLV Type=Stream_ID List
List Number=4
Priority: 1
List Length=100
{000001 000005 000009 }
Priority=2
List Length=100
{000004 000006 00000A }
Priority=3
List Length=100
{000003 000007 00000B }
Priority=4
List Length=100
Figure imgf000020_0001
聚合链路两端的端口 a和端口 w互发数据流协商 TLV， 并根据收到的数据流协商 TLV生成一张对端的数据流承载优先级序列表， 并将自己的数据流承载优先级序列表 也对端的数据流承载优先级序列表进行比较。 从上述表 7和表 8中可以看出， 各个端口最初的承载流量是有差异的， 然后依据 某特定策略， 例如依据系统优先级 （System Priority), 假设端点 1的系统优先级要高 于端点 2的系统优先级， 因此端口 w遵从于端口 a所承载的流量， 修改其自身的数据 流承载优先级序列表， 经过 LACP的协商， 端口 w的数据流承载优先级序列表修改为 表 12所示， 和端口 a的数据流承载优先级序列表一致。 一旦修改成功， 则端口 w发 送的 LACP报文中其数据流协商 TLV中的信息如上述表 16所示， 和端口 a发送的数 据流协商 TLV—致。 当聚合端口收到的 LACP报文中数据流协商 TLV信息和自身的数据流承载表内容 一致时， 则表示两者协商达成了一致， 该特定的数据流量开始从该聚合链路上进行传 输 （聚合器的状态进入 distributing状态）， 同一会话的双向的流量能保证双向同路径 了。 当聚合链路发生故障或从聚合组中隔离出来时， 其操作过程与实施例一相似， 只 是业务标识改为流标识。 在本实施例中， 采用流标识来进行报文的分发， 以及同路径的协商， 可以用于识 别同一会话的流量， 减小了识别不同流量的颗粒度， 可以增强聚合组在进行负载均衡 上更加的均勾。 对应于上述实施例介绍的链路聚合组中流量路径的协商方法， 本实施例提供了一 种链路聚合组中流量路径的协商装置， 用于实现上述实施例。 图 5是根据本发明实施 例的链路聚合组中流量路径的协商装置的结构框图， 如图 5所示， 该装置包括： 聚合 端口 10， 以及上述聚合端口所在的聚合组端点 20。 图 5以聚合端口 10位于聚合组端 点 20中来表示二者的关系， 当然图 5只是示意性说明。二者的关系实际上是聚合端口 10从属于聚合组端点 20。 其中， 上述聚合端口 10包括： 指示信息获取模块 12， 设置为获取指示信息； 其 中， 上述指示信息中包括上述聚合端口所需承载的多组业务或会话， 其中， 每组业务 或会话中包括一个或多个业务或会话； 确定模块 14， 连接至指示信息获取模块 12， 设 置为确定上述聚合端口所需承载的多组业务或会话， 和 /或， 确定当前所承载的业务或 会话； 上述聚合组端点 20包括： 分发模块 22， 设置为依据各个上述聚合端口当前所承 载的业务或会话进行流量的分发。 通过上述实施例， 聚合端口获取指示信息， 该指示信息中包括聚合端口所需承载 的多组业务或会话， 每组业务或会话中包括一个或多个业务或会话， 上述聚合端口确 定本端口所需承载的多组业务或会话， 和 /或， 确定当前所承载的业务或会话， 上述聚 合端口所在的聚合组端点依据各个上述聚合端口当前所承载的业务或会话进行流量的 分发， 解决了相关技术中同业务或会话无法进行双向同路径传输的问题， 实现了互连 接口上的保护。 在本实施例中， 上述当前所承载的业务或会话是上述多组业务或会话中优先级最 高的一组业务或会话。 在上述聚合端口所属的聚合组端点中， 每个上述业务或会话对 应一个聚合端口序列， 上述聚合端口序列由上述聚合组端点中的聚合端口排列构成。 依据上述聚合组端点中的每个上述业务或会话对应一个聚合端口序列， 确定上述聚合 端口所需承载的上述多组业务或会话。 上述聚合端口序列中的上述多个聚合端口按照 承载上述业务或会话的优选级进行排序。 上述聚合端口所需承载的多组业务或会话是 根据各个聚合端口序列中不同优先级的聚合端口所对应的业务或会话形成的。 上述聚 合端口所属的聚合组端点依据预定策略修改或设置聚合端口所需承载的上述多组业务 或会话， 和 /或， 确定当前所承载的业务或会话。 对于聚合组端点依据预定策略修改聚合端口所需承载的上述多组业务或会话的流 程， 本实施例提供了一种优选实施方式， 即上述聚合组端点还包括： 修改模块， 设置 为依据上述预定策略修改上述聚合端口所需承载的上述多组业务或会话； 上述确定模 块包括： 确定单元， 设置为根据上述修改模块修改的上述多组业务或会话， 确定该端 口所需承载的多组业务或会话。 本实施例提供了一种优选实施方式， 即上述修改模块包括： 修改确定单元， 设置 为在上述聚合端口当前承载的上述多组业务或会话与上述指示信息中的业务或会话不 一致的情况下， 通过对该聚合组端点的优先级与对端的聚合端口所属聚合组端点的优 先级进行比较， 确定是否需要修改上述聚合端口当前承载的上述多组业务或会话； 或 者， 修改判断单元， 设置为依据主备关系判断是否需要按照上述指示信息修改上述聚 合端口当前承载的上述多组业务或会话。 本实施例提供了一种优选实施方式， 即上述修改模块还包括： 第一修改单元， 设 置为在上述聚合组端点的优先级低于对端的聚合端口所属的聚合组端点， 或者上述聚 合组端点从属于上述对端的聚合端口所属的聚合组端点的情况下， 按照上述指示信息 修改上述聚合端口当前承载的上述多组业务或会话。 本实施例提供了一种优选实施方式， 即上述修改模块还包括： 第二修改单元， 设 置为在上述聚合端口未形成上述聚合端口当前承载的业务或会话的情况下， 按照上述 指示信息设置上述聚合端口当前承载的上述多组业务或会话。 上述聚合组端点还包括： 屏蔽模块， 设置为在上述聚合端口所对应的聚合链路发 生故障或不可用， 或者， 从上述聚合链路组脱离的情况下， 在上述聚合端口当前承载 的业务或会话对应的上述聚合端口序列中， 屏蔽上述聚合链路对应的聚合端口。 上述聚合组端点还包括： 第一模式确定模块， 设置为在上述一个或多个聚合端口 所对应的聚合链路恢复使用或者重新加入上述聚合链路组的情况下， 确定保护模式； 添加模块， 设置为在上述保护模式为非反转模式的情况下， 将上述聚合链路对应的聚 合端口添加到上述聚合端口序列中。 上述聚合组端点还包括： 第二模式确定模块， 设置为在上述一个或多个聚合端口 所对应的聚合链路恢复使用或者重新加入上述聚合链路组的情况下， 确定保护模式； 恢复模块， 设置为在上述保护模式为反转模式的情况下， 在上述聚合端口序列中恢复 上述聚合链路对应的聚合端口。 如果上述保护模式为反转模式， 则聚合端口序列的变 化将触发上述聚合端口上当前所承载的业务或会话的变化。 从以上的描述中可以看出， 本发明基于 LACP协议， 提供一种保证同业务双向同 路径的方法， 能够有效的保证同业务在聚合组的两端双向上选择同一条聚合链路， 即 同一业务 /同一会话的流量在聚合组的两端选择相同的一条聚合链路， 从而满足对保护 的需求， 实现互连接口上的保护。 显然， 本领域的技术人员应该明白， 上述的本发明的各模块或各步骤可以用通用 的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布在多个计算装置所 组成的网络上， 可选地， 它们可以用计算装置可执行的程序代码来实现， 从而， 可以 将它们存储在存储装置中由计算装置来执行， 并且在某些情况下， 可以以不同于此处 的顺序执行所示出或描述的步骤， 或者将它们分别制作成各个集成电路模块， 或者将 它们中的多个模块或步骤制作成单个集成电路模块来实现。 这样， 本发明不限制于任 何特定的硬件和软件结合。 以上所述仅为本发明的优选实施例而已， 并不用于限制本发明， 对于本领域的技 术人员来说， 本发明可以有各种更改和变化。 凡在本发明的精神和原则之内， 所作的 任何修改、 等同替换、 改进等， 均应包含在本发明的保护范围之内。

Claims

权 利 要 求 书
1. 一种链路聚合组中流量路径的协商方法， 包括：
聚合端口获取指示信息； 其中， 所述指示信息中包括聚合端口所需承载的 一组或多组业务或会话，其中，每组业务或会话中包括一个或多个业务或会话; 所述聚合端口确定本端口所需承载的多组业务或会话， 和 /或， 确定当前所 承载的业务或会话；
所述聚合端口所在的聚合组端点依据各个所述聚合端口当前所承载的业务 或会话进行流量的分发。
2. 根据权利要求 1所述的方法， 其中， 所述当前所承载的业务或会话是所述多组 业务或会话中优先级最高的一组业务或会话。
3. 根据权利要求 1所述的方法， 其中， 在所述聚合端口所属的聚合组端点中， 每 个所述业务或会话对应一个聚合端口序列， 所述聚合端口序列由所述聚合组端 点中的聚合端口排列构成。
4. 根据权利要求 3所述的方法， 其中， 依据所述聚合组端点中的每个所述业务或 会话对应一个聚合端口序列， 确定所述聚合端口所需承载的所述多组业务或会 话。
5. 根据权利要求 2所述的方法， 其中， 所述聚合端口序列中的所述多个聚合端口 按照承载所述业务或会话的优选级进行排序。
6. 根据权利要求 5所述的方法， 其中， 所述聚合端口所需承载的多组业务或会话 是根据各个聚合端口序列中不同优先级的聚合端口所对应的业务或会话形成 的。
7. 根据权利要求 1所述的方法， 其中， 所述聚合端口所属的聚合组端点依据预定 策略修改或设置聚合端口所需承载的所述多组业务或会话， 和 /或， 确定当前所 承载的业务或会话。
8. 根据权利要求 1所述的方法， 其中， 所述聚合端口确定本端口所需承载的多组 业务或会话包括： 所述聚合端口所属的所述聚合组端点依据所述预定策略修改所述聚合端口 所需承载的所述多组业务或会话；
所述聚合端口根据所述聚合组端点修改后的所述多组业务或会话确定本端 口所需承载的多组业务或会话。
9. 根据权利要求 7或 8所述的方法， 其中， 所述聚合组端点依据所述预定策略修 改所述聚合端口所需承载的所述多组业务或会话包括：
所述聚合端口所属的聚合组端点在所述聚合端口当前承载的所述多组业务 或会话与所述指示信息中的业务或会话不一致的情况下， 通过对该聚合组端点 的优先级与对端的聚合端口所属聚合组端点的优先级进行比较， 确定是否需要 修改所述聚合端口当前承载的所述多组业务或会话；
或者，
所述聚合端口所属的聚合组端点依据主备关系判断是否需要按照所述指示 信息修改所述聚合端口当前承载的所述多组业务或会话。
10. 根据权利要求 9所述的方法， 其中， 所述聚合端口所属的聚合组端点依据自身 的优先级关系； 或者， 依据自身的主备关系判断是否需要按照所述指示信息修 改所述聚合端口当前承载的所述多组业务或会话包括：
如果所述聚合组端点的优先级低于对端的聚合端口所属的聚合组端点， 或 者所述聚合组端点从属于所述对端的聚合端口所属的聚合组端点， 则所述聚合 组端点按照所述指示信息修改所述聚合端口当前承载的所述多组业务或会话。
11. 根据权利要求 7所述的方法， 其中， 所述聚合端口所属的聚合组端点依据所述 预定策略设置所述聚合端口所需承载的所述多组业务或会话包括：
如果所述聚合端口未形成所述聚合端口当前承载的业务或会话， 则所述聚 合端口所属的聚合组端点按照所述指示信息设置所述聚合端口当前承载的所述 多组业务或会话。
12. 根据权利要求 1所述的方法， 其中， 所述方法还包括：
当所述聚合端口所对应的聚合链路发生故障或不可用， 或者， 从所述聚合 链路组脱离时， 所述聚合端口所在的聚合组端点在所述聚合端口当前承载的业 务或会话对应的所述聚合端口序列中， 屏蔽所述聚合链路对应的聚合端口。
13. 根据权利要求 12所述的方法， 其中， 所述方法还包括: 当所述一个或多个聚合端口所对应的聚合链路恢复使用或者重新加入所述 聚合链路组时， 所述聚合组端点确定保护模式；
如果所述保护模式为非反转模式， 则将所述聚合链路对应的聚合端口添加 到所述聚合端口序列中。
14. 根据权利要求 12所述的方法， 其中， 所述方法还包括：
当所述一个或多个聚合端口所对应的聚合链路恢复使用或者重新加入所述 聚合链路组时， 所述聚合组端点确定保护模式；
如果所述保护模式为反转模式， 则在所述聚合端口序列中恢复所述聚合链 路对应的聚合端口。
15. 根据权利要求 14所述的方法， 其中， 所述方法还包括：
如果所述保护模式为反转模式， 则聚合端口序列的变化将触发所述聚合端 口上当前所承载的业务或会话的变化。
16. 根据权利要求 1至 15中任一项所述的方法，其中，所述指示信息为类型长度值 TLV字段。
17. 根据权利要求 1至 15中任一项所述的方法，其中，所述指示信息携带在链路汇 聚控制协议 LACP报文中。
18. 一种链路聚合组中流量路径的协商装置， 包括聚合端口， 以及所述聚合端口所 在的聚合组端点， 其中， 所述聚合端口包括：
指示信息获取模块， 设置为获取指示信息； 其中， 所述指示信息中包括所 述聚合端口所需承载的多组业务或会话， 其中， 每组业务或会话中包括一个或 多个业务或会话；
确定模块， 设置为确定所述聚合端口所需承载的多组业务或会话， 和 /或， 确定当前所承载的业务或会话；
所述聚合组端点包括： 分发模块， 设置为依据各个所述聚合端口当前所承 载的业务或会话进行流量的分发。
19. 根据权利要求 18所述的装置，其中，所述当前所承载的业务或会话是所述多组 业务或会话中优先级最高的一组业务或会话。
20. 根据权利要求 18所述的装置， 其中， 在所述聚合端口所属的聚合组端点中， 每 个所述业务或会话对应一个聚合端口序列， 所述聚合端口序列由所述聚合组端 点中的聚合端口排列构成。
21. 根据权利要求 20所述的装置，其中，依据所述聚合组端点中的每个所述业务或 会话对应一个聚合端口序列， 确定所述聚合端口所需承载的所述多组业务或会 话。
22. 根据权利要求 19所述的装置，其中，所述聚合端口序列中的所述多个聚合端口 按照承载所述业务或会话的优选级进行排序。
23. 根据权利要求 22所述的装置，其中，所述聚合端口所需承载的多组业务或会话 是根据各个聚合端口序列中不同优先级的聚合端口所对应的业务或会话形成 的。
24. 根据权利要求 18所述的装置，其中，所述聚合端口所属的聚合组端点依据预定 策略修改或设置聚合端口所需承载的所述多组业务或会话， 和 /或， 确定当前所 承载的业务或会话。
25. 根据权利要求 18所述的装置， 其中，
所述聚合组端点还包括： 修改模块， 设置为依据所述预定策略修改所述聚 合端口所需承载的所述多组业务或会话；
所述确定模块包括： 确定单元， 设置为根据所述修改模块修改的所述多组 业务或会话， 确定该端口所需承载的多组业务或会话。
26. 根据权利要求 24或 25所述的装置， 其中， 所述修改模块包括： 修改确定单元， 设置为在所述聚合端口当前承载的所述多组业务或会话与 所述指示信息中的业务或会话不一致的情况下， 通过对该聚合组端点的优先级 与对端的聚合端口所属聚合组端点的优先级进行比较， 确定是否需要修改所述 聚合端口当前承载的所述多组业务或会话；
或者，
修改判断单元， 设置为依据主备关系判断是否需要按照所述指示信息修改 所述聚合端口当前承载的所述多组业务或会话。 根据权利要求 26所述的装置， 其中， 所述修改模块还包括: 第一修改单元， 设置为在所述聚合组端点的优先级低于对端的聚合端口所 属的聚合组端点， 或者所述聚合组端点从属于所述对端的聚合端口所属的聚合 组端点的情况下， 按照所述指示信息修改所述聚合端口当前承载的所述多组业 务或会话。
28. 根据权利要求 24所述的装置， 其中， 所述修改模块还包括：
第二修改单元， 设置为在所述聚合端口未形成所述聚合端口当前承载的业 务或会话的情况下， 按照所述指示信息设置所述聚合端口当前承载的所述多组 业务或会话。
29. 根据权利要求 18所述的装置， 其中， 所述聚合组端点还包括：
屏蔽模块， 设置为在所述聚合端口所对应的聚合链路发生故障或不可用， 或者， 从所述聚合链路组脱离的情况下， 在所述聚合端口当前承载的业务或会 话对应的所述聚合端口序列中， 屏蔽所述聚合链路对应的聚合端口。
30. 根据权利要求 29所述的装置， 其中， 所述聚合组端点还包括： 第一模式确定模块， 设置为在所述一个或多个聚合端口所对应的聚合链路 恢复使用或者重新加入所述聚合链路组的情况下， 确定保护模式；
添加模块， 设置为在所述保护模式为非反转模式的情况下， 将所述聚合链 路对应的聚合端口添加到所述聚合端口序列中。
31. 根据权利要求 29所述的装置， 其中， 所述聚合组端点还包括：
第二模式确定模块， 设置为在所述一个或多个聚合端口所对应的聚合链路 恢复使用或者重新加入所述聚合链路组的情况下， 确定保护模式；
恢复模块， 设置为在所述保护模式为反转模式的情况下， 在所述聚合端口 序列中恢复所述聚合链路对应的聚合端口。 根据权利要求 31所述的装置， 其中， 如果所述保护模式为反转模式， 则聚合端 口序列的变化将触发所述聚合端口上当前所承载的业务或会话的变化。
PCT/CN2013/084522 2012-10-19 2013-09-27 链路聚合组中流量路径的协商方法及装置 WO2014059873A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US14/437,051 US9736060B2 (en) 2012-10-19 2013-09-27 Method and device for negotiating traffic path in link aggregation group
EP13847072.9A EP2911353B1 (en) 2012-10-19 2013-09-27 Method and device for flow path negotiation in link aggregation group

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210401321.3 2012-10-19
CN201210401321.3A CN103780511B (zh) 2012-10-19 2012-10-19 链路聚合组中流量路径的协商方法及装置

Publications (1)

Publication Number Publication Date
WO2014059873A1 true WO2014059873A1 (zh) 2014-04-24

Family

ID=50487559

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/084522 WO2014059873A1 (zh) 2012-10-19 2013-09-27 链路聚合组中流量路径的协商方法及装置

Country Status (4)

Country Link
US (1) US9736060B2 (zh)
EP (1) EP2911353B1 (zh)
CN (1) CN103780511B (zh)
WO (1) WO2014059873A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104092604B (zh) * 2014-07-02 2018-02-09 新华三技术有限公司 报文传输控制方法及装置
US20160373294A1 (en) * 2015-06-18 2016-12-22 Fortinet, Inc. Flow management in a link aggregation group system
CN108540380B (zh) 2017-03-02 2021-08-20 华为技术有限公司 多子流网络传输方法及装置
CN108390780B (zh) * 2018-02-11 2021-04-20 北京百度网讯科技有限公司 用于处理信息的方法和装置
US10862794B2 (en) 2019-01-31 2020-12-08 Dell Products L.P. Automated link aggregation group configuration system

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1725761A (zh) * 2005-06-10 2006-01-25 杭州华为三康技术有限公司 网络设备实现链路聚合的方法
CN101014005A (zh) * 2007-01-22 2007-08-08 华为技术有限公司 一种减少链路聚合组中业务损伤的方法和装置
CN101022456A (zh) * 2007-03-22 2007-08-22 华为技术有限公司 一种链路聚合方法、端口负载均衡方法及其装置
CN101605091A (zh) * 2009-02-13 2009-12-16 华为技术有限公司 一种多端口负载分担方法、装置和网络系统

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7155674B2 (en) * 2002-04-29 2006-12-26 Seachange International, Inc. Accessing television services
US8611363B2 (en) * 2002-05-06 2013-12-17 Adtran, Inc. Logical port system and method
US7197038B1 (en) * 2002-10-21 2007-03-27 Sprint Communications Company L.P. Internetwork quality of service provisioning with reciprocal compensation
US7079010B2 (en) * 2004-04-07 2006-07-18 Jerry Champlin System and method for monitoring processes of an information technology system
US7881192B2 (en) * 2006-01-13 2011-02-01 Futurewei Technologies, Inc. System for providing aggregate-rate communication services
EP1921808B1 (en) * 2006-11-10 2014-06-18 Alcatel Lucent Preemptive transmission protection scheme for data services
CN101018228B (zh) * 2006-12-22 2011-11-23 华为技术有限公司 一种端口聚合方法及装置
CN101123510B (zh) * 2007-07-11 2011-03-02 中兴通讯股份有限公司 实现交换机端口隔离的方法、交换机及交换芯片
US8954874B2 (en) * 2007-12-05 2015-02-10 Verizon Patent And Licensing Inc. Methods and systems for providing one or more topic specific portals
CN102752187B (zh) * 2011-04-21 2018-02-13 中兴通讯股份有限公司 弹性网络接口的实现方法和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1725761A (zh) * 2005-06-10 2006-01-25 杭州华为三康技术有限公司 网络设备实现链路聚合的方法
CN101014005A (zh) * 2007-01-22 2007-08-08 华为技术有限公司 一种减少链路聚合组中业务损伤的方法和装置
CN101022456A (zh) * 2007-03-22 2007-08-22 华为技术有限公司 一种链路聚合方法、端口负载均衡方法及其装置
CN101605091A (zh) * 2009-02-13 2009-12-16 华为技术有限公司 一种多端口负载分担方法、装置和网络系统

Also Published As

Publication number Publication date
CN103780511A (zh) 2014-05-07
EP2911353A4 (en) 2015-10-14
EP2911353A1 (en) 2015-08-26
US9736060B2 (en) 2017-08-15
EP2911353B1 (en) 2019-02-27
CN103780511B (zh) 2018-09-28
US20150381474A1 (en) 2015-12-31

Similar Documents

Publication Publication Date Title
CN104488238B (zh) 用于网络环境中集群链路聚合控制的系统和方法
WO2014059867A1 (zh) 链路聚合组中流量路径的协商方法及装置
EP3066784B1 (en) Supporting operator commands in link aggregation group
US8121126B1 (en) Layer two (L2) network access node having data plane MPLS
CN102752187B (zh) 弹性网络接口的实现方法和系统
RU2620995C2 (ru) Способ и система для обновления состояний распределенного отказоустойчивого сетевого межсоединения (drni)
EP2179367B1 (en) Stream reservation protocol for bridged networks
US9614788B2 (en) All delivered network switch
CN103780500B (zh) 聚合组中流量双向同路的方法、装置以及系统
US9565112B2 (en) Load balancing in a link aggregation
CN113824647B (zh) 一种确定组播流的df的方法、设备及系统
WO2013174024A1 (zh) 环形网络的无缝冗余实现方法
CN102469019B (zh) 一种包交换网络中聚合链路带宽的分配方法及装置
WO2014059873A1 (zh) 链路聚合组中流量路径的协商方法及装置
US9787607B2 (en) End-to-end provisioning of Ethernet Virtual Circuits
WO2012159346A1 (zh) 业务负载分配方法、装置和通信系统
WO2012051888A1 (zh) 包交换网络中实现跨节点聚合链路的方法及系统
Alimi Bandwidth management and loop prevention in redundant networks
Budiansyah et al. High Performance Computing

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2013847072

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 14437051

Country of ref document: US