Advanced LMSD intersystem handoff

• US 9,949,171 B2
• Filed: 10/21/2011
• Issued: 04/17/2018
• Est. Priority Date: 05/20/2011
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Bienn, Marvin, Stephens, Gary
• Primary Examiner(s): Orgad, Edan
• Assistant Examiner(s): Mansoury, Nourali
• Application Number:
  US13/278,782
• Publication Number:
  US 20120294280A1
• Time in Patent Office: 2,370 Days
• Field of Search: 370331
• CPC Class Codes: H04W 36/00226 wherein the core network technologies comprise IP multimedia system [IMS], e.g. single radio voice call continuity [SRVCC]
• CPC Class Codes: H04W 36/14 Reselecting a network or an air interface
• CPC Class Codes: H04W 76/22 Manipulation of transport tunnels

Abstract

An Anchor Mobile Switching Center emulation (MSCe) and a Target MSCe are described herein that take part in an intersystem handoff of a Mobile Station (MS) which is in communication with a B-party. Upon the MS establishing a connection with the Target MSCe, the Anchor MSCe may perform SDP offer/answer exchange between the Target network and the B-Party for the purpose of codec renegotiation to correct a transcoding incompatibility or to enhance the voice bearer path characteristics or to minimize the number of transcodings in the bearer path, between the two parties. The Anchor MSCe and the Target MSCe both support Advanced Legacy Mobile Station Domain (ALMSD) implying that only the SIP transport is used for intersystem handoff communications.

Claims

1. An Anchor Mobile Switching Center emulation (MSCe) for supporting an intersystem handoff of a Mobile Station (MS) from an Anchor Network to a Target Network, wherein the MS is in communication with a B-Party, wherein the Anchor Network comprises an Anchor Base Station (BS), the Anchor MSCe and an Anchor Media Gateway (MGW), and wherein the Target Network comprises a Target BS, a Target MSCe and a Target MGW, the Anchor MSCe comprising:

a Target MSCe message interface configured to send a Handoff Request message to the Target MSCe, wherein the Handoff Request message comprises a Session Initiation Protocol (SIP) INVITE message that contains a TIA/EIA-41 FacilitiesDirective2 INVOKE message;

the Target MSCe message interface is further configured to receive from the Target MSCe a SIP Provisional Response which contains a TIA/EIA-41 FacilitiesDirective2 RETURN RESULT message;

the Target MSCe message interface is further configured to receive from the Target MSCe a SIP 200 OK (INVITE) message indicating that the MS has established a connection with the Target BS, wherein the SIP 200 OK (INVITE) message is received after receipt of the SIP Provisional Response;

the Anchor MSCe is configured to evaluate whether the Anchor MGW supports transcoding between a first codec established for a first termination to the B-Party and a second codec established for a second termination to the Target MGW which will result in a voice bearer that meets or exceeds a pre-established criteria;

based on a positive evaluation, the Anchor MSCe instructs the Anchor MGW to connect the first termination to the second termination; and

based on a negative evaluation, the Anchor MSCe solicits a Session Description Protocol (SDP) offer/answer exchange between the B-Party and the Target MGW to establish a codec combination for a voice bearer path between the B-Party and the MS that meets or exceeds the pre-established criteria.

2. The Anchor MSCe of claim 1, wherein the SDP offer/answer exchange comprises:

sending a command to the Anchor MGW to remove the first termination to the B-Party; and

sending a SIP re-INVITE which does not contain a SDP offer to the B-Party; and

receiving a reliable non-failure SIP response message which contains a SDP offer from the B-Party.

3. The Anchor MSCe of claim 2, wherein the SDP offer/answer exchange further comprises:

sending a command to the Anchor MGW to modify the second termination to the Target MGW based on a codec list in the SDP offer obtained from the B-Party; and

receiving a reply from the Anchor MGW that contains a local SDP including a list of codecs that are in common with codecs in the codec list in the SDP offer obtained from the B-Party and a list of codecs for which the Anchor MGW can transcode based on the codec list in the SDP offer obtained from the B-Party.

4. The Anchor MSCe of claim 3, wherein the SDP offer/answer exchange further comprises:

sending a SIP re-INVITE to the Target MSCe where the SIP re-INVITE contains a SDP offer based upon the local SDP of the second termination from the Anchor MGW to the Target MGW; and

receiving a reliable non-failure SIP response message from the Target MSCe where the reliable non-failure SIP response message contains an SDP answer to the SDP offer.

5. The Anchor MSCe of claim 4, wherein the SDP offer/answer exchange further comprises:

sending a command to the Anchor MGW to modify the second termination to the Target MGW based on the SDP answer obtained from the Target MSCe;

sending a command to the Anchor MGW to add the first termination to the B-Party based on the SDP offer received from the B-Party;

