WO2007006224A1 - Procédé et système destinés à réaliser la translation de l’interface r3 - Google Patents

Procédé et système destinés à réaliser la translation de l’interface r3 Download PDF

Info

Publication number
WO2007006224A1
WO2007006224A1 PCT/CN2006/001620 CN2006001620W WO2007006224A1 WO 2007006224 A1 WO2007006224 A1 WO 2007006224A1 CN 2006001620 W CN2006001620 W CN 2006001620W WO 2007006224 A1 WO2007006224 A1 WO 2007006224A1
Authority
WO
WIPO (PCT)
Prior art keywords
interface
asn
mobile
information
migration
Prior art date
Application number
PCT/CN2006/001620
Other languages
English (en)
Chinese (zh)
Inventor
Jianjun Wu
Yong Xie
Original Assignee
Huawei Technologies Co., Ltd.
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 Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2007006224A1 publication Critical patent/WO2007006224A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices

Definitions

  • the present invention relates to the field of wireless communication technologies, and more particularly to a method and system for implementing R3 interface migration. Background of the invention
  • IEEE 802.16 defines a wireless metropolitan area network standard for fixed broadband wireless access (BWA), which includes IEEE 802.16a, IEEE 802.16d, and IEEE 802.16e.
  • WiMAX is the world's microwave access interoperability industry organization, which aims to promote the global promotion and application of the IEEE 802.16 series air interface protocol.
  • WiMAX provides an end-to-end reference model that includes mobile/user stations (MSS/SS), access service network (ASN), and connection service network (CSN).
  • MSS/SS is a user equipment, and the user accesses the WiMAX network by using the device.
  • the ASN is used to provide a set of network functions for wireless access services for WiMAX terminals.
  • the ASN includes a base station (BS) and an ASN gateway (ASN GW).
  • the ASN mainly provides connection with the MSS/SS, radio resource management, measurement, and power through the BS. Control, compression and encryption of air interface data; and provide proxy (proxy) function for authentication, authorization, and accounting of MSS/SS through ASN GW, support NSP network discovery and selection functions, and provide IP addresses such as IP addresses for MSS/SS L3 information relay function such as allocation;
  • ASN can also provide other functions such as ASN internal handover, MSS/SS paging and location management, ASN-CSN tunnel management and visit location registration.
  • CSN is similar to the core network in mobile communication systems and is used to provide IP connection services for WiMAX terminals. It mainly provides IP address allocation, Internet access, AAA proxy or server functions of MSS/SS, and also provides user-based authorization control. ASN to CSN tunnel, WiMAX User billing and billing between operators.
  • the ASN GW in the figure is the same device as the external agent (FA).
  • the MSS/SS is originally located in the cell of the BS1, and the MSS/SS interacts with the home agent (HA) in the CSN through the BS1 and the ASN GW1. If the MSS/SS moves to the cell under the BS2, the MSS/SS needs to pass.
  • BS2 ASN GW2 interacts with HA. It can be seen that the inter-cell handover of the MSS/SS results in air interface switching, R6 interface switching between the ASN GW and the BS, and the R3 interface between the HA and the FA is also migrated.
  • the MSS/SS movement may be the active movement of the MSS/SS due to user movement; or the MSS passive movement caused by the optimization of the network resources, that is, the network switches the MSS/SS to other resources based on resource optimization. Community.
  • network resource optimization does not necessarily lead to inter-cell handover of MSS/SS. That is to say, resource optimization does not necessarily change the R6 interface between air interface and ASN GW and BS, but resource optimization usually needs to change FA and HA.
  • the channel between the two that is, the migration of the R3 interface between the FA and the HA. There is currently no migration plan for this situation.
  • the main problem to be solved by the present invention is to provide a method and system for implementing R3 interface migration, so that the WiMAX network can implement R3 interface migration without causing MSS/SS inter-cell handover.
  • the present invention provides a method for implementing R3 interface migration, which is applicable to a WiMAX network, and the method includes:
  • Access service network gateway ASN GW determines to perform R3 interface on the terminal of its own service The migration, triggering the mobile IP client corresponding to the terminal to initiate registration;
  • the mobile IP client module initiates registration based on the target R3 interface determined by the ASN GW for R3 interface migration.
  • the mobile IP client that triggers the terminal initiates the registration as:
  • the ASN GW sends a message including the service information to be migrated and the target R3 interface information to the mobile IP client module of the terminal that needs to perform the R3 interface migration. Requesting to perform R3 interface migration; then, in step b, the mobile IP client initiates registration according to the received request.
  • the request to initiate registration in step b is:
  • the mobile IP client module After receiving the request message, the mobile IP client module sends a registration request to the home agent HA.
  • the service information that needs to be migrated may be: information of a terminal that needs to perform R3 interface migration; or: information of a part of the session in the terminal that needs to perform R3 interface migration.
  • the step a is performed.
  • the ASN GW determines the service information required for the R3 interface to be migrated according to the QoS requirements of the current service of the terminal and/or whether the terminal has an R4 interface connection.
  • the step b further comprises:
  • the MIP client module returns a response message of successful migration to the ASN GW;
  • the ASN GW After receiving the response message of the successful migration, the ASN GW releases the data path information of the original R3 interface for migration.
  • the ASN GW may be an ASN GW corresponding to the original R3 interface or an ASN GW corresponding to the target R3 interface.
  • the step b further includes: the ASN GW corresponding to the original R3 interface, the migrated service related information, the anchor data channel function information, and/or the anchor service flow authorization information, and / or anchor the dynamic host configuration protocol proxy or relay information, and / or anchor accounting client information, transfer to the ASN GW corresponding to the target R3 interface.
  • the ASN GW corresponding to the target R3 interface sends a message to the ASN GW corresponding to the original R3 interface to request the information related to the migrated service;
  • the ASN GW corresponding to the original R3 interface actively sends a message carrying the information related to the migrated service to the ASN GW corresponding to the target 3 interface.
  • the mobile IP client module is a proxy mobile IP mode client
  • the mobile IP client module is the terminal, and the ASN GW notifies the serving ASN GW to trigger the corresponding mobile foreign agent or the mobile access router to send a broadcast message to the terminal.
  • the present invention also provides a system for implementing R3 interface migration, which is applicable to a WiMAX network, and the system includes: an ASN GW and a mobile IP client module, where
  • the ASN GW is configured to perform R3 interface migration on the terminal that serves the service, and trigger the mobile IP client corresponding to the terminal to initiate registration.
  • the mobile IP client module is used to initiate registration of the R3 interface based on the target R interface determined by the ASN GW.
  • the system can further include:
  • the HA is configured to establish, according to the registration request from the mobile IP client module, the target R3 interface, a data path between the terminal corresponding to the mobile IP client and the HA based on the target R3 interface in the registration request.
  • the HA may be further configured to notify the mobile IP client of information indicating that the data path is successful; the mobile IP client module is further configured to send, according to information about success of establishing a data path from the HA, to the ASN GW. Information that the R3 interface migrates successfully; then the ASN GW is further used, according to the R3 from the mobile IP client module The information about successful interface migration releases the corresponding data path and context information.
  • the ASN GW is an ASN GW corresponding to the original R3 interface, or an ASN GW corresponding to the target R3 interface.
  • the solution of the present invention determines that the ASN GW determines to perform R3 interface migration on the terminal that serves the service, and triggers the mobile IP client corresponding to the terminal to initiate registration; the mobile IP client module initiates registration based on the target R3 interface determined by the ASN GW.
  • the R3 interface migration makes up for the shortcomings of the prior art that the R3 interface can only be migrated when the MSS/SS performs inter-cell handover.
  • the ASN GW determines that its own resource cannot meet the service requirements of its own service terminal, or initiates the R3 interface migration in the presence of the R4 interface, resource optimization is implemented.
  • FIG. 1 is an effect diagram of current MSS/SS-based inter-cell handover triggering R3 interface migration
  • FIG. 2 is a flowchart of implementation of the scheme of the present invention
  • FIG. 3 is a timing diagram of a message flow according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of the R3 interface migration effect of the solution of the present invention
  • FIG. 5 is a system structural diagram of the solution of the present invention.
  • Mode for Carrying Out the Invention The solution of the present invention mainly implements interface migration of R3 by the ASN GW when the terminal (MSS/SS) does not perform cell handover.
  • the solution of the present invention will be made below with reference to the accompanying drawings and specific embodiments. Further details.
  • the entity that specifically performs the R3 interface migration function in the ASN GW may be a resource management (RM) module that manages resources.
  • RM resource management
  • FIG. 2 The implementation process of the solution of the present invention is shown in FIG. 2, which corresponds to the following steps:
  • Step 201 Predefine an R3 handover request message (R3_Relocate.request) for requesting to migrate the R3 interface, and an R3 handover response message (R3_Relocate.reply) for returning the migration result.
  • R3_Relocate.request an R3 handover request message
  • R3_Relocate.reply an R3 handover response message
  • Step 202 The RM module triggers the R3 interface migration when the QoS module determines that its own resources cannot be met according to the QoS policy of the user and the service flow (user/service flow), or the QoS requirement of the user/service flow cannot be guaranteed. And selecting the MSS/SS for migrating the ASN GW service corresponding to the RM module, and determining the R3 interface corresponding to the target FA after the migration, and then sending the R3_Rdocate.request message to the mobile IP that completes the MIP function of the client specified by the MIP protocol.
  • Client (MIP client) module Client (MIP client) module.
  • the above MIP Client is PMIP Client, then the following P Client is PMIP Cllient.
  • the MIP client is the MSS/SS, and the RM module sends a broadcast message to the MSS/SS through the corresponding mobile foreign agent or mobile access router.
  • the above process of determining the MSS/SS to be migrated is mainly determined according to the QoS requirements of the current service or session of the MSS/SS, or whether the MSS/SS has an R4 connection. For example, when the network is congested, the low-priority service or session is migrated to ensure the high-priority service or session; when the MSS/SS has the R4 interface connection, the MSS/SS anchor data channel function is migrated to the current service (Serving) ASN GW, to reduce the number of nodes through which the service passes, and improve QoS.
  • the current service Server
  • the above determination of the target FA may be the FA in the lightly loaded ASN GW in the network, or may be the FA in the current Serving ASN GW when there is an R4 interface connection.
  • the RM module that triggers the R3 interface migration may be, for example, a data channel function/foreign agent (DPF/FA) entity.
  • the RM module may be an RM module located in the anchor ASN GW connected to the HA, when anchoring the ASN GW.
  • the RM module in the RM module triggers the R3 interface migration when it is confirmed that the ASN GW cannot meet the QoS requirements of the user/service flow; or the RM module in the service gateway device corresponding to the target R3 interface when the R4 interface exists, when the service gateway device
  • the internal RM module triggers the R3 interface migration when it confirms that the current anchor ASN GW cannot meet the QoS requirements of the user/service flow.
  • the RM module may also be located in a separate device capable of acquiring the anchor ASN GW or the serving ASN GW resource status.
  • the R3_Relocate.request message includes the MSS/SS information and the determined information of the R3 interface.
  • the R3_Relocate.request message may also include a transaction identifier for matching between messages in a subsequent interaction.
  • the information of the determined R3 interface is: Address information of the target FA after the migration.
  • the RM selects the migrated MSS/SS, all the sessions in the MSS/SS can be migrated, or a part of the sessions in the MSS/SS can be migrated according to the QoS of the session. If it is the former case, the MSS/SS information contained in the R3_Relocate.request message sent by the RM module should be: MSS/SS identification information; if it is the latter case, the MSS/SS information should be It is: the identification information of the MSS/SS, and the information of the session that needs to be migrated, and the session information is usually: the ID of the session, the IP address, and the information of the HA that allocates the IP address.
  • Step 203 After receiving the R3_Relocate.request message, the P client module sends the registration request to the HA.
  • the MSS/SS information and R3 interface information are also included in the registration request sent.
  • the registration request can be forwarded by the FA.
  • the HA returns a response message, it can also be transferred by the FA. hair.
  • the MIP client module may also return a response message indicating that the migration process is being performed to the RM module.
  • the response message may be the R3_Relocate.reply message preset in step 201, but the busy flag needs to be set in the message to indicate that the migration process is currently in progress.
  • Step 204 After receiving the registration request, the HA establishes a data path between the MSS/SS and the local HA based on the R3 interface, and creates a context of the data path, and then sends a corresponding registration response to the MIP client module. .
  • the registration response message should carry the context information of the data path; otherwise, the response message should carry the information of the establishment failure.
  • Step 205 After receiving the registration response, the MIP client module returns a corresponding R3_Relocate.reply message to the RM module.
  • the R3_Relocate.reply message should carry the context information of the data path; otherwise, the R3_Relocate.reply message should carry the information of the establishment failure.
  • the information from the ASN GW corresponding to the original R3 interface to the ASN GW corresponding to the target 3 interface includes migration.
  • MSS/SS or migrated sessions anchor DPF information, and/or anchor service flow authorization (SFA) information, and/or anchor Dynamic Host Configuration Protocol (DHCP) proxy or relay information, and/or anchors Set billing client information.
  • the access service network gateway corresponding to the target R3 interface sends a message to the information related to the service that the access service network gateway corresponding to the original R3 interface seeks to migrate; or the access service network gateway corresponding to the original R3 interface sends the information actively.
  • the message carrying the information related to the migrated service is sent to the access service network gateway corresponding to the target R3 interface.
  • Step 206 After receiving the R3_Relocate.reply message, the RM module if the message If the Context information of the data path is carried, the migration is successful. After the migration is successful, the subsequent data packets related to the MSS/SS are forwarded to the ASN GW corresponding to the target R3 interface.
  • the RM module can directly release the corresponding data path and context information of the R3 interface corresponding to the original FA; if only the MSS/SS is migrated In some sessions, the RM module cannot directly release the data path and context, and only the information of the session can be deleted from the context.
  • the migration of the R3 interface can be realized based on resource optimization.
  • the RM module may directly send the message to the internal access service network mobility management (Intra ASN MM) module, The Intra ASN MM module forwards the message to the MIP client module.
  • the MIP client module returns the R3_Relocate. reply message, it can also be transferred through the Intra ASN MM module.
  • the message flow sequence of the R3 interface migration based on the Intra ASN MM module transit is shown in FIG. 3 , where the FA and the ASN GW are located in the same device, and the MP client module and the Authenticator are located in the same device, because FIG. 2
  • the message flow has been clearly described and will not be described here.
  • the FA and the ASN GW are located in the same device, and all sessions in the MSS/SS need to be migrated.
  • the MSS/SS is initially connected to the HA through the BS1, the ASN GW2, and the ASN GW1, that is, the data path corresponding to the R6, R4, and R3 needs to be interacted with the HA.
  • the ASN GW1 is the serving gateway, that is, the serving FA.
  • the RM determines that the MSS/SS needs to be migrated according to the resource optimization, it is determined that the ASN GW2 is the target gateway, that is, the target FA.
  • the original R3 interface between the ASN GW1 and the HA is migrated to the ASN.
  • GW2 R3 interface with HA It can be seen that, based on the solution of the present invention, the data forwarding of the R4 interface in FIG. 4 is terminated, the R3 interface is redirected, the transmission route of the service is optimized, and the load of the network is adjusted.
  • the ASN GW and the MIP client module of the present invention constitute a system for implementing the R3 interface migration.
  • the specific functions of the ASN GW can be performed by the RM module in the ASN GW.
  • HA may be included in the system of the present invention, as shown in FIG.
  • the functions implemented by the various components in Figure 5 are as described above, and the functions implemented by these components are now briefly described:
  • the RM module is configured to determine the MSS/SS to be migrated, determine the R3 interface corresponding to the target FA after the migration, and send an R3 handover request message to the MlP client module according to the determined MSS/SS and R3 interfaces, and according to the MIP.
  • the response message returned by the client module confirms that the data path based on the target R3 interface and the corresponding context are maintained after the migration is successful.
  • the RM module can be further used to: when all the session information in the MSS/SS needs to perform the R3 interface migration, the data path and the context information corresponding to the R3 interface of the original FA are placed; the partial session information needs to be in the MSS/SS.
  • the information of the part of the session is deleted from the context information of the corresponding data path of the original FA R3 interface.
  • the RM module determines the MSS/SS to be migrated according to the resource policy of the RM, and the RM module can be replaced with the ASN GW, and can be the ASN GW corresponding to the original R3 interface, or the ASN corresponding to the target R3 interface. GW.
  • the MIP client module is configured to send a registration request including the MSS/SS information and the R3 interface information to the HA, and send the registration response returned by the HA to the RM module.
  • the MIP client module may be further configured to, after receiving the R3 handover request message, return a response message to the RM module indicating that the module is undergoing migration processing.
  • An HA configured to establish, according to the registration request, a data path of the R3 interface sent by the MSS/SS and the HA based on the registration request, create a context of the data path, and construct the data path
  • the context information of the data path is sent to the MIP clien by registering the response.
  • the system may further include: an Intra ASN MM module, configured to relay messages between the RM module and the MIP client module. It may further include: FA, for transiting HA and

