+

WO2018103665A1 - Procédé, appareil et système de gestion de dispositifs basés sur un l2tp - Google Patents

Procédé, appareil et système de gestion de dispositifs basés sur un l2tp Download PDF

Info

Publication number
WO2018103665A1
WO2018103665A1 PCT/CN2017/114824 CN2017114824W WO2018103665A1 WO 2018103665 A1 WO2018103665 A1 WO 2018103665A1 CN 2017114824 W CN2017114824 W CN 2017114824W WO 2018103665 A1 WO2018103665 A1 WO 2018103665A1
Authority
WO
WIPO (PCT)
Prior art keywords
lns
tunnel
unavailable
interface
tunnel interface
Prior art date
Application number
PCT/CN2017/114824
Other languages
English (en)
Chinese (zh)
Inventor
朱筠
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2018103665A1 publication Critical patent/WO2018103665A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/12—Avoiding congestion; Recovering from congestion
    • H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0892—Network architectures or network communication protocols for network security for authentication of entities by using authentication-authorization-accounting [AAA] servers or protocols

Definitions

  • the embodiments of the present invention relate to the field of network technologies, and in particular, to a device management method, device, and system based on L2TP.
  • VPDN Virtual Private Dial-up Network
  • L2TP Layer 2 Tunneling Protocol
  • LNS L2TP Network Server
  • the LAC is used to initiate a tunnel establishment request to the LNS.
  • the LNS is used to receive the LAC.
  • the tunnel establishment request sends a setup response to the LAC. After receiving the setup response sent by the LNS, the LAC can successfully establish an L2TP tunnel to the LNS.
  • FIG. 1A is a network architecture diagram of an L2TP protocol.
  • the network architecture of the L2TP protocol generally includes an LAC side 10 and an LNS side 20.
  • the LAC side 10 includes multiple LAC11 and AAA (Authentication, Authorization, Accounting, Authentication, and Accounting) servers 12, and the AAA server 12 is connected to the multiple LACs 11 to provide authentication, authorization, and accounting for each LAC11.
  • the LNS side 20 includes a plurality of LNSs 21.
  • each LNS 21 can include at least one tunnel interface through which an L2TP tunnel can be established.
  • a tunnel interface is a logical interface or a physical interface created by the LNS to establish an L2TP tunnel.
  • a loopback interface can be used as the source address or destination address of an L2TP tunnel.
  • the AAA server 12 can obtain the identifier of at least one tunnel interface included in each LNS 21 of the LNS side 20, obtain the identifiers of the multiple tunnel interfaces, and store the identifiers of the multiple tunnel interfaces in the In the interface information list.
  • the identifier of each tunnel interface is used to indicate a tunnel interface and an LNS to which the tunnel interface belongs.
  • the AAA server 12 can send the interface information list to the LAC11, and the LAC11 can select the LNS21 and the tunnel interface for establishing the tunnel based on the multiple tunnel interface information in the interface information list. And initiate a tunnel establishment request to the selected LNS21. After receiving the request of the LAC11, the selected LNS21 can establish an L2TP tunnel from the selected tunnel interface to the LAC11.
  • the LAC sends the LNS and the tunnel interface of the LNS based on the interface information list.
  • the LNS or tunnel interface may not meet the working requirements, and the selected LNS cannot establish a tunnel or establish a poor tunnel quality after receiving the tunnel request. Therefore, there is a need for an L2TP-based device management method to prevent the LAC from selecting an LNS or tunnel interface that does not meet the operational requirements.
  • an embodiment of the present invention provides a device management method, device, and system based on L2TP.
  • the technical solution is as follows:
  • the first aspect provides an L2TP-based device management method, which is applied to a controller, where the controller is connected to multiple LNSs on the LNS side of the L2TP network server, and the controller and the L2TP access concentrator LAC side are respectively connected.
  • Authentication and authorization and accounting AAA server connection the method includes:
  • the device information including device identifiers and device state information corresponding to the LNS;
  • the AAA server And sending, by the AAA server, a first notification message, where the first notification message carries an identifier of the tunnel interface of the unavailable LNS, where the first notification message is used to notify the AAA server to use the tunnel of the unavailable LNS.
  • the ID of the interface is removed from the list of stored interface information.
  • a controller is introduced between the LAC side and the LNS side, and the controller can monitor the device of each LNS on the LNS side by receiving device information of each LNS from multiple LNSs on the LNS side.
  • the first notification message of the identifier of the tunnel interface carrying the unavailable LNS is sent to the AAA server on the LAC side to notify the AAA server that the LNS is unavailable.
  • the identifier of the tunnel interface is deleted from the stored interface information list, and the updated interface information list is obtained.
  • the LNS corresponding to the identifier of all the tunnel interfaces included in the updated interface information list is available, and each tunnel interface of the available LNS is also available, because the updated interface information list has deleted the identifier of the tunnel interface of the LNS. Available, therefore, when the LAC selects the LNS and the tunnel interface based on the updated interface information list, any LNS and any tunnel interface selected are also available, thereby solving the problem that the selected LNS or tunnel interface may not meet the working conditions.
  • the problem that the tunnel cannot be established or the quality of the established tunnel is poor, and the success rate and stability of the tunnel establishment are improved.
  • the device status information includes at least one of fault information, CPU utilization of the central processing unit, memory usage, total traffic of the outbound interface carrying the L2TP tunnel, and the total amount of users of the total bearer;
  • the target LNS is determined to be an unavailable LNS, and the target LNS is any one of the plurality of LNSs;
  • the target LNS is determined to be an unavailable LNS
  • the identifier of the tunnel interface of the unavailable LNS refers to the label of all the tunnel interfaces of the unavailable LNS. knowledge.
  • the controller may determine each device status information based on the fault information of each LNS, the CPU usage of the central processing unit, the memory usage, the total traffic of the outbound interface carrying the L2TP tunnel, and the total amount of users. Whether the LNSs are available, and the identifiers of all tunnel interfaces of the unavailable LNS are used as the identifiers of the tunnel interfaces of the unavailable LNSs that need to be deleted.
  • the AAA server is notified to delete the identifier of all the tunnel interfaces of the LNS from the interface information list, so that the LNS fault state is quickly perceived and avoided.
  • the LAC still sends a tunnel establishment failure request to the LNS.
  • the AAA server When the at least one of the CPU usage, the memory usage, the total traffic of the outbound interface carrying the L2TP tunnel, and the total number of users of the total bearer is greater than the threshold, the AAA server is notified to identify the identifiers of all the tunnel interfaces of the LNS.
  • the LNS load status is quickly deleted, and some LNSs that are in the live network are overloaded. Some LNS access users are very small. This LNS load is unbalanced and resource allocation is not. Reasonable problems, thus ensuring the balance of LNS load and improving the stability of tunnel establishment.
  • the method further includes:
  • An identifier of all tunnel interfaces is used to notify the AAA server to add an identifier of all tunnel interfaces of the available LNS in the interface information list.
  • the second notification message may be sent to the AAA server, indicating that the AAA server will restore the identifier of the tunnel interface that is restored to the available LNS. To the list of interface information. In this way, the LNS after the problem is removed can be re-introduced into the L2TP network to share the load and achieve the purpose of balancing the load.
  • the device information further includes identifiers and tunnel interface state information corresponding to at least one tunnel interface included in the LNS;
  • the first notification message carries an identifier of the unavailable tunnel interface in the unavailable LNS, and the first notification message is used to notify the AAA server to identify the identifier of the unavailable tunnel interface in the unavailable LNS.
  • the list of stored interface information is deleted.
  • the tunnel interface state information includes at least one of a quantity of users carried by the corresponding tunnel and a traffic of the tunnel interface;
  • the determining, according to the identifier of the at least one tunnel interface and the tunnel interface state information included in the device information of each of the plurality of LNSs, determining that an unavailable tunnel interface exists in the multiple LNSs LNS including:
  • the target tunnel interface is determined as An unavailable tunnel interface in the LNS, and determining the LNS as an LNS having an unavailable tunnel interface, where the target tunnel is connected
  • the interface is any one of the at least one tunnel interface included in the LNS;
  • the controller may also monitor the state of each tunnel interface in the at least one tunnel interface included in the LNS.
  • the tunnel interface may be used.
  • the tunnel interface is determined to be unavailable, and the AAA server is instructed to remove the identifier of the unavailable tunnel interface from the interface information list. In this way, for each LNS, only the overloaded tunnel interface in the LNS can be excluded, and the tunnel interface that is not overloaded is still retained, which realizes load balancing on the tunnel interface granularity and improves the accuracy.
  • the method further includes:
  • the third notification message may also be sent to the AAA server, indicating that the AAA server will restore the identifier of the available tunnel interface. To the list of interface information. In this way, the tunnel interface after the problem is re-introduced into the L2TP network to share the load and achieve load balancing on the tunnel interface granularity.
  • the receiving device information from each of the plurality of LNSs includes:
  • Device information from each of the plurality of LNSs is received through a Simple Network Management Protocol SNMP.
  • SNMP Simple Network Management Protocol
  • the device information of multiple LNSs on the LNS side is obtained by using NETCONF or SNMP, and the accuracy and efficiency of acquiring LNS device information are improved.
  • the method before the sending the first notification to the AAA server, the method further includes:
  • the sending the first notification message to the AAA server includes:
  • a Radius connection may be established between the controller and the AAA server, and the first notification message is sent to the AAA server by using the Radius connection, that is, the interaction of the notification message between the controller and the AAA server is implemented based on the Radius protocol.
  • the second aspect provides a device management method based on the Layer 2 Tunneling Protocol (L2TP), which is characterized in that, in the AAA server for authentication and authorization and accounting, the AAA server and the controller and the L2TP access concentrator LAC side
  • the LACs are respectively connected, and the controllers are respectively connected to multiple LNSs on the LNS side of the L2TP network server.
  • the method includes:
  • the controller Receiving, by the controller, a first notification message, where the first notification message carries an identifier of a tunnel interface of an unavailable LNS, and the first notification message is used by the controller based on each of the multiple LNSs
  • the device information of the LNS is sent when the unavailable LNS in the multiple LNSs is determined, and the device information includes the device identifier corresponding to the LNS. And device status information;
  • the identifier of the tunnel interface of the unavailable LNS is deleted from the stored interface information list.
  • the deleting the identifier of the tunnel interface of the unavailable LNS from the stored interface information list includes:
  • the identifiers of all the tunnel interfaces in the unavailable LNS are deleted from the stored interface information list.
  • the method further includes:
  • the unavailable LNS is sent when the problem is restored to an available LNS after the problem is eliminated;
  • the deleting the identifier of the tunnel interface of the unavailable LNS from the stored interface information list includes:
  • the identifier of the unavailable tunnel interface in the unavailable LNS is deleted from the stored interface information list, where the first notification message is deleted. Determining, by the controller, the LNS of the unavailable tunnel interface in the plurality of LNSs based on the identifier of the at least one tunnel interface and the tunnel interface state information included in the device information of each of the plurality of LNSs send.
  • the method further includes:
  • the method further includes:
  • the updated interface information list is sent to the LAC, and the LAC is instructed to select the LNS and the tunnel based on the updated interface information list. Tunnel interface.
  • a controller having a function of implementing the L2TP-based device management method in the above first aspect.
  • the controller includes at least one module for implementing the L2TP-based device management method provided by the above first aspect.
  • an authentication authorization and accounting AAA server is provided, and the AAA server has a function of implementing the L2TP-based device management method in the second aspect.
  • the AAA server includes at least one module for implementing the L2TP-based device management method provided by the second aspect above.
  • a controller comprising a processor and a memory.
  • the memory is configured to store a program supporting the controller to execute the L2TP-based device management method, and to store data related to implementing the L2TP-based device management method, where the data may be device information of the LNS, an identifier of the tunnel interface, or the like.
  • the processor is configured to execute a program stored in the memory.
  • the controller can also include a communication bus for establishing a connection between the processor and the memory.
  • an authentication and accounting and accounting AAA server includes a processor and a memory.
  • the memory is configured to store a program that supports the controller to execute the L2TP-based device management method, and store data related to implementing the L2TP-based device management method, where the data may be a tunnel interface identifier, an interface information list, or the like.
  • the processor is configured to execute a program stored in the memory.
  • the AAA server can also include a communication bus for establishing a connection between the processor and the memory.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions used by the controller, or storing a program involved in executing the controllers of the first aspect and the third aspect.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions used by the AAA server, or storing a program related to the AAA server for performing the second and fourth aspects.
  • the embodiment of the present invention provides an L2TP-based device management system, where the device management system includes a controller, an L2TP access concentrator LAC side, and an L2TP network server LNS side, where the LAC side includes an authentication authorization and a meter.
  • a controller is introduced between the LAC side and the LNS side, and the controller may determine, according to the device information of each LNS in the multiple LNSs on the LNS side, the unavailable LNS in the multiple LNSs, and
  • the AAA server on the LAC sends a first notification message to notify the AAA server to delete the identifier of the tunnel interface of the unavailable LNS from the stored interface information list, and obtain the updated interface information list.
  • the LNS corresponding to the identifier of all the tunnel interfaces included in the updated interface information list is available, and each tunnel interface of the available LNS is also available, because the updated interface information list has deleted the identifier of the tunnel interface of the LNS.
  • any LNS and any tunnel interface selected are also available, thereby solving the problem that the selected LNS or tunnel interface may not meet the working conditions.
  • the problem that the tunnel cannot be established or the quality of the established tunnel is poor, and the success rate and stability of the tunnel establishment are improved.
  • 1A is a network architecture diagram of an L2TP protocol according to an embodiment of the present invention.
  • 1B is a network architecture diagram of another L2TP protocol according to an embodiment of the present invention.
  • 1C is a network architecture diagram of another L2TP protocol according to an embodiment of the present invention.
  • 1D is a network architecture diagram of another L2TP protocol according to an embodiment of the present invention.
  • FIG. 1E is a schematic structural diagram of a hardware of a controller according to an embodiment of the present invention.
  • 1F is a schematic structural diagram of hardware of an AAA server according to an embodiment of the present invention.
  • FIG. 2 is a flowchart of a device management method based on L2TP according to an embodiment of the present invention
  • FIG. 3 is a schematic structural diagram of a controller according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of an AAA server according to an embodiment of the present invention.
  • An L2TP-based device management method provided by an embodiment of the present invention is applied to a network of an L2TP protocol.
  • FIG. 1B is a network architecture diagram of another L2TP protocol according to an embodiment of the present invention.
  • the network architecture of the L2TP protocol includes an LAC side 10, an LNS side 20, and a controller 30.
  • the LAC side 10 includes a plurality of LACs 11 and AAA servers 12, and the LNS side 20 includes a plurality of LNSs 21, and the controller 30 is connected to the AAA server 12 and the plurality of LNSs 21 of the LNS side 20, respectively.
  • the LNS side 20 may also include an AAA server (not shown in FIG. 1B).
  • the AAA server of the LNS side 20 is separately connected to the plurality of LNSs 21 for providing authentication, authorization, and accounting services for the respective LNSs 21.
  • the LAC may be a device of the telecommunication carrier, for example, a network access server (NAS) of the telecommunication carrier
  • the LNS may be a device of the telecommunication carrier or a device of the enterprise client, for example,
  • the router or the server of the telecommunications carrier is not limited in this embodiment of the present invention.
  • the user equipment can access the LAC11 through the access network of the service provider, and then connect to the remote LNS 21 through the L2TP tunnel.
  • the user equipment can send a dialing request to the LAC11 by dialing.
  • the LAC11 receives the dialing request, it can send an online request to the AAA server on the LAC side.
  • the dialing request can carry the user account entered by the user. Password, etc.
  • the embodiment of the present invention introduces a controller 30 between the LAC side 10 and the LNS side 20 based on the network architecture of the existing L2TP protocol shown in FIG. 1A.
  • the controller 30 is configured to monitor the device status of the plurality of LNSs 21 on the LNS side 20, and send a notification message to the AAA server 12 according to the device status of each LNS 21, indicating whether each LNS 21 is available, and whether the identifier of the tunnel interface of each LNS 21 can be It is sent to the LAC11 of the LAC side 10.
  • the controller 30 is configured to receive device information from each of the plurality of LNSs 21 on the LNS side, where the device information includes device identifiers and device state information corresponding to the LNS 21; and each LNS21 according to the plurality of LNSs 21
  • the device information determines the unavailable LNS 21 of the plurality of LNSs 21; and sends a first notification message to the AAA server 12 on the LAC side, where the first notification message carries the identifier of the tunnel interface of the unavailable LNS.
  • the AAA server 12 is configured to receive the first notification message sent by the controller 30, and delete the identifier of the tunnel interface of the unavailable LNS 21 from the stored interface information list according to the first notification message; when receiving the LAC10 side When any online request sent by the LAC11 is sent, the updated interface information list is sent to the LAC11.
  • the LAC 11 is configured to receive the updated interface information list sent by the AAA server 12, select an LNS21 and a tunnel interface for establishing an L2TP tunnel based on the updated interface information list, and send a tunnel establishment request to the selected LNS 21, the tunnel establishment request.
  • the identifier carrying the selected tunnel interface.
  • the selected LNS 21 is configured to send a setup response to the LAC 11 when the tunnel establishment request sent by the LAC 11 is received, to establish an L2TP tunnel to the LAC 11 through the selected tunnel interface.
  • the controller 30 and each LNS 21 can be connected through a wired network or a wireless network. Further, a specified network management protocol connection may be established between the controller 30 and each LNS 21, so that the controller 30 acquires device information of each LNS 21 through the specified network management protocol.
  • the specified network management protocol may be a NETCONF (Network Configuration Protocol) or an SNMP (Simple Network Management Protocol).
  • NETCONF and SNMP will be further described in detail:
  • the controller 30 establishes a NETCONF connection with each LNS 21, and acquires device information of each LNS 21 through NETCONF.
  • NETCONF is a network configuration and management protocol based on XML (Extensible Markup Language), which can manage the configuration information and status information of network devices. It specifically uses XML as the encoding method of configuration data and protocol messages, and uses C/S (client/server) mode to obtain management information of the device.
  • XML Extensible Markup Language
  • the controller 30 can establish a NETCONF connection through a schema or a yang interface, where both schema and yang belong to a data modeling language in XML.
  • the NETCONF management terminal can be configured in the controller 30, and the NETCONF agent is configured in each LNS 21.
  • the controller 30 obtains the device information of the NETCONF agent in a remote procedure call manner through the configured NETCONF management terminal.
  • the NETCONF management terminal can obtain the device information of each NETCONF proxy by using the get command or the get-config command.
  • the controller 30 establishes an SNMP connection with each LNS 21, and acquires device information of each LNS 21 through SNMP.
  • SNMP is a network management standard protocol widely used in TCP/IP (Transmission Control Protocol/Internet Protocol) networks. It can support network management systems to monitor whether devices connected to the network cause any management. The situation of concern.
  • an SNMP manager can be configured in the management terminal controller 30, and an SNMP agent (Agent) is configured in each managed terminal LNS21. The manager is used to run a hypervisor, and the agent is used to run an agent.
  • the controller 30 can actively obtain the device information of the corresponding LNS from the agents configured in the respective LNSs through the configured Manager. For example, the controller 30 can periodically query the device information of the corresponding LNS from the agents configured in the respective LNSs through the configured Manager.
  • each LNS can report the current device information to the Manager in time through the configured Agent. For example, the LNS can report fault information to the Manager through the configured agent when the device is faulty.
  • the controller 30 assumes the function of the NETCONF management terminal in the implementation manner of using NETCONF.
  • the controller 30 assumes the function of part of the SNMP management terminal, that is, The controller 30 assumes part of the functions of the network management system, and can manage and maintain the device information of the plurality of LNSs 21 in the LNS side 20.
  • controller 30 and the AAA server 12 can also be connected through a wired network or a wireless network.
  • the controller 30 can establish a Radius (Remote Authentication Dial In User Service) connection with the AAA server 12 to send a notification message to the AAA server 12 through the Radius connection to notify each LNS 21. Whether the tunnel interface is available.
  • Radius Remote Authentication Dial In User Service
  • the network architecture of the L2TP protocol may further include an LTS (L2TP Tunnel Switch), and the LTS can serve as a tunnel intermediate switching node, and has the functions of the LAC and the LNS. That is, the LTS can be used as the LNS of the LAC to receive the tunnel establishment request sent by the LAC, establish an L2TP tunnel, or act as an LNS LAC to send a tunnel establishment request to the LNS to request to establish an L2TP tunnel.
  • LTS L2TP Tunnel Switch
  • FIG. 1C is a network architecture diagram of another L2TP protocol according to an embodiment of the present invention.
  • the network architecture of the L2TP protocol includes an LAC side 10, an LTS side 40, an LNS side 20, and a controller 30.
  • the LAC side 10 includes multiple LACs 11 and AAA servers 12, and the AAA server 12 is connected to the multiple LACs 11 to provide authentication, authorization, and accounting services for each LAC11.
  • the LTS side 40 includes a plurality of LTSs 41 and AAA servers 42, and the AAA server 41 is separately connected to the plurality of LTSs 41 for providing authentication, authorization, and billing services for the respective LTSs 41;
  • the LNS side 20 includes a plurality of LNSs 21.
  • the controller 30 is connected to the AAA server 12 of the LAC side 10, and is connected to the plurality of LTSs 41 of the LTS side 40.
  • the LTS 41 of the plurality of LTSs 41 can be determined according to the device information of each LTS 41 of the plurality of LTSs 41, and
  • the identity of the tunnel interface of the unavailable LTS 41 is sent to the AAA server 12 of the LAC side 10 so that the AAA server 12 updates the stored list of LTS interface information according to the identity of the tunnel interface of the unavailable LTS 41.
  • the controller 30 is also connected to the AAA server 42 of the LTS side 40 and connected to the plurality of LNSs 21 of the LNS side 20, and can determine that the plurality of LNSs 21 are unavailable based on the device information of each of the plurality of LNSs 21
  • the LNS 21 transmits the identity of the tunnel interface of the unavailable LNS 21 to the AAA server 42 of the LTS side 40 so that the AAA server 42 updates the stored LNS interface information list according to the identity of the tunnel interface of the unavailable LNS 21.
  • FIG. 1D is a network architecture diagram of another L2TP protocol according to an embodiment of the present invention.
  • the controller 31 is connected to the AAA server 12 on the LAC side, and is connected to multiple LTSs 41 on the LTS side 40 for LTS-based.
  • the device information of the plurality of LTSs 41 in the side 40 notifies the AAA server 12 of the LAC side 10 to update the stored LTS interface information list.
  • the controller 32 is connected to the AAA server 42 of the LTS side 40, and is connected to the plurality of LNSs 21 of the LNS side 20, respectively, for notifying the AAA server 42 of the LTS side 40 to update the storage based on the device information of the plurality of LNSs 21 in the LNS side 20.
  • LNS interface information list is connected to the AAA server 42 of the LTS side 40, and is connected to the plurality of LNSs 21 of the LNS side 20, respectively, for notifying the AAA server 42 of the LTS side 40 to update the storage based on the device information of the plurality of LNSs 21 in the LNS side 20.
  • FIG. 1E is a schematic diagram showing the hardware structure of a controller according to an embodiment of the present invention.
  • the controller may include a communication bus 131, a memory 132, a transmitter 133, a receiver 134, and a processor 135, and the memory 132, Transmitter 133, receiver 134 and processor 135 can communicate over communication bus 131.
  • the transmitter 133 and the receiver 134 are configured to communicate with other network devices.
  • the controller 30 can communicate with multiple LNSs on the LNS side through the receiver 134 to obtain device information of each LNS.
  • the shooter 133 communicates with the AAA server on the LAC side, and transmits a notification message to the AAA server.
  • the memory 132 is configured to store a program
  • the processor 135 is configured to invoke a program stored in the memory 132 to implement the L2TP-based device management method.
  • processor 135 may be an integrated circuit chip with signal processing capability. In the implementation process, the above steps may be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software. These instructions can be implemented and controlled by the processor in them.
  • the processor may also be a general purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or the like. Programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • the above general purpose processor may be a microprocessor or may be any conventional processor, decoder or the like.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the transmitter 133 and the receiver 134 may be separate hardware or integrated into the controller as a whole, as the transmitter 133 and the receiver 134 may be integrated into one transceiver.
  • the controller can also include a communication interface for supporting communication of the controller with other network devices.
  • the communication bus 131 includes a power bus, a control bus, and a status signal bus in addition to the data bus. However, for clarity of description, various buses are labeled as communication bus 131 in FIG. 1E.
  • the controller may also configure a management end of the network management protocol, such as a NETCONF management terminal or an SNMP management terminal, to receive device information of multiple LNSs from the LNS side through a corresponding network management protocol.
  • a management end of the network management protocol such as a NETCONF management terminal or an SNMP management terminal
  • FIG. 1F is a schematic diagram showing the hardware structure of an AAA server according to an embodiment of the present invention.
  • the controller may include a communication bus 231, a memory 232, a transmitter 233, a receiver 234, and a processor 235, and the memory 232, Transmitter 233, receiver 234, and processor 235 can communicate over communication bus 231.
  • the transmitter 233 and the receiver 234 are configured to communicate with other network devices, for example, the AAA server can communicate with the controller through the receiver 234 to obtain a notification message sent by the controller; or through the transmitter 233 and the LAC on the LAC side. Communicate and send a list of interface information to the LAC.
  • the AAA server can communicate with the controller through the receiver 234 to obtain a notification message sent by the controller; or through the transmitter 233 and the LAC on the LAC side. Communicate and send a list of interface information to the LAC.
  • the memory 132 is configured to store a program
  • the processor 135 is configured to invoke a program stored in the memory 132 to implement the L2TP-based device management method.
  • processor 235 may be an integrated circuit chip with signal processing capability. In the implementation process, the above steps may be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software. These instructions can be implemented and controlled by the processor in them.
  • the processor may also be a general purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or the like. Programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • the above general purpose processor may be a microprocessor or may be any conventional processor, decoder or the like.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the transmitter 233 and the receiver 234 may be two separate hardwares, or may be integrated as a whole in the control plane node, for example, the transmitter 233 and the receiver 234 may be integrated into one transceiver.
  • the controller can also include a communication interface for supporting communication of the controller with other network devices.
  • the communication bus 231 includes a power bus, a control bus, and a status signal bus in addition to the data bus. However, for clarity of description, various buses are labeled as communication bus 231 in FIG. 1F.
  • FIG. 2 is a flowchart of a method for managing a device based on L2TP according to an embodiment of the present invention. The method is applied to the L2TP network architecture shown in FIG. 1B. Referring to FIG. 2, the method includes:
  • Step 201 The controller receives device information from each of the plurality of LNSs on the LNS side, where the device information includes device identifiers and device state information corresponding to the LNS.
  • the controller may establish a specified network management protocol connection with multiple LNSs on the LNS side, and receive device information of multiple LNSs by using a specified network management protocol.
  • the specified network management protocol can be NETCONF or SNMP.
  • the implementation manner of receiving device information from each of the plurality of LNSs on the LNS side includes at least one of: receiving, by the NETCONF, device information from each of the plurality of LNSs on the LNS side; Alternatively, device information from each of the plurality of LNSs on the LNS side is received through SNMP.
  • NETCONF and SNMP are both well-developed network management protocols, which can monitor and manage device information of network devices. Therefore, by using NETCONF or SNMP to receive device information of multiple LNSs on the LNS side, the LNS is improved. Accuracy and efficiency of device information.
  • the device information of each LNS may include device identifiers and device state information corresponding to the LNS.
  • the device identifier of the LNS may be the factory serial number of the LNS, the MAC (Media Access Control) address, the IP address of the device, and the like. The embodiment of the present invention does not limit this.
  • the device status information of the LNS may include at least one of fault information, CPU (Central Processing Unit) utilization, memory usage, total traffic of the outbound interface carrying the L2TP tunnel, and the total amount of users of the total bearer.
  • the fault information is used to indicate that the LNS is in a fault state.
  • the CPU usage, the memory usage, the total traffic of the outbound interface carrying the L2TP tunnel, and the total number of users of the L2TP tunnel are the load information of the LNS, which is used to indicate the load status of the LNS.
  • the device status information of the LNS may also include information that can reflect the status of other devices of the LNS, which is not limited by the embodiment of the present invention.
  • the controller can monitor the fault status and the whole load status of each LNS on the LNS side, so that the fault problem of the device and the load capacity of the whole device can be quickly presented, and the existing network is solved.
  • Step 202 The controller determines, according to device information of each LNS in the multiple LNSs, an unavailable LNS in the multiple LNSs.
  • the first mode is: when the device information of each LNS includes the device identifier and the device state information of the LNS, the unavailable LNS in the multiple LNSs is determined according to the device state information of each LNS in the multiple LNSs.
  • the manner of determining the unavailable LNS in the plurality of LNSs according to the device state information of each of the plurality of LNSs includes at least one of the following manners: when the fault information exists in the device state information of the target LNS, the target is The LNS is determined to be an unavailable LNS, and the target LNS is any one of the plurality of LNSs; when the CPU utilization of the target LNS is greater than a first preset threshold, the target LNS is determined to be an unavailable LNS; when the target LNS is When the memory usage is greater than the second preset threshold, the target LNS is determined to be an unavailable LNS; and when the total traffic of the outbound interface of the L2TP tunnel of the target LNS is greater than a third preset threshold, the target LNS is determined to be unavailable. LNS; when the amount of users of the total bearer of the target LNS is greater than a fourth preset threshold, the target LNS is determined to be an unavailable LNS.
  • the fault information of the LNS is used to indicate that the LNS is in the fault state, that is, the LNS is faulty, and the L2TP tunnel cannot be successfully established. Therefore, when there is fault information in the device status information of the target LNS, The target LNS is determined to be an unavailable LNS.
  • the total traffic of the outbound interface that carries the L2TP tunnel is the sum of the traffic of the outbound interface that carries the L2TP tunnel in the target LNS, and is used to indicate the bandwidth occupied by the L2TP tunnel service.
  • the total number of users of the total bearer refers to the sum of the users carried by the tunnels corresponding to all the tunnel interfaces included in the target LNS.
  • the first preset threshold, the second preset threshold, the third preset threshold, and the fourth preset threshold may all be set according to the load capacity of the specific LNS, and the preset threshold may be set by the controller, and may be performed by each LNS.
  • the setting may also be set by the controller and the corresponding LNS, which is not limited by the embodiment of the present invention.
  • the information about the CPU usage, the memory usage, the total traffic of the outbound interface carrying the L2TP tunnel, and the total number of users of the L2TP tunnel are the load information of the LNS, which is used to indicate the load status of the LNS.
  • the load information of the LNS which is used to indicate the load status of the LNS.
  • the embodiment of the present invention only determines whether the target LNS is in an overload state according to the foregoing load factors and corresponding preset thresholds, and further determines whether the target LNS is available as an example.
  • the load status of the LNS may be comprehensively analyzed in combination with any of the above load factors, or the LNS may be in an overload state according to other factors indicating the load capacity of the whole machine. The embodiment does not limit this.
  • the second mode when the device information further includes the identifier of the at least one tunnel interface and the tunnel interface state information of the LNS, the identifier of the at least one tunnel interface included in the device information of each LNS in the multiple LNSs
  • the tunnel interface status information is determined, and the LNSs of the plurality of LNSs having the unavailable tunnel interfaces are determined, and the LNSs of the plurality of LNSs having the unavailable tunnel interfaces are determined as the unavailable LNSs of the plurality of LNSs.
  • the LNS may include at least one tunnel interface, and each tunnel interface refers to a logical interface or a physical interface created by the LNS for establishing an L2TP tunnel, and may be a lookback (loopback interface) or the like.
  • the tunnel interface address can be used as the source or destination address of the L2TP tunnel.
  • the controller may further determine whether the tunnel interface is located according to the tunnel interface state information of a tunnel interface in the LNS.
  • the tunnel interface In the overload state, when it is determined that the tunnel interface is in an overload state, the tunnel interface can no longer carry a new task, that is, the tunnel interface of the LNS is unavailable, and the LNS can no longer pass the tunnel interface. An L2TP tunnel is established. Therefore, an LNS with an unavailable tunnel interface can be determined as an unavailable LNS.
  • the tunnel interface state information may include at least one of a quantity of users carried by the corresponding tunnel and a traffic of the tunnel interface, and an identifier and a tunnel interface of the at least one tunnel interface included in the device information of each LNS in the multiple LNSs.
  • the status information, the manner of determining that the LNS of the plurality of LNSs has an unavailable tunnel interface includes at least one of the following manners:
  • the fifth preset threshold may be set according to a specific user threshold that can be assumed by the tunnel corresponding to each tunnel interface in the LNS, and the sixth preset threshold may be set according to a bandwidth threshold of each tunnel interface in the LNS, and the The fifth preset threshold and the sixth preset threshold may be set by the controller, may be set by the respective LNS, or may be set by the controller and the corresponding LNS, which is not limited by the embodiment of the present invention.
  • Step 203 The controller sends a first notification message to the AAA server on the LAC side, where the first notification message carries the identifier of the tunnel interface of the unavailable LNS.
  • the first notification message is used to notify the AAA server on the LAC side to delete the identifier of the tunnel interface of the unavailable LNS from the stored interface information list.
  • the LNS when the LNS is in a fault state or a full-load overload state, it indicates that the LNS cannot process a new tunnel establishment request. Therefore, all tunnel interfaces of the LNS are unavailable. The identifier of all tunnel interfaces of the LNS needs to be deleted.
  • the LNS may still receive the tunnel establishment request, but only through other interfaces. To establish an L2TP tunnel, that is, only the overloaded tunnel interface is unavailable, and other tunnel interfaces are still available. Simply delete the identifier of the overloaded tunnel interface. Therefore, the first notification message may include the following two implementation forms:
  • the identifier of the tunnel interface of the unavailable LNS carried in the first notification message is the identifier of all the tunnel interfaces of the unavailable LNS, and the first notification message is carried.
  • the AAA server used to notify the LAC side deletes the identifiers of all tunnel interfaces of the unavailable LNS from the stored interface information list.
  • the first notification message carries the identifier of the unavailable tunnel interface in the unavailable LNS, and is used to notify the AAA server on the LAC that the unavailable tunnel in the LNS is unavailable.
  • the ID of the interface is removed from the list of stored interface information.
  • the identifier of the tunnel interface may include the interface address of the tunnel interface, the tunnel identifier corresponding to the tunnel interface, and the device identifier of the LNS to which the tunnel interface belongs.
  • the identifier of the tunnel interface may include Tunnel-Server-Endpoint (Tunnel Server Endpoint) and Tunnel-Assignment-ID (Tunnel Assignment) of the tunnel interface. number).
  • the Tunnel-Server-Endpoint is the IP address of the tunnel interface.
  • the Tunnel-Assignment-ID is the number of the tunnel corresponding to the tunnel interface.
  • the controller may establish a Radius connection with the AAA server on the LAC side in advance to send the first notification message through the Radius connection.
  • the first notification message may be sent through a Radius message.
  • the Radius packet in the Radius protocol may be extended, and the first notification message may be sent in the extended field; or the original specified field in the Radius packet may be extended, and the first notification is sent in the specified field.
  • the controller may extend the Status-Client-Experimental field in the Radius packet, and carry the first notification message in the Status-Client-Experimental field.
  • Step 204 The AAA server on the LAC side receives the first notification message sent by the controller, and deletes the identifier of the tunnel interface of the unavailable LNS from the stored interface information list according to the first notification message.
  • the interface information list includes the identifiers of all the tunnel interfaces of the LNSs, and is sent to the specific LAC, so that the LAC selects the LNS and the tunnel interface for establishing the tunnel based on the interface information list.
  • the identifier of the tunnel interface of the unavailable LNS is deleted from the stored interface information list according to the first notification message, and may include at least one of the following manners:
  • the first mode is: when the first notification message carries the identifiers of all the tunnel interfaces of the unavailable LNS, the identifiers of all the tunnel interfaces of the unavailable LNS are deleted from the interface information list.
  • the second mode is: when the first notification message carries the identifier of the tunnel interface that is not available in the LNS, the identifier of the unavailable tunnel interface in the LNS is deleted from the interface information list.
  • the implementation process of deleting the identifier of the tunnel interface that does not use the LNS from the stored interface information list is different according to the storage mode of the interface information list, and may specifically include at least one of the following methods:
  • the AAA server may pre-store an interface information list, where the interface information list includes identifiers of all tunnel interfaces of each LNS on the LNS side.
  • the identifier of the tunnel interface of the unavailable LNS is deleted from the interface information list according to the first notification message, and the updated interface information list is sent to the interface information list.
  • the AAA server may also obtain the interface information list from the interface state list, and delete the identifier of the tunnel interface of the unavailable LNS from the interface information list by using the operation of the interface state list.
  • the AAA server may further store an interface status list, where the interface status list includes an identifier of the tunnel interface of each LNS and a corresponding status identifier.
  • the status indicator may include a first status identifier and a second status identifier, where the first status identifier is used to indicate that the corresponding tunnel interface is available, the identifier of the tunnel interface may be sent to the LAC, and the second status identifier is used to indicate the corresponding tunnel interface.
  • the identifier of the tunnel interface cannot be sent to the LAC.
  • the AAA server may first determine all available tunnel interfaces based on the status identifiers in the interface status list, and combine the identifiers of all available tunnel interfaces to obtain the interface information list.
  • the identifier of the tunnel interface of the unavailable LNS carried in the first notification message may be obtained, and the unavailability is not available in the status list.
  • the state identifier corresponding to the identifier of the tunnel interface of the LNS is switched from the first state identifier to the second state identifier to The identifier of the tunnel interface that is not available for the LNS is removed from the interface information list.
  • the first notification message sent by the controller is received, and the notification is received.
  • the message carries the identifier of all the tunnel interfaces of the unavailable LNS
  • the state identifier of all the tunnel interfaces of the unavailable LNS can be switched from 0 to 1 to send the identifiers of all the tunnel interfaces of the LNS to the LAC.
  • the interface information list is removed.
  • Step 205 When the LAC receives the dialing request of the user terminal, the LAC sends an online request to the AAA server on the LAC side.
  • the LAC can be any LAC in the LAC, and the LAC online request is triggered by the dialing request sent by the user terminal.
  • the user terminal can send a dialing request to the LAC on the LAC side when the dialing operation is detected based on the currently input user account and password, and the dialing request can carry the user account and password.
  • the LAC receives the dialing request, it can send an online request to the AAA server, and the online request also carries the user account and password, so that the AAA server can perform authorization, authentication, or accounting management on the user account.
  • Step 206 The AAA server on the LAC sends the updated interface information list to the LAC when receiving the online request sent by the LAC.
  • Step 207 The LAC receives the updated interface information list sent by the AAA server on the LAC side, and selects an LNS and a tunnel interface for establishing an L2TP tunnel based on the updated interface information list, and sends a tunnel establishment request to the selected LNS.
  • the LAC may select an identifier of the tunnel interface from the updated interface information list, determine an LNS indicated by the identifier of the selected tunnel interface, and determine the indicated LNS as the selected LNS. And the tunnel establishment request carries the identifier of the selected tunnel interface, so that the LNS establishes a tunnel based on the identifier of the selected tunnel interface.
  • the LNS corresponding to the identifier of all the tunnel interfaces included in the updated interface information list is available, and each tunnel interface of the available LNS is also available, because the updated interface information list has deleted the identifier of the tunnel interface of the LNS. Available, therefore, when the LAC selects the LNS and tunnel interface based on the updated interface information list, any selected LNS and any tunnel interface are also available.
  • Step 208 When receiving the tunnel establishment request sent by the LAC, the selected LNS sends a setup response to the LAC to establish an L2TP tunnel to the LAC through the selected tunnel interface.
  • the selected LNS may send a setup response to the LAC according to the identifier of the tunnel interface carried in the request, where the setup response indicates that the tunnel establishment request is verified, and the LAC receives the After the response is established, the L2TP tunnel between the tunnel interfaces of the selected LNS can be successfully established.
  • the LAC can set the LAC address as the start address and the tunnel interface address as the destination address to establish the LAC from the LAC. L2TP tunnel between tunnel interfaces.
  • the LNS when an LNS is in a fault state, if the LAC still sends a tunnel establishment request to the LNS, the LNS will not be able to respond to the tunnel establishment request due to the failure of the LNS, and the tunnel establishment fails.
  • the fault state of the LNS is monitored, and when any LNS is in a fault state, the LAC is notified.
  • the AAA server on the side deletes the identifier of all the tunnel interfaces of the LNS from the interface information list, and implements the LNS fault status quickly. This prevents the LAC from sending a tunnel establishment request to the LNS when an LNS fails.
  • the tunnel establishment fails, and the fast switching of services after the LNS fault is implemented, which improves the success rate of tunnel establishment.
  • the tunnel of the LNS may be congested, and the L2TP tunnel or the established tunnel quality cannot be established. Poor.
  • the AAA server of the LAC is notified to delete the identifier of all the tunnel interfaces of the LNS from the interface information list.
  • the LNS load capacity is quickly perceived, and some LNSs that are present in the existing network are overloaded. Some LNS access users are very small. This LNS load is unbalanced, which solves the problem of unbalanced load. The problem of unreasonable resource allocation and waste of network resources ensures the balance of load between multiple LNSs and improves the performance of the L2TP network and the tunnel establishment effect.
  • the AAA server is notified to remove the overloaded tunnel interface identifier from the interface information list, and the load on the LNS granularity is In addition to equalization, load balancing on the tunnel interface granularity is also achieved, which improves accuracy.
  • the controller may further introduce the LNS after the problem is re-introduced into the L2TP network to share load.
  • the device information of the unavailable LNS may continue to be received, and whether the unavailable LNS has been restored is determined based on the device information of the unavailable LNS. And determining, according to the device information of the unavailable LNS, that the unavailable LNS reverts to an available LNS after the problem is removed, and sends a second notification message to the AAA server on the LAC side, where the second notification message carries all the tunnels of the available LNS.
  • the identifier of the interface is used to notify the AAA server on the LAC side to add the identifiers of all tunnel interfaces of the available LNS to the interface information list.
  • the identifier of all tunnel interfaces of the available LNS may be added to the interface information list according to the second notification message, and the steps are repeated. Operation of 205-208.
  • determining, according to the device information of the unavailable LNS, whether the unavailable LNS is restored to the available LNS after the problem is eliminated may include at least one of the following manners:
  • the first mode is: when it is determined that the unavailable LNS is restored from the fault state to the normal state based on the device information of the unavailable LNS, that is, when the fault is eliminated, it is determined that the unavailable LNS is restored to the available LNS.
  • the second mode is: when the LNS is restored from the overload state of the whole device to the normal state based on the device information of the LNS, that is, when the load of the whole device decreases, it is determined that the unavailable LNS is restored to the available LNS.
  • the controller may further introduce the tunnel interface after the problem is reintroduced into the L2TP network. In the middle to share the load.
  • the device may continue to receive the tunnel interface state information of the unavailable tunnel interface in the unavailable LNS, and determine the tunnel interface state information based on the unavailable tunnel interface. Whether the problem with the unavailable tunnel interface has been eliminated. Determining, according to the tunnel interface state information of the unavailable tunnel interface in the unavailable LNS, determining that the unavailable tunnel interface is restored to an available tunnel interface after the problem is eliminated, to the The AAA server on the LAC side sends a third notification message, where the third notification message carries the identifier of the available tunnel interface, and is used to notify the AAA server on the LAC side to add the identifier of the available tunnel interface in the interface information list. When the AAA server on the LAC side receives the third notification message sent by the controller, the identifier of the available tunnel interface is added to the interface information list according to the third notification message, and steps 205-208 are repeated. Operation.
  • the unavailable tunnel interface can be restored to the available tunnel interface when the overloaded state is restored to the normal state, that is, when the load of the tunnel interface decreases.
  • the manner of adding the identifier of the tunnel interface to the interface information list according to the second notification message or the third notification message is different according to the manner of obtaining the interface information list, and may specifically include at least one of the following manners:
  • the first mode is: when the AAA server on the LAC side stores the interface information list in the first implementation manner in step 204, the AAA server on the LAC side can receive the second notification message or the third notification message. Add the identifier of the tunnel interface directly to the interface information list, obtain the updated interface information list, and send the updated interface information list to the LAC.
  • the second mode when the AAA server on the LAC side stores the interface information list in the second implementation manner in step 204, the AAA server on the LAC side may receive the second notification message or the third notification message.
  • the state identifier corresponding to the identifier of the tunnel interface is switched from the second state identifier to the first state identifier, so as to add the identifier of the tunnel interface in the interface information list.
  • the AAA server on the LAC side updates the stored interface information list according to the notification message sent by the controller, and sends the updated interface information list to any LAC as an example.
  • the AAA server may also send different interface information lists for different online requests sent by different LACs, or for different user accounts carried in the online request; or, according to the notification message sent by the controller, the storage is performed.
  • the different interface information lists are updated, which is not limited by the embodiment of the present invention.
  • the AAA server on the LAC side can update the stored interface information list according to the notification message sent by the controller, and obtain the updated interface information list. After receiving the online request sent by the LAC, the updated interface information is obtained.
  • the LNS and the tunnel interface corresponding to the LAC or the user account carried in the online request are selected in the list, and the selected tunnel interface identifiers are combined into a new interface information list and sent to the LAC.
  • the AAA server may store a plurality of interface information lists, each interface information list corresponding to a group of LACs or a group of user accounts; when the AAA server receives the notification message sent by the controller, the AAA server may store the information according to the notification message.
  • the interface information list is updated. After receiving the online request sent by the LAC, the interface information list corresponding to the LAC or the interface information corresponding to the user account carried in the online request may be selected from the multiple interface information lists. And send the selected interface information list to the LAC.
  • the AAA server 12 of the LAC side 10 can update the stored LTS interface information list in the above manner, and the AAA server 42 of the LTS side 40 can access the stored LNS interface according to the foregoing manner.
  • the information list is updated.
  • the LTS interface information list stores the identifiers of the tunnel interfaces of the LTSs 41 in the LTS side 40.
  • the LNS interface information list stores the identifiers of the tunnel interfaces of the LNSs 21 in the LNS side 20.
  • the controller 30 or the controller 31 may receive device information from each of the plurality of LTSs 41 in the LTS side 40, the device information including the device label corresponding to the LTS 41. Identifying the device status information; determining the unavailable LTS 41 of the plurality of LTSs 41 according to the device information of each of the plurality of LTSs 41; transmitting a first notification message to the AAA server 12 of the LAC side 10, the first notification message carrying The identifier of the tunnel interface of the unavailable LTS 41 is used to notify the AAA server 12 to delete the identifier of the tunnel interface of the unavailable LTS 41 from the stored LTS interface information list.
  • the AAA server 12 can send the updated LTS interface information list to the LAC11, so that the LAC11 selects the LTS 41 based on the updated LTS interface information list.
  • the tunnel interface is configured to send a tunnel establishment request to the selected LTS 41.
  • the selected LTS 41 can establish an L2TP tunnel from the selected tunnel interface to the LAC11.
  • the controller 30 or the controller 32 may receive device information from each of the plurality of LNSs 21 in the LNS side 20, the device information including the device identifier corresponding to the LNS 21 and Determining the unavailable LNS 21 of the plurality of LNSs 21 according to the device information of each of the plurality of LNSs 21; sending a first notification message to the AAA server 42 of the LTS side 40, the first notification message carrying the The identifier of the tunnel interface of the LNS 21 is used to notify the AAA server 42 to delete the identifier of the tunnel interface of the unavailable LNS 21 from the stored LNS interface information list.
  • the AAA server 42 may send the updated LNS interface information list to the LTS 41, so that the LTS 41 selects the LNS 21 based on the updated LNS interface information list. And the tunnel interface, and sends a tunnel establishment request to the selected LNS 21, after the selected LNS 21 receives the request of the LTS 41, the L2TP tunnel from the selected tunnel interface to the LTS 41 can be established.
  • the online request sent by the LAC11 or the online request sent by the LTS41 is also triggered by the dialing request sent by the user terminal.
  • the AAA server 12 on the LAC 10 side may also send different LTS interface information lists for different online requests sent by different LACs or different user accounts carried in the online request.
  • the AAA server 42 on the LTS 40 side may also be used.
  • the uplink request sent by the different LTSs, or for the different user accounts carried in the online request the different LNS interface information lists are sent.
  • the specific implementation process reference may be made to the related descriptions, and details are not described herein again.
  • a controller is introduced between the LAC side and the LNS side, and the controller can monitor each of the LNS sides by receiving device information from each LNS of the multiple LNSs.
  • the device status of the LNS is determined, and the LNS in the plurality of LNSs is determined based on the information of each LNS device, and the first notification message of the identifier of the tunnel interface carrying the unavailable LNS is sent to the AAA server on the LAC side, and the LAC side is notified.
  • the AAA server deletes the identifier of the tunnel interface of the unavailable LNS from the stored interface information list, and obtains the updated interface information list.
  • the LNS corresponding to the identifier of all tunnel interfaces included in the updated interface information list is available, and the tunnel interface of the available LNS is also available. Therefore, when the LAC selects the LNS and the tunnel interface based on the updated interface information list, any LNS selected and any tunnel interface are also available, thereby solving the problem that the selected LNS or tunnel interface may not meet the working condition.
  • the problem that the tunnel cannot be established or the quality of the established tunnel is poor, and the success rate and stability of the tunnel establishment are improved.
  • FIG. 3 is a schematic structural diagram of a controller according to an embodiment of the present invention.
  • the controller is connected to multiple LNSs on the LNS side, and the controller is connected to an AAA server on the LAC side.
  • the controller includes:
  • the receiving module 301 is configured to perform step 201 of the foregoing embodiment
  • the processing module 302 is configured to perform step 202 of the foregoing embodiment
  • the sending module 303 is configured to perform step 203 of the foregoing embodiment.
  • a controller is introduced between the LAC side and the LNS side, and the controller can monitor the device status of each LNS in the LNS side by receiving device information from each LNS of the multiple LNSs. And determining, according to the LNS device information, the unavailable LNS in the multiple LNSs, and sending the first notification message of the identifier of the tunnel interface carrying the unavailable LNS to the AAA server on the LAC side, notifying that the AAA server on the LAC side is unavailable.
  • the identifier of the tunnel interface of the LNS is deleted from the stored interface information list, and the updated interface information list is obtained.
  • the LNS corresponding to the identifier of all tunnel interfaces included in the updated interface information list is available, and the tunnel interface of the available LNS is also available.
  • any LNS selected and any tunnel interface are also available, thereby solving the problem that the selected LNS or tunnel interface may not meet the working condition.
  • the problem that the tunnel cannot be established or the quality of the established tunnel is poor, and the success rate and stability of the tunnel establishment are improved.
  • the above receiving module and the sending module may be transmitters, and the receiving module and the sending module may be integrated in one transceiver module, and implemented as a transceiver corresponding to hardware.
  • the above processing module may be embedded in or independent of the processor of the controller in hardware, or may be stored in the memory of the controller in software, so that the processor calls to perform operations corresponding to the above modules.
  • the processor can be a central processing unit (CPU), a microprocessor, a microcontroller, or the like.
  • FIG. 4 is a schematic structural diagram of an AAA server according to an embodiment of the present invention.
  • the AAA server is connected to a controller and a plurality of LACs on the LAC side, and the controller is respectively connected to multiple LNSs on the LNS side.
  • the AAA server includes:
  • the receiving module 401 and the processing module 402 are configured to perform step 204 of the above embodiment.
  • the AAA server further includes:
  • the sending module is configured to perform step 206 of the above embodiment.
  • the AAA server may receive the first notification message sent by the controller, and according to the identifier of the tunnel interface of the unavailable LNS carried in the first notification message, remove the identifier of the tunnel interface of the LNS from the stored interface information. Remove from the list.
  • the LNS corresponding to the identifier of all tunnel interfaces included in the updated interface information list is available, and the tunnel interface of the available LNS is also available. Therefore, when the LAC selects the LNS and the tunnel interface based on the updated interface information list, any LNS selected and any tunnel interface are also available, thereby solving the problem that the selected LNS or tunnel interface may not meet the working condition.
  • the problem that the tunnel cannot be established or the quality of the established tunnel is poor, and the success rate and stability of the tunnel establishment are improved.
  • the above receiving module and the sending module may be transmitters, and the receiving module and the sending module may be integrated in one transceiver module, and implemented as a transceiver corresponding to hardware.
  • the above processing module may be embedded in or independent of the processor of the controller in hardware, or may be stored in the memory of the controller in software, so that the processor calls to perform operations corresponding to the above modules.
  • the processor can be a central processing unit (CPU), a microprocessor, a microcontroller, or the like.
  • the controller and the AAA server provided by the foregoing embodiments are only illustrated by the foregoing division of each functional module. In actual applications, the foregoing functions may be allocated according to requirements. Different functional modules are completed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.
  • the controller and the AAA server provided by the foregoing embodiments are in the same concept as the L2TP-based device management method embodiment, and the specific implementation process is described in detail in the method embodiment, and details are not described herein again.
  • a person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium.
  • the storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention se rapporte au domaine technique des réseaux. L'invention concerne un procédé, un appareil et un système de gestion de dispositifs basés sur un protocole d'acheminement couche deux (L2TP). Le procédé comprend les étapes suivantes : la réception d'informations de dispositif de chaque serveur de réseau L2TP (LNS) d'une pluralité de LNS à partir d'un côté LNS, les informations de dispositif comprenant un identifiant de dispositif et des informations d'état de dispositif du LNS correspondant ; la détermination d'un LNS indisponible de la pluralité de LNS en fonction des informations de dispositif de chaque LNS de la pluralité de LNS ; la transmission d'un premier message de notification à un serveur d'authentification, d'autorisation et de comptabilité (AAA) côté LAC, le premier message de notification portant une identification d'une interface tunnel du LNS indisponible, pour donner l'instruction au serveur AAA de supprimer l'identification de l'interface tunnel du LNS indisponible à partir d'une liste d'informations d'interface stockée. Lorsque l'identification de l'interface tunnel du LNS indisponible a été supprimée de la liste d'informations d'interface, lors de la sélection d'un LNS et d'une interface tunnel sur la base de la liste d'informations d'interface mise à jour, un quelconque LNS sélectionné et une quelconque interface tunnel sélectionnée seront donc disponibles, ce qui permet de traiter le problème selon lequel un LNS sélectionné ou une interface tunnel sélectionnée ne peut pas satisfaire les conditions de fonctionnement et permet d'augmenter le taux de réussite de l'établissement du tunnel.
