Method and apparatus for establishing communication

Abstract

The application discloses a method and device for establishing communication, relates to the technical field of communication, and can quickly establish communication between a LAC forwarding entity and a LNS forwarding entity in a control plane entity co-management LAC forwarding entity and LNS forwarding entity scenario. The method is applied to a network device for managing a Layer 2 Tunnel Protocol Access Concentrator (LAC) forwarding entity. The method comprises the following steps: determining that the network device manages a Layer 2 Tunnel Protocol Network Server (LNS) forwarding entity; in response to the determination that the network device manages the LNS forwarding entity, generating first forwarding information and second forwarding information; sending the first forwarding information to the LAC forwarding entity and sending the second forwarding information to the LNS forwarding entity. The first forwarding information and the second forwarding information are used to realize communication between the LAC forwarding entity and the LNS forwarding entity.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method and apparatus for establishing communication. Background Technology

[0002] A Layer 2 tunneling protocol (L2TP) typically includes a client, an L2TP access concentrator (LAC), and an L2TP network server (LNS). The LAC is responsible for connecting the client to the LNS and forwarding messages between the LNS and the client. The LNS is usually connected to an Internet Service Provider (ISP). Once a communication connection is established between the client and the LNS, the client can access the ISP's services.

[0003] With the development of Software Defined Networking (SDN) and Network Functions Virtualization (NFV) technologies, LAC and LNS have gradually achieved decoupling of the control plane (CP) and user plane (UP), i.e., CU separation. Here, the CP can implement its functions through a control plane entity, and the UP can implement its functions through a forwarding plane entity. Specifically, the control plane entity can be used to uniformly manage at least one LAC forwarding plane entity and at least one LNS forwarding plane entity; in other words, the control plane entity can co-manage at least one LAC forwarding plane entity and at least one LNS forwarding plane entity.

[0004] Therefore, in scenarios where control plane entities co-manage LAC forwarding plane entities and LNS forwarding plane entities, how to quickly establish communication between LAC forwarding plane entities and LNS forwarding plane entities is an urgent technical problem to be solved. Summary of the Invention

[0005] This application provides a method and apparatus for establishing communication. The method can quickly establish communication between LAC forwarding plane entities and LNS forwarding plane entities in scenarios where control plane entities co-manage LAC forwarding plane entities and LNS forwarding plane entities.

[0006] To achieve the above objectives, this application provides the following technical solution:

[0007] In a first aspect, this application provides a method for establishing communication, applied to a network device for managing LAC forwarding plane entities. The method includes: determining that the network device manages an LNS forwarding plane entity; generating first forwarding information and second forwarding information in response to determining that the network device manages the LNS forwarding plane entity; sending the first forwarding information to the LAC forwarding plane entity and sending the second forwarding information to the LNS forwarding plane entity. The first and second forwarding information are used to enable communication between the LAC forwarding plane entity and the LNS forwarding plane entity.

[0008] The method provided in this application can directly generate first and second forwarding information when a network device is determined to be a co-managed LAC forwarding plane entity and LNS forwarding plane entity. The first forwarding information is then sent to the LAC forwarding plane entity, and the second forwarding information is sent to the LNS forwarding plane entity. In this way, communication between the LAC and LNS forwarding plane entities can be quickly established based on the first and second forwarding information. This method eliminates the need for multiple transmissions of L2TP tunnel protocol messages between the co-managed network devices, the LAC forwarding plane entity, and the LNS forwarding plane entity to achieve communication between them. This significantly improves the efficiency of establishing communication between the LAC and LNS forwarding plane entities, thereby improving the efficiency of user access to the LNS, enhancing user online performance, and reducing system resource consumption.

[0009] In one possible design approach, the aforementioned "determining the network device management LNS forwarding plane entity" includes: determining that the Internet Protocol (IP) address of the LNS forwarding plane entity is within the IP address range managed by the network device.

[0010] In another possible design approach, the aforementioned "determining that the IP address of the LNS forwarding plane entity is within the IP address range managed by the network device" includes: determining the IP address of the LNS forwarding plane entity based on the aforementioned access request; and determining that the IP address of the LNS forwarding plane entity is within the IP address range managed by the network device based on the IP address of the LNS forwarding plane entity and the address resource pool. The address resource pool includes the IP addresses of forwarding plane entities managed by the network device.

[0011] This possible design allows for the identification of shared LAC forwarding plane entities and LNS forwarding plane entities within the network devices. The network devices can then directly generate first and second forwarding information, sending the first forwarding information to the LAC forwarding plane entity and the second forwarding information to the LNS forwarding plane entity. This enables rapid communication between the LAC and LNS forwarding plane entities based on the first and second forwarding information. This method eliminates the need for multiple transmissions of L2TP tunnel protocol messages between the network devices, the LAC forwarding plane entity, and the LNS forwarding plane entity, significantly improving the efficiency of establishing communication between them. This, in turn, improves the efficiency of user access to the LNS, enhances user online performance, and reduces system resource consumption.

[0012] In another possible design, the first forwarding information mentioned above includes a first tunnel identifier, which is used by the LAC forwarding plane entity to send a message to the LNS forwarding plane entity, and the message sent by the LAC forwarding plane entity to the LNS forwarding plane entity contains the first tunnel identifier.

[0013] In another possible design, the second forwarding information mentioned above includes a second tunnel identifier, which is used by the LNS forwarding plane entity to send a message to the LAC forwarding plane entity. The message sent by the LNS forwarding plane entity to the LAC forwarding plane entity contains the second tunnel identifier.

[0014] These two possible designs enable the rapid establishment of tunnels between the LAC forwarding plane entity and the LNS forwarding plane entity to achieve communication.

[0015] In another possible design, the first forwarding information mentioned above also includes a first session identifier, which is included in the message sent by the LAC forwarding plane entity to the LNS forwarding plane entity.

[0016] In another possible design, the second forwarding information mentioned above also includes a second session identifier, which is included in the message sent by the LNS forwarding plane entity to the LAC forwarding plane entity.

[0017] These two possible designs enable the LAC forwarding plane entity and the LNS forwarding plane entity to quickly establish a session on the aforementioned tunnel to achieve communication.

[0018] In another possible design, the network device described above includes an LAC control plane component and an LNS control plane component. Then, the aforementioned "generating first forwarding information and second forwarding information" includes: generating the first forwarding information and the second forwarding information through interactive communication between the LAC control plane component and the LNS control plane component.

[0019] The LAC control plane component and the LNS control plane component communicate with each other, including the LAC control plane component receiving a first tunnel identifier from the LNS control plane component; and the LNS control plane component receiving a second tunnel identifier from the LAC control plane component.

[0020] Through these two possible implementations, the communication establishment method provided in this application can, when a network device is determined to be a control plane entity co-managing both the LAC forwarding plane entity and the LNS forwarding plane entity, generate first forwarding information and second forwarding information through interactive communication between the LAC control plane component and the LNS control plane component in the network device. The network device then sends the first forwarding information to the LAC forwarding plane entity and the second forwarding information to the LNS forwarding plane entity. Thus, communication between the LAC forwarding plane entity and the LNS forwarding plane entity can be achieved based on the first and second forwarding information. This method eliminates the need for multiple transmissions of L2TP tunnel protocol messages between the network device co-managing the LAC and LNS forwarding plane entities, the LAC forwarding plane entity, and the LNS forwarding plane entity to achieve communication between them. This significantly improves the efficiency of establishing communication between the LAC and LNS forwarding plane entities, thereby improving the efficiency of user access to the LNS, enhancing user online performance, and reducing system resource consumption.

[0021] In another possible design, prior to generating the first and second forwarding information, the method further includes obtaining an access request from the user terminal. Based on the access request, if it is determined that the user terminal is an L2TP type user terminal, then the access request is used to indicate that the user terminal requests communication with the LNS control plane entity.

[0022] In another possible design approach, the aforementioned "determining that the user terminal is an L2TP type user terminal based on the access request" specifically includes: obtaining the domain name carried in the access request; and determining that the user terminal is an L2TP type user terminal based on the obtained domain name.

[0023] In another possible design, before “sending the first forwarding information to the LAC forwarding plane entity and the second forwarding information to the LNS forwarding plane entity”, the method further includes: determining the route reachability between the LAC forwarding plane entity and the LNS forwarding plane entity.

[0024] Secondly, this application provides an apparatus for establishing communication.

[0025] In one possible design, the communication establishment device is used to execute any of the methods provided in the first aspect. This application can divide the communication establishment device into functional modules according to any of the methods provided in the first aspect. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. For example, this application can divide the communication establishment device into a determining unit, a generating unit, and a sending unit, etc., according to function. The descriptions of the possible technical solutions and beneficial effects performed by the various functional modules described above can be found in the technical solutions provided in the first aspect or its corresponding possible designs, and will not be repeated here.

[0026] In another possible design, the means of establishing communication includes a memory and one or more processors, the memory and processors being coupled. The memory is used to store computer instructions, and the processor is used to invoke the computer instructions to perform any of the methods provided by the first aspect and any of its possible design embodiments.

[0027] Thirdly, this application provides a computer-readable storage medium, such as a non-transient computer-readable storage medium. A computer program (or instructions) is stored thereon, which, when executed on a means of establishing communication, causes the means of establishing communication to perform any method provided by any possible implementation of the first aspect described above.

[0028] Fourthly, this application provides a computer program product that, when run on a means of establishing communication, causes any method provided by any possible implementation of the first aspect to be executed.

[0029] Fifthly, this application provides a chip system comprising: a processor, the processor being configured to retrieve and execute a computer program stored in a memory, performing any of the methods provided in the implementation of the first aspect.

[0030] It is understood that any of the devices, computer storage media, computer program products or chip systems provided above can be applied to the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0031] In this application, the names of the aforementioned communication establishment devices do not limit the devices or functional modules themselves. In actual implementation, these devices or functional modules may appear under other names. As long as the functions of each device or functional module are similar to those in this application, they fall within the scope of the claims of this application and their equivalents.

[0032] These or other aspects of this application will become more readily apparent in the following description. Attached Figure Description

[0033] Figure 1 This is a schematic diagram of a method for establishing an L2TP tunnel between an LAC forwarding plane entity and an LNS forwarding plane entity in the prior art.

[0034] Figure 2 A schematic diagram of the hardware structure of a communication establishment device provided in an embodiment of this application;

[0035] Figure 3 A schematic diagram of a network architecture provided in an embodiment of this application;

[0036] Figure 4 A schematic diagram of another network architecture provided for an embodiment of this application;

[0037] Figure 5 This is a schematic flowchart illustrating a method for establishing communication, as provided in an embodiment of this application.

[0038] Figure 6 A schematic diagram illustrating the interactive communication between the LAC control plane component and the LNS control plane component in the control plane entity provided in the embodiments of this application;

[0039] Figure 7 A schematic diagram of a communication establishment device provided in an embodiment of this application;

[0040] Figure 8 This is a schematic diagram of the structure of a chip system provided in an embodiment of this application;

[0041] Figure 9 This is a schematic diagram of the structure of a computer program product provided in an embodiment of this application. Detailed Implementation

[0042] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0043] In the embodiments of this application, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0044] In this application, the term "at least one" means one or more, and the term "multiple" means two or more. For example, multiple second messages refer to two or more second messages. The terms "system" and "network" are often used interchangeably in this document.

[0045] It should also be understood that, in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0046] It should be understood that determining B based on A does not mean determining B solely based on A; B can also be determined based on A and / or other information.

[0047] It should also be understood that the term “comprising” (also referred to as “includes”, “including”, “comprises” and / or “comprising”) as used in this specification specifies the presence of the stated features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0048] It should also be understood that the term "if" can be interpreted as meaning "when" or "upon" or "in response to determination" or "in response to detection." Similarly, depending on the context, the phrases "if determination..." or "if detection [the stated condition or event]" can be interpreted as meaning "when determination..." or "in response to determination..." or "when detection [the stated condition or event]" or "in response to detection [the stated condition or event]."

[0049] L2TP is a tunneling protocol typically set up for transmitting point-to-point protocol (PPP) messages between user terminals and enterprise servers. It is an extension of the PPP protocol.

[0050] L2TP typically includes two types of connections: tunnel connections and session connections. At least one tunnel can be established between a LAC and an LNS. At least one session can be established on each tunnel between the LAC and the LNS.

[0051] Once the LAC establishes a tunnel connection and a session connection between the LAC and the LNS based on the user's access request, the user can communicate with the LNS through the LAC and based on the tunnel connection and session connection. In other words, the LAC connects the user to the LNS by establishing a tunnel connection and a session connection between the LAC and the LNS.

[0052] In traditional methods, when control plane entities co-manage LAC forwarding plane entities and LNS forwarding plane entities, it is typically necessary to transmit (e.g., transparently transmit) L2TP tunneling protocol messages via a virtual extended local area network (VxLAN) between the control plane entities, LAC forwarding plane entities, and LNS forwarding plane entities to establish an L2TP tunnel between the LAC forwarding plane entities and the LNS forwarding plane entities. Based on this L2TP tunnel, communication can then occur between the LAC forwarding plane entities and the LNS forwarding plane entities.

[0053] As an example, refer to Figure 1 , Figure 1 A schematic diagram illustrating a method for establishing an L2TP tunnel between an LAC forwarding plane entity and an LNS forwarding plane entity is shown. Figure 1 As shown, the control plane entity can encapsulate a start control connection request (SCCRQ) message based on the user's access request and send it to the LAC forwarding plane entity via VxLAN. The LAC forwarding plane entity then forwards the received SCCRQ message to the LNS forwarding plane entity. Finally, the LNS forwarding plane entity, upon receiving the SCCRQ message, forwards it to the control plane entity via VxLAN.

[0054] When the control plane entity receives and processes the SCCRQ protocol message, it sends a start control connection reply (SCCRP) message to the LNS forwarding plane entity via VxLAN. The LNS forwarding plane entity then forwards the SCCRP message to the LAC forwarding plane entity. Upon receiving the SCCRP message, the LAC forwarding plane entity then forwards it to the control plane entity. This completes one interaction of the L2TP tunneling protocol messages.

[0055] Then, similarly, after receiving and processing the SCCRP message, the control plane entity sends a start control connection connected (SCCCN) message to the LNS forwarding plane entity via the LAC forwarding plane entity. Finally, when the LNS forwarding plane entity receives the SCCCN message, it forwards the SCCCN message to the control plane entity, thus completing the establishment of the L2TP tunnel between the LAC forwarding plane entity and the LNS forwarding plane entity.

[0056] Similarly, control plane entities can be accessed through... Figure 1 The method shown establishes a session connection between the LAC forwarding plane entity and the LNS forwarding plane entity based on the existing L2TP tunnel between them. This is achieved by transmitting L2TP session protocol messages between the control plane entity, the LAC forwarding plane entity, and the LNS forwarding plane entity. Details are omitted here. In this way, the user terminal can communicate with the LNS via the LAC forwarding plane entity and this session connection.

[0057] However, through Figure 1 The method shown requires multiple decapsulation and forwarding of messages to determine the tunnel identifier used to establish the L2TP tunnel (or the session identifier used to establish the L2TP session) when establishing a tunnel (or session) for communication. This makes the interaction process of establishing a tunnel (or session) between the LAC forwarding plane entity and the LNS forwarding plane entity complex and lengthy, which greatly affects the efficiency of user terminal access to LNS, i.e., poor user terminal online performance.

[0058] Based on this, embodiments of this application provide a method for establishing communication, applied to a network device used to manage the LAC forwarding plane entity in a CU-separated LAC. When it is determined that the network device is also used to manage the LNS forwarding plane entity in a CU-separated LNS, that is, when the network device, as a control plane entity, jointly manages the LAC forwarding plane entity and the LNS forwarding plane entity, the network device can generate first forwarding information and second forwarding information, and directly send the first forwarding information to the LAC forwarding plane entity and the second forwarding information to the LNS forwarding plane entity. In this way, the forwarding plane entity of the LAC and the forwarding plane entity of the LNS can quickly achieve communication based on the first forwarding information and the second forwarding information.

[0059] The first forwarding information includes a first tunnel identifier for sending messages from the LAC forwarding plane entity to the LNS forwarding plane entity, and the second forwarding information includes a second tunnel identifier for sending messages from the LNS forwarding plane entity to the LAC forwarding plane entity. Thus, compared to... Figure 1The method shown in this application embodiment does not require multiple packet forwardings between the control plane entity, LAC forwarding plane entity, and LNS forwarding plane entity to establish an L2TP tunnel, thereby enabling communication between the LAC forwarding plane entity and the LNS forwarding plane entity. Therefore, the method provided in this application embodiment improves the efficiency of user access to LNS and enhances the online performance of the user terminal.

[0060] Typically, both LAC and LNS can be any device that supports PPP and L2TP protocol processing capabilities, such as computer equipment, routers, or switches.

[0061] For the LAC forwarding plane entity of the LAC with CU separation and the LNS forwarding plane entity of the LNS with CU separation, the LAC forwarding plane entity and the LNS forwarding plane entity can still use devices in the existing network that support PPP and L2TP protocol processing capabilities to implement their functions. For example, the device can be a computer, router, or switch.

[0062] This application provides an apparatus for establishing communication. This apparatus can be applied to a network device, which serves as a network device for managing the LAC forwarding plane entity in a CU-separated LAC as a control plane entity. This network device can also be used to manage the LNS forwarding plane entity in a CU-separated LNS.

[0063] The network device can be any computing device with computing capabilities, such as a computer or server, without limitation.

[0064] refer to Figure 2 , Figure 2 A schematic diagram of the hardware structure of the communication establishment apparatus 20 provided in an embodiment of this application is shown. Figure 2 As shown, the communication establishment device 20 includes a processor 21, a memory 22, a communication interface 23, and a bus 24. The processor 21, the memory 22, and the communication interface 23 can be connected via the bus 24.

[0065] The processor 21 is the control center of the communication device 20. It can be a general-purpose central processing unit (CPU) or other general-purpose processors. The general-purpose processor can be a microprocessor or any conventional processor.

[0066] As an example, processor 21 may include multiple CPUs, for example Figure 2The CPUs shown are CPU 0 and CPU 1. CPU 0 may be the processor of the LAC control plane component in the communication establishment device 20, and CPU 1 may be the processor of the LNS control plane component in the communication establishment device 20; there is no limitation on this.

[0067] The memory 22 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.

[0068] In one possible implementation, the memory 22 can exist independently of the processor 21. The memory 22 can be connected to the processor 21 via a bus 24 and is used to store data, instructions, or program code. When the processor 21 calls and executes the instructions or program code stored in the memory 22, it can implement the communication establishment method provided in the embodiments of this application.

[0069] In another possible implementation, the memory 22 can also be integrated with the processor 21.

[0070] Communication interface 23 is used to establish communication between the device 20 and other devices (such as LAC forwarding plane entities, LNS forwarding plane entities, etc.) via a communication network. This communication network can be Ethernet, radio access network (RAN), wireless local area network (WLAN), etc. Communication interface 23 may include a receiving unit for receiving data and a transmitting unit for sending data.

[0071] Bus 24 can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 2 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0072] It should be pointed out that, Figure 2 The structure shown does not constitute a limitation on the device for establishing communication, except... Figure 2 In addition to the components shown, the communication establishment device 20 may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0073] Based on the separation of CU (Control Unit) and LAC (Low-Card Area) and LNS (Low-Novice), this application also provides a network architecture. This network architecture is one in which network devices, as control plane entities, jointly manage both the LAC forwarding plane entity and the LNS forwarding plane entity. Through this network architecture, user terminals can access the LNS via the LAC to achieve communication between the user terminal and the LNS.

[0074] like Figure 3 As shown, Figure 3 This application illustrates a network architecture 30 provided in an embodiment. The network architecture 30 includes a control plane control (CU) 31 and a network management system (LNS) 32. Here, the CU 31 includes an CU forwarding plane entity 311 and a network device 33, and the LNS 32 includes an LNS forwarding plane entity 321 and a network device 33. It is evident that the network device 33, as a control plane entity, uniformly manages both the CU forwarding plane entity 311 and the LNS forwarding plane entity 321; that is, the network device 33 jointly manages both the CU forwarding plane entity 311 and the LNS forwarding plane entity 321.

[0075] Network device 33 is used to implement the control functions of LAC 31 and LNS 32. For example, network device 33 can be used to control the establishment of a communication link between LAC forwarding plane entity 311 and user terminal 34, which can typically be a PPP link.

[0076] Network device 33 can also be used to control the establishment of a communication connection between LAC forwarding plane entity 311 and LNS forwarding plane entity 321. Here, the process of establishing a communication connection between LAC forwarding plane entity 311 and LNS forwarding plane entity 321 can be referred to the description of the method below, and will not be repeated here.

[0077] In this way, once the communication links between LAC forwarding plane entity 311 and user terminal 34, and between LAC forwarding plane entity 311 and LNS forwarding plane entity 321 are established, user terminal 34 can communicate with LNS forwarding plane entity 321 through the communication links between LAC forwarding plane entity 311 and user terminal 34, and between LAC forwarding plane entity 311 and LNS forwarding plane entity 321.

[0078] LAC forwarding plane entity 311 is connected to network device 33 and is used to implement the forwarding function of LAC 31. LNS forwarding plane entity 321 is connected to network device 33 and is used to implement the forwarding function of LNS 32.

[0079] For example, LAC forwarding plane entity 311 can be used to forward access request packets sent by user terminal 34 to network device 33, or LAC forwarding plane entity 311 can be used to forward session packets sent by user terminal 34 to LNS forwarding plane entity 321, and so on.

[0080] For example, LNS forwarding plane entity 321 can be used to forward session messages sent by user terminal 34 via LAC forwarding plane entity 311 to the server, or LNS forwarding plane entity 321 can be used to forward response messages returned by the server to user terminal 34 to LAC forwarding plane entity 311, and so on.

[0081] It should be understood that the LNS forwarding plane entity can typically connect and communicate with the servers (such as enterprise servers) of ISPs that provide various services. In this way, the user terminal 34 can access the ISP through the LAC forwarding plane entity 311 and the LNS forwarding plane entity 321.

[0082] refer to Figure 4 , Figure 4 Another network architecture 40 provided in this application embodiment is illustrated. This network architecture 40 includes user terminals 411, 412, and 413, and an LAC 42. Here, user terminals 411, 412, and 413 are connected to the LAC 42. User terminals 411, 412, and 413 can communicate with the LAC 42 through an access network. As an example, this access network can be a network supporting the PPP protocol.

[0083] The network architecture 40 also includes LNS 431 and LNS 432. Here, LNS 431 and LNS 432 are respectively routeable to LAC 42. LNS 431 and LNS 432 can communicate with LAC 42 via a network connection supporting the L2TP protocol. As an example, this network could be a multi-protocol label switching (MPLS) network.

[0084] The network architecture 40 also includes IPS 531 and IPS 532. IPS 531 communicates with LNS 431, and IPS 532 communicates with LNS 432. Optionally, LNS 431 can be a gateway node for IPS 531, and LNS 432 can be a gateway node for IPS 532.

[0085] As can be seen, in network architecture 40, user terminal 411 can access LNS 431 connected to IPS 531 via LAC 42, thereby enabling user terminal 411 to access IPS 531. Similarly, user terminal 411 can also access LNS 432 connected to IPS 532 via LAC 42, thereby enabling user terminal 412 to access IPS 532. Further details are omitted.

