CN105594244B - Apparatus and method for distributed updating of self-organizing network - Google Patents

Abstract

The disclosure gives the distributed method and apparatus updated for self-organizing network.Such as, the disclosure gives a kind of method and is used for: being transmitted in a part for the data that the base station is collected to network entity via the transfer assembly of base station, it is wherein that from being in one or more base stations, the one or more user equipments (UE) communicated are received, and wherein the base station is one of the one or more base station by the base station in the data that the base station is collected；Feedback associated with one or more network parameters of the base station is received from the network entity, wherein the feedback received from the network entity is at least determined based on the part of the data transmitted from the one or more base station to the network entity at the network entity；And the one or more network parameter of the base station is updated based on the local information received from the feedback of the network entity and the base station.It may achieve the distributed of self-organizing network as a result, to update.

Description

Apparatus and method for distributed updating of self-organizing network

priority claim

In addition, this application requires the provisional application No.61/ 885,355, the provisional application is assigned to the assignee of the present application and is hereby expressly incorporated by reference.

background

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may employ a multiple access technique capable of supporting communication with multiple users by sharing available system resources (eg, bandwidth, transmit power). Examples of such multiple access techniques include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) system, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) system.

These multiple-access technologies have been adopted in various telecommunications standards to provide a common protocol that enables disparate wireless devices to communicate on a city, national, regional, and even global level. An example of an emerging telecommunication standard is Long Term Evolution (LTE). LTE is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by Third Generation Partnership Project (3GPP). It is designed to improve spectral efficiency, reduce costs, improve services, utilize new spectrum, and use OFDMA on the downlink (DL), SC-FDMA on the uplink (UL), and use multiple-input multiple-output Other open standards for (MIMO) antenna technology are better integrated to better support mobile broadband Internet access. However, as the demand for mobile broadband access continues to grow, there exists a need for further improvements in LTE technology. Preferably, these improvements should be applicable to other multiple access technologies and telecommunication standards employing these technologies.

To supplement conventional base stations, additional limited-power or limited-coverage base stations, referred to as small-coverage base stations or cells, can be deployed to provide more robust wireless coverage to mobile devices. For example, wireless relay stations and low-power base stations (e.g., which may be commonly referred to as Home Node Bs or Home eNBs—collectively H(e)NBs, femto nodes, pico nodes, etc.) can be deployed for incremental capacity growth , a richer user experience, in-building or other specific geographic coverage, and more. Such low-power or small-coverage base stations (e.g., as opposed to a macro network base station or cell) may be connected to the Internet via a broadband connection (e.g., a digital subscriber line (DSL) router, cable or other modem, etc.), The operator's network provides the backhaul link. Thus, for example, a small-coverage base station may be deployed in a user's home to provide mobile network access to one or more devices via a broadband connection. Since the deployment of such base stations is unplanned, low power base stations may interfere with each other if multiple stations are deployed within close proximity of each other.

For example, transmit power management for small cells can help improve capacity and coverage, and was identified as part of the "Capacity and Coverage Optimization" framework in LTE, and defined in 3GPP as a centralized ad hoc that can reside within a central network server Network features. A centralized framework can benefit from information gathered over a wider area and from a large number of resources, including reports from eNBs and reports from UEs via Minimization of Drive Test (MDT) procedures. A centralized ad-hoc network function can reduce the transmit power of a cell where it can reduce interference and improve signal-to-interference-noise ratio (SINR) without compromising coverage. The MDT feature allows the central SON server to track coverage holes in the network, while measurement reports from UEs allow tracking of SINR. For faster responsiveness and better scalability at lower cell densities, a better coordination between centralized and distributed design options is required.

Accordingly, methods and apparatus for distributed updating of ad hoc networks are desired.

overview

Various aspects are now described with reference to the figures. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects. It may be evident, however, that such aspect(s) may be practiced without these specific details. A brief summary of one or more aspects is presented below to provide a basic understanding of these aspects.

This disclosure presents example methods and apparatus for distributed updates of ad hoc networks. For example, this disclosure presents an example method for transmitting a portion of data collected at a base station to a network entity via a transmitting component at the base station, where the data collected at the base station was obtained by the base station from an Received by one or more user equipment (UE) with multiple base stations in communication, where the base station is one of the one or more base stations; receiving feedback from the network entity associated with one or more network parameters of the base station , wherein the feedback received from the network entity is determined at the network entity based on at least the portion of the data transmitted from the one or more base stations to the network entity; and based on the feedback received from the network entity and the base station local information at the base station to update the one or more network parameters at the base station.

In an additional aspect, an apparatus for distributed updating of an ad hoc network is disclosed. For example, the apparatus may include means for communicating to a network entity a portion of data collected at a base station obtained by the base station from one or more Received by a user equipment (UE), where the base station is one of the one or more base stations; means for receiving, from the network entity, feedback associated with one or more network parameters of the base station, where received from the network the entity's feedback is determined at the network entity based on at least the portion of the data transmitted from the one or more base stations to the network entity; and for determining based on feedback received from the network entity and local information at the base station means for updating the one or more network parameters at the base station.

In a further aspect, a computer program product for distributed updating of an ad hoc network is disclosed. For example, the computer program product may include a computer-readable medium comprising code executable by a computer to: transmit to a network entity, via a transmitting component at the base station, a portion of the data collected at the base station, where the collected The data for the base station is received by the base station from one or more user equipments (UEs) in communication with one or more base stations, where the base station is one of the one or more base stations; receiving from the network entity the communication with the base station Feedback associated with one or more network parameters, wherein the feedback received from the network entity is determined at the network entity based on at least the portion of the data transmitted from the one or more base stations to the network entity; and based on Feedback from the network entity and local information at the base station is received to update the one or more network parameters at the base station.

Furthermore, the present disclosure presents means for distributed updating of ad hoc networks. For example, the apparatus may include a data transmitting component for transmitting to a network entity a portion of data collected at a base station, where the data collected at the base station was obtained by the base station from a network in communication with one or more base stations or a plurality of user equipments (UEs), wherein the base station is one of the one or more base stations; a feedback receiving component configured to receive, from the network entity, feedback associated with one or more network parameters of the base station , wherein the feedback received from the network entity is determined at the network entity based on at least the portion of the data transmitted from the one or more base stations to the network entity; The one or more network parameters at the base station are updated using feedback from a network entity and local information at the base station.

To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the appended claims. Certain illustrative aspects of the one or more aspects are set forth in detail in the following description and accompanying drawings. These aspects are indicative, however, of but a few of the various ways in which the principles of the various aspects may be employed and described aspects are intended to cover all such aspects and their equivalents.

Brief description of the drawings

1 is an illustration of a wireless communication system in accordance with various aspects set forth herein.

2 is an illustration of a wireless network environment that may be employed in connection with the various systems and methods described herein.

3 illustrates a communication system that enables deployment of access point base stations within a network environment.

4 is an overview of an environment that facilitates distributed coverage optimization, according to an aspect of the present specification.

5 illustrates a block diagram of a self-optimizing unit that facilitates distributed coverage optimization in accordance with an aspect of the present specification.

6 is an illustration of the coupling of electrical components enabling distributed coverage optimization, according to an aspect.

7 is a flowchart illustrating a methodology for performing self-optimization in accordance with an aspect of the present specification.

8 is a flowchart illustrating a methodology for propagating coverage reports in accordance with an aspect of the present specification.

9 is a block diagram illustrating an example wireless system in various aspects of the present disclosure.

10 is a block diagram illustrating an example distributed update manager in accordance with various aspects described herein.

11 is a flowchart illustrating an example of a method for distributed updates according to various aspects described herein.

12 is a block diagram illustrating an example of a logical grouping of electrical components in accordance with various aspects described herein.

13 illustrates an example of a network that facilitates distributed coverage optimization according to an aspect described herein.

14 is an illustration of an example of a communication system implemented in accordance with various aspects described herein.

15 is an illustration of an example of a base station in accordance with various aspects described herein.

16 is an illustration of an example of a wireless terminal implemented in accordance with various aspects described herein.

Detailed Description

Various aspects are now described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects. It may be evident, however, that such aspect(s) may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form to help describe one or more aspects.

In one aspect, the present disclosure provides methods and apparatus for distributed updates of ad hoc networks. For example, a base station may collect data from UEs in communication with the base station and/or neighboring base stations. The base station may transmit a portion of the data (eg, an aggregated sample or report) to a network entity. In an aspect, the network entity may receive such information from one or more base stations in the ad hoc network of base stations. The network entity determines feedback for the base station based on data received from the base station (and other base stations), and may communicate minimum values, maximum values, and/or ranges of values to the base station. For example, the network entity may provide feedback to the base station to update the transmit power of the base station to at least 200mW. In addition to feedback received from the network entity (eg, to update the transmit power to at least 200mW), the base station may also use local information available at the base station and may update the transmit power to a value (eg, 220mW).

