Client device management method, device and system

Abstract

The present application provides a method, device and system for managing client devices, which belong to the field of communication technology. In the solution provided by the present application, the broadband access device can manage the client devices belonging to the domain of the original domain name based on the mapping relationship between the created original domain name and the target domain name using the domain of the target domain name. Since in a scenario where there is a need to modify the domain name, the broadband access device can map the original domain name to a target domain name different from the original domain name, the client device does not need to modify its user name, and the authentication server does not need to modify the user name of the client device it stores. In this way, the problem of a large amount of data modification caused by directly modifying the domain name can be avoided, reducing the operation and maintenance costs of the client device and the authentication server.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method, device, and system for managing client devices. Background Art

[0002] A broadband remote access server (BRAS) is a new type of access gateway for broadband network applications. Client devices (also called users) can access the network through the BRAS. Each user connected to the BRAS belongs to a domain, and users in the same domain have the same service attributes. In other words, the BRAS can distinguish different user groups by domain, allowing them to enjoy different services. Different domains in the BRAS can be distinguished by different domain names, and each user's username is composed of the domain name of the domain to which they belong.

[0003] When managing different BRASs in a unified manner, you may need to modify the domain name. For example, you may need to modify the same domain name on different BRASs to different domain names to resolve domain name conflicts, or modify different domain names on different BRASs to the same domain for unified management. If you modify the domain name directly, all users in the domain will need to modify their usernames, and the authentication server will also need to modify each user's username accordingly, resulting in a large amount of data modification. Summary of the Invention

[0004] The present application provides a client device management method, device and system, which can solve the technical problem of a large amount of modified data caused by modifying a domain name.

[0005] On the one hand, a method for managing a client device is provided, which is applied to a broadband access device. The method may include: creating a mapping relationship between a first original domain name and a first target domain name, determining that the domain name of the domain to which the first client device belongs is the first original domain name, and based on the mapping relationship between the first original domain name and the first target domain name, using the domain of the first target domain name to manage the first client device; wherein the first target domain name is different from the first original domain name.

[0006] Since broadband access equipment can map the original domain name to a target domain name that is different from the original domain name, in scenarios where domain name modification is required, neither the client device nor the authentication server needs to be modified. This avoids the problem of large data modifications caused by directly modifying the domain name, and reduces the operation and maintenance costs of the client device and the authentication server.

[0007] Optionally, the first configuration information of the domain of the first target domain name in the broadband access device is the same as the configuration information of the domain of the first original domain name in the first network device.

[0008] This ensures that after the broadband access device manages the first client device based on the first configuration information, the management policy for the first client device will not be changed. For example, the first client device can continue to enjoy the previously subscribed services. Because neither the client device nor the authentication server is aware of the domain name mapping operation performed by the broadband access device, the impact on existing network services can be effectively reduced.

[0009] Optionally, the broadband access device is a CP device in a CU-separated network access system, and the network access system also includes at least two UP devices connected to the CP device. The first network device is a first BRAS, and the at least two UP devices include: a first UP device evolved from the first BRAS, and a second UP device evolved from the second BRAS.

[0010] The solution provided in this application can be applied to the scenario where the network access system evolves to CU separation deployment, which can ensure that there is no need to modify the client device and authentication server during the evolution process.

[0011] Optionally, based on the mapping relationship between the first original domain name and the first target domain name, the process of using the domain of the first target domain name to manage the first client device may include: determining that the first client device goes online from the first UP device; based on the mapping relationship between the first original domain name and the first target domain name, using the first configuration information to manage the first client device.

[0012] Because the first configuration information is identical to the domain configuration information of the first original domain name in the first BRAS, the first configuration information is used to manage the first client device that goes online from the first UP device, thereby avoiding any impact on the services customized by the first client device. In other words, the first client device will not be aware of the transformation and evolution of the network access system.

[0013] Optionally, the first configuration information is different from the configuration information of the domain of the first original domain name in the second BRAS; the method may also include: creating a mapping relationship between the first original domain name and a second target domain name, the second target domain name is different from the first target domain name and different from the first original domain name, the second configuration information of the domain of the second target domain name is the same as the configuration information of the domain of the first original domain name in the second BRAS; determining that the second client device goes online from the second UP device, and the domain name of the domain to which the second client device belongs is the first original domain name; and based on the mapping relationship between the first original domain name and the second target domain name, using the second configuration information to manage the second client device.

[0014] Because the second configuration information is identical to the domain configuration information for the first original domain name in the second BRAS, using the second configuration information to manage the second client device that goes online from the second UP device can avoid affecting the services customized by the second client device. In other words, the second client device will not be aware of the transformation and evolution of the network access system.

[0015] Optionally, the first configuration information is the same as the configuration information of the domain of the second original domain name in the second BRAS, and the second original domain name is different from the first original domain name; the method may also include: creating a mapping relationship between the second original domain name and the first target domain name; determining that the second client device goes online from the second UP device, and the domain name of the domain to which the second client device belongs is the second original domain name; based on the mapping relationship between the second original domain name and the first target domain name, using the first configuration information to manage the second client device.

[0016] The solution provided in this application can also map different original domain names to the same target domain name, thereby facilitating unified management and maintenance of client devices within a domain with the same configuration information, effectively improving the management flexibility of domain-based client devices.

[0017] Optionally, the method may further include: configuring a mapping relationship between the first original domain name and the first target domain name on a first interface of a CP device, where the first interface is used to receive a message from the first client device.

[0018] The CP device configures the mapping relationship on the first interface to ensure that after detecting that the first client device goes online from the first interface, the CP device can map the first original domain name of the domain to which the first client device belongs based on the domain name mapping relationship configured on the first interface.

[0019] Optionally, the method may also include: configuring a mapping relationship between the first original domain name and the second target domain name on the second interface of the CP device, or configuring a mapping relationship between the second original domain name and the first target domain name on the second interface of the CP device, and the second interface is used to receive the message from the second client device.

[0020] That is, the mapping relationship on the CP device is configured on the interface. Multiple interfaces can be configured with different mapping relationships to support selecting the appropriate mapping relationship under the interface where the client device goes online and mapping the original domain name to the target domain name.

[0021] Optionally, the broadband access device is the first BRAS in the network access system, the first network device is the first BRAS, the network access system also includes a second BRAS and a backup BRAS, the backup BRAS is used to back up the data in the first BRAS and the second BRAS; the first configuration information is different from the configuration information of the domain of the first original domain name in the second BRAS; the backup BRAS includes a domain whose domain name is the first target domain name, and the configuration information of the domain of the first target domain name in the backup BRAS is the same as the first configuration information.

[0022] The solution provided in this application can also be applied to scenarios where the network access system adopts a hot standby solution, which can ensure that during the network access system transformation process, there is no need for client devices and authentication servers to cooperate in the transformation.

[0023] Optionally, the method may further include: configuring a mapping relationship between the first original domain name and the first target domain name on a backup channel of the first BRAS, the backup channel being used to synchronize data in the first BRAS to the backup BRAS.

[0024] In a hot standby scenario, configuring mappings on the backup channel ensures the independence of resources within the backup channel. Furthermore, configuring mappings at the backup channel level facilitates management and maintenance of mappings.

[0025] Optionally, the broadband access device is a backup BRAS in a network access system, the first network device is a first BRAS in the network access system, and the network access system also includes a second BRAS, and the backup BRAS is used to back up data in the first BRAS and the second BRAS; the first configuration information is different from the configuration information of the domain of the first original domain name in the second BRAS; based on the mapping relationship between the first original domain name and the first target domain name, the process of using the domain of the first target domain name to manage the first client device may include: determining that the first client device is a client device registered in the first BRAS; based on the mapping relationship between the first original domain name and the first target domain name, using the first configuration information to manage the first client device.

[0026] In the hot standby scenario, since the backup BRAS can map the conflicting first original domain name to the first target domain name, different domains can be effectively distinguished.

[0027] Optionally, the method may also include: creating a mapping relationship between the first original domain name and a second target domain name, the second target domain name is different from the first target domain name and different from the first original domain name, the second configuration information of the domain of the second target domain name in the backup BRAS is the same as the configuration information of the domain of the first original domain name in the second BRAS; determining that the second client device is a client device registered in the second BRAS, and the domain name of the domain to which the second client device belongs is the first original domain name; and based on the mapping relationship between the first original domain name and the second target domain name, using the second configuration information to manage the second client device.

[0028] Since the second configuration information is the same as the domain configuration information of the first original domain name in the second BRAS, using the second configuration information to manage the second client device can avoid affecting the services customized by the second client device after adding a hot standby solution.

[0029] Optionally, the method may also include: configuring a mapping relationship between the first original domain name and the first target domain name on a first backup channel of the backup BRAS, the first backup channel being used to synchronize data in the first BRAS; and configuring a mapping relationship between the first original domain name and the second target domain name on a second backup channel of the backup BRAS, the second backup channel being used to synchronize data in the second BRAS.

[0030] In a hot standby scenario, configuring different mapping relationships on different backup channels ensures the independence of resources within the backup channels. Furthermore, configuring mapping relationships at the backup channel level facilitates management and maintenance of mapping relationships.

[0031] Optionally, the process of creating a mapping relationship between the first original domain name and the first target domain name may include: creating a mapping relationship between the first original domain name and the first target domain name based on a received creation instruction.

[0032] The creation instruction may be configured by an operation and maintenance personnel, or may be issued by a third-party controller connected to the broadband access device.

[0033] Optionally, the method may further include: sending an authentication request for instructing to authenticate the first client device to an authentication server, the authentication request including a user name of the first client device, and the user name including the first original domain name.

[0034] Since the user name carried in the authentication request sent by the broadband access device to the authentication server is the original user name of the client device, that is, the user name of the client device has not changed, during the transformation or evolution of the network access system, the client device and the authentication server do not need to cooperate in the transformation.

[0035] On the other hand, a broadband access device is provided. The broadband access device includes at least one module, and the at least one module can be used to implement the client device management method provided by the above aspect.

[0036] On the other hand, a broadband access device is provided, which includes: a memory, a processor and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, it implements the client device management method provided in the above aspects.

[0037] On the other hand, a computer-readable storage medium is provided, in which instructions are stored. When the instructions are executed on a computer, the computer executes the client device management method provided in the above aspects.

[0038] In yet another aspect, a computer program product comprising instructions is provided. When the computer program product is run on a computer, the computer is enabled to execute the client device management method provided in the above aspect.

[0039] On the other hand, a network access system with separate CP and UP is provided. The system may include a CP device and multiple UP devices connected to the CP device, wherein the CP device includes the broadband access device provided in the above aspect.

