US7260070B1

US7260070B1 - System and method for providing information to a mobile unit

Info

Publication number: US7260070B1
Application number: US10/133,921
Authority: US
Inventors: Malcolm M. Smith
Original assignee: Cisco Technology Inc
Current assignee: Cisco Technology Inc
Priority date: 2002-04-26
Filing date: 2002-04-26
Publication date: 2007-08-21

Abstract

A gateway provides a multicast packet of information to a plurality of transceiver stations. The plurality of transceiver stations belong to a soft handoff group associated with a mobile unit. The multicast packet of information includes a common traffic section and a plurality of unique control sections. A particular transceiver station receives the multicast packet of information from the gateway and identifies its associated unique control section. The particular transceiver station then sends the common traffic section to the mobile unit according to its associated unique control section.

Description

TECHNICAL FIELD OF THE INVENTION

The present invention relates in general to wireless telecommunications and more particularly to a system and method for providing information to a mobile unit.

BACKGROUND OF THE INVENTION

Conventional approaches to providing information in a wireless telecommunications environment to a mobile unit include distributing bearer traffic from a gateway, or base station controller, to multiple radio access points, or base transceiver stations that are associated with the mobile unit. Though communication with a mobile unit typically occurs with one radio access point, other radio access points must be ready to take over communications with the mobile unit in case the mobile unit moves to a different area or as the result of traffic congestion at the radio access point serving the mobile unit. In providing the necessary information to multiple radio access points, a problem arises from the close relationship between control and bearer information. Bearer traffic destined for the mobile unit is typically combined with control information for the radio access point. Each radio access point receives the bearer traffic and the control information on a separate link from the gateway different from the other radio access points. However, this approach does not leverage the underlying packet network that is capable of multicast operation.

SUMMARY OF THE INVENTION

From the foregoing, it may be appreciated by those skilled in the art that a need has arisen to the multicast capabilities of an underlying packet network in a wireless telecommunications system. In accordance with the present invention, a system and method for providing information to a mobile unit are provided that substantially eliminate or greatly reduce disadvantages and problems associated with conventional wireless telecommunications systems.

According to an embodiment of the present invention, there is provided a system for providing information to a mobile unit that includes a gateway operable to generate a packet of information. The packet of information includes a common traffic section and a plurality of unique control sections. A transceiver station receives the packet of information from the gateway and identifies one of the plurality of unique sections as being associated therewith. The transceiver station sends the common traffic section to the mobile unit according to its identified one of the plurality of unique control sections.

The present invention provides various technical advantages over conventional wireless telecommunications systems. For example, one technical advantage is to eliminate separate links from a gateway to each of a plurality of transceiver stations. Another technical advantage is to provide multiple unique control sections wherein each control section is readily identifiable by an associated transceiver station. Yet another example is to allow existing networks to be easily upgraded to support packet based selection distribution and leverage packet multi-casting without changing the functional architecture of the network or its external interfaces. Still another technical advantage is to apply this technique to inter-network soft handoff in order to facilitate scaling and roaming. Other examples may be readily ascertainable by those skilled in the art from the following figures, description, and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention and the advantages thereof, reference is now made to the following description taken in conjunction with the accompanying drawings, wherein like reference numerals represent like parts, in which:

FIG. 1 illustrates a communications system having a packet-switched network supporting wireless communications with mobile units;

FIG. 2 is a block diagram illustrating a gateway in the communications system that supports multicasting of packets for delivery to a mobile unit;

FIG. 3 is a block diagram illustrating a base transceiver station that receives multicast packets containing information for communication to a mobile unit;

FIG. 4 is a flowchart illustrating a method for generating multicast packets containing information for communication to a mobile unit;

FIG. 5 is a flowchart illustrating a method for receiving multicast packets and communicating information from the packets to a mobile unit;

FIG. 6 is a flowchart illustrating the operation of a base transceiver station implementing High Data Rate (HDR) communications that receives and processes multicast packets associated with a mobile unit;

FIG. 7 is a flowchart illustrating a method for managing a multicast group containing base transceiver stations communicating with a mobile unit;

FIG. 8 is a simplified block diagram showing packet transfer in the communications system;

FIG. 9 is an example of a packet format in the communications system.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 illustrates a communications system, indicated generally at 10, that includes mobile units 12 coupled via wireless links to base transceiver stations 14. System 10 also includes a packet network 16 that couples to stations 14, a gateway 18, and a roam manager 20. In general, mobile unit 12 supports communications sessions by establishing wireless links with one or more stations 14, and packet network 16 communicates packets associated with the communications sessions to and from stations 14. More specifically, for the distribution of packets containing information for communication to mobile unit 12, packet network 16 uses multicast protocols to distribute copies of these packets to one or more stations 14. For example, gateway 18 may receive information for communication to mobile unit 12 and generate a multicast packet containing that information. Packet network 16 then distributes copies of the multicast packet to stations 14 that are in a multicast group associated with mobile unit 12.

Mobile units

12 provide wireless communications for voice, data, video, signaling, control, telemetry, and/or other transmissions using any suitable wireless communications protocols by establishing wireless links with stations 14. Mobile units 12 may be analog or digital cellular telephones, personal digital assistants (PDAs), pagers, or other suitable wireless devices providing wireless services for subscribers. Wireless links represent any channel or channels established between devices for the persistent, periodic, or sporadic communication of information, including signaling, registration, data, voice, and other information, using any suitable wireless communications protocols.

Stations