Referring now to FIG. 1 , a wireless communication system 100 is illustrated in accordance with various aspects presented herein. System 100 includes a base station 102, which may include multiple antenna groups. For example, one antenna group may include antennas 104 and 106 , another group may include antennas 108 and 110 , and yet another group may include antennas 112 and 114 . Two antennas are shown for each antenna group; however, more or fewer antennas may be utilized for each group. The base station 102 may also include a transmitter chain and a receiver chain, each of which may in turn include various components associated with signal transmission and reception (e.g., processors, modulators, multiplexers, demodulators, demultiplexers, antenna, etc.), as will be appreciated by those skilled in the art.

Base station 102 can communicate with one or more access terminals, such as access terminal 116 and access terminal 122; however, it should be appreciated that base station 102 can communicate with substantially any number of access terminals similar to access terminals 116 and 122. terminal communication. Access terminals 116 and 122 may be, for example, cellular telephones, smartphones, laptops, handheld communication devices, handheld computing devices, satellite radios, global positioning systems, PDAs, and/or any other devices suitable for communicating wirelessly Devices on system 100 that communicate. As depicted, access terminal 116 is in communication with antennas 112 and 114, where antennas 112 and 114 transmit information to access terminal 116 on forward link 118 and transmit information to access terminal 116 on reverse link 120. 116 Receive information. Additionally, access terminal 122 is in communication with antennas 104 and 106, wherein antennas 104 and 106 transmit information to access terminal 122 on forward link 124 and receive information from access terminal 122 on reverse link 126. . In a frequency division duplex (FDD) system, for example, forward link 118 may utilize a different frequency band than that used by reverse link 120, and forward link 124 may utilize a different frequency band than that used by reverse link 126. different frequency bands. Furthermore, in a time division duplex (TDD) system, forward link 118 and reverse link 120 can utilize a common frequency band and forward link 124 and reverse link 126 can utilize a common frequency band.

Each group of antennas and/or the area in which they are designated to communicate may be referred to as a sector of base station 102 . For example, an antenna group may be designed to communicate with access terminals in a sector of the area covered by base station 102 . In communications on forward links 118 and 124 , the transmit antennas of base station 102 can utilize beamforming to improve the signal-to-noise ratio of forward links 118 and 124 for access terminals 116 and 122 . In addition, when base station 102 utilizes beamforming to transmit to access terminals 116 and 122 scattered randomly throughout the associated coverage, in contrast to a base station transmitting to all of its access terminals through a single antenna, neighbor base stations Access terminals in will experience less interference.

FIG. 2 illustrates an example wireless communication system 200 . For simplicity, wireless communication system 200 depicts a base station 210 and an access terminal or user equipment (UE) 250 . It should be appreciated, however, that system 200 may include more than one base station and/or more than one access terminal, wherein additional base stations and/or access terminals may be substantially similar or similar to the example base station 210 and access terminal 250 described below. different. In addition, it should be appreciated that base station 210 and/or access terminal 250 can employ the systems and/or methods described herein to facilitate wireless communication therebetween.

At base station 210 , traffic data for several data streams is provided from a data source 212 to a transmit (TX) data processor 214 . According to an example, each data stream may be transmitted on a respective respective antenna. TX data processor 214 formats, codes, and interleaves the traffic data stream based on a particular coding scheme selected for the traffic data stream to provide coded data.

The coded data for each data stream may be multiplexed with pilot data using Orthogonal Frequency Division Multiplexing (OFDM) techniques. Additionally or alternatively, the pilot symbols may be frequency division multiplexed (FDM), time division multiplexed (TDM), or code division multiplexed (CDM). Pilot data is typically a known data pattern that is processed in a known manner and can be used at the access terminal 250 to estimate the channel response. The multiplexed pilot and encoded data for each data stream may be based on the particular modulation scheme selected for that data stream (e.g., Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), M-phase Modulation (e.g., symbol mapping) by Shift Keying (M-PSK), M-Quadrature Amplitude Modulation (M-QAM), etc.) to provide modulation symbols. The data rate, coding, and modulation for each data stream may be determined by instructions executed or provided by processor 230 .

The modulation symbols for the data streams may be provided to TX MIMO processor 220, which may further process the modulation symbols (eg, for OFDM). TX MIMO processor 220 then provides NT modulation symbol streams to _NT transmitters ( _TMTR ) 222a through 222t. In various aspects, TX MIMO processor 220 applies beamforming weights to the symbols of each data stream and to the antenna from which the symbol is being transmitted.

Each transmitter 222 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and frequency upconverts) these analog signals to provide a signal suitable for transmission over a MIMO channel. modulated signal. Further, NT modulated signals from transmitters 222a through _222t are then transmitted from NT antennas 224a through _224t , respectively.

At access terminal 250, the transmitted modulated signals are received by _NR antennas 252a through 252r and the received signal from each antenna 252 is provided to a corresponding receiver (RCVR) 254a through 254r. Each receiver 254 conditions (eg, filters, amplifies, and downconverts) a respective signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding "received" symbol stream.

An RX (receive) data processor 260 can receive and process the _NR received symbol streams from _NR receivers 254 based on a particular receiver processing technique to provide _NT "detected" symbol streams. RX data processor 260 can demodulate, deinterleave, and decode each detected symbol stream to recover the traffic data for the data stream. The processing by RX data processor 260 is complementary to that performed by TX MIMO processor 220 and TX data processor 214 at base station 210 .

Processor 270 may periodically determine which available technology to use, as discussed above. Additionally, processor 270 can formulate a reverse link message including a matrix index portion and a rank value portion.

Reverse link messages may include various types of information about the communication link and/or the received data stream. Reverse link messages may be processed by TX data processor 238, which also receives traffic data for several data streams from data source 236, modulated by modulator 280, conditioned by transmitters 254a through 254r, and transmitted back to the base station 210.

At base station 210, the modulated signal from access terminal 250 is received by antenna 224, conditioned by receiver 222, demodulated by demodulator 240, and processed by RX data processor 242 to extract reverse link message. Additionally, processor 230 can process the extracted messages to determine which precoding matrix to use to determine beamforming weights.

Processors 230 and 270 can direct (eg, control, coordinate, manage, etc.) operation at base station 210 and access terminal 250, respectively. Respective processors 230 and 270 can be associated with memory 232 and 272 that store program codes and data. Processors 230 and 270 may also perform computations for deriving frequency and impulse response estimates for the uplink and downlink, respectively.

3 illustrates an example communication system that enables deployment of access point base stations within a network environment. As shown in FIG. 3 , system 300 includes a plurality of access point base stations or, alternatively, femtocells, Home Node B units (HNBs), or Home Evolved Node B units (HeNBs), such as, for example, HNB 310 , each installed in a respective small-scale network environment such as, for example, one or more user residences 330 and configured to serve associated as well as foreign user equipment (UE) or mobile stations 320 . Each HNB 310 is further coupled to the Internet 340 and mobile operator core network 350 via a DSL router (not shown) or alternatively a cable modem (not shown).

This specification is generally directed to various aspects that enable distributed coverage optimization. In particular, aspects are disclosed for the concept of information exchange for the purpose of automated distributed CCO, the semantics of the information exchanged, and the method for computing the information to be exchanged. To this end, an overview of an example system that facilitates distributed coverage optimization according to an aspect of the present specification is provided in FIG. 4 . As illustrated, system 400 includes a plurality of base stations 410, 420, 430 that serve wireless terminals 412, 422, 432, respectively. For this particular aspect, information is exchanged between base stations 410, 420, 430 for CCO purposes. In one aspect, base stations 410, 420, 430 directly exchange information about long-term coverage statistics in the cells they maintain. In this regard, these statistics reflect measurements collected by base stations 410 , 420 , 430 and/or by wireless terminals 412 , 422 , 432 connected to cells maintained by base stations 410 , 420 , 430 . In a specific aspect, the information is packaged into specific messages to be exchanged between eNBs using standardized protocols such as X2AP (3GPP TS 36.423) or S1AP (TS 36.421) generic name). Here, it should be noted that information may be exchanged via any of a variety of mechanisms, including, for example, periodically (where the period may be configurable by the network operator), on base station request, and/or triggered by certain configurable events (eg, when the load in the cell exceeds a certain threshold, etc.).

With regard to semantics, it should be noted that eNBs may exchange coverage related statistics reflecting any of a number of characteristics. For example, in an aspect, such statistics may reflect downlink/uplink coverage quality in a cell, received downlink/uplink power, received downlink/uplink interference power, Downlink interference power received from a particular neighbor, UE transmit power level, cell geometry, and/or path loss in the cell.

In a further aspect, coverage related statistics are computed using internal eNB measurements and/or UE Measurement Report Messages (MRMs), where the time scale for computing these statistics is configurable by the network operator. In a particular aspect, coverage-related statistics are computed over a period of time long enough to cover any of a variety of changes, including, for example, UE geographic distribution changes, serving and neighbor cell load changes, and/or UE mobility Pattern changes.

