JP5161050B2 - Continuity test method and network system - Google Patents

Description

  The present invention relates to a network continuity test, and more particularly to a continuity characteristic test method using Ether OAM.

  In recent years, networks using Ethernet (trademark registration, the same applies hereinafter) lines have become widespread and are provided at a low price. For networks using Ethernet lines, ITU-T (International Telecommunication Union-Telecommunication Sector) and IEEE (Institut of Electrical and Electronic Engineers) are used to detect faults in Ethernet lines. Also, APS (Automatic Protection Switching) for switching communication paths has been standardized. As a result, the fault tolerance of the Ethernet line is greatly improved. Networks using Ethernet lines are beginning to be applied to leased line services provided by communication carriers as carrier grade Ethernet.

  This leased line service is a communication service that requires extremely high reliability. Therefore, the provider of the leased line service needs to guarantee the QoS (Quality of Service) such as the contract bandwidth and the delay time defined in the SLA (Service Level Agreement) to the user. Therefore, the dedicated line service provider measures the end-end continuity characteristics (throughput, transfer delay, frame loss number, etc.) of the network for providing the service, and sets the bandwidth control function of each device. It is necessary to confirm that there is no error or traffic bias in the network. Usually, the leased line service is a service that connects each user point-to-point. The user uses a dedicated device (user access device) installed at each user site in order to access the dedicated line service. This user access device is the end of the carrier network. The continuity characteristic test is performed between the opposing user access devices.

  There is a method of performing an end-end conduction characteristic test using a test-dedicated measuring device installed at each user site (see, for example, Patent Document 1).

  Further, in accordance with remote operation (In-band) from the carrier management network (network monitoring and control device), the user access device (gateway) generates a test signal corresponding to the request signal from the carrier management network, and the opposite user access There is a method in which a continuity characteristic test is executed between devices, and the result is notified to a carrier management network by In-band (for example, see Patent Document 2).

In Ether OAM, a TST (Test) frame for testing throughput and a DM (Delay Measurement) frame for testing delay time are defined. By using Ether OAM, a continuity characteristic test of the Ethernet line can also be executed (for example, see Non-Patent Document 1).
JP 2007-49602 A JP 2008-5480 A ITU-T recommendation 1731 (OAM functions and machinery for Ethernet based networks)

  According to the technique described in Patent Literature 1, it is possible to perform a continuity characteristic test between opposing user access devices. However, the service provider (maintenance manager) must go to the user site where the measuring instrument is installed and operate the measuring instrument. Therefore, there is a problem that human and time costs required for measurement are large.

  Moreover, according to the technique described in Patent Document 2, since the conduction characteristic test can be controlled by remote operation from the carrier management network, it is possible to reduce human and time costs required for the test. However, in the conduction characteristic test by remote operation described in Patent Document 2, only a simple test that transmits and receives several test frames for confirming connectivity can be executed.

  In the continuity characteristic test in Ethernet, it is necessary to measure test frame transmission / reception at a wire rate, bandwidth control, throughput, transfer delay, frame loss number, and the like.

  In order to test these conduction characteristics described above, the user access device must have a test function similar to that of the measuring instrument. If all the user access devices are provided with such a test function, the user access devices are expensive, and the unit price of the service to be provided increases.

  Therefore, depending on the technique described in Patent Document 2, it is not possible to execute a test for ensuring the communication quality required for the Ethernet line.

  In addition, in Ether OAM described in Non-Patent Document 1, two types of tests are required to measure throughput and delay time.

  The present invention has been made in view of the above-described problems, and does not use a measuring instrument, and further provides an end-end continuity characteristic test of an Ethernet line without providing an advanced test function in a user access device. It aims to be realized. It is another object of the present invention to simultaneously measure an end-end throughput and a delay time of an Ethernet line by using an Ether OAM test frame used for a continuity characteristic test.

A typical example of the present invention is as follows. That is, in a network system including a relay device configuring a core network and at least two access devices for connecting a user terminal to the core network, a connection for testing a connection between the two access devices In this test method, a management level for managing a connection test section is set for each device provided in the network, and a test frame of a first management level is returned to each access device. in the provided first been management level is set, the relay device to transfer the first management level of the test frame, and the first management level is different second management level In the method, the relay device transmits the first management level test frame, and the access device transmits the intermediate management frame. The test frame of the first management level sent from the device is folded back, the relay device transfers the test frame of the first management level received from the direction in which the test frame was sent, and the relay device The connection between the two access devices is confirmed by terminating the first management level test frame received from the direction opposite to the direction in which the test frame was transmitted.

  According to an embodiment of the present invention, the relay device can perform a continuity characteristic test between opposing user access devices without the user access device having an advanced test function.

  The outline of the present invention is as follows.

  In one embodiment of the present invention, a relay device that constitutes a relay network in which a plurality of user access devices are multiplexed has a test function and realizes an end-end conduction characteristic test using the relay device as a test start point.

  The relay device transfers the test frame to one user access device. The user access device that has received the test frame returns the test frame to the same port as the port to which the test frame was transferred. The relay apparatus transmits the folded test frame, and the test frame is transferred to the opposite user access apparatus. The opposite user access device returns the test frame to the port of the relay device to which the test frame has been transferred. The relay apparatus that is the test start point terminates the test frame that is returned from the opposite user access apparatus.

  In one embodiment of the present invention, VSP (Vendor Specific OAM), which is a message format unique to a device vendor, is used as a test frame. The relay apparatus serving as a test start point sends a test frame after adding a sequence number and a time stamp to the test frame. The relay device described above terminates the test frame transferred according to the path, and calculates the throughput and the delay time based on information such as a time stamp included in the test frame.

