JP6541434B2 - Relay device and relay system - Google Patents

Description

  The present invention relates to a relay apparatus and a relay system, for example, to a relay system provided with a PBB (Provider Backbone Bridge) network and an EoE (Ethernet over Ethernet) network, and a relay apparatus installed at the boundary between the PBB network and the EoE network.

  For example, Patent Document 1 shows a switching hub that converts a PBB frame and an EoE frame. Specifically, the switching hub is configured such that the BVID (Backbone VLAN ID) or ISID (backbone Service Instance VLAN ID) included in the PBB frame and the EID (Extended) included in the EoE frame are transmitted via the internal VID (VLAN ID). Converts ID) and SVID (Service provider VLAN ID).

  In addition, according to Patent Document 2, between a relay device installed in a PB (Provider Bridge) network and a relay device installed in a PBB network, Ethernet (registered trademark) is based on the Operation Administration and Maintenance (OAM) standard. A network is shown that allows communication of control frames. Specifically, if the relay device (core switch) installed in the PBB network is an identifier representing an Ethernet OAM frame, even if the destination BMAC address is a frame addressed to itself, that frame is used. Perform predetermined processing without discarding.

JP 2011-120032 A JP, 2013-201779, A

  For example, a MAC-in-MAC method is known as a technology for realizing wide area Ethernet. The MAC-in-MAC scheme further encapsulates the number of VLANs by encapsulating a MAC (Media Access Control) frame for customers with a MAC frame for carriers, and switches in a wide area network (core switch) Is a technique for reducing the number of MAC addresses learned in As the MAC-in-MAC method, as disclosed in Patent Document 1, an EoE method and a PBB method based on IEEE802.1ah are known.

  Also, in the Ethernet network, as shown in Patent Document 2, a standard for maintenance and management called Ethernet OAM is used. The Ethernet OAM standard is standardized as "ITU-T Y. 1731", "IEEE 802.1 ag" or the like. The Ethernet OAM standard defines a function called LB (LoopBack) as one of the functions. This is a bi-directional connection between monitoring points called MEPs (Maintenance End Points), in which one MEP sends a Loop Back Message (LBM) frame and the other MEP sends back a LBR (Loop Back Reply) frame. It is a function to confirm.

  Here, in the PBB network based on the PBB method, each device (specifically, an LBM frame, an LBR frame, etc.) based on the Ethernet OAM standard is applied by applying, for example, the technology of Patent Document 2 or the like. Two-way connection between MEPs can be verified. On the other hand, in the EoE system, a unique control frame (referred to as an ECP (EoE Control Protocol) frame in this specification) for confirming such bidirectional connection is provided.

  As a result, for example, it may be difficult to confirm bidirectional connection between devices in the PBB network and devices in the EoE network. That is, by converting the encapsulation header of the PBB frame and the encapsulation header of the EoE frame using the technique of Patent Document 1 etc., it is possible to communicate user frames between the respective devices. However, since the control frame based on the Ethernet OAM standard and the ECP frame have different frame formats before the encapsulation header is added, it may be difficult to communicate the control frame.

  The present invention has been made in view of the foregoing, and one of its objects is to provide a relay apparatus and a relay system capable of confirming bidirectional connection between a PBB network and an EoE network. It is to do.

  The above and other objects and novel features of the present invention will be apparent from the description of the present specification and the accompanying drawings.

  Among the inventions disclosed in the present application, the outline of a typical embodiment will be briefly described as follows.

  The relay apparatus according to the present embodiment includes a PBB port connected to the PBB network, an EoE port connected to the EoE network, and a control frame processing unit. The control frame processing unit converts the ECP request frame received by the EoE port into an LBM frame and transmits it from the PBB port, and converts the LBR frame received by the PBB port into an ECP response frame. And the second process of transmitting from the EoE port. The ECP request frame and the ECP response frame are control frames for confirming a two-way connection in the EoE network, and include a message ID area for storing an identifier representing the correspondence between the request and the response. The LBM frame and the LBR frame are control frames based on the Ethernet OAM standard, and include a transaction ID area configured to be larger than the message ID area. Here, at the time of the first processing, the control frame processing unit stores the value of the message ID area of the ECP request frame in a partial area in the transaction ID area of the LBM frame, and the rest in the transaction ID area. Store a predetermined fixed value in the area. Further, at the time of the second process, the control frame processing unit stores the value of a partial area in the transaction ID area of the LBR frame in the message ID area of the ECP response frame.

  Among the inventions disclosed in the present application, the effects obtained by the typical embodiment can be briefly described. In the relay device and the relay system, it is possible to confirm bidirectional connection between the PBB network and the EoE network. become.

