JP3757863B2 - Access network equipment - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to an access network apparatus that provides a user terminal with a communication path to an ISP (Internet Service Provider) network or a specific private network.
[0002]
[Prior art]
Communication using PPP (Point-to-Point Protocol) when a general user who has contracted with an access network such as ADSL (Asynchronous Digital Subscriber Line) has designated a private network such as an ISP network or a company at the start of communication. When performing the above, the user terminal first establishes a PPPoE (PPP over Ethernet) session such as ADSL with the access server. After that, the access server selects a destination ISP or company based on the PPP user authentication information received from the user terminal, and the user passes through the VPN (Virtual Private Network) tunnel between the access server and the ISP, and then the PPP Communication by is realized.
[0003]
As a VPN tunnel at this time, for example, L2TP (Layer 2 Tunneling Protocol) is used. L2TP was originally developed for a remote access server that accepted a PPP dial-up connection via a telephone to tunnel a PPP frame to the gateway device of the target private network via the IP (Internet Protocol) network. This protocol is also applied to tunneling from a remote access server provided as a public telephone network facility.
[0004]
[Problems to be solved by the invention]
In the above prior art, because the access server selects the connection destination ISP or company based on the PPP user authentication information received from the terminal used by the contracted user, the user terminal is connected to the access server. A PPPoE session is established between them and LCP (Link Control Protocol), a PPP sub-protocol, is negotiated and authentication information is transmitted. Therefore, it was necessary to tunnel PPP frames between the access server and the ISP.
[0005]
The above-mentioned conventional technology is the depth of the protocol stack of L2TP, that is, capsule / decapsulation in the access server and ISP / enterprise gateway device by encapsulating the user IP packet with PPP, L2TP, UDP (User Datagram Protocol), IP There has been a problem that the processing load is not taken into consideration, so that the transfer throughput is small and the transfer delay is large.
[0006]
[Means for Solving the Problems]
The present invention reduces the encapsulation level between the access server and the connected gateway device, reduces the encapsulation level between the access server and the connected gateway device without impairing the function of the access server selecting the connected network based on the transmission information from the user terminal, and increases the transfer throughput. Provide technology to reduce delay.
[0007]
The present invention provides a technique for suppressing an increase in traffic between an access server and a connection destination gateway device according to a PPPoE connection procedure when PPPoE is applied.
[0008]
The present invention provides a technique for realizing a connection service for each user by recognizing the user by the access server even when the PPP is not terminated by the access server.
[0009]
The present invention provides a technique for equalizing the traffic load and increasing the number of simultaneously connected users in a connection destination network when there are a plurality of connection destination gateway devices belonging to the same connection destination network.
[0010]
The present invention provides a technology that enables access to an IPv6 network without replacing an access server of an existing facility.
[0011]
Specifically, the present invention provides a MAC frame transmission / reception processing unit for transmitting / receiving MAC (Media Access Control) frames to / from a gateway device of a connection destination network to the access server, and a MAC address of the gateway device of the connection destination network. And a connection destination network information storage processing unit for associating the identification information of the connection destination network.
[0012]
When the terminal transmits identification information of the connection destination network to the access server in order to inquire about the MAC address of the connection destination network, the access server specifies the MAC address to be responded by the connection destination network information storage processing unit, and responds to the terminal . This can reduce transmission of inquiry broadcast frames to the ISP side network.
[0013]
In addition, the present invention receives a MAC address inquiry packet (PADI) issued by a terminal to which an ISP name that a user desires to connect is set in the access server, and issued by the PADI or the terminal in which the ISP name is set. A processing unit is provided for transmitting the same packet as the MAC address inquiry packet (PADI) to the ISP side network.
[0014]
When the connection destination network information storage processing unit receives identification information of a connection destination network that has not been associated yet from the terminal, it makes an inquiry to the ISP-side network and performs association with the response.
[0015]
Also, connection destination network identification information that does not exist in the connection destination network information storage unit is sent to the line that the gateway device of the connection destination network seems to be connected, and a response from the gateway device of the corresponding connection destination network is sent. A response waiting time measuring unit for waiting is provided, and the same connection destination network identification information is received from the terminal within a predetermined specified time after sending the connection destination network identification information to the line and before receiving the response. In this case, the identification information is not sent again to the line.
[0016]
Even when PPP is not terminated at the access server, PPP that monitors PPP authentication frames sent and received between the terminal and the gateway device of the connection destination network to recognize the user at the access server and realize the connection service for each user An authentication frame monitoring unit and a session user storage unit that stores association between user information acquired by the PPP authentication frame monitoring unit and a PPPoE session ID are provided.
[0017]
In addition, a user profile management unit that manages session control parameters corresponding to user information is provided, and session control is performed based on the control parameters stored in the user profile management unit.
[0018]
In addition, when there are multiple connection destination gateway devices belonging to the same connection destination network, in order to equalize their traffic load and increase the number of simultaneous connection users of the connection destination network, the traffic volume for each gateway device of the connection destination network A traffic volume measurement unit for measuring traffic and a gateway group management unit for recognizing multiple gateway devices as the same group. When there is a connection request from a terminal, a connection with a small traffic volume within the same group Select the gateway device of the destination network.
[0019]
DETAILED DESCRIPTION OF THE INVENTION
Examples of the present invention will be described below.
[0020]
(System configuration)
FIG. 1 shows a network configuration for a user to access an ISP 1203 or the Internet 1205 using a user side device (PC) 1200.
[0021]
The TE 100 is a user terminal (hereinafter referred to as TE or Terminal Equipment) viewed from an access network apparatus (hereinafter referred to as Access Gateway or AG) 101 according to the present embodiment. The PC 1200 and the TE100 are connected by an interface such as Ethernet (Ethernet is a registered trademark of Fuji Xerox), RS232C, USB (Universal Serial Bus), and the like. PC1200 and TE100 may be integrated.
[0022]
TE100 communicates with AG101 via an access network. Examples of access networks include ADSL 1206, FTTH (Fiber to The Home) 1207, and cable television network 1208.
[0023]
In the case of the ADSL 1206, the TE 100 is connected to a DSLMODEM (Digital Subscriber Line Modem, referred to as DSLMDM) 1201, the DSLMDM 1201 is connected to a DSLAM (Digital Subscriber Line Access Multiplexer) 1202 via a metal cable, and the DSLAM 1202 is connected to the AG 101. The AG 101 is connected to the gateway device ISPGW102 of a plurality of ISPs 1203 via a relay network. ISP 1203 also has a gateway device ISPGW 1204 for the Internet 1205. AG101 can also be connected to a private network PN1214 of a company or the like via a gateway device PNGW1213.
[0024]
When the access network is FTTH 1207, TE 100 is connected to AG 101 via ONU (Optical Network Unit) 1209 and OLT (Optical Line Terminal) 1210.
[0025]
When the access network is a cable television network 1208, connection is made with the AG 101 via a cable modem CM (Cable Modem) 1211 and a cable modem terminator CMTS (Cable Modem Termination System) 1212. There are ATM, Ethernet, etc. as an interface between the access network and AG101.
[0026]
FIG. 2 (a) shows a conventional protocol stack when the access network is ADSL.
[0027]
In FIG. 2 (a), the PC 1200 and the TE 100 are connected by Ethernet to form a local network. The TE 100 has a NAT function and converts the source IP address of the IP packet transmitted by the PC 1200 into an IP address assigned by the AG 101. The TE 100 terminates the PPP link, and the opposite end of the link is the gateway device ISPGW 102 of the connection destination ISP tunneled by L2TP. The packet whose IP address has been converted in TE100 is subjected to PPP framing, and then a PPPoE header is added, and the packet is transmitted to the DSLMDM 1201 as a MAC frame. The DSLMDM 1201 converts the received MAC frame into an ATM cell and transmits it to the DSLAM 1202. In this figure, since the interface between the DSLAM 1202 and the AG 101 is ATM, the ATM cell is restored to the original MAC frame in the AG 101.
[0028]
AG 101 replaces the internal PPP frame with the L2TP session based on the PPPoE header. The PPP frame encapsulated in L2TP is further added with a UDP header and an IP header, and then transmitted to the ISPGW 102. ISPGW102 extracts a PPP frame from the received packet, performs PPP protocol processing, and extracts an internal user IP packet.
[0029]
The interface of AG101 and ISPGW102 includes ATM, POS (Packet Over Sonet), etc. in addition to Ethernet, but does not affect the layers above IP.
[0030]
When the TE 100 starts access to the ISP, the TE 100 establishes a PPPoE session with the AG 101 instead of the ISPGW 102. Then, LCP (Link Control Protocol), which is a sub-protocol of PPP, is negotiated and authentication information is transmitted.
[0031]
AG 101 selects a gateway device of a connection destination ISP based on the received authentication information, and establishes an L2TP tunnel / session for the IP address.
[0032]
The ISPGW 102 assigns an IP address to the TE 100 by negotiation of IPCP (Internet Protocol Control Protocol), which is a PPP sub-protocol, whereby the PC 1200 can access the target ISP via the TE 100 and the ISPGW 102.
[0033]
AG 101 transfers the PPP frame transmitted from TE 100 to ISPGW 102 and the PPP frame transmitted from ISPGW 102 to TE 100 until the L2TP session is disconnected.
[0034]
Thus, conventionally, the connection destination ISPGW 102 is selected based on the PPP user authentication information received from the TE 100 by the AG 101. Therefore, it was necessary to establish a PPPoE session between TE100 and AG101. Furthermore, in order to perform communication by PPP between ISPGW102 and TE100, it was necessary to tunnel a PPP frame between AG101 and ISPGW102.
[0035]
(Example 1)
In this embodiment, PPPoE is adopted not only between the TE 100 and the AG 101 but also as a tunneling protocol between the AG 101 and the ISPGW 102. Figure 2 (b) shows the protocol stack. It is assumed that ISPGW102 supports PPPoE.
[0036]
In this embodiment, the relay network does not have to be an IP network, and has a MAC frame transfer function.
[0037]
The ATM or POS layer is shown below the Ethernet MAC layer, but this is not present in the case of Gigabit Ethernet, for example.
Compared with the protocol of Ethernet MAC layer and above in Fig. 2 (a), in Fig. 2 (a), there are three protocols, IP, UDP and L2TP, whereas in Fig. 2 (b), only PPPoE. This indicates that the protocol processing in AG101 and ISPGW102 is lighter than in FIG. 2 (a).
[0038]
(AG configuration example)
FIG. 3 shows a configuration example of the AG 101 that realizes the present embodiment.
[0039]
AG 101 includes a physical line accommodation card (Line Interface, hereinafter referred to as LIF) 1100, an upper layer processing card (High Layer Module, hereinafter referred to as HLYR-MDL) 1103, a switch SW 1108, and a device control card (Controller, hereinafter referred to as CTL) 1109.
[0040]
First, a signal from the outside of the AG 101 becomes a digital electric signal shaped by a physical layer (hereinafter referred to as PHY) chip 1101 of the LIF 1100, and is input to a lower layer protocol processing unit (Low Protocol, hereinafter referred to as LOWPROT) 1102. . LOWPROT1102 performs the protocol processing when the line type is ATM or POS, and then transmits the MAC frame of the upper protocol to the HLYR-MDL1103. In the HLYR-MDL 1103, the received MAC frame is transferred by a MAC layer processing unit (MAC frame forwarding, hereinafter referred to as MACFWD) 1107. FIG. 5 shows an address table managed by the MACFWD 1107.
[0041]
The address table 1000 shown in FIG. 5 includes a MAC address 1001 of an external device connected to the line of the AG 101, its line ID 1002, and an ISP flag 1003 for identifying whether the MAC address is ISP or TE. The line ID 1002 is an identifier assigned to each physical line when the physical line is Ethernet, and is assigned to each VC when the physical line is ATM. When MACFWD 1107 receives the MAC frame, it refers to address table 1000, identifies the destination line ID from the destination MAC address of the frame, and transfers it to the target HLYR-MDL 1103 via SW 1108 based on it. Similarly, the transfer destination HLYR-MDL 1103 also refers to the address table 1000, identifies the LIF 1100 as the transmission destination and the physical port from the line ID, and transmits them outside the AG 101 via the LOWPROT 1102 and the PHY 1101. The ISP flag 1003 is used to identify a target line when broadcasting a PPPoE packet, and will be described in detail later.
[0042]
In FIG. 3, a MACFWD 1107 is connected to a high function protocol processing unit (Proccessing unit, hereinafter referred to as PROC) 1104. PROC 1104 receives a specific PPPoE control packet and instructs MACFWD 1107 on session control and frame encapsulation method. The packet that the PROC 1104 expects to receive is identified by the MACFWD 1107 and transferred to the PROC 1104. The PROC 1104 includes a CPU 1106 and a DB 1105 that perform the above processing. The DB 1105 holds a cache table 900 that manages the identifier of the ISP transmitted by the TE 100 when making a connection request and the MAC address of the connection destination gateway device associated with the identifier.
[0043]
FIG. 4 shows the cache table 900. Cache table 900 is ISP identifier ServiceName 901, gateway device MAC address 902, remaining entry valid time 903, and transmission guard time that suppresses transmission of MAC address inquiry packets (PPPoE Active Discovery Initiation (PADI) packets). 904. The CPU 1106 of the PROC 1104 performs PPPoE control packet reception processing based on the cache table 900. The CTL 1109 controls the entire AG101. It has a CPU 1111 as a processing execution unit and a DB 1110 that holds information necessary for control.
[0044]
(Example 1-1)
In the first embodiment, an embodiment in which the AG 101 operates as a PPPoE bridge will be described.
[0045]
FIG. 6, FIG. 9, and FIG. 10 show message sequences of this embodiment. In this embodiment, the TE 100 does not recognize the AG 101 as an opposite node in the MAC layer, and recognizes the gateway device of the connection destination ISP 1 (102) as the opposite node. On the other hand, it appears to ISP1 (102) that TE100 and AG101 are connected to the same segment.
[0046]
FIG. 6 shows a connection sequence when the TE 100 requests connection to an ISP that the AG 101 does not hold in the cache table 900. As an overview, the flow in which TE100 obtains the MAC address of the connection destination ISP1 (102) is the transmission / reception of PADI103 and PADO (PPPoE Active Discovery Offer) 108, and the flow that subsequently establishes the actual PPPoE session is PADR (PPPoE Active Discovery Request) 110 and PADS (PPPoE Active Discovery Session-confirmation) 111, and then PPP negotiation 112 is performed on the PPPoE session.
[0047]
First, the format of the PPPoE packet and TAG 3109 will be described, and then FIG. 6 will be described in detail.
[0048]
Fig. 7 shows the PPPoE packet format. The PPPoE packet 3100 is a MAC frame whose Ether type 3103 value is 0x8863 or 0x8864 (0x indicates a hexadecimal number). The destination MAC address 3101 is a broadcast address when the PPPoE packet type is PADI, and the other is a unicast address of the destination device. In this embodiment, the PADO source MAC address 3102 is set to the ISP gateway device address, not the original PPPoE packet source address.
[0049]
The version of PPPoE is set in Ver3104. Set 1 to type3105. Code 3106 indicates the type of PPPoE packet, and various values of PADI, PADO, PADR, PADS, and PADT (PPPoE Active Discovery Terminate) can be identified by this value. A session ID 3107 is an ID for identifying a PPP session to which a PPP frame to be encapsulated belongs. Length 3108 indicates the PPPoE payload length. The PPPoE payload is the TAG 3109 when the Ether type 3103 value is 0x8863, that is, a control packet, and the PPP frame 3110 when the Ether type 3103 value is 0x8864, that is, a PPP frame encapsulated packet. In the case of a PPPoE control packet, a plurality of TAGs 3109 may be included.
[0050]
A checksum 3115 is a checksum defined as a MAC frame format. The format of the PPP frame 3110 differs depending on whether the content of the protocol 3111 indicates IP or a PPP control frame. In the former case, a user IP packet 3114 is set behind the protocol 3111. In the latter case, a code 3112 indicating a message type defined for each sub-protocol of PPP indicated in the protocol 3111 and other information 3113 are set.
[0051]
FIG. 8 shows the format of TAG3109. The TAG 3109 includes a TAG type 3200, a TAGLength 3201, and a TAGValue 3202. The ISP name set in PADI103 is set in the TAGValue field of ServiceNameTAG (the value of TAG type 3200 is 0x0101).
[0052]
Next, FIG. 6 will be described.
[0053]
The TE 100 transmits a PPPoE PADI packet 103 to the broadcast MAC address. In the PADI 103, ISP1 is set as the ISP name that the PC1200 user desires to connect to.
[0054]
When AG 101 receives PADI 103, it checks whether the ISP name (ISP1 in this case) set in PADI 103 is registered in cache table 900 (step 104).
[0055]
If not registered, a new entry with ServiceName 901 of ISP1, remaining effective time 903 of 0, and transmission guard time 904 of, for example, a few seconds is registered as a new entry in the cache table 900 (steps 105 and 106).
[0056]
Thereafter, the AG 101 broadcasts the same packet as the PADI 103 received from the TE 100 to the outside of the AG 101 as the PADI 107. At this time, the AG 101 transmits only the line for which the ISP flag 1003 in the address table 1000 indicates ISP. As a result, PADI that is a broadcast message is not wastedly transmitted to the TE side. Note that the ISP flag 1003 is consciously set by command operation by a maintenance person when constructing a network.
[0057]
When the ISP 1 (102) receives the PADI 107, the ISP 1 (102) recognizes that the ISP name shown in the PADI 107 matches itself, and transmits the PADO 108 to the PADI transmission source MAC address, that is, the TE 100. As a result, ISPGW 102 is selected.
[0058]
When AG101 receives PADO, it searches the address table 1000 with the destination MAC address and transfers it to TE100. At the same time, it sends the MAC address Ai of ISP1 (102) to MACaddr902 of cache table 900, and 3600 for the remaining valid time 903, for example, transmission guard Set time 904 to 0.
[0059]
The TE100 that has received the PADO 108 transmits the PADR 110 to the ISP 1 (102) via the AG 101, and the ISP 1 transmits the PADS 111 to the TE 100. Thus, a PPPoE session is established between TE100 and ISP1 (102).
[0060]
Thereafter, PPP negotiation 112 is performed between TE100 and ISP1 (102), thereby enabling IP packet communication 113.
[0061]
In addition, since AG101 does not perform user authentication, it seems that AG101 cannot manage users at first glance, but based on ATM VPI / VCI set in advance between DSLMDM1201 and AG101 connected to TE100 and installed in each home, It is possible to manage which service subscriber is accessing.
[0062]
As described above, according to the above sequence, in the MAC address inquiry phase of PPPoE, the access server can store the MAC address of the gateway device of the ISP network in the cache table. In response to the inquiry, the access server can respond on behalf of the gateway device as described with reference to FIG. 9, which has the effect of reducing the amount of traffic between the access server and the ISP gateway device.
[0063]
Next, a sequence in another situation will be described with reference to FIG.
[0064]
In FIG. 9, the sequence in the case where the TE 100 requests connection to the ISP while the AG 101 is inquiring about the MAC address of the ISP gateway device will be described. When TE100 designates ISP1 (102) and transmits PADI103 to AG101, AG101 searches cache table 900 for an entry for ISP1 (102) in step 104. If there is an entry in the cache table 900, it is determined whether or not the value of the remaining valid time 903 is positive (step 200),
If it is not positive, it means that it is after the PADI107 from AG101 shown in Fig. 6 has already been sent to the same ISP1 (102) (which nevertheless exists). The PADI 103 received from the TE 100 is discarded (step 201).
[0065]
Even when the TE 100 is a terminal different from the terminal that causes the AG 101 to transmit the PADI 107 to the ISP 1 (102), the PADI transmission from the AG 101 to the same ISP 1 is redundant and is suppressed.
[0066]
In FIG. 9, a sequence when the TE 100 makes a connection request to the ISP whose AG 101 holds the MAC address in the cache table 900 will be described. When the TE 100 transmits the PADI 103, the AG 101 determines in step 104 whether the cache has been registered, and if it has been registered, determines whether the remaining valid time 903 is a positive value (step 200).
[0067]
If it is a positive value, the MAC address of ISP1 (102) registered in the cache table 900 is recognized as valid, and PADO300 is transmitted to TE100 without transmitting PADI103 to the ISP side. This eliminates the need to send useless broadcast messages and increases network traffic. The source address of this packet is MACaddr 902 in the cache table 900. The TE 100 that has received the PADO 300 can perform IP packet communication with the ISP 1 (102) through a sequence similar to that shown in FIG.
[0068]
In the disconnection sequence from TE100, when TE100 transmits a PADT with the source MAC address At and the destination MAC address Ai, AG101 transfers it to ISP1 (102). ISP1 (102) receives it and performs a disconnection process of the PPP link and PPPoE session with TE100.
[0069]
In the disconnection sequence from ISP1 (102), when ISP1 (102) transmits a PADT with the source MAC address Ai and the destination MAC address At, AG101 transfers it to TE100. The TE100 receives it and performs a disconnection process of the PPP link and PPPoE session with the ISP1 (102).
[0070]
FIG. 10 is a sequence for inquiring about the MAC address of ISP1 (102) with AG101 as the transmission source when the remaining valid time 903 of the entry in the cache table 900 of AG101 is equal to or less than the specified value.
[0071]
When the inquiry becomes necessary, AG 101 sets, for example, several seconds as the transmission guard time 904 of the cache table 900 in step 106, and transmits the PADI 601 to the broadcast MAC address. The actual lines to be sent are all the ones whose ISP flag 1003 is ISP in the address table 1000, and only the line specified by MACaddr 902 while the remaining valid time 903 is a positive value. There is a way. Note that the source MAC address of this packet is the address of AG101.
[0072]
When ISP1 (102) receives PADI601, it sends PADO602 to the source MAC address.
[0073]
When AG101 receives PADO602, it sets the remaining valid time 903 and MACaddr 902 of the cache table 900 in step 109, and further clears the transmission guard time 904.
[0074]
This sequence allows AG101 to periodically check the MAC address of the ISP without receiving PADI from TE100, and promptly return PADO when receiving PADI from TE100.
[0075]
As described above, according to the present embodiment, since the MAC address of the connecting terminal is transmitted to the ISP, the ISP can independently perform control (filtering, priority control) and the like based on the MAC address.
[0076]
(Example 1-1-1)
The present embodiment describes the processing of the AG 101 that performs the sequence of FIGS. 6, 9, and 10 using packet reception as a trigger in the embodiment 1-1. FIG. 11 shows the processing flow.
[0077]
This processing is performed by PROC 1104 and MACFWD 1107 in FIG. In the state of waiting for packet reception 700, PADI reception (branch 701) and PADO / PADS reception (branch 703) are processed by PROC 1104. Therefore, MACFWD 1107 transfers these packets unconditionally to PROC 1104. PADR / PADT / other MAC frames may be processed by a normal LAN switch and executed by the MACFWD 1107 regardless of the PROC 1104.
[0078]
First, in the case of PADI reception (branch 701), PROC 1104 checks whether there is an entry corresponding to ISP1 set in PADI in cache table 900 stored in DB 1105 (step 104).
[0079]
If there is no entry, add an entry (step 105)
Set transmission guard time 904 (step 106)
The received PADI packet is transferred to MACFWD 1107. The MACFWD 1107 recognizes that the packet is PADI, and transmits this packet to the line whose ISP flag 1003 in the address table 1000 is ISP (step 107).
[0080]
If there is an entry for ISP1 in the cache table 900 in step 104, it is checked whether the remaining valid time 903 is a positive value (step 200).
[0081]
In the case of a positive value, a PADO packet having the MACaddr 902 of the cache table 900 as the transmission source MAC address is transmitted to the transmission source address of the PADI packet. The PADO packet transferred from the PROC 1104 to the MACFWD 1107 is transmitted from a specific line based on the address table 1000 (step 300).
[0082]
If the remaining valid time 903 is not a positive value in step 200, the received packet is discarded (step 201).
[0083]
In the case of PADO / PADS reception (branch 703), PROC 1104 checks in step 705 that there is an entry for ISP1 in cache table 900, and if there is no entry, creates a new one (step 105).
[0084]
In step 706, the remaining valid time 903 and MACaddr 902 are set, and in step 707, the transmission guard time 904 is cleared to zero. If there is an entry of ISP1 in the cache table 900 in step 705, the process proceeds to step 706. After step 707, it is determined whether the received packet is destined for the MAC address of AG 101 (step 708).
[0085]
If not destined for AG101, the packet is transferred to MACFWD 1107 and sent out from the line based on address table 1000 (step 709).
[0086]
If the address is AG101 in step 708, the process ends. In the case of PADR / PADT / other MAC frame reception (branch 702), the MACFWD 1107 performs normal MAC frame transfer processing based on the address table 1000 (step 704).
[0087]
(Example 1-1-2)
The present embodiment describes the processing of the AG 101 that performs the sequence of FIGS. 6, 9, and 10 with the period activation as a trigger in the embodiment 1-1. FIG. 12 shows the processing flow.
[0088]
When activation starts from the state of cyclic activation waiting 800, the PROC 1104 individually performs the following processing for all ISP-related entries in the cache table 900.
[0089]
It is checked whether or not the value of the transmission guard time 904 is positive (step 801).
[0090]
If positive, subtract the value (step 805)
It is determined whether or not the result is positive (step 806).
[0091]
If it is not positive, it means that the PADO of the response to the PADI transmitted from the AG 101 to the ISP has not returned within the specified time, so the entry is deleted from the cache table 900 (step 807).
[0092]
If the guard time subtraction result is positive in step 806, it is checked whether the remaining effective time 903 is a positive value (step 808),
If it is a positive value, the value is subtracted (step 809).
[0093]
If it is not a positive value, the processing related to the ISP entry is terminated. If the transmission guard time 904 is not a positive value in step 801, that is, if the MAC address is not inquired to the ISP, it is determined in step 802 whether the value of the remaining valid time 903 is positive. If positive, subtract the value (step 803)
It is determined whether the result is larger than a specified value n (step 804).
[0094]
Here, n is a value that determines how long before entry deletion the MAC address inquiry to the ISP starts, and is defined in advance. If the remaining valid time 903 is greater than n, no further inquiry is required, and the process for that entry ends. If the remaining valid time 903 is n or less at step 804, the transmission guard time 904 is set (step 600),
A PADI packet is transmitted to MACaddr 902 (step 601).
[0095]
The PROC 1104 transfers the PADI packet to the MACFWD 1107, and the MACFWD 1107 refers to the address table 1000 and transmits the packet from all the lines whose ISP flag 1003 is ISP. If the remaining valid time 903 is not a positive value in step 802, the process proceeds to step 106 and PADI transmission processing is performed.
[0096]
(Example 1-2)
In the first embodiment, an example in which the AG 101 has MAC addresses in both the TE side interface and the ISP side interface and establishes separate PPPoE sessions between the TE 101 and the AG 101 and between the AG 101 and the ISPGW 102 will be described.
[0097]
The present embodiment will be described with reference to FIGS.
[0098]
FIG. 13 shows a connection sequence when TE 100 requests connection to an ISP that AG 101 does not hold in cache table 900.
[0099]
When TE 100 transmits PADI 103 to AG 101, AG 101 refers to cache table 900 to check whether ISP1 has been registered (step 104).
[0100]
If not registered, add a new entry (step 105)
For example, the transmission guard time 904 is set to several seconds (step 106).
[0101]
Further, in this embodiment, a PADI table for managing to which TE the PADO transmission must be set is set (step 1800).
[0102]
FIG. 14 shows the PADI table. The PADI table 2600 is composed of ServiceName 2601 which is an identifier of the ISP that is inquiring the MAC address, the address TEaddr 2602 of the TE that made the PADI transmission source, that is, the inquiry request, and the PADO waiting time 2603 of the remaining time that the AG 101 waits for PADO from the ISP. This table is held in DB1105 of PROC1104.
[0103]
In FIG. 13, in step 1800, ISP identifier ISP1 set in PADI is set to ServiceName2601, the source address is set to TEaddr2602, and PADO waiting time 2603 is set to several seconds, for example. Thereafter, PADI 1801 with a source MAC address of AG101 is transmitted to ISP1 (102). When ISP1 (102) receives PADI1801, it transmits PADO1802 whose source MAC address is ISP1 (102) to AG101. When AG 101 receives PADO1802, it registers the valid time of this entry in the remaining valid time 903 of the cache table 900, the MAC address of ISP1 (102) in MACaddr 902, and 0 in the transmission guard time 904 (step 110).
[0104]
Thereafter, the AG 101 refers to the PADI table 2600, transmits the PADO 1803 addressed to the TE 100, and deletes the corresponding entry in the PADI table 2600 (step 1804).
[0105]
Upon receiving PADO1803, TE100 transmits PADR1805 to AG101, which is the transmission source address of PADO1803. When receiving the PADR 1805, the AG 101 sets a PADR table for managing to which TE the PADS must be transmitted (step 1806).
[0106]
FIG. 15 shows the PADR table. The PADR table 2700 is composed of ServiceName 2701 which is an identifier of the connection request destination ISP, a PADR transmission source TEaddr 2702, and a PADS waiting time 2703 indicating the remaining time to wait for PADS from the connection request destination ISP. This table is held in DB1105 of PROC1104.
[0107]
In FIG. 13, after setting the PADR table 2700, the AG 101 transmits PADR 1807 with the AG 101 as the transmission source address to the ISP 1 (102). When ISP1 (102) receives PADR1807, it assigns a session ID for identifying a session between AG101 and ISP1 (102), and transmits PADS1808 in which the session ID is set to AG101. AG 101 assigns a session ID for identifying a session between TE 100 and AG 101 to TE 100, and registers it in the session management table together with the session ID notified by PADS 1808.
[0108]
FIG. 16 shows a session management table. The session management table 2200 is composed of TEaddr 2201, TE side session ID 2202, ISPaddr 2203, ISP side session ID 2204, and user name 2205 using the session as seen from AG101. The user name 2205 can be recognized by the AG 101 monitoring a PPP control frame transmitted / received between the TE 100 and the ISP 1 (102) during the PPP negotiation, and an example thereof will be described later.
[0109]
This table is referenced every time one user packet is transferred after the session is established. Therefore, it is desirable that the MACFWD 1107, which is preferably configured by a dedicated LSI, and the PROC 1104, which performs complicated processing based on the user name, each hold this table.
[0110]
When this table is implemented in the apparatus, the MACFWD 1107 may hold a table in which an index is provided instead of the user name entry, and the PROC 1104 may hold a table in which the index is associated with the user name. .
[0111]
MACFWD1107 uses this table to change the PPPoE packet header transmitted from TE100 and forwards it to ISP1 (102), or vice versa. PROC1104 uses this table to create user-specific profile information. To control the session.
[0112]
In FIG. 13, after setting the session management table 2200 (step 1809), the AG 101 transmits the PADS 1810 to the TE 100 based on the PADR table 2700, and deletes the entry related to the transmitted TE from the PADR table 2700 (step 1811).
[0113]
When the TE100 receives the PADS 1810, a PPPoE session is established, and the TE100 performs a PPP negotiation 112 with the ISP1 (102). As a result, IP packet communication 113 becomes possible.
[0114]
FIG. 17 shows a sequence when the TE 100 makes a connection request to the ISP whose AG 101 holds the MAC address in the cache table 900. Step 200 is the same as in FIG. If the remaining valid time 903 of the cache table 900 is a positive value in step 200, the AG 101 transmits the PADO 1803 whose source address is AG 101 to the TE 100. The sequence after TE100 receives PADO1803 is the same as FIG.
[0115]
The cutting sequence from TE100 will be described. When TE100 sends a PADT with a transmission source of TE100 and a transmission destination of AG101 to AG101, AG101 searches TE-side session ID 2202 of session management table 2200 using session ID 3107 in the PADT as a key, and based on the matching entry The PADT header content is changed, and the PADT having the transmission source AG101 and the transmission destination ISPGW102 is transmitted to ISP1 (102). Further, the referenced entry is deleted.
[0116]
A disconnection sequence from ISP1 (102) will be described. When ISP1 (102) sends a PADT with ISPGW102 as the source and AG101 as the destination to AG101, AG101 searches and matches the session ID 2204 in the session management table 2200 using session ID 3107 in the PADT as a key. Based on the entry, the PADT header content is changed, and a PADT with the transmission source AG101 and the transmission destination TE100 is transmitted to TE100. Further, the referenced entry is deleted.
[0117]
(Example 1-2-1)
In the present embodiment, the processing of the AG 101 that performs the sequence of FIGS. 13 and 17 with packet reception as a trigger in the embodiment 1-2 will be described. 18 and 19 show the processing flow.
[0118]
This processing is performed by PROC 1104 and MACFWD 1107 in FIG. When waiting for packet reception 2300, PADI reception (branch 2301), PADR reception (branch 2302), PADO / PADS reception (branch 2303), and PADT reception (branch 2401 in Fig. 19) are processed by PROC1104, so MACFWD1107 Transfer to PROC1104. The PPP frame reception (branch 2400 in FIG. 19) is processed by MACFWD 1107. First, in the case of PADI reception (branch 2301), PROC 1104 checks whether there is an entry of the connection destination ISP in the cache table 900 (step 104),
If not, create a new one (step 105), set ServiceName901 and transmission guard time 904 (step 106),
Further, the PADI table 2600 is set (step 1800), the PADI transmission source address is changed to AG, and then the packet is transferred to the MACFWD 1107. In MACFWD 1107, PADI is transmitted to the line whose ISP flag 1003 in the address table 1000 indicates ISP (step 1801).
[0119]
If there is an entry for the target ISP in the cache table 900 in step 104, it is determined whether the remaining valid time 903 is a positive value (step 200).
[0120]
In the case of a positive value, PADO with the source address AG101 is transmitted to TE100 (step 1803).
[0121]
If it is not a positive value, the received packet is discarded (step 201).
[0122]
In the case of PADO / PADS reception (branch 2303) from the packet reception wait state 2300, the cache table 900 is searched for an entry for ISP1 (step 705).
If it does not exist, create a new ISP1 entry (step 105)
Set the remaining effective time 903 and MACaddr 902 (step 706)
The transmission guard time 904 is cleared (step 707).
[0123]
If there is an entry for ISP1 in step 705, the process proceeds to step 706. After step 707, the type of the received packet is determined (step 2305).
[0124]
If the received packet is PADO, the PADI table 2600 is searched to check whether there is a TE waiting for a response (step 2306).
[0125]
If there is nothing waiting for a response, the process ends. If there is something waiting for a response, PADO is transmitted to TEaddr2602 based on the PADI table 2600 (step 1803).
[0126]
Thereafter, the entry related to the transmitted TE is deleted from the PADI table 2600 (step 1804).
[0127]
The PADO packet transferred by PROC 1104 to MACFWD 1107 is sent to the line based on address table 1000. If the received packet is PADS in step 2305, a new entry is created in the session management table 2200, TEaddr2702 in the PADR table 2700 is set in TEaddr2201 in the session management table 2200, and the source MAC address of the received PADS packet 3102 is set in ISPaddr 2203 and session ID 3107 is set in ISP-side session ID 2204. Then, the session ID assigned by the AG 101 is set to the TE-side session ID 2202 (step 1809).
[0128]
This table is also set in MACFWD1107. Then, PADS is sent to the TE waiting for response in the PADR table 2700 (step 1810),
The entry related to the TE is deleted (step 1811).
[0129]
In the case of PADR reception (branch 2302) from the packet reception waiting state 2300, it is checked in step 2304 whether an entry relating to the connection destination ISP1 exists in the cache table 900, and if not, the received packet is discarded (step 201).
[0130]
If it exists, the PADR table 2700 is set based on the information (step 1806).
[0131]
ISP1 indicated in the received PADR packet is set in ServiceName 2701, the source MAC address is set in TEaddr 2702, and for example, several seconds is set in PADS waiting time 2703. Then, PADR is transmitted to ISP1 (step 1807).
[0132]
In the case of PPP frame reception (branch 2400) from the state of waiting for packet reception 2300, change the destination MAC address 3101, source MAC address 3102, and session ID 3107 of the packet based on the session management table 2200 in MACFWD 1107, then the address table A packet is transmitted to the line with reference to 1000 (step 2402).
[0133]
In the case of PADT reception (branch 2401) from the state of waiting for packet reception 2300, referring to the session management table 2200 in PROC 1104, the packet destination MAC address 3101, source MAC address 3102 and session ID 3107 are changed and transmitted ( Step 2403).
[0134]
Thereafter, the entry of the target session is deleted from the session management table 2200 existing in each of the PROC 1104 and the MACFWD 1107 (2404).
[0135]
(Example 1-2-2)
In the present embodiment, the processing of the AG 101 that performs the sequence of FIGS. 13 and 17 with the period activation as a trigger in the embodiment 1-2 will be described. FIG. 20 shows the processing flow. However, only the necessary part is shown in addition to the processing of FIG. When activation starts from the state of cyclic activation waiting 2500, a PADO (PPPoE Active Discovery Offer) waiting time 2603 in a PADI (PPPoE Active Discovery Initiation) table 2600 is subtracted (step 2501).
[0136]
As a result, entries that are no longer positive are deleted from the table (step 2502).
[0137]
Similarly for the PADR (PPPoE Active Discovery Request) table 2700, the PADS (PPPoE Active Discovery Session-confirmation) waiting time 2703 is subtracted (step 2503).
The entry whose PADS waiting time is no longer positive is deleted (step 2504).
[0138]
(Example 2)
In this embodiment, a PPPoE session is established between the TE 100 and the ISPGW 102, and PPPoA is used as a tunneling protocol between the AG 101 and the ISPGW 102 instead of L2TP. Figure 2 (c) shows the protocol stack. In this case, the lower layer of PPP is ATM.
[0139]
In addition, ISPGW102 supports PPPoA.
[0140]
Compared to the case where the interface of AG101 and ISPGW102 in Fig. 2 (a) is not IPoverEther but IPoverATM, the protocol above the ATM layer is IP, UDP, L2TP, PPP in Fig. 2 (a), In FIG. 2 (c), only PPP is used. This indicates that the protocol processing in AG101 and ISPGW102 is lighter than in FIG. 2 (a).
[0141]
FIG. 21 shows a message sequence of the embodiment when AG 101 communicates with TE100 by PPPoE and communicates with ISP1 (102) by PPPoA.
[0142]
When TE 100 transmits PADI 103 to AG 101, AG 101 refers to the ISP table.
[0143]
FIG. 22 shows the ISP table. The ISP table 3000 is held by both the PROC 1104 and the MACFWD 1107, and the PROC 1104 is used to manage the availability of VCs for each ISP to which the AG 101 is connected in advance through an ATM line. Further, the MACFWD 1107 is used for processing to which VC the PPP frame in the packet received from the TE in the PPPoE session should be transferred, or vice versa.
[0144]
The table shows identification information ServiceName3001 of connection destination ISP, physical port 3002, VPI / VCI (Virtual Path Identifier / Virtual Channel Identifier) 3003 used for connection, TEaddr3004 and session ID 3005 as PPPoE session information using the VC, user using session The name is 3006. Among these, ServiceName3001, physical port 3002, and VPI / VCI3003 are set when the ATM line is set.
[0145]
When one VC corresponds to one PPPoE session and TE100 connects to AG101, TEaddr 3004, session ID 3005, and user name 3006 are set in the table. Whether each VC is in use is identified based on whether the value of TEaddr3004 is other than 0, for example. The user name 3006 can be recognized by the AG 101 monitoring a PPP control frame transmitted / received between the TE 100 and the ISP 1 (102) during the PPP negotiation, and an example thereof will be described later.
[0146]
In FIG. 21, upon receiving the PADI 103, the AG 101 checks whether there is a free space in the VC connected to the designated ISP with reference to FIG. 22 (step 2800).
[0147]
If there is no space, the received packet is discarded (step 2801).
[0148]
If there is an empty VC, a connection request from TE100 can be accepted, and PADO1803 in which AG101 is set as the transmission source address is transmitted to TE100. Upon receiving PADO1803, TE100 transmits PADR1805 to AG101. AG101 searches ISP table 3000 again (step 2802)
If there is no free VC, the packet is discarded (step 2803).
[0149]
If there is a free VC, the TEaddr 3004 and session ID 3005 are registered for the entry of the VC selected in the ISP table 3000 (step 2804).
[0150]
After that, AG101 transmits PADS1810 to TE100. When TE 100 receives PADS 1810, PPP negotiation 112 is performed with ISP 1 (102), and IP packet communication 113 is enabled.
[0151]
The cutting sequence from TE100 will be described. When TE100 transmits PADT2000 to AG101, AG101 searches ISP table 3000 using session ID 3107 set in PADT as a key, and returns the VC to an empty state by deleting the corresponding entry.
[0152]
FIG. 23 is a processing flow of the AG 101 for realizing the sequence of FIG. This processing is performed by PROC 1104 and MACFWD 1107 in FIG. From the packet reception waiting state 4000, PADI reception (branch 4001), PADR reception (branch 4002), PADT reception (branch 4004) are processed by PROC1104, and PPP frames, that is, reception other than PPPoE control packets (branch 4003) are performed by MACFWD1107. To process.
[0153]
First, in the case of PADI reception (branch 4001), the ISP table 3000 is searched to check whether there is a vacancy in the VC for the ISP that requested the connection (step 2800).
[0154]
If there is a free VC, PADO is transmitted to TE (step 1803).
[0155]
PROC 1104 transfers the packet to MACFWD 1107 and sends it to the line based on address table 1000. If there is no space in step 2800, the received packet is discarded (2801).
[0156]
In the case of PADR reception (branch 4002), the ISP table 3000 is searched in step 2802 as in step 2800. If there is a free VC, the session ID 3005 assigned by the AG 101 and the TEaddr 3004 are registered in the ISP table 3000. Registration is also performed for the table held by the MACFWD 1107 (step 2804).
[0157]
And PADS is transmitted with respect to TE. PROC 1104 transfers the packet to MACFWD 1107, and MACFWD 1107 sends the packet to the line based on address table 1000 (step 1810).
[0158]
If there is no free VC in step 2802, the received packet is discarded (step 2803).
[0159]
In the case of PADT reception (branch 4004), the session information specified by the session ID 3107 in the packet is deleted from the ISP table 3000, and the VC used so far is made free. Deletion is also performed on the table held by MACFWD 1107 (step 2900).
[0160]
In the case of PPP frame reception (branch 4003), PPP frame encapsulation / decapsulation processing is performed with reference to the ISP table 3000 held by the MACFWD 1107 to realize PPP communication between TE100 and ISP1 (102) (step 4005).
[0161]
(Example 3)
In this embodiment, a user authentication sequence of a session is shown in the PPP negotiation performed between the TE 100 and the ISP 1 (102).
[0162]
FIG. 24 is a diagram for explaining in detail the phase of PPP negotiation in each embodiment of FIG. 6, FIG. 13, or FIG.
[0163]
First, TE100 and ISP1 (102) perform LCP negotiation 3300, which is a sublayer of PPP.
[0164]
Thereafter, ISP1 (102) transmits a CHAP (Challenge Handshake Authentication Protocol) Challenge message 3301 having an authentication random number for user authentication to TE100.
[0165]
The TE 100 sets the calculation result performed on the user name and the random number in the CHAP Response message 3302, and transmits it to the ISP 1 (102) via the AG 101.
[0166]
When the AG 101 recognizes the message, it acquires the user name, and the user name 3904 (in the case of Example 1-1 shown in FIG. 6) in the session user information table 3900 (FIG. 25) or the session management table 2200 (FIG. 16). The user name 2205 (in the case of the embodiment 1-2 shown in FIG. 13) or the user name 3006 (in the case of the embodiment 2 shown in FIG. 21) of the ISP table 3000 (FIG. 22) is registered (step 3303).
[0167]
Note that the source MAC address 3102, the session ID 3107, and the destination MAC address 3101 of the PPPoE packet encapsulating the CHAP Response message 3302 are set in the TEaddr3901, session ID 3902, and ISPaddr 3903 of the session user information table 3900, respectively. This table is managed by DB1105 of PROC1104.
[0168]
If the authentication is successful, ISP1 (102) transmits a CHAP Success message 3304 to TE100. When the AG 101 receives this CHAP Success 3304 and the user is confirmed, the AG 101 determines that the user name set in any of the above tables is correct, and starts a unique control for each user. For example, PROC 1104 instructs MACFWD 1107 to count the statistical information of the target session (step 3305).
[0169]
When the TE 100 receives the CHAP Success 3304, the TE 100 performs the IPCP negotiation 3306, which is a PPP sublayer, and enables the IP packet communication 113. On the other hand, when terminating the PPP session, that is, when the LCP Term-req (LCP Terminate-Request) message 3308 is transmitted / received between the TE100-ISP1 (102), the AG 101 recognizes this message and terminates the user-specific control ( Step 3309).
[0170]
The ISP 1 (102) that has received the LCP Term-req 3308 transmits an LCP Term-ack 3310 to the TE 100, and proceeds to the PPPoE session disconnection phase.
[0171]
In step 3309, a detailed communication amount for each user can be acquired. For example, the number of transmitted frames and the number of received frames are read from MACFWD 1107, and transmitted to CTL 1109 together with the communication time and user name measured by PROC 1104 itself. The CTL 1109 registers these information in the internal DB 1110 or the DB 3500 outside the AG 101. In this way, a detailed communication amount for each user can be acquired and used for billing and the like.
[0172]
As a specific example of the unique control for each user, there is statistical information acquisition. FIG. 28 shows a statistical information table. The statistical information table 3700 is managed by the CTL 1109 in FIG. 3 or the DB 3500 outside the AG 101 shown in FIG. This table includes information registration time 3701, user name 3702, user communication time 3703, transmission frame number 3704, and reception frame number 3705.
[0173]
In the present embodiment, CHAP is shown as an example of the authentication protocol, but PAP (PPP Authentication Protocol) can be similarly performed. For identification of these CHAP / PAP messages, CHAP / PAP can be identified by the protocol 3111 in the PPP frame format 3110, and Challenge / Response / Success can be identified by the code 3112, for example, CHAP.
[0174]
Another specific example of control unique to each user is control of packet transfer priority. FIG. 26 shows a priority table.
[0175]
The priority table 3600 stores priority levels assigned in advance for each user, and is held in the DB 1110 in the CTL 1109 in FIG. 3 or held in the DB 3500 outside the AG 101 shown in FIG. When AG 101 receives CHAP Success 3304 and the user is confirmed, PROC 1104 transmits the user name to CTL 1109. The CTL 1109 searches the priority table 3600 in the internal DB 1110 or the DB 3500 outside the AG 101, specifies the priority level 3602 corresponding to the user name 3601, and transmits it to the PROC 1104. PROC 1104 issues an instruction to the queue control of MACFWD 1107. By doing so, packets transmitted and received by a user with a high priority level can be preferentially transferred in the MACFWD.
[0176]
FIG. 29 is a processing flow for realizing the sequence of FIG. In the case of PPP frame reception (branch 3401) from the state of waiting for packet reception 3400, the MACFWD 1107 performs packet transfer processing (step 3403),
When the PPP frame contents are CHAP Response / PAP Auth Req (PAP Authenticate-Request) reception (branch 3404) and CHAPSuccess / PAP Auth Ack reception (branch 3405), the PPPoE packet is transferred to PROC 1104. In the case of CHAP Response / PAP Auth Req reception (branch 3404), the user name is acquired from the contents of the PPP frame, and the user name 3904 (in the case of the embodiment in FIG. 6) in the session user information table (FIG. 25) or the session management table The user name 2205 of 2200 (in the case of the embodiment of FIG. 13) or the user name 3006 of the ISP table 3000 (in the case of the embodiment of FIG. 21) is registered (3303). In the case of CHAP Success / PAP Auth Ack reception (branch 3405), the user information DB is searched with respect to the CTL 1109 according to the control content (step 3406), and unique control for each user is started (step 3407).
[0177]
If PADT reception (branch 3402) from the state of waiting for packet reception 3400, packet transfer is performed by MACFWD1107 (step 3403)
The PROC 1104 executes user-specific control end processing (step 3309).
[0178]
According to the present embodiment, since the user of the PPP session can be recognized, there is an effect that a service for each user can be provided.
[0179]
As the service, there is an effect that a packet of a specific user can be preferentially transferred. Further, since traffic information for each user can be acquired, there is an effect that it can be used for fine accounting control.
[0180]
(Example 4)
An embodiment will be described in which loads between gateway devices are averaged when a plurality of gateway devices exist in the same ISP.
[0181]
FIG. 30 shows an extended cache table in which the cache table 900 is extended in AG 101 to manage the traffic volume of each of a plurality of gateway devices of the same ISP. The extended cache table 3800 has a configuration in which unit time traffic 3806 is added to the cache table 900.
[0182]
At the timing of step 109 for registering the cache table of FIG. 6 or FIG. 10, the PROC 1104 instructs the MACFWD 1107 to measure the traffic for each MACaddr 3802, periodically reads the information, and sets and updates the unit time traffic 3806. Using this information, if there are multiple ISP MAC address candidates to be notified to TE100 in step 104 of FIG. 9, the smallest unit time traffic 3806 is set as the source address of the PADO packet and set to TE100. Notice. As a result, traffic can be averaged between gateway devices of the same ISP, so the number of users that can be connected to the ISP at the same time can be increased, and the ISP as a whole can accommodate users efficiently. .
[0183]
(Example 5)
As described above, by applying each of the above-described embodiments, it is possible to connect to any of the IPv4 network and the IPv6 network without changing the existing access network device as described below.
[0184]
If the existing access network device AG1300 supports IPv4 PPP and does not support IPv6 PPP, it is necessary to change AG1300 to realize branching from the IPv4 network to the IPv6 network.
[0185]
Therefore, as shown in FIG. 31, an AG 101 based on the above-described embodiment is added between existing facilities communicating with PPPoE, for example, between DSLAM 1202-AG 1300. Since AG101 can be connected to both the DSLAM1202 and the existing AG1300 using the PPPoE interface, the AG101 can be added without changing the DSLAM1202 and the existing AG1300.
[0186]
【The invention's effect】
According to the present invention, the processing load related to tunneling from the access server to the ISP network is reduced, the packet transfer delay can be reduced, and the packet transfer rate can be increased.
[Brief description of the drawings]
FIG. 1 is a network configuration diagram to which an access network apparatus of the present invention is applied.
FIG. 2 is a diagram illustrating a conventional network and a protocol stack according to each embodiment.
FIG. 3 is a configuration diagram of an access network device.
FIG. 4 is a cache table for managing an ISP MAC address in an embodiment in which an access network apparatus operates as a bridge.
FIG. 5 is a MAC address table of an embodiment in which an access network device operates as a PPPoE bridge.
FIG. 6 is a sequence in a case where the access network apparatus does not cache the MAC address of the connection destination ISP when the terminal connects to the ISP in the embodiment in which the access network apparatus operates as a bridge.
FIG. 7 is a format of a PPPoE packet.
FIG. 8 is a PPPoE TAG format.
FIG. 9 is a sequence in a case where the access network apparatus is inquiring about the MAC address of the connection destination ISP when the terminal connects to the ISP in the embodiment in which the access network apparatus operates as a bridge.
FIG. 10 is a sequence for inquiring about an ISP MAC address when the access network apparatus is activated in an embodiment in which the access network apparatus operates as a bridge;
FIG. 11 is a processing flow of packet reception activation according to an embodiment in which the access network device operates as a bridge.
FIG. 12 is a processing flow of periodic activation according to an embodiment in which the access network device operates as a bridge.
FIG. 13 shows an embodiment in which the access network device has MAC addresses on both sides of the TE-side interface and the ISP-side interface and always terminates the MAC frame, and the access network device is connected when the terminal connects to the ISP. This is a sequence when the MAC address of the destination ISP is not cached.
FIG. 14 is a PADI table for managing PADI reception from a TE according to an embodiment in which an access network apparatus has MAC addresses on both sides of a TE side interface and an ISP side interface and always terminates a MAC frame.
FIG. 15 is a PADR table for managing PADR reception from a TE in an embodiment in which an access network device has MAC addresses on both sides of a TE side interface and an ISP side interface and always terminates a MAC frame.
FIG. 16 is a session management table of an embodiment when the access network device has MAC addresses on both sides of the TE side interface and the ISP side interface and always terminates the MAC frame.
FIG. 17 shows an embodiment in which the access network device has MAC addresses on both sides of the TE-side interface and the ISP-side interface and always terminates the MAC frame, and the access network device is connected when the terminal connects to the ISP. This is a sequence when the MAC address of the destination ISP is cached.
FIG. 18 is a processing flow of packet reception activation in an embodiment in which an access network apparatus has MAC addresses on both sides of a TE side interface and an ISP side interface and always terminates a MAC frame.
FIG. 19 is a processing flow of packet reception activation in an embodiment in which an access network apparatus has MAC addresses on both sides of a TE side interface and an ISP side interface and always terminates a MAC frame.
FIG. 20 is a processing flow based on periodic activation in an embodiment in which an access network apparatus has MAC addresses on both sides of a TE side interface and an ISP side interface and always terminates a MAC frame.
FIG. 21 is a connection sequence in an embodiment when the access network apparatus communicates with TE100 by PPPoE and communicates with ISP1 (102) by PPPoA.
FIG. 22 is an ISP table for managing VCs in an embodiment in which the access network apparatus communicates with TE100 using PPPoE and ISP1 (102) communicates with PPPoA.
FIG. 23 is a processing flow of an embodiment when the access network apparatus communicates with TE100 by PPPoE and communicates with ISP1 (102) by PPPoA.
FIG. 24 is a sequence of an embodiment in which a user of a session is specified in a PPP negotiation performed by the access network apparatus between the TE 100 and the ISP.
FIG. 25 is a session user information table of an embodiment in which a user of a session is specified in a PPP negotiation performed between the TE 100 and the ISP by the access network apparatus.
FIG. 26 is a priority table in the case where packet transfer priority is controlled as user-specific control in an embodiment in which a user of a session is specified in PPP negotiation between the TE 100 and the ISP performed by the access network apparatus.
FIG. 27 is a network configuration in a case where user information is managed by an external DB in an embodiment in which a user of a session is specified in a PPP negotiation performed between the TE 100 and the ISP by the access network apparatus.
FIG. 28 is a statistical information table in a case where traffic statistical information is acquired as user-specific control in an embodiment in which a user of a session is specified in a PPP negotiation performed between the TE 100 and the ISP by the access network apparatus.
FIG. 29 is a processing flow of an embodiment in which a user of a session is specified in a PPP negotiation performed between the TE 100 and the ISP by the access network apparatus.
FIG. 30 is an extended cache table for managing the traffic amount of each gateway device according to an embodiment in which the load between the gateway devices is averaged when there are a plurality of gateway devices at the same ISP to which the access network device is connected; is there.
FIG. 31 is a protocol stack when an access network device is added to an existing access network.
[Explanation of symbols]
100 ... User terminal, 101 ... Access network device, 102 ... ISP, 900 ... Cache table, 2200 ... Session management table, 2600 ... PADI table, 2700 ... PADR table, 3000 ... ISP table, 3800 ... Extended cache table