[0086] The method for establishing communication provided in the embodiments of this application will be described below with reference to the accompanying drawings.

[0087] refer to Figure 5 , Figure 5 A flowchart illustrating a method for establishing communication according to an embodiment of this application is shown. This method is applied to a network device, which acts as a control plane entity to manage the LAC forwarding plane entity in a CU-separated LAC. The LAC forwarding plane entity implements the forwarding function of the CU-separated LAC, and the network device implements the control function of the CU-separated LAC. The method may include the following steps:

[0088] S101, The network device receives an access request from the user.

[0089] The access request includes the user's identity identifier and domain name. Here, the identity identifier represents the user's identity; for example, it can be a username or a Media Access Control Address (MAC). The domain name can be used to determine the user type of the user. It should be understood that the user's domain name can exist as part of the user's username, and this embodiment of the application does not specifically limit this.

[0090] For example, the username on the user terminal could be kk@l2tp, where l2tp is the domain name of the user terminal.

[0091] Typically, a user can initiate a network access process by sending an access request to the network device via the LAC forwarding plane entity. The network device can then receive the access request.

[0092] For example, the user terminal can initiate a point-to-point protocol over Ethernet (PPPoE) dial-up process by carrying a username and domain name, thereby sending an access request to the network device of the LAC. Correspondingly, the network device receives the access request from the user terminal.

[0093] S102. If the network device determines that the above-mentioned user terminal is an L2TP type user terminal based on the obtained access request, then the access request is used to instruct the user terminal to request communication with the LNS forwarding plane entity.

[0094] In this context, L2TP-type client refers to a client that needs to transmit data through an L2TP connection. The access request initiated by an L2TP-type client typically carries username or domain name information. Based on this username or domain name information, the L2TP-type client can establish communication with the LNS.

[0095] Optionally, the network device can parse the obtained access request to identify the domain name of the user carried in the access request.

[0096] Then, based on the identified domain name, the network device determines in its preset configuration whether to include the L2TP configuration group corresponding to that domain name. Here, the L2TP configuration group is configured with the Internet Protocol (IP) address of the LNS forwarding plane entity, which can be the IP address corresponding to any tunnel source interface of the LNS forwarding plane entity.

[0097] When a network device determines in its preset configuration that it includes the L2TP configuration group corresponding to a domain name, the network device determines that the client corresponding to that domain name is an L2TP type client.

[0098] In this way, network devices can determine the IP address of the LNS forwarding plane entity based on the configuration parameters of the L2TP configuration group. In this case, it indicates that the above access request is used to instruct the user terminal to request communication with the LNS forwarding plane entity indicated by the IP address.

[0099] It should be understood that when configuring the IP address of the LNS forwarding plane entity in the L2TP configuration group, the network device can configure the IP address of the LNS forwarding plane entity in the L2TP configuration group according to preset rules.

[0100] Here, the preset rule could be to configure the IP address of the LNS forwarding plane entity of the LNS with the lowest load in the L2TP configuration group. Alternatively, the preset rule could be to configure the IP address of the LNS forwarding plane entity of the LNS closest to the user's location in the L2TP configuration group, and so on. It should be understood that the preset rule in this embodiment is not specifically limited.

[0101] S103 (optional): The network device determines that the route between the LAC forwarding plane entity and the aforementioned LNS forwarding plane entity is reachable.

[0102] Here, the LAC forwarding plane entity is the LAC forwarding plane entity in S101 used to forward access requests to network devices.

[0103] It should be understood that before establishing a communication connection between the LAC forwarding plane entity and the aforementioned LNS forwarding plane entity, the network device must first determine whether the route between the LAC forwarding plane entity and the LNS forwarding plane entity is reachable. This ensures that the LAC forwarding plane entity can successfully forward user packets to the LNS forwarding plane entity.

[0104] As described above, a network device can manage multiple forwarding plane entities. In this case, the network device can pre-obtain the IP address of at least one LAC forwarding plane entity managed by the network device, as well as the routing information corresponding to that IP address. The IP address can be the IP address of the tunnel source interface of each LAN forwarding plane entity.

[0105] Optionally, at least one LAC forwarding plane entity managed by the network device can pre-report the IP address of its respective tunnel source interface and the routing information corresponding to that IP address to the network device. In this way, the network device can obtain the IP address of the tunnel source interface of the at least one LAC forwarding plane entity and the routing information corresponding to that IP address.

[0106] In this embodiment, at least one LAC forwarding plane entity managed by the network device can report its own tunnel source interface IP address and the corresponding routing information to the network device at any time before the network device needs to determine whether a route between the LAC forwarding plane entity and the LNS forwarding plane entity is reachable. For example, at least one LAC forwarding plane entity managed by the network device can report its own tunnel source interface IP address and the corresponding routing information to the network device when networking with the network device. This embodiment does not specifically limit this.

[0107] Optionally, the IP address of the tunnel source interface of at least one LAC forwarding plane entity managed by the network device, and the routing information corresponding to that IP address, can be pre-configured in the network device. For example, it can be configured in the network device by manual input. Here, this embodiment of the application does not specifically limit the configuration method.

[0108] In this way, the network device can determine whether the route between the LAC forwarding plane entity and the LNS forwarding plane entity is reachable based on the IP address of the LNS forwarding plane entity determined in S102, the IP address of the tunnel source interface of the LAC forwarding plane entity obtained in advance, and the routing information corresponding to the IP address.

[0109] If the route is reachable, the network device can continue to execute the communication establishment method provided in the embodiments of this application; otherwise, the network device controls the communication connection between the LAC forwarding plane entity and the LNS forwarding plane entity to fail.

[0110] It is understood that in the embodiments of this application, S101-S103, the implementation is achieved through the LAC control plane component in the network device corresponding to the aforementioned LAC forwarding plane entity.

[0111] S104. The network device determines whether it is used to manage the aforementioned LNS forwarding plane entity.

[0112] Specifically, network devices can determine whether they are managing the aforementioned LNS forwarding plane entities by checking whether the IP address of the LNS forwarding plane entity is within the range of IP addresses managed by the network device.

[0113] Specifically, network devices can determine whether the IP address of an LNS forwarding plane entity is within the IP address range managed by the network device, based on the IP address of the LNS forwarding plane entity and the address resource pool mentioned above. The address resource pool includes the IP addresses of the forwarding plane entities managed by the network device.

[0114] If the network device determines that the IP address of the aforementioned LNS forwarding plane entity is within the address resource pool, then it determines that the IP address of the LNS forwarding plane entity is within the IP address range managed by the network device, that is, it determines that the network device manages the LNS forwarding plane entity. In other words, the network device jointly manages the aforementioned LAC forwarding plane entity and the LNS forwarding plane entity. In this case, the embodiments of this application can execute S105-S106.

[0115] If the network device determines that the IP address of the aforementioned LNS forwarding plane entity is not within the address resource pool, then it determines that the IP address of the LNS forwarding plane entity is not within the IP address range managed by the network device, that is, it determines that the LNS forwarding plane entity is not a forwarding plane device managed by the network device. In this case, the embodiment of this application can execute S107.

[0116] The network device is pre-configured with an address resource pool, which includes the IP addresses of at least one forwarding plane entity managed by the network device. Here, the IP address can be the IP address corresponding to any tunnel source interface of the at least one forwarding plane entity.

[0117] Optionally, at least one forwarding plane entity managed by the network device can pre-report its own IP address to the network device. In response, the network device can obtain these IP addresses. In this way, the network device can record the obtained IP addresses as an address resource pool.

[0118] In this embodiment, at least one forwarding plane entity managed by the network device can report its IP address to the network device at any time before the network device determines whether the IP address of the LNS forwarding plane entity is within the range of IP addresses managed by the network device based on the IP address of the aforementioned LNS forwarding plane entity and the address resource pool. For example, at least one forwarding plane entity managed by the network device can report its IP address to the network device when forming a network with the network device; this embodiment does not specifically limit this.

