Sign In to Follow Application
View All Documents & Correspondence

Iot Based System And Method For Monitoring And Controlling A Utility Meter

Abstract: IOT BASED SYSTEM AND METHOD FOR MONITORING AND CONTROLLING A UTILITY METER Exemplary embodiments of the present disclosure are directed towards an IOT based system, comprising: a smart meter comprising a IOT device configured to identify and capture utility parameters consumed by utility meters, the IOT device comprising a sensing module configured to transmit the captured utility parameters to a data concentrator unit via a network, the data concentrator unit configured to manage and control the one or more utility meters through the IOT device over the network; and a computing device configured to transmit utility service commands to the IOT device through the network, the utility service commands transmitted in response to the utility parameters and the IOT device comprising ports configured to connect to the utility meters and a network interface controller, the network interface controller configured to facilitate a communication between the utility meter and the at least one computing device. FIG. 1

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
08 December 2018
Publication Number
24/2020
Publication Type
INA
Invention Field
ELECTRICAL
Status
Email
naresh@prometheusip.com
Parent Application
Patent Number
Legal Status
Grant Date
2025-02-05
Renewal Date

Applicants

WINAMR SYSTEMS PRIVATE LIMITED
# 209, Myhome Tycoon, Begumpet, Hyderabad

Inventors

1. NAGA RAJA SRINIVASA NARASIMHA MURTHY AMBADIPUDI
Plot No. 83, 24-3/83, Vimala Devi Nagar, Malkajgiri, Hyderabad–500 047
2. THIRUPATHI RAO JALAGAM
H.No. 6-3-1099/1/2/3, Flat No. 310, Bhavyas Varun Sargam Villa, Somajiguda, Hyderabad–82

Specification

DESC:The present disclosure is a complete specification for the provisional application number: 201841038046, titled IOT BASED SYSTEM AND METHOD FOR MONITORING AND CONTROLLING A UTILITY METER; filed on: 08.10.2018.

TECHNICAL FIELD
[001] The disclosed subject matter relates generally to the field of IOT based utility meters. More particularly, the present disclosure relates to a system and method for monitoring, reporting, and controlling a utility meter from a computing device.

BACKGROUND
[002] Conventionally, the utility providers sent a technician on a periodic basis to verify the utility meter operation and to record the utility consumption for billing purposes. This is an expensive and time-consuming method of reading meters, particularly as the customer is often not at home at the time of the visit. Nowadays, a large number of utility meters are in use for reading the utility consumption. For example, most of the utility meters use optical light-sensing arrangements to provide remote utility readings for determining utility consumption and billing purposes. These utility meters avoid having a technician walk or drive from establishment to establishment and manual recording of the utility use. The majority of methods using optical light-sensing devices inside the existing utility meters and/or require professional installation. Thus, a trained individual must physically remove the glass housing present on such a utility meter in order to install the automatic reading device. This process is inefficient and also very costly for either the utility company or the consumer. The drawbacks that are inherent in these systems are that customers cannot see their utility use in real-time, cannot access this information except when a billing statement is received and, cannot see data except in the standard format chosen by the utility service provider.

[003] In order to overcome the drawbacks of the prior art, the present invention provides an IOT based system for monitoring and controlling the utility meter periodically.

[004] In the light of the aforementioned discussion, there exists a need for a certain system with novel methodologies that would overcome the above-mentioned disadvantages.

SUMMARY
[005] The following presents a simplified summary of the disclosure in order to provide a basic understanding of the reader. This summary is not an extensive overview of the disclosure and it does not identify key/critical elements of the invention or delineate the scope of the invention. Its sole purpose is to present some concepts disclosed herein in a simplified form as a prelude to the more detailed description that is presented later.

[006] An objective of the present disclosure is directed towards monitoring and controlling the tamper attempts remotely.

[007] Another objective of the present disclosure is directed towards monitoring the quality of utility supply.

