Method and nodes for performing bridging of data traffic over an access domain
Abstract
This record has no abstract on file.
Term
Term ended
Expired 14 February 2026, 0.6 years ago.
- Priority
- Filed
- Granted
- Expired
- Today
20 claims: 4 independent, 16 dependent
- 1アクセスドメイン上でのデータトラフィックのブリッジング処理に関する方法であり、前記方法は、 第1アクセスノード上で第1ユーザドメインからデータトラフィックを受信し、このとき前記データトラフィックは第2ユーザドメインを宛先としているステップと、 前記第1アクセスノード内で、受信された前記データトラフィックに対応するサービスバインディングを識別するステップと、 識別された前記サービスバインディングに従って、アクセスエッジノードにアドレス指定された、ユニキャストメッセージ内の前記データトラフィックをトンネリングするステップと、 トンネリングされた前記データトラフィックを前記アクセスエッジノードに転送するステップと、 トンネリングされた前記データトラフィックを前記アクセスエッジノードで受信するステップと、 前記アクセスエッジノードで、受信されたトンネリングされた前記データトラフィックに対応する前記サービスバインディングを識別するステップと、 識別された前記サービスバインディングに従い、前記アクセスエッジノードで受信されたトンネリングされた前記データトラフィックを第2アクセスノードにリダイレクトするステップと、 リダイレクトされた、トンネリングされた前記データトラフィックを前記第2アクセスノードで受信するステップと、 デトンネリングされた前記データトラフィックを、前記第2アクセスノードから前記第2ユーザドメインへ転送するステップとから構成されていることを特徴とする、アクセスドメイン上でのデータトラフィックのブリッジング処理に関する方法。
- 2受信された前記データトラフィックが別のユニキャストメッセージに含まれていることを特徴とする、請求項1に記載の方法。
- 3前記サービスバインディングが、前記アクセスドメイン上で、アクセスノードと前記アクセスエッジノードとの間のデータトラフィックを管理するという方法で、第1ユーザドメインおよび第2ユーザドメインに接続を提供する前記アクセスノードと前記アクセスエッジノードをコミットすることによって、前記第1ユーザドメインと前記第2ユーザドメインとの間のデータトラフィックを規定することを特徴とする、請求項2に記載の方法。
- 4前記第1アクセスノード上の前記サービスバインディングが、ユーザドメイン入出力ユニットにおける入力ポート識別と、第1仮想アクセスエッジノードMACアドレスを含み、 前記第2アクセスノード上の前記サービスバインディングが、ユーザドメイン入出力ユニットにおける出力ポート識別と、第2仮想アクセスエッジノードMACアドレスを含み、 前記アクセスエッジノードにおける前記サービスバインディングが、第1アクセスノードMACアドレス、前記第1仮想アクセスエッジノードMACアドレス、前記第2仮想アクセスエッジノードMACアドレス、前記アクセスエッジノードにおける入力ポート識別、および前記アクセスエッジノードにおける出力ポート識別を含むことを特徴とする、請求項3に記載の方法。
- 5識別された前記サービスバインディングに従って、前記アクセスエッジノードにアドレス指定された、前記ユニキャストメッセージ内の前記データトラフィックをトンネリングするステップが、 前記ユニキャストメッセージのユーザデータ部分に、前記データトラフィックを書き込むステップと、 前記ユニキャストメッセージの目的アドレスに、前記アクセスエッジノードのMACアドレスを割り当てるステップと 前記ユニキャストメッセージのソースアドレスに、前記第1アクセスノードのMACアドレスを割り当てるステップと 前記ユニキャストメッセージの仮想ローカルエリアネットワークタグに前記サービスエージェント識別子を割り当てるステップとから構成されることを特徴とする、請求項4に記載の方法。
- 6識別された前記サービスバインディングに従って、前記アクセスエッジノードにおいて、受信されたトンネリングされた前記データトラフィックを第2アクセスノードにリダイレクトするステップが、 前記第2アクセスノードのMACアドレスと対応するように、前記目的アドレスを変更するステップと、 前記ソースアドレスを、前記アクセスエッジノードの前記MACアドレスに対応するように変更するステップとから構成されることを特徴とする、請求項5に記載の方法。
- 7識別された前記サービスバインディングに従って、前記アクセスエッジノードにおいて、受信されたトンネリングされた前記データトラフィックを第2アクセスノードにリダイレクトするステップが、さらに、 受信されたトンネリングされた前記データトラフィックの仮想ローカルエリアネットワークタグフィールドを、前記第2アクセスノードの入力ポートに対応するように変更するステップから構成されることを特徴とする、請求項6に記載の方法。
- 8トンネリングされた前記データトラフィックを転送するステップが、前記アクセスドメイン上で、アクセスドメイン上のスイッチを通して運ばれることを特徴とする、請求項1に記載の方法。
- 9請求項5に記載の方法であり、さらに、前記ユニキャストメッセージのイーサタイプフィールドに、前記ユニキャストメッセージが、トンネリングされたデータトラフィックに関与することを示す値を割り当てるステップから構成されることを特徴とする、請求項5に記載の方法。
- 10アクセスドメイン上で、データトラフィックをブリッジングするアクセスエッジノードであり、前記アクセスエッジノードが、アクセスドメイン入出力ユニットとサービスバインディングホスティングユニットと、制御ユニットとから構成され、 前記アクセスドメイン入出力ユニットは、前記アクセスドメイン上で、データトラフィックを送受信し、 前記サービスバインディングホスティングユニットは、前記アクセスエッジノードに関するサービスバインディングについての情報を格納し、 前記制御ユニットは、前記アクセスドメイン入出力ユニットで受信された前記データトラフィックが、第1ユーザドメインから第2ユーザドメインへのデータトラフィックをブリッジングするユニキャストメッセージであるかどうかを決定し、前記制御ユニットは、前記サービスバインディングホスティングユニットを使用して、前記ユニキャストメッセージに対応するサービスバインディングを識別し、前記制御ユニットは、識別された前記サービスバインディングに従って、前記ユニキャストメッセージの目的アドレスを第二ユーザドメインに接続を提供するノードのアドレスに対応するように変更し、前記アクセスドメイン上に送信するために、前記アクセスドメイン入出力ユニットに、前記修正されたユニキャストメッセージを引き渡すことを特徴とする、アクセスドメイン上で、データトラフィックをブリッジングするアクセスエッジノード。
- 11それぞれの前記サービスバインディングが、前記アクセスドメイン上で、アクセスノードと前記アクセスエッジノードとの間のデータトラフィックを管理するという方法で、第1ユーザドメインおよび第2ユーザドメインに接続を提供する前記アクセスノードと前記アクセスエッジノードをコミットすることによって、前記第1ユーザドメインと前記第2ユーザドメインとの間のデータトラフィックを規定することを特徴とする、請求項10に記載のアクセスエッジノード。
- 12前記サービスバインディングホスティングユニットが、第1アクセスノードMACアドレス、前記第1仮想アクセスエッジノードMACアドレス、前記第2仮想アクセスエッジノードMACアドレス、前記アクセスエッジノードにおける入力ポート識別、および前記アクセスエッジノードにおける出力ポート識別の情報を含むことを特徴とする、請求項11に記載のアクセスエッジノード。
- 13前記制御ユニットが、さらに、前記ユニキャストメッセージのソースアドレスを、前記アクセスエッジノードのMACアドレスに対応するように変更することを特徴とする、請求項10に記載のアクセスエッジノード。
- 14前記制御ユニットが、さらに、前記データトラフィックの仮想ローカルエリアネットワークタグフィールドを、前記第2ユーザドメインに接続を提供するアクセスノードの入力ポートに対応するように変更することを特徴とする、請求項12に記載のアクセスエッジノード。
- 15ユニキャストメッセージのイーサタイプフィールドの値により、前記アクセスドメイン入出力ユニットで受信された前記データトラフィックが、第1ユーザドメインから第2ユーザドメインへのデータトラフィックをブリッジングする前記ユニキャストメッセージであるであるかどうかを、前記制御ユニットが決定することを特徴とする、請求項10に記載のアクセスエッジノード。
- 16アクセスドメイン上で、データトラフィックをブリッジングするアクセスノードであり、前記アクセスノードが、ユーザドメイン入力ユニット、サービスバインディングユニット、ブリッジングユニット、制御ユニット、アクセスドメイン出力ユニットから構成され、 前記ユーザドメイン入力ユニットは、第1ユーザドメインから第2ユーザドメイン宛のデータトラフィックを受信し、 前記サービスバインディングユニットは、サービスバインディング関連情報を格納し、それぞれのサービスバインディングは、前記アクセスドメイン上で、前記アクセスノードとアクセスエッジノードとの間のデータトラフィックを管理するという方法で、前記アクセスノードと前記アクセスエッジノードとをコミットすることによって、ユーザドメインと前記アクセスエッジノードとの間のデータトラフィックを規定し、 前記ブリッジングユニットは、前記アクセスエッジノードにアドレス指定されたユニキャストメッセージ内の受信されたデータトラフィックを、前記データトラフィックに対応するサービスバインディングに従ってトンネリングし、 前記制御ユニットは、前記受信されたデータトラフィックに対応する1つの前記サービスバインディングを識別し、前記制御ユニットは、前記受信されたデータトラフィックを、対応する前記サービスバインディングの指示によりトンネリングする前記ブリッジングユニットに転送し、 アクセスドメイン出力ユニットは、前記ブリッジングユニットからトンネリングされた前記データトラフィックを受け取り、トンネリングされた前記データトラフィックを、前記アクセスドメイン上で転送することを特徴とする、アクセスドメイン上で、データトラフィックをブリッジングするアクセスノード。
- 17前記サービスバインディング関連情報が、それぞれのサービスバインディングごとに、ユーザドメイン入出力ユニットにおける入力ポート識別、および第1仮想アクセスエッジノードMACアドレスを含むことを特徴とする、請求項16に記載のアクセスノード。
- 18前記アクセスドメイン出力ユニットがアクセスドメイン入出力ユニットであり、前記サービスバインディングが前記アクセスエッジノードで作成され、前記アクセスノードが、前記アクセスドメイン入出力ユニットを通して、前記サービスバインディングの作成の情報を伝達されることを特徴とする、請求項16に記載のアクセスノード。
- 19前記ブリッジングユニットが、 前記ユニキャストメッセージのユーザ部分に前記データトラフィックを書き込み、 前記ユニキャストメッセージに、前記アクセスエッジノードのMACアドレスに対応する目的アドレスを割り当て、 前記ユニキャストメッセージに前記アクセスノードMACアドレスに対応するソースアドレスを割り当て、 前記ユニキャストメッセージの仮想ローカルエリアネットワークタグフィールドに、前記アクセスドメイン出力ユニットの前記出力ポートに対応する値を割り当てることによって、前記データトラフィックをトンネリングすることを特徴とする、請求項17に記載のアクセスノード。
- 20前記ユーザドメイン入力ユニットが、ユーザドメイン入出力ユニットであり、前記ユーザドメイン入出力ユニットは、前記第1ユーザドメインからの/前記ユーザドメインへのデータトラフィックを送受信し、 前記アクセスドメイン出力ユニットが、アクセスドメイン入出力ユニットであり、前記アクセスドメイン入出力ユニットは、前記アクセスドメインからトンネリングされた前記データトラフィックを受信し、前記トンネリングされたデータトラフィックを前記制御ユニットへ転送し、 前記制御ユニットが、さらに、前記アクセスドメイン入出力ユニットで受信されたデータトラフィックがトンネリングされたデータトラフィックであることを決定し、受信されたトンネリングされたデータトラフィックに対応する1つの前記サービスバインディングを識別し、対応する前記サービスバインディングの指示により、トンネリングされた前記データトラフィックを前記ブリッジングユニットに転送し、 前記ブリッジングユニットが、さらに、識別された前記サービスバインディングに従って、前記アクセスドメイン入出力ユニットから受信されたトンネリングされたデータトラフィックをデトンネリングし、デトンネリングされた前記データトラフィックを、前記ユーザドメイン入出力ユニットに転送することを特徴とする、請求項15に記載のアクセスノード。
Independent claims20
41 paragraphs, as filed
Priority statement under 35 USCS119 (e) and 37 CFRS 1.78. The patent application was filed on February 14, 2005 in the names of Sylvain Monette, Mathieu Giguere, Marthin Julien and Benoit Tremblay. Application No. 60 / 651,971 "Poly project" and the names of Sylvain Monette, Mathieu Giguere, Marthin Julien and Benoit Tremblay. Claims priority under US Provisional Patent Application prior to Application No. 60 / 674,307, "Access node-edge node complex protocol (AEP)" filed April 25, 2005. It is a thing.
The present invention relates to a method of bridging data traffic on an access domain and a node.
In recent years, there has been an explosive increase in Internet Protocol (IP) networks. Initially, it was developed to allow universities and researchers to communicate and collaborate on research projects, but it has grown into a network offered at the huge market level. Today, ordinary households connect to IP networks to use the Worldwide Web, play interactive games, carry voice over IP, download documents and software, and conduct e-commerce. It's becoming normal to do.
Hereinafter, FIG. 1 will be described. FIG. 1 is an explanatory diagram showing a conventional technical example of the IP network 100. Typically, an IP network consists of an access domain 115, a network service provider domain 140, and an application service provider domain 150. The access domain 115 includes an access node (AN) 120 and an access network 130 such as an IP network. The access node 120 is a network provider that provides the user domain 110 with a connection to the IP network 130. The user domain 110 includes, for example, a user device (UD) (computer, mobile phone, personal digital assistant (PDA), etc.), a local area network (LAN), and a wireless LAN (W-LAN). .. The user domain communicates with the access node using various possible technologies. These technologies include dial-up connection over telephone lines and ADSL (Asymmetric Distribution Subscriber). There are Line) connections, cable modem connections over TV cable networks, and wireless communication. Access network 130 consists of a group of independent routers. The role of the router is to route incoming data traffic based on the destination address embedded in the data traffic. The network service provider domain 140 is suitable for voice transmission services on IP, for example, while the application service provider domain 150 is suitable for electronic banking and electronic commerce.
Figure 1 depicts three user domains, two access nodes, two service provider domains, and two application service domains, but typically an IP network 100 has thousands of user domains and dozens. Includes access nodes and hundreds of service provider domains and application service provider domains. For access network 130, it is normal to encounter a network that contains hundreds of routers. Thus, Figure 1 depicts the IP network 100, which is extremely simplified for clarity.
Early IP network principles are based on switches and routers that process incoming data traffic with as few operations as possible before routing it to its final destination. To that end, different types of messages: unicast messages, multicast messages, and broadcast messages are available. For each of these three message types, an address width is assigned for each type of message. Unicast messages are used to exchange messages between one sender and one recipient. Multicast messages allow a single sender to reach multiple recipients. For broadcast messages, broadcast messages are used to deliver messages to all switches in a segment of an IP network.
In particular, unicast messages are used to make data communication between the user domain 110 and the network service provider domain 140 and / or the application service provider domain 150. Unicast messages can also be used for data communication between user domains 110. When a unicast message is used on the access network 130, the switch on the access network 130 (not shown for clarity) forwards the unicast message to the destination in the corresponding packet. Need to be switched. In a wide range of networks, such as IP networks, the switch must maintain a large table to allow proper switching of packets. In addition, the transfer of unicast messages from source to destination requires the involvement of many switches, thus producing a lot of data traffic for a single unicast message on access network 130. The result is.
Currently, there is no known solution to the problem that leads to an increase in the number of user devices and the number of service providers that provide services on IP networks. In addition, a long-term solution has not yet been identified to enable a substantive solution to the increasing data traffic of a wide IP network servicing thousands of user domains.
<p> Therefore, to overcome the shortcomings and shortcomings of existing solutions, bridge data traffic on the access domain, which effectively reduces data traffic and loads the network. The benefits of having nodes and methods that effectively enable the reduction of The present invention provides the methods and nodes described above.</p>
<p> The present invention makes it possible for thousands of user domains to efficiently send and receive data traffic on an access domain by using service bindings. To that end, the method of the invention bridges data traffic on the access domain. In particular, for data traffic sent from the first user domain and received on the first access node, the corresponding service binding is identified. The received data traffic is then tunneled within the unicast addressed to the access edge node according to the identified service binding. The tunneled data traffic is then forwarded to the access edge node. When tunneled data traffic is received at the access edge node, the service binding corresponding to the received tunneled data traffic is identified. The tunneled data traffic is then redirected to the second access node according to the identified service binding. Then, when the redirected tunneled data traffic is received at the second access node, the tunneled data traffic is detunneled and forwarded to the second user domain.</p><p> According to another aspect of the invention, it relates to an access edge node adapted to carry out the method of the invention. More precisely, an access edge node includes an access domain I / O unit that sends and receives data traffic on the access domain, and a service binding hosting unit that stores information about service bindings about the access edge node. The access edge node also includes a control unit. The control unit has a plurality of roles, and the roles are as follows. i) Access domain Determine if the data traffic received by the ingress unit is a unicast message bridging data traffic from the first user domain to the second user domain. ii Use the service binding hosting unit to identify the service binding that corresponds to the unicast. iii) Change the target address of the unicast message to correspond to the address of the node providing the connection to the second user domain according to the identified service binding iv) Modified to send on the access domain Pass the unicast message to the access domain I / O unit.</p><p> According to another aspect of the invention, the invention is directed to an access node that bridges data traffic over an access domain. The access node includes a user domain input unit, a service binding unit, a bridging unit, a control unit, and an access domain output unit. In particular, the user domain input unit receives data traffic from the first user domain, and the received data traffic is destined for the second user domain. The service binding unit stores service binding related information. Each service binding manages data traffic between the access node and the access edge node, and by committing the access node and the access edge node, one of multiple user domains and the access edge node. Specifies data traffic to and from. The bridging unit tunnels the received data traffic in the unicast message addressed to the access edge node according to the service binding corresponding to the received data traffic. The control unit identifies the corresponding service binding and forwards the received data traffic to the tunneling bridging unit at the direction of the corresponding service binding. With respect to the access domain output unit, the access domain output unit receives tunneled data traffic from the bridging unit and forwards the tunneled data traffic on the access domain.</p>
For a more detailed understanding of the objects and advantages of the present invention, the description will be given in conjunction with the accompanying drawings described below. Innovative disclosures of the present invention are described by individually referring to examples of various embodiments. However, it should be understood that this type of embodiment provides only a few examples of the numerous advantageous uses of the innovative disclosures of the present invention. In general, what is described in the specification of the present application does not necessarily limit any of the various required items of the present invention. Moreover, some statements apply to the features of some inventions, but not to the features of other inventions. In the figure, the same or similar elements are indicated by the same code throughout several charts.
The present invention relates to methods and nodes for bridging data traffic on an access domain. Although technically known, an access domain consists of multiple switches, which are responsible for switching data traffic to their destination. Data traffic carried on the access domain originates from the user domain and the service provider domain. As interest in applications such as the Worldwide Web grows, the number of service provider and user domains that forward and receive data traffic carried over access domains is exploding. To allow you to switch data traffic appropriately, each switch has a MAC address learning feature (Media Access Control). Some knowledge needs to be gained by performing a process known as learning). With the MAC address learning feature, each switch learns on which port the MAC address is reachable and sends data traffic to the correct port instead of sending data traffic to all ports. However, as the number of service provider domains and user domains that exchange data traffic on access domains has exploded, so have the tables in the switch. Accounting for traffic on the network, as is the case with the present invention. There is another problem with the execution of function). Thus, it is important to find a way to reduce the number of MAC addresses learned by the switch. Providing a concise way to stream data traffic between two user domains has also become essential. Therefore, the present invention introduces an access edge node within the access domain. Further, the present invention uses a service binding between an access node and an access edge node in order to carry data traffic between the access node and the access edge node on the access domain. Finally, the present invention uses access edge nodes and service bindings between access nodes that provide connectivity and access edge nodes to bridge data traffic between two user domains.
In order to understand the present invention and the mechanism of the present invention, FIG. 2 will be described. FIG. 2 is a schematic view illustrating the network 200 in which the present invention is incorporated. The schematic of Network 200 has been simplified for clarity purposes. The various elements depicted are grouped by similar functions and do not represent network entities in a positional diagram. However, each group with similar functions typically corresponds to a physical network entity with a particular function, located scattered across the network 200. The schematic of network 200 includes user domain 110, access domain 115, network service provider 140, and application server 150. The access domain 115 includes an access node 120, an access network 130, an access edge node 160, and a regional network 135. A comprehensive description and examples of each element are provided in the following paragraphs with reference to Figure 2.
The network 200 corresponds to one or more data networks that communicate with each other. In this way, the network 200 can be operated by one or more operators. Data networks are typically supported by a large number of operable entities and / or a large number of operational organizations, so it is not possible to clarify how these entities and organizations make communication successful. Required. For this reason, data networks are typically open system interconnect models (OSI model: Open System Interconnection). It will be explained in detail using model). The OSI model clarifies the network framework for executing protocols within seven layers. Each of these seven layers is in the order shown below. 1) Physical layer; 2) Data link layer; 3) Network layer; 4) Transport layer; 5) Session layer; 6) Presentation layer; 7) Application layer. Each layer corresponds to possible aspects and undertaken behavior when transferring data over a data network. Using the OSI model to represent the network 200 of the invention, some of the various protocols used and / or supported by the network 200 of the invention are layered as follows: be able to. Layer 2: Ethernet, Asynchronous Transfer Mode (ATM) Layer 3: Internet Protocol (IP) version 4, Internet Protocol (IP) version 6 Layers 4 and 5: Transmission Control Protocol (TCP), User Datagram Protocol (UDP) Layers 6 and 7: Various presentation and application protocols that currently exist or will be used in the future
The above list of protocols is provided for illustrative purposes only and does not limit the protocols supported by the present invention. For the sake of brevity, Ethernet and IP have been described above, but such protocols are only used as examples. The expressions Ethernet and IP are interpreted as the Layer 2 protocol and the Layer 3 protocol, respectively. As used herein, the term "domain" refers to one or more network components with similar functional characteristics.
Next, the access domain 115 will be described. Access domain 115 can be summarized as a means of providing end-to-end connectivity between user domain 110, network service provider 140, and application service provider 150. Access domains include access node 120, access network 130, regional network 135, and access edge node 160. Thus, the access domain 115 is not itself an entity, but rather a collection of components. This set of components, whether direct or indirect, behaves as a domain to provide a connection when connected to each other. Therefore, this name is called "access domain". The representation of the current access domain 115, which includes only one access node 120, one access network 130, one access edge node 160, and one regional network 135, means that such an entity is single within the access domain. It is also clear that only one of those entities is represented, not for the purpose of clarification. The following paragraphs provide a more detailed description of the various components of the access domain.
Access node 120 includes an access gateway (not shown) and represents the first component of access domain 115. Typically, the access node 120 asks an access provider that allows connection to the access network 130 of the user domain 110, for example, whether it is fixed or pay-as-you-go. Such connections are possible using a variety of media and technologies. Media that can be used include cables, landlines, and mobile phones. Available technologies include Integrated Services Digital Network (ISDN), Asymmetric Digital Subscriber Line (ADSL), and WiMax (Worldwide Interoperability for Microwave). Access) is an example. However, it should be noted that the present invention is not limited to those media or technologies. Similarly, although only three access nodes are depicted in the figure, it should also be noted that network 200 potentially contains hundreds or thousands of access nodes.
The access domain also includes the access network 130 and the regional network 135, which will be discussed together below. The primary function of the access network 130 and the regional network 135 is to provide end-to-end, independent forwarding between the access node 120, the network service provider 140, and the application service provider 150. The access network 130 and the regional network 135 are networks that play the following roles. Its role is to aggregate, switch, and route downstream and upstream data traffic. The access network 130 can preferably use Ethernet, or other similar protocol, corresponding to Layer 2 of the OSI model. However, it is not limited to the protocol corresponding to layer 2 of the OSI model. Access network 130 can favorably support IPv4 and / or IPv6. Regional network 135 preferably supports Ethernet and / or IP and MPLS, and supports other possible Layer 3 protocols. In addition, the access network 130 and the regional network 135 can be operated and / or managed by one or more different operators. The access network 130 and the regional network 135 are composed of a plurality of switches (not shown) through which the switching of data traffic is handled.
Through a strong coupling of their traffic engineering capabilities through the access edge node 160, the access network 130 and the regional network 135 can provide end-to-end quality of service (QoS). The role of access edge node 160 is to create, manage, and host service agents 170 and service bindings (not shown in Figure 2 but depicted in Figure 3). Each service agent 170 supports a single service provider domain (140 or 150) as well as access network bridging capabilities. Each service agent 170 is a virtual local area network (VLAN) on the access network 130. Manage and control Network). The expression "service binding" refers to the binding between the user domain 110 and one service agent 170 on the access edge node 160. The concept of access edge node 160, service agent 170, and service binding is described in more detail in the descriptions described in FIGS. 3, 4a, and 4b.
Next, the user domain 110 will be described. The user domain relates to an access node 120 that provides an entry point to the access domain 115. In the present invention, the expression "user domain" refers to an independent computer, a local network of computers physically or wirelessly connected through a router, a mobile phone, or a personal digital assistant (PDA). Refers to Assistant) or any other device that can communicate data over a network, such as Network 200. In addition, the expression "user domain" is intended to include multiple data traffic sessions that occur at the same time. Multiple simultaneous data traffic sessions are performed by multiple devices through a single user port. For example, users can simultaneously access different applications and network services such as Internet connectivity and video conferencing and TV programming. The user can then use one or more devices to access simultaneously through the user domain provided in the VLAN or through one single user port, referred to here as the "user domain". ..
Network service provider 140 represents an entity that uses access domain 115, for example, to provide IP address assignments and connections to other networks, and to provide and deliver specific applications. For data traffic with user domain 110, the network service provider 140 typically owns an IP address, using, for example, identification based on RADIUS (Remote Authentication Dial-In User Service), and IP address in user domain 110. To assign. In addition, if requested and / or required, Network Service Provider 140 provides user-level authentication and authorization.
The application service provider 150 uses the access domain 115 to deliver and deliver the application to the end users of the user domain 110. Examples of such applications include games, video on demand, video conferencing, and many other possible applications. However, it is the access domain 115 that assigns the IP address to the user domain 110 on behalf of the application service provider. If requested, application service provider 150 can also authenticate at the user level and, if necessary, authorize. In the above description, the terms "service provider" and "service provider domain" are used instead to represent both the network service provider 140 and the application service provider 150 at the same time. The expression "service provider" may also refer to one of network service provider 140 or application service provider 150.
As mentioned earlier, service bindings relate to forwarding relationships. In the description of the present invention, the transfer relationship is built between two user domains and directly affects the access node 120 and the access edge node 160 that provide the connection. Conceptually, creating a service binding corresponds to adding the identified user domain to the VLAN corresponding to the service agent on the access domain. In this way, each service binding may represent a tradable business entity. A tradable business entity guarantees delivery of the corresponding service. Service bindings are created, managed, hosted, and exist in conjunction with Service Agent 170 within the Access Edge node. Service bindings are also hosted within the access node where they regulate data traffic.
Service agents and service bindings are created, managed, and hosted within the Access Edge node. Therefore, FIGS. 2 and 3 will be described at the same time. FIG. 3 is a schematic diagram of an access edge node according to the disclosure of the present invention. Access edge nodes are made up of multiple elements to allow them to play the role of creating, managing, and hosting service agents and service bindings. For locational reasons within the access domain 115, the access edge node includes an access domain I / O unit 310 to communicate with the access node 120 on the access network 130. The access edge node 160 also includes a network / application service provider domain I / O unit 320 to communicate with the network service provider 140 and the application service provider 150 on the regional network 135. Further, the access edge node 160 includes a service agent unit 340 and a control unit 330, and may optionally include a translation table 350, a transfer unit 360, a coordination unit 370, and a broadcast handler 380.
The service agent unit 340 is composed of a service agent management / control unit 342 and a service binding hosting unit 344. The service agent unit 340 holds the information of the existing service agent 170 in the service agent management / control unit 342. The service agent management and control unit 342 is then responsible for creating and managing the service binding 346. Therefore, the service agent management / control unit 342 determines when a new service binding 346 is requested or an existing service binding is deleted, and subsequently creates / deletes the service binding 346. Service agent management and control unit 342 is also responsible for adding / removing user devices to existing service bindings. In addition, the service agent management and control unit 342 is responsible for ensuring the synchronicity of service binding 346 related information with the access nodes communicating with each other.
Next, FIGS. 3 and 4a will be described at the same time. FIG. 4a is a chart illustrating the items of the service agent management / control unit 342. With the exception of the first line, which is the header line, each line in FIG. 4a illustrates items of several service agents 170 managed and controlled by the service agent management and control unit 342. Each column in Figure 4a corresponds to the specific information held by the service agent management and control unit 342 for each service agent 170. The first column shows the identification of the service agent 170. The identification is typically a numeric identifier that behaves as a service agent identifier. In a preferred embodiment of the invention, each service agent within the access edge node has a unique service agent identifier. The second column shows the identification of a particular service type for the corresponding service agent. For example, if one service provider domain 140 or 150 provides multiple services, each service provided is associated with a different service type due to the differentiation between the various services in the service provider domain. The third column identifies the preferred or required quality of service (QoS). The quality of service (QoS) described above is the quality of service (QoS) required to properly forward data traffic for the associated service type and service agent described above. Examples of QoS criteria include delay, bit error rate, bandwidth, and recommended protocols. The fourth column points to the port used by the access edge node 160 to further route the received data traffic associated with the individual service agent. In addition to this item, the service agent management and control unit is used to create added service agents and delete service agents that are no longer needed. 342 includes sufficient logic software and hardware. It should be noted that although the items of the service agent management / control unit are represented in the form of a table in Fig. 4a, such items are not limited to those shown in Fig. 4a. The service agent management and control unit can also consist of a relational database, hard-coded components, microprocessors, programming libraries, and so on.
Next, FIGS. 3 and 4b will be described at the same time. FIG. 4b is a chart illustrating the items of the service binding hosting unit in the disclosure of the present invention. With the exception of the header line, each line in Figure 4b illustrates several service binding 346 items hosted within the service binding hosting unit 344. Each column in Figure 4b represents the possible information hosted within the service binding hosting unit 344 for each service binding 346. However, such information is not constructed as "essential" information, and the information listed in FIG. 4 represents an example of a field used in one embodiment of the present invention. The first column represents the identification of the corresponding service agent, for example by using the service agent identifier of the service agent. The second column identifies the service type, as described for Figure 4a. The other columns represent the forwarding primitives for data traffic related to service bindings. More specifically, the third column is the MAC address of the user domain (Media). Access Controll address). The fourth column consists of identifying the ports used by the user domain when communicating with the access node that provides the connection. The fifth column corresponds to the local network indefinite identifier used by the user domain and may contain, for example, potential or explicit VLAN information. The sixth column shows the MAC address of the access node that provides the connection to the user domain. Thus, to provide data traffic on the access domain 115, each service binding 346 connects one service agent with two access nodes. It should be noted that although the items of service binding hosting unit 344 are represented in the form of a table in Figure 4b, such items are not limited to those shown in Figure 4b. The service binding hosting unit can also consist of a relational database, hard-coded components, microprocessors, programming libraries, and so on.
The combination of ingress ports and VLAN information thus provides a concise and reliable way to quickly relate incoming data traffic to the appropriate service bindings. Other combinations of information can also be used to reliably align incoming data traffic with the corresponding service bindings. For example, in the first embodiment of the invention, bridging between user domains of the invention comprises port level bridging. As briefly mentioned above, port-level bridging is between the ports of the first access node and the ports of the second access node without affecting other fields in the Ethernet message, such as the VLAN tag field. Consists of bridging data traffic. In a second embodiment of the invention, bridging between user domains of the invention comprises subnet-level bridging. Therefore, the data traffic between the first user domain and the second user domain includes the input port information of the first access node, the corresponding first VLAN, the input port information of the second access node, and the corresponding input port information. Bridging using the second VLAN. Typically, once a service binding is created and the access node propagates that information, data traffic between user domains is processed on the access domain according to the service binding.
In particular, in one embodiment of the invention, the service agent accommodates the provision of streaming data traffic between user domains, while the service binding 346 hosted within the service binding hosting unit 344 is the first. And provide the necessary information for the second user domain. Therefore, as can be seen in the line corresponding to the service agent identifier SA2, the service type supports streaming between user domains, and the user MAC information corresponds to the MAC address of the first user domain and another corresponding to the second user domain. Includes the MAC address of. The fields corresponding to the user port information, the local network context, and the access-no MAC address that provides the connection also provide information about both the first and second user domains. On the other hand, in another embodiment of the present invention, the user MAC address can be replaced by the I / O port identification of the access domain I / O unit, and the local network context can correspond to the VLAN information. is there.
Returning to Figure 3, when the access edge node control unit 330 receives the data traffic 710b, it is responsible for deciding whether the data traffic 710b corresponds to one service agent. To do so, control unit 330 accesses the information contained in the header of the data traffic and queries service agent management and control unit 342, which determines whether one service agent 170 corresponds to the information contained in the header. .. If data traffic bridging is done for two user domains where connections are provided by different access edge nodes, the control unit will receive an MPLS of data traffic between the two related access edge nodes. Create layer 2 tunneling.
If necessary, the control unit 330 optionally cooperates with the translation table 350. Since each service agent 170 of the service agent management / control unit is uniquely identified by the service agent identifier, the service agent identifier corresponding to the service agent 170 and the corresponding service provider are provided in the translation table at an appropriate time. It is essential to maintain a mapping to and from the domain (140 or 150). In this way, when the access domain input / output unit 310 receives data traffic having a target address corresponding to the virtual MAC address for the access edge node 160, the virtual MAC address of the access edge node is provided in the VLAN tag. The control unit 330 queries translation table 350 to quickly translate to the desired service provider domain address (140 or 150 address) corresponding to the service agent identifier given. In the description of the present invention, the virtual MAC address indicates the physical address of the node and the related port information of the corresponding I / O unit.
In addition, the control unit 330 is transferred to the transfer unit 360 to determine whether the data traffic received by the access domain I / O unit 310 is forwarded directly to the service provider domain I / O unit without any modification. Inquire. Finally, the control unit 330 also cooperates with the adjustment unit 370. Coordinating unit 370 was pointed to and / or requested by the corresponding service agent 170 whether it received data traffic on either the access domain I / O unit 310 or the network / application service provider domain I / O unit 320. As such, keep upstream / downstream traffic in order, mark, and remark traffic.
Next, FIG. 5 will be described. FIG. 5 is a schematic view of one access node according to the disclosure of the present invention. For locational reasons within the access domain 115, the access node 120 includes an access domain I / O unit 520 to communicate with the access network 130 and the access edge node 160 of the access domain 115. The access node 120 also includes a user domain I / O unit 510 to communicate with the user domain 110. In this way, the data traffic entering the access node 120 sent from the user domain whose access node provides the connection service to the access network 130 or sent to the user domain is sent to the user domain I / O unit 510. Pass.
Access node 120 also includes service binding unit 540. The service binding unit hosts service binding related information. Service binding related information includes specific service binding information (in the form of service agent attributes and service types), information about the access node's port for communicating with the user domain, and the local network context of the user domain. The service binding unit 540 contains only service binding related information regarding the service binding related to the access node. In this way, the service binding unit 540 in the different access nodes 120 stores different information. The service binding related information includes the service agent identifier, the user port of the user domain I / O unit 510, and some or all of the user domain's local context information.
The access node 120 further includes a control unit 530. The control unit evaluates the data traffic 710a received by the user domain I / O unit 510 to determine the requested procedure. To that end, control unit 530 queries service binding unit 540 to determine if the service binding corresponds to received data traffic 710a. If the received data traffic corresponds to a service binding that bridges the data traffic between user domains, the control unit 530 forwards the received data traffic 710a to the bridging unit 550. The bridging unit 550 makes the necessary changes to the data traffic to prepare the received data traffic for forwarding on the access domain. In addition, bridging unit 550 adds data traffic 710 received in the user data field of the Ethernet unicast message. This is referred to as tunneling throughout this specification. The bridging unit 550 also assigns a destination address to the Ethernet unicast message to correspond to the virtual MAC address of the access edge node 120. Finally, the bridging unit further assigns a value corresponding to the port of the access domain I / O unit 520 to the VLAN tag field of the Ethernet unicast message.
In one embodiment of the invention, data traffic is bridged over the access domain by tunneling the data traffic within a unicast message on the access node that acts as an entry point for the access domain for the source user domain. Will be done. The unicast message is sent to the access edge node, which redirects to the access edge node that provides the connection to the second user domain, which is the intended recipient of the data traffic. Thus, it is essential that the access node providing the connection to the receiving user domain has the necessary capability to detunnel the received data traffic corresponding to the tunneled data traffic. To that end, the control unit 530 further determines when the received data traffic consists of tunneled data traffic, detunnels the data traffic, and through the user domain I / O unit 510, the recipient. Transfer to the user domain that is.
Next, FIG. 6 will be described. FIG. 6 shows a simplified flow chart of how to perform layer 2 bridging according to the disclosure of the present invention. The method begins at step 605. In step 605, the first access node receives data traffic from the first user domain. The method then continues to step 610. In step 610, the control unit of the first access node identifies whether the service binding in the service binding unit 540 corresponds to the received data traffic. A number of parameters may be used to correlate received data traffic with service binding related information. Once the corresponding service binding has been identified and the service binding corresponds to the bridging service between user domains, in step 615 the corresponding service agent identifier is bridging in order to properly tunnel the data traffic in the unicast message. Provided to unit 550. Step 615 also includes the transfer of tunneled data traffic to the access edge node 160 through the access domain I / O unit 520. The tunneled data traffic is then received at the access edge node 160 in step 620. At step 625, access edge node 160 identifies whether there is a service binding corresponding to the received, tunneled data traffic. At step 630, the access edge node modifies the destination address of the tunneled data traffic to correspond to the virtual MAC address of the access node providing the connection to the second user domain according to the corresponding service binding identified. To do. The access edge node then forwards the tunneled data traffic modified in step 635 on the access domain. The modified, tunneled data traffic is received within the second access node in step 640. If the second access node evaluates the type of data traffic in step 645 and is determined to consist of tunneled data traffic, then in step 650 it degenerates the modified, tunneled data traffic. Tunnel. Once detunneled, in step 655 the data traffic is forwarded to the receiving user domain.
Next, FIG. 7 will be described. FIG. 7 is an explanatory diagram showing changes made to Ethernet type messages to allow bridging of data traffic in accordance with the present invention. The first user domain sends Ethernet message 710a to the first access node, and in Ethernet message 710a, DA corresponds to the MAC address of the second user domain, SA corresponds to the MAC address of the first user domain, and so on. The VLAN tag corresponds to the local information of the first user domain. On the access node, the Ethernet message is encapsulated in the user data field of another Ethernet message 710b. The DA and SA of Ethernet message 710 are assigned the virtual MAC address of the access edge node and the virtual MAC address of the access node, respectively. The VLAN tag field, on the other hand, is used by the access domain I / O unit 520 to contain information about the I / O ports used for this data traffic. Ethernet message 710b is sent from the first access node to the access edge node, which is the second access node that provides the connection to the receiving user domain, as depicted in Ethernet message 710c. Redirected by modifying the destination address to correspond to the virtual MAC address of. Finally, the Ethernet message 710c is forwarded to the second access node, where it is detunneled and forwarded to the receiving user domain to obtain the Ethernet message 710d. To facilitate the management of VLAN information, an option that can be used is the attribute of the VLAN value to the port identification of the access node. For example, the access node port 0 uses the VLAN value 455 and port 1 uses the VLAN value 456.
As can be seen, changes to data traffic for bridging over the access domain are visible only to access node 120, access network 130, and access edge node 160. Changes to data traffic are transparent to user device 110. The modification is made possible by the service banding created by the access edge node 160 and can be implemented at both the access node 120 and the access edge node 160. Service bindings stored on both the access node and the access edge node store the information required to make changes to the data traffic to enable bridging.
Although some preferred embodiments of the methods and nodes of the invention are set forth in the accompanying drawings and described in the detailed description above, the invention is not limited to the examples and protocols described and is patented. It should be understood that various changes, modifications and alternatives are possible that do not depart from the technical thinking of the invention described and defined in the claims.
<figref num="1">It is explanatory drawing which shows the prior art example of an IP network.</figref><figref num="2">It is the schematic which illustrates the network in which this invention was incorporated.</figref><figref num="3">It is the schematic of the access edge node according to the disclosure of this invention.</figref><figref num="4a">It is a figure which illustrated the item of the service agent management | control unit in this invention.</figref><figref num="4b">It is a figure which illustrated the item of the service binding hosting unit in the disclosure of this invention.</figref><figref num="5">It is the schematic of the access node according to the disclosure of this invention.</figref><figref num="6">It is a simplified flowchart of the method of performing layer 2 bridging according to the disclosure of this invention.</figref><figref num="7">It is a chart representing the changes made to the data traffic with respect to the tunneling of the data traffic according to the disclosure of the present invention.</figref>
Every citation, both ways
| Document | Relation | Office |
|---|---|---|
| US6269404B1 | Cites | United States of America |
| US2004165600A1 | Cites | United States of America |
| WO03092226A1 | Cites | World Intellectual Property Organization (WIPO) |
82 members in 10 offices
Priority claims19
| Document | Office | Kind | Date |
|---|---|---|---|
| 60651971 | United States of America | – | |
| 65197105 | United States of America | P | |
| 65197105 | United States of America | P | |
| 60674307 | United States of America | – | |
| 67430705 | United States of America | P | |
| 67430705 | United States of America | P | |
| 11353164 | United States of America | – | |
| 2006050487 | International Bureau of the World Intellectual Property Organization (WIPO) | W | |
| 2006050487 | International Bureau of the World Intellectual Property Organization (WIPO) | W | |
| 35316406 | United States of America | A | |
| 35316406 | United States of America | A | |
| 2005651971 | – | – | – |
| 2005674307 | – | – | – |
| 2006353164 | – | – | – |
| 2006050487 | – | – | – |
| US20050651971P | – | – | – |
| US20050674307P | – | – | – |
| US20060353164 | – | – | – |
| WO2006IB50487 | – | – | – |
Members82
| Document | Office | Kind | |
|---|---|---|---|
| CA2594429A1 | Canada | A1 | |
| CA2594432A1 | Canada | A1 | |
| US2006182123A1 | United States of America | A1 | |
| US2006182146A1 | United States of America | A1 | |
| US2006184645A1 | United States of America | A1 | |
| US2006184694A1 | United States of America | A1 | |
| US2006184695A1 | United States of America | A1 | |
| WO2006085233A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2006085234A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2006085286A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2006085290A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2006085292A1 | World Intellectual Property Organization (WIPO) | A1 | |
| CA2604234A1 | Canada | A1 | |
| WO2006114713A2 | World Intellectual Property Organization (WIPO) | A2 | |
| US2006251055A1 | United States of America | A1 | |
| WO2006085233A3 | World Intellectual Property Organization (WIPO) | A3 | |
| WO2006114713A3 | World Intellectual Property Organization (WIPO) | A3 | |
| WO2006085234A3 | World Intellectual Property Organization (WIPO) | A3 | |
| EP1849265A1 | European Patent Office (EPO) | A1 | |
| EP1849266A1 | European Patent Office (EPO) | A1 | |
| EP1849267A1 | European Patent Office (EPO) | A1 | |
| EP1849271A2 | European Patent Office (EPO) | A2 | |
| EP1849272A2 | European Patent Office (EPO) | A2 | |
| EP1878171A2 | European Patent Office (EPO) | A2 | |
| CN101120544A | China | A | |
| CN101120545A | China | A | |
| CN101120546A | China | A | |
| CN101120553A | China | A | |
| CN101120554A | China | A | |
| CN101164302A | China | A | |
| JP2008530881A | Japan | A | |
| JP2008530882A | Japan | A | |
| JP2008530889A | Japan | A | |
| JP2008530891A | Japan | A | |
| JP2008537365A | Japan | A | |
| JP2008538885A | Japan | A | |
| EP1849266B1 | European Patent Office (EPO) | B1 | |
| EP1849267B1 | European Patent Office (EPO) | B1 | |
| AT418212T | Austria | T | |
| AT421206T | Austria | T | |
| ATE418212T1 | Austria | T1 | |
| ATE421206T1 | Austria | T1 | |
| DE602006004307D1 | Germany | D1 | |
| EP1849272B1 | European Patent Office (EPO) | B1 | |
| DE602006004845D1 | Germany | D1 | |
| EP1849265B1 | European Patent Office (EPO) | B1 | |
| EP1849271B1 | European Patent Office (EPO) | B1 | |
| AT424678T | Austria | T | |
| AT425612T | Austria | T | |
| AT425617T | Austria | T | |
| ATE424678T1 | Austria | T1 | |
| ATE425612T1 | Austria | T1 | |
| ATE425617T1 | Austria | T1 | |
| DE602006005468D1 | Germany | D1 | |
| DE602006005620D1 | Germany | D1 | |
| DE602006005621D1 | Germany | D1 | |
| ES2318730T3 | Spain | T3 | |
| US7660253B2 | United States of America | B2 | |
| BRPI0607334A2 | Brazil | A2 | |
| BRPI0607337A2 | Brazil | A2 | |
| CN101120544B | China | B | |
| US7792996B2 | United States of America | B2 | |
| US7801039B2 | United States of America | B2 | |
| CN101120546B | China | B | |
| CN101120554B | China | B | |
| CN101120553B | China | B | |
| JP4583455B2 | Japan | B2 | |
| JP4583456B2This record | Japan | B2 | |
| US7881198B2 | United States of America | B2 | |
| JP4638511B2 | Japan | B2 | |
| JP4696131B2 | Japan | B2 | |
| JP4698684B2 | Japan | B2 | |
| US8077619B2 | United States of America | B2 | |
| BRPI0610375A2 | Brazil | A2 | |
| JP5133873B2 | Japan | B2 | |
| EP1878171B1 | European Patent Office (EPO) | B1 | |
| CA2594432C | Canada | C | |
| CA2604234C | Canada | C | |
| CA2594429C | Canada | C | |
| CN104717118A | China | A | |
| CN104717118B | China | B | |
| BRPI0607334B1 | Brazil | B1 |
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 no payment of annual feesLAPS | LAPS | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| 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 | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| 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 request for application examinationJAPANESE INTERMEDIATE CODE: A621A621 | A621 |
Numbers
- Publication
- 4583456
- Publication, DOCDB
- 4583456
- Publication, EPODOC
- JP4583456B
- Application
- 2007554731
- Application, DOCDB
- 2007554731
- Application, EPODOC
- JP20070554731
Titles2
- Japanese
- アクセスドメイン上でデータトラフィックのブリッジングを行う方法、およびノード
- English
- How to bridge data traffic on the access domain, and nodes
Classification
- CPC, 4
- H04L12/4633
- H04L12/4666
- H04L12/2869
- H04L12/18
- IPC, 2
- H04L12 56
- H04W92 02