Abstract

La présente invention concerne un procédé destiné à réaliser la translation de l’interface R3, qui est appliqué au réseau WiMAX de communication globale d’accès micro-ondes et qui comprend : a. la passerelle de réseau de service d’accès ASN GW détermine la translation de l’interface R3 pour le terminal qu’elle sert et déclenche le client IP mobile correspondant au terminal pour enregistrement ; b. le module du client IP mobile demande l’enregistrement sur la base de l’interface cible R3 déterminée par le ASN GW, de manière à translater l’interface R3. La présente invention fournit également un système de réalisation de la translation de l’interface R3 et le programme relatif à cette même translation. Le programme résout le problème existant dans l’art antérieur selon lequel la translation de l’interface R3 n’est réalisée que dans le cas où MSS/SS provoque le transfert de la cellule.
PCT/CN2006/001620 2005-07-09 2006-07-10 Procédé et système destinés à réaliser la translation de l’interface r3 WO2007006224A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200510080898.9 2005-07-09
CNB2005100808989A CN100455111C (zh) 2005-07-09 2005-07-09 一种基于资源优化实现r3接口迁移的方法及系统

Publications (1)

Publication Number Publication Date
WO2007006224A1 true WO2007006224A1 (fr) 2007-01-18

Family

ID=36806077

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/001620 WO2007006224A1 (fr) 2005-07-09 2006-07-10 Procédé et système destinés à réaliser la translation de l’interface r3

