What is input backoff (IBO) in WCDMA?

Input backoff is the difference in decibels between the output from an amplifier and its 1dB compression point. As the input to an amplifier is increased the output from the amplifier increases steadily also, the difference between these two is the Gain of the amplifier.There comes a point however when the amplifier can no longer supply any more output power with an increase in input signal and thus the gain of the amplifier drops with increasing input level; when the gain has dropped by 1dB the amplifier has reached its 1dB compression point or P1dB as it is often called and distortion rises rapidly beyond this point. With CDMA signals they have quite a high ratio of Peak power to Average power or Peak to Average Ratio (PAR), so as to prevent the amplified signal from being badly distorted it is important that the peak levels of the signal do not approach the P1dB point, thus if my amplifier had an output P1dB of (say) 30dBm and I chose my signal levels so that the peak output signal never exceeded 20dBm then I would be operating at 10dB backoff. The problem with backed off amplifiers is that they need to be big and relatively power hungry in order to amplify relatively small signals and so there are now a variety of methods that deliberately introduce distortions into the amplifier in order to cancel those from compression - digital predistortion is one such method, feed forward is the classic old school technique.Another old technique that is now undergoing a renaissance (from companies like Nujira) is envelope tracking in which the power supply to the amplifier is intelligently varied in real time to keep the amplifier at a constant distance from the compression point as the signal is varied, in order to get good efficiency the system is adjusted to hold the amplifier close to compression, the resulting distortions are removed by digitalpre-distortion. Automatic Neighbor Relations(ANR) Self Organising Newtwork(SOS)

ell Reselection
5.3 Cell Reselection
The cell reselection can be controlled either autonomously by the mobile or by the network. It is based on measurements performed by the mobile. The network can order that these measurements be reported periodically. Three cell reselection modes NC0, NC1, and NC2 have been defined: NC0. In this mode, the GPRS mobile performs autonomous cell reselection without sending measurement reports to the network. NC1. In this mode, the GPRS mobile performs autonomous cell reselection and periodically sends measurement reports to the network.

 NC2. In this mode, the network controls the cell reselection. The mobile sends measurement reports to the network. When the mobile performs autonomous cell reselection, it chooses a new cell and triggers a cell reselection on its own. The NC2 mode allows the network to control the mobility of GPRS users within the network. The GPRS cell reselection mode for a GPRS-attached MS is given by the network control mode (NETWORK_CONTROL_ORDER parameter), which is broadcast on the BCCH or PBCCH. The mobile behavior is determined by both its GMM state and the network control mode. Whatever the value of the network control mode, when the MS is in GMM STANDBY state, it performs autonomous cell reselection and does not send measurement reports to the network. In GMM READY state, the mobile performs cell reselection according to the network control mode. Two criteria are defined for autonomous cell reselection: one is based on the (C1, C2) criteria. It corresponds to the GSM cell-reselection criteria. The other, based on the (C'1, C31, C32) criteria, has been introduced for GPRS. All these criteria are based on received signal level (RXLEV) measurements in the serving cell and in the neighbor cells. In a cell where PBCCH does not exist (GPRS cell reselection parameters are not broadcast), the MS performs cell reselection based on (C1, C2) criteria; except if the cell reselection parameters are sent explicitly to the mobile in one control message, in which case the mobile performs autonomous cell reselection based on criteria (C'1, C31, C32). In a cell where PBCCH exists, the MS performs cell reselection based on (C'1, C31, C32) criteria. Table 5.8 summarizes the different reselection modes and the criteria used. Table 5.8: Mode of Reselection and Criteria for Cell Reselection Criteria If Criteria If NETWORK_CONT GMM State PBCCH PBCCH Does ROL_ORDER Value of the MS Mode of Cell Reselection Exists Not Exist NC0 Standby/Rea Autonomous cell reselection dy Standby Ready Autonomous cell reselection Autonomous cell reselection with measurement reports Autonomous cell reselection C'1, C31, C32 C1, C2 [*]

NC1

C'1, C31, C32 C1, C2[*] C'1, C31, C32 C1, C2[*]

NC2

Standby Ready

C'1, C31, C32 C1, C2[*] -

Network-controlled cell reselection with measurement reports

[*]Except

if the GPRS cell reselection parameters are sent to the MS in an RLC/MAC control

message.

5.3.1 Measurements
When the mobile camps on a cell, it receives from the network the list of the neighbor cells identified by their BCCH frequencies and their BSICs. The mobile measures periodically the RXLEV on these

neighbor BCCHs and checks the BSIC of the BCCH carriers. These RXLEV measurements are used in autonomous cell reselection mode and reported to the network in case of cell reselection controlled by the network and NC1 mode. 5.3.1.1 In Packet Idle Mode In packet idle mode, the mobile measures the RXLEV on the BCCH carrier of the serving cell and on each BCCH carrier of the neighboring cells. It calculates an average RXLEV on each carrier, with at least five measurements during a maximum period corresponding to the maximum of 5 seconds or five consecutive paging blocks of the mobile. The mobile must perform a minimum of one measurement on a cell every 4 seconds or a maximum of 20 measurements every second. The mobile maintains a list of the six strongest received BCCH carriers, which is updated every averaging period. The mobile must decode the BSIC on the BCCHs of the six most powerful cells every 14 paging block periods or at least every 10 seconds. 5.3.1.2 In Packet Transfer Mode In packet transfer mode, the mobile measures the RXLEV on the BCCH carrier of the serving cell and on each BCCH carrier of the neighboring cells. It calculates an average RXLEV on each carrier during a period of 5 seconds, with at least five measurements. The mobile performs a measurement on each TDMA frame for at least one of the given BCCH carriers, one after the other. The mobile must decode the BSIC on the BCCHs of the six most powerful cells at least every 10 seconds. The mobile does this decoding during the two idle frames of the 52-multiframe.

5.3.2 Criteria
In this section, the criteria C1, C'1, C2, C31, and C32 that were introduced in the previous section are described in detail. The way these parameters are used in the cell reselection process will be described in the next section. 5.3.2.1 C1 Criterion The path loss criterion parameter C1 is used as a minimum signal level criterion for cell reselection when there is no PBCCH in the cell. C1 is defined by the following formula:

RXLEV_ACCESS_MIN represents the minimum RXLEV at the MS to access the cell. MS_TXPWR_MAX_CCH represents the maximum transmit power level allowed to the MS when accessing the cell. P is the maximum RF output power of the MS (parameter specific to the MS). A represents the reception margin. The MS is allowed to access the cell if its RXLEV is higher than RXLEV_ACCESS_MIN; that is, A > 0. If A > 0, the mobile is in the cell coverage and the downlink is good enough. If A < 0, the mobile is outside the cell coverage. B represents the mobile transmission capability margin. If B < 0, the transmission capabilities of the mobile are sufficient; if the mobile is in the cell coverage A > 0, the cell can be selected. If B > 0 and

A - B > 0, the mobile transmission capabilities are compensated by the reception margin and the cell can be selected. If B > 0 and A - B < 0, the mobile transmission capabilities are not compensated, and the mobile cannot select the cell. Thus the path loss criterion is satisfied if C1 > 0. 5.3.2.2 C'1 Criterion The path loss criterion parameter C'1 is used as a minimum signal level criterion for GPRS cell reselection in the same way as for GSM idle mode. C'1 is the same as C1, except that GPRS-specific parameters are used instead. C' 1 is defined by the following formula:

5.3.2.3 C2 Criterion The C2 criterion is used for cell ranking in the GSM cell-reselection process. It is computed with the following formulas:

T is a timer that is started from 0 at the time the cell enters in the list of strongest carriers. CELL_RESELECT_OFFSET is a parameter that is used to prioritize one cell in relation to the others. TEMPORARY_OFFSET is a parameter used to penalize during PENALTY_TIME when this cell just enters the list of strongest carriers. 5.3.2.4 C31 Criterion The signal level threshold criterion parameter C31 for hierarchical cell structures (HCS) is used to determine whether prioritized hierarchical GPRS cell reselection applies. The C31 criterion allows cells for GPRS-attached mobiles to be prioritized during autonomous cell reselection. A GPRS-attached MS will preferably select the cell having the highest priority as indicated by the parameter PRIORITY_CLASS. However, a sufficient RXLEV in the cell (HCS_THR parameter) is required for it to belong within the highest-priority class. If the signal level becomes too low, a determination of lowest priority is made. The C31 criterion contains a time-based offset. This offset can be used to penalize a cell, belonging to another priority level as the serving cell, during GPRS_PENALTY_TIME. The C31 criteria for the serving and neighbor cells are evaluated with the following formula:

where HCS_THR is the signal threshold for applying HCS GPRS reselection, and GPRS_PENALTY_TIME gives the duration for which the temporary offset GPRS_TEMPORARY_OFFSET is applied. T is a timer that is started from 0 at the time the cell enters in the list of strongest carriers. 5.3.2.5 C32 Criterion The cell-ranking criterion parameter (C32) is used to select cells among those with the same priority and is defined for the serving cell and the neighbor cells by:

The C32 criterion also contains a time-based offset that can be used to penalize a cell belonging to the same priority level during a certain time. It could be use to perform speed discrimination. The GPRS_RESELECT_OFFSET parameter allows a neighbor cell to be penalized. When the MS is in GMM READY state (a transfer can be ongoing or about to start), in order to avoid unnecessary cell reselection or to be sure that it is really needed, an hysteresis GPRS_CELL_RESELECT_HYSTERESIS is subtracted from the C32 criteria of the neighbor cells. This hysteresis is also subtracted from the C31 criterion if requested by the network. When the neighbor cell does not belong to the same RA as the serving cell, an hysteresis RA_RESELECT_HYSTERESIS is subtracted from the C32 criterion of the neighbor cell. This is done to avoid changing from one RA to the other and so triggering an RA update procedure, increasing the signaling within the network. In case cell reselection occurred within the previous 15 seconds, all neighbor cells are penalized by 5 dB in order to avoid ping-pong between cells.

All the GPRS cell-reselection parameters described in this section are broadcast on the PBCCH carrier of the serving cell. The cell-reselection parameters used for calculation of the (C1, C2) criteria are broadcast on the BCCH carrier of the serving cell and the BCCH carriers of the neighbor cells.

5.3.3 Autonomous Cell-Reselection Process

The process of cell reselection is either based on the (C1, C2) criteria or (C'1, C31, C32) criteria. (C1, C2) criteria are used when there is no PBCCH in the serving cell and the cell-reselection parameters needed for (C'1, C31, C32) criteria evaluation have not been explicitly transmitted to the mobile. (C'1, C31, C32) criteria are used when the PBCCH is transmitted in the serving cell, or when the cell reselection parameters needed for (C'1, C31, C32) criteria evaluation have been explicitly transmitted to the mobile and there is no PBCCH. 5.3.3.1 Procedure for (C1, C2) The mobile must compute the C1 and C2 values for the serving cell and the neighbor cells at least every 5 seconds. A cell-reselection is triggered if one of the following events occurs: The path loss criterion parameter C1 indicates that the path loss in the serving cell has become too high (i.e., C1 < 0 ). Downlink signaling failure is experienced (see Section 5.4.5). The serving cell has become barred. A neighbor cell for which the C2 criterion is higher than the serving cell for a period of 5 seconds is detected. When the neighbor cell is not in the same RA or if the mobile is in GMM READY state, the C2 value for the neighbor cell must exceed the C2 value for the serving cell by at least CELL_RESELECT_HYSTERESYS. This allows for the avoidance of unnecessary cell reselection when the mobile is in READY state or between two different RAs. For a cell reselection occurring in the previous 15 seconds, the C2 value for the neighbor cell must exceed the C2 value for the serving cell by at least 5 dB for a period of 5 seconds. A random access attempt is still unsuccessful after "Max retrans" repetitions, Max retrans being a parameter broadcast on the control channel. 5.3.3.2 Procedure for (C'1, C31, C32) The mobile computes the values of the C'1, C31, and C32 criteria for the serving cell and the nonserving cells at least every second or at every new measurement, whichever is the greatest. A cell reselection is then triggered if one of the following events occurs: The path loss criterion parameter C'1 indicates that the path loss to the cell has become too high (i.e., C'1 < 0). A nonserving suitable cell is evaluated to be better than the serving cell. The best cell is the cell with the highest C32 value among: (a) the cells that have the highest PRIORITY_CLASS among the cells that fulfill C31 >=0, or (b) all cells, if no cell fulfills the criterion C31 >= 0. Downlink signaling failure is experienced (see Section 5.4.5). The cell on which the mobile is camping has become barred. A random access attempt is still unsuccessful after MAX_RETRANS_RATE attempt. The cell that the mobile was camped on must not be returned to within 5 seconds.

5.3.4 Measurement Report Sending

When the cell reselection mode given by the NETWORK_CONTROL_ORDER parameter indicates NC1 or NC2 and the MS is in GMM READY state, the MS reports measurements in the PACKET MEASUREMENT REPORT message to the network. This message contains: The measured RXLEV for the serving cell; In packet idle mode, the average interference level ch for the serving cell; The measured RXLEV from the nonserving cells. The reporting period is defined as follows: In packet idle mode, the reporting period is indicated by NC_REPORTING_PERIOD_I parameter; In packet transfer mode, the reporting period is indicated by the NC_REPORTING_PERIOD_T parameter. NC_REPORTING_PERIOD_I and NC_REPORTING_PERIOD_T parameters are broadcast on PBCCH. They can also be broadcast on PACCH in case there is no PBCCH.

5.3.5 Network-Controlled Cell-Reselection Process

When the cell-reselection mode indicates NC2 and the mobile is in GMM READY state, the network controls the cell-reselection process. Based on the measurements reported by the mobile (RXLEV and RXQUAL only during packet transfer) or by the BTS during packet transfer mode, the network decides whether a cell reselection must be triggered. When the decision to trigger a cell reselection is made by the network, it sends a PACKET CELL CHANGE ORDER message. When the MS receives the command, it reselects the cell according to the included cell description (BCCH frequency and BSIC) and changes the network control mode according to the NETWORK_CONTROL_ORDER parameter included in the command. Note that in order to reduce the cell-reselection delay, the MS may continue its transfer in the old cell until it decodes the BCCH or PBCCH information necessary to reestablish a TBF in the new neighbor cell.

below is the concerned parameters for IRAT ^_^ IRAT concer ned Parameter s gsmAmountPropRepeat gsmPropRepeatInterval gsmThresh3a hysteresis3a maxGsmMonSubset timeToTrigger3a utranRelThresh3aEcno utranRelThresh3aRscp Compress Mode concer ned Parameter s fddGsmHOSupp fddIFHOSupp hoType hysteresis2d hysteresis2f serviceOffset2dEcno serviceOffset2dRscp timeToTrigger2dEcno timeToTrigger2dRscp timeToTrigger2fEcno timeToTrigger2fRscp

timeToTrigger6d timeTrigg6b ueTxPowerThresh6b usedFreqRelThresh2fEcno usedFreqRelThresh2fRscp usedFreqThresh2dEcno usedFreqThresh2dRscp utranRelThreshRscp

SETUP (indicating the establishment of a connection) CALL PROCEEDING (indicating that the call is being processed by the destination terminal) ALERTING (tells the calling party that the destination terminal is ringing) CONNECT (sent back to the calling party indicating that the intended destination has answered the call) DISCONNECT (sent to indicate a request to terminate the connection, by the end that seeks to terminate) RELEASE (sent in response to the disconnect request indicating that the call is to be terminated). RELEASE COMPLETE (sent by the receiver of the release to complete the handshake).

Q.931 Protocol Overview

Q.931 is ISDN's connection control protocol, roughly comparable to TCP in the Internet protocol stack. Q.931 doesn't provide flow control or perform retransmission, since the underlying layers are assumed to be reliable and the circuit-oriented nature of ISDN allocates bandwidth in fixed increments of 64 kbps. Q.931 does manage connection setup and breakdown. Like TCP, Q.931 documents both the protocol itself and a protocol state machine. Note: In accordance with the conventions of ITU standards, bits are numbered from LSB to MSB, 1 to 8 (Internet standards use MSB to LSB, 0 to 7). The general format of a Q.931 message includes a single byte protocol discriminator (8 for Q.931 messages), a call reference value to distinguish between different calls being managed over the same D channel, a message type, and various information elements (IEs) as required by the message type in question: The most important messages types are: ALERTING (1) IEs: Bearer capability, Channel identification, Progress indicator, Display, Signal, High layer compatibility Direction: Called user -> network -> calling user The called user is being alerted, i.e "the phone is ringing". CALL PROCEEDING (2) IEs: Bearer capability, Channel identification, Progress indicator, Display, High layer compatibility

Direction: Called user -> network -> calling user Call establishment is proceeding. CONNECT (7) IEs: Bearer capability, Channel identification, Progress indicator, Display, Date/time, Signal, Low layer compatibility, High layer compatibility Direction: Called user -> network -> calling user The call has gone through and been accepted. CONNECT ACKNOWLEDGE (15) IEs: Display, Signal Direction: Calling user -> network -> called user SETUP (5) IEs: Sending complete, Repeat indicator, Bearer capability, Channel identification, Progress indicator, Network specific facilities, Display, Keypad facility, Signal, Calling party number, Calling party subaddress, Called party number, Called party subaddress, Transit network selection, Repeat indicator, Low layer compatibility, High layer compatibility Direction: Calling user -> network -> called user Initial message sent to initiate a call SETUP ACKNOWLEDGE (13) IEs: Channel identification, Progress indicator, Display, Signal Direction: Called user -> network -> calling user SUSPEND (37) IEs: Call identity Direction: User -> network ISDN calls can be suspended (put on hold) to allow another call to use the B channel. SUSPEND/RESUME messages manage suspended calls. SUSPEND ACKNOWLEDGE (45) IEs: Display Direction: Network -> user SUSPEND REJECT (33) IEs: Cause, Display Direction: Network -> user

RESUME (40) IEs: Call identity Direction: User -> network RESUME ACKNOWLEDGE (48) IEs: Channel identification, Display Direction: Network -> user RESUME REJECT (34) IEs: Cause, Display Direction: Network -> user DISCONNECT (69) IEs: Cause, Progress indicator, Display, Signal A message sent from the user to request call breakdown, or from the network to indicate the call has been cleared. RELEASE (77) IEs: Cause, Display, Signal A message sent to indicate the channel is being released. RELEASE COMPLETE (90) IEs: Cause, Display, Signal STATUS ENQUIRY (117) IEs: Display Direction: User -> network Requests a STATUS message from the network STATUS (125) IEs: Cause, Call State, Display Direction: Network -> user Indicates current call state in terms of Q.931 state machine A simple Q.931 message exchange might go as follows: After the Q.931 header, identifying the call and the message type, comes the information elements. There are two types of IEs: single byte and multi-byte, distinguished by their high-order bit: The most important IEs are all multi-byte: Bearer capability (4) Specifies a requested service: packet or circuit mode, data rate, type of information content

Call identity (16) Used to identify a suspended call Call state (20) Describes the current status of a call in terms of the standard Q.931 state machine Called party number (112) The phone number being dialed Calling party number (108) The origin phone number Cause (16) The reason a call was rejected or disconnected. A sample of possible cause codes: 1 Unassigned number 3 No route to destination 6 Channel unacceptable 16 Normal call clearing 17 User busy 18 User not responding 19 User alerting; no answer 22 Number changed 27 Destination out of order 28 Invalid number format 34 No circuit/channel available 42 Switching equipment congestion Channel identification (24) Identify a B channel Date/time (41) Poorly defined. Not year 2000 compliant! Display (40) Human-readable text. Can be specified with almost any message to provide text for an LCD display, for example. Service Profile Identification (58) Contains a Service Profile Identifier (SPID) Signal (52) Provide call status tones according to the following chart: Meaning 0000 0000 0000 0001 0000 0010 Dial tone Ringing Intercept North American Practice 350 Hz + 440 Hz; continuous 440 Hz + 480 Hz; 2 sec on/4 sec off Alternating 440 Hz and 620 Hz; 250 ms each

0000 Network congestion (fast 0011 busy) 0000 Busy 0100 0000 Confirm 0101 0000 Answer 0110 0000 Call waiting 0111 0000 Off-hook warning 1000 0011 1111 Tones off

480 Hz + 620 Hz; 250 ms on/250 ms off 480 Hz + 620 Hz; 500 ms on/500 ms off 350 Hz + 440 Hz; repeated three times: 100 ms on/100 ms off not used 440 Hz; 300 ms burst 1400 Hz + 2060 Hz + 2450 Hz + 2600 Hz; 100 ms on/100 ms off