WO2018090210A1 - 业务报文传输方法及节点设备 - Google Patents

业务报文传输方法及节点设备 Download PDF

Info

Publication number
WO2018090210A1
WO2018090210A1 PCT/CN2016/105966 CN2016105966W WO2018090210A1 WO 2018090210 A1 WO2018090210 A1 WO 2018090210A1 CN 2016105966 W CN2016105966 W CN 2016105966W WO 2018090210 A1 WO2018090210 A1 WO 2018090210A1
Authority
WO
WIPO (PCT)
Prior art keywords
service packet
instance
ring protection
node device
service
Prior art date
Application number
PCT/CN2016/105966
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 KR1020197016997A priority Critical patent/KR102161422B1/ko
Priority to EP16921924.3A priority patent/EP3534571B1/en
Priority to PCT/CN2016/105966 priority patent/WO2018090210A1/zh
Priority to CN201680089090.3A priority patent/CN109691031B/zh
Publication of WO2018090210A1 publication Critical patent/WO2018090210A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/42—Loop networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/42—Loop networks
    • H04L12/437—Ring fault isolation or reconfiguration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2408—Traffic characterised by specific attributes, e.g. priority or QoS for supporting different services, e.g. a differentiated services [DiffServ] type of service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/35—Switches specially adapted for specific applications
    • H04L49/351—Switches specially adapted for specific applications for local area network [LAN], e.g. Ethernet switches

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a service message transmission method and a node device.
  • the ERPS (Ethernet Ring Protection Switch) protocol is the G.8032 protocol defined by the ITU-T (International Telecommunication Union Telecommunication Standardization Sector). It is specifically used for Ethernet ring protection. Link layer protocol.
  • the ERPS protocol can prevent broadcast storms caused by data loops when the Ethernet ring is complete. When a link on the Ethernet ring is disconnected, the backup link can be quickly enabled to restore the communication path between nodes on the ring network.
  • FIG. 1 is a schematic diagram of an architecture of an existing ERPS network.
  • the ERPS network includes an ERPS ring composed of node devices A, B, C, and D.
  • PAB link between A and B
  • PBC link between B and C
  • PCD link between them
  • PAD link between A and D
  • PAD link between A and D
  • the node device D is a protection node
  • the port connected to device C on the node device D is a ring protection link (RPL) port
  • the PCD is an RPL link; when all links in the network are connected (up In the state, as shown in FIG. 1a of FIG.
  • the RPL port is in a blocked state (BLOCKED) state, and the protocol state of the ERPS protocol is the Idle state, and the data of the device A and the device D are forwarded through the link PAD.
  • BLOCKED blocked state
  • the protocol state of the ERPS protocol is the protection state, and the state of the RPL port changes from the blocked state to the forwarding state.
  • the data is forwarded through the links PCD, PBC and PAB in turn.
  • the protocol under normal circumstances, under normal circumstances, the protocol is in idle state, and the backup link cannot be used for data transmission. At this time, all data flows are in the normal link. It is only forwarded from one link, and the remaining links are idle, resulting in wasted bandwidth.
  • the embodiment of the invention provides a service message transmission method and a node device, which solves the problem of bandwidth waste caused by the RPL link being idle state existing in the prior art.
  • the embodiment of the present invention adopts the following technical solutions:
  • an embodiment of the present invention provides an Ethernet ring network protection switching ERPS network, where each ERPS ring in the ERPS network is configured with at least one ring protection instance, and each ring protection instance includes at least two ring protection sub-instances. Each of the ring protection sub-instances corresponds to a ring protection link RPL port, and the state of the RPL port is a blocked state.
  • the existing single ring protection instance is further divided into multiple ring protection sub-instances, and the service packets transmitted by the ring protection instance can be divided to make different rings.
  • the protection sub-instance transmits the corresponding service packet.
  • each ring protection sub-instance corresponds to one RPL port, that is, each ring protection sub-instance corresponds to one RPL link.
  • the RPL link of a ring protection sub-instance is a backup link for the ring protection sub-instance, but the RPL link is able to perform service packets normally for another ring protection sub-instance.
  • the transmitted link is therefore able to take full advantage of the link bandwidth in the ERPS network.
  • the second aspect is applicable to the ERPS network according to the first aspect.
  • the embodiment of the present invention further provides a service packet transmission method, where the execution entity of the method is a common node device that does not include an RPL port, and the method includes: when receiving When a service packet is received, the common node device determines the ring protection sub-instance corresponding to the service packet according to the preset rule and the packet header information of the service packet, and according to the corresponding relationship between the preset ring protection sub-instance and the forwarding path, Determining a forwarding path for forwarding the service packet; and forwarding the service packet according to the forwarding path.
  • the common node device in the embodiment of the present invention is a device that does not include an RPL port.
  • the number of common node devices may be one or more.
  • the preset rule is a rule that is pre-configured on each common node device, and is used to guide the node device to determine the ring protection corresponding to the service packet according to the packet header information of the service packet and the preset rule after receiving the service packet. Child instance.
  • the ordinary node device needs to determine the service report.
  • Ring protection sub-instance and then according to the ring protection sub-instance
  • the corresponding relationship between the forwarding path and the forwarding path determines the forwarding path corresponding to the ring protection sub-instance and forwards the service packet according to the forwarding path.
  • the corresponding RPL link is a backup path.
  • the service packet transmission method can fully utilize the network bandwidth of the ERPS network.
  • the preset rule includes a correspondence between the hash value and the ring protection sub-instance.
  • the hash value is calculated according to the packet header information of the service packet.
  • the corresponding common node device determines the specific implementation manner of the ring protection sub-instance corresponding to the service packet, including: when receiving In the case of a service packet, the ordinary node device calculates a hash value corresponding to the service packet according to the virtual LAN VLAN identifier and the preset byte of the MAC address carried in the packet header information, and further, according to the hash value and the preset rule. Determine the ring protection sub-instance corresponding to the service packet.
  • the MAC address is the source MAC address or the destination MAC address.
  • the preset byte can be all bytes or partial bytes.
  • the preset rule includes a correspondence between a value of a preset field of the service packet and a ring protection sub-instance.
  • the correspondence between the preset field and the ring protection sub-instance can be manually specified and saved as a preset rule.
  • the preset rule includes the correspondence between the VLAN identifier field and the priority field and the ring protection sub-instance
  • the normal node device determines the service according to the preset rule and the packet header information of the service packet.
  • the ring protection sub-instance corresponding to the packet includes: when receiving the service packet, the ordinary node device obtains the value of the priority field and the VLAN identifier field in the packet header information; and according to the priority field and the VLAN identifier field The value and the preset rule determine the ring protection sub-instanment corresponding to the service packet.
  • the first implementation manner and the second implementation manner of the foregoing preset rule may be applied in the process of performing specific processing on the service packet, for example, when the ring protection instance transmits the same type of service report. If the receiving end is the same destination MAC address and the number of service packets sent to the receiving end is large, the same destination MAC address will be used. Service packets are forwarded through different ring protection sub-instances to distribute service packets to different transmission paths.
  • the preset rule includes a correspondence between a service type and a ring protection sub-instance.
  • different ring protection sub-instances are used to transport different types of traffic.
  • the common node device determines, according to the preset rule and the packet header information of the service packet, the ring protection sub-instance corresponding to the service packet, which includes: when receiving the service packet, the ordinary node device obtains the service packet.
  • a service type field in the packet header information, where the service type field is used to indicate the type of the service packet, and the ring protection sub-instance corresponding to the service packet is determined according to the service type field and the preset rule.
  • the third implementation of the preset rule is mainly used in the ring protection instance to transmit multiple types of service packets.
  • the ring protection sub-instance is used to distinguish the types of service packets.
  • the embodiment of the present invention further provides a service packet transmission method, where the method is also applicable to the ERPS network in the first aspect, where the execution entity of the method is a protection node device that includes at least one RPL port.
  • the method includes: when receiving the service packet, the protection node device determines the ring protection sub-instance corresponding to the service packet according to the preset rule and the packet header information of the service packet; and the protection node device determines the ring where the service packet is located.
  • the protection node device determines the packet used for forwarding the service packet according to the corresponding relationship between the ring protection sub-instance and the forwarding path. Forward the path and forward the service packet according to the forwarding path.
  • the protection node device discards the service packet.
  • the protection node device does not block all service packets, and the protection node device does not block all service packets.
  • the present invention further provides a node device, which is used to perform each step in the method described in the foregoing second aspect.
  • the function of the node device may be implemented by using hardware or by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the node device includes a processor, a memory, a transceiver, and a bus, and the processor is configured to support the node device to perform a corresponding function in the foregoing method.
  • the memory is for coupling with a processor that holds the necessary program instructions and data for the node device.
  • the transceiver is used by the node device to send data to other devices or receive data sent by other devices.
  • the node device further includes a communication interface, where the communication interface is used to support communication between the node device and other devices.
  • the node device includes: a receiving unit, configured to receive a service packet, and a processing unit, configured to determine a service according to the preset rule and the packet header information of the service packet received by the receiving unit. a ring protection sub-instance corresponding to the packet; and determining, according to a preset correspondence between the ring protection sub-instance and the forwarding path, a forwarding path for forwarding the service packet; and a sending unit, configured to be determined according to the processing unit The forwarding path forwards the service packet.
  • the embodiment of the present invention provides a node device, which is used to perform each step in the method described in the foregoing third aspect, and the function of the node device may be implemented by using hardware, or may be implemented by using hardware corresponding software. .
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the node device includes a processor, a memory, a display, and a bus, and the processor is configured to support the node device to perform a corresponding function in the foregoing method.
  • the memory is for coupling with a processor that holds the necessary program instructions and data for the node device.
  • the transceiver is used by the node device to send data to other devices or receive data sent by other devices.
  • the node device further includes a communication interface, where the communication interface is used to support communication between the node device and other devices.
  • the node device includes: a receiving unit, configured to receive a service packet, and a processing unit, configured to determine, according to the preset rule and the packet header information of the service packet, the service packet corresponding to the service packet The ring protects the sub-instance; and determines whether the RPL port corresponding to the ring protection sub-instance of the service packet is the same as the port used to receive the service packet; and the RPL port corresponding to the ring protection sub-instance where the service packet is located and is used for receiving If the port of the service packet is different, the forwarding path for forwarding the service packet is determined according to the corresponding relationship between the ring protection sub-instance and the forwarding path, and the sending unit is configured to forward according to the forwarding path determined by the processing unit.
  • Business message configured to receive a service packet
  • a processing unit configured to determine, according to the preset rule and the packet header information of the service packet, the service packet corresponding to the service packet The ring protects the sub-instance; and determines whether the R
  • the present invention provides a computer storage medium for storing as the fourth Computer software instructions for use by a node device as described in the aspects, comprising a program designed to perform the above aspects.
  • the present invention provides a computer storage medium for storing computer software instructions for use in the node device of the above fifth aspect, comprising a program designed to perform the above aspects.
  • FIG. 1 is a schematic diagram of an ERPS network architecture configured with an ERPS ring protection example in the prior art
  • FIG. 2 is a schematic diagram of an ERPS network architecture configured with an ERPS ring protection sub-example according to an embodiment of the present invention
  • FIG. 3 is a schematic structural diagram of a computer device according to an embodiment of the present disclosure.
  • FIG. 4 is a schematic flowchart of a method for transmitting a service packet according to an embodiment of the present disclosure
  • FIG. 5 is a schematic structural diagram of a service packet encapsulated by using an 802.1Q protocol according to an embodiment of the present disclosure
  • FIG. 6 is a schematic flowchart of another service packet transmission method according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of an ERPS semi-ring networking according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a network for applying the ERPS semi-ring network shown in FIG. 7 to a multicast dual-selection collection according to an embodiment of the present disclosure
  • FIG. 9 is a schematic structural diagram of a common node device according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of a protection node device according to an embodiment of the present invention.
  • Ring protection example Multiple logical ERPS rings are virtualized by one physical ring, and each logical ERPS ring is called a ring protection instance.
  • the RPL port can be any port on any node device in the ERPS network. Each instance corresponds to an RPL port.
  • the ERPS ring is normal, that is, when there is no faulty link in the ERPS ring, the status of the RPL port is BLOCKED.
  • the difference between the RPL port and the common port is that when the ERPS ring is normal, that is, when there is no faulty link in the ERPS ring, the RPL port is in the blocking state, the normal port is in the forwarding state, and there is a certain one in the ERPS ring. A faulty link, the normal port corresponding to the faulty link is switched from the forwarding state to the blocking state, and the RPL port is switched from the blocking state to the forwarding state.
  • Protection node The node where the RPL port is located is called the protection node (RPL OWNER) and is used to control the status of the RPL port.
  • RPL OWNER protection node
  • RPL The link where the RPL port is located. Normally, the RPL port is in the BLOCKED state. Therefore, the RPL link cannot perform normal data forwarding and is the backup link.
  • Control Virtual Wireless LAN (Control Vlan): The virtual wireless LAN used to manage ERPS protocol status messages.
  • Idle state The link in the ring network is normal, and the RPL port is in the Blocked state.
  • Pending state An intermediate state when the link has not been switched back to the Idle state after a link failure occurs on the ring network and is restored.
  • each ring protection instance in the ERPS network corresponds to one RPL port.
  • each ring protection instance is divided into at least two ring guards in order to perform more detailed division of the existing ring protection instances.
  • each ring protection sub-instance corresponds to one RPL port.
  • the ERPS network includes an ERPS ring composed of devices A, B, C, D, E, and F.
  • the ERPS ring is configured with at least one ring protection instance.
  • the ring protection instances it includes at least two ring protection sub-instances, each of which has a different management VLAN, and each ring protection sub-instance is used to transmit a service packet that meets certain conditions.
  • Each ring protection sub-instance corresponds to one RPL port.
  • the ring protection instance includes ring protection sub-instance 1 and ring protection sub-instance 2, and the RPL port corresponding to ring protection sub-instance 1 is device D, device D and device. Phase E Connected port; the RPL port corresponding to ring protection sub-instance 2 is the port on device B and device B is connected to device A.
  • the node device B and the node device D are protection devices; the device that does not include the RPL port is called a common node device, and the node devices A, C, E, and F in FIG. 2 are common. Node device.
  • the existing single ring protection instance is further divided into multiple ring protection sub-instances, and the service packets transmitted by the ring protection instance can be divided to make different rings.
  • the protection sub-instance transmits the corresponding service packet.
  • each ring protection sub-instance corresponds to one RPL port, that is, each ring protection sub-instance corresponds to one RPL link.
  • the RPL link of a ring protection sub-instance is a backup link for the ring protection sub-instance, but the RPL link is able to perform service packets normally for another ring protection sub-instance.
  • the transmitted link is therefore able to take full advantage of the link bandwidth in the ERPS network.
  • the protection node device and the ordinary node device in FIG. 2 can be implemented in the manner of the computer device (or system) in FIG.
  • FIG. 3 is a schematic diagram of a computer device according to an embodiment of the present invention.
  • the computer device 100 includes at least one processor 101, a communication bus 102, a memory 103, and at least one communication interface 104.
  • the processor 101 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present invention.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • Communication bus 102 can include a path for communicating information between the components described above.
  • the communication interface 104 is configured to communicate with other devices or communication networks.
  • the memory 103 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device can also be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), disk storage media Or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of an instruction or data structure and that can be accessed by a computer, but is not limited thereto.
  • the memory can exist independently and be connected to the processor via a bus.
  • the memory can also be integrated with the processor.
  • the memory 103 is used to store application code for executing the solution of the present invention, and is controlled by the processor 101 for execution.
  • the processor 101 is configured to execute application code stored in the memory 103.
  • processor 101 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • computer device 100 can include multiple processors, such as processor 101 and processor 105 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • processors herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • the service packet transmission method provided by the embodiment of the present invention describes the process of forwarding the service packet in the ERPS network from the perspective of the common node device and the protection node device.
  • the embodiment of the present invention further provides a service packet transmission method, which can be applied to the ERPS network shown in FIG. 2, and the execution body of the method is a common node device as shown in FIG. 3, as shown in FIG. include:
  • Step 201 When receiving the service packet, the normal node device determines the ring protection sub-instance corresponding to the service packet according to the preset rule and the packet header information of the service packet.
  • the packet header information is the information contained in the packet header of the service packet, such as the destination media access control (MAC) address of the packet, the source MAC address, the destination IP address of the packet, the source IP address, and the priority. Level field, VLAN ID, etc.
  • MAC media access control
  • the preset rule is a rule that is pre-configured on each common node device, and is used to guide the node device to determine, according to the packet header information of the service packet and the preset rule, after receiving the service packet.
  • the preset rule includes a correspondence between a specific field in the packet header information and the ring protection sub-instance, or a value obtained by processing or processing a specific field in the packet header information and the ring protector.
  • the ordinary node device may calculate or process the value according to the obtained packet header information, the packet header information stored in the preset rule, or a specific field in the packet header information.
  • a ring protection sub-instance corresponding to the service packet is determined by the correspondence between the ring protection sub-instance and the ring protection sub-instance.
  • Step 202 The common node device determines a forwarding path for forwarding service packets according to a preset relationship between the ring protection sub-instance and the forwarding path.
  • the service packets transmitted by the same node belong to the same ring protection instance, and the forwarding is performed.
  • the path is the same. Therefore, after receiving the service packet, the ordinary node device does not need to make any judgment. It only needs to forward the service packet according to the pre-stored forwarding rule.
  • the ordinary node device needs to determine the ring corresponding to the service packet after receiving the service packet.
  • the sub-instance is protected, and the forwarding path of the service packet is determined according to the corresponding relationship between the ring protection sub-instance and the forwarding path.
  • Step 203 The ordinary node device forwards the service packet according to the forwarding path.
  • the ordinary node device needs to determine the service report.
  • the ring protection sub-instance corresponding to the text, and then the forwarding path corresponding to the ring protection sub-instance is determined according to the correspondence between the ring protection sub-instance and the forwarding path, and the service packet is forwarded according to the forwarding path.
  • the corresponding RPL link is a backup path.
  • the service packet transmission method can fully utilize the network bandwidth of the ERPS network.
  • the packet encapsulated by the 802.1Q protocol is used as an example, and the embodiment of the present invention provides the service packet.
  • the packet structure includes the packet header of the service packet and the data of the service packet body.
  • the packet header information of the service packet includes a destination address, a source address, an 802.1Q tag header, and a length/type (Length/Type) of the service packet.
  • the 802.1Q tag header includes a TPID (Tag Protocol Identifier) and a Tag Control Information (TCI).
  • the TCI specifically includes a User Priority and a Canonical Format Indicator. CFI) and VLAN identification (VLAN ID).
  • the source address and the destination address are both MAC addresses.
  • the preset rule includes a correspondence between the hash value and the ring protection sub-instance.
  • the hash value is calculated according to the packet header information of the service packet, for example, the hash value determined by hash calculation according to the source MAC address of the service packet or all bytes or partial bytes of the destination MAC address. .
  • the hash value determined by the hash calculation according to all or part of the byte and the VLAN ID of the destination MAC address in the packet header information of the service packet; or all or part of the byte of the source MAC address and the VLAN identifier The determined hash value.
  • the hash value determined by the hash calculation is performed according to the VLAN identifier in the header information and all or part of the bytes of the priority field.
  • the step 201 is, when the service packet is received, the common node device according to the preset rule and the service packet.
  • the packet header information is used to determine the ring protection sub-instance corresponding to the service packet, which specifically includes:
  • the normal node device When receiving the service packet, calculates the hash value corresponding to the service packet according to the virtual local area network VLAN identifier and the preset byte of the medium access control MAC address carried in the packet header information, according to the hash.
  • the value and the preset rule determine a ring protection sub-instanment corresponding to the service packet.
  • the MAC address is a source MAC address or a destination MAC address.
  • the preset rule includes a correspondence between a value of a preset field of the service packet and a ring protection sub-instance.
  • the correspondence between the preset field and the ring protection sub-instance can be manually specified. And save as a preset rule.
  • the preset field includes a VLAN identifier
  • the preset rule includes a correspondence between the VLAN identifier and the ring protection sub-instance.
  • the preset rule may be a service packet whose VLAN ID is VLAN 100, VLAN 200, or VLAN 300.
  • the corresponding ring protection sub-instance is the ring protection sub-instance 1;
  • the VLAN ID is the service packet of VLAN 400 and VLAN 500, and the corresponding ring protection sub-instance is the ring protection sub-instance 2.
  • the preset rule includes a VLAN identifier and a MAC address
  • the preset rule includes a correspondence between the VLAN identifier, the MAC address, and the ring protection sub-instance.
  • the preset rule may be a VLAN identifier.
  • VLAN 100 and the last bit of the MAC address is an even number of service packets.
  • the corresponding ring protection sub-instance is the ring protection sub-instance 1; the VLAN ID is VLAN 100 and the last bit of the MAC address is an odd number of service packets.
  • the sub-instance is the ring protection sub-instance 2; the VLAN ID is VLAN 200 and the last bit of the MAC address is an odd-numbered service packet, and the corresponding ring protection sub-instance is the ring protection sub-instance 3.
  • the preset field includes a priority field and a VLAN identifier field
  • the preset rule includes a correspondence between the priority field and the VLAN identifier field.
  • the preset rule may be a VLAN ID of the VLAN 100, and the ring protection sub-instance corresponding to the priority field is the ring protection sub-instance 1; the VLAN ID is VLAN 100, and the priority field is 2;
  • the ring protection sub-instance is the ring protection sub-instance instance 2;
  • the VLAN ID is VLAN 200, and the ring protection sub-instance whose priority value is 1 is the ring protection sub-instance 1;
  • the VLAN ID is VLAN 200, and the priority field is 2
  • the corresponding ring guard sub-instance is ring protection sub-instance 1.
  • the ordinary node device determines according to the preset rule and the packet header information of the service packet.
  • the ring protection sub-instance corresponding to the service packet the method includes: when receiving the service packet, the ordinary node device acquires a value of a priority field and a VLAN identifier field in the packet header information; The value of the priority field and the VLAN identifier field and the preset rule determine the ring protection sub-instanment corresponding to the service packet.
  • the first implementation manner and the second implementation manner of the foregoing preset rule may be applied in the process of performing specific processing on the service packet, for example, when the ring protection instance transmits the same type of service report.
  • the protection sub-instance is forwarded; or, when the receiving end is the same destination MAC address, and the number of service packets sent to the receiving end is large, the service packets of the same destination MAC address are forwarded through different ring protection sub-instances to implement the service. Messages are scattered into different transmission paths.
  • the preset rule includes a correspondence between a service type and a ring protection sub-instance.
  • different ring protection sub-instances are used to transport different types of traffic.
  • the packet header information of the service packet includes a service type field, and the service type field can be used to indicate the service type of the service packet. For example, when the value of the service type field is the first value, the corresponding service is used. The packet type is type one. When the value of the service type field is the second value, the corresponding service packet type is type 2.
  • the common node device determines the ring protection sub-instance corresponding to the service packet according to the preset rule and the packet header information of the service packet, which includes: when receiving the service When the packet is received, the common node device obtains the service type field in the packet header information of the service packet, and determines the ring protection sub-instance corresponding to the service packet according to the service type field and the preset rule.
  • the third implementation of the preset rule is mainly used in the ring protection instance to transmit multiple types of service packets.
  • the ring protection sub-instance is used to distinguish the types of service packets.
  • the embodiment of the present invention further provides a service packet transmission method, which is also applicable to the ERPS network shown in FIG. 2, where the execution body of the method is a protection node device including at least one RPL port, and the protection node device is specific.
  • the structure may be the computer device shown in FIG. 3, as shown in FIG. 6, the method includes:
  • Step 301 When receiving the service packet, the protection node device determines the ring protection sub-instance corresponding to the service packet according to the preset rule and the packet header information of the service packet.
  • Step 302 The protection node device determines whether the RPL port corresponding to the ring protection sub-instance in which the service packet is located is the same as the port used to receive the service packet.
  • each node device When applied to an ERPS ring, each node device includes two ports, which may be RPL ports, or only one port may be an RPL port, or both ports may be non-RPL ports. If the port for receiving the service packet is an RPL port, and the RPL port is different from the RPL port corresponding to the ring protection sub-instance of the specified service packet, the RPL port does not need to block service packets or receive the packet. If the port of the service packet is a non-RPL port, that is, the normal port, perform the following step 303. Otherwise, step 305 is performed.
  • the node device may also include other ports for interacting with other devices outside the ERPS ring.
  • Step 303 The protection node device determines a forwarding path for forwarding service packets according to a preset relationship between the ring protection sub-instance and the forwarding path.
  • next hop port in the forwarding path is another RPL port of the protection node device
  • the protection node device still performs step 302. If the next hop port in the forwarding path is another protection node device, the other protection node device repeatedly performs steps 301 to 305; if the next hop port is a normal node device, the ordinary node device performs the above Step 201 to step 203.
  • Step 304 The protection node device forwards the service packet according to the forwarding path.
  • Step 305 The protection node device discards the service packet.
  • the protection node device does not block all service packets, and the protection node device does not block all service packets.
  • the ring protection sub-example corresponding to the service packet is a ring protection sub-
  • the node B belongs to the RPL port corresponding to the ring protection sub-instance 2, and does not block the service packet of the ring protection sub-instance 1.
  • the device can reach the device D along the path of the A, B, C, and D; If the ring protection sub-instance instance corresponding to the service packet is the ring protection sub-instance 2, the node D belongs to the RPL port corresponding to the ring protection sub-instance 1, and does not block the service packet of the ring protection sub-instance 2. Therefore, Path along A, F, E, D Arrive to device D. In turn, the bandwidth of the RPL link can be fully utilized, so that all links in the network can be used to transmit service packets.
  • ERPS semi-ring means that the interconnection between node devices does not form a real ring network, but there is a "gap".
  • the ERPS protocol is not enabled on a device.
  • the link of the ERPS network is still open.
  • devices A, B, C, D, and E form an ERPS ring network, but the ERPS protocol is not enabled on device E, so that devices A, B, C, and D form a half ring.
  • the video source server 401, the video source server 402, and the routing device 403 form an ERPS half ring.
  • routing device 403 also includes a port C (located outside of the ERPS half-ring) for connection to a user equipment (not shown).
  • the same join request is used to request the video data of program 1 and program 2.
  • the video source server 401 forwards the video streams of both programs to port A, and the video source server 402 will stream the video of the two programs. Both are forwarded to port B, so that each program has two video streams on the routing device 403, so each program needs to select one video stream to be forwarded to the user side port C.
  • the routing device needs to send the on-demand message to the video source servers 401 and 402 through the port A.
  • the packet is not sent through port B.
  • the implementation process is complicated and costly.
  • the video source servers 401 and 402 send the on-demand message to the routing device 403 through port B only when port A is disconnected. Text, the video stream is taken down from port B.
  • the packet control implementation solution in the prior art is complicated. After the link where the A port is disconnected, the routing device 403 needs to re-route the video source through the B port. The device 402 sends the on-demand message, and the delay is large, and the load cannot be shared, and the bandwidth of the B is wasted.
  • the two ERPS semi-rings can be configured as two ring protection sub-instances, and the ports A and B of the routing device 403 are respectively configured as the two ring protections.
  • the RPL port of the child instance are respectively referred to as ring protection sub-instance 1 and ring protection sub-instance 2, and the RPL port corresponding to ring protection sub-instance 1 is port A, allowing data flow through program 1;
  • the RPL port corresponding to the protection sub-instance 2 is port B, which allows data flow through the program 2.
  • the service packet transmission method provided by the embodiment of the present invention automatically blocks unnecessary video streams, and each program only forwards one data stream to the user side port C.
  • the RPL port of the ring protection sub-instance will quickly change from the Block state to the Forwarding state. The entire process will almost never lose any video stream packets. There is no impact on watching the program, and the implementation of multicast on the device is basically unaffected and convenient to implement.
  • the embodiment of the present invention further provides a schematic structural diagram of a common node device 500, which is used to perform a service packet transmission method as shown in FIG. 3.
  • the node device includes: a receiving unit 501, configured to receive Business message.
  • the processing unit 502 is configured to determine, according to the preset rule and the packet header information of the service packet received by the receiving unit 501, a ring protection sub-instance corresponding to the service packet; and according to a preset ring protection sub-instance And a forwarding path that is used to forward the service packet.
  • the sending unit 503 is configured to forward the service packet according to the forwarding path determined by the processing unit 502.
  • the preset rule includes a correspondence between a hash value and a ring protection sub-instance.
  • the processing unit 502 is further configured to calculate, according to the virtual local area network (VLAN) VLAN identifier and the preset byte of the medium access control MAC address carried in the packet header information of the service packet received by the receiving unit 501, A hash value corresponding to the service packet, where the MAC address is a source MAC address or a destination MAC address, and the ring protection sub-instance corresponding to the service packet is determined according to the hash value and the preset rule.
  • VLAN virtual local area network
  • the preset rule includes a correspondence between a value of a preset field of the service packet and a ring protection sub-instance.
  • the preset field includes a priority field and a VLAN identifier field.
  • the processing unit 502 is further configured to obtain a value of a priority field and a VLAN identifier field in the packet header information of the service packet received by the receiving unit 501; The value of the priority field and the VLAN identifier field and the preset rule determine the ring protection sub-instanment corresponding to the service packet.
  • the preset rule includes a correspondence between a service type and a ring protection sub-instance.
  • the processing unit 502 is further configured to obtain a service type field in the packet header information of the service packet received by the receiving unit 501, where the service type field is used to represent the service packet. a service type; determining, according to the service type field and the preset rule, a ring protection sub-instance corresponding to the service packet.
  • the single ring protection instance is divided into multiple ring protection sub-instances. Therefore, in the embodiment of the present invention, after receiving the service packet, the ordinary node device needs to determine the ring protection sub-instance corresponding to the service packet. Then, the forwarding path corresponding to the ring protection sub-instance is determined according to the correspondence between the ring protection sub-instance and the forwarding path, and the service packet is forwarded according to the forwarding path. In this case, for a ring protection sub-instance, the corresponding RPL link is a backup path.
  • the ring protection sub-instance When the ring protection sub-instance is normal, it cannot be used for service packet transmission; and the RPL link is for another ring protection sub-
  • the example is a normal link and can be used for the transmission of service packets. Therefore, the network bandwidth of the ERPS network can be fully utilized.
  • the ordinary node device is presented in the form of a functional unit.
  • a "unit” herein may refer to an application-specific integrated circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above. Device.
  • ASIC application-specific integrated circuit
  • a conventional node device may take the form shown in FIG.
  • the receiving unit 501 and the transmitting unit 503 can be implemented by the communication interface 104 of FIG. 3, and the processing unit 502 can be implemented by the processor 101 and the memory 103 of FIG.
  • the embodiment of the present invention further provides a structure diagram of a protection node device 600, which is used to perform a service packet transmission method as shown in FIG. 6.
  • the node device includes: a receiving unit 601, configured to receive Business message.
  • the processing unit 602 is configured to determine, according to the preset rule and the packet header information of the service packet, a ring protection sub-example corresponding to the service packet; Whether the RPL port corresponding to the ring protection sub-instance of the service packet is the same as the port used to receive service packets; the RPL port corresponding to the ring protection sub-instance where the service packet is located is not the same as the port used to receive service packets.
  • the forwarding path for forwarding the service packet is determined according to the corresponding relationship between the ring protection sub-instance and the forwarding path.
  • the sending unit 603 is configured to forward the service packet according to the forwarding path determined by the processing unit 602.
  • the processing unit 602 is further configured to discard the service packet when the RPL port corresponding to the ring protection sub-instance of the service packet is the same as the port for receiving the service packet.
  • the protection node device does not block all service packets in the embodiment of the present invention, in which the RPL port of the protection node in the prior art blocks all service packets.
  • the protection node device is presented in the form of a functional unit.
  • a "unit” herein may refer to an application-specific integrated circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above. Device.
  • ASIC application-specific integrated circuit
  • protection node device can take the form shown in FIG.
  • the receiving unit 601 and the transmitting unit 603 can be implemented by the communication interface 104 of FIG. 3, and the processing unit 602 can be implemented by the processor 101 and the memory 103 of FIG.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present invention which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including A number of instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the methods of the various embodiments of the present invention step.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

