Communication method and apparatus, related device, and storage medium

Abstract

The application discloses a communication method, device, BRAS forwarder, second BRAS controller and storage medium. The method comprises the following steps: the BRAS forwarder receives a first request sent by a first customer preposition device (CPE), wherein the first request is used for requesting to access a network; in the case that a first BRAS controller fails, a second request is sent to a second BRAS controller, wherein the second request is used for requesting to authenticate the first CPE and allocate relevant information for data forwarding of the first CPE, the first BRAS controller is arranged in the cloud, the second BRAS controller and the BRAS forwarder are arranged on one physical device, and the first BRAS controller and the second BRAS controller at least have a control plane function; and first information sent by the second BRAS controller is received, wherein the first information is used for data forwarding of the BRAS forwarder to the first CPE.

Description

Technical Field

[0001] This application relates to the field of network transmission, and more particularly to a communication method, apparatus, related equipment, and storage medium. Background Technology

[0002] A Broadband Remote Access Server (BRAS) is a new type of access gateway for broadband network applications. Located at the edge layer of the backbone network, it enables users to access broadband networks via Internet Protocol (IP) or Asynchronous Transfer Mode (ATM). This facilitates broadband internet access for commercial buildings and residential communities, IP Virtual Private Network (VPN) services based on Internet Protocol Security (IPSec), the construction of enterprise intranets, and support for Internet Service Providers (ISPs) to provide wholesale services to users.

[0003] With the increasing number of broadband users, the development of 4K high-definition and IoT services, BRAS devices need to separate the forwarding plane from the control plane.

[0004] However, in related technologies, during the traffic forwarding process, in a BRAS system architecture where forwarding and control are separated, if the control device of the BRAS device (which can be called the BRAS controller) fails, there is a problem that new users cannot access the network, thus preventing the forwarding of new users' data. Summary of the Invention

[0005] To address the related technical problems, embodiments of this application provide a communication method, apparatus, related devices, and storage medium.

[0006] The technical solution of this application embodiment is implemented as follows:

[0007] This application provides a communication method applied to a BRAS repeater, including:

[0008] Receive a first request sent by a first customer pre-installed equipment (CPE), the first request being used to request network access;

[0009] In the event of a failure of the first BRAS controller, a second request is sent to the second BRAS controller. The second request is used to request authentication of the first CPE and allocation of relevant information for data forwarding of the first CPE. The first BRAS controller is located in the cloud, and the second BRAS controller and the BRAS forwarder are deployed on a physical device. The first BRAS controller and the second BRAS controller have at least control plane functions.

[0010] The system receives first information sent by the second BRAS controller, which is used by the BRAS repeater to forward the data of the first CPE.

[0011] The method in the above scheme further includes:

[0012] When it is determined that the first BRAS controller has failed, second information is synchronized to the second BRAS controller. The second information contains information related to data forwarding of at least one CPE in the local network of the BRAS repeater.

[0013] The method in the above scheme further includes:

[0014] When the first BRAS controller is determined to have returned to normal, a third message is sent to the second BRAS controller, the third message indicating that at least one relevant information for CPE data forwarding of the local access network of the second BRAS controller is synchronized to the first BRAS controller.

[0015] The method in the above scheme further includes:

[0016] A fourth piece of information is provided, which indicates that the BRAS controller communicating with the BRAS repeater includes the first BRAS controller.

[0017] In the above scheme, the first information is used by the BRAS forwarder to forward data of multiple CPEs containing the first CPE.

[0018] The method in the above scheme further includes:

[0019] When it is determined that the first BRAS controller has failed, a connection is established with the second BRAS controller;

[0020] And / or,

[0021] Once the first BRAS controller is determined to be back to normal, disconnect the connection with the second BRAS controller.

[0022] The method in the above scheme further includes:

[0023] After the connection with the second BRAS controller is established, fifth information is set, which indicates that the BRAS controller communicating with the BRAS repeater includes the second BRAS controller.

[0024] This application also provides a communication method applied to a second BRAS controller, including:

[0025] The system receives a second request sent by the BRAS repeater after the first BRAS controller fails. The second request is used to request authentication of the first CPE and allocation of relevant information for data forwarding of the first CPE. The first BRAS controller is located in the cloud, and the second BRAS controller and the BRAS repeater are deployed on the same physical device. The first BRAS controller and the second BRAS controller have at least control plane functions.

[0026] The first CPE is authenticated, and after successful authentication, a first message is sent to the BRAS forwarder. The first message is used by the BRAS forwarder to forward the data of the first CPE.

[0027] The method in the above scheme further includes:

[0028] The system receives second information synchronized by the BRAS forwarder after a failure of the first BRAS controller. The second information contains information related to data forwarding from at least one CPE in the local network of the BRAS forwarder.

[0029] The method in the above scheme further includes:

[0030] The system receives a third message sent by the BRAS device repeater after the first BRAS controller returns to normal operation. The third message indicates that the system should synchronize with the first BRAS controller the relevant information for data forwarding of at least one CPE in the local network of the second BRAS controller that is connected to the network.

[0031] Synchronize with the first BRAS controller the relevant information for data forwarding from at least one CPE in the local connected network.

[0032] In the above scheme, the first information is used by the BRAS forwarder to forward data of multiple CPEs containing the first CPE.

[0033] The method in the above scheme further includes:

[0034] In the event of a failure of the first BRAS controller, a connection is established with the BRAS repeater;

[0035] And / or,

[0036] Once the first BRAS controller returns to normal, disconnect the connection with the BRAS repeater.

[0037] This application also provides a communication device, including:

[0038] The first receiving unit is configured to receive a first request sent by the first CPE, the first request being used to request network access.

[0039] The first processing unit is configured to send a second request to the second BRAS controller in the event of a failure of the first BRAS controller. The second request is used to request authentication of the first CPE and allocation of relevant information for data forwarding of the first CPE. The first BRAS controller is located in the cloud, and the second BRAS controller and the BRAS forwarder are deployed on a physical device. The first BRAS controller and the second BRAS controller have at least control plane functions.

[0040] The second receiving unit is used to receive first information sent by the second BRAS controller, the first information being used by the BRAS repeater to forward the data of the first CPE.

[0041] This application also provides a communication device, including:

[0042] The third receiving unit is used to receive a second request sent by the BRAS repeater after the first BRAS controller fails. The second request is used to request authentication of the first CPE and allocation of relevant information for data forwarding of the first CPE. The first BRAS controller is located in the cloud, and the second BRAS controller and the BRAS repeater are deployed on the same physical device. The first BRAS controller and the second BRAS controller have at least control plane functions.

[0043] The second processing unit is used to authenticate the first CPE and send first information to the BRAS forwarder after successful authentication. The first information is used for the BRAS forwarder to forward the data of the first CPE.

[0044] This application also provides a BRAS repeater, including: a first processor and a first communication interface; wherein,

[0045] The first communication interface is used for:

[0046] Receive a first request sent by a first CPE, the first request being used to request network access;

[0047] In the event of a failure of the first BRAS controller, a second request is sent to the second BRAS controller. The second request is used to request authentication of the first CPE and allocation of relevant information for data forwarding of the first CPE. The first BRAS controller is located in the cloud, and the second BRAS controller and the BRAS forwarder are deployed on a physical device. The first BRAS controller and the second BRAS controller have at least control plane functions.

[0048] The system receives first information sent by the second BRAS controller, which is used by the BRAS repeater to forward the data of the first CPE.

[0049] This application also provides a second BRAS controller, including: a second processor and a second communication interface; wherein...

[0050] The second communication interface is used to receive a second request sent by the BRAS repeater after the first BRAS controller fails. The second request is used to request authentication of the first CPE and allocation of relevant information for data forwarding of the first CPE. The first BRAS controller is located in the cloud, and the second BRAS controller and the BRAS repeater are deployed on the same physical device. The first BRAS controller and the second BRAS controller have at least control plane functions.

[0051] The second processor is used to authenticate the first CPE and, upon successful authentication, send first information to the BRAS forwarder through the second communication interface. The first information is used by the BRAS forwarder to forward the data of the first CPE.

[0052] This application also provides a BRAS repeater, including: a first processor and a first memory for storing a computer program capable of running on the processor.

[0053] Wherein, when the first processor is used to run the computer program, it executes the steps of any of the methods on the BRAS transponder side described above.

[0054] This application also provides a second BRAS controller, including: a second processor and a second memory for storing a computer program capable of running on the processor.

[0055] Wherein, when the second processor is used to run the computer program, it executes the steps of any of the methods on the second BRAS controller side described above.

[0056] This application embodiment also provides a storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of any of the methods described above on the BRAS transponder side, or implements the steps of any of the methods described above on the second BRAS controller side.

[0057] The communication method, apparatus, related devices, and storage medium provided in this application embodiment include a BRAS repeater receiving a first request sent by a first CPE, the first request being used to request network access; in the event of a failure of the first BRAS controller, a second request is sent to a second BRAS controller, the second request being used to request authentication of the first CPE and allocation of relevant information for data forwarding of the first CPE; the first BRAS controller is located in the cloud, and the second BRAS controller and the BRAS repeater are deployed on the same physical device, the first BRAS controller and the second BRAS controller having at least control plane functionality; the second BRAS controller authenticates the first CPE and, upon successful authentication, sends first information to the BRAS repeater, the first information being used by the BRAS repeater to forward the data of the first CPE. The solution provided in this application embodiment, under a BRAS system architecture with separation of forwarding and control, when the external BRAS controller deployed in the cloud fails, the built-in BRAS controller deployed on the same device as the BRAS repeater responds to the user's access request, thereby enabling network access and data forwarding for new users. Thus, in the event of a failure of the external BRAS controller, it can ensure successful network access and data forwarding for new users, improving the success rate of network access. Attached Figure Description

[0058] Figure 1 This is a schematic diagram of the data forwarding method in related technologies;

[0059] Figure 2 This is a flowchart illustrating the data forwarding method in the event of a failure of an external BRAS controller in related technologies.

[0060] Figure 3 This is a schematic flowchart of the first communication method according to an embodiment of this application;

[0061] Figure 4 This is a schematic flowchart of the second communication method according to an embodiment of this application;

[0062] Figure 5 This is a schematic diagram illustrating the method for a user to access the network, as used in this application example.

[0063] Figure 6 This is a schematic diagram of the structure of a first type of communication device according to an embodiment of this application;

[0064] Figure 7This is a schematic diagram of the structure of a second type of communication device according to an embodiment of this application;

[0065] Figure 8 This is a schematic diagram of the BRAS repeater structure according to an embodiment of this application;

[0066] Figure 9 This is a schematic diagram of the second BRAS controller structure according to an embodiment of this application;

[0067] Figure 10 This is a schematic diagram of the communication system structure according to an embodiment of this application. Detailed Implementation

[0068] The present application will now be described in further detail with reference to the accompanying drawings and embodiments.

[0069] With the increasing number of broadband users, the development of 4K high-definition and IoT services, BRAS devices, as edge devices and access gateways of IP networks, face challenges such as low equipment utilization, high complexity of operation and maintenance services, and long new service launch cycles. On the other hand, with the gradual maturation of emerging technologies such as Software Defined Networking (SDN), Network Functions Virtualization (NFV), and cloud technology, these technologies can be applied to the transformation of telecommunications networks. For example, traditional network equipment rooms can be transformed into flexible and open network clouds, and traditional network elements can be developed from specialized to general-purpose, thereby achieving an organic combination of Communication Technology (CT) and Internet Technology (IT). For BRAS devices, based on these new technologies, the separation of forwarding and control can be achieved, i.e., a BRAS system with separated forwarding and control (referred to as a forwarding-control separation BRAS system in the following description).

[0070] The basic idea of ​​a control plane-separated BRAS system is to extract the control plane functions from multiple BRAS devices and centrally deploy them in the cloud to form a unified BRAS controller. Simultaneously, the BRAS devices whose control plane functions have been extracted (or stripped away) become BRAS repeaters. In other words, a control plane-separated BRAS system includes a BRAS controller (also called a BRAS-control plane (CP)) and a BRAS repeater (also called a BRAS-user plane (UP)).

[0071] The following uses the Point-to-Point Protocol Over Ethernet (PPPoE) service as an example to describe the traffic processing process in a BRAS system architecture with separate control and traffic handling. Figure 1 As shown, the data processing flow based on PPPoE services includes the following steps:

[0072] Step 101: The CPE sends a PPPoE Active Discovery Initiation (PADI) message to the BRAS repeater through the switch (SW) / optical line terminal (OLT) to locate the BRAS controller in the network.

[0073] Here, before step 101, a communication channel is established between the BRAS repeater and the BRAS controller for information transmission.

[0074] Step 102: After receiving the PADI message, the BRAS repeater forwards the PADI message to multiple BRAS controllers in the network.

[0075] Step 103: For each BRAS controller, after receiving the PADI message, the BRAS controller sends a PPPoE Active Discovery Request (PADO) to the BRAS repeater.

[0076] Step 104: After receiving multiple PADO messages, the BRAS repeater forwards the multiple PADO messages to the CPE via the SW / OLT;

[0077] Here, after receiving multiple PADO messages, the CPE selects one BRAS controller from multiple BRAS controllers in the network based on the PADO messages, and sends a PPPoE Active Discovery Session Confirmation (PADS) to the selected BRAS controller through the BRAS forwarder. Correspondingly, after receiving the PADS, the selected BRAS controller sends a PPPoE Active Discovery Terminate (PADT) to the CPE through the BRAS forwarder to establish a session between the CPE and the BRAS controller. At the same time, the selected BRAS controller will also execute step 105.

[0078] Step 105: The BRAS controller sends a challenge to the BRAS repeater to request authentication of the CPE;

[0079] Step 106: After receiving the request, the BRAS repeater forwards the request to the CPE via the SW / OLT;

[0080] Step 107: After receiving the request, the CPE returns a response to the BRAS forwarder via the SW / OLT;

[0081] The response includes the CPE's identity information, such as its IP address.

[0082] Step 108: After receiving the response, the BRAS transponder will pass the response through to the BRAS controller.

[0083] Step 109: After receiving the response, the BRAS controller sends an access request to the Authentication, Authorization, Accounting (AAA) server based on the response.

[0084] The access request includes the CPE's identity information, such as the device identifier.

[0085] Step 110: After receiving the access request, the AAA server authenticates the CPE based on the access request and returns an access response to the BRAS controller.

[0086] In practical applications, the AAA server searches its local database for identity information that matches the CPE's identity information contained in the access request. If a matching identity information is found, it means that the CPE authentication is successful, and step 111 is executed; if no matching identity information is found, it means that the CPE authentication has failed.

[0087] Step 111: In the scenario where the access response indicates successful authentication, the BRAS controller will send access success (Success) information to the BRAS forwarder.

[0088] Step 112: After receiving the access success information, the BRAS repeater transmits the access success information to the CPE through the SW / OLT;

[0089] Step 113: After receiving the access success information, the CPE sends an IP address request to the BRAS forwarder via the SW / OLT;

[0090] The IP address request is used to request an IP address to be allocated to the CPE.

[0091] Step 114: After receiving the IP address request, the BRAS repeater forwards the IP address request to the BRAS controller.

[0092] Step 115: The BRAS controller receives the IP address request, assigns the corresponding IP address to the CPE based on the IP address request, and then sends the IP address assignment information to the BRAS forwarder.

[0093] The IP address assignment information includes the assigned IP address.

[0094] Step 116: After receiving the IP address allocation information, the BRAS repeater forwards the IP address allocation information to the CPE through the SW / OLT;

[0095] Step 117: After assigning an IP address, the BRAS controller will also generate a corresponding user entry for the CPE and send the generated user entry to the BRAS forwarder.

[0096] In practical applications, user entry information may include CPE identity information, IP address, Virtual Local Area Network (VLAN) information, or data forwarding policies.

[0097] It should be noted that the execution order of steps 115 and 117 is not important.

[0098] Step 118: After receiving the IP address allocation information, the CPE sends a data forwarding request to the BRAS forwarder based on the allocated IP address, so that the BRAS forwarder can forward the CPE's data according to the user table entry.

[0099] However, regarding the above process, if the BRAS controller malfunctions, such as Figure 2 As shown, for a CPE already connected to the network, the BRAS forwarder can forward the CPE's data based on the user entry information stored on the BRAS forwarder, enabling the CPE to access the network normally. However, for a newly connected CPE, the BRAS controller cannot complete the authentication, IP address allocation, and user entry information generation steps, resulting in the newly connected CPE failing to connect successfully and data not being forwarded.

[0100] It should be noted that this also applies to Ethernet-based Internet Protocol over Ethernet (IPoE) or Layer 2 Tunneling Protocol (L2TP) services. Figure 2 The problem shown.

[0101] Based on this, in various embodiments of this application, the physical device corresponding to the BRAS repeater is functionally expanded, that is, a built-in BRAS controller is deployed on the same physical device, so that when the BRAS controller in the cloud fails, the built-in BRAS controller can respond to the user's access request and realize the user's data forwarding, thereby enabling the user to access the network normally even when the BRAS controller in the cloud fails, thus improving the success rate of network access.

[0102] This application provides a communication method applied to a BRAS repeater, such as... Figure 3 As shown, the method includes:

[0103] Step 301: Receive a first request sent by the first CPE, the first request being used to request network access;

[0104] Step 302: In the event of a failure of the first BRAS controller, a second request is sent to the second BRAS controller. The second request is used to request authentication of the first CPE and allocation of relevant information for data forwarding of the first CPE. The first BRAS controller is located in the cloud, and the second BRAS controller and the BRAS forwarder are deployed on the same physical device. The first BRAS controller and the second BRAS controller have at least control plane functions.

[0105] Step 303: Receive first information sent by the second BRAS controller, the first information being used by the BRAS repeater to forward the data of the first CPE.

[0106] In practical applications, the BRAS repeater can also be called a BRAS UP. This application embodiment does not limit this terminology, as long as its functionality is achieved. The first BRAS controller can also be called a first BRAS CP, an external BRAS CP, or an external CP, etc. This application embodiment does not limit this terminology, as long as its functionality is achieved. Correspondingly, the second BRAS controller can also be called a second BRAS CP, an internal BRAS CP, or an internal CP, etc. This application embodiment does not limit this terminology, as long as its functionality is achieved.

[0107] In addition, the first CPE can also be called user equipment (UE), or user, etc. This application embodiment does not limit it in this way, as long as its function is implemented.

[0108] In practical applications, in step 301, the first CPE can communicate with the BRAS repeater based on PPPoE, IPoE, or L2TP, corresponding to PPPoE, IPoE, or L2TP services. That is, the solution in this application embodiment is applicable to data processing of PPPoE, IPoE, or L2TP services, and this application embodiment does not limit this. During the communication between the first CPE and the BRAS repeater, the first CPE can send the first request to the BRAS repeater through the access network, specifically through a SW or OLT.

[0109] In practical applications, after receiving the first request, the BRAS repeater needs to communicate with the first BRAS controller to determine whether the first BRAS controller can respond to the first request. To achieve communication with the first BRAS controller, the BRAS repeater establishes a communication connection with it. During this connection establishment process, three types of channels can be established: management channel, control channel, and protocol channel. The method by which the BRAS repeater establishes a communication connection with the first BRAS controller can refer to the process of establishing a connection between the first BRAS controller and the BRAS repeater in related technologies; this application embodiment does not limit this process.

[0110] After establishing a communication connection, the BRAS repeater can determine whether the first BRAS controller has malfunctioned through the established communication connection. For example, if the BRAS repeater sends a first request to the first BRAS controller N times consecutively through the communication connection and receives no response to the first request, it indicates that the first BRAS controller has malfunctioned, where N is an integer greater than or equal to 1, and the value of N can be set as needed, such as 3; otherwise, it indicates that the first BRAS controller has not malfunctioned. This application embodiment does not limit the method for determining whether the first BRAS controller has malfunctioned.

[0111] If the first BRAS controller does not malfunction, the BRAS forwarder will not send the second request to the second BRAS, but will instead send a third request to the first BRAS controller to allocate relevant information for data forwarding to the first CPE through the first BRAS controller, thereby realizing data forwarding to the first CPE; wherein, the relevant information for data forwarding may include forwarding policies and IP addresses, etc.

[0112] In the event of a failure of the first BRAS controller, the BRAS forwarder sends the second request to the second BRAS controller, which temporarily takes over from the first BRAS controller to enable network access and data forwarding for CPEs that need to access the network.

[0113] In practical applications, in order to enable information exchange between the BRAS repeater and the second BRAS controller, the BRAS repeater needs to establish a communication connection with the second BRAS controller.

[0114] Based on this, in one embodiment, the method may further include:

[0115] When a fault is detected in the first BRAS controller, a connection is established with the second BRAS controller.

[0116] When it is determined that the first BRAS controller has returned to normal, in order to save communication resources, the BRAS repeater can disconnect from the second BRAS controller.

[0117] In practical applications, during the process of establishing a connection between the BRAS repeater and the second BRAS controller, three types of channels can be established: management channel, control channel, and protocol channel. The method by which the BRAS repeater establishes a communication connection with the second BRAS controller can refer to the process of establishing a connection between the first BRAS controller and the BRAS repeater in related technologies, and this application embodiment does not limit this.

[0118] In practical applications, in order to facilitate the differentiation of the BRAS controller currently communicating with the BRAS repeater, the BRAS repeater can mark the second BRAS controller before communicating with it.

[0119] Based on this, in one embodiment, the method may further include:

[0120] After the connection with the second BRAS controller is established, fifth information is set, which indicates that the BRAS controller communicating with the BRAS repeater includes the second BRAS controller.

[0121] In practical applications, after it is determined that the first BRAS controller has failed, the BRAS forwarder can synchronize the relevant information of the data forwarding stored locally to the second BRAS controller.

[0122] Based on this, in one embodiment, the method may further include:

[0123] When it is determined that the first BRAS controller has failed, second information is synchronized to the second BRAS controller. The second information contains information related to data forwarding of at least one CPE in the local network of the BRAS repeater.

[0124] Here, after the BRAS forwarder synchronizes the second information to the second BRAS controller, the second BRAS controller can return the first information to the BRAS forwarder so that the BRAS forwarder can use the first information to forward the data of the first CPE; wherein, the first information may include identity information, VLAN information, IP address or data forwarding policy, etc.; the first information may also be called a user entry, which is not limited in this embodiment, as long as its function is implemented.

[0125] In practical applications, during the transmission of the first information, the second BRAS controller can send pre-configured information as the first information to the BRAS forwarder, enabling the BRAS forwarder to forward data from multiple CPEs based on the first information.

[0126] Specifically, in one embodiment, the first information is used by the BRAS forwarder to forward data of a plurality of CPEs containing the first CPE.

[0127] Here, since the second BRAS controller uses pre-configured first information to forward data from multiple CPEs, it does not need to send different first information to the BRAS forwarder for different CPEs. Therefore, the second BRAS controller can achieve the above functions without complex configuration and calculation. In this case, the second BRAS controller can be called a lightweight BRAS controller compared to the first BRAS controller.

[0128] For example, the second BRAS controller can configure the data forwarding policy in the first information according to a preset policy, such as a rate limiting policy. At the same time, the second BRAS controller can also configure the IP address in the first information for the CPE according to a preset address range. In this way, the pre-configuration of the first information is realized so that the BRAS forwarder can forward the data of multiple CPEs containing the first CPE.

[0129] In practical applications, during the period when the first BRAS controller fails, the BRAS repeater can periodically check the first BRAS controller to determine whether the first BRAS controller has returned to normal.

[0130] For example, the BRAS repeater can periodically send test requests to the first BRAS controller based on a preset period. If it receives responses to the test requests sent by the first BRAS controller M times consecutively, it indicates that the first BRAS controller has recovered normally, where M is an integer greater than or equal to 1, and the value of M can be set as needed, such as 4. Otherwise, it indicates that the first BRAS controller has not recovered normally, and the BRAS repeater needs to continue to periodically detect the first BRAS controller. This application embodiment does not limit the method for determining whether the first BRAS controller has recovered normally.

[0131] Here, after the first BRAS controller recovers, the second BRAS controller, which temporarily replaces the first BRAS controller, can stop working. The first BRAS controller then begins communication with the BRAS repeater to enable subsequent CPE network access and data forwarding. In this scenario, the BRAS repeater can disconnect its communication connection with the second BRAS controller to conserve communication resources.

[0132] Here, in order to determine the BRAS controller currently communicating with the BRAS transponder, the BRAS transponder may mark the first BRAS controller before communicating with it.

[0133] Based on this, in one embodiment, the method may further include:

[0134] A fourth piece of information is provided, which indicates that the BRAS controller communicating with the BRAS repeater includes the first BRAS controller.

[0135] In practical applications, after the first BRAS controller recovers to normal, the BRAS repeater can notify the second BRAS controller to synchronize all data forwarding information stored locally to the first BRAS controller, so that the first BRAS controller can subsequently enable network access and data forwarding for CPEs that need to access the network.

[0136] Based on this, in one embodiment, the method may further include:

[0137] When the first BRAS controller is determined to have returned to normal, a third message is sent to the second BRAS controller, the third message indicating that at least one relevant information for CPE data forwarding of the local access network of the second BRAS controller is synchronized to the first BRAS controller.

[0138] Accordingly, embodiments of this application also provide a communication method applied to a second BRAS controller, such as... Figure 4 As shown, the method includes:

[0139] Step 401: Receive a second request sent by the BRAS repeater after the first BRAS controller fails. The second request is used to request authentication of the first CPE and allocation of relevant information for data forwarding of the first CPE. The first BRAS controller is located in the cloud, and the second BRAS controller and the BRAS repeater are deployed on the same physical device. The first BRAS controller and the second BRAS controller have at least control plane functions.

[0140] Step 402: Authenticate the first CPE and send first information to the BRAS forwarder after successful authentication. The first information is used by the BRAS forwarder to forward the data of the first CPE.

[0141] In practical applications, before step 401, if the first BRAS controller fails, the second BRAS controller needs to establish a communication connection with the BRAS repeater to achieve information exchange.

[0142] Based on this, in one embodiment, the method may further include:

[0143] In the event of a failure of the first BRAS controller, a connection is established with the BRAS repeater;

[0144] In order to conserve communication resources, the second BRAS controller may disconnect from the BRAS repeater when the first BRAS controller returns to normal.

[0145] After the communication connection is established, the second BRAS controller can receive relevant information about the data forwarding synchronized by the BRAS repeater through the established communication connection.

[0146] Specifically, in one embodiment, the method may further include:

[0147] The system receives second information synchronized by the BRAS forwarder after a failure of the first BRAS controller. The second information contains information related to data forwarding from at least one CPE in the local network of the BRAS forwarder.

[0148] In practical applications, after information synchronization is complete, the second BRAS controller can receive a second request sent by the BRAS repeater to request the first CPE to perform authentication and allocate relevant information for data forwarding of the first CPE; wherein, the second request may include the first CPE's identity information, such as a device identifier. Using the second request, the second BRAS controller can authenticate the first CPE through an AAA server.