[008] Another objective of the present disclosure is directed towards transmitting the tampering alerts with date and timestamp to a utility service provider’s device and to an end-user’s device via a network.
[009] Another objective of the present disclosure is directed towards controlling the smart meter by triggering the utility service commands from the computing device based on the received utility parameters through the data concentrator unit.

[0010] In an embodiment of the present disclosure, a system and method for monitoring, reporting and controlling a utility meter from a computing device.

[0011] According to an exemplary aspect, the method comprising a step of providing the utility services by the utility service provider to the end user.

[0012] According to another exemplary aspect, the method comprising a step of enabling a smart meter to identify and capture utility parameters of the utility services.

[0013] According to another exemplary aspect, the method further comprising a step of transferring the utility parameters to the data concentrator unit via the network from the smart meter.

[0014] According to another exemplary aspect, the method further comprising a step of receiving the utility parameters by the computing device from the data concentrator unit. Analyzing the utility parameters of the particular smart meter by the computing device.

[0015] According to another exemplary aspect, the method further comprising a step of managing and controlling the smart meter by the computing device through the data concentrator unit.

[0016] According to another exemplary aspect, the method further comprising a step of storing the utility parameters in the central database and generating the alerts to the end user device.

[0017] According to an exemplary aspect, the system comprising, a smart meter comprising a IOT device configured to identify and capture one or more utility parameters consumed by one or more utility meters.

[0018] According to another exemplary aspect, the IOT device comprising a sensing module configured to transmit the one or more captured utility parameters to a data concentrator unit via a network, the data concentrator unit configured to manage and control the one or more utility meters through the IOT device over the network.

[0019] According to another exemplary aspect, at least one computing device configured to transmit one or more utility service commands to the IOT device through the network.

[0020] According to another exemplary aspect, the one or more utility service commands transmitted in response to the one or more utility parameters and the IOT device comprising at least two ports configured to connect to the one or more utility meters and a network interface controller.

[0021] According to another exemplary aspect, the network interface controller configured to facilitate a communication between the utility meter and the at least one computing device.

BRIEF DESCRIPTION OF THE DRAWINGS
[0022] Figure 1 is a block diagram depicting a schematic representation of an IOT based system for monitoring, reporting and controlling a utility meter, in accordance with one or more embodiments.

[0023] Figure 2 is a block diagram depicting a schematic representation of the IOT device 106 as shown in FIG. 1, in accordance with one or more embodiments.

[0024] FIG. 3 is a flowchart depicting a method for monitoring and controlling a utility meter, according to one or more embodiments.

[0025] FIG. 4 is a flowchart depicting a method for reporting and controlling the utility meter, according to one or more embodiments.

[0026] FIG. 5 is a block diagram illustrating the details of a digital processing system in which various aspects of the present disclosure are operative by execution of appropriate software instructions.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS
[0027] It is to be understood that the present disclosure is not limited in its application to the details of construction and the arrangement of components set forth in the following description or illustrated in the drawings. The present disclosure is capable of other embodiments and of being practiced or of being carried out in various ways. Also, it is to be understood that the phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting.

[0028] The use of “including”, “comprising” or “having” and variations thereof herein is meant to encompass the items listed thereafter and equivalents thereof as well as additional items. The terms “a” and “an” herein do not denote a limitation of quantity, but rather denote the presence of at least one of the referenced item. Further, the use of terms “first”, “second”, and “third”, and the like, herein do not denote any order, quantity, or importance, but rather are used to distinguish one element from another.

[0029] Referring to FIG. 1 is a block diagram 100 depicting an example environment in accordance with one or more embodiments. Specifically, FIG. 1 depicting a schematic representation of an IOT based system for monitoring, reporting and controlling a utility meter, in accordance with one or more embodiments. The system 100 depicting a smart meter 102, a data concentrator unit 104, a network 110, a utility service provider 112, a central database 114, a computing device 116, an end-user device 120, and a sensing module 122. The smart meter 102 may be integrated with an IOT device 106 and a utility meter 108. For example, the smart meter 102 provided by the utility service provider 112 is integrated with intelligent remote interface software standards. The utility meter 108 may include, but not limited to, an electricity meter, a water meter, a heat meter, a gas meter, and the like. In another embodiment, the IOT device 106 may be connected externally to the utility meter 108. The IOT device 106 comprising two ports, one is to connect to an optical port of the utility meter 108 and the other is to connect to a network interface controller 118. The network interface controller 118 may facilitate communication between the utility meter 108 and the cloud (the data concentrator unit 104, a utility service provider 112, the central database 114 and the computing device 116) via the network 110. The network 110 may include, but is not limited to, an Internet of things (IOT network devices), an Ethernet, a wireless local area network (WLAN), or a wide area network (WAN), a Bluetooth low energy network, a ZigBee network, a WIFI communication network e.g., the wireless high speed internet, or a combination of networks, a cellular service such as a 4G (e.g., LTE, mobile WiMAX) or 5G cellular data service, a RFID module, a NFC module, wired cables and the like without limiting the scope of the present disclosure. The utility service provider 112 may provide the utility services to the end-users. The utility services may include, but not limited to, electricity generation, electricity retailing, electricity supplies, natural gas supplies, water supplies, sewage works, sewage systems, broadband internet services, and the like. The computing device 116 and end-user device 120 may include, but not limited to, a personal digital assistant, a smart phone, a personal computer, a mobile station, computing tablets, a handheld device, an internet enabled calling device, an internet enabled calling software, a telephone, a mobile phone, a digital processing system, and the like. The end user may include but not limited to, a consumer, a customer, a user, an operator, an industrialist, a service provider, and the like.

[0030] The IOT device 106 includes a sensing module 122 configured to sense the utility parameters delivered to the utility meter 108. The sensing module 122 may also be configured to derive the power consumption and energy used by the utility meter 108 connected with the IOT device 106. The smart meter 102 may be configured to identify and capture the utility parameters consumed by the utility meter 108. The smart meter 102 may also be configured to transmit the captured utility parameters to the data concentrator unit 104 via the network 110. The utility parameters may include, but not limited to, load profile, power quality data, time/date stamp, the smart meter serial number, voltage, current, digital certificates, serial or tracking ID's, which could include geographic location such as longitude and latitude, volts, amps, Watts, phase relationships between waveforms, kWh, kvAr, power factor, frequency, and the like. The smart meter 102 may be operated both in credit or prepaid mode. The prepaid mode may be programmed with relevant slabs & tariffs, recharger credits, and low balance alerts. The load balance alerts, for example, load exceeded beyond the allowed value, as per end user’s opted demand response (DR) program, and credit points are exhausted (prepaid mode). The smart meter 102 may be supplied form factor in 1Ø / 3Ø configuration. The IOT device 106 may be attached to the utility meters 108 existing in the field. In an embodiment, the smart meter 102 may be developed with open software standards. To these smart meters 102, data transceiver and data concentrator is possible and the computing device 116 may communicate in respective formats. The data concentrator unit 104 may be configured to manage and control the utility meter 102 through the IOT device 106 over the network 110. In another embodiment, the smart meter 102 is a normal digital meter having standard outputs (RS-232 or USB, for e.g.). From these outputs data transceiver may collect the utility parameters through the optical port and transmit the utility parameters to the data concentrator unit 104 as per the protocol which is given by the utility service provider 112. The data concentrator unit 104 may act as an interface between the smart meter 102 and the computing device 116. The data concentrator unit 104 may also be configured to record the utility parameters supplied by the utility service provider 112 to the end-user. For example, the data concentrator unit 104 may perform many operations like, handling both long range and short communications, and maintains a group of smart meters and their utility parameters periodically. The below table depicting the specifications of the smart meter 102,
VALUE PARAMETER

Working Voltage 80 to 260 VAC
Working Current 5 to 30 Amps (1ø) , 10 to 60 Amps (3ø)
Burden 4 Watts (with 2G modem)
Operating Frequency 45 to 65Hz
Measurement Accuracy 1.0
Single/Three Phase measurement Unit IS13779, IS14697
Load Switch IS15884 (UC2/UC3)
Safety ISI mark/ IEC61010-1
Ingress Protection : IEC 60529 (IP51)
Relative Humidity 0 to 96 %
Temperature Operation range
10 Deg C to 55 Deg C

[0031] The computing device 116 may be programmed with software applications. The software applications may be a middleware engine or a layer of software between the advanced metering infrastructures (AMI) network and advanced metering management (AMM) applications like Utility Billing, CRM, Demand Response, etc. The utility service may also execute services such as identification, authentication, authorization, demand response, load profiling, customer profiling, TOU/TOD, and the like within the network 110. The central database 114 may include a utility parameters management system. The central database 114 may be configured to store the utility parameters captured by the smart meter 102. The central database 114 may also be configured to manage the utility services provided by the utility service provider 112. The central database 114 may process the utility parameters and generates alerts to the end-users. The alerts may include but not limited to, SMS or e-mail alters, notifications, alarms, warnings, and the like. The computing device 116 may be configured to monitor the utility parameters received by the data concentrator unit 104. The computing device 116 may also be configured to manage and control the utility meter 108 by transmitting the utility service commands based on the monitored utility parameters via the network 110. The utility service commands may include but not limited to, activate the utility service, deactivate the utility service, disconnect the power, connect the power, and the like. The smart meter 102 may read the utility meter 108 data through its optical port (IEC 61107, for e.g.). Utility service provider 112 need to share the utility meter 108 in this case. Otherwise, the IOT device 106 may sense the line voltage and current and derive the required utility parameters in sync with the utility meter 108. IOT based system 100 further comprising utility seals may be added at appropriate places by the utility service provider 112. The smart meter 102 may support up to programmable Time of Use (TOU) registers (for e.g. four registers). The smart meter 102 may be used in prepayment option also to disconnect the end user (consumer, for e.g.) power based on a command from the CLOUD which has the prepayment module. The smart meter 102 may support a load switch to disconnect the end user (consumer, for e.g.) load from the cloud-based on various utility parameters monitored by utility meter 108.

[0032] Referring to FIG. 2 is a block diagram 200 depicting the IOT device 106 shown in FIG. 1, in accordance with one or more exemplary embodiments. The IOT device 106 depicting a bus 202, a communication module 204, and LPRF communication module 206, a memory 208, and a data transceiver 210. The bus 202 may include a path that permits communication among the components of the IOT device 106. The communication module 204 may be configured to allow the two-way communication between the smart meter 102 and the data concentrator unit 104 to control the voltage and current delivered to the utility meter 108. The communication module 204 may include, but not limited to, subscriber identity modules (GSM LTE, GSM 2G), analog cell systems, digital cell systems, Ethernet, short-range radio wireless, ZigBee, power line carrier, Hybrid-Fiber Coax, RF, WiFi, and WiMax. The LPRF communication module 206 may be allowed to communicate within short-range radio connections. The LPRF communication module 206 may also be called Bluetooth technology. The data transceiver 210 may be configured to collect the utility parameters from the utility meter 108 and transmits the collected utility parameters to the data concentrator unit 104 via the network 110. The memory 208 may be configured to store latest events.

[0033] Referring to FIG. 3 is a flowchart 300 depicting a method for managing and controlling the smart meter, according to some embodiments. As an option, the method 300 is carried out in the context of the details of FIG. 1, and FIG. 2. However, the method 300 is carried out in any desired environment. Further, the aforementioned definitions are equally applied to the description below.

[0034] The exemplary method 300 commences at step 302, providing the utility services by the utility service provider to the end user. Thereafter, at step 304, enabling a smart meter to identify and capture utility parameters of the utility services. Thereafter, at step 306, transferring the utility parameters to the data concentrator unit via the network from the smart meter. Thereafter, at step 308, receiving the utility parameters by the computing device from the data concentrator unit. Thereafter, at step 310, analyzing the utility parameters of the particular smart meter by the computing device. Thereafter, at step 312, managing and controlling the smart meter by the computing device through the data concentrator unit. Thereafter, at step 314, storing the utility parameters in the central database and generating the alerts to the end user device.

[0035] Referring to FIG. 4 is a flowchart 400 depicting a method for sending the low balance information alerts to the end user device, according to some embodiments. As an option, the method 400 is carried out in the context of the details of FIG. 1, FIG. 2, and FIG. 3. However, the method 400 is carried out in any desired environment. Further, the aforementioned definitions are equally applied to the description below.

[0036] The exemplary method 400 commences at step 402, determining whether the smart meter gets fewer credits regarding a low payment balance associated with that end user destination. The end user destination may include residential as well as commercial and industrial consumer needs. If the answer to the step 402 is NO, then the method continues at step 404, identifying and capturing utility parameters of the utility service by the smart meter. If the answer to the step 402 is YES, then the method continues at step 406, generating low balance alerts by the smart meter and transmitting the generated alerts to the central database through the computing device. Thereafter, at step 408, processing the low balance alerts by the central database and sending the low balance information alerts to the end user device. Thereafter, at step 410, performing payment transactions by the end user for the meter credits through any payment gateways.

[0037] Referring to FIG. 5 is a block diagram 500 illustrating the details of a digital processing system 500 in which various aspects of the present disclosure are operative by execution of appropriate software instructions. The Digital processing system 500 may correspond to the computing device 116 (or any other system in which the various features disclosed above can be implemented).

[0038] Digital processing system 500 may contain one or more processors such as a central processing unit (CPU) 510, random access memory (RAM) 520, secondary memory 530, graphics controller 560, display unit 570, network interface 580, and input interface 590. All the components except display unit 570 may communicate with each other over communication path 550, which may contain several buses as is well known in the relevant arts. The components of Figure 5 are described below in further detail.

[0039] CPU 510 may execute instructions stored in RAM 520 to provide several features of the present disclosure. CPU 510 may contain multiple processing units, with each processing unit potentially being designed for a specific task. Alternatively, CPU 510 may contain only a single general-purpose processing unit.

[0040] RAM 520 may receive instructions from secondary memory 530 using communication path 550. RAM 520 is shown currently containing software instructions, such as those used in threads and stacks, constituting shared environment 525 and/or user programs 526. Shared environment 525 includes operating systems, device drivers, virtual machines, etc., which provide a (common) run time environment for execution of user programs 526.

[0041] Graphics controller 560 generates display signals (e.g., in RGB format) to display unit 570 based on data/instructions received from CPU 510. Display unit 570 contains a display screen to display the images defined by the display signals. Input interface 590 may correspond to a keyboard and a pointing device (e.g., touch-pad, mouse) and may be used to provide inputs. Network interface 580 provides connectivity to a network (e.g., using Internet Protocol), and may be used to communicate with other systems (such as those shown in Figure 1) connected to the network 110.

[0042] Secondary memory 530 may contain hard drive 535, flash memory 536, and removable storage drive 537. Secondary memory 530 may store the data software instructions (e.g., for performing the actions noted above with respect to the Figures), which enable digital processing system 500 to provide several features in accordance with the present disclosure.

[0043] Some or all of the data and instructions may be provided on removable storage unit 540, and the data and instructions may be read and provided by removable storage drive 537 to CPU 510. Floppy drive, magnetic tape drive, CD-ROM drive, DVD Drive, Flash memory, removable memory chip (PCMCIA Card, EEPROM) are examples of such removable storage drive 537.

[0044] Removable storage unit 540 may be implemented using medium and storage format compatible with removable storage drive 537 such that removable storage drive 537 can read the data and instructions. Thus, removable storage unit 540 includes a computer readable (storage) medium having stored therein computer software and/or data. However, the computer (or machine, in general) readable medium can be in other forms (e.g., non-removable, random access, etc.).

[0045] In this document, the term "computer program product" is used to generally refer to removable storage unit 540 or hard disk installed in hard drive 535. These computer program products are means for providing software to digital processing system 500. CPU 510 may retrieve the software instructions, and execute the instructions to provide various features of the present disclosure described above.

[0046] The term “storage media/medium” as used herein refers to any non-transitory media that store data and/or instructions that cause a machine to operate in a specific fashion. Such storage media may comprise non-volatile media and/or volatile media. Non-volatile media includes, for example, optical disks, magnetic disks, or solid-state drives, such as storage memory 530. Volatile media includes dynamic memory, such as RAM 530. Common forms of storage media include, for example, a floppy disk, a flexible disk, hard disk, solid-state drive, magnetic tape, or any other magnetic data storage medium, a CD-ROM, any other optical data storage medium, any physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, NVRAM, any other memory chip or cartridge.

[0047] Storage media is distinct from but may be used in conjunction with transmission media. Transmission media participates in transferring information between storage media. For example, transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus 550. Transmission media can also take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications.

[0048] More illustrative information will now be set forth regarding various optional architectures and uses in which the foregoing method may or may not be implemented, as per the desires of the auto system/user. It should be strongly noted that the following information is set forth for illustrative purposes and should not be construed as limiting in any manner. Any of the following features may be optionally incorporated with or without the exclusion of other features described.

[0049] Furthermore, the described features, structures, or characteristics of the disclosure may be combined in any suitable manner in one or more embodiments. In the above description, numerous specific details are provided such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments of the disclosure.

[0050] Although the present disclosure has been described in terms of certain preferred embodiments and illustrations thereof, other embodiments and modifications to preferred embodiments may be possible that are within the principles and spirit of the invention. The above descriptions and figures are therefore to be regarded as illustrative and not restrictive.

[0051] Thus the scope of the present disclosure is defined by the appended claims and includes both combinations and sub-combinations of the various features described here in above as well as variations and modifications thereof, which would occur to persons skilled in the art upon reading the foregoing description. ,CLAIMS:We claim:

1. An IOT based system, comprising:

a smart meter comprising a IOT device configured to identify and capture one or more utility parameters consumed by one or more utility meters, whereby the IOT device comprising a sensing module configured to transmit the one or more captured utility parameters to a data concentrator unit via a network, the data concentrator unit configured to manage and control the one or more utility meters through the IOT device over the network; and

at least one computing device configured to transmit one or more utility service commands to the IOT device through the network, whereby the one or more utility service commands transmitted in response to the one or more utility parameters and the IOT device comprising at least two ports configured to connect to the one or more utility meters and a network interface controller, whereby the network interface controller configured to facilitate a communication between the utility meter and the at least one computing device.

2. The IOT based system of claim 1, wherein the sensing module is configured to derive a power consumption and an energy utilization of the utility meter.

3. The IOT based system of claim 1, wherein the data concentrator unit is configured to act as an interface between the smart meter and the at least one computing device.

4. The IOT based system of claim 1, wherein the data concentrator unit is also configured to record the one or more utility parameters.

5. The IOT based system of claim 1, wherein the at least one computing device is configured to receive the one or more utility parameters from a service provider’s device.

6. The IOT based system of claim 1, wherein the IOT device comprising a communication module configured to allow the two-way communication between the smart meter and the data concentrator unit.

7. The IOT based system of claim 1, wherein the IOT device comprising a LPRF communication module is allowed to communicate within short-range radio connections.

8. The IOT based system of claim 1, wherein the IOT device comprising a data transceiver configured to collect the one or more utility parameters from the utility meter and transmits the collected utility parameters to the data concentrator unit via the network.

9. A method for managing and controlling a smart meter, comprising:

providing one or more utility services of one or more utility meters to an end-user from a utility service provider;

enabling a smart meter comprising a IOT device configured to identify and capture one or more utility parameters of the one or more utility meters, whereby the IOT device comprising a sensing module configured to transmit the one or more captured utility parameters to a data concentrator unit via a network, the data concentrator unit configured to manage and control the one or more utility meters through the IOT device over the network;

receiving the one or more utility parameters to a computing device from the data concentrator unit;

analyzing the one or more utility parameters of the one or more smart meters on the computing device, whereby the computing device configured to transmit one or more utility service commands to the IOT device through a network;

managing and controlling the one or more smart meter on the computing device through the data concentrator unit; and

storing the one or more utility parameters in a central database and generating the alerts to an end user device.

10. The method of claim 9, further comprising a step of facilitating a communication between the one or more utility meters and the at least one computing device through a network interface controller.

Documents

Application Documents

# Name Date
1 201841038046-STATEMENT OF UNDERTAKING (FORM 3) [08-10-2018(online)].pdf 2018-10-08
2 201841038046-PROVISIONAL SPECIFICATION [08-10-2018(online)].pdf 2018-10-08
3 201841038046-POWER OF AUTHORITY [08-10-2018(online)].pdf 2018-10-08
4 201841038046-FORM 1 [08-10-2018(online)].pdf 2018-10-08
5 201841038046-DRAWINGS [08-10-2018(online)].pdf 2018-10-08
6 201841038046-DECLARATION OF INVENTORSHIP (FORM 5) [08-10-2018(online)].pdf 2018-10-08
7 Correspondence by Agent_Form1, Form3, Form5, And Form26_17-10-2018.pdf 2018-10-17
8 201841038046-PostDating-(04-10-2019)-(E-6-265-2019-CHE).pdf 2019-10-04
9 201841038046-APPLICATIONFORPOSTDATING [04-10-2019(online)].pdf 2019-10-04
10 201841038046-FORM-26 [03-12-2019(online)].pdf 2019-12-03
11 201841038046-FORM FOR SMALL ENTITY [03-12-2019(online)].pdf 2019-12-03
12 201841038046-EVIDENCE FOR REGISTRATION UNDER SSI [03-12-2019(online)].pdf 2019-12-03
13 201841038046-DRAWING [03-12-2019(online)].pdf 2019-12-03
14 201841038046-COMPLETE SPECIFICATION [03-12-2019(online)].pdf 2019-12-03
15 Correspondence by Agent_Form 28, MSME REGISTRATION CERTIFICATE AND POA_09-12-2019.pdf 2019-12-09
16 201841038046-FORM 18 [06-12-2022(online)].pdf 2022-12-06
17 201841038046-FER.pdf 2024-03-21
18 201841038046-OTHERS [09-08-2024(online)].pdf 2024-08-09
19 201841038046-FORM-26 [09-08-2024(online)].pdf 2024-08-09
20 201841038046-FER_SER_REPLY [09-08-2024(online)].pdf 2024-08-09
21 201841038046-CORRESPONDENCE [09-08-2024(online)].pdf 2024-08-09
22 201841038046-COMPLETE SPECIFICATION [09-08-2024(online)].pdf 2024-08-09
23 201841038046-US(14)-HearingNotice-(HearingDate-06-12-2024).pdf 2024-11-07
24 201841038046-Correspondence to notify the Controller [05-12-2024(online)].pdf 2024-12-05
25 201841038046-Written submissions and relevant documents [18-12-2024(online)].pdf 2024-12-18
26 201841038046-Annexure [18-12-2024(online)].pdf 2024-12-18
27 201841038046-PatentCertificate05-02-2025.pdf 2025-02-05
28 201841038046-IntimationOfGrant05-02-2025.pdf 2025-02-05

Search Strategy

1 201841038046ferE_28-02-2024.pdf

ERegister / Renewals