14 represent hardware and/or software supporting wireless links with mobile units 12. Stations 14 receive information from mobile units 12 in packets or receive information from mobile units 12 and packetize the information for packet-switched communication using packet network 16. Packet network 16 represents any collection and arrangement of hardware and/or software providing packet-switched communications between stations 14, gateway 18, and roam manager 20. For example, packet network 16 may include routers, bridges, gateways, switches, or other suitable network equipment providing packet-switched communications.

Gateway 18 represents hardware and/or software, such as a mobile switching center (MSC), network gateway, router, switch, or other suitable equipment, that links packet network 16 to outside networks 26. For example, gateway 18 may link to the public switched telephone network (PSTN), a global computer network such as the Internet, local area networks (LANs), wide area networks (WANs), or other communications networks. Moreover, gateway 18 may support conversions between the packet-switched communications supported by packet network 16 and protocols used by outside networks 26. For example, gateway 18 may communicate information with packet network 16 using packet-switched protocols while providing circuit-switched communications with selected outside networks 26. While this example illustrates a system having a single gateway 18, system 10 contemplates incorporating multiple gateways 18 each coupling to one or more outside networks 26.

Roam manager 20 represents hardware and/or software that monitors, manages, and controls wireless links between mobile units 12 and stations 14. As part of this management and control, roam manager 20 facilitates the handoff of mobile units 12 between stations 14. Handoff refers to any activities supporting communications between mobile unit 12 and multiple stations 14 or supporting movement of mobile units 12 between areas serviced by different stations 14 or other wireless services equipment. Moreover, handoff contemplates “soft-handoff,” such as that provided by code division multiple access (CDMA) systems. Thus, roam manager 20 supports management and control of links between mobile units 12 and stations 14 to provide substantially uninterrupted communications. In addition, roam manager 20 may manage membership in multicast groups associated with mobile units 12. These multicast groups allow multiple stations 14 to receive copies of packets containing information for communication to mobile units 12. In managing membership in multicast groups, roam manager 20 registers and removes stations 14 from various multicast groups associated with mobile units 12.

While this figure illustrates roam manager 20 as a separate component, system 10 contemplates incorporating the functionalities of roam manager 20 into any suitable component or components. That is, devices in packet network 16, gateway 18, stations 14, mobile units 12, and/or other suitable equipment may provide some or all of the functions of roam manager 20. Moreover, any of the functionalities of roam manger 20 may be separated and distributed among components of system 10 and may be implemented using any suitable combination of hardware and/or software. For example, in certain wireless systems, each mobile unit 12 may monitor the strength of pilot signals received from stations 14 and communicate a list of “candidate” stations 14 (each with a relatively high potential for supporting a wireless link) to a central, decision-making component. Moreover, in a system implementing a form of High Data Rate (HDR) communications, such as CDMA 1xEV-DO (1x Evolution-Data Only) or 1xEV-DV (data and voice), mobile unit 12 may further determine, on a packet-by-packet or frame-by-frame basis, a single station 14 from which to receive communications. Thus, elements may work in coordination to effect handoff decisions and manage membership in multicast groups.

To facilitate management and control of handoff decisions and multicast group membership, roam manager 20 may access information stored in a memory 22. Memory 22 represents any one or combination of volatile or non-volatile, local or remote devices suitable for storing data, for example, random access memory (RAM) devices, read only memory (ROM) devices, magnetic storage devices, optical storage devices, or any other suitable data storage devices. In a particular embodiment, memory 22 stores multicast association information 24 that maintains information associating mobile units 12 to multicast addresses. For example, association information 24 may include a table listing identifiers for mobile units 12 corresponding to multicast addresses for each mobile unit 12. Thus, the identifiers, such as Internet protocol (IP) addresses or mobile identifiers (MINs), index to a multicast address assigned for each mobile unit 12. These multicast addresses represent designated addresses in any addressing scheme designed for the delivery of copies of a single packet to multiple recipients. For example, Internet protocol (IP) provides a range of addresses (Class D) as multicast addresses.

Roam manager 20 may dynamically or statically allocate multicast addresses to mobile units 12. For example, upon detecting mobile unit 12 within a radio access network (RAN) serviced by roam manager 20, roam manager 20 may create an entry in association information 24 associating mobile unit 12 with a multicast address. Mobile unit 12 may then remain associated with that multicast address until exiting that particular RAN. Alternatively, roam manager 20 may assign a multicast address to mobile unit 12 prior to mobile unit 12 handing off between multiple stations 14. Once handoff completes and mobile unit 12 communicates with a single station 14, roam manager 20 may reassign that multicast address. However, system 10 contemplates roam manager 20 using any suitable techniques and criteria for assigning and reassigning multicast addresses to mobile units 12.

In operation, mobile unit 12 establishes communications sessions with remote locations using wireless links with one or more stations 14. These stations 14 may use any suitable connection-oriented or connectionless, synchronous or asynchronous protocols. The establishment of a session may result from mobile unit 12 initiating a telephone call, receiving a telephone call, establishing a data session, transmitting or receiving a page, moving into a geographic region, roaming into an area, or any other suitable event. During a communications session, packet network 16 communicates packets associated with the session between gateway 18 and appropriate stations 14. For example, packet network 16 may deliver copies of outbound packets (containing information for transmission to mobile unit 12) to stations 14 currently communicating with or likely to communicate with mobile unit 12.

