| (11) | EP 2 391 067 B1 |
(12) | EUROPEAN PATENT SPECIFICATION |
|
|
(54) | Methods and apparatuses for forwarding data in case of a handover between GERAN/UTRAN systems using the Direct Tunnel solution Verfahren und Vorrichtungen zur Weiterleitung von Daten im Falle eines Handovers zwischen GERAN/UTRAN-Systemen unter Verwendung der Direct Tunnel - Lösung Procédés et appareils pour transférer des données en cas d'un transfert intersystèmes GERAN/UTRAN en utilisant la solution Tunnel Direct |
|
| |||||||||||||||||||||||||||||||||||||||
Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention). |
Field of the Invention
Background of the Invention
step S301: a source Base Station Subsystem (BSS) decides to initiate a PS handover;
step S302: the source BSS sends a PS handover request message to an old SGSN, i.e. 2G SGSN;
step S303: the 2G SGSN sends a forward relocation request message to a new SGSN, i.e. 3G SGSN;
step S304: the 3G SGSN builds a relocation request message and sends the message to a target RNC;
step S305: the target RNC sends a relocation request acknowledge message to the 3G SGSN;
step S306: the 3G SGSN sends a forward relocation response to the 2G SGSN;
step S307: the 2G SGSN receives an IP packet from a GGSN and sends the IP packet to an MS via the source BSS;
step S308: the 2G SGSN forwards the IP packet to the target RNC via the 3G SGSN;
step S309: the 2G SGSN sends a PS handover request acknowledge message to the source BSS;
step S310: the MS sends a handover to UTRAN complete message to the target RNC;
step S311: the target RNC sends a relocation complete message to the 3G SGSN;
step S312: the 3G SGSN sends an update PDP context request message to the GGSN;
step S313: the GGSN returns an update PDP context response message to the 3G SGSN;
step S401: a source RNC decides to initiate a PS handover;
step S402: the source RNC sends a relocation request message to an old SGSN, i.e. 3G SGSN;
step S403: the 3G SGSN sends a forward relocation request message to a new SGSN, i.e. 2G SGSN;
step S404: the 2G SGSN builds a PS handover request message and sends the message to a target BSS;
step S405: the target RNC sends a PS handover request acknowledge message to the 2G SGSN;
step S406: the 2G SGSN sends a forward relocation response message to the 3G SGSN;
step S407: the 3G SGSN receives an IP packet from a GGSN and sends the IP packet to an MS via the source RNC;
step S408: the 3G SGSN sends a relocation command message to the source RNC;
step S409: the source RNC forwards the IP packet to the 3G SGSN, the 3G SGSN forwards the IP packet to the 2G SGSN, and the 2G SGSN forwards the IP packet to the target BSS;
step S410: the target BSS sends a PS handover complete message to the 2G SGSN;
step S411: the 2G SGSN sends an update PDP context Request message to the GGSN;
step 412: the GGSN returns an update PDP context response message to the 2G SGSN;
step S501: an MS decides to perform an inter-system change;
step S502: the MS sends a routing area update request message to a new SGSN, i.e. 3G SGSN;
step S503: the 3G SGSN sends an SGSN context request message to an old SGSN, i.e. 2G SGSN, to obtain user context;
step S504: the 2G SGSN returns an SGSN context response message to the 3G SGSN, and carries the user context information in the context response message;
step S505: the 3G SGSN sends an SGSN context acknowledge message to the 2G SGSN, informing the 2G SGSN that the 3G SGSN is ready to receive data packets;
step S506: the 2G SGSN duplicates a buffered data packet and forwards to the 3G SGSN;
step S507: the 3G SGSN sends an update PDP context request message to a GGSN;
step S508: the GGSN returns an update PDP context response to the 3G SGSN;
step S509: the 3G SGSN returns a routing area update accept message to the MS;
step S510: the MS returns a routing area update complete message to the 3G SGSN;
step S511: the MS sends a service request message to the 3G SGSN;
step S512: Radio Access Bearer (RAB) Assignment procedure is performed between the 3G SGSN and an RNC, thereby establishing a RAB;
step S601: an MS decides to perform an inter-system change;
step S602: the MS sends a routing area update request message to a new SGSN, i.e. 2G SGSN;
step S603: the 2G SGSN sends an SGSN context request message to an old SGSN, i.e. 3G SGSN, to obtain user context;
step S604: the 3G SGSN sends an SRNS context request message to a source RNC;
step S605: the source RNC returns an SRNS context response message to the 3G SGSN, stops sending downlink data to the MS, and buffers the data;
step S606: the 3G SGSN returns an SGSN context response message to the 2G SGSN, and carries the user context information in the context response message;
step S607: the 2G SGSN sends an SGSN context acknowledge message to the 3G SGSN, informing the 3G SGSN that the 2G SGSN is ready to receive data packets,;
step S608: the 3G SGSN sends an SRNS data forward command to the source RNC, the source RNC duplicates a buffered data packet and forwards to the 3G SGSN;
step S609: the 3G SGSN forwards the data packet to the 2G SGSN
step S610: the 2G SGSN sends an update PDP context request message to a GGSN;
step S611: the GGSN returns an update PDP context response to the 2G SGSN;
step S612: the 2G SGSN returns a routing area update accept message to the MS;
step S510: the MS returns a routing area update complete message to the 2G SGSN;
Summary of the Invention
Brief Description of the Drawings
Figure 1 illustrates network architecture of GPRS/ UMTS;
Figure 2 illustrates user plane processing in the conventional art;
Figure 3 is a flow chart of a data processing method when a handover from a GERAN to a UTRAN takes place according to the protocol 43.129;
Figure 4 is a flow chart of a data processing method when a handover from a UTRAN to a GERAN takes place according to the protocol 43.129;
Figure 5 is a flow chart of a data processing method when a change from a GERAN to a UTRAN takes place according to the protocol 23.060;
Figure 6 is a flow chart of a data processing method when a change from a UTRAN to a GERAN takes place according to the protocol 23.060;
Figure 7 is a flow chart of a data processing method when a handover from a GERAN to a UTRAN takes place according to a first embodiment of the present invention;
Figure 8 is a flow chart of a data processing method when a handover from a UTRAN to a GERAN takes place according to a first embodiment of the present invention;
Figure 9 is a flow chart of a data processing method when a change from a GERAN to a UTRAN takes place according to a first embodiment of the present invention;
Figure 10 is a flow chart of a data processing method when a change from a UTRAN to a GERAN takes place according to a first embodiment of the present invention;
Figure 11 illustrates network architecture of an evolved packet core network in the conventional art;
Figure 12 is a flow chart of a data processing method when a handover from a GERAN to a UTRAN takes place according to a second embodiment of the present invention;
Figure 13 is a flow chart of a data processing method when a handover from a UTRAN to a GERAN takes place according to a second embodiment of the present invention;
Figure 14 is a flow chart of a data processing method when a change from a GERAN to a UTRAN takes place according to a second embodiment of the present invention;
Figure 15 is a flow chart of a data processing method when a change from a UTRAN to a GERAN takes place according to a second embodiment of the present invention;
Figure 16 is a flow chart of a data processing method when a handover from a GERAN to a UTRAN takes place according to a third embodiment of the present invention;
Figure 17 is a flow chart of a data processing method when a handover from a UTRAN to a GERAN takes place according to a third embodiment of the present invention;
Figure 18 is a flow chart of a data processing method when a change from a GERAN to a UTRAN takes place according to a third embodiment of the present invention;
Figure 19 is a flow chart of a data processing method when a change from a UTRAN to a GERAN takes place according to a third embodiment of the present invention; and
Figure 20 is a structural diagram of a data processing system provided in an embodiment of the present invention.
Detailed Description of the Embodiments
step S701: a source BSS decides to initiate a handover;
step S702: the source BSS sends a handover request message to an old SGSN, i.e. 2G SGSN;
step S703: the 2G SGSN sends a forward relocation request message to a new SGSN, i.e. 3G SGSN;
step S704: the 3G SGSN builds a relocation request message, and sends the message to a target RNC;
step S705: the target RNC sends a relocation request acknowledged message to the 3G SGSN;
step S706: the 3G SGSN sends an update PDP context request message to a GGSN, to request to change user plane routing from the GGSN to the 3G SGSN;
step S707: the GGSN returns an update PDP context response to the 3G SGSN;
step S708: the 3G SGSN sends a forward data request to the GGSN, to request the GGSN to assign a data forwarding tunnel for data forwarding;
step S709: the GGSN returns a forward data response message to the 3G SGSN, assigns a data forwarding tunnel identifier to the data forwarding tunnel and carries the data forwarding tunnel identifier in the response message to the 3G SGSN, the data forwarding tunnel identifier includes IP address and TEID (Tunnel End Point Identifier);
step S710: the 3G SGSN sends a forward relocation response message to the 2G SGSN, a data forwarding tunnel identifier carried in the message is the data forwarding tunnel identifier of the GGSN;
step S711: the 2G SGSN receives a data packet from the GGSN, and sends the data packet to an MS via the source BSS;
step S712: for data of a lossless service, the 2G SGSN forwards the data packet to the GGSN according to the data forwarding tunnel identifier carried in the forward relocation response message sent by the 3G SGSN, the GGSN buffers the data packet after receiving the data packet forwarded by the 2G SGSN;
step S713: the 2G SGSN sends a handover request acknowledge message to the source BSS;
step S714: the MS sends a handover to UTRAN complete message to the target RNC;
step S715: the target RNC sends a relocation complete message to the 3G SGSN;
step S716: the 3G SGSN sends an update context request message to the GGSN;
step S717: the GGSN returns an update context response message to the 3G SGSN;
step S718: the GGSN forwards the buffered forwarded data packet to the target RNC.
step S801: a source RNC decides to initiate a handover;
step S802: the source RNC sends a relocation request message to an old SGSN, i.e. 3G SGSN;
step S803: the 3G SGSN sends a forward relocation request message to a new SGSN, i.e. 2G SGSN;
step S804: the 2G SGSN builds a handover request message, and sends the message to a target BSS;
step S805: the target BSS sends a handover request acknowledged message to the 2G SGSN;
step S806: the 2G SGSN sends a forward relocation response message to the 3G SGSN;
step S807: the 3G SGSN sends a forward data request to a GGSN, to request the GGSN to assign a data forwarding tunnel for data forwarding;
step S808: the GGSN returns a forward data response message to the 3G SGSN, assigns a data forwarding tunnel identifier to the data forwarding tunnel and carries the data forwarding tunnel identifier in the response message to the 3G SGSN;
step S809: the 3G SGSN receives a data packet from the GGSN, and sends the data packet to an MS via the source RNC;
step S810: the 3G SGSN sends a relocation command message to the source RNC, a data forwarding tunnel identifier carried in the message is the data forwarding tunnel identifier of the GGSN;
step S811: for data of a lossless service, the source RNC forwards the data packet to the GGSN according to the data forwarding tunnel identifier carried in the relocation command message sent by the 3G SGSN, the GGSN buffers the received data packet;
step S812: the target BSS sends a handover complete message to the 2G SGSN;
step S813: the 2G SGSN sends an update context request message to the GGSN;
step S814: the GGSN returns an update context response message to the 2G SGSN;
step S815: the GGSN forwards the buffered forwarded data packet to the 2G SGSN.
step S901: an MS decides to initiate an intersystem change;
step S902: the MS sends a routing area update request message to a new SGSN, i.e. 3G SGSN;
step S903: the 3G SGSN sends an SGSN context request message to an old SGSN, i.e. 2G SGSN, to obtain user context;
step S904: the 2G SGSN returns an SGSN context response message to the 3G SGSN, and carries the user context information in the message;
step S905: the 3G SGSN sends an update PDP context request message to a GGSN, to request to change user plane routing from the GGSN to the 3G SGSN;
step S906: the GGSN returns an update PDP context response to the 3G SGSN;
step S907: the 3G SGSN sends a forward data request message to the GGSN, to request the GGSN to assign a data forwarding tunnel for data forwarding;
step S908: the GGSN returns a forward data response message to the 3G SGSN, assigns a data forwarding tunnel identifier to the data forwarding tunnel, and carries the data forwarding tunnel identifier in the response message to the 3G SGSN;
step S909: the 3G SGSN sends an SGSN context acknowledge message to the 2G SGSN, informing the 2G SGSN that the 3G SGSN is ready to receive data packets, a data forwarding tunnel identifier carried in the message is the data forwarding tunnel identifier of the GGSN;
step S910: the 2G SGSN duplicates a buffered data packet and forwards to the GGSN according to the data forwarding tunnel identifier carried in the SGSN context acknowledge message sent by the 3G SGSN, the GGSN buffers the received forwarded data packet;
step S911: the 3G SGSN returns a routing area update accept message to the MS;
step S912: the MS returns a routing area update complete message to the 3G SGSN;
step S913: the MS returns a service request message to the 3G SGSN;
step S914: RAB assignment procedure is performed between the 3G SGSN and an RNC, thereby establishing RAB;
step S915: the 3G SGSN sends an update context request message to the GGSN;
step S916: the GGSN returns an update context response message to the 3G SGSN;
step S917: the GGSN forwards the buffered forwarded data packet to the target RNC.
step S1001: an MS decides to initiate an intersystem change;
step S1002: the MS sends a routing area update request message to a new SGSN, i.e. 2G SGSN;
step S1003: the 2G SGSN sends an SGSN context request message to an old SGSN, i.e. 3G SGSN, to obtain user context;
step S1004: the 3G SGSN sends an SRNS context request message to a source RNC;
step S1005: the source RNC returns an SRNS context response message to the 3G SGSN, stops sending downlink data to the MS, and buffers the data;
step S1006: the 3G SGSN returns an SGSN context response message to the 2G SGSN, and carries the user context information in the message;
step S1007: the 2G SGSN sends an SGSN context acknowledge message to the 3G SGSN, informing the 3G SGSN that the 2G SGSN is ready to receive data packets;
step S1008: the 3G SGSN sends a forward data request to a GGSN, to request the GGSN to assign a data forwarding tunnel for data forwarding;
step S1009: the GGSN returns a forward data response message to the 3G SGSN, assigns a data forwarding tunnel identifier to the data forwarding tunnel, and carries the data forwarding tunnel identifier in the response message to the 3G SGSN;
step S1010: the 3 G SGSN sends an SRNS data forward command to the source RNC, a data forwarding tunnel identifier carried in the message is the data forwarding tunnel identifier of the GGSN, the source RNC duplicates a buffered data packet and forwards to the GGSN, the GGSN buffers the forwarded data packet;
step S1011: the 2G SGSN sends an update PDP context request message to the GGSN;
step S1012: the GGSN returns an update PDP context response message to the 2G SGSN;
step S1013: the GGSN forwards the buffered forwarded data packet to the 2G SGSN;
step S1014: the 2G SGSN returns a routing area update accept message to the MS;
step S1015: the MS returns a routing area update complete message to the 2G SGSN.
step 1201: a source BSS decides to initiate a handover;
step 1202: the source BSS sends a handover request message to an old SGSN, i.e. 2G SGSN;
step 1203: the 2G SGSN sends a forward relocation request message to a new SGSN, i.e. 3G SGSN;
step 1204: the 3G SGSN builds a relocation request message and sends the message to a target RNC;
step 1205: the target RNC sends relocation request acknowledge message to the 3G SGSN;
step 1206: the 3G SGSN sends a forward data request message to a GGSN, to request the GGSN to assign a data forwarding tunnel for data forwarding, an identifier of a GTP tunnel of the target RNC side is carried in the message, subsequently the GGSN will forward data of a lossless service to the GTP tunnel;
step 1207: the GGSN returns a forward data response message to the 3G SGSN, assigns a data forwarding tunnel identifier to the data forwarding tunnel, and sends to the 3G SGSN in the response message;
step 1208: the 3G SGSN sends a forward relocation response message to the 2G SGSN, a data forwarding tunnel identifier carried in the message is the data forwarding tunnel identifier of the GGSN;
step 1209: the 2G SGSN receives a data packet from the GGSN, and sends the data packet to an MS via the source BSS;
step 1210: for data of a lossless service, the 2G SGSN forwards the data packet to the GGSN according to the data forwarding tunnel identifier carried in the forward relocation response message sent by the 3G SGSN, the GGSN forwards the data packet forwarded by the 2G SGSN to the target RNC on receipt of the data packet;
step 1211: the 2G SGSN sends a handover request acknowledge message to the source BSS;
step S1212: the MS sends a handover to UTRAN complete message to the target RNC;
step S1213: the target RNC sends a relocation complete message to the 3G SGSN;
step S1214: the 3G SGSN sends an update context request message to the GGSN;
step S1215: the GGSN returns an update context response message to the 3G SGSN.
step S1301: a source RNC decides to initiate a handover;
step S1302: the source RNC sends a relocation request message to an old SGSN, i.e. 3G SGSN;
step S1303: the 3G SGSN sends a forward relocation request message to a new SGSN, i.e. 2G SGSN;
step S1304: the 2G SGSN builds a handover request message, and sends the message to a target B S S;
step S1305: the target BSS sends a handover request acknowledged message to the 2G SGSN; step S1306: the 2G SGSN sends a forward relocation response message to the 3G SGSN;
step S 1307: the 3 G SGSN sends a forward data request to a GGSN, to request the GGSN to assign a data forwarding tunnel for data forwarding, an identifier of a data forwarding tunnel of the 2G SGSN is carried in the message, subsequently the GGSN will forward data of a lossless service to the data forwarding tunnel;
step S1308: the GGSN returns a forward data response message to the 3G SGSN, assigns a data forwarding tunnel identifier to the data forwarding tunnel and carries the data forwarding tunnel identifier in the response message to the 3G SGSN;
step S 1309: the 3G SGSN receives a data packet from the GGSN, and sends the data packet to an MS via the source RNC;
step S1310: the 3 G SGSN sends a relocation command message to the source RNC, a data forwarding tunnel identifier carried in the message is the data forwarding tunnel identifier of the GGSN;
step S1311: for data of a lossless service, the source RNC forwards the data packet to the GGSN according to the data forwarding tunnel identifier carried in the relocation command message sent by the 3G SGSN, the GGSN forwards the data packet forwarded by the source RNC to the 2G SGSN on receipt of the data packet, the 2G SGSN forwards the data packet to the target B S S;
step S1312: the target BSS sends a handover complete message to the 2G SGSN;
step S 1313: the 2G SGSN sends an update context request message to the GGSN;
step S 1314: the GGSN returns an update context response message to the 2G SGSN.
step S 140 1: an MS decides to initiate an intersystem change;
step S1402: the MS sends a routing area update request message to a new SGSN, i.e. 3G SGSN;
step S1403: the 3G SGSN sends an SGSN context request message to an old SGSN, i.e. 2G SGSN, to obtain user context;
step S1404: the 2G SGSN returns SGSN context response message to the 3G SGSN, and carries the user context information in the message;
step 1405: RAB assignment procedure is performed between the 3G SGSN and an RNC, thereby establishing RAB;
step S1406: the 3G SGSN sends an update PDP context request message to a GGSN, to request to change user plane routing from the GGSN to the 3G SGSN;
step S 1407: the GGSN returns an update PDP context response to the 3G SGSN;
step S1408: the 3G SGSN sends a forward data request message to the GGSN, to request the GGSN to assign a data forwarding tunnel for data forwarding, an identifier of a GTP tunnel of the target RNC side is carried in the message, subsequently the GGSN will forward data of a lossless service to the GTP tunnel;
step S1409: the GGSN returns a forward data response message to the 3G SGSN, assigns a data forwarding tunnel identifier to the data forwarding tunnel, and carries the data forwarding tunnel identifier in the response message to the 3G SGSN;
step S1410: the 3G SGSN sends an SGSN context acknowledge message to the 2G SGSN, informing the 2G SGSN that the 3G SGSN is ready to receive data packets, a data forwarding tunnel identifier carried in the message is the data forwarding tunnel identifier of the GGSN;
step S1411: the 2G SGSN duplicates a buffered data packet and forwards to the GGSN according to the data forwarding tunnel identifier carried in the SGSN context acknowledge message sent by the 3G SGSN, the GGSN forwards the data packet forwarded by the 2G SGSN to the target RNC on receipt of the data packet;
step S1412: the 3 G SGSN returns a routing area update accept message to the MS;
step S1413: the MS returns a routing area update complete message to the 3G SGSN;
step S1414: the 3 G SGSN sends an update context request message to the GGSN, to change a downlink GTP tunnel identifier of user context in the GGSN to the GTP tunnel identifier of the RNC;
step S 1415: the GGSN returns an update context response message to the 3G SGSN.
step S 1501: an MS decides to initiate an intersystem change;
step S1502: the MS sends a routing area update request message to a new SGSN, i.e. 2G SGSN;
step S1503: the 2G SGSN sends an SGSN context request message to an old SGSN, i.e. 3G SGSN, to obtain user context;
step S1504: the 3G SGSN sends an SRNS context request message to a source RNC;
step S1505: the source RNC returns an SRNS context response message to the 3G SGSN, stops sending downlink data to the MS, and buffers the data;
step S1506: the 3G SGSN returns an SGSN context response message to the 2G SGSN, and carries the user context information in the message;
step S1507: the 2G SGSN sends an SGSN context acknowledge message to the 3G SGSN, informing the 3G SGSN that the 2G SGSN is ready to receive data packets;
step S1508: the 3G SGSN sends a forward data request to a GGSN, to request the GGSN to assign a data forwarding tunnel for data forwarding, an identifier of a data forwarding tunnel of the 2G SGSN is carried in the message, subsequently the GGSN will forward data of a lossless service to the data forwarding channel;
step S1509: the GGSN returns a forward data response message to the 3G SGSN, assigns a data forwarding tunnel identifier to the data forwarding tunnel, and carries the data forwarding tunnel identifier in the response message to the 3G SGSN;
step S1510: the 3 G SGSN sends an SRNS data forward command to the source RNC, a data forwarding tunnel identifier carried in the message is the data forwarding tunnel identifier of the GGSN, the source RNC duplicates a buffered data packet and forwards to the GGSN, the GGSN forwards the data packet forwarded by the source RNC to the 2G SGSN on receipt of the data packet;
step S 1511: the 2G SGSN sends an update PDP context request message to the GGSN;
step S1512: the GGSN returns an update PDP context response message to the 2G SGSN;
step S 1513: the 2G SGSN returns a routing area update accept message to the MS;
step S 1514: the MS returns a routing area update complete message to the 2G SGSN.
A user plane anchor network element sends data to a source data forwarding network element and a target side processing network element on receipt of an instruction. The instruction may be a bicast command instruction instructing the user plane anchor network element to send data to the source data forwarding network element and the target side processing network element. On completion of update of user plane routing, the user plane anchor network element stops bicasting and sends data to the target side processing network element only.
step 1601: a source BSS decides to initiate a handover;
step 1602: the source BSS sends a handover request message to an old SGSN, i.e. 2G SGSN;
step 1603: the 2G SGSN sends a forward relocation request message to a new SGSN, i.e. 3G SGSN;
step 1604: the 3G SGSN builds a relocation request message and sends the message to a target RNC;
step 1605: the target RNC sends relocation request acknowledge message to the 3G SGSN;
step 1606: the 3G SGSN sends a forward relocation response message to the 2G SGSN, an indication is carried in the message to instruct the 2G SGSN not to perform data forwarding;
step 1607: the 3G SGSN sends a bicast command message to a GGSN, instructing the GGSN to send data to the 2G SGSN and the target RNC, a GTP tunnel identifier of the target RNC is carried in the message;
step 1608: the GGSN sends a downlink data packet to the 2G SGSN and the target RNC;
step 1609: the 2G SGSN sends a handover request acknowledge message to the source BSS;
step 1610: an MS sends a handover to UTRAN complete message to the target RNC;
step 1611: the target RNC sends a relocation complete message to the 3G SGSN;
step 1612: a process of PDP context update is performed between the 3G SGSN and the GGSN, which changes a downlink GTP tunnel identifier of user in the GGSN to the GTP tunnel identifier of the target RNC, the GGSN stops data bicasting in the process;
step 1613: the GGSN sends a downlink data packet to the target RNC.
step S 170 1: a source RNC decides to initiate a handover;
step S1702: the source RNC sends a relocation request message to an old SGSN, i.e. 3G SGSN;
step S1703: the 3G SGSN sends a forward relocation request message to a new SGSN, i.e. 2G SGSN;
step S1704: the 2G SGSN builds a handover request message, and sends the message to a target BSS;
step S1705: the target BSS sends a handover request acknowledged message to the 2G SGSN;
step S1706: the 2G SGSN sends a forward relocation response message to the 3G SGSN;
step S1707: the 3G SGSN sends a bicast command message to a GGSN, instructing the GGSN to send data to the source RNC and the 2G SGSN, a GTP tunnel identifier of the 2G SGSN is carried in the message;
step S 1708: the GGSN sends a downlink data pack to the source RNC and the 2G SGSN;
step S1709: the 3G SGSN sends a relocation command message to the source RNC, an indication is carried in the message to instruct the source RNC not to perform data forwarding;
step S1710: the target BSS sends a handover complete message to the 2G SGSN;
step S1711: a process of PDP context update is performed between the 2G SGSN and the GGSN, which changes a downlink GTP tunnel identifier of user in the GGSN to the GTP tunnel identifier of the 2G SGSN, the GGSN stops data bicasting in the process;
step S 1712: the GGSN sends a downlink data packet to the 2G SGSN, the 2G SGSN sends the downlink data packet to the target BSS.
step S 1801: an MS decides to initiate an intersystem change;
step S 1802: the MS sends a routing area update request message to a new SGSN, i.e. 3G SGSN;
step S1803: the 3G SGSN sends an SGSN context request message to an old SGSN, i.e. 2G SGSN, to obtain user context;
step S1804: the 2G SGSN returns an SGSN context response message to the 3G SGSN, and carries the user context information in the message;
step 1805: RAB assignment procedure is performed between the 3G SGSN and an RNC, thereby establishing RAB;
step S1806: the 3G SGSN sends an SGSN context acknowledge message to the 2G SGSN, an indication is carried in the message to instruct the 2G SGSN not to perform data forwarding;
step S1807: the 3G SGSN sends a bicast command message to the GGSN, instructing the GGSN to send data to the 2G SGSN and a target RNC, a GTP tunnel identifier of the target RNC is carried in the message;
step S 1808: the GGSN sends a downlink data packet to the 2G SGSN and the target RNC;
step S1809: the 3G SGSN returns a routing area update accept message to the MS;
step S1810: the MS returns a routing area update complete message to the 3G SGSN;
step S1811: a process of PDP context update is performed between the 3G SGSN and the GGSN, which changes a downlink GTP tunnel identifier of user in the GGSN to the GTP tunnel identifier of the target RNC, the GGSN stops data bicasting in the process;
step S 1812: the GGSN sends a downlink data packet to the target RNC.
step S 1901: an MS decides to initiate an intersystem change;
step S1902: the MS sends a routing area update request message to a new SGSN, i.e. 2G SGSN;
step S1903: the 2G SGSN sends an SGSN context request message to an old SGSN, i.e. 3G SGSN, to obtain user context;
step S 1904: the 3G SGSN sends an SRNS context request message to a source RNC;
step S1905: the source RNC returns an SRNS context response message to the 3G SGSN, stops sending downlink data to the MS, and buffers the data;
step S1906: the 3G SGSN returns an SGSN context response message to the 2G SGSN, and carries the user context information in the message;
step S1907: the 2G SGSN sends an SGSN context acknowledge message to the 3G SGSN, informing the 3G SGSN that the 2G SGSN is ready to receive data packets;
step S1908: the 3G SGSN sends a bicast command message to the GGSN, instructing the GGSN to send data to the source RNC and the 2G SGSN, a GTP tunnel identifier of the 2G SGSN is carried in the message;
step S 1909: the GGSN sends a downlink data packet to the source RNC and the 2G SGSN;
step S1910: a process of PDP context update is performed between the 2G SGSN and the GGSN, which changes a downlink GTP tunnel identifier of user in the GGSN to the GTP tunnel identifier of the 2G SGSN, the GGSN stops data bicasting in the process;
step S 1911: the GGSN sends a downlink data packet to the 2G SGSN, the 2GSN sends the downlink data packet to the MS;
step S 1912: the 2G SGSN returns a routing area update accept message to the MS;
step S1913: the MS returns a routing area update complete message to the 2G SGSN.
in a handover procedure from a GSM/EDGE Radio Access Network, GERAN, system to a System Architecture Evolution, SAE, system,
receiving, by a User Plane Entity, UPE, a data forwarding tunnel identifier of a Long Term Evolution, LTE, access network, from a Mobility Management Entity, MME;
exchanging messages, by the UPE, with the MME for the MME to obtain a data forwarding tunnel identifier of the UPE;
informing, by the MME, a 2G Serving GPRS Support Node, 2G-SGSN, about the data forwarding tunnel identifier of the UPE;
receiving, by the UPE, data forwarded by the 2G-SGSN; and
forwarding, by the UPE, the data to the LTE access network.
in a handover procedure from a System Architecture Evolution, SAE, system to a GSM/EDGE Radio Access Network, GERAN, system,
receiving, by a User Plane Entity, UPE, a data forwarding tunnel identifier of a 2G Serving GPRS Support Node, 2G-SGSN, from a Mobility Management Entity, MME;
exchanging messages, by the UPE, with the MME for the MME to obtain a data forwarding tunnel identifier of the UPE;
informing, by the MME, a Long Term Evolution, LTE, access network about the data forwarding tunnel identifier of the UPE;
receiving, by the UPE, data forwarded by the LTE access network; and
forwarding, by the UPE, the data to the 2G-SGSN.
in a handover procedure from a UMTS Territorial Radio Access Network, UTRAN, system to a System Architecture Evolution, SAE, system;
receiving, by a User Plane Entity, UPE, a data forwarding tunnel identifier of a Long Term Evolution, LTE, access network from a 3G Serving GPRS Support Node, 3G-SGSN;
exchanging messages, by the UPE, with the 3G SGSN for the 3G-SGSN to obtain a data forwarding tunnel identifier of the UPE;
informing, by the 3G-SGSN, a source Radio Network Controller, RNC, about the data forwarding tunnel identifier of the UPE;
receiving, by the UPE, data forwarded by the source RNC; and
forwarding, by the UPE, the data to the LTE access network.
in a handover procedure from a System Architecture Evolution, SAE, system to a UMTS Territorial Radio Access Network, UTRAN, system,
receiving, by a User Plane Entity, UPE, a data forwarding tunnel identifier of a target Radio Network Controller, RNC, from a Mobility Management Entity, MME;
exchanging messages, by the UPE, with the MME for the MME to obtain a data forwarding tunnel identifier of the UPE;
informing, by the MME, a Long Term Evolution, LTE, access network about the data forwarding tunnel identifier of the UPE;
receiving, by the UPE, data forwarded by the LTE access network, and
forwarding, by the UPE, the data to the target RNC.
in einer Weiterreichungsprozedur von einem "GSM/EDGE Radio Access Network"-System, GERAN-System, zu einem "System Architecture Evolution"-System, SAE-System:
Empfangen einer Datenweiterleitungs-Tunnelkennung eines "Long Term Evolution"-Zugangsnetzes, LTE-Zugangsnetz, durch eine "User Plane Entity", UPE, von einer "Mobility Management Entity" MME;
Austauschen von Nachrichten mit der MME durch die UPE, damit die MME eine Datenweiterleitungs-Tunnelkennung der UPE erhält,
Informieren eines 2G-"Serving GPRS Support Node", 2G-SGSN, durch die MME über die Datenweiterleitungs-Tunnelkennung der UPE;
Empfangen von durch den 2G-SGSN weitergeleiteten Daten durch die UPE; und
Weiterleiten der Daten durch die UPE zu dem LTE-Zugangsnetz.
in einer Weiterreichungsprozedur von einem "System Architecture Evolution"-System, SAE-System, zu einem "GSM/EDGE Radio Access Network"-System, GERAN-System:
Empfangen einer Datenweiterleitungs-Tunnelkennung eines 2G-"Serving GPRS Support Node", 2G-SGSN, durch eine "User Plane Entity", UPE, von einer "Mobility Management Entity" MME;
Austauschen von Nachrichten mit der MME durch die UPE, damit die MME eine Datenweiterleitungs-Tunnelkennung der UPE erhält,
Informieren eines "Long Term Evolution"-Zugangsnetzes, LTE-Zugangsnetz, durch die MME über die Datenweiterleitungs-Tunnelkennung der UPE;
Empfangen von durch das LTE-Zugangsnetz weitergeleiteten Daten durch die UPE; und
Weiterleiten der Daten durch die UPE zu dem 2G-SGSN.
in einer Weiterreichungsprozedur von einem "UMTS Territorial Radio Access Network"-System, UTRAN-System, zu einem "System Architecture Evolution"-System, SAE-System:
Empfangen einer Datenweiterleitungs-Tunnelkennung eines "Long Term Evolution"-Zugangsnetzes, LTE-Zugangsnetz, durch eine "User Plane Entity", UPE, von einem 3G-"Serving GPRS Support Node", 3G-SGSN;
Austauschen von Nachrichten mit dem 3G-SGSN durch die UPE, damit der 3G-SGSN eine Datenweiterleitungs-Tunnelkennung der UPE erhält,
Informieren eines Quellen-"Radio Network Controller", Quellen-RNC, durch den 3G-SGSN über die Datenweiterleitungs-Tunnelkennung der UPE;
Empfangen von durch den Quellen-RNC weitergeleiteten Daten durch die UPE; und Weiterleiten der Daten durch die UPE zu dem LTE-Zugangsnetz.
in einer Weiterreichungsprozedur von einem "System Architecture Evolution"-System, SAE-System, zu einem "UMTS Territorial Radio Access Network"-System, UTRAN-System:
Empfangen einer Datenweiterleitungs-Tunnelkennung eines Ziel-"Radio Network Controller", Ziel-RNC, durch eine "User Plane Entity", UPE, von einer "Mobility Management Entity" MME;
Austauschen von Nachrichten mit der MME durch die UPE, damit die MME eine Datenweiterleitungs-Tunnelkennung der UPE erhält,
Informieren eines "Long Term Evolution"-Zugangsnetzes, LTE-Zugangsnetz, durch die MME über die Datenweiterleitungs-Tunnelkennung der UPE;
Empfangen von durch das LTE-Zugangsnetz weitergeleiteten Daten durch die UPE; und
Weiterleiten der Daten durch die UPE zu dem Ziel-RNC.
la MME est configurée pour échanger des messages avec l'UPE pour obtenir un identificateur de tunnel de renvoi de données de l'UPE, pour informer l'UPE d'un identificateur de tunnel de renvoi de données du réseau d'accès LTE, et pour informer le noeud 2G-SGSN de l'identificateur de tunnel de renvoi de données de l'UPE ; et
l'UPE est configurée pour recevoir des données renvoyées par le noeud 2G-SGSN, et pour renvoyer les données au réseau d'accès LTE.
la MME est configurée pour échanger des messages avec l'UPE pour obtenir un identificateur de tunnel de renvoi de données de l'UPE, pour informer l'UPE d'un identificateur de tunnel de renvoi de données du noeud 2G-SGSN et pour informer le réseau d'accès LTE de l'identificateur de tunnel de renvoi de données de l'UPE ; et
l'UPE est configurée pour recevoir des données renvoyées par le réseau d'accès LTE, et pour renvoyer les données au noeud 2G-SGSN.
le noeud 3G-SGSN est configuré pour échanger des messages avec l'UPE pour obtenir un identificateur de tunnel de renvoi de données de l'UPE, pour informer l'UPE d'un identificateur de tunnel de renvoi de données du réseau d'accès LTE et
pour informer le RNC source de l'identificateur de tunnel de renvoi de données de l'UPE ; et
l'UPE est configurée pour recevoir des données renvoyées par le RNC source, et pour renvoyer les données au réseau d'accès LTE.
la MME est configurée pour échanger des messages avec l'UPE pour obtenir un identificateur de tunnel de renvoi de données de l'UPE, pour informer l'UPE d'un identificateur de tunnel de renvoi de données du RNC cible et pour informer le réseau d'accès LTE de l'identificateur de tunnel de renvoi de données de l'UPE ; et
l'UPE est configurée pour recevoir des données renvoyées par le réseau d'accès LTE, et pour renvoyer les données au RNC cible.
dans une procédure de transfert d'un système de réseau d'accès radio GSM/EDGE, GERAN, vers un système à évolution d'architecture de système, SAE, recevoir, par une entité de plan utilisateur, UPE, un identificateur de tunnel de renvoi de données d'un réseau d'accès à technologie d'évolution à long terme, LTE, depuis une entité de gestion de mobilité, MME ;
échanger des messages, par l'UPE, avec la MME pour que la MME obtienne un identificateur de tunnel de renvoi de données de l'UPE, informant, par la MME, un noeud de support GPRS de desserte 2G, 2G-SGSN, relativement à l'identificateur de tunnel de renvoi de données de l'UPE ;
recevoir, par l'UPE, des données renvoyées par le noeud 2G-SGSN ; et
renvoyer, par l'UPE, les données au réseau d'accès LTE.
des moyens pour recevoir un identificateur de tunnel de renvoi de données d'un réseau d'accès à technologie d'évolution à long terme, LTE, depuis une entité de gestion de mobilité, MME ;
des moyens pour échanger des messages avec la MME pour que la MME obtienne un identificateur de tunnel de renvoi de données de l'UPE pour informer un noeud de support GPRS de desserte 2G, 2G-SGSN, relativement à l'identificateur de tunnel de renvoi de données de l'UPE ;
des moyens pour recevoir des données renvoyées par le noeud 2G-SGSN ; et
des moyens pour renvoyer les données au réseau d'accès LTE.
dans une procédure de transfert d'un système à évolution d'architecture de système, SAE, vers un système de réseau d'accès radio GSM/EDGE, GERAN, recevoir, par une entité de plan utilisateur, UPE, un identificateur de tunnel de renvoi de données d'un noeud de support GPRS de desserte 2G, 2G-SGSN, depuis une entité de gestion de mobilité, MME ;
échanger des messages, par l'UPE, avec la MME pour que la MME obtienne un identificateur de tunnel de renvoi de données de l'UPE, informant, par la MME, un réseau d'accès à technologie d'évolution à long terme, LTE, relativement à l'identificateur de tunnel de renvoi de données de l'UPE ;
recevoir, par l'UPE, des données renvoyées par le réseau d'accès LTE ; et
renvoyer, par l'UPE, les données au noeud 2G-SGSN.
des moyens pour recevoir un identificateur de tunnel de renvoi de données d'un noeud de support GPRS de desserte 2G, 2G-SGSN, depuis une entité de gestion de mobilité, MME ;
des moyens pour échanger des messages avec la MME pour que la MME obtienne un identificateur de tunnel de renvoi de données de l'UPE pour informer un réseau d'accès à technologie d'évolution à long terme, LTE, relativement à l'identificateur de tunnel de renvoi de données de l'UPE ;
des moyens pour recevoir des données renvoyées par le réseau d'accès LTE ; et
des moyens pour renvoyer les données au noeud 2G-SGSN.
dans une procédure de transfert d'un système de réseau d'accès radio territorial UMTS, UTRAN, vers un système à évolution d'architecture de système, SAE, recevoir, par une entité de plan utilisateur, UPE, un identificateur de tunnel de renvoi de données d'un réseau d'accès à technologie d'évolution à long terme, LTE, depuis un noeud de support GPRS de desserte 3G, 3G-SGSN ;
échanger des messages, par l'UPE, avec le noeud 3G-SGSN pour que le noeud 3G-SGSN obtienne un identificateur de tunnel de renvoi de données de l'UPE, informant, par le noeud 3G-SGSN, un contrôleur de réseau radio, RNC, source relativement à l'identificateur de tunnel de renvoi de données de l'UPE ;
recevoir, par l'UPE, des données renvoyées par le RNC source ; et
renvoyer, par l'UPE, les données au réseau d'accès LTE.
des moyens pour recevoir, par une entité de plan utilisateur, UPE, un identificateur de tunnel de renvoi de données d'un réseau d'accès à technologie d'évolution à long terme, LTE, depuis un noeud de support GPRS de desserte 3G, 3G-SGSN ;
des moyens pour échanger des messages avec le noeud 3G-SGSN pour que le noeud 3G-SGSN obtienne un identificateur de tunnel de renvoi de données de l'UPE pour informer un contrôleur de réseau radio, RNC, source relativement à l'identificateur de tunnel de renvoi de données de l'UPE ;
des moyens pour recevoir, par l'UPE, des données renvoyées par le RNC source ; et
des moyens pour renvoyer, par l'UPE, les données au réseau d'accès LTE.
dans une procédure de transfert d'un système à évolution d'architecture de système, SAE, vers un système de réseau d'accès radio territorial UMTS, UTRAN, recevoir, par une entité de plan utilisateur, UPE, un identificateur de tunnel de renvoi de données d'un contrôleur de réseau radio, RNC, cible depuis une entité de gestion de mobilité, MME ;
échanger des messages, par l'UPE, avec la MME pour que la MME obtienne un identificateur de tunnel de renvoi de données de l'UPE, informant, par la MME, un réseau d'accès à technologie d'évolution à long terme, LTE, relativement à l'identificateur de tunnel de renvoi de données de l'UPE ;
recevoir, par l'UPE, des données renvoyées par le réseau d'accès LTE ; et
renvoyer, par l'UPE, les données au RNC cible.
des moyens pour recevoir un identificateur de tunnel de renvoi de données d'un contrôleur de réseau radio, RNC, cible depuis une entité de gestion de mobilité, MME ;
des moyens pour échanger des messages avec la MME pour que la MME obtienne un identificateur de tunnel de renvoi de données de l'UPE pour informer un réseau d'accès à technologie d'évolution à long terme, LTE, relativement à l'identificateur de tunnel de renvoi de données de l'UPE ;
des moyens pour recevoir des données renvoyées par le réseau d'accès LTE ; et
des moyens pour renvoyer les données au RNC cible.