<Embodiment 1>
Hereinafter, a first embodiment of the present invention will be described with reference to FIGS. The first embodiment described below is one of the embodiments of the present invention and does not limit the present invention.

  FIG. 1 is an explanatory diagram illustrating an example of a conduction characteristic test according to the first embodiment of this invention.

  The core network includes a relay device 31-1, a relay device 31-2, and a relay network 33, and is managed by the carrier management network 32.

  The relay device 31-1 is connected to the relay network 33 and the access network 34-1, connected to the user access device 30-1 installed in the site 35-1 via the access network 34-1, and the user access device 30. -1 is managed. The user access device 30-1 connects a user terminal (not shown) installed at the site 35-1, and connects the user terminal to the core network via the access network 34-1.

  The relay device 31-2 is connected to the relay network 33 and the access network 34-2, and is connected to the user access device 30-2 installed in the site 35-2 via the access network 34-2. -2. The user access device 30-2 connects a user terminal (not shown) installed at the site 35-2, and connects the user terminal to the core network via the access network 34-2.

  Note that the relay device 31-1 and the relay device 31-2 have the same configuration, and in the following description, each relay device will be collectively referred to as the relay device 31 when the description applies to any of the relay devices. Also, the user access device 30-1 and the user access device 30-2 have the same configuration, and in the following description, when referring to any user access device, the user access devices are collectively referred to as the user access device. 30.

  In one embodiment of the present invention, the test frame 38 used for the continuity characteristic test is transmitted from, for example, the relay device 31-1, transferred to each node (relay device and user access device) according to the transfer path 39, and started the test. It is terminated at the relay device 31-1 that is a point (and an end point). In this specification, the relay device 31-1 is used as the test start point (and end point), but the relay device 31-2 may be used as the test start point (and end point). Further, the direction of the transfer path 39 may be reversed.

  For example, when the continuity characteristic test is executed according to the transfer path 39 shown in FIG. 1, the user access device 30 needs to return the received test frame 38. Further, the relay device 31 passes through the test frame 38, and in particular, the relay device 31-1 that is a test start point needs to terminate the test frame 38.

  In Ethernet OAM (Ethernet Operation Administration and Maintenance), which is a management function used for operation and maintenance of an Ethernet network, for example, the user access device 30 receives an Ether OAM frame and sends a response to the received Ether OAM frame to the transmission source Can wrap to port.

  When the destination MAC (Media Access Control) address of the received Ether OAM frame is a unicast address, the user access device 30 wraps the Ether OAM frame by switching the destination MAC address and the source MAC address. . If the destination MAC address of the received Ether OAM frame is a multicast address, the user access device 30 overwrites the destination MAC address with the source MAC address, and the source MAC address is set to the own device. Overwrite the Ether OAM frame by overwriting with.

  Further, in Ether OAM, each node (relay device and user access device) of the Ethernet network is set as a management point, and a management section (MEG: Maintenance Entity Group) is set between the management points. The management section (MEG) is hierarchized according to the MEG level. The MEG level is set at a management end point (MEP: MEG End Point) of each management section (MEG).

  For example, the EtE MEG level is set at the management end point that becomes End-End of the Ethernet network. In addition, a MEG level (section MEG level) lower than the above-mentioned EtE MEG level is set as a management point serving as a relay point.

  In the first embodiment, “EtE MEG level 36-1” is set in each user access device 30 that is End-End. As a result, the management section 37-1 between the user access devices 30 is a section in which “EtE MEG level 36-1” is set. The user access device 30 can be set to “section MEG level 36-2”.

  Further, the “section MEG level 36-2” is set in the relay device 31 located between the respective user access devices 30 facing each other. As a result, the management section 37-2 between the user access device 30-1 and the relay apparatus 31-1, the management section 37-3 between the relay apparatus 31-1 and the relay apparatus 31-2, and the relay apparatus A management section 37-4 between 31-2 and the user access device 30-2 is a section in which “section MEG level 36-2” is set.

  When executing the test, generally, the node transmits an Ether OAM frame to which the same MEG level as the MEG level set in the own device is given. Here, each node transmits an Ether OAM frame having a level higher than the MEG level set in the own device, terminates or loops back an Ether OAM frame at the same level as the set MEG level, and then goes from the set MEG level. The lower level Ether OAM frame is discarded as a level error.

  Therefore, for example, the Ether OAM frame to which the same MEG level as the MEG level (for example, “section MEG level 36-2”) set in the relay device 31-1 is assigned by the relay device 31-1 to the user access device 30. When it is sent to -1, the relay device 31-1 terminates the Ether OAM frame (response frame) returned from the user access device 30-1.

  As described above, in Ether OAM, when an Ether OAM frame is transmitted with a management point (for example, the relay device 31-1) between the End-End management sections in which the EtE MEG level is set as a test start point. In general, since the MEG level set at the test start point and the MEG level assigned to the Ether OAM frame are the same, the relay device 31-1 tests the conduction characteristics according to the transfer path 39 shown in FIG. I can't.

  Therefore, in the first embodiment, the relay apparatus 31-1 as the test start point transmits an Ether OAM frame (test frame) to which a MEG level higher than the MEG level set in the relay apparatus 31-1 is sent. To do. As a result, the carrier management network 32 can test the end-to-end conduction characteristics according to the transfer path 39 shown in FIG. Below, the outline | summary of the continuity characteristic test of this invention and the process of the test frame in each node are demonstrated.

  FIG. 2 is a sequence diagram showing a conduction characteristic test process according to the first embodiment of the present invention.

  First, the relay device 31-1 as the test start point executes the test frame insertion processing 41 in accordance with the test frame insertion command from the carrier management network 32, and sends the test frame 38-1 to the user access device 30-1. .

  In this case, the relay apparatus 31-1 gives the test frame 38-1 a multicast address, an identifier (Ether type) for identifying the test frame 38, and the like, and adds “EtE MEG level” to the payload of the test frame. 36-1 "and test information for acquiring the conduction characteristics in the management section (MEG). The configurations of the test frame 38 and the payload will be described later with reference to FIGS. 4 and 5 respectively. Details of the test frame insertion processing 41 will be described later with reference to FIG.

  Next, the user access device 30-1 that has received the test frame 38-1 executes a test frame loopback process 42-1, and transfers the test frame 38-2 to the relay device 31-1. In this case, the user access device 30-1 determines whether or not the test frame 38-1 is an OAM frame used for the continuity characteristic test, based on the identifier (ether type) assigned to the test frame 38-1. The user access device 30-1 overwrites the transmission source MAC address of the received test frame 38-1 with the address set in the own device, and then uses the test frame 38-1 as the test frame 38-2 and the relay device 31-1. Turn back to.

  Next, the relay device 31-1 compares the MEG level assigned to the test frame 38-2 with the MEG level set in the relay device 31-1. Since the MEG level (“EtE MEG level 36-1”) assigned to the test frame 38-2 is higher than the MEG level (“section MEG level 36-2”) set in the relay apparatus 31-1, relaying is performed. The device 31-1 performs the test frame transmission process 43-1 and transfers the test frame 38-3 to the relay device 31-2.

  Next, the relay device 31-2 executes a test frame transmission process 43-2. The test frame transmission process 43-2 is the same as the test frame transmission process 43-1. The relay device 31-2 transfers the test frame 38-4 to the user access device 30-2.

  Next, the user access device 30-2 that has received the test frame 38-4 executes a test frame loopback process 42-2. The test frame folding process 42-2 is the same as the test frame folding process 42-1. The user access device 30-2 overwrites the transmission source MAC address assigned to the test frame 38-4 with the address set in the own device, and then uses the test frame 38-4 as the test frame 38-5 and the relay device 31- Return to 2.

  Next, the relay device 31-2 executes a test frame transmission process 43-3. The test frame transmission process 43-3 is the same as the above-described test frame transmission processes 43-1 and 43-2. The relay device 31-2 transfers the test frame 38-6 to the relay device 31-1.

  Then, the relay device 31-1 that is the test end point executes the test frame end process 44. Here, the MEG level (“EtE MEG level 36-1”) assigned to the test frame 38-6 is higher than the MEG level (“section MEG level 36-2”) set in the relay apparatus 31-1. The relay apparatus 31-1 cannot terminate the test frame by the MEG level comparison process. Therefore, the relay device 31-1 determines whether or not the test frame 38-6 is the test frame 38-1 transmitted in the test frame insertion process 41 by using the coincidence filter. Terminate.

  Details of the test frame folding processing 42-1 and 42-2 will be described later with reference to FIG. Details of the test frame termination processing 44 will be described later with reference to FIG.

  FIG. 4 is an explanatory diagram illustrating the format of a test frame according to the first embodiment of this invention.

  The test frame 38 includes a destination MAC address 61, a transmission source MAC address 62, a VLAN ID 63, an ether type value 64, a payload 65, and a frame check sequence (FCS) 66.

  In the destination MAC address 61 and the source MAC address 62, the MAC address of the user access device 30 or the relay device 31 is set. A multicast MAC address may be set as the destination MAC address 61. In the VLAN ID 63, a VLAN identifier serving as a flow identifier is set. In the ether type value 64, an identifier indicating that the frame is an Ether OAM frame is set. The FCS 66 detects a frame error. The payload 65 will be described below.

  FIG. 5 is an explanatory diagram illustrating the format of the payload of the test frame according to the first embodiment of this invention.

  The user access device 30 and the relay device 31 that are nodes of the Ethernet network are devices that can execute Ether OAM for operation, maintenance, and management of the Ethernet network. The payload area of the test frame 38, which is an Ether OAM frame, includes a CCM (Connectivity Check Message) for confirming normality, an AIS (Alarm Indication Signal) for notifying other devices of failure occurrence, and other device vendor-specific messages. VSP (Vendor Specific OAM) is defined for exchanging. VSP can be used for vendor-specific purposes. In the first embodiment, an Ether OAM frame conforming to the VSP message format is used as the test frame 38.

  The payload (VSP payload) of the test frame 38 includes MEG (Maintenance Entity Group) level 701, Version 702, OpCode 703, flag 704, TLV (Type Length Value 8), 70, OUI (Organizationally Uni 70). , Timestamp 709, TLV 710, and End TLV 711.

  In the MEG level 701, a management level (MEG level) is set by the carrier management network. In version 702, an OAM version is set. In OpCode 703, a value indicating the type of the Ether OAM frame is set. For example, “51” indicating VSM (VSP Message: request control frame) or “50” indicating VSR (VSP Reply: response control frame) is set in OpCode 703.

  The flag 704 is an area that can be used independently by the vendor. In the recommendation shown in Non-Patent Document 1, the content of the flag 704 is not defined. In the TLV offset 705, a value indicating a length obtained by adding some of the regions from the MEG level 701 to the TLV 710 is set. The TLV offset 705 is an area that can be used independently by the vendor. Here, a length obtained by adding OUI 706, SubOpCode 707, sequence number 708, and time stamp 709 is set. In the OUI 706, an identifier indicating a device vendor is set. In the recommendation shown in Non-Patent Document 1, the content of OUI 706 is not defined. In SubOpCode 707, a value indicating the type of VSP is set. In the recommendation shown in Non-Patent Document 1, the contents of SubOpCode 707 are not defined. In the sequence number 708, a sequence number for measuring the number of frame losses of the conduction characteristic is set. In the time stamp 709, time information for measuring the transfer delay of the conduction characteristic is set. The TLV 710 is a data area of a payload and can be freely used by a vendor. In the End TLV 711, “0” indicating the end of the payload is set.

  Below, the structure of the relay apparatus 31 is demonstrated.

  FIG. 6 is a block diagram illustrating a configuration of the relay device according to the first embodiment of this invention.

  The user access device 30 may have the same configuration as the relay device 31 illustrated in FIG.

  The relay device 31 includes a plurality of network interface boards (NIFs) (800-1 to 800-N), a switch unit 810 connected to each NIF 800, and a node management unit 815 that manages the entire relay device.

  Each NIF 800 includes a plurality of input / output line interfaces (801-1 to 801-M) serving as communication ports. The relay device 31 is connected to other devices via these input / output line interfaces (communication ports). In the first embodiment, the input / output line interface 801 is a line interface for Ethernet.

  Each NIF 800 includes an input header processing unit 802 connected to the input / output line interface 801, an input frame buffer 803 connected to the input header processing unit 802, and an input scheduler 804 connected to the input frame buffer 803. . Each NIF 800 is connected to a plurality of SW interfaces (805-1 to 805-M) connected to the switch unit 810, an output header processing unit 806 connected to these SW interfaces 805, and an output header processing unit 806. An output frame buffer 807 and an output scheduler 808 connected to the output frame buffer 807.

  Here, a certain SW interface 805-I corresponds to the input / output line interface 801-I, and an input frame received by the input / output line interface (input port) 801-I passes through the SW interface 805-I. The data is transferred to the switch unit 810. The output frame transferred from the switch unit 810 to the SW interface 805-I is transferred to another device via the corresponding input / output line interface 801-I (output port).

  The input header processing unit 802, the input frame buffer 803, the input scheduler 804, the output header processing unit 806, the output frame buffer 807, and the output header processing unit 806 process input / output frames for each line. Will not mix.

  Further, the input / output line interface (input port) 801-I adds an in-device header to the received input frame.

  FIG. 3 is an explanatory diagram illustrating a format of the in-device header added to the input / output frame of the relay device according to the first embodiment of this invention.

  The in-device header 5 includes a flow ID 51, a reception port ID 52, a reception NIF ID 53, and a frame length 54.

  When the input / output line interface 801-I adds the in-device header 5 to the input frame, the flow ID 51 is blank. A value is set in the flow ID 51 by the input header processing unit 802.

  The input header processing unit 802 identifies the flow of each input frame, executes VLAN tag processing according to the identified flow, and adds the flow ID 51 to the in-device header 5. VLAN tag processing includes transparency, conversion, addition, and deletion of VLAN tags.

  In the VLAN tag processing, the input header processing unit 802 may overwrite the destination MAC address 61 and the source MAC address 62 with values set for each port, or values registered for each flow. May be overwritten. However, when overwriting with a value set for each port, the destination MAC address 61 is a multicast address. Even in this case, the relay network 33 is a VPN using only the VLAN, and the user access device 30 has a one-to-one connection. Therefore, the relay device 31 transfers the test frame 38 between the user access devices 30 facing each other. Can do.

  The input header processing unit 802 further analyzes the header of the input frame and determines whether or not the Ethertype value 64 shown in FIG. 4 is an Ether OAM value. If the Ethertype value 64 is not an Ether OAM value, that is, if the input frame is not an Ether OAM frame, the input header processing unit 802 stores the input frame as it is in the input frame buffer 803 for each line.

  On the other hand, when the ether type value 64 is an Ether OAM value, that is, when the input frame is an Ether OAM frame, the input header processing unit 802 performs payload analysis processing (S1201) described later with reference to FIG. Run.

  After the payload analysis process (S1201), the input header processing unit 802 transfers the input frame to the OAM control unit 811 or the test control unit 812, stores the input frame in the input frame buffer 803 for each line, or Discard the input frame.

  The input header processing unit 802 and the output header processing unit 806 use the VSP filter 809 in payload analysis processing (S1201) described later with reference to FIG. Here, the VSP filter 809 is a perfect match filter, and is a filter used for determining whether or not the input frame is the test frame 38 to be terminated.

  When a frame is stored in the input frame buffer 803, the input scheduler 804 reads the stored frame independently for each line and transfers it to the SW interface 805 corresponding to the line. Further, the input scheduler 804 schedules the frame inserted from the OAM control unit 811 or the test control unit 812 and the frame read from the input frame buffer 803. Here, the insertion frame is an Ether OAM frame that is a test frame 38 inserted from the relay apparatus 31 or an Ether OAM frame other than the test frame.

  After receiving the input frame from the SW interface 805 of each NIF 800, the switch unit 810 specifies the identifier (ID) of the output NIF and the identifier (ID) of the output port that are the transfer destination of the received input frame. Next, the switch unit 810 transfers the received input frame as an output frame to the SW interface 805 corresponding to the specified output port.

  Here, the switch unit 810 may use a frame transfer table in order to specify the output NIF and the identifier (ID) of the output port. The switch unit 810 refers to the frame transfer table, and by using a search key that combines a VLAN identifier (ID), an input NIF identifier (ID), and an input port identifier (ID), the output NIF identifier (ID) and A table entry indicating the identifier (ID) of the output port can be searched. Here, the identifier (ID) of the input NIF and the identifier (ID) of the input port are identifiers that are physically fixedly assigned to each SW interface 805 of each NIF 800, and which SW interface (input port) 805 the input frame is. It is uniquely determined depending on whether it was received at

  The switch unit 810 transfers the received input frame to the SW interface 805 of the transfer destination NIF 800 as an output frame. The SW interface 805 transfers the output frame to the output header processing unit 806. In the first embodiment, the input header processing unit 802 performs format conversion from an input frame to an output frame. Alternatively, the output header processing unit 806 may perform format conversion. When format conversion (header conversion) is performed in the input header processing unit 802, the output header processing unit 806 stores the output frame received from the SW interface 805 in the output frame buffer 807 as it is.

  When an output frame is stored in the output frame buffer 807, the output scheduler 808 reads the stored output frame independently for each line and outputs it to the input / output line interface 801 corresponding to the line. Further, the output scheduler 808 schedules the frame inserted from the OAM control unit 811 or the test control unit 812 and the frame read from the output frame buffer 807. Here, the insertion frame is created by the test control unit 812, the Ether OAM frame that is the test frame 38 inserted by the test control unit 812 into the output scheduler 808, and the OAM control unit 811, and the OAM control unit 811. Are Ether OAM frames other than the test frame 38 to be inserted into the output scheduler 808.

  The input / output line interface 801 (output port) transfers the output frame to another device after removing the in-device header 5 from the output frame.

  The OAM control unit 811 terminates an Ether OAM frame other than the test frame 38 received from the input header processing unit 802 or inserts it into each scheduler. The test control unit 812 executes termination processing of the test frame 38 received from the input header processing unit 802, loops back the received test frame to each scheduler, or inserts a test frame into each scheduler. However, in the first embodiment, the test control unit 812 included in the user access device 30 only wraps back to each scheduler without terminating the received test frame.

  The node management unit 815 is connected to the carrier management network 32 and controls the NIF management unit 813 provided in each NIF 800. The NIF management unit 813 controls the setting register 814. The setting register 814 sets each register value to be described later.

  The test frame insertion process (S900) executed by the test control unit 812 will be described below.

  FIG. 7 is a flowchart showing test frame insertion processing executed by the test control unit according to the first embodiment of the present invention.

  First, after detecting the insertion test start flag set in the setting register 814, the test control unit 812 of a certain NIF 800 (for example, NIF 800-1) starts the test frame insertion process 41 (S901). The start of test frame insertion test is instructed from the carrier management network 32 via the node management unit 815.

  Next, when transmitting the test frame 38, the test control unit 812 initializes a token bucket corresponding to the frame length of the test frame 38 set by the register value of the setting register 814 for bandwidth processing ( S902). After initializing the token bucket, the test control unit 812 executes frame creation processing (S1000). The frame creation process (S1000) will be described later with reference to FIG. In addition, the test control unit 812 adds the in-device header 5 to the created test frame 38.

  Next, the test control unit 812 determines whether the insertion direction of the test frame 38 into the scheduler is the Egress direction or the Ingress direction based on the insertion direction into the scheduler set in the register value ( S903).

  Here, the Egress direction is a direction in which, for example, in the NIF 800-1, the test frame 38 created by the test control unit 812 is inserted into the output scheduler 808 and transferred to the input / output line interface (output port) 801. . The Ingress direction is a direction in which, for example, in the NIF 800-1, the test frame 38 created by the test control unit 812 is inserted into the input scheduler 804 and transferred to the SW interface 805. The test frame 38 transferred to the SW interface 805 is transferred to a network interface board (for example, NIF 800-N) different from the NIF 800-1 by the switch unit 810, and is output via the output scheduler 808 of the NIF 800-N. The data is transferred from the input / output line interface (output port) 801 to the connection destination device.

  If it is determined in S903 that the insertion direction to the scheduler is the Egress direction (direction from the test control unit 812 to the output port 801), the test control unit 812 sets the register value set in the setting register 814 to the register value. Based on this, the setting values are written in the reception port ID 52 and the reception NIF ID 53 of the in-device header 5 (S904-1).

  Next, the test control unit 812 executes a band control process (S1100-1). The bandwidth control processing (S1100-1 and S1100-2) will be described later with reference to FIG.

  Next, the test control unit 812 inserts the test frame 38 into the output scheduler 808 (S906-1). Next, the test control unit 812 counts the number of inserted frames (S907).

  On the other hand, if it is determined in S903 that the insertion direction to the scheduler is the Ingress direction (the direction from the test control unit 812 to the SW interface 805), the test control unit 812 displays the register set in the setting register 814. Based on the value, the setting value is written in the receiving port ID 52 and the receiving NIF ID 53 of the in-device header 5 (S904-2).

  Next, the test control unit 812 executes band control processing (S1101-2), inserts the test frame 38 into the input scheduler 804 (S906-2), and counts the number of inserted frames (S907).

  The SW interface 805 that has received the test frame 38 transferred from the input scheduler 804 transfers the received test frame 38 to the switch unit 810. Here, the switch unit 810 specifies an output NIF and an output port for transferring the test frame 38 using, for example, a frame transfer table (not shown), and an NIF corresponding to the specified output port (for example, NIF800-N). The test frame 38 may be transferred to the SW interface 805.

  After S907, the test control unit 812 determines whether or not the insertion test start flag set by the setting register 814 is “1” (S908).

  When it is determined in S908 that the insertion test start flag is “0”, that is, when the end of the insertion test is instructed from the carrier management network 32, the test frame insertion processing is ended (S910).

  On the other hand, when it is determined in S908 that the insertion test start flag is “1”, that is, when the insertion test is continued, the test control unit 812 next registers the number of inserted frames in advance. It is determined whether or not it is equal to the number of frames set by the value (S909).

  If it is determined in S909 that the number of inserted frames is not equal to the set number of frames, the test control unit 812 returns to the processing of S1000 and continues from S1000 to S907 until the set number of frames is completely inserted. Repeat the process.

  On the other hand, when it is determined in S909 that the number of inserted frames is equal to the number of set frames, the test control unit 812 ends the test frame insertion process (S910).

  Next, the test frame creation process (S1000) shown in FIG. 7 will be described with reference to FIG.

  FIG. 8 is a flowchart illustrating test frame creation processing executed by the test control unit according to the first embodiment of this invention.

  After detecting the insertion test start flag, the test control unit 812 starts test frame creation processing (S1001). The test control unit 812 describes the set value in the frame length 54 of the in-device header 5 based on the register value set in the setting register 814. In addition, set values are described in the destination MAC address 61, the source MAC address 62, the VLAN ID 63, and the ether type value 64 of the test frame 38.

  Further, the test control unit 812 describes the set value in the MEG level 701 of the payload 65 based on the set register value, and “51” indicating that the test frame 38 includes VSM (VSP Message) in the OpCode 703. Describe. A multicast address is set as the register value for creating the destination MAC address 61. Further, “EtE MEG level 36-1” is set as the register value for creating the MEG level 701.

  In addition, the test control unit 812 writes values created by hardware counter values in the sequence number 708 and the time stamp 709. In other areas, values created from register values or hard fixed values are described (S1002). The test control unit 812 ends the process (S1003).

  Next, the bandwidth control processing (S1100-1 and S1100-2) shown in FIG. 7 will be described with reference to FIG.

  FIG. 9 is a flowchart illustrating a bandwidth control process executed by the test control unit according to the first embodiment of this invention.

  When starting the bandwidth control process (S1101), the test control unit 812 determines the timing for requesting frame insertion to the input scheduler 804 or the output scheduler 808 using a token.

  First, the test control unit 812 determines whether the token accumulated in the token bucket is equal to or longer than the frame length of the test frame 38 (S1103). If it is determined in S1103 that the token is not longer than the set frame length, the test control unit 812 adds the token (S1102), and returns to the processing of S1103. In S1102, the token is added every clock.

  If it is determined in S1103 that the token is longer than the set frame length, the test control unit 812 requests the input scheduler 804 or the output scheduler 808 to insert the test frame 38 and is stored in the token bucket. The token corresponding to the frame length of the test frame 38 is subtracted from the obtained token (S1104), and the process ends (S1105).

  Hereinafter, payload analysis processing (S1200) in the input header processing unit 802 of each node (relay device or user access device) will be described.

  FIG. 10 is a flowchart illustrating payload analysis processing executed by the input header processing unit according to the first embodiment of this invention.

