Method and system for multicasting data in a communication network

FIELD OF THE INVENTION

0001The present invention relates generally to the field of communication networks, and more specifically to multicasting data in communication networks.

BACKGROUND

0002With an increase in the need for communication and data transmission, there has been an increased demand for multicasting data, from a single source User Equipment (UE) to a plurality of UEs. Examples of data that can be transmitted include video data, voice data, and data files. Existing services for transmitting data to a plurality of UEs include Push-over-Cellular (PoC) service, Multi Media Broadcast/Multicast Service (MBMS), and Broadcast and Multicast Service (BCMCS). The PoC service enables a user to transmit the data to or interact with another user or group of users. In a group, only one user is allowed to transmit the data at a time, while the other users receive the data. However, the operation of the PoC service is inefficient. Transmission of the data through the PoC service requires duplication of the data packets, at every stage, over the communication network. Therefore, the PoC service has limited usage in operations requiring a high bandwidth.

0003MBMS is a Third Generation Partnership Project (3GPP) service and BCMCS is a Third Generation Partnership Project 2 (3GPP2) service. MBMS and BCMCS enable point-to-multipoint services in which the data is transmitted from the single-source UE to a plurality of UEs. However, both MBMS and the BCMCS enable unidirectional point-to-multipoint services only for Third Party Broadcast/Multicast Content Providers. Examples of these services include the CNN channel transmitting news to subscriber UEs.

SUMMARY OF THE INVENTION

0004According to one aspect of the invention, there is provided a method of multicasting data in a communication network to a specific group of user equipments (UEs) that includes a source UE, the method comprising: communicating at least one FlowID to the UEs in the specific group, the communicating including informing the UEs in the specific group of a broadcast server's IP address and port number to allow the UEs to set up resources in the network, for reception of wireless broadcast or wireless multicasts data; allowing the source UE to have a floor control for the specific group of UEs that are uniquely identified in the communication network, the allowing being provided by a push server in response to the push server receiving a floor control request from the source UE; receiving the data at the broadcast server, the data being transmitted from the source UE ; and multi-casting the data in non-duplicated packets from the broadcast server to the specific group of UEs.

0005According to another aspect of the invention, there is provided a system for multicasting data in a communication network, the data being provided by a source User Equipment (UE), the system including: a broadcast server, for receiving the data from the source UE through the communication network and transmitting the data in non-duplicated packets to a specific group of UEs; and a push server, for communicating with the broadcast server to communicate Flow ID information there between.

0006According to yet another aspect of the invention, there is provided a method performed by a UE that forms part a specific group of UEs in a communication network, the specific group of UEs being uniquely identified in the communication network by a FlowID, the method including: receiving from a push server at least one FlowID, a broadcast server's IP address and broadcast server's port number; transmitting a request to the network for a Multicast IP address and associated port number corresponding to the FlowID; receiving the Multicast IP address and associated port number; transmitting a request for registration of the source UE as a valid user of the FlowID; receiving acceptance of the request confirming that the UE is a valid user; and receiving data in a multi-cast transmission at the Multicast IP address and associated port number the data being in non-duplicated packets to all the UEs in the specific group of UEs.

BRIEF DESCRIPTION OF THE FIGURES

0007In order that the invention may be readily understood and put into practical effect, reference will now be made to at least one exemplary embodiment as illustrated with reference to the accompanying figures, where like reference numerals refer to identical or functionally similar elements throughout the separate views. The figures together with a detailed description below, are incorporated in and form part of the specification, and serve to further illustrate the embodiments and explain various principles and advantages, in accordance with the present invention where:

0008<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram illustrating the flow of data in a communication network, in accordance with an exemplary embodiment of the present invention;

0009<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram illustrating the flow of data in a communication network, in accordance with another exemplary embodiment of the present invention;

0010<figref idref="DRAWINGS">FIG. 3</figref> is a flowchart illustrating a method for multicasting data in a communication network, in accordance with an embodiment of the present invention;