FIG. 1 is a schematic view showing an example of the overall configuration of a relay system according to an embodiment of the present invention. FIG. 2 is a block diagram showing a schematic configuration example of main parts of a gateway device in the relay system of FIG. 1; FIG. 3 is a block diagram showing an example of a schematic configuration of main parts of a PBB line card in the gateway device of FIG. 2; FIG. 3 is a block diagram showing an example of a schematic configuration of main parts of an EoE line card in the gateway device of FIG. 2; (A) is a schematic diagram showing a structural example of FDB in FIG. 3 and FIG. 4, (b) is a schematic diagram showing a structural example of VID conversion table in FIG. 3, (c) is FIG. It is the schematic which shows the example of a structure of the VID conversion table in. (A) is a schematic view showing a structural example of a PBB frame, (b) is a schematic view showing a structural example of an EoE frame, (c) is a frame inside the device in the gateway device of FIG. It is the schematic which shows the structural example. (A) is a figure which shows the structural example of the control frame based on Ethernet OAM specification, (b) is a figure which shows the structural example of the TLV area | region in (a). It is a figure which shows the structural example of an ECP flame | frame. FIG. 7 is a flow chart showing an example of processing contents of an EoE control frame processing unit in the EoE line card of FIG. 4; FIG. 7 is a flow chart showing an example of processing contents of a control frame processing unit for PBB in the PBB line card of FIG. 3; FIG. 8 is a diagram showing an example of a schematic operation sequence when confirming bidirectional connection between a switch device in the PBB network and a switch device in the EoE network in the relay system of FIG. 1; It is a figure which shows an example of the rough operation sequence different from FIG. FIG. 12 is an explanatory view showing an example of conversion operation performed by the gateway device in FIG. FIG. 13 is an explanatory view showing an example of conversion operation performed by the gateway device in FIG. 12; The relay apparatus by Embodiment 2 of this invention WHEREIN: It is the schematic which shows the structural example of the one part.

  In the following embodiments, when it is necessary for the sake of convenience, it will be described by dividing into a plurality of sections or embodiments, but unless specifically stated otherwise, they are not mutually unrelated, one is the other Some or all of the variations, details, supplementary explanations, etc. are in a relation. Further, in the following embodiments, when referring to the number of elements (including the number, numerical value, quantity, range, etc.), it is particularly pronounced and clearly limited to a specific number in principle. Except for the specific number, it is not limited to the specific number, and may be more or less than the specific number.

  Furthermore, in the following embodiments, the constituent elements (including element steps and the like) are not necessarily essential unless explicitly stated or considered to be obviously essential in principle. Needless to say. Similarly, in the following embodiments, when referring to the shapes, positional relationships and the like of components etc., the shapes thereof are substantially the same unless particularly clearly stated and where it is apparently clearly not so in principle. It is assumed that it includes things that are similar or similar to etc. The same applies to the above numerical values and ranges.

  Hereinafter, embodiments of the present invention will be described in detail based on the drawings. In all the drawings for describing the embodiments, the same reference numeral is attached to the same member in principle, and the repetitive description thereof will be omitted.

Embodiment 1
<< General configuration of relay system >>
FIG. 1 is a schematic diagram showing an example of the entire configuration of a relay system according to an embodiment of the present invention. The relay system shown in FIG. 1 includes a PBB network 10 in which communication based on the PBB method is performed, an EoE network 20 in which communication based on the EoE method is performed, and a gateway device installed at the boundary between the PBB network 10 and the EoE network 20 ( Relay apparatus) GW. In the PBB network 10, a switch device (for example, Ethernet switch) SWp that relays an encapsulated frame based on the PBB method (herein referred to as a PBB frame) is installed. In the EoE network 20, a switch device (for example, Ethernet switch) SWe that relays an encapsulated frame based on the EoE scheme (herein referred to as an EoE frame) is installed.

  The gateway device (relaying device) GW is responsible for relaying frames between the PBB network 10 and the EoE network 20. Specifically, the gateway apparatus GW mutually converts the PBB frame and the EoE frame by mutually converting the PBB encapsulated header and the EoE encapsulated header in the same manner as in the case of Patent Document 1. In addition to this, the gateway device GW executes control frame conversion processing in order to realize confirmation of bidirectional connection between the switch device SWp and the switch device SWe, which will be described in detail later.

