TECHNICAL FIELD
The present subject matter is related, in general to data communication and more particularly, but not exclusively to a method and system for enabling data communication in field service management system.
BACKGROUND
Field work for example, in utilities generally includes periodic activities like inspections, disconnections/reconnections, consumer/asset surveying, maintenance apart from incidental activities like repairs, verifications/validation, outage management, customer complaints resolution, etc. Utilities are managing the field activities and meeting their business goals using web or mobile application or a combination of both. Irrespective of the technology used, a field person has to visit the field and perform the task whether it is maintenance or regular task. Most of the utilities, use traditional means, expect their field staff to take instructions over phone or text message, execute the job, note down the information and then enter the information in to a software application after reaching the office. In utilities that implemented mobile workforce management systems, a field technician has a mobile application, to receive instructions through the application and update job status information on the field itself for immediate feedback to customers. But in both the cases if the field technician requires any visual guidance to perform a certain task, it is not possible.
Further, the field staff are expected to service or repair the latest field equipment with high tech gadgets. It is difficult for ageing field person to acquire these new skills quickly and at the same time for young people who are conversant with gadgetry don't have enough practical experience on the field. For most service visits there is a need for supplementary information and communication about the work as the field service professional's onsite visit progresses; such as availability of parts, helpers, additional assets, or documentation about the problem or an asset. Some of the organizations rely on phone calls, which is in sufficient and requires stoppage of work.
Laptops and tablets offer powerful computing and connectivity on the go but share a common drawback that when they are used in the field they must be held with one or two hands. Use of Internet of Things (IOT) and Augmented reality (AR) in field service is the current trend that offers effective service and efficient data record. Data communication between various IOT devices or

utilities and dynamic connection establishment for data recording is the current challenge in field service management.
SUMMARY
One or more shortcomings of the prior art are overcome and additional advantages are provided through the present disclosure. Additional features and advantages are realized through the techniques of the present disclosure. Other embodiments and aspects of the disclosure are described in detail herein and are considered a part of the claimed disclosure.
Embodiments of the present disclosure relates to a method of enabling data communication for field service management. The method comprises receiving a synchronization signal from at least one IOT device and a user device at a current location. The method further comprises identifying the at least one IOT device capable of establishing connection with the IOT gateway based on one or more parameters associated with the synchronization signal. The method also comprises dynamically creating at least one mesh network comprising the at least one IOT device identified based on the one or more parameters. The method further comprises receiving a sensor data from the at least one IOT device of the at least one mesh network.
Further, the present disclosure relates to a system for enabling data communication for field service management. The system comprises at least one IOT device installed in a location and an IOT gateway. The system further comprises a user device communicatively coupled with the IOT gateway using a first communication protocol. The IOT gateway comprises a processor configured to receive a synchronization signal from the at least one IOT device and the user device, at the current location. The processor is further configured to identify the at least one IOT device capable of establishing connection with the IOT gateway based on one or more parameters associated with the synchronization signal. The processor is also configured to dynamically create at least one mesh network comprising the at least one IOT device identified based on the one or more parameters. Further, the processor is configured to receive a sensor data as input from the at least one IOT devices of the at least one mesh network.
The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects,

embodiments, and features will become apparent by reference to the drawings and the following detailed description.
BRIEF DECSRIPTION OF DRAWINGS
The embodiments of the disclosure itself, as well as a preferred mode of use, further objectives and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings. One or more embodiments are now described, by way of example only, with reference to the accompanying drawings in which:
Figure 1 illustrates an exemplary architecture of a system for enabling data communication in field service management in accordance with some embodiment of the present disclosure;
Figure 2a illustrates an exemplary block diagram of IOT gateway of Figure 1 in accordance with an embodiment of the present disclosure;
Figure 2b illustrates an exemplary block diagram of memory of IOT gateway of Figure 2a in
accordance with an embodiment of the present disclosure;
Figure 2c illustrates an exemplary block diagram of field service manager of Figure 1 in
accordance with an embodiment of the present disclosure;
Figure 3a illustrates an exemplary flowchart showing a method for enabling data communication performed by the IOT gateway in accordance with some embodiments of the present disclosure;
Figure 3b illustrates an exemplary flowchart showing a method for enabling data communication performed by the user device in accordance with some embodiments of the present disclosure; and
Figure 4 is a block diagram of an exemplary computer system for implementing embodiments consistent with the present disclosure.
The figures depict embodiments of the disclosure for purposes of illustration only. One skilled in the art will readily recognize from the following description that alternative embodiments of the

structures and methods illustrated herein may be employed without departing from the principles of the disclosure described herein.
DETAILED DESCRIPTION
In the present document, the word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.
While the disclosure is susceptible to various modifications and alternative forms, specific embodiment thereof has been shown by way of example in the drawings and will be described in detail below. It should be understood, however that it is not intended to limit the disclosure to the specific forms disclosed, but on the contrary, the disclosure is to cover all modifications, equivalents, and alternative falling within the scope of the disclosure.
The terms "comprises", "comprising", "includes", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, device, or method that comprises a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or device or method. In other words, one or more elements in a system or apparatus proceeded by "comprises... a" does not, without more constraints, preclude the existence of other elements or additional elements in the system or method.
The present disclosure relates to a method and system for enabling data communication in field service management. The system comprises a portable IOT gateway capable of connecting with at least one IOT device installed in a location of a user. The IOT gateway receives synchronization signals from the at least IOT device and identifies the capability or availability of IOT devices to connect with the IOT gateway based on one or more parameters associated with the synchronization signal. Upon identifying the IOT devices available for connection establishment, the IOT gateway dynamically creates a mesh network with the identified IOT devices. In one embodiment, the IOT gateway creates the mesh network with the at least one identified IOT devices as mesh nodes and the IOT gateway as a gateway node by assigning a mesh ID for the mesh network. The IOT devices in the mesh network is now capable of transmitting all sensor data

to the gateway node of the mesh network using a secure mesh protocol. The IOT gateway receives the sensor data from the mesh nodes and transmits to the user device. The user device is configured to detect abnormalities of the IOT devices based on the sensor data and enables connection to an expert system for dynamically resolving the abnormalities by seeking virtual assistance using an Augmented Reality (AR) device connected with the user device.
Figure 1 illustrates an exemplary architecture of a system for enabling data communication in field service management in accordance with some embodiment of the present disclosure.
As shown in Figure 1, the exemplary system 100 comprises one or more components configured for enabling data communication in field service management. In one embodiment, the exemplary system 100 comprises an Internet of Things (IOT) gateway 104 connected to at least one IOT devices 106-1,2...N (collectively referred to as IOT devices 106), an augmented reality (AR) device 107, field service manager (FSM) 108, user 109, a user device 110 and a data repository (interchangeably referred to as repository) 111 connected via a communication network 112.
The communication network 112 may include, without limitation, a direct interconnection, LAN (local area network), WAN (wide area network), wireless network, point-to-point network, or another configuration. One of the most common types of network in current use is a TCP/IP (Transfer Control Protocol and Internet Protocol) network for communication between database client and database server. Other common Internet protocols used for such communication include HTTPS, FTP, AFS, and WAP and using secure communication protocols etc.
In some examples, the AR device 107 may be any wearable device that is capable of enabling augmented reality technique. In one embodiment, the AR device 107 may be a wearable frame like ordinary eyeglasses and comprises a positioning device that determines a physical location and field of view of the user 109 of the wearable frame. The user 109 may be any person visiting the field with the AR device 107, user device 110 and the IOT gateway 104. In one example, the positioning device may include both a geographic locator (e.g., a global positioning system (GPS) device that utilizes signals from GPS satellites to determine the current position of the user or wearer as well as orientation devices (e.g., accelerometers, 3-axis gravity detectors, etc.) that determine the direction that the user/wearer is looking ("field of view") while wearing the AR device 107. The AR device 107 may receive data of the IOT devices 106 via the user device 110

and may provide with a display of images or the sensor data onto the lens of the wearable device. The sensor data may be data associated with the IOT devices 106. For example, if the IOT device 106 is an energy meter, then the sensor data include meter operations related data, field inspection related data, maintenance data, and information like manuals, instructions, operational steps etc. In one embodiment, the AR device 107 may be a standalone device coupled with the user device
110 and IOT gateway 104. In another embodiment, the AR device 107 may be integrated within
the user device 110.
The user devices 110 may be a mobile device or a computing device including the functionality for communicating over the network. For example, the mobile device can be a conventional web-enabled personal computer in the home, mobile computer (laptop, notebook or subnotebook), Smart Phone (iOS, Android), personal digital assistant, wireless electronic mail device, tablet computer or other device capable of communicating both ways over the Internet or other appropriate communications network. The user device 110 may comprise an integrated software application that enables real time interaction with the AR device 107 and the IOT gateway 104. The user device 110 and the AR device 107 are communicatively coupled with the FSM 108 via the network 112. In one example, the user device 110 may be communicatively coupled with the IOT gateway 104 using a first communication protocol for example, Bluetooth and WIFI protocol. In another example, the user device 110 may be communicatively coupled with the AR device 107 using a second communication protocol for example, WIFI protocol.
The repository 111 may store a list of the IOT devices 106 registered to avail the services of the FSM 108 along with corresponding IOT deviceldentification (ID). The IOT devicelD, in one example, may be a unique identification code used to identify the IOT devices 106. The repository
111 may also store the sensor data received from the user device 110. Further, the repository 111
stores predefined data constraints or validation rules for verifying the validity of the sensor data
related to the IOT devices 106 using the predefined data constraints. In one embodiment, the
repository 111 may be integrated within the FSM 108. In another embodiment, the repository 104
may be a standalone repository communicatively coupled with the FSM 108, the user device 110
and the IOT gateway 104.
The IOT gateway 104 may be a device capable of creating a dynamic mesh network by connecting with the IOT devices 106 available within the proximity of the IOT gateway 104. In one example,

the IOT gateway 104 may be an IOT concentrator device. The IOT gateway 104 may be a portable hand-held device capable of being carried manually to field location and capable of dynamically connecting to the IOT devices 106 for effective data recording in field service. In one embodiment, the IOT devices 106 may comprise one or more sensors to record sensor data in real time. Figure 2a illustrates the block diagram of an exemplary IOT gateway 104. As shown in Figure 2a, the IOT gateway 104 comprises a processor 202 to perform certain tasks for enhancing data communication in filed service management. The processor 202 may be coupled with a memory 206. Further, IOT gateway 104 is configured with various communication protocols including WIFI 205, Bluetooth 207 and Radio Frequency (RF) 208. The block diagram of memory 206 of the IOT gateway 104 is illustrated in Figure 2b. The memory 206 comprises a synchronization signal 212, an IOT device identification (ID) 213, a gateway ID 214, a mesh ID 215 and other data 216
The IOT gateway 104 may also include one or more components comprising a synchronization unit 115, a mesh generating unit 117 and a data validation unit 209. The synchronization unit 115 is configured to receive the synchronization signal 212 from the IOT devices 106 and identify the at least one IOT device 106 capable of establishing connection with the IOT gateway 104 based on one or more parameters associated with the synchronization signal 212. The mesh generation unit 117 is configured to generate a dynamic mesh network comprising the IOT gateway 104 and the IOT devices 106 identified by the synchronization unit 115. The data validation unit 209 is configured to validate the sensor data by comparing the received sensor data with the predefined data constraints of the sensor data.
The FSM 108 is capable of enabling field service management, by monitoring the field services of the user 109 using the AR device 107 and the IOT gateway 104. In one example, the FSM 108 may include a desktop personal computer, workstation, laptop, PDA, cell phone, or any WAP-enabled device or any other computing device capable of interfacing directly or indirectly to the Internet or other network connection. The FSM 108 typically includes one or more user interface devices, such as a keyboard, a mouse, touch screen, pen or the like, for interacting with the GUI provided on a display. The FSM 108 also includes a graphical user interface (GUI) provided therein for interacting with the repository 111 to access required data and to enable field service management and related processes. In one example, the FSM 108 may be configured as a standalone system. In another example, the FSM 108 may be configured in cloud environment.

The FSM 108 comprises an anomaly detector 119 configured to detect anomaly in the sensor data received from the IOT devices 106.
In an embodiment, the FSM 108 may be a typical FSM as illustrated in Figure 2. The FSM 108 comprises a processor 220, a memory 221, and an I/O interface 222. The memory 221 stores data and stores processor-readable instructions for performing the operations of the processor 220. The FSM 108 further includes data 224 and one or more components including the anomaly detector 119 and an expert assistant 225 and a report generation unit 226. In one implementation, the data 224 may be stored within the memory 221. In one example, the data 224 may include sensor data 228, anomaly data 229, task completion reports 230 and other data 232. In some embodiments, the data 224 may be stored within the memory 221 in the form of various data structures. Additionally, the data 224 may be organized using data models, such as relational or hierarchical data models. The other data 232 may store data, including temporary data and temporary files, generated by the components for performing the various functions of the FSM 108.
In operation, the system 100 enables field service management using the IOT gateway 104. In a field service management, the user 109 visits the field location for asset monitoring using the portable IOT gateway 104 hand-held by the user 109. The IOT gateway 104 dynamically creates a mesh network of the IOT devices 106 available within the proximity of the IOT gateway 104 to communicate with the IOT devices 106 for asset monitoring. The IOT devices 106 may be the assets installed in the field location that needs field service and monitoring. In one embodiment, the IOT gateway 104 identifies the IOT devices 106 by broadcasting a signal indicating presence of the IOT gateway 104 in the field location. The IOT devices 106 may verify the IOT gateway 104 by using the gateway ID 214 received in the broadcasted signal. In response, the IOT devices 106 located within the proximity of the IOT gateway 104 sends the synchronization signal 212 to the IOT gateway 104 to indicate availability of the IOT devices 106 in the current location. In one embodiment, the synchronization unit 115 of the IOT gateway receives the synchronization signal 212 from the at least one IOT device 106 and identifies the IOT devices 106 capable of establishing connection with the IOT gateway 104 based on one or more parameters associated with the synchronization signal 212. For example, the one or more parameters may include signal strength, signal quality, signal to noise ratio (SNR), coverage area and other signal parameters. The synchronization unit 115, in one aspect, determines the capability or availability of the IOT devices 106 to connect with the IOT gateway 104. Upon identifying the available IOT devices 106, the

mesh generating unit 117 dynamically creates at least one mesh network comprising the identified IOT devices 106 as mesh nodes.
In one embodiment, the mesh generating unit 117 identifies the IOT device 106 proximal to the IOT gateway 104 and determines the IOT device_ ID 213 associated with the identified IOT devices 106. The mesh generating unit 117 further verifies the IOT devicelD 213 of the identified IOT devices 106 by comparing with the plurality of registered IOT devicelDs stored in the data repository 111. Upon successful verification, the mesh generating unit 117 creates the at least one mesh network comprising the IOT devices 106 as mesh node that can communicate with the IOT gateway 104 (alternatively gateway node) using an appropriate mesh protocol. Further, the mesh generation unit 117 assigns the mesh ID 215 for each generated mesh network. In one example, the mesh network comprises the at least one IOT devices 106 having verified IOT devicelD 213 as mesh node and the IOT gateway 104 as a gateway node. Upon generating the mesh network, the IOT gateway 104 communicates with the mesh nodes to receive data for field service and asset monitoring.
In one embodiment, the IOT gateway 104 in the mesh network having the mesh ID 215 sends request to the mesh nodes or the IOT devices 106 to transmit the sensor data 228 using the mesh protocol. In response, the mesh nodes or the IOT devices 106 transmit the sensor data 228 to the IOT gateway 104 in the mesh network having the mesh ID 215. The data validation unit 209 of the IOT gateway 104 receives the sensor data 228 from the at least one IOT device 106 of the mesh network and verifies the sensor data 228 using predefined validation rules or data constraints. In one example, the data validation unit 209 verifies the sensor data 228 by comparing the received sensor data 228 with the predefined data constraints of the sensor data. Upon successful verification, the data validation unit 209 transmits the validated sensor data 228 outside the mesh network for example, to the user device 110 using the first communication protocol. The user device 110 connects to the AR device 107 using the second communication protocol including Bluetooth and WIFI protocol and displays the received validated sensor data 228 on the display of the AR device 107. The user device 110 may further transmit the validated sensor data 228 to the repository 111 for storing and further processing.
The user device 110 may also transmit the validated sensor data 228 to the FSM 108. In real time monitoring of the assets in the field location, the FSM 108 may process the validated sensor data

228 to detect any abnormal functioning of the IOT devices 106 in the field location. In one aspect, the FSM 108 detects the presence of abnormalities of the at least one IOT device 106 based on the validated sensor data 228. The anomaly detector 119 of the FSM 108 receives the validated sensor data 228 from the user device 110 and detects the anomaly data 229 from the validated sensor data 228 using the standard functional data stored in the repository 111. In one embodiment, the anomaly detector 119 may also detect the anomaly data 229 of the IOT gateway 104 using the user device 110. In one example, the user device 110 obtains data such as health data of the IOT gateway 104 by scanning a QR code of the IOT gateway 104, and subsequently determines the anomaly data 229 of the IOT gateway 104. Upon detecting the anomaly data 229, the FSM 108 enable the expert assistant 225 to connect the user with an expert team located remotely.
In one embodiment, the expert assistant 225 may be an expert engine capable of mapping the anomaly data 229 to determine appropriate expert team and connect the expert team with the user in the field location. In one aspect, expert assistant 225 connects the user device 110 to user device of the expert team to enable dynamic visual assistance using AR device. The expert assistant 225 provides real time visual assistance to the user 109 from experts by enabling the real time view of the current situation to an in-house expert using video streaming operations and applications available. The expert assistant 225 also transmits the responses received from the expert onto the AR device 107 to accomplish the task in response to queries inputted by the user 109 based on the anomaly data 229. Upon completion of the task, the FSM 108 generates the reports for further processing.
In one embodiment, the report generation unit 226 generates field analysis reports 230 based on the task execution. The field analysis reports 230 may comprise the operational steps performed by the user and the health data of the assets or the IOT devices 106. The IOT gateway 104 and FSM 108 together thus enables data communication in field service by dynamically creating a mesh network with an improved communication protocol.
Figure 3a illustrates an exemplary flowchart showing a method for enabling data communication performed by the IOT gateway in accordance with some embodiments of the present disclosure;

As illustrated in Figure 3a, the method 300 comprises one or more blocks for enabling data communication in field service performed by the processor 202 of IOT gateway 104. The method 300 may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform particular functions or implement particular abstract data types.
The order in which the method 300 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method 300. Additionally, individual blocks may be deleted from the method 300 without departing from the spirit and scope of the subject matter described herein. Furthermore, the method 300 can be implemented in any suitable hardware, software, firmware, or combination thereof.
At block 302, the synchronization signal 212 from IOT devices 106 is received. In one embodiment, the synchronization unit 115 of the IOT gateway 104 receives the synchronization signal 212 from the at least one IOT device 106. In one example, the user 109 visits the field location for asset monitoring along with the IOT gateway 104. The one or more assets or IOT devices 106 installed in the field location sends the synchronization signal 212 to the IOT gateway 104 to indicate presence of the IOT devices 106 in the current location.
At block 304, the at least one available IOT device 106 is identified to establish connection with the IOT gateway 104. In one embodiment, the synchronization unit 115 identifies the at least one IOT device 106 capable of establishing connection with the IOT gateway 104 based on one or more parameters associated with the synchronization signal 212. In one example, the one or more parameters may include signal strength, maximum coverage area and other related signal parameters. The synchronization unit 115, in one aspect, determines the availability of the IOT devices 106 to connect with the IOT gateway 104. Based on identified IOT devices 106, the mesh network is dynamically created at block 306.
At block 306, the mesh network is created dynamically with the available IOT devices 106. In one embodiment, the mesh generating unit 117 determines the nearest at least one IOT device 106 to the IOT gateway 104 and the IOT device_ ID 213 associated with the nearest at least one IOT device 106. The mesh generating unit 117 further verifies the IOT devicelD 213 of the identified

IOT devices 106 with the plurality of predefined IOT devicelD stored in the data repository 111. Upon verification, the mesh generating unit 117 creates the at least one mesh network with the at least one IOT device 106 using an appropriate mesh protocol. In one aspect, the mesh generating unit 117 assigns the mesh ID 215 for each generated mesh network. In one example, the mesh network comprises the at least one IOT device 106 having verified IOT devicelD 213 as a mesh node and the IOT gateway 104 as a gateway node.
At block 308, the sensor data 228 is received from the mesh network. In one embodiment, the data validation unit 209 of IOT gateway 104 receives the sensor data 228 from the at least one IOT device 106 of the mesh network. The at least one IOT device 106 of the mesh network with the mesh ID 215 captures the sensor data 228 from the one or more sensors and transmits the sensor data 228 to the IOT gateway 104 of the mesh network of the same mesh ID 215. In one example, the sensor data 228 may comprise meter readings of the asset, energy utilization data, current payment status and other related data of the assets or IOT devices 106. The data validation unit 209 validates the sensor data 228 by comparing the received sensor data 228 with the predefined data constraints of the sensor data 228. Upon validation, the data validation unit 209 transmits the validated sensor data 228 from the IOT gateway 104 to the user device 110 using the first communication protocol.
Figure 3b illustrates an exemplary flowchart showing a method for enabling data communication performed by the user device in accordance with some embodiments of the present disclosure.
As illustrated in Figure 3b, the method 320 comprises one or more blocks for enabling data communication using the user device 104 coupled with the Field service manager (FSM) 108. The method 320 may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform particular functions or implement particular abstract data types.
The order in which the method 320 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method 320. Additionally, individual blocks may be deleted from the method 300 without departing from

the spirit and scope of the subject matter described herein. Furthermore, the method 320 can be implemented in any suitable hardware, software, firmware, or combination thereof.
At block 322, the sensor data 228 from IOT gateway 104 is received. In one embodiment, the user data receives the validated sensor data from the IOT gateway 104 and connects to the AR device 107 and displays the received validated sensor data 228 on the visual screen using the AR device 107. The user device 110 may further transmit the validated sensor data 228 to the repository 111 upon the user instructions.
AT block 324, the anomaly of IOT devices 106 is detected based on the sensor data 228. In one embodiment, the user device 110 transmits the validated sensor data 228 to the FSM 108. In one aspect, the FSM 108 detects the presence of anomalies in the at least one IOT device 106 based on the validated sensor data 228. The anomaly detector 119 receives the validated sensor data 228 from the user device 110 and detects the anomaly data 229 from the validated sensor data using the standard functional data stored in the repository 111. In one embodiment, the anomaly detector 119 may also detect the anomaly data 229 of the IOT gateway 104 using the user device 110. In one example, the user device 110 determines the data related to the IOT gateway 104 by scanning a QR code of the IOT gateway 104, and subsequently determines the abnormality of the IOT gateway 104.
At block 326, the anomaly data 229 is processed to seek the virtual expert assistance. In one embodiment, the expert assistant 225 of the FSM 108 may connect the user 109 to the expert team to enable dynamic visual assistance using the AR device 107. The expert assistant 225 provides real time assistance to user 109 from expert team by enabling the real time view of the current situation to an in-house expert using video streaming operations and applications available. The expert assistant 225 also transmits the responses received from the expert onto the AR device 107 to accomplish the task in response to queries inputted by the user 109.
At block 328, the task completion reports 230 are generated. In one embodiment, the report generation unit 226 generates the task completion reports 230 based on the task execution. The task completion reports 230 may comprise the operational steps performed by the user and the health data of the assets or the IOT devices 106.

The IOT gateway 104 and FSM 108 together thus enables data communication in field service by dynamically creating a mesh network with an improved communication protocol.
Figure 4 is a block diagram of an exemplary computer system for implementing embodiments consistent with the present disclosure.
Variations of computer system 401 may be used for implementing all the computing systems that may be utilized to implement the features of the present disclosure. Computer system 401 may comprise a central processing unit ("CPU" or "processor") 402. Processor 402 may comprise at least one data processor for executing program components for executing user- or system-generated requests. The processor may include specialized processing units such as integrated system (bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, etc. The processor 402 may include a microprocessor, such as AMD Athlon, Duron or Opteron, ARM's application, embedded or secure processors, IBM PowerPC, Intel's Core, Itanium, Xeon, Celeron or other line of processors, etc. The processor 402 may be implemented using mainframe, distributed processor, multi-core, parallel, grid, or other architectures. Some embodiments may utilize embedded technologies like application-specific integrated circuits (ASICs), digital signal processors (DSPs), Field Programmable Gate Arrays (FPGAs), etc.
Processor 402 may be disposed in communication with one or more input/output (I/O) devices via I/O interface 403. The I/O interface 403 may employ communication protocols/methods such as, without limitation, audio, analog, digital, monoaural, RCA, stereo, IEEE-1394, serial bus, universal serial bus (USB), infrared, PS/2, BNC, coaxial, component, composite, digital visual interface (DVI), high-definition multimedia interface (HDMI), RF antennas, S-Video, VGA, IEEE 802.n /b/g/n/x, Bluetooth, cellular (e.g., code-division multiple access (CDMA), high-speed packet access (HSPA+), global system for mobile communications (GSM), long-term evolution (LTE), WiMax, or the like), etc.
Using the I/O interface 403, the computer system 401 may communicate with one or more I/O devices. For example, the input device 404 may be an antenna, keyboard, mouse, joystick, (infrared) remote control, camera, card reader, fax machine, dongle, biometric reader, microphone, touch screen, touchpad, trackball, sensor (e.g., accelerometer, light sensor, GPS, gyroscope,

proximity sensor, or the like), stylus, scanner, storage device, transceiver, video device/source, visors, etc. Output device 405 may be a printer, fax machine, video display (e.g., cathode ray tube (CRT), liquid crystal display (LCD), light-emitting diode (LED), plasma, or the like), audio speaker, etc. In some embodiments, a transceiver 406 may be disposed in connection with the processor 402. The transceiver may facilitate various types of wireless transmission or reception. For example, the transceiver may include an antenna operatively connected to a transceiver chip (e.g., Texas Instruments WiLink WL1283, Broadcom BCM4750IUB8, Infineon Technologies X-Gold 618-PMB9800, or the like), providing IEEE 802.11a/b/g/n, Bluetooth, FM, global positioning system (GPS), 2G/3GHSDPA/HSUPA communications, etc.
In some embodiments, the processor 402 may be disposed in communication with a communication network 408 via a network interface 407. The network interface 407 may communicate with the communication network 408. The network interface 407 may employ connection protocols including, without limitation, direct connect, Ethernet (e.g., twisted pair 10/40/400 Base T), transmission control protocol/internet protocol (TCP/IP), token ring, IEEE 802.11a/b/g/n/x, etc. The communication network 408 may include, without limitation, a direct interconnection, local area network (LAN), wide area network (WAN), wireless network (e.g., using Wireless Application Protocol), the Internet, etc. Using the network interface 407 and the communication network 408, the computer system 401 may communicate with user device 104, IOT gateway 104 and the FSM 108.
In some embodiments, the processor 402 may be disposed in communication with one or more memory devices (e.g., RAM 413, ROM 4Error! Reference source not found. 14, etc.) via a storage interface 412. The storage interface may connect to memory devices including, without limitation, memory drives, removable disc drives, etc., employing connection protocols such as serial advanced technology attachment (SATA), integrated drive electronics (IDE), IEEE-1394, universal serial bus (USB), fiber channel, small computer systems interface (SCSI), etc. The memory drives may further include a drum, magnetic disc drive, magneto-optical drive, optical drive, redundant array of independent discs (RAID), solid-state memory devices, solid-state drives, etc.
The memory 415 may store a collection of program or database components, including, without limitation, an operating system 4Error! Reference source not found. 16, user interface application

4Error! Reference source not found. 17, web browser 418, mail server 419, mail client 420, user/application data 421 (e.g., any data variables or data records discussed in this disclosure), etc. The operating system 416 may facilitate resource management and operation of the computer system 401. Examples of operating systems include, without limitation, Apple Macintosh OS X, UNIX, Unix-like system distributions (e.g., Berkeley Software Distribution (BSD), FreeBSD, NetBSD, OpenBSD, etc.), Linux distributions (e.g., Red Hat, Ubuntu, Kubuntu, etc.), IBM OS/2, Microsoft Windows (XP, Vista/7/8, etc.), Apple iOS, Google Android, Blackberry OS, or the like. User interface 417 may facilitate display, execution, interaction, manipulation, or operation of program components through textual or graphical facilities. For example, user interfaces may provide computer interaction interface elements on a display system operatively connected to the computer system 401, such as cursors, icons, check boxes, menus, scrollers, windows, widgets, etc. Graphical user interfaces (GUIs) may be employed, including, without limitation, Apple Macintosh operating systems'Aqua, IBM OS/2, Microsoft Windows (e.g., Aero, Metro, etc.), Unix X-Windows, web interface libraries (e.g., ActiveX, Java, Javascript, AJAX, HTML, Adobe Flash, etc.), or the like.
In some embodiments, the computer system 401 may implement a web browser 418 stored program component. The web browser may be a hypertext viewing application, such as Microsoft Internet Explorer, Google Chrome, Mozilla Firefox, Apple Safari, etc. Secure web browsing may be provided using HTTPS (secure hypertext transport protocol), secure sockets layer (SSL), Transport Layer Security (TLS), etc. Web browsers may utilize facilities such as AJAX, DHTML, Adobe Flash, JavaScript, Java, application programming interfaces (APIs), etc. In some embodiments, the computer system 301 may implement a mail server 419 stored program component. The mail server may be an Internet mail server such as Microsoft Exchange, or the like. The mail server may utilize facilities such as ASP, ActiveX, ANSI C++/C#, Microsoft .NET, CGI scripts, Java, JavaScript, PERL, PHP, Python, WebObjects, etc. The mail server may utilize communication protocols such as internet message access protocol (FMAP), messaging application programming interface (MAPI), Microsoft Exchange, post office protocol (POP), simple mail transfer protocol (SMTP), or the like. In some embodiments, the computer system 401 may implement a mail client 420 stored program component. The mail client may be a mail viewing application, such as Apple Mail, Microsoft Entourage, Microsoft Outlook, Mozilla Thunderbird, etc.

In some embodiments, computer system 401 may store user/application data 421, such as the data, variables, records, etc. as described in this disclosure. Such databases may be implemented as fault-tolerant, relational, scalable, secure databases such as Oracle or Sybase. Alternatively, such databases may be implemented using standardized data structures, such as an array, hash, linked list, struct, structured text file (e.g., XML), table, or as object-oriented databases (e.g., using ObjectStore, Poet, Zope, etc.). Such databases may be consolidated or distributed, sometimes among the various computer systems discussed above in this disclosure. It is to be understood that the structure and operation of the any computer or database component may be combined, consolidated, or distributed in any working combination.
As described above, the modules 206, amongst other things, include routines, programs, objects, components, and data structures, which perform particular tasks or implement particular abstract data types. The modules 206 may also be implemented as, signal processor(s), state machine(s), logic circuitries, and/or any other device or component that manipulate signals based on operational instructions. Further, the modules 206 can be implemented by one or more hardware components, by computer-readable instructions executed by a processing unit, or by a combination thereof.
The illustrated steps are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments. Also, the words "comprising," "having," "containing," and "including," and other similar forms are intended to be equivalent in meaning and be open ended in that an item or items following any one of these words is not meant to be an exhaustive listing of such item or items, or meant to be limited to only the listed item or items. It must also be noted that as used herein and in the appended claims, the singular forms "a," "an," and "the" include plural references unless the context clearly dictates otherwise.

Furthermore, one or more computer-readable storage media may be utilized in implementing embodiments consistent with the present disclosure. A computer-readable storage medium refers to any type of physical memory on which information or data readable by a processor may be stored. Thus, a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the embodiments described herein. The term "computer-readable medium" should be understood to include tangible items and exclude carrier waves and transient signals, i.e., are non-transitory. Examples include random access memory (RAM), read-only memory (ROM), volatile memory, nonvolatile memory, hard drives, CD ROMs, DVDs, flash drives, disks, and any other known physical storage media.
Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. Accordingly, the disclosure of the embodiments of the disclosure is intended to be illustrative, but not limiting, of the scope of the disclosure.
With respect to the use of substantially any plural and/or singular terms herein, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. The various singular/plural permutations may be expressly set forth herein for sake of clarity.

We claim:
1. A method of enabling data communication for field service management, the method
comprising;
receiving, by a processor of an Internet of Things (IOT) gateway, a synchronization signal from at least one IOT device and a user device, at a current location;
identifying, by the processor, the at least one IOT device capable of establishing connection with the IOT gateway based on one or more parameters associated with the synchronization signal;
dynamically creating, by the processor, at least one mesh network comprising the at least one IOT device identified based on the one or more parameters; and
receiving, by the processor, a sensor data from the at least one IOT device of the at least one mesh network.
2. The method as claimed in claim 1, wherein dynamically creating the at least one mesh
network comprising the steps of:
determining the nearest at least one IOT device and an IOT device_ identification (ID) of the at least one IOT device nearest to the IOT gateway;
verifying the IOT devicelD with a list of predetermined IOT devicelD stored in a data repository coupled with the IOT gateway; and
generating the at least one mesh network with a mesh ID using an appropriate mesh protocol, wherein the at least one mesh network comprises at least one IOT device having verified IOT devicelD as a mesh node and the IOT gateway as a gateway node.
3. The method as claimed in claim 1, further comprising:
validating the sensor data received from the at least one IOT device by comparing with predefined data constraints of the sensor data, wherein the predefined data constraints are stored in the data repository; and
transmitting the validated sensor data to the user device, wherein the user device is connected to the IOT gateway using a first communication protocol.

4. The method as claimed in claim 3, further comprising enabling display of the validated sensor data on an augmented reality (AR) device coupled with the user device using a second communication protocol.
5. The method as claimed in claim 3, further comprising:
detecting, by the user device, an anomaly in the validated sensor data received from at least one IOT device of the mesh network;
automatically connecting, by the user device, to an external expert system to enable dynamic visual assistance using the AR device coupled with the user device;
receiving, by the user device, content related to visual assistance from the external expert system in response to detected anomaly in the sensor data; and
rendering, by the user device, the received content on the AR device for visual display by the user of the user device.
6. The method as claimed in claim 5, further comprising detecting, by the user device, abnormality data of the IOT gateway to ensure health of the IOT gateway by scanning a QR code of the IOT gateway.
7. The method as claimed in claim 1, wherein the IOT gateway is a portable hand-held device capable of being carried to one or more locations and dynamically connecting to at least one IOT device.
8. The method as claimed in claim 1, wherein the at least one IOT device is identified by the IOT devicelD and the mesh ID of the at least one mesh network that includes the at least one IOT device as the mesh node.
9. The method as claimed in claim 2, wherein the IOT gateway is identified by at least one IOT device using a unique gateway ID of the IOT gateway, list of IOT devicelDs and the mesh ID of at least one mesh network created corresponding to the IOT gateway.
10. A system for enabling data communication for field service management, the system comprising:
at least one IOT device installed in a location;

an IOT gateway comprises a processor; and
a user device communicatively coupled with the IOT gateway using a first communication protocol;
wherein the processor of IOT gateway is configured to:
receive a synchronization signal from the at least one IOT device and the user device, at a current location;
identify the at least one IOT device capable of establishing connection with the IOT gateway based on one or more parameters associated with the synchronization signal;
dynamically create at least one mesh network comprising the at least one IOT device identified based on the one or more parameters; and
receive a sensor data as input from the at least one IOT devices of the at least one mesh network.
11. The system as claimed in claim 10, wherein the processor is configured to dynamically
create the at least one mesh network by:
determining the nearest at least one IOT device and an IOT device_ identification (ID) of the at least one IOT device nearest to the IOT gateway;
verifying the IOT devicelD with a list of predetermined IOT devicelD stored in a data repository coupled with the IOT gateway; and
generating the at least one mesh network with a mesh ID using an appropriate mesh protocol, wherein the at least one mesh network comprises at least one IOT device having verified IOT devicelD as a mesh node and the IOT gateway as a gateway node.
12. The system as claimed in claim 10, wherein the processor is further configured to:
validate the sensor data received from the at least one IOT device by comparing with predefined data constraints of the sensor data, wherein the predefined data constraints are stored in the data repository; and
transmit the validated sensor data to the user device, wherein the user device is connected to the IOT gateway.

13. The system as claimed in claim 12, further comprises an augmented reality (AR) device coupled with the user device using a second communication protocol, wherein the user device is configured to enable display of the validated sensor data on the AR device.
14. The system as claimed in claim 12, wherein the user device is configured to:
detect an anomaly in the validated sensor data received from at least one IOT device of the mesh network;
automatically connect to an external expert system to enable dynamic visual assistance using the AR device coupled with the user device;
receive content related to visual assistance from the external expert system in response to detected anomaly in the sensor data; and
render the received content on the AR device for visual display by the user of the user device.
15. The system as claimed in claim 14, wherein the user device is further configured to detect anomaly data of the IOT gateway to ensure health of the IOT gateway by scanning a QR code of the IOT gateway.
16. The system as claimed in claim 10, wherein the IOT gateway is a portable hand-held device capable of being carried to one or more locations and dynamically connecting to at least one IOT device.
17. The system as claimed in claim 10, wherein the at least one IOT device is identified by the IOT devicelD and the mesh ID of the at least one mesh network that includes the at least one IOT device as the mesh node.
18. The system as claimed in claim 11, wherein the IOT gateway is identified by at least one IOT device using a unique gateway ID of the IOT gateway, list of IOT devicelDs and the mesh ID of at least one mesh network created corresponding to the IOT gateway.