[0040] On the other hand, a network access system is provided, which may include multiple active BRASs and at least one backup BRAS, wherein the at least one active BRAS includes the broadband access device provided by the above aspect, and the backup BRAS includes the broadband access device provided by the above aspect.

[0041] In summary, the present application provides a method, device, and system for managing client devices. The broadband access device can manage client devices belonging to the domain of the original domain name based on the mapping relationship between the created original domain name and the target domain name using the domain of the target domain name. Since, in a scenario where there is a need to modify the domain name, the broadband access device can map the original domain name to a target domain name that is different from the original domain name, the client device does not need to modify its user name, and the authentication server does not need to modify the user name of the client device it stores. In this way, the problem of a large amount of data modification caused by directly modifying the domain name can be avoided, reducing the operating and maintenance costs of the client device and the authentication server. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 This is a schematic diagram of the structure of a network access system provided by an embodiment of the present application;

[0043] Figure 2This is a structural diagram of a CU-separated network access system provided in an embodiment of the present application;

[0044] Figure 3 This is a flowchart of a client device management method provided by an embodiment of the present application;

[0045] Figure 4 This is a flowchart of another client device management method provided by an embodiment of the present application;

[0046] Figure 5 This is a flowchart of another method for managing a client device provided in an embodiment of the present application;

[0047] Figure 6 This is a schematic diagram of the structure of another network access system provided in an embodiment of the present application;

[0048] Figure 7 This is a flowchart of another method for managing a client device provided in an embodiment of the present application;

[0049] Figure 8 This is a schematic diagram of the structure of a broadband access device provided in an embodiment of the present application;

[0050] Figure 9 This is a schematic diagram of the structure of another broadband access device provided in an embodiment of the present application;

[0051] Figure 10 This is a structural diagram of another broadband access device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0052] The following describes in detail the client device management method, device and system provided by the embodiments of the present application in conjunction with the accompanying drawings.

[0053] Figure 1 This is a schematic diagram of the structure of a network access system provided by an embodiment of the present application. Figure 1 As shown, the system may include multiple BRASs, each of which may be connected to the Internet via a forwarding device 01, and each of which may also be connected to a client device 02. The forwarding device 01 may be a network device such as a router or a switch. The client device 03 may also be called a user device, which may be a computer device such as a mobile phone, a laptop or a desktop computer. Figure 1As can be seen, the BRAS can be connected to the client device 02 through the customer-premises equipment (CPE). The CPE can also be called an access node (AN), which can be a switch (SW), an optical line terminal (OLT) or a digital subscriber line access multiplexer (DSLAM). Figure 1 As shown, the client device 02 can exchange dial-up protocol messages with the BRAS to access the network. Furthermore, after accessing the network, the client device 02 can send and receive service messages through the BRAS. The dial-up protocol can be PPPoE (Point to Point Protocol over Ethernet) or IPoE (Internet Protocol over Ethernet).

[0054] With the development of technology, network access systems have gradually evolved into systems with separate CP devices and UP devices (CU separation). In a system with separate CU deployment, Figure 2 As shown, each BRAS can evolve into a UP device, and multiple UP devices can be taken over by a CP device 03 and uniformly controlled by the CP device 03. Figure 1 and Figure 2As can be seen, BRAS1 evolves into UP1, and BRAS2 evolves into UP2. UP1 and UP2 are taken over by the same CP device 03. Each UP device can be a physical UP (pUP) device or a virtual UP (vUP) device. For example, the UP device can be a VM deployed on a physical server. Furthermore, each UP device serves as the user plane of the BNG (or VBNG), responsible for forwarding user service messages based on user entries issued by the CP device, and implementing traffic policies based on technologies such as Quality of Service (QoS) and Access Control Lists (ACLs). CP device 03 can be implemented and centrally deployed using cloud technology. For example, CP device 03 can include multiple virtual machines (VMs) deployed on a physical server. CP device 03 serves as the control plane of the BNG (or VBNG), responsible for controlling and managing client devices (also referred to as users), as well as for unified management of multiple UP devices. For example, the CP device 03 is mainly responsible for exchanging dial-up protocol messages with the client device 02 to enable the client device 02 to go online, and for delivering configurations and user entries to the UP device.

[0055] In a CU-separated deployment system, UP devices are also called forwarding plane devices. Therefore, CU separation can also be referred to as forwarding and control separation, or forwarding-control separation. Systems deployed using this CU-separated deployment approach are also called CU-separated network access systems, or forwarding-control separation network access systems.

[0056] After the network access system evolves to CU separation deployment, if multiple different BRASs are taken over by the same CP device, and there are domains with the same domain name but different configuration information in the multiple BRASs, it will cause domain name conflicts. For example, refer to Figure 1 , assuming that the domain with the domain name domain1 in BRAS1 is deployed with the Destination Address Accounting (DAA) service, and the domain with the domain name domain1 in BRAS2 is deployed with the Enhanced Dynamic Service Gateway (EDSG) service. Figure 2 After the CU separation is deployed as shown, the domain named domain1 in the CP device 03 can only have one configuration information. The CP device 03 cannot manage users from UP1 (i.e. BRAS1 before evolution) and users who go online from UP2 (i.e. BRAS2 before evolution) at the same time based on the configuration information.

[0057] In the related art, in order to solve the problem of domain name conflicts caused by the above-mentioned domain name duplication, the client device can modify the domain name in its username, and accordingly, the authentication server also needs to modify the username of each client device accordingly. This results in a large amount of data modification and low efficiency. Alternatively, in the related art, the CP device can also forcibly authenticate the default domain, or forcibly replace the authentication domain, to manage the client devices that go online from a certain UP according to the preset default domain. However, this method will forcibly modify the domain to which all client devices that go online from a certain UP device belong, and its adjustment precision is low and its flexibility is poor. Alternatively, in the related art, the authentication server can also identify the client device whose domain name is to be modified, and issue a new domain name to the identified client device. However, this method requires the authentication server to accurately identify the client device and modify the username of the client device stored in its database, which places high requirements on the authentication server.

[0058] In the embodiments of the present application, the configuration information for each domain is used to indicate the management policy for managing client devices within the domain. For example, the configuration information may include policy information for authentication, billing, and authorization of client devices within the domain, as well as service deployment information for client devices within the domain. The service deployment information includes information such as the permissions, bandwidth, and QoS for client devices to use basic access services (such as Internet access) or value-added services.

[0059] Figure 3 This is a flowchart of a client device management method provided by an embodiment of the present application. The method can be applied to a broadband access device in a network access system. The broadband access device can be a BRAS or a CP device. Figure 3 As shown, the method may include:

[0060] Step 101: Create a mapping relationship between a first original domain name and a first target domain name.

[0061] In a domain name conflict scenario, or other scenario where a domain name needs to be modified, the broadband access device can create a mapping relationship between a first original domain name and a first target domain name, where the first target domain name is different from the first original domain name. The first original domain name is a duplicate domain name in the domain name conflict scenario, or the first original domain name is a domain name to be modified in other scenarios.

[0062] Optionally, the domain of the first target domain name may be a new domain created by the broadband access device, or may be a domain already deployed in the broadband access device.

[0063] Step 102: Determine that the domain name of the domain to which the first client device belongs is the first original domain name.

[0064] In an embodiment of the present application, the client device can exchange dial-up protocol messages with the broadband access device to access the network. The broadband access device can determine the domain name of the domain to which the first client device belongs during the client device access process (also referred to as the online process) or after the client device is online. If the broadband access device determines that the domain name of the domain to which the first client device belongs is the first original domain name, step 103 can be continued. If the broadband access device determines that the domain name of the domain to which the first client device belongs is not the first original domain name, the first client device can be managed directly based on the domain of the first original domain name.

[0065] Step 103: Based on the mapping relationship between the first original domain name and the first target domain name, the first client device is managed using the domain of the first target domain name.

[0066] The broadband access device is pre-configured with a mapping relationship between the first original domain name and the first target domain name. If the broadband access device determines that the domain name of the domain to which the currently connected client device belongs is the first original domain name, the first client device can be managed using the domain of the first target domain name based on the mapping relationship. The domain configuration information of the first target domain name can be the same as or different from the domain configuration information of the first original domain name, and this is not limited in this embodiment of the present application.

[0067] Because the first target domain name is different from the first original domain name, it can effectively distinguish different domains in the event of a domain name conflict, and can flexibly modify domain names in other scenarios where domain name modification is required. Furthermore, because the broadband access device can create a mapping relationship between the original domain name and the target domain name, the client device does not need to modify its original domain name and username, and accordingly, the authentication server does not need to modify the client device's username stored therein.

[0068] In summary, the embodiment of the present application provides a method for managing client devices, in which the broadband access device can manage the client devices belonging to the domain of the original domain name based on the mapping relationship between the created original domain name and the target domain name using the domain of the target domain name. Since, in a scenario where there is a need to modify the domain name, the broadband access device can map the original domain name to a target domain name that is different from the original domain name, the client device does not need to modify its user name, and the authentication server does not need to modify the user name of the client device it stores. In this way, the problem of a large amount of data modification caused by directly modifying the domain name can be avoided, thereby reducing the operating and maintenance costs of the client device and the authentication server.

[0069] Optionally, the first configuration information for the domain of the first target domain name in the broadband access device is identical to the configuration information for the domain of the first original domain name in the first network device. This ensures that, after the broadband access device manages the first client device based on the first configuration information, the management policy for the first client device will not be changed. For example, the first client device can continue to enjoy previously subscribed services. Because neither the client device nor the authentication server is aware of the domain name mapping operation performed by the broadband access device, the impact on existing network services can be effectively reduced.

[0070] As an optional implementation, the client device management method provided in the embodiment of the present application can be applied to the CP device in the network access system where the CP and UP are separated. Figure 2 CP device 03 shown. Reference Figure 2 , the network access system also includes: at least two UP devices connected to the CP device 03, the at least two UP devices include: a first UP device evolved from a first BRAS, and a second UP device evolved from a second BRAS. The domain of the first original domain name is deployed in both the first BRAS and the second BRAS, and the configuration information of the domain of the first original domain name deployed in the two BRAS is different. Among them, the first BRAS is the first network device, that is, the first configuration information of the domain of the first target domain name in the CP device is the same as the configuration information of the domain of the first original domain name in the first BRAS.

[0071] The method provided in the embodiment of the present application can be applied to the scenario where the same first original domain name in different BRASs needs to be mapped to different target domain names. Figure 4 As shown, the method includes:

[0072] Step 201: The CP device creates a mapping relationship between a first original domain name and a first target domain name.

