Control Plane CIoT EPS optimization

-
Home               LTE              NB-IoT          5G(NR-NSA)

Hi Guys today we are learning about  Control Plane CIoT EPS optimization in detail for NB-IoT, For more update Please visit our NB-IoT page.


Control Plane CIoT EPS optimization:


In order to reduce the total number of control plane messages when handling a short data transaction, user data or SMS messages is conveyed to the IOT services via MME by encapsulating them in NAS messages.

There are two paths through which, user data or SMS can be transmitted on the Control Plane CIoT EPS optimization:
  • UL data are transferred from the eNB (CIoT RAN) >> the MME >> the Serving Gateway (SGW) >> the Packet Data Network Gateway (PGW) >> IOT Services


  • UL data are transferred from the eNB (CIoT RAN) >> the MME >> the Service Capability Exposure Function (SCEF)(only for non-IP data packets) >> IOT Services.



In both the cases mentioned above, DL data is transmitted over the same paths but in the reverse direction.

In these cases, since data packets are sent on the signaling radio bearer (SRB), there is no need for data radio bearer (DRB) set up.

For small data transmission between the MME and S-GW, a new interface named S11-U is introduced as a part of control plane CIoT EPS optimization.

The SCEF, a new node designed especially for machine type data, is used for delivery of non-IP data over control plane and also provides an abstract interface for the network services like authorization and authentication, discovery and access network capabilities.

Data transfer of both IP and non-IP data follows the conventional path in Control Plane CIoT optimization. It is transmitted over data radio bearers through the SGW and PGW, to the CIoT application services.Structure-wise the access network in NB-IoT is the same as LTE.

In the Control Plane CIoT EPS optimisation, the exchange of data between the UE and the eNB is done on RRC level. Here the DL data packets can be piggybacked in the RRCConnectionSetup message or in the RRCConnectionSetupComplete message for UL. If this is not enough, DLInformationTransfer and ULInformationTransfer can also be used for data transfer.

All these messages contain a byte array which has NAS information, which corresponds to the NB-IoT data packets in this case. The dedicatedInfoNAS between the eNB and the MME is exchanged via the S1-MME interface. As a result, it is transparent to the eNB, and the UE's RRC directly forwards the content of the received DLInformationTransfer to its upper layer. For the data delivery method, Security on AS level is not applied. As data is transferred via NAS messages, there is no RRC connection reconfiguration. It may either start immediately after or during the RRC connection setup or RRC Connection resume procedure, respectively due to termination of the RRC connection after RRC connection release.

If the operator supports SCEF, then MME uses SCEF based delivery mechanism for Non-IP data.First a PDN connection is established towards the selected SCEF which is also known as an "SCEF Connection".

Note: For SCEF based delivery, the APN used is an FQDN, which either resolves to an SCEF hostname or to an SCEF IP address.


Comments

Post a Comment

Popular posts from this blog

5G Deployment Option-3/3a/3x

-
Image
Home                 LTE                NB-IoT            5G(NR-NSA)   Hi Guys today we are learning about 5G deployment options, if you want to know more about other 5G deployment option please  click here Option 3: EN-DC (EUTRA-NR Dual Connectivity) Option 3 represents a network having both LTE and NR radio access, but using only the EPC core of LTE to route the Control signals. In this option, LTE is used as the control plane anchor for NR, and both LTE and NR are used for user data traffic.(user plane). It could also be called as Non-Standalone (NSA) NR in Evolved Packet System. The only difference between Options 3 and 3A is based on whether the user plane data is sent to NR directly or via the LTE RAN. This standardization was concluded in 3GPP Rel-15. This is a possible first step in the migration towards 5G-SA. This option will be most attractive for operators which have early deployments of 5G NR access systems in areas where legacy eNB and EPC a
Read more

DC Carrier in NR

