DESC:CROSS-REFERENCE TO RELATED APPLICATIONS AND PRIORITY
[0001] The present application claims priority from the Indian patent application having application number 202411036811, filed on 9th May 2024, incorporated herein by a reference.
TECHNICAL FIELD
[0002] The present subject matter described herein, in general, relates to the field of smart meter systems and devices. More particularly, the present subject matter relates to a system and a method for enabling alternative communication for smart meters with dual communication capability.
BACKGROUND
[0003] This section is intended to introduce the reader to various aspects of art, which may be related to various aspects of the present disclosure that are described or claimed below. This discussion is believed to be helpful in providing the reader with background information to facilitate a better understanding of the various aspects of the present disclosure. Accordingly, it should be understood that these statements in this background section are to be read in this light, and not as admissions of prior art. Similarly, a problem mentioned in the background section or associated with the subject matter of the background section should not be assumed to have been previously recognized in the prior art. The subject matter in the background section merely represents different approaches, which in and of themselves may also correspond to implementations of the claimed technology.
[0004] The advent of the Internet of Things (IoT) has revolutionized remote monitoring and control across various sectors, particularly in energy management. Digital smart meters represent a significant advancement over traditional analog meters, embodying a fundamental concept of IoT applications. By enabling remote load monitoring and control, smart metering plays a crucial role in the integration of modern technologies such as smart grids, blockchain, and automation into conventional power systems. Smart meters leverage IoT technology to monitor and manage energy consumption in real time, providing utilities with valuable insights into usage patterns and enhancing consumer engagement through transparent energy tracking.
[0005] Through interconnected networks, smart meters collect and transmit data that allows utilities to optimize energy distribution and improve operational efficiency. The integration of IoT in smart metering not only enhances energy management and promotes sustainability but also facilitates the implementation of demand-response programs, contributing to the resilience of the power grid.
[0006] Despite these advancements, smart meters are often confronted with network reliability challenges, particularly in adverse conditions. For instance, consider a scenario where smart meters are installed in the basement of a building, relying solely on cellular connectivity. In such environments, limited or intermittent cellular reception can lead to significant performance issues, undermining the effectiveness of these smart meters.
[0007] Current smart metering systems typically depend on communication technologies such as cellular networks, Power Line Communication (PLC), Radio Frequency (RF) mesh, or G3 Power Line Communication (G3PLC). While these systems offer various connectivity options, they face challenges stemming from the lack of a robust and cost-effective communication infrastructure. Although some smart meters are designed with dual communication capabilities, allowing them to switch between different networks for data transmission, limitations still persist.
[0008] A notable issue arises when smart meters operate exclusively on cellular technology in locations with poor connectivity, such as basements. These smart meters suffer from data transmission delays, incomplete readings, and diminished overall operational efficiency due to inadequate cellular reception. While certain smart meters feature Bluetooth capabilities for functionalities like remote meter reading and reconnecting/disconnecting services, they often lack the ability to relay data back to central systems effectively.
[0009] Additionally, existing smart metering systems are hindered by structural limitations. Although some meters incorporate Bluetooth functionality, it is typically integrated directly onto the meter board rather than being housed on a separate Network Interface Card (NIC). This configuration complicates network setups and restricts the flexibility and scalability of the overall system. Furthermore, in many instances, meters equipped with communication capabilities are limited to a single communication channel or protocol (e.g., Bluetooth or RF), which may only facilitate data transfer to a central hub without leveraging the advantages of dual communication.
[0010] Moreover, even when smart meters include Bluetooth functionality on their NICs, existing systems often fail to utilize Bluetooth connectivity in conjunction with star or mesh communication protocols. As a result, these systems are unable to identify the nearest operational smart meter within a cellular network, preventing them from effectively relaying data from non-cellular network meters to a functioning cellular meter.
[0011] In light of these challenges, there is an urgent need for an enhanced system and method for smart meters that improves communication capabilities and the overall efficiency of smart meter networks, particularly through the implementation of dual communication capabilities. Such improvements would not only address current limitations but also pave the way for a more resilient and responsive energy management infrastructure.
[0012] Further limitations and disadvantages of conventional and traditional approaches will become apparent to one of skill in the art, through the comparison of described systems with some aspects of the present disclosure, as set forth in the remainder of the present application and with reference to the drawings.
SUMMARY
[0013] This summary is provided to introduce concepts related to a method and system for communication on one or more devices, and the concepts are further described below in the detailed description. This summary is not intended to identify essential features of the claimed subject matter, nor is it intended for use in determining or limiting the scope of the claimed subject matter.
[0014] According to embodiments illustrated herein, there is provided a method for communication on one or more devices. In one implementation of the present disclosure, the method may involve identifying a condition of a primary communication interface of one or more devices. Each of the one or more devices comprises at least one of the primary communication interface, a secondary communication interface, and a combination thereof. Further, the method may involve categorizing the one or more devices into one or more device groups, based on the condition of the primary communication interface. The one or more device groups may comprise a connected device group and a disconnected device group. The connected device group comprises one or more first devices from the one or more devices, and the disconnected device group comprises one or more second devices from the one or more devices. Further, the method may involve connecting the one or more devices to the one or more second devices via the secondary communication interface.
[0015] According to embodiments illustrated herein, there is provided a system for communication on the one or more devices. In one implementation of the present disclosure, the system may include a processor and a memory communicatively coupled to the processor, which, upon execution, causes the processor to identify the condition of the primary communication interface of the one or more devices. Further, each of the one or more devices may comprise at least one of the primary communication interface, the secondary communication interface, and a combination thereof. Furthermore, the system may categorize the one or more devices into the one or more device groups, based on the condition of the primary communication interface. Furthermore, one or more device groups may comprise the connected device group and the disconnected device group. Furthermore, the connected device group may comprise the one or more first devices from the one or more devices, and the disconnected device group may comprise the one or more second devices from the one or more devices. Furthermore, the system may connect the one or more first devices to the one or more second devices via the secondary communication interface.
[0016] According to the embodiments illustrated herein, the non-transitory computer-readable medium storing computer-executable instructions for communication on the one or more devices is disclosed. The computer-executable instructions may be configured to, when executed by a processor, cause the processor to perform steps that may include identifying the condition of the primary communication interface of the one or more devices. Further, each of the one or more devices may comprise at least one of the primary communication interface, the secondary communication interface, and a combination thereof. Further steps may include categorizing the one or more devices into the one or more device groups, based on the condition of the primary communication interface. Further, the one or more device groups may comprise the connected device group and the disconnected device group. The connected device group may comprise the one or more first devices from the one or more devices, and the disconnected device group may comprise the one or more second devices from the one or more devices. Furthermore the step include, connecting the one or more first devices to the one or more second devices via the secondary communication interface.
[0017] 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 DESCRIPTION OF DRAWINGS
[0018] The accompanying drawings illustrate the various embodiments of systems, methods, and other aspects of the disclosure. Any person with ordinary skills in the art will appreciate that the illustrated element boundaries (e.g., boxes, groups of boxes, or other shapes) in the figures represent one example of the boundaries. In some examples, one element may be designed as multiple elements, or multiple elements may be designed as one element. In some examples, an element shown as an internal component of one element may be implemented as an external component in another, and vice versa. Further, the elements may not be drawn to scale.
[0019] Various embodiments will hereinafter be described in accordance with the appended drawings, which are provided to illustrate and not to limit the scope in any manner, wherein similar designations denote similar elements, and in which:
[0020] FIGURE. 1 is a block diagram that illustrates a system architecture (100) for communication on one or more devices (108), in accordance with an embodiment of the present disclosure.
[0021] FIGURE. 2 is a block diagram that illustrates an exemplary connection of the one or more devices (108) to a communication network (106), in accordance with an embodiment of the present disclosure.
[0022] FIGURE. 3 is a block diagram (300) that illustrates an exemplary downlink messaging functionality of the system (100) for communication on one or more devices (202), in accordance with an embodiment of the present disclosure.
[0023] FIGURE. 4 is a block diagram (400) that illustrates an exemplary uplink messaging functionality of the system (100) for communication on the one or more devices (202), in accordance with an embodiment of the present disclosure.
[0024] FIGURE. 5 is a flowchart that illustrates a method (500) for communication on the one or more devices (108), in accordance with an embodiment of the present disclosure.
[0025] FIGURE. 6 illustrates a block diagram (600) of an exemplary computer system for implementing embodiments consistent with the present disclosure.
DETAILED DESCRIPTION
[0026] The present disclosure may be best understood with reference to the detailed figures and description set forth herein. Various embodiments are discussed below with reference to the figures. However, those skilled in the art will readily appreciate that the detailed descriptions given herein with respect to the figures are simply for explanatory purposes, as the methods and systems may extend beyond the described embodiments. For example, the teachings presented\ and the needs of a particular application may yield multiple alternative and suitable approaches to implement the functionality of any detail described herein. Therefore, any approach may extend beyond the particular implementation choices in the following embodiments described and shown.
[0027] References to “one embodiment,” “at least one embodiment,” “an embodiment,” “one example,” “an example,” “for example,” and so on indicate that the embodiment(s) or example(s) may include a particular feature, structure, characteristic, property, element, or limitation but that not every embodiment or example necessarily includes that particular feature, structure, characteristic, property, element, or limitation. Further, repeated use of the phrase “in an embodiment” does not necessarily refer to the same embodiment.
[0028] An objective of the present disclosure is to enhance the reliability of smart meter networks by allowing communication through multiple channels, ensuring consistent data transfer even under challenging conditions.
[0029] Another objective of the present disclosure is to enable smart meters to identify the nearest operational meter(s) with a working primary communication channel, which facilitates efficient data routing in areas with poor cellular connectivity.
[0030] Yet another objective of the present disclosure is to promote energy efficiency by allowing smart meters to optimize data reporting based on real-time energy usage patterns.
[0031] Yet another objective of the present disclosure is to support the implementation of demand-response programs by providing utilities with timely and accurate data on energy consumption from smart meters.
[0032] Yet another objective of the present disclosure is to enable seamless integration of smart meters with existing smart grid technologies, enhancing the overall functionality of the energy distribution system.
[0033] Yet another objective of the present disclosure is to provide a cost-effective solution for enhancing communication capabilities in smart meters, reducing reliance on traditional cellular networks in areas with limited coverage.
[0034] Yet another objective of the present disclosure is to facilitate the expansion of smart meter networks by ensuring compatibility with various communication protocols, allowing for greater scalability.
[0035] Yet another objective of the present disclosure is to improve user experience by allowing consumers to access their energy usage data in real-time through reliable communication channels.
[0036] Yet another objective of the present disclosure is to integrate Bluetooth connectivity with star or mesh communication protocols in smart meters, leading to improved data transfer capabilities between the meters and remote servers.
[0037] Another objective of the present disclosure is to enhance the resilience of smart meter networks against communication failures, ensuring continuous operation and data integrity.
[0038] FIGURE. 1 is a block diagram that illustrates a system (100) for communication on one or more devices (108), in accordance with an embodiment of the present subject matter. The system environment (100) typically includes a memory (102), a processor (104), a communication network (106), and one or more portable devices (108). The memory (102), the processor (104), and the one or more portable devices (108) are typically communicatively coupled with each other via the communication network (106). In an embodiment, processing capability of the processor (104) may be implemented by an applications server (104) and the storage capability of the memory (102) may be implemented by a database server (102). Thus, the term “processor” and “application server” can be used interchangeably throughout this specification. Further, the term “memory” and “database server” can be used interchangeably throughout this specification. Further, the term “one or more devices” and “one or more portable devices” can be used interchangeably throughout this specification. In an embodiment, the application server (104) may communicate with the database server (102), and the one or more portable devices (108) using one or more protocols such as, but not limited to, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), RF mesh, Bluetooth Low Energy (BLE), and the like, to communicate with one another.
[0039] In an embodiment, the memory (102) may be configured to store, manage, and retrieve data associated with the one or more portable devices (108). The memory (102) may maintain information related to device identifiers, operational status, communication interface conditions, device group categorizations (such as connected device groups and disconnected device groups), and historical communication data. The memory (102) may also store routing tables, multi-hop communication paths, and other metadata necessary for enabling communication between devices through secondary communication interfaces when primary communication interfaces are non-functional. In some embodiments, the memory (102) may interact with the processor (104) to update device statuses in real-time and to facilitate efficient data transmission from the portable devices (108) to external systems, such as a meter data management (MDM) server or other backend applications.
[0040] In an embodiment, the memory (102) may be realized through various memory technologies such as, but not limited to, flash memory, solid-state drives (SSD), dynamic random-access memory (DRAM), static random-access memory (SRAM), read-only memory (ROM), or a combination thereof. In an embodiment, the memory (102) may be configured to utilize the processor (104) for processing, analyzing, and managing communication-related data received from the one or more portable devices (108).
[0041] A person with ordinary skills in art will understand that the scope of the disclosure is not limited to the memory (102) as a separate entity. In an embodiment, the functionalities of the memory (102) can be integrated into the processor (104) or into the one or more portable devices (108).
[0042] In an embodiment, the processor (104) may refer to a computing unit or a software framework configured to host and execute an application or software service. In an embodiment, the processor (104) may be implemented to execute procedures such as, but not limited to, programs, routines, or scripts stored in one or more memories (102) for supporting the hosted application or software service. The hosted application or software service may be configured to perform one or more predetermined operations. The processor (104) may be realized through various types of processing environments such as, but not limited to, Java Virtual Machine (JVM), .NET runtime, PHP runtime environment, embedded processors, or other computing architectures capable of managing communication services and operations.
[0043] In an embodiment, the processor (104) may be configured to utilize the memory (102) and the one or more portable devices (108), in conjunction, for securely managing communication operations based on the functional condition of the primary communication interface. In an implementation, the processor (104) may be configured to periodically monitor the primary communication interface of each of the one or more portable devices (108) and categorize the devices into a connected device group and a disconnected device group. The processor (104) may then facilitate the connection of one or more first devices from the connected device group to one or more second devices from the disconnected device group via the secondary communication interface, ensuring continuous communication even when the primary communication interface is non-functional. In an embodiment, the processor (104) may correspond to a communication management platform, which performs one or more communication operations based on the detected functionality conditions of the primary communication interfaces.
[0044] In an embodiment, the communication network (106) may correspond to a communication medium through which the application server (104), the database server (102), and the one or more portable devices (108) may communicate with each other. Such a communication may be performed in accordance with various wired and wireless communication protocols. Examples of such wired and wireless communication protocols include, but are not limited to, Transmission Control Protocol and Internet Protocol (TCP/IP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), Wireless Application Protocol (WAP), File Transfer Protocol (FTP), ZigBee, EDGE, infrared IR), IEEE 802.11, 802.16, 2G, 3G, 4G, 5G, 6G, 7G cellular communication protocols, and/or Bluetooth (BT) communication protocols. The communication network (106) may either be a dedicated network or a shared network. Further, the communication network (106) may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, and the like. The communication network (106) may include, but is not limited to, the Internet, intranet, a cloud network, a Wireless Fidelity (Wi-Fi) network, a Wireless Local Area Network (WLAN), a Local Area Network (LAN), a cable network, the wireless network, a telephone network (e.g., Analog, Digital, POTS, PSTN, ISDN, xDSL), a telephone line (POTS), a Metropolitan Area Network (MAN), an electronic positioning network, an X.25 network, an optical network (e.g., PON), a satellite network (e.g., VSAT), a packet-switched network, a circuit-switched network, a public network, a private network, and/or other wired or wireless communications network configured to carry data.
[0045] In an embodiment, the one or more portable devices (108) may refer to at least one of a computing device, one or more devices, one or more smart devices or a combination thereof. In another embodiment, the one or more portable devices (108) may be configured for communication with external networks or other devices. The one or more portable devices (108) may comprise one or more processors and one or more memory modules. The one or more memories may include computer-readable instructions that are executable by the processors to perform predetermined operations.
[0046] In an embodiment, the one or more portable devices (108) may be configured to identify a functionality condition of their primary communication interface. Based on the identified condition, the portable devices (108) may categorize themselves into a connected device group or a disconnected device group. The one or more portable devices (108) may also be configured to establish communication with other devices via the secondary communication interface when the primary communication interface is non-functional, ensuring continuous connectivity. In an implementation, the portable devices (108) may present a user interface for managing device connectivity and performing relevant communication operations, securely transmitting data between the connected and disconnected device groups. Examples of the one or more portable devices (108) may include, but are not limited to, a personal computer, a laptop, a personal digital assistant (PDA), a mobile device, a tablet, or any other computing device.
[0047] The system (100) can be implemented using hardware, software, or a combination of both, which may include utilizing one or more computer programs, mobile applications, or "apps" deployed either on-premises over corresponding computing terminals or virtually over cloud infrastructure. The system (100) may incorporate various micro-services or groups of independent computer programs, each capable of functioning autonomously while collaborating with other micro-services to achieve the overall functionality. The system (100) may also interface with third-party or external computer systems as necessary. Internally, the system (100) may serve as the central processor for handling communication operations between the various devices within the connected device group and the disconnected device group. A critical feature of the system (100) is its ability to securely perform one or more communication operations based on the functionality conditions of the primary communication interfaces, enabling continuous connectivity between devices. In a specific embodiment, the system (100) is implemented to ensure secure and efficient data transmission via the secondary communication interface when the primary communication interface is non-functional.
[0048] In one non-limiting embodiment of the present disclosure, a system for communication on one or more smart meters is disclosed. The system may include one or more smart meters connected to each other using either a star communication network protocol or a mesh communication network protocol. Further, each smart meter within the system may be equipped with a network interface card (NIC) featuring a dual communication channel/protocol. Furthermore, the dual communication channel/protocol may comprise a primary communication channel and a secondary communication channel. Furthermore, the primary communication channel may include a wireless network, including cellular or non-cellular networks. Additionally, the secondary communication channel may utilize another type of wireless network.
[0049] In an exemplary embodiment, the wireless network, including cellular or non-cellular networks may be of various type such as 2G, 3G, 4G LTE, 5G, Radio Frequency (RF) mesh, Narrowband Internet of Things (NB-IoT), Power Line Communication (PLC), GSM, Bluetooth, Bluetooth Low energy (BLE) or a combination thereof.
[0050] In an exemplary embodiment, particularly, the secondary communication interface may utilize wireless networks, such as Bluetooth or BLE SoC (System on Chip), RF, LoRa (Long Range) or a combination thereof. In an implementation, the star or mesh communication network of the one or more smart meters only includes the smart meters within the said network, without having a centralized hub for data transmission. Each smart meter within the mesh/star network, due to its dual communication capability, may either directly connect to a remote server or may be indirectly connected to the remote server via other smart meters on the said network. Moreover, one or more smart meters may communicate with each other using a secondary communication interface in combination with either the star communication network protocol or the mesh communication network protocol.
[0051] In one exemplary embodiment, the dual communication channel/protocol may be integrated either directly onto the network interface card (NIC) of each smart meter or may be enabled on a printed circuit board (PCB) of the smart meter. This implementation may ensure seamless communication capabilities, enhancing the efficiency and adaptability of the one or more smart meters, thereby ensuring continuous data transmission.
[0052] In another exemplary embodiment, one or more smart meters, connected in a star or mesh communication network, may communicate with each other using the secondary communication interface. More specifically, the smart meter with a non-functional primary communication interface may possess the capability to identify the nearest smart meter whose primary communication interface is working.
[0053] In yet another exemplary embodiment, one or more smart meters may communicate with the remote server either via the primary communication interface or the secondary communication interface, thereby ensuring uninterrupted data transmission. More particularly, for instance, if the smart meter’s primary communication interface is not functioning, then that smart meter may relay data, using the secondary communication interface to another smart meter having a working primary communication interface, connected over the mesh communication network. Another smart meter, with a primary communication interface, will send the relay data to the remote network using the primary communication interface.
[0054] In yet another exemplary embodiment, the system may enable one or more smart meters to communicate with the remote server either via the primary communication interface or the secondary communication interface, thereby ensuring uninterrupted data. Notably, in instances where a smart meter's primary communication interface is not working, the smart meter intelligently reroutes data through another meter with a functional primary communication interface, by using the secondary communication interface in combination with a mesh network. Thus, connecting one or more smart meters using the mesh network helps to overcome existing communication challenges, enhancing reliability and cost-effectiveness in remote monitoring and control applications.
[0055] Now referring to FIGURE 2, an exemplary connection of the one or more portable devices (108) to the communication network (106) is illustrated in accordance with an embodiment of the present subject matter. In one embodiment, the one or more portable devices (108) may include one or more devices (202) connected to the communication network (106) via at least one of a primary communication interface, a secondary communication interface, or a combination thereof. In one embodiment, the one or more portable devices (108) may include one or more devices (202) connected to the communication network (106) via a primary communication interface.
[0056] In an embodiment, the one or more devices (202) may correspond to a variety of utility meters, including, but not limited to, electricity meters, water meters, gas meters, hybrid meters, digital meters, prepaid meters, postpaid meters, as well as residential, commercial, and industrial meters. These one or more devices (202) may benefit from the disclosed dual-channel communication architecture to ensure uninterrupted data transmission in environments with unreliable or intermittent connectivity.
[0057] In one embodiment, the primary communication interface may comprise one of a cellular or non-cellular network, such as 2G, 3G, 4G LTE, 5G, Radio Frequency (RF) mesh, Narrowband Internet of Things (NB-Iot), Power Line Communication (PLC), GSM, or a combination thereof.
[0058] In an embodiment, identifying the condition of the primary communication interface of each of the one or more devices (202) may comprise determining at least one of an operational status, a signal strength, a connectivity status, or a combination thereof. The condition assessment may be performed using periodic diagnostic checks or continuous monitoring algorithms. Based on this assessment, the system (100) may categorize the devices into a connected device group or a disconnected device group. This categorization may occur periodically over a predefined time interval, such as every few seconds or minutes, depending on application requirements. Each of the one or more devices may comprise a network interface card (NIC), wherein the NIC may include both the primary communication interface and the secondary communication interface. In another embodiment, the primary communication interface may differ from the secondary communication interface in terms of communication protocol, frequency, or range. For instance, the primary interface may use a long-range protocol such as 4G, LTE, or RF mesh, while the secondary interface may employ Bluetooth or BLE for short-range, device-to-device communication.
[0059] In another embodiment, one or more devices (202) are connected to each other via the secondary communication interface. Another wireless communication network may comprise one of Bluetooth or BLE Soc (System on Chip), RF, LoRa (Long Range), Zigbee, Z-Wave, NFC, Wi-Fi Direct, Thread, RFID, infrared communication protocols, or a combination thereof.
[0060] In yet another embodiment, one or more devices (202), including M1, M2, M3, M4, M5, may be connected via the primary communication interface and/or the secondary communication interface. Further, one or more devices (202) (M1, M2, M3, M4, M5) may be connected with each other through a secondary communication interface if the primary communication interface is unavailable.
[0061] In an embodiment, the connection between the one or more first devices and the one or more second devices via the secondary communication interface may be achieved using either a star topology or a mesh topology. The selection of the topology may be based on factors such as device density, communication range, energy efficiency, and network resilience. In a star topology, the one or more second devices may communicate with a central first device acting as a relay to the application server or memory (102). In a mesh topology, each device may serve as both a transmitter and a receiver, allowing multi-hop communication wherein data is dynamically routed through intermediate devices until it reaches its destination. This flexibility in topology may enhance the robustness of communication, particularly in environments where the primary communication interface is degraded or unavailable.
[0062] In an embodiment, each of the one or more second devices may be configured to identify the nearest first device having a functional primary communication interface. This identification may be performed based on parameters such as signal strength, last known connectivity status, device proximity, or historical communication patterns. Upon identifying a suitable first device, the second device may initiate a connection via the secondary communication interface, such as Bluetooth or BLE, to relay its data to the remote system.
[0063] In an embodiment, the one or more devices (202) may dynamically switch between the primary communication interface and the secondary communication interface based on the detected condition of the primary communication interface. For instance, when the primary interface (e.g., cellular or RF mesh) is available and functional, a device may use it for direct data transmission. However, upon detection of a degraded or unavailable primary interface, the device may automatically switch to the secondary interface (e.g., BLE) to maintain communication continuity, either directly or via neighbouring devices.
[0064] In an embodiment, data from a second device of the one or more second devices may be communicated to a remote server through multi-hop routing. In such cases, the second device may transmit its data via the secondary communication interface to a first device that has a working primary communication interface. This first device may then forward the data to the remote server using its functional primary interface. The remote server may correspond to a meter data management (MDM) server or another backend system responsible for processing, analyzing, or storing the metering data.
[0065] In an exemplary embodiment, the one or more devices (202) M3 may have both primary and secondary communication interface working, and other one or more devices (202) M1, M2, M4, M5 may have a non-functional primary communication interface but a functional secondary communication interface. Here, the one or more devices (202) M1, M2, M4, M5 may be connected to each other (specifically with M3) via the secondary communication interface in combination with a mesh network and route the data to the nearby one or more devices (202) M3 with a working primary communication interface. The received data from one or more devices (202) M1, M2, M4, M5 may be routed further to the communication network (106), via one or more devices (202) M3 having the active primary communication interface.
[0066] In an exemplary embodiment, a system (100) for communication on one or more devices (202) may be deployed in a building basement where one or more devices (202) (e.g., smart meters) may primarily rely on a 4G communication protocol. Due to the location of the basement, the cellular connectivity may be weak, resulting in unreliable performance of the devices. To address this, the system may equip the devices with dual communication capabilities: a primary communication interface using cellular/RF mesh technology (e.g., 4G LTE) and a secondary communication interface using Bluetooth. Further, the system (100) may categorize the one or more devices (202) into two groups based on the condition of their primary communication interface. The one or more devices (202) with a functional primary communication interface (e.g., 4G LTE) may be categorized into the connected device group, while those with a non-functional primary communication interface may be categorized into the disconnected device group. In this embodiment, the one or more devices (202) may establish a communication network using their secondary communication interface. Further, when a device from the one or more devices (202) in the disconnected device group may lose its primary communication interface (e.g., 4G), the system (100) may automatically switch to the secondary communication interface. For example, if only a few one or more devices (202) (e.g., M1 and M5) may maintain a stable 4G connection while other one or more devices (202) (e.g., M2, M4) may struggle to maintain connectivity, the one or more devices (202) with a functional Bluetooth (e.g., M2 and M4) may relay data to a nearby one or more devices (202) with an operational primary communication interface (e.g., M3). The data may be transmitted through a secondary communication interface in a mesh or star topology, allowing the data to be routed from one device to another until it may reach the device with the active 4G connection. From there, the data may be transmitted to the communication network (106) or cloud server via the primary communication interface. In one embodiment, the system (100) may categorize the devices into the appropriate groups based on the status of the primary communication interface, enabling continuous communication even when the primary communication interface fails. This may ensure uninterrupted operation and reliable communication within the network.
[0067] In an exemplary embodiment, the remote server may be a cloud-based server, a head-end system (HES), a data center server, an application server, or a combination of these, depending on the system’s configuration.
[0068] Now referring to FIGURE 3, a block diagram (300) describing an exemplary downlink messaging functionality of the system (100) for communication on the one or more devices (202), is illustrated in accordance with an embodiment of the present subject matter.
[0069] Further, the flowchart (300) illustrates a database server (320) connected with the communication network (106). Further, an application server (322) may be connected to the one or more devices (202) via the wireless communication network (106). The wireless communication network may comprise one of a cellular or non-cellular network, such as 2G, 3G, 4G LTE, 5G, Radio Frequency (RF) mesh, Narrowband Internet of Things (NB-IoT), Power Line Communication (PLC), GSM, or a combination thereof. The exemplary downlink messaging functionality of the system (100) may initiate at step (302). At step (304), the system (100) may check for the availability of the network or historical network data for the one or more devices (202) connected to the application server (322) via the wireless network. If no network is found and no historical network data is available, then the downlink messaging on Bluetooth for the system (100) may be stopped at step (318). If no network is found but historical network data may be available, then the system (100) may search for the nearest one or more devices (202) which were sending data previously, at step (306).
[0070] At step (308), the system (100) may send the received data to a connected device (M1) among the one or more devices (202) for further forwarding to a target device out of the one or more devices (202). The one or more devices (202) may be connected to each other via Bluetooth mesh communication (310).
[0071] At step (312), the connected one or more devices (202) (M1) may attempt to connect with the target device over the BLE mesh communication network (310). If the connection is successfully established (314), a command may be sent by the connected device (M1) to the target device, and the BLE connection may be disconnected at step (316). If the BLE connection is not established, the downlink messaging on Bluetooth may be stopped at step (318).
[0072] Now referring to FIGURE 4, a block diagram (400) describing an exemplary uplink messaging functionality of the system (100) for communication on the one or more devices (202) is illustrated, in accordance with an embodiment of the present subject matter. The exemplary uplink messaging functionality of the system (100) may start at step (402).
[0073] Further, the flowchart (400) illustrates one or more devices (202) (e.g., M1, M2) connected via a wireless network. The wireless network may comprise one of Bluetooth or BLE SoC (System on Chip), RF, LoRa (Long Range) or a combination thereof.
[0074] At step (404), the system (100) may check if the one or more devices (202) are connected to the Network Interface Card (NIC). If a connection is not found, the system (100) may open Transparent TCP at step (406) (for the second meter) and continue further operations.
[0075] If the device is connected to the NIC, the system (100) may set a process to check for the network and update the BLE status at given intervals at step (408). If the network is found, the system (100) may proceed to open Transparent TCP at step (410). If the network is not found, the system (100) may enable waiting for the network at step (412).
[0076] Subsequently, at step (414), whether from the network wait or after setting BLE status, the system (100) may start a scheduler and a BLE advertiser.
[0077] At step (416), the system (100) may check if a schedule is found. If no schedule is found, the system (100) may restart advertisement after a waiting time at step (428).
[0078] If a schedule is found, the system (100) may check again for the network at step (420). If the network is detected, the system (100) may skip the schedule and process transparent operations at step (422).
[0079] If the network is not detected, the system (100) may stop advertising and start BLE scanning at step (418).
[0080] At step (424), the system (100) may filter devices based on Company ID and network status. If a device is found at step (426), the system (100) may connect to the target meter at step (432).
[0081] After connection, the system (100) may send DLMS data over BLE at step (430). Following the data transmission, the device may disconnect at step (434), and the system (100) may stop the scanner and start the advertiser at step (438). The collected data at the receiver meter may be sent via UDP at step (436). Further, eventually, the uplink messaging on Bluetooth star/mesh may be stopped at step (440).
[0082] Now, referring to FIGURE 5 is a flowchart that illustrates a method (500) for communication on one or more devices (108), in accordance with at least one embodiment of the present disclosure. The flowchart is described in conjunction with Figures 1 and 2. The method (500) starts at step (502) and proceeds to step (506).
[0083] In operation, the method (500) may involve a variety of steps for communication on one or more devices (202).
[0084] The method (500) for communication on one or more devices (202) may initiate at step (502), where the system (100) may identify a condition of a primary communication interface of the one or more devices (202). The primary communication interface may comprise at least one of a cellular interface, RF mesh, NB-IoT, PLC, or similar long-range communication protocols. The condition may include parameters such as signal strength, connectivity status, or network availability.
[0085] At step (504), based on the evaluated condition, the method (500) may categorize the one or more devices (202) into one or more device groups. The device groups may include a connected device group, comprising one or more first devices having a functional or available primary communication interface, and a disconnected device group, comprising one or more second devices having a non-functional or unavailable primary communication interface. The grouping may be updated dynamically as the network condition changes over time.
[0086] At step (506), the method (500) may establish communication between the connected device group and the disconnected device group using a secondary communication interface. The secondary communication interface may include Bluetooth, BLE SoC (System on Chip), Zigbee, RF, LoRa, or other short-range communication technologies. The one or more first devices may act as relay nodes and may forward data to or from the one or more second devices using a mesh or star topology formed via the secondary interface. This may allow the disconnected devices to maintain communication with backend systems such as a remote server (e.g., application server (322) or database server (320)) through the connected devices.
[0087] Let us delve into a detailed working example of the present disclosure.
Example 1:
[0088] In this working example, a smart metering system is deployed across a large urban residential complex consisting of multiple buildings with varying network conditions, such as basements, upper floors, and rooftop installations. Each building is equipped with smart meters for monitoring electricity consumption. Each smart meter is equipped with dual communication capabilities: a primary communication channel (such as LTE, RF mesh, or PLC) and a secondary communication channel (such as Bluetooth, BLE, or Zigbee).
[0089] Let’s consider a situation where the building has three smart meters: Smart Meter A, located in the basement; Smart Meter B, located on the ground floor; and Smart Meter C, installed on the rooftop.
Scenario 1: Primary Communication Failure in the Basement
[0090] Smart Meter A, installed in the basement, experiences signal disruption due to poor cellular reception in the underground area. Its primary communication channel, which operates on LTE, is unable to send meter readings to the remote server. As per the system design, Smart Meter A automatically switches to its secondary communication channel, which uses Bluetooth mesh.
[0091] Smart Meter A identifies Smart Meter B on the ground floor as the nearest operational smart meter with a working primary communication channel. Smart Meter A connects to Smart Meter B using its Bluetooth mesh connection and securely transmits its data (energy consumption readings) to Smart Meter B.
[0092] Since Smart Meter B has stable LTE connectivity, it acts as an intermediary and forwards the data received from Smart Meter A to the remote server via its primary communication channel. This data is processed by the server, ensuring that Smart Meter A’s readings are recorded, despite the basement’s limited connectivity.
Scenario 2: Bluetooth Mesh Communication for Data Routing
[0093] In another instance, Smart Meter C, installed on the rooftop, remains fully functional with a strong LTE connection. Both Smart Meter A (in the basement) and Smart Meter B (on the ground floor) experience intermittent primary communication failures. Smart Meter A and Smart Meter B are still able to communicate using the Bluetooth mesh network.
[0094] Smart Meter A first routes its data to Smart Meter B using Bluetooth mesh, and then, Smart Meter B passes this data, via the bluetooth further to Smart Meter C, which has an active LTE connection. Smart Meter C then transmits all data, including its own readings and the readings from Smart Meter A and Smart Meter B, to the remote server. The system ensures that even in a multi-hop scenario, data from smart meters with faulty primary channels can still be routed and delivered without any loss.
Scenario 3: Dual Communication Channel Integration
[0095] All smart meters in the system operate with both primary and secondary communication channels integrated on their network interface cards (NIC). The printed circuit board (PCB) within each smart meter is designed to seamlessly manage these dual channels. Whenever a primary communication channel fails, it switches to the secondary channel automatically, ensuring that there is no interruption in data transmission. This dual-channel setup allows the system to utilize a hybrid network topology, employing both mesh (via Bluetooth or BLE) and direct communication (via LTE or RF) for optimized data transmission.
[0096] For instance, if the primary LTE network of Smart Meter B is temporarily down, it will route its data through the Bluetooth mesh network to either Smart Meter A or Smart Meter C, whichever has an operational primary communication channel at that time. This flexibility allows the system to efficiently handle both small and large-scale disruptions in communication infrastructure.
[0097] In this detailed working example, the system demonstrates robust dual communication capabilities that ensure continuous, reliable data transmission from smart meters to remote servers, regardless of the environmental or network conditions. By leveraging both Bluetooth mesh and primary communication protocols, smart meters can maintain network connectivity, route data intelligently, and provide energy consumption data without interruptions. This enhances the resilience of the smart metering system, particularly in locations where traditional communication methods may fail.
Example 2:
[0098] In this working example, the present disclosure is applied to an industrial IoT (Internet of Things) sensor network deployed within a factory facility. Each IoT sensor device (202) is configured with a primary communication interface, such as a Narrowband Internet of Things (NB-IoT) module, and a secondary communication interface comprising a Bluetooth Low Energy (BLE) system.
[0099] During regular operation, each IoT sensor device (202) communicates directly with the application server (104) through the primary communication interface over the wireless communication network (106). However, certain areas within the factory, such as underground storage rooms or metal-dense production zones, experience poor NB-IoT coverage. In such cases, affected IoT sensor devices (202) are categorized into a disconnected device group due to the unavailability of the primary communication channel.
[00100] The system (100) dynamically forms a Bluetooth star or mesh network between disconnected device group members and nearby connected device group members which maintain active primary connectivity. For example, a humidity sensor (S1) and a temperature sensor (S2) lose NB-IoT signal inside an underground warehouse, while a vibration sensor (S3) near the stairwell retains stable connectivity. Through the secondary communication interface, the humidity sensor (S1) and temperature sensor (S2) route their collected data via the vibration sensor (S3), which acts as a relay node.
[00101] The vibration sensor (S3) forwards the uplink data over the primary NB-IoT communication channel to the application server (104), thereby ensuring continuous data availability. Furthermore, the application server (104) synchronizes all transmitted data to the database server (102) and updates the network topology, dynamically adjusting device groupings based on ongoing connectivity assessments.
[00102] Thus, the disclosed system (100) facilitates robust IoT sensor data communication even in challenging environments, using both primary and secondary communication interfaces intelligently.
[00103] A person skilled in the art will understand that the scope of the disclosure is not limited to scenarios based on the aforementioned factors and using the aforementioned techniques and that the examples provided do not limit the scope of the disclosure.
[00104] FIGURE. 6 illustrates a block diagram of an exemplary computer system (601) for implementing embodiments consistent with the present disclosure.
[00105] Variations of computer system (601) may be used for communication of the one or more devices (108). The computer system (601) may comprise a central processing unit (“CPU” or “processor”) (602). The processor (602) may comprise at least one data processor for executing program components for executing user- or system-generated requests. A user may include a person, a person using a device such as such as those included in this disclosure, or such a device itself. Additionally, the processor (602) 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, or the like. In various implementations the processor (602) 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, for example. Accordingly, the processor (602) 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), or Field Programmable Gate Arrays (FPGAs), for example.
[00106] Processor (602) may be disposed in communication with one or more input/output (I/O) devices via I/O interface (603). Accordingly, the I/O interface (603) 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, for example.
FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See Section 10 and Rule 13)

Title of Invention:
A SYSTEM AND A METHOD FOR COMMUNICATION ON ONE OR MORE DEVICES

APPLICANT:
PROBUS SMART THINGS PRIVATE LIMITED

An Indian entity having address as:
63, IIIrd Floor, DSIDC Complex, Phase-I, Okhla Industrial Area, New Delhi- 110020

The following specification particularly describes the invention and the manner in which it is to be performed.

CROSS-REFERENCE TO RELATED APPLICATIONS AND PRIORITY
[0001] The present application claims priority from the Indian patent application having application number 202411036811, filed on 9th May 2024, incorporated herein by a reference.
TECHNICAL FIELD
[0002] The present subject matter described herein, in general, relates to the field of smart meter systems and devices. More particularly, the present subject matter relates to a system and a method for enabling alternative communication for smart meters with dual communication capability.
BACKGROUND
[0003] This section is intended to introduce the reader to various aspects of art, which may be related to various aspects of the present disclosure that are described or claimed below. This discussion is believed to be helpful in providing the reader with background information to facilitate a better understanding of the various aspects of the present disclosure. Accordingly, it should be understood that these statements in this background section are to be read in this light, and not as admissions of prior art. Similarly, a problem mentioned in the background section or associated with the subject matter of the background section should not be assumed to have been previously recognized in the prior art. The subject matter in the background section merely represents different approaches, which in and of themselves may also correspond to implementations of the claimed technology.
[0004] The advent of the Internet of Things (IoT) has revolutionized remote monitoring and control across various sectors, particularly in energy management. Digital smart meters represent a significant advancement over traditional analog meters, embodying a fundamental concept of IoT applications. By enabling remote load monitoring and control, smart metering plays a crucial role in the integration of modern technologies such as smart grids, blockchain, and automation into conventional power systems. Smart meters leverage IoT technology to monitor and manage energy consumption in real time, providing utilities with valuable insights into usage patterns and enhancing consumer engagement through transparent energy tracking.
[0005] Through interconnected networks, smart meters collect and transmit data that allows utilities to optimize energy distribution and improve operational efficiency. The integration of IoT in smart metering not only enhances energy management and promotes sustainability but also facilitates the implementation of demand-response programs, contributing to the resilience of the power grid.
[0006] Despite these advancements, smart meters are often confronted with network reliability challenges, particularly in adverse conditions. For instance, consider a scenario where smart meters are installed in the basement of a building, relying solely on cellular connectivity. In such environments, limited or intermittent cellular reception can lead to significant performance issues, undermining the effectiveness of these smart meters.
[0007] Current smart metering systems typically depend on communication technologies such as cellular networks, Power Line Communication (PLC), Radio Frequency (RF) mesh, or G3 Power Line Communication (G3PLC). While these systems offer various connectivity options, they face challenges stemming from the lack of a robust and cost-effective communication infrastructure. Although some smart meters are designed with dual communication capabilities, allowing them to switch between different networks for data transmission, limitations still persist.
[0008] A notable issue arises when smart meters operate exclusively on cellular technology in locations with poor connectivity, such as basements. These smart meters suffer from data transmission delays, incomplete readings, and diminished overall operational efficiency due to inadequate cellular reception. While certain smart meters feature Bluetooth capabilities for functionalities like remote meter reading and reconnecting/disconnecting services, they often lack the ability to relay data back to central systems effectively.
[0009] Additionally, existing smart metering systems are hindered by structural limitations. Although some meters incorporate Bluetooth functionality, it is typically integrated directly onto the meter board rather than being housed on a separate Network Interface Card (NIC). This configuration complicates network setups and restricts the flexibility and scalability of the overall system. Furthermore, in many instances, meters equipped with communication capabilities are limited to a single communication channel or protocol (e.g., Bluetooth or RF), which may only facilitate data transfer to a central hub without leveraging the advantages of dual communication.
[0010] Moreover, even when smart meters include Bluetooth functionality on their NICs, existing systems often fail to utilize Bluetooth connectivity in conjunction with star or mesh communication protocols. As a result, these systems are unable to identify the nearest operational smart meter within a cellular network, preventing them from effectively relaying data from non-cellular network meters to a functioning cellular meter.
[0011] In light of these challenges, there is an urgent need for an enhanced system and method for smart meters that improves communication capabilities and the overall efficiency of smart meter networks, particularly through the implementation of dual communication capabilities. Such improvements would not only address current limitations but also pave the way for a more resilient and responsive energy management infrastructure.
[0012] Further limitations and disadvantages of conventional and traditional approaches will become apparent to one of skill in the art, through the comparison of described systems with some aspects of the present disclosure, as set forth in the remainder of the present application and with reference to the drawings.
SUMMARY
[0013] This summary is provided to introduce concepts related to a method and system for communication on one or more devices, and the concepts are further described below in the detailed description. This summary is not intended to identify essential features of the claimed subject matter, nor is it intended for use in determining or limiting the scope of the claimed subject matter.
[0014] According to embodiments illustrated herein, there is provided a method for communication on one or more devices. In one implementation of the present disclosure, the method may involve identifying a condition of a primary communication interface of one or more devices. Each of the one or more devices comprises at least one of the primary communication interface, a secondary communication interface, and a combination thereof. Further, the method may involve categorizing the one or more devices into one or more device groups, based on the condition of the primary communication interface. The one or more device groups may comprise a connected device group and a disconnected device group. The connected device group comprises one or more first devices from the one or more devices, and the disconnected device group comprises one or more second devices from the one or more devices. Further, the method may involve connecting the one or more devices to the one or more second devices via the secondary communication interface.
[0015] According to embodiments illustrated herein, there is provided a system for communication on the one or more devices. In one implementation of the present disclosure, the system may include a processor and a memory communicatively coupled to the processor, which, upon execution, causes the processor to identify the condition of the primary communication interface of the one or more devices. Further, each of the one or more devices may comprise at least one of the primary communication interface, the secondary communication interface, and a combination thereof. Furthermore, the system may categorize the one or more devices into the one or more device groups, based on the condition of the primary communication interface. Furthermore, one or more device groups may comprise the connected device group and the disconnected device group. Furthermore, the connected device group may comprise the one or more first devices from the one or more devices, and the disconnected device group may comprise the one or more second devices from the one or more devices. Furthermore, the system may connect the one or more first devices to the one or more second devices via the secondary communication interface.
[0016] According to the embodiments illustrated herein, the non-transitory computer-readable medium storing computer-executable instructions for communication on the one or more devices is disclosed. The computer-executable instructions may be configured to, when executed by a processor, cause the processor to perform steps that may include identifying the condition of the primary communication interface of the one or more devices. Further, each of the one or more devices may comprise at least one of the primary communication interface, the secondary communication interface, and a combination thereof. Further steps may include categorizing the one or more devices into the one or more device groups, based on the condition of the primary communication interface. Further, the one or more device groups may comprise the connected device group and the disconnected device group. The connected device group may comprise the one or more first devices from the one or more devices, and the disconnected device group may comprise the one or more second devices from the one or more devices. Furthermore the step include, connecting the one or more first devices to the one or more second devices via the secondary communication interface.
[0017] 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 DESCRIPTION OF DRAWINGS
[0018] The accompanying drawings illustrate the various embodiments of systems, methods, and other aspects of the disclosure. Any person with ordinary skills in the art will appreciate that the illustrated element boundaries (e.g., boxes, groups of boxes, or other shapes) in the figures represent one example of the boundaries. In some examples, one element may be designed as multiple elements, or multiple elements may be designed as one element. In some examples, an element shown as an internal component of one element may be implemented as an external component in another, and vice versa. Further, the elements may not be drawn to scale.
[0019] Various embodiments will hereinafter be described in accordance with the appended drawings, which are provided to illustrate and not to limit the scope in any manner, wherein similar designations denote similar elements, and in which:
[0020] FIGURE. 1 is a block diagram that illustrates a system architecture (100) for communication on one or more devices (108), in accordance with an embodiment of the present disclosure.
[0021] FIGURE. 2 is a block diagram that illustrates an exemplary connection of the one or more devices (108) to a communication network (106), in accordance with an embodiment of the present disclosure.
[0022] FIGURE. 3 is a block diagram (300) that illustrates an exemplary downlink messaging functionality of the system (100) for communication on one or more devices (202), in accordance with an embodiment of the present disclosure.
[0023] FIGURE. 4 is a block diagram (400) that illustrates an exemplary uplink messaging functionality of the system (100) for communication on the one or more devices (202), in accordance with an embodiment of the present disclosure.
[0024] FIGURE. 5 is a flowchart that illustrates a method (500) for communication on the one or more devices (108), in accordance with an embodiment of the present disclosure.
[0025] FIGURE. 6 illustrates a block diagram (600) of an exemplary computer system for implementing embodiments consistent with the present disclosure.
DETAILED DESCRIPTION
[0026] The present disclosure may be best understood with reference to the detailed figures and description set forth herein. Various embodiments are discussed below with reference to the figures. However, those skilled in the art will readily appreciate that the detailed descriptions given herein with respect to the figures are simply for explanatory purposes, as the methods and systems may extend beyond the described embodiments. For example, the teachings presented\ and the needs of a particular application may yield multiple alternative and suitable approaches to implement the functionality of any detail described herein. Therefore, any approach may extend beyond the particular implementation choices in the following embodiments described and shown.
[0027] References to “one embodiment,” “at least one embodiment,” “an embodiment,” “one example,” “an example,” “for example,” and so on indicate that the embodiment(s) or example(s) may include a particular feature, structure, characteristic, property, element, or limitation but that not every embodiment or example necessarily includes that particular feature, structure, characteristic, property, element, or limitation. Further, repeated use of the phrase “in an embodiment” does not necessarily refer to the same embodiment.
[0028] An objective of the present disclosure is to enhance the reliability of smart meter networks by allowing communication through multiple channels, ensuring consistent data transfer even under challenging conditions.
[0029] Another objective of the present disclosure is to enable smart meters to identify the nearest operational meter(s) with a working primary communication channel, which facilitates efficient data routing in areas with poor cellular connectivity.
[0030] Yet another objective of the present disclosure is to promote energy efficiency by allowing smart meters to optimize data reporting based on real-time energy usage patterns.
[0031] Yet another objective of the present disclosure is to support the implementation of demand-response programs by providing utilities with timely and accurate data on energy consumption from smart meters.
[0032] Yet another objective of the present disclosure is to enable seamless integration of smart meters with existing smart grid technologies, enhancing the overall functionality of the energy distribution system.
[0033] Yet another objective of the present disclosure is to provide a cost-effective solution for enhancing communication capabilities in smart meters, reducing reliance on traditional cellular networks in areas with limited coverage.
[0034] Yet another objective of the present disclosure is to facilitate the expansion of smart meter networks by ensuring compatibility with various communication protocols, allowing for greater scalability.
[0035] Yet another objective of the present disclosure is to improve user experience by allowing consumers to access their energy usage data in real-time through reliable communication channels.
[0036] Yet another objective of the present disclosure is to integrate Bluetooth connectivity with star or mesh communication protocols in smart meters, leading to improved data transfer capabilities between the meters and remote servers.
[0037] Another objective of the present disclosure is to enhance the resilience of smart meter networks against communication failures, ensuring continuous operation and data integrity.
[0038] FIGURE. 1 is a block diagram that illustrates a system (100) for communication on one or more devices (108), in accordance with an embodiment of the present subject matter. The system environment (100) typically includes a memory (102), a processor (104), a communication network (106), and one or more portable devices (108). The memory (102), the processor (104), and the one or more portable devices (108) are typically communicatively coupled with each other via the communication network (106). In an embodiment, processing capability of the processor (104) may be implemented by an applications server (104) and the storage capability of the memory (102) may be implemented by a database server (102). Thus, the term “processor” and “application server” can be used interchangeably throughout this specification. Further, the term “memory” and “database server” can be used interchangeably throughout this specification. Further, the term “one or more devices” and “one or more portable devices” can be used interchangeably throughout this specification. In an embodiment, the application server (104) may communicate with the database server (102), and the one or more portable devices (108) using one or more protocols such as, but not limited to, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), RF mesh, Bluetooth Low Energy (BLE), and the like, to communicate with one another.
[0039] In an embodiment, the memory (102) may be configured to store, manage, and retrieve data associated with the one or more portable devices (108). The memory (102) may maintain information related to device identifiers, operational status, communication interface conditions, device group categorizations (such as connected device groups and disconnected device groups), and historical communication data. The memory (102) may also store routing tables, multi-hop communication paths, and other metadata necessary for enabling communication between devices through secondary communication interfaces when primary communication interfaces are non-functional. In some embodiments, the memory (102) may interact with the processor (104) to update device statuses in real-time and to facilitate efficient data transmission from the portable devices (108) to external systems, such as a meter data management (MDM) server or other backend applications.
[0040] In an embodiment, the memory (102) may be realized through various memory technologies such as, but not limited to, flash memory, solid-state drives (SSD), dynamic random-access memory (DRAM), static random-access memory (SRAM), read-only memory (ROM), or a combination thereof. In an embodiment, the memory (102) may be configured to utilize the processor (104) for processing, analyzing, and managing communication-related data received from the one or more portable devices (108).
[0041] A person with ordinary skills in art will understand that the scope of the disclosure is not limited to the memory (102) as a separate entity. In an embodiment, the functionalities of the memory (102) can be integrated into the processor (104) or into the one or more portable devices (108).
[0042] In an embodiment, the processor (104) may refer to a computing unit or a software framework configured to host and execute an application or software service. In an embodiment, the processor (104) may be implemented to execute procedures such as, but not limited to, programs, routines, or scripts stored in one or more memories (102) for supporting the hosted application or software service. The hosted application or software service may be configured to perform one or more predetermined operations. The processor (104) may be realized through various types of processing environments such as, but not limited to, Java Virtual Machine (JVM), .NET runtime, PHP runtime environment, embedded processors, or other computing architectures capable of managing communication services and operations.
[0043] In an embodiment, the processor (104) may be configured to utilize the memory (102) and the one or more portable devices (108), in conjunction, for securely managing communication operations based on the functional condition of the primary communication interface. In an implementation, the processor (104) may be configured to periodically monitor the primary communication interface of each of the one or more portable devices (108) and categorize the devices into a connected device group and a disconnected device group. The processor (104) may then facilitate the connection of one or more first devices from the connected device group to one or more second devices from the disconnected device group via the secondary communication interface, ensuring continuous communication even when the primary communication interface is non-functional. In an embodiment, the processor (104) may correspond to a communication management platform, which performs one or more communication operations based on the detected functionality conditions of the primary communication interfaces.
[0044] In an embodiment, the communication network (106) may correspond to a communication medium through which the application server (104), the database server (102), and the one or more portable devices (108) may communicate with each other. Such a communication may be performed in accordance with various wired and wireless communication protocols. Examples of such wired and wireless communication protocols include, but are not limited to, Transmission Control Protocol and Internet Protocol (TCP/IP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), Wireless Application Protocol (WAP), File Transfer Protocol (FTP), ZigBee, EDGE, infrared IR), IEEE 802.11, 802.16, 2G, 3G, 4G, 5G, 6G, 7G cellular communication protocols, and/or Bluetooth (BT) communication protocols. The communication network (106) may either be a dedicated network or a shared network. Further, the communication network (106) may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, and the like. The communication network (106) may include, but is not limited to, the Internet, intranet, a cloud network, a Wireless Fidelity (Wi-Fi) network, a Wireless Local Area Network (WLAN), a Local Area Network (LAN), a cable network, the wireless network, a telephone network (e.g., Analog, Digital, POTS, PSTN, ISDN, xDSL), a telephone line (POTS), a Metropolitan Area Network (MAN), an electronic positioning network, an X.25 network, an optical network (e.g., PON), a satellite network (e.g., VSAT), a packet-switched network, a circuit-switched network, a public network, a private network, and/or other wired or wireless communications network configured to carry data.
[0045] In an embodiment, the one or more portable devices (108) may refer to at least one of a computing device, one or more devices, one or more smart devices or a combination thereof. In another embodiment, the one or more portable devices (108) may be configured for communication with external networks or other devices. The one or more portable devices (108) may comprise one or more processors and one or more memory modules. The one or more memories may include computer-readable instructions that are executable by the processors to perform predetermined operations.
[0046] In an embodiment, the one or more portable devices (108) may be configured to identify a functionality condition of their primary communication interface. Based on the identified condition, the portable devices (108) may categorize themselves into a connected device group or a disconnected device group. The one or more portable devices (108) may also be configured to establish communication with other devices via the secondary communication interface when the primary communication interface is non-functional, ensuring continuous connectivity. In an implementation, the portable devices (108) may present a user interface for managing device connectivity and performing relevant communication operations, securely transmitting data between the connected and disconnected device groups. Examples of the one or more portable devices (108) may include, but are not limited to, a personal computer, a laptop, a personal digital assistant (PDA), a mobile device, a tablet, or any other computing device.
[0047] The system (100) can be implemented using hardware, software, or a combination of both, which may include utilizing one or more computer programs, mobile applications, or "apps" deployed either on-premises over corresponding computing terminals or virtually over cloud infrastructure. The system (100) may incorporate various micro-services or groups of independent computer programs, each capable of functioning autonomously while collaborating with other micro-services to achieve the overall functionality. The system (100) may also interface with third-party or external computer systems as necessary. Internally, the system (100) may serve as the central processor for handling communication operations between the various devices within the connected device group and the disconnected device group. A critical feature of the system (100) is its ability to securely perform one or more communication operations based on the functionality conditions of the primary communication interfaces, enabling continuous connectivity between devices. In a specific embodiment, the system (100) is implemented to ensure secure and efficient data transmission via the secondary communication interface when the primary communication interface is non-functional.
[0048] In one non-limiting embodiment of the present disclosure, a system for communication on one or more smart meters is disclosed. The system may include one or more smart meters connected to each other using either a star communication network protocol or a mesh communication network protocol. Further, each smart meter within the system may be equipped with a network interface card (NIC) featuring a dual communication channel/protocol. Furthermore, the dual communication channel/protocol may comprise a primary communication channel and a secondary communication channel. Furthermore, the primary communication channel may include a wireless network, including cellular or non-cellular networks. Additionally, the secondary communication channel may utilize another type of wireless network.
[0049] In an exemplary embodiment, the wireless network, including cellular or non-cellular networks may be of various type such as 2G, 3G, 4G LTE, 5G, Radio Frequency (RF) mesh, Narrowband Internet of Things (NB-IoT), Power Line Communication (PLC), GSM, Bluetooth, Bluetooth Low energy (BLE) or a combination thereof.
[0050] In an exemplary embodiment, particularly, the secondary communication interface may utilize wireless networks, such as Bluetooth or BLE SoC (System on Chip), RF, LoRa (Long Range) or a combination thereof. In an implementation, the star or mesh communication network of the one or more smart meters only includes the smart meters within the said network, without having a centralized hub for data transmission. Each smart meter within the mesh/star network, due to its dual communication capability, may either directly connect to a remote server or may be indirectly connected to the remote server via other smart meters on the said network. Moreover, one or more smart meters may communicate with each other using a secondary communication interface in combination with either the star communication network protocol or the mesh communication network protocol.
[0051] In one exemplary embodiment, the dual communication channel/protocol may be integrated either directly onto the network interface card (NIC) of each smart meter or may be enabled on a printed circuit board (PCB) of the smart meter. This implementation may ensure seamless communication capabilities, enhancing the efficiency and adaptability of the one or more smart meters, thereby ensuring continuous data transmission.
[0052] In another exemplary embodiment, one or more smart meters, connected in a star or mesh communication network, may communicate with each other using the secondary communication interface. More specifically, the smart meter with a non-functional primary communication interface may possess the capability to identify the nearest smart meter whose primary communication interface is working.
[0053] In yet another exemplary embodiment, one or more smart meters may communicate with the remote server either via the primary communication interface or the secondary communication interface, thereby ensuring uninterrupted data transmission. More particularly, for instance, if the smart meter’s primary communication interface is not functioning, then that smart meter may relay data, using the secondary communication interface to another smart meter having a working primary communication interface, connected over the mesh communication network. Another smart meter, with a primary communication interface, will send the relay data to the remote network using the primary communication interface.
[0054] In yet another exemplary embodiment, the system may enable one or more smart meters to communicate with the remote server either via the primary communication interface or the secondary communication interface, thereby ensuring uninterrupted data. Notably, in instances where a smart meter's primary communication interface is not working, the smart meter intelligently reroutes data through another meter with a functional primary communication interface, by using the secondary communication interface in combination with a mesh network. Thus, connecting one or more smart meters using the mesh network helps to overcome existing communication challenges, enhancing reliability and cost-effectiveness in remote monitoring and control applications.
[0055] Now referring to FIGURE 2, an exemplary connection of the one or more portable devices (108) to the communication network (106) is illustrated in accordance with an embodiment of the present subject matter. In one embodiment, the one or more portable devices (108) may include one or more devices (202) connected to the communication network (106) via at least one of a primary communication interface, a secondary communication interface, or a combination thereof. In one embodiment, the one or more portable devices (108) may include one or more devices (202) connected to the communication network (106) via a primary communication interface.
[0056] In an embodiment, the one or more devices (202) may correspond to a variety of utility meters, including, but not limited to, electricity meters, water meters, gas meters, hybrid meters, digital meters, prepaid meters, postpaid meters, as well as residential, commercial, and industrial meters. These one or more devices (202) may benefit from the disclosed dual-channel communication architecture to ensure uninterrupted data transmission in environments with unreliable or intermittent connectivity.
[0057] In one embodiment, the primary communication interface may comprise one of a cellular or non-cellular network, such as 2G, 3G, 4G LTE, 5G, Radio Frequency (RF) mesh, Narrowband Internet of Things (NB-Iot), Power Line Communication (PLC), GSM, or a combination thereof.
[0058] In an embodiment, identifying the condition of the primary communication interface of each of the one or more devices (202) may comprise determining at least one of an operational status, a signal strength, a connectivity status, or a combination thereof. The condition assessment may be performed using periodic diagnostic checks or continuous monitoring algorithms. Based on this assessment, the system (100) may categorize the devices into a connected device group or a disconnected device group. This categorization may occur periodically over a predefined time interval, such as every few seconds or minutes, depending on application requirements. Each of the one or more devices may comprise a network interface card (NIC), wherein the NIC may include both the primary communication interface and the secondary communication interface. In another embodiment, the primary communication interface may differ from the secondary communication interface in terms of communication protocol, frequency, or range. For instance, the primary interface may use a long-range protocol such as 4G, LTE, or RF mesh, while the secondary interface may employ Bluetooth or BLE for short-range, device-to-device communication.
[0059] In another embodiment, one or more devices (202) are connected to each other via the secondary communication interface. Another wireless communication network may comprise one of Bluetooth or BLE Soc (System on Chip), RF, LoRa (Long Range), Zigbee, Z-Wave, NFC, Wi-Fi Direct, Thread, RFID, infrared communication protocols, or a combination thereof.
[0060] In yet another embodiment, one or more devices (202), including M1, M2, M3, M4, M5, may be connected via the primary communication interface and/or the secondary communication interface. Further, one or more devices (202) (M1, M2, M3, M4, M5) may be connected with each other through a secondary communication interface if the primary communication interface is unavailable.
[0061] In an embodiment, the connection between the one or more first devices and the one or more second devices via the secondary communication interface may be achieved using either a star topology or a mesh topology. The selection of the topology may be based on factors such as device density, communication range, energy efficiency, and network resilience. In a star topology, the one or more second devices may communicate with a central first device acting as a relay to the application server or memory (102). In a mesh topology, each device may serve as both a transmitter and a receiver, allowing multi-hop communication wherein data is dynamically routed through intermediate devices until it reaches its destination. This flexibility in topology may enhance the robustness of communication, particularly in environments where the primary communication interface is degraded or unavailable.
[0062] In an embodiment, each of the one or more second devices may be configured to identify the nearest first device having a functional primary communication interface. This identification may be performed based on parameters such as signal strength, last known connectivity status, device proximity, or historical communication patterns. Upon identifying a suitable first device, the second device may initiate a connection via the secondary communication interface, such as Bluetooth or BLE, to relay its data to the remote system.
[0063] In an embodiment, the one or more devices (202) may dynamically switch between the primary communication interface and the secondary communication interface based on the detected condition of the primary communication interface. For instance, when the primary interface (e.g., cellular or RF mesh) is available and functional, a device may use it for direct data transmission. However, upon detection of a degraded or unavailable primary interface, the device may automatically switch to the secondary interface (e.g., BLE) to maintain communication continuity, either directly or via neighbouring devices.
[0064] In an embodiment, data from a second device of the one or more second devices may be communicated to a remote server through multi-hop routing. In such cases, the second device may transmit its data via the secondary communication interface to a first device that has a working primary communication interface. This first device may then forward the data to the remote server using its functional primary interface. The remote server may correspond to a meter data management (MDM) server or another backend system responsible for processing, analyzing, or storing the metering data.
[0065] In an exemplary embodiment, the one or more devices (202) M3 may have both primary and secondary communication interface working, and other one or more devices (202) M1, M2, M4, M5 may have a non-functional primary communication interface but a functional secondary communication interface. Here, the one or more devices (202) M1, M2, M4, M5 may be connected to each other (specifically with M3) via the secondary communication interface in combination with a mesh network and route the data to the nearby one or more devices (202) M3 with a working primary communication interface. The received data from one or more devices (202) M1, M2, M4, M5 may be routed further to the communication network (106), via one or more devices (202) M3 having the active primary communication interface.
[0066] In an exemplary embodiment, a system (100) for communication on one or more devices (202) may be deployed in a building basement where one or more devices (202) (e.g., smart meters) may primarily rely on a 4G communication protocol. Due to the location of the basement, the cellular connectivity may be weak, resulting in unreliable performance of the devices. To address this, the system may equip the devices with dual communication capabilities: a primary communication interface using cellular/RF mesh technology (e.g., 4G LTE) and a secondary communication interface using Bluetooth. Further, the system (100) may categorize the one or more devices (202) into two groups based on the condition of their primary communication interface. The one or more devices (202) with a functional primary communication interface (e.g., 4G LTE) may be categorized into the connected device group, while those with a non-functional primary communication interface may be categorized into the disconnected device group. In this embodiment, the one or more devices (202) may establish a communication network using their secondary communication interface. Further, when a device from the one or more devices (202) in the disconnected device group may lose its primary communication interface (e.g., 4G), the system (100) may automatically switch to the secondary communication interface. For example, if only a few one or more devices (202) (e.g., M1 and M5) may maintain a stable 4G connection while other one or more devices (202) (e.g., M2, M4) may struggle to maintain connectivity, the one or more devices (202) with a functional Bluetooth (e.g., M2 and M4) may relay data to a nearby one or more devices (202) with an operational primary communication interface (e.g., M3). The data may be transmitted through a secondary communication interface in a mesh or star topology, allowing the data to be routed from one device to another until it may reach the device with the active 4G connection. From there, the data may be transmitted to the communication network (106) or cloud server via the primary communication interface. In one embodiment, the system (100) may categorize the devices into the appropriate groups based on the status of the primary communication interface, enabling continuous communication even when the primary communication interface fails. This may ensure uninterrupted operation and reliable communication within the network.
[0067] In an exemplary embodiment, the remote server may be a cloud-based server, a head-end system (HES), a data center server, an application server, or a combination of these, depending on the system’s configuration.
[0068] Now referring to FIGURE 3, a block diagram (300) describing an exemplary downlink messaging functionality of the system (100) for communication on the one or more devices (202), is illustrated in accordance with an embodiment of the present subject matter.
[0069] Further, the flowchart (300) illustrates a database server (320) connected with the communication network (106). Further, an application server (322) may be connected to the one or more devices (202) via the wireless communication network (106). The wireless communication network may comprise one of a cellular or non-cellular network, such as 2G, 3G, 4G LTE, 5G, Radio Frequency (RF) mesh, Narrowband Internet of Things (NB-IoT), Power Line Communication (PLC), GSM, or a combination thereof. The exemplary downlink messaging functionality of the system (100) may initiate at step (302). At step (304), the system (100) may check for the availability of the network or historical network data for the one or more devices (202) connected to the application server (322) via the wireless network. If no network is found and no historical network data is available, then the downlink messaging on Bluetooth for the system (100) may be stopped at step (318). If no network is found but historical network data may be available, then the system (100) may search for the nearest one or more devices (202) which were sending data previously, at step (306).
[0070] At step (308), the system (100) may send the received data to a connected device (M1) among the one or more devices (202) for further forwarding to a target device out of the one or more devices (202). The one or more devices (202) may be connected to each other via Bluetooth mesh communication (310).
[0071] At step (312), the connected one or more devices (202) (M1) may attempt to connect with the target device over the BLE mesh communication network (310). If the connection is successfully established (314), a command may be sent by the connected device (M1) to the target device, and the BLE connection may be disconnected at step (316). If the BLE connection is not established, the downlink messaging on Bluetooth may be stopped at step (318).
[0072] Now referring to FIGURE 4, a block diagram (400) describing an exemplary uplink messaging functionality of the system (100) for communication on the one or more devices (202) is illustrated, in accordance with an embodiment of the present subject matter. The exemplary uplink messaging functionality of the system (100) may start at step (402).
[0073] Further, the flowchart (400) illustrates one or more devices (202) (e.g., M1, M2) connected via a wireless network. The wireless network may comprise one of Bluetooth or BLE SoC (System on Chip), RF, LoRa (Long Range) or a combination thereof.
[0074] At step (404), the system (100) may check if the one or more devices (202) are connected to the Network Interface Card (NIC). If a connection is not found, the system (100) may open Transparent TCP at step (406) (for the second meter) and continue further operations.
[0075] If the device is connected to the NIC, the system (100) may set a process to check for the network and update the BLE status at given intervals at step (408). If the network is found, the system (100) may proceed to open Transparent TCP at step (410). If the network is not found, the system (100) may enable waiting for the network at step (412).
[0076] Subsequently, at step (414), whether from the network wait or after setting BLE status, the system (100) may start a scheduler and a BLE advertiser.
[0077] At step (416), the system (100) may check if a schedule is found. If no schedule is found, the system (100) may restart advertisement after a waiting time at step (428).
[0078] If a schedule is found, the system (100) may check again for the network at step (420). If the network is detected, the system (100) may skip the schedule and process transparent operations at step (422).
[0079] If the network is not detected, the system (100) may stop advertising and start BLE scanning at step (418).
[0080] At step (424), the system (100) may filter devices based on Company ID and network status. If a device is found at step (426), the system (100) may connect to the target meter at step (432).
[0081] After connection, the system (100) may send DLMS data over BLE at step (430). Following the data transmission, the device may disconnect at step (434), and the system (100) may stop the scanner and start the advertiser at step (438). The collected data at the receiver meter may be sent via UDP at step (436). Further, eventually, the uplink messaging on Bluetooth star/mesh may be stopped at step (440).
[0082] Now, referring to FIGURE 5 is a flowchart that illustrates a method (500) for communication on one or more devices (108), in accordance with at least one embodiment of the present disclosure. The flowchart is described in conjunction with Figures 1 and 2. The method (500) starts at step (502) and proceeds to step (506).
[0083] In operation, the method (500) may involve a variety of steps for communication on one or more devices (202).
[0084] The method (500) for communication on one or more devices (202) may initiate at step (502), where the system (100) may identify a condition of a primary communication interface of the one or more devices (202). The primary communication interface may comprise at least one of a cellular interface, RF mesh, NB-IoT, PLC, or similar long-range communication protocols. The condition may include parameters such as signal strength, connectivity status, or network availability.
[0085] At step (504), based on the evaluated condition, the method (500) may categorize the one or more devices (202) into one or more device groups. The device groups may include a connected device group, comprising one or more first devices having a functional or available primary communication interface, and a disconnected device group, comprising one or more second devices having a non-functional or unavailable primary communication interface. The grouping may be updated dynamically as the network condition changes over time.
[0086] At step (506), the method (500) may establish communication between the connected device group and the disconnected device group using a secondary communication interface. The secondary communication interface may include Bluetooth, BLE SoC (System on Chip), Zigbee, RF, LoRa, or other short-range communication technologies. The one or more first devices may act as relay nodes and may forward data to or from the one or more second devices using a mesh or star topology formed via the secondary interface. This may allow the disconnected devices to maintain communication with backend systems such as a remote server (e.g., application server (322) or database server (320)) through the connected devices.
[0087] Let us delve into a detailed working example of the present disclosure.
Example 1:
[0088] In this working example, a smart metering system is deployed across a large urban residential complex consisting of multiple buildings with varying network conditions, such as basements, upper floors, and rooftop installations. Each building is equipped with smart meters for monitoring electricity consumption. Each smart meter is equipped with dual communication capabilities: a primary communication channel (such as LTE, RF mesh, or PLC) and a secondary communication channel (such as Bluetooth, BLE, or Zigbee).
[0089] Let’s consider a situation where the building has three smart meters: Smart Meter A, located in the basement; Smart Meter B, located on the ground floor; and Smart Meter C, installed on the rooftop.
Scenario 1: Primary Communication Failure in the Basement
[0090] Smart Meter A, installed in the basement, experiences signal disruption due to poor cellular reception in the underground area. Its primary communication channel, which operates on LTE, is unable to send meter readings to the remote server. As per the system design, Smart Meter A automatically switches to its secondary communication channel, which uses Bluetooth mesh.
[0091] Smart Meter A identifies Smart Meter B on the ground floor as the nearest operational smart meter with a working primary communication channel. Smart Meter A connects to Smart Meter B using its Bluetooth mesh connection and securely transmits its data (energy consumption readings) to Smart Meter B.
[0092] Since Smart Meter B has stable LTE connectivity, it acts as an intermediary and forwards the data received from Smart Meter A to the remote server via its primary communication channel. This data is processed by the server, ensuring that Smart Meter A’s readings are recorded, despite the basement’s limited connectivity.
Scenario 2: Bluetooth Mesh Communication for Data Routing
[0093] In another instance, Smart Meter C, installed on the rooftop, remains fully functional with a strong LTE connection. Both Smart Meter A (in the basement) and Smart Meter B (on the ground floor) experience intermittent primary communication failures. Smart Meter A and Smart Meter B are still able to communicate using the Bluetooth mesh network.
[0094] Smart Meter A first routes its data to Smart Meter B using Bluetooth mesh, and then, Smart Meter B passes this data, via the bluetooth further to Smart Meter C, which has an active LTE connection. Smart Meter C then transmits all data, including its own readings and the readings from Smart Meter A and Smart Meter B, to the remote server. The system ensures that even in a multi-hop scenario, data from smart meters with faulty primary channels can still be routed and delivered without any loss.
Scenario 3: Dual Communication Channel Integration
[0095] All smart meters in the system operate with both primary and secondary communication channels integrated on their network interface cards (NIC). The printed circuit board (PCB) within each smart meter is designed to seamlessly manage these dual channels. Whenever a primary communication channel fails, it switches to the secondary channel automatically, ensuring that there is no interruption in data transmission. This dual-channel setup allows the system to utilize a hybrid network topology, employing both mesh (via Bluetooth or BLE) and direct communication (via LTE or RF) for optimized data transmission.
[0096] For instance, if the primary LTE network of Smart Meter B is temporarily down, it will route its data through the Bluetooth mesh network to either Smart Meter A or Smart Meter C, whichever has an operational primary communication channel at that time. This flexibility allows the system to efficiently handle both small and large-scale disruptions in communication infrastructure.
[0097] In this detailed working example, the system demonstrates robust dual communication capabilities that ensure continuous, reliable data transmission from smart meters to remote servers, regardless of the environmental or network conditions. By leveraging both Bluetooth mesh and primary communication protocols, smart meters can maintain network connectivity, route data intelligently, and provide energy consumption data without interruptions. This enhances the resilience of the smart metering system, particularly in locations where traditional communication methods may fail.
Example 2:
[0098] In this working example, the present disclosure is applied to an industrial IoT (Internet of Things) sensor network deployed within a factory facility. Each IoT sensor device (202) is configured with a primary communication interface, such as a Narrowband Internet of Things (NB-IoT) module, and a secondary communication interface comprising a Bluetooth Low Energy (BLE) system.
[0099] During regular operation, each IoT sensor device (202) communicates directly with the application server (104) through the primary communication interface over the wireless communication network (106). However, certain areas within the factory, such as underground storage rooms or metal-dense production zones, experience poor NB-IoT coverage. In such cases, affected IoT sensor devices (202) are categorized into a disconnected device group due to the unavailability of the primary communication channel.
[00100] The system (100) dynamically forms a Bluetooth star or mesh network between disconnected device group members and nearby connected device group members which maintain active primary connectivity. For example, a humidity sensor (S1) and a temperature sensor (S2) lose NB-IoT signal inside an underground warehouse, while a vibration sensor (S3) near the stairwell retains stable connectivity. Through the secondary communication interface, the humidity sensor (S1) and temperature sensor (S2) route their collected data via the vibration sensor (S3), which acts as a relay node.
[00101] The vibration sensor (S3) forwards the uplink data over the primary NB-IoT communication channel to the application server (104), thereby ensuring continuous data availability. Furthermore, the application server (104) synchronizes all transmitted data to the database server (102) and updates the network topology, dynamically adjusting device groupings based on ongoing connectivity assessments.
[00102] Thus, the disclosed system (100) facilitates robust IoT sensor data communication even in challenging environments, using both primary and secondary communication interfaces intelligently.
[00103] A person skilled in the art will understand that the scope of the disclosure is not limited to scenarios based on the aforementioned factors and using the aforementioned techniques and that the examples provided do not limit the scope of the disclosure.
[00104] FIGURE. 6 illustrates a block diagram of an exemplary computer system (601) for implementing embodiments consistent with the present disclosure.
[00105] Variations of computer system (601) may be used for communication of the one or more devices (108). The computer system (601) may comprise a central processing unit (“CPU” or “processor”) (602). The processor (602) may comprise at least one data processor for executing program components for executing user- or system-generated requests. A user may include a person, a person using a device such as such as those included in this disclosure, or such a device itself. Additionally, the processor (602) 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, or the like. In various implementations the processor (602) 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, for example. Accordingly, the processor (602) 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), or Field Programmable Gate Arrays (FPGAs), for example.
[00106] Processor (602) may be disposed in communication with one or more input/output (I/O) devices via I/O interface (603). Accordingly, the I/O interface (603) 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, for example.
[00107] Using the I/O interface (603), the computer system (601) may communicate with one or more I/O devices. For example, the input device (604) 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, or visors, for example. Likewise, an output device (605) may be a user’s smartphone, tablet, cell phone, laptop, printer, fax machine, video display (e.g., cathode ray tube (CRT), liquid crystal display (LCD), light- emitting diode (LED), plasma, or the like), or audio speaker, for example. In some embodiments, a transceiver (606) may be disposed in connection with the processor (602). The transceiver (606) may facilitate various types of wireless transmission or reception. For example, the transceiver (606) may include an antenna operatively connected to a transceiver chip (example devices include the 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), and/or 2G/3G/5G/6G HSDPA/HSUPA communications, for example.
[00108] In some embodiments, the processor (602) may be disposed in communication with a communication network (608) via a network interface (607). The network interface (607) is adapted to communicate with the communication network (608). The network interface (607) may employ connection protocols including, without limitation, direct connect, Ethernet (e.g., twisted pair 10/100/1000 Base T), transmission control protocol/internet protocol (TCP/IP), token ring, or IEEE 802.11a/b/g/n/x, for example. The communication network (608) may include, without limitation, a direct interconnection, local area network (LAN), wide area network (WAN), wireless network (e.g., using Wireless Application Protocol), or the Internet, for example. Using the network interface (607) and the communication network (608), the computer system (601) may communicate with devices such as shown as a laptop (609) or a mobile/cellular phone (610). Other exemplary devices may include, without limitation, personal computer(s), server(s), fax machines, printers, scanners, various mobile devices such as cellular telephones, smartphones (e.g., Apple iPhone, Blackberry, Android-based phones, etc.), tablet computers, eBook readers (Amazon Kindle, Nook, etc.), laptop computers, notebooks, gaming consoles (Microsoft Xbox, Nintendo DS, Sony PlayStation, etc.), or the like. In some embodiments, the computer system (601) may itself embody one or more of these devices.
[00109] In some embodiments, the processor (602) may be disposed in communication with one or more memory devices (e.g., RAM 613, ROM 614, etc.) via a storage interface (612). The storage interface (612) 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, or solid-state drives, for example.
[00110] The memory devices may store a collection of program or database components, including, without limitation, an operating system (616), user interface application (617), web browser (618), mail client/server (619), user/application data (620) (e.g., any data variables or data records discussed in this disclosure) for example. The operating system (616) may facilitate resource management and operation of the computer system (601). 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.
[00111] The user interface (617) is for facilitating the 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 (601), such as cursors, icons, check boxes, menus, scrollers, windows, or widgets, for example. 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, or web interface libraries (e.g., ActiveX, Java, JavaScript, AJAX, HTML, Adobe Flash, etc.), for example.
[00112] In some embodiments, the computer system (601) may implement a web browser (618) stored program component. The web browser (618) may be a hypertext viewing application, such as Microsoft Internet Explorer, Google Chrome, Mozilla Firefox, Apple Safari, or Microsoft Edge, for example. Secure web browsing may be provided using HTTPS (secure hypertext transport protocol), secure sockets layer (SSL), Transport Layer Security (TLS), or the like. Web browsers may utilize facilities such as AJAX, DHTML, Adobe Flash, JavaScript, Java, or application programming interfaces (APIs), for example. In some embodiments the computer system (601) may implement a mail client/server (619) stored program component. The mail server (619) 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, or WebObjects, for example. The mail server (619) may utilize communication protocols such as internet message access protocol (IMAP), 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 (601) may implement a mail client (619) stored program component. The mail client (619) may be a mail viewing application, such as Apple Mail, Microsoft Entourage, Microsoft Outlook, or Mozilla Thunderbird.
[00113] In some embodiments, the computer system (601) may store user/application data (621), such as the data, variables, records, or the like as described in this disclosure. Such databases may be implemented as fault-tolerant, relational, scalable, secure databases such as Oracle or Sybase, for example. 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.
[00114] Furthermore, one or more computer-readable storage media may be utilized in implementing embodiments consistent with the present invention. 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., non-transitory. Examples include Random Access Memory (RAM), Read- Only Memory (ROM), volatile memory, nonvolatile memory, hard drives, Compact Disc (CD) ROMs, Digital Video Disc (DVDs), flash drives, disks, and any other known physical storage media.
[00115] Various embodiments of the disclosure encompass numerous advantages of a method and a system for communication on the one or more devices. The disclosed method and system have several technical advantages, but not limited to the following:
• Enhanced Communication Reliability: By incorporating dual communication channels and enabling communication between smart meters via a star/mesh communication protocol, the system enhances the reliability of communication within the smart meter network. This redundancy ensures that even if one communication channel fails, the system can seamlessly switch to the alternative channel, thereby reducing the risk of data loss or communication disruptions.
• Flexibility and Adaptability: The system supports a wide range of communication channels and protocols for both primary and secondary communication. This flexibility allows the smart meters to adapt to various network environments and conditions, ensuring optimal performance across different scenarios. Additionally, the ability to enable dual communication channels on the PCB of the smart meter enhances the system's scalability and ease of deployment.
• Efficient Data Routing: The system's capability to identify the nearest smart meter with a properly functioning primary communication channel enables efficient data routing. In cases where a smart meter's primary communication channel is unavailable, the system can intelligently route data through neighbouring meters with operational channels, ensuring timely and reliable transmission of data to the remote server.
• Redundancy and Failover Mechanism: With the option to communicate with the remote server via either the primary or secondary communication channel, the system establishes a redundancy and failover mechanism. This redundancy minimizes the risk of data loss or disruption by providing alternative communication pathways, thereby enhancing the overall robustness and resilience of the smart meter network.
• Cost-Effective Solution: By leveraging existing communication technologies such as Bluetooth or BLE for secondary communication, the system offers a cost-effective solution for enabling alternative communication for smart meters. This approach allows for efficient utilization of resources while still ensuring reliable communication capabilities within the network.
[00116] In summary, these technical advantages solve the technical problem of enabling reliable, efficient, and adaptive communication across diverse devices and networks. Additionally, these advantages contribute to enhancing system performance, reducing operational downtime, and optimizing network resource utilization, which leads to improved service delivery and better user experience across various applications, including smart metering, IoT systems, and other connected environments.
[00117] Furthermore, the invention involves a non-trivial combination of technologies and methodologies that provide a technical solution to a technical communication problem. While individual components such as wireless transceivers, communication protocols, processors, and authentication frameworks are well-known in the field of computer science and telecommunications, their integration into a unified system for enabling dynamic, dual-channel communication across multiple devices represents a significant improvement and technical advancement. This advancement improves the reliability, flexibility, and efficiency of communications in real-world operational settings, such as utility networks, industrial IoT platforms, and consumer device ecosystems.
[00118] The present disclosure may be realized in hardware, or a combination of hardware and software. The present disclosure may be realized in a centralized fashion, in at least one computer system, or in a distributed fashion, where different elements may be spread across several interconnected computer systems. A computer system or other apparatus adapted for carrying out the methods described herein may be suited. A combination of hardware and software may be a general-purpose computer system with a computer program that, when loaded and executed, may control the computer system such that it carries out the methods described herein. The present disclosure may be realized in hardware that comprises a portion of an integrated circuit that also performs other functions.
[00119] A person with ordinary skills in the art will appreciate that the systems, modules, and sub-modules have been illustrated and explained to serve as examples and should not be considered limiting in any manner. It will be further appreciated that the variants of the above disclosed system elements, modules, and other features and functions, or alternatives thereof, may be combined to create other different systems or applications.
[00120] Those skilled in the art will appreciate that any of the aforementioned steps and/or system modules may be suitably replaced, reordered, or removed, and additional steps and/or system modules may be inserted, depending on the needs of a particular application. In addition, the systems of the aforementioned embodiments may be implemented using a wide variety of suitable processes and system modules, and are not limited to any particular computer hardware, software, middleware, firmware, microcode, and the like. The claims can encompass embodiments for hardware and software, or a combination thereof.
[00121] While the present disclosure has been described with reference to certain embodiments, it will be understood by those skilled in the art that various changes may be made, and equivalents may be substituted without departing from the scope of the present disclosure. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the present disclosure without departing from its scope. Therefore, it is intended that the present disclosure is not limited to the particular embodiment disclosed, but that the present disclosure will include all embodiments falling within the scope of the appended claims.
[00108] In some embodiments, the processor (602) may be disposed in communication with a communication network (608) via a network interface (607). The network interface (607) is adapted to communicate with the communication network (608). The network interface (607) may employ connection protocols including, without limitation, direct connect, Ethernet (e.g., twisted pair 10/100/1000 Base T), transmission control protocol/internet protocol (TCP/IP), token ring, or IEEE 802.11a/b/g/n/x, for example. The communication network (608) may include, without limitation, a direct interconnection, local area network (LAN), wide area network (WAN), wireless network (e.g., using Wireless Application Protocol), or the Internet, for example. Using the network interface (607) and the communication network (608), the computer system (601) may communicate with devices such as shown as a laptop (609) or a mobile/cellular phone (610). Other exemplary devices may include, without limitation, personal computer(s), server(s), fax machines, printers, scanners, various mobile devices such as cellular telephones, smartphones (e.g., Apple iPhone, Blackberry, Android-based phones, etc.), tablet computers, eBook readers (Amazon Kindle, Nook, etc.), laptop computers, notebooks, gaming consoles (Microsoft Xbox, Nintendo DS, Sony PlayStation, etc.), or the like. In some embodiments, the computer system (601) may itself embody one or more of these devices.
[00109] In some embodiments, the processor (602) may be disposed in communication with one or more memory devices (e.g., RAM 613, ROM 614, etc.) via a storage interface (612). The storage interface (612) 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, or solid-state drives, for example.
[00110] The memory devices may store a collection of program or database components, including, without limitation, an operating system (616), user interface application (617), web browser (618), mail client/server (619), user/application data (620) (e.g., any data variables or data records discussed in this disclosure) for example. The operating system (616) may facilitate resource management and operation of the computer system (601). 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.
[00111] The user interface (617) is for facilitating the 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 (601), such as cursors, icons, check boxes, menus, scrollers, windows, or widgets, for example. 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, or web interface libraries (e.g., ActiveX, Java, JavaScript, AJAX, HTML, Adobe Flash, etc.), for example.
[00112] In some embodiments, the computer system (601) may implement a web browser (618) stored program component. The web browser (618) may be a hypertext viewing application, such as Microsoft Internet Explorer, Google Chrome, Mozilla Firefox, Apple Safari, or Microsoft Edge, for example. Secure web browsing may be provided using HTTPS (secure hypertext transport protocol), secure sockets layer (SSL), Transport Layer Security (TLS), or the like. Web browsers may utilize facilities such as AJAX, DHTML, Adobe Flash, JavaScript, Java, or application programming interfaces (APIs), for example. In some embodiments the computer system (601) may implement a mail client/server (619) stored program component. The mail server (619) 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, or WebObjects, for example. The mail server (619) may utilize communication protocols such as internet message access protocol (IMAP), 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 (601) may implement a mail client (619) stored program component. The mail client (619) may be a mail viewing application, such as Apple Mail, Microsoft Entourage, Microsoft Outlook, or Mozilla Thunderbird.
[00113] In some embodiments, the computer system (601) may store user/application data (621), such as the data, variables, records, or the like as described in this disclosure. Such databases may be implemented as fault-tolerant, relational, scalable, secure databases such as Oracle or Sybase, for example. 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.
[00114] Furthermore, one or more computer-readable storage media may be utilized in implementing embodiments consistent with the present invention. 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., non-transitory. Examples include Random Access Memory (RAM), Read- Only Memory (ROM), volatile memory, nonvolatile memory, hard drives, Compact Disc (CD) ROMs, Digital Video Disc (DVDs), flash drives, disks, and any other known physical storage media.
[00115] Various embodiments of the disclosure encompass numerous advantages of a method and a system for communication on the one or more devices. The disclosed method and system have several technical advantages, but not limited to the following:
• Enhanced Communication Reliability: By incorporating dual communication channels and enabling communication between smart meters via a star/mesh communication protocol, the system enhances the reliability of communication within the smart meter network. This redundancy ensures that even if one communication channel fails, the system can seamlessly switch to the alternative channel, thereby reducing the risk of data loss or communication disruptions.
• Flexibility and Adaptability: The system supports a wide range of communication channels and protocols for both primary and secondary communication. This flexibility allows the smart meters to adapt to various network environments and conditions, ensuring optimal performance across different scenarios. Additionally, the ability to enable dual communication channels on the PCB of the smart meter enhances the system's scalability and ease of deployment.
• Efficient Data Routing: The system's capability to identify the nearest smart meter with a properly functioning primary communication channel enables efficient data routing. In cases where a smart meter's primary communication channel is unavailable, the system can intelligently route data through neighbouring meters with operational channels, ensuring timely and reliable transmission of data to the remote server.
• Redundancy and Failover Mechanism: With the option to communicate with the remote server via either the primary or secondary communication channel, the system establishes a redundancy and failover mechanism. This redundancy minimizes the risk of data loss or disruption by providing alternative communication pathways, thereby enhancing the overall robustness and resilience of the smart meter network.
• Cost-Effective Solution: By leveraging existing communication technologies such as Bluetooth or BLE for secondary communication, the system offers a cost-effective solution for enabling alternative communication for smart meters. This approach allows for efficient utilization of resources while still ensuring reliable communication capabilities within the network.
[00116] In summary, these technical advantages solve the technical problem of enabling reliable, efficient, and adaptive communication across diverse devices and networks. Additionally, these advantages contribute to enhancing system performance, reducing operational downtime, and optimizing network resource utilization, which leads to improved service delivery and better user experience across various applications, including smart metering, IoT systems, and other connected environments.
[00117] Furthermore, the invention involves a non-trivial combination of technologies and methodologies that provide a technical solution to a technical communication problem. While individual components such as wireless transceivers, communication protocols, processors, and authentication frameworks are well-known in the field of computer science and telecommunications, their integration into a unified system for enabling dynamic, dual-channel communication across multiple devices represents a significant improvement and technical advancement. This advancement improves the reliability, flexibility, and efficiency of communications in real-world operational settings, such as utility networks, industrial IoT platforms, and consumer device ecosystems.
[00118] The present disclosure may be realized in hardware, or a combination of hardware and software. The present disclosure may be realized in a centralized fashion, in at least one computer system, or in a distributed fashion, where different elements may be spread across several interconnected computer systems. A computer system or other apparatus adapted for carrying out the methods described herein may be suited. A combination of hardware and software may be a general-purpose computer system with a computer program that, when loaded and executed, may control the computer system such that it carries out the methods described herein. The present disclosure may be realized in hardware that comprises a portion of an integrated circuit that also performs other functions.
[00119] A person with ordinary skills in the art will appreciate that the systems, modules, and sub-modules have been illustrated and explained to serve as examples and should not be considered limiting in any manner. It will be further appreciated that the variants of the above disclosed system elements, modules, and other features and functions, or alternatives thereof, may be combined to create other different systems or applications.
[00120] Those skilled in the art will appreciate that any of the aforementioned steps and/or system modules may be suitably replaced, reordered, or removed, and additional steps and/or system modules may be inserted, depending on the needs of a particular application. In addition, the systems of the aforementioned embodiments may be implemented using a wide variety of suitable processes and system modules, and are not limited to any particular computer hardware, software, middleware, firmware, microcode, and the like. The claims can encompass embodiments for hardware and software, or a combination thereof.
[00121] While the present disclosure has been described with reference to certain embodiments, it will be understood by those skilled in the art that various changes may be made, and equivalents may be substituted without departing from the scope of the present disclosure. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the present disclosure without departing from its scope. Therefore, it is intended that the present disclosure is not limited to the particular embodiment disclosed, but that the present disclosure will include all embodiments falling within the scope of the appended claims.
,CLAIMS:
WE CLAIM
1. A method (500) for communication on one or more devices (202), wherein the method (500) comprises:
identifying (502) a condition of a primary communication interface of the one or more devices (202),
wherein each of the one or more devices (202) comprises at least one of the primary communication interface, a secondary communication interface, and a combination thereof;
categorizing (504) the one or more devices (202) into one or more device groups, based on the condition of the primary communication interface,
wherein the one or more device groups comprise a connected device group and a disconnected device group, wherein the connected device group comprises one or more first devices from the one or more devices (202), and the disconnected device group comprises one or more second devices from the one or more devices (202); and
connecting (506) the one or more first devices to the one or more second devices via the secondary communication interface.
2. The method (500) as claimed in claim 1, wherein identifying (502) the condition of the primary communication interface comprises determining at least one of an operational status, a signal strength, a connectivity status, or a combination thereof, of the primary communication interface of each of the one or more devices (202).
3. The method (500) as claimed in claim 1, wherein categorizing (504) of the one or more devices (202) into the connected device group and the disconnected device group is performed periodically in a predefined time period through monitoring the condition of the primary communication interface, wherein each of the one or more devices comprises a network interface card (NIC), wherein the NIC of each device comprises the primary communication interface and the secondary communication interface, wherein the primary communication interface is different from the secondary communication interface.
4. The method (500) as claimed in claim 1, wherein the primary communication interface is selected from one of 2G, 3G, 4G LTE, 5G, radio frequency (RF) mesh, narrowband Internet of Things (NB-IoT), power line communication (PLC), GSM, cellular communication technologies, or a combination thereof.
5. The method (500) as claimed in claim 1, wherein the secondary communication interface is selected from one of Bluetooth, Bluetooth Low Energy (BLE), Zigbee, Z-Wave, NFC, Wi-Fi Direct, Thread, RFID, infrared communication protocols, or a combination thereof.
6. The method (500) as claimed in claim 1, wherein the connecting (504) the one or more first devices to the one or more second devices via the secondary communication interface corresponds to utilizing either a star topology or a mesh topology, of the secondary communication interface among the one or more first devices and the one or more second devices.
7. The method (500) as claimed in claim 1, wherein each of the one or more second devices identify a nearest first device having a functional primary communication interface, to connect via the secondary communication interface.
8. The method (500) as claimed in claim 1, wherein the one or more devices (202) dynamically switch between the primary communication interface and the secondary communication interface for connecting with each other, based on the condition of the primary communication interface of the one or more devices (202).
9. The method (500) as claimed in claim 1, comprises communicating data from a second device of the one or more second devices, to a remote server via a multi-hop routing of transmitting the data from the second device to a first device of the one or more first devices via the secondary communication interface and then transmitting the data from the first device to the remote server via the primary communication interface of the first device, wherein the remote server corresponds to a meter data management (MDM) server.
10. The method (500) as claimed in claim 1, wherein the one or more devices (202) corresponds to one of a utility meter, electricity meter, gas meter, water meter, hybrid meters, digital meter, prepaid meter, postpaid meter, residential meter, commercial meter, industrial meter and a combination thereof.
11. A system (200) for communication on one or more devices (202), wherein the system (200) comprises:
a processor (104); and
a memory (102) communicatively coupled to the processor (104), wherein the memory (102) stores processor executable instructions, which, on execution, cause the processor (104) to:
identify (502) a condition of a primary communication interface of the one or more devices (202),
wherein each of the one or more devices (202) comprises at least one of the primary communication interface, a secondary communication interface, and a combination thereof;
categorize (504) the one or more devices (202) into one or more device groups, based on the condition of the primary communication interface,
wherein the one or more device groups comprise a connected device group and a disconnected device group, wherein the connected device group comprises one or more first devices from the one or more devices (202), and the disconnected device group comprises one or more second devices from the one or more devices (202); and
connect (506) the one or more first devices to the one or more second devices via the secondary communication interface.

12. A non-transitory computer-readable storage medium having stored thereon, a set of computer-executable instructions causing a computer comprising one or more processors to perform steps comprising:
identifying (502) a condition of a primary communication interface of the one or more devices (202),
wherein each of the one or more devices (202) comprises at least one of the primary communication interface, a secondary communication interface, and a combination thereof;
categorizing (504) the one or more devices (202) into one or more device groups, based on the condition of the primary communication interface,
wherein the one or more device groups comprise a connected device group and a disconnected device group, wherein the connected device group comprises one or more first devices from the one or more devices (202), and the disconnected device group comprises one or more second devices from the one or more devices (202); and
connecting (506) the one or more first devices to the one or more second devices via the secondary communication interface.

Dated this 08th Day of May 2025

ABHIJEET GIDDE
IN/PA- 4407
AGENT FOR THE APPLICANT