WO2003021891A1 - Use of ip-multicast technology for 2-party calls in mobile communication networks - Google Patents

Use of ip-multicast technology for 2-party calls in mobile communication networks Download PDF

Info

Publication number
WO2003021891A1
WO2003021891A1 PCT/US2002/023438 US0223438W WO03021891A1 WO 2003021891 A1 WO2003021891 A1 WO 2003021891A1 US 0223438 W US0223438 W US 0223438W WO 03021891 A1 WO03021891 A1 WO 03021891A1
Authority
WO
WIPO (PCT)
Prior art keywords
site
multicast
call
address
message
Prior art date
Application number
PCT/US2002/023438
Other languages
French (fr)
Inventor
Surender Kumar
Mark L. Shaughnessy
James E. Mathis
Gregory A. Dertz
Michael D. Sasuta
Original Assignee
Motorola, Inc.
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Motorola, Inc. filed Critical Motorola, Inc.
Priority to AT02750268T priority Critical patent/ATE516681T1/en
Priority to IL15531002A priority patent/IL155310A0/en
Priority to EP02750268A priority patent/EP1423943B1/en
Publication of WO2003021891A1 publication Critical patent/WO2003021891A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/16Arrangements for providing special services to substations
    • H04L12/18Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1886Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with traffic restrictions for efficiency improvement, e.g. involving subnets or subdomains
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/15Flow control; Congestion control in relation to multipoint traffic
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/70Admission control; Resource allocation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/70Admission control; Resource allocation
    • H04L47/80Actions related to the user profile or the type of traffic
    • H04L47/801Real time traffic
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/70Admission control; Resource allocation
    • H04L47/80Actions related to the user profile or the type of traffic
    • H04L47/806Broadcast or multicast traffic
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/70Admission control; Resource allocation
    • H04L47/82Miscellaneous aspects
    • H04L47/824Applicable to portable or mobile terminals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/50Address allocation
    • H04L61/5069Address allocation for group communication, multicast communication or broadcast communication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066Session management
    • H04L65/1101Session protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60Network streaming of media packets
    • H04L65/61Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/611Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for multicast or broadcast
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/26Network addressing or numbering for mobility support
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/16Arrangements for providing special services to substations
    • H04L12/18Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W84/00Network topologies

