SMART RESCUE SYSTEM

Abstract

A smart rescue system 100 is disclosed. The system 100 includes a mobile device 101 allowing a requester to request for ambulance services, a network 102, and a server 103 communicatively coupled with the mobile device 101 through network 102. The requester provides details including patient's address. The server 103 includes a geo-location system 104 to automatically determine the ambulance available in a geo-spatial vicinity of the patient's address, a notification system 106 to notify a driver of the ambulance available in a geo-spatial vicinity of the requested address, a navigation system 105 to navigate the driver to a nearest medical centre in a geo-spatial vicinity of the patient's address, and recognizes upcoming traffic lights upto a certain distance in advance, and a microchip technology 107 fitted in the traffic lights controlled by the server 103.

Claims

1. A smart rescue system (100) comprising: a mobile device (101) allowing a requester to request for ambulance services; a network (102); and a server (103) communicatively coupled with the mobile device (101) through the network (102), wherein the requester provides details including patient's address, and wherein the server (103) comprises a geolocation system (104) to automatically determine the ambulance available in a geo-spatial vicinity of the patient's address; a notification system (106) to notify a driver of the ambulance available in a geo-spatial vicinity of the requested address; a navigation system (105) to navigate the driver to a nearest medical centre in a geo-spatial vicinity of the patient's address, and recognizes upcoming traffic lights upto a certain distance in advance; and a microchip technology (107) communicating with the traffic lights controlled by the server (103).

2. The smart rescue system (100) as claimed in claim 1, wherein the notification system (106) comprises a ping notification technology.

3. The smart rescue system (100) as claimed in claim 1, wherein the driver of the ambulance available accepts the request through an interactive application installed in a mobile device (101), or through hotline emergency services.

4. The smart rescue system (100) as claimed in claim 1, wherein the server (103) stores data entered by the requester and live location of the ambulance available.

5. The smart rescue system (100) as claimed in claim 1, wherein the navigation system (105) recognizes upcoming traffic lights upto a distance of 2 km (from the ambulance available) in advance.

6. The smart rescue system (100) as claimed in claim 5, wherein the navigation system (105) turns the upcoming traffic lights green.

7. The smart rescue system (100) as claimed in claim 1, wherein the server (103) comprises: a memory to store patient details entered by the ambulance driver and examining staff in the ambulance available; and a communication unit to communicate the stored patient details to the nearest hospital, the navigation system (105) identifies.

8. A method of smart rescue, the method comprising: requesting, by a mobile device (101), for ambulance service for patient; determining, by a server (103), an ambulance available in a geo-spatial vicinity of the patient's address; accepting, by a mobile device (101), request for ambulance by a driver of the ambulance available; navigating the ambulance, by the server (103), to provide a shortest path to reach the patient and a nearest hospital; and recognizing and controlling, by the server (103), upcoming traffic lights in the path upto a certain distance in advance.

9. The method as claimed in claim 8, comprising saving details including address of patient, patient's details as provided by requester, live location of the ambulance available, and patient details entered by the ambulance driver and examining staff in the ambulance available, wherein the saved details are communicated to the nearest hospital the server (103) identifies.

10. The method as claimed in claim 8, comprising turning the upcoming traffic lights green upto a distance of 2 Km.

Description

BRIEF DESCRIPTION OF DRAWINGS

[0020] To further clarify the advantages and features of the present disclosure, a more particular description of the disclosure will be rendered by reference to specific embodiments thereof, which is illustrated in the appended drawings. It is appreciated that these drawings depict only typical embodiments of the disclosure and are therefore not to be considered limiting of its scope. The disclosure will be described and explained with additional specificity and detail with the accompanying drawings.

[0021] The subject matter that is regarded as the invention is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other aspects, features, and advantages of the invention are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:

[0022] FIG. 1 illustrates a basic structure of the smart rescue system, according to an embodiment of the invention;

[0023] FIG. 2A-2I illustrates an overall process of operating the smart rescue system, according to an embodiment of the present invention; and

[0024] FIG. 3 illustrates schematically the process of controlling traffic lights by the server, according to an embodiment of the present invention.

[0025] Further, skilled artisans will appreciate that elements in the drawings are illustrated for simplicity and may not have necessarily been drawn to scale. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having benefit of the description herein.

DETAILED DESCRIPTION OF THE INVENTION

