Method and apparatus for transparent intermediate system based filtering on a lan of multicast packets
Abstract
This record has no abstract on file.
Term
Term ended
Expired 11 October 2016, 9.9 years ago.
- Priority
- Filed
- Granted
- Expired
- Today
36 claims: 18 independent, 18 dependent
- 1ソース・アドレスとデスティネーション・アドレスを有するパケットを転送しかつ受信できる複数のエンド・システムと、ネットワーク・セグメントに接続するための複数のポートを持ち、パケットを透過的に発送することができる複数のLAN中間システムとを含むLANにおいて、好ましくないWANマルチキャスト・パケットの転送を減らす方法であって、前記中間システムの少なくとも一つにおいて前記エンド・システムに対するWANマルチキャスト質問を検出し、前記WANマルチキャスト質問が受信された各ポートに対しこれらのポートを質問ポートとして指定する識別子を前記中間システムにおいて記録し;WANマルチキャスト・パケットを受信するために前記エンド・システムからのリクエストであって前記エンド・システムによって前記中間システムのデスティネーション・アドレス以外のデスティネーション・アドレスに向けられたリクエストを前記中間システムにおいて受信し;前記リクエストが前記リクエスト中で特定されるマルチキャスト・アドレスと共に受信されたポートに対する識別子を前記中間システムにおいてストアし;質問ポートとして指定された前記中間システム上のポートのみの中から前記リクエストを発送し;パケットのマルチキャスト・デスティネーション・アドレスを決定するために受信された全てのWANマルチキャスト・データ・パケットを前記中間システムにおいて調べ;前記マルチキャスト・パケットのデスティネーション・アドレスに対するリクエスト又は質問のいずれかが受信されたこれらのポートのみから前記WANマルチキャスト・データ・パケットを発送するLANにおいて好ましくないWANマルチキャスト・パケットの転送を減らす方法。
- 2請求項 1記載の方法において、さらに前記中間システムに接続されたどのポートも質問ポートとして指定されておらず、前記中間システム上の全てのポートから前記WANマルチキャスト質問パケットを発送する時には、中間システムにおいてWANマルチキャスト質問パケットを生成することを含む方法。
- 3請求項 2記載の方法において、さらに前記中間システムのポートの一つで受信されたWANマルチキャスト質問のソース・アドレスを前記中間システムにおいて調べ;前記受信されたソース・アドレスと前記中間システムのソース・アドレスとの比較をし;前記比較に基づいて、前記ポートを質問ポートに指定するか、又は前記中間システムにおいてWANマルチキャスト質問を生成することを含む方法。
- 4前記受信されたソースアドレスが、前記中間システムのソース・アドレスよりも小さければ、前記ポートは質問ポートとして指定される、ことを特徴とする請求項3記載の方法。
- 5前記比較はWANソースアドレス相互を比較する、ことを特徴とする請求項3記載の方法。
- 6前記比較はLANソースアドレス相互を比較する、ことを特徴とする請求項3記載の方法。
- 7前記比較は受けたWANソースアドレスと仮のWANソースアドレスとを比較する、ことを特徴とする請求項3記載の方法。
- 8前記比較は、前記WANソースアドレス相互の値がタイであれば、LANソースアドレス相互を比較する、ことを特徴とする請求項7記載の方法。
- 9前記LANが複数の中間システムを含み、これらの中間システムの幾つかが第1のグループに属し、その第1のグループの中間システムは第2のグループに属する中間システムとは異なる機能を有し、2つの異なる仮のWANマルチキャスト・アドレスが前記グループにそれぞれ割り当てられ、一方のグループの中間システムによって発生されたWANマルチキャスト質問が他のグループのポートで受けられると、当該ポートが常に質問ポートとされる、ことを特徴とする請求項8記載の方法。
- 10特定のタイムアウト時間が設定され、質問ポートと指定されたポートにおいて前記タイムアウト時間中に質問パケットが受信されなければ、前記ポートと指定されたポートは、非質問ポートと再指定される、ことを特徴とする請求項1記載の方法。
- 11前記質問ポートにおいて質問ポートを受信する頻度をサンプリングし、サンプルされた頻度の数倍に前記タイムアウト時間を設定することを特徴とする請求項10記載の方法。
- 12前記LANの中間システムは、LANユニキャスト・パケットを、そのWANルーティング情報の調査をすることなく、発送するデバイスである、ことを特徴とする請求項1記載の方法。
- 13前記LANの中間システムは、前記エンド・システムに対して、パケットを、その内容またはヘッダに変更を加えることなく、透過的に送る、ことを特徴とする請求項1記載の方法。
- 14前記エンド・システムは、前記LANを前記WANに接続する複数のルータとコミュニケーションを行い、そして、前記ルータおよび前記エンド・システムはコントロール情報の交換を行い、前記コントロール情報には前記WANマルチキャスト質問および前記リクエストが含まれている、ことを特徴とする請求項1記載の方法。
- 15前記エンド・システムは、TCP/IPプロトコル・スイートを使用する複数のルータとコミュニケーションを行う、ことを特徴とする請求項14記載の方法。
- 16前記LANの中間システムの少なくとも1つは、IEEE802.1dの仕様に準拠している、ことを特徴とする請求項1記載の方法。
- 17前記複数のエンド・システムおよび前記中間システムは、イーサネットプロトコルを使用してコミュニケーションを行う、ことを特徴とする請求項1記載の方法。
- 18前記WANマルチキャスト質問および前記WANマルチキャスト・パケットは、LANグループ・パケットとしてカプセル化され、前記LANグループパケットは、前記WANマルチキャスト・アドレスへとアルゴリズムで変換できるLANマルチキャスト・アドレスを有し、前記中間システムが、前記LANマルチキャスト・アドレスを、検出し、ストアし、調べる、ことを特徴とする請求項1記載の方法。
- 19割り当てられた前記仮のアドレスは、前記WANソース・アドレスへとアルゴリズムで変換できるLANグループ・アドレスである、ことを特徴とする請求項7記載の方法。
- 20ローカル・エリア・ネットワークにおいて用いるブリッジであって、ネットワーク・セグメントからのデータを転送および受信することができる複数のポートと;このポート上で受信したデータをバッファし、又は前記ポート上で転送されるのを待つ複数のシェアード・バッファ・メモリと;前記ポートの一つにおいて受信されたデータ・パケットのソース・アドレスとデスティネーション・アドレスを読み取ることができるブリッジ・コントローラと;このコントローラが特定のセグメント上で受信されたあらゆるパケットのソース・アドレスを前記特定のセグメントの識別子と共にストアし、前記ブリッジ・コントローラが受信されたあらゆるマルチキャスト・リクエスト・パケットのマルチキャスト・アドレスを前記パケットが受信されたポートの識別子と共にストアするブリッジ・フィルタ・テーブルと;を備え、 前記ブリッジ・フィルタ・テーブルには、 前記ブリッジのポート毎に、質問ポートとして指定されているか否かを示すインジケータを含む質問ポート・エントリが設けられ、 複数のデスティネーション・アドレス・エントリが設けられ、これらのデスティネーション・アドレス・エントリのそれぞれには、デスティネーション・アドレスと、前記ブリッジのポートのインジケータであって、前記ブリッジで受けられ前記デスティネーション・アドレスを有するパケットを前記ポートに発送すべきか否かを示すインジケータとが含まれている、 ことを特徴とするブリッジ。
- 21前記複数のデスティネーション・アドレス・エントリには、グループ・デスティネーション・アドレスと、前記ブリッジのポートのインジケータであって、前記ブリッジで受けられ前記グループ・デスティネーション・アドレスを有するパケットを前記ポートに発送すべきか否かを示すインジケータとが含まれている、ことを特徴とする請求項 20 記載のブリッジ。
- 22前記各ポートの前記タイムアウト時間の値をストアするメモリ・ロケーションがあり、ポートに対する前記質問ポート・エントリ・インジケータが、そのポートのタイムアウト時間内にマルチキャスト質問パケットの受信がなければ、質問ポートでないことにセットされる、ことを特徴とする請求項21記載のブリッジ。
- 23質問ポートとして指定されたポートがない時に、マルチキャスト質問パケットを発生する手段を、さらに有する、ことを特徴とする請求項21記載のブリッジ。
- 24複数のエンド・システムと複数のブリッジを備え、前記複数のエンド・システムのそれぞれはネットワーク・セグメントとのコネクションを有し、このエンド・システムがそこからデータを受信することを希望するリクエストされたマルチキャスト・アドレスを有するマルチキャスト・レポート・パケットを前記セグメント上で転送することができ;前記複数のブリッジのそれぞれは少なくとも2つのネットワーク・セグメントとコネクションを持ち、前記ブリッジのうちの少なくとも一つは前記ネットワーク・セグメント上で転送されたマルチキャスト・レポート・パケットを検知することができるとともに、前記リクエストされたマルチキャスト・アドレスの識別子を前記セグメントの識別子と共にストアすることができ、前記少なくとも一つのブリッジは、受信したマルチキャスト・パケットをこれらのマルチキャスト・パケットをリクエストするマルチキャスト・レポート・パケットが受信されたこれらのセグメントにのみ発送する ものであり、 ブリッジがさらにポートに受けたマルチキャスト質問パケットを検出することができ、そのポートを質問ポートと指定し、前記ブリッジが質問ポートに受けた質問パケットの頻度を決定し、その頻度の何倍化にタイムアウト間隔を設定し、前記ブリッジがそのタイムアウト間隔の間に質問パケットを受けなかったとき質問ポートを非質問ポートに指定することを特徴としたローカル・エリア・ネットワーク。
- 25少なくともLANソース・アドレスとLANデスティネーション・アドレスとを有するレイヤー2のLANパケットを転送しかつ受信できる複数のエンド・システムと、ネットワーク・セグメントに接続するための複数のポートを持ち、レイヤー2においてパケットを透過的に発送することができる複数のレイヤー2のLAN中間システムとを含むLANにおいて、好ましくないレイヤー3のWANマルチキャスト・パケットの転送を減らす方法であって、前記中間システムの少なくとも一つにおいて、すべてのレイヤー2グループ・パケットのコンテンツを調べることによって前記エンド・システムに対してエンキャプシュレートされたレイヤー3のWANマルチキャスト質問を検知し、前記WANマルチキャスト質問が受信された各ポートに対してこれらのポートを質問ポートとして指定する識別子を前記中間システムにおいて記録し;WANマルチキャスト・パケットを受信するために、前記エンド・システムからのレイヤー3のリクエストであって前記エンド・システムによって前記中間システムのデスティネーション・アドレス以外のデスティネーション・アドレスに向けられたリクエストを前記中間システムにおいて受信し、前記リクエストのレイヤー3のコンテンツを調べ;前記リクエストが前記リクエスト中で特定されたレイヤー2のグループ・アドレスと共に受信されたポートに対する識別子を前記中間システムにおいてレイヤー2のフィルタリング・テーブルの中に記録し;質問ポートとして指定された前記中間システム上のこれらのポートのみの中から前記リクエストを発送し;前記中間システムにおいて前記レイヤー2のフィルタリング・テーブルに基づいてあらゆるLANグループ・アドレスされたデータ・パケットをフィルタリングし、これによって前記マルチキャスト・パケットのデスティネーション・アドレスに対するリクエスト又は質問のいずれかが受信されたこれらのポートのみから前記WANマルチキャスト・データ・パケットを発送するLANにおいて好ましくないレイヤー3のWANマルチキャスト・パケットの転送を減らす方法。
- 26請求項25 に記載された方法であって、さらに前記中間システムに接続されたどのポートも質問ポートとして指定されておらず、前記中間システム上の全てのポートから前記WANマルチキャスト質問パケットを発送する時に、中間システムにおいてレイヤー3のWANマルチキャスト質問パケットを生成することを含む方法。
- 27前記中間システムにおいてそのポートの1つで受けたWANマルチキャスト質問のソース・アドレスを調べ、受けたソース・アドレスと、中間システムのソース・アドレスとを比較し、比較の結果に基づいて前記ポートを質問ポートとして指定するか、前記WANマルチキャスト質問を発生しつづけるかのいずれかを行うことを特徴とする請求項 26 記載の方法。
- 28前記ポートは、前記受けたソースアドレスが前記中間システムのソース・アドレスよりも小さいときに、質問ポートとして指定される、ことを特徴とする請求項 27 記載の方法。
- 29前記比較は、受けたWANソース・アドレスと前記中間システムに割り当てられた仮のWANソース・アドレスとの間で行う、ことを特徴とする請求項 27 記載の方法。
- 30前記比較は、LANソース・アドレス相互を、前記WANソース・アドレスの値相互にタイがあれば、との間で行う、ことを特徴とする請求項 29 記載の方法。
- 31前記LANが複数の中間システムを含み、これらの中間システムの幾つかが第1のグループに属し、その第1のグループの中間システムは第2のグループに属する中間システムとは異なる機能を有し、2つの異なる仮のWANマルチキャスト・アドレスが前記グループにそれぞれ割り当てられ、一方のグループの中間システムによって発生されたWANマルチキャスト質問が他のグループのポートで受けられると、当該ポートが常に質問ポートとされる、ことを特徴とする請求項 30 記載の方法。
- 32前記LANのISはパケットの内容を試験せずかつ変えずにLANキャスト・パケットを送る層2デバイスである請求項 25 記載の方法
- 33前記エンド・システムがLANをWANに接続さする複数のルータと層3プロトコルで通信し、そのルータとエンド・システムがWANマルチキャスト質問とそのリクエストを含むコントロール情報を交換する請求項 25 記載の方法。
- 34前記エンド・システムがTCP/IPスイートのプロトコルを用いて複数のルータと通信する請求項 25 に記載された方法。
- 35LAN ISの少なくとも一つはIEEE 802.1dに記載された使用に合致する 請求項25に記載された 方法。
- 36複数のエンド・システムとISがイーサネットで通信する請求項 25 に記載の方法
Independent claims36
2 paragraphs, as filed
<u style="single">Background of the invention</u>The present invention relates to the transfer of information between multiple digital devices on a network and between multiple networks on an internetwork. The present invention is particularly limited to end systems in which an intermediate system within a local area network (LAN) wants to receive multicast packets from a wide area network, or internetwork, to the LAN. With respect to devices and methods that allow transparent filtering to be sent. Related techniques are discussed in U.S. Patent Application No. 08 / 502,835, which is assigned to the applicant of the present application.<u style="single">Standard</u>This specification assumes that you have some knowledge of the general concepts, protocols, and devices currently used in LAN networking and WAN Internetworking applications. The set of protocols used for networking within a LAN is the IEEE802 protocol suite (available from the Institute for Electrical and Electronics Engineers (IEEE)). These IEEE802 protocols were revised and republished as ISO8802 by the International Organization for Standardization (ISO). The protocol specified as IEEE802.3 in the IEEE802 protocol is usually referred to as Ethernet. Another set of protocols used for internetworking, or coupling of multiple LANs, is referred to as the TCP / IP protocol suite. (TCP and IP are Transmission Control Protocol and An acronym for Internet Protocol. The TCP / IP Protocol Suite is published in a series of documents published by the Internet Engineering Task Force. The document is called RFC (Request For Comment) and can be found at the URL "http // www.cis.ohio-state.edu: 80 / hypertext / information / rfc.html" or via FTP on ds.internet.net. Obtainable. An overview of the concepts required for understanding the present invention is given below. For a more detailed explanation, refer to the above standard book or reference books including "TCP / IP Illustrated" by RW Stevens published by Addison Wesley in 1994.<u style="single">Figure 1</u>Figure 1 illustrates a type of local area network (LAN) 40 that can be used today in moderately sized offices and academic environments and that can effectively adopt the present invention. A LAN is a collection of various hardware and software elements that work together to allow multiple digital devices to exchange data within a LAN, with an external wide area as shown by 42,44. It also enables an internet connection with a network (WAN). A typical current LAN, such as 40, has a large number of LAN intermediate systems (IS), such as those shown in 60-62, which are responsible for transferring data across the LAN, and 50a-50d, which represent end-user equipment. Includes multiple end systems (ES) such as, 51a ~ 51d, 52a ~ 52d. The ES is a well-known end-user data processing device (such as a personal computer, workstation, printer, digital telephone or real-time display). Different types of ES can work together on the same LAN. If there is a LAN, LAN Is60-61 are called bridges, and WAN IS63,64 are called routers. However, different configurations of LANs are possible, and the present invention is not limited to the network applications shown in FIG. The LAN shown in FIG. 1 has segments 70a to 70e, 71a to 71e, 72a to 72e. A segment is generally a continuous, length of wire, optical fiber, or a single interconnected medium, such as a coaxial cable or a particular frequency band. One segment like the 70a only connects two devices, while one segment like the 72d is the Carrier Sense Multiple Access / Collision Detect (CSMA / CD) protocol or token bus or You can connect multiple devices that use other multiple access protocols such as Token Ring. A signal transferred over a single segment, such as the 72d, is heard simultaneously by all of the connected ESs and ISs in that segment.<u style="single">packet</u>In a LAN such as 40, data is generally transferred as independent packets between ESs. Each packet contains a header, which contains at least a destination address that identifies the final address, and more generally other forwarding information such as the source address and forwarding priority. The ES normally continuously listens to the destination addresses of all packets sent to those ES segments, but only for packets whose destination address matches the ES address. Receive. An ES such as 52g can transfer data to any ES on the LAN by forwarding a data packet containing the destination address of the desired destination. If, like the ES52d, the desired destination is directly connected to the same segment, the ES52d will only hear and receive the packet in transit from the ES52g. However, if the destination ES is not directly connected to the same segment as the source ES, the task of transferring data to the segment to which the destination ES is connected is the responsibility of LAN40. Normally, the source ES does not know if the destination ES in its LAN is directly connected to that segment. The source ES simply forwards the packet with the destination address and considers the network to deliver the packet. Forwarding within a LAN is usually source driven, that is, the LAN sends a data packet from the source to a destination address identified within that packet, and that destination ES is actually of that packet. It transfers regardless of whether you want to receive it. Generally, a packet contains user data such as part of a data file or part of a video stream displayed to the user that the ES user wants to receive. Some of the above data files , Will be reassembled in ES after all the packets that make up the data file have been received. Packets also include control packets that contain control information for communication within the network.<u style="single">Drivers, adapters, and LAN topologies</u>Each of the IS and ES in Figure 1 contains one or more sets of adapters and drivers. Adapters typically include connectors and circuits used for communication over the segment and are converted from digital forms used by computer circuits within IS or ES to forms that can be transferred over the segment. An ES like the 50b has one adapter for connecting to that one segment. LAN like 61 The IS contains 5 adapters for each of the 5 segments connected to it. A driver is a set of instructions that resides on a device, which allows the device to perform a variety of tasks defined by different network protocols. A driver is usually a software program stored in IS or ES, and it is possible to change the driver without changing the hardware of IS or ES. LANs can change the connection and topology of devices to each other. In the context of communication networks, the term topology refers to the way stations are connected to a network. Common LAN topologies include buses, trees, rings, and stars. The LAN also has a hybrid topology consisting of a mixture of these. The entire LAN shown in Figure 1 is basically a tree topology, but segment 72d is a bus topology. Although the ring topology is not shown in Figure 1, it will be appreciated that the present invention can be used for LANs in the ring topology.<u style="single">bridge</u>LAN in LAN40 IS includes bridges 60-63. In this field of technology, a bridge is the kind of computer optimized for high-speed data communication between two or more segments. For example, bridge 60 is a computer that has a processor, memory for storing network information, connections to two or more individual segments, and packets received for transfer from one segment to another. Has buffer memory to store. The bridge 60 receives a packet from a source segment such as 70e, stores the packet, and then forwards the packet to another segment, such as 70a, when the other segment is silent. The bridge does not make any changes to a packet received on one segment before forwarding that packet to another segment. The bridge is not required for LAN operation, in fact the ES to which the bridge is connected, The bridge is invisible to any of the other bridges and routers. Invisible means the following. That is, traditional bridges do not communicate control packets to other devices in the network, and when communicating between two different segments, both the sending and receiving devices do. It means doing it without knowing that it is not on the same segment. Simply, the bridge temporarily stores all packet data received on that connection, one of the ports, and then, if each other port is available, the bridge sends the packet to each other. Send from the port, that is, perform bridge operation. Even in this simplest one, a bridge like 60 acts to separate network traffic on the segment, reducing the chance of collisions between packets. Modern bridges have a filtering function, as described below, which allows the bridge to learn the LAN address of all ESs through that port and only to the port to which the packet destination ES is connected. Send a packet. Filtering bridges allow you to quickly look up the LAN address of each packet you receive and decide whether to bridge that packet and to which segment you should bridge it. For example, when the filtering bridge 62 receives a packet that is on segment 72a and is addressed to 52b, the packet is bridged only to segment 72b and not to segment 72c. To achieve this filtering function, the bridge must somehow know which ES is attached to each segment connected to it. This is usually done in one of two ways: The first is to configure the bridge with a network manager (person) who knows the LAN address of the ES connected to each segment. The eye is to allow the bridge to know the LAN address of the ES connected to each segment when it receives the packet. The bridge can know (learn) the ES connected to each of its segments by examining the LAN source address of the packet received on a particular port. Self-learning bridges typically store information learned by looking up the source address of a packet in bridge memory, referred to here as the Bridge Filtering Table (BFT). Once the entry is placed in the BFT, the bridge looks up the LAN destination address of the buffered packet when it receives the packet, and if the destination ES receives the packet according to the BFT, the segment. If above, the packet is presumed to have already been received by the destination ES and the bridge discards the buffered packet. If the destination ES is on a different segment than the segment from the ES that sent the packet, the bridge performs the bridge operation by forwarding the packet to the segment of the destination ES. If the destination address is not found in the BFT, the bridge must bridge the packet to all other segments to ensure that the original ES can receive the packet. In this way, the self-learning bridge gradually increases learning about the ES connected to it and gradually reduces unnecessary data flow through the LAN. In traditional bridges, configuring BFT and subsequent packet filtering is achieved transparently by the bridge without the ES knowing the existence of the bridge, that is, without the ES having to send control packets to the bridge. Will be done. Traditional bridges forward and receive control packets to and from other devices in the LAN. I don't believe it. Some with traditional bridges execute an algorithm known as the spanning tree algorithm. The spanning tree algorithm ensures that segments connected to one or more bridges receive only packets from one of the bridges. The entire algorithm is described in IEEE Standard 802.1d.<u style="single">LAN broadcast and group address packets</u>The discussion so far has assumed that every packet in the LAN has a destination address that indicates delivery to only one destination. This is referred to in the art as unicast packets. Sources in LAN40 can also forward to all ESs in the network by using a special address known as the broadcast address. A broadcast address is a special destination address reserved for broadcast packets by the LAN protocol. In most LAN implementations, the broadcast address cannot be the source address of the packet, so the broadcast address should never be a BFT entry. Every bridge that receives a broadcast packet looks for the destination address of the packet in its BFT and fails, so it bridges the packet to all ports. All those ports are exactly the destinations of broadcast packets. Alternatively, the bridge is preconfigured by driver software to identify the broadcast packet, thereby sending the broadcast packet to all ports. For standard 802.3 Ethernet, the Ethernet address is 48 bits. Broadcast addresses are defined as FFFF or all 1. Standard 802. 3 also defines a set of Ethernet group addresses that indicate a number of destinations greater than 1 but less than all destinations Ethernet group addresses are assigned to individual ESs or ISs. No reserve address. Within a standard conventional LAN, all packets with Ethernet group addresses are broadcast to all ESs in the LAN, and it is up to each ES to receive packets with group addresses.<u style="single">Router</u>An ES in LAN40 can communicate with other ESs in LAN40 directly if the other ESs are in the same physical segment, otherwise through a bridge. But if the ES wants to communicate with the ES or other services on different LANsThat data must be transferred over a WAN such as 42. Figure 2 shows WAN42. WAN42 is a network of multiple networks, that is, an internetwork. (The largest and most well-known internetwork is the World Wide Internet.) WANs are usually shown here as routers 64,68a-68e, and are numerous large-sized optimized for WAN forwarding. Equipped with a computer. A router is usually a computer larger than a bridge, but like a bridge, a router is also a processor, a memory that stores network information, And have connections to two or more separate segments. Some routers, like Router 64, provide WAN services to the LAN, and in addition can send WAN packets through a mesh network, enabling WAN communication. The other router is a multi-user, multi-purpose computer, that is, a file server having a routing function. Yet another router is a computer dedicated to handling WAN data traffic. Communication of WAN packets over WAN64 through routers is very different from packet communication within LAN40, with different protocols with different addressing schemes. Unlike bridges, routers communicate control packets to all installed ESs and to other routers in the WAN. A router uses the information it receives via control packets, and perhaps also the configuration information provided by the operator (person), to build a representation for that router in the network. The router stores it in the routing table. The router looks up the WAN destination address of every packet it receives and uses the information stored in the routing table to make individual routing decisions about the packet in the packet's destination address, packet header. Other information, And based on knowledge of the dynamic state of the WAN. Unlike bridges, routers make two different routing decisions for different packets with the same destination address, based on the dynamic state of the WAN. A router like 64 usually has no knowledge of the existence of a bridge in the connected LAN and sends all the data to the LAN as if the router 64 were directly connected to each ES in the LAN. And send. Typically, WANs like 42 have different addressing schemes and different packet structures than those used in LANs. All ESs in LAN40 wishing to receive packets from WAN42 must be assigned a different WAN address. In TCP / IP, WAN addresses are 32 bits long and typically have a period-separated decimal notation with values ranging from 0.0.0.0 to 255.255.255.255. Router 64 learns LAN and WAN addresses for all ESs in LAN40 and translates packets and addresses between LAN40 and WAN42. Figure 3 shows packets that can be forwarded to or from router 64 on LAN segment 73A. This packet is essentially an Ethernet packet and has an Ethernet header 202, 48-bit Ethernet address (00: 60: 8C: 19: AA) 204, and an Ethernet trailer 230. Within the Ethernet packet 200, the IP packet represented by the IP header 212 is contained, that is, encapsulated. The IP header 212 contains a 32-bit IP address 214 (199.35.126.34). Packet 200 contains a data payload 220 that holds the data that the user wants to receive and the control messages used to configure the network. 34) is included. Packet 200 contains a data payload 220 that holds the data that the user wants to receive and the control messages used to configure the network. 34) is included. Packet 200 contains a data payload 220 that holds the data that the user wants to receive and the control messages used to configure the network. It has a period-separated decimal notation with values from 0 to 255.255.255.255. Router 64 learns LAN and WAN addresses for all ESs in LAN40 and translates packets and addresses between LAN40 and WAN42. Figure 3 shows packets that can be forwarded to or from router 64 on LAN segment 73A. This packet is essentially an Ethernet packet with an Ethernet header 202,48-bit Ethernet address (00: 60: 8C: 19: AA) 204, and an Ethernet trailer 230. Within the Ethernet packet 200, the IP packet represented by the IP header 212 is contained, that is, encapsulated. The IP header 212 contains a 32-bit IP address 214 (199.35.126.34). Packet 200 contains a data payload 220 that holds the data that the user wants to receive and the control messages used to configure the network. It has a period-separated decimal notation with values from 0 to 255.255.255.255. Router 64 learns LAN and WAN addresses for all ESs in LAN40 and translates packets and addresses between LAN40 and WAN42. Figure 3 shows packets that can be forwarded to or from router 64 on LAN segment 73A. This packet is essentially an Ethernet packet with an Ethernet header 202,48-bit Ethernet address (00: 60: 8C: 19: AA) 204, and an Ethernet trailer 230. Within the Ethernet packet 200, the IP packet represented by the IP header 212 is contained, that is, encapsulated. The IP header 212 contains a 32-bit IP address 214 (199.35.126.34). Packet 200 contains a data payload 220 that holds the data that the user wants to receive and the control messages used to configure the network. 34) is included. Packet 200 contains a data payload 220 that holds the data that the user wants to receive and the control messages used to configure the network. 34) is included. Packet 200 contains a data payload 220 that holds the data that the user wants to receive and the control messages used to configure the network.<u style="single">WAN multicasting</u>WAN42 is enabled to route WAN Multicast Packets (WMP). The WAN multicast packets (WMP) are delivered to each router requesting their reception. When operating according to the TCP / IP suite, routers and ESs perform multitasking through a special protocol called the Internet Group Management Protocol (IGMP). In IGMP, the source wishing to send WMP is assigned a special WAN multicast destination address from the list of addresses reserved by IGMP for multicast. Within LAN40, WMP is translated by router 64 into a LAN packet with a LAN destination address, which is a LAN group address. IGMP is WAN Includes direct algorithmic mapping between IP multicast addresses and LAN group addresses. According to IGMP, a router like 64 periodically asks the ESs connected to it and asks them to return a report as to whether they want to receive the WMP stream. This question will be broadcast to the reserved Ethernet group address in LAN40. An ES wishing to receive a WMP stream responds to this IGMP question by returning an IGMP report to Router 64. The IGMP report is addressed to the LAN address that corresponds to the WMP address that the ES wants to receive. The IGMP report lists the WMP addresses that the ES wants to receive. ES sends a separate report for each WMP stream that it wants to receive. In technology in this area, ES is often referred to as joining a multicast group each time it indicates to a router that it wants to receive a particular WMP stream. The router sends a request to other routers in WAN42 to deliver a specific WMP stream according to the IGMP reports received from one or more ESs. The following three details about IGMP are important. First, the ES can leave the multicast group at any time (ie, stop receiving WMP to that multicast address) without informing the router that it no longer wants to receive WMP. ). The ES simply does not have to answer the next IGMP question sent by the router. (In newer versions of IGMP, ES can send packets telling routers that they no longer want to receive certain WPM streams, but it does not have to send such packets.) The second important detail of is that if there are two routers in a LAN like 40 that have connections to the same WAN, question packets from both routers. The IGMP protocol has a mechanism to prevent the transfer of data to the LAN. According to IGMP, when a router receives a question packet on one of its LAN ports, it looks up the WAN source address of that packet, and if that source address is lower than the router's own WAN address. If so, the router stops forwarding interrogation packets. Thus, in the end, only one router (the router with the lowest IP address) forwards the interrogation packet over a given LAN. An important third detail of IGMP is that the ES monitors those segments and reads all the IGMP reports that appear on those segments. According to IGMP, an ES attempts to send an IGMP report for a WMP address, but does not send that IGMP report if another ES has already requested that WMP address on that segment. The second ES simply receives the WMP that is forwarded to the first ES that made the request earlier. This means that: That is, under IGMP, is it the single ES on the LAN to which the router is connected that wants the router to receive a particular WMP stream, or is it more than one ES? It means that I don't know at all. Therefore, the router makes WMP a specific ES It cannot be directed to the LAN destination address and the WMP must be directed to one of the reserved LAN group addresses. As mentioned above, within LAN40, group address packets are delivered over the bridge to all segments of the LAN. Therefore, even if only ES72b of LAN40 requests a special WMP stream, the WMP stream is converted to a LAN group address and distributed to all ESs in LAN40. For heavy WMP streams such as video links, this results in an undesired huge amount of LAN traffic. One of the prior art solutions to this problem is to reconfigure the LAN40, replacing each of the bridges 60-63 with one that has more functionality than the router. Such pseudo-routers participate in all of the IGMP protocols and direct WMP packets only to the segments where they are desired. However, this is an expensive idea, which increases the cost of LAN hardware infrastructure and LAN management, and tends to slow down the entire LAN.<u style="single">Layer</u>The final background concept important for understanding the present invention is the stratified network protocol. Recent communication standards, such as the TCP / IP suite and the IEEE E802 standard, layer the tasks required for data communication. At different layers, data looks and is organized differently, followed by different protocols, and different physical devices handle data traffic. Figure 4 illustrates a stratified network standard with multiple layers. Multiple layers include a physical layer, a data link layer, a routing layer, a transport layer, and an application layer. These layers roughly correspond to the layers defined in the TCP / IP suite. (The 802 standard has layers of different organizational structures and uses different names.) At the physical layer, data is transferred from one transmitter to one or more racers in one segment, unformatted. Treated as a bit stream. For example, in 802, the physical layer handles encoding / decoding of physical transfer signals, generation / removal of preambles of transferred data used for synchronization (such as start and stop bits), and bit transfer / receive protocols. Different physical layer protocols and devices exist to transfer data as electrical, optical, or radio signals over wires, optical fibers, or other media. ES and IS hardware generally interact with the physical layer through an adapter that receives binary data from the IS or ES and converts that data into a signal that can be transferred over the medium. The adapter contains the circuits and connections needed for communication in the medium. Adapters for PCs are commonly implemented as standard bus cards that connect to a PC parallel bus, and include connectors for connecting to media to which network signals are transferred. In the data link layer (DLL) (sometimes called layer 2 or MAC layer), data is treated as a series of independent packets. Will be Each packet has fields that identify the destination address and packet length, priority, error, and check code. A type of device that aids in transfer over a network at the data link layer is a bridge. IEEE802 is primarily concerned with the data link layer and the physical layer. Ethernet and Token Ring are two common protocols that operate at the data link layer and the physical layer. At the routing layer (sometimes referred to as layer 3), data is treated as a series of independent routing packets. Routing packets contain the information needed for the correct delivery of packets over large WANs such as the Internet. This information is used at the routing layer to forward packets over the network to their destinations. A router is a device that helps transfer over a network at the routing layer. In the TCP / IP suite, protocols that handle forwarding at the routing layer include IP, IGMP, and ICMP. At the transport layer, data is seen as a connection between two hosts on the network. Transport layer protocols in the TCP / IP suite include TCP and UDP. The application layer contains programs that users interact with to use network features such as email, ftp, remote login, or http. What is important in stratified standards is the idea of stratification. The layered protocol suite specifies the standard interface between layers as follows: That is, logically, a device and a protocol operating in one layer can have many different protocols operating in a high layer or a low layer at the same time as long as the standard interface between layers continues. Specify in. Combining the concept of layers with the previous explanation, in LAN40 WAN forwarding is done at the routing layer, while LAN forwarding is done at the lower data link layer. At the routing layer, ES is a control Communicate roll packets to the router to which they are connected. However, at the data link layer, ES does not communicate control packets with the bridge, so ES cannot participate in the multicast protocol at the data link layer. What we can see from the above description is the ability of the LAN to properly receive and deliver WAN multicast packets to the end system that wants to receive them, but the unwanted terrible traffic that occurs on traditional LANs. Is to not experience the amount of. More details on LAN technology can be found in US Patent Application No. 08/506, entitled "Methods and Devices for Asynchronous PPP to Synchronous PPP Conversion". It can be found in simultaneous applications such as No. 533, applications of the same assignor. It is incorporated here by reference for all purposes. For the sake of clarity, specific examples, such as Ethernet and TCP / IP terms, refer to network devices and concepts. However, the devices and methods of the present invention are capable of operating with many types of network devices, including networks that are extremely different from the particular examples described in FIG. 1 and below. In particular, the present invention has applications within a set of WANs and LANs for which standards have been developed by Apple Computer Corporation and can be claimed for ownership, called Applelinks and SMRPs. Therefore, the present invention is intended to be unrestricted except within the appended claims. Abstract of the Invention According to the present invention, the improved LAN can receive WMP from the WAN via a router and distributes WMP only on the segment having at least one ES that wants to receive those WMPs. You can do it. According to the present invention, these are modified so that the layer 2 intermediate system of the LAN listens to the layer 3 routing control packets and causes layer 2 to filter decisions based on the information in the layer 3 packets. It is done by things. The present invention provides a mechanism by which a layer 2 intermediate system generates a layer 3 interim packet if a high level system does not generate a layer 3 interrogation packet in the LAN. The present invention is WAN It is a substantial improvement over many types of traditional LANs, where MPs flood each segment of the LAN. Under one embodiment of the invention, no modifications are required to the ES or WAN protocol or hardware. Alternatively, the present invention filters routing layer (layer 3) packets at the data link layer (layer 2) and does not require any modification of the routing layer protocol. In the present invention, the bridge selectively sends WMP based on the routing layer request from ES. The bridge according to the invention carefully monitors all routing layer multicast data and control packets, thereby facilitating decisions. The bridge uses this information to grow the filtered database, thereby making unwanted WMP filtering faster.
BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a diagram of a type of local area network in which the present invention can be effectively adopted. FIG. 2 is a diagram of one type of wide area network in which the present invention can be effectively adopted. FIG. 3 is a diagram of an IP packet encapsulated within an Ethernet packet. FIG. 4 is a diagram showing a stratified network protocol. FIG. 5 is a block circuit diagram of a bridge improved by the present invention. Detailed Description of Preferred Embodiments In the following detailed description, the previously described 802. The improved bridge function according to the present invention is described in terms of two protocol suites, 3 and TCP / IP. Those skilled in the art will appreciate that it can be applied to other protocol suites that employ the analog multicast protocol. FIG. 5 is a block diagram of the bridge 62 improved by the embodiment of the present invention. The bridge has circuits that can communicate with each segment 72a-e and five ports 80a-e that make up the connection. Packets received on either port are stored in the shared packet memory 82. The controller 84 reads the received packet and processes the packet based on the instruction specified by the driver 86. Controller 84 includes connections (not shown) to each of the other bridge components that transmit and receive control signals. As can be seen from the traditional bridge, controller 84 maintains a bridge filtering table (BFT) in a memory area away from the packet buffer. As can be seen from the prior art, the BFT88 contains an entry for the LAN address for each ES in which the packet is received. Each entry provides a means of specifying the LAN address where the packet was received and pointing to the port to which that address is connected. According to the default operating mode, the bridge 62 gradually learns about the ES to which it is connected by reading the LAN source address of the packet received on the port. When the bridge identifies the LAN address of a particular ES and stores the identifier of the port to which the ES is connected in BFT88, the packet addressed to that LAN address and received by the bridge 62 is only on the port to which the ES is connected. The bridge is operated. In this way, the bridge 62 gradually reduces unnecessary traffic on the network. According to the present invention, the bridge 62 can additionally filter IGMP multicast packets based on LAN group addresses, as follows: Power-up or cis When the system resets or ports do not have a port designated as a question port as shown below, the bridge 62 modified by the present invention behaves like a router and IGMP questions on each port AE at tuned intervals. Forward the packet. Initially, those ports are designated as non-questioning ports by bridge 62. The bridge forwards the question with a temporary WAN source address set to a value higher than the possible WAN source address of the actual IP router. This temporary WAN source address is assigned to the bridge according to the present invention. Standard traditional bridges do not have a WAN address because they cannot communicate at layer 3. In response to that question, the ES attached to the bridge trying to receive WMP forwards a report on that segment. The bridge 62 receives those reports. The reports include a destination address equal to the multicast address on which the ES intends to receive the packet, and include the source address of the ES that sent the report. Each time the bridge 62 hears a report for one of the ports, it stores the identifier for that port and its LAN group address in the BFT88 indexed according to the LAN group address, and puts a flag value in the appropriate position. It tells which port received the report packet (in the example in Figure 5, bridge 62 is the Ethernet group address 09:10: 7D: Place "1" in the column that specifies ports B and D that are going to receive WMP packets addressed to 00. ). When any next packet going to that LAN group is received on bridge 62, bridge 62 refers to the LAN group address of BFT88 and sends those packets only to the ports identified by that group. When bridge 62 receives a question packet on one of its ports, it tests the WAN source address of the question, and if the WAN source address of the received question packet is greater than the temporary WMP source address of bridge 62, the bridge 62 keeps sending his question packets periodically, marking the port that received the question as a non-question port. If the WAN source address of the received interrogation packet is less than the temporary WMP source address of bridge 62, the bridge 62 stops sending its interrogation packet and marks the interrogated port as the interrogation port. In this way, the bridge according to the invention "lose" to the actual IP router connected to the LAN segment of the bridge. Alternatively, the bridge 62 may be tested to prioritize the LAN source address. According to other embodiments of the invention, there are different types of LAN intermediate systems according to the invention with different capabilities. For example, in one LAN, some ISs according to the invention are bridges that are fully adapted to IEEE802.1d, thus fully implementing the bridge spanning tree algorithm, while others according to the invention are spanning. Some do not fully implement the tree algorithm. In this case, it is desirable that the IS that is fully adapted to IEEE802.1d is selected as a temporary router on the IS that is not fully adapted to 802.1d in the LAN. Therefore, according to one embodiment of the invention, two temporary WAN source addresses for the LAN intermediate system are reserved for use when generating the interrogation packet. The higher of the two temporary addresses is non-802. Assign to 1d. In this case, when the IS receives the question packet on the port, it tests the WAN source address of the question. When the WAN source address that received the interrogation packet is greater than the IS's temporary WAN source address, the IS continues to send its interrogation packet periodically, marking the port that received the interrogation packet as a non-inquiry port. When the WAN source address of the interrogation packet is smaller than the IS's temporary WAN source address, the IS stops sending its own interrogation packet and marks the port that received the interrogation packet as the interrogation port. However, if the WAN source address of the received question packet is the same as the IS temporary WAN source address, the IS will compare the LAN address to the LAN source address of the received question packet and if the received question packet If the LAN source address is smaller than the IS LAN source address, specify it as the question port. When a port is designated as an interrogation port, according to embodiments of the present invention, the bridge 62 retains that designation even if the bridge 62 does not find an IGMP interrogation packet on that port within a predetermined timeout. After that timeout elapses, the port reverts to the non-questioned port designation. According to yet another embodiment of the invention, the bridge can handle the specificity of IGMP with respect to its timeout. IGMP does not specify how often the router sends questions, and there is no information in the IGMP question packet to specify the interval. Therefore, the proper timeout for a given question port is not always clear. According to this embodiment, the bridge monitors the frequency with which the interrogation packet is received on the interrogation port and sets a timeout at a time longer than the specific frequency. If the interrogation port does not receive an interrogation packet within the timeout period, the bridge of this embodiment designates that port as a non-inquiry port. If all ports of the bridge according to the invention are designated as non-questioning ports, the bridge will generate and forward interrogation packets. Bridge 62 is IGM on non-questioned port Monitor the P report and use the information stored there to build the BFT. According to the present invention, the bridge 62 does not send any IGMP report packets to the non-questioning port. Bridge 62 sends a report packet out of the question port. The reason is to prevent other ESs from suppressing IGMP report packets on ESs on other ports because they see other reports on the same LAN with the same WMP request. As explained, in the IGMP protocol, to prevent all ESs from sending their own copy of the report, ES monitors all IGMP report packets on its segment and the WMP of interest. If it finds a pass for the report about, it does not request that WMP. However, bridge 62 does not need to receive another report packet in at least one of the segments to know which segment has to bridge WMP. One advantage of the present invention is that it can be implemented in a LAN such as 40, does not require new software for ES, and does not require a new protocol between ES and router or between ES and bridge. In one embodiment, the present invention can be implemented by transforming some of the bridges in the LAN without the need to transform the LAN or WAN. The present invention has been described in particular embodiments. Other embodiments will be apparent to those skilled in the art. In particular, the steps of the method are grouped and labeled to be part of many sub-methods for clarity of disclosure, but these steps differ without changing the main behavior of the invention. Can be divided into groups. The present invention is not subject to any limitation other than the claims. This is to prevent suppressing the IGMP report packets of ES on other ports because we are looking at other reports on N. As explained, in the IGMP protocol, to prevent all ESs from sending their own copy of the report, ES monitors all IGMP report packets on its segment and the WMP of interest. If it finds a pass for the report about, it does not request that WMP. However, bridge 62 does not need to receive another report packet in at least one of the segments to know which segment has to bridge WMP. One advantage of the present invention is that it can be implemented in a LAN such as 40, does not require new software for ES, and does not require a new protocol between ES and router or between ES and bridge. In one embodiment, the present invention can be implemented by transforming some of the bridges in the LAN without the need to transform the LAN or WAN. The present invention has been described in particular embodiments. Other embodiments will be apparent to those skilled in the art. In particular, the steps of the method have been grouped and labeled to be part of many sub-methods for clarity of disclosure, but these steps differ without changing the main behavior of the invention. Can be divided into groups. The present invention is not subject to any limitation other than the claims. This is to prevent suppressing the IGMP report packets of ES on other ports because we are looking at other reports on N. As explained, in the IGMP protocol, to prevent all ESs from sending their own copy of the report, ES monitors all IGMP report packets on its segment and the WMP of interest. If it finds a pass for the report about, it does not request that WMP. However, bridge 62 does not need to receive another report packet in at least one of the segments to know which segment has to bridge WMP. One advantage of the present invention is that it can be implemented in a LAN such as 40, does not require new software for ES, and does not require a new protocol between ES and router or between ES and bridge. In one embodiment, the present invention can be implemented by transforming some of the bridges in the LAN without the need to transform the LAN or WAN. The present invention has been described in particular embodiments. Other embodiments will be apparent to those skilled in the art. In particular, the steps of the method are grouped and labeled to be part of many sub-methods for clarity of disclosure, but these steps differ without changing the main behavior of the invention. Can be divided into groups. The present invention is not subject to any limitation other than the claims. The advantage is that it can be implemented in a LAN like 40, does not require new software for ES, and does not require a new protocol between ES and router or between ES and bridge. In one embodiment, the present invention can be implemented by transforming some of the bridges in the LAN without the need to transform the LAN or WAN. The present invention has been described in particular embodiments. Other embodiments will be apparent to those skilled in the art. In particular, the steps of the method are grouped and labeled to be part of many sub-methods for clarity of disclosure, but these steps differ without changing the main behavior of the invention. Can be divided into groups. The present invention is not subject to any limitation other than the claims. The advantage is that it can be implemented in a LAN like 40, does not require new software for ES, and does not require a new protocol between ES and router or between ES and bridge. In one embodiment, the present invention can be implemented by transforming some of the bridges in the LAN without the need to transform the LAN or WAN. The present invention has been described in particular embodiments. Other embodiments will be apparent to those skilled in the art. In particular, the steps of the method have been grouped and labeled to be part of many sub-methods for clarity of disclosure, but these steps differ without changing the main behavior of the invention. Can be divided into groups. The present invention is not subject to any limitation other than the claims.
Every citation, both ways
| Document | Relation | Office |
|---|---|---|
| JP08274805A | Cites | Japan |
| US5530703A | Cites | United States of America |
13 members in 7 offices
Priority claims9
| Document | Office | Kind | Date |
|---|---|---|---|
| 08542157 | United States of America | – | |
| 54215795 | United States of America | A | |
| 54215795 | United States of America | A | |
| 9616383 | United States of America | W | |
| 9616383 | United States of America | W | |
| 1995542157 | – | – | – |
| 1996016383 | – | – | – |
| US19950542157 | – | – | – |
| WO1996US16383 | – | – | – |
Members13
| Document | Office | Kind | |
|---|---|---|---|
| WO9714239A1 | World Intellectual Property Organization (WIPO) | A1 | |
| AU7443296A | Australia | A | |
| EP0855115A1 | European Patent Office (EPO) | A1 | |
| US5818838A | United States of America | A | |
| US5999530A | United States of America | A | |
| US6169741B1 | United States of America | B1 | |
| JP2001517379A | Japan | A | |
| IL124067A | Israel | A | |
| EP0855115A4 | European Patent Office (EPO) | A4 | |
| EP0855115B1 | European Patent Office (EPO) | B1 | |
| DE69634916D1 | Germany | D1 | |
| JP3737517B2This record | Japan | B2 | |
| DE69634916T2 | Germany | T2 |
16 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Cancellation because of completion of termEXPY | EXPY | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 |
Numbers
- Publication
- 3737517
- Publication, DOCDB
- 3737517
- Publication, EPODOC
- JP3737517B
- Application
- 51525897
- Application, DOCDB
- 51525897
- Application, EPODOC
- JP19970515258
Titles2
- Japanese
- マルチキャスト・パケットのLAN上における、透過形の中間システムを基礎とするフィルタリングの方法および装置
- English
- Filtering methods and devices based on transparent intermediate systems on a LAN for multicast packets
Classification
- CPC, 7
- H04L12/1877
- H04L12/1836
- H04L12/185
- H04L12/1886
- H04L12/4604
- H04L12/4625
- Y10S370/911
- IPC, 4
- H04L12 66
- H04L12 56
- H04L12 18
- H04L12 46