Maintaining MBMS continuity

US9723523B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9723523-B2
Application numberUS-201213566766-A
CountryUS
Kind codeB2
Filing dateAug 3, 2012
Priority dateAug 3, 2012
Publication dateAug 1, 2017
Grant dateAug 1, 2017

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

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.

First claim

Opening claim text (preview).

What is claimed is: 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 sou

Assignees

Inventors

Classifications

  • Selecting an access point · CPC title

  • for multicast or broadcast services, e.g. MBMS (multicast or broadcast application services H04W4/06; resource management for broadcast services H04W72/30; connection management for selective distribution or broadcast H04W76/40) · CPC title

  • H04W76/40Primary

    for selective distribution or broadcast · CPC title

  • Identifying congestion · CPC title

  • for handling the traffic · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9723523B2 cover?
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 prov…
Who is the assignee on this patent?
Purnadi Rene, Cai Zhijun, Blackberry Ltd
What technology area does this patent fall under?
Primary CPC classification H04W76/40. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Aug 01 2017 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).