<< Schematic Configuration and General Operation of Gateway Device (Relay Device) >>
FIG. 2 is a block diagram showing a schematic configuration example of main parts of the gateway device in the relay system of FIG. Here, the gateway apparatus GW shown in FIG. 2 is a chassis type switch apparatus which also has a function as an Ethernet switch. The gateway apparatus GW includes a PBB line card LCp, an EoE line card LCe, and a frame relay path 130.

  The PBB line card LCp includes a PBB port Pp1 connected to the PBB network 10 to transmit or receive PBB frames, and an internal port Pi1 connected to the frame relay path 130. The EoE line card LCe includes an EoE port Pe1 connected to the EoE network 20 to transmit or receive an EoE frame, and an internal port Pi2 connected to the frame relay path 130.

  Here, the gateway apparatus GW includes one PBB line card LCp and one EoE line card LCe, but may include one or both of them. In addition, although each of the PBB line card LCp and the EoE line card LCe includes one external port (ie, the PBB port Pp1 and the EoE port Pe1) here, each of the PBB line card LCp and the EoE line card LCe may have a plurality. The frame relay path 130 is responsible for relaying frames between each line card. The frame relay route 130 may be configured by, for example, a mesh communication line or may be configured by a fabric switch.

  FIG. 3 is a block diagram showing an example of a schematic configuration of main parts of a PBB line card in the gateway device of FIG. FIG. 4 is a block diagram showing an example of a schematic configuration of main parts of an EoE line card in the gateway device of FIG. 5 (a) is a schematic view showing an example of the structure of the FDB in FIGS. 3 and 4, and FIG. 5 (b) is a schematic view showing an example of the structure of the VID conversion table in FIG. c) is a schematic view showing a structural example of the VID conversion table in FIG. 6 (a) is a schematic view showing a structural example of a PBB frame, FIG. 6 (b) is a schematic view showing a structural example of an EoE frame, and FIG. 6 (c) is a gateway apparatus of FIG. It is the schematic which shows the structural example of the flame | frame inside the apparatus in.

  First, the PBB frame used in the PBB network 10 of FIG. 1 has a structure in which a predetermined non-encapsulated frame (Ethernet frame) (not shown) is encapsulated by the PBB encapsulation header 300 as shown in FIG. ing. The PBB encapsulation header 300 includes a destination encapsulation address B-DA representing a device in the PBB network 10 to be a destination, and a transmission source encapsulation address B-SA representing a device in the PBB network 10 to be a transmission source. , B-TAG and I-TAG. In B-TAG, BVID (Backbone VLAN ID) is included, and in I-TAG, ISID (backbone Service Instance VLAN ID) is included.

  Further, the EoE frame used in the EoE network 20 of FIG. 1 has a structure in which a predetermined non-encapsulated frame (Ethernet frame) not shown is encapsulated by an EoE encapsulation header 310 as shown in FIG. ing. The EoE encapsulation header 310 includes a destination encapsulation address E-DA representing a device in the EoE network 20 as a destination, and a transmission source encapsulation address E-SA representing a device in the EoE network 20 as a transmission source. , S-TAG and E-TAG. The S-TAG contains a Service Provider VLAN ID (SVID), and the E-TAG contains an EID (Extended ID).

  Here, the PBB line card LCp shown in FIG. 3 includes the PBB relay processing unit 112 and the PBB control frame processing unit 113 in addition to the PBB port Pp1 and the internal port Pi1. The PBB relay processing unit 112 includes an FDB (Forwarding DataBase) and a VID conversion table 114. As shown in FIG. 5B, the VID conversion table 114 holds the correspondence between the internal VLAN identifier IVID set in advance and the BVID and ISID.

  As shown in FIG. 5A, the FDB holds the correspondence between the MAC address (for example, the address for encapsulation), the internal VLAN identifier IVID, and the port identifier. In FIG. 5A, for example, {Pp1} represents the identifier of the PBB port Pp1, and similarly, in the present specification, {AA} represents the identifier of “AA”.

  The PBB relay processing unit 112 learns information on the transmission source of the received frame by using such an FDB and VID conversion table 114, and further searches for a destination port of the received frame. For example, when the PBB relay processing unit 112 receives the PBB frame as described in FIG. 6A at the PBB port Pp1, first, based on the VID conversion table 114, the PBB relay processing unit 112 corresponds to the BVID and ISID of the frame. Acquire the internal VLAN identifier IVID.

  Next, the PBB relay processing unit 112 learns the B-SA of the frame in association with the acquired internal VLAN identifier IVID and the reception port identifier of the frame (here, {Pp1}) in the FDB. The PBB relay processing unit 112 also searches the FDB using the B-DA of the frame and the acquired internal VLAN identifier IVID as a search key, and acquires a port identifier (that is, a destination port identifier). Then, the PBB relay processing unit 112 adds the device internal header 320 as shown in FIG. 6C to the decapsulated frame included in the PBB frame, and sends it to the PBB control frame processing unit 113. Send.

  The device internal header 320 includes an internal VLAN identifier IVID in addition to the B-DA and B-SA contained in the PBB frame, as shown in FIG. 6 (c). Although not shown, the device internal header 320 further includes a receiving port identifier and a destination port identifier.

  The control frame processing unit 113 for PBB transmits the frame from the relay processing unit 112 for PBB as it is to the internal port Pi1. When the frame received by the internal port Pi1 is a control frame, the PBB control frame processing unit 113 performs control frame conversion processing as described later with reference to FIG.

  As shown in FIG. 4, the EoE line card LCe includes an EoE relay processing unit 122 and an EoE control frame processing unit 123 in addition to the EoE port Pe1 and the internal port Pi2. The EoE relay processing unit 122 includes the FDB as described in FIG. 5A and the VID conversion table 124. The VID conversion table 124 holds, as shown in FIG. 5C, the correspondence between the internal VLAN identifier IVID set in advance and the SVID and EID.

  The EoE relay processing unit 122 learns information on the transmission source of the received frame using the FDB and VID conversion table 124 as in the case of the PBB relay processing unit 112, and further, the destination of the received frame Search for the port of. Briefly described, when the EoE relay processing unit 122 receives an EoE frame as described in FIG. 6B at the EoE port Pe1, the EoE relay processing unit 122 copes with the SVID and EID of the frame based on the VID conversion table 124. To obtain an internal VLAN identifier IVID.

  In addition, the EoE relay processing unit 122 learns the E-SA of the frame to the FDB in association with the internal VLAN identifier IVID and the reception port identifier (here, {Pe1}), and the E-DA of the frame and the internal The FDB is searched using the VLAN identifier IVID as a search key. Based on these, the EoE relay processing unit 122 transmits a frame including the E-DA, E-SA, internal VLAN identifier IVID, reception port identifier, and destination port identifier as the device internal header 320 to the EoE control frame processing unit 123 Do.

  The EoE control frame processing unit 123 transmits the frame from the EoE relay processing unit 122 as it is to the internal port Pi2. When the frame received by the internal port Pi2 is a control frame, the EoE control frame processing unit 123 performs control frame conversion processing as described later with reference to FIG.

  Here, the conversion operation from PBB frame to EoE frame will be briefly described, for example, in the case where the destination port identifier of the PBB frame received by the PBB port Pp1 is the port identifier {Pe1} of the EoE port Pe1. Do. Further, it is assumed that the PBB frame is not a control frame but a user frame, and the frame relay path 130 in FIG. 2 is a fabric switch.

  First, as described above, the PBB relay processing unit 112 processes the frame including the B-DA and B-SA, the internal VLAN identifier IVID, the reception port identifier, and the destination port identifier as the apparatus internal header 320 in the PBB control frame process. It transmits to the frame relay route 130 via the unit 113 and the internal port Pi1. The frame relay path 130 relays the frame to the EoE line card LCe based on the destination port identifier (here, {Pe1}) included in the device internal header 320 of the frame.

  The EoE line card LCe receives the frame at the internal port Pi2, and transmits the frame to the EoE relay processing unit 122 via the EoE control frame processing unit 123. The EoE relay processing unit 122 defines B-DA and B-SA included in the device internal header 320 of the frame as E-DA and E-SA, respectively. Further, the EoE relay processing unit 122 determines the SVID and the EID from the internal VLAN identifier IVID contained in the device internal header 320 of the frame based on the VID conversion table 124. Accordingly, the EoE relay processing unit 122 generates an EoE frame, and transmits the EoE frame to a port based on the destination port identifier (here, {Pe1}).

  It is desirable that the EoE relay processing unit 122 learns its own FDB even when the frame is received at the internal port Pi2 as described above. Although the learning of the FDB is not necessarily limited, for example, the PBB relay processing unit 112 separately generates a learning frame including information on the transmission source of the frame, and transmits the learning frame to another line card. You can do it in

  Further, although the FDB of FIG. 5A holds the encapsulation address, it may hold the customer address in addition to this. In this case, when learning the FDB, the customer address and the encapsulation address are learned, and when searching the FDB, the customer address or the encapsulation address becomes the search key. Furthermore, although the conversion operation from the PBB frame to the EoE frame has been described here, the same is true for the conversion operation from the EoE frame to the PBB frame. In this case, the PBB relay processing unit 112 generates a PBB frame (in other words, a conversion operation).

<< Structure of control frame >>
FIG. 7A is a view showing an example of the structure of a control frame based on the Ethernet OAM standard, and FIG. 7B is a view showing an example of the structure of the TLV region in FIG. 7A. A control frame (Ethernet OAM frame) 400 shown in FIG. 7A is an unencapsulated frame, and includes a destination customer address C-DA, a transmission source customer address C-SA, an Ethernet type, an MEL + version, an operation code, and a flag. , TLV offset, TLV, and FCS regions. An identifier indicating that it is an Ethernet OAM frame is stored in the Ethernet type area.

  A maintenance domain level (MEL) based on the Ethernet OAM standard and a predetermined protocol version value are stored in the MEL (MEG Level) + version area. In the opcode area, an identifier for identifying the above-described LBM frame, LBR frame or the like is stored. In the flag area and the TLV offset area, predetermined values based on the Ethernet OAM standard are stored. A code for error detection and correction is stored in a frame check sequence (FCS) area.

  The TLV area 400a stores the operation content of the Ethernet OAM frame according to the value of the op code area. For example, when identifiers of LBM frames and LBR frames (herein, LBM frames and LBR frames are collectively referred to as OAM_LB frames) are stored in the operation code area, the TLV area 400a of the OAM_LB frame is shown in FIG. The structure is as shown in b).

  In FIG. 7B, the TLV area 400a of the OAM_LB frame includes a transaction ID area 400a1, an optional TLV area 400a2, and an end TLV area. The transaction ID area 400a1 is an area of 4 bytes, and in this area, a transaction identifier representing the correspondence between the request and the response is stored. The optional TLV area 400a2 stores arbitrary data according to the needs of the user. The end TLV area stores predetermined values based on the Ethernet OAM standard.

  FIG. 8 is a diagram showing an example of the structure of an ECP frame. The ECP frame 410 shown in FIG. 8 includes EoE encapsulation header, subtype, version, opcode, subcode, message ID, sequence number, reply ID, chassis ID, port ID, pad, and FCS areas. In the EoE encapsulation header area, the EoE encapsulation header 310 shown in FIG. 6B is stored. In the EoE frame, the user frame and the ECP frame are distinguished by a not-shown TPID included in the E-TAG in FIG. 6 (b). The subtype area of FIG. 8 stores an identifier (for example, an identifier representing that it is an ECP frame for confirming communication normality) that defines the function of the ECP frame. In the opcode area and the subcode area, identifiers for identifying ECP request frames, ECP response frames, and the like are stored.

  The message ID area 410a is a 2-byte area, in which an identifier representing the correspondence between the request and the response is stored. The reply ID MAC address is stored in the reply ID area, the name of the switch that transmitted the ECP frame is stored in the chassis ID, and the port number that transmitted the ECP frame is stored in the port ID. The pad area 410b stores arbitrary data according to the user's needs.

  As described above, in the Ethernet OAM frame 400 used in the PBB network 10 and the ECP frame 410 used in the EoE network 20, before the encapsulation header is added in addition to the frame format of the encapsulation header. The frame format of is also different. Therefore, for example, when it is desired to confirm the bidirectional connection between the switch device SWp in the PBB network 10 and the switch device SWe in the EoE network 20, the other party uses the value of the transaction ID area 400a1 and the message ID. The value of the area 410a can not be recognized correctly. As a result, it may be difficult to verify bidirectional connectivity between the PBB network and the EoE network. Therefore, it is useful to use the following method.

