Abstract: The present invention discloscs a mobile based emergency response system or mHooter ( m ~c)o mpiising of an Application (A) downloaded in Mobile Device (MD) and an External Wamir~y Device (ED). The mHooter provides alerts by sending mass notifications to members"within community along with a hooter alarm placed in the community in the event of an emergency. The External Warning Device (ED) comprises of a Device (D) and a Hooter (H). The Device (D) comprises of GSM modem, Display Unit, Power supply, Control Unit having a Micro-controller (M), Hooter, LED, Indication Unit having switches which when pressed notifies the selection. to the Control Unit and signifies the type of emergency.
FIELD OF INVENTION:
The invention relates to response and alert generation in case of emergency. More
particularly, the invention relates to a mobile based emergency response
application integrated with an external warning device (also referred to as
5 'mHooter') providing alerts by sending mass notifications to the members of the
community along with a hooter alarm placed in the community in the event of an
emergency such as theft, fire and medical emergency amongst many othcrs.
BACKGROUND OF THE INVENTION
10 In case of any emergency the first person to extend help or assistance can be the
immediate neighbor and now-a-days mobile or cell phones are ubiquitous and
have evolved to be the primary means of communication. In usual course as well
as in case of emergencies the mobile phones are used to malie calls. However, in
case ot cr~tical emergency or panic situation, people tend to forget everything as
15 the mind goes into state of oblivion and is not able to perform any conscious act.
Because of adrenalin rush / shock, an individual is not able to scream and is not
able to recall / decide what to do. Therefore, there was a need to provide the cell
- phones with applications meeting such.emergency.needs.. .- -. - .
20 The products in the existing state of the art provide individual hooter through
. . panic button. These are individual hardware or software or mobile based
applications. There are hundreds of SOS mobile applications which communicate
with ST)S nr relatives r.nntacts in case of emergency. In many cases cmbcddcd
programmed devices available to communicate with one-on-one hooter. ow ever
25 none of them provides community based siren mechanism where every resident
living in the community can use single hooter. None of the hardware device
available in the market communicates with every individual resident in a
community in collaborative manner.
30 The present invention caters this kind of panic situation and obviates the problems
in the existing state of the art. All one needs to do is just to press both up and down
2
,.s,m p**a-pL- : a -
& pr. --. " - & & . - & - &. --- PI;. a = bpm.5 .7d -
volume rocker simultaneously three times; or press the hooter button in mobile
application.
OBJECT AND SUMMARY OF THE JNVEN'I'ION
'5 The main object of the present invention is to provide a mobile based emergency
response application integrated with an external warning device.
Another object of the present invention is to provide a mobile based emergency
response application providing alerts by sending mass notific.ations to members of
10 the community along with a hooter alarm placed in the community in the event of
an emergency.
Yet another object of present invention is to provide a mobile based emergency
response application designed to cater the smart city security needs by providing
15 an additional layer of protection through the automated notification and instant
help from immediate neighbors within community along with activation of single
common hooter in case of emergency.
Yet another object of present invention is to provide a mobile based emergency
20 response application providing different users wherein each user has segregated
rights to access and administer.
Accordingly, present invention ,provides a mnhile l.>ase,d emergency responsc
application integrated with an external warning device'. The external warning
25 device is also referred to as 'Hooter'. It is specially designed to cater the smart city
security needs of common citizens of Indian societies. The application of present
invention provides an additional layer of protection through the automated
notification and instant help from neighbors within community along with
activation of single common hooter in case of emergency. Before the trained
30 personnel like policemen, firemen or ambulance can come to the rescue, this
application helps create an additional layer of community policing. .
I -Le-g :. .-m&r:=- -z& , arns ,:-, &. , gs-,- "%.',- 23.;&5.2..g 1 g-5. =lp.. 'A
The application of the present invention. needs to be downloaded from online
marketplace and then users are required to register within the application and join
the community1 apartment to be able to carry out its defined function. .
5 BRIEF DESCRIPTION OF DRAWINGS
Fig. 1 depicts Block Diagram of mHooter
Fig. 2 depicts Circuit Diagram of mHooter Control I-lnit
Fig. 3 depicts Circuit Diagram of mHooter Display and Switch Interface
Fig. 4 depicts Functional Diagram of GSM Modem & Power Supply
10 Fig. 5 depicts the mHooter user flow
Fig. 6a and Fig. 6b depict guard interface and user interface on smart-phone
Fig. 7a and Fig. 7b actual device interface and depicts actual device 3D image
Fig. 8a and Fig. 8b Web Console for Super Admin and Community Admin
15 DETAILED DESCRIPTION OF INVENTION WITH ILLUSTRATED
EXAMPLES
The present invention provides a mobile based emergency response application
integrated with an external warning device. The mobile based emergency response
application, external warning device are togethe; referred as 'rnHooterf. It is
20 specially .designed to cater the smart city security needs of common citizens of
Indian societies. This gives an additional layer of protection through the automated
notification and instant help from neighbors within community along with
activation of single common hooter in ca.se Krncrgency., Before the trninod
personnel like policemen, firemen and ambulance can come to the rescue, this
25 application helps create an additional layer of community policing.
In a preferred embodiment, the mHooter (mH) comprises of an Application (A)
that is downloaded in Mobile Devices (MD) along with an External Warning
Device (ED) to be purchased from the company. The External Warning (ED)
30 comprises of at least one Guard Interface Device (D) and at least one Hooter (H).
The Guard Interface Device (D) comprises of at least one GSM modem (1 1 I), at
least one Control Unit (1 12), at least one Indication Unit ( 1 13), at least one
Display Unit (1 14) and at least one Power Supply (1 15). The Indication Unit (1 13)
comprises of at least six Switches (SI - S6) and six LED (LI - L6) (Fig. I).
5 For administration purpose there are two categories of users: Super Admin and
Cotrirnunity Admin. These users are having a Web Console (WC) interface only.
This Web Console (WC) can be accessed via i.ntcrnet on any Desktop PC, Laptop
connected to internet (Fig. 8a and Fig. 8b).
10 Super ~ d m i nca n access his account using the User id and Password. Once Super
Admin is logged in, he is able to the following operations:
Add Hooter
Single hooter
hfulliple Huuiers (CSV ~m~0t-t)
15 Edit Hooter details
'Search Hooter information wherein the information comprises, but not
limited to, the fields like unique id, Install location, status, registered SIM
number, activation date of SIh4, expiry datc of SIM, purchased by, seller.
- .,
Activate a Hooter on new purchaselregistration
20 , Deactivate a Hooter
Change Password
Update individual community information
Super Admin is able to add a new Hooter (when dispatching for store) by filling
25 up a form with the following details:
Hooter ID
Status of Hooter (by default inactive)
~ e ~ i s t e r eSdIM Number for Hooter
.Activation Date of SIM
3.0 Expiry Date of SIM
Name of Registered Person for SIM
. .
Seller of the Hooter
Community name for particular Hooter .
Super Admin is also able to access all community admin accounts and can
viewledit each of the details of every community.
5
The second type of user is Community Admin. A community admin has to register
: a new hooter device along with himlher thro~lght he registration procecc on ~ c b
panel providing the following information:
Hooter ID
10 Mobile No. '
Verify Mobile No.
Password
After successfully creation of the account Community Admin is able to login to
his account and to perform the following opcrations:
15 AddIUpdate community information
Community Iconlimage
Community Name
Comm~lnity.A ddress
. . . . . ..
Update Password
20 Addlupdate guard
Mobile No.
Addlremove community admin
Addlupdate police station details.
Add/edit/delete members
25 Edit all the details at any point bf navigation
Search functionality
Change password of his account.
The Application (A) is downloaded from internet marketplace in the Mobile
. 30 Device (D) and then users are required to register and join the community /
apartment to be able to carry out its defined function.
6
FA-,nrd:..m . Sw.FEzEB,S: n. P -? A-. Q--g-.G-! ..&-a--s, .wn-. -%gr;?e -, z%: ~in. l.-Fb- *-~- " ~F.d .'
The Application (A) has different users and each user has segregated rights of
access.
5 The first type of user is simple user. Simple user has to download the Application.
(A). Once the download completes, a splash screen opens for few seconds on the
Mobile Device (D). After splash scr'een, user has tn register himself and join
apartmentJcommunity by entering following details:
. .
Mobile Number
10 Enter Verification code
Apartment Name
Flat number
SOS Screen Number, e.g.
Ni~rnher 1
15 Number 2
Number 3
The registered user can open the Application (A) on the Mobile Device (MD) and
press the Hooter hutt.nn for 5 Sec in case of any emergency. A text message
activates Hooter (H), guard and all residents within a community. A text message
20 is also send to registired SOS numbers on user account.
The second category of user is Guard. Guard also has to register himself for the
Application (A) with the details as of the Simple user. The Display .Unit ( 1 14) of
the Device (D) in the Guard Room where the guard can view the flat number of
25 the user who needs emergency assistance. (When hooter is buzzing, guard will
ascertain the situation and take relevant action accordingly. The Device (D) in the
Guard / Security room comprises of Switches (SI - Sg) (Fig, 7a):
Hooter Switch (S,): This button is to follow up re-press hooter option in
the critical situation for pressing the hooter again in the society. This sends
a reconfirmation to everyone with alert message that there is a situation of
emergency.
Stop Switch (S2): TO Stop Hooter.
Relax Switch (S3): TO send "relax" follow up message to all community
residents for false alert or "situation under control" notification so that
people do not create unnecessary panic during exceptions.
5 Patrol Switch (S4): TO send a message to the police control room and
thereafter the control room takes appropriate action.
c Medical Switch (SJ); To sand a messngc to tlic ar~rbulancec ontrol room
and thereafter the control room takes appropriate action.
0. Fire button switch (S6): In case of fire, if the guard presses this button the
10 message is delivered to the centralized cali center of the Fire-department,
which can then dispatch a fire brigade for assistance.
In another embodiment, the Application (A) activates the ~ o o t e(rH ) if any user
presses the hooter button in the Application (A) on the Mobile Device (M) for 5
15 seconds or presses both up and down volume rocker simultaneously in the Mobile
Device (M) in case of emergency (Fig.6b).
In a non-limiting example, the Application (A) sends a message (according to thc
situation) to server and the server after verifying the number sends the alert
20 message to guard room, SOS numbers and all registered community members.
Hooter (H) also switches on automatically in such situation and stays in turned on
state for a specified period, such as for 60 seconds (Fig. 5).
The working of Application (A) and its connection to the Hooter (H) is explained
25 briefly through the figures, circuit diagrams and flowcharts.
At first GSM modem (1 11) does the work of receiving and sending message.
Control Unit (1 12) decodes message received by GSM Modem (I 11) and also
sends encoded data in the form of message through GSM Modem (1 11) to server.
30 Further, Control Unit (I 12) having a Micro-controller (M) also communicates and
commands Display Unit (1 l4), Hooter (H) and LEDs (LI - L6). Display Unit (1 14)
displays the all accrued events and received messages. Switches (S1 - S6) when
pressed notify the selection to the Control Unit (1 12), the selection signifies the
type of emergency. The LEDs (LI - L6) indicate the status of particular switch (S1
- S6). Hooter (H) gets turn on when Control circuit (I 12) receives input regarding
5 any emergency or out of control condition. All components get power from power
supply (1 15) component.
Circuit Description:
For the working of the mHooter (mH) different circuit segments are required to be
interconnected with each other. The connector JI and J2 at fig. 2 and fig. 3 are
connected together and connector JACK is connected with 230V AC input and
12V CD output terminal of SMPS (Switch Mode Power Supply) respectively.
Connector 54 and 53 are for DC Hooter and AC Hooter respectively. 12V DC
uulpul ul' SklPS Is required to get c.onnected with 12V DC input tcrminal of GSM
15 Modem (1 11). Connector GSM JACK is used to connect data Tx and Rx pin of
micro-controller with Rx and Tx pin of GSM Modem (1 11) respectively.
Connector JACK is to provide Vcc and GND supply from Vcc and GND pins at
GSM Modem (Fig. 2, Fig. 3, and Fig. 4).
20 After making all the connections, the power supply (1 15) is turned on to initialize
GSM modem (1 1 I), Display Unit (1 14), LEDs (Ll - L6), Switches (SI - S6), and
Micro-controller (M) and till power supply remains on, its status is displayed by
the Display Unit (1 14). After initialization Micro-controller (M) sends command
to GSM Modem (1 11). If GSM Modem is connected and working properly, it
25 acknowledges said command by sending dqta to Micro-controller (M) in the
Control Unit (1 12). On receiving acknowledgment from GSM Modem (1 1 I), the
~icro-controller (M) sends command and data to Display Unit (1 14), for
displaying "ok" status. Once system reaches this state it is able to do normal
functioning and a message "Waiting for Message" is being displayed on the
30 Display Unit (1 14). On the other hand, if system does not reaches at this status it
will not be able to do any further operation and a message "Communication fails,
system not ready" will display on Display Unit (1 14).
The Micro-controller (M) continuously checks status from GSM Modem (I 1 I )
5 that comes at Rx pin of micro-controller there. If Micro-controller (M) does not
detcct any message the status re-checked.
GSM Modem (I 1 1 ) has a SIM connection at SIM card slot and that SIM has its
number provided by network provider. As GSM Modem (1 11) receives any SMS
10 message at its SIM card, Micro-controller (M) detects that message (SMS). On
detection of SMS Micro-controller (M) sends command to GSM Modem (1 11) to
fetch the number or sender ID from which message had received. If said number
or Sender ID matches to the predefined number or sender ID that already stored in
the memory of Micro-contrnller (M) nn!y (ban it goec to further stcp elsc it
15 displays "message not from valid sender" on the Display Unit (1 14) and it again
starts waiting for new input.
Where said number or sender ID matches with predefined number or sendcr ID,
the Micro-controller (M) sends command to fetch the data of received message.
20 After receiving said data of received message, the Micro-controller (M) decodes
said data on the basis of message received. If data come in the format of
*ALT-MH-SFT-XYZ# it indicate that there is an emergency status at flat
number XYZ, if data come in the format of *STP# it indicate that it is required to
stop hooter, if data come in the format of *EMG# it indicate that there is an
25 emergency status atcommunity, and if data come in the format of *PLT# it
' . indicate patrol status which means that emergency status that have already accrued
is out of control and external support is required.
On receiving emergency status Micro-controller (M) sends command to turn on
30 both Hooters (H) and LED (LI) as emergency indication. If this emergency comes
from particular flat, a message "There is an emergency at flat no. XYZ" displays
on Display Unit (1 14) or if it comes from community a message "Alert there is an
emergency at community" is displayed. On receiving stop status Micro-controller
(M) sends command to turn off both Hooter (H) and emergency indication LED
(L,), and turn on stop indication LED (L2) for some moment. Then a message
5 "Hooter Stop" is displayed on Display Unit (1 14). If Micro-controller does not
receive slop command it automatically turn off Hooter (H) after 1 minute. On
receiving patrol status Micro-controller (M) sends commands to turn on Hooter
(H), patrol status indication LED (L4) and a message "Situation out of control call
external support (Police)" is displayed on Display Unit (1 14). After patrol status if
10 Micro-controller (M) does not read stop status hooters and indication LED (L4)
will turn off automatically after 3 minutes.
At any point after receiving any of the messages and responding to that message,
the Micro-controller (M) comes on initial status where it again starts waiting for
15 new input and message "Waiting for new message" will display on Display Unit
(1 14).
The switches (SI - S6) on the Device (!(FIig.) 7a ), S1 is for HOOTER command,
S2 for STOP command, S3 is REL RELAX command, S4 is for PATROL command,
20 S5 MEDICAL command and S6 is for FIRE command. When Micro-controller (M)
in the Control Unit (1.1 2) reads STOP command through S2 it stops the hooter (H),
turns off status indicating LED (L1) and turns on STOP indication LED (L2) for
. some time. It also displays a message "Hooter Stop" on Display Unit ( 1 14). On
receiving HOOTER command through SI it means there is an emergency at
25 community and hooters turn on along with emergency indication LED (LI). A.
message "Alert there is an emergency at community" is displayed on Display Unit
(1 14) and message "HOOT ALERT..!! EMERGENCY AT COMMUNITY" will'
be sent by Micro-controller (M) through GSM Modem (I 11) to a specified
number. On receiving RELAX command through S3 Micro-controller (M) will
30 turn on relax status indication LED (L3) for some time, display message "Relax
problem solved" on Display Unit (1 14) and also sends a message "HOOT
RELAX..!! PROBLEM SOLVED" to a specified number. Upon receiving
PATROL command through Sq Micro-controller (M) will. turn on hooters, patrol
status indicating LED (L4) and send message "Situation out of control call external
. . support (Police)" will'be displayed on Display Unit (1 14). It also sends a message
5 "HOOT OUT OF CONTROL..!! CALL POLICE" to specified number.
Along with all its operational functioning, to periodically check the working statu~
of the devices a message *ACK# from server to mHooter (mH) is sent. When
Micro-controller (M) of Control Unit (1 12) reads this message it responds in terms
10 of sending a message "HOOT OK ... I AM FmE" and also displays a message on
Display Unit (1 14) "OK ... I AM FINE". When server gets this message in return
it means particular mHooter (mH) is working properly.
Exnmplc:
15 The User downloads the Application on his Mobile Device (D). In case of
emergency the user uses the Application (A) to send emergency message to the
GuardISecurity room of the Community and registered SOSs numbers on user
account (Fig. 5). The user make< a selection of the emergency situation by thc
selecting the options on the Application (A) (Fig. 6b). The message is received by
20 the Device (D) placed in the GuardISecurity room of the community. The GSM
modem (1 11) of the Device (D) (Fig. 4) receives the messages, decodes and sends
to the Control Unit (1 15). The Micro controller (M) in the Control Unit (1 15)
verifies the number. Once the number is verified the message is displayed on the
Display Unit (1 14) of the Device (D) (Fig. 5). According to the emergency as
25 reflected in the message of the user, the Guard / Security takes appropriate action
using the Switches (S, - S6).
We claim:
1. A mobile based emergency response 'system or mHooter (mH) comprising of at
least one Application (A) downloaded in Mobile Device (MD) and at least one
External Warning Device (ED) comprising of at least one Device (D) and at least
5 one Hooter (H)
wherein
said Device (D) comprises the components nf
. at least one GSM modem (1 1 1) to receive and send messages,
at least one Display Unit (1 14) to display all accr~red events and
10 received messages,
at least one Power supply (I 12) to supply power,
at least one Control Unit (1 15) 'having at least one Micro-controller ,
(M) to decode message received by GSM Modem (1 1 I), to send
encoded data in the form ot'messagc through GSM Mode111 (I 11) Lo
server, to communicate and command Display Unit (1 14), Hooter
(1 10) and LED (LI - Lg)
at least one Indication Unit (1 13) having at least six switches (S1 - I
s6) which when pressed notifies the selection to thc Control Unit I
(1 15); the selection signifies the type of emergency and at least six
LED (LI - L6) to indicate the status of particular switch,
wherein said mHooter provides alerts by sending mass notifications to members
within community along with a hooter alarm placed in the community in the event
of an emergency. I
25
2. The mobile based emergency response system or mHooter (mH) as claimed in
claim 1 wherein said mHooter activation comprises the steps of
- activation of Application (A) by user wherein said activation is
enabled either by pressing the hooter button in application for 5 I
seconds or by pressing both up and down volume rocker
simultaneously for 5 seconds of the mobile in case of emergency,
- transmission of emergency message to Control Unit (1 13,
- verification of mobile 'number by the Control Unit (1 15),
- transmission of alert message to guard room, sos numbers and .all
registered community members
wherein said Device (D)
switches on the Hooter (H) automatically in emergency situation and
stays in turned on state for 60 seconds,
0 provides alerts by sending mass notifications to proximate communities
along with a Hooter (H) alarm placed ,in the co~nrr~uriitiny the event of
an emergency.
3. The mobile based emergency response system or mHooter (mH) as claimed
in claim 1 wherein said users are of four types comprising
- Super admin on Web Console who after logging in is able to
add new Hooter by providing pre-defined information on a Form
edit Hooter details
to search Hooter information
activate or deactivate a Hnnter
change password
update individual community information
wherein Super admin is also able to access all community admin accounts
and to viewledit each of the details of every community.
- community admin on Web Console who registers a new hooter device
through the registration process on. web panel providing the pre-dkfined
information and after logging in is able to.
AddIUpdate community information
'* Community lcon/image
community Name
Community Address
Update Password
Addlupdate guard.
Addlupdate Mobile No.
Addlremove community admin
Add/update police station details
5 Addleditldelete members
Edit all the detai'ls at any point of navigation
search functionality
Change password of his account.
10 - Simple user who downloads the Application (A) from an online application
store and after registration joins the community by entering information
including mobile number, verification code, apartment name, flat number
and at least one SOS screen number wherein the registered Simple user is
able to open the application and press the Hooter button present on mobile
for 5 Sec in case of any emergency which in turn notifies hooter, guard and
all residents of the community by sending a text message to said hooter,
guard and all residents of the community and to user's SOS numbers.
- Guard who undergoes registration process for the Application (A) and
20 thereafter is able to get access to relevant details of the Simple user
registered within the community. These details will be displayed on
Display Unit (1 14) of the Device (D) on device and Application (A> (Fig.
6a) available in the Guard room based on which the guard takes relevant i
I
' I
action ascertaining the situation.
25
4. The mobile based emergency response system or mHooter (mH) as claimed in 1
I
in claim 3 wherein each user has segregated rights to access and administer. I ~
5. The-mobile based emergency response system or mHooter (mH) as claimed in
30 claim 3 wherein said pre-defined information to add new Hooter by the Super
admin are comprises of
Hooter ID
Status of Hooter (by default inactive)
Registered Sim Number for Hooter
Activation Date of Sim
Expiry Date of Sim
Name of Registered Person for Sim
Seller of the Hooter
Community name for particular Hooter
10 6. The mobile based emergency response application as claimed in claim 3
wherein said pre-defined information to register a new Hooter (H) through the
registration'process on web panel by the Community user are comprises of
Hooter ID - hlubile Nu.
Verify Mobile No.
Password
7. The mobile based emergency response application as claimed in claim 3
wherein said Device has at least six switches (S1 - S6) comprising
20 .Hooter button: To follow up re-press hooter option in the critical
situation for pressing the hooter again in the society which sends a
reconfirmation to everyone with alert message that there is a situation of
emergency.
. Stop button: To Stop ~ooter
Relax button: To send "relax" follow up message to all community
residents for false alert or "situation under control" notification so
that people do not create unnecessary panic during exceptions
Patrol button: To send a message to the police control room and
there after the control, room takes appropriate action.
Ambulance button: To send a message to the ambulance control
room and thereafter the control room takes appropriate action.
Fire button: In case of fire, if the guard presses this button the
message is delivered to the centralized'call center of the Firedepartment,
which can then dispatch a fire brigade for assistance.
| Section | Controller | Decision Date |
|---|---|---|
| 15 and 43 | Sudhish Gaur | 2024-03-08 |
| 15 and 43 | Sudhish Gaur | 2024-04-08 |
| # | Name | Date |
|---|---|---|
| 1 | 2627-del-2015-GPA-(25-08-2015).pdf | 2015-08-25 |
| 1 | 2627-DEL-2015-GPA-220324.pdf | 2024-04-24 |
| 2 | 2627-del-2015-Form-3-(25-08-2015).pdf | 2015-08-25 |
| 2 | 2627-DEL-2015-Correspondence-220324.pdf | 2024-04-12 |
| 3 | 2627-DEL-2015-IntimationOfGrant08-04-2024.pdf | 2024-04-08 |
| 3 | 2627-del-2015-Form-2-(25-08-2015).pdf | 2015-08-25 |
| 4 | 2627-DEL-2015-PatentCertificate08-04-2024.pdf | 2024-04-08 |
| 4 | 2627-del-2015-Form-1-(25-08-2015).pdf | 2015-08-25 |
| 5 | 2627-DEL-2015-PETITION UNDER RULE 137 [22-03-2024(online)].pdf | 2024-03-22 |
| 5 | 2627-del-2015-Form-5-(05-01-2016).pdf | 2016-01-05 |
| 6 | 2627-DEL-2015-RELEVANT DOCUMENTS [22-03-2024(online)].pdf | 2024-03-22 |
| 6 | 2627-del-2015-Form-3-(05-01-2016).pdf | 2016-01-05 |
| 7 | 2627-DEL-2015-Written submissions and relevant documents [22-03-2024(online)].pdf | 2024-03-22 |
| 7 | 2627-del-2015-Form-2-(05-01-2016).pdf | 2016-01-05 |
| 8 | 2627-del-2015-Form-1-(05-01-2016).pdf | 2016-01-05 |
| 8 | 2627-DEL-2015-Correspondence to notify the Controller [09-03-2024(online)].pdf | 2024-03-09 |
| 9 | 2627-DEL-2015-US(14)-ExtendedHearingNotice-(HearingDate-14-03-2024).pdf | 2024-03-04 |
| 9 | 2627-del-2015-Correspondence Others-(05-01-2016).pdf | 2016-01-05 |
| 10 | 2627-del-2005-Form-2-(05-01-2016).pdf | 2016-01-05 |
| 10 | 2627-DEL-2015-FORM-26 [02-03-2024(online)].pdf | 2024-03-02 |
| 11 | 2627-DEL-2015-FORM 13 [29-02-2024(online)].pdf | 2024-02-29 |
| 11 | Form 18 [17-05-2017(online)].pdf | 2017-05-17 |
| 12 | 2627-DEL-2015-FER.pdf | 2020-07-31 |
| 12 | 2627-DEL-2015-FORM-26 [29-02-2024(online)].pdf | 2024-02-29 |
| 13 | 2627-DEL-2015-FORM FOR STARTUP [27-01-2021(online)].pdf | 2021-01-27 |
| 13 | 2627-DEL-2015-REQUEST FOR ADJOURNMENT OF HEARING UNDER RULE 129A [29-02-2024(online)].pdf | 2024-02-29 |
| 14 | 2627-DEL-2015-FORM 4(ii) [27-01-2021(online)].pdf | 2021-01-27 |
| 14 | 2627-DEL-2015-US(14)-HearingNotice-(HearingDate-29-02-2024).pdf | 2024-02-16 |
| 15 | 2627-DEL-2015-EVIDENCE FOR REGISTRATION UNDER SSI [27-01-2021(online)].pdf | 2021-01-27 |
| 15 | 2627-DEL-2015-REQUEST FOR ADJOURNMENT OF HEARING UNDER RULE 129A [12-02-2024(online)].pdf | 2024-02-12 |
| 16 | 2627-DEL-2015-RELEVANT DOCUMENTS [25-02-2021(online)].pdf | 2021-02-25 |
| 16 | 2627-DEL-2015-US(14)-HearingNotice-(HearingDate-12-02-2024).pdf | 2024-01-04 |
| 17 | 2627-DEL-2015-ABSTRACT [25-02-2021(online)].pdf | 2021-02-25 |
| 17 | 2627-DEL-2015-POA [25-02-2021(online)].pdf | 2021-02-25 |
| 18 | 2627-DEL-2015-AMMENDED DOCUMENTS [25-02-2021(online)].pdf | 2021-02-25 |
| 18 | 2627-DEL-2015-PETITION UNDER RULE 137 [25-02-2021(online)].pdf | 2021-02-25 |
| 19 | 2627-DEL-2015-OTHERS [25-02-2021(online)].pdf | 2021-02-25 |
| 19 | 2627-DEL-2015-CLAIMS [25-02-2021(online)].pdf | 2021-02-25 |
| 20 | 2627-DEL-2015-COMPLETE SPECIFICATION [25-02-2021(online)].pdf | 2021-02-25 |
| 20 | 2627-DEL-2015-MARKED COPIES OF AMENDEMENTS [25-02-2021(online)].pdf | 2021-02-25 |
| 21 | 2627-DEL-2015-DRAWING [25-02-2021(online)].pdf | 2021-02-25 |
| 21 | 2627-DEL-2015-FORM-26 [25-02-2021(online)].pdf | 2021-02-25 |
| 22 | 2627-DEL-2015-ENDORSEMENT BY INVENTORS [25-02-2021(online)].pdf | 2021-02-25 |
| 22 | 2627-DEL-2015-FORM 13 [25-02-2021(online)].pdf | 2021-02-25 |
| 23 | 2627-DEL-2015-FER_SER_REPLY [25-02-2021(online)].pdf | 2021-02-25 |
| 24 | 2627-DEL-2015-ENDORSEMENT BY INVENTORS [25-02-2021(online)].pdf | 2021-02-25 |
| 24 | 2627-DEL-2015-FORM 13 [25-02-2021(online)].pdf | 2021-02-25 |
| 25 | 2627-DEL-2015-FORM-26 [25-02-2021(online)].pdf | 2021-02-25 |
| 25 | 2627-DEL-2015-DRAWING [25-02-2021(online)].pdf | 2021-02-25 |
| 26 | 2627-DEL-2015-MARKED COPIES OF AMENDEMENTS [25-02-2021(online)].pdf | 2021-02-25 |
| 26 | 2627-DEL-2015-COMPLETE SPECIFICATION [25-02-2021(online)].pdf | 2021-02-25 |
| 27 | 2627-DEL-2015-CLAIMS [25-02-2021(online)].pdf | 2021-02-25 |
| 27 | 2627-DEL-2015-OTHERS [25-02-2021(online)].pdf | 2021-02-25 |
| 28 | 2627-DEL-2015-AMMENDED DOCUMENTS [25-02-2021(online)].pdf | 2021-02-25 |
| 28 | 2627-DEL-2015-PETITION UNDER RULE 137 [25-02-2021(online)].pdf | 2021-02-25 |
| 29 | 2627-DEL-2015-ABSTRACT [25-02-2021(online)].pdf | 2021-02-25 |
| 29 | 2627-DEL-2015-POA [25-02-2021(online)].pdf | 2021-02-25 |
| 30 | 2627-DEL-2015-RELEVANT DOCUMENTS [25-02-2021(online)].pdf | 2021-02-25 |
| 30 | 2627-DEL-2015-US(14)-HearingNotice-(HearingDate-12-02-2024).pdf | 2024-01-04 |
| 31 | 2627-DEL-2015-EVIDENCE FOR REGISTRATION UNDER SSI [27-01-2021(online)].pdf | 2021-01-27 |
| 31 | 2627-DEL-2015-REQUEST FOR ADJOURNMENT OF HEARING UNDER RULE 129A [12-02-2024(online)].pdf | 2024-02-12 |
| 32 | 2627-DEL-2015-FORM 4(ii) [27-01-2021(online)].pdf | 2021-01-27 |
| 32 | 2627-DEL-2015-US(14)-HearingNotice-(HearingDate-29-02-2024).pdf | 2024-02-16 |
| 33 | 2627-DEL-2015-FORM FOR STARTUP [27-01-2021(online)].pdf | 2021-01-27 |
| 33 | 2627-DEL-2015-REQUEST FOR ADJOURNMENT OF HEARING UNDER RULE 129A [29-02-2024(online)].pdf | 2024-02-29 |
| 34 | 2627-DEL-2015-FER.pdf | 2020-07-31 |
| 34 | 2627-DEL-2015-FORM-26 [29-02-2024(online)].pdf | 2024-02-29 |
| 35 | 2627-DEL-2015-FORM 13 [29-02-2024(online)].pdf | 2024-02-29 |
| 35 | Form 18 [17-05-2017(online)].pdf | 2017-05-17 |
| 36 | 2627-del-2005-Form-2-(05-01-2016).pdf | 2016-01-05 |
| 36 | 2627-DEL-2015-FORM-26 [02-03-2024(online)].pdf | 2024-03-02 |
| 37 | 2627-DEL-2015-US(14)-ExtendedHearingNotice-(HearingDate-14-03-2024).pdf | 2024-03-04 |
| 37 | 2627-del-2015-Correspondence Others-(05-01-2016).pdf | 2016-01-05 |
| 38 | 2627-del-2015-Form-1-(05-01-2016).pdf | 2016-01-05 |
| 38 | 2627-DEL-2015-Correspondence to notify the Controller [09-03-2024(online)].pdf | 2024-03-09 |
| 39 | 2627-DEL-2015-Written submissions and relevant documents [22-03-2024(online)].pdf | 2024-03-22 |
| 39 | 2627-del-2015-Form-2-(05-01-2016).pdf | 2016-01-05 |
| 40 | 2627-DEL-2015-RELEVANT DOCUMENTS [22-03-2024(online)].pdf | 2024-03-22 |
| 40 | 2627-del-2015-Form-3-(05-01-2016).pdf | 2016-01-05 |
| 41 | 2627-DEL-2015-PETITION UNDER RULE 137 [22-03-2024(online)].pdf | 2024-03-22 |
| 41 | 2627-del-2015-Form-5-(05-01-2016).pdf | 2016-01-05 |
| 42 | 2627-DEL-2015-PatentCertificate08-04-2024.pdf | 2024-04-08 |
| 42 | 2627-del-2015-Form-1-(25-08-2015).pdf | 2015-08-25 |
| 43 | 2627-del-2015-Form-2-(25-08-2015).pdf | 2015-08-25 |
| 43 | 2627-DEL-2015-IntimationOfGrant08-04-2024.pdf | 2024-04-08 |
| 44 | 2627-DEL-2015-Correspondence-220324.pdf | 2024-04-12 |
| 44 | 2627-del-2015-Form-3-(25-08-2015).pdf | 2015-08-25 |
| 45 | 2627-del-2015-GPA-(25-08-2015).pdf | 2015-08-25 |
| 45 | 2627-DEL-2015-GPA-220324.pdf | 2024-04-24 |
| 1 | 2020-07-1413-22-46E_14-07-2020.pdf |