WO2018223991A1 - 一种切换主宽带网络网关bng和备bng的方法、系统和bng - Google Patents

一种切换主宽带网络网关bng和备bng的方法、系统和bng Download PDF

Info

Publication number
WO2018223991A1
WO2018223991A1 PCT/CN2018/090135 CN2018090135W WO2018223991A1 WO 2018223991 A1 WO2018223991 A1 WO 2018223991A1 CN 2018090135 W CN2018090135 W CN 2018090135W WO 2018223991 A1 WO2018223991 A1 WO 2018223991A1
Authority
WO
WIPO (PCT)
Prior art keywords
bng
database
service
primary
user
Prior art date
Application number
PCT/CN2018/090135
Other languages
English (en)
French (fr)
Inventor
彭书萍
郭红涛
陈国义
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP18814303.6A priority Critical patent/EP3627766B1/en
Publication of WO2018223991A1 publication Critical patent/WO2018223991A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access
    • H04L12/2869—Operational details of access network equipments
    • H04L12/287—Remote access server, e.g. BRAS
    • 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
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting

Definitions

  • the present invention relates to the field of communications, and in particular, to a method, a system, and a BNG for switching a primary broadband network gateway (Broadband Network Gateway, BNG for short) and a standby BNG.
  • BNG Broadband Network Gateway
  • the multiple BNGs can form a VRRP group through the Virtual Router Redundancy Protocol (VRRP) and negotiate the main BNG of the VRRP group.
  • VRRP Virtual Router Redundancy Protocol
  • the VRRP group is equivalent to a virtual router, and the host in the local area network only needs to know the Internet Protocol (English: Internet Protocol, IP address) address of the virtual router, and does not need to know the IP of a specific BNG.
  • the address is set to the default gateway of the host in the local area network as the IP address of the virtual router, and the host can use the virtual gateway to communicate with the external network.
  • each BNG in the VRRP group can be monitored by bidirectional forwarding detection (English: Bidirectional Forwarding Detection, BFD for short) or Ethernet operation management and maintenance (English: Ethernet Operations) Administration Maintenance (abbreviation: ETH OAM) performs fast fault detection on the communication link between devices connected to the BNG.
  • BFD or ETH OAM function can detect the link fault in milliseconds. With VRRP, the active/standby switchover can be performed quickly.
  • the common attribute information of the primary BNG and the standby BNG and the user's service are required after the VRRP protocol determines the primary BNG and the standby BNG.
  • the information is backed up to the standby BNG.
  • the standby BNG is always in the backup state.
  • the standby BNG runs all the time but does not process the user's services. This will result in waste of communication resources between the standby BNG and the primary BNG and the central processor for preparing the BNG.
  • Central processing unit CPU
  • the embodiment of the present invention provides a method, a system, and a BNG for switching a primary BNG and a standby BNG, which can reduce waste of communication resources of the primary BNG and the standby BNG and waste of CPU resources of the standby BNG.
  • an embodiment of the present invention provides a method for switching a primary BNG and a secondary BNG, where the method is applied to a system including a database, a first BNG, and a second BNG, wherein the first BNG is a primary BNG, The second BNG is a standby BNG, and the primary BNG processes the service of the first user, where the method includes:
  • the second BNG is from the database Reading the shared attribute information of the first BNG and the second BNG.
  • the second BNG reads the first from the database after the static information of the first user is written by the first BNG to the database until the second BNG is switched to be a primary BNG User's static information.
  • the second BNG reads dynamic information generated by the service on the first BNG from the database, where the service is in the first Dynamic information generated on a BNG is synchronously written to the database by the first BNG.
  • the second BNG switches to a primary BNG and takes over the service by the first BNG.
  • the first BNG does not need to share the common attribute information of the first BNG and the second BNG, the static information of the first user, and the dynamic generated by the service on the first BNG.
  • the information is directly backed up to the standby BNG.
  • the backup BNG runs continuously but does not process the user's services, resulting in waste of BNG communication resources and waste of CPU resources.
  • the second BNG reads the dynamic information generated by the service on the first BNG from the database only when a fault occurs, so that the waste of the CPU resources of the standby BNG can be further reduced.
  • the method further includes:
  • the second BNG When the second BNG is switched to be the primary BNG and the first BNG is processed to process the service, the second BNG synchronously writes the dynamic information generated by the service on the second BNG to the database.
  • the second BNG may back up the dynamic information generated by the service on the second BNG to the database, so that when the second BNG fails, the first BNG may be from the
  • the dynamic information generated by the service on the second BNG is read in the database, and the second BNG is processed to process the service of the first user, thereby improving network stability.
  • the first BNG and the second BNG determine, by using VRRP, that the first BNG is a primary BNG, and the second BNG is a standby BNG.
  • the above solution forms a VRRP backup group by the VRRP, which is equivalent to a virtual router.
  • the second BNG takes over the first BNG to process the service of the first user, so that the VRRP backup group consisting of the first BNG and the second BNG can be implemented.
  • the first user's business is processed without interruption.
  • an embodiment of the present invention provides a method for switching a primary BNG and a secondary BNG, where the method is applied to a system including a database, a first BNG, and a second BNG.
  • the primary BNG processes the service of the first user.
  • the method includes:
  • the first BNG When it is determined that the first BNG is a primary BNG, and the second BNG is a standby BNG, the first BNG stores the shared attribute information of the first BNG and the second BNG, and the static of the first user. The information and the dynamic information generated by the first user's service on the first BNG are written into the database.
  • the second BNG is from the database Reading the shared attribute information of the first BNG and the second BNG.
  • the second BNG reads the first from the database after the static information of the first user is written by the first BNG to the database until the second BNG is switched to be a primary BNG User's static information.
  • the second BNG reads the dynamic information generated by the service on the first BNG from the database.
  • the dynamic information generated by the service on the first BNG is written into the database by the first BNG.
  • the second BNG switches to a primary BNG and takes over the first BNG to process the service of the first user.
  • the method further includes: when the second BNG is switched to be a primary BNG and the first BNG is processed to process the service, the second BNG The dynamic information generated by the service on the second BNG is synchronously written to the database.
  • the first BNG When the first BNG fails to recover, the first BNG reads dynamic information generated by the service on the second BNG from the database.
  • the first BNG takes over the second BNG to process the service.
  • the first BNG and the second BNG determine, by using VRRP, that the first BNG is a primary BNG, and the second BNG is a standby BNG.
  • the present invention provides a BNG, which is a second BNG in a system, the system number including a database and a first BNG.
  • the second BNG is a BNG.
  • the first BNG is a main BNG.
  • the first BNG processes the service of the first user.
  • the second BNG includes a reading unit and a processing unit.
  • a reading unit configured to: after the shared attribute information of the first BNG and the second BNG is written by the first BNG to the database, before the second BNG is switched to be a primary BNG, from the database Reading the shared attribute information of the first BNG and the second BNG. And reading the static information of the first user from the database after the static information of the first user is written by the first BNG to the database until the second BNG is switched to be a primary BNG.
  • the reading unit is further configured to: when the first BNG fails to continue processing the service, read dynamic information generated by the service on the first BNG from the database.
  • the dynamic information generated by the service on the first BNG is synchronously written to the database by the first BNG.
  • the processing unit is configured to switch the second BNG to a primary BNG and cause the second BNG to take over the first BNG to process the service.
  • the second BNG is not passively backed up by the shared attribute information of the first BNG and the second BNG, the static information of the first user, and the dynamic information generated by the service on the first BNG.
  • the second BNG can read the foregoing information from the database to prevent the second BNG from being in the running state but cannot be processed, and reducing the waste of the second BNG resource.
  • the second BNG may further read the dynamic information generated by the service on the primary BNG from the database only when the first BNG fails, so that the CPU of the second BNG may be improved. The efficiency of resources.
  • the second BNG further includes a writing unit, where the writing unit is configured to: when the second BNG processes the service, The dynamic information generated on the second BNG is synchronously written to the database.
  • the present invention provides a system for switching between a primary BNG and a standby BNG.
  • the system includes a database, a first BGN, and a second BGN.
  • the first BNG processes the service of the first user.
  • the first BGN is configured to use the common attribute information of the first BNG and the second BNG, the first user
  • the static information and the dynamic information generated by the first user's service on the first BNG are written into the database.
  • the second BNG is used after the shared attribute information of the first BNG and the second BNG is written by the first BNG to the database until the second BNG is switched to be a primary BNG.
  • the shared attribute information of the first BNG and the second BNG is read in the database.
  • the second BNG reads the first from the database after the static information of the first user is written by the first BNG to the database until the second BNG is switched to be a primary BNG User's static information.
  • the first BNG fails to process the service of the first user
  • the dynamic information generated by the service of the first user on the first BNG is read from the database.
  • the dynamic information generated by the service on the first BNG is synchronously written into the database by the first BNG. And used to replace the first BNG to process the service of the first user;
  • the database is configured to store shared attribute information of the first BNG and the second BNG written by the first BNG, static information of the first user, and the service is generated on the first BNG Dynamic information.
  • the second BNG is further configured to: when the main BNG is switched and the service is processed by the first BNG, the service is in the second The dynamic information generated on the BNG is synchronously written to the database.
  • the database is further configured to store dynamic information generated by the service on the second BNG.
  • the present application provides a computer readable storage medium having instructions stored therein that, when executed on a computer, cause the computer to perform the first aspect, the second aspect, and each of the foregoing The described method of implementation.
  • FIG. 1 is a schematic diagram of a networking architecture provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of an application scenario according to an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of a method for switching between a primary BNG and a standby BNG according to an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of another method for switching between a primary BNG and a standby BNG according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of a BNG according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of another BNG according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a system for switching between a primary BNG and a standby BNG according to an embodiment of the present invention.
  • FIG. 1 is a schematic diagram of a networking structure of a primary BNG and a standby BNG switching method, including a host A, a host B, and a host C, and a local area network switch (LSW) LSW1 and LSW2.
  • BNG1 and standby BNG2 as well as external networks.
  • the BNG can be a broadband access server (English: broadband access server, BSS for short), or a broadband remote access server (BRAS), or a broadband network access server (English: broadband network
  • the access server (BNAS) can be a Layer 2 tunneling protocol network server (English: L2TP network server, LNS) or a service router (English: service router, SR).
  • BNG1 and BNG2 form a virtual router through VRRP.
  • Host A, host B, and host C in the LAN can access the BNG and communicate with the external network by knowing the IP address of the virtual router.
  • Host B and Host C do not need to know the IP addresses of specific BNG1 and BNG2.
  • the VRRP protocol uses a mechanism to ensure that the services of Host A, Host B, and Host C are switched to BNG2 in time when BNG1 fails to process the services of Host A, Host B, and Host C, thus ensuring Host A and Host B. And the continuity and reliability of the host C access service.
  • BNG1 and BNG2 the primary BNG and the standby BNG need to be negotiated through VRRP.
  • BNG1 is the primary BNG
  • BNG2 is the standby BNG.
  • the main BNG and standby BNG switching will be described.
  • host A When host A sends an online request to a virtual router composed of BNG1 and BNG2, both BNG1 and BNG2 receive the online request.
  • BNG1 processes the online request, including authentication and real-time. Billing and authorization, etc., and BNG2 as the standby BNG will actively discard the online request.
  • the BNG1 After the host A is connected to the BNG1, the BNG1 synchronizes the common attribute information of the BNG1 and the BNG2 with the user information of the host A to the BNG2 through the Transmission Control Protocol (TCP).
  • TCP Transmission Control Protocol
  • the BNG2 generates a corresponding information for the user information.
  • the user service is used to ensure that when BNG1 fails, BNG2 can take over the service of host A smoothly, ensure the continuity of the host service, and reduce the loss caused by the fault.
  • the processing flow of BNG1 and BNG2 to Host B and Host C is similar to that of Host A.
  • the common attribute information of BNG1 and BNG2 in BNG1 includes the same IP address pool, virtual local area network (VLAN), and quality of service (QoS) policy.
  • VLAN virtual local area network
  • QoS quality of service
  • the BNG2 can only handle the online service of the host A, the host B, and the host C only when the BNG1 fails and the BNG2 is set to the primary BNG.
  • BNG2 performs the backup of the common attribute information of BNG1 and BNG2 and the static information of the user in BNG1 and the dynamic information generated by the user service on BNG1. This unified backup will cause unnecessary execution of BNG2.
  • the backup operation causes waste of communication resources between BNG1 and BNG2 and waste of CPU resources of BNG1 and BNG2.
  • FIG. 2 is a schematic diagram of an application scenario for solving the above technical problem.
  • the VRRP protocol can be used.
  • BNG1 is the primary BNG and BNG2 is the standby BNG.
  • BNG1 is the primary BNG and BNG2 is the standby BNG.
  • BNG2 is the primary BNG and BNG1.
  • both BNG1 and BNG2 can process the host online service.
  • the online request of host A and host B is processed by BNG1 in VRRP group 1, and BNG2 is the standby BNG of VRRP group 1.
  • the uplink request service of the host C and the host D is processed by the BNG2 in the VRRP group 2, and the BNG1 is the standby BNG in the VRRP group 2.
  • the shared attribute information of BNG1 and BNG2 and the static information of the user processed by BNG1 do not need to be directly backed up to BNG2, and can be written into the database by BNG1 (English: database, referred to as DB).
  • the DB saves the shared attribute information of the BNG1 and BNG2 of the VRRP group 1 and the static information of the user processed by the BNG1.
  • the BNG2 of the VRRP group 2 can also write the shared attribute information of the VRRP group 2 and the static information of the user processed by the BNG2 into the DB, and the DB saves the shared attribute information of the VRRP group 2 and is processed by the BNG2.
  • Static information of the user For example, when determining the active/standby relationship between BNG1 and BNG2 in VRRP group 1, it is determined that BNG1 is the primary BNG in VRRP group 1, and BNG1 is the common attribute information of VRRP group 1 that needs to be backed up. The static information of the user processed by BNG1 and the dynamic information generated by BNG1 by the user of BNG1 are written to the DB for backup.
  • BNG2 can read the shared attribute information of BNG1 and BNG2 and the static information of the user processed by BNG1 from the DB. If the BNG1 in the VRRP group 1 fails to process the user's online service, the BNG2 can obtain the dynamic information generated by the BNG1 service on the BNG1 from the DB to take over the BNG1 to continue processing the BNG1. User's business. In this way, BNG2 not only does not handle the passive backup state, but also can classify the required information from the DB, reducing the waste of communication resources and waste of CPU resources.
  • the following takes the main BNG and the standby BNG switching provided in the embodiment of the present application as an example to further explain the working process of switching between the primary BNG and the standby BNG.
  • FIG. 3 a schematic flowchart of a method for switching a primary BNG and a secondary BNG is provided.
  • the method is applied to a system including a database, a first BNG, and a second BNG, where the first BNG is a primary BNG, and the first The second BNG is a standby BNG, and the first BNG processes the service of the first user, where the method specifically includes:
  • the first BNG and the second BNG may determine, by using VRRP, that the first BNG is a primary BNG, and the second BNG is a standby BNG, where the first The BNG and the second BNG form a VRRP group, and the VRRP group is equivalent to a virtual router.
  • the first BNG and the second BNG need to ensure the consistency of the configuration.
  • the first BNG and the second BNG are configured with the same IP address pool, VLAN, and QoS policy parameters.
  • the parameters are the first BNG.
  • the common attribute information of the first BNG and the second BNG includes at least an IP address pool, a VLAN, and a QoS policy of the VRRP group.
  • the first BNG backs up the shared attribute information into the database.
  • the shared attribute information of the first BNG and the second BNG is written by the first BNG into the database when determining a primary/back relationship between the first BNG and the second BNG, that is, when When the first BNG is determined to be a primary BNG, and the second BNG is a standby BNG, the first BNG writes the shared attribute information into the database. Therefore, the first BNG will quickly write the shared attribute information into the belonging database.
  • the second BNG may read the shared attribute information from the database at any time after the first BNG writes the shared attribute information into the database until the second BNG switches to the primary BNG.
  • the first BNG when the service of the first user accesses the first BNG, the first BNG writes the static information of the first user to the database for backup.
  • the static information of the first user includes the media access control (MAC) address and the session identifier (English: session identifier), which are not frequent over time. Change of information.
  • MAC media access control
  • the second BNG can read the static information of the first user from the database to share the static information of the first user with the first BNG.
  • the link fault can be quickly detected through BFD or ETH OAM.
  • the second BNG reads the dynamic information generated by the first user's service on the first BNG from the database.
  • the dynamic information includes an uplink/downstream packet (English: up/down-pack), an uplink/downlink byte (English: up/down-byte), and the like, and information for charging for real-time traffic statistics, the first
  • the dynamic information generated by the user's service on the first BNG is synchronously written into the database by the first BNG.
  • S304 The second BNG switches to a primary BNG and takes over the service by the first BNG.
  • the second BNG is switched from the standby BNG to the new BNG, and the first BNG is taken over to continue processing the service of the first user.
  • the shared attribute information of the primary BNG and the standby BNG, the dynamic information generated by the first user's service on the first BNG, and the static information of the first user are classified and backed up by using the database, so that the The first BNG does not need to directly back up the shared attribute information of the first BNG and the second BNG, the static information of the first user, and the dynamic information generated by the service on the first BNG to the standby BNG causes BNG to run continuously but cannot process services, resulting in waste of communication resources between BNG and waste of CPU resources of BNG.
  • the second BNG reads the dynamic information generated by the service on the first BNG from the database only when a fault occurs, so that the waste of the CPU resources of the standby BNG can be further reduced.
  • the database is used to separate the common attribute information of the primary BNG and the standby BNG, the static information of the first user, and the dynamic information generated by the first user's service on the first BNG from the primary BNG and the standby BNG, and the backup can also be implemented. The information is decoupled from the primary BNG and the standby BNG.
  • the method further includes: when the fault of the first BNG is restored, cutting back the service of the first user to the first BNG, where the first BNG obtains the database from the database Dynamic information generated by the service on the second BNG The dynamic information generated by the service on the second BNG is synchronously written by the second BNG to the database.
  • the service of the first user may be processed, and the service of the first user is switched back to the first BNG, and the service of the first user is used by the first BNG.
  • the first BNG may obtain dynamic information of the first user required to process the service of the first user from the database.
  • the dynamic information of the first user is backed up by the second BNG into the database.
  • FIG. 4 is a schematic flowchart of another method for switching a primary BNG and a secondary BNG according to the present disclosure.
  • the method is applied to a system including a database, a first BNG, and a second BNG, where the first BNG processing is first.
  • the method includes:
  • the first BNG and the second BNG determine, by the VRRP, that the first BNG is a primary BNG, and the second BNG is a standby BNG.
  • the first BNG and the second BNG form a VRRP group through VRRP.
  • the VRRP group is functionally equivalent to a virtual router, and the virtual router is configured with a virtual IP address and a virtual MAC address.
  • a first user in the local area network sets the virtual IP address of the virtual router as a default gateway and communicates with the external network through the virtual router. Determining the primary BNG and the secondary BNG from the first BNG and the second BNG in the VRRP group by using VRRP, for example, determining that the first BNG with the highest priority is the primary BNG, and the second BNG with the lower priority is the standby BNG.
  • the first BNG sends a free address resolution protocol (ARP) packet to notify the second BNG and the first user of the virtual MAC address of the virtual router, thereby taking the message of the first user.
  • a forwarded task that helps the first user to communicate with the external network.
  • the first BNG is the common attribute information of the first BNG and the second BNG, the static information of the first user, and the first user.
  • the dynamic information generated on a BNG is written to the database for backup, wherein the dynamic information generated by the first user on the first BNG is synchronously written into the database.
  • the common attribute information of the first BNG and the second BNG includes parameters such as the same IP address pool, VLAN, and QoS policy configured for the first BNG and the second BNG.
  • the static information of the first user includes information that the MAC address, the session ID, and the like do not change frequently with time.
  • the dynamic information generated by the first user's service on the first BNG includes up/down-pack, up/down-byte, and the like for performing real-time traffic statistics for charging.
  • the shared attribute information of the first BNG and the second BNG, the static information of the first user, and the dynamic information generated by the first user's service on the first BNG are both used by the BNG to process the first user to communicate with the outside.
  • the first BNG when determining that the first BNG is the primary BNG and the second BNG is the standby BNG, the first BNG writes the shared attribute information of the first BNG and the second BNG to the In the database, to make a backup in the database.
  • the second BNG may read the shared attribute information from the database after the shared attribute information is written to the database until the second BNG is switched to be a primary BNG.
  • the common attribute information includes parameters such as an IP address pool, a VLAN, and a QoS policy.
  • the first BNG when it is determined that the first BNG is a primary BNG, and the second BNG is a standby BNG, the first BNG writes static information of the first user to the database.
  • the second BNG may read the data from the data path after the first BNG writes the static information of the first user to the database and before the second BNG switches to the primary BNG.
  • the static information of the first user, the static information of the first user includes a MAC address of the first user and a session identifier.
  • the first BNG assumes the task of processing the first user service as the primary BNG, and the second BNG is in the ready listening state as the standby BNG.
  • the second BNG can use BFD to monitor the reachability of the IP address on the first BNG. If the first BNG fails, the second BNG can use BFD to sense the fault change. At this time, the second BNG will read the data from the database.
  • the dynamic information generated by the service on the first BNG the dynamic information includes information for charging, such as up/down-pack, up/down-byte, and the like, and the service is on the first BNG.
  • the generated dynamic information is synchronously written into the database by the first BNG.
  • S405 The second BNG switches to a primary BNG and takes over the service by the first BNG.
  • the BFD technology may be used to monitor the state of the first BNG on the second BNG, so that when the first BNG fails, the second BNG can immediately switch to the new primary. BNG, and the first BNG is replaced by the second BNG to process the service of the first user.
  • the method further includes: when the second BNG is switched to be a primary BNG and succeeding the first BNG to process the service, the second BNG generates the service on the second BNG. Dynamic information is written to the database. When the first BNG fails to recover, the first BNG reads dynamic information generated by the service on the second BNG from the database. The first BNG replaces the second BNG to process the service.
  • the second BNG when the second BNG becomes the new primary BNG and takes over the first BNG to process the service, the second BNG needs to write the dynamic information generated by the first user's service on the second BNG to the The database.
  • the first BNG may read the dynamic information generated by the service on the second BNG from the database.
  • the first BNG switch is the primary BNG to replace the second BNG to process the service of the first user.
  • a BNG 500 is provided for the application.
  • the BNG 500 is applied to a system including a database and a first BNG.
  • the BNG 500 is a second BNG in the system, and the first BNG is
  • the primary BNG is a standby BNG, the first BNG processes the service of the first user, and the second BNG 500 includes a reading unit 501 and a processing unit 502.
  • the reading unit 501 is configured to: before the common attribute information of the first BNG and the second BNG 500 is written by the first BNG to the database until the second BNG 500 is switched to be a primary BNG, Reading the shared attribute information of the first BNG and the second BNG 500 in the database, and after the static information of the first user is written by the first BNG to the database to the Before the second BNG 500 switches to the primary BNG, the static information of the first user is read from the database.
  • the reading unit 501 is further configured to: when the first BNG fails to continue processing the service, read dynamic information generated by the service on the first BNG from the database, where the service Dynamic information generated on the first BNG is synchronously written to the database by the first BNG.
  • the processing unit 502 is configured to switch the second BNG 500 to a primary BNG and cause the second BNG 500 to take over the first BNG to process the service.
  • the specific implementation manner of the reading unit 501 may be performed by referring to the second BNG in FIG. 3 and FIG. 4 that the primary BNG and the standby BNG read the common BNG and the second BNG from the database.
  • the specific conditions and processes of the attribute information, the static information of the first user, and the dynamic information generated by the service of the first user on the first BNG are not described herein again for the sake of briefing.
  • the specific implementation of the processing unit 502 may be performed by referring to step 304 of FIG. 3 and step 405 of FIG. 4, where the second BNG is switched to be the primary BNG and the first BNG is processed to process the service. .
  • the second BNG further includes a writing unit 503, where the writing unit 503 is configured to: when the processing unit processes the service, write dynamic information generated by the service on the second BNG. Go to the database.
  • an embodiment of another BNG 600 is provided in the present application.
  • the BNG 600 is applied to a system including a database and a first BNG, where the BNG is a second BNG in the system,
  • the first BNG is a primary BNG
  • the second BNG is a standby BNG
  • the primary BNG processes a service of a first user
  • the second BNG 600 includes a communication interface 601 and a processor 602.
  • the BNG 600 shown in FIG. 6 may be the second BNG in FIG. 3 and FIG. 4 of the foregoing method embodiment, and the function of the second BNG described above may be implemented.
  • the second BNG includes a communication interface 601, a processor 602, a memory 603, and a bus 604 that connects the processor 602, the communication interface 601, and the memory 603.
  • the communication interface 601 is used for communication between the second BNG and the database
  • the memory 603 is used for storing program instructions
  • the memory 603 may include high-speed random access memory (English: random access memory, RAM for short), and may also include non-volatile A non-volatile memory, such as at least one disk storage, can be invoked by the processor 602 to execute program functions stored in the memory 603.
  • the communication interface 601 is configured to: before the common attribute information of the first BNG and the second BNG 600 is written by the first BNG to the database, until the second BNG is switched to be a primary BNG, Reading the shared attribute information of the first BNG and the second BNG 600 in the database, and after the static information of the first user is written by the first BNG to the database to the Before the two BNGs 600 are switched to be the primary BNG, the static information of the first user is read from the database.
  • the communication interface 601 is further configured to: when the first BNG fails to continue processing the service, receive dynamic information generated by the service on the first BNG from the database, where the service is in the office The dynamic information generated on the first BNG is synchronously written to the database by the first BNG.
  • the processor 602 is configured to switch to the primary BNG and replace the first BNG to process the service.
  • the communication interface 601 is further configured to: when the processor processes the service, send dynamic information generated by the service on the second BNG to the database.
  • the present embodiment may also be based on the virtual server implemented by the physical server combined with the network function to virtualize the NFV technology.
  • One BNG and the second BNG are common BNGs.
  • Those skilled in the art can use the NFV technology to virtualize the first BNG and the second BNG having the above functions on the physical server by reading the present application. I will not repeat them here.
  • the present application provides a system 700 for switching a primary BNG and a standby BNG, where the system includes a database 702, a first BGN 701, and a second BGN 703, wherein the first BNG 701 processes the first user. business.
  • the first BGN 701 is configured to use the shared attribute information of the first BNG 701 and the second BNG 703.
  • the static information of the first user and the dynamic information generated by the first user's service on the first BNG 701 are written into the database 702.
  • the second BNG 703 is configured to: after the shared attribute information of the first BNG 701 and the second BNG 703 is written to the database 702 until the second BNG 703 is switched to be the primary BNG, The shared attribute information of the first BNG 701 and the second BNG 703 is read in the database 702.
  • the second BNG 703 reads from the database after the static information of the first user is written by the first BNG 701 to the database until the second BNG 703 is switched to be a primary BNG.
  • the static information of the first user and when the first BNG 701 fails to continue processing the service, the second BNG 703 reads the dynamic information generated by the service on the first BNG 701 from the database.
  • the dynamic information generated by the service on the first BNG 701 is synchronously written into the database 702 by the first BNG 701.
  • the second BNG 703 takes over the first BNG 701 to process the service.
  • the second BNG 703 is further configured to: when the primary BNG is switched and the first BNG 701 is processed, the dynamic information generated by the service on the second BNG 703 is written. Go to the database.
  • the database 702 is further configured to store dynamic information generated by the service on the second BNG 703.
  • the database 702 is configured to store shared attribute information of the first BNG 701 and the second BNG 703 written by the first BNG 701, static information of the first user, and the service in the first Dynamic information generated on a BNG.
  • the specific implementation of the first BNG 701 may refer to the functions and implementation steps of the first BNG in the methods of FIG. 3 and FIG. 4, and the database 702 may refer to the database in the method described in FIG. 3 and FIG. Features and implementation steps.
  • the function and implementation steps of the second BNG in the method of FIG. 3 and FIG. 4 may be referred to for the second BNG 703.
  • details are not described herein again.
  • the disclosed systems and methods can be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the modules is only a logical function division.
  • there may be another division manner for example, multiple modules or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional module in each embodiment of the present invention may be integrated into one processing unit, or each module may exist physically separately, or two or more modules may be integrated into one unit.
  • the above integrated modules can be implemented in the form of hardware or in the form of hardware plus software functional units.
  • the computer can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be passed from a website site, computer, server or data center Wired (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, redwire, wireless microwave, etc.) to another website site, computer, server, or data center.
  • Wired eg, coaxial cable, fiber optic, digital subscriber line (DSL)
  • wireless eg, redwire, wireless microwave, etc.
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium, an optical medium, or a semiconductor medium or the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本申请提供了一种切换主BNG和备BNG的方法和系统，该系统包括第一BNG、第二BNG和数据库，第一BNG为主BNG，第二BNG为备BNG，第一BNG处理第一用户的业务，当第一BNG和第二BNG的共有属性信息被写入到所述数据库中之后至所述第二BNG切换为主BNG之前，第二BNG从所述数据库中读取所述共有属性信息。当所述第一用户的静态信息被第一BNG写入到所述数据库中之后至所述第二BNG切换为主BNG之前，第二BNG从所述数据库中读取所述静态信息。当所述第一BNG出现故障不能继续处理所述业务时，第二BNG从所述数据库中读取所述业务在所述第一BNG上生成的动态信息。第二BNG切换为主BNG并接替第一BNG处理所述业务。上述方案可以减少主BNG和备BNG之间的通信资源浪费，提高备BNG的CPU资源的效率。

Description

一种切换主宽带网络网关BNG和备BNG的方法、系统和BNG
本申请要求于2017年6月8日提交中国专利局、申请号为201710429393.1、申请名称为“一种切换主宽带网络网关BNG和备BNG的方法、系统和BNG”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信领域，尤其涉及一种切换主宽带网络网关(英文：broadband network gateway，简称：BNG)和备BNG的方法、系统和BNG。
背景技术
在用户通过多个BNG接入网络的场景下，该多个BNG可以通过虚拟路由冗余协议(英文：Virtual Router Redundancy Protocol，简称：VRRP)形成一个VRRP组，并协商出该VRRP组的主BNG和备BNG，该VRRP组相当于一台虚拟路由器，局域网内的主机只需知道这个虚拟路由器的网际互联协议(英文：Internet Protocol，简称：IP)地址，并不需要知道具体某个BNG的IP地址，将局域网内主机的缺省网关设置为该虚拟路由器的IP地址，主机就可以利用该虚拟网关与外部网络进行通信。为了减小BNG故障对业务的影响，提高网络的稳定性，VRRP组中的每个BNG可以通过双向转发检测(英文：Bidirectional Forwarding Detection，简称：BFD)或者以太网运营管理维护(英文：Ethernet Operations Administration Maintenance，简称：ETH OAM)对连接该BNG的设备间的通信链路进行快速故障检测。当所述通信链路出现故障时，通过BFD或ETH OAM功能，可以在毫秒级时间内探测到链路故障，配合VRRP协议，可以快速进行主备切换。
在上述主BNG和备BNG切换的过程中，为了确保用户业务在故障发生时不中断，就需要在VRRP协议确定主BNG和备BNG之后，将主BNG和备BNG的共有属性信息和用户的业务信息一起备份到备BNG，导致备BNG一直处于备份状态，备BNG一直运行但并不处理用户的业务，这样就会造成备BNG与主BNG的通信资源浪费和备BNG的中央处理器(英文：central processing unit,CPU)处理资源的浪费。
发明内容
本申请实施例提供了一种切换主BNG和备BNG的方法、系统和BNG，可以降低主BNG与备BNG的通信资源的浪费和备BNG的CPU资源的浪费。
第一方面，本发明实施例提供了一种切换主BNG和备BNG的方法，该方法应用于包括数据库、第一BNG和第二BNG的系统中，其中，所述第一BNG为主BNG，所述第二BNG为备BNG，所述主BNG处理第一用户的业务，所述方法包括：
在所述第一BNG和所述第二BNG的共有属性信息被所述第一BNG写入到所述数据库之后至所述第二BNG切换为主BNG之前，所述第二BNG从所述数据库中读取所述第一BNG和所述第二BNG的共有属性信息。
在所述第一用户的静态信息被所述第一BNG写入到所述数据库之后至所述第二BNG切换为主BNG之前，所述第二BNG从所述数据库中读取所述第一用户的静态信息。
当所述第一BNG出现故障不能继续处理所述业务时，所述第二BNG从所述数据库中读取所述业务在所述第一BNG上生成的动态信息，所述业务在所述第一BNG上生成的动态信息由所述第一BNG同步写入到所述数据库。
所述第二BNG切换为主BNG并接替所述第一BNG处理所述业务。
通过上述方案，所述第一BNG不需要将所述第一BNG和所述第二BNG的共有属性信息、所述第一用户的静态信息和所述业务在所述第一BNG上生成的动态信息一起直接备份到备BNG，导致备BNG一直运行但不处理用户的业务，造成备BNG通信资源的浪费和CPU资源的浪费。此外，第二BNG仅在出现故障时，从所述数据库中读取所述业务在所述第一BNG上生成的动态信息，这样就可以进一步降低备BNG的CPU资源的浪费。
结合第一方面，在第一种可能的实现方式中，所述方法还包括：
当所述第二BNG切换为主BNG并接替所述第一BNG处理所述业务时，所述第二BNG将所述业务在所述第二BNG上生成的动态信息同步写入所述数据库。
通过上述方法，所述第二BNG可以将所述业务在所述第二BNG上生成的动态信息备份到所述数据库，以使当第二BNG出现故障时，所述第一BNG可以从所述数据库中读取所述业务在所述第二BNG上生成的动态信息并接替所述第二BNG处理所述第一用户的业务，提高网络的稳定性。
结合第一方面，在第二种可能的实现方式中，所述第一BNG和所述第二BNG通过VRRP确定所述第一BNG为主BNG，所述第二BNG为备BNG。
上述方案通过VRRP将所述第一BNG和所述第二BNG形成一个VRRP备份组，相当于一台虚拟路由器。当所述第一BNG出现故障时，由所述第二BNG接替第一BNG处理所述第一用户的业务，这样由所述第一BNG和所述第二BNG组成的VRRP备份组就可以实现不间断处理所述第一用户的业务。
第二方面，本发明实施例提供了一种切换主BNG和备BNG的方法，所述方法应用于包括数据库、第一BNG和第二BNG的系统中。所述主BNG处理第一用户的业务。所述方法包括：
当确定所述第一BNG为主BNG，所述第二BNG为备BNG时，所述第一BNG将所述第一BNG和所述第二BNG的共有属性信息、所述第一用户的静态信息和所述第一用户的业务在所述第一BNG上生成的动态信息写入到所述数据库中。
在所述第一BNG和所述第二BNG的共有属性信息被所述第一BNG写入到所述数据库之后至所述第二BNG切换为主BNG之前，所述第二BNG从所述数据库中读取所述第一BNG和所述第二BNG的共有属性信息。
在所述第一用户的静态信息被所述第一BNG写入到所述数据库之后至所述第二BNG切换为主BNG之前，所述第二BNG从所述数据库中读取所述第一用户的静态信息。
当所述第一BNG出现故障不能继续处理所述业务时，所述第二BNG从所述数据库中读取所述业务在所述第一BNG上生成的动态信息。所述业务在所述第一BNG上生成的动态信息由所述第一BNG写入到所述数据库中。
所述第二BNG切换为主BNG并接替所述第一BNG处理所述第一用户的业务。
结合第二方面，在第一种可能的实现方式中，所述方法还包括：当所述第二BNG切换为主BNG并接替所述第一BNG处理所述业务时，所述第二BNG将所述业务在所述第二BNG上生成的动态信息同步写入到所述数据库。
当所述第一BNG故障恢复时，所述第一BNG从所述数据库中读取所述业务在所述第二BNG上生成的动态信息。
所述第一BNG接替所述第二BNG处理所述业务。
结合第二方面，在第二种可能的实现方式中，所述第一BNG和所述第二BNG通过VRRP确定所述第一BNG为主BNG，所述第二BNG为备BNG。
第三方面，本发明提供了一种BNG，所述BNG为系统中的第二BNG，所述系统号包括数据库和第一BNG。所述第二BNG为备BNG。所述第一BNG为主BNG。所述第一BNG处理第一用户的业务。所述第二BNG包括读取单元和处理单元。
读取单元用于在所述第一BNG和所述第二BNG的共有属性信息被所述第一BNG写入到所述数据库之后至所述第二BNG切换为主BNG之前，从所述数据库中读取所所述第一BNG和所述第二BNG的共有属性信息。以及在所述第一用户的静态信息被所述第一BNG写入到所述数据库之后至所述第二BNG切换为主BNG之前，从所述数据库中读取所述第一用户的静态信息。
所述读取单元还用于当所述第一BNG出现故障不能继续处理所述业务时，从所述数据库中读取所述业务在所述第一BNG上生成的动态信息。所述业务在所述第一BNG上生成的动态信息由所述第一BNG同步写入到所述数据库。
处理单元用于将所述第二BNG切换为主BNG并使所述第二BNG接替所述第一BNG处理所述业务。
上述第二BNG不会被被动备份所述第一BNG和所述第二BNG的共有属性信息、所述第一用户的静态信息和所述业务在所述第一BNG上生成的动态信息，第二BNG可以从所述数据库中读取上述信息，避免所述第二BNG只能一直处于运行状态时但不能处理，减少所述第二BNG资源的浪费。并且所述第二BNG还可以仅在所述第一BNG出现故障时再从所述数据库中读取所述业务在所述主BNG上生成的动态信息，这样可以提高所述第二BNG的CPU资源的效率。
结合第三方面，在一种可能的实现方式中，所述第二BNG还包括写入单元，所述写入单元用于当所述第二BNG处理所述业务时，将所述业务在所述第二BNG上生成的动态信息同步写入到所述数据库。
第四方面，本发明提供了一种切换主BNG和备BNG的系统。所述系统包括数据库、第一BGN和第二BGN。所述第一BNG处理第一用户的业务。
当确定所述第一BNG为主BNG，所述第二BNG为备BNG时，所述第一BGN用于将所述第一BNG和所述第二BNG的共有属性信息、所述第一用户的静态信息和所述第一用户的业务在所述第一BNG上生成的动态信息写入到所述数据库中。
所述第二BNG用于在所述第一BNG和所述第二BNG的共有属性信息被所述第一BNG写入到所述数据库之后至所述第二BNG切换为主BNG之前，从所述数据库中读取所述第一BNG和所述第二BNG的共有属性信息。在所述第一用户的静态信息被所述第一BNG 写入到所述数据库之后至所述第二BNG切换为主BNG之前，所述第二BNG从所述数据库中读取所述第一用户的静态信息。以及当所述第一BNG出现故障不能继续处理所述第一用户的业务时，从所述数据库中读取所述第一用户的业务在所述第一BNG上生成的动态信息。所述业务在所述第一BNG上生成的动态信息由所述第一BNG同步写入到所述数据库中。并用于接替所述第一BNG处理所述第一用户的业务；
所述数据库用于存储所述第一BNG写入的所述第一BNG和所述第二BNG的共有属性信息、所述第一用户的静态信息和所述业务在所述第一BNG上生成的动态信息。
结合第四方面，在一种可能的实现方式中，所述第二BNG，还用于当切换为主BNG并接替所述第一BNG处理所述业务时，将所述业务在所述第二BNG上生成的动态信息同步写入到所述数据库。
所述数据库还用于存储所述业务在所述第二BNG上生成的动态信息。
第五方面，本申请提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述第一方面、第二方面以及各个可能实现方式的所述的方法。
附图说明
图1为本申请实施例提供的一种组网架构示意图。
图2为本发明实施例提供的一种应用场景示意图。
图3为本发明实施例提供的一种主BNG和备BNG切换的方法流程示意图。
图4为本发明实施例提供的另一种主BNG和备BNG切换的方法流程示意图。
图5为本发明实施例提供的一种BNG结构示意图。
图6为本发明实施例提供的另一种BNG结构示意图。
图7为本发明实施例提供的一种主BNG和备BNG切换的系统结构示意图。
具体实施方式
下面将结合附图对本申请作进一步详细描述。
图1提供了一种主BNG和备BNG切换方法的组网架构示意图，该架构包括主机A、主机B和主机C，局域网交换机(英文：local area network switch，简称：LSW)LSW1和LSW2，主BNG1和备BNG2，以及外部网络。BNG可以是宽带接入服务器(英文：broadband access server，简称：BAS)、也可以是宽带远程接入服务器(英文：broadband remote access server，BRAS)、可以是宽带网络接入服务器(英文：broadband network access server，BNAS)、可以是二层隧道协议网络服务器(英文：L2TP network server，LNS)、或者是业务路由器(英文：service router，SR)等设备。通过VRRP将BNG1和BNG2组成一台虚拟路由器，局域网中的主机A、主机B和主机C只要了解所述虚拟路由器的IP地址就可以接入BNG，并与外部网络进行通信，局域网中的主机A、主机B和主机C并不需要了解具体BNG1和BNG2的IP地址。VRRP协议使用一定的机制保证当BNG1出现故障不能继续处理主机A、主机B和主机C的业务时，及时将主机A、主机B和主机C的业务切换到备BNG2，从而保证主机A、主机B和主机C接入业务的连续性和可靠性。
对于BNG1和BNG2来说，需要通过VRRP协商出主BNG和备BNG，例如确定BNG1为主BNG，BNG2为备BNG。下面将以BNG1为主BNG，BNG2为备BNG为例，对主BNG和 备BNG切换进行说明。以主机A为例，当主机A向BNG1和BNG2组成的虚拟路由器发送上线请求时，BNG1和BNG2都会收到该上线请求，但由于BNG1为主BNG，则BNG1处理该上线请求，包括认证、实时计费和授权等，而作为备BNG的BNG2则会主动丢弃该上线请求。主机A通过BNG1上线后，BNG1通过传输控制协议(英文：Transmission Control Protocol，简称：TCP)将BNG1和BNG2的共有属性信息和主机A的用户信息同步到BNG2中，BNG2针对所述用户信息生成对应的用户业务，以保证当BNG1出现故障时，BNG2可以顺利接管主机A的业务，确保主机业务的连续性，减小故障造成的损失。BNG1和BNG2对主机B和主机C的处理流程与主机A类似。
但上述方法为了确保主机A、主机B和主机C接入BNG的业务不会因为BNG1出现故障而中断，需要将BNG1中的BNG1和BNG2的共有属性信息、用户的静态信息以及用户业务在主BNG上生成的用户动态信息备份到BNG2中。在实际部署备份业务时，BNG1和BNG2的共有属性信息包括相同的IP地址池、虚拟局域网(英文：virtual local area network，简称：VLAN)、服务质量(英文：quality of service，简称：QoS)策略等参数，而通常情况下BNG1会将上述BNG1和BNG2的共有属性信息、用户的静态信息以及用户业务在BNG1上生成的用户的动态信息不作区分统一备份到BNG2中，这样不仅导致BNG2处于被动备份状态，而且还会使BNG2仅处于运行状态但不能处理主机的上线业务，只有在BNG1出现故障而将BNG2设置成主BNG时，BNG2才可以处理主机A、主机B和主机C的上线业务。此外，BNG2在进行备份时，是将BNG1和BNG2的共有属性信息和BNG1中的用户静态信息和用户业务在BNG1上生成的动态信息统一备份，不作区分，这种统一备份会导致BNG2执行不必要的备份操作，造成BNG1与BNG2间通信资源的浪费和BNG1和BNG2的CPU资源的浪费。
为了减少BNG2处于备状态时不能处理上线业务而造成的资源浪费，请参阅图2，为本申请提供的一种解决上述技术问题的应用场景示意图，在该具体实施方式中，使用VRRP协议既可以将BNG1和BNG2配置为一个VRRP组，例如BNG1为主BNG，BNG2为备BNG。也可以使用VRRP协议将BNG1和BNG2配置为两个VRRP组实现负载分担，相互备份，例如，在VRRP组1中BNG1是主BNG，BNG2为备BNG，在VRRP组2中BNG2是主BNG，BNG1为备BNG，这样BNG1和BNG2都可以处理主机上线业务，例如主机A和主机B的上线请求由VRRP组1中的BNG1处理，BNG2为VRRP组1的备BNG。主机C和主机D的上线请求业务由VRRP组2中的BNG2处理，此时BNG1为VRRP组2中的备BNG。对于VRRP组1来说，BNG1和BNG2的共有属性信息和由BNG1处理的用户的静态信息并不需要再直接备份到BNG2中，可以由BNG1写入到数据库(英文：database，简称：DB)中，所述DB保存VRRP组1的所述BNG1和BNG2的共有属性信息和由BNG1处理的用户的静态信息。同样，VRRP组2的BNG2也可以将VRRP组2的共有属性信息和由BNG2处理的用户的静态信息写入所述DB中，所述DB保存VRRP组2的所述共有属性信息和由BNG2处理的用户的静态信息。举例来说，在VRRP组1中确定BNG1和BNG2的主备关系时，即确定在VRRP组1中BNG1为主BNG，BNG2为备BNG时，BNG1将需要备份的VRRP组1的共有属性信息、由BNG1处理的用户的静态信息以及由BNG1处理的用户的业务在BNG1上生成的动态信息写入到DB中以进行备份。BNG2可以从所述DB中读取BNG1和BNG2的共有属性信息以及由BNG1处理的用户的静态信息。如果 VRRP组1中的BNG1发生故障不能继续处理用户的上线业务时，BNG2可以从所述DB中获取由BNG1处理的用户的业务在BNG1上生成的动态信息，以接替BNG1继续处理BNG1所处理的用户的业务。这样BNG2不仅不会处理被动的备份状态，而且可以分类从所述DB中读出需要的信息，减少通信资源的浪费和CPU资源的浪费。下面以本申请实施例提供的主BNG和备BNG切换为例，进一步说明主BNG和备BNG间切换的工作过程。
参见图3，提供了一种切换主BNG和备BNG的方法流程示意图，所述方法应用于包括数据库、第一BNG和第二BNG的系统中，所述第一BNG为主BNG，所述第二BNG为备BNG，所述第一BNG处理第一用户的业务，所述方法具体包括：
S301：在所述第一BNG和所述第二BNG的共有属性信息被所述第一BNG写入到所述数据库之后至所述第二BNG切换为主BNG之前，所述第二BNG从所述数据库中读取所述第一BNG和所述第二BNG的共有属性信息。
在一个具体的实施方式中，可选的，所述第一BNG和所述第二BNG可以通过VRRP确定所述第一BNG为主BNG，所述第二BNG为备BNG，将所述第一BNG和所述第二BNG组成一个VRRP组，该VRRP组相当于一台虚拟路由器。在实际部署备份业务时，第一BNG和第二BNG需要保证配置的一致性，例如对第一BNG和第二BNG配置相同的IP地址池、VLAN和QoS策略等参数，这些参数为第一BNG和第二BNG的共有属性信息，即第一BNG和第二BNG的共有属性信息至少包括VRRP组的IP地址池、VLAN和QoS策略。第一BNG将所述共有属性信息备份到所述数据库中。由于所述第一BNG和所述第二BNG的所述共有属性信息是在确定第一BNG和第二BNG的主备关系时由所述第一BNG向所述数据库中写入的，即当确定所述第一BNG为主BNG，所述第二BNG为备BNG时，第一BNG就会向所述数据库中写入所述共有属性信息。因此第一BNG会快速的将所述共有属性信息写入所属数据库中。第二BNG在第一BNG向数据库中写入所述共有属性信息之后至第二BNG切换为主BNG之前的任何时间，第二BNG都可以从所述数据库中读取所述共有属性信息。
S302：在所述第一用户的静态信息被所述第一BNG写入到所述数据库之后至所述第二BNG切换为主BNG之前，所述第二BNG从所述数据库中读取所述第一用户的静态信息。
在一个具体的实施方式中，当第一用户的业务接入第一BNG时，第一BNG就会将第一用户的静态信息写入到所述数据库中进行备份。所述第一用户的静态信息包括第一用户的介质访问控制(英文：media access control,简称：MAC)地址、会话标识(英文：session identifier,简称：Session ID)等不会随着时间发生频繁变化的信息。举例来说，当第一BNG将所述第一用户的MAC地址和会话ID等第一用户的静态信息写入到所述数据库之后至所述第二BNG切换为主BNG之前的任何时间，第二BNG都可以从所述数据库读取所述第一用户的静态信息，以和所述第一BNG共享所述第一用户的静态信息。
S303：当所述第一BNG出现故障不能继续处理所述业务时，所述第二BNG从所述数据库中读取所述业务在所述第一BNG上生成的动态信息。所述业务在所述第一BNG上生成的动态信息由所述第一BNG同步写入到所述数据库。
在一个具体的实施方式中，为了减小BNG故障对业务的影响，可以通过BFD或ETH OAM实现链路故障快速检测。当检测到第一BNG出现故障不能继续处理第一用户的业务时，第二BNG从所述数据库中读取第一用户的业务在第一BNG上生成的动态信息。所述动态信息包括上行/下行包(英文：up/down-pack)、上行/下行字节(英文：up/down-byte)等进行实时流量统计的用于计费的信息，所述第一用户的业务在所述第一BNG上生成的动态信息由所述第一BNG同步写入到所述数据库中。
S304：所述第二BNG切换为主BNG并接替所述第一BNG处理所述业务。
在一个具体的实施方式中，第二BNG由备BNG切换为新的BNG，并接替第一BNG继续处理第一用户的业务。
本发明实施例的上述方案，通过利用数据库将主BNG和备BNG的共有属性信息、第一用户的业务在第一BNG上生成的动态信息和第一用户的静态信息进行分类备份，使所述第一BNG不需要将所述第一BNG和所述第二BNG的共有属性信息、所述第一用户的静态信息和所述业务在所述第一BNG上生成的动态信息被直接备份到备BNG，导致备BNG一直运行但不能处理业务，造成BNG间通信资源的浪费和BNG的CPU资源的浪费。此外，第二BNG仅在出现故障时，从所述数据库中读取所述业务在所述第一BNG上生成的动态信息，这样就可以进一步降低对备BNG的CPU资源的浪费。利用数据库将主BNG和备BNG的共有属性信息、第一用户的静态信息和第一用户的业务在第一BNG上生成的动态信息从所述主BNG和备BNG上分离出来，还可以实现备份信息与主BNG和备BNG的解耦。
可选的，所述方法还包括：当所述第一BNG的故障恢复时，将所述第一用户的业务回切到所述第一BNG，所述第一BNG从所述数据库中获取所述业务在所述第二BNG上生成的动态信息所述业务在所述第二BNG上生成的动态信息由所述第二BNG同步写入所述数据库。
在一个具体的实施方式中，当所述第一BNG的故障被排除，可以处理第一用户的业务时，将第一用户的业务回切到第一BNG，第一用户的业务由第一BNG处理，第一BNG可以从所述数据库中获取处理第一用户的业务所需要的第一用户的动态信息。第一用户的动态信息是由第二BNG备份到所述数据库中的。
请参阅图4，为本申请提供的另一种切换主BNG和备BNG方法流程示意图，所述方法应用于包括数据库、第一BNG和第二BNG的系统中，所述第一BNG处理第一用户的业务，所述方法包括：
S401：当确定所述第一BNG为主BNG，所述第二BNG为备BNG时，所述第一BNG将所述第一BNG和所述第二BNG的共有属性信息、所述第一用户的静态信息和所述第一用户的业务在所述第一BNG上生成的动态信息写入到所述数据库中。
可选的，所述第一BNG和所述第二BNG通过VRRP确定所述第一BNG为主BNG，所述第二BNG为备BNG。
在一个具体的实施方式中，第一BNG和第二BNG通过VRRP形成一个VRRP组，该VRRP组在功能上相当于一台虚拟路由器，该虚拟路由器配置虚拟的IP地址和虚拟MAC地址。局域网中的第一用户将所述虚拟路由器的虚拟IP地址设置为默认网关，并通过所述虚拟路由器与外部网络通信。通过VRRP从所述VRRP组中的第一BNG和第二BNG 张根据优先级确定主BNG和备BNG,例如确定优先级高的第一BNG为主BNG，优先级较低的第二BNG为备BNG。第一BNG通过发送免费的地址解析协议(英文：Address Resolution Protocol,简称ARP)报文，将所述虚拟路由器的虚拟MAC地址通知给第二BNG和第一用户，从而承担第一用户的报文转发的任务，帮助第一用户与外部网络通信。
在通过VRRP协议确定所述第一BNG为主BNG，第二BNG为备BNG时，第一BNG将第一BNG和第二BNG的共有属性信息、第一用户的静态信息以及第一用户在第一BNG上生成的动态信息写入到数据库进行备份，其中所述第一用户在所述第一BNG上生成的动态信息同步写入到所述数据库中。所述第一BNG和所述第二BNG的共有属性信息包括为第一BNG和第二BNG配置的相同的IP地址池、VLAN和QoS策略等参数。所述第一用户的静态信息包括MAC地址、会话ID等不会随着时间发生频繁变化的信息。所述第一用户的业务在第一BNG上生成的动态信息包括up/down-pack、up/down-byte等进行实时流量统计的用于计费的信息。上述第一BNG和第二BNG的共有属性信息、第一用户的静态信息和第一用户的业务在第一BNG上生成的动态信息都用于BNG处理第一用户与外部进行通信的业务。
S402：在所述第一BNG和所述第二BNG的共有属性信息被所述第一BNG写入到所述数据库之后至所述第二BNG切换为主BNG之前，所述第二BNG从所述数据库中读取所述第一BNG和所述第二BNG的共有属性信息。
在一个具体的实施方式中，在确定第一BNG为主BNG，第二BNG为备BNG时，第一BNG就将所述第一BNG和所述第二BNG的共有属性信息写入到所述数据库中，以在数据库中进行备份。所述第二BNG可以在所述共有属性信息写入到所述数据库之后至所述第二BNG切换为主BNG之前，从所述数据库中读取所述共有属性信息。所述共有属性信息包括IP地址池、VLAN和QoS策略等参数。
S403：在所述第一用户的静态信息被所述第一BNG写入到所述数据库之后至所述第二BNG切换为主BNG之前，所述第二BNG从所述数据库中读取所述第一用户的静态信息。
在一个具体的实施方式中，在确定所述第一BNG为主BNG，所述第二BNG为备BNG时，第一BNG就会将第一用户的静态信息写入到所述数据库。第二BNG在所述第一BNG将所述第一用户的静态信息写入到所述数据库之后至所述第二BNG切换为主BNG之前的过程中可以从所述数据路中读取所述第一用户的静态信息，所述第一用户的静态信息包括第一用户的MAC地址和会话标识。
S404：当所述第一BNG出现故障不能继续处理所述业务时，所述第二BNG从所述数据库中读取所述业务在所述第一BNG上生成的动态信息。所述业务在所述第一BNG上生成的动态信息由所述第一BNG同步写入到所述数据库中。
在一个具体的实施例中，第一BNG作为主BNG承担处理第一用户业务的任务，第二BNG作为备BNG处于就绪监听状态。第二BNG可以使用BFD监视第一BNG上IP地址的可达性，如果第一BNG发生故障，第二BNG可以利用BFD感知故障变化，此时第二BNG将从所述数据库中读取所述业务在第一BNG上生成的动态信息，所述动态信息包括up/down-pack、up/down-byte等进行实时流量统计的用于计费的信息，所述业务 在所述第一BNG上生成的动态信息由所述第一BNG同步写入到所述数据库中。
S405：所述第二BNG切换为主BNG并接替所述第一BNG处理所述业务。
在一个具体的实施例中，为了保证网络传输的稳定性，可以在第二BNG上使用BFD技术监视第一BNG的状态，使得第一BNG发生故障时，第二BNG能够立刻切换为新的主BNG，并由第二BNG接替所述第一BNG处理第一用户的业务。
可选的，所述方法还包括：当所述第二BNG切换为主BNG并接替所述第一BNG处理所述业务时，所述第二BNG将所述业务在所述第二BNG上生成的动态信息写入到所述数据库。当所述第一BNG故障恢复时，所述第一BNG从所述数据库中读取所述业务在所述第二BNG上生成的动态信息。所述第一BNG接替所述所述第二BNG处理所述业务。
在一个具体的实施方式中，当第二BNG成为新的主BNG并接替第一BNG处理所述业务时，第二BNG需要将第一用户的业务在第二BNG上生成的动态信息写入到所述数据库。当第一BNG的故障恢复时，第一BNG可以从所述数据库中读取所述业务在第二BNG上生成的动态信息。第一BNG切换为主BNG接替第二BNG处理第一用户的业务。
请参阅图5，为本申请提供了一种BNG 500，所述BNG 500应用于包括数据库和第一BNG的系统中，所说BNG 500为所述系统中的第二BNG，所述第一BNG为主BNG，所述第二BNG 500为备BNG，所述第一BNG处理第一用户的业务，所述第二BNG 500包括读取单元501和处理单元502。
读取单元501用于在所述第一BNG和所述第二BNG 500的共有属性信息被所述第一BNG写入到所述数据库之后至所述第二BNG 500切换为主BNG之前，从所述数据库中读取所所述第一BNG和所述第二BNG 500的共有属性信息，以及在所述第一用户的静态信息被所述第一BNG写入到所述数据库之后至所述第二BNG 500切换为主BNG之前，从所述数据库中读取所述第一用户的静态信息。
所述读取单元501还用于当所述第一BNG出现故障不能继续处理所述业务时，从所述数据库中读取所述业务在所述第一BNG上生成的动态信息，所述业务在所述第一BNG上生成的动态信息由所述第一BNG同步写入到所述数据库。
处理单元502用于将所述第二BNG 500切换为主BNG并使所述第二BNG 500接替所述第一BNG处理所述业务。
具体实施方式中，所述读取单元501的具体实施方式可以参考图3和图4中第二BNG进行主BNG和备BNG从所述数据库中读取第一BNG和所述第二BNG的共有属性信息、第一用户的静态信息和所述第一用户的业务在第一BNG上生成的动态信息的具体条件和过程，为了简介，此处不再赘述。所述处理单元502的具体实施方式可以参考图3的步骤304和图4的步骤405中第二BNG切换为主BNG并接替所述第一BNG处理所述业务，为了简洁，此处不再赘述。
可选的，所述第二BNG还包括写入单元503，写入单元503用于当所述处理单元处理所述业务时，将所述业务在所述第二BNG上生成的动态信息写入到所述数据库。
请参阅图6，为本申请提供了另一种BNG 600的实施例，所述BNG 600应用于包括数据库和第一BNG的系统中，所述BNG为所述系统中的第二BNG，所述第一BNG为主BNG，所述第二BNG为备BNG，所述主BNG处理第一用户的业务，所述第二BNG 600 包括通信接口601和处理器602。图6所示的BNG 600可以为前述方法实施例图3和图4中的第二BNG，可以实现上述第二BNG的功能。所述第二BNG包括通信接口601、处理器602、存储器603以及连接该处理器602、通信接口601和存储器603的总线604。通信接口601用于第二BNG与数据库进行通信，存储器603用于存放程序指令，存储器603可能包含高速随机存取存储器(英文：random access memory，简称：RAM)，也可能还包括非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器，处理器602可以调用存储器603中存放的程序指令执行相应功能。
在一个具体的实施方式中：
所述通信接口601用于在所述第一BNG和所述第二BNG 600的共有属性信息被所述第一BNG写入到所述数据库之后至所述第二BNG切换为主BNG之前，从所述数据库中读取所述第一BNG和所述第二BNG 600的共有属性信息，以及在所述第一用户的静态信息被所述第一BNG写入到所述数据库之后至所述第二BNG 600切换为主BNG之前，从所述数据库中读取所述第一用户的静态信息。
所述通信接口601还用于当所述第一BNG出现故障不能继续处理所述业务时，从所述数据库中接收所述业务在所述第一BNG上生成的动态信息，所述业务在所述第一BNG上生成的动态信息由所述第一BNG同步写入到所述数据库。
所述处理器602用于切换为主BNG并接替所述第一BNG处理所述业务。
可选的，所述通信接口601还用于当所述处理器处理所述业务时，将所述业务在所述第二BNG上生成的动态信息发送到所述数据库。
该实施方式中，所述通信接口601和所述处理器602的具体实现可参考图3和图4中所述第二BNG的功能和实施的步骤，为了简洁，不再赘述。
需要说明的是，该实施方式中，除了上述几种通过处理器执行存储器上的程序代码指令方式等常规方式之外，本实施方式也可以基于物理服务器结合网络功能虚拟化NFV技术实现的虚拟第一BNG和第二BNG。本领域技术人员通过阅读本申请即可结合NFV技术在物理服务器上虚拟出具有上述功能的第一BNG和第二BNG。此处不再赘述。
请参阅图7，为本申请提供了一种切换主BNG和备BNG的系统700，所述系统包括数据库702、第一BGN 701和第二BGN 703，其中，第一BNG 701处理第一用户的业务。
当确定所述第一BNG 701为主BNG，所述第二BNG 703为备BNG时，所述第一BGN701用于将所述第一BNG 701和所述第二BNG 703的共有属性信息、所述第一用户的静态信息和所述第一用户的业务在所述第一BNG 701上生成的动态信息写入到所述数据库702中。
所述第二BNG 703用于在所述第一BNG 701和所述第二BNG 703的共有属性信息被写入到所述数据库702之后至所述第二BNG 703切换为主BNG之前，从所述数据库702中读取所述第一BNG 701和所述第二BNG 703的共有属性信息。在所述第一用户的静态信息被所述第一BNG 701写入到所述数据库之后至所述第二BNG 703切换为主BNG之前，所述第二BNG 703从所述数据库中读取所述第一用户的静态信息。以及当所述第一BNG 701出现故障不能继续处理所述业务时，所述第二BNG 703从所述数据库中读取所述业务在所述第一BNG 701上生成的动态信息。所述业务在所述第一BNG701上生成的动态信息由所述第一BNG 701同步写入到所述数据库702中。所述第二 BNG 703接替所述第一BNG 701处理所述业务。
可选的，所述第二BNG 703还用于当切换为主BNG并接替所述第一BNG 701处理所述业务时，将所述业务在所述第二BNG 703上生成的动态信息写入到所述数据库。
所述数据库702还用于存储所述业务在所述第二BNG 703上生成的动态信息。
所述数据库702用于存储所述第一BNG 701写入的所述第一BNG 701和所述第二BNG 703的共有属性信息、所述第一用户的静态信息和所述业务在所述第一BNG上生成的动态信息。
该具体实施方式中，所述第一BNG 701的具体实现可以参考图3和图4方法中的第一BNG的功能和实施步骤，所述数据库702可以参考图3和图4所述方法中数据库的功能和实施步骤。第二BNG 703可以参考图3和图4方法中第二BNG的功能和实施步骤，为了简介，此处不再赘述。
在本申请所提供的几个实施例中，应该理解到，所公开的系统和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个模块或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的模块可以是或者也可以不是物理上分开的，作为模块显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能模块可以集成在一个处理单元中，也可以是各个模块单独物理存在，也可以两个或两个以上模块集成在一个单元中。上述集成的模块既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红线、无线微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，光介质、或者半导体介质等。

Claims (10)

  1. 一种切换主宽带网络网关BNG和备BNG的方法，其特征在于，所述方法应用于包括数据库、第一BNG和第二BNG的系统中，所述第一BNG为主BNG，所述第二BNG为备BNG，所述主BNG处理第一用户的业务，所述方法包括：
    在所述第一BNG和所述第二BNG的共有属性信息被所述第一BNG写入到所述数据库之后至所述第二BNG切换为主BNG之前，所述第二BNG从所述数据库中读取所述第一BNG和所述第二BNG的共有属性信息；
    在所述第一用户的静态信息被所述第一BNG写入到所述数据库之后至所述第二BNG切换为主BNG之前，所述第二BNG从所述数据库中读取所述第一用户的静态信息；
    当所述第一BNG出现故障不能继续处理所述业务时，所述第二BNG从所述数据库中读取所述业务在所述第一BNG上生成的动态信息，所述业务在所述第一BNG上生成的动态信息由所述第一BNG同步写入到所述数据库；
    所述第二BNG切换为主BNG并接替所述第一BNG处理所述业务。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    当所述第二BNG切换为主BNG并接替所述第一BNG处理所述业务时，所述第二BNG将所述业务在所述第二BNG上生成的动态信息同步写入到所述数据库。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一BNG和所述第二BNG通过虚拟路由冗余协议VRRP确定所述第一BNG为主BNG，所述第二BNG为备BNG。
  4. 一种切换主宽带网络网关BNG和备BNG的方法，其特征在于，所述方法应用于包括数据库、第一BNG和第二BNG的系统中，所述第一BNG处理第一用户的业务，所述方法包括：
    当确定所述第一BNG为主BNG，所述第二BNG为备BNG时，所述第一BNG将所述第一BNG和所述第二BNG的共有属性信息、所述第一用户的静态信息和所述第一用户的业务在所述第一BNG上生成的动态信息写入到所述数据库中；
    在所述第一BNG和所述第二BNG的共有属性信息被所述第一BNG写入到所述数据库之后至所述第二BNG切换为主BNG之前，所述第二BNG从所述数据库中读取所述第一BNG和所述第二BNG的共有属性信息；
    在所述第一用户的静态信息被所述第一BNG写入到所述数据库之后至所述第二BNG切换为主BNG之前，所述第二BNG从所述数据库中读取所述第一用户的静态信息；
    当所述第一BNG出现故障不能继续处理所述业务时，所述第二BNG从所述数据库中读取所述业务在所述第一BNG上生成的动态信息，所述业务在所述第一BNG上生成的动态信息由所述第一BNG同步写入到所述数据库中；
    所述第二BNG切换为主BNG并接替所述第一BNG处理所述业务。
  5. 根据权利要求4所述的方法，其特征在于，所述方法还包括：
    当所述第二BNG切换为主BNG并接替所述第一BNG处理所述业务时，所述第二BNG 将所述业务在所述第二BNG上生成的动态信息同步写入到所述数据库；
    当所述第一BNG故障恢复时，所述第一BNG从所述数据库中读取所述业务在所述第二BNG上生成的动态信息；
    所述第一BNG接替所述第二BNG处理所述业务。
  6. 根据权利要求4或5所述的方法，其特征在于，所述
    所述第一BNG和所述第二BNG通过虚拟路由冗余协议VRRP确定所述第一BNG为主BNG，所述第二BNG为备BNG。
  7. 一种宽带网络网关BNG，其特征在于，所述BNG为系统中的第二BNG，所述系统还包括数据库和第一BNG，所述第二BNG为备BNG，所述第一BNG为主BNG，所述第一BNG处理第一用户的业务，所述第二BNG包括：
    读取单元，用于在所述第一BNG和所述第二BNG的共有属性信息被所述第一BNG写入到所述数据库之后至所述第二BNG切换为主BNG之前，从所述数据库中读取所述第一BNG和所述第二BNG的共有属性信息，以及在所述第一用户的静态信息被所述第一BNG写入到所述数据库之后至所述第二BNG切换为主BNG之后，从所述数据库中读取所述第一用户的静态信息；
    所述读取单元，还用于当所述第一BNG出现故障不能继续处理所述业务时，从所述数据库中读取所述业务在所述第一BNG上生成的动态信息，所述业务在所述第一BNG上生成的动态信息由所述第一BNG同步写入到所述数据库；
    处理单元，用于将所述第二BNG切换为主BNG并使所述第二BNG接替所述第一BNG处理所述业务。
  8. 根据权利要求7所述的BNG，其特征在于，所述第二BGN还包括写入单元，
    所述写入单元，用于当所述第二BNG处理所述业务时，将所述业务在所述第二BNG上生成的动态信息同步写入到所述数据库。
  9. 一种切换主宽带网络网关BNG和备BNG的系统，其特征在于，所述系统包括数据库、第一BGN和第二BGN，所述第一BNG处理第一用户的业务，
    所述第一BGN，用于当确定所述第一BNG为主BNG，所述第二BNG为备BNG时，将所述第一BNG和所述第二BNG的共有属性信息、所述第一用户的静态信息和所述业务在所述第一BNG上生成的动态信息写入到所述数据库中；
    所述第二BNG，用于在所述第一BNG和所述第二BNG的共有属性信息被所述第一BNG写入到所述数据库之后至所述第二BNG切换为主BNG之前，从所述数据库中读取所述第一BNG和所述第二BNG的共有属性信息，在所述第一用户的静态信息被所述第一BNG写入到所述数据库之后至所述第二BNG切换为主BNG之前，所述第二BNG从所述数据库中读取所述第一用户的静态信息，以及当所述第一BNG出现故障不能继续处理所述业务时，从所述数据库中读取所述业务在所述第一BNG上生成的动态信息，所述业务在所述第一BNG上生成的动态信息由所述第一BNG同步写入到所述数据库中， 并接替所述第一BNG处理所述业务；
    所述数据库，用于存储所述第一BNG写入的所述第一BNG和所述第二BNG的共有属性信息、所述第一用户的静态信息和所述业务在所述第一BNG上生成的动态信息。
  10. 根据权利要求9所述的系统，其特征在于，所述第二BNG，还用于当切换为主BNG并接替所述第一BNG处理所述业务时，将所述业务在所述第二BNG上生成的动态信息同步写入到所述数据库；
    所述数据库，还用于存储所述业务在所述第二BNG上生成的动态信息。
PCT/CN2018/090135 2017-06-08 2018-06-06 一种切换主宽带网络网关bng和备bng的方法、系统和bng WO2018223991A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP18814303.6A EP3627766B1 (en) 2017-06-08 2018-06-06 Method and system for switching between active bng and standby bng

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710429393.1A CN109039680B (zh) 2017-06-08 2017-06-08 一种切换主宽带网络网关bng和备bng的方法、系统和bng
CN201710429393.1 2017-06-08

Publications (1)

Publication Number Publication Date
WO2018223991A1 true WO2018223991A1 (zh) 2018-12-13

Family

ID=64566786

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/090135 WO2018223991A1 (zh) 2017-06-08 2018-06-06 一种切换主宽带网络网关bng和备bng的方法、系统和bng

Country Status (3)

Country Link
EP (1) EP3627766B1 (zh)
CN (1) CN109039680B (zh)
WO (1) WO2018223991A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115701040A (zh) * 2021-07-16 2023-02-07 中兴通讯股份有限公司 Dbng-cp的备份方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1533100A (zh) * 2003-03-18 2004-09-29 ����ͨѶ�ɷ����޹�˾ 对基于流控制传送协议的偶联进行保护的方法
US6888937B1 (en) * 2000-09-06 2005-05-03 Cisco Technology, Inc. Managing processes of a network component
CN102447742A (zh) * 2011-11-24 2012-05-09 中兴通讯股份有限公司 一种动态数据主备同步的方法、系统及一种元数据服务器
CN102611519A (zh) * 2010-11-25 2012-07-25 上海贝尔股份有限公司 一种对无源光网络进行链路保护的方法和装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101340272B (zh) * 2008-08-25 2012-12-19 中兴通讯股份有限公司 一种双机切换方法及系统
US8626344B2 (en) * 2009-08-21 2014-01-07 Allure Energy, Inc. Energy management system and method
US9173117B2 (en) * 2013-05-02 2015-10-27 Telefonaktiebolaget L M Ericsson (Publ) Enhancing a mobile backup channel to address a node failure in a wireline network
US20160262073A1 (en) * 2015-03-04 2016-09-08 Alcatel-Lucent Usa Inc. System and method for providing maximum fill link via bonded services
CN105207874A (zh) * 2015-09-02 2015-12-30 中国联合网络通信集团有限公司 一种l2tp网络保护的方法及网络系统
CN105099793B (zh) * 2015-09-24 2019-02-05 华为技术有限公司 热备方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6888937B1 (en) * 2000-09-06 2005-05-03 Cisco Technology, Inc. Managing processes of a network component
CN1533100A (zh) * 2003-03-18 2004-09-29 ����ͨѶ�ɷ����޹�˾ 对基于流控制传送协议的偶联进行保护的方法
CN102611519A (zh) * 2010-11-25 2012-07-25 上海贝尔股份有限公司 一种对无源光网络进行链路保护的方法和装置
CN102447742A (zh) * 2011-11-24 2012-05-09 中兴通讯股份有限公司 一种动态数据主备同步的方法、系统及一种元数据服务器

Also Published As

Publication number Publication date
EP3627766B1 (en) 2022-01-26
CN109039680A (zh) 2018-12-18
EP3627766A4 (en) 2020-09-09
CN109039680B (zh) 2021-06-01
EP3627766A1 (en) 2020-03-25

Similar Documents

Publication Publication Date Title
US11533248B2 (en) Method and system of resiliency in cloud-delivered SD-WAN
US11323307B2 (en) Method and system of a dynamic high-availability mode based on current wide area network connectivity
US10567340B2 (en) Data center system
US11734138B2 (en) Hot standby method, apparatus, and system
EP2242325B1 (en) Method, system and equipment for access of a network device to a packet exchange network
US7826393B2 (en) Management computer and computer system for setting port configuration information
US7975180B2 (en) Method and apparatus for fault detection/isolation in metro ethernet service
CN110784400B (zh) N：1有状态应用网关冗余方法、系统和备用服务网关
JP2007088949A (ja) 情報処理装置、通信負荷分散方法および通信負荷分散プログラム
WO2013113228A1 (zh) 网络设备冗余备份的方法、路由设备及系统
US20160205033A1 (en) Pool element status information synchronization method, pool register, and pool element
US20230111966A1 (en) Ethernet storage system, and information notification method and related apparatus thereof
CN112087375A (zh) Wan口备援路由器的wan口切换方法、存储介质及路由器
CN112564983B (zh) 数据传输方法、装置、计算机系统和介质
WO2011110134A2 (zh) 负载分担的方法及装置、宽带接入服务器系统
WO2009152700A1 (zh) 管理网络设备端口状态的方法、系统及中转设备
WO2018223991A1 (zh) 一种切换主宽带网络网关bng和备bng的方法、系统和bng
WO2020181733A1 (zh) 一种基于vpc的多数据中心互通方法及相关设备
US11418382B2 (en) Method of cooperative active-standby failover between logical routers based on health of attached services
US8903991B1 (en) Clustered computer system using ARP protocol to identify connectivity issues
JP4133738B2 (ja) 高速ネットワークアドレス引継ぎ方法、ネットワーク装置及びプログラム
CN109450794A (zh) 一种基于sdn网络的通信方法及设备
US20230344756A1 (en) Routing method and related device
WO2022044546A1 (ja) 通信システムおよびその障害復旧方法
WO2021223646A1 (zh) 保护倒换方法及装置

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: 18814303

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018814303

Country of ref document: EP

Effective date: 20191216