If the input header processing unit 802 determines that the input frame is an Ether OAM frame based on the value of the ether type value 64 of the input frame, the input header processing unit 802 starts payload analysis processing of the input frame (S1201). Next, the input header processing unit 802 determines whether the MEP operation setting is valid or invalid based on the register value set by the setting register 814 (S1202). The MEP operation setting is set in the NIF setting register 814 including the test control unit 812 that executes the test frame loopback processing and termination processing in each node included in the transfer path 39. For example, even if the NIF 800 is provided in the relay apparatus 31 that is the test end point, the MEP operation setting is not set in the NIF 800 that is not related to the process of terminating the test frame 38.

  If it is determined in S1202 that the MEP operation setting is valid, the input header processing unit 802 acquires the MEG level 701 and the OpCode 703 from the payload 65 of the input frame that is an Ether OAM frame (S1203).

  Next, the input header processing unit 802 compares the obtained MEG level 701 of the input frame with the MEG level set in the own device, and determines whether the MEG level 701 of the input frame is equal to or lower than the MEG level of the own device. Determination is made (S1204).

  Each node terminates or wraps the input frame at its own device when the MEG level of the input frame is the same as the MEG level set for the own device. Further, when the MEG level of the input frame is higher than the MEG level set in the own apparatus, the input OAM frame is transmitted. When the MEG level of the input frame is lower than the MEG level set in the own apparatus, the input frame is an abnormal OAM frame, and thus the input frame is discarded.

  If it is determined in step S1204 that the MEG level 701 is equal to or lower than the MEG level set in the own device, the input header processing unit 802 then selects the MEG level in which the MEG level 701 is set in the own device. It is judged whether it is lower than (S1205).

  If it is determined in S1205 that the MEG level 701 is lower than the MEG level of the own apparatus, the input header processing unit 802 discards the input Ether OAM frame (S1206) and ends the payload analysis process. (S1213).

  On the other hand, if it is determined in S1205 that the MEG level 701 is not lower than the MEG level of the own device, that is, if the MEG level 701 is the same as the MEG level of the own device, the input header processing unit 802 The value of OpCode 703 acquired from the above is referred to, and it is determined whether the value of OpCode 703 is “51” (S1207).

  If it is determined in S1207 that the OpCode 703 is not “51”, that is, if the input frame is another Ether OAM frame that is not the test frame 38, the input header processing unit 802 converts the input frame into the OAM control unit 811. (S1208), and the process ends (S1213).

  On the other hand, if it is determined in S1207 that the OpCode 703 is “51”, that is, if the input frame is the test frame 38, the input header processing unit 802 transfers the input frame to the test control unit 812 ( In step S1211), the process ends (S1213).

  In S1204, when it is determined that the MEG level 701 is higher than the MEG level set in the own apparatus, the input header processing unit 802 next, based on the register value set by the setting register 814, It is determined whether the VSP filter setting is valid or invalid (S1209). Here, the VSP filter is a matching filter that determines whether or not an input frame matches a format that conforms to the VSP message format. In the first embodiment, by using this VSP filter, even if the MEG level 701 is higher than the MEG level set in the own device, the input frame is not transmitted and the node (for example, relay The device 31-1) can terminate the input frame (test frame 38-6) extracted by the VSP filter.

  Here, the VSP filter setting is set in the NIF 800 of the relay apparatus 31-1, which is the test start point. For example, in the NIF 800 of the relay apparatus 31-1, which is the test start point, when the test frame 38 is sent to the access apparatus 30-1 in the Egress direction, the test frame 38 returned from the access apparatus 30-1 is converted to the Ingress. The VSP filter setting of the input header processing unit 802 received from the direction is invalid. The input header processing unit 802 transmits the received test frame 38 (input frame) based on the VSP filter setting, and stores it in the input frame buffer 803.

  On the other hand, the VSP filter setting of the output header processing unit 806 that receives the test frame 38 returned from the access device 30-2 from the Egress direction via the switch unit 810 is valid. The output header processing unit 806 transfers the received test frame 38 (output frame) to the test control unit 812 based on the VSP filter setting. The test control unit 812 terminates the received test frame 38 (output frame). As a result, the NIF 800 that is the test start point can terminate the circulated test frame at the NIF 800 that is the test start point based on the VSP filter setting.

  If it is determined in step S1209 that the VSP filter setting is valid, the input header processing unit 802 next determines whether or not the format of the input frame matches the format set in the VSP filter 809-1. Determination is made (S1210).

  If it is determined in S1210 that the input frame matches the format set in the VSP filter 809-1, that is, if the input frame is the test frame 38-6 to be terminated at this node, the input header processing unit In step 802, the input frame is transferred to the test control unit 812 (S1211), and the process ends (S1213).

  Note that after S1211, the test control unit 812 terminates or loops back the received input frame. The test frame reception process (S1300) of the test control unit 812 will be described later with reference to FIG.

  On the other hand, if it is determined in S1210 that the input frame does not match the format set in the VSP filter 809-1, that is, if the input frame is an Ether OAM frame to be transmitted, the input header processing unit 802 The input frame is stored in the input frame buffer 803 (S1212), and the process ends (S1213).

  If it is determined in S1209 that the VSP filter setting is invalid, the input header processing unit 802 stores the input frame in the input frame buffer 803 (S1212), and ends the process (S1213).

  If it is determined in S1202 that the MEP operation setting is invalid, the input header processing unit 802 stores the input frame in the input frame buffer 803 (S1212), and ends the process (S1213).

  Note that the input frame is read by the input scheduler 804 and transferred to the switch unit 810 via the SW interface 805 after S1212. The switch unit 810 transfers the received input frame to the SW interface 805 of the transfer destination NIF 800 as an output frame. Here, the output header processing unit 806 that has received the output frame may execute payload analysis processing (S1200) instead of the input header processing unit 802 when the MEP operation setting is valid. When the VSP filter setting is valid in S1209, that is, when the output frame is the test frame 38 to be terminated, the output header processing unit 806 transfers the output frame to the test control unit 812 ( S1211).

  The test frame reception process (S1300) of the test control unit 812 of the relay device 31 or the user access device 30 will be described below.

  FIG. 11 is a flowchart illustrating test frame reception processing executed by the test control unit according to the first embodiment of this invention.

  After receiving the test frame 38 (S1301), the test control unit 812 of the relay apparatus 31 determines whether or not the return setting is set by the setting register (S1302).

  If it is determined in S1302 that the loopback setting has been made, the test control unit 812 executes a test frame loopback process (S1400) and ends the process (S1305).

  On the other hand, if it is determined in S1302 that the loopback setting has not been made, the test control unit 812 executes a test frame termination process (S1500) and ends the process (S1305).

  In the first embodiment, since a continuity characteristic test in an end-end management section is performed with a certain relay device 31 as a test start point, the test control unit 812 of the relay device 31 performs a test frame loopback process ( S1400) is not executed. However, since the test control unit 812 of the relay device 31 can also wrap the test frame, the relay device 31 uses each relay device 31 as a transfer path according to an instruction from the carrier management network 32, or The continuity characteristic test may be executed using the transfer path between the relay apparatus 31 and one user access apparatus 30 as a transfer path.

  The user access device 30 may have the same configuration as that of the relay device 31. However, in the first embodiment, the user access device 30 does not serve as a test start point. In 812, the received test frame 38 does not need to be terminated, and the received test frame 38 only needs to be folded. The test frame reception process (S2300) executed by the test control unit 812 of the user access device 30 will be described below.

  FIG. 21 is a flowchart illustrating test frame reception processing executed by the test control unit of the user access apparatus according to the first embodiment of the present invention.

  After receiving the test frame 38 (S2301), the test control unit 812 of the user access device 30 executes a test frame return process (S1400), and ends the process (S2302). The details of the test frame loopback process (S1400) executed by the test control unit 812 of the user access device 30 are the same as the test frame loopback process shown in FIG.

  The test frame loopback process (S1400) executed by the test control unit 812 of the user access device 30 (or relay device 31) shown in FIG. 21 (or FIG. 11) will be described below.

  FIG. 12 is a flowchart illustrating test frame folding processing executed by the test control unit according to the first embodiment of this invention.

  The test control unit 812 of the user access device 30 (or the relay device 31) starts a loopback process for the received test frame 38 (S1401).

  First, the test control unit 812 matches the reception direction (Ingress direction or Egress direction) of the test frame 38 with the acquisition setting direction (Ingress direction or Egress direction) set by the register value, and receives the in-device header 5. It is determined whether or not the port ID 52 matches the fetch port identifier (ID) set by the register value (S1402).

  If it is determined in S1402 that the reception direction of the test frame 38 matches the acquisition setting direction and the reception port ID 52 of the in-device header 5 matches the identifier (ID) of the acquisition port, Next, the control unit 812 determines whether or not the destination MAC address 61 is a multicast address (S1403).

  If it is determined in S1403 that the destination MAC address 61 is not a multicast address, the test control unit 812 acquires the source MAC address 62 from the test frame 38 (S1404), and uses the acquired source MAC address as the destination MAC address. The address 61 is overwritten (S1405), and the source MAC address 62 is overwritten with the MAC address set in the register value (S1406).

  On the other hand, if it is determined in S1403 that the destination MAC address 61 is a multicast address, the test control unit 812 does not overwrite the destination MAC address 61, and uses the source MAC address according to the MAC address set in the register value. Only the address 62 is overwritten (S1406).

  After S1406, the test control unit 812 determines whether the insertion direction of the test frame 38 into the scheduler is the Egress direction or the Ingress direction based on the set register value (S1407).

  If it is determined in S1407 that the insertion direction is the Egress direction, the test control unit 812 sets the reception port ID 52 and the reception NIF ID 53 of the in-device header 5 based on the register value set in the setting register 814. The value is described (S1408-1). Next, the test control unit 812 inserts the test frame 38 into the output scheduler 808 (S1409-1), and ends the process (S1411).

  On the other hand, if it is determined in S1407 that the insertion direction is the Ingress direction, the test control unit 812, based on the register value set in the setting register 814, receives the reception port ID 52 and the reception NIF ID 53 of the in-device header 5. The set value is described in (S1408-2). Next, the test control unit 812 inserts the test frame 38 into the input scheduler 804 (S1409-2), and ends the process (S1411).

  If it is determined in S1402 that the reception direction of the test frame 38 does not match the acquisition setting direction, or the reception port ID 52 of the in-device header 5 does not match the identifier (ID) of the acquisition port, the test control unit In step 812, the received frame is discarded (S1410), and the test frame return processing is terminated (S1411).

  The test frame termination process (S1500) executed by the test control unit 812 of the relay apparatus 31 shown in FIG. 11 will be described below.

  FIG. 13 is a flowchart illustrating a test frame termination process executed by the test control unit according to the first embodiment of this invention.

  The test control unit 812 of the relay device 31 starts termination processing of the received test frame 38 (S1501).

  First, the test control unit 812 matches the reception direction (Ingress direction or Egress direction) of the test frame 38 with the acquisition setting direction (Ingress direction or Egress direction) set by the register value, and receives the in-device header 5. It is determined whether or not the port ID 52 matches the fetch port identifier (ID) set by the register value (S1502).

  If it is determined in S1502 that the reception direction of the test frame 38 matches the acquisition setting direction and the reception port ID 52 of the in-device header 5 matches the identifier (ID) of the acquisition port, The control unit 812 acquires the sequence number 708 and the time stamp 709 from the payload of the test frame 38 (S1503).

  Next, the test control unit 812 measures the number of frame losses by comparing the acquired sequence number 708 with the sequence number expected by the test control unit 812 (S1504). After S1504, the test control unit 812 updates the expected sequence number (S1505).

  Next, the test control unit 812 measures the delay time by comparing the acquired time stamp 709 with the current time of the test control unit 812 (S1506).

  The test control unit 812 ends the process after measuring the number of frame losses and the delay time, which are information of the continuity characteristic test (S1508).

  If it is determined in S1502 that the reception direction of the test frame 38 does not match the acquisition setting direction, or the reception port ID 52 of the in-device header 5 does not match the identifier (ID) of the acquisition port, the test control unit In step 812, the received test frame 38 is discarded (S1507), and the termination process of the test frame is ended (S1508).

  As described above, according to the first embodiment, the relay device can execute the continuity characteristic test between the opposing user access devices without the user access device having an advanced test function. Further, since the throughput and the delay time can be measured simultaneously using the test frame of Ether OAM, the test can be simplified. As a result, the human and time costs required for the measurement and the cost required for the apparatus of the entire system can be suppressed, and an inexpensive and highly reliable dedicated line service can be provided.