0011<figref idref="DRAWINGS">FIG. 4</figref> is a flowchart illustrating a method performed by a User Equipment (UE) in a communication network, in accordance with an embodiment of the present invention;

0012<figref idref="DRAWINGS">FIG. 5</figref> and <figref idref="DRAWINGS">FIG. 6</figref> are flow diagrams illustrating call flows during the setup of a multicasting call as per the 3GPP2 standard in a communication network, in accordance with an embodiment of the present invention; and

0013<figref idref="DRAWINGS">FIG. 7</figref> is a flow diagram illustrating the transmission of data in an exemplary communication network, in accordance with an embodiment of the present invention.

0014Skilled artisans will appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions of some of the elements in the figures may be exaggerated relative to other elements to help to improve understanding of embodiments of the present invention.

DETAILED DESCRIPTION

0015Various embodiments of the present invention provide a method and a system for multicasting data in a communication network. A plurality of User Equipments (UEs) forms a specific group of UEs. A source UE, which is one of the UEs in the specific group of UEs, sends the data to other UEs in the group. The data is routed to a broadcast server in the communication network and the broadcast server multicasts the data, in non-duplicated packets, to the specific group of UEs. The data may also be routed through a push server, depending on whether the specific group of UEs is enabled to receive the multicast data.

0016Before describing in detail embodiments that are in accordance with the present invention, it should be observed that the embodiments reside primarily in combinations of method steps and system components related to multicasting data in a communication network. Accordingly, the system components and method steps have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

0017In this document, the terms “comprises,” “comprising,” or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, system or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, system or system. An element proceeded by “comprises . . . a” does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or system that comprises the element.

0018<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram illustrating the flow of data along data paths <b>128</b> in a communication network <b>100</b>, in accordance with an exemplary embodiment of the present invention. The communication network <b>100</b> includes a User Equipment (UE) <b>102</b>, a UE <b>103</b>, a UE <b>104</b>, a UE <b>105</b>, a UE <b>106</b>, base stations <b>108</b> with associated base station controllers <b>107</b>, a unicast data node <b>110</b>, a push server <b>112</b>, a broadcast server <b>114</b>, and a broadcast node <b>116</b>. Examples of UEs include mobile phones, laptops, Personal Digital Assistants (PDAs), and so forth. The communication network <b>100</b> may include a plurality of UEs. However, for the purpose of this description, the communication network <b>100</b> is shown to include the UEs <b>102</b>, <b>103</b>, <b>104</b>, <b>105</b> and <b>106</b>, which together form a specific group of UEs <b>118</b> in which a source UE transmits data to other UEs in the group. For example, the UE <b>102</b> is the source UE in the communication network <b>100</b>, which transmits the data to the UEs <b>103</b>, <b>104</b>, <b>105</b> and <b>106</b>. Examples of the data that can be transmitted include, but are not limited to, voice data, video data, and data files.

0019The unicast data node <b>110</b> and the broadcast node <b>116</b> are routers for routing the data to and from the wireless access network <b>109</b> comprising of a plurality of UEs, a set of base stations <b>108</b> and associated base station controllers <b>107</b> in the communication network <b>100</b>. The specific group of UEs <b>118</b> includes a multicast subscribed subgroup <b>120</b> and a non-multicast subscribed subgroup <b>122</b>. The multicast subscribed subgroup <b>120</b> includes the UEs <b>102</b>, <b>104</b> and <b>106</b> that are enabled to receive multicast data in the form of wireless broadcast packets such as, but not limited to Multi Media Broadcast/Multicast Service (MBMS) (for 3GPP) data packets or Broadcast and Multicast Service (BCMCS) (3GPP2) data packets. The non-multicast subscribed subgroup <b>122</b> includes the UEs <b>103</b> and <b>105</b> that are not enabled to receive multicast data in the form of MBMS (for 3GPP) data packets or BCMCS (3GPP2) data packets. A UE may belong to the multicast subscribed subgroup <b>120</b> or the non-multicast subscribed subgroup <b>122</b> depending on whether the UE supports the wireless broadcast /multicast services, and whether the corresponding base station to which the UE is connected supports the wireless broadcast/multicast services.

