LTE (E-UTRA) UM RLC PDU Encoding With Examples


LTE Unacknowledged Mode (UM) RLC PDU overview is discussed in another tutorial. If you want to learn the basics of UM data PDUs you can check the following tutorial.

In this tutorial examples for most important encoding techniques used for UM RLC PDUs are discussed.


UMD PDU with 5 bit SN (No LI)

Assumptions

Sequence Number (SN) Length: 5 bits
Sequence Number: 1
Service Data Unit (SDU): 01 02 03 04 05
Framing Info: 00
00: First byte of the data field corresponds to first byte of a RLC SDU & last byte of the Data field corresponds to last byte of a RLC SDU.

No Length Indicator is used.


UMD PDU with 10 bit SN (No LI)

Assumptions

Sequence Number (SN) Length: 10 bits
Sequence Number: 1
Service Data Unit (SDU): 01 02 03 04 05
Framing Info: 00
00: First byte of the data field corresponds to first byte of a RLC SDU & last byte of the Data field corresponds to last byte of a RLC SDU.

No Length Indicator is used.


UMD PDU with 5 bit SN (Odd number of LIs)

Sequence Number (SN) Length: 5 bits
Sequence Number: 1

SDU-1: 01 02 03
SDU-2: 04 05
SDU-3: 06 07 08

Framing Info: 00

00: First byte of the data field corresponds to first byte of a RLC SDU & last byte of the Data field corresponds to last byte of a RLC SDU.

SDUs are hex data.


UMD PDU with 5 bit SN (Even number of LIs)

Sequence Number (SN) Length: 5 bits
Sequence Number: 1

SDU-1: 01 02 03
SDU-2: 04 05

Framing Info: 00

00: First byte of the data field corresponds to first byte of a RLC SDU & last byte of the Data field corresponds to last byte of a RLC SDU.

SDU are hex data.


UMD PDU with 10 bit SN (Odd number of LIs)

Sequence Number (SN) Length: 10 bits
Sequence Number: 1

SDU-1: 01 02 03
SDU-2: 04 05
SDU-3: 06 07 08

Framing Info: 00

00: First byte of the data field corresponds to first byte of a RLC SDU & last byte of the Data field corresponds to last byte of a RLC SDU.

SDU are hex data.


UMD PDU with 10 bit SN (Even number of LIs)

Sequence Number (SN) Length: 10 bits
Sequence Number: 1

SDU-1: 01 02 03
SDU-2: 04 05

Framing Info: 00

00: First byte of the data field corresponds to first byte of a RLC SDU & last byte of the Data field corresponds to last byte of a RLC SDU.

SDU are hex data.


Further Studies


Soft & Softer Handover In UMTS System

What are soft and softer handover in 3G UMTS mobile system?

Handovers are an important part of every cellular communication system. They are used for providing mobility in cellular architectures. In UMTS systems different handover types have been introduced to cope also with other requirements as load control, coverage provisioning and offering quality of services.

Handover aims to provide continuity of mobile services to a user traveling over cell boundaries in a cellular infrastructure. For a user having an ongoing communication and crossing the cell edge, it is more favorable to use the radio resources in the new cell – also called the target cell because the signal strength perceived in the “old” cell worsens as the user penetrates the target cell.

The whole process of tearing down the existing connection in the current cell and establishing a new connection in the appropriate cell is called “handover”. The ability of a cellular network to perform efficient handovers is crucial to offer attractive services as real-time applications or streaming media as planned in third generation networks.

Especially in WCDMA two special types of handovers have been introduced; soft and softer handovers, allowing a mobile user to use 2 separate air interface channels when being in the overlapping area of two adjacent sectors.

Soft & Softer handovers are similar in techniques but there are some differences in both the techniques.

Softer Handover

Softer handover is the situation where one base station receives two user signals from two adjacent sectors it serves. In the case of softer handover the base station receives 2 separated signals through multi-path propagation. Due to reflections on buildings or natural barriers the signal sent from the mobile stations reaches the base station from two different sectors.

The signals received during softer handover are treated similarly as multi-path signals. In the uplink direction the signals received at the base station are routed to the same rake receiver and then combined following the maximum ratio combining technique. In the downlink direction the situation is slightly different as the base station uses different scrambling codes to separate the different sectors it serves.

So it is necessary for the different fingers of the rake receiver in the mobile terminal to apply the appropriate de-spreading code on the signals received from the different sectors before combining them together.

Soft Handover

In the case of soft handover the mobile station is in the overlapping cell coverage area of two sectors belonging to different base stations.

In downlink direction the signals received from the two different base stations are combined using MRC Rake processing in the mobile station.

