Network management method and system

Abstract

The application discloses a kind of identification network management method and system, the method is applied to the control plane in identification network management architecture, the control plane and data plane are separated in identification network management architecture, and the data plane includes several switches, the method comprises: when detecting mobile message, mobile switch corresponding mobile identification information and mobile terminal corresponding mobile access identification are acquired according to mobile message, mobile switch is the switch for sending mobile message, and mobile message is generated when mobile switch detects mobile terminal access;Mobile flow table is determined according to mobile identification information and mobile access identification;Mobile flow table is issued to mobile switch, to make mobile switch build the communication connection of mobile terminal in target identification network based on mobile flow table.The control logic of the present application mobile switching is realized by the control plane, and the processing delay of the control plane is relatively short and stable, so as to improve the reaction efficiency of mobile switching control.

Description

Technical Field

[0001] This invention relates to the field of Internet technology, and in particular to a method and system for identifying and managing networks. Background Technology

[0002] To resolve the ambiguity of IP addresses, identification networks define an Access Identifier (AID) representing device identity information and a Route Identifier (RID) representing user access location information. In an identification network, when a mobile terminal undergoes a handover, its Access Identifier remains unchanged; only the Route Identifier corresponding to the access location information is changed—that is, a new Route Identifier is assigned to the mobile terminal. Current mobility management mechanisms in identification networks are mostly based on switch network functions and networking. Specifically, existing technologies often use Access Switch Routers (ASRs) to handle the control logic in the identification network. In this architecture, ASRs are responsible for network control capabilities, and ASRs communicate with each other via signaling to complete network processing.

[0003] When terminal devices in the identification network need to be moved and handed over, the handover process in the existing technology includes the delay of signaling transmission between ASRs. Due to the large scale and long distance between ASRs before and after the handover, or the fluctuation of communication links between ASRs, the handover delay is prone to be large. Therefore, the existing identification network management system has the problem of slow response speed. Summary of the Invention

[0004] The main objective of this invention is to provide a method and system for managing identification networks, aiming to solve the technical problem of slow response speed in existing identification network management systems.

[0005] To achieve the above objectives, the present invention provides an identification network management method. The method is applied to the control plane of an identification network management architecture, wherein the control plane and data plane are separated, and the data plane includes several switches. The method includes:

[0006] When a mobile packet is detected, the mobile identification information corresponding to the mobile switch and the mobile access identifier corresponding to the mobile terminal are obtained according to the mobile packet. The mobile switch is the switch that sent the mobile packet. The mobile packet is generated by the mobile switch when it detects the access of the mobile terminal.

[0007] A mobile flow table is determined based on the mobile identification information and the mobile access identifier;

[0008] The mobile flow table is sent to the mobile switch so that the mobile switch can build a communication connection for the mobile terminal in the target identification network based on the mobile flow table.

[0009] Optionally, the mobile flow table includes: a mobile communication flow table and a mobile mapping flow table; the step of determining the mobile flow table based on the mobile identification information and the mobile access identifier includes:

[0010] Determine whether the mobile identification information is consistent with the initial identification information corresponding to the mobile terminal;

[0011] If not, then determine the mobile communication flow table based on the mobile access identifier, and allocate a mobile routing identifier to the mobile switch based on the mobile identifier information;

[0012] Establish a mobile mapping relationship between the mobile route identifier and the mobile access identifier, and determine the mobile mapping flow table based on the mobile mapping relationship.

[0013] Optionally, before obtaining the mobile identification information corresponding to the mobile switch and the mobile access identifier corresponding to the mobile terminal based on the mobile packet when a mobile packet is detected, the method further includes:

[0014] When an access request is detected, the connection identifier information corresponding to the connection switch and the connection access identifier corresponding to the terminal to be connected are obtained according to the access request. The connection switch is a switch that forwards the access request. The access request is a connection request sent to the connection switch when the terminal to be connected accesses the target identifier network.

[0015] Based on the connection access identifier, a connection communication flow table is sent to the connection switch;

[0016] Assign a connection route identifier to the connection switch based on the identification information of the connection switch, and establish a connection mapping relationship between the terminal to be connected and the connection switch;

[0017] The connection mapping relationship is used to determine the connection mapping flow table, and the connection mapping flow table is sent to the connection switch so that the connection switch can construct the communication connection of the terminal to be connected in the target identification network based on the connection communication flow table and the connection mapping flow table.

[0018] Optionally, the method is applied to several switches in an identification network management architecture, wherein the control plane and data plane are separated in the identification network management architecture, the several switches are located on the data plane, and the several switches are connected to the terminal to be connected via a wireless access point. The method includes:

[0019] When a mobile packet is detected, the mobile packet is forwarded to the control plane so that the control plane can feed back a mobile flow table based on the mobile packet. The mobile packet is generated by the corresponding wireless access point when the mobile terminal is detected to be accessing the network.

[0020] The communication connection of the mobile terminal in the target identifier network is constructed based on the mobile flow table.

[0021] Optionally, the data plane further includes: a core network, an access network, and core routers, and the method includes:

[0022] When a communication request sent by a terminal to be communicated is detected, a communication data packet is obtained according to the communication request. The header of the communication data packet is encapsulated with a destination access identifier corresponding to the terminal to be transmitted. The terminal to be communicated is a data packet sending terminal device located in the access network, and the terminal to be transmitted is a data packet receiving terminal device located in the access network.

[0023] Detect whether the communication data packet contains a mapping flow table corresponding to the destination access identifier;

[0024] If not, the destination access identifier and mapping query request are sent to the control plane so that the control plane can return the destination mapping flow table, which includes the destination route identifier;

[0025] The destination route identifier is encapsulated in the header of the communication data packet according to the destination mapping flow table to obtain a tagged communication data packet;

[0026] The tagged communication data packet is sent to the core router in the core network, so that the core router sends the tagged communication data packet to the target communication switch corresponding to the destination route identifier, and the target communication switch sends the tagged communication data packet to the terminal to be transmitted according to the destination access identifier.

[0027] Furthermore, to achieve the above objectives, the present invention also proposes an identification network management system, the system comprising: a control plane and a data plane, wherein the control plane and the data plane are separated, and the data plane includes a plurality of switches, wherein the plurality of switches includes: a mobile switch;

[0028] The control plane is used to obtain the mobile identification information corresponding to the mobile switch and the mobile access identifier corresponding to the mobile terminal based on the mobile packet when a mobile packet is detected. The mobile packet is generated by the mobile switch when the mobile terminal is detected to be accessing the network. The mobile terminal is a terminal device that performs mobile handover.

[0029] The control plane is also used to determine a mobile flow table based on the mobile identification information and the mobile access identifier, and to send the mobile flow table to the mobile switch;

[0030] The mobile switch is used to construct the communication connection of the mobile terminal in the target identification network based on the mobile flow table.

[0031] Optionally, the control plane includes: at least one controller, which is connected to the plurality of switches respectively;

[0032] The controller is used to determine whether the mobile identification information is consistent with the initial identification information corresponding to the mobile terminal;

[0033] The controller is further configured to, if not, determine the mobile communication flow table based on the mobile access identifier, and allocate a mobile routing identifier to the mobile switch based on the mobile identifier information;

[0034] The controller is further configured to establish a mobile mapping relationship between the mobile route identifier and the mobile access identifier, and to determine the mobile mapping flow table based on the mobile mapping relationship.

[0035] Optionally, the control plane further includes a mapping database, and the controller includes a management module, a mobility module, and a mapping module;

[0036] The management module is used to, when the mobile packet is detected, obtain the mobile identification information of the mobile switch and the mobile access identifier corresponding to the mobile terminal according to the mobile packet, and send the mobile identification information and the mobile access identifier to the mobility module;

[0037] The mobility module is used to determine whether the mobility identification information is consistent with the initial identification information corresponding to the mobile terminal;

[0038] The mobility module is further configured to, if not, send the mobile communication flow table to the mobile switch based on the mobile access identifier, and send the mobile identifier information and the mobile access identifier to the mapping module;

[0039] The mapping module is used to allocate a mobile routing identifier to the mobile switch according to the mobile identification information, and to establish a mobile mapping relationship between the mobile routing identifier and the mobile access identifier;

[0040] The mapping module is further configured to send the mobile mapping relationship to the mapping database for mapping update, and issue the mobile mapping flow table to the mobile switch according to the mobile mapping relationship.

[0041] Optionally, the plurality of switches includes: a connection switch;

[0042] The management module is also used to obtain the connection identifier information corresponding to the connection switch and the connection access identifier corresponding to the terminal to be connected according to the access request when an access request is detected. The access request is a connection request sent to the connection switch when the terminal to be connected accesses the target identifier network.

[0043] The management module is also used to send the connection access identifier to the mobility module;

[0044] The mobility module is also configured to send a connection communication flow table to the connection switch based on the connection access identifier;

[0045] The management module is also used to send the connection identification information to the mapping module;

[0046] The mapping module is further configured to allocate a connection route identifier to the connection switch according to the connection identifier information, establish a connection mapping relationship between the connection route identifier and the connection access identifier, and send the connection mapping relationship to the mapping database so that the mapping database stores the connection mapping relationship;

[0047] The mapping module is further configured to send the connection mapping flow table to the connection switch through the connection mapping relationship, so that the connection switch can construct the communication connection of the terminal to be connected in the target identification network based on the connection communication flow table and the connection mapping flow table.