Here, it should be noted that the method for computing coverage statistics exchanged between eNBs can be standardized. For example, the definition of each statistic that is exchanged can be standardized. Another approach, however, is to not standardize the methods used to compute coverage statistics. For example, average cell geometry can be defined as a number between 0 and 1, where lower numbers are associated with lower geometries. In this regard, the eNB may then simply indicate that its average geometry is 0.5 without indicating how this average geometry was calculated. Similarly, an eNB maintaining cell i may advertise an interference coefficient IC _i,j to describe the level of interference received in cell i from cell j (e.g., IC _i,j = 0.5), without specifying how computational. In this case, the semantics (eg, meaning) of each statistic and its range (eg, 0 to 1) can be normalized.

As previously mentioned, the eNB may compute coverage statistics from internal measurements and/or UE MRM. An eNB may configure UEs served by the eNB to collect and report measurements of signal quality, per serving cell and/or neighbor cells. In an aspect, the UE can measure and report the signal quality of the serving cell as well as the neighbor cells. For example, the eNB may configure the UE to measure and report the reference signal received power (RSRP) level of the serving cell and/or neighbor cell, the reference signal received quality (RSRQ) level of the serving cell and/or neighbor cell , Radio Signal Strength Indication (RSSI) levels, UE transmit power levels, other measurements specified by specific protocols (eg, 3GPP TS 36.423). Here, it should also be noted that these measurement reports can be configured to be periodic and/or triggered.

Referring next to FIG. 5 , there is provided a block diagram of a self-optimizing unit that facilitates distributed coverage optimization according to an aspect. As shown, the self-optimizing unit 500 may include a processor component 510 , a memory component 520 , a communication component 530 , an optimization component 540 , a computation component 550 , and a trigger component 560 . Here, it should be appreciated that self-optimizing unit 500 may reside, for example, in a base station (eg, eNB) or an access point base station (eg, HeNB).

In one aspect, processor component 510 is configured to execute computer readable instructions related to performing any of a plurality of functions. Processor component 510 may be a single unit dedicated to analyzing information to be conveyed from self-optimizing unit 500 and/or generating information that may be utilized by memory component 520, communication component 530, optimization component 540, computing component 550, and/or triggering component 560 processor or multiple processors. Additionally or alternatively, the processor component 510 may be configured to control one or more components in the self-optimizing unit 500 .

In another aspect, memory component 520 is coupled to processor component 510 and configured to store computer readable instructions for execution by processor component 510 . Memory component 520 may also be configured to store any of a variety of other types of data, including data generated by any of communication component 530 , optimization component 540 , calculation component 550 , and/or trigger component 560 . Memory component 520 may be configured in a number of different configurations, including as random access memory, battery backed memory, hard disk, magnetic tape, and the like. Various features can also be implemented on the storage component 520, such as compression and automatic backup (eg, the use of redundant independent drive array configurations).

In another aspect, communication component 530 is also coupled to processor component 510 and configured to interface self-optimizing unit 500 with external entities. For example, the communication component 530 can be configured to receive coverage-related measurements from external entities, and to report coverage reports generated by the computing component 550 . Here, it should be noted that such external entities may include wireless terminals and/or base stations, where communication components are configured to facilitate certain communications. For example, with respect to wireless terminals, the communication component 530 can be further configured to provide configuration data to the wireless terminals to configure the wireless terminals to collect certain coverage-related measurements. With respect to base stations, however, communication component 530 may be further configured to facilitate a backhaul connection with a particular base station (eg, via an S1 or X2 interface).

As illustrated, the self-optimizing unit 500 may further include an optimizing component 540 and a computing component 550 . In this aspect, optimizing component 540 is configured to self-optimize coverage parameters as a function of at least one coverage-related measure, and computing component 550 is configured to provide a coverage report based on the at least one coverage-related measure. In a particular aspect, computing component 550 is further configured to determine a set of coverage-related statistics to include in the coverage report. It should be noted that the set of coverage-related statistics may be associated with any of a variety of characteristics including, for example, coverage quality (e.g., downlink/uplink coverage quality in a cell), received power (e.g., received received downlink/uplink power), received interference power (e.g., received downlink/uplink interference power), received downlink interference power from a specific neighbor, user equipment transmit power , cell geometry, and/or path loss in the cell.

In a further aspect, computing component 550 is configured to compute the set of coverage-related statistics across the at least one coverage-related measurement. For example, calculation component 550 can be configured to calculate an average, maximum, and/or minimum across the at least one coverage-related measurement. In this regard, calculation component 550 can be further configured to perform such calculations across any of a plurality of coverage-related measurements, where such measurements can be associated with a serving cell and/or a neighbor cell. For example, it is contemplated that coverage-related measurements may include reference signal received power, reference signal received quality, reference signal strength indication, and/or user equipment transmit power. Computing component 550 may also be configured to perform averaging of cell geometry, path loss in the cell, and/or signal-to-noise ratio requirements of the user equipment. In another aspect, computing component 550 is further configured to compute an interference coefficient associated with at least one neighbor cell.

Here, it should be noted that the coverage report provided by computing component 550 is associated with the coverage provided by at least one cell. For example, the at least one cell may be a serving cell, a neighbor cell, and/or an extended neighbor cell. Here, with respect to extended neighbor cells, coverage reports may be configured by a network entity (eg, a radio resource controller) to include coverage information associated with a particular set of extended neighbor cells. For example, the network entity may specify that the coverage report is based on coverage related measurements related to an extended set of neighbor cells within a threshold number of hops from the serving cell.

In a further aspect, coverage reports generated by computing component 550 can be disseminated to external entities. For example, communicating component 530 can be further configured to communicate the coverage report to a base station. In a particular aspect, the coverage report is included in a series of coverage reports, wherein communication component 530 is configured to report the series of coverage reports on a periodic basis. In this regard, the period may be configurable by a network entity. In another aspect, communication component 530 is configured to communicate the coverage report based on detection of a trigger event (eg, a request for the coverage report) by trigger component 560 . For this aspect, triggering component 560 is thus configured to detect any of a plurality of triggering events including, for example, a request for a coverage report, a determination of whether a load in a cell exceeds a threshold, and the like.

Referring next to FIG. 6 , illustrated is a system 600 that facilitates distributed coverage optimization in accordance with an aspect. System 600 can reside within, for example, a base station (eg, eNB, HeNB, etc.). System 600 includes functional blocks that can represent functions implemented by a processor, software, or combination thereof (eg, firmware), where system 600 includes a logical grouping 602 of electrical components that can act in conjunction. As illustrated, logical grouping 602 can include electrical component 610 for establishing communication with at least one external entity. Furthermore, logical grouping 602 can include an electrical component 612 for receiving coverage related measurements from the at least one external entity. Logical grouping 602 can also include an electrical component 614 for self-optimizing coverage parameters as a function of coverage-related measurements. Additionally, system 600 may include memory 620 that retains instructions for performing functions associated with electrical components 610 , 612 , and 614 . Although shown as being external to memory 620 , it should be understood that electrical components 610 , 612 , and 614 may reside within memory 620 .

Referring next to FIG. 7 , a flowchart illustrating an example method for performing self-optimization according to an aspect is provided. As illustrated, process 700 includes a series of actions that may be performed by a base station (eg, eNB, HeNB, etc.) in accordance with an aspect of the present specification. For example, process 700 may be implemented by employing a processor to execute computer-executable instructions stored on a computer-readable storage medium to implement the series of actions. In another aspect, a computer-readable storage medium comprising code for causing at least one computer to implement the acts of process 700 is contemplated.

In one aspect, process 700 begins at act 710 with establishing an external entity communication. As previously stated, such communications may be with, for example, wireless terminals or base stations. Once communication is established, a determination is performed at act 720 as to whether the external entity is a wireless terminal. If the external entity is indeed a wireless terminal, process 700 proceeds to configuring the wireless terminal at act 730 , where coverage related measurements are then received from the wireless terminal at act 740 . Otherwise, if the external entity is not a wireless terminal, process 700 proceeds directly to act 740, where coverage related measurements are received from a non-wireless terminal external entity (eg, an eNB serving a neighbor cell). Once the coverage related measurements are received at act 740, the process 700 then ends at act 750, where self-CCO is performed based on the received coverage related measurements.

Referring next to FIG. 8 , a flowchart illustrating an example method for disseminating coverage reports is provided. As illustrated, process 800 also includes a series of actions that can be performed by a base station (eg, eNB, HeNB, etc.) in accordance with an aspect of the present specification. For example, process 800 may be implemented by employing a processor to execute computer-executable instructions stored on a computer-readable storage medium to implement the series of actions. In another aspect, a computer-readable storage medium comprising code for causing at least one computer to implement the actions of process 800 is contemplated.