To deliver copies of outbound packets to multiple stations 14, elements in system 10 use multicast packet routing techniques. For example, roam manager 20 determines stations 14 communicating with (or likely to communicate with) mobile unit 12, assigns a multicast address to mobile unit 12, and registers the selected stations 14 with a multicast group identified by the multicast address. Gateway 18 receives information for communication to mobile unit 12, generates packets addressed to the multicast address assigned to mobile unit 12, and communicates these packets using packet network 16. Packet network 16 delivers copies of each of these multicast packets to stations 14 registered for the multicast group. These stations 14 may then communicate information from the multicast packets to mobile unit 12. Thus, using multicast protocols, gateway 18 can deliver copies of each outbound packet to one or more stations 14 without knowing the particular stations 14 that will receive copies. That is, packet network 16 automatically distributes copies of each multicast packet to stations 14 in the multicast group, regardless of whether the device generating the multicast packets is aware of the members of the multicast group.

For example, consider mobile unit 12, having established a communications session, communicating information for the session using wireless links with stations 14 labeled A and B (station A and station B). To receive outbound packets containing information for communication to mobile unit 12, stations A and B register or are registered for a multicast group associated with mobile unit 12. Gateway 18 need not know the members of the group, rather only a multicast address for the group. That is, using protocols such as Internet Group Management Protocol (IGMP), packet network 16 may establish routing trees for delivering multicast packets to each station 14 registered for a multicast group. Thus, gateway 18 addresses each outbound packet to the multicast address and communicates the outbound packets to packet network 16. Packet network 16 then communicates copies of each outbound packet to stations A and B.

To aid with handoffs and multicast group membership determinations, stations 14 may provide information to roam manager 20 describing communications with mobile units 12. Roam manager 20 monitors this information to make handoff decisions and/or determine membership of stations 14 in multicast groups. For example, mobile unit 12 may monitor signal strength for pilot signals received from stations 14, generate a list of candidate stations 14 indicating signal strength for a group of stations 14, and communicate this list to station 14 currently communicating with mobile unit 12. Similarly, stations 14 may monitor signals from mobile units 12 on a range of channels to detect signal information on both mobile units 12 that are currently communicating with station 14 and other mobile units 12. Station 14 reports information on signals, whether from its own monitoring or if received from other devices, to roam manager 20.

Given an appropriate triggering event, such as a signal strength dropping below or exceeding some predetermined threshold, roam manager 20 may initiate handoff of mobile unit 12 between stations 14. For example, roam manager 20 may register certain stations 14 in a multicast group associated with mobile unit 12 and direct the establishment of wireless links between mobile unit 12 and these stations 14. This allows a communications session to continue without interruption by switching between stations 14 when moving between areas serviced by different stations 14.

For example, consider mobile unit 12 entering an area serviced by station A. Station A and/or other stations 14 monitor signals received from mobile unit 12 and report this information to roam manager 20. Roam manager 20, upon detecting an appropriate condition, such as the signals exceeding some predetermined threshold, registers station A for a multicast group associated with mobile unit 12. In addition, roam manager 20 may inform station A that it has been registered for the multicast group, allowing station A to begin providing service for mobile unit 12. When roam manager 20 determines that mobile unit 12 no longer needs service from station A, roam manager 20 removes station A from the multicast group associated with mobile unit 12. For example, when mobile unit 12 moves out of the area serviced by station A, roam manager 20 may remove station A from the multicast group and inform station A to no longer provide service to mobile unit 12.

In addition to registering and removing stations 14 from multicast groups, roam manger 20 may direct the establishment of wireless links between stations 14 and mobile units 12. For example, after registering station A with a multicast group, roam manger 20 may direct station A to communicate with mobile unit 12 and direct mobile unit 12 to communicate with station A. However, system 10 contemplates stations 14 and mobile units 12 using any appropriate methods for determining when to establish wireless links and provide wireless services. For example, station A may detect its registration into a multicast group by roam manager 20 and, in response, begin providing service to mobile unit 12. In addition, while this example focuses on the registration and removal of station A in a multicast group based on mobile unit 12 moving in and out of an area serviced by station A, system 10 contemplates roam manager 20 using any suitable criteria for adding and removing stations 14 from multicast groups. Thus, roam manager 20 may manage membership in multicast groups based on geographic location, load balancing, and/or any other suitable criteria.

Moreover, while these examples focus on a separate roam manager 20 handling handoff decisions and managing membership in multicast groups, system 10 contemplates any appropriate division of these functions among various components. For example, each station 14 may monitor signals from mobile units 12 to determine mobile units 12 within an effective range of that station 14. This includes, for example, stations 14 determining all mobile units 12 that are receiving a pilot signal at a signal strength that exceeds a threshold, or mobile units 12 transmitting signals that exceed a threshold. Based on these determinations, each station 14 may register with multicast groups for mobile units 12 within range and drop from multicast groups for mobile units 12 that have moved out of range. Thus, each station 14 may manage its membership in multicast groups associated with mobile units 12. However, system 10 contemplates having any distribution or centralization of handoff and multicast group management functions.

FIG. 2 illustrates functional elements of an exemplary gateway 18 having two

interfaces

40 and 42, a processor 44, and a memory 46. Gateway 40 couples to outside networks 26 using interface 40 and couples to packet network 16 using interface 42. Memory 46 maintains information for use by elements of gateway 18, such as programs for execution by processor 44, tables associating mobile units 12 with multicast addresses, and other suitable information. In general, gateway 18 provides a link to outside networks 26 and, for information received from outside networks 26 for communication to mobile units 12, provides for delivery of this information to stations 14 using multicast communications protocols.