[0149] For example, using the first CPE identity information in the second request, the second BRAS controller can generate an authentication request and send it to the AAA server. The authentication request contains the first CPE identity information. After receiving the authentication request, the AAA server searches for information matching the first CPE identity information in its locally stored CPE identity information. If a matching information is found, the authentication is successful, and the AAA server returns a successful authentication response to the second BRAS controller. If no matching information is found, the authentication fails, and the AAA server returns a failed authentication response to the second BRAS controller.

[0150] If the response characterization authentication is successful, for multiple CPEs, the second BRAS controller can send the pre-configured information as the first information to the BRAS forwarder.

[0151] Specifically, in one embodiment, the first information is used by the BRAS forwarder to forward data of a plurality of CPEs containing the first CPE.

[0152] In other words, for multiple CPEs that need to access the network, the second BRAS controller can send pre-configured first information to the BRAS forwarder to forward data for multiple CPEs, without needing to send different first information to the BRAS forwarder for different CPEs.

[0153] In practical applications, since the second BRAS controller stores the first information issued during the failure of the first BRAS controller, after the first BRAS controller recovers, the second BRAS controller can, under the instruction of the BRAS repeater, synchronize the first information of all data forwarding stored locally to the first BRAS controller, so that the first BRAS controller can subsequently enable network access and data forwarding for CPEs that need to access the network.

[0154] Based on this, in one embodiment, the method may further include:

[0155] The system receives a third message sent by the BRAS device repeater after the first BRAS controller recovers. The third message indicates that the system should synchronize with the first BRAS controller the relevant information for data forwarding of at least one CPE in the local network of the second BRAS controller that is connected to the network.

[0156] Synchronize with the first BRAS controller the relevant information for data forwarding from at least one CPE in the local connected network.

[0157] In practical applications, after receiving the third information, before the second BRAS controller communicates with the first BRAS controller, it needs to determine whether a communication connection has been established with the first BRAS controller. If the second BRAS controller has not established a communication connection with the first BRAS controller, then a communication connection needs to be established. The method by which the second BRAS controller establishes a communication connection with the first BRAS controller can refer to the process of establishing a connection between the first BRAS controller and the BRAS repeater in related technologies, and this application embodiment does not limit this.

[0158] After synchronization is complete, in order to save storage resources, the second BRAS controller can clear the relevant information for data forwarding of at least one CPE in the local connected network, and then stop operating until the first BRAS controller fails again.

[0159] The communication method provided in this application embodiment involves a BRAS repeater receiving a first request from a first CPE, the first request being for requesting network access. In the event of a failure of the first BRAS controller, a second request is sent to a second BRAS controller. This second request is for requesting authentication of the first CPE and allocation of relevant information for data forwarding by the first CPE. The first BRAS controller is located in the cloud, and the second BRAS controller and the BRAS repeater are deployed on the same physical device. Both the first and second BRAS controllers have at least control plane functionality. The second BRAS controller authenticates the first CPE and, upon successful authentication, sends first information to the BRAS repeater. This first information is used by the BRAS repeater to forward the data from the first CPE. The solution provided in this application embodiment, under a BRAS system architecture with separation of forwarding and control, allows a built-in BRAS controller deployed on the same device as the BRAS repeater to respond to new user access requests when the external BRAS controller deployed in the cloud fails, thereby enabling network access and data forwarding for new users. This ensures successful network access and data forwarding for new users even when the external BRAS controller fails, improving the success rate of network access.

[0160] The present application will be further described in detail below with reference to application examples.

[0161] This application example proposes a novel BRAS architecture with separate control and forwarding mechanisms. It extends the functionality of the BRAS repeater (hereinafter referred to as BRAS-UP) device within the existing BRAS architecture; in other words, an additional BRAS controller is deployed on the BRAS-UP device. For ease of description, the BRAS-CP deployed in the cloud is referred to as the external CP, and the BRAS-CP deployed on the BRAS-UP device is referred to as the built-in CP. Under this new BRAS system architecture, the data processing flow based on PPPoE services is as follows: Figure 5 As shown, it includes the following steps:

[0162] Step 501: When BRAS-UP detects a fault in the external CP (i.e., the second BRAS controller), proceed to step 502;

[0163] For example, BRAS-UP periodically sends messages to an external CP. If it does not receive a response to the message from the external CP three times in a row, BRAS-UP can determine that the external CP has failed.

[0164] Step 502: Establish a communication channel between BRAS-UP and the built-in CP;

[0165] Here, after the communication channel is established, BRAS-UP will set the first tag information internally to mark the CP currently connected to BRAS-UP as the built-in CP, and then execute step 503.

[0166] Step 503: BRAS-UP synchronizes the user entries of the CPE that have been connected to the network to the built-in CP. Then, proceed to step 504.

[0167] Step 504: The CPE sends a PADI to the BRAS-UP via the SW / OLT to request network access;

[0168] Step 505: After receiving the PADI, the BRAS-UP will pass the PADI through to the built-in CP;

[0169] Step 506: After receiving PADI, the built-in CP sends PADO to BRAS-UP;

[0170] Step 507: After receiving PADO, BRAS-UP transmits PADO to CPE via SW / OLT;

[0171] In practical applications, after receiving PADO, the CPE sends PADS to the built-in CP via BRAS-UP for further confirmation; correspondingly, after receiving PADS, the built-in CP sends PADT for PADS to the CPE via BRAS-UP, thus achieving bidirectional confirmation between the CPE and the built-in CP. Then, step 508 is executed.

[0172] Step 508: After confirmation, the built-in CP authenticates the CPE through the AAA server;

[0173] In practical application, the built-in CP actively sends an authentication request to the CPE via BRAS-UP to request authentication of the CPE. Correspondingly, after receiving the authentication request, the CPE returns an authentication response to the built-in CP via BRAS-UP, which at least contains the CPE's identity information. After receiving the authentication response, the built-in CP sends an access request to the AAA server, which also contains the CPE's identity information. Upon receiving the access request, the AAA server searches its database for information matching the CPE's identity information in the access request to authenticate the CPE. Then, it executes step 509. If the AAA server finds a matching information, authentication is successful; otherwise, authentication fails.

[0174] Step 509: The AAA server sends an authentication response (Access-Accept) to the built-in CP;

[0175] The authentication response can characterize the authentication result, specifically including authentication success or authentication failure.

[0176] Here, if the authentication response indicates successful authentication, proceed to step 510.

[0177] Step 510: The built-in CP sends user entries (i.e., the first information) to BRAS-UP;

[0178] In practical applications, the built-in CP can assign the same user policies to CPEs, such as rate limiting policies. Additionally, the built-in CP can use reserved address ranges to assign IP addresses to CPEs. Based on the assigned user policies and IP addresses, the built-in CP can obtain pre-configured user entries to forward data to multiple CPEs. Because the built-in CP uses a unified method for configuring user policies and IP addresses, it can achieve the above functions without complex configuration and calculations. Therefore, compared to external CPs, the built-in CP can be considered a lightweight CP.

[0179] Furthermore, in practical applications, external service providers (CPs) are typically deployed at the provincial / municipal level, while internal CPs are deployed at the district / county level. In the above scenario, the number of users that an internal CP needs to manage is far less than that that of an external CP, and the configuration of an internal CP is also much simpler compared to an external CP.