[0026] For the purpose of promoting an understanding of the principles of the invention, reference will now be made to the embodiment illustrated in the drawings, and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended. Such alterations and further modifications in the illustrated system, and such further applications of the principles of the invention as illustrated therein would be contemplated as would normally occur to one skilled in the art to which the invention relates. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skilled in the art. The system, methods, and examples provided herein are illustrative only and are not intended to be limiting.

[0027] The term “some” as used herein is to be understood as “none or one or more than one or all.” Accordingly, the terms “none,” “one,” “more than one,” “more than one, but not all” or “all” would all fall under the definition of “some.” The term “some embodiments” may refer to no embodiments or to one embodiment or to several embodiments or to all embodiments, without departing from the scope of the present disclosure.

[0028] The terminology and structure employed herein is for describing, teaching, and illuminating some embodiments and their specific features. It does not in any way limit, restrict or reduce the spirit and scope of the claims or their equivalents.

[0029] More specifically, any terms used herein such as but not limited to “includes,” “comprises,” “has,” “consists,” and grammatical variants thereof do not specify an exact limitation or restriction and certainly do not exclude the possible addition of one or more features or elements, unless otherwise stated, and furthermore must not be taken to exclude the possible removal of one or more of the listed features and elements, unless otherwise stated with the limiting language “must comprise” or “needs to include.”

[0030] Whether or not a certain feature or element was limited to being used only once, either way, it may still be referred to as “one or more features” or “one or more elements” or “at least one feature” or “at least one element.” Furthermore, the use of the terms “one or more” or “at least one” feature or element do not preclude there being none of that feature or element, unless otherwise specified by limiting language such as “there needs to be one or more . . . ” or “one or more element is required.”

[0031] Unless otherwise defined, all terms, and especially any technical and/or scientific terms, used herein may be taken to have the same meaning as commonly understood by one having ordinary skills in the art.

[0032] Reference is made herein to some “embodiments.” It should be understood that an embodiment is an example of a possible implementation of any features and/or elements presented in the attached claims. Some embodiments have been described for the purpose of illuminating one or more of the potential ways in which the specific features and/or elements of the attached claims fulfill the requirements of uniqueness, utility and non-obviousness.

[0033] Use of the phrases and/or terms including, but not limited to, “a first embodiment,” “a further embodiment,” “an alternate embodiment,” “one embodiment,” “an embodiment,” “multiple embodiments,” “some embodiments,” “other embodiments,” “further embodiment”, “furthermore embodiment”, “additional embodiment” or variants thereof do not necessarily refer to the same embodiments. Unless otherwise specified, one or more particular features and/or elements described in connection with one or more embodiments may be found in one embodiment, or may be found in more than one embodiment, or may be found in all embodiments, or may be found in no embodiments. Although one or more features and/or elements may be described herein in the context of only a single embodiment, or alternatively in the context of more than one embodiment, or further alternatively in the context of all embodiments, the features and/or elements may instead be provided separately or in any appropriate combination or not at all. Conversely, any features and/or elements described in the context of separate embodiments may alternatively be realized as existing together in the context of a single embodiment.

[0034] Any particular and all details set forth herein are used in the context of some embodiments and therefore should not be necessarily taken as limiting factors to the attached claims. The attached claims and their legal equivalents can be realized in the context of embodiments other than the ones used as illustrative examples in the description below. Embodiments of the present invention will be described below in detail with reference to the accompanying drawings.

[0035] The present invention provides a smart rescue system 100 (hereinafter “system” 100) that includes smart management of availing ambulance services to people in need. FIG. 1 illustrates a basic structure of the smart rescue system 100, according to an embodiment of the invention. The system 100 may be server 103 based and accessible by authorized person only. Though, any one feeling a need of calling an ambulance either for himself/herself or someone else may make a request, the server 103 may direct the request to such a driver, who can easily and rapidly reach at the location. Further, the server 103 may help the driver reach the destination in minimum time and avail medical services in time.

[0036] Further the server 103 may comprise a geo-location system 104 that may automatically determine the ambulance available in a geo-spatial vicinity of the patient's address, navigation system 105 notification system 106 and microchip 107.

[0037] In an embodiment, the system 100 may comprise a mobile device 101, a network 102, and a server 103 for controlling the operation of the system 100. FIG. 2a illustrates the step of making a request for ambulance services, according to an embodiment of the present invention. The mobile device 101 may be a smart phone, a tablet or any other mobile device 101 adapted to perform a minimum function of either calling on a specified number or an emergency service. In an embodiment, the mobile device 101 may be a normal calling cellphone, through which any person may make a call on a hotline emergency services to make a request to call an ambulance. In another embodiment, the mobile device 101 may be a smart mobile phone with an interactive application installed therein. The interactive application may be specifically designed to make ambulance services available and controlling the same. The patient may make a request himself/herself if the condition allows so, or any relative or anyone witnessing the situation of the patient may make the request.

[0038] The mobile device 101 may be connected to the server 103 through the network 102. The server 103 may receive the request. The server 103 may also receive additional details entered by the requester. The additional details may be a part of required details or optional details according to embodiments. In an exemplary embodiment, the address of the patient may be required while the name of the patient may be optional. In yet another embodiment, the condition of the patient may also be required to be furnished by the requester. FIG. 2b illustrates step of determining the ambulance available for the patient, according to an embodiment of the present invention. The server 103 may be an IoT server 103 that may save details of the patient as received by the requester. The server 103 may comprise a geo-location system 104 that may automatically determine the ambulance available in a geo-spatial vicinity of the patient's address. The geo-spatial vicinity of the patient's address may vary depending on the system 100 settings. In an exemplary embodiment, the system 100 may be adapted to identify ambulances within a range of 2 Km, while in another embodiment, the system 100 may be adapted to identify ambulances within a range of 5 Km. The geo-location system 104 may then determine the ambulance closest to the patient's address and if the ambulance is available.

[0039] FIG. 2c illustrates step of receiving request by a driver of the ambulance, according to an embodiment of the present invention. The server 103 may comprise a notification system 106 to notify the driver of the ambulance that has been identified by the geo-location system 104. The driver may be an authorized person having access to the server 103 through the network 102. In an embodiment, the server 103 may comprise a ping notification system to notify the driver of the request made by the requester, by a ping on the driver's device. The driver's device may be any mobile device 101 in the network 102 communicatively connected to the server 103. In an embodiment, the driver may have a mobile phone connected to the server 103 over which the driver may receive the notification. In another embodiment, the ambulance may comprise a mobile device 101 attached to/or placed in the ambulance that may be connected to the server 103 and receive a notification of the request received.

[0040] FIG. 2d illustrates step of accepting request by a driver of the ambulance, according to an embodiment of the present invention. The driver may accept the request based on the availability of the services. There might be a situation where the driver may not be able to take the ambulance to the patient. In case the driver finds it possible to take the ambulance to the patient, he may accept the request. The driver may accept the request on the interactive application installed in the mobile device 101 of the driver.

[0041] FIG. 2e illustrates step of ambulance proceeding to the patient, according to an embodiment of the present invention. The acceptance of the request by the driver of the ambulance available may be recognized by the IoT server 103. Once the acceptance is recognized, the navigation system 105 in the server 103 may be turned on. The navigation system 105 may highlight the fastest path to reach the patient. In an embodiment, the navigation system 105 may take into consideration the traffic in the path, distances of all the available paths leading to the patient, any road congestion, etc. The driver may start the trip to the patient. The geo-location system 104 in the server 103 may feed to the IoT server 103, the live location of the ambulance while travelling to the patient's address. The live location of the ambulance may be fed to IoT server 103 in real time. Therefore, the server 103 may take note of where the ambulance is, how much time it is taking or going to take to reach the patient.

[0042] FIG. 2f illustrates step of controlling traffic lights in the path, according to an embodiment of the present invention. There may be a microchip technology 107 (interchangeably used as “microchip” 107) fitted in the traffic lights. The microchip 107 may transmit signals upto a certain distance. In an embodiment, the distance may be upto 2 Kms in an embodiment. In another embodiment, the distance may be upto 5 Kms, depending on the type of microchip 107 installed in the traffic lights. The ambulances in the network 102 may be fitted with a receiver adapted to receive the signals transmitted by the microchip 107 in the traffic lights. Therefore, the ambulance in the range of the specified distance, may recognize the upcoming traffic lights in the distance range. The IoT server 103 may control the traffic lights as per the navigation path within the distance range as specified, and mainly 2 Kms. The IoT server 103 may turn the recognized traffic lights green so as not to let the ambulance wait there due to the traffic signals and also the traffic due to these signals. Therefore, the ambulance may reach the patient in time as illustrated in FIG. 2i.

[0043] FIG. 3 illustrates schematically the process of controlling traffic lights by the server 103, according to an embodiment of the present invention. In an embodiment, a pop-up mechanism may be employed. The pop-up mechanism may include an extra light 108 along with the conventional traffic lights at a traffic signal. The color of the extra light 108 added may be blue in an exemplary embodiment. As soon as the microchip 107 installed in the traffic light senses the ambulance (or vice versa), the pop-up mechanism may push down the extra light 108 that may alert drivers (traffic at the signal) of the approaching ambulance and also their estimated waiting time. There might be a situation where cars may be waiting for several minutes and the ambulance is not passing through. The ambulance might have recognized the traffic light but due to some reasons, the ambulance has still not covered the distance of 2 Kms between its location and the traffic light. The drivers waiting there might get frustrated due to them being stuck at red signal. However, this extra light 108 glowing may communicate to them the reason of the delay. Said extra light 108 would flash to indicate that the traffic lights are behaving unusually due to an ambulance approaching. In an embodiment, said light would flash slowly when an ambulance would be far away (>0.5 km) from the traffic light and flash rapidly when the ambulance was closer (<0.5 km).

[0044] In another embodiment, there might be a timer fixed with the extra light 108 reflecting the number of minutes the traffic has to wait, and/or how far the ambulance is.

[0045] The process of controlling the traffic lights may continue till the ambulance reaches the patient's location and the same has been illustrated in FIG. 2h. The traffic lights may return to normal after the ambulance passes by said location. FIG. 2g illustrates the process of the traffic lighting control after the ambulance passes them. Once the ambulance reaches the patient's location, the geo-location system 104 may update the status on the server 103.

[0046] In an embodiment, the driver or medical staff in the ambulance may examine the patient, provide a first aid (in case it is required), and fed all the relevant details in the interactive application. The relevant details may include but not limited to the condition of the patient, type of accident the patient has met with, criticality of the patient, etc. There may be a continuous communication between the paramedics, driver, and patient done through the interactive application. The server 103 and the geo-location systems 104 may be constantly on as illustrated in the FIG. 2i.

[0047] In an embodiment, the status of the criticality of the patient may form a part of the required information/detail, the medical staff or the driver are required to enter after examining the patient. In case, while controlling the traffic lights, the traffic lights receive two or more signals from approaching ambulance, the priority criteria that may be considered would be either or both criticality of patient and distance to designated hospital. In other words, if a traffic light senses that two ambulances are approaching, it may give priority on the discussed bases. In an exemplary embodiment, the criticality of the patient may be specified in the following stages and the driver or the examining staff may have to select one of the stages from the list and update it on the interactive application.

The patient's criticality stages are:

[0048] No worrying required (least deadly)—Sprain, Twisted ankle

[0049] Not critical—Broken bones

[0050] Slightly critical—Minorish bleeding, Few sprains

[0051] Most critical—Medium bleeding, Few serious scars

[0052] Super critical—Lots of bleeding, Deep cuts

[0053] Ultra critical—Cancer, COVID-19 bad state

[0054] May die soon—Could die any second

[0055] In an embodiment, if the IoT server 103 fails to control the traffic lights, the interactive application may be adapted to control the traffic lights. The driver or the paramedic in the ambulance or other as authorized by the system 100 may be able to control the traffic lights by the interactive application.

[0056] In an embodiment, based on the location and condition of the patient and availability of hospital, the IoT server 103 may communicate the nearest hospital location to the navigation system 105. The navigation system 105 may navigate the driver to the selected hospital and the driver may start the trip accordingly. The geo-location system 104 may automatically feed to the IoT server 103, the live location of the ambulance moving to the hospital. The IoT server 103 may also recognize the upcoming traffic lights in the same manner as it recognized while moving to the patient. The distance upto which the traffic lights may be recognize may either be same o different depending on the construction of the system 100. The IOT server 103 may take control of all traffic lights as per navigation path within 2 km, and turns them green. The process of controlling the traffic lights continues until the driver reaches the hospital's location and therefore, the trip may end with a minimum delay.

[0057] The figures and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein. Moreover, the actions of any flow diagram need not be implemented in the order shown; nor do all of the acts necessarily need to be performed. Also, those acts that are not dependent on other acts may be performed in parallel with the other acts. The scope of the embodiments is by no means limited by these specific examples. Numerous variations, whether explicitly given in the specification or not, such as differences in structure, dimension, and use of material, are possible.