Patent Grant
8520659
This description relates to absolute time recovery in wireless networks.
Cellular wireless communications systems are designed to serve many access terminals distributed in a large geographic area by dividing the area into cells, as shown in
Occasionally, macro signals in the environments of the access terminals 114, which normally provide timing information, are weak. For this reason, it is difficult to decode, for example, sync messages, included in the macro signals. Accordingly, it is desirable to recover absolute time from the timing pattern of weak macro signals provided by a local base transceiver station 108.
The 1x EV-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-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-856-B, 3GPP2 C.S0024-B and is also incorporated herein by reference. Other wireless communication protocols can also be used.
In general, in one aspect, a method includes receiving from a server, information that is based on an offset between a boundary of a synchronous capsule in a control channel cycle occurring at an access point and a boundary of a periodic pseudo-noise sequence, and synchronizing an access point to an absolute time based on the information.
The following are embodiments within the scope of this aspect.
The information comprises at least one of a UTC time at a beginning of the control channel cycle and a synchronous capsule offset. The method also includes synchronizing the access point to the periodic pseudo-noise sequence. The beginning the periodic pseudo-noise sequence immediately precedes the boundary of the synchronous capsule. The method also includes transmitting, to the server, a carrier frequency corresponding to each macro signal acquired by the access point.
The method also includes transmitting to the server a difference between a first boundary of a PN short code of a current sector and a second boundary of a PN short code of a reference sector. In addition, the method includes transmitting to the server a first carrier frequency corresponding to a current sector and a second carrier frequency corresponding to a reference sector. The control channel cycle is a current control channel cycle.
The server is configured to store location information for each access point. The location information comprises at least one of a street address, a zip code, a latitude and a longitude. The method of claim 1 also includes identifying the boundary of the synchronous capsule by detecting a preamble of the synchronous capsule.
In another aspect, a method includes receiving a UTC time corresponding to a beginning of a control channel cycle, and synchronizing an access point to the UTC time, if at least a predetermined number of sectors, each having a unique synchronous capsule offset, is acquired by the access point. In an embodiments within the scope of this aspect, the predetermined number of sectors acquired by the access point is at least two. In some examples, receiving a UTC time corresponding to the beginning of the control channel cycle is in response to the detection of a boundary of a synchronous capsule.
In another aspect, a method includes synchronizing an access point to a periodic pseudo-noise sequence in a macro signal, and establishing absolute time synchronization based on at least a boundary of a synchronous capsule in a control channel cycle occurring at the access point and a beginning of the periodic pseudo-noise sequence that immediately precedes the boundary of the synchronous capsule.
In some embodiments within the scope of this aspect, establishing absolute time synchronization includes receiving information from a server based on an offset between the boundary of the synchronous capsule in the control channel cycle occurring at the access point and the beginning of the periodic pseudo-noise sequence, and establishing absolute time synchronization based on the information. In some examples, synchronizing the access point to the periodic pseudo-noise sequence comprises detecting a pilot signal burst in at least one frame of the current control channel cycle.
In another aspect, a method includes receiving a difference between a first boundary of a first PN short code corresponding to a current sector and a second boundary of a second PN short code corresponding to a reference sector, determining information corresponding to the current sector based on the difference, and transmitting the information corresponding to the current sector to an access point.
The following are embodiments within the scope of this aspect.
The method also includes receiving carrier frequencies of a plurality of macro signals acquired by the access point. The information is at least one of a slot offset between a boundary of a frame and a boundary of a synchronous capsule and a UTC time of the synchronous capsule for the current sector. In some examples, the information is at least one of a slot offset between a boundary of a frame and a boundary of a synchronous capsule and a UTC time at a beginning of a periodic pseudo-noise sequence for the reference sector. Determining information corresponding to the current sector is also based on location information of each access point. The location information is at least one of a street address, a zip code, a latitude and a longitude.
In another aspect, an apparatus includes an access point configured to receive information that is based on an offset between a boundary of a synchronous capsule in a current control channel cycle occurring at the access point and a beginning of a periodic pseudo-noise sequence, and synchronize the access point to an absolute time based on the information.
The following are embodiments within the scope of this aspect.
The information includes at least one of a UTC time at a beginning of the control channel cycle and a synchronous capsule offset. The access point is configured to also synchronize the access point to the periodic pseudo-noise sequence.
The beginning the periodic pseudo-noise sequence immediately precedes the boundary of the synchronous capsule. The access point is configured to also transmit, to a server, a carrier frequency corresponding to each macro signal acquired by the access point. The access point is configured to also transmit, to a server, a difference between a first boundary of a PN short code of a current sector and a second boundary of a PN short code of a reference sector.
The control channel cycle is a current control channel cycle. The server is configured to store location information for each access point. The location information includes at least one of a street address, a zip code, a latitude and a longitude. The access point is also configured to identify the boundary of the synchronous capsule by detecting a preamble of the synchronous capsule.
In another aspect, an apparatus includes a server configured to receive a difference between a first boundary of a first PN short code corresponding to a current sector and a second boundary of a second PN short code corresponding to a reference sector, determine information corresponding to the current sector based on the difference, and transmit the information corresponding to the current sector to an access point.
The following are embodiments within the scope of this aspect.
The server is configured to also receive a carrier frequency corresponding to each macro signal acquired by the access point. The information is at least one of a slot offset between a boundary of a frame and a boundary of a synchronous capsule, and a UTC time of the synchronous capsule for the current sector. In some examples, the information is at least one of a slot offset between a boundary of a frame and a boundary of a synchronous capsule, and a UTC time at a beginning of a periodic pseudo-noise sequence for the reference sector. The server is configured to determine information corresponding to the current sector is also based on location information of each access point. The location information is at least one of a street address, a zip code, a latitude and a longitude.
In another aspect, a computer readable medium comprising instructions to cause an access point to receive information that is based on an offset between a boundary of a synchronous capsule in a current control channel cycle occurring at the access point and a beginning of a periodic pseudo-noise sequence, and determine an absolute start time of the current control channel cycle based on the absolute time signal.
The following are embodiments within the scope of this aspect.
The medium includes instructions to cause the access point to synchronize to the periodic pseudo-noise sequence. The beginning the periodic pseudo-noise sequence immediately precedes the boundary of the synchronous capsule. The medium includes instructions to cause the access point to also transmit, to a server, a carrier frequency corresponding to each macro signal acquired by the access point. The medium includes instructions to cause the access point to also transmit, to a server, a difference between a first boundary of a PN short code of a current sector and a second boundary of a PN short code of a reference sector.
The control channel cycle is a current control channel cycle. The location information comprises at least one of a street address, a zip code, a latitude and a longitude. The information comprises at least one of a UTC time at a beginning of the control channel cycle and a synchronous capsule offset. The medium includes instructions to cause the access point to identify the boundary of the synchronous capsule by detecting a preamble of the synchronous capsule.
In another aspect, a computer readable medium includes instructions to cause a server to receive a difference between a first boundary of a first PN short code corresponding to a current sector and a second boundary of a second PN short code corresponding to a reference sector, determine information corresponding to the current sector based on the difference, and transmit the information corresponding to the current sector to an access point.
The following are embodiments within the scope of this aspect.
The medium also includes instructions to cause a server to also receive a carrier frequency corresponding to each macro signal acquired by the access point. The information is at least one of a slot offset between a boundary of a frame and a boundary of a synchronous capsule, and a UTC time of the synchronous capsule for the current sector. In some examples, the information is at least one of a slot offset between a boundary of a frame and a boundary of a synchronous capsule, and a UTC time at a beginning of a periodic pseudo-noise sequence for the reference sector.
The medium includes instructions to also cause the server to determine information corresponding to the current sector based also on location information of each access point. The location information is at least one of a street address, a zip code, a latitude and a longitude.
In another aspect, a method includes receiving from a server, information that is based on an offset between a first timing boundary and a second timing boundary, and synchronizing an access point to an absolute time based on the information.
In embodiments within the scope of this aspect, the first timing boundary is a boundary of at least one of a frame, a periodic pseudo-noise sequence, a control channel cycle and a synchronous capsule occurring in a macro signal. Also, in some examples, the first timing boundary is in a first macro signal and the second timing boundary is in a second macro signal.
Other aspects and features and combinations of them can be expressed as methods, apparatus, systems, program products, means for performing functions, and in other ways. Other advantages and features will become apparent from the following description and claims.
Referring to
The access terminals 114 are typically 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 114 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 LAN.
In some examples, the functions of the base transceiver station 108 and the radio network controller (RNC) 120a are combined into a single device. In addition, the functions of the PDSN 120b and the radio network control (RNC) 120a are typically combined into a single device. In some implementations, functions of the base transceiver station 108, the RNC 120a and the PDSN 120b are additionally combined into the same device.
The implementations in this disclosure 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.
Each access terminal 114 is in communication with a base transceiver station 108 through an air link 124. The air link 124 includes a forward link 124a (also referred to as a downlink), which carries data from a base transceiver station 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 base transceiver station 108.
In some examples, as shown in
Typically, an access point 202 uses an available high-speed internet connection, such as a connection over a DSL modem 204 or a cable modem 214, for connection to the backhaul 118. In some examples, the access points 202 are in communication with a network 219, e.g., a remote network or the Internet. Generally, the access points 202 communicate with the network 219 through a backhaul connection 218, e.g., a digital subscriber line (DSL) or a cable connection. As shown, the network 219 includes one or more remote network servers, e.g., servers 201 and 203. In some implementations, a network server database, e.g., database 209, described in further detail below, is included within at least one of the network servers, e.g., server 203. In some implementations, the database 209 is included within the same server 201 as a time server. In some implementations, the network server database 209 includes the time server (not shown).
When an authorized access terminal, e.g., access terminals 206, 216 is inside a home (or anywhere within range of the access point 202), it uses the access point 202 rather than the macro base transceiver station 108 to place or receive voice calls and establish data connections. In some examples, the access point 202 is integrated into or connected to the cable modem 204, a WiFi access point (not shown), or other network hardware (such as the router 117a in
In general, the 1xEv-DO protocol provides for digital messages, i.e., messages transmitted over the air link 124, to be communicated to and from one or more access terminals 114, and macro base transceiver stations 108 in the radio access network 100. The messages transmitted over the air link 124 are typically provided to, for example, report statuses of the access terminals 114, send requests to the macro base transceiver stations 108, adjust configurations of the access terminals 114, and transmit user data.
Typically, the access points 202, 212 are configured to receive radio signals 205 from the macro base transceiver station 108. Accordingly, in some examples, the access points 202 and 212 do not transmit signals to the macro base transceiver station 108 but listen to the radio signals 205 transmitted by the macro base transceiver station 108.
The digital messages from the macro base transceiver stations 108 are communicated as “chips,” which form the basic signal elements in a CDMA waveform. In some examples, the 1xEv-DO protocol provides for the transmission of up to 1.2288 million chips per second.
As shown in
Referring briefly to
A boundary 404 of the PN short code 400 is offset from a boundary 408 of the macro signal frame 308 by a PN offset 412. In some examples, the PN offset 412 is substantially unique for each sector 102a in the local environment of the access point 202, at a given carrier frequency. The 1xEv-DO protocol provides for 512 PN offsets, often described as PN offset indices 0 to 511. Accordingly, the PN offset indices are separated from each other by 64 chips.
Referring again to
As shown in an enlarged view 314 of the frame 308, the macro base transceiver station 108 sends a synchronous capsule 316 of a predetermined length, within 0-3 slots offset from the start 318 of each control channel cycle 304. In some examples, the synchronous capsule 316 is 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. In some examples, the location of the boundary 320 of the synchronous capsule 316 depends on the sector 102a.
The 1x Ev-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. In some examples, the Walsh covers are [+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 1x EV-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 1x EV-DO protocol provides that the base transceiver station 108 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. In some examples, the access point 202 is configured to decode the sync message.
The process of synchronizing an 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. In some examples, this is accomplished by processing a pilot portion, i.e., 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. In some examples, this is accomplished by associating a UTC time received in a message with an identifiable chip, such as, for example, the start 318 of the control channel cycle 318 or the boundary 328 of the 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.
As shown in
Subsequently, the access point 202 determines the boundary 320 of the synchronous capsule 316 by detecting a predetermined chip sequence. (Step 508) In some examples, the access point 202 processes at least a predetermined number, e.g., 512, of simultaneous chips corresponding to the length of the preamble of the synchronous capsule 316 to determine the location of the boundary 320 of the synchronous capsule 316.
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 . . . ] sequence and accumulating over a predetermined number, e.g., 512, of chips. The accumulation can be effected over many successive synchronous capsules.
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 access 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 absolute time with the help of the server 201.
The server 201 returns the UTC time in response to a request from an access point 202. In some examples, the network server automatically transmits the UTC time at the beginning of every control channel cycle, i.e., every 400 ms, to all access points 202. In some examples, the access points 202 sends a request to the network server 201 for the UTC time on detecting a boundary 320 of the synchronous capsule 316 which is substantially close to the beginning of a control channel cycle 304. In some examples, for accurate operation, the backhaul delay between an access point 202 and the server 201 must not exceed the duration of a control channel cycle, e.g., 400 ms.
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. (Step 512) In some examples, the interference from strong macro signals while detecting the boundary 320 of the synchronous capsule 316 in a weak macro signal 300 cannot be cancelled. However, in these situations, only one synchronous capsule 316 in a weak macro signal 300 needs to be detected. As such, the effect of the interference is minimal.
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. (Step 516) In some examples, the access point 202 sends several such offsets, corresponding to different macro signals to the server 203.
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 1x EV-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. (Step 520) The server 203 then returns information based on the frequency, offset and PN offset delta for each macro signal 300. For example, the server 203 returns the UTC time for the synchronous capsule 316 belonging to the macro signal 300 corresponding to at least one sector 102a within range of the access point 202, as well as a synchronous capsule slot offset, e.g., one of slot offsets 324a-d, to the access point 202. (Step 524)
In some examples, the server 203 returns the UTC time at the beginning of the PN short code 400 for the macro signal 300 corresponding to at least one sector 102a within range of the access point 202, as well as a PN offset 412 used by the sector 102a. The server 203 also returns the synchronous capsule slot offset 324a-d for at least one macro signal, e.g., macro signal 300. Accordingly, the information from the server 203 allows the access point 202 to achieve absolute time synchronization.
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 the UTC time of a start 318 of the most recent control channel cycle 304 as well as 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 UTC time of a start 318 of the most recent control channel cycle 304 as well as the slot offset, i.e., one, 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. If a predetermined number of PN offset deltas is measured and communicated to the server 203 to uniquely identify a reference sector and if the backhaul delay does not exceed the duration of a short PN code 400, then there is typically no need to identify a boundary 320 of a synchronous capsule 316 and transmit the offset, S to the server 203. The server 203 returns the UTC time of the latest boundary 404 of the short PN code 400 of the reference sector, as well as its PN offset 412.
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 described herein 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.
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.
Other embodiments are within the scope of the following claims. For example, the techniques described herein can be performed in a different order and still achieve desirable results.
| 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 |
| 7558356 | Pollman et al. | Jul 2009 | B2 |
| 7558588 | To et al. | Jul 2009 | 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 |
| 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 |
| 20080254792 | Ch'ng | Oct 2008 | A1 |
| 20080304604 | Oh | Dec 2008 | A1 |
| 20080318557 | Poulson et al. | Dec 2008 | A1 |
| 20090034440 | Samar et al. | Feb 2009 | A1 |
| 20090082020 | Ch'ng et al. | Mar 2009 | A1 |
| 20090088155 | Kim | Apr 2009 | A1 |
| 20090116445 | Samar et al. | May 2009 | A1 |
| 20090154447 | Humblet | Jun 2009 | A1 |
| 20090156165 | Raghothaman et al. | Jun 2009 | A1 |
| 20090156195 | Humblet | Jun 2009 | A1 |
| 20090156218 | Garg et al. | Jun 2009 | A1 |
| 20090161638 | Mullen | Jun 2009 | A1 |
| 20090163202 | Humblet et al. | Jun 2009 | A1 |
| 20090163216 | Hoang et al. | Jun 2009 | A1 |
| 20090163238 | Rao et al. | Jun 2009 | A1 |
| 20090164547 | Ch'ng et al. | Jun 2009 | A1 |
| 20090168766 | Eyuboglu et al. | Jul 2009 | A1 |
| 20090168788 | Den et al. | Jul 2009 | A1 |
| 20090170440 | Eyuboglu et al. | Jul 2009 | A1 |
| 20090170475 | Ch'ng et al. | Jul 2009 | A1 |
| 20090170520 | Jones | Jul 2009 | A1 |
| 20090170547 | Raghothaman et al. | Jul 2009 | A1 |
| 20090172169 | Ch'Ng et al. | Jul 2009 | A1 |
| 20090172397 | Kim | Jul 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 |
|---|
| 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-A, version 2, Jul. 2005 (1227 pages). |
| 3rd Generation Partnership Project 2 “3GPP2”, “cdma2000 High Rate Packet Data Interface Specification”, C.S0024-B, version 1, Apr. 2006 (1623 pages). |
| 3rd Generation Partnership Project 2 “3GPP2”, “cdma2000 High Rate Packet Data Interface Specification”, C.S0024-B, version 2, Mar. 2007 (1627 pages). |
| 3rd Generation Partnership Project 2 “3GPP2”, “cdma2000 High Rate Packet Data Interface Specification”, C.S0024, version 4, Oct. 25, 2002 (548 pages). |
| Wu, Qiang et al., “cdma2000 Highly Detectable Pilot”, 2008 IEEE, pp. 16-20. |
| Office action from U.S. Appl. No. 12/343,850, mailed Apr. 25, 2012 (21 pages). |
| Fish & Richardson, P.C., Response to Non Final Office Action mailed Apr. 25, 2012 in U.S. Appl. No. 12/343,850, filed Aug. 26, 2012 (13 pages). |
| Number | Date | Country | |
|---|---|---|---|
| 20090154447 A1 | Jun 2009 | US |