<< Operation of EoE / PBB control frame processing unit >>
FIG. 9 is a flow chart showing an example of processing contents of an EoE control frame processing unit in the EoE line card of FIG. 4. The EoE control frame processing unit 123 first determines whether or not the frame received by the internal port Pi2 is an OAM_LB frame based on the Ethernet type, op code, etc. of FIG. 7A (step S501). The frame received by the internal port Pi2 is a frame received by the PBB port Pp1 and relayed by the frame relay path 130, as in the case of the user frame described above.

  If the frame is an OAM_LB frame in step S501, the EoE control frame processing unit 123 determines whether the frame is an LBM frame or an LBR frame based on the operation code of FIG. 7A (step S502). If it is an LBM frame, the EoE control frame processing unit 123 converts the LBM frame into an ECP request frame (step S 503, third process), and transmits it to the EoE port Pe 1 through the EoE relay processing unit 122. It transmits (step S505, 3rd processing).

  On the other hand, if it is determined in step S502 that the LBR frame is received, the EoE control frame processing unit 123 converts the LBR frame into an ECP response frame (step S504, second process), and transmits it through the EoE relay processing unit 122. It transmits from EoE port Pe1 (step S505, second processing). If the frame is not an OAM_LB frame in step S501, the EoE control frame processing unit 123 executes predetermined communication processing without performing such conversion processing (step S505).

  FIG. 10 is a flow chart showing an example of the processing content of the control frame processing unit for PBB in the PBB line card of FIG. 3. The control frame processing unit 113 for PBB first determines whether the frame received at the internal port Pi1 is an ECP_ping frame based on the sub-type of FIG. 8 or the like (step S511). The ECP_ping frame is a generic name of an ECP request frame (ECP request) and an ECP response frame (ECP reply / expire). The frame received by the internal port Pi1 is a frame received by the EoE port Pe1 and relayed by the frame relay path 130, as in the case of the user frame described above.

  If it is an ECP_ping frame in step S511, the control frame processing unit 113 for PBB determines whether it is an ECP request frame or an ECP response frame based on the opcode, subcode, etc. of FIG. 8 (step S512). If it is an ECP request frame, the PBB control frame processing unit 113 converts the ECP request frame into an LBM frame (step S513, first processing), and the PBB port Pp1 via the PBB relay processing unit 112. To the transmission (step S515, first processing).

  On the other hand, when it is the ECP response frame in step S512, the PBB control frame processing unit 113 converts the ECP response frame into an LBR frame (step S514, fourth process), and transmits it via the PBB relay processing unit 112. Then, it transmits from the PBB port Pp1 (step S515, fourth processing). When the frame is not an ECP_ping frame in step S511, the PBB control frame processing unit 113 executes predetermined communication processing without performing such conversion processing (step S515).

  FIG. 11 is a diagram showing an example of a schematic operation sequence at the time of confirming bidirectional connection between the switch device SWp in the PBB network and the switch device SWe in the EoE network in the relay system of FIG. 1; is there. FIG. 13 is an explanatory view showing an example of the conversion operation performed by the gateway device in FIG. FIG. 11 shows an operation sequence when the switch device SWe in the EoE network transmits an ECP request frame to the switch device SWp in the PBB network.

  In FIG. 11 and FIG. 13, first, the switch device SWe in the EoE network transmits an ECP request frame. In the ECP request frame, the destination encapsulation address E-DA is an encapsulation address of the switch device SWp, and the transmission source encapsulation address E-SA is an encapsulation address of the switch device SWe. Further, a predetermined value (here, “C”) is stored in the message ID area 410a, and an arbitrary value is stored in the pad area 410b.

  The gateway apparatus (relay apparatus) GW (specifically, the control frame processing unit 113 for PBB) receives the ECP request frame, and converts the ECP request frame into an LBM frame according to step S513 of FIG. S601, first processing). At this time, as shown in FIG. 13, the control frame processing unit 113 for PBB sets the value of the message ID area 410a of the ECP request frame to a partial area (for example, lower 2 bytes) in the transaction ID area 400a1 of the LBM frame. Store in). In addition, the control frame processing unit 113 for PBB stores a predetermined fixed value (for example, 0x0000) in the remaining area (for example, upper 2 bytes) in the transaction ID area 400a1.

  In addition, in step S601, as shown in FIG. 13, the PBB control frame processing unit 113 stores the value of the pad area 410b of the ECP request frame in the optional TLV area 400a2 of the LBM frame. Furthermore, the control frame processing unit 113 for PBB is configured to transmit the destination customer address C-DA and the transmission source customer address C-SA in the LBM frame of FIG. 7A to the destination encapsulation address E-SA of the ECP request frame. And the transmission source encapsulation address E-SA. The values of the other areas in the LBM frame of FIG. 7A are predetermined values.

  The control frame processing unit 113 for PBB transmits the LBM frame generated in this way from the PBB port Pp1 via the relay processing unit 112 for PBB. At this time, based on the device internal header 320 shown in FIG. 6C, the PBB relay processing unit 112 uses the PBB encapsulated header 300 shown in FIG. 6A in the LBM frame (unencapsulated frame). Add That is, the relay processing unit 112 for PBB transmits the source encapsulation address E-SA and the destination encapsulation address E-DA of the received ECP request frame to the source encapsulation address B-SA and the LBM frame respectively. Address encapsulation address B-DA is determined.

  Next, the switch device SWp in the PBB network receives the LBM frame from the gateway device GW. The switch device SWp responds to the LBR frame because the destination receives the LBM frame addressed to the own device (step S602). Specifically, for example, the switch device SWp stores the source customer address C-SA in the LBM frame in the destination customer address C-DA, stores the own device address etc. in C-SA, and changes the operation code. Then, the LBR frame is generated by storing the same value as the LBM frame (here, 0x0000 + 'C') in the transaction ID area 400a1. The LBR frame actually stores the source encapsulation address B-SA in the LBM frame in the destination encapsulation address B-DA, and the own device address etc. as the source encapsulation address B-SA. The PBB encapsulation header 300 as stored in is added.

  Subsequently, the gateway apparatus GW (specifically, the EoE control frame processing unit 123) receives the LBR frame, and converts the LBR frame into an ECP response frame according to step S504 of FIG. 9 (step S603, Second process). At this time, as shown in FIG. 13, the EoE control frame processing unit 123 sets the value ('C' in this case) of a partial area (here, lower 2 bytes) in the transaction ID area 400a1 of the LBR frame. , ECP response frame stored in the message ID area 410a.

  In addition, in step S603, the EoE control frame processing unit 123 stores the value of the option TLV area 400a2 of the LBR frame in the pad area 410b of the ECP response frame, as shown in FIG. In the ECP response frame shown in FIG. 8, the values of the EoE encapsulated header area and the other areas excluding the above-described message ID area 410a and pad area 410b are predetermined values.

  The EoE control frame processing unit 123 transmits the ECP response frame thus generated from the EoE port Pe1 via the EoE relay processing unit 122. At this time, the EoE relay processing unit 122 determines the EoE encapsulated header 310 of the ECP response frame based on the device internal header 320 shown in FIG. 6C. That is, the EoE relay processing unit 122 respectively transmits the source encapsulation address B-SA and the destination encapsulation address B-DA of the received LBR frame to the source encapsulation address E-SA of the ECP response frame and the ECP response frame. The address is defined as the destination encapsulation address E-DA. Thereafter, the switch device SWe can confirm the bidirectional connection by receiving an ECP response frame addressed to the own device whose value in the message ID area 410a is 'C'.

  12 is a schematic operation sequence different from that in FIG. 11 in confirming bidirectional connection between the switch device SWp in the PBB network and the switch device SWe in the EoE network in the relay system of FIG. It is a figure which shows an example. FIG. 14 is an explanatory drawing showing an example of the conversion operation performed by the gateway device in FIG. FIG. 12 shows an operation sequence when the switch device SWp in the PBB network transmits an LBM frame to the switch device SWe in the EoE network.

  In FIG. 12 and FIG. 14, first, the switch device SWp in the PBB network transmits an LBM frame. In the LBM frame, the destination encapsulation address B-DA and the destination customer address C-DA are both MAC addresses of the switch device SWe, and a source encapsulation address B-SA and a source customer address C-SA. Are both MAC addresses of the switch device SWp. Also, a predetermined value (here, “A”) is stored in the transaction ID area 400 a 1, and an arbitrary value is stored in the option TLV area 400 a 2.

  The gateway apparatus (relay apparatus) GW (specifically, the EoE control frame processing unit 123) receives the LBM frame, and converts the LBM frame into an ECP request frame by the step S503 of FIG. 9 and the like (step S611). , Third process). At this time, as shown in FIG. 14, the EoE control frame processing unit 123 sets the value of the TLV area 400a including the value of the transaction ID area 400a1 of the LBM frame and the value of the optional TLV area 400a2 to the pad of the ECP request frame. It stores in the area 410b. Furthermore, as shown in FIG. 14, the EoE control frame processing unit 123 sets the value of the message ID area 410a of the ECP request frame to an arbitrary value (for example, 'B').

  In the ECP request frame shown in FIG. 8, the values of the EoE encapsulated header area and the other areas excluding the above-described message ID area 410a and pad area 410b are predetermined values. The EoE control frame processing unit 123 transmits the ECP request frame thus generated from the EoE port Pe1 via the EoE relay processing unit 122. At this time, the EoE relay processing unit 122 determines the EoE encapsulation header 310 of the ECP request frame based on the device internal header 320 shown in FIG. 6C. That is, the EoE relay processing unit 122 respectively transmits the source encapsulation address B-SA and the destination encapsulation address B-DA of the received LBM frame to the source encapsulation address E-SA of the ECP request frame and the transmission source encapsulation address E-SA of the ECP request frame. The address is defined as the destination encapsulation address E-DA.

  Next, the switch device SWe in the EoE network receives the ECP request frame from the gateway device GW. The switch device SWe responds to the ECP response frame because the destination receives the ECP request frame addressed to itself (step S612). Specifically, for example, the switch device SWe stores the source encapsulation address E-SA in the ECP request frame in the destination encapsulation address E-DA, and the own device address etc. as the source encapsulation address E. The ECP response frame is generated by storing in the SA, changing the operation code, the subcode, etc., and storing the same value (here, 'B') as the ECP request frame in the message ID area 410a.

  Subsequently, the gateway apparatus GW (specifically, the control frame processing unit 113 for PBB) receives the ECP response frame, and converts the ECP response frame into an LBR frame in step S514 or the like of FIG. 10 (step S613). , 4th process). At this time, as shown in FIG. 14, the control frame processing unit 113 for PBB stores the values stored in the pad area 410b of the ECP response frame at step S611 (ie, the values of the transaction ID area 400a1 and the optional TLV area 400a2). Value) is stored in the TLV area 400a of the LBR frame. As a result, the value of the transaction ID area 400a1 in the LBM frame (here, 'A') and the value of the option TLV area 400a2 are restored in the LBR frame.

  In step S613, the PBB control frame processing unit 113 encapsulates the destination customer address C-DA and the transmission source customer address C-SA in the LBR frame of FIG. 7A into a destination encapsulation of the ECP response frame. Address E-DA and source encapsulation address E-SA. The values of the other areas in the LBR frame in FIG. 7A are predetermined values.

  The PBB control frame processing unit 113 transmits the LBR frame generated in this manner from the PBB port Pp1 via the PBB relay processing unit 112. At this time, the PBB relay processing unit 112 uses the PBB encapsulated header 300 shown in FIG. 6A in the LBR frame (unencapsulated frame) based on the device internal header 320 shown in FIG. 6C. Add Thereafter, the switch device SWp can confirm the bidirectional connection by receiving the LBR frame addressed to the own device whose value of the transaction ID area 400a1 is 'A'.

  As described above, when the relay device and the relay system according to the first embodiment confirm the bidirectional connection between the PBB network 10 and the EoE network 20, the control frame of the transmission source network is used as the destination network. Convert to an identifiable form. At this time, the relay apparatus stores the unique information included in the control frame representing the request in a form that can be restored in the converted control frame, and the unique information is stored when the response from the request destination is returned. Keeping the request and response consistent by restoring it. As a result, the value of the transaction ID area 400a1 and the value of the message ID area 410a can be correctly determined, and the bidirectional connection can be confirmed between the PBB network 10 and the EoE network 20.

  Here, in the first embodiment, as shown in FIG. 13, since the transaction ID area 400a1 is configured to be larger in size than the message ID area 410a, the value of the message ID area 410a is set in the transaction ID area 400a1. It is stored in a part of the area and used to restore it. However, in the reverse direction, the value of the transaction ID area 400a1 can not be stored in the message ID area 410a. Therefore, in the first embodiment, as shown in FIG. 14, in the reverse direction, the value of the transaction ID area 400a1 is stored in the pad area 410b, and a method of restoring it is used.

  Although FIG. 2 exemplifies the chassis type switch device, it may of course be a box type switch device. In this case, for example, the PBB control frame processing unit 113 of FIG. 3 and the EoE control frame processing unit 123 of FIG. 4 are configured as one control frame processing unit, and the PBB relay processing unit 112 of FIG. The fourth EoE relay processing unit 122 may be configured as one relay processing unit.

  Further, although the control frame is converted by the line card on the egress side here, it is possible to convert the control frame by the line card on the ingress side depending on the case. In this case, for example, when the destination port of the control frame received by the PBB port Pp1 is the EoE port Pe1, the PBB control frame processing unit 113 performs the conversion process of FIG. However, in this case, since it is necessary to determine the destination port, it is preferable to perform conversion using the line card on the egress side from the viewpoint of processing efficiency.

Second Embodiment
<< Schematic Configuration and General Operation of Gateway Device (Relay Device) (Modified Example) >>
FIG. 15 is a schematic view showing a configuration example of a part of the relay device according to the second embodiment of the present invention. The gateway device (relay device) GW illustrated in FIG. 15 includes an information conversion table 700. The information conversion table 700 holds the correspondence between the value of the transaction ID area and the value of the option TLV area, and the value of the message ID area and the value of the pad area.

  For example, when the gateway apparatus GW receives an ECP request frame as in the case of FIG. 13, the gateway apparatus GW holds the value of the message ID area 410 a and the value of the pad area 410 b in the information table 700. Then, the gateway apparatus GW arbitrarily determines the value of the transaction ID area 400a1 and the value of the option TLV area 400a2, and generates an LBM frame including the determined value. At this time, the gateway apparatus GW stores at least the determined value of the transaction ID area 400a1 in the information conversion table 700 in association with the value of the message ID area 410a and the value of the pad area 410b described above.

  On the other hand, when the gateway apparatus GW receives the LBR frame as in the case of FIG. 13, the gateway apparatus GW searches the information conversion table 700 using the value of the transaction ID area 400a1 as a search key, and the value of the message ID area and the pad area Get the value. Then, the gateway apparatus GW generates an ECP response frame including the acquired value of the message ID area and the value of the pad area. Also in the case of FIG. 14, the gateway apparatus GW temporarily holds unique information in the information conversion table 700 as in the case of FIG. 13, and when the response from the request destination is returned, the information conversion table Restore unique information using 700.

  As described above, it is possible to confirm bidirectional connection between the PBB network 10 and the EoE network 20 also by using the method of the second embodiment. However, from the viewpoint of resource reduction and the like, it is preferable to use a method of storing unique information not in the information conversion table 700 but in the control frame after conversion as in the first embodiment.

  As mentioned above, although the invention made by the present inventor was concretely explained based on an embodiment, the present invention is not limited to the above-mentioned embodiment, and can be variously changed in the range which does not deviate from the gist. For example, the above-described embodiments are described in detail in order to explain the present invention in an easy-to-understand manner, and are not necessarily limited to those having all the described configurations. Also, part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of one embodiment. . In addition, with respect to a part of the configuration of each embodiment, it is possible to add, delete, and replace other configurations.

