Combined handover of the circuit-switched (CS) and packet-switched (PS) resources

[0001] This application claims priority from U.S. Provisional Patent Application No. 60/672,686 filed on Mar. 30, 2005.

[0002] Dual Transfer Mode (DTM) is specified in 3GPP TS 43.055 V6.7.0 (2004-11), 3^rd Generation Partnership Project; Technical Specification Group GSM/EDGE, Radio Access Network; Dual Transfer Mode (DTM); Stage 2 (Release 6). In this dual transfer mode, where the mobile station (MS) has simultaneous Circuit-Switched (CS) and Packet-Switched (PS) connections, a handover procedure is defined only for the CS resources. The details of a handover of CS resources is being specified for general handover purposes in 3GPP TS 23.009 V6.0.0 (2004-12), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Core Network; Handover procedures (Release 6).

[0003] In DTM handover, the PS resources are torn down and only re-established once the MS has successfully completed the handover. The handover of PS resources is being standardized for general purposes in the 3GPP TSG (Technical Specification Group) “GERAN” (GSM (Global System for Mobile Communication) EDGE (Enhanced Data Rates for GSM Evolution) Radio Access Network) in the technical specification 3GPP TS 43.129 v6.0.0 (2004-11), 3^rd Generation Partnership Project; Group GERAN, Packet-switched handover for GERAN A/Gb mode; Stage 2 (Release 6).

[0004] FIG. 1 of TS 43.129 shows a reference architecture for PS handover in GERAN A/Gb mode including a Core Network (CN) with an MSC connected to a first SGSN via a Gs interface, the first SGSN connected to a second SGSN and to a GGSN via Gn interfaces, the MSC also connected to a PSTN with the first SGSN connected to other networks via a Gp interface, and with the GGSN connected to other networks via Go and Gi interfaces. For the radio access network, a BSS/GERAN is shown connected to the MSC of the CN via an A interface and to the first SGSN via a Gb interface. The BSS/GERAN includes a BSC connected to BTSs by Abis interfaces. One of the BTSs is shown in communication with an MS via a Um (wireless) interface. An RNS (or another BSS) is also shown with an RNC (or BSC) connected to NodeBs each having cells with Uu interfaces also capable of communicating with the MS. The RNC (or BSS) is shown connected to the MSC via an Iu-CS interface and to the second SGSN via an Iu-PS interface. The figure shows both user traffic and signalling on most of these interfaces. It will be understood from the foregoing that in the case of a handover involving both CS and PS resources, there is a longer path for the PS signalling which will take longer than the CS signalling.

[0005] As suggested above, the DTM procedures specified in 3GPP TS 43.055 only enable the handover of CS resources, while PS resources have to be (re-)established after the MS's successful access in the new cell.

[0006] It has been shown that for such an MS in DTM, the PS service interruption at handover is substantial (3.4 s in the Inter-BSC Inter-MSC Inter-SGSN case, with approximately 2.7 s induced by Routing Area Update procedure). See PS Service Interruption Estimations for DTM Operation, 3GPP TSG GERAN #17bis, Edinburgh, Scotland, 12-16 Jan. 2004, Source: Siemens; Tdoc G2-040049, Agenda Item 5.4.6.2. This interruption is not tolerable for services with stringent delay requirements, e.g., PS conversational video. Thus, the handover in the existing TS 43.055 specification introduces a problematic interruption of the PS service.

