WO2016121293A1 - ネットワーク中継装置、ゲートウェイ冗長化システム、プログラム、および冗長化方法 - Google Patents
ネットワーク中継装置、ゲートウェイ冗長化システム、プログラム、および冗長化方法 Download PDFInfo
- Publication number
- WO2016121293A1 WO2016121293A1 PCT/JP2016/000003 JP2016000003W WO2016121293A1 WO 2016121293 A1 WO2016121293 A1 WO 2016121293A1 JP 2016000003 W JP2016000003 W JP 2016000003W WO 2016121293 A1 WO2016121293 A1 WO 2016121293A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- subscriber terminal
- subscriber
- status
- network relay
- relay device
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/22—Alternate routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/15—Interconnection of switching modules
Definitions
- the present invention relates to a gateway redundancy system in which a network relay device serving as a gateway for connecting an access network and another network is operated in a redundant configuration.
- multiple gateway devices are operated with redundancy.
- an architecture (Active-Standby method) is often adopted in which one gateway device is used as an active system, the other gateway device is used as a standby system, and standby system resources are kept in a standby state.
- an architecture (Active-Active method) in which two gateway devices are associated with each other to make the active system and the standby system interdependent, and both gateway devices are operated as the active system.
- the Active-Active method has better load distribution characteristics than the Active-Standby method.
- Patent Document 1 Related techniques are described in Patent Document 1 and Patent Document 2.
- elemental technologies used in the network system are described in Non-Patent Document 1 and Non-Patent Document 2, for example.
- Patent Document 1 describes a packet transfer system that relays between a subscriber terminal and the Internet.
- the packet transfer system has a structure in which an access network and a relay network are connected by a gateway device as an architecture for relaying packet communication between an arbitrary subscriber terminal and the Internet. Also, in this network architecture, two gateway devices with redundant connections between the access network and the relay network are in charge.
- Patent Document 2 discloses a mechanism in which a gateway load distribution device is provided in an access network as a mechanism for distributing a load of a subscriber terminal group to a plurality of gateway devices in a network architecture similar to that of Patent Document 1.
- Non-Patent Document 1 is RFC (Request for Comments) that specifies VRRP (Virtual Router Redundancy Protocol) described as an example of redundant protocol in the embodiment.
- VRRP Virtual Router Redundancy Protocol
- Non-Patent Document 2 is an RFC that prescribes IPv6 RA (Router Advertisement) described as an example of IP Prefix notification (IP Prefix Advertisement) in the embodiment.
- IPv6 RA Router Advertisement
- IP Prefix Advertisement IP Prefix Advertisement
- the Active-Standby method has been generally adopted. If the Active-Active method is adopted for the redundancy of the gateway device, the number of subscriber terminals and the amount of communication can be integrated together with the redundancy, which is desirable from the viewpoint of device resource utilization efficiency.
- L2 Layer 2
- This network architecture will be described with reference to FIG.
- This example is an example in which multiple BRAS (BRoadband Access Server) devices (network relay devices) are operated in an active-active redundant configuration in consideration of load balancing.
- Each BRAS device operates as a gateway that relays between the access network and the core network.
- the CPE starts over from re-accepting the AAA server (Authentication / Authorization / Accounting Server) through the newly active BRAS device.
- the CPE resumes communication after receiving the IP-prefix (IP-address) issued by the BRAS device that has been switched to the active system upon approval of the AAA server.
- IP-prefix IP-address
- devices that manage IP Address / Prefix such as BRAS, Router, DHCP Server, etc., determine the IP Address / Prefix assigned to each subscriber terminal, and notify the IP address / Prefix to the subscriber terminal through Protocol. It is to be.
- both BRAS devices that are in a redundant configuration relationship are in a state of notifying or advertising the setting indicating the working system and the value of the same priority. In this case, it is not possible to determine which BRAS device is the correct (to be used) gateway from another terminal or device.
- the advertisement means that the route information possessed by the router or the like is propagated to other routers or the like connected to itself using the routing protocol.
- the behavior of the core router may deviate from the assumed operation.
- the CPE may not be able to communicate normally with Core Network.
- the communication speed is reduced or extra network resources are consumed.
- the current network system does not have an algorithm for early recovery from this failure.
- Patent Document 1 and Patent Document 2 do not describe a solution technique.
- the inventor has a problem that may arise from several technical specifications of the current mechanism, assuming an architecture in which multiple network relay devices having a redundant configuration distribute and accommodate subscriber terminals in an active-active system. We examined a gateway device to prevent this.
- the present invention has been made based on the above point of view, and provides a gateway redundancy system that can further improve the communication continuity between a subscriber terminal and a relay destination network.
- the network relay device has a redundancy status indicating whether the own device operates as an active system or a standby system for each subscriber terminal or each subscriber terminal group, and uses for each subscriber terminal.
- a gateway redundancy system maintains an internal status that defines an operation for relay in a plurality of network relay devices that relay an access network and a relay destination network as gateways, respectively, in a storage unit.
- the network relay device has, as the internal status, a list of a redundancy status indicating whether the own device operates as an active system or a standby system for each subscriber terminal or each subscriber terminal group and used address information for each subscriber terminal. Is recorded in the storage unit sequentially, and a message including the predetermined status is sequentially notified / advertised to the notification destination at a predetermined timing, and the communication that has reached its own device is monitored, and another network relay device The used address information paid out to the subscriber terminal is also sequentially recorded in the storage unit. , Characterized in that relays communication between networks.
- a program includes a redundancy status indicating whether the own apparatus operates as an active system or a standby system, for each subscriber terminal or each subscriber terminal group, the processor of the network relay device, A logical storage unit that records a subscriber status indicating a list of used address information for each subscriber terminal; and a communication between another network relay device adopting a redundant configuration and a subscriber terminal group;
- the used address information issued to the subscriber terminal by the network relay device is recorded as a part of the subscriber status in the physical storage unit that handles the logical storage unit, and a predetermined status is sequentially included in the notification destination at a predetermined timing. It is characterized by operating as a management unit that notifies / advertises a message.
- the network relay device that relays between the access network and the relay destination network is configured such that the own device is an active or standby device for each subscriber terminal or each subscriber terminal group.
- a redundant status indicating which system is to be operated and a subscriber status indicating a list of used address information for each subscriber terminal are sequentially managed in a storage unit, and a predetermined status is included in a sequential notification destination at a predetermined timing
- the message is notified / advertised, and the network relay device monitors the communication between the other network relay device having a redundant configuration and the subscriber terminal group, and the used address issued by the other network relay device to the subscriber terminal.
- Information is recorded and managed in the storage unit as part of the subscriber status.
- a gateway redundancy system that can further improve communication continuity between a subscriber terminal and a relay destination network.
- FIG. 4 is a flowchart illustrating an operation for performing initial setting and updating of redundant information using a redundant protocol of the BRAS device 100. It is explanatory drawing which illustrated the change of the redundant information 142,242 updated by exchange of a redundant Protocol message. 4 is a flowchart showing an operation of advertising IP Pool Prefix of a terminal accommodated by the BRAS device 100 to a core network using a routing protocol.
- 3 is a flowchart showing an operation of notifying a subscriber of IP Prefix when accommodating a subscriber of the BRAS device 100.
- 4 is a flowchart showing an operation of snooping an IP Prefix message notification of the BRAS device 100. It is explanatory drawing which illustrated the change of the subscriber information 122,222 updated by exchange of an IP-Prefix message.
- 4 is a flowchart showing an operation of switching to a subscriber terminal accommodation location due to a failure of the access network of the BRAS device 100. It is explanatory drawing which illustrated the change of the subscriber information 122,222 updated by switching of an accommodation destination.
- FIG. 5 is a flowchart illustrating an operation of advertising routing information having a priority that is adjusted by the BRAS device 200; It is explanatory drawing which illustrated the change of the redundant information 142,242 updated by the exchange of a Route information message, and IP-route information 152,252. It is explanatory drawing which illustrated the network architecture of the L2 frame relay system which has a gateway redundancy structure.
- FIG. 1 is a configuration diagram illustrating a network relay device according to an embodiment.
- the network relay device 10 operates as a gateway that relays communication between an access network and a relay destination network (for example, a mobile core network or an ISP (Internet Service Provider) network).
- the network relay device 10 holds various internal statuses, and determines its own operation such as whether to operate as a working system or a standby system for a predetermined subscriber terminal according to the internal status. .
- status and information have meanings as containers as well as so-called information.
- the network relay device 10 provides a redundant configuration of a plurality of gateways to each subscriber terminal in cooperation with other network relay devices (not shown).
- other network relay devices not shown.
- the same arrangement as that of FIG. 16 is adopted as the network structure, and other network relay devices are described as autonomously performing the same configuration and operation as the network relay device 10.
- the network relay device 10 sequentially executes the storage unit 11 that stores the internal status, the recording of the internal status in the storage unit 11, and the notification / advertisement to the sequential notification destination including the predetermined status at a predetermined timing.
- the management part 12 is included. Note that description of communication means (physical input / output unit, logical communication interface, relay mechanism, etc.) of the existing configuration included in the network relay device 10 is simplified or omitted.
- the management unit 12 records and manages the redundancy status and the subscriber status as an internal status. Further, in the present embodiment, the storage unit 11 records and manages the address group that can be paid out by the device as IP Pool information and information indicating the communication route as IP Route information (communication route information).
- redundancy status information indicating whether the own apparatus operates as an active system or a standby system is recorded for each subscriber terminal or each subscriber terminal group.
- IPv6 IP prefix
- IPv4 IP address
- IPv4 IP address
- the subscriber terminal group may be associated with the IP pool number to which the used address information belongs for each group. Further, by using the subscriber status, a plurality of Tag information used by the subscriber terminal group and the subscriber terminal may be used in association with the used address information.
- the management unit 12 appropriately records and manages various information including the redundancy status and the subscriber status in the storage unit 11, and notifies each notification to the notification destination in response to the request or autonomously. For example, when receiving an RS (Router Solicitation) from a subscriber terminal that desires an IPv6 address, the management unit 12 issues an IP address and notifies the access network of the information (Advertisement).
- RS Raster Solicitation
- the management unit 12 further monitors the port of the own device, acquires the used address information that the other network relay device has issued to the subscriber terminal from the communication between the other network relay device and the subscriber terminal, and Record information in subscriber status.
- the management unit 12 monitors the port of the own device, acquires the used address information that the other network relay device has issued to the subscriber terminal from the communication between the other network relay device and the subscriber terminal, and Record information in subscriber status.
- the management unit 12 manages a plurality of IP pools that are the same as those of other network relay apparatuses that have a redundant configuration in advance, and uses an IP pool that is not used for the operation of the active system of the other network relay apparatuses. It should be used for the operation of For this reason, it is desirable that the management unit 12 designates or allocates a plurality of IP pools in advance.
- the management unit 12 monitors the notification (Advertisement) for the subscriber terminal corresponding to the standby system with the redundancy status sent out by another network relay device adopting a redundant configuration, and is paid out to this subscriber terminal. Hope to make it work to snoop on the address. Note that snoop means that a communication message of a certain protocol is acquired by a device outside the destination existing on the network and the information of the propagation content is used.
- the used address information (group) of the subscriber terminal (group) is not collected more than necessary from the notified message (group).
- the management unit 12 monitors the communication waiting time and the communication success amount for each subscriber terminal or each subscriber terminal group recorded in the internal status, and records it as a part of the internal status.
- the internal status may include the communication waiting time and the communication success amount as communication state information.
- the management unit 12 can use this communication state information to give a difference in the priority of the communication route used by each subscriber terminal or subscriber terminal group between itself and another network relay device.
- the network relay device 10 can advertise the communication path information including this priority to a predetermined destination.
- the communication paths provided by the own device and the other network relay device are set to the same setting as viewed from the other device. Can be prevented.
- Redundant gateways that can further improve communication continuity between subscriber terminals and relay destination networks by autonomously executing network relay devices that distribute and accommodate subscriber terminals using the Active-Active method. You can build a system. For example, it becomes easy to continue communication and logical setting that were temporarily disconnected in the current gateway system at the time of switching between the active / standby system of an arbitrary subscriber terminal or failure / switching of a specific facility or route.
- FIG. 2 is an explanatory diagram showing a presupposed network architecture.
- the first BRAS device 100 (# 1) and the second BRAS device 200 (# 2) connect the access network and the carrier core network to each CPE ⁇ ⁇ ⁇ ⁇ A01-D01 in a redundant configuration.
- the carrier core network is connected to the Internet network.
- the first BRAS device 100 and the second BRAS device 200 each operate as a working or standby gateway device for each CPE A01-D01.
- An L2 switch 300 is interposed between the first BRAS device 100, the second BRAS device 200, and each CPE A01-D01.
- the first BRAS device 100 and the second BRAS device 200 manage the same two sets of IP pools (IP Pool 01, IP Pool 02).
- the first BRAS device 100 and the second BRAS device 200 are connected to the AAA server 400 through the Management Plane network.
- AAA server 400 requests authentication of a subscriber terminal (CPE) or the like from first and second BRAS devices 100 and 200, it returns an authentication result of the subscriber terminal.
- CPE subscriber terminal
- the AAA server 400 uses a protocol such as RADIUS (Remote Authentication, Dial, In, User, Service).
- the first BRAS device 100 and the second BRAS device 200 are connected to the core router 500 through the carrier core network.
- the core router 500 plays a role of relaying the traffic of the subscriber terminals accommodated by the first and second BRAS devices 100 and 200 to a server in the carrier (not shown) or an external network (such as the Internet or other mobile network). Take charge.
- the first and second BRAS devices 100 and 200 and the core router 500 appropriately exchange routes with each other using a routing protocol, and transfer the relayed IP packet to an appropriate destination.
- the first BRAS device 100 and the second BRAS device 200 are connected to the CPEs A01, B01, C01, and D01 through the L2 switch 300.
- Each of the CPEs A01, B01, C01, and D01 assigns a Q-in-Q C-tag (Customer tag) to the received subscriber traffic, and sends it to the access network.
- the L2 switch 300 relays the subscriber traffic with a Q-in-Q S-tag (Service tag).
- the L2 switch 300 also relays control traffic between the first BRAS device 100 and the second BRAS device 200.
- the IP pool number for each CPE A01-D01 is specified from the AAA server 400 at the time of each subscriber authentication.
- the first and second BRAS devices 100 and 200 serving as IPFE (IP Front End) select an IP prefix to be allocated from the IP Pool, and notify each CPE A01-D01 by RA (IP Prefix advertisement).
- IPFE IP Front End
- the first and second BRAS devices 100 and 200 are made redundant by VRRP in S-tag units.
- the first and second BRAS devices 100 and 200 advertise the IP pool prefix assigned to the subscribers accommodated by their own devices to the core network using a routing protocol message.
- the first and second BRAS devices 100 and 200 receive Q-in-Q frames from each CPE via the L2 switch 300 when relaying communication.
- the first and second BRAS devices 100 and 200 terminate the Q-in-Q tunnel and transfer the frame / packet from each CPE to the core network.
- FIG. 3 is a configuration diagram showing the first BRAS device 100.
- the second BRAS device 200 has a similar configuration.
- FIG. 4 is an explanatory diagram showing an example of initial setting of each setting information held by the first BRAS device 100 and the second BRAS device 200.
- Subscriber information 122 (a), IP pool information 130 (b), redundancy information 142 (c), and IP route information 152 (d) are setting information of the first BRAS device 100.
- Subscriber information 222 (e), IP pool information 230 (f), redundant information 242 (g), and IP Route information 252 (h) are setting information of the second BRAS device 200.
- the first BRAS device 100 has subscriber information 122, IP pool information 130, redundant information 142, and IP route information 152 as settings.
- IP pool information 130 and redundancy information 142 are set according to the network configuration as a pre-setting before operation.
- the first BRAS device 100 has an AAA processing unit 110 inside.
- the AAA processing unit 110 transmits a request for authentication of the CPE to the AAA server 400 with the traffic from the new CPE as a trigger. Further, when the AAA processing unit 110 receives the authentication response (including the subscriber ID, IP Pool Name, etc.) from the AAA server 400, the AAA processing unit 110 includes the information in the subscriber information 122, and specifies the IP specified by the AAA server 400.
- the Pool Name is sent to the IP prefix information management unit 120.
- the IP prefix information management unit 120 reads the IP pool information 130 and selects an IP prefix to be paid out to the subscriber from the IP pool prefix according to the IP pool name received from the AAA processing unit 110. At this time, the IP prefix information management unit 120 selects the recorded IP Prefix if there is an IP Prefix of the subscriber already recorded in the procedure described later. The IP prefix information manager 120 notifies the IP prefix information transmitter / receiver 121 of the selected IP prefix. Thus, the IP prefix information manager 120 notifies the subscriber of the notified IP prefix via the IP prefix information transmitter / receiver 121. Furthermore, the IP prefix information management unit 120 includes the IP prefix that has been paid out to the subscriber in the subscriber information 122.
- the IP prefix information management unit 120 records the recorded information if there is an already recorded IP prefix. Based on the above, IP ⁇ ⁇ Prefix may be issued immediately. For example, the approval lifetime may be recorded in the subscriber information 122, or the approval process with the AAA server 400 may be omitted or executed in parallel or post-reported according to the reliability of the CPE.
- the subscriber ID and IP Pool name recorded in the subscriber information 122 may be periodically acquired from the opposite device (BRAS device 200) or the AAA server 400 with an arbitrary message.
- the redundant protocol management unit 140 reads the setting of the redundant information 142 as appropriate, and instructs the redundant protocol transmission / reception unit 141 as appropriate for information to be described in the redundant protocol message.
- the redundant protocol transmission / reception unit 141 transmits / receives a redundant protocol message such as VRRP (Virtual Router Redundancy Protocol) as appropriate.
- This redundant protocol message is encapsulated with the S-tag set in the redundancy information 142 and transmitted, and is received by the redundant protocol transmission / reception unit 241 of the opposing second BRAS device 200 forming a redundant configuration.
- the redundant protocol message transmitted by the redundant protocol transmission / reception unit 241 of the second BRAS device 200 is also encapsulated and transmitted with the S-tag set in the redundancy information 242 and the redundant protocol transmission / reception unit of the first BRAS device 100 is transmitted. Received at 141.
- the redundant protocol manager 140 After exchanging redundant protocol messages between the first BRAS device 100 and the second BRAS device 200, the redundant protocol manager 140 uses the first BRAS device 100 and the second BRAS device 200 for each S-tag. To determine the redundant Master (active) / Backup (backup). The redundant protocol management unit 140 includes the status indicating Master / Backup in the redundant information 142.
- the IP route information management unit 150 constantly monitors the status of the redundant information 142 and the IP pool information 130.
- the IP / Route information management unit 150 checks the update status and determines whether or not the IP / Pool / prefix advertisement is necessary when the information is updated.
- a change in IP Pool prefix related to a terminal or a terminal group included as a master state of the redundant information 142 requires advertisement to a predetermined destination.
- the IP route information management unit 150 notifies the IP route information transmitting / receiving unit 151 of the change and advertises new route information to the core router 500.
- the IP Route information management unit 150 adds the metric of the Route information to be advertised corresponding to the value if the idle time recorded as the communication status information corresponding to the target IP Pool prefix is not 0, the IP Route information management unit 150 adds the metric of the Route information to be advertised corresponding to the value .
- items of communication status information are provided in the redundant information, and the values are linked between the statuses using the redundant group as a key.
- the CPE is currently communicating with the device.
- the route information on the side is a smaller metric than the other. As a result, routing in the core network is maintained in a normal state, and communication of CPE (subscriber) is not interrupted.
- the Access communication monitoring unit 160 monitors the communication of the subscriber terminal or the subscriber group at the access interface for the redundant information S-tag in the master state. When no communication continues, the Access communication monitoring unit 160 updates the idle time of the redundancy information 142 every certain period (for example, 60 seconds).
- FIG. 5 is a flowchart showing an operation for initializing and updating redundant information using the redundant protocol of the first BRAS device 100.
- the second BRAS device 200 operates in the same manner.
- the redundancy protocol management unit 140 reads the redundancy setting included in the redundancy information 142 (S101).
- the redundant protocol transmission / reception unit 141 transmits a redundant protocol message for each S-tag indicated by the redundant protocol management unit 140.
- the redundant protocol transmission / reception unit 141 appropriately notifies the redundant protocol management unit 140 of the S-tag and the state (information indicating whether it is master or backup).
- the redundant protocol management unit 140 includes the information notified from the redundant protocol transmitting / receiving unit 141 in the redundant information 142 (S103).
- FIG. 6 shows an example of changes in the redundant information 142 and 242 updated by exchanging redundant Protocol messages between the first and second BRAS devices 100 and 200. In this manner, the redundant information is updated as appropriate in the BRAS devices 100 and 200.
- FIG. 7 is a flowchart showing an operation of advertising the IP Pool Prefix of the terminal accommodated in the first BRAS device 100 to the core network using the routing protocol.
- the IP route information management unit 150 refers to the IP pool information 130 and the redundancy information 142, and extracts an IP pool prefix having a redundant group in the master state (S201).
- An IP Pool Prefix in the Master state is a set of used address information assigned to the CPE (group) accommodated in the own device.
- the IP Route information management unit 150 includes the IP ⁇ Pool Prefix information in the IP Route information 152 and instructs the IP Route information transmitting / receiving unit 151 to transmit a Routing protocol message including the contents (S202). At this time, the default value that has been set may be used as the metric indicating the priority of the IP route information.
- the IP route information transmission / reception unit 151 advertises the IP route information notified from the IP route information management unit 150 to the core interface.
- the IP route information transmission / reception unit 151 notifies the IP route information management unit 150 of the contents of the routing protocol message received from the core interface.
- the IP route information management unit 150 includes the route information notified from the IP route information transmission / reception unit 151 in the IP route information 152 (S203).
- FIG. 8 shows an example of changes in the IP-route information 152 and 252 updated by transmission and reception of routing protocol messages in the first and second BRAS devices 100 and 200.
- the IP / Route information is appropriately updated in the first and second BRAS devices 100 and 200.
- FIG. 9 is a flowchart showing an operation of notifying the subscriber of IP Prefix when the subscriber is accommodated.
- the AAA processing unit 110 When receiving the first communication from the subscriber, the AAA processing unit 110 requests the AAA server 400 to authenticate the subscriber (S301).
- the AAA server 400 performs subscriber authentication and responds with an authentication result.
- the authentication result includes information on the subscriber such as the subscriber ID and the IP Pool Name used by the subscriber.
- the AAA processing unit 110 receives the authentication result from the AAA server 400 and includes the subscriber information included in the authentication result in the subscriber information 122 (S302). Further, the AAA processing unit 110 notifies the IP prefix information management unit 120 of the subscriber's IP Pool Name. The IP prefix information management unit 120 may read the subscriber information 122.
- the IP prefix information management unit 120 identifies the IP pool prefix corresponding to the notified IP pool name by referring to the IP pool information 130 (S303).
- the IP prefix information management unit 120 determines the IP prefix to be paid out to the subscriber from the identified IP pool prefix (S304).
- the IP prefix information management unit 120 notifies the IP prefix transmitting / receiving unit 121 of the determined IP prefix and additional information (S-tag / C-tag information read from the subscriber information 122) and transmits an IP prefix message (advertisement). ) Is instructed (S305).
- the IP Prefix transmission / reception unit 121 transmits an IP Prefix message to the access network based on the notified information. Note that this IP Prefix notification is encapsulated with S-tag and C-tag, and reaches the target subscriber's CPE via the L2 switch 300.
- Advertised IP Prefix can use IPv6 RA (Router Advertisement) mechanism, for example.
- FIG. 10 is a flowchart showing a process in which the first BRAS device 100 snoops the notification of the IP Prefix message of the opposite device (second BRAS device 200).
- the second BRAS device 200 notifies the IP PE prefix to the CPE accommodated at an arbitrary timing.
- This advertisement processing corresponds to the operation of the first BRAS device 100 described with reference to FIG.
- the IP Prefix notified by the second BRAS device 200 reaches the first BRAS device 100 via the L2 switch 300.
- the first BRAS device 100 receives the IP Prefix notified by the second BRAS device 200.
- the IP prefix information management unit 120 may notify the IP prefix transmission / reception unit 121 of the snooping target (subscriber terminal or subscriber terminal group) in advance, or all the arrived IP prefix messages may be notified. You may manage with.
- the IP Prefix transmission / reception unit 121 notifies the IP prefix information management unit 120 of the content of the received IP Prefix message for the CPE.
- the IP prefix information management unit 120 identifies (S401) the IP prefix information and additional information (S-tag, C-tag, etc.) of the notified contents and includes them in the subscriber information 122 (S402). Maintaining this information improves communication continuity in many situations.
- FIG. 11 shows an example of changes in the subscriber information 122 and 222 updated by transmission / reception of IP200Prefix messages by the BRAS devices 100 and 200. In this way, the subscriber information is appropriately updated in the first and second BRAS devices 100 and 200.
- FIG. 12 is a flowchart showing the operation of switching to the accommodation location of the subscriber terminal due to an access network failure.
- the gateway redundancy system changes the accommodation destination of CPE C01, D01 from the second BRAS device 200 to the first BRAS device 100 as the entire redundant network.
- the redundant protocol transmission / reception unit 141 of the first BRAS device 100 does not receive the redundant protocol message from the second BRAS device 200 for the redundant group2.
- the redundant protocol management unit 140 operating autonomously switches to the active system as a standby system for the subscriber terminal or the subscriber terminal group based on the preset switching conditions. (S501).
- the switching condition is that a redundant protocol message from the second BRAS device 200 has not been received for a certain period.
- the AAA processing unit 110 requests each subscriber authentication from the AAA server 400 when receiving communication from CPE C01, D01 (newly accommodated subscriber terminals) (S502).
- the AAA processing unit 110 Upon receiving the authentication response from the AAA server 400, the AAA processing unit 110 includes the subscriber information in the subscriber information 122 (S503), and notifies the IP prefix information management unit 120 of the subscriber IP Pool name.
- the IP prefix information management unit 120 may monitor the subscriber information 122 to identify a change in subscriber information.
- the IP Pool information management unit 120 reads the IP Pool Prefix of the notified IP Pool Name from a part of the IP pool information 130, and if the corresponding subscriber information can be identified, the IP Pool information management unit 120 uses the managed IP Prefix. Select as the subscriber's IP Prefix (S504). In addition, the identification of a corresponding subscriber may be determined by matching S-tag and C-tag. Moreover, you may identify a subscriber by another method. Whether or not there is corresponding subscriber information is determined by whether or not the second BRAS device 200 has been able to snoop the used address information that was previously issued to the corresponding CPE. If the registered IP Prefix is outside the range of the IP Pool Prefix, the IP Pool information management unit 120 may perform a process of newly selecting an IP Prefix from the IP Pool Prefix.
- This operation allows CPE C01 and D01 to continue to use the same IP Prefix in the first BRAS device 100 as when accommodated in the second BRAS device 200.
- the IP prefix information management unit 120 notifies the IP prefix transmitting / receiving unit 121 of the selected IP prefix and additional information (S-tag / C-tag information included in the subscriber information 122) to transmit a message. Instruct (S505).
- the IP Prefix transmission / reception unit 121 transmits an IP Prefix message to the access network based on the notified information.
- FIG. 13 shows an example of changes in the subscriber information 122 and 222 updated by a series of operations. In this way, the subscriber information is updated in the first and second BRAS devices 100 and 200, and communication continuity is maintained.
- FIG. 14 is a flowchart showing an operation of advertising routing information having an adjusted priority. This processing operation provides a mechanism for preventing the routing information advertised from the first and second BRAS devices 100 and 200 from matching with each other during autonomous operation.
- the gateway redundancy system changes the accommodation destination of CPE C01, D01 from the second BRAS device 200 to the first BRAS device 100 as the entire redundant network.
- each component of the second BRAS device 200 will be described as performing the same operation as that of the first BRAS device 100.
- the code number of the second BRAS device 200 corresponds to the first BRAS device 100.
- the Access communication monitoring unit 260 of the second BRAS device 200 refers to the redundancy information 242 as needed, and constantly monitors the communication that can be identified by the access interface including the S-tag of the redundant group in the master state ( S601).
- the Access communication monitoring unit 260 updates the communication state of the redundant group having the corresponding S-tag included in the redundant information 242 (in this example, idle time) when there is no communication for the monitored S-tag for a certain period of time. (S602). In this example, every time 15 seconds of no-communication continues, the idle time value is included in the redundancy information 142, and no communication has passed for 360 seconds.
- the IP route information management unit 250 uses the update of the redundant information 242 as a trigger, the IP pool pre-fix included in the IP pool information 230, the status (master / backup status) and idle time value included in the redundant information 242. Is read. Then, the Route information management unit 250 updates the IP / Route information 252 (S603), and instructs the IP / Route information transmission / reception unit 251 to advertise the IP / Pool / Prefix that is the master as an advertisement target (S604).
- the IP Route information management unit 250 indicates that the CPE using the S-tag is non-communication (for identification of the own device) when the idle timeout is 1 or more.
- Add information metric In this example, metric is incremented by 1 every time 15 seconds of no-communication continues, and the priority of the communication route via the own apparatus is lowered.
- the metric may be adjusted by detecting an error detection of a predetermined amount or more and identifying the communication success rate.
- FIG. 15 shows an example of changes in the redundant information 142, 242 and the IP-route information 152, 252 updated by transmission / reception of the Route information message in the first and second BRAS devices 100, 200. In this way, the priority of the communication route is updated as appropriate in the first and second BRAS devices 100 and 200.
- the access network side communication is monitored by the BRAS device and the no-communication state is reflected in the priority of the IP-Route information.
- the normality of the communication route such as the core network becomes stronger, and the continuity of communication is improved in many situations.
- the program according to the present invention is expanded in a RAM (Random Access Memory), and each unit may be realized by operating hardware such as various processors based on the program. Further, this program may be recorded non-temporarily on a recording medium and distributed.
- the program recorded on the recording medium is read into a memory via a wired, wireless, or recording medium itself, and operates a processor or the like. Examples of the recording medium include an optical disk, a magnetic disk, a semiconductor memory device, and a hard disk.
- the processor included in the network relay device monitors the communication with the storage unit that records the redundancy status and the subscriber status based on the program developed in the RAM, and the like. It can be realized by recording the used address information issued to the subscriber terminal by the network relay device and operating as a management unit that advertises the internal status sequentially to the notification destination.
- the network relay device to which the present invention is applied can further enhance the communication continuity between the subscriber terminal and the relay destination network as a gateway redundancy system.
- [Appendix 1] Internally includes a redundancy status indicating whether the device operates as an active system or a standby system for each subscriber terminal or each subscriber terminal group, and a subscriber status indicating a list of used address information for each subscriber terminal.
- a management unit that records and sequentially notifies / advertises the internal status that has been sequentially recorded to a notification destination at a predetermined timing;
- a network relay device that relays between an access network and a relay destination network.
- the management unit monitors a message for the subscriber terminal or the subscriber terminal group notified by another network relay device adopting a redundant configuration, and a predetermined subscriber terminal indicated as a standby system in the internal status is in use.
- the used address information used by the predetermined subscriber terminal is read from the storage unit, and communication between the predetermined subscriber terminal and the relay destination network is performed by the predetermined subscriber terminal.
- the network relay device as described in the above supplementary note, which is continued with the used address information used.
- the management unit monitors communication status information for each subscriber terminal or each subscriber terminal group included in the internal status, and adjusts the priority of the communication route via the own device according to the communication status information. And advertises the communication route information to the relay destination network device.
- [Appendix 4] Uses an IP pool that collects address groups as used address information, manages a plurality of IP pools that are the same as the other network relay device adopting a redundant configuration, and is used for the operation of the active system of the other network relay device.
- the management unit updates the redundancy status, switches to the active system and receives communication from each subscriber terminal or each subscriber terminal group that relays communication, and already uses address information in the subscriber status. Is included, the use address information issued by the other network relay device to the subscriber terminal is set as the use address of the subscriber terminal in parallel with the approval of the subscriber terminal.
- a network relay device as described in the above supplementary note.
- the network relay device and the other network relay device are BRAS devices,
- the relay destination network is a core network
- the subscriber terminal is CPE (Customer Premises Equipment)
- CPE Customer Premises Equipment
- IP v6 and VRRP Virtual Router Redundancy Protocol
- Each of the storage units stores an internal status that defines an operation for relaying by a plurality of network relay devices that relay each of the access network and the relay destination network as a gateway, Individual network relay devices As the internal status, for each subscriber terminal or each subscriber terminal group, a subscriber status indicating a redundant status indicating whether the own apparatus operates as an active system or a standby system and a list of address information used for each subscriber terminal Are sequentially recorded in the storage unit, and a message including a predetermined status is sequentially notified / advertised to a notification destination at a predetermined timing, A gateway characterized by monitoring communication that has reached its own device, and relaying communication between networks while sequentially recording in the storage unit the used address information that other network relay devices have issued to subscriber terminals. Redundant system.
- Each network relay device monitors a message for the subscriber terminal or subscriber terminal group notified by another network relay device adopting a redundant configuration, and is also a predetermined subscriber terminal indicated as a standby system in the internal status. Is switched to a state in which it operates as an active system, the used address information used by the predetermined subscriber terminal is read from the storage unit, and communication between the predetermined subscriber terminal and a relay destination network is performed.
- the gateway redundancy system according to the above supplementary note, characterized in that it continues with the used address information used by the terminal.
- Each network relay device monitors the communication status information for each subscriber terminal or each subscriber terminal group included in the internal status, and the priority of the communication route via the own device according to the communication status information
- the gateway redundancy system as described in the above supplementary note, wherein communication path information is advertised to a relay destination network device by adjusting the level of the gateway.
- Each network relay device uses an IP pool in which address groups are grouped as used address information, manages a plurality of the same IP pool as the other network relay device having a redundant configuration, and uses the other network relay device.
- the gateway redundancy system as described in the above supplementary note, wherein an IP pool that is not used for the current system operation is used for the current system operation of its own device.
- Each network relay device updates the redundancy status and switches to the active system, and when it receives communication from each subscriber terminal or each subscriber terminal group that relays communication, it is already used for the subscriber status. If the address information is included, the approval of the subscriber terminal is omitted or in parallel with the approval, the used address information issued by the other network relay device to the subscriber terminal is used as the used address of the subscriber terminal.
- the gateway redundancy system according to the above supplementary note, characterized in that it is set.
- Each network relay device is a BRAS device, The relay destination network is a core network, The subscriber terminal is CPE (Customer Premises Equipment), The gateway redundancy system as described in the above supplementary note, wherein the communication path between the CPE and the core network is made redundant for each Service-tag while using IP v6 and VRRP (Virtual Router Redundancy Protocol) as communication protocols.
- CPE Customer Premises Equipment
- VRRP Virtual Router Redundancy Protocol
- Network relay device processor For each subscriber terminal or each subscriber terminal group, a redundancy status indicating whether the own device operates as a working system or a standby system, and a subscriber status indicating a list of used address information for each subscriber terminal, A logical storage section to record; A physical storage unit that monitors communication between another network relay device adopting a redundant configuration and a subscriber terminal group, and uses the logical storage unit for the used address information that the other network relay device issues to the subscriber terminal.
- the processor monitors a message for the subscriber terminal or the subscriber terminal group notified by another network relay device adopting a redundant configuration, and a predetermined subscriber terminal indicated as a backup system in the internal status is an active system. Is used, the used address information used by the predetermined subscriber terminal is read from the storage unit, and the communication between the predetermined subscriber terminal and the relay destination network is used by the predetermined subscriber terminal.
- the program according to the above supplementary note, wherein the program is operated so as to continue with the used address information.
- the processor monitors the communication status information for each subscriber terminal or each subscriber terminal group included in the internal status, and adjusts the priority of the communication route via the own device according to the communication status information. And the relay destination network device is advertised with the communication path information.
- the processor manages a plurality of the same IP pool as the other network relay device adopting a redundant configuration by using an IP pool in which an address group is collected, The program described in the above supplementary note, wherein an IP pool that is not used for the operation of the active system of the network relay device is operated so as to be used for the operation of the active system of the own device.
- the network relay device that relays between the access network and the relay destination network has, for each subscriber terminal or each subscriber terminal group, a redundancy status indicating whether the own device operates as an active system or a standby system, and for each subscriber terminal. Subscriber status indicating a list of used address information, and sequentially managing / notifying / advertising a message including a predetermined status to a notification destination at a predetermined timing in a storage unit,
- the network relay device monitors communication between another network relay device having a redundant configuration and a subscriber terminal group, and uses the address information issued by the other network relay device to the subscriber terminal in the storage unit.
- a redundancy method for a network relay device characterized in that records are managed as part of a subscriber status.
- the network relay device monitors a message for the subscriber terminal or the subscriber terminal group notified by another network relay device adopting a redundant configuration, and a predetermined subscriber terminal indicated as a backup system in the internal status.
- the used address information used by the predetermined subscriber terminal is read from the storage unit, and communication between the predetermined subscriber terminal and a relay destination network is performed.
- the network relay device redundancy method according to the above supplementary note, characterized in that the network relay device continues using the used address information used by the network.
- the network relay device monitors the communication status information for each subscriber terminal or each subscriber terminal group included in the internal status, and determines the priority of the communication route via the own device according to the communication status information.
- the network relay device redundancy method according to the above supplementary note, wherein the communication route information is advertised to the relay destination network device.
- the network relay device uses an IP pool in which an address group is gathered as used address information, manages a plurality of the same IP pool as the other network relay device adopting a redundant configuration, and The network relay device redundancy method described in the above supplementary note, wherein an IP pool that is not used for the operation of the active system is used for the operation of the active system of the own device.
- the network relay device updates the redundancy status, switches to the active system, receives communication from each subscriber terminal or each subscriber terminal group that relays communication, and already uses the address in the subscriber status. If the information is included, the approval of the subscriber terminal is omitted or in parallel with the approval, the used address information issued by the other network relay device to the subscriber terminal is set as the used address of the subscriber terminal.
- a redundancy method for a network relay device as described in the above supplementary note.
- the present invention can be applied to a general network relay device such as an L3 router as long as it is a redundant gateway. Further, the present invention may be realized by vBRAS (virtual Broadband Remote Access Server) using virtualization technology.
- vBRAS virtual Broadband Remote Access Server
- the redundant protocol is VRRP and the IP prefix advertisement is taken as an example of IPv6 RA, the message content may be notified by another protocol having the same function.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
[構成]
図2は、前提とするネットワークアーキテクチャを示した説明図である。
第1のBRAS装置100と第2のBRAS装置200と各CPE A01-D01との間は、L2スイッチ300が介在する。第1のBRAS装置100と第2のBRAS装置200は、同一の2組のIPプール(IP Pool 01, IP Pool 02)を管理している。
第1および第2のBRAS装置100,200とコアルータ500は、互いにルーティングプロトコルを用いて経路の交換を適宜実行して、中継するIPパケットを適正な宛先に転送する。
次に、図5~図15を用いて、ゲートウェイ冗長化システムの各種動作をテーブル及びフローチャートを示して説明する。
冗長Protocolメッセージの送受信状況により状態変化が発生した場合、冗長protocol送受信部141は、冗長protocol管理部140にそのS-tagと状態(MasterであるかBackupであるかを示す情報)を適宜通知する。冗長protocol管理部140は、冗長protocol送受信部141から通知された情報を冗長情報142に含ませる(S103)。
このことを、自律的に動作している冗長protocol管理部140は、予め成されている切替条件の設定に基づいて、加入者端末又は加入者端末グループの予備系として現用系に切り替わり動作を開始する(S501)。この事例は、一定期間第2のBRAS装置200からの冗長Protocolメッセージを受信していないことを切替条件とする。
該当する加入者情報があるか否かは、先に第2のBRAS装置200が該当CPEに払い出した使用アドレス情報をスヌーピングできているか否かによって定まる。
もし、登録済みのIP PrefixがIP Pool Prefixの範囲外であれば、IP Pool情報管理部120は、IP Pool Prefixの中から新たにIP Prefixを選択し直す処理を行えばよい。
Access通信監視部260は、監視しているS-tagについて一定時間通信がなかった場合、冗長情報242に含まれる該当S-tagを持つ冗長groupの通信状態(本例ではidle time)を更新する(S602)。この例では、15秒間の無通信が継続するたびに冗長情報142にidle time値を含ませ、360秒間無通信が経過した状態としている。
この動作により、第1のBRAS装置100と第2のBRAS装置200が自律的に通信の監視結果を反映させて、異なるmetricの値を有するRoute情報メッセージをそれぞれ広告する。
[付記1]
加入者端末毎又は加入者端末グループ毎に自装置が現用系又は予備系の何れとして動作するかを示す冗長ステータスと、加入者端末毎の使用アドレス情報の一覧を示す加入者ステータスと、を内部ステータスとして記憶する記憶部と、
冗長構成を採る他のネットワーク中継装置と加入者端末群との通信を監視し、前記他のネットワーク中継装置が加入者端末に払い出した使用アドレス情報を、前記記憶部に加入者ステータスの一部として記録すると共に、逐次記録した前記内部ステータスを所定タイミングで逐次通知先に通知/広告する管理部と、
を含むことを特徴とするアクセスネットワークと中継先ネットワークを中継するネットワーク中継装置。
前記管理部は、冗長構成を採る他のネットワーク中継装置の通知した前記加入者端末又は加入者端末グループに対するメッセージを監視すると共に、前記内部ステータスに予備系として示されている所定加入者端末が現用系として動作する状態に切り替わった際に、前記記憶部から前記所定加入者端末の用いていた使用アドレス情報を読み出して、前記所定加入者端末と中継先ネットワークとの通信を前記所定加入者端末の用いていた使用アドレス情報で継続することを特徴とする上記付記記載のネットワーク中継装置。
前記管理部は、前記内部ステータスに含まれている加入者端末毎又は加入者端末グループ毎に通信状態情報を監視して、該通信状態情報に応じた自装置を介する通信ルートの優先度を加減して中継先ネットワーク装置に対して通信経路情報を広告することを特徴とする上記付記記載のネットワーク中継装置。
使用アドレス情報として、アドレス群を纏めたIPプールを用いて、冗長構成を採る前記他のネットワーク中継装置と同一のIPプールを複数管理して、前記他のネットワーク中継装置の現用系の運用に用いていないIPプールを、自装置の現用系の運用に用いることを特徴とする上記付記記載のネットワーク中継装置。
前記管理部は、前記冗長ステータスを更新して、現用系に切り替えて通信を中継する加入者端末毎又は加入者端末グループ毎からの通信を受けた際に、前記加入者ステータスに既に使用アドレス情報が含まれていれば該加入者端末の承認を省略又は承認と並行して、前記他のネットワーク中継装置が該加入者端末に払い出した使用アドレス情報を、該加入者端末の使用アドレスとして設定することを特徴とする上記付記記載のネットワーク中継装置。
該ネットワーク中継装置及び前記他のネットワーク中継装置は、BRAS装置であり、
中継先ネットワークは、コアネットワークであり、
前記加入者端末は、CPE(Customer Premises Equipment)であり、
通信プロトコルとしてIP v6及びVRRP(Virtual Router Redundancy Protocol)を用いつつ、Service-tag毎にCPEとコアネットワーク間の通信経路を冗長化する
ことを特徴とする上記付記記載のネットワーク中継装置。
アクセスネットワークと中継先ネットワークを各々ゲートウェイとして中継する複数のネットワーク中継装置で中継にかかる動作を定める内部ステータスを記憶部に各々保持し、
個々のネットワーク中継装置は、
前記内部ステータスとして、加入者端末毎又は加入者端末グループ毎に自装置が現用系又は予備系の何れとして動作するかを示す冗長ステータスと加入者端末毎の使用アドレス情報の一覧を示す加入者ステータスとを前記記憶部に逐次記録して所定タイミングで逐次通知先に所定のステータスを含むメッセージを通知/広告し、
自装置に到達した通信を監視して、他のネットワーク中継装置が加入者端末に払い出した使用アドレス情報をも前記記憶部に逐次記録しながら、ネットワーク間の通信を中継する
ことを特徴とするゲートウェイ冗長化システム。
個々のネットワーク中継装置は、冗長構成を採る他のネットワーク中継装置の通知した前記加入者端末又は加入者端末グループに対するメッセージを監視すると共に、前記内部ステータスに予備系として示されている所定加入者端末が現用系として動作する状態に切り替わった際に、前記記憶部から前記所定加入者端末の用いていた使用アドレス情報を読み出して、前記所定加入者端末と中継先ネットワークとの通信を前記所定加入者端末の用いていた使用アドレス情報で継続することを特徴とする上記付記記載のゲートウェイ冗長化システム。
個々のネットワーク中継装置は、前記内部ステータスに含まれている加入者端末毎又は加入者端末グループ毎に通信状態情報を監視して、該通信状態情報に応じた自装置を介する通信ルートの優先度を加減して中継先ネットワーク装置に対して通信経路情報を広告することを特徴とする上記付記記載のゲートウェイ冗長化システム。
個々のネットワーク中継装置は、使用アドレス情報として、アドレス群を纏めたIPプールを用いて、冗長構成を採る前記他のネットワーク中継装置と同一のIPプールを複数管理して、前記他のネットワーク中継装置の現用系の運用に用いていないIPプールを、自装置の現用系の運用に用いることを特徴とする上記付記記載のゲートウェイ冗長化システム。
個々のネットワーク中継装置は、前記冗長ステータスを更新して、現用系に切り替えて通信を中継する加入者端末毎又は加入者端末グループ毎からの通信を受けた際に、前記加入者ステータスに既に使用アドレス情報が含まれていれば該加入者端末の承認を省略又は承認と並行して、前記他のネットワーク中継装置が該加入者端末に払い出した使用アドレス情報を、該加入者端末の使用アドレスとして設定することを特徴とする上記付記記載のゲートウェイ冗長化システム。
個々のネットワーク中継装置は、BRAS装置であり、
中継先ネットワークは、コアネットワークであり、
前記加入者端末は、CPE(Customer Premises Equipment)であり、
通信プロトコルとしてIP v6及びVRRP(Virtual Router Redundancy Protocol)を用いつつ、Service-tag毎にCPEとコアネットワーク間の通信経路を冗長化する
ことを特徴とする上記付記記載のゲートウェイ冗長化システム。
ネットワーク中継装置のプロセッサを、
加入者端末毎又は加入者端末グループ毎に、自装置が現用系又は予備系の何れとして動作するかを示す冗長ステータスと、加入者端末毎の使用アドレス情報の一覧を示す加入者ステータスと、を記録する論理的記憶部と、
冗長構成を採る他のネットワーク中継装置と加入者端末群との通信を監視し、前記他のネットワーク中継装置が加入者端末に払い出した使用アドレス情報を、前記論理的記憶部を受け持つ物理的記憶部に加入者ステータスの一部として記録すると共に、所定タイミングで逐次通知先に所定のステータスを含むメッセージを通知/広告する管理部
として動作させることを特徴とするコンピュータリーダブルメディウムに非一時的に記録されたプログラム。
前記プロセッサを、冗長構成を採る他のネットワーク中継装置の通知した前記加入者端末又は加入者端末グループに対するメッセージを監視すると共に、前記内部ステータスに予備系として示されている所定加入者端末が現用系として動作する状態に切り替わった際に、前記記憶部から前記所定加入者端末の用いていた使用アドレス情報を読み出して、前記所定加入者端末と中継先ネットワークとの通信を前記所定加入者端末の用いていた使用アドレス情報で継続するように動作させることを特徴とする上記付記記載のプログラム。
前記プロセッサを、前記内部ステータスに含まれている加入者端末毎又は加入者端末グループ毎に通信状態情報を監視して、該通信状態情報に応じた自装置を介する通信ルートの優先度を加減して中継先ネットワーク装置に対して通信経路情報を広告するように動作させることを特徴とする上記付記記載のプログラム。
前記プロセッサを、自ネットワーク中継装置で用いる使用アドレス情報として、アドレス群を纏めたIPプールを用いて、冗長構成を採る前記他のネットワーク中継装置と同一のIPプールを複数管理して、前記他のネットワーク中継装置の現用系の運用に用いていないIPプールを、自装置の現用系の運用に用いるように動作させることを特徴とする上記付記記載のプログラム。
前記プロセッサを、前記冗長ステータスを更新して、現用系に切り替えて通信を中継する加入者端末毎又は加入者端末グループ毎からの通信を受けた際に、前記加入者ステータスに既に使用アドレス情報が含まれていれば該加入者端末の承認を省略又は承認と並行して、前記他のネットワーク中継装置が該加入者端末に払い出した使用アドレス情報を、該加入者端末の使用アドレスとして設定するように動作させることを特徴とする上記付記記載のプログラム。
アクセスネットワークと中継先ネットワークを中継するネットワーク中継装置は、加入者端末毎又は加入者端末グループ毎に、自装置が現用系又は予備系の何れとして動作するかを示す冗長ステータスと、加入者端末毎の使用アドレス情報の一覧を示す加入者ステータスと、を記憶部で逐次管理して所定タイミングで逐次通知先に所定のステータスを含むメッセージを通知/広告し、
該ネットワーク中継装置は、冗長構成を採る他のネットワーク中継装置と加入者端末群との通信を監視すると共に、前記他のネットワーク中継装置が加入者端末に払い出した使用アドレス情報を、前記記憶部に加入者ステータスの一部として記録管理する
ことを特徴とするネットワーク中継装置の冗長化方法。
前記ネットワーク中継装置は、冗長構成を採る他のネットワーク中継装置の通知した前記加入者端末又は加入者端末グループに対するメッセージを監視すると共に、前記内部ステータスに予備系として示されている所定加入者端末が現用系として動作する状態に切り替わった際に、前記記憶部から前記所定加入者端末の用いていた使用アドレス情報を読み出して、前記所定加入者端末と中継先ネットワークとの通信を前記所定加入者端末の用いていた使用アドレス情報で継続することを特徴とする上記付記記載のネットワーク中継装置の冗長化方法。
前記ネットワーク中継装置は、前記内部ステータスに含まれている加入者端末毎又は加入者端末グループ毎に通信状態情報を監視して、該通信状態情報に応じた自装置を介する通信ルートの優先度を加減して中継先ネットワーク装置に対して通信経路情報を広告することを特徴とする上記付記記載のネットワーク中継装置の冗長化方法。
前記ネットワーク中継装置は、使用アドレス情報として、アドレス群を纏めたIPプールを用いて、冗長構成を採る前記他のネットワーク中継装置と同一のIPプールを複数管理して、前記他のネットワーク中継装置の現用系の運用に用いていないIPプールを、自装置の現用系の運用に用いることを特徴とする上記付記記載のネットワーク中継装置の冗長化方法。
前記ネットワーク中継装置は、前記冗長ステータスを更新して、現用系に切り替えて通信を中継する加入者端末毎又は加入者端末グループ毎からの通信を受けた際に、前記加入者ステータスに既に使用アドレス情報が含まれていれば該加入者端末の承認を省略又は承認と並行して、前記他のネットワーク中継装置が該加入者端末に払い出した使用アドレス情報を、該加入者端末の使用アドレスとして設定することを特徴とする上記付記記載のネットワーク中継装置の冗長化方法。
11 記憶部
12 管理部
100,200 BRAS装置
110 AAA処理部
120 IP prefix情報管理部
121 IP prefix情報送受信部
122 加入者情報
130 IP pool情報
140 冗長protocol管理部
141 冗長protocol送受信部
142 冗長情報
150 IP Route情報管理部
152 IP Route情報
160 Access通信監視部
A01,B01,C01,D01 CPE
300 スイッチ
400 AAAサーバ
500 コアルータ
Claims (10)
- 加入者端末毎又は加入者端末グループ毎に自装置が現用系又は予備系の何れとして動作するかを示す冗長ステータスと、加入者端末毎の使用アドレス情報の一覧を示す加入者ステータスと、を内部ステータスとして記憶する記憶部と、
冗長構成を採る他のネットワーク中継装置と加入者端末群との通信を監視し、前記他のネットワーク中継装置が加入者端末に払い出した使用アドレス情報を、前記記憶部に加入者ステータスの一部として記録すると共に、逐次記録した前記内部ステータスを所定タイミングで逐次通知先に通知/広告する管理部と、
を含むことを特徴とするアクセスネットワークと中継先ネットワークを中継するネットワーク中継装置。 - 前記管理部は、
冗長構成を採る他のネットワーク中継装置の通知した前記加入者端末又は加入者端末グループに対するメッセージを監視すると共に、
前記内部ステータスに予備系として示されている所定加入者端末が現用系として動作する状態に切り替わった際に、前記記憶部から前記所定加入者端末の用いていた使用アドレス情報を読み出して、前記所定加入者端末と中継先ネットワークとの通信を前記所定加入者端末の用いていた使用アドレス情報で継続する
ことを特徴とする請求項1記載のネットワーク中継装置。 - 前記管理部は、
前記内部ステータスに含まれている加入者端末毎又は加入者端末グループ毎に通信状態情報を監視して、該通信状態情報に応じた自装置を介する通信ルートの優先度を加減して中継先ネットワーク装置に対して通信経路情報を広告する
ことを特徴とする請求項1又は2に記載のネットワーク中継装置。 - 使用アドレス情報として、アドレス群を纏めたIPプールを用いて、
冗長構成を採る前記他のネットワーク中継装置と同一のIPプールを複数管理して、前記他のネットワーク中継装置の現用系の運用に用いていないIPプールを、自装置の現用系の運用に用いる
ことを特徴とする請求項1又は2に記載のネットワーク中継装置。 - 前記管理部は、前記冗長ステータスを更新して、現用系に切り替えて通信を中継する加入者端末毎又は加入者端末グループ毎からの通信を受けた際に、前記加入者ステータスに既に使用アドレス情報が含まれていれば該加入者端末の承認を省略又は承認と並行して、前記他のネットワーク中継装置が該加入者端末に払い出した使用アドレス情報を、該加入者端末の使用アドレスとして設定することを特徴とする請求項1ないし4の何れか一項に記載のネットワーク中継装置。
- 該ネットワーク中継装置及び前記他のネットワーク中継装置は、BRAS装置であり、
中継先ネットワークは、コアネットワークであり、
前記加入者端末は、CPE(Customer Premises Equipment)であり、
通信プロトコルとしてIP v6及びVRRP(Virtual Router Redundancy Protocol)を用いつつ、Service-tag毎にCPEとコアネットワーク間の通信経路を冗長化する
ことを特徴とする請求項1ないし5の何れか一項に記載のネットワーク中継装置。 - アクセスネットワークと中継先ネットワークを各々ゲートウェイとして中継する複数のネットワーク中継装置で中継にかかる動作を定める内部ステータスを記憶部に各々保持し、
個々のネットワーク中継装置は、
前記内部ステータスとして、加入者端末毎又は加入者端末グループ毎に自装置が現用系又は予備系の何れとして動作するかを示す冗長ステータスと加入者端末毎の使用アドレス情報の一覧を示す加入者ステータスとを前記記憶部に逐次記録して所定タイミングで逐次通知先に所定のステータスを含むメッセージを通知/広告し、
自装置に到達した通信を監視して、他のネットワーク中継装置が加入者端末に払い出した使用アドレス情報をも前記記憶部に逐次記録しながら、ネットワーク間の通信を中継する
ことを特徴とするゲートウェイ冗長化システム。 - アクセスネットワークと中継先ネットワークを中継するネットワーク中継装置は、加入者端末毎又は加入者端末グループ毎に、自装置が現用系又は予備系の何れとして動作するかを示す冗長ステータスと、加入者端末毎の使用アドレス情報の一覧を示す加入者ステータスと、を記憶部で逐次管理して所定タイミングで逐次通知先に所定のステータスを含むメッセージを通知/広告し、
該ネットワーク中継装置は、冗長構成を採る他のネットワーク中継装置と加入者端末群との通信を監視すると共に、前記他のネットワーク中継装置が加入者端末に払い出した使用アドレス情報を、前記記憶部に加入者ステータスの一部として記録管理する
ことを特徴とするネットワーク中継装置の冗長化方法。 - ネットワーク中継装置のプロセッサを、
加入者端末毎又は加入者端末グループ毎に、自装置が現用系又は予備系の何れとして動作するかを示す冗長ステータスと、加入者端末毎の使用アドレス情報の一覧を示す加入者ステータスと、を記録する論理的記憶部と、
冗長構成を採る他のネットワーク中継装置と加入者端末群との通信を監視し、前記他のネットワーク中継装置が加入者端末に払い出した使用アドレス情報を、前記論理的記憶部を受け持つ物理的記憶部に加入者ステータスの一部として記録すると共に、所定タイミングで逐次通知先に所定のステータスを含むメッセージを通知/広告する管理部
として動作させることを特徴とするコンピュータ読み取り可能な非一時的にプログラムを記録した記録媒体。 - ネットワーク中継装置のプロセッサを、
加入者端末毎又は加入者端末グループ毎に、自装置が現用系又は予備系の何れとして動作するかを示す冗長ステータスと、加入者端末毎の使用アドレス情報の一覧を示す加入者ステータスと、を記録する論理的記憶部と、
冗長構成を採る他のネットワーク中継装置と加入者端末群との通信を監視し、前記他のネットワーク中継装置が加入者端末に払い出した使用アドレス情報を、前記論理的記憶部を受け持つ物理的記憶部に加入者ステータスの一部として記録すると共に、所定タイミングで逐次通知先に所定のステータスを含むメッセージを通知/広告する管理部
として動作させることを特徴とするプログラム。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2016571830A JP6350839B2 (ja) | 2015-01-28 | 2016-01-04 | ネットワーク中継装置、ゲートウェイ冗長化システム、プログラム、および冗長化方法 |
US15/547,334 US10367680B2 (en) | 2015-01-28 | 2016-01-04 | Network relay apparatus, gateway redundancy system, program, and redundancy method |
EP16742902.6A EP3253010A4 (en) | 2015-01-28 | 2016-01-04 | Network relay device, gateway redundancy system, program, and redundancy method |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2015-013978 | 2015-01-28 | ||
JP2015013978 | 2015-01-28 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016121293A1 true WO2016121293A1 (ja) | 2016-08-04 |
Family
ID=56542922
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2016/000003 WO2016121293A1 (ja) | 2015-01-28 | 2016-01-04 | ネットワーク中継装置、ゲートウェイ冗長化システム、プログラム、および冗長化方法 |
Country Status (4)
Country | Link |
---|---|
US (1) | US10367680B2 (ja) |
EP (1) | EP3253010A4 (ja) |
JP (1) | JP6350839B2 (ja) |
WO (1) | WO2016121293A1 (ja) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107819602A (zh) * | 2016-09-14 | 2018-03-20 | 中国电信股份有限公司 | 用户流量分配方法和系统 |
CN108322368A (zh) * | 2017-06-23 | 2018-07-24 | 新华三技术有限公司 | 视频点播方法和装置 |
CN109391597A (zh) * | 2017-08-10 | 2019-02-26 | 中国电信股份有限公司 | 认证方法、认证系统以及通信系统 |
JP2019164518A (ja) * | 2018-03-19 | 2019-09-26 | 株式会社リコー | 仲介装置、機器監視システム、仲介方法 |
EP3573295A4 (en) * | 2017-01-17 | 2020-01-08 | Nec Corporation | GATEWAY DEVICE, NETWORK ADDRESS TRANSLATION DEVICE, COMMUNICATION SYSTEM, COMMUNICATION METHOD, AND PROGRAM |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3641278A1 (de) * | 2018-10-17 | 2020-04-22 | Siemens Aktiengesellschaft | Verfahren zur bereitstellung redundanter relay-, insbesondere routing funktion, system, computerprogramm und computerlesbares medium |
CN109617736A (zh) * | 2018-12-26 | 2019-04-12 | 杭州和利时自动化有限公司 | 一种数据传输方法和相关装置 |
CN112737946B (zh) * | 2019-10-14 | 2023-09-05 | 中兴通讯股份有限公司 | 用于IPv6网络的路由通告方法、装置、存储介质和系统 |
CN114430310A (zh) * | 2020-10-29 | 2022-05-03 | 南京中兴新软件有限责任公司 | 信息处理方法及其装置、宽带接入服务器、存储介质 |
CN112650048B (zh) * | 2021-01-21 | 2021-09-17 | 杭州康吉森自动化科技有限公司 | 一种工业网关冗余系统和控制方法 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7269132B1 (en) * | 2002-02-22 | 2007-09-11 | Nortel Networks, Ltd. | Method and apparatus for achieving transparent redundancy at a hierarchical boundary |
US20120179826A1 (en) * | 2009-09-23 | 2012-07-12 | Zte Corporation | Address Distribution Method, Device and System Thereof |
JP2013500651A (ja) * | 2009-09-03 | 2013-01-07 | ▲ホア▼▲ウェイ▼技術有限公司 | ユーザ側のマルチキャストサービスのプライマリおよびスタンバイ保護システム、方法、ならびにルーティングデバイス |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2002135303A (ja) | 2000-10-18 | 2002-05-10 | Nec Corp | リモートアクセスサーバにおけるipアドレスプールの有効利用システム及び方法 |
JP3896897B2 (ja) * | 2002-05-24 | 2007-03-22 | 株式会社日立製作所 | ルータ設定方法およびルータ |
JP5107339B2 (ja) | 2006-03-31 | 2012-12-26 | シスコ テクノロジー インコーポレーテッド | アクティブ地理的冗長性のためのシステムおよび方法 |
JP4791252B2 (ja) | 2006-05-22 | 2011-10-12 | 株式会社日立製作所 | パケット転送装置、パケット転送システム、ユーザ端末装置およびパケット転送方法 |
JP4680866B2 (ja) | 2006-10-31 | 2011-05-11 | 株式会社日立製作所 | ゲートウェイ負荷分散機能を備えたパケット転送装置 |
US8547844B2 (en) | 2007-07-10 | 2013-10-01 | Telefonaktiebolaget L M Ericsson (Publ) | System and method for balancing IP gateway services |
JP5024195B2 (ja) * | 2008-06-17 | 2012-09-12 | 富士通株式会社 | 負荷分散サーバ、ネットワーク負荷分散方法および輻輳回避方法 |
CN102025528B (zh) * | 2009-09-23 | 2013-12-18 | 中兴通讯股份有限公司 | 地址管理方法、装置和系统 |
TW201042774A (en) * | 2010-07-21 | 2010-12-01 | Nexpower Technology Corp | Thin film solar cell and manufacturing method thereof |
CO6340173A1 (es) * | 2011-03-18 | 2011-11-21 | Talero John Alejandro Sanchez | Protector mascarilla retractil respiratorio |
US8614941B2 (en) * | 2011-05-09 | 2013-12-24 | Telefonaktiebolaget L M Ericsson (Publ) | Hitless switchover from active TCP application to standby TCP application |
ES2832725T3 (es) * | 2011-05-31 | 2021-06-11 | Huawei Tech Co Ltd | Método para realizar el respaldo de tolerancia ante desastres |
US20120029086A1 (en) * | 2011-10-25 | 2012-02-02 | Richard Jacobsen | Compositions and Method for Temporary Reduction of Nasal and Sinus Pain |
-
2016
- 2016-01-04 EP EP16742902.6A patent/EP3253010A4/en not_active Withdrawn
- 2016-01-04 US US15/547,334 patent/US10367680B2/en active Active
- 2016-01-04 WO PCT/JP2016/000003 patent/WO2016121293A1/ja active Application Filing
- 2016-01-04 JP JP2016571830A patent/JP6350839B2/ja active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7269132B1 (en) * | 2002-02-22 | 2007-09-11 | Nortel Networks, Ltd. | Method and apparatus for achieving transparent redundancy at a hierarchical boundary |
JP2013500651A (ja) * | 2009-09-03 | 2013-01-07 | ▲ホア▼▲ウェイ▼技術有限公司 | ユーザ側のマルチキャストサービスのプライマリおよびスタンバイ保護システム、方法、ならびにルーティングデバイス |
US20120179826A1 (en) * | 2009-09-23 | 2012-07-12 | Zte Corporation | Address Distribution Method, Device and System Thereof |
Non-Patent Citations (1)
Title |
---|
See also references of EP3253010A4 * |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107819602A (zh) * | 2016-09-14 | 2018-03-20 | 中国电信股份有限公司 | 用户流量分配方法和系统 |
EP3573295A4 (en) * | 2017-01-17 | 2020-01-08 | Nec Corporation | GATEWAY DEVICE, NETWORK ADDRESS TRANSLATION DEVICE, COMMUNICATION SYSTEM, COMMUNICATION METHOD, AND PROGRAM |
CN108322368A (zh) * | 2017-06-23 | 2018-07-24 | 新华三技术有限公司 | 视频点播方法和装置 |
WO2018233632A1 (zh) * | 2017-06-23 | 2018-12-27 | 新华三技术有限公司 | 视频点播流的转发 |
CN108322368B (zh) * | 2017-06-23 | 2020-01-03 | 新华三技术有限公司 | 视频点播方法和装置 |
US11418843B2 (en) | 2017-06-23 | 2022-08-16 | New H3C Technologies Co., Ltd. | Forwarding video-on-demand flow |
CN109391597A (zh) * | 2017-08-10 | 2019-02-26 | 中国电信股份有限公司 | 认证方法、认证系统以及通信系统 |
CN109391597B (zh) * | 2017-08-10 | 2021-04-30 | 中国电信股份有限公司 | 认证方法、认证系统以及通信系统 |
JP2019164518A (ja) * | 2018-03-19 | 2019-09-26 | 株式会社リコー | 仲介装置、機器監視システム、仲介方法 |
JP7073820B2 (ja) | 2018-03-19 | 2022-05-24 | 株式会社リコー | 仲介装置、機器監視システム、仲介方法 |
Also Published As
Publication number | Publication date |
---|---|
US10367680B2 (en) | 2019-07-30 |
US20180006876A1 (en) | 2018-01-04 |
JPWO2016121293A1 (ja) | 2017-10-26 |
EP3253010A1 (en) | 2017-12-06 |
JP6350839B2 (ja) | 2018-07-04 |
EP3253010A4 (en) | 2018-09-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP6350839B2 (ja) | ネットワーク中継装置、ゲートウェイ冗長化システム、プログラム、および冗長化方法 | |
US10917262B2 (en) | VXLAN packet forwarding method, device, and system | |
JP4796184B2 (ja) | エッジノード冗長システム | |
US10404355B2 (en) | Mobility across satellite beams using L2 connectivity | |
CN101094102B (zh) | 路由设备的主备切换方法和路由备份系统 | |
JP5074327B2 (ja) | 経路制御システム | |
EP3373547B1 (en) | Method for realizing disaster tolerance backup | |
EP2992644B1 (en) | Enhancing a mobile backup channel to address a node failure in a wireline network | |
US8166187B2 (en) | Distributed IP gateway based on sharing a MAC address and IP address concurrently between a first network switching device and a second network switching device | |
US8509059B2 (en) | Method for operating a virtual router redundancy protocol router and communication system therefor | |
US9288140B2 (en) | Multichassis failover and recovery for MLPPP wireless backhaul | |
JP6389956B2 (ja) | ネットワークトラフィックを管理する方法およびシステム | |
WO2013113228A1 (zh) | 网络设备冗余备份的方法、路由设备及系统 | |
US20120182994A1 (en) | Address compatibility in a network device reload | |
JP6795043B2 (ja) | ゲートウェイ装置、ネットワークアドレス変換装置、通信システム、通信方法、および、プログラム | |
CN101562576B (zh) | 一种路由发布方法和设备 | |
JP6037251B2 (ja) | ネットワーク経路を制御するための方法、デバイス、及びシステム | |
WO2013159549A1 (zh) | 一种建立和使用浮动网段的方法、装置和系统 | |
JP5518771B2 (ja) | 冗長ネットワークシステム、終端装置及び中継点隣接装置 | |
JP2006270680A (ja) | レイヤ2スイッチ装置 | |
US20180123956A1 (en) | Router advertisement caching | |
CN102263668A (zh) | Mpls网络中单向伪线路的实现方法、系统及装置 | |
JP3764149B2 (ja) | データ中継方法、経路情報管理装置、データ中継装置およびデータ中継システム | |
KR101475306B1 (ko) | 라우터 이중화 방법 | |
KR20030055671A (ko) | 가상 홈 네트워크의 네트워크 인터페이스 이중화 장치 및그 방법 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 16742902 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2016571830 Country of ref document: JP Kind code of ref document: A |
|
REEP | Request for entry into the european phase |
Ref document number: 2016742902 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15547334 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |