WO2019062249A1 - Procédé et dispositif de configuration, et système de communication pour étiquette de tunnel interne sr-be - Google Patents

Procédé et dispositif de configuration, et système de communication pour étiquette de tunnel interne sr-be Download PDF

Info

Publication number
WO2019062249A1
WO2019062249A1 PCT/CN2018/094240 CN2018094240W WO2019062249A1 WO 2019062249 A1 WO2019062249 A1 WO 2019062249A1 CN 2018094240 W CN2018094240 W CN 2018094240W WO 2019062249 A1 WO2019062249 A1 WO 2019062249A1
Authority
WO
WIPO (PCT)
Prior art keywords
label
tunnel
devices
inner layer
mpls
Prior art date
Application number
PCT/CN2018/094240
Other languages
English (en)
Chinese (zh)
Inventor
胡永健
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2019062249A1 publication Critical patent/WO2019062249A1/fr

Links

Images

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/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H04L45/507—Label distribution
    • 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/16—Multipoint routing
    • 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/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/82—Miscellaneous aspects
    • H04L47/825—Involving tunnels, e.g. MPLS

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a method, a device, and a communication system for configuring an SR-BE inner layer tunnel label.
  • the service data When the service data is transmitted in the network, it usually starts from the source node device, passes through a path composed of links between several intermediate node devices and neighboring intermediate node devices, and transmits to the sink node device, and the sink node device transmits the service data again. Go to the target device.
  • the service data can still reach the target device, and two or more sink node devices can be configured to connect with the target device, and the transmission path of the source node device to each sink node device is configured. Get two or more transmission paths. This configuration is the multi-homing protection of the sink device.
  • Segment Routing Protocol-based segments IGP-based segments
  • SR segment routing
  • SR-BE tunneling technology simplifies the deployment of multi-homing protection. Therefore, the network protection scheme based on the SR-BE tunnel technology configuration is increasingly widespread.
  • SR-BE tunneling technology is an important tunnel bearer technology in the future. In the multi-homing protection scenario based on the SR-BE tunnel, how to configure the inner tunnel label of the SR-BE tunnel to ensure multi-homing protection takes effect is a technology to be solved. problem.
  • the embodiment of the present application provides a method, a device, and a communication system for configuring an inner-layer tunnel label of an SR-BE, so as to solve the problem that the multi-homing protection cannot be effective due to different inner tunnel labels of different sink devices. .
  • the technical solution of the embodiment of the present application is implemented in a scenario of an SR-BE tunnel-based network, where the network includes a first Provider Edge (PE) device, N second PE devices, and a first client side edge ( Customer Edge, CE) device, second CE device.
  • the first CE device is connected to the first PE device, and the second CE device is connected to the N second PE devices.
  • the first CE device and the second CE device belong to the same virtual private network (VPN).
  • the first PE device is a source node device, and the N second PE devices are N sink node devices.
  • the N sink node devices occupy the same Anycast tag.
  • the Anycast tag is used as an outer tunnel tag of the SR-BE tunnel.
  • the Anycast label is a label in a first Multi-Protocol Label Switching (MPLS) label set. Any of the labels included in the first MPLS label set is occupied by at least one of the sink node devices, and N is an integer greater than or equal to 2.
  • MPLS Multi-Protocol Label Switching
  • an embodiment of the present application provides a method for configuring an SR-BE inner layer tunnel label, where the method includes
  • the network management device acquires the MPLS label that is not occupied by the N second PE devices, and obtains a second MPLS label set, where the second MPLS label set does not intersect with the first MPLS label set.
  • the network management device selects an MPLS label as a common inner layer label from the second MPLS label set; wherein the common inner layer label is a label shared by the N second PE devices, and the common inner layer label Used as an inner tunnel label for the SR-BE tunnel.
  • the network management device sends, to the N second PE devices, indication information that carries the common inner layer label, where the N second PE devices occupy the common inner layer label.
  • the network management device sends the public inner layer label to the first PE device.
  • a tunnel label is configured by the network management device for N second PE devices in the network.
  • the network management device can obtain the MPLS label that is not occupied by each second PE device.
  • the N second PE devices respectively allocate unoccupied MPLS labels to the network management device, and the network management device can be used in the unoccupied MPLS label.
  • traversing maintains the usage status of each MPLS label in the network management device, and selects an unoccupied MPLS label therefrom.
  • an MPLS label is selected from the unoccupied MPLS label as a common inner layer label, wherein the common inner layer label is an inner layer label commonly used by the N second PE devices.
  • the network management device configures the management protocol channel, and sends the public inner layer label to the N second PE devices through the management protocol channel. And, the public inner layer label is sent to the first PE device.
  • the network management device configures the same inner layer tunnel label for each second PE device, so that after the service data is switched, the inner layer tunnel label in the data packet and the inner layer of the second PE device after the switching are performed.
  • the tunnel label can be successfully matched to ensure the smooth transmission of service data and ensure the effectiveness of multi-homing protection.
  • the network management device selects a common inner layer label from the unused MPLS labels of the second PE device, which is simple to implement and does not require complicated deployment.
  • the common inner layer label is a Label Switching Path (LSP) label, a Pseudo-Wire (PW) tunnel label, or a virtual private network (VPN). Private network label.
  • LSP Label Switching Path
  • PW Pseudo-Wire
  • VPN virtual private network
  • the N second PE devices When the N second PE devices share an inner tunnel label, the N second PE devices are a service transmission path from the perspective of execution logic.
  • the public inner label is a VPN private network label
  • the N second PE devices share one VPN private network label, and logically, the N second PE devices are connected to the same VPN.
  • the N second PE devices share an inner tunnel label
  • the N second PE devices are a service transmission path from the perspective of execution logic, so the second PE device passes the service transmission data.
  • the transmission data is on the same transmission path, so the effectiveness of multi-homing protection can be guaranteed.
  • the embodiment of the present application further provides a method for configuring an SR-BE inner layer tunnel label, where the method includes:
  • the second PE device receives the indication information sent by the network management device;
  • the indication information carries a common inner layer label, and the public inner layer label is a label shared by the N second PE devices, and the public inner layer a label is used as an inner tunnel label of the SR-BE tunnel;
  • the common inner layer label is an MPLS label selected by the network management device from a second MPLS label set, wherein the second MPLS label set is a set of MPLS labels that are not currently occupied by the N second PE devices, where the second MPLS label set does not intersect with the first MPLS label set;
  • the second PE device occupies the common inner tunnel label according to the indication of the indication information.
  • the second PE device is the execution entity, and corresponding to the implementation method of the first aspect, the N second PE devices respectively receive the common inner layer label through the management protocol channel established by each of the network management devices, and respectively The public inner label is occupied as an inner label.
  • each second PE device can maintain a linear table indexed by an MPLS label, and in the linear table, each entry corresponds to an item, such as a usage status, a label attribute, and an occupied object of the MPLS label.
  • the parameter corresponding to the usage status may indicate whether the label is occupied, and the parameter corresponding to the label attribute may indicate what the label is occupied.
  • the parameter corresponding to the occupied object may be the device identifier occupying the label.
  • any second PE device of the N second PE devices may modify the label state of the label to an inner tunnel label by modifying the usage state parameter of the label to occupy the corresponding parameter. Add your own device ID to the occupied object column to complete the occupation of the public inner tag.
  • the N second PE devices can be bound to be a service transmission path, so that the N second PE devices can successfully match the inner tunnel labels of the data packets, thereby enabling the service data to be enabled. Smooth transmission ensures the effectiveness of multiple protection.
  • the embodiment of the present application further provides a method for configuring an SR-BE inner layer tunnel label, where the method includes:
  • the common inner layer label is an MPLS label selected by the network management device from a second MPLS label set not currently occupied by the N second PE devices, and the second MPLS label The set does not intersect with the first MPLS label set;
  • the first PE device configures the SR-BE tunnel according to the common inner layer label.
  • the method is performed by the first PE device, and corresponding to the implementation method of the first aspect, the first PE device receives the common inner layer label sent by the network management device by using a management protocol channel established with the network management device, and further Tunnels can be established based on common inner label.
  • the first PE device receives the common inner layer label sent by the network management device by using a management protocol channel established with the network management device, and further Tunnels can be established based on common inner label.
  • the embodiment of the present application further provides an apparatus for configuring an SR-BE tunnel label, where the apparatus is disposed in a network management device, and includes a method step for performing the first aspect and the implementation manners of the first aspect. Module.
  • the embodiment of the present application further provides an apparatus for configuring an SR-BE tunnel label, where the apparatus is disposed in each of the second second PE devices, including A module of the method steps of each implementation of the second aspect.
  • the embodiment of the present application further provides an apparatus for configuring an SR-BE tunnel label, where the apparatus is disposed in a first PE device, and includes a method step for performing the implementation manners of the third aspect and the third aspect. Module.
  • an embodiment of the present application provides a network management device, including a transceiver, a processor, and a memory.
  • the transceiver, the processor and the memory can be connected by a bus system.
  • the memory is for storing a program, instruction or code for executing a program, instruction or code in the memory, the first aspect, or the method of any one of the possible aspects of the first aspect.
  • an embodiment of the present application provides a PE device, including a transceiver, a processor, and a memory.
  • the transceiver, the processor and the memory can be connected by a bus system.
  • the memory is for storing a program, instruction or code for executing a program, instruction or code in the memory to perform the method of the second aspect.
  • the embodiment of the present application further provides a PE device, including a transceiver, a processor, and a memory.
  • the transceiver, the processor and the memory can be connected by a bus system.
  • the memory is for storing a program, an instruction or a code
  • the processor is for executing a program, an instruction or a code in the memory to complete the method of the third aspect.
  • the present application provides a computer readable storage medium having instructions stored therein that, when executed on a computer, cause the computer to perform the first aspect, the second aspect, and the third aspect Or the method of any possible design in the first aspect.
  • the present application provides a communication system comprising the network device of the seventh aspect, and the PE device of the eighth aspect and the ninth aspect.
  • the network management device acquires an MPLS label that is not occupied by each sink node device, and selects one of the unoccupied MPLS labels as all the sink nodes.
  • the inner tunnel label shared by the device, so that the inner tunnel labels of all the sink devices in the network are all the same, even if the service data packet is switched in the middle of the transmission, and the service data packet is transmitted to the switched sink device.
  • the inner tunnel label can still be correctly matched with the inner tunnel label of the switched sink node device, so that the transmission can be smoothly performed, thereby ensuring multi-homing protection effectiveness.
  • FIG. 1 is a schematic diagram of a transmission path of an SR-BE dual-homing protection network according to an embodiment of the present application
  • FIG. 2 is a schematic diagram of a label encapsulation structure based on an SR-BE tunnel provided by an embodiment of the present application;
  • FIG. 3 is a schematic diagram of an implementation scenario of the solution provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of signaling interaction of a method for configuring an SR-BE inner layer tunnel label according to an embodiment of the present application
  • FIG. 5 is a schematic structural diagram of a label stack package provided according to FIG. 3 according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of signaling interaction of an optional configuration method of an SR-BE inner layer tunnel label according to an embodiment of the present application
  • FIG. 7 is a schematic structural diagram of a virtual device of a network management device according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a physical device of a network management device according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a virtual device of a second PE device according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a physical device of a second PE device according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a virtual device of a first PE device according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a physical device of a first PE device according to an embodiment of the present application.
  • the embodiments of the present application refer to "first" and “second” and the like to distinguish a plurality of objects, and are not used to define the order of the plurality of objects.
  • the SR-BE multi-homing protection scenario and the label encapsulation structure of the SR-BE tunnel in the embodiments of the present application are exemplarily described below with reference to FIG. 1 and FIG. It will be understood by those skilled in the art that the exemplary description in FIG. 1 is only for the dual-homing scenario, and should not be construed as limiting the present application.
  • Figure 1 is a transmission path diagram of an SR-BE dual-homing protection network.
  • CE1 can transmit service data to CE2 through two transmission paths.
  • the sink node device PE2 and the sink node device PE3 are connected to the target device CE2.
  • the source node device PE1 forms a path via the intermediate node device P1 and the sink node device PE2, and the source node device PE1 forms another path via the intermediate node device P2 and the sink node device PE3. It is assumed that the default transmission path of the service data is from the source node device PE1 to the sink node device PE2 via the intermediate node device P1.
  • the entry of the sink node device PE2 fails, then when the service data is transmitted to the intermediate node device P1, it is forwarded by the intermediate node device P1 to the intermediate node device P2 and transmitted to the sink node device PE3 via the intermediate node device P2.
  • the application of the SR technology to the traditional dual-homing protection scenario shown in FIG. 1 can effectively simplify the tunneling technology, and can control the traffic path arbitrarily by performing label operation on the packets of the source node, thereby implementing traffic tuning, and
  • the SR can perform arbitrary protection of the local node based on, for example, Topology Independent Loop-free Alternate Fast Re-route (TI-LFA), which improves the reliability of message transmission.
  • TI-LFA Topology Independent Loop-free Alternate Fast Re-route
  • the SR tunneling technology is an MPLS technology implemented based on the Interior Gateway Protocol (IGP) extension.
  • the Segment is essentially an MPLS label, the Routing indicates a route, and the MPLS label is a fragment identifier of the corresponding route, and is therefore defined as Segment of Routing, referred to as Segment Routing (SR).
  • the implementation modes of the SR include, but are not limited to, a Segment Routing Traffic Engineering (SR-TE) mode and an SR-BE mode.
  • the service forwarding path is marked by setting an outer tunnel label and an inner tunnel label.
  • the Anycast label is used to identify the MPLS label of the IGP route of a group (multiple) nodes.
  • PE2 and PE3 are logically used as a node group, and the Anycast label lable F is used to identify the MPLS label of the IGP route that reaches the node group, that is, at the source node PE1, the Anycast label operation of the packet can be controlled.
  • the packet forwarding path to the node group including the sink nodes PE2 and PE3.
  • the inner tunnel label is used to guide the service forwarding.
  • the inner tunnel label is a virtual private network (VPN) label (also referred to as a VPN private network label)
  • the sink node forwards the packet to the VPN label according to the indication of the VPN label.
  • the identified VPN when the multi-homing protection is configured based on the SR-BE tunneling technology, the configuration related to the intermediate path and the path switching can be simplified, and only the outer tunnel label indicating the source node device to the sink node device and the indication sink node device are configured.
  • the inner tunnel label for service forwarding is sufficient. Therefore, multi-homing protection based on SR-BE technology is widely used.
  • the inner tunnel label configuration requirement is that the downstream node device diffuses the inner tunnel label to the upstream node device, and the inner tunnel label of the sink node device is used by the sink node device itself. Configuration, therefore, the inner tunnel labels configured by each sink node device in the multi-homing protection network are different from each other.
  • the inner tunnel labels configured by the sink node devices PE2 and PE3 are different, and when the data packets of the service data are transmitted, the default transmission path is the path where the sink node device PE2 is located, so the data packet is The inner tunnel label is the inner tunnel label of the sink node device PE2, and when the entrance of the sink node device PE2 fails, the transport service needs to be switched to the path where the sink node device PE3 is located.
  • the internal tunnel label of the data packet does not match the inner tunnel label of the sink node PE3, so that the sink node PE3 cannot continue to transmit service data, which in turn causes more The protection cannot take effect.
  • FIG. 2 is a schematic diagram of a label encapsulation structure based on an SR-BE tunnel according to an embodiment of the present disclosure, where an outer tunnel label is an Anycast label, and the dual-homing protection path shown in FIG. 1 is used.
  • the sink node device PE2 and the sink node device PE3 are bound and virtualized into a cluster, and then a public outer tunnel label assigned to the cluster.
  • the Anycast label is allocated to the sink node devices PE2 and PE3 based on the IGP, and then the sink node device PE2 advertises the Anycast label to the intermediate node device P1, and the sink node device PE3 advertises the Anycast label to the intermediate node device P2 until the source node device PE1, and the source node device PE1 can calculate the shortest transmission path of the data packet in the transmission network according to the Anycast label, for example, the path formed by the source node device PE1, the intermediate node device P1, and the sink node device PE2.
  • the sink node PE2 and the sink node PE3 When configuring the inner tunnel label, the sink node PE2 and the sink node PE3 respectively select an MPLS label as their inner tunnel label from their own MPLS labels, and respectively advertise their inner tunnel labels to the source node.
  • Equipment PE1 After the source node device PE1 receives the inner tunnel label of the sink node device PE2 and the sink node device PE3, since the sink node device of the determined forwarding path is PE2, when the data packet is transmitted to the sink node device PE2, the sink node device The PE2 needs to continue to transmit service data according to the service path indicated by the inner tunnel label. Therefore, the inner tunnel label of the PE2 is pushed into the label stack, and the label encapsulation structure diagram based on the SR-BE tunnel shown in FIG. 2 is obtained.
  • the source node device PE1 transmits a data packet
  • the data packet is transmitted to the intermediate node device P1 according to the determined next hop node device indicated by the shortest transmission path, and the intermediate node
  • the device P1 strips the outer tunnel label of the label stack and pushes it into the outer tunnel label of the intermediate node device P1.
  • the outer tunnel label of P1 is also an Anycast label.
  • the next hop node device is the sink node device PE2, so that it can detect whether the entry of the sink node device PE2 is faulty, and when the entry of the sink node device PE2 fails, the intermediate node device P1 recalculates the shortest transmission path, and learns that the data packet is transmitted from the intermediate node device P2 to the sink node device PE3 as the shortest transmission path, and then the transmission interface is modified to be transmitted to the interface of the intermediate node device P2, and passes through the intermediate node device. P2 transmits the data message to the sink node device PE3.
  • the intermediate node device P2 strips the Anycast label corresponding to P1 in the label stack, and pushes the Anycast label corresponding to P2.
  • the sink device PE3 strips the Anycast label of the label stack, reads the inner tunnel label, and matches the inner tunnel label set by itself.
  • the sink node device PE3 matches the read inner tunnel label and the inner tunnel label set by itself, and is substantially determined to read.
  • the service transmission path corresponding to the inner tunnel label is the same as the service transmission path set by itself. If the two transmission paths are the same, the transmission path can be entered to continue to transmit service data.
  • the internal tunnel label read by the sink node device PE3 is the inner tunnel label set by the sink node device PE2, that is, the service transmission path set by the PE2 does not match the service transmission path set by the sink node device PE3. Therefore, the sink node device PE3 cannot continue to transmit service data at all. It can be seen that the existing inner layer tunnel label generation method will cause the multi-homing protection to be invalid. In view of this, the technical solutions of the embodiments of the present application are proposed by those skilled in the art.
  • the solution of the present application is applied to the network of the SR-BE tunnel, where the network of the SR-BE tunnel includes the first PE device, the N second PE devices, the first CE device, and the second CE device, specifically, the first CE.
  • the device is connected to the first PE device, and the second CE device is connected to the N second PE devices.
  • the first CE device and the second CE device belong to the same VPN, and the first PE device is the source node device and the N second PE devices.
  • the device is N sink devices, and the outer tunnel labels of the N second PE devices are the same Anycast label.
  • the Anycast label is used as an outer tunnel label of the SR-BE tunnel, and the Anycast label is a label in a first multi-protocol label switching MPLS label set, and any label included in the first MPLS label set is at least one The sink node device is occupied, where N is an integer greater than or equal to 2.
  • the method provided by the embodiment of the present application is specifically described below with reference to FIG. 3 to FIG. 6 .
  • FIG. 3 is a schematic diagram of an implementation scenario of the solution provided by an embodiment of the present application.
  • the first PE device in the present application may be, for example, the PE 30 shown in FIG. 3
  • the first CE device may be, for example, the CE 31 shown in FIG. 3
  • the N second PE devices may be, for example, the PE 31 shown in FIG. 3 .
  • PE32 to PE3N the second CE device may be, for example, the CE32 shown in FIG.
  • the CE 31 sends the service data to the CE32.
  • the network management device described in this application may be, for example, a network management system or an SDN controller, or other dedicated device capable of centralized management or control.
  • the PE30 is the source node device of the network, and the N second PE devices PE31 to PE3N are N sink node devices of the network, and the same Anycast label is configured.
  • the node device P31 to the node device P3N are the intermediate node devices of the network.
  • the first CE device CE31 is connected to the first PE device PE30, and the second CE device CE32 is connected to the N second PE devices PE31 to PE3N.
  • the network management device configures the same inner layer tunnel label to the second PE device PE31 to the PE3N, so that the service data packet can be smoothly transmitted even if the service data packet is switched in the middle of the transmission, thereby ensuring more Protected by effectiveness.
  • the data interaction between the network management device and each second PE device in the network is basically the same when the solution is executed.
  • N second PE devices are used.
  • a second PE device is taken as an example to describe the execution process of the solution.
  • FIG. 4 is a signaling interaction diagram of a method for configuring an SR-BE inner layer tunnel label according to an embodiment of the present application.
  • This embodiment provides a method 500, including:
  • the network management device acquires an MPLS label that is not occupied by the second PE device, and obtains a second MPLS label set, where the first MPLS label set and the second MPLS label set do not intersect.
  • the network management device selects an MPLS label from the second MPLS label set as a common inner layer label.
  • the network management device sends the indication information to the second PE device.
  • the second PE device occupies a common inner layer label in response to the indication information.
  • the network management device sends the public inner layer label to the first PE device of the network.
  • the first PE device configures a tunnel according to a common inner layer label.
  • the common inner layer label refers to a label shared by the N second PE devices of the network device, and the common inner layer label is used as an inner tunnel label of the SR-BE tunnel, and is used as a public
  • the MPLS label of the layer label can be an LSP label, a PW tunnel label, or a VPN private network label.
  • the N second PE devices are a service transmission path from the perspective of execution logic.
  • the public inner layer label is a VPN private network label
  • the N second PE devices share a VPN private network label, which is used to identify the same VPN. Logically, the N second PE devices are connected to the same VPN.
  • each PE device can maintain a linear table indexed by an MPLS label, and in the linear table, each entry corresponds to an item such as a usage status, a label attribute, and an occupied object of the MPLS label.
  • the parameter corresponding to the usage status may indicate whether the label is occupied, and the parameter corresponding to the label attribute may indicate what the label is occupied.
  • the parameter corresponding to the occupied object may be the device identifier occupying the label. Based on this, when the MPLS label of the public inner layer label is occupied, the usage status parameter of the label can be modified to occupy the corresponding parameter, and the label attribute of the label is modified into an inner tunnel label, and the label is occupied.
  • the object is added as the device identifier of the N second PE devices.
  • the structure and content of the MPLS label are relatively mature technologies in the field, and the embodiments of the present application are not detailed herein.
  • each second PE device is configured with multiple MPLS labels, and based on the characteristics of the MPLS label, which MPLS label of the multiple MPLS labels is already occupied, and which MPLS label is currently not occupied, can be read by corresponding
  • the usage status of the MPLS label is known.
  • the MPLS label of each second PE device can be maintained in the corresponding sink device, it can also be maintained in the network management device. Therefore, in this embodiment, the network management device does not currently occupy the MPLS label from the second PE device.
  • Centrally determining the common inner layer label may include, but is not limited to, the following two embodiments.
  • the network management device may send an acquisition request to the N second PE devices to obtain an MPLS label that is not currently occupied by each second PE device, and further, N The second PE device allocates an unoccupied MPLS label to the network management device, and the network management device can select an MPLS label from the unoccupied MPLS label as a common inner label.
  • Manner 2 When the MPLS label is maintained in the network management device, the network management device can traverse the usage status of each MPLS label, select an unoccupied MPLS label, and further select from the unoccupied MPLS label.
  • An MPLS label acts as a public inner label.
  • the network management device may randomly select an MPLS label as a common inner layer label, which is not limited in this embodiment.
  • the MPLS label of the N second PE devices in FIG. 3 is specifically a VPN private network label
  • the second PE device PE31 maintains a VPN private network label VPN1, a VPN private network label VPN2, and a VPN private network label.
  • VPN3 and the second PE device PE31 already occupies the VPN private network label VPN1 and the VPN private network label VPN3.
  • the second PE device PE32 maintains the VPN private network label VPN4, the VPN private network label VPN5 and the VPN private network label VPN6, and the second PE device PE32 has occupied the VPN private network label VPN4, and so on, and obtains the second PE device.
  • the VPN private network label VPN 10, the VPN private network label VPN 11 and the VPN private network label VPN 12 are maintained in the PE3N, and the second PE device PE3N has occupied the VPN private network label VPN 12. Then, the network management device may send a request for acquiring the unoccupied VPN private network label to the second PE device PE31, the PE32, and the second PE device PE3N, and the second PE device PE31 allocates the VPN private network label VPN2 to the network management in response to the request.
  • the second PE device PE32 allocates the VPN private network label VPN5 and the VPN private network label VPN6 to the network management device in response to the request
  • the second PE device PE3N allocates the VPN private network label VPN 10 and the VPN private network label VPN 11 to the request in response to the request.
  • the network management device randomly selects a VPN private network label as a public inner tunnel from the VPN private network label VPN2, the VPN private network label VPN5, the VPN private network label VPN6, the VPN private network label VPN10, and the VPN private network label VPN11.
  • the label for example, the VPN private network label VPN6, then configures the second PE device PE31 to the second PE device PE3N to occupy the VPN private network label VPN6.
  • the indication information may be generated, and the public inner layer label is carried in the indication information and sent to the N second PE devices.
  • the network management device can communicate with the N second PE devices through the N management protocol channels, and send the indication information to the N second PE devices through the N management protocol channels.
  • the management protocol channel may be based on, for example, an OpenFlow protocol, a Path Computation Element Protocol (PCEP), or an extended command added by a Network Configuration (NetConf) protocol.
  • a private type-length-value may be newly defined based on the OpenFlow, and an object is added to the PCEP message or a command word is added in the NetConf to carry the indication information.
  • the network management device After transmitting the indication information to the N second PE devices, the network management device sends the public inner layer label to the first PE device to instruct the first PE device to establish an SR-BE tunnel.
  • the network management device configures the same inner tunnel label for each second PE device, so that after the service data is switched, the inner tunnel label in the data packet and the second PE device after the switching are performed.
  • the layer tunnel label can be successfully matched to ensure the smooth transmission of service data and ensure the effectiveness of multi-homing protection.
  • the network management device selects a common inner layer label from the unused MPLS labels of the second PE device, which is simple to implement and does not require complicated deployment.
  • An inner tunnel label configuration method 600 includes:
  • the SDN controller selects one VPN private network label from the second PE device PE31 to the second private device tunnel label of the second PE device PE3 to the second PE device PE3N. For example, the VPN private network label 1030.
  • the SDN controller sends N messages 1 to the N second PE devices, where each message 1 carries the determined common inner tunnel label.
  • the message 1 can for example be an extended open message.
  • the determined common inner layer tunnel label is sent to the second PE device PE31 to the second PE device PE3N, respectively, by newly defining a type length value TLV field in the open message.
  • the type T field in the TLV field is used to indicate that the TLV field carries the common inner layer tunnel label of the SR-BE tunnel, and indicates that each second PE device occupies the common inner layer tunnel label; the TLV field
  • the length L field is used to identify the length of the information carried in the V field; the value V field in the TLV field is used to carry the common inner layer tunnel label.
  • the N second PE devices respectively occupy the public inner tunnel label determined by the foregoing, for example, the VPN private network label 1030.
  • the second PE device PE31 to the second PE device PE3N respectively modify the usage state parameter of the VPN private network label 1030 to be occupied in the linear table, and mark the label attribute as a private network label, and occupy the object identifier.
  • the device identification of the second PE device PE31 to the second PE device PE3N indicates that the VPN label has been occupied by the second PE device PE31 to the second PE device PE3N as private network labels.
  • the SDN controller sends the public inner tunnel label to the first PE device, for example, the PE30.
  • the SDN controller may send the VPN private network label 1030 to the first PE device PE30 in an advertised manner.
  • the first PE device PE30 may calculate a shortest transmission path according to the identifier of the Anycast label 1001, where the shortest transmission path is the path with the least number of forwarding node devices, for example, the path 301. Further, the first PE device PE30 configures the label stack according to the outer tunnel label of the path 301, the Anycast label 1001, and the inner tunnel label of the sink node device PE31 of the path 301, and the label stack is configured to obtain the label stack.
  • Tag stack package structure diagram is a shortest transmission path according to the identifier of the Anycast label 1001, where the shortest transmission path is the path with the least number of forwarding node devices, for example, the path 301. Further, the first PE device PE30 configures the label stack according to the outer tunnel label of the path 301, the Anycast label 1001, and the inner tunnel label of the sink node device PE31 of the path 301, and the label stack is configured to obtain the label stack.
  • the service data of the first CE device CE31 is transmitted to the first CE device CE32.
  • the first PE device PE30 will be as shown in FIG.
  • the label data stack and the service data configuration of the first CE device CE31 form a data packet, and the data packet is transmitted through the path 301.
  • the PE 30 transmits the data packet to the intermediate node device P31 according to the path 301, and the P31 strips the Anycast label 1001 that is pushed in by the PE30, and pushes the Anycast label 1001 corresponding to the P31, and further, according to the indication of 1001 corresponding to P31, It is known that the next hop node is the second PE device PE31, so that it can detect whether the entry of the second PE device PE31 is faulty before the transmission. If the portal of the second PE device PE31 is running normally, the intermediate node device P31 will send the data packet.
  • the intermediate node device P31 recalculates a shortest transmission path and switches to the re-determined shortest transmission path.
  • the shortest path determined by the intermediate node device P31 is the path 302.
  • the intermediate node device P31 transmits the data packet to the intermediate node device P32 of the path 302, and the P32 strips the Anycast tag 1001 corresponding to the P31, and presses the 1001 corresponding to the P32.
  • the data packet is transmitted to the second PE device PE32, and finally, the data packet is transmitted to the second CE device CE32.
  • the outer tunnel label Anycast label 1001 is stripped, and the inner tunnel label VPN private network label 1030 is read. Since the VPNS private network label of the second PE device PE31 to the second PE device PE3N is 1030, the second PE device PE31 to the second PE device PE3N are connected to one VPN, that is, the second PE device PE31 to the first The PEs of the PEs can enter their own service transmission path according to the VPNS private network label 1030. Therefore, the data packet is transmitted by the second PE device PE31 to any of the second PE devices PE3N, and the private network label can be successfully matched, and then the corresponding transmission path is continued to be transmitted.
  • FIG. 5 and FIG. 6 is only an optional embodiment of the present application, and any extensions and modifications based on FIG. 5 and FIG. 6 belong to the protection scope of the embodiment of the present application.
  • the network management device selects one of the unoccupied MPLS labels as the inner tunnel label of all the second PE devices, so that the deployment is not increased.
  • the multi-homing protection network is deployed, and the inner tunnel labels of all the second PE devices are set to be the same, and the inner tunnel label of the data packet and the inner tunnel label of any second PE device can be guaranteed.
  • the matching is correct, so that it can be transmitted smoothly, ensuring the effectiveness of multi-homing protection.
  • FIG. 7 is a schematic diagram of a network management device 700 according to an embodiment of the present application.
  • the network management device 700 can be applied to the scenario shown in FIG. 3 for performing the method corresponding to FIG.
  • the network management device 700 includes a processing module 701 and a transceiver module 702.
  • the transceiver module 702 is specifically configured to perform various types of information transmission and reception performed by the network device in the foregoing method 500.
  • the processing module 701 is specifically configured to perform other processing in addition to information transmission and reception of the network device in the foregoing method 500.
  • the processing module 701 may be configured to obtain a multi-protocol label switching MPLS label that is not currently occupied by the N second PE devices, obtain an MPLS label set, and select an MPLS label from the MPLS label set as a common inner label.
  • the transceiver module 702 can be configured to separately send, to the N second PE devices, first indication information indication information that carries the common inner layer label.
  • the transceiver module 702 can be implemented by a transceiver
  • the processing module 701 can be implemented by a processor.
  • the network management device 700 can include a processor 801, a transceiver 802, and a memory 803.
  • the memory 803 can be used to store a program/code pre-installed when the network management device 700 is shipped from the factory, and can also store code for execution of the processor 801 and the like.
  • the network management device 700 may correspond to the network device in the method 500 according to the embodiment of the present application, where the transceiver 802 is configured to perform various information transceiving performed by the network device in the method 500,
  • the processor 801 is configured to perform other processing in addition to information transceiving of the network device in the method 500. I will not repeat them here.
  • FIG. 9 is a schematic diagram of a PE device 900 provided by an embodiment of the present application.
  • the PE device 900 can be applied to the scenario shown in FIG. 3 as a second PE device for performing the method corresponding to FIG. 4.
  • the PE device 900 includes a processing module 901 and a transceiver module 902.
  • the transceiver module 902 is specifically configured to perform various information transmission and reception performed by the second PE device in the foregoing method 500.
  • the processing module 901 is specifically configured to execute the second PE device in the method 500, except for information transmission and reception. Other processing.
  • the transceiver module 902 can be configured to receive indication information sent by the network management device, where the indication information carries a common inner layer label.
  • the processing module 901 can be configured to occupy the public inner tunnel label according to the indication of the indication information.
  • the transceiver module 902 can be implemented by a transceiver
  • the processing module 901 can be implemented by a processor.
  • PE device 900 can include a processor 1001, a transceiver 1002, and a memory 1003.
  • the memory 1003 may be used to store a program/code pre-installed by the PE device 900 at the time of shipment, or may store a code or the like for execution of the processor 1001.
  • the PE device 900 may correspond to the second PE device in the method 500 according to the embodiment of the present application, where the transceiver 1002 is configured to perform various functions performed by the second PE device in the method 500.
  • the information is transmitted and received by the processor 1001 to perform processing other than information transmission and reception of the second PE device in the method 500. I will not repeat them here.
  • FIG. 11 is a schematic diagram of a PE device 1100 according to an embodiment of the present application.
  • the PE device 1100 can be applied to the scenario shown in FIG. 3 as the first PE device for performing the method corresponding to FIG. 4.
  • the PE device 1100 includes a processing module 1101 and a transceiver module 1102.
  • the transceiver module 1102 is specifically configured to perform various information transmission and reception performed by the first PE device in the foregoing method 500.
  • the processing module 1101 is specifically configured to execute the first PE device in the method 500 except for information transmission and reception. Other processing.
  • the transceiver module 1102 can be configured to receive a common inner layer tag advertised by the network management device.
  • the processing module 1101 can be configured to configure a tunnel according to the common inner layer label.
  • the transceiver module 1102 can be implemented by a transceiver
  • the processing module 1101 can be implemented by a processor.
  • the PE device 1100 can include a processor 1201, a transceiver 1202, and a memory 1203.
  • the memory 1203 may be used to store a program/code pre-installed when the PE device 1100 is shipped from the factory, or may store a code or the like for execution of the processor 1201.
  • the PE device 1100 may correspond to the first PE device in the method 500 according to an embodiment of the present application, wherein the transceiver 1202 is configured to perform various functions performed by the first PE device in the method 500.
  • the information is transmitted and received by the processor 1201 for performing processing other than information transmission and reception of the first PE device in the method 500. I will not repeat them here.
  • the embodiment of the present application provides a communication system.
  • the communication system includes a network management device, a first PE device, and N second PE devices.
  • the network management device may be the network management device provided by the embodiment corresponding to FIG. 7 or FIG. 8.
  • the first PE device may be the first PE device provided by the embodiment corresponding to FIG. 11 or FIG. 12, and the second The PE device may be the second PE device provided by the embodiment corresponding to FIG. 9 or FIG. 10.
  • the communication system is for performing the method 500 or method 600 of the embodiment corresponding to FIGS. 4 and 6.
  • the network storage device, the first PE device, and the second PE device are respectively provided by the embodiment of the present application, where the computer storage medium is separately provided, wherein the computer storage medium is stored in any device, and the program is executed.
  • the storage medium in any device may be a magnetic disk, an optical disk, a read-only memory (English: read-only memory, or ROM) or a random access memory (English: random access memory, RAM for short).
  • the transceiver may be a wired transceiver, a wireless transceiver, or a combination thereof.
  • the wired transceiver can be, for example, an Ethernet interface.
  • the Ethernet interface can be an optical interface, an electrical interface, or a combination thereof.
  • the wireless transceiver can be, for example, a wireless local area network transceiver, a cellular network transceiver, or a combination thereof.
  • the processor can be a central processing unit (English: central processing unit, abbreviated: CPU), a network processor (English: network processor, abbreviated: NP) or a combination of CPU and NP.
  • the processor may further include a hardware chip.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (abbreviated as PLD), or a combination thereof.
  • the above PLD can be a complex programmable logic device (English: complex programmable logic device, abbreviation: CPLD), field-programmable gate array (English: field-programmable gate array, abbreviation: FPGA), general array logic (English: generic array Logic, abbreviation: GAL) or any combination thereof.
  • the memory may include a volatile memory (English: volatile memory), such as random access memory (English: random-access memory, abbreviation: RAM); the memory may also include non-volatile memory (English: non-volatile memory).
  • read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviation: HDD) or solid state drive (English: solid-state drive, Abbreviation: SSD); the memory may also include a combination of the above types of memory.
  • the 8 , 10 and 12 may also include a bus interface, which may include any number of interconnected buses and bridges, in particular various circuit links of memory represented by one or more processors and memories represented by the processor Together.
  • the bus interface can also link various other circuits, such as peripherals, voltage regulators, and power management circuits, as is known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • the transceiver provides a unit for communicating with various other devices on a transmission medium.
  • the processor is responsible for managing the bus architecture and the usual processing, and the memory can store the data that the processor uses when performing operations.
  • a general purpose processor may be a microprocessor.
  • the general purpose processor may be any conventional processor, controller, microcontroller, or state machine.
  • the processor may also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration. achieve.
  • the steps of the method or algorithm described in the embodiments of the present application may be directly embedded in hardware, a software unit executed by a processor, or a combination of the two.
  • the software unit can be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium in the art.
  • the storage medium can be coupled to the processor such that the processor can read information from the storage medium and can write information to the storage medium.
  • the storage medium can also be integrated into the processor.
  • the processor and the storage medium may be disposed in an ASIC, and the ASIC may be disposed in the UE. Alternatively, the processor and the storage medium may also be located in different components in the UE.
  • the size of the sequence number of each process does not mean the order of execution sequence, and the order of execution of each process should be determined by its function and internal logic, and should not be taken by the embodiment of the present application.
  • the implementation process constitutes any qualification.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).

