This patent application describes a system for use in a wireless communication, which clusters access points and allocates communication frequencies to the clusters.
When connecting to a radio network, an access terminal selects an access point from available radio network access points that are within communication range. Network protocols are used in communicating between an access point and the access terminal.
The 1xRTT protocol has been standardized by the Telecommunication Industry Association (TIA) in the TIA-2000.1 through TIA-2000.6 series of specifications, which are incorporated herein by reference.
The 1xEV-DO protocol has been standardized by the TIA as TIA/EIA/IS-856, “CDMA2000 High Rate Packet Data Air Interface Specification,” 3GPP2 C.S0024-0, Version 4.0, Oct. 25, 2002, which is incorporated herein by reference. Revision A to this specification has been published as TIA/EIA/IS-856A, “CDMA2000 High Rate Packet Data Air Interface Specification,” 3GPP2 C.S0024-A, Version 2.0, July 2005. Revision A is also incorporated herein by reference. Revision B to this specification has been published as TIA/EIA/IS-8560B, 3GPP2 C.S0024-B, version 1.0, May 2006, and is also incorporated herein by reference. Other wireless communication protocols, such as UMTS (Universal Mobile Telecommunications Service), may also be used.
A system is described for use in a wireless communication system comprised of cells, at least one of which comprises at least one sector The system comprises first access points in a first area of a sector of a cell, where the first access points are prohibited from communicating over a first frequency, and second access points in a second area of the sector of the cell, where the second access points are prohibited from communicating over a second frequency that is different from the first frequency. The system may also comprise one or more of the following features, either alone or in combination.
The first access points may be prohibited from communicating over a third frequency that is different from the first frequency and the second frequency. The second access points may be prohibited from communicating over a fourth frequency that is different from the first frequency, the second frequency, and the third frequency.
The system may comprise third access points in a third area of the sector of the cell, where the third access points are prohibited from communicating over a third frequency that is different from the first frequency and different from the second frequency. The system may comprise an Nth (N>3) set of access points in an Nth area of the sector of the cell, where the Nth set of access points are prohibited from communicating over an Nth frequency that is different from the first frequency, different from the second frequency, and different from the third frequency.
The system may comprise a mobile station and a controller associated with the sector. The controller may be configured to direct the mobile station, after entering an area of the sector, to communicate over a frequency over which access points in the area are prohibited from communicating. The controller may be configured to identify interference in communications with the mobile station and to thereafter direct the mobile station.
The first area and the second area may be separated by a zone in which communications of the first access points and the second access points do not interfere. The zone may be predefined based on geography of a region encompassing the sector.
Also described herein is a method for use in a wireless communication system comprised of cells, at least one of which comprises at least one sector. The method comprises first access points in a first area of a sector of a cell communicating over one or more frequencies but not over a first frequency, and second access points in a second area of the sector of the cell communicating over one or more frequencies but not over a second frequency that is different from the first frequency. The method may also comprise one or more of the following features, either alone or in combination.
The first access points may be prohibited from communicating over a third frequency that is different from the first frequency and the second frequency. The second access points may be prohibited from communicating over a fourth frequency that is different from the first frequency, the second frequency, and the third frequency.
The method may comprise third access points in a third area of the sector of the cell communicating over one or more frequencies but not over a third frequency that is different from the first frequency and different from the second frequency. The method may comprise an Nth (N>3) set of access points in an Nth area of the sector of the cell communicating over one or more frequencies but not over an Nth frequency that is different from the first frequency, from the second frequency, and from the third frequency.
The method may comprise a mobile station attempting to communicate with a base station associated with the sector, and a controller directing the mobile station, after entering an area of the sector, to communicate over a frequency over which access points in the area are prohibited from communicating. The controller may identify interference in communications with the mobile station and thereafter direct the mobile station.
The first area and the second area may be separated by a zone in which communications of the first access points and the second access points do not interfere. The zone may be predefined based on geography of a region encompassing the sector.
Also described herein is a method that comprises sharing frequencies for communication among access points of a cell sector and, in each predefined area of a sector, reserving at least one frequency for communication by a mobile station, where the at least one frequency is different in each area. Access points in each area of the sector are configured not to communicate over the at least one frequency for each corresponding area. The method may also comprise one or more of the following features, either alone or in combination.
Upon entering an area of the sector, the mobile station may be controlled to communicate over the at least one frequency corresponding to the area entered if interference from an access point is detected. There may be N (N≧2) areas, and there may be a multiple of N frequencies reserved for communication by the mobile station. Predefined areas of the sector may be separated by substantially interference-free zones.
The foregoing methods, or any aspect thereof, may be implemented as a computer program product comprised of instructions that are stored on one or more machine-readable media, and that are executable on one or more processing devices. The foregoing method may be implemented as an apparatus or system that includes one or more processing devices and memory to store executable instructions to implement the method.
The details of one or more examples are set forth in the accompanying drawings and the description below. Further features, aspects, and advantages will become apparent from the description, the drawings, and the claims.
Cellular wireless communications systems are designed to serve many access terminals distributed in a large geographic area by dividing the area into cells, as shown in
The radio access network (RAN) 100 shown in
For ease of description, communication between wireless network entities, such as between access points and access terminals, is described as occurring at the access point transmission frequency. In general, however, for example, frequency division duplex (FDD) may be used where the transmit frequency of an entity may be associated with, but distinct from, the receive frequency of the entity.
As shown in
When an authorized access terminal 206 is present inside the home (or anywhere within range of the private access point 202), it may use the private access point 202 rather than a regular cellular radio network access point, such as BTS 108, to place or receive voice calls and data connections, even if the access terminal is otherwise within the cell 102 for that BTS 108. We therefore refer to BTS 108 as a macro BTS to distinguish it from a private access point, as macro BTS 108 provides direct access to the wider RAN. An access terminal or mobile macrocell(s) may send signals to and receive signals from the macro BTS 108.
As in
A neighboring home 210 may have its own private access point 212 connected to its cable modem 214 for use by its owner's authorized access terminal 216. Neighboring private access points may operate independently, in part because real-time communication is difficult between neighboring private access points. Private access points may also operate in a licensed spectrum.
The following implementation describes clustering access points and allocating communication frequencies to the clusters. Femtocells and mobile stations are described in the implementation. However, any types of access points may be used.
Referring to
In more detail, femtocells of a sector may be configured to communicate over a set of frequencies, which are identified as F1, F2, and F3 in this example. Each area 301, 302, 303 of the sector includes at least one cluster of femtocells. In area 301, femtocells 301a, 301b, 301c are configured to communicate with a mobile station over frequencies F1 and/or F2. A third frequency, here F3, is reserved for communication between a mobile station and macro BTS 305. Femtocells 301a, 301b, 301c are prohibited from communicating over this third frequency and are configured accordingly. In area 302, femtocells 302a, 302b, 302c are configured to communicate with a mobile station over frequencies F2 and/or F3. A third frequency, here F1, is reserved for communication between the mobile station and the macro BTS. Femtocells 302a, 302b, 302c are prohibited from communicating over this third frequency and are configured accordingly. In area 303, femtocells 303a, 303b, 303c are configured to communicate with a mobile station over frequencies F1 and/or F3. A third frequency, here F2, is reserved for communication between the mobile station and the macro BTS. Femtocells 303a, 303b, 303c are prohibited from communicating over this third frequency and are configured accordingly.
The foregoing configuration promotes frequency balancing among the femtocells and the mobile station. That is, the mobile station tends to use a different frequency in each area for communication with the macro BTS in order to avoid interference from nearby femtocells. The remaining frequencies are distributed (e.g., split evenly or as evenly as possible) among the areas for femtocell communication. This results in more equal utilization of frequencies in the sector than if the same frequency were dedicated to the mobile station in each area. It is noted that a mobile station may not be prohibited from using any particular frequencies for communication in a sector if there is no interfering femtocell within communication range.
Furthermore, allocating more than one frequency for femtocell communication is advantageous because it improves communication quality. That is, since there are multiple frequencies to choose from for communication, a femtocell can choose, or be allocated, a frequency in a way that reduces (e.g., minimizes) interference between nearby femtocells.
Areas in a sector are separated by zones in which femtocell density is low. These zones are referred to as “low-interference” zones. In this regard, femtocells and other types of access points operate at relatively low power and, thus, have limited range. It is therefore possible to arrange clusters of femtocells at sufficient distances from each another to substantially prevent cluster-to-cluster interference at a reserved frequency. For example, femtocells using frequency F1 in cluster 301 should not interfere with reserved frequency F1 in cluster 302 or at least the interference should be below some predefined level.
Regions in which the clusters are contained, and in which femtocell communication is permissible, include areas 301, 302, 303 of
Physical barriers may be used to separate the areas and thereby define the low-interference zones. For example, parks, highways, waterways, commercial zones, buildings, or the like may be used for separation. The size, shape and construction of the zones may be defined when the sector is configured. Additional clusters of femtocells, which define new areas, may be defined in a sector.
Femtocells in each cluster are configured (402). The femtocells may be configured manually, e.g., before or after placement in the clusters. Alternatively, the femtocells may be configured automatically using a network provisioning software tool. Femtocells in a cluster may be configured to communicate over a single frequency within an area of the sector. Alternatively, femtocells in a cluster may be configured to share communication frequencies within an area of the sector. In this case, femtocells in a cluster are configured so that each femtocell is capable of communicating over multiple frequencies within the sector. For example, a femtocell may be configured to switch between frequencies F1 and F2 for communication based, e.g., on the communication traffic over those frequencies. In any case, the femtocells are prohibited from communicating over at least one frequency within the sector, and sometimes more than one frequency. For example, as described above with respect to
During process 400, a mobile station 307 enters sector 300. While in an area 301, mobile station 307 sends a communication to a macro BTS, which is base station 305 in this example, over frequency F1 (the communication could also be over frequency F2). Because femtocells 301a, 301b, 301c communicate over frequency F1 in area 301, communication to/from the mobile station over frequency F1 has low signal quality. For example, there may be interference resulting from femtocell(s) communicating over the same frequency. RNC 120 identifies (403) a relatively low signal quality, and directs (404) the mobile station to communicate over a different frequency. In this case, RNC 120 directs (404) mobile station 307 to communicate over the frequency that femtocells in the area are prohibited from using. In area 301, that frequency is F3. RNC 120 may be pre-programmed with data identifying, for each area of a sector, which communication frequencies are dedicated to femtocell communication, and which communication frequencies are available for other, non-femtocell communication, including for mobile station/macro BTS communication. Alternatively, RNC 320 can request mobile station 307 to measure and report signal quality at available frequencies which, in this case, include frequencies F2 and F3. RNC 320 can then direct mobile station 307 to use the frequency that has the higher signal quality.
RNC 120 may detect low signal quality using any type of mechanism or algorithm. For example, RNC 120 may compare a signal from the mobile station, or attributes thereof, to predefined signals and/or values. If the comparison is unfavorable, e.g., if the signal from the mobile station does not meet one or more predefined threshold(s), RNC 120 identifies low signal quality. RNC 120 may direct the mobile station to switch communication frequencies by, e.g., sending the mobile station one or more signals over a predefined control channel. In response, the mobile station switches (405) communication frequencies as directed by the base station—here to F3.
While in area 301, mobile station 307 continues (406) to communicate over frequency F3. As noted, femtocells in area 301 are prohibited from communicating over frequency F3. As a result, communications between the mobile station and the macro BTS experience less signal degradation. This is advantageous compared to systems where no frequency is reserved for communication with base station 305, and where frequent frequency switching may thus be required.
Mobile station 307 may move (407) within sector 300 to a new area, such as area 302. Mobile station 307 continues to communicate over frequency F3. However, in area 302, frequency F3 is allowed for use by femtocells, as is frequency F2. Frequency F1 is reserved for mobile station/macro BTS communication (or other non-femtocell communications) within area 302. Accordingly, as above, when mobile station 307 communicates over frequency F3 in area 302, RNC 120 identifies (403) a low signal quality for such communications. RNC 120 therefore directs (404) mobile station 307 to switch to frequency F1. In area 302, femtocells are prohibited from communicating over frequency F1. Therefore, as was the case above, communications between the mobile station and base station 305 experience less signal degradation.
When mobile station 307 moves from area 302 to area 303, mobile station 307 will experience the same type of signal degradation described above. That is, in area 303, frequency F1 is allowed for femtocell communication, and mobile station 307 is likely to approach an interfering femtocell. Accordingly, part 408 of process 400 is repeated for area 303, which causes the communication frequency of mobile station 307 to switch to frequency F2. The same process occurs when the mobile station moves between sectors of the cell, e.g., from sector 102b to a sector 102c (
Process 400 is not limited to use with the sector configuration shown in
Outside of femtocell areas of a sector, all frequencies available in that sector or cell may be used by mobile station(s) for communication with the macro BTS. Alternatively, a subset of frequencies available in that sector or cell may be used. The RNC(s) for each sector/cell may be programmed to control the mobile stations accordingly.
By allocating frequency(ies) to femtocells, and reserving frequency(ies) for mobile stations, the cell is able to accommodate a relatively large number of communication signals. Furthermore, it reduces the need to continuously redirect the communication frequencies of the mobile stations; instead limiting redirection to movement between areas. Also, the number of mobile stations per frequency need not be changed significantly from the case where no femtocells are present, and inter-femtocell interference can be reduced.
Process 400 and its various modifications (hereinafter “the processes”), are not limited to the hardware and software described above. All or part of the processes can be implemented, at least in part, via a computer program product, e.g., a computer program tangibly embodied in an information carrier, such as one or more machine-readable media or computer-readable medium, for execution by, or to control the operation of, one or more data processing apparatus, e.g., a programmable processor, a computer, multiple computers, and/or programmable logic components. The computer program product may be resident in the base station, femtocells, and/or the mobile station.
A computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a network.
Actions associated with implementing all or part of the processes can be performed by one or more programmable processors executing one or more computer programs to perform the functions of the calibration process. All or part of the processes can be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) and/or an ASIC (application-specific integrated circuit).
Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. Components of a computer include a processor for executing instructions and one or more memory devices for storing instructions and data.
The foregoing implementations describe RNCs controlling the mobile stations. This functionality may be incorporated into a base station, such as the macro BTS, or in any other device included inside of, or outside of, a cell.
Components of different implementations described herein may be combined to form other embodiments not specifically set forth above. Other implementations not specifically described herein are also within the scope of the following claims.
Number | Name | Date | Kind |
---|---|---|---|
5799154 | Kuriyan | Aug 1998 | A |
6711144 | Kim et al. | Mar 2004 | B1 |
6731618 | Chung et al. | May 2004 | B1 |
6741862 | Chung et al. | May 2004 | B2 |
6781999 | Eyuboglu et al. | Aug 2004 | B2 |
6961323 | Xu et al. | Nov 2005 | B1 |
7170871 | Eyuboglu et al. | Jan 2007 | B2 |
7200391 | Chung et al. | Apr 2007 | B2 |
7242958 | Chung et al. | Jul 2007 | B2 |
7277446 | Abi-Nassif et al. | Oct 2007 | B1 |
7299278 | Ch'ng | Nov 2007 | B2 |
7835698 | Eyuboglu et al. | Nov 2010 | B2 |
7933619 | Kim | Apr 2011 | B2 |
7983672 | Humblet et al. | Jul 2011 | B2 |
8060058 | Ch'ng et al. | Nov 2011 | B2 |
8165528 | Raghothaman et al. | Apr 2012 | B2 |
8229397 | Hou et al. | Jul 2012 | B2 |
8259671 | Raghothaman et al. | Sep 2012 | B2 |
8295256 | Humblet et al. | Oct 2012 | B2 |
8345694 | Den et al. | Jan 2013 | B2 |
8355727 | Hoang et al. | Jan 2013 | B2 |
8358623 | Samar et al. | Jan 2013 | B2 |
8400989 | Ch'ng et al. | Mar 2013 | B2 |
8402143 | Ramaswamy et al. | Mar 2013 | B2 |
8452299 | Raghothaman et al. | May 2013 | B2 |
8520659 | Humblet | Aug 2013 | B2 |
8543139 | Samar et al. | Sep 2013 | B2 |
8554231 | Jones | Oct 2013 | B2 |
8594663 | Ch'ng et al. | Nov 2013 | B2 |
8615593 | Ch'ng et al. | Dec 2013 | B2 |
8750271 | Jones | Jun 2014 | B2 |
8781483 | Ch'ng | Jul 2014 | B2 |
20020196749 | Eyuboglu et al. | Dec 2002 | A1 |
20030100311 | Chung et al. | May 2003 | A1 |
20050213555 | Eyuboglu et al. | Sep 2005 | A1 |
20050243749 | Mehrabanzad et al. | Nov 2005 | A1 |
20050245279 | Mehrabanzad et al. | Nov 2005 | A1 |
20060067422 | Chung | Mar 2006 | A1 |
20060067451 | Pollman et al. | Mar 2006 | A1 |
20060126509 | Abi-Nassif et al. | Jun 2006 | A1 |
20060159045 | Ananthaiyer et al. | Jul 2006 | A1 |
20060240782 | Pollman et al. | Oct 2006 | A1 |
20060291420 | Ng | Dec 2006 | A1 |
20060294241 | Cherian et al. | Dec 2006 | A1 |
20070026884 | Rao | Feb 2007 | A1 |
20070058628 | Rao et al. | Mar 2007 | A1 |
20070077948 | Sharma et al. | Apr 2007 | A1 |
20070097916 | Eyuboglu et al. | May 2007 | A1 |
20070115896 | To et al. | May 2007 | A1 |
20070140172 | Garg et al. | Jun 2007 | A1 |
20070140184 | Garg et al. | Jun 2007 | A1 |
20070140185 | Garg et al. | Jun 2007 | A1 |
20070140218 | Nair et al. | Jun 2007 | A1 |
20070155329 | Mehrabanzad et al. | Jul 2007 | A1 |
20070220573 | Chiussi et al. | Sep 2007 | A1 |
20070230419 | Raman et al. | Oct 2007 | A1 |
20070238442 | Mate et al. | Oct 2007 | A1 |
20070238476 | Raman et al. | Oct 2007 | A1 |
20070242648 | Garg et al. | Oct 2007 | A1 |
20070248042 | Harikumar et al. | Oct 2007 | A1 |
20080003988 | Richardson | Jan 2008 | A1 |
20080013488 | Garg et al. | Jan 2008 | A1 |
20080062925 | Mate et al. | Mar 2008 | A1 |
20080065752 | Ch'ng et al. | Mar 2008 | A1 |
20080069020 | Richardson | Mar 2008 | A1 |
20080069028 | Richardson | Mar 2008 | A1 |
20080070510 | Doppler et al. | Mar 2008 | A1 |
20080076398 | Mate et al. | Mar 2008 | A1 |
20080117842 | Rao | May 2008 | A1 |
20080119172 | Rao et al. | May 2008 | A1 |
20080120417 | Harikumar et al. | May 2008 | A1 |
20080139203 | Ng et al. | Jun 2008 | A1 |
20080146232 | Knisely | Jun 2008 | A1 |
20080151843 | Valmikam et al. | Jun 2008 | A1 |
20080159236 | Ch'ng et al. | Jul 2008 | A1 |
20080162924 | Chinitz et al. | Jul 2008 | A1 |
20090156218 | Garg et al. | Jun 2009 | A1 |
20090163238 | Rao et al. | Jun 2009 | A1 |
20090168766 | Eyuboglu et al. | Jul 2009 | A1 |
20090172397 | Kim | Jul 2009 | A1 |
20100085910 | Humblet | Apr 2010 | A1 |
20100118801 | Yavuz et al. | May 2010 | A1 |
20110026441 | Diener et al. | Feb 2011 | A1 |
20110128916 | Kwon et al. | Jun 2011 | A1 |
20120178415 | Ch'ng et al. | Jul 2012 | A1 |
20130136104 | Samar et al. | May 2013 | A1 |
Number | Date | Country |
---|---|---|
WO2010011084 | Jan 2010 | WO |
Entry |
---|
3rd Generation Partnership Project “3GPP2”, “cdma2000 High Rate Packet Data Air Interface Specification”, TIA/EIA/IS-856, C.S0024, version 4.0, Oct. 25, 2002 (548 pages). |
3rd Generation Partnership Project “3GPP2”, “cdma2000 High Rate Data Air Interface Specification”, TIA/EIA/IS-856, C.S0024-A, version 2.0, Jul. 2005 (1227 pages). |
3rd Generation Partnership Project “3GPP2”, “cdma2000 High Rate Data Air Interface Specification”, TIA/EIA/IS-856, C.S0024-B, version 1.0, Apr. 2006 (1623 pages). |
3rd Generation Partnership Project 2 “3GPP2”, “cdma2000 High Rate Packet Data Interface Specification”, C.S0024, version 2, Oct. 27, 2000 (441 pages). |
3rd Generation Partnership Project 2 “3GPP2”, “cdma2000 High Rate Packet Data Interface Specification”, C.S0024-B, version 2, Mar. 2007 (1627 pages). |
3rd Generation Partnership Project 2 “3GPP2”, “Introduction to cdma2000 Standards for Spread Spectrum Systems”, 3Gpp2 C.S0001-D, Version 2.0, Sep. 6, 2005, Release D (16 pages). |
3rd Generation Partnership Project 2 “3GPP2”, “Physical Layer Standard for cdma2000 Spread Spectrum Systems”, 3GPP2 C.S0002-D, Version 2.0, Sep. 6, 2005, Revision D (538 pages). |
3rd Generation Partnership Project 2 “3GPP2”, “Medium Access Control (MAC) Standard for cdma2000 Spread Spectrum Systems”, 3GPP2 C.S0003-D, Version 2.0, Sep. 2005, Release D (255 pages). |
3rd Generation Partnership Project 2 “3GPP2”, “Signaling Link Access Control (LAC) Standard for cdma2000 Spread Spectrum Systems”, Release D, 3GPP2 C.S0004-D, Version 2.0, Sep. 2005, Revision D. v2.0, (264 pages). |
3rd Generation Partnership Project 2 “3GPP2”, “Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread Spectrum Systems”, Release D, 3GPP2 C.S0005-D, Version 2.0, Sep. 2005, Release D (2367 pages). |
3rd Generation Partnership Project 2 “3GPP2”, “Analog Signaling Standard for cdma2000 Spread Spectrum Systems”, 3GPP2 C.S0006-D, Version 2.0, Sep. 2005, Release D (95 pages). |
Number | Date | Country | |
---|---|---|---|
20100085910 A1 | Apr 2010 | US |