IP Library Granted Patent US 9,723,523
Granted Patent B2
US 9,723,523 · App. 13/566,766 · Granted Aug 1, 2017

Maintaining MBMS continuity

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,723,523
App. No.
13/566,766
Granted
Aug 1, 2017
Kind
B2
Abstract

Methods and systems for managing Multimedia Broadcast Multicast Service (MBMS) service continuity include, with a source node in a communication system, providing an MBMS, processing an event that indicates that a User Equipment (UE) being serviced by the source node is to be transferred to one of a number of candidate nodes, receiving a congestion bit from each of the candidate nodes, and providing data to the UE that causes the UE to be serviced by a target node selected from the candidate nodes based at least in part on values of the congestion bits from each of the candidate nodes.

Claims (88)

1. A method for managing Multimedia Broadcast Multicast Service (MBMS) service continuity, the method comprising:

by a source node in a communication system, providing an MBMS;

by the source node, processing an event that indicates that a User Equipment (UE) being serviced by the source node for MBMS is to be transferred to one of a number of candidate nodes;

by the source node, receiving a congestion bit from each of the candidate nodes, wherein receiving the congestion bits is in response to a query sent by the source node to the candidate nodes, and at least one of the congestion bits indicates whether a respective candidate node can provide a non-MBMS service to an additional device;

by the source node, providing data to the UE that causes the UE to be serviced for MBMS by a target node selected from the candidate nodes based at least in part on values of the congestion bits from each of the candidate nodes and whether the UE prioritizes MBMS;

if the UE is in a Radio Resource Controller (RRC) idle mode:

by the source node, providing the UE with the congestion bits over a broadcast control channel associated with the MBMS; and

wherein the target node is selected at the UE based at least in part on the values of the congestion bits and a priority maintained by the UE that indicates whether the UE prioritizes MBMS; and

if the UE is in an RRC connected mode:

by the source node, receiving a priority bit from the UE, the priority bit indicating whether the UE prioritizes MBMS; and

by the source node, selecting the target node based at least in part on a value of the priority bit and the values of the congestion bits.

2. The method of claim 1 , wherein the non-MBMS service comprises a unicast service.

3. The method of claim 1 , wherein the UE is in a Radio Resource Controller (RRC) idle mode.

4. The method of claim 1 , wherein the UE is in an RRC connected mode.

5. The method of claim 4 , wherein, if the priority bit indicates that the UE prioritizes MBMS, selecting the target node comprises selecting a candidate node having a stronger signal strength than other candidate nodes, the signal strength being above a predefined threshold for MBMS.

6. The method of claim 4 , wherein, if the priority bit indicates that the UE does not prioritize MBMS, selecting the target node comprises selecting a candidate node with an available non-MBMS service and stronger signal strength than other candidate nodes, the signal strength being above a predefined threshold for the non-MBMS service.

7. The method of claim 4 , wherein the priority bit is received by the source node in a measurement report sent by the UE.

8. The method of claim 4 , wherein the congestion bit is received as part of at least one of: an MBMS query response, a handover command, and a handover request ACK.

9. The method of claim 1 , further comprising, by the source node, narrowing the candidate nodes to those that provide the MBMS on a same single frequency network of the source node.

10. The method of claim 1 , further comprising, with the source node, sending the congestion bit of the selected target node to the UE to inform the UE whether the UE can receive a non-MBMS service from the target node.

11. The method of claim 10 , wherein the congestion bit is sent to the UE in an RRC Connection Reconfiguration message.

12. The method of claim 1 , further comprising, with the source node, maintaining the congestion bit from each of the candidate nodes as valid for a predefined period of time.

13. A source node within a communication network, the source node comprising:

a processor; and

a non-transitory computer readable medium comprising a set of computer readable instructions that when executed by the processor, cause the node to:

provide a Multimedia Broadcast Multicast Service (MBMS);

process an event that indicates that a User Equipment (UE) being serviced by the source node for MBMS is to be transferred to one of a number of candidate nodes;

receive a congestion bit from each of the candidate nodes, wherein at least one of the congestion bits from a respective candidate node indicates whether the respective candidate node can provide a non-MBMS service to an additional device;

provide data to the UE that causes the UE to be serviced for MBMS by a target node selected from the candidate nodes based at least in part on values of the congestion bits from each of the candidate nodes and whether the UE prioritizes MBMS, wherein the congestion bits are received as part of at least one of: an MBMS query response, a handover command, and a handover request ACK;

if the UE is in a Radio Resource Controller (RRC) idle mode:

provide the UE with the congestion bits over a broadcast control channel associated with the MBMS; and

wherein the target node is selected at the UE based at least in part on the values of the congestion bits and a priority maintained by the UE that indicates whether the UE prioritizes MBMS; and