[0048] Optionally, the data plane further includes: a core network, an access network, and a core router; the plurality of switches includes: a source communication switch and a destination communication switch;

[0049] The source communication switch is used to obtain a communication data packet according to the communication request when a communication request sent by the terminal to be communicated is detected. The header of the communication data packet is encapsulated with a destination access identifier corresponding to the terminal to be communicated and the terminal to be transmitted. The terminal to be communicated is a data packet sending terminal device located in the access network, and the terminal to be transmitted is a data packet receiving terminal device located in the access network.

[0050] The source communication switch is also used to detect whether the communication data packet contains a mapping flow table corresponding to the destination access identifier;

[0051] The source communication switch is further configured to send the destination access identifier and mapping query request to the management module if no;

[0052] The management module is also used to send the destination access identifier and mapping query request to the mapping module;

[0053] The mapping module is further configured to send the destination access identifier to the mapping database, so that the mapping database can provide feedback on the destination mapping relationship corresponding to the destination access identifier;

[0054] The mapping module is further configured to establish a destination mapping flow table based on the destination mapping relationship, and to send the destination mapping flow table to the source communication switch, wherein the destination mapping flow table contains a destination route identifier;

[0055] The source communication switch is further configured to encapsulate the destination route identifier in the header of the communication data packet according to the destination mapping flow table, obtain a marked communication data packet, and send the marked communication data packet to the core router in the core network;

[0056] The core router is used to send the marked communication data packet to the target communication switch corresponding to the destination route identifier;

[0057] The target communication switch is used to send the marked communication data packet to the terminal to be transmitted according to the destination access identifier.

[0058] This invention discloses a method and system for managing an identification network. The method includes: when an access request is detected, obtaining connection identification information corresponding to a connection switch and a connection access identifier corresponding to a terminal to be connected based on the access request, wherein the connection switch is a switch that forwards access requests, and the access request is a connection request sent to the connection switch when the terminal to be connected accesses the target identification network; issuing a connection communication flow table to the connection switch based on the connection access identifier; allocating a connection routing identifier to the connection switch based on the identification information of the connection switch, and establishing a connection mapping relationship between the terminal to be connected and the connection switch; determining a connection mapping flow table through the connection mapping relationship, and issuing the connection mapping flow table to the connection switch, so that the connection switch can construct a communication connection for the terminal to be connected in the target identification network based on the connection communication flow table and the connection mapping flow table. When a mobile packet is detected, the system obtains the mobile identification information corresponding to the mobile switch and the mobile access identifier corresponding to the mobile terminal based on the mobile packet. The mobile switch is the switch that sent the mobile packet, which is generated by the mobile switch when it detects the mobile terminal's access. The system then determines whether the mobile identification information matches the initial identification information corresponding to the mobile terminal. If not, it determines the mobile communication flow table based on the mobile access identifier and allocates a mobile routing identifier to the mobile switch based on the mobile identification information. A mobile mapping relationship is established between the mobile routing identifier and the mobile access identifier, and a mobile mapping flow table is determined based on this relationship. The mobile flow table is then distributed to the mobile switch, enabling the mobile switch to build the communication connection of the mobile terminal in the target identification network based on the mobile flow table. This embodiment adopts a control and forwarding separation architecture. Since the control logic, such as updating the mapping relationship, is centrally implemented in the control plane during mobile handover, the handover latency mainly comes from the processing latency of the control plane. Therefore, compared to the identification network mobility management mechanism based on switches for control and forwarding, this embodiment transforms the decentralized control between switches into centralized control of the control plane. This makes the mobile handover control process no longer affected by the scale of the switch equipment, resulting in a relatively short and stable handover latency, thereby significantly improving the system's response efficiency. Meanwhile, in this embodiment, the control plane has global awareness of the switches in the data plane. Therefore, when any terminal device connects to any switch, it can obtain mobility management-related information in the switch without signaling interaction between switches, and realize fast mapping relationship registration of terminal devices based on this information, or achieve better handover performance in the handover process. Attached Figure Description

[0059] Figure 1 This is a first flowchart illustrating the first embodiment of the network control method of the present invention;

[0060] Figure 2 This is a second flowchart illustrating the first embodiment of the network control method of the present invention;

[0061] Figure 3 This is a schematic diagram of the third process of the first embodiment of the network control method of the present invention;

[0062] Figure 4 This is a mobile handover interaction diagram representing the first embodiment of the network control method of the present invention;

[0063] Figure 5 This is a first flowchart illustrating the second embodiment of the network control method of the present invention;

[0064] Figure 6 This is a second flowchart illustrating a second embodiment of the network control method of the present invention;

[0065] Figure 7 This is a schematic diagram of the structure of the first embodiment of the network management and control system of the present invention;

[0066] Figure 8 This is a schematic diagram of the structure of the second embodiment of the network management and control system of the present invention;

[0067] Figure 9 This is a schematic diagram of the management module in the second embodiment of the network control system of the present invention;

[0068] Figure 10 This is a schematic diagram of the mobility module in the second embodiment of the network control system of the present invention;

[0069] Figure 11 This is a schematic diagram of the mapping module in the second embodiment of the network management system of the present invention;

[0070] Figure 12 This is a structural diagram of the third embodiment of the network management system of the present invention.

[0071] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0072] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0073] Understandably, current identification network mobility management mechanisms are mostly based on switch network functions and networking, requiring deep customization of the packet parsing and forwarding logic in the switching device's operating system kernel protocol stack, and adding customized network functions. However, existing identification network management protocols are typically fixed, resulting in low system portability. This embodiment, to reduce the cost of innovative development, deployment, and maintenance of identification networks, can implement identification network management based on a programmable platform, thereby facilitating the promotion and application of identification networks. Furthermore, since existing identification networks are managed by ASRs (Access Switch Routers), when the identification network becomes too large or information exchange between ASRs encounters problems due to link fluctuations, the system's response rate can easily decrease. Furthermore, the current identification network mobility management mechanism based on switch control and forwarding cannot be directly applied to programmable platforms. To address this issue, the programmable platform architecture for identification network management in this embodiment adopts the idea of ​​separating forwarding and control. Specifically, this embodiment decouples routing and switching in the network into a data plane and a control plane. The data plane is responsible for forwarding in the identification network and can flexibly design and implement different packet parsing and processing flows and forwarding logic. The control plane is responsible for the control logic of the identification network, can collect information from the data plane, implement complex control calculation logic of the identification network, and direct the forwarding of the data plane, thus also possessing programmable flexibility.

[0074] Therefore, embodiments of the present invention provide a method for identifying network management, referring to... Figure 1 , Figure 1 This is a first flowchart illustrating the first embodiment of the network control method of the present invention.

[0075] In this embodiment, the identification network management method includes the following steps:

[0076] Step S10: When a mobile packet is detected, the mobile identification information corresponding to the mobile switch and the mobile access identifier corresponding to the mobile terminal are obtained according to the mobile packet. The mobile switch is the switch that sent the mobile packet. The mobile packet is generated by the mobile switch when it detects the access of the mobile terminal.

[0077] It should be noted that the method described above in this embodiment is applied to the control plane of the identification network management architecture (i.e., the programmable platform architecture described above). The control plane and data plane are separated in the identification network management architecture, and the data plane includes several switches. It is easy to understand that the above switches can be ASRs (Access Switch Routers), and in practical applications, they can be programmable commercial white-box switches. Based on the above identification network management architecture, the target identification network can be managed and controlled.

[0078] It's important to understand that the target identification network defines an Access Identifier (AID) representing the terminal device's identity information and a Route Identifier (RID) representing the terminal device's access location information. A mapping mechanism between these two identifiers is established, and this mapping mechanism can be stored in the control plane's mapping database. Specifically, the Access Identifier corresponds one-to-one with the terminal device's device information, and the Route Identifier corresponds one-to-one with the device information of the switch the terminal device is connected to. In the target identification network, when a terminal device undergoes a handover (i.e., the switch it's connected to changes), the terminal device's Access Identifier remains unchanged; only the Route Identifier representing the access location information changes. This means a new Route Identifier needs to be assigned to the mobile terminal, and the mobile terminal can be the one undergoing the handover.

[0079] It's easy to understand that when a handover occurs, the mobile terminal needs to reconnect to a new switch, namely the aforementioned mobile switch. In practical applications, the wireless access point (AP) corresponding to this mobile switch can detect whether a terminal device is connected. When the mobile switch detects a mobile terminal's connection, it generates a mobile packet, which may contain the mobile access identifier or communication key corresponding to the mobile terminal. This mobile packet is then sent to the control plane, allowing the control plane to update and maintain the mapping relationship before and after the handover, ensuring that the AID remains unchanged and the RID is reassigned. The aforementioned mobile identifier information can be the device information or location information of the mobile switch, and the aforementioned mobile access identifier can be the access identifier corresponding to the mobile terminal in the target identification network.

[0080] It is understandable that any terminal device needs to register the AID-RID mapping relationship when it first accesses the target identifier network. Therefore, if Figure 2 As shown, Figure 2 This is a second flowchart illustrating the first embodiment of the network management method of the present invention. In this embodiment, before step S10, the method further includes:

[0081] Step S00: When an access request is detected, the connection identifier information corresponding to the connection switch and the connection access identifier corresponding to the terminal to be connected are obtained according to the access request. The connection switch is the switch that forwards the access request. The access request is the connection request sent to the connection switch when the terminal to be connected accesses the target identifier network.