To facilitate the operation of elements in gateway 18, memory 46 may store tables or other information associating mobile units 12 with multicast addresses. For example, memory 46 may store some or all of association information 24. As with memory 22, memory 46 represents any collection and arrangement of volatile or non-volatile, local or remote data storage devices. Moreover, because system 10 contemplates a distribution of functions, memory 46 may further represent all or part of memory 22. That is, gateway 18 may access information stored by any appropriate device in system 10.

In operation, gateway 18 receives information for communication to mobile unit 12 from outside network 26, in packet form or otherwise, using interface 40. Upon receipt, processor 44 determines whether mobile unit 12 has an associated multicast group and, if so, determines the multicast address for mobile unit 12. Processor 40 then generates a multicast packet (or packets) encapsulating this information and communicates the packet to packet network 16 using interface 42. Processor 40 may also fragment information as one or more packets and generate multicast packets encapsulating this fragmented information. Packet network 16 then communicates this multicast packet to each station 14 registered for the multicast group associated with mobile unit 12.

Thus, to deliver outbound packets containing information for delivery to mobile unit 12, gateway 18 generates packets addressed to a multicast address associated with mobile unit 12. For example, upon receiving a packet addressed to mobile unit 12, gateway 18 may encapsulate the received packet as the payload for a packet addressed to a multicast address. Or, upon receiving the packet, gateway 18 may readdress the packet by replacing the address for mobile unit 12 with the assigned multicast address. In addition, gateway 18 may receive circuit-switched or other non-packet forms of information destined for mobile unit 12. Gateway 18 reforms this information as the payload for one or more multicast packets addressed to the multicast address for mobile unit 12. However, system 10 contemplates gateway 18 using any suitable techniques for generating multicast packets for delivery to stations 14. After generating a multicast packet, gateway 18 communicates the packet to packet network 16, which communicates copies of the multicast packet to each station 14 registered for the multicast group associated with mobile unit 12. Thus, using multicast protocols, gateway 18 can deliver copies of each outbound packet to one or more stations 14.

While this example includes specific functional elements for gateway 18, system 10 contemplates gateway 18 containing any collection and arrangement of elements. Moreover, system 10 contemplates gateway 18 implementing some or all of the functions of roam manager 20. Thus, gateway 18 may manage handoff of mobile units 12 and membership of stations 14 in multicast groups associated with mobile units 12. In addition, system 10 contemplates implementing each of the functional elements within gateway 18 using any suitable combination and arrangement of hardware and/or software and implementing any of the functionalities using a computer program stored on a computer readable medium.

FIG. 3 illustrates functional elements of an exemplary station 14 having an interface 50, a wireless interface 52, a processor 54, and a memory 56. Interface 50

couples station

14 to packet network 16, and wireless interface 52

couples station

14 to mobile units 12. Memory 56 stores information for use by elements of station 14, such as computer code for execution by processor 54, information associating mobile units 12 with multicast groups, time-slot assignments, frequency assignments, Walsh code assignments, and/or other suitable information. Processor 54 manages and controls the operation of elements within station 14. In general, station 14 provides wireless communications services for mobile units 12 and, more specifically, receives some or all information for communication to mobile units 12 as packets addressed to multicast addresses associated with mobile units 12.

To facilitate the operation of elements in station 14, memory 56 may store tables or other information associating mobile units 12 with multicast addresses. For example, memory 56 may store some or all of association information 24. In addition, as discussed with respect to memory 46 in gateway 18, memory 56 represents any collection and arrangement of volatile or non-volatile, local or remote devices suitable for data storage. Moreover, because system 10 contemplates any suitable distribution of functions, memory 56 may represent some or all of memory 22 and/or memory 46. Thus, station 14 may access information stored by gateway 18, roam manager 20, or any other suitable element in system 10 during operation.

In operation, station 14 receives information for communication to mobile units 12 from packet network 16 using interface 50. Some or all of the information received may be in the form of packets addressed to multicast addresses. Upon receiving a multicast packet, processor 54 determines mobile unit 12 identified by the multicast packet. For example, processor 54 may determine the multicast address of the multicast packet and access information in memory 56 to determine mobile unit 12 associated with that multicast address. Station 14 may communicate the multicast packet to mobile unit 12 as received or may alter or extract information from the multicast packet before communicating with mobile unit 12. For example, if gateway 18 receives packets from outside network 26 and then encapsulates these packets as payloads for multicast packets, then station 14 may extract the encapsulated packets before communicating with mobile unit 12. Alternatively, station 14 may readdress the multicast packet by replacing the multicast address with an address, such as an IP address, for mobile unit 12. However, while this description focuses on specific techniques for altering or extracting information from multicast packets, system 10 contemplates station 14 using any suitable techniques to transform information received as multicast packets into formats suitable for communication to mobile units 12.

Once in proper format, station 14 communicates information from the multicast packet to mobile unit 12 using wireless interface 52. However, in certain situations station 14 may discard multicast packets without communicating any information from the packets to mobile unit 12. For example, station 14 may become a member of a multicast group associated with mobile unit 12 in anticipation of communicating with mobile unit 12. This ensures that station 14 may immediately commence communication of information to mobile unit 12 in any appropriate circumstance, thus ensuring continuous service for mobile unit 12 and allowing seamless handoffs between stations 14. According to a particular embodiment, stations 14 communication with mobile units 12 using CDMA protocols. By distributing packets using multicast protocols, each station 14 communicating with a particular mobile unit 12 can receive packets, thus enabling soft-handoffs.