if the UE is in an RRC connected mode:

receive a priority bit from the UE, the priority bit indicating whether the UE prioritizes MBMS; and

select the target node based at least in part on a value of the priority bit and the values of the congestion bits.

14. The source node of claim 13 , wherein the non-MBMS service comprises a unicast service.

15. The source node of claim 13 , wherein the UE is in a Radio Resource Controller (RRC) idle mode.

16. The source node of claim 13 , wherein the UE is in an RRC connected mode.

17. The source node of claim 16 , wherein to select the target node, if the priority bit indicates that the UE prioritizes MBMS, the processor further causes the node to select a candidate node with a stronger signal strength than other candidate nodes, the signal strength being above a predefined threshold for MBMS.

18. The source node of claim 16 , wherein to select the target node, if the priority bit indicates that the UE does not prioritize MBMS, the processor further causes the node to select a candidate node with an available non-MBMS service and a stronger signal strength than other candidate nodes, the signal strength being above a predefined threshold for the non-MBMS service.

19. The source node of claim 16 , wherein the priority bit is received by the source node in a measurement report sent by the UE.

20. The source node of claim 13 , wherein the processor further causes the source node to narrow the candidate nodes to those that provide the MBMS on a same single frequency network of the source node.

21. The source node of claim 13 , wherein the processor further causes the source node to send the congestion bit of the selected target node to the UE to inform the UE whether the UE can receive a non-MBMS service from the target node.

22. The source node of claim 21 , wherein congestion bit is sent to the UE in an RRC Connection Reconfiguration message.

23. The source node of claim 13 , wherein the processor further causes the source node to receive the congestion bits is in response to a query sent by the source node to the candidate nodes.

24. The source node of claim 13 , wherein the processor further causes the source node to maintain the congestion bit from each of the candidate nodes as valid for a predefined period of time.

25. A method for managing Multimedia Broadcast Multicast Service (MBMS) service continuity, the method comprising:

by a User Equipment (UE) being serviced by a source node in a communication system, receiving an MBMS;

by the UE, sending a signal to the source node that indicates that the UE is to be transferred to one of a number of candidate nodes; and

by the UE, receiving a signal that causes the UE to be serviced for MBMS by a target node selected from the candidate nodes, the target node being selected based at least in part on values of congestion bits received by the source node from the candidate nodes and whether the UE prioritizes MBMS, wherein at least one of the congestion bits indicates whether a respective candidate node can provide a non-MBMS service to an additional device, and the source node maintains the congestion bit from each of the candidate nodes as valid for a predefined period of time;

if the UE is in a Radio Resource Controller (RRC) idle mode:

receiving the congestion bits from the source node over a broadcast channel; and

selecting the target node based on at least in part on the values of the congestion bits received by the source node from the candidate nodes and a priority of the UE that indicates whether the UE prioritizes MBMS; and

if the UE is in an RRC connected mode:

sending a priority bit to the source node, the priority bit indicating whether the UE prioritizes MBMS.

26. The method of claim 25 , wherein the non-MBMS service comprises a unicast service.

27. The method of claim 25 , wherein the UE is in a Radio Resource Controller (RRC) idle mode.

28. The method of claim 25 , wherein the UE is in an RRC connected mode.

29. The method of claim 28 , wherein, if the priority bit indicates that the UE prioritizes MBMS, selecting the target node comprises selecting a candidate node with a stronger signal strength than other candidate nodes, the signal strength being above a predefined threshold for MBMS.

30. The method of claim 28 , wherein, if the priority bit indicates that the UE does not prioritize MBMS, selecting the target node comprises selecting a candidate node with an available non-MBMS service and having a stronger signal strength than other candidate nodes, the signal strength being above a predefined threshold for the non-MBMS service.

31. The method of claim 28 , wherein the priority bit is received by the source node in a measurement report sent by the UE.

32. The method of claim 28 , further comprising, with the UE, receiving the congestion bit of the selected target node to determine whether the UE can receive a non-MBMS service from the target node.

33. The method of claim 32 , wherein congestion bit is received by the UE in an RRC Connection Reconfiguration message.

34. The method of claim 25 , wherein the congestion bit is received by the source node as part of at least one of: an MBMS query response, a handover command, and a handover request ACK.

35. The method of claim 25 , wherein the candidate nodes have been narrowed by the source node to those that provide the MBMS on a same single frequency network of the source node.

36. The method of claim 25 , wherein the source node receives the congestion bits in response to a query sent by the source node to the candidate nodes.

37. A User Equipment (UE) being serviced by a source node within a communication network, the UE comprising:

a processor; and