[0082] Step S01: Send the connection communication flow table to the connection switch based on the connection access identifier;

[0083] Step S02: Assign a connection route identifier to the connection switch according to the identification information of the connection switch, and establish a connection mapping relationship between the terminal to be connected and the connection switch;

[0084] Step S03: Determine the connection mapping flow table through the connection mapping relationship, and send the connection mapping flow table to the connection switch, so that the connection switch can construct the communication connection of the terminal to be connected in the target identification network based on the connection communication flow table and the connection mapping flow table.

[0085] It is easy to understand that when a terminal device first accesses the target identification network, it can initiate an access request to the switch. Therefore, in this embodiment, the aforementioned connecting switch can be the switch that receives the access request sent by the terminal to be connected. In existing identification network management methods, routing tables are obtained through mutual learning between switches. However, in this application, some routing tables can only be issued by the control plane. Only after the terminal device completes the mapping registration access process will the corresponding routing table be generated and issued to the switch device. This allows the switch device to correctly process forwarded packets based on the issued routing table, namely the aforementioned connection communication flow table and connection mapping flow table, thereby enabling the terminal to access the target identification network for communication.

[0086] Understandably, in this embodiment, the connection switch directly forwards the access request to the control plane after receiving it. Upon receiving the access request, the control plane first issues a connection communication flow table to the connection switch based on the connection access identifier of the terminal to be connected. The connection switch can then establish a communication connection between the terminal to be connected and a specific port on the connection switch based on this connection communication flow table. Then, the control plane assigns a RID (Routing Identifier) ​​to the terminal to be connected (i.e., the location information or device information of the connection switch) based on the obtained connection identifier information of the connection switch, thereby establishing a connection mapping relationship between the terminal to be connected and the connection switch.

[0087] It is important to understand that in this embodiment, a mapping database can be set up in the control plane to specifically store AID-RID mapping relationships. Therefore, after establishing the connection mapping relationship between the terminal to be connected and the connection switch, the connection mapping relationship can be written into the mapping database to achieve global synchronization of the mapping relationship. At the same time, the control plane can also determine the connection mapping flow table based on the connection mapping relationship and send the connection mapping flow table to the connection switch in the data plane, so that the connection switch can build the communication connection between the terminal to be connected in the target identification network and the connection switch based on the connection mapping flow table.

[0088] Step S20: Determine the mobile flow table based on the mobile identification information and the mobile access identifier;

[0089] It is important to understand that after the control plane obtains the mobile identification information and mobile access identifier based on the mobile packet, it can update the routing identifier corresponding to the new access location (i.e., the aforementioned mobile switch) for the mobile terminal according to the mobile identification information, thereby establishing a new AID-RID mapping relationship and storing it in the aforementioned mapping database to achieve global synchronization. Therefore, further, as one possible implementation, such as Figure 3 As shown, Figure 3 This is a schematic diagram of the third process of the first embodiment of the network management method of the present invention. In this embodiment, the mobile flow table includes: a mobile communication flow table and a mobile mapping flow table, and step S20 includes:

[0090] Step S201: Determine whether the mobile identification information is consistent with the initial identification information corresponding to the mobile terminal;

[0091] It should be noted that the aforementioned mobile terminal handover can be further divided into intra-domain handover and inter-domain handover. Intra-domain handover refers to a mobile terminal switching from one port of a mobile switch to another; while inter-domain handover refers to a mobile terminal switching between switches. Therefore, when the control plane receives a mobile packet uploaded by the mobile switch, it can first determine whether the mobile identification information corresponding to the mobile switch is consistent with the initial identification information corresponding to the mobile terminal. Understandably, if an intra-domain handover is performed, the mobile identification information should be consistent with the initial identification information; if an inter-domain handover is performed, the mobile identification information will not be consistent with the initial identification information.

[0092] Step S202: If not, determine the mobile communication flow table based on the mobile access identifier, and allocate a mobile routing identifier to the mobile switch based on the mobile identifier information;

[0093] Step S203: Establish a mobile mapping relationship between the mobile route identifier and the mobile access identifier, and determine the mobile mapping flow table based on the mobile mapping relationship.

[0094] Step S30: The mobile flow table is sent to the mobile switch so that the mobile switch can build a communication connection for the mobile terminal in the target identification network based on the mobile flow table.

[0095] It's important to understand that when a mobile handover is determined to be an inter-domain handover, the control plane first determines the mobile communication flow table between the mobile terminal and the mobile switch based on the mobile access identifier, and then sends the mobile communication flow table to the mobile switch. Next, it assigns a mobile routing identifier to the mobile switch based on the mobile identifier information and establishes a mobile mapping relationship between the mobile routing identifier and the mobile access identifier. Based on this mobile mapping relationship, it determines the mobile mapping flow table and sends it to the mobile switch. This allows the mobile switch to build a communication connection for the mobile terminal within the target identifier network based on the mobile communication flow table and the mobile mapping flow table, thus restoring the mobile terminal's communication capabilities.

[0096] When the mobile handover performed by the mobile terminal is determined to be an intra-domain handover, the control plane only needs to determine a new mobile communication flow table based on the mobile access identifier and the port information of the mobile terminal reconnecting with the mobile switch, and send the new mobile communication flow table to the mobile switch to realize the communication handover of the mobile terminal within the target identifier network and restore the communication capability of the mobile terminal.

[0097] It is easy to understand that when performing inter-domain handover, this embodiment also needs to delete the flow table information related to the mobile terminal in the switch that the mobile terminal last accessed. Specifically, the control plane can first determine the initial switch that the mobile terminal last connected to based on the initial identification information corresponding to the mobile terminal, and then send the mobile flow table to the mobile switch, and then send the flow table deletion command and the mobile access identifier to the initial switch so that the initial switch can delete the invalid flow table corresponding to the mobile terminal according to the flow table deletion command and the mobile access identifier.

[0098] As can be understood from the above analysis, this embodiment adopts a control and forwarding separation architecture. Since the control logic, such as mapping updates, during mobile handover is centrally implemented by the control plane, the handover latency mainly comes from the processing latency of the control plane. Therefore, compared to the identification network mobility management mechanism based on switches for control and forwarding, this embodiment transforms the decentralized control between switches into centralized control of the control plane. This makes the mobile handover control process no longer affected by the scale of switch devices, resulting in a relatively short and stable handover latency, thereby significantly improving the system's response efficiency. Simultaneously, in this embodiment, the control plane has global awareness of switches in the data plane. Therefore, when any terminal device connects to any switch, it can obtain mobility management-related information from the switch without signaling interaction between switches, and based on this information, quickly register the mapping relationship of the terminal device or achieve better handover performance during the handover process.

[0099] In specific implementations, such as Figure 4 As shown, Figure 4The diagram illustrates the mobile handover interaction in the first embodiment of the network management method of this invention. The control plane may include a controller and a mapping database. The mobile handover process for a mobile terminal can be as follows: The mobile terminal switches from ASR1 (the initial switch) to ASR2 (the mobile switch). First, the access point (AP) corresponding to the mobile switch ASR2 detects the mobile terminal's access and sends a mobile handover message to ASR2. Upon receiving the mobile handover message, the mobile switch ASR2 initiates the mobile handover process, transferring the message to the controller in the control plane. The controller parses the message to extract the message information and proceeds with the mobile handover process, i.e., the determination of whether it is an inter-domain or intra-domain handover (if it is an intra-domain handover, only mobile communication is sent to ASR1). When the controller determines it is an inter-domain handover, a new mobile mapping relationship is established, and the mapping relationship is updated in the mapping database. Simultaneously, the mobile communication flow table and the mobile mapping flow table are sent to ASR2, and the invalid flow table corresponding to the mobile terminal in ASR1 is deleted. This completes the mobile handover process.

[0100] This embodiment discloses an identification network management method, which includes: when an access request is detected, obtaining connection identification information corresponding to the connection switch and connection access identification corresponding to the terminal to be connected according to the access request, wherein the connection switch is a switch that forwards access requests, and the access request is a connection request sent to the connection switch when the terminal to be connected accesses the target identification network; issuing a connection communication flow table to the connection switch based on the connection access identification; allocating a connection routing identification to the connection switch according to the identification information of the connection switch, and establishing a connection mapping relationship between the terminal to be connected and the connection switch; determining a connection mapping flow table through the connection mapping relationship, and issuing the connection mapping flow table to the connection switch, so that the connection switch can construct a communication connection of the terminal to be connected in the target identification network based on the connection communication flow table and the connection mapping flow table. When a mobile packet is detected, the system obtains the mobile identification information corresponding to the mobile switch and the mobile access identifier corresponding to the mobile terminal based on the mobile packet. The mobile switch is the switch that sent the mobile packet, which is generated by the mobile switch when it detects the mobile terminal's access. The system then determines whether the mobile identification information matches the initial identification information corresponding to the mobile terminal. If not, it determines the mobile communication flow table based on the mobile access identifier and allocates a mobile routing identifier to the mobile switch based on the mobile identification information. A mobile mapping relationship is established between the mobile routing identifier and the mobile access identifier, and a mobile mapping flow table is determined based on this relationship. The mobile flow table is then distributed to the mobile switch, enabling the mobile switch to build the communication connection of the mobile terminal in the target identification network based on the mobile flow table. This embodiment adopts a control and forwarding separation architecture. Since the control logic, such as updating the mapping relationship, is centrally implemented in the control plane during mobile handover, the handover latency mainly comes from the processing latency of the control plane. Therefore, compared to the identification network mobility management mechanism based on switches for control and forwarding, this embodiment transforms the decentralized control between switches into centralized control of the control plane. This makes the mobile handover control process no longer affected by the scale of the switch equipment, resulting in a relatively short and stable handover latency, thereby significantly improving the system's response efficiency. Meanwhile, in this embodiment, the control plane has global awareness of the switches in the data plane. Therefore, when any terminal device connects to any switch, it can obtain mobility management-related information in the switch without signaling interaction between switches, and realize fast mapping relationship registration of terminal devices based on this information, or achieve better handover performance in the handover process.

