WO2018113633A1

WO2018113633A1 - Packet forwarding method, packet forwarding controller, bras, and computer storage medium

Info

Publication number: WO2018113633A1
Application number: PCT/CN2017/116994
Authority: WO
Inventors: 郑坤
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-12-21
Filing date: 2017-12-18
Publication date: 2018-06-28
Also published as: CN108234322A

Abstract

Disclosed in embodiments of the present application are a packet forwarding method, a packet forwarding controller, a BRAS, and a computer storage medium. The method comprises: receiving a forwarded packet; querying for a floating interface according to a destination media access control (MAC) address of the forwarded packet, and determining whether an outbound interface is a floating interface; if the outbound interface is a floating interface, querying for an access physical interface according to a binding relationship between the access physical interface and the floating interface; and forwarding the packet according to the access physical interface.

Description

Packet forwarding method, message forwarding controller, BRAS, computer storage medium

Cross-reference to related applications

The present application is filed on the basis of the Chinese Patent Application No. PCT Application No. No. No. No. No. No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No

Technical field

The present application relates to a packet forwarding method, a packet forwarding controller, a broadband access server (BRAS), and a computer storage medium.

Background technique

BRAS is an access gateway for broadband network applications. It is a bridge between the broadband access network and the backbone network, providing basic access means and management functions of the broadband access network. The BRAS is located at the edge of the network and provides broadband access services to achieve convergence and forwarding of multiple services. It can meet the requirements of different users for transmission capacity and bandwidth utilization. Therefore, the BRAS is the core device for broadband user access. The BRAS first authenticates the accessed user. The authentication allows the user to access the broadband network, and the authentication fails to deny the user access.

As a broadband service gateway, the BRAS is located at the edge of the metropolitan area network. To ensure carrier-class reliability, the BRAS is usually deployed to implement 1:1 or 1+1 backup. When a 1:1 backup is implemented, only the primary device can perform broadband service processing and data traffic forwarding, and the standby device is idle, resulting in wasted processing performance. When the 1+1 backup is performed, the two BRAS devices perform load balancing for the primary and backup devices, which solves the problem of device idleness to some extent. However, the load balancing policy is performed according to the VLAN. If the VLANs of the users are not evenly distributed, the load sharing of the BRAS devices is not implemented. The problem of both.

Moreover, due to the above problems, the BRAS device cannot form the management of the pool, and cannot be the most Current traffic forwarding reliability and load sharing.

Summary of the invention

To solve the above technical problem, the embodiment of the present application provides a packet forwarding method based on a broadband access server, a packet forwarding controller, a broadband access server (BRAS), and a computer storage medium.

The technical solution of the embodiment of the present application is as follows:

A packet forwarding method, the method comprising:

Receiving and forwarding packets;

Query the floating interface based on the destination MAC address of the forwarding packet to determine whether the interface is a floating interface.

When the outbound interface is a floating interface, the access physical interface is queried according to the binding relationship between the physical interface and the floating interface.

Forwarding the packet according to the access physical interface.

In the embodiment of the present application, the method further includes:

When the floating interface is not found based on the destination MAC address, the currently received packet is discarded.

In the embodiment of the present application, the method further includes:

The outbound interface is the physical interface on the network side and forwards packets directly from the physical interface on the network side.

In the embodiment of the present application, the method includes:

And reporting the access request message to the packet forwarding controller, where the access request message is used by the packet forwarding controller to determine the access physical interface, and according to the binding of the access physical interface and the floating interface The relationship determines the bound floating interface, and generates a forwarding table for forwarding the packet.

And receiving, by the packet forwarding controller, an access response packet, where the access response packet carries the forwarding table.

In the embodiment of the present application, the method includes:

And reporting, by the packet forwarding controller, information about accessing the physical interface;

The information of the access physical interface is used to query the physical interface of the BRAS pool and the floating interface of the unbound physical interface;

Receiving a binding relationship between the access physical interface and the floating interface that is fed back by the packet forwarding controller after the binding physical interface is bound to the floating interface.

A packet forwarding method, the method comprising:

Receiving the access request message sent by the BRAS in the BRAS pool of the broadband access server, selecting the access physical interface and selecting the floating interface, completing the BRAS access, and generating a forwarding table, where the interface associated with the forwarding table is The selected floating interface.

In the embodiment of the present application, the method includes:

Receiving the physical interface information of the access report reported by the BRAS in the BRAS pool, and configuring the floating interface;

Query the physical interface of the BRAS pool and query the floating interface that has no binding relationship.

Configure the unbound physical interface to be bound to the floating interface and record the binding relationship.

In the embodiment of the present application, the method includes:

Receiving an access request message sent by the access physical interface of the BRAS, and querying a floating interface that is bound to the currently accessed physical interface; when the number of floating interfaces is more than one, a floating interface is selected;

Generating a forwarding table, and sending an access response message to the BRAS, where the access response packet carries the forwarding table.

In the embodiment of the present application, the method further includes:

When it is detected that the first BRAS is unavailable, the user of the first BRAS is migrated to at least one other available BRAS based on a pre-configured orchestration policy.

In the embodiment of the present application, the detecting that the first BRAS cannot be used includes:

When it is detected that the first BRAS is unavailable, determining that the first BRAS accesses the physical connection And querying the floating interface bound to the physical interface of the first BRAS. When the floating interface of the query is more than one, select a floating interface as the bound floating interface; and query the floating interface according to the binding. Decoding a forwarding table associated with the first BRAS, and deleting an access physical interface of the first BRAS.

In the embodiment of the present application, the migrating the user of the first BRAS to the at least one other available BRAS includes:

Querying an access physical interface of the at least one other available BRAS, and binding the floating interface associated with the first BRAS to the access physical interface of the at least one other available BRAS;

Updating the binding relationship to a binding relationship between the floating interface of the first BRAS and the access physical interface of the at least one other available BRAS, and updating the binding relationship to the at least one other available BRAS notice;

The updated forwarding table is notified to the at least one other available BRAS.

In the embodiment of the present application, the scheduling policy is: when the first BRAS is selected to be migrated to the second BRAS, the user of the first BRAS is migrated to the at least one other available BRAS, including:

Querying the access physical interface of the first BRAS, querying the floating interface bound to the physical interface of the first BRAS, and selecting a floating interface as the bound floating interface when the floating interface is more than one; The bound floating interface queries the forwarding table associated with the first BRAS, and reclaims the forwarding table and the floating interface.

Querying the access physical interface of the second BRAS, and binding the floating interface associated with the first BRAS to the access physical interface of the second BRAS;

