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 FOR IDENTIFICATION OF DIFFERENT PROTOCOLS IN CAT- NARROW BAND (NB)
LTE”
We, Reliance Jio Infocomm Limited, an Indian National of, 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad-380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

TECHNICAL FIELD
The present invention relates to the technical field of wireless communication. More particularly, the present invention relates to identification of different protocols in a CAT-Narrow Band (NB) channel.
BACKGROUND
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 (LP-WAN). 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
• Low power consumption
• Use of low-cost devices
• Provides excellent coverage.
In an NB-IoT deployment, the NB-IoT cells have a 20db gain over other categories like CAT-1 cells. As such, the NB-IoT Carrier can support much larger areas when compared to a CAT-1 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-4 operation due to the difference in the NB-IoT and other category cell coverage areas.
As huge number of IoT devices are connected, and as businesses use applications to parse IoT data, connectivity becomes a real concern for both the CAT-1 and the CAT-NB-IoT. There is a challenge to support and identify data with different protocol types over non-IP delivery data [NIDD] in NB-IoT between a user device and the network. For instance, when a device chooses to send NIDD transmission in a NB-IoT network, the ability to support different protocol types at the Service Capability Exposure Function (SCEF) of the wireless network is a major challenge.

Currently, the user device shall know the protocol type supported but there exists no mechanism to differentiate the different protocol types at the SCEF in order to route the data to different adaptors like Message Queuing Telemetry Transport (MQTT), Constrained Application Protocol (CoAP), Open Mobile Alliance- Lightweight Machine to Machine (OMA -LWM2M) etc. Thus, in the current architecture, there is a limitation for the device to implement/design different protocols like MQTT, CoAP, OMA LWM2M etc. on a single platform and route the data in the NIDD path. Also, existing solutions do not provide any mechanism for operating the different protocols for data transmission in the NIDD path. Further, the current 3GPP specification do not specify any method to overcome the above problem that support and identify data with different protocol types over NIDD between device and network of the NB- IoT.
Thus, there exists a need in the art to find a solution for a system and a method support and identify data with different protocol types over NIDD in NB-IoT between device and network and help to provide efficient way of connectivity to devices that has to be managed efficiently to handle the high traffic and provide efficient connectivity. Therefore, in view of the above shortcomings in the existing approaches, there is a need in the art to provide an efficient solution for identifying at different protocols for data transmitted by a user equipment [200] to an application server [101] over a narrow-band channel in a wireless network.
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 invention is to provide a system and method that support and identify data with different protocol types over NIDD in NB-IoT between device and network and help to provide efficient way of connectivity to devices that has to be managed efficiently to handle the high traffic and provide efficient connectivity. Another object of the present disclosure is to

provide a system and a method to address the issue of NIDD data connectivity of NB IoT devices. Yet another object of the present disclosure is to provide a system and a method to help devices in opting different protocols for data transmission in NIDD path which will overcome the restrictions imposed by service provider network. Yet another object of the present disclosure is to provide a system and a method for NB-IoT where different use cases using different protocols for data transmission to different application servers may be successfully implemented.
In order to achieve at least some of the above-mentioned objectives, the present disclosure provides a method and system for identifying at least one protocol for data transmitted by a user equipment to an application server over a narrow-band channel in a wireless network. A first aspect of the present invention relates to a method for identifying at least one protocol for data transmitted by a user equipment to an application server over a narrow-band channel in a wireless network. The method comprising establishing a connection between the user equipment and a network entity of the wireless network. Next, the user equipment identifies the data to be transmitted to the application server, wherein said data comprises a NAS payload information. Further, the user equipment attaches an application interworking header [AIH] information to the NAS payload information of the data. Furthermore, the user equipment transmits said data to the network entity. Subsequently, the network entity receives said data from the user equipment and decodes the NAS payload information of said data to identify the at least one protocol for said data. Finally, the network entity routes said data to the application server via at least one adaptor based on the identified protocol.
Another aspect of the present invention relates to a method for identifying at least one protocol for data transmitted by a user equipment to an application server over a narrow-band channel in a wireless network. The method comprising identifying, at the user equipment, the data to be transmitted to the application server, wherein said data comprises a NAS payload information. Next, the user equipment analyses the NAS payload information of said data to identify at least one protocol. Further, the user equipment transmits a PDN connection request to at least one network entity of

