Interface management in wireless communication system using hybrid time reuse
Claim Score by NHIP
Abstract
Interference that occurs during wireless communication may be managed by hybrid time reuse. A method, apparatus amend medium of communication determines one or more time reuse patterns of respective one or more unplanned access points. A second time reuse pattern that is less interfering with the one or more time reuse patterns is selected. Signals are transmitted according to the second time reuse pattern from a second unplanned access point to an associated access terminal.

Term
4.1 yearsto projected expiry
Projected expiry 10 November 2030, counted from filing; an application has no term until it is granted.
- Priority
- Filed
- Published
- Today
- Projected expiry
32 claims: 4 independent, 28 dependent
- 1Broadest claimClaim Score 73, broad(NHIP)A method of communication, comprising:determining one or more time reuse patterns of respective one or more unplanned access points;selecting a second time reuse pattern that is less interfering with the one or more time reuse patterns;and transmitting signals according to the second time reuse pattern from a second unplanned access point to an associated access terminal.
- 9An apparatus for communication, comprising:an interference controller configured to determine one or more time reuse patterns of respective one or more unplanned access points and to select a second time reuse pattern that is less interfering with the one or more time reuse patterns;and a communication controller configured to transmit signals according to the second time reuse pattern from a second unplanned access point to an associated access terminal.
- 17An apparatus for communication, comprising:means for determining one or more time reuse patterns of respective one or more unplanned access points;means for selecting a second time reuse pattern that is less interfering with the one or more time reuse patterns;and means for transmitting signals according to the second time reuse pattern from a second unplanned access point to an associated access terminal.
- 25A computer-program product, comprising:computer-readable medium comprising codes for causing a computer to: determine one or more time reuse patterns of respective one or more unplanned access points;select a second time reuse pattern that is less interfering with the one or more time reuse patterns;and transmit signals according to the second time reuse pattern from a second unplanned access point to an associated access terminal.
Independent claims4
254 paragraphs in 5 sections, as filed
CLAIM OF PRIORITY UNDER 35 U.S.C. §119
p-0002This application claims the benefit of and priority to commonly owned U.S. Provisional Patent Application No. 60/990,541, filed Nov. 27, 2007, and assigned Attorney Docket No. 080324P1; U.S. Provisional Patent Application No. 60/990,547, filed Nov. 27, 2007, and assigned Attorney Docket No. 080325P1; U.S. Provisional Patent Application No. 60/990,459, filed Nov. 27, 2007, and assigned Attorney Docket No. 080301P1; U.S. Provisional Patent Application No. 60/990,513, filed Nov. 27, 2007, and assigned Attorney Docket No. 080330P1; U.S. Provisional Patent Application No. 60/990,564, filed Nov. 27, 2007, and assigned Attorney Docket No. 080323P1; and U.S. Provisional Patent Application No. 60/990,570, filed Nov. 27, 2007, and assigned Attorney Docket No. 080331P1, the disclosure of each of which is hereby incorporated by reference herein.
CROSS-REFERENCE TO RELATED APPLICATION
p-0003This application is related to concurrently filed and commonly owned: <ul><li id="ul0001-0001" num="0003">U.S. patent application Ser. No. ______, entitled “INTERFERENCE MANAGEMENT IN A WIRELESS COMMUNICATION SYSTEM USING BEAM AND NULL STEERING,” and assigned Attorney Docket No. 080324;</li><li id="ul0001-0002" num="0004">U.S. patent application Ser. No. ______, entitled “INTERFERENCE MANAGEMENT IN A WIRELESS COMMUNICATION SYSTEM USING OVERHEAD CHANNEL POWER CONTROL,” and assigned Attorney Docket No. 080325;</li><li id="ul0001-0003" num="0005">U.S. patent application Ser. No. ______, entitled “INTERFERENCE MANAGEMENT IN A WIRELESS COMMUNICATION SYSTEM USING FREQUENCY SELECTIVE TRANSMISSION,” and assigned Attorney Docket No. 080301;</li><li id="ul0001-0004" num="0006">U.S. patent application Ser. No. ______, entitled “INTERFERENCE MANAGEMENT IN A WIRELESS COMMUNICATION SYSTEM USING ADAPTIVE PATH LOSS ADJUSTMENT,” and assigned Attorney Docket No. 080330; and</li><li id="ul0001-0005" num="0007">U.S. patent application Ser. No. ______, entitled “INTERFACE MANAGEMENT IN A WIRELESS COMMUNICATION SYSTEM USING SUBFRAME TIME REUSE,” and assigned Attorney Docket No. 080323; the disclosure of each of which is hereby incorporated by reference herein.</li></ul>
BACKGROUND
p-00041. Field
p-0005This application relates generally to wireless communication and more specifically, but not exclusively, to improving communication performance.
p-00062. Introduction
p-0007Wireless communication systems are widely deployed to provide various types of communication (e.g., voice, data, multimedia services, etc.) to multiple users. As the demand for high-rate and multimedia data services rapidly grows, there lies a challenge to implement efficient and robust communication systems with enhanced performance.
p-0008To supplement conventional mobile phone network base stations, small-coverage base stations may be deployed (e.g., installed in a user's home) to provide more robust indoor wireless coverage to mobile units. Such small-coverage base stations are generally known as access points, base stations, Home NodeBs, or femto cells. Typically, such small-coverage base stations are connected to the Internet and the mobile operator's network via a DSL router or a cable modem.
p-0009Since radio frequency (“RF”) coverage of small-coverage base stations may not be optimized by the mobile operator and deployment of such base stations may be ad-hoc, RF interference issues may arise. Moreover, soft handover may not be supported for small-coverage base stations. Lastly a mobile station may not be allowed to communicate with the access point which has the best RF signal due to restricted association (i.e., closed subscriber group) requirement. Thus, there is a need for improved interference management for wireless networks.
SUMMARY
p-0010The disclosure relates to managing interference through hybrid time reuse. By determining interfering time reuse patterns, the transmission of optimal time reuse pattern of the access point may be adjusted. In one exemplary embodiment, a method of communication includes determining time reuse patterns of neighboring unplanned access points and control channel offset of macro access point. Then optimal time reuse pattern is selected based wherein the signal to noise ratio of the associated access terminal is maximized.
p-0011In another exemplary embodiment, an apparatus for communication includes an interference controller configured to determine time reuse patterns of neighboring unplanned access points and wherein the signal to noise ratio of the access terminals are maximized. The apparatus further includes a communication controller configured to transmit signals according to the optimal time reuse patterns of unplanned access points.
BRIEF DESCRIPTION OF THE DRAWINGS
p-0012These and other sample aspects of the disclosure will be described in the detailed description and the appended claims that follow, and in the accompanying drawings, wherein:
p-0013<figref idrefs="DRAWINGS">FIG. 1</figref> is a simplified block diagram of several sample aspects of a communication system;
p-0014<figref idrefs="DRAWINGS">FIG. 2</figref> is a simplified block diagram illustrating several sample aspects of components in a sample communication system;
p-0015<figref idrefs="DRAWINGS">FIG. 3</figref> is a flowchart of several sample aspects of operations that may be performed to manage interference;
p-0016<figref idrefs="DRAWINGS">FIG. 4</figref> is a simplified diagram of a wireless communication system;
p-0017<figref idrefs="DRAWINGS">FIG. 5A</figref> is a simplified diagram of a wireless communication system including femto nodes;
p-0018<figref idrefs="DRAWINGS">FIG. 5B</figref> is a simplified diagram of a specific arrangement of femto nodes and access terminals illustrating negative geometries;
p-0019<figref idrefs="DRAWINGS">FIG. 6</figref> is a simplified diagram illustrating coverage areas for wireless communication;
p-0020<figref idrefs="DRAWINGS">FIG. 7</figref> is a flowchart of several sample aspects of operations that may be performed to manage interference through the use of beam and null steering;
p-0021<figref idrefs="DRAWINGS">FIG. 8</figref> is a flowchart of several sample aspects of operations that may be performed to manage interference through the use of optimized reduced power levels for an overhead channel;
p-0022<figref idrefs="DRAWINGS">FIG. 9</figref> is a flowchart of several sample aspects of operations that may be performed to manage interference through the use of optimized reduced power levels for an overhead channel;
p-0023<figref idrefs="DRAWINGS">FIG. 10</figref> is a flowchart of several aspects of operations that may be performed to manage interference through the use of frequency selective transmission to address jamming and negative geometries;
p-0024<figref idrefs="DRAWINGS">FIGS. 11A-11B</figref> are flowcharts of several aspects of operations that may be performed to manage interference through the use of adaptive noise figure and path loss adjustment;
p-0025<figref idrefs="DRAWINGS">FIG. 12</figref> is a flowchart of several aspects of operations that may be performed to manage interference through the use of subframe time reuse techniques;
p-0026<figref idrefs="DRAWINGS">FIG. 13</figref> is a slot diagram illustrating time sharing among femto nodes that may be performed to manage interference through the use of hybrid time reuse techniques;
p-0027<figref idrefs="DRAWINGS">FIG. 14</figref> is a flowchart of several aspects of operations that may be performed to manage interference through the use of hybrid time reuse;
p-0028<figref idrefs="DRAWINGS">FIG. 15</figref> is a simplified block diagram of several sample aspects of communication components; and
p-0029<figref idrefs="DRAWINGS">FIGS. 16-21</figref> are simplified block diagrams of several sample aspects of apparatuses configured to manage interference as taught herein.
p-0030In accordance with common practice the various features illustrated in the drawings may not be drawn to scale. Accordingly, the dimensions of the various features may be arbitrarily expanded or reduced for clarity. In addition, some of the drawings may be simplified for clarity. Thus, the drawings may not depict all of the components of a given apparatus (e.g., device) or method. Finally, like reference numerals may be used to denote like features throughout the specification and figures.
DETAILED DESCRIPTION
p-0031Various aspects of the disclosure are described below. It should be apparent that the teachings herein may be embodied in a wide variety of forms and that any specific structure, function, or both being disclosed herein is merely representative. Based on the teachings herein one skilled in the art should appreciate that an aspect disclosed herein may be implemented independently of any other aspects and that two or more of these aspects may be combined in various ways. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, such an apparatus may be implemented or such a method may be practiced using other structure, functionality, or structure and functionality in addition to or other than one or more of the aspects set forth herein. Furthermore, an aspect may comprise at least one element of a claim.
p-0032In some aspects the teachings herein may be employed in a network that includes macro scale coverage (e.g., a large area cellular network such as a 3G networks, typically referred to as a macro cell network) and smaller scale coverage (e.g., a residence-based or building-based network environment). As an access terminal (“AT”) moves through such a network, the access terminal may be served in certain locations by access nodes (“ANs”) that provide macro coverage while the access terminal may be served at other locations by access nodes that provide smaller scale coverage. In some aspects, the smaller coverage nodes may be used to provide incremental capacity growth, in-building coverage, and different services (e.g., for a more robust user experience). In the discussion herein, a node that provides coverage over a relatively large area may be referred to as a macro node. A node that provides coverage over a relatively small area (e.g., a residence) may be referred to as a femto node. A node that provides coverage over an area that is smaller than a macro area and larger than a femto area may be referred to as a pico node (e.g., providing coverage within a commercial building).
p-0033A cell associated with a macro node, a femto node, or a pico node may be referred to as a macro cell, a femto cell, or a pico cell, respectively. In some implementations, each cell may be further associated with (e.g., divided into) one or more sectors.
p-0034In various applications, other terminology may be used to reference a macro node, a femto node, or a pico node. For example, a macro node may be configured or referred to as an access node, base station, access point, eNodeB, macro cell, and so on. Also, a femto node may be configured or referred to as a Home NodeB, Home eNodeB, access point, base station, femto cell, and so on.
p-0035<figref idrefs="DRAWINGS">FIG. 1</figref> illustrates sample aspects of a communication system <b>100</b> where distributed nodes (e.g., access points <b>102</b>, <b>104</b>, and <b>106</b>) provide wireless connectivity for other nodes (e.g., access terminals <b>108</b>, <b>110</b>, and <b>112</b>) that may be installed in or that may roam throughout an associated geographical area. In some aspects, the access points <b>102</b>, <b>104</b>, and <b>106</b> may communicate with one or more network nodes (e.g., a centralized network controller such as network node <b>114</b>) to facilitate wide area network connectivity.
p-0036An access point such as access point <b>104</b> may be restricted whereby only certain access terminals (e.g., access terminal <b>110</b>) are allowed to access the access point, or the access point may be restricted in some other manner. In such a case, a restricted access point and/or its associated access terminals (e.g., access terminal <b>110</b>) may interfere with other nodes in the system <b>100</b> such as, for example, an unrestricted access point (e.g., macro access point <b>102</b>), its associated access terminals (e.g., access terminal <b>108</b>), another restricted access point (e.g., access point <b>106</b>), or its associated access terminals (e.g., access terminal <b>112</b>). For example, the closest access point to given access terminal may not be the serving access points for that access terminal. Consequently, transmissions by that access terminal may interfere with reception at the access terminal. As discussed herein, frequency reuse, frequency selective transmission, interference cancellation and smart antenna (e.g., beamforming and null steering) and other techniques may be employed to mitigate interference.
p-0037Sample operations of a system such as the system <b>100</b> will be discussed in more detail in conjunction with the flowchart of <figref idrefs="DRAWINGS">FIG. 2</figref>. For convenience, the operations of <figref idrefs="DRAWINGS">FIG. 2</figref> (or any other operations discussed or taught herein) may be described as being performed by specific components (e.g., components of the system <b>100</b> and/or components of a system <b>300</b> as shown in <figref idrefs="DRAWINGS">FIG. 3</figref>). It should be appreciated, however, that these operations may be performed by other types of components and may be performed using a different number of components. It also should be appreciated that one or more of the operations described herein may not be employed in a given implementation.
p-0038For illustration purposes various aspects of the disclosure will be described in the context of a network node, an access point, and an access terminal that communicate with one another. It should be appreciated, however, that the teachings herein may be applicable to other types of apparatuses or apparatuses that are referred to using other terminology.
p-0039<figref idrefs="DRAWINGS">FIG. 3</figref> illustrates several sample components that may be incorporated into the network node <b>114</b> (e.g., a radio network controller), the access point <b>104</b>, and the access terminal <b>110</b> in accordance with the teachings herein. It should be appreciated that the components illustrated for a given one of these nodes also may be incorporated into other nodes in the system <b>100</b>.
p-0040The network node <b>114</b>, the access point <b>104</b>, and the access terminal <b>110</b> include transceivers <b>302</b>, <b>304</b>, and <b>306</b>, respectively, for communicating with each other and with other nodes. The transceiver <b>302</b> includes a transmitter <b>308</b> for sending signals and a receiver <b>310</b> for receiving signals. The transceiver <b>304</b> includes a transmitter <b>312</b> for transmitting signals and a receiver <b>314</b> for receiving signals. The transceiver <b>306</b> includes a transmitter <b>316</b> for transmitting signals and a receiver <b>318</b> for receiving signals.
p-0041In a typical implementation, the access point <b>104</b> communicates with the access terminal <b>110</b> via one or more wireless communication links and the access point <b>104</b> communicates with the network node <b>114</b> via a backhaul. It should be appreciated that wireless or non-wireless links may be employed between these nodes or other in various implementations. Hence, the transceivers <b>302</b>, <b>304</b>, and <b>306</b> may include wireless and/or non-wireless communication components.
p-0042The network node <b>114</b>, the access point <b>104</b>, and the access terminal <b>110</b> also include various other components that may be used in conjunction with interference management as taught herein. For example, the network node <b>114</b>, the access point <b>104</b>, and the access terminal <b>110</b> may include interference controllers <b>320</b>, <b>322</b>, and <b>324</b>, respectively, for mitigating interference and for providing other related functionality as taught herein. The interference controller <b>320</b>, <b>322</b>, and <b>324</b> may include one or more components for performing specific types of interference management. The network node <b>114</b>, the access point <b>104</b>, and the access terminal <b>110</b> may include communication controllers <b>326</b>, <b>328</b>, and <b>330</b>, respectively, for managing communications with other nodes and for providing other related functionality as taught herein. The network node <b>114</b>, the access point <b>104</b>, and the access terminal <b>110</b> may include timing controllers <b>332</b>, <b>334</b>, and <b>336</b>, respectively, for managing communications with other nodes and for providing other related functionality as taught herein. The other components illustrated in <figref idrefs="DRAWINGS">FIG. 3</figref> will be discussed in the disclosure that follows.
p-0043For illustrations purposes, the interference controller <b>320</b> and <b>322</b> are depicted as including several controller components. In practice, however, a given implementation may not employ all of these components. Here, a hybrid automatic repeat request (HARQ) controller component <b>338</b> or <b>340</b> may provide functionality relating to HARQ interlace operations as taught herein. A profile controller component <b>342</b> or <b>344</b> may provide functionality relating to transmit power profile or receive attenuation operations as taught herein. A timeslot controller component <b>346</b> or <b>348</b> may provide functionality relating to timeslot portion operations as taught herein. An antenna controller component <b>350</b> or <b>352</b> may provide functionality relating to smart antenna (e.g., beamforming and/or null steering) operations as taught herein. A receive noise controller component <b>354</b> or <b>356</b> may provide functionality relating to adaptive noise figure and path loss adjustment operations as taught herein. A transmit power controller component <b>358</b> or <b>360</b> may provide functionality relating to transmit power operations as taught herein. A time reuse controller component <b>362</b> or <b>364</b> may provide functionality relating to time reuse operations as taught herein.
p-0044<figref idrefs="DRAWINGS">FIG. 2</figref> illustrates how the network node <b>114</b>, the access point <b>104</b>, and the access terminal <b>110</b> may interact with one another to provide interference management (e.g., interference mitigation). In some aspects, these operations may be employed on an uplink and/or on a downlink to mitigate interference. In general, one or more the techniques described by <figref idrefs="DRAWINGS">FIG. 2</figref> may be employed in the more specific implementations that are described in conjunction with <figref idrefs="DRAWINGS">FIGS. 7-14</figref> below. Hence, for purposes of clarity, the descriptions of the more specific implementations may not describe these techniques again in detail.
p-0045As represented by block <b>202</b>, the network node <b>114</b> (e.g., the interference controller <b>320</b>) may optionally define one or more interference management parameters for the access point <b>104</b> and/or the access terminal <b>110</b>. Such parameters may take various forms. For example, in some implementations the network node <b>114</b> may define types of interference management information. Examples of such parameters will be described in more detail below in conjunction with <figref idrefs="DRAWINGS">FIGS. 7-14</figref>.
p-0046In some aspects, the definition of interference parameters may involve determining how to allocate one or more resources. For example, the operations of block <b>402</b> may involve defining how an allocated resource (e.g., a frequency spectrum, etc.) may be divided up for fractional reuse. In addition, the definition of fraction reuse parameters may involve determining how much of the allocated resource (e.g., how many HARQ interlaces, etc.) may be used by any one of a set of access points (e.g., restricted access points). The definition of fraction reuse parameters also may involve determining how much of the resource may be used by a set of access points (e.g., restricted access points).
p-0047In some aspects, the network node <b>114</b> may define a parameter based on received information that indicates whether there may be interference on an uplink or a downlink and, if so, the extent of such interference. Such information may be received from various nodes in the system (e.g., access points and/or access terminals) and in various ways (e.g., over a backhaul, over-the-air, and so on).
p-0048For example, in some cases one or more access points (e.g., the access point <b>104</b>) may monitor an uplink and/or a downlink and send an indication of interference detected on the uplink and/or downlink to the network node <b>114</b> (e.g., on a repeated basis or upon request). As an example of the former case, the access point <b>104</b> may calculate the signals strength of signals it receives from nearby access terminals that are not associated with (e.g., served by) the access point <b>104</b> (e.g., access terminals <b>108</b> and <b>112</b>) and report this to the network node <b>114</b>.
p-0049In some cases, each of the access points in the system may generate a load indication when they are experiencing relatively high loading. Such an indication may take the form of, for example, a busy bit in 1×EV-DO, a relative grant channel (“RGCH”) in 3GPP, or some other suitable form. In a conventional scenario, an access point may send this information to its associated access terminal via a downlink. However, such information also may be sent to the network node <b>114</b> (e.g., via the backhaul).
p-0050In some cases, one or more access terminals (e.g., the access terminal <b>110</b>) may monitor downlink signals and provide information based on this monitoring. The access terminal <b>110</b> may send such information to the access point <b>104</b> (e.g., which may forward the information to the network node <b>114</b>) or to the network node <b>114</b> (via the access point <b>104</b>). Other access terminals in the system may send information to the network node <b>114</b> in a similar manner.
p-0051In some cases, the access terminal <b>110</b> may generate measurement reports (e.g., on repeated basis). In some aspects, such a measurement report may indicate which access points the access terminal <b>110</b> is receiving signals from, a received signal strength indication associated with the signals from each access point (e.g., Ec/Io), the path loss to each of the access points, or some other suitable type of information. In some cases a measurement report may include information relating to any load indications the access terminal <b>110</b> received via a downlink.
p-0052The network node <b>114</b> may then use the information from one or more measurement reports to determine whether the access point <b>104</b> and/or the access terminal <b>110</b> are relatively close to another node (e.g., another access point or access terminal). In addition, the network node <b>114</b> may use this information to determine whether any of these nodes interfere with any other one of these nodes. For example, the network node <b>114</b> may determine received signal strength at a node based on the transmit power of a node that transmitted the signals and the path loss between these nodes.
p-0053In some cases, the access terminal <b>110</b> may generate information that is indicative of the signal to noise ratio (e.g., signal and interference to noise ratio, SINR) on a downlink. Such information may comprise, for example a channel quality indication (“CQI”), a data rate control (“DRC”) indication, or some other suitable information. In some cases, this information may be sent to the access point <b>104</b> and the access point <b>104</b> may forward this information to the network node <b>114</b> for use in interference management operations. In some aspects, the network node <b>114</b> may use such information to determine whether there is interference on a downlink or to determine whether interference in the downlink is increasing or decreasing.
p-0054As will be described in more detail below, in some cases the interference-related information may be used to determine how to mitigate interference. As one example, CQI or other suitable information may be received on a per-HARQ interlace basis whereby it may be determined which HARQ interlaces are associated with the lowest level of interference. A similar technique may be employed for other fractional reuse techniques.
p-0055It should be appreciated that the network node <b>114</b> may define parameters in various other ways. For example, in some cases the network node <b>114</b> may randomly select one or more parameters.
p-0056As represented by block <b>204</b>, the network node <b>114</b> (e.g., the communication controller <b>326</b>) sends the defined interference management parameters to the access point <b>104</b>. As will be discussed below, in some cases the access point <b>104</b> uses these parameters and in some cases the access point <b>104</b> forwards these parameters to the access terminal <b>110</b>.
p-0057In some cases, the network node <b>114</b> may manage interference in the system by defining the interference management parameters to be used by two or more nodes (e.g., access points and/or access terminals) in the system. For example, in the case of a fractional reuse scheme, the network node <b>114</b> may send different (e.g., mutually exclusive) interference management parameters to neighboring access points (e.g., access points that are close enough to potentially interfere with one another). As a specific example, the network node <b>114</b> may assign a first HARQ interlace to the access point <b>104</b> and assign a second HARQ interlace to the access point <b>106</b>. In this way, communication at one restricted access point may not substantially interfere with communication at the other restricted access point.
p-0058As represented by block <b>206</b>, the access point <b>104</b> (e.g., the interference controller <b>322</b>) determines interference management parameters that it may use or that may send to the access terminal <b>110</b>. In cases where the network node <b>114</b> defines the interference management parameters for the access point <b>104</b>, this determination operation may simply involve receiving the specified parameters and/or retrieving the specified parameters (e.g., from a data memory).
p-0059In some cases the access point <b>104</b> determines the interference management parameters on its own. These parameters may be similar to the parameters discussed above in conjunction with block <b>202</b>. In addition, in some cases these parameters may be determined in a similar manner as discussed above at block <b>202</b>. For example, the access point <b>104</b> may receive information (e.g., measurement reports, CQI, DRC) from the access terminal <b>110</b>. In addition, the access point <b>104</b> may monitor an uplink and/or a downlink to determine the interference on such a link. The access point <b>104</b> also may randomly select a parameter.
p-0060In some cases, the access point <b>104</b> may cooperate with one or more other access points to determine an interference management parameter. For example, in some cases the access point <b>104</b> may communicate with the access point <b>106</b> to determine which parameters are being used by the access point <b>106</b> (and thereby selects different parameters) or to negotiate the use of different (e.g., mutually exclusive) parameters. In some cases, the access point <b>104</b> may determine whether it may interfere with another node (e.g., based on CQI feedback that indicates that another node is using a resource) and, if so, define its interference management parameters to mitigate such potential interference.
p-0061As represented by block <b>208</b>, the access point <b>104</b> (e.g., the communication controller <b>328</b>) may send interference management parameters or other related information to the access terminal <b>110</b>. In some cases this information may relate to power control (e.g., specifies uplink transmit power).
p-0062As represented by blocks <b>210</b> and <b>212</b>, the access point <b>104</b> may thus transmit to the access terminal <b>110</b> on the downlink or the access terminal <b>110</b> may transmit to the access point <b>104</b> on the uplink. Here, the access point <b>104</b> may use its interference management parameters to transmit on the downlink and/or receive on the uplink. Similarly, the access terminal <b>110</b> may take these interference management parameters into account when receiving on the downlink or transmitting on the uplink.
p-0063In some implementations the access terminal <b>110</b> (e.g., the interference controller <b>306</b>) may define one or more interference management parameters. Such a parameter may be used by the access terminal <b>110</b> and/or sent (e.g., by the communication controller <b>330</b>) to the access point <b>104</b> (e.g., for use during uplink operations).
p-0064<figref idrefs="DRAWINGS">FIG. 4</figref> illustrates a wireless communication system <b>400</b>, configured to support a number of users, in which the teachings herein may be implemented. The system <b>400</b> provides communication for multiple cells <b>402</b>, such as, for example, macro cells <b>402</b>A-<b>402</b>G, with each cell being serviced by a corresponding access node <b>404</b> (e.g., access nodes <b>404</b>A-<b>404</b>G). As shown in <figref idrefs="DRAWINGS">FIG. 4</figref>, access terminals <b>406</b> (e.g., access terminals <b>406</b>A-<b>406</b>L) may be dispersed at various locations throughout the system over time. Each access terminal <b>406</b> may communicate with one or more access nodes <b>404</b> on a downlink (DL) (also known as forward link (FL)) and/or an uplink (UL) (also known as a reverse link (RL)) at a given moment, depending upon whether the access terminal <b>406</b> is active and whether it is in soft handoff, for example. The wireless communication system <b>400</b> may provide service over a large geographic region. For example, macro cells <b>402</b>A-<b>402</b>G may cover a few blocks in a neighborhood.
p-0065As stated, a node or localized access point that provides coverage over a relatively small area (e.g., a residence) may be referred to as a femto node. <figref idrefs="DRAWINGS">FIG. 5A</figref> illustrates an exemplary communication system <b>500</b> where one or more femto nodes are deployed within a network environment. Specifically, the system <b>500</b> includes multiple femto nodes <b>510</b> (e.g., femto nodes <b>510</b>A and <b>510</b>B) installed in a relatively small scale network environment (e.g., in one or more user residences <b>530</b>). Each femto node <b>510</b> may be coupled to a wide area network <b>540</b> (e.g., the Internet) and a mobile operator core network <b>550</b> via a DSL router, a cable modem, a wireless link, or other connectivity means (not shown). As will be discussed below, each femto node <b>510</b> may be configured to serve associated access terminals <b>520</b> (e.g., access terminal <b>520</b>A) and, optionally, non-associated (alien) access terminals <b>520</b> (e.g., access terminal <b>520</b>F). In other words, access to femto nodes <b>510</b> may be restricted whereby a given access terminal <b>520</b> may be served by a set of designated home femto node(s) <b>510</b> but may not be served by any non-designated foreign (alien) femto nodes <b>510</b> (e.g., a neighbor's femto node <b>510</b>).
p-0066<figref idrefs="DRAWINGS">FIG. 5B</figref> illustrates a more detailed view of negative geometries of multiple femto nodes and access terminals within a network environment. Specifically, the femto node <b>510</b>A and femto node <b>510</b>B are respectively deployed in neighboring user residence <b>530</b>A and user residence <b>530</b>B. Access terminals <b>520</b>A-<b>520</b>C are permitted to associate and communicate with femto node <b>510</b>A, but not with femto node <b>510</b>B. Likewise, access terminal <b>520</b>D and access terminal <b>520</b>E are permitted to associate and communicate with femto node <b>510</b>B, but not with femto node <b>510</b>A. Access terminal <b>520</b>F and access terminal <b>520</b>G are not permitted to associate or communicate with either femto node <b>510</b>A or femto node <b>510</b>B. Access terminal <b>520</b>F and access terminal <b>520</b>G may be associated with a macro cell access node <b>560</b> (<figref idrefs="DRAWINGS">FIG. 5A</figref>), or another femto node in another residence (not shown).
p-0067In unplanned femto node <b>510</b> deployments with restricted associations (i.e., an access point may not be allowed to associate with the “closest” femto node providing the most favorable signal quality), jamming and negative geometries can be common. Solutions to address these negative geometries will be further discussed below.
p-0068<figref idrefs="DRAWINGS">FIG. 6</figref> illustrates an example of a coverage map <b>600</b> where several tracking areas <b>602</b> (or routing areas or location areas) are defined, each of which includes several macro coverage areas <b>604</b>. Here, areas of coverage associated with tracking areas <b>602</b>A, <b>602</b>B, and <b>602</b>C are delineated by the wide lines and the macro coverage areas <b>604</b> are represented by the hexagons. The tracking areas <b>602</b> also include femto coverage areas <b>606</b>. In this example, each of the femto coverage areas <b>606</b> (e.g., femto coverage area <b>606</b>C) is depicted within a macro coverage area <b>604</b> (e.g., macro coverage area <b>604</b>B). It should be appreciated, however, that a femto coverage area <b>606</b> may not lie entirely within a macro coverage area <b>604</b>. In practice, a large number of femto coverage areas <b>606</b> may be defined with a given tracking area <b>602</b> or macro coverage area <b>604</b>. Also, one or more pico coverage areas (not shown) may be defined within a given tracking area <b>602</b> or macro coverage area <b>604</b>.
p-0069Referring again to <figref idrefs="DRAWINGS">FIGS. 5A-5B</figref>, the owner of a femto node <b>510</b> may subscribe to mobile service, such as, for example, 3G mobile service, offered through the mobile operator core network <b>550</b>. In addition, an access terminal <b>520</b> may be capable of operating both in macro environments and in smaller scale (e.g., residential) network environments. In other words, depending on the current location of the access terminal <b>520</b>, the access terminal <b>520</b> may be served by an access node <b>560</b> of the macro cell mobile network <b>550</b> or by any one of a set of femto nodes <b>510</b> (e.g., the femto nodes <b>510</b>A and <b>510</b>B that reside within a corresponding user residence <b>530</b>). For example, when a subscriber is outside his home, he is served by a standard macro access node (e.g., node <b>560</b>) and when the subscriber is at home, he is served by a femto node (e.g., node <b>510</b>A). Here, it should be appreciated that a femto node <b>520</b> may be backward compatible with existing access terminals <b>520</b>.
p-0070A femto node <b>510</b> may be deployed on a single frequency or, in the alternative, on multiple frequencies. Depending on the particular configuration, the single frequency or one or more of the multiple frequencies may overlap with one or more frequencies used by a macro node (e.g., node <b>560</b>).
p-0071In some aspects, an access terminal <b>520</b> may be configured to connect to a preferred femto node (e.g., the home femto node of the associated access terminal <b>520</b>) whenever such connectivity is possible. For example, whenever the access terminal <b>520</b> is within the user's residence <b>530</b>, it may be desired that the access terminal <b>520</b> communicate only with the home femto node <b>510</b>.
p-0072In some aspects, if the access terminal <b>520</b> operates within the macro cellular network <b>550</b> but is not residing on its most preferred network (e.g., as defined in a preferred roaming list), the access terminal <b>520</b> may continue to search for the most preferred network (e.g., the home femto node <b>510</b>) using a Better System Reselection (“BSR”), which may involve a periodic scanning of available systems to determine whether better systems are currently available, and subsequent efforts to associate with such preferred systems. With the acquisition entry, the access terminal <b>520</b> may limit the search for specific band and channel. For example, the search for the most preferred system may be repeated periodically. Upon discovery of a preferred femto node <b>510</b>, the access terminal <b>520</b> selects the femto node <b>510</b> for camping within its coverage area.
p-0073A femto node may be restricted in some aspects. For example, a given femto node may only provide certain services to certain access terminals. In deployments with so-called restricted (or closed) association, a given access terminal may only be served by the macro cell mobile network and a defined set of femto nodes (e.g., the femto nodes <b>510</b> that reside within the corresponding user residence <b>530</b>). In some implementations, a node may be restricted to not provide, for at least one node, at least one of: signaling, data access, registration, paging, or service.
p-0074In some aspects, a restricted or foreign (alien) femto node (which may also be referred to as a Closed Subscriber Group Home NodeB) is one that provides service to a restricted provisioned set of access terminals. This set may be temporarily or permanently extended as necessary. In some aspects, a Closed Subscriber Group (“CSG”) may be defined as the set of access nodes (e.g., femto nodes) that share a common access control list of access terminals. A channel on which all femto nodes (or all restricted femto nodes) in a region operate may be referred to as a femto channel.
p-0075Various relationships may thus exist between a given femto node and a given access terminal. For example, from the perspective of an access terminal, an open femto node may refer to a femto node with no restricted association. A restricted femto node may refer to a femto node that is restricted in some manner (e.g., restricted for association and/or registration). A home femto node may refer to a femto node on which the access terminal is authorized to access and operate on. A guest femto node may refer to a femto node on which an access terminal is temporarily authorized to access or operate on. A restricted or foreign (alien) femto node may refer to a femto node on which the access terminal is not authorized to access or operate on, except for perhaps emergency situations (e.g., 911 calls).
p-0076From a restricted or foreign femto node perspective, an associated or home access terminal may refer to an access terminal that authorized to access the restricted femto node. A guest access terminal may refer to an access terminal with temporary access to the restricted femto node. A non-associated (alien) access terminal may refer to an access terminal that does not have permission to access the restricted femto node, except for perhaps emergency situations, for example, such as 911 calls (e.g., an access terminal that does not have the credentials or permission to register with the restricted femto node).
p-0077For convenience, the disclosure herein describes various functionality in the context of a femto node. It should be appreciated, however, that a pico node may provide the same or similar functionality for a larger coverage area. For example, a pico node may be restricted, a home pico node may be defined for a given access terminal, and so on.
p-0078A wireless multiple-access communication system may simultaneously support communication for multiple wireless access terminals. As mentioned above, each terminal may communicate with one or more base stations via transmissions on the downlink (forward link) and uplink (reverse link). The downlink refers to the communication link from the base stations to the terminals, and the uplink refers to the communication link from the terminals to the base stations. This communication link may be established via a single-in-single-out system, a multiple-in-multiple-out (“MIMO”) system, or some other type of system.
p-0079A MIMO system employs multiple (N<sub>T</sub>) transmit antennas and multiple (N<sub>R</sub>) receive antennas for data transmission. A MIMO channel formed by the N<sub>T </sub>transmit and N<sub>R </sub>receive antennas may be decomposed into N<sub>S </sub>independent channels, which are also referred to as spatial channels, where N<sub>S</sub>≦min {N<sub>T</sub>, N<sub>R</sub>}. Each of the N<sub>S </sub>independent channels corresponds to a dimension. The MIMO system may provide improved performance (e.g., higher throughput and/or greater reliability) if the additional dimensionalities created by the multiple transmit and receive antennas are utilized.
p-0080A MIMO system may support time division duplex (“TDD”) and frequency division duplex (“FDD”). In a TDD system, the forward and reverse link transmissions are on the same frequency region so that the reciprocity principle allows the estimation of the downlink (forward link) channel from the uplink (reverse link) channel. This enables the access point to extract transmit beam-forming gain on the downlink when multiple antennas are available at the access point.
p-0081As stated, in unplanned base station deployments with restricted association (i.e., a mobile station is not allowed to associate with the “closest” base station to which it has the strongest link), jamming and negative geometries can be common. In one exemplary embodiment spatially described in conjunction with <figref idrefs="DRAWINGS">FIG. 5B</figref>, the femto node <b>510</b>A and femto node <b>510</b>B are deployed in neighboring residences. Access terminals <b>520</b>A-<b>520</b>C are permitted to associate and communicate with femto node <b>510</b>A, but not with femto node <b>510</b>B. Likewise, access terminals <b>520</b>D-<b>520</b>E are permitted to associate and communicate with femto node <b>510</b>B, but not with femto node <b>510</b>A. Access terminals <b>520</b>F-<b>520</b>G are not permitted to associate or communicate with either femto nodes <b>510</b>A-<b>510</b>B. Access terminals <b>520</b>F-<b>520</b>G may be associated with a macro cell access node <b>560</b> (<figref idrefs="DRAWINGS">FIG. 5A</figref>), or another femto node in another residence (not shown). Accordingly, such negative geometries respecting access-permitted femto nodes and neighboring access terminals may result if various interfering or jamming conditions on the uplink and downlink.
p-0082Uplink Jamming
p-0083By way of example, let L<sub>A3 </sub>(dB) and L<sub>A5 </sub>(dB) be the path loss between femto node <b>510</b>A and access terminal <b>520</b>C and access terminal <b>520</b>D, respectively. In particular, L<sub>A3 </sub>may be much larger than L<sub>A5</sub>. Thus, when access terminal <b>520</b>D transmits to its home femto node <b>510</b>B, it causes excessive interference (or jamming) at femto node <b>510</b>A, effectively blocking the reception of access terminals <b>520</b>A-C at femto node <b>510</b>A. In this uplink jamming situation, even if access terminal <b>520</b>C transmits at its maximum Tx power P<sub>3max</sub>, the received C/I for access terminal at femto node <b>510</b>A may be characterized as:
p-0084<br /><i>C/I</i>(AT 520<i>C </i>at femto node 510<i>A</i>)=<i>P</i><sub>3max</sub><i>−L</i><sub>A3</sub>−(<i>P</i><sub>5</sub><i>−L</i><sub>A5</sub>) (dB)
p-0085In some exemplary embodiments, depending on the transmit power P<sub>5</sub>, the C/I of access terminal <b>520</b>C at femto node <b>510</b>A may be a very large negative value due to the large value of L<sub>A3</sub>. Such a configuration geometry is referred to as a highly negative uplink geometry.
p-0086Downlink Jamming
p-0087Similarly, in one exemplary embodiment, L<sub>B5 </sub>may be much larger than L<sub>A5</sub>. This implies that when femto node <b>510</b>A transmits to access terminal <b>520</b>A, it may cause excessive interference (or jamming) at access terminal <b>520</b>D, effectively blocking the reception of femto node <b>510</b>B at access terminal <b>520</b>D. In this downlink jamming situation, the received C/I for femto node <b>510</b>B at access terminal <b>520</b>D may be calculated as follows:
p-0088<br /><i>C/I</i>(femtocell <i>B </i>at AT 5)=<i>P</i><sub>B</sub><i>−L</i><sub>B5</sub>−(<i>P</i><sub>A</sub><i>−L</i><sub>A5</sub>) (dB)
p-0089Again, the C/I of femto node <b>510</b>B at access terminal <b>520</b>D may be a very large negative value due to the large value of L<sub>B5</sub>. Such a configuration geometry is referred to as a highly negative downlink geometry.
p-0090A further practical consideration includes addressing negative geometries without necessitating modifications to the operation of deployed (legacy) access terminals. Therefore, it is desirable in the present exemplary embodiment to address interference mitigation from negative geometries through modification processes in a femto node rather than requiring modifications to access terminals. Accordingly, negative geometries at the uplink and downlink are desirably addressed according to an exemplary embodiment disclosed below.
p-0091Referring now to <figref idrefs="DRAWINGS">FIG. 7</figref> and with further reference to <figref idrefs="DRAWINGS">FIGS. 5A-5B</figref>, operations relating to the use of beam-steering and null-steering to address jamming and negative geometries will be described in more detail. The present exemplary embodiment uses methods and apparatus to prevent jamming and negative geometries using beamsteering and null steering in unplanned base station deployments with restricted access.
p-0092In an exemplary femto node deployment scenario, nearby signals (desired or interference) may be Rician by nature which includes a strong directional component and flat fading across the frequency band (due to the small delay-spread and multiple reflected paths in indoor environments). Especially for jamming situations, sectorization may provide a desirable method for combating a strong Rician component of interference.
p-0093As represented by block <b>702</b>, a femto node <b>510</b> continuously listens (i.e., receives according to the various receiver configurations describe herein) for transmissions from access terminals <b>520</b>. As represented by query <b>704</b>, the femto node <b>510</b> determines if an access probe (e.g., transmission) by an access terminal are directed to the femto node <b>510</b>. If the detected access probe of the access terminal is directed to the specific femto node <b>510</b>, then, as represented by block <b>706</b>, no interference mitigation is necessary since the access terminal is an “associated” access terminal with the “home” femto node.
p-0094As represented by query <b>708</b>, femto node <b>510</b> further compares a characteristic (e.g., power level) of the access probe for determining if the characteristic is of a sufficient threshold level to result in interference at the home femto node. When the access probe does not exceed an interference threshold, then, as represented by block <b>706</b>, no interference mitigation is necessary since the characteristic of the access probe by the “home” femto node <b>510</b> results in acceptable interference.
p-0095As represented by block <b>710</b>, when the home femto node <b>510</b> receives a sufficiently strong (i.e., greater than an interference threshold) access probe or otherwise strong uplink transmission from the non-associated access terminal <b>520</b>, the home femto node <b>510</b> applies beam-forming (i.e., directional transmission and reception) antennas to steer signals or lack of signals (e.g., nulls) toward the non-associated access terminal <b>520</b> on the downlink and uplink.
p-0096By way of example, beam-forming (i.e., beam-steering) may be performed using a sectorized or directional (e.g., switched beam) antenna configuration described herein for forming a transmission signal beam and/or null or a reception signal beam and/or null. Specifically, interference nulling may be provided on a received Radio Frequency (RF) signal thereby reducing problems such as front-end overload and A/D desensitization of the receiver which results from jamming femto nodes. Furthermore, sectorized or directional antenna configurations enable the downlink and uplink to maintain the same directional component for use in both link directions.
p-0097As represented by block <b>712</b>, downlink pilot and overhead transmissions, as well as traffic channel transmissions if any, are transmitted according to beam-forming such that minimal energy is directed towards a nearby non-associated access terminal. Steering a transmission signal away from a non-associated access terminal results in reduction in the negative geometry at the non-associated access terminal.
p-0098As represented by block <b>714</b>, a directional null is steered towards the nearby non-associated access terminal <b>520</b> using the antenna configuration (e.g., sectorized antennas or null-steering with adaptive phased arrays) described herein. Therefore, when an associated access terminal <b>520</b> attempts to communicate with the home femto node <b>510</b>, the associated access terminal's access probe, as well as other traffic (e.g., voice/data) communications is not jammed by the strong transmissions from the nearby non-associated access terminals having negative geometries.
p-0099As an example, if the access point employs two separate antennas AP can monitor the AT access probe characteristics on both antennas. If it is determined that the strong uplink transmission from the non-associated access terminal at one of the antennas, AP can turn off transmit function (beam steering) and turn off receive function (null steering) on that antenna.
p-0100As represented in query <b>716</b>, periodically (e.g., once per second) the femto node <b>510</b> eliminates the sectorization null in the receive direction to determine, as represented in block <b>702</b>, if the strong undesired non-associated access terminal <b>520</b> has moved or terminated its communication. If, as represented in query <b>704</b>, the strong undesired signal has disappeared, the femto node <b>510</b> can eliminate the sectorization null and continue operation with omni-directional transmit and receive, as represented in block <b>706</b>. If the strong undesired signal is still present or has moved and exceeds the threshold as represented by block <b>708</b>, the femto node <b>510</b> can adjust the transmit and receive sectorization null steering, as represented in block <b>710</b>, in the direction of the undesired non-associated access terminal <b>520</b>.
p-0101The above-example with reference to <figref idrefs="DRAWINGS">FIG. 5B</figref> illustrates femto node <b>510</b>A steering a receive and transmit sectorization null in the direction of non-associated access terminal <b>520</b>D as long as non-associated access terminal <b>520</b>D was present and in an active call with femto node <b>510</b>B. When non-associated access terminal <b>520</b>D is idle, femto node <b>510</b>A would revert back to operating with omnidirectional transmit and receive.
p-0102During periods when the femto node is steering a sectorization null in a particular direction, if there are any associated access terminals <b>520</b> in the same direction they would experience outage. Accordingly, an exemplary embodiment, the femto node <b>510</b> steers the sectorization nulls (i) as long as the strong undesired non-associated access terminal <b>520</b> is active, and (ii) only if the undesired transmission from the non-associated access terminal <b>520</b> exceeds a high signal strength threshold at the receiver as determined at query <b>408</b>, signifying that access probes from desired associated access terminals would not be decodable at the femto node <b>510</b>. With reference to <figref idrefs="DRAWINGS">FIG. 5B</figref>, it is noted that femto node <b>510</b>B would have no need to steer a sectorization null towards non-associated access terminal <b>520</b>A since the signal from non-associated access terminal <b>520</b>A is not very strong. If femto node <b>510</b>B steers such a sectorization null towards non-associated access terminal <b>520</b>A, the sectorization null would resulting an outage at desired associated access terminal <b>520</b>E.
p-0103As a general case of the described method if the AP can not determine the direction of the interference from the non-associated access terminal (e.g., very strong jamming that saturates the AP receiver) it can try different directions for beam steering and null steering to maximize the received signal quality from associated AT.
p-0104Referring now to <figref idrefs="DRAWINGS">FIG. 8</figref> and with further reference to <figref idrefs="DRAWINGS">FIGS. 5A-5B</figref>, operations relating to the use of optimization in transmit power on overhead channels to address jamming and negative geometries will be described in more detail. The present exemplary embodiment uses methods and apparatus to prevent jamming and negative geometries using optimized transmit power levels on overhead channels in unplanned base station deployments.
p-0105Generally, the transmit power gain of overhead channels and total transmit power of a femto node are chosen based on the desired range of a femto node. In order to allow access terminals to acquire a femto node in a location where the access terminal is being jammed by a neighbor femto node that restricts association, the overhead channels (e.g., common control channels such as pilot, synch and broadcast/paging) may be time multiplexed. Various numbers of time scales and methods for time multiplexing are contemplated. Furthermore, the overhead channels may be turned on only periodically, for example at the slot cycle index of the associated access terminals, so that the associated access terminals may receive paging messages. In a further configuration, a femto node may not transmit any signal at all.
p-0106However, during an active voice call or data transfer, there may be no idle periods that allow a neighbor femto node the opportunity to time multiplex the overhead channels jamming situations resulting from negative geometries. Accordingly, an exemplary embodiment describes a method for optimizing transmit power for overhead signals (e.g., pilot, synch and broadcast/paging channels) when there is an active call at a femto node and time multiplexing of overhead signals is not practical.
p-0107For example in 1×RTT and WCDMA networks, overhead channel (e.g., pilot, page, sych. channels) gain settings are adjusted for certain performance based on geometry and coverage constraints. Furthermore, femto node deployments exhibit some significant differences when compared to macro cell access node deployments. Various differences include: <ul><li id="ul0002-0001" num="0000"><ul><li id="ul0003-0001" num="0110">1. Due to limited coverage size, maximum path loss values are much less in areas (e.g., cells) serviced by femto nodes compared to areas (e.g., cells) serviced by macro cell access nodes (e.g., 80 dB max path loss compared to 140 dB in a macrocellular deployment);</li><li id="ul0003-0002" num="0111">2. The number of simultaneously active access terminals are fewer in cells serviced by femto nodes than in cells serviced by macro cell access nodes (e.g., 1-2 users compared to 20-40 users);</li><li id="ul0003-0003" num="0112">3. As discussed above, due to the femto node restricted association requirements, negative geometries can be common for femto node deployments unlike for macro cell access node deployments.</li></ul></li></ul>
p-0108These differences can result in very different optimal power settings for overhead channels for femto nodes <b>510</b>. Since a femto node <b>510</b> generally will have few to no active access terminals <b>520</b>, it would be desirable for the overhead channels to be maintained at a minimum power setting in order to minimize interference to neighboring cells serviced by femto nodes <b>510</b> and cells serviced by macro cell access nodes <b>560</b> (i.e., assuming co-channel operation). By way of example, one exemplary embodiment focuses on pilot channel optimization, however, the analysis can be applied to other overhead channels as well.
p-0109In the exemplary embodiment, an optimal traffic-to-pilot (“T2P”) value for the case of a single voice call is determined as well as a default pilot power setting, Ecp<sub>DEFAULT</sub>. When downlink (forward link) power control results in a modified ratio of traffic-to-pilot, the pilot power is adjusted so as to maintain the smallest value of total transmitted power and interference caused by the neighbor femto node.
p-0110By way of example, an access terminal <b>520</b>A at the boundary of home femto node <b>510</b>A and neighbor femto node <b>510</b>B exhibits equal path loss to both femto nodes <b>510</b> and the neighbor femto node <b>520</b>B is transmitting at full power thereby creating interference, Ior_max. In the present example, assuming the home femto node <b>510</b>A is transmitting a pilot channel at a gain level, Ecp, then the pilot signal-to-noise ratio (SNR) can be written as: Ecp/Ior_max. According to the present exemplary embodiment, it is desirable to find the optimal Ecp setting that results in lowest total transmitted power from a home femto node <b>510</b>A.
p-0111As represented by block <b>802</b>, the pilot channel gain level Ecp is initialized to Ecp<sub>DEFAULT</sub>. Thus, a default value of Ecp (Ecp<sub>DEFAULT</sub>) can be determined based on a reasonable load and path loss differential values expected in femto networks.
p-0112As represented in block <b>804</b>, a traffic call (e.g., voice call) is set up between the home femto <b>510</b>A and an access terminal <b>520</b>A with the power used on traffic channel denoted as Ect. In one exemplary embodiment, the Ect value is determined by the downlink (forward link) power control, as represented by query <b>806</b>. Downlink (forward link FL) power control is used to maintain the required quality of service (e.g, packet error rate, PER). Downlink (forward link FL) power controls may either designate a decrease in Ect as represented by block <b>808</b>, an increase in Ect as represented by block <b>810</b>, or no change in Ect.
p-0113As represented in query <b>812</b>, a determination of the packet error rate (PER) is used to identify adequate signal quality. Generally, if Ecp is very low, then channel estimation quality would degrade which will result in very large Ect. As Ecp increases, channel estimation will improve and the required Ect will go down. However, if Ecp is very large, then channel estimation quality will be higher than the required amount, which will not result any further reduction in Ect. Accordingly, when PER is inadequate, downlink (forward link FL) power control adjusts the Ect.
p-0114Since the interference generated to other femto nodes needs to be minimized, it would be desirable to have the optimal Ecp value that results in the minimum (Ect+Ecp). As represented by block <b>814</b>, Ecp<sub>OPTIMAL </sub>is determined where:
p-0115<maths id="MATH-US-00001" num="00001"><math overflow="scroll"><mrow><msub><mi>Ecp</mi><mi>OPTIMAL</mi></msub><mo>=</mo><mrow><mi>arg</mi><mo></mo><mrow><munder><mi>min</mi><mi>Ecp</mi></munder><mo></mo><mrow><mo>[</mo><mrow><mi>Ecp</mi><mo>+</mo><mrow><mi>f</mi><mo></mo><mrow><mo>(</mo><mi>Ecp</mi><mo>)</mo></mrow></mrow></mrow><mo>]</mo></mrow></mrow></mrow></mrow></math></maths><ul><li id="ul0004-0001" num="0000"><ul><li id="ul0005-0001" num="0120">in other optimal Ecp value is found that minimizes total transmit power where</li></ul></li></ul>
p-0116<br /><i>Ect</i>=ƒ(<i>Ecp</i>)<ul><li id="ul0006-0001" num="0000"><ul><li id="ul0007-0001" num="0121">(The function ƒ(.) can be determined through offline simulations or tests.) Then, as represented by block <b>816</b>, the optimal Ect value is determined as:</li></ul></li></ul>
p-0117<br /><i>Ect</i><sub>OPTIMAL</sub>=ƒ(<i>Ecp</i><sub>OPTIMAL</sub>).
p-0118As represented by block <b>818</b>, the T2P<sub>OPTIMAL </sub>is determined as:
p-0119<maths id="MATH-US-00002" num="00002"><math overflow="scroll"><mrow><mrow><mi>T</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mn>2</mn><mo></mo><msub><mi>P</mi><mi>OPTIMAL</mi></msub></mrow><mo>=</mo><mrow><mfrac><msub><mi>Ect</mi><mi>OPTIMAL</mi></msub><msub><mi>Ecp</mi><mi>OPTIMAL</mi></msub></mfrac><mo>.</mo></mrow></mrow></math></maths>
p-0120In another exemplary embodiment, simulations may be run to find the Ecp<sub>OPTIMAL </sub>and Ect<sub>OPTIMAL </sub>for typical channel types expected in cells of femto nodes using, for example, flat fading models, either Rayleigh or Rician, with low Doppler that can be tracked by power control. These optimal values depend, in one exemplary embodiment, on the particular path loss differential of the access terminal to neighbor femto node and the interference power received from the neighbor femto node (e.g., if the mobile terminal has 3 dB less path loss to neighbor femto compared to home femto, then the optimal Ecp and Ect values would need to increased by 3 dB).
p-0121On the other hand, in an alternate exemplary embodiment, if neighbor femto node is transmitting at half of Ior_max, then optimal Ecp and Ect values would need to be reduced by 3 dB. However, also note that it is not very practical to change Ecp values very frequently since it determines the handoff boundaries of the femto cell. Thus, as stated, a default value of Ecp (Ecp<sub>DEFAULT</sub>) can be determined based on a reasonable load and path loss differential values expected in femto networks.
p-0122Referring now to <figref idrefs="DRAWINGS">FIG. 9</figref>, to maintain optimal operation for cases with higher then expected load and path loss differential, in one exemplary embodiment, the following algorithm can be run for each of a plurality of calls occurring between a femto node and multiple associated access terminals.
p-0123As represented by block <b>902</b>, the pilot channel gain level Ecp is initialized to Ecp<sub>DEFAULT </sub>for analysis of each voice call. Thus, a default value of Ecp (Ecp<sub>DEFAULT</sub>) can be determined based on a reasonable load and path loss differential values expected in femto networks.
p-0124As represented in block <b>904</b>, the process is repeated for each call set up between the home femto <b>510</b>A and associated access terminals <b>520</b> with the power used on traffic channel denoted as Ect. In one exemplary embodiment, the Ect value is determined by the downlink (forward link FL) power control, as represented by query <b>906</b>. Downlink (forward link FL) power control is used to maintain the required quality of service (e.g, packet error rate, PER). Downlink (forward link FL) power controls may either designate a decrease in Ect as represented by block <b>908</b>, an increase in Ect as represented by block <b>910</b>, or no change in Ect.
p-0125As represented in query <b>912</b>, a determination of the packet error rate (PER) is used to identify adequate signal quality. Accordingly, when PER is inadequate, downlink (forward link FL) power control adjusts the Ect.
p-0126As represented by block <b>918</b>, the T2P<sub>FILTERED </sub>(e.g., Ect<sub>FILTERED</sub>/Ecp<sub>FILTERED</sub>) is monitored during the call. The purpose of filtering T2P would be to eliminate small scale fluctuations from the T2P calculation. E.g., a moving average filter can be used to filter Ect and Ecp values to compute Ect<sub>FILTERED </sub>and Ecp<sub>FILTERED </sub>respectively.
p-0127As represented in query <b>920</b>, a determination is made as to the value of T2P<sub>FILTERED</sub>. If T2P<sub>FILTERED</sub>>T2P<sub>OPTIMAL</sub>+Δ<sub>1</sub>, then as represented in block <b>922</b> Ecp is increased to
p-0128<br /><i>Ecp=Ect</i><sub>FILTERED</sub><i>/T</i>2<i>P</i><sub>OPTIMAL</sub>.
p-0129As represented in query <b>924</b>, a determination is made as the value of T2P<sub>FILTERED</sub>. If T2P<sub>FILTERED</sub><T2P<sub>OPTIMAL</sub>−Δ<sub>2</sub>, then as represented in block <b>926</b> Ecp is decreased to
p-0130<br /><i>Ecp</i>=max[<i>Ect</i><sub>FILTERED</sub><i>/T</i>2<i>P</i><sub>OPTIMAL</sub><i>,Ecp</i><sub>DEFAULT</sub>].
p-0131T2P<sub>OPTIMAL </sub>depends on particular traffic configuration (rate, coding etc.). For example, if two users are performing voice calls with same rate vocoders, they would have same T2P<sub>OPTIMAL</sub>. However if there is another user performing data transfer (e.g., 1×RTT data transfer at 153 kbps) it would require a different T2P<sub>OPTIMAL</sub>. Once the T2P<sub>OPTIMAL </sub>is determined for given user (based on its traffic type), then the algorithm automatically adjusts Ecp. The above algorithm is specified for one user. If there are multiple users, then the algorithm may result in different Ecp values for each user. However, overhead channels are common to all users and we can only have one Ecp setting. Thus the algorithm could be generalized to a multiple users case. By way of example, an “optimal” Ecp<sub>i </sub>for each user (i=1, . . . , N) in the system could be found as described above and then an actual Ecp could be decided as max(Ecp<sub>1</sub>, . . . , Ecp<sub>N</sub>). Another option could be to find the optimal Ecp such that total power transmitted as overhead and traffic to all users is minimized. This would mean a modification of the calculation of box <b>814</b> to:
p-0132<maths id="MATH-US-00003" num="00003"><math overflow="scroll"><mrow><msub><mi>Ecp</mi><mi>OPTIMAL</mi></msub><mo>=</mo><mrow><mi>arg</mi><mo></mo><mrow><munder><mi>min</mi><mi>Ecp</mi></munder><mo></mo><mrow><mo>[</mo><mrow><mi>Ecp</mi><mo>+</mo><mrow><msub><mi>f</mi><mn>1</mn></msub><mo></mo><mrow><mo>(</mo><msub><mi>Ecp</mi><mn>1</mn></msub><mo>)</mo></mrow></mrow><mo>+</mo><mi>…</mi><mo>+</mo><mrow><msub><mi>f</mi><mi>N</mi></msub><mo></mo><mrow><mo>(</mo><msub><mi>Ecp</mi><mi>N</mi></msub><mo>)</mo></mrow></mrow></mrow><mo>]</mo></mrow></mrow></mrow></mrow></math></maths>
p-0133for users <b>1</b> to N in the femtocell. The purpose of filtering T2P would be to eliminate small scale fluctuations from the T2P calculation. E.g., a moving average filter can be used to filter Ect and Ecp values to compute Ect<sub>FILTERED </sub>and Ecp<sub>FILTERED </sub>respectively.
p-0134The optimal T2P may be obtained through simulations and once the T2P is decided, power control adjust Ect (which is part of standard 3G operation) may be determined. Then the Ecp is adjusted to achieve/maintain optimal T2P. Specifically, two algorithms may run together: 1) the power control algorithm adjusting Ect and 2) the adjustment of Ecp described herein.
p-0135In the above algorithm, Δ<sub>1 </sub>and Δ<sub>2 </sub>are hystheresis parameters used to prevent fast fluctuations of Ecp. Furthermore, in order to prevent abrupt changes of Ecp equations above may be modified, in one exemplary embodiment, to let the Ecp correction to be performed more slowly. Lastly, other overhead channels (e.g., page, sych) can be adjusted based on the pilot power level (i.e., their relative power level with respect to pilot power level can be kept constant).
p-0136Accordingly, exemplary embodiments have been described for reducing transmit power for overhead signals (e.g., pilot, synch and broadcast/paging channels) when there is an active call at a femto node by determining an optimal overhead signal power level. The exemplary embodiment has been disclosed by way of example using in the pilot channel as the exemplary channel, however, the analysis can be applied to other overhead channels as well.
p-0137Referring now to <figref idrefs="DRAWINGS">FIG. 10</figref> and with further reference to <figref idrefs="DRAWINGS">FIGS. 5A-5B</figref>, operations relating to the use of frequency selective transmission to address jamming and negative geometries will be described in more detail. As stated, due to unplanned deployment of femto nodes, the received SINR for an associated access terminal can become very low due to interference from a neighbor femto node transmission. This interference degrades control channel and traffic channel performance for the access terminal and may result in outages or decreased services. The exemplary embodiment disclosed herein addresses operations to improve the performance of an access terminal in a high interference area without the need to change legacy access terminals.
p-0138Generally, the exemplary embodiment introduces intentional frequency selectivity in downlink transmissions by orthogonalizing the transmit waveform among neighboring femto nodes to minimize interference. As an example, each femto node <b>510</b> selects transmit pulse shaping via channel sensing from available waveforms, for example, from three 3-tap channel waveforms, with each coefficient set from a given row of, for example, a 3×3 DFT matrix. In this case each for a given access point, the transmitted waveform would be filtered by a three tap FIR (in addition to normal baseband filtering) with filter impulse responses selected from one of the following three waveforms:
p-0139<br /><i>h</i><sub>1</sub><i>[n]=δ[n]+δ[n−</i>2]+δ[<i>n−</i>4]
p-0140<br /><i>h</i><sub>2</sub><i>[n]=δ[n]+e</i><sup>j</sup><sup><sup2>2π/3</sup2></sup><i>δ[n−</i>2]+<i>e</i><sup>−j</sup><sup><sup2>2π/3</sup2></sup><i>δ[n−</i>4]=δ[<i>n</i>]+(−0.5+<i>j</i>0.866)·δ[<i>n−</i>2]+(−0.5−<i>j</i>0.866)·δ[<i>n−</i>4]
p-0141<br /><i>h</i><sub>3</sub><i>[n]=δ[n]+e</i><sup>−j</sup><sup><sup2>2π/3</sup2></sup><i>δ[n−</i>2]+<i>e</i><sup>j</sup><sup><sup2>2π/3</sup2></sup><i>δ[n−</i>4]==δ[<i>n</i>]+(−0.5−<i>j</i>0.866)·δ[<i>n−</i>2]+(−0.5+<i>j</i>0.866)·δ[<i>n−</i>4]
p-0142where exp(jx)=cos(x)+j sin(x).
p-0143An alternative choice is two impulse responses with coefficient from 2×2 DFT (N=2). The choice of transmit filter stays for a certain period, after which the femto node <b>510</b> may make the selection again based on channel sensing.
p-0144With initial reference to <figref idrefs="DRAWINGS">FIG. 10</figref>, <figref idrefs="DRAWINGS">FIG. 10</figref> describes method for interference management in a wireless communication system transmit waveform selection. As represented by block <b>1002</b>, a set of N transmit waveforms are allocated to femto nodes <b>510</b> for use in downlink transmissions. In one exemplary embodiment, the channel waveforms may be formed from coefficients of an N-tap channel filter with each coefficient set being derived from a specific row in an N×N DFT matrix.
p-0145As represented by block <b>1004</b>, a femto node <b>510</b> selects a default waveform upon initialization (e.g., power up) according to a defined selection process (e.g., randomization, randomly assigned by the network, etc.). The default waveform from the set of N transmit (downlink) waveforms. The default waveform is initially assigned as the preferred transmit waveform, TxWave<sub>PREFERED</sub>.
p-0146As represented by query <b>1006</b>, the femto node <b>510</b> transmits on the downlink using the preferred transmit waveform when a call is initiated. Call setup with the associated access terminal <b>520</b> occurs and includes channel quality indications (e.g., Channel Quality Indicator CQI, Data Rate Control DRC) determined by the access terminal <b>520</b> and forwarded to the femto node <b>510</b> on the uplink.
p-0147As represented by query <b>1008</b>, the femto node initiates a waveform testing cycle for a time period of T_test_waveform until all the possible waveforms have been tested. As represented by block <b>1010</b>, the femto node <b>510</b> communicates with the associated access terminal <b>520</b> using the current waveform. The associated access terminal receives the downlink transmissions and generates a channel quality indication in response to the signal quality. The channel quality indication is forwarded in the uplink (reverse link) to the femto node <b>510</b>.
p-0148As represented by block <b>1012</b>, the femto node monitors the uplink to determine the channel quality using the current waveform based on the received channel quality indication. The femto node <b>510</b> may either form a table of waveforms and corresponding channel quality indications, or compare the current channel quality indication with any previous channel quality indications and retained an indication of the preferred waveform.
p-0149As represented by block <b>1014</b>, the waveform testing increments to the next allocated waveform for continued evaluation. The exemplary waveform selection process iterates until the possible waveforms have been engaged for transmission on the downlink and the corresponding channel quality indication has been received on the uplink. As represented by block <b>1016</b>, the preferred waveform based upon channel quality determination is then selected as the preferred transmit waveform which provides the best channel quality in the presence of interference from negative geometries associated with deployments of other unplanned base station deployments.
p-0150As represented by block <b>1018</b>, the preferred waveform may be periodically updated based upon various factors including a specific time period, call termination, channel quality degradation threshold or other channel conditions know by those of ordinary skill in the art. Upon an update determination, processing returns to evaluate the channel quality of the various possible transmit waveforms.
p-0151The present exemplary embodiment manages interference from strong neighboring interference energy due to orthogonality of the Fourier series on the dominant signal energy during convolution, at the expense of creating self-noise through ISI and thereby limiting performance at high geometry. Further gains could be achieved with the use of MMSE equalizer due to different frequency coloring of impulse responses for the desired and interference signals. This mechanism is feasible in a femto node configuration as the delay spread is significantly smaller than one chip interval.
p-0152Referring now to <figref idrefs="DRAWINGS">FIGS. 11A-11B</figref> and with further reference to <figref idrefs="DRAWINGS">FIGS. 5A-5B</figref>, operations relating to the use of adaptive noise figure and path loss adjustment to address jamming and negative geometries will be described in more detail. The present exemplary embodiment uses methods and apparatus to prevent jamming and address jamming and negative geometries using adaptive noise figures and path loss adjustments.
p-0153Generally, femto nodes are connected to the Internet <b>540</b> and the mobile operator core network <b>550</b> via a wide band connection (e.g., DSL router or cable modem). Since the RF coverage of femto nodes <b>510</b> is not manually optimized by the mobile operator core network <b>550</b> and deployment is generally ad hoc, serious RF interference issues may arise unless appropriate interference mitigation methods are utilized.
p-0154In a macro cell network, access terminals <b>520</b> and macro cell access nodes <b>560</b> are designed to operate in a certain dynamic range. In cells formed by femto nodes <b>510</b>, a home femto node <b>510</b> and an associated access terminal <b>520</b> may be arbitrarily spatially nearby, thus creating very high signal levels beyond the sensitivity range of the respective receivers. On a downlink (forward link FL), such a configuration can saturate the receiver of associated access terminal and create degraded demodulation performance. On the reverse link, such a configuration can create very high noise rise (RoT), also known to create instability at the home femto node <b>510</b>. Thus maximum and minimum transmit power levels and receiver noise figure values need to be adjusted accordingly for home femto nodes <b>510</b>. This situation is illustrate in <figref idrefs="DRAWINGS">FIG. 5B</figref> with reference to home femto node <b>510</b>A and associated access terminal <b>520</b>A.
p-0155Femto nodes <b>510</b>B can cause interference both on the uplink UL (reverse link RL)) and in the downlink DL (forward link FL) of cells serviced by macro cell access nodes <b>560</b>. For example a femto node <b>510</b>B installed, for example, near a window of a residence <b>530</b>B can cause significant downlink DL interference to the access terminals <b>520</b>F outside the house (i.e., non-associated access terminal) that are not served by the femto node <b>510</b>B. Also, on the uplink UL, the associated access terminals <b>520</b> that are served by a specific home femto node <b>510</b> can cause significant interference on the macro cell access nodes <b>560</b>.
p-0156On the uplink UL, non-associated access terminals <b>520</b>F that are served by the macro cell access nodes <b>560</b> can cause significant interference on the home femto node <b>510</b>A.
p-0157As stated, femto nodes <b>510</b> can also create significant interference to each other due to unplanned deployment. For example in nearby residences <b>530</b>, a femto node <b>510</b> installed near a wall separating two residences <b>530</b> can cause significant interference to a neighboring femto node <b>510</b> in an adjacent residence <b>530</b>. In such a case, the strongest signal (in terms of RF signal strength) from a femto node <b>510</b> to an access terminal <b>520</b> may not necessarily be the associated access terminal's home femto node due to restricted association requirement described above. Such a scenario is illustrated in <figref idrefs="DRAWINGS">FIG. 5B</figref> where on the downlink DL, femto node <b>510</b>A may cause significant interference (e.g., low SINR) to access terminal <b>520</b>D. Also, on the uplink UL, non-associated access terminal <b>520</b>D may cause significant interference (e.g., high RoT) to foreign (alien) femto node <b>510</b>A.
p-0158For example, on the uplink of CDMA wireless networks, system stability and load is usually determined by the metric: rise over thermal (RoT), also know as noise rise, at the femto node. Rise over thermal (RoT) indicates the ratio between the total power received from all sources at the femto node and the thermal noise:
p-0159<br /><i>RoT</i>=(<i>Ioc+Ior+</i>No)/No,
p-0160where <ul><li id="ul0008-0001" num="0000"><ul><li id="ul0009-0001" num="0154">Ior: Total received power received at the femto node from all wireless devices for whom femto node is in their active set</li><li id="ul0009-0002" num="0155">Ioc: Total received power received at the femto node from all wireless devices for whom femto node is not in their active set</li><li id="ul0009-0003" num="0156">No: Variance of the thermal noise including the femto node noise figure (NF).</li></ul></li></ul>
p-0161For stable system operation on the uplink UL, RoT needs to be controlled. Typically, RoT is controlled to be around 5 dB and higher. High RoT values can cause significant performance degradation. For example, in <figref idrefs="DRAWINGS">FIG. 5B</figref> for the two neighboring cells formed by femto nodes <b>510</b>A and <b>510</b>B, high RoT caused by access terminal <b>520</b>D at femto node <b>510</b>A results in performance degradation for associated access terminal <b>520</b>C. One specific interfering scenario occurs when neighbor access terminal <b>520</b>D has bursty uplink UL traffic and exhibits overly high power levels (e.g., in close proximity) at femto node <b>510</b>A. Accordingly, during high rate data uplink UL bursts from access terminal <b>520</b>D, the RoT at femto node <b>510</b>A goes above 20 dB. Furthermore, the uplink UL power control mechanism in CDMA systems (e.g., CDMA2000, WCDMA, 1×EV-DO) is design to combat this type of interference scenarios. However due to excessive variation in RoT, the mechanism may take some time for femto node <b>510</b>A to power control associated access terminal <b>520</b>C to overcome the interference caused by non-associated access terminal <b>520</b>D. Meanwhile the signal-to-interference ratio (SIR) of associated access terminal <b>520</b>C falls below required levels resulting in consecutive packet errors on the uplink UL from associated access terminal <b>520</b>C to home femto node <b>510</b>A.
p-0162To minimize the sudden drop in SIR in the described scenario, one alternative could be to increase the power control step size on the uplink UL as conveyed from home femto node <b>510</b>A to associated access terminal <b>520</b>C. However, there are usually upper limits on the power control step size imposed by the communication standards since other system degradations occur when a system operates at very high power control step size. Thus it is desirable to control the RoT level at the femto node <b>510</b>.
p-0163In order to prevent an abrupt jump in RoT due to sudden increase in interference created by non-associated access terminals (e.g., interference created by non-associated access terminal <b>520</b>D at femto node <b>510</b>A), the noise figure NF can be increased or the received signal can be attenuated by adding some path loss (PL) component on the uplink UL. However, such an operation is performed at the femto node experiencing high levels of interference. For example, in the scenario shown in <figref idrefs="DRAWINGS">FIG. 5B</figref>, if both femto node <b>510</b>A and femto node <b>510</b>B increase the noise figure NF or attenuation by the same amount, the result is larger uplink UL transmit power levels for both access terminals <b>520</b>C and access terminal <b>520</b>D. As a result, the high RoT problem occurring at femto node <b>510</b>A is not remedied.
p-0164According to an exemplary embodiment, the femto node exhibiting high RoT, femto node <b>510</b>A in the present scenario, increases its noise figure NF or attenuation level while femto nodes not exhibiting high RoT, femto node <b>510</b>B in the present scenario, keep their noise figures NFs constant as long as they are not experiencing high levels of out-of-cell interference. Thus, a method is provided to adjust the noise figure NF or attenuation when there is high level of out-of-cell interference at a particular femto node. According to an exemplary embodiment for managing interference in a wireless communication system, RoT at a given time slot n can be expressed as:
p-0165<maths id="MATH-US-00004" num="00004"><math overflow="scroll"><mrow><mrow><mi>RoT</mi><mo></mo><mrow><mo>(</mo><mi>n</mi><mo>)</mo></mrow></mrow><mo>=</mo><mrow><mrow><mo>[</mo><mrow><mrow><mi>Ioc</mi><mo></mo><mrow><mo>(</mo><mi>n</mi><mo>)</mo></mrow></mrow><mo>+</mo><mrow><mi>Ior</mi><mo></mo><mrow><mo>(</mo><mi>n</mi><mo>)</mo></mrow></mrow><mo>+</mo><mrow><mi>No</mi><mo></mo><mrow><mo>(</mo><mi>n</mi><mo>)</mo></mrow></mrow></mrow><mo>]</mo></mrow><mo>/</mo><mrow><mi>No</mi><mo></mo><mrow><mo>(</mo><mi>n</mi><mo>)</mo></mrow></mrow></mrow></mrow></math></maths><maths id="MATH-US-00004-2" num="00004.2"><math overflow="scroll"><mi>and</mi></math></maths><maths id="MATH-US-00004-3" num="00004.3"><math overflow="scroll"><mrow><mrow><mi>Ior</mi><mo></mo><mrow><mo>(</mo><mi>n</mi><mo>)</mo></mrow></mrow><mo>=</mo><mrow><munder><mo>∑</mo><mrow><mi>i</mi><mo>∈</mo><mi>InCell</mi></mrow></munder><mo></mo><mrow><msub><mi>Ec</mi><mi>i</mi></msub><mo></mo><mrow><mo>(</mo><mi>n</mi><mo>)</mo></mrow></mrow></mrow></mrow></math></maths>
p-0166where Ec<sub>i </sub>is the total received energy per user i.
p-0167With initial reference to <figref idrefs="DRAWINGS">FIGS. 11A-11B</figref>, <figref idrefs="DRAWINGS">FIGS. 11A-11B</figref> describe a method for interference management in a wireless communication system using adaptive noise figure and path loss adjustment to adaptively adjust path loss for controlling RoT. It is noted that the adjustment factor can be applied either to uplink UL attenuation or the noise figure NF of the femto node.
p-0168As represented by query <b>1104</b>, the operations described herein may occur periodically, such as upon the occurrence of a subsequent time slot n. By way of example, at every slot n, the femto node <b>510</b> may perform the following method to provide interference management to a communication system. As represented by block <b>1104</b>, various signals are measured and levels are computed. Specifically as represented by block <b>1106</b>, a thermal noise figure: No(n) is measured at the femto node <b>510</b>. The thermal noise figure No(n) is the variance of the thermal noise including the femto node noise figure (NF).
p-0169As represented by block <b>1108</b>, a total received signal strength Io(n) is measured. The total received signal strength Io(n) is the total received power received at the femto node from all wireless devices for whom femto node is in their active set and from all wireless devices for whom femto node is not in their active set. As represented by block <b>1112</b>, the in-cell (associated access terminal) interference level Ior, which is the total received power received at the femto node from all wireless devices for whom femto node is in their active set, is computed. The computed in-cell interference level can be expressed as:
p-0170<maths id="MATH-US-00005" num="00005"><math overflow="scroll"><mrow><mrow><mi>Ior</mi><mo></mo><mrow><mo>(</mo><mi>n</mi><mo>)</mo></mrow></mrow><mo>=</mo><mrow><munder><mo>∑</mo><mrow><mi>i</mi><mo>∈</mo><mi>InCell</mi></mrow></munder><mo></mo><mrow><msub><mi>Ec</mi><mi>i</mi></msub><mo></mo><mrow><mo>(</mo><mi>n</mi><mo>)</mo></mrow></mrow></mrow></mrow></math></maths>
p-0171As represented by block <b>1110</b>, a received pilot chip energy Ecp(n) to interference and noise Nt(n) ratio is measured from all wireless devices for whom the femto node is in their active set.
p-0172As represented by block <b>1114</b>, the out-of-cell (non-associated access terminal) interference level Ioc, which is the total received power received at the femto node from all wireless devices for whom femto node is not in their active set, is computed. The computed out-of-cell interference level can be expressed as:
p-0173<br /><i>Ioc</i>(<i>n</i>)=<i>Io</i>(<i>n</i>)−<i>Ior</i>(<i>n</i>)−<i>No</i>(<i>n</i>)
p-0174As represented by block <b>1116</b> the received out-of-cell interference level to the thermal noise figure No(n) ratio and maximum filtered received pilot chip energy Ecp(n) to interference plus noise Nt(n) ratio among in-cell access terminals are computed. As represented by block <b>1118</b>, the access terminal signal-to-noise ratio measured as the received pilot chip energy Ecp(n) to interference and noise Nt(n) ratio for all in-cell access terminals are filtered, by way of example, according to infinite impulse response (IIR) filtering in the dB domain. The maximum filtered value among access terminals for whom the femto node is in their active set can be expressed as:
p-0175<maths id="MATH-US-00006" num="00006"><math overflow="scroll"><mrow><mrow><mi>max</mi><mo></mo><mover><mrow><mo>(</mo><mfrac><mrow><mi>Ecp</mi><mo></mo><mrow><mo>(</mo><mi>n</mi><mo>)</mo></mrow></mrow><mrow><mi>Nt</mi><mo></mo><mrow><mo>(</mo><mi>n</mi><mo>)</mo></mrow></mrow></mfrac><mo>)</mo></mrow><mi>_</mi></mover></mrow><mo>=</mo><mrow><munder><mi>max</mi><mrow><mi>i</mi><mo>∈</mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mrow><mi>in</mi><mo>-</mo><mrow><mi>cell</mi><mo></mo><mstyle><mspace width="0.8em" height="0.8ex" /></mstyle><mo></mo><mi>access</mi><mo></mo><mstyle><mspace width="0.8em" height="0.8ex" /></mstyle><mo></mo><mi>terminals</mi></mrow></mrow></mrow></munder><mo></mo><mrow><mo>[</mo><mrow><mi>filter</mi><mo></mo><mrow><mo>(</mo><mfrac><mrow><msub><mi>Ecp</mi><mi>i</mi></msub><mo></mo><mrow><mo>(</mo><mi>n</mi><mo>)</mo></mrow></mrow><mrow><msub><mi>Nt</mi><mi>i</mi></msub><mo></mo><mrow><mo>(</mo><mi>n</mi><mo>)</mo></mrow></mrow></mfrac><mo>)</mo></mrow></mrow><mo>]</mo></mrow></mrow></mrow></math></maths>
p-0176As represented by block <b>1120</b>, the signal-to-noise ratio of the out-of-cell received interference level Ioc and the thermal noise figure No(n) are computed. The signal-to-noise ratio is also further filtered, by way of example, according to finite impulse response (FIR) filtering in the dB domain. The computed out-of-cell (non-associated access terminal) signal-to-noise ratio can be expressed as:
p-0177<maths id="MATH-US-00007" num="00007"><math overflow="scroll"><mrow><mover><mrow><mo>(</mo><mfrac><mrow><mi>Ion</mi><mo></mo><mrow><mo>(</mo><mi>n</mi><mo>)</mo></mrow></mrow><mrow><mi>No</mi><mo></mo><mrow><mo>(</mo><mi>n</mi><mo>)</mo></mrow></mrow></mfrac><mo>)</mo></mrow><mi>_</mi></mover><mo>=</mo><mrow><mi>filter</mi><mo>(</mo><mfrac><mrow><mi>Ioc</mi><mo></mo><mrow><mo>(</mo><mi>n</mi><mo>)</mo></mrow></mrow><mrow><mi>No</mi><mo></mo><mrow><mo>(</mo><mi>n</mi><mo>)</mo></mrow></mrow></mfrac><mo>)</mo></mrow></mrow></math></maths>
p-0178As represented by block <b>1122</b>, the excessive received out-of-cell interference beyond the allowed (target) amount with which the communication system can reliably operate and the maximum excessive received pilot chip energy to interference and noise ratio among in-cell access terminals are determined. As represented by block <b>1124</b>, the excess amount for received pilot chip energy to interference and noise ratio can be expressed as:
p-0179<maths id="MATH-US-00008" num="00008"><math overflow="scroll"><mrow><mi>EcpNt_excess</mi><mo>=</mo><mrow><mrow><mi>max</mi><mo></mo><mover><mrow><mo>(</mo><mfrac><mrow><mi>Ecp</mi><mo></mo><mrow><mo>(</mo><mi>n</mi><mo>)</mo></mrow></mrow><mrow><mi>Nt</mi><mo></mo><mrow><mo>(</mo><mi>n</mi><mo>)</mo></mrow></mrow></mfrac><mo>)</mo></mrow><mi>_</mi></mover></mrow><mo>-</mo><mi>EcpNt_target</mi></mrow></mrow></math></maths>
p-0180with the above allowed threshold EcpNt_target having the units of dB.
p-0181As represented by block <b>1126</b>, the excess amount of the out-of-cell received interference level Ioc_excess can be expressed as:
p-0182<maths id="MATH-US-00009" num="00009"><math overflow="scroll"><mrow><mi>Ioc_excess</mi><mo>=</mo><mrow><mover><mrow><mo>(</mo><mfrac><mrow><mi>Ioc</mi><mo></mo><mrow><mo>(</mo><mi>n</mi><mo>)</mo></mrow></mrow><mrow><mi>No</mi><mo></mo><mrow><mo>(</mo><mi>n</mi><mo>)</mo></mrow></mrow></mfrac><mo>)</mo></mrow><mi>_</mi></mover><mo>-</mo><mi>Ioc_target</mi></mrow></mrow></math></maths>
p-0183with the above allowed threshold Ioc_target having the units of dB.
p-0184As represented in block <b>1128</b>, an amount of additional path loss (PL_adjust) that needs to be applied is computed. As represented in block <b>1130</b>, the candidate path loss adjustments are determined. The candidate adjustments can be expressed as:
p-0185<maths id="MATH-US-00010" num="00010"><math overflow="scroll"><mrow><msub><mi>PL_cand</mi><mn>1</mn></msub><mo>=</mo><mi>Ior_excess</mi></mrow></math></maths><maths id="MATH-US-00010-2" num="00010.2"><math overflow="scroll"><mrow><msub><mi>PL_cand</mi><mn>2</mn></msub><mo>=</mo><mrow><mo>{</mo><mrow><mrow><mtable><mtr><mtd><mrow><mn>0</mn><mo>,</mo></mrow></mtd><mtd><mrow><mn>0</mn><mo>≥</mo><mi>EcpNt_excess</mi></mrow></mtd></mtr><mtr><mtd><mrow><mrow><mi>EcpNtbased_PL</mi><mo></mo><mi>_step</mi></mrow><mo>,</mo></mrow></mtd><mtd><mrow><mn>0</mn><mo><</mo><mi>EcpNt_excess</mi></mrow></mtd></mtr></mtable><mo></mo><mstyle><mtext /></mstyle><mo></mo><msub><mi>PL_cand</mi><mn>3</mn></msub></mrow><mo>=</mo><mrow><mrow><mrow><mi>PL_cand</mi><mo></mo><mrow><mo>(</mo><mrow><mi>n</mi><mo>-</mo><mn>1</mn></mrow><mo>)</mo></mrow></mrow><mo>-</mo><mrow><mi>PL_step</mi><mo></mo><mi>_down</mi><mo></mo><mstyle><mtext /></mstyle><mo></mo><mi>PL_cand</mi></mrow></mrow><mo>=</mo><mrow><mi>max</mi><mo></mo><mrow><mo>(</mo><mrow><msub><mi>PL_cand</mi><mn>1</mn></msub><mo>,</mo><msub><mi>PL_cand</mi><mn>2</mn></msub><mo>,</mo><msub><mi>PL_cand</mi><mn>3</mn></msub></mrow><mo>)</mo></mrow></mrow></mrow></mrow></mrow></mrow></math></maths>
p-0186Regarding determining the candidate adjustment values, the candidate values may be based upon various characteristics or rules. By way of example, various points can be expressed as: <ul><li id="ul0010-0001" num="0000"><ul><li id="ul0011-0001" num="0171">(1) PL_cand<sub>1 </sub>and PL_cand<sub>2 </sub>are designed to quickly adjust the PL based on high Ecp/Nt or Ioc values exceeding a high threshold.</li><li id="ul0011-0002" num="0172">(2) In case both Ecp/Nt and Ioc are below allowed limits, PL_cand<sub>3 </sub>is designed to slowly reduce (decay) PL such that it won't be unnecessarily high.</li><li id="ul0011-0003" num="0173">(3) If there is only one active user in the cell there maybe no reason to directly limit Ioc since RoT control mechanisms already can control the RoT level. So in the case when there is only one active user in the system, Ioc_target can be set to a very large value.</li></ul></li></ul>
p-0187As represented in block <b>1132</b>, the appropriate path loss (PL_adjust) can be applied according to the upper and lower path loss PL adjustment limitations expressed as:
p-0188<br />If (<i>PL</i>_cand>PL_adjust_max)
p-0189<br /><i>PL</i>_adjust(<i>n</i>)=<i>PL</i>_adjust_max
p-0190<br />elseif (<i>PL</i>_cand>0)
p-0191<br /><i>PL</i>_adjust(<i>n</i>)=<i>PL</i>_cand
p-0192<br />elseif (<i>PL</i>_cand≦0)
p-0193<br /><i>PL</i>_adjust(<i>n</i>)=0
p-0194As represented in block <b>1134</b>, the uplink UL attenuation (or noise figure) is increased by PL_adjust(n). It is noted that in an actual implementation, hardware limitations may require quantization of PL_adjust(n) to the closest possible setting.
p-0195Referring now to <figref idrefs="DRAWINGS">FIG. 12</figref> and with further reference to <figref idrefs="DRAWINGS">FIGS. 5A-5B</figref>, operations relating to the use of subframe time reuse to address jamming and negative geometries will be described in more detail. The present exemplary embodiment uses methods and apparatus to prevent jamming and address jamming and negative geometries using subframe time reuse.
p-0196In one exemplary embodiment, if an air interface permits time division multiplexing, transmissions can be scheduled in such a manner as to eliminate time periods with negative geometries. Thus, femto node <b>510</b>B may communicate with associated access terminal <b>520</b>D during a period that femto node <b>510</b>A is silent. Similarly, associated access terminal <b>520</b>C may communicate with femto node <b>510</b>A during a period where non-associated access terminal <b>520</b>D is scheduled by femto node <b>510</b>A to be silent. Such methods of synchronization and scheduling approaches find application to systems that permit time division scheduling, such as 1×EVDO. By way of example, since the 1×EVDO control channels are time multiplexed, neighbor femto nodes <b>510</b> can be organized to use time re-use of these control channels.
p-0197However, as discussed next, this does not work with air interface technologies that do not permit operation with scheduling and time division multiplexing, for example, technologies that use CDM control channels, including, for example, 1×RTT, WCDMA and HSPA. Design details for sub-frame time reuse are described in detail in embodiments below.
p-0198In one exemplary embodiment, sub-frame time reuse is applicable to technologies where hybrid time reuse cannot be applied. In many cellular technologies such as cdma2000 and WCDMA, the base station transmits a continuous pilot and other CDM control channels (e.g., synch, paging and broadcast, etc.) which the access terminals use for a variety of purposes, including initial scanning and acquisition, idle mode tracking and channel estimation. This continuous transmission of pilot and overhead channels from femto nodes may result in the above described downlink jamming, even when there is no active traffic at the jammer.
p-0199In one exemplary embodiment, the first step is to address the outage situations when the desired femto node <b>510</b> pilot and overhead channels (e.g., synch and paging) cannot be received at the access terminal <b>520</b>. By way of example, a cdma2000 frame is divided into sixteen power control groups (PCGs). To permit acquisition of the pilot signal, a fraction of the pilot and overhead channel transmission is gated off.
p-0200With reference to <figref idrefs="DRAWINGS">FIG. 5B</figref>, femto node <b>510</b>A, transmitting to associated access terminals <b>520</b>A-C, transmits such gated frames (i.e., during gated off periods no FL traffic is transmitted). At non-associated access terminal <b>520</b>D, the carrier-to-interference ratio, C/I, for transmissions from femto node <b>510</b>B improves dramatically during the period that femto node <b>510</b>A is gated off, permitting acquisition of the pilot and synch channels from femto node <b>510</b>B at access terminal <b>520</b>D, in spite of the highly negative geometry at access terminal <b>520</b>D.
p-0201In one exemplary embodiment, these gated on-off periods are scheduled to be non-overlapping. Thus, femto node <b>510</b>A and femto node <b>510</b>B can use non-overlapping sub-frames (or power-control groups). In one exemplary embodiment, by gating off (i.e., not transmitting any FL traffic) a fraction ½, ⅔ or ¾ of the sub-frames, for example, a time division reuse pattern of 2, 3 or 4 may be created. If the pilot and overhead channels have sufficient redundancy, for pilot acquisition as well as decoding of the overhead channels, this would have an impact of 3-6 dB, for example, on the link budget of the pilot and overhead channels. However, this can be easily compensated by increasing the transmit power of the femto node <b>510</b>, since in the femto node <b>510</b> deployment, the arrangements are not limited by transmit power.
p-0202In addition to the pilot and overhead channels, the same gating method may also be applied to the voice or data channel transmissions. In one exemplary embodiment, the femto node <b>510</b> gates a fraction of each frame transmission off. If, for example, the fraction (e.g., ½) that is turned off is lesser than the channel coding rate used for that transmission, for example, in cdma2000 forward link voice packet transmissions, a particular standard format (RC3) uses a rate ¼ convolutional code, the access terminal <b>520</b> will be able to decode the packet, even though half of the packet transmission was gated off. To avoid the necessity of knowing these geometries and scheduling these non-overlapping gated off times, the following method is disclosed to prevent jamming and address jamming and negative geometries using subframe time reuse.
p-0203With initial reference to <figref idrefs="DRAWINGS">FIG. 12</figref>, <figref idrefs="DRAWINGS">FIG. 12</figref> describes an exemplary embodiment for interference management in a wireless communication system using subframe time reuse. As represented by block <b>1202</b>, gating sequences (or patterns) are identified with each gating sequence gating-off, for example, either eleven of sixteen power control groups (PCGs) to obtain a reuse of 5/16, or eight of sixteen PCGs to obtain a reuse of 2.
p-0204The gating sequence may be chosen in such a way as to minimize the cross-correlation between pairs of gating sequences from potentially interfering femto nodes <b>510</b>. As represented by block <b>1204</b>, each femto node <b>510</b> selects one of the gating sequences. Although the femto node <b>510</b> may attempt to choose a gating sequence that is non-overlapping with neighbor femto nodes, general selection does not necessarily result in a non-overlapping arrangement. However, the exemplary embodiment provides a mechanism such that a non-overlapping gating sequence can be identified and selected.
p-0205As represented by block <b>1206</b>, an access terminal <b>520</b> establishes an active connection with a femto node <b>510</b>. In response to establishing the connection, the access terminal <b>520</b> provides a “fast” per-subframe downlink (forward link) power control feedback allowing the femto node <b>5101</b> to select a desired non-overlapping gating sequence.
p-0206Specifically and as represented in block <b>1208</b>, femto node <b>510</b>B transmits a series of frames on, for example, a data/voice channel to the access terminal <b>520</b>D with all power control groups (PCGs) gated on. As represented by block <b>1210</b>, since a potentially interfering neighbor femto node <b>530</b>A is already engaged in communication with access terminals <b>520</b>A-C using sub-frame gating techniques, access terminal <b>520</b>D will observe interference on a subset of the subframes in response to gated transmissions by interfering neighbor femto node <b>510</b>A. Furthermore, access terminal <b>520</b>D will also observe another subset of subframes where no interference from neighbor femto node <b>520</b>A is observed when neighbor femto node <b>510</b>A is gated off during that subset of subframes.
p-0207During the subframes in which femto node <b>510</b>A is gated on, the access terminal <b>520</b>D will observe, for example, low Eb/No. As represented by block <b>1212</b>, the downlink (forward link) power control feedback from access terminal <b>520</b>D will indicate that femto node <b>510</b>B should increase the transmit power for specific subframes. Similarly, during the subframes that femto node <b>510</b>A is gated off, access terminal <b>520</b>D will observe high Eb/No and the downlink (forward link) power control feedback from access terminal <b>520</b>D will indicate that femto node <b>510</b>B should decrease the transmit power for specific subframes.
p-0208As represented by block <b>1214</b>, the sub-frame downlink (forward link) power control feedback provided by access terminal <b>520</b>D to femto node <b>510</b>B indicates which sub-frames at transmitted by interfering neighbor femto node <b>510</b>A are gated on and which are gated off. Accordingly, such an indication allows femto node <b>510</b>B to select a gating sequence (pattern) that is non-overlapping (complementary) with the gating sequence (pattern) chosen and in use by interfering neighbor femto node <b>510</b>A. The exemplary embodiment finds application for the gating sequence (pattern) chosen by interfering neighboring femto node <b>510</b>A.
p-0209Depending on the implementation technology, other considerations may further determine the types of gating sequences (patterns) best suited for this sub-frame gating technique. Furthermore, since legacy access terminals are unaware of the gating being done on the downlink (forward link), other considerations may be applied to include choosing gating sequences (patterns) that intersperse shortened “off” periods between shortened “on” periods. Such a consideration may reduce impact on downlink (forward link) channel estimation and channel quality feedback estimation methods in use by the legacy access terminal. Thus, for example, in a case when eight sub-frames out of sixteen are gated off, there may be beneficial reasons for selecting alternating sub-frames to be gated off and gated on.
p-0210In another exemplary embodiment, gating sequence selection may apply different considerations for deployments where neighbor femto nodes <b>510</b> are not synchronized. Such considerations may exist, for example, when WCDMA femto nodes <b>510</b> are not synchronized. In one exemplary embodiment of non-synchronized femto nodes <b>510</b>, instead of alternate on-off gated subframes, it may be beneficial to have all or many of the gated-off subframes be contiguous, as well as all or many of the gated-on subframes. For example, in the case of a WCDMA system with fifteen subframes over 10 ms, or thirty subframes over 20 ms, a beneficial method may be for each femto node <b>510</b> to gate off nine contiguous of the fifteen subframes and gate on six contiguous subframes. Alternately, using a 20 ms frame, the femto node <b>510</b> may gate off sixteen contiguous subframes and gate on fourteen contiguous subframes out of thirty subframes.
p-0211In alternate exemplary embodiments, other methods to address this situation and improve downlink C/I involve femto nodes <b>510</b> configured to gate-off pilot and overhead channel transmissions when there are no access terminals associated, and to turn on pilot and overhead channels periodically and/or at very low power only at times when associated access terminals <b>520</b> are expected to be scanning for the femto node <b>510</b>.
p-0212Referring now to <figref idrefs="DRAWINGS">FIGS. 13-14</figref> and with further reference to <figref idrefs="DRAWINGS">FIGS. 5A-5B</figref>, operations relating to the use of hybrid time reuse to address jamming and negative geometries will be described in more detail. The present exemplary embodiment uses methods and apparatus to prevent jamming and address jamming and negative geometries using hybrid time reuse techniques.
p-0213In an exemplary embodiment, if an air interface permits time division multiplexing (such as 1×EV-DO), then transmissions may be scheduled in such a manner as to eliminate time periods with negative geometries. Thus, femto node <b>510</b>B can communicate with associated access terminal <b>520</b>D during a period when femto node <b>510</b>A is not transmitting. Similarly, associated access terminal <b>520</b>C may communicate with femto node <b>510</b>A during a period where access terminal <b>520</b>D is scheduled by femto node <b>510</b>B to not transmit.
p-0214In an exemplary embodiment of a hybrid time reuse method, a downlink DL transmission is divided into three separate groups in time: <ul><li id="ul0012-0001" num="0000"><ul><li id="ul0013-0001" num="0196">1. Synchronous Control Channel (SCC) transmission period</li><li id="ul0013-0002" num="0197">2. Limited HARQ Interlace Tx. Period</li><li id="ul0013-0003" num="0198">3. Unlimited HARQ Interlace Tx. Period</li></ul></li></ul>
p-0215<figref idrefs="DRAWINGS">FIG. 13</figref> illustrates an exemplary downlink DL timeline including three different time periods during each synchronous control channel (SCC) cycle period of 256 time slots. In one exemplary embodiment based on time sharing of the resources during “unlimited HARQ interlace,” there are three different femto channels defined. As described in more detail later, it is desired that neighboring femto nodes <b>510</b> pick different femto channels so that they do not experience interference from other neighbor femto nodes <b>510</b> (i.e., each femto node selects a primary femto channel different than the neighbor femto node <b>510</b>). If there is no interference from a neighbor femto node, multiple femto channels (in addition to the primary femto channel) can be used by one femto node <b>510</b>. Details of one exemplary embodiment of a hybrid time reuse operation is described below.
p-0216With initial reference to <figref idrefs="DRAWINGS">FIG. 14</figref>, <figref idrefs="DRAWINGS">FIG. 14</figref> describes a method for interference management in a wireless communication system using hybrid time reuse, in accordance with an exemplary embodiment. As represented by block <b>1402</b>, at the initial power up or other synchronization of a femto node <b>510</b>, the femto node <b>510</b> performs time synchronization with the macro cell network (e.g., macro cell access node <b>560</b>). As represented by block <b>1404</b>, during time synchronization with the macro cell access node <b>560</b>, the femto node <b>510</b> measures secondary synchronization channel (SCC) offsets (MSCCO) used by the macro cell access node <b>560</b> and neighboring femto nodes <b>510</b>. Based on the measurement, the femto node <b>510</b> identifies a preferred HARQ interlace with the least interference, as represented by block <b>1406</b>. A preferred slot offset (PSO) is defined from the identified preferred HARQ interlace.
p-0217As represented in block <b>1408</b>, a primary femto channel is selected. By way of example, on exemplary selection process may follow the following algorithm:
p-0218<br />If mod(<i>PSO</i>-<i>MSCCO,</i>4)=1 then Femto Chn. 1 is picked as primary Femto Channel
p-0219<br />If mod(<i>PSO</i>-<i>MSCCO,</i>4)=2 then Femto Chn. 2 is picked as primary Femto Channel
p-0220<br />If mod(<i>PSO</i>-<i>MSCCO,</i>4)=3 then Femto Chn. 3 is picked as primary Femto Channel
p-0221where Chn<b>1</b>, Chn<b>2</b> and Chn<b>3</b> are described in <figref idrefs="DRAWINGS">FIG. 13</figref>.
p-0222Once femto channels are determined, femto nodes <b>510</b> may transmit traffic in the downlink (forward link). Transmissions by femto nodes <b>510</b> are timed to reduce interference with macro cell transmissions and other femto node transmissions. A femto node transmission protocol for the various macro cell transmission periods, SCC transmission period, limited HARQ interlace transmission period, and unlimited HARQ interlace transmission period, are described below.
p-0223As represented in block <b>1410</b> and with reference to <figref idrefs="DRAWINGS">FIG. 13</figref>, an SCC transmission period <b>1302</b> is defined at the beginning of each SCC cycle <b>1304</b> (e.g., 256 slots) to allow transmission of an SCC offset (e.g., first 32 slots of every SCC cycle). In one exemplary embodiment, two sub-periods <b>1306</b>, <b>1308</b> are defined based on HARQ interlace: preferred slot offset and non-preferred slot offset.
p-0224On HARQ interlace with the preferred slot offset (PSO), femto node <b>510</b> transmits SCC information. This allows reliable transmission of control channel information and enables associated access terminals <b>520</b> to hand-in and hand-out from femto node <b>510</b>. During HARQ interlaces on non preferred slot offsets, femto nodes <b>510</b> do not transmit any downlink (forward link) traffic (DTX FL transmission) so that minimum interference is caused to neighbor macro cells and neighbor femto node SCC transmission. On these slot offsets, a fractional of downlink DL power is used for Pilot and MAC channels so that these channels can operate successfully.
p-0225As represented in block <b>1412</b> and with reference to <figref idrefs="DRAWINGS">FIG. 13</figref>, during a limited HARQ interlace transmission period, the femto node <b>510</b> is allowed to transmit downlink (forward link) traffic on the HARQ interlace of PSO and delay sensitive traffic is given absolute priority over best effort traffic. With reference to <figref idrefs="DRAWINGS">FIG. 13</figref>, limited HARQ interlace transmission period gives a transmission opportunity for each femto node so that delay sensitive traffic (such as VoIP etc.) does not suffer too excessive delay. In one example, during limited HARQ interlace transmission period, if requested DRC is null, then single user packet type of 38.4 kbps may be used. If DRC is null or erased, then compatible packet types such as single user packet (SUP) 38.4 kbps or multi user packet (MUP) of 256/512/1024 bits may be utilized (similar to DRC erasure mapping).
p-0226In one exemplary embodiment, downlink (forward link) traffic may also be transmitted on HARQ interlace of MSCCO. In one embodiment, neighboring femto nodes <b>510</b> may use this interlace as well (i.e., no protection against interference). During HARQ interlaces of other slot offsets, femto nodes do not transmit any downlink (forward link) traffic (time re-use) however a fraction of downlink (forward link) power can be allocated to pilot and MAC channels for successful operation of these channels.
p-0227As represented in block <b>1414</b> and with reference to <figref idrefs="DRAWINGS">FIG. 13</figref>, during an unlimited HARQ interlace transmission period, the femto node <b>510</b> is allowed to transmit downlink (forward link) traffic on all of the four HARQ interlaces. At the beginning of the period, downlink (forward link) transmit power can be ramped up slowly to let the access terminal rate predictor to ramp up. In one exemplary embodiment, to further increase the ramp-up of DRC values, DRC length of 1 slot should be used. Due to conservative predictor behavior, if null DRC is requested by the mobile at the beginning of unlimited HARQ interlace transmission period, femto node <b>510</b> can transmit compatible packet types (multi use packet or 38.4 kbps single user packet). Also, femto node downlink (forward link) scheduler can keep track of previously requested DRC values and maintain DRC values from last transmission periods and HARQ early termination statistics to decide on what data rates can be decoded by access terminal <b>520</b>.
p-0228The teachings herein may be incorporated into a node (e.g., a device) employing various components for communicating with at least one other node. <figref idrefs="DRAWINGS">FIG. 15</figref> depicts several sample components that may be employed to facilitate communication between nodes. Specifically, <figref idrefs="DRAWINGS">FIG. 15</figref> illustrates a wireless device <b>1510</b> (e.g., an access point) and a wireless device <b>1550</b> (e.g., an access terminal) of a MIMO system <b>1500</b>. At the device <b>1510</b>, traffic data for a number of data streams is provided from a data source <b>1512</b> to a transmit (“TX”) data processor <b>1514</b>.
p-0229In some aspects, each data stream is transmitted over a respective transmit antenna. The TX data processor <b>1514</b> formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data.
p-0230The coded data for each data stream may be multiplexed with pilot data using OFDM techniques. The pilot data is typically a known data pattern that is processed in a known manner and may be used at the receiver system to estimate the channel response. The multiplexed pilot and coded data for each data stream is then modulated (i.e., symbol mapped) based on a particular modulation scheme (e.g., BPSK, QSPK, M-PSK, or M-QAM) selected for that data stream to provide modulation symbols. The data rate, coding, and modulation for each data stream may be determined by instructions performed by a processor <b>1530</b>. A data memory <b>1532</b> may store program code, data, and other information used by the processor <b>1530</b> or other components of the device <b>1510</b>.
p-0231The modulation symbols for all data streams are then provided to a TX MIMO processor <b>1520</b>, which may further process the modulation symbols (e.g., for OFDM). The TX MIMO processor <b>1520</b> then provides N<sub>T </sub>modulation symbol streams to N<sub>T </sub>transceivers (“XCVR”) <b>1522</b>A through <b>1522</b>T. In some aspects, the TX MIMO processor <b>1520</b> applies beam-forming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.
p-0232Each transceiver <b>1522</b> receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel. N<sub>T </sub>modulated signals from transceivers <b>1522</b>A through <b>1522</b>T are then transmitted from N<sub>T </sub>antennas <b>1524</b>A through <b>1524</b>T, respectively.
p-0233At the device <b>1550</b>, the transmitted modulated signals are received by N<sub>R </sub>antennas <b>1552</b>A through <b>1552</b>R and the received signal from each antenna <b>1552</b> is provided to a respective transceiver (“XCVR”) <b>1554</b>A through <b>1554</b>R. Each transceiver <b>1554</b> conditions (e.g., filters, amplifies, and downconverts) a respective received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding “received” symbol stream.
p-0234A receive (“RX”) data processor <b>1560</b> then receives and processes the N<sub>R </sub>received symbol streams from N<sub>R </sub>transceivers <b>1554</b> based on a particular receiver processing technique to provide N<sub>T </sub>“detected” symbol streams. The RX data processor <b>1560</b> then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for the data stream. The processing by the RX data processor <b>1560</b> is complementary to that performed by the TX MIMO processor <b>1520</b> and the TX data processor <b>1514</b> at the device <b>1510</b>.
p-0235A processor <b>1570</b> periodically determines which pre-coding matrix to use (discussed below). The processor <b>1570</b> formulates a reverse link message comprising a matrix index portion and a rank value portion. A data memory <b>1572</b> may store program code, data, and other information used by the processor <b>1570</b> or other components of the device <b>1550</b>.
p-0236The reverse link message may comprise various types of information regarding the communication link and/or the received data stream. The reverse link message is then processed by a TX data processor <b>1538</b>, which also receives traffic data for a number of data streams from a data source <b>1536</b>, modulated by a modulator <b>1580</b>, conditioned by the transceivers <b>1554</b>A through <b>1554</b>R, and transmitted back to the device <b>1510</b>.
p-0237At the device <b>1510</b>, the modulated signals from the device <b>1550</b> are received by the antennas <b>1524</b>, conditioned by the transceivers <b>1522</b>, demodulated by a demodulator (“DEMOD”) <b>1540</b>, and processed by a RX data processor <b>1542</b> to extract the reverse link message transmitted by the device <b>1550</b>. The processor <b>1530</b> then determines which pre-coding matrix to use for determining the beam-forming weights then processes the extracted message.
p-0238<figref idrefs="DRAWINGS">FIG. 15</figref> also illustrates that the communication components may include one or more components that perform interference control operations as taught herein. For example, an interference (“INTER.”) control component <b>1590</b> may cooperate with the processor <b>1530</b> and/or other components of the device <b>1510</b> to send/receive signals to/from another device (e.g., device <b>1550</b>) as taught herein. Similarly, an interference control component <b>1592</b> may cooperate with the processor <b>1570</b> and/or other components of the device <b>1550</b> to send/receive signals to/from another device (e.g., device <b>1510</b>). It should be appreciated that for each device <b>1510</b> and <b>1550</b> the functionality of two or more of the described components may be provided by a single component. For example, a single processing component may provide the functionality of the interference control component <b>1590</b> and the processor <b>1530</b> and a single processing component may provide the functionality of the interference control component <b>1592</b> and the processor <b>1570</b>.
p-0239The teachings herein may be incorporated into various types of communication systems and/or system components. In some aspects, the teachings herein may be employed in a multiple-access system capable of supporting communication with multiple users by sharing the available system resources (e.g., by specifying one or more of bandwidth, transmit power, coding, interleaving, and so on). For example, the teachings herein may be applied to any one or combinations of the following technologies: Code Division Multiple Access (“CDMA”) systems, Multiple-Carrier CDMA (“MCCDMA”), Wideband CDMA (“W-CDMA”), High-Speed Packet Access (“HSPA,” “HSPA+”) systems, Time Division Multiple Access (“TDMA”) systems, Frequency Division Multiple Access (“FDMA”) systems, Single-Carrier FDMA (“SC-FDMA”) systems, Orthogonal Frequency Division Multiple Access (“OFDMA”) systems, or other multiple access techniques. A wireless communication system employing the teachings herein may be designed to implement one or more standards, such as IS-95, cdma2000, IS-856, W-CDMA, TDSCDMA, and other standards. A CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (“UTRA)”, cdma2000, or some other technology. UTRA includes W-CDMA and Low Chip Rate (“LCR”). The cdma2000 technology covers IS-2000, IS-95 and IS-856 standards. A TDMA network may implement a radio technology such as Global System for Mobile Communications (“GSM”). An OFDMA network may implement a radio technology such as Evolved UTRA (“E-UTRA”), IEEE 802.11, IEEE 802.16, IEEE 802.20, Flash-OFDM®, etc. UTRA, E-UTRA, and GSM are part of Universal Mobile Telecommunication System (“UMTS”). The teachings herein may be implemented in a 3GPP Long Term Evolution (“LTE”) system, an Ultra-Mobile Broadband (“UMB”) system, and other types of systems. LTE is a release of UMTS that uses E-UTRA. Although certain aspects of the disclosure may be described using 3GPP terminology, it is to be understood that the teachings herein may be applied to 3GPP (Re199, Re15, Re16, Re17) technology, as well as 3GPP2 (1×RTT, 1×EV-DO Re1O, RevA, RevB) technology and other technologies.
p-0240The teachings herein may be incorporated into (e.g., implemented within or performed by) a variety of apparatuses (e.g., nodes). In some aspects, a node (e.g., a wireless node) implemented in accordance with the teachings herein may comprise an access point or an access terminal.
p-0241For example, an access terminal may comprise, be implemented as, or known as user equipment, a subscriber station, a subscriber unit, a mobile station, a mobile, a mobile node, a remote station, a remote terminal, a user terminal, a user agent, a user device, or some other terminology. In some implementations an access terminal may comprise 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, or some other suitable processing device connected to a wireless modem. Accordingly, one or more aspects taught herein may be incorporated into a phone (e.g., a cellular phone or smart phone), a computer (e.g., a laptop), a portable communication device, a portable computing device (e.g., a personal data assistant), an entertainment device (e.g., a music device, a video device, or a satellite radio), a global positioning system device, or any other suitable device that is configured to communicate via a wireless medium.
p-0242An access point may comprise, be implemented as, or known as a NodeB, an eNodeB, a radio network controller (“RNC”), a base station (“BS”), a radio base station (“RBS”), a base station controller (“BSC”), a base transceiver station (“BTS”), a transceiver function (“TF”), a radio transceiver, a radio router, a basic service set (“BSS”), an extended service set (“ESS”), or some other similar terminology.
p-0243In some aspects a node (e.g., an access point) may comprise an access node for a communication system. Such an access node may provide, for example, connectivity for or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link to the network. Accordingly, an access node may enable another node (e.g., an access terminal) to access a network or some other functionality. In addition, it should be appreciated that one or both of the nodes may be portable or, in some cases, relatively non-portable.
p-0244Also, it should be appreciated that a wireless node may be capable of transmitting and/or receiving information in a non-wireless manner (e.g., via a wired connection). Thus, a receiver and a transmitter as discussed herein may include appropriate communication interface components (e.g., electrical or optical interface components) to communicate via a non-wireless medium.
p-0245A wireless node may communicate via one or more wireless communication links that are based on or otherwise support any suitable wireless communication technology. For example, in some aspects a wireless node may associate with a network. In some aspects the network may comprise a local area network or a wide area network. A wireless device may support or otherwise use one or more of a variety of wireless communication technologies, protocols, or standards such as those discussed herein (e.g., CDMA, TDMA, OFDM, OFDMA, WiMAX, Wi-Fi, and so on). Similarly, a wireless node may support or otherwise use one or more of a variety of corresponding modulation or multiplexing schemes. A wireless node may thus include appropriate components (e.g., air interfaces) to establish and communicate via one or more wireless communication links using the above or other wireless communication technologies. For example, a wireless node may comprise a wireless transceiver with associated transmitter and receiver components that may include various components (e.g., signal generators and signal processors) that facilitate communication over a wireless medium.
p-0246The components described herein may be implemented in a variety of ways. Referring to <figref idrefs="DRAWINGS">FIGS. 16-21</figref>, apparatuses <b>1600</b>, <b>1700</b>, <b>1800</b>, <b>1900</b>, <b>2000</b>, and <b>2100</b> are represented as a series of interrelated functional blocks. In some aspects the functionality of these blocks may be implemented as a processing system including one or more processor components. In some aspects the functionality of these blocks may be implemented using, for example, at least a portion of one or more integrated circuits (e.g., an ASIC). As discussed herein, an integrated circuit may include a processor, software, other related components, or some combination thereof. The functionality of these blocks also may be implemented in some other manner as taught herein.
p-0247The apparatuses <b>1600</b>, <b>1700</b>, <b>1800</b>, <b>1900</b>, <b>2000</b>, and <b>2100</b> may include one or more modules that may perform one or more of the functions described above with regard to various figures. In some aspects, one or more components of the interference controller <b>320</b> or the interference controller <b>322</b> may provide functionality relating to, for example, a interference receiving/direction means <b>1602</b>, interference comparing/determining/updating means <b>1606</b>, overhead channel power means <b>1702</b>, transmit waveform means <b>1802</b>, channel quality means <b>1806</b>, interference determining means <b>1902</b>, path loss means <b>1906</b>, gating sequence means <b>2002</b>, reuse pattern means <b>2102</b>, and synchronization/offset/timing means <b>2106</b>. In some aspects, the communication controller <b>326</b> or the communication controller <b>328</b> may provide functionality relating to, for example, transceiving (transmitting/receiving) means <b>1604</b>, <b>1704</b>, <b>1804</b>, <b>1904</b>, <b>2004</b>, and <b>2104</b>.
p-0248It should be understood that any reference to an element herein using a designation such as “first,” “second,” and so forth does not generally limit the quantity or order of those elements. Rather, these designations may be used herein as a convenient method of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements may be employed there or that the first element must precede the second element in some manner. Also, unless stated otherwise a set of elements may comprise one or more elements.
p-0249Those of skill in the art would understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
p-0250Those of skill would further appreciate that any of the various illustrative logical blocks, modules, processors, means, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two, which may be designed using source coding or some other technique), various forms of program or design code incorporating instructions (which may be referred to herein, for convenience, as “software” or a “software module”), or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
p-0251The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented within or performed by an integrated circuit (“IC”), an access terminal, or an access point. The IC may comprise a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute codes or instructions that reside within the IC, outside of the IC, or both. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
p-0252It is understood that any specific order or hierarchy of steps in any disclosed process is an example of a sample approach. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.
p-0253The functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media. In summary, it should be appreciated that a computer-readable medium may be implemented in any suitable computer-program product.
p-0254The previous description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects without departing from the scope of the disclosure. Thus, the present disclosure is not intended to be limited to the aspects shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Contents5
30 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17 Sheet 18 Sheet 19 Sheet 20 Sheet 21 Sheet 22 Sheet 23 Sheet 24 Sheet 25 Sheet 26 Sheet 27 Sheet 28 Sheet 29 Sheet 30
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2011149921A1 | Cited by | United States of America | Pre-grant |
| US2009137241A1 | Cited by | United States of America | Pre-grant |
| US2009286496A1 | Cited by | United States of America | Pre-grant |
| US2012106442A1 | Cited by | United States of America | Pre-grant |
| US8897274B2 | Cited by | United States of America | Search report |
| US8831621B2 | Cited by | United States of America | Applicant |
| US2009286545A1 | Cited by | United States of America | Pre-grant |
| US2009080499A1 | Cited by | United States of America | Pre-grant |
| US9648596B2 | Cited by | United States of America | Applicant |
| US2009135796A1 | Cited by | United States of America | Pre-grant |
| US8611911B2 | Cited by | United States of America | Search report |
| US8725083B2 | Cited by | United States of America | Applicant |
| US2009285113A1 | Cited by | United States of America | Pre-grant |
| US8391796B2 | Cited by | United States of America | Search report |
| US2010087149A1 | Cited by | United States of America | Pre-grant |
| US2014153425A1 | Cited by | United States of America | Pre-grant |
| US2009082026A1 | Cited by | United States of America | Pre-grant |
| US2012064904A1 | Cited by | United States of America | Pre-grant |
| US9647820B2 | Cited by | United States of America | Search report |
| US8169933B2 | Cited by | United States of America | Applicant |
| US2011310858A1 | Cited by | United States of America | Pre-grant |
| US2010087221A1 | Cited by | United States of America | Pre-grant |
| US8260207B2 | Cited by | United States of America | Search report |
| US8737317B2 | Cited by | United States of America | Search report |
| US2010118801A1 | Cited by | United States of America | Pre-grant |
| US8463190B2 | Cited by | United States of America | Search report |
| US8718696B2 | Cited by | United States of America | Applicant |
| US2010087148A1 | Cited by | United States of America | Pre-grant |
| US8711786B2 | Cited by | United States of America | Applicant |
| US10667186B2 | Cited by | United States of America | Applicant |
| US2009086861A1 | Cited by | United States of America | Pre-grant |
| US2010039948A1 | Cited by | United States of America | Pre-grant |
| US2009252099A1 | Cited by | United States of America | Pre-grant |
| US2010085884A1 | Cited by | United States of America | Pre-grant |
| US2009135754A1 | Cited by | United States of America | Pre-grant |
| US8873477B2 | Cited by | United States of America | Search report |
| US8412103B2 | Cited by | United States of America | Search report |
| US9179320B2 | Cited by | United States of America | Search report |
| US2014044107A1 | Cited by | United States of America | Pre-grant |
| US9392598B2 | Cited by | United States of America | Applicant |
| US2009082027A1 | Cited by | United States of America | Pre-grant |
| US10091695B2 | Cited by | United States of America | Applicant |
| US2009137221A1 | Cited by | United States of America | Pre-grant |
| US9386541B2 | Cited by | United States of America | Applicant |
| US2009197631A1 | Cited by | United States of America | Pre-grant |
| CN112039607A | Cited by | China | Search report |
| US9462562B2 | Cited by | United States of America | Applicant |
| US2010216405A1 | Cited by | United States of America | Pre-grant |
| US2002136179A1 | Cites | United States of America | Pre-grant |
| US2002154621A1 | Cites | United States of America | Pre-grant |
| US2003109274A1 | Cites | United States of America | Pre-grant |
| US2004114552A1 | Cites | United States of America | Pre-grant |
| US2004151264A1 | Cites | United States of America | Pre-grant |
| US2004160925A1 | Cites | United States of America | Pre-grant |
| US2004179480A1 | Cites | United States of America | Pre-grant |
| US2005070287A1 | Cites | United States of America | Pre-grant |
| US2005201351A1 | Cites | United States of America | Pre-grant |
| US2006019679A1 | Cites | United States of America | Pre-grant |
| US2006094436A1 | Cites | United States of America | Pre-grant |
| US2006104242A1 | Cites | United States of America | Pre-grant |
| US2006104254A1 | Cites | United States of America | Pre-grant |
| US2006111137A1 | Cites | United States of America | Pre-grant |
| US2006116154A1 | Cites | United States of America | Pre-grant |
| US2007004423A1 | Cites | United States of America | Pre-grant |
| US2007010203A1 | Cites | United States of America | Pre-grant |
| US2007087749A1 | Cites | United States of America | Pre-grant |
| US2007173199A1 | Cites | United States of America | Pre-grant |
| US2007191051A1 | Cites | United States of America | Pre-grant |
| US2008062925A1 | Cites | United States of America | Pre-grant |
| US2008076407A1 | Cites | United States of America | Pre-grant |
| US2008089296A1 | Cites | United States of America | Pre-grant |
| US2008130593A1 | Cites | United States of America | Pre-grant |
| US2008222021A1 | Cites | United States of America | Pre-grant |
| US2008225966A1 | Cites | United States of America | Pre-grant |
| US2008242243A1 | Cites | United States of America | Pre-grant |
| US2009003305A1 | Cites | United States of America | Pre-grant |
| US2009017832A1 | Cites | United States of America | Pre-grant |
| US2009042593A1 | Cites | United States of America | Pre-grant |
| US2009042596A1 | Cites | United States of America | Pre-grant |
| US2009046632A1 | Cites | United States of America | Pre-grant |
| US2009047931A1 | Cites | United States of America | Pre-grant |
| US2009069017A1 | Cites | United States of America | Pre-grant |
| US2009080386A1 | Cites | United States of America | Pre-grant |
| US2009080499A1 | Cites | United States of America | Pre-grant |
| US2009081970A1 | Cites | United States of America | Pre-grant |
| US2009082026A1 | Cites | United States of America | Pre-grant |
| US2009082027A1 | Cites | United States of America | Pre-grant |
| US2009086861A1 | Cites | United States of America | Pre-grant |
| US2009092111A1 | Cites | United States of America | Pre-grant |
| US2009111473A1 | Cites | United States of America | Pre-grant |
| US2009135754A1 | Cites | United States of America | Pre-grant |
| US2009135796A1 | Cites | United States of America | Pre-grant |
| US2009137221A1 | Cites | United States of America | Pre-grant |
| US2009137241A1 | Cites | United States of America | Pre-grant |
| US2009203320A1 | Cites | United States of America | Pre-grant |
| US2009203372A1 | Cites | United States of America | Pre-grant |
| US2009252099A1 | Cites | United States of America | Pre-grant |
| US2010086092A1 | Cites | United States of America | Pre-grant |
| US2010136998A1 | Cites | United States of America | Pre-grant |
| US2011009065A1 | Cites | United States of America | Pre-grant |
149 members in 16 offices
Priority claims6
| Document | Office | Kind | Date |
|---|---|---|---|
| 99054107 | United States of America | P | |
| 99054707 | United States of America | P | |
| 99045907 | United States of America | P | |
| 99051307 | United States of America | P | |
| 99056407 | United States of America | P | |
| 99057007 | United States of America | P |
Members149
| Document | Office | Kind | |
|---|---|---|---|
| US2009135754A1 | United States of America | A1 | |
| US2009135790A1 | United States of America | A1 | |
| US2009135796A1 | United States of America | A1 | |
| US2009137221A1 | United States of America | A1 | |
| US2009137241A1 | United States of America | A1 | |
| AU2008329793A1 | Australia | A1 | |
| AU2008329797A1 | Australia | A1 | |
| AU2008329799A1 | Australia | A1 | |
| AU2008329801A1 | Australia | A1 | |
| AU2008329805A1 | Australia | A1 | |
| AU2008329809A1 | Australia | A1 | |
| CA2706682A1 | Canada | A1 | |
| CA2706696A1 | Canada | A1 | |
| CA2706698A1 | Canada | A1 | |
| CA2706875A1 | Canada | A1 | |
| CA2706876A1 | Canada | A1 | |
| CA2706877A1 | Canada | A1 | |
| WO2009070602A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2009070606A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2009070608A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2009070610A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2009070614A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2009070618A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2009070602A3 | World Intellectual Property Organization (WIPO) | A3 | |
| WO2009070606A3 | World Intellectual Property Organization (WIPO) | A3 | |
| WO2009070610A3 | World Intellectual Property Organization (WIPO) | A3 | |
| TW200939804A | Taiwan Province of China | A | |
| TW200939805A | Taiwan Province of China | A | |
| TW200939808A | Taiwan Province of China | A | |
| TW200939829A | Taiwan Province of China | A | |
| WO2009070608A3 | World Intellectual Property Organization (WIPO) | A3 | |
| WO2009070614A3 | World Intellectual Property Organization (WIPO) | A3 | |
| US2009252099A1 | United States of America | A1 | |
| TW200943995A | Taiwan Province of China | A | |
| TW200944001A | Taiwan Province of China | A | |
| MX2010005770A | Mexico | A | |
| MX2010005770A | Mexico | A | |
| MX2010005771A | Mexico | A | |
| MX2010005771A | Mexico | A | |
| MX2010005772A | Mexico | A | |
| MX2010005772A | Mexico | A | |
| KR20100087391A | Republic of Korea | A | |
| MX2010005773A | Mexico | A | |
| MX2010005773A | Mexico | A | |
| MX2010005777A | Mexico | A | |
| MX2010005777A | Mexico | A | |
| KR20100087754A | Republic of Korea | A | |
| KR20100088701A | Republic of Korea | A | |
| MX2010005780A | Mexico | A | |
| MX2010005780A | Mexico | A | |
| EP2215874A2 | European Patent Office (EPO) | A2 | |
| KR20100090790A | Republic of Korea | A | |
| KR20100090791A | Republic of Korea | A | |
| EP2218274A1 | European Patent Office (EPO) | A1 | |
| EP2218276A2 | European Patent Office (EPO) | A2 | |
| KR20100092490A | Republic of Korea | A | |
| EP2220774A2 | European Patent Office (EPO) | A2 | |
| EP2220878A2 | European Patent Office (EPO) | A2 | |
| EP2243306A2 | European Patent Office (EPO) | A2 | |
| IL205919A0 | Israel | A0 | |
| IL205921A0 | Israel | A0 | |
| IL205922A0 | Israel | A0 | |
| IL205994A0 | Israel | A0 | |
| IL205995A0 | Israel | A0 | |
| IL205997A0 | Israel | A0 | |
| CN101926139A | China | A | |
| CN101926193A | China | A | |
| CN101926194A | China | A | |
| CN101926195A | China | A | |
| CN101926196A | China | A | |
| CN101926207A | China | A | |
| JP2011505102A | Japan | A | |
| JP2011505759A | Japan | A | |
| JP2011505760A | Japan | A | |
| JP2011508473A | Japan | A | |
| JP2011517863A | Japan | A | |
| JP2011518446A | Japan | A | |
| UA97033C2 | Ukraine | C2 | |
| RU2010126083A | Russian Federation | A | |
| RU2010126095A | Russian Federation | A | |
| RU2010126205A | Russian Federation | A | |
| RU2010126215A | Russian Federation | A | |
| RU2010126228A | Russian Federation | A | |
| UA97430C2 | Ukraine | C2 | |
| HK1152442A | Hong Kong, China | A | |
| HK1152442A1 | Hong Kong, China | A1 | |
| HK1152444A | Hong Kong, China | A | |
| HK1152444A1 | Hong Kong, China | A1 | |
| RU2450483C2 | Russian Federation | C2 | |
| RU2454834C2 | Russian Federation | C2 | |
| AU2008329809B2 | Australia | B2 | |
| UA98985C2 | Ukraine | C2 | |
| KR101173756B1 | Republic of Korea | B1 | |
| KR101180614B1 | Republic of Korea | B1 | |
| KR101180603B1 | Republic of Korea | B1 | |
| RU2461980C2 | Russian Federation | C2 | |
| KR101216063B1 | Republic of Korea | B1 | |
| AU2008329797B2 | Australia | B2 | |
| AU2008329801B2 | Australia | B2 | |
| TWI388227B | Taiwan Province of China | B |
143 transactions on the USPTO file
Allowed after 1 non-final rejection and 4 RCEs.
- Non-final rejections
- 1
- Final rejections
- 0
- RCEs
- 4
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Payment of Maintenance Fee, 4th Year, Large EntityM1551 | M1551 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Printer Rush- No mailingTCPB | TCPB | |
| Printer Rush- No mailingTCPB | TCPB | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Email NotificationEML_NTR | EML_NTR | |
| Printer Rush- No mailingTCPB | TCPB | |
| Mail Miscellaneous Communication to ApplicantMM327 | MM327 | |
| Miscellaneous Communication to Applicant - No Action CountM327 | M327 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Examiner's Amendment CommunicationEX.A | EX.A | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| New or Additional Drawing FiledC614 | C614 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Drawings FinishedDRWF | DRWF | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Miscellaneous Communication to ApplicantMM327 | MM327 | |
| Miscellaneous Communication to Applicant - No Action CountM327 | M327 | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Examiner's Amendment CommunicationEX.A | EX.A | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail PUB Notice of non-compliant IDSMM327-B | MM327-B | |
| PUB Notice of non-compliant IDSM327-B | M327-B | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Workflow - Request for RCE - BeginBRCE | BRCE |
6 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Maintenance fee paymentMAFP | MAFP | |
| Maintenance fee paymentMAFP | MAFP | |
| Maintenance fee paymentMAFP | MAFP | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS | |
| AssignmentAS | AS |
Numbers
- Application
- 27693208
Titles
- English
- INTERFACE MANAGEMENT IN WIRELESS COMMUNICATION SYSTEM USING HYBRID TIME REUSE
Patent term adjustment
- A delay
- +738 daysthe office missed an examination deadline
- B delay
- +441 dayspendency past three years
- Applicant delay
- −463 days
- Net adjustment
- 716 days
Classification
- CPC, 16
- H04W52/143
- H04W72/541
- H04W52/20
- H04W52/244
- H04W52/322
- H04W52/325
- H04W56/0015
- H04W56/0025
- H04W52/44
- H04L1/1825
- H04L5/0092
- H04W52/32
- H04W56/001
- H04W52/38
- H04W28/04
- H04W74/04
- IPC, 2
- H04J3 00
- H04W72 54