Updating a binding relationship between the first BRAS floating interface and a physical interface of the second BRAS, and notifying the binding relationship to the second BRAS, and notifying the updated forwarding table to the second BRAS.

In the embodiment of the present application, when the scheduling policy is time-migrated, the user of the first BRAS is migrated to at least one other available BRAS, including:

When the migration time expires to trigger the migration, the physical interface of the first BRAS is queried, and the floating interface bound to the physical interface of the first BRAS is queried. When the floating interface of the query is more than one, a floating interface is selected. As a binding floating interface; and querying, according to the bound floating interface, the forwarding table associated with the first BRAS, and notifying the first BRAS to reclaim the forwarding table and the floating interface;

Updating a binding relationship between the first BRAS floating interface and the physical interface of the second BRAS, and notifying the binding relationship and the updated forwarding table to the second BRAS.

A broadband access server, the server comprising:

The floating interface component is configured to receive the forwarded packet; the media interface access control MAC address is used to query the floating interface according to the destination of the forwarded packet, and the interface is determined to be a floating interface; if the outgoing interface is a floating interface, the triggering is performed. Access physical interface components;

The physical interface component is configured to forward the packet according to the access physical interface.

In the embodiment of the present application, the floating interface component is configured to discard the currently received packet when the floating interface is not found according to the destination MAC address.

In the embodiment of the present application, the floating interface component is configured to query the outbound interface as a physical interface on the network side, and forward the packet to the physical interface on the network side.

In the embodiment of the present application, the accessing the physical interface component is configured to report the access request message to the packet forwarding controller, where the access request packet is used by the packet forwarding controller to determine the access. The physical interface determines the bound floating interface according to the binding relationship between the physical interface and the floating interface, and generates a forwarding table for forwarding the packet.

Receiving an access response message fed back by the packet forwarding controller, where the access response The forwarding table is carried in the packet.

In the embodiment of the present application, the accessing the physical interface component is configured to report the information of the physical interface to the packet forwarding controller; the information of the access physical interface is used to query the physical interface of the BRAS pool. And a floating interface that is not bound to the physical interface;

A packet forwarding controller, the packet forwarding controller is connected to a broadband access server BRAS pool, and the controller includes: a BRAS pool access physical interface management component, a floating interface management component, and a policy control component;

The broadband access server BRAS pool accesses the physical interface management component, and is configured to receive the access physical interface information reported by the physical interface component of the BRAS in the BRAS pool;

A floating interface management component configured to perform floating interface configuration.

a policy control component, configured to query the physical interface management component of the BRAS pool to query an access physical interface of the BRAS pool, and query the floating interface management component for a floating interface that has no binding relationship;

The policy control component is configured to bind the unbound access physical interface to the floating interface, and notify the floating interface management component of the configured binding relationship;

The floating interface management component is configured to record the binding relationship and bind the floating interface of the BRAS to the physical interface. When the floating interface of the BRAS is more than one, select a floating interface as the bound floating interface. And notify the floating interface component of the BRAS that is queried or selected.

In the embodiment of the present application, the controller further includes: an access control component and a forwarding table component; wherein:

An access control component, configured to receive an access request message sent by the access physical interface of the BRAS, and notify the policy control component of the currently accessed physical access interface;

The policy control component is configured to query the floating interface management component to query a floating interface bound to the currently accessed physical interface; when the floating interface of the query exceeds one, select a floating interface, and query or select The floating interface notifies the access control component;

The access control component is configured to notify the forwarding table component to generate a forwarding table, and send an access response packet to the access physical interface of the BRAS, and send the generated forwarding table component of the BRAS in the forwarding table .

In the embodiment of the present application, the policy control component is configured to store an orchestration policy, and when detecting that the first BRAS is unavailable, the user of the first BRAS is migrated to at least one other available BRAS based on the orchestration policy. .

In the embodiment of the present application, the policy control component is configured to detect that the first BRAS cannot be used, and access the physical interface management component of the BRAS pool to query the access physical interface of the first BRAS, and go to the The floating structure management component queries the floating interface bound to the physical interface of the first BRAS, and when the floating interface of the query exceeds one, selects a floating interface as the bound floating interface; and according to the bound floating interface The forwarding table management component queries the forwarding table associated with the first BRAS, and deletes the access physical interface of the first BRAS to the BRAS pool access physical interface management component.

In the embodiment of the present application, the controller further includes a forwarding table management component;

The policy control component is configured to query the BRAS pool access physical interface management component to query the access physical interface of the at least one other available BRAS, and bind the floating interface associated with the first BRAS to the Said access physical interface of at least one other available BRAS;

The floating interface management component is configured to update the binding relationship to a binding relationship between the floating interface of the first BRAS and the access physical interface of the at least one other available BRAS, and update the binding relationship Notifying the floating interface management component of the at least one other available BRAS;

a forwarding table management component configured to forward the updated forwarding table to the at least one other usable BRAS forwarding table management component notification.

In the embodiment of the present application, the scheduling policy includes: selecting the first BRAS to migrate to the second BRAS, or triggering the migration when the migration time expires.

In the embodiment of the present application, the forwarding table component is configured to query the accessing physical interface through the floating interface, and forward the packet according to the access physical interface; and query the outgoing interface as the physical interface on the network side. Forward packets from the physical interface on the network side.

The computer storage medium provided by the embodiment of the present application stores a computer program configured to execute the message forwarding method.

The technical solution of the embodiment of the present invention receives the forwarded packet, and queries the floating interface according to the destination media access control MAC address of the forwarded packet to determine whether the interface is a floating interface; if the outgoing interface is a floating interface, Bind the physical interface to the floating interface to query the access physical interface and forward the packet according to the access physical interface. In this way, in some time periods, there are few online users, and the user can be migrated to some BRASs during the changed time period, and the migrated BRAS is dormant or shut down, saving energy consumption and reducing operation and maintenance costs.

DRAWINGS

1 is a schematic diagram of a packet forwarding system based on a broadband access server according to an embodiment of the present application;

2 is a schematic structural diagram of components in a packet forwarding system based on a broadband access server according to an embodiment of the present application;

FIG. 3 is a schematic diagram of a process of accessing and forwarding BRAS-based packet forwarding according to an embodiment of the present disclosure;

4 is a schematic flowchart of a BRAS-based packet forwarding configuration phase according to an embodiment of the present application;

FIG. 5 is a schematic flowchart of an access phase of a BRAS-based packet forwarding according to an embodiment of the present application;

6 is a schematic flowchart of a BRAS-based packet forwarding phase according to an embodiment of the present application;