[0073] Since the domain configuration information of the first original domain name in the first BRAS is different from the domain configuration information of the first original domain name in the second BRAS, after the two BRASs evolve into UP devices and are taken over by the same CP device, the CP device can create a mapping relationship between the first original domain name and the first target domain name in order to distinguish the two domains. The first target domain name is different from the first original domain name, and the first configuration information of the domain of the first target domain name is the same as the domain configuration information of the first original domain name in the first BRAS. The domain of the first target domain name can be a new domain created by the CP device, or it can be a domain already deployed in the CP device.

[0074] Optionally, the CP device may create a mapping relationship between the first original domain name and the first target domain name based on a received creation instruction, wherein the creation instruction may be configured by an operation and maintenance person, or may be issued by a third-party controller connected to the CP device.

[0075] Example, reference Figure 1 and Figure 2 Assuming that a domain with the first original domain name domain1 is deployed on both BRAS1 and BRAS2, the creation instruction configured by the operation and maintenance personnel on CP device 03 may include the following command line:

[0076] #

[0077] domain-map-list test1

[0078] domain domain1 mapping domianA

[0079] #

[0080] The CP device 03 can create a first domain mapping template (domain-map-list) named test1 based on the command line. The first domain mapping template records the mapping relationship between the first original domain name domain1 and the first target domain name domianA.

[0081] Step 202: The CP device configures a mapping relationship between the first original domain name and the first target domain name on the first interface.

[0082] Among them, the first interface is an interface (interface) for receiving messages sent by the first client device among the multiple interfaces included in the CP device. The interface in the CP device for receiving messages sent by the client device can also be called a broadband access service (BAS) interface. The first client device is a client device that accesses the network from the first BRAS before the network access system evolves to CU separation deployment, and the first client device belongs to the domain of the first original domain name in the first BRAS. Optionally, the CP device can configure the mapping relationship between the first original domain name and the first target domain name on the first interface based on the configuration instructions input by the operation and maintenance personnel, or the configuration instructions issued by the third-party controller.

[0083] For example, suppose that Figure 1 In the network access system shown, client device user1 accesses the network through BRAS1. Figure 2In the network access system shown, the first interface in CP device 03 for receiving the message from user 1 is an Ethernet link aggregation (Ethernet-Trunk, Eth-Trunk) interface, and the identifier of the Eth-Trunk interface is 1.1. The operation and maintenance personnel can configure the following command line in CP device 03:

[0084]

[0085] Based on the above command line, CP device 03 can configure (also referred to as reference) the first domain mapping template named test1 under Eth-Trunk 1.1 interface. In the above command line, "access-type layer2-subscriber" indicates setting the user access type to Layer 2 user.

[0086] Step 203: The CP device creates a mapping relationship between the first original domain name and the second target domain name.

[0087] To distinguish the domain of the first original domain name in the first BRAS from the domain of the first original domain name in the second BRAS, the CP device may further establish a mapping relationship between the first original domain name and a second target domain name. The second target domain name is different from the first original domain name and the first target domain name. Furthermore, the second configuration information for the domain of the second target domain name is consistent with the configuration information for the domain of the first original domain name in the second BRAS.

[0088] Optionally, the domain of the second target domain name can be a new domain created by the CP device, or a domain already deployed in the CP device. Furthermore, the CP device can create a mapping relationship between the first original domain name and the second target domain name based on the received creation instruction. The creation instruction can be configured by operations and maintenance personnel, or issued by a third-party controller connected to the CP device.

[0089] Example, reference Figure 1 and Figure 2 Assuming that a domain with the first original domain name domain1 is deployed in both BRAS1 and BRAS2, the creation instruction configured by the operation and maintenance personnel on CP device 03 may also include the following command line:

[0090] #

[0091] domain-map-list test2

[0092] domain domain1 mapping domainB

[0093] #

[0094] The CP device 03 can create a second domain mapping template named test2 based on the command line. The second domain mapping template records the mapping relationship between the first original domain name domain1 and the second target domain name domianB.

[0095] Step 204: The CP device configures a mapping relationship between the first original domain name and the second target domain name on the second interface.

[0096] The second interface is an interface among multiple interfaces included in the CP device for receiving messages sent by a second client device. The second client device is a client device that accesses the network from a second BRAS before the network access system evolves to a CU-separated deployment, and the second client device belongs to the domain of the first original domain name in the second BRAS. Optionally, the CP device can configure the mapping relationship between the first original domain name and the second target domain name on the second interface based on a configuration instruction input by an operation and maintenance personnel or a configuration instruction issued by a third-party controller.

[0097] For example, suppose that Figure 1 In the network access system shown, client device user2 accesses the network through BRAS2. Figure 2 In the network access system shown, the second interface in CP device 03 for receiving the message from user 2 is an Eth-Trunk interface, and the identifier of the Eth-Trunk interface is 1.2. The operation and maintenance personnel can configure the following command line in CP device 03:

[0098]

[0099] Based on the above command line, the CP device 03 can configure a first domain mapping template named test2 on the Eth-Trunk 1.2 interface. In the above command line, "statistic enable" indicates enabling the traffic statistics function.

[0100] Step 205: The CP device exchanges dial-up protocol messages with the first client device through the first UP device.

[0101] After the network access system evolves to a CU-separated deployment, the first client device can exchange dial-up protocol messages with the CP device through the first UP device to access the network. Accordingly, the CP device can determine that the first client device is online from the first UP device. The dial-up protocol can be PPPoE or IPoE, etc. If the dial-up protocol is PPPoE, the dial-up protocol messages exchanged between the CP device and the first client device may include: PPPoE active discovery initiation (PPPoE active discovery initiation, PADI) message, PPPoE active discovery service (PPPoE active discovery offer, PADO) message, PPPoE active discovery request (PPPoE active discovery request, PADR) message and PPPoE active discovery session (PPPoE active discovery session, PADS) message, etc.

[0102] Step 206: The CP device determines that the domain name of the domain to which the first client device belongs is the first original domain name.

[0103] In the embodiment of the present application, the CP device can determine the domain name of the domain to which the first client device belongs during the process of the first client device accessing the network (also referred to as the online process) or after the first client device completes the online process. If the CP device determines that the domain name of the domain to which the first client device belongs is the first original domain name, it can continue to execute Figure 4 The next steps in the flowchart shown.

[0104] If the CP device determines that the domain name of the domain to which the first client device belongs is not the first original domain name, the CP device may proceed according to the existing process. The existing process includes: the CP device sending an authentication request to the authentication server to instruct authentication of the first client device; after the CP device determines that the first client device has passed authentication based on the authentication response sent by the authentication server, the CP device directly manages the first client device based on the domain name of the first original domain name.

[0105] Optionally, in an embodiment of the present application, the CP device may determine the domain name of the domain to which the first client device belongs based on the user name sent by the first client device during the online process. Alternatively, the CP device may determine the domain name of the domain to which the first client device belongs based on the domain name or user name issued by the authentication server to the first client device during the online process. Alternatively, the CP device may determine the domain name of the domain to which the first client device belongs based on the domain name issued by the change of authorization (COA) module in the authentication server after the first client device goes online. Alternatively, the CP device may determine the domain name of the domain to which the first client device belongs based on the configuration of its first interface (i.e., the interface for receiving messages sent by the first client device).

[0106] Step 207: The CP device sends a first authentication request to the authentication server.

[0107] In an embodiment of the present application, after the CP device completes the dial-up protocol message interaction with the first client device, it is also necessary to send a first authentication request to the authentication server to instruct the authentication of the first client device. The first authentication request includes the username of the first client device, and the username includes the first original domain name. The authentication server can be a Remote Authentication Dial-in User Service (RADIUS) server. The authentication server supports the Authentication, Authorization, and Accounting (AAA) protocol and is also called an AAA server.

[0108] For example, assuming that the user name of the first client device user1 is user1@domain1, the user name included in the first authentication request sent by the CP device to the authentication server to instruct the authentication of the first client device user1 is user1@domain1.

[0109] Since the user name carried in the first authentication request sent by the CP device to the authentication server is still the original user name of the first client device, that is, the user name of the first client device has not changed, during the process of the network access system evolving into a CU-separated deployment, the first client device and the authentication server do not need to cooperate in the transformation.

[0110] Step 208: The authentication server sends a first authentication response to the CP device.

[0111] After receiving the first authentication request, the authentication server may authenticate the first client device and send a first authentication response to the CP device after the authentication is completed. The first authentication response may be used to indicate that the authentication of the first client device is successful or failed.

[0112] Step 209: The CP device sends a first authentication response to the first client device through the first UP device.

[0113] After receiving the first authentication response, the CP device may send the first authentication response to the first client device via the first UP device. If the first authentication response indicates that the first client device has been successfully authenticated, the CP device allows the first client device to access the network. If the first authentication response indicates that the first client device has failed authentication, the CP device prohibits the first client device from accessing the network.

[0114] Step 210: The CP device manages the first client device using the domain of the first target domain name based on the mapping relationship between the first original domain name and the first target domain name.

[0115] After the first client device accesses the network, the CP device can manage the first client device using the domain of the first target domain name based on the pre-established mapping between the first original domain name and the first target domain name. In other words, the CP device can manage the first client device based on the first configuration information. For example, the CP device 03 can manage the first client device user1 using the first configuration information under domainA.

[0116] Step 211: The CP device exchanges dial-up protocol messages with the second client device through the second UP device.

[0117] After the network access system evolves to CU separation deployment, the second client device can access the network by exchanging dial-up protocol messages with the CP device through the second UP device. The implementation process of step 211 can refer to the above step 205 and will not be repeated here.

[0118] Step 212: The CP device determines that the domain name of the domain to which the second client device belongs is the first original domain name.

[0119] In the embodiment of the present application, the CP device can determine the domain name of the domain to which the second client device belongs during the process of the second client device accessing the network (also referred to as the online process), or after the second client device completes the online process. If the CP device determines that the domain name of the domain to which the second client device belongs is the first original domain name, it can continue to execute Figure 4 The subsequent steps in the flowchart shown in FIG. 212 can be implemented by referring to the above-mentioned step 206 and will not be described in detail here.

[0120] Step 213: The CP device sends a second authentication request to the authentication server.

[0121] The second authentication request includes the username of the second client device, and the username includes the first original domain name. For example, assuming the username of the second client device user2 is user2@domain1, the username included in the second authentication request sent by the CP device to the authentication server to instruct the authentication server to authenticate the second client device user2 is user2@domain1.

[0122] The implementation process of step 213 may refer to the above step 207 and will not be repeated here.

[0123] Step 214: The CP device sends a second authentication response to the second client device through the second UP device.

