Patent Application
20110116358
I. Field
The following description relates generally to wireless communications, and more particularly to selectively inserting Beacon signals in downlink transmission units in a wireless communication system.
II. Background
Wireless communication systems are widely deployed to provide various types of communication; for instance, voice and/or data may be provided via such wireless communication systems. A typical wireless communication system, or network, can provide multiple users access to one or more shared resources. For instance, a system may use a variety of multiple access techniques such as Frequency Division Multiplexing (FDM), Time Division Multiplexing (TDM), Code Division Multiplexing (CDM), Orthogonal Frequency Division Multiplexing (OFDM), and others.
Common wireless communication systems employ one or more base stations that provide a coverage area. A typical base station can transmit multiple data streams for broadcast, multicast and/or unicast services, wherein a data stream may be a stream of data that can be of independent reception interest to a wireless terminal. A wireless terminal within the coverage area of such base station can be employed to receive one, more than one, or all the data streams carried by the composite stream. Likewise, a wireless terminal can transmit data to the base station or another wireless terminal.
Generally, wireless multiple-access communication systems may simultaneously support communication for multiple mobile devices. Each mobile device may communicate with one or more base stations via transmissions on forward and reverse links. The forward link (or downlink) refers to the communication link from base stations to mobile devices, and the reverse link (or uplink) refers to the communication link from mobile devices to base stations.
In a time division duplex (TDD) system, the air interface resource may be used alternately as downlink and uplink transmission units with guard time intervals being added in-between. A downlink transmission unit represents a time interval in which the downlink signal is sent, and an uplink transmission unit represents a time interval in which the uplink signal is sent. In the TDD system, the downlink and uplink transmission units are interleaved with each other. When a TDD system is deployed in a cellular environment, the downlink and uplink transmission units of base stations may be synchronized; accordingly, when one base station is in downlink transmission other base stations may also be in downlink transmission, and when one base station is in uplink transmission other base stations may also be in uplink transmission. Since downlink transmission units from disparate base stations may be synchronized, control data such as Beacons and the like may be simultaneously transmitted by each of the disparate base stations; thus, a mobile device may encounter difficulty associated with discerning control data (e.g., Beacon signals) provided from differing base stations (e.g., disparate cells) at common times.
The following presents a simplified summary of one or more embodiments in order to provide a basic understanding of such embodiments. This summary is not an extensive overview of all contemplated embodiments, and is intended to neither identify key or critical elements of all embodiments nor delineate the scope of any or all embodiments. Its sole purpose is to present some concepts of one or more embodiments in a simplified form as a prelude to the more detailed description that is presented later.
In accordance with one or more embodiments and corresponding disclosure thereof, various aspects are described in connection facilitating generation and/or analysis of downlink transmission units in OFDM TDD environments. A downlink transmission unit includes a number of non-strip OFDM symbols, and may furthermore include one or multiple strip OFDM symbols. While the non-strip OFDM symbols are used to transmit data and control signals, the strip OFDM symbols are mainly used to transmit control signals (e.g., broadcast control signals). A tone hopping scheme is used in the non-strip OFDM symbols to average inter-cell interference and achieve frequency diversity. The tone hopping scheme is not used in the strip OFDM symbols. The operation of coding and modulation in the strip OFDM symbols is done independently of that in the non-strip OFDM symbols. Different types of transmission units are used. A first type of transmission unit includes only non-strip OFDM symbols. A second type of transmission unit is constructed by adding strip OFDM symbols to the first type, in which case the second type of transmission unit has the same number of non-strip OFDM symbols as the first type transmission unit and the tone hopping scheme used in the non-strip symbols of the first and the second type transmission units is the same. Beacon signals may be selectively inserted within the second type downlink transmission units; for example, the position of Beacon signals may vary from cell to cell. Further, the position may be a function of a characteristic of a cell (e.g., cell identifier) and/or an expected drift. Moreover, a Beacon signal may be interjected at a location in a downlink transmission unit so as to mitigate alignment with disparate Beacon signals in downlink transmission units associated with differing cells. Additionally, an identity of a cell providing downlink transmission units may be determined by analyzing a position of the Beacon signal within the downlink transmission units.
According to related aspects, a method that facilitates generating downlink transmission units in an Orthogonal Frequency Division Multiplexing (OFDM) time division duplex (TDD) environment is described herein. The method may include selectively positioning a Beacon signal within a downlink transmission unit based upon a characteristic of a cell. Further, the method may comprise transmitting the downlink transmission unit.
Another aspect relates to a wireless communications apparatus. The wireless communications apparatus may include a memory that retains instructions for determining a time location for a Beacon signal within a downlink transmission unit, determining a subband position for the Beacon signal, and sending the Beacon signal with the time location and the subband position via a downlink. Moreover, the wireless communications apparatus may comprise a processor, coupled to the memory, configured to execute the instructions retained in the memory.
Yet another aspect relates to a wireless communications apparatus that generates downlink transmission units in an OFDM TDD environment. The wireless communications apparatus may include means for selectively interposing a Beacon signal in a downlink transmission unit to mitigate alignment with a disparate Beacon signal between cells; and means for transferring the downlink transmission unit via a downlink.
Still another aspect relates to a machine-readable medium having stored thereon machine-executable instructions for selectively positioning strip OFDM symbols in downlink transmission units, selectively carrying a Beacon signal with a subset of the strip OFDM symbols in the downlink transmission units based upon a characteristic of a cell, and sending the downlink transmission units over a downlink.
In accordance with another aspect, an apparatus in a wireless communication system may include a processor, wherein the processor may be configured to selectively position a Beacon signal within downlink transmission units so as to mitigate alignment with a disparate Beacon signal associated with a disparate cell. Further, the processor may be configured to transfer the downlink transmission units over a downlink.
According to other aspects, a method that facilitates analyzing downlink transmission units in an OFDM TDD environment is described herein. The method may include receiving downlink transmission units from a base station associated with a cell. Further, the method may include analyzing a time position of a Beacon signal included in the downlink transmission units. Moreover, the method may include determining an identity of the cell based upon the time position.
Yet another aspect relates to a wireless communications apparatus that may include a memory that retains instructions for obtaining downlink transmission units that include a Beacon signal from a cell and evaluating a position of the Beacon signal within the downlink transmission units to yield an identity of the cell. Further, the wireless communications apparatus may include a processor, coupled to the memory, configured to execute the instructions retained in the memory.
Another aspect relates to a wireless communications apparatus that employs a downlink transmission unit that includes a Beacon signal in an OFDM TDD environment. The wireless communications apparatus may include means for obtaining a downlink transmission unit; and means for evaluating a Beacon signal selectively interjected within the downlink transmission unit as a function of a cell identifier.
Still another aspect relates to a machine-readable medium having stored thereon machine-executable instructions for receiving downlink transmission units from a plurality of cells, the downlink transmission units include Beacon signals positioned according to characteristics of respective cells, and determining identities of each of the plurality of cells from which the downlink transmission units are obtained based upon positions of the Beacon signals.
In accordance with another aspect, an apparatus in a wireless communication system may include a processor, wherein the processor may be configured to obtain downlink transmission units from a base station associated with a cell. Moreover, the processor may be configured to evaluate a time position of a Beacon signal included in the downlink transmission units. Further, the processor may be configured to determine an identity of the cell based upon the time position.
To the accomplishment of the foregoing and related ends, the one or more embodiments comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative aspects of the one or more embodiments. These aspects are indicative, however, of but a few of the various ways in which the principles of various embodiments may be employed and the described embodiments are intended to include all such aspects and their equivalents.
Various embodiments are now described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more embodiments. It may be evident, however, that such embodiment(s) may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate describing one or more embodiments.
As used in this application, the terms “component,” “module,” “system,” and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems by way of the signal).
Furthermore, various embodiments are described herein in connection with a mobile device. A mobile device can also be called a system, subscriber unit, subscriber station, mobile station, mobile, remote station, remote terminal, access terminal, user terminal, terminal, wireless communication device, user agent, user device, or user equipment (UE). A mobile device may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device having wireless connection capability, computing device, or other processing device connected to a wireless modem. Moreover, various embodiments are described herein in connection with a base station. A base station may be utilized for communicating with mobile device(s) and may also be referred to as an access point, Node B, or some other terminology.
Moreover, various aspects or features described herein may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques. The term “article of manufacture” as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer-readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips, etc.), optical disks (e.g., compact disk (CD), digital versatile disk (DVD), etc.), smart cards, and flash memory devices (e.g., EPROM, card, stick, key drive, etc.). Additionally, various storage media described herein can represent one or more devices and/or other machine-readable media for storing information. The term “machine-readable medium” can include, without being limited to, wireless channels and various other media capable of storing, containing, and/or carrying instruction(s) and/or data.
Referring now to
Base stations 102 may each communicate with one or more mobile devices 104. Base stations 102 may transmit information to mobile devices 104 over a forward link (downlink) and receive information from mobile devices 104 over a reverse link (uplink). Further, system 100 may be a time division duplex (TDD) system; thus, the forward link and the reverse link may utilize a common frequency band. In the TDD system, the downlink and uplink transmission signals alternately share the common frequency band, with guard time intervals being added in-between. A downlink transmission unit represents a time interval in which the downlink signal is sent, and an uplink transmission unit represents a time interval in which the uplink signal is sent. Moreover, system 100 may be synchronized when employing TDD such that base stations 102 receive uplink transmission units (UL TU) from mobile devices 104 during a first set of times and mobile devices 104 receive downlink transmission units (DL TU) from base stations 102 during a second set of times. According to an example, mobile devices 104 may transmit on the uplink to base stations 102 (e.g., transmit uplink transmission units), followed by a gap in time (e.g., guard time interval), and then base stations 102 may transmit on the downlink to mobile devices 104 (e.g., transmit downlink transmission units), followed by another gap in time (e.g., guard time interval), and so forth.
In accordance with an example, a downlink (or uplink) transmission unit includes any number of non-strip OFDM symbols. Further, a downlink transmission unit may include one or multiple strip OFDM symbols. Non-strip OFDM symbols are commonly utilized to transmit data and controls signals (e.g., via traffic channel(s) and/or control channel(s)). Additionally, strip OFDM symbols may be employed to transmit control signals (e.g., broadcast control signals, Beacon signals, . . . ). A tone hopping scheme may be used in connection with the non-strip OFDM symbols to average inter-cell interference and enable frequency diversity. Further, the same tone hopping scheme may not be utilized in connection with the strip OFDM symbols. Tone hopping may or may not be utilized in the strip OFDM symbols. Moreover, operation of coding and modulation in the strip OFDM symbols may be independent of that in the non-strip OFDM symbols.
Different types of transmission units are used in system 100. A first type of transmission unit includes only non-strip OFDM symbols. A second type of transmission unit is constructed by adding strip OFDM symbols to the first type. According to an example, the second type of transmission unit can have the same number of non-strip OFDM symbols as the first type of transmission unit and the tone hopping scheme used in the non-strip symbols of the first and the second type transmission units can be the same.
In a TDD system (e.g., system 100) with synchronized cells, a strip channel of one cell (e.g., associated with one of the base stations 102) may interfere with a strip channel of a disparate cell (e.g., associated with a differing one of the base stations 102), which may not be desired from an interference averaging perspective. Such interference may be mitigated by base stations 102 selectively positioning the strip OFDM symbols within downlink transmission units transferred to mobile devices 104. Further, the position of the strip OFDM symbol may vary from one cell to another (e.g., at least in a local area). For example, the position may be determined as a function of a physical layer identifier corresponding to each cell (e.g., cell identifier), which may be assigned locally unique when system 100 is deployed. Pursuant to another example, in a given cell, the position of the strip OFDM symbol within a downlink transmission unit may vary over time.
Strip OFDM symbols may be utilized to transfer Beacon signals from base stations 102 to mobile devices 104. However, each strip OFDM symbol need not carry a Beacon signal; rather, a subset of strip OFDM symbols may include Beacon signals (e.g., one out of every 8 strip OFDM symbols may carry Beacon signals, . . . ). Pursuant to an example, time position associated with Beacon signal transmission when a cell is in downlink mode may vary from one cell to another (e.g., at least in a local area). According to a further illustration, the spectrum may be divided into a plurality of frequency subbands and the Beacon signal may be transmitted sequentially in any one of the subbands. Thus, the combination of the time position and subband position may mitigate collisions of Beacon signals from neighboring cells. Moreover, for example, the time position and/or subband position may be determined as a function of a characteristic of a cell (e.g., physical layer identifier of a cell, cell identifier, . . . ); for instance, the physical layer identifier may be assigned locally unique to a cell when the network is deployed. Further, based upon the time location of strip OFDM symbols and/or Beacon signals within downlink transmission units, mobile devices 104 may determine the identity of base stations 102 that transmitted each of the downlink transmission units.
By utilizing differing time positions and/or subband positions for Beacon signal transfer in downlink transmission units, Beacon signal alignment from disparate cells may be mitigated. In contrast, conventional techniques oftentimes enable simultaneous transmission of Beacon signals from disparate cells in TDD systems. Thus, Beacon signals from different cells may commonly interfere with each other, thereby increasing difficulty associated with discerning Beacon signals from the different cells. For example, a relatively weak Beacon signal from a first cell may be difficult to utilize when a comparatively strong Beacon signal from a second cell is concurrently obtained at mobile device 104. However, the relatively weak Beacon signal (e.g., discerned by mitigating Beacon signal alignment) may be employed to enable robust handoffs, since detection of the presence of a cell may be effectuated through the relatively weak Beacon signal.
Now turning to
Downlink transmission unit generator 206 may create distinct types of downlink transmission units. For example, downlink transmission unit generator 206 may yield a first type of downlink transmission unit (e.g., type 0 downlink transmission unit) that includes only non-strip OFDM symbols. Pursuant to an illustration, downlink transmission unit generator 206 may include N non-strip OFDM symbols in type 0 downlink transmission units, where N may be any integer. Further to this illustration, N may be 31; however, the claimed subject matter is not so limited. Additionally, downlink transmission unit generator 206 may create a second type of downlink transmission unit (e.g., type 1 downlink transmission unit) that includes non-strip OFDM symbols and one or more strip OFDM symbols. Type 1 downlink transmission units generated by downlink transmission unit generator 206 may include N non-strip OFDM symbols, where N may be any integer (e.g., N may be 31, . . . ), and M strip OFDM symbols, where M may be any integer (e.g., M may be 1, . . . ). Pursuant to an example, the number of non-strip OFDM symbols in the type 0 and type 1 transmission units can be the same. Moreover, the tone hopping scheme used in the non-strip OFDM symbols of the type 0 and type 1 transmission units can be the same. The tone hopping scheme can be symbol-by-symbol hopping in which the physical tone(s) of a logical channel hop every OFDM symbol, or block-based hopping in which the physical tone(s) of a logical channel hop every a few OFDM symbols, or mixed symbol-by-symbol and blocked based hopping.
Downlink transmission unit generator 206 may further include a strip symbol inserter 208 that selectively positions strip OFDM symbol(s) within downlink transmission units (e.g., type 1 downlink transmission units) yielded by downlink transmission unit generator 206. For example, strip symbol inserter 208 may arrange the strip OFDM symbol at a fixed position (e.g., at the beginning of the transmission unit) and allow the non-strip OFDM symbols to fill the remaining positions. Strip symbol inserter 208 may selectively incorporate the strip OFDM symbols into the downlink transmission unit at varying positions as a function of cell identity (e.g., employing a physical layer identifier corresponding to a cell). By employing strip symbol inserter 208, alignment of strip OFDM symbols between disparate cells may be mitigated—thus, resultant interference associated with strip OFDM symbols from differing cells being transmitted at a common time may be reduced. Further, strip symbol inserter 208 may space the strip OFDM symbols as a function of expected drift.
According to one or more aspects, a strip OFDM symbol may comprise, for example, 113 tones, 56 of which may be utilized to transmit data, training information, etc., and have a non-zero energy associated with them. Further, the remaining tones are non-zero energy tones, known as null tones, that do not carry any signal transmission energy. However, the claimed subject matter is not so limited to the foregoing description of strip OFDM symbols.
Further, downlink transmission unit generator 206 may include a beacon inserter 210. Beacon inserter 210 may selectively incorporate Beacon signals at varying locations in downlink transmission units as a function of characteristics of cells (e.g., cell identifiers), expected drift, and so forth. Further, beacon inserter 210 may interject the Beacon signal to mitigate alignment with Beacon signal(s) included in downlink transmission units associated with differing cells. By way of illustration, beacon inserter 210 may enable including Beacon signals in a subset of the strip OFDM symbols selectively positioned by strip symbol inserter 208; for example, out of a set of F strip OFDM symbols, G of the strip OFDM symbols may carry Beacon signals, where F and G may be any integers. According to another example, beacon inserter 210 may determine subband positions to be employed in connection with each of the Beacon signals in the downlink transmission units.
Pursuant to an example, a strip OFDM symbol may be utilized to carry a Beacon signal, where a majority of transmission power is concentrated upon 1 tone; for instance, the per-tone transmission power of the Beacon signal may be much higher (e.g., 10, db, 15 db, 20 db, x db, . . . ) than an average per-tone transmission power associated with other OFDM symbols. Due to the higher transmission power, Beacon signals may be received by remotely located mobile devices (e.g., mobile device 204) and may be utilized for system acquisition and handoff. For example, mobile devices (e.g., mobile device 204) can utilize the Beacon signal to identify the cell and measure the channel gain from the cell. However, since Beacon signals tend to be peaky, difficulty is encountered when differentiating between Beacon signals from disparate base stations obtained at substantially similar times; thus, beacon inserter 210 may enable selectively spacing Beacon signals to mitigate Beacon signal overlap from different cells.
Mobile device 204 may further include a cell identity evaluator 212 that may analyze received downlink transmission units (e.g., type 1 downlink transmission units) to determine an identity of a transmitting cell (e.g., associated with base station 202). For example, Beacon signals may be provided in a subset of the strip OFDM symbols (e.g., every eighth strip OFDM symbol) by employing beacon inserter 210, and from the time location of the Beacon signal the identity of the cell may be determined by cell identity evaluator 212. It is contemplated that a minimum of one Beacon signal may be used by cell identity evaluator 212 to obtain the identity of a cell; however, more than one Beacon signal may be employed for such evaluation.
Further, each cell may include one or more sectors. According to an illustration, the time location of the strip OFDM symbol and/or the Beacon carried by the strip OFDM symbol may be a function of the cell identifier; thus, different sectors of the same cell may utilize the same time location within the downlink transmission units. However, the disparate sectors may employ a different time location based upon a sector identifier, which is different for a different sector.
Beacon inserter 210 may selectively incorporate Beacon signals at respective time positions and/or subband positions. For example, a combination of the time position and subband position utilized to transmit a Beacon signal as set forth by beacon inserter 210 may be fixed (e.g., constant over time), and may correspond to a particular cell. Further to this example, system synchronization (e.g., timing and frequency) information may be uniquely derived from the time and frequency location of the Beacon signal (e.g., by employing cell identity evaluator 212). For instance, after mobile device 204 detects the Beacon signal, it can derive a physical layer identifier of a cell based upon the determined time position of the Beacon signal within the downlink transmission interval. Further, cell identity evaluator 212 may determine when the downlink transmission interval starts and ends, which may enhance synchronization.
With reference to
Turning to
The following provides an example for operating in the first mode 402 to yield the type 0 transmission units. In particular, a data and control information bit can be coded and modulated by a coder and modulator 406 to yield a codeword. The codeword can thereafter be tone hopped by a tone hopper 408. Further, an OFDM symbol generator 410 can output the non-strip symbols that form the type 0 transmission unit.
By way of further illustration, type 1 transmission units can be generated while operating in the second mode 404. Accordingly, a data and control information bit can be coded and modulated by the coder and modulator 406. The codeword outputted by the coder and modulator 406 can be tone hopped by the tone hopper 408. Thereafter, the OFDM symbol generator 410 can yield the non-strip symbols. Moreover, a broadcast control information bit can be coded and modulated by the coder and modulator 406 to yield a corresponding codeword. This codeword can further be inputted to an OFDM symbol generator 412 that can yield strip symbols. The non-strip symbols and the strip symbols can be provided to a strip symbol inserter 208 (e.g., strip symbol inserter 208 of
With reference to
Turning to
Now turning to
According to an example, the channel structure of the remaining non-strip OFDM symbols of the type 1 DL TU can be the same as that of the type 0 DL TU. In particular, the tone hopping scheme can be the same. The coding and modulation scheme can also be the same. The strip OFDM symbol is generated from a codeword using a different coding/modulation scheme and separately from the generation of the non-strip OFDM symbols. In another example, to preserve block hopping as described in connection with the type 0 DL TU (e.g., type 0 DL TU 600 of
With reference to
According to an example, propagation differences may cause a mobile device to receive symbols of downlink transmission units transferred simultaneously from differing base stations at slightly disparate times, which yields drift. For instance, propagation differences may be a function of cell size, distance from each base station to the mobile device, and the like. Accordingly, a symbol transferred from a first cell during a first synchronized time may interfere with a symbol transmitted from a second cell during a second synchronized time. Further, the separation between strip OFDM symbols of differing cells may be based upon the expected drift; thus, if the drift is half a symbol, then a separation of one symbol may be employed, while if the drift is one symbol, then a separation of two symbols may be utilized, for example.
Referring to
With reference to
At 904, the downlink transmission unit may be transmitted. For example, the downlink transmission unit may be sent over a downlink during allocated time(s) within a superslot. Further, uplink transmission unit(s) and downlink transmission unit(s) lacking a strip OFDM symbol (e.g., that include 31 non-strip OFDM symbols) may be transmitted during disparate times within the superslot.
Now turning to
Turning to
Referring now to
According to an example, a wireless terminal may receive a downlink signal (e.g., downlink transmission unit). The Beacon signal may be decoded to recover a cell ID, sector ID, etc., from which the wireless terminal determinations the position of the Beacon signal in the downlink signal. Accordingly, a framing structure of the downlink signal of the intended base station associated with the downlink signal may be recognized. For instance, a starting point of DL TUs, scheduling for different types of DL TUs, etc. may be determined as a function of the framing structure. The wireless terminal may store the framing structure in memory and use it to retrieve other control/data information from the downlink signal. The wireless terminal may further determine the framing structure of the uplink signal, and transmit a signal (e.g., an access signal) according to the uplink framing structure.
It will be appreciated that, in accordance with one or more aspects described herein, inferences can be made regarding generating downlink transmission units and/or identifying sources of received downlink transmission units. As used herein, the term to “infer” or “inference” refers generally to the process of reasoning about or inferring states of the system, environment, and/or user from a set of observations as captured via events and/or data. Inference can be employed to identify a specific context or action, or can generate a probability distribution over states, for example. The inference can be probabilistic—that is, the computation of a probability distribution over states of interest based on a consideration of data and events. Inference can also refer to techniques employed for composing higher-level events from a set of events and/or data. Such inference results in the construction of new events or actions from a set of observed events and/or stored event data, whether or not the events are correlated in close temporal proximity, and whether the events and data come from one or several event and data sources.
According to an example, one or more methods presented above can include making inferences pertaining to electing a location to insert strip OFDM symbols and/or Beacon signals within downlink transmission units. In accordance with another example, an inference may be made related to identifying an expected drift, which may be utilized in connection with selectively position strip OFDM symbols and/or Beacon signals in downlink transmission units. By way of further illustration, an inference may be made related to determining an identity of a cell that generated and/or transmitted a received downlink transmission unit. It will be appreciated that the foregoing examples are illustrative in nature and are not intended to limit the number of inferences that can be made or the manner in which such inferences are made in conjunction with the various embodiments and/or methods described herein.
Sector boundary regions provide potential for signal interference between signals transmitted by base stations in neighboring sectors. Line 1316 represents a sector boundary region between sector I 1310 and sector II 1312; line 1318 represents a sector boundary region between sector II 1312 and sector III 1314; line 1320 represents a sector boundary region between sector III 1314 and sector I 1310. Similarly, cell M 1304 includes a first sector, sector I 1322, a second sector, sector II 1324, and a third sector, sector III 1326. Line 1328 represents a sector boundary region between sector I 1322 and sector II 1324; line 1330 represents a sector boundary region between sector II 1324 and sector III 1326; line 1332 represents a boundary region between sector III 1326 and sector 11322. Cell I 1302 includes a base station (BS), base station I 1306, and a plurality of end nodes (ENs) (e.g., mobile devices) in each sector 1310, 1312, 1314. Sector I 1310 includes EN(1) 1336 and EN(X) 1338 coupled to BS 1306 via wireless links 1340, 1342, respectively; sector II 1312 includes EN(1′) 1344 and EN(X′) 1346 coupled to BS 1306 via wireless links 1348, 1350, respectively; sector III 1314 includes EN(1″) 1352 and EN(X″) 1354 coupled to BS 1306 via wireless links 1356, 1358, respectively. Similarly, cell M 1304 includes base station M 1308, and a plurality of end nodes (ENs) in each sector 1322, 1324, 1326. Sector I 1322 includes EN(1) 1336′ and EN(X) 1338′ coupled to BS M 1308 via wireless links 1340′, 1342′, respectively; sector II 1324 includes EN(1′) 1344′ and EN(X′) 1346′ coupled to BS M 1308 via wireless links 1348′, 1350′, respectively; sector 31326 includes EN(1″) 1352′ and EN(X″) 1354′ coupled to BS 1308 via wireless links 1356′, 1358′, respectively.
System 1300 also includes a network node 1360 which is coupled to BS I 1306 and BS M 1308 via network links 1362, 1364, respectively. Network node 1360 is also coupled to other network nodes, e.g., other base stations, AAA server nodes, intermediate nodes, routers, etc. and the Internet via network link 1366. Network links 1362, 1364, 1366 may be, e.g., fiber optic cables. Each end node, e.g., EN(1) 1336 may be a wireless terminal including a transmitter as well as a receiver. The wireless terminals, e.g., EN(1) 1336 may move through system 1300 and may communicate via wireless links with the base station in the cell in which the EN is currently located. The wireless terminals, (WTs), e.g., EN(1) 1336, may communicate with peer nodes, e.g., other WTs in system 1300 or outside system 1300 via a base station, e.g., BS 1306, and/or network node 1360. WTs, e.g., EN(1) 1336 may be mobile communications devices such as cell phones, personal data assistants with wireless modems, etc. Respective base stations perform tone subset allocation using a different method for the strip-symbol periods, from the method employed for allocating tones and determining tone hopping in the rest symbol periods, e.g., non strip-symbol periods. The wireless terminals use the tone subset allocation method along with information received from the base station, e.g., base station slope ID, sector ID information, to determine tones that they can employ to receive data and information at specific strip-symbol periods. The tone subset allocation sequence is constructed, in accordance with various aspects to spread inter-sector and inter-cell interference across respective tones.
Sectorized antenna 1403 coupled to receiver 1402 is used for receiving data and other signals, e.g., channel reports, from wireless terminals transmissions from each sector within the base station's cell. Sectorized antenna 1405 coupled to transmitter 1404 is used for transmitting data and other signals, e.g., control signals, pilot signal, beacon signals, etc. to wireless terminals 1500 (see
Data/information 1420 includes data 1436, tone subset allocation sequence information 1438 including downlink strip-symbol time information 1440 and downlink tone information 1442, and wireless terminal (WT) data/info 1444 including a plurality of sets of WT information: WT 1 info 1446 and WT N info 1460. Each set of WT info, e.g., WT 1 info 1446 includes data 1448, terminal ID 1450, sector ID 1452, uplink channel information 1454, downlink channel information 1456, and mode information 1458.
Routines 1418 include communications routines 1422 and base station control routines 1424. Base station control routines 1424 includes a scheduler routine 1426 and signaling routines 1428 including an encoding/modulation routine 1430, a tone hopping routine 1432, and a Beacon signal insertion routine 1434. Scheduler routine 1426 controls determining a type of downlink transmission unit to transmit (e.g., type 0, type 1, . . . ) and/or whether to include a Beacon signal in a particular type 1 downlink transmission unit.
Data 1436 includes data to be transmitted that will be sent to encoder 1414 of transmitter 1404 for encoding prior to transmission to WTs, and received data from WTs that has been processed through decoder 1412 of receiver 1402 following reception. Downlink strip-symbol time information 1440 includes the frame synchronization structure information, such as the superslot, beaconslot, and ultraslot structure information and information specifying whether a given symbol period is a strip-symbol period, and if so, the index of the strip-symbol period and whether the strip-symbol is a resetting point to truncate the tone subset allocation sequence used by the base station. Downlink tone information 1442 includes information including a carrier frequency assigned to the base station 1400, the number and frequency of tones, and the set of tone subsets to be allocated to the strip-symbol periods, and other cell and sector specific values such as slope, slope index and sector type.
Data 1448 may include data that WT11500 has received from a peer node, data that WT11500 desires to be transmitted to a peer node, and downlink channel quality report feedback information. Terminal ID 1450 is a base station 1400 assigned ID that identifies WT11500. Sector ID 1452 includes information identifying the sector in which WT11500 is operating. Sector ID 1452 can be used, for example, to determine the sector type. Uplink channel information 1454 includes information identifying channel segments that have been allocated by scheduler 1426 for WT11500 to use, e.g., uplink traffic channel segments for data, dedicated uplink control channels for requests, power control, timing control, etc. Each uplink channel assigned to WT11500 includes one or more logical tones, each logical tone following an uplink hopping sequence. Downlink channel information 1456 includes information identifying channel segments that have been allocated by scheduler 1426 to carry data and/or information to WT11500, e.g., downlink traffic channel segments for user data. Each downlink channel assigned to WT11500 includes one or more logical tones, each following a downlink hopping sequence. Mode information 1458 includes information identifying the state of operation of WT11500, e.g. sleep, hold, on.
Communications routines 1422 control the base station 1400 to perform various communications operations and implement various communications protocols. Base station control routines 1424 are used to control the base station 1400 to perform basic base station functional tasks, e.g., signal generation and reception, scheduling, and to implement the steps of the method of some aspects including transmitting signals to wireless terminals using the tone subset allocation sequences during the strip-symbol periods.
Signaling routine 1428 controls the operation of receiver 1402 with its decoder 1412 and transmitter 1404 with its encoder 1414. The signaling routine 1428 is responsible for controlling the generation of transmitted data 1436 and control information. Encoding/modulation routine 1430 controls coding and modulation for non-strip symbols and strip symbols. Further, tone hopping routine 1432 controls tone hopping in connection with non-strip symbols. Moreover, Beacon signal insertion routine 1434 controls selectively positioning a Beacon signal within a type 1 downlink transmission unit.
The processor 1506, e.g., a CPU controls the operation of the wireless terminal 1500 and implements methods by executing routines 1520 and using data/information 1522 in memory 1508.
Data/information 1522 includes user data 1534, user information 1536, and tone subset allocation sequence information 1550. User data 1534 may include data, intended for a peer node, which will be routed to encoder 1514 for encoding prior to transmission by transmitter 1504 to base station 1400, and data received from the base station 1400 which has been processed by the decoder 1512 in receiver 1502. User information 1536 includes uplink channel information 1538, downlink channel information 1540, terminal ID information 1542, base station ID information 1544, sector ID information 1546, and mode information 1548. Uplink channel information 1538 includes information identifying uplink channels segments that have been assigned by base station 1400 for wireless terminal 1500 to use when transmitting to the base station 1400. Uplink channels may include uplink traffic channels, dedicated uplink control channels, e.g., request channels, power control channels and timing control channels. Each uplink channel includes one or more logic tones, each logical tone following an uplink tone hopping sequence. The uplink hopping sequences are different between each sector type of a cell and between adjacent cells. Downlink channel information 1540 includes information identifying downlink channel segments that have been assigned by base station 1400 to WT 1500 for use when BS 1400 is transmitting data/information to WT 1500. Downlink channels may include downlink traffic channels and assignment channels, each downlink channel including one or more logical tone, each logical tone following a downlink hopping sequence, which is synchronized between each sector of the cell.
User info 1536 also includes terminal ID information 1542, which is a base station 1400 assigned identification, base station ID information 1544 which identifies the specific base station 1400 that WT has established communications with, and sector ID info 1546 which identifies the specific sector of the cell where WT 1500 is presently located. Base station ID 1544 provides a cell slope value and sector ID info 1546 provides a sector index type; the cell slope value and sector index type may be used to derive tone hopping sequences. Mode information 1548 also included in user info 1536 identifies whether the WT 1500 is in sleep mode, hold mode, or on mode.
Tone subset allocation sequence information 1550 includes downlink strip-symbol time information 1552 and downlink tone information 1554. Downlink strip-symbol time information 1552 include the frame synchronization structure information, such as the superslot, beaconslot, and ultraslot structure information and information specifying whether a given symbol period is a strip-symbol period, and if so, the index of the strip-symbol period and whether the strip-symbol is a resetting point to truncate the tone subset allocation sequence used by the base station. Downlink tone info 1554 includes information including a carrier frequency assigned to the base station 1400, the number and frequency of tones, and the set of tone subsets to be allocated to the strip-symbol periods, and other cell and sector specific values such as slope, slope index and sector type.
Routines 1520 include communications routines 1524 and wireless terminal control routines 1526. Communications routines 1524 control the various communications protocols used by WT 1500. Wireless terminal control routines 1526 control basic wireless terminal 1500 functionality including the control of the receiver 1502 and transmitter 1504. Wireless terminal control routines 1526 include the signaling routine 1528. The signaling routine 1528 includes a cell deriving routine 1530 and a Beacon signal locating routine 1532. Cell ID deriving routine 1530 can determine an identifier of a cell. Further, Beacon signal locating routine 1532 can identify a position of a Beacon signal within a type 1 downlink transmission unit as described herein.
With reference to
Turning to
It is to be understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof. For a hardware implementation, the processing units may be implemented within one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, other electronic units designed to perform the functions described herein, or a combination thereof.
When the embodiments are implemented in software, firmware, middleware or microcode, program code or code segments, they may be stored in a machine-readable medium, such as a storage component. A code segment may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted using any suitable means including memory sharing, message passing, token passing, network transmission, etc.
For a software implementation, the techniques described herein may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The software codes may be stored in memory units and executed by processors. The memory unit may be implemented within the processor or external to the processor, in which case it can be communicatively coupled to the processor via various means as is known in the art.
What has been described above includes examples of one or more embodiments. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the aforementioned embodiments, but one of ordinary skill in the art may recognize that many further combinations and permutations of various embodiments are possible. Accordingly, the described embodiments are intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. Furthermore, to the extent that the term “includes” is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim.
This application claims the benefit of U.S. Provisional Patent application Ser. No. 60/845,939 entitled “OFFSETTING BEACON POSITION IN A TIME DIVISION DUPLEX COMMUNICATIONS” which was filed Sep. 19, 2006. The entirety of the aforementioned application is herein incorporated by reference.
| Number | Date | Country | |
|---|---|---|---|
| 20080130480 A1 | Jun 2008 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60845939 | Sep 2006 | US | |
| 60511964 | Oct 2003 | US | |
| 60406076 | Aug 2002 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 10964908 | Oct 2004 | US |
| Child | 11266643 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11266643 | Nov 2005 | US |
| Child | 11857761 | US | |
| Parent | 10642096 | Aug 2003 | US |
| Child | 10964908 | US | |
| Parent | 10641399 | Aug 2003 | US |
| Child | 10642096 | US |