0020In the communication network <b>100</b>, the source UE <b>102</b> is in communication with the push server <b>112</b>. The push server <b>112</b> further communicates with the broadcast server <b>114</b> for controlling the transmission of data. The push server <b>112</b> can be a Push-over-Cellular (PoC) server, and the broadcast server <b>114</b> can be a MBMS content server or a BCMCS content server. The control information exchange between some of the entities, for example, the UEs in group <b>118</b> and the push server <b>112</b> in the communication network <b>100</b> can be in the form of SIP (Session Initiation Protocol) packets containing SDP (Session Description Protocol) attributes over Real Time Control Protocol (RTCP) packets. A data path <b>124</b> represents a communication interface established between the push server <b>112</b> and the broadcast server <b>114</b>. The data path <b>124</b> can be used for the exchange of security, authentication, and control information, using at least one of the existing, but not limited to, communication interfaces such as the User Datagram Protocol (UDP), the Transmission Control Protocol (TCP), and the Stream Control Transmission Protocol (SCTP) over Internet Protocol (IP). Existing MBMS or BCMCS service uses a FlowID <b>130</b> which identifies a unique multicast IP address and port number, which the UEs <b>120</b> can join in order to receive broadcast and multicast packets sent by the broadcast/multicast server through the communication network <b>100</b>. For example, in existing MBMS/BCMCS, the FlowID <b>130</b> is exchanged between the wireless network <b>109</b>, the broadcast/multicast node <b>116</b> and broadcast/multicast server <b>114</b>. In addition, the data path <b>124</b> can be used to exchange a FlowID <b>130</b>, which identifies specific group of UEs <b>118</b>. It should be noted that there may be more than one such FlowID <b>130</b> assigned for a group of UEs, each of these FlowIDs are typically assigned to a specific form of media such as voice, audio, video etc. A data path <b>126</b>, routed through the base stations <b>108</b>, represents the flow of RTCP packets, containing SDP attributes, in the communication network <b>100</b>.

0021The source UE <b>102</b>, or for that matter any UE in the group of UEs <b>118</b> sends data intended for the other UEs in group <b>118</b> to the multicast IP address and port number mapped by FlowID <b>130</b> through the wireless communication network <b>109</b> and the unicast data node <b>110</b>. Typically, the data is sent in the form of Real Time Protocol (RTP) packets. Data paths <b>128</b>, routed through the base stations <b>108</b>, represent the flow of RTP packets in the communication network <b>100</b>. The unicast data node <b>110</b>, routes the data along the data paths <b>128</b> to all the receivers that have joined the multicast IP address and port number mapped by the FlowID <b>130</b>, the receivers which include the broadcast server <b>114</b>, and optionally the push server <b>112</b>. The broadcast server <b>114</b> further transmits the data to the UEs <b>102</b>, <b>104</b> and <b>106</b> via the broadcast node <b>116</b> and the wireless communication network <b>109</b>. The transmission of the data from the broadcast server <b>114</b> to the UEs <b>102</b>, <b>104</b> and <b>106</b> is carried out as per the existing wireless broadcast/multicast mechanisms, such as, but not limited to MBMS or BCMCS standards.

0022In an embodiment of the present invention, the push server <b>114</b> keeps a record of the UEs in the multicast subscribed subgroup <b>120</b> and the non-multicast subscribed subgroup <b>122</b>. When it is required to send data to a UE in the non-multicast subscribed subgroup <b>122</b>, the push server <b>114</b> joins the multicast IP address group mapped by the FlowID <b>130</b> through a standard Multicast Group Management Protocol such as, but not limited to, Internet Group Management Protocol (IGMP). The push server <b>114</b> then receives data from the unicast data node <b>110</b>, and routes the data to the non-multicast subscribed subgroup <b>122</b> as per the existing standards. Typically, the data is also transmitted to the source UE <b>102</b>, since the source UE <b>102</b> is a part of the specific group of UEs <b>118</b>. The source UE <b>102</b> has the option of receiving the multicast data. To avoid an echo or inconvenience, the source UE <b>102</b> can choose to disregard the multicast data by operating on a mute mode while transmitting the data.

