Method for implementing Iu-Flex based MBMS

• US 7,457,275 B2
• Filed: 03/17/2003
• Issued: 11/25/2008
• Est. Priority Date: 04/09/2002
• Status: Active Grant

• Current Assignee: Honor Device Company Limited
• Original Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Inventors: Zhao, Jianguo
• Primary Examiner(s): Orgad; Edan
• Assistant Examiner(s): Wong; Blanche
• Application Number:
  US10/390,341
• Publication Number:
  US 20030189914A1
• Time in Patent Office: 2,080 Days
• Field of Search: 370/270, 370/352, 370/401, 370/465, 370/390, 370/432, 455/524, 455/525
• US Class Current: 370/342
• CPC Class Codes: H04L 12/189 in combination with wireless systems selective distribution or broadcast in wireless communication networks H04W4/06
• CPC Class Codes: H04L 47/15 in relation to multipoint traffic arrangements for broadcast or multicast in data networks H04L12/18
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 47/762 triggered by the network
• CPC Class Codes: H04L 47/806 Broadcast or multicast traffic
• CPC Class Codes: H04L 47/822 Collecting or measuring resource availability data
• CPC Class Codes: H04L 47/824 Applicable to portable or mobile terminals
• CPC Class Codes: H04M 15/8016 based on quality of service [QoS]
• CPC Class Codes: H04M 2215/2073 Multipoint, e.g. messaging, broadcast or group SMS
• CPC Class Codes: H04M 2215/22 Bandwidth or usage-sensitve billing
• CPC Class Codes: H04M 2215/32 Involving wireless systems
• CPC Class Codes: H04M 2215/7414 QoS
• CPC Class Codes: H04W 28/0247 based on conditions of the access network or the infrastructure network central resource management H04W28/16
• CPC Class Codes: H04W 28/10 Flow control between communication endpoints
• CPC Class Codes: H04W 72/30 Resource management for broadcast services
• CPC Class Codes: H04W 8/04 Registration at HLR or HSS [Home Subscriber Server]
• CPC Class Codes: H04W 92/14 between access point controllers and backbone network device

Abstract

A method is provided for implementing Iu-Flex-Based MBMS. A SGSN sends an RAB request to an RNC. The RNC establishes a corresponding RAB for the multicast traffic according to the request and the SGSN sending the request. At the same time, if the RNC detects that a plurality of multicast traffics from other SGSNs correspond to a multicast traffic, the RNC will choose an SGSN as the primary SGSN, take the RAB between the primary SGSN and itself as the primary path to receive the multicast traffic, and maintain the connections to other SGSN. Transmission of the multicast traffic is then performed through the primary SGSN, during the multicast traffic transmission process. The RNC may change the primary SGSN when necessary, receive multicast traffic through the RAB of the new primary SGSN, and maintain the connections to other SGSNs. In this method, multicast traffics can be implemented simply and reliably. The method also helps to reduce consumption of network resources and improve network security and accounting management.

Claims

1. A method for implementing a Multimedia Broadcast/Multicast Service (MBMS) in a network environment having an intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes, the method comprising:

sending a request to establish a Radio Access Bearer (RAB) connection for multicast traffic from each of a plurality of Serving GPRS (General Packet Radio Services) Support Nodes (SGSNs) to a Radio Network Controller (RNC);

establishing a RAB connection for multicast traffic between the RNC and each of the SGSNs according to the request;

detecting by the RNC whether multicast traffic from more than one of the SGSNs corresponds to the same multicast service;

if yes

choosing one of the SGSNs as a primary SGSN, deeming the RAB connection between the primary SGSN and the RNC as a primary path to receive the multicast traffic, deeming the remaining SGSNs as secondary SGSNs, and maintaining RAB connections between the secondary SGSNs and the RNC by sending a minimum data volume or zero data volume from the secondary SGSNs to the RNC; and

transmitting the multicast traffic to the RNC through the primary SGSN.

2. The method of claim 1, wherein the transmitting the multicast traffic to the RNC through the primary SGSN comprises:

determining by the RNC whether to change the primary SGSN; and

if the RNC determines that the primary SGSN is to be changed, choosing one of the secondary SGSNs as a primary SGSN, receiving the multicast traffic through the RAB connection between the chosen primary SGSN and the RNC; and

maintaining RAB connections between the secondary SGSNs and the RNC.

3. The method of claim 2, wherein if the primary SGSN needs to be changed, the changing is performed when a network requires releasing the RAB connection between the RNC and the primary SGSN.

4. The method of claim 3, wherein the choosing one of the secondary SGSNs as the primary SGSN is performed according to factors including an order of precedence of multicast traffic received by the RNC through RAB connections between the RNC and the secondary SGSNs, a quality of transmission links, a load on transmission links, an order of precedence of transmission links established, QoS requirements of the primary and the secondary SGSNs for the multicast service.

5. The method of claim 4, before determining whether to change the primary SGSN, the method further comprises:

consulting by the RNC with the primary and the secondary SGSNs for QoS requirements for the multicast traffic to ensure the multicast RAB connection of the primary path to satisfy the QoS requirements of the primary and the secondary SGSNs for the multicast service.

6. The method of claim 5, further comprising:

when the multicast traffic received by a secondary SGSN from a Gateway GPRS Support Node (GGSN) does not exceed a restriction of the RNC, not forwarding the multicast traffic received from the GGSN to the RNC by the secondary SGSNs, or forwarding compressed messages to the RNC by the secondary SGSNs, and deeming by the secondary SGSN to have already received the multicast traffic at the RNC.

7. The method of claim 6, further comprising:

sending a statistical message about the multicast traffic received from the primary SGSN to the primary SGSN and to the secondary SGSNs by the RNC.

8. The method of claim 2, wherein if the primary SGSN needs to be changed, the changing is performed when an SGSN that has not established an RAB connection to the RNC initiates a request to establish a RAB connection for multicast traffic.

9. The method of claim 8, wherein the choosing one of the secondary SGSNs as the primary SGSN is performed according to factors including an order of precedence of multicast traffic received by the RNC through RAB connections between the RNC and the secondary SGSNs, a quality of transmission links, a load on transmission links, an order of precedence of transmission links established, QoS requirements of the primary and the secondary SGSNs for the multicast service.