-
Image
Home                 LTE                NB-IoT               5G(NR-NSA) In this article, we will learn the basics of DC Carrier and why it is needed. Why in NR, DC subcarrier is not reserved like LTE? With legacy LTE (4G) it was decided that all devices (UE) should be capable of the maximum carrier bandwidth of 20MHz (UE can also support 10/15/5/3 MHz). This was a reasonable assumption at the time given the relatively modest bandwidth compared to NR, Whereas NR is designed to support very wide bandwidths up to 400MHz (for FR2) and 100Mhz (for FR1) for a single carrier. As well as NR supports multiple numerologies on the same transmitted carrier frequency. It is not necessary that all devices can support up to 400 MHz Bandwidth, hence in NR BWP concept is introduced. (To learn more about BWP Click here ). Note: in the above and below NR case figure, we assume that for each and every BWP have configured some  txDirectCurrentLocation  value.     As shown in the a
Read more

5G Deployment Option-7/7a/7x

-
Image
Home                 LTE                NB-IoT            5G(NR-NSA) Hi Guys today we are learning about 5G deployment options, if you want to know more about other 5G deployment option please  click here Option 7: Deployment Option 7 represents a deployment scenario in which the Next Generation Core (NGC) will be used with a mixture of LTE and NR radio.  Next Generation signaling will be used but it will be routed via the LTE RAN because the LTE network is more fully built out and thus more reliable for handling signaling.  Options 7 and 7a differ on whether the user plane data is sent to NR directly or via the LTE RAN. 7/7A/7X require an eLTE upgrade of the existing LTE network at the start. (Difference is UP path Non Standalone ( Dual Connectivity 4G/5G ) Option 7/7A: NSA NR in 5GS. This option is particularly attractive for areas in which legacy LTE eNBs and the EPCs are ready to be upgraded to ngeNBs and the 5GCs.  From the point of
Read more

Authentication in LTE

-
Home                 LTE                NB-IoT            5G(NR-NSA)   What is Authentication and what type of Authentication is used in LTE? Authentication is a process by which both the UE and Network check whether the other party is authorized to communicate with them. In LTE and WCDMA, a mutual authentication process is used i.e. the Network checks whether the UE is authorized to camp on it and the UE also checks whether it is trying to camp on is the correct Network. The UE becomes authorized to camp on a network by subscribing to the network. In LTE, EPS AKA i.e. Authentication Key Agreement procedure is used for Mutual Authentication. Why is Authentication required from both sides in LTE? The UE needs to be authenticated by the NW to check whether it has subscribed to the NW or not. Only UEs which have a valid subscription should be allowed to camp on the NW. The NW should also be authenticated by the UE because if the UE does not check its
Read more

DRX (Discontinuous Reception)

-
Image
Home                 LTE                NB-IoT            5G(NR-NSA)   What is DRX and DRX active period? What channels does it monitor in active period? Data transmission between UE and their base stations(eNodeB) uses radio frames with10ms duration, where in each radio frame consists of 10 1ms( 1 frame=10ms duration=10 subframe) subframes. Physical Downlink Control Channel (PDCCH) at the beginning of each subframe indicates whether there is data for UE to receive or not. Devices has to monitor these PDCCHs in each subframe so that it can find out whether they carry any data to receive. Because devices do not receive data in every subframe, this monitoring process naturally leads to high battery consumption.  What is the purpose of DRX? The main purpose of DRX is to lower battery consumption when there is no UL/DL data. means, when there is no traffic(DL/UL) that time devices enter into sleep mode (with RF module turned off) for some period of time as configured by
Read more

Soft Handover vs Hard Handover

-
Home                 LTE                NB-IoT            5G(NR-NSA) Now before we move to other things like measurements in handover, handover decision, handover procedure, handover interruption time, and mobility robustness optimization, let us take a look into difference between soft handover and hard handover. Soft Handover Hard Handover The handover in which radio links are added and removed in a way that MS always keeps at least one radio link to the UTRAN is known as soft handover. The handover in which all the old radio links in MS are removed before the new radio links are established is known as hard handover. This can also be simplified as make before break This can also be simplified as break before make As call drop rate is lower this handover is used to lower the rate of call drop. In this case higher rates of call drops are found Why soft handover is not included
Read more