However, some communications protocols, such as High Data Rate (HDR) communications, limit the number of stations 14 that may communicate information to mobile unit 12. For example, to increase the amount of data that may be sent within a particular spectrum, the HDR communications protocol specifies that each frame of packets for communication to mobile unit 12 be sent by a single station 14. Yet, to ensure seamless handoffs between stations 14 when using protocols such as these, multiple stations 14 may be members of a multicast group associated with mobile unit 12, with only a subset of the members of the multicast group communicating information from multicast packets to mobile unit 12. By including stations 14 likely to communicate with mobile unit 12 in the multicast group, system 10 ensures that stations 14 have information available for a substantially seamless handoff between stations 14. However, until transmissions from station 14 are specified, station 14 may discard some or all multicast packets received.

As previously discussed, system 10 contemplates any appropriate distribution of functions between components. Thus, stations 14 may handle some or all of the tasks of roam manager 20, such as managing membership in multicast groups. For example, station 14 may register for multicast groups for all mobile units 12 within an effective range. That is, station 14 may register for a multicast group associated with mobile unit 12 when mobile unit 12 moves into an area serviced by station 14, when mobile unit 12 activates within the service area of station 14, when mobile unit 12 requests service from station 14, or at any other appropriate time. Station 14 may then withdraw from the multicast group associated with mobile unit 12 when mobile unit 12 moves out of the area serviced by station 14, when mobile unit 12 is no longer detected, when mobile unit 12 requests service to be discontinued, or at any other appropriate time. Moreover, station 14 may collaborate with other elements in system 10 in determining membership in multicast groups. For example, station 14 may communicate with other stations 14, gateway 18, a centralized element such as roam manager 20, and/or other appropriate elements in system 10 to aid in determining appropriate membership in multicast groups.

While this example includes specific functional elements for station 14, system 10 contemplates station 14 containing any collection and arrangement of elements. Moreover, system 10 contemplates implementing each of the functional elements within station 14 using any suitable combination and arrangement of hardware and/or software and implementing any of the functionalities using a computer program stored on a computer readable medium.

FIG. 4 is a flowchart illustrating a method for generating multicast packets for distribution to a group of stations 14, with the multicast packets containing information for communication to mobile unit 12. While the following description of this method focuses on the operation of gateway 18, however, system 10 contemplates any suitable element or elements performing these or similar steps.

Gateway

18 monitors packets received from outside networks 26 at step 70 and determines whether a packet has been received at step 72. If not, gateway 18 continues monitoring packets at step 70. However, upon receiving a packet, gateway 18 determines the destination address of the packet at step 74. If gateway 18 determines that the destination address indicates mobile unit 12 at step 76, gateway 18 determines whether the indicated mobile unit 12 is associated with a multicast address at step 78. For example, gateway 18 may access association information 24 to determine whether the destination address maps to an associated multicast address. If the destination address does not indicate mobile unit 12 at step 76 or is not associated with a multicast address at step 78, gateway 18 forwards the packet according to standard protocols at step 80.

However, if the destination address indicates a mobile unit that is associated with a multicast address, gateway 18 determines the multicast address for the mobile unit at step 82 and generates a multicast packet containing information from the received packet at step 84. Gateway 18 may use any suitable techniques for generating the multicast packet. For example, gateway 18 may generate the multicast packet by encapsulating the received packet as the payload for a multicast packet addressed to the multicast address. Alternatively, gateway 18 may readdress the received packet by replacing the address of mobile unit 12 with the associated multicast address. Moreover, these two methods for generating a multicast packet illustrate only specific examples, and system 10 contemplates gateway 18 using any suitable methods for generating multicast packets containing information received from outside network 26 for communication to mobile unit 12. After generating the multicast packet, gateway 18 communicates the multicast packet to packet network 16 at step 86. After appropriately handling the received packet, gateway 18 continues monitoring packets at step 70.

While this flowchart illustrates an exemplary method, system 10 contemplates using any suitable techniques and equipment for receiving information for communication to mobile units 12 and encapsulating this information in multicast packets for distribution to stations 14. In addition, many of the steps in this flowchart may take place simultaneously and/or in different orders than is shown. For example, gateway 18 may process multiple packets received simultaneously and/or process information received using a variety of different protocols. Moreover, system 10 contemplates using methods with additional steps, fewer steps, or different steps, so long as the methods remain appropriate for distributing information for communication to mobile units 12 to stations 14 using multicast packets.

FIG. 5 is a flowchart illustrating the operation of an exemplary station 14. Station 14 monitors packets received from packet network 16 at step 100 and determines whether a packet has been received at step 102. If not, station 14 continues monitoring packets at step 100. However, upon receiving a packet, station 14 determines the destination address of the packet at step 104 and whether that destination address indicates a multicast address at step 106. If the destination address indicates a multicast address, station 14 determines whether the multicast address is associated with mobile unit 12 at step 108. For example, station 14 may access information such as association information 24 to determine mobile unit 12 associated with the multicast address. If the destination address is not a multicast address or the multicast address is not associated with mobile unit 12, station 14 processes the received packet normally at step 110.

However, if the destination address is a multicast address associated with mobile unit 12, station 14 determines mobile unit 12 from the multicast address at step 112 and communicates information from the multicast packet to mobile unit 12 at step 114. As previously discussed, station 14 may transform multicast packets received from packet network 16 using any appropriate techniques before communicating with mobile unit 12. For example, station 14 may extract an encapsulated packet from the multicast packet, readdress the multicast packet to mobile unit 12, extract the information from the multicast packet for communication to mobile unit 12 in a particular time-slot, or otherwise modify the multicast packet before communicating with mobile unit 12.