<Embodiment 2>
Hereinafter, a second embodiment of the present invention will be described with reference to FIGS.

  In the first embodiment, the relay device 31 gives the test frame 38 a MEG level that is higher than the MEG level set for the own device. In the second embodiment, the relay device 31 gives the test frame 38 the same MEG level as the MEG level set for the own device. In this case, the relay device 31 transmits the transferred test frame 38 based on the transmission flag setting.

  FIG. 14 is an explanatory diagram illustrating the format of the payload of the test frame according to the second embodiment of this invention.

  The payload of the second embodiment is different from the payload of the first embodiment shown in FIG. As a result, even if the MEG level 701 of the received test frame 38 indicates a value to be terminated by the own apparatus, the relay apparatus 31 transmits the test frame 38 according to the transmission flag setting and the transmission flag 1601 value. Let The configuration of the relay device 31 is the same as the configuration of the relay device 31 in the first embodiment shown in FIG.

  Hereinafter, the test frame creation processing (S1700) and the payload analysis processing (S1800) in the second embodiment will be described with reference to FIGS. 15 and 16, respectively.

  FIG. 15 is a flowchart illustrating a test frame creation process executed by the test control unit according to the second embodiment of this invention.

  After detecting the insertion test start flag, the test control unit 812 starts test frame creation processing (S1701). The test control unit 812 describes the set value in the frame length 54 of the in-device header 5 based on the register value set in the setting register 814. In addition, set values are described in the destination MAC address 61, the source MAC address 62, the VLAN ID 63, and the ether type value 64 of the test frame 38. Further, the test control unit 812 describes the set value in the MEG level 701 of the payload 65 based on the set register value, and “51” indicating that the test frame 38 includes VSM (VSP Message) in the OpCode 703. Describe. Furthermore, the test control unit 812 writes the set value in the transparency flag 1601 based on the register value. In addition, the test control unit 812 writes the value created by the hard counter value in the sequence number 708 and the time stamp 709 (S1702), and ends the process (S1703). In this case, the register value for creating the destination MAC address 61 is set with a multicast address, the register value for creating the MEG level 701 is set with “section MEG level 36-2”, and the register for creating a transparency flag The value is set to “1”. In other areas, values created from register values or hard fixed values are described.

  FIG. 16 is a flowchart illustrating payload analysis processing executed by the input header processing unit according to the second embodiment of this invention.

  If the input header processing unit 802 determines that the input frame is an Ether OAM frame based on the value of the ether type value 64 of the input frame, the input header processing unit 802 starts payload analysis processing of the input frame (S1801). Next, the input header processing unit 802 determines whether the MEP operation setting is valid or invalid based on the register value set by the setting register 814 (S1802).

  If it is determined in S1802 that the MEP operation setting is valid, the input header processing unit 802 acquires the MEG level 701 and OpCode 703 from the payload 65 of the input frame (S1803).

  Next, the input header processing unit 802 compares the obtained MEG level 701 of the input frame with the MEG level set in the own device, and determines whether the MEG level 701 of the input frame is equal to or lower than the MEG level of the own device. Determination is made (S1804).

  Each node terminates or wraps the input frame at its own device when the MEG level of the input frame is the same as the MEG level set for the own device. Further, when the MEG level of the input frame is higher than the MEG level set in the own apparatus, the input frame is transmitted. When the MEG level of the input frame is lower than the MEG level set in the own apparatus, the input frame is an abnormal OAM frame, and thus the input frame is discarded.

  If it is determined in S1804 that the MEG level 701 is equal to or lower than the MEG level set in the own device, the input header processing unit 802 then selects the MEG level in which the MEG level 701 is set in the own device. It is determined whether it is lower than (S1805).

  If it is determined in S1805 that the MEG level 701 is lower than the MEG level of the own apparatus, the input header processing unit 802 discards the input frame (S1806) and ends the payload analysis process (S1813).

  On the other hand, if it is determined in S1805 that the MEG level 701 is not lower than the MEG level of the own device, that is, if the MEG level 701 is the same as the MEG level of the own device, the input header processing unit 802 is input. The value of OpCode 703 acquired from the Ether OAM frame is referenced to determine whether the value of OpCode 703 is “51” (S1807).

  If it is determined in S1807 that the OpCode 703 is not “51”, that is, if the input frame is another Ether OAM frame that is not the test frame 38, the input header processing unit 802 converts the input frame into the OAM control unit 811. (S1808), and the process ends (S1813).

  On the other hand, when it is determined in S1207 that the OpCode 703 is “51”, that is, when the input frame is the test frame 38, the input header processing unit 802 next determines the transparency flag based on the register value. It is determined whether the setting is valid or invalid (S1809).

  In the Ether OAM, when the MEG level 701 of the Ether OAM frame is the same as the MEG level set in the own apparatus, the relay apparatus 31 terminates or returns the received Ether OAM frame. There is a need. Therefore, in the second embodiment, the relay device 31 transmits the test frame 38 by setting the transmission flag.

  Here, the transparent flag setting is set in the NIF 800 of the relay apparatus 31 that is a node of the transfer path 39. For example, in the NIF 800 of the relay apparatus 31-1, which is the test start point, when the test frame 38 is sent to the access apparatus 30-1 in the Egress direction, the test frame 38 returned from the access apparatus 30-1 is converted to the Ingress. The transparency flag setting of the input header processing unit 802 that receives from the direction is valid. The input header processing unit 802 transmits the received test frame 38 (input frame) based on the transmission flag setting and stores it in the input frame buffer 803.

  On the other hand, the transparent flag setting of the output header processing unit 806 that receives the test frame 38 returned from the access device 30-2 from the Egress direction via the switch unit 810 is invalid. The output header processing unit 806 transfers the received test frame 38 (output frame) to the test control unit 812 based on the transmission flag setting. The test control unit 812 terminates the received test frame 38 (output frame). As a result, the NIF 800 that is the test start point can terminate the circulated test frame at the NIF 800 that is the test start point based on the transmission flag setting.

  If it is determined in S1809 that the transparency flag setting is invalid, the input header processing unit 802 transfers the test frame 38 to the test control unit 812 (S1810), and ends the process (S1813). Note that the test control unit 812 executes a loopback process (S1400) or a termination process (S1500) for the received test frame 38.

  On the other hand, if it is determined in S1809 that the transparency flag setting is valid, the input header processing unit 802 next determines whether or not the transparency flag 1601 is “1” (S1811).

  If it is determined in S1811 that the transparency flag 1601 is “0”, the input header processing unit 802 transfers the test frame 38 to the test control unit 812 (S1810), and ends the process (S1813).

  On the other hand, if it is determined in S1811 that the transmission flag 1601 is “1”, that is, if the test frame 38 is a test frame (38-2, 38-3, 38-5) to be transmitted, The input header processing unit 802 stores the test frame 38 as it is in the input frame buffer 803 (S1812), and ends the processing (S1813).

  If it is determined in S1802 that the MEP operation setting is invalid, the input header processing unit 802 stores the test frame 38 as it is in the input frame buffer 803 without performing the subsequent payload analysis processing ( In step S1812, the process ends (S1813). In this case, for example, instead of the input header processing unit 802 that receives the test frame 38 (input frame) from the Ingress direction, the output header processing unit 806 that receives the test frame 38 (output frame) from the Egress direction performs payload analysis processing ( S1800) may be executed.

  Specifically, after S 1812, the input frame is read by the input scheduler 804 and transferred to the switch unit 810 via the SW interface 805. The switch unit 810 transfers the received input frame to the SW interface 805 of the transfer destination NIF 800 as an output frame. Here, the output header processing unit 806 that has received the output frame from the Egress direction executes payload analysis processing (S1800) instead of the input header processing unit 802 when the MEP operation setting is valid. Also good. If the transparency flag setting is invalid in S1809, that is, if the output frame is the test frame 38 to be terminated, the output header processing unit 806 transfers the output frame to the test control unit 812 ( S1810).

  Note that the process of terminating or turning back the test frame 38 by the test control unit 812 is the same as the process shown in FIGS. 11 to 13 of the first embodiment.

  As described above, according to the second embodiment, the relay device 31 uses the transmission flag setting even when the MEG level given to the test frame 38 is the same as the MEG level set to the own device. The test frame 38 can be terminated. As a result, similarly to the effect of the first embodiment, the relay device can execute the continuity characteristic test between the opposing user access devices without the user access device having an advanced test function. Further, since the throughput and the delay time can be measured simultaneously using the test frame of Ether OAM, the test can be simplified. As a result, the human and time costs required for the measurement and the cost required for the apparatus of the entire system can be suppressed, and an inexpensive and highly reliable dedicated line service can be provided.

<Embodiment 3>
Hereinafter, a third embodiment of the present invention will be described with reference to FIGS.

  In the first embodiment, the relay device 31 includes the VSP filter 809, thereby terminating the test frame 38 to which the MEG level higher than the MEG level set in the own device is given. In the third embodiment, the relay device 31 terminates the test frame 38 based on TTL (Time To Live) included in the test frame 38.

  FIG. 17 is an explanatory diagram illustrating a payload format of a test frame according to the third embodiment of this invention.

  The payload of the test frame 38 of the third embodiment is different from the payload format of the test frame 38 of the first embodiment shown in FIG. 5 in that it includes a TTL 1901. Even if the MEG level 701 of the received test frame 38 is higher than the MEG level set in the own apparatus, the relay apparatus 31 uses the TTL (Time To Live) without using the VSP filter. 38 can be terminated. The test frame creation process (S2000), payload analysis process (S2100), and test frame return process (S2200) in the third embodiment will be described below.

  FIG. 18 is a flowchart illustrating test frame creation processing executed by the test control unit according to the third embodiment of this invention.

  After detecting the insertion test start flag, the test control unit 812 starts test frame creation processing (S2101). The test control unit 812 describes the set value in the frame length 54 of the in-device header 5 based on the register value set in the setting register 814. In addition, set values are described in the destination MAC address 61, the source MAC address 62, the VLAN ID 63, and the ether type value 64 of the test frame 38. Further, the test control unit 812 describes the set value in the MEG level 701 of the payload 65 based on the set register value, and “51” indicating that the test frame 38 includes VSM (VSP Message) in the OpCode 703. And set values are described in TTL 1901. In addition, the test control unit 812 describes the value created by the hard counter value in the sequence number 708 and the time stamp 709, and describes the value created from the register value and the hard fixed value in the other payload (S2002), The process ends (S2003).

  Note that the test control unit 812 may set a multicast address as a register value for creating the destination MAC address 61. Further, the test control unit 812 sets “EtE MEG level 36-1” as a register value for creating the MEG level 701. In addition, when the test frame 38 is transferred to the relay apparatus 31 that is the test end point, the test control unit 812 calculates a value so that the TTL value becomes “0”, and creates the TTL using the calculated value. Set to register value.

  For example, in the case of the transfer path 39 shown in FIG. 1, the test frame 38 sent from the node (relay apparatus 31-1) that is the test start point moves the node “5 times before returning to the test start point. Via. Therefore, the value of TTL 1901 is set to “5” in the process for creating the test frame 38. Accordingly, the relay apparatus 31 that is the test end point (test start point) receives the test frame 38 in which the value of TTL 1901 is “0”, and determines that the test frame 38 is a frame to be terminated. Can do.

  FIG. 19 is a flowchart illustrating payload analysis processing executed by the input header processing unit according to the third embodiment of this invention.

  Note that instead of the input header processing unit 802, the output header processing unit 806 may execute the payload analysis processing (S2100).

  When the input header processing unit 802 confirms that the input frame is an Ether OAM frame based on the value of the ether type value 64 of the input frame, the input header processing unit 802 starts payload analysis processing of the input frame (S2101). Next, the input header processing unit 802 determines whether the MEP operation setting is valid or invalid based on the register value set by the setting register 814 (S2102). If it is determined in S2102 that the MEP operation setting is valid, the input header processing unit 802 acquires the MEG level 701 and the OpCode 703 from the payload 65 of the input frame (Ether OAM frame) (S2103).

  Next, the input header processing unit 802 compares the obtained MEG level 701 of the input frame with the MEG level set in the own device, and determines whether the MEG level 701 of the input frame is equal to or lower than the MEG level of the own device. Determination is made (S2104).

  Each relay device 31 terminates or wraps the input frame at its own device when the MEG level of the input frame is the same as the MEG level set in its own device. Further, when the MEG level of the input frame is higher than the MEG level set in the own apparatus, the input frame is transmitted. When the MEG level of the input frame is lower than the MEG level set in the own apparatus, the input frame is an abnormal OAM frame, and thus the input frame is discarded.

  If it is determined in S2104 that the MEG level 701 is equal to or lower than the MEG level set in the own apparatus, the input header processing unit 802 then selects the MEG level in which the MEG level 701 is set in the own apparatus. It is determined whether it is lower than (S2105).

  If it is determined in S2105 that the MEG level 701 is lower than the MEG level of the own apparatus, the input header processing unit 802 discards the input Ether OAM frame (S2106) and ends the process (S2115). .

  On the other hand, if it is determined in S2105 that the MEG level 701 is not lower than the MEG level of the own device, that is, if the MEG level 701 is the same as the MEG level of the own device, the input header processing unit 802 is input. The value of the OpCode 703 acquired from the Ether OAM frame is referred to, and it is determined whether or not the value of the OpCode 703 is “51” (S2107).

  If it is determined in S2107 that the OpCode 703 is not “51”, that is, if the input frame is another Ether OAM frame that is not the test frame 38, the input header processing unit 802 converts the input frame into the OAM control unit 811. (S2108), and the process ends (S2115).

  On the other hand, when it is determined in 2107 that the OpCode 703 is “51”, that is, when the input frame is the test frame 38, the input header processing unit 802 transfers the input frame to the test control unit 812 ( In step S2109, the process ends (S2115).

  If it is determined in S2104 that the MEG level 701 is higher than the MEG level set in the own apparatus, the input header processing unit 802 then sets the value of the OpCode 703 acquired from the input frame to “51”. It is determined whether or not there is (S2110).

  If it is determined in S2110 that the OpCode 703 is “51”, the input header processing unit 802 acquires the TTL value described in the TTL 1901 of the VSP payload (S2111), and the acquired TTL value is “ It is determined whether it is “0” (S2112).

  If it is determined in S2112 that the TTL value is “0”, that is, if the test frame 38 is the test frame 38-6 to be terminated, the input header processing unit 802 tests the test frame 38. The data is transferred to the control unit 812 (S2109), and the process ends (S2115).

  On the other hand, if it is determined in S2112 that the TTL is not “0”, the input header processing unit 802 subtracts 1 from the TTL value described in the TTL 1901 and overwrites the TTL 1901 (S2113). The frame is stored in the input frame buffer 803 (S2114), and the process ends (S2115).

  If it is determined in S2110 that the OpCode 703 is not “51”, that is, if the input frame is another Ether OAM frame that is not the test frame 38, the input header processing unit 802 uses the input frame as it is. The data is stored in the buffer 803 (S2114), and the process ends (S2115).

  If it is determined in S2102 that the MEP operation setting is invalid, the input header processing unit 802 stores the input frame as it is in the input frame buffer 803 (S2114), and ends the process (S2115).

  Hereinafter, a process (S2200) in which the test control unit 812 returns the test frame 38 will be described.

  FIG. 20 is a flowchart illustrating test frame folding processing executed by the test control unit according to the third embodiment of this invention.

  The test frame folding process (S2200) in the third embodiment is different from the test frame folding process (S1400) of the first embodiment shown in FIG. 12 in that it includes a TTL process.

  The test control unit 812 matches the receiving direction (Ingress direction or Egress direction) of the test frame 38 with the acquisition setting direction (Ingress direction or Egress direction) set by the register value, and receives the port ID 52 of the in-device header 5. It is determined whether or not is coincident with the identifier (ID) of the take-in port set by the register value (S2202).

  If it is determined in S2202 that the reception direction of the test frame 38 matches the acquisition setting direction and the reception port ID 52 of the in-device header 5 matches the identifier (ID) of the acquisition port, Next, the control unit 812 determines whether or not the destination MAC address 61 is a multicast address (S2203).

  If it is determined in S2203 that the destination MAC address 61 is not a multicast address, the test control unit 812 acquires the source MAC address 62 from the test frame 38 (S2204), and uses the acquired source MAC address as the destination MAC address. The address 61 is overwritten (S2205), and the source MAC address 62 is overwritten with the MAC address set in the register value (S2206).

  On the other hand, when it is determined in S2203 that the destination MAC address 61 is a multicast address, the test control unit 812 does not overwrite the destination MAC address 61, and uses the source MAC address according to the MAC address set in the register value. Only the address 62 is overwritten (S2206).

  After S2206, the test control unit 812 acquires the TTL value from the payload TTL 1901, subtracts 1 from the acquired TTL value, and overwrites the TTL 1901 (S2207).

  Next, the test control unit 812 determines whether the insertion direction of the test frame 38 into the scheduler is the Egress direction or the Ingress direction based on the set register value (S2208).

  If it is determined in S2208 that the insertion direction is the Egress direction, the test control unit 812 sets the reception port ID 52 and the reception NIF ID 53 of the in-device header 5 based on the register value set in the setting register 814. The value is described (S2209-1). Next, the test control unit 812 inserts the test frame 38 into the output scheduler 808 (S2210-1), and ends the process (S2212).

  On the other hand, when it is determined in S2208 that the insertion direction is the Ingress direction, the test control unit 812, based on the register value set in the setting register 814, receives the reception port ID 52 and the reception NIF ID 53 of the in-device header 5. The set value is described in (S2209-2). Next, the test control unit 812 inserts the test frame 38 into the input scheduler 804 (S2210-2), and ends the process (S2212).

  If it is determined in S2202 that the reception direction of the test frame 38 does not match the acquisition setting direction, or the reception port ID 52 of the in-device header 5 does not match the identifier (ID) of the acquisition port, the test control unit In step 812, the received frame is discarded (S2211), and the process ends (S2212).

  As described above, according to the third embodiment, the relay device 31 can terminate the test frame 38 without using a VSP filter. As a result, similarly to the effect of the first embodiment, the relay device can execute the continuity characteristic test between the opposing user access devices without the user access device having an advanced test function. Further, since the throughput and the delay time can be measured simultaneously using the test frame of Ether OAM, the test can be simplified. As a result, the human and time costs required for the measurement and the cost required for the apparatus of the entire system can be suppressed, and an inexpensive and highly reliable dedicated line service can be provided.

It is explanatory drawing which shows the example of the conduction | electrical_connection characteristic test of the 1st Embodiment of this invention. It is a sequence diagram which shows the process of the conduction | electrical_connection characteristic test of the 1st Embodiment of this invention. It is explanatory drawing which shows the format of the header in an apparatus added to the input / output frame of the relay apparatus of the 1st Embodiment of this invention. It is explanatory drawing which shows the format of the test frame of the 1st Embodiment of this invention. It is explanatory drawing which shows the format of the payload of the test frame of the 1st Embodiment of this invention. It is a block diagram which shows the structure of the relay apparatus of the 1st Embodiment of this invention. It is a flowchart which shows the insertion process of the test frame which the test control part of the 1st Embodiment of this invention performs. It is a flowchart which shows the preparation process of the test frame which the test control part of the 1st Embodiment of this invention performs. It is a flowchart which shows the band control process which the test control part of the 1st Embodiment of this invention performs. It is a flowchart which shows the payload analysis process which the input header process part of the 1st Embodiment of this invention performs. It is a flowchart which shows the reception process of the test frame which the test control part of the 1st Embodiment of this invention performs. It is a flowchart which shows the return process of the test frame which the test control part of the 1st Embodiment of this invention performs. It is a flowchart which shows the termination | terminus process of the test frame which the test control part of the 1st Embodiment of this invention performs. It is explanatory drawing which shows the format of the test frame of the 2nd Embodiment of this invention. It is a flowchart which shows the preparation process of the test frame which the test control part of the 2nd Embodiment of this invention performs. It is a flowchart which shows the payload analysis process which the input header process part of the 2nd Embodiment of this invention performs. It is explanatory drawing which shows the format of the payload of the test frame of the 3rd Embodiment of this invention. It is a flowchart which shows the preparation process of the test frame which the test control part of the 3rd Embodiment of this invention performs. It is a flowchart which shows the payload analysis process which the input header process part of the 3rd Embodiment of this invention performs. It is a flowchart which shows the return process of the test frame which the test control part of the 3rd Embodiment of this invention performs. It is a flowchart which shows the reception process of the test frame which the test control part of the user access apparatus of the 3rd Embodiment of this invention performs.

Explanation of symbols

30 user access device 31 relay device 32 carrier management network 33 relay network 34 access network 36-1 EtE MEG level 36-2 section MEG level 38 test frame 39 transfer path 800 network interface board 801 input / output line interface 802 input header processing unit 803 Input frame buffer 804 Input scheduler 805 SW interface 806 Output header processing unit 807 Output frame buffer 808 Output scheduler 809 VSP filter 810 Switch unit 811 OAM control unit 812 Test control unit 813 NIF management unit 814 Setting register 815 Node management unit

Claims (14)

In a network system comprising a relay device constituting a core network and at least two access devices for connecting user terminals to the core network, a connection test method for testing a connection between the two access devices Because
Each device provided in the network has a management level for managing a connection test section.
Wherein each access device, to wrap the first management level of the test frame, the first management level is set,
Wherein the relay device to transfer the first management level of the test frame are set different second management level from the first management level,
The method
The relay device transmits the test frame of the first management level;
The access device loops back the first management level test frame sent from the relay device;
The relay apparatus transfers the test frame of the first management level received from the direction in which the test frame was transmitted,
The relay device confirms the connection between the two access devices by terminating the test frame of the first management level received from the opposite direction of the direction in which the test frame was transmitted. Continuity test method. The relay device includes a filter that extracts a frame that matches a pattern of the transmitted test frame,
The continuity test method according to claim 1, wherein the method terminates the test frame by extracting a test frame received from a direction opposite to a direction in which the test frame is transmitted by the filter. The method
The relay device sends the test frame in which the number of hops in the test section is set to the lifetime,
Each time the relay device and the access device transfer the test frame, the lifetime is reduced by one,
The continuity test method according to claim 1, wherein when the lifetime of the test frame is 0, the relay device terminates the test frame. A frame transfer path is set between the two access devices,
2. The continuity test method according to claim 1, wherein the relay apparatus transmits the test frame in which a multicast address is set as a destination.   The first management level is a higher management level than the second management level;
  2. The continuity test according to claim 1, wherein, when the relay apparatus receives the second management level test frame, the relay apparatus terminates the received second management level test frame. Method.   In a network system comprising a relay device constituting a core network and at least two access devices for connecting user terminals to the core network, a connection test method for testing a connection between the two access devices Because
  Each device provided in the network has a management level for managing a connection test section.
  The first management level is set so that the test frame of the first management level is turned back to each device through which the test frame to be subjected to the continuity test passes,
  The method
  The relay device sends a test frame in which a transparency flag is set to the first access device at the first management level;
  The first access device loops back the first management level test frame sent from the relay device;
  The relay device forwards the test frame received from the first access device according to the transparency flag of the test frame received from the first access device;
  A second access device facing the first access device loops back the first management level test frame sent from the relay device;
  When the relay device receives a test frame from the second access device, it invalidates the transparency flag to terminate the received test frame and confirm the connection between the two access devices. A continuity test method characterized by:   A frame transfer path is set between the two access devices,
  7. The continuity test method according to claim 6, wherein the relay device transmits the test frame in which a multicast address is set as a destination.   A network system comprising a relay device configuring a core network and at least two access devices for connecting a user terminal to the core network,
  Each device provided in the network has a management level for managing a connection test section.
  In each access device, the first management level is set so that the test frame of the first management level is folded.
  In the relay device, a second management level different from the first management level is set so as to transfer the test frame of the first management level,
  The relay device transmits the test frame of the first management level;
  The access device loops back the first management level test frame sent from the relay device,
  The relay device is
  Transferring the first management level test frame received from the direction in which the test frame was sent,
  A network system characterized by terminating the first management level test frame received from a direction opposite to the direction in which the test frame was transmitted.   The relay device includes a filter that extracts a frame that matches a pattern of the transmitted test frame,
  9. The network system according to claim 8, wherein the filter terminates the test frame by extracting a test frame received from a direction opposite to a direction in which the test frame is transmitted.   The relay device sends the test frame in which the number of hops in the test section is set to the lifetime,
  Each time the relay device and the access device transfer the test frame, the lifetime is reduced by one,
  The network system according to claim 8, wherein the relay apparatus terminates the test frame when the lifetime of the test frame is zero.   A frame transfer path is set between the two access devices,
  The network system according to claim 8, wherein the relay apparatus transmits the test frame in which a multicast address is set as a destination.   The first management level is a higher management level than the second management level;
  9. The continuity test method according to claim 8, wherein when the relay device receives the second management level test frame, the relay device terminates the received second management level test frame.   A network system comprising a relay device configuring a core network and at least two access devices for connecting a user terminal to the core network,
  Each device provided in the network has a management level for managing a connection test section.
  The first management level is set so that the test frame of the first management level is turned back to each device through which the test frame to be subjected to the continuity test passes,
  The relay device transmits a test frame in which a transparency flag is set to the first access device at the first management level,
  The first access device loops back the first management level test frame sent from the relay device,
  The relay device transfers the test frame received from the first access device to the test frame received from the first access device according to the transparency flag;
  The second access device opposite to the first access device returns the test frame of the first management level sent from the relay device,
  When the relay device receives a test frame from the second access device, the relay device terminates the received test frame by invalidating the transparency flag.   A frame transfer path is set between the two access devices,
  The network system according to claim 13, wherein the relay apparatus transmits the test frame in which a multicast address is set as a destination.

Images