CN102547908B - Listing maintenance, system and IAD router - Google Patents

Abstract

The present invention provides a table maintenance method, system and access gateway router, wherein the table maintenance method includes: the access gateway router (AGR) obtains and saves the user type information of the local user equipment (UE); obtain the mapping relationship between the AID of the peer UE and the routing identifier (RID); and maintain the peer table entry according to the mapping relationship and the saved user type information of the local UE. The above table maintenance method, system and access gateway router can effectively reduce the number of peer table entries maintained by the AGR, reduce equipment costs, and improve table lookup performance.

Description

Table maintenance method, system and access gateway router

technical field

The invention relates to the technical field of communication, in particular to a table maintenance method, system and access gateway router.

Background technique

The IP address in Transmission Control Protocol/Internet Protocol (TCP/IP), which is widely used in the Internet, has dual functions. As the identity of the network interface of the transport layer host. The TCP/IP protocol did not consider the movement of the host at the beginning of its design. However, when the host mobile becomes more and more common, the semantic overload defect of this IP address becomes more and more obvious. When the IP address of the host changes, not only the route changes, but also the identity of the communication terminal host changes, which will lead to a heavier and heavier routing load, and the change of the host identity will also cause the interruption of applications and connections.

The purpose of the separation of identity and location is to solve the problems of semantic overload of IP addresses and serious routing load, and to separate the dual functions of IP addresses, so as to realize mobility, multi-homing, dynamic redistribution of IP addresses, and ease of routing. Support for issues such as load and mutual visits between different network areas in the next generation Internet.

In the prior art, a network-based identity identification and location separation scheme (hereinafter referred to as identification network) is proposed. The basic idea of this scheme is: the network is divided into access layer and core layer, and mobile nodes in the network There are two identification types: Access Identifier (AID for short) and Routing-Location Identifier (RID for short). Configure a unique AID for each user in the network, and the AID will remain unchanged during the moving process; during the data forwarding process, the AID can only be used at the access layer, and the RID can only be used at the core layer; between user terminals When the application layer communicates, use the AID to identify the peer.

The topology diagram of the network-based identity and location separation framework is shown in Figure 1. In the network-based identity and location separation framework, it mainly includes: radio access network (RAN) 11, access gateway router (Access Gateway Router, referred to as AGR) 12, generalized gateway router (General Switch Router, referred to as GSR) 13, mapping server (Identifier Mapping Server, referred to as IDMS) 14 and authentication center 15, etc.; where:

AGR is responsible for providing access services for various mobile nodes, allocating RIDs for accessing users, and marking and encapsulating user data packets for transmission in the backbone network.

When AGR receives the data message sent by the terminal, it queries the AID-RID mapping table in the local cache (CACHE) according to the destination address in the data message (that is, the AID of the communication peer): if the corresponding AID-RID mapping is found entry, the found RID of the communication terminal is encapsulated in the message header and sent to the backbone network for forwarding processing; if no corresponding AID-RID mapping entry is found, the data message is forwarded to the backbone network and sent to the IDMS Initiate the process of querying (communication peer) AID-RID mapping information, and store the corresponding AIDc-RIDc mapping returned by the IDMS locally for query when subsequent message forwarding.

Or, when the AGR does not find the corresponding AID-RID mapping entry, it can also choose not to forward the data message to the backbone network, but initiates the process of querying the (communication peer) AID-RID mapping information to the IDMS. After returning the corresponding AIDc-RIDc mapping, the found RID of the communication terminal is encapsulated in the message header and sent to the backbone network for forwarding processing.

When the AGR receives the data message sent to the terminal, it decapsulates the data message, strips off the newly added message header containing the RID in the data message, and sends it to the terminal.

The main function of the GSR is to select routes and forward data packets according to the routing location identifier RID in the data packets.

IDMS is mainly responsible for maintaining the mapping relationship between user IDs and location IDs in the network, and providing query services to access gateway routers and other mapping servers.

The authentication center is responsible for recording information such as user categories and user service levels, and performs legal authentication and authorization for users when they access. The authentication center supports two-way authentication between the network and users.

The wireless access network is responsible for providing and maintaining the Layer 2 link between the user terminal and the access gateway router AGR; it is responsible for wireless resource management in the application scenario of the cellular mobile network.

