Radio network control

Information

  • Patent Grant
  • 8619702
  • Patent Number
    8,619,702
  • Date Filed
    Friday, December 16, 2005
    18 years ago
  • Date Issued
    Tuesday, December 31, 2013
    10 years ago
Abstract
The radio node controller of one subnet sends a communication to an access terminal over a control channel through the infrastructure of another subnet. The radio node controller maintains an open traffic channel with an access terminal when the access terminal moves from a coverage area of the first subnet to a coverage area of the second subnet and when the access terminal uses a carrier in the first subnet that cannot be used in the second subnet. In a radio access network including a first and a second subnet, in which the first subnet includes both a first radio node controller and radio nodes that are configured in accordance with one 1xEV-DO standard and the second subnet includes radio nodes configured in accordance with another 1xEV-DO standard, the first radio node controller maintains an open traffic channel with an access terminal when the access terminal moves from the coverage area of the first subnet to the coverage area of the second subnet.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related to U.S. application Ser. Nos. 11/037,896 filed on Jan. 18, 2005, 09/891,103, filed on Jun. 25, 2001, 10/848,597, filed on May 18, 2004, and 11/243,405, filed on Oct. 4, 2005, all of which are incorporated herein by reference.


This application is also related to U.S. application Ser. No. 11/303,773, titled “Radio Frequency Dragging Prevention,” and U.S. application Ser. No. 11/303,774, titled “Radio Network Communication,” being filed concurrently with the present application, which are also incorporated herein by reference.


TECHNICAL FIELD

This invention relates to radio network control.


BACKGROUND

High Data Rate (HDR) is an emerging mobile wireless access technology that enables personal broadband Internet services to be accessed anywhere, anytime (see P. Bender, et al., “CDMA/HDR: A Bandwidth-Efficient High-Speed Wireless Data Service for Nomadic Users”, IEEE Communications Magazine, July 2000, and 3GPP2, “Draft Baseline Text for 1xEV-DO,” Aug. 21, 2000). Developed by Qualcomm, HDR is an air interface optimized for Internet Protocol (IP) packet data services that can deliver a shared forward link transmission rate of up to 2.46 Mbit/s per sector using only (1×) 1.25 MHz of spectrum. Compatible with CDMA2000 radio access (TIA/EIA/IS-2001, “Interoperability Specification (IOS) for CDMA2000 Network Access Interfaces,” May 2000) and wireless IP network interfaces (TIA/EIA/TSB-115, “Wireless IP Architecture Based on IETF Protocols,” Jun. 6, 2000, and TLA/EIA/IS-835, “Wireless IP Network Standard,” 3rd Generation Partnership Project 2 (3GPP2), Version 1.0, Jul. 14, 2000), HDR networks can be built entirely on IP technologies, all the way from the mobile Access Terminal (AT) to the global Internet, thus taking advantage of the scalability, redundancy and low-cost of IP networks.


An EVolution of the current 1xRTT standard for high-speed data-only (DO) services, also known as the 1xEV-DO protocol has been standardized by the Telecommunication Industry Association (TIA) as TIA/EIA/IS-856, “CDMA2000 High Rate Packet Data Air Interface Specification”, 3GPP2 C.S0024-0, Version 4.0, Oct. 25, 2002, which is incorporated herein by reference. Revision A to this specification has been published as TIA/EIA/IS-856, “CDMA2000 High Rate Packet Data Air Interface Specification”, 3GPP2 C.S0024-A, Version 2.0, June 2005, but has yet not been adopted. Revision A is also incorporated herein by reference.



FIG. 1 shows a 1xEV-DO radio access network 100 with radio node controllers 102 and 104 connected to radio nodes 108, 110, 112, 114, 116, 118 over a packet network 122. The packet network 122 can be implemented as an IP-based network that supports many-to-many connectivity between the radio nodes and the radio node controllers. The packet network is connected to the Internet 124 via a packet data serving node (PDSN) 106. Other radio nodes, radio node controllers, and packet networks (not shown in FIG. 1) can be included in the radio access network. The packet network 122 may be several distinct networks connecting individual radio node controllers to their associated radio nodes, or it may be a single network as shown in FIG. 1, or a combination.


Typically, each radio node controller controls 25-100 radio nodes and each radio node supports 1-4 carriers each of 1.25 MHz of bandwidth. A carrier is a band of radio frequencies used to establish airlinks with access terminals. The geographic area of the radio access network that is served by any given radio node is referred to as a cell. Each cell can be divided into multiple sectors (typically 3 or 6) by using multiple sectorized antennas (the term “sector” is used both conventionally and in this document, however, even when there is only one sector per cell).


Access terminals 120 communicate with the network 100 over airlinks 126. Each access terminal may be a laptop computer, a Personal Digital Assistant (PDA), a dual-mode voice/data handset, or another device, with built-in 1xEV-DO Rev-0 or Rev-A support. The airlink 126 between the network 100 and an access terminal 120 includes a control channel over which a serving radio node controller (i.e., the radio node controller on which a 1xEV-DO session of the access terminal 120) transmits messages and parameters that the access terminal 120 may need for access and paging operations. The messages and parameters (collectively referred to in this description as “control channel messages”) convey system parameters, access parameters, neighbor lists, paging messages, and channel assignment information to the access terminal 120.


Access terminals 120 periodically send route update messages to the network 100. Each route update message identifies the sectors that are “visible” to the access terminal 120. The visible sectors may include sectors of radio nodes that are not controlled by the access terminal's serving radio node controller.


When a packet destined for an access terminal 120 is received at the serving radio node controller 102, the serving radio node controller 102 selects a set of sectors on which the access terminal 120 is to be paged, and sends a paging message to the selected sectors over respective control channels. One selection method known as “flood paging” involves selecting the sectors of all of the radio nodes that are controlled by the access terminal's serving radio node controller. Another selection method known as “selective paging” involves selecting only the visible sectors (or a subset of the visible sectors) of radio nodes that are controlled by the access terminal's serving radio node controller.


In a scenario in which the access terminal is located at or near the border of two sectors, both of which are visible to the access terminal but only sector A is controlled by the access terminal's serving radio node controller, the network is limited to sending paging messages, UATI_Assignment messages, and/or TrafficChannelAssignment messages to the access terminal over the control channel of the single sector A.


In a scenario in which an active access terminal crosses over the border between two sectors that are on different carriers and/or subnets, an inter-carrier and/or inter-subnet hard handoff is performed between the radio node controller's controlling the radio nodes associated with the two sectors. The user disruption associated with such hard handoffs are generally in the order of 5-10 seconds.


In both scenarios, lower success rates are generally associated with the activities (e.g., paging, UATI assignment, traffic channel assignment, and hard handoffs) that take place when an access terminal is located at or near a carrier and/or subnet boundary.


SUMMARY

In general, in one aspect, the radio node controller of one subnet sends a communication to an access terminal over a control channel through the infrastructure of another subnet. Implementations may include one or more of the following features: The communication comprises packets. The infrastructure includes a radio node controller. The access terminal is in an idle state. The communication sent over the control channel comprises a paging message, UATI_Assignment message, or TrafficChannelAssignment message. The access terminal notifies the radio node controller of sectors that are visible to the access terminal. The access terminal notifies the radio node controller of information about pilot strengths of sectors that are visible to the access terminal. The notification sent by the access terminal is sent as a route update message. The radio node controller determines, based on the pilot strengths, to which sectors to send a communication over the control channel to the access terminal. The radio node controller sends a communication to the access terminal over a control channel via sectors chosen based on their pilot signal strengths as reported by the access terminal, where at least one chosen sector is located in a different subnet than the radio node controller.


In general, in one aspect, the radio node controller maintains an open traffic channel with an access terminal when the access terminal moves from a coverage area of the first subnet to a coverage area of the second subnet and when the access terminal uses a carrier in the first subnet that cannot be used in the second subnet.


Implementations may include one or more of the following features: Each of the carriers comprises an operating frequency. The radio nodes in the first subnet are configured in accordance with one 1xEV-DO standard and radio nodes in the second subnet are configured in accordance with another 1xEV-DO standard. The radio nodes in the first subnet are configured in accordance with the 1xEV-DO Rev-A standard and radio nodes in the second subnet are configured in accordance with the 1xEV-DO Rev-0 standard.


In general, in one aspect, in a radio access network including a first and a second subnet, in which the first subnet includes both a first radio node controller and radio nodes that are configured in accordance with one 1EV-DO standard and the second subnet includes radio nodes configured in accordance with another 1xEV-DO standard, the first radio node controller maintains an open traffic channel with an access terminal when the access terminal moves from the coverage area of the first subnet to the coverage area of the second subnet.


Implementations may include the following feature: The radio nodes of the first subnet are configured in accordance with the 1xEV-DO Rev-A standard and the radio nodes of the second subnet are configured in accordance with the 1xEV-DO Rev-0 standard.


The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of the invention will be apparent from the description and drawings, and from the claims.





DESCRIPTION OF DRAWINGS


FIGS. 1-3 each show a radio access network.





DETAILED DESCRIPTION

In the illustrated example of FIG. 1, the network 100 is divided into two 1xEV-DO subnets, each having a radio node controller 102, 104 and three radio nodes 108-118.