receiving a reply from the Anchor MGW that contains a local SDP for the first termination to the B-Party including a list of codecs that are in common with the codec list in the SDP offer obtained from the B-Party and a list codecs for which the Anchor MGW can transcode based on the codec list in the SDP offer obtained from the B-Party;

receiving a reply from the Anchor MGW where the reply contains a local SDP for the second termination to the Target MGW which has a list of codecs that are in common with the codec list in the SDP answer obtained from the Target MSCe and a list of codecs for which the Anchor MGW can transcode based on the codec list in the SDP answer obtained from the Target MSCe; and

sending to the B-Party a SIP Response containing an SDP answer based on the local SDP of the first termination to the B-Party.

6. The Anchor MSCe of claim 1, wherein the Session Initiation Protocol (SIP) INVITE message does not contain a Session Description Protocol (SDP), and wherein the TIA/EIA-41 FacilitiesDirective2 INVOKE message comprises a list of candidate cells, an identity of the Target BS, and a codec the MS is presently using.

7. The Anchor MSCe of claim 1, wherein the SIP Provisional Response further comprises (1) a SDP offer and (2) a full list of codecs that can be supported by the target MGW for the intersystem handoff of the MS.

8. A method implemented by an Anchor Mobile Switching Center emulation (MSCe) for supporting an intersystem handoff of a Mobile Station (MS) from an Anchor Network to a Target Network, wherein the MS is in communication with a B-Party, wherein the Anchor Network comprises an Anchor Base Station (BS), the Anchor MSCe and an Anchor Media Gateway (MGW), and wherein the Target Network comprises a Target BS, a Target MSCe and a Target MGW, the method comprising the steps of:

sending a Handoff Request message to the Target MSCe, wherein the Handoff Request message comprises a Session Initiation Protocol (SIP) INVITE message that contains a TIA/EIA-41 FacilitiesDirective2 INVOKE message;

receiving from the Target MSCe a SIP Provisional Response which contains a TIA/EIA-41 FacilitiesDirective2 RETURN RESULT message;

receiving from the Target MSCe a SIP 200 OK (INVITE) message indicating that the MS has established a connection with the Target BS, wherein the SIP 200 OK (INVITE) message is received after receipt of the SIP Provisional Response;

evaluating whether the Anchor MGW supports transcoding between a first codec established for a first termination to the B-Party and a second codec established for a second termination to the Target MGW which will result in a voice bearer that meets or exceeds a pre-established criteria;

based on a positive evaluation, instructing the Anchor MGW to connect the first termination to the second termination; and

based on a negative evaluation, soliciting a Session Description Protocol (SDP) offer/answer exchange between the B-Party and the Target MGW to establish a codec combination for a voice bearer path between the B-Party and the MS that meets or exceeds the pre-established criteria.

9. The method of claim 8, wherein the SDP offer/answer exchange comprises:

sending a command to the Anchor MGW to remove the first termination to the B-Party;

sending a SIP re-INVITE which does not contain a SDP offer to the B-Party; and

receiving a reliable non-failure SIP response message which contains a SDP offer from the B-Party.

10. The method of claim 9, wherein the SDP offer/answer exchange further comprises:

sending a command to the Anchor MGW to modify the second termination to the Target MGW based on a codec list in the SDP offer obtained from the B-Party; and

receiving a reply from the Anchor MGW that contains a local SDP including a list of codecs that are in common with codecs in the codec list in the SDP offer obtained from the B-Party and a list of codecs for which the Anchor MGW can transcode based on the codec list in the SDP offer obtained from the B-Party.

11. The method of claim 10, wherein the SDP offer/answer exchange further comprises:

sending a SIP re-INVITE to the Target MSCe which contains a SDP offer based upon the local SDP of the second termination from the Anchor MGW to the Target MGW; and

receiving a reliable non-failure SIP response message from the Target MSCe where the reliable non-failure SIP response message contains an SDP answer to the SDP offer.

12. The method of claim 11, wherein the SDP offer/answer exchange further comprises:

sending a command to the Anchor MGW to modify the second termination to the Target MGW based on the SDP answer obtained from the Target MSCe;

sending a command to the Anchor MGW to add the first termination to the B-Party based the SDP Offer received from the B-Party;

receiving a reply from the Anchor MGW that contains a local SDP for the first termination to the B-Party including a list of codecs that are in common with the codec list in the SDP offer obtained from the B-Party and a list codecs for which the Anchor MGW can transcode based on the codec list in the SDP offer obtained from the B-Party;

receiving a reply from the Anchor MGW where the reply contains the local SDP for the second termination to the Target MGW including a list of codecs that are in common with the codec list in the SDP answer obtained from the Target MSCe and a list codecs for which the Anchor MGW can transcode based on the codec list in the SDP answer obtained from the Target MSCe; and

sending to the B-Party a SIP Response containing an SDP answer based upon the local SDP of the first termination to the B-Party.

