DESC:FIELD OF INVENTION
[0001] The embodiments of the present disclosure generally relate to telecommunication networks. More particularly, the present disclosure relates to systems and methods for switching and interworking between two cellular IoT networks.

BACKGROUND OF THE INVENTION
[0002] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[0003] NB-IoT (narrowband IoT) and Category M 1 (Cat-M1), are both 3GPP standardized technologies that are well known in the art. Both these network types are complementary to each other and address different types of use cases based on the strength/capabilities of the two technologies. For instance, NB-IoT may support ultra-low complexity devices with very narrow bandwidth, 200 kHz. Due to its narrow bandwidth, the data rate peaks at around 250 kbs per second. An NB-IoT carrier can be deployed even in guard-band of an LTE carrier to use the spectrum that is otherwise unused. With an impressive coverage capability, NB-IoT is ideal for supporting very low data rate applications in challenging radio conditions. On the other hand, the Cat-M1 technology operates at 1.4 MHz bandwidth with higher device complexity/cost than NB-IoT. The wider bandwidth allows Cat-M1 to achieve greater data rates (up to 1 Mbps), lower latency and more accurate device positioning capabilities. Cat-M1 supports voice calls and connected mode mobility.
[0004] Most common use cases of NB-IoT may include utility meters and sensors. Typical uses cases for Cat-M1 may include connected vehicles, wearable devices, trackers and alarm panels. Although Cat-M1 is more powerful than NB-IoT, it may not necessarily be a better technology. The two technologies are suitable for different applications and use cases. In order to provide the best of service experience to the end customer, a telecom network is in a constant state of expansion, upgrade, and optimization. All such activities may involve change in configuration of existing nodes, inclusion of new nodes to address increased demand and rolling out new features in the form of software, firmware upgrades and parameter value changes. Most of the times, such configuration changes may involve disruption of existing services for a limited period. This service disruption is experienced by all the users that are using the network (Active users) at that time. Solution owners may have to take a tough decision on choosing between Wide Band IoT networks (Cat-M1 or WBIoT) and Narrow Band IoT (NBIoT) that would best suit the use case based on data rate and latency, frequency of data exchange, need of coverage enhancement, accuracy in positioning, mobility, cost and the like.
[0005] The stake holders may also be forced to take tough calls like changing of vendors/changing of devices or have a complete overhaul of the end-to-end system to meet the expectations and SLAs. For example, there may be use cases that involve stationary devices and may be expected to report sensor data to an application server in a predefined schedule. Solution owners may prefer NBIoT network for such use cases as it meets the bandwidth requirement along with device cost and complexity requirement. However, there may be instances where there is a sudden surge in the bandwidth requirement of these devices where the size of the application data exceeds a certain limit and hence the use case may fail. For example, metered data which is usually of not more than 5-10 Kb increases to 200-500 Kb if historical/saved data is considered. There may be high chances of failures if the application data on an NBIoT network exceeds 200-300 Kb.
[0006] There may also be instances where concurrent sessions by a number of IoT devices deployed in close proximity exceeds a certain supported limit. The NBIoT Radio Access Network may fail to support the concurrent sessions beyond a calculated limit which is proportional to the bandwidth of the network. i.e., the number of concurrent sessions in a cell is high if the transmission bandwidth of the cell is high. A WBIoT based personal tracker may find it difficult to report positioning data to the application server in constrained network conditions. The stake holders do not have the flexibility or option to select/switch between the two technologies on-the-go which would avoid failures and further avoid SLA penalties and inconveniences.
[0007] Therefore, there is a need in the art to provide systems and methods that can overcome the abovementioned shortcomings in the art.

OBJECTS OF THE PRESENT DISCLOSURE
[0008] Some of the objects of the present disclosure, which at least one embodiment herein satisfies are as listed herein below.
[0009] An object of the present disclosure is to provide a provision in a Long Term Evolution (LTE) Standard based IoT backend network to allow an IoT device to select either of the two cellular IoT networks as and when required.
[0010] An object of the present disclosure is to provide a mechanism to the end points (IoT Devices) to seamlessly switch between WBIoT and NBIoT networks based on a predefined criteria.
[0011] Another object of the present disclosure is to reduce business impact and poor SLAs pertaining to performance issues caused by limitations of Low-power Wide Area network (LPWAN) by introducing interworking between different LTE based cellular IoT networks.

SUMMARY
[0012] Embodiments of a user equipment (UE) are disclosed. In an embodiment, the UE includes a processor coupled to a memory comprising a set of instructions that when executed by the processor causes the processor to compute values of a predefined set of parameters associated with data transmission via a first Internet of Things (IoT) network, determine whether the value of each of a predefined first set of parameters out of the predefined set of parameters is below a predefined threshold, and upon a positive determination, transmit a network change command, to a modem comprised in the UE, through one or more Application Program Interfaces (APIs), wherein the network change command corresponds to a switch from the first IoT network to a second IoT network.
[0013] In an embodiment, the first IoT network corresponds to Narrow Band Internet of Things (NBIoT) network and the second IoT network corresponds to Wide Band Internet of Things (WBIoT) network. In an embodiment, the memory further comprises set of instructions that when executed by the processor causes the processor to execute an embedded application stored in the memory when the UE is powered on. In an embodiment, the embedded application upon execution causes the UE to connect to a default communication network, wherein the default communication network corresponds to the first IoT network. In an embodiment, the predefined set of parameters comprises application payload delivery status, NAS payload send status, radio condition, and lower layer failures. In an embodiment, the value of each of the predefined set of parameters correspond to either “0” or “1”. In an embodiment, the positive determination is made when the value of each of the predefined first set of parameters is “0”.
[0014] In an embodiment, the predefined first of parameters comprises any three of application payload delivery status, NAS payload send status, radio condition, and lower layer failures. In an embodiment, the memory further comprises set of instructions that when executed by the processor causes an embedded application to wait for application layer and TCP layer to exhaust the ongoing transmission attempt via the first IoT network. In an embodiment, the memory further comprises set of instructions that when executed by the processor causes the embedded application to store a copy of application data set, associated with a previously failed transmission attempt via the first IoT network, in a buffer memory comprised in the UE. In an embodiment, the memory further comprises set of instructions that when executed by the processor causes the modem to, responsive to receiving the network change command, disassociate from the first IoT network and initiate an attempt to associate with the second IoT network.
[0015] Embodiments of a computer-implemented method for switching between a first IoT network and a second IoT network are disclosed. In an embodiment, the method includes computing, by a processor comprised in an Internet of Things (IoT) device, values of a predefined set of parameters associated with data transmission via the first IoT network. The method further includes determining, by the processor, whether the value of each of a predefined first set of parameters out of the predefined set of parameters is below a predefined threshold. The method further includes, upon a positive determination, transmitting, by the processor, a network change trigger, to a modem comprised in the IoT device, through one or more Application Program Interfaces (APIs), wherein the network change trigger corresponds to the switching from the first IoT network to a second IoT network.
[0016] In an embodiment, the first IoT network corresponds to Narrow Band Internet of Things (NBIoT) network and the second IoT network corresponds to Wide Band Internet of Things (WBIoT) network. In an embodiment, the method further includes executing, by the processor, an embedded application stored in the memory when the IoT device is powered on. In an embodiment, the method further includes: upon execution of the embedded application, connecting, by the processor, to a default communication network, wherein the default communication network corresponds to the first IoT network. In an embodiment, the predefined set of parameters comprises application payload delivery status, NAS payload send status, radio condition, and lower layer failures. In an embodiment, the value of each of the predefined set of parameters correspond to either “0” or “1”. In an embodiment, the positive determination is made when the value of each of the predefined first set of parameters is “0”.
[0017] In an embodiment, the predefined first of parameters comprises any three of application payload delivery status, NAS payload send status, radio condition, and lower layer failures. In an embodiment, the method further includes: waiting, by the processor, for application layer and TCP layer to exhaust the ongoing transmission attempt. In an embodiment, the method further includes: storing, by the processor, a copy of application data set, associated with a previously failed transmission attempt, in a buffer memory comprised in the IoT device. In an embodiment, the method further includes, responsive to receiving the network change command, disassociating, by the processor, from the first IoT network and initiating, by the processor, an attempt to associate with the second IoT network.
[0018] Embodiments of a non-transitory computer readable medium (CRM) are disclosed. In an embodiment, the CRM stores a set of instructions that when executed by a processor comprised in an Internet of Things (IoT) device causes the processor to compute values of a predefined set of parameters associated with data transmission via a first Internet of Things (IoT) network, determine whether the value of each of a predefined first set of parameters out of the predefined set of parameters is below a predefined threshold; and upon a positive determination, transmit a network change command, to a modem comprised in the IoT device, through one or more Application Program Interfaces (APIs), wherein the network change command corresponds to a switch from the first IoT network to a second IoT network.
[0019] In an embodiment, the first IoT network corresponds to Narrow Band Internet of Things (NBIoT) network and the second IoT network corresponds to Wide Band Internet of Things (WBIoT) network. In an embodiment, the predefined set of parameters comprises application payload delivery status, NAS payload send status, radio condition, and lower layer failures. In an embodiment, the value of each of the predefined set of parameters correspond to either “0” or “1”. In an embodiment, the positive determination is made when the value of each of the predefined first set of parameters is “0”. In an embodiment, the predefined first of parameters comprises any three of application payload delivery status, NAS payload send status, radio condition, and lower layer failures.

BRIEF DESCRIPTION OF DRAWINGS
[0020] The accompanying drawings, which are incorporated herein, and constitute a part of this invention, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present invention. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that invention of such drawings includes the invention of electrical components, electronic components or circuitry commonly used to implement such components.
[0021] FIG. 1A illustrates an exemplary network architecture 100 in which or with which proposed system for switching between two cellular IoT networks of the present disclosure can be implemented, in accordance with an embodiment of the present disclosure.
[0022] FIG. 1B illustrates an exemplary detailed network architecture 150 in which or with which the proposed system for switching between two cellular IoT networks of the present disclosure can be implemented, in accordance with an embodiment of the present disclosure.
[0023] FIG. 2 illustrates an exemplary representation 200 of the proposed system for switching between two cellular IoT networks, in accordance with an embodiment of the present disclosure.
[0024] FIG. 3 illustrates an exemplary representation of the signal flow diagram for associating with a cellular IoT network, in accordance with an embodiment of the present disclosure.
[0025] FIG. 4 illustrates an exemplary representation of the proposed method for switching between two cellular IoT networks, in accordance with an embodiment of the present disclosure.
[0026] FIG. 5 illustrates an exemplary computer system in which or with which embodiments of the present invention can be utilized, in accordance with embodiments of the present disclosure.
[0027] The foregoing shall be more apparent from the following more detailed description of the invention.