[0124] After receiving the second authentication request, the authentication server may authenticate the second client device and send a second authentication response to the CP device after the authentication is completed. The second authentication response may be used to indicate that the authentication of the second client device is successful or failed.

[0125] Step 215: The CP device sends a second authentication response to the second client device through the second UP device.

[0126] After receiving the second authentication response, the CP device may send the second authentication response to the second client device via the second UP device. If the second authentication response indicates that the second client device has been successfully authenticated, the CP device allows the second client device to access the network. If the second authentication response indicates that the second client device has failed authentication, the CP device prohibits the second client device from accessing the network.

[0127] Step 216: The CP device manages the second client device using the domain of the second target domain name based on the mapping relationship between the first original domain name and the second target domain name.

[0128] After the second client device accesses the network, the CP device can manage the second client device using the domain of the second target domain name based on the pre-established mapping between the first original domain name and the second target domain name. In other words, the CP device can manage the second client device based on the second configuration information. For example, the CP device 03 can manage the second client device user2 using the second configuration information under domainB.

[0129] The relevant information of the first client device user1 and the second client device user2 during the online process and after the online completion can be shown in Table 1. Referring to Table 1, the first client device user1 goes online from UP1 evolved from BRAS1, and the domain name carried during the online process is domain1. Since the interface through which the first client device user1 goes online on the CP device is the first interface, and the first interface is configured with the configuration domain mapping template test1, the CP device can use the first target domain name domainA to manage the first client device user1 based on the mapping relationship of the domain names recorded in the domain mapping template test1. In addition, the user name carried in the authentication request sent by the CP device to the authentication server for authenticating the first client device user1 is: user1@domain1.

[0130] Table 1

[0131]

[0132] According to the above analysis, the method provided by the embodiment of the present application can ensure that the user name of the client device does not need to be changed during the evolution of the network access system to CU separation deployment. As a result, neither the client device nor the authentication server needs to cooperate with the transformation, thereby effectively improving the evolution efficiency and reducing the operation and maintenance costs of the client device and the authentication server. In addition, because the domain configuration information of the target domain name is the same as the domain configuration information of the original domain name, it can ensure that the services planned and customized based on the user name of the client device can continue to be used. In other words, the impact on the existing network services can be avoided.

[0133] Optionally, the order of the steps of the client device management method provided in the embodiment of the present application can be adjusted appropriately, and the steps can also be increased or decreased accordingly according to the situation. For example, step 203 and step 204, as well as step 212 and step 216 can be deleted according to the situation, that is, in the scenario of domain name conflict, the CP device can also only map the first original domain name in the first BRAS to the first target domain name, without mapping the first original domain name in the second BRAS. Alternatively, step 206 can also be performed after step 207, and step 212 can also be performed after step 213, that is, the CP device can determine the domain name of the domain to which the client device belongs after the client device is online. Any technician familiar with this technical field can easily think of a method of change within the technical scope disclosed in this application, which should be covered by the protection scope of this application, and therefore will not be repeated.

[0134] As another optional implementation, the client device management method provided in the embodiment of the present application can be applied to the CP device in the network access system where the CP and UP are separated. Figure 2CP device 03 shown. Reference Figure 2 The network access system further includes: at least two UP devices connected to the CP device 03, the at least two UP devices including: a first UP device evolved from a first BRAS, and a second UP device evolved from a second BRAS. Furthermore, a domain of a first original domain name is deployed in the first BRAS, and a domain of a second original domain name is deployed in the second BRAS. The first original domain name and the second original domain name are different, but the domain configuration information of the first original domain name is the same as the domain configuration information of the second original domain name.

[0135] After the network access system evolves to CU separation deployment, in order to more clearly implement domain-granular service and user management, there will be a need to integrate domains with different domain names into one domain. Accordingly, the method provided in the embodiment of the present application can also be applied to scenarios where different original domain names in different BRAS need to be mapped to the same target domain name. Figure 5 As shown, the method includes:

[0136] Step 301: A CP device creates a mapping relationship between a first original domain name and a first target domain name.

[0137] The implementation process of step 301 can refer to the above step 201 and will not be repeated here.

[0138] Step 302: The CP device configures a mapping relationship between the first original domain name and the first target domain name on the first interface.

[0139] The implementation process of step 302 can refer to the above step 202 and will not be repeated here.

[0140] Step 303: The CP device creates a mapping relationship between the second original domain name and the first target domain name.

[0141] To map both the first original domain name in the first BRAS and the second original domain name in the second BRAS to the first target domain name, the CP device may also establish a mapping relationship between the second original domain name and the first target domain name. The second original domain name is different from the first target domain name. The implementation process of step 303 can be referenced to step 203 above and will not be repeated here.

[0142] Example, reference Figure 1 and Figure 2 Assume that BRAS1 is deployed with a domain whose first original domain name is domain1, and BRAS2 is deployed with a domain whose second original domain name is domain2, and both domains are configured with the Voice over Internet Protocol (VoIP) service, then the creation command configured by the operation and maintenance personnel on the CP device may include the following command line:

[0143] #

[0144] domain-map-list test1

[0145] domain domain1 mapping domian3

[0146] domain domain2 mapping domian3

[0147] #

[0148] The CP device can create a domain mapping template named test1 based on the command line. The domain mapping template records the mapping relationship between the first original domain name domain1 and the first target domain name domian3, and the mapping relationship between the second original domain name domain2 and the first target domain name domian3.

[0149] Step 304: The CP device configures a mapping relationship between the second original domain name and the first target domain name on the second interface.

[0150] For example, suppose that Figure 1 In the network access system shown, client device user1 accesses the network from BRAS1, and client device user2 accesses the network from BRAS2. Figure 2 In the network access system shown, the first interface of CP device 03 for receiving messages from user 1 is Eth-Trunk 1.1, and the second interface for receiving messages from user 2 is Eth-Trunk 1.2. The operation and maintenance personnel can configure the following command line in CP device 03:

[0151]

[0152] Based on the above command line, CP device 03 can configure a domain mapping template named test1 on Eth-Trunk 1.1 and Eth-Trunk 1.2 respectively. The domain mapping template named test1 records two mapping relationships.

[0153] Based on the above steps 203 and 204, as well as steps 303 and 304, it can be seen that in this embodiment of the present application, each domain mapping template created by the broadband access device can record one or more domain name mapping relationships. Furthermore, the broadband access device can configure the same domain mapping template or different domain mapping templates on different interfaces, which provides high configuration flexibility for this mapping relationship.

[0154] Step 305: The CP device exchanges dial-up protocol messages with the first client device through the first UP device.

[0155] Step 306: The CP device determines that the domain name of the domain to which the first client device belongs is the first original domain name.

[0156] Step 307: The CP device sends a first authentication request to the authentication server.

[0157] Step 308: The authentication server sends a first authentication response to the CP device.

[0158] Step 309: The CP device sends a first authentication response to the first client device through the first UP device.

[0159] Step 310: The CP device manages the first client device using the domain of the first target domain name based on the mapping relationship between the first original domain name and the first target domain name.

[0160] Step 311: The CP device exchanges dial-up protocol messages with the second client device through the second UP device.

[0161] Step 312: The CP device determines that the domain name of the domain to which the second client device belongs is the first original domain name.

[0162] Step 313: The CP device sends a second authentication request to the authentication server.

[0163] Step 314: The CP device sends a second authentication response to the second client device through the second UP device.

[0164] Step 315: The CP device sends a second authentication response to the second client device through the second UP device.

[0165] The implementation process of the above steps 305 to 315 can refer to Figure 4 The descriptions of steps 205 to 215 in the illustrated embodiment will not be repeated here.

[0166] Step 316: The CP device manages the second client device using the domain of the first target domain name based on the mapping relationship between the second original domain name and the first target domain name.

[0167] After the second client device accesses the network, the CP device can manage the second client device using the domain of the first target domain name based on the pre-established mapping between the second original domain name and the first target domain name. In other words, the CP device can manage the second client device based on the first configuration information. For example, the CP device 03 can manage the second client device user2 using the first configuration information under domain3.

[0168] The relevant information of the first client device user1 and the second client device user2 during and after the online process can be shown in Table 2. Referring to Table 2, the second client device user2 goes online from UP2 evolved from BRAS2, and the domain name carried during the online process is domain2. Since the interface through which the second client device user2 goes online on the CP device is the second interface, and the second interface is configured with the configuration domain mapping template test1, the CP device can use the first target domain name domain3 to manage the second client device user2 based on the mapping relationship of the domain names recorded in the domain mapping template test1. In addition, the user name carried in the authentication request sent by the CP device to the authentication server for authenticating the second client device user2 is: user2@domain2.

[0169] Table 2

[0170]

[0171] Based on the above analysis, it can be seen that the method provided by the embodiment of the present application can ensure that when the network access system evolves to a CU-separated deployment, when it is necessary to uniformly manage client devices in domains with different domain names in different BRASs, there is no need to change the user name of the client device. As a result, neither the client device nor the authentication server needs to be modified, thereby reducing the operating and maintenance costs of the client device and the authentication server. In addition, because the domain configuration information of the target domain name is the same as the domain configuration information of the original domain name, it can ensure that services planned and customized based on the user name of the client device can continue to be used. In other words, the impact on existing network services can be avoided.

[0172] Optionally, the order of steps of the client device management method provided in the embodiment of the present application can be adjusted appropriately, and the steps can also be increased or decreased accordingly according to the situation. For example, step 303 and step 304, as well as step 312 and step 316 can be deleted according to the situation. That is, in the above scenario where different original domain names need to be mapped to the same target domain name, the CP device can also only map the first original domain name in the first BRAS to the first target domain name, and the first target domain name can be the same as the second original domain name, thereby eliminating the need to map the second original domain name in the second BRAS. Alternatively, step 306 can also be performed after step 307, and step 312 can also be performed after step 313, that is, the CP device can determine the domain name of the domain to which the client device belongs after the client device is online. Any technician familiar with this technical field can easily think of a method of change within the technical scope disclosed in this application, and it should be covered within the scope of protection of this application, so it will not be repeated.

[0173] As another optional implementation, the client device management method provided in the embodiment of the present application can be applied to the BRAS in the network access system using the hot standby solution. Figure 6 any BRAS in the network access system. The network access system may include n active BRASs and a backup BRAS, and the backup BRAS is used to back up the data in each active BRAS. Wherein, n is an integer greater than 1, and the n active BRASs may include a first BRAS and a second BRAS. Optionally, the n active BRASs and the backup BRAS may both support the redundant user information (RUI) protocol. Since the one backup BRAS can back up the data in n active BRASs, the hot standby solution can also be called an n:1 hot standby solution. If the domain of the first original domain name is deployed in both the first BRAS and the second BRAS, and the configuration information of the domain of the first original domain name in the two BRASs is different, then when the backup BRAS is promoted to the active BRAS, it can only manage the client devices belonging to the domain of the first original domain name based on one configuration information. This will also cause the problem of domain name conflict.