[0101] Reference Figure 5 , Figure 5 This is a schematic diagram of the first process of the second embodiment of the network control method of the present invention, based on the above. Figure 1 The illustrated embodiment presents a second embodiment of the network control method of the present invention.

[0102] In this embodiment, the method includes the following steps:

[0103] Step S11: When a mobile packet is detected, the mobile packet is forwarded to the control plane so that the control plane can feed back a mobile flow table based on the mobile packet. The mobile packet is generated by the corresponding wireless access point when the mobile terminal is detected to be accessing the network.

[0104] It should be noted that in this embodiment, the above method is applied to several switches in the identification network management architecture. The control plane and data plane in the identification network management architecture are separated, several switches are set in the data plane, and several switches are connected to the terminal to be connected through a wireless access point.

[0105] It is easy to understand that existing identification networks are typically managed by switches. Therefore, when the identification network becomes too large or information exchange between switches encounters problems due to link fluctuations, the response rate of the management system can be reduced. To solve this problem, this embodiment decouples the routing and switching in the network into a data plane and a control plane, and centralizes the control logic in the identification network management process into the control plane. Specifically, the data plane is responsible for forwarding in the identification network and can flexibly design and implement different packet parsing processing flows and forwarding logic; while the control plane is responsible for the control logic of the identification network, can collect information from the data plane, implement the complex control calculation logic of the identification network, and direct the forwarding of the data plane.

[0106] Understandably, when a mobile handover occurs, the mobile terminal needs to reconnect to a new switch. In practical applications, the wireless access points (APs) corresponding to the aforementioned switches can detect whether a terminal device is connected. When any of the switch's APs detects a mobile terminal's connection, it generates a mobile packet, which may contain the mobile access identifier or communication key corresponding to the mobile terminal, and sends the mobile packet to the switch. When the switch detects the mobile packet, it can directly forward it to the control plane, allowing the control plane to update and maintain the mapping relationship before and after the mobile terminal handover based on the mobile packet. This ensures that the AID remains unchanged and the RID is reallocated before and after the handover, and feeds back the mobile flow table.

[0107] It is important to understand that after the control plane obtains the mobile identification information and mobile access identification based on the mobile message, it can update the routing identifier corresponding to the new access location (i.e., the aforementioned mobile switch) for the mobile terminal according to the mobile identification information, thereby establishing a new AID-RID mapping relationship and storing it in the aforementioned mapping database to achieve global synchronization. Here, the mobile identification information can be the device information or location information of the mobile switch, and the mobile access identification can be the access identification corresponding to the mobile terminal in the target identification network.

[0108] Step S21: Construct the communication connection of the mobile terminal in the target identifier network based on the mobile flow table.

[0109] It should be noted that the mobility flow table fed back by the control plane may include: a mobility communication flow table and a mobility mapping flow table. The mobility communication flow table is used to determine which port in the mobile exchange establishes communication between the mobile terminal and the exchange; the mobility mapping flow table is used to determine which mobile exchange the mobile terminal establishes communication with. After the exchange sends a mobility packet to the control plane, the control plane can determine whether the mobile handover of the mobile terminal is an inter-domain handover or an intra-domain handover based on the mobility packet. Specifically, when the control plane determines that the mobile handover performed by the mobile terminal is an inter-domain handover, the control plane can first determine the mobility communication flow table for communication between the mobile terminal and the mobile exchange based on the mobile access identifier, and feed back the mobility communication flow table. Then, it allocates a mobile routing identifier to the exchange based on the mobility identifier information, and establishes a mobility mapping relationship between the mobile routing identifier and the mobile access identifier, thereby determining the mobility mapping flow table based on the mobility mapping relationship, and feeding back the mobility communication flow table, so that the exchange can build a communication connection for the mobile terminal in the target identifier network based on the mobility communication flow table and the mobility mapping flow table, and restore the communication capability of the mobile terminal.

[0110] Understandably, when the control plane determines that the mobile handover performed by the mobile terminal is an intra-domain handover, the control plane only needs to determine a new mobile communication flow table based on the mobile access identifier and the port information of the mobile terminal reconnecting with the switch, and feed back the new mobile communication flow table to realize the communication handover of the mobile terminal within the target identifier network and restore the communication capability of the mobile terminal.

[0111] It is important to understand that in the current identification network mobility management mechanism, switches are not only responsible for control capabilities within the identification network, but also need to complete network forwarding through signaling interaction between switches. Since the transmission of signaling between switches consumes the forwarding performance of the switch devices, and the logical processing in the control flow also consumes the computing performance of the switch devices, the existing identification network has relatively low data throughput and low processing efficiency. To solve this problem, this embodiment can integrate some of the data forwarding processing logic into the control plane. Therefore, further, as a possible implementation, such as... Figure 6 As shown, Figure 6 This is a second flowchart illustrating a second embodiment of the network management method of the present invention. In this embodiment, the data plane further includes: a core network, an access network, and a core router. The method further includes:

[0112] Step S31: When a communication request sent by the terminal to be communicated is detected, a communication data packet is obtained according to the communication request. The header of the communication data packet is encapsulated with the destination access identifier corresponding to the terminal to be transmitted. The terminal to be communicated is a data packet sending terminal device located in the access network, and the terminal to be transmitted is a data packet receiving terminal device located in the access network.

[0113] Step S41: Detect whether the communication data packet contains a mapping flow table corresponding to the destination access identifier;

[0114] It should be noted that the data plane also includes the core network and the access network. Terminal devices are located in the access network, switches are located in the access network and at the edge of the core network, and core routers are located within the core network. Neither the core network nor the core routers are perceived by the user. During communication between terminal devices, the sender (in this embodiment, the terminal to be communicated) typically sends communication data packets to the receiver (in this embodiment, the terminal to be transmitted) through the switch and the core router. Specifically, the terminal to be communicated can send a communication request to the corresponding connected switch when communication is needed. The switch obtains the communication data packet based on the communication request. The header of this communication data packet encapsulates the destination access identifier corresponding to the terminal to be transmitted. Therefore, the switch can query whether the communication data packet contains an AID-RID mapping relationship corresponding to the terminal to be transmitted, i.e., the mapping flow table corresponding to the aforementioned destination access identifier.

[0115] Step S51: If not, send the destination access identifier and mapping query request to the control plane so that the control plane can return the destination mapping flow table, which includes the destination routing identifier;

[0116] It is understandable that communication data packets need to be sent from the core network edge to the core router via the switch corresponding to the terminal to be communicated. The core router within the core network completes the data packet transmission according to the RID, and then forwards it to the target communication switch corresponding to the terminal to be transmitted at the core network edge. Therefore, if the AID-RID mapping relationship of the destination access identifier is unknown, the switch cannot deliver the communication data packet to the terminal to be transmitted. In this case, the switch corresponding to the terminal to be communicated can extract the destination access identifier from the header encapsulation of the communication data packet and send the destination access identifier and mapping query request to the control plane so that the control plane can return the destination mapping flow table, which includes the destination routing identifier. If a mapping flow table corresponding to the destination access identifier exists, the AID-RID mapping relationship of the device to be transmitted can be directly obtained, and in this embodiment, step S61 can be directly performed.

[0117] Step S61: Encapsulate the destination routing identifier in the header of the communication data packet according to the destination mapping flow table to obtain a tagged communication data packet;

[0118] Step S71: Send the marked communication data packet to the core router in the core network, so that the core router sends the marked communication data packet to the target communication switch corresponding to the destination route identifier, and the target communication switch sends the marked communication data packet to the terminal to be transmitted according to the destination access identifier.

[0119] It should be noted that after obtaining the destination mapping flow table and then the destination routing identifier, this embodiment can encapsulate the destination routing identifier in the header of the communication data packet and send the marked communication data packet from the core network edge to the core router located inside the core network. The core router finds the target communication switch in the core network according to the destination routing identifier, and then sends the marked communication data packet to the target communication switch, so that the target communication switch sends the marked communication data packet to the terminal to be transmitted according to the destination access identifier.

[0120] As can be understood from the above analysis, this embodiment adopts a control and forwarding separation architecture and centralizes the mapping relationship query process in the data communication process to the control plane. Compared with the existing control method that uses signaling interaction between switches for data communication, since the mapping relationship query and allocation process is handled by the control plane, it no longer occupies the hardware performance and forwarding capacity of the switches. At the same time, it also reduces the number of signaling messages between switches in the identification network. Therefore, this embodiment can improve the forwarding efficiency during data communication.

