Unlock all 17 lessons of Overview of 4G Networks and evolutions to 5GFull course ₹40,000 · paid
LTE Protocol Stacks and Logical, Transport and Physical Channels
A free lesson from Skill-Lync's Overview of 4G Networks and evolutions to 5G course, on Grow by Skill-Lync · Last updated 16 Nov 2026 · Session: “Week 1 Session 2”
What will you learn in this free Overview of 4G Networks and evolutions to 5G lesson?
The instructor compares the LTE control plane and user plane stacks, then describes the role of RRC, NAS, PDCP, RLC, MAC, S1AP and GTP. The lesson ends with logical, transport and physical channels and how each maps to the next in downlink and uplink.
- Control plane versus user plane protocol stacks
- Functions of RRC, NAS, PDCP, RLC and MAC
- Logical, transport and physical channel types
- Downlink and uplink channel mapping
What comes after lesson 2?
The next free lesson is lesson 3, “LTE Initial Cell Search: PSS, SSS, MIB and SIB Messages” (26 min). Later in Skill-Lync's Overview of 4G Networks and evolutions to 5G course (paid): lesson 4, Week 1 Session 4; lesson 5, Week 2 Session 1; lesson 6, Week 2 Session 2. The full course has 17 lessons (7 h 11 min of video); see the course overview or its price and syllabus.
Lesson transcript
Machine transcript of the lesson audio (lightly cleaned). Technical terms may contain errors; the video is the reference.
Hi, in this course, Overview of 4G Networks and Evolutions to 5G. Week 1. Let's do a quick recap, whatever we discussed in the last session. So we discussed about LTE frame structure, where we discussed about two types of frame structure. Type 1 is for FDD and Type 2 is for TDD, where we saw like both Type 1 and Type 2 is having 10 millisecond of radio frame or system frame that is divided into 10 parts, each having 1 millisecond of subframe and then further divided into two parts, that is 0.5, 0.5 time slot in each SF and then its time slot was having 6 or 7 OFDM symbols depending upon cyclic prefix, normal or extended.
Then we discussed about LTE resource block and resource element. What is a resource element? There we discussed about one subcarrier and one OFDM symbol is resource element and one resource block is having 84 resource elements for normal CP and 72 for extended. Then we discussed about LTE bearers, where we discussed about EPS bearers, ERAP bearers, DRBs, default bearers and dedicated bearers. Then we discussed about LTE quality of service. As part of QoS, we discussed about functionality of QoS, how this is applied in LTE, what is GBR and what is non-GBR bearers, what is the difference between a guaranteed bitrate and non-guaranteed bitrate bearers.
Then we discussed about cost class identifier. So each bearers is having one QCI ID. So that QCI table we discussed where we saw that there are different IDs for GBRs and different IDs for non-GBRs. So these are the table of contents for today's discussion. So today we'll be discussing about LTE protocol stack. As part of that, we'll discuss about control plane stack and user plane stack. We'll see that what protocols are there as part of control and what protocols are there as part of user in UE, in radio systems, in U-Tron, in EPC and further.
Then we'll discuss about various channels. As part of channels, we'll discuss about physical channels, transport channels and logical channels. Then we'll see the mapping, how a logical channel maps to transport and how transport maps to logical and other way around. So DL is having mapping from logical to transport to physical and U-L is having the other way around, that is physical to transport to logical. Then at the end of the session, we'll discuss about the summary, whatever we'll be discussing as part of today's. So these are the learning objectives. So for the students to understand LTE protocol stack, including the control plane and user plane stacks, and to learn about LTE channel mappings and also need to understand various channels available and what is the use of having a channel in LTE.
So let's start our very first topic of today's is LTE protocol stack. So this is LTE control plane stack. So here there's no any data involved. So whatever here you are seeing, the mapping is a control plane stack. So in the UE, so UE and MME, this are connected via NAS protocol. You can see here. So NAS to NAS. NAS is basically non-access stratum. Non-access means this is not accessible to E-NodeB. So all the, you know, protocols of E-NodeBs are called AS, that is access stratum.
But the protocols of MME which talks to UE is NAS. Although it goes through E-NodeB itself, but E-NodeB doesn't have access. It is transparent to E-NodeB. Okay. So it is mainly for the UE, directly for the UE and whatever UE is also sending as part of NAS signaling, it is mainly for the MME. Then here you can see between RRC and RRC, PDCP, PDCP, RLC, MAG, PHY, this all having the functionalities of control plane. And between E-NodeB and MME, S1AP talks to S1AP as we know that S1AP is a mainly interface between MME and E-NodeB.
Then it has to go through HCTP transport, IP, L2 and L1. The next is MME to S-gateway. Between MME and S-gateway till transport layer, it is same, L1, L2, IP and UDP. Then there is a GTP-C stack. Okay. This is tunneling protocol. So GTP-C and GTP-U both are there. C is for control plane, U for user plane. User plane we will see in the next slide. And same stack is here as well to talk from S-gateway to P-gateway. That is L1, L2, IP, UDP and GTP-C. So GTP-C is talking to GTP-C here in IP. So for example, let's say P-gateway has to send any data.
So first it has to put GTP-C header. It will go through UDP, IP, L2, L1. It will come to S-gateway. Again, L1 will do its own processing. Then L2, then IP, then UDP and then GTP-C. It will do its own processing. Then next is X2. In the X2 protocol, we have this between E-NodeB to E-NodeB. So this is mainly the X2AP protocol. This also uses S-CTP as transport and IP, L2 and L1 underlying layers. This is LTE user plane stack. So for the user plane, as you can see here, there is no NAS signaling between EPC and UE.
So for the user plane stack, there is no any direct communication between UE and EPC. So here the application is sitting. As you can see, it is directly mapped to the PDN. So PDN application has to talk to the UE application. And here you can see there is no RRC because RRC doesn't have to do anything with the data. So for data, mainly PDCP, RLC, MAC and PHY will be involved. In the E-NodeB and S gateway, you can see here all the GTP-C has been replaced with GTP-U.
And underlying layers will still be same UDP, IP, L2, L1 because these all layers are involved in both control plane and user plane. Similarly, here also at the P gateway, this GTP-C has been replaced with GTP-U. And on top of GTP-U, there is an IP header. IP talks to the UE's IP protocol only for data. And this IP again has to talk to PDN, PDN IP. So IP to IP protocol for the data. In the X2 connection again, to transfer any user data, there is GTP-U itself is being used.
So as in the earlier slide we saw here for the X2, it was X2AP over SCTP. But here GTP-U over UDP. Here transport is UDP for the data. So let's understand one by one protocols. Let's start with RRC. So the first protocol stack, whatever we will be discussing is RRC. So RRC is mainly used for broadcasting of system information. So it keeps on broadcasting all the system information which is common to all the UE's mostly. So this system information which is being broadcast, that is common for all the UE's.
Any UE's coming in the system has to read this. Next is RRC connection establishment and release between UE and UTRAN. So we will see what is RRC connection. But till this point, let's just understand that RRC is responsible for establishing a connection and releasing a connection between UE and UTRAN. Then it has to do measurement configuration, control and reporting. So this is for the handover. So RRC, you know, does the all the configurations part for the measurement. UE has to do the measurement reporting. So it has to control it.
RRC does all the configuration that how will you report, where will you report, when will you report, all those things. Next, then radio link failure also reported by RRC as part of RRC re-establishment. Then RRC connection configuration. So let's say UE is already attached to a network and it has to, you know, network has to change some parameters in the UE. So any of the layer takes help from RRC. It tells the RRC that this is what I want to change. OK, and then RRC does the RRC connection and reconfiguration.
It will send the reconfiguration message to the UE and UE has to send an acknowledgement for that as part of RRC connection and reconfiguration complete. Next is NAS protocol. So NAS protocol, as we discussed, is a non-access stratum and this is between UE and your EPC. So this plays a role to authenticate and do the security procedures for the UE. It does the identification procedure. It helps in mobility management and bearer management functions. Mobility management is again part of. For your handover functionality. Then attach and detach procedures. So whatever attach, complete, attach, request, attach, accept, detach, request, detach, accept, complete.
All is handled by this NAS protocol. Then tracking area updating procedure, service request, EPS bearer, context activation, deactivation and the modification. So EPS bearer we already discussed as part of bearer in LTE. So the activation and deactivation is done by NAS and also it can do the modification procedure for the EPS bearer context. Next is PDCP. So PDCP is part of eutron that part of eNodeB. It is the topmost layer for the data plane PDCP. Transport of user data and control plane over the radio link. It is a part of both user data and control plane.
So in the control plane, there is one more layer RRC that is already discussed. So PDCP is a part of both user data and control plane. So user data, any user data coming to eNodeB directly comes to the PDCP, but control has to come via RRC. Then the header compression. It does the header compression to, you know, do the efficient transmission, you know, to faster transmission. It has to do the header compression. Access start-up security. So whatever security happening between UE and eNodeB, that has to be done by PDCP as part of ciphering and integrity protection.
User data ciphering. So integrity is for only for control data, but ciphering is for user data as well. Next is RLC. So RLC is, you know, doing the transferring of upper layer peer use. So upper layer data, whatever is coming to RLC, it is transferring to the lower layers. Then error correction through ARQ, automatic repeat request. So error correction also it has to do. So RLC will be discussing about different modes. So in the AA mode, it does the error correction as part of ARQ by means of acknowledgement of each and every peer use.
Concatenation, segmentation and reassembly. So concatenation and segmentation done at the transmitter side of RLC and the reassembly of RLC SDUs has to be done at your receiver side. So this is applicable for both UM and AM mode. Then buffer equipancy report to scheduler. So whenever this EnodeBee is receiving any data for any of the UE or any of the bearer, it has to report that to the scheduler that I have this much occupancy in my buffer. You need to schedule it. Then the next is MAC. This is the most important protocol of radio side.
It does the mapping between logical and transport channels. So in the earlier slides, we just saw that logical channels has to be mapped to transport channels. So that is being done by MAC. Multiplexing and demultiplexing of SDUs. It can multiplex multiple SDUs in one transport block and it has to do the demultiplexing again at the receiver side. It does the HARQ, hybrid ARQ, we'll be discussing in the coming slides. This is also one error correction mechanism. Then priority handling between logical channels of a UE and between UEs. So it has to decide the priority based on the QOS that what should be the priority of which logical channel and which UE should be prioritized over which UE.
Dynamic allocation to radio resources to UE and perform QOS. So it has to do the dynamic allocation of the resources in terms of RBs to all the UEs. Okay. And it has to perform the quality of services. Next is S1AP. So S1AP, as we know, it is interfaced between E-NodeB and EPC. So S1MME is interfaced between E-NodeB and MME and S1U is between your E-NodeB and S-Gateway. So S1MME, this is a control plane protocol stack between U-Tron and MME. S1AP uses SCTP as transport. We just saw in the diagram that below S1AP, there is SCTP as transport layer protocol.
So, you know, you can map it from OSI layers what we discussed in the very first session that what all part of transport layer. So this SCTP is also part of transport layer which we are using here. S1U is reference point between E-UTRA and NSGateway for per bearer user planning, user plane tunneling. Okay. So let's say one U is having two bearers. So there has to be two different user plane tunneling. Okay. GTPU V1 uses UDP as transport. Okay. So we saw like in case of S1AP, SCTP was the transport. Okay.
But in case of GTPU, it uses UDP as transport for the data. Next is X2. X2 is reference point providing control and user plane between E-NodeBs. So for control plane, X2AP uses SCTP as transport and for user plane, GTPU uses UDP as transport. That we saw in the diagram. In the control plane, we saw that below X2AP, SCTP was sitting and instead of X2AP, it was GTPU for user plane and below GTP, UDP was there as transport. Then GTP that we already discussed that GTP is having two parts, GTP-C and GTP-U for control plane and user plane.
GTP-C allows exchanging of control information in order to create, modify and terminate GTP tunnels. Okay. And once the tunnel is created, then GTP-U helps forward user IP packets over S1U, S5 and X2 interfaces. And also it uses end marker to identify the last package transferred. That is used in case of handover. We'll see exactly how this end marker is been. Now next is LTE channel mappings. LTE channels. So channel is a medium to transfer data across various RAN protocol stacks. Okay. So we could have just one channel if you just had to transfer the data. Okay. But why there are different channels?
So used to segregate different types of data. So there could be, we have categorized different type of data that is control data, dedicated data, broadcast data. So, you know, to segregate this kind of data, we have different types of channels. So first, we'll discuss about different types of channel. One is physical channel. Physical channel is basically air interface. As you can see here, from PHY onwards, it is physical channel. Between MAC and PHY is transport channel. And between RLC and MAC is logical channel. So let's first discuss about logical channels.
So these are the logical channels. PCCH, BCCH, CCCH, DCCH, and MCCH. So PCCH, it is used for paging the UE. PCCH is used to broadcast MIB and SIB information. That is master information block and system information block. This we'll see in the detail. But here just we need to know that PCCH is used for broadcasting this information to all of the UEs. CCCCH is whatever data which is common to the multiple UEs has to go through CCCCH. And DCCH is basically dedicated control information for a particular UE.
MCCH helps transmit information for multicast reception. Okay. This multicast reception also we'll see later. Then logical traffic channels. Logical traffic channels is DTCH. It is used to dedicated traffic. It is used for dedicated traffic for a particular UE. And MTCCH is used to transmit multicasted. Downlink transport channels, PCH. PCH is used for paging. So, till here, all the, you know, logical channels we discussed. So, these were the control channels. These were all the control channels and these were all the data channels. Okay. The traffic channels. Now, next is transport channels. So, in transport channel, we'll be discussing about downlink transport channels and the uplink transport channels.
So, downlink transport channel is PCH used for paging. BCCH used for MIB and it gets mapped to BCCH. BCCH we discussed about as part of logical channels. Then DLSCH, it is used for SIB and data transfer. So, you can see here, if I go back to the previous slide, from the BCCH, both the broadcasting information like MIBs and SIBs comes through. BCCCH channel. But here, MIB gets mapped to BCCH, but for SIB, this DLSCH. So, basically, the MIB is mapped to BCH and SIB is mapped to DLSCH of the transport.
Then is MCH. It is employed to transmit MCCH information for setting up multicast transmissions. Uplink transport channels are RACH. This is used for the initial access. Helps obtain initial access to the network, random access procedure. Then ULSCH, it is used for UL data transfer. These are the physical channels. So, physical channels is PBCCH. It is used for transmitting MIB. So, whatever data as part of broadcast is coming, that is transmitted over PBCH, but only the MIB, not the SIBs. So, SIB and the data has to be transmitted over PDSCH.
Then PMCH is used for multicast channel. PHICH. PHICH is used to send acknowledgement for the data received in UL. So, for... HARC, AAC, and NAC, it has to be used, PHICH. If we have to send any acknowledgement for HARC procedures, then we use this channel. PDCCH is used to send the control information. So whatever a UE needs to decode the data or needs to decode any information, first we send the control information for that, that where is your data, what kind of data you are going to receive. So that all control information has to go on PDCCH.
These are the physical channels in UPLINK. So in UPLINK, there is PRACH. This is used for transmission of random access preamber. So this channel is being used by the UE to send the random access. Okay. During the initial attach, UE has to first do a random access. So it uses this particular channel. There is a separate channel only for the random access procedure. Then PUSCH. PUSCH is basically, it is similar to PDCCH. PDCCH is for downlink data and PUSCH is for uplink, uplink data. But PDCCH cannot hold, you know, the control information.
It has to only hold the user information, but PUSCH can hold both UL control and user information. And PUSCH is very similar to PDCCH in downlink. PDCCH control the DCI, that is downlink control information. Here, PUSCH holds the uplink control information, which is called UCI. So as part of uplink control information, there are SRs, HARC, CQI. SRs is the scheduling request. Let's say UE has to ask for the grant or for any kind of scheduling. Then it has to do the scheduling request and it will happen through PUSCH channel.
Then the HARC procedure. HARC, now you will say that we already had a PHI-CH for HARC related feedback. Why this is required? PUSCH also. Okay. So PHI-CH is a dedicated channel. It is a separate channel. Dedicated means it is a separate channel only for this HARC acknowledgement in the downlink. So in the downlink, if you are sending HARC, it means you are doing acknowledgement for the uplink data. But there can be some downlink data as well, right? So you have to send HARC related information, HARC acknowledgement in uplink as well. So how will you send that? You cannot send. PHI-CH is only for downlink, right?
So you use this channel. So basically this PUSCH is being used by the UE to send the HARC information. And then the CQI. CQI is channel quality indicator. So when UE has to report the channel quality, the quality of the channel, then it uses the PUSCH as, you know, to carry the uplink control information. So this is the mapping for DL channels. So here you can see all the channels, whatever we discussed is PCCH, BCCH, CCCH, DCCH, DTCH, MCCH, and MTCH. Okay. These are the logical channels and these are the transport. Transport channels are PCCH, BCCH, DLSCH, and MCH and PHI-CH, PMCH, PCFCH, PDSCH, PBCH, and PDCCCH.
These are the physical channels. Now see, this is very important to understand the mapping. You can see here, as we discussed that PCCH is used for the paging. So PCCH directly go to the PCH for paging and the paging has to, you know, go through PDSCH. So there is no any separate channel for paging in physical. Okay. So all the paging has to happen via PCCH, PCH, and PDSCH. Next is BCCCH. So BCCCH, we know that it is used to broadcast SIB and MIB. But why BCCCH is mapping to BCH and DLSCH?
So that we already discussed that the MIB information is broadcasted from BCCCH to BCH. Okay. And the same MIB has to be broadcasted from BCH to PBCH. But the SIBs segregated from BCCCH to DLSCH. And DLSCH has to be broadcasted via PDSCH. Okay. And CCCH for common control channel and dedicated control channel, DTCH, MCCH, and MTCCH. This all has to map through DLSCH. So whatever data coming on this channel has to go through DLSCH on the transport channel. But still, there are few scenarios where MTCH is having MCH and DLSCH.
So again, here we have a separate kind of segregation similar to BCCCH that few has to go via DLSCH and few has to go via MCH. Now, whatever data coming to MCH has to go directly to the PMCH in the physical channel. And whatever data coming to DLSCH. So, you know, as we saw that in the DL at the file here, there is just one channel PDSCH which control, I mean, which has the user information, which has the user data. So, all the data which is coming through DLSCH and through PCH has to go through PDSCH. Okay. PBCH will again, it is as you would have understood that this is only for the MIB transmission.
And okay. So, this PCFICH, PCFICH will discuss in detail. This is a control format indicator which tells about the control information. It tells the information for the PDCCCH that how many symbols is required for PDCCCH. That we will see later. But this is not getting mapped to any of the channel because it doesn't need to go through transport and, you know, to logical channel. PDCCCH that we saw like it is used for DCI information. It is for sending DCI information. So, whatever DCI we are creating here, that control information has to go through PDCCCH.
And PHICS for the HARC information. Okay. Now, these are the UL channel mappings. So, in the UL channel mappings, let's go from down. So, here you can see that PUCCH is through, now UCI is going through PUCCH and the same has been mapped to PUSCH as well. So, if you go to the last slide. PDCCCH is having only DCI or you can say DCI is having only PDCCCH. Okay. So, means downlink control information cannot be carried by PDSCH, the shared channel, only by the PDCCCH. But, as we discussed that UL, uplink control information can be carried either by PUCCH or PUSCH. So, you can see here the mapping. Then all the information, whatever going through PUSCH has to go to ULSCH and here it will be segregated like it is for either DTCH, data traffic channel, dedicated traffic channel, dedicated control channel or common control channel. Okay.
And PRACH is move, you know, PRACH will be mapped to RACH. So, PRACH is a physical channel and RACH is transport channel. So, why it is not going here? Because RACH is a MAC layer procedure. So, it doesn't need to go to the RLC because you know that logical channel is between MAC and RLC. So, there is no any mapping through the logical channel for RACH because the RACH has to be responded back from MAC itself. So, it doesn't have to go to this level. Okay.
So, that is it from today's session. We will quickly summarize whatever we discussed today. So, we discussed about various protocol stacks. As part of that, we discussed about LTE control plane stack. Then we discussed about LTE user plane stack. Then we saw the difference that what is there in the control, what is there in the user and what all the protocol stacks which are common to the control and user both the plane, both the stacks. Then we discussed about LTE channels. Then there we learned about what is the channel, why it is being used and why there are different channels required. Then we discussed about various physical channels. So, as part of physical we discussed about downlink physical channels, uplink physical channels.
Then we discussed about the channels which is between RLC and MAC. Then we discussed about logical channels that is between RLC and MAC. Then we saw the mapping of the channels in DL and UL. So, how in DL logical channel what all channels map to which transport channel and which transport channel map to which physical channels. Then in uplink again at the receiver side we saw like what all physical channels map to which of the transport channels and which transport channel maps to which of the logical channels.
So, that is it from today's session. Thank you for joining.