System and Method to Trigger a Mobile Device in Different Domains Based on Unsuccessful Initialization or Handover

• US 20110276701A1
• Filed: 06/27/2011
• Published: 11/10/2011
• Est. Priority Date: 02/26/2007
• Status: Abandoned Application

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Research In Motion Limited (Blackberry Limited)
• Inventors: Buckley, Adrian, Islam, M. Khaledul, Purnadi, Rene W.
• Application Number:
  US13/169,905
• Publication Number:
  US 20110276701A1
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: H04W 36/00224 between packet switched [PS] and circuit switched [CS] network technologies, e.g. circuit switched fallback [CSFB]
• CPC Class Codes: H04W 48/18 Selecting a network or a communication service
• CPC Class Codes: H04W 80/04 Network layer protocols, e.g. mobile IP [Internet Protocol]
• CPC Class Codes: H04W 88/06 adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Abstract

A system to promote communication in a second domain responsive to a failure in a first domain. The system includes a first domain for communicating, and a second domain for communicating. The system includes a rejection message and a mobile device. The rejection message transmitted upon a failure of a call in the first domain. The mobile device configured to communicate in both the first domain and the second domain. The mobile device configured to attempt the call in the second domain responsive to receiving the rejection message in the first domain.

Claims

1. A method in a mobile device, the method comprising:

initiating a communication session in a first domain;

receiving, at the mobile device, a rejection message associated with failure to establish the communication session in the first domain, the rejection message including a reason for the failure; and

determining, at the mobile device, based at least in part upon the reason for the failure whether to;

reattempt the communication session in the first domain, or

initiate the communication session in a second domain.

2. The method of claim 1, further comprising:

automatically initiating the communication session in the second domain, if so determined.

3. The method of claim 1, further comprising:

presenting, to a user of the mobile device, an option of initiating the communication session in the second domain, if so determined.

4. The method of claim 1, wherein said determining comprises:

interpreting the reason for the failure; and

determining whether to allow further attempts to initiate the communication session based at least in part upon the reason for the failure.

5. The method of claim 1, wherein the rejection message is a SIP “

Not Acceptable”

message.

6. The method of claim 1, wherein said determining is further based on whether the reason for the failure is associated with a technology-related issue.

7. The method of claim 1, wherein the mobile device determines to initiate the communication session in the second domain when the reason for failure is a technology-related issue.

8. The method of claim 7, wherein the technology-related issue is one of:

a lack of radio channel available to carry the communication session, or network resources being overloaded.

9. The method of claim 1, wherein the rejection message includes a text field that contains the reason for failure.

10. A mobile device capable of communicating in at least one of a first domain and a second domain, the mobile device comprising:

an antenna capable of receiving, in response to the mobile device initiating a communication session in the first domain, a rejection message associated with failure to establish the communication session in the first domain, the rejection message including a reason for the failure; and

a processor configured to determine, based at least in part upon the reason for the failure, whether the mobile device is to;

reattempt the communication session in the first domain, or

initiate the communication session in a second domain.

11. The mobile device of claim 10, wherein the mobile device automatically initiates the communication session in the second domain, if the processor so determines.

12. The mobile device of claim 10, wherein the processor is further configured to promote presenting to a user of the mobile device, an option of initiating the communication session in the second domain, if the processor so determines.

13. The mobile device of claim 10, wherein the processor is further configured to interpret the reason for the failure determine whether to allow further attempts to initiate the communication session based at least in part upon the reason for the failure.

14. The mobile device of claim 10, wherein the rejection message is a SIP “

Not Acceptable”

message.

15. The mobile device of claim 10, wherein the determination by the processor is further based on whether the reason for the failure is associated with a technology-related issue.

16. The mobile device of claim 10, wherein the processor determines that the mobile device is to initiate the communication session in the second domain when the reason for failure is a technology-related issue.

17. The mobile device of claim 16, wherein the technology-related issue is one of:

a lack of radio channel available to carry the communication session, or network resources being overloaded.

18. The mobile device of claim 10, wherein the rejection message includes a text field that contains the reason for failure.

19. A system comprising:

a mobile device configured to initiate a communication session in a first domain; and

a domain component capable of receiving a rejection message associated with failure to establish the communication session in the first domain, the rejection message including a reason for the failure,

wherein the domain component is configured to determine, based at least in part upon the reason for the failure, whether the mobile device is to;

reattempt the communication session in the first domain, or

initiate the communication session in a second domain.

20. The system of claim 19, wherein the domain component automatically causes the mobile device to initiate the communication session in the second domain upon receiving the rejection message.

21. The system of claim 19, wherein the mobile device is configured to present a user of the mobile device an option of initiating the communication session in the second domain, if the domain component so determines.

22. The system of claim 19, wherein the domain component is further configured to interpret the reason for the failure determine whether to allow further attempts to initiate the communication session based at least in part upon the reason for the failure.

23. The system of claim 19, wherein the rejection message is a SIP “

Not Acceptable”

message.

24. The system of claim 19, wherein the determination by the domain component is further based on whether the reason for the failure is associated with a technology-related issue.

25. The system of claim 19, wherein the domain component determines that the mobile device is to initiate the communication session in the second domain when the reason for failure is a technology-related issue.

26. The system of claim 25, wherein the technology-related issue is one of:

a lack of radio channel available to carry the communication session, or

network resources being overloaded.

27. The system of claim 19, wherein the rejection message includes a text field that contains the reason for failure.