Each radio node has a primary association with the radio node controller in its subnet and may have a secondary association with a radio node controller in another subnet. Generally, when a radio node has a primary association with a radio node controller, messages can be exchanged over the forward and reverse traffic channels, the control channel, and the access channel. When a radio node has a secondary association with a radio node controller, messages can only be exchanged over the forward and reverse traffic channels. That is, no messages are exchanged over the access and control channels. Additional information concerning the primary and secondary associations between radio nodes and radio node controllers are described in U.S. application Ser. No. 11/037,896 filed on Jan. 18, 2005, Ser. No. 09/891,103, filed on Jun. 25, 2001, and Ser. No. 10/848,597, filed on May 18, 2004, and incorporated by reference.


In some implementations, the network operator further configures the radio node controllers to have a border association with certain radio nodes in another subnet. Typically, the radio nodes with which a radio node controller has a border association are geographically located at or near the subnet boundaries. The border association concept extends the secondary association concept by enabling a radio node controller to exchange messages over the control channel with radio nodes of another subnet without passing through another radio node controller.


As an example, suppose the network operator configures the radio node controller RNC-1102 to have a primary association with the radio nodes RN-1108, RN-2110, RN-3112, and a border association with the radio node RN-4114. An idle access terminal moving within the coverage areas of the radio nodes RN-1, RN-2, RN-3 sends route update messages to the radio node controller RNC-1 to identify the sectors that are visible to the access terminal 120, and for each visible sector, its associated pilot strength. In instances in which the idle access terminal is in the coverage area of the radio node RN-3, the last sent route update message will likely identify, as visible, one or more sectors associated with the radio node RN-4. The sector identification and the relative pilot strengths enable the radio access network to keep track of the access terminal's approximate location within the footprint of the network.


When a packet destined for the idle access terminal 120 is received at the radio node controller RNC-1, the radio node controller RNC-1 uses the last sent route update message to select a set of sectors on which the idle access terminal 120 is to be paged. In some implementations, the radio node controller RNC-1 sends a paging message to the idle access terminal 120 over the control channel of each of the radio nodes with visible sectors. In some implementations, the radio node controller RNC-1 examines the pilot strengths of the visible sectors, identifies those visible sectors associated with the relatively stronger pilot strengths, and sends a paging message to the idle access terminal 120 over the control channel of each of the radio nodes with the identified visible sectors.


In those instances in which the selected set of sectors includes sectors of the radio node RN-4 with which the radio node controller RNC-1 has a border association 130 relationship, a paging message can be sent from the radio node controller RNC-1 to the radio node RN-4 over the control channel. By enabling the idle access terminal 120 to be paged on the sectors associated with the radio node RN-4 as well as those associated with the radio node RN-3, the radio node controller RNC-1 increases the likelihood of receiving a page response from the access terminal 120. In so doing, the network enhances paging reachability for access terminals located at or near the subnet border, which in turn results in a higher page response success rate.


In other examples, rather than sending a paging message only to those sectors identified as visible in the last sent route update message, the radio node controller RNC-1 can be implemented to select a subset of the sectors of its subnet or adjoining subnet in accordance with the distance-based selective techniques described in U.S. application Ser. No. 11/243,405 filed on Oct. 4, 2005, and incorporated by reference, and send the paging message over the control channel of each of the radio nodes associated with the selected subset of sectors.


In other examples, rather than use the last sent route update message to select a set of sectors on which the idle access terminal 120 is to be paged, the radio node controller RNC-1 can be implemented to send a paging message over the control channel of each of the radio nodes with which the radio node controller RNC-1 has a border association. Such a subnet-wide paging technique also enhances the page response success rate for access terminals located at or near the subnet border.


In addition to enhancing paging reachability, the border association concept can be implemented to enhance control channel messaging reliability overall. As an example, an access terminal 120 in the coverage area of the radio node RN-3 can send a UATI_Request or a ConnectionRequest message over access channels of the radio node RN-3. Typically, the UATI_Request or ConnectionRequest message is accompanied by a route update message, which may include, as visible, the sectors of the radio node RN-4 if the access terminal is at or near the subnet boundary. The messages are forwarded by the radio node RN-3 to the radio node controller RNC-1, which processes the request and generates a UATI_Assignment or TrafficChannelAssignment message as appropriate. The radio node controller RNC-1 then sends the UATI_Assignment or TrafficChannelAssignment message to the access terminal over the control channel of each of the visible sectors including those of the radio node RN-4. In those instances in which the access terminal is at or near the subnet boundary, delivery of the UATI_Assignment or TrafficChannelAssignment message over the control channels of the sectors of the radio node RN-4 increases the likelihood of the access terminal receiving the message, thus enabling the network to achieve a higher A13 dormant handoff or connection setup success rate.


In some implementations, the radio node controllers of the 1EV-DO network 100 of FIG. 1 support multi-carrier sectors. FIG. 2 shows a network coverage area with two carriers C1 and C2, where C1 operates in the sectors S1-S8 of both subnets 1 and 2, and C2 operates only in the sectors S1-S4 of subnet 1. In some implementations, the radio node controllers of the 1xEV-DO network 100 of FIG. 1 support multi-carrier, multi-revision sectors. FIG. 3 shows a network coverage area with two carriers C1 and C2, where C1 operates in the sectors S1-S8 of both subnets 1 and 2, and C2 operates only in the sectors S1-S4 of subnet 1. The sectors S1-S4 of subnet 1 are served by Rev-A capable radio nodes, and the sectors S5-S8 of subnet 2 are served by Rev-0 capable radio nodes. As 1xEvDO Rev-A is backwards compatible with 1xEvDO Rev-0, Rev-A capable access terminals can operate in either Rev-0 mode or Rev-A mode, depending on whether its serving radio node is Rev-0 or Rev-A capable.


Referring to FIGS. 1, 2 and 3, during network design, the network operator designates the sectors (in this case, sectors S4 and S5) at the subnet boundary as border sectors, configures the radio node RN-2110 and RN-3112 (which collectively serve the sectors S1-S4) to have a primary association with the radio node controller RNC-1102 of subnet 1, and configures the radio node RN-4114 (which serves sector S5) to have a secondary association with the radio node controller RNC-1102 of subnet 1.


As an active access terminal 120 operating on carrier C2 moves within the coverage area of the subnet 1, the access terminal 120 periodically sends route update messages to the serving radio node controller RNC-1102 to identify the sectors that are visible to the access terminal 120. For each visible sector, the access terminal 120 provides its associated pilot strength. When serving radio node controller RNC-1102 detects that the pilot strength associated with the border sector S5 is stronger than the other pilot strengths being reported, the serving radio node controller RNC-1102 sends a TrafficChannelAssignment message to the access terminal 120. Upon receipt of the message, the access terminal 120 processes the TrafficChannelAssignment message to change the carrier on which it operates to the carrier specified in the TrafficChannelAssignment message. In this case, the access terminal will operate on carrier C1 after the TrafficChannelAssignment message is processed. If the access terminal has any data to send, the access terminal will send it through RNC-1 on carrier C1. This can be done with no interruption in service for the access terminal.


In another implementation, a Connection Close message and a Unicast Redirect message can be used in place of the TrafficChannelAssignment message. When serving radio node controller RNC-1102 detects that the pilot strength associated with the border sector S5 is stronger than the other pilot strengths being reported, the serving radio node controller RNC-1102 sends a Connection Close message and a Unicast Redirect message to the access terminal 120. Upon receipt of the message, the access terminal 120 first processes the Connection Close message to close the connection, and then processes the Unicast Redirect message to change the carrier on which it operates to the carrier specified in the Unicast Redirect message. In this case, the access terminal will operate on carrier C1 after the Unicast Redirect message is processed. If the access terminal has any data to send, the access terminal will initiate another connection request on the carrier C1 and the serving radio node controller RNC-1 will establish an active traffic channel by allocating traffic channel resources on the carrier C1. The user disruption associated with the “close connection-switch carrier-open connection” process typically averages about 1 second long.


If the active access terminal crosses the subnet boundary into the coverage area of the sector S5, the secondary association established between the radio node RN-4114 (which serves the sector S5) and the radio node controller RNC-1102 enables the user activity (e.g., phone call, data transfer) to continue uninterrupted as the radio node controller RNC-1102 remains the serving radio node controller for the traffic channel operating on the carrier C1.


If the access terminal 120 moves back into the coverage area of the sector S4 of the subnet 1, the access terminal 120 will continue to operate on the carrier C1. If, however, the access terminal 120 moves further into subnet 2, for example, into the coverage area of the sector S5 which the radio node controller RNC-1102 has no relationship with and therefore no control over, a hard handoff between the radio node controllers RNC-1102 and RNC-2104 is triggered.


The techniques described with reference to FIGS. 2 and 3 improve network reliability by minimizing the number of dropped data connections that may occur when an active access terminal crosses over a subnet boundary into a coverage area of a sector operating on a different carrier and/or 1xEV-DO revision. Further, the techniques reduce the number of hard handoffs that are performed by the network by limiting those hard handoff instances to scenarios in which the access terminal has moved deep into the coverage area of a subnet (i.e., not at or near the subnet boundary). In so doing, network resources that would be tied up with the hard handoffs are made available for use by other components of the network.