[0007] While Dual Transfer Mode (DTM) Enhancements have been proposed as a work item for GERAN A/Gb mode in 3GPP Release 6 (see Reduction of PS service interruption in Dual Transfer Mode in TSG GERAN #17, Budapest, Hungary, 17-21 Nov. 2003 in Tdoc GP-032548, Agenda item 6.7, see also GERAN Project Scheduling and open issues for GERAN in 3GPP GERAN TSG#22, Cape Town, 8-12 Nov. 2004 (GP-042836)), there is still an outstanding need to define improvements enabling combined handover of the CS and PS resources in dual transfer mode in order to minimize the end-to-end delays for real-time PS services. The service interruption required by the real-time PS services is a maximum of 150 ms.

[0008] There is no prior art solution enabling combined (parallel or simultaneous) handover of CS and PS resources.

[0009] The problem could be circumvented if the handover of the PS resources were to be enabled together with the handover of the CS resources either in parallel or simultaneously.

[0010] A problem in enabling the combined handover of CS and PS resources in parallel in DTM is that the CS and PS handover procedures are executed independently of each other and hence there might be a risk that one procedure completes before the other, for example, CS handover is completed prior to the PS Handover completion. This would lead to failing a handover for one of the CS or PS resources in DTM, although there were resources allocated in the target cell, the DTM handover would not be able to be performed. Therefore, there is a need to synchronize the PS and CS handover procedures in the source and target systems, such that the MS in DTM can continue with both the CS and PS sessions after handover at the same time.

[0011] A new mechanism is provided, according to the present invention, which facilitates the combined handover of PS resources and CS resources in dual transfer mode. The new mechanism is particularly applicable to an MS in DTM with an ongoing CS service and one or more active PS services.

[0012] The new mechanism on combined handover of CS resources and PS resources can be accomplished in two different embodiments:

• • [0013] 1. Utilizing the PS handover procedures that are currently being standardized in TSG GERAN [3GPP TS 43.129] and CS handover procedures as defined in 3GPP TS 23.009 in parallel—“CS and PS handover in parallel”
  • [0014] 2. Enhancing CS handover procedure defined in 3GPP TS 23.009 to support the handover of the PS resources as well—“simultaneous CS and PS handover”.

[0015] Above mentioned embodiments are independent of each other.

[0016] A basic principle followed, according to the first embodiment of the present invention, is that the CS and PS handover procedures are enhanced to enable the synchronization of the combined handover of the PS and CS resources in DTM.

[0017] The new mechanism minimizes the PS end-to-end delays in DTM. The principles of CS and PS handover are utilized to improve the performance of DTM in terms of end-to-end delay. This will not only allow for reducing the PS service interruption of all PS services while in DTM, but in particular for enabling the provision of real-time PS services in DTM.

[0018] For an MS in DTM, the combined handover of the PS resources and the CS resources is enabled by either utilizing in parallel the CS handover procedure in 3GPP TS 23.009 and the PS handover procedure as defined in 3GPP TS 43.129 or enhancing the CS handover procedure specified in the above-mentioned 3GPP TS 23.009 to support the handover of the PS resources as well. With this mechanism, the MS will continue with the packet flows in the new cell, provided PS resources are available. In this manner the service interruption will be minimized resulting in a better performance for the PS service while the MS is in DTM. Apart from the enhancements to the CS handover procedure, additional functionality is also needed in the PS domain to enable the resource allocation in the target cell for the PS handover.

[0019] An objective is to enable the handover of the CS and PS resources without affecting the performance of the CS handover. The CS handover is not delayed or interfered with due to the handover of PS resources described in both embodiments.

[0020] The first embodiment may provide synchronization of the handover PS and the CS resources in the source BSS and in the target BSS. The mechanism of synchronizing the handover of the PS and CS resources in the DTM applies to both CS and PS handover procedures. This mechanism is supported by the following functions:

• • [0021] resource indications on the CS and PS handover signalling to indicate to target cell network nodes that the CS and PS handover is ongoing at the same time for the same MS;
  • [0022] allocated resource indications on the CS and PS handover signalling to indicate to the source cell nodes that there are CS and PS resources available in the target cell;
  • [0023] Management of the synchronization of the CS and PS handover in the source and target cell.

[0024] The second embodiment for the simultaneous handover of the CS and the PS resources provided according to the present invention is based on the CS handover procedure defined in 3GPP TS 23.009 with the:

• • [0025] PS resource indication on the CS handover signalling to indicate to target cell network nodes that the handover of the CS handover and PS resources is ongoing for the MS;
  • [0026] Additional functionality over the Gb interface (between BSC ad SGSN) and the Gn interface (between SGSNs) in order to allocate PS resources in the target cell; and
  • [0027] Allocated PS resources indication on the CS handover signalling to indicate to the source cell nodes that there are CS and PS resources available in the target cell.

[0028] These and other objects, features and advantages of the present invention will become more apparent in light of the detailed description which follows.

[0029] FIG. 1 presents a PS Indication and CS Indication transfer procedure between the source BSS and target BSS via the CN, according to a first embodiment of the present invention.

[0030] FIG. 2 presents a PS Resource Availability and CS Resource Availability transfer procedure executed between the target BSS and the source BSS via the CN after the procedure of FIG. 1, according to the first embodiment of the present invention.

[0031] FIG. 3 presents an Inter-BSS, Intra-MSC, Inter-SGSN DTM Handover, Network Mode of Operation (NMO) I, preparation phase, including most of the steps of FIGS. 1 and 2 in a larger context, according to the first embodiment of the present invention.

[0032] FIG. 4 presents the Inter-BSS, Intra-MSC, Inter-SGSN DTM Handover, NMO I, execution phase including the Handover Commands of FIG. 2, according to the first embodiment of the present invention.

[0033] FIG. 5 shows handover of the PS resources with the CS handover, allocation of the CS and PS resources, according to a second embodiment of the present invention.

[0034] FIG. 6 shows handover of the PS resources with the CS handover in the same time, PS resource availability indication, according to the second embodiment of the present invention.

[0035] FIG. 7 shows an example of the applicability of the invention for the case when the BSS and SGSN change but the MSC remains the same and a Gs interface is available in a preparation phase, according to the second embodiment of the present invention.

[0036] FIG. 8 shows the example of FIG. 7 in an execution phase, according to the present invention, according to the second embodiment of the present invention.

[0037] FIG. 9 shows a source BSS according to the first embodiment of the present invention.

[0038] FIG. 10 shows a source BSS according to the second embodiment of the present invention

[0039] FIG. 11 shows a target BSS according to the first embodiment of the present invention.

[0040] FIG. 12 shows a target BSS according to the second embodiment of the present invention.

[0041] FIG. 13 shows a mobile station according to either the first embodiment or the second embodiment of the present invention.

[0042] FIG. 14 shows a signal processor which could be used in any of the embodiments of the present inventions as shown for instance in FIGS. 9-13.

[0043] As mentioned in the Background section above, the dual transfer mode (DTM) procedures are presently defined in 3GPP TS 43.055 in such a way that, for an MS in DTM, only the CS resources may be handed over. At handover in DTM, the PS resources are released and once the handover is successfully completed, only then are the PS resources re-established in the target cell. As mentioned above, the service interruption is about 3.4 s in the Inter-BSC—Inter-MSC—Inter-SGSN case, with approximately 2.7 s introduced by the Routing Area Update procedure (see the above-mentioned PS Service Interruption Estimations for DTM Operation in 3GPP TSG GERAN #17bis, Edinburgh, Scotland, 12-16 Jan. 2004, Tdoc G2-040049, Agenda item 5.4.62). Such delays are not acceptable for real-time PS services.

[0044] In order to minimize the end-to-end delays in DTM for the PS services and in particular for the real-time PS data flow, as pointed out above, there is a need for a new mechanism that enables combined handover of the CS and PS resources either in parallel or simultaneously. This invention utilizes the existing PS and CS Handover procedures in order to support either the parallel or simultaneous handover of both PS and CS resources for an MS in dual transfer mode.

“CS and PS Handover in Parallel”—Utilizing Both CS Handover and PS Handover Procedures

[0045] As mentioned above, there is a problem in enabling the parallel handover of CS and PS resources in DTM in that the CS and PS handover procedures are executed independently of each other. Hence, there is a risk that one procedure completes before the other, for example, CS handover is completed prior to the PS handover completion. This would lead to failing a handover for one of the CS or PS resources in DTM, although there were resources allocated in the target cell, the DTM handover cannot be performed. Therefore, there is a need to synchronize the PS and CS handover procedures in the source and target systems, such that the MS in DTM can continue with both the CS and PS session after handover at the same time. A basic principle followed according to the present invention is that the CS and PS handover procedures will be enhanced to enable the synchronization of the handover of the PS and CS resources in DTM.

PS Indication and CS Indication IEs

[0046] Referring now to FIG. 1, a PS Indication IE (Information Element) and a CS Indication IE can be provided in parallel, according to the invention, facilitated by synchronization of the handover of both CS and PS resources by synchronizing CS and PS handover procedures.

[0047] Two IEs may be used to allow for synchronizing the PS handover and CS handover in the target BSS. These indications are set by a source BSS 10 and only used by a target BSS 12. The target BSS waits for both a HANDOVER REQUEST message on a line 118 and a PS HANDOVER REQUEST message on a line 119 before it sends acknowledgments on lines 130a and 131 (see FIG. 2) to a CN 14:

• • [0048] PS Indication IE is sent (see FIG. 1) in a HANDOVER REQUIRED message (BSS->CN) on a line 116 and the HANDOVER REQUEST message (CN->BSS) on the line 118 within an Old BSS to New BSS transparent container (see 3GPP TS 48.008).
  • [0049] CS Indication IE is sent in a PS HANDOVER REQUIRED message (BSS->CN) on a line 117 and the PS HANDOVER REQUEST message (CN->BSS) on the line 119 within a Source BSS to Target BSS container (see 3GPP TS 43.129).
    PS Resources Available IE and CS Resources Available IE

[0050] Two additional new IEs are sent to the source BSS 10 (see FIG. 2) by the target BSS 12 in order to synchronize the handover in the backward direction:

• • [0051] PS resources available IE is sent in a HANDOVER REQUEST ACKNOWLEDGE message (BSS->CN) on the line 130a and in a HANDOVER COMMAND message (CN->BSS) on a line 140. The PS resources available IE may be used by an MSC in the CN to indicate to the MS that the data transmission can continue in case of partial PS handover failure.
  • [0052] CS Resources available IE is sent in a PS HANDOVER REQUEST ACKNOWLEDGE message (BSS->CN) on the line 131 and in a PS HANDOVER REQUIRED message (CN->BSS) on a line 141.
    Source and Target BSS DTM Handover Timers for Management of the Synchronization of the CS and PS Resource Allocation

[0053] There are two timers defined:

• • [0054] Target BSS timer (T1) 150 (see FIG. 2)
    • [0055] T1 is defined in the target BSS 12.
    • [0056] The purpose of this timer is the management of the CS and PS resource allocation needed for performing DTM handover. The CS handover has priority with respect to PS handover and it shall for example not be delayed due to PS resource allocation, which can be longer than CS handover due to core network signaling in particular, in case of SGSN change. However for a limited amount of time i.e. the duration or value of timer T1, the target BSS can wait for the PS handover signaling in order to prepare the DTM handover information (CS and PS resource availability) for the source BSS and consequently indicate the CS and PS resource availability in the CS and PS handover signaling. The value of the timer T1 should be small such that it does not impact the CS handover performance.
    • [0057] The target BSS has to wait for both handover request messages (HANDOVER REQUEST and PS HANDOVER REQUEST messages on the lines 118, 119) with the CS and the PS information in order to be able to build the transparent containers sent from the target BSS 12 needed by the source BSS 10 to build the information needed for the DTM HANDOVER COMMAND message.
  • [0058] The definition of the timer T1 is given below:
    • [0059] Timer T1
      • [0060] The timer T1 is started upon receipt of the CS handover message indicating DTM handover, i.e. the HANDOVER REQUEST message on the line 118 with the new PS indication IE indicating that PS handover is to happen as well in the target BSS 12.
      • [0061] The timer T1 is stopped at the sending of the last acknowledge message to the CS and PS handover requests, i.e. HANDOVER REQUEST ACKNOWLEDGE message on the line 130a with the new PS resources available IE indicating that PS resources are available or the PS HANDOVER REQUEST ACKNOWLEDGE message on the line 131 with the new CS Resources available IE indicating that CS resources are available messages to the MSC or SGSN correspondingly in the CN.
      • [0062] At the expiry of the timer T1, if PS handover fails (e.g. the target BSS has not received the PS HANDOVER REQUEST message on the line 119 from the SGSN in the CN 14 or it has not enough radio resources), the target BSS shall for example send the HANDOVER REQUEST ACKNOWLEDGE message (with PS Resources available IE indicating that PS resources are not available) on the line 130a to the MSC in the CN 14. In this case only the CS handover continues. The allocated PS resources will be utilized/allocated after the successful access of the MS in the target cell. If the CS handover fails then a HANDOVER FAILURE message (not shown) is sent to the MSC in the CN 14 by the target BSS 12.
      • [0063] The value of the timer T1 shall, e.g., be defined so that CS handover is not delayed too long since it has priority over PS side handover.
  • [0064] Source BSS timer (T2) 160
    • [0065] Timer T2 160 is defined in the source BSS 10.
    • [0066] The purpose of this timer is to enable the source BSS to build the DTM HANDOVER COMMAND (to be sent to the MS; see FIG. 4, line 180) based on the information on the CS and PS resource allocation it receives from the target BSS in the messages on the lines 140, 141 in FIG. 2. The CS handover has priority with respect to PS handover and it shall not be delayed because of PS handover, which can be longer due to core network signaling in particular, as already mentioned above, in case of a change in the SGSN. However, for a limited amount of time, i.e., the duration or value of timer T2, the source BSS should wait for the PS handover signaling in order to prepare the DTM HANDOVER COMMAND message on the line 180 for the MS (again, see FIG. 4). The value of the timer T2 should be chosen such that it does not impact the CS handover performance. The value of the timer T2 is larger than the value of the timer T1.
    • [0067] The source BSS 10 has to wait for both handover command messages (PS HANDOVER REQUIRED ACKNOWLEDGE message on the line 141 and HANDOVER COMMAND message on the line 140 in FIG. 2) with the CS and the PS information in order to be able to build the radio interface message DTM HANDOVER COMMAND message for the MS. The definition of the timer T2 is given below:
      • [0068] Timer T2
        • [0069] The timer T2 is started upon receipt of the 1^st message indicating DTM handover, i.e. either HANDOVER COMMAND message on the line 140 or PS HANDOVER REQUIRED ACKNOWLEDGE message on the line 141 in the source cell.
        • [0070] The timer T2 is stopped when the source BSS has received both HANDOVER COMMAND and PS HANDOVER REQUIRED ACKNOWLEDGE messages on the lines 140, 141.
        • [0071] At the expiry of the timer T2, the source BSS may send again the HANDOVER REQUIRED message on the line 116 and for PS HANDOVER REQUIRED message on the line 117 to the CN 14 to signify the restart of the handover for CS domain or CS and PS domain.
        • [0072] The value of the timer T2 shall be defined so that CS handover is not delayed too long since it has priority over PS side handover.
          NOTE: In the above, priority is given to the CS service; however the invention is not restricted to that case.
          Second Embodiment—“Simultaneous CS and PS Handover”—Enhancements to the CS Handover Procedure

[0073] In order to support the simultaneous handover of the PS resources with the CS resources at handover in DTM, according to the second embodiment, the following enhancements are needed to the CS handover procedure:

[0074] BSS side

• • [0075] Addition of signalling for provision of PS Information during CS handover, enabling PS handover
  • [0076] Indication of PS resource availability in the target cell from the target BSS (Base Station Subsystem) to the MSC (Mobile Switching Center);
  • [0077] Transmission of the Routing Area Code information, old TLLI (Temporary Logical Link Identity) or IMSI (International Mobile Subscriber Identity), from the source BSS to the new SGSN (Serving GPRS Support Node), when SGSN changes;
  • [0078] Management of the CS and PS resources allocation in the source and target BSS.

[0079] MSC side

• • [0080] New procedure over Gs interface (between MSC and SGSN) when Gs interface is available in order to indicate the completion of the handover of the PS resources to SGSN.

[0081] These enhancements are described in detail below:

[0082] PS Information

• • [0083] Referring to FIG. 5, information about the utilized PS resources in a source cell need to be passed from the source BSS 10 to the target BSS 12 (via CN 14) to allow for PS handover to the target cell. This information may be passed transparently through the core network 14, by including a new Information Element (IE) within a HANDOVER REQUIRED message (BSS>CN) on a line 16 and HANDOVER REQUEST message (CN>BSS) on a line 18 used at CS handover.

[0084] New procedure to enable SGSN context exchange during handover

[0085] In case the SGSN changes at handover, in order to identify the old SGSN from which the SGSN Context is downloaded, the new SGSN needs to know the old Routing Area Identifier (RAI), as well as the identification of the MS through either the old TLLI or IMSI. A new procedure (see FIG. 5) for getting this information to the target BSS is described below:

• • [0086] the old Routing Area Code (RAC) may be passed within the HANDOVER REQUIRED message on the line 16 and the HANDOVER REQUEST message on the line 18 from the source BSS 10 to the target BSS 12 via the CN 14 as part of the target cell identifiers.
  • [0087] the IMSI may be added by an MSC in the CN 14 to the HANDOVER REQUEST message on the line 18 sent to the target BSS 12. Alternatively, the old TLLI information can be sent by the source BSS 10 transparently to the target BSS 12 through the CN 14 by including it in HANDOVER REQUIRED message (BSS>CN) on the line 16 and the HANDOVER REQUEST message (CN>BSS) on the line 18 used at CS handover.

[0088] Management of the CS and PS resource allocation

[0089] The Target BSS 12 has to wait for the handover message (HANDOVER REQUEST message on the line 18) with the CS and the PS information in order to be able to operate the handover for both CS and PS resources. The Target BSS 12 builds the final HANDOVER COMMAND message on a line 40 (see FIG. 6), which is passed to the source BSS 10 via the CN 14.

[0090] Upon reception of the HANDOVER COMMAND message the Source BSS will send it to the MS as a message 180 (see FIG. 8) on the air interface provided that this message has arrived prior to the timer expiry in the source BSS. Source BSS starts the timer after the HANDOVER REQUIRED message has been sent on the line 16 to the CN and stops it after the HANDOVER COMMAND message is received on the line 40 from the CN.

[0091] Allocation of the PS Resources

[0092] Referring to FIG. 6, information about the allocated PS resources in the target cell, need to be passed from the target BSS 12 to the source BSS 10 to allow for PS handover to the target cell. This information may be sent as a new IE within a HANDOVER REQUEST ACK message (BSS>CN) on a line 30 and a HANDOVER COMMAND message (CN>BSS) on a line 40 used at CS handover. In case of the change of the MSC this information should be sent between the CN nodes as well.

[0093] New procedure over Gs interface (between MSC and SGSN) when Gs interface is supported in order to indicate the completion of the handover of the PS resources to SGSN

[0094] MSC reports the status of the PS resource allocation in the target BSS to the SGSN if a Gs interface is available by means of a new procedure. This new procedure is initiated as shown in FIG. 8 when a HANDOVER COMPLETE message on a line 100 is received by the MSC from the target BSS (BSS2 in FIG. 8). A new Handover Status message on a line 102 is sent from the MSC to the new SGSN only if the information on the availability of the PS resources indicated by a new IE is received at the MSC within the HANDOVER REQUEST ACK message on a line 30 as shown in FIG. 6 which may first go from the BSS2 to the MSC and then from the MSC to the old SGSN over the Gs interface and thence to the new SGSN over the Gn interface (between the old and new SGSNs). After receiving this message an appropriate SGSN may initiate a Delete BSS PFC procedure to the source BSS (BSS1 in FIG. 8) to release the resources in the old cell.

[0095] In this case another two alternative solutions are possible, as also shown in FIG. 8:

• • [0096] First solution is to send a Dummy LLC PDU from the MSC to the new SGSN to start the release of the BSS PFCs in the source cell.
  • [0097] Second solution is that the source BSS may start deleting BSS PFC information if the BSS detects user inactivity (see 3GPP TS 48.018).
    Additional Functionality over the Gb and Gn Interface

[0098] In order to support the handover of the PS resources the following enhancements are hereby recommended to the PS domain procedures over the Gb, Gn, Gs interfaces (Gs is between BSC and SGSN):

[0099] BSS side

• • [0100] New triggering point for the Download BSS PFC procedures

[0101] SGSN side

• • [0102] New Enhanced SGSN Context procedures over the Gn interface are defined

[0103] These enhancements are described in detail below:

[0104] New triggering action for the Download BSS PFC procedure, over the Gb interface, is defined in this case. The target BSS 12, as shown in FIG. 5, initiates this procedure upon receiving the HANDOVER REQUEST message (CN->BSS) on the line 18 from the MSC within CN 14. The target BSS 12 will have to wait for both the HANDOVER REQUEST message received on the line 18 from the MSC and a CREATE BSS PFC message received on a line 110 from the SGSN also within CN 14 in order to form the HANDOVER REQUEST ACK message on the line 30 (see FIG. 6), sent back to the MSC. The MSC then forwards the radio information contained into the LAYER 3 information transparent container to the source BSS 10 within the HANDOVER COMMAND message (CN->BSS) on the line 40 as also shown in FIG. 6. The transparent container transfers either the HANDOVER COMMAND message with both PS and CS resource indications or the HANDOVER COMMAND message with only a CS resource indication in a case where, e.g., a waiting timer expires in the target BSS or PS resources could not be allocated.

[0105] >Enhanced SGSN Context procedures

[0106] A new procedure for transferring the information from the old SGSN to the new SGSN (over a Gn interface) is defined during the preparation phase of the handover. The new procedure consists of defining two new GTP messages exchanged between the old SGSN to the New SGSN (see FIG. 7).

[0107] These two messages are:

• • [0108] 1. ENHANCED SGSN CONTEXT REQUEST message on a line 130; and
  • [0109] 2. ENHANCED SGSN CONTEXT RESPONSE message on a line 132.

[0110] These messages are exchanged between the New SGSN and the Old SGSN. The new SGSN receives a DOWNLOAD BSS PACKET FLOW CONTEXT REQUEST (old RAI, old TLLI, IMSI, Packet Flow Id) message on a line 134 from the target BSS (BSS2 in FIG. 7) as also shown in FIG. 5. If the old TLLI is not available to the BSS, the IMSI has to be sent in this case. The new SGSN may derive the old SGSN from the old RAI and IMSI (or old TLLI) and send the SGSN Context Request message to this old SGSN. Otherwise, the new SGSN derives the old SGSN from the old RAI.

[0111] The New SGSN sends ENHANCED SGSN CONTEXT REQUEST (New SGSN Address, IMSI, old TLLI, old RAI) message on the line 130 to the old SGSN in order to download the MM Context and PDP context.

[0112] When the new SGSN receives the ENHANCED SGSN CONTEXT RESPONSE message (MM Context, PDP Context, XID parameters (see 3GPP TS 3GPP TS 43.129)) on the line 132 from the old SGSN it then initiates the Create BSS PFC procedures which then allocate the resources in the target BSS. This is shown by a Create BSS PFC message on the line 110 from the new SGSN to the target BSS (BSS2 in FIG. 7) as also shown in FIG. 5, in a slightly different way, from the Target BSS 12 to the CN 14 (which of course includes old and new SGSNs, MSCs, GGSNs, etc.).

[0113] FIG. 9 shows a source BSS 10 according to the first embodiment of the present invention interchanging signals with the core network 14 as shown in FIGS. 1-4. The source BSS 10 of FIG. 9 includes a signal processor 200-9 which may be an integrated circuit (in whole or in part) or which may be of the type shown for instance in FIG. 14, without limitation. As such, it may include a central processing unit 202, a random access memory 204, a read only memory 206, an input/output device 208, and a data, address and control bus 210 interconnecting the aforementioned components of the signal processor. In such a signal processor, a set of coded instructions written in a computer programming language are stored on the read only memory (ROM) 206, typically in complied form, i.e., human-readable source code may be compiled into machine-readable instructions and stored on the computer readable medium 206 for retrieval by the CPU 202 for execution in the sequence laid out by the programmer. Of course, the stored code could be interpreted “on-the-fly” instead of complied. Intermediate results and calculations carried out according to the instructions may be stored in a random access memory (RAM) 204 which serves the purpose of storing intermediate results temporarily. The signal processor may be responsive to input signals received by the input/output device 208 for processing and may, in response thereto, provide output signals emerging from the same input/output device or another similar device. The source BSS 10 of FIG. 9 is itself shown having an input/output device 220 which may be different from the input/output device 208 of the signal processor 200 so that it may handle signals of various kinds interfacing with the environment outside the source BSS. As such, it may include a transmitter 222 and a receiver 224. The transmitter 222 is responsive to a signal on a line 224 from the signal processor 200-9 for providing the Handover Required signal on the line 116 and the PS Handover Required signal on the line 117, both of which are shown in FIGS. 1 and 3. The input/output device 220 also includes a receiver 224 that is responsive to the Handover Command signal on the line 140 and the PS Handover Required Acknowledge signal on the line 141 for providing a signal on a line 226 to the signal processor 200-9. In general, the signal processor 200-9 in the source BSS 10 will also be responsive to measurements made by the MS and also by itself concerning the radio environment, particularly as the MS moves about in the cell and as it moves from cell-to-cell. The types of measurement activities carried out by the MS are beyond the scope of the present invention but details thereof can be found for example in the 3GPP specification such as TS 43.055 mentioned above. The details of the radio information as far as handover is concerned is given in 3GPP-TS 24.008 and the relevant network information is given in 3GPP-TS 23.009. In any event, the PS Handover Required message on the line 117 of FIGS. 1 and 3 may contain Source BSS to Target BSS Transparent Container information element (IE) carrying a CS Indication IE having contents that uniquely identify, for this MS, the handover attempt, and may be identical to the contents of a PS Indication IE included in the Handover Required message on the line 116. Similarly, a Target Cell Identifier IE may be included in the message to identify the same cell as the one specified in a preferred cell Identifier List information element in the corresponding Handover Required message on the line 116. Regarding the signals on the lines 140 and 141 shown in FIG. 9, and received by the receiver 224 and then provided on the line 226 to the signal processor 200-9, the source BSS 10 will wait until it has received both the Handover Command signal on the line 140 and the PS Handover Required signal on the line 141 before stopping the timer 160 and sending the Handover Command signal on the line 180 of FIG. 4 and ending the PS handover required procedure. If the timer 160 of FIG. 2 times out before receiving both signals on the lines 140 and 141 then the source BSS 10 will do one of the following, depending on which signals are received: (1) if the source BSS 10 has received the PS Handover Required Acknowledge signal on the line 141 but not the Handover Command signal on the line 140 and the timer has expired, it may initiate a PS handover cancellation procedure; (2) if the source BSS 10 has received a Handover Command signal on the line 140 but not the PS Handover Required Acknowledge signal on the line 141 and the timer 160 expires, it may send a handover failure message to the MSC with the cause indicated, e.g., “timer expired;” (3) if the source BSS 10 received neither the signal on the line 140 or the line 141 then the handover procedure may be terminated and no message sent to either the MSC or the SGSN; any message or PDU relating to this handover attempt which is received from the MSC or the SGSN after the expiration of the timer 160 may be discarded.

[0114] If the source BSS 10 receives a negative acknowledgement in response to the handover required message on the line 116 and a handover required reject message then the handover procedure is terminated and no message is sent to either the MSC or the SGSN.

[0115] If the source BSS 10 receives a negative acknowledgement to the PS handover required signal on the line 116 with a cause value indicating an SGSN failure and a handover command message then the source BSS 10 sends a handover failure message to the MSC with the cause of the failure indicated as an “SGSN failure” and no message is sent to the MS.

[0116] If the source BSS receives a positive acknowledgement and a handover required reject message then the source BSS 10 initiates a PS handover cancel procedure and no message is sent to the MS.

[0117] Thus, this embodiment provides synchronization of the handover of PS and CS resources in the source BSS 10 and in the target BSS 12. The mechanism of synchronizing the handover of the PS and the CS resources in the DTM applies to both CS and PS handover procedures and the mechanism is supported by resource indications on the CS and PS handover signaling to indicate to the target cell network nodes that the CS and PS handover is ongoing at the same time for the same MS.

[0118] Referring to FIG. 10, it is similar to FIG. 9 with respect to the source BSS 10 of FIGS. 5 and 6 as well as FIGS. 7 and 8 which all pertain to the second embodiment of the present invention. The source BSS 10 of FIG. 10 includes a signal processor 200-10 which may take the form shown in FIG. 14 as described previously or some other form such as an integrated circuit. The signal processor may provide output signals shown generally by a signal on a line 230 to a transmitter 232 within an input/output device 234. The transmitter device 232 provides the Handover Required signal on the line 16 of FIG. 5 and as also shown in FIG. 7 as being received by the MSC of the core network 14. The Handover Command signal on the line 40 of FIG. 6 is also shown in FIG. 8 sent from the MSC of the core network 14 to the source BSS 10. In FIG. 10, this Handover Command signal on the line 40 is shown being received by a receiver 240 which in turn provides an output signal on a line 242 to the signal processor 200-10. The details of what is carried out in the signal processor 200-10 and the signaling processes associated with FIG. 10 are similar to those already described in connection with FIGS. 5-8 above.

[0119] FIG. 11 shows a target BSS 12 such as shown in the first embodiment of FIGS. 1 and 2 receiving the Handover Request signal on the line 118 and the PS Handover Request signal on the line 119 (the same signals as shown in FIGS. 1 and 3). These are shown being received by a receiver 250 which in turn provides an output signal on a line 252 to a signal processor 200-11 which may be a chip or may have a structure similar to that shown in FIG. 14. As shown in FIG. 3, the new SGSN is the core network 14 element that sends the PS Handover Request message on the line 119 to the target BSS 12. It includes the NAS container for PS handover corresponding to the PFCs to be set-up (except in the case of intra-SGSN PS handover). As mentioned above, the timer 150 is started in response to the signal on the line 119. Upon receipt of the PS handover request signal on the line 119 containing a CS indication information element (i.e., that a DTM handover procedure is ongoing), then the target BSS 12 can proceed in a number of different ways. First, if the timer 150 is not running then it may start the timer. When both the PS Handover Request message on the line 119 and the Handover Request message on the line 118 are both received and the contents of both the CS indication information element and the PS indication information element are identical, the target BSS 12 stops the timer 150, attempts to create a new BSS context for the MS, creates PFC's according to the received ABQP (Aggregate BSS QoS Profile) parameters and allocates both dedicated resources and TBF resources within the capabilities of the mobile station (where dedicated resources are allocated for instance as described in 3GPP-TS 48.008). The signal processor provides and output signal on the line 254 to a transmitter 256 that provides the Handover Request Acknowledge signal on the line 130a and the PS Handover Request Acknowledge signal on the line 131. The PS Handover Request Acknowledge message on the line 131 may include a Target BSS to Source BSS Transparent Container i.e., a complete DTM Handover Command message such as described in 3GPP-TS 44.060. In the case of an attempted DTM handover when no shared resources are allocated, the target BSS 12 may continue with the corresponding handover resource allocation procedure, allocating only dedicated resources (see 3GPP-TS 48.008). If the timer 150 expires and the target BSS 12 has received a PS-Handover Request message on the line 119, the target BSS may terminate the PS Handover Request procedure by sending a PS Handover Request Negative Acknowledgement to the SGSN with a cause indicated for instance “timer expiration.” The target BSS 12 need only store the mobile station's identity and the CS indication IE for this handover attempt if timer 150 expires. Otherwise, no knowledge of the MS should be kept by the target BSS 12. It should be noted that the duration for which the target BSS stores the MS identity and CS indication E is implementation specific. However, it should be long enough to allow the new BSS to determine whether or not a handover request message corresponds to a previously terminated DTM handover attempt. If the A interface timer 150 expires and the target BSS has received a Handover Request message, the ongoing handover resource allocation fails.

[0120] In addition to the case of PS handover, the target BSS may initiate a PS handover complete procedure in case of DTM handover, on receipt of a (RR) handover complete message on the main DCCH in the target cell (see 3GPP-TS 44.018).

[0121] Upon reception of the handover request signal on the line 118 as shown in FIG. 11, containing a PS indication IE within an Old BSS to New BSS Information IE, then the target BSS 12 may proceed in a number of different ways. If the target BSS timer is not running, then the target BSS can start it. When a matching pair of handover request message and PS handover request PDU have been received (i.e., the contents of the CS indication and PS indication IE's are identical), the target BSS 12 may stop its timer and allocate dedicated and (optionally) shared resources (see 3GPP-TS 48.018) respecting the capabilities of the mobile station.

[0122] If, in the case of DTM handover, both dedicated and shared resources are allocated, the handover request acknowledge message sent on the line 138 by the target BSS 12 may contain a radio interface message DTM HANDOVER COMMAND within its “Layer 3 Information” information element. The “Layer 3 Information” (which may be either a RR-layer 3 HANDOVER COMMAND or an RLC/MAC-layer 2 DTM HANDOVER COMMAND) is transferred by the controlling MSC to the source BSS using a BSMAP message HANDOVER COMMAND also within the IE “Layer 3 Information” of that BSMAP message. Information about the appropriate new channels and a handover reference number chosen by the new BSS are contained in the HANDOVER COMMAND or DTM HANDOVER COMMAND. Knowledge of the channel in use at the source BSS allows the target BSS to minimize the size of the HANDOVER COMMAND or DTM HANDOVER COMMAND message (i.e., to decide whether the mode of the first channel IE need not be included in the HANDOVER COMMAND).

[0123] If the timer expires and the target BSS has received a HANDOVER COMMAND REQUEST message on the line 118 (but no corresponding PS handover request PDU on the line 119, the target BSS may either abort the handover resource allocation procedure by sending a HANDOVER FAILURE message to the MSC with cause “DTM handover-timer expiry,” or may continue with the handover resource allocation procedure, allocating only a dedicated resource. In the latter case, the BSS sends a HANDOVER REQUEST ACKNOWLEDGE message on the line 138 to the MSC with the L3 information IE containing an RR handover command message. In either case, the target BSS may store the contents of the PS Indication IE and the identity of the MS. It should be noted that the duration for which the new BSS stores the content of the PS Indication IE is implementation dependent. However, it should be long enough to allow the target BSS to determine whether or not a late PS-handover-request PDU corresponds to a previously terminated DTM handover attempt.

[0124] If the timer expires and the target BSS has received a PS HANDOVER REQUEST PDU (but no corresponding HANDOVER REQUEST message), the ongoing PS handover request procedure implicitly fails and the target BSS may send a PS-HANDOVER-REQUEST-NACK PDU to the SGSN with cause “DTN Handover-Timer expiry” (see 3GPP-TS 48.018).

[0125] Referring now to FIG. 12, it is similar to that already described in connection with FIG. 11 except being applicable to the second embodiment shown in FIGS. 5-8. Thus, a receiver 260 of an input/output device 262 is shown receiving the Handover Request signal on the line 18 in response to which the receiver 260 provides an output signal on a line 264 to a signal processor 200-12 which may take the form shown in FIG. 14 or which may be an integrated circuit (chip). As already described above, the target BSS 12 may send, in response thereto, a download BSS PFC message on the line 134 to the core network 14. Thus, the signal processor 200-12 of FIG. 12 is shown providing a signal on a line 266 to a transmitter 268 within device 262 which in turn provides the download signal on the line 134. In response thereto, the core network provides the Create BSS PFC signal on the line 110 which is shown being received by the receiver 260 and provided on the line 264 to the signal processor 200-12.

[0126] The signal processor 200-12 also provides the Handover Request signal on the line 30 as described previously in connection with FIG. 6 in response to a signal on the line 266 from the signal processor 200-12.

[0127] FIG. 13 shows a mobile station 60 such as the mobile station shown in the two embodiments of the present invention and more particularly as shown in FIGS. 3-4 and 7-8. A signal processor 200-13 is shown which may take the form shown in FIG. 14 while not being limited thereto. I.e., it could take another form such as that of an integrated circuit. The various signals shown already in connection with the previous figures are illustrated in FIG. 13 being received by a receiver 270 or provided by a transmitter 272 and being part of an input/output device 274 within the MS 60. This input/output device 274 is connected to the signal processor 200-13 with as shown so as to be in a position to provide the various input and output signals already illustrated in FIGS. 3-4 and 7-8.

[0128] The mobile station 60 may of course take part as an element of a system including the various elements shown in the foregoing figures including the source BSS 10, the core network 14 and its various elements shown in detail in FIGS. 3-4 and 7-8 as well as the target BSS 12.