[0180] Step 511: Through BRAS-UP, CPE can achieve normal data forwarding;

[0181] Here, for the data that the CPE needs to forward, BRAS-UP can forward the data to the CPE based on the issued user table entries.

[0182] Step 512: When BRAS-UP detects that the external CP has returned to normal, proceed to step 513;

[0183] Step 513: BRAS-UP establishes a communication channel with the external CP;

[0184] Here, after the communication channel is established, BRAS-UP will internally set a second tag to mark the CP currently connected to BRAS-UP as an external CP, and then execute step 514.

[0185] Step 514: BRAS-UP notifies the built-in CP to synchronize all user entries to the external CP;

[0186] Here, BRAS-UP sends a notification to the built-in CP to cause the built-in CP to perform step 515;

[0187] Step 515: The built-in CP synchronizes all user entries to the external CP;

[0188] Here, the built-in CP stores all user entries sent to BRAS-UP by the built-in CP during an external CP failure. When the built-in CP receives a notification from BRAS-UP, it synchronizes all stored user entries to the external CP, and then executes step 516.

[0189] Step 516: Delete the stored user table entries using the built-in CP;

[0190] After synchronization is complete, in order to save storage resources, the built-in CP can delete the user table entries stored locally and execute step 517.

[0191] Step 517: Dismantle the communication channel between the built-in CP and BRAS-UP.

[0192] After the communication channel is dismantled, newly connected users can access the network and forward data through an external CP.

[0193] In this application example, during the failure of the external CP, the built-in CP on the BRAS-UP device temporarily takes over the responsibility of new user online and data forwarding. In this way, even when the external CP fails, users can still access the network normally, ensuring the success rate of network access and thus improving the user experience.

[0194] To implement the method on the BRAS repeater side of this application embodiment, this application embodiment also provides a communication device disposed on the BRAS repeater, such as... Figure 6 As shown, the device includes:

[0195] The first receiving unit 601 is used to receive a first request sent by the first CPE, the first request being used to request network access.

[0196] The first processing unit 602 is configured to send a second request to the second BRAS controller in the event of a failure of the first BRAS controller. The second request is used to request authentication of the first CPE and allocation of relevant information for data forwarding of the first CPE. The first BRAS controller is located in the cloud, and the second BRAS controller and the BRAS forwarder are deployed on a physical device. The first BRAS controller and the second BRAS controller have at least control plane functions.

[0197] The second receiving unit 603 is used to receive first information sent by the second BRAS controller, the first information being used by the BRAS repeater to forward the data of the first CPE.

[0198] In one embodiment, the first processing unit 602 is further configured to synchronize second information to the second BRAS controller when it is determined that the first BRAS controller has failed. The second information includes information related to data forwarding of at least one CPE in the local network of the BRAS repeater.

[0199] In one embodiment, the first processing unit 602 is further configured to send third information to the second BRAS controller when the first BRAS controller recovers to normal operation. The third information indicates that at least one relevant information for CPE data forwarding of the local access network of the second BRAS controller is synchronized to the first BRAS controller.

[0200] In one embodiment, the first processing unit 602 is further configured to set fourth information, the fourth information indicating that the BRAS controller communicating with the BRAS repeater includes the first BRAS controller.

[0201] In one embodiment, the first information is used by the BRAS forwarder to forward data from multiple CPEs containing the first CPE.

[0202] In one embodiment, the first processing unit 602 is further configured to:

[0203] When it is determined that the first BRAS controller has failed, a connection is established with the second BRAS controller;

[0204] And / or,

[0205] Once the first BRAS controller is determined to be back to normal, disconnect the connection with the second BRAS controller.

[0206] In one embodiment, the first processing unit 602 is further configured to set fifth information after establishing a connection with the second BRAS controller, wherein the fifth information indicates that the BRAS controller communicating with the BRAS repeater includes the second BRAS controller.

[0207] In practical applications, the first receiving unit 601 and the second receiving unit 603 can be implemented by the communication interface in the communication device; the first processing unit 603 can be implemented by the processor in the communication device in combination with the communication interface.

[0208] To implement the method on the second BRAS controller side of the embodiments of this application, the embodiments of this application also provide a communication device, which is disposed on the second BRAS controller, such as... Figure 7 As shown, the device includes:

[0209] The third receiving unit 701 is used to receive a second request sent by the BRAS repeater after the first BRAS controller fails. The second request is used to request authentication of the first CPE and allocation of relevant information for data forwarding of the first CPE. The first BRAS controller is located in the cloud, and the second BRAS controller and the BRAS repeater are deployed on a physical device. The first BRAS controller and the second BRAS controller have at least control plane functions.

[0210] The second processing unit 702 is used to authenticate the first CPE and, after successful authentication, send first information to the BRAS repeater through the second communication interface. The first information is used by the BRAS repeater to forward the data of the first CPE.

[0211] In one embodiment, the third receiving unit 701 is further configured to receive second information synchronized by the BRAS repeater after the first BRAS controller fails, the second information containing relevant information for data forwarding of at least one CPE of the locally accessed network of the BRAS repeater.

[0212] In one embodiment, the third receiving unit 701 is further configured to receive third information sent by the BRAS device repeater after the first BRAS controller recovers normal operation, the third information indicating relevant information for data forwarding of at least one CPE of the local access network of the second BRAS controller to synchronize with the first BRAS controller.

[0213] Accordingly, the second processing unit 702 is also configured to synchronize with the first BRAS controller information related to data forwarding of at least one CPE in the local access network.

[0214] In one embodiment, the first information is used by the BRAS forwarder to forward data from multiple CPEs containing the first CPE.

[0215] In one embodiment, the second processing unit 702 is further configured to:

[0216] In the event of a failure of the first BRAS controller, a connection is established with the BRAS repeater;

[0217] And / or,

[0218] Once the first BRAS controller returns to normal, disconnect the connection with the BRAS repeater.

[0219] In practical applications, the third receiving unit 701 can be implemented by the communication interface in the communication device; the second processing unit 702 can be implemented by the processor in the communication device in combination with the communication interface.

[0220] It should be noted that the communication device provided in the above embodiments is only illustrated by the division of the above program modules. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the communication device and communication method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0221] Based on the hardware implementation of the above program modules, and in order to implement the method on the BRAS repeater side of the embodiments of this application, the embodiments of this application also provide a BRAS repeater, such as... Figure 8 As shown, the BRAS transponder 800 includes:

[0222] The first communication interface 801 is capable of exchanging information with the second BRAS controller;

[0223] The first processor 802 is connected to the first communication interface 801 to enable information interaction with the second BRAS controller, and is used to execute the methods provided by one or more of the above-mentioned terminal-side technical solutions when running a computer program.

[0224] The computer program is stored in the first memory 803.

[0225] Specifically, the first communication interface 801 is used for:

[0226] Receive a first request sent by a first CPE, the first request being used to request network access;

[0227] The first processor 802 is used for:

[0228] In the event of a failure of the first BRAS controller, a second request is sent to the second BRAS controller through the first communication interface 801. The second request is used to request authentication of the first CPE and allocation of relevant information for data forwarding of the first CPE. The first BRAS controller is located in the cloud, and the second BRAS controller and the BRAS forwarder are deployed on the same physical device. The first BRAS controller and the second BRAS controller have at least control plane functions.

[0229] The first communication interface 801 receives first information sent by the second BRAS controller, and the first information is used for the BRAS repeater to forward the data of the first CPE.

[0230] In one embodiment, the first processor 802 is further configured to, when determining that the first BRAS controller has failed, synchronize second information to the second BRAS controller through the first communication interface 801, the second information including relevant information for data forwarding of at least one CPE of the local access network of the BRAS repeater.

[0231] In one embodiment, the first processor 802 is further configured to, upon determining that the first BRAS controller has returned to normal operation, send third information to the second BRAS controller via the first communication interface 801, the third information indicating at least one relevant information for CPE data forwarding of the local accessed network of the second BRAS controller to be synchronized to the first BRAS controller.

[0232] In one embodiment, the first processor 802 is further configured to set fourth information, the fourth information indicating that the BRAS controller communicating with the BRAS repeater includes the first BRAS controller.

[0233] In one embodiment, the first information is used by the BRAS forwarder to forward data from multiple CPEs containing the first CPE.

[0234] In one embodiment, the first processor 802 is further configured to:

[0235] When it is determined that the first BRAS controller has failed, a connection is established with the second BRAS controller;

[0236] And / or,

[0237] Once the first BRAS controller is determined to be back to normal, disconnect the connection with the second BRAS controller.

[0238] It should be noted that the specific processing procedures of the first communication interface 801 and the first processor 802 can be understood with reference to the above method.

[0239] Of course, in practical applications, the various components in the BRAS repeater 800 are coupled together through the bus system 804. It can be understood that the bus system 804 is used to implement communication between these components. In addition to the data bus, the bus system 804 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 8 The general labeled all buses as Bus System 804.

[0240] The first memory 803 in this embodiment is used to store various types of data to support the operation of the BRAS repeater 800. Examples of such data include any computer program used to operate on the BRAS repeater 800.

[0241] The methods disclosed in the above embodiments of this application can be applied to the first processor 802, or implemented by the first processor 802. The first processor 802 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware or by instructions in the form of software in the first processor 802. The first processor 802 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The first processor 802 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly reflected as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in the first memory 803. The first processor 802 reads the information in the first memory 803 and completes the steps of the aforementioned method in combination with its hardware.

[0242] In an exemplary embodiment, the BRAS transponder 800 may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to perform the aforementioned method.

[0243] Based on the hardware implementation of the above program modules, and in order to implement the method on the second BRAS controller side of the embodiments of this application, the embodiments of this application also provide a second BRAS controller, such as... Figure 9 As shown, the second BRAS controller 900 includes:

[0244] The second communication interface 901 is capable of exchanging information with the BRAS repeater;

[0245] The second processor 902 is connected to the second communication interface 901 to enable information interaction with the BRAS repeater and to execute the methods provided by one or more technical solutions on the second BRAS controller side when running a computer program.

[0246] The computer program is stored in the second memory 903.

[0247] Specifically, the second communication interface 901 is used to receive a second request sent by the BRAS repeater after the first BRAS controller fails. The second request is used to request authentication of the first CPE and allocation of relevant information for data forwarding of the first CPE. The first BRAS controller is located in the cloud, and the second BRAS controller and the BRAS repeater are deployed on the same physical device. The first BRAS controller and the second BRAS controller have at least control plane functions.

[0248] The second processor 902 is used to authenticate the first CPE and, after successful authentication, send first information to the BRAS repeater through the second communication interface 901. The first information is used by the BRAS repeater to forward the data of the first CPE.

[0249] In one embodiment, the second communication interface 901 is further configured to receive second information synchronized by the BRAS repeater after a failure of the first BRAS controller, the second information containing information related to data forwarding of at least one CPE of the locally accessed network of the BRAS repeater.

[0250] In one embodiment, the second communication interface 901 is further configured to:

[0251] The system receives a third message sent by the BRAS device repeater after the first BRAS controller recovers. The third message indicates that the system should synchronize with the first BRAS controller the relevant information for data forwarding of at least one CPE in the local network of the second BRAS controller that is connected to the network.

[0252] Synchronize with the first BRAS controller the relevant information for data forwarding from at least one CPE in the local connected network.

[0253] In one embodiment, the first information is used by the BRAS forwarder to forward data from multiple CPEs containing the first CPE.

[0254] In one embodiment, the second processor 902 is further configured to:

[0255] In the event of a failure of the first BRAS controller, a connection is established with the BRAS repeater;

[0256] And / or,

[0257] Once the first BRAS controller returns to normal, disconnect the connection with the BRAS repeater.

[0258] It should be noted that the specific processing procedures of the second communication interface 901 and the second processor 902 can be understood by referring to the above method.

[0259] Of course, in practical applications, the various components in the second BRAS controller 900 are coupled together via a bus system 904. It can be understood that the bus system 904 is used to implement communication between these components. In addition to a data bus, the bus system 904 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 9 The general labeled all buses as Bus System 904.

[0260] The second memory 903 in this embodiment is used to store various types of data to support the operation of the second BRAS controller 900. Examples of such data include any computer program used to operate on the second BRAS controller 900.

[0261] The methods disclosed in the embodiments of this application can be applied to, or implemented by, the second processor 902. The second processor 902 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by the integrated logic circuitry of the hardware or by instructions in the form of software within the second processor 902. The second processor 902 may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The second processor 902 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, specifically a second memory 903. The second processor 902 reads information from the second memory 903 and, in conjunction with its hardware, completes the steps of the aforementioned method.

[0262] In an exemplary embodiment, the second BRAS controller 900 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, microprocessors, or other electronic components to perform the aforementioned method.

[0263] It is understood that the memories (first memory 803, second memory 903) in the embodiments of this application can be volatile memory or non-volatile memory, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memories.

[0264] To implement the methods of the embodiments of this application, the embodiments of this application also provide a communication system, such as... Figure 10 As shown, the system includes: a BRAS repeater 1001 and a second BRAS controller 1002.

[0265] It should be noted that the specific processing procedures of the BRAS repeater 1001 and the second BRAS controller 1002 have been described in detail above and will not be repeated here.

[0266] In an exemplary embodiment, this application also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, such as a first memory 803 storing a computer program, which can be executed by a first processor 802 of a BRAS repeater 800 to complete the steps described in the aforementioned BRAS repeater-side method. Another example is a second memory 903 storing a computer program, which can be executed by a second processor 902 of a second BRAS controller 900 to complete the steps described in the aforementioned second BRAS controller-side method. The computer-readable storage medium can be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM.