[0174] For example, reference Figure 6 When both BRAS1 and BRAS2 are operating normally, client device user1 goes online through BRAS1, and client device user2 goes online through BRAS2. The domain name of the domain to which client device user1 belongs on BRAS1 is aka, and the configuration information for the domain with aka on BRAS1 includes address pool pool1. BRAS1 can then assign IP address 10.1.1.2 from address pool pool1 to client device user1. The domain name of the domain to which client device user2 belongs on BRAS2 is also aka, and the configuration information for the domain with aka on BRAS2 includes address pool pool2. BRAS2 can then assign IP address 20.1.1.2 from address pool pool2 to client device user2.

[0175] Assume that after the network access system is transformed, BRAS1 and BRAS2 adopt a 2:1 hot standby solution, in which BRAS1 and BRAS2 are both active BRASs, and BRAS3 is the backup BRAS for BRAS1 and BRAS2. When both BRAS1 and BRAS2 fail and are downgraded to standby at the same time, and BRAS3 becomes active, the client devices user1 and user2 will both go online from BRAS3. Since in BRAS3, the configuration information of the domain with the domain name aka contains two address pools pool1 and pool2, when the client device user1 or user2 goes online, BRAS3 will first allocate an IP address to the client device from the address pool pool1. If the addresses in the address pool pool1 are allocated, the IP address will be allocated to the client device from the address pool pool2. As a result, the address pool (i.e., the network segment) to which the IP address of the client device belongs may change. Accordingly, the method provided in the embodiment of the present application can also be applied to a network access system that adopts a hot standby solution, in scenarios where the same original domain name in different BRASs needs to be mapped to different target domain names. For example Figure 7 As shown, the method includes:

[0176] Step 401: A first BRAS creates a mapping relationship between a first original domain name and a first target domain name.

[0177] The first BRAS may create a mapping relationship between the first original domain name and the first target domain name based on the received creation instruction. The creation instruction may be configured by an operation and maintenance personnel, or may be issued by a third-party controller connected to the first BRAS. The first target domain name is different from the first original domain name, and the first configuration information of the domain of the first target domain name is the same as the configuration information of the domain of the first original domain name in the first BRAS.

[0178] Optionally, the domain of the first target domain name can be a new domain created by the first BRAS, or it can be a domain already deployed in the first BRAS. For example, the first BRAS can create a new domain with the domain name of the first target domain name based on the received creation instruction, and can copy the configuration information of the domain of the first original domain name in the first BRAS to the domain of the first target domain name. In addition, after the first BRAS completes the creation of the domain of the first target domain name, it can also delete the configuration information under the domain of the first original domain name, and only retain the first original domain name.

[0179] Example, reference Figure 6 Assuming that a domain with the first original domain name aka is deployed on both BRAS1 and BRAS2, the creation instruction configured by the operation and maintenance personnel on BRAS1 may include the following command line:

[0180] #

[0181] domain-map-list list1

[0182] domain aka mapping aka1

[0183] #

[0184] BRAS1 may create a first domain mapping template named list1 based on the command line. The first domain mapping template records a mapping relationship between the first original domain name aka and the first target domain name aka1.

[0185] Step 402: The first BRAS configures a mapping relationship between the first original domain name and the first target domain name on its backup channel.

[0186] The backup channel is used to synchronize data in the first BRAS with the backup BRAS. For example, the backup channel can be a remote backup service (RBS). By referencing the RBS, the service module in the first BRAS can maintain synchronization of service control data between the primary and backup devices, thereby ensuring that when the primary and backup devices switch, the user services carried by them are quickly and synchronously switched.

[0187] For example, suppose that Figure 6 In the network access system shown, the backup channel used by BRAS1 to synchronize data with BRAS3 is rbs1. The operation and maintenance personnel can configure the following command line in BRAS1:

[0188] #

[0189] remote-backup-service rbs1

[0190] …

[0191] domain-map-list list1

[0192] #

[0193] Based on the above command line, BRAS1 can configure (also referred to as referencing) the first domain mapping template named list1 on the backup channel rbs1.

[0194] Step 403: The second BRAS creates a mapping relationship between the first original domain name and the second target domain name.

[0195] The second BRAS may create a mapping relationship between the first original domain name and the second target domain name based on the received creation instruction. The creation instruction may be configured by an operation and maintenance personnel, or may be issued by a third-party controller connected to the second BRAS. The second target domain name is different from the first original domain name and different from the first target domain name. Furthermore, the second configuration information of the domain of the second target domain name is consistent with the configuration information of the domain of the first original domain name in the second BRAS.

[0196] Optionally, the domain of the second target domain name can be a new domain created by the second BRAS, or can be a domain already deployed in the second BRAS. For example, based on the received creation instruction, the second BRAS can create a new domain with the domain name of the second target domain name, and can copy the configuration information of the domain of the first original domain name in the second BRAS to the domain of the second target domain name. Furthermore, after the second BRAS completes the creation of the domain of the second target domain name, it can also delete the configuration information under the domain of the first original domain name, retaining only the first original domain name.

[0197] Example, reference Figure 6 Assuming that a domain with the first original domain name aka is deployed on both BRAS1 and BRAS2, the creation instruction configured by the operation and maintenance personnel on BRAS2 may include the following command line:

[0198] #

[0199] domain-map-list list2

[0200] domain aka mapping aka2

[0201] #

[0202] BRAS2 may create a second domain mapping template named list2 based on the command line. The second domain mapping template records a mapping relationship between the first original domain name aka and the second target domain name aka2.

[0203] Step 404: The second BRAS configures a mapping relationship between the first original domain name and the second target domain name on its backup channel.

[0204] The backup channel is used to synchronize the data in the second BRAS to the backup BRAS. For example, the backup channel may be an RBS. Figure 6 In the network access system shown, the backup channel used by BRAS2 to synchronize data with BRAS3 is rbs2. The operation and maintenance personnel can configure the following command line in BRAS2:

[0205] #

[0206] remote-backup-service rbs2

[0207] …

[0208] domain-map-list list2

[0209] #

[0210] BRAS2 can configure (also referred to as referencing) a second domain mapping template named list2 on the backup channel rbs2 based on the above command line.

[0211] Step 405: The backup BRAS creates a mapping relationship between the first original domain name and the first target domain name, and a mapping relationship between the first original domain name and the second target domain name.

[0212] The backup BRAS can create a mapping relationship between the first original domain name and the first target domain name, and a mapping relationship between the first original domain name and the second target domain name based on the received creation instruction. The creation instruction can be configured by an operation and maintenance personnel, or can be issued by a third-party controller connected to the backup BRAS. The first original domain name, the first target domain name, and the second target domain name are different from each other. In addition, the first configuration information of the domain of the first target domain name is consistent with the configuration information of the domain of the first original domain name in the first BRAS, and the second configuration information of the domain of the second target domain name is consistent with the configuration information of the domain of the first original domain name in the second BRAS.

[0213] Optionally, the domain of the first target domain name and the domain of the second target domain name can both be new domains created by the backup BRAS, or can also be domains already deployed in the backup BRAS. For example, the backup BRAS can create a new domain with the domain name of the first target domain name based on the received creation instruction, and can copy the configuration information of the domain of the first original domain name in the first BRAS to the domain of the first target domain name. In addition, the backup BRAS can create a new domain with the domain name of the second target domain name, and can copy the configuration information of the domain of the first original domain name in the second BRAS to the domain of the second target domain name. After the backup BRAS completes the creation of the domain of the first target domain name and the domain of the second target domain name, it can also delete the configuration information under the domain of the first original domain name in the first BRAS and the configuration information under the domain of the first original domain name in the second BRAS, and only retain the first original domain name.

[0214] Example, reference Figure 6 Assuming that a domain with the first original domain name aka is deployed on both BRAS1 and BRAS2, the creation instruction configured by the operation and maintenance personnel on BRAS3 may include the following command line:

[0215] #

[0216] domain-map-list list1

[0217] domain aka mapping aka1

[0218] #

[0219] domain-map-list list2

[0220] domain aka mapping aka2

[0221] #

[0222] Based on the command line, BRAS3 can create a first domain mapping template named list1 and a second domain mapping template named list2. The first domain mapping template records the mapping relationship between the first original domain name aka and the first target domain name aka1, and the second domain mapping template records the mapping relationship between the first original domain name aka and the second target domain name aka2.

[0223] Step 406: The backup BRAS configures a mapping relationship between the first original domain name and the first target domain name on its first backup channel, and configures a mapping relationship between the first original domain name and the second target domain name on its second backup channel.

[0224] The first backup channel is used to synchronize data within the first BRAS, and the second backup channel is used to synchronize data within the second BRAS. For example, both the first backup channel and the second backup channel can be RBSs. In a hot standby scenario, the backup BRAS configures different mapping relationships on different backup channels to ensure the independence of resources within the backup channels. Furthermore, configuring mapping relationships at the backup channel granularity facilitates management and maintenance of mapping relationships.

[0225] For example, suppose that Figure 6 In the network access system shown, the first backup channel used by BRAS3 to synchronize data in BRAS1 is rbs1, and the second backup channel used to synchronize data in BRAS2 is rbs2. The operation and maintenance personnel can configure the following command line instructions in BRAS3:

[0226] #

[0227] remote-backup-service rbs1

[0228] domain-map-list list1

[0229] #

[0230] remote-backup-service rbs2

[0231] domain-map-list list2

[0232] #

[0233] Based on the command line, BRAS3 may configure a first domain mapping template named list1 on the first backup channel rbs1 and configure a second domain mapping template named list2 on the second backup channel rbs2.

[0234] Step 407: The backup BRAS exchanges dial-up protocol messages with the first client device.

[0235] If both the first and second BRASs fail, the backup BRAS will need to take over. At this point, the first client device can access the network by exchanging dial-up protocol messages with the backup BRAS. The dial-up protocol can be PPPoE or IPoE, for example.

[0236] Step 408: The backup BRAS determines that the first client device is a client device registered in the first BRAS, and the domain name of the domain to which the first client device belongs is the first original domain name.

[0237] In this embodiment of the present application, the backup BRAS can determine the primary BRAS with which the first client device is registered, as well as the domain name of the domain to which the first client device belongs. For example, the backup BRAS can determine the primary BRAS with which the first client device is registered based on a backup channel for receiving user data of the first client device. The process by which the backup BRAS determines the domain name of the domain to which the first client device belongs can be referred to the description of step 206 above and will not be repeated here.