[0119] Optionally, the IP addresses of at least one forwarding plane entity managed by the network device can be pre-configured in the network device. For example, they can be configured in the network device by manual input. Here, this embodiment of the application does not specifically limit the configuration method. In this way, the network device can record the IP addresses corresponding to the pre-configured tunnel source interfaces as address resource pools.

[0120] It should be understood that network devices can obtain IP addresses from the address resource pool through the LNS control plane component corresponding to the aforementioned LNS forwarding plane entity. It should also be understood that the LAC control plane component in the network device can access this address resource pool. Thus, based on the determined IP address of the LNS forwarding plane entity, the network device can use the LAC control plane component to determine whether the address resource pool contains the IP address of that LNS forwarding plane entity.

[0121] S105. The network device generates first forwarding information and second forwarding information through interactive communication between the LAC control plane component and the LNS control plane component in the network device.

[0122] The LAC control plane component manages the aforementioned LAC forwarding plane entity, and the LNS control plane component manages the aforementioned LNS forwarding plane entity. The first forwarding information and the second forwarding information are used to enable communication between the LAC forwarding plane entity and the LNS forwarding plane entity.

[0123] The first forwarding information includes a first tunnel identifier, which is used by the LAC forwarding plane entity to send messages to the LNS forwarding plane entity. The messages sent by the LAC forwarding plane entity to the LNS forwarding plane entity contain the first tunnel identifier.

[0124] The second forwarding information includes a second tunnel identifier, which is used by the LNS forwarding plane entity to send messages to the LAC forwarding plane entity. The messages sent by the LNS forwarding plane entity to the LAC forwarding plane entity contain the second tunnel identifier.

[0125] The first tunnel identifier can be a tunnel identifier configured by the network device for the LNS forwarding plane entity through the LNS control plane component. The second tunnel identifier can be a tunnel identifier configured by the network device for the LAC forwarding plane entity through the LAC control plane component.

[0126] Optionally, the first tunnel identifier and the second tunnel identifier may be the same or different, and this application embodiment does not limit this.

[0127] Then, the network device can interact with the first tunnel identifier and the second tunnel identifier through the LAC control plane component and the LNS control plane component, so that the LAC control plane component can obtain the first tunnel identifier and generate first forwarding information based on the first tunnel identifier. And, the LNS control plane component can obtain the second tunnel identifier and generate second forwarding information based on the second tunnel identifier.

[0128] For example, refer to Figure 6 , Figure 6 An exemplary schematic diagram of the interactive tunnel identifier between the LAC control plane component 61 and the LNS control plane component 62 in network device 60 is shown.

[0129] like Figure 6 As shown, network device 60 can send the allocated second tunnel identifier to LNS control plane component 62 after allocating a second tunnel identifier to an LAC forwarding plane entity via LAC control plane component 61. In this way, LNS control plane component 62 can receive the second tunnel identifier. Then, network device 60 can allocate a first tunnel identifier corresponding to the second tunnel identifier to LNS forwarding plane entity via LNS control plane component 62.

[0130] Then, network device 60 can send the allocated first tunnel identifier to LAC control plane component 61 via LNS control plane component 62. Correspondingly, LAC control plane component 61 receives the first tunnel identifier. This completes one interactive communication between LAC control plane component 61 and LNS control plane component 62 in network device 60.

[0131] Thus, the LAC control plane component 61 in network device 60 can generate first forwarding information based on the first tunnel identifier received from the LNS control plane component 62. Similarly, the LNS control plane component 62 in network device 60 can generate second forwarding information based on the second tunnel identifier received from the LAC control plane component 61.

[0132] Optionally, the first forwarding information may also include a second tunnel identifier, which corresponds to a second session identifier. A description of the second session identifier can be found below and will not be repeated here.

[0133] Optionally, the second forwarding information may also include a first tunnel identifier, which corresponds to a first session identifier. A description of the first session identifier can be found below and will not be repeated here.

[0134] Optionally, the first forwarding message may also include a first session identifier. The message sent by the LAC forwarding plane entity to the LNS forwarding plane entity contains this first session identifier. The second forwarding message may also include a second session identifier. The message sent by the LNS forwarding plane entity to the LAC forwarding plane entity contains this second session identifier.

[0135] The process by which network devices allocate and interact with the first session identifier and the second session identifier through the LAC control plane component and the LNS control plane component can be referred to the process above for network devices allocating and interacting with the first tunnel identifier and the second tunnel identifier through the LAC control plane component and the LNS control plane component, and will not be repeated here.

[0136] Optionally, the first session identifier and the second session identifier may be the same or different, and this application embodiment does not limit this.

[0137] Optionally, the first forwarding information may also include a second session identifier. The second session identifier corresponds to the second tunnel identifier, indicating that the session indicated by the second session identifier is established based on the tunnel indicated by the second tunnel identifier. The second session identifier also corresponds to a second user identifier. A description of the second user identifier can be found below and will not be repeated here.

[0138] Optionally, the second forwarding information may also include a first session identifier. The first session identifier corresponds to a first tunnel identifier, indicating that the session indicated by the first session identifier is established based on the tunnel indicated by the first tunnel identifier. The first session identifier also corresponds to a first user identifier. A description of the first user identifier can be found below and will not be repeated here.

[0139] Optionally, the first forwarding message may also include a first user identifier. The message sent by the LAC forwarding plane entity to the LNS forwarding plane entity contains this first user identifier. The second forwarding message may also include a second user identifier. The message sent by the LNS forwarding plane entity to the LAC forwarding plane entity contains this second user identifier.

[0140] The process by which network devices allocate and interact with the first user identifier and the second user identifier through the LAC control plane component and the LNS control plane component can be referred to the process above for network devices allocating and interacting with the first tunnel identifier and the second tunnel identifier through the LAC control plane component and the LNS control plane component, and will not be repeated here.

[0141] Optionally, the first user identifier and the second user identifier may be the same or different, and this application embodiment does not limit this.

[0142] Optionally, the first forwarding information may also include a second user identifier, which corresponds to the second session identifier. That is, the message from the user terminal indicated by the second user identifier is transmitted through the session indicated by the second session identifier.

[0143] Optionally, the second forwarding information may also include a first user identifier, which corresponds to a first session identifier. That is, the message from the user terminal indicated by the first user identifier is transmitted through the session indicated by the first session identifier.

[0144] It should be understood that both the first user identifier and the second user identifier are used to indicate the user terminal that initiated the access request. For example, both the first user identifier and the second user identifier correspond to the MAC address or IP address of the user terminal, and there is no limitation on this.

[0145] S106. The network device sends the first forwarding information to the LAC forwarding plane entity and the second forwarding information to the LNS forwarding plane entity.

[0146] In this way, the LAC forwarding plane entity and the LNS forwarding plane entity can communicate through the first forwarding information and the second forwarding information.

[0147] Optionally, the network device can send the first forwarding information to the LAC forwarding plane entity via the control channel through the aforementioned LAC control plane component, and send the second forwarding information to the LNS forwarding plane entity via the control channel through the aforementioned LNS control plane component.

[0148] For example, a network device can send first forwarding information to the LAC forwarding plane entity via the OpenFlow control channel through the aforementioned LAC control plane component, and send second forwarding information to the LNS forwarding plane entity via the aforementioned LNS control plane component. No specific limitations are imposed on this.

[0149] In response, the LAC forwarding plane entity can receive the first forwarding information, and the LNS forwarding plane entity can receive the second forwarding message.

[0150] In this way, the LAC forwarding plane entity can establish a first correspondence between the first user identifier, the first session identifier, and the first tunnel identifier based on the received first forwarding information. Thus, when the LAC forwarding plane entity receives a packet sent by a user terminal indicated by the second user identifier, it can determine, based on this first correspondence, to transmit the packet through the session indicated by the first session identifier on the tunnel indicated by the first tunnel identifier.