In the uplink direction the received signals can no longer be combined in the base station but are routed to the RNC. The combining follows a different principle; in the RNC the two signals are compared on a frame-by-frame basis and the best candidate is selected after each interleaving period; i.e. every 10, 20, 40 or 80ms. As the outer loop power control algorithm measures the SNR of received uplink signals at a rate between 10 and 100Hz, this information is used to select the frame with the best quality during the soft handover.

The Soft Handover procedure is composed of a number of single functions:

  • Measurements
  • Filtering of Measurements
  • Reporting of Measurement results
  • The Soft Handover Algorithm
  • Execution of Handover

Soft Handover Algorithm

Soft handover in practice is a complex technique. The following example will describe soft handover for best case scenario.

Before describing the above scenario we need to know three important terms.

Active Set

User information is sent all the cell belongs to Active Set. In FDD, the cells in the active set are involved in soft handover. In TDD the active set always comprises one cell only. The UE shall only consider active set cells included in the variable CELL_INFO_LIST for measurement; i.e. active set cells not included in the CELL_INFO_LIST shall not be considered in any event evaluation and measurement reporting.

Monitored Set

Cells, which are not included in the active set, but are included in the CELL_INFO_LIST belong to the monitored set.

Detected Set

Cells detected by the UE, which are neither in the CELL_INFO_LIST nor in the active set belong to the detected set. Reporting of measurements of the detected set is only applicable to intra-frequency measurements made by UEs in CELL_DCH state.

The above scenario can be devided into three different parts.

Radio Link Addition (Event 1A)

Event 1A is triggered when a primary CPICH enters the reporting range. This means when a cell is strong enough to enter into Active Set.

Radio Link Deletion (Event 1B)

Event 1B is triggered when a primary CPICH leaves the reporting range. This happens when a cell in active set become weak and needs to be removed from Active Set.

Combined Radio Link Addition & Deletion (Event 1C)

Event 1C is triggered when a non-active primary CPICH becomes better than an active primary CPICH. When this event is triggered a primary CPICH is removed from the Active Set and a new stronger cell is added into Active Set.

You can get information on other events in another article.

Soft Handover Algorithm Flow Diagram

Further Studies

5 Reasons Why Testing Is Important For User Equipments


After much evolution of telecommunication technologies we are now in a generation where mobile communication is the biggest medium of communication. Apart from biggest now Mobile communication is one of the most complex systems ever used so vastly around the globe.

In mobile communication system User Equipment (Mobile Stations) are one of the most important node.

To make sure that the mobile stations should work properly testing is a must during the whole development cycle and also after the complete product is developed.
We have documented 5 important reasons why testing is very important in mobile station development.


Reason:1 So Many Technologies

Mobile communication has a long history. Starting from 1st generation till 4th generation the technology becomes complex. For example GSM which was a second generation popular technology was developed for Voice and CS related traffic. But when the demand for data (PS) services grew different other technologies were added with GSM. These include GPRS, EDGE, etc.

When 3G was drafted during beginning of 1990s many more services were introduced. It was also decided that mobile stations will support different verities of QoS (Quality of Service), which includes Voice, PS (there are many QoS specified for PS like Background class, interactive class, streaming, etc), video telephony, SMS, MMS.

By adding so many services the system became more complex. During the evolution of 3GPP standardization many more new concepts were introduced. Some of these are IMS, MIMO, HSDPA, HSUPA, etc. These added extra overhead in the design of the mobile stations.

With introduction of LTE added a new type of air interface and new type of QoS criteria.

To make sure the mobile stations are working as per the standards with these technologies testing of each and every service type is very important. This includes signaling and data testing of each kind of services.

Testing also should be done when user equipments do handover inside the systems and also between different systems.


Reason:2 Different Network Vendors Different Configuration

The number of Network Equipment (Base stations, Core Network, RNC, etc) providers are many. Some of them are Ericsson, Alcatel Lucent, Nokia Siemens Network, Huawei, Nortel, ZTE, DoCoMo, Motorola, etc.

With so many different NW vendors it is the goal of the mobile station producers to test their mobile stations against most of them. This is because each NW vendors have their own set of implemented configuration from 3GPP standards.

This is the reason that most of the NW vendors have their own labs where UE manufactures can test the mobile stations. This type of testing is called interoperability testing. In this type of interoperability testing, UEs are tested against NW configurations in controlled environments.


Reason:3 UE Manufacturers Are Not Component Suppliers

In today’s competitive industry, it is hard for one company to focus on all aspect of mobile handset development. That is the reason why many handset manufacturers buy components from other companies. These components include protocol stacks, chipsets, cameras, etc.

