US20120275457A1 - Method and apparatus for establishing multicast groups - Google Patents
Method and apparatus for establishing multicast groups Download PDFInfo
- Publication number
- US20120275457A1 US20120275457A1 US13/534,291 US201213534291A US2012275457A1 US 20120275457 A1 US20120275457 A1 US 20120275457A1 US 201213534291 A US201213534291 A US 201213534291A US 2012275457 A1 US2012275457 A1 US 2012275457A1
- Authority
- US
- United States
- Prior art keywords
- multicast
- group
- multicast group
- request
- user devices
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/185—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with management of multicast group membership
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
Definitions
- MM 130 sends a multicast group response message to UD 102 1 .
- the multicast group response message includes the multicast address assigned to the multicast group.
- the multicast group response message may include at least a portion of the parameters included in the request to establish the multicast group (e.g., for verification of the parameters used by MM 130 to establish the multicast group).
- the multicast group response message may include the multicast session description parameters accepted during establishment of the multicast group.
- the multicast group response message may include a multicast group identifier.
- UD 102 1 begins transmitting multicast traffic to the multicast group using the assigned multicast address.
- the UD 102 1 begins transmitting multicast traffic using a multicast session in accordance with the multicast session description parameters.
- MM 130 may periodically forward a current list of multicast group members to various combinations of non-member user devices which may be used by the non-member user devices as a basis for determining whether to request to join the multicast group (e.g., using SIP INVITE messages, SIP re-INVITE messages, and the like, as well as various combinations thereof).
- the SIP INVITE message (i.e., the request to establish the multicast group) is multicasted by SS 120 to all devices that listen to SIP signaling on the multicast signaling address specified by MM 130 (i.e., to all devices which have joined the multicast signaling group).
- the SS 120 multicasts the SIP INVITE message to UDs 102 1 , 102 2 , and 102 4 which have joined the multicast signaling group and MM 130 which formed the multicast signaling group.
- FIG. 5 depicts a high-level block diagram of a general-purpose computer suitable for use in performing the functions described herein.
- system 500 includes a processor element 502 (e.g., a CPU), a memory 504 , e.g., random access memory (RAM) and/or read only memory (ROM), a multicast group establishment/management module 505 , and various input/output devices 506 (e.g., storage devices, including but not limited to, a tape drive, a floppy drive, a hard disk drive or a compact disk drive, a receiver, a transmitter, a speaker, a display, an output port, and a user input device (such as a keyboard, a keypad, a mouse, and the like)).
- processor element 502 e.g., a CPU
- memory 504 e.g., random access memory (RAM) and/or read only memory (ROM)
- ROM read only memory
- multicast group establishment/management module 505 e.g., storage devices
- the present invention may be implemented in software and/or in a combination of software and hardware, e.g., using application specific integrated circuits (ASIC), a general purpose computer or any other hardware equivalents.
- ASIC application specific integrated circuits
- the present multicast group establishment/management module or process 505 can be loaded into memory 504 and executed by processor 502 to implement the functions as discussed above.
- multicast group establishment/management process 505 (including associated data structures) of the present invention can be stored on a computer readable medium or carrier, e.g., RAM memory, magnetic or optical drive or diskette and the like.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Telephonic Communication Services (AREA)
- Small-Scale Networks (AREA)
Abstract
Description
- This application is a continuation of pending U.S. patent application Ser. No. 11/551,516, filed on Oct. 20, 2006, entitled METHOD AND APPARATUS FOR ESTABLISHING MULTICAST GROUPS, which application is hereby incorporated herein by reference as if set forth in its entirety.
- The invention relates to the field of communication networks and, more specifically, to establishing multicast groups.
- Internet Protocol (IP) multicast is a bandwidth-conserving technology that delivers IP traffic conveying a single stream of information from a transmitter to multiple receivers which form a multicast group. IP multicast may be used for numerous applications such as videoconferencing, distance learning, software distribution, and the like. IP multicast packets are replicated in the network by multicast routers supporting various multicast protocols for managing multicast group membership, replicating IP multicast packets, and performing like functions associated with IP multicast. Dynamic establishment of multicast groups is currently performed using the Session Announcement Protocol (SAP), including the associated Session Directory Tool (SDR), as defined in RFC2974, which uses a distributed session directory and session announcements to dynamically establish a multicast group.
- Various deficiencies in the prior art are addressed through the invention of a method and apparatus for dynamically establishing a multicast group. The method includes receiving, from a first user device, a request to establish a multicast group including a plurality of parameters adapted for establishing the multicast group, obtaining a multicast address for the multicast group, and establishing the multicast group using the assigned multicast address and the parameters. The parameters include at least one multicast group definition parameter and at least one multicast session description parameter. The multicast address and at least a portion of the parameters are adapted for being provided to a second user device to enable the second user device to dynamically join the multicast group.
- The teachings of the present invention can be readily understood by considering the following detailed description in conjunction with the accompanying drawings, in which:
-
FIG. 1 depicts a high-level block diagram of a communication network; -
FIG. 2 depicts a high-level block diagram of a portion of the communication network ofFIG. 1 including signaling according to one embodiment of the present invention; -
FIG. 3 depicts a high-level block diagram of a portion of the communication network ofFIG. 1 including signaling according to one embodiment of the present invention; -
FIG. 4 depicts a high-level block diagram of a portion of the communication network ofFIG. 1 including signaling according to one embodiment of the present invention; and -
FIG. 5 depicts a high-level block diagram of a general-purpose computer suitable for use in performing at least a portion of the functions described herein. - To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures.
- The present invention enables dynamic establishment of multicast groups. The present invention enables dynamic establishment of multicast groups by user devices. The present invention enables signaling other than multicast protocol signaling (e.g., Session Initiation Protocol (SIP) signaling, Hypertext Transfer Protocol (HTTP) signaling, and the like, as well as various combinations thereof) to be used for establishing IP multicast groups. As such, the present invention supports robust, dynamic establishment of multicast groups.
-
FIG. 1 depicts a high-level block diagram of a communication network. Specifically,communication network 100 ofFIG. 1 includes a plurality of user devices (UDs) 102 1-102 4 (collectively, UDs 102), a transport network (TN) 110, a SIP server (SS) 120, and a Multicast Manager (MM) 130. The UDs 102 1-102 4 communicate withTN 110 using respective communication paths which may include network elements and communication links for transporting signaling and bearer traffic betweenUDs 102 andTN 110. The SS 120 and MM 130 communicate with TN 110 using communication paths which may include network elements and communication links for transporting signaling traffic between SS 120 and MM 130, respectively, and TN 110. - The UDs 102 include devices operable for participating in multicast sessions. For example, UDs 102 may include wireline phones, wireless phones, computers, and the like, as well as various combinations thereof. The UDs 102 support multicast functions enabling participation in multicast sessions. The UDs may initiate establishment of multicast groups. The UDs 102 may invite
other UDs 102 to join a multicast group andUDs 102 may request permission fromother UDs 102 to join a multicast group. After joining a multicast group, UDs 102 may operate as sending UDs and/or receiving UDs. The UDs 102 may support various applications requiring multicast capabilities, such as video conferencing applications, instant messaging applications, and the like, as well as various combinations thereof. - The TN 110 includes a plurality of routers 112 1-112 4 (collectively, routers 112). The routers 112 may include multicast routers (i.e., routers including multicast functionality, including support for one or more multicast protocols (e.g., Protocol Independent Multicast (PIM), Internet Group Management Protocol (IGMP), and like multicast protocols, as well as various combinations thereof). The multicast functionality may include IP multicast functionality. The routers 112 communicate using a plurality of communication paths (CPs) 114 which may include network elements and communication links adapted for transporting traffic between various combinations of routers 112.
- The SS 120 is a server supporting SIP signaling. The SS 120 may route SIP messages between UDs 102. For example, SS 120 may route SIP INVITE messages between
UDs 102 and betweenUDs 102 and routers 112, thereby enablingUDs 102 to inviteother UDs 102 to join a multicast group and enablingUDs 102 to request to join a multicast group. The SS 120 may route messages between UDs 102 and MM 130. The MM 130 is a system adapted for managing multicast functions. TheMM 130 may perform at least a portion of the functions described herein, including establishing a multicast group according to a request to establish a multicast group received from one ofUDs 102. - Although primarily depicted and described with respect to specific numbers and configurations of
UDs 102, routers 112,SSs 120, andMMs 130, the present invention may be implemented using various other numbers and configurations ofUDs 102, routers 112,SSs 120, andMMs 130, and, in some embodiments, other network elements adapted to perform various functions depicted and described herein. The operation ofUDs 102, routers 112,SS 120, and MM 130 in support of multicast establishment and communication functions of the present invention may be better understood with respect toFIG. 2-FIG . 5. -
FIG. 2 depicts a high-level block diagram of a portion of the communication network ofFIG. 1 including signaling according to one embodiment of the present invention. Thecommunication network portion 200 ofFIG. 2 includesUDs communication network portion 200 ofFIG. 2 further includesMM 130. For purposes of clarity in describing functions of the present invention, routers 112 and SS 120 are omitted (although, as depicted and described herein with respect toFIG. 3 andFIG. 4 , routers 112 and SS 120 may support various functions of the present invention). The signaling depicted and described herein with respect toFIG. 2 is performed in order to establish a multicastgroup including UDs - At
step 202, UD 102 1 creates a request to establish a multicast group and forwards the request to establish the multicast group toMM 130. The UD 102 1 forwards the request to establish the multicast group toMM 130. The UD 102 1 may forward the request to establish the multicast group toMM 130 using one or more of a plurality of protocols and associated message formats. In one embodiment, UD 102 1 forwards the request to establish the multicast group toMM 130, and other message and information may be exchanged, using SIP signaling. Use of SIP signaling for the present invention is depicted and described herein in more detail with respect toFIG. 3 ,FIG. 4 , andFIG. 5 . - The request to establish the multicast group includes one or more parameters. The one or more parameters included in the request to establish the multicast group include one or more parameters adapted to establish the multicast group. The one or more parameters included in the request to establish the multicast group include one or more parameters adapted to define the multicast group being established (denoted as multicast group definition parameters). The one or more parameters included in the request to establish the multicast group include one or more parameters adapted to describe the multicast session for the multicast group being established (denoted as multicast session description parameters). The one or more parameters included in the request to establish the multicast group may include various other parameters.
- The multicast group definition parameters may include a time at which the multicast group is scheduled to be established, a list of network elements authorized to initiate an invitation to join the multicast group, a list of user devices authorized to join the multicast group, and the like, as well as various combinations thereof. In one embodiment, in which the multicast group definition parameters include a list of user devices authorized to join the multicast group, the multicast group definition parameters may further include one or more privileges associated with the user devices authorized to join the multicast group.
- The time at which the multicast group is scheduled to be established may specify that the multicast group be established immediately or at a future date/time. The list of network elements authorized to initiate an invitation to join the multicast group may include one or more user devices (e.g., only
UD 102 1 is authorized to inviteother UDs 102 to join the multicast group), one or more management systems (e.g., MM 130), and the like, as well as various combinations thereof. The list of user devices authorized to join the multicast group may include any user devices (and, in some embodiments, may alternatively be provided as a list of users authorized to join the multicast group). - In one embodiment, the list of user devices authorized to join the multicast group may include, for each user device in the list, at least one parameter (attribute) adapted for indicating whether the user device should be automatically invited to join the multicast group in response to establishment of the multicast group. The parameter may be denoted as an invite parameter. In one embodiment, the invite parameter associated with a user device may indicate that the management system which established the multicast group (illustratively, MM 130) should automatically invite the user device to join the multicast group in response to establishment of the multicast group.
- In one embodiment, the list of user devices authorized to join the multicast group may include, for each user device in the list, at least one privilege parameter (attribute) defining participation by the user device in the multicast session. In one embodiment, a privilege parameter associated with each user device authorized to join a multicast group may include an indication as to whether the user device may transmit multicast traffic to other members of the multicast group (i.e., operate only as a receiving UD or as both a receiving and sending UD). Although described with respect to one specific privilege parameter, various other privilege parameters associated with individual UDs or groups of UDs may be specified in the request to establish the multicast group.
- In one embodiment, the request to establish the multicast group may specify that specific devices are authorized to invite specific sets of user devices (i.e., user devices authorized to join the multicast group) to join the multicast group. For example, the request to establish the multicast group may specify that
UD 102 1 is authorized to invite UD 102 2 (and other user devices (not depicted)) to join the multicast group andMM 130 is authorized to invite UD 102 4 (and other user devices (not depicted)) to join the multicast group. - The multicast session description parameters may include any parameter adapted for defining the multicast session by which multicast traffic is multicasted to members of the multicast group. In one embodiment, for example, multicast session description parameters include at least one of an IP address (i.e., multicast address to be used by members of the multicast group), one or more ports (i.e., multicast ports to be used by members of the multicast group), one or more coder-decoders (codecs) (i.e., codecs to be used by members of the multicast group), and the like, as well as various combinations thereof. Although described with respect to specific multicast session description parameters, various other multicast session description parameters may be specified in the request to establish the multicast group.
- In response to the request to establish the multicast group,
MM 130 obtains a multicast address for the multicast group. TheMM 130 may obtain the multicast address locally (e.g., from a list or range of available multicast addresses). TheMM 130 assigns the multicast address to the multicast group. TheMM 130 stores a mapping between the multicast group and the assigned multicast address. In one embodiment,MM 130 stores at least a portion of the parameters included in the request to establish the multicast group. TheMM 130 stores the parameters included in the request to establish the multicast group in a manner for associating the stored parameters with the multicast group. In one embodiment,MM 130 stores at least a portion of the multicast group definition parameters included the request to establish the multicast group. In one embodiment,MM 130 stores at least a portion of the multicast session description parameters included in the request to establish the multicast group. - At
step 204,MM 130 sends a multicast group response message toUD 102 1. The multicast group response message includes the multicast address assigned to the multicast group. The multicast group response message may include at least a portion of the parameters included in the request to establish the multicast group (e.g., for verification of the parameters used byMM 130 to establish the multicast group). In one such embodiment, the multicast group response message may include the multicast session description parameters accepted during establishment of the multicast group. The multicast group response message may include a multicast group identifier. Atstep 206,UD 102 1 begins transmitting multicast traffic to the multicast group using the assigned multicast address. TheUD 102 1 begins transmitting multicast traffic using a multicast session in accordance with the multicast session description parameters. - At
step 207,MM 130 initiates an invite toUD 102 4 to join the multicast group established byMM 130. In one embodiment, the invite toUD 102 4 to join the established multicast group may be initiated byMM 130 automatically in response to establishment of the multicast group. As described herein, in one embodiment, the request to establish the multicast group may include one or more parameters (denoted as an invite parameter(s)) adapted for identifying user device(s) 104 that should be automatically invited to join the multicast group in response to establishment of the multicast group. - At
step 208, other user devices begin joining the multicast group dynamically requested byUD 102 1 and dynamically established byMM 130. There are several ways in which user devices may join the multicast group. A user device may be invited to join the multicast group (e.g., by a user device that dynamically requested establishment of the multicast group (illustratively, UD 102 1), by a management system associated with establishment of the multicast group (illustratively, MM 130), and the like, as well as various combinations thereof). A user device may request to join the multicast group (e.g., sending a request to a user device which dynamically requested establishment of the multicast group (illustratively, UD 102 1), sending a request to a management system associated with establishment of the multicast group (illustratively, MM 130), and the like, as well as various combinations thereof). - At
step 208 A1,UD 102 1 sends an invitation toUD 102 2 invitingUD 102 2 to join the multicast group. In one embodiment, the invitation fromUD 102 1 toUD 102 2 invitingUD 102 2 to join the multicast group may include the multicast address of the multicast group, as well as one or more multicast session description parameters required byUD 102 2 in order to participate in the multicast group. Atstep 208 B1, in response to the invitation to join the multicast group,UD 102 2 accepts the invitation fromUD 102 1 to join the multicast group. TheUD 102 2 may then begin receiving multicast traffic over the multicast address of the multicast group. Although omitted for purposes of clarity, in one embodiment, UD 102 2 (or other UDs 102) may initiate a request toUD 102 1 to be joined to the multicast group. - At
step 208 A2,UD 102 4 initiates a request toMM 130 requesting to join the multicast group. Atstep 208 B2, in response to the request to join the multicast group,MM 130 accepts the request fromUD 102 4 to join the multicast group. In one embodiment, the acceptance byMM 130 of the request byUD 102 4 to join the multicast group may include the multicast address of the multicast group, as well as one or more multicast session description parameters required byUD 102 4 in order to participate in the multicast group. TheUD 102 4 may then begin receiving multicast traffic over the multicast address of the multicast group. Although omitted for purposes of clarity, in one embodiment,MM 130 may initiate a request to UD 102 4 (or other UDs 102) invitingUD 102 4 to join the multicast group. - Although described with respect to specific methods by which user devices join a multicast group, user devices may join a multicast group using various other methods. In one example, although omitted for purposes of clarity, a user device may join a multicast group through a router using standard multicast join capabilities. In another example, a user device may be joined to a multicast group by a management system (illustratively, MM 130) through communication between the manager and the router. These and other methods by which user devices may join an established multicast group may be better understood with respect to
FIG. 3 andFIG. 4 depicted and described herein. - Upon joining the multicast group, at step 210,
UD 102 2 begins receiving multicast traffic fromUD 102 1 over the multicast address of the multicast group. Upon joining the multicast group, atstep 212,UD 102 2 begins transmitting multicast traffic toUD UD 102 4 begins receiving multicast traffic fromUD 102 1 over the multicast address of the multicast group. Upon joining the multicast group, atstep 212,UD 102 4 begins receiving multicast traffic fromUD 102 2 over the multicast address of the multicast group. Although omitted for purposes of clarity,UDs -
FIG. 3 depicts a high-level block diagram of a portion of the communication network ofFIG. 1 including signaling according to one embodiment of the present invention. Thecommunication network portion 200 ofFIG. 2 includesUDs communication network portion 300 ofFIG. 3 further includesSS 120 andMM 130. The signaling depicted and described herein with respect toFIG. 3 is performed in order to establish a multicastgroup including UDs - At
step 302,UD 102 1 initiates a request to establish a multicast group. The request to establish the multicast group is similar to the request to establish the multicast group described with respect toFIG. 2 (i.e., the request to establish the multicast group may include various parameters adapted to establish the multicast group, including multicast group definition parameters, multicast session description parameters, and like parameters, as well as various combinations thereof). - As described herein, in one embodiment, the request to establish the multicast group may include a time at which the multicast group is scheduled to be established. If the multicast group is scheduled to be established immediately,
MM 130 immediately establishes the multicast group (e.g., by assigning a multicast address to the multicast group and storing at least a portion of the parameters included in the request to establish the multicast group). If the multicast group is scheduled to be established at a later time,MM 130 stores the information received with the request to establish the multicast group for use in establishing the multicast group at the scheduled time. For purposes of clarity in describing the invention, assume that the request to establish the multicast group initiated byUD 102 1 indicates that the multicast group is scheduled to be established immediately. - The
UD 102 1 forwards the request to establish the multicast group toSS 120. TheSS 120 forwards the request to establish the multicast group toMM 130. In one embodiment, the request to establish the multicast group is conveyed using a SIP INVITE message. In one embodiment, at least a portion of the parameters included in the request to establish the multicast group may be conveyed using one or more existing SIP fields, including SIP header fields and SIP body fields. In one embodiment, for example, at least a portion of the multicast session description parameters may be conveyed using the SIP session description field. In one embodiment, at least a portion of the parameters included in the request to establish the multicast group may be conveyed using new SIP fields, including new SIP header fields and new SIP body fields. In one embodiment,MM 130 may be implemented as a SIP application server. - The
MM 130 establishes the multicast group in response to the request to establish the multicast group. TheMM 130 establishes the multicast group in a manner similar to establishment of the multicast group as described herein with respect toFIG. 2 . TheMM 130 assigns the multicast address to the multicast group. TheMM 130 stores at least a portion of the parameters (e.g., multicast group definition parameters and multicast session description parameters) included in the request to establish the multicast group. TheMM 130 stores the multicast address and the parameters included in the request to establish the multicast group in a manner for associating the multicast address and the parameters with the multicast group. - At
step 304,MM 130 initiates a response to the request to establish the multicast group. TheMM 130 forwards the response toSS 120. TheSS 120 forwards the response toUD 102 1. The response includes the multicast address assigned for the multicast group. The response includes the multicast session description parameters associated with the multicast session for the multicast group. In one embodiment, the multicast session description parameters returned in the response are identical to the multicast session description parameters included in the request to establish the multicast group. The response to the request to establish the multicast group may be conveyed using a SIP OK message. - In one embodiment, in which at least a portion of the multicast session description parameters included in the request to establish the multicast session are not accepted by
MM 130, the response may include multicast session description parameters accepted by MM 130 (a portion of which may be different than the requested multicast session description parameters). This response may be conveyed using a SIP OK message. In one embodiment, in which at least a portion of the multicast session description parameters included in the request to establish the multicast session are not accepted byMM 130, the response may be a negative response (e.g., a SIP 486 BUSY message). - At
step 306,UD 102 1 begins transmitting multicast traffic to the multicast group. TheUD 102 1 begins transmitting multicast traffic using the assigned multicast address. TheUD 102 1 begins transmitting multicast traffic using a multicast session in accordance with the accepted multicast session description parameters (returned fromMM 130 toUD 102 1 in the response to the request to establish the multicast group). As depicted inFIG. 3 ,UD 102 1 transmits multicast traffic to router 112 1, from which the multicast traffic may be transmitted toother UDs 102 which join the multicast group, as well as to other routers 112 supportingUDs 102 which join the multicast group. Although depicted as beginning prior toother UDs 102 joining the multicast group, in other embodiments, transmission of multicast traffic byUD 102 1 to the multicast group may occur before, contemporaneous with, or after one or moreother UDs 102 begin joining the multicast group. - At
step 308, other user devices begin joining the multicast group dynamically requested byUD 102 1 and dynamically established byMM 130. There are several ways in which user devices may join the multicast group. A user device may be invited to join the multicast group (e.g., by a user device which dynamically requested establishment of the multicast group (illustratively, UD 102 1), by a management system associated with establishment of the multicast group (illustratively, MM 130), and the like, as well as various combinations thereof). There are several ways in which a user device may respond to an invitation to join the multicast group. - In one embodiment, a user device may respond to an invitation to join the multicast group using standard multicast join mechanisms of existing multicast protocols (e.g., sending a join message to a router associated with the user device, such as an Internet Group Management Protocol (IGMP) join message, a Multicast Listener Discover (MLD) message, and the like). Although omitted for purposes of clarity,
MM 130 is expected to be aware of such joins to (as well as leaves from) the multicast group through routers 112. TheMM 130 may be made aware of such joins/leaves using periodic polling fromMM 130 to routers 112, explicit signaling from routers 112 toMM 130, and the like, as well as various combinations thereof. - In one embodiment, in which the invitation to join the multicast group is sent using a SIP request message (e.g., SIP INVITE message), a user device may respond to an invitation to join the multicast group with a SIP response message (e.g., SIP OK). In this embodiment, the device which receives the SIP OK message may notify the appropriate router(s) that the user device is joining the multicast group. For example, if the SIP INVITE message originated from one of the
UDs 102, thatUD 102 may receive the SIP OK message and, in response to the SIP OK message, directly or indirectly (e.g., viaSS 120 and/or MM 130) inform the appropriate router that theUD 102 is joining the multicast group. For example, if the SIP INVITE message originated fromMM 130,MM 130 may receive the SIP OK message and, in response to the SIP OK message, inform the appropriate router that theUD 102 is joining the multicast group. - At
step 308 A1,UD 102 1 sends a SIP INVITE message toUD 102 2 invitingUD 102 2 to join the multicast group. TheUD 102 1 sends the SIP INVITE message toSS 120 which forwards the SIP INVITE message toUD 102 2. In one embodiment, the invitation fromUD 102 1 toUD 102 2 invitingUD 102 2 to join the multicast group may include the multicast address of the multicast group, as well as one or more multicast session description parameters required byUD 102 2 in order to participate in the multicast group. Atstep 308 B1, in response to the SIP INVITEmessage inviting UD 102 2 to join the multicast group,UD 102 2 accepts the invitation fromUD 102 1 to join the multicast group by initiating a standard multicast join to router 112 2 (e.g., using IGMP, MLD, and like protocols). - At
step 308 A2,MM 130 sends a SIP INVITE message toUD 102 4 invitingUD 102 24 to join the multicast group. TheMM 130 sends the SIP INVITE message toSS 120 which forwards the SIP INVITE message toUD 102 4. In one embodiment, the invitation fromMM 130 toUD 102 4 invitingUD 102 4 to join the multicast group may include the multicast address of the multicast group, as well as one or more multicast session description parameters required byUD 102 4 in order to participate in the multicast group. Atstep 308 B2, in response to the SIP INVITEmessage inviting UD 102 4 to join the multicast group,UD 102 4 accepts the invitation fromMM 130 to join the multicast group by initiating a SIP OK message in response to the SIP INVITE message. TheUD 102 4 sends the SIP OK message toSS 120. TheSS 120 forwards the SIP OK message toMM 130. In response to the SIP OK message,MM 130 notifies router 112 4 thatUD 102 4 is joining the multicast group. - At
step 310, upon joining the multicast group,UDs UD 102 1 over the multicast address of the multicast group. TheUD 102 2 receives multicast traffic fromUD 102 1 via routers 112 1 and 112 2. TheUD 102 4 receives multicast traffic fromUD 102 1 via routers 112 1, 112 2, and 112 4. Atstep 312, upon joining the multicast group,UD 102 2 begins transmitting multicast traffic to UDs 102 1 and 102 4 over the multicast group. TheUD 102 1 receives multicast traffic fromUD 102 2 via routers 112 1 and 112 2. TheUD 102 4 receives multicast traffic fromUD 102 2 via routers 112 2 and 112 4. Although omitted for purposes of clarity,UDs UD 102 to join the multicast group (e.g.,UD 102 1 or MM 130), and the like. - Although omitted for purposes of clarity, rather than being invited to join the multicast group, a user device may request to join the multicast group (e.g., sending a request to a user device which dynamically requested establishment of the multicast group (illustratively, UD 102 1), sending a request to a management system associated with establishment of the multicast group (illustratively, MM 130), and the like, as well as various combinations thereof). In one embodiment, a request by a user device to join the multicast group may be conveyed using one or more SIP messages (e.g., SIP INVITE messages). In one embodiment,
MM 130 may periodically forward a current list of multicast group members to various combinations of non-member user devices which may be used by the non-member user devices as a basis for determining whether to request to join the multicast group (e.g., using SIP INVITE messages, SIP re-INVITE messages, and the like, as well as various combinations thereof). - In one embodiment, in which a user device initiates a request to join the multicast group to a user device which dynamically requested establishment of the multicast group, the user device to which the request is initiated may respond directly to the user device which initiates the request or, alternatively, may forward the request to the management system associated with establishment of the multicast group. If the user device to which the request is initiated responds directly, the direct response may include the multicast address and associated multicast session description parameters of the multicast session. The direct response may be conveyed using one or more SIP messages (e.g., SIP INVITE, SIP OK, and the like, as well as various combinations thereof).
- If the request is forwarded to the management system associated with establishment of the multicast group, the management system (illustratively, MM 130) may respond to the request directly, or, alternatively, may instruct one or more routers associated with the joining user device that the user device is joining the multicast group. If the
MM 130 responds to the request directly, the direct response may include the multicast address and associated multicast session description parameters of the multicast session. The direct response may be conveyed using one or more SIP messages (e.g., SIP INVITE, SIP OK, and the like, as well as various combinations thereof). TheMM 130 may alternatively instruct one or more routers associated with the joining user device that the user device is joining the multicast group (which may be performed in a manner as described with respect to steps 308 B2). -
FIG. 4 depicts a high-level block diagram of a portion of the communication network ofFIG. 1 including signaling according to one embodiment of the present invention. Thecommunication network portion 400 ofFIG. 4 includesUDs communication network portion 400 ofFIG. 4 further includesSS 120 andMM 130. The signaling depicted and described herein with respect toFIG. 4 is performed in order to establish a multicastgroup including UDs - At
step 402,MM 130 registers withSS 120 using a SIP REGISTER message. TheMM 130 registers using a pre-defined multicast signaling address known by a number of UDs 102 (e.g., each ofUDs 102 depicted with respect toFIG. 1 ). TheMM 130 may manage one or more multicast signaling groups and each multicast signaling group may include one or more multicast signaling addresses. A multicast signaling group including multiple multicast signaling addresses enables further grouping ofUDs 102 included within the multicast signaling group, thereby enabling reductions in the number of signaling messages received byspecific UDs 102. - For example, UDs 102 1-102 4 may belong to a multicast signaling group and, within the multicast signaling group,
UDs UDs MM 130 to determine multicast signaling of leaf addresses using the associated root address. - At step 404, a SIP OK message is multicasted to UDs 102 that have joined the multicast signaling group (potentially all user devices in the network). For purposes of clarity, an assumption is made that
UDs UD 102 3 has not joined the multicast signaling group). In accordance with this assumption,SS 120 multicasts the SIP OK message to UDs 102 1 (via router 112 1), 102 2 (via routers 112 1 and 112 2), and 102 4 (via routers 112 1, 112 2, and 112 4). The signaling associated withsteps 402 and 404 may be performed at any time prior to requests to establish multicast groups. - At
step 406,UD 102 1 creates a request to establish a multicast group and forwards the request to establish the multicast group toMM 130. TheUD 102 1 conveys the request to establish the multicast group as a SIP INVITE message, transmitting the SIP INVITE message toSS 120, which forwards the SIP INVITE message toMM 130. In one embodiment, the request to establish the multicast group is substantially similar to the request to establish the multicast group depicted and described herein with respect tosteps FIG. 2 andFIG. 3 , respectively. In order to support establishment of multicast groups in which the multicast group is scheduled to be established at a future time,MM 130 may operate as a SIP application server (i.e., caching the request to establish the multicast group until the scheduled multicast group establishment time). - At step 408, the SIP INVITE message (i.e., the request to establish the multicast group) is multicasted by
SS 120 to all devices that listen to SIP signaling on the multicast signaling address specified by MM 130 (i.e., to all devices which have joined the multicast signaling group). TheSS 120 multicasts the SIP INVITE message to UDs 102 1, 102 2, and 102 4 which have joined the multicast signaling group andMM 130 which formed the multicast signaling group. TheSS 120 multicasts the SIP INVITE message to UDs 102 1 (via router 112 1), 102 2 (via routers 112 1 and 112 2), and 102 4 (via routers 112 1, 112 2, and 112 4), and MM 130 (via router 112 1). - As described herein, in one embodiment, the request to establish the multicast group may include a time at which the multicast group is scheduled to be established. If the multicast group is scheduled to be established immediately,
MM 130 immediately establishes the multicast group (e.g., by assigning a multicast address to the multicast group and storing at least a portion of the parameters included in the request to establish the multicast group). If the multicast group is scheduled to be established at a later time,MM 130 stores the information received with the request to establish the multicast group for use in establishing the multicast group at the scheduled time. For purposes of clarity in describing the invention, assume that the request to establish the multicast group initiated byUD 102 1 indicates that the multicast group is scheduled to be established immediately. - The
MM 130 establishes the multicast group in response to the request to establish the multicast group. TheMM 130 establishes the multicast group in a manner similar to establishment of the multicast group as described herein with respect toFIG. 2 andFIG. 3 . TheMM 130 assigns the multicast address to the multicast group. TheMM 130 stores at least a portion of the parameters (e.g., multicast group definition parameters and multicast session description parameters) included in the request to establish the multicast group. TheMM 130 stores the multicast address and the parameters included in the request to establish the multicast group in a manner for associating the multicast address and the parameters with the multicast group. - At
step 410,MM 130 initiates a SIP OK message in response to the request to establish the multicast group. TheMM 130 forwards the SIP OK message toSS 120 which forwards the SIP OK message toUD 102 1. The SIP OK response message fromMM 130 toUD 102 1 is not multicast bySS 120 using the multicast signaling group used to multicast the SIP INVITE message (i.e., the request to establish the multicast group). The response includes the multicast session description parameters associated with the multicast session for the multicast group, including the multicast address assigned to the multicast group. In one embodiment, the multicast session description parameters returned in the SIP OK message are identical to the multicast session description parameters included in the SIP INVITE message. In one embodiment, in which at least a portion of the multicast session description parameters included in the request to establish the multicast session are not accepted byMM 130, the response may include multicast session description parameters accepted byMM 130. - At
step 412,UD 102 1 begins transmitting multicast traffic to the multicast group. TheUD 102 1 begins transmitting multicast traffic using the assigned multicast address. TheUD 102 1 begins transmitting multicast traffic using a multicast session in accordance with the accepted multicast session description parameters (returned fromMM 130 toUD 102 1 in the response to the request to establish the multicast group). As depicted inFIG. 4 ,UD 102 1 transmits multicast traffic to router 112 1, from which the multicast traffic may be transmitted toother UDs 102 which join the multicast group, as well as to other routers 112 supportingUDs 102 which join the multicast group. Although depicted as beginning prior toother UDs 102 joining the multicast group, in other embodiments, transmission of multicast traffic byUD 102 1 to the multicast group may occur before, contemporaneous with, or after one or moreother UDs 102 begin joining the multicast group. - At
step 414,UD 102 2 responds to the SIP INVITE message (i.e., the request to establish the multicast group) with a SIP OK message. TheUD 102 2 transmits the SIP OK message toSS 120, which forwards the SIP OK message toUD 102 1. Since the SIP INVITE message multicast bySS 120 includes the multicast session description parameters,UD 102 2 receives the multicast session description parameters required to participate in the multicast session as part of the SIP INVITE message multicast bySS 120. TheUD 102 2, however, does not yet have the multicast address required to join the multicast group and participate in the multicast session. - At
step 416,UD 102 1 responds to the SIP OK message with a SIP ACK message. TheUD 102 1 transmits the SIP ACK message toSS 120, which forwards the SIP ACK message toUD 102 2. The SIP ACK message fromUD 102 1 includes the multicast address assigned byMM 130 and provided byMM 130 to UD 102 1 (in the SIP OK message of step 410). Although omitted for purposes of clarity, after receiving the multicast address fromUD 102 1,UD 102 2 may join the multicast group in one of several ways. In one embodiment,UD 102 2 may join the multicast group using one of the several methods depicted and described herein with respect toFIG. 3 . Atstep 418, upon joining the multicast group,UD 102 2 begins receiving multicast traffic fromUD 102 1 over the multicast address of the multicast group. TheUD 102 2 receives multicast traffic fromUD 102 1 via routers 112 1 and 112 2. - At
step 420, at some later time (e.g., later than the time at whichUD 1022 responds to the SIP INVITE message),UD 102 4 responds to the SIP INVITE message (i.e., the request to establish the multicast group) with a SIP OK message. TheUD 102 4 transmits the SIP OK message toSS 120, which forwards the SIP OK message toUD 102 1. Since the SIP INVITE message multicast bySS 120 includes the multicast session description parameters,UD 102 4 receives the multicast session description parameters required to participate in the multicast session as part of the SIP INVITE message multicast bySS 120. TheUD 102 4, however, does not yet have the multicast address required to join the multicast group and participate in the multicast session. - At
step 422,UD 102 1 responds to the SIP OK message with a SIP ACK message. TheUD 102 1 transmits the SIP ACK message toSS 120, which forwards the SIP ACK message toUD 102 4. The SIP ACK message fromUD 102 1 includes the multicast address assigned byMM 130 and provided byMM 130 to UD 102 1 (in the SIP OK message of step 410). Although omitted for purposes of clarity, after receiving the multicast address fromUD 102 1,UD 102 4 may join the multicast group in one of several ways. In one embodiment,UD 102 4 may join the multicast group using one of the several methods depicted and described herein with respect toFIG. 3 . Atstep 424, upon joining the multicast group,UD 102 4 begins receiving multicast traffic fromUD 102 1 over the multicast address of the multicast group. TheUD 102 4 receives multicast traffic fromUD 102 1 via routers 112 1, 112 2, and 112 4. - Although omitted for purposes of clarity,
UDs BYE messages UD 102 1. TheMM 130 will not receive such SIP BYE messages fromUDs MM 130 is in the signaling path (e.g., unlessMM 130 is implemented as a SIP application server). Although omitted for purposes of clarity, the multicast session may be closed by UD 102 1 (e.g., by sending a SIP BYE message to allUDs 102 which joined the multicast signaling group established by MM 130). The SIP BYE message is multicasted to allUDs 102 which joined the multicast signaling group using the multicast signaling group. - In one embodiment, in which
MM 130 is a SIP application server, the SIP OK message initiated by UD 102 1 (in step 404) and multicast toUDs 102 that have joined the multicast signaling group may be suppressed. In this embodiment, the SIP OK message would be received byMM 130, however,MM 130 would be able to suppress the multicasting of the SIP OK message to UDs 102 1, 102 2, and 102 4. - In one embodiment, in which
MM 130 is a SIP application server, the SIP INVITE message (i.e., the request to establish the multicast group multicast bySS 120 to all devices that listen to SIP signaling on the multicast signaling address) may be modified, before the SIP INVITE message is multicasted bySS 120 to all devices that listen to SIP signaling on the multicast signaling address, byMM 130 to include the multicast address assigned byMM 130. - In one embodiment, in which
MM 130 is a SIP application server, sinceMM 130 receives all SIP signaling,MM 130 could set up the multicast paths in the routers in response to SIP OK message received fromUDs 102 attempting to join the multicast group, thereby obviating the need for specific multicast joins by each of the UDs 102 (as well as obviating the need for eachUD 102 to support an associated multicast stack). - Although omitted from
FIGS. 2-4 for purposes of clarity, in one embodiment, the multicast session may be periodically re-announced (e.g., using a SIP RE-INVITE message which may be multicast to various combinations ofUDs 102 using one or more multicast signaling groups established as described herein). Although omitted for purposes of clarity, in one embodiment, after the multicast session is established, the multicast session may be altered. The multicast session may be altered by aUD 102 which requested establishment of the multicast group (illustratively, UD 102 1) or by one or moreother UDs 102 which join the multicast group and participate in the multicast session (illustratively,UDs 102 2 and 102 4). - The multicast session may be altered such that one or more of the parameters specified in the request to establish the multicast group (or one or more parameters altered in a previous request to alter the multicast session) may be altered. In one embodiment, at least a portion of the multicast group definition parameters may be altered (e.g., to change the list of UDs authorized to join the multicast group, to change permissions associated with one or more UDs authorized to join the multicast group, and the like, as well as various combinations thereof). In one embodiment, at least a portion of the multicast session description parameters may be altered (e.g., to change the ports used in the multicast session, to change the codec used in the multicast session, and the like, as well as various combinations thereof).
- In one embodiment, the multicast session may be altered by initiating a SIP RE-INVITE message to
MM 130. In one embodiment, the SIP RE-INVITE message may be multicast within the multicast group (i.e., so that only UDs 102 participating in the multicast session receive the SIP RE-INVITE message). For example, the SIP RE-INVITE message may be multicast toUDs UDs 102 other thanUDs 102 participating in the multicast session receive the SIP RE-INVITE message). For example, the SIP RE-INVITE message may be multicast toUDs - Although primarily depicted and described herein with respect to user devices, in some embodiments, since end users may access communication networks from multiple user devices associated with one or more network access points, references herein to user device may alternatively refer to a specific user irrespective of the user device by which that user accesses communication networks. In such embodiments, user device may refer to the end user associated with the user device. For example, although primarily described herein with respect to privilege parameters associated with each user device authorized to join a multicast group, privilege parameters may in fact be associated with the respective users associated with the user devices.
- Although primarily depicted and described herein with respect to an embodiment in which Any Source Multicast (ASM) is used, the present invention may be implemented in embodiments in which Source Specific Multicast (SSM) is used. For example, although primarily depicted and described herein with respect to multicast streams originating from
multiple UDs 102, in one embodiment, only one of theUDs 102 may have permission to transmit to other members of the multicast group. Although primarily depicted and described herein with respect to embodiments in which SIP signaling is used to establish and manage multicast groups, in other embodiments, various other protocols may be used to establish and maintain multicast groups. In one such embodiment, for example, HTTP may be used to establish and maintain multicast groups. -
FIG. 5 depicts a high-level block diagram of a general-purpose computer suitable for use in performing the functions described herein. As depicted inFIG. 5 ,system 500 includes a processor element 502 (e.g., a CPU), amemory 504, e.g., random access memory (RAM) and/or read only memory (ROM), a multicast group establishment/management module 505, and various input/output devices 506 (e.g., storage devices, including but not limited to, a tape drive, a floppy drive, a hard disk drive or a compact disk drive, a receiver, a transmitter, a speaker, a display, an output port, and a user input device (such as a keyboard, a keypad, a mouse, and the like)). - It should be noted that the present invention may be implemented in software and/or in a combination of software and hardware, e.g., using application specific integrated circuits (ASIC), a general purpose computer or any other hardware equivalents. In one embodiment, the present multicast group establishment/management module or
process 505 can be loaded intomemory 504 and executed byprocessor 502 to implement the functions as discussed above. As such, multicast group establishment/management process 505 (including associated data structures) of the present invention can be stored on a computer readable medium or carrier, e.g., RAM memory, magnetic or optical drive or diskette and the like. - Although various embodiments which incorporate the teachings of the present invention have been shown and described in detail herein, those skilled in the art can readily devise many other varied embodiments that still incorporate these teachings.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/534,291 US8767733B2 (en) | 2006-10-20 | 2012-06-27 | Method and apparatus for establishing multicast groups |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/551,516 US8249068B2 (en) | 2006-10-20 | 2006-10-20 | Method and apparatus for establishing multicast groups |
US13/534,291 US8767733B2 (en) | 2006-10-20 | 2012-06-27 | Method and apparatus for establishing multicast groups |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/551,516 Continuation US8249068B2 (en) | 2006-10-20 | 2006-10-20 | Method and apparatus for establishing multicast groups |
Publications (2)
Publication Number | Publication Date |
---|---|
US20120275457A1 true US20120275457A1 (en) | 2012-11-01 |
US8767733B2 US8767733B2 (en) | 2014-07-01 |
Family
ID=39247838
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/551,516 Active 2027-09-16 US8249068B2 (en) | 2006-10-20 | 2006-10-20 | Method and apparatus for establishing multicast groups |
US13/534,291 Expired - Fee Related US8767733B2 (en) | 2006-10-20 | 2012-06-27 | Method and apparatus for establishing multicast groups |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/551,516 Active 2027-09-16 US8249068B2 (en) | 2006-10-20 | 2006-10-20 | Method and apparatus for establishing multicast groups |
Country Status (8)
Country | Link |
---|---|
US (2) | US8249068B2 (en) |
EP (1) | EP2076998B1 (en) |
JP (1) | JP4949478B2 (en) |
KR (1) | KR101033057B1 (en) |
CN (1) | CN101529803B (en) |
AT (1) | ATE458327T1 (en) |
DE (1) | DE602007004875D1 (en) |
WO (1) | WO2008051400A2 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150222444A1 (en) * | 2014-02-04 | 2015-08-06 | Dipankar Sarkar | System and method for reliable multicast data transport |
US11038929B1 (en) * | 2017-05-24 | 2021-06-15 | First Orion Corp. | Efficient SIP message modification |
US20210194928A1 (en) * | 2019-12-18 | 2021-06-24 | Caliola Engineering, LLC | Secure overlay multicast |
Families Citing this family (35)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8249068B2 (en) * | 2006-10-20 | 2012-08-21 | Alcatel Lucent | Method and apparatus for establishing multicast groups |
US7626984B2 (en) * | 2006-10-25 | 2009-12-01 | At&T Corp. | Method and apparatus for providing congruent multicast and unicast routing |
JP5196685B2 (en) * | 2007-06-26 | 2013-05-15 | メディア パテンツ エセ.エレ. | Method and apparatus for managing multicast groups |
US20100046516A1 (en) * | 2007-06-26 | 2010-02-25 | Media Patents, S.L. | Methods and Devices for Managing Multicast Traffic |
US8203943B2 (en) * | 2007-08-27 | 2012-06-19 | Cisco Technology, Inc. | Colored access control lists for multicast forwarding using layer 2 control protocol |
US8064449B2 (en) * | 2007-10-15 | 2011-11-22 | Media Patents, S.L. | Methods and apparatus for managing multicast traffic |
US8184630B2 (en) * | 2007-10-15 | 2012-05-22 | Media Patents, S.L. | Method for managing multicast traffic in a data network and network equipment using said method |
WO2009056175A1 (en) * | 2007-10-30 | 2009-05-07 | Soporte Multivendor S.L. | Method for managing multicast traffic between routers communicating by means of a protocol integrating the pim protocol; and router and switch involved in said method |
CN101442502B (en) * | 2007-11-20 | 2013-10-09 | 华为技术有限公司 | Method, apparatus and system for monitoring session based on multicast technology |
US20090161590A1 (en) * | 2007-12-19 | 2009-06-25 | Motorola, Inc. | Multicast data stream selection in a communication system |
US9031068B2 (en) * | 2008-02-01 | 2015-05-12 | Media Patents, S.L. | Methods and apparatus for managing multicast traffic through a switch |
WO2009095041A1 (en) * | 2008-02-01 | 2009-08-06 | Soporte Multivendor S.L. | Method for managing multicast traffic through a switch operating in the layer 2 of the osi model, and router and switch involved in said method |
WO2009109684A1 (en) * | 2008-03-05 | 2009-09-11 | Media Patents, S. L. | Method for monitoring or managing devices connected to a data network |
KR101573329B1 (en) * | 2008-05-27 | 2015-12-01 | 삼성전자주식회사 | Method and apparatus for using internet protocol television based on application received by multi-cast session |
CN102271578B (en) * | 2008-12-11 | 2013-12-04 | 普罗秋斯数字健康公司 | Evaluation of gastrointestinal function using portable electroviscerography systems and methods of using the same |
US8885830B2 (en) * | 2009-05-04 | 2014-11-11 | Mitre Corporation | Method and apparatus for dynamically establishing and joining an encrypted collaborative communication session |
US8189584B2 (en) | 2009-07-27 | 2012-05-29 | Media Patents, S. L. | Multicast traffic management in a network interface |
US20110149960A1 (en) * | 2009-12-17 | 2011-06-23 | Media Patents, S.L. | Method and apparatus for filtering multicast packets |
US9497083B1 (en) * | 2013-06-10 | 2016-11-15 | Palo Alto Networks, Inc. | Discovering network nodes |
US10349225B2 (en) * | 2013-08-27 | 2019-07-09 | Verizon Patent And Licensing Inc. | Private multicast networks |
KR102138338B1 (en) * | 2014-03-06 | 2020-07-27 | 삼성전자주식회사 | Messaging system, terminal apparatus, server and messaging service providing method thereof |
KR101711698B1 (en) * | 2014-05-26 | 2017-03-02 | 한국전자통신연구원 | Method for processing data, and data processing apparatus |
JP6737272B2 (en) * | 2015-06-15 | 2020-08-05 | ソニー株式会社 | Communication device, communication method, program, and communication system |
US9800424B2 (en) | 2015-11-11 | 2017-10-24 | International Business Machines Corporation | Initial synchronization of a multicast group |
CN108605042B (en) * | 2015-12-19 | 2021-10-22 | 瑞典爱立信有限公司 | Method and apparatus for trust-based authentication in SDN clustering |
US11968132B2 (en) | 2017-03-24 | 2024-04-23 | Oracle International Corporation | System and method to use queue pair 1 for receiving multicast based announcements in multiple partitions in a high performance computing environment |
US10630499B2 (en) | 2017-03-24 | 2020-04-21 | Oracle International Corporation | System and method to provide path records derived from ARP responses and peer-to-peer negotiation based on homogeneous fabric attribute in a high performance computing environment |
CN106993279A (en) * | 2017-06-13 | 2017-07-28 | 深圳市伊特利网络科技有限公司 | The method for building up and system of terminal multicast group |
CN111034121B (en) | 2017-06-30 | 2022-04-08 | Idac控股公司 | Ad hoc link local multicast delivery of HTTP responses |
CN110351194B (en) * | 2018-04-04 | 2021-03-30 | 华为技术有限公司 | Multicast group creating method and device and multicast group joining method and device |
CN110798812B (en) * | 2018-08-02 | 2021-07-09 | 华为技术有限公司 | Group communication method and device |
CN110753371B (en) * | 2019-10-23 | 2023-04-18 | 腾讯科技(深圳)有限公司 | Data frame transmission method, device and equipment |
FI20195978A1 (en) * | 2019-11-15 | 2021-05-16 | Genelec Oy | Loudspeaker and loudspeaker control system |
US12010092B2 (en) * | 2021-06-24 | 2024-06-11 | Panduit Corp. | Distributed automatic multicast address assignment device and method |
CN113542129B (en) * | 2021-07-15 | 2023-01-24 | 无锡思朗电子科技有限公司 | Single transmission method using signal linked list |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7894377B2 (en) * | 2002-12-31 | 2011-02-22 | Motorola Solutions, Inc. | Method and system for group communications |
US8249068B2 (en) * | 2006-10-20 | 2012-08-21 | Alcatel Lucent | Method and apparatus for establishing multicast groups |
Family Cites Families (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5956491A (en) | 1996-04-01 | 1999-09-21 | Marks; Daniel L. | Group communications multiplexing system |
US6587943B1 (en) * | 1998-12-03 | 2003-07-01 | Nortel Networks Ltd. | Apparatus and method for limiting unauthorized access to a network multicast |
KR20030047874A (en) * | 2000-03-03 | 2003-06-18 | 퀄컴 인코포레이티드 | Method and apparatus for participating in group communication services in an existing communication system |
US7184415B2 (en) | 2001-12-07 | 2007-02-27 | Telefonaktiebolaget Lm Ericsson (Publ) | Service access system and method in a telecommunications network |
EP1454451A1 (en) * | 2001-12-15 | 2004-09-08 | Thomson Licensing S.A. | Videoconference bandwidth selection mechanism |
US7936752B2 (en) * | 2002-07-31 | 2011-05-03 | Cisco Technology, Inc. | Source specific multicast group to source mapping |
US7471645B2 (en) * | 2002-10-25 | 2008-12-30 | Hughes Network Systems, Llc | Method and system for multicast in a broadband satellite system |
US7558262B2 (en) * | 2002-11-29 | 2009-07-07 | Telefonaktiebolaget L M Ericsson (Publ) | Group hopping and channel zapping during transmission of multicast applications |
US7457815B2 (en) * | 2003-03-27 | 2008-11-25 | Apple Inc. | Method and apparatus for automatically providing network services |
US7574526B2 (en) * | 2003-07-31 | 2009-08-11 | International Business Machines Corporation | Multicast group management in infiniband |
US20050060411A1 (en) * | 2003-09-16 | 2005-03-17 | Stephane Coulombe | System and method for adaptation of peer-to-peer multimedia sessions |
US20050233776A1 (en) | 2004-04-16 | 2005-10-20 | Allen Andrew M | Method and apparatus for dynamic group address creation |
ES2278278T3 (en) * | 2004-04-16 | 2007-08-01 | Research In Motion Limited | METHOD AND APPARATUS FOR THE CREATION OF ADDRESSES OF DYNAMIC GROUPS. |
KR20060011262A (en) * | 2004-07-29 | 2006-02-03 | 삼성전자주식회사 | Apparatus and method of processing message in mobile communication service providing system |
FI20041075A0 (en) * | 2004-08-12 | 2004-08-12 | Nokia Corp | Sending information to a group of reception devices |
US7483416B2 (en) * | 2005-04-01 | 2009-01-27 | Cml Emergency Services Inc. | Internet protocol radio dispatch system and method |
JP2007067995A (en) * | 2005-09-01 | 2007-03-15 | Fujitsu Ltd | Apparatus and method for originating push-to-talk information |
-
2006
- 2006-10-20 US US11/551,516 patent/US8249068B2/en active Active
-
2007
- 2007-10-16 CN CN2007800387775A patent/CN101529803B/en not_active Expired - Fee Related
- 2007-10-16 DE DE602007004875T patent/DE602007004875D1/en active Active
- 2007-10-16 AT AT07852782T patent/ATE458327T1/en not_active IP Right Cessation
- 2007-10-16 WO PCT/US2007/022032 patent/WO2008051400A2/en active Application Filing
- 2007-10-16 JP JP2009533339A patent/JP4949478B2/en not_active Expired - Fee Related
- 2007-10-16 EP EP07852782A patent/EP2076998B1/en not_active Not-in-force
- 2007-10-16 KR KR1020097008023A patent/KR101033057B1/en not_active IP Right Cessation
-
2012
- 2012-06-27 US US13/534,291 patent/US8767733B2/en not_active Expired - Fee Related
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7894377B2 (en) * | 2002-12-31 | 2011-02-22 | Motorola Solutions, Inc. | Method and system for group communications |
US8249068B2 (en) * | 2006-10-20 | 2012-08-21 | Alcatel Lucent | Method and apparatus for establishing multicast groups |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150222444A1 (en) * | 2014-02-04 | 2015-08-06 | Dipankar Sarkar | System and method for reliable multicast data transport |
US9900168B2 (en) * | 2014-02-04 | 2018-02-20 | Dipankar Sarkar | System and method for reliable multicast data transport |
US11038929B1 (en) * | 2017-05-24 | 2021-06-15 | First Orion Corp. | Efficient SIP message modification |
US11811835B1 (en) | 2017-05-24 | 2023-11-07 | First Orion Corp. | Efficient SIP message modification |
US20210194928A1 (en) * | 2019-12-18 | 2021-06-24 | Caliola Engineering, LLC | Secure overlay multicast |
US11671452B2 (en) * | 2019-12-18 | 2023-06-06 | Caliola Engineering, LLC | Secure overlay multicast |
Also Published As
Publication number | Publication date |
---|---|
JP4949478B2 (en) | 2012-06-06 |
JP2010507338A (en) | 2010-03-04 |
EP2076998A2 (en) | 2009-07-08 |
EP2076998B1 (en) | 2010-02-17 |
KR101033057B1 (en) | 2011-05-06 |
US8249068B2 (en) | 2012-08-21 |
WO2008051400A3 (en) | 2008-06-19 |
ATE458327T1 (en) | 2010-03-15 |
US20080095183A1 (en) | 2008-04-24 |
CN101529803A (en) | 2009-09-09 |
DE602007004875D1 (en) | 2010-04-01 |
CN101529803B (en) | 2012-11-14 |
KR20090058574A (en) | 2009-06-09 |
US8767733B2 (en) | 2014-07-01 |
WO2008051400A2 (en) | 2008-05-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8767733B2 (en) | Method and apparatus for establishing multicast groups | |
US8737397B2 (en) | Method for converting between unicast sessions and multicast session | |
US8589547B2 (en) | Side channel for membership management within conference control | |
US5973724A (en) | Merging multiple teleconferences | |
US7801134B2 (en) | VoIP system, VoIP server and client, and multicast packet communication method | |
US7535857B2 (en) | Method for transmitting data from a participant device in a session in an internet protocol (IP) system | |
US20060235981A1 (en) | Providing a second service to a group of users using a first service | |
US20070083667A1 (en) | Method and system for multicast delivery of multimedia content on demand | |
KR101235511B1 (en) | Method of handling group communications in a communications network | |
US8102846B2 (en) | Method and apparatus for managing a multicast tree using a multicast tree manager and a content server | |
KR20050057417A (en) | A communication device for providing multimedia in a group communication network | |
CN101218777A (en) | Method and system for multicasting data in a communication network | |
WO2021228005A1 (en) | Session creation method and apparatus, and electronic device | |
WO2010108404A1 (en) | Method, device and system for a terminal selectively participating in a conference or controlling a terminal selectively participating in a conference | |
US8249612B2 (en) | Method, system, server, and client for transmitting media burst data | |
US9680880B2 (en) | Method and apparatus for supporting IP multicast | |
Ho et al. | A conference gateway supporting interoperability between SIP and H. 323 | |
CN101305623B (en) | Method and apparatus for determining PT server having controlling function | |
US20180227342A1 (en) | Media stream management system | |
Kausar et al. | End to end reliable multicast transport protocol requirements for collaborative multimedia systems | |
Uyar | Multiparty Video Conferencing over Internet | |
Kausar et al. | End-to-end reliable multicast transport protocol adaptation for floor control and other conference control functions requirements |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: CREDIT SUISSE AG, NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:LUCENT, ALCATEL;REEL/FRAME:029821/0001 Effective date: 20130130 Owner name: CREDIT SUISSE AG, NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:ALCATEL LUCENT;REEL/FRAME:029821/0001 Effective date: 20130130 |
|
AS | Assignment |
Owner name: ALCATEL-LUCENT USA INC., NEW JERSEY Free format text: MERGER;ASSIGNOR:LUCENT TECHNOLOGIES INC.;REEL/FRAME:031628/0469 Effective date: 20081101 Owner name: ALCATEL LUCENT, FRANCE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ALCATEL-LUCENT USA INC;REEL/FRAME:031628/0650 Effective date: 20120522 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
AS | Assignment |
Owner name: LUCENT TECHNOLOGIES INC., NEW JERSEY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BIJWAARD, DENNIS;DEHEER, ARJAN;PLAS, DIRK-JAAP;SIGNING DATES FROM 20061018 TO 20061019;REEL/FRAME:032837/0676 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: ALCATEL LUCENT, FRANCE Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG;REEL/FRAME:033868/0555 Effective date: 20140819 |
|
AS | Assignment |
Owner name: PROVENANCE ASSET GROUP LLC, CONNECTICUT Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NOKIA TECHNOLOGIES OY;NOKIA SOLUTIONS AND NETWORKS BV;ALCATEL LUCENT SAS;REEL/FRAME:043877/0001 Effective date: 20170912 Owner name: NOKIA USA INC., CALIFORNIA Free format text: SECURITY INTEREST;ASSIGNORS:PROVENANCE ASSET GROUP HOLDINGS, LLC;PROVENANCE ASSET GROUP LLC;REEL/FRAME:043879/0001 Effective date: 20170913 Owner name: CORTLAND CAPITAL MARKET SERVICES, LLC, ILLINOIS Free format text: SECURITY INTEREST;ASSIGNORS:PROVENANCE ASSET GROUP HOLDINGS, LLC;PROVENANCE ASSET GROUP, LLC;REEL/FRAME:043967/0001 Effective date: 20170913 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.) |
|
AS | Assignment |
Owner name: NOKIA US HOLDINGS INC., NEW JERSEY Free format text: ASSIGNMENT AND ASSUMPTION AGREEMENT;ASSIGNOR:NOKIA USA INC.;REEL/FRAME:048370/0682 Effective date: 20181220 |
|
AS | Assignment |
Owner name: PROVENANCE ASSET GROUP LLC, CONNECTICUT Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CORTLAND CAPITAL MARKETS SERVICES LLC;REEL/FRAME:058983/0104 Effective date: 20211101 Owner name: PROVENANCE ASSET GROUP HOLDINGS LLC, CONNECTICUT Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CORTLAND CAPITAL MARKETS SERVICES LLC;REEL/FRAME:058983/0104 Effective date: 20211101 Owner name: PROVENANCE ASSET GROUP LLC, CONNECTICUT Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:NOKIA US HOLDINGS INC.;REEL/FRAME:058363/0723 Effective date: 20211129 Owner name: PROVENANCE ASSET GROUP HOLDINGS LLC, CONNECTICUT Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:NOKIA US HOLDINGS INC.;REEL/FRAME:058363/0723 Effective date: 20211129 |
|
AS | Assignment |
Owner name: RPX CORPORATION, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:PROVENANCE ASSET GROUP LLC;REEL/FRAME:059352/0001 Effective date: 20211129 |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20220701 |