Method and apparatus for supporting MBMS in system architecture evolution

• US 8,451,764 B2
• Filed: 03/20/2008
• Issued: 05/28/2013
• Est. Priority Date: 03/21/2007
• Status: Active Grant

• Current Assignee: Nokia Technologies Oy (Nokia Corporation)
• Original Assignee: Alcatel-Lucent SA (Nokia Corporation)
• Inventors: Chao, Hua, Hu, Zhongji, Wang, He, Wang, Yonggang
• Primary Examiner(s): Moore, Ian N
• Assistant Examiner(s): Le, Brian T
• Application Number:
  US12/531,744
• Publication Number:
  US 20100110961A1
• Time in Patent Office: 1,895 Days
• Field of Search: None
• US Class Current: 370/312
• CPC Class Codes: H04W 76/40 for selective distribution or broadcast
• CPC Class Codes: H04W 88/18 Service support devices; Network management devices

Abstract

The present invention discloses a system structure for supporting Evolved Multimedia Broadcast/Multicast Service (Evolved MBMS), comprising: a Broadcast/Multicast Service Center (BM-SC) for initiating control signaling and bearer services for Multimedia Broadcast/Multicast Service (MBMS); a System Architecture Evolved Gateway (SAE GW) for receiving MBMS service data and MBMS control signaling or service data from another network, and forwarding the received service data and control signaling; a Broadcast/Multicast Management Entity (BME) for receiving, processing and forwarding the MBMS control signaling, and determining, for each item of the service data for MBMS, an enhanced Node B (eNB) which needs to receive the control signaling; and an multicast User Plane Entity (mUPE) for receiving the MBMS service data, processing the received MBMS service data in Evolved Packet System Architecture Evolution, and forwarding the processed MBMS service data to a downstream node.

Claims

1. A system structure for supporting Evolved Multimedia Broadcast/Multicast Service (Evolved MBMS), comprising:

a Broadcast/Multicast Service Center (BM-SC) for initiating control signaling and bearer services for Multimedia Broadcast/Multicast Service (MBMS), said BM-SC being operative to transmit service data and control signaling to a System Architecture Evolved Gateway (SAE GW);

a System Architecture Evolved Gateway (SAE GW), said SAE GW being operative to receive MBMS service data and MBMS control signaling from said BM-SC, if available therefrom and to receive MBMS service data and MBMS control signaling from another network, if available therefrom, and to forward said received MBMS service data and MBMS control signaling, said SAE GW being further operative to forward said received MBMS service data and MBMS control signaling to a Broadcast/Multicast Management Entity (BME);

a Broadcast/Multicast Management Entity (BME) for receiving, processing and forwarding the MBMS control signaling, and determining, for each item of said MBMS service data, an enhanced Node B (eNB) which needs to receive said MBMS control signaling, said BME being operative to forward said MBMS control signaling to the determined eNB; and

a multicast User Plane Entity (mUPE) for receiving the MBMS service data, processing the received MBMS service data according to the Evolved Packet System Architecture Evolution, and forwarding the processed MBMS service data to a downstream node, said mUPE being configured to receive MBMS service data sent from said BM-SC,

wherein the SAE GW comprises;

a Packet Data Network SAE GW for receiving the MBMS service data and the MBMS control signaling from the BM-SC or another network, storing locally service parameters and forwarding the received MBMS service data and MBMS control signaling to a Serving SAE GW;

the Serving SAE GW for receiving the MBMS service data and the MBMS control signaling from the Packet Data Network SAE GW, storing locally service parameters and forwarding the received MBMS service data and MBMS control signaling to the downstream node and wherein the Serving SAE GW has a function of distribution tree management on the MBMS to be forwarded.

2. The system structure of claim 1, wherein the Serving SAE GW and the Packet Data Network SAE GW are located at one same physical node.

3. The system structure of claim 1, wherein the Serving SAE GW and the Packet Data Network SAE GW are located at different physical nodes.

4. The system structure of claim 1, wherein the Serving SAE GW stores locally parameters contained in the forwarded MBMS control signaling.

5. The system structure of claim 1, wherein the BME stores parameters contained in the forwarded MBMS control signaling.

6. A system structure for supporting Evolved Multimedia Broadcast/Multicast Service (Evolved MBMS), comprising:

a Broadcast/Multicast Service Center (BM-SC) for initiating control signaling and bearer services for Multimedia Broadcast/Multicast Service (MBMS), said BM-SC being operative to transmit service data and control signaling to a System Architecture Evolved Gateway (SAE GW);