Definitions

  • This invention relates generally to wireless communication systems and, more particularly, to IP multicast communication systems.
  • FIG. 1 A typical example of such a system 100 is illustrated in FIG. 1.
  • the configuration shown in FIG. 1 is typical in wireless communications systems such as Global System for Mobile Communications (GSM), Advanced Mobile Phone Service (AMPS), Terrestrial Trunked Radio (TETRA), "IDEN”, and "SMARTZONE” systems.
  • GSM Global System for Mobile Communications
  • AMPS Advanced Mobile Phone Service
  • TETRA Terrestrial Trunked Radio
  • IDEN IDEN
  • SMARTZONE a central switch 101 provides connections between cell sites 104-107.
  • a plurality of communication units 110-115 wirelessly communicate with the sites 104-107 and each other, and are often logically divided into various subgroups or talk groups.
  • the call processing management and switching functionality are generally contained within the same physical unit, i.e., the central switch 101.
  • the sites 104-107 are connected to the central switch 101 through dedicated or on-demand links and intermediate processors 102-103 in what is often called a "star" configuration.
  • Some very large systems use a hierarchy of such "stars" where intervening concentrators group the links from multiple cell sites and do some lower level processing on them before passing them up to the central switch.
  • IP Multicast communication systems include the referenced U.S. Patent Application Ser. No. 09/283,121, now issued as U.S. Patent No. 6,141,347; and U.S. Patent Application Serial No. 09/464,269, titled "Methods for Implementing a Talkgroup Call in a Multicast IP Network,” each of which is assigned to Motorola, Inc. and incorporated herein by reference in its entirety.
  • IP multicasting protocols are considered to be more efficient and less costly than traditional circuit-switched networks.
  • the multicast IP network defines a distributed, rather than centralized, connection and mobility processing environment where there is no centralized location register (VLR/HLR). Rather, mobility information is inherent to the packet network as communication units register or de-register individual or group affiliations with cells, and the cells join or leave multicast IP addresses to participate in traffic for the communication units.
  • VLR/HLR centralized location register
  • the benefits of a distributed connection and mobility processing environment include fully localized resource management, fully distributed mobility management and easy network scalability.
  • distributed connection and mobility processing networks such as multicast IP networks have been used for one-to-many communications (e.g., talkgroup calls) but not for one-to-one communications, specifically 2-party calls. It would be desirable to extend the benefits of distributed connection and mobility processing, using IP multicast techniques, to support 2-party calls.
  • the present invention is directed to satisfying this need.
  • FIG. 1 is a block diagram of a prior art wireless communication system
  • FIG. 2 is a block diagram of a wireless communication system supporting 2- party calls in accordance with the present invention.
  • FIG. 3 is a message sequence chart illustrating implementation of a 2-party call in accordance with the present invention.
  • a wireless communication system 200 comprising a connectionless packet network 201 coupled to a plurality of sites 203- 208.
  • sites 205, 206 are in communication, via wireless communication resources 251, 252, with respective communication units 213, 215.
  • the communication units 213, 215 are operable, according to principles of the present invention, to execute 2-party calls between themselves or between other communication units (not shown) at other sites.
  • the connectionless packet network 201 is coupled to a public switched telephone network (PSTN) 241 via a telephone gateway 240.
  • PSTN public switched telephone network
  • the communication system may include fewer or greater numbers of sites and/or communication units, and the communication units may be distributed among different sites.
  • the sites 203-208 include respective controllers 220-225 operably linked to the connectionless packet network 201.
  • the controllers 220-225 are physically located at the respective sites in one or more base stations (not shown) or in multicast router(s) (not shown).
  • the controllers 220-225 may be located at a fixed equipment ("infrastructure") site.
  • the controllers 220-225 manage operation of the sites 203-208 in accordance with well known techniques.
  • the controllers 220-225 each comprise a processor (not shown), such as a microprocessor, microcontroller, digital signal processor or combination of such devices) coupled to a memory (not shown), such as volatile or non- volatile digital storage devices or combination of such devices.
  • mappings of talk group identifications to multicast addresses are stored in the memory of the controllers 220-225.
  • the connectionless packet network 201 comprises a wide area network (WAN) 230 coupled to one or more local area networks (LANs) 231-234.
  • WAN wide area network
  • LANs local area networks
  • Suitable equipment for establishing the WAN 230 and LANs 231-234 are Cisco 2600 routers, 3640 routers, 7200 routers, 7500 routers, or 3Com "NetBuilder" series routers.
  • the network 201 may also comprise at least one call server (sometimes known as a "zone controller") 235 coupled to either the WAN 230 or one of the LANs 231-234.
  • the call server is a functional element that may be embodied in one or more physical devices.
  • the call server function can be a distributed process rather than the classic centralized server processing.
  • portions of the call server function can be implemented on separate call server devices 235 implemented within the network 201 or implemented on at least one of the plurality of communications device.
  • the network 201 is connectionless in that any data sent across the network from one end point (e.g., a first site) to another (e.g., a second site) does not require a connection to be established between the two end points before the data can be sent.
  • Examples of connectionless protocols that may be used to implement the present invention are Internet Protocol (IP) over Ethernet, or over Point to Point Protocol (PPP), as known in the art.
  • IP Internet Protocol
  • PPP Point to Point Protocol
  • the connectionless packet network 201 supports a plurality of multicast addresses. In the context of the present invention, two multicast addresses are allocated for each 2-party (unit-to-unit) call.
  • each entity in the call will be a source for one multicast address and a destination for the other, with the roles reversed for each entity.
  • a multicast address regardless of any underlying implementation, provides one-to-many or many-to-many communications capability within the network 201.
  • Multipoint routes pertaining to multicast addresses used in the present invention are maintained by the routers forming the network, rather than by a centralized entity.
  • a suitable technique for providing multicast addressing capabilities is through the use of Internet Protocol (IP) Multicast.
  • IP Multicast is based on the well-known Internet Group Management Protocol (IGMP) which allows a multicast router to track the existence of multicast group members on local networks coupled to that router.
  • IGMP Internet Group Management Protocol
  • multicast routers use the information provided by IGMP in conjunction with a multicast routing protocol to support forwarding of data across a network of routers.
  • sparse mode protocols such as the Core Based Tree (CBT) protocol and the Protocol Independent Multicast - Sparse Mode (PIM- SM) protocol are preferred multicast routing protocols for use in the present invention.
  • dense mode protocols such as the Distance Vector Multicast Routing Protocol (DVMRP), the Multicast Open Shortest Path First (MOSPF) protocol, and the Protocol Independent Multicast - Dense Mode (PBVI-DM) protocol may also be used to implement the present invention.
  • DVMRP Distance Vector Multicast Routing Protocol
  • MOSPF Multicast Open Shortest Path First
  • PBVI-DM Protocol Independent Multicast - Dense Mode
  • a common feature of these multicast routing protocols is that each establishes a "spanning tree" which, for a given multicast group, defines all of the router interfaces which contain group members and the necessary routes between these interfaces to provide the multicast distribution with a minimum amount of data replication.
  • the call server is responsible for managing the 2- party (unit-to-unit) call and providing the information necessary for applicable devices to participate in the call. This includes assigning resources at the necessary devices, assigning two multicast addresses and issuing the appropriate commands to the necessary devices in the system.
  • the call server function may be performed by a centralized device (e.g., zone controller) or distributed among multiple devices.
  • the multicast address used for the call can be fixed or assigned dynamically.
  • the call server dynamically assigns and manages IP multicast addresses for 2-party calls (voice, data, video, etc.) between participating communication devices at the various sites 203-208. That is, multicast addresses for particular devices are not fixed but rather are identified and assigned by the zone controller 235 on a call-by-call basis. As such, a particular multicast address is only temporarily assigned to any one device for the duration of the call and can be reassigned to different devices as needed or desired.
  • static assignment of addresses can also be done. This may be accomplished by the communication units maintaining a list of potential target units' known multicast addresses, or autonomously determining the statically assigned addresses through a known mapping procedure.
  • the scenarios for static assignment could include but not limited to the following: a) the communication unit only knows its own multicast address that it would receive payload on and the multicast addresses are exchanged between the two communication units as part of the call setup; b) the units know the multicast address of the target parties and the multicast addresses are not exchanged during call setup.
  • the call maybe setup without requiring the call server.
  • the call server is responsible for assigning the two multicast addresses that will be used in the unit-to-unit call and is responsible for informing the endpoints in the call as to which multicast address to use. In one embodiment, this is accomplished by the call server informing site controllers of each site participating in the call.
  • the site controllers maintain mapping(s) of multicast addresses to be used for particular 2-party calls. For example, with reference to FIG. 2, controller 222 (site 205) stores a first multicast group address associated with a connection to communication unit 213 and controller 223 (site 206) stores a second multicast address associated with a connection to communication unit 215.
  • the mapping of multicast addresses to particular calls may be assigned dynamically or statically.
  • the multicast addresses are obtained by sites when a communication unit affiliated with the site either initiates a 2-party call or is targeted as a recipient of a 2-party call.
  • a communication unit affiliated with the site either initiates a 2-party call or is targeted as a recipient of a 2-party call.
  • site 205 suppose communication unit 213 (site 205) sends a request for a call designating communication unit 215 (site 206) as a target. This may be accomplished by communication unit 213 specifying an ID associated with communication unit 215 (i.e., "target ID") in the call request.
  • the call server 235 performs a name lookup to determine a multicast address associated with the source and target IDs.
  • the communication unit e.g., communication unit 213 is given a grant to proceed.
  • this grant would also include the multicast addresses to be used for the call.
  • the target is also notified that the call is starting for it.
  • this notification is sourced from a higher level process, such as the call server and contains the multicast IP addresses for both target and source of the call.
  • communication unit 213 (or site 205) may join a first multicast IP address ("MCI") and communication unit 215 (or site 206) may join a second multicast IP address (“MC2").
  • MCI multicast IP address
  • MC2 second multicast IP address
  • the routers of the network Responsive to the Join messages, the routers of the network generates multicast spanning trees that allow the communication units 213, 215 (or cell sites 205, 206 on behalf of the communication units 213, 215) to receive packets addressed to their respective multicast IP addresses.
  • the sourcing communication unit (e.g., communication unit 213) then sends payload traffic addressed to the multicast IP address (e.g., MC2) of the target.
  • the sourcing communication unit may send payload to its associated site (e.g., site 205) on an assigned RF channel which the site or infrastructure could then map to the correct multicast address (e.g., MC2).
  • site 205 e.g., site 205
  • the cell site would forward the user payload to the local router.
  • the local router forwards the traffic into the network where it would be routed to devices (e.g., communication unit 215 and/or site 206) having joined the multicast address (e.g., MC2) of the target.
  • the target desires to talk back to the originator, it uses the multicast address associated with the call originator and/or originating site to send the user payload traffic.
  • the target communication unit e.g., communication unit 215), now becoming a source, sends payload traffic addressed to the multicast IP address (e.g., MCI) of the former source (now the target).
  • the target communication unit 215 may send payload to its associated site (e.g., site 206) on an assigned RF channel which the site or infrastructure could then map to the correct destination identifier (e.g., MCI). Once the payload is addressed for entry into the network, the cell site would forward the user payload to the local router.
  • the local router forwards the traffic into the network where it would be routed to devices (e.g., communication unit 213 and/or site 205) having joined the associated multicast address (e.g., MCI).
  • devices e.g., communication unit 213 and/or site 205 having joined the associated multicast address (e.g., MCI).
  • MCI multicast address
  • the use of two multicast addresses supports a full duplex connection between endpoints participating in the call.
  • Each device will use one of the multicast addresses to source payload traffic on and the other address to receive payload on.
  • the zone controller indicates which address should be used for sourcing or receiving payload in the grant message sent to participating devices.
  • the call can be used to exchange payload traffic including but not limited to audio, data, images, text, location, etc.
  • one or both of the communication units 213, 215 may change affiliated cell sites for a variety of reasons, including but not limited to physical movement and site failures.
  • a first communication unit e.g., communication unit 213 affiliates with a new site (e.g., site 207)
  • the first communication unit, or the cell site on behalf of the first communication unit then joins the assigned multicast IP address, in one embodiment by sending IGMP Join messages to their attached routers.
  • the routers of the network Responsive to the Join messages, the routers of the network generate multicast spanning tree changes that allow the first communication unit (or cell site on behalf of the first communication unit) to receive packets addressed to the assigned multicast IP address.
  • HLR/VLR centralized mobility server
  • the cell site can determine the multicast IP address.
  • the multicast IP address is directly communicated from the communication unit (e.g., communication unit 213) to the cell site.
  • the communication unit communicates a call ID, connection ID, unit ID or other identifier to the cell site; the site's controller (e.g., controller 224) queries a database (such as implemented by a call server) to determine the multicast IP address.
  • the communication unit communicates the identity or address of the previous cell site (e.g., site 205) to the new cell site (e.g., site 207); the new site's controller 224 queries the old site's controller 222 to determine the multicast IP address.
  • Pruning of the spanning tree can be accomplished in a number of ways.
  • the site could periodically page for the individual communication unit being present at the site. Failure to confirm its presence will result in the site sending an IP multicast "leave" message to remove the site from the spanning tree.
  • a background site function may be used to detect mobile terminals attaching to a new site and then sending a "detach" message to the site from which that terminal has come. The "detach" message can be used to remove that terminal at the old site and a leave message can be sent to the network.
  • a third embodiment might have each site exchanging lists of attached communication units along with a timestamp that indicates the last time the site successfully interacted with the communication unit. This information may be exchanged much like reachability information in a distributed routing protocol.
  • a site detects that another site has a significantly more recent interaction with a communication unit, it assumes that the communication unit has left its site and it sends a leave message to its attached router.
  • FIG. 3 shows a call setup message sequence according to the invention. The steps of the procedure are described as follows:
  • RF Site 1 receives a call request from an affiliated communication unit on the RF interface and forwards the call request U2U_Call_Request 302 to the call server.
  • the call server validates the communication unit for system access and other necessary checks.
  • the call server issues a U2U_Answer_Reqest 304 to target site Site 2 and the originating site Site 1 in attempt to determine if the target communication unit is available to participate in the call and to notify the originating communication unit of the call status.
  • the target site sends a U2U_Answer_Response 306 to the call server with a disposition of wait or proceed. 5.
  • the call server acknowledges the target site Site2 by sending
  • U2U_Ring_ACK 308 and sends a U2U_Ring_Update 310 to Sitel.
  • the call server After receiving the U2U_Answer_Response 312 from the Site2 with disposition of Proceed, the call server determines the multicast addresses associated with the call. These multicast addresses are either dynamically assigned or statically assigned and retrieved from the database.
  • Controller issues the U2U_Call_Grant 314 to the originating and target sites.
  • the grant message includes the multicast addresses to be used for the call.
  • Communication units or sites on behalf of the units j oin the multicast address, with the routers associated with the respective sites by sending IGMP Join messages 316 to receive payload from the other party.
  • the present invention decentralizes the setup and maintenance of a 2-party call and has the following desirable characteristics.
  • No complex hierarchy of location registers (HLR/VLR) is required.
  • the network can constantly reconfigure itself to route packets to the destination communication unit(s).
  • c. No network connection setup activities required at the start of a call. Once a communication unit or a cell site on behalf of a communication unit has joined the multicast IP address, the network is ready to route traffic to the communication unit or cell site at all times.

