{"id":9760,"date":"2020-08-15T10:15:12","date_gmt":"2020-08-15T06:15:12","guid":{"rendered":"https:\/\/techxmedia.com\/?p=9760"},"modified":"2025-04-16T15:42:40","modified_gmt":"2025-04-16T11:42:40","slug":"iot-in-5g-network-research-by-jayakumar","status":"publish","type":"post","link":"https:\/\/techxmedia.com\/en\/iot-in-5g-network-research-by-jayakumar\/","title":{"rendered":"IoT in 5G Network \u2013 Research by Jayakumar.S PhD \u2013 Part 1"},"content":{"rendered":"\r\n
\"IoT-in-5G-Network-1-techxmedia\"<\/figure>\r\n\r\n\r\n\r\n

Network Application containers from Kaloom and IEEE 1451 team run on Openshift with support from OpenPower CPU and Tofino 2. Satellite broadband is emerging to support IoT<\/a> across the globe. 5G<\/a> provisioned mMTC (massive Machine Type Communications) and Low latency for IoT events. 4G is trying to keep VM in business but Openshift is using Container technology and Kubernetes to emerge as a modern platform in Edge-Native Cloud and also in Core\/ Center Cloud<\/a>.\u00a0\u00a0Fiber to the Home might become Fiber to the Edge. IEEE1451 provides an amazing framework for a huge number of smart sensors to work towards an objective which is defined in the Application layer in Edge-Native Cloud. Kaloom provides Network applications that help Edge-native applications handle the Communication part efficiently.<\/p>\r\n\r\n\r\n\r\n

    \r\n
  1. Why 5G good is for IoT enabled Service?<\/strong><\/li>\r\n<\/ol>\r\n\r\n\r\n\r\n

    Digital Platform based services require complex infrastructure that includes Sense, Communicate, Compute, Store, and Share results. IoT applications with cameras as sensing elements generate good amounts of data. 5G provides a fast communication link such that applications can access sensor data and communicate results to those subscribed to the same service within the order of 10\u2019s of milli seconds or less.<\/p>\r\n\r\n\r\n\r\n

    \r\n
    \"IoT-in-5G-Network-2-techxmedia\"<\/figure>\r\n<\/div>\r\n\r\n\r\n\r\n

    In the above figure, details on 4G and 5G based link service for application is illustrated. Evolved Packet Data (EPG) is the core of data links which are used by applications. In 5G, User Plane Function (UPF) and Session Management Functions (SMF) together provide required functions for Data to Applications. It appears that 5G provides 100 times more data rate compared to 4G networks.\u00a0\u00a0In 4G, Release 13 (R 13) onwards there is support for narrow band IoT.\u00a0\u00a0However, that appears to be good for sensor networks that generate data in the order of kilobytes per second.\u00a0\u00a0Moreover, there is no commitment from network on network delay during data travel from sensor to application.\u00a0\u00a0There has been an option to deploy intelligence along with sensors such that inference will travel to Applications instead of full data.\u00a0\u00a0<\/p>\r\n\r\n\r\n\r\n

    2.<\/strong> IoT enabled Service Delayed by 4G?<\/strong><\/p>\r\n\r\n\r\n\r\n

    EPG service is carried out by using Virtual Machine (VM) or dedicated Bare metal server.\u00a0\u00a0\u00a0Setting up a given VM will take in the order of seconds time taken to create a VM depends on the steps involved and time you take to fill in the options…On an avg when you fill the details and click on finish on the last step is should not take more than 30 secs…15 secs on an average…..similarly powering on a vm\u00a0etc takes almost 30 sec to 60 sec depending on the hardware. After setting up VM then there is a need to deploy applications and that also might take an equal amount or more to download all dependencies from the web and make VM to handle EPG traffic. The mentioned setup time of VM is insignificant if EPG continues to use VM for an hour or more for given application data transportation.\u00a0\u00a0In case, data time itself is for 10 seconds or less (which is a normal case in IoT) then the above mentioned setup time is not good for application.\u00a0\u00a0Moreover, it may not result in good business sense as well. But for non-IoT applications such as Movie download and browsing, the above time for setup will not create any issues.<\/p>\r\n\r\n\r\n\r\n

    3. <\/strong> IoT Data Handling in 5G<\/strong><\/p>\r\n\r\n\r\n\r\n

    In 5G, it is recommended to have Cloud Native application to handle UPF which is high bit rate data traffic.\u00a0\u00a0Data traffic in SMF might be low bitrate and thus it is not an issue in handling the same.\u00a0\u00a0Deploy a container image on an OpenShift cluster to make the application easier to manage, scale, connect and monitor.<\/p>\r\n\r\n\r\n\r\n

    Shifting from virtual machines to Docker containers allows developers to deliver changes in a fraction of the time. And once an app is in a container<\/a>, it\u2019s portable. So the team can move it freely from any Cloud service providers. Kaloom provides switch fabric to handle UPF in real-time. Moreover, three is provision to program Kaloom fabric for a given\u00a0\u00a0data traffic in UPF. Thus time required to start serving UPF tatta traffic in the order of sub millisecond.<\/p>\r\n\r\n\r\n\r\n

    IoT applications will benefit from Kaloom fabric to handle data traffic in UPF.\u00a0\u00a0Moreover, to handle SMF, there is no need to have a separate controller. In Kaloom fabric SMF is also done by scripting. Thus there is a possibility to handle IoT data traffic in real time and applications continue to provide service in real time.<\/p>\r\n\r\n\r\n\r\n

    Kaloom platform includes its software-defined fabric (SDF), virtual router (vRouter), virtual switch (vSwitch), and virtual gateway (vGW). The platform sits between orchestration, an SDN controller, or a spine controller and the application servers or storage servers in a data center. It offloads data plane functions from virtual machines (VMs) and containers to gain throughput and reduce latency. zero-touch provisioning of the virtual network and components is able to reduce set-up time from several days to minutes. This also allows for the network components to receive automatic updates during runtime.<\/p>\r\n\r\n\r\n\r\n

    4.<\/strong> IoT Edge Configuration<\/strong><\/p>\r\n\r\n\r\n\r\n

    End to End (E2E) service creation and management the same till end of created E2E service. Mentioned E2E services include the following sub systems to handle full workflow that are linked with IoT Sensors, IoT Edge at one side and other side with Cloud native applications that run in Cloud.\u00a0\u00a0<\/p>\r\n\r\n\r\n\r\n