[0267] It should be noted that terms such as "first" and "second" are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0268] Furthermore, the technical solutions described in the embodiments of this application can be combined arbitrarily without conflict.

[0269] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application.

Claims

1. A communication method, characterized in that, Applications to Broadband Remote Access Server (BRAS) repeaters include: Receive a first request sent by a first customer front-end device (CPE), the first request being used to request network access; In the event of a failure of the first BRAS controller, a second request is sent to the second BRAS controller. The second request is used to request authentication of the first CPE and allocation of relevant information for data forwarding of the first CPE. The first BRAS controller is located in the cloud, and the second BRAS controller and the BRAS forwarder are deployed on a physical device. The first BRAS controller and the second BRAS controller have at least control plane functions. The system receives first information sent by the second BRAS controller. The first information is used for the BRAS forwarder to forward data of multiple CPEs containing the first CPE. The first information is pre-configured.

2. The method according to claim 1, characterized in that, The method further includes: When it is determined that the first BRAS controller has failed, second information is synchronized to the second BRAS controller. The second information contains information related to data forwarding of at least one CPE in the local network of the BRAS repeater.

3. The method according to claim 1, characterized in that, The method further includes: When the first BRAS controller is determined to have returned to normal, a third message is sent to the second BRAS controller, the third message indicating that at least one relevant information for CPE data forwarding of the local access network of the second BRAS controller is synchronized to the first BRAS controller.

4. The method according to claim 3, characterized in that, The method further includes: A fourth piece of information is provided, which indicates that the BRAS controller communicating with the BRAS repeater includes the first BRAS controller.

5. The method according to claim 1, characterized in that, The first information is used by the BRAS forwarder to forward data from multiple CPEs containing the first CPE.

6. The method according to any one of claims 1 to 5, characterized in that, The method further includes: When it is determined that the first BRAS controller has failed, a connection is established with the second BRAS controller; And / or, Once the first BRAS controller is determined to be back to normal, disconnect the connection with the second BRAS controller.

7. The method according to claim 6, characterized in that, The method further includes: After the connection with the second BRAS controller is established, fifth information is set, which indicates that the BRAS controller communicating with the BRAS repeater includes the second BRAS controller.

8. A communication method, characterized in that, Applied to the second BRAS controller, including: The system receives a second request sent by the BRAS repeater after the first BRAS controller fails. The second request is used to request authentication of the first CPE and allocation of relevant information for data forwarding of the first CPE. The first BRAS controller is located in the cloud, and the second BRAS controller and the BRAS repeater are deployed on the same physical device. The first BRAS controller and the second BRAS controller have at least control plane functions. The first CPE is authenticated, and after successful authentication, a first message is sent to the BRAS forwarder. The first message is used by the BRAS forwarder to forward data of multiple CPEs containing the first CPE. The first message is pre-configured.

9. The method according to claim 8, characterized in that, The method further includes: The system receives second information synchronized by the BRAS forwarder after a failure of the first BRAS controller. The second information contains information related to data forwarding from at least one CPE in the local network of the BRAS forwarder.

10. The method according to claim 8, characterized in that, The method further includes: The system receives a third message sent by the BRAS device repeater after the first BRAS controller returns to normal operation. The third message indicates that the system should synchronize with the first BRAS controller the relevant information for data forwarding of at least one CPE in the local network of the second BRAS controller that is connected to the network. Synchronize with the first BRAS controller the relevant information for data forwarding from at least one CPE in the local connected network.

11. The method according to claim 8, characterized in that, The first information is used by the BRAS forwarder to forward data from multiple CPEs containing the first CPE.

12. The method according to any one of claims 8 to 11, characterized in that, The method further includes: In the event of a failure of the first BRAS controller, a connection is established with the BRAS repeater; And / or, Once the first BRAS controller returns to normal, disconnect the connection with the BRAS repeater.

13. A communication device, characterized in that, include: The first receiving unit is configured to receive a first request sent by the first CPE, the first request being used to request network access. The first processing unit is configured to send a second request to the second BRAS controller in the event of a failure of the first BRAS controller. The second request is used to request authentication of the first CPE and allocation of relevant information for data forwarding of the first CPE. The first BRAS controller is located in the cloud, and the second BRAS controller and the BRAS forwarder are deployed on a physical device. The first BRAS controller and the second BRAS controller have at least control plane functions. The second receiving unit is configured to receive first information sent by the second BRAS controller. The first information is used by the BRAS forwarder to forward data of multiple CPEs containing the first CPE. The first information is pre-configured.

14. A communication device, characterized in that, include: The third receiving unit is used to receive a second request sent by the BRAS repeater after the first BRAS controller fails. The second request is used to request authentication of the first CPE and allocation of relevant information for data forwarding of the first CPE. The first BRAS controller is located in the cloud, and the second BRAS controller and the BRAS repeater are deployed on the same physical device. The first BRAS controller and the second BRAS controller have at least control plane functions. The second processing unit is used to authenticate the first CPE and send first information to the BRAS forwarder after successful authentication. The first information is used by the BRAS forwarder to forward data of multiple CPEs containing the first CPE. The first information is pre-configured.

15. A BRAS repeater, characterized in that, include: A first processor and a first communication interface; wherein... The first communication interface is used for: Receive a first request sent by a first CPE, the first request being used to request network access; In the event of a failure of the first BRAS controller, a second request is sent to the second BRAS controller. The second request is used to request authentication of the first CPE and allocation of relevant information for data forwarding of the first CPE. The first BRAS controller is located in the cloud, and the second BRAS controller and the BRAS forwarder are deployed on a physical device. The first BRAS controller and the second BRAS controller have at least control plane functions. The system receives first information sent by the second BRAS controller. The first information is used for the BRAS forwarder to forward data of multiple CPEs containing the first CPE. The first information is pre-configured.

16. A second BRAS controller, characterized in that, include: A second processor and a second communication interface; wherein... The second communication interface is used to receive a second request sent by the BRAS repeater after the first BRAS controller fails. The second request is used to request authentication of the first CPE and allocation of relevant information for data forwarding of the first CPE. The first BRAS controller is located in the cloud, and the second BRAS controller and the BRAS repeater are deployed on the same physical device. The first BRAS controller and the second BRAS controller have at least control plane functions. The second processor is used to authenticate the first CPE and, after successful authentication, send first information to the BRAS forwarder through the second communication interface. The first information is used by the BRAS forwarder to forward data of multiple CPEs containing the first CPE. The first information is pre-configured.

17. A BRAS repeater, characterized in that, include: A first processor and a first memory for storing computer programs capable of running on the processor. Wherein, when the first processor is used to run the computer program, it performs the steps of the method according to any one of claims 1 to 7.

18. A second BRAS controller, characterized in that, include: A second processor and a second memory for storing computer programs that can run on the processor. Wherein, when the second processor is used to run the computer program, it performs the steps of the method according to any one of claims 8 to 12.

19. A storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7, or the steps of the method according to any one of claims 8 to 12.

Images