PCT/CN2017/114824 2016-12-08 2017-12-06 Procédé, appareil et système de gestion de dispositifs basés sur un l2tp WO2018103665A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201611121163.0 2016-12-08
CN201611121163.0A CN108183849B (zh) 2016-12-08 2016-12-08 基于l2tp的设备管理方法、设备及系统

Publications (1)

Publication Number Publication Date
WO2018103665A1 true WO2018103665A1 (fr) 2018-06-14

Family

ID=62491728

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/114824 WO2018103665A1 (fr) 2016-12-08 2017-12-06 Procédé, appareil et système de gestion de dispositifs basés sur un l2tp

Country Status (2)

Country Link
CN (1) CN108183849B (fr)
WO (1) WO2018103665A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109327376A (zh) * 2018-11-15 2019-02-12 北京首信科技股份有限公司 建立虚拟专用拨号网络会话的方法和装置
CN113055835A (zh) * 2019-12-10 2021-06-29 中国电信股份有限公司 车载应用流量处理方法、装置和系统

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109617778B (zh) * 2018-11-22 2021-05-18 西安佰才邦网络技术有限公司 跨域二层网络业务的实现方法、装置和系统
CN110636464B (zh) * 2019-09-29 2021-05-18 广西东信易联科技有限公司 一种物联网设备间通信及与企业内网的通信系统
CN116170297B (zh) * 2023-04-23 2023-07-14 北京首信科技股份有限公司 一种网络接入认证中lns网元监控的方法和装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1617541A (zh) * 2004-09-30 2005-05-18 上海金诺网络安全技术发展股份有限公司 一种虚拟专用拨号网络的实现方法
CN101163085A (zh) * 2007-11-16 2008-04-16 中国联合通信有限公司 一种CDMA 1x LNS负载均衡的实现方法及系统
US20090034451A1 (en) * 2007-08-03 2009-02-05 Utstarcom, Inc. System and method for handling QoS flows in a roaming scenario
EP2028793A1 (fr) * 2007-08-21 2009-02-25 Nokia Siemens Networks Oy Dispositif de médiation et procédé pour adapter une première connexion vers une deuxième connexion dans un réseau de communication
CN102523583A (zh) * 2011-12-07 2012-06-27 福建星网锐捷网络有限公司 一种vpdn多接入点备份接入方法和设备

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103634189A (zh) * 2012-08-29 2014-03-12 中兴通讯股份有限公司 L2tp隧道的建立方法及系统
CN105591869B (zh) * 2015-07-22 2019-03-01 新华三技术有限公司 一种选择二层隧道协议网络服务器的方法和装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1617541A (zh) * 2004-09-30 2005-05-18 上海金诺网络安全技术发展股份有限公司 一种虚拟专用拨号网络的实现方法
US20090034451A1 (en) * 2007-08-03 2009-02-05 Utstarcom, Inc. System and method for handling QoS flows in a roaming scenario
EP2028793A1 (fr) * 2007-08-21 2009-02-25 Nokia Siemens Networks Oy Dispositif de médiation et procédé pour adapter une première connexion vers une deuxième connexion dans un réseau de communication
CN101163085A (zh) * 2007-11-16 2008-04-16 中国联合通信有限公司 一种CDMA 1x LNS负载均衡的实现方法及系统
CN102523583A (zh) * 2011-12-07 2012-06-27 福建星网锐捷网络有限公司 一种vpdn多接入点备份接入方法和设备

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109327376A (zh) * 2018-11-15 2019-02-12 北京首信科技股份有限公司 建立虚拟专用拨号网络会话的方法和装置
CN113055835A (zh) * 2019-12-10 2021-06-29 中国电信股份有限公司 车载应用流量处理方法、装置和系统
CN113055835B (zh) * 2019-12-10 2022-11-08 中国电信股份有限公司 车载应用流量处理方法、装置和系统