[0238] If the backup BRAS determines that the first client device is a client device registered in the first BRAS, and the domain name of the domain to which the first client device belongs is the first original domain name, steps 409 to 411 may be continued.

[0239] If the backup BRAS determines that the first client device is not a client device registered with the first BRAS or the second BRAS, or that the domain name of the domain to which the first client device belongs is not the first original domain name, the backup BRAS may handle the situation according to the existing process. The existing process includes: the backup BRAS sending an authentication request to the authentication server to instruct authentication of the first client device; and after the backup BRAS determines, based on the authentication response sent by the authentication server, that the first client device has passed authentication, directly managing the first client device based on the domain name of the first original domain name.

[0240] Step 409: The backup BRAS sends a first authentication request to the authentication server.

[0241] In an embodiment of the present application, after the backup BRAS completes the dial-up protocol message interaction with the first client device, it is also necessary to send a first authentication request to the authentication server to instruct the authentication of the first client device. The first authentication request includes the user name of the first client device, and the user name includes the first original domain name.

[0242] Step 410: The authentication server sends a first authentication response to the backup BRAS.

[0243] After receiving the first authentication request, the authentication server may authenticate the first client device and send a first authentication response to the backup BRAS after the authentication is completed. The first authentication response may be used to indicate that the authentication of the first client device is successful or failed.

[0244] After receiving the first authentication response, the backup BRAS may send the first authentication response to the first client device. If the first authentication response indicates that the first client device has been successfully authenticated, the backup BRAS allows the first client device to access the network. If the first authentication response indicates that the first client device has failed authentication, the backup BRAS prohibits the first client device from accessing the network.

[0245] Step 411: The backup BRAS manages the first client device using the domain of the first target domain name based on the mapping relationship between the first original domain name and the first target domain name.

[0246] After the first client device accesses the network, the backup BRAS can manage the first client device using the domain of the first target domain name based on the pre-established mapping between the first original domain name and the first target domain name. In other words, the backup BRAS can manage the first client device based on the first configuration information. For example, BRAS3 can assign an IP address to the first client device user1 from address pool pool1 under the domain of the first target domain name aka1.

[0247] Step 412: The backup BRAS exchanges dial-up protocol messages with the second client device.

[0248] The implementation process of step 412 can refer to the relevant description of step 407 above, which will not be repeated here.

[0249] Step 413: The backup BRAS determines that the second client device is a client device registered in the second BRAS, and the domain name of the domain to which the second client device belongs is the first original domain name.

[0250] The implementation process of step 413 can refer to the relevant description of step 408 above, which will not be repeated here.

[0251] Step 414: The backup BRAS sends a second authentication request to the authentication server.

[0252] The implementation process of step 414 can refer to the relevant description of step 409 above, which will not be repeated here.

[0253] Step 415: The authentication server sends a second authentication response to the backup BRAS.

[0254] The implementation process of step 415 can refer to the relevant description of step 410 above, which will not be repeated here.

[0255] Step 416: The backup BRAS manages the second client device using the second target domain name based on the mapping relationship between the first original domain name and the second target domain name.

[0256] After the second client device accesses the network, the backup BRAS can manage the second client device using the domain of the second target domain name based on the pre-established mapping between the first original domain name and the second target domain name. In other words, the backup BRAS can manage the second client device based on the second configuration information. For example, BRAS3 can assign an IP address to the second client device user2 from the address pool pool2 under the domain of the second target domain name aka2.

[0257] According to the above analysis, it can be seen that based on the method provided in the embodiment of the present application, it can be ensured that when the network access system adopts the n:1 hot standby solution, there is no need to change the user name of the client device. As a result, neither the client device nor the authentication server needs to cooperate in the transformation, thereby effectively improving the efficiency of the network transformation and reducing the operation and maintenance costs of the client device and the authentication server. In addition, since the domain configuration information of the target domain name is the same as the domain configuration information of the original domain name (including the address pool), it can be ensured that after the client device goes online from the backup BRAS, the IP address assigned by the backup BRAS to the client device still belongs to the original address pool, that is, the network segment to which the client device belongs will not change. Thus, it can be ensured that the services planned and customized based on the user name or IP address of the client device can continue to be used. In other words, the impact on the existing network services can be avoided.

[0258] Optionally, the order of steps of the client device management method provided in the embodiment of the present application can be appropriately adjusted, and the steps can also be increased or decreased according to the situation. For example, step 403 and step 404 can be deleted according to the situation, and the step of creating a mapping relationship between the first original domain name and the second target domain name in step 405, and the step of configuring the mapping relationship between the first original domain name and the second target domain name on the second backup channel in step 406 can both be deleted. That is, only the first original domain name in the first BRAS can be mapped to the first target domain name, without the need to map the first original domain name in the second BRAS. Alternatively, step 408 can also be performed after step 409, and step 413 can also be performed after step 414, that is, the backup BRAS can determine the domain name of the domain to which the client device belongs after the client device is online. Alternatively, steps 407, 409 and 410, as well as steps 412, 414 and 415 can also be deleted according to the situation. That is, if the first and second client devices have already connected to the network before the backup BRAS becomes the active BRAS, then after the backup BRAS takes over the first and second BRAS, it can directly manage the client devices that have already connected to the network based on the domain of the mapped target domain name. Any person skilled in the art can easily conceive of variations within the technical scope disclosed in this application, and these variations are intended to be covered by the scope of protection of this application, and therefore will not be described in detail.

[0259] Optionally, in the method provided in the embodiment of the present application, the broadband access device can also display the mapping relationship between the original domain name and the target domain name it created based on the received viewing instruction, or can send the mapping relationship to the third-party controller to which it is connected for display by the third-party controller. The viewing instruction can be configured directly on the broadband access device by the operation and maintenance personnel, or issued by the third-party controller. In addition, the broadband access device can also record the mapping relationship between the original domain name and the target domain name of the domain to which the client device belongs in the detailed information of the client device. Accordingly, after receiving the viewing instruction, the broadband access device can also display the detailed information of the client device, or can send the mapping relationship to the third-party controller to which it is connected for display by the third-party controller.

[0260] By viewing the mapping relationship between domain names recorded in the broadband access device, it is convenient to manage and maintain the mapping relationship between the domain names.

[0261] For example, Figure 6 In the illustrated network access system, BRAS1 may display detailed information of the first client device user1 based on the received viewing instruction, including:

[0262] Domain:aka1

[0263] IP address:10.1.1.2(pool1)

[0264] Domain: aka.

[0265] The detailed information of the first client device user1 includes the first original domain name of the domain to which the first client device user1 belongs: aka, the first target domain name aka1 mapped to the first original domain name, and the IP address 10.1.1.2 of the first client device user1, which belongs to the address pool pool1.

[0266] Based on the received viewing instruction, the detailed information of the second client device user2 displayed by BRAS2 may include:

[0267] Domain:aka2

[0268] IP address:20.1.1.2(pool2)

[0269] Domian: aka.

[0270] Based on the received viewing instruction, the detailed information displayed by the BRAS3 about the first client device user1 and the second client device user2 may include:

[0271] user1:

[0272] Domain:aka1

[0273] IP address:10.1.1.2(pool1)

[0274] user2:

[0275] Domain:aka2

[0276] IP address:20.1.1.2(pool2)

[0277] Domian: aka.

[0278] In summary, the embodiment of the present application provides a method for managing client devices, and the broadband access device can use the domain of the target domain name to manage the client devices belonging to the domain of the original domain name based on the mapping relationship between the created original domain name and the target domain name. Since in scenarios where there is a need to modify the domain name (such as scenarios that evolve into CU separation deployment, or scenarios where a hot standby solution is newly added), the broadband access device can map the original domain name to a target domain name that is different from the original domain name, the client device does not need to modify its user name, and the authentication server does not need to modify the user name of the client device it stores. In this way, the problem of a large amount of data modification caused by directly modifying the domain name can be avoided, and the operation and maintenance costs of the client device and the authentication server are reduced.

[0279] Because the domain configuration information of the mapped target domain name is identical to that of the original domain name (including the address pool), services planned and customized based on the client device's username or IP address can continue to function. This effectively improves the flexibility of domain-based client device management without impacting existing network services.

[0280] Figure 8 This is a schematic diagram of the structure of a broadband access device provided by an embodiment of the present application. The broadband access device can be applied to Figure 1 , Figure 2 ,or Figure 6 The network access system shown in FIG. For example, the broadband access device can be Figure 2 CP device 03 shown, or Figure 6 Any BRAS shown. Figure 8 As shown, the broadband access device may include:

[0281] The first creation module 501 is used to create a mapping relationship between a first original domain name and a first target domain name, where the first target domain name is different from the first original domain name. The implementation of the functions of the first creation module 501 can refer to the relevant description of the above steps 101, 201, 301 or 401.

[0282] The first determining module 502 is configured to determine that the domain name of the domain to which the first client device belongs is the first original domain name. The implementation of the function of the first determining module 502 can refer to the relevant description of the above steps 102, 206, 306 or 408.

[0283] The first management module 503 is configured to manage the first client device using the domain of the first target domain name based on the mapping relationship between the first original domain name and the first target domain name. The implementation of the functions of the first management module 503 can refer to the relevant description of the above steps 103, 210, 310, or 411.

[0284] Optionally, the first configuration information of the domain of the first target domain name in the broadband access device is the same as the configuration information of the domain of the first original domain name in the first network device.

[0285] As an optional implementation, the broadband access device is a CP device in a CU-separated network access system, such as Figure 2 As shown, the network access system further includes at least two UP devices connected to the CP device 03, the first network device is a first BRAS, and the at least two UP devices may include: a first UP device evolved from the first BRAS, and a second UP device evolved from the second BRAS. In this implementation, the first management module 503 may be used to:

[0286] Determine that the first client device goes online from the first UP device; and manage the first client device using the first configuration information based on a mapping relationship between the first original domain name and the first target domain name.

[0287] Optionally, the first configuration information is different from the configuration information of the domain of the first original domain name in the second BRAS. Figure 9 As shown, the broadband access device may further include:

[0288] The second creation module 504 is configured to create a mapping relationship between the first original domain name and a second target domain name, where the second target domain name is different from the first target domain name and the first original domain name, and the second configuration information of the domain of the second target domain name is the same as the configuration information of the domain of the first original domain name in the second BRAS. The implementation of the functions of the second creation module 504 may refer to the description of step 203 above.

[0289] The second determining module 505 is configured to determine that the second client device is online from the second UP device and the domain name of the domain to which the second client device belongs is the first original domain name. The implementation of the second determining module 505 may refer to the description of step 212 above.

[0290] The second management module 506 is configured to manage the second client device using the second configuration information based on the mapping relationship between the first original domain name and the second target domain name. The implementation of the second management module 506 can refer to the description of step 216 above.

[0291] Optionally, the first configuration information is the same as the configuration information of the second original domain name in the second BRAS, and the second original domain name is different from the first original domain name; Figure 9 As shown, the broadband access device also includes:

[0292] The second creation module 504 is configured to create a mapping relationship between the second original domain name and the first target domain name. The implementation of the second creation module 504 can refer to the description of step 303 above.

[0293] The second determining module 505 is configured to determine that the second client device is online from the second UP device and the domain name of the domain to which the second client device belongs is the second original domain name. The implementation of the second determining module 505 can refer to the description of step 312 above.

[0294] The second management module 506 is configured to manage the second client device using the domain of the first target domain name based on the mapping relationship between the second original domain name and the first target domain name. The implementation of the second management module 506 can refer to the description of step 316 above.

[0295] Alternatively, as Figure 9 As shown, the broadband access device may further include:

[0296] Configuration module 507 is configured to configure a mapping relationship between the first original domain name and the first target domain name on a first interface of the CP device, where the first interface is configured to receive messages from the first client device. The implementation of the functions of configuration module 507 may refer to the description of steps 202 or 302 above. The implementation of the functions of configuration module 507 may also refer to the description of steps 204 or 304 above.

[0297] As another optional implementation, the broadband access device is a first BRAS in a network access system, and the first network device is the first BRAS. Figure 6The network access system may further include a second BRAS and a backup BRAS, the backup BRAS being configured to back up data in the first BRAS and the second BRAS. The first configuration information is different from the domain configuration information of the first original domain name in the second BRAS; the backup BRAS includes a domain whose domain name is the first target domain name, and the domain configuration information of the first target domain name in the backup BRAS is the same as the first configuration information.

[0298] In this implementation, if Figure 9 As shown, the broadband access device may further include:

[0299] Configuration module 507 is used to configure the mapping relationship between the first original domain name and the first target domain name on the backup channel of the first BRAS, and the backup channel is used to synchronize the data in the first BRAS to the backup BRAS. The function implementation of configuration module 507 can refer to the relevant description of step 402 above.

[0300] As another optional implementation, the broadband access device is a backup BRAS in a network access system, the first network device is a first BRAS in the network access system, the network access system further includes a second BRAS, the backup BRAS is used to back up data in the first BRAS and the second BRAS; the first configuration information is different from the domain configuration information of the first original domain name in the second BRAS; the first management module 503 can be used to:

[0301] Determine that the first client device is a client device registered in the first BRAS; manage the first client device using the first configuration information based on the mapping relationship between the first original domain name and the first target domain name. The implementation of the function of the first management module 503 can refer to the relevant description of the above step 411.

[0302] In this implementation, if Figure 9 As shown, the broadband access device may further include:

[0303] The second creation module 504 is configured to create a mapping relationship between the first original domain name and a second target domain name, where the second target domain name is different from the first target domain name and the first original domain name, and the second configuration information of the domain of the second target domain name in the backup BRAS is the same as the configuration information of the domain of the first original domain name in the second BRAS. The implementation of the functions of the second creation module 504 may refer to the description of step 405 above.

[0304] The second determining module 505 is configured to determine that the second client device is a client device registered in the second BRAS and the domain name of the domain to which the second client device belongs is the first original domain name. The implementation of the function of the second determining module 505 may refer to the description of step 413 above.

[0305] The second management module 506 is configured to manage the second client device using the second configuration information based on the mapping relationship between the first original domain name and the second target domain name. The implementation of the second management module 506 can refer to the description of step 416 above.

[0306] Alternatively, as Figure 9 As shown, the broadband access device further includes a configuration module 507, which can be used to:

[0307] A mapping relationship between the first original domain name and the first target domain name is configured on a first backup channel of the backup BRAS, where the first backup channel is used to synchronize data in the first BRAS; and a mapping relationship between the first original domain name and the second target domain name is configured on a second backup channel of the backup BRAS, where the second backup channel is used to synchronize data in the second BRAS. The functional implementation of configuration module 507 may refer to the description of step 406 above.

[0308] Optionally, the first creation module 501 may be configured to: based on the received domain creation instruction, create a domain whose domain name is a mapping relationship between the first original domain name, the first target domain name, and the first original domain name.

[0309] Alternatively, as Figure 9 As shown, the broadband access device may further include:

[0310] The sending module 508 is configured to send an authentication request to the authentication server, instructing the authentication of the first client device. The authentication request includes the username of the first client device, and the username includes the first original domain name. The implementation of the functions of the sending module 508 can refer to the description of steps 207, 307, or 409 above. The implementation of the functions of the sending module 508 can also refer to the description of steps 213, 313, or 414 above.

[0311] In summary, an embodiment of the present application provides a broadband access device that can manage client devices belonging to the domain of the original domain name based on the mapping relationship between the created original domain name and the target domain name using the domain of the target domain name. Since, in a scenario where there is a need to modify the domain name, the broadband access device can map the original domain name to a target domain name that is different from the original domain name, the client device does not need to modify its user name, and the authentication server does not need to modify the user name of the client device it stores. In this way, the problem of a large amount of data modification caused by directly modifying the domain name can be avoided, reducing the operating and maintenance costs of the client device and the authentication server.

[0312] Because the domain configuration information of the mapped target domain name is identical to that of the original domain name (including the address pool), services planned and customized based on the client device's username or IP address can continue to function. This effectively improves the flexibility of domain-based client device management without impacting existing network services.

[0313] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the broadband access device and each module described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0314] It should be understood that the broadband access device provided in the embodiments of the present application can also be implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD can be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof. The client device management method provided in the above method embodiment can also be implemented through software. When the client device management method provided in the above method embodiment is implemented through software, each module in the broadband access device can also be a software module.

[0315] Figure 10 1 is a schematic diagram of the structure of a broadband access device provided in an embodiment of the present application. The broadband access device 1000 can be applied to a network access system. For example, the broadband access device 1000 can be a BRAS in a network access system, or a CP device in a CU-separated network access system. Specifically, the broadband access device can be applied to Figure 1 , Figure 2 ,or Figure 6 The network access system shown in FIG. For example, the broadband access device can be Figure 2 CP device 03 shown, or Figure 6 Any BRAS shown. Figure 10 , the broadband access device 1000 may include: a processor 1001, a memory 1002, a transceiver 1003 and a bus 1004. The bus 1004 is used to connect the processor 1001, the memory 1002 and the transceiver 1003. Communication with other devices can be achieved through the transceiver 1003 (which can be wired or wireless). The memory 1002 stores a computer program, which is used to implement various application functions. When Figure 8 or Figure 9 When the modules in the broadband access device shown are implemented in the form of software modules, the programs corresponding to these software modules can be stored in the memory 1002 of the broadband access device 1000 .

[0316] It should be understood that in the embodiment of the present application, the processor 1001 may be a CPU, and the processor 1001 may also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), GPUs, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0317] The memory 1002 may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DRRAM).

[0318] In addition to the data bus, the bus 1004 may also include a power bus, a control bus, a status signal bus, etc. However, for the sake of clarity, various buses are labeled as the bus 1004 in the figure.

[0319] In a specific embodiment, the processor 1001 in the broadband access device 1000 is used to create a mapping relationship between a first original domain name and a first target domain name, where the first target domain name is different from the first original domain name; determine that the domain name of the domain to which the first client device belongs is the first original domain name; and based on the mapping relationship between the first original domain name and the first target domain name, use the domain of the first target domain name to manage the first client device. For the detailed processing process of the processor 1001, please refer to the above method embodiment. For example, you can refer to Figure 3 In the illustrated embodiment, steps 101 to 103 are Figure 4 In the embodiment shown, steps 201 to 207, steps 209 to 213, steps 215 and 216 are referred to as Figure 5 Steps 301 to 307, steps 309 to 313, steps 315 and 316, and Figure 7The detailed description of steps 401 to 409, steps 411 to 414, and step 416 in the illustrated embodiment will not be repeated here.

[0320] An embodiment of the present application further provides a computer-readable storage medium having instructions stored therein. When the computer-readable storage medium is run on a computer, the computer is enabled to execute the client device management method provided in the above method embodiment.

[0321] An embodiment of the present application further provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the client device management method provided by the above method embodiment.

[0322] refer to Figure 2 The embodiment of the present application provides a CU-separated network access system, which includes: a CP device 03, and a plurality of UP devices connected to the CP device 03. The CP device 03 may include: Figures 8 to 10 Any broadband access device shown.

[0323] refer to Figure 6 , the embodiment of the present application provides another network access system, which includes: multiple active BRASs and at least one backup BRAS. Figure 6 In the network access system shown, BRAS1 and BRAS2 are both active BRASs, and BRAS3 is a backup BRAS.

[0324] Among them, at least one master BRAS may include: Figures 8 to 10 For any broadband access device shown, the backup BRAS may include: Figures 8 to 10 Any broadband access device shown.

[0325] The above embodiments can be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented using software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded or executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that contains one or more available media sets. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium. The semiconductor medium can be a solid state drive (SSD).

[0326] In this application, the terms "first," "second," and the like are used to distinguish between identical or similar items with substantially the same role and function. It should be understood that "first," "second," and "nth" do not have a logical or temporal dependency, nor do they limit quantity or order of execution. It should also be understood that although the following description uses the terms "first," "second," and the like to describe various elements, these elements should not be limited by these terms. These terms are simply used to distinguish one element from another. For example, a first BRAS could be referred to as a second BRAS, and similarly, a second BRAS could be referred to as a first BRAS, without departing from the scope of the various described examples.

[0327] In this application, the term "at least one" means one or more, and the term "plurality" means two or more. For example, a plurality of UP devices refers to two or more UP devices. The terms "system" and "network" are often used interchangeably herein.

[0328] The above are merely optional embodiments of the present application, but the scope of protection of the present application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and such modifications or substitutions should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for managing a client device, characterized in that: Applied to broadband access equipment, the method includes: Creating a mapping relationship between a first original domain name and a first target domain name, where the first target domain name is different from the first original domain name; Determining that the domain name of the domain to which the first client device belongs is the first original domain name; Based on a mapping relationship between the first original domain name and the first target domain name, using the first target domain name to manage the first client device; The broadband access device is used to distinguish different client device groups through different domains, and client devices in the same domain have the same service attributes.

2. The method according to claim 1, characterized in that The first configuration information of the domain of the first target domain name in the broadband access device is the same as the configuration information of the domain of the first original domain name in the first network device.