Although the techniques described above employ the 1xEV-DO air interface standard, the techniques are also applicable to other CDMA and non-CDMA air interface technologies in which secondary associations and border associations can be established between radio nodes and radio node controllers.


The techniques described above 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 or in a propagated signal, 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.


Method steps of the techniques described herein can be performed by one or more programmable processors executing a computer program to perform functions of the invention by operating on input data and generating output. Method steps can also be performed by, and apparatus of the invention can be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). Modules can refer to portions of the computer program and/or the processor/special circuitry that implements that functionality.


Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in special purpose logic circuitry.


A number of embodiments of the invention have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the invention, and, accordingly, other embodiments are within the scope of the following claims.

Claims
  • 1. A method performed in a first radio network controller of a first subnet of a radio access network, the method comprising: establishing a border association between the first radio network controller and a radio node of a second subnet, the border association being established based at least in part on a proximity of the radio node to a subnet boundary between the first subnet and the second subnet; andafter the border association has been established, sending a communication to an access terminal over a control channel through the radio node of the second subnet without the communication passing through any radio network controller of the second subnet.
  • 2. The method of claim 1, wherein the communication comprises packets.
  • 3. The method of claim 1, further comprising: configuring the first radio network controller to have a border association with at least one radio node of the second subnet, the at least one radio node comprising the radio node.
  • 4. The method of claim 1, wherein the access terminal is in an idle state at least during the communication.
  • 5. The method of claim 1, wherein the communication sent over the control channel comprises a paging message.
  • 6. The method of claim 1, wherein the communication sent over the control channel comprises a UATI_Assignment message.
  • 7. The method of claim 1, wherein the communication sent over the control channel comprises a TrafficChannelAssignment message.
  • 8. The method of claim 1, further comprising: receiving a notification from the access terminal at the first radio network controller, the notification comprising information identifying sectors that are visible to the access terminal.
  • 9. The method of claim 8, wherein the notification comprises a route update message.
  • 10. The method of claim 1, further comprising: receiving a notification from the access terminal at the first radio network controller, the notification comprising information about pilot strengths of sectors that are visible to the access terminal.
  • 11. The method of claim 10, further comprising: determining, based on the pilot strengths, at least one sector to send the communication over the control channel to the access terminal.
  • 12. A method performed in a first radio network controller of a first subnet of a radio access network, the method comprising: establishing a border association between the first radio network controller and at least one sector of a radio node of a second subnet, the border association being established based at least in part on a proximity of the radio node to a subnet boundary between the first subnet and the second subnet;receiving a notification from an access terminal, the notification comprising information about pilot strengths of sectors that are visible to the access terminal;selecting one or more of the sectors based on the information about the pilot strengths, wherein a first sector of the one or more sectors is located in the second subnet of the radio access network and has a border association with the first radio network controller; andafter the border association has been established, sending a communication to the access terminal over a control channel through the first sector without the communication passing through any radio network controller of the second subnet.
  • 13. A method performed at a first radio network controller of a first subnet of a radio access network, comprising: establishing a border association between the first radio network controller and a radio node of a second subnet, the border association being established based at least in part on a proximity of the radio node to a subnet boundary between the first subnet and the second subnet; andafter the border association has been established, maintaining an open traffic channel with an access terminal when the access terminal moves from a coverage area of the first subnet to a coverage area of the radio node of the second subnet of the radio access network;wherein the access terminal initially uses a first carrier in the first subnet that cannot be used in the second subnet.
  • 14. The method of claim 13, wherein the first carrier comprises an operating frequency; and wherein the first carrier operates in the first subnet and a second carrier operates in the first and second subnets.
  • 15. The method of claim 13, wherein radio nodes of the first subnet are configured in accordance with a first 1xEV-DO standard and radio nodes of the second subnet are configured in accordance with a second 1xEV-DO standard.
  • 16. The method of claim 15, wherein the first 1xEV-DO standard comprises the 1xEV-DO Rev-A standard and the second 1xEV-DO standard comprises the 1xEV-DO Rev-0 standard.
  • 17. A method, comprising: establishing a border association between the first radio network controller and a radio node of a second subnet, the border association being established based at least in part on a proximity of the radio node to a subnet boundary between the first subnet and the second subnet; andafter the border association has been established, maintaining, at a first radio network controller of a first subnet of a radio access network, an open traffic channel with an access terminal when the access terminal moves from a coverage area of the first subnet to a coverage area of a second subnet of the radio access network;wherein the first subnet comprises radio nodes that are configured in accordance with a first 1xEV-DO standard and the second subnet comprises radio nodes that are configured in accordance with a second 1xEV-DO standard.
  • 18. The method of claim 17, wherein the first 1xEV-DO standard comprises the 1xEV-DO Rev-A standard and the second 1xEV-DO standard comprises the 1xEV-DO Rev-0 standard.
  • 19. A radio network controller configured to operate in a first subnet of a radio access network, the radio network controller comprising: a processor; andmemory for storing instructions that are executable by the processor to: establish a border association between the radio network controller and a radio node of a second subnet, the border association being established based at least in part on a proximity of the radio node to a subnet boundary between the first subnet and the second subnet; andafter the border association has been established, send a communication, from the radio network controller of the first subnet of the radio access network, to an access terminal over a control channel through the second subnet of the radio access network without the communication passing through any radio network controller of the second subnet.
  • 20. The radio network controller of claim 19, wherein the instructions comprise instructions that are executable by the processor to: receive a notification from the access terminal, the notification comprising information identifying sectors that are visible to the access terminal.
  • 21. The radio network controller of claim 19, wherein the instructions comprise instructions that are executable by the processor to: receive a notification from the access terminal, the notification comprising information about pilot strengths of sectors that are visible to the access terminal.
  • 22. The radio network controller of claim 21, wherein the instructions comprise instructions that are executable by the processor to: determine, based on the pilot strengths, at least one sector to send the communication over the control channel to the access terminal.
  • 23. A radio network controller configured to operate in a first subnet of a radio access network, the radio network controller comprising: a processor; andmemory for storing instructions that are executable by the processor to: establish a border association between the first radio network controller and at least one sector of a radio node of a second subnet, the border association being established based at least in part on a proximity of the radio node to a subnet boundary between the first subnet and the second subnet;receive a notification from an access terminal at the first radio network controller of a first subnet of a radio access network, the notification comprising information about pilot strengths of sectors that are visible to the access terminal;select one or more of the sectors based on the information about the pilot strengths, wherein a first sector of the one or more sectors is located in the second subnet of the radio access network and has a border association with the first radio network controller; andafter the border association has been established, send a communication to the access terminal over a control channel through the first sector without the communication passing through any radio network controller of the second subnet.
  • 24. A radio network controller configured to operate in a first subnet of a radio access network, the radio network controller comprising: means for establishing a border association between the radio network controller and a radio node of a second subnet, the border association being established based at least in part on a proximity of the radio node to a subnet boundary between the first subnet and the second subnet; andmeans for sending a communication, after the border association has been established, from the radio network controller of the first subnet, to an access terminal over a control channel through the radio node of the second subnet without the communication passing through any radio network controller of the second subnet.
  • 25. The radio network controller of claim 24, further comprising: means for receiving a notification from the access terminal, the notification comprising information identifying sectors that are visible to the access terminal.
  • 26. The radio network controller of claim 24, further comprising: means for receiving a notification from the access terminal, the notification comprising information about pilot strengths of sectors that are visible to the access terminal.
  • 27. The radio network controller of claim 26, further comprising: means for determining, based on the pilot strengths, at least one sector to send the communication over the control channel to the access terminal.
  • 28. A radio network controller configured to operate in a first subnet of a radio access network, the radio network controller comprising: means for establishing a border association between the first radio network controller and at least one sector of a radio node of a second subnet, the border association being established based at least in part on a proximity of the radio node to a subnet boundary between the first subnet and the second subnet;means for receiving a notification from an access terminal at the first radio network controller of a first subnet of a radio access network, the notification comprising information about pilot strengths of sectors that are visible to the access terminal;means for selecting one or more of the sectors based on the information about the pilot strengths, wherein a first sector of the one or more sectors is located in the second subnet of the radio access network and has a border association with the first radio network controller; andmeans for sending, after the border association has been established, a communication to the access terminal over a control channel through the first sector without the communication passing through any radio network controller of the second subnet.
  • 29. A system, comprising: a first subnet of a radio access network and a second subnet of a radio access network, the first subnet comprising: a first radio network controller configured to: establish a border association between the radio network controller and a radio node of a second subnet, the border association being established based at least in part on a proximity of the radio node to a subnet boundary between the first subnet and the second subnet; andafter the border association has been established, send a communication, from the radio network controller of the first subnet of the radio access network, to an access terminal over a control channel through the second subnet of the radio access network without the communication passing through any radio network controller of the second subnet.
  • 30. The system of claim 29, wherein the first radio network controller is configured to receive a notification from the access terminal, the notification comprising information identifying sectors that are visible to the access terminal.
  • 31. The system of claim 29, wherein the first radio network controller is configured to receive a notification from the access terminal, the notification comprising information about pilot strengths of sectors that are visible to the access terminal.
  • 32. The system of claim 31, wherein the first radio network controller is configured to determine, based on the pilot strength, at least one sector to send the communication over the control channel to the access terminal.
  • 33. The system of claim 29, further comprising: a packet data serving node connected to a network, wherein the first radio network controller is connected to the packet data serving node, and wherein the at least one radio node is connected to the first radio network controller.
  • 34. The system of claim 29, further comprising: the second subnet of the radio access network, comprising: the radio node, the radio node being configured to communicate with a second radio network controller; andthe second radio network controller, wherein the second radio network controller is configured to send a second communication to a second access terminal over a second control channel through a second radio node of the at least one radio node of the first subnet of the radio access network without the communication passing through any radio network controller of the first subnet.
  • 35. A system, comprising: a first subnet of a radio access network and a second subnet of the radio access network, the first subnet comprising: a first radio network controller configured to: establish a border association between the first radio network controller and at least one sector of a radio node of a second subnet, the border association being established based at least in part on a proximity of the radio node to a subnet boundary between the first subnet and the second subnet;receive a notification from an access terminal at the first radio network controller, the notification comprising information about pilot strengths of sectors that are visible to the access terminal;select one or more of the sectors based on the information about the pilot strengths, wherein a first sector of the one or more sectors is located in the second subnet of the radio access network and has a border association with the first radio network controller; andafter the border association has been established, send a communication to the access terminal over a control channel the first sector without the communication passing through any radio network controller of the second subnet.
  • 36. A radio network controller configured to operated in a first subnet of a radio access network, the radio network controller comprising: a processor; andmemory for storing instructions that are executable by the processor to: establish a border association between the first radio network controller and a radio node of a second subnet, the border association being established based at least in part on a proximity of the radio node to a subnet boundary between the first subnet and the second subnet; andafter the border association has been established, maintain, at the radio network controller of a first subnet of a radio access network, an open traffic channel with an access terminal when the access terminal moves from a coverage area of the first subnet to a coverage area of the radio node of the second subnet of the radio access network;wherein the access terminal initially uses a first carrier in the first subnet that cannot be used in the second subnet.
  • 37. The radio network controller of claim 36, wherein the first carrier comprises an operating frequency; and wherein the first carrier operates in the first subnet and a second carrier operates in the first and second subnets.
  • 38. The radio network controller of claim 36, wherein radio nodes of the first subnet are configured in accordance with a first 1xEV-DO standard and radio nodes of the second subnet are configured in accordance with a second 1xEV-DO standard.
  • 39. The radio network controller of claim 38, wherein the first 1xEV-DO standard comprises the 1xEV-DO Rev-A standard and the second 1xEV-DO standard comprises the 1xEV-DO Rev-0 standard.
  • 40. A radio network controller configured to operate in a first subnet of a radio access network, the radio network controller comprising: means for establishing a border association between the first radio network controller and a radio node of a second subnet, the border association being established based at least in part on a proximity of the radio node to a subnet boundary between the first subnet and the second subnet; andmeans for maintaining, at the radio network controller after the border association has been established, an open traffic channel with an access terminal when the access terminal moves from a coverage area of the first subnet to a coverage area of the radio node of the second subnet of the radio access network;wherein the access terminal initially uses a first carrier in the first subnet that cannot be used in the second subnet.
  • 41. The radio network controller of claim 40, wherein the first carrier comprises an operating frequency; and wherein the first carrier operates in the first subnet and a second carrier operates in the first and second subnets.
  • 42. The radio network controller of claim 40, wherein radio nodes of the first subnet are configured in accordance with a first 1xEV-DO standard and radio nodes of the second subnet are configured in accordance with a second 1xEV-DO standard.
  • 43. The radio network controller of claim 42, wherein the first 1xEV-DO standard comprises the 1xEV-DO Rev-A standard and the second 1xEV-DO standard comprises the 1xEV-DO Rev-0 standard.
  • 44. A system, comprising: a first subnet of a radio access network, comprising:a first radio network controller, wherein the first radio network controller is configured to: establish a border association between the first radio network controller and a radio node of a second subnet, the border association being established based at least in part on a proximity of the radio node to a subnet boundary between the first subnet and the second subnet; andafter the border association has been established, maintain an open traffic channel with an access terminal when the access terminal moves from a coverage area of the first subnet to a coverage area of the radio rode of the second subnet of the radio access network;wherein the access terminal initially uses a first carrier in the first subnet that cannot be used in the second subnet.
  • 45. The system of claim 44, wherein the first carrier comprises an operating frequency; and wherein the first carrier operates in the first subnet and a second carrier operates in the first and second subnets.
  • 46. The system of claim 44, wherein radio nodes of the first subnet are configured in accordance with a first 1xEV-DO standard and radio nodes of the second subnet are configured in accordance with a second 1xEV-DO standard.
  • 47. The system of claim 46, wherein the first 1xEV-DO standard comprises the 1xEV-DO Rev-A standard and the second 1xEV-DO standard comprises the 1xEV-DO Rev-0 standard.
  • 48. The system of claim 44, further comprising: a packet data serving node connected to a network, wherein the first radio network controller is connected to the packet data serving node; andwherein the first subnet further comprises:at least one radio node configured to communicate with the first radio network controller, wherein the at least one radio node is connected to the first radio network controller.
  • 49. A radio network controller configured to operate in a first subnet of a radio access network, the radio network controller comprising: a processor; andmemory for storing instructions that are executable by the processor to: establish a border association with a radio node of a second subnet, the border association being established based at least in part on a proximity of the radio node to a subnet boundary between the first subnet and the second subnet; andafter the border association has been established, maintain, at the radio network controller, an open traffic channel with an access terminal when the access terminal moves from a coverage area of the first subnet to a coverage area of the radio node of the second subnet of the radio access network;wherein the first subnet comprises radio nodes that are configured in accordance with a first 1xEV-DO standard and the second subnet comprises radio nodes that are configured in accordance with a second 1xEV-DO standard.
  • 50. The radio network controller of claim 49, wherein the first 1xEV-DO standard comprises the 1xEV-DO Rev-A standard and the second 1xEV-DO standard comprises the 1xEV-DO Rev-0 standard.
  • 51. A radio network controller configured to operated in a first subnet of a radio access network, the radio network controller comprising: means for establishing a border association between the first radio network controller and a radio node of a second subnet, the border association being established based at least in part on a proximity of the radio node to a subnet boundary between the first subnet and the second subnet; andmeans for maintaining, after the border association has been established, an open traffic channel with an access terminal when the access terminal moves from a coverage area of the first subnet to a coverage area of the radio node of the second subnet of the radio access network;wherein the first subnet comprises radio nodes that are configured in accordance with a first 1xEV-DO standard and the second subnet comprises radio nodes that are configured in accordance with a second 1xEV-DO standard.
  • 52. The radio network controller of claim 51, wherein the first 1xEV-DO standard comprises the 1xEV-DO Rev-A standard and the second 1xEV-DO standard comprises the 1xEV-DO Rev-0 standard.
  • 53. A system, comprising: a first subnet of a radio access network, comprising: radio nodes, wherein at least one radio node of the radio nodes is configured to communicate with a first radio network controller; andthe first radio network controller, wherein the first radio network controller is configured to: establish a border association between the first radio network controller and at least one sector of a radio node of a second subnet, the border association being established based at least in part on a proximity of the radio node to a subnet boundary between the first subnet and the second subnet; andafter the border association has been established, maintain an open traffic channel with an access terminal when the access terminal moves from a coverage area of the first subnet to a coverage area of the radio node of the second subnet of the radio access network;wherein the radio nodes of the first subnet comprise at least some radio nodes that are configured in accordance with a first 1xEV-DO standard and the second subnet comprises radio nodes that are configured in accordance with a second 1xEV-DO standard.
  • 54. The system of claim 53, wherein the first 1xEV-DO standard comprises the 1xEV-DO Rev-A standard and the second 1xEV-DO standard comprises the 1xEV-DO Rev-0 standard.
  • 55. A method performed in a radio access network including a first and a second subnet, in which the first subnet includes a first radio network controller, and in which radio nodes in the first subnet are configured in accordance with one 1xEV-DO standard that comprises the 1xEV-DO Rev-A standard, and radio nodes in the second subnet are configured in accordance with another 1xEV-DO standard that comprises the 1xEV-DO Rev-0 standard, the method comprising; establishing a border association between the first radio network controller and at least one border radio node of a second subnet, the border association being established based at least in part on a proximity of the border radio node to a subnet boundary between the first subnet and the second subnet; andafter the border association has been established, enabling the first radio network controller to maintain an open traffic channel with an access terminal when the access terminal moves from a coverage area of the first subnet to a coverage area of the border radio node of the second subnet;wherein the access terminal uses a carrier in the first subnet that cannot be used in the second subnet.
  • 56. A method performed in a radio access network including a first and a second subnet, in which the first subnet includes both a first radio network controller and radio nodes that are configured in accordance with one 1xEV-DO standard that comprises the 1xEV-DO Rev-A standard, and the second subnet includes radio nodes configured in accordance with another 1xEV-DO standard that comprises the 1xEV-DO Rev-0 standard, the method comprising: establishing a border association between the first radio network controller and at least one border radio node of a second subnet, the border association being established based at least in part on a proximity of the border radio node to a subnet boundary between the first subnet and the second subnet; andafter the border association has been established, enabling the first radio network controller to maintain an open traffic channel with an access terminal when the access terminal moves from the coverage area of the first subnet to the coverage area of the border radio node of the second subnet.
  • 57. A radio network controller configured to operate in a first subnet of a radio access network, the radio network controller comprising: means for establishing a border association between the radio network controller and a radio node of a second subnet, the border association being established based at least in part on a proximity of the radio node to a subnet boundary between the first subnet and the second subnet; andmeans for maintaining, after the border association has been established, an open traffic channel with an access terminal when the access terminal moves from a coverage area of a first subnet to a coverage area of the radio node of the second subnet;wherein radio nodes in the first subnet are configured in accordance with a 1xEV-DO standard that comprises the 1xEV-DO Rev-A standard, and radio nodes in the second subnet are configured in accordance with another 1xEV-DO standard that comprises the 1xEV-DO Rev. 0 standard.
  • 58. A system comprising, a packet data serving node connected to a network;at least two subnets, each subnet comprising: at least one radio network controller connected to the packet data serving node; andat least one radio node connected to a radio network controller in the same subnet;wherein a first radio network controller located in a first subnet is configured to: establish a border association between the first radio network controller and a border radio node of a second subnet, the border association being established based at least in part on a proximity of the border radio node to a subnet boundary between the first subnet and the second subnet; andmaintain, after the border association has been established, an open traffic channel with an access terminal when the access terminal moves from a coverage area of a first subnet to a coverage area of the border radio node of the second subnet;wherein radio nodes in the first subnet are configured in accordance with a 1xEV-DO standard that comprises the 1xEV-DO Rev-A standard, and radio nodes in the second subnet are configured in accordance with another 1xEV-DO standard that comprises the 1xEV-DO Rev. 0 standard.
US Referenced Citations (297)
Number Name Date Kind
5128938 Borras Jul 1992 A
5239675 Dudczak Aug 1993 A
5377224 Hudson Dec 1994 A
5574996 Raith Nov 1996 A
5754945 Lin et al. May 1998 A
5790528 Muszynski Aug 1998 A
5815813 Faruque Sep 1998 A
5828661 Weaver et al. Oct 1998 A
5852630 Langberg et al. Dec 1998 A
5857154 Laborde et al. Jan 1999 A
5884177 Hanley Mar 1999 A
5930714 Abu-Amara et al. Jul 1999 A
5937345 McGowan et al. Aug 1999 A
5940762 Lee et al. Aug 1999 A
5960349 Chheda Sep 1999 A
5974318 Satarasinghe Oct 1999 A
5983282 Yucebay Nov 1999 A
5991635 Dent et al. Nov 1999 A
6011970 McCarthy Jan 2000 A
6014564 Donis et al. Jan 2000 A
6016429 Khafizov et al. Jan 2000 A
6023625 Myers Feb 2000 A
6032033 Morris et al. Feb 2000 A
6047186 Yu et al. Apr 2000 A
6049715 Willhoff et al. Apr 2000 A
6052594 Chuang et al. Apr 2000 A
6061560 Saboorian et al. May 2000 A
6069871 Sharma et al. May 2000 A
6091953 Ho et al. Jul 2000 A
6101394 Illidge Aug 2000 A
6111857 Soliman et al. Aug 2000 A
6112089 Satarasinghe Aug 2000 A
6119024 Takayama Sep 2000 A
6122513 Bassirat Sep 2000 A
6151512 Chheda et al. Nov 2000 A
6167036 Beven Dec 2000 A
6178328 Tang et al. Jan 2001 B1
6192246 Satarasinghe Feb 2001 B1
6198719 Faruque et al. Mar 2001 B1
6198910 Hanley Mar 2001 B1
6208615 Faruque et al. Mar 2001 B1
6219539 Basu et al. Apr 2001 B1
6223047 Ericsson Apr 2001 B1
6233247 Alami et al. May 2001 B1
6246674 Feuerstein et al. Jun 2001 B1
6252862 Sauer et al. Jun 2001 B1
6256300 Ahmed et al. Jul 2001 B1
6266529 Chheda Jul 2001 B1
6272148 Takagi et al. Aug 2001 B1
6285875 Alajoki et al. Sep 2001 B1
6289220 Spear Sep 2001 B1
6320898 Newson et al. Nov 2001 B1
6345185 Yoon et al. Feb 2002 B1
6366961 Subbiah et al. Apr 2002 B1
6370357 Xiao et al. Apr 2002 B1
6370381 Minnick et al. Apr 2002 B1
6393482 Rai et al. May 2002 B1
6400712 Phillips Jun 2002 B1
6404754 Lim Jun 2002 B1
6408182 Davidson et al. Jun 2002 B1
6418306 McConnell Jul 2002 B1
6424834 Chang et al. Jul 2002 B1
6430168 Djurkovic et al. Aug 2002 B1
6438370 Einola et al. Aug 2002 B1
6438376 Elliott et al. Aug 2002 B1
6438377 Savolainen Aug 2002 B1
6445922 Hiller et al. Sep 2002 B1
6459696 Carpenter et al. Oct 2002 B1
6473399 Johansson et al. Oct 2002 B1
6477159 Yahagi Nov 2002 B1
6480476 Willars Nov 2002 B1
6480718 Tse Nov 2002 B1
6507741 Bassirat Jan 2003 B1
6522885 Tang et al. Feb 2003 B1
6539030 Bender et al. Mar 2003 B1
6542481 Foore et al. Apr 2003 B2
6542752 Illidge Apr 2003 B1
6545984 Simmons Apr 2003 B1
6560453 Henry et al. May 2003 B1
6580699 Manning et al. Jun 2003 B1
6590879 Huang et al. Jul 2003 B1
6611695 Periyalwar Aug 2003 B1
6618585 Robinson et al. Sep 2003 B1
6621811 Chang et al. Sep 2003 B1
6628637 Li et al. Sep 2003 B1
6651105 Bhagwat et al. Nov 2003 B1
6687237 Lee et al. Feb 2004 B1
6701148 Carter et al. Mar 2004 B1
6701149 Bagchi et al. Mar 2004 B1
6711144 Kim et al. Mar 2004 B1
6731618 Chung et al. May 2004 B1
6738625 Oom et al. May 2004 B1
6741862 Chung et al. May 2004 B2
6754191 Paranchych et al. Jun 2004 B1
6757319 Parsa et al. Jun 2004 B1
6768903 Fauconnier et al. Jul 2004 B2
6771962 Saifullah et al. Aug 2004 B2
6781999 Eyuboglu et al. Aug 2004 B2
6813498 Durga et al. Nov 2004 B1
6826402 Tran Nov 2004 B1
6834050 Madour et al. Dec 2004 B1
6842630 Periyalwar Jan 2005 B2
6847821 Lewis et al. Jan 2005 B1
6877104 Shimono Apr 2005 B1
6909887 Fauconnier et al. Jun 2005 B2
6944452 Coskun et al. Sep 2005 B2
6975869 Billon Dec 2005 B1
6996056 Chheda et al. Feb 2006 B2
6999784 Choi et al. Feb 2006 B1
7035636 Lim et al. Apr 2006 B1
7042858 Jia et al. May 2006 B1
7047009 Laroia et al. May 2006 B2
7072663 Ramos et al. Jul 2006 B2
7079511 Abrol et al. Jul 2006 B2
7085251 Rezaiifar Aug 2006 B2
7110785 Paranchych et al. Sep 2006 B1
7130626 Bender et al. Oct 2006 B2
7130668 Chang et al. Oct 2006 B2
7139575 Chen et al. Nov 2006 B1
7162247 Baba et al. Jan 2007 B2
7170871 Eyuboglu et al. Jan 2007 B2
7177650 Reiger et al. Feb 2007 B1
7200391 Chung et al. Apr 2007 B2
7212822 Vicharelli et al. May 2007 B1
7236764 Zhang et al. Jun 2007 B2
7242958 Chung et al. Jul 2007 B2
7251491 Jha Jul 2007 B2
7277446 Abi-Nassif et al. Oct 2007 B1
7298327 Dupray et al. Nov 2007 B2
7299168 Rappaport et al. Nov 2007 B2
7299278 Ch'ng Nov 2007 B2
7349699 Kelly et al. Mar 2008 B1
7398087 McConnell et al. Jul 2008 B1
7408887 Sengupta et al. Aug 2008 B2
7411996 Kim et al. Aug 2008 B2
7453912 Laroia et al. Nov 2008 B2
7457265 Julka et al. Nov 2008 B2
7486696 Garg et al. Feb 2009 B2
7512110 Sayeedi et al. Mar 2009 B2
7546124 Tenneti et al. Jun 2009 B1
7751835 Sharma et al. Jul 2010 B2
7751858 Chou Jul 2010 B2
8085696 Garg et al. Dec 2011 B2
8094630 Garg et al. Jan 2012 B2
8145221 Garg et al. Mar 2012 B2
8160020 Eyuboglu et al. Apr 2012 B2
8195187 Eyuboglu et al. Jun 2012 B2
19930057970 Willhoff et al. May 1993
19960019459 Graves et al. Jun 1996
19970859197 Chheda et al. May 1997
19980036191 Sharma et al. Mar 1998
19980198387 Bevan Nov 1998
19980213523 Simmons Dec 1998
19980217064 Xia et al. Dec 1998
19990283151 Lee et al. Apr 1999
19990461454 Robinson Dec 1999
20010797273 Periyalwar et al. Mar 2001
20010046863 Rinne et al. Nov 2001 A1
20020025820 Fauconnier et al. Feb 2002 A1
20020031107 Li et al. Mar 2002 A1
20020032034 Tiedemann et al. Mar 2002 A1
20020035699 Crosbie Mar 2002 A1
20020067707 Morales et al. Jun 2002 A1
20020068570 Abrol et al. Jun 2002 A1
20020082018 Coskun et al. Jun 2002 A1
20020085719 Crosbie Jul 2002 A1
20020102976 Newbury et al. Aug 2002 A1
20020136226 Christoffel et al. Sep 2002 A1
20020145990 Sayeedi Oct 2002 A1
20020193110 Julka et al. Dec 2002 A1
20020196749 Eyuboglu et al. Dec 2002 A1
20010871581 Chheda et al. Jan 2003
20030003913 Chen et al. Jan 2003 A1
20030438748 Zhang et al. Jan 2003
20030026240 Eyuboglu et al. Feb 2003 A1
20030031201 Choi Feb 2003 A1
20030067970 Kim et al. Apr 2003 A1
20030095513 Woodmansee et al. May 2003 A1
20030100311 Chung et al. May 2003 A1
20030469105 Zhang et al. May 2003
20030114162 Chheda et al. Jun 2003 A1
20030117948 Ton et al. Jun 2003 A1
20030125039 Lachtar et al. Jul 2003 A1
20030195016 Periyalwar Oct 2003 A1
20040008649 Wybenga et al. Jan 2004 A1
20040015607 Bender et al. Jan 2004 A1
20040038700 Gibbs Feb 2004 A1
20040068668 Lor et al. Apr 2004 A1
20040081111 Bae et al. Apr 2004 A1
20040179492 Zhang et al. Sep 2004 A1
20040203771 Chang et al. Oct 2004 A1
20040214574 Eyuboglu et al. Oct 2004 A1
20040218556 Son et al. Nov 2004 A1
20040224687 Rajkotia Nov 2004 A1
20040266436 Jaakkola et al. Dec 2004 A1
20050021616 Rajahalm et al. Jan 2005 A1
20050648187 Schmidt et al. Jan 2005
20050025116 Chen et al. Feb 2005 A1
20050036504 Joshi et al. Feb 2005 A1
20050053034 Chiueh Mar 2005 A1
20050111429 Kim et al. May 2005 A1
20050113117 Bolin et al. May 2005 A1
20050124343 Kubo Jun 2005 A1
20050148297 Lu et al. Jul 2005 A1
20050181795 Mark et al. Aug 2005 A1
20050207368 Nam Sep 2005 A1
20050213555 Eyuboglu et al. Sep 2005 A1
20050713958 Akhtar et al. Sep 2005
20050715281 Fong Sep 2005
20050223097 Ramsayer et al. Oct 2005 A1
20050233746 Laroia et al. Oct 2005 A1
20050728848 Novak et al. Oct 2005
20050243749 Mehrabanzad et al. Nov 2005 A1
20050245279 Mehrabanzad et al. Nov 2005 A1
20050751848 Fong Dec 2005
20060758743 Novak et al. Jan 2006
20060067422 Chung Mar 2006 A1
20060067451 Pollman et al. Mar 2006 A1
20060126509 Abi-Nassif Jun 2006 A1
20060126554 Motegi et al. Jun 2006 A1
20060126556 Jiang et al. Jun 2006 A1
20060804343 Fong Jun 2006
20060805670 Novak et al. Jun 2006
20060146751 Obuchi et al. Jul 2006 A1
20060148460 Mukherjee et al. Jul 2006 A1
20060159045 Ananthaiyer et al. Jul 2006 A1
20060820683 Novak et al. Jul 2006
20060820705 Novak et al. Jul 2006
20060182063 Jia et al. Aug 2006 A1
20060183497 Paranchych et al. Aug 2006 A1
20060822018 Novak et al. Aug 2006
20060203766 Kim et al. Sep 2006 A1
20060209760 Saito et al. Sep 2006 A1
20060209882 Han et al. Sep 2006 A1
20060824848 Novak et al. Sep 2006
20060825360 Novak et al. Sep 2006
20060240782 Pollman et al. Oct 2006 A1
20060828312 Novak et al. Oct 2006
20060829426 Novak et al. Oct 2006
20060259628 Vadlapudi et al. Nov 2006 A1
20060264218 Zhang et al. Nov 2006 A1
20060291420 Ng Dec 2006 A1
20060294214 Chou Dec 2006 A1
20060294241 Cherian et al. Dec 2006 A1
20070022396 Attar et al. Jan 2007 A1
20070026884 Rao Feb 2007 A1
20070058628 Rao et al. Mar 2007 A1
20070077948 Sharma et al. Apr 2007 A1
20070097916 Eyuboglu et al. May 2007 A1
20070099632 Choksi May 2007 A1
20070105527 Nylander et al. May 2007 A1
20070115896 To et al. May 2007 A1
20070140172 Garg et al. Jun 2007 A1
20070140184 Garg et al. Jun 2007 A1
20070140185 Garg et al. Jun 2007 A1
20070140218 Nair et al. Jun 2007 A1
20070153750 Baglin et al. Jul 2007 A1
20070155329 Mehrabanzad et al. Jul 2007 A1
20070160008 Burgess Jul 2007 A1
20070197220 Willey Aug 2007 A1
20070220573 Chiussi et al. Sep 2007 A1
20070230419 Raman et al. Oct 2007 A1
20070238442 Mate et al. Oct 2007 A1
20070238476 Rao et al. Oct 2007 A1
20070242648 Garg et al. Oct 2007 A1
20070248042 Harikumar et al. Oct 2007 A1
20080003988 Richardson Jan 2008 A1
20080009328 Narasimha Jan 2008 A1
20080013488 Garg et al. Jan 2008 A1
20080062925 Mate et al. Mar 2008 A1
20080065752 Ch'ng et al. Mar 2008 A1
20080069020 Richardson Mar 2008 A1
20080069028 Richardson Mar 2008 A1
20080070574 Vikberg et al. Mar 2008 A1
20080076398 Mate et al. Mar 2008 A1
20080117842 Rao May 2008 A1
20080119172 Rao et al. May 2008 A1
20080120417 Harikumar et al. May 2008 A1
20080139203 Ng et al. Jun 2008 A1
20080146232 Knisely Jun 2008 A1
20080151843 Valmikam et al. Jun 2008 A1
20080159236 Ch'ng et al. Jul 2008 A1
20080162924 Chinitz et al. Jul 2008 A1
20080162926 Xiong et al. Jul 2008 A1
20080253550 Ch'ng et al. Oct 2008 A1
20080254792 Ch'ng Oct 2008 A1
20080273493 Fong et al. Nov 2008 A1
20080287130 Laroia et al. Nov 2008 A1
20090034440 Samar et al. Feb 2009 A1
20090082020 Ch'ng et al. Mar 2009 A1
20090088155 Kim Apr 2009 A1
20090103494 Jia et al. Apr 2009 A1
20090116445 Samar et al. May 2009 A1
20090129334 Feng et al. May 2009 A1
20090156218 Garg et al. Jun 2009 A1
20090191878 Hedqvist et al. Jul 2009 A1
20120243476 Eyuboglu et al. Sep 2012 A1
Foreign Referenced Citations (66)
Number Date Country
199872855 Dec 1998 AU
199884574 Feb 1999 AU
200121976 Jun 2001 AU
735575 Jul 2001 AU
2003202721 Oct 2003 AU
2295922 Mar 2004 CA
1265253 Aug 2000 CN
1653844 Oct 2004 CN
101015224 Aug 2007 CN
101015224 May 2012 CN
625863 Nov 1994 EP
0904369 Mar 1999 EP
983694 Mar 2000 EP
983705 Mar 2000 EP
995278 Apr 2000 EP
995296 Apr 2000 EP
1005245 May 2000 EP
1011283 Jun 2000 EP
1014107 Jun 2000 EP
1397929 Mar 2004 EP
1491065 Dec 2004 EP
1751998 Feb 2007 EP
1896980 Mar 2008 EP
1897383 Mar 2008 EP
2447585 Aug 2008 GB
2452688 Mar 2009 GB
2447585 Oct 2010 GB
1101334 Oct 2007 HK
2007-538476 Dec 2007 JP
2008-547329 Dec 2008 JP
2008-547358 Dec 2008 JP
5117188 Oct 2012 JP
9833373 Aug 1998 KR
2004046069 Jun 2004 KR
2004089744 Oct 2004 KR
787289 Dec 2007 KR
199910613 Mar 2002 MX
WO9748191 Dec 1997 WO
WO 9808353 Feb 1998 WO
WO 9809460 Mar 1998 WO
WO9853618 Nov 1998 WO
WO9853620 Nov 1998 WO
WO9903245 Jan 1999 WO
WO9904511 Jan 1999 WO
WO0060891 Oct 2000 WO
WO0145308 Jun 2001 WO
WO0186988 Nov 2001 WO
WO02071633 Sep 2002 WO
WO02071652 Sep 2002 WO
WO03001820 Jan 2003 WO
WO03009576 Jan 2003 WO
WO 03043364 May 2003 WO
WO03054721 Jul 2003 WO
WO03081938 Oct 2003 WO
WO2004064434 Jul 2004 WO
WO2005012520 Dec 2005 WO
WO2005115026 Dec 2005 WO
WO2006081527 Aug 2006 WO
WO2007002659 Jan 2007 WO
WO2007028122 Mar 2007 WO
WO2007028252 Mar 2007 WO
WO2007044099 Apr 2007 WO
WO2007045101 Apr 2007 WO
WO 2007075446 Jul 2007 WO
WO 2007078766 Jul 2007 WO
WO2007078766 May 2011 WO
Non-Patent Literature Citations (162)
Entry
Paul Bender, et al., “CDMA/HDR: A Bandwidth-Efficient High-Speed Wireless Data Service for Nomadic Users”, IEEE Communications Magazine, Jul. 2000.
Paul Bender & Ramin Rezalifar, “Draft Baseline Text for the 1xEV-DO Upper Layers (excluding Physical Layer)”, 3GPP2, Aug. 17, 2000.
3GPP2, “3GPP2 Access Network Interfaces Interoperability Specification 2, Release A,” Jun. 2000.
TIA/EIA/TSB-115, “Wireless IP Architecture Based on IETF Protocols”, Jun. 6, 2000.
3GPP2, “Wireless IP Network Standard”, 3rd Generation Partnership Project 2 (3GPP2), Version 1.0.0, Jul. 14, 2000.
Goran Janevski, “IP-Based Mobile Wireless Access Network Architecture”, Nortel Networks-MWIF Contribution, Draft dated Sep. 7, 2000.
International Search Report, Patent Cooperation Treaty, Apr. 26, 2007, 10 pages.
International Search Report, Patent Cooperation Treaty, Oct. 29, 2002, 5 pages.
International Preliminary Report on Patentability for Application No. PCT/US2005/017385, Dec. 7, 2006, 8 pages.
International Preliminary Report on Patentability for Application No. PCT/US2006/024958, Jan. 17, 2008, 7 pages.
EP Examination Report for Application No. 06785637.7, Feb. 6, 2008, 2 pages.
U.S. Appl. No. 09/891,103, filed Jun. 25, 2001.
PCT application No. PCT/US2002/020380 filed on Jun. 25, 2002, with Publication No. WO2003/001820.
U.S. Appl. No. 11/640,619, filed Dec. 18, 2006.
PCT application No. PCT/US2005/17385 filed on May 17, 2005, with Publication No. WO2005/115026.
U.S. Appl. No. 11/037,896, filed Jan. 18, 2005.
U.S. Appl. No. 11/167,785, filed Jun. 27, 2005.
U.S. Appl. No. 11/243,405, filed Oct. 4, 2005.
PCT application No. PCT/US2006/24958 filed on Jun. 27, 2006, with Publication No. WO2007/002659.
U.S. Appl. No. 11/303,773, filed Dec. 16, 2005.
PCT application No. PCT/US2006/47524 filed on Dec. 13, 2006, with Publicaton No. WO2007/075446.
U.S. Appl. No. 11/303,774, filed Dec. 16, 2005.
PCT application No. PCT/US2006/47963 filed on Dec. 15, 2006, with Publication No. WO2007/075446.
U.S. Appl. No. 11/955,644, filed Dec. 13, 2007.
International Search Report, Patent Cooperation Treaty, Oct. 26, 2006, 6 pages.
Written Opinion of the International Searching Authority, Patent Cooperation Treaty, Oct. 26, 2006, 8 pages.
International Search Report and Written Opinion for PCT international application No. PCT/US2006/25018, mailed Jan. 29, 2008 (11 pages).
International Preliminary Report on Patentability for Application No. PCT/US2006/25018, Mar. 19, 2009 (8 pages).
International Preliminary Report on Patentability for PCT international application No. PCT/US2006/047963, mailed Dec. 11, 2008 (5 pages).
International Search Report and Written Opinion for PCT international application No. PCT/US2006/047963, mailed Sep. 26, 2008 (9 pages).
International Search Report and Written Opinion for PCT international application No. PCT/US2006/047524, mailed May 26, 2009 (13 pages).
U.S. Appl. No. 10/848,597, filed May 18, 2004, now U.S. Patent No. 7,170,871, issued Jan. 30, 2007.
U.S. Appl. No. 11/166,893, filed Jun. 24, 2005.
PCT application No. PCT/US2006/025018 filed on Jun. 26, 2006, with Publication No. WO2007/044099.
U.S. Appl. No. 11/402,744, filed Apr. 12, 2006.
3rd Generation Partnership Project “3GPP2”, cdma2000 High Rate Packet Data Interface Specification, C.S0024-A, version 4.0, Oct. 25, 2002.
3rd Generation Partnership Project “3GPP2”, cdma2000 High Rate Packet Data Interface Specification, C.S0024-A, version 1.0, Mar. 2004.
3rd Generation Partnership Project “3GPP2”, cdma2000 High Rate Packet Data Interface Specification, C.S0024-A, version 2.0, Jul. 2005.
3rd Generation Partnership Project “3GPP2”, cdma2000 High Rate Packet Data Interface Specification, C.S0024-B, version 1.0, Apr. 2006.
Rashid Attar et al., “Evolution of cdma2000 Cellular Networks: Multicarrier EV-DO”, IEEE Communications Magazine, Mar. 2006. pp. 46-53.
Chinese Office action of Chinese application No. 200580024230.0 mailed Mar. 15, 2009 (13 pages).
EP Examination Report for Application No. 05750705.5, Jan. 9, 2007 (2 pages).
TIA/EIA/IS-2001, Interoperability Specification (IOS) for CDMA2000 Network Access Interfaces, Aug. 2001 (revised version of May 2000).
Office action and response history of U.S. Appl. No. 09/891,103 to May 27, 2009.
Office action and response history of U.S. Appl. No. 10/848,597 to May 18, 2004.
Office action and response history of U.S. Appl. No. 11/166,893 to May 27, 2009.
Office action and response history of U.S. Appl. No. 11/037,896 to May 27, 2009.
Office action and response history of U.S. Appl. No. 11/167,785 to May 27, 2009.
Office action and response history of U.S. Appl. No. 11/243,405 to May 27, 2009.
Office action and response history of U.S. Appl. No. 11/303,773 to May 27, 2009.
Office action and response history of U.S. Appl. No. 11/303,774 to May 27, 2009.
Office action and response history of U.S. Appl. No. 11/402,744 to May 27, 2009.
Office action and response history of U.S. Appl. No. 11/955,644 to May 27, 2009.
Office action of U.S. Appl. No. 11/303,774 dated Jun. 12, 2009.
Australian (AU) Examination Report for Application No. 2005426813, Jun. 4, 2009 (18 pages).
Office Action and response from European Patent Office for Application No. 06836082.5 mailed Jun. 18, 2009 and sent Jul. 21, 2009 (21 pages).
Chinese Office action response of Chinese application No. 200580024230.0 sent Jul. 22, 2009 (8 pages).
Office action and response history of U.S. Appl. No.. 11/166,893 to Aug. 11, 2009.
Office action and response history of U.S. Appl. No. 11/955,644 to Aug. 11, 2009.
Office action and response history of U.S. Appl. No. 09/891,103 to Aug. 11, 2009.
Office action and response history of U.S. Appl. No. 11/167,785 to Aug. 11, 2009.
Office action and response history of U.S. Appl. No. 11/243,405 to Aug. 11, 2009.
Office action and response history of U.S. Appl. No. 11/303,773 to Aug. 13, 2009.
Office action and response history of U.S. Appl. No. 11/402,744 to Aug. 17, 2009.
Office action and response history of U.S. Appl. No. 11/486,545 to Aug. 26, 2009.
3rd Generation Partnership Project 2 “3GPP2”, “cdma2000 High Rate Packet Data Interface Specification”, C.S0024, version 2, Oct. 27, 2000 (441 pages).
3rd Generation Partnership Project 2 “3GPP2”, “cdma2000 High Rate Packet Data Interface Specification”, C.S0024-B, version 2, Mar. 2007 (1627 pages).
Library Search for Nortel and frequency handoff. Search results dated Aug. 28, 2009 (85 pages).
Office action and response history of U.S. Appl. No. 11/037,896 to Sep. 17, 2009.
Office action and response history of U.S. Appl. No. 11/303,774 to Sep. 17, 2009.
Office action and response history of U.S. Appl. No. 11/167,785 to Sep. 22, 2009.
Office action and response history of U.S. Appl. No. 11/243,405 to Sep. 22, 2009.
Office action and response history of U.S. Appl. No. 11/243,405 to Nov. 9, 2009.
Office action and response history of U.S. Appl. No. 11/640,619 to Nov. 9, 2009.
Office action and response history of U.S. Appl. No. 09/891,103 to Nov. 10, 2009.
Office action and response history of U.S. Appl. No. 11/303,773 to Nov. 20, 2009.
Office action and response history of U.S. Appl. No. 11/402,744 to Nov. 30, 2009.
Chinese Office action of Chinese application No. 200580024230.0 mailed Nov. 20, 2009 (4 pages).
Office action and response history of U.S. Appl. No. 11/166,893 to Dec. 8, 2009.
Office action and response history of U.S. Appl. No. 09/891,103 to Dec. 8, 2009.
Office action and response history of U.S. Appl. No. 11/037,896 to Dec. 8, 2009.
Office action and response history of U.S. Appl. No. 11/243,405 to Dec. 8, 2009.
Office action and response history of U.S. Appl. No. 11/955,644 to Dec. 8, 2009.
Office action and response history of U.S. Appl. No. 11/303,774 to Dec. 11, 2009.
Office action and response history of U.S. Appl. No. 11/243,405 to Jan. 6, 2010.
Office action and response history of U.S. Appl. No. 11/037,896 to Jan. 11, 2010.
Office action and response history of U.S. Appl. No. 11/167,785 to Jan. 11, 2010.
Office action and response history of U.S. Appl. No. 09/891,103 to Dec. 13, 2009.
GB Examination Report for Application No. 0811839.0, mailed Jan. 22, 2010 (2 pages).
Office action and response history of U.S. Appl. No. 11/486,545 to Dec. 8, 2009.
USPTO Non Final Office Action in U.S. Appl. No. 11/955,644, dated May 4, 2012, 17 pages.
European Patent Office communication from European application No. 06785637.7 mailed Apr. 27, 2012 (2 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.
Final Office Action in U.S. Appl. No. 11/037,896, dated May 24, 2012, 29 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).
Fish & Richardson, P.C., Response to Non Final Office Action dated May 4, 2012 in U.S. Appl. No. 11/955,644, filed Aug. 3, 2012, 14 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.
Supplemental Search Report from European Application No. 05750705.5 issued Aug. 2, 2012 (102 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.
Chinese Office action Chinese application No. 200580024230.0 sent Nov. 20, 2009 with English translation (6 pages).
Chinese Office action response of Chinese application No. 200580024230.0 filed Feb. 5, 2010, along with instructions for response and associate recommendation (12 pages).
European Patent Office communication mailed Jun. 18, 2009 and response to Jun. 18, 2009 communication of European application No. 06836082.5 filed Jul. 21, 2009 (21 pages).
Chinese Office action with English translation of Chinese application No. 200580024230.0 dated May 17, 2010 (6 pages).
Response filed May 21, 2010 to GB Examination Report for Application No. 0811839.0, dated Jan. 22, 2010 (12 pages).
GB Examination Report for Application No. 0811839.0, mailed Jun. 3, 2010 (3 pages).
Office action and response history of U.S. Appl. No. 11/640,619 to Jun. 18, 2010.
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.
USPTO Advisory Action in U.S. Appl. No. 11/303,774, dated Jun. 30, 2010, 2 pages.
Examiner Interview Summary in U.S. Appl. No. 11/166,893, dated Jun. 30, 2010, 4 pages.
USPTO Notice of Allowance in U.S. Appl. No. 11/486,545, dated Jul. 28, 2010, 8 pages.
Fish & Richardson, P.C., Amendment in Reply to Action dated Mar. 25, 2010 in U.S. Appl. No. 11/166,893, filed Jun. 28, 2010, 19 pages.
Response filed Aug. 9, 2010 to GB Examination Report for Application No. 0811839.0, dated Jun. 3, 2010 (10 pages).
Response filed Aug. 2, 2010 to Chinese office action for Chinese application No. 200580024230.0 dated May 17, 2010 (41 pages).
USPTO Final Office Action in U.S. Appl. No. 11/303,773, dated Aug. 18, 2010, 12 pages.
Fish & Richardson, P.C., Amendment in Reply to Action dated Mar. 30, 2010 in U.S. Appl. No. 11/402,744, filed Aug. 30, 2010, 12 pages.
Notice of Allowance in U.S. Appl. No. 11/303,774, dated Aug. 31, 2010, 4 pages.
USPTO Office Action in U.S. Appl. No. 11/166,893, dated Sep. 2, 2010, 31 pages.
Fish & Richardson, P.C., Supplemental Amendment in Reply to Action dated Jun. 18, 2010 in U.S. Appl. No. 11/640,619, filed Oct. 18, 2010, 20 pages.
USPTO Final Office Action in U.S. Appl. No. 11/167,785, dated Oct. 15, 2010, 10 pages.
USPTO Supplemental Notice of Allowance in U.S. Appl. No. 09/891,103, dated Oct. 15, 2010, 4 pages.
USPTO Final Office Action in U.S. Appl. No. 11/402,744, dated Nov. 12, 2010, 22 pages.
Supplemental Notice of Allowability in U.S. Appl. No. 11/303,774, dated Nov. 22, 2010, 9 pages.
Notice of Allowability in U.S. Appl. No. 11/486,545, dated Nov. 8, 2010, 6 pages.
Notice of Allowance in U.S. Appl. No. 11/303,774, dated Dec. 21, 2010, 8 pages.
Examiner Interview Summary in U.S. Appl. No. 11/166,893, dated Dec. 17, 2010, 3 pages.
Final Office Action in U.S. Appl. No. 11/640,619, dated Jan. 7, 2011, 24 pages.
Notice of Allowance in U.S. Appl. No. 11/037,896, dated Jan. 5, 2011, 5 pages.
Notice of Allowance in U.S. Appl. No. 11/303,773, dated Dec. 30, 2010, 9 pages.
Fish & Richardson, P.C., Amendment in Reply to Final Office Action dated Nov. 12, 2010 in U.S. Appl. No. 11/402,744, filed Feb. 14, 2011, 12 pages.
Japanese Office action of application No. 2007-527408 issued Nov. 24, 2010, mailed Nov. 29, 2010 with English translation (21 pages).
Fish & Richardson, P.C., Amendment in Reply to Office Action dated Sep. 2, 2010 in U.S. Appl. No. 11/166,893, filed Jan. 3, 2011, 18 pages.
USPTO Notice of Allowance in U.S. Appl. No. 11/166,893, dated Mar. 18, 2011, 21 pages.
Notice of Allowability in U.S. Appl. No. 11/486,545, dated Mar. 11, 2011, 9 pages.
USPTO Supplemental Notice of Allowance in U.S. Appl. No. 09/891,103, dated Mar. 14, 2011, 6 pages.
USPTO Non-Final Office Action in U.S. Appl. No. 11/402,744, dated Apr. 1, 2011, 14 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,773, dated Apr. 15, 2011, 6 pages.
USPTO Supplemental Notice of Allowance in U.S. Appl. No. 11/166,893, dated Apr. 22, 2011, 17 pages.
International Preliminary Report on Patentability for PCT international application No. PCT/US2006/047524, mailed Apr. 28, 2011 (8 pages).
Notice of Allowance in U.S. Appl. No. 11/037,896, dated May 17, 2011, 8 pages.
Response filed May 30, 2011 to Japanese Office action issued in application No. 2007-527408, Nov. 24, 2010, mailed Nov. 29, 2010 (31 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.
USPTO Final Office Action in U.S. Appl. No. 11/402,744, dated Oct. 6, 2011, 14 pages.
Non Final Office Action in U.S. Appl. No. 11/037,896, dated Oct. 20, 2011, 28 pages.
USPTO Notice of Appeal Decision in U.S. Appl. No. 11/167,785, dated May 3, 2011, 2 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.
Japanese Office action issued in application No. 2007-527408 on Nov. 11, 2011, mailed Nov. 16, 2011 (5 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 Oct. 20, 2011 in U.S. Appl. No. 12/857,206, filed Mar. 20, 2012, 19 pages.
USPTO Final Office Action in U.S. Appl. No. 11/955,644, dated Sep. 21, 2012, 22 pages.
Fish & Richardson, P.C., Response to Final Office Action dated Sep. 21, 2012 in U.S. Appl. No. 11/955,644, filed Dec. 20, 2012, 16 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/167,785, dated Dec. 6, 2012, 9 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 Final Office Action dated Dec. 6, 2012 in U.S. Appl. No. 11/167,785, filed Mar. 6, 2013, 13 pages.
Examination Report from European Application No. 05750705.5 issued Mar. 11, 2013 (9 pages).
Fish & Richardson, P.C., Amendment After Allowance in U.S. Appl. No. 12/857,206, filed Feb. 21, 2013, 10 pages.
Response to European Patent Office communication from European application No. 06785637.7 mailed Apr. 27, 2012, filed Jun. 24, 2012, 3 pages.
European Search Report from European Application No. 06836082.5 mailed Apr. 26, 2013 (80 pages).
USPTO Final Office Action in U.S. Appl. No. 13/430,422, dated May 31, 2013, 12 pages.
Supplemental European Search Report from European Application No. 06836082.5 mailed May 15, 2013 (1 page).
USPTO Non Final Office Action in U.S. Appl. No. 11/167,785, dated Jun. 13, 2013, 10 pages.
Related Publications (1)
Number Date Country
20070140172 A1 Jun 2007 US