Abstract

Upon a first communication unit (213) initiating a call request for a 2-party call with a second communication unit (215), a call server (235) identifies respective multicast IP addresses (MC1, MC2) associated with the source and target. If the first communication unit (213), or associated site (205) desires to send payload to the second communication unit (215), it addresses the payload to the multicast IP address (MC2) of the second communication unit, and the second communication unit (215), or associated site (206) joins the multicast address (MC2) to receive the payload. Conversely, if the second communication unit (215), or associated site (206) desires to send payload to the first communication unit (213), it addresses the payload to the multicast IP address (MC1) of the first communication unit, and the first communication unit (213), or associated site (205) joins the multicast address (MC1) to receive the payload.

Description

USE OF IP-MULTICAST TECHNOLOGY FOR 2-PARTY CALLS IN MOBILE COMMUNICATION NETWORKS
CROSS-REFERENCE TO RELATED APPLICATIONS This invention is related to U.S. Patent Application No. 09/283,121, filed
March 31, 1999, titled "Wireless Communication System Incorporating Multicast Addressing and Method for Use," which application issued October 31, 2000 as U.S. Patent No. 6,141,347.
FIELD OF THE INVENTION
This invention relates generally to wireless communication systems and, more particularly, to IP multicast communication systems.
BACKGROUND OF THE INVENTION Today' s wireless communication systems provide a broad range of services to both individual communication units and groups of communication units while they move about. These services include cellular telephony, group dispatch, and packet data, to name just a few. A typical example of such a system 100 is illustrated in FIG. 1. The configuration shown in FIG. 1 is typical in wireless communications systems such as Global System for Mobile Communications (GSM), Advanced Mobile Phone Service (AMPS), Terrestrial Trunked Radio (TETRA), "IDEN", and "SMARTZONE" systems. As shown, a central switch 101 provides connections between cell sites 104-107.
A plurality of communication units 110-115 (e.g., mobile or portable radios, cellular telephones, personal digital assistants (PDAs)) wirelessly communicate with the sites 104-107 and each other, and are often logically divided into various subgroups or talk groups. In such a system, the call processing management and switching functionality are generally contained within the same physical unit, i.e., the central switch 101. The sites 104-107 are connected to the central switch 101 through dedicated or on-demand links and intermediate processors 102-103 in what is often called a "star" configuration. Some very large systems use a hierarchy of such "stars" where intervening concentrators group the links from multiple cell sites and do some lower level processing on them before passing them up to the central switch. Next-generation wireless systems propose to employ multicast addressing protocols, such as multicast Internet Protocol (IP) for providing group or dispatch call services. Examples of IP Multicast communication systems include the referenced U.S. Patent Application Ser. No. 09/283,121, now issued as U.S. Patent No. 6,141,347; and U.S. Patent Application Serial No. 09/464,269, titled "Methods for Implementing a Talkgroup Call in a Multicast IP Network," each of which is assigned to Motorola, Inc. and incorporated herein by reference in its entirety.
Generally, IP multicasting protocols are considered to be more efficient and less costly than traditional circuit-switched networks. The multicast IP network defines a distributed, rather than centralized, connection and mobility processing environment where there is no centralized location register (VLR/HLR). Rather, mobility information is inherent to the packet network as communication units register or de-register individual or group affiliations with cells, and the cells join or leave multicast IP addresses to participate in traffic for the communication units. The benefits of a distributed connection and mobility processing environment include fully localized resource management, fully distributed mobility management and easy network scalability.
Heretofore, distributed connection and mobility processing networks such as multicast IP networks have been used for one-to-many communications (e.g., talkgroup calls) but not for one-to-one communications, specifically 2-party calls. It would be desirable to extend the benefits of distributed connection and mobility processing, using IP multicast techniques, to support 2-party calls. The present invention is directed to satisfying this need.
BRIEF DESCRIPTION OF THE DRAWINGS
The foregoing and other advantages of the invention will become apparent upon reading the following detailed description and upon reference to the drawings in which:
FIG. 1 is a block diagram of a prior art wireless communication system;
FIG. 2 is a block diagram of a wireless communication system supporting 2- party calls in accordance with the present invention; and
FIG. 3 is a message sequence chart illustrating implementation of a 2-party call in accordance with the present invention.
DESCRIPTION OF A PREFERRED EMBODIMENT
Turning now to FIG. 2, there is shown a wireless communication system 200 comprising a connectionless packet network 201 coupled to a plurality of sites 203- 208. As shown, sites 205, 206 are in communication, via wireless communication resources 251, 252, with respective communication units 213, 215. The communication units 213, 215 are operable, according to principles of the present invention, to execute 2-party calls between themselves or between other communication units (not shown) at other sites. Additionally, the connectionless packet network 201 is coupled to a public switched telephone network (PSTN) 241 via a telephone gateway 240. As will be appreciated, the communication system may include fewer or greater numbers of sites and/or communication units, and the communication units may be distributed among different sites.
In one embodiment, the sites 203-208 include respective controllers 220-225 operably linked to the connectionless packet network 201. Typically, the controllers 220-225 are physically located at the respective sites in one or more base stations (not shown) or in multicast router(s) (not shown). Alternatively, the controllers 220-225 may be located at a fixed equipment ("infrastructure") site. The controllers 220-225 manage operation of the sites 203-208 in accordance with well known techniques. The controllers 220-225 each comprise a processor (not shown), such as a microprocessor, microcontroller, digital signal processor or combination of such devices) coupled to a memory (not shown), such as volatile or non- volatile digital storage devices or combination of such devices. In one embodiment of the present invention, mappings of talk group identifications to multicast addresses are stored in the memory of the controllers 220-225.
The connectionless packet network 201 comprises a wide area network (WAN) 230 coupled to one or more local area networks (LANs) 231-234. Suitable equipment for establishing the WAN 230 and LANs 231-234 are Cisco 2600 routers, 3640 routers, 7200 routers, 7500 routers, or 3Com "NetBuilder" series routers. The network 201 may also comprise at least one call server (sometimes known as a "zone controller") 235 coupled to either the WAN 230 or one of the LANs 231-234. As will be appreciated the call server is a functional element that may be embodied in one or more physical devices. Thus, the call server function can be a distributed process rather than the classic centralized server processing. For example, portions of the call server function can be implemented on separate call server devices 235 implemented within the network 201 or implemented on at least one of the plurality of communications device. The network 201 is connectionless in that any data sent across the network from one end point (e.g., a first site) to another (e.g., a second site) does not require a connection to be established between the two end points before the data can be sent. Examples of connectionless protocols that may be used to implement the present invention are Internet Protocol (IP) over Ethernet, or over Point to Point Protocol (PPP), as known in the art. The connectionless packet network 201 supports a plurality of multicast addresses. In the context of the present invention, two multicast addresses are allocated for each 2-party (unit-to-unit) call. As will be described in greater detail hereinafter, each entity in the call will be a source for one multicast address and a destination for the other, with the roles reversed for each entity. A multicast address, regardless of any underlying implementation, provides one-to-many or many-to-many communications capability within the network 201. Multipoint routes pertaining to multicast addresses used in the present invention are maintained by the routers forming the network, rather than by a centralized entity. A suitable technique for providing multicast addressing capabilities is through the use of Internet Protocol (IP) Multicast. IP Multicast is based on the well-known Internet Group Management Protocol (IGMP) which allows a multicast router to track the existence of multicast group members on local networks coupled to that router. Additionally, multicast routers use the information provided by IGMP in conjunction with a multicast routing protocol to support forwarding of data across a network of routers. Given the nature of wireless communication systems, sparse mode protocols such as the Core Based Tree (CBT) protocol and the Protocol Independent Multicast - Sparse Mode (PIM- SM) protocol are preferred multicast routing protocols for use in the present invention. However, it is anticipated that dense mode protocols such as the Distance Vector Multicast Routing Protocol (DVMRP), the Multicast Open Shortest Path First (MOSPF) protocol, and the Protocol Independent Multicast - Dense Mode (PBVI-DM) protocol may also be used to implement the present invention. A common feature of these multicast routing protocols is that each establishes a "spanning tree" which, for a given multicast group, defines all of the router interfaces which contain group members and the necessary routes between these interfaces to provide the multicast distribution with a minimum amount of data replication.
In the preferred embodiment, the call server is responsible for managing the 2- party (unit-to-unit) call and providing the information necessary for applicable devices to participate in the call. This includes assigning resources at the necessary devices, assigning two multicast addresses and issuing the appropriate commands to the necessary devices in the system. As has been described, the call server function may be performed by a centralized device (e.g., zone controller) or distributed among multiple devices. The multicast address used for the call can be fixed or assigned dynamically.
In one embodiment, the call server dynamically assigns and manages IP multicast addresses for 2-party calls (voice, data, video, etc.) between participating communication devices at the various sites 203-208. That is, multicast addresses for particular devices are not fixed but rather are identified and assigned by the zone controller 235 on a call-by-call basis. As such, a particular multicast address is only temporarily assigned to any one device for the duration of the call and can be reassigned to different devices as needed or desired.
Alternatively, static assignment of addresses can also be done. This may be accomplished by the communication units maintaining a list of potential target units' known multicast addresses, or autonomously determining the statically assigned addresses through a known mapping procedure. The scenarios for static assignment could include but not limited to the following: a) the communication unit only knows its own multicast address that it would receive payload on and the multicast addresses are exchanged between the two communication units as part of the call setup; b) the units know the multicast address of the target parties and the multicast addresses are not exchanged during call setup. In the static multicast assignment, the call maybe setup without requiring the call server.
In one embodiment, the call server is responsible for assigning the two multicast addresses that will be used in the unit-to-unit call and is responsible for informing the endpoints in the call as to which multicast address to use. In one embodiment, this is accomplished by the call server informing site controllers of each site participating in the call. The site controllers maintain mapping(s) of multicast addresses to be used for particular 2-party calls. For example, with reference to FIG. 2, controller 222 (site 205) stores a first multicast group address associated with a connection to communication unit 213 and controller 223 (site 206) stores a second multicast address associated with a connection to communication unit 215. As will be appreciated, the mapping of multicast addresses to particular calls may be assigned dynamically or statically.
In one embodiment, the multicast addresses are obtained by sites when a communication unit affiliated with the site either initiates a 2-party call or is targeted as a recipient of a 2-party call. For example, referring to FIG. 2, suppose communication unit 213 (site 205) sends a request for a call designating communication unit 215 (site 206) as a target. This may be accomplished by communication unit 213 specifying an ID associated with communication unit 215 (i.e., "target ID") in the call request. The call server 235 performs a name lookup to determine a multicast address associated with the source and target IDs. After appropriate authorization and provisioning checks, the communication unit (e.g., communication unit 213) is given a grant to proceed. In the preferred embodiment, this grant would also include the multicast addresses to be used for the call. The target is also notified that the call is starting for it. In the preferred embodiment, this notification is sourced from a higher level process, such as the call server and contains the multicast IP addresses for both target and source of the call.
The communication units, or the cell sites on behalf of the communication units, then join their assigned multicast IP addresses, in one embodiment by sending IGMP Join messages to their attached routers. For example, communication unit 213 (or site 205) may join a first multicast IP address ("MCI") and communication unit 215 (or site 206) may join a second multicast IP address ("MC2"). Responsive to the Join messages, the routers of the network generates multicast spanning trees that allow the communication units 213, 215 (or cell sites 205, 206 on behalf of the communication units 213, 215) to receive packets addressed to their respective multicast IP addresses.
The sourcing communication unit (e.g., communication unit 213) then sends payload traffic addressed to the multicast IP address (e.g., MC2) of the target. Alternatively, the sourcing communication unit may send payload to its associated site (e.g., site 205) on an assigned RF channel which the site or infrastructure could then map to the correct multicast address (e.g., MC2). Once the payload is addressed for entry into the network, the cell site would forward the user payload to the local router. The local router, in turn, forwards the traffic into the network where it would be routed to devices (e.g., communication unit 215 and/or site 206) having joined the multicast address (e.g., MC2) of the target.
If the target desires to talk back to the originator, it uses the multicast address associated with the call originator and/or originating site to send the user payload traffic. Thus, for example, the target communication unit (e.g., communication unit 215), now becoming a source, sends payload traffic addressed to the multicast IP address (e.g., MCI) of the former source (now the target). Alternatively, communication unit 215 may send payload to its associated site (e.g., site 206) on an assigned RF channel which the site or infrastructure could then map to the correct destination identifier (e.g., MCI). Once the payload is addressed for entry into the network, the cell site would forward the user payload to the local router. The local router, in turn, forwards the traffic into the network where it would be routed to devices (e.g., communication unit 213 and/or site 205) having joined the associated multicast address (e.g., MCI). In this manner, the use of two multicast addresses supports a full duplex connection between endpoints participating in the call. Each device will use one of the multicast addresses to source payload traffic on and the other address to receive payload on. The zone controller indicates which address should be used for sourcing or receiving payload in the grant message sent to participating devices. As will be appreciated, once the connection between endpoints is established, the call can be used to exchange payload traffic including but not limited to audio, data, images, text, location, etc.
Once a two-party call has been established, one or both of the communication units 213, 215 may change affiliated cell sites for a variety of reasons, including but not limited to physical movement and site failures. When a first communication unit (e.g., communication unit 213) affiliates with a new site (e.g., site 207), the first communication unit, or the cell site on behalf of the first communication unit, then joins the assigned multicast IP address, in one embodiment by sending IGMP Join messages to their attached routers. Responsive to the Join messages, the routers of the network generate multicast spanning tree changes that allow the first communication unit (or cell site on behalf of the first communication unit) to receive packets addressed to the assigned multicast IP address. In this circumstance, communication is re-established without any actions on the part of a centralized mobility server (HLR/VLR) or on part of the second communication unit. One skilled in the art will recognize that the described mechanism also works for simultaneous or concurrent re-affiliation of a first communication unit and a second communication unit.
When the new cell site joins an assigned multicast IP address on behalf of a communication unit, the cell site can determine the multicast IP address. In one embodiment, the multicast IP address is directly communicated from the communication unit (e.g., communication unit 213) to the cell site. In another embodiment, the communication unit communicates a call ID, connection ID, unit ID or other identifier to the cell site; the site's controller (e.g., controller 224) queries a database (such as implemented by a call server) to determine the multicast IP address. In another embodiment, the communication unit communicates the identity or address of the previous cell site (e.g., site 205) to the new cell site (e.g., site 207); the new site's controller 224 queries the old site's controller 222 to determine the multicast IP address.
Pruning of the spanning tree (e.g., upon de-registration of communication units) can be accomplished in a number of ways. In one embodiment, the site could periodically page for the individual communication unit being present at the site. Failure to confirm its presence will result in the site sending an IP multicast "leave" message to remove the site from the spanning tree. In another embodiment, a background site function may be used to detect mobile terminals attaching to a new site and then sending a "detach" message to the site from which that terminal has come. The "detach" message can be used to remove that terminal at the old site and a leave message can be sent to the network. A third embodiment might have each site exchanging lists of attached communication units along with a timestamp that indicates the last time the site successfully interacted with the communication unit. This information may be exchanged much like reachability information in a distributed routing protocol. When a site detects that another site has a significantly more recent interaction with a communication unit, it assumes that the communication unit has left its site and it sends a leave message to its attached router. FIG. 3 shows a call setup message sequence according to the invention. The steps of the procedure are described as follows:
Call setup procedure
1. RF Site 1 receives a call request from an affiliated communication unit on the RF interface and forwards the call request U2U_Call_Request 302 to the call server.
2. The call server validates the communication unit for system access and other necessary checks.
3. The call server issues a U2U_Answer_Reqest 304 to target site Site 2 and the originating site Site 1 in attempt to determine if the target communication unit is available to participate in the call and to notify the originating communication unit of the call status.
4. The target site sends a U2U_Answer_Response 306 to the call server with a disposition of wait or proceed. 5. The call server acknowledges the target site Site2 by sending
U2U_Ring_ACK 308 and sends a U2U_Ring_Update 310 to Sitel.
6. After receiving the U2U_Answer_Response 312 from the Site2 with disposition of Proceed, the call server determines the multicast addresses associated with the call. These multicast addresses are either dynamically assigned or statically assigned and retrieved from the database.
7. Once the call server has determined the resources necessary for the call are available Controller issues the U2U_Call_Grant 314 to the originating and target sites. The grant message includes the multicast addresses to be used for the call. 8. Communication units or sites on behalf of the units j oin the multicast address, with the routers associated with the respective sites by sending IGMP Join messages 316 to receive payload from the other party. The present invention decentralizes the setup and maintenance of a 2-party call and has the following desirable characteristics. a. Fully Localized Resource Management. RF Resources and link resources are managed in a distributed fashion. Resource unavailability or congestion is determined locally and this information is made known to the higher layer processes, either by application layer timeouts, or by direct messaging from the connection processing in each client. The higher layer application (for example, the 2-party call service processing) is then able to take appropriate action, such as to busy the call. b. No complex hierarchy of location registers (HLR/VLR) is required.
Through the use of Join and Leave messages, the network can constantly reconfigure itself to route packets to the destination communication unit(s). c. No network connection setup activities required at the start of a call. Once a communication unit or a cell site on behalf of a communication unit has joined the multicast IP address, the network is ready to route traffic to the communication unit or cell site at all times. d. Highly scalable network design. Unlike a centralized connection management approach which must be reconfigured as connection elements are added or deleted, the method allows the network to update itself constantly, determine new routes, and delete old ones. No manual link configuration is required. Configurations are also highly localized with each cell site having to know only about its local links.
The foregoing description of a preferred embodiment of the invention has been presented for purposes of illustration and description, and is not intended to be exhaustive or to limit the invention to the precise form disclosed. The description was selected to best explain the principles of the invention and practical application of these principles to enable others skilled in the art to best utilize the invention in various embodiments and various modifications as are suited to the particular use contemplated. It is intended that the scope of the invention not be limited by the specification, but be defined by the claims set forth below.

Claims

WHAT IS CLAIMED IS:
1. In a communication system including a plurality of sites linked together by a packet network, a method comprising: determining first and second multicast IP addresses to be used for a two-party call; and issuing commands to the packet network requesting reconfiguration of the packet network to enable a first site of the communication system to receive payload for the call via the first multicast IP address and a second site of the communication system to receive payload for the call via the second multicast IP address.
2. The method of claim 1, wherein the step of issuing commands comprises sending, from the first and second site, respective IGMP Join messages identifying the first and second multicast IP addresses to one or more network devices of the packet network.
3. The method of claim 1, comprising: receiving, by the first site, a message identifying a target device associated with the second site; sending the message from the first site to the second multicast IP address; receiving, by the second site, at least a portion of the message via the second multicast IP address; and sending the at least a portion of the message from the second site to the target device.
4. The method of claim 3, further comprising: receiving, by the second site, a message identifying a target device associated with the first site; sending the message from the second site to the first multicast IP address; receiving, by the first site, at least a portion of the message via the first multicast IP address; and sending the at least a portion of the message from the first site to the target device.
5. The method of claim 3, wherein the step of receiving, by the first site, a message identifying a target device comprises receiving a message from a source device associated with the first site.
6. The method of claim 5, wherein one of the source device and target device moves to a different site during the call, defining a moved communication unit and an old site and a new site for the moved communication unit, the method further comprising: receiving, by the new site, a message identifying at least one multicast IP address associated with the call; and issuing commands to the packet network requesting reconfiguration of the packet network to enable the new site to receive payload for the call.
7. The method of claim 6, wherein the step of receiving, by the new site, a message identifying at least one multicast IP address comprises receiving, from the moved communication unit, a message identifying the first and second multicast IP address associated with the call.
8. The method of claim 6, wherein the step of receiving, by the new site, a message comprises: requesting, by the new site from a call server, the first and second multicast IP addresses associated with the call; and receiving the message from the call server identifying the first and second multicast IP addresses.
9. In a communication system including at least a first and second communication device participating in a two-party call, a method comprising: sending a first payload from the first communication device to one or more network devices and addressed to a second multicast group address; and joining, by the second communication device, the second multicast group address to receive the first payload from the one or more network devices.
10. The method of claim 9, further comprising: sending a second payload from the second communication device to one or more network devices and addressed to a first multicast group address; and joining, by the first communication device, the first multicast group address to receive the second payload from the one or more network devices.
PCT/US2002/023438 2001-08-30 2002-07-23 Use of ip-multicast technology for 2-party calls in mobile communication networks WO2003021891A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
AT02750268T ATE516681T1 (en) 2001-08-30 2002-07-23 USE OF IP MULTICAST TECHNOLOGY FOR SUBSCRIBER CONNECTIONS IN MOBILE COMMUNICATION NETWORKS
IL15531002A IL155310A0 (en) 2001-08-30 2002-07-23 Use of ip-multicast technology for 2-party calls in mobile communication networks
EP02750268A EP1423943B1 (en) 2001-08-30 2002-07-23 Use of ip-multicast technology for 2-party calls in mobile communication networks

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US31693901P 2001-08-30 2001-08-30
US60/316,939 2001-08-30
US09/975,353 2001-10-11
US09/975,353 US7103011B2 (en) 2001-08-30 2001-10-11 Use of IP-multicast technology for 2-party calls in mobile communication networks

