Professional Documents
Culture Documents
Channel Element
Channel Element (CE) describes the SW licensed capacity resources required for a
dedicated channel (DCH or E-DCH). The number of channel elements required in a
RBS is based on the traffic type, and is dependent on the radio bearers to be used, as
well as on the number of simultaneous users for each specific radio bearer.
Hardware
https://www.linkedin.com/pulse/channel-element-r99hsdpahsupa-mohamed-abdel-monem 1/10
9/21/21, 8:34 AM Channel Element at R99/HSDPA/HSUPA
bearer for the dedicated channel. The channel element cost can be expressed with
Mohamed Abdel Monem
weighting factors for the various radio bearers.
In a RAN, CE resources are managed by both the RNC and NodeB. The NodeB reports
its CE capacity to the RNC. The RNC determines whether to admit a new service
based on the number of CEs that need to be consumed and controls CE resources
during CE congestion. This ensures the proper use of CE resources. The NodeB
dynamically manages CE resources and rapidly adjusts the number of CEs that can be
consumed based on the actual service rate. This increases CE resource usage.
https://www.linkedin.com/pulse/channel-element-r99hsdpahsupa-mohamed-abdel-monem 2/10
9/21/21, 8:34 AM Channel Element at R99/HSDPA/HSUPA
Basic Channel Element Concepts
One UL CE needs to be consumed by a UL 12.2 kbit/s voice service (SF = 64) plus 3.
kbit/s signaling.
One DL CE needs to be consumed by a DL 12.2 kbit/s voice service (SF = 128) plus
3.4 kbit/s signaling.
If only 3.4 kbit/s signaling traffic is carried on a DCH or HSPA channel, one CE still
needs to be consumed. The number of CEs that need to be consumed by services of
other types can be calculated by analogy.
https://www.linkedin.com/pulse/channel-element-r99hsdpahsupa-mohamed-abdel-monem 3/10
9/21/21, 8:34 AM Channel Element at R99/HSDPA/HSUPA
CE is a concept of the NodeB side. On the RNC side, it is called NodeB credit. The
RNC performs admission and congestion control based on the NodeB credit. In the
UL, the number of Node credit resources is twice that of CEs. In the DL, the number of
NodeB credit resources equals that of CEs.
The RNC determines the number of CEs required for a service based on the SF that
matches the service rate. When an RAB connection is set up or released for a service,
CE resources must be allocated or taken back and the number of CEs must be deducted
or added accordingly. Different rules for calculating CE resource consumption apply to
channels or services of different types.
CE resources reserved by the NodeB for common and HSDPA channels are shown in
gray.
CE resources that need to be consumed by R99 and HSUPA services are shown in
pink.
https://www.linkedin.com/pulse/channel-element-r99hsdpahsupa-mohamed-abdel-monem 4/10
9/21/21, 8:34 AM Channel Element at R99/HSDPA/HSUPA
Similarly, the NodeB reserves CE resources for the high-speed downlink shared
channel (HS-DSCH) and the related control channels if HSDPA is used. These CEs
also do not need to be considered in the calculation of CE consumption.
Note that the signaling of an HSDPA UE that is not performing an R99 service
occupies one DCH and needs to consume one DL CE. If the SRB over HSDPA
function is enabled, the signaling of an HSDPA service does not consume additional
CE resources. For an HSDPA UE that is performing an R99 service, its signaling and
the R99 service occupy the same DCH. Therefore, only the CEs consumed on R99
traffic channels need to be calculated.
Traffic on the HS-DSCH will not consume channel elements. However, every HSDPA
connection will require A-DCHs for UL/DL signaling and UL traffic. A‑DCHs are
https://www.linkedin.com/pulse/channel-element-r99hsdpahsupa-mohamed-abdel-monem 5/10
9/21/21, 8:34 AM Channel Element at R99/HSDPA/HSUPA
For an R99 service, the RNC determines the number of CEs and NodeB credit
resources that need to be consumed based on the SF that matches the maximum bit rate
(MBR) of the service.
https://www.linkedin.com/pulse/channel-element-r99hsdpahsupa-mohamed-abdel-monem 6/10
9/21/21, 8:34 AM Channel Element at R99/HSDPA/HSUPA
EUL can only be used for connections that use HS-DSCH in the DL. Each admitted
EUL user will carry traffic and signaling on an E-DCH. Similar to HSDPA, the E-DCH
user has one serving cell. The E-DCH serving cell is always equal to the HS-DSCH
serving cell for the connection. If the terminal is in soft or softer handover there is
always at least one non-serving E-DCH cell.
E-DCH users consume channel elements from the SW licensed CE pool, but the
resources for E-DCH are handled in a different way compared to A-DCH and DCH.
The resources for E-DCH are controlled by the EUL scheduler located in the RBS and
resources for A-DCH and DCH are controlled by the RNC.
Each admitted E-DCH user will have a minimum amount of channel elements
allocated. The minimum amount of channel elements depends on licensing.Those
channel elements are reserved to the E-DCH user as long as the user is active in the
cell. The minimum channel element allocation can be used for non-scheduled data
(signaling) and scheduled data to a certain rate (user data). The channel elements
https://www.linkedin.com/pulse/channel-element-r99hsdpahsupa-mohamed-abdel-monem 7/10
9/21/21, 8:34 AM Channel Element at R99/HSDPA/HSUPA
represented by the minimum CE allocation are guaranteed and are not affected by
Mohamed Abdel Monem
Enhanced Soft Congestion or re-scheduling in the RBS. As a result, an admitted E-
DCH user has the possibility to reach a minimum rate supported by the minimum CE
allocation.
If an E-DCH user requests rates higher than the rates supported by the minimum CE
allocation, additional channel elements will be needed. These are handled by the EUL
scheduler only and are not seen by the Admission Control function. The EUL
scheduler will grant an E-DCH user a higher rate if it is possible to allocate more CEs
in addition to the other two required UL resource types (air interface interference and
Iub bandwidth [2]). The additional CEs for an E-DCH user might be affected by
Enhanced Soft Congestion or re-scheduling in the RBS.
Notes
It is not necessary to dimension for common channels, since common channels do not
consume channel elements.
Allocation of channel elements due to compressed mode has not been considered, since
there is no additional channel element cost for connections in compressed mode.
This article is based on search at different documents for different vendors and 3GPP
TS 36.213.
For more articles, you can visit my blog and for video tutorial
153 ·
24 Comments
https://www.linkedin.com/pulse/channel-element-r99hsdpahsupa-mohamed-abdel-monem 8/10
9/21/21, 8:34 AM Channel Element at R99/HSDPA/HSUPA
Like Comment Share
2y
AhmedThank you sir for your sharing. Is there any possibility to forcast CE consumption of a NodeB?
ayenew
Like
Reply
Ashish Shrivastava
3y
Ashish
Good description of Channel Element resource concept. Do you know similar hardware re‐
Shrivastava
source concept in LTE's eNodeB?
Like
Reply
Mohammed Amer
3y
Mohammed
I've found this article through google, then noticed that it's written by you, well done :)
Amer Like
Reply
1 Like
3y
Mohamed
You’re welcome any time :))))
AbdelLike
Reply
Monem
Debashis Dalai
3y
Debashis
Thank you Mahamed! You have helped me clear many of my doubts! Thanks again! God Bless
Dalai you!
Like
Reply
1 Like
3y
Mohamed
Welcome ;)
AbdelLike
Reply
Monem
3y
Mohamed
Welcome ;)
AbdelLike
Reply
Monem
Muhammad Nur
4y
Muhammad
Very Helpfull document....
Nur Like
Reply
1 Like
4y
Mohamed
Thanks mohamed :)
AbdelLike
Reply
Monem
See more comments
https://www.linkedin.com/pulse/channel-element-r99hsdpahsupa-mohamed-abdel-monem 9/10
9/21/21, 8:34 AM Channel Element at R99/HSDPA/HSUPA
© 2021 About
Language
https://www.linkedin.com/pulse/channel-element-r99hsdpahsupa-mohamed-abdel-monem 10/10