3. The method according to claim 2, characterized in that The broadband access device is a CP device in a network access system in which the control plane CP and the user plane UP are separated. The network access system also includes at least two UP devices connected to the CP device. The first network device is a first broadband remote access server BRAS. The at least two UP devices include: a first UP device evolved from the first BRAS, and a second UP device evolved from the second BRAS.

4. The method according to claim 3, characterized in that The managing the first client device using the domain of the first target domain name based on the mapping relationship between the first original domain name and the first target domain name includes: Determining that the first client device goes online from the first UP device; Based on a mapping relationship between the first original domain name and the first target domain name, the first configuration information is used to manage the first client device.

5. The method according to claim 4, characterized in that The first configuration information is different from the domain configuration information of the first original domain name in the second BRAS; the method further includes: Creating a mapping relationship between the first original domain name and a second target domain name, where the second target domain name is different from the first target domain name and different from the first original domain name, and second configuration information of the domain of the second target domain name is the same as the configuration information of the domain of the first original domain name in the second BRAS; Determining that a second client device goes online from the second UP device, and the domain name of the domain to which the second client device belongs is the first original domain name; Based on the mapping relationship between the first original domain name and the second target domain name, the second configuration information is used to manage the second client device.

6. The method according to claim 4, characterized in that The first configuration information is the same as the domain configuration information of the second original domain name in the second BRAS, and the second original domain name is different from the first original domain name; the method further includes: Creating a mapping relationship between the second original domain name and the first target domain name; Determining that a second client device goes online from the second UP device, and the domain name of the domain to which the second client device belongs is the second original domain name; Based on a mapping relationship between the second original domain name and the first target domain name, the first configuration information is used to manage the second client device.

7. The method according to any one of claims 3 to 6, characterized in that: The method further comprises: A mapping relationship between the first original domain name and the first target domain name is configured on a first interface of the CP device, where the first interface is used to receive a message from the first client device.

8. The method according to claim 2, characterized in that The broadband access device is a first BRAS in a network access system, the first network device is the first BRAS, the network access system further includes a second BRAS and a backup BRAS, the backup BRAS is configured to back up data in the first BRAS and the second BRAS; the first configuration information is different from domain configuration information of the first original domain name in the second BRAS; The backup BRAS includes a domain whose domain name is the first target domain name, and configuration information of the domain of the first target domain name in the backup BRAS is the same as the first configuration information.

9. The method according to claim 8, characterized in that The method further comprises: A mapping relationship between the first original domain name and the first target domain name is configured on a backup channel of the first BRAS, where the backup channel is used to synchronize data in the first BRAS to the backup BRAS.

10. The method according to claim 2, characterized in that The broadband access device is a backup BRAS in a network access system, the first network device is a first BRAS in the network access system, the network access system further includes a second BRAS, the backup BRAS is configured to back up data in the first BRAS and the second BRAS; the first configuration information is different from domain configuration information of the first original domain name in the second BRAS; The managing the first client device using the domain of the first target domain name based on the mapping relationship between the first original domain name and the first target domain name includes: Determining that the first client device is a client device registered in the first BRAS; Based on a mapping relationship between the first original domain name and the first target domain name, the first configuration information is used to manage the first client device.

11. The method according to claim 10, characterized in that The method further comprises: Creating a mapping relationship between the first original domain name and a second target domain name, where the second target domain name is different from the first target domain name and different from the first original domain name, and the second configuration information of the domain of the second target domain name in the backup BRAS is the same as the configuration information of the domain of the first original domain name in the second BRAS; Determining that the second client device is a client device registered in the second BRAS, and the domain name of the domain to which the second client device belongs is the first original domain name; Based on the mapping relationship between the first original domain name and the second target domain name, the second configuration information is used to manage the second client device.

12. The method according to claim 11, characterized in that The method further comprises: Configuring a mapping relationship between the first original domain name and the first target domain name on a first backup channel of the backup BRAS, where the first backup channel is used to synchronize data in the first BRAS; A mapping relationship between the first original domain name and the second target domain name is configured on a second backup channel of the backup BRAS, and the second backup channel is used to synchronize data in the second BRAS.

13. The method according to any one of claims 1 to 6, characterized in that: The creating a mapping relationship between the first original domain name and the first target domain name includes: Based on the received creation instruction, a mapping relationship between the first original domain name and the first target domain name is created.

14. The method according to any one of claims 1 to 6, characterized in that: The method further comprises: An authentication request for instructing to authenticate the first client device is sent to an authentication server, where the authentication request includes a user name of the first client device, and the user name includes the first original domain name.

15. A broadband access device, characterized in that: The broadband access device includes: a first creation module, configured to create a mapping relationship between a first original domain name and a first target domain name, where the first target domain name is different from the first original domain name; A first determining module, configured to determine that the domain name of the domain to which the first client device belongs is the first original domain name; a first management module, configured to manage the first client device using the domain of the first target domain name based on a mapping relationship between the first original domain name and the first target domain name; The broadband access device is used to distinguish different client device groups through different domains, and client devices in the same domain have the same service attributes.

16. The broadband access device according to claim 15, characterized in that: The first configuration information of the domain of the first target domain name in the broadband access device is the same as the configuration information of the domain of the first original domain name in the first network device.

17. The broadband access device according to claim 16, characterized in that: The broadband access device is a CP device in a network access system in which CP and UP are separated. The network access system also includes at least two UP devices connected to the CP device. The first network device is a first BRAS. The at least two UP devices include: a first UP device evolved from the first BRAS, and a second UP device evolved from the second BRAS.

18. The broadband access device according to claim 17, wherein: The first management module is configured to: Determining that the first client device goes online from the first UP device; Based on a mapping relationship between the first original domain name and the first target domain name, the first configuration information is used to manage the first client device.

19. The broadband access device according to claim 18, characterized in that: The first configuration information is different from the domain configuration information of the first original domain name in the second BRAS; the broadband access device further includes: a second creation module, configured to create a mapping relationship between the first original domain name and a second target domain name, where the second target domain name is different from the first target domain name and the first original domain name, and second configuration information of the domain of the second target domain name is the same as the configuration information of the domain of the first original domain name in the second BRAS; A second determining module is configured to determine that a second client device goes online from the second UP device, and the domain name of the domain to which the second client device belongs is the first original domain name; The second management module is configured to manage the second client device using the second configuration information based on a mapping relationship between the first original domain name and the second target domain name.

20. The broadband access device according to claim 18, wherein: The first configuration information is the same as the domain configuration information of the second original domain name in the second BRAS, and the second original domain name is different from the first original domain name; The broadband access device further includes: A second creation module, configured to create a mapping relationship between the second original domain name and the first target domain name; A second determining module is configured to determine that a second client device goes online from the second UP device, and the domain name of the domain to which the second client device belongs is the second original domain name; The second management module is configured to manage the second client device by using the first configuration information based on a mapping relationship between the second original domain name and the first target domain name.

21. The broadband access device according to any one of claims 17 to 20, characterized in that: The broadband access device further includes: A configuration module is configured to configure a mapping relationship between the first original domain name and the first target domain name on a first interface of the CP device, where the first interface is used to receive a message from the first client device.

22. The broadband access device according to claim 16, wherein: The broadband access device is a first BRAS in a network access system, the first network device is the first BRAS, the network access system further includes a second BRAS and a backup BRAS, the backup BRAS is configured to back up data in the first BRAS and the second BRAS; the first configuration information is different from domain configuration information of the first original domain name in the second BRAS; The backup BRAS includes a domain whose domain name is the first target domain name, and configuration information of the domain of the first target domain name in the backup BRAS is the same as the first configuration information.

23. The broadband access device according to claim 22, characterized in that: The broadband access device further includes: A configuration module is used to configure a mapping relationship between the first original domain name and the first target domain name on a backup channel of the first BRAS, where the backup channel is used to synchronize data in the first BRAS to the backup BRAS.

24. The broadband access device according to claim 16, wherein: The broadband access device is a backup BRAS in a network access system, the first network device is a first BRAS in the network access system, the network access system further includes a second BRAS, the backup BRAS is configured to back up data in the first BRAS and the second BRAS; the first configuration information is different from configuration information of the domain of the first original domain name in the second BRAS; the first management module is configured to: Determining that the first client device is a client device registered in the first BRAS; Based on a mapping relationship between the first original domain name and the first target domain name, the first configuration information is used to manage the first client device.

25. The broadband access device according to claim 24, characterized in that: The broadband access device further includes: a second creation module, configured to create a mapping relationship between the first original domain name and a second target domain name, where the second target domain name is different from the first target domain name and different from the first original domain name, and second configuration information of the domain of the second target domain name in the backup BRAS is the same as the configuration information of the domain of the first original domain name in the second BRAS; a second determining module, configured to determine that the second client device is a client device registered in the second BRAS, and that the domain name of the domain to which the second client device belongs is the first original domain name; The second management module is configured to manage the second client device using the second configuration information based on a mapping relationship between the first original domain name and the second target domain name.

26. The broadband access device according to claim 25, characterized in that: The broadband access device further includes a configuration module, which is configured to: Configuring a mapping relationship between the first original domain name and the first target domain name on a first backup channel of the backup BRAS, where the first backup channel is used to synchronize data in the first BRAS; A mapping relationship between the first original domain name and the second target domain name is configured on a second backup channel of the backup BRAS, and the second backup channel is used to synchronize data in the second BRAS.

27. The broadband access device according to any one of claims 15 to 20, characterized in that: The first creation module is used to: Based on the received domain creation instruction, a domain is created whose domain name is a mapping relationship between the first original domain name, the first target domain name, and the first original domain name.

28. The broadband access device according to any one of claims 15 to 20, characterized in that: The broadband access device further includes: A sending module is used to send an authentication request for instructing to authenticate the first client device to an authentication server, wherein the authentication request includes a user name of the first client device, and the user name includes the first original domain name.

29. A computer-readable storage medium, characterized in that The computer-readable storage medium stores instructions, and when the instructions are executed on a computer, the computer is caused to execute the method according to any one of claims 1 to 14.

30. A network access system with separated CP and UP, characterized in that: The system includes: a CP device, and a plurality of UP devices connected to the CP device; The CP device includes the broadband access device according to any one of claims 15 to 21, or includes the broadband access device according to claim 27 or 28.

31. A network access system, characterized in that: The system includes: a plurality of active BRASs and at least one backup BRAS; Wherein, at least one of the primary BRASs includes the broadband access device according to claim 15, or claim 16, or claim 22, or claim 23, or claim 27, or claim 28; The backup BRAS includes the broadband access device according to claim 15, claim 16, or any one of claims 24 to 28.

Images