Landscapes

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

Abstract

Les modes de réalisation de la présente invention concernent un procédé et un dispositif de configuration,, et un système de communication, pour une étiquette de tunnel interne SR-BE (routage de segment au mieux). Le procédé est utilisé dans un réseau sur la base d'un tunnel SR-BE. Selon le procédé, un dispositif de gestion de réseau : obtient des étiquettes de commutation multiprotocole par étiquette (MPLS) qui ne sont pas occupées actuellement par N seconds dispositifs de bord fournisseur (PE), pour obtenir un ensemble d'étiquettes MPLS, et sélectionne une étiquette MPLS de l'ensemble d'étiquettes MPLS en tant que l'étiquette de couche interne commune ; et envoie des informations d'indication contenant l'étiquette de couche interne commune aux N seconds dispositifs PE respectivement de sorte à signifier que les N seconds dispositifs PE occupent l'étiquette de couche interne commune. Selon la solution technique décrite dans les modes de réalisation de la présente invention, les étiquettes de tunnel interne de tous les seconds dispositifs PE dans le réseau sont identiques, et même si un message de données de service commute des chemins durant la transmission, le message de données de service peut être transmis sans à-coups, ce qui garantit l'efficacité d'une protection multi-retour.
PCT/CN2018/094240 2017-09-28 2018-07-03 Procédé et dispositif de configuration, et système de communication pour étiquette de tunnel interne sr-be WO2019062249A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710897059.9A CN109587059B (zh) 2017-09-28 2017-09-28 Sr-be内层隧道标签的配置方法、设备及通信系统
CN201710897059.9 2017-09-28

Publications (1)

Publication Number Publication Date
WO2019062249A1 true WO2019062249A1 (fr) 2019-04-04

Family

ID=65900478

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/094240 WO2019062249A1 (fr) 2017-09-28 2018-07-03 Procédé et dispositif de configuration, et système de communication pour étiquette de tunnel interne sr-be

Country Status (2)

Country Link
CN (1) CN109587059B (fr)
WO (1) WO2019062249A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111865784A (zh) * 2020-06-17 2020-10-30 烽火通信科技股份有限公司 一种sr网络的路由可视化方法及系统
WO2021109997A1 (fr) * 2019-12-05 2021-06-10 中兴通讯股份有限公司 Procédé et dispositif anti-rupture de fibre pour tunnel de routage de segment, nœud d'entrée et support de données
US20230388228A1 (en) * 2021-02-09 2023-11-30 Huawei Technologies Co., Ltd. Packet forwarding method and device, and system

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110120914B (zh) * 2019-05-13 2021-10-12 广西电网有限责任公司 一种基于sr-te隧道的节点保护方法和本地修复节点
CN110519168B (zh) * 2019-08-27 2022-03-11 北京华为数字技术有限公司 一种创建srte隧道的方法及相关设备
CN112583650B (zh) * 2019-09-27 2022-06-10 烽火通信科技股份有限公司 一种spn中sr-be隧道链路检测方法及系统
TWI802481B (zh) * 2022-08-04 2023-05-11 中華電信股份有限公司 配置路由器的任播標籤的電子裝置及方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103312611A (zh) * 2013-06-03 2013-09-18 华为技术有限公司 报文处理方法、设备标签处理方法及设备
CN103888356A (zh) * 2014-04-12 2014-06-25 何顺民 Vpls实现方法、系统和提供商边缘设备
US20140286336A1 (en) * 2013-03-25 2014-09-25 Dell Products, Lp System and Method for Paging Flow Entries in a Flow-Based Switching Device
CN105591800A (zh) * 2015-07-29 2016-05-18 杭州华三通信技术有限公司 流量保护方法及装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9832115B2 (en) * 2014-10-29 2017-11-28 Cisco Technology, Inc. Label-switched packets with device-independent labels
US10069639B2 (en) * 2015-07-28 2018-09-04 Ciena Corporation Multicast systems and methods for segment routing

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140286336A1 (en) * 2013-03-25 2014-09-25 Dell Products, Lp System and Method for Paging Flow Entries in a Flow-Based Switching Device
CN103312611A (zh) * 2013-06-03 2013-09-18 华为技术有限公司 报文处理方法、设备标签处理方法及设备
CN103888356A (zh) * 2014-04-12 2014-06-25 何顺民 Vpls实现方法、系统和提供商边缘设备
CN105591800A (zh) * 2015-07-29 2016-05-18 杭州华三通信技术有限公司 流量保护方法及装置

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021109997A1 (fr) * 2019-12-05 2021-06-10 中兴通讯股份有限公司 Procédé et dispositif anti-rupture de fibre pour tunnel de routage de segment, nœud d'entrée et support de données
CN111865784A (zh) * 2020-06-17 2020-10-30 烽火通信科技股份有限公司 一种sr网络的路由可视化方法及系统
CN111865784B (zh) * 2020-06-17 2022-06-07 烽火通信科技股份有限公司 一种sr网络的路由可视化方法及系统
US20230388228A1 (en) * 2021-02-09 2023-11-30 Huawei Technologies Co., Ltd. Packet forwarding method and device, and system