[0151] For example, after receiving message 1 sent by the user terminal indicated by the first user identifier, the LAC forwarding plane entity can determine the corresponding first tunnel identifier and first session identifier based on the first correspondence. Then, the LAC forwarding plane entity adds the first tunnel identifier and first session identifier to message 1, thereby enabling message 1 to be transmitted over the tunnel indicated by the first tunnel identifier through the session indicated by the first session identifier.

[0152] The LNS forwarding plane entity can establish a second correspondence between the second user identifier, the second session identifier, and the second tunnel identifier based on the received second forwarding information. In this way, when the LNS forwarding plane entity receives a packet transmitted by the session indicated by the second session identifier on the tunnel indicated by the second tunnel identifier, it can determine, based on the second correspondence, that the packet was sent by the user terminal indicated by the second user identifier.

[0153] S107. Network devices transmit L2TP tunnel protocol messages through the LAC forwarding plane entity and the LNS forwarding plane entity to realize communication between the LAC forwarding plane entity and the LNS forwarding plane entity.

[0154] Here, the network device transmits L2TP tunnel protocol messages through the LAC forwarding plane entity and the LNS forwarding plane entity, realizing the communication process between the LAC forwarding plane entity and the LNS forwarding plane entity. Please refer to the above text for details. Figure 1 The method shown will not be described again here.

[0155] Therefore, this embodiment of the application, through the communication establishment method described in S101-S107 above, generates first forwarding information and second forwarding information by directly interacting between the LAC control plane component and the LNS control plane component in the network device when determining the LAC and LNS co-managed forwarding plane entities of the network device. Then, the network device directly sends the generated first forwarding information to the LAC forwarding plane entity and the generated second forwarding information directly to the LNS forwarding plane entity. Thus, based on the first and second forwarding information, communication between the LAC and LNS forwarding plane entities can be quickly achieved. This method eliminates the need for L2TP tunnel protocol message transmission and interaction between the network device, the LAC forwarding plane entity, and the LNS forwarding plane entity to achieve communication between them, thereby improving the efficiency of accessing the LNS via LAC and enhancing the online performance of the user end.

[0156] To more clearly illustrate the methods provided in the embodiments of this application, specific examples are described below.

[0157] Combination Figure 3 The tunnel source interface of LAC forwarding plane entity 311 can be Loopback1, and the IP address corresponding to this tunnel source interface can be 1.1.1.1. The tunnel source interface of LNS forwarding plane entity 321 can be Loopback2, and the IP address corresponding to this tunnel source interface can be 2.2.2.2.

[0158] As described above, LNS forwarding plane entity 321 can report the IP address 2.2.2.2 corresponding to the tunnel source interface of LNS forwarding plane entity 321 to network device 33, which is a control plane entity, during network formation.

[0159] Correspondingly, network device 33 receives the IP address 2.2.2.2 corresponding to the tunnel source interface of LNS forwarding plane entity 321. In this way, network device 33 can record the IP address corresponding to the received tunnel source interface in the address resource pool. It can be seen that the address resource pool of network device 33 includes IP address 2.2.2.2.

[0160] Optionally, during network configuration, the LAC forwarding plane entity 311 may report the IP address 1.1.1.1 of the tunnel source interface of the LAC forwarding plane entity 311, as well as the routing information corresponding to the IP address, to the network device 33, which acts as the control plane entity.

[0161] Accordingly, network device 33 receives the IP address 1.1.1.1 of the tunnel source interface of LAC forwarding plane entity 311, as well as the routing information corresponding to that IP address.

[0162] When user terminal 34 initiates a PPPoE dial-up process carrying the username kk@l2tp, for example, user terminal 34 can send a PPPoE Active Discovery Initiation (PADI) message to network device 33 via LAC forwarding plane entity 311. This PADI message can be understood as an access request sent by user terminal 34 to LAC 31, and this access request carries the username of user terminal 34.

[0163] In response, after receiving the PADI message, network device 33 processes the message to establish a PPP link between user terminal 34 and LAC forwarding plane entity 311, and extracts the username kk@l2tp from the PADI message. Then, network device 33 resolves the username kk@l2tp and identifies the domain name of user terminal 34 as l2tp.

[0164] Next, network device 33 determines in its preset configuration that there exists a configuration group l2tp-group tt (where tt is the name of the configuration group) corresponding to the domain name l2tp. In this way, network device 33 can determine that user terminal 34 is an L2TP type user.

[0165] Then, based on the configuration parameters of configuration group l2tp-group tt, network device 33 determines that the IP address of LNS forwarding plane entity 321 configured in the configuration group is 2.2.2.2.

[0166] Optionally, network device 33 may also determine whether a route between LAC forwarding plane entity 311 and LNS forwarding plane entity 321 is reachable based on the IP address 1.1.1.1 of LAC forwarding plane entity 311 (which is the forwarding plane entity that forwards PADI packets for user terminal 34 as mentioned above) and the IP address 2.2.2.2 of LNS forwarding plane entity 321 determined according to configuration group l2tp-grouptt, from the routing information corresponding to the pre-collected IP address 1.1.1.1.

[0167] It should be understood that if network device 33 determines that the route between LAC forwarding plane entity 311 and LNS forwarding plane entity 321 is unreachable, then the communication connection between LAC forwarding plane entity 311 and LNS forwarding plane entity 321 has failed.

[0168] If network device 33 determines that the route between LAC forwarding plane entity 311 and LNS forwarding plane entity 321 is reachable, it then determines whether the IP address 2.2.2.2 of the determined LNS forwarding plane entity 321 exists in the pre-collected address resource pool based on the determined IP address 2.2.2.2 of LNS forwarding plane entity 321.

[0169] When network device 33 determines that the IP address 2.2.2.2 of LNS forwarding plane entity 321 exists in the pre-collected address resource pool, it means that network device 33 co-manages LAC forwarding plane entity 311 and LNS forwarding plane entity 321. In this case, network device 33 can generate first forwarding information and second forwarding information through the interaction between the LAC control plane component and the LNS control plane component within network device 33. Here, the LAC control plane component corresponds to LAC forwarding plane entity 311, and the LNS control plane component corresponds to LNS forwarding plane entity 321.

[0170] Then, network device 33 sends first forwarding information to LAC forwarding plane entity 311 through the LAC control plane component, and sends second forwarding information to LNS forwarding plane entity 321 through the LNS control plane component. In this way, communication between LAC forwarding plane entity 311 and LNS forwarding plane entity 321 can be realized based on the first and second forwarding information.

[0171] Of course, if network device 33 determines that its pre-collected address resource pool does not include the IP address of LNS forwarding plane entity 321, it means that LAC forwarding plane entity 311 and LNS forwarding plane entity 321 correspond to different control plane entities. In this case, network device 33 can use... Figure 1 The method shown enables communication between LAC forwarding plane entity 311 and LNS forwarding plane entity 321 by transmitting L2TP tunnel protocol messages between network device 33, LAC forwarding plane entity 311 and LNS forwarding plane entity 321, which will not be described in detail here.

[0172] In summary, this application provides a method for establishing communication. When a network device is determined to be a control plane entity co-managing both the LAC forwarding plane entity and the LNS forwarding plane entity, the method generates first forwarding information and second forwarding information through interactive communication between the LAC control plane component and the LNS control plane component within the network device. The network device then sends the first forwarding information to the LAC forwarding plane entity and the second forwarding information to the LNS forwarding plane entity. Thus, communication between the LAC forwarding plane entity and the LNS forwarding plane entity can be achieved based on the first and second forwarding information.