While this flowchart illustrates an exemplary method, system 10 contemplates using any suitable techniques and equipment for processing multicast packets having information for communication to mobile units 12. Moreover, many of the steps in this flowchart may take place simultaneously and/or in different orders than is shown. For example, station 14 may process multiple packets received simultaneously. In addition, system 10 contemplates using methods with additional steps, fewer steps, or different steps, so long as the methods remain appropriate for processing multicast packets having information for communication to mobile units 12.

FIG. 6 is a flowchart illustrating the operation of an exemplary station 14 implementing HDR communications with mobile units 12. In the particular embodiment detailed, station 14 is currently registered for a multicast group associated with mobile unit 12, and the multicast group may contain any number of other stations 14. Moreover, in this embodiment, mobile unit 12 determines selected stations 14 from which to receive packets. For example, on a frame-by-frame basis, mobile unit 12 may select an individual station 14 to communicate packets.

Station

14 monitors packets received from packet network 16 and requests for communications from mobile units 12 at step 130. Upon receiving a request for communications at step 132, station 14 determines whether the request identifies this station 14 at step 134. If so, station 14 enables communications with mobile unit 12 at step 136. If not, station 14 disables communications with mobile unit 12 at step 138. However, while this example illustrates station 14 monitoring requests from mobile unit 12 to determine when to enable and disable communications, system 10 contemplates station 14 using any appropriate methods for determining whether to enable communications according to the particular protocols being used for communications.

If station 14 receives a packet at step 140, station 14 determines a destination address of the packet at step 142. If station 14 determines that the destination address is for a multicast address at step 144, station 14 determines whether the multicast address is associated with mobile unit 12 at step 146. If the destination address is not for a multicast address associated with mobile unit 12, station 14 processes the packet normally at step 154. However, if the destination address is for a multicast address associated with mobile unit 12, station 14 determines whether communications are enabled with mobile unit 12 at step 148. If so, station 14 extracts the packet encapsulated within the multicast packet at step 150 and communicates the extracted packet to mobile unit 12 at step 152. However, if communications are not enabled with mobile unit 12, station 14 discards the packet at step 156.

While this flowchart illustrates an exemplary method, system 10 contemplates using any suitable techniques and equipment for processing multicast packets containing information for communication to mobile units 12 using communications protocols such as HDR communications. For example, station 14 may use similar techniques for any protocol in which station 14 may receive multicast packets that are not to be communicated to mobile unit 12. In addition, many of the steps in this flowchart may take place simultaneously and/or in different orders than as shown. For example, station 14 may simultaneously process multiple requests for communications and/or multiple packets received simultaneously from packet network 16. Moreover, system 10 contemplates using methods with additional steps, fewer steps, or different steps, so long as the methods remain appropriate for processing multicast packets containing information for communication to mobile units 12.

FIG. 7 is a flowchart illustrating a method for managing handoffs and membership of stations 14 in multicast groups. The following description focuses on the operation of roam manager 20, however, as previously discussed, system 10 contemplates any suitable division of these functions and any appropriate elements in system 10 implementing some or all of these functions.

Roam manager 20 monitors signals, for example, to determine radio link quality, between stations 14 and mobile units 12 at step 170. This information may be reported by stations 14, mobile units 12, or other devices monitoring communications between stations 14 and mobile units 12. Roam manager determines whether signals between a particular mobile unit 12 and a particular station 14 exceed an add threshold at step 172. For example, roam manager 20 may monitor signal strength of signals between mobile unit 12 and station 14 currently not registered with a multicast group associated with mobile unit 12. This determines whether to add station 14 to the multicast group for mobile unit 12. If those signals do not exceed the add threshold, roam manager 20 determines whether signals between some mobile unit 12 and station 14 are below a drop threshold at step 174. For example, roam manager 20 may monitor signal strength for signals between mobile unit 12 and station 14 that is currently registered for a multicast group associated with mobile unit 12. This determines whether roam manager 20 should remove station 14 from the multicast group associated with mobile unit 12 and discontinue communications between station 14 and mobile unit 12. If roam manager 20 does not detect a particular station 14 for adding to a multicast group at step 172 and does not detect a particular station 14 for removing from a multicast group at step 174, roam manager 20 continues monitoring signals between stations 14 and mobile units 12 at step 170.

However, if roam manager 20 identifies a particular station 14 for adding to a multicast group, roam manager 20 registers that particular station 14 with the multicast group for mobile unit 12 at step 182, directs station 14 to communicate with mobile unit 12 at step 184, and directs mobile unit 12 to communicate with station 14 at step 186. For example, in a CDMA system, roam manager 20 may direct station 14 to communicate with mobile unit 12 on a particular Walsh code/frequency pair and direct mobile unit 12 to receive communications from station 14 on a particular Walsh code/frequency pair. Thus, station 14 and mobile unit 12 establish a wireless link supporting the establishment of communications sessions, and the registration of station 14 in the multicast group enables station 14 to receive multicast packets containing information for these communications sessions. Similarly, if roam manager 20 determines that a particular station 14 should be removed from a multicast group, roam manager 20 withdraws station 14 from the multicast group for mobile unit 12 at step 176, directs station 14 to discontinue communications with mobile unit 12 at step 178, and directs mobile unit 12 to discontinue communications with station 14 at step 180.

