WO2003032668A1 - Procede et systeme pour transferts dans un reseau de service general de radiocommunication en mode paquet (gprs) avec des noeuds prenant en charge differentes versions internet - Google Patents

Procede et systeme pour transferts dans un reseau de service general de radiocommunication en mode paquet (gprs) avec des noeuds prenant en charge differentes versions internet Download PDF

Info

Publication number
WO2003032668A1
WO2003032668A1 PCT/EP2001/011525 EP0111525W WO03032668A1 WO 2003032668 A1 WO2003032668 A1 WO 2003032668A1 EP 0111525 W EP0111525 W EP 0111525W WO 03032668 A1 WO03032668 A1 WO 03032668A1
Authority
WO
WIPO (PCT)
Prior art keywords
address information
network node
network
sgsn
connection
Prior art date
Application number
PCT/EP2001/011525
Other languages
English (en)
Inventor
Serge Haumont
Original Assignee
Nokia Corporation
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 Nokia Corporation filed Critical Nokia Corporation
Priority to PCT/EP2001/011525 priority Critical patent/WO2003032668A1/fr
Priority to KR1020047004623A priority patent/KR100693975B1/ko
Priority to CNB028196082A priority patent/CN100542165C/zh
Priority to DE60216791T priority patent/DE60216791T2/de
Priority to RU2004110040/09A priority patent/RU2273104C2/ru
Priority to EP02772680A priority patent/EP1436964B1/fr
Priority to US10/491,664 priority patent/US7818453B2/en
Priority to CA002462701A priority patent/CA2462701A1/fr
Priority to CN2009101268721A priority patent/CN101511081B/zh
Priority to PCT/IB2002/004079 priority patent/WO2003032604A1/fr
Priority to KR1020067023436A priority patent/KR20060135946A/ko
Priority to AT02772680T priority patent/ATE348476T1/de
Priority to PL02369412A priority patent/PL369412A1/xx
Priority to JP2003535437A priority patent/JP3834036B2/ja
Publication of WO2003032668A1 publication Critical patent/WO2003032668A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/167—Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/30—Network architectures or network communication protocols for network security for supporting lawful interception, monitoring or retaining of communications or communication related information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • the present invention relates to a method, system and network element for providing an address transition, such as a transition from an IPv4 (Internet Protocol ver- sion 4) address to an IPv6 address, between a first network node and a second network node of a cellular network, e.g. a GPRS (General Packet Radio Services) network.
  • IPv4 Internet Protocol ver- sion 4
  • IPv6 IPv6 address
  • UMTS Universal Mobile Telecommunications System
  • 3G Third Generation
  • GSM Third Generation
  • TDMA Time Division Multiple Access
  • the goal of the GPRS system is to provide global layer 2 connectivity from a cellular mobile terminal (MT, sometimes also referred to as mobile station (MS) or user equipment (UE)) using 2G or 3G radio technology (e.g. GSM, American
  • TDMA Time Division Multiple Access
  • UMTS Universal Mobile Telecommunications
  • GERAN GSM/EDGE Radio Access Network
  • GPRS can support various layer 3 protocols (e.g. IPv4; IPv6; PPP (Point-to-Point Protocol)).
  • IPv4 IPv4
  • IPv6 IPv6
  • PPP Point-to-Point Protocol
  • the main nodes of a GPRS network are SGSN (Serving GPRS Support Node) and GGSN (Gateway GPRS Support Node).
  • SGSNs are the nodes serving the MT. Each SGSN supports GPRS for GSM and/or UMTS.
  • GGSNs are the node handling the interworking with PDNs (Packet Data Networks). Signaling and data are exchanged between SGSN and GGSN or SGSN and SGSN using the GTP (GPRS Tunneling Protocol) protocol.
  • GTP protocol handles mobility, and creation, modification and deletion of GTP tunnels, as well as transfer of user data between GSNs.
  • GTP allows multi-protocol packets to be tunneled between GSNs and between an SGSN and the UMTS Terrestrial Radio Access Network (UTRAN, not shown) through which a connection to the concerned MT is established.
  • Other systems components need not be aware of the GTP.
  • two IP addresses are used for a single tunnel, one for the GTP control message (i.e. signaling) and one for the GTP user packet (i.e. carrying user data).
  • the SGSN establishes a mobility management (MM) context containing information pertaining to e.g. mobility and security for the concerned MT.
  • MM mobility management
  • the SGSN establishes a PDP context, to be used for routing purposes, with the GGSN the subscriber will be using.
  • a GPRS attached mo- bile terminal can be assigned either a static or dynamic IP address (referred to also as PDP address).
  • the static address is assigned by the Home Public Land Mobile Network (HPLMN) operator at the time of subscription.
  • the dynamic IP address can be allocated by a GGSN (Gateway GPRS Support Node) of either the HPLMN or the visited PLMN (VPLMN) operator at PDP (Packet Date Protocol) context activation time.
  • the GGSN implements the forwarding of IP packets from a GTP (GPRS Tunneling Protocol) tunnel to a packet data network (PDN) and vice versa.
  • GTP GPRS Tunneling Protocol
  • PDN packet data network
  • the Intra-PLMN backbone network is a private IP network intended for packet domain data and signalling within a PLMN only, while the Inter-PLMN backbone is used for roaming from one PLMN to another (via Border Gateways).
  • Serving GPRS Support Nodes (SGSNs) and GGSNs use the Intra-PLMN backbone to exchange GPRS domain data and signalling.
  • SGSNs Serving GPRS Support Nodes
  • GGSNs use the Intra-PLMN backbone to exchange GPRS domain data and signalling.
  • both the Intra-PLMN backbone of the home and visited networks are used in addition to the Inter-PLMN backbone.
  • a subscriber When a subscriber is roaming to another PLMN, i.e. a VPLMN, the user needs to first attach to the network.
  • the MT informs the Serving SGSN of its intention to connect to the network by giving information about its identity, capability and location.
  • the SGSN checks the MT's identity and performs an authentication procedure in order to secure the transmission path.
  • the attachment is completed after the SGSN has received roaming subscriber data from the Home Location Register (HLR) of the subscriber's HPLMN and finished a location update procedure.
  • HLR Home Location Register
  • the MT sends an 'Activate PDP context' request, in which the Access Point Name (APN) is a reference to the GGSN Access Point (AP) to be used in either the home or visited PLMN.
  • the SGSN selects the GGSN based on a PDP context subscription record and sends the context data to a selected GGSN.
  • the GGSN then routes the packets to the appropriate Packet Data Networks (PDN).
  • PDN Packet Data Networks
  • the home network GGSN can be used via the Inter-PLMN backbone and BGs.
  • the home GGSN then routes the packets to their destination.
  • a visited domain GGSN can be used for routing the packets from the VPLMN to their destination directly through a packet data network (PDN), such as the public Internet.
  • PDN packet data network
  • the corresponding IP address is referred to as PDP address or user address;
  • the corresponding IP addresses are the node IP addresses used to exchange GTP packets between GSNs. These IP addresses might also be used for network operation such as charging or O&M.
  • the GPRS backbone nodes of the second (2G) and third (3G) generation may optionally use an IPv6 based addressing for network addresses.
  • IPv6 based addressing for network addresses.
  • existing specifications allowing the use of IPv6 addresses do not define how to maintain backward compatibility with IPv4 based nodes.
  • An SGSN should know in advance that the GGSN selected supports IPv6 addresses before inserting an IPv6 address e.g. in a create PDP context request message.
  • the old point of connection e.g. old SGSN
  • the new point of connection e.g. new SGSN both first and second address, in order to allow the new point of connection to re-establish the connection towards the other end of the connection (GGSN), even if it can only communicate using one of the 2 addresses.
  • Fig. 1 shows a schematic block diagram of a GPRS backbone network architecture, in which the present invention can be implemented;
  • Fig. 2 shows a signaling diagram indicating indicating an Inter-SGSN routing area update procedure according to the preferred embodiment, and
  • Fig. 3 shows a signaling diagram indicating a Serving SRNS Relocation procedure according to the preferred embodiment.
  • a packet data network (PDN) 10 (e.g. an IP network) is connected via a first GGSN 31 to a first PLMN 71 comprising a first Intra-PLMN backbone network 51.
  • the first PLMN 71 includes at least a first SGSN 61 and a second SGSN 62 connected to each other and to the first GGSN 31 through the first Intra-PLMN backbone network 51.
  • the PDN 10 is connected to each other via a second GGSN 32 to a second PLMN 72 comprising a second Intra-PLMN backbone network 52.
  • the second PLMN 72 includes at least a third SGSN 63 connected to the second GGSN 32 through the second Intra-PLMN backbone network 52.
  • the first and second PLMNs 71 , 71 are connected to each other via an Inter-PLMN backbone network 20.
  • the connection between the first PLMN 71 and the Inter-PLMN backbone network 20 is provided through a first border gateway (BG) 41.
  • BG border gateway
  • the connection between the second PLMN 72 and the Inter-PLMN backbone network 20 is provided through a second BG 42.
  • Each of the Intra-PLMN backbone networks 51 , 52 may be a private IP network intended for packet domain data and signaling.
  • a private IP network is an IP network to which some access control mechanism is applied in order to achieve a required level of security.
  • the Inter-PLMN backbone network 20 can be packet data network, e.g. the public Internet or a leased line, which may be selected by a roaming agreement including a BG security functionality (i.e. typically just a router with security functions).
  • the first and second BGs 41 , 42 are not defined within the scope of the packet domain.
  • the first to third SGSNs 61 to 63 and the first and second GGSNs 31 , 32 contain functionality required to support GPRS functionality for GSM (Global System for Mobile communication) and/or UMTS.
  • the first and second GGSNs 31 , 31 represent network nodes which are accessed by the PDN 10 due to evaluation of the PDP address. It contains routing information for GPRSattached users. The routing information is used to tunnel packet data units (PDUs) to the MT's current point of attachment, i.e. the respective Serving SGSN.
  • PDUs packet data units
  • the first and second GGSNs 31 , 32 are the first point of PDN interconnection with the first and second PLMNs 71 , 72, respectively.
  • the first to third SGSNs 61 to 63 represent nodes for serving the MT. Each SGSN supports GPRS for GSM and/or UMTS.
  • an SGSN willing to use an IPv6 addressing will always indicate IPv6 and also IPv4 SGSN addresses in a respective GTP signaling message used to request creation of a GTP tunnel to the selected GGSN.
  • the SGSN may also indicate IPv6 and also IPv4 SGSN adr dresses in a respective GTP signaling message used to request update of a GTP tunnel. But this is not necessary if before sending the update, the SGSN already knows the type of addresses supported by GGSN. It may however be useful if the operator like to configure on a node by node basis the technology to be used (may be due to intermediate network).
  • the selected GGSN supports IPv6 in the network plane, it shall also indicate IPv6 addresses in the corresponding GTP response message together with IPv4 addresses.
  • the IPv4 addresses are stored in the SGSN and not used for transmission. IPv6 addresses are used for transmission on the network plane. In case of an inter SGSN handover, IPv4 and IPv6 addresses shall be given to the new SGSN in a backward compatible way. If the new SGSN does not support IPv6 addresses, it uses the obtained IPv4 addresses to update the tunnel towards the GGSN. Also the GGSN may start receiving user data from the new SGSN before the tunnel has been updated.
  • the first and second GGSNs 31 , 32 shall be ready to receive GTP packets (signaling or user data) on either IPv4 or IPv6 addresses. It should be noted, that in future a new SGSN may be provided, which is capable of using only IPv6 on network plane, and same principles would apply.
  • the node could select the transmission technology (IPv4 or IPv6) to be used based on operator configuration
  • the selected GGSN does not support IPv6 in the network plane, it indicates only IPv4 addresses in the corresponding GTP response message. IPv4 addresses are then used for transmission on the network plane as currently defined.
  • a Create PDP Context Request is sent from a SGSN node to a GGSN node as a part of the GPRS PDP Context Activation procedure.
  • a valid request initiates the creation of a tunnel between a PDP Context in a SGSN and a PDP Context in a GGSN.
  • the SGSN prefers to use IPv6 below GTP, it include the IPv6 addresses in new message fields Alternative SGSN Address, and an alternative or equivalent IPv4 address in existing message fields SGSN address.
  • the GGSN supports IPv6 below GTP, it stores and uses the alternative IPv6 SGSN addresses for communication with the SGSN.
  • the GGSN If the GGSN supports only IPv4 below GTP, it stores and uses the IPv4 SGSN addresses for communication with the SGSN. The SGSN accepts packets whether they are sent to its IPv4 or IPv6 address. The GGSN should not store SGSN IP addresses that it does not use. This mechanism provides maximum flexibility, as it is not based on special DNS features, and allows the GGSN to have processes using IPv4 only and processes using both IPv4 and IPv6.
  • Table 1 shows the specific information elements provided in the Create PDP Context Request message.
  • the Create PDP Context Response message is sent from the GGSN node to the SGSN node as a response of a Create PDP Context Request.
  • the SGSN receives the Create PDP Context Response with the Cause value indicating 'Request Accepted', the SGSN activates the PDP context and may start to forward PDUs to/from the MT from/to the external data network.
  • the GGSN shall include the IPv6 addresses in the new fields Alternative GGSN Address, and an equivalent IPv4 address in the fields GGSN address.
  • the SGSN uses the alternative IPv6 GGSN addresses for communication with the GGSN, except if the operator has configured the use of IPv4.
  • the SGSN stores the GGSN addresses and sends them to a new SGSN in a PDP context response message (message sent by old SGSN to new SGSN, after an MS has performed a Routing area update procedure to a new SGSN, that the new SGSN has sent a PDP context request message to the old SGSN).
  • the GGSN shall accept packets whether they are sent to its IPv4 or IPv6 address. This mechanism avoids losing connection if the new SGSN support IPv4 only below GTP.
  • Table 2 shows specific information elements provided in the Create PDP Context Response message.
  • an Update PDP Context Request message is sent from a SGSN to a GGSN as part of the GPRS Inter SGSN Routing Update procedure or the PDP Context Modification procedure or to redistribute contexts due to load sharing.
  • the SGSN may use SGSN IPv6 addresses only if it has received an IPv6 GGSN address from an old SGSN (Inter SGSN Routing Area Update case) or GGSN (PDP context modification). Otherwise SGSN uses SGSN IPv4 addresses.
  • the GGSN supports IPv6 below GTP, and the SGSN included an IPv6 SGSN address in the request, the GGSN includes the IPv6 addresses in the fields Alternative GGSN Address, and an equivalent IPv4 address in the fields GGSN address.
  • the SGSN uses the alternative IPv6 GGSN addresses for communication with the GGSN.
  • the SGSN may store both IPv4 and IPv6 GGSN addresses and send them to a new SGSN in PDP context response message.
  • the GGSN alternative address fields are not sent if the GGSN address field is not sent. This mechanism guarantees that the SGSN always stores proper IPv4 and IPv6 GGSN addresses, so that connection will not be lost if moving to a new SGSN supporting only IPv4 below GTP.
  • the new SGSN sends this message to the old SGSN to get the mobility management (MM) and PDP Contexts for the MT.
  • the old SGSN responds with an SGSN Context Response.
  • the new SGSN adds an SGSN Address for the control plane. If the new SGSN supports IPv6 below GTP, it adds its IPv6 address in the field Alternative SGSN Address for Control Plane.
  • the old SGSN selects the SGSN address for Con- trol Plane depending on its IPv6 supports, and stores this selected SGSN Address and uses it when sending control plane messages for the MT to the new SGSN in the SGSN context transfer procedure.
  • Table 4 shows specific information elements provided in the SGSN Context Re- quest message.
  • the old SGSN sends an SGSN Context Response message to the new SGSN as a response to a previous SGSN Context Request.
  • the old SGSN may use SGSN IPv6 addresses only if it received IPv6 SGSN address from the new SGSN. Otherwise SGSN shall use SGSN IPv4 addresses.
  • the new SGSN sends an SGSN Context Acknowledge message to the old SGSN as a response to the SGSN Context Response message. Only after receiving the SGSN Context Acknowledge message, the old SGSN starts to forward user data packets.
  • SGSN Context Acknowledge indicates to the old SGSN that the new SGSN has correctly received PDP Context information and is ready to receive user data packets.
  • the new SGSN uses an SGSN Address for user traffic, which may differ from that provided by the underlying network service (e.g. IP).
  • the old SGSN stores this SGSN Address and uses it when sending downlink PDUs to the new SGSN for the MT.
  • the SGSN may use IPv6 addresses only if it received IPv6 SGSN address for control plane from the old SGSN. Otherwise the SGSN use SGSN IPv4 addresses.
  • Fig. 2 shows a signaling diagram indicating an Inter-SGSN routing area update procedure according to the preferred embodiment.
  • the MT sends a Routing Area Update Request to a new SGSN, so as to initiate a routing area update.
  • the new SGSN sends an SGSN Context Request message including the SGSN Address fields and the Alternative SGSN Address fields to the old SGSN.
  • the old SGSN returns an SGSN Context Response message in which the desired address type is set in the SGSN Address for Control Plane fields, and all GGSN IPv4 and IPv6 addresses are included if available.
  • the new SGSN responds with an SGSN Context Acknowledge message including the used address type information.
  • the new SGSN sends an Update PDP Context Request message including the set address type information to the respective GGSN.
  • This message is sent using a GGSN IP address received from old SGSN. If the new SGSN and GGSN support IPv6 on the network plane, the IPv6 address of GGSN is preferably used. If either SGSN or GGSN does not support IPv6, IPv4 addresses are used. Here, it is assumed that in a first phase of transition towards IPv6, all nodes support IPv4.
  • the GGSN returns an Update PDP Context Response message includ- ing the GGSN Address fields and the Alternative GGSN Address fields. These address fields are especially necessary in the following cases:
  • the GGSN has changed its IP address (typically due to a reallocation of the PDP context to a new processing card)
  • the GGSN is configured to use IPv4 to communicate towards the new SGSN (due to possible problem in intermediate IP network), the GGSN will return only the IPv4 addresses and will not send an alternative address field containing the IPv6 address.
  • a Forward Relocation Request message is defined, which is sent by an old SGSN to a new SGSN to convey necessary in- formation to perform an SRNS (Serving Radio Network Subsystem) relocation procedure between the new SGSN and a target RNC (Radio Network Controller) of the UTRAN.
  • the old SGSN adds an SGSN Address for Control Plane field information. If the old SGSN supports IPv6 below GTP, it adds its IPv6 address in this field Alternative SGSN Address for Control Plane.
  • the new SGSN selects the SGSN address for Control Plane depending on its IPv6 supports, and stores this selected SGSN address and uses it when sending control plane messages for the MT to the old SGSN in the SRNS relocation procedure.
  • Table 5 shows specific information elements provided in the Forward Relocation Request message. Table 5:
  • the new SGSN sends a Forward Relocation Response message to the old SGSN as a response to a previous Forward Relocation Request message.
  • the new SGSN adds an SGSN Address for Control Plane information.
  • the SGSN may insert IPv6 addresses only if it received an IPv6 SGSN address for control plane from the old SGSN. Otherwise the new SGSN uses SGSN IPv4 addresses.
  • the old SGSN stores this SGSN address and uses it when sending control plane messages for the MT to the new SGSN in the SRNS relocation procedure.
  • Fig. 3 shows a signaling diagram indicating an SRNS (Serving Radio Network Subsystem) relocation procedure according to the preferred embodiment.
  • SRNS Serving Radio Network Subsystem
  • a source SRNS of the UTRAN decides to perform or initiate an SRNS relocation and sends a Relocation Required message to the old SGSN.
  • the old SGSN determines if the SRNS relocation is an inter-SGSN SRNS relocation and, if so, it sends a Forward Relocation Request message including the SGSN Address field and the Alternative SGSN Address field for control plane signaling to the respective new SGSN.
  • the new SGSN send a Relocation Request message to the target Radio Network Controller (RNC) of the UTRAN.
  • RNC Radio Network Controller
  • the lu bearers of the radio access bearers are setup between the target RNC and the new SGSN as the existing radio bearers will be reallocated between the MT and the target RNC when the target RNC takes the role of the Serving RNC in the new SRNS.
  • the GTP tunnels are established between the target RNC and the new SGSN.
  • the Forward Relocation Response message is sent from the new SGSN to the old SGSN to thereby indicate that the target RNC is ready to receive from the source SRNC (Serving RNC) of the SRNS the forwarded packet data units (PDUs).
  • the old SGSN continues the SRNS relocation by sending a Reloca- tion Command message to the source SRNC.
  • the source SRNC is now ready to forward downlink user data directly to the target RNC.
  • the target RNC send a relocation Detect message to the new SGSN.
  • the new SGSN sends an Update PDP Context Request message to a concerned GGSN.
  • the GGSN returns an Update PDP Context Re- sponse message including the GGSN Address fields and the Alternative GGSN Address fields.
  • the new SGSN When the new SGSN receives a Relocation Complete message from the SRNC, a Forward Relocation Complete signaling is exchanged between the new and the old SGSNs , and then the old SGSN initiates an lu release procedure at the SRNC. Finally, if the new Routing Area Identification is different, the MT initiates a Routing Area Update procedure.
  • a PDP Context information element contains the Session Management parameters, defined for an external packet data network address, that are necessary to transfer between SGSNs at the Inter SGSN Routing Area Update procedure.
  • the old SGSN sets Alternative GGSN Address for User Traffic and Alternative GGSN Address for Control Plane fields to contain the IPv6 addresses to be used to communicate with the GGSN.
  • a new SGSN not supporting IPv6 below GTP ignores these alternative GGSN addresses, and uses for communication the GGSN Address for User Traffic and GGSN Address for Control Plane fields.
  • a new SGSN supporting IPv6 below GTP stores the GGSN Address for User Traffic and GGSN Address for Control Plane, but uses use for communication the Control Plane, but uses use for communication the Alternative GGSN Address for User Traffic and Alternative GGSN Address for Control Plane.
  • the present invention can be implemented in any cellular network to provide address or network backward compatibility, when an address information is transferred between network nodes.
  • the names of the various functional entities, signaling messages and information elements used in the context of the preferred embodiment are not intended to limit or restrict the invention. The preferred embodiments may thus vary within the scope of the attached claims.

Landscapes

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

Abstract

L'invention concerne un procédé, un système et un élément de réseau permettant d'effectuer une transition d'adresse si un point de connexion à une extrémité de liaison est modifié entre un premier noeud de réseau et un second noeud de réseau d'un réseau cellulaire. Une information d'adresse et au moins une autre information d'adresse sont transmises dans un message de signalisation entre le premier noeud de réseau et le second noeud de réseau. Une desdites informations d'adresse et une desdites autres informations d'adresse sont sélectionnées au niveau du second noeud de réseau et sont utilisées pour rétablir ladite liaison en direction de l'autre extrémité de ladite liaison. A cet effet, le nouveau point de connexion est autorisé à rétablir la liaison en direction de l'autre extrémité de la liaison, même s'il ne peut communiquer qu'à l'aide d'une des deux adresses.
PCT/EP2001/011525 2001-10-05 2001-10-05 Procede et systeme pour transferts dans un reseau de service general de radiocommunication en mode paquet (gprs) avec des noeuds prenant en charge differentes versions internet WO2003032668A1 (fr)

Priority Applications (14)

Application Number Priority Date Filing Date Title
PCT/EP2001/011525 WO2003032668A1 (fr) 2001-10-05 2001-10-05 Procede et systeme pour transferts dans un reseau de service general de radiocommunication en mode paquet (gprs) avec des noeuds prenant en charge differentes versions internet
KR1020047004623A KR100693975B1 (ko) 2001-10-05 2002-10-04 네트워크 노드들간의 주소 변환 및 메시지 상관
CNB028196082A CN100542165C (zh) 2001-10-05 2002-10-04 提供地址转换以及消息相关的方法和系统
DE60216791T DE60216791T2 (de) 2001-10-05 2002-10-04 Adressenübergang und korrelation von nachrichten zwischen netzknoten
RU2004110040/09A RU2273104C2 (ru) 2001-10-05 2002-10-04 Переключение адресов и корреляция сообщений между сетевыми узлами
EP02772680A EP1436964B1 (fr) 2001-10-05 2002-10-04 Transition d'adresse et correlation de messages entre noeuds de reseau
US10/491,664 US7818453B2 (en) 2001-10-05 2002-10-04 Address transition and message correlation between networks nodes
CA002462701A CA2462701A1 (fr) 2001-10-05 2002-10-04 Transition d'adresse et correlation de messages entre noeuds de reseau
CN2009101268721A CN101511081B (zh) 2001-10-05 2002-10-04 网络节点之间的地址转换与消息相关
PCT/IB2002/004079 WO2003032604A1 (fr) 2001-10-05 2002-10-04 Transition d'adresse et correlation de messages entre noeuds de reseau
KR1020067023436A KR20060135946A (ko) 2001-10-05 2002-10-04 네트워크 노드들간의 주소 변환 및 메시지 상관
AT02772680T ATE348476T1 (de) 2001-10-05 2002-10-04 Adressenübergang und korrelation von nachrichten zwischen netzknoten
PL02369412A PL369412A1 (en) 2001-10-05 2002-10-04 Address transition and message correlation between network nodes
JP2003535437A JP3834036B2 (ja) 2001-10-05 2002-10-04 ネットワークノード間におけるアドレスの変更とメッセージの関連付け

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2001/011525 WO2003032668A1 (fr) 2001-10-05 2001-10-05 Procede et systeme pour transferts dans un reseau de service general de radiocommunication en mode paquet (gprs) avec des noeuds prenant en charge differentes versions internet

Publications (1)

Publication Number Publication Date
WO2003032668A1 true WO2003032668A1 (fr) 2003-04-17

Family

ID=8164614

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2001/011525 WO2003032668A1 (fr) 2001-10-05 2001-10-05 Procede et systeme pour transferts dans un reseau de service general de radiocommunication en mode paquet (gprs) avec des noeuds prenant en charge differentes versions internet

Country Status (1)

Country Link
WO (1) WO2003032668A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005088921A1 (fr) * 2004-03-18 2005-09-22 Huawei Technologies Co., Ltd. Procede de communication entre des reseaux satellitaires mondiaux utilisant le protocole ip de versions differentes
EP1753189A1 (fr) * 2004-11-10 2007-02-14 Huawei Technologies Co., Ltd. Procede de communication entre noeuds serveurs de prise en charge de services de radiotransmission par paquets generaux
CN1305346C (zh) * 2003-08-18 2007-03-14 乐金电子(中国)研究开发中心有限公司 通用分组无线业务系统的网络状态通知服务方法
CN100362829C (zh) * 2005-02-24 2008-01-16 华为技术有限公司 IPv6和IPv4 GPRS核心网互通的方法及装置
DE102004008720B4 (de) * 2003-02-21 2009-03-19 Samsung Electronics Co., Ltd., Suwon Vorrichtung und Verfahren zur Durchführung von Verkehrsflussschablonen-Paketfilterung gemäß Internet-Protokollversionen in einem mobilen Kommunikationssystem
CN111225072A (zh) * 2018-11-26 2020-06-02 厦门本能管家科技有限公司 一种基于区块链的动态寻址方法及系统

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000022839A1 (fr) * 1998-10-12 2000-04-20 Nokia Networks Oy Maintien de connexion entre un point de commande de reseau intelligent et un commutateur d'acces

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000022839A1 (fr) * 1998-10-12 2000-04-20 Nokia Networks Oy Maintien de connexion entre un point de commande de reseau intelligent et un commutateur d'acces

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
TRANSITION TO IPV6 IN 2G AND 3G MOBILE NETWORKS. WHITE PAPER, NOKIA (C 2000. RETRIEVED ON 2002-05-06 FROM THE INTERNET: HTTP://NDS1.NOKIA.COM/IPV6/WHITEPAPER_IPV6_10832.PDF), 6 May 2002 (2002-05-06), XP002902467 *

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102004008720B4 (de) * 2003-02-21 2009-03-19 Samsung Electronics Co., Ltd., Suwon Vorrichtung und Verfahren zur Durchführung von Verkehrsflussschablonen-Paketfilterung gemäß Internet-Protokollversionen in einem mobilen Kommunikationssystem
CN1305346C (zh) * 2003-08-18 2007-03-14 乐金电子(中国)研究开发中心有限公司 通用分组无线业务系统的网络状态通知服务方法
WO2005088921A1 (fr) * 2004-03-18 2005-09-22 Huawei Technologies Co., Ltd. Procede de communication entre des reseaux satellitaires mondiaux utilisant le protocole ip de versions differentes
CN100387022C (zh) * 2004-03-18 2008-05-07 华为技术有限公司 一种使用不同版本的ip协议的gsn之间的通讯方法
EP1753189A1 (fr) * 2004-11-10 2007-02-14 Huawei Technologies Co., Ltd. Procede de communication entre noeuds serveurs de prise en charge de services de radiotransmission par paquets generaux
EP1753189A4 (fr) * 2004-11-10 2008-05-28 Huawei Tech Co Ltd Procede de communication entre noeuds serveurs de prise en charge de services de radiotransmission par paquets generaux
CN100362829C (zh) * 2005-02-24 2008-01-16 华为技术有限公司 IPv6和IPv4 GPRS核心网互通的方法及装置
CN111225072A (zh) * 2018-11-26 2020-06-02 厦门本能管家科技有限公司 一种基于区块链的动态寻址方法及系统

Similar Documents

Publication Publication Date Title
US7818453B2 (en) Address transition and message correlation between networks nodes
US9929952B2 (en) Methods and apparatus for data transfer in a packet-switched data network
US8824430B2 (en) Wireless mobility gateway
EP1560378B1 (fr) Une passerelle des services mobiles dans les réseaux sans fil
US7995523B2 (en) Method and apparatus for data transfer in a packet-switched network
MXPA04012156A (es) Red de area local inalambrica (wlan) como un modo de soporte logico para un acoplamiento hibrido en un interfuncionamiento etnre una red local inalambrica (wlan) y un sistema de comunicaciones moviles.
US20100061386A1 (en) Method and Arrangement Relating to Communications Network Services Request Activation
EP1929716B1 (fr) Porteuses conservees
KR20020005625A (ko) 정보 전송 방법 및 장치
US20190364467A1 (en) Method and communication entity for proving a communication connection
EP1224819B1 (fr) Service de donnees en paquets dans un systeme de communication mobile
WO2003032668A1 (fr) Procede et systeme pour transferts dans un reseau de service general de radiocommunication en mode paquet (gprs) avec des noeuds prenant en charge differentes versions internet
US20110007632A1 (en) Technique for route optimization in a communication network
EP1667384B1 (fr) Procédé pour un gateway pour selectionner un canal pour transferer des pakets de données
EP1436964B1 (fr) Transition d'adresse et correlation de messages entre noeuds de reseau

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BY BZ CA CH CN CO CR CU CZ DE DM DZ EC EE ES FI GB GD GE GH HR HU ID IL IN IS JP KE KG KP KR LC LK LR LS LT LU LV MA MD MG MN MW MX MZ NO NZ PH PL PT RO SD SE SG SI SK SL TJ TM TR TT TZ UG US UZ VN YU ZA

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ UG ZW AM AZ BY KG KZ MD TJ TM AT BE CH CY DE DK ES FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP