Description:FIELD OF INVENTION
[001] The field of invention generally relates to wireless communications. More specifically, it relates to a system and method for converting Internet of Things (IoT) device to 5G network enabled device through 5G IoT Gateway using gNodeB with IP interface instead of RRC.

BACKGROUND
[002] 5G technology is often seen as a suitable common platform for connecting various devices, including both mobile devices and IoT devices, due to its high-speed data transmission capabilities, low latency, and capacity to handle a massive number of connections simultaneously. In the IoT (Internet of Things) world, there is a growing need for devices to be connected through a 5G common platform to ensure interoperability and ease of scalability.
[003] Currently, existing systems do not succeed in harnessing the potential of the cloud to deliver 5G capabilities, enhancing connectivity options, and utilizing IP gNodeBs. These hurdles hinder the realization of devices that can achieve similar interoperability to 5G devices, consequently eliminating the necessity for physical SIM slots.
[004] Other existing systems have tried to address this problem. However, their scope was limited to including 5G-Stack and SIM, in most IoT devices and there is lack of 5G capabilities.
[005] Thus, in light of the above discussion, it is implied that there is a need for a system and method to enable IoT devices to function as a 5G device, which is reliable, efficient, scalable, and does not suffer from the problems discussed above.

OBJECT OF INVENTION
[006] The principal object of this invention is to provide a system and method for converting Internet of Things (IoT) device to 5G network enabled device.
[007] A further object of the invention is to provide a universal identification of IoT devices via usage of e-SIMs for the devices which can’t hold SIM/USIM/eSIM.
[008] Another object of the invention is to enable non-5G devices to function as 5G devices without the need for hardware changes by remote UE stack implementation. Additional module helps device to pass the required NAS messages through IP, instead of RRC.
[009] Another object of the invention is to easily incorporate the latest 3GPP upgrades, features and functionalities.
[0010] Another object of the invention is to provide cloud-based or remote SIM provisioning for simplified device identification and service provisioning.
[0011] Another object of the invention is to provide reduced downtime and alternative server connectivity.
[0012] Another object of the invention is to provide multi-vendor connectivity capability to ensure independence from specific suppliers, promote flexibility and vendor diversity.
[0013] Another object of the invention is to provide the 5G system that can leverage existing utilities such as OSS (Operations Support Systems), BSS (Business Support Systems), billing systems, NMS (Network Management Systems), and IMS (IP Multimedia Subsystem), reducing implementation costs and complexity.
[0014] Another object of the invention is to provide the system and method that can access the broadcast services, such as TV and radio broadcasts, thereby expanding the range of services available to users.
[0015] Another object of the invention is to provide improved visibility and discoverability within the 5G network by registering IoT servers to the NEF/NRF (Network Exposure Function/Network Repository Function).
[0016] Another object of the invention is to provide a 5G system that supports interoperability, allowing for the addition or removal of different vendor components, promoting flexibility and choice.
[0017] Another object of the invention is to provide the system and method that can leverage 5G advantages such as IoT slicing, SLA QoS (Quality of Service), and increased speed, improving the overall quality and performance of IoT services.
[0018] Another objective of the invention is to provide cross connectivity to any IoT network, allowing for continuity of operations even if one server is down.

BRIEF DESCRIPTION OF FIGURES
[0019] This invention is illustrated in the accompanying drawings, throughout which, like reference letters indicate corresponding parts in the various figures.
[0020] The embodiments herein will be better understood from the following description with reference to the drawings, in which:
[0021] Figure 1 depicts a system for converting Internet of Things (IoT) device to 5G network enabled device, in accordance with an embodiment of the present disclosure;
[0022] Figure 2 depicts block diagram comprising sub-components of the system, in accordance with an embodiment of the present disclosure;
[0023] Figure 3 depicts a method for converting Internet of Things (IoT) device to a 5G network enabled device, in accordance with an embodiment of the present disclosure; and
[0024] Figure 4 illustrates a method for sending registration and deregistration requests by the IoT to the aggregator, in accordance with an embodiment of the present disclosure.

STATEMENT OF INVENTION
[0025] The present invention discloses a system and method for converting Internet of Things (IoT) device to 5G network enabled device. The system comprises at least one IoT device configured to send a registration request to at least one IoT server through 5G Gateway.
[0026] Furthermore, the system comprises the IoT server configured to forward the registration request to an aggregator to access a 5G network on behalf of the at least one IoT device, wherein 5G core and the aggregator is connected to the IoT server based on IP addresses of the 5G core and the aggregator.
[0027] Furthermore, the system comprises the aggregator configured to allocate an e-SIM and 5G-UE-Stack to the at least one IoT device, upon receiving the request forwarded by the at least one IoT server.
[0028] Furthermore, the system comprises an IP-gNodeB configured to connect the at least one IoT device and the aggregator through Internet Protocol connectivity carrying the NAS messages through IP and passing the same to NGAP for 5GCore.
[0029] Thereafter, the system comprises a 5G gNodeB configured to provide the 5G network to the IP-gNodeB via configuring a 5G Public core connected to the at least one IoT server, thereby considering each communication of the at least one IoT device as the 5G communication by the 5G core, thereby converting the at least one IoT device to the 5G network enabled device.
[0030] Therefore, the present invention provides the system and method for system for converting Internet of Things (IoT) device to 5G network enabled device that is reliable, efficient, scalable, interoperable, and has enhanced connectivity.

DETAILED DESCRIPTION
[0031] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and/or detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
[0032] The present invention discloses a system and method for converting Internet of Things (IoT) device to 5G network enabled device. The present invention enables both user devices (5G) and IoT (non-5G) devices to connect seamlessly to the 5G network, providing 5G features to all devices. The user devices connect through 5G-gNodeB, while IoT devices connect through IP-gNodeB after being converted to 5G devices by using remote 5G virtual UE stack and eSIM provisioning.
[0033] The main advantage is that non-5G devices can function like 5G devices without the need for dedicated 5G spectrum or physical 5G-enabled SIM slots/ the devices which can’t hold SIM/USIM/eSIM. Further, advantageously, the disclosed system supports multi-vendor compatibility, standardized scalability, and interoperability through 3GPP standards. Additionally, it offers standard 5G authentication, security, and authorization, and allows for easy deployment with existing 5G utilities such as billing and network management systems. The proposed system can be hosted in the cloud or on-premises and enables the establishment of a 5G IoT network without requiring additional infrastructure or spectrum.
[0034] Figure 1 depicts a system 100 comprising at least one IoT device 102, communication unit 118, the at least one IoT server 104, aggregator 106, IP-gNodeB 108, 5G gNodeB, 5G Core 110, 5G Public core 114 and at least one or more user devices 116.
[0035] In an embodiment, the at least one IoT device 102 may comprise any non-Radio device such as Wi-Fi-enabled Smart Home Devices, Bluetooth-based Wearable Devices, Zigbee-based Home Automation Devices, 2G/3G/4G-based Industrial IoT device 102s, LoRaWAN-based IoT device 102s and any other device connected without Radio Resource Control (RRC) Protocol. The IoT device 102 may comprise multiple IoT device 102s such as a first IoT device 102, a second IoT device 102, a third IoT device 102 and so on. The at least one IoT device 102 may be configured to power on and send a registration request to at least one IoT server 104 through a 5G IoT network. The at least one IoT device 102 may also be configured to send a deregistration request to the at least one IoT server 104 in case the one or more of the at least one IoT device 102 opts to enable non-5G network. The at least one IoT device 102 connects to the at least one IoT server 104 through the 5G network, via logging in to an application programming Interface 212 (API) through login details of the at least one IoT device 102.
[0036] In an embodiment, the communication unit 118 may be configured to connect to the at least one IoT device 102 with the IP-gNodeB 108 via Internet Protocol (IP) connectivity comprising at least one of one or more of Bluetooth (registered trademark), ZigBee (registered trademark), a short-range wireless communication such as UWB, a medium-range wireless communication such as WiFi (registered trademark) or a long-range wireless communication such as 3G/4G or WiMAX (registered trademark), LoRa.
[0037] In an embodiment, the aggregator 106 may be configured to allocate an e-SIM and 5G-UE-Stack to the at least one IoT device 102, upon receiving the request forwarded by the at least one IoT server 104.
[0038] In an embodiment, the at least one IoT server 104 may be configured to forward the registration request to an aggregator 106 to access a 5G network or deregistration request to access a non-5G network on behalf of the at least one IoT device 102. The 5G Core 110 and the aggregator 106 are connected to the at least one IoT server 104 based on IP addresses of the 5G Core 110 and the aggregator 106. The aggregator 106 serves as the gateway for the proposed system, responsible for gathering incoming messages from the at least one IoT device 102, the at least one IoT server 104, and other web applications. It performs message authentication and establishes connections with the corresponding modules of the proposed system. On one side, the aggregator 106 connects to the external world through the OneM2M web socket protocol. On the other side, it establishes connections with 5G modules such as the UE-stack and IP-gNodeB 108 using the user data gram protocol (UDP) protocol.
[0039] In an embodiment, the aggregator 106 incorporates a WebSocket interface to establish connections with one or more of the at least one IoT device 102. As at least one or more IoT devices 102 may employ various interfaces, the aggregator 106 also incorporates an HTTP server and a UDP/TCP server to cater to diverse IoT requirements. In case the at least one IoT server 104 sends a WebSocket handshake request to the aggregator 106, the aggregator 106 verifies the handshake parameters. If all the parameters are valid, the aggregator 106 responds with a handshake acknowledgment containing specific details about the aggregator 106. This confirms the success of the handshake process. Similarly, the at least one IoT device 102 also engages in a handshake process, like the IoT server 104, to establish a connection with the aggregator 106.
[0040] In an embodiment, in case registration and deregistration requests are sent by the IoT 102 to the aggregator 106, firstly, the at least one IoT 102 sends the registration request on behalf of the at least one IoT device 102 logging into the aggregator 106. The login details of the IoT device 102 comprises User ID, Password, Device-type, and APN name. In an embodiment, each of the at least one IoT device 102 involved in the system has its own login details/ credentials. Upon sending the request by the at least one IoT server 104, the aggregator 106 authenticates the request using the IoT server 104's database (not shown in figure 1). If authentication is successful, the aggregator 106 forwards the request to the 5G-UE-stack. The aggregator 106 also facilitates communication between the IoT server 104 and the IoT device 102. Upon connection to the aggregator 106, the at least one IoT device 102 can choose between accessing the 5G network or a non-5G network. For 5G communication, it goes through the 5G-UE-stack, while non-5G communication is directly forwarded to the at least one IoT server 104. In an embodiment, in case the at least one IoT server 104 on behalf of the at least one IoT device 102 sends a deregistration request, including login details, to the aggregator 106. The aggregator 106 then forwards the deregistration message to the 5G-UE-stack, updates the at least one IoT server 104, and removes the entry from the database.
[0041] In an embodiment, the IP-gNodeB 108 is configured to connect the at least one IoT device 102 and the aggregator 106 through Internet Protocol (IP) connectivity. The IP-gNodeB 108 adheres to the 3GPP protocol implementation and includes the N2 and N3 interface 236s. The Radio interface is transformed into an IP interface, allowing devices to connect to the gNodeB through IP instead of the NR-PHY and RRC interfaces. This transition is facilitated by the aggregator 106 and 5G-UE-Stack entities, which handle the protocol conversion for the at least one IoT device 102 in the 5G network. In case a login request is received, the at least one IoT device is allocated a UE-Stack and an eSIM. These functionalities are controlled by additional IP-gNodeB communication functions, effectively transforming it into a 5G-IoT-Gateway. The IP-gNodeB 108 manages the contexts of each of the at least one IoT device 102 as a UE and handles their control plane and user plane requirements.
[0042] In an embodiment, the 5G gNodeB configured to provide the 5G network to the IP-gNodeB 108 via configuring a 5G Public core 114 connected to the at least one IoT server 104. The IP-gNodeB 108 comprises N2 and N3 interfaces (234, 236) to establish connection between the IP-gNodeB 108 and the at least one IoT device 102. The N2 interface 234 is configured to transfer control plane data and the N3 interface 236 is configured to transfer user plane data.
[0043] In an embodiment, the 5G Core 110 is connected to the at least one IoT server 104 to provide the 5G network to the IP-gNodeB 108 through the configuration of the 5G gNodeB. The 5G Core 110 conforms to the specifications of 3GPP. Both the 5G Core 110 and IP-gNodeB 108 sides have internal interfaces and a built-in external interface, such as N2 between the RAN and the AMF, N3 between the RAN and the UPF, and N6 between the UPF and a Data Network.
[0044] In an embodiment, the 5G Public core 114 connected to the at least one IoT server 104 to provide the 5G network to the IP-gNodeB 108 through the configuration of the 5G gNodeB. The IP-gNodeB 108 within the system can be configured to establish a connection with a third-party 5G Core 110 network by configuring the 5G-gNodeB and the corresponding external 5G Core 110 Node. Additionally, in case a specific slice is requested, the core has the capability to forward the registration request to another core by utilizing the 5G-gNodeB Re-Route message.
[0045] In an embodiment, the at least one or more user devices 116 may comprise a smart phone, a mobile device/phone, a Personal Digital Assistant (PDA), a computer, a workstation, a notebook, a mainframe computer, a laptop, a tablet, an internet appliance and any other computing device connected to the 5G network.
[0046] In an embodiment, the at least one IoT device 102 accesses 5G network. Firstly, the at least one IoT device 102 sends the registration request to the IoT server 104 via the aggregator 106 for authentication. The at least one IoT device 102 configured to be assigned with user ID, upon the at least one IoT device 102 receives the authentication successful response from the IoT server 104, thereby enabling the IoT device 102 to perform one or more 5G communication functions. The at least one IoT device 102 subscribes for the feature to get access to perform the one or more 5G communication functions. The IoT server 104 comprises a database to store membership and subscription data, wherein the at least one IoT device 102 needs to send membership request to use the 5G network for the first time, wherein the user ID and onetime password is provided by the system. The one or more 5G communication functions comprises at least one of SMS, Payload, Send_file_cp and Send_file_up.
[0047] Figure 2 depicts a block diagram comprising sub-components if the system. In an embodiment, the
[0048] In an embodiment, the at least one IoT device 102 comprises a processing unit 202, memory unit 204, communication unit 118, e-SIM module 208, NAS interface application 210 and Application programming Interface 212.
[0049] In an embodiment, the processing unit 202 may comprise one or more microprocessors, circuits, and other hardware configured for processing. The processing unit 202 is configured to execute instructions stored in the memory unit 204 as well as communicate via the communication unit 118.
[0050] In an embodiment, the memory unit 204 comprises one or more volatile and non-volatile memory components which are capable of storing data and instructions to be executed.
[0051] In an embodiment, the communication unit 118 may include wired and wireless communication, including but not limited to, GPS, GSM, LAN, Wi-fi compatibility, Bluetooth low energy as well as NFC. The wireless communication may further comprise one or more of Bluetooth, ZigBee, a short-range wireless communication such as UWB, a medium-range wireless communication such as WiFi or a long-range wireless communication such as 3G/4G or WiMAX, according to the usage environment.
[0052] In an embodiment, e-SIM module 208 allows the at least one IoT device 102 to have a virtual SIM card instead of a physical SIM card. This enables flexibility and convenience as the at least one IoT device 102 can be remotely provisioned with different network profiles and operator credentials. It eliminates the need for physical SIM card swapping, making it easier to manage connectivity and switch between different networks.
[0053] In an embodiment, NAS interface application 210 facilitates communication between the at least one IoT device 102 and the core network's Non-Access Stratum (NAS). NAS handles various functionalities such as authentication, security, mobility management, and session management for the at least one IoT device 102. By including the NAS interface module, the at least one IoT device 102 can securely connect to the 5G network, authenticate itself, and perform necessary network procedures to establish and maintain communication.
[0054] In an embodiment, Application programming Interface 212 (API) configured to connect to the 5G platform, accessing the e-SIM module 208, and utilizing the NAS interface application 210 for seamless integration and communication within the system.
[0055] In an embodiment, the aggregator 106 comprises M2M server module 214, Memory module 216, Communication module 218, Processing module 220.
[0056] In an embodiment, the M2M server module 214 in the aggregator 106 acts as a central component that facilitates machine-to-machine communication. It provides a distributed operating system for the at least one IoT device 102, allowing it to interact and exchange data efficiently. The M2M server module 214 implements the necessary protocols and functionalities to handle incoming messages from the at least one IoT device 102 and the at least one IoT server 104.
[0057] In an embodiment, the memory module 216 in the aggregator 106 is configured to store and manage data related to the system's operation. It stores information such as device registrations, authentication details, message queues, and other relevant data required for efficient processing and management of IoT communications.
[0058] In an embodiment, the communication module 218 in the aggregator 106 enables connectivity with the at least one IoT device 102 and the at least one IoT server 104. It implements different communication protocols such as WebSocket, HTTP, and UDP to establish connections and handle incoming and outgoing messages effectively. The communication module 218 ensures seamless interaction and data exchange between the aggregator 106 and the external entities in the system.
[0059] In an embodiment, the processing module 220 in the aggregator 106 is responsible for executing the necessary logic and operations required for the system's functioning. It processes incoming messages, performs authentication and verification of requests, manages data flows, and routes messages to their respective destinations within the system. The processing module 220 ensures smooth operation and coordination of communication between the at least one IoT device 102 and the at least one IoT server 104, and other components of the system.
[0060] In an embodiment, the aggregator 106's configuration with the M2M server module 214, memory module 216, communication module 218, and processing module 220 enables it to act as a central hub for managing and facilitating communication between the at least one IoT device 102 and the at least one IoT server 104 in the system.
[0061] In an embodiment, the at least one IoT server 104 comprises processing segment 222, memory segment 224, communication segment 226, SIM managing module 228, NAS stack managing module 230 and IoT device managing module 232.
[0062] In an embodiment, the processing segment 222 in the at least one IoT server 104 handles the computational tasks required for processing incoming requests, managing data, and executing application logic. It ensures efficient handling of requests from the at least one IoT device 102 and performs necessary operations based on the received data.
[0063] In an embodiment, the memory segment 224 in the at least one IoT server 104 stores and manages data related to the system's operation, including device information, authentication credentials, and other relevant data. It provides fast access to stored information and supports efficient data retrieval and storage.
[0064] In an embodiment, the communication segment 226 in the IoT server 104 handles the communication protocols and interfaces used for exchanging data with IoT device 102s. It includes modules for handling communication protocols such as MQTT, CoAP, HTTP, or WebSocket, allowing seamless communication between the IoT device 102s and the server.
[0065] In an embodiment, the SIM managing module 228 is responsible for managing the eSIMs (Embedded Subscriber Identity Modules) associated with the at least one IoT device 102. It handles tasks such as provisioning, activation, deactivation, and updating of eSIMs. This module ensures proper management and authentication of the at least one IoT device 102 within the system.
[0066] In an embodiment, the NAS (Non-Access Stratum) stack managing module 230 handles the communication between the at least one IoT server 104 and the at least one IoT device 102 at the NAS layer of the protocol stack. It manages the establishment and maintenance of NAS sessions, authentication, security procedures, and mobility management for the at least one IoT device 102.
[0067] In an embodiment, the IoT device managing module 232 is responsible for managing the connected at least one IoT device 102 within the system. It handles tasks such as device registration, authentication, device configuration, and status monitoring. This module ensures proper management and control of the at least one IoT device 102 in the system.
[0068] In an embodiment, the IP-gNodeB 108 comprises N2 interface unit 234 and N3 interface unit 236.
[0069] In an embodiment, the N2 interface unit 234 is responsible for communication between the IP-gNodeB 108 and the Access and Mobility Management Function (AMF) in the 5G Core 110 network. It handles the exchange of control plane information related to mobility management, session management, and other network-related functions.
[0070] In an embodiment, the N3 interface unit 236 facilitates communication between the IP-gNodeB 108 and the User Plane Function (UPF) in the 5G Core network 110. It is responsible for the transport of user plane data, including data packets transmitted between the gNodeB and the UPF. By configuring the N2 and N3 interface units (234, 236), the IP-gNodeB 108 is able to establish and maintain communication links with the AMF and UPF, respectively. These interface units ensure the proper exchange of control plane and user plane data, enabling the IP-gNodeB 108 to fulfill its role as a key component in the 5G network architecture.
[0071] Figure 3 depicts a method for converting Internet of Things (IoT) device to 5G network enabled device, in accordance with an embodiment of the present disclosure. The method 300 begins with powering on the at least one IoT device 102 and sending a registration request to at least one IoT server 104 by at least one IoT device 102, as depicted at step 302. Subsequently, the method 300 discloses forwarding, by the at least one IoT server 104, the registration request to an aggregator 106 to access a 5G network on behalf of the at least one IoT device, wherein 5G core 110 and the aggregator 106 is connected to the IoT server 104 based on IP addresses of the 5G core 110 and the aggregator 106, as depicted at step 304. Subsequently, the method 300 discloses allocating an e-SIM and 5G-UE-Stack to the at least one IoT device, upon receiving the request forwarded by the at least one IoT server 104 by the aggregator 106, as depicted at step 306. Subsequently, the method 300 discloses connecting, by an IP-gNodeB 108, the at least one IoT device 102 and the aggregator 106 through IP connectivity protocol, as depicted at step 308. Thereafter, the method 300 discloses providing, by a 5G gNodeB 108, the 5G network to the IP-gNodeB 108 via configuring a 5G Public core 114 connected to the at least one IoT server 104, thereby considering each communication of the at least one IoT device 102 as the 5G communication by the 5G core 110, thereby converting the at least one IoT device 102 to the 5G network enabled device and enabling back and forth data transmission through at least one of the 5G core (110), the 5G Public core (114), and the IP-gNodeB (108).
[0072] Furthermore, the at least one IoT device 102 forwards a deregistration request to the at least one IoT server 104. Thereafter, the at least one IoT device 102 is powered off, as depicted at step 310.
[0073] Figure 4 illustrates a method for sending registration and deregistration requests by the IoT server to the aggregator, in accordance with an embodiment of the present disclosure. The method begins with powering on the at least one IoT device 102 and sending, by the at least one IoT server 104 and the at least one IoT device 102, the registration request via the at least one IoT device 102 login details to the aggregator 106, as depicted at step 402. Subsequently, the method 400 discloses authenticating, by the aggregator 106, the status of the request in a database of the at least one IoT server 104, wherein in case authentication is successful for the request received from the at least one IoT server 104 and the at least one IoT device 102, the aggregator 106 forwards the request to 5G-UE-stack, as depicted at step 404. Subsequently, the method 400 discloses connecting, by the aggregator 106, the at least one IoT server 104 to communicate with the at least one IoT device 102, upon forwarding the request to 5G-UE-stack by the aggregator 106, as depicted at step 406. Subsequently, the method 400 discloses selecting, by the at least one IoT device 102, at least one of access 5G network or non-5G network, upon the aggregator 106 connected to the at least one IoT server 104, thereby forwarding 5G communication through the UE-stack and non-5G communication directly to the at least one IoT server 104, as depicted at step 408. Thereafter, the method 400 discloses sending, by the at least one IoT server 104 and the at least one IoT device 102 the deregistration request via the at least one IoT device 102 login details to the aggregator 106, wherein the aggregator 106 forwards the deregistration message to 5G-UE-stack, update IoT server 104 and delete from the database, as depicted at step 410.
[0074] The advantages of the current invention include providing a system and method that is reliable, efficient, scalable, interoperable, and has enhanced connectivity.
[0075] An additional advantage is that the present invention allows for universal identification of IoT devices via usage of e-SIMs, ensuring proper tracking and accountability.
[0076] An additional advantage is that the present invention easily incorporates the latest 3GPP upgrades, features and functionalities.
[0077] An additional advantage is that the present invention provides the 5G system that leverage existing utilities such as OSS (Operations Support Systems), BSS (Business Support Systems), billing systems, NMS (Network Management Systems), and IMS (IP Multimedia Subsystem), reducing implementation costs and complexity.
[0078] An additional advantage is that the present invention enables non-5G devices to function as 5G devices without the need for hardware changes by remote UE stack implementation.
[0079] An additional advantage is that the present invention provides reduced downtime and alternative server connectivity.
[0080] An additional advantage is that the present invention provides simplified device identification and service provisioning via cloud-based or remote SIM provisioning.
[0081] An additional advantage is that the present invention provides cross connectivity to any IoT network, allowing for continuity of operations even if one server is down.
[0082] An additional advantage is that the present invention provides the system and method that leverage 5G advantages such as IoT slicing, SLA QoS (Quality of Service), and increased speed, improving the overall quality and performance of IoT services.
[0083] An advantage is that the present invention provides the 5G system that supports interoperability, allowing for the addition or removal of different vendor components, promoting flexibility and choice.
[0084] An additional advantage is that the present invention provides improved visibility and discoverability within the 5G network by registering IoT servers to the NEF/NRF (Network Exposure Function/Network Repository Function).
[0085] An additional advantage is that the present invention provides multi-vendor connectivity capability to ensure independence from specific suppliers, promote flexibility and vendor diversity.
[0086] Applications of the current invention include smart cities, Industrial IoT, Healthcare, Transportation, smart homes, agriculture, public safety, and emergency response.
[0087] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the scope of the embodiments as described here. , Claims:We claim:

1. A system for converting Internet of Things (IoT) device to 5G network enabled device, comprising:
at least one IoT device (102) configured to send a registration request to at least one IoT server (104);
the at least one IoT server (104) configured to forward the registration request to an aggregator (106) to access a 5G network on behalf of the at least one IoT device (102), wherein a 5G core (110) and the aggregator (106) are connected to the IoT server (104) based on IP addresses of the 5G core (110) and the aggregator (106);
the aggregator (106) configured to allocate an e-SIM and 5G-UE-Stack to the at least one IoT device (102), upon receiving the request forwarded by the at least one IoT server (104);
an IP-gNodeB (108) configured to connect the at least one IoT device (102) and the aggregator (106) through Internet Protocol (IP) connectivity; and
a 5G gNodeB (108) configured to provide the 5G network to the IP-gNodeB (108) via configuring a 5G Public core (114) connected to the at least one IoT server (104), by considering each communication of the at least one IoT device (102) as the 5G communication by the 5G core (110), thereby converting the at least one IoT device (102) to the 5G network enabled device and enabling back and forth data transmission through at least one of the 5G core (110), the 5G Public core (114), and the IP-gNodeB (108).

2. The system as claimed in claim 1, wherein the at least one IoT device (102) is connected to IP-gNodeB (108) via IP connectivity comprising at least one of one or more of Bluetooth (registered trademark), ZigBee (registered trademark), a short-range wireless communication such as UWB, a medium-range wireless communication such as WiFi (registered trademark) or a long-range wireless communication such as 3G/4G or WiMAX (registered trademark), and LoRa.

3. The system as claimed in claim 1, wherein the at least one IoT device (102) connects to the at least one IoT server (104) through the 5G network, via logging in to an Application Programming Interface (API) through login details of the at least one IoT device (102).

4. The system as claimed in claim 1, wherein the 5G core (110) is connected to the at least one IoT server (104) to provide the 5G network to the IP-gNodeB (108) through the configuration of the 5G gNodeB (108).

5. The system as claimed in claim 1, wherein the at least one IoT device (102) comprises a non-Radio device and/or device connected without RRC protocol.

6. The system as claimed in claim 1, wherein the at least one IoT device (102) is configured to send a deregistration request to the at least one IoT server (104).

7. The system as claimed in claim 6, wherein registration and deregistration requests are sent by the IoT server (104) to the aggregator (106), comprising:
the at least one IoT server (104) and the at least one IoT device (102) configured to send the registration request via the at least one IoT device (102) login details to the aggregator (106);
the aggregator (106) configured to authenticate the status of the request in a database of the at least one IoT server (104), wherein in case authentication is successful for the request received from the at least one IoT server (104) and the at least one IoT device (102), the aggregator (106) forwards the request to the 5G-UE-stack;
the aggregator (106) configured to connect the at least one IoT server (104) to communicate with the at least one IoT device (102), upon forwarding the request to the 5G-UE-stack by the aggregator (106);
the at least one IoT device (102) configured to select at least one of access 5G network or non-5G network, upon the aggregator (106) connected to the at least one IoT server (104), thereby forwarding 5G communication through the 5G-UE-stack and non-5G communication directly to the at least one IoT server (104); and
the at least one IoT server (104) and the at least one IoT device (102) configured to send the deregistration request via the at least one IoT device (102) login details to the aggregator (106), wherein the aggregator (106) forwards the deregistration message to 5G-UE-stack, update IoT server (104) and delete from the database.

8. The system as claimed in claim 1, wherein the at least one IoT device (102) configured to access 5G network comprises:
the at least one IoT device (102) configured to send the registration request to the IoT server (104) via the aggregator (106) for authentication;
the at least one IoT device (102) configured to be assigned with user ID, upon the at least one IoT device (102) receives the authentication successful response from the IoT server (104), thereby enabling the IoT device (102) to perform one or more 5G communication functions; and
the at least one IoT device (102) configured to subscribe for the feature to get access to perform the one or more 5G communication functions, wherein the IoT server (104) comprises a database to store membership and subscription data, wherein the at least one IoT device (102) needs to send membership request to use the 5G network for the first time, wherein the user ID and onetime password is provided by the system.

9. The system as claimed in claim 8, wherein the one or more 5G communication functions comprises at least one of SMS, Payload, Send_file_cp and Send_file_up.

10. The system as claimed in claim 1, wherein the aggregator (106) connects to the at least one IoT server (104) and the at least one IoT device (102) via the User Datagram Protocol (UDP) Protocol to access 5G network and the WebSocket Protocol to access non-5G network.

11. The system as claimed in claim 1, wherein the IP-gNodeB (108) comprises N2 and N3 interfaces (234, 236) to establish connection between the IP-gNodeB (108) and the at least one IoT device (102), wherein the N2 interface (234) is configured to transfer control plane data, wherein the N3 interface (236) is configured to transfer user plane data.

12. A method for converting Internet of Things (IoT) device to 5G network enabled device, comprising:
sending, by at least one IoT device (102), a registration request to at least one IoT server (104);
forwarding, by the at least one IoT server (104), the registration request to an aggregator (106) to access a 5G network on behalf of the at least one IoT device, wherein 5G core (110) and the aggregator (106) is connected to the IoT server (104) based on IP addresses of the 5G core (110) and the aggregator (106);
allocating, by the aggregator (106), an e-SIM and 5G-UE-Stack to the at least one IoT device, upon receiving the request forwarded by the at least one IoT server (104);
connecting, by an IP-gNodeB (108), the at least one IoT device (102) and the aggregator (106) through IP connectivity protocol; and
providing, by a 5G gNodeB (108), the 5G network to the IP-gNodeB (108) via configuring a 5G Public core (114) connected to the at least one IoT server (104), thereby considering each communication of the at least one IoT device (102) as the 5G communication by the 5G core (110), thereby converting the at least one IoT device (102) to the 5G network enabled device and enabling back and forth data transmission through at least one of the 5G core (110), the 5G Public core (114) and the IP-gNodeB (108).

13. The method as claimed in claim 12, comprising connecting the at least one IoT device (102) to IP-gNodeB (108) via IP connectivity, comprising at least one of one or more of Bluetooth (registered trademark), ZigBee (registered trademark), a short-range wireless communication such as UWB, a medium-range wireless communication such as WiFi (registered trademark) or a long-range wireless communication such as 3G/4G or WiMAX (registered trademark), LoRa.