FIG. 7 is a schematic diagram of a BRAS-based message forwarding scheduling and management process according to an embodiment of the present application;

FIG. 8 is a schematic flowchart of a BRAS-based packet forwarding unusable user migration according to an embodiment of the present disclosure;

FIG. 9 is a schematic flowchart of manual user migration based on BRAS packet forwarding according to an embodiment of the present disclosure;

10 is a schematic flowchart of time-based user migration of BRAS-based packet forwarding according to an embodiment of the present application;

FIG. 11 is a PPPoE networking diagram of a BRAS-based packet forwarding method according to an embodiment of the present disclosure;

FIG. 12 is a schematic diagram of PPPoE Client access based on BRAS-based packet forwarding according to an embodiment of the present disclosure;

FIG. 13 is a schematic diagram of BRAS-based packet forwarding according to an embodiment of the present application;

FIG. 14 is a schematic diagram of a BRAS-free PPPoE user migration based on BRAS-based packet forwarding according to an embodiment of the present application.

detailed description

The embodiments of the present application are described in detail with reference to the accompanying drawings.

In the embodiment of the present application, a plurality of BRASs are interconnected, and an external packet forwarding controller is used to manage online users through a customized floating interface; the pooled BRAS can load users to different BRASs according to a better load balancing policy; Interfaces can be customized and managed by a variety of policies to load switch, facilitate operation and maintenance, and consume less resources according to load conditions.

As shown in FIG. 1 , the packet forwarding system based on the broadband access server in the embodiment of the present application includes: a packet forwarding controller and a BRAS pool. The BRAS pool consists of multiple BRAS interconnections and access The protocol request message can go to any BRAS in the BRAS pool.

As shown in FIG. 2, in the packet forwarding controller of the packet forwarding system based on the broadband access server and the component structure in the BRAS, the packet forwarding controller includes:

The policy control component, the function of the policy control component includes: accessing the physical interface component of the BRAS pool accessing the packet forwarding controller according to the BRAS pool and the specific BRAS query; and querying the floating interface management component of the packet forwarding controller The floating interface is bound to the physical interface. The floating interface management component of the packet forwarding controller queries the floating interface according to the physical interface of the BRAS. The physical interface is bound to the floating interface. The interface management component adds the binding relationship between the floating interface and the access physical interface. The floating interface management component of the packet forwarding controller notifies the binding relationship between the floating interface and the access physical interface, and receives the access control of the packet forwarding controller. The user of the component accesses the physical interface notification. The floating interface that is queried according to the access physical interface selects a floating interface to notify the access control component of the packet controller; configures the orchestration policy; triggers the orchestration when the scheduling trigger condition is met; The forwarding table management component of the forwarding controller queries the forwarding table according to the floating interface; The BRAS pool physical access management component of the forwarding controller deletes the access physical interface; the forwarding table management component of the notification packet forwarding controller sends the forwarding table;

The access control component, the function of the access control component includes: receiving an access request message reported by the access physical interface of the BRAS; when the access physical interfaces of the multiple BRASs report the same access request message, selecting one according to the policy Accessing the access request packet of the physical interface; notifying the physical interface of the policy control component of the packet forwarding controller to access and access the user; and receiving the policy control component of the packet forwarding controller to notify the floating associated with the forwarding table The forwarding table management component of the notification packet forwarding control controller generates a forwarding table; generates a request response packet, and sends an access response packet to the physical interface of the BRAS;

The function of the floating interface management component, the floating interface management component includes: configuring a floating interface; providing an interface that is not bound to the access physical interface; providing a query according to the access physical interface An interface that adds a floating interface to an interface that is connected to a physical interface. It provides an interface that updates the floating interface to the physical interface. It provides the function of saving and recording the binding relationship between the floating interface and the physical interface. A floating interface management component that is bound to the BRAS that accesses the physical interface and is sent to the BRAS that accesses the physical interface.

The BRAS pool accesses the physical interface management component. The function of the BRAS pool to access the physical interface management component includes: receiving the physical interface of the BRAS reporting access and saving; providing an interface for querying the BRAS pool to access the physical interface; and providing the access physical of the query BRAS Interface of the interface; provides an interface for deleting the physical interface of the BRAS;

The forwarding table management component, the function of the forwarding table management component includes: providing an interface for generating a forwarding table; delivering a forwarding table to a forwarding table management component of the BRAS, wherein the BRAS is an accessing physical entity bound to the floating interface in the forwarding table The BRAS of the interface; provides an interface for querying the forwarding table according to the floating interface; and receiving the notification of the BRAS sent by the packet forwarding controller;

BRAS includes:

The function of the floating interface component, the floating interface component includes: receiving a floating interface associated with the access physical interface of the BRAS delivered by the floating interface management component of the packet forwarding controller, and saving the component; receiving the forwarding of the physical interface component notification of the BRAS Packets are searched for the floating interface based on the MAC address. The floating interface discards the packet. The packet is forwarded by the BRAS forwarding table. The packet is forwarded to the floating interface. The physical interface sends the packet to the discovered access physical interface.

The function of accessing the physical interface component and accessing the physical interface component includes: reporting the access physical interface of the BRAS to the BRAS pool of the packet forwarding controller to access the physical interface management component; and receiving the access request packet to report the packet forwarding The access control component of the controller receives the access response packet sent by the access control component of the packet forwarding controller, and sends the access response packet to the user; receives the forwarded packet, and sends the forwarded packet The floating interface management component of the BRAS; receiving the forwarding packet sent by the floating interface component of the BRAS, and forwarding the packet to the user;

The function of the forwarding table component, the forwarding table component includes: receiving a forwarding table delivered by the forwarding table management component of the packet forwarding controller, and saving the component in the component; adding the forwarding table, issuing the user route; receiving the floating interface management component of the BRAS The forwarded packet is sent, and the forwarding packet is forwarded to the forwarding table for forwarding. The outbound interface is sent to the floating interface management component of the BRAS. The outgoing interface is the network-side interface and is forwarded to the network-side interface for forwarding.

The packet forwarding system based on the broadband access server of the embodiment of the present invention can complete the basic functions of user access packet forwarding and perform management according to different policies.

As shown in Figure 3, basic access and forwarding functions include: system configuration, access, and packet forwarding.

301. System configuration: The physical interface is reported to the packet forwarding controller; the floating interface and its interface attributes are configured; and the physical interface is bound to the floating interface.

302: Access: the access protocol request message in the BRAS pool is sent to the packet forwarding controller by multiple BRAS packets; the packet forwarding controller completes the selection of the physical interface and selects the floating interface; and completes the access processing; The forwarding table is generated, and the interface associated with the forwarding table is the selected floating interface.