In an aspect, similar to process 700, process 800 begins at act 810 with the base station establishing communication with an external entity. Next, at act 820, coverage related measurements are received from the external entity (eg, from a wireless terminal, eNB, HeNB, etc.), after which at act 830 a coverage report is generated based on the received coverage related measurements. Process 800 then proceeds to act 840, where a determination is made as to whether a triggering event has occurred. Here, it should be noted that detecting a trigger event at act 840 may comprise monitoring any of a plurality of trigger events, including eg monitoring a load in a cell. If a triggering event is indeed detected, process 800 ends at act 860, where a coverage report is communicated to the base station. Otherwise, if no triggering event is detected, coverage reports may be reported based on a predetermined periodicity. For example, in one aspect, process 800 proceeds to act 850, where an elapsed period determination is made. Here, if the period for communicating the coverage report has elapsed, process 800 ends at act 850, where the coverage report is communicated to the base station. Otherwise, if the period has not elapsed, process 800 loops back to act 840 where the trigger event is again monitored.

9 illustrates a wireless communication system 900 that facilitates distributed updates of a self-organizing network (SON) by operating a distributed update manager 1002 by one or more base stations of the system 900 . In this case, the one or more base stations may be defined as a SON.

For example, in one aspect, system 900 can be a system having one or more base stations (e.g., base station 922) in communication with core network entity 910 via one or more communication links (e.g., links 932, 934, and/or 936). , 924 and/or 926) communication network. System 900 may include one or more user equipments (UEs), such as UEs 942 , 944 and/or 946 . For example, in an aspect, UEs 942, 944, and 946 can be in communication with base stations 922, 924, and 926, respectively. In an additional aspect, each of UEs 942, 944, and 946 can communicate with more than one base station, even if the UE is only camped on one base station. In additional or optional aspects, network entity 910 may reside on one server, or on multiple servers for load sharing and/or redundancy in the event of a failure.

In one aspect, base stations 922, 924, and/or 926 can be small cells. As used herein, the term "small cell" refers to a cell of relatively lower transmit power and/or relatively smaller coverage area than that of a macrocell. Further, the term "small cell" may include, but is not limited to, cells such as femtocells, picocells, access point base stations, Home NodeBs, femto access points, or femtocells. For example, a macro cell may cover a relatively large geographic area, such as but not limited to a radius of several kilometers. In contrast, a small cell, such as a picocell, may cover a relatively small geographic area, such as, but not limited to, a building. Alternatively or additionally, a small cell, such as a femtocell, may also cover a relatively small geographic area, such as, but not limited to, a home, or the first floor of a building.

In one aspect, apparatus and methods for distributed updating of an ad hoc network are disclosed. For example, in one aspect, the present apparatus and methods may be directed to information exchange for the purpose of distributed updating of an ad hoc network (e.g., distributed coverage and capacity optimization (CCO)), and/or to the semantics of the exchanged information, and/or information to be exchanged for computing, as described in detail above with reference to FIG. 4 .

CCO effectively manages the trade-off between coverage and capacity to assist operators in dealing with dynamic traffic distribution, design failures, and real-world network operating constraints. For example, radio frequency (RF) parameters of a base station play a key role in radio access network (RAN) performance, capacity and coverage, and ultimately, quality of experience (QoE) for users. Network performance is affected not only by suboptimal planning, but also by dynamic radio environments, and therefore radio parameters should be updated or adjusted dynamically. To assist this situation, 3GPP introduced the CCO use case for networks. The CCO identifies coverage holes and high overlaps, and automatically performs corrective actions by adjusting the radio control parameters of the base stations.

In one aspect, the present disclosure provides methods and apparatus for distributed updates of ad hoc networks. For example, a base station may update one or more network parameters at the base station based on feedback received from network entities and local information at the base station. Feedback received at the network entity may be determined at the network entity based on a portion of data transmitted from one or more base stations to the network entity.

For example, in an aspect, the feedback received at the base station from the network entity may include minimum values, maximum values, or ranges of values for one or more network parameters of the base station. For example, the network entity may determine poor coverage areas, and may determine a lower limit (eg, a minimum value) of transmit power for the base station at which the base station provides adequate coverage. The base station may update one or more network parameters based on the lower limit value received from the network entity and other local information available at the base station to determine an appropriate transmit power for the base station.

As illustrated in FIG. 9 , system 900 includes a plurality of base stations 922, 924, and/or 926 that serve UEs 942, 944, and/or 946, respectively, and that each include a distributed update system for performing the functions described herein. Manager 1002. For example, in an aspect, distributed update manager 1002 can be configured to exchange information between base stations 922, 924, and/or 926 for CCO purposes. In an aspect, base stations 922, 924, and/or 926 directly exchange information regarding long-term coverage statistics in the cells in which they operate. In this regard, these statistics reflect measurements collected by base stations 922, 924, and/or 926 and/or by wireless terminals 942, 944, and/or 946 connected to cells operated by base stations 922, 924, and/or 926.

For example, in an aspect regarding information exchange, the distributed update manager 1002 may include specific messages (e.g., CSI - coverage statistics, which is the information in the generic name used herein). In an aspect, the distributed update manager 1002 may exchange information via any of a variety of mechanisms, including, for example, periodically (where the period may be configurable by the network operator), by base station request, and/or by a specific configurable Configure event triggering (eg, when the load on the base station or cell exceeds a certain threshold, etc.).

In one aspect, with respect to semantics, it should be noted that the distributed update manager 1002 can cause base stations to exchange coverage-related statistics reflecting any of a variety of characteristics. For example, in one aspect, such statistics may reflect one or more of: downlink/uplink coverage quality in a cell, received downlink/uplink power, received downlink / Uplink interference power, downlink interference power received from a particular neighbor, UE transmit power level, cell geometry, and/or path loss in the cell.

In a further aspect, the distributed update manager 1002 can use internal base station measurements and/or UE measurement report messages (MRMs) to compute coverage related statistics, where the time scale for computing these statistics is configurable by the network operator. For example, in one aspect, coverage-related statistics may be computed over a sufficiently long period of time to cover any of a variety of changes, including, for example, one or more of: UE geographic distribution changes, serving cell and neighbor cell Load changes, and/or UE mobility patterns change.

In an aspect, each distributed update manager 1002 can include a standardized mechanism for computing coverage statistics exchanged between base stations. For example, the definition of each statistic that is exchanged can be standardized. However, in an alternative or in addition, methods for calculating one or more coverage statistics may not be standardized. For example, in one aspect, average cell geometry can be defined as a number between 0 and 1, where lower numbers are associated with lower geometries. For this aspect, the base station may then simply indicate, through operation of the distributed update manager 1002, that its average geometry is 0.5, without indicating how the average geometry was calculated. Similarly, a base station operating cell 'i' may declare an interference coefficient IC _i,j to describe the level of interference received in cell i from cell j (e.g., IC _i,j = 0.5), without specifying that it is How is it calculated. In this case, the semantics (eg, meaning) of each statistic and its range (eg, 0 to 1) can be normalized.

For example, a base station operating the distributed update manager 1002 can compute coverage statistics from internal measurements and/or UE MRM, as described above. Additionally, a base station operating the distributed update manager 1002 can configure UEs served by the base station to collect and report measurements of signal quality. In an aspect, the UE can measure and report the signal quality of the serving cell as well as the neighbor cells. For example, the base station may configure the UE to measure and report one or more of the following: reference signal received power (RSRP) level of the serving cell and/or neighbor cell, reference signal of the serving cell and/or neighbor cell Received Quality (RSRQ) levels, Radio Signal Strength Indication (RSSI) levels, UE transmit power levels, and other measurements specified by specific protocols (eg, 3GPP TS 36.423). Also, note that these measurement reports can be configured to be periodic and/or triggered.

Referring to FIG. 10 , an example distributed update manager 1002 in aspects of the present disclosure is illustrated.

In one aspect, the distributed update manager 1002 can be configured for distributed updates of an ad hoc network. For example, in one aspect, each of base stations 922, 924, and/or 926 may be configured to include distributed update manager 1002. In additional aspects, the distributed update manager 1002 (of the base stations 922 , 924 and/or 926 ) can be configured to further include a data transmitting component 1004 , a feedback receiving component 1006 and/or a parameter updating component 1008 .

In an aspect, data transmitting component 1004 can be configured to transmit data collected at the base station to a network entity. For example, data transfer component 1004 may include or interface with a transceiver or transmitter, and/or may include software or firmware executed by a processor, and/or may include a specially programmed processor module. For example, in an aspect, data transmitting component 1004 can be configured to transmit data collected at base station 922 to network entity 910 . In additional aspects, data transmitting component 1004 can be configured to transmit data collected at base stations 924 and/or 926 to network entity 910 . As described above with reference to FIG. 9, the data collected at base stations 922, 924, and/or 926 may include coverage statistics from internal measurements at the base station and/or received from the UE's MRM.

For example, in an aspect, data collected at the base stations can be received at the base stations from user equipment (UE) (eg, UE 942, 944, and/or 946) that can be in communication with the base stations. In additional aspects, the base station can be a small cell or a macro cell, and/or a combination of both. In additional example aspects, network entity 910 may include a central server that receives data transmitted from base stations in an ad hoc network.