While this flowchart illustrates an exemplary method, system 10 contemplates using any suitable techniques and equipment for managing handoffs and membership of stations 14 in multicast groups for mobile units 12. Thus, many of the steps in this flowchart may take place simultaneously and/or in different orders than is shown. For example, roam manager 20 may simultaneously monitor signals from multiple stations 14 for any number of mobile units 12 and respond appropriately to any conditions indicating a need for adding or removing stations 14 from multicast groups. In addition, system 10 contemplates using methods with additional steps, fewer steps, or different steps, so long as the methods remain appropriate for managing membership of stations 14 in multicast groups. For example, different communications protocols may dictate different methods for making handoff decisions and directing the establishment of wireless links between mobile units 12 and stations 14. System 10 contemplates using any suitable steps for implementing multicast distribution of information for any communications systems. Furthermore, while this description details the operation of roam manager 20, system 10 contemplates any suitable components managing membership in multicast groups. Thus, as previously discussed, elements such as stations 14, gateways 18, and mobile units 12 may manage or participate in management of membership of stations 14 in multicast groups.

FIG. 8 shows how the underlying packet network 16 of communications system 10 can be leveraged with multicast operation. For a soft handoff group associated with mobile unit 12, all base transceivers 14 of the soft handoff group need to receive the same packet containing the bearer traffic. Instead of using multiple virtual circuits between gateway 18 and base transceiver stations 14 to transfer multiple packets of information each unique for each base transceiver station 14 as is conventionally implemented, a single multicast packet of information 200 is transferred from gateway 18 to base transceiver stations 14. Generation of the multicast packet may be performed at step 84 of FIG. 4. The multicast packet of information 200 includes a common traffic section 202 and a plurality of unique control sections 204. The common traffic section 202 has information destined for mobile unit 12 including bearer traffic and control traffic used by mobile unit 12. Each unique control section 204 is associated with one of the base transceiver stations 14 in the soft handoff group of mobile unit 12. Each unique control section 204 includes control information specific to the particular base transceiver station with which it corresponds in order to control transfer of the common traffic section 202 to mobile unit 12. In this manner, multiple bearer virtual circuits between gateway 18 and base transceiver stations 14 can be replaced by a single multicast tree implementation. Packet network 16 may be an Internet Protocol (IP) network, an Asynchronous Transfer Mode (ATM) network, or provide any other type of packet transport capability. Packet network 16 may also provide an underlying network of a first packet type carrying information in a second packet type, for example as in IP packets being carried in ATM cells.

In operation, the multicast packet of information 200 is transmitted in a multicast tree to each base transceiver station in the soft handoff group of mobile unit 12. Each base transceiver unit 12 extracts the common traffic section 202 for transmission to mobile unit 12. Each base transceiver station 14 identifies its corresponding unique control section 202 and extracts unique control information therefrom to control transmission of the common traffic section 202 to mobile unit 12. Each base transceiver station 14 will discard those unique control sections 204 that are associated with other base transceiver stations in the soft handoff group. Performance of this operation may occur at step 114 of FIG. 5. If gateway 18 supports N base transceiver stations 14, the multicast packet of information 200 will include N unique control sections 204 and one common traffic section 202 for a soft handoff group of N legs. Though there may be N base transceiver stations 14, the soft handoff group may be established with less than N legs.

Each unique control section 204 has control information elements for a corresponding base transceiver station 14 to include power control settings and other information unique to a specific soft handoff leg. FIG. 9 shows an example of how each unique control section 204 is carried in the multicast packet of information 200. In addition to transport layer information, the multicast packet of information 200 may include common traffic section 202 having a values for a Forward Power Control—Sector Link Count (FPC:SLC) that indicates how many legs are in the soft handoff group with mobile station 12 and count repetitions of the unique control sections 204. Another portion of common traffic section 202 may be a Frame Sequence Number (FSN), Forward Link Information (FLI) which has the bearer data destined for mobile unit 12, and a Frame Content (FC) which defines a frame size or length of the bearer data used to find an end of common traffic section 202 in the multicast packet of information 200. Each unique control section 204 may be made up of values for a Forward Power Control—Gain Ratio (FPC:GR), a Reverse Power Control—Outer Loop Threshold (RPC:OTL), and/or a Soft handoff Leg Index (SLI). Through use of the SLC and the FC fields, each base transceiver station 14 can identify its corresponding unique control section 204 within the multicast packet of information 200. Alternatively, each base transceiver station 14 may use its unique SLI established through prior signaling with gateway 18 to extract its corresponding unique control section 204 for ease in searching and identifying within the multicast packet of information 200.

Since a soft handoff group is expected to be relatively small, as in a group of one to three base transceivers, only a small amount of additional overhead may occur through the use of the multicast packet of information 200 with common traffic section 202 and multiple unique control sections 204. Assignment of the SLI for each base transceiver station 14 in a soft handoff group may be performed through signaling messages in establishing a connection between gateway 18 and base transceiver stations 14. During this connection, a SLI may be assigned to uniquely identify a bearer stream from other bearer streams from the same gateway 18 for the same mobile unit 12. Gateway 18 controls the format of the multicast packet of information 200, assigns the SLI, and ensures that each unique control section 204 includes proper control information for the appropriate leg. For example, gateway 18 may assign an initial SLI of 0 to the first leg terminating at BTS A. Gateway 18 then assigns a SLI of 1 to the second leg terminating at BTS B. BTS A would extract a first unique control section 204 in the multicast packet of information 200 associated with SLI 0. BTS B would extract a second unique control section 204 associated with SLI 1. The assigning of an SLI continues for all base station transceivers in the soft handoff group and as more base station transceivers are dynamically added to the soft handoff group during operation.

