Source: https://patents.google.com/patent/US8145221B2/en
Timestamp: 2019-04-24 07:38:49+00:00

Document:
2006-02-16 Assigned to AIRVANA, INC. reassignment AIRVANA, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: KNISELY, DOUGLAS NORMAN, GARG, DEEPAK, PALNATI, PRASASTH R.
Techniques for enabling a radio access network to cause an access terminal in communication with the radio access network to send an update including information about a location of the access terminal.
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/305,286, titled “Radio Network Control,” being filed concurrently with the present application, which are also incorporated herein by reference.
This description relates to radio network communication.
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. 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, and 112 over a packet network 114. The packet network 114 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 114 is connected to the Internet 116 via a packet data serving node 106. Other radio nodes, radio node controllers, and packet networks (not shown in FIG. 1) can be included in the radio access network 100. The packet network 114 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 118 communicate with the network 100 over airlinks 120. Each access terminal may be a cellular phone, 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 120 between the network 100 and an access terminal 118 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 118) transmits messages and parameters that the access terminal 118 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 118.
FIG. 2 shows a network coverage area corresponding to the 1xEV-DO radio access network 100. In this example, the radio nodes serve coverage areas of different sizes. The large coverage areas served by radio nodes 108 and 110 are referred to as macro cells, while the smaller coverage areas served by radio node 112 is referred to as a pico cell. A macro cell covers a very large geographic area; for example, the metropolitan area of a city. A pico cell generally has a much smaller coverage area; for example, a single office building. The coverage area of a pico cell may partially or completely overlap the coverage area of a macro cell. The pico cell within the coverage area of the macro cell may operate on the same or different carrier frequency. An access terminal 118 in the pico cell coverage area may access the network either through the macro cell radio node 108 or the pico cell radio node 112. Accessing the network through the pico cell radio node 112 conserves the network resources of the macro cell and vice versa.
There are a number of different techniques that may be implemented by the 1xEV-DO radio access network 100 to determine when a handoff between the radio nodes of overlapping pico and macro cells is to take place. One example technique involves installing, in the coverage area of the macro cell radio node, a pilot beacon that transmits a pilot signal on the same carrier frequency as that of the macro cell radio node 108. A handoff can be triggered by the network upon detection of a carrier frequency change. However, these pilot beacons do not provide any actual carrier service to an access terminal and are therefore very limited in application. Additionally installation of each pilot beacon can be very expensive. Another example technique involves configuring an access terminal to constantly assume the presence of a pico cell and attempt to connect to it. However, such constant activity is very draining on the limited access terminal resources, including the access terminal's battery. Furthermore, this technique does not enable the network to determine instances in which it may be more beneficial to serve the access terminal via the macro cell radio node, although weaker pico cell signals may be available.
In general, in one aspect, a radio access network causes an access terminal in communication with the radio access network to send an update including information about a location of the access terminal.
Implementations may include one or more of the following features. The radio access network causes the access terminal to send the update by broadcasting trigger information. The trigger information comprises a trigger that is specific to a cell of the radio access network. The radio access network causes the access terminal to send the update by unicasting query information. The query information comprises a query that is specific to a cell of the radio access network. The query information comprises a query that is specific to a carrier frequency on which a radio node of the radio access network or a different radio access network operates. The information comprises information about one or more radio nodes each operating on a carrier frequency on which the access terminal operates. The information comprises information about one or more radio nodes, at least one of which operates on a carrier frequency other than a carrier frequency on which the access terminal operates. The information comprises a sector identifier and a pilot strength associated with a sector of a macro cell. The information comprises a sector identifier and a pilot strength associated with a sector of a pico cell. The radio access network uses the information sent by the access terminal to determine whether a handoff between cells of the radio access network is to be performed.
In general, in one aspect, an access terminal performs a comparison of a recently-received cell-specific identifier with a previously-received cell-specific identifier; and takes action as a result of the comparison.
Implementations may include one or more of the following features. Each of the recently-received cell-specific identifier and the previously-received cell-specific identifier comprises a cell-specific route update trigger code. Taking action comprises sending a message to a radio access network. The message comprises a pilot strength of at least one sector of the radio access network that is visible to the access terminal. Taking action comprises replacing the previously-received cell-specific identifier with the recently-received cell-specific identifier.
In general, in one aspect, when an access terminal is communicating with a first cell of a network and is within a service area of both the first cell of the network and a second cell of the network, the network determines when to initiate a handoff of the access terminal from the first cell to the second cell.
Advantages that can be seen in particular implementations of the invention include one or more of the following. When a macro and pico cell are controlled by the same radio network controller, the access terminal can be redirected from one to the other without experiencing an interruption in service. Allowing an access terminal to use the local resources of a pico cell when possible conserves the resources of the macro cell. The access terminal is also able to conserve its resources and battery power. Additionally, by implementing the techniques in the form of software that is easy to update as new cells are added to the radio access network and additional carrier frequencies are supported by the radio access network, the network operator does not have to install expensive hardware, such as pilot beacons, in the network in order to determine when handoffs between macro and pico cells are to be performed.
FIGS. 1-2 each show a radio access network.
FIG. 3 shows a flowchart of a macro-pico handoff determination process.
In some implementations, the 1xEV-DO network 100 of FIG. 1 supports a triggering mechanism that enables the network to cause an access terminal, in communication with the network, to send an update with information about the access terminal's location.
In the examples to follow, this triggering mechanism is used to facilitate handoffs between macro and pico cells within the coverage area of the network, where the macro cell radio nodes operate on carrier frequency C1 and the pico cell radio nodes operate on carrier frequency C2. In some cases, the macro cell and the pico cell are homed to the same radio node controller. In those cases in which the macro cell and the pico cell are homed to different radio node controllers, the network 100 of FIG. 1 may be implemented with a multi-homing architecture (e.g., as described in U.S. application Ser. No. 11/305,286, titled “Radio Network Control,”) or a clustering architecture.
Referring to FIGS. 1-3, in some examples, each radio node controller of the 1xEV-DO network 100 of FIG. 1 has (or has access to) information about all of the operational pico cell(s) in the network 100. The information includes each pico cell's carrier frequency, PN Offset, and the macro cell(s) with which the pico cell's coverage area overlaps. The radio node of each macro cell with which a pico cell's coverage area overlaps is configured to periodically broadcast a cell-specific Route Update Trigger Code (“RUTriggerCode”) in overhead messages transmitted on the control channels of the macro cell radio node (302).
Each idle access terminal 118 periodically monitors a control channel of its serving radio node for overhead messages. Upon receipt (304) of an overhead message containing the cell-specific RUTriggerCode, the access terminal 118 compares (306) the recently-received RUTriggerCode with a RUTriggerCode stored in its memory. The RUTriggerCode stored in memory corresponds to the macro cell radio node that last served the access terminal. If the comparison yields a match, no action is taken (308). A non-match serves as an indicator that the idle access terminal has entered the coverage area of a new macro cell, and triggers the idle access terminal to send (310) a Route Update message back to the network by way of the macro cell radio node 108. The Route Update message typically identifies, to the radio node controller 102, the sectors that are visible to the idle access terminal, and for each visible sector, its associated pilot strength. The visible sectors generally include sectors of radio nodes that are operating on the same carrier frequency C1 as that of the idle access terminal. 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. For example, if the idle access terminal 118 moves from the coverage area of macro cell B 206 into the coverage area of macro cell A 204, where the radio nodes 108, 110 of both macro cells operate on the same carrier frequency C1, the idle access terminal will report, as visible, the sectors of the macro cell radio node 108 in its Route Update message.
The radio node controller examines each Route Update message it receives to determine (312) whether the idle access terminal is in the coverage area of a macro cell with which a pico cell's coverage area overlaps. To do so, the serving radio node controller compares the sector identification information provided in the Route Update message with the information it has about the operational pico cell(s) within the network. If the determination yields a negative result (i.e., no pico cells within the coverage area of the macro cell 108), no action is taken (314). If the determination yields a positive result (i.e., there are one or more pico cells within the coverage area of the macro cell 108), the radio node controller sends (316) a specific query (referred to in this description as a Modified Route Update Request) to the access terminal. The query can be made on the access terminal's paging cycle to avoid excessive use of network resources. This query typically relates to those specific pico cells that are within the coverage area of the macro cell, including those pico cells having radio nodes that are operating on a different carrier frequency C2 than that of the macro cell radio node.
Upon receipt of the Modified Route Update Request, the idle access terminal will return (318) a Route Update message. In this Route Update message, the idle access terminal reports not only the sectors of radio nodes that are operating on the same carrier frequency C1 as that of the idle access terminal, but also the radio nodes that are operating on a different carrier frequency C2. In this manner, the network is made aware of the signal strengths of the sectors of pico cell radio nodes operating on a different carrier frequency C2 that are visible to the access terminal.
In instances in which the idle access terminal is at or near the boundary of a pico cell coverage area, the Route Update message will likely identify, as visible, one or more sectors associated with the pico cell radio node and one or more sectors associated with the macro cell radio node. The radio node controller uses the relative reported signal strengths to determine whether a macro-to-pico handoff is to be performed (320). In some implementations, the radio node controller examines the reported pilot strengths of each pico cell radio node to determine whether any one of the reported pilot strengths exceeds a configurable threshold for a configurable number of times. Generally, the network operator sets the configurable values such that macro-to-pico handoffs are not triggered when the macro cell coverage is sufficiently strong. By continuously evaluating which radio node would most efficiently serve the idle access terminal, handoffs can be reduced or minimized to those instances in which a macro-to-pico handoff would provide for efficient network resource utilization.
In some implementations, once a determination is made to trigger a macro-to-pico handoff, the radio node controller sends a Unicast Redirect message to the access terminal. Upon receipt of the message, the idle access terminal processes the Unicast Redirect message to seamlessly transition from the carrier on which it operates to the carrier frequency specified in the Unicast Redirect message. In this case, the idle access terminal operating on the carrier frequency C1 will operate on the carrier frequency C2 after the Unicast Redirect message is processed. The user disruption associated with the “switch carrier” process typically averages about 100-500 ms long and is not typically noticeable by the access terminal user, especially when the access terminal is idle.
In the case of an active access terminal in the coverage area of a macro cell 108, the active access terminal can be configured to send a Route Update message to the network when the pilot strength associated with the macro cell radio node 108 exceeds the Pilot_Add threshold. The Route Update message identifies, to the radio node controller 102, the sectors operating on carrier frequency C1 that are visible to the active access terminal, and for each visible sector, its associated pilot strength (310).
The radio node controller examines each Route Update message it receives to determine whether the active access terminal is in the coverage area of a macro cell with which a pico cell's coverage area overlaps in the same manner described above with reference to the idle access terminal example (314). If the determination is made that there are one or more pico cells within the coverage area of the macro cell, the radio node controller sends a Modified Route Update Request to the active access terminal (316), which returns the pilot strengths of the visible sectors of the one or more pico cells operating on carrier frequency C2 (318).
The radio node controller uses the relative reported signal strengths to determine whether a macro-to-pico handoff is to be performed (320). In the implementations in which the macro cell and the pico cell are homed to the same vendor, the radio node controller examines the reported pilot strengths of each pico cell radio node to determine whether any one of the reported pilot strengths satisfies a condition (e.g., exceeds a configurable threshold for a configurable number of times). The pico cell associated with the reported strength that satisfies the condition is referred to as the target pico cell. Once a determination is made to trigger a macro-to-pico handoff, the radio node controller allocates airlink resources for the radio node of the target pico cell, and sends a TrafficChannelAssignment message to the active access terminal over the control channel of each of the visible sectors associated with the target pico cell. Upon receipt of the TrafficChannelAssignment message, the active access terminal processes the TrafficChannelAssignment message to seamlessly transition from the carrier on which it operates to the carrier frequency C2 of the target pico cell while remaining active.
In the implementations in which the macro and pico cells are homed to different vendors, the radio node controller determines when a macro-to-pico handoff is to be triggered as described above, then sends a Unicast Redirect message to the active access terminal to effect the handoff. The access terminal closes its current connection with the network via the macro cell's radio node and opens a new connection with the network via the target pico cell's radio node. The user disruption associated with the “close connection-open connection” process typically averages about 1 second long.
The triggering mechanism can also be used to facilitate a transition from a pico cell to the macro cell. Generally, once an access terminal has transitioned to a local pico cell, it will continue to access the network via the pico cell node while it remains parked, or within the coverage area of that pico cell. Once the access terminal becomes mobile, moving out of the coverage area of the pico cell, it will transition back to the macro cell.
An idle or active access terminal in the coverage area of a pico cell will periodically report the pilot strengths of visible sectors to the network using a Route Update Message. In the idle case, the pico cell can include the macro cell's sector identification in its neighbor list, as described in U.S. application Ser. No. 11/303,733 titled “Radio Frequency Dragging Prevention”. In those instances in which the radio node controller determines that the reported pilot strength of the serving pico cell radio node is below a configurable threshold (or the reported pilot strength of a macro cell radio node is exceeds a configurable threshold) for a configurable number of times, the radio node controller sends a Unicast Redirect message to the access terminal to effect pico-to-macro handoff that involves a carrier frequency change from C2 (that of the pico cell radio node) to C1 (that of the macro cell radio node). In the active case, the radio node controller sends a TrafficChannelAssignment message to the access terminal to effect a seamless pico-to-macro handoff between cells homed to the same vendor. When the cells are homed to different vendors, a Unicast Redirect message can be used, resulting in a brief disruption of service.
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 involving handoffs or multi-carrier traffic allocation.
sending a signal to the access terminal that initiates the handoff if the radio network controller determines to handoff the access terminal from the macro cell radio node to the private access point.
2. The method of claim 1, wherein the macro cell radio node and the private access point operate on different carrier frequencies.
3. The method of claim 1, wherein the macro cell radio node and the private access point operate on a common carrier frequency.
4. The method of claim 1, wherein the first information was sent by the access terminal in response to a RUTrigger message.
5. The method of claim 1, wherein the first information comprises signal strengths.
6. The method of claim 1, wherein the first information comprises a signal strength of the macro cell radio node.
7. The method of claim 1, wherein the request is sent via a radio node.
8. The method of claim 7, wherein the radio node comprises the macro cell radio node.
wherein the second information comprises additional location information from the access terminal about at least one private access point having a service area that overlaps the service area of the macro cell radio node.
11. The method of claim 10, wherein the at least one private access point comprises any private access points operating on a same carrier frequency as the macro cell radio node.
12. The method of claim 10, wherein the at least one private access point further comprises any private access points operating on a different carrier frequency as the macro cell radio node.
13. The method of claim 10, wherein the location information comprises a signal strength of a sector of the private access point.
14. The method of claim 1, wherein the second information comprises a signal strength of a sector of at least one private access point having a service area that overlaps the service area of the macro cell radio node.
15. The method of claim 1, wherein the at least one private access point comprises the private access point.
send a signal to the access terminal that initiates the handoff if the radio network controller determines to handoff the access terminal from the macro cell radio node to the private access point.
initiating the handoff by sending a signal to the access terminal.
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-A, version 4.0, Oct. 25, 2002.
3rd Generation Partnership Project "3GPP2", cdma2000 High Rate Packet Data Interface Specification, C.S0024-B, version 1.0, Apr. 2006.
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).
Australian (AU) Examination Report for Application No. 2005426813, Jun. 4, 2009 (18 pages).
Chinese Office action Chinese application No. 200580024230.0 sent Nov. 20, 2009 with English translation (6 pages).
Chinese Office action of Chinese application No. 200580024230.0 mailed Mar. 15, 2009 (13 pages).
Chinese Office action of Chinese application No. 200580024230.0 mailed Nov. 20, 2009 (4 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).
Chinese Office action response of Chinese application No. 200580024230.0 sent Jul. 22, 2009 (8 pages).
Chinese Office action with English translation of Chinese application No. 200580024230.0 dated May 17, 2010 (6 pages).
EP Examination Report for Application No. 05750705.5, Jan. 9, 2007 (2 pages).
EP Examination Report for Application No. 06785637.7, Feb. 6, 2008, 2 pages.
European Patent Office communication and response of European application No. 06836082.5 mailed Jun. 18, 2009 (21 pages).
Examiner Interview Summary in U.S. Appl. No. 11/166,893, dated Dec. 17, 2010, 3 pages.
Examiner Interview Summary in U.S. Appl. No. 11/166,893, dated Jun. 30, 2009, 4 pages.
Final Office Action in U.S. Appl. No. 11/640,619, dated Jan. 7, 2011, 24 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, 24 pages.
Fish & Richardson, P.C., Amendment in Reply to Action dated Jun. 24, 2010 in U.S. Appl. No. 11/305,286, filed on Oct. 25, 2010, 31 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.
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.
Fish & Richardson, P.C., Amendment in Reply to Final Office Action dated Nov. 12, 2010 in U.S. Appl. No. 11/402,744, filed on Feb. 14, 2011, 12 pages.
Fish & Richardson, P.C., Amendment in Reply to Office Action dated Apr. 1, 2011 in U.S. Appl. No. 11/402,744, filed on Jun. 30, 2011, 13 pages.
Fish & Richardson, P.C., Amendment in Reply to Office Action dated Sep. 2, 2010 in U.S. Appl. No. 11/166,893, filed on Jan. 3, 2011, 18 pages.
Fish & Richardson, P.C., Supplemental Amendment in Reply to Action dated Jun. 18, 2010 in U.S. Appl. No. 11/640,619, filed on Oct. 18, 2010, 20 pages.
GB Examination Report for Application No. 0811839.0, mailed Jan. 22, 2010 (2 pages).
GB Examination Report for Application No. 0811839.0, mailed Jun. 3, 2010 (3 pages).
Goran Janevski, "IP-Based Mobile Wireless Access Network Architecture", Nortel Networks- MWIF Contribution, Draft dated Sep. 7, 2000.
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.
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/047524, mailed Apr. 28, 2011 (8 pages).
International Preliminary Report on Patentability for PCT international application No. PCT/US2006/047963, mailed Dec. 11, 2008 (5 pages).
International Preliminary Report on Patentability mailed Nov. 27, 2008 in corresponding PCT application No. PCT/US2006/047963 (5pages).
International Search Report and Written Opinion for PCT international application No. PCT/US2006/047524, mailed May 26, 2009 (13 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/25018, mailed Jan. 29, 2008 (11 pages).
International Search Report and Written Opinion mailed Sep. 26, 2008 in corresponding PCT application No. PCT/US2006/47963 (9 pages).
International Search Report, Patent Cooperation Treaty, Apr. 26, 2007, 10 pages.
International Search Report, Patent Cooperation Treaty, Oct. 26, 2006, 6 pages.
International Search Report, Patent Cooperation Treaty, Oct. 29, 2002, 5 pages.
Japanese Office action of application No. 2007-527408 issued Nov. 24, 2010, mailed Nov. 29, 2010 with English translation (21 pages).
Library Search for Nortel and frequency handoff. Search results dated Aug. 28, 2009 (85 pages).
Non Final Office Action in U.S. Appl. No. 11/037,896, dated Oct. 20, 2011, 28 pages.
Notice of Allowability in U.S. Appl. No. 11/486,545, dated Mar. 11, 2011, 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/037,896, dated Jan. 5, 2011, 5 pages.
Notice of Allowance in U.S. Appl. No. 11/037,896, dated May 17, 2011, 8 pages.
Notice of Allowance in U.S. Appl. No. 11/303,773, dated Apr. 15, 2011, 6 pages.
Notice of Allowance in U.S. Appl. No. 11/303,773, dated Dec. 30, 2010, 9 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).
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. 09/891,103 to Dec. 13, 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. 09/891,103 to Jun. 14, 2010.
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. 09/891,103 to Nov. 10, 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/037,896 to Dec. 8, 2009.
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/037,896 to Jun. 16, 2010.
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/037,896 to Sep. 17, 2009.
Office action and response history of U.S. Appl. No. 11/166,893 to Apr. 13, 2010.
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/166,893 to Dec. 8, 2009.
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/167,785 to Apr. 28, 2010.
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/167,785 to Jan. 11, 2010.
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/167,785 to Sep. 22, 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/243,405 to Dec. 8, 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/243,405 to Jun. 17, 2010.
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/243,405 to Nov. 9, 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/303,773 to Jun. 11, 2010.
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,773 to Nov. 20, 2009.
Office action and response history of U.S. Appl. No. 11/305,286 to Aug. 11, 2008.
Office action and response history of U.S. Appl. No. 11/305,286 to Jan. 11, 2010.
Office action and response history of U.S. Appl. No. 11/305,286 to Jun. 1, 2009.
Office action and response history of U.S. Appl. No. 11/305,286 to Jun. 24, 2010.
Office action and response history of U.S. Appl. No. 11/305,286 to Sep. 30, 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/402,744 to Mar. 30, 2010.
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/402,744 to Nov. 30, 2009.
Office action and response history of U.S. Appl. No. 11/486,545 to Aug. 26, 2009.
Office action and response history of U.S. Appl. No. 11/486,545 to Dec. 8, 2009.
Office action and response history of U.S. Appl. No. 11/486,545 to May 28, 2010.
Office action and response history of U.S. Appl. No. 11/640,619 to Jun. 18, 2010.
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. 11/955,644 to Aug. 11, 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/955,644 to Jun. 3, 2010.
Office action and response history of U.S. Appl. No. 11/955,644 to May 27, 2009.
PCT application No. PCT/US2002/020380 filed on Jun. 25, 2002, with Publication No. W02003/001820, including copy of application as filed.
PCT application No. PCT/US2005/17385 filed on May 17, 2005, with Publication No. W02005/115026, including copy of application as filed.
PCT application No. PCT/US2006/025018 filed Jun. 26, 2006, with Publication No. W02007/044099, including application as filed, transaction history from PAIR (PTO website).
PCT application No. PCT/US2006/24958 filed on Jun. 27, 2006, with Publication No. W02007/002659, including copy of application as filed.
PCT application No. PCT/US2006/47524 filed on Dec. 13, 2006, with Publication No. W02007/078766, including copy of application as filed.
PCT application No. PCT/US2006/47963 filed on Dec. 15, 2006, with Publication No. W02007/075446, including copy of application as filed.
Rashid Attar et al., "Evolution of cdma2000 Cellular Networks: Multicarrier EV-DO", IEEE Communications Magazine, Mar. 2006. pp. 46-53.
Response filed Aug. 2, 2010 to Chinese office action for Chinese application No. 200580024230.0 dated May 17, 2010 (40 pages).
Response filed Aug. 9. 2010 to GB Examination Report for Application No. 0811839.0, dated Jun. 3, 2010 (10 pages).
Response filed May 21, 2010 to GB Examination Report for Application No. 0811839.0, dated Jan. 22, 2010 (12 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).
TIA/EIA/IS-2001, Interoperability Specification (IOS) for CDMA2000 Network Access Interfaces, Aug. 2001 (revised version of May 2000).
U.S. Appl. No. 09/891,103, filed on Jun. 25, 2001, including copy of application as filed, and pending claims.
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, transaction history from PAIR (PTO website).
U.S. Appl. No. 11/037,896, filed on Jan. 18, 2005, including copy of application as filed, and pending claims.
U.S. Appl. No. 11/166,893, filed Jun. 24, 2005, including application as filed, transaction history from PAIR (PTO website), and pending claims.
U.S. Appl. No. 11/167,785, filed on Jun. 27, 2005, including copy of application as filed, and pending claims.
U.S. Appl. No. 11/243,405, filed on Oct. 4, 2005, including copy of application as filed, and pending claims.
U.S. Appl. No. 11/303,773, filed on Dec. 16, 2005, including copy of application as filed, and pending claims.
U.S. Appl. No. 11/305,286, filed on Dec. 16, 2005, including copy of application as filed.
U.S. Appl. No. 11/402,744, filed Apr. 12, 2006, including application as filed, transaction history from PAIR (PTO website), and pending claims.
U.S. Appl. No. 11/640,619, filed on Dec. 18, 2006, including copy of application as filed.
U.S. Appl. No. 11/955,644, filed on Dec. 13, 2007, including copy of application as filed.
USPTO Final Office Action in U.S. Appl. No. 11/167,785, dated Oct. 15, 2010, 10 pages.
USPTO Final Office Action in U.S. Appl. No. 11/303,773, dated Aug. 18, 2010, 12 pages.
USPTO Final Office Action in U.S. Appl. No. 11/305,286, dated Jun. 24, 2010, 39 pages.
USPTO Final Office Action in U.S. Appl. No. 11/402,744, dated Nov. 12, 2010, 22 pages.
USPTO Final Office Action in U.S. Appl. No. 11/402,744, dated Oct. 6, 2011, 14 pages.
USPTO Non-Final Office Action in U.S. Appl. No. 11/402,744, dated Apr. 1, 2011, 14 pages.
USPTO Notice of Allowance in U.S. Appl. No. 11/166,893, dated Mar. 18, 2011, 21 pages.
USPTO Notice of Allowance in U.S. Appl. No. 11/486,545, dated Jul. 18, 2011, 10 pages.
USPTO Notice of Allowance in U.S. Appl. No. 11/486,545, dated Jul. 28, 2010, 8 pages.
USPTO Office Action in U.S. Appl. No. 11/166,893, dated Sep. 2, 2010, 31 pages.
USPTO Supplemental Notice of Allowance in U.S. Appl. No. 09/891,103, dated Mar. 14, 2011, 6 pages.
USPTO Supplemental Notice of Allowance in U.S. Appl. No. 09/891,103, dated Oct. 15, 2010, 4 pages.
USPTO Supplemental Notice of Allowance in U.S. Appl. No. 11/166,893, dated Apr. 22, 2011, 17 pages.
Written Opinion of the International Searching Authority, Patent Cooperation Treaty, Oct. 26, 2006, 8 pages.

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