This patent application relates to an access point in a cellular network obtaining time information, such as absolute time.
When connecting to a radio network, an access terminal selects an access point from available radio network access points that are within communication range. Network protocols are used in communicating between an access point and the access terminal.
The 1xRTT protocol has been standardized by the Telecommunication Industry Association (TIA) in the TIA-2000.1 through TIA-2000.6 series of specifications, which are incorporated herein by reference.
The 1xEV-DO protocol has been standardized by the 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-856A, “CDMA2000 High Rate Packet Data Air Interface Specification,” 3GPP2 C.S0024-A, Version 2.0, July 2005. Revision A is also incorporated herein by reference. Revision B to this specification has been published as TIA/EIA/IS-8560B, 3GPP2 C.S0024-B, version 1.0, May 2006, and is also incorporated herein by reference. Other wireless communication protocols, such as UMTS (Universal Mobile Telecommunications Service), may also be used.
This patent application describes a method, performed by an access point of a cellular network, that obtains time information. The method comprises identifying a control channel cycle boundary; at a beginning of the control channel cycle boundary, sending a request to a time server; receiving a response from the time server, the request comprising a server time; and obtaining the timing information using the server time. Obtaining the timing information includes using the server time and a first reference time to obtain an integer and a fraction; using the fraction to obtain a time difference; and using the time difference to obtain the timing information. The method may include one or more of the following features.
The timing information may comprise a time corresponding to the control channel cycle boundary. The request may be sent at a time that is delayed relative to the control channel cycle boundary. The server time may be offset from the control channel cycle boundary. The timing information may correspond to a time at the control channel cycle boundary.
Using the time difference to obtain the timing information may comprise subtracting the difference from the server time to obtain a result, the result corresponding to a time at the control channel cycle boundary. The access point may a femtocell. The time server need not know a time at the control channel cycle boundary.
The foregoing method, or any feature thereof may be implemented as a computer program product comprised of instructions that are stored on one or more machine-readable storage media, and that are executable on one or more processing devices. The foregoing method may be implemented as an apparatus or system that includes one or more processing devices and memory to store executable instructions to implement the method.
This patent application also describes a method, performed by an access point of a cellular network, for obtaining time information. The method comprises identifying a control channel cycle boundary; at a beginning of the control channel cycle boundary, sending a request to a time server; receiving a response from the time server, the request comprising a server time; and obtaining the timing information using the server time. Obtaining the timing information comprises using the server time and a first reference time to obtain an integer and a fraction, and using the integer to obtain the timing information. The method may include one or more of the following features.
Using the server time and the first reference time to obtain the integer and the fraction may comprise obtaining a difference between the server time and the first reference time, and obtaining a quotient of the difference and a predefined time interval, where the quotient comprises the integer and the fraction. Using the integer to obtain the timing information may comprise obtaining a product of the integer and a predefined time interval, and adding the product to a second predefined reference time. The timing information may comprise a time at the control channel cycle boundary. The access point may be a femtocell. The time server need not know a time at the control channel cycle boundary.
The foregoing method, or any feature thereof, may be implemented as a computer program product comprised of instructions that are stored on one or more machine-readable storage media, and that are executable on one or more processing devices. The foregoing method may be implemented as an apparatus or system that includes one or more processing devices and memory to store executable instructions to implement the method.
The details of one or more examples are set forth in the accompanying drawings and the description below. Further features, aspects, and advantages will become apparent from the description, the drawings, and the claims.
Referring to
RAN 100 uses the 1xEV-DO protocol to transmit data packets between an access terminal, e.g., access terminal 114 and 116, and a macro BTS, e.g., BTSs 108, 110, 112. The BTSs 108 may be connected over a backhaul connection 118 to radio network controller/packet data serving nodes (RNC/PDSN) 120a-b, which may include one or more physical devices at different locations. Although this description uses terminology from EV-DO standards, the same concepts are applicable to other communication standards, including 1xRTT, GSM, UMTS, HSDPA, WiMax, WiBro or WiFi.
The access terminals, such as access terminal 114, may be single-user devices, such as a cellular telephones and PDAs, or multiple-user devices, such as routers 117a that allow single-user devices, such as laptops 117b, to connect to the access terminals through local links (not shown). In some examples, the local links can be wired connections, e.g., Ethernet on a wired LAN, or wireless, e.g., Wi-Fi connections to a wireless local area network (LAN).
Functions of the BTS and the radio network controller (RNC) may be combined into a single device; functions of the PDSN and the radio network control (RNC) may be combined into a single device; and functions of the BTS, the RNC and the PDSN may be combined into the same device.
The implementations described herein are independent of the above combinations and the benefits apply to all combinations. References in this description to a radio access network (RAN) 100 taking action or being acted upon generally refer to a radio network control (RNC) 120a or a radio network control (RNC) 120a in combination with other devices.
Access terminals, such as access terminal 114, may be in communication with a BTS, such as BTS 108, through an air link 124. The air link 124 may include a forward link 124a (also referred to as a downlink), which carries data from a BTS 108 to an access terminal 114, and a reverse link 124b (also referred to as an uplink), which carries data from the access terminal 114 to the BTS 108.
Referring to
A private access point, such as access point 202, may use an available high-speed Internet connection, such as a connection over a digital subscriber line (DSL) modem 204 or a cable modem 214, for connection to the backhaul 218. Such an access point may be in communication with a network 219, such as a remote network or the Internet. Generally, private access points communicate with network 219 through a backhaul connection 218, such as a DSL or a cable connection. Network 219 may include one or more remote network servers, such as servers 201 and 203. For example, server 201 may be a network time protocol server and server 203 may be for finding an offset of a sync capsule. A network database, such as database 209, may be included within at least one of the network servers, such as server 203. Database 209 may be included within the same server 201 as a time server or network server database 209 may include the time server.
When an authorized access terminal, such as access terminals 206, 216, is inside a home (or anywhere within range of access point 202), the authorized access terminal uses access point 202 rather than the macro BTS 108 to place or receive voice calls and/or to establish data connections. Access point 202 may be integrated into, or connected to, a cable modem 204, a WiFi access point (not shown), or other network hardware (such as router 117a in
In general, the 1xEv-DO protocol provides for digital messages, such as messages transmitted over the air link 124, to be communicated to and from one or more access terminals 114 and macro BTSs, such as macro BTS 108, in RAN 100. Messages transmitted over the air link 124 may report status of the access terminals 114, send requests to a macro BTS, adjust configurations of the access terminals 114, and transmit user data. Such messages may be used for other purposes as well.
Access points 202, 212 may be configured to receive radio signals 205 from a macro BTS 108. Accordingly, in some examples, access points 202 and 212 do not transmit signals to the macro BTS, but rather listen to radio signals 205 transmitted by the macro BTS 108.
Digital messages from the macro BTSs are communicated as “chips,” which form the basic signal elements in a code division multiple access (CDMA) waveform. The 1xEv-DO protocol may provide for transmission of up to 1.2288 million chips per second.
Macro signals in environments of the access terminals, which normally provide timing information, may be weak. For this reason, it may be difficult to decode sync messages included in macro signals for CDMA communication. Accordingly, it is desirable to recover absolute time from the timing pattern of weak macro signals provided by a BTS. A process for obtaining this absolute time is described below with respect to
Referring to
Referring to
Referring again to
As shown in an enlarged view 314 of frame 308, macro BTS 108 sends a synchronous capsule 316 of a predetermined length, within 0-3 slots offset from a start 318 of each control channel cycle 304. The synchronous capsule 316 may be spread over non-contiguous slots that are spaced apart from each other by a predetermined number of slots, e.g., 4 slots. In the enlarged view 314, only a first slot of the synchronous capsule 316 is shown. The synchronous capsule 316 typically includes control information transmitted at 38.4 or 76.8 kb/s, scrambled with the PN short code 400.
The boundary 320 of the synchronous capsule 316 is at the beginning of one of the first four slots 324a-d (slots 0, 1, 2 and 3) immediately following the boundary 328 of the first macro signal frame 308 in the control channel cycle 304. The location of the boundary 320 of the synchronous capsule 316 may depend on the sector 102a. The 1xEV-DO protocol provides that the position of the boundary 320 of the synchronous capsule 316 is indicated by a data chip sequence or a preamble comprising 1,024 (for a chip rate of 38.4 kb/s) or 512 (for a chip rate 76.8 kb/s) chips. Accordingly, the preamble is a 64-chip signed Walsh cover corresponding to specialized indices, e.g., Medium Access Control (MAC) indices 2 or 3. The Walsh covers may be [+1 −1 +1 −1 . . . ] and [−1 +1 −1 +1 . . . ] sequences.
Since there are 800 available data chips in each half-slot 402, the preamble of the synchronous capsule 316 extends over a predetermined portion belonging to one or two half-slots 402. In general, references to timing boundaries in this description refer to one or more boundaries in the macro signal 300, such as, for example, boundaries of half-slots 402, frames 308, synchronous capsules 316 and control channel cycles 304.
Absolute time is generally determined relative to a standard. For example, the 1xEV-DO provides a CDMA system time of Jan. 6, 1980 00:00:00 UTC (Coordinated Universal Time, also the beginning of GPS time) as the start time of a control channel cycle 304 that is substantially the same across one or more sectors 102a in one or more cells 102.
The 1xEV-DO protocol provides that a BTS transmits a synchronization macro signal, e.g., a sync message, in at least every three synchronous capsules. The sync message contains an indication of the current time expressed in number of macro signal frames 308 since the time origin as well as a value of a PN offset 412. Each access point may be configured to decode the sync message to thereby obtain the absolute time.
The process of synchronizing an access point, such as access point 202, typically has two aspects. In a first aspect known as frequency synchronization, the chip rate used by the access point 202 matches the chip rate used in the macro signal 300. This may be accomplished by processing a pilot portion, such as the pilot signal based the short PN code 400, of the macro signal 300. In a second aspect, known as absolute time synchronization, the access point 202 associates an absolute time of transmission with each chip it receives. This may be accomplished by associating an absolute, e.g., UTC, time with an identifiable chip, such as the start of the control channel cycle 318 or boundary 328 of frame 308.
The access point 202 determines the location of the boundary 404 of the PN short code 400 in the macro signal 300. Various methods for synchronizing the access point 202 to pilot using the PN short code 400, and determining the position of the boundary 404 of the PN short code 400 and the position of the half slot boundaries are known to persons skilled in the art.
The access point 202 determines the location of the boundary 404 of the PN short code 400 by correlating the pilot portion of the macro signal 300 that is received (oversampled at a multiple X of the chip rate, e.g., X=1 or 2 times the chip rate) with delayed copies of a PN short code generated by the access point 202 and locating a region of significant peaks (for example, a region of width, W).
In some situations, an initial clock frequency of the access point 202 does not match that used by the macro base transceiver station 108. As a result, it is not possible to correlate coherently over long periods of time. If the relative frequency error does not exceed 10−6, which can be achieved by temperature compensated crystal oscillators, coherent correlation is possible over 96 pilot chips in a half slot. As the frequency error decreases, coherent correlation can be effected on groups of several consecutive half slots. Correlation across these groups can be done by using non coherent accumulation, or by performing coherent modulation with a set of hypothesized frequency errors.
The access point 202 obtains a power profile of a channel response over a window region W while correlating the macro signal 300 that is received from the macro base transceiver station 108 to the delayed copies of the PN short code 400. The power profile is obtained in a manner similar to a moving average. However, if time drift compensation is not implemented, the frequency error also contributes to a non-coherent accumulation of an energy profile during the correlation process because a 10−6 error translates into a 1.25 chip offset per second. The maximum accumulation time is of the order of 800/X ms in order to achieve accurate channel delay power profile.
In some examples, the access point 202 acquires the macro signals 300 of all base transceiver stations 108 within range of the access point 202. The access point 202 then detects the pilot signal of the PN short code 400 corresponding to the strongest macro signal 300 from a macro base transceiver station 108. Subsequently, the access point 202 begins to look for the second strongest macro signal (not shown), possibly after canceling the strongest macro signal 300.
Referring to
Subsequently, the access point 202 determines the boundary 320 of the synchronous capsule 316 by detecting a predetermined chip sequence (808 of
In some examples, the access point 202 determines the location of the boundary 320 of the synchronous capsule 316 by known processing techniques, such as rake filtering, PN despreading and multiplying an in-phase component (PNI component) of the PN short code 400 by the [+1 −1 +1 −1 . . . ] or [−1 +1 −1 +1 . . . ] synchronous capsule pre accumulating over a predetermined number, e.g., 512, of chips. The accumulation can be effected over many successive synchronous capsules.
The synchronous capsule boundary is offset from the control channel boundary by a number of slots varying between 0 and 3 (324a-d of
If the macro signal 300 is strong enough, the access point 202 decodes the synchronous capsule 316, and eventually the sync message, which contain enough information to obtain the UTC time at the macro base transceiver station 108 at the start of the current control channel cycle 304. With this information, the absolute time of all subsequent chips and macro signal frames 308 can be determined.
In some examples, the macro signal 300 is too weak for the receiver 202 to decode the sync message. In such situations, the receiver 202 exploits one or more timing patterns in the macro signal 300 to retrieve the position of a control channel cycle boundary with the help of the server 203.
In some examples, if the access point 202 is within range of the macro signals 300 from a predetermined number of distinct macro base transceiver stations 108, corresponding to the smallest and largest possible values for the synchronous capsule slot offsets 324a-d, then further processing is not needed.
In these situations, the start time of the current control channel cycle 304 is known from the position of the synchronous capsule slots 324a-d with smallest offset. Accordingly, the access point 202 only needs to request a start time for the current control channel cycle 304 from the server 201.
However, if the predetermined number of distinct macro signals 300 are unavailable, the access point 202 will need to take the assistance of the network server database 209 in the server 203 as described in further detail below.
The access point 202 then measures the offset between the boundary of the synchronous capsule and the boundary of the PN short code, S (812 of
The access point 202 then sends the carrier frequency of a macro signal, e.g. macro signal 300 corresponding to sector 102a, and the offset S corresponding to the distance between the boundary 320 of the synchronous capsule 316 and the boundary 328 of the macro signal frame 308 to the server 203 (816 of
In some examples, the access point 202 also sends a “PN offset delta” that is the difference, expressed as a multiple of 64 chips, between a boundary 404 of the PN short code 400 of a first sector 102a of the cell 102 and a boundary of a PN short code of a second sector 102b of the cell 102, as well as their carrier frequencies, to the server 203. Accordingly, the first sector 102a is designated a reference sector and a subsequently acquired sector, e.g., the second sector 102b, is designated a current sector. The second sector 102b can also transmit 1xRTT signals as it uses a PN short code 400 that is compatible with that of the 1xEV-DO protocol.
The database 209 includes information about all the sectors 102a and/or macro base transceiver stations 108. In some implementations, the database 209 is also configured to store location information of the access point 202. For example, the database 209 is configured to store a street address, a zip code or, in some situations, latitude and longitude information. In some implementations, the location information is provided by a service manager, or the access point 202 itself.
At the server 203, at least one of the carrier frequency, the offset and the PN offset delta for each received macro signal 300 is matched with the network server database 209 (820 of
In some examples, the access point 202 receives macro signals 300 from macro base transceiver stations 108 corresponding to three sectors 102a. As shown in Table 1, the access point 202 acquires three distinct macro signals 300, e.g., entries 1, 2 and 3 (column 1), having frequencies F1, F2, and F2, respectively (column 2).
As described above, the access point 202 determines the offset, S (column 3) between the boundary 320 of the synchronous capsule 316 and the boundary 404 of the PN short code 400, expressed as a multiple of 64 chips. In some examples, the access point 202 also determines the PN offset delta (column 4) for a sector, e.g. sector 102b, by computing the distance between the boundary 404 of the PN short code 400 corresponding to sector 102b and the boundary 404 of the PN short code 400 corresponding to the first sector, e.g., 102a, which is used as a reference sector.
The database 209 in the server 203 includes information for all the sectors, e.g., 102a-c, 104a-c and 106a-c, corresponding to the cells 102, 104 and 106, of the radio access network (RAN) 100. For example, information is stored in the database 209 as shown in Table 2. In some examples, the database 209 can also include information about the access points 202 such as rough geographical location, e.g., street name/address, zip code or latitude and longitude information.
As shown, the database 209 includes a sector number or ID (column 1), a carrier frequency of the macro base transceiver station 108 corresponding to the sector 102 (column 2), the PN offset 412 (column 3), the synchronous capsule slot offset 324a-d (column 4) and the offset, S (column 5) between the boundary 320 of the synchronous capsule 316 and the boundary 404 of the PN short code 400, expressed in multiples of 64 chips, modulo 512, for each sector 102a.
In some implementations, the server 203 matches a value, e.g., value 33, received from an access point 202 with the entry of the offset, S (column 5) corresponding to sector 2 (column 1) in the database 209. The server 203 then returns a slot offset 324a-d (column 4) to the access point 202. In these implementations, there is only one match having the offset, S (column 5) being 33. In some implementations, there can be several such matches.
In some examples, an ambiguity can also be resolved by using the PN offset differences received from access point 202. Accordingly, in some implementations, the server 203 determines values for the PN offset delta (column 4) for at least three entries corresponding to distinct macro signals 300 as being 0, 11, and 35.
Referring once again to Table 2, the difference between the PN offset for sector 1, at frequency, F1, and the PN offsets for sectors 4, 5, and 6, at frequency, F2, are 31, 53 and 55. Also, the difference between the PN offset for sector 2, at frequency, F2, and the PN offsets for sectors 4, 5, and 6, at frequency, F2 are 11, 33 and 35, respectively.
As a result, the server 203 successfully matches the PN offset delta determined by the access point 202, as shown in Table 1, with the difference between the PN offset for sector 2 and the PN offsets for sectors 4, 5 and 6, respectively. In such situations, the server 203 matches entry 1 (of Table 1) with sector 2 (of Table 2), entry 2 with sector 4 and entry 3 with sector 6. Subsequently, the server 203 returns the slot offset of one sector, i.e. that of sector 2 (the first macro signal acquired by the receiver 202,) to the access point 202.
In some examples, the value of the offset, S is used to directly identify possible reference sectors as described in the first set of examples, and the PN offset matching technique described in the second set of examples is used to identify a correct reference sector.
Obtaining Absolute Time from an NTP Server
To associate an absolute, e.g., UTC, time with an identifiable chip, such as the start of the control channel cycle 318 or boundary 328 of frame 308, the access point obtains the absolute time. The absolute time may be obtained from a time server, such as a network time protocol (NTP) server, as long as the propagation delay from the access point to the server does not exceed a control channel cycle duration. Processes for obtaining the absolute time are described below.
Referring to
At about the beginning of a CDMA control channel cycle boundary 500, access point 202 sends (601) a request to an NTP server 201 for the current time. Access point 202 and NTP server 201 are identified by their respective time lines in
NTP server 201 receives the request, and responds with the current time, which is referred to as the “server time”. The response by NTP server 201 is depicted by arrow 509, going from NTP server 201 to access point 202. Another such response is depicted by arrow 511. As depicted in
Access point 202 receives (602) the response from NTP server 201. The response includes server time 517. Access point 202 obtains (603) the CDMA control channel cycle boundary time (timing information) using server time 517. In this implementation, access point 202 executes code, which may be stored on access point 202, to obtain the CDMA control channel cycle boundary. However, such code may be executed elsewhere to provide access point 202 with the CDMA control channel cycle boundary.
The CDMA control channel cycle boundary time may be determined with respect to a reference time. In this example, a reference time is Jan. 6, 1980. Time since the reference time is divided into time intervals which, in this case, are about 400 millisecond intervals (ms). These 400 ms intervals correspond to CDMA control channel cycles.
Access point 202 may use one of several processes to determine a time at the CDMA control channel cycle boundary 500. For example, access point 202 may use the server time and a first reference time to obtain an integer and a fraction, use the fraction to obtain a time difference; and use the time difference to obtain the timing information. In more detail, access point 202 may determine the absolute (e.g., not local) time at the CDMA control channel cycle boundary as follows. Access point 202 determines the number of CDMA control channel cycles 704 since the reference time as follows:
(T2−TJan. 6, 1980)/0.4s=Integer (N)+Fraction (x/0.4s)
That is, the integer N in this case corresponds to the number of CDMA control channel cycles 704 since the reference time. The value of “x” corresponds to the difference 706 between the CDMA control channel cycle boundary T1 and T2. To obtain the time at the CDMA control channel cycle boundary, access point 202 multiplies the Integer, N, by the time interval, here 400 ms. Access point 202 may normalize the product of N and 400 ms with respect to the second reference time to obtain the time at CDMA control channel cycle boundary 500. For example, if the access point uses an internal time that is not based on a reference time, such as Jan. 6, 1980, the access point can obtain an absolute time by adding an offset (e.g., a second reference time, such as Unix® time or Windows® time) to the product of N and 400 ms.
In an alternative process, access point 202 may multiply the fraction above, x/0.4s, by 0.4s to obtain x, which corresponds to the difference 706 between the CDMA control channel cycle boundary T1 (500) and T2 (517). Access point 202 may then subtract x from T2 to obtain T1.
Process 600 is described in the context of a femtocell and an NTP server; however, it may be used with any type(s) of access point(s) and/or time server(s).
The techniques described herein can be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. The techniques can be implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device such as a computer-readable storage medium, 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.
Actions associated with the techniques described herein can be performed by one or more programmable processors executing a computer program to perform functions described herein by operating on input data and generating output. Actions associated with the techniques can also be performed by, and apparatus for implementing the techniques can include, e.g., 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.
The computing system can include clients and servers. A client and server are generally remote from each other and typically interact over a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
Components of different embodiments described herein may be combined to form other embodiments not specifically set forth above. Any features described herein may be combined with features found in U.S. application Ser. No. 11/958,975.
Other embodiments not specifically described herein are also within the scope of the following claims.
This patent application is a continuation-in-part application of U.S. patent application Ser. No. 11/958,975 titled “Absolute Time Recovery”, which was filed on Dec. 18, 2007. The contents of U.S. patent application Ser. No. 11/958,975 are hereby incorporated by reference into this application as if set forth herein in full.
Number | Name | Date | Kind |
---|---|---|---|
4677617 | O'Connor et al. | Jun 1987 | A |
5172396 | Rose et al. | Dec 1992 | A |
5363110 | Inamiya | Nov 1994 | A |
5736964 | Ghosh et al. | Apr 1998 | A |
5812749 | Fernandez et al. | Sep 1998 | A |
5898929 | Haartsen | Apr 1999 | A |
6369751 | Naruse | Apr 2002 | B1 |
6433739 | Soliman | Aug 2002 | B1 |
6438702 | Hodge | Aug 2002 | B1 |
6477154 | Cheong et al. | Nov 2002 | B1 |
6549559 | Kamgar et al. | Apr 2003 | B2 |
6581110 | Harif et al. | Jun 2003 | B1 |
6711144 | Kim et al. | Mar 2004 | B1 |
6731618 | Chung et al. | May 2004 | B1 |
6741862 | Chung et al. | May 2004 | B2 |
6781999 | Eyuboglu et al. | Aug 2004 | B2 |
6813478 | Glazko et al. | Nov 2004 | B2 |
7009948 | Carlsson et al. | Mar 2006 | B1 |
7170871 | Eyuboglu et al. | Jan 2007 | B2 |
7200391 | Chung et al. | Apr 2007 | B2 |
7242958 | Chung et al. | Jul 2007 | B2 |
7277446 | Abi-Nassif et al. | Oct 2007 | B1 |
7299278 | Ch'ng | Nov 2007 | B2 |
7301987 | Edlis et al. | Nov 2007 | B2 |
8138945 | Hayakawa et al. | Mar 2012 | B2 |
20010010505 | Naruse | Aug 2001 | A1 |
20010026547 | Moulsley et al. | Oct 2001 | A1 |
20010046872 | Masuda | Nov 2001 | A1 |
20020014990 | Kimura | Feb 2002 | A1 |
20020072853 | Sullivan | Jun 2002 | A1 |
20020110151 | Dickey | Aug 2002 | A1 |
20020129291 | Gonzalez | Sep 2002 | A1 |
20020196749 | Eyuboglu et al. | Dec 2002 | A1 |
20030012174 | Bender et al. | Jan 2003 | A1 |
20030016702 | Bender et al. | Jan 2003 | A1 |
20030026240 | Eyuboglu et al. | Feb 2003 | A1 |
20030040869 | Nir et al. | Feb 2003 | A1 |
20030084190 | Kimball | May 2003 | A1 |
20030100311 | Chung et al. | May 2003 | A1 |
20030103475 | Heppe et al. | Jun 2003 | A1 |
20040029591 | Chapman et al. | Feb 2004 | A1 |
20040042576 | Anderson | Mar 2004 | A1 |
20040085938 | Tiedemann et al. | May 2004 | A1 |
20040098506 | Jean | May 2004 | A1 |
20040120386 | Grilli et al. | Jun 2004 | A1 |
20040125822 | Jun et al. | Jul 2004 | A1 |
20040131032 | Sendonaris et al. | Jul 2004 | A1 |
20040203853 | Sheynblat | Oct 2004 | A1 |
20040249949 | Gourraud et al. | Dec 2004 | A1 |
20050043046 | Lee | Feb 2005 | A1 |
20050048969 | Shaheen et al. | Mar 2005 | A1 |
20050053047 | Osterloh et al. | Mar 2005 | A1 |
20050063358 | Houghton et al. | Mar 2005 | A1 |
20050078032 | Gilkes | Apr 2005 | A1 |
20050135194 | Ishii | Jun 2005 | A1 |
20050138531 | Kim | Jun 2005 | A1 |
20050177591 | Kanda et al. | Aug 2005 | A1 |
20050213555 | Eyuboglu et al. | Sep 2005 | A1 |
20050243749 | Mehrabanzad et al. | Nov 2005 | A1 |
20050245279 | Mehrabanzad et al. | Nov 2005 | A1 |
20050281231 | Kwon et al. | Dec 2005 | A1 |
20060046762 | Yoon et al. | Mar 2006 | A1 |
20060067422 | Chung | Mar 2006 | A1 |
20060067451 | Pollman et al. | Mar 2006 | A1 |
20060125685 | Jeon et al. | Jun 2006 | A1 |
20060126509 | Abi-Nassif | Jun 2006 | A1 |
20060159045 | Ananthaiyer et al. | Jul 2006 | A1 |
20060219087 | Yanase et al. | Oct 2006 | A1 |
20060240782 | Pollman et al. | Oct 2006 | A1 |
20060291420 | Ng | Dec 2006 | A1 |
20060294241 | Cherian et al. | Dec 2006 | 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 |
20070115896 | To et al. | May 2007 | A1 |
20070133501 | Park | Jun 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 |
20070155329 | Mehrabanzad et al. | Jul 2007 | A1 |
20070159321 | Ogata et al. | Jul 2007 | A1 |
20070206838 | Fouquet | Sep 2007 | A1 |
20070220573 | Chiussi et al. | Sep 2007 | A1 |
20070230419 | Raman et al. | Oct 2007 | A1 |
20070238442 | Mate et al. | Oct 2007 | A1 |
20070238476 | Raman et al. | Oct 2007 | A1 |
20070242648 | Garg et al. | Oct 2007 | A1 |
20070248042 | Harikumar et al. | Oct 2007 | A1 |
20070280098 | Bhatt et al. | Dec 2007 | A1 |
20080003988 | Richardson | 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 |
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 |
20080183525 | Tsuji et al. | Jul 2008 | A1 |
20080212518 | Wells | Sep 2008 | A1 |
20080253550 | Ch'ng et al. | Oct 2008 | A1 |
20080304604 | Oh | Dec 2008 | A1 |
20080318557 | Poulson et al. | Dec 2008 | A1 |
20090156195 | Humblet | Jun 2009 | A1 |
20090161638 | Mullen | Jun 2009 | A1 |
20100066601 | Abraham et al. | Mar 2010 | A1 |
20100069035 | Johnson | Mar 2010 | A1 |
20100074180 | Palanki et al. | Mar 2010 | A1 |
20100226214 | Irie et al. | Sep 2010 | A1 |
20110110360 | Fenwick et al. | May 2011 | A1 |
Number | Date | Country |
---|---|---|
2452688 | Mar 2009 | GB |
Entry |
---|
Office action from U.S. Appl. No. 11/958,975, mailed Nov. 30, 2011 (9 pages). |
Fish & Richardson, P.C., Response to Non Final Office Action mailed Nov. 30, 2011 in U.S. Appl. No. 11/958,975, filed Mar. 30, 2012 (21 pages). |
Wu, Qiang et al., “cdma2000 Highly Detectable Pilot”, 2008 IEEE, pp. 16-20. |
3rd Generation Partnership Project “3GPP2”, “cdma2000 High Rate Packet Data Air Interface Specification”, C.S0024, version 4.0, Oct. 25, 2002 (548 pages). |
3rd Generation Partnership Project “3GPP2”, “cdma2000 High Rate Packet Data Air Interface Specification”, C.S0024-A, version 1.0, Mar. 2004 (1083 pages). |
3rd Generation Partnership Project “3GPP2”, “cdma2000 High Rate Data Air Interface Specification”, C.S0024-A, version 2.0, Jul. 2005 (1227 pages). |
3rd Generation Partnership Project “3GPP2”, “cdma2000 High Rate Data Air Interface Specification”, C.S0024-B, version 1.0, Apr. 2006 (1623 pages). |
3rd Generation Partnership Project “3GPP2”, “cdma2000 High Rate Data Air Interface Specification”, C.S0024-B, version 2.0, Mar. 2007 (1627 pages). |
Number | Date | Country | |
---|---|---|---|
20090156195 A1 | Jun 2009 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11958975 | Dec 2007 | US |
Child | 12343850 | US |