[0121] This embodiment discloses an identification control method, which includes: when a mobile packet is detected, forwarding the mobile packet to the control plane so that the control plane can feed back a mobile flow table based on the mobile packet, wherein the mobile packet is generated by the corresponding radio access point when a mobile terminal is detected to access the network; and constructing a communication connection of the mobile terminal in the target identification network based on the mobile flow table. Furthermore, this embodiment can also, when a communication request sent by a terminal to be communicated is detected, obtain a communication data packet according to the communication request. The header of the communication data packet encapsulates the destination access identifier corresponding to the terminal to be transmitted. The terminal to be communicated is a data packet sending terminal device located in the access network, and the terminal to be transmitted is a data packet receiving terminal device located in the access network. It can also detect whether the communication data packet contains a mapping flow table corresponding to the destination access identifier. If not, it can send the destination access identifier and mapping query request to the control plane so that the control plane can return the destination mapping flow table, which includes a destination routing identifier. According to the destination mapping flow table, the destination routing identifier is encapsulated in the header of the communication data packet to obtain a marked communication data packet. The marked communication data packet is sent to the core router in the core network so that the core router sends the marked communication data packet to the target communication switch corresponding to the destination routing identifier. The target communication switch sends the marked communication data packet to the terminal to be transmitted according to the destination access identifier. This embodiment adopts a control and forwarding separation architecture. Since the switch directly forwards the mobile packet to the control plane after detecting it, the control logic, such as mapping updates during handover, is centrally implemented by the control plane. The handover latency mainly comes from the processing latency of the control plane. Therefore, compared to the identification network mobility management mechanism based on switch-based control and forwarding, this embodiment transforms the decentralized control between switches into centralized control of the control plane. This makes the handover control process no longer affected by the scale of switch equipment, resulting in a relatively short and stable handover latency, thus significantly improving the system's response efficiency. Simultaneously, this embodiment also centralizes the mapping query process during data communication to the control plane. Compared to existing control methods that use signaling interaction between switches for data communication, since the mapping query and allocation process is handled by the control plane, it no longer consumes the hardware performance and forwarding capacity of the switches. It also reduces the number of signaling packets between switches in the identification network. Therefore, this embodiment can improve the forwarding efficiency during data communication.

[0122] This invention provides an identification network management system, with reference to... Figure 7 , Figure 7 This is a structural diagram of the first embodiment of the network management and control system of the present invention.

[0123] like Figure 7As shown, the identification network management system proposed in this embodiment of the invention includes: a control plane and a data plane, wherein the control plane and the data plane are separated, and the data plane includes a plurality of switches, wherein the plurality of switches includes: mobile switches;

[0124] The control plane is used to obtain the mobile identification information corresponding to the mobile switch and the mobile access identifier corresponding to the mobile terminal based on the mobile packet when a mobile packet is detected. The mobile packet is generated by the mobile switch when the mobile terminal is detected to be accessing the network. The mobile terminal is a terminal device that performs mobile handover.

[0125] The control plane is also used to determine a mobile flow table based on the mobile identification information and the mobile access identifier, and to send the mobile flow table to the mobile switch;

[0126] The mobile switch is used to construct the communication connection of the mobile terminal in the target identification network based on the mobile flow table.

[0127] It is easy to understand that the aforementioned switches can be ASRs (Access Switch Routers), and in practical applications, they can be programmable commercial white-box switches. This embodiment can use white-box switches to construct a network data forwarding plane in the data plane. In this embodiment, the switches can utilize data plane programmable protocol-independent packet processing technology to implement packet parsing, packet processing, and packet forwarding functions. In the management and control system, the switches can connect to the control plane through southbound interfaces, receive management and transmission information from the control plane, implement the data plane packet parsing and processing process according to the data packet processing flow issued by the control plane, and match and forward data packets according to the flow tables issued by the control plane.

[0128] It's important to understand that the target identification network defines an Access Identifier (AID) representing the terminal device's identity information and a Route Identifier (RID) representing the terminal device's access location information. A mapping mechanism between these two identifiers is established, and this mapping mechanism can be stored in the control plane's mapping database. Specifically, the Access Identifier corresponds one-to-one with the terminal device's device information, and the Route Identifier corresponds one-to-one with the device information of the switch the terminal device is connected to. In the target identification network, when a terminal device undergoes a handover (i.e., the switch it's connected to changes), the terminal device's Access Identifier remains unchanged; only the Route Identifier representing the access location information changes. This means a new Route Identifier needs to be assigned to the mobile terminal, and the mobile terminal can be the one undergoing the handover.

[0129] Understandably, when a handover occurs, the mobile terminal needs to reconnect to a new switch, namely the aforementioned mobile switch. In practical applications, the wireless access point (AP) corresponding to this mobile switch can detect whether a terminal device is connected. When the mobile switch detects a mobile terminal's connection, it generates a mobile packet, which may contain the mobile access identifier or communication key corresponding to the mobile terminal. This mobile packet is then sent to the control plane, allowing the control plane to update and maintain the mapping relationship before and after the handover, ensuring that the AID remains unchanged and the RID is reassigned. The aforementioned mobile identifier information can be the device information or location information of the mobile switch, and the aforementioned mobile access identifier can be the access identifier corresponding to the mobile terminal in the target identification network.

[0130] It is important to understand that after the control plane obtains the mobile identification information and mobile access identifier based on the mobile message, it can update the routing identifier corresponding to the new access location (i.e., the aforementioned mobile switch) for the mobile terminal according to the mobile identification information, thereby establishing a new AID-RID mapping relationship and storing it in the aforementioned mapping database to achieve global synchronization. The aforementioned mobile terminal handover can also be divided into intra-domain handover or inter-domain handover. Intra-domain handover refers to the mobile terminal switching from one port of the mobile switch to another port; while inter-domain handover refers to the mobile terminal switching switches. To implement this discrimination process, this embodiment can set up a controller in the control plane. Therefore, further, as one possible implementation, in this embodiment, the control plane includes: at least one controller, which is connected to the plurality of switches respectively.

[0131] The controller is used to determine whether the mobile identification information is consistent with the initial identification information corresponding to the mobile terminal;

[0132] The controller is further configured to, if not, determine the mobile communication flow table based on the mobile access identifier, and allocate a mobile routing identifier to the mobile switch based on the mobile identifier information;

[0133] The controller is further configured to establish a mobile mapping relationship between the mobile route identifier and the mobile access identifier, and to determine the mobile mapping flow table based on the mobile mapping relationship.

[0134] It should be noted that when the controller receives a mobile packet uploaded by the mobile switch, it can first determine whether the mobile identification information corresponding to the mobile switch is consistent with the initial identification information corresponding to the mobile terminal. Understandably, if a handover is performed within a domain, the mobile identification information should be consistent with the initial identification information; if a handover is performed between domains, the mobile identification information will be inconsistent with the initial identification information.

[0135] It's important to understand that when a mobile handover is determined to be an inter-domain handover, the controller first determines the mobile communication flow table between the mobile terminal and the mobile switch based on the mobile access identifier, and then sends the mobile communication flow table to the mobile switch. Next, it assigns a mobile routing identifier to the mobile switch based on the mobile identifier information and establishes a mobile mapping relationship between the mobile routing identifier and the mobile access identifier. Based on this mobile mapping relationship, it determines the mobile mapping flow table and sends it to the mobile switch. This allows the mobile switch to build a communication connection for the mobile terminal within the target identifier network based on the mobile communication flow table and the mobile mapping flow table, thus restoring the mobile terminal's communication capabilities.

[0136] When the mobile handover performed by the mobile terminal is determined to be an intra-domain handover, the controller only needs to determine a new mobile communication flow table based on the mobile access identifier and the port information of the mobile terminal reconnecting with the mobile switch, and send the new mobile communication flow table to the mobile switch to realize the communication handover of the mobile terminal within the target identifier network and restore the communication capability of the mobile terminal.

[0137] It is easy to understand that when performing inter-domain handover, this embodiment also needs to delete the flow table information related to the mobile terminal in the switch that the mobile terminal last accessed. Specifically, the controller can first determine the initial switch that the mobile terminal last connected to based on the initial identification information corresponding to the mobile terminal, and then send the mobile flow table to the mobile switch after sending it. Then, it sends the flow table deletion command and the mobile access identifier to the initial switch so that the initial switch can delete the invalid flow table corresponding to the mobile terminal according to the flow table deletion command and the mobile access identifier.

[0138] As can be understood from the above analysis, this embodiment adopts a control and forwarding separation architecture. Since the control logic, such as mapping updates, during mobile handover is centrally implemented by the control plane, the handover latency mainly comes from the processing latency of the control plane. Therefore, compared to the identification network mobility management mechanism based on switches for control and forwarding, this embodiment transforms the decentralized control between switches into centralized control of the control plane. This makes the mobile handover control process no longer affected by the scale of switch devices, resulting in a relatively short and stable handover latency, thereby significantly improving the system's response efficiency. Simultaneously, in this embodiment, the control plane has global awareness of switches in the data plane. Therefore, when any terminal device connects to any switch, it can obtain mobility management-related information from the switch without signaling interaction between switches, and based on this information, quickly register the mapping relationship of the terminal device or achieve better handover performance during the handover process.