a non-transitory computer readable medium comprising a set of computer readable instructions that when executed by the processor, cause the UE to:

receive an MBMS;

send a signal to the source node that indicates that the UE is to be transferred to one of a number of candidate nodes; and

receive a signal that causes the UE to be serviced for MBMS by a target node selected from the candidate nodes, the target node being selected based at least in part on values of congestion bits received by the source node from the candidate nodes and whether the UE prioritizes MBMS, wherein at least one of the congestion bits indicates whether a respective candidate node can provide a non-MBMS service to an additional device, and the candidate nodes have been narrowed by the source node to those that provide the MBMS on a same single frequency network of the source node;

if the UE is in a Radio Resource Controller (RRC) idle mode:

receive the congestion bits from the source node over a broadcast channel; and

select the target node based on at least in part on the values of the congestion bits received by the source node from the candidate nodes and a priority of the UE that indicates whether the UE prioritizes MBMS; and

if the UE is in an RRC connected mode:

send a priority bit to the source node, the priority bit indicating whether the UE prioritizes MBMS.

38. The UE of claim 37 , wherein the non-MBMS service comprises a unicast service.

39. The UE of claim 37 , wherein the UE is in a Radio Resource Controller (RRC) idle mode.

40. The UE of claim 37 , wherein the UE is in an RRC connected mode.

41. The UE of claim 40 , wherein to select the target node, if the priority bit indicates that the UE prioritizes MBMS, the source node selects a candidate node with a stronger signal strength than other candidate nodes, the signal strength being above a predefined threshold for MBMS.

42. The UE of claim 40 , wherein to select target node, if the priority bit indicates that the UE does not prioritize MBMS, the source node selects a candidate node with an available non-MBMS service and having a stronger signal strength than other candidate nodes, the signal strength being above a predefined threshold for the non-MBMS service.

43. The UE of claim 40 , wherein the priority bit is received by the source node in a measurement report sent by the UE.

44. The UE of claim 40 , wherein the computer readable instructions are further configured to cause the UE to receive the congestion bit of the selected target node to allow the UE to determine whether the UE can receive a non-MBMS service from the target node.

45. The UE of claim 44 , wherein congestion bit is received by the UE in an RRC Connection Reconfiguration message.

46. The UE of claim 37 , wherein the congestion bit is received by the source node as part of at least one of: an MBMS query response, a handover command, and a handover request ACK.

47. The UE of claim 37 , wherein the source node receives the congestion bits in response to a query sent by the source node to the candidate nodes.

48. The UE of claim 37 , wherein the source node maintains the congestion bit from each of the candidate nodes as valid for a predefined period of time.

Assignments (9)
CORRECTIVE ASSIGNMENT TO CORRECT THE ADDED PATENT NUMBER TO REMOVE PATENT NO. 8,873,407 AT PREVIOUSLY RECORDED ON REEL 64066 FRAME 1. ASSIGNOR(S) HEREBY CONFIRMS THE NUNC PRO TUNC ASSIGNMENT EFFECTIVE DATE MARCH 20, 2023. Recorded Feb 2, 2026
From: BLACKBERRY LIMITED
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 074921/0001 →
CORRECTIVE ASSIGNMENT TO CORRECT 12817157 APPLICATION NUMBER PREVIOUSLY RECORDED AT REEL: 064015 FRAME: 0001. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Sep 5, 2023
From: OT PATENT ESCROW, LLC
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064807/0001 →
CORRECTIVE ASSIGNMENT TO CORRECT THE COVER SHEET AT PAGE 50 TO REMOVE 12817157 PREVIOUSLY RECORDED ON REEL 063471 FRAME 0474. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Sep 5, 2023
From: BLACKBERRY LIMITED
To: OT PATENT ESCROW, LLC
Reel/Frame 064806/0669 →
NUNC PRO TUNC ASSIGNMENT Recorded Jun 19, 2023
From: BLACKBERRY LIMITED
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064066/0001 →
NUNC PRO TUNC ASSIGNMENT Recorded Jun 16, 2023
From: OT PATENT ESCROW, LLC
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064015/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 27, 2023
From: BLACKBERRY LIMITED
To: OT PATENT ESCROW, LLC
Reel/Frame 063471/0474 →
CHANGE OF NAME Recorded Sep 5, 2013
From: RESEARCH IN MOTION CORPORATION
To: BLACKBERRY CORPORATION
Reel/Frame 031163/0437 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 5, 2013
From: BLACKBERRY CORPORATION
To: BLACKBERRY LIMITED
Reel/Frame 031163/0479 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 30, 2012
From: PURNADI, RENE WARAPUTRA; CAI, ZHIJUN
To: RESEARCH IN MOTION CORPORATION
Reel/Frame 028878/0702 →