[0173] This method eliminates the need for multiple transmissions of L2TP tunnel protocol messages between the network devices, LAC forwarding plane entities, and LNS forwarding plane entities in the co-managed LAC forwarding plane entity and LNS forwarding plane entity. This significantly improves the efficiency of establishing communication between the LAC forwarding plane entity and LNS forwarding plane entity, thereby increasing the efficiency of user access to LNS, improving user online performance, and reducing system resource consumption.

[0174] The foregoing mainly describes the solutions provided by the embodiments of this application from a methodological perspective. To achieve the above functions, it includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0175] This application embodiment can divide the communication establishment device into functional modules according to the above method example. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0176] like Figure 7 As shown, Figure 7 This diagram illustrates the structure of a communication establishment apparatus 70 (hereinafter referred to as "apparatus 70") according to an embodiment of this application. Apparatus 70 can be applied to network devices used for managing LAC forwarding plane entities. This apparatus 70 can be used to execute the aforementioned communication establishment method, for example, to execute... Figure 5 The method is shown. The device 70 may include a determining unit 71, a generating unit 72, and a sending unit 73.

[0177] The determining unit 71 is used to determine the network device management LNS forwarding plane entity. The generating unit 72 is used to generate first forwarding information and second forwarding information in response to the determining unit 71 determining the network device management LNS forwarding plane entity. The sending unit 73 is used to send the first forwarding information to the LAC forwarding plane entity and the second forwarding information to the LNS forwarding plane entity. The first and second forwarding information are used to enable communication between the LAC forwarding plane entity and the LNS forwarding plane entity.

[0178] As an example, combined Figure 5 The determining unit 71 can be used to execute S104, the generating unit 72 can be used to execute S105, and the sending unit 73 can be used to execute S106.

[0179] Optionally, the determining unit 71 is specifically used to determine whether the Internet Protocol IP address of the LNS forwarding plane entity is within the range of IP addresses managed by the network device.

[0180] As an example, combined Figure 5 Unit 71 can be used to execute S104.

[0181] Optionally, the first forwarding information mentioned above includes a first tunnel identifier, which is used by the LAC forwarding plane entity to send a message to the LNS forwarding plane entity, and the message sent by the LAC forwarding plane entity to the LNS forwarding plane entity contains the first tunnel identifier.

[0182] Optionally, the second forwarding information mentioned above includes a second tunnel identifier, which is used by the LNS forwarding plane entity to send a message to the LAC forwarding plane entity, and the message sent by the LNS forwarding plane entity to the LAC forwarding plane entity contains the second tunnel identifier.

[0183] Optionally, the first forwarding information mentioned above also includes a first session identifier, which is included in the message sent by the LAC forwarding plane entity to the LNS forwarding plane entity.

[0184] Optionally, the second forwarding information mentioned above also includes a second session identifier, which is included in the message sent by the LNS forwarding plane entity to the LAC forwarding plane entity.

[0185] Optionally, the aforementioned network device includes an LAC control plane component and an LNS control plane component. The generation unit 72 is specifically configured to generate the aforementioned first forwarding information and second forwarding information through interactive communication between the LAC control plane component and the LNS control plane component.

[0186] As an example, combined Figure 5 The generation unit 72 can be used to execute S105.

[0187] Optionally, the apparatus 70 further includes: an acquisition unit 74, configured to acquire an access request from a user terminal; and a determination unit 71, configured to determine, based on the access request, that the user terminal is an L2TP type user terminal before the generation unit 72 generates the first forwarding information and the second forwarding information, if the access request is used to indicate that the user terminal requests to communicate with the aforementioned LNS control plane entity.

[0188] As an example, combined Figure 5 The acquisition unit 74 can be used to execute S101, and the determination unit 71 can be used to execute S102.

[0189] Optionally, the determining unit 71 is specifically used to determine the IP address of the LNS forwarding plane entity based on the access request, and to determine, based on the IP address of the LNS forwarding plane entity and the address resource pool, that the IP address of the LNS forwarding plane entity is within the IP address range managed by the network device. The address resource pool includes the IP addresses of the forwarding plane entities managed by the network device.

[0190] As an example, combined Figure 5 Unit 71 can be used to execute S104.

[0191] Optionally, the determining unit 71 is further configured to determine the route reachability between the LAC forwarding plane entity and the LNS forwarding plane entity before the sending unit 73 sends the first forwarding information to the LAC forwarding plane entity and the second forwarding information to the LNS forwarding plane entity.

[0192] As an example, combined Figure 5 Unit 71 can be used to execute S103.

[0193] Optionally, the acquisition unit 74 is further configured to acquire the domain name carried in the access request. The determination unit 71 is specifically configured to determine, based on the domain name, that the aforementioned client is an L2TP type client.

[0194] As an example, combined Figure 5 The acquisition unit 74 and the determination unit 71 can be used to execute S102.

[0195] For a detailed description of the above-mentioned optional methods, please refer to the foregoing method embodiments, which will not be repeated here. Furthermore, the explanation of any of the above-provided devices 70 and the description of their beneficial effects can be found in the corresponding method embodiments, which will not be repeated here.

[0196] As an example, combined Figure 2 The determining unit 71, generating unit 72, and acquiring unit 74 in device 70 can be... Figure 2 The processor 21 in the middle executes Figure 2 The program code in memory 22 is implemented, and the sending unit 73 can be used through... Figure 2 The communication interface 23 is implemented in the middle.

[0197] This application embodiment also provides a chip system 80, such as Figure 8 As shown, the chip system 80 includes at least one processor and at least one interface circuit. As an example, when the chip system 80 includes one processor and one interface circuit, the processor can be... Figure 8 The processor 81 shown in the solid box (or the processor 81 shown in the dashed box) can be an interface circuit. Figure 8 The interface circuit 82 is shown in the solid box (or the dashed box). When the chip system 80 includes two processors and two interface circuits, the two processors include... Figure 8 The processor 81 shown in the solid box and the processor 81 shown in the dashed box, these two interface circuits include Figure 8 Interface circuit 82 is shown in both solid and dashed boxes. No limitations are imposed on this.

[0198] The processor 81 and the interface circuit 82 can be interconnected via a line. For example, the interface circuit 82 can be used to receive signals (e.g., to obtain an access request). As another example, the interface circuit 82 can be used to send signals to other devices (e.g., the processor 81). Exemplarily, the interface circuit 82 can read instructions stored in memory and send those instructions to the processor 81. When the instruction is executed by the processor 81, it can cause the device establishing communication to perform the steps in the above embodiments. Of course, the chip system 80 may also include other discrete components, and this application embodiment does not specifically limit this.

[0199] Another embodiment of this application also provides a computer-readable storage medium storing instructions that, when executed on a communication-establishing device, perform the various steps of the communication-establishing device in the method flow shown in the above method embodiment.

[0200] In some embodiments, the disclosed method may be implemented as computer program instructions encoded in a machine-readable format on a computer-readable storage medium or on other non-transitory media or articles of art.

[0201] Figure 9 A conceptual partial view of a computer program product provided in an embodiment of this application is shown schematically. The computer program product includes a computer program for executing computer processes on a computing device.

[0202] In one embodiment, a computer program product is provided using a signal bearer medium 90. The signal bearer medium 90 may include one or more program instructions that, when executed by one or more processors, can provide the above-mentioned... Figure 5 The described function or part of the function. Therefore, for example, refer to... Figure 5 One or more features of S101 to S107 can be assumed by one or more instructions associated with the signal carrying medium 90. Furthermore, Figure 9 The program instructions in the document also describe example instructions.

[0203] In some examples, the signal carrying medium 90 may include a computer-readable medium 91, such as, but not limited to, a hard disk drive, a compact disc (CD), a digital video optical disc (DVD), a digital magnetic tape, a memory, read-only memory (ROM), or random access memory (RAM), etc.

[0204] In some implementations, the signal carrying medium 90 may include a computer recordable medium 92, such as, but not limited to, a memory, a read / write (R / W) CD, a R / W DVD, and so on.