In an aspect, data received from a UE in communication with a base station may contain thousands of signaling reports. In an alternative or additional aspect, it should be noted that data received at a base station may include data from one or more neighboring base stations received from a UE in communication with the one or more neighboring base stations. In an aspect, the base station can consolidate data received from the UEs (eg, signaling reports) and transmit at least a portion of that data to network entity 910 (eg, a central server). For example, in an additional aspect, the base station may generate a representation, aggregation, or mathematical function of the data (e.g., an average of signaling information received from the UE and/or neighboring base stations) and send the representation, aggregation, or mathematical function of the data to the network entity 910. or math functions. For example, this may allow the network entity to have a network-wide field of view rather than a localized or limited field of view maintained by the base stations in the SON. For example, in one aspect, the network-wide field of view maintained by network entity 910 may be on the order of 15 minutes and/or up to twenty-four hours of data, and the duration of the network-wide field of view may be at network entity 910 The location can be configured by the network operator, for example.

In an aspect, the feedback receiving component 1006 can be configured to receive feedback associated with the network parameter(s) of the base station from the network entity, wherein the feedback received from the network entity is based at the network entity on the basis of information from the one or more It is determined by the data transmitted by a base station to the network entity. In an aspect, network entity 910 can determine feedback for a base station (eg, 922) based on data communicated to the network entity from the base station (eg, 922). In an additional aspect, the network entity may also consider data received from other base stations (eg, 924 and/or 926) to determine feedback for that base station (eg, 922). For example, in one aspect, feedback receiving component 1006 may comprise or interface with a transceiver or receiver, and/or may comprise software or firmware executed by a processor, and/or may comprise a specially programmed processor module. For example, in an aspect, feedback received from network entity 910 can be associated with one or more network parameters of a base station (eg, base station 922). In an example aspect, the network parameters can include one or more of: transmit power of the base station, antenna downtilt at the base station, and frequency reuse factor at the base station.

For example, in an aspect, network entity 910 can identify coverage gaps in an ad hoc network based on data transmitted by the base stations in accordance with the minimization drive test (MDT) procedure defined in the 3GPP specification. In an additional aspect, network entity 910 may determine a minimum threshold for a network parameter of a base station and communicate the minimum threshold to the base station. For example, in an aspect, base station 922 can receive feedback from network entity 910 to update the base station's transmit power by a minimum value (eg, 200 mW) to address coverage gap issues. In an optional or additional aspect, base station 922 may update the transmit power of base station 922 at or above a minimum threshold received from network entity 910 .

In an aspect, parameter updating component 1008 can be configured to update the one or more network parameters at the base station based at least on feedback received from the network entity and local information at the base station. For example, parameter update component 1008 may include or interface with a processor, and/or may include software or firmware executed by a processor, and/or may include a specially programmed processor module. For example, in an aspect, parameter updating component 1008 can be configured to update one or more network parameters at base station 922 (e.g., the transmit power of the base station) based at least on feedback received from network entity 910 and local information available at base station 922. , antenna downtilt, and/or frequency reuse factor).

For example, base station 922, via operation of parameter update component 1008, may update the transmit power of base station 922 based on additional data that may be locally available at base station 922, as it may not be possible that all data available at the base station will be communicated to network entity 910, to alleviate any bandwidth and/or processing power issues at the base station and/or the network entity.

In an aspect, local information can include pilot contamination information at the base station. For example, the pilot pollution information may include the number of UEs reporting a number of strong interferers (eg, relatively stronger than the serving cell 922 by about, eg, 5 dB or a configurable threshold). In an additional aspect, the local information can include the number of call failures and/or handover failures measured at the serving base station. For example, if the number of call failures and/or handoff failures at the base station 922 is high (e.g., above a configurable threshold), the call failure and/or handover failure reasons may be determined from available local information, and the call failure and/or handover failure reasons may be and/or handover failure due to reduced power at the base station (eg, base station 922) in the presence of increased interference. In an optional aspect, if another base station that satisfies the serving cell selection criteria is unavailable, the power of that base station (eg, base station 922) is not reduced.

In one aspect, if there are several base stations (e.g., small cells) in a small coverage area of a SON, it is expected that only some of the small cells of the SON transmit at their maximum power and these small cells of the SON The remaining small cells in the cell transmit at lower power (but equal to or greater than the minimum threshold received from the network entity) to reduce interference and/or improve SINR values. In additional aspects, once a base station (e.g., small cell) receives a minimum threshold for a network parameter from the network entity, the small cell can operate parameter update component 1008 to further optimize additional parameters (e.g., SINR and/or throughput capacity), which can ultimately lead to a better user experience.

For example, in an aspect, if the antenna at a base station (eg, base station 922) is tilted downward, the base station can create strong beams and can localize coverage in the area. However, the overall coverage area of the base station may be reduced. Alternatively, the base station coverage area may be higher if the base station (eg, base station 922) has an antenna that is tilted upward or toward the horizon. However, this may lead to increased interference with other base stations and/or UEs. For example, the base station (e.g., base station 922) may receive feedback comprising a minimum value for the antenna downtilt parameter, and the base station operating parameter updating component 1008 may update the downtilt parameter to A value equal to or higher than this minimum value.

In another example aspect, a base station (eg, base station 922) can receive feedback from network entity 910 that includes a minimum frequency reuse parameter, which can include a frequency reuse factor. In this case, the base station is operable to update parameter updating component 1008 to update the frequency reuse factor by equal to or greater than the minimum frequency reuse factor based on information locally available at the base station.

In an additional aspect, the feedback including frequency reuse parameters can include a fragmented frequency reuse (FFR) configuration that can further include assignment of specific prioritized frequency blocks at different base stations. In an additional aspect, the soft FFR can include the assignment of specific prioritized frequency blocks at different base stations, where each prioritized block in the base station has a different transmit power limit. For example, a higher FFR factor may result in better coverage at the base station, but the base station must consider the higher interference that comes with a higher reuse factor, and choose a value that balances the two.

In an additional aspect, when the base station receives feedback including a range of network parameter values, the range may include a lower bound and/or upper bound for a frequency reuse factor, a prioritized frequency block number limit for FFR or an ordered list of prioritized frequency blocks , and/or transmit power level limits that vary by frequency block.

For example, in additional aspects, each UE's SINR, data rate, traffic conditions, specific location (e.g., near the center or edge of a base station) may be known locally at the base station and/or updated at the operating parameter update component 1008. Network parameters at the base station are taken into account for the distributed update of the ad hoc network.

In an additional aspect, the feedback received from the network entity for changing one or more network parameters at one or more base stations may include the corresponding network The minimum value and/or range of values for the parameter.

FIG. 11 illustrates an example methodology 1100 for distributed updates of an ad hoc network. In an aspect, at block 1102, the methodology 1100 can include transmitting, via a transmitting component at the base station, to a network entity, a portion of the data collected at the base station, where the data collected at the base station was obtained by the base station from a communication with one or The plurality of base stations is received by one or more user equipments (UEs) in communication, where the base station is one of the one or more base stations. For example, in an aspect, base stations 922 , 924 , and/or 926 can operate distributed update manager 1002 and/or data transfer component 1004 to transfer data collected at the base station to network entity 910 .

Further, at block 1104, the methodology 1100 may include receiving, from the network entity, feedback associated with one or more network parameters of the base station, wherein the feedback received from the network entity is at the network entity based at least on the basis of the determined by the portion of data transmitted by one or more base stations to the network entity. For example, in an aspect, base stations 922, 924, and/or 926 can operate distributed update manager 1002 and/or feedback receiving component 1006 to receive feedback from network entity 910 associated with one or more network parameters of the base station. For example, in an aspect, the network parameters can include transmit power of the base station, antenna downtilt at the base station, and/or frequency reuse factor of the base station.

Additionally, at block 1106, methodology 1100 can include updating the one or more network parameters at the base station based on feedback received from the network entity and local information at the base station. For example, in an aspect, base stations 922, 924, and/or 926 are operable to operate distributed update manager 1002 and/or feedback update component 1008 to update updates at the base station based on feedback received from the network entity and local information at the base station. The one or more network parameters of .

Referring to FIG. 12, an example system 1200 for distributed updating of an ad hoc network is shown. For example, system 1200 can reside at least partially within a base station (eg, base stations 922, 924, and/or 926 (FIG. 9)). It is to be appreciated that system 1200 is represented as including functional blocks, which can be functional blocks that represent functions implemented by a processor, software, or combination thereof (eg, firmware). System 1200 includes a logical grouping 1202 of electrical components that can act in conjunction. In one aspect, logical grouping 1202 can include an electrical component 1204 for communicating to a network entity a portion of the data collected at the base station, where the data collected at the base station was obtained by the base station from communications with one or more base stations. received by one or more user equipments (UEs), where the base station is one of the one or more base stations. In an aspect, electrical component 1204 can include data transfer component 1004 (FIG. 10).