14. The method as claimed in claim 12, comprising connecting the at least one IoT device (102) to the at least one IoT server (104) through the 5G network, via logging in to an Application Programming Interface (API) using login details of the at least one IoT device (102).

15. The method as claimed in claim 12, comprising connecting the 5G core (110) to the at least one IoT server (104) to provide the 5G network to the IP-gNodeB (108) by configuring the 5G gNodeB (108).

16. The method as claimed in claim 12, wherein the at least one IoT device (102) comprises a non-Radio device.

17. The method as claimed in claim 12, comprising configuring the at least one IoT device (102) to send a deregistration request to the at least one IoT server (104).

18. The method as claimed in claim 12, comprising sending registration and deregistration request by the IoT server (104) to the aggregator (106) comprises:
sending, by the at least one IoT server (104) and the at least one IoT device (102), the registration request via the at least one IoT device (102) login details to the aggregator (106);
authenticating, by the aggregator (106), status of the request in a database of the at least one IoT server (104), wherein in case authentication is successful for the request received from the at least one IoT server (104) and the at least one IoT device (102), the aggregator (106) forwards the request to 5G-UE-stack;
connecting, by the aggregator (106), the at least one IoT server (104) to communicate with the at least one IoT device (102), upon forwarding the request to 5G-UE-stack by the aggregator (106);
selecting, by the at least one IoT device (102), at least one of access 5G network or non-5G network, upon the aggregator (106) connected to the at least one IoT server (104), thereby forwarding 5G communication through the UE-stack and non-5G communication directly to the at least one IoT server (104); and
sending, by the at least one IoT server (104) and the at least one IoT device (102) the deregistration request via the at least one IoT device (102) login details to the aggregator (106), wherein the aggregator (106) forwards the deregistration message to 5G-UE-stack, update IoT server (104) and delete from the database.

19. The method as claimed in claim 12, comprising configuring the at least one IoT device (102) to access 5G network comprises:
sending, by the at least one IoT device (102), the registration request to the IoT server (104) via the aggregator (106) for authentication;
configuring the at least one IoT device (102) to be assigned with user ID, upon the at least one IoT device (102) receives the authentication successful response from the IoT server (104), thereby enabling the IoT device (102) to perform one or more 5G communication functions; and
configuring the at least one IoT device (102) to subscribe for the feature to get access to perform the one or more 5G communication functions, wherein the IoT server (104) comprises a database to store membership and subscription data, wherein the at least one IoT device (102) needs to send membership request to use the 5G network for the first time, wherein the user ID and onetime password is provided by the system.

20. The method as claimed in claim 19, comprising the one or more 5G communication functions comprise at least one of SMS, Payload, Send_file_cp and Send_file_up.

21. The method as claimed in claim 12, comprising connecting the aggregator (106) to the at least one IoT server (104) and the at least one IoT device (102) via the User Datagram Protocol (UDP) Protocol to access 5G network and the WebSocket Protocol to access non-5G network.

22. The method as claimed in claim 12, comprising configuring the IP-gNodeB (108) comprises N2 and N3 interfaces (234, 236) to establish connection between the IP-gNodeB (108) and the at least one IoT device (102), wherein theN2 interface (234) is configured to transfer control plane data, wherein the N3 interface (236) is configured to transfer user plane data.