303. Packet forwarding: The physical interface receives the packet and sends the packet to the associated floating interface. The floating interface checks the packet and discards the illegal packet. The query forwarding table forwards the packet according to the outgoing interface. If the outgoing interface is a floating interface. Sends a packet from the physical interface associated with the floating interface. If the outbound interface is a network-side interface, the packet is sent directly from the network-side interface.

As shown in FIG. 4, the BRAS-based packet forwarding configuration process in this embodiment of the present application includes the following steps:

Step 4001: The physical interface component of the BRAS1 in the BRAS pool reports the physical interface to the BRAS pool access physical interface management component of the packet forwarding controller, and the reported information includes but is not limited to: interface name, interface MAC address, interface status, and rate. Wait. The physical interface information can be accessed through the SNMP protocol, the NETCONF protocol, or the protocol including OPENFLOW and RADIUS.

Step 4002: The physical interface component of the BRAS2 in the BRAS pool reports the physical interface to the BRAS pool access physical interface management component of the packet forwarding controller, and the reported information includes but is not limited to: interface name, interface MAC address, interface status, and rate. Wait.

Step 4003: The floating interface management component of the packet forwarding controller completes configuring the floating interface, and the configuration information includes an interface name, a description, a MAC address, a gateway IP address, and the like. Configure multiple floating interfaces, which can be configured one by one or a configuration template. A template can dynamically generate floating interfaces.

Step 4004: The policy control component of the message forwarding controller accesses the BRAS pool to access the physical interface management component to query the BRAS pool to access the physical interface.

Step 4005: The BRAS pool access physical interface management component of the packet forwarding controller returns a BRAS pool access physical interface to the policy control component.

Step 4006: The policy control component of the packet forwarding controller queries the floating interface management component to query the floating interface that is not bound to the access physical interface.

Step 4007: The floating interface management component of the packet forwarding controller returns a floating interface that is not bound to the access physical interface to the policy control component.

Step 4008: The policy control component of the packet forwarding controller completes the configuration of the physical interface to be bound to the floating interface, and one physical interface can be bound to multiple floating interfaces. The configuration can be manually bound to the physical interface.

Step 4009: The policy control component of the packet forwarding controller notifies the configured binding relationship to the floating interface management component.

Step 4010: The floating interface management component of the packet forwarding controller records the binding relationship between the physical interface and the physical interface.

Step 4011: The floating interface management component of the packet forwarding controller notifies the floating interface component of the BRAS1 to the floating interface component of the BRAS1, and the floating interface component of the BRAS1 records the relationship with the physical interface. The notification interface can be implemented through a network management interface such as SNMP or Netconf, or by extending the RADIUS or Openflow protocol.

Step 4012: The floating interface management component of the packet forwarding controller notifies the floating interface component of the BRAS2 to the floating interface component of the BRAS2, and the floating interface component of the BRAS2 records the relationship with the physical interface.

FIG. 5 is a schematic flowchart of a BRAS-based packet forwarding access process according to an embodiment of the present disclosure. As shown in FIG. 5, the BRAS-based packet forwarding access procedure in the embodiment of the present application includes the following steps:

Step 5001: The access physical interface of the BRAS1 of the BRAS pool receives the access request packet, and reports the access request packet to the access control component of the packet forwarding controller. The reported protocol may use the packet in message of OPENFLOW, or may use the GRE tunnel encapsulation or VxLAN tunnel encapsulation of the access request message.

Step 5002: The physical interface of the BRAS2 accessing the BRAS2 receives the access request packet, and reports the access request packet to the access control component of the packet forwarding controller. The reported protocol may use the packet in message of OPENFLOW, or may use the GRE tunnel encapsulation or VxLAN tunnel encapsulation of the access request message.

Step 5003: The access control component of the packet forwarding controller selects the access physical interface of the BRAS1 to perform access processing according to a certain policy. The policies include, but are not limited to, first-come, first-served, minimum number of users, maximum remaining memory, minimum CPU utilization, and the like.

Step 5004: The access control component of the packet forwarding controller notifies the physical access interface accessed by the policy control component user;

Step 5005: The policy control component of the packet forwarding controller queries the bound floating interface according to the access physical interface to the floating interface management component.

Step 5006: The floating interface management component of the packet forwarding controller queries the bound floating interface according to the access physical interface. If the floating interface is one, the floating interface is returned to the policy control; if the floating interface is multiple, The floating interface is selected according to the policy, and the policy includes not limited to the number of users on the floating interface.

Step 5007: The access control component of the packet forwarding controller notifies the forwarding table component to generate a forwarding table, where the forwarding table includes: a user table and a user route. And the user accessing the physical interface and the floating interface used by the user is added.

Step 5008: The access control component of the packet forwarding controller sends an access response message to the selected physical interface of the selected BRAS1, and the sending protocol may use the packet out message of OPENFLOW, or may use the access response message to perform GRE. Tunnel encapsulation or VxLAN tunnel encapsulation. The access physical interface receives the access response packet and decapsulates it, and then sends the packet to the access terminal.

Step 5009: The forwarding table component of the packet forwarding controller sends the generated user forwarding table to the forwarding table component of the BRAS1.

Step 5010: The forwarding table component of the BRAS1 saves the delivered forwarding table. The forwarding table includes a user table and a user routing table, and advertises the user-side route to the network side to ensure that the packet to the access user reaches the BRAS1 through the route.

In the above process, the access control component of the packet forwarding controller selects a specific BRAS to perform online access according to the policy as described above, so that load sharing is optimal.

FIG. 6 is a schematic flowchart of a BRAS-based packet forwarding process according to an embodiment of the present disclosure. As shown in FIG. 6 , the BRAS-based packet forwarding process in the embodiment of the present application includes the following steps:

Step 6001: The access physical interface of the BRAS1 receives the forwarded packet.

Step 6002: Send the floating interface component to the BRAS1, and query the floating interface according to the physical interface;

Step 6003: Query the floating interface according to the destination MAC address, and the query does not discard, otherwise the next step is to process. The user table is sent to perform BRAS service processing. After the processing is completed, the second layer header is stripped and the routing table is queried.

Step 6004: Query the routing table, and obtain the outbound interface as a floating interface.

Step 6005: After the outbound interface is a floating interface, the packet is forwarded through the floating interface.

Step 6006: Querying to access the physical interface through the floating interface, and then accessing the physical interface according to the access Port forwarding message;

Step 6007: After the outbound interface is the physical interface on the network side, the user can directly forward the packet from the physical interface on the network side. After the user goes online successfully and forwards the packet, the BRAS can be scheduled and managed according to the policy.