13. The method of claim 8, wherein the Session Initiation Protocol (SIP) INVITE message does not contain a Session Description Protocol (SDP), and wherein the TIA/EIA-41 FacilitiesDirective2 INVOKE message comprises a list of candidate cells, an identity of the Target BS, and a codec the MS is presently using.

14. The method of claim 8, wherein the SIP Provisional Response further comprises (1) a SDP offer and (2) a full list of codecs that can be supported by the target MGW for the intersystem handoff of the MS.

15. A Target Mobile Switching Center emulation (MSCe) for supporting an intersystem handoff of a Mobile Station (MS) from an Anchor Network to a Target Network, wherein the MS is in communication with a B-Party, wherein the Anchor Network comprises an Anchor Base Station (BS), an Anchor MSCe and an Anchor Media Gateway (MGW), and wherein the Target Network comprises a Target BS, the Target MSCe and a Target MGW, the Target MSCEe comprising:

an Anchor MSCe message interface configured to receive a Handoff Request message from the Anchor MSCe, wherein the Handoff Request message comprises a Session Initiation Protocol (SIP) INVITE message that contains a TIA/EIA-41 FacilitiesDirective2 INVOKE message;

the Anchor MSCe message interface is further configured to send to the Anchor MSCe a SIP Provisional Response which contains a TIA/EIA-41 FacilitiesDirective2 RETURN RESULT message;

the Target MSCe is configured to establish bearer resources in the Target MGW and the Target BS;

the Anchor MSCe message interface is further configured to send to the Anchor MSCe a SIP 200 OK (INVITE) message indicating that the MS has established a connection with the Target BS, wherein the SIP 200 OK (INVITE) message is sent after the SIP Provisional Response is sent

the Target MSCe is further configured to;

receive a SIP re-INVITE from the Anchor MSCe where the SIP re-INVITE contains an SDP offer;

send a command to the Target MGW to modify a first termination to the Anchor MGW based on a codec list in the SDP offer;

receive a reply from the Target MGW where the reply contains a local SDP including a list of codecs that are in common with codecs in the codec list in the SDP offer and a list of codecs for which the Target MGW can transcode based on the codec list in the SDP offer; and

send a reliable non-failure SIP response message to the Anchor MSCe where the reliable non-failure SIP response message contains a SDP answer to the SDP offer.

16. The Target MSCe of claim 15, wherein the Session Initiation Protocol (SIP) INVITE message does not contain a Session Description Protocol (SDP), and wherein the TIA/EIA-41 FacilitiesDirective2 INVOKE message comprises a list of candidate cells, an identity of the Target BS, and a codec the MS is presently using.

17. The Target MSCe of claim 15, wherein the SIP Provisional Response further comprises (1) a SDP offer and (2) a full list of codecs that can be supported by the target MGW for the intersystem handoff of the MS.

18. A method implemented by a Target Mobile Switching Center emulation (MSCe) for supporting an intersystem handoff of a Mobile Station (MS) from an Anchor Network to a Target Network, wherein the MS is in communication with a B-Party, wherein the Anchor Network comprises an Anchor Base Station (BS), an Anchor MSCe and an Anchor Media Gateway (MGW), and wherein the Target Network comprises a Target BS, the Target MSCe and a Target MGW, the method comprising the steps of:

receiving a Handoff Request message from the Anchor MSCe, wherein the Handoff Request message comprises a Session Initiation Protocol (SIP) INVITE message that contains a TIA/EIA-41 FacilitiesDirective2 INVOKE message;

sending to the Anchor MSCe a SIP Provisional Response which contains a TIA/EIA-41 FacilitiesDirective2 RETURN RESULT message;

establishing bearer resources in the Target MGW and the Target BS;

sending to the Anchor MSCe a SIP 200 OK (INVITE) message indicating that the MS has established a connection with the Target BS, wherein the SIP 200 OK (INVITE) message is sent after the SIP Provisional Response is sent;

receiving a SIP re-INVITE from the Anchor MSCe where the SIP re-INVITE contains an SDP offer; and

sending a command to the Target MGW to modify a first termination to the Anchor MGW based on a codec list in the SDP offer;

receiving a reply from the Target MGW where the reply contains a local SDP including a list of codecs that are in common with codecs in the codec list in the SDP offer and a list of codecs for which the Target MGW can transcode based on the codec list in the SDP offer; and

sending a reliable non-failure SIP response message to the Anchor MSCe where the reliable non-failure SIP response message contains a SDP answer to the SDP offer.

19. The method of claim 18, wherein the Session Initiation Protocol (SIP) INVITE message does not contain a Session Description Protocol (SDP), and wherein the TIA/EIA-41 FacilitiesDirective2 INVOKE message comprises a list of candidate cells, an identity of the Target BS, and a codec the MS is presently using.

20. The method of claim 18, wherein the SIP Provisional Response further comprises (1) a SDP offer and (2) a full list of codecs that can be supported by the target MGW for the intersystem handoff of the MS.