0023<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram illustrating the flow of data along data paths <b>228</b> in the communication network <b>100</b>, in accordance with another exemplary embodiment of the present invention. The source UE <b>102</b>, or for that matter any UE in the group of UEs <b>118</b>, sends data intended for the other UEs in group <b>118</b> to the push server <b>112</b> through the wireless communication network <b>109</b> and the unicast data node <b>110</b>. The data is typically sent as RTP packets and the data paths <b>228</b>, routed through the base stations <b>108</b>, represents the flow of RTP packets. The unicast data node <b>110</b> transmits the data to the push server <b>112</b>, which in turn transmits the data to the non-multicast subscribed subgroup <b>122</b>. To transmit data to the multicast subscribed subgroup <b>120</b>, the push server <b>112</b> routes the data to the to the multicast IP address and port number mapped by FlowID <b>130</b>, which includes broadcast server <b>114</b>. The broadcast server <b>114</b> sends the data in non-duplicated packets to the broadcast node <b>116</b>, which then transmits the data to the multicast subscribed subgroup. For example, the broadcast node <b>116</b> transmits the data to the UEs <b>102</b>, <b>104</b> and <b>106</b>, which are a part of the multicast subscribed subgroup, through the broadcast node <b>116</b> and wireless communication network <b>109</b>. The source UE <b>102</b> may also receive the multicast data, and may disregard the multicast data by operating on a mute mode.

0024<figref idref="DRAWINGS">FIG. 3</figref> is a flowchart illustrating a method for multicasting the data in the communication network <b>100</b>, using either data paths <b>128</b> or <b>228</b>. At step <b>301</b>, the specific group of UEs <b>118</b> is assigned a FlowID <b>130</b>. The source UE <b>102</b> or any other of the UEs in the specific group of UEs <b>118</b> sends a group conference initiation request to the push server <b>112</b>. The group conference initiation request includes an IP address and port number identifying the source UE <b>102</b> or another UE in the group of UEs <b>118</b>. After receiving the group conference initiation request, the push server <b>112</b> communicates with the broadcast server <b>114</b>, to assign the FlowID <b>130</b> to the specific group of UEs <b>118</b>. The FlowID <b>130</b> provides a unique identification of the specific group of UEs <b>118</b> in the communication network <b>100</b>. Assigning the FlowID <b>130</b> includes mapping it to a unique multicast Internet Protocol (IP) address and port number. Once the FlowID <b>130</b> is assigned, broadcast server <b>114</b> joins the multicast IP address port number mapped by the FlowID <b>130</b>.

0025At a step <b>302</b>, the assigned FlowID <b>130</b>, is communicated to the specific group of UEs <b>118</b> by the push server <b>112</b>. Also, the broadcast/multicast server <b>114</b>, and optionally, the push server <b>112</b>, join the multicast IP address group mapped to by the FlowID <b>130</b>. The communicating also includes informing the UEs in the specific group of a broadcast server's IP address and port number to allow the UEs to set up necessary resources in the network; for reception of wireless broadcast or wireless multicast data. These resources are set up provided that the necessary authentication and registration procedures have been setup successfully within the network <b>100</b>. Once the resources are set up successfully then the UEs in the specific group of UEs <b>120</b> also join the multicast group mapped by the FlowID <b>130</b>.

0026At a step <b>303</b>, the source UE <b>102</b> (or any other of the UEs in the UEs in the specific group of UEs) is allowed to have a floor control by the push server <b>112</b> for the specific group of UEs <b>118</b>. For instance, the source UE <b>102</b> can make a request for the floor control from the push server <b>112</b> by sending a floor control request. If the push server <b>112</b> allows floor control to the source UE <b>102</b>, in response to the floor control request, the source UE <b>102</b> sends the data as RTP packets either to the multicast IP address and port number mapped by the FlowID <b>130</b>, through the wireless communication network <b>109</b> and the unicast data node <b>110</b>, or to the push server <b>112</b> via the wireless communication network <b>109</b> and the unicast data node <b>110</b>. If the data is sent to the push server <b>112</b>, the push server <b>112</b> shall forward it to any receiver (which includes the broadcast server <b>114</b>), which is a part of the multicast IP address and port number mapped by the FlowID <b>130</b> by the push server <b>112</b>.