FIG. 7 is a schematic diagram of a process of scheduling and managing BRAS-based packet forwarding according to an embodiment of the present disclosure. As shown in FIG. 7, the scheduling and management process of the embodiment of the present application includes the following steps:

The orchestration policy configuration is completed first, and multiple policies can be configured, including but not limited to BRAS unavailable migration, manual migration, and time migration. Each policy is configured with a trigger point and a migration process. The migration is triggered when the trigger point is met, and the migration is processed according to the configured migration process. Orchestration policy configuration: Support multiple policies, including but not limited to BRAS unavailable migration, manual migration, time migration, and so on. Orchestration policy trigger: triggers the orchestration strategy according to the configured policy trigger point. Execution orchestration: Arrange and process according to the specific orchestration strategy.

FIG. 8 is a schematic flowchart of BRAS unusable user migration based on BRAS-based packet forwarding according to an embodiment of the present invention. As shown in FIG. 8, the scheduling policy is a BRAS unavailable migration process, including the following steps:

Step 8001: Configure an orchestration policy on the policy control component of the packet forwarding controller, and the BRAS is unavailable for migration. When detecting that a certain BRAS is unavailable, the user of the BRAS is migrated to another available BRAS, and can be migrated to a BRAS. It can also be migrated to multiple BRASs, which must be in a BRAS pool. The example describes migration to only one BRAS. The detection mechanism can be through SNMP, Netconf, Openflow and other protocols.

Step 8002: When the policy control component of the message forwarding controller detects that BRAS1 is unavailable, triggering the BRAS to be unavailable to migrate the user.

Step 8003: The policy control component of the packet forwarding controller accesses the physical interface management component of the BRAS pool to query the access physical interface of the BRAS1.

Step 8004: The policy control component of the message forwarding controller is connected according to the queried BRAS1. Enter the physical interface to the floating structure management component to query the floating interface bound to the physical interface of BRAS1. When more than one floating interface is queried, select a floating interface as the bound floating interface.

Step 8005: The policy control component of the packet forwarding controller queries the forwarding table associated with the BRAS1 according to the floating interface bound to the physical interface of the accessed BRAS1 to the forwarding table management component.

Step 8006: The BRAS1 is unavailable, and the policy control component of the packet forwarding controller accesses the physical interface management component of the BRAS pool to delete the access physical interface of the BRAS1.

Step 8007: The policy control component of the packet forwarding controller accesses the physical interface management component of the BRAS pool to query the access physical interface of the BRAS2.

Step 8008: The policy control component of the packet forwarding controller binds the floating interface associated with the BRAS1 to the access physical interface of the BRAS2.

Step 8009: The policy control component of the packet forwarding controller notifies the physical interface of the BRAS2 accessing the floating interface management component, and the floating interface management component updates the binding relationship between the floating interface and the physical interface, and accesses the physical interface of the BRAS1. The bound floating interface updates the interface physical interface bound to BRAS2.

Step 8010: The floating interface management component of the packet forwarding controller notifies the floating interface management component of the updated floating interface and the access physical interface to the floating interface management component of the BRAS2, and the floating interface management component of the BRAS2 records the binding relationship. The notification interface can be implemented through a network management interface such as SNMP or Netconf, or by extending the RADIUS or Openflow protocol.

Step 8011: The policy control component of the packet forwarding controller notifies the forwarding table management component, and notifies the BRAS2 of the user table associated with the floating interface that updates the binding relationship;

Step 8012: The forwarding table management component of the packet forwarding controller sends the forwarding table notification to the forwarding table management component of the BRAS2. The interface can be implemented through SNMP, Netconf, and other network management interfaces, or by extending RADIUS or Openflow protocols.

Step 8013: The forwarding table management component of the BRAS2 receives the forwarding table and saves it locally. The forwarding table includes the user table and the user route, and the BRAS2 network side advertises the user route.

According to the above process, the BRAS unavailable user can be switched to other BRASs according to the method as described above, and the high availability of the user is ensured.

As shown in FIG. 9, the process of the manual migration policy in the embodiment of the present application includes the following steps:

Step 9001: Configure an orchestration policy on the policy control component of the packet forwarding controller, and configure the policy as manual migration.

Step 9002: When the user migration is manually triggered, and the user selecting BRAS1 is migrated to BRAS2.

Step 9003: The policy control component of the packet forwarding controller accesses the physical interface management component of the BRAS pool to query the access physical interface of the BRAS1.

Step 9004: The policy control component of the packet forwarding controller queries the floating interface of the access physical interface bound to the BRAS1 according to the queried access physical interface of the BRAS1 to the floating structure management component. When more than one floating interface is queried, select a floating interface as the bound floating interface.

Step 9005: The policy control component of the packet forwarding controller queries the forwarding table associated with the BRAS1 according to the floating interface bound to the physical interface of the accessed BRAS1 to the forwarding table management component.

Step 9006: The policy control component of the packet forwarding controller sends a forwarding table to the forwarding table management component of the BRAS1;

Step 9007: The forwarding table management component of the BRAS1 reclaims the forwarding table and revokes the user route.

Step 9008: The policy control component of the packet forwarding controller reclaims the floating interface to the floating interface management component of the BRAS1;

Step 9009: The policy control component of the packet forwarding controller accesses the physical interface management component of the BRAS pool to query the access physical interface of the BRAS2.

Step 9010: The policy control component of the packet forwarding controller binds the floating interface associated with the BRAS1 to the access physical interface of the BRAS2.

Step 9011: The policy control component of the packet forwarding controller notifies the floating interface management component of the BRAS2 access physical interface corresponding to the floating interface, and the floating interface management component updates the floating interface and The binding relationship of the physical interface binds the floating interface update bound to the physical interface of BRAS1 to the physical interface of the interface of BRAS2.

Step 9012: The floating interface management component of the packet forwarding controller notifies the floating interface management component of the updated floating interface and the access physical interface to the floating interface management component of the BRAS2, and the floating interface management component of the BRAS2 records the binding relationship. The notification interface can be implemented through a network management interface such as SNMP or Netconf, or by extending the RADIUS or Openflow protocol.

Step 9013: The policy control component of the packet forwarding controller notifies the forwarding table management component, and notifies the BRAS2 of the user table associated with the floating interface that updates the binding relationship;

Step 9014: The forwarding table management component of the packet forwarding controller sends the forwarding table notification to the forwarding table management component of the BRAS 2. The interface can be implemented through SNMP, Netconf, and other network management interfaces, or by extending RADIUS or Openflow protocols.