[0139] This embodiment discloses an identification network management system, which includes a control plane and a data plane, which are separated. The data plane includes several switches, including a mobile switch. The control plane is used to obtain the mobile identification information corresponding to the mobile switch and the mobile access identifier corresponding to the mobile terminal based on the mobile packet when a mobile packet is detected. The mobile packet is generated by the mobile switch when a mobile terminal is detected to be accessing the network, and the mobile terminal is a terminal device performing mobile handover. The control plane is also used to determine a mobile flow table based on the mobile identification information and the mobile access identifier, and to distribute the mobile flow table to the mobile switch. The mobile switch is used to construct the communication connection of the mobile terminal in the target identification network based on the mobile flow table. The control plane includes at least one controller, which is connected to several switches. The controller is used to determine whether the mobile identification information is consistent with the initial identification information corresponding to the mobile terminal. If not, the controller is also used to determine a mobile communication flow table based on the mobile access identifier and to allocate a mobile routing identifier to the mobile switch based on the mobile identification information. The controller is also used to establish a mobile mapping relationship between the mobile routing identifier and the mobile access identifier, and to determine a mobile mapping flow table based on the mobile mapping relationship. This embodiment adopts a control and forwarding separation architecture. Since the control logic such as mapping relationship updates during mobile handover is centrally implemented by the control plane, the handover latency mainly comes from the processing latency of the control plane. Therefore, compared with the identification network mobility management mechanism based on switches for control and forwarding, this embodiment transforms the decentralized control between switches into centralized control of the control plane. This makes the mobile handover control process no longer affected by the scale of switch equipment, and the handover latency is relatively short and stable, thereby significantly improving the system's response efficiency.

[0140] Reference Figure 8 , Figure 8 This is a structural diagram of the second embodiment of the network management and control system of the present invention, based on the above. Figure 7 The first embodiment shown is followed by a second embodiment of the network management system of the present invention.

[0141] like Figure 8 As shown, in this embodiment, the control plane further includes a mapping database, and the controller includes a management module, a mobility module, and a mapping module;

[0142] The management module is used to, when the mobile packet is detected, obtain the mobile identification information of the mobile switch and the mobile access identifier corresponding to the mobile terminal according to the mobile packet, and send the mobile identification information and the mobile access identifier to the mobility module;

[0143] The mobility module is used to determine whether the mobility identification information is consistent with the initial identification information corresponding to the mobile terminal;

[0144] The mobility module is further configured to, if not, send the mobile communication flow table to the mobile switch based on the mobile access identifier, and send the mobile identifier information and the mobile access identifier to the mapping module;

[0145] The mapping module is used to allocate a mobile routing identifier to the mobile switch according to the mobile identification information, and to establish a mobile mapping relationship between the mobile routing identifier and the mobile access identifier;

[0146] The mapping module is further configured to update the mapping by sending the mobile mapping relationship to the mapping database, and to send the mobile mapping flow table to the mobile switch according to the mobile mapping relationship.

[0147] It should be noted that the aforementioned management module is used to manage the connection between the control plane and the data plane, including sensing data plane devices and driving the controller to connect to white-box devices, issuing data packet processing procedures to the data plane white-box switching devices, processing and parsing messages forwarded by the data plane and sensing their intent to execute corresponding processing procedures. For ease of understanding, let's use... Figure 9 Let's take an example to illustrate this. Figure 9 This is a schematic diagram of the management module in the second embodiment of the network control system of the present invention, as shown below. Figure 9 As shown, the management module may include a pipeline module and a packet processor. The pipeline module can monitor, deploy, and control the switches in the data plane using the controller's southbound interface. The packet processor is responsible for connecting the data plane and the control plane in terms of network function implementation. It is the starting point of the network function flow in the controller, using the packet_in channel in the controller to obtain data packets transferred from the data plane to the control plane, and performs intent parsing and information acquisition on the data packets to initiate the processing flow of different network functions.

[0148] It should be understood that the aforementioned mobility module is used to handle communication recovery after a mobile terminal performs a handover. For ease of understanding, let's use... Figure 10 Let's take an example to illustrate this. Figure 10 This is a schematic diagram of the mobility module in the second embodiment of the network management system of the present invention, as shown below. Figure 10As shown, the mobility module may include an intra-domain handover module, a mobility type awareness module, and an inter-domain handover module. In practical applications, when a mobile terminal accesses a new switch (i.e., the aforementioned mobile switch), the wireless access point corresponding to the mobile switch can send a mobile handover message to the mobile terminal after sensing the terminal's access. The mobile switch then forwards the mobile message to the management module in the controller for parsing and processing. The management module then transmits the extracted mobile identification information of the mobile switch and the mobile access identifier corresponding to the mobile terminal to the mobility type awareness module in the mobility module. The mobility type awareness module can determine whether the mobile terminal has moved out of the switch's access domain range before and after the handover based on the mobile identification information. Specifically, in this embodiment, the mobility type awareness module can detect whether the mobile identification information is consistent with the initial identification information corresponding to the mobile terminal. When the mobility type awareness module determines that the mobile terminal is performing an inter-domain handover, it can hand it over to the inter-domain handover module in the mobility module for processing, deleting the invalid flow table in the initial switch that the mobile terminal last connected to, maintaining the correct flow table logic, and issuing the mobile communication flow table to the mobile switch based on the mobile access identifier. Meanwhile, the inter-domain handover module can send mobile identification information and mobile access identification to the mapping module, so that it can update the mapping relationship for the mobile terminal. When the mapping relationship is updated and synchronized globally, the flow table logic in the data plane switching device returns to normal, and the corresponding mobile terminal communication can also be restored.

[0149] When the mobility type awareness module determines that the mobile terminal is performing an intra-domain handover, it can be handed over to the intra-domain handover module in the mobility module for processing. Based on the mobile access identifier and the port information of the mobile terminal reconnecting with the mobile switch, a new mobile communication flow table is determined and sent to the mobile switch. This enables the mobile terminal to switch communication within the target identifier network and restores the mobile terminal's communication capabilities.

[0150] It is understandable that the aforementioned mapping module can be used to handle the mapping relationship between terminals and switches, including: registering the mapping relationship for new terminal devices, querying the mapping relationship for terminal devices in external access domains, updating the mapping relationship for mobile handover terminal devices, and interacting with the database storing the mapping relationship. For ease of understanding, let's use... Figure 11 Let's take an example to illustrate this. Figure 11 This is a schematic diagram of the mapping module in the second embodiment of the network management system of the present invention, as shown below. Figure 11As shown, the mapping module may include a mapping registration module, a mapping update module, and a mapping query module. In practical applications, when the mobility module needs to update the mobile terminal mapping relationship, the mapping update module in the mapping module updates the RID of the mobile terminal according to the location information of the switch where the mobile terminal is located after the handover, writes the updated AID-RID mapping relationship into the mapping database to achieve global synchronization, and at the same time sends the mobile mapping flow table related to the updated mapping relationship to the mobile switch corresponding to the mobile terminal after the handover.

[0151] It is understood that any terminal device needs to register the AID-RID mapping relationship when it first accesses the target identifier network. Therefore, as a possible implementation, in this embodiment, the plurality of switches include: a connection switch;

[0152] The management module is also used to obtain the connection identifier information corresponding to the connection switch and the connection access identifier corresponding to the terminal to be connected according to the access request when an access request is detected. The access request is a connection request sent to the connection switch when the terminal to be connected accesses the target identifier network.

[0153] The management module is also used to send the connection access identifier to the mobility module;

[0154] The mobility module is also configured to send a connection communication flow table to the connection switch based on the connection access identifier;

[0155] The management module is also used to send the connection identification information to the mapping module;

[0156] The mapping module is further configured to allocate a connection route identifier to the connection switch according to the connection identifier information, establish a connection mapping relationship between the connection route identifier and the connection access identifier, and send the connection mapping relationship to the mapping database so that the mapping database stores the connection mapping relationship;

[0157] The mapping module is further configured to send the connection mapping flow table to the connection switch through the connection mapping relationship, so that the connection switch can construct the communication connection of the terminal to be connected in the target identification network based on the connection communication flow table and the connection mapping flow table.

[0158] It should be noted that in practical applications, when the pipeline module in the management module receives an access request forwarded by the connection switch in the data plane, the packet processor obtains the connection identifier information corresponding to the connection switch and the connection access identifier corresponding to the terminal to be connected based on the access request. The packet processor then sends the connection access identifier to the mobility module, enabling the mobility module to issue a connection communication flow table to the connection switch based on the connection access identifier. The packet processor then passes the connection identifier information and the connection access identifier to the mapping registration module in the mapping module. The mapping registration module assigns a connection routing identifier to the connection switch based on the connection identifier information, establishes a connection mapping relationship between the connection routing identifier and the connection access identifier, and sends the connection mapping relationship to the mapping database for storage. Finally, the mapping update module issues the connection mapping flow table related to the mapping relationship to the connection switch. After the connection communication flow table and connection mapping flow table in the connection switch take effect, the corresponding connection terminal can communicate in the target identifier network.

[0159] It is important to understand that in this embodiment, the mobile terminal's AID (i.e., the aforementioned mobile access identifier) ​​remains unchanged before and after the handover, while the RID is reassigned. Therefore, the network layer supports terminal mobility. Furthermore, since the AID remains unchanged, the mobile terminal's communication will not be interrupted during the movement. The RID reassignment process is completed by the identifier network management system and is transparent to the terminal. The entire mobile handover process is implemented by the network layer without the need for upper-layer network involvement, thus achieving inherent network support for mobility and achieving the effect of uninterrupted service and device unawareness, thereby improving the user experience.