[0205] In some implementations, the signal carrying medium 90 may include a communication medium 93, such as, but not limited to, digital and / or analog communication media (e.g., fiber optic cables, waveguides, wired communication links, wireless communication links, etc.).

[0206] The signal-bearing medium 90 can be transmitted by a wireless communication medium 93 (e.g., a wireless communication medium conforming to the IEEE 1902.11 standard or other transmission protocols). One or more program instructions can be, for example, computer-executable instructions or logical implementation instructions.

[0207] In some examples, such as targeting Figure 5 The described communication establishment apparatus can be configured to provide various operations, functions, or actions in response to one or more program instructions in a computer-readable medium 91, a computer-recordable medium 92, and / or a communication medium 93.

[0208] It should be understood that the arrangements described herein are for illustrative purposes only. Therefore, those skilled in the art will understand that other arrangements and other elements (e.g., machines, interfaces, functions, sequences, and functional groups, etc.) can be used instead, and some elements may be omitted depending on the desired outcome. Furthermore, many of the described elements are functional entities that can be implemented as discrete or distributed components, or in any suitable combination and location with other components.

[0209] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When executed on a computer and when the computer execution instructions are executed, all or part of the processes or functions according to the embodiments of this application are generated. 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. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs).

[0210] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for establishing communication, characterized in that, Applied to a network device for managing a Layer 2 Tunneling Protocol Access Concentrator (LAC) forwarding plane entity, the network device includes an LAC control plane component and a Layer 2 Tunneling Protocol Network Server (LNS) control plane component, the method includes: Identify the network device management LNS forwarding plane entity; In response to determining that the network device manages the LNS forwarding plane entity, the first forwarding information and the second forwarding information are directly generated through interactive communication between the LAC control plane component and the LNS control plane component; the first forwarding information and the second forwarding information are used to realize communication between the LAC forwarding plane entity and the LNS forwarding plane entity; The first forwarding information is sent to the LAC forwarding plane entity, and the second forwarding information is sent to the LNS forwarding plane entity.

2. The method according to claim 1, characterized in that, The determination of the network device management LNS forwarding plane entity includes: The Internet Protocol IP address of the LNS forwarding plane entity is determined to be within the range of IP addresses managed by the network device.

3. The method according to claim 1 or 2, characterized in that, The first forwarding information includes a first tunnel identifier, which is used by the LAC forwarding plane entity to send a message to the LNS forwarding plane entity. The message sent by the LAC forwarding plane entity to the LNS forwarding plane entity contains the first tunnel identifier.

4. The method according to claim 1 or 2, characterized in that, The second forwarding information includes a second tunnel identifier, which is used by the LNS forwarding plane entity to send a message to the LAC forwarding plane entity. The message sent by the LNS forwarding plane entity to the LAC forwarding plane entity contains the second tunnel identifier.

5. The method according to claim 3, characterized in that, The first forwarding information also includes a first session identifier, which is included in the message sent by the LAC forwarding plane entity to the LNS forwarding plane entity.

6. The method according to claim 4, characterized in that, The second forwarding information also includes a second session identifier, which is included in the message sent by the LNS forwarding plane entity to the LAC forwarding plane entity.

7. The method according to claim 1, 2, 5, or 6, characterized in that, Before generating the first forwarding information and the second forwarding information, the method further includes: Obtain the user's access request; Based on the access request, if it is determined that the user terminal is an L2TP type user terminal, then the access request is used to instruct the user terminal to request communication with the LNS control plane entity.

8. The method according to claim 7, characterized in that, Determining that the IP address of the LNS forwarding plane entity is within the IP address range managed by the network device includes: Based on the access request, determine the IP address of the LNS forwarding plane entity; Based on the IP address of the LNS forwarding plane entity and the address resource pool, the IP address of the LNS forwarding plane entity is determined to be within the range of IP addresses managed by the network device; wherein, the address resource pool includes the IP addresses of the forwarding plane entities managed by the network device.

9. The method according to claim 1, 2, 5, 6, or 8, characterized in that, Before sending the first forwarding information to the LAC forwarding plane entity and the second forwarding information to the LNS forwarding plane entity, the method further includes: Determine that the route between the LAC forwarding plane entity and the LNS forwarding plane entity is reachable.

10. The method according to claim 7, characterized in that, The step of determining that the user terminal is an L2TP type user terminal based on the access request specifically includes: Obtain the domain name carried in the access request; Based on the domain name, it is determined that the client is an L2TP type client.

11. An apparatus for establishing communication, characterized in that, Applied to a network device for managing a Layer 2 Tunneling Protocol Access Concentrator (LAC) forwarding plane entity, the network device includes an LAC control plane component and a Layer 2 Tunneling Protocol Network Server (LNS) control plane component, the device comprising: The determining unit is used to determine the network device management LNS forwarding plane entity; The generation unit is configured to, in response to the determining unit determining that the network device manages the LNS forwarding plane entity, directly generate first forwarding information and second forwarding information through interactive communication between the LAC control plane component and the LNS control plane component; the first forwarding information and the second forwarding information are used to realize communication between the LAC forwarding plane entity and the LNS forwarding plane entity; The sending unit is configured to send the first forwarding information to the LAC forwarding plane entity and send the second forwarding information to the LNS forwarding plane entity.

12. The apparatus according to claim 11, characterized in that, The determining unit is specifically used to determine the Internet Protocol IP address of the LNS forwarding plane entity within the IP address range managed by the network device.

13. The apparatus according to claim 11 or 12, characterized in that, The first forwarding information includes a first tunnel identifier, which is used by the LAC forwarding plane entity to send a message to the LNS forwarding plane entity. The message sent by the LAC forwarding plane entity to the LNS forwarding plane entity contains the first tunnel identifier.

14. The apparatus according to claim 11 or 12, characterized in that, The second forwarding information includes a second tunnel identifier, which is used by the LNS forwarding plane entity to send a message to the LAC forwarding plane entity. The message sent by the LNS forwarding plane entity to the LAC forwarding plane entity contains the second tunnel identifier.

15. The apparatus according to claim 13, characterized in that, The first forwarding information also includes a first session identifier, which is included in the message sent by the LAC forwarding plane entity to the LNS forwarding plane entity.

16. The apparatus according to claim 14, characterized in that, The second forwarding information also includes a second session identifier, which is included in the message sent by the LNS forwarding plane entity to the LAC forwarding plane entity.

17. The apparatus according to claim 11, 12, 15, or 16, characterized in that, The device further includes: The acquisition unit is used to acquire access requests from the user's client. The determining unit is further configured to, before the generating unit generates the first forwarding information and the second forwarding information, determine, based on the access request, that the user terminal is an L2TP type user terminal, and the access request is used to instruct the user terminal to request communication with the LNS control plane entity.

18. The apparatus according to claim 17, characterized in that, The determining unit is specifically configured to determine the IP address of the LNS forwarding plane entity based on the access request; and to determine the IP address of the LNS forwarding plane entity within the IP address range managed by the network device based on the IP address of the LNS forwarding plane entity and the address resource pool; wherein the address resource pool includes the IP addresses of the forwarding plane entities managed by the network device.

19. The apparatus according to claim 11, 12, 15, 16, or 18, characterized in that, The determining unit is further configured to determine, before the sending unit sends the first forwarding information to the LAC forwarding plane entity and the second forwarding information to the LNS forwarding plane entity, that the route between the LAC forwarding plane entity and the LNS forwarding plane entity is reachable.

20. The apparatus according to claim 17, characterized in that, The acquisition unit is further configured to acquire the domain name carried in the access request; The determining unit is specifically used to determine, based on the domain name, that the user terminal is an L2TP type user terminal.

21. An apparatus for establishing communication, characterized in that, The apparatus includes a memory and one or more processors, the memory storing computer instructions and the processors invoking the computer instructions to perform the method as described in any one of claims 1 to 10.

22. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed on a means of establishing communication, causes the means of establishing communication to perform the method as described in any one of claims 1 to 10.

Images