Publications (1)

Publication Number Publication Date
WO2003021891A1 true WO2003021891A1 (en) 2003-03-13

Family

ID=26980676

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2002/023438 WO2003021891A1 (en) 2001-08-30 2002-07-23 Use of ip-multicast technology for 2-party calls in mobile communication networks

Country Status (4)

Country Link
US (1) US7103011B2 (en)
EP (1) EP1423943B1 (en)
AT (1) ATE516681T1 (en)
WO (1) WO2003021891A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100490442C (en) * 2003-11-07 2009-05-20 华为技术有限公司 Optimization method for protocol process on RP in PIM-SM
CN100583686C (en) * 2006-07-20 2010-01-20 北京航空航天大学 Method for constructing multiple-core sharing multicast tree

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7133371B2 (en) * 2000-12-01 2006-11-07 Motorola, Inc. Methods for achieving reliable joins in a multicast IP network
US8429296B2 (en) * 2001-03-06 2013-04-23 Pluris, Inc. Method and apparatus for distributing routing instructions over multiple interfaces of a data router
US20030135594A1 (en) * 2001-12-06 2003-07-17 Lin Xu System and method for efficient distribution of multicastable services
US6792281B2 (en) * 2002-06-28 2004-09-14 Motorola, Inc. Method and system for patching dispatch calling parties together
US7808932B2 (en) * 2003-01-16 2010-10-05 Sony United Kingdom Limited Virtual connection for packetised data transfer in a video and audio network
GB2416279B (en) * 2004-07-16 2009-02-11 Motorola Inc A cellular communication system, a communication unit and a method of call initiation therefor
US8605649B2 (en) * 2006-12-21 2013-12-10 Alcatel Lucent Method for providing reliable communication session establishment in a communication infrastructure
US20080240096A1 (en) * 2007-03-29 2008-10-02 Twisted Pair Solutions, Inc. Method, apparatus, system, and article of manufacture for providing distributed convergence nodes in a communication network environment
EP2294548A4 (en) 2008-07-01 2013-06-26 Twisted Pair Solutions Inc Method, apparatus, system, and article of manufacture for reliable low-bandwidth information delivery across mixed-mode unicast and multicast networks
CN101958840B (en) * 2010-10-18 2014-09-10 中兴通讯股份有限公司 Method and device for creating message table entry as well as method and device for forwarding multicast data stream
DE102011076998A1 (en) * 2011-06-06 2012-12-06 S. Siedle & Söhne Telefon- und Telegrafenwerke OHG Communication method for a telecommunication system, in particular for a home communication system, and home communication system

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5442633A (en) * 1992-07-08 1995-08-15 International Business Machines Corporation Shortcut network layer routing for mobile hosts
US6141347A (en) * 1998-08-26 2000-10-31 Motorola, Inc. Wireless communication system incorporating multicast addressing and method for use
US20010043607A1 (en) * 1997-12-09 2001-11-22 Michael V. Socaciu Signaling system and method to connect idle internet end stations with application in internet telephony
US20020039357A1 (en) * 2000-09-29 2002-04-04 Jaakko Lipasti Addressing and routing in mobile ad hoc networks

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5608726A (en) * 1995-04-25 1997-03-04 Cabletron Systems, Inc. Network bridge with multicast forwarding table
US6370142B1 (en) * 1995-07-12 2002-04-09 Nortel Networks Limited Method and apparatus for performing per-port IP multicast pruning
US5822523A (en) * 1996-02-01 1998-10-13 Mpath Interactive, Inc. Server-group messaging system for interactive applications
US5778187A (en) * 1996-05-09 1998-07-07 Netcast Communications Corp. Multicasting method and apparatus
US6101180A (en) * 1996-11-12 2000-08-08 Starguide Digital Networks, Inc. High bandwidth broadcast system having localized multicast access to broadcast content
US6496704B2 (en) * 1997-01-07 2002-12-17 Verizon Laboratories Inc. Systems and methods for internetworking data networks having mobility management functions
US6483832B1 (en) 1997-04-17 2002-11-19 At&T Corp. IP multicast over routed ATM network using lane
US6011782A (en) * 1997-05-08 2000-01-04 At&T Corp. Method for managing multicast addresses for transmitting and receiving multimedia conferencing information on an internet protocol (IP) network
US6215766B1 (en) * 1998-01-30 2001-04-10 Lucent Technologies Inc. Hierarchical rate control of receivers in a communication system transmitting layered video multicast data with retransmission (LVMR)
US6147986A (en) * 1998-03-06 2000-11-14 Lucent Technologies Inc. Address updating of wireless mobile terminal hosts affiliated with a wired network
US6046979A (en) * 1998-05-04 2000-04-04 Cabletron Systems, Inc. Method and apparatus for controlling the flow of variable-length packets through a multiport switch
US6298058B1 (en) 1999-12-17 2001-10-02 Motorola, Inc. Methods for implementing a talkgroup call with competing sources in a multicast IP network
US6647020B1 (en) 1999-12-17 2003-11-11 Motorola, Inc. Methods for implementing a talkgroup call in a multicast IP network
US7650424B2 (en) * 2000-04-04 2010-01-19 Alcatel-Lucent Usa Inc. Supporting mobile hosts on an internet protocol network
JP3833450B2 (en) * 2000-07-27 2006-10-11 三菱電機株式会社 Communication control method and router
US6996414B2 (en) * 2001-04-30 2006-02-07 Motorola, Inc. System and method of group calling in mobile communications
US7339903B2 (en) * 2001-06-14 2008-03-04 Qualcomm Incorporated Enabling foreign network multicasting for a roaming mobile node, in a foreign network, using a persistent address
US6781999B2 (en) * 2001-07-23 2004-08-24 Airvana, Inc. Broadcasting and multicasting in wireless communication

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5442633A (en) * 1992-07-08 1995-08-15 International Business Machines Corporation Shortcut network layer routing for mobile hosts
US20010043607A1 (en) * 1997-12-09 2001-11-22 Michael V. Socaciu Signaling system and method to connect idle internet end stations with application in internet telephony
US6141347A (en) * 1998-08-26 2000-10-31 Motorola, Inc. Wireless communication system incorporating multicast addressing and method for use
US20020039357A1 (en) * 2000-09-29 2002-04-04 Jaakko Lipasti Addressing and routing in mobile ad hoc networks

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100490442C (en) * 2003-11-07 2009-05-20 华为技术有限公司 Optimization method for protocol process on RP in PIM-SM
CN100583686C (en) * 2006-07-20 2010-01-20 北京航空航天大学 Method for constructing multiple-core sharing multicast tree