the wireless network based on the identified at least one protocol, wherein the at least one network entity comprises an adaptor corresponding to the identified protocol, and wherein the at least one network entity is associated with a unique APN configuration. Next, a connection is established between the user equipment and the at least one network entity. Finally, the at least one network entity routes said data to the application server.
Yet another aspect of the present invention relates to a system for identifying at least one protocol for data transmitted by a user equipment to an application server over a narrow-band channel in a wireless network. The system comprises of an application server, a user equipment and a network entity. The application server is configured to receive the data transmitted by the user equipment. The user equipment is configured to identify the data to be transmitted to the application server, wherein said data comprise NAS payload information. The user equipment is further configured to attach an application interworking header [AIH] information to the NAS payload information of the data. The user equipment is further configured to transmit said data to the network entity. The network entity is connected to the application server via at least one adaptor, said network entity configured to receive said data from the user equipment. The network entity is further configured to decode the NAS payload information of said data to identify the at least one protocol for said data. The network entity is further configured to route said data to the application server via the at least one adaptor based on the identified protocol for said data.
Yet another aspect of the present invention relates to a system for identifying at least one protocol for data transmitted by a user equipment to an application server over a narrow-band channel in a wireless network. The system comprises of an application server, a user equipment and at least one network entity. The application server is configured to receive the data transmitted by the user equipment. The user equipment is configured to identify the data to be transmitted to the application server, wherein said data comprise NAS payload information. The user equipment is further configured to analyse the NAS payload information of said data to identify at least one protocol. The user equipment is further configured to transmit a PDN

connection request to at least one network entity of the wireless network based on the identified at least one protocol. The at least one network entity is connected to the application server, said at least one network entity further comprising at least one adaptor and a unique APN configuration, the at least one network entity configured to receive said data from the user equipment. The at least one network entity is also configured to route said data to the application server.
Yet another aspect of the present disclosure relates to a user equipment connected to a wireless network. The user equipment comprises an application module, a memory unit and a processor. The processor is connected to the memory unit, the application module and the transceiver. The processor is configured to identify a data to be transmitted to the network entity [300], wherein said data comprise NAS payload information. The application module is connected to the memory unit, and the processor. The application module is configured to analyse the NAS payload information of said data to identify at least one protocol. The application module is also configured to transmit a PDN connection request to at least one network entity of the wireless network based on the identified at least one protocol, wherein the at least one network entity comprise an adaptor corresponding to the identified protocol, and the at least one network entity has a unique APN configuration.
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 invention. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the invention. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.

Fig. 1 illustrates an exemplary block diagram of a system [100] for identifying at least one protocol for data transmitted by a user equipment to an application server over a narrow-band channel in a wireless network, in accordance with exemplary embodiments of the present disclosure.
Fig. 2 illustrates an exemplary block diagram of a system [100B] for identifying at least one protocol for data transmitted by a user equipment to an application server over a narrow-band channel in a wireless network, in accordance with exemplary embodiments of the present disclosure.
Fig. 3 illustrates an exemplary block diagram of a user equipment [200], in accordance with exemplary embodiments of the present disclosure.
Fig. 4 illustrates an exemplary method flow diagram depicting method [400] for identifying at least one protocol for data transmitted by a user equipment to an application server over a narrow-band channel in a wireless network, in accordance with exemplary embodiments of the present disclosure.
Fig. 5 illustrates an exemplary method flow diagram depicting method [500] for identifying at least one protocol for data transmitted by a user equipment to an application server over a narrow-band channel in a wireless network, in accordance with exemplary embodiments of the present disclosure.
Fig. 6 illustrates an exemplary signal flow diagram [600] depicting an exemplary method for identifying at least one protocol for data transmitted by a user equipment to an application server over a narrow-band channel in a wireless network, in accordance with exemplary embodiments of the present disclosure.
Fig. 7 illustrates an exemplary signal flow diagram [700] depicting an exemplary method for identifying at least one protocol for data transmitted by a user equipment to an application server over a narrow-band channel in a wireless network, in accordance with exemplary embodiments 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 “IoT device” or "user equipment“, refers to any electrical, electronic, electromechanical and computing device. The IoT device is capable of receiving and/or transmitting one or parameters, performing function/s, communicating with other IoT devices as well as non-IoT devices and transmitting data to the devices. The IoT device may have a processor, a display, a memory unit, a battery and an input-means such as a hard keypad and/or a soft keypad. The at least one 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. 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 “processor” 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 processor is a hardware processor.
As used herein, a “controller” or “control unit” includes one or more controllers, wherein the controller refers to any logic circuitry for processing instructions. A controller may be a general-purpose controller, a special-purpose controller, a conventional controller, a digital signal controller, a plurality of microcontrollers, one or more microcontrollers in association with a DSP core, a microcontroller,

Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The controller 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 controller or control 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 unit (“ROM”), random access memory unit (“RAM”), magnetic disk storage media, optical storage media, flash memory unit 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 disclosure provides a system and a method for identifying at least one protocol for data transmitted by a user equipment to an application server over a narrow-band channel in a wireless network, in order to support and identify data with different protocol types over NIDD in NB-IoT channel between the user equipment and the wireless network. The solution of the present invention also provides an efficient way of connectivity to user equipments during high traffic.
As used herein, the "wireless network" may include, but not limited to any private or public wireless LTE network that may be presently implemented or deployed, and any wireless LTE network that may be deployed in the future. The wireless network may also be a later or newer technology of wireless LTE network, for example, LTE, LTE-A, LTE-B, LTE-C, voice over LTE etc. or any other such wireless LTE network technology obvious to a person skilled in the art. The wireless network is capable of providing one of a long-range and short-range wireless communication.

As used herein, “network entity” is an entity that serves a cellular network for providing voice services (calls) and the data services to the user equipment. The network entity 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, and any such entity obvious to a person skilled in the art.
As used herein, the “identifier” may refer to a numeric or alphanumeric string that is used for identifying the user equipment.
Referring to Fig. 1 illustrates an exemplary block diagram of a system [100] for identifying at least one protocol for data transmitted by a user equipment to an application server over a narrow-band channel in a wireless network, in accordance with exemplary embodiments of the present disclosure. The system [100] comprises a user equipment [200], connected to a network entity [300] of the wireless network, an application server [101] connected to the network entity [300] via at least one adaptor [102].
The user equipment [200] 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 user equipment [200] may be configured to receive at least one of a data or voice service from the network entity [300]. The user equipment [200] is configured to identify the data to be transmitted to the application server [101], wherein said data comprise NAS payload information. In an instance of the present invention, the data transmitted by the user equipment maybe a non-IP data.
The user equipment [200] is configured to attach an application interworking header [AIH] information to the NAS payload information of the identified data. The user equipment [200] is described in further detail below with reference to Fig. 3.
Further, in an instance of the present invention, the AIH information attached to the NAS payload information of the identified data may be presented in the following format, proposed as a first element of User Data Container Content:

AIH Header Information Element Type / Reference Presence Format Length
AIH Header Discriminator Discriminator M V 1
Header Length Length M V 1
Application Protocol Discriminator IoT protocol discriminator M V 1
Application Protocol End Point M T 1
Application PEP Length Length M V 1
Application PEP URL / IP address M V N
Device ID IMEI M V 16
The network entity [300] is connected to the application server [200] via at least one adaptor [102]. The network entity [300] further comprises a transceiver [302], a processor [306] and an interface [308]. The network entity [300] may provide network access to the one or more user equipment [200] connected to the network entity [300], and thereby, the one or more user equipment [200] may connect to the application server [200] using said wireless network. The network entity [300] is also capable of provisioning and supporting NB-IoT RAT to the user equipment [200] via one or more access points such as an IoT gateway.
The network entity [300] 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 user equipment [200]. The wireless network entity [300] 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. In an instance of the present invention, the network entity [300] may be one of a SCEF and a SCS.

The processor [306] may be configured to execute functions/operations performed by each module/component of the network entity [300]. The processor [306] 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 [306] is also configured to decode the NAS payload information of said data to identify the at least one protocol for said data. Further, the processor [306] is configured to route said data to the application server [101] via the at least one adaptor [102] based on the identified protocol for said data.
Further the transceiver [302] coupled to said processor [306] may include at least one transmission unit and at least one receiving unit and the transceiver [302] may be configured to transmit or receive the communication signals/data via the network entity [300] to user equipment [200] or vice versa. The transceiver [302] is configured to network entity [300] configured to receive said data from the user equipment [200]. In an instance of the present invention, said data may be received at the network entity [300] via a non-IP delivery data [NIDD] path
The interface [308] may be coupled to the transceiver [302] and processor [306] and the interface [308] may be configured for backhaul and to further reach out to an on-boarding server for information exchange.
The application server [101] is connected to the network entity [300] via at least one adaptor [102]. The at least one adaptor [102] is configured to receive the NAS payload information sent by the user equipment [200] via the at least network entity [300]. The at least one adaptor [102] is also configured to encode the received data in to a format consistence with the identified protocol.
In an instance of the present invention, the at least one adaptor [102] may reside outside the application server, and accordingly, the at least one adaptor [102] may be configured to send the encoded received data to the Application Server [101]. In an instance of the present invention, the application protocols are standard defined protocols. For instance, the present invention encompasses different adaptors

including, but not limited to, a Message Queuing Telemetry Transport (MQTT), a Constrained Application Protocol (CoAP), an Open Mobile Alliance- Lightweight Machine to Machine (OMA -LWM2M) etc.
For instance, in operation, the MQTT Adaptor (or CoAP Adaptor, or HTTP Adaptor, or LwM2M Adaptor) listens for the NAS payload messages sent from the user equipment [200] through SCEF and encodes the received data in a format consistence with the respective protocol and sends it to Application Server. For example, MQTT will Publish, Subscribe the data in JSON format, HTTP will POST/GET the data with header and Body.
The application server [101] is a framework that provides a server environment to run software application. The application server [101] comprises of a comprehensive service layer model. Per present invention, the applications server [101] is configured to receive the data transmitted by the user equipment [200]. For instance, such data received from the user equipment [200] may be used for running an application on the application server [101].
Although a limited number of user equipment [200], network entity [300], adaptor [102], application server [200] 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 components.
As illustrated in Fig. 2, an exemplary block diagram of a system [100B] for identifying at least one protocol for data transmitted by a user equipment to an application server over a narrow-band channel in a wireless network, in accordance with another exemplary embodiments of the present disclosure. The system [100B] comprises a user equipment [200], connected to at least one network entity [300] of the wireless network, and an application server [101] connected to the network entity [300].
The user equipment [200] is configured to identify the data to be transmitted to the application server [101], wherein said data comprise NAS payload information. In an instance of the present invention, the data transmitted by the user equipment maybe a non-IP data. The user equipment [200] is also configured to analyse the NAS payload

information of said data to identify at least one protocol. Further, the user equipment [200] is configured to transmit a PDN connection request to at least one network entity [300] of the wireless network based on the identified at least one protocol. The user equipment [200] is described in further detail below with reference to Fig. 3.
The at least one network entity [300] is connected to the application server [200]. The network entity [300] comprises at least one adaptor [102], a transceiver [302], a processor [306] and an interface [308]. The at least one adaptor [102] may be configured to receive the NAS payload information sent by the user equipment [200] via the at least network entity [300]. The at least one adaptor [102] is also configured to encode the received data in to a format consistence with the identified protocol. For instance, the present invention encompasses different adaptors including, but not limited to, a Message Queuing Telemetry Transport (MQTT), a Constrained Application Protocol (CoAP), an Open Mobile Alliance- Lightweight Machine to Machine (OMA -LWM2M) etc.
Further the transceiver [302] coupled to said processor [306] may include at least one transmission unit and at least one receiving unit and the transceiver [302] may be configured to transmit or receive the communication signals/data via the network entity [300] to user equipment [200] or vice versa. The transceiver [302] is configured to network entity [300] configured to receive said data from the user equipment [200]. In an instance of the present invention, said data may be received at the network entity [300] via a non-IP delivery data [NIDD] path.
The processor [306] may be configured to execute functions/operations performed by each module/component of the network entity [300]. The processor [306] 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 processor [306] is configured to route said data to the application server [101].
As illustrated in Fig. 3, an exemplary block diagram of a user equipment [200], in accordance with exemplary embodiments of the present disclosure. The user

equipment [200] comprises at least one application module [202], at least one memory unit [206] and at least one processor [208]. The user equipment [200] may further comprise of at least one transceiver [204], at least one antenna [212] and at least one on-boarding client module [210]. All the above said components of the user equipment [200] are connected to each other.
The processor [208] of the user equipment [200] is coupled to the transceiver [204], the application module [202], the on-boarding client module [210] and the memory unit [206]. The processor [208] is configured to identify data to be transmitted to the application server [101] via the network entity [300], wherein said data comprises NAS payload information.
The application module [202] is coupled to said antenna [212], the transceiver [204], the memory unit [206], the on-boarding client module [210] and the processor [208]. The application module [202] is configured to analyse the NAS payload information of said data to identify at least one protocol. The application module [202] is configured to transmit a PDN connection request to at least one network entity [300] of the wireless network based on the identified at least one protocol, wherein the at least one network entity [300] comprise an adaptor [102] corresponding to the identified protocol, and wherein the at least one network entity [300] has a unique APN configuration.
The transceiver [204] of the user equipment [200] is coupled to said antenna [212], the memory unit [206], the application module [202], the on-boarding client module [210] and the processor [208]. The transceiver [204] is to be configured to transmit the PDN connection request to at least one network entity [300].
The on-boarding client module [210] is coupled to said antenna [212], the transceiver [204], the application module [202], the processor [208] and the memory unit [206]. The on-boarding client module [210] may be configured to communicate to an on-boarding server via the transceiver [204] while being in charge of the device-specific on-boarding function.

The memory unit [206] is coupled to transceiver [204], the application module [202], the on-boarding client module [210] and the processor [208]. The memory unit [206] is configured to store the data identified to be transmitted to the application server [101].
Fig. 4 illustrates an exemplary method flow diagram depicting method [400] for identifying at least one protocol for data transmitted by a user equipment to an application server over a narrow-band channel in a wireless network, in accordance with exemplary embodiments of the present disclosure. The user equipment [200] may currently be connected to the network entity [300] over the NB-IoT channel.
The method begins at step [402]. The method begins with the user equipment [200] establishing a connection between the user equipment [200] and a network entity [300] of the wireless network. At step [404], the user equipment [200] identifies the data to be transmitted to the application server [101], wherein said data comprises a NAS payload information. At step [406], the user equipment [200] attaches an application interworking header [AIH] information to the NAS payload information of the data. At step [408], the user equipment [200] transmits said data to the network entity [300].
At step [410], the network entity [300] receives said data from the user equipment [200]. At step [412], the network entity [300] decodes the NAS payload information of said data to identify the at least one protocol for said data. Thereafter, at step [414], the network entity [300] routes said data to the application server [101] via at least one adaptor [102] based on the identified protocol.
Fig. 5 illustrates an exemplary method flow diagram depicting method [500] for identifying at least one protocol for data transmitted by a user equipment to an application server over a narrow-band channel in a wireless network, in accordance with exemplary embodiments of the present disclosure.
The method begins at step [501]. At step [502], the user equipment [200] identifies the data to be transmitted to the application server [101], wherein said data comprises a NAS payload information. At step [504], the user equipment [200]

analyses the NAS payload information of said data to identify at least one protocol. At step [506], the user equipment [200] transmits a PDN connection request to at least one network entity [300] of the wireless network based on the identified at least one protocol, wherein the at least one network entity [300] comprises an adaptor [102] corresponding to the identified protocol, and the at least one network entity [300] is associated with a unique APN configuration. At step [508], a connection is established between the user equipment [200] and the at least one network entity [300]. At step [510], the at least one network entity [300] routes said data to the application server [101].
Referring to Fig. 6 illustrates an exemplary signal flow diagram [600] depicting an exemplary method for identifying at least one protocol for data transmitted by a user equipment to an application server over a narrow-band channel in a wireless network, in accordance with exemplary embodiments of the present disclosure. The user equipment adds AIH information to the NAS PDU data, and the network entity [300] decodes the AIH information to determine the protocol. Thus, identification of the protocol occurs at the network entity [300].
Fig. 7 illustrates an exemplary signal flow diagram [700] depicting an exemplary method for identifying at least one protocol for data transmitted by a user equipment to an application server over a narrow-band channel in a wireless network, in accordance with exemplary embodiments of the present disclosure. The user equipment may trigger NIDD attach or PDN connection request to SCEF which are separated through different APN configuration. Thus, identification of the protocol occurs at the user equipment [200].
Therefore, as is evident from the above disclosure, the present invention provides system and method for identifying at least one protocol for data transmitted by a user equipment [200] to an application server [101] over a narrow-band channel in a wireless network. Thus, the present invention provides technical advancement of identifying data with different protocol types over NIDD in NB-IoT between device and network and help to provide efficient way of connectivity to devices that has to be managed efficiently to handle the high traffic and provide efficient connectivity.

Also, the solution of the present invention addresses the issue of NIDD data connectivity of NB IoT devices, by assisting devices in opting different protocols for data transmission in NIDD path which will overcome the restrictions imposed by service provider network.
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 the system [100] are exemplary, and any components/module/interface in the system [100] 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 component 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 for identifying at least one protocol for data transmitted by a user
equipment [200] to an application server [101] over a narrow-band channel in a
wireless network, the method comprising:
- establishing a connection between the user equipment [200] and a network entity [300] of the wireless network;
- identifying, at the user equipment [200], the data to be transmitted to the application server [101], wherein said data comprises a NAS payload information;
- attaching, at the user equipment [200], an application interworking header [AIH] information to the NAS payload information of the data;
- transmitting, by the user equipment [200], said data to the network entity [300];
- receiving, at the network entity [300], said data from the user equipment [200];
- decoding, at the network entity [300], the NAS payload information of said data to identify the at least one protocol for said data; and
- routing, by the network entity [300], said data to the application server [101] via at least one adaptor [102] based on the identified protocol.

2. The method as claimed in claim 1, wherein the data transmitted by the user equipment is a Non-IP data.
3. The method as claimed in claim 1, wherein the network entity [300] is at least one of a SCEF and a SCS.
4. The method as claimed in claim 1, wherein said data is received at the network entity [300] via a non-IP delivery data [NIDD] path.
5. The method as claimed in claim 1, wherein the at least one protocol is one of a MQTT protocol, a CoAP protocol and a LwM2M protocol.

6. The method as claimed in claim 5, further comprising configuring a custom adaptor [102] for the at least one protocol in an event the network entity [300] fails to identify the at least one protocol based on the NAS payload information.
7. A method for identifying at least one protocol for data transmitted by a user equipment [200] to an application server [101] over a narrow-band channel in a wireless network, the method comprising:

- identifying, at the user equipment [200], the data to be transmitted to the application server [101], wherein said data comprises a NAS payload information;
- analysing, at the user equipment [200], the NAS payload information of said data to identify at least one protocol;
- transmitting, by the user equipment [200], a PDN connection request to at least one network entity [300] of the wireless network based on the identified at least one protocol, wherein

- the at least one network entity [300] comprises at least one adaptor [102] corresponding to the identified protocol, and
- the at least one network entity [300] is associated with a unique APN configuration;

- establishing a connection between the user equipment [200] and the at least one network entity [300];
- routing, by the at least network entity [300], said data to the application server [100].
8. A system for identifying at least one protocol for data transmitted by a user
equipment [200] to an application server [101] over a narrow-band channel in a
wireless network, the system comprising:
- an application server [101] configured to receive the data transmitted by the user equipment [200];
- a user equipment [200] configured to:

- identify the data to be transmitted to the application server [101], wherein said data comprise NAS payload information;
- attach an application interworking header [AIH] information to the NAS payload information of the data;
- transmit said data to the network entity [300];
- a network entity [300] connected to the application server [200] via at
least one adaptor [102], said network entity [300] configured to:
- receive said data from the user equipment [200];
- decode the NAS payload information of said data to identify the at least one protocol for said data;
- route said data to the application server [101] via the at least one adaptor [102] based on the identified protocol for said data.
9. A system for identifying at least one protocol for data transmitted by a user equipment [200] to an application server [101] over a narrow-band channel in a wireless network, the system comprising:
- an application server [101] configured to receive the data transmitted by the user equipment [200];
- a user equipment [200] configured to:

- identify the data to be transmitted to the application server [101], wherein said data comprise a NAS payload information,
- analyse the NAS payload information of said data to identify at least one protocol, and
- transmit a PDN connection request to at least one network entity [300] of the wireless network based on the identified at least one protocol;
- at least one network entity [300] connected to the application server
[200], said at least one network entity [300] further comprising at least

one adaptor [102] and a unique APN configuration, the at least one network entity [300] configured to:
- receive said data from the user equipment [200], and
- route said data to the application server [101].
10. A user equipment [200] connected to a wireless network, said user equipment [200] comprising:
- a memory unit [206];
- a processor [208] connected to the memory unit [206], said processor [208] configured to identify a data to be transmitted to the network entity [300], wherein said data comprise NAS payload information, and
- an application module [202] connected to the memory unit [206] and the processor [208], said application module [202] configured to:

- analyse the NAS payload information of said data to identify at least one protocol;
- transmit a PDN connection request to at least one network entity [300] of the wireless network based on the identified at least one protocol, wherein

- the at least one network entity [300] comprise an adaptor [102] corresponding to the identified protocol, and
- the at least one network entity [300] has a unique APN configuration.