DETAILED DESCRIPTION OF INVENTION
[0028] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address all of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein.
[0029] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the invention as set forth.
[0030] As described above, existing technologies do not provide for an efficient and seamless switching mechanism between two cellular IoT networks. There is a service disruption or downtime associated with the known methods of switching between two cellular IoT networks. Such switching may be very useful in multiple scenarios to optimize the network resources and also to maintain quality of service under various network conditions.
[0031] To this end, the present invention provides an efficient and reliable system and method to facilitate switching and interworking of two cellular IoT networks. In an embodiment, the user equipment or the IoT device includes a multi-radio access technology (RAT) support which enables the UE/IoT device to switch between a first and a second cellular IoT network (such as an NBIoT network and an WBIoT network) whenever required based on a predefined set of criteria or a rules. In an embodiment, the proposed approach involves monitoring the status or values of the parameters associated with the two or more cellular IoT networks and correlate it with the quality of the network service and the network interface statuses.
[0032] Embodiments of a computer-implemented method for switching between a first IoT network and a second IoT network are disclosed. In an embodiment, the method includes computing, by a processor comprised in an Internet of Things (IoT) device, values of a predefined set of parameters associated with data transmission via the first IoT network. The method further includes determining, by the processor, whether the value of each of a predefined first set of parameters out of the predefined set of parameters is below a predefined threshold. The method further includes, upon a positive determination, transmitting, by the processor, a network change trigger, to a modem comprised in the IoT device, through one or more Application Program Interfaces (APIs), wherein the network change trigger corresponds to the switching from the first IoT network to a second IoT network.
[0033] FIG. 1A illustrates an exemplary network architecture (100) in which or with which proposed system for switching between two cellular IoT networks, of the present disclosure can be implemented, in accordance with an embodiment of the present disclosure. As illustrated, the network architecture includes a system (110) that may be communicatively coupled to a plurality of first computing devices (104-1, 104-2, 104-3…104-N) (interchangeably referred to as user equipment (104-1, 104-2, 104-3…104-N) or devices (104-1, 104-2, 104-3…104-N) or IoT devices 104-1, 104-2, 104-3…104-N) and individually referred to as the user equipment (UE) (104), the device (104) or the IoT device (104) and collectively referred to as the UE (104), the devices (104) or the IoT devices (104)) associated with a plurality of users (101-1,101-2,…101-N). The communication network (108) may further include a radio access network Radio Unit (RU) (114), one or more third computing devices (116) (interchangeably referred to as radio nodes or eNodeBs or gNB)). The network architecture (100) may further include a centralized server (112) that may implement an application server in an embodiment. The radio nodes (116) may include support for two or more cellular IoT networks such as, but not limited to NBIoT network and WBIoT network.
[0034] As illustrated in FIG. 1B, the UE (104) may be equipped with a modem (152), an embedded application (154) and a multi-international mobile subscriber identity (IMSI) universal subscriber identity module (USIM) (156). The UE (104) may be communicatively coupled to the radio nodes (116) that may include the functionalities of NBIoT eNodeB and WBIoT eNodeB in accordance with an embodiment. The radio nodes may be further operatively coupled to an Evolved Packet Core (EPC) having a Home Subscriber Server (HSS) (158), a Mobility Management Entity (MME) (160), a serving gateway (S-GW) (162), and a packet data network (PDN) gateway (P-GW) (164).
[0035] The UE (104) may further be equipped with one or more processor (202) (ref. FIG. 2) that may cause the UE (104) to receive a first set of data packets from the one or more third computing devices or the eNodeBs (116). The first set of data packets may pertain to a set of network parameters. For example, the set of network parameters may include Application payload delivery status, Non-Access Stratum (NAS) transmit/receive status, Radio condition, Lower layer conditions. The UE (104) may extract a set of attributes from the first set of data packets received. The set of attributes may pertain to "application data sent, whether NAS payload delivered, if receive Radio link control (RLC) acknowledgement (ACK) from the EnodeB, whether radio condition is Good (RSRP>-100 dBm, SNR>0) or Bad(RSRP<-100 dBm, SNR<0), whether radio link failures” are detected and the like. The system (110) may then perform analysis on the set of attributes extracted and correlate the analysed set of attributes to a predefined set of parameters that may enable the system (110) to cause switching of the current network to a second network. Thus, based on the analysis, the system (110) may cause the embedded application to smartly decide and ask the modem to switch to the second network. For example, the system (110) may switch form an NBIoT network to a WBIoT network.
[0036] In an embodiment, the multi-IMSI USIM card may have at least two profiles, each burnt with the same carrier but different IMSIs. For example, both the IMSIs may have access to the same carrier but one will be provisioned with WBIoT services and the other IMSI will be provisioned with NBIoT services in the network.
[0037] The cells of NB-IoT radio access technology (RAT) and WB- Evolved UMTS Terrestrial Radio Access Network (EUTRAN) may be configured with different Tracking Area codes. In an embodiment, when the UE (102) tries to attach with the NBIoT cell and NBIoT provisioned SIM, the EnodeB (116) will send the Attach message in the Initial UE message to the MME over a S1AP interface. In an embodiment, the message also includes the PDN Connectivity Request message. The Tracking Area Identify (TAI) and the NB-IoT Cell Global Identifier (ECGI) are also included in the message. The MME would identify from the Tracking Area or group of Tracking Area whether the TA belongs to NBIoT or WBIoT. During call setup or updating procedures, the MME passes the RAT Type as NBIoT to other nodes such as SGW/PGW or peer MME. The MME also passes the RAT type information to HSS over the S6a interface. MME initiates the default route establishment by asking the SGW to create a GTP tunnel. The APN specified by the UE is used for default bearer activation. The IP Address assigned to the UE is also included along with the downlink and uplink maximum data rates allowed at the APN level.
[0038] In an embodiment, once the UE attaches to the NBIoT network, the UE may execute the usual use case and the embedded application will record and keep monitoring the set of network parameters through APIs which give real time data about the modem from the lower layers to the application layer.
[0039] In an embodiment, the UE may start scanning WBIoT network and attach to the network using the same attach process. The Tracking Area will be different and will belong to the WBIoT network definition. The UE will attach to the WBIoT network and try to send the same data from its internal buffer/ROM memory which had failed on NBIoT.
[0040] In an embodiment, the UE can also voluntarily switch its Network/ Radio to WBIoT for certain use cases like firmware upgrade of the devices which has heavy application data to download.
[0041] In an exemplary embodiment, the network (108) may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. A network may include, by way of example but not limitation, one or more of: a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, some combination thereof.
[0042] In another exemplary embodiment, the centralized server (112) may be included in architecture (100). The centralized server (112) may include or comprise, by way of example but not limitation, one or more of: a stand-alone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof.
[0043] FIG. 2 illustrates an exemplary representation (200) of the UE (104), in accordance with an embodiment of the present disclosure. As illustrated UE (104) may include one or more processors (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that manipulate data based on operational instructions. Among other capabilities, one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204). The memory (204) may store one or more computer-readable instructions or routines, which may be fetched and executed to create or share the data units over a network service. The memory (204) may comprise any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as EPROM, flash memory, and the like.
[0044] The UE (104) may also comprise an interface(s) (206). The interface(s) (206) may comprise a variety of interfaces, for example, interfaces for data input and output devices, referred to as I/O devices, storage devices, SCADA, Sensors and the like. The interface(s) (206) may facilitate communication of the computing device (102) with various devices coupled to it. The interface(s) (206) may also provide a communication pathway for one or more components of the UE (104). Examples of such components include, but are not limited to, processing engine(s) (202) and database (210).
[0045] The one or more processors (202) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the one or more processors (202). In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the one or more processors (202) may be processor executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the one or more processors (202) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the one or more processors (202). In such examples, the system (104) may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system (104) and the processing resource. In other examples, one or more processors (202) may be implemented by electronic circuitry. In an aspect, the database (210) may comprise data that may be either stored or generated as a result of functionalities implemented by any of the components of the processor (202) or the processing engines (208).
[0046] In an exemplary embodiment, the processing engine(s) (208) of the UE (104) may include, a data acquisition engine (212), a monitoring engine (214), a switching engine (216) and other engines (218) wherein the other engines (218) may further include, without limitation, storage engine, computing engine, signal generation engine, or a time series prediction engine.
[0047] In an embodiment, the data acquisition engine (212) may receive data from one or more components of UE (104) to compute values of a predefined set of parameters associated with data transmission via a first Internet of Things (IoT) network (e.g., NBIoT). In an embodiment, the data acquisition engine may execute an embedded application stored in the memory (204) when the UE (104) is powered on. In an embodiment, the embedded application upon execution causes the modem of the UE (104) to connect to a default communication network or the first IoT network. In an embodiment, the predefined set of parameters comprises application payload delivery status, NAS payload send status, radio condition, and lower layer failures. In an embodiment, the value of each of the predefined set of parameters correspond to either “0” or “1”. In an embodiment, the positive determination is made when the value of each of the predefined first set of parameters is “0”.
[0048] In an embodiment, the monitoring engine (214) may monitor the computed values of the predefined set of parameters to determine whether the value of each of a predefined first set of parameters out of the predefined set of parameters is below a predefined threshold. In an embodiment, the predefined first set of parameters include three or more parameters out of the predefined set of parameters. In an embodiment, the predefined threshold may be different for each of the predefined set of parameters. In an embodiment, the predefined threshold may be same for each of the predefined set of parameters. In an embodiment, the values of each of the predefined set of parameters may be quantized values and not a digital “0” or “1”.
[0049] In an embodiment, upon a positive determination by the monitoring engine (214) that the value of each of a predefined first set of parameters out of the predefined set of parameters is below a predefined threshold, the switching engine (216) may transmit a network change command or a trigger, to a modem comprised in the UE (104), through one or more Application Program Interfaces (APIs). The network change command corresponds to a switch from the first IoT network (i.e., NBIoT) to a second IoT network (e.g., WBIoT).
[0050] In an embodiment, the predefined first of parameters comprises any three of application payload delivery status, NAS payload send status, radio condition, and lower layer failures. In an embodiment, the embedded application when executed causes the processor (202) or the monitoring engine (214) to wait for application layer and TCP layer to exhaust the ongoing transmission attempt via the first IoT network before saving the application data set.
[0051] In an embodiment, the embedded application when executed causes the processor (202) to store a copy of application data set, associated with a previously failed transmission attempt via the first IoT network, in a buffer memory comprised in the UE (104). In an embodiment, the embedded application saves such application data set subsequent to a predefined number of attempts for successful transmission. In another embodiment, the embedded application may wait for execution of predefined number of retries of ongoing transmission of data. In an embodiment, the switching engine (216) causes the modem to, responsive to receiving the network change command from the monitoring engine (214), disassociate from the first IoT network and initiate an attempt to associate with the second IoT network.
[0052] FIG. 3 illustrates an exemplary representation of the signal flow diagram in the communication network, in accordance with an embodiment of the present disclosure. As illustrated, the signal flow may take place between an IoT device/UE (104), operatively coupled to an eNodeB (116) comprising an NBIoT network and communicatively coupled to an Evolved Packet Core (EPC) (306) comprising MME (314), S-GW (316), P-GW (318) that is further coupled to a HSS (320). In an embodiment, the IoT device may include a set of characteristics 322. For example, the IoT Device (UE) may have Multi RAT support (WBIoT and NBIoT). In another example, the IoT Device (UE) may have a SIM configured with at least two profiles that has at least two different international mobile subscriber identity (IMSI) burnt therein. In an embodiment, the HSS/PGW/MME may have separate definitions for the at least two IMSIs, one belonging to NBIoT and other belonging to WBIoT. In an embodiment, a default Network type may be defined in the device as per the use case. When the IoT device will be turned on, the IOT device will attempt to attach to the default network type. In an embodiment, cells of NBIoT-RAT and WB-EUTRAN may be configured with different tracking area codes.
[0053] In an embodiment, the IoT device (302) at step 324, initiates an attach procedure through a non-access stratum (NAS) layer that may include a tracking area id, IMSI, public land mobile network (PLMN) ID. The eNodeB (304), at step (326) then sends S1AP initial UE message that contains the attach request and the packet data network (PDN) connectivity request. The S1AP protocol provides transport function between the UE/IOT device and the MME (314) by offering NAS signalling transport. The NAS protocol provides mobility management and session management between the User equipment (UE) (302) and the MME (314). The EPC (306) may, at step (328), then send an update location request to the HSS (320) in response to which the HSS (320) then sends an update location request answer (330) that may include IMSI, aggregate maximum bit rate (MBR0 during downlink (DL) and uplink (UL), Mobile Station International Subscriber Directory Number (MSISDN), Access Point Name (APN)=PDN GW address, Quality of Systems (QoS) Class Identifier (QCI), charging, aggregate MBR (DL and UL) and the like to the EPC (302).
[0054] The MME (314), at step (332), may then send a create session request to the S-GW (316) in response to which the S-GW (316), at step (334), may send a create default bearer request to the P-GW (318). The P-GW (318), at step (336), may then send a create default bearer response to the S-GW (316) and on its receipt, the S-GW (316), at step (338) may send a create session response to the MME (314). The MME (314) at step (340), then sends initial context set up request having attach accept and activate Evolved Packet System (EPS) bearer request.
[0055] As per 3GPP TS 23.401, cells of NB-IoT RAT and WB-EUTRAN are configured with different Tracking Area codes. In an embodiment, when the IoT device or UE tries to attach with the NBIoT cell and NBIoT provisioned SIM, the EnodeB will send the attach message in the Initial UE message to the MME over the S1AP interface. The message also includes the PDN Connectivity Request message. The Tracking Area Identify (TAI) and the NB-IoT Cell Global Identifier (ECGI) are also included in the attach message. The MME (314) would identify from the Tracking Area or group of Tracking Area whether the TA belongs to NBIoT or WBIoT.
[0056] During call setup or update procedures, the MME (314) passes the RAT Type as NBIoT to other nodes such as SGW, PGW or peer MME. The MME (314) also passes the RAT type information to HSS (320) over the S6a interface. MME (314) initiates the default route establishment by asking the S-GW (316) to create a GTP tunnel. The APN specified by the UE/IoT device (302) is used for default bearer activation. The IP Address assigned to the UE/IoT device (302) is also included along with the downlink and uplink maximum data rates allowed at the APN level. Once the UE attaches to the NBIoT network, it would execute the usual use case and an embedded application therein will record and keep monitoring a set of parameters through APIs which give real time data about the modem from the lower layers to the application layer. In an embodiment, the set of parameters include application payload delivery status, NAS transmit/receive status, NBIoT radio condition, and lower layer failures.
[0057] In an embodiment, the embedded application may have a predefined criteria which will have these parameters as an input to decide whether to switch the network type (e.g., NBIoT to WBIoT). The status value of these parameters may be represented as a binary “1” or “0”. Based on the status value, the application may trigger the modem (of the UE) to detach from the attached network (e.g., NBIoT) and switch to the WBIoT network.
[0058] Next, the UE (302) may start scanning for WBIoT network and attach to the WBIoT network following the same attach process described above. The tracking area will be different and will belong to the WBIoT network definition. The UE (302) may attach to the WBIoT network and attempt to transmit the same data from its internal buffer/ROM memory which was not successfully transmitted on the NBIoT network.
[0059] In an embodiment, the UE (302) may also voluntarily switch (e.g., without any trigger from the application) its radio to WBIoT for certain use cases like firmware upgrade which has large application data to be downloaded.
[0060] Embodiments of a computer-implemented method for switching between a first IoT network and a second IoT network are disclosed. As described above, the first IoT network may correspond to NBIoT and the second IoT network may correspond to WBIoT. In an embodiment, the method includes computing, by a processor comprised in an Internet of Things (IoT) device, values of a predefined set of parameters associated with data transmission via the first IoT network.
[0061] The method further includes determining, by the processor, whether the value of each of a predefined first set of parameters out of the predefined set of parameters is below a predefined threshold. In an embodiment, the predefined first set of parameters comprises one or more of application payload delivery status, NAS payload send status, radio condition, and lower layer failures. In an embodiment, the predefined set of parameters comprises any three of application payload delivery status, NAS payload send status, radio condition, and lower layer failures. In an embodiment, the value of each of the predefined set of parameters correspond to either “0” or “1”. In an embodiment, the positive determination is made when the value of each of the predefined first set of parameters is “0”.
[0062] The method further includes, upon a positive determination, transmitting, by the processor, a network change trigger, to a modem comprised in the IoT device, through one or more Application Program Interfaces (APIs), wherein the network change trigger corresponds to the switching from the first IoT network to a second IoT network.
[0063] In an embodiment, the method further includes executing, by the processor, an embedded application stored in the memory when the IoT device is powered on. In an embodiment, the method further includes: upon execution of the embedded application, connecting, by the processor, to a default communication network, wherein the default communication network corresponds to the first IoT network.
[0064] In an embodiment, the method further includes waiting, by the processor, for the application layer and the TCP layer to exhaust an ongoing transmission attempt using the first IoT network (e.g., NBIoT). In an embodiment, the method further includes storing, by the processor, a copy of application data set, associated with a previously failed transmission attempt, in a buffer memory comprised in the IoT device. In an embodiment, the method further includes, responsive to receiving the network change command/trigger, disassociating, by the processor, from the first IoT network and initiating, by the processor, an attempt to associate with the second IoT network (e.g., WBIoT).
[0065] FIG. 4 illustrates an exemplary representation of the proposed method (400) for switching between a first IoT network and a second IoT network, in accordance with an embodiment of the present disclosure. The proposed method (400) may include at step (402), the step of powering on the UE or IoT device (e.g., 104, 302). As described above, the UE is configured with a default IoT network type when powered on. At step (404), the method may include the step of attaching the device to the default network. At (406), the method may include the step of reporting by an embedded application executed by the UE, the application data to the application server (e.g., 112). At 408, the method may include the step of recording and monitoring values, by the embedded application, of a set of parameters listed in TABLE 1 below (also shown as 410) while reporting the application payload/data set to the application server.
TABLE 1
Parameter Definition Value
Application payload delivery status Application data sent “1” or “0”
NAS transmit/receive status NAS payload delivered. If receive RLC ACK from the EnodeB “1” or “0”
Radio condition Good (RSRP>-100 dBm, SNR>0)
Bad (RSRP<-100 dBm, SNR<0) “1” or “0”
Lower layer failures No Radio Link Failure detected “1” or “0”

[0066] At 412, it is determined whether the values for the set of parameters is high during the ongoing data transaction (e.g., “1”). Upon a positive determination, at 424, the method may include continuing to transmit data using the current IoT network (e.g., NBIoT) and not sending any trigger (by the embedded application. Further, at 426, the IoT device stays on the same network. Upon a negative determination, at 414, it is determined if the value for any of the three parameters is low (i.e., Binary “0”) and all the retries at application layer and TCP layers are exhausted for the attempted ongoing data transmission. At 416, the method may include the step of storing by the embedded application, the copy of the complete application data that had failed (during the previously attempted transmission) in its internal buffer memory and also sending a RAT/Network change command or trigger to the modem through APIs.
[0067] At 418, the method may include the step of detaching by the modem (of the IoT device) from the attached network type (e.g., NBIoT) and switching its radio and trying to attach to the other network type (WBIoT). At 420, once the IoT device is attached to the WBIoT network, it will retry to send the application payload through the attached WBIoT network and at 422, once the data is sent successfully, the IoT device stays on the WBIoT network till it is power cycled (switched “off” and switched “on” again). After the power cycle, device would return back to the default network.
[0068] FIG. 5 illustrates an exemplary computer system in which or with which embodiments of the present invention can be utilized in accordance with embodiments of the present disclosure. As shown in FIG. 5, computer system 500 can include an external storage device 510, a bus 520, a main memory 530, a read only memory 540, a mass storage device 550, communication port 560, and a processor 570. A person skilled in the art will appreciate that the computer system may include more than one processor and communication ports. Processor 550 may include various modules associated with embodiments of the present invention. Communication port 560 can be any of an RS-232 port for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fibre, a serial port, a parallel port, or other existing or future ports. Communication port 560 may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which computer system connects. Memory 550 can be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. Read-only memory 540 can be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or BIOS instructions for processor 570. Mass storage 550 may be any current or future mass storage solution, which can be used to store information and/or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and/or Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g. an array of disks (e.g., SATA arrays).
[0069] Bus 520 communicatively couple processor(s) 570 with the other memory, storage and communication blocks. Bus 520 can be, e.g., a Peripheral Component Interconnect (PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), USB or the like, for connecting expansion cards, drives and other subsystems as well as other buses, such a front side bus (FSB), which connects processor 550 to software system.
[0070] Optionally, operator and administrative interfaces, e.g., a display, keyboard, and a cursor control device, may also be coupled to bus 520 to support direct operator interaction with a computer system. Other operator and administrative interfaces can be provided through network connections connected through communication port 560. Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system limit the scope of the present disclosure.
[0071] Thus, the present disclosure provides for a unique and efficient system and method that can leveraged the advantages of two or more types of networks by a single device and provides flexibility to Solution Owners to switch the network on the go to reduce failures.
[0072] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the invention. These and other changes in the preferred embodiments of the invention will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter to be implemented merely as illustrative of the invention and not as limitation.

RESERVATION OF RIGHTS
[0073] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, IC layout design, and/or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (herein after referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.

ADVANTAGES OF THE INVENTION
[0074] The present disclosure provides a provision in a Long Term Evolution (LTE) Standard based IoT backend network to allow an IoT device to select either of the two cellular IoT networks as and when required.
[0075] The present disclosure provides a mechanism to the end points (IoT Devices) to seamlessly switch between WBIoT and NBIoT networks based on a predefined criteria.
[0076] The present disclosure reduces business impact and poor SLAs pertaining to performance issues caused by limitations of Low-power Wide Area network (LPWAN) by introducing interworking between different LTE based cellular IoT networks.
,CLAIMS:1. A user equipment (UE), comprising:
a processor coupled to a memory comprising a set of instructions that when executed by the processor causes the processor to:
compute values of a predefined set of parameters associated with data transmission via a first Internet of Things (IoT) network;
determine whether the value of each of a predefined first set of parameters out of the predefined set of parameters is below a predefined threshold; and
upon a positive determination, transmit a network change command, to a modem comprised in the UE, through one or more Application Program Interfaces (APIs), wherein the network change command corresponds to a switch from the first IoT network to a second IoT network.

2. The UE as claimed in claim 1, wherein the first IoT network corresponds to Narrow Band Internet of Things (NBIoT) network and the second IoT network corresponds to Wide Band Internet of Things (WBIoT) network.

3. The UE as claimed in claim 1, wherein the memory further comprises set of instructions that when executed by the processor causes the processor to execute an embedded application stored in the memory when the UE is powered on.

4. The UE as claimed in claim 3, wherein the embedded application upon execution causes the UE to connect to a default communication network, wherein the default communication network corresponds to the first IoT network.

5. The UE as claimed in claim 1, wherein the predefined set of parameters comprises application payload delivery status, NAS payload send status, radio condition, and lower layer failures.

6. The UE as claimed in claim 1, wherein the value of each of the predefined set of parameters correspond to either “0” or “1”.

7. The UE as claimed in claim 6, wherein the positive determination is made when the value of each of the predefined first set of parameters is “0”.

8. The UE as claimed in claim 6, wherein the predefined first of parameters comprises any three of application payload delivery status, NAS payload send status, radio condition, and lower layer failures.

9. The UE as claimed in claim 7, wherein the memory further comprises set of instructions that when executed by the processor causes an embedded application to wait for application layer and TCP layer to exhaust the ongoing transmission attempt via the first IoT network.

10. The UE as claimed in claim 9, wherein the memory further comprises set of instructions that when executed by the processor causes the embedded application to store a copy of application data set, associated with a previously failed transmission attempt via the first IoT network, in a buffer memory comprised in the UE.

11. The UE as claimed in claim 1, wherein the memory further comprises set of instructions that when executed by the processor causes the modem to, responsive to receiving the network change command, disassociate from the first IoT network and initiate an attempt to associate with the second IoT network.

12. A computer-implemented method for switching between a first Internet of Things (IoT) network and a second IoT network, the method comprising:
computing, by a processor comprised in an IoT device, values of a predefined set of parameters associated with data transmission via the first IoT network;
determining, by the processor, whether the value of each of a predefined first set of parameters out of the predefined set of parameters is below a predefined threshold; and
upon a positive determination, transmitting, by the processor, a network change trigger, to a modem comprised in the IoT device, through one or more Application Program Interfaces (APIs), wherein the network change trigger corresponds to the switching from the first IoT network to a second IoT network.

13. The method as claimed in claim 12, wherein the first IoT network corresponds to Narrow Band Internet of Things (NBIoT) network and the second IoT network corresponds to Wide Band Internet of Things (WBIoT) network.

14. The method as claimed in claim 12 further comprising executing, by the processor, an embedded application stored in the memory when the IoT device is powered on.

15. The method as claimed in claim 14 further comprising: upon execution of the embedded application, connecting, by the processor, to a default communication network, wherein the default communication network corresponds to the first IoT network.

16. The method as claimed in claim 12, wherein the predefined set of parameters comprises application payload delivery status, NAS payload send status, radio condition, and lower layer failures.
17. The method as claimed in claim 12, wherein the value of each of the predefined set of parameters correspond to either “0” or “1”.

18. The method as claimed in claim 17, wherein the positive determination is made when the value of each of the predefined first set of parameters is “0”.

19. The method as claimed in claim 17, wherein the predefined first of parameters comprises any three of application payload delivery status, NAS payload send status, radio condition, and lower layer failures.

20. The method as claimed in claim 18 further comprising: waiting, by the processor, for application layer and TCP layer to exhaust an ongoing transmission attempt.

21. The method as claimed in claim 18 further comprising: storing, by the processor, a copy of application data set, associated with a previously failed transmission attempt, in a buffer memory comprised in the IoT device.

22. The method as claimed in claim 1 further comprising, responsive to receiving the network change command, disassociating, by the processor, from the first IoT network and initiating, by the processor, an attempt to associate with the second IoT network.