Step 9015: The forwarding table management component of the BRAS2 receives the forwarding table and saves it locally, the forwarding table includes the user table and the user route, and the BRAS2 network side advertises the user route.

Due to the needs of operation and maintenance, such as operations on the BRAS such as updating hardware and software, locating faults, etc., according to the above procedure, the packet forwarding controller can manually switch the user to other BRAS according to the above method, thereby ensuring the user. Do not drop.

As shown in Figure 10, the orchestration strategy is defined as a time-migrated process that includes the following steps:

Step 10001: Configure an orchestration policy on the policy control component of the packet forwarding controller, configure the policy to migrate by time, and select the user of BRAS2 to migrate to BRAS1.

Step 10002: User migration is triggered when the set time expires.

Step 10003: The policy control component of the message forwarding controller accesses the physical interface management component of the BRAS pool to query the access physical interface of the BRAS2.

Step 10004: The policy control component of the packet forwarding controller queries the floating interface of the access physical interface bound to the BRAS2 according to the queried access physical interface of the BRAS2 to the floating structure management component. When the floating interface of the query exceeds one, select a floating interface as the bound floating interface. mouth.

Step 10005: The policy control component of the packet forwarding controller queries the forwarding table associated with the BRAS2 according to the floating interface bound to the physical interface of the accessed BRAS2 to the forwarding table management component.

Step 10006: The policy control component of the packet forwarding controller sends a forwarding table to the forwarding table management component of the BRAS2;

Step 10007: The forwarding table management component of the BRAS2 reclaims the forwarding table and then revokes the user route.

Step 10008: The policy control component of the packet forwarding controller reclaims the floating interface to the floating interface management component of the BRAS2;

Step 10009: The policy control component of the packet forwarding controller accesses the physical interface management component of the BRAS pool to query the access physical interface of the BRAS1.

Step 10010: The policy control component of the packet forwarding controller binds the floating interface associated with the BRAS2 to the access physical interface of the BRAS1.

Step 10011: The policy control component of the packet forwarding controller notifies the physical interface of the BRAS1 accessing the floating interface management component, and the floating interface management component updates the binding relationship between the floating interface and the physical interface, and accesses the physical interface of the BRAS2. The bound floating interface updates the interface physical interface bound to BRAS1.

Step 10012: The floating interface management component of the packet forwarding controller notifies the floating interface management component of the updated floating interface and the access physical interface to the floating interface management component of the BRAS1, and the floating interface management component of the BRAS1 records the binding relationship. The notification interface can be implemented through a network management interface such as SNMP or Netconf, or by extending the RADIUS or Openflow protocol.

Step 10013: The policy control component of the packet forwarding controller notifies the forwarding table management component, and notifies the BRAS1 of the user table associated with the floating interface that updates the binding relationship;

Step 10014: The forwarding table management component of the packet forwarding controller sends the forwarding table notification to the forwarding table management component of the BRAS1. Knowing interfaces can pass SNMP, Netconf and other network management interfaces. It can also be implemented by extending the RADIUS or Openflow protocol.

Step 10015: The forwarding table management component of the BRAS1 receives the forwarding table and saves it locally. The forwarding table includes the user table and the user route, and the BRAS1 network side advertises the user route.

According to the above process, the number of online users is small during certain time periods, and the user can be migrated to some BRASs during the changed time period to sleep or shut down the migrated BRAS, thereby saving energy consumption and reducing operation and maintenance costs.

Figure 11 is a network diagram of PPPoE user access deployment. As shown in Figure 11, two PPPoE clients Client1 and Client2 access the BRAS pool through the access network. The BRAS pool contains three BRASs. The BRAS is located on the boundary of the metropolitan area network. The packet forwarding controller establishes a connection between the packet forwarding controller and the BRAS pool in the metropolitan area network data center, and manages packet forwarding in the BRAS pool.

As shown in Figure 12, the PPPoE client access process includes the following steps:

Step 12001: The packet forwarding controller configures the MAC address of the floating interface and its floating interface: float1, Fa:16:3e:66:cf:65;float2, Fa:16:3e:66:cf:66;float3,Fa: 16:3e: 66: cf: 67;

Step 12002: The BRAS1 reports the access to the physical interface access-interface1 to the packet forwarding controller.

Step 12003: The BRAS2 reports the access to the physical interface access-interface2 to the packet forwarding controller.

Step 12004: The BRAS3 reports the access to the physical interface access-interface3 to the packet forwarding controller.

Step 12005: The packet forwarding controller establishes the binding relationship between the physical interface and the floating interface: access-interface1 is bound to float1, access-interface2 is bound to float2, and access-interface3 is bound to float3.

Step 12006: Deliver floating1 floating structure information to BRAS1, and BRAS1 saves float1 information.

Step 12007: Deliver float2 floating structure information to BRAS2, BRAS2 saves float2 information;

Step 12008: The floating structure information of the float3 is sent to the BRAS3, and the BRAS3 saves the float3 information.

Step 12009: The PPPoE client1 sends the first packet PADI packet of the PPPoE to the BRAS1.

Step 12010: The BRAS1 reports the PADI packet to the packet forwarding controller.

Step 12011: The PPPoE client1 sends the first packet PADI packet of the PPPoE to the BRAS2.

Step 12012: The BRAS2 reports the PADI message to the message forwarding controller.

Step 12013: PPPoE Client1 sends the first packet PADI packet of PPPoE to BRAS3.

Step 12014: The BRAS3 reports the PADI message to the message forwarding controller.

Step 12015: The packet forwarding controller selects acess-interface1 of BRAS1 as the access physical interface.

Step 12016: The subsequent PPPoE protocol exchanges, and the access physical interface of the protocol packet is the access-interface1 of the BRAS1 selected by the packet forwarding controller. The PPPoE protocol interaction is a process defined by the standard protocol and will not be described here.

Step 12017: After the access protocol is authenticated, the forwarding table is generated. The floating interface of the forwarding table is the access-interface1 bound to float1. The PPPoE client access is complete, and the saved MAC address of the PPPoE session is the MAC address of the float1.

Step 12018: The packet forwarding controller sends the forwarding table of the PPPoE client1 user to the BRAS1, and the BRAS1 saves the forwarding table.

Step 12019: After receiving the forwarding table, the BRAS1 advertises the PPPoE client1 user route to the network side.

Step 12020: The PPPoE client 2 completes the access, and the access-interface 2 of the BRAS 2 is selected as the physical interface. The process is the same as that of PPPoE Client1 and is not mentioned here.

