WO2020001514A1 - 业务处理 - Google Patents

业务处理 Download PDF

Info

Publication number
WO2020001514A1
WO2020001514A1 PCT/CN2019/093166 CN2019093166W WO2020001514A1 WO 2020001514 A1 WO2020001514 A1 WO 2020001514A1 CN 2019093166 W CN2019093166 W CN 2019093166W WO 2020001514 A1 WO2020001514 A1 WO 2020001514A1
Authority
WO
WIPO (PCT)
Prior art keywords
bras
service data
database server
terminal device
service
Prior art date
Application number
PCT/CN2019/093166
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 新华三技术有限公司
Publication of WO2020001514A1 publication Critical patent/WO2020001514A1/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/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
    • H04L49/00—Packet switching elements
    • H04L49/35—Switches specially adapted for specific applications
    • H04L49/354—Switches specially adapted for specific applications for supporting virtual local area networks [VLAN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/55—Prevention, detection or correction of errors

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a service processing method, system, and device.
  • BRAS Broadband Remote Access Server, Broadband Remote Access Server
  • VPN Virtual Private Network
  • Support ITMS Integrated Terminal Management System
  • VoIP Voice Over Internet Protocol
  • BRAS bandwidth Remote Access Server
  • multiple BRASs can be deployed, and multiple BRASs can jointly provide services for all terminals.
  • a backup BRAS can be provided for each BRAS (hereinafter referred to as the primary BRAS).
  • the primary BRAS can be provided for each BRAS (hereinafter referred to as the primary BRAS).
  • the standby BRAS can be upgraded to the primary BRAS, and Provide BRAS services.
  • a backup BRAS12 may be provided for the main BRAS11
  • a backup BRAS22 may be provided for the main BRAS21
  • a backup BRAS32 may be provided for the main BRAS31.
  • each active BRAS corresponds to one standby BRAS, and the number of active BRAS is the same as the number of standby BRAS, that is, a large number of standby BRAS need to be deployed, which wastes BRAS resources. Moreover, most of the standby BRAS may not be really used, and the processing resources of the standby BRAS cannot be fully utilized.
  • FIG. 1 is a schematic diagram of an application scenario in an embodiment of the present application
  • FIG. 2 is a flowchart of a service processing method in an embodiment of the present application
  • FIG. 3 is a flowchart of a business processing method in another embodiment of the present application.
  • FIG. 5 is a structural diagram of a service processing device in an embodiment of the present application.
  • FIG. 6 is a structural diagram of a service processing device in another embodiment of the present application.
  • FIG. 7 is a structural diagram of a service processing device in another embodiment of the present application.
  • FIG. 8 is a structural diagram of a service processing device in another embodiment of the present application.
  • FIG. 9 is a hardware structural diagram of a BRAS in an embodiment of the present application.
  • first, second, third, etc. may be used in this application to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information.
  • word “if” can be interpreted as “at ", or "when !, or "in response to a determination”.
  • the embodiment of the present application proposes a service processing method, which is applied to a system including a management device, a database server, a BRAS, and a terminal device.
  • a schematic diagram of the application scenario of this embodiment is taken as an example, taking terminal devices 111, 112, aggregation switches 121, 122, gateway devices 131, BRAS 141, 142, 143, management devices 151, core switches 161, core routers 171, and database servers 181 as examples.
  • Figure 1 is only an example, and there is no limitation on this.
  • This article uses three BRAS as examples for illustration. In practical applications, the number of BRAS can be more, and there is no limit on this number.
  • the terminal devices 111, 112 can be, for example, a virtual machine, a PC (Personal Computer), a laptop computer, a mobile phone, a host computer, a home terminal, an E8C terminal, an IPTV (Internet Protocol Television) set-top box, an enterprise terminal, etc. There is no restriction on the type of this terminal device.
  • the terminal equipment can be connected to the aggregation switch, for example, it is connected to the aggregation switch through an OLT (Optical Line Terminal).
  • OLT Optical Line Terminal
  • the aggregation switches 121 and 122 may be, for example, POP (Point Of Presence) switches.
  • the gateway device 131 serves as a gateway of the BRAS resource pool and can be connected to the aggregation switches 121 and 122.
  • the gateway device 131 is configured to distribute the uplink packets sent by the terminal devices 111, 112 through the aggregation switches 121, 122 to the BRAS 141, 142, 143 in the BRAS resource pool, and receive the downlink packets sent by the BRAS 141, 142, 143, and send the downlink packets to the aggregation switches 121, 122.
  • the management device 151 serves as a MANO (Management and Orchestration, Management Orchestration) of the BRAS resource pool, and can be a controller (such as an SDN (Software Defined Network) controller). There is no limitation on the type of this management device. Take the controller as an example.
  • the controller can control the configuration information and service information of each BRAS in the BRAS resource pool. It is used to implement management and control of the BRAS, deployment of the BRAS resource pool network architecture, daily operation and maintenance management, and flexible service scheduling. , Network configuration) protocol calls API (Application Programming Interface) to complete interaction with BRAS 141,142,143.
  • API Application Programming Interface
  • the database server 181 is used to store service data generated by each of the BRAS 141,142,143, and may provide a query interface to the BRAS 141,142,143, and send the service data to the BRAS 141,142,143.
  • the number of database servers may be one or more. For convenience of description, in FIG. 1, one database server is used as an example for description.
  • the BRAS can be a physical BRAS or a virtual BRAS (that is, vBRAS).
  • a physical BRAS is a BRAS in the form of hardware, such as a server with BRAS service processing capabilities.
  • a virtual BRAS is a BRAS in the form of software, such as a virtual resource with BRAS service processing capability running on an X86 server.
  • the above process only introduces the two expressions of BRAS, and there are no restrictions on this expression. It can be understood that the number of servers in the system applied in the embodiment of the present application may be one or two, in other words, the service data and the BRAS may be run on two servers, respectively, or the service data and the BRAS may be on the same server. run.
  • BRAS can be a BRAS with separate transfer control, that is, it includes BRAS-CP (BRAS Control Plane, BRAS control plane) and BRAS-UP (BRAS User Plane, BRAS forwarding plane).
  • BRAS-CP BRAS Control Plane, BRAS control plane
  • BRAS-UP BRAS User Plane, BRAS forwarding plane.
  • BRAS-CP is a user control management component, which is used to implement functions such as user control management, user access control, user authentication and authorization charging, address management, and configuration management.
  • BRAS-UP is a network edge and user policy enforcement component. It is used to implement traffic forwarding, QoS (Quality of Service), traffic statistics, ACL (Access Control List) control, and CAR (Committed Access Access Rate). Access rate), route advertisement, etc.
  • BRAS can also be a BRAS without transfer control, that is, it has both BRAS-CP and BRAS-UP functions. It can be used to implement user control management, user access control, user authentication and authorization accounting, address management, configuration management, and traffic forwarding. , QoS, traffic statistics, ACL control, CAR, route advertisement, etc.
  • the BRAS in this embodiment is described by using a virtual BRAS as an example, and the BRAS is a BRAS that is not separated from the transfer control.
  • a BRAS resource pool can be deployed, and multiple BRASs can be divided into the BRAS resource pool through the NFV (Network Functions Virtualization) technology.
  • NFV Network Functions Virtualization
  • An arbitrary number of BRAS is illustrated in FIG. 1 by taking three BRAS as an example.
  • all the BRASs in the BRAS resource pool may be the main BRAS, and the main BRAS is a BRAS used to provide services to the terminal device.
  • the BRAS 141, the BRAS 142, and the BRAS 143 may all be the main BRAS.
  • all the BRASs in the BRAS resource pool may include a redundant BRAS, and the remaining BRASs are the primary BRAS.
  • the primary BRAS is a BRAS used to provide service to the terminal device.
  • the redundant BRAS is not currently Any terminal device provides services. After the redundant BRAS becomes the primary BRAS, it is used to provide services to the terminal device.
  • BRAS 141 and BRAS 142 can be the primary BRAS, and BRAS 143 can be the redundant BRAS.
  • BRAS 141 and BRAS 142 can be the primary BRAS
  • BRAS 143 can be the redundant BRAS.
  • other numbers of redundant BRAS may be included in the BRAS resource pool, and the number of redundant BRAS is not limited.
  • a network such as a data center
  • a network that needs to use a BRAS resource pool, whether it is a networking scenario in which multiple BRASs in the BRAS resource pool are primary BRASs, or a networking scenario in which the BRAS resource pool includes multiple primary BRASs and one redundant BRAS
  • the method provided by the present disclosure it is possible not to deploy redundant BRAS or to deploy the same redundant BRAS for all master BRAS, that is, it is not necessary to deploy a large number of redundant BRAS, thereby saving BRAS resources and making full use of the processing resources of each BRAS. , Reducing the number of BRAS in the data center. It can be understood that this application is only using one redundant BRAS as an example. Those skilled in the art can appropriately set the number of redundant BRASs according to the actual application or technical experience. The number of BRAS.
  • FIG. 2 it is a schematic flowchart of a service processing method in an embodiment of the present application.
  • the method can be applied to a first BRAS in a BRAS resource pool.
  • the method can include the following steps 201 to 203.
  • Step 201 The first BRAS receives a handover command sent by the controller, where the handover command carries a device identifier of the second BRAS in the BRAS resource pool, and the handover command is sent when the controller determines that the second BRAS meets the handover condition.
  • the switching conditions include: the second BRAS fails; the first BRAS and the second BRAS are light loads.
  • the second BRAS may be any master BRAS in the BRAS resource pool.
  • the controller determines that the second BRAS meets the handover condition, it determines that the first BRAS bears the services of the second BRAS and sends a handover command to the first BRAS.
  • the switch command may carry the device identifier of the second BRAS.
  • the first BRAS may be any one of the multiple BRASs that meets a preset condition, as long as it is different from the second BRAS.
  • the preset condition is, for example, that the current load of the BRAS is a light load.
  • multiple BRASs that are active and standby each other can all be working BRASs.
  • BRAS 141, BRAS 142, and BRAS 143 are all working BRASs.
  • BRAS 142 can be selected as BRAS.
  • the standby BRAS of 141 that is, the BRAS 142 is used as the first BRAS, or the BRAS 143 is selected as the standby BRAS of the BRAS 141, that is, the BRAS 143 is used as the first BRAS.
  • the first BRAS may be a redundant BRAS in the BRAS resource pool.
  • Step 202 The first BRAS obtains, from the database server, service data corresponding to the device identifier of the second BRAS.
  • the service data is service data associated with the terminal device backed up by the second BRAS to the database server.
  • service data associated with each terminal device may be generated, and a correspondence relationship between the service data and the device identifier of the second BRAS is backed up to a database server.
  • the second BRAS may periodically back up the correspondence between the service data and the device identification to the database server, and for example, each time the service data changes, such as when new data is generated or a certain data is overwritten, the second BRAS may Back up the correspondence between the new business data and the device identification to the database server.
  • the first BRAS can parse out the device identity of the second BRAS from the handover command, and retrieve it from the database server. Obtain the business data corresponding to the backup identifier.
  • the first BRAS obtains the service data corresponding to the device identifier of the second BRAS from the database server, which may include, but is not limited to, the first BRAS obtains the basic configuration corresponding to the database server, such as the authentication password and IP address. And port number, etc., and sends a query request carrying the device identification to the database server according to the basic configuration. Then, the first BRAS may receive a query response returned by the database server for the query request, and the query response carries the service data corresponding to the device identifier obtained by the database server.
  • the database server may include, but is not limited to, the first BRAS obtains the basic configuration corresponding to the database server, such as the authentication password and IP address. And port number, etc., and sends a query request carrying the device identification to the database server according to the basic configuration. Then, the first BRAS may receive a query response returned by the database server for the query request, and the query response carries the service data corresponding to the device identifier obtained by the database server
  • the first BRAS may further send an update request to the database server, where the update request may carry the device identifier of the first BRAS and the device identifier of the second BRAS;
  • the update request is used to request the database server to update the device identifier of the second BRAS corresponding to the service data to the device identifier of the first BRAS.
  • the first BRAS may also send a notification message that the service data has been restored to the controller, so that the controller will receive the uplink packet from the terminal device. Migration from the second BRAS to the first BRAS, thereby realizing the migration of services.
  • Step 203 The first BRAS performs service processing on the terminal device according to the service data.
  • the first BRAS performs service processing on the terminal device according to the service data, which may include, but is not limited to, the first BRAS obtains the charging information (such as online time, user traffic) of the terminal device from the service data, and charges according to the charging.
  • the information performs charging processing on the terminal device; and / or, the first BRAS obtains the address information (such as an IP address) of the terminal device from the service data, and publishes a route carrying the address information, which is used to enable the gateway device to use the destination as Downlink packets of the terminal device are migrated from the second BRAS to the first BRAS, thereby implementing service migration.
  • the first BRAS may also receive the first VSI (Virtual Switch Instance) and the first service configuration of the first BRAS sent by the controller, and correspond to the first VSI according to the first service configuration.
  • the terminal device performs service processing; and / or, the first BRAS may also receive the second VSI and the second service configuration of the second BRAS sent by the controller, and the controller determines the second BRAS by the second VSI and the second service configuration. Sent when the handover condition is met; then, the terminal device corresponding to the second VSI may be processed according to the second service configuration.
  • the first BRAS may also generate service data associated with each terminal device, and back up the correspondence between the generated service data and the device identifier of the first BRAS to Database server.
  • the first BRAS may periodically back up the correspondence between the service data and the device identification of the first BRAS to the database server.
  • the first BRAS stores the new service data and the first BRAS. The correspondence between the device IDs is backed up to the database server.
  • the services of the second BRAS can be migrated to the first BRAS.
  • the second BRAS may back up the service data to a database server, and the first BRAS may obtain the service data from the database server, and then perform service processing on the terminal device according to the service data.
  • the BRAS resource pool includes multiple primary BRASs or multiple primary BRASs and one redundant BRAS, and the first BRAS can be the primary BRAS or redundant BRAS, it is not necessary to deploy redundant BRAS or deploy the same for all primary BRASs Redundant BRAS. In this way, since there is no need to deploy a large number of redundant BRAS, the processing resources of each BRAS can be effectively used, which makes the networking mode more flexible and lower cost.
  • tidal migration can be implemented flexibly.
  • Each BRAS takes over the services of other BRAS, so that other BRAS can be powered off and save energy.
  • an embodiment of the present application further provides a service processing system, which includes a management device, a database server, and a BRAS resource pool.
  • the BRAS resource pool includes multiple BRASs, and the multiple BRASs include a first BRAS and a second BRAS.
  • the management device determines that the second BRAS satisfies the handover condition, it selects a first BRAS from the BRAS resource pool for carrying services of the second BRAS; the management device sends a handover command to the first BRAS, and the handover command carries the device identifier of the second BRAS;
  • the first BRAS executes the service processing method of the foregoing embodiment.
  • the service processing system includes a first server and a second server.
  • the first server carries and runs a BRAS resource pool.
  • the second server carries service data.
  • the BRAS resource pool includes multiple BRASs, and the multiple BRASs include a first BRAS and a second BRAS.
  • the first server executes the service processing method of the foregoing embodiment.
  • the first server may be one, that is, the BRAS and the second BRAS run on the one server. There may also be multiple first servers, such as two, that is, the first BRAS and the second BRAS are run on the two servers, respectively.
  • the management device selects the first BRAS used to carry the services of the second BRAS from the BRAS resource pool. Due to different networking forms, the management device may specifically include the following two embodiments.
  • Embodiment 1 If the BRAS resource pool includes multiple BRASs that are active and standby, the management device selects a suitable BRAS from the multiple BRASs as the standby BRAS according to the load of each BRAS.
  • the management device may select an appropriate BRAS from other BRASs currently working in the resource pool as the The first BRAS, which is the standby BRAS of the second BRAS.
  • the first BRAS which is the standby BRAS of the second BRAS.
  • the BRAS with the lightest current load may be selected as the standby BRAS of the second BRAS.
  • a BRAS whose sum of its current load and the second BRAS load is less than the upper limit of its load is selected as the backup BRAS of the second BRAS.
  • BRAS 141, BRAS 142, and BRAS 143 are the main BRAS, and the switching condition is that the BRAS is faulty or the load of the BRAS is lower than a preset value.
  • the management device can determine that BRAS 141 meets the switching conditions. If it is determined that BRAS 142 is a light load, then BRAS 142 can be selected as the first BRAS, that is, BRAS 142 is selected as BRAS 141 Prepared BRAS. In this way, the services of BRAS 141 can be migrated to BRAS 142, that is, the services of the faulty BRAS are migrated.
  • BRAS 141 is light load and BRAS 142 is light load, that is, the loads of BRAS 141 and BRAS 142 are lower than the preset value.
  • BRAS 141 can be selected as the second BRAS, and BRAS 142 is used as the The first BRAS. In this way, the services of BRAS 141 can be migrated to BRAS 142, so that one BRAS can process the services of two BRASs, saving BRAS resources.
  • Embodiment 2 If the BRAS resource pool includes multiple primary BRASs and one redundant BRAS, the management device selects the redundant BRAS as the standby BRAS of the multiple primary BRASs.
  • the management device may select the currently inactive redundant BRAS as the standby BRAS, that is, select the redundant BRAS as the one that meets the handover condition. Standby BRAS for the master BRAS.
  • BRAS 141 and BRAS 142 are the main BRAS, and BRAS 143 is the redundant BRAS, the switching condition is BRAS failure.
  • the management device can determine that the BRAS 141 meets the switching conditions. At this time, a redundant BRAS can be selected, that is, the BRAS 143 is used as the backup BRAS of the BRAS 141. In this way, the services of the BRAS 141 can be migrated To BRAS 143, the services of the faulty BRAS were migrated.
  • BRAS 141 is used as the first BRAS and BRAS 142 is used as the second BRAS.
  • a service processing method may be shown in FIG. 3, and the method may include steps 301 to 310.
  • Step 301 The controller sends basic configurations to all BRASs, and sends service configurations to the main BRAS.
  • the basic configuration can also be called a global configuration, which is a configuration that does not need to be migrated after a BRAS failure;
  • the service configuration can also be called an interface configuration, which is a configuration that needs to be migrated after a BRAS failure.
  • both BRAS 141 and BRAS 142 are master BRAS
  • basic configuration A 'and service configuration A may be sent to BRAS 141
  • basic configuration B' and service configuration B may be sent to BRAS 142.
  • basic configuration B' and service configuration B are sent to BRAS 142.
  • the basic configuration may include, but is not limited to, one or any combination of the following: the authentication password of the database server, the IP address of the database server, the port number of the database server, the device identification of the BRAS, DHCP (Dynamic Host Configuration Protocol, Dynamic Host Configuration Protocol) ) Address pool and so on.
  • DHCP Dynamic Host Configuration Protocol, Dynamic Host Configuration Protocol
  • the basic configuration A ′ of BRAS 141 may include the authentication password of the database server 181, the IP address of the database server 181, the port number of the database server 181, the device identification of the BRAS 141, and the DHCP address pool 1.
  • the basic configuration B 'of BRAS 142 may include the authentication password of the database server 181, the IP address of the database server 181, the port number of the database server 181, the device identification of the BRAS 142, the DHCP address pool 1, and the DHCP address pool 2.
  • the service configuration may include, but is not limited to, one or any combination of the following: access mode (such as IPoE (Internet Protocol over Ethernet), and PPPoE (Point Protocol) over Ethernet Point-to-point connection protocol) method, authentication method, DHCP address pool indication information (used to indicate which DHCP address pool is used to allocate addresses), etc.
  • access mode such as IPoE (Internet Protocol over Ethernet), and PPPoE (Point Protocol) over Ethernet Point-to-point connection protocol) method
  • authentication method such as IPoE (Internet Protocol over Ethernet), and PPPoE (Point Protocol) over Ethernet Point-to-point connection protocol) method
  • authentication method such as IPoE (Internet Protocol over Ethernet
  • DHCP address pool indication information used to indicate which DHCP address pool is used to allocate addresses
  • the service configurations of different BRASs may be the same or different.
  • the service configuration is related to the VSI.
  • the controller may send the first service configuration corresponding to the first VSI to the BRAS 141 and the second VSI.
  • the second service configuration may be the same or different.
  • the controller 151 can send the VSI and service configuration to the BRAS 141 / BRAS 142, so that the BRAS 141 / BRAS 142 can distinguish the service configuration of different VSIs.
  • the controller 151 sends VSI 1 and service configuration A to BRAS 141, and sends VSI 2 and service configuration B to BRAS 142.
  • the controller 151 may send the basic configuration to all BRASs through the Netconf protocol, and send the service configuration to the main BRAS through the Netconf protocol, and there is no limitation on the sending manner.
  • Step 302 The main BRAS performs service processing on the terminal device corresponding to the VSI according to the service configuration.
  • the BRAS 142 performs service processing on the terminal device corresponding to the VSI 2 according to the service configuration B.
  • a VXLAN (Virtual Extensible LAN) tunnel A can be established between the BRAS 141 and the gateway device 131, and the BRAS 141 can establish a correspondence between the VXLAN tunnel A and VSI1.
  • a VXLAN tunnel B can be established between the BRAS 142 and the gateway device 131, and a correspondence relationship between the VXLAN tunnel B and VSI 2 can be established.
  • the establishment process of the VXLAN tunnel A and the VXLAN tunnel B there are no restrictions in this embodiment. For example, the establishment may be performed in a static manner or in a dynamic manner.
  • VXLAN tunnel A and VSI 1 may be notified by the controller to BRAS 141, and the correspondence between VXLAN tunnel B and VSI 2 may be notified by the controller to BRAS 142.
  • the gateway device 131 may query the VXLAN tunnel corresponding to the VLAN of the uplink message, assuming that the VXLAN tunnel is queried B, the uplink packet can be sent to BRAS 142 through VXLAN tunnel B.
  • BRAS142 queries the VSI 2 corresponding to the VXLAN tunnel B, and then queries the service configuration B corresponding to the VSI 2 tunnel.
  • the BRAS 142 may perform service processing on the terminal device 111 according to the service configuration B.
  • the BRAS 142 may allocate an address to the terminal device 111 according to the service configuration B. Specifically, the BRAS 142 parses the DHCP address pool information from the service configuration B, selects an available IP address from the DHCP address pool, and assigns the IP address to the terminal device 111. Then, the gateway device 131 can pass through the gateway device 131 A DHCP response message is sent to the terminal device 111, and the DHCP response message may carry the IP address, and there is no restriction on the address allocation process. If the uplink message is an authentication request message, the BRAS 142 may perform authentication processing on the terminal device 111 according to the service configuration B. Specifically, the BRAS 142 parses the access mode and authentication mode from the service configuration B, and uses the parsed access mode and authentication mode to authenticate the terminal device 111, and there is no restriction on the authentication process.
  • BRAS 142 performs service processing on terminal device 111 according to service configuration B.
  • BRAS 142 can perform user control management, user access control, and user authentication according to service configuration B.
  • the BRAS 142 may back up the correspondence between the service data and the device identifier of the BRAS 142 to the database server 181.
  • step 304 the database server 181 stores the correspondence between the service data and the device identifier.
  • the service data of the terminal device 111 such as the service data B "
  • the BRAS 142 can associate the service data B" with the device identifier of the BRAS 142.
  • the database server 181 receives and stores the corresponding relationship, as shown in Table 1.
  • the service data B "of the terminal device 111 includes, but is not limited to, one or any combination of the following: IP address, MAC (Media Access Control) address, VLAN information, VPN information, VXLAN identification, authorization information (Such as QoS policy, speed limit policy, statistical policy, ACL policy), user traffic, online time, etc.
  • step 305 when the controller 151 determines that the BRAS 142 meets the handover condition, it sends the VSI 2 and service configuration B corresponding to the BRAS 142 to the BRAS 141, but does not send the basic configuration B ', and sends a handover command to the BRAS 141.
  • the handover command carries BRAS Device ID of 142.
  • the controller 151 may periodically send a heartbeat message to the BRAS 142, and after sending a preset number (such as 10) of heartbeat messages, if no response message for the heartbeat message is received by the BRAS 142 , It is determined that the BRAS 142 fails, and it is determined that the BRAS 142 meets the switching condition.
  • a preset number such as 10
  • the controller 151 can monitor the load of BRAS 142 and BRAS 141. If the load of BRAS 142 is light and the load of BRAS 141 is light, then it is determined that one of BRAS 141 and BRAS 142 can be released. For example, BRAS 142 is released, that is, the service of BRAS 142 is migrated to BRAS 141, and it is determined that BRAS 142 meets the handover condition.
  • the above is only an example in which the BRAS 142 satisfies the handover condition, and there is no restriction on the handover condition.
  • the controller 151 may select a target BRAS for carrying the services of the BRAS 142 from the BRAS resource pool, for example, determine that the target BRAS is BRAS 141.
  • the BRAS resource pool includes redundant BRAS
  • determine the redundant BRAS as the target BRAS or select a BRAS from the BRAS resource pool and determine the selected BRAS as the target BRAS according to the load of each master BRAS, such as A lightly loaded BRAS is determined as the target BRAS.
  • the controller 151 may send the VSI 2 and the service configuration B corresponding to the BRAS 142 to the BRAS 141, and send a handover command to the BRAS 141, which carries the device identification of the BRAS 142.
  • the controller 151 can maintain the device identification, service configuration, basic configuration, VSI and other contents of all BRAS. Therefore, when the BRAS 142 meets the handover condition, the controller 151 can query the BRAS 142 device identification and service configuration B locally. And VSI 2 and other information, and send VSI 2 and service configuration B to BRAS 141, and send a switch command carrying the device identification of BRAS 142 to BRAS 141.
  • the BRAS 141 receives the VSI 2 and the service configuration B corresponding to the BRAS 142 sent by the controller 151, and receives the handover command sent by the controller 151.
  • the switch command carries the device identification of BRAS 142.
  • the BRAS 141 obtains the service data B corresponding to the device identification of the BRAS 142 from the database server 181.
  • the database server 181 stores the correspondence between the device identification of the BRAS 142 and the business data B ", and the BRAS 141 can be obtained from The database server 181 acquires business data B ".
  • step 308 the BRAS 141 sends a notification message that the service data has been restored to the controller 151, so that the controller 151 migrates the uplink packet of the terminal device from the BRAS 142 to the BRAS 141.
  • the data recovery is marked as the second identifier.
  • BRAS 141 obtains all the business data of BRAS 142 from the database server 181 (for example, BRAS 142 may back up a large amount of business data to the database server 181, BRAS 141 After obtaining all the business data of the BRAS 142 from the database server 181), the data recovery flag is set as the first identifier. This achieves data backup and recovery functions.
  • the controller 151 may periodically send a query command to the BRAS 141.
  • the BRAS 141 receives the query command, if the data recovery is marked as the second identification, the BRAS 141 completes the unrecovered service data.
  • the notification message is sent to the controller 151. In this way, the controller 151 continues to send the query command to the BRAS 141 in the next cycle. If the data recovery flag is the first identifier, the BRAS 141 sends a notification message that the service data has been restored to the control. In this way, the controller 151 learns that the service data has been restored and stops sending query commands, and migrates the uplink packets of the terminal device from BRAS 142 to BRAS 141.
  • the controller 151 changes the destination address (such as IP address, MAC address, etc.) of the VXLAN tunnel B of the gateway device 131,
  • the IP address is taken as an example in the following) and the address (such as IP address, MAC address, etc.) of BRAS 141 is modified, so that the uplink packet destined for BRAS 142 is migrated to BRAS 141.
  • the gateway device 131 may establish a VXLAN tunnel A with the BRAS 141, and the gateway device 131 may establish a VXLAN tunnel B with the BRAS 142. Based on this, if the controller 151 changes the destination IP address of the VXLAN tunnel B of the gateway device 131 to the IP address of the BRAS 141, the gateway device 131 sends an uplink message (that is, a message sent by the terminal device) through the VXLAN tunnel B , The uplink message is sent to BRAS 141 instead of BRAS 142, so that the uplink packet destined for BRAS 142 is migrated to BRAS 141, and the service migration is realized.
  • an uplink message that is, a message sent by the terminal device
  • controller 151 may notify the BRAS 141 to establish the VXLAN tunnel B with the gateway device 131, and record the correspondence between the VXLAN tunnel B and VSI 2.
  • the gateway device 131 receives an uplink packet (such as an uplink data packet) sent by an online terminal device, and the terminal device such as the above-mentioned terminal device 111 is online at the BRAS 142, the gateway device 131 needs to pass the VXLAN tunnel B When sending an uplink packet, since the destination IP address of VXLAN tunnel B is the IP address of BRAS 141 (instead of the IP address of BRAS 142), the gateway device 131 sends the uplink packet to BRAS 141 through VXLAN tunnel B.
  • an uplink packet such as an uplink data packet
  • the terminal device such as the above-mentioned terminal device 111 is online at the BRAS 142
  • the gateway device 131 needs to pass the VXLAN tunnel B
  • the gateway device 131 sends the uplink packet to BRAS 141 through VXLAN tunnel B.
  • the gateway device 131 may query the VXLAN tunnel corresponding to the VLAN of the uplink packet.
  • the gateway device 131 sends an uplink packet to BRAS 141 through VXLAN tunnel B.
  • step 309 the BRAS 141 performs service processing on the terminal device according to the service data B ”, and the BRAS 141 performs service processing on the terminal device corresponding to the VSI 2 according to the service configuration B of the BRAS 142.
  • BRAS 141 may perform service processing on terminal device 111 according to the service data B".
  • the BRAS 141 obtains the charging information (such as online time and user traffic) of the terminal device 111 from the service data B ”, and performs charging processing on the terminal device 111 according to the charging information.
  • the charging information such as online time and user traffic
  • the BRAS 141 may obtain the user traffic and online time of the terminal device 111 from the service data B", and the user traffic and the online time On the basis of, the user traffic and online time of the terminal device 111 are continuously counted, so that the terminal device 111 is charged based on the user traffic and online time.
  • BRAS 141 can obtain the IP address, MAC address, VLAN information, VPN information, VXLAN identification, etc. of the terminal device 111 from the service data B ”, and can use the above IP address, MAC address, VLAN information, VPN information, The VXLAN identifier and other content generate a forwarding entry, and use this forwarding entry to guide the BRAS 141 to forward packets. There is no restriction on this forwarding process.
  • BRAS 141 can obtain the QoS policy of terminal device 111 from service data B ”, and guide BRAS 141 to implement QoS control on terminal device 111 through the QoS policy; obtain the speed limit policy of terminal device 111 from service data B”, The speed limit policy is used to guide BRAS 141 to implement CAR on terminal device 111; the statistical strategy of terminal device 111 is obtained from service data B ”, and the statistical policy is used to guide BRAS 141 to implement traffic statistics on terminal device 111; from service data B” Obtain the ACL policy of the terminal device 111, and guide the BRAS 141 to implement ACL control on the terminal device 111 through the ACL policy.
  • the BRAS 141 obtains the address information (such as an IP address) of the terminal device 111 from the service data B ”, and publishes a route carrying the IP address. The route is used to enable the gateway device 131 to report the downstream report of the terminal device 111. This article migrates from BRAS 142 to BRAS 141, thus realizing the migration of business.
  • the address information such as an IP address
  • BRAS 141 publishes a route carrying the IP address of the terminal device 111 to the gateway device 131, and the gateway device 131 receives the After routing, the outbound interface corresponding to the IP address of the terminal device 111 is learned to the BRAS 141, so that the downstream packets destined for the terminal device 111 are migrated to the BRAS 141.
  • the IP address of the terminal device 111 is the IP address 111
  • the interface connected between the gateway device 131 and the BRAS 141 is 1311
  • the interface connected between the gateway device 131 and the BRAS 142 is 1312.
  • the BRAS 142 provides services to the terminal device 111
  • it can advertise the route carrying the IP address 111 to the gateway device 131
  • the gateway device 131 can generate the routing entry shown in Table 2.
  • BRAS 141 can obtain the IP address 111 of the terminal device 111 from the service data B ”and publish a route carrying the IP address 111 to the gateway device 131.
  • the gateway device 131 determines that the outbound interface corresponding to the IP address 111 is migrated from 1312 to 1311, and modifies the routing entry shown in Table 2 to Table 3.
  • the gateway device 131 when the gateway device 131 receives a downlink packet with a destination IP address of the IP address 111 (the following data packet may be a data packet sent from the Internet to the terminal device 111), The interface 1311 sends the downlink message to the BRAS 141, thereby migrating the downlink message destined for the terminal device 111 to the BRAS 141, and realizing service migration. After receiving the downlink message, the BRAS 141 may also send the downlink message to the terminal device 111, and there is no restriction on the sending process.
  • the above-mentioned several cases are just examples of the BRAS 141 performing service processing on the terminal device 111 according to the service data B ”, and there is no limitation on the service processing process, and it can be implemented according to actual conditions.
  • the BRAS 141 performs service processing on the terminal device corresponding to the VSI 2 according to the service configuration B of the BRAS 142, and may further include: for the terminal device to be online, such as the terminal device 112, the gateway device 131 receives the terminal device 112 After sending an uplink packet (such as a DHCP request packet or an authentication request packet), you can query the VXLAN tunnel corresponding to the VLAN of the uplink packet. Assuming that VXLAN tunnel B is queried, the uplink packet can be sent through VXLAN tunnel B. To BRAS 141.
  • an uplink packet such as a DHCP request packet or an authentication request packet
  • the BRAS 141 can query the VSI 2 corresponding to the VXLAN tunnel B, and query the service configuration B corresponding to the VSI 2 tunnel.
  • the BRAS 141 may allocate an address to the terminal device 112 according to the service configuration B. For example, the BRAS 141 can parse the information of the DHCP address pool from the service configuration B, select an available IP address from the DHCP address pool, and assign the IP address to the terminal device 112. There is no restriction on the address allocation process.
  • the uplink message is an authentication request message
  • the BRAS 141 may perform authentication processing on the terminal device 112 according to the service configuration B. For example, the BRAS 141 may parse the access mode and authentication mode from the service configuration B, and use the access mode and authentication mode to authenticate the terminal device 112, and there is no restriction on the authentication process.
  • the BRAS 141 may also perform service processing on the terminal device corresponding to the VSI 1 according to the service configuration A of the BRAS 141.
  • the gateway device 131 receives the terminal device.
  • the VXLAN tunnel corresponding to the VLAN of the uplink message can be queried.
  • the uplink message can be sent to BRAS 141 through VXLAN tunnel A.
  • BRAS 141 queries VSI 1 corresponding to VXLAN tunnel A, and queries service configuration A corresponding to VSI 1.
  • the BRAS 141 may perform service processing on the terminal device 113 according to the service configuration A, such as performing address allocation and authentication processing on the terminal device 113.
  • Step 310 After performing service processing on the terminal device, the BRAS 141 may regenerate service data of the terminal device, and back up the correspondence between the service data and the device identifier of the BRAS 141 to the database server 181.
  • the database server 181 stores the correspondence between the service data and the device identifier.
  • step 310 reference may be made to step 303 and step 304, and details are not described herein again.
  • each BRAS may include a database module (also referred to as a database process, such as a RedisDBM process running independently on the BRAS) and at least one service module (also referred to as a service process, such as running independently on the BRAS IPoE process, PPPoE process, DHCP process, etc.
  • the IPoE process is used to implement IPoE access authentication
  • the PPPoE process is used to implement PPPoE access authentication
  • the DHCP process is used to implement address allocation.
  • the database module of the BRAS can establish a long-term connection with the database server 181 (for example, the database module can obtain the basic configuration such as the authentication password, IP address, and port number of the database server 181, and establish a long-term connection with the database server 181 according to the basic configuration),
  • the BRAS business module can establish a connection with the database module.
  • the business module can generate business data and can write the business data to the database server 181 (such as the writing process of steps 303-304 and step 310 above). This embodiment does not do the process of generating business data by the business module. limit.
  • the service module may send the service data to the database module.
  • the database module may obtain the device identifier, and store the service data and the device identifier to the database server 181 through the long connection.
  • the database module can read the business data from the database server 181 through the above long connection, and Send business data to the business module.
  • the process in which the BRAS 141 obtains the business data B from the database server 181 can be implemented as shown in FIG. 4, and the process can include the following steps 401 to 416.
  • step 401 the database module of the BRAS 141, after receiving the switching command (also referred to as a data recovery start message) sent by the controller, notifies each business module to start data recovery, that is, it tells the business module to prepare to recover business data, and The switch command obtains the device identification of the BRAS 142.
  • the switching command also referred to as a data recovery start message
  • the database module sends a query request to the database server 181, where the query request carries the device identification of the BRAS142. For example, the database module sends a query request through the long connection.
  • step 403 after receiving the query request, the database server 181 parses out the device identifier of the BRAS 142 from the query request, and queries the service data B corresponding to the device identifier ".
  • step 404 the database server 181 returns a query response carrying the service data B "to the BRAS 141.
  • step 405 the database module receives the query response and obtains business data B "from the query response.
  • step 406 the database module pushes the business data B "to each business module.
  • the database module may obtain multiple business data from the database server 181, and each time the business data is obtained, the database module may push the business data to each business module.
  • the business module After receiving the business data B ", the business module can also reorganize the business data B". For example, if the business data B "stored by the database server 181 is in the first format and the business data B" required by the business module is in the second format, the business module may convert the received business data B "into the second format.
  • the business module may convert the received business data B "into the second format.
  • Step 407 After the service data push is completed, the database module sends a data push completion message to the service module.
  • the data push completion message indicates that all the business data of the BRAS 142 has been pushed.
  • step 408 after receiving the service data B ", the database module sends an update request to the database server 181, where the update request carries the device identification of BRAS 141 and the device identification of BRAS 142.
  • step 409 after receiving the update request, the database server 181 updates the device identification corresponding to the service data B "from the device identification of BRAS 142 to the device identification of BRAS 141 according to the update request.
  • Step 410 After receiving the data push completion message, the business module sends a data reception completion message to the database module.
  • the data reception completion message indicates that the business module has received and processed all the business data.
  • step 411 the database module detects whether a data receiving completion message is received from all service modules.
  • step 412 can be performed; if not, it means that there is still a business module that has not received all the business data, and can continue to wait.
  • step 412 the database module sends a synchronization completion message to all business modules, indicating that the data reception completion message of all the business modules has been received, and all the business modules have received all the business data.
  • Step 413 After receiving the synchronization completion message, the service module performs a data smoothing operation of the service module.
  • Step 414 After the data smoothing ends, the service module sends a smoothing completion message to the database module.
  • Step 415 After receiving the smooth completion messages of all service modules, the database module sends service processing messages to each service module, so that each service module performs service processing according to service data.
  • step 416 the database module sends a notification message that the service data has been restored to the controller 151, so that the controller 151 migrates the uplink packets of the terminal device from BRAS 142 to BRAS 141.
  • an embodiment of the present application further proposes a service processing device, which is applied to a first BRAS in a BRAS resource pool.
  • the device includes a receiving module 501, an obtaining module 502, and a processing module 503.
  • the receiving module 501 is configured to receive a handover command sent by a management device, where the handover command carries a device identifier of a second BRAS in a BRAS resource pool, and the handover command is sent when the management device determines that the second BRAS meets a handover condition.
  • the obtaining module 502 is configured to obtain service data corresponding to the device identifier of the second BRAS from the database server, where the service data is service data associated with the terminal device backed up by the second BRAS to the database server.
  • the processing module 503 is configured to perform service processing on the terminal device according to the service data.
  • the obtaining module 502 is specifically configured to obtain a basic configuration of the database server; send a query request carrying the device identifier of the second BRAS to the database server according to the basic configuration; and receive a query response returned by the database server for the query request
  • the query response carries service data corresponding to the device identifier of the second BRAS obtained by the database server.
  • the apparatus further includes a first sending module 504.
  • a first sending module 504 is configured to send an update request to the database server after the obtaining module 502 obtains service data corresponding to the device identifier of the second BRAS from the database server, where the update request carries the first A device identifier of a BRAS and a device identifier of the second BRAS; wherein the update request is used to request the database server to update the device identifier of the second BRAS corresponding to the service data in the database server to the first A BRAS device identifier.
  • the apparatus further includes a second sending module 505.
  • a second sending module 505, configured to, after the obtaining module 502 obtains service data corresponding to the device identifier of the second BRAS from a database server, send a notification message that the service data has been restored to the management device, So that the management device migrates the uplink packet of the terminal device from the second BRAS to the first BRAS.
  • the processing module 503 is specifically configured to: obtain the charging information of the terminal device from the service data, and perform charging processing on the terminal device according to the charging information; and / or, from the service
  • the data obtains the address information of the terminal device, and publishes a route carrying the address information, and the route is used to enable the gateway device to migrate a downlink packet destined for the terminal device from the second BRAS to the first A BRAS.
  • the apparatus further includes a generating module 506.
  • a generating module 506, configured to generate service data of the terminal device after the processing module 503 performs service processing on the terminal device, and back up the correspondence between the generated service data and the device identifier of the first BRAS to all The database server.
  • the BRAS includes: a machine-readable storage medium 901 and a processor 902.
  • the machine-readable storage medium 901 stores instruction codes, such as business processing instructions 902.
  • the processor 902 communicates with the machine-readable storage medium 901, reads and executes the instruction code stored in the machine-readable storage medium, and implements the business processing operations disclosed in the foregoing examples of this application.
  • a switching command sent by a management device is received, where the switching command carries a device identifier of a second BRAS, and the switching command is sent when the management device determines that the second BRAS meets a switching condition; Service data corresponding to the device identification of the second BRAS, where the service data is service data associated with a terminal device backed up to the database server by the second BRAS; and performing service on the terminal device according to the service data deal with.
  • the machine-readable storage medium 901 may be any electronic, magnetic, optical, or other physical storage device, and may contain or store information such as executable instructions, data, and so on.
  • the machine-readable storage medium may be: RAM (Radom Access Memory), volatile memory, non-volatile memory, flash memory, storage drive (such as hard drive), solid state hard disk, any type of storage disk (Such as optical discs, DVDs, etc.), or similar storage media, or a combination thereof.
  • the system, device, module, or unit described in the foregoing embodiments may be specifically implemented by a computer chip or entity, or a product with a certain function.
  • a typical implementation device is a computer, and the specific form of the computer may be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email sending and receiving device, and a game control Desk, tablet computer, wearable device, or a combination of any of these devices.
  • the embodiments of the present application may be provided as a method, a system, or a computer program product. Therefore, this application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the embodiments of the present application may take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
  • computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
  • these computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured article including an instruction device,
  • the instruction device implements the functions specified in a flowchart or a plurality of processes and / or a block or a plurality of blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing device, so that a series of operation steps can be performed on the computer or other programmable device to generate a computer-implemented process, which can be executed on the computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more flowcharts and / or one or more blocks of the block diagrams.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

提供一种业务处理方法、系统和装置，应用于BRAS资源池内的第一BRAS。该方法包括：接收管理设备发送的切换命令，所述切换命令携带所述BRAS资源池内的第二BRAS的设备标识，所述切换命令是所述管理设备确定所述第二BRAS满足切换条件时发送的；从数据库服务器获取与所述第二BRAS的设备标识对应的业务数据，所述业务数据是所述第二BRAS备份到所述数据库服务器的与终端设备关联的业务数据；根据所述业务数据对所述终端设备进行业务处理。

Description

业务处理 技术领域
本申请涉及通信技术领域，尤其是涉及一种业务处理方法、系统和装置。
背景技术
BRAS(Broadband Remote Access Server，宽带远程接入服务器)是面向宽带网络应用的新型接入网关，位于骨干网边缘，可以实现宽带上网、VPN(Virtual Private Network，虚拟专用网络)服务、构建企业内部网络、支持ITMS(Integrated Terminal Management System，终端综合管理系统)、VoIP(Voice over Internet Protocol，网络电话)等业务。在实际组网环境中，可能存在大量终端，即BRAS需要为大量终端提供服务，因此，BRAS可能出现性能瓶颈。为了提高BRAS的处理性能，则可以部署多个BRAS，由多个BRAS共同为所有终端提供服务。
为了保证每个BRAS的高可用性，从而提高可靠性，则可以为每个BRAS(后续称为主BRAS)提供备BRAS，这样，当主BRAS发生故障时，则备BRAS可以升级为主BRAS，并由备BRAS提供服务。例如，可以为主BRAS11提供备BRAS12，为主BRAS21提供备BRAS22，为主BRAS31提供备BRAS32。
显然，在上述方式中，每个主BRAS对应一个备BRAS，主BRAS的数量与备BRAS的数量相同，即需要部署大量备BRAS，浪费了BRAS资源。而且，大多数备BRAS可能并不会真正用到，无法充分利用备BRAS的处理资源。
附图说明
为了更加清楚地说明本申请实施例的技术方案，下面将对本申请实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请中记载的一些实施例，对于本领域普通技术人员来讲，还可以根据本申请实施例的这些附图获得其他的附图。
图1是本申请一种实施方式中的应用场景示意图；
图2是本申请一种实施方式中的业务处理方法的流程图；
图3是本申请另一种实施方式中的业务处理方法的流程图；
图4是本申请另一种实施方式中的业务处理方法的流程图；
图5是本申请一种实施方式中的业务处理装置的结构图；
图6是本申请另一种实施方式中的业务处理装置的结构图；
图7是本申请另一种实施方式中的业务处理装置的结构图；
图8是本申请另一种实施方式中的业务处理装置的结构图；
图9是本申请一种实施方式中的BRAS的硬件结构图。
具体实施方式
在本申请使用的术语，仅仅是出于描述特定实施例的目的，而非限制本申请。本申请和权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其它含义。还应当理解，本文中使用的术语“和/或”是指包含一个或多个相关联的列出项目的任何或者所有可能组合。
应当理解，尽管在本申请可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本申请范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，此外，所使用的词语“如果”可以被解释成为“在……时”，或者，“当……时”，或者，“响应于确定”。
本申请实施例提出一种业务处理方法，应用于包括管理设备、数据库服务器、BRAS和终端设备的系统。如图1所示，为本实施例的应用场景示意图，以终端设备111,112、汇聚交换机121,122、网关设备131、BRAS 141,142,143、管理设备151、核心交换机161、核心路由器171、数据库服务器181为例，当然，图1只是一个示例，对此不做限制。本文以3个BRAS为例进行说明，实际应用中，BRAS的数量还可以更多，对此数量不做限制。
其中，终端设备111,112可以如虚拟机、PC(Personal Computer，个人计算机)、笔记本电脑、手机、主机、家庭终端、E8C终端、IPTV(Internet Protocol Television，交互式网络电视)机顶盒、企业终端等，对此终端设备的类型不做限制。终端设备可以接入到汇聚交换机，如通过OLT(Optical Line Terminal，光线路终端)连接到汇聚交换机。
汇聚交换机121,122可以如POP(Point Of Presence，入网点)交换机。
网关设备131作为BRAS资源池的网关，可以与汇聚交换机121,122连接。网关设备131用于将终端设备111,112通过汇聚交换机121,122发送的上行报文分发到BRAS资源池中的BRAS 141,142,143，以及，接收BRAS 141,142,143发送的下行报文，并通过汇聚交换机121,122将下行报文发送给终端设备111,112。
管理设备151作为BRAS资源池的MANO(Management and Orchestration，管理编排器)，可以为控制器(如SDN(Software Defined Network，软件定义网络)控制器)，对此管理设备的类型不做限制，后续以控制器为例。控制器能够控制BRAS资源池内的各BRAS的配置信息和业务信息，用于实现对BRAS的管理和控制、BRAS资源池组网架构部署、日常运维管理和灵活业务调度，并通过Netconf(Network Configuration，网络配置)协议调用API(Application Programming Interface，应用程序编程接口)完成与BRAS 141,142,143的交互。
数据库服务器181用于存储各BRAS 141,142,143生成的业务数据，并可以向BRAS141,142,143提供查询接口，将业务数据发送给BRAS 141,142,143。在实际应用中，数据库服务器的数量可以为一个或多个，为了方便描述，在图1中，以一个数据库服务器为例进行说明。
BRAS可以为物理BRAS，也可以为虚拟BRAS(即vBRAS)。物理BRAS是硬件形式的BRAS，如具有BRAS业务处理能力的服务器。虚拟BRAS是软件形式的BRAS，如运行于X86服务器的具有BRAS业务处理能力的虚拟资源。当然，上述过程只是介绍了BRAS的两种表现形式，对此表现形式不做限制。可理解的是，本申请实施例所应用的系统中的服务器数量可以是一个或两个，换言之，业务数据和BRAS可以分别在两个服务器上运行，或者，业务数据和BRAS在同一个服务器上运行。
BRAS可以是转控分离的BRAS，即包括BRAS-CP(BRAS Control Plane，BRAS控制平面)和BRAS-UP(BRAS User Plane，BRAS转发平面)。BRAS-CP为用户控制管理部件，用于实现用户控制管理、用户接入控制、用户认证授权计费、地址管理、配置管理等功能。BRAS-UP为网络边缘和用户策略执行部件，用于实现流量转发、QoS(Quality of Service，服务质量)、流量统计、ACL(Access Control List，访问控制列表)控制、CAR(Committed Access Rate，承诺访问速率)、路由发布等。BRAS也可以是转控未分离的BRAS，即同时具备BRAS-CP和BRAS-UP的功能，可用于实现用户控制管理、用户接入控制、用户认证授权计费、地址管理、配置管理、流量转发、QoS、流 量统计、ACL控制、CAR、路由发布等。
为了方便描述，本实施例中的BRAS是以虚拟BRAS为例进行说明，且该BRAS是转控未分离的BRAS。为了实现虚拟BRAS，则可以部署BRAS资源池，并可以通过NFV(Network Functions Virtualisation网络功能虚拟化)技术，在BRAS资源池内划分出多个BRAS，对此BRAS的数量不做限制，可以根据经验划分任意数量的BRAS，在图1中，是以3个BRAS为例进行说明。
在一个例子中，BRAS资源池内的所有BRAS可以均为主BRAS，而主BRAS是用于为终端设备提供服务的BRAS，例如，BRAS 141、BRAS 142和BRAS 143可以均为主BRAS。在另一例子中，在BRAS资源池内的所有BRAS中，可以包括一个冗余BRAS，而剩余的BRAS均为主BRAS，主BRAS是用于为终端设备提供服务的BRAS，冗余BRAS当前不为任何终端设备提供服务，当冗余BRAS成为主BRAS后，才用于为终端设备提供服务，例如，BRAS 141和BRAS 142可以为主BRAS，而BRAS 143可以为冗余BRAS。当然，在BRAS资源池内还可以包括其它数量的冗余BRAS，对此冗余BRAS的数量并不做限制。
在需要使用BRAS资源池的网络(如数据中心)中，无论是BRAS资源池内多个BRAS均为主BRAS的组网场景，还是BRAS资源池内包括多个主BRAS和一个冗余BRAS的组网场景，通过本公开所提供的方法，可以不部署冗余BRAS或者为所有主BRAS部署同一个冗余BRAS，即不需要部署大量冗余BRAS，从而可以节约BRAS资源，充分利用每个BRAS的处理资源，降低了数据中心中的BRAS的数量。可理解，本申请仅是以一个冗余BRAS为例，本领域技术人员可以根据实际应用或技术经验适当设置冗余BRAS的数量，所设置的冗余BRAS的数量少于现有技术中所需BRAS的数量。
在上述应用场景下，参见图2所示，为本申请实施例中的业务处理方法的流程示意图，该方法可以应用于BRAS资源池内的第一BRAS，该方法可以包括以下步骤201～203。
步骤201，第一BRAS接收控制器发送的切换命令，该切换命令携带BRAS资源池内的第二BRAS的设备标识，该切换命令是控制器确定第二BRAS满足切换条件时发送的。
其中，切换条件包括：第二BRAS发生故障；第一BRAS和第二BRAS为轻负载。
在一个示例中，第二BRAS可以为BRAS资源池内的任意主BRAS，控制器在确定 第二BRAS满足切换条件时，确定由第一BRAS承载第二BRAS的业务，并向第一BRAS发送切换命令，该切换命令可以携带第二BRAS的设备标识。
其中，若BRAS资源池内包括互为主备的多个BRAS，则第一BRAS可以为所述多个BRAS中满足预设条件的任一BRAS，只要与第二BRAS不同即可。该预设条件例如是BRAS的当前负载为轻负载。其中，互为主备的多个BRAS可以均是工作的BRAS，例如，BRAS 141、BRAS 142和BRAS 143均是工作的主BRAS，在BRAS 141为第二BRAS时，可以将BRAS 142选择为BRAS 141的备BRAS，即BRAS 142作为第一BRAS，或者，将BRAS 143选择为BRAS 141的备BRAS，即BRAS 143作为第一BRAS。
在另一个示例中，若BRAS资源池内包括多个主BRAS和一个冗余BRAS(即暂时不工作的BRAS)，则第一BRAS可以为BRAS资源池内的冗余BRAS。
步骤202，第一BRAS从数据库服务器获取与该第二BRAS的设备标识对应的业务数据，该业务数据是第二BRAS备份到数据库服务器的与终端设备关联的业务数据。
其中，第二BRAS为至少一个终端设备提供服务时，可以生成与每个终端设备关联的业务数据，并将该业务数据和第二BRAS的设备标识之间的对应关系备份到数据库服务器。例如，第二BRAS可以周期性将业务数据和设备标识之间的对应关系备份到数据库服务器，又例如，每次业务数据发生变化例如产生新的数据或某个数据被覆盖时，第二BRAS可以将新业务数据和设备标识之间的对应关系备份到数据库服务器。
进一步的，由于数据库服务器存储有业务数据与第二BRAS的设备标识的对应关系，因此，第一BRAS接收到切换命令后，可以从切换命令中解析出第二BRAS的设备标识，并从数据库服务器获取与该备标识对应的业务数据。
在一个例子中，第一BRAS从数据库服务器获取与该第二BRAS的设备标识对应的业务数据，可以包括但不限于：第一BRAS获取与该数据库服务器对应的基础配置，如认证密码、IP地址及端口号等，并根据该基础配置向数据库服务器发送携带该设备标识的查询请求。然后，第一BRAS可以接收数据库服务器针对该查询请求返回的查询响应，该查询响应携带数据库服务器获得的与该设备标识对应的业务数据。
在一个例子中，第一BRAS从数据库服务器获取与该设备标识对应的业务数据之后，还可以向数据库服务器发送更新请求，该更新请求可以携带第一BRAS的设备标识和第二BRAS的设备标识；该更新请求用于请求数据库服务器将该业务数据对应的第二BRAS的设备标识更新为第一BRAS的设备标识。
第一BRAS从数据库服务器获取与该设备标识对应的业务数据之后，还可以将该业务数据的已经恢复完成的通知消息发送给控制器，以使控制器将自终端设备接收上行报文的接收方从第二BRAS迁移到第一BRAS，从而实现业务的迁移。
步骤203，第一BRAS根据该业务数据对终端设备进行业务处理。
其中，第一BRAS根据该业务数据对终端设备进行业务处理，可以包括但不限于：第一BRAS从业务数据中获取终端设备的计费信息(如在线时间、用户流量)，并根据该计费信息对终端设备进行计费处理；和/或，第一BRAS从业务数据中获取终端设备的地址信息(如IP地址)，发布携带该地址信息的路由，该路由用于使网关设备将目的为终端设备的下行报文从第二BRAS迁移到第一BRAS，从而实现业务的迁移。
在一个例子中，第一BRAS还可以接收控制器发送的第一BRAS的第一VSI(Virtual Switch Instance，虚拟交换实例)和第一业务配置，并根据该第一业务配置对该第一VSI对应的终端设备进行业务处理；和/或，第一BRAS还可以接收控制器发送的第二BRAS的第二VSI和第二业务配置，且第二VSI和第二业务配置是控制器确定第二BRAS满足切换条件时发送的；然后，可以根据该第二业务配置对该第二VSI对应的终端设备进行业务处理。
在一个例子中，第一BRAS在对至少一个终端设备进行业务处理后，还可以生成与每个终端设备关联的业务数据，并将生成的业务数据与第一BRAS的设备标识的对应关系备份到数据库服务器。例如，第一BRAS可以周期性将业务数据和第一BRAS的设备标识之间的对应关系备份到数据库服务器，又例如，每次产生新业务数据时，第一BRAS将新业务数据和第一BRAS的设备标识之间的对应关系备份到数据库服务器。
基于上述技术方案，在第二BRAS满足切换条件时，可以将第二BRAS的业务迁移到第一BRAS。例如，第二BRAS可以将业务数据备份到数据库服务器，且第一BRAS可以从数据库服务器获取该业务数据，继而根据该业务数据对终端设备进行业务处理。
由于BRAS资源池内包括多个主BRAS或者包括多个主BRAS和一个冗余BRAS，且第一BRAS可以为主BRAS或者冗余BRAS，因此，可以不部署冗余BRAS或者为所有主BRAS部署同一个冗余BRAS。这样，由于不需要部署大量冗余BRAS，可以有效利用每个BRAS的处理资源，使得组网方式更加灵活，更加低成本。
而且，可以灵活实现潮汐迁移。当业务繁忙时，可以启动多个BRAS，将业务压力较大的BRAS的部分业务迁移到业务压力较小或新的BRAS；当业务较少时，可以将所 有业务集中到几个BRAS，这几个BRAS接替其它BRAS的业务，这样其它BRAS可以断电节能。
基于与上述方法同样的构思，本申请实施例还提出一种业务处理系统，包括管理设备、数据库服务器、BRAS资源池。BRAS资源池中包括多个BRAS，所述多个BRAS包括第一BRAS和第二BRAS。在管理设备确定第二BRAS满足切换条件时，从BRAS资源池内选择用于承载第二BRAS的业务的第一BRAS；管理设备向第一BRAS发送切换命令，切换命令携带第二BRAS的设备标识；第一BRAS执行上述实施例的业务处理方法。
在一个实施例中，业务处理系统包括第一服务器和第二服务器，第一服务器承载和运行BRAS资源池。第二服务器承载业务数据。该BRAS资源池包括多个BRAS，所述多个BRAS包括第一BRAS和第二BRAS。第一服务器执行上述实施例的业务处理方法。其中，第一服务器可以是一个，也即在该一个服务器上运行BRAS和第二BRAS。第一服务器也可以是多个，例如两个，也即在两个服务器上分别运行第一BRAS和第二BRAS。
其中，管理设备从BRAS资源池内选择用于承载第二BRAS的业务的第一BRAS，由于组网形式的不同，可以具体包括几种以下两个实施方式。
实施方式一：若BRAS资源池内包括互为主备的多个BRAS，则管理设备根据每个BRAS的负载情况从多个BRAS中选择一个合适的BRAS作为备BRAS。
具体的，当BRAS资源池内所述多个BRAS中存在某个BRAS(称为第二BRAS)满足切换条件时，则管理设备可以从资源池中当前正在工作的其他BRAS中选择一个合适的BRAS作为第一BRAS，该第一BRAS即为第二BRAS的备BRAS。例如，可以选择当前负载最轻的BRAS作为第二BRAS的备BRAS。又例如，选择其当前负载和第二BRAS负载之和小于其负载上限的BRAS作为第二BRAS的备BRAS。
以下结合图1所示的应用场景，对上述的业务处理方法进行详细说明。
假设BRAS 141、BRAS 142和BRAS 143为主BRAS，切换条件为BRAS故障或者BRAS的负载低于预设值。
在一个场景中，若BRAS 141发生故障，则管理设备可以确定BRAS 141满足切换条件，若此时判断出BRAS 142为轻负载，则可以选择BRAS 142为第一BRAS，即选择BRAS 142作为BRAS 141的备BRAS。这样，可以将BRAS 141的业务迁移到BRAS 142，即将故障BRAS的业务进行了迁移。
在另一场景中，若BRAS 141为轻负载，且BRAS 142为轻负载，即BRAS 141和BRAS 142的负载均低于预设值，此时，可以选择BRAS 141作为第二BRAS，BRAS 142作为第一BRAS，这样，可以将BRAS 141的业务迁移到BRAS 142，使得一个BRAS能够处理两个BRAS的业务，节约BRAS的资源。
实施方式二：若BRAS资源池内包括多个主BRAS和一个冗余BRAS，则管理设备选择冗余BRAS作为多个主BRAS的备BRAS。
具体的，当BRAS资源池内多个主BRAS中存在某个BRAS满足切换条件时，则管理设备可以选择当前未工作的冗余BRAS作为备BRAS，即选择该冗余BRAS作为所述满足切换条件的主BRAS的备BRAS。
继续结合图1所示的应用场景，对上述的业务处理方法进行详细说明。
若BRAS 141和BRAS 142为主BRAS，BRAS 143为冗余BRAS，切换条件为BRAS故障。
在一个场景中，若BRAS 141发生故障，则管理设备可以确定BRAS 141满足切换条件，此时，可以选择冗余BRAS，即BRAS 143作为BRAS 141的备BRAS，这样，可以将BRAS 141的业务迁移到BRAS 143，即将故障BRAS的业务进行了迁移。
当然，上述第一BRAS和第二BRAS的选择方式只是几个示例，对此不做限制，为方便描述，以BRAS 141为第一BRAS，BRAS 142为第二BRAS为例。
在上述应用场景下，业务处理方法可以参见图3所示，该方法可以包括步骤301～310。
步骤301，控制器向所有BRAS发送基础配置，并向主BRAS发送业务配置。其中，基础配置也可以称为全局配置，是BRAS发生故障后不需要进行迁移的配置；业务配置也可以称为接口配置，是BRAS发生故障后需要进行迁移的配置。
例如，若BRAS 141和BRAS 142均为主BRAS，则可以向BRAS 141发送基础配置A’和业务配置A，并向BRAS 142发送基础配置B’和业务配置B。或，若BRAS 141为冗余BRAS，BRAS 142为主BRAS，则可以向BRAS 141发送基础配置A’，但不发送业务配置A，并向BRAS 142发送基础配置B’和业务配置B。
其中，基础配置可以包括但不限于以下之一或者任意组合：数据库服务器的认证密码、数据库服务器的IP地址、数据库服务器的端口号、BRAS的设备标识、DHCP(Dynamic  Host Configuration Protocol，动态主机配置协议)地址池等。当然，上述基础配置只是本申请的几个示例，基础配置还可以包括其它内容，对此基础配置的内容不做限制。不同BRAS的基础配置可以不同，例如，BRAS 141的基础配置A’可以包括数据库服务器181的认证密码、数据库服务器181的IP地址、数据库服务器181的端口号、BRAS 141的设备标识、DHCP地址池1和DHCP地址池2；BRAS 142的基础配置B’可以包括数据库服务器181的认证密码、数据库服务器181的IP地址、数据库服务器181的端口号、BRAS 142的设备标识、DHCP地址池1和DHCP地址池2。
其中，业务配置可以包括但不限于以下之一或者任意组合：接入模式(例如IPoE(Internet Protocol over Ethernet，以太网上承载的因特网协议)方式、PPPoE(Point to Point Protocol over Ethernet，以太网上承载点到点连接协议)方式、认证方式、DHCP地址池的指示信息(用于指示使用哪个DHCP地址池分配地址)等。当然，上述业务配置只是本申请的几个示例，业务配置可以包括其它内容，对此业务配置的内容不做限制。不同BRAS的业务配置可以相同或不同。
在一个例子中，业务配置是与VSI相关的，例如，BRAS 141对应两个VSI时，则控制器可以向BRAS 141发送与第一个VSI对应的第一业务配置、与第二个VSI对应的第二业务配置，这两个业务配置可以相同或不同。为了区别不同VSI的业务配置，控制器151可以向BRAS 141/BRAS 142发送VSI和业务配置，这样，BRAS 141/BRAS 142可以区分不同VSI的业务配置。例如，控制器151向BRAS 141发送VSI 1和业务配置A，向BRAS 142发送VSI 2和业务配置B。
在上述实施例中，控制器151可以通过Netconf协议向所有BRAS发送基础配置，并通过Netconf协议向主BRAS发送业务配置，对此发送方式不做限制。
步骤302，主BRAS根据业务配置对VSI对应的终端设备进行业务处理。例如，BRAS142根据业务配置B对VSI 2对应的终端设备进行业务处理。
在一个示例中，BRAS 141与网关设备131之间可以建立VXLAN(Virtual Extensible LAN，虚拟可扩展局域网)隧道A，且BRAS 141可以建立VXLAN隧道A与VSI 1的对应关系。此外，BRAS 142与网关设备131之间可以建立VXLAN隧道B，且可以建立VXLAN隧道B与VSI 2的对应关系。针对VXLAN隧道A、VXLAN隧道B的建立过程，本实施例中不做限制，如可以采用静态方式建立，也可以采用动态方式建立。
在另一示例中，VXLAN隧道A与VSI 1的对应关系可以是控制器通知给BRAS 141 的，VXLAN隧道B与VSI 2的对应关系可以是控制器通知给BRAS 142的。
进一步的，网关设备131在接收到终端设备111发送的上行报文(如DHCP请求报文或者认证请求报文等)后，可以查询与上行报文的VLAN对应的VXLAN隧道，假设查询到VXLAN隧道B，则可以通过VXLAN隧道B将上行报文发送给BRAS 142。BRAS142通过VXLAN隧道B接收到上行报文后，查询到与VXLAN隧道B对应的VSI 2，然后查询到与该VSI 2对应的业务配置B。
然后，BRAS 142可以根据业务配置B对终端设备111进行业务处理。
例如，若上行报文是DHCP请求报文，则BRAS 142可以根据业务配置B对终端设备111进行地址分配。具体的，BRAS 142从业务配置B中解析出DHCP地址池的信息，并从该DHCP地址池中选择一个可用的IP地址，并将该IP地址分配给终端设备111，然后，可以通过网关设备131向终端设备111发送DHCP响应报文，该DHCP响应报文可以携带该IP地址，对此地址分配过程不做限制。若上行报文是认证请求报文，则BRAS 142可以根据业务配置B对终端设备111进行认证处理。具体的，BRAS 142从业务配置B中解析出接入模式和认证方式，并采用解析出的接入模式和认证方式对终端设备111进行认证，对此认证过程不做限制。
当然，上述方式只是BRAS 142根据业务配置B对终端设备111进行业务处理的两个示例，业务处理还有其它方式，如BRAS 142可以根据业务配置B进行用户控制管理、用户接入控制、用户认证授权计费、地址管理、配置管理等。
步骤303，BRAS 142在生成终端设备111的业务数据之后，可以将该业务数据与BRAS 142的设备标识的对应关系备份到数据库服务器181。
步骤304，数据库服务器181存储该业务数据与该设备标识的对应关系。
在一个例子中，BRAS 142对终端设备111进行业务处理后，可以得到终端设备111的业务数据，如业务数据B”，然后，BRAS 142可以将业务数据B”和BRAS 142的设备标识的对应关系备份到数据库服务器181，数据库服务器181接收并存储该对应关系，如表1所示。
表1
设备标识 业务数据
BRAS 142的设备标识 业务数据B”
在一个例子中，终端设备111的业务数据B”包括但不限于以下之一或任意组合：IP地址、MAC(Media Access Control，介质访问控制)地址、VLAN信息、VPN信息、VXLAN标识、授权信息(如QoS策略、限速策略、统计策略，ACL策略)、用户流量、在线时间等。
步骤305，控制器151确定BRAS 142满足切换条件时，向BRAS 141发送BRAS 142对应的VSI 2和业务配置B，但不发送基础配置B’，并向BRAS 141发送切换命令，该切换命令携带BRAS 142的设备标识。
在一个例子中，控制器151可以周期性向BRAS 142发送心跳报文，在发送预设数量(如10个)的心跳报文后，若均未接收到BRAS 142针对该心跳报文的响应报文，则确定BRAS 142发生故障，并确定BRAS 142满足切换条件。
在另一个例子中，控制器151可以监控BRAS 142和BRAS 141的负载情况，若BRAS 142的负载较轻，且BRAS 141的负载也较轻，则确定BRAS 141和BRAS 142中的一个可以释放，例如BRAS 142被释放，即将BRAS 142的业务迁移到BRAS 141，并确定BRAS 142满足切换条件。
当然，上述只是BRAS 142满足切换条件的示例，对此切换条件不做限制。
在BRAS 142满足切换条件时，控制器151可以从BRAS资源池内选择用于承载BRAS 142的业务的目标BRAS，例如确定目标BRAS为BRAS 141。
例如，若BRAS资源池内包括冗余BRAS，则将冗余BRAS确定为目标BRAS，或者，根据每个主BRAS的负载情况从BRAS资源池内选择一个BRAS，并将选择的BRAS确定为目标BRAS，例如将负载较轻的BRAS确定为目标BRAS。
然后，控制器151可以向BRAS 141发送BRAS 142对应的VSI 2和业务配置B，并向BRAS 141发送切换命令，该切换命令携带BRAS 142的设备标识。
其中，控制器151可以维护所有BRAS的设备标识、业务配置、基础配置、VSI等内容，因此，在BRAS 142满足切换条件时，控制器151可以从本地查询到BRAS 142的设备标识、业务配置B、VSI 2等信息，并向BRAS 141发送VSI 2和业务配置B，并向BRAS 141发送携带BRAS 142的设备标识的切换命令。
步骤306，BRAS 141接收控制器151发送的BRAS 142对应的VSI 2和业务配置B，并接收控制器151发送的切换命令。其中，该切换命令携带BRAS 142的设备标识。
步骤307，BRAS 141从数据库服务器181获取与BRAS 142的设备标识对应的业务数据B”。参见表1，数据库服务器181存储有BRAS 142的设备标识与业务数据B”的对应关系，BRAS 141可从数据库服务器181获取业务数据B”。
步骤308，BRAS 141将业务数据的已经恢复完成的通知消息发送给控制器151，以使控制器151将终端设备的上行报文从BRAS 142迁移到BRAS 141。
其中，在获取到所有业务数据前，数据恢复标记为第二标识，BRAS 141在从数据库服务器181获取到BRAS 142的所有业务数据(如BRAS 142可能将大量业务数据备份到数据库服务器181，BRAS 141可以从数据库服务器181获取BRAS 142的所有业务数据)后，将数据恢复标记设置为第一标识。由此实现数据的备份和恢复功能。
进一步的，控制器151向BRAS 141发送切换命令后，可以周期性向BRAS 141发送查询命令，BRAS 141接收到查询命令后，若数据恢复标记为第二标识，则BRAS 141将业务数据的未恢复完成的通知消息发送给控制器151，这样，控制器151在下一个周期继续向BRAS 141发送查询命令，若数据恢复标记为第一标识，则BRAS 141将业务数据的已经恢复完成的通知消息发送给控制器151，这样，控制器151获知业务数据已经恢复完成，并停止发送查询命令，并将终端设备的上行报文从BRAS 142迁移到BRAS 141。
在一个例子中，为了将终端设备的上行报文从BRAS 142迁移到BRAS 141，则可以采用如下方式：控制器151将网关设备131的VXLAN隧道B的目的地址(如IP地址、MAC地址等，后续以IP地址为例)修改为BRAS 141的地址(如IP地址、MAC地址等)，从而将目的为BRAS 142的上行报文迁移到BRAS 141。
在上述实施例中已经介绍，网关设备131可以与BRAS 141建立VXLAN隧道A，网关设备131可以与BRAS 142建立VXLAN隧道B。基于此，若控制器151将网关设备131的VXLAN隧道B的目的IP地址修改为BRAS 141的IP地址，则网关设备131在通过VXLAN隧道B发送上行报文(即终端设备发送的报文)时，将上行报文发送给BRAS 141，而不是发送给BRAS 142，从而将目的为BRAS 142的上行报文迁移到BRAS 141，即实现了业务迁移。
进一步的，控制器151还可以通知BRAS 141与网关设备131建立VXLAN隧道B，并记录VXLAN隧道B与VSI 2的对应关系。
例如，网关设备131在接收到已上线的终端设备发送的上行报文(如上行数据报文)， 且该终端设备如上述终端设备111是在BRAS 142上线，则网关设备131需要通过VXLAN隧道B发送上行报文，由于VXLAN隧道B的目的IP地址为BRAS 141的IP地址(而不再是BRAS 142的IP地址)，因此网关设备131通过VXLAN隧道B将上行报文发送给BRAS 141。
又例如，网关设备131在接收到待上线的终端设备发送的上行报文(如上行DHCP请求报文或上行认证请求报文)后，可以查询与上行报文的VLAN对应的VXLAN隧道，假设查询到VXLAN隧道B，由于VXLAN隧道B的目的IP地址为BRAS 141的IP地址(而不再是BRAS 142的IP地址)，因此网关设备131通过VXLAN隧道B将上行报文发送给BRAS 141。
步骤309，BRAS 141根据业务数据B”对终端设备进行业务处理，BRAS 141根据BRAS 142的业务配置B对VSI 2对应的终端设备进行业务处理。
在一个例子中，针对在BRAS 142上线的终端设备，如上述的终端设备111，BRAS141在获取到终端设备111的业务数据B”后，可以根据该业务数据B”对终端设备111进行业务处理，以下结合具体例子，对业务处理过程进行说明。
情况一、BRAS 141从业务数据B”中获取终端设备111的计费信息(如在线时间、用户流量)，并根据该计费信息对终端设备111进行计费处理。
具体的，由于业务数据B”可以包括用户流量、在线时间等计费信息，因此，BRAS141可以从业务数据B”中获取终端设备111的用户流量和在线时间，并在该用户流量和该在线时间的基础上，继续统计终端设备111的用户流量和在线时间，从而基于用户流量和在线时间对终端设备111进行计费。
情况二、BRAS 141可以从业务数据B”中获取终端设备111的IP地址、MAC地址、VLAN信息、VPN信息、VXLAN标识等内容，并可以利用上述IP地址、MAC地址、VLAN信息、VPN信息、VXLAN标识等内容生成转发表项，并通过该转发表项指导BRAS 141进行报文的转发，对此转发过程不做限制。
情况三、BRAS 141可以从业务数据B”中获取终端设备111的QoS策略，并通过QoS策略指导BRAS 141对终端设备111实现QoS控制；从业务数据B”中获取终端设备111的限速策略，并通过限速策略指导BRAS 141对终端设备111实现CAR；从业务数据B”中获取终端设备111的统计策略，并通过统计策略指导BRAS 141对终端设备111实现流量统计；从业务数据B”中获取终端设备111的ACL策略，并通过ACL 策略指导BRAS 141对终端设备111实现ACL控制。
情况四、BRAS 141从业务数据B”中获取终端设备111的地址信息(如IP地址)，并发布携带该IP地址的路由，该路由用于使网关设备131将目的为终端设备111的下行报文从BRAS 142迁移到BRAS 141，从而实现业务的迁移。
其中，为了将目的为终端设备111的下行报文从BRAS 142迁移到BRAS 141，则可以采用如下方式：BRAS 141发布携带终端设备111的IP地址的路由给网关设备131，网关设备131接收到该路由后，将终端设备111的IP地址对应的出接口学习到BRAS 141，从而将目的为终端设备111的下行报文迁移到BRAS 141。
例如，假设终端设备111的IP地址为IP地址111，网关设备131与BRAS 141连接的接口为1311，网关设备131与BRAS 142连接的接口为1312。在BRAS 142为终端设备111提供服务时，可以发布携带IP地址111的路由给网关设备131，网关设备131可以生成表2所示的路由表项。在将目的为终端设备111的下行报文从BRAS 142迁移到BRAS 141时，则BRAS 141可以从业务数据B”中获取终端设备111的IP地址111，并发布携带IP地址111的路由给网关设备131，网关设备131接收到该路由后，确定IP地址111对应的出接口从1312迁移到1311，并将表2所示的路由表项修改为表3。
表2
目的IP地址 出接口
IP地址111 1312
表3
目的IP地址 出接口
IP地址111 1311
进一步，参见表3所示，网关设备131在接收到目的IP地址为IP地址111的下行报文(如下行数据报文，可以是互联网发送给终端设备111的数据报文)时，可以通过出接口1311将下行报文发送给BRAS 141，从而将目的为终端设备111的下行报文迁移到BRAS 141，实现业务的迁移。而BRAS 141在接收到该下行报文后，还可以将该下行报文发送给终端设备111，对此发送过程不做限制。
当然，上述几种情况，只是BRAS 141根据业务数据B”对终端设备111进行业务处理的示例，对此业务处理过程不做限制，可以根据实际情况实现。
在一个例子中，BRAS 141根据BRAS 142的业务配置B对VSI 2对应的终端设备进行业务处理，还可以包括：针对待上线的终端设备，如终端设备112，网关设备131在接收到终端设备112发送的上行报文(如DHCP请求报文或者认证请求报文)后，可以查询与上行报文的VLAN对应的VXLAN隧道，假设查询到VXLAN隧道B，则可以通过VXLAN隧道B将上行报文发送给BRAS 141。
进一步的，BRAS 141在通过VXLAN隧道B接收到上行报文之后，可以查询到与VXLAN隧道B对应的VSI 2，并查询到与VSI 2对应的业务配置B。
若上行报文是DHCP请求报文，则BRAS 141可以根据业务配置B对终端设备112进行地址分配。例如，BRAS 141可以从业务配置B中解析出DHCP地址池的信息，并从DHCP地址池中选择一个可用的IP地址，将该IP地址分配给终端设备112，对此地址分配过程不做限制。若上行报文是认证请求报文，则BRAS 141可以根据业务配置B对终端设备112进行认证处理。例如，BRAS 141可以从业务配置B中解析出接入模式和认证方式，采用该接入模式和认证方式对终端设备112进行认证，对此认证过程不做限制。
在一个例子中，BRAS 141还可以根据BRAS 141的业务配置A对VSI 1对应的终端设备进行业务处理，具体的，针对待上线的终端设备，如终端设备113，网关设备131在接收到终端设备113发送的上行报文后，可以查询与上行报文的VLAN对应的VXLAN隧道，假设查询到VXLAN隧道A，则可以通过VXLAN隧道A将上行报文发送给BRAS 141。BRAS 141在通过VXLAN隧道A接收到该上行报文后，查询到与VXLAN隧道A对应的VSI 1，并查询到与VSI 1对应的业务配置A。然后，BRAS 141可以根据业务配置A对终端设备113进行业务处理，如对终端设备113进行地址分配、认证处理等处理。
步骤310，BRAS 141在对终端设备进行业务处理后，可以重新生成终端设备的业务数据，并将该业务数据与BRAS 141的设备标识的对应关系备份到数据库服务器181。数据库服务器181存储该业务数据与该设备标识的对应关系。
其中，步骤310可以参见步骤303和步骤304，在此不再重复赘述。
在上述实施例中，每个BRAS均可以包括一个数据库模块(也可以称为数据库 进程，如独立运行在BRAS的RedisDBM进程)和至少一个业务模块(也可以称为业务进程，如独立运行在BRAS的IPoE进程、PPPoE进程、DHCP进程等，IPoE进程用于实现IPoE接入方式的认证，PPPoE进程用于实现PPPoE接入方式的认证，DHCP进程用于实现地址分配)。
其中，BRAS的数据库模块可以与数据库服务器181建立长连接(例如，数据库模块可以获取数据库服务器181的认证密码、IP地址及端口号等基础配置，并根据基础配置与数据库服务器181建立长连接)，BRAS的业务模块可以与数据库模块建立连接。基于此，业务模块可以生成业务数据，并可以将业务数据写入到数据库服务器181(如上述步骤303-304、步骤310的写入过程)，本实施例对于业务模块生成业务数据的过程不做限制。
具体的，业务模块可以将业务数据发送给数据库模块，数据库模块在接收到业务数据后，可以获得设备标识，通过上述长连接将该业务数据和设备标识存储到数据库服务器181。在需要从数据库服务器181读取业务数据时(如上述步骤306-307，在接收到切换命令后，读取业务数据)，数据库模块可以通过上述长连接从数据库服务器181读取到业务数据，并将业务数据发送给业务模块。
在上述应用场景下，针对上述步骤307，BRAS 141从数据库服务器181获取业务数据B”的过程，其实现流程可以参见图4所示，该流程可以包括以下步骤401～416。
步骤401，BRAS 141的数据库模块在接收到控制器发送的切换命令(也可以称为数据恢复开始消息)后，通知各业务模块开始进行数据恢复，即告知业务模块准备要恢复业务数据，并从该切换命令获取BRAS 142的设备标识。
步骤402，数据库模块向数据库服务器181发送查询请求，该查询请求携带BRAS142的设备标识，如数据库模块通过上述长连接发送查询请求。
步骤403，数据库服务器181在接收到该查询请求后，从该查询请求中解析出BRAS 142的设备标识，并查询到与该设备标识对应的业务数据B”。
步骤404，数据库服务器181向BRAS 141返回携带业务数据B”的查询响应。
步骤405，数据库模块接收该查询响应，并从该查询响应中获取业务数据B”。
步骤406，数据库模块将业务数据B”推送给各业务模块。
其中，数据库模块可能从数据库服务器181获取多个业务数据，每获取到一个 业务数据，数据库模块就可以将该业务数据推送给各业务模块。
业务模块在接收到业务数据B”后，还可以重新组织业务数据B”。例如，数据库服务器181存储的业务数据B”为第一格式，而业务模块需要的业务数据B”是第二格式，则业务模块可以将接收到的业务数据B”转换为第二格式，当然，上述只是重新组织业务数据B”的示例，对此重新组织的方式不做限制。
步骤407，在业务数据推送完成后，数据库模块向业务模块发送数据推送完成消息，该数据推送完成消息表示BRAS 142的所有业务数据已经推送完成。
步骤408，数据库模块在接收到业务数据B”后，向数据库服务器181发送更新请求，该更新请求携带BRAS 141的设备标识和BRAS 142的设备标识。
步骤409，数据库服务器181在接收到更新请求后，根据该更新请求将业务数据B”对应的设备标识，从BRAS 142的设备标识更新为BRAS 141的设备标识。
步骤410，业务模块在接收到数据推送完成消息后，向数据库模块发送数据接收完成消息，该数据接收完成消息表示业务模块已经接收并处理完所有业务数据。
步骤411，数据库模块检测是否接收到所有业务模块的数据接收完成消息。
如果是，则表示所有业务模块均已经接收完所有业务数据，可以执行步骤412，如果否，则表示还有业务模块未接收完所有业务数据，可以继续等待。
步骤412，数据库模块向所有业务模块发送同步完成消息，表示已经接收到所有业务模块的数据接收完成消息，所有业务模块均已经接收完所有业务数据。
步骤413，业务模块接收到同步完成消息后，进行业务模块的数据平滑操作。
步骤414，在数据平滑结束后，业务模块向数据库模块发送平滑完成消息。
步骤415，数据库模块在接收到所有业务模块的平滑完成消息后，向各业务模块发送业务处理消息，以使各业务模块根据业务数据进行业务处理。
步骤416，数据库模块将业务数据的已经恢复完成的通知消息发送给控制器151，以使控制器151将终端设备的上行报文从BRAS 142迁移到BRAS 141。
基于与上述方法同样的申请构思，本申请实施例还提出一种业务处理装置，应用于BRAS资源池内的第一BRAS。参见图5所示，为该装置的结构图，该装置包括：接收模块501、获取模块502和处理模块503。接收模块501用于接收管理设备发送的切换命令，所述切换命令携带BRAS资源池内第二BRAS的设备标识，所述切换命令是 所述管理设备确定所述第二BRAS满足切换条件时发送的。获取模块502用于从数据库服务器获取与所述第二BRAS的设备标识对应的业务数据，所述业务数据是所述第二BRAS备份到数据库服务器的与终端设备关联的业务数据。处理模块503用于根据所述业务数据对所述终端设备进行业务处理。
获取模块502具体用于：获取数据库服务器的基础配置；根据所述基础配置向数据库服务器发送携带所述第二BRAS的设备标识的查询请求；接收所述数据库服务器针对所述查询请求返回的查询响应，所述查询响应携带所述数据库服务器获得的与所述第二BRAS的设备标识对应的业务数据。
在一个例子中，如图6所示，所述装置还包括第一发送模块504。第一发送模块504，用于在所述获取模块502从数据库服务器获取与所述第二BRAS的设备标识对应的业务数据之后，向所述数据库服务器发送更新请求，所述更新请求携带所述第一BRAS的设备标识和所述第二BRAS的设备标识；其中，所述更新请求用于请求所述数据库服务器将数据库服务器中与所述业务数据对应的第二BRAS的设备标识更新为所述第一BRAS的设备标识。
在一个例子中，如图7所示，所述装置还包括第二发送模块505。第二发送模块505，用于在所述获取模块502从数据库服务器获取与所述第二BRAS的设备标识对应的业务数据之后，将所述业务数据的已经恢复完成的通知消息发送给管理设备，以使管理设备将所述终端设备的上行报文从所述第二BRAS迁移到第一BRAS。
所述处理模块503具体用于：从所述业务数据中获取所述终端设备的计费信息，并根据所述计费信息对所述终端设备进行计费处理；和/或，从所述业务数据中获取所述终端设备的地址信息，发布携带所述地址信息的路由，所述路由用于使网关设备将目的为所述终端设备的下行报文从所述第二BRAS迁移到所述第一BRAS。
在一个例子中，如图8所示，所述装置还包括生成模块506。生成模块506，用于在所述处理模块503对所述终端设备进行业务处理之后，生成终端设备的业务数据，并将生成的业务数据与所述第一BRAS的设备标识的对应关系备份到所述数据库服务器。
本申请实施例提供的BRAS(如上述第一BRAS)，从硬件层面而言，BRAS的硬件架构示意图可以参见图9。BRAS包括：机器可读存储介质901和处理器902。
机器可读存储介质901存储指令代码，例如业务处理指令902。
处理器902与机器可读存储介质901通信，读取和执行机器可读存储介质中存储的所述指令代码，实现本申请上述示例公开的业务处理操作。
具体的，接收管理设备发送的切换命令，所述切换命令携带第二BRAS的设备标识，所述切换命令是所述管理设备确定所述第二BRAS满足切换条件时发送的；从数据库服务器获取与所述第二BRAS的设备标识对应的业务数据，所述业务数据是所述第二BRAS备份到所述数据库服务器的与终端设备关联的业务数据；根据所述业务数据对所述终端设备进行业务处理。
这里，机器可读存储介质901可以是任何电子、磁性、光学或其它物理存储装置，可以包含或存储信息，如可执行指令、数据，等等。例如，机器可读存储介质可以是：RAM(Radom Access Memory，随机存取存储器)、易失存储器、非易失性存储器、闪存、存储驱动器(如硬盘驱动器)、固态硬盘、任何类型的存储盘(如光盘、dvd等)，或者类似的存储介质，或者它们的组合。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机，计算机的具体形式可以是个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件收发设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任意几种设备的组合。
为了描述的方便，描述以上装置时以功能分为各种单元分别描述。当然，在实施本申请时可以把各单元的功能在同一个或多个软件和/或硬件中实现。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请实施例可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可以由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其它可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其它可编程数据处理设备的处理器执行的 指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
而且，这些计算机程序指令也可以存储在能引导计算机或其它可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或者多个流程和/或方框图一个方框或者多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其它可编程数据处理设备上，使得在计算机或者其它可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其它可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
以上所述仅为本申请的实施例而已，并不用于限制本申请。对于本领域技术人员来说，本申请可以有各种更改和变化。凡在本申请的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本申请的权利要求范围之内。

Claims (15)

  1. 一种业务处理方法，应用于宽带远程接入服务器BRAS资源池内的第一BRAS，所述方法包括：
    接收管理设备发送的切换命令，所述切换命令携带所述BRAS资源池内的第二BRAS的设备标识，所述切换命令是所述管理设备确定所述第二BRAS满足切换条件时发送的；
    从数据库服务器获取与所述第二BRAS的设备标识对应的业务数据，所述业务数据是所述第二BRAS备份到所述数据库服务器的与终端设备关联的业务数据；
    根据所述业务数据对所述终端设备进行业务处理。
  2. 根据权利要求1所述的方法，其特征在于，
    所述BRAS资源池内包括互为主备的多个BRAS，所述第一BRAS为互为主备的多个BRAS中满足预设条件的任一BRAS；或者，
    所述BRAS资源池内包括多个主BRAS和一个冗余BRAS，所述第一BRAS为所述冗余BRAS。
  3. 根据权利要求1所述的方法，其特征在于，从所述数据库服务器获取与所述第二BRAS的设备标识对应的业务数据，包括：
    获取所述数据库服务器的基础配置；
    根据所述基础配置向所述数据库服务器发送携带所述第二BRAS的设备标识的查询请求；
    接收所述数据库服务器针对所述查询请求返回的查询响应，所述查询响应携带所述数据库服务器获得的与所述第二BRAS的设备标识对应的业务数据。
  4. 根据权利要求1所述的方法，其特征在于，从所述数据库服务器获取与所述第二BRAS的设备标识对应的业务数据之后，所述方法还包括：
    向所述数据库服务器发送更新请求，所述更新请求携带所述第一BRAS的设备标识和所述第二BRAS的设备标识；
    其中，所述更新请求用于请求所述数据库服务器将所述数据库服务器中与所述业务数据对应的第二BRAS的设备标识更新为所述第一BRAS的设备标识。
  5. 根据权利要求1所述的方法，其特征在于，从所述数据库服务器获取与所述设备标识对应的业务数据之后，所述方法还包括：
    将所述业务数据的已经恢复完成的通知消息发送给所述管理设备，以使所述管理设备将所述终端设备的上行报文从所述第二BRAS迁移到所述第一BRAS。
  6. 根据权利要求1所述的方法，其特征在于，根据所述业务数据对所述终端设备进行业务处理，包括：
    从所述业务数据中获取所述终端设备的计费信息，并根据所述计费信息对所述终端设备进行计费处理；和/或，
    从所述业务数据中获取所述终端设备的地址信息，发布携带所述地址信息的路由，所述路由用于使网关设备将目的为所述终端设备的下行报文从所述第二BRAS迁移到所述第一BRAS。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，所述方法还包括：
    在对所述终端设备进行业务处理后，生成所述终端设备的业务数据，并将生成的业务数据与所述第一BRAS的设备标识的对应关系备份到所述数据库服务器。
  8. 一种业务处理系统，所述系统包括：管理设备、数据库服务器、宽带远程接入服务器BRAS资源池，所述BRAS资源池中包括多个BRAS，其中：
    在所述管理设备确定所述多个BRAS中的第二BRAS满足切换条件时，从所述多个BRAS内选择用于承载所述第二BRAS的业务的第一BRAS；
    所述管理设备向所述第一BRAS发送切换命令，所述切换命令携带所述第二BRAS的设备标识；
    所述第一BRAS用于执行如权利要求1-6任一项所述的方法。
  9. 根据权利要求8所述的系统，其特征在于，所述从所述BRAS资源池内选择用于承载所述第二BRAS的业务的第一BRAS，具体包括：
    若所述BRAS资源池内包括互为主备的多个BRAS，则所述管理设备根据每个BRAS的负载情况从所述多个BRAS中选择一个BRAS作为第一BRAS；
    若所述BRAS资源池内包括多个主BRAS和一个冗余BRAS，则所述管理设备选择所述冗余BRAS作为第一BRAS；
    其中，所述第一BRAS是第二BRAS的备BRAS。
  10. 一种业务处理装置，应用于宽带远程接入服务器BRAS资源池内的第一BRAS，所述装置包括：
    接收模块，用于接收管理设备发送的切换命令，所述切换命令携带所述BRAS资源池内第二BRAS的设备标识，所述切换命令是所述管理设备确定所述第二BRAS满足切换条件时发送的；
    获取模块，用于从数据库服务器获取与所述第二BRAS的设备标识对应的业务数据，所述业务数据是所述第二BRAS备份到所述数据库服务器的与终端设备关联的业务数 据；
    处理模块，用于根据所述业务数据对所述终端设备进行业务处理。
  11. 根据权利要求10所述的装置，其特征在于，所述获取模块具体用于：
    获取所述数据库服务器的基础配置；
    根据所述基础配置向所述数据库服务器发送携带所述第二BRAS的设备标识的查询请求；
    接收所述数据库服务器针对所述查询请求返回的查询响应，所述查询响应携带所述数据库服务器获得的与所述第二BRAS的设备标识对应的业务数据。
  12. 根据权利要求10所述的装置，其特征在于，还包括：
    第一发送模块，用于在所述获取模块从所述数据库服务器获取与所述第二BRAS的设备标识对应的业务数据之后，向所述数据库服务器发送更新请求，所述更新请求携带所述第一BRAS的设备标识和所述第二BRAS的设备标识；
    其中，所述更新请求用于请求所述数据库服务器将所述数据库服务器中与所述业务数据对应的第二BRAS的设备标识更新为所述第一BRAS的设备标识。
  13. 根据权利要求10所述的装置，其特征在于，还包括：
    第二发送模块，用于在所述获取模块从所述数据库服务器获取与所述第二BRAS的设备标识对应的业务数据之后，将所述业务数据的已经恢复完成的通知消息发送给所述管理设备，以使所述管理设备将所述终端设备的上行报文从所述第二BRAS迁移到第一BRAS。
  14. 根据权利要求10所述的装置，其特征在于，所述处理模块具体用于：
    从所述业务数据中获取所述终端设备的计费信息，并根据所述计费信息对所述终端设备进行计费处理；和/或，
    从所述业务数据中获取所述终端设备的地址信息，发布携带所述地址信息的路由，所述路由用于使网关设备将目的为所述终端设备的下行报文从所述第二BRAS迁移到所述第一BRAS。
  15. 根据权利要求10-14任一项所述的装置，其特征在于，还包括：
    生成模块，用于在所述处理模块对所述终端设备进行业务处理之后，生成所述终端设备的业务数据，并将生成的业务数据与所述第一BRAS的设备标识的对应关系备份到所述数据库服务器。
PCT/CN2019/093166 2018-06-28 2019-06-27 业务处理 WO2020001514A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810691277.1A CN110061855B (zh) 2018-06-28 2018-06-28 一种业务处理方法、系统和装置
CN201810691277.1 2018-06-28

Publications (1)

Publication Number Publication Date
WO2020001514A1 true WO2020001514A1 (zh) 2020-01-02

Family

ID=67315366

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/093166 WO2020001514A1 (zh) 2018-06-28 2019-06-27 业务处理

Country Status (2)

Country Link
CN (1) CN110061855B (zh)
WO (1) WO2020001514A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111654384A (zh) * 2019-09-27 2020-09-11 中兴通讯股份有限公司 一种主备切换方法、bras设备及存储介质
CN112511326B (zh) 2020-03-16 2024-02-02 中兴通讯股份有限公司 一种切换方法、装置、设备和存储介质
CN114531394B (zh) * 2020-11-20 2023-11-17 华为技术有限公司 一种数据同步方法及装置
CN112860661B (zh) * 2021-01-20 2022-11-08 上海万物新生环保科技集团有限公司 一种数据序列标识的生成方法及设备
CN113225628B (zh) * 2021-04-25 2023-02-10 中国移动通信集团陕西有限公司 一种业务数据配置方法、装置、设备及计算机存储介质
CN114070715A (zh) * 2021-11-11 2022-02-18 中国电信股份有限公司 通信系统的备用通信通道搭建方法、装置及电子设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101902357A (zh) * 2010-06-29 2010-12-01 中兴通讯股份有限公司 对业务服务器进行调度的方法和系统
EP2536068A1 (en) * 2011-06-18 2012-12-19 Deutsche Telekom AG Virtual subscriber management
CN104994071A (zh) * 2015-05-28 2015-10-21 杭州华三通信技术有限公司 宽带远程接入服务器设备的备份方法及装置
CN106657330A (zh) * 2016-12-22 2017-05-10 北京华为数字技术有限公司 用户数据迁移方法和用户数据备份方法、装置及系统
CN107547675A (zh) * 2017-05-26 2018-01-05 新华三技术有限公司 一种用户设备迁移方法和装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106407045B (zh) * 2016-09-29 2019-09-24 郑州云海信息技术有限公司 一种数据灾难恢复方法、系统及服务器虚拟化系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101902357A (zh) * 2010-06-29 2010-12-01 中兴通讯股份有限公司 对业务服务器进行调度的方法和系统
EP2536068A1 (en) * 2011-06-18 2012-12-19 Deutsche Telekom AG Virtual subscriber management
CN104994071A (zh) * 2015-05-28 2015-10-21 杭州华三通信技术有限公司 宽带远程接入服务器设备的备份方法及装置
CN106657330A (zh) * 2016-12-22 2017-05-10 北京华为数字技术有限公司 用户数据迁移方法和用户数据备份方法、装置及系统
CN107547675A (zh) * 2017-05-26 2018-01-05 新华三技术有限公司 一种用户设备迁移方法和装置

Also Published As

Publication number Publication date
CN110061855B (zh) 2021-01-26
CN110061855A (zh) 2019-07-26

Similar Documents

Publication Publication Date Title
WO2020001514A1 (zh) 业务处理
CN108616431B (zh) 一种报文处理方法、装置、设备及机器可读存储介质
US10063470B2 (en) Data center network system based on software-defined network and packet forwarding method, address resolution method, routing controller thereof
US10812394B2 (en) Virtual network device and related method
US8953618B2 (en) IP multicast service leave process for MPLS-based virtual private cloud networking
US8831000B2 (en) IP multicast service join process for MPLS-based virtual private cloud networking
US11005752B2 (en) Packet transmission
CN110635987B (zh) 一种报文传输方法、装置、设备及机器可读存储介质
WO2019047855A1 (zh) 一种bras转控分离的备份方法和装置
JP6043879B2 (ja) ＯｐｅｎＦｌｏｗ有効化クラウドコンピューティングにおいてＭＰＬＳを用いる場合のテナント固有データの分離のための装置及び方法
CN108667575B (zh) 一种bras转控分离的备份方法和装置
CN108737224B (zh) 一种基于微服务架构的报文处理方法和装置
CN109587286B (zh) 一种设备接入控制方法及装置
US10671421B2 (en) Virtual machine start method and apparatus
WO2016107512A1 (zh) 胖树网络中的组播组建立方法、装置及胖树网络
US11824765B2 (en) Fast redirect of traffic when pods fail
US20210176172A1 (en) Packet forwarding method, device and apparatus, and storage medium
CN103631652A (zh) 虚拟机迁移的实现方法及系统
CN117546537A (zh) 用于基于无线电的网络的分布式用户平面功能
WO2016095142A1 (zh) 软件定义网络sdn中数据转发的方法、设备和系统
CN112804276B (zh) 虚拟化宽带远程接入服务器及其控制方法、通信系统
WO2020181733A1 (zh) 一种基于vpc的多数据中心互通方法及相关设备
JP6369730B2 (ja) 仮想マシン始動方法及び装置
WO2018113633A1 (zh) 报文转发方法、报文转发控制器、bras、计算机存储介质
US11245660B1 (en) Communication of endpoint information among virtual switches

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19826537

Country of ref document: EP

Kind code of ref document: A1