The following describes a method for implementing handover management supported by mobility under the above-mentioned network architecture. The correspondent node (Correspondent Node, referred to as CN) of the mobile node establishes communication with the mobile node (Mobile Node, referred to as MN), and sends and receives data messages to each other. In the process of establishing a communication relationship with the MN, the AGR where the CN is located can query the mapping relationship between the AID and the RID of the MN from the mapping server IDMS according to the AID carried in the message of the MN, so as to obtain the routing location identifier RID of the MN; The AGR maintains the AID and RID mapping relationship table (referred to as the mapping table) of the MN locally, and the format is as shown in the following table:

Table 1 Peer Identity Location Identification Mapping Table of Access Gateway Router

AID1 RID1 AID2 RID2 ... ...

When the radio access network detects the mobility of the MN (that is, the location of the MN changes, moving from one AGR coverage area to another AGR, in which case a handover procedure needs to be initiated), the handover procedure is triggered. During the handover process, the switching-out gateway AGR establishes a forwarding relationship with the switching-in gateway AGR. During the switching process or after the switching is completed, the switching-out gateway AGR forwards the data message sent to the The AGR is forwarded to the MN.

In order to avoid the routing circuitous problem after the handover, after the handover is completed, the cut-in gateway notifies all the access gateway routers where the CN is located of the new mapping relationship of the MN. In this way, the access gateway router where the CN is located can directly send subsequent messages to the cut-in gateway of the MN, avoiding roundabout routing.

Therefore, the access gateway router needs to store all CN information for each locally accessed MN, and notify the access gateway router where the CN is located of the new MN identification mapping relationship according to the saved information.

In the specific implementation, firstly, the access gateway router is required to be able to save the records of the communication peers of all locally accessed user terminals (referred to as the peer table), and secondly, all the access gateway routers are required to be able to notify The access router that the communication peer accesses. If the mapping server cannot provide help for forwarding notifications, then the access gateway router must save the information of the access gateway router where the communication peer is located. Table 2 and Table 3 are an organization form of the local access mapping table and the communication peer mapping table saved by the access gateway router in this case.

Table 2 Local access terminal identification mapping table of access gateway router

Table 3 The communication peer identification mapping table of the access gateway router

Peer AID1 Peer RID1 The access gateway router of the access network timer

In Table 2 and Table 3, the record of the communication peer needs to set a timer to decide that if there is no communication with the communication peer for a long time, the record of the communication peer should be deleted to save memory space.

The above solutions mainly have the following problems:

AGR not only needs to maintain the mapping table, but also maintains the peer table for the MN for mobility, which occupies a lot of memory space for the AGR, and requires timers for aging processing, and the system overhead is also very large.

Contents of the invention

In order to solve the above technical problems, the present invention proposes a table maintenance method, system and access gateway router to reduce the occupation of AGR memory space and system overhead.

The present invention proposes a table maintenance method, which method includes:

The access gateway router (AGR) obtains and saves the user type information of the local user equipment (UE);

Obtain the mapping relationship between the AID of the peer UE and the routing identifier (RID) according to the AID of the peer UE; and

The peer table entry is maintained according to the mapping relationship and the saved user type information of the local UE.

Preferably, the above table maintenance method may have the following characteristics:

The AGR acquires and saves the user type information of the local UE including:

The AGR receives the authentication information sent by the local UE, and sends an authentication request to the authentication center according to the authentication information;

The AGR receives the authentication response returned by the authentication center according to the authentication request, and obtains the user type information of the local UE included in the authentication response.

Preferably, the above table maintenance method can also have the following characteristics:

The maintaining the peer table entry according to the mapping relationship and the saved user type information of the local UE includes:

If the saved local UE is a mobile user, generate and save the peer table entry according to the mapping relationship;

If the stored local UE is a fixed user, the peer table entry is not generated.

Preferably, the above table maintenance method can also have the following characteristics:

Obtaining the mapping relationship between the AID of the peer UE and the routing identifier (RID) according to the AID of the peer UE includes:

Receive the service flow sent by the local UE;

sending a query request to the mapping server according to the access identification (AID) of the peer UE in the service flow; and

receiving the mapping relationship between the AID of the peer UE and the routing identifier (RID) returned by the mapping server according to the query request.

Preferably, the above table maintenance method can also have the following characteristics:

Obtaining the mapping relationship between the AID of the peer UE and the routing identifier (RID) according to the AID of the peer UE includes:

Receive the message sent by the peer UE, and decapsulate the message to obtain the AID of the peer UE;

sending a query request to a mapping server according to the AID of the peer UE; and

receiving the mapping relationship between the AID of the peer UE and the routing identifier (RID) returned by the mapping server according to the query request.

The present invention also provides a kind of access gateway route (AGR), and described AGR comprises:

An acquisition module, configured to acquire and store user type information of the local user equipment (UE);

An obtaining module, configured to obtain the mapping relationship between the AID of the peer UE and the routing identifier (RID) according to the AID of the peer UE; and

A maintenance module, configured to maintain the peer table entry according to the mapping relationship and the saved user type information of the local UE.

Preferably, the above-mentioned AGR may have the following characteristics:

The obtaining module is further configured to receive the authentication information sent by the local UE, and send an authentication request to the authentication center according to the authentication information; and receive an authentication response returned by the authentication center according to the authentication request, and obtain the User type information of the local UE in the response.

Preferably, the above-mentioned AGR can also have the following characteristics:

The maintenance module is further configured to generate and save the peer table entry according to the mapping relationship if the saved local UE is a mobile user; if the saved local UE is a fixed user, the peer table entry is not generated. End table entry.

Preferably, the above-mentioned AGR can also have the following characteristics:

The acquisition module includes:

The first receiving unit is configured to receive the service flow sent by the local UE;

A first sending unit, configured to send a query request to the mapping server according to the access identifier (AID) of the peer UE in the service flow; and

The first obtaining unit is configured to receive the mapping relationship between the AID of the peer UE and the routing identifier (RID) returned by the mapping server according to the query request.

Preferably, the above-mentioned AGR can also have the following characteristics:

The acquisition module includes:

The second receiving unit is configured to receive a message sent by the peer UE, and decapsulate the message to obtain the AID of the peer UE;

A second sending unit, configured to send a query request to a mapping server according to the AID of the peer UE; and

The second obtaining unit is configured to receive the mapping relationship between the AID of the peer UE and the routing identifier (RID) returned by the mapping server according to the query request.

The present invention also provides a table maintenance system, the system includes an access gateway router (AGR) and a mapping server, wherein:

The AGR is used to obtain and save the user type information of the local user equipment (UE); send a query request to the mapping server according to the access identification (AID) of the peer UE; receive the peer UE's ID returned by the mapping server A mapping relationship between the AID and the routing identifier (RID); and maintaining the peer table entry according to the mapping relationship and the saved user type information of the local UE;

The mapping server is configured to return the mapping relationship between the AID of the peer UE and the routing identifier (RID) to the AGR according to the query request.

Preferably, the above table maintenance system may have the following characteristics:

The system also includes an authentication center; the AGR is further configured to receive authentication information sent by the local UE, and send an authentication request to the authentication center according to the authentication information; and receive an authentication response returned by the authentication center, and obtain User type information of the local UE included in the authentication response;

The authentication center is configured to return an authentication response to the AGR according to the authentication request.

Preferably, the above table maintenance system can also have the following characteristics:

The AGR is further used to generate and save the peer table entry according to the mapping relationship if the saved local UE is a mobile user; if the saved local UE is a fixed user, the peer table entry is not generated. table entry.

Preferably, the above table maintenance system can also have the following characteristics:

The AGR is further used to receive the service flow sent by the local UE; send a query request to the mapping server according to the access identification (AID) of the peer UE in the service flow; and receive the query request from the mapping server according to the query The request returns the mapping relationship between the AID of the peer UE and the routing identifier (RID).

Preferably, the above table maintenance system can also have the following characteristics:

The AGR is further used to receive a message sent by the peer UE, and decapsulate the message to obtain the AID of the peer UE; send a query request to the mapping server according to the AID of the peer UE; and receive the The mapping server returns the mapping relationship between the AID of the peer UE and the routing identifier (RID) according to the query request.

The above table maintenance method, system and access gateway router can effectively reduce the number of peer table entries maintained by the AGR, reduce equipment costs, and improve table lookup performance.

Description of drawings

FIG. 1 is a schematic diagram of a network topology of a network-based identity and location separation architecture in the prior art;