0027At step <b>304</b>, the data is received at the broadcast server <b>114</b>. At step <b>306</b>, the data is multicast to the multicast subscribed subgroup <b>120</b> in the specific group of UEs <b>118</b>. The broadcast server <b>114</b> sends the data in non-duplicated packets to the broadcast node <b>116</b>, which then transmits the data to the multicast subscribed subgroup. For example, the broadcast server <b>114</b> sends the data in non-duplicated packets to the broadcast node <b>116</b>, which then transmits the data to the UEs <b>102</b>, <b>104</b> and <b>106</b> through the wireless communication network <b>109</b>. It should be noted that if the push server <b>112</b> receives the data transmitted by source UE <b>102</b> for the other UEs in group <b>118</b>, the push server <b>112</b> forwards the data to the non-multicast subscribed subgroup <b>122</b> in the specific group of UEs <b>118</b>.

0028<figref idref="DRAWINGS">FIG. 4</figref> is a flowchart of a method performed by the source UE <b>102</b> or any other UE in group <b>120</b> in the communication network <b>100</b>, using either data paths <b>128</b> or <b>228</b>. At step <b>400</b>, the source UE <b>102</b> receives a FlowID <b>130</b>, and the IP address, port number of the broadcast/multicast server <b>114</b> from the push server while in the process of setting up a group conference call.

0029At step <b>402</b>, the method performs transmitting a request the network <b>100</b> for a Multicast IP address and associated port number corresponding (mapped) to the FlowID. Next, at step <b>404</b>, the UE receives the Multicast IP address and associated port number, thereafter at step <b>406</b>, the source UE effects transmitting a request for registration of the source UE as a valid user of the FlowID. In response to step <b>406</b>, the network may accept the source UE as a valid user. Hence, if accepted, then at a step <b>408</b>, the source UE allows for receiving acceptance of the request confirming that the UE is a valid user.

0030Finally, at a step <b>410</b>, the source UE can operate to provide for receiving data in a multi-cast transmission at the Multicast IP address and associated port number the data being in non-duplicated packets to all the UEs in the specific group of UEs. The source UE <b>102</b> informs the push server that it has joined the multicast IP address and port number mapped by the FlowID by echoing back the FlowID in subsequent control messages to the push server <b>112</b>. Furthermore, if the data paths <b>128</b> are used for routing data then the source UE <b>102</b> optionally receives instructions from the push server <b>112</b> instructing the source UE <b>102</b> to set the intended target destination for any RTP or non control packet to the multicast IP address and port number mapped by the FlowID <b>130</b>. Alternatively, if the data paths <b>228</b> are used for routing data, then the source UE <b>102</b> receives instructions from the push server <b>112</b> instructing the source UE <b>102</b> to set the intended target destination for any RTP or non control packet to the IP address and port number of the push server <b>112</b>.

0031It should be noted that after <b>410</b>, the source UE <b>102</b> may send a floor control request to the push server <b>112</b>. The floor control request is for floor control of the specific group of UEs <b>118</b> that are uniquely identified in the communication network <b>100</b>. Floor control is required to enable the transmission of the data from the source UE <b>102</b> with the floor control to the specific group of UEs <b>118</b>. The source UE <b>102</b> receives allowance of the floor control from the push server <b>112</b>.