Further, logical grouping 1202 can include an electrical component 1206 for receiving, from the network entity, feedback associated with one or more network parameters of the base station, wherein the feedback received from the network entity is at the network entity based at least on The portion of the data transmitted by the one or more base stations to the network entity is determined. For example, in one aspect, electrical component 1206 can include feedback receiving component 1006 (FIG. 10).

Furthermore, logical grouping 1202 can include an electrical component 1208 for updating the one or more network parameters at the base station based on feedback received from the network entity and local information at the base station. For example, in an aspect, electrical component 1208 can include parameter update component 1008 (FIG. 10).

Additionally, system 1200 may include memory 1210 that retains instructions for performing functions associated with electrical components 1204, 1206, and 1208, stores data used or obtained by electrical components 1204, 1206, and 1208, and the like. Although shown as being external to memory 1210 , it should be understood that one or more of electrical components 1204 , 1206 , and 1208 may reside within memory 1210 . In one example, electrical components 1204, 1206, and 1208 may include at least one processor, or each electrical component 1204, 1206, and 1208 may be a corresponding module of at least one processor. Furthermore, in an additional or alternative example, electrical components 1204, 1206, and 1208 can be a computer program product comprising a computer readable medium, where each electrical component 1204, 1206, and 1208 can be corresponding code.

Referring next to FIG. 13 , an example network that facilitates distributed updating of an ad hoc network is provided. As illustrated, network 1300 includes a plurality of cells 1310, 1320, 1330, 1340, 1350, 1360, 1370, which are respectively controlled by base stations 1312, 1322, 1332, 1342, 1352, 1362, 1372 (which may be The base stations 922, 924 and/or 926) that operate the distributed update manager 1002 serve. In one aspect, the coverage statistics ascertained by any of the base stations 1312, 1322, 1332, 1342, 1352, 1362, 1372 are obtained by analyzing the MRM data provided by any of the wireless terminals 1380, 1382, 1384, 1386. to calculate. For example, statistics computed by eNBs and exchanged with other eNBs may be direct aggregations of measurements reported by UEs in MRM. For example, such calculations may include average/maximum/minimum reported RSRP/RSRQ/RSSI for the serving cell, average/maximum/minimum reported RSRP/RSRQ/RSSI for each neighbor, and/or average/maximum/minimum transmit power.

In a further aspect, statistics computed by eNBs and exchanged with other eNBs may also be obtained by further analyzing the MRM. For this particular aspect, such calculations may reflect, for example, the Average cell geometry, the average path loss in that cell, the average signal-to-noise ratio requirement for UEs in that cell, and/or the interference coefficient for each neighbor . Example calculations for such parameters could include:

Referring next to FIG. 14 , an exemplary communication system 1400 implemented in accordance with various aspects is provided that includes a plurality of cells: base stations I and M (which may be base stations 922, 924 and/or operable to operate distributed update manager 1002 ), respectively. or 926) Serving Cell I 1402, Cell M 1404. Note here that the neighbor cells 1402, 1404 overlap slightly - as indicated by the cell border region 1468, thereby creating the potential for signal interference between signals transmitted by base stations in the neighbor cells. Each cell 1402, 1404 of system 1400 includes three sectors. According to various aspects, cells that are not subdivided into multiple sectors (N=1), cells with two sectors (N=2), and cells with more than three sectors (N>3 ) are also possible. Cell 1402 includes a first sector - sector I 1414 , a second sector - sector II 1412 , and a third sector - sector III 1414 . Each sector 1414, 1412, and 1414 has two sector boundary regions; each boundary region is shared between two adjacent sectors.