So it is the responsibility of the component suppliers to check the quality of the components before delivering to UE manufacturers.
The UE manufacturers should check the quality of the end product.


Reason:4 Operators Are The New Bosses

These days it is a regular practice to buy mobiles directly from operators. Operators decide which mobile station they will sell. This is the reason why the component suppliers and the mobile manufacturers need to test their UEs in Operators labs & live environment.

This process finds out if there are some bugs or issue with the mobile station or component in the operator’s NW configuration. Some of the most common issues which can be fixed during this phase are Throughput, configuration issue, handover problems, call drop issues, etc.


Reason:5 Without Certification Mobiles Can Not Be Sold

Certifications are introduced by standardization bodies to make sure that all mobile stations should follow a minimum set of criteria before those can be released. For this reason standardization bodies like GCF created test suites and those suites are tested against the UEs. This type of testing brings out many common functionality problems in the mobile stations. This is called conformance testing.

These tests are most of the time tested against system simulators.

There are many companies they provide system simulators. These include Anristu, Anite, Rohde & Schwarz, etc.


Tricks to Read and Understand 3GPP Specifications


3GPP specifications are backbone of 3G, IMS, HSPA, Enhanced UTRA technologies. To understand a certain aspect of a protocol stack or encoding of PDUs or to study deep into physical layer one need to understand the respective specifications.

 

The specifications are developed taking into consideration that they should describe the behaviors of certain layer but the implementations in most of places are left to the developers.

For a beginner studying 3GPP specifications are really difficult. There are various reasons.


3GPP Specification Are Interlinked

Each specification in 3GPP has many referenced specifications. So when one tries to understand one specification he end up following many. This happens to many new 3GPP professionals.


3GPP Specifications Do Not Cover Examples

It is always handy to have some real time examples with the theories. As many part of 3GPP specification are left implementation dependent, they do not cover many examples.

Also encoding and decoding of PDUs also are described without examples (e.g. encoding of RLC or MAC PDUs).


Some Specifications Are Very Big

Specifications like RRC (Radio Resource Control, 25.331) are huge in size. Some of them contain more than 1000 pages. So most of time it is very hard to complete the specification.


So Many Technologies

Sometimes beginners find it difficult to know what technology to follow. As 3GPP specifications cover UMTS, GSM/GPRS/EDGE, HSPA, IMS, LTE and many other technologies, it is very hard for a beginner to know what he or she needs to read.

Apart from above few problems there are many more problems may arise while one starts following the specifications.

To understand a specification or part of the specification one need to follow some simple guidelines. These guidelines may not be the strict ones but these can help a lot while reading a specification.


Know What You Want To Read

This is the most important thing before opening any specifications. For example if you want to know detail about cell reselection, you should start with idle mode specification 25.304.

Apart from that one should know for which specification version one is looking for. The specifications are version numbered from Release 99 till Release 11. Not all NW vendors or UE manufacturer supports all releases.
So before downloading any specification from 3GPP website make sure exactly what you are looking for.


Study The Respective Specification First Then Go To The References

It is always get confused easily if you start following the references before reading the specific part.

For example you want to study about PDU structure of MAC (Medium Access Control) protocol, you should study the PDU structure from MAC specification (25.211) before going to other specification like RLC (Radio Link Control) protocol to study MAC SDU (Service Data Unit).
This way you will stick to the part what you are looking for.


Take A Printout When Necessary

It is good for the environment not to take printouts, but it is always helpful to make printout of the part you are just studying.

This works for many engineers I talked to. They like to read from paper printouts more than reading from computer screens. This is because it is always handy to write notes on the printouts and putting markers on important points.
You may use the computer screen to read the reference documents.


Follow What You Are Studying

Master of all is a good term. But it is achieved through small steps.

When you start reading a specification try to follow the whole. This way the fundamental of the protocol layer or technology can be understood easily.

If your professional career is based on RRC (Radio Resource Control) protocol try to read the main part of the specification and then the communication between Upper layers and lower layers.

Sometimes exceptions can be done here when you need to understand a small part for your work. Then you can study deeply in that part.


Examples Can Solve Your Problem

This is always true that examples can help you a lot to understand certain parts of specification.

In most of the time it is hard to get good examples. In those cases try to study and make a specific examples yourself.
For example you want to study RLC (Radio Link Protocol) AM (Acknowledge Mode) PDU structure.

Try to make an example of different way the PDU can be encoded.


Always Good To Ask

It is always good to ask questions to colleagues and co professionals when needed.

But before asking any question to other make sure that you studied the part completely so that you should not waste others time. This will make the discussion complete and relevant.