0032The push server <b>112</b> allows the source UE <b>112</b> to have floor control, in response to the floor control request made by the source UE <b>102</b>. The source UE <b>102</b> starts transmitting the data after receiving the floor control. The source UE <b>102</b> transmits the data as RTP packets that eventually reach the broadcast server <b>114</b> using either data paths <b>128</b> or <b>228</b>. The broadcast server <b>114</b> multicasts the data in non-duplicated packets to all the UEs in the specific group of UEs <b>118</b>. These non-duplicated packets are routed through communication network <b>100</b> and reach the base stations <b>108</b>. The base stations <b>108</b> then transmit the packets to the specific group of UEs <b>118</b>. Also, the source UE <b>102</b> receives the multicast data from the broadcast server <b>114</b>. The source UE <b>102</b> is one of the UEs in the specific group of UEs <b>118</b>, in accordance with an embodiment of the present invention. The source UE <b>102</b> may choose to disregard the multicast data, in order to avoid an echo at its end and the source UE <b>102</b> may disregard the multicast data by operating on a mute mode during transmission of the data.

0033<figref idref="DRAWINGS">FIG. 5</figref> and <figref idref="DRAWINGS">FIG. 6</figref> are flow diagrams illustrating call flows during the setup of a multicasting call as per the 3GPP2 standard in a communication network <b>500</b>, in accordance with an embodiment of the present invention. It should be noted that though these flow diagrams are explained in accordance with the 3GPP2 standard, any other standard that supports multicasting of data can also be used to enable various embodiments of the present invention. The communication network <b>500</b> includes a source UE <b>502</b>, a wireless network <b>504</b>, a broadcast node <b>506</b>, a unicast data node <b>507</b>, a push server <b>508</b>, a broadcast controller <b>510</b>, a broadcast server <b>512</b>, and an Authentication, Authorization and Accountin(AAA) server <b>514</b>. The broadcast controller <b>510</b> is responsible for managing and providing the BCMCS session information to the broadcast node <b>506</b> and broadcast server <b>512</b>.

0034The broadcast controller <b>510</b> and the broadcast server <b>512</b> can be combined into a single entity that performs the functions of both the broadcast controller <b>510</b> and the broadcast server <b>512</b>. The source UE <b>102</b> transmits the data to the specific group of UEs <b>118</b>. The data is sent to the unicast data node <b>507</b> through the wireless network <b>504</b>. The broadcast node <b>506</b> and the unicast data node <b>507</b> are routers for routing the data in the communication network <b>500</b>. The unicast data node <b>507</b> routes the data further to the push server <b>508</b>. Examples of the push server <b>112</b> include a Push-over-Cellular (PoC) server. The push server <b>508</b> routes the data to the broadcast server <b>512</b> through the broadcast controller <b>510</b>. Examples of the broadcast server <b>512</b> include MBMS content servers and BCMCS content servers. The AAA server <b>514</b> is an authentication server used in network access control. It stores the usernames and passwords to identify the UEs. The AAA server <b>514</b> is also referred to as a Radius server.

0035A signal <b>516</b> represents call origination, wherein the source UE <b>502</b> communicates with the network <b>504</b>. A signal <b>518</b> sends a group conference initiation request in the form of a SIP_INVITE message. In an embodiment of the present invention, the SIP messages (for example, SIP_INVITE, SIP_UPDATE and the like) described herein include SDP attributes. The source UE <b>502</b> sends the group conference initiation request to the push server <b>508</b>, The group conference initiation request includes an IP address and port number identifying the source UE <b>502</b>. After receiving the group conference initiation request, the push server <b>508</b> communicates with the broadcast controller <b>510</b>, to assign a FlowID to the specific group of UEs <b>118</b> to which the source UE <b>502</b> belongs, through a signal <b>520</b>. The FlowID provides a unique identification of the specific group of UEs <b>118</b> in the communication network <b>500</b>. Assigning the FlowID includes mapping it to a unique multicast Internet Protocol (IP) address and port number.