Fig. 2 is a schematic diagram of relevant interfaces of the network architecture of the network-based identity identification and location separation framework of the present invention;

Fig. 3 is a flow chart of Embodiment 1 of the table maintenance method of the present invention;

FIG. 4 is a signaling flow chart of an embodiment of obtaining and storing user type information in the present invention;

Fig. 5 is a signaling flowchart of the service processing method of the present invention;

6 is a flow chart of Embodiment 2 of the table maintenance method of the present invention;

Fig. 7 is the structural representation of AGR of the present invention;

Fig. 8 is a schematic structural diagram of the meter maintenance system of the present invention.

Detailed ways

The present invention will be described in more detail below in conjunction with the accompanying drawings and embodiments.

Under the network framework shown in Figure 1, the network can be divided into an access network and a backbone network. The access network is located at the edge of the backbone network and is responsible for the access of all terminals. In the RAN part of the access network, all user terminals use AID for addressing. The backbone network is responsible for the routing of terminals accessed through different access networks. There is no overlap between the access network and the backbone network in topology. The application layer between the communication hosts uses the AID to identify the opposite end, and the communication between the user terminals only needs to use the AID of the opposite end.

The access gateway router (AGR) is located at the boundary point between the backbone network and the access network, interfaces with the access network and the backbone network, and is responsible for providing access services for terminals, maintaining user connections, forwarding user data, etc. All communication of the user terminal is forwarded and managed through the access gateway router of the access network where it is located. Data packets between terminals within the service range of the same access gateway router are directly forwarded to the opposite end. The forwarding of data packets between terminals located within the service range of different access gateway routers is as follows: when a terminal sends a data packet, the corresponding access gateway router carries RID information in the forwarded data packet (the RID is the same as the AID). Correspondingly); Correspondingly, when the terminal receives the data message, the access gateway router performs the opposite operation, that is, strips the RID information and forwards the data message to the terminal. The mapping server stores the mapping relationship of identity location identifiers allocated by all user terminals that have accessed the network, and interacts with the access gateway router to resolve the identifier relationship through signaling.

The relevant interfaces of the network architecture of the network-based identity and location separation framework are shown in Figure 2, S1/D1 is the interface between the user terminal and the access gateway router AGR, S1 is used for signaling of user access management, and D1 is Data forwarding interface; S2 is used for handover management signaling when switching between AGRs, D2 is used for data forwarding when switching between AGRs; D3 is the data forwarding interface between AGR and GSR, and S4/S5/S6 is used for querying and maintaining AID - The signaling interface of the RID mapping relationship, D4m is the data forwarding interface between the AGR and the home IDMS (Home IDMS). Among them, when the visited IDMS (visited IDMS) has no direct relationship with the Home IDMS, the relay IDMS (Broke IDMS) forwards the signaling between the visited IDMS and the Home IDMS.

Since the identity network is a fixed-mobile unified packet network, in actual deployment, not every access user is a mobile node. Therefore, if the user type is identified when the user accesses, only the peer table is maintained for the mobile node. It will greatly improve the system performance of AGR.

The present invention provides a table maintenance method, the method comprising:

The access gateway router (AGR) obtains and saves the user type information of the local user equipment (UE);

Obtain the mapping relationship between the AID of the peer UE and the routing identifier (RID) according to the AID of the peer UE; and

The peer table entry is maintained according to the above mapping relationship and the saved user type information of the local UE.

As shown in FIG. 3 , it is a flow chart of Embodiment 1 of the table maintenance method of the present invention. This embodiment is described from the AGR side, and in this embodiment, the UE at the local end is the sending end. The method includes:

Step 301, AGR obtains and saves the user type information of the local user equipment (UE);

User type information can be mobile users and fixed users;

Step 302, sending a query request to the mapping server according to the access identification (AID) of the peer UE in the received service flow;

Step 303, receiving the mapping relationship between the AID of the peer UE and the routing identifier (RID) returned by the above-mentioned mapping server according to the above-mentioned query request;

Step 304: Maintain the peer table entry according to the above mapping relationship and the saved user type information of the local UE.

Among them, the user type information signed by the user is stored in the authentication center. When the UE attaches, the AGR can obtain and save the user type information by interacting with the authentication center. The interaction process can be seen in Figure 4. The process includes:

Step 401, a link layer session is established between the UE and the AGR, such as a point-to-point protocol (PPPoE) session based on Ethernet;

Step 402, an authentication session is initiated between the UE and the AGR, and the UE sends authentication information (such as user name and password) to the AGR;

Step 403, AGR sends an authentication request to the authentication center according to the authentication information sent by the UE;

Step 404: After receiving the UE's authentication request, the authentication center authenticates the user according to the subscription information, and determines the user type of the UE according to the subscription information;

Step 405, the authentication center returns an authentication response to the AGR, and includes UE user type information in the response;

Step 406, the AGR completes the authentication session with the UE, and saves the user type information of the UE locally.

When the UE initiates a service flow, the process of AGR maintaining peer table entries is shown in Figure 5. The process includes:

Step 501, when the UE accesses a certain service, for example, browsing a web page, ordering a video, etc., the generation of a service flow will be triggered;

Step 502, UE sends service flow to AGR;

Step 503, AGR sends a request to the mapping server according to the AID of the peer UE in the service flow, and queries the mapping relationship between the AID and the RID of the peer UE;

Step 504, the mapping server returns the mapping relationship to the AGR;

Step 505, AGR performs outer layer encapsulation on the message according to the mapping relationship, and at the same time, decides whether to generate and save the peer table entry according to the user type of the local UE previously saved.

If the local UE is a mobile user, an entry in the peer table is generated and saved, and if it is a fixed user, no entry in the peer table is generated.

The processing when the local UE receives as a service flow is also similar to the above (that is, the local UE and the peer UE are relative). When the AGR of the local UE receives the message sent by the peer UE, it The outer layer encapsulation forwards the message to the UE. On the other hand, according to the user type of the local UE, it is determined whether to generate and save the peer table entry. The specific process is shown in Figure 6. This embodiment is from the AGR side described, and in this embodiment, the local UE is the receiving end, and the process includes:

Step 601, the access gateway router (AGR) obtains and saves the user type information of the local user equipment (UE);

The implementation process of this step can be seen in Figure 4;

Step 602, receiving the message sent by the peer UE, and decapsulating the above message to obtain the AID of the peer UE;

Step 603, sending a query request to the mapping server according to the AID of the peer UE;

Step 604, receiving the mapping relationship between the AID of the peer UE and the routing identifier (RID) returned by the above-mentioned mapping server according to the above-mentioned query request;

Step 605: Maintain the peer table entry according to the above mapping relationship and the saved user type information of the local UE.

If the saved local UE is a mobile user, then generate and save the above peer table entry according to the above mapping relationship; if the saved local UE is a fixed user, then do not generate the above peer table entry.

To sum up, the method of the present invention can effectively reduce the number of peer table entries maintained by the AGR, reduce equipment costs, and improve table lookup performance.

As shown in Figure 7, it is a schematic structural diagram of the AGR of the present invention, the AGR includes an acquisition module 71, an acquisition module 72 and a maintenance module 74, wherein: the acquisition module is used to acquire and save the user type information of the local user equipment (UE); The obtaining module is used to obtain the mapping relationship between the AID of the peer UE and the routing identifier (RID) according to the AID of the peer UE; the maintenance module is used to pair the peer table entry according to the above mapping relationship and the saved user type information of the local UE for maintenance.

Preferably, the acquisition module may be further configured to receive the authentication information sent by the local UE, and send an authentication request to the authentication center according to the authentication information; and receive an authentication response returned by the authentication center according to the authentication request, and obtain the The user type information of the above-mentioned local UE in . The above maintenance module may be further configured to generate and save the above peer table entry according to the above mapping relationship if the saved local UE is a mobile user; if the saved local UE is a fixed user, then not generate the above peer table entry.

The AGR can effectively maintain the peer table. When the AGR is the sending end, the above-mentioned obtaining module can include: a first receiving unit, used to receive the service flow sent by the local UE; a first sending unit, used to The access identifier (AID) of the peer UE in the flow sends a query request to the mapping server; and the first obtaining unit is configured to receive the AID and routing identifier (RID) of the peer UE returned by the mapping server according to the query request Mapping relations. Its specific implementation can refer to Fig. 3-Fig. 5 . When the AGR is the receiving end, the obtaining module may include: a second receiving unit, configured to receive a message sent by the opposite end UE, and decapsulate the above message to obtain the AID of the opposite end UE; sending a query request to the mapping server according to the AID of the peer UE; and a second obtaining unit configured to receive the mapping relationship between the AID of the peer UE and the routing identifier (RID) returned by the mapping server according to the query request. Its specific implementation can be referred to FIG. 4 and FIG. 6 , which will not be repeated here.

The AGR effectively reduces the number of peer table entries maintained by the AGR through the acquisition module, the interaction between the acquisition module and the maintenance module, reduces equipment costs, and improves table lookup performance.

As shown in FIG. 8 , it is a schematic structural diagram of the table maintenance system of the present invention. The system includes AGR81 and a mapping server 82, wherein: the above-mentioned AGR is used to obtain and save the user type information of the local user equipment (UE); The access identification (AID) of the above-mentioned mapping server sends a query request to the mapping server; receives the mapping relationship between the AID of the peer UE and the routing identification (RID) returned by the above-mentioned mapping server; and according to the above-mentioned mapping relationship and the saved user type information of the local UE Maintaining peer table entries; the above-mentioned mapping server is used to return the mapping relationship between the peer UE's AID and the routing identifier (RID) to the above-mentioned AGR according to the above-mentioned query request.

Preferably, the above-mentioned system may further include an authentication center 83; wherein, the above-mentioned AGR may be further used to receive the authentication information sent by the local UE, and send an authentication request to the above-mentioned authentication center according to the above-mentioned authentication information; and receive an authentication response returned by the authentication center , and acquire the user type information of the local UE included in the authentication response; the authentication center may be used to return an authentication response to the AGR according to the authentication request.

In addition, the above-mentioned AGR can be further used to generate and save the above-mentioned peer table entry according to the above-mentioned mapping relationship if the saved local UE is a mobile user; if the saved local UE is a fixed user, the above-mentioned peer table entry is not generated .

Further, the above-mentioned AGR can be used to receive the service flow sent by the local UE; send a query request to the mapping server according to the access identifier (AID) of the peer UE in the above-mentioned service flow; and receive the query request returned by the above-mentioned mapping server according to the above-mentioned query request. The mapping relationship between the AID of the peer UE and the routing identifier (RID). The above-mentioned AGR can also be used to receive a message sent by the peer UE, and decapsulate the above-mentioned message to obtain the AID of the peer UE; send a query request to the mapping server according to the AID of the peer UE; and receive the mapping server according to the above-mentioned Query the mapping relationship between the peer UE's AID and the routing identifier (RID) returned by the query request.

Through the interaction between AGR, mapping server and authentication center, the system can effectively reduce the number of peer table entries maintained by AGR, reduce equipment costs, and improve table lookup performance.

Those skilled in the art can understand that all or part of the steps in the above method can be completed by instructing related hardware through a program, and the above program can be stored in a computer-readable storage medium, such as a read-only memory, a magnetic disk or an optical disk, and the like. Optionally, all or part of the steps in the foregoing embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the foregoing embodiments may be implemented in the form of hardware, or may be implemented in the form of software function modules. The present invention is not limited to any specific combination of hardware and software.

The above embodiments are only used to illustrate the technical solutions of the present invention rather than limit them, and the present invention is described in detail with reference to preferred embodiments. Those skilled in the art should understand that the technical solutions of the present invention can be modified or equivalently replaced without departing from the spirit and scope of the technical solutions of the present invention, and all should be covered by the claims of the present invention.

Claims (12)