Step 12021: The physical interface of the packet forwarding controller selected by the PPPoE client 2 is access-interface 2, and the floating interface of the generated forwarding table is float2.

Step 12022: The packet forwarding controller sends the forwarding table of the PPPoE client2 user to the BRAS2, and the BRAS2 saves the forwarding table.

Step 12023: After receiving the forwarding table, the BRAS2 advertises the PPPoE client2 user route to the network side.

As shown in FIG. 13, the PPPoE client packet forwarding process in the embodiment of the present application includes the following steps:

Step 13001: The PPPoE client sends a forwarding packet, and the destination MAC address is the MAC address of the floating interface of the float1.

Step 13002: The physical interface access-interface1 of the BRAS1 receives the packet, queries the floating interface according to the destination MAC address, and finds that the floating interface is float1; searches the forwarding table and finds the outgoing interface to forward the packet;

Step 13003: The access physical interface of the BRAS2 also receives the forwarded packet sent by the PPPoE.

Step 13004: The floating interface is searched according to the destination MAC address on the BRAS2, and the floating interface is not queried, and the forwarding packet is discarded.

Step 13005: The PPPoE client2 sends a packet with the same PPPoE client2. The destination MAC address of the packet is the MAC address of the float2, so it is forwarded through the BRAS2.

As shown in FIG. 14, the BRAS1 unavailable user migration process in the embodiment of the present application includes the following steps:

Step 14001: The packet forwarding controller sets the migration policy to BRAS unavailable for migration.

Step 14002: The message forwarding controller detects that BRAS1 is unavailable, triggering the migration. Migrate BRAS1 users to BRAS3

Step 14003: Modify the floating interface of the forwarding table on BRAS1 to float3.

Step 14004: The message forwarding controller sends the forwarding table of the original BRAS1 to the BRAS3, and the BRAS3 saves the forwarding table.

Step 14005: After receiving the forwarding table, the BRAS3 issues a user route to the network side. Subsequent forwarding packets to the original BRAS1 are subsequently forwarded through BRAS3.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, such as: multiple units or components may be combined, or Can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, or direct coupling, or communication connection of the components shown or discussed may be indirect coupling or communication connection through some interfaces, devices or units, and may be electrical, mechanical or other forms. of.

The units described above as separate components may or may not be physically separated, and the components displayed as the unit may or may not be physical units, that is, may be located in one place or 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.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may be separately used as one unit, or two or more units may be integrated into one unit; the above integration The unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by using hardware related to the program instructions. The foregoing program may be stored in a computer readable storage medium, and the program is executed when executed. The foregoing steps include the steps of the foregoing method embodiments; and the foregoing storage medium includes: a removable storage device, a read only memory (ROM), a magnetic disk, or an optical disk, and the like, which can store program codes.

Alternatively, the above integrated unit of the present application is implemented in the form of a software functional module and Separate products can also be stored on a computer readable storage medium when sold or used. Based on such understanding, the technical solution of the embodiments of the present application may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium, including a plurality of instructions. A computer device (which may be a personal computer, server, or network device, etc.) is caused to perform all or part of the methods described in various embodiments of the present application. The foregoing storage medium includes: a removable storage device, a read only memory (ROM), a magnetic disk, or an optical disk, and the like, which can store program codes.

Correspondingly, the embodiment of the present application further provides a computer storage medium, where a computer program is configured, and the computer program is configured to execute the message forwarding method in the embodiment of the present application.

The foregoing is only a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present application. It should be covered by the scope of protection of this application. Therefore, the scope of protection of the present application should be determined by the scope of the claims.

Industrial applicability

Claims

A packet forwarding method, the method comprising:

Receiving and forwarding packets;

Query the floating interface based on the destination MAC address of the forwarding packet to determine whether the interface is a floating interface.

When the outbound interface is a floating interface, the access physical interface is queried according to the binding relationship between the physical interface and the floating interface.

Forwarding the packet according to the access physical interface.
The method of claim 1 wherein the method further comprises:

When the floating interface is not found based on the destination MAC address, the currently received packet is discarded.
The method of claim 1 wherein the method further comprises:

The outbound interface is the physical interface on the network side and forwards packets directly from the physical interface on the network side.
The method of claim 1 wherein said method comprises:

And reporting the access request message to the packet forwarding controller, where the access request message is used by the packet forwarding controller to determine the access physical interface, and according to the binding of the access physical interface and the floating interface The relationship determines the bound floating interface, and generates a forwarding table for forwarding the packet.

And receiving, by the packet forwarding controller, an access response packet, where the access response packet carries the forwarding table.
The method of claim 1 wherein said method comprises:

And reporting, by the packet forwarding controller, information about accessing the physical interface;

The information of the access physical interface is used to query the physical interface of the BRAS pool and the floating interface of the unbound physical interface;

Receiving a binding relationship between the access physical interface and the floating interface that is fed back by the packet forwarding controller after the binding physical interface is bound to the floating interface.
A packet forwarding method, the method comprising:

Receiving the access request message sent by the BRAS in the BRAS pool of the broadband access server, selecting the access physical interface and selecting the floating interface, completing the BRAS access, and generating a forwarding table, where the interface associated with the forwarding table is The selected floating interface.
The method of claim 6 wherein said method comprises:

Receiving the physical interface information of the access report reported by the BRAS in the BRAS pool, and configuring the floating interface;

Query the physical interface of the BRAS pool and query the floating interface that has no binding relationship.

Configure the unbound physical interface to be bound to the floating interface and record the binding relationship.
The method of claim 7 wherein said method comprises:

Receiving an access request message sent by the access physical interface of the BRAS, and querying a floating interface that is bound to the currently accessed physical interface; when the number of floating interfaces is more than one, a floating interface is selected;

Generating a forwarding table, and sending an access response message to the BRAS, where the access response packet carries the forwarding table.
The method of claim 7 or 8, wherein the method further comprises:

When it is detected that the first BRAS is unavailable, the user of the first BRAS is migrated to at least one other available BRAS based on a pre-configured orchestration policy.
The method of claim 9 wherein said detecting that said first BRAS is unusable comprises:

When it is detected that the first BRAS is unavailable, the physical interface of the first BRAS is determined, and the floating interface bound to the physical interface of the first BRAS is queried, and when the floating interface of the query is more than one, one is selected. The floating interface is configured as a binding floating interface; and the forwarding table associated with the first BRAS is queried according to the bound floating interface, and the access physical interface of the first BRAS is deleted.
The method of claim 9 wherein said migrating a user of said first BRAS to at least one other usable BRAS comprises:

Querying an access physical interface of the at least one other available BRAS, and binding the floating interface associated with the first BRAS to the access physical interface of the at least one other available BRAS;

