Source: https://patents.google.com/patent/US8843638B2/en
Timestamp: 2019-04-19 08:50:09+00:00

Document:
A connection is established between an access terminal and a first radio network controller through a first radio node. The first radio node is controllable primarily by the first radio network controller. The connection is maintained with the first radio network controller as the access terminal moves from a coverage area of the first radio node toward a coverage area of a second radio node. The second radio node is controllable primarily by a second radio network controller and controllable subordinately by the first radio network controller. A connection is also established through the second radio node. Upon a fulfillment of a predetermined criterion, the connection is transferred from the first radio network controller to the second radio network controller.
This disclosure relates to active handoffs between radio networks.
Cellular wireless communications systems are designed to serve many access terminals distributed in a large geographic area by dividing the area into cells, as shown in FIG. 1. At or near the center of each cell 102, 104, 106, a radio network access point 108, 110, 112, also referred to as a radio node (RN) or base transceiver station (BTS), is located to serve access terminals 114, 116 (e.g., cellular telephones, laptops, PDAs) located in the cell. Access terminals (AT) are sometimes referred to as mobile stations (MS) or user equipment (UE). Each cell is often further divided into sectors 102 a-c, 104 a-c, 106 a-c by using multiple sectorized antennas. An RN is identified by one or more of several properties, which may include the offset of a pseudonoise pattern in its pilot signal (PN offset), a frequency, an IP address, or a SectorID. In each cell, that cell's radio network access point may serve one or more sectors and may communicate with multiple access terminals in its cell.
When an access terminal moves from one sector or cell to another and control of the access terminal is transitioned between different network elements, the transfer is referred to as handoff. If the access terminal has a call in progress during handoff, the handoff is said to be active. Co-pending patent application Ser. No. 11/037,896, filed Jan. 18, 2005, and titled Radio Network Control, also assigned to Airvana, Inc., described active handoffs in partially-connected radio networks. The type of handoff described in that application is now standardized as the A16 interface in the TIA-878-B standard. According to the standard, A16 handoff is a hard handoff, such that during the handoff, the source radio network controller cannot add the target radio node to its active set, and the target radio network controller cannot add the source radio node to its active set.
In general, in one aspect, a connection is established between an access terminal and a first radio network controller through a first radio node. The first radio node is controllable primarily by the first radio network controller. The connection is maintained with the first radio network controller as the access terminal moves from a coverage area of the first radio node toward a coverage area of a second radio node. The second radio node is controllable primarily by a second radio network controller and controllable subordinately by the first radio network controller. A connection is also established through the second radio node. Upon a fulfillment of a predetermined criterion, the connection is transferred from the first radio network controller to the second radio network controller.
Implementations may include one or more of the following features. The first and second radio network controllers are located in different subnets. The criterion is fulfilled when the first radio node is dropped from an active set of the access terminal. The first radio node is dropped from the active set of the access terminal when a strength of a signal of the first radio node falls below a minimum threshold. The criterion is fulfilled when a strength of a signal of the first radio node falls below a minimum threshold. The connection uses the Ev-DO, CDMA2000, W-CDMA, HSUPA, HSDPA, HSPA, or LTE telecommunications standard. The connection uses voice over IP (VoIP) protocol. The first radio node is also controlled by a third radio network controller. The second radio network controller continues to control the session until a predetermined criterion is fulfilled. The criterion is fulfilled when the active set of the access terminal contains only radio nodes that are controlled subordinately by the second radio network controller. The second radio node sends the second RNC's address to the first RNC.
In general, in one aspect, a connection is established between an access terminal and a first radio network controller, through both a first radio node and a second radio node. The connection is maintained with the first radio network controller as the access terminal moves from a coverage area of the first radio node toward a coverage area of a second radio node. The connection is transferred to a second radio network controller. The connection is maintained with the second radio network controller as the access terminal returns toward the coverage area of the first radio node. The connection is transferred to the first radio network controller once an active set of the access terminal contains no radio nodes primarily controllable by the second radio network controller.
FIG. 1 is a block diagram of a radio area network.
FIG. 2 is a flow chart.
FIG. 3 is a messaging diagram.
Referring to FIG. 1, in some examples, a radio access network (RAN) 100 uses an Ev-DO protocol to transmit data packets between an access terminal, e.g., access terminals 114 and 116, and a radio node, e.g., radio nodes 108, 110, 112. The radio nodes are connected over a backhaul connection 118 to radio network control/packet data serving nodes (RNC/PDSN) 120, which may be one or more physical devices at different locations. Each cell may be divided into sectors 102 a-c, 104 a-c, 106 a-c by antennas as noted above. In each cell, that cell's radio network access point may serve one or more sectors and may communicate with multiple access terminals in its cell. Although this description uses terminology from Ev-DO standards, the same concepts are applicable to other communication methods, including Code Division Multiple Access 2000 (CDMA2000); Wideband Code Division Multiple Access (W-CDMA); High-Speed Uplink Packet Access (HSUPA); High-Speed Downlink Packet Access (HSDPA); High-Speed Packet Access (HSPA), Long Term Evolution (LTE), and the like.
In some examples, as shown in FIG. 2, multihoming allows a single radio node 202 to be controlled by two or more radio network controllers 208 and 210. Traditionally, RNs located within a subnet of a radio area network are controlled by only one RNC located within the same subnet. In contrast, a multihoming system works by associating RNs located near a subnet boundary 220 with at least two RNCs 208 and 210. In some examples, such as that illustrated by FIG. 2, the RNCs 208 and 210 that jointly control the RN 202 are located in different subnets 216 and 218.
When one RN 202 is multihomed, i.e., controlled by two RNCs 208 and 210, we describe one of the RNCs as the primary RNC, and we describe the other RNC as the secondary RNC. In the example of FIG. 2, the RN 202 is multihomed to the RNCs 208 and 210. For purposes of this example, the RNC 208 is the primary RNC, shown by a solid line 205, and the RNC 210 is the secondary RNC, shown by a dashed line 207. We say the RN 202 is primarily homed to the primary RNC 208 and secondarily homed to the secondary RNC 210. There may be more than one secondary RNC.
In its broadest sense, a node is considered to be multihomed if that node has multiple ways of reaching a destination. In the context of mobile wireless networks and the example of FIG. 2, the destination is the packet data serving node (PDSN) 214, and RNs 202 and 204 that are multihomed may communicate with a PDSN 214 through at least two different RNCs 208 and 210. By using multihoming, the functions of the primary RNC are assumed by the secondary RNC when the primary RNC becomes unavailable (e.g., when the AT moves out of range of any RN controlled by the primary RNC), or less desirable (e.g., the AT moves closer to an RN located within the control of the secondary RNC). Uninterrupted connectivity can be achieved if at least one connection to the PDSN is maintained.
When an AT 212 is in handoff from one RNC to another, the RNC 208 originally controlling the AT 212 is the serving RNC, and the RNC 210 to which control is being transferred is the target RNC. When the radio node 202 is multihomed, its primary RNC 208 may be the serving RNC for the AT 212 that is moving to the second RN 204, which happens to be primarily homed to the first RN's secondary RNC 210, such that the first RN's secondary RNC is the target RNC. At the same time, from that second RN 204's point of view, it's primary RNC 210 is the target RNC for the incoming AT 212, and the serving RNC is the secondary RNC 208.
In some examples, as the AT moves from the coverage area of one RN to the coverage area of another RN, it sends a RouteUpdate message to its serving RNC. The RouteUpdate message indicates the identification and strength of any compatible radio nodes' pilot signals that the AT can detect at its current location. The serving RNC uses the RouteUpdate message to trigger and perform normal soft handoffs, in which the AT is transitioned to another RN controlled by the same RNC without dropping any active calls. Through these RouteUpdate messages, the serving RNC obtains a fairly accurate assessment of where the AT is located. The RNC uses this information to trigger an active RNC handoff.
An AT's “active set” refers to the set of available RNs whose pilot signals are received by the AT and are sufficiently strong to remain in communication with the AT. Thus, if an AT were being served by both RN1 and RN2, its active set would be the pilot signals for both RN1 and RN2, which we represent in the parenthetical form (RN1, RN2). An RN is dropped from an AT's active set when its pilot falls below a certain minimum strength threshold. In traditional wireless networks, all the RNs in an ATs active set must be controlled by the same RNC.
In traditional wireless networks using the TIA-878-B standard, an AT crossing the boundary between two RNCs needs to end communication with the serving RNC in order to establish a communication link with the target RNC. These A16 handoffs are “hard handoffs” because while the AT is controlled by the source RNC, it cannot add a target RN controlled only by the target RNC to its active set, and once controlled by the target RNC, the AT could not keep the source RN controlled only by the source RNC in its active set. Because of the lack of overlap in the active sets before and after handoff, a connection cannot be maintained.
In some examples, enhancements to the handoff methods in multi-homed networks allow an A16 handoff to be converted into a soft handoff, rather than a hard handoff. This allows more robust handoffs to take place between radio nodes that otherwise would be controlled by separate radio network controllers, requiring hard handoff, and for active calls to be handed off without being dropped.
To provide a multi-homed handoff, each RN associates a single traffic channel with the two (or more) RNCs that are controlling it. In some examples, one or two layers of RNs of each subnet, generally those near the boundary 220 between subnets 216 and 218, are secondarily homed to the RNC controlling the RNs on the other subnet, which will be the target RNC when an AT is handed off across the boundary. With the bordering RNs homed to both source and target RNCs, the AT is able to add the pilots signals of target RNs to its active set when it is located near a boundary, and to keep the source RNs in its active set during the handoff. The primary RNC knows that the AT is near the subnet boundary when the AT begins to report pilots from both RNs in the RouteUpdate message.
When the AT 212 is in transition range (e.g., near a subnet boundary 220, shown as position t1 in FIG. 2), all the RNs in the active set are homed to both RNCs 208 and 210, such that the active set is the same immediately before and after handoff between the two RNCs. Before the AT is in range (e.g., where the AT 212 is at position t0), its active set includes RNs of only the original serving RNC. After the AT moves past the transition range (e.g., where AT 212 is at position t2), as discussed below, the RNs of the original serving RNC 208 are removed, so that the active set includes RNs of only the target RNC 210. In both cases, the transition to and from the joint active set is done with standard soft handoff. While the active set is (RN1, RN2), the AT 212 may begin using the RN2 204. Thus, when the AT moves from the RN1 202 toward the RN2 204, with the RNC subnet boundary 220 between the two, the active set transitions as: (RN1)→(RN1, RN2)→(RN2). Because communication with at least one RN is preserved throughout the handoff, each handoff is soft and connectivity is maintained without interruption.
Handoff is triggered when a predetermined criterion is fulfilled. For example, as the AT 212 moves away from the first subnet 216, the strength of the pilot signal of the RN 202 will decrease until the RN is dropped form the AT's active set. The target RNC is then selected based on the strongest pilot in the AT's active set. When all the pilots in the AT's active set are only secondarily homed to the serving RNC, control of the AT, including any initiated connections, is transferred to the target RNC. Referring to FIG. 2 as an example, when the AT reaches position t2 and drops RN1 from its actives set, the only RN left in the active set is RN2, which is primarily homed to the target RNC2 210 and only secondarily homed to the source RNC1 208. By triggering handoff at this point, rather than waiting until the AT moves so far into the subnet 218 that the serving RNC 208 may not be homed to any RNs, both the serving RNC 208 and the target RNC 210 can access the RNs in the active set during handoff.
Delaying handoff until all RNs primarily homed to the source RNC are dropped from the active set helps prevent handoff ping-pong, where an AT that stays near the subnet border is continually handed off, back and forth between the two subnets. If the AT 212 moves back toward the subnet boundary 220, it will add the RN1 202 back into the active set, but it will not handoff back to the RNC 208 unless it moves so far into the subnet 216 that the RN2 204 is dropped. As long as the AT stays near the boundary 220, the active set will include RNs primarily homed to both RNCs and handoff will not take place. Delaying handoff also reduces the amount of A16 session transfer latency and the number of dropped calls, as the active set remains the same during the A16 handoff.
To facilitate this type of handoff, the target RN 204 sends its primary RNC's 210 address (e.g., an IP address if an IP backhaul network is used to connect the RNCs and RNs) to its secondary RNC 208. With this information, the serving (secondary to RN 204) RNC 208 can find the target (primary as to RN 204) RNC 210 automatically rather than through operator configuration.
Relevant elements of the flow of messaging and control to implement multihomed soft handoff is shown in FIG. 3. The A16 handoff is triggered 300 when RN1 is dropped from the AT's active set and the AT informs the source RNC1 about the change. The session configuration is locked 302 to avoid session configuration change in the middle of a handoff. Next, the source RNC1 sends 304 an A16 transfer request to the target RNC2. The RN2 associates 306 the existing traffic channel over which it serving the AT with the target RNC2. This will allow the active connection to be transferred to RNC2 without dropping. Once the traffic channel is associated with RNC2, RNC2 and RNC1 acknowledge completion of the transfer by sending 308 A16 transfer response and A16 transfer complete messages, respectively.
The RNC2 next sets up 310 an A10 connection to the PDSN and resets 312 the RLP flows with the AT. The former A10 connection from the RNC1 to the PDSN is torn down 314, and the target RNC2 assigns 316 a new Unicast Access Terminal Identifier (UATI) to the AT. A16 Release and Release acknowledge signals are exchanged 318 between the RNC1 208 and RNC2 210 to let the source RNC release the session. The session configuration is then unlocked 320. Some time later, the connection between the AT 212 and the target RN2 204 is closed 322 and A13 release request and response messages are exchanged 324 between the RNCs. The A13 release request is sent to the source RNC which requests that the source RNC release the UATI assigned by said source RNC, finally completing the handoff.
The techniques described herein can be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. The techniques can be implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device, for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. A computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.
Other embodiments are within the scope of the following claims and other claims to which the applicant may be entitled. The following are examples for illustration only and do not limit the alternatives in any way.
wherein the first and second radio network controllers are located in different subnets of the radio access network.
2. The method of claim 1 in which the the determination that the active set of the access terminal contains only radio nodes which are subordinately controllable by the first radio network controller is fulfilled when the first radio node is dropped from the active set of the access terminal.
3. The method of claim 2 in which the first radio node is dropped from the active set of the access terminal when a strength of a signal of the first radio node falls below a minimum threshold.
4. The method of claim 1 in which the determination that the active set of the access terminal contains only radio nodes which are subordinately controllable by the first radio network controller is fulfilled when a strength of a signal of the first radio node falls below a minimum threshold.
5. The method of claim 1 in which the connection uses the Ev-DO, CDMA2000, W-CDMA, HSUPA, HSDPA, HSPA, or LTE telecommunications standard.
6. The method of claim 1 in which the session uses voice over IP (VoIP) protocol.
7. The method of claim 1 in which the first radio node is also controlled by a third radio network controller.
8. The method of claim 1 in which the second radio network controller continues to control the session until a second predetermined criterion is fulfilled.
9. The method of claim 8 in which the session is transferred back to the first radio network controller from the second radio network controller after the second predetermined criterion is fulfilled, the second predetermined criterion being fulfilled when the active set of the access terminal contains only radio nodes that are both controlled subordinately by the second radio network controller and controlled primarily by the first radio network controller.
10. The method of claim 1 in which the second radio node sends an address of the second radio network controller to the first radio network controller.
wherein the first and second radio network controllers are located in different subnets of a radio access network.
the second radio network controller is configured to assume control of the session upon the fulfillment of a first predetermined criterion.
14. The system of claim 13 in which the first radio node is also controlled by a third radio network controller.
3rd Generation Partnership Project 2 "3GPP2", "cdma2000 High Rate Packet Data Interface Specification", C.S0024, version 2, Oct. 27, 2000, see pp. 113-153.
3rd Generation Partnership Project 2 "3GPP2", "cdma2000 High Rate Packet Data Interface Specification", C.S0024-B, version 2, Mar. 2007, see pp. 307-401.
Austrailian (AU) Examination Report for Application No. 2005426813, Jun. 4, 2009 (18 pages).
European Patent Office communication from European application No. 06785637.7 mailed Apr. 27, 2012 (2 pages).
European Search Report from European Application No. 06836082.5 mailed Apr. 26, 2013 (80 pages).
Examination Report from European Application No. 05750705.5 issued Mar. 11, 2013 (9 pages).
Final Action in U.S. Appl. No. 11/166,893, dated Mar. 25, 2010, 30 pages.
Final Office Action in U.S. Appl. No. 11/037,896, dated Jul. 10, 2008, 27 pages.
Final Office Action in U.S. Appl. No. 11/037,896, dated May 24, 2012, 29 pages.
Final Office Action in U.S. Appl. No. 11/037,896, dated Sep. 10, 2009, 29 pages.
Final Office Action in U.S. Appl. No. 11/166,893, dated Mar. 5, 2009, 26 pages.
Final Office Action in U.S. Appl. No. 11/167,785, dated Jan. 11, 2010, 11 pages.
Final Office Action in U.S. Appl. No. 11/167,785, dated Jul. 21, 2008, 10 pages.
Fish & Richardson P.C., Amendment in Reply to Action dated Apr. 17, 2009 in U.S. Appl. No. 11/402,744, filed Aug. 17, 2009, 12 pages.
Fish & Richardson P.C., Amendment in Reply to Action dated Apr. 2, 2008 in U.S. Appl. No. 11/303,773, filed Aug. 4, 2008, 19 pages.
Fish & Richardson P.C., Amendment in Reply to Action dated Apr. 4, 2008 in U.S. Appl. No. 11/303,774, filed Aug. 29, 2008, 13 pages.
Fish & Richardson P.C., Amendment in Reply to Action dated Aug. 19, 2009 in U.S. Appl. No. 11/486,545, filed Nov. 19, 2009, 24 pages.
Fish & Richardson P.C., Amendment in Reply to Action dated Dec. 30, 2009 in U.S. Appl. No. 11/305,286, filed Mar. 30, 2010, 31 pages.
Fish & Richardson P.C., Amendment in Reply to Action dated Jan. 12, 2009 in U.S. Appl. No. 11/243,405, filed Apr. 10, 2009, 14 pages.
Fish & Richardson P.C., Amendment in Reply to Action dated Jan. 29, 2010 in U.S. Appl. No. 11/486,545, filed Apr. 29, 2010, 19 pages.
Fish & Richardson P.C., Amendment in Reply to Action dated Jan. 30, 2008 in U.S. Appl. No. 11/243,405, filed May 30, 2008, 9 pages.
Fish & Richardson P.C., Amendment in Reply to Action dated Jun. 1, 2009 in U.S. Appl. No. 11/305,286, filed Sep. 30, 2009, 27 pages.
Fish & Richardson P.C., Amendment in Reply to Action dated Jun. 12, 2009 in U.S. Appl. No. 11/303,774, filed Aug. 13, 2009, 15 pages.
Fish & Richardson P.C., Amendment in Reply to Action dated Mar. 10, 2010 in U.S. Appl. No. 11/303,774, filed Jun. 10, 2010, 14 pages.
Fish & Richardson P.C., Amendment in Reply to Action dated Nov. 18, 2009 in U.S. Appl. No. 11/303,773, filed Feb. 18, 2010, 22 pages.
Fish & Richardson P.C., Amendment in Reply to Action dated Nov. 20, 2008 in U.S. Appl. No. 11/303,774, filed Mar. 19, 2009, 12 pages.
Fish & Richardson P.C., Amendment in Reply to Action dated Nov. 25, 2009 in U.S. Appl. No. 11/402,744, filed Feb. 25, 2010, 14 pages.
Fish & Richardson P.C., Amendment in Reply to Action dated Oct. 22, 2008 in U.S. Appl. No. 11/303,773, filed Feb. 23, 2009, 16 pages.
Fish & Richardson P.C., Amendment in Reply to Action dated Oct. 8, 2008 in U.S. Appl. No. 11/305,286, filed Feb. 27, 2009, 25 pages.
Fish & Richardson P.C., Amendment in Reply to Action dated Oct. 8, 2008 in U.S. Appl. No. 11/402,744, filed Jan. 8, 2009, 15 pages.
Fish & Richardson P.C., Amendment in Reply to Action dated Sep. 10, 2009 in U.S. Appl. No. 11/303,774, filed Dec. 10, 2009, 18 pages.
Fish & Richardson P.C., Notice of Appeal and Pre-Appeal Brief Request for Review in U.S. Appl. No. 11/243,405, filed Sep. 22, 2009, 6 pages.
Fish & Richardson P.C., Reply to Action dated Jul. 10, 2008 in U.S. Appl. No. 11/243,405, filed Dec. 10, 2008, 8 pages.
Fish & Richardson P.C., Reply to Action dated Mar. 11, 2010 in U.S. Appl. No. 11/303,773, filed Jun. 11, 2010, 23 pages.
Fish & Richardson P.C., Reply to Action dated Mar. 13, 2009 in U.S. Appl. No. 11/303,773, filed Aug. 13, 2009, 22 pages.
Fish & Richardson P.C., Supplemental Amendment in Reply to Action dated Aug. 19, 2009 in U.S. Appl. No. 11/486,545, filed Nov. 20, 2009, 24 pages.
Fish & Richardson, P.C., Amendment After Allowance in U.S. Appl. No. 12/857,206, filed Feb. 21, 2013, 10 pages.
Fish & Richardson, P.C., Amendment in Reply to Action dated Apr. 29, 2009 in U.S. Appl. No. 09/891,103, filed Jul. 29, 2009, 40 pages.
Fish & Richardson, P.C., Amendment in Reply to Action dated Aug 4, 2009 in U.S. Appl. No. 11/166,893, filed Dec. 1, 2009, 23 pages.
Fish & Richardson, P.C., Amendment in Reply to Action dated Aug. 5, 2008 in U.S. Appl. No. 11/166,893, filed Dec. 4, 2008, 22 pages.
Fish & Richardson, P.C., Amendment in reply to Action dated Feb. 5, 2009 in U.S. Appl. No. 11/037,896, dated May 5, 2009, 26 pages.
Fish & Richardson, P.C., Amendment in reply to Action dated Jan. 11, 2010 in U.S. Appl. No. 11/167,785, dated Apr. 12, 2010, 16 pages.
Fish & Richardson, P.C., Amendment in Reply to Action dated Jan. 28, 2005 in U.S. Appl. No. 09/891,103, filed Jul. 29, 2005, 28 pages.
Fish & Richardson, P.C., Amendment in Reply to Action dated Jan. 31, 2008 in U.S. Appl. No. 09/891,103, filed Jun. 30, 2008, 36 pages.
Fish & Richardson, P.C., Amendment in Reply to Action dated Jan. 31, 2008 in U.S. Appl. No. 09/891,103, filed May 12, 2008, 36 pages.
Fish & Richardson, P.C., Amendment in Reply to Action dated Jun. 11, 2007 in U.S. Appl. No. 09/891,103, filed Nov. 2, 2007, 32 pages.
Fish & Richardson, P.C., Amendment in reply to Action dated Jun. 16, 2010 in U.S. Appl. No. 11/037,896, dated Jun. 28, 2010, 21 pages.
Fish & Richardson, P.C., Amendment in reply to Action dated Jun. 22, 2009 in U.S. Appl. No. 11/167,785, dated Sep. 22, 2009, 18 pages.
Fish & Richardson, P.C., Amendment in reply to Action dated Mar. 25, 2010 in U.S. Appl. No. 11/166,893, dated Jun. 25, 2010, 19 pages.
Fish & Richardson, P.C., Amendment in Reply to Action dated Mar. 5, 2009 in U.S. Appl. No. 11/166,893, filed Apr. 24, 2009, 19 pages.
Fish & Richardson, P.C., Amendment in Reply to Action dated Mar. 5, 2009 in U.S. Appl. No. 11/166,893, filed Apr. 30, 2009, 21 pages.
Fish & Richardson, P.C., Amendment in Reply to Action dated May 17, 2006 in U.S. Appl. No. 09/891,103, filed Nov. 20, 2006, 30 pages.
Fish & Richardson, P.C., Amendment in reply to Action dated Nov. 15, 2007 in U.S. Appl. No. 11/167,785, dated Apr. 10, 2008, 14 pages.
Fish & Richardson, P.C., Amendment in Reply to Action dated Nov. 2, 2009 in U.S. Appl. No. 11/640,619, filed Mar. 2, 2010, 13 pages.
Fish & Richardson, P.C., Amendment in reply to Action dated Nov. 21, 2007 in U.S. Appl. No. 11/037,896, dated Feb. 21, 2008, 20 pages.
Fish & Richardson, P.C., Amendment in Reply to Action dated Nov. 3, 2005 in U.S. Appl. No. 09/891,103, filed Mar. 3, 2006, 24 pages.
Fish & Richardson, P.C., Amendment in reply to Action dated Sep. 10, 2009 in U.S. Appl. No. 11/037,896, dated Jan. 11, 2010, 26 pages.
Fish & Richardson, P.C., Amendment in Reply to Office Action dated Apr. 1, 2011 in U.S. Appl. No. 11/402,744, filed Jun. 30, 2011, 13 pages.
Fish & Richardson, P.C., Preliminary Amendment in U.S. Appl. No. 09/891,103, filed Aug. 1, 2004, 11 pages.
Fish & Richardson, P.C., Response to Final Office Action dated Dec. 6, 2012 in U.S. Appl. No. 11/167,785, filed Mar. 6, 2013, 13 pages.
Fish & Richardson, P.C., Response to Final Office Action dated May 24, 2012 in U.S. Appl. No. 12/857,206, filed Aug. 23, 2012, 17 pages.
Fish & Richardson, P.C., Response to Final Office Action dated Oct. 6, 2011 in U.S. Appl. No. 11/402,744, filed Jan. 6, 2012, 13 pages.
Fish & Richardson, P.C., Response to Non Final Office Action dated Dec. 7, 2012 in U.S. Appl. No. 13/430,422, filed Mar. 4, 2013, 9 pages.
Fish & Richardson, P.C., Response to Non Final Office Action dated Jun. 7, 2012 in U.S. Appl. No. 11/167,785, filed Sep. 6, 2012, 11 pages.
Fish & Richardson, P.C., Response to Non Final Office Action dated Oct. 20, 2011 in U.S. Appl. No. 12/857,206, filed Mar. 20, 2012, 19 pages.
Fish & Richardson, P.C., Response to Notice of Appeal Decision dated May 3, 2011 in U.S. Appl. No. 11/167,785, filed Nov. 3, 2011, 13 pages.
Fish & Richardson, P.C., Response to Notice of Panel Decision from Pre-Appeal Brief Review dated Feb. 23, 2012 in U.S. Appl. No. 11/402,744, filed May 23, 2012, 11 pages.
Fish & Richardson, P.C., Supplemental Amendment in Reply to Action dated Jan. 31, 2008 in U.S. Appl. No. 09/891,103, filed Jul. 10, 2008, 36 pages.
Fish & Richardson, P.C., Supplemental Amendment in Reply to Action dated Sep. 16, 2008 in U.S. Appl. No. 09/891,103, filed Jan. 14, 2009, 39 pages.
Goran Janevski, "IP—Based Mobile Wireless Access Network Architecture", Nortel Networks-MWIF Contribution, Draft dated Sep. 7, 2000.
International Search Report and Written Opinion mailed Apr. 26, 2007, in corresponding PCT application No. PCT/US2006/24958 (10 pages).
International Search Report and Written Opinion mailed Oct. 26, 2006, in corresponding PCT application No. PCT/US2005/17385 (14 pages).
International Search Report mailed Oct. 29, 2002, in corresponding PCT application No. PCT/US2002/020380 (5 pages).
Interview Summary in U.S. Appl. No. 11/166,893, dated Dec. 8, 2009, 3 pages.
Interview Summary in U.S. Appl. No. 11/640,619, dated Mar. 12, 2010, 3 pages.
Japanese Office action issued in application No. 2007-527408 on Nov. 11, 2011, mailed Nov. 16, 2011 (5 pages).
Library Search for Nortel and frequency handoff. Search results dated Aug. 28, 2009, see pp. 4, 7, 9, 11, 19, 25, 29, 32, 41, 45, 49, 52, 56-60, 65 and 70.
Non Final Office Action in U.S. Appl. No. 11/037,896, dated Feb. 5, 2009, 26 pages.
Non Final Office Action in U.S. Appl. No. 11/037,896, dated Nov. 21, 2007, 15 pages.
Non Final Office Action in U.S. Appl. No. 11/166,893, dated Aug. 4, 2009, 28 pages.
Non Final Office Action in U.S. Appl. No. 11/166,893, dated Aug. 5, 2008, 41 pages.
Non Final Office Action in U.S. Appl. No. 11/167,785, dated Apr. 28, 2010, 9 pages.
Non Final Office Action in U.S. Appl. No. 11/167,785, dated Jun. 22, 2009, 9 pages.
Non Final Office Action in U.S. Appl. No. 11/167,785, dated Nov. 15, 2007, 7 pages.
Non Final Office Action in U.S. Appl. No. 11/640,619, dated Jun. 18, 2010, 20 pages.
Non Final Office Action in U.S. Appl. No. 11/640,619, dated Nov. 2, 2009, 18 pages.
Notice of Allowance in U.S. Appl. No. 09/891,103, dated Feb. 17, 2010, 4 pages.
Notice of Allowance in U.S. Appl. No. 09/891,103, dated Jun. 14, 2010, 6 pages.
Notice of Allowance in U.S. Appl. No. 09/891,103, dated Nov. 10, 2009, 4 pages.
Notice of Allowance in U.S. Appl. No. 11/037,896, dated Feb. 22, 2010, 6 pages.
Notice of Allowance in U.S. Appl. No. 11/037,896, dated Jun. 16, 2010, 5 pages.
Notice of Allowance in U.S. Appl. No. 11/303,774, dated Apr. 4, 2011, 7 pages.
Notice of Allowance in U.S. Appl. No. 11/303,774, dated Aug. 31, 2010, 4 pages.
Office action and response history of U.S. Appl. No. 11/303,774 to Sep. 17, 2009.
Paul Bender & Ramin Rezalifar, "Draft Baseline Text for the 1×EV-DO Upper Layers (excluding Physical Layer)", 3GPP2, Aug. 17, 2000.
PCT application No. PCT/US2002/020380 filed on Jun. 25, 2002, with Publication No. WO2003/001820, including application as filed.
PCT application No. PCT/US2005/17385 filed on May 17, 2005, with Publication No. WO2005/115026, including application as filed.
PCT application No. PCT/US2006/025018 filed on Jun. 26, 2006, with Publication No. WO2007/044099, including application as filed.
PCT application No. PCT/US2006/24958 filed on Jun. 27, 2006, with Publication No. WO2007/002659, including application as filed.
PCT application No. PCT/US2006/47524 filed on Dec. 13, 2006, with Publication No. WO2007/078766, including application as filed.
PCT application No. PCT/US2006/47963 filed on Dec. 15, 2006, with Publication No. WO2007/075446, including application as filed.
Response filed Aug. 9, 2010 to GB Examination Report for Application No. 0811839.0, dated Jun. 3, 2010 (10 pages).
Response to European Patent Office communication from European application No. 06785637.7 mailed Apr. 27, 2012, filed Jun. 24, 2012, 3 pages.
Response to Japanese Office action issued in application No. 2007-527408 on Nov. 11, 2011, mailed Nov. 16, 2011, response filed May 16, 2012 (26 pages).
Supplemental Search Report from European Application No. 05750705.5 issued Aug. 2, 2012 (102 pages).
U.S. Appl. No. 09/891,103, filed Jun. 25, 2001, including application as filed.
U.S. Appl. No. 10/848,597, filed May 18, 2004, now U.S. Patent No. 7,170,871, issued Jan. 30, 2007, including application as filed.
U.S. Appl. No. 11/037,896, filed Jan. 18, 2005, including application as filed.
U.S. Appl. No. 11/167,785, filed Jun. 27, 2005, including application as filed.
U.S. Appl. No. 11/243,405, filed Oct. 4, 2005, including application as filed.
U.S. Appl. No. 11/303,773, filed Dec. 16, 2005, including application as filed.
U.S. Appl. No. 11/303,774, filed Dec. 16, 2005, including application as filed.
U.S. Appl. No. 11/305,286, filed Dec. 16, 2005, including application as filed.
U.S. Appl. No. 11/640,619, filed Dec. 18, 2006, including application as filed.
USPTO Advisory Action in U.S. Appl. No. 09/891,103, dated Jun. 5, 2008, 3 pages.
USPTO Advisory Action in U.S. Appl. No. 11/243,405, dated Apr. 23, 2009, 3 pages.
USPTO Advisory Action in U.S. Appl. No. 11/243,405, dated May 13, 2009, 3 pages.
USPTO Advisory Action in U.S. Appl. No. 11/486,545, dated May 7, 2010, 3 pages.
USPTO Final Office Action in U.S. Appl. No. 09/891,103, dated Jan. 31, 2008, 24 pages.
USPTO Final Office Action in U.S. Appl. No. 09/891,103, dated Nov. 3, 2005, 11 pages.
USPTO Final Office Action in U.S. Appl. No. 11/243,405, dated Feb. 12, 2009, 14 pages.
USPTO Final Office Action in U.S. Appl. No. 11/303,773, dated Nov. 18, 2009, 14 pages.
USPTO Final Office Action in U.S. Appl. No. 11/303,773, dated Oct. 22, 2008, 14 pages.
USPTO Final Office Action in U.S. Appl. No. 11/303,774, dated Jun. 12, 2009, 8 pages.
USPTO Final Office Action in U.S. Appl. No. 11/303,774, dated Mar. 10, 2010, 9 pages.
USPTO Final Office Action in U.S. Appl. No. 11/305,286, dated Jun. 1, 2009, 22 pages.
USPTO Final Office Action in U.S. Appl. No. 11/402,744, dated Nov. 25, 2009, 13 pages.
USPTO Final Office Action in U.S. Appl. No. 11/486,545, dated Jan. 29, 2010, 13 pages.
USPTO Interview Summary in U.S. Appl. No. 11/243,405, dated Nov. 5, 2009, 3 pages.
USPTO Interview Summary in U.S. Appl. No. 11/303,773, dated Feb. 26, 2009, 2 pages.
USPTO Non Final Office Action in U.S. Appl. No. 09/891,103, dated Apr. 29, 2009, 27 pages.
USPTO Non Final Office Action in U.S. Appl. No. 09/891,103, dated Jan. 28, 2005, 8 pages.
USPTO Non Final Office Action in U.S. Appl. No. 09/891,103, dated Jun. 11, 2007, 23 pages.
USPTO Non Final Office Action in U.S. Appl. No. 09/891,103, dated May 17, 2006, 10 pages.
USPTO Non Final Office Action in U.S. Appl. No. 09/891,103, dated Sep. 16, 2008, 26 pages.
USPTO Non Final Office Action in U.S. Appl. No. 11/167,785, dated Dec. 6, 2012, 9 pages.
USPTO Non Final Office Action in U.S. Appl. No. 13/430,422, dated Dec. 7, 2012, 6 pages.
USPTO Non-Final Office Action in U.S. Appl. No. 11/243,405, dated Jan. 30, 2008, 7 pages.
USPTO Non-Final Office Action in U.S. Appl. No. 11/243,405, dated Jul. 10, 2008, 13 pages.
USPTO Non-Final Office Action in U.S. Appl. No. 11/243,405, dated Jun. 22, 2009, 11 pages.
USPTO Non-Final Office Action in U.S. Appl. No. 11/303,773, dated Apr. 2, 2008, 11 pages.
USPTO Non-Final Office Action in U.S. Appl. No. 11/303,773, dated Mar. 11, 2010, 14 pages.
USPTO Non-Final Office Action in U.S. Appl. No. 11/303,773, dated Mar. 13, 2009, 14 pages.
USPTO Non-Final Office Action in U.S. Appl. No. 11/303,774, dated Apr. 4, 2008, 8 pages.
USPTO Non-Final Office Action in U.S. Appl. No. 11/303,774, dated Nov. 20, 2008, 8 pages.
USPTO Non-Final Office Action in U.S. Appl. No. 11/303,774, dated Sep. 10, 2009, 9 pages.
USPTO Non-Final Office Action in U.S. Appl. No. 11/305,286, dated Dec. 30, 2009, 27 pages.
USPTO Non-Final Office Action in U.S. Appl. No. 11/305,286, dated Oct. 8, 2008, 12 pages.
USPTO Non-Final Office Action in U.S. Appl. No. 11/402,744, dated Apr. 17, 2009, 14 pages.
USPTO Non-Final Office Action in U.S. Appl. No. 11/402,744, dated Mar. 30, 2010, 14 pages.
USPTO Non-Final Office Action in U.S. Appl. No. 11/402,744, dated Oct. 8, 2008, 14 pages.
USPTO Non-Final Office Action in U.S. Appl. No. 11/486,545, dated Aug. 19, 2009, 17 pages.
USPTO Notice of Allowance in U.S. Appl. No. 11/243,405, dated Jan. 6, 2010, 4 pages.
USPTO Notice of Allowance in U.S. Appl. No. 11/303,774, dated Aug. 31, 2010, 4 pages.
USPTO Notice of Appeal Decision in U.S. Appl. No. 11/167,785, dated May 3, 2011, 2 pages.
USPTO Notice of Panel Decision from Pre-Appeal Brief Review in U.S. Appl. No. 11/243,405, dated Oct. 22, 2009, 2 pages.

References: Application No. 2005426813
 application No. 06785637
 Application No. 06836082
 Application No. 05750705
 application No. 2007
 Application No. 0811839
 application No. 06785637
 application No. 2007
 Application No. 05750705