10 PBB network 112 PBB relay processing unit 113 PBB control frame processing unit 114, 124 VID conversion table 122 EoE relay processing unit 123 EoE control frame processing unit 130 frame relay route 20 EoE network 300 PBB encapsulated header 310 EoE capsule Internal header 320 Device internal header 400 Ethernet OAM frame 400a TLV area 400a1 Transaction ID area 400a2 Option TLV area 410 ECP frame 410a Message ID area 410b Pad area 700 Information conversion table GW gateway apparatus LCe EoE line card LCp PBB line card Pe1 EoE Port Pi1, Pi2 Internal port Pp1 PBB port SWp, SWe Switch device

Claims (8)

A port for PBB connected to a PBB (Provider Backbone Bridge) network,
EoE port connected to EoE (Ethernet over Ethernet) network,
The first process of converting the ECP request frame received by the EoE port into an LBM frame and transmitting it from the PBB port, and the LBR frame received by the PBB port into an ECP response frame by the EoE A second process of transmitting from the E-port, a third process of converting the LBM frame received by the PBB port into the ECP request frame and transmitting from the EoE port, and the EoE port received by the EoE port A control frame processing unit that executes a fourth process of converting an ECP response frame into the LBR frame and transmitting the converted frame from the PBB port ;
Have
The ECP request frame and the ECP response frame are control frames for confirming a two-way connection in the EoE network, and a message ID area for storing an identifier representing correspondence between request and response, and optionally And a pad area capable of storing data of
The LBM frame and the LBR frame are control frames based on the Ethernet OAM standard, and include a transaction ID area configured to be larger than the message ID area,
The control frame processing unit
In the first process, the value of the message ID area of the ECP request frame is stored in a partial area in the transaction ID area of the LBM frame, and is stored in the remaining area in the transaction ID area. Stores the fixed value of
Upon the second processing, the value of the partial area of the transaction ID area of the LBR frame, stored in the message ID area of the ECP response frame,
In the third process, the value of the transaction ID area of the LBM frame is stored in the pad area of the ECP request frame, and the value of the message ID area of the ECP request frame is set to an arbitrary value.
At the time of the fourth process, a value stored in the pad area of the ECP response frame along with the third process is stored in the transaction ID area of the LBR frame.
Relay device. In the relay device according to claim 1 ,
The LBM frame and the LBR frame further comprise an optional TLV region based on Ethernet OAM standard,
The control frame processing unit
Further, during the first processing, the value of the pad area of the ECP request frame is stored in the optional TLV area of the LBM frame,
In the second processing, the value of the optional TLV area of the LBR frame is further stored in the pad area of the ECP response frame.
Relay device. In the relay device according to claim 1 ,
The LBM frame and the LBR frame further comprise an optional TLV region based on Ethernet OAM standard,
The control frame processing unit
In the third processing, the value of the optional TLV area of the LBM frame is further stored in the pad area of the ECP request frame,
Further, in the fourth process, a value stored in the pad area of the ECP request frame along with the third process is stored in the optional TLV area of the LBR frame.
Relay device. The relay device according to any one of claims 1 to 3 .
The relay device is
A line card for PBB comprising the port for PBB;
An EoE line card including the EoE port;
Frame relay route responsible for relaying frames between each line card,
Have
The PBB line card includes the control frame processing unit that executes the first process and the fourth process,
The EoE line card includes the control frame processing unit that executes the second process and the third process.
Relay device. PBB (Provider Backbone Bridge) network,
EoE (Ethernet over Ethernet) network,
A relay device installed at the boundary between the PBB network and the EoE network;
A relay system having
The relay device is
A port for PBB connected to the PBB network;
An EoE port connected to the EoE network;
The first process of converting the ECP request frame received by the EoE port into an LBM frame and transmitting it from the PBB port, and the LBR frame received by the PBB port into an ECP response frame by the EoE A second process of transmitting from the E-port, a third process of converting the LBM frame received by the PBB port into the ECP request frame and transmitting from the EoE port, and the EoE port received by the EoE port A control frame processing unit that executes a fourth process of converting an ECP response frame into the LBR frame and transmitting the converted frame from the PBB port ;
Have
The ECP request frame and the ECP response frame are control frames for confirming a two-way connection in the EoE network, and a message ID area for storing an identifier representing correspondence between request and response, and optionally And a pad area capable of storing data of
The LBM frame and the LBR frame are control frames based on the Ethernet OAM standard, and include a transaction ID area configured to be larger than the message ID area,
The control frame processing unit
In the first process, the value of the message ID area of the ECP request frame is stored in a partial area in the transaction ID area of the LBM frame, and is stored in the remaining area in the transaction ID area. Stores the fixed value of
Upon the second processing, the value of the partial area of the transaction ID area of the LBR frame, stored in the message ID area of the ECP response frame,
In the third process, the value of the transaction ID area of the LBM frame is stored in the pad area of the ECP request frame, and the value of the message ID area of the ECP request frame is set to an arbitrary value.
At the time of the fourth process, a value stored in the pad area of the ECP response frame along with the third process is stored in the transaction ID area of the LBR frame.
Relay system. In the relay system according to claim 5 ,
The LBM frame and the LBR frame further comprise an optional TLV region based on Ethernet OAM standard,
The control frame processing unit
Further, during the first processing, the value of the pad area of the ECP request frame is stored in the optional TLV area of the LBM frame,
In the second processing, the value of the optional TLV area of the LBR frame is further stored in the pad area of the ECP response frame.
Relay system. In the relay system according to claim 5 ,
The LBM frame and the LBR frame further comprise an optional TLV region based on Ethernet OAM standard,
The control frame processing unit
In the third processing, the value of the optional TLV area of the LBM frame is further stored in the pad area of the ECP request frame,
Further, in the fourth process, a value stored in the pad area of the ECP request frame along with the third process is stored in the optional TLV area of the LBR frame.
Relay system. In the relay system according to any one of claims 5 to 7 ,
The relay device is
A line card for PBB comprising the port for PBB;
An EoE line card including the EoE port;
Frame relay route responsible for relaying frames between each line card,
Have
The PBB line card includes the control frame processing unit that executes the first process and the fourth process,
The EoE line card includes the control frame processing unit that executes the second process and the third process.
Relay system.

Images