0036The FlowID can be assigned statically or dynamically. Static assigning of the FlowID includes mapping a unique multicast Internet Protocol (IP) address and port number permanently to the specific group of UEs <b>118</b>. Dynamic assigning of the FlowID includes instructing the broadcast controller <b>510</b> to release the dynamic FlowID when a last UE leaves the specific group of UEs <b>118</b>. Also, the broadcast server <b>512</b> and optionally the push server <b>508</b> are removed from the multicast IP address and port number corresponding to the flow ID. The dynamic assigning of the FlowID enables the broadcast controller <b>510</b> to assign the released FlowID to another specific group of UEs <b>118</b>. Typically, once the FlowID <b>130</b> is assigned the broadcast server <b>512</b> joins as a member of the multicast IP address and port number mapped by the FlowID <b>130</b> by a signal <b>521</b>, Now the broadcast server <b>512</b> is in a position to receive any data that is sent to the multicast IP address and port number. The assigned FlowIDs are communicated to the source UE <b>502</b> through a signal <b>522</b>, along with the IP address and port number of the broadcast controller <b>510</b>. This communication is in the form of an SIP_OK. The SIP_OK also contains an additional new SDP attribute, which has the IP address and port number of the broadcast controller <b>510</b> and the FlowID <b>130</b>.

0037Through a signal <b>524</b>, the source UE <b>502</b> sends an information acquisition request to the broadcast controller <b>510</b>. The information acquisition request relates to a multicast IP address of the FlowID and a port number. The necessary authentication procedures are carried out through a signal <b>526</b> between the broadcast controller <b>510</b> and the AAA server <b>514</b>, to authenticate the source UE <b>502</b>. After authentication procedures, the broadcast controller <b>510</b> communicates a multicast IP address and the port number mapped by the FlowID <b>130</b> to the source UE <b>502</b> through a signal <b>528</b>, in response to the information acquisition request.

0038Signals <b>532</b> through <b>546</b> (with reference to <figref idref="DRAWINGS">FIG. 5</figref> and <figref idref="DRAWINGS">FIG. 6</figref>) represent control signals involved in registering the source UE <b>502</b> as a valid recipient of any packets intended for the multicast IP address and port number mapped by the FlowID <b>130</b>. The source UE <b>502</b> sends a registration request to the network <b>504</b> through a signal <b>532</b>. The registration request includes the FlowID <b>130</b> received by the source UE <b>502</b>. The network <b>504</b> forwards the registration request to the broadcast node <b>506</b> through a signal <b>534</b>. The broadcast node <b>506</b> forwards the registration request to the broadcast controller <b>510</b> through a signal <b>536</b>. The broadcast controller <b>510</b> sends an acceptance to the broadcast node <b>506</b>, in response to the registration request, through a signal <b>538</b>. Through signals <b>540</b> through <b>544</b>, the wireless network <b>504</b> communicates with the broadcast node <b>506</b> for acceptance of the registration request. Through the signal <b>540</b>, the broadcast node <b>506</b> communicates a service response to the network <b>504</b>. Through the signal <b>542</b>, the network <b>504</b> communicates a registration request to the broadcast node <b>506</b>. Through the signal <b>544</b>, the broadcast node <b>506</b> communicates a registration response to the network <b>504</b>. The broadcast node <b>506</b> communicates the registration acceptance to the source UE <b>502</b>, thereby accepting the source UE <b>502</b> a part of the specific group of UEs <b>118</b>, through a signal <b>546</b>.

0039Through a signal <b>548</b>, the source UE <b>502</b> sends a SIP_UPDATE message to the push server <b>508</b>. The additional SDP attributes in the SIP_UPDATE message echoes back the FlowID <b>130</b> for the multicast subscribed group of UEs. Through a signal <b>550</b>, the push server <b>508</b> acknowledges the SIP_UPDATE message by sending a SIP_OK message, with the additional SDP attribute containing the FlowID <b>130</b> to the multicast subscribed group of UEs. In an embodiment of the present invention, the push server <b>508</b> has the option of joining the multicast subscribed subgroup. The push server <b>508</b> joins the multicast subscribed subgroup <b>120</b> when the specific group of UEs <b>118</b> includes at least one member of UE in the non-multicast subscribed subgroup <b>122</b>.

0040After joining the multicast subscribed group, the push server <b>508</b> is capable of receiving data intended to the multicast group of UEs <b>120</b>, and also capable of forwarding the data to the non-multicast subscribed subgroup <b>122</b>. In an embodiment of the present invention, when a new UE joins the specific group of UEs <b>118</b>, the push server <b>112</b> communicates the FlowID, IP address, the IP address and port number of the broadcast controller <b>510</b> and other relevant information to the new UE. This enables the new UE to setup the multicast capability if it supports it. This enables the new UE to receive multicast data in non-duplicated packets.