[0160] In this embodiment, the control plane further includes a mapping database. The controller includes a management module, a mobility module, and a mapping module. The management module is used to obtain the mobile identification information of the mobile switch and the mobile access identifier corresponding to the mobile terminal based on the mobile packet when a mobile packet is detected, and send the mobile identification information and the mobile access identifier to the mobility module. The mobility module is used to determine whether the mobile identification information is consistent with the initial identification information corresponding to the mobile terminal. If not, the mobility module is also used to issue a mobile communication flow table to the mobile switch based on the mobile access identifier and send the mobile identification information and the mobile access identifier to the mapping module. The mapping module is used to allocate a mobile routing identifier to the mobile switch based on the mobile identification information and establish a mobile mapping relationship between the mobile routing identifier and the mobile access identifier. The mapping module is also used to send the mobile mapping relationship to the mapping database for mapping update and issue a mobile mapping flow table to the mobile switch based on the mobile mapping relationship. Several switches include: a connection switch; a management module, which, when an access request is detected, obtains the connection identifier information corresponding to the connection switch and the connection access identifier corresponding to the terminal to be connected based on the access request, wherein the access request is a connection request sent to the connection switch when the terminal to be connected accesses the target identifier network; the management module, which is also used to send the connection access identifier to the mobility module; the mobility module, which is also used to issue a connection communication flow table to the connection switch based on the connection access identifier; the management module, which is also used to send the connection identifier information to the mapping module; the mapping module, which is also used to allocate a connection routing identifier to the connection switch based on the connection identifier information, establish a connection mapping relationship between the connection routing identifier and the connection access identifier, and send the connection mapping relationship to the mapping database so that the mapping database stores the connection mapping relationship; and the mapping module, which is also used to issue a connection mapping flow table to the connection switch through the connection mapping relationship so that the connection switch constructs the communication connection of the terminal to be connected in the target identifier network based on the connection communication flow table and the connection mapping flow table. In this embodiment, during mobile handover, the mobile access identifier (RID) corresponding to the mobile terminal remains unchanged. The network simply reassigns a mobile routing identifier (RID) to the newly connected mobile switch. This achieves network-layer support for terminal mobility. Furthermore, because the RID remains unchanged, communication between the mobile terminal and the network remains uninterrupted during movement. The RID reassignment process is completed by the identifier network management system, transparent to the terminal. The entire mobile handover process is implemented at the network layer without the need for upper-layer network intervention, achieving inherent network support for mobility and ensuring uninterrupted service without device awareness, thus improving user experience. In addition, when any terminal device connects to any switch, it can obtain mobility management information from the switch without signaling interaction between switches, and quickly register the terminal device's mapping relationship based on this information, further enhancing the user experience.

[0161] Reference Figure 12 , Figure 12 This is a structural diagram of the third embodiment of the network management and control system of the present invention, based on the above. Figure 7 The first embodiment shown or the above Figure 8 The second embodiment shown presents a third embodiment of the network management system of the present invention.

[0162] like Figure 12 As shown, based on the first or second embodiment of the identification network management system of the present invention, a third embodiment of the identification network management system of the present invention is proposed.

[0163] In this embodiment, the data plane further includes: a core network, an access network, and a core router; the plurality of switches include: a source communication switch and a destination communication switch.

[0164] The source communication switch is used to obtain a communication data packet according to the communication request when a communication request sent by the terminal to be communicated is detected. The header of the communication data packet is encapsulated with a destination access identifier corresponding to the terminal to be communicated and the terminal to be transmitted. The terminal to be communicated is a data packet sending terminal device located in the access network, and the terminal to be transmitted is a data packet receiving terminal device located in the access network.

[0165] The source communication switch is also used to detect whether the communication data packet contains a mapping flow table corresponding to the destination access identifier;

[0166] The source communication switch is further configured to send the destination access identifier and mapping query request to the management module if no;

[0167] The management module is also used to send the destination access identifier and mapping query request to the mapping module;

[0168] The mapping module is further configured to send the destination access identifier to the mapping database, so that the mapping database can provide feedback on the destination mapping relationship corresponding to the destination access identifier;

[0169] The mapping module is further configured to establish a destination mapping flow table based on the destination mapping relationship, and to send the destination mapping flow table to the source communication switch, wherein the destination mapping flow table contains a destination route identifier;

[0170] The source communication switch is further configured to encapsulate the destination route identifier in the header of the communication data packet according to the destination mapping flow table, obtain a tagged communication data packet, and send the tagged communication data packet to the core router in the core network;

[0171] The core router is used to send the marked communication data packet to the target communication switch corresponding to the destination route identifier;

[0172] The target communication switch is used to send the marked communication data packet to the terminal to be transmitted according to the destination access identifier.

[0173] It should be noted that the source communication switch mentioned above can be the switch connected to the terminal to be communicated with, and the destination communication switch can be the switch connected to the terminal to be transmitted. For example... Figure 12 As shown, in this embodiment, the identification control system may include a control plane and a data plane. The data plane may include: a basic network consisting of an access network and a core network, wireless terminals (including: mobile terminal devices MN and fixed terminal devices CN), ASR (Access Switching Router, corresponding to the switch in this embodiment), AP (Access Point), and CR (Core Router). The control plane may include: a controller and a mapping database. Figure 12 In this context, ASR1 refers to the source communication switch, and ASR3 refers to the destination communication switch. Correspondingly, ASRs and RIDs are the source access identifier and source routing identifier corresponding to the source communication switch; ASRd and RIDd are the destination access identifier and destination routing identifier corresponding to the destination communication switch. In practical applications, when the management module receives a mapping query request from the data plane, it passes the corresponding destination access identifier to the mapping query module within the mapping module. The mapping module queries the corresponding AID-RID mapping relationship (i.e., the aforementioned destination mapping relationship) based on the destination access identifier, establishes a destination mapping flow table based on the destination mapping relationship, and sends the destination routing identifier to the source communication switch that initiated the mapping query request, enabling the source communication switch to complete the encapsulation of communication data packets entering the core network.

[0174] It should be noted that after obtaining the destination mapping flow table and then the destination routing identifier, this embodiment can encapsulate the destination routing identifier in the header of the communication data packet and send the marked communication data packet from the core network edge to the core router located inside the core network. The core router finds the target communication switch in the core network according to the destination routing identifier, and then sends the marked communication data packet to the target communication switch, so that the target communication switch sends the marked communication data packet to the terminal to be transmitted according to the destination access identifier.

[0175] As can be understood from the above analysis, this embodiment adopts a control and forwarding separation architecture and centralizes the mapping relationship query process in the data communication process to the control plane. Compared with the existing control method that uses signaling interaction between switches for data communication, since the mapping relationship query and allocation process is handled by the control plane, it no longer occupies the hardware performance and forwarding capacity of the switches. At the same time, it also reduces the number of signaling messages between switches in the identification network. Therefore, this embodiment can improve the forwarding efficiency during data communication.

[0176] In this embodiment, the data plane further includes: a core network, an access network, and a core router; several switches include: source communication switches and destination communication switches; the source communication switch is used to obtain communication data packets according to the communication request when a communication request sent by a terminal to be communicated is detected. The header of the communication data packet encapsulates the destination access identifier corresponding to the terminal to be communicated and the terminal to be transmitted. The terminal to be communicated is a data packet sending terminal device located in the access network, and the terminal to be transmitted is a data packet receiving terminal device located in the access network; the source communication switch is also used to detect whether the communication data packet contains a mapping flow table corresponding to the destination access identifier; the source communication switch is also used to send a destination access identifier and mapping query request to the management module if not; the management module is also used to transfer the destination access identifier and mapping query... The query request is sent to the mapping module; the mapping module is also used to send the destination access identifier to the mapping database so that the mapping database can return the destination mapping relationship corresponding to the destination access identifier; the mapping module is also used to establish a destination mapping flow table according to the destination mapping relationship and distribute the destination mapping flow table to the source communication switch, the destination mapping flow table containing the destination routing identifier; the source communication switch is also used to encapsulate the destination routing identifier in the header of the communication data packet according to the destination mapping flow table, obtain the marked communication data packet, and send the marked communication data packet to the core router in the core network; the core router is used to send the marked communication data packet to the target communication switch corresponding to the destination routing identifier; the target communication switch is used to send the marked communication data packet to the terminal to be transmitted according to the destination access identifier. In this embodiment, the mapping relationship query process in the data communication process is centralized in the control plane. Compared with the existing control method that uses signaling interaction between switches for data communication, since the mapping relationship query and allocation process is handled by the control plane, it no longer occupies the hardware performance and forwarding capacity of the switch, and also reduces the number of signaling messages between switches in the identifier network. Therefore, this embodiment can improve the forwarding efficiency during data communication.

[0177] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0178] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0179] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0180] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

Claims