Landscapes

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

Abstract

本发明公开了业务报文传输方法及节点设备，涉及通信技术领域，为了解决现有技术中存在的由于RPL链路处于空闲状态带来的带宽浪费的问题。本发明提供的业务报文传输方法，应用于ERPS网络，该网络中的每个ERPS环配置有至少一个环保护实例，每个环保护实例包括至少两个环保护子实例，每个环保护子实例分别对应一个RPL端口，该RPL端口的状态为阻塞状态，该方法包括：当接收到业务报文时，普通节点设备根据预设规则以及业务报文的报文头信息，确定业务报文对应的环保护子实例；根据预先设置的环保护子实例与转发路径的对应关系，确定转发路径；按照转发路径转发业务报文。本发明应用在ERPS网络中进行报文传输的过程中。

Description

业务报文传输方法及节点设备 技术领域
本发明涉及通信技术领域，尤其涉及业务报文传输方法及节点设备。
背景技术
ERPS(Ethernet Ring Protection Switch，以太网环网保护倒换)协议为ITU-T(International Telecommunication Union Telecommunication Standardization Sector，国际电信联盟电信标准分局)定义的G.8032协议，为专门用于以太环网保护的链路层协议。ERPS协议在以太网环完整时能够防止数据环路引起的广播风暴，而当以太网环上一条链路断开时能迅速启用备份链路以恢复环网上各个节点之间的通信通路。
如图1所示为现有的ERPS网络的一种架构示意图。该ERPS网络包括由节点设备A、B、C、D组成的ERPS环，为便于描述将A与B之间的链路称为PAB、B与C之间的链路称为PBC，C与D之间的链路称为PCD，A与D之间的链路称为PAD。其中，节点设备D为保护节点，节点设备D上与设备C相连的端口为环保护链路(Ring Protection Link，RPL)端口，PCD为RPL链路；当网络中所有链路均为联通(up)状态时，如图1中图1a所示，RPL端口处于阻塞(BLOCKED)状态，此时ERPS协议的协议状态为Idle状态，设备A和设备D的数据通过链路PAD进行转发。当链路PAD断开时，如图1中图1b所示，此时ERPS协议的协议状态为保护(protection)状态，RPL端口的状态由阻塞状态变为转发状态，设备A和设备D之间的数据依次通过链路PCD、PBC和PAB进行转发。
经发明人研究发现，在现在的协议规定下，正常情况下，协议处于空闲(Idle)状态，备份链路无法用于进行数据传输，此时，所有的数据流在链路正常的情况下都仅从一条链路转发，而其余链路处于空闲状态，造成了带宽浪费。
发明内容
本发明实施例提供一种业务报文传输方法及节点设备，以解决现有技术中存在的由于RPL链路处于空闲状态带来的带宽浪费的问题。
为达到上述目的，本发明实施例采用如下技术方案：
第一方面，本发明实施例提供一种以太网环网保护倒换ERPS网络，该ERPS网络中的每个ERPS环配置有至少一个环保护实例，每个环保护实例包括至少两个环保护子实例，每个所述环保护子实例分别对应一个环保护链路RPL端口，其中，RPL端口的状态为阻塞状态。
可见，本发明实施例提供的ERPS网络中，将现有的单个环保护实例进行细化划分为多个环保护子实例，进而可以将环保护实例传输的业务报文进行划分，使不同的环保护子实例传输相应的业务报文。这样，由于每个环保护子实例分别对应一个RPL端口，也即每个环保护子实例分别对应一个RPL链路。则在正常情况下某个环保护子实例的RPL链路对该环保护子实例而言为备份链路，但该RPL链路对另一个环保护子实例而言则为能够正常进行业务报文传输的链路，因此能够充分利用ERPS网络中的链路带宽。
第二方面，应用于第一方面所述的ERPS网络，本发明实施例还提供一种业务报文传输方法，该方法的执行主体为不包含RPL端口的普通节点设备，该方法包括：当接收到业务报文时，普通节点设备根据预设规则以及业务报文的报文头信息，确定业务报文对应的环保护子实例；并根据预先设置的环保护子实例与转发路径的对应关系，确定用于转发业务报文的转发路径；进而按照该转发路径转发业务报文。
其中，本发明实施例所指的普通节点设备为不包含RPL端口的设备，在ERPS网络中，普通节点设备的数量可以为一个或多个。预设规则为预先配置在各个普通节点设备的规则，用于指导节点设备在接收到业务报文后，根据业务报文的报文头信息以及该预设规则确定该业务报文对应的环保护子实例。
本发明实施例提供的业务报文传输方法，由于单个环保护实例被划分为多个环保护子实例，因此，本发明实施例中，普通节点设备在收到业务报文后，需要确定业务报文对应的环保护子实例，进而根据环保护子实例 和转发路径之间的对应关系确定该环保护子实例对应的转发路径并按照该转发路径转发业务报文。这样，对于某个环保护子实例而言，其对应的RPL链路为备份路径，在环保护子实例正常时，无法用于业务报文的传输；而该RPL链路对于另一个环保护子实例而言为正常链路，可以用于业务报文的传输。因此，本发明实施例提供的业务报文传输方法，能够充分利用ERPS网络的网络带宽。
在该实施例的第一种实现方式中，该预设规则包括哈希值与环保护子实例之间的对应关系。其中，该哈希值为根据业务报文的报文头信息计算得到。当该预设规则中的哈希值为根据VLAN标识和MAC地址进行哈希计算得到时，则相应的普通节点设备确定业务报文对应的环保护子实例的具体实现方式，包括：当接收到业务报文时，普通节点设备根据报文头信息中携带的虚拟局域网VLAN标识和MAC地址的预设字节，计算业务报文对应的哈希值，进而根据该哈希值以及该预设规则，确定业务报文对应的环保护子实例。其中，MAC地址为源MAC地址或目的MAC地址。预设字节可以为全部字节或部分字节。
在该实施例的第二种实现方式中，该预设规则包括业务报文的预设字段的取值与环保护子实例之间的对应关系。在该实现方式中，可以手工指定预设字段和环保护子实例的对应关系并保存成预设规则。当该预设规则中包括的是VLAN标识字段和优先级字段与环保护子实例之间的对应关系时，相应的，普通节点设备根据预设规则以及业务报文的报文头信息，确定业务报文对应的环保护子实例，具体包括：当接收到业务报文时，普通节点设备获取报文头信息中的优先级字段和VLAN标识字段的取值；并根据优先级字段和VLAN标识字段的取值以及该预设规则，确定业务报文对应的环保护子实例。
需要说明的是，上述预设规则的第一种实现方式和第二种实现方式可以应用在需要对业务报文进行特定处理的过程中，例如：当环保护实例中传输同一种类型的业务报文时，需要将不同优先级的业务报文通过不同环保护子实例转发；或者，当接收端为同一目的MAC地址，且发往该接收端的业务报文的数量较多时，将同一目的MAC地址的业务报文通过不同环保护子实例转发以实现将业务报文分散到不同的传输路径中。
在该实施例的第三种实现方式中，该预设规则包括业务类型与环保护子实例之间的对应关系。在该实现方式中，不同的环保护子实例用于传输不同类型的业务。相应的，普通节点设备根据预设规则以及业务报文的报文头信息，确定业务报文对应的环保护子实例，具体包括：当接收到业务报文时，普通节点设备获取业务报文的报文头信息中的业务类型字段，其中，该业务类型字段用于表示业务报文的类型，并根据该业务类型字段以及该预设规则，确定业务报文对应的环保护子实例。
该预设规则的第三种实现方式主要应用在环保护实例中用于传输多种类型的业务报文，需要通过环保护子实例对业务报文的类型进行区分的过程中。
第三方面，本发明实施例还提供一种业务报文传输方法，该方法同样可应用于第一方面所述的ERPS网络中，该方法的执行主体为包含至少一个RPL端口的保护节点设备，该方法包括：当接收到业务报文时，保护节点设备根据预设规则以及业务报文的报文头信息，确定业务报文对应的环保护子实例；保护节点设备确定业务报文所在的环保护子实例对应的RPL端口和用于接收业务报文的端口是否相同；如果不相同，保护节点设备则根据预先设置的环保护子实例与转发路径的对应关系，确定用于转发业务报文的转发路径，并按照该转发路径转发业务报文。
当保护节点设备确定的业务报文所在的环保护子实例对应的RPL端口和用于接收业务报文的端口相同时，保护节点设备丢弃所述业务报文。
本发明实施例提供的上述业务报文传输方法，与现有技术中保护节点的RPL端口会阻塞所有业务报文相比，本发明实施例中，保护节点设备并非阻塞所有的业务报文，而是能够转发业务报文所在的环保护子实例对应的RPL端口和用于接收业务报文的RPL端口不同的业务报文，也即仅阻塞业务报文所在的环保护子实例对应的RPL端口和用于接收业务报文的端口相同的业务报文。
第四方面，本发明还提供一种节点设备，用于执行上述第二方面所述的方法中的各个步骤，该节点设备的功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。
在一种可能的实施例中，该节点设备的结构中包括处理器、存储器、收发器和总线，该处理器被配置为支持该节点设备执行上述方法中相应的功能。该存储器用于与处理器耦合，其保存该节点设备必要的程序指令和数据。该收发器用于该节点设备向其他设备发送数据或接收其他设备发送的数据。可选的，该节点设备还包括通信接口，该通信接口用于支持该节点设备与其他设备之间的通信。
在另一种可能的实施例中，该节点设备包括：接收单元，用于接收业务报文；处理单元，用于根据预设规则以及接收单元接收的业务报文的报文头信息，确定业务报文对应的环保护子实例；并根据预先设置的环保护子实例与转发路径的对应关系，确定用于转发所述业务报文的转发路径；发送单元，用于按照处理单元确定的所述转发路径转发所述业务报文。
第五方面，本发明实施例提供了一种节点设备，用于执行上述第三方面所述的方法中的各个步骤，该节点设备的功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。
在一种可能的实施例中，该节点设备的结构中包括处理器、存储器、显示器和总线，该处理器被配置为支持该节点设备执行上述方法中相应的功能。该存储器用于与处理器耦合，其保存该节点设备必要的程序指令和数据。该收发器用于该节点设备向其他设备发送数据或接收其他设备发送的数据。可选的，该节点设备还包括通信接口，该通信接口用于支持该节点设备与其他设备之间的通信。
在另一种可能的实施例中，该节点设备包括：接收单元，用于接收业务报文；处理单元，用于根据预设规则以及业务报文的报文头信息，确定业务报文对应的环保护子实例；并确定业务报文所在的环保护子实例对应的RPL端口和用于接收业务报文的端口是否相同；当业务报文所在的环保护子实例对应的RPL端口和用于接收业务报文的端口不相同时，根据预先设置的环保护子实例与转发路径的对应关系，确定用于转发所述业务报文的转发路径；发送单元，用于按照处理单元确定的转发路径转发业务报文。
第六方面，本发明提供了一种计算机存储介质，用于储存为上述第四 方面所述的节点设备所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
第七方面，本发明提供了一种计算机存储介质，用于存储为上述第五方面所述的节点设备所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
附图说明
图1为现有技术中的配置有ERPS环保护实例的ERPS网络架构示意图；
图2为本发明实施例提供的配置有ERPS环保护子实例的ERPS网络架构示意图；
图3为本发明实施例提供的一种计算机设备的结构示意图；
图4为本发明实施例提供的一种业务报文传输方法的流程示意图；
图5为本发明实施例提供的一种采用802.1Q协议封装的业务报文的结构示意图；
图6为本发明实施例提供的另一种业务报文传输方法的流程示意图；
图7为本发明实施例提供的一种ERPS半环组网结构示意图；
图8为本发明实施例提供的一种将图7所示的ERPS半环组网应用于组播双发选收的组网结构示意图；
图9为本发明实施例提供的一种普通节点设备的结构示意图；
图10为本发明实施例提供的一种保护节点设备的结构示意图。
具体实施方式
下文先对ERPS网络中的相关技术术语进行如下解释：
环保护实例：由一个物理上的环虚拟出多个逻辑上的ERPS环，每个逻辑上的ERPS环称为一个环保护实例。
RPL(Ring Protection Link，环保护链路)端口：RPL端口可为ERPS网络中任意节点设备上的任意端口。每个实例对应一个RPL端口，在ERPS环正常时，也即ERPS环中不存在故障链路时，该RPL端口的状态为阻塞(BLOCKED)状态。
需要说明的是，RPL端口与普通端口的区别在于，在ERPS环正常时，即ERPS环中不存在故障链路时，RPL端口处于阻塞状态，普通端口处于转发状态；在ERPS环中存在某一条故障链路，该故障链路对应的普通端口由转发状态切换为阻塞状态，RPL端口由阻塞状态切换到转发(Forwarding)状态。
保护节点：RPL端口所在的节点称为保护节点(RPL OWNER)，用于控制RPL端口的状态。
普通节点：ERPS网络中，不包含RPL端口的其他节点。
RPL：RPL端口所在的链路，正常情况下，RPL端口处于BLOCKED状态，因此，该RPL链路无法进行正常的数据转发，为备份链路。
控制虚拟无线局域网(Control Vlan)：用来管理ERPS协议状态报文所使用的虚拟无线局域网。
ERPS协议规定的环网状态：
空闲(Idle)状态：环网中各链路连接均正常，RPL端口为Blocked状态时的状态。
保护(Protection)状态：当环网中有链路断开，RPL端口状态转变为Forwarding状态时的状态。
过渡(Pending)状态：环网出现链路故障且恢复后，链路尚未回切到Idle状态时的一种中间状态。
目前，ERPS网络中的每个环保护实例对应一个RPL端口；本实施例中，为了对现有的环保护实例进行更加细化的划分，将每个环保护实例划分为至少两个环保护子实例，每个环保护子实例分别对应一个RPL端口。
本发明实施例提供一种ERPS网络，如图2所示，该ERPS网络包括由设备A、B、C、D、E和F组成的ERPS环，该ERPS环配置有至少一个环保护实例。对于其中一个环保护实例而言，其包括至少两个环保护子实例，每个环保护子实例对应的管理VLAN不同，且每个环保护子实例分别用于传输满足特定条件的业务报文。每个环保护子实例分别对应一个RPL端口，例如：该环保护实例包括环保护子实例1和环保护子实例2，且环保护子实例1对应的RPL端口为设备D上，设备D与设备E相 连的端口；环保护子实例2对应的RPL端口为设备B上，设备B与设备A相连的端口。
在图2所示的ERPS网络中，节点设备B和节点设备D为保护设备；将不包含RPL端口的设备称为普通节点设备，如图2中的节点设备A、C、E和F为普通节点设备。
可见，本发明实施例提供的ERPS网络中，将现有的单个环保护实例进行细化划分为多个环保护子实例，进而可以将环保护实例传输的业务报文进行划分，使不同的环保护子实例传输相应的业务报文。这样，由于每个环保护子实例分别对应一个RPL端口，也即每个环保护子实例分别对应一个RPL链路。则在正常情况下某个环保护子实例的RPL链路对该环保护子实例而言为备份链路，但该RPL链路对另一个环保护子实例而言则为能够正常进行业务报文传输的链路，因此能够充分利用ERPS网络中的链路带宽。
如图3所示，图2中的保护节点设备和普通节点设备可以以图3中的计算机设备(或系统)的方式来实现。
图3所示为本发明实施例提供的计算机设备示意图。计算机设备100包括至少一个处理器101，通信总线102，存储器103以及至少一个通信接口104。
处理器101可以是一个通用中央处理器(CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本发明方案程序执行的集成电路。
通信总线102可包括一通路，在上述组件之间传送信息。所述通信接口104，用于与其他设备或通信网络通信。
存储器103可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、只读光盘(Compact Disc Read-Only Memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质 或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过总线与处理器相连接。存储器也可以和处理器集成在一起。
其中，所述存储器103用于存储执行本发明方案的应用程序代码，并由处理器101来控制执行。所述处理器101用于执行所述存储器103中存储的应用程序代码。
在具体实现中，作为一种实施例，处理器101可以包括一个或多个CPU，例如图3中的CPU0和CPU1。
在具体实现中，作为一种实施例，计算机设备100可以包括多个处理器，例如图3中的处理器101和处理器105。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
基于上述ERPS网络，本发明实施例提供的业务报文传输方法分别从普通节点设备和保护节点设备的角度描述业务报文在ERPS网络中进行转发的过程。
需要说明的是，本发明实施例提供的业务报文传输方法应用于ERPS环正常运行时，也即ERPS环中不存在链路故障的情况下，该RPL端口的状态为阻塞状态。
本发明实施例还提供一种业务报文传输方法，可应用于图2所述的ERPS网络中，该方法的执行主体为如图3所示的普通节点设备，如图4所示，该方法包括：
步骤201：当接收到业务报文时，普通节点设备根据预设规则以及业务报文的报文头信息，确定业务报文对应的环保护子实例。
报文头信息为业务报文的报文头中包含的信息，比如报文的目的媒体访问控制(Media Access Control，MAC)地址、源MAC地址、报文的目的IP地址、源IP地址、优先级字段、VLAN标识等。
预设规则为预先配置在各个普通节点设备的规则，用于指导节点设备在接收到业务报文后，根据业务报文的报文头信息以及该预设规则确定该 业务报文对应的环保护子实例。
可选的，预设规则中包括报文头信息中的特定字段与环保护子实例之间的对应关系；或者将报文头信息中的特定字段进行计算或处理后得到的值与环保护子实例之间的对应关系。则在本步骤的具体实现中，普通节点设备可以根据获取的报文头信息，以及预设规则中存储的报文头信息或者将报文头信息中的特定字段进行计算或处理后得到的值与环保护子实例之间的对应关系，确定业务报文对应的环保护子实例。
步骤202：普通节点设备根据预先设置的环保护子实例与转发路径的对应关系，确定用于转发业务报文的转发路径。
现有技术中，对单个环保护实例而言，由于没有进一步细化的划分环保护子实例，因此对于普通节点设备而言，其所传输的业务报文都属于同一个环保护实例，其转发路径都一样，因此，普通节点设备在接收到业务报文后，无需进行任何判断，只需要按照预先存储的转发规则进行业务报文的转发即可。
本实施例中，由于将环保护实例划分为多个环保护子实例，不同环保护子实例的转发路径不同，则普通节点设备在收到业务报文后，需要确定该业务报文对应的环保护子实例，进而再根据预先设置的环保护子实例与转发路径的对应关系，确定业务报文的转发路径。
步骤203：普通节点设备按照转发路径转发业务报文。
本发明实施例提供的业务报文传输方法，由于单个环保护实例被划分为多个环保护子实例，因此，本发明实施例中，普通节点设备在收到业务报文后，需要确定业务报文对应的环保护子实例，进而根据环保护子实例和转发路径之间的对应关系确定该环保护子实例对应的转发路径，并依照该转发路径转发业务报文。这样，对于某个环保护子实例而言，其对应的RPL链路为备份路径，在环保护子实例正常时，无法用于业务报文的传输；而该RPL链路对于另一个环保护子实例而言为正常链路，可以用于业务报文的传输。因此，本发明实施例提供的业务报文传输方法，能够充分利用ERPS网络的网络带宽。
为了便于说明本实施例中的预设规则的可能实现方式，如图5所示，以应用了802.1Q协议封装的报文为例，本发明实施例提供了业务报文的 报文结构，包括业务报文的报文头和业务报文本身的数据。其中，业务报文的报文头信息包括业务报文的目的地址(destination address)、源地址(source address)、802.1Q标签头、长度/类型(Length/Type)。其中，802.1Q标签头包括TPID(Tag Protocol Identifier，标签协议标识)、标记控制信息(Tag Control Information，TCI)；TCI又具体包括用户优先级(User Priority)、规范格式指示器(Canonical Format Indicator，CFI)和VLAN标识(VLAN ID)。
其中，上文所指的源地址和目的地址均是MAC地址，该报文的具体结构可参考现有技术。
在预设规则的一种实现方式中，所述预设规则包括哈希值与环保护子实例之间的对应关系。
其中，该哈希值为根据业务报文的报文头信息计算得到，例如：根据业务报文的源MAC地址或者目的MAC地址的全部字节或部分字节进行哈希计算确定的哈希值。又如：根据业务报文的报文头信息中的目的MAC地址的全部或部分字节以及VLAN ID进行哈希计算确定的哈希值；或者根据源MAC地址的全部或部分字节以及VLAN标识确定的哈希值。再如：根据报文头信息中的VLAN标识和优先级字段的全部或部分字节进行哈希计算确定的哈希值。
当该预设规则中的哈希值为根据VLAN标识和MAC地址进行哈希计算得到时，所述步骤201“当接收到业务报文时，普通节点设备根据预设规则以及所述业务报文的报文头信息，确定所述业务报文对应的环保护子实例”，具体包括：
当接收到业务报文时，普通节点设备根据报文头信息中携带的虚拟局域网VLAN标识和介质访问控制MAC地址的预设字节，计算业务报文对应的哈希值，根据所述哈希值以及所述预设规则，确定所述业务报文对应的环保护子实例。
其中，所述MAC地址为源MAC地址或目的MAC地址。
在预设规则的另一种实现方式中，所述预设规则包括业务报文的预设字段的取值与环保护子实例之间的对应关系。
在该实现方式中，可以手工指定预设字段和环保护子实例的对应关系 并保存成预设规则。
例如：该预设字段包括VLAN标识，则该预设规则包括VLAN标识和环保护子实例之间的对应关系，具体的，该预设规则可以为VLAN标识为VLAN100、VLAN200、VLAN300的业务报文，对应的环保护子实例为环保护子实例1；VLAN标识为VLAN400、VLAN500的业务报文，对应的环保护子实例为环保护子实例2。
又如：该预设字段包括VLAN标识、MAC地址，则该预设规则包括VLAN标识、MAC地址和环保护子实例三者之间的对应关系，具体的，该预设规则可以为VLAN标识为VLAN100且MAC地址的最后一位为偶数的业务报文，对应的环保护子实例为环保护子实例1；VLAN标识为VLAN100且MAC地址的最后一位为奇数的业务报文，对应的环保护子实例为环保护子实例2；VLAN标识为VLAN200且MAC地址的最后一位为奇数的业务报文，对应的环保护子实例为环保护子实例3。
再如：该预设字段包括优先级字段和VLAN标识字段，则该预设规则包括优先级字段和VLAN标识字段这三者之间的对应关系。具体的，该预设规则可以为VLAN标识为VLAN100，且优先级字段取值为1对应的环保护子实例为环保护子实例1；VLAN标识为VLAN100，且优先级字段取值为2对应的环保护子实例为环保护子实例2；VLAN标识为VLAN200，且优先级字段取值为1对应的环保护子实例为环保护子实例1；VLAN标识为VLAN200，且优先级字段取值为2对应的环保护子实例为环保护子实例1。
当所述预设字段包括优先级字段和VLAN标识字段时，相应的，步骤201“当接收到业务报文时，普通节点设备根据预设规则以及所述业务报文的报文头信息，确定所述业务报文对应的环保护子实例”，具体包括：当接收到业务报文时，所述普通节点设备获取报文头信息中的优先级字段和VLAN标识字段的取值；根据所述优先级字段和VLAN标识字段的取值以及所述预设规则，确定所述业务报文对应的环保护子实例。
需要说明的是，上述预设规则的第一种实现方式和第二种实现方式可以应用在需要对业务报文进行特定处理的过程中，例如：当环保护实例中传输同一种类型的业务报文时，需要将不同优先级的业务报文通过不同环 保护子实例转发；或者，当接收端为同一目的MAC地址，且发往该接收端的业务报文的数量较多时，将同一目的MAC地址的业务报文通过不同环保护子实例转发以实现将业务报文分散到不同的传输路径中。
在该实施例的第三种实现方式中，该预设规则包括业务类型与环保护子实例之间的对应关系。在该实现方式中，不同的环保护子实例用于传输不同类型的业务。
一般而言，业务报文的报文头信息中包括业务类型字段，该业务类型字段可以用来表示业务报文的业务类型，例如：业务类型字段取值为第一取值时，对应的业务报文类型为类型一；业务类型字段取值为第二取值时，对应的业务报文类型为类型二。
需要说明的是，802.1Q标签头中的TPID的不同取值可以区分不同的业务类型。
对应于预设规则的第三种实现方式，相应的，普通节点设备根据预设规则以及业务报文的报文头信息，确定业务报文对应的环保护子实例，具体包括：当接收到业务报文时，普通节点设备获取业务报文的报文头信息中的业务类型字段，并根据该业务类型字段以及该预设规则，确定业务报文对应的环保护子实例。
该预设规则的第三种实现方式主要应用在环保护实例中用于传输多种类型的业务报文，需要通过环保护子实例对业务报文的类型进行区分的过程中。
本发明实施例还提供了一种业务报文传输方法，同样可应用于图2所示的ERPS网络中，该方法的执行主体为包含至少一个RPL端口的保护节点设备，该保护节点设备的具体结构可以为图3所示的计算机设备，如图6所示，该方法包括：
步骤301：当接收到业务报文时，保护节点设备根据预设规则以及业务报文的报文头信息，确定业务报文对应的环保护子实例。
该步骤的具体实现过程可参考普通节点设备侧执行步骤201时的具体实现过程。
步骤302：保护节点设备确定业务报文所在的环保护子实例对应的RPL端口和用于接收业务报文的端口是否相同。
应用于ERPS环中时，每个节点设备包括两个端口，这两个端口可能都为RPL端口，也可能只有一个端口为RPL端口，也可能这两个端口都为非RPL端口。如果用于接收业务报文的端口为RPL端口，且该RPL端口和确定的业务报文所在的环保护子实例对应的RPL端口不相同，表明RPL端口不需要阻塞业务报文，或者用于接收业务报文的端口为非RPL端口，也即普通端口则执行下述步骤303。否则，执行步骤305。
需要说明的是，节点设备可能还包括其他端口，用于与ERPS环外的其他设备进行交互。
步骤303：保护节点设备根据预先设置的环保护子实例与转发路径的对应关系，确定用于转发业务报文的转发路径。
其中，如果该转发路径中所指的该下一跳端口为该保护节点设备的另一RPL端口，则该保护节点设备仍然要执行步骤302。如果该转发路径中所指的下一跳端口为其他保护节点设备，则该其他保护节点设备重复执行步骤301至步骤305；如果该下一跳端口为普通节点设备，则该普通节点设备执行上述步骤201至步骤203。
步骤304：保护节点设备按照转发路径转发业务报文。
步骤305：保护节点设备丢弃所述业务报文。
本发明实施例提供的上述业务报文传输方法，与现有技术中保护节点的RPL端口会阻塞所有业务报文相比，本发明实施例中，保护节点设备并非阻塞所有的业务报文，而是能够转发业务报文所在的环保护子实例对应的RPL端口和用于接收业务报文的RPL端口不同的业务报文，也即仅阻塞业务报文所在的环保护子实例对应的RPL端口和用于接收业务报文的端口相同的业务报文。这样能够充分利用RPL链路的带宽。
结合图2所示的ERPS网络架构，在应用本发明实施例提供的报文传输方法时，由节点A向节点D发送业务报文时，当业务报文对应的环保护子实例为环保护子实例1时，由于节点B属于环保护子实例2对应的RPL端口，不会阻塞环保护子实例1的业务报文，因此，可沿着A、B、C、D的路径到达设备D；相应的，当业务报文对应的环保护子实例为环保护子实例2时，由于节点D属于环保护子实例1对应的RPL端口，不会阻塞环保护子实例2的业务报文，因此，可沿着A、F、E、D的路径 到达设备D。进而可以充分利用RPL链路的带宽，使得网络中的所有链路都可以用来传输业务报文。
为了更清楚的说明当执行主体为保护节点设备时，本发明实施例提供的业务报文传输方法的效果，结合组播双发选收的应用场景进行说明。
在介绍组播双发选收的应用场景之前，先介绍一下ERPS半环的概念，ERPS半环是指节点设备之间的相互连接没有组成一个真正的环网，而是存在一个“缺口”，如某个设备上未开启ERPS协议等；但在ERPS半环的应用场景下，ERPS网络的链路仍然是通的。如图7所示，设备A、B、C、D、E组成ERPS环网，但设备E上不启用ERPS协议使得设备A、B、C、D组成一个半环。
应用于该ERPS半环，如图8所示，视频源服务器401、视频源服务器402和路由设备403组成ERPS半环。
为了便于描述，本发明实施例中，将路由设备403与视频源服务器401连接的端口用端口A描述，将路由设备403与视频源服务器402连接的端口用端口B描述。此外，路由设备403还包括用于与用户设备(图中未示出)相连的端口C(位于ERPS半环外)。
结合图8，组播双发选收是指，路由设备403收到用户的组播加入请求后，例如点播节目1和节目2，路由设备403会向视频源服务器401和视频源服务器402分别发送相同的加入请求，用于请求节目1和节目2的视频数据，此后，视频源服务器401会将两个节目的视频流都转发下来到达端口A，视频源服务器402会将两个节目的视频流都转发下来到达端口B，这样在用路由设备403上，每个节目都有两路视频流，所以需要每个节目选择一路视频流向用户侧端口C转发。
现有技术中，在应用组播双发选收的应用场景下时，如果仅将端口B作为RPL端口，则路由设备需要通过端口A向视频源服务器401和402发送点播报文，而且要确保报文不会通过端口B发送，该实现过程比较复杂，代价比较大；这种情况下，只有当端口A断开时，视频源服务器401和402才会通过端口B向路由设备403发送点播报文，将视频流从端口B引下来。现有技术中的这种报文控制实现方案较为复杂，且A端口所在的链路断开后需要由路由设备403重新通过B端口向视频源服务 器402发送点播报文，时延较大，且不能负荷分担，浪费B的带宽。
应用于本发明实施例提供的业务报文传输方法，可以将上述两个ERPS半环配置为两个环保护子实例，且分别将路由设备403的端口A、B分别配置为这两个环保护子实例的RPL端口。为便于描述，将这两个环保护子实例分别称为环保护子实例1和环保护子实例2，且环保护子实例1对应的RPL端口为端口A，允许通过节目1的数据流；环保护子实例2对应的RPL端口为端口B，允许通过节目2的数据流。这样，应用本发明实施例提供的业务报文传输方法会自动将不需要的视频流阻塞掉，每个节目只转发一份数据流到用户侧端口C。
由于ERPS的倒换性能时毫秒级的，如果A或B端口出现问题，环保护子实例的RPL端口会迅速由Block状态转变为Forwarding状态，整个过程几乎不会丢失任何视频流的报文，对用户观看节目的没有任何影响，而且对于设备上组播的实现基本不受影响，实现方便。
如图9所示，本发明实施例还提供了一种普通节点设备500的结构示意图，用于执行如图3所示的业务报文传输方法，该节点设备包括：接收单元501，用于接收业务报文。处理单元502，用于根据预设规则以及所述接收单元501接收的所述业务报文的报文头信息，确定所述业务报文对应的环保护子实例；根据预先设置的环保护子实例与转发路径的对应关系，确定用于转发所述业务报文的转发路径。发送单元503，用于按照所述处理单元502确定的所述转发路径转发所述业务报文。
可选的，所述预设规则包括哈希值与环保护子实例之间的对应关系。相应的，所述处理单元502，还用于根据所述接收单元501接收的业务报文的报文头信息中携带的虚拟局域网VLAN标识和介质访问控制MAC地址的预设字节，计算所述业务报文对应的哈希值，所述MAC地址为源MAC地址或目的MAC地址；根据所述哈希值以及所述预设规则，确定所述业务报文对应的环保护子实例。
可选的，所述预设规则包括业务报文的预设字段的取值与环保护子实例之间的对应关系。其中，所述预设字段包括优先级字段和VLAN标识字段。相应的，所述处理单元502，还用于获取所述接收单元501接收的业务报文的报文头信息中的优先级字段和VLAN标识字段的取值；根据所述 优先级字段和VLAN标识字段的取值以及所述预设规则，确定所述业务报文对应的环保护子实例。
可选的，所述预设规则包括业务类型与环保护子实例之间的对应关系。相应的，所述处理单元502，还用于获取所述接收单元501接收的所述业务报文的报文头信息中的业务类型字段，所述业务类型字段用于表示所述业务报文的业务类型；根据所述业务类型字段以及所述预设规则，确定所述业务报文对应的环保护子实例。
需要说明的是，上述以普通节点设备为执行主体所描述的方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
采用上述方案后，由于单个环保护实例被划分为多个环保护子实例，因此，本发明实施例中，普通节点设备在收到业务报文后，需要确定业务报文对应的环保护子实例，进而根据环保护子实例和转发路径之间的对应关系确定该环保护子实例对应的转发路径，并依照该转发路径转发业务报文。这样，对于某个环保护子实例而言，其对应的RPL链路为备份路径，在环保护子实例正常时，无法用于业务报文的传输；而该RPL链路对于另一个环保护子实例而言为正常链路，可以用于业务报文的传输。因此，能够充分利用ERPS网络的网络带宽。
在本实施例中，普通节点设备是以功能单元的形式来呈现。这里的“单元”可以指特定应用集成电路(application-specific integrated circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。
在一个简单的实施例中，本领域的技术人员可以想到普通节点设备可以采用图3所示的形式。接收单元501和发送单元503可以通过图3的通信接口104来实现，处理单元502可以通过图3的处理器101和存储器103来实现。
如图10所示，本发明实施例还提供了一种保护节点设备600的结构示意图，用于执行如图6所示的业务报文传输方法，该节点设备包括：接收单元601，用于接收业务报文。处理单元602，用于根据预设规则以及业务报文的报文头信息，确定业务报文对应的环保护子实例；以及确定业 务报文所在的环保护子实例对应的RPL端口和用于接收业务报文的端口是否相同；当业务报文所在的环保护子实例对应的RPL端口和用于接收业务报文的端口不相同时，根据预先设置的环保护子实例与转发路径的对应关系，确定用于转发业务报文的转发路径。发送单元603，用于按照所述处理单元602确定的所述转发路径转发所述业务报文。
所述处理单元602，还用于当所述业务报文所在的环保护子实例对应的RPL端口和用于接收所述业务报文的端口相同时，丢弃所述业务报文。
需要说明的是，上述以保护节点设备为执行主体所描述的方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
采用上述方案后，本发明实施例提供的保护节点设备，与现有技术中保护节点的RPL端口会阻塞所有业务报文相比，本发明实施例中，保护节点设备并非阻塞所有的业务报文，而是能够转发业务报文所在的环保护子实例对应的RPL端口和用于接收业务报文的端口不同的业务报文，也即仅阻塞业务报文所在的环保护子实例对应的RPL端口和用于接收业务报文的端口相同的业务报文。
在本实施例中，保护节点设备是以功能单元的形式来呈现。这里的“单元”可以指特定应用集成电路(application-specific integrated circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。
在一个简单的实施例中，本领域的技术人员可以想到保护节点设备可以采用图3所示的形式。接收单元601和发送单元603可以通过图3的通信接口104来实现，处理单元602可以通过图3的处理器101和存储器103来实现。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述方法的全部或部分 步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。

Claims (20)

  1. 一种业务报文传输方法，其特征在于，所述方法应用于以太网环网保护倒换ERPS网络，所述ERPS网络中的每个ERPS环配置有至少一个环保护实例，每个环保护实例包括至少两个环保护子实例，每个所述环保护子实例分别对应一个环保护链路RPL端口，所述RPL端口的状态为阻塞状态，所述方法包括：
    当接收到业务报文时，普通节点设备根据预设规则以及所述业务报文的报文头信息，确定所述业务报文对应的环保护子实例，所述普通节点设备为不包含所述RPL端口的设备；
    普通节点设备根据预先设置的环保护子实例与转发路径的对应关系，确定用于转发所述业务报文的转发路径；
    普通节点设备按照所述转发路径转发所述业务报文。
  2. 根据权利要求1所述的方法，其特征在于，所述预设规则包括哈希值与环保护子实例之间的对应关系。
  3. 根据权利要求2所述的方法，其特征在于，所述当接收到业务报文时，普通节点设备根据预设规则以及所述业务报文的报文头信息，确定所述业务报文对应的环保护子实例，具体包括：
    当接收到业务报文时，所述普通节点设备根据报文头信息中携带的虚拟局域网VLAN标识和介质访问控制MAC地址的预设字节，计算所述业务报文对应的哈希值，所述MAC地址为源MAC地址或目的MAC地址；
    所述普通节点设备根据所述哈希值以及所述预设规则，确定所述业务报文对应的环保护子实例。
  4. 根据权利要求1所述的方法，其特征在于，所述预设规则包括业务报文的预设字段的取值与环保护子实例之间的对应关系。
  5. 根据权利要求4所述的方法，其特征在于，所述预设字段包括优先级字段和VLAN标识字段；
    所述当接收到业务报文时，普通节点设备根据预设规则以及所述业务报文的报文头信息，确定所述业务报文对应的环保护子实例，具体包括：
    当接收到业务报文时，所述普通节点设备获取报文头信息中的优先级字段和VLAN标识字段的取值；
    所述普通节点设备根据所述优先级字段和VLAN标识字段的取值以及所述预设规则，确定所述业务报文对应的环保护子实例。
  6. 根据权利要求1所述的方法，其特征在于，所述预设规则包括业务类型与环保护子实例之间的对应关系。
  7. 根据权利要求6所述的方法，其特征在于，所述当接收到业务报文时，普通节点设备根据预设规则以及所述业务报文的报文头信息，确定所述业务报文对应的环保护子实例，具体包括：
    当接收到业务报文时，所述普通节点设备获取所述业务报文的报文头信息中的业务类型字段，所述业务类型字段用于表示所述业务报文的业务类型；
    所述普通节点设备根据所述业务类型字段以及所述预设规则，确定所述业务报文对应的环保护子实例。
  8. 一种业务报文传输方法，其特征在于，所述方法应用于以太网环网保护倒换ERPS网络，所述ERPS网络中的每个ERPS环配置有至少一个环保护实例，每个环保护实例包括至少两个环保护子实例，每个所述环保护子实例分别对应一个环保护链路RPL端口，所述RPL端口的状态为阻塞状态，所述方法包括：
    当接收到业务报文时，保护节点设备根据预设规则以及所述业务报文的报文头信息，确定所述业务报文对应的环保护子实例，所述保护节点设备为包含至少一个RPL端口的设备；
    所述保护节点设备确定所述业务报文所在的环保护子实例对应的RPL端口和用于接收所述业务报文的端口是否相同；
    如果不相同，所述保护节点设备则根据预先设置的环保护子实例与转发路径的对应关系，确定用于转发所述业务报文的转发路径；
    所述保护节点设备按照所述转发路径转发所述业务报文。
  9. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    如果所述业务报文所在的环保护子实例对应的RPL端口和用于接收所述业务报文的端口相同，所述保护节点设备则丢弃所述业务报文。
  10. 一种节点设备，其特征在于，所述节点设备应用于以太网环网保护倒换ERPS网络，所述ERPS网络中的每个ERPS环配置有至少一个环 保护实例，每个环保护实例包括至少两个环保护子实例，每个所述环保护子实例分别对应一个环保护链路RPL端口，所述RPL端口的状态为阻塞状态，所述节点设备作为不包含所述RPL端口的普通节点设备，包括：
    接收单元，用于接收业务报文；
    处理单元，用于根据预设规则以及所述接收单元接收的所述业务报文的报文头信息，确定所述业务报文对应的环保护子实例；根据预先设置的环保护子实例与转发路径的对应关系，确定用于转发所述业务报文的转发路径；
    发送单元，用于按照所述处理单元确定的所述转发路径转发所述业务报文。
  11. 根据权利要求10所述的节点设备，其特征在于，所述预设规则包括哈希值与环保护子实例之间的对应关系。
  12. 根据权利要求11所述的节点设备，其特征在于，
    所述处理单元，还用于根据所述接收单元接收的业务报文的报文头信息中携带的虚拟局域网VLAN标识和介质访问控制MAC地址的预设字节，计算所述业务报文对应的哈希值，所述MAC地址为源MAC地址或目的MAC地址；
    根据所述哈希值以及所述预设规则，确定所述业务报文对应的环保护子实例。
  13. 根据权利要求10所述的节点设备，其特征在于，所述预设规则包括业务报文的预设字段的取值与环保护子实例之间的对应关系。
  14. 根据权利要求13所述的节点设备，其特征在于，所述预设字段包括优先级字段和VLAN标识字段；
    所述处理单元，还用于获取所述接收单元接收的业务报文的报文头信息中的优先级字段和VLAN标识字段的取值；
    根据所述优先级字段和VLAN标识字段的取值以及所述预设规则，确定所述业务报文对应的环保护子实例。
  15. 根据权利要求10所述的节点设备，其特征在于，所述预设规则包括业务类型与环保护子实例之间的对应关系。
  16. 根据权利要求15所述的节点设备，其特征在于，
    所述处理单元，还用于获取所述接收单元接收的所述业务报文的报文头信息中的业务类型字段，所述业务类型字段用于表示所述业务报文的业务类型；
    根据所述业务类型字段以及所述预设规则，确定所述业务报文对应的环保护子实例。
  17. 一种节点设备，其特征在于，所述节点设备应用于以太网环网保护倒换ERPS网络，所述ERPS网络中的每个ERPS环配置有至少一个环保护实例，每个环保护实例包括至少两个环保护子实例，每个所述环保护子实例分别对应一个环保护链路RPL端口，所述RPL端口的状态为阻塞状态，所述节点设备作为包含至少一个RPL端口的设备，包括：
    接收单元，用于接收业务报文；
    处理单元，用于根据预设规则以及所述业务报文的报文头信息，确定所述业务报文对应的环保护子实例；确定所述业务报文所在的环保护子实例对应的RPL端口和用于接收所述业务报文的端口是否相同；当所述业务报文所在的环保护子实例对应的RPL端口和用于接收所述业务报文的端口不相同时，根据预先设置的环保护子实例与转发路径的对应关系，确定用于转发所述业务报文的转发路径；
    发送单元，用于按照所述处理单元确定的所述转发路径转发所述业务报文。
  18. 根据权利要求17所述的节点设备，其特征在于，
    所述处理单元，还用于当所述业务报文所在的环保护子实例对应的RPL端口和用于接收所述业务报文的端口相同时，丢弃所述业务报文。
  19. 一种节点设备，其特征在于，包括存储器、处理器、收发器和总线，所述存储器、处理器和收发器通过所述总线互相连接，所述存储器存储有程序代码，所述处理器用于根据所述程序代码执行如权利要求1至7任一项所述的方法。
  20. 一种节点设备，其特征在于，包括存储器、处理器、收发器和总线，所述存储器、处理器和收发器通过所述总线互相连接，所述存储器存储有程序代码，所述处理器用于根据所述程序代码执行如权利要求8或9所述的方法。
PCT/CN2016/105966 2016-11-15 2016-11-15 业务报文传输方法及节点设备 WO2018090210A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
KR1020197016997A KR102161422B1 (ko) 2016-11-15 2016-11-15 서비스 패킷 송신 방법 및 노드 디바이스
EP16921924.3A EP3534571B1 (en) 2016-11-15 2016-11-15 Service packet transmission method, and node apparatus
PCT/CN2016/105966 WO2018090210A1 (zh) 2016-11-15 2016-11-15 业务报文传输方法及节点设备
CN201680089090.3A CN109691031B (zh) 2016-11-15 2016-11-15 业务报文传输方法及节点设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/105966 WO2018090210A1 (zh) 2016-11-15 2016-11-15 业务报文传输方法及节点设备

Publications (1)

Publication Number Publication Date
WO2018090210A1 true WO2018090210A1 (zh) 2018-05-24

Family

ID=62145903

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/105966 WO2018090210A1 (zh) 2016-11-15 2016-11-15 业务报文传输方法及节点设备

Country Status (4)

Country Link
EP (1) EP3534571B1 (zh)
KR (1) KR102161422B1 (zh)
CN (1) CN109691031B (zh)
WO (1) WO2018090210A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112118493A (zh) * 2020-08-24 2020-12-22 烽火通信科技股份有限公司 一种erps环网中实现组播协议的方法与系统
CN113645312A (zh) * 2021-08-25 2021-11-12 烽火通信科技股份有限公司 一种基于erps协议的子环网链路保护方法与装置

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102220636B1 (ko) * 2019-07-25 2021-02-26 한국전자기술연구원 G/n 필드가 부가된 프레임 통신 방법
CN113132294B (zh) * 2019-12-30 2022-05-13 中国移动通信集团四川有限公司 一种数据包的过滤方法、系统及装置
US20240106680A1 (en) * 2022-09-28 2024-03-28 Adtran, Inc. Communication Resilience in a Ring Network Topology

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103190121A (zh) * 2011-11-23 2013-07-03 华为技术有限公司 以太网环保护倒换方法、节点及系统
CN104283758A (zh) * 2014-08-04 2015-01-14 杭州华三通信技术有限公司 一种通过数据vlan关联主子环的方法和设备
US20150036544A1 (en) * 2012-09-05 2015-02-05 Brocade Communications Systems, Inc. Multiple ring identification and configuration protocol
CN104883337A (zh) * 2014-02-27 2015-09-02 中兴通讯股份有限公司 环网用户安全的实现方法及装置
CN105763483A (zh) * 2016-02-19 2016-07-13 杭州华三通信技术有限公司 一种报文发送方法和装置

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101789903B (zh) * 2009-12-30 2012-05-23 华为技术有限公司 一种半环网络的保护方法、设备及系统
KR101180223B1 (ko) * 2010-09-29 2012-09-05 한국전력공사 링 네트워크에서의 데이터 패킷 송/수신 방법 및 이를 위한 링 네트워크 노드 단말
WO2013148303A1 (en) * 2012-03-27 2013-10-03 Alcatel Lucent System and method for virtual fabric link failure recovery
US9264254B2 (en) * 2012-03-30 2016-02-16 Ciena Corporation Generalized service protection systems and methods
US8848509B2 (en) * 2012-04-27 2014-09-30 Telefonaktiebolaget L M Ericsson (Publ) Three stage folded Clos optimization for 802.1aq
CN102754390B (zh) * 2012-04-28 2015-06-17 华为技术有限公司 以太网环保护倒换方法、网络设备及系统
CN104079462B (zh) * 2014-07-16 2017-10-17 北京华为数字技术有限公司 环网配置检测方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103190121A (zh) * 2011-11-23 2013-07-03 华为技术有限公司 以太网环保护倒换方法、节点及系统
US20150036544A1 (en) * 2012-09-05 2015-02-05 Brocade Communications Systems, Inc. Multiple ring identification and configuration protocol
CN104883337A (zh) * 2014-02-27 2015-09-02 中兴通讯股份有限公司 环网用户安全的实现方法及装置
CN104283758A (zh) * 2014-08-04 2015-01-14 杭州华三通信技术有限公司 一种通过数据vlan关联主子环的方法和设备
CN105763483A (zh) * 2016-02-19 2016-07-13 杭州华三通信技术有限公司 一种报文发送方法和装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112118493A (zh) * 2020-08-24 2020-12-22 烽火通信科技股份有限公司 一种erps环网中实现组播协议的方法与系统
CN113645312A (zh) * 2021-08-25 2021-11-12 烽火通信科技股份有限公司 一种基于erps协议的子环网链路保护方法与装置

Also Published As

Publication number Publication date
CN109691031A (zh) 2019-04-26
CN109691031B (zh) 2020-11-06
EP3534571A1 (en) 2019-09-04
EP3534571A4 (en) 2019-10-16
EP3534571B1 (en) 2021-03-03
KR20190085039A (ko) 2019-07-17
KR102161422B1 (ko) 2020-10-05

Similar Documents

Publication Publication Date Title
US11411770B2 (en) Virtual port channel bounce in overlay network
US9887917B2 (en) Port extender
US9665530B2 (en) Method and system for implementing elastic network interface and interconnection
WO2020134739A1 (zh) 配置无缝双向转发检测sbfd机制的方法和装置
WO2018090210A1 (zh) 业务报文传输方法及节点设备
WO2017071269A1 (zh) 业务流的转发路径的重定向方法、装置和业务流转发系统
WO2017157052A1 (zh) 基于隧道绑定的通信方法和网络设备
EP2911355B1 (en) Method and device for flow path negotiation in link aggregation group
WO2013113218A1 (zh) 相交环保护方法、设备和系统
CN103684953A (zh) 避免多连接到vpls传输网的以太网环路中流量损失方法、装置
US11356372B2 (en) Data traffic processing method, device, and system
KR20130032300A (ko) 빠른 ｌｓｐ 경보 메커니즘
WO2011113395A2 (zh) 一种负载分担方法和装置
US9124524B2 (en) System and method for priority based flow control between nodes
WO2016169214A1 (zh) 一种隧道保护切换的方法和装置
CN107018072B (zh) 一种数据帧发送方法和接入设备
EP3462681B1 (en) Apparatus and method for transmitting multicast service
JP2008054058A (ja) データ伝送方法及び装置
US20110128892A1 (en) Avoiding high-speed network partitions in favor of low-speed links
WO2019071585A1 (zh) 路径切换过程中快速恢复业务的方法、装置和系统
WO2021082820A1 (zh) 双归接入时选择切换为工作状态的端口的方法和设备
WO2024140374A1 (zh) 信息处理方法、设备和存储介质
KR101260646B1 (ko) 데이터 전달 방법 및 이를 이용한 네트워크 시스템
KR20140131480A (ko) 루트화된 다점 연결 네트워크에서 보호절체 방법 및 장치
JP2002344462A (ja) 通信装置及び通信ネットワークシステム

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20197016997

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2016921924

Country of ref document: EP

Effective date: 20190529