WO2012088828A1 - 表维护方法、系统和接入网关路由器 - Google Patents

表维护方法、系统和接入网关路由器 Download PDF

Info

Publication number
WO2012088828A1
WO2012088828A1 PCT/CN2011/074627 CN2011074627W WO2012088828A1 WO 2012088828 A1 WO2012088828 A1 WO 2012088828A1 CN 2011074627 W CN2011074627 W CN 2011074627W WO 2012088828 A1 WO2012088828 A1 WO 2012088828A1
Authority
WO
WIPO (PCT)
Prior art keywords
peer
aid
agr
local
mapping
Prior art date
Application number
PCT/CN2011/074627
Other languages
English (en)
French (fr)
Inventor
孙默
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2012088828A1 publication Critical patent/WO2012088828A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W40/00Communication routing or communication path finding

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a table maintenance method, system, and access gateway router.
  • the IP address in the Transmission Control Protocol/Internet Protocol which is widely used in the Internet, has a dual function, and serves as the location identifier of the communication terminal host network interface of the network layer in the network topology. And as the identity of the transport layer host network interface.
  • the TCP/IP protocol was not designed with host mobility in mind. However, as host mobility becomes more prevalent, the semantic overload defects of such IP addresses are becoming increasingly apparent.
  • the IP address of the host changes, not only the route changes, but also the identity of the communication terminal host changes. This will cause the routing load to become heavier and heavy, and the change of the host identity will also cause the application and connection to be interrupted.
  • the purpose of identification and location separation is to solve the problem of semantic overload and severe routing load of IP addresses, and to separate the dual functions of IP addresses to achieve dynamic redistribution of mobility, multiple townships, IP addresses, and mitigation of routes. Support for issues such as load and mutual visits between different network areas in the next generation Internet.
  • an identification network a network-based identity identification and location separation scheme
  • the basic idea of this scheme is: dividing the network into an access layer and a core layer, and a mobile node in the network.
  • AID Access Identifier
  • RID Routing-Location Identifier
  • the topology diagram of the foregoing network-based identity identification and location separation framework is as shown in FIG. 1.
  • the method mainly includes: a radio access network (RAN) 11, Access Gateway Router (AGR) 12, General Switch Router (GSR) 13, Identifier Mapping Server (IDMS) 14, and Authentication Center 15;
  • RAN radio access network
  • AGR Access Gateway Router
  • GSR General Switch Router
  • IDMS Identifier Mapping Server
  • AGR which is responsible for providing access services for various mobile nodes, assigning RIDs to the connected users, and
  • the AGR queries the AID-RID mapping table in the local cache (CACHE) according to the destination address (ie, the AID of the communication peer) in the data packet: If the corresponding AID-RID mapping is found The entry, the RID of the communication terminal that is found is encapsulated in the packet header and sent to the backbone network for forwarding processing; if the corresponding AID-RID mapping entry is not found, the data packet is forwarded to the backbone network, and to the IDMS The process of initiating the AID-RID mapping information of the query (communication peer), and storing the mapping of the AIDc-RIDc returned by the IDMS to the local, for the subsequent packet forwarding.
  • the AGR may choose not to forward the data packet to the backbone network, but initiate the process of querying the AID-RID mapping information (communicating the peer end) to the IDMS, waiting for the IDMS. After returning the corresponding AIDc-RIDc mapping, the RID of the communication terminal that is found is encapsulated in the packet header and sent to the backbone network for forwarding processing.
  • the AGR decapsulates the data packet, and strips the newly added RID packet header from the data packet to the terminal.
  • the main function of the GSR is to select and forward data packets based on the routing location identifier RID in the data packet.
  • IDMS is mainly responsible for maintaining the mapping between user identity and location identity 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 legalizes and authorizes users when they access them.
  • the Certification Authority supports two-way authentication between the network and the user.
  • the radio access network is responsible for providing and maintaining a Layer 2 link between the user terminal and the access gateway router AGR; and is responsible for radio resource management in the cellular mobile network application scenario.
  • a communication node Correspondent Node, CN
  • a mobile node Mobile Node, MN
  • the AGR of the CN can query the mapping server IDMS for the mapping relationship between the AID and the RID of the MN according to the AID carried in the message of the MN.
  • the MN's routing location identifier RID is obtained.
  • the AGR of the CN maintains the MN's AID and RID mapping relationship table (referred to as the mapping table).
  • Table 1 The format is shown in Table 1:
  • the radio access network detects the mobility of the MN (i.e., the location of the MN has changed, moving from one AGR coverage to another, in which case the handover procedure needs to be initiated), the handover procedure is triggered.
  • the gateway AGR and the ingress gateway AGR establish a forwarding relationship. After the handover or the handover is completed, the gateway AGR forwards the received data packet to the MN to the gateway AGR. The AGR is forwarded to the MN.
  • the new mapping relationship of the MN is notified by the handover gateway to all access gateway routers where the CN is located. In this way, the access gateway router where the CN is located can directly send subsequent packets to the MN's hand-in gateway, thereby avoiding route bypass.
  • the access gateway router it is necessary for the access gateway router to save all CN information for each locally accessed MN, and notify the access gateway router where the CN is located according to the saved information.
  • the access gateway router is first required to save the records of the communication peers of all locally accessed user terminals (referred to as the peer table), and secondly, all access gateway routers can be notified by the help of the mapping server alone or with the help of the mapping server.
  • Table 2 and Table 3 are an organization form of the local access mapping table and the communication peer mapping table held by the access gateway router in this case.
  • the communication peer record also 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.
  • AGR maintains the mapping table. For mobility, it also maintains the peer table for the MN. This has a large memory footprint for the AGR, and the performance requires a timer for aging processing, and the system overhead is also large. Summary of the invention
  • the present invention provides a table maintenance method, system, and access gateway router to reduce the occupation of the AGR memory space and reduce system overhead.
  • the invention provides a table maintenance method, the method comprising:
  • the access gateway router acquires and stores user type information of the local user equipment (UE);
  • the mapping relationship between the AID of the opposite UE and the route identifier (RID) is obtained;
  • the peer table entry is maintained according to the mapping relationship and the saved user type information of the local UE.
  • the above table maintenance method has 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 performs authentication according to the authentication information.
  • Heart sends an authentication request;
  • the AGR receiving authentication center obtains the user type information of the local UE included in the authentication response according to the authentication response returned by the authentication request.
  • the above table maintenance method may 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:
  • the peer table entry is generated and saved according to the mapping relationship.
  • maintaining the peer table entry according to the mapping relationship and the saved user type information of the local UE includes:
  • the peer table entry is not generated.
  • the above table maintenance method may also have the following characteristics:
  • the mapping relationship between the AID of the opposite UE and the route identifier (RID) obtained according to the AID of the peer UE includes:
  • mapping server And sending a query request to the mapping server according to the access identifier (AID) of the peer UE in the service flow; and receiving a mapping between the AID and the route identifier (RID) of the peer UE returned by the mapping server according to the query request relationship.
  • AID access identifier
  • RID route identifier
  • the above table maintenance method may also have the following characteristics:
  • the mapping relationship between the AID of the opposite UE and the route identifier (RID) obtained according to the AID of the peer UE includes:
  • mapping server And receiving, by the mapping server, a mapping relationship between the AID of the opposite UE and the route identifier (RID) returned according to the query request.
  • RID route identifier
  • the invention also provides an access gateway route (AGR), the AGR comprising: An acquisition module, configured to: obtain and save user type information of a local user equipment (UE); and obtain an module, where: the method is: obtaining an AID and a route identifier (RID) of the peer UE according to the AID of the peer UE Mapping relationship;
  • AGR access gateway route
  • the maintenance module is configured to: maintain the peer table entry according to the mapping relationship and the saved user type information of the local UE.
  • the above AGR can have the following characteristics:
  • the obtaining module is 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 according to the authentication request, and obtain the authentication included in the authentication User type information of the local UE in response.
  • the above AGR may also have the following characteristics:
  • the maintenance module is configured to: if the saved local UE is a mobile user, generate and save the peer table entry according to the mapping relationship.
  • the maintenance module is configured to: if the saved local UE is a fixed user, the peer table entry is not generated.
  • the above AGR may also have the following characteristics:
  • the obtaining module includes:
  • a first receiving unit configured to: receive a service flow sent by the local UE; the first sending unit is configured to: send a query request to the mapping server according to an access identifier (AID) of the peer UE in the service flow ; as well as
  • AID access identifier
  • a first obtaining unit configured to: receive a mapping relationship between the AID of the correspondent UE and the route identifier (RID) returned by the mapping server according to the query request.
  • RID route identifier
  • the above AGR may also have the following characteristics:
  • the obtaining module includes:
  • a second receiving unit configured to: receive a packet sent by the peer UE, and decapsulate the packet to obtain an AID of the peer UE;
  • a second sending unit configured to: send a query request to the mapping server according to the AID of the peer UE; and And a second obtaining unit, configured to: receive a mapping relationship between the AID of the opposite UE and the route identifier (RID) returned by the mapping server according to the query request.
  • RID route identifier
  • the present invention also provides a table maintenance system, the system comprising an access gateway router (AGR), wherein:
  • the AGR is set to: acquire and save user type information of the local user equipment (UE); and, according to the mapping relationship between the AID and the route identifier (RID) of the peer UE, and the saved user type information of the local UE, Table entries are maintained.
  • the system further includes a mapping server,
  • the AGR is further configured to: send a query request to the mapping server according to the access identifier (AID) of the peer UE; and receive a mapping relationship between the AID of the opposite UE and the route identifier (RID) returned by the mapping server;
  • AID access identifier
  • RID route identifier
  • the mapping server is configured to: return a mapping relationship between the AID of the opposite UE and the route identifier (RID) to the AGR according to the query request.
  • RID route identifier
  • the above table maintenance system can have the following characteristics:
  • the system further includes: an authentication center; the AGR is 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.
  • the above table maintenance system may also have the following characteristics:
  • the AGR is further configured to: if the saved local UE is a mobile user, generate and save the peer table entry according to the mapping relationship.
  • the AGR is further configured to:
  • the peer table entry is not generated.
  • the above table maintenance system may also have the following characteristics:
  • the AGR is configured to: receive a service flow sent by the local UE; send a query request to the mapping server according to an access identifier (AID) of the peer UE in the service flow; and receive the mapping The mapping relationship between the AID of the peer UE and the route identifier (RID) returned by the server according to the query request.
  • AID access identifier
  • RID route identifier
  • the above table maintenance system may also have the following characteristics:
  • the AGR is configured to: receive a packet sent by the peer UE, and decapsulate the packet to obtain an 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 relationship between the AID of the peer UE and the route identifier (RID) returned by the mapping server according to the query request.
  • RID route identifier
  • the AGR includes:
  • An obtaining module configured to: obtain and save user type information of the local UE;
  • Obtaining a module configured to: obtain a mapping relationship between an AID of a peer UE and a route identifier (RID) according to an AID of the peer UE;
  • RID route identifier
  • the maintenance module is configured to: 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 AGR, reduce equipment costs, and improve table lookup performance.
  • FIG. 1 is a schematic diagram of a network topology of a prior art network-based identity and location separation architecture
  • FIG. 2 is a schematic diagram of related interfaces of a network architecture of a network-based identity identification and location separation framework according to the present invention
  • Embodiment 3 is a flowchart of Embodiment 1 of a table maintenance method according to the present invention.
  • FIG. 4 is a signaling flowchart of an embodiment of acquiring and saving user type information according to the present invention.
  • FIG. 5 is a signaling flowchart of a service processing method according to the present invention.
  • Embodiment 6 is a flowchart of Embodiment 2 of a table maintenance method according to the present invention.
  • Figure 7 is a schematic structural view of an AGR of the present invention
  • Figure 8 is a schematic view showing the structure of the watch maintenance system of the present invention. Preferred embodiment of the invention
  • 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 access by all terminals.
  • all user terminals are addressed by AID.
  • the backbone network is responsible for routing of terminals accessed through different access networks.
  • the access network and the backbone network do not overlap in the topology relationship.
  • the application layer between the communication hosts uses the AID to identify the peer.
  • the communication between the user terminals only needs to use the AID of the peer.
  • the access gateway router (AGR) is located at the demarcation point between the backbone network and the access network, and interfaces with the access network and the backbone network to provide access services for the terminal, maintain user connections, and forward user data. All communication of the user terminal is forwarded and managed by the access gateway router of the access network. Data packets between terminals in the service range of the same access gateway are directly forwarded to the peer.
  • the forwarding of data packets between terminals in the service range of different access gateway routers is as follows:
  • the corresponding access gateway router carries the RID information in the forwarded data packet (the RID and the AID are
  • the access gateway router performs the opposite operation, that is, stripping the RID information and forwarding the data packet to the terminal.
  • the mapping server stores the identity location identifier mapping relationship assigned by all the user terminals that have been accessed in the network, and performs identification relationship analysis with the access gateway router through signaling interaction.
  • S1/D1 is an interface between the user terminal and the access gateway router AGR, and S1 is used for signaling of user access management, and D1 is Data forwarding interface
  • S2 is used for switching management signaling when switching between AGRs
  • D2 is used for data forwarding between AGRs
  • D3 is a data forwarding interface between AGR and GSR
  • S4/S5/S6 is used for querying and maintaining AIDs.
  • D4m is the data forwarding interface between the AGR and the home IDMS (Home IDMS).
  • the IDMS (Broke IDMS) forwards the signaling between the visited IDMS and the Home IDMS when the visited IDMS (destination IDMS) has no direct connection with the Home IDMS.
  • the identification 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 mobile node maintains the peer table, which will greatly improve the system performance of AGR.
  • the invention provides a table maintenance method, the method comprising:
  • the access gateway router acquires and stores user type information of the local user equipment (UE);
  • the mapping relationship between the AID of the opposite UE and the route identifier (RID) is obtained;
  • the peer table entry is maintained according to the above mapping relationship and the saved user type information of the local UE.
  • FIG. 3 it is a flowchart of Embodiment 1 of the table maintenance method of the present invention.
  • the embodiment is described from the AGR side, and in this embodiment, the local UE is a sender, and the method includes:
  • Step 301 The AGR obtains and saves the user type information of the local user equipment (UE); the user type information may be a mobile user or a fixed user;
  • UE local user equipment
  • Step 302 Send a query request to the mapping server according to the access identifier (AID) of the peer UE in the received service flow.
  • Step 303 Receive a mapping relationship between an AID and a route identifier (RID) of the peer UE that is returned by the mapping server according to the query request.
  • RID route identifier
  • Step 304 Maintain the peer table entry according to the mapping relationship and the saved user type information of the local UE.
  • the user type information of the user subscription is stored in the authentication center.
  • the AGR can obtain and save the user type information by interacting with the authentication center.
  • the interaction process can be seen in FIG. 4, and the process includes:
  • Step 401 Establish a link layer session between the UE and the AGR, such as an Ethernet-based Point-to-Point Protocol (PPPoE) session;
  • PPPoE Point-to-Point Protocol
  • Step 402 The UE initiates an authentication session with the AGR, and the UE sends the authentication information (such as the username and password) to the AGR.
  • the authentication information such as the username and password
  • Step 403 The AGR sends an authentication request to the authentication center according to the authentication information sent by the UE.
  • Step 405 The authentication center returns an authentication response to the AGR, and includes user type information of the UE in the response.
  • Step 406 The AGR completes an authentication session with the UE, and locally saves the user type information of the UE.
  • the process of maintaining the peer table entry by the AGR is as shown in FIG. 5, and the process includes:
  • Step 501 When the UE accesses a certain service, for example, browsing a webpage, an on-demand video, or the like, triggering the generation of the service flow;
  • Step 502 The UE sends a service flow to the AGR.
  • Step 503 The 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 The AGR encapsulates the packet according to the mapping relationship, and determines whether the peer table entry needs to be generated and saved according to the user type of the local UE saved in the foregoing.
  • the peer table entry is generated and saved, and if it is a fixed user, the peer table entry is not generated.
  • Step 601 The access gateway router (AGR) acquires and saves user type information of the local user equipment (UE);
  • Step 602 Receive a packet sent by the peer UE, and decapsulate the packet to obtain an AID of the peer UE.
  • Step 603 Send a query request to the mapping server according to the AID of the peer UE.
  • Step 604 Receive a mapping relationship between the AID of the peer UE and the route identifier (RID) returned by the mapping server according to the query request.
  • RID route identifier
  • Step 605 Maintain the peer table entry according to the foregoing mapping relationship and the saved user type information of the local UE. If the saved local UE is a mobile user, the peer table entry is generated and saved according to the mapping relationship; if the saved local UE is a fixed user, the peer table entry is not generated.
  • the method of the present invention can effectively reduce the number of peer table entries maintained by AGR, reduce equipment costs, and improve table lookup performance.
  • the AGR includes an obtaining module 71, an obtaining module 72, and a maintenance module 73.
  • the acquiring module 71 is configured to acquire and save user type information of the local user equipment (UE).
  • the obtaining module 72 is configured to obtain a mapping relationship between the AID of the peer UE and the route identifier (RID) according to the AID of the peer UE, and the maintenance module 73 is configured to perform pairing according to the foregoing mapping relationship and the saved user type information of the local UE. End table entries are maintained.
  • the acquiring 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 foregoing authentication information; and receive the authentication response returned by the authentication center according to the authentication request, and obtain the authentication response included in the authentication response.
  • User type information of the above local UE in the middle may be further configured to: if the saved local UE is a mobile user, generate and save the peer table entry according to the mapping relationship; if the saved local UE is a fixed user, the peer table entry is not generated.
  • the AGR can effectively maintain the peer table.
  • the obtaining module may include: a first receiving unit, configured to receive a service flow sent by the local UE, and a first sending unit, configured to use the foregoing service
  • the access identifier (AID) of the peer UE in the stream sends a query request to the mapping server; and the first obtaining unit is configured to receive the AID and the route identifier (RID) of the peer UE returned by the mapping server according to the query request.
  • mapping relations The specific implementation can be seen in Figure 3-5.
  • the obtaining module may include: a second receiving unit, configured to receive a packet sent by the peer UE, and decapsulate the packet to obtain an AID of the peer UE; Sending a query request to the mapping server according to the AID of the peer UE; and And a second obtaining unit, configured to receive a mapping relationship between the AID of the opposite UE and the route identifier (RID) returned by the mapping server according to the foregoing query request.
  • a second receiving unit configured to receive a packet sent by the peer UE, and decapsulate the packet to obtain an AID of the peer UE; Sending a query request to the mapping server according to the AID of the peer UE; and And a second obtaining unit, configured to receive a mapping relationship between the AID of the opposite UE and the route identifier (RID) returned by the mapping server according to the foregoing query request.
  • RID route identifier
  • the AGR effectively reduces the number of peer table entries maintained by the AGR by acquiring modules, obtaining modules, and maintaining module interactions, reducing device costs and improving table lookup performance.
  • FIG. 8 it is a schematic structural diagram of a table maintenance system according to the present invention.
  • the system includes an AGR 81 and a mapping server 82, where: the AGR is used to obtain and save user type information of the local user equipment (UE );
  • the access identifier (AID) sends a query request to the mapping server; receives the mapping relationship between the AID and the route identifier (RID) of the peer UE returned by the mapping server; and the user type information of the local UE according to the mapping relationship and the saved
  • the mapping between the AID and the route identifier (RID) of the peer UE is returned to the AGR according to the foregoing query request.
  • the system may further include an authentication center 83.
  • the AGR may be 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 acquiring the user type information of the local UE included in the foregoing authentication response; the foregoing authentication center may be configured to return an authentication response to the AGR according to the foregoing authentication request.
  • the AGR may be further configured to: if the saved local UE is a mobile user, generate and save the peer table entry according to the mapping relationship; if the saved local UE is a fixed user, the peer table entry is not generated. .
  • the AGR may be used to receive a 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 service flow; and receive the mapping server to return according to the query request.
  • the foregoing AGR may be further configured to: receive a packet sent by the peer UE, and decapsulate the packet to obtain an 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 foregoing. Query the mapping between the AID of the peer UE and the route identifier (RID) returned by the query.
  • the system can effectively reduce the number of peer table entries maintained by AGR, reduce equipment costs, and improve table lookup performance.
  • AGR peer table entries maintained by AGR
  • all or a portion of the above steps may be accomplished by a program that instructs the associated hardware, such as a read-only memory, a magnetic disk, or an optical disk.
  • all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits.
  • each module/unit in the foregoing embodiment may be implemented in the form of hardware, or may be implemented in the form of a software function module. The invention is not limited to any specific form of combination of hardware and software.
  • the number of peer table entries maintained by AGR reduces equipment costs and improves table lookup performance.

Abstract

本发明提供了一种表维护方法、系统和接入网关路由器。其中,表维护方法包括:接入网关路由器(AGR)获取并保存本端用户设备(UE)的用户类型信息;根据对端UE的AID获得对端UE的AID和路由标识(RID)的映射关系;以及根据所述映射关系和保存的本端UE的用户类型信息对对端表条目进行维护。上述表维护方法、系统和接入网关路由器,可以有效地减少AGR维护的对端表条目的数量,降低设备成本,提高查表性能。

Description

表维护方法、 系统和接入网关路由器
技术领域
本发明涉及通信技术领域, 尤其涉及一种表维护方法、 系统和接入网关 路由器。
背景技术
现有因特网广泛使用的传输控制协议 /互联网络协议 ( Transmission Control Protocol/Internet Protocol, TCP/IP ) 中 IP地址具有双重功能, 既作为 网络层的通信终端主机网络接口在网络拓朴中的位置标识, 又作为传输层主 机网络接口的身份标识。 TCP/IP协议在设计之初并未考虑主机移动的情况。 但是, 当主机移动越来越普遍时, 这种 IP地址的语义过载缺陷日益明显。 当 主机的 IP地址发生变化时, 不仅路由发生变化, 通信终端主机的身份标识也 发生变化, 这样将会导致路由负载越来越重, 而且主机标识的变化还将导致 应用和连接的中断。
身份标识和位置分离问题提出的目的是为了解决 IP地址的语义过载和路 由负载严重等问题, 将 IP地址的双重功能进行分离, 实现对移动性、 多家乡 性、 IP地址动态重分配、 减轻路由负载及下一代互联网中不同网络区域之间 的互访等问题的支持。
在现有技术中, 提出了一种基于网络的身份标识和位置分离方案 (后面 简称标识网) , 这种方案的基本思想是: 将网络划分为接入层和核心层, 网 络中的移动节点有两种标识类型:用户身份标识(Access Identifier,简称 AID ) 和路由位置标识(Routing-Location Identifier, 简称 RID ) 。 为网络中的每个 用户配置唯一的 AID, 该 AID在移动过程中始终保持不变; 在数据转发过程 中, AID只能在接入层使用, RID只能在核心层使用; 在用户终端间应用层 通信时, 使用 AID识别对端。
上述基于网络的身份标识和位置分离框架的拓朴示意图如图 1所示, 在 该基于网络的身份标识和位置分离框架中, 主要包括: 无线接入网 (RAN)11、 接入网关路由器(Access Gateway Router, 简称 AGR ) 12、 广义网关路由器 ( General Switch Router,简称 GSR )13、映射服务器( Identifier Mapping Server, 简称 IDMS ) 14和认证中心 15等; 其中:
AGR, 负责为各种移动节点提供接入服务, 为接入的用户分配 RID, 并
AGR在收到终端发来的数据报文时, 根据数据报文中目的地址 (即通信 对端的 AID )查询本地緩存 ( CACHE )中的 AID-RID映射表: 如果查到对应 的 AID-RID映射条目,则将查到的通信终端的 RID封装在报文头部发送到骨 干网进行转发处理; 如果没有查到对应的 AID-RID映射条目, 则将数据报文 转发到骨干网, 并向 IDMS发起查询 (通信对端的 ) AID-RID映射信息的流 程 , 并将 IDMS返回对应的 AIDc-RIDc映射保存在本地 , 以备后续报文转发 时查询。
或者, AGR在没有查到对应的 AID-RID映射条目时,也可以选择不将数 据报文转发到骨干网, 而是向 IDMS发起查询 (通信对端的 ) AID-RID映射 信息的流程, 待 IDMS返回对应的 AIDc-RIDc映射后, 将查到的通信终端的 RID封装在报文头部发送到骨干网进行转发处理。
AGR在收到发往终端的数据报文时, 对数据报文进行解封装处理, 剥去 数据报文中新增的包含 RID的报文头, 发往终端。
GSR的主要功能是根据数据报文中的路由位置标识 RID进行选路和转发 数据报文。
IDMS 主要负责维护网络中用户身份标识和位置标识的映射关系, 并向 接入网关路由器和其它映射服务器提供查询服务。
认证中心, 负责记录用户类别、 用户服务等级等信息, 在用户接入时对 用户进行合法性认证和授权。 认证中心支持网络与用户间的双向鉴权。
无线接入网,负责提供并维护用户终端到接入网关路由器 AGR之间的二 层链路; 在蜂窝移动网应用场景中负责无线资源管理。
下面描述在上述网络架构下实现移动性支持的切换管理的方法, 移动节 点的通信对端 ( Correspondent Node , 简称 CN )与移动节点 ( Mobile Node , 简称 MN )建立通信, 相互间收发数据报文, 在与 MN建立通信关系的过程 中, CN所在的 AGR可以根据 MN的消息中携带的 AID ,向映射服务器 IDMS 查询 MN的 AID和 RID的映射关系,从而得到 MN的路由位置标识 RID; 同 时 CN所在的 AGR在本地维护 MN的 AID和 RID映射关系表(简称映射表), 格式如表 1所示:
表 1 接入网关路由器的对端身份位置标识映射表
Figure imgf000004_0001
当无线接入网检测到 MN的移动性(即 MN的位置发生了变化, 从一个 AGR覆盖范围移动到了另一个 AGR, 在这种情况下需要发起切换流程)后, 触发切换流程。 在切换过程中, 切出网关 AGR与切入网关 AGR建立转发关 系,在切换过程中或切换完成后,切出网关 AGR将收到的发往 MN的数据报 文转发给切入网关 AGR, 由切入网关 AGR转发给 MN。
为了避免切换后的路由迂回问题, 在切换完成后, 由切入网关将 MN的 新映射关系通知所有 CN所在的接入网关路由器。 这样, CN所在的接入网关 路由器就可以将后续的报文直接发送给 MN的切入网关, 避免了路由迂回。
因此, 就需要在接入网关路由器为每个本地接入的 MN保存所有的 CN 的信息, 根据保存的信息, 将 MN新的标识映射关系通知给 CN所在的接入 网关路由器。
在具体实施中, 首先要求接入网关路由器能够保存所有本地接入的用户 终端的通信对端的记录(简称对端表) , 其次要求所有的接入网关路由器单 独或者在映射服务器的帮助下能通知通信对端接入的接入路由器。 如果映射 服务器不能提供转发通知的帮助, 那么接入网关路由器就必须保存通信对端 所在的接入网关路由器的信息。 表 2和表 3是在这种情况下接入网关路由器 保存的本地接入映射表和通信对端映射表的一种组织形式。 接入网关路由器的本地接入终端标识映射表
Figure imgf000005_0001
接入网关路由器的通信对端标识映射表
Figure imgf000005_0002
在表 2和表 3中, 通信对端的记录还需要设置定时器, 来决定如果很长 时间没有和这个通信对端通信了就应该删除这个通信对端的记录, 以节省内 存空间。
以上解决方案主要存在以下问题:
AGR既要维护映射表, 为了移动性,也要为 MN维护对端表,这对 AGR 的内存空间占用很大, 而且表现需要定时器来进行老化处理, 系统开销也很 大。 发明内容
为了解决上述技术问题, 本发明提出了一种表维护方法、 系统和接入网 关路由器, 以减少对 AGR内存空间的占用, 降低系统开销。
本发明提出了一种表维护方法, 该方法包括:
接入网关路由器(AGR )获取并保存本端用户设备 ( UE )的用户类型信 息;
才艮据对端 UE的 AID获得对端 UE的 AID和路由标识 ( RID ) 的映射关 系; 以及
根据所述映射关系和保存的本端 UE的用户类型信息对对端表条目进行 维护。
优选地, 上述表维护方法可具有如下特点:
所述 AGR获取并保存本端 UE的用户类型信息包括:
所述 AGR接收本端 UE发送的认证信息,并根据所述认证信息向认证中 心发送认证请求;
所述 AGR接收认证中心根据所述认证请求返回的认证应答,获取包含在 所述认证应答中的所述本端 UE的用户类型信息。
优选地, 上述表维护方法还可具有如下特点:
所述根据所述映射关系和保存的本端 UE的用户类型信息对对端表条目 进行维护包括:
若保存的本端 UE为移动用户, 则根据所述映射关系生成并保存所述对 端表条目。
优选地, 所述根据所述映射关系和保存的本端 UE的用户类型信息对对 端表条目进行维护包括:
若保存的本端 UE为固定用户, 则不生成所述对端表条目。
优选地, 上述表维护方法还可具有如下特点:
所述根据对端 UE的 AID获得对端 UE的 AID和路由标识 ( RID ) 的映 射关系包括:
接收本端 UE发送的业务流;
根据所述业务流中的对端 UE的接入标识( AID )向映射服务器发送查询 请求; 以及 接收所述映射服务器根据所述查询请求返回的对端 UE的 AID和路由标 识(RID ) 的映射关系。
优选地, 上述表维护方法还可具有如下特点:
所述根据对端 UE的 AID获得对端 UE的 AID和路由标识 ( RID ) 的映 射关系包括:
接收对端 UE发送的报文, 并对所述报文解封装获得对端 UE的 AID; 根据所述对端 UE的 AID向映射服务器发送查询请求; 以及
接收所述映射服务器根据所述查询请求返回的对端 UE的 AID和路由标 识(RID ) 的映射关系。
本发明还提供了一种接入网关路由 (AGR ) , 所述 AGR包括: 获取模块, 其设置为: 获取并保存本端用户设备(UE )的用户类型信息; 获得模块, 其设置为: 根据所述对端 UE的 AID获得对端 UE的 AID和 路由标识(RID ) 的映射关系; 以及
维护模块, 其设置为: 根据所述映射关系和保存的本端 UE的用户类型 信息对对端表条目进行维护。
优选地, 上述 AGR可具有如下特点:
所述获取模块是设置为: 接收本端 UE发送的认证信息, 并根据所述认 证信息向认证中心发送认证请求; 以及接收认证中心根据所述认证请求返回 的认证应答, 获取包含在所述认证应答中的所述本端 UE的用户类型信息。
优选地, 上述 AGR还可具有如下特点:
所述维护模块是设置为: 若保存的本端 UE为移动用户, 则根据所述映 射关系生成并保存所述对端表条目。
优选地, 所述维护模块是设置为: 若保存的本端 UE为固定用户, 则不 生成所述对端表条目。
优选地, 上述 AGR还可具有如下特点:
所述获得模块包括:
第一接收单元, 其设置为: 接收本端 UE发送的业务流; 第一发送单元, 其设置为: 根据所述业务流中的对端 UE 的接入标识 ( AID ) 向映射服务器发送查询请求; 以及
第一获得单元, 其设置为: 接收所述映射服务器根据所述查询请求返回 的对端 UE的 AID和路由标识( RID ) 的映射关系。
优选地, 上述 AGR还可具有如下特点:
所述获得模块包括:
第二接收单元, 其设置为: 接收对端 UE发送的报文, 并对所述报文解 封装获得对端 UE的 AID;
第二发送单元, 其设置为: 根据所述对端 UE的 AID向映射服务器发送 查询请求; 以及 第二获得单元, 其设置为: 接收所述映射服务器根据所述查询请求返回 的对端 UE的 AID和路由标识( RID ) 的映射关系。
本发明还提供了一种表维护系统,所述系统包括接入网关路由器( AGR ), 其中:
所述 AGR设置为: 获取并保存本端用户设备(UE ) 的用户类型信息; 以及根据对端 UE的 AID和路由标识( RID )的映射关系和保存的本端 UE的 用户类型信息对对端表条目进行维护。
优选地, 所述系统还包括映射服务器,
所述 AGR还设置为: 根据对端 UE的接入标识(AID ) 向映射服务器发 送查询请求; 接收所述映射服务器返回的对端 UE的 AID和路由标识( RID ) 的映射关系;
所述映射服务器设置为:根据所述查询请求向所述 AGR返回对端 UE的 AID和路由标识(RID ) 的映射关系。
优选地, 上述表维护系统可具有如下特点:
所述系统还包括认证中心; 所述 AGR是设置为: 接收本端 UE发送的认 证信息, 并根据所述认证信息向所述认证中心发送认证请求; 以及接收认证 中心返回的认证应答, 并获取包含在所述认证应答中的所述本端 UE的用户 类型信息;
所述认证中心设置为: 根据所述认证请求向所述 AGR返回认证应答。 优选地, 上述表维护系统还可具有如下特点:
所述 AGR还设置为: 若保存的本端 UE为移动用户, 则根据所述映射关 系生成并保存所述对端表条目。
优选地, 所述 AGR还设置为:
若保存的本端 UE为固定用户, 则不生成所述对端表条目。
优选地, 上述表维护系统还可具有如下特点:
所述 AGR是设置为: 接收本端 UE发送的业务流; 根据所述业务流中的 对端 UE的接入标识( AID )向映射服务器发送查询请求; 以及接收所述映射 服务器根据所述查询请求返回的对端 UE的 AID和路由标识(RID ) 的映射 关系。
优选地, 上述表维护系统还可具有如下特点:
所述 AGR是设置为: 接收对端 UE发送的报文, 并对所述报文解封装获 得对端 UE的 AID; 根据所述对端 UE的 AID向映射服务器发送查询请求; 以及接收所述映射服务器根据所述查询请求返回的对端 UE的 AID和路由标 识(RID ) 的映射关系。
优选地, 所述 AGR包括:
获取模块, 其设置为: 获取并保存本端 UE的用户类型信息;
获得模块, 其设置为: 根据对端 UE的 AID获得对端 UE的 AID和路由 标识(RID ) 的映射关系; 以及
维护模块, 其设置为: 根据所述映射关系和保存的本端 UE的用户类型 信息对对端表条目进行维护。
上述表维护方法、 系统和接入网关路由器,可以有效地减少 AGR维护的 对端表条目的数量, 降低设备成本, 提高查表性能。 附图概述
图 1为现有技术的基于网络的身份标识和位置分离架构的网络拓朴示意 图;
图 2为本发明基于网络的身份标识和位置分离框架的网络架构的相关接 口示意图;
图 3为本发明表维护方法实施例一的流程图;
图 4为本发明获取并保存用户类型信息实施例的信令流程图;
图 5为本发明业务处理方法的信令流程图;
图 6为本发明表维护方法实施例二的流程图;
图 7为本发明 AGR的结构示意图; 图 8为本发明表维护系统的结构示意图。 本发明的较佳实施方式
下面将结合附图及实施例对本发明进行更详细的说明。
在图 1所示的网络框架下, 网络可划分为接入网和骨干网。 接入网位于 骨干网的边缘, 负责所有终端的接入, 在接入网 RAN部分, 所有的用户终端 都使用 AID进行寻址。 骨干网负责通过不同接入网接入的终端的路由。 接入 网与骨干网在拓朴关系上没有重叠。通信主机之间应用层使用 AID标识对端, 用户终端间的通信只需使用对端的 AID进行。
接入网关路由器(AGR )位于骨干网和接入网的分界点, 与接入网及骨 干网接口, 负责为终端提供接入服务、 维护用户连接、 转发用户数据等。 用 户终端的所有通信都通过所在接入网络的接入网关路由器进行转发和管理。 同一接入网关路由器服务范围内的终端之间数据报文直接转发给对端。 位于 不同接入网关路由器服务范围内的终端之间数据报文的转发如下: 终端在发 出数据报文时,对应的接入网关路由器在转发的数据报文中携带 RID信息(该 RID与 AID相对应) ; 对应地, 终端在接收数据报文时, 接入网关路由器进 行相反的操作, 即剥离 RID信息并将数据报文转发给终端。 映射服务器中保 存了网络中所有已经接入的用户终端所分配的身份位置标识映射关系, 并与 接入网关路由器通过信令交互进行标识关系解析。
上述基于网络的身份标识和位置分离框架的网络架构的相关接口如图 2 所示, S1/D1是用户终端与接入网关路由器 AGR的接口, S1用于用户接入管 理的信令, D1 为数据转发接口; S2用于 AGR间切换时切换管理信令, D2 用于 AGR间切换时数据转发; D3是与 AGR与 GSR间的数据转发接口, S4/S5/S6是用于查询和维护 AID-RID映射关系的信令接口, D4m是 AGR与 归属地 IDMS ( Home IDMS )间的数据转发接口。其中,在拜访地 IDMS( visited IDMS )与 Home IDMS无直联关系时, 中继 IDMS ( Broke IDMS )转发 visited IDMS与 Home IDMS间的信令。
由于标识网是一个固定移动统一的分组网络, 在实际部署中, 并不是每 一个接入用户都是移动节点, 因此, 如果在用户接入时识别用户类型, 仅为 移动节点维护对端表, 将对 AGR的系统性能会有较大提升。
本发明提供了一种表维护方法, 该方法包括:
接入网关路由器(AGR )获取并保存本端用户设备 ( UE )的用户类型信 息;
才艮据对端 UE的 AID获得对端 UE的 AID和路由标识 ( RID ) 的映射关 系; 以及
根据上述映射关系和保存的本端 UE的用户类型信息对对端表条目进行 维护。
如图 3所示,为本发明表维护方法实施例一的流程图 ,该实施例是从 AGR 侧进行描述的, 且在该实施例中, 本端 UE是发送端, 该方法包括:
步骤 301、 AGR获取并保存本端用户设备 ( UE ) 的用户类型信息; 用户类型信息可以为移动用户或固定用户;
步骤 302、 根据接收的业务流中的对端 UE的接入标识(AID )向映射服 务器发送查询请求;
步骤 303、接收上述映射服务器根据上述查询请求返回的对端 UE的 AID 和路由标识(RID ) 的映射关系;
步骤 304、根据上述映射关系和保存的本端 UE的用户类型信息对对端表 条目进行维护。 其中, 用户签约的用户类型信息存储在认证中心中, 当 UE附着时, 该 AGR通过与该认证中心进行交互可获取并保存该用户类型信息, 交互过程可 参见图 4, 该过程包括:
步骤 401、 UE和 AGR之间建立起链路层会话, 比如基于以太网的点到 点协议(PPPoE )会话;
步骤 402、 UE和 AGR之间发起认证会话, UE将认证信息 (比如用户名、 密码)发送给 AGR;
步骤 403、 AGR根据 UE发送的认证信息向认证中心发送认证请求; 步骤 404、认证中心收到 UE的认证请求后,根据签约信息对用户进行认 证, 并且根据签约信息确定 UE的用户类型;
步骤 405、 认证中心向 AGR返回认证应答, 并在应答中包含 UE的用户 类型信息;
步骤 406、 AGR与 UE完成认证会话, 并在本地保存 UE的用户类型信 息。
当 UE发起业务流时, AGR维护对端表条目的流程如图 5所示, 该过程 包括:
步骤 501、 当 UE访问某个业务时, 比如, 浏览网页、 点播视频等, 会触 发业务流的产生;
步骤 502、 UE发送业务流到 AGR;
步骤 503、 AGR根据业务流中的对端 UE的 AID发送请求到映射服务器, 查询对端 UE的 AID和 RID的映射关系;
步骤 504、 映射服务器将该映射关系返回给 AGR;
步骤 505、 AGR根据映射关系对报文进行外层封装, 同时根据前面保存 的本端 UE的用户类型, 决定是否需要生成并保存对端表条目。
如果本地 UE为移动用户, 则生成并保存对端表条目, 如果是固定用户 , 则不生成对端表条目。
当本端 UE作为业务流接收时的处理也与上面类似(即本端 UE和对端 UE是相对的 ) , 当本端 UE的 AGR接收到对端 UE发送过来的 文时, 一 方面去除外层封装,将报文转发给 UE, 另一方面,根据本端 UE的用户类型, 来决定是否需要生成并保存对端表条目, 具体流程如图 6所示, 该实施例是 从 AGR侧进行描述的, 且在该实施例中, 本端 UE是接收端, 该过程包括: 步骤 601、 接入网关路由器(AGR )获取并保存本端用户设备(UE ) 的 用户类型信息;
该步骤的实现过程可参见图 4;
步骤 602、 接收对端 UE发送的报文, 并对上述报文解封装获得对端 UE 的 AID; 步骤 603、 根据上述对端 UE的 AID向映射服务器发送查询请求; 步骤 604、接收上述映射服务器根据上述查询请求返回的对端 UE的 AID 和路由标识(RID ) 的映射关系;
步骤 605、根据上述映射关系和保存的本端 UE的用户类型信息对对端表 条目进行维护。 若保存的本端 UE为移动用户, 则根据上述映射关系生成并保存上述对 端表条目; 若保存的本端 UE为固定用户, 则不生成上述对端表条目。
综上上述,釆用本发明的方法,可以有效地减少 AGR维护的对端表条目 的数量, 降低设备成本, 提高查表性能。
如图 7所示, 为本发明 AGR的结构示意图, 该 AGR包括获取模块 71、 获得模块 72和维护模块 73 , 其中: 获取模块 71用于获取并保存本端用户设 备( UE ) 的用户类型信息; 获得模块 72用于根据上述对端 UE的 AID获得 对端 UE的 AID和路由标识(RID ) 的映射关系; 维护模块 73用于根据上述 映射关系和保存的本端 UE的用户类型信息对对端表条目进行维护。
优选地, 上述获取模块可以进一步用于接收本端 UE发送的认证信息, 并根据上述认证信息向认证中心发送认证请求; 以及接收认证中心根据上述 认证请求返回的认证应答, 获取包含在上述认证应答中的上述本端 UE的用 户类型信息。 上述维护模块可以进一步用于若保存的本端 UE为移动用户, 则根据上述映射关系生成并保存上述对端表条目; 若保存的本端 UE为固定 用户, 则不生成上述对端表条目。
该 AGR可以有效地维护对端表, 当该 AGR为发送端时, 上述获得模块 可以包括: 第一接收单元, 用于接收本端 UE发送的业务流; 第一发送单元, 用于根据上述业务流中的对端 UE的接入标识( AID )向映射服务器发送查询 请求; 以及第一获得单元, 用于接收上述映射服务器根据上述查询请求返回 的对端 UE的 AID和路由标识(RID ) 的映射关系。 其具体实现可参见图 3- 图 5。 当该 AGR为接收端时, 上述获得模块可以包括: 第二接收单元, 用于 接收对端 UE发送的报文,并对上述报文解封装获得对端 UE的 AID; 第二发 送单元, 用于根据上述对端 UE的 AID向映射服务器发送查询请求; 以及第 二获得单元, 用于接收上述映射服务器根据上述查询请求返回的对端 UE的 AID和路由标识(RID )的映射关系。 其具体实现可参见图 4和图 6, 此处不 再赘述。
该 AGR通过获取模块、获得模块和维护模块的交互,有效地减少了 AGR 维护的对端表条目的数量, 降低了设备成本, 提高了查表性能。
如图 8 所示, 为本发明表维护系统的结构示意图, 该系统包括 AGR81 和映射服务器 82, 其中: 上述 AGR用于获取并保存本端用户设备(UE ) 的 用户类型信息;根据对端 UE的接入标识( AID )向映射服务器发送查询请求; 接收上述映射服务器返回的对端 UE的 AID和路由标识(RID )的映射关系; 以及根据上述映射关系和保存的本端 UE的用户类型信息对对端表条目进行 维护; 上述映射服务器用于根据上述查询请求向上述 AGR返回对端 UE的 AID和路由标识(RID ) 的映射关系。
优选地, 上述系统还可以包括认证中心 83; 其中, 上述 AGR可以进一 步用于接收本端 UE发送的认证信息, 并根据上述认证信息向上述认证中心 发送认证请求; 以及接收认证中心返回的认证应答, 并获取包含在上述认证 应答中的上述本端 UE的用户类型信息; 上述认证中心可以用于根据上述认 证请求向上述 AGR返回认证应答。
另外, 上述 AGR可以进一步用于若保存的本端 UE为移动用户, 则根据 上述映射关系生成并保存上述对端表条目; 若保存的本端 UE为固定用户, 则不生成上述对端表条目。
进一步地, 上述 AGR可以用于接收本端 UE发送的业务流; 根据上述业 务流中的对端 UE的接入标识 ( AID )向映射服务器发送查询请求; 以及接收 上述映射服务器根据上述查询请求返回的对端 UE的 AID和路由标识 ( RID ) 的映射关系。 上述 AGR还可以用于接收对端 UE发送的报文, 并对上述报文 解封装获得对端 UE的 AID; 根据上述对端 UE的 AID向映射服务器发送查 询请求; 以及接收上述映射服务器根据上述查询请求返回的对端 UE的 AID 和路由标识(RID ) 的映射关系。
该系统通过 AGR与映射服务器及认证中心的交互,可以有效地减少 AGR 维护的对端表条目的数量, 降低设备成本, 提高查表性能。 本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序 来指令相关硬件完成, 上述程序可以存储于计算机可读存储介质中, 如只读 存储器、 磁盘或光盘等。 可选地, 上述实施例的全部或部分步骤也可以使用 一个或多个集成电路来实现。 相应地, 上述实施例中的各模块 /单元可以釆用 硬件的形式实现, 也可以釆用软件功能模块的形式实现。 本发明不限制于任 何特定形式的硬件和软件的结合。
以上实施例仅用以说明本发明的技术方案而非限制, 仅仅参照较佳实施 例对本发明进行了详细说明。 本领域的普通技术人员应当理解, 可以对本发 明的技术方案进行修改或者等同替换, 而不脱离本发明技术方案的精神和范 围, 均应涵盖在本发明的权利要求范围当中。
工业实用性 本发明实施例的表维护方法、 系统和接入网关路由器, 可以有效地减少
AGR维护的对端表条目的数量, 降低设备成本, 提高查表性能。

Claims

权 利 要 求 书
1、 一种表维护方法, 所述方法包括:
接入网关路由器(AGR )获取并保存本端用户设备 ( UE )的用户类型信 息;
才艮据对端 UE的 AID获得对端 UE的 AID和路由标识 ( RID ) 的映射关 系; 以及
根据所述映射关系和保存的本端 UE的用户类型信息对对端表条目进行 维护。
2、 根据权利要求 1所述的表维护方法, 其中, 所述 AGR获取并保存本 端 UE的用户类型信息包括:
所述 AGR接收本端 UE发送的认证信息,并根据所述认证信息向认证中 心发送认证请求; 以及
所述 AGR接收认证中心根据所述认证请求返回的认证应答,获取包含在 所述认证应答中的所述本端 UE的用户类型信息。
3、 根据权利要求 1所述的表维护方法, 其中, 所述根据所述映射关系和 保存的本端 UE的用户类型信息对对端表条目进行维护包括:
若保存的本端 UE为移动用户, 则根据所述映射关系生成并保存所述对 端表条目。
4、 根据权利要求 1所述的表维护方法, 其中, 所述根据所述映射关系和 保存的本端 UE的用户类型信息对对端表条目进行维护包括:
若保存的本端 UE为固定用户, 则不生成所述对端表条目。
5、 根据权利要求 1-4任一权利要求所述的表维护方法, 其中, 所述根据 对端 UE的 AID获得对端 UE的 AID和路由标识( RID ) 的映射关系包括: 接收本端 UE发送的业务流;
根据所述业务流中的对端 UE的接入标识( AID )向映射服务器发送查询 请求; 以及 接收所述映射服务器根据所述查询请求返回的对端 UE的 AID和路由标 识(RID ) 的映射关系。
6、 根据权利要求 1-4任一权利要求所述的表维护方法, 其中, 所述根据 对端 UE的 AID获得对端 UE的 AID和路由标识( RID ) 的映射关系包括: 接收对端 UE发送的报文, 并对所述报文解封装获得对端 UE的 AID; 根据所述对端 UE的 AID向映射服务器发送查询请求; 以及
接收所述映射服务器根据所述查询请求返回的对端 UE的 AID和路由标 识(RID ) 的映射关系。
7、 一种接入网关路由 (AGR ) , 所述 AGR包括:
获取模块, 其设置为: 获取并保存本端用户设备(UE )的用户类型信息; 获得模块, 其设置为: 根据对端 UE的 AID获得对端 UE的 AID和路由 标识(RID ) 的映射关系; 以及
维护模块, 其设置为: 根据所述映射关系和保存的本端 UE的用户类型 信息对对端表条目进行维护。
8、 根据权利要求 7所述的 AGR, 其中,
所述获取模块是设置为: 接收本端 UE发送的认证信息, 并根据所述认 证信息向认证中心发送认证请求; 以及接收认证中心根据所述认证请求返回 的认证应答, 获取包含在所述认证应答中的所述本端 UE的用户类型信息。
9、 根据权利要求 7所述的 AGR, 其中,
所述维护模块是设置为: 若保存的本端 UE为移动用户, 则根据所述映 射关系生成并保存所述对端表条目。
10、 根据权利要求 7所述的 AGR, 其中,
所述维护模块是设置为: 若保存的本端 UE为固定用户, 则不生成所述 对端表条目。
11、根据权利要求 7-10任一权利要求所述的 AGR, 其中, 所述获得模块 包括:
第一接收单元, 其设置为: 接收本端 UE发送的业务流;
第一发送单元, 其设置为: 根据所述业务流中的对端 UE 的接入标识 ( AID ) 向映射服务器发送查询请求; 以及
第一获得单元, 其设置为: 接收所述映射服务器根据所述查询请求返回 的对端 UE的 AID和路由标识( RID ) 的映射关系。
12、根据权利要求 7-10任一权利要求所述的 AGR, 其中, 所述获得模块 包括:
第二接收单元, 其设置为: 接收对端 UE发送的报文, 并对所述报文解 封装获得对端 UE的 AID;
第二发送单元, 其设置为: 根据所述对端 UE的 AID向映射服务器发送 查询请求; 以及
第二获得单元, 其设置为: 接收所述映射服务器根据所述查询请求返回 的对端 UE的 AID和路由标识( RID ) 的映射关系。
13、 一种表维护系统, 所述系统包括接入网关路由器(AGR ) , 其中: 所述 AGR设置为: 获取并保存本端用户设备(UE ) 的用户类型信息; 以及根据对端 UE的 AID和路由标识( RID )的映射关系和保存的本端 UE的 用户类型信息对对端表条目进行维护。
14、 根据权利要求 13所述的表维护系统, 其中, 所述系统还包括映射服 务器,
所述 AGR还设置为: 根据对端 UE的接入标识(AID ) 向映射服务器发 送查询请求; 接收所述映射服务器返回的对端 UE的 AID和路由标识( RID ) 的映射关系;
所述映射服务器设置为:根据所述查询请求向所述 AGR返回对端 UE的 AID和路由标识(RID ) 的映射关系。
15、 根据权利要求 14所述的表维护系统, 其中, 所述系统还包括认证中 心;
所述 AGR是设置为: 接收本端 UE发送的认证信息, 并根据所述认证信 息向所述认证中心发送认证请求; 以及接收认证中心返回的认证应答, 并获 取包含在所述认证应答中的所述本端 UE的用户类型信息; 所述认证中心设置为: 根据所述认证请求向所述 AGR返回认证应答。
16、 根据权利要求 13所述的表维护系统, 其中,
所述 AGR还设置为: 若保存的本端 UE为移动用户, 则根据所述映射关 系生成并保存所述对端表条目。
17、 根据权利要求 13所述的表维护系统, 其中, 所述 AGR还设置为: 若保存的本端 UE为固定用户, 则不生成所述对端表条目。
18、 根据权利要求 14-17任一权利要求所述的表维护系统, 其中, 所述 AGR是设置为: 接收本端 UE发送的业务流; 根据所述业务流中的 对端 UE的接入标识( AID )向映射服务器发送查询请求; 以及接收所述映射 服务器根据所述查询请求返回的对端 UE的 AID和路由标识(RID ) 的映射 关系。
19、 根据权利要求 14-17任一权利要求所述的表维护系统, 其中, 所述 AGR是设置为: 接收对端 UE发送的报文, 并对所述报文解封装获 得对端 UE的 AID; 根据所述对端 UE的 AID向映射服务器发送查询请求; 以及接收所述映射服务器根据所述查询请求返回的对端 UE的 AID和路由标 识(RID ) 的映射关系。
20、 根据权利要求 13所述的表维护系统, 其中, 所述 AGR包括: 获取模块, 其设置为: 获取并保存本端 UE的用户类型信息;
获得模块, 其设置为: 根据对端 UE的 AID获得对端 UE的 AID和路由 标识(RID ) 的映射关系; 以及
维护模块, 其设置为: 根据所述映射关系和保存的本端 UE的用户类型 信息对对端表条目进行维护。
PCT/CN2011/074627 2010-12-28 2011-05-25 表维护方法、系统和接入网关路由器 WO2012088828A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010613020.8A CN102547908B (zh) 2010-12-28 2010-12-28 表维护方法、系统和接入网关路由器
CN201010613020.8 2010-12-28

Publications (1)

Publication Number Publication Date
WO2012088828A1 true WO2012088828A1 (zh) 2012-07-05

Family

ID=46353590

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/074627 WO2012088828A1 (zh) 2010-12-28 2011-05-25 表维护方法、系统和接入网关路由器

Country Status (2)

Country Link
CN (1) CN102547908B (zh)
WO (1) WO2012088828A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104579969B (zh) 2013-10-29 2019-04-23 中兴通讯股份有限公司 报文发送方法及装置
CN103716391A (zh) * 2013-12-26 2014-04-09 星云融创(北京)信息技术有限公司 一种内容缓存的实现方法及路由器
CN111586675B (zh) * 2019-02-15 2022-04-12 华为技术有限公司 一种终端装置识别方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020186696A1 (en) * 2001-06-12 2002-12-12 Lg Electronics Inc. Method and system for packet data transmission
EP2003825A1 (en) * 2007-06-12 2008-12-17 Alcatel Lucent Method for sending a message to a receiving equipment attached to a network domain and associated to an unknown identifier and corresponding server(s)
CN101656765A (zh) * 2009-09-14 2010-02-24 中兴通讯股份有限公司 身份位置分离网络的名址映射系统及数据传输方法
CN101754219A (zh) * 2009-12-28 2010-06-23 中国人民解放军信息工程大学 标识分配和分离存储方法、标识替换传输方法及系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080005275A1 (en) * 2000-06-02 2008-01-03 Econnectix, Llc Method and apparatus for managing location information in a network separate from the data to which the location information pertains
CN100428719C (zh) * 2006-01-23 2008-10-22 北京交通大学 一种基于身份与位置分离的互联网接入方法
CN101123536B (zh) * 2007-09-19 2010-12-15 北京交通大学 实现一体化网络位置管理的方法
CN101667916B (zh) * 2009-09-28 2011-11-23 北京交通大学 一种基于分离映射网络使用数字证书验证用户身份的方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020186696A1 (en) * 2001-06-12 2002-12-12 Lg Electronics Inc. Method and system for packet data transmission
EP2003825A1 (en) * 2007-06-12 2008-12-17 Alcatel Lucent Method for sending a message to a receiving equipment attached to a network domain and associated to an unknown identifier and corresponding server(s)
CN101656765A (zh) * 2009-09-14 2010-02-24 中兴通讯股份有限公司 身份位置分离网络的名址映射系统及数据传输方法
CN101754219A (zh) * 2009-12-28 2010-06-23 中国人民解放军信息工程大学 标识分配和分离存储方法、标识替换传输方法及系统

Also Published As

Publication number Publication date
CN102547908A (zh) 2012-07-04
CN102547908B (zh) 2015-08-12

Similar Documents

Publication Publication Date Title
US9622072B2 (en) Communication method, method for forwarding data message during the communication process and communication node thereof
EP2954713B1 (en) Method and apparatus for reconfiguring a virtual home gateway
US8711749B2 (en) Information obtaining and notification, data message forwarding and handover method and access node
WO2017088628A1 (zh) 地址转换方法、装置及系统、网络标识控制方法及装置
JP2019526983A (ja) ブロードバンドリモートアクセスサーバの制御プレーン機能と転送プレーン機能の分離
JP2013527632A (ja) マルチnat64環境のための方法及びホストノード
CN113872845B (zh) 建立vxlan隧道的方法及相关设备
WO2016150140A1 (zh) 一种基于sdn的网关中控制报文的处理方法及系统
WO2011044790A1 (zh) 信息通知方法、切换过程中数据报文的转发方法及an
WO2011035710A1 (zh) 面向用户的通信方法和路由注册方法及设备及通信系统
WO2011015001A1 (zh) 通过无线局域网接入网络实现接入的方法及系统
WO2011032492A1 (zh) 身份识别、跨网通信、业务移植方法及信息互通网络架构
WO2011035615A1 (zh) 一种数据传输方法、系统及装置
WO2011035667A1 (zh) 实现网间漫游的方法、系统及查询和网络附着方法及系统
WO2011131097A1 (zh) 数据报文处理方法、系统及接入服务节点
WO2011032455A1 (zh) 切换管理及切换时用户数据管理的方法、系统和agr
WO2021169291A1 (zh) 发布路由的方法、网元、系统及设备
EP2466815B1 (en) Method and system for initiating forwarding of communicaiton, information and data message and for routing configuration
WO2014205680A1 (zh) 报文转发系统、设备和方法
WO2012088828A1 (zh) 表维护方法、系统和接入网关路由器
WO2011035582A1 (zh) WiMAX系统中多接口数据流负荷分担的方法及装置
WO2013023465A1 (zh) 身份位置分离与传统网络互联互通方法、ilr和asr
US9439127B2 (en) Method for data transmission and local network entity
WO2012089032A1 (zh) 一种采用多种接入方式中的数据传输方法和接入设备
WO2012088830A1 (zh) 一种通信方法、消息处理方法及系统

Legal Events

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

Ref document number: 11853538

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11853538

Country of ref document: EP

Kind code of ref document: A1