Skip to main content


One way of estimating the pathloss is the
received signal code power (RSCP) of the CPICH. However the CPICH RSCP does not
take any interference into consideration. The Ec/No of the CPICH is a measurement that
takes both the pathloss and the interference situation into consideration.

The CPICH Received Signal Code Power (CPICH RSCP) is dependent on the CPICH
transmitted code power, the pathloss. Since the transmitted power on the CPICH is
constant the CPICH RSCP will primarily be affected by the pathloss. Hence a decrease in
the CPICH RSCP will mean that the pathloss in both up and downlink has increased. The
absolute accuracy requirement for the CPICH RSCP measurements is 6-8 dB [1].

The CPICH Ec/No is defined as the energy per chip divided by the total in-band
interference. Theoretically it is defined as the CPICH RSCP divided by the RSSI (received
signal strength indicator).
Both the CPICH RSCP and the CPICH Ec/No will increase with a decrease in the pathloss.
However the Ec/No is both proportional to the pathloss and inversely proportional to the
RSSI. Thus, the relation between CPICH Ec/No and pathloss is not linear as in the RSCP
case. Particularly at the cell border in cases where there is mainly one dominant server the
behaviour of the CPICH Ec/No is not completely straightforward.

The figure above describes the principle of the scenario previously mentioned. As can be
seen the CPICH Ec/No remains relatively constant since both the pilot signal and the
interfering signals are more or less subject to the same pathloss. Once the thermal noise
becomes the dominant part of the RSSI the CPICH Ec/No also starts to degrade but not as
steep as the RSCP degradation. When the signal finally becomes lower than the thermal
noise floor the Ec/No will drop sharply. This description of the scenario is highly simplified.
The advantage with the CPICH Ec/No measurement is that it takes into consideration the
downlink interference situation in the network through its dependency on the RSSI.
The absolute accuracy requirement for the CPICH Ec/No measurements is 1.5-3 dB,
which is considerably higher than the requirements for the RSCP [1]


wayanpur said…
Thank for sharing Bos...
fernando21278 said…
Nice explanation. Thanks!

Popular posts from this blog

LTE intra frequency vs inter frequency question

His main question was about mobility. Mobility in LTE can be quite tricky. The main point of his question was about the frequency band size. In LTE there is a scalable OFDM channel. The bandwidth can vary from 1.4 MHz to 20 MHz. There are also a number of frequency bands that are going to be used for LTE (the new 700 MHz as well as the old PCS and Cellular bands).
The question basically was can a mobile move between frequency bands and the answer is absolutely yes. The second part of the question regarded movement between different sizes of bands. The best way to approach this question is to define two terms. The two terms are intra-frequency and inter-frequency mobility. We are use to these terms in other technologies (i.e. GSM and UMTS), but LTE puts a new spin on things. Intra-frequency mobility is when a mobile moves between two cells and both cells have the same frequencies (I know, not the most profound statement).  If there is a change in the center frequency this is now called…

Data link layer add both header and trailer to the data it receives from above layer

Data Flow in the OSI Model38 out of 58 rated this helpful - Rate this topic The OSI model presents a standard data flow architecture, with protocols specified in such a way that the receiving layer at the destination computer receives exactly the same object as sent by the matching layer at the source computer. Figure A.2 shows the OSI model data flow. Figure A.2 OSI Model Data Flow The sending process passes data to the application layer. The application layer attaches an application header and then passes the frame to the presentation layer. The presentation layer can transform data in various ways, if necessary, such as by translating it and adding a header. It gives the result to the session layer. The presentation layer is not aware of which portion (if any) of the data received from the application layer is the application header and which portion is actually user data, because that information is irrelevant to the presentation layer's role. The process of adding headers is …

RSCP/EcNo Mapping value

RSCP/EcNo Mapping value(3GPP TS 25.133)Reported valueMeasured quantity valueUnitCPICH_RSCP_LEV _-05CPICH RSCP<-120dBmCPICH_RSCP_LEV _-04-120<=CPICH RSCP<-119dBmCPICH_RSCP_LEV _-03-119<=CPICH RSCP<-118dBmCPICH_RSCP_LEV _-02-118<=CPICH RSCP<-117dBmCPICH_RSCP_LEV _-01-117<=CPICH RSCP<-116dBmCPICH_RSCP_LEV _00-116<=CPICH RSCP<-115dBmCPICH_RSCP_LEV _01-115<=CPICH RSCP<-114dBmCPICH_RSCP_LEV _02-114<=CPICH RSCP<-113dBmCPICH_RSCP_LEV _03-113<=CPICH RSCP<-112dBmCPICH_RSCP_LEV _04-112<=CPICH RSCP<-111dBmCPICH_RSCP_LEV _05-111<=CPICH RSCP<-110dBmCPICH_RSCP_LEV _06-110<=CPICH RSCP<-109dBmCPICH_RSCP_LEV _07-109<=CPICH RSCP<-108dBmCPICH_RSCP_LEV _08-108<=