1. A method for network management and control, characterized in that, The method is applied to the control plane in an identification network management architecture, wherein the control plane and data plane are separated, and the data plane includes several switches. The method includes: When a mobile packet is detected, the mobile identification information corresponding to the mobile switch and the mobile access identifier corresponding to the mobile terminal are obtained according to the mobile packet. The mobile switch is the switch that sent the mobile packet. The mobile packet is generated by the mobile switch when it detects the access of the mobile terminal. A mobile flow table is determined based on the mobile identification information and the mobile access identifier. The mobile flow table includes a mobile communication flow table and a mobile mapping flow table. The mobile communication flow table is used to determine which port in the mobile switch the mobile terminal establishes communication with, and the mobile mapping flow table is used to determine which mobile switch the mobile terminal establishes communication with. The mobile flow table is sent to the mobile switch so that the mobile switch can construct the communication connection of the mobile terminal in the target identification network based on the mobile flow table. The step of determining the mobile flow table based on the mobile identification information and the mobile access identifier includes: Determine whether the mobile identification information is consistent with the initial identification information corresponding to the mobile terminal; If so, then the mobile communication flow table is determined based on the mobile access identifier and the port information of the mobile terminal reconnecting with the mobile switch, and the mobile communication flow table is sent to the mobile switch; If not, the mobile communication flow table is determined based on the mobile access identifier, and a mobile routing identifier is allocated to the mobile switch based on the mobile identifier information. A mobile mapping relationship is established between the mobile routing identifier and the mobile access identifier, and the mobile mapping flow table is determined based on the mobile mapping relationship. The mobile communication flow table and the mobile mapping flow table are then sent to the mobile switch.

2. The identification network management method as described in claim 1, characterized in that, Before obtaining the mobile identification information corresponding to the mobile switch and the mobile access identifier corresponding to the mobile terminal based on the mobile packet when a mobile packet is detected, the method further includes: When an access request is detected, the connection identifier information corresponding to the connection switch and the connection access identifier corresponding to the terminal to be connected are obtained according to the access request. The connection switch is a switch that forwards the access request. The access request is a connection request sent to the connection switch when the terminal to be connected accesses the target identifier network. Based on the connection access identifier, a connection communication flow table is sent to the connection switch; Assign a connection route identifier to the connection switch based on the identification information of the connection switch, and establish a connection mapping relationship between the terminal to be connected and the connection switch; The connection mapping relationship is used to determine the connection mapping flow table, and the connection mapping flow table is sent to the connection switch so that the connection switch can construct the communication connection of the terminal to be connected in the target identification network based on the connection communication flow table and the connection mapping flow table.

3. A method for network management and control, characterized in that, The method is applied to several switches in an identification network management architecture, wherein the control plane and data plane are separated in the identification network management architecture, the several switches are located on the data plane, and the several switches are connected to the terminal to be connected via a wireless access point. The method includes: When a mobile packet is detected, the mobile packet is forwarded to the control plane so that the control plane can feed back a mobile flow table based on the mobile packet. The mobile packet is generated by the corresponding wireless access point when the mobile terminal is detected to be accessing the network. The communication connection of the mobile terminal in the target identifier network is constructed based on the mobile flow table; The mobile flow table includes a mobile communication flow table and a mobile mapping flow table; The control plane is used to determine whether the mobile identification information is consistent with the initial identification information corresponding to the mobile terminal; if yes, it determines a mobile communication flow table based on the mobile access identifier and the port information for the mobile terminal to reconnect with the mobile switch, and sends the mobile communication flow table to the mobile switch; if no, it determines the mobile communication flow table based on the mobile access identifier, allocates a mobile routing identifier to the mobile switch based on the mobile identification information, establishes a mobile mapping relationship between the mobile routing identifier and the mobile access identifier, determines the mobile mapping flow table based on the mobile mapping relationship, and sends the mobile communication flow table and the mobile mapping flow table to the mobile switch.

4. The identification network management method as described in claim 3, characterized in that, The data plane further includes: a core network, an access network, and a core router; the method includes: When a communication request sent by a terminal to be communicated is detected, a communication data packet is obtained according to the communication request. The header of the communication data packet is encapsulated with a destination access identifier corresponding to the terminal to be transmitted. The terminal to be communicated is a data packet sending terminal device located in the access network, and the terminal to be transmitted is a data packet receiving terminal device located in the access network. Detect whether the communication data packet contains a mapping flow table corresponding to the destination access identifier; If not, the destination access identifier and mapping query request are sent to the control plane so that the control plane can return the destination mapping flow table, which includes the destination route identifier; The destination route identifier is encapsulated in the header of the communication data packet according to the destination mapping flow table to obtain a tagged communication data packet; The tagged communication data packet is sent to the core router in the core network, so that the core router sends the tagged communication data packet to the target communication switch corresponding to the destination route identifier, and the target communication switch sends the tagged communication data packet to the terminal to be transmitted according to the destination access identifier.

5. A network identification and control system, characterized in that, The system includes a control plane and a data plane, which are separate. The data plane includes a plurality of switches, including a mobile switch. The control plane is used to obtain the mobile identification information corresponding to the mobile switch and the mobile access identifier corresponding to the mobile terminal based on the mobile packet when a mobile packet is detected. The mobile packet is generated by the mobile switch when the mobile terminal is detected to be accessing the network. The mobile terminal is a terminal device that performs mobile handover. The control plane is further configured to determine a mobile flow table based on the mobile identification information and the mobile access identifier, and to send the mobile flow table to the mobile switch. The mobile flow table includes a mobile communication flow table and a mobile mapping flow table. The mobile communication flow table is used to determine which port in the mobile switch the mobile terminal establishes communication with, and the mobile mapping flow table is used to determine which mobile switch the mobile terminal establishes communication with. The mobile switch is used to construct the communication connection of the mobile terminal in the target identification network based on the mobile flow table; The control plane is further configured to determine whether the mobile identification information is consistent with the initial identification information corresponding to the mobile terminal; if so, it determines a mobile communication flow table based on the mobile access identifier and the port information for the mobile terminal to reconnect with the mobile switch, and sends the mobile communication flow table to the mobile switch; if not, it determines the mobile communication flow table based on the mobile access identifier, allocates a mobile routing identifier to the mobile switch based on the mobile identification information, establishes a mobile mapping relationship between the mobile routing identifier and the mobile access identifier, determines the mobile mapping flow table based on the mobile mapping relationship, and sends the mobile communication flow table and the mobile mapping flow table to the mobile switch.

6. The identification network management system as described in claim 5, characterized in that, The control plane includes at least one controller, which is connected to the plurality of switches respectively.

7. The identification network management system as described in claim 6, characterized in that, The control plane further includes a mapping database, and the controller includes a management module, a mobility module, and a mapping module. The management module is used to, when the mobile packet is detected, obtain the mobile identification information of the mobile switch and the mobile access identifier corresponding to the mobile terminal according to the mobile packet, and send the mobile identification information and the mobile access identifier to the mobility module; The mobility module is used to determine whether the mobility identification information is consistent with the initial identification information corresponding to the mobile terminal; The mobility module is further configured to, if not, send the mobile communication flow table to the mobile switch based on the mobile access identifier, and send the mobile identifier information and the mobile access identifier to the mapping module; The mapping module is used to allocate a mobile routing identifier to the mobile switch according to the mobile identification information, and to establish a mobile mapping relationship between the mobile routing identifier and the mobile access identifier; The mapping module is further configured to send the mobile mapping relationship to the mapping database for mapping update, and issue the mobile mapping flow table to the mobile switch according to the mobile mapping relationship.

8. The identification network management system as described in claim 7, characterized in that, The plurality of switches includes: a connection switch; The management module is also used to obtain the connection identifier information corresponding to the connection switch and the connection access identifier corresponding to the terminal to be connected according to the access request when an access request is detected. The access request is a connection request sent to the connection switch when the terminal to be connected accesses the target identifier network. The management module is also used to send the connection access identifier to the mobility module; The mobility module is also configured to send a connection communication flow table to the connection switch based on the connection access identifier; The management module is also used to send the connection identification information to the mapping module; The mapping module is further configured to allocate a connection route identifier to the connection switch according to the connection identifier information, establish a connection mapping relationship between the connection route identifier and the connection access identifier, and send the connection mapping relationship to the mapping database so that the mapping database stores the connection mapping relationship; The mapping module is further configured to send the connection mapping flow table to the connection switch through the connection mapping relationship, so that the connection switch can construct the communication connection of the terminal to be connected in the target identification network based on the connection communication flow table and the connection mapping flow table.

9. The identification network management system as described in claim 8, characterized in that, The data plane further includes: a core network, an access network, and core routers; the plurality of switches includes: source communication switches and destination communication switches; The source communication switch is used to obtain a communication data packet according to the communication request when a communication request sent by the terminal to be communicated is detected. The header of the communication data packet is encapsulated with a destination access identifier corresponding to the terminal to be communicated and the terminal to be transmitted. The terminal to be communicated is a data packet sending terminal device located in the access network, and the terminal to be transmitted is a data packet receiving terminal device located in the access network. The source communication switch is also used to detect whether the communication data packet contains a mapping flow table corresponding to the destination access identifier; The source communication switch is further configured to send the destination access identifier and mapping query request to the management module if no; The management module is also used to send the destination access identifier and mapping query request to the mapping module; The mapping module is further configured to send the destination access identifier to the mapping database, so that the mapping database can provide feedback on the destination mapping relationship corresponding to the destination access identifier; The mapping module is further configured to establish a destination mapping flow table based on the destination mapping relationship, and to send the destination mapping flow table to the source communication switch, wherein the destination mapping flow table contains a destination route identifier; The source communication switch is further configured to encapsulate the destination route identifier in the header of the communication data packet according to the destination mapping flow table, obtain a tagged communication data packet, and send the tagged communication data packet to the core router in the core network; The core router is used to send the marked communication data packet to the target communication switch corresponding to the destination route identifier; The target communication switch is used to send the marked communication data packet to the terminal to be transmitted according to the destination access identifier.

Images