Also Published As

Publication number Publication date
CN108183849A (zh) 2018-06-19
CN108183849B (zh) 2021-01-08

Similar Documents

Publication Publication Date Title
US12260264B2 (en) Edge service providing method and apparatus, and device by utilizing resources based on geographical coverage
EP3745645B1 (fr) Procédé, dispositif et système pour garantir un accord de niveau de service d'une application
US11038972B2 (en) Service providing method, apparatus, and system
US10601728B2 (en) Software-defined data center and service cluster scheduling and traffic monitoring method therefor
US11237858B2 (en) Software-defined data center, and deployment method for service cluster therein
US11032105B2 (en) Method for implementing GRE tunnel, home gateway and aggregation gateway
EP3827577B1 (fr) Système et procédé de gestion intelligente de sessions dans un réseau mobile
CN110896371B (zh) 一种虚拟网络设备及相关方法
US11588679B2 (en) System and method of establishing seamless remote access virtual private network connections
EP3565182B1 (fr) Procédé de gestion de découpage de réseau en tranches, et unité de gestion et système
WO2018103665A1 (fr) Procédé, appareil et système de gestion de dispositifs basés sur un l2tp
CN106657330B (zh) 用户数据迁移方法和用户数据备份方法、装置及系统
US11251981B2 (en) Communication method and apparatus
JP2021518094A (ja) 課金方法、装置およびシステム
CN113825251B (zh) 会话建立方法、装置、系统及计算机存储介质
CN109842507B (zh) 一种网络切片管理方法及设备
KR20140052397A (ko) 이동 통신 시스템에서 가상 머신 관리 장치 및 방법
CN104703165A (zh) 一种处理无线接入的方法、转发设备及网络控制器
CN102239670A (zh) 一种负载分担方法和装置
WO2019018472A1 (fr) Procédés, systèmes et supports lisibles par ordinateur pour faire fonctionner un réseau de télécommunications à l'aide d'un système informatique sur site et d'un système informatique en nuage hors site
WO2023035925A1 (fr) Procédé, appareil et système de traitement de service
WO2018177003A1 (fr) Procédé de facturation, et dispositif et système associés
US20250132973A1 (en) Virtual internet protocol address associated with subscriber group
CN115622869A (zh) 数据处理方法、装置、设备、存储介质和系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17878060

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17878060

Country of ref document: EP

Kind code of ref document: A1

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载