As base station transceivers 14 are deleted from the soft handoff group, there will be an unused unique control section 204. No efficiency loss occurs if the unused unique control section 204 is at the end of the multicast packet of information 200. If an unused unique control section 204 is amongst other in use unique control sections 204, the unused unique control section 204 is transmitted redundantly until the call ends or another gateway 18 is handed responsibility for the call. For optimization, gateway 18 may re-assign SLIs of base transceiver stations. Gateway 18 coordinates the generation of the multicast packet of information 200 with signaling messages to base transceiver stations 14 indicating changes in SLI assignments. To affect a seamless change, the signaling message indicating SLI changes may also indicate that the change is to take effect in a specified number of frames to allow a receiver in a base transceiver station 14 to be aligned with a transmitter at gateway 18. Alternatively, SLI assignments and changes may be provided in the multicast packet of information 200.

Claims

1. A system for providing information to a mobile unit, comprising:

a gateway operable to generate a packet of information, the packet of information including a common traffic section and a plurality of unique control sections;

a first transceiver station operable to receive the packet of information from the gateway, the first transceiver station operable to identify one of the plurality of unique control sections as being associated therewith, the first transceiver station operable to transmit the common traffic section according to its identified one of the plurality of unique control sections;

wherein each of the plurality of unique control sections corresponds to a separate one of a plurality of transceiver stations.

2. The system of claim 1, wherein the plurality of unique control sections are associated with a soft handoff group of transceiver stations.

3. The system of claim 1, wherein each of the plurality of unique control sections includes a forward power control gain ratio value, a reverse power control value, and an outer loop threshold value.

4. The system of claim 1, wherein the common traffic section includes a forward power control sector link count value, a frame sequence number, a frame size value, and bearer information.

5. The system of claim 1, wherein the common traffic section includes an indication of a number of unique control sections carried in the packet of information.

6. The system of claim 1, wherein the gateway provides the transceiver station with a leg index, the leg index operable to identify the one of the plurality of unique control sections associated with the first transceiver station.

7. The system of claim 1, further comprising:

a second transceiver station operable to receive the packet of information from the gateway, the second transceiver station belonging to a soft handoff group with the first transceiver station, the second transceiver station operable to identify one of the plurality of unique control sections as being associated therewith, the second transceiver station operable to transmit the common traffic section according to its identified one of the plurality of unique control sections.

8. A system for providing information to a mobile unit, comprising:

a second transceiver station operable to receive the packet of information from the gateway, the second transceiver station belonging to a soft handoff group with the first transceiver station, the second transceiver station operable to identify one of the plurality of unique control sections as being associated therewith, the second transceiver station operable to transmit the common traffic section according to its identified one of the plurality of unique control sections;

wherein the gateway is operable to dynamically assign a leg index to each of the first and second transceiver stations in response to an addition or deletion of other transceiver stations to the soft handoff group, the leg index operable to identify an associated unique control section.

9. The system of claim 8, wherein the plurality of unique control sections includes a redundant control section for an other transceiver station deleted from the soft handoff group.

10. A method for providing information to a mobile unit, comprising;

receiving a packet of information, the packet of information including a common traffic section and a plurality of unique control sections associated with a soft handoff group for the mobile unit;

identifying an appropriate one of the plurality of unique control sections;

transmitting the common traffic section according to the appropriate one of the unique control sections;

receiving a leg index;

identifying the appropriate one of the plurality of unique control sections in response to the leg index.

11. The method of claim 10, further comprising:

adjusting membership in the soft handoff group;

reassigning the leg index in response to soft handoff group adjustment.

12. The method of claim 11, further comprising:

including a redundant control section in the packet of information in response to a deletion in the soft handoff group membership.

13. A method for providing information to a mobile unit, comprising;

identifying an appropriate one of the plurality of unique control sections;

wherein the common traffic section includes an indication of a number of the plurality of unique control sections carried in the packet of information.

14. A system of providing information to a mobile unit, comprising;

means for receiving a packet of information, the packet of information including a common traffic section and a plurality of unique control sections associated with a soft handoff group for the mobile unit;

means for identifying an appropriate one of the plurality of unique control sections;

means for transmitting the common traffic section according to the appropriate one of the unique control sections;

means for receiving a leg index;

means for identifying the appropriate one of the plurality of unique control sections in response to the leg index.

15. The system of claim 14, further comprising:

means for adjusting membership in the soft handoff group;

means for reassigning the leg index in response to soft handoff group adjustment.

16. The system of claim 15, further comprising:

means for including a redundant control section in the packet of information in response to a deletion in the soft handoff group membership.

17. A system of providing information to a mobile unit, comprising;

18. A computer readable medium including code for providing information to a mobile unit, the code upon execution operable to:

receive a packet of information, the packet of information including a common traffic section and a plurality of unique control sections associated with a soft handoff group for the mobile unit;

identify an appropriate one of the plurality of unique control sections;

transmit the common traffic section according to the appropriate one of the unique control sections;

receive a leg index;

identify the appropriate one of the plurality of unique control sections in response to the leg index.

19. The computer readable medium of claim 18, wherein the code is further operable to:

adjust membership in the soft handoff group;

reassign the leg index in response to soft handoff group adjustment.

20. The computer readable medium of claim 19, wherein the code is further operable to:

include a redundant control section in the packet of information in response to a deletion in the soft handoff group membership.

21. A computer readable medium including code for providing information to a mobile unit, the code upon execution operable to:

identify an appropriate one of the plurality of unique control sections;