Sector boundary regions provide the potential for signal interference between signals transmitted by base stations in adjacent sectors. Line 1416 represents the sector boundary region between sector I 1414 and sector II 1412; line 1418 represents the sector boundary region between sector II 1412 and sector III 1414; line 1420 represents the sector boundary region between sector III 1414 and sector Sector boundary area between I 1414. Similarly, Cell M 1404 includes a first sector - Sector I 1422 , a second sector - Sector II 1424 , and a third sector - Sector III 1426 . Line 1428 represents the sector boundary region between sector I 1422 and sector II 1424; line 1430 represents the sector boundary region between sector II 1424 and sector III 1426; line 1432 represents the sector boundary region between sector III 1426 and sector The sector boundary area between I 1422. Cell I 1402 includes a base station (BS), base station I 1406 , and a number of end nodes (EN) in each sector 1414 , 1412 , 1414 . Sector I 1414 includes EN(1) 1436 and EN(X) 1438 coupled to BS 1406 via wireless links 1440, 1442, respectively; sector II 1412 includes EN( 1') 1444 and EN(X') 1446; Sector III 1414 includes EN(1") 1452 and EN(X") 1454 coupled to BS 1406 via wireless links 1456, 1458, respectively. Similarly, cell M 1404 includes base station M 1408 and a number of end nodes (EN) in each sector 1422 , 1424 , 1426 . Sector I 1422 includes EN(1) 1436' and EN(X) 1438' coupled to BS M 1408 via wireless links 1440', 1442', respectively; sector II 1424 includes EN(1') 1444' and EN(X') 1446' to BS M 1408; sector 3 1426 includes EN(1") 1452' and EN(1") 1452' coupled to BS 1408 via wireless links 1456', 1458', respectively (X') 1454.

System 1400 also includes a network node 1460 coupled to BS I 1406 and BS M 1408 via network links 1462, 1464, respectively. Network node 1460 is also coupled to other network nodes, such as other base stations, AAA server nodes, intermediate nodes, routers, etc., and the Internet via network link 1466. Network links 1462, 1464, 1466 may be, for example, fiber optic cables. Each end node (eg, EN 1 1436) may be a wireless terminal that includes a transmitter and a receiver. A wireless terminal (eg, EN(1) 1436) can move within system 1400 and can communicate via a wireless link with a base station in the cell in which the EN is currently located. Wireless terminals (WTs) (eg, EN(1) 1436) may communicate with peer nodes (eg, other WTs in system 1400 or outside system 1400) via base stations (eg, BS 1406) and/or network nodes 1460. A WT (eg, EN(1) 1436) may be a mobile communication device such as a cellular telephone, a personal data assistant with a wireless modem, or the like. The respective base station performs tone subset allocation for the stripe symbol period using a different method than for allocating tones and determining tone hopping in the remaining symbol periods, eg, non-stripe symbol periods. The wireless terminals use this tone subset allocation method along with information received from the base station (eg, base station ramp ID, sector ID information) to determine the tones they can employ to receive data and information at a particular strip symbol period. A tone subset allocation sequence is constructed in accordance with various aspects to apportion inter-sector and inter-cell interference onto corresponding tones. Although the subject system is primarily described in the context of a cellular mode, it should be understood that multiple modes are available and may be employed in accordance with the various aspects described herein.

15 illustrates an example base station 1500, which may be base station 922, 924, and/or 926 operable with distributed update manager 1002, in accordance with various aspects. Base station 1500 implements a tone subset assignment sequence, wherein a different tone subset assignment sequence is generated for each different sector type of the cell. Base station 1500 may be used as any of base stations 1322, 1324, and/or 1326 in system 900 of FIG. 9, and/or base stations 1406 and/or 1408 in system 1400 of FIG. The base station 1500 includes a receiver 1502, a transmitter 1504, a processor 1506 (e.g., a CPU), an input/output interface 1508, and a memory 1510 coupled together via a bus 1509. Exchange data and information online.

Sectorized antenna 1503 coupled to receiver 1502 is used to receive data and other signals (eg, channel reports) from wireless terminal transmissions from each sector within the base station's cell. Sectorized antenna 1505 coupled to transmitter 1504 is used to transmit data and other signals, such as control signals, pilot signals, beacons, to wireless terminals 1200 (see FIG. 12 ) within each sector of the cell of the base station. signal etc. In various aspects, base station 1500 can employ multiple receivers 1502 and multiple transmitters 1504, eg, a separate receiver 1502 per sector and a separate transmitter 1504 per sector. Processor 1506 may be, for example, a general-purpose central processing unit (CPU). Processor 1506 controls the operation of base station 1500 under the direction of one or more routines 1518 stored in memory 1510 and implements the methods. I/O interface 1508 provides connections to other network nodes, thereby coupling BS 1500 to other base stations, access routers, AAA server nodes, etc., other networks, and the Internet. Memory 1510 includes routines 1518 and data/information 1520 .

Data/information 1520 includes data 1536, tone subset assignment sequence information 1538 including downlink strip symbol time information 1540 and downlink tone information 1542, and includes multiple wireless terminal (WT) information sets - WT 1 information 1546 and WT N information 1560 - WT data/information 1544. Each set of WT information (eg, WT 1 information 1546 ) includes data 1548 , terminal ID 1550 , sector ID 1552 , uplink channel information 1554 , downlink channel information 1556 , and mode information 1558 .

Routine 1518 includes communication routine 1522 and base station control routine 1524 . The base station control routines 1524 include a scheduler module 1526 and signaling routines 1528, which include a tone subset assignment routine 1530 for the stripe symbol period, a tone subset assignment routine 1530 for the remaining symbol periods (e.g. Other downlink tone allocation hopping routine 1532, and beacon routine 1534.

Data 1536 includes data to be transmitted to be sent to encoder 1514 of transmitter 1504 for encoding prior to transmission to the WT, as well as data received from the WT that has been processed by decoder 1512 of receiver 1502 after receipt. Downlink strip symbol timing information 1540 includes frame synchronization structure information, such as superslot, beacon slot, and ultraslot structure information, and specifies whether a given symbol period is a strip symbol period - and if so information specifying the index of the strip symbol period and whether the strip symbol is a reset point for truncating the tone subset assignment sequence used by the base station. Downlink tone information 1542 includes information including the carrier frequency assigned to base station 1500, the number and frequency of tones, and the set of tone subsets to be assigned to the strip-symbol period, as well as information such as slope, slope index, and sector Other cell and sector specific values such as cell type.

Data 1548 may include data that WT1 1200 has received from peer nodes, data that WT1 1200 desires to transmit to peer nodes, and downlink channel quality report feedback information. Terminal ID 1550 is an ID assigned by base station 1500 to identify WT 1 1200 . Sector ID 1552 includes information identifying the sector in which WT1 1200 is operating. Sector ID 1552 may be used, for example, to determine the sector type. Uplink channel information 1554 includes information identifying channel segments that have been allocated by scheduler 1526 for use by WT1 1200, such as uplink traffic channel segments for data, dedicated uplinks for requests, power control, timing control, etc. Link Control Channel. Each uplink channel assigned to WT1 1200 includes one or more logical tones, each logical tone following an uplink frequency hopping sequence. Downlink channel information 1556 includes information identifying channel segments that have been allocated by scheduler 1526 to carry data and/or information to WT1 1200 (eg, downlink traffic channel segments for user data). Each downlink channel assigned to WT1 1200 includes one or more logical tones each following a downlink hopping sequence. Mode information 1558 includes information identifying the operational state of WT1 1200 (eg, sleep, hold, on).

The communication routine 1522 controls the base station 1500 to perform various communication operations and implement various communication protocols. Base station control routines 1524 are used to control base station 1500 to perform basic base station functional tasks (e.g., signal generation and reception, scheduling, etc.) to transmit signals to wireless terminals.

Signaling routine 1528 controls the operation of receiver 1502 and its decoder 1512 and transmitter 1504 and its encoder 1514 . Signaling routine 1528 is responsible for controlling the generation of transmitted data 1536 and control information. The tone subset allocation routine 1530 uses the method of this aspect and uses the data/information 1520 including the downlink stripe symbol time information 1540 and the sector ID 1552 to construct the subset of tones to be used in the stripe symbol period. The downlink tone subset assignment sequence is different for each sector type in a cell, and is also different for adjacent cells. WT 1200 receives the signal in a strip symbol period according to the downlink tone subset assignment sequence; base station 1500 uses the same downlink tone subset assignment sequence to generate the transmitted signal. Other downlink tone assignment hopping routine 1532 uses information including downlink tone information 1542 and downlink channel information 1556 to construct downlink tone hopping for symbol periods other than the strip symbol periods sequence. The downlink data tone hopping sequence is synchronized across sectors of the cell. Beacon routine 1534 controls the transmission of beacon signals (e.g., signals with relatively high power signals concentrated on one or a few tones), which may be used for synchronization purposes, such as for synchronizing downlinks with respect to pole slot boundaries The frame timing structure of the signal and thus the synchronization tone subset allocation sequence.

16 illustrates an example wireless terminal (end node) 1600 that may be used as any of the wireless terminals (end nodes) (e.g., EN(1) 1436) of the system 1400 shown in FIG. 14 , which may be UE 942 , 044 and/or 946 in communication with base station 922 , 924 and/or 926 operable distributed update manager 1002 . In an aspect, EN(1) 1436 may be UE 1342, 1344, and/or 1346. Wireless terminal 1600 implements a tone subset assignment sequence. The wireless terminal 1600 includes a receiver 1602 including a decoder 1616, a transmitter 1604 including an encoder 1614, a processor 1606, and a memory 1608 coupled together by a bus 1610 on which the individual elements 1602, 1604, 1606, 1608 can be Exchange data and information. An antenna 1603 for receiving signals from base stations (and/or alien wireless terminals) is coupled to receiver 1602 . An antenna 1605 is coupled to the transmitter 1604 for transmitting signals, eg, to a base station (and/or to alien wireless terminals).

Processor 1606 (eg, CPU) controls the operation of wireless terminal 1600 and implements various methods by executing routines 1620 in memory 1608 and using data/information 1622 in memory 1608 .

Data/information 1622 includes user data 1634 , user information 1636 , and tone subset allocation sequence information 1650 . User data 1634 may include data intended for peer nodes to be routed to encoder 1614 for encoding prior to transmission by transmitter 1604 to the base station, as well as data received from the base station that has been decoded in receiver 1602 The data processed by the device 1616. User information 1636 includes uplink channel information 1638 , downlink channel information 1640 , terminal ID information 1642 , base station ID information 1644 , sector ID information 1646 , and mode information 1648 . Uplink channel information 1638 includes information identifying uplink channel segments that have been assigned by the base station to wireless terminal 1600 for use in transmitting to the base station. Uplink channels may include uplink traffic channels, dedicated uplink control channels (eg, request channels, power control channels, and timing control channels). Each uplink channel includes one or more logical tones, and each logical tone follows an uplink tone hopping sequence. The uplink hopping sequence is different between each sector type of a cell and between adjacent cells. Downlink channel information 1640 includes information identifying downlink channel segments that have been assigned by the base station to WT 1600 for use when the base station transmits data/information to WT 1600 . Downlink channels may include downlink traffic channels and assignment channels, each downlink channel including one or more logical tones, each logical tone being synchronized between each sector of the cell following downlink hopping sequence.

Subscriber information 1636 also includes terminal ID information 1642 (which is a base station assigned identity), base station ID information 1644 identifying the particular base station with which the WT has established communication, and identifying the particular sector within the cell where the WT 1600 is currently located. Sector ID information 1646. The base station ID 1644 provides the cell ramp value and the sector ID information 1646 provides the sector index type; the cell ramp value and sector index type can be used to derive the tone hopping sequence. Mode information 1648, also included in user information 1636, identifies whether WT 1600 is in sleep mode, hold mode, or on mode.

Tone subset allocation sequence information 1650 includes downlink strip symbol time information 1652 and downlink tone information 1654 . Downlink strip symbol timing information 1652 includes frame synchronization structure information (such as superslot, beacon slot, and pole slot structure information), and designates whether a given symbol period is a strip symbol period—and if so In this case, information specifying the index of the strip symbol period and whether the strip symbol is a reset point for truncating the tone subset allocation sequence used by the base station. Downlink tone information 1654 includes information including the carrier frequency assigned to the base station, the number and frequency of tones, and the set of subsets of tones to be assigned to the strip-symbol period, as well as other cell- and sector-specific values (such as slope, slope index and sector type).

Routine 1620 includes communication routine 1624 and wireless terminal control routine 1626 . Communication routine 1624 controls the various communication protocols used by WT 1600. Wireless terminal control routines 1626 control basic wireless terminal 1600 functions, including control of receiver 1602 and transmitter 1604 . Wireless terminal control routines 1626 include signaling routines 1628 . Signaling routines 1628 include tone subset allocation routines 1630 for the strip symbol periods and other downlink tone allocation hopping routines 1632 for the remaining symbol periods (eg, non-strip symbol periods). Tone subset allocation routine 1630 uses user data/information 1622 including downlink channel information 1640, base station ID information 1644 (e.g., slope index and sector type), and downlink tone information 1654 to generate downlink The link tone subset allocates sequences and processes received data transmitted from the base station. Other downlink tone assignment hopping routine 1630 uses information including downlink tone information 1654 and downlink channel information 1640 to construct downlink tone hopping for symbol periods other than the strip symbol periods sequence. Tone subset assignment routine 1630, when executed by processor 1606, is used to determine when and on which tones wireless terminal 1600 receives one or more bar symbol signals from base station 1500. The uplink tone allocation hopping routine 1630 uses the tone subset allocation function along with information received from the base station to determine the tones on which to transmit.

In one or more example aspects, the 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 may include RAM, ROM, EEPROM, CD-ROM, or other optical disk storage, magnetic disk storage, or other magnetic storage devices, or other desired program code and any other medium that can be accessed by a computer. Any connection is also properly termed a computer-readable medium. For example, if the software is transmitted from a web site, server, or other remote source using 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 media. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks are often reproduced magnetically. data, while a disc (disc) uses laser light to reproduce data optically. Combinations of the above should also be included within the scope of computer-readable media.

When these aspects are implemented in program code or code segments, it should be understood that the code segments can represent procedures, functions, subroutines, procedures, routines, subroutines, modules, software packages, classes, or instructions, data structures, or any combination of program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or communicated using any suitable means, including memory sharing, message passing, token passing, network transmission, and the like. Additionally, in some aspects, the steps and/or actions of a method or algorithm may reside as one of code and/or instructions, or any combination or collection thereof, on a machine-readable medium that may be incorporated into a computer program product and/or on a computer on readable media.

For a software implementation, the techniques described herein can be implemented with modules (eg, procedures, functions, and so on) that perform the functions described herein. The software codes may be stored in memory units and executed by processors. The memory unit can be implemented within the processor or external to the processor, in which case it can be communicatively coupled to the processor via various means as is known in the art.

For hardware implementation, each processing unit can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays ( FPGA), processors, controllers, microcontrollers, microprocessors, other electronic units designed to perform the functions described herein, or combinations thereof.

What has been described above includes examples of one or more aspects. It is, of course, not possible to describe every conceivable combination of components or methodology for purposes of describing the foregoing aspects, but those of ordinary skill in the art will recognize that many further combinations and permutations are possible. Accordingly, the described aspects are intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. Also, to the extent that the term "comprises" is used in the detailed description or the claims, the term is intended to be interpreted in a manner similar to that in which the term "comprises" is used as a transitional word in the claims. Can be both solutions.

As used herein, the term "inference" or "inference" generally refers to the process of inferring or inferring the state of a system, environment, and/or user from a set of observations captured via events and/or data. For example, inference can be employed to identify a specific context or action, or a probability distribution over states can be generated. Inference can be probabilistic—that is, computing a probability distribution over states of interest based on a consideration of data and events. Inference can also refer to techniques employed for composing higher-level events from a set of events and/or data. Such inference results in the construction of new events or actions from a set of observed events and/or stored event data, whether or not these events are closely related in temporal proximity, and regardless of whether the events and data originate from one or Several events and data sources.

As used in this application, the terms "component," "module," "system" and the like mean a computer-related entity, whether hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being limited to, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. As an illustration, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process and/or thread of execution, and a component can be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. Components can communicate by means of local and/or remote processes, such as in accordance with a signal having one or more data packets (e.g., from interacting with another component in a local system, a distributed system, and and/or data of a component that interacts with other systems over a network such as the Internet) to conduct this communication.

Claims (22)

1. A method for distributed updating of an ad hoc network, comprising: transmitting, via a transmitting component at the base station, a portion of the data collected at the base station to a network entity, wherein the data collected at the base station was obtained by the base station from one or more users in communication with one or more base stations received by an equipment (UE), wherein the base station is one of the one or more base stations; Feedback associated with one or more network parameters of the base stations is received from the network entity, wherein the feedback received from the network entity is at the network entity based at least on the basis of sending from the one or more base stations to the said portion of data transmitted by said network entity, and wherein said feedback associated with said one or more network parameters comprises at least one of the following for each of said one or more network parameters or: minimum, maximum, and range; and The one or more network parameters at the base station are updated based on feedback received from the network entity and local information at the base station. 2. The method according to claim 1, wherein the one or more network parameters comprise at least one of the following: transmit power of the base station, antenna downtilt of the base station, and frequency reuse factor. 3. The method of claim 1, wherein the minimum value for the one or more network parameters is determined by the network entity in response to at least the data transmitted from the one or more base stations. It is determined by detecting a coverage gap in the ad hoc network as described above. 4. The method of claim 1, further comprising setting the transmit power of the base station to a value based on the minimum value and data collected at the base station from the one or more UEs . 5. The method according to claim 4, wherein the data collected at the base station includes one or more of the following: the number of the one or more UEs camped at the base station, the number of UEs camped at the base station, The location of the one or more UEs on the base station, the signal-to-interference and noise ratio (SINR) of the one or more UEs camped on the base station, and the distance between the one or more UEs and the base station path loss. 6. The method of claim 1 , wherein updating the one or more network parameters based on local information at the base station comprises based on pilot contamination, call failure, and handover failure at the base station One or more of the relevant information to update the one or more network parameters. 7. An apparatus for distributed updating of an ad hoc network, comprising: means for communicating to a network entity a portion of data collected at a base station, wherein the data collected at the base station is obtained by the base station from one or more user equipment (UE) in communication with one or more base stations received, wherein the base station is one of the one or more base stations; means for receiving, from the network entity, feedback associated with one or more network parameters of the base station, wherein the feedback received from the network entity is at the network entity based at least on the portion of data transmitted by a base station to the network entity, and wherein the feedback associated with the one or more network parameters includes each of the one or more network parameters At least one of the following: minimum value, maximum value, and range; and means for updating the one or more network parameters at the base station based on feedback received from the network entity and local information at the base station. 8. The apparatus of claim 7, wherein the one or more network parameters comprise at least one of: transmit power of the base station, antenna downtilt of the base station, and a frequency reuse factor. 9. The apparatus of claim 7, wherein the minimum value for the one or more network parameters is determined by the network entity in response to at least the data transmitted from the one or more base stations. It is determined by detecting a coverage gap in the ad hoc network as described above. 10. The apparatus of claim 7, further comprising means for setting the transmit power of the base station based on the minimum value and data collected from the one or more UEs at the base station to A value device. 11. The equipment according to claim 10, wherein the data collected at the base station includes at least one of the following: the number of the one or more UEs camped at the base station, the number of the one or more UEs camped at the base station, The location of the one or more UEs on the base station, the signal-to-interference and noise ratio (SINR) of the one or more UEs camped on the base station, and the path from the one or more UEs to the base station loss. 12. A non-transitory computer-readable medium storing code executable by a computer to: transmitting, via a transmitting component at the base station, a portion of the data collected at the base station to a network entity, wherein the data collected at the base station was obtained by the base station from one or more users in communication with one or more base stations received by an equipment (UE), wherein the base station is one of the one or more base stations; Feedback associated with one or more network parameters of the base stations is received from the network entity, wherein the feedback received from the network entity is at the network entity based at least on the basis of sending from the one or more base stations to the said portion of data transmitted by said network entity, and wherein said feedback associated with said one or more network parameters comprises at least one of the following for each of said one or more network parameters or: minimum, maximum, and range; and The one or more network parameters at the base station are updated based on feedback received from the network entity and local information at the base station. 13. The non-transitory computer-readable medium of claim 12, wherein the one or more network parameters include at least one of: transmit power of the base station, antenna downtilt of the base station, and a frequency reuse factor. 14. The non-transitory computer-readable medium of claim 12, wherein the minimum value for the one or more network parameters is determined by the network entity in response to at least The portion of data transmitted by the base station is determined by detecting a coverage gap in the ad hoc network. 15. The non-transitory computer readable medium of claim 12 , further comprising means for calculating the The transmit power of the base station is set to a value code. 16. The non-transitory computer-readable medium of claim 15 , wherein the data collected at the base station includes at least one of: number, the location of the one or more UEs camped on the base station, the signal-to-interference and noise ratio (SINR) of the one or more UEs camped on the base station, and the one or more UEs Path loss to the base station. 17. An apparatus for distributed updating of an ad hoc network, comprising: a data transfer component for transferring to a network entity a portion of the data collected at the base station, where the data collected at the base station was received by the base station from one or more user equipment in communication with one or more base stations received by (UE), wherein the base station is one of the one or more base stations; a feedback receiving component for receiving feedback associated with one or more network parameters of the base station from the network entity, wherein the feedback received from the network entity is at the network entity based at least on said portion of data transmitted by one or more base stations to said network entity, and wherein said feedback associated with said one or more network parameters includes each of said one or more network parameters at least one of the following network parameters: a minimum value, a maximum value, and a range; and A parameter updating component for updating the one or more network parameters at the base station based on feedback received from the network entity and local information at the base station. 18. The apparatus of claim 17, wherein the parameter updating component is configured to update the one or more network parameters, the one or more network parameters comprising at least one of the following: the base station The transmit power of the base station, the antenna downtilt of the base station, and the frequency reuse factor. 19. The apparatus of claim 17, wherein the minimum value for the one or more network parameters is determined by the network entity in response to at least the data transmitted from the one or more base stations. It is determined by detecting a coverage gap in the ad hoc network as described above. 20. The apparatus of claim 17, wherein the parameter update component is configured to update the base station's The transmit power is updated to a value. 21. The apparatus according to claim 20, wherein the data collected at the base station includes at least one of the following: the number of the one or more UEs camped at the base station, the number of UEs camped at the base station The location of the one or more UEs on the base station, the signal-to-interference and noise ratio (SINR) of the one or more UEs camped on the base station, and the path from the one or more UEs to the base station loss. 22. The apparatus of claim 17, wherein the parameter update component is configured to update the one or more network parameters based on local information at the base station, the local information at the base station comprising Information at the base station related to one or more of pilot contamination, call failure, and handover failure.