Claims (15)

Connected to a terminal via a terminal-side network, connected to a gateway device of a plurality of connection destination networks via a relay network, selected a connection destination network based on transmission information from the terminal, and the terminal and the selected An access network device that enables communication with a connected network,
A terminal-side MAC frame transmission / reception means for transmitting / receiving a MAC frame to / from the terminal;
Gateway side MAC frame transmission / reception means for performing transmission / reception of MAC frames with the gateway device of the connection destination network;
A connection destination network information storage means for associating the MAC address of the gateway device of the connection destination network with the identification information of the connection destination network;
In response to a destination MAC address inquiry for communication with the connection destination network from the terminal, means for notifying the terminal of a MAC address and communication by the terminal using the MAC address notified to the terminal Means for relaying to a gateway device. The access network device according to claim 1, wherein
The means for notifying the terminal of the MAC address transmits an answer to the MAC address inquiry to the terminal in which the gateway device is set as transmission source information. The access network device according to claim 1, wherein
The means for notifying the terminal of the MAC address is an access network apparatus configured to transmit the response to the MAC address inquiry to the terminal in which the access network apparatus is set as transmission source information. The access network device according to claim 1, further comprising:
If the identification information is not stored in the connection destination network information storage means, it issues a MAC address inquiry of the gateway device to the relay network, and the gateway device MAC to which the gateway device of the connection destination network responds An access network device comprising means for obtaining an address and storing it in the information storage means. The access network device according to claim 4, wherein
The means for notifying the terminal of the MAC address issues an inquiry about the MAC address of the gateway device that has set the terminal as transmission source information, and forwards the received response to the terminal. The access network device according to claim 4, wherein
The means for notifying the terminal of the MAC address issues an inquiry about the MAC address of the gateway device that has set the access network device as transmission source information, and returns a response from the access network device after receiving the response. Access network device. The access network device according to claim 1, wherein
A terminal-side PPPoE communication means for performing PPPoE protocol communication with the terminal;
Gateway-side PPPoE communication means for performing PPPoE protocol communication with the gateway device of the connection destination network,
An access network device comprising means for relaying a PPPoE session between the terminal and the gateway device. The access network device according to claim 1, wherein
A terminal-side PPPoE communication means for performing PPPoE protocol communication with the terminal;
Gateway-side PPPoE communication means for performing PPPoE protocol communication with the gateway device of the connection destination network,
An access network device comprising session connection management means for associating a PPPoE session between the terminals and a PPPoE session between the connection destination networks. The access network device according to claim 4,
Issued from means for notifying the MAC address to the terminal, providing a response waiting time measuring means for the MAC address inquiry of the gateway device,
The means for notifying the terminal of the MAC address, when the MAC address inquiry of the gateway device of the same connected network is further received within a predetermined time after the inquiry is issued and before the response is received, An access network device that does not issue the inquiry to the relay network in response to a MAC address inquiry. The access network device according to claim 7 or claim 8,
PPP authentication frame monitoring means for monitoring a PPP authentication frame transmitted and received between the terminal and the gateway device of the selected connection destination network;
An access network device comprising session user storage means for storing a correspondence between user information acquired by the PPP authentication frame monitoring means and a PPPoE session ID. The access network device according to claim 10, wherein
User profile management means for managing session control parameters for each user information;
An access network apparatus comprising means for performing session control based on control parameters managed by the user profile management means. The access network device according to claim 10, wherein
Control information inquiry means for inquiring session control parameters to a user profile management device that manages session control parameters for each user information connected to the access network device,
An access network apparatus comprising means for performing session control based on the inquiry result. The access network device according to claim 10, wherein
An access network device comprising statistical information management means for storing session statistical information for each user information. The access network device according to claim 10, wherein
An access network device comprising statistical information transfer means for transferring statistical information to statistical information management means for storing session statistical information for each user information connected to the access network device. The access network device according to any one of claims 1 to 14,
Traffic volume measuring means for measuring the traffic volume to each of the plurality of gateway devices provided in the connection destination network;
Recognizing the plurality of gateway devices as a group, and providing gateway group management means for managing the amount of each traffic based on the measurement,
An access network device comprising means for selecting a gateway device based on the managed traffic volume among the gateway devices in the group in response to a connection request to the connection destination network.

Images