1. A table maintenance method, characterized in that the method comprises: The access gateway router AGR obtains and saves the user type information of the local user equipment UE; Obtain the mapping relationship between the AID of the peer UE and the routing identifier RID according to the access identifier AID of the peer UE; and Maintaining the peer table entry according to the mapping relationship and the saved user type information of the local UE; The maintaining the peer table entry according to the mapping relationship and the saved user type information of the local UE includes: If the saved local UE is a mobile user, generate and save the peer table entry according to the mapping relationship; If the stored local UE is a fixed user, the peer table entry is not generated. 2. The table maintenance method according to claim 1, wherein the AGR obtaining and saving the user type information of the local UE comprises: The AGR receives the authentication information sent by the local UE, and sends an authentication request to the authentication center according to the authentication information; and The AGR receives the authentication response returned by the authentication center according to the authentication request, and acquires the user type information of the local UE included in the authentication response. 3. The table maintenance method according to any one of claims 1-2, wherein said obtaining the mapping relationship between the AID of the peer UE and the routing identifier RID according to the AID of the peer UE comprises: Receive the service flow sent by the local UE; sending a query request to the mapping server according to the access identifier AID of the peer UE in the service flow; and receiving the mapping relationship between the AID of the peer UE and the routing identifier RID returned by the mapping server according to the query request. 4. The table maintenance method according to any one of claims 1-2, wherein said obtaining the mapping relationship between the AID of the peer UE and the routing identifier RID according to the AID of the peer UE comprises: Receive the message sent by the peer UE, and decapsulate the message to obtain the AID of the peer UE; sending a query request to a mapping server according to the AID of the peer UE; and receiving the mapping relationship between the AID of the peer UE and the routing identifier RID returned by the mapping server according to the query request. 5. A kind of access gateway routing AGR, it is characterized in that, described AGR comprises: An acquisition module, configured to acquire and save user type information of the local user equipment UE; An obtaining module, configured to obtain the mapping relationship between the AID of the peer UE and the routing identifier RID according to the access identifier AID of the peer UE; and A maintenance module, configured to maintain the peer table entry according to the mapping relationship and the saved user type information of the local UE; The maintenance module is further configured to generate and save the peer table entry according to the mapping relationship if the saved local UE is a mobile user; if the saved local UE is a fixed user, the peer table entry is not generated. End table entry. 6. AGR according to claim 5, characterized in that: The obtaining module is further configured to receive the authentication information sent by the local UE, and send an authentication request to the authentication center according to the authentication information; and receive an authentication response returned by the authentication center according to the authentication request, and obtain the User type information of the local UE in the response. 7. The AGR according to any one of claims 5-6, wherein the obtaining module comprises: The first receiving unit is configured to receive the service flow sent by the local UE; A first sending unit, configured to send a query request to the mapping server according to the access identifier AID of the peer UE in the service flow; and The first obtaining unit is configured to receive the mapping relationship between the AID of the peer UE and the routing identifier RID returned by the mapping server according to the query request. 8. The AGR according to any one of claims 5-6, wherein the obtaining module comprises: The second receiving unit is configured to receive a message sent by the peer UE, and decapsulate the message to obtain the AID of the peer UE; A second sending unit, configured to send a query request to a mapping server according to the AID of the peer UE; and The second obtaining unit is configured to receive the mapping relationship between the AID of the peer UE and the routing identifier RID returned by the mapping server according to the query request. 9. A table maintenance system, characterized in that the system includes an access gateway router AGR and a mapping server, wherein: The AGR is used to obtain and save the user type information of the UE at the local end; send a query request to the mapping server according to the access identifier AID of the peer UE; receive the AID and routing identifier of the peer UE returned by the mapping server The mapping relationship of the RID; and maintaining the peer table entry according to the mapping relationship and the saved user type information of the local UE; The mapping server is configured to return the mapping relationship between the AID of the peer UE and the routing identifier RID to the AGR according to the query request; The AGR is further used to generate and save the peer table entry according to the mapping relationship if the saved local UE is a mobile user; if the saved local UE is a fixed user, the peer table entry is not generated. table entry. 10. The table maintenance system according to claim 9, wherein the system further comprises an authentication center; The AGR is further configured to receive authentication information sent by the local UE, and send an authentication request to the authentication center according to the authentication information; and receive an authentication response returned by the authentication center, and obtain the authentication information included in the authentication response User type information of the local UE; The authentication center is configured to return an authentication response to the AGR according to the authentication request. 11. The watch maintenance system according to any one of claims 9-10, characterized in that: The AGR is further configured to receive the service flow sent by the UE at the local end; send a query request to the mapping server according to the access identifier AID of the peer UE in the service flow; and receive the query request returned by the mapping server according to the query request The mapping relationship between the AID of the peer UE and the routing identifier RID. 12. The watch maintenance system according to any one of claims 9-10, characterized in that: The AGR is further used to receive a message sent by the peer UE, and decapsulate the message to obtain the AID of the peer UE; send a query request to the mapping server according to the AID of the peer UE; and receive the The mapping server returns the mapping relationship between the AID of the peer UE and the routing identifier RID according to the query request.