US8089876B2 - Packet transmission apparatus and packet transmission method - Google Patents
Packet transmission apparatus and packet transmission method Download PDFInfo
- Publication number
- US8089876B2 US8089876B2 US12/554,214 US55421409A US8089876B2 US 8089876 B2 US8089876 B2 US 8089876B2 US 55421409 A US55421409 A US 55421409A US 8089876 B2 US8089876 B2 US 8089876B2
- Authority
- US
- United States
- Prior art keywords
- user
- monitor rate
- maintenance
- monitor
- oam
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related, expires
Links
- 230000005540 biological transmission Effects 0.000 title claims abstract description 75
- 238000000034 method Methods 0.000 title claims description 36
- 238000012423 maintenance Methods 0.000 claims abstract description 160
- 238000004891 communication Methods 0.000 claims abstract description 86
- 238000000605 extraction Methods 0.000 claims abstract description 22
- 238000012544 monitoring process Methods 0.000 claims abstract description 3
- 239000000284 extract Substances 0.000 claims description 4
- NFBAXHOPROOJAW-UHFFFAOYSA-N phenindione Chemical compound O=C1C2=CC=CC=C2C(=O)C1C1=CC=CC=C1 NFBAXHOPROOJAW-UHFFFAOYSA-N 0.000 description 258
- 230000008569 process Effects 0.000 description 26
- 238000012545 processing Methods 0.000 description 20
- 238000010586 diagram Methods 0.000 description 18
- 230000000694 effects Effects 0.000 description 12
- 230000006870 function Effects 0.000 description 8
- 238000000926 separation method Methods 0.000 description 8
- 230000008859 change Effects 0.000 description 5
- 230000009977 dual effect Effects 0.000 description 5
- 230000002159 abnormal effect Effects 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 230000002411 adverse Effects 0.000 description 2
- 230000009467 reduction Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 244000287680 Garcinia dulcis Species 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/25—Flow control; Congestion control with rate being modified by the source upon detecting a change of network conditions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/2483—Traffic characterised by specific attributes, e.g. priority or QoS involving identification of individual flows
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/33—Flow control; Congestion control using forward notification
Definitions
- the embodiments relate to a packet transmission apparatus and a packet transmission method.
- WAN Wide Area Network
- LAN Local Area Network
- Ethernet registered trademark
- the telecommunication common carriers often carry out maintenance and operations using the TCP/IP management protocol SNMP (Simple Network Management Protocol).
- SNMP Simple Network Management Protocol
- the OAM is being standardized as Y.1731 of ITU (International Telecommunication Union)-T or IEEE802. lag of IEEE (Institute of Electrical and Electronic Engineers).
- the OAM is a protocol technique used for maintenance and operation of a network device, and by use of this protocol technique, a fault which may occur may be automatically detected and the place of the fault may be analyzed.
- policing is carried out, upon receipt of the user flow, based on the user flow monitor rate regardless of whether the packets are communication packets or OAM packets.
- Policing is equivalent to a rate limiting function which controls the transparent output of a user flow containing communication packets and OAM packets based on the monitor rate setting.
- the packet transmission apparatus assume that policing is carried out on the user flow.
- the packets in the particular user flow are discarded.
- the packets in the particular user flow are transparently output.
- the communication packets and the OAM packets are extracted from the user flow after policing, and the OAM packets are transmitted to a CPU through a buffer.
- a packet transmission apparatus includes a user identification unit for identifying the user of an input user flow upon input of the user flow containing communication packets and maintenance packets, a maintenance packet extraction unit for extracting the maintenance packets from the user flow of the user identified by the user identification unit, a maintenance packet output control unit for controlling the transparent output of the maintenance packets extracted by the maintenance packet extraction unit based on the monitor rate setting, and a control unit for monitoring and controlling the user flow of the particular user based on the maintenance packets of the user transparently output by the maintenance packet output control unit.
- FIG. 1 is a block diagram illustrating the configuration of a packet transmission system according to a first embodiment
- FIG. 2 is a block diagram illustrating the configuration of a first flow identification unit and a second flow identification unit in the input port unit;
- FIG. 3 is a diagram explaining the contents of an input-side user management table
- FIG. 4 is a diagram explaining the contents of an input-side OAM type management table
- FIG. 5 is a block diagram illustrating the configuration of a third flow identification unit in the output port unit
- FIG. 6 is a diagram explaining the contents of an output-side user management table
- FIG. 7 is a flowchart illustrating the processing operation on the input port unit side for the first policing setting process in the packet transmission apparatus according to the first embodiment
- FIG. 8 is a block diagram illustrating the configuration of the first flow identification unit and the second flow identification unit in the input port unit in the packet transmission apparatus according to a second embodiment
- FIG. 9 is a flowchart illustrating the processing operation of the input port unit for the second policing setting process according to the second embodiment
- FIG. 10 is a block diagram illustrating the configuration of the packet transmission system according to a third embodiment.
- FIG. 11 is a block diagram illustrating the configuration of a fourth flow identification unit.
- the extracted OAM packets are sequentially stored in a buffer, and the OAM packets thus stored in the buffer are sequentially output to a CPU at a transmission rate tolerable to the CPU.
- the CPU therefore, may monitor and control the maintenance and operation of the user flow communication based on the OAM packets acquired.
- the policing is carried out on the user flow containing the communication packets and the OAM packets, and the effect of the policing extends to the concerned communication packets. In the present situation, however, substantially no policing effect extends to the OAM packets which are smaller than the communication packets.
- the packet processing ability of the CPU is very low compared to the transmission rate of the packets provided as a relay function.
- the CPU On a line of 10 Gbps, for example, the CPU has a processing ability of only about several hundred Mbps. Thus, the burden on the CPU is large.
- the OAM packets which may be input at an abnormally high rate beyond estimation and may even be from a malicious user such as in a DoS attack, are similarly transmitted to the CPU sequentially through the buffer.
- the CPU having received a vast amount of OAM packets or at an abnormal high rate, however, is liable to hang up, or the CPU's processing ability may be remarkably reduced as a whole.
- the packet transmission apparatus disclosed above which sequentially transmits the OAM packets to the CPU in a vast amount or at an abnormally high rate through the buffer, may cause an overflow of the buffer, with the result that the OAM packets of other users stored in the buffer may also be discarded without permission, thereby adversely affecting the other users.
- the CPU can no longer acquire OAM packets. In spite of the fact that the current route of the user flow communication is not yet disconnected, the current OAM route of the user flow communication would be judged as disconnected, resulting in an unnecessary line switching operation.
- the packet transmission apparatus disclosed above may include a buffer for each user flow to remove the effect of the abnormal rate of the OAM packets between users.
- the provision of a buffer for each user flow may greatly increase the capacity of the memory making up the queue for accommodating a great number of users, resulting in a very bulky apparatus.
- a packet transmission apparatus including a user identification unit for identifying a user of an input user flow containing communication packets and OAM packets, and a CPU for maintaining and controlling the user flow of the user based on the OAM packets of the user identified by the user identification unit, wherein the transparent output of the OAM packets extracted from the user flow to the CPU is controlled based on the monitor rate setting. For example, the control of the transparent output is conducted by policing the OAM packets extracted.
- the adverse effect on other users which might be caused by the discard of the OAM packets, may be reduced if not prevented without imposing any burden on the buffer in the front stage of the CPU or on the CPU.
- FIG. 1 is a block diagram illustrating the configuration of the packet transmission system according to the first embodiment.
- the packet transmission system in FIG. 1 includes a plurality of packet transmission apparatuses 2 for transmitting and receiving a user flow containing communication packets and OAM packets, and a switching unit 3 for switching and connecting the plurality of the packet transmission apparatuses 2 .
- the packet transmission apparatus 2 includes an input port unit 11 and an output port unit 12 for transmitting and receiving the user flow, and a CPU 13 for controlling the input port unit 11 and the output port unit 12 .
- the input port unit 11 includes a first flow identification unit 21 for identifying a user of the received user flow, and a plurality of second flow identification units 22 for separating and extracting the communication packets and the OAM packets in the user flow for each user identified by the first flow identification unit 21 .
- the input port unit 11 includes an input-side communication policer unit 23 for controlling by policing the communication packets separated and extracted by the second flow identification unit 22 , and an input-side OAM policer unit 24 for controlling by policing only the OAM packets separated and extracted by the second flow identification unit 22 .
- the communication packets for each user which are separated and extracted by the second flow identification unit 22 , are controlled by policing according to the dual token bucket scheme.
- the OAM packets for each user which are separated and extracted by the second flow identification unit 22 , are controlled by policing according to the single token bucket scheme.
- the input port unit 11 includes an input-side buffer unit 25 for provisionally storing the OAM packets police-controlled by the input-side OAM policer unit 24 and output to the CPU 13 at the transmission rate on the CPU 13 side.
- the output port unit 12 includes a third flow identification unit 31 which, upon reception of the user flow from the switching unit 3 , identifies the user of the particular user flow while separating and extracting the communication packets and the OAM packets contained in the user flow.
- the output port unit 12 includes an output-side OAM policer unit 32 for controlling by policing only the OAM packets separated and extracted by the third flow identification unit 31 , and an output-side buffer unit 33 for provisionally storing the OAM packets police-controlled by the output-side OAM policer unit 32 and for outputting the OAM packets thus stored to the CPU 13 in accordance with the transmission rate on the CPU 13 side.
- an output-side OAM policer unit 32 for controlling by policing only the OAM packets separated and extracted by the third flow identification unit 31
- an output-side buffer unit 33 for provisionally storing the OAM packets police-controlled by the output-side OAM policer unit 32 and for outputting the OAM packets thus stored to the CPU 13 in accordance with the transmission rate on the CPU 13 side.
- the OAM packets for each user which are separated and extracted by the third flow identification unit 31 , are police-controlled according to the single token bucket scheme.
- the separated and extracted communication packets are transmitted to their specific addresses by the third flow identification unit 31 .
- FIG. 2 is a block diagram illustrating the configuration of the first flow identification unit 21 and the second flow identification unit 22 in the input port unit 11 .
- the first flow identification unit 21 includes an input-side user management table 41 for managing the user monitor rate identification information (hereinafter referred to simply as “user PID”) 41 B and an OAM type request flag 41 C for each user 41 A, and an input-side user identification unit 42 for identifying the user of the user flow which may be received.
- user PID user monitor rate identification information
- OAM type request flag 41 C OAM type request flag
- the input-side user identification unit 42 upon reception of the user flow, extracts the address information of the user flow, and, based on the address information thus extracted, identifies the user of the user flow.
- the first flow identification unit 21 includes an input-side user-by-user PID acquisition unit 43 (hereinafter referred to as “input-side user PID acquisition unit 43 ”) for acquiring, from the input-side user management table 41 , the user PID 41 B corresponding to the user 41 A identified by the input-side user identification unit 42 , and an input-side OAM type request flag acquisition unit 44 for acquiring, from the input-side user management table 41 , the OAM type request flag 41 C corresponding to the user 41 A identified by the input-side user identification unit 42 .
- input-side user PID acquisition unit 43 for acquiring, from the input-side user management table 41 , the user PID 41 B corresponding to the user 41 A identified by the input-side user identification unit 42
- input-side OAM type request flag acquisition unit 44 for acquiring, from the input-side user management table 41 , the OAM type request flag 41 C corresponding to the user 41 A identified by the input-side user identification unit 42 .
- FIG. 3 is a diagram for explaining the contents of the input-side user management table 41 .
- the input-side user management table 41 in FIG. 3 manages the user 41 A, the user PID 41 B, and the OAM type request flag 41 C in correspondence with each other.
- the user PID 41 B “1” and the OAM type request flag 41 C “OFF” are associated with the user #A
- the user PID 41 B “3” and the OAM type request flag 41 C “ON” are associated with the user #C.
- the maintenance operator may appropriately change the user 41 A, the user PID 41 B, and/or the OAM type request flag 41 C in the input-side user management table 41 with an input operation.
- the first flow identification unit 21 upon reception of the user flow, identifies the user of the user flow while at the same time acquiring the user PID 41 B and the OAM type request flag 41 C corresponding to the user 41 A from the input-side user management table 41 .
- the additionally acquired information including the user 41 A, the user PID 41 B, and the OAM type request flag 41 C are added to the header of the packet in the user flow, and the user flow carrying the additional information is transmitted to the second flow identification unit 22 .
- the second flow identification unit 22 in FIG. 2 includes an input-side OAM type management table 51 for managing an OAM type 51 B and an OAM type PID 51 C corresponding to each OAM type 51 B of each user 51 A, and an input-side packet separation/extraction unit 52 for separating and extracting the communication packets and the OAM packets upon reception of the user flow carrying the additional information from the first flow identification unit 21 .
- the second flow identification unit 22 also includes a monitor rate management table 53 for managing the monitor rate 53 B for each PID 53 A, and an input-side communication policing setting unit 54 for setting, based on the additional information of the user flow, the monitor rate on the input-side communication policer unit 23 side to police the communication packets of the user which are separated and extracted by the input-side packet separation/extraction unit 52 .
- the input-side communication policing setting unit 54 acquires, from the monitor rate management table 53 , the monitor rate 53 B for the communication packets corresponding to the user PID 41 B contained in the additional information of the user flow, e.g., the user PID 41 B acquired by the input-side user PID acquisition unit 43 , and sets the acquired monitor rate 53 B as the monitor rate of the input-side communication policer unit 23 of the communication packets.
- FIG. 4 is a diagram for explaining the contents of the input-side OAM type management table 51 .
- the input-side OAM type management table 51 in FIG. 4 manages the OAM type 51 B corresponding to the user 51 A, and the OAM type PID 51 C corresponding to each OAM type 51 B.
- the maintenance operator may appropriately change, by an input operation, the user 51 A, the OAM type 51 B, and/or the OAM type PID 51 C in the input-side OAM type management table 51 .
- Examples of the OAM type 51 B include CC (Continuity Check), indicating the function of periodically confirming the connection, LB (Loop Back), indicating the function of confirming the loop response, and LT (Link Trace), indicating the function of confirming the trace response.
- CC Continuousity Check
- LB Loop Back
- LT Link Trace
- the input-side OAM type management table 51 manages the OAM type PID 51 C corresponding to the OAM type “CC” as “10”, the OAM type PID 51 C corresponding to the OAM type “LB” as “11”, and the OAM type PID 51 C corresponding to the OAM type “LT” as “12”.
- a comparison between the monitor rate of the OAM type PID 51 C and that of the user PID 41 B indicates that the OAM type PID 51 C has a monitor rate corresponding to the OAM type of the OAM packet, whereas the user PID 41 B has a monitor rate corresponding to the communication packet.
- the monitor rate of the OAM type PID 51 C therefore, is lower than that of the user PID 41 B.
- the second flow identification unit 22 illustrated in FIG. 2 includes an input-side OAM type PID acquisition unit 55 for acquiring, from the input-side OAM type management table 51 , the OAM type PID 51 C corresponding to the OAM type of the user's OAM packet separated and extracted by the input-side packet separation/extraction unit 52 based on the additional information of the user flow.
- the input-side OAM type PID acquisition unit 55 based on the additional information of the user flow, acquires the OAM type PID 51 C corresponding to each OAM type 51 B of the user 51 A from the input-side OAM type management table 51 .
- the second flow identification unit 22 includes an input-side flag judgment unit 56 for judging the state of the OAM type request flag 41 C containing the additional information of the user flow, and an input-side OAM policing setting unit 57 for setting the monitor rate of the input-side OAM policer unit 24 at the time of policing the OAM packets of the user which are separated and extracted by the input-side packet separation/extraction unit 52 .
- the input-side flag judgment unit 56 judges whether the OAM type request flag 41 C contained in the additional information of the user flow is “on” or not.
- the input-side OAM policing setting unit 57 acquires, from the monitor rate management table 53 , the monitor rate 53 B corresponding to the OAM type PID 51 C for each OAM type of the user which has been acquired by the input-side OAM type PID acquisition unit 55 .
- the monitor rate thus acquired is set as that for the input-side OAM policer unit 24 for each OAM type of the particular user.
- the input-side OAM policer unit 24 based on the monitor rate 53 B for the OAM type corresponding to the OAM type PID 51 C for each OAM type (CC, LB, LT) of the user, carries out the process of controlling by policing the OAM packets of the particular user for each OAM type (CC, LB, LT) according to the single token bucket scheme.
- the input-side OAM policing setting unit 57 acquires, from the monitor rate management table 53 , the monitor rate 53 B for the communication packets corresponding to the user PID 41 B contained in the additional information, e.g., the user PID 41 B acquired by the input-side user PID acquisition unit 43 .
- the monitor rate thus acquired is set as the monitor rate of the input-side OAM policer unit 24 of the OAM packets of the particular user.
- the input-side OAM policer unit 24 based on the monitor rate 53 B for the communication packets corresponding to the user PID 41 B, executes the process of controlling by policing the OAM packets of the particular user according to the single token bucket scheme.
- FIG. 5 is a block diagram of the configuration of the third flow identification unit 31 in the output port unit 12 .
- the third flow identification unit 31 has an output-side user management table 61 to manage the OAM type 61 B, the user PID 61 C, the OAM type request flag 61 D, and the OAM type PID 61 E for each user 61 A.
- FIG. 6 is a diagram for explaining the contents of the output-side user management table 61 .
- the output-side user management table 61 illustrated in FIG. 6 manages the OAM type 61 B, the user PID 61 C, the OAM type request flag 61 D, and the OAM type PID 61 E in correspondence with each user 61 A.
- the user #H for example, the user PID 61 C “6”, the OAM type request flag 61 D “ON”, and CC “50”, LB “51”, and LT “52” of the OAM type PID 61 E are managed in correspondence with each other.
- the user PID 61 C “8”, the OAM type request flag 61 D “OFF”, and CC “60”, LB “61”, and LT “62” of the OAM type PID 61 E are managed in correspondence with each other.
- the maintenance operator may appropriately change the user 61 A, the OAM type 61 B, the user PID 61 C, the OAM type request flag 61 D, and the OAM type PID 61 E in the output-side user management table 61 with an input operation.
- the third flow identification unit 31 includes an output-side user identification unit 62 for identifying the user of the user flow upon reception of the user flow, and an output-side packet separation/extraction unit 63 for separating and extracting communication packets and OAM packets upon reception of the user flow.
- the output-side user identification unit 62 upon reception of the user flow, extracts the address information of the user flow and identifies the user of the user flow based on the address information thus extracted.
- the third flow identification unit 31 includes an output-side user PID acquisition unit 64 for acquiring, from the output-side user management table 61 , the user PID 61 C corresponding to the user 61 A identified by the output-side user identification unit 62 .
- the third flow identification unit 31 includes an output-side OAM type request flag acquisition unit 65 for acquiring the OAM type request flag 61 D corresponding to the user 61 A identified by the output-side user identification unit 62 , and an output-side OAM type PID acquisition unit 66 for acquiring, from the output-side user management table 61 , the OAM type PID 61 E corresponding to the user 61 A identified by the output-side user identification unit 62 .
- the third flow identification unit 31 includes an output-side flag judgment unit 67 for judging whether the OAM type request flag 61 D acquired by the output-side OAM type request flag acquisition unit 65 is “ON” or not, a monitor rate management table 68 for managing the monitor rate 68 B for each PID 68 A, and an output-side OAM policing setting unit 69 for setting the monitor rate of the output-side OAM policer unit 32 at the time of policing the OAM packets extracted by the output-side packet separation/extraction unit 63 .
- the output-side OAM policing setting unit 69 acquires, from the monitor rate management table 68 , the monitor rate 68 B for the OAM type corresponding to the OAM type PID 61 E for each OAM type of the user which is acquired by the output-side OAM type PID acquisition unit 66 .
- the monitor rate thus acquired is set as the monitor rate for the output-side OAM policer unit 32 of each OAM type of the particular user.
- the output-side OAM policer unit 32 based on the monitor rate 68 B for the OAM type corresponding to the OAM type PID 61 E for each OAM type (CC, LB, LT) of the user, executes the process of controlling by policing the OAM packets of the particular user for each OAM type (CC, LB, LT) according to the single token bucket scheme.
- the output-side OAM policing setting unit 69 acquires, from the monitor rate management table 68 , the OAM monitor rate 68 B for each user corresponding to the user PID 61 C acquired by the output-side user PID acquisition unit 64 .
- the monitor rate thus acquired is set as the monitor rate for the output-side OAM policer unit 32 of the OAM packets of the particular user.
- the output-side OAM policer unit 32 based on the OAM monitor rate 68 B for each user corresponding to the user PID 61 C, executes the process of controlling by policing the OAM packets of the particular user according to the single token bucket scheme.
- FIG. 7 is a flowchart of the processing operation on the input port unit 11 side for the first policing setting process in the packet transmission apparatus 1 according to the first embodiment.
- the first policing setting process in FIG. 7 is for controlling by policing the communication packets on the side of the input-side communication policer unit 23 while at the same time controlling by policing the OAM packets on the side of the input-side OAM policer unit 24 .
- the input-side user identification unit 42 illustrated in FIG. 2 upon reception of the user flow (YES in S 11 ), identifies the user of the user flow (step S 12 ).
- the input-side user PID acquisition unit 43 acquires, from the input-side user management table 41 , the user PID 41 B corresponding to the user 41 A identified by the input-side user identification unit 42 (step S 13 ).
- the input-side OAM type request flag acquisition unit 44 acquires, from the input-side user management table 41 , the OAM type request flag 41 C corresponding to the user 41 A identified by the input-side user identification unit 42 (step S 14 ).
- the user PID 41 B and the OAM type request flag 41 C are transmitted from the first flow identification unit 21 to the second flow identification unit 22 as the additional information added to the user flow for each user 41 A.
- the input-side packet separation/extraction unit 52 of the second flow identification unit 22 judges whether the user flow includes OAM packets or not (step S 15 ).
- the input-side OAM type PID acquisition unit 55 of the second flow identification unit 22 acquires, from the input-side OAM type management table 51 , the OAM type PID 51 C corresponding to each OAM type (CC, LB, LT) of the particular user which is contained in the additional information (step S 16 ).
- the input-side flag judgment unit 56 of the second flow identification unit 22 judges whether the OAM type request flag 41 C of the particular user contained in the additional information is “ON” or not (step S 17 ).
- the input-side OAM policing setting unit 57 of the second flow identification unit 22 acquires, from the monitor rate management table 53 , the monitor rate 53 B corresponding to the OAM type PID 51 C acquired in step S 16 .
- the monitor rate of each OAM type (CC, LB, LT) thus acquired is set in the input-side OAM policer unit 24 (step S 18 ).
- the input-side OAM policer unit 24 executes the process of controlling by policing the OAM packets of the particular user according to the single token bucket scheme based on the monitor rate set by the input-side OAM policing setting unit 57 , and judges whether or not the transmission rate of the OAM packets has exceeded the monitor rate setting (step S 19 ).
- the input-side OAM policer unit 24 discards the OAM packets (step S 20 ) and ends the processing operation illustrated in FIG. 7 .
- the input-side OAM policer unit 24 reduces the burden which otherwise might be imposed by the OAM packets on the input-side buffer 25 and the CPU 13 .
- the input-side OAM policer unit 24 transparently outputs the OAM packets destined to the CPU 13 and sequentially stores them in the input-side buffer 25 (step S 21 ), thereby finishing the processing operation illustrated in FIG. 7 .
- the input-side OAM policer unit 24 transmits the OAM packets sequentially at a rate tolerable for the CPU 13 and without imposing any burden on the CPU 13 or on the input-side buffer unit 25 .
- the input-side OAM policing setting unit 57 acquires, from the monitor rate management table 53 , the monitor rate 53 B for the communication packets corresponding to the user PID 41 B acquired in step S 13 .
- the monitor rate thus acquired for each user is set in the input-side OAM policer unit 24 (step S 22 ) and the process proceeds to step S 19 to judge whether the transmission rate of the particular OAM packets has exceeded the monitor rate setting or not.
- step S 15 judges that the user flow includes communication packets (NO in step S 15 )
- the input-side communication policing setting unit 54 acquires, from the monitor rate management table 53 , the monitor rate 53 B for the communication packets corresponding to the user PID 41 B acquired in step S 13 , and sets the acquired monitor rate for each user in the input-side communication policer unit 23 (step S 23 ).
- the input-side communication policer unit 23 executes the process of controlling by policing the communication packets of the user in accordance with the dual token bucket scheme based on the monitor rate set by the input-side communication policing setting unit 54 , and judges whether or not the transmission rate of the communication packet has exceeded the monitor rate setting (step S 24 ).
- the input-side communication policer unit 23 discards the communication packets (step S 25 ) and ends the processing operation illustrated in FIG. 7 . As a result, the input-side communication policer unit 23 may smoothly transmit the communication packets to another party.
- the input-side communication policer unit 23 transparently outputs the communication packets and outputs the communication packets of the other party through the output interface (step S 26 ), thereby ending the processing operation illustrated in FIG. 7 .
- the input-side communication policer unit 23 may smoothly transmit the communication packets to the other party.
- step S 11 judges that the user flow is not received (NO in step S 11 )
- the input-side user identification unit 42 ends the processing operation illustrated in FIG. 7 .
- the input-side user identification unit 42 upon identification of the user flow in step S 12 , executes the operation of acquiring the user PID 41 B and the OAM type request flag 41 C for each user through the process of steps S 13 and S 14 .
- the user PID 41 B, the OAM type request flag 41 C and the OAM PID 51 C corresponding to the identified user are acquired.
- the monitor rate for each OAM type (CC, LB, LT) corresponding to the OAM type PID 51 C is set as that for the input-side OAM policer unit 24 thereby to execute the police control process according to the single token bucket scheme for each OAM type of each user.
- the burden of the OAM packets on the CPU 13 and the input-side buffer unit 25 may be reduced.
- the monitor rate for the communication packets corresponding to the user PID 41 B is set as that for the input-side OAM policer unit 24 , and the process of controlling by policing the OAM packets is executed for each user according to the single token bucket scheme. As a result, the burden of the OAM packets on the CPU 13 and the input-side buffer unit 25 may be reduced.
- the monitor rate for the communication packets corresponding to the user PID 41 B is set as that for the input-side communication policer unit 23 , and the communication packets are police controlled for each user according to the dual token bucket scheme. Therefore, the communication packets may be transmitted smoothly to other parties.
- the output-side user identification unit 62 in the third flow identification unit 31 on the output port unit 12 side upon reception of the user flow, identifies the user of the user flow based on the address information of the user flow as illustrated in FIG. 5 .
- the output-side packet separation/extraction unit 63 in the third flow identification unit 31 separates and extracts the communication packets and the OAM packets.
- the output-side user PID acquisition unit 64 acquires, from the output-side user management table 61 , the user PID 61 C corresponding to the user identified by the output-side user identification unit 62 .
- the output-side OAM type request flag acquisition unit 65 acquires, from the output-side user management table 61 , the OAM type request flag 61 D corresponding to the user identified by the output-side user identification unit 62 .
- the output-side OAM type PID acquisition unit 66 acquires, from the output-side user management table 61 , the OAM type PID 61 E for each OAM type (CC, LB, LT) corresponding to the user identified by the output-side user identification unit 62 .
- the output-side flag judgment unit 67 judges whether the OAM type request flag 61 D of the user flow is “ON” or not.
- the output-side OAM policing setting unit 69 acquires, from the monitor rate management table 68 , the monitor rate for the OAM type corresponding to the OAM type PID 61 E for each OAM type (CC, LB, LT) of the user acquired by the output-side OAM type PID acquisition unit 66 .
- the monitor rate thus acquired is set as that for the output-side OAM policer unit 32 of each OAM type of the particular user.
- the output-side OAM policer unit 32 sets the monitor rate with the OAM type PID 61 E, and when the transmission rate of the OAM packet for each OAM type exceeds the monitor rate, discards the particular OAM packet. As a result, the output-side OAM policer unit 32 may reduce the burden of the OAM packets on the output-side buffer unit 33 and the CPU 13 .
- the output-side OAM policer unit 32 sequentially stores the OAM packets destined for the CPU 13 in the output-side buffer unit 33 .
- the output-side OAM policer unit 32 may transmit the OAM packets sequentially at the rate tolerable for the CPU 13 and without imposing any burden on the CPU 13 or on the output-side buffer unit 33 .
- the output-side OAM policing setting unit 69 acquires, from the monitor rate management table 68 , the OAM monitor rate 68 B for each user corresponding to the user PID 61 C acquired by the output-side user PID acquisition unit 64 .
- the monitor rate thus acquired is set as the monitor rate of the output-side OAM policer unit 32 of the OAM packets of the particular user.
- the output-side OAM policer unit 32 sets the monitor rate with the user PID 61 C, and when the transmission rate of the OAM packet for each user has exceeded the monitor rate, discards the particular OAM packet. As a result, the output-side OAM policer unit 32 may reduce the burden of the OAM packets on the output buffer unit 33 and the CPU 13 .
- the output-side OAM policer unit 32 sequentially stores the OAM packets destined for the CPU 13 in the output-side buffer unit 33 .
- the output-side OAM policer unit 32 may transmit the OAM packets sequentially at the rate tolerable for the CPU 13 without imposing any burden on both the CPU 13 and the output-side buffer unit 33 .
- the user PID 41 B, the OAM type request flag 41 C, and the OAM type PID 51 C corresponding to the identified user are acquired, and when the OAM type request flag 41 C is “ON”, the monitor rate for each OAM type (CC, LB, LT) corresponding to the OAM type PID 51 C is set as the monitor rate for the input-side OAM policer unit 24 . Then, the police control operation is carried out according to the single token bucket scheme for each OAM type of the OAM packets of each user. According to the first embodiment, therefore, the burden of the OAM packets on the CPU 13 and the input-side buffer unit 25 may be reduced.
- the reduction in the processing ability and the hang-up of the CPU 13 , the overflow of the buffer, and the line switching judgment error may be prevented, while at the same time making it possible to avoid the situation in which the abnormal rates of the OAM packets between users affect each other.
- the monitor rata corresponding to the user PID 41 B is set as that for the input-side OAM policer unit 24 , and the OAM packets for each user are controlled by policing according to the single token bucket scheme. As a result, the burden of the OAM packets on the CPU 13 and the input buffer unit 25 may be reduced.
- the monitor rate corresponding to the user PID 41 B is set as that for the input-side communication policer unit 23 , and the communication packets of each user are controlled by policing according to the dual token bucket scheme. Therefore, the communication packets may be transmitted smoothly to the other party.
- the single token bucket scheme is employed for controlling by policing the OAM packets. Therefore, as compared to the dual token bucket scheme used for controlling by policing the communication packets, the memory capacity may be reduced.
- the user PID 61 C, the OAM type request flag 61 D, and the OAM type PID 61 E corresponding to the user thus identified are acquired.
- the monitor rate for each OAM type (CC, LB, LT) corresponding to the OAM type PID 61 E is set as the monitor rate for the output-side OAM policer unit 32 , and the OAM packets of each user are controlled by policing operation for each OAM type (CC, LB, LT) according to the single token bucket scheme.
- the burden of the OAM packets on the CPU 13 and the output-side buffer unit 33 may be reduced.
- the reduction in the processing ability and the hang-up of the CPU 13 , the overflow of the buffer and the erroneous judgment of line switching may be reduced if not prevented while at the same time making it possible to avoid the situation in which abnormal rates of the OAM packets between the users affect each other.
- the OAM monitor rate for each user corresponding to the user PID 61 C is set as the monitor rate for the output-side OAM policer unit 32 , and the OAM packets are controlled by policing for each user according to the single token bucket scheme. As a result, the burden of the OAM packets on the CPU 13 and the output buffer unit 33 may be reduced.
- the monitor rate of the input-side OAM policer unit 24 and the monitor rate of the output-side OAM policer unit 32 are not set directly, but managed with PID for each user.
- the maintenance operator may change the PID setting for each user.
- an arbitrary group may be set, and the policing control operation may be carried out at the monitor rate for each group.
- the monitor rate is managed with the PID (OAM type PID 51 C) for each OAM type of the user, and the PID (OAM type PID 51 C) setting may be changed in accordance with the service contents for each OAM type.
- the policing control operation may be realized at the monitor rate corresponding to the service contents of the OAM type, while at the same time making it possible to make the most of the limited packet processing ability of the CPU 13 .
- the input-side user management table 41 , the input-side OAM type management table 51 , and the monitor rate management table 53 in the input port unit 11 are arranged separately from the output-side user management table 61 and the monitor rate management table 68 in the output port unit 12 . Nevertheless, the same items of these tables may be integrally managed as a single table. By doing so, the memory capacity of the apparatus as a whole may be further reduced.
- the monitor rate of the OAM packets for the input-side OAM policer unit 24 or the output-side OAM policer unit 32 is set as the monitor rate corresponding to the user PID 41 B or the OAM type PID 51 C based on the OAM type request flag 41 C.
- the provision of the policer unit for the OAM packets may reduce the burden on the CPU 13 and the buffer units (input-side buffer unit 25 and output-side buffer unit 33 ).
- the monitor rate for the communication packets corresponding to the user PID 41 B acquired by the input-side user PID acquisition unit 43 is set in the input-side OAM policer unit 24 .
- the user PID 41 B corresponds to the monitor rate of the communication packets for each user and is set high compared to the monitor rate of the OAM packets.
- the PID dedicated to the OAM hereinafter referred to as “the OAM-only PID” corresponding to the monitor rate of the OAM packet may be set.
- the OAM-only PID corresponding to the monitor rate of the OAM packet may be set.
- FIG. 8 is a block diagram of the configuration of the input port unit 11 of the packet transmission apparatus according to the second embodiment.
- the same component parts as those of the packet transmission apparatus 2 according to the first embodiment are designated by the same reference numerals, respectively, and not explained again.
- the difference between the packet transmission apparatus according to the first embodiment and the packet transmission apparatus according to the second embodiment resides in the internal configuration of the input-side OAM type management table 510 , the input-side OAM type PID acquisition unit 550 , and the input-side OAM policing setting unit 570 in the second flow identification unit 22 of the input port unit 11 .
- the input-side OAM type management table 510 in addition to the OAM type 51 B and the OAM type PID 51 C, manages a user OAM-only PID 51 D corresponding to the OAM-only monitor rate corresponding to the user 51 A.
- the maintenance operator may appropriately change, by an input operation, the user 51 A, the OAM type 51 B, the OAM type PID 51 C, and the user OAM-only PID 51 D in the input-side OAM type management table 510 .
- the OAM-only monitor rate corresponding to the user OAM-only PID 51 D is low compared to the monitor rate for the communication packets corresponding to the user PID 41 B, and is equivalent to the monitor rate corresponding to the OAM packets.
- the input-side OAM type PID acquisition unit 550 acquires, from the input-side OAM type management table 510 , the OAM type PID 51 C and the user OAM-only PID 51 D corresponding to the user 51 A contained in the additional information of the user flow.
- the input-side OAM policing setting unit 570 acquires the monitor rate 53 B for the OAM type corresponding to the OAM type PID 51 C from the monitor rate management table 53 .
- the monitor rate thus acquired is set as the monitor for the input-side OAM policer unit 24 of each OAM type of the particular user.
- the input-side OAM policing setting unit 570 acquires the OAM-only monitor rate 53 B corresponding to the user OAM-only PID 51 D from the monitor rate management table 53 , and sets the acquired monitor rate as the monitor rate for the input-side OAM policer unit 24 of the particular user.
- the input-side OAM policer unit 24 executes the process of controlling by policing the OAM packets of the particular user according to the single token bucket scheme based on the OAM-only monitor rate corresponding to the user OAM-only PID 51 D.
- FIG. 9 is a flowchart illustrating the processing operation of the input port unit 11 for the second policing setting process according to the second embodiment.
- step S 15 judges that the user includes OAM packets
- the input-side OAM type PID acquisition unit 550 illustrated in FIG. 8 acquires the OAM type PID 51 C and the user OAM-only PID 51 D corresponding to each OAM type of the particular user contained in the additional information (step S 31 ).
- the input-side flag judgment unit 56 judges whether the OAM type request flag 41 C of the particular user contained in the additional information is “ON” or not (step S 32 ).
- the input-side OAM policing setting unit 570 acquires, from the monitor rate management table 53 , the monitor rate 53 B for the OAM type corresponding to the OAM type PID 51 C acquired in step S 31 . Then, the process proceeds to step S 18 to set the acquired monitor rate of each OAM type in the input-side OAM policer unit 24 .
- the input-side OAM policing setting unit 570 acquires, from the monitor rate management table 53 , the OAM-only monitor rate 53 B corresponding to the user OAM-only PID 51 D acquired in step S 31 . Then, the input-side OAM policing setting unit 570 , after setting the acquired user OAM-only monitor rate in the input-side OAM policer unit 24 (step S 33 ), proceeds to step S 19 to execute policing control operation according to the single token bucket scheme based on the monitor rate thus set.
- the OAM-only monitor rate is set which corresponds not to the user PID 41 B of the communication packets but to the OAM-only user PID, i.e., the user OAM-only PID 51 D. Therefore, compared to the first policing setting process in FIG. 7 , the optimum policing control corresponding to the OAM-only monitor rate may be realized.
- the monitor rate of the OAM packets is set in the input-side OAM policer unit 24 or the output-side OAM policer unit 32 based on the OAM type request flag 41 C in such a manner that the monitor rate corresponds to the OAM type PID 51 C or the user OAM-only PID 51 D.
- the provision of the policer unit for the OAM packets may reduce the burden on the CPU 13 and the buffer unit (input-side buffer unit 25 and output-side buffer unit 33 ).
- a similar effect may be obtained, without the user OAM-only PID 51 D, also in such a manner that when the OAM type request flag 41 C is “ON”, the monitor rate corresponding to the OAM type PID 51 C of the same monitor rate as the user OAM-only PID 51 D is set in the input-side OAM policer unit 24 or the output-side OAM policer unit 32 .
- the output-side OAM policer unit 32 and the output-side buffer unit 33 are arranged inside the output port unit 12 .
- the output-side OAM policer unit 32 and the output-side buffer unit 33 inside the output port unit 12 may double as the input-side OAM policer unit 24 and the input-side buffer unit 25 , respectively, in the input port unit 11 .
- This configuration is explained as a third embodiment below.
- FIG. 10 is a block diagram of the configuration of the packet transmission system according to the third embodiment
- FIG. 11 is a block diagram of the configuration of the fourth flow identification unit inside the output port unit 12 .
- the same component parts as those of the packet transmission system 1 according to the first embodiment are designated by the same reference numerals, respectively, and the same configuration and operation thereof are not explained again.
- the output-side OAM policer unit 32 and the output-side buffer unit 33 are not included in the output port unit 12 , but the output-side OAM policer unit 32 and the output-side buffer unit 33 double as the input-side OAM policer unit 24 and the input-side buffer unit 25 , respectively.
- the monitor rate corresponding to the OAM packets received by a fourth flow identification unit 71 of the output port unit 12 is set in the input-side OAM policer unit 24 .
- the fourth flow identification unit 71 in FIG. 11 has substantially the same configuration as the third flow identification unit 31 in FIG. 5 .
- the fourth flow identification unit 71 illustrated in FIG. 11 receives the user flow, and acquires the user PID 61 C, the OAM type request flag 61 D, and the OAM type PID 61 E corresponding to the user from the output-side user management table 61 .
- the OAM type request flag 61 D is “ON”
- the monitor rate for the OAM type corresponding to each OAM type PID 61 E is set in the input-side OAM policer unit 24 .
- the input-side OAM policer unit 24 based on each monitor rate for the OAM type corresponding to each OAM type PID 61 E, executes the process of controlling by policing the OAM packets of the particular user for each OAM type according to the single token bucket scheme.
- the fourth flow identification unit 71 sets the user OAM monitor rate corresponding to the user PID 61 C in the input-side OAM policer unit 24 .
- the input-side OAM policer unit 24 based on the monitor rate corresponding to the user PID 61 C, executes the process of controlling by policing the OAM packets of the particular user according to the single token bucket scheme.
- the user flow of a user #F is received on the input port unit 11 side and the user flow of a user #H on the output port unit 12 side.
- the user PID of the user #F is set to “6”
- the OAM type request flag is turned “ON”
- the CC of the OAM type PID is set to “50”, LB to “51”, and LT to “52”.
- the user PID of the user #H is set to “6”
- the OAM type request flag is turned “ON”
- the CC of the OAM type PID is set to “50”, LB to “51”, and LT to “52”.
- the PID is shared by the users #F and #H.
- the first flow identification unit 21 and the second flow identification unit 22 of the input port unit 11 receive the user flow, and acquire the user PID 41 B corresponding to the user #F as “6”, the OAM type request flag 41 C as “ON”, the CC of the user OAM type PID 51 C as “50”, LB as “51”, and LT as “52”. Then, the monitor rate for the OAM type corresponding to each user OAM type PID 51 C for the OAM packets of the user #F is set in the input-side OAM policer unit 24 .
- the fourth flow identification unit 71 of the output port unit 12 receives the user flow, and acquires the user PID 61 C corresponding to the user #H as “6”, the OAM type request flag 61 D as “ON”, the CC of the OAM type PID 61 E as “50”, LB as “51”, and LT as “52”. Then, the monitor rate for the OAM type corresponding to each OAM type PID 61 E of the OAM packets of the user #H is set in the input-side OAM policer unit 24 .
- the input-side OAM policer unit 24 sets the monitor rate for the OAM type corresponding to the same OAM type PID 61 E for the OAM packets of the users #F and #H.
- the OAM packets of the users #F and #H may be controlled by policing according to the single token bucket scheme at the same monitor rate.
- the user PID 41 B of the user #G is set to “8”
- the OAM type request flag 41 C is turned “OFF”
- the CC of the user OAM type PID 51 C is set to “60”, LB to “61”, and LT to “62”.
- the user PID 61 C of the user #I is set to “8”
- the OAM type request flag 61 D is turned “OFF”
- the CC of the user OAM type PID 61 E is set to “60”, LB to “61”, and LT to “62”.
- the PID is shared by the users #G and #I.
- the first flow identification unit 21 and the second flow identification unit 22 of the input port unit 11 receive the user flow, and acquire the user PID 41 B corresponding to the user #G as “8”, the OAM type request flag 41 C as “OFF”, the CC of the user OAM type PID 51 C as “60”, LB as “61”, and LT as “62”. Then, the monitor rate for the communication packets corresponding to the user PID “8” for the OAM packets of the user #G is set in the input-side OAM policer unit 24 .
- the fourth flow identification unit 71 of the output port unit 12 receives the user flow, and acquires the user PID 61 C corresponding to the user #I as “8”, the OAM type request flag 61 D as “OFF”, the CC of the user OAM type PID 61 E as “60”, LB as “61”, and LT as “62”. Then, the monitor rate for the user OAM corresponding to the user PID “8” for the OAM packets of the user #I is set in the input-side OAM policer unit 24 .
- the input-side OAM policer unit 24 sets the monitor rate for the communication packets (or the user OAM) corresponding to the same user PID “8” shared by the OAM packets of the users #G and #I, and executes the process of controlling by policing the OAM packets of the users #G and #I at the same monitor rate according to the single token bucket scheme.
- the output-side OAM policer unit 32 and the output-side buffer unit 33 are not included in the output port unit 12 , but double as the input-side OAM policer unit 24 and the input-side buffer unit 25 in the input port unit 11 ; and the monitor rate corresponding to the OAM packets received by the fourth flow identification unit 71 of the output port unit 12 side is set in the input-side OAM policer unit 24 . Therefore, compared to the packet transmission apparatus 2 according to the first embodiment, the memory capacity may be reduced in an amount equivalent to that of the output-side OAM policer unit 32 and the output-side buffer unit 33 .
- the OAM packets of the users received by the input port unit 11 and the output port unit 12 are set at the same monitor rate, and therefore, the memory consumption may be reduced.
- the OAM packet monitor rate corresponding to the user PID 41 B or the OAM type PID 51 C is set, based on the OAM type request flag 41 C, in the input-side OAM policer unit 24 .
- the provision of the policer unit for the OAM packets (input-side OAM policer unit 24 ) separate from the policer unit for the communication packets (input-side communication policer unit 23 ) may reduce the burden on the CPU 13 and the buffer unit (input-side buffer unit 25 ). Therefore, without setting the OAM type request flag 41 C, a similar effect may be obtained by setting the monitor rate corresponding to one of the user PID 41 B or the OAM type PID 51 C or 61 E in the input-side OAM policer unit 24 .
- the monitor rate is managed with PID.
- an arrangement may be made in which the monitor rate corresponding to a specified PID “0” is set as “nil” so that when the specified PID “0” is acquired by the second flow identification unit 22 or the third flow identification unit 31 (fourth flow identification unit 71 ), the policing control operation is not carried out on the input-side OAM policer unit 24 side or the output-side OAM policer unit 32 side. In this case, whether the policing control operation on the OAM packets is executed or not may be easily set.
- a monitor rate high enough to make it substantially impossible to obtain the effect of policing the OAM packets may be assigned to a specified PID, and upon acquisition of such a specified PID on the second flow identification unit 22 side or the third flow identification unit 31 (fourth flow identification unit 71 ) side, a high monitor rate may be set on the input-side OAM policer unit 24 side or the output-side OAM policer unit 32 side. In this case, the effect of policing the OAM packets cannot be substantially obtained, and therefore, whether the policing control operation on the OAM packets is executed or not may be easily set.
- an independent setting flag not to execute the policing control operation on the OAM packets is provided so that the policing control operation on the OAM packets may be prohibited based on the particular setting flag. In this case, whether the policing control operation on the OAM packets is executed or not may be easily set.
- the input-side OAM policing setting unit 57 or the output-side OAM policing setting unit 69 sets the monitor rate corresponding to the OAM type PID or the user PID of the OAM packets on the input-side OAM policer unit 24 and or output-side OAM policer unit 32 , respectively.
- the monitor rate set on the input-side OAM policer unit 24 or the output-side OAM policer unit 32 exceeds the tolerable rate of the CPU 13 , the setting of the particular monitor rate may be rejected, and when the monitor rate set does not exceed the tolerable rate of the CPU 13 , the setting of the monitor rate may be permitted.
- the OAM packets may be discarded by a policing-control operation according to the single token bucket scheme on the input-side OAM policer unit 24 side or the output-side OAM policer unit 32 side using a counter for counting the number of discarded packets.
- the number of the OAM packets discarded is statistically determined in units of the port, the service, or the OAM type; and the statistical result may be displayed on a display unit (not shown).
- a similar counter may be used to count the number of packets discarded for the input-side communication policer unit 23 .
- the invention is not limited to these three types.
- the whole or a part of the various processes described above in the embodiments as automatically executable may be executed manually, and conversely, the whole or a part of the processes described as manually executed may be executed automatically.
- the processing steps, the control steps, the specific names, the various data, and other information including parameters described in the embodiments above may be changed appropriately.
- each component element of each device illustrated in the drawings is described conceptually but may not necessarily be physically configured as illustrated. Thus, the specific form of each device is not confined to the illustrated one.
- the whole or an arbitrary part of the various processing functions executed by the devices described above may be executed alternatively by the CPU (central processing unit) (or a microcomputer such as a MPU (micro processing unit) or MCU (micro controller unit)), the program analyzed and executed by the CPU (or a microcomputer such as a MPU or MCU), or the hardware based on the wired logics.
- the CPU central processing unit
- MPU micro processing unit
- MCU micro controller unit
- the maintenance packets are extracted from the user flow, and the transparent output of the maintenance packets thus extracted is controlled based on the monitor rate setting, for example, by the policing-control operation on the extracted maintenance packets. Therefore, in the apparatus and the method disclosed above, the discard of the maintenance packets which otherwise might affect other users may be positively prevented from affecting the other users without imposing any burden on the buffer, etc. arranged in the front stage of the controller as well as on the controller even when the maintenance packets are received at an abnormally high rate or in a great amount.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Claims (16)
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2008-230235 | 2008-09-08 | ||
JP2008230235A JP4734388B2 (en) | 2008-09-08 | 2008-09-08 | Packet transmission apparatus and packet transmission method |
Publications (2)
Publication Number | Publication Date |
---|---|
US20100061267A1 US20100061267A1 (en) | 2010-03-11 |
US8089876B2 true US8089876B2 (en) | 2012-01-03 |
Family
ID=41799202
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/554,214 Expired - Fee Related US8089876B2 (en) | 2008-09-08 | 2009-09-04 | Packet transmission apparatus and packet transmission method |
Country Status (2)
Country | Link |
---|---|
US (1) | US8089876B2 (en) |
JP (1) | JP4734388B2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100246425A1 (en) * | 2009-03-31 | 2010-09-30 | Fujitsu Limited | Packet processing apparatus, interface unit and method thereof |
US8830841B1 (en) * | 2010-03-23 | 2014-09-09 | Marvell Israel (M.I.S.L) Ltd. | Operations, administration, and maintenance (OAM) processing engine |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4734388B2 (en) * | 2008-09-08 | 2011-07-27 | 富士通株式会社 | Packet transmission apparatus and packet transmission method |
JP5432018B2 (en) | 2010-03-24 | 2014-03-05 | Necエンベデッドプロダクツ株式会社 | Library device |
JP6011540B2 (en) * | 2011-09-20 | 2016-10-19 | 日本電気株式会社 | Diagnostic system |
KR101727779B1 (en) * | 2013-01-02 | 2017-04-17 | 한국전자통신연구원 | PON Reach Extender and method thereof based on Tunable Optical Transceiver |
CN104394025A (en) * | 2014-12-19 | 2015-03-04 | 成都朗锐芯科技发展有限公司 | OAM (Operation, Administration and Maintenance) message sending method |
Citations (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH05284172A (en) | 1992-03-30 | 1993-10-29 | Nippon Telegr & Teleph Corp <Ntt> | Cell monitoring device |
JPH0637790A (en) | 1992-07-21 | 1994-02-10 | Fujitsu Ltd | Policing equipment |
US6735219B1 (en) * | 1998-09-10 | 2004-05-11 | International Business Machines Corporation | Packet-processing apparatus and packet switch adapter for the processing of variable-length packets and a method thereof |
US20040131064A1 (en) * | 1994-01-21 | 2004-07-08 | Alcatel Canada Inc. | Digital communications system |
US20050083845A1 (en) * | 2003-10-21 | 2005-04-21 | Comcast Cable Communications, Inc. | Method and packet-level device for traffic regulation in a data network |
US7027394B2 (en) * | 2000-09-22 | 2006-04-11 | Narad Networks, Inc. | Broadband system with traffic policing and transmission scheduling |
US7042848B2 (en) * | 2001-05-04 | 2006-05-09 | Slt Logic Llc | System and method for hierarchical policing of flows and subflows of a data stream |
US7236458B2 (en) * | 2002-04-24 | 2007-06-26 | Samsung Electronics Co., Ltd. | Method for monitoring traffic in packet switched network |
US20070177504A1 (en) | 2006-01-31 | 2007-08-02 | Fujitsu Limited | Hub Apparatus |
US7349338B2 (en) * | 2003-04-15 | 2008-03-25 | Lucent Technologies Inc | Scheduler and method for scheduling transmissions in a communication network |
US20100061267A1 (en) * | 2008-09-08 | 2010-03-11 | Fujitsu Limited | Packet transmission apparatus and packet transmission method |
US7688727B1 (en) * | 2000-04-17 | 2010-03-30 | Juniper Networks, Inc. | Filtering and route lookup in a switching device |
-
2008
- 2008-09-08 JP JP2008230235A patent/JP4734388B2/en not_active Expired - Fee Related
-
2009
- 2009-09-04 US US12/554,214 patent/US8089876B2/en not_active Expired - Fee Related
Patent Citations (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH05284172A (en) | 1992-03-30 | 1993-10-29 | Nippon Telegr & Teleph Corp <Ntt> | Cell monitoring device |
JPH0637790A (en) | 1992-07-21 | 1994-02-10 | Fujitsu Ltd | Policing equipment |
US7327688B2 (en) * | 1994-01-21 | 2008-02-05 | Alcatel Canada Inc. | Digital communications system |
US20040131064A1 (en) * | 1994-01-21 | 2004-07-08 | Alcatel Canada Inc. | Digital communications system |
US6735219B1 (en) * | 1998-09-10 | 2004-05-11 | International Business Machines Corporation | Packet-processing apparatus and packet switch adapter for the processing of variable-length packets and a method thereof |
US7688727B1 (en) * | 2000-04-17 | 2010-03-30 | Juniper Networks, Inc. | Filtering and route lookup in a switching device |
US7027394B2 (en) * | 2000-09-22 | 2006-04-11 | Narad Networks, Inc. | Broadband system with traffic policing and transmission scheduling |
US7042848B2 (en) * | 2001-05-04 | 2006-05-09 | Slt Logic Llc | System and method for hierarchical policing of flows and subflows of a data stream |
US7236458B2 (en) * | 2002-04-24 | 2007-06-26 | Samsung Electronics Co., Ltd. | Method for monitoring traffic in packet switched network |
US7349338B2 (en) * | 2003-04-15 | 2008-03-25 | Lucent Technologies Inc | Scheduler and method for scheduling transmissions in a communication network |
US20050083845A1 (en) * | 2003-10-21 | 2005-04-21 | Comcast Cable Communications, Inc. | Method and packet-level device for traffic regulation in a data network |
JP2007509577A (en) | 2003-10-21 | 2007-04-12 | コムキャスト ケーブル ホールディングス,エルエルシー | Data network traffic adjustment method and packet level device |
WO2005043931A2 (en) | 2003-10-21 | 2005-05-12 | Comcast Cable Holdings, Llc | Method and packet-level device for traffic regulation in a data network |
JP2007208518A (en) | 2006-01-31 | 2007-08-16 | Fujitsu Ltd | Concentrator |
US20070177504A1 (en) | 2006-01-31 | 2007-08-02 | Fujitsu Limited | Hub Apparatus |
US20100061267A1 (en) * | 2008-09-08 | 2010-03-11 | Fujitsu Limited | Packet transmission apparatus and packet transmission method |
Non-Patent Citations (1)
Title |
---|
English translation of Japanese Office Action dated Jul. 27, 2010 issued in corresponding Japanese Patent Application 2008-230235. |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100246425A1 (en) * | 2009-03-31 | 2010-09-30 | Fujitsu Limited | Packet processing apparatus, interface unit and method thereof |
US8369223B2 (en) * | 2009-03-31 | 2013-02-05 | Fujitsu Limited | Packet processing apparatus, interface unit and method thereof |
US8830841B1 (en) * | 2010-03-23 | 2014-09-09 | Marvell Israel (M.I.S.L) Ltd. | Operations, administration, and maintenance (OAM) processing engine |
US9680720B1 (en) | 2010-03-23 | 2017-06-13 | Marvell Israel (M.I.S.L.) Ltd. | Operations, administration, and maintenance (OAM) engine |
Also Published As
Publication number | Publication date |
---|---|
JP2010068052A (en) | 2010-03-25 |
JP4734388B2 (en) | 2011-07-27 |
US20100061267A1 (en) | 2010-03-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8089876B2 (en) | Packet transmission apparatus and packet transmission method | |
JP5233504B2 (en) | Route control apparatus and packet discarding method | |
US8451742B2 (en) | Apparatus and method for controlling data communication | |
US9413611B2 (en) | Generating and enforcing a holistic quality of service policy in a network | |
CN112242914B (en) | Network abnormal root cause positioning method, device and system and computer storage medium | |
US7522525B2 (en) | L2 switch | |
KR100809261B1 (en) | High speed plc network-ethernet bridge system supporting qos | |
US20130042317A1 (en) | Frontend system and frontend processing method | |
JP5883743B2 (en) | Method for reducing communication interruption time in packet communication networks | |
US9608927B2 (en) | Packet exchanging device, transmission apparatus, and packet scheduling method | |
US9319334B2 (en) | Apparatus and method for controlling congestion in a communication network | |
RU2586062C2 (en) | Network communication device and method for selective restriction of bandwidth of transmission frame | |
US9065862B2 (en) | Communication device, method for controlling the communication device, and communication system | |
JP4946909B2 (en) | Frame monitoring apparatus and frame monitoring method | |
US8531951B2 (en) | Network system, management computer, and bandwidth management method | |
US20170054646A1 (en) | Bandwidth control device and bandwidth control method | |
US8331389B2 (en) | Relay device and band controlling method | |
CN110417656A (en) | A kind of QoS guarantee system and method based on SDN network | |
JP2005278215A (en) | Communication system and communication method | |
US8675506B2 (en) | Network system, edge node, and access device | |
US8780736B2 (en) | Communication apparatus and heat generation suppressing method | |
JP5814969B2 (en) | Management system and management method | |
JP5032535B2 (en) | Frame transmission band control system and frame transmission band control method | |
JP2017069691A (en) | Relay device and relay system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: FUJITSU LIMITED,JAPAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KATSURA, YUICHIRO;EHARA, TETSUO;HACHIYA, KOJI;AND OTHERS;REEL/FRAME:023225/0047 Effective date: 20090619 Owner name: FUJITSU LIMITED, JAPAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KATSURA, YUICHIRO;EHARA, TETSUO;HACHIYA, KOJI;AND OTHERS;REEL/FRAME:023225/0047 Effective date: 20090619 |
|
ZAAA | Notice of allowance and fees due |
Free format text: ORIGINAL CODE: NOA |
|
ZAAB | Notice of allowance mailed |
Free format text: ORIGINAL CODE: MN/=. |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
CC | Certificate of correction | ||
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20240103 |