WO2009137994A1 - 接入网关绑定建立方法和系统 - Google Patents

接入网关绑定建立方法和系统 Download PDF

Info

Publication number
WO2009137994A1
WO2009137994A1 PCT/CN2009/070148 CN2009070148W WO2009137994A1 WO 2009137994 A1 WO2009137994 A1 WO 2009137994A1 CN 2009070148 W CN2009070148 W CN 2009070148W WO 2009137994 A1 WO2009137994 A1 WO 2009137994A1
Authority
WO
WIPO (PCT)
Prior art keywords
binding
proxy mobile
capability
access gateway
base station
Prior art date
Application number
PCT/CN2009/070148
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 WO2009137994A1 publication Critical patent/WO2009137994A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W92/00Interfaces specially adapted for wireless communication networks
    • H04W92/04Interfaces between hierarchically different network devices
    • H04W92/06Interfaces between hierarchically different network devices between gateways and public network devices
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W80/00Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04Network layer protocols, e.g. mobile IP [Internet Protocol]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18Service support devices; Network management devices
    • H04W88/182Network node acting on behalf of an other network entity, e.g. proxy

Definitions

  • the present invention relates to the field of Ultra Mobile Broadband (UMB) communication, and in particular, to an access gateway binding establishment method and system. Background technique
  • FIG. 1 is a block diagram of a network structure of an access network supporting UMB technology determined in the related art.
  • AGW Access Gateway
  • AT Access Terminal
  • IP attachment point required to access the data packet network.
  • AGW is equivalent to the first hop router.
  • Evolved Base Station (eBS) is available on the wireless carrier.
  • the eBS includes an Access Network Route Instance (ANRI).
  • ANRI Access Network Route Instance
  • the eBS can assume at least one of the following roles: Forward Link Serving eBS (FLSE), Reverse Link Serving eBS (RTLSE) ), Data Attachment Point (DAP), of course, for each AT, eBS can also bear other roles, not listed here.
  • the DAP is the communication point that communicates with the AGW when receiving the forward link data on the bearer plane, and the AGW sends the AT-related data and signaling to the DAP, and the reverse link data from the AT. It can be sent to the AGW via DAP or directly to the AGW by RLSE.
  • Session Reference Network Controller Session Reference Network Controller
  • SRNC is responsible for maintaining the session reference with the AT.
  • the SRNC is also responsible for supporting the idle state management of the AT, and participating in the authentication of the AT, and providing paging when the AT is idle.
  • Control function, for each AT supported, SRNC contains a session anchor ANRI.
  • Proxy Mobile IP Bindings include the following types: (1) Primary Proxy Mobile IP Binding (PMIP Binding): Also known as Single Proxy Mobile IP Binding, Once the basic proxy mobile IP binding is successfully established, the AGW will only send the forward link data packet to the eBS;
  • PMIP binding of IPV4 After the AT authentication authentication is passed, after the AT acquires the information of the relevant network through the access network, for example, after obtaining the link identifier (Link ID), the authentication key, etc., the evolved base station and The AGW establishes an initial PMIP tunnel or binding. This binding can be RL+Primary or Primary PMIP binding. If the AT adds an eBS to its routing set, if the eBS wishes to establish a proprietary reverse tunnel or binding with the AGW, then the eBS and AGW can establish a reverse only PMIP tunnel. If an eBS wants to be a DAP, it can establish an RL+Primary or Primary PMIP binding with the AGW.
  • the eBS establishes various tunnels or bindings by sending a PMIP Registration Request (RRQ) message to the AGW.
  • RRQ PMIP Registration Request
  • the PMIP RRQ message sent therein will carry different extension fields to display the binding that the eBS attempts to establish. Types of. details as follows:
  • the PMIP RRQ message does not carry 'Binding Type Extension'; (2) If the eBS establishes the reverse PMIP binding only, the PM PM PMQ RRQ message carries the 'RL Only Binding Type Extension'; if the AGW does not support the reverse only binding, then AGW ⁇ ! Retrieve the PMIP RRP message and carry the code value 129 (admintically prohibited);
  • the PMIP RRQ message carries the 'Signaling Only Binding Type Extension'. If the AGW does not support the signaling only binding, the AGW ⁇ 1 returns the PMIP RRP message, and Carrying code 129 (admintically prohibited);
  • the PMIP RRQ message contains 'RL + Primary Binding Type Extension'.
  • the AGW does not support the 'Binding Type Extension' field, the PMIP RRQ message will be discarded. In this case, no notification will be sent to the evolved base station or SRNC, which will result in eBS/SRNC. PMIP RRQ messages are sent again and again, and these messages are eventually discarded without any notification. Therefore, if the eBS can know the AGW's ability to support PMIP binding, it will help the eBS correctly judge and successfully establish the corresponding tunnel or binding, thus avoiding multiple message interactions caused by the AGW not supporting.
  • the prior art has proposed defining the capabilities of the AGW in the following ways:
  • AGW supports Primary type of binding only
  • AGW supports Primary + Reverse-Link types of bindings
  • AGW supports Primary + Signaling types of bindings 3.
  • AGW supports Primary + Reverse-Link + Signaling types of bindings
  • the main purpose of the invention is to provide an improved access gateway binding establishment solution to solve the above-mentioned interaction problem in the related art. According to an aspect of the present invention, an access gateway binding establishment method is provided.
  • the access gateway binding establishment method includes: the session reference network controller acquires the capability of the proxy mobile IP binding supported by the access gateway; and the session reference network when the evolved base station acquires the session information from the session reference network controller
  • the controller sends the capability of the supported proxy mobile IP binding of the access gateway to the evolved base station; the evolved base station acquires the capability of the supported proxy mobile IP binding of the access gateway, and according to the capability of the evolved base station itself
  • the acquired capability of the proxy mobile IP binding supported by the access gateway sends a proxy mobile IP registration request message to the access gateway to establish a corresponding binding to the access gateway.
  • the session reference network controller acquires the capability of the proxy mobile IP binding supported by the access gateway when participating in the authentication of the access terminal.
  • the evolved base station acquires the binding capability of the supported proxy mobile IP of the access gateway by sending a session information request message to the session reference network controller and from the session information response message returned by the session reference network controller.
  • the capability value indicates that the access gateway supports any of the basic proxy mobile IP binding, the reverse only link proxy mobile IP binding, the signaling binding, or a combination thereof as the binding type extension.
  • the manner in which the capability value indicates the capability of the supported proxy mobile IP binding of the access gateway is specifically: 0 indicates that the access gateway only supports basic proxy mobile IP binding, and 1 indicates that the access gateway supports the basic proxy Mobile IP binding and/or reverse only link proxy mobile IP binding, 2 indicates that the access gateway supports basic proxy mobile IP binding or signaling binding, and 3 indicates that the access gateway supports basic proxy mobile IP binding Fixed, and/or reverse link proxy mobile IP binding, and / or signaling binding, and 4 as a reserved field.
  • the method further includes one of the following: if the evolved base station establishes a basic proxy mobile IP binding or a single basic proxy mobile IP binding, and the evolved base station acquires the capability value of 0, 1, 2, Or 3, the proxy mobile IP registration request message does not carry the binding type extension; if the evolved base station establishes the reverse only proxy mobile IP binding, and the acquired capability value is 1 or 3, then the mobile mobile IP registration request message Carry the following binding type extensions: RL Only Binding Type Extension; If the evolved base station establishes the only proxy mobile IP binding of the signaling, and the acquired capability value is 2 or 3, the proxy mobile IP registration request message carries the following binding type extension: Signaling Only Binding Type Extension; The evolved base station establishes multiple proxy mobile IP bindings, and the acquired capability value is 2 or 3.
  • the proxy mobile IP registration request message carries the following binding type extension: RL+Primary Binding Type Extension.
  • an access gateway binding establishment system includes: a session reference network controller, configured to acquire a proxy mobile IP binding capability supported by the access gateway, and acquire a session from the session reference network controller at the evolved base station Information, the session reference network controller sends the capability of the supported proxy mobile IP binding of the access gateway to the evolved base station; the evolved base station, configured to acquire the supported proxy mobile IP binding capability of the access gateway, and The proxy mobile IP registration request message is sent to the access gateway according to the capability of the evolved base station itself and the acquired capability of the proxy mobile IP binding supported by the access gateway to establish a corresponding binding to the access gateway.
  • the session reference network controller acquires the capability of the proxy mobile IP binding supported by the access gateway when participating in the authentication of the access terminal.
  • the evolved base station may acquire the binding capability of the supported proxy mobile IP of the access gateway by sending a session information request message to the session reference network controller and from the session information response message returned by the session reference network controller.
  • the session reference network controller may indicate, by using the capability value, that the access gateway supports basic proxy mobile IP binding, reverse only link proxy mobile IP binding, signaling binding, or a combination thereof as the binding type. Expansion.
  • the PMIP support capability of the AGW can be transmitted in the access network, thereby realizing the optimization of the PMIP binding establishment process between the eBS and the AGW in the UMB network, and avoiding unnecessary signaling interaction.
  • FIG. 1 is a block diagram of a network structure of an access network supporting UMB technology according to the related art
  • FIG. 2 is a flowchart of a method for establishing an access gateway binding according to an embodiment of the method of the present invention
  • FIG. 4 is a signaling flowchart of a processing example 2 of an access gateway binding establishment method according to an embodiment of the method of the present invention
  • FIG. 1 is a block diagram of a network structure of an access network supporting UMB technology according to the related art
  • FIG. 2 is a flowchart of a method for establishing an access gateway binding according to an embodiment of the method of the present invention
  • FIG. 4 is a signaling flowchart of a processing example 2 of an access gateway binding establishment method according to an embodiment of the method of the present invention
  • FIG. 4 is a signaling flowchart of a processing example 2 of an access gateway binding establishment method according to an embodiment of the method of the present invention
  • 5 is a flow diagram of an access gateway binding setup system in accordance with an embodiment of the present invention.
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The preferred embodiments of the present invention are described with reference to the accompanying drawings. If not conflicting, the embodiments of the present invention and the features of the embodiments can be combined with each other, and are all within the protection scope of the present invention.
  • Method Embodiment In this embodiment, an access gateway binding establishment method is provided.
  • the access gateway binding establishment method includes: Step S202: The SRNC acquires the capability of the PMIP binding supported by the AGW; Step S204: When the eBS obtains the session information from the SRNC, the SRNC The capability of the supported PMIP binding of the AGW is sent to the eBS; in step S206, the eBS acquires the capability of the supported PMIP binding of the AGW, and the data is obtained.
  • the capability of the eBS itself and the acquired ability of the AMG to support the PMIP binding send a proxy mobile IP registration request message to the AGW to establish a corresponding binding to the AGW.
  • the SRNC may acquire the authentication performed by the access terminal, and the eBS obtains the session information request message from the SRNC, and obtains the supported information of the AGW from the session information response message returned by the SRNC.
  • Proxy mobile IP binding capabilities indicates that the AGW supports any one of the basic PMIP, the reverse only link PMIP, the signaling binding, or a combination thereof as the binding type extension. The details are described below.
  • the way in which the capability value indicates the capability of the supported PMIP binding of the AGW can be set as follows: 0 indicates that the AGW only supports the basic PMIP, and 1 indicates that the AGW supports the basic PMIP and/or the reverse only link PMIP, 2 indicates that the AGW supports basic PMIP or signaling binding, and 3 indicates that the AGW supports basic PMIP, and/or reverse link PMIP, and/or signaling binding, and uses 4 as a reserved field.
  • 0 indicates that the AGW only supports the basic PMIP
  • 1 indicates that the AGW supports the basic PMIP and/or the reverse only link PMIP
  • 2 indicates that the AGW supports basic PMIP or signaling binding
  • 3 indicates that the AGW supports basic PMIP, and/or reverse link PMIP, and/or signaling binding
  • uses 4 as a reserved field.
  • the proxy mobile IP registration request message does not carry the binding type extension
  • the proxy mobile IP registration request message carries the following binding type extension: RL Only Binding Type Extension;
  • the proxy mobile IP registration request message carries the following binding type extension: Signaling Only Binding Type Extension;
  • the proxy mobile IP registration request message carries the following binding type extensions: RL+Primary Binding Type Extension; (5) If the eBS acquires capabilities The value is 0, and the e-BBS does not carry the binding type extension in the proxy mobile IP registration request message;
  • the e-mail mobile IP registration request message carries the RL Only Binding Type Extension (only Establish reverse only link PMIP) or RL Only+Primary Binding Type Extension (establish multi-PMIP);
  • the proxy mobile IP registration request message carries the following binding type extension: RL Only Binding Type Extension;
  • the eBS does not carry the binding type extension in the proxy mobile IP registration request message; (10) if the eBS acquires the capability value of 3, And the eBS supports the reverse link only PMIP, and the e-mail carries the following binding type extensions in the mobile IP registration request message: RL Only Binding Type Extension or RL Only+Primary Binding Type Extension;
  • the e-mail mobile registration request message carries the following binding type extension: RL Only Binding Type Extension;
  • Step 1 the SRNC participates in the authentication of the AT. In the process, the capability of the AGW to support the PMIP binding is obtained.
  • Step 2 When the eBS requests the session information from the SRNC, the SRNC simultaneously sends the PMIP support capability of the AGW to the eBS.
  • Step 3 The eBS sends the capability according to its own capabilities and the capabilities of the AGW.
  • the PMIP RRQ message is used to establish the corresponding binding.
  • step 2 enhance the prior art eBS and SRNC message Internet authentication service IAS) -Session Information Response to include the capabilities of the AGW PMIP.
  • IAS Internet authentication service
  • the message is defined as an IAS-Session Information Response, and the message format is as shown in Table 1. Table 1
  • the IAS DAP Record information unit in the session information response message is enhanced by an IAS DAP Record, which contains information of each AGW connected by the AT.
  • the information element also contains information about the DAP (This IE contains AGW information for each AC
  • this IE also contains information About the DAP), Bay 1 J This cell structure is delicious as shown in Table 2.
  • IAS AGW Record- 1 Variable IAS AGW Record - 1 Variable 4.2.1.18 IAS DAP Record
  • Length The field includes the length of the information unit (in this case, the number of bytes is X This field contains the number of octets in this IE following this field as a binary number );
  • IAS AGW Record Count This field indicates the number of IAS AGW records in this IE (This field indicates the number IAS AGW Records in this IE);
  • IAS AGW Record The encoding of the IAS AGW Record (IAS AGW Record) is shown in Table 4:
  • AGW-RAN PMIP Capability (AGW - RAN PMIP capability) is defined 0: support basic PMIP binding (AGW supports Primary type of binding only AGW)
  • AGW supports Primary + Reverse-Link types of bindings
  • AGW supports Primary + Signaling types of bindings
  • AGW supports basic + reverse link + signaling binding (AGW supports Primary + Reverse-Link + Signaling types of bindings)
  • the PM PM RRQ message does not carry the Binding Type Extension
  • Example 1 Establishing the initial PMIP binding As shown in Figure 3, the processing in this example is as follows:
  • AGW is from AAA (Home AAA-HAAA) receives the AAA-session identifier and other parameters; the AGW selects a unique random key for the AT called PMN-AN-RK, and derives PMN-AN-RK1.AGW from PMN-AN-RK1, The AAA-session identifier and other related parameters are sent to the SRNC; the AGW sends its support PMIP binding capability to the SRNC at the same time; ( ⁇ ) The SRNC obtains the AGW support PMIP binding capability and other parameters;
  • eBS1 sends an IAS session information request message to the SRNC to obtain related session information
  • the SRNC Upon receiving the session information request, the SRNC responds with an IAS-session information response message including the AGW IP address, LinkID, user name, AAA-session ID, PMN-AN-RK, and the PIMP binding capability supported by the AGW. , ie, AGW-RAN-PMIP-Binding-Capability information;
  • the eBS1 assigns a link identifier (LinkID) to the AT, and the link identifier represents an IP interface created by the ZT for session with the IP layer;
  • LinkID link identifier
  • the ZT sends a Data Attachment Request (DAP Move Request) message to the eBS l;
  • DAP Move Request Data Attachment Request
  • the eBS 1 sends a PMIP RRQ message to the AGW, which includes the NAI and eBS 1 IP addresses to establish the initial PMIP tunnel; and the eBS1 also receives the AGW-RAN-PMIP-Binding-Capability received in step 3. AMB-supported PMIP binding capability) to determine whether to carry 'Binding Type Extension 4 or, and the corresponding extension value.
  • eBSl and AGW support reverse binding only, then carry RL+Primary binding type;
  • the parameter can be carried: NAI, eBS1 IP Address, GRE extension, MN-HA Authentication;
  • the AGW sends a PMIP-Registration Reply message to confirm the establishment of the corresponding PMIP tunnel; preferably, the parameter can carry: NAI, GRE Key, MN-HA Authentication;
  • eBS1 sends a DAP to the AT
  • the AT indicates to the upper layer of the IP layer that the link has been established, and the upper layer IP layer compares the current IP interface with its current IP interface. If not, the IP address is triggered. (12) Complete the IP address assignment;
  • IP packets can be passed between the AT and the AGW.
  • Example 2 Adding an AT route set As shown in FIG. 4, in this example, the following processing procedure is included: (a) AT is currently in connection with eBS1, and SRNC is in a route set;
  • the AT sends a Route Open Request message to eBS2 in a tunnel manner to increase eBS2 to the route set;
  • eBS2 sends an IAS-Session Information Request message to the SRNC;
  • the SRNC responds to the eBS2 with an IAS-Session Information Response message, which includes the PMIP binding capability supported by the AGW;
  • the eBS According to the PMIP capability of the AGW, the eBS sends a PMIP-Registration Request message to the AGW to establish an additional data tunnel, and the RL Only Type Extension is included in the message;
  • the SRNC After receiving the updated Route Ma, the SRNC sends an IAS-UATI Update message to eBS2; ( k* "eBS2 sends an IAS-UATI Update Ack message to the SRNC;
  • eBS l sends an IPT-Notification message to eBS2 to clarify that it is a forward serving base station and a data attachment point;
  • the AGW binding establishment system includes: SRNC 502, which is used to acquire the capability of PMIP supported by the AGW, and when the eBS 504 acquires session information from the SRNC, the SRNC 502 will The capabilities of the supported PMIP bindings are sent to the eBS 504, where the SRNC 502 can acquire the capabilities of the PMIP support supported by the AGW when participating in authentication of the access terminal.
  • the SRNC 502 may indicate that the AGW supports the basic PMIP, the reverse only link PMIP, the signaling binding, or a combination thereof as the binding type extension by the capability value, and the specific representation manner has been described before, and is no longer described here. repeat.
  • the eBS 504 is configured to acquire the supported PMIP binding capability of the AGW, and send the proxy mobile IP registration request message to the AGW according to the capability of the eBS 504 itself and the acquired capability of the AMG-supported PMIP binding to the AGW. Establish the appropriate bindings.
  • the eBS 504 can acquire the binding capability of the supported Proxy Mobile IP of the AGW by sending a Session Information Request message to the SRNC 502 and a Session Information Response message returned from the SRNC 502.
  • a Session Information Request message to the SRNC 502
  • a Session Information Response message returned from the SRNC 502.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Description

接入网关绑定建立方法和系统
技术领域 本发明涉及超移动宽带 ( Ultra Mobile Broadband, 简称为 UMB ) 通信 领域, 并且特别地, 涉及一种接入网关绑定建立方法和系统。 背景技术
UMB是码分多址( Code Division Multiple Access, 简称为 CDMA ) 2000 接入技术的演进技术, UMB空中接口的诸多技术可以提升 CDMA 2000接入 技术网络的性能, 从而可以为用户提供更多更高要求的无线多媒体业务。 为了支持 UMB空中接口技术, 相应的网络也在进行新的演进发展。 图 1是相关技术中确定的支持 UMB技术的接入网的网络结构框图。 图 1中各个网元的功能如下: 接入网关( Access Gateway, 简称 AGW )为接入终端( Access Terminal, 简称 AT )提供了接入数据分组网络所需的 "IP依附点 ", 因此对于 AT而言, AGW相当于第一跳路由器。 演进的基站 ( Evolved Base Station, 简称 eBS ) 是可以在无线载波上与
AT进行通信的逻辑实体。 对于所服务的每个 AT, eBS都包含一个接入网络 路由实例 ( Access Network Route Instance, 简称 ANRI )。 对于每个 AT, eBS 都可以 担如下多个角色中的至少一个: 前向链路月 务基站 ( Forward Link Serving eBS, 简称 FLSE )、 反向链路月 务基站 ( Reverse Link Serving eBS , 简称 RLSE )、 数据依附点 (Data Attachment Point, 简称 DAP ), 当然, 对于 每个 AT, eBS还可以寿担其它角色, 这里不再 列举。 对于 AT而言, DAP是其在承载面上接收前向链路数据时与 AGW进行 通信的通信点, AGW将与 AT相关的数据和信令发送给 DAP, 而来自 AT的 反向链路数据既可以通过 DAP发给 AGW,也可以由 RLSE直接发给 AGW。 会话参考网络控制器 (Session Reference Network Controller, 简称为
SRNC ) 负责维护与 AT之间的会话参考, SRNC还负责对 AT的空闲状态管 理提供支持, 以及参与对 AT的鉴权认证, 并在 AT处于空闲状态时提供寻呼 控制功能, 对于所支持的每个 AT, SRNC都包含一个会话锚点 ANRI。 在 UMB网络技术中, eBS和 AGW之间通过建立代理移动 IP隧道来 载数据的传输。 这些代理移动 IP隧道绑定 ( Proxy Mobile IP Binding ) 包括 如下类型: ( 1 )基本^ ^理移动 IP绑定 ( Primary Proxy Mobile IP Binding, PMIP 绑定): 也称为单个代理移动 IP绑定, 一旦基本代理移动 IP绑定成功建立, AGW将只发送前向链路数据包给这个 eBS;
( 2 ) 多个 PMIP绑定 ( Multiple PMIP Binding ): 基于 AT, 如果 AGW 被配置使用多绑定,则 AGW只处理与其成功建立了反向链路 PMIP注册(也 就是 Binding Type Extention设置为 RL Only Binding )的 eBS发送的 AT的数 据、 或者基本 PMIP注册的 eBS发送的 AT的数据, 而对于其他 eBS发送过 来的数据, AG W将丢弃;
( 3 ) 信令仅有 PMIP绑定 ( Signaling-Only PMIP Binding ): 对于 AT, 信令仅有 PMIP绑定在某些时刻是存在的; AGW不再向涉及到 AT的该实体 发送任何数据包, 而是当有数据抵达 AGW时, 向其发送数据通知信令消息。
IPV4的 PMIP绑定一 ^:在 AT鉴权认证通过之后, 在 AT通过接入网获 取相关网络的信息之后, 例如, 获取链路标识 ( Link ID )、 鉴权密钥等之后, 演进基站和 AGW建立初始 PMIP隧道或者绑定,这个绑定可以是 RL+Primary 或者 Primary PMIP绑定。 如果 AT增加一个 eBS到它的路由集中, 如果该 eBS希望建立和 AGW 之间的专有反向隧道或者绑定,则该 eBS和 AGW可以建立反向仅有的 PMIP 隧道。 如果某个 eBS 想成为 DAP, 则它可以和 AGW 建立 RL+Primary 或 Primary PMIP绑定。 eBS建立各种隧道或者绑定都是通过发送 PMIP注册请求( RRQ )消息 给 AGW, 艮据 eBS的能力, 其发送的 PMIP RRQ消息中将会携带有不同的 扩展字段来显示 eBS试图建立的 binding类型。 具体如下:
( 1 ) 如果 eBS 建立单个 PMIP 绑定, 则 PMIP RRQ 消息中不携带 'Binding Type Extension'; ( 2 ) 如果 eBS建立反向仅有的 PMIP绑定, 贝l PMIP RRQ消息中携带 'RL Only Binding Type Extension'; 如果 AGW不支持反向仅有绑定, 则 AGW ^!夺返回 PMIP RRP消息, 并携带码值 129 ( administratively prohibited );
( 3 ) 如果 eBS建立信令仅有的 PMIP绑定, 则 PMIP RRQ消息中携带 ' Signaling Only Binding Type Extension' , 如果 AGW不支持信令仅有绑定, 则 AGW^1返回 PMIP RRP消息,并携带码值 129( administratively prohibited );
( 4 ) 如果 eBS想建立多个 PMIP绑定, 则 PMIP RRQ消息包含 'RL +Primary Binding Type Extension' 。 另夕卜, 如果 AGW不支持 'Binding Type Extension,字段, 贝l PMIP RRQ 消息将会被丢弃, 在这种情况下, 不会有任何通知发送给演进基站或者 SRNC, 这样就会导致 eBS/SRNC重新多次地发送 PMIP RRQ消息, 而这些 消息最终都会被丢弃, 却没有任何通知。 因此, 如果能够让 eBS知道 AGW支持 PMIP绑定的能力, 将有助于 eBS正确判断并成功建立相应隧道或者绑定, 从而避免因 AGW不支持而造 成的多次消息交互。 现有技术已经提出通过以下方式对 AGW的能力进行了定义:
0. AGW supports Primary type of binding only
1. AGW supports Primary + Reverse-Link types of bindings
2. AGW supports Primary + Signaling types of bindings 3. AGW supports Primary + Reverse-Link + Signaling types of bindings
4. Other values are reserved。 但是, 目前的方案不能将该能力信息传递到 eBS , 因此, 无法避免因 AGW不支持而导致的多次消息交互的问题。 发明内容 考虑到相关技术中存在的不能将该能力信息传递到 eBS, 因此, 无法避 免因 AGW不支持而导致的多次消息交互的问题而提出本发明, 为此, 本发 明的主要目的在于提供一种改进的接入网关绑定建立方案, 以解决相关技术 中的上述交互的问题。 根据本发明的一个方面, 提供了一种接入网关绑定建立方法。 根据本发明的接入网关绑定建立方法包括:会话参考网络控制器获取接 入网关所支持的代理移动 IP绑定的能力;在演进基站从会话参考网络控制器 获取会话信息时,会话参考网络控制器将接入网关的所支持的代理移动 IP绑 定的能力发送给演进基站;演进基站获取接入网关的所支持的代理移动 IP绑 定的能力, 并才艮据演进基站本身的能力及获取的接入网关支持的代理移动 IP 绑定的能力向接入网关发送代理移动 IP 注册请求消息以对接入网关建立相 应的绑定。 其中, 会话参考网络控制器在参与对接入终端进行的鉴权时, 获取接入 网关所支持的代理移动 IP绑定的能力。 并且, 演进基站通过向会话参考网络控制器发送会话信息请求消息, 并 从会话参考网络控制器返回的会话信息响应消息获取接入网关的所支持的代 理移动 IP的绑定能力。 此外, 通过能力值表示接入网关支持基本代理移动 IP绑定、 反向仅有 链路代理移动 IP绑定、 信令绑定中的任一个或其组合作为绑定类型扩展。 具体地, 通过能力值表示接入网关的所支持的代理移动 IP绑定的能力 的方式具体为: 通过 0表示接入网关仅支持基本代理移动 IP绑定, 通过 1 表示接入网关支持基本代理移动 IP 绑定和 /或反向仅有链路代理移动 IP 绑 定, 通过 2表示接入网关支持基本代理移动 IP绑定或信令绑定, 通过 3表示 接入网关支持基本代理移动 IP绑定、 和 /或反向链路代理移动 IP绑定、 和 / 或信令绑定, 并将 4作为保留字段。 此时, 在演进基站建立绑定时, 进一步包括以下之一: 如果演进基站建立基本代理移动 IP绑定或单个基本代理移动 IP绑定, 且演进基站获取的能力值为 0、 1、 2、 或 3 , 则代理移动 IP注册请求消息不 携带绑定类型扩展; 如果演进基站建立反向仅有的代理移动 IP绑定, 且获取的能力值为 1 或 3 ,则«理移动 IP注册请求消息中携带以下绑定类型扩展: RL Only Binding Type Extension; 如果演进基站建立信令仅有的代理移动 IP绑定, 且获取的能力值为 2 或 3 , 则代理移动 IP注册请求消息中携带以下绑定类型扩展: Signaling Only Binding Type Extension; 如果演进基站建立多个代理移动 IP绑定, 且获取的能力值为 2或 3 , 则代理移动 IP注册请求消息中携带以下绑定类型扩展: RL+Primary Binding Type Extension。 根据本发明的另一个方面, 提供了一种接入网关绑定建立系统。 才艮据本发明的接入网关绑定建立系统包括: 会话参考网络控制器, 用于 获取接入网关所支持的代理移动 IP绑定的能力,并且在演进基站从会话参考 网络控制器获取会话信息时, 会话参考网络控制器将接入网关的所支持的代 理移动 IP绑定的能力发送给演进基站; 演进基站, 用于获取接入网关的所支 持的代理移动 IP绑定的能力,并才艮据演进基站本身的能力及获取的接入网关 支持的代理移动 IP绑定的能力向接入网关发送代理移动 IP注册请求消息以 对接入网关建立相应的绑定。 其中, 会话参考网络控制器在参与对接入终端进行的鉴权时, 获取接入 网关所支持的代理移动 IP绑定的能力。 此外, 演进基站可通过向会话参考网络控制器发送会话信息请求消息, 并从会话参考网络控制器返回的会话信息响应消息获取接入网关的所支持的 代理移动 IP的绑定能力。 另外,会话参考网络控制器可通过能力值表示接入网关支持基本代理移 动 IP绑定、 反向仅有链路代理移动 IP绑定、 信令绑定中的任一个或其组合 作为绑定类型扩展。 通过本发明的上述技术方案, 能够通过在接入网传递 AGW的 PMIP支 持能力, 从而实现了对 UMB网络中 eBS和 AGW之间 PMIP绑定的建立流 程的优化, 避免了不必要的信令交互。 本发明的其它特征和优点将在随后的说明书中阐述, 并且, 部分地从说 明书中变得显而易见, 或者通过实施本发明而了解。 本发明的目的和其他优 点可通过在所写的说明书、 权利要求书、 以及附图中所特别指出的结构来实 现和获得。 附图说明 此处所说明的附图用来提供对本发明的进一步理解,构成本申请的一部 分, 本发明的示意性实施例及其说明用于解释本发明, 并不构成对本发明的 不当限定。 在附图中: 图 1是根据相关技术中支持 UMB技术的接入网的网络结构框图; 图 2是根据本发明方法实施例的接入网关绑定建立方法的流程图; 图 3 是根据本发明方法实施例的接入网关绑定建立方法的处理实例 1 的信令流程图; 图 4 是根据本发明方法实施例的接入网关绑定建立方法的处理实例 2 的信令流程图; 以及 图 5是根据本发明系统实施例的接入网关绑定建立系统的流程图。 具体实施方式 以下结合附图对本发明的优选实施例进行说明, 应当理解, 此处所描述 的优选实施例仅用于说明和解释本发明, 并不用于限定本发明。如果不沖突, 本发明实施例以及实施例中的特征可以相互组合, 均在本发明的保护范围之 内。 方法实施例 在本实施例中, 提供了一种接入网关绑定建立方法。 需要说明的是, 在 附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中 执行, 并且, 虽然在流程图中示出了逻辑顺序, 但是在某些情况下, 可以以 不同于此处的顺序执行所示出或描述的步骤。 如图 2 所示, 根据本发明实施例的接入网关绑定建立方法包括: 步骤 S202 , SRNC获取 AGW所支持的 PMIP绑定的能力; 步骤 S204 , 在 eBS从 SRNC获取会话信息时, SRNC将 AGW的所支持的 PMIP绑定的能力发送 给 eBS; 步骤 S206, eBS获取 AGW的所支持的 PMIP绑定的能力, 并才艮据 eBS本身的能力及获取的 AGW支持的 PMIP绑定的能力, 向 AGW发送代 理移动 IP注册请求消息, 以对 AGW建立相应的绑定。 对于 AGW所支持的 PMIP绑定的能力, SRNC可以在参与对接入终端 进行的鉴权时获取, eBS通过向 SRNC发送会话信息请求消息, 并从 SRNC 返回的会话信息响应消息获取 AGW的所支持的代理移动 IP的绑定能力。 此外, 通过能力值表示 AGW支持基本 PMIP、 反向仅有链路 PMIP、 信 令绑定中的任一个或其组合作为绑定类型扩展。 以下进行详细描述。 例如, 通过能力值表示 AGW的所支持的 PMIP绑定的能力的方式可以 如下设置: 通过 0表示 AGW仅支持基本 PMIP, 通过 1表示 AGW支持基本 PMIP和 /或反向仅有链路 PMIP, 通过 2表示 AGW支持基本 PMIP或信令绑 定, 通过 3表示 AGW支持基本 PMIP, 和 /或反向链路 PMIP, 和 /或信令绑 定, 并将 4作为保留字段。 此时, 在 eBS建立绑定时, 有如下几种不同的处理情况:
( 1 ) 如果 eBS建立基本 PMIP或单个基本 PMIP, 且 eBS获取的能力 值为 0、 1、 2、 或 3 , 则代理移动 IP注册请求消息不携带绑定类型扩展;
( 2 )如果 eBS建立反向仅有的 PMIP, 且获取的能力值为 1或 3 , 则代 理移动 IP 注册请求消息中携带以下绑定类型扩展: RL Only Binding Type Extension;
( 3 )如果 eBS建立信令仅有的 PMIP, 且获取的能力值为 2或 3 , 则代 理移动 IP 注册请求消息中携带以下绑定类型扩展: Signaling Only Binding Type Extension;
( 4 )如果 eBS建立多个 PMIP, 且获取的能力值为 2或 3 , 则代理移动 IP 注册请求消息中携带以下绑定类型扩展: RL+Primary Binding Type Extension; ( 5 )如果 eBS获取的能力值为 0, 贝l eBS不在代理移动 IP注册请求消 息携带绑定类型扩展;
( 6 ) 如果 eBS获取的能力值为 1 , 且 eBS支持反向仅有链路 PMIP, 贝l eBS在^ ^理移动 IP注册请求消息携带 RL Only Binding Type Extension (只 建立反向仅有链路 PMIP )或者 RL Only+Primary Binding Type Extension (建 立多 PMIP );
( 7 )如果 eBS获取的能力值为 1 , 且 eBS不支持反向仅有链路 PMIP, 则 eBS不在代理移动 IP注册请求消息中携带绑定类型扩展; ( 8 ) 如果 eBS获取的能力值为 2 , 且 eBS支持信令仅有 PMIP, 则代 理移动 IP 注册请求消息中携带以下绑定类型扩展: RL Only Binding Type Extension;
( 9 ) 如果 eBS获取的能力值为 2 , 且 eBS不支持信令仅有 PMIP, 则 eBS不在代理移动 IP注册请求消息中携带绑定类型扩展; ( 10 ) 如果 eBS获取的能力值为 3 , 且 eBS支持反向仅有链路 PMIP, 贝l eBS 在^ ^理移动 IP 注册请求消息中携带以下绑定类型扩展: RL Only Binding Type Extension或者 RL Only+Primary Binding Type Extension;
( 11 )如果 eBS获取的能力值为 3 ,且 eBS支持信令仅有 PMIP,贝l eBS 在^ ^理移动 IP注册请求消息中携带以下绑定类型扩展: RL Only Binding Type Extension;
( 12 ) 如果 eBS获取的能力值为 3 , 且 eBS既不支持信令仅有 PMIP, 也不支持反向仅有链路 PMIP, 贝l eBS在代理移动 IP注册请求消息中不携带 绑定类型扩展。 也就是说, 为了能让 eBS获取到 AGW PMIP支持能力, 需要进行以下 步骤(优选地, 可以对应于上述情况( 1 ) 至情况 ( 12 ) 的处理): 步骤 1 , SRNC在参与 AT的鉴权过程中获取 AGW支持 PMIP绑定的 能力; 步骤 2, eBS在向 SRNC索取会话信息时, SRNC同时将 AGW的 PMIP 支持能力发送给 eBS; 步骤 3 , eBS才艮据自己的能力和 AGW的能力发送 PMIP RRQ消息以建 立相应的绑定。 针对步骤 2 ,增强现有技术中 eBS和 SRNC间消息互联网验证服 IAS ) -Session Information Response , 使其包括 AGW PMIP的能力。 在相关技术中, 该消息的定义为 IAS-Session Information Response (会 话信息响应), 消息格式如表 1所示。 表 1
Figure imgf000011_0001
为了实现本发明实施例的技术方案,本发明对会话信息响应消息中 IAS DAP Record信息单元增强在于 IAS DAP Record ( IAS DAP 己录), 该信息单 元包含了 AT连接的每个 AGW的信息。 对于每个 AGW, 如果 DAP存在, 该信息单元也包含了 DAP的相关信息( This IE contains AGW information for each AC|W to which the AT connects. For each AGW, if the DAP exists , this IE also contains information about the DAP ), 贝1 J该信元 结构可 口表 2所示。
4.2.1.18 IAS DAP Record
7 f 6 5 4 3 2 1 0 Octet j IAS IEI = [AOH] 1 I IAS信息单元标识
(MSB) ( Length = <variable> 2 J 长度 =<可变长 >
; (LSB) 3
IAS AGW Record Count = <any value> 4 IAS AGW记录计数= <任何值〉
IAS AGW Record- 1 Variable IAS AGW记录 - 1 可变 4.2.1.18 IAS DAP Record
Figure imgf000012_0001
其中, Length (长度 ): 该域包括了其之后该信息单元长度 (以字节的 个数计 X This field contains the number of octets in this IE following this field as a binary number );
IAS AGW Record Count: 该域包括了 IAS AGW记录的个数 ( This field indicates the number IAS AGW Records in this IE );
IAS AGW Record-n的编码如表 3所示: 表 3
Figure imgf000012_0002
IAS AGW记录 ( IAS AGW Record ) 的编码如表 4所示:
表 4
Figure imgf000013_0001
其中, AGW-RAN PMIP Capability ( AGW - RAN PMIP能力) 被定义 0: 支持基本 PMIP绑定 ( AGW supports Primary type of binding only AGW )
1 : AGW 支持基本 +反向链路 PMIP绑定 (AGW supports Primary + Reverse-Link types of bindings ) 2: 支持基本 +信令绑定 ( AGW supports Primary + Signaling types of bindings AGW )
3 : AGW 支持基本 +反向链路 +信令绑定 (AGW supports Primary + Reverse-Link + Signaling types of bindings )
4: 保留值 ( Other values are reserved ) 针对上述步骤 3 , eBS在建立各种 PMIP绑定时候, 发送 PMIP RRQ消 息^1携带响应的 Binding Type Extension , 具体如下:
( 1 ) 如果 eBS建立基本或者单个 PMIP绑定, 且 AGW-RAN PMIP能 力为以上任何值, 贝l PMIP RRQ消息不携带 Binding Type Extension;
( 2 ) 如果 eBS建立反向仅有的 PMIP绑定, 且 AGW-RAN PMIP能力 值为 ' 1, 或者 '3,, 贝 'J PMIP RRQ 消息中携带 'RL Only Binding Type Extension';
( 3 ) 如果 eBS建立信令仅有的 PMIP绑定, 且 AGW-RAN PMIP能力 值为 '2,, 或者 '3,, 贝l PMIP RRQ消息中携带 'Signaling Only Binding Type Extension'; ( 4 ) 如果 eBS想建立多个 PMIP绑定, 且 AGW-RAN PMIP能力值为
'2,, 或者 '3,, 贝l PMIP RRQ 消息中携带 'RL +Primary Binding Type Extension' 。 下面将结合具体实例描述本发明。 实例 1 : 初始 PMIP绑定的建立 如图 3所示, 本实例中的处理过程如下:
( 1 ) AT 执行成功的鉴权和 4吏权过程, AGW 从归属 AAA ( Home AAA-HAAA )接收到 AAA-会话标识和其他参数; AGW为 AT选择一个唯 一的随机密钥称为 PMN-AN-RK , 并由此导出 PMN-AN-RK1.AGW 将 PMN-AN-RK1 , AAA -会话标识和其他相关参数发送给 SRNC; AGW将其 支持 PMIP绑定能力也同时发送给 SRNC; ( Γ ) SRNC获取了 AGW支持 PMIP绑定能力和其他参数;
( 2 ) eBSl发送 IAS会话信息请求消息给 SRNC以获取相关会话信息;
( 3 ) 收到会话信息请求, SRNC回应以 IAS-会话信息响应消息, 该消 息包括 AGW IP地址、 LinkID、 用户名称、 AAA-会话 ID、 PMN-AN-RK 以及 AGW所支持的 PIMP绑定能力,即, AGW-RAN-PMIP-Binding-Capability 信息;
( 4 ) eBSl向 AT分配链路标识( LinkID ), 链路标识代表了 ZT创建的 用于和 IP层会话的 IP接口;
( 5 ) ZT发送数据附着点移动请求( DAP Move Request )消息给 eBS l ;
( 6 )eBS 1发送 PMIP RRQ消息给 AGW,该消息包括 NAI和 eBS 1 IP 地 址以建立初个 PMIP 隧道; 同 时 eBSl 也才艮据步骤 3 收到的 AGW-RAN-PMIP-Binding-Capability (表示 AGW支持的 PMIP绑定能力)来 确定是否携带 'Binding Type Extension 4或,及相应的扩展值,例如,如果 eBSl 和 AGW也都支持反向仅有绑定, 则携带 RL+Primary binding类型; 优选地, 可以携带参数: NAI , eBSl IP Address, GRE extension, MN-HA Authentication; ( 7 ) AGW发送 PMIP-Registration Reply消息确认相应的 PMIP隧道的 建立; 优选地, 可以携带参数: NAI, GRE Key, MN-HA Authentication;
( 8 ) eBSl发送 DAP分配给 AT;
( 9 ) eBS l发送 IPT-通知消息 ( IPT-Notification )给 SRNC通知其称为
DAP; ( 10 ) SRNC反馈 IPT-通知确认消息 ( IPT-Notification ACK );
( 11 ) AT向其上层 IP层展示链路已经建立, 上层 IP层比较当前 IP接 口和其当前的 IP接口, 如果不一样的话, 则触动 IP地址分配; ( 12 ) 完成 IP地址分配;
( 13 ) 可以在 AT和 AGW之间传递 IP数据包。 实例 2: AT路由集增加情形 如图 4所示, 在本实例中, 包括以下处理过程: ( a ) AT当前和 eBSl处于连接^ 态, SRNC在路由集中;
( b ) AT通过隧道方式将 Route Open Request消息发送到 eBS2以增加 eBS2到路由集中;
( c ) eBS2发送 IAS-Session Information Request消息给 SRNC;
( d ) SRNC回应 eBS2以 IAS-Session Information Response消息, 该消 息包括 AGW支持的 PMIP绑定能力;
( e ) eBS2发送 Route Open Accept消息给 AT;
( f) AT和 eBS l处于连接^ 态, eBS2和 SRNC也在路由集中;
( g ) AT发送 RouteMa 消息给路由集中的每个成员;
( h* ) eBS2 才艮据 AGW 的 PMIP 能力, eBS 发送 PMIP-Registration Request消息给 AGW以建立额外的数据隧道, RL Only Type Extension包括 在该消息中;
( i** ) AGW发送 PMIP-Registration Reply消息给 eBS2;
( j** )收到更新后的 Route Ma , SRNC发送 IAS-UATI Update消息给 eBS2; ( k* " eBS2发送 IAS-UATI Update Ack消息给 SRNC;
( 1 ) eBS l发送 IPT-Notification消息给 eBS2以明确其为前向服务基站 和数据附着点;
( m ) eBS2发送 IPT-Notification Ack消息给 eBS 1。 系统实施例 在本实施例中, 提供了一种 AGW绑定建立系统。 如图 5所示, 才艮据本实施例的 AGW绑定建立系统包括: SRNC 502, 用于获取 AGW所支持的 PMIP的能力, 并且在 eBS 504从 SRNC获取会话 信息时, SRNC 502将 AGW的所支持的 PMIP绑定的能力发送给 eBS 504其 中, SRNC 502可以在参与对接入终端进行的鉴权时, 获取 AGW所支持的 PMIP 邦定的能力。 另外, SRNC 502可通过能力值表示 AGW支持基本 PMIP、 反向仅有 链路 PMIP, 信令绑定中的任一个或其组合作为绑定类型扩展, 其具体表示 方式之前已经描述, 这里不再重复。 eBS 504,用于获取 AGW的所支持的 PMIP绑定的能力,并才艮据 eBS 504 本身的能力及获取的 AGW支持的 PMIP绑定的能力, 向 AGW发送代理移 动 IP注册请求消息以对 AGW建立相应的绑定。 此外, eBS 504可通过向 SRNC 502发送会话信息请求消息,并从 SRNC 502返回的会话信息响应消息获取 AGW的所支持的代理移动 IP的绑定能力。 综上所述, 借助于本发明的技术方案, 能够通过在接入网传递 AGW的
PMIP支持能力,从而实现了对 UMB网络中 eBS和 AGW之间 PMIP绑定的 建立流程的优化, 避免了不必要的信令交互。 以上所述仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本 领域的技术人员来说, 本发明可以有各种更改和变化。 凡在本发明的精神和 原则之内, 所作的任何修改、 等同替换、 改进等, 均应包含在本发明的保护 范围之内。

Claims

权 利 要 求 书
1. 一种接入网关绑定建立方法, 其特征在于, 所述方法包括:
会话参考网络控制器获取接入网关所支持的代理移动 IP绑定的能 力;
在演进基站从所述会话参考网络控制器获取会话信息时,所述会话 参考网络控制器将所述接入网关的所支持的所述代理移动 IP 绑定的能 力发送给所述演进基站;
所述演进基站获取所述接入网关的所支持的所述代理移动 IP绑定 的能力, 并才艮据所述演进基站本身的能力及获取的所述接入网关支持的 代理移动 IP绑定的能力, 向所述接入网关发送代理移动 IP注册请求消 息, 以对所述接入网关建立相应的绑定。
2. 根据权利要求 1所述的方法, 其特征在于, 所述会话参考网络控制器在 参与对接入终端进行的鉴权时, 获取所述接入网关所支持的代理移动 IP 绑定的能力。
3. 根据权利要求 1所述的方法, 其特征在于, 所述演进基站通过向所述会 话参考网络控制器发送会话信息请求消息, 并从所述会话参考网络控制 器返回的会话信息响应消息获取所述接入网关的所支持的所述代理移动 IP的绑定能力。
4. 根据权利要求 1所述的方法, 其特征在于, 通过能力值表示所述接入网 关支持基本代理移动 IP绑定、 反向仅有链路代理移动 IP绑定、 信令绑 定中的任一个或其组合作为绑定类型扩展。
5. 根据权利要求 4所述的方法, 其特征在于, 通过所述能力值表示所述接 入网关所支持的所述代理移动 IP绑定的能力的方式具体为: 通过 0表示 所述接入网关仅支持所述基本代理移动 IP绑定,通过 1表示所述接入网 关支持所述基本 «理移动 IP绑定和 /或所述反向仅有链路«理移动 IP绑 定,通过 2表示所述接入网关支持所述基本代理移动 IP绑定或所述信令 绑定, 通过 3表示所述接入网关支持所述基本代理移动 IP绑定、 和 /或 所述反向链路代理移动 IP绑定、 和 /或所述信令绑定, 并将 4作为保留 字段。
6. 4艮据权利要求 5所述的方法, 其特征在于, 在所述演进基站建立所述绑 定时, 进一步包括以下之一:
如果所述演进基站建立所述基本代理移动 IP绑定或单个基本代理 移动 IP绑定, 且所述演进基站获取的所述能力值为 0、 1、 2、 或 3 , 则 所述代理移动 IP注册请求消息不携带绑定类型扩展;
如果所述演进基站建立所述反向仅有的代理移动 IP绑定, 且获取 的所述能力值为 1或 3 , 则所述代理移动 IP注册请求消息中携带以下绑 定类型扩展: RL Only Binding Type Extension;
如果所述演进基站建立所述信令仅有的代理移动 IP绑定, 且获取 的所述能力值为 2或 3 , 则所述代理移动 IP注册请求消息中携带以下绑 定类型扩展: Signaling Only Binding Type Extension;
如果演进基站建立多个代理移动 IP绑定,且获取的所述能力值为 2 或 3 , 则所述代理移动 IP 注册请求消息中携带以下绑定类型扩展: RL+Primary Binding Type Extension。
7. 一种接入网关绑定建立系统, 其特征在于, 所述系统包括:
会话参考网络控制器, 用于获取接入网关所支持的代理移动 IP绑 定的能力,并且在演进基站从所述会话参考网络控制器获取会话信息时, 将所述接入网关的所支持的所述代理移动 IP 绑定的能力发送给所述演 进基站;
所述演进基站,用于获取所述接入网关的所支持的所述代理移动 IP 绑定的能力, 并才艮据所述演进基站本身的能力及获取的所述接入网关支 持的代理移动 IP绑定的能力向所述接入网关发送代理移动 IP注册请求 消息以对所述接入网关建立相应的绑定。
8. 根据权利要求 7所述的系统, 其特征在于, 所述会话参考网络控制器用 于在参与对接入终端进行的鉴权时, 获取所述接入网关所支持的代理移 动 IP绑定的能力。
9. 根据权利要求 7所述的系统, 其特征在于, 所述演进基站用于通过向所 述会话参考网络控制器发送会话信息请求消息, 并从所述会话参考网络 控制器返回的会话信息响应消息获取所述接入网关的所支持的所述代理 移动 IP的绑定能力。 才艮据权利要求 7所述的系统, 其特征在于, 所述会话参考网络控制器用 于通过能力值表示所述接入网关支持基本代理移动 IP绑定、反向仅有链 路代理移动 IP绑定、 信令绑定中的任一个或其组合作为绑定类型扩展。
PCT/CN2009/070148 2008-05-12 2009-01-14 接入网关绑定建立方法和系统 WO2009137994A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200810096974.9 2008-05-12
CN2008100969749A CN101582828B (zh) 2008-05-12 2008-05-12 接入网关绑定建立方法和系统

Publications (1)

Publication Number Publication Date
WO2009137994A1 true WO2009137994A1 (zh) 2009-11-19

Family

ID=41318350

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/070148 WO2009137994A1 (zh) 2008-05-12 2009-01-14 接入网关绑定建立方法和系统

Country Status (2)

Country Link
CN (1) CN101582828B (zh)
WO (1) WO2009137994A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030214958A1 (en) * 2002-04-12 2003-11-20 Lila Madour Linking of bearer and control for a multimedia session
CN101043727A (zh) * 2006-03-24 2007-09-26 华为技术有限公司 一种演进网络中目标优选三层快速切换的实现方法
CN101072425A (zh) * 2006-05-11 2007-11-14 华为技术有限公司 一种无线演进网络中的切换方法及系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030214958A1 (en) * 2002-04-12 2003-11-20 Lila Madour Linking of bearer and control for a multimedia session
CN101043727A (zh) * 2006-03-24 2007-09-26 华为技术有限公司 一种演进网络中目标优选三层快速切换的实现方法
CN101072425A (zh) * 2006-05-11 2007-11-14 华为技术有限公司 一种无线演进网络中的切换方法及系统

Also Published As

Publication number Publication date
CN101582828B (zh) 2011-12-07
CN101582828A (zh) 2009-11-18

Similar Documents

Publication Publication Date Title
JP4440933B2 (ja) データサービス起動ネットワークのための方法と装置
US8582529B2 (en) Resource management for mobility between different wireless communications architectures
RU2409907C2 (ru) Объединение интернет-протокола и сотовой мобильности
JP2010213357A (ja) 2つの無線ネットワークのインターフェースを確立する方法
JP2005537767A (ja) アクセスネットワークとホームネットワークとの間でセッション速度および状態情報を転送する方法およびシステム
WO2008151544A1 (fr) Procédé, appareil et système pour établir une connexion de support
WO2007147345A1 (fr) Procédé de sélection d&#39;entité plan utilisateur du côté réseau et d&#39;entité plan contrôle
US20030208601A1 (en) System and method for session control in a mobile internet protocol network
KR20060074037A (ko) Wlan-gprs 연동 망에서 sip를 이용한 등록되지않은 가입자의 착신 처리 방법
WO2009006848A1 (fr) Procédé de commutation de réseau d&#39;accès, dispositif de gestion d&#39;ancrage, et dispositif d&#39;accès mobile
US20080225793A1 (en) Method and system for performing handoff in wireless networks
WO2007112690A1 (fr) Procédé et système de mise à jour de route dans un système de communications mobiles
US6400950B1 (en) System and method for de-registration of multiple H.323 end points from a H.323 gatekeeper
JP2007520097A (ja) 圧縮されたメッセージを送信するためのシステム及び方法
CA2522846C (en) Methods and apparatuses for optimizing resource management in cdma2000 wireless ip networks
WO2011011945A1 (zh) 消息发送方法及通用无线分组业务服务支持节点
WO2010139285A1 (zh) 一种信息同步方法及通讯系统以及相关设备
WO2009097779A1 (zh) 一种接入sae核心网的方法、系统及装置
WO2008151481A1 (fr) Procédé pour commander de manière centralisée le service d&#39;implémentation d&#39;appel de terminal dans un sous-système de réseau central multimédia ip
JP4591263B2 (ja) 通信制御装置、及び、通信システム
WO2011020418A1 (zh) 终端转为连接态时更改服务网关的连接激活方法及系统
JP4477239B2 (ja) 共通ipアドレス付きの移動端末および無線装置
WO2009137994A1 (zh) 接入网关绑定建立方法和系统
WO2010124644A1 (zh) 紧急业务实现方法、系统和网络设备
WO2008138264A1 (fr) Controleur de reseau et procede de gestion d&#39;interface utilisateur

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: 09745378

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: 09745378

Country of ref document: EP

Kind code of ref document: A1