Also Published As

Publication number Publication date
CN109587059B (zh) 2021-07-09
CN109587059A (zh) 2019-04-05

Similar Documents

Publication Publication Date Title
US11533249B2 (en) Route processing method and apparatus, and data transmission method and apparatus
WO2019062249A1 (fr) Procédé et dispositif de configuration, et système de communication pour étiquette de tunnel interne sr-be
JP7419510B2 (ja) Ｂｉｅｒ転送項目構築方法、装置、およびシステム
CN111510379B (zh) Evpn报文处理方法、设备及系统
CN108574630B (zh) Evpn报文处理方法、设备及系统
CN110912796B (zh) 一种通信方法、设备和系统
WO2021258754A1 (fr) Procédé et appareil d'indication de message, ainsi que dispositif et support de stockage
WO2015165311A1 (fr) Procédé permettant de transmettre un paquet de données et dispositif côté fournisseur
US20160277279A1 (en) Link discovery method, system, and device
CN111698152B (zh) 一种故障保护方法、节点及存储介质
WO2015144018A1 (fr) Procédé de transmission d'informations, dispositif et système de communication
CN112887139B (zh) 报文处理方法及装置
WO2021088561A1 (fr) Procédé, dispositif et équipement de partage de charge dans un réseau de reproduction explicite à indice d'élément binaire
CN106789540B (zh) 一种网关部署方法和装置
WO2021073357A1 (fr) Procédé, dispositif, système et appareil de traitement de paquets, et support de stockage
CN114598635A (zh) 报文传输的方法和装置
WO2022017225A1 (fr) Procédé, dispositif et système d'envoi de message
CN117478503A (zh) 一种组播配置方法及装置
WO2022048469A1 (fr) Procédé, dispositif et système de mise à jour d'un routage mac
EP4054149A1 (fr) Procédé et appareil permettant de configurer le temps de vieillissement d'une adresse de commande d'accès au support (mac)
CN111435948B (zh) 一种在网络中传输报文的方法及网络设备
US9444728B2 (en) Packet switching device including cascaded aggregation nodes
CN107947989B (zh) 动态ac生成方法及装置
CN113132222B (zh) 报文转发方法、设备及计算机可读存储介质
WO2021077972A1 (fr) Procédé de transfert de paquet, dispositif, et support de stockage

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18863081

Country of ref document: EP

Kind code of ref document: A1