Also Published As

Publication number Publication date
US20030043804A1 (en) 2003-03-06
ATE516681T1 (en) 2011-07-15
EP1423943B1 (en) 2011-07-13
EP1423943A1 (en) 2004-06-02
US7103011B2 (en) 2006-09-05
EP1423943A4 (en) 2005-03-16

Similar Documents

Publication Publication Date Title
US6697349B2 (en) System and methods for distributed connection and mobility processing in a multicast IP network incorporating multi-cell location areas
CN112087722B (en) Communication system, communication method and device thereof
EP1421819B1 (en) Multicast group management in telecommunication networks
EP1108302B1 (en) Wireless communication system incorporating multicast addressing and method for use
KR100951026B1 (en) System and method for distributing voip data packets in group communications among wireless telecommunication devices
CN100592693C (en) Multicast IP zones for fast spanning tree convergence in wide-area packet network systems
JP4050702B2 (en) Method and system for multicasting message selecting mobile recipients
US6785254B2 (en) Wireless communication system incorporating multicast addressing and method for use
US20050233760A1 (en) Multimedia broadcast/multicast service (mbms) support in utran
JP2005506728A (en) System and method for group calling in mobile communications
EP1423943B1 (en) Use of ip-multicast technology for 2-party calls in mobile communication networks
JP4712095B2 (en) Communication method and wireless communication system
US7120147B2 (en) Reservation proxy function supporting filtering of multicast traffic in packet-based communication systems
US7009970B2 (en) Methods for managing bandwidth in a packet-based communication system incorporating a reservation proxy function
Namee et al. Designing a Protocol to Support Multicast Mobility in IPv6 Network

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SD SE SG SI SK SL TJ TM TN TR TT TZ UA UG UZ VN YU ZA ZM ZW

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BY BZ CA CH CN CO CR CU CZ DE DM DZ EC EE ES FI GB GD GE GH HR HU ID IL IN IS JP KE KG KP KR LC LK LR LS LT LU LV MA MD MG MN MW MX MZ NO NZ OM PH PL PT RU SD SE SG SI SK SL TJ TM TN TR TZ UA UG UZ VN YU ZA ZM

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR IE IT LU MC NL PT SE SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ UG ZM ZW AM AZ BY KG KZ RU TJ TM AT BE BG CH CY CZ DK EE ES FI FR GB GR IE IT LU MC PT SE SK TR BF BJ CF CG CI GA GN GQ GW ML MR NE SN TD TG

WWE Wipo information: entry into national phase

Ref document number: 2002750268

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 155310

Country of ref document: IL

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWP Wipo information: published in national office

Ref document number: 2002750268

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP