METHOD AND SYSTEM FOR ALLOWING VARIED FUNCTIONALITY BASED ON MULTIPLE TRANSMISSIONS

• US 20110159895A1
• Filed: 12/30/2009
• Published: 06/30/2011
• Est. Priority Date: 12/30/2009
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Arzelier, Claude Jean-Frede, Islam, M. Khaledul
• Granted Patent: US 8,983,532 B2
• Time in Patent Office: Days
• US Class Current: 455/466
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements

Abstract

A method and apparatus for allowing varied functionality between a sending entity and a receiving entity, the method sending a first message from the sending entity to the receiving entity utilizing a first protocol, detecting an indication that the receiving entity did not recognize the first message or that the receiving entity did not fulfill a request in the first message, and sending a second message from the sending entity to the receiving entity utilizing a second protocol.

Claims

1. A method for allowing varied functionality between a sending entity and a receiving entity, the method comprising:

sending a first message from the sending entity to the receiving entity utilizing a first protocol;

detecting an indication that the receiving entity did not recognize the first message or that the receiving entity did not fulfill a request in the first message; and

sending a second message from the sending entity to the receiving entity utilizing a second protocol.

2. The method of claim 1, wherein the indication is a lack of a response to the sending of the first message for a predetermined time period.

3. The method of claim 2, wherein the predetermined time period is based on a response time of the receiving entity.

4. The method of claim 3, wherein the predetermined time period further includes an additional timing gap.

5. The method of claim 1, wherein the indication is an incompatibility message.

6. The method of claim 1, wherein the indication is a response in an unexpected or unrecognized format.

7. The method of claim 1, wherein the indication that the receiving entity did not fulfill the request of the first message is based on the sending entity to consider a response to the first message to be inefficient.

8. The method of claim 7, wherein the consideration to determine whether the response is inefficient includes battery consumption as a criteria.

9. The method of claim 1, wherein the first message is a request to change a state or mode of the sending entity.

10. The method of claim 1, wherein the sending entity is a user equipment operating in a Universal Mobile Telecommunications System network, and wherein the first protocol is a signal release indication with a cause code.

11. The method of claim 1, wherein the sending entity is a user equipment operating in a Universal Mobile Telecommunications System network, and wherein the first protocol is a preferred state indication.

12. The method of claim 1, wherein the sending entity is a user equipment operating in a Universal Mobile Telecommunications System network, and wherein the first protocol is a radio release indication.

13. The method of claim 1, wherein the sending entity is a user equipment operating in a Universal Mobile Telecommunications System network, and wherein the first protocol is a signaling connection release indication.

14. The method of claim 1, wherein the sending entity is a user equipment operating in a Universal Mobile Telecommunications System network, and wherein the first protocol is a signaling connection release indication with appended cause value.

15. The method of claim 1, wherein the sending entity is a mobile device.

16. The method of claim 1, wherein the first protocol and the second protocol are different versions of the same protocol.

17. A sending entity configured to communicate with a receiving entity utilizing varied functionality, the sending entity comprising:

a processor; and

a communications subsystem;

the processor and communications subsystem cooperating to;

send a first message from the sending entity to the receiving entity utilizing a first protocol;

detect an indication that the receiving entity did not recognize the first message or the receiving entity did not fulfill a request in the first message; and

send a second message from the sending entity to the receiving entity utilizing a second protocol.

18. The sending entity of claim 17, wherein the indication is a lack of a response to the sending of the first message for a predetermined time period.

19. The sending entity of claim 18, wherein the predetermined time period is based on a response time of the receiving entity.

20. The sending entity of claim 19, wherein the predetermined time period further includes an additional timing gap.

21. The sending entity of claim 17, wherein the indication is one of an incompatibility message and a response in an unexpected or unrecognized format.

22. The sending entity of claim 17, wherein the indication that the receiving entity did not fulfill the request is based on the sending entity considering a response to the first message to be inefficient.

23. The sending entity of claim 17, wherein the first protocol and the second protocol are different versions of the same protocol.

24. The sending entity of claim 17, wherein the first message is a request to change a state or mode of the sending entity.

25. The sending entity of claim 17, wherein the sending entity is a user equipment operating in a Universal Mobile Telecommunications System network, and wherein the first protocol is one of:

a signal release indication with a cause code, a preferred state indication;

a radio release indication;

a signaling connection release indication; and

a signaling connection release indication with appended cause value.