US7995562B2
Active / In Force
US
⏱️ 0.3 years remaining
System and method to trigger a mobile device in different domains based on unsuccessful initialization or handover
Assignee: Malikie Innovations Ltd
•
Filing: 2007-02-26
•
Granted: 2011-08-09
•
Expires: 2027-02-26
Abstract
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.
Inventors
- 👤 Rene W. Purnadi
- 👤 M. Khaledul Islam
- 👤 Adrian Buckley
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-03 03:16
CPC Classifications
H; H04; H04W; H04W4/00; H04W4/16; H04W36/00; H04W36/0005; H04W36/0011; H04W36/0022; H04W36/00224; H04W36/06; H04W48/00; H04W48/18; H04W80/00; H04W80/04; H04W88/00; H04W88/02; H04W88/06
Claims Analysis
Total Claims: 25
Claim 1
Independent Claim
110 words
A system comprising: a mobile device configured to attempt a call session in a packet-switched domain; and a SIP rejection message transmitted to the mobile device upon a failure to connect the call session in the packet-switched domain; wherein the SIP rejection message is indicative of a rejection and a reason for the rejection of the call session in the packet-switched domain; and wherein the mobile device is configured to determine whether to reattempt the call session in a circuit-switched domain based at least in part on the reason for the rejection, and if so determined, the mobile device is operable to reattempt the call session in the circuit-switched domain.
Claim 2
Independent Claim
110 words
A system comprising: a mobile device configured to attempt a call session in a packet-switched domain; and a SIP rejection message transmitted to the mobile device upon a failure to connect the call session in the packet-switched domain; wherein the SIP rejection message is indicative of a rejection and a reason for the rejection of the call session in the packet-switched domain; and wherein the mobile device is configured to determine whether to reattempt the call session in a circuit-switched domain based at least in part on the reason for the rejection, and if so determined, the mobile device is operable to reattempt the call session in the circuit-switched domain.
Claim 3
Dependent Claim
20 words
The system of claim 1 , wherein the call session is one of a session initiation and a session handover.
Claim 4
Dependent Claim
31 words
The system of claim 1 , wherein a domain component in the mobile device interprets the SIP rejection message and determines whether to make the call session in the circuit-switched domain.
Claim 5
Dependent Claim
26 words
The system of claim 1 , wherein the mobile device automatically reattempts the call session in the circuit-switched domain upon receipt of the SIP rejection message.
Claim 6
Dependent Claim
35 words
The system of claim 1 , wherein the mobile device, upon receipt of the SIP rejection message, offers a user of the mobile device an option of reattempting the call session in the circuit-switched domain.
Claim 7
Dependent Claim
37 words
The system of claim 1 , wherein when the failure occurs during a handover, the SIP rejection message is sent to the mobile device when the call session is anchored at a voice call continuity (VCC) server.
Claim 8
Dependent Claim
152 words
A dual mode mobile device operable to communicate in a packet-switched domain and a circuit-switched domain, the dual mode mobile device comprising: an antenna capable of receiving a SIP rejection message upon a failure to initiate a call session in the packet-switched domain; a storage device to store instructions; and a processor, such that responsive to execution of the instructions and responsive to receiving and interpreting the SIP rejection message, the processor is configured to determine whether to reattempt the call session in the circuit-switched domain, wherein the SIP rejection message is indicative of a reason for a rejection of the call in the packet-switched domain, and wherein the determination whether to reattempt the call session in the circuit-switched domain is based at least in part on the reason for the rejection, and if the processor so determines, the mobile device is operable to reattempt the call session in the circuit-switched domain.
Claim 9
Dependent Claim
152 words
A dual mode mobile device operable to communicate in a packet-switched domain and a circuit-switched domain, the dual mode mobile device comprising: an antenna capable of receiving a SIP rejection message upon a failure to initiate a call session in the packet-switched domain; a storage device to store instructions; and a processor, such that responsive to execution of the instructions and responsive to receiving and interpreting the SIP rejection message, the processor is configured to determine whether to reattempt the call session in the circuit-switched domain, wherein the SIP rejection message is indicative of a reason for a rejection of the call in the packet-switched domain, and wherein the determination whether to reattempt the call session in the circuit-switched domain is based at least in part on the reason for the rejection, and if the processor so determines, the mobile device is operable to reattempt the call session in the circuit-switched domain.
Claim 10
Dependent Claim
20 words
The device of claim 7 , wherein the call session is one of a session initiation and a session handover.
Claim 11
Dependent Claim
23 words
The device of claim 7 , wherein the SIP rejection message includes a suggestion to attempt the call session in the circuit-switched domain.
Claim 12
Dependent Claim
32 words
The device of claim 7 , wherein the processor is further programmed to promote providing a user of the mobile device an option of reattempting the call session in the circuit-switched domain.
Claim 13
Dependent Claim
45 words
The device of claim 7 , wherein the SIP rejection message follows a messaging protocol for at least one of: a Code Division Multiple Access (CDMA) message; a Universal Mobile Telecommunications System Terrestrial Radio Access Network (UTRAN) message; and a Session Initiation Protocol (SIP) message.
Claim 14
Independent Claim
103 words
A method in a mobile device, the method comprising: attempting a call session in a packet-switched domain; receiving, at the mobile device, a SIP rejection message associated with failure to connect the call session in the packet-switched domain, the SIP rejection message indicative of a rejection and a reason for the rejection of the call session in the packet-switched domain; responsive to receiving and interpreting the SIP rejection message, determining whether to reattempt the call session in a circuit-switched domain based at least in part on the reason for the rejection; and if so determined, attempting the call session in the circuit-switched domain.
Claim 15
Independent Claim
103 words
A method in a mobile device, the method comprising: attempting a call session in a packet-switched domain; receiving, at the mobile device, a SIP rejection message associated with failure to connect the call session in the packet-switched domain, the SIP rejection message indicative of a rejection and a reason for the rejection of the call session in the packet-switched domain; responsive to receiving and interpreting the SIP rejection message, determining whether to reattempt the call session in a circuit-switched domain based at least in part on the reason for the rejection; and if so determined, attempting the call session in the circuit-switched domain.
Claim 16
Dependent Claim
20 words
The method of claim 12 , wherein the call session is one of a session initiation and a session handover.
Claim 17
Dependent Claim
75 words
The method of claim 12 , further comprising at least one of: automatically attempting the call session in the circuit-switched domain upon receipt of the SIP rejection message by the mobile device, the mobile device being operable to receive and interpret the SIP rejection message; and offering a user of the mobile device an option of making the call session in the circuit-switched domain upon receipt of the SIP rejection message by the mobile device.
Claim 18
Dependent Claim
33 words
The method of claim 12 , wherein, when the rejection did not occur because of a technology-related issue, the SIP rejection message does not promote attempting the call session in the circuit-switched domain.
Claim 19
Dependent Claim
41 words
The method of claim 12 , wherein determining whether to reattempt the call session in the circuit-switched domain is based on whether the reason for the rejection of the call session in the packet-switched domain is associated with a technology-related issue.
Claim 20
Independent Claim
120 words
A method in a mobile device, the method comprising: attempting a call session in a packet switched domain by sending a Session Initiation Protocol (SIP) Invite message; receiving, at the mobile device, a SIP rejection message associated with failure to connect the call session in the packet switched domain, the rejection message indicative of a rejection and a reason for the rejection of the call session in the packet switched domain; responsive to receiving the SIP rejection message, interpreting the SIP rejection message to determine whether to reattempt the call session in a circuit switched domain based at least in part upon the reason for the rejection; and if so determined, reattempting the call session in the circuit switched domain.
Claim 21
Independent Claim
120 words
A method in a mobile device, the method comprising: attempting a call session in a packet switched domain by sending a Session Initiation Protocol (SIP) Invite message; receiving, at the mobile device, a SIP rejection message associated with failure to connect the call session in the packet switched domain, the rejection message indicative of a rejection and a reason for the rejection of the call session in the packet switched domain; responsive to receiving the SIP rejection message, interpreting the SIP rejection message to determine whether to reattempt the call session in a circuit switched domain based at least in part upon the reason for the rejection; and if so determined, reattempting the call session in the circuit switched domain.
Claim 22
Dependent Claim
20 words
The method of claim 17 , wherein the call session is one of a session initiation and a session handover.
Claim 23
Dependent Claim
54 words
The method of claim 17 , further comprising at least one of: automatically reattempting the call session in the circuit switched domain upon receiving the SIP rejection message; and offering a user of the mobile device an option of making the call session in the circuit switched domain upon receiving the SIP rejection message.
Claim 24
Dependent Claim
33 words
The method of claim 17 , wherein, when the rejection did not occur because of a technology-related issue, the mobile device determines not to reattempt the call session in the circuit switched domain.
Claim 25
Dependent Claim
17 words
The method of claim 17 , wherein the SIP rejection message is a (SIP) “Not Acceptable” message.
References Cited (Backward Citations)
US6681105B1
Cited
KR20010030725A
Cited
US6304565B1
Cited
US6567667B1
Cited
US20030152048A1
Cited
US20020024943A1
Cited
US6937704B1
Cited
US20050117576A1
Cited
US20020085516A1
Cited
US20030134650A1
Cited
US20030139184A1
Cited
US20030139180A1
Cited
KR20050012255A
Cited
US7151931B2
Cited
US20040001474A1
Cited
US20040264410A1
Cited
US20050030928A1
Cited
US20050041640A1
Cited
US20050047398A1
Cited
US20050265284A1
Cited
US20050083909A1
Cited
US20050083899A1
Cited
WO2005051025A1
Cited
US7010299B2
Cited
US20050154793A1
Cited
US20050163078A1
Cited
US20050190747A1
Cited
US20050220079A1
Cited
US20050238041A1
Cited
US20060121916A1
Cited
KR20060013951A
Cited
US20090323623A1
Cited
US20060068778A1
Cited
US20060094396A1
Cited
US20090156215A1
Cited
KR20070067234A
Cited
WO2006057924A2
Cited
US20060159059A1
Cited
US20060268840A1
Cited
US20060276192A1
Cited
US20080198764A1
Cited
US20090233600A1
Cited
US20060286984A1
Cited
US20070015510A1
Cited
WO2007009348A1
Cited
US20070022200A1
Cited
US20080102844A1
Cited
US20070049281A1
Cited
US7546125B2
Cited
US20080119165A1
Cited
US20070117588A1
Cited
WO2007079578A1
Cited
US20070183410A1
Cited
US20080049675A1
Cited
US20080056236A1
Cited
US20100110978A1
Cited
US20080112392A1
Cited
US20080186953A1
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2014-08-08 | 2015-02-07 | 2015-08-09 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2018-08-08 | 2019-02-07 | 2019-08-09 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2022-08-08 | 2023-02-07 | 2023-08-09 | $7700.00 | Window Closed / Lapsed |