Country Status (2)

Country Link
CN (1) CN100455111C (fr)
WO (1) WO2007006224A1 (fr)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100450291C (zh) * 2005-07-11 2009-01-07 华为技术有限公司 一种建立接口链路的方法
CN101106491A (zh) * 2006-07-11 2008-01-16 华为技术有限公司 微波接入全球互通网络中r3接口的迁移方法及其系统
CN101542978B (zh) * 2007-02-20 2011-06-15 华为技术有限公司 利用授权令牌进行WiMAX外地代理重定位的方法和系统
CN101222767B (zh) * 2008-01-23 2011-01-05 中兴通讯股份有限公司 一种移动ip业务基于流的服务质量实现方法及系统
CN101784072B (zh) * 2009-01-16 2012-07-04 华为技术有限公司 检测数据通道通畅性的方法、装置及系统
CN102196503B (zh) * 2011-06-28 2014-04-16 哈尔滨工程大学 面向服务质量保障的认知网络服务迁移方法
CN112190951B (zh) * 2020-10-28 2024-02-09 网易（杭州）网络有限公司 运营数据迁移方法、装置、设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1468474A (zh) * 2001-12-28 2004-01-14 ƽ 用于在移动ip中实现网络地址翻译穿越的方法和装置
US6744729B2 (en) * 2001-08-17 2004-06-01 Interactive Sapience Corp. Intelligent fabric
US20050025134A1 (en) * 1999-05-03 2005-02-03 Cisco Technology, Inc. Packet-switched telephony with circuit-switched backup
EP1530330A2 (fr) * 2003-11-04 2005-05-11 Alcatel Chemins protégés en utilisant des chemins de reroutage DBR

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI108832B (fi) * 1999-03-09 2002-03-28 Nokia Corp IP-reitityksen optimointi accessverkossa
KR100520141B1 (ko) * 2000-10-26 2005-10-10 삼성전자주식회사 이동통신 시스템에서 고정 주소를 가지는 이동단말의 핸드오버 방법
CN1184763C (zh) * 2001-12-05 2005-01-12 华为技术有限公司 Cdma系统中传输资源优化的方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050025134A1 (en) * 1999-05-03 2005-02-03 Cisco Technology, Inc. Packet-switched telephony with circuit-switched backup
US6744729B2 (en) * 2001-08-17 2004-06-01 Interactive Sapience Corp. Intelligent fabric
CN1468474A (zh) * 2001-12-28 2004-01-14 ƽ 用于在移动ip中实现网络地址翻译穿越的方法和装置
EP1530330A2 (fr) * 2003-11-04 2005-05-11 Alcatel Chemins protégés en utilisant des chemins de reroutage DBR