0041<figref idref="DRAWINGS">FIG. 7</figref> is a flow diagram illustrating the transmission of the data in an exemplary communication network <b>700</b>, in accordance with an embodiment of the present invention. The communication network <b>700</b> includes a specific group of UEs <b>702</b>, in addition to the entities referred to in <figref idref="DRAWINGS">FIG. 5</figref> and <figref idref="DRAWINGS">FIG. 6</figref>. The source UE <b>502</b> transmits the data to the specific group of UEs <b>702</b>. The source UE <b>502</b> makes a request for floor control to the push server <b>508</b>, for the purpose of transmitting the data, through a signal <b>704</b>. Through a signal <b>706</b>, after receiving permission for transmission of the data, the UE <b>502</b> sends the data to the multicast IP address and port number mapped by the FlowID <b>130</b>, either directly (as in <figref idref="DRAWINGS">FIG. 1</figref> or indirectly as in <figref idref="DRAWINGS">FIG. 2</figref>). Since the broadcast server <b>512</b> has also joined to the corresponding multicast IP address and port number mapped by FlowID, the broadcast server <b>512</b> receives the data. Through a signal <b>708</b>, the broadcast server <b>512</b> multicasts the data to the specific group of UEs <b>702</b>. During this process, the source UE <b>502</b> is operating on a mute mode, so it does not receive the data, which may cause an echo in the source UE <b>502</b>. The source UE <b>502</b> makes a request for release of floor control to the push server <b>508</b> through a signal <b>710</b>, after sending the data. Once the transmission of the data is complete, the source UE <b>502</b> emerges from the mute mode.

0042Advantageously, the present invention provides a method and system for multicasting data as described above, typically the system comprises the broadcast server <b>112</b> and multicast server <b>114</b> in which data is provided by a source User Equipment (UE) and the broadcast server <b>112</b> provides for receiving the data from the source UE through the communication network <b>100</b> and transmitting the data in non-duplicated packets to a specific group of UEs. Also, the push server <b>112</b> provides for communicating with the broadcast server <b>114</b> to communicate the Flow ID information.

0043Various embodiments of the present invention, as described above, provide a method and system for multicasting data from a single UE to a plurality of UEs in a communication network. The data is sent in non-duplicated packets, thereby resulting in efficient network resource utilization. Further, in case some UEs do not support the capability to receive multicast data, the data is sent to these UEs as per the existing standards.

0044It will be appreciated that embodiments of the invention described herein may be comprised of one or more conventional processors and unique stored program instructions that control the one or more processors to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions of the method and system for multicasting data in a communication network described herein. The non-processor circuits may include, but are not limited to, a radio receiver, a radio transmitter, signal drivers, clock circuits, power source circuits, and user input devices. As such, these functions may be interpreted as steps of a method to multicast data in a communication network. Alternatively, some or all functions could be implemented by a state machine that has no stored program instructions, or in one or more application specific integrated circuits (ASICs), in which each function or some combinations of certain of the functions are implemented as custom logic. Of course, a combination of the two approaches could be used. Thus, methods and means for these functions have been described herein. Further, it is expected that one of ordinary skill, notwithstanding possibly significant effort and many design choices motivated by, for example, available time, current technology, and economic considerations, when guided by the concepts and principles disclosed herein will be readily capable of generating such software instructions and programs and ICs with minimal experimentation.

0045In the foregoing specification, specific embodiments of the present invention have been described. However, one of ordinary skill in the art appreciates that various modifications and changes can be made without departing from the scope of the present invention as set forth in the claims below. Accordingly, the specification and figures are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of present invention. The benefits, advantages, solutions to problems, and any element(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential features or elements of any or all the claims. The invention is defined solely by the appended claims including any amendments made during the pendency of this application and all equivalents of those claims.