Updating the binding relationship to a binding relationship between the floating interface of the first BRAS and the access physical interface of the at least one other available BRAS, and updating the binding relationship to the at least one other available BRAS notice;

The updated forwarding table is notified to the at least one other available BRAS.
The method of claim 9, wherein the orchestration policy migrates a user of the first BRAS to at least one other available BRAS when the selected first BRAS is migrated to the second BRAS, include:

Querying the access physical interface of the first BRAS, querying the floating interface bound to the physical interface of the first BRAS, and selecting a floating interface as the bound floating interface when the floating interface is more than one; The bound floating interface queries the forwarding table associated with the first BRAS, and reclaims the forwarding table and the floating interface.

Querying the access physical interface of the second BRAS, and binding the floating interface associated with the first BRAS to the access physical interface of the second BRAS;

Updating a binding relationship between the first BRAS floating interface and a physical interface of the second BRAS, and notifying the binding relationship to the second BRAS, and notifying the updated forwarding table to the second BRAS.
The method according to claim 9, wherein, when the orchestration policy is time-migrated, the migrating the user of the first BRAS to at least one other available BRAS comprises:

When the migration time expires, the access physical interface of the first BRAS is queried. Querying the floating interface bound to the physical interface of the first BRAS, and selecting a floating interface as the bound floating interface when the floating interface is more than one, and querying the first BRAS based on the bound floating interface. Correlating the forwarding table, and notifying the first BRAS to recycle the forwarding table and the floating interface;

Querying the access physical interface of the second BRAS, and binding the floating interface associated with the first BRAS to the access physical interface of the second BRAS;

Updating a binding relationship between the first BRAS floating interface and the physical interface of the second BRAS, and notifying the binding relationship and the updated forwarding table to the second BRAS.
A broadband access server, the server comprising:

The floating interface component is configured to receive the forwarded packet; the media interface access control MAC address is used to query the floating interface according to the destination of the forwarded packet, and the interface is determined to be a floating interface; if the outgoing interface is a floating interface, the triggering is performed. Access physical interface components;

The physical interface component is configured to forward the packet according to the access physical interface.
The broadband access server of claim 14, wherein the floating interface component is configured to discard the currently received packet when the floating interface is not found according to the destination MAC address.
The broadband access server according to claim 14, wherein the floating interface component is configured to query the outgoing interface as a network side physical interface, and forward the packet to the network side physical interface.
The broadband access server according to claim 14, wherein the access physical interface component is configured to report an access request message to the packet forwarding controller, wherein the access request message is used for the The packet forwarding controller determines to access the physical interface, and determines the bound floating interface according to the binding relationship between the physical interface and the floating interface, and generates a forwarding table for forwarding the packet.

Receiving an access response message fed back by the packet forwarding controller, where the access ringing The forwarding table is carried in the message.
The broadband access server according to claim 14, wherein the access physical interface component is configured to report information of the access physical interface to the packet forwarding controller; the information of the access physical interface is used for Query the physical interface of the BRAS pool and the floating interface of the unbound physical interface;

Receiving a binding relationship between the access physical interface and the floating interface that is fed back by the packet forwarding controller after the binding physical interface is bound to the floating interface.
A packet forwarding controller, the packet forwarding controller is connected to a broadband access server BRAS pool, and the controller includes: a BRAS pool access physical interface management component, a floating interface management component, and a policy control component;

The broadband access server BRAS pool accesses the physical interface management component, and is configured to receive the access physical interface information reported by the physical interface component of the BRAS in the BRAS pool;

A floating interface management component configured to perform floating interface configuration.

a policy control component, configured to query the physical interface management component of the BRAS pool to query an access physical interface of the BRAS pool, and query the floating interface management component for a floating interface that has no binding relationship;

The policy control component is configured to bind the unbound access physical interface to the floating interface, and notify the floating interface management component of the configured binding relationship;

The floating interface management component is configured to record the binding relationship and bind the floating interface of the BRAS to the physical interface. When the floating interface of the BRAS is more than one, select a floating interface as the bound floating interface. And notify the floating interface component of the BRAS that is queried or selected.
The controller of claim 19, wherein the controller further comprises: an access control component and a forwarding table component; wherein:

An access control component configured to receive an access sent by the access physical interface of the BRAS Requesting a message, notifying the policy control component of the currently accessed physical access interface;

The policy control component is configured to query the floating interface management component to query a floating interface bound to the currently accessed physical interface; when the floating interface of the query exceeds one, select a floating interface, and query or select The floating interface notifies the access control component;

The access control component is configured to notify the forwarding table component to generate a forwarding table, and send an access response packet to the access physical interface of the BRAS, and send the generated forwarding table component of the BRAS in the forwarding table .
A controller according to claim 19 or 20, wherein

The policy control component is configured to store an orchestration policy, and when detecting that the first BRAS is unavailable, the user of the first BRAS is migrated to at least one other available BRAS based on the orchestration policy.
The controller of claim 21, wherein the policy control component is configured to detect that the first BRAS is unavailable, and to the BRAS pool access physical interface management component to query the access physical of the first BRAS And the floating structure management component queries the floating interface bound to the physical interface of the first BRAS, and when the floating interface exceeds one, selects a floating interface as the bound floating interface; The bound floating interface to the forwarding table management component queries the forwarding table associated with the first BRAS, and deletes the access physical interface of the first BRAS to the BRAS pool access physical interface management component.
The controller of claim 21 wherein said controller further comprises a forwarding table management component;

The policy control component is configured to query the BRAS pool access physical interface management component to query the access physical interface of the at least one other available BRAS, and bind the floating interface associated with the first BRAS to the Said access physical interface of at least one other available BRAS;

The floating interface management component is configured to update a binding relationship to the first BRAS And a binding relationship between the floating interface and the access physical interface of the at least one other available BRAS, and notifying the updated binding relationship to the floating interface management component of the at least one other available BRAS;

The forwarding table management component is configured to notify the updated forwarding table to the forwarding table management component of the at least one other available BRAS.
The controller of claim 21, wherein the orchestration policy comprises: selecting a first BRAS to migrate to a second BRAS, or expiring a migration time to trigger a migration.
The controller according to claim 24, wherein the forwarding table component is configured to query the access physical interface through the floating interface, and forward the packet according to the access physical interface; An interface is a physical interface on the network side and forwards packets from the physical interface on the network side.
A computer storage medium having stored therein computer executable instructions configured to perform the message forwarding method of any one of claims 1 to 5, or any of claims 6 to 13 A message forwarding method as described.