FORM 2
THE PATENTS ACT, 1970
(39 OF 1970)
AND
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM OF DATA DELIVERY OVER ROAMING NETWORK IN CAT-NARROW BAND (NB) - IoT”
We, RELIANCE JIO INFOCOMM LIMITED, an Indian National, of, 3rd Floor, Maker Chamber-IV, 222, Nariman Point, Mumbai- 400021, Maharashtra, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

FIELD OF INVENTION
The present invention relates to wireless communications, and more particularly, to data delivery mechanism in roaming network via CAT- Narrow Band- Internet of Things (NB-IoT) cell/channel.
BACKGROUND OF THE INVENTION
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.
The Internet of Things (IoT) is a network of devices, vehicles, home appliances, and other items embedded with electronics, software, sensors, actuators, and connectivity which can be readable, recognizable, locatable, addressable, and controllable via an IoT communications network that enables these things to connect and exchange data, creating opportunities for more direct integration of the physical world into computer-based systems, resulting in efficiency improvements, economic benefits, and reduced human exertions. The “Internet of things” (IoT) concept is getting more and more popular, and devices, such as sensors, actuators and everyday objects including the coffee makers, washing machines, headphones, lamps and wearable devices, etc. are being increasingly looked upon as potential IoT devices. IoT involves extending Internet connectivity beyond standard devices, such as desktops, laptops, smartphones and tablets, to any range of traditionally dumb or non-internet-enabled physical devices and everyday objects. Embedded with technology, these devices can communicate and interact over the Internet, and they can be remotely monitored and controlled. The term "Enterprise IoT" refers to devices used in business and corporate settings in a network of physical objects that contain embedded technology to communicate and sense or interact with their internal

states or the external environment. Here, IoT refers to Internet-connected physical devices, in many cases everyday objects (things) that can communicate their status, respond to events, or even act autonomously. This enables communication among those things, closing the gap between the real and the virtual world and creating smarter processes and structures that can support us without needing our attention. IoT has evolved from the convergence of wireless technologies, micro-electromechanical systems (MEMS), and the Internet. An IoT device is generally provisioned with an IP address to provide it with the capability of transferring data and receive control signals over an IP network using the standard Internet protocols such as TCP/IP which is being exclusively used on the Internet.
Recently, 3GPP has introduced a new technology NB-IoT in release 13. The low-end IoT applications can be met with this technology. This technology has better performance than Low Power Wide Area Networks (LPWAN). It has taken efforts to address IoT markets with completion of standardization on NB-IoT. The NB-IoT technology has been implemented in licensed bands of LTE, which are used for exploiting this technology. This technology makes use of a minimum system bandwidth of 180 kHz i.e. one PRB (Physical Resource Block) is allocated for this technology. The NB-IoT can be seen as a separate RAT (Radio Access Technology). The NB-IoT can be deployed in 3 modes: “in-band”, “guard band” and “standalone”. In the “in-band” operation, resource blocks present within LTE carrier are used. The inner resource blocks are not used as they are allotted for synchronization of LTE signals. In “guard band” operation, resource blocks between LTE carriers that are not utilized by any operator are used. In “standalone” operation, GSM frequencies are used or possibly unused LTE bands are used. Release 13 contains important refinements like extended or enhanced discontinuous reception (eDRX) and power save mode (PSM). The PSM ensures battery longevity in release 12 and is completed by eDRX for devices that need to receive data more frequently.

The NB-IoT technology focuses on devices like meter reading of water and electricity consumption that are stationery. Some of the use cases are: facility management services, fire alarms for home and commercial properties, tracking of persons and objects. The industries where NB-IoT services can add value are: Smart city, smart home, Safety and security, agriculture, health care and Energy. Another example for IoT industry includes logistic tracking. The tracking devices on shipping containers send huge volumes of sensor data that are collected and taken for analysis in order to make sure that real-time tracking of shipment locations can be made possible. The output display units are used for receiving alerts and optimized with service recommendations. The NB-IoT technology addresses some of the key IoT requirements:
• Battery lifetime of the devices increases.
• Improved network coverage.
• Cost of the devices is reduced.
• Multiplexing of devices met for capacity requirements.
• Support a massive number of devices.
The NB-IoT technology support low power consumption, use of low-cost devices
and provides excellent coverage.
In a NB-IoT deployment, the NB-IoT cells have a 20db gain over other categories
like CAT-1/4 cells. As such, the NB-IoT Carrier can support much larger areas
when compared to a CAT-1/4 base station or channel. Typically in NB-IOT
scenario, the same base station provides the NB-IoT channels for a device. The
same or a different base station can provide a channel for a CAT-1 or a CAT-3/4
operation due to the difference in the NB-IoT and other category cell coverage
areas.
Every network operator has a unique Public Land Mobile Network (PLMN)
number. PLMN number consists of the Mobile Country Code (MCC) and Mobile

Network Code (MNC). Every subscriber of service provider operator is identified by a unique International Mobile Subscriber Identity (IMSI) which consists of the PLMN (MCC, MNC) of the service provider operator and the Mobile Subscription Identification Number (MSIN). The PLMN contained in the subscriber’s IMSI is called Home PLMN 5 (HPLMN) and the corresponding network is referred to as Home Network (HN). When a subscriber of an operator tries to attach to another network operator due to various reasons like unavailability of home network, etc. it is identified as a Roaming Subscriber (RS) and that network is referred to as Roamed Network (RN) or Visited PLMN (VPLMN). The roaming subscriber can access the roamed network services as per the bilateral roaming agreements between the home and the roamed network operators.
The current IoT devices latch on the HPLMN in the CAT- NB and provide services from the service provider as subscribed by the subscriber. In NB-IoT, data delivery may occur through IP-path or non-IP path. If the IoT device uses a non-IP path, it utilises the Service Capabilities Exposure Function (SCEF) of the HPLMN. When the IoT device goes into a VPLMN, the standard provides for the utilisation of Interworking SCEF (IWK-SCEF), i.e. the SCEF of the HPLMN talks to the IWK-SCEF of the VLPMN to enable data delivery via non-IP path. The IWK-SCEF receives the Monitoring Event Reports from the underlying entities and sends them to the SCEF. The IWK-SCEF relays the non-IP data between the MME and the SCEF. IWK-SCEF routes the data in this scenario from VPLMN to the HPLMN. However, it is to be noted that deployment of the IWK-SCEF is optional. Thus, when IWK-SCEF is not deployed, the non-IP data delivery in the VPLMN fails. Thus, there is a challenge for providing data service in roaming network of IoT system. When NB device moved from Home PLMN to Visited PLMN in a CP-CIoT (Control plane cellular IoT) supported cell, the NB device initiate ATTACH request for Non-IP data delivery (NIDD) with CP-CIoT optimization. If IWK-SCEF is not deployed in the visited PLMN, NB device cannot attach for Non-IP data delivery with CP-CIoT optimization support between the device and application server.

Currently, there is no mechanism for IoT Device to initiate request for Non-IP data delivery (NIDD) with CP-CIoT optimization, if IWK-SCEF is not deployed in the visited PLMN. There is no method defined on how the IoT device may be able to latch on the other VPLMN for smooth IoT data delivery. There is primarily a challenge for latching on other VPLMN for smooth IoT data delivery and this is necessary as continuous bandwidth which will help to provide efficient way of connectivity to billions of devices in roaming network. Also as the numbers grow for the IoT devices in future there needs to be an efficient architecture for latching on the VPLMN for NB-IoT service request for quicker service delivery. Therefore, there is a need in the art for a system and method to support latching on other VPLMN for smooth IoT data delivery, when the IoT device is roaming in the said VPLMN.
SUMMARY
This section is provided to introduce certain objects and aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
In order to overcome at least a few problems associated with the known solutions as provided in the previous section, an object of the present disclosure is to provide a method and system of data delivery over roaming network in CAT-Narrow Band (NB) – IoT. It is another object of the invention to provide a system and method that can support latching on VPLMN for smooth IoT data delivery as this is necessary for continuous bandwidth to provide an efficient way of connectivity to billions of devices in roaming network. It is also an object of the invention to enable connectivity in visited or roaming network that does not support IWK-SCEF. It is yet another object of the invention to address the issue of connectivity of NB IoT devices in roaming network. It is also an object of the present invention to enable connectivity in the NB-IoT tacking device in roaming

network. Yet another object of the present invention is to provide IP data path (over S8 interface) for data delivery between NB device and application server. In order to achieve the aforementioned objectives, the present disclosure provides a method and system of data delivery over a roaming network via a Narrow band – Internet of Things (NB-IoT) device.
One aspect of the present invention relates to a method of data delivery over a roaming network via a Narrow band – Internet of Things (NB-IoT) device. The said method comprises, receiving, at the NB-IoT device, via said roaming network, at least one system information broadcast message. The system information broadcast message further comprises a Control Plane – Cellular IoT (CP-CIoT) Optimization Support indication or an additional information element. Thereafter, the method comprises, identifying, by the NB-IoT device, an absence of an inter-working service capabilities exposure function support in the said roaming network, based on which said NB-IoT device attaches to the roaming network via an IP-data delivery path, to facilitate data delivery over said roaming network.
Another aspect of the present disclosure encompasses a Narrow band (NB) – IoT device comprising a transceiver unit configured to receive, via said roaming network at least one system information broadcast message; a processing unit connected to said receiver unit, configured to identify, an absence of an inter-working service capabilities exposure function support in said roaming network; and attach, said NB-IoT device to the roaming network via an IP-data delivery path, based on identification of said absence of the inter-working service capabilities exposure function support in said roaming network, to facilitate data delivery over said roaming network.
BRIEF DESCRIPTION OF DRAWINGS
The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, 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 disclosure. 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 disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components. FIG.1 illustrates a general overview of the network environment in which the present invention is implemented, in accordance with exemplary embodiments of the present disclosure.
FIG.2 illustrates a block diagram of NB-IoT Device, in accordance with exemplary embodiments of the present disclosure.
FIG.3 illustrates an exemplary diagram of the roaming network, in accordance with exemplary embodiments of the present disclosure.
FIG. 4 illustrates an exemplary method flow diagram depicting data delivery over a roaming network via a Narrow band – Internet of Things (NB-IoT) device. FIG. 5 illustrates an exemplary signalling flow diagram for VPLMN ATTACH in NB-IoT Device, in accordance with a first embodiment of the present disclosure. FIG. 6 illustrates an exemplary signalling flow diagram for VPLMN ATTACH in NB-IoT Device, in accordance with a second embodiment of the present disclosure. The foregoing shall be more apparent from the following more detailed description of the disclosure.
DESCRIPTION OF THE INVENTION
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.
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.
Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.

As used herein, the “NB-IoT device” or “IoT device” or "NB-IoT Device“, refers to any electrical, electronic, electromechanical and computing device. The NB-IoT device is capable of receiving and/or transmitting one or parameters, performing function/s, communicating with other NB-IoT devices as well as legacy devices and transmitting data to the devices. The NB-IoT device may have a processor, a display, a memory, a battery and an input means such as a hard keypad and/or a soft keypad. The at least one NB-IoT device may include, but is not limited to, a thermostat, an electric switch, a washing machine, a computing device, a coffee maker, a refrigerator, a headphone, a lamp, a room sensor, a microwave, a fan, a light and any such device that is obvious to a person skilled in the art. NB-IoT devices may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, etc.
As used herein, a “processor” or “processing unit” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
As used herein, “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic

disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media.
Systems depicted in some of the figures may be provided in various configurations. In some embodiments, the systems may be configured as a distributed system where one or more components of the system are distributed across one or more networks in a cloud computing system.
The present invention facilitates data delivery over a roaming network via a Narrow band – Internet of Things (NB-IoT) device.
As used herein, the roaming network is a visitor cellular network for providing voice services (calls) and the data services to the NB-IoT Device.
Referring to FIG. 1, that illustrates a general overview of the network environment [100] in which the present invention is implemented, in accordance with exemplary embodiments of the present disclosure. As shown in Fig. 1, the NB-IoT Device [102A], [102B], [102C]….. [102N] (Collectively referred to as NB-IoT Device [102]) may be connected to at least one roaming network entity [104]. Further, the said roaming network entity [104] comprises at least one transceiver unit [106], at least one processing system [108] and at least one interface [110]. The roaming network entity [104] may provide network access to the one or more NB-IoT Device [102A – 102N] connected to the roaming network and thereby, the one or more NB-IoT Device [102A – 102N] may avail voice and data services using said network. The roaming network entity [104] is also capable of provisioning and supporting NB-IoT RAT to the NB-IoT Device [102] via one or more access points such as an IoT gateway.
The roaming network entity [104] may be one or more cellular network entities in a wireless LTE network that serves a network for providing voice services (calls) and the data services to the NB-IoT Device. The roaming network [104] may include, but not limited to, a base station controller, a base transceiver station, a cell site, a Node B, an eNodeB, a radio network controller, etc.

Further the said NB-IoT Device [102] may be an NB-IoT device and may include,
but not limited to, a mobile phone, a tablet, a phablet, a laptop, a desktop
computer, a personal digital assistant (PDA), a consumer electronics device such
as meter, television etc. and said NB-IoT Device [102] may be configured to
receive at least one of a data or voice service from the said roaming network
[104].
The processing system [108] may be configured to execute functions/operations
performed by each module/component of the roaming network [104]. The
processing system [108] as used herein may include, but not limited to, a
processor or set of processors such as a microprocessor, a multi-core
microprocessor, a digital signal processor, a collection of electronic circuits, or a
combination thereof and may be configured to perform operations /functions as
described herein.
Further the transceiver unit [106] coupled to said processor system [108] may
include at least one transmission unit and at least one receiving unit and the said
transceiver unit [106] may be configured to transmit and receive the
communication signals/data via roaming network entity [104] to NB-IoT Device
[102] and vice versa respectively.
The interface [110] may be coupled to the transceiver unit [106] and processing
system [108] and the said interface [110] may be configured for backhaul and to
further reach out to an on-boarding server for information exchange.
Although a limited number of NB-IoT Devices [102] are shown in Fig. 1, however,
it will be appreciated by those skilled in the art that the invention encompasses
the use of multiple such NB-IoT Devices [102].
As illustrated in FIG. 2, an exemplary NB-IoT device [102] deployed in the
roaming network, is shown. The NB-IoT device [102] comprises at least one
transceiver unit [210], at least one antenna [212], at least one IoT application
module [202], at least one memory unit [206], at least one on-boarding client

module [208] and at least one processing unit [204], said components being connected to each other.
The transceiver unit [210] of the said NB-IoT device [102] is coupled to said antenna [212], IoT application module [202], on-boarding client module [208] and processing unit [204]. The transceiver unit [210] may be configured to receive, via said roaming network entity [104] at least one system information broadcast message, wherein the said system information broadcast message comprises one of a Control Plane – Cellular IoT (CP-CIoT) Optimization Support indication, and an additional information element. The additional information element of said system information broadcast message indicates the absence of the inter-working service capabilities exposure function (IWK-SCEF) support. Further, the said transceiver unit [210] may also be configured to transmit an attach request message via a non-IP data delivery path.
The transceiver unit [210] may further configured to receive, from the roaming network entity [104] at the NB-IoT device [102], an attach reject message, wherein said attach reject message comprises at least an indication of said absence of the inter-working service capabilities exposure function support in said roaming network [104].
Further, the transceiver unit [210] is also configured to transmit an attach request message via a IP data delivery path and thereafter said transceiver unit [210], in response to said attach request message via a IP data delivery path, further configured to receive, from the roaming network entity [104] at the NB-IoT device [102], an attach accept message for said attach request message via said IP data delivery path.
In an instance, the said transceiver unit [210] in a roaming network may transmit at least one attach request message via a Non-IP data delivery path and as a response to said request may receive an attached reject message due to unavailability of the inter-working service capabilities exposure function in said roaming network. Further after identification of unavailability of the inter-

working service capabilities exposure function in said roaming network, the said transceiver unit [210] may further transmit at least one attach request message via a IP data delivery path in order to enable data delivery over the roaming network via a Narrow band – Internet of Things (NB-IoT) device [102]. Thereafter the said transceiver unit [210] may receive from the roaming network entity [104] an attach accept indication in response to said attach request message via an IP data delivery path to enable data delivery over said roaming network. The memory unit [206] is coupled to said IOT application module [202], on-boarding client module [208] and processing unit [204]. The memory unit [206] is configured to store data from the different modules of NB-IoT Device [102], in order to assist the said modules to carry out different functions. The said memory unit [206] is also further configured to perform the storage management of the said NB-IoT Device [102].
The IoT application module [202] is coupled to said Transceiver unit [210], memory unit [206], on-boarding client module [208] and processing unit [204]. The IoT application module [202] may be configured to implement IoT functionality in combination with multiple hardware and software components. The said IoT application module [202] is further configured to communicate over the desired IP path via said transceiver unit [210].
The on-boarding client module [208] is coupled to said Transceiver unit [210], one memory unit [206], IoT application module [202] and processing unit [204]. The on-boarding client module [208] may be configured to communicate to an on-boarding server via the Transceiver unit [210] while being in charge of device-specific on-boarding function.
Further, the processing unit [204] of NB-IoT Device [102] is coupled to said, IoT Application module [202], transceiver unit [210], the memory unit [206], and the on-boarding client module [208]. The processing unit [204] is configured to execute the functions of all modules present in the NB-IoT Device [102]. Further, the processing unit [204], is configured to identify an absence of an inter-working

service capabilities exposure function support in the roaming network and to attach, said NB-IoT device [102] to the roaming network entity [104] via an IP-data delivery path, based on identification of said absence of the inter-working service capabilities exposure function support in said roaming network, in order to facilitate data delivery. Furthermore, the said processing unit [204], is also configured to decode the system information broadcast message to identify the absence of the inter-working service capabilities exposure function support in said roaming network [104] based on said decoding. The processing unit [204], may also be configured to switch said NB-IoT device [102] from the roaming network [104] to a home network of said NB-IoT device [102].
In an instance, the said processing unit [204], identifies the absence of an inter-working service capabilities exposure function support in a roaming network, wherein the said identification may be based on the decoding by said processing unit [204], a system information broadcast message received on the NB-IoT device [102] via roaming network entity [104]. In another instance the said processing unit [204], is configured to identify the absence of an inter-working service capabilities exposure function support in a roaming network by acknowledgement of receipt of an attach reject message in response to an attach request message via a non-IP data delivery path. Thereafter, the processing unit [204], may further attach the NB-IoT device [102] to the roaming network via an IP-data delivery path, based on the identification of said absence of the inter-working service capabilities exposure function support in said roaming network, to facilitate data delivery over said roaming network. In yet another instance when the NB-IoT device [102] is moved back in home network the said processing unit [204], may facilitate the switching said NB-IoT device [102] from the roaming network to a home network of said NB-IoT device [102]. Referring to FIG. 3, the present invention illustrates an exemplary diagram of the roaming network entity [104], in accordance with exemplary embodiments of the present disclosure. As shown in Fig. 3, the roaming network entity [104]

comprises at least one antenna [310], at least one transceiver unit [106], at least one processing system [108] and at least one interface [110]. The said processing system [108] further comprises at least one processor [302] and at least one memory [304].
The antenna [310] coupled with the transceiver unit [106], is configured to transmit or receive the radio signals via said transceiver unit [106]. Further said transceiver unit [106] may include at least one transmission unit and at least one receiving unit (not shown in figure) and the said transceiver unit [106] is configured to transmit or receive the communication signals/data via roaming network [104] to NB-IoT Device [102] or vice versa. In an example, the transceiver unit [106] of roaming network [104] may be configured to establish a tunnel between a serving gateway of said roaming network [104] and a gateway of a home network of said NB-IoT device [102].
The processing system [108] further comprises at least one processor [302] and at least one memory [304]. The said processing system [108] may be configured to execute functions/operations performed by each module/component of the roaming network entity [104]. The processing system [108] as used herein may include, but not limited to, a processor or set of processors such as a microprocessor, a multi-core microprocessor, a digital signal processor, a collection of electronic circuits, or a combination thereof and may be configured to perform operations /functions as described herein. The processor [302] is configured to process the Attach Procedure initiated by the NB-IoT Device [102], wherein the said Attach Procedure may comprise one of a, attach request message via a non-IP data delivery path and attach request message via an IP data delivery path.
Further, the memory [304] is configured to perform memory management of said roaming network [104]. The said memory [304], is also configured to store data related to each component/module of the said roaming network [104].

The interface [110] may be coupled to the processing system [108], wherein said interface [110] may be configured for backhaul and to further reach out to an on-boarding server for information exchange.
Referring to FIG.4, an exemplary method flow diagram [400] depicting data delivery over a roaming network [104] via a Narrow band – Internet of Things (NB-IoT) device [102], is shown.
The method begins at step [402]. The method may begin when the NB-IoT Device [102] is in roaming or visitor network and to enable data delivery over said roaming network via a Narrow band – Internet of Things (NB-IoT) device [102]. The method at step [404], receives, on said NB-IoT Device [102] at least one system information broadcast message via said roaming network [104]. The said system information broadcast message further comprises one of a, Control Plane – Cellular IoT (CP-CIoT) Optimization Support indication, and an additional information element.
Thereafter, the method further at step [406] comprises, identification by the NB-IoT device [102], an absence of an inter-working service capabilities exposure function support in said roaming network. In an event the system information broadcast message comprises said additional information element, which indicates absence of the inter-working service capabilities exposure function support, the identification occurs by decoding said system information broadcast message. Alternatively, in an event, the system information broadcast message comprises CP-CIoT Optimization Support indication, it is not possible to directly determine whether or not inter-working service capabilities exposure function is supported by the roaming network. In such a case, the identification of absence of inter-working service capabilities exposure function, occurs by transmission of an attach request message via a non-IP data delivery path via the NB-IoT device [102] to roaming network entity [104] and receiving, from the roaming network [104] at the NB-IoT device [102], an attach reject message for said attach request message, wherein said attach reject message comprises at least an indication of

said absence of the inter-working service capabilities exposure function support in said roaming network [104].
Therefore, the identification of an inter-working service capabilities exposure function support in said roaming network [102] is done on the basis of a Control Plane – Cellular IoT (CP-CIoT) Optimization Support indication or an additional information element of system information broadcast message.
Thereafter, the method further at step [408], comprises attaching said NB-IoT device [102] to the roaming network [104] via an IP-data delivery path, based on the identification of said absence of the inter-working service capabilities exposure function support in said roaming network, to facilitate data delivery over said roaming network. The said attachment of NB-IoT device [102] to the roaming network via an IP-data delivery path, is achieved by transmitting, via the NB-IoT device [102], an attach request message via a IP data delivery path and thereafter receiving, from the roaming network at the NB-IoT device [102], an attach accept message for said attach request message via said IP data delivery path. Further the method on successful data delivery over a roaming network [102] via a Narrow band – Internet of Things (NB-IoT) device [102], terminates at step [410].
The invention encompasses establishing a tunnel between a serving gateway of said roaming network and a gateway of a home network of said NB-IoT device [102] to facilitate data delivery.
When the NB-IoT Device [102] moves back to the home network, the method thereafter facilitates the switching of said NB-IoT device [102] from the roaming network to a home network of said NB-IoT device [102].
Referring to FIG.5, an exemplary signalling flow diagram [500], for VPLMN ATTACH in NB-IoT Device is shown. The invention encompasses that the method, on receipt of system information broadcast message (SIB2 – NB) begins at step [502], wherein the said SIB2 – NB message comprises CP-CIoT Optimization support indication. Thereafter, the NB-IoT device [102], further processes the

said received SIB2 – NB message with said CP CIoT Optimization support indication and on the bases of said CP CIoT Optimization support indication the NB-IoT Device [102] at step [504] initiates an attach request via a non-IP data delivery path. The said attach request further comprises PDN Type: Non –IP Data / CP CIoT Optimization.
Further, the roaming network entity [104] processes the received, attach request over a non-IP data delivery path and at step [506] the said roaming network entity [104] initiates attach reject indication to the NB-IoT Device [102]. The said attach reject indication further comprises Cause#IWK-SCEF not Supported indication, wherein the said Cause#IWK-SCEF not Supported indication, further indicates the absence of the IWK-SCEF in the said roaming network. For an instance when the inter-working service capabilities exposure function support is not present in a roaming/visitor network, the NB-IoT device [102] fails to deliver data over said roaming network [102] via said non-IP data delivery path. Thereafter, upon rejection of attach request via non-IP data delivery path, the NB-IoT Device [102] further at step [508], further initiates an attach request via IP data delivery path to the roaming network entity [104]. The said attach request via IP data delivery path further comprises PDN Type: IP Data / APN INTERNET. Thereafter, the roaming network entity [104] processes the said attach request via IP data delivery path and at step [510], initiates an Attach Accept indication.
On successful receipt of Attach Accept indication via roaming network entity [104], the NB-IoT Device [102] gets attached/latched to the said roaming network by establishing a tunnel between a serving gateway of said roaming network and a gateway of a home network of said NB-IoT device [102]. The said attaching/latching of the NB-IoT Device [102] with roaming network entity [104] enables the data delivery over a roaming network via a Narrow band – Internet of Things (NB-IoT) device [102].

Referring to FIG. 6, an exemplary signalling flow diagram [600], for VPLMN ATTACH in NB-IoT Device [102] with SIB2 –NB, is shown. The method begins at step [602]. The method at step [602] receives at least one system information broadcast message (SIB2 – NB) via roaming network entity [104] at NB-IoT Device [102], wherein the said SIB2 – NB message comprises at least an additional information element. The additional information element of the said SIB2-NB message further comprises at least one bit, wherein the said bit indicates the absence of the inter-working service capabilities exposure function (IWF-SCEF) support in said roaming network. This additional information element of the said SIB2-NB message is decoded by the processing unit [204] of the NB-IoT Device [102] to identify the absence of the inter-working service capabilities exposure function support in said roaming network based on said decoding. Thereafter, on identifying by the NB-IoT device [102], an absence of an inter-working service capabilities exposure function support in said roaming network [104] the method leads to step [604]. At step [604], NB-IoT Device [102] initiates ATTACH procedure for IP Data mechanism, wherein the said ATTACH procedure is based on decoding of SIB2-NB and verifying the non-availability of IWK-SCEF support in visited PLMN/roaming network [104].
The ATTACH procedure for IP Data mechanism further comprises initiating an attach request via IP data delivery path from the NB-IoT [102] to the roaming network entity [104] and in response to said attach request over IP data delivery path, receiving the Attach accept indication from the roaming network entity [104] on the NB-IoT [102].
On successful receipt of Attach Accept indication via roaming network entity [104], the NB-IoT Device [102] gets attached/latched to the said roaming network [104] by establishing a tunnel between a serving gateway of said roaming network [104] and a gateway of a home network of said NB-IoT device [102].

The said attaching/latching of the NB-IoT Device [102] with roaming network [104] further enables the data delivery over a roaming network [104] via a Narrow band – Internet of Things (NB-IoT) device [102]. Thus, via this procedure, unnecessary signalling between the NB-IoT device [102] and the roaming network entity [104] is avoided as the NB-IoT device [102] receives information relating to the absence of support of the inter-networking service capabilities exposure function via the additional elements included in the broadcast message.
The interface, module, memory, database, processor and component depicted in
the figures and described herein may be present in the form of a hardware, a
software and a combination thereof. The connection shown between these
components/module/interface in are exemplary and any
components/module/interface in the system may interact with each other through various logical links and/or physical links. Further, the components/module/interface may be connected in other possible ways. Though a limited number of servers, gateways, user equipment, wireless network, interface, module, memory, database, processor and other components have been shown in the figures, however, it will be appreciated by those skilled in the art that the overall system of the present invention encompasses any number and varied types of the entities/elements such as servers, gateways, user equipment, wireless network, interface, module, memory, database, processor and component.
While considerable emphasis has been placed herein on the disclosed embodiments, it will be appreciated that many embodiments can be made and that many changes can be made to the embodiments without departing from the principles of the present invention. These and other changes in the embodiments of the present invention will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

We Claim
1. A method of data delivery over a roaming network via a Narrow band –
Internet of Things (NB-IoT) device [102], the method comprising:
- receiving, at the NB-IoT device [102], via a roaming network entity [104], at least one system information broadcast message;
- identifying, by the NB-IoT device [102], an absence of an inter-working service capabilities exposure function support in said roaming network; and
- attaching said NB-IoT device [102] to the roaming network entity [104] via an IP-data delivery path, based on identification of said absence of the inter-working service capabilities exposure function support in said roaming network, to facilitate data delivery over said roaming network.

2. The method as claimed in claim 1, wherein the system information broadcast message further comprises one of a Control Plane – Cellular IoT (CP-CIoT) Optimization Support indication, and an additional information element, wherein said additional information element indicates absence of the inter-working service capabilities exposure function support.
3. The method as claimed in claim 2, wherein in an event, the system information broadcast message comprises the CP-CIoT Optimization Support indication, said identifying the absence of the inter-working service capabilities exposure function support in said roaming network further comprises:

- transmitting, via the NB-IoT device [102], an attach request message via a non-IP data delivery path; and
- receiving, from the roaming network entity [104] at the NB-IoT device [102], an attach reject message for said attach request message, wherein said attach reject message comprises at least an indication of

said absence of the inter-working service capabilities exposure function support in said roaming network.
4. The method as claimed in claim 2, wherein in an event, the system
information broadcast message comprises the additional information
element, said identifying the absence of the inter-working service
capabilities exposure function support in said roaming network further
comprises:
- decoding, by the NB-IoT device [102], the system information
broadcast message to identify the absence of the inter-working
service capabilities exposure function support in said roaming
network based on said decoding.
5. The method as claimed in claim 2, wherein attaching said NB-IoT device
[102] to the roaming network via an IP-data delivery path further
comprises:
- transmitting, via the NB-IoT device [102], an attach request message via a IP data delivery path; and
- receiving, from the roaming network entity [104] at the NB-IoT device [102], an attach accept message for said attach request message via said IP data delivery path.

6. The method as claimed in claim 1 further comprising, establishing a tunnel between a serving gateway of said roaming network and a gateway of a home network of said NB-IoT device [102].
7. A Narrow-band Internet of Things (NB – IoT) device [102] comprising:

- a transceiver unit [210] configured to receive, via a roaming network entity [104], at least one system information broadcast message;
- a processing unit [204] connected to said transceiver unit [210], the processing unit [204] configured to:

identify, an absence of an inter-working service capabilities exposure function support in said roaming network; and attach, said NB-IoT device [102] to the roaming network entity [104] via an IP-data delivery path, based on identification of said absence of the inter-working service capabilities exposure function support in said roaming network, to facilitate data delivery over said roaming network.
8. The NB-IoT device as claimed in claim 7, wherein the system information broadcast message further comprises one of a Control Plane – Cellular IoT (CP-CIoT) Optimization Support indication, and an additional information element, wherein said additional information element indicates absence of the inter-working service capabilities exposure function support.
9. The NB-IoT device as claimed in claim 8, wherein in an event the system information broadcast message comprises CP-CIoT Optimization Support indication, the at least one transceiver unit [210] is further configured to:

- transmit an attach request message via a non-IP data delivery path; and
- receive, from the roaming network entity [104] an attach reject message for said attach request message, wherein said attach reject message comprises at least an indication of said absence of the inter-working service capabilities exposure function support in said roaming network.
10. The NB-IoT device [102] as claimed in claim 7, wherein the at least one
transceiver unit [210] is further configured to:
- transmit, via the NB-IoT device [102], an attach request message via a
IP data delivery path; and

- receive, from the roaming network entity [104] at the NB-IoT device
[102], an attach accept message for said attach request message via
said IP data delivery path.
11. The NB-IoT device as claimed in claim 8, wherein in an event the system
information broadcast message comprises said additional information
element, the processing unit [204] is further configured to decode the
system information broadcast message to identify the absence of the
inter-working service capabilities exposure function support in said
roaming network based on said decoding.