a System Architecture Evolved Gateway (SAE GW), said SAE GW being operative to receive MBMS service data and MBMS control signaling from said BM-SC, if available therefrom and to receive MBMS service data and MBMS control signaling from another network, if available therefrom, and to forward said received MBMS service data and MBMS control signaling, said SAE GW being further operative to forward said received MBMS service data and MBMS control signaling to a Broadcast/Multicast Management Entity (BME);

a Broadcast/Multicast Management Entity (BME) for receiving, processing and forwarding the MBMS control signaling, and determining, for each item of said MBMS service data, an enhanced Node B (eNB) which needs to receive said MBMS control signaling, said BME being operative to forward said MBMS control signaling to the determined eNB; and

a multicast User Plane Entity (mUPE) for receiving the MBMS service data, processing the received MBMS service data according to the Evolved Packet System Architecture Evolution, and forwarding the processed MBMS service data to a downstream node, said mUPE being configured to receive MBMS service data sent from said BM-SC;

wherein the BME has a function of distribution tree management on the MBMS to be forwarded.

7. The system structure of claim 6, wherein the BME can be implemented as an individual network entity, or can be provided in a Multicast Coordination Entity (MCE) or a Mobility Management Entity (MME).

8. The system structure of claim 6, wherein the BME is connected to the Serving SAE GW and a node (eNB) via interfaces, respectively.

9. The system structure of claim 6, wherein the MBMS is Evolved MBMS.

18. The system structure of claim 6, wherein the BME is a management entity for Evolved MBMS.

10. A method for supporting Multimedia Broadcast/Multicast Service (MBMS) in system architecture evolution, comprising:

initiating, by a Broadcast/Multicast Service Center (BM-SC), MBMS bearer services and forwarding, by the BM-SC, content of said MBMS bearer services to a System Architecture Evolved Gateway (SAE GW), or sending service data by another network to the SAE GW;

receiving, by the SAE GW, the MBMS service data and the MBMS control signaling from the BM-SC or another network, storing locally service parameters and forwarding the received MBMS service data and MBMS control signaling to a Serving SAE GW;

forwarding, by the SAE GW, to a Serving SAE GW, the received MBMS service data or the service data from the another network to an multicast User Plane Entity (mUPE) after the SAE GW receives the MBMS service data or the service data from another network;

receiving, by the Serving SAE GW, the MBMS service data and the MBMS control signaling from the SAE GW;

storing locally, by the Serving SAE GW service parameters and forwarding the received MBMS service data and MBMS control signaling to the downstream node;

performing, by the Serving SAE GW, distribution tree management on the MBMS to be forwarded; and

performing, by the mUPE, a core-network processing on the received MBMS service data in Evolved Packet Core Network and forwarding the processed MBMS service data to a downstream node after the mUPE receives the MBMS service data.

11. The method of claim 10, further comprising performing, by the SAE GW, distribution tree management on the MBMS to be forwarded.

12. The method of claim 10, further comprising performing, by a Broadcast/Multicast Management Entity (BME), distribution tree management on the MBMS to be forwarded.

13. The method of claim 10, wherein the MBMS is Evolved MBMS.

14. The method of claim 10 comprising:

initiating, by the Broadcast/Multicast Service Center (BM-SC), an MBMS Session Start message and forwarding the MBMS Session Start message to the System Architecture Evolved Gateway (SAE GW);

forwarding, by the SAE GW, the received MBMS Session Start message to a Broadcast/Multicast Management Entity (BME) after the SAE GW receives the MBMS Session Start message;

sending, by the SAE GW, a response message back to the BM-SC in response to the reception of the MBMS Session Start message, so as to acknowledge the reception of the MBMS Session Start message;

receiving, by the BME, the MBMS Session Start message forwarded from the SAE GW, and forwarding the received MBMS Session Start message to each of enhance Node Bs (eNBs) which are connected to the BME and located in a service area covered by the MBMS;

sending, by the BME, a response message back to the SAE GW in response to the reception of the MBMS Session Start message so as to acknowledge the reception of the MBMS Session Start message;

sending, by each of the eNBs, a response message back to the BME in response to the reception of the MBMS Session Start message so as to acknowledge the reception of the MBMS Session Start message.

15. The method of claim 14, further comprising storing locally parameters contained in the MBMS Session Start message by the SAE GW.

16. The method of claim 14, further comprising storing locally parameters contained in the MBMS Session Start message by the BME.

17. The method of claim 14, wherein the BME is able to update and stop an MBMS Session.