Also Published As

Publication number Publication date
CN100455111C (zh) 2009-01-21
CN1794869A (zh) 2006-06-28

Similar Documents

Publication Publication Date Title
JP5989868B2 (ja) 第２のサービスドメインにおけるホームエージェントでの第１のサービスドメインに属する移動局のサービスの固定
JP5547835B2 (ja) 移動端末のスリープ状態およびサービスの起動
WO2007006227A1 (fr) Procédé et système de négociation destinés à l’établissement de chemins de données d’interface
US8914005B2 (en) Method and system for network logout of a mobile station in idle mode
US20130324125A1 (en) Non-3gpp to 3gpp network handover optimizations
US20020068565A1 (en) New session or handoff methods in wireless networks
TW200939717A (en) Wireless communication method and system for implementing media independent handover between technologically diversified access networks
WO2008052467A1 (fr) Procédé et système de transfert entre systèmes d'accès hétérogènes
JP2007536787A (ja) Ｉｐアドレス設定の遅延によるハンドオーバー実行方法
US8045522B2 (en) Method and system for performing handoff in wireless networks
WO2007051426A1 (fr) Procede et systeme d’affectation de sfid destine a l’interoperabilite mondiale de l’acces microonde
US20090052398A1 (en) Method of performing a handover
MX2011001801A (es) Metodo para transferencia en una red inalambrica heterogenea.
WO2008119296A1 (fr) Procédé et dispositif permettant de réaliser la négociation du protocole de gestion de la mobilité
WO2009021442A1 (fr) Procédé et système pour maintenir la communication de schéma de compression d'en-tête robuste en continu
WO2007006224A1 (fr) Procédé et système destinés à réaliser la translation de l’interface r3
KR102017167B1 (ko) 무선 통신 시스템에서 데이터 트래픽 분산을 위한 방법 및 장치
WO2007112690A1 (fr) Procédé et système de mise à jour de route dans un système de communications mobiles
WO2008009230A1 (fr) Procédé et système de traitement du déplacement de l'interface r3 dans un réseau d'interopérabilité mondiale pour l'accès micro-ondes
WO2011020418A1 (fr) Procédé d'activation de connexion pour changer une passerelle de desserte tandis qu'un terminal est converti à un état de connexion, et système correspondant
WO2011157100A1 (fr) Procédé et système de mise en cache de données
US20220345885A1 (en) User equipment (ue)
WO2007109995A1 (fr) Procédé permettant à un terminal de quitter un réseau et système de communication mobile
WO2012068935A1 (fr) Procédé de translation de passerelle et passerelle de dérivation source
WO2007033558A1 (fr) Procede et dispositif d'annulation du transfert dans un reseau a acces sans fil

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

WWW Wipo information: withdrawn in national office

Country of ref document: DE

122 Ep: pct application non-entry in european phase

Ref document number: 06753128

Country of ref document: EP

Kind code of ref document: A1