SYSTEM AND METHOD OF CONTROLLING NETWORK TRAFFIC USING PREAMBLE DETECTION AND AUTOMATED OPTIMIZATION OF RANDOM ACCESS CHANNEL PARAMETERS
20170374683 · 2017-12-28
Inventors
- Marcos TAVARES (Ocean Township, NJ, US)
- Dirck Uptegrove (Mendham, NJ)
- Dragan SAMARDZIJA (Highlands, NJ, US)
Cpc classification
H04W28/02
ELECTRICITY
H04W74/008
ELECTRICITY
International classification
Abstract
Detecting physical random access channel (RACH) preambles is accomplished by computing a correlation power profile based on received RACH preambles, where the correlation power profile values may be sorted. A weight factor is computed for each of the correlation power profile values based on a normalized RACH detection threshold. Outlier peaks of the correlation power profile values are selected based on the weight factor. The outlier peaks to the first set of RACH signatures are mapped in order to identify a user equipment (UE) that is associated with one of the received RACH preambles. Network traffic is then controlled for network communications associated with the identified UE.
Claims
1. A method of preamble detection to control network traffic in a communication network, comprising: detecting, by at least a first processor of at least a first network node, physical random access channel (RACH) preambles, by performing the steps of, computing a correlation power profile based on a set of received RACH preambles, sorting correlation power profile values, computing a weight factor for each of the correlation power profile values based on a normalized RACH detection threshold, selecting outlier peaks of the correlation power profile values based on the weight factor, mapping the outlier peaks to the first set of RACH signatures in order to identify at least one UE that is associated with one of the received RACH preambles; and controlling, by the first processor, the network traffic of network communications associated with the at least one identified UE.
2. The method of claim 1, wherein the detecting of the RACH preambles is accomplished using a forward consecutive mean excision (FCME) method.
3. The method of claim 1, wherein, the detecting of the RACH preambles further includes, collecting noise rise information and preamble miss information for a set of transmitted RACH preambles, computing an overall average noise rise for the communication network based on the collected noise rise information, computing an average missed detection ratio for the communication network using the collected preamble miss information, determining a target receiver power and a power ramp-up using the average nose rise and the average missed detection ratio.
4. The method of claim 1, wherein, the detecting of the RACH preambles further includes determining the normalized RACH detection threshold by performing the steps of, collecting preamble false alarm ratio information, computing an average false alarm rate for the communication network based on the preamble false alarm ratio information, and determining the normalized RACH detection threshold based on the average false alarm rate, the controlling the network traffic further includes, broadcasting the normalized RACH detection threshold to UEs of the communication network.
5. The method of claim 1, further comprising: collecting a contention ratio information, computing an average contention ratio for the communication network based on the collected contention ratio information, determining the opportunity period based on the average contention ratio, wherein the controlling the network traffic further includes, broadcasting the opportunity period to UEs of the communication network.
6. The method of claim 3, wherein, repeating the steps of collecting noise rise information and preamble miss information, and repeating the steps of computing an overall average noise rise and an average missed detection ratio until the determined target receiver power and the power ramp-up remain constant; and wherein the controlling the network traffic further includes, broadcasting the target receiver power and a power ramp-up to UEs of the communication network; wherein the detecting of the RACH preambles further includes determining the normalized RACH detection threshold, once the determined target receiver power and the power ramp-up remain constant, by performing the steps of, collecting preamble false alarm ratio information, computing an average false alarm rate for the communication network based on the preamble false alarm ratio information, and determining the normalized RACH detection threshold based on the average false alarm rate, wherein the controlling the network traffic further includes, broadcasting the normalized RACH detection threshold to UEs of the communication network.
7. The method of claim 6, further comprising: repeating the steps of collecting preamble false alarm ratio information and computing an average false alarm rate until the determined normalized RACH detection threshold remains constant; and wherein the detecting of the RACH preambles further includes determining an opportunity period, once the determined target receiver power, the power ramp-up, and the normalized RACH detection threshold remain constant, by performing the steps of, collecting a contention ratio information, computing an average contention ratio for the communication network based on the collected contention ratio information, determining the opportunity period based on the average contention ratio, wherein the controlling the network traffic further includes, broadcasting the opportunity period to UEs of the communication network.
8. The method of claim 1, wherein, the at least a first processor of at least a first network node includes a plurality of processors, each of the plurality of the processors being associated with a network node dedicated to a respective sector within the communication network, the detecting of the RACH preambles further includes, each of the processors collecting noise rise information and preamble miss information for a set of transmitted RACH preambles for the respective sector, each of the processors computing an overall average noise rise based on the collected noise rise information for the respective sector, each of the processors computing an average missed detection ratio, for the respective sectors, using the collected preamble miss information from each respective sector, each of the processors sharing the overall average noise rise and the average missed detection ratio with at least one of the other processors, of the plurality of processors, which is a neighbor processor, each of the processors determining a target receiver power and a power ramp-up, for the respective sectors, using the shared average nose rise and the shared average missed detection ratio.
9. The method of claim 8, further comprising: repeating the steps of each of the processors of the respective sectors collecting noise rise information and preamble miss information, and repeating the step of computing an overall average noise rise and an average missed detection ratio until the determined target receiver power and the power ramp-up remain constant; wherein the controlling the network traffic further includes, each of the processors broadcasting the target receiver power and a power ramp-up to UEs for the respective sectors; wherein the detecting of the RACH preambles further includes determining the normalized RACH detection threshold, once the determined target receiver power and the power ramp-up remain constant, by performing the steps of, each of the processors collecting preamble false alarm ratio information for the respective sectors, each of the processor computing an average false alarm rate, for the respective sectors, based on the preamble false alarm ratio information, and each of the processors determining the normalized RACH detection threshold, for the respective sectors, based on the average false alarm rate, wherein the controlling of the network traffic further includes each of the processors broadcasting the normalized RACH detection threshold to UEs for the respective sectors.
10. The method of claim 9, further comprising: repeating the steps of each of the processors of the respective sectors collecting preamble false alarm ratio information and computing an average false alarm rate, until the determined normalized RACH detection threshold remains constant, wherein the detecting of the RACH preambles further includes determining the opportunity period, once the determined normalized RACH detection threshold remains constant, by performing the steps of, each of the processors collecting a contention ratio information for the respective sectors, computing an average contention ratio for the respective sectors based on the collected contention ratio information, each of the processors determining the opportunity period, for the respective sectors, based on the average contention ratio; and wherein the controlling of the network traffic further includes each of the processors broadcasting the target receiver power, the power ramp-up, and the opportunity period to the UEs for the respective sectors.
11. At least a first network node in a communication network, the at least a first network node comprising: at least a first processor, configured to, detect physical random access channel (RACH) preambles, by performing the steps of, computing a correlation power profile based on a set of received RACH preambles, sorting correlation power profile values, computing a weight factor for each of the correlation power profile values based on a normalized RACH detection threshold, selecting outlier peaks of the correlation power profile values based on the weight factor, mapping the outlier peaks to the first set of RACH signatures in order to identify at least one UE that is associated with one of the received RACH preambles; and control network traffic of network communications associated with the at least one identified UE.
12. The at least a first network node of claim 1, wherein the at least a first processor is further configured to detect the RACH preambles by using a forward consecutive mean excision (FCME) method.
13. The at least a first network node of claim 11, wherein, the at least a first processor is further configured to detect the RACH preambles by, collecting noise rise information and preamble miss information for a set of transmitted RACH preambles, computing an overall average noise rise for the communication network based on the collected noise rise information, computing an average missed detection ratio for the communication network using the collected preamble miss information, determining a target receiver power and a power ramp-up using the average nose rise and the average missed detection ratio.
14. The at least a first network node of claim 11, wherein, the at least a first processor is further configured to detect the RACH preambles by determining the normalized RACH detection threshold by performing the steps of, collecting preamble false alarm ratio information, computing an average false alarm rate for the communication network based on the preamble false alarm ratio information, and determining the normalized RACH detection threshold based on the average false alarm rate, the at least a first processor is further configured to control the network traffic by, broadcasting the normalized RACH detection threshold to UEs of the communication network.
15. The at least a first network node of claim 1, wherein the at least a first processor is further configured to, collect a contention ratio information, compute an average contention ratio for the communication network based on the collected contention ratio information, determine the opportunity period based on the average contention ratio, wherein the at least a first processor is further configured to control the network traffic by, broadcasting the opportunity period to UEs of the communication network.
16. The at least a first network node of claim 13, wherein the at least a first processor is further configured to, repeat the steps of collecting noise rise information and preamble miss information, and repeating the steps of computing an overall average noise rise and an average missed detection ratio until the determined target receiver power and the power ramp-up remain constant, wherein the at least a first processor is further configured to control the network traffic by, broadcasting the target receiver power and a power ramp-up to UEs of the communication network, wherein the at least a first processor is further configured to detect the RACH preambles by determining the normalized RACH detection threshold, once the determined target receiver power and the power ramp-up remain constant, by performing the steps of, collecting preamble false alarm ratio information, computing an average false alarm rate for the communication network based on the preamble false alarm ratio information, and determining the normalized RACH detection threshold based on the average false alarm rate, the at least a first processor is further configured to control the network traffic by, broadcasting the normalized RACH detection threshold to UEs of the communication network.
17. The at least a first network node of claim 16, wherein the at least a first processor is further configured to, repeat the steps of collecting preamble false alarm ratio information and computing an average false alarm rate until the determined normalized RACH detection threshold remains constant, wherein the at least a first processor is further configured to detect the RACH preambles by determining an opportunity period, once the determined target receiver power, the power ramp-up, and the normalized RACH detection threshold remain constant, by performing the steps of, collecting a contention ratio information, computing an average contention ratio for the communication network based on the collected contention ratio information, determining the opportunity period based on the average contention ratio, wherein the at least a first processor is further configured to control the network traffic by, broadcasting the opportunity period to UEs of the communication network.
18. The at least a first network node of claim 11, wherein, the at least a first processor includes a plurality of processors, each of the plurality of the processors being associated with a respective sector within the communication network, the at least a first processor is further configured to detect the RACH preambles by, each of the processors collecting noise rise information and preamble miss information for a set of transmitted RACH preambles for the respective sector, each of the processors computing an overall average noise rise based on the collected noise rise information for the respective sector, each of the processors computing an average missed detection ratio, for the respective sectors, using the collected preamble miss information from each respective sector, each of the processors sharing the overall average noise rise and the average missed detection ratio with at least one of the other processors, of the plurality of processors, which is a neighbor processor, each of the processors determining a target receiver power and a power ramp-up, for the respective sectors, using the shared average nose rise and the shared average missed detection ratio.
19. The at least a first network node of claim 18, wherein the at least a first processor is further configured to, repeat the steps of each of the processors of the respective sectors collecting noise rise information and preamble miss information, and repeating the step of computing an overall average noise rise and an average missed detection ratio until the determined target receiver power and the power ramp-up remain constant, wherein the at least a first processor is further configured to control the network traffic by, each of the processors broadcasting the target receiver power and a power ramp-up to UEs for the respective sectors, wherein the at least a first processor is further configured to detect the RACH preambles by determining the normalized RACH detection threshold, once the determined target receiver power and the power ramp-up remain constant, by performing the steps of, each of the processors collecting preamble false alarm ratio information for the respective sectors, each of the processor computing an average false alarm rate, for the respective sectors, based on the preamble false alarm ratio information, and each of the processors determining the normalized RACH detection threshold, for the respective sectors, based on the average false alarm rate, wherein the at least a first processor is further configured to control the network traffic by each of the processors broadcasting the normalized RACH detection threshold to UEs for the respective sectors.
20. The at least a first network node of claim 19, wherein the at least a first processor is further configured to, repeat the steps of each of the processors of the respective sectors collecting preamble false alarm ratio information and computing an average false alarm rate, until the determined normalized RACH detection threshold remains constant, wherein the at least a first processor is further configured to detect the RACH preambles by determining the opportunity period, once the determined normalized RACH detection threshold remains constant, by performing the steps of, each of the processors collecting a contention ratio information for the respective sectors, computing an average contention ratio for the respective sectors based on the collected contention ratio information, each of the processors determining the opportunity period, for the respective sectors, based on the average contention ratio; and wherein the at least a first processor is further configured to control the network traffic by each of the processors broadcasting the target receiver power, the power ramp-up, and the opportunity period to the UEs for the respective sectors.
Description
BRIEF DESCRIPTION OF THE DRAWINGS
[0042] The above and other features and advantages of example embodiments will become more apparent by describing in detail, example embodiments with reference to the attached drawings. The accompanying drawings are intended to depict example embodiments and should not be interpreted to limit the intended scope of the claims. The accompanying drawings are not to be considered as drawn to scale unless explicitly noted.
[0043]
[0044]
[0045]
[0046]
[0047]
[0048]
[0049]
[0050]
[0051]
[0052]
[0053]
[0054]
[0055]
[0056]
[0057]
[0058]
[0059]
[0060]
[0061]
[0062]
[0063]
[0064]
[0065]
[0066]
[0067]
[0068]
[0069]
[0070]
[0071]
[0072]
[0073]
DETAILED DESCRIPTION
[0074] While example embodiments are capable of various modifications and alternative forms, embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that there is no intent to limit example embodiments to the particular forms disclosed, but on the contrary, example embodiments are to cover all modifications, equivalents, and alternatives falling within the scope of the claims. Like numbers refer to like elements throughout the description of the figures.
[0075] Before discussing example embodiments in more detail, it is noted that some example embodiments are described as processes or methods depicted as flowcharts. Although the flowcharts describe the operations as sequential processes, many of the operations may be performed in parallel, concurrently or simultaneously. In addition, the order of operations may be re-arranged. The processes may be terminated when their operations are completed, but may also have additional steps not included in the figure. The processes may correspond to methods, functions, procedures, subroutines, subprograms, etc.
[0076] Methods discussed below, some of which are illustrated by the flow charts, may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware or microcode, the program code or code segments to perform the necessary tasks may be stored in a machine or computer readable medium such as a storage medium, such as a non-transitory storage medium. A processor(s) may perform the necessary tasks.
[0077] Specific structural and functional details disclosed herein are merely representative for purposes of describing example embodiments. This invention may, however, be embodied in many alternate forms and should not be construed as limited to only the embodiments set forth herein.
[0078] It will be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.
[0079] It will be understood that when an element is referred to as being “connected” or “coupled” to another element, it can be directly connected or coupled to the other element or intervening elements may be present. In contrast, when an element is referred to as being “directly connected” or “directly coupled” to another element, there are no intervening elements present. Other words used to describe the relationship between elements should be interpreted in a like fashion (e.g., “between” versus “directly between,” “adjacent” versus “directly adjacent,” etc.).
[0080] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a,” “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and/or “including,” when used herein, specify the presence of stated features, integers, steps, operations, elements and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components and/or groups thereof.
[0081] It should also be noted that in some alternative implementations, the functions/acts noted may occur out of the order noted in the figures. For example, two figures shown in succession may in fact be executed concurrently or may sometimes be executed in the reverse order, depending upon the functionality/acts involved.
[0082] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which example embodiments belong. It will be further understood that terms, e.g., those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
[0083] Portions of the example embodiments and corresponding detailed description are presented in terms of software, or algorithms and symbolic representations of operation on data bits within a computer memory. These descriptions and representations are the ones by which those of ordinary skill in the art effectively convey the substance of their work to others of ordinary skill in the art. An algorithm, as the term is used here, and as it is used generally, is conceived to be a self-consistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of optical, electrical, or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.
[0084] In the following description, illustrative embodiments will be described with reference to acts and symbolic representations of operations (e.g., in the form of flowcharts) that may be implemented as program modules or functional processes include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types and may be implemented using existing hardware at existing network elements. Such existing hardware may include one or more Central Processing Units (CPUs), digital signal processors (DSPs), application-specific-integrated-circuits, field programmable gate arrays (FPGAs) computers or the like.
[0085] It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise, or as is apparent from the discussion, terms such as “processing” or “computing” or “calculating” or “determining” of “displaying” or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical, electronic quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
[0086] Note also that the software implemented aspects of the example embodiments are typically encoded on some form of program storage medium or implemented over some type of transmission medium. The program storage medium may be any non-transitory storage medium such as magnetic (e.g., a floppy disk or a hard drive) or optical (e.g., a compact disk read only memory, or “CD ROM”), and may be read only or random access. Similarly, the transmission medium may be twisted wire pairs, coaxial cable, optical fiber, or some other suitable transmission medium known to the art. The example embodiments not limited by these aspects of any given implementation.
[0087] General Methodology:
[0088] The achievement of optimal random access performance through efficient RACH signature detection algorithms and the correct configuration of the RACH parameters, which may be adapted to diverse situations encountered in practical deployment of cellular networks, may meet at least the following five objectives.
[0089] A) Avoidance of excessive interference on communication channels;
[0090] B) Achievement of an intended RACH coverage;
[0091] C) Minimization of delays related to call setup, handovers, etc.;
[0092] D) Reduction of network signaling overhead related to identification assignments, resource grants, etc.; and
[0093] E) Obtainment of a proper resource allocation balance between random access and other communication needs.
[0094] The five objectives, listed above, may be quantified in terms of metrics, and these metrics are referred to as ‘network metrics’ throughout the remainder of this document. Due to the multi-dimensionality of network problems associated with the simultaneous optimization of several parameters, and due to the dynamic nature of cellular networks (with varying traffic loads and changing interference patterns), automated and adaptive RACH parameter setting methods may assist proper network operations. More specifically, some or all of the following parameters may be optimized via the example embodiment. Throughout the remainder of this document, these parameters are referred to as ‘RACH parameters.’
[0095] 1) RACH initial target receive power P.sub.0,RACH;
[0096] 2) RACH transmit power ramp-up P.sub.ramp,RACH;
[0097] 3) Normalized RACH preamble detection threshold T.sub.RACH;
[0098] 4) RACH resource allocation period τ.sub.RACH.
[0099] Within the context of the example embodiments, the optimization of RACH parameters 1) and 2) may directly affect objectives A), B), C); the optimization of RACH parameter 3) may directly affect objectives C) and D); and the optimization of RACH parameter 4) may directly affect objectives A), C) and E). For this reason, example embodiments provide an adaptive RACH parameter optimization solution that may be designed to handle performance constraints which are concurrently affected by the RACH parameters 1) through 4).
Structural Embodiment
[0100]
[0101]
[0102]
[0103] RACH Signature Detection Method:
[0104] Relevant to the characterization of the RACH signature detection algorithm is a random variable Y (transmitted from adder 117 of
[0105] Where N.sub.RX may be a number of receiver antennas at the eNB 105a and X.sub.k may be assumed to be a complex, zero-mean with variance σ.sup.2.
[0106] Using Equation 1, the distribution of the random variable represented by each Y, may be approximated by a chi-squared distribution with 2N.sub.RX degrees of freedom. After normalization (by making σ.sup.2=1), the cumulative distribution function (CDF) may be written as shown below.
[0107] Assuming that M is a number of metrics to be searched in the correlation power profile represented by Y, a probability that all M metrics are below a normalized threshold value T.sub.RACH may be given by [Q.sub.X.sub.
P.sub.FA=1−[Q.sub.X.sub.
[0108] By setting P.sub.FA to a particular value, T.sub.RACH may be determined numerically using Equations 2 and 3. As an example, Table 1 shows the normalized threshold values T.sub.RACH for M=13.Math.64=832 and several combinations of N.sub.RX and P.sub.FA values.
TABLE-US-00001 TABLE 1 P.sub.FA 0.01 0.01 0.01 0.001 0.001 0.001 N.sub.RX 1 2 4 1 2 4 T.sub.RACH 13.63 8.24 5.28 15.93 9.46 5.94
[0109] In a conventional implementation of a signature detection procedure, a normalized threshold T.sub.RACH generally needs to be scaled by a noise floor of the correlation power profile Y in order to provide an actual threshold value T′.sub.RACH to be used in the detection. However, because of the non-stationary nature of Y, due to random RACH transmissions, unpredictable scheduling decisions, and non-Gaussian interference, estimating the noise floor may be difficult, and may lead to inaccurate results for T′.sub.RACH. Therefore, use of a detection algorithm which is blind with respect to the noise floor, may be advantageous. Below is an algorithm (Algorithm 1) that describes signature detection based on a forward consecutive mean excision (FCME) method. Inputs for this algorithm include a correlation power profile Y=(Y.sub.1, Y.sub.2, . . . , Y.sub.N.sub.
[0110] Algorithm 1—RACH Signature Detection Based on FCME:
[0111] =ø and, stopFlag=0, and k=I, while (stopFlag=0)
(k≦N.sub.cor). In step S302, the processor 210 may then compute a weighting factor T.sub.k to be used with the values {Y′.sub.1, Y′.sub.2, . . . , Y′.sub.N.sub.
[0112] In step S304, the processor 210 may determine if Y′.sub.k+1>T.sub.k Σ.sub.i=1.sup.k Y′.sub.i. If this relationship holds true, then in step S306 the processor 210 may determine outliers {Y′.sub.k+1, Y′.sub.k+2, . . . , Y′.sub.N.sub.={Y′.sub.k+1, Y′d, . . . , Y′.sub.N.sub.
to the original metric space (i.e., signature windows), whereupon the procedure may stop at step S310.
[0113] If in step S304 the processor 210 determines that the relationship Y′.sub.k+1>T.sub.kΣ.sub.i=1.sup.k Y′.sub.i does not hold true, then in step S312 the processor 210 may increment k (k=k+1) in step S312, whereupon the processor may determine if k is less than or equal to N.sub.cor (in step S314), and if k is less than or equal to N.sub.cor then the processor repeats step S302 (otherwise the procedure ends at step S316).
[0114]
[0115] Optimization of RACH Initial Target Receive Power P.sub.0,RACH and Power Ramp-Up P.sub.ramp,RACH:
[0116] Following an initial cell synchronization process, the UE 110 may decode useful information related to cell access. Specifically, the System Information Block 2 (SIB2, in step S900 of
P.sub.RACH(k)=min{P.sub.max,P.sub.0,RACH−P.sub.loss+(k−1)P.sub.ramp,RACH+Δ.sub.preamble}, Equation 4
[0117] Where P.sub.max may be a maximum power that can be transmitted by the UE 110, P.sub.loss may be a path-loss that is to be compensated for (estimated using downlink reference signals), k may be a number of attempts associated with the preamble detection by the eNB 105a, and Δ.sub.preamble may be a power offset that may depend on a type of RACH preamble being transmitted.
[0118] As mentioned above, the power level defined by P.sub.0,RACH and P.sub.ramp,RACH may directly reflect the network metrics A)-C). In this context, the metrics A)-C) may be periodically monitored such that a proper adjustment of P.sub.0,RACH and P.sub.ramp,RACH may be made.
[0119] In the case of network metric A), P.sub.0,RACH and P.sub.ramp,RACH may impact network interference levels in two ways.
[0120] First, the Physical Random Access Channel (PRACH), which has a transmit power controlled by P.sub.0,RACH and P.sub.ramp,RACH, and which transports the RACH preambles, may cause interference in data/control channels (PUSCH/PUCCH) of neighboring sectors.
[0121] Second, after the RACH preamble (Message 1 in step S902 of
[0122] In order to measure network metric A) such that P.sub.0,RACH and P.sub.ramp,RACH may be controlled, the eNB 105a measurements associated with a received interference power and a thermal noise power may be used, as shown below.
[0123] Equation 5 describes an interference caused by the messages 1 (step S902 of
[0124] A thermal noise on the physical resource block p of sector r at time t may be defined as N.sub.v,t(p). In the case of receiver diversity, all quantities describe above may represent a linear average of the measurements in each diversity branch.
[0125] Based on the quantities described above, a single parameter may be used to represent the network metric A). This parameter may be designated as a noise rise, R.sub.v,t(p), and may be defined as follows.
[0126] Where this variable relates to the physical resource block p of sector v at a time t. Note that either the component I.sub.u,v,t.sup.msg1(p) or the component I.sub.u,v,t.sup.msg3(p) from a particular originating sector u, or none of these components, may be contributing to the noise floor R.sub.v,t(p). The contribution of each interference component may be dependent upon a relative alignment of the physical resource blocks across the multiple sectors of the network.
[0127] In order to measure the network metrics B) and C), the preamble miss ratio for the l-th trial in sector v at time t, M.sub.v,t(l), may be quantified. M.sub.v,t(l) may be defined as follow.
[0128] Where D.sub.v,t(l) may be a number of preambles validated with messages 3 during an l-th trial in sector v at time t, and S.sub.v,t(l) may be a total number of preambles sent for the l-th attempt in sector v at time t. In both counters D.sub.v,t(l) and S.sub.v,t(l), the preambles detected as a result of the contention resolution process may be excluded. Furthermore, from an implementation perspective, the counters D.sub.v,t(l) and S.sub.v,t(l) may be obtained from the information received as a response to the UEInformationRequest message sent by the eNB's 105a to a UE (see
[0129] The values in Equations 7 and 8 may be defined for a certain instant of time t. However, for system optimization purposes, an averaging value of R.sub.v,t(p) and M.sub.v,t(l) over a period of time is useful. This is shown in the equations below.
[0130] Where T may be defined as a sampling period during which measurements may be made.
[0131] Using quantities described in Equations 9 and 10, the RACH parameters P.sub.0,RACH and P.sub.ramp,RACH may be obtained from the multi-objective optimization program described below.
[0132] Where R.sub.[kT]=(R.sub.[kT](1), R.sub.[kT](2), . . . ) with R.sub.[kT](p)=(R.sub.1,[kT](p), R.sub.2,[kT](p), . . . , R.sub.N.sub.
[0133] Centralized Architecture (Algorithm 2):
[0134]
[0135] Referring to
[0136] The multi-objective optimization program defined by Equation 11 may be solved using numerical methods such as an evolutionary algorithm which may use the concept of Pareto optimality. Alternatively, each element in the objective vector in Equation 11 may be optimized individually, but in coordination with each other. A specific method of implementing this latter method is shown in
[0137] Algorithm 2—Optimizing Power:
[0138] In algorithm 2, a maximum tolerable value for the noise rise and preamble miss ratios (i.e., R.sub.max, M.sub.max,1 and M.sub.max, respectively) may be set in agreement with each other because of an intertwined effect that variations in P.sub.0,RACH and P.sub.ramp,RACH may cause. In this context, the scaling constants, γ.sub.P and γ.sub.R, and the scaling functions, γ.sub.N.sub.
[0139]
[0140] In step S404, the processor 502 may compute an overall average noise rise for the network, as defined by R.sub.[kT]=(1/N.sub.p)Σ.sub.p=1.sup.N.sup.
[0141] In step S410, the processor 502 may determine if the relationship if |M.sub.max,1 . . . M.sub.[kT](1)|>ε.sub.M.sub.
[0142] If in step S410 the relationship |M.sub.max,1 . . . M.sub.[kT](1)|>εM.sub.1 does not hold true, then in step S414 the processor 502 may adjust the target receive power by P.sub.0,RACH(k)=P.sub.0,RACH(k−1), where M.sub.1—Flag(k)=0.
[0143] Following steps S412 or S414, in step S416 (
[0144] Following steps S420 or S422, the processor 502 may make adjustments in P.sub.0,RACH(k) or P.sub.ramp,RACH(k) to control the noise rise by adjusting R.sub.1—Flag(k)=0 and R.sub.2—Flag(k)=0.
[0145] In step S424, the processor 502 then determines whether the relationship R.sub.[kT]−R.sub.max>ε.sub.R holds true, and if so the processor 502 then determines (in step S426) whether the relationship M.sub.[kT](1) . . . M.sub.max,1<ε.sub.M.sub.
[0146] In step S432 (
[0147] In step S436, the processor 502 may go to a next sampling period by incrementing k (k=k+1), and then returning to step S400 (
[0148]
[0149]
[0150] Optimization of the Normalized RACH Preamble Detection Threshold T.sub.RACH (Algorithm 3):
[0151] An optimization of T.sub.RACH may have a direct effect on network metrics C) and D) (i.e., minimization and delays and reduction of network signaling), respectively. As discussed above, the network metric C) may be measured in the eNBs 105a by computing a preamble miss ratio as defined in Equations 8 and 10. On the other hand, in order to measure network metric D), a new quantity called a ‘preamble false alarm ratio’ may be defined. For sector v at time t, preamble false alarm ratio F.sub.v,t may be defined as follows.
[0152] Where N.sub.v,t.sup.msg3 is a number of messages 3 (see
[0153] An optimization of T.sub.RACH may also be defined by an optimization program similar to Equation 11. Equation 14 (below) offers such an optimization.
[0154] Where F.sub.[kT]=(F.sub.1,[kT], F.sub.2,[kT], . . . , F.sub.N.sub.
[0155] In order to solve the problem defined by Equation 14, the system architecture depicted by
TABLE-US-00002 TABLE 2 N.sub.RX 1 2 4 α.sub.FA −2.31 −1.22 −0.66
[0156] Thus, using the slopes provided in Table 2, a new normalized threshold
[0157] Algorithm 3—Optimization of the Preamble Detection Threshold:
[0158] Optimization of the normalized RACH preamble detection threshold (described above) is reflected in the method shown in
[0159] In step S504, the processor 502 may determine whether the relationship |F.sub.max−F.sub.[kT]>ε.sub.FA holds true, and if so then in step S508 the processor 502 may update the threshold by T.sub.RACH(k)=α.sub.FA.Math.[log.sub.10(F.sub.max)−log.sub.10(F.sub.[kT])]+T.sub.RACH(k−1). Otherwise, the processor 502 may determine that T.sub.RACH(k)=T.sub.RACH(k−1) in step S506. Following steps S506 or S508, the processor 502 may increment k (k=k+1) in step S510, and return to step S500 to repeat the algorithm 2 procedure.
[0160] Optimization of RACH Opportunity Period τ.sub.RACH (Algorithm 4):
[0161] By controlling the RACH opportunity period τ.sub.RACH (i.e., a frequency with which PRACH opportunity slots may be provided for random access communications), an optimization of network metric E) may be achieved. In this context, a measurement may be provided by the eNBs 105a that indicates a suitability of network metric E), where the measurement may be a ‘contention ratio.’ The contention ratio, C.sub.v,t, for sector v at time t may be defined as follows.
[0162] Where D.sub.v,t may be an overall number of preambles detected in sector v at time t, and A.sub.v,t may be a total number of UEs 110 that were granted access to the network without the need for the ‘contention resolution’ procedure.
[0163] Similar to the other network measurements defined above, system optimization purposes dictate the use of a time averaging of C.sub.v,t, as shown in the equation below.
[0164] Where T may be defined as a sampling period during which measurements may be collected.
[0165] An optimization program may be defined to find a optimum value for τ.sub.RACH, as shown below.
[0166] Where C.sub.[kT]=(C.sub.1,[kT], C.sub.2,[kT], . . . C.sub.N.sub.
[0167] Similar to the normalized threshold T.sub.RACH, a simpler means of solving the problem in Equation 18 may be implemented, where it is assumed that an exponential distribution with parameter λ for inter-arrival time exists between each pair of consecutive RACH preamble transmissions. The number of RACH preamble transmissions, k, in any given time span, τ, may be distributed according to a Poisson distribution, as shown below.
[0168] From Equation 19, a collision probability, p.sub.col, as seen by a particular UE 110 during a time span τ may be written as follows.
[0169] Thus, for a particular p.sub.col and a time span τ, a supported intensity λ may be determined as follows.
[0170] Because there are N.sub.preamble orthogonal preambles available in each sector, for a particular p.sub.col and a particular RACH opportunity period τ.sub.RACH, a supported RACH intensity λ.sub.RACH may be determined as follows.
[0171] Algorithm 4—Optimizing Periodity:
[0172]
[0173]
[0174] In step S604, the processor 502 may then determine is the relationship |C.sub.max−C.sub.[kT]|>ε.sub.col holds true, and if so the processor 502 then may adjust the RACH opportunity period based on the look-up table, where τ.sub.RACH(k)=τ.sub.RACH(k−1)+Δ.sub.col(τ.sub.RACH(k−1), C.sub.[kT]) in step S606. Otherwise, the processor 502 may determine that τ.sub.RACH(k)=τ.sub.RACH(k−1), in step S608. Following steps S606 or S608, the processor may increment k (k=k+1), in step S610, and then return the process to step S600.
[0175] Comprehensive RACH Optimization Program (Algorithm 5):
[0176] The prior example embodiments (described above) considered an optimization of individual RACH parameters as stand-alone processes. However, in reality, there are interactions among the RACH parameters. For example, changing a normalized threshold T.sub.RACH may affect not only a preamble false alarm ratio but also a preamble miss ratio, which in turn may require a RACH target receive power P.sub.0,RACH to be adjusted. Due to the dependencies between the RACH parameters,
[0177] As depicted in (P.sub.ramp,RACH(k)=P.sub.ramp,RACH(k−1)) holds true, and if so then in step S654 the processor 502 may run algorithm 3 (
[0178] Following step S654, in step S656 the processor 502 may determine if T.sub.RACH(k)=T.sub.RACK(k−1), and if so then in step S658 the processor 502 may run algorithm 4 (
[0179] Decentralized RACH Optimization Procedures (Algorithm 6);
[0180] The example embodiments associated with
[0181] Because changes in the RACH preamble detection threshold T.sub.RACH and opportunity period τ.sub.RACH have a low impact on a performance of neighboring sectors, an optimization may be carried out independently in each sector (i.e., in a decentralized fashion). In this scenario, the only required changes to the methods of
[0182] However, because variations in P.sub.0,RACH and P.sub.ramp,RACH (c affect interference levels in neighboring sectors, a small amount of coordination between the sectors may improve performance. Specifically, neighboring sectors may be able to exchange information about the interference levels that are experienced due to changes in P.sub.0,RACH and P.sub.ramp,RACH. This exchange of interference information between eNBs 105a may be done using the quantities R.sub.v,[kT](p) as defined in Equation 9. Therefore,
[0183] In step S700 of
[0184] In step S704, the processor 210 may compute an overall average noise rise for the neighboring sectors using R.sub.[kT]=(1/N.sub.p)Σ.sub.p=1.sup.N.sup.
[0185] In step S708, the processor 210 may determine if |M.sub.max,1−M.sub.w,[kT](1)|>ε.sub.M.sub.
[0186] Following step S710 or S712, the processor may determine adjust a power ramp P.sub.ramp,RACH(k) by determining in step S714 whether |M.sub.max−M.sub.w[kT]|>ε.sub.M.sub.
[0187] Following steps S716 or S718, the processor 210 may make adjustments in P.sub.0,RACH(k) or P.sub.ramp,RACH(k) to control the noise rise in the neighboring sectors by resetting flags R.sub.1—Flag(k)=0 and R.sub.2—Flag(k)=0 in step S720.
[0188] Following step S720, in step S724 the processor 210 may determine if R.sub.[kT]−R.sub.max>ε.sub.R, and if so then in step S722 the processor 210 may then determine if M.sub.w,[kT](1)−M.sub.max,1<ε.sub.M.sub.
[0189] In step S728, if the processor 210 makes the determination in the affirmative, then in step S730 the processor 210 may make adjustments to control a rise in noise by calculating P.sub.ramp,RACH(k)=Q.sub.ramp{P.sub.ramp,RACH(k−1)+γ.sub.N.sub.
[0190] As in the centralized architecture shown in
[0191] In
[0192] In step S802, the processor 210 may determine if (P.sub.0,RACH(k)=P.sub.0,RACH(k−1))(P.sub.ramp,RACH(k)=P.sub.ramp,RACH(k−1)), and if so then in step S804 the processor 210 may run an iteration of the decentralized version of Algorithm 3 (
[0193] Following step S804, in step S806 the processor 210 may determine if T.sub.RACH(k)=T.sub.RACH(k−1), and if so then in step S808 the processor may perform an iteration of the decentralized version of Algorithm 4 (
[0194] Following step S808, the processor 210 ends the method (in step S810).
[0195] Example embodiments having thus been described, it will be obvious that the same may be varied in many ways. Such variations are not to be regarded as a departure from the intended spirit and scope of example embodiments, and all such modifications as would be obvious to one skilled in the art are intended to be included within the scope of the following claims.