IL301539A - Systems, devices and methods for activating an emergency button using a mobile communication device - Google Patents

Description

PT001/IL SYSTEMS, DEVICES, AND METHODS FOR PANIC BUTTON ACTIVATION USING A MOBILE COMMUNICATION DEVICE TECHNICAL FIELD [0001]The present invention, in some embodiments thereof, relates to systems, devices, and methods for activating a panic button, and more specifically, but not exclusively, to panic button activation using a mobile communication device such as a smartphone. BACKGROUND OF THE INVENTION [0002]Panic button systems and devices are used to call for help in emergency situations. These systems are typically used in high-risk environments such as hospitals, kindergartens, schools, and workplaces. A panic button can have several advantages over dialing 911 in an emergency situation. First, a panic button provides more accurate and precise location information to emergency responders, as it is usually known in advance where the panic button is located. Second, a panic button can be discreetly activated, without drawing attention to the user or alerting potential attackers or perpetrators. Finally, panic buttons offer direct access to the relevant emergency services, related to the organization, utilizing the panic button service – local government security officers, on-premise security, patrols, etc. In most cases, these services provide much faster response times than police and are trained to handle emergency situations other than crimes. [0003]Panic buttons can be physical buttons installed in the premises, however they pose various limitations, such as required connectivity, hardware costs, limited functionality and risk of failure. [0004]The increasing prevalence of mobile communication devices, such as mobile phones and smartphones presents an opportunity to use these devices as panic buttons, as they are readily available and are carried by most people in the country With cellular connectivity, mobile phones can connect to cellular networks, which are available in most areas and provide a strong and stable connection. [0005]Existing panic buttons and emergency call solutions typically require users to undergo training before they can use them, which may include installing specific applications like emergency call applications in order to activate a distress signal. This can be a problem in emergency situations, as users such as teachers or nursery staff who have not installed the necessary applications or are unfamiliar with the installation process may be unable to activate the panic button when it is most needed. -2- PT001/IL id="p-6" id="p-6"

[0006]In view of the foregoing, there is a need for enhanced systems, apparatus, and techniques for actuating a panic button system, which address some of the aforementioned drawbacks of prior art. Advantageously, these methods and systems for panic button activation should involve the use of mobile devices, including for example smartphones, without necessitating the installation of a pre-installed application or any prior familiarity with the panic button system's operation SUMMARY OF THE INVENTION [0007]The panic button systems and methods in accordance with embodiments comprise using a communication mobile devise such as a phone or smartphone triggered by scanning one or more communication tag or code such as an NFC tag or scanning a QR code to provide a convenient and efficient way for individuals to call for help in emergency situations. [0008]Advantageously, the systems and methods can be easily installed and used, and provide relevant information to a panic button server to facilitate an effective response. The systems and methods, in accordance with embodiments, can be used in a variety of settings, such as homes, schools, kindergartens, workplaces, and public places, to improve safety and security for individuals. [0009]There is provided, in accordance with embodiments, a panic button system comprising: at least one NFC (Near Field Communication) tag or QR code, wherein said NFC tag or QR code comprises data, said data comprises one or more of, Uniform Resource Locator (URL), location of said NFC tag or QR code; a mobile communication device, said mobile communication device comprising: a wireless communication circuitry to communicate with a remote server; a processor, and an NFC unit in communication with the processor; wherein, upon recognition of the NFC tag or QR code by the NFC unit, the NFC unit cause the processor to: download an emergency alarm application from the remote server; and activate the emergency alarm application, thereby activating an emergency alarm. [0010]In an embodiment, the download process comprises an instruction to the processor to: retrieve the URL associated with the NFC tag or QR code; cause the emergency alarm application to be opened on the user device; automatically direct the browser application to load the URL retrieved from the NFC tag or QR code; and initiate an alarm signal using said emergency alarm application. [0011]In an embodiment, the emergency alarm application is a web-based application. -3- PT001/IL id="p-12" id="p-12"

[0012]In an embodiment, the mobile communication device is a mobile phone device or a smartphone. [0013]In an embodiment, the web-based application is configured to send an emergency message to a preconfigured set of contact entities. [0014]In an embodiment, the activation is triggered by the mobile communication device scanning the NFC tag or QR code. [0015]In an embodiment, the processor is configured to authenticate the user device based on a predetermined authentication protocol. [0016]In an embodiment, the mobile phone device or smartphone comprises: one or more Operating systems such as iOS or Android that support said application;a Memory unit configured to store said application and any data associated with it; Input or output devices: comprising a display screen, speaker, and microphone to provide input and output to a user; Connectivity: The mobile phone device should have the ability to connect to the internet (either through a cellular network or Wi-Fi) to download and install the application, and to communicate with external systems; One or more sensors selected from the group consisting of: GPS, accelerometer, camera. [0017]According to another embodiment of the invention there is provided a panic button system, said system comprising: a mobile communication device comprising a processor and wireless communication circuitry to couple to NFC tag or QR Code and communicate with a remote server, the processor comprising instructions to recognize an NFC tag or QR code using the NFC unit; and cause the processor to: upon recognition of the NFC tag or QR code, cause the processor to: download the emergency alarm application from the remote server and activate the application, thereby activating the emergency alarm. [0018]According to another embodiment of the invention there is provided an NFC (Near Field Communication) tag or QR code configured to trigger an alarm in case of an emergency using a mobile phone, said phone is enabled to scan the NFC tag or QR code and open a URL in the browser upon recognition. [0019]According to another embodiment of the invention there is provided mobile communication device comprising a computer software product, comprising a non-transitory computer-readable medium in which program instructions are stored, which instructions, when read by a computer, cause the computer, upon recognition of an NFC tag or QR code, to automatically: download an -4- PT001/IL emergency alarm application from a remote server; and activate the emergency alarm application, thereby activating an emergency alarm. [0020]According to another embodiment of the invention, there is provided An NFC (Near Field Communication) tag or QR code, for initiating an emergency signal, wherein said NFC tag or QR code comprises data, said data comprises one or more of, URLs, location of said NFC tag or QR code; and wherein said NFC tag or QR code are configured to trigger an emergency alarm application from a remote server and activate the application, thereby activating an emergency alarm. BRIEF DESCRIPTION OF THE DRAWINGS [0021]A better understanding of the features and advantages of the present disclosure will be obtained by reference to the following detailed description that sets forth illustrative embodiments, in which the principles of embodiments of the present disclosure are utilized, and the accompanying drawings. [0022] FIG. 1 shows a schematic diagram of a panic button system, in accordance with embodiments; [0023] FIG. 2 shows a flowchart of a method for activating a panic button using a mobile communication device without requiring a pre-installed application, in accordance with embodiments; [0024] FIG. 3 shows another flowchart of a method for activating a panic button using a mobile communication device without requiring a pre-installed application, in accordance with embodiments; [0025] FIG. 4 shows an example of a panic button, including a tag and code in accordance with embodiments; [0026] FIGs. 5 and 7 show a screenshot of an alert message, in accordance with embodiments; [0027] FIGs. 6 and 8 show a screenshot video of the user once the panic button is activated, in accordance with embodiments; and [0028] FIGs 9 and 10 show panic alert screenshots including a map and location pointer of the call in accordance with embodiments. DETAILED DESCRIPTION OF THE INVENTION -5- PT001/IL id="p-29" id="p-29"

[0029]In the following description, various aspects of the invention will be described. For the purposes of explanation, specific details are set forth in order to provide a thorough understanding of the invention. It will be apparent to one skilled in the art that there are other embodiments of the invention that differ in details without affecting the essential nature thereof. Therefore, the invention is not limited by that which is illustrated in the figure and described in the specification, but only as indicated in the accompanying claims, with the proper scope determined only by the broadest interpretation of said claims. [0030]As used herein, like characters refer to like elements. [0031]The present invention, in some embodiments thereof, relates to activating an emergency alarm such as a panic button or panic alert (e.g. a virtual or electronic panic alert) using mobile communication devices, without requiring a pre-installed application. Specifically, the present invention enables the use of a mobile communication device, such as any modern smartphone without requiring the installation or use of a specific application. As a result, it is possible for anyone such as layman to activate the panic alert with ease and without the need for any prior preparation or training. [0032]The systems and methods, in accordance with embodiments, include utilizing hardware and software of the mobile communication devices to enable users to quickly and easily signal for help in emergency situations. [0033]In accordance with embodiments the systems and devices include: a mobile communication device(e.g. a smartphone), a communication tag such as Near-field communication (NFC) tag or Quick Response (QR) code, and a panic button server. In operation, the panic button can be activated by scanning an NFC tag or QR Code, which triggers the browser to send a distress signal to the panic button server. The server receives the signal and sends a notification to the designated contacts with the panic location and other relevant information. [0034]In some embodiments, a direct video conversation is opened between the user and an emergency response call center. The video call may be recorded and saved on the server. [0035] FIG. 1 shows a schematic diagram of a panic button system 100, in accordance with embodiments. In many embodiments, the panic button system 100 comprises one or more mobile communication devices such as mobile communication device 110 (e.g. smartphones) which may communicate with one or more communication tags or codes 102 such as Near-field communication (NFC) tag 103 or Quick Response (QR) code 104. -6- PT001/IL id="p-36" id="p-36"

[0036]In accordance with embodiments, the tags or codes 102 comprise a specific and unique URL as described herein. [0037] The mobile communication device 110 (e.g. smartphone) may be in wireless communication 116 with a cloud based panic button server 118. [0038]In some cases, the server 118 comprises a processor and a memory storage, which may store one or more of data assets and/or database 117. Memory may also store a plurality of media recordings such as personal recordings of different users that processor has received from user clients. In some embodiments, server 118 may be a cloud-based server. Typically, server 118 comprises a suitable general-purpose computer (or a cluster of such computers), which has been programmed in software to carry out the functions that are described herein. This software may be downloaded to the mobile communication device 110 in electronic form, over a network 128, for example. Additionally or alternatively, the software may be stored on tangible, non-transitory computer-readable media, such as magnetic, optical, or electronic memory media. [0039]Server 118 communicates over a network 128 with multiple devices such as the mobile communication device 110. Typically, network 128 comprises the public Internet, and server 118 communicates with the devices (e.g. device 110) via a suitable Web interface, as is known in the art. Alternatively, the server and clients may communicate using any other suitable sort of network and interface. [0040]Mobile communication device may include video and audio interfaces and computing capabilities needed to interact with server 118 . By way of example, device 110 comprises one or more processors , memory, video display and speakers , along with a video camera and microphone for recording. [0041]More specifically, the mobile communication device 110, in accordance with embodiments, may be a smart phone. A smartphone is a type of mobile device that combines the functionality of a phone and a computer. Smartphones typically have a touchscreen display and can run various software applications, also known as apps, which can perform a wide range of functions, such as web browsing, email, social media, messaging, and multimedia playback. In addition to traditional cellular voice and data communication, smartphones can also connect to Wi-Fi and other wireless networks, enabling users to access the internet and other devices. [0042]Smartphones run some type of operating system, as the operating system provides the framework for the device to function and run applications. Some popular operating systems include -7- PT001/IL Android, by Google, which is the most widely used mobile operating system in the world and iOS, by Apple, which is exclusive to Apple's devices, including the iPhone, iPad, and iPod Touch. [0043]In accordance with embodiments, the mobile communication device 100 may include wireless communication technology that enables the mobile communication device to exchange data over short distances such as an NFC unit which is in communication with the processor. [0044]Near Field Communication (NFC) is a wireless communication technology that enables devices to exchange data over short distances, typically within a few centimeters. NFC is commonly used for contactless payments, mobile ticketing, and other applications that require secure and convenient data exchange. [0045]NFC technology relies on two-way communication between two devices, known as an initiator and a target. The initiator generates a radio frequency (RF) field that the target can detect and use to establish a connection. Once a connection is established, data can be exchanged between the two devices. [0046]An NDEF (NFC Data Exchange Format) formatted tag is a type of NFC tag that can store and transmit data using the NDEF data format. NDEF is a standardized data format that enables interoperability between different NFC devices, allowing them to exchange data in a consistent and predictable way. [0047]NDEF formatted tags can store various types of data, including text, URLs, contact information, and other types of binary data. When an NFC-enabled device comes into range of an NDEF tag, it can read the data stored on the tag and perform various actions, such as launching a website, displaying text, or initiating a phone call. [0048]If an NDEF formatted tag contains a URL, reading the tag with a smartphone will typically open the URL in a web browser. [0049]A QR code is a two-dimensional barcode that can be scanned using a mobile communication device 110 (e.g. smartphone) camera or other QR code reader. QR codes can contain various types of data, including for example text, URLs, and other binary data. [0050]If a QR code contains a URL, scanning the code with a smartphone camera will typically open the URL in a web browser. [0051]The system and method of the present invention may use and may include various types of mobile communication devices, NFC and QR codes. -8- PT001/IL id="p-52" id="p-52"

[0052]In operation, a web-based panic button application 150 is automatically loaded from the web server 118, for example by URL and receives one or more parameters, for example, a single query parameter – location ID, which is contained for example in the URL after the question mark. When a user activates the panic button in his mobile communication device by accessing the application 1(e.g. via URL), an alert is sent to the server 118, which can then trigger a response from emergency services or designated contacts. [0053]In some cases, in addition to sending an alert, the application 150 can also provide the option for the user to establish a video call with the emergency services or designated contacts. This can provide a more direct and effective means of communication, allowing the user to provide real-time information about their situation and receive guidance or assistance from emergency responders. [0054]In accordance with some embodiments, to establish a video call, the application 150 uses WebRTC (Web Real-Time Communication) technology, which allows for real-time audio and video communication within web browsers. It is stressed that other technologies may be used. For example, application 150 requests access to the user's camera and microphone and then establishes a secure connection with the emergency services or designated contacts. [0055]The web-based emergency call center application 160 is a software application that allows emergency call center operators to receive, manage, and respond to emergency calls. The application can be accessed through a web browser and can be used by call center operators to quickly and efficiently manage emergency calls and dispatch emergency services. [0056]In accordance with embodiments, upon receiving a panic alert, application 160 sounds a loud siren and presents a user with all information available for the triggered alert. This information includes for example, one or more of: the name and the address of the facility, relevant contacts, phone numbers, etc. This information is received from the panic button server (e.g. server 118) and retrieved from database 117 by looking for the location ID, provided in the panic alert. [0057]In accordance with some embodiments, in addition to managing and responding to emergency calls, the application 150 can also provide the option for the user to establish a video call with the user, that triggered the panic alert. [0058]A panic button web server 118, in accordance with embodiments, is a software application that receives and processes panic button requests from users, through the web-based panic button application 150. The server 118 is designed to receive a location ID and retrieve from its database -9- PT001/IL 117 data such as the location data, user information, and other relevant details, which can be used to quickly and accurately alert emergency services or designated contacts in the event of an emergency. [0059]When a user activates the panic button, the web-based application 150 sends a request to the panic button web server 118. The request contains for example the location ID, where the panic button has been triggered. The panic button server application 150 will look up database 117 for the received location ID and retrieve all available information about that location, as well as the list of designated contacts to be notified upon the panic button alert at that location. The application will then send email and text (SMS) notifications 119 to these contacts and call their phones with a pre-recorded voice message, notifying these contacts about the alert. [0060]In some cases, the application 150 will also trigger a panic alert on the web-based call center 180 application, using for example WebSocket technology. [0061]The NFC tag 103 or QR code 104 are used to trigger the web-based panic button application 150. The tag or code can be placed in a visible and accessible location, such as on a wall or a desk. Handling the panic button alert on the panic button server [0062]In accordance with embodiments, as illustrated in FIG. 1 The panic button server 1includes several components: 1. It serves a web-based panic button application; mobile communication devices such as smartphones can be loaded by scanning (or manually browsing) the URL from NFC tag or QR Code. 2. It serves a web-based emergency call center application, used to receive panic buttons alerts, respond and communicate with the user that initiated a panic alert. 3. It notifies designated contacts upon receiving a panic button alert 4. It integrates with external systems, handling panic button alerts in the field, dispatching units and provide emergency response services. 5. It records video calls between the emergency response call center and the user that initiated a panic alert id="p-63" id="p-63"

[0063]The panic button server 118 comprises a storage unit such as database 117 comprising panic button location IDs, containing the relevant information about each location. This information includes a list of designated contacts that should be notified upon a panic button alert in each location. [0064]In some cases, there might be some contacts that will be notified on every single panic button alert, regardless of their location or contacts, notified upon a group of locations. These contacts will receive an email and a text message (SMS), stating the panic button alert as well as the information, -10- PT001/IL retrieved from the database using the location ID. Also, these contacts will receive a phone call with a pre-recorded message, notifying about the panic alert and asking to read the text message with all the information. [0065]In accordance with embodiments, the panic button server 118 interacts with a web-based emergency response call center application 160. The call center application 160 will receive an instant push notification, using for example WebSocket technology upon the server receiving a panic alert. This notification will contain the information, retrieved from the database using the location ID of the panic alert as well as the unique device ID, received from the panic button application, in order to establish a video call between the user and the call center. [0066]In accordance with embodiments, the panic button server retrieves the unique device ID, received from the panic button application, in order to establish and record the video call between the user and the call center. The recorded call will be saved and available for future investigation of the panic alert, as well as being used as evidence. [0067]The panic button server integrates with external systems, such as call center applications or field service management solutions to provide assistance, dispatch units, etc. Responding to the panic button alert in the call center [0068]The web-based emergency response call center application 160 enables a call center to handle panic button alerts, received from users, initiating these alerts. [0069]In some cases, for example by default, the application shows a live dashboard with a map to the emergency call center responders. As soon as a panic button alert is triggered, the dashboard will immediately show a popup notification, displaying the information about the alert, including its exact location on the map and the information retrieved by the panic button server from the database using the location ID. This information as shown in FIGs 6-10 includes for example the facility name, the location of the panic button inside the facility, relevant contact phone numbers, access information, etc. [0070]The dashboard sounds a loud siren when a new panic button alert is displayed. This siren can be manually silenced by the responder, handling the alert. Also, in some cases, the siren will be automatically silenced when the responder asks to establish a video call with the user that triggered the panic alert. [0071]In some cases, the call center response user has the option to establish a video call with the user, triggered the panic button alert as shown in FIGs. 6 and 8. The video call supports two-way -11- PT001/IL video and audio, so the responders can communicate with the user, triggered the alert and help. For the video call, the application uses for example WebRTC (Web Real-Time Communication) technology, which allows for real-time audio and video communication within web browsers. In case multiple responders connect to the call, a video conference is created in such a way that all parties can see and hear each other. The entire video call, featuring all participants, is recorded on the panic button server and the recording is stored for future access at any time. In accordance with embodiments, Upon handing situation, the response user can close the triggered panic button alert by providing the alert status, such as real alert, testing, triggered by mistake, etc. as well as a written summary. This information is sent back to the panic button server 118, that will save it in the database, together with the recording of the video call for future records. In accordance with some embodiments, a history of the triggered alerts can be retrieved in the emergency response call center application when required. [0072]FIG. 2 shows a flowchart 200 of a method for activating a panic button using a mobile communication device without requiring a pre-installed application, in accordance with embodiments. When the user scans the tag 103 or code 104 using for example the smartphone 110, then at step 210 upon recognition of the NFC tag or QR code by the NFC unit of the mobile communication devices, causes or triggers (e.g. automatically) the processor of the mobile communication device to download at step 220 the web-based panic button application 150 from the web server 118 by opening, for example, a URL, encoded in the QR code or NFC tag. [0073]The URL contains for example three parts: the application web address which is common to all customers and panic buttons, customer identifier used to identify an organization or the emergency call center responding to this panic alert and the location ID used to identify the specific panic button triggering the alert. [0074]Optionally, in some embodiments, at step 230 once loaded, the web-based panic button application 150 immediately starts a count down, for example counting from 5 to 0 in order to allow the user to cancel the alert in case it has been triggered by mistake. Upon finishing the count to zero, at step 240 the application sends a distress signal to the panic button server 118. The distress signal contains known customer and panic button identifiers, taken for example from the URL, encoded in the QR code or NFC tag as well as a unique device ID. The device ID is generated within the panic button application using for example UUID (Universally Unique Identifier) and stored in the browser’s local storage or database 117. -12- PT001/IL id="p-75" id="p-75"

[0075]In case the same mobile communication device has already used the panic button application 150 in the past, the original device ID will be retrieved from the browser’s local storage instead of generating a new one. This device ID will be used by the call center to instantiate a video call with the user, triggering the panic alert. [0076]At step 250, The panic button server 118 receives the distress signal from the user's mobile communication device 110 and sends a notification to the designated contacts. The notification includes the user's location and other relevant information. The server also notifies an emergency response call center and enables initiating a video conversation between the call center and the user trigged the panic alert. [0077] FIG. 3 shows another flowchart of a method for activating a panic button using a mobile communication device without requiring a pre-installed application, in accordance with embodiments; Triggering the panic alert [0078]FIG. 4 shows an example of a panic button 300, including a tag (e.g. NFC tag 303) and code (e.g. QR code 304) in accordance with embodiments. In every location, a panic button is required, there is a sign installed in a visible place, such as on the wall or at the desk. In some case, on this sign, or in proximity to the sign there are user instructions as well as a QR code and NFC tag. [0079]In some cases, the NFC tag is formatted as NDEF URL data tag. This allows saving a web URL link into the tag. The QR Code contains the same URL as the NFC tag. [0080]In accordance with some embodiments, Each pair of NFC and QR Code (e.g. 303 and 304) are sharing the same URL, which identifies a unique panic button location ID. This is done by encoding three components in the URL: panic button server’s web address, customer ID and a unique location ID. The location ID is set in the URL using query parameters, while the customer ID is a part of the path. The location ID will be then used in the panic button server to retrieve all relevant and available information about the location of the panic button 300. [0081]In accordance with some embodiments, in operation, to scan an NFC tag, the user must unlock his mobile communication device ( e.g. smartphone 310) and place the back or the top of the smartphone near the NFC tag 303. The device will automatically read the information from the tag. As the tag contains a URL, the smartphone will open a browser and automatically browse to the web address encoded in that URL. Some devices might ask the user to confirm the browsing request. -13- PT001/IL id="p-82" id="p-82"

[0082]In accordance with some embodiments, in operation, to scan a QR code, the user must unlock his smartphone and open the devices’ camera. The user must then point the viewfinder of the camera to the QR code. The camera application will automatically recognize the QR code and present the user with the URL. Tapping on the URL will open a browser and automatically browse to the web address encoded in that URL. [0083]The browser will connect to the panic button server (as explained in flowchart 200 of FIG. 2) and load a web-based application, presenting the applications user interface, which does not require any further interaction with the user in order to report a panic alert. In some cases, the application will count back for example from 5 to 0 in order to allow the user cancelling the panic button, in case the user is just testing the service. Once counted to zero, the panic alert will be triggered by sending a command to the server, together with the location ID, taken from the URL as well as a random and unique device ID, generated for the current session. This device ID will be used in the emergency call center application to establish a video call with the user. [0084]In accordance with some embodiments, upon triggering the panic button alert, the client’s application will load a web-based video call screen as shown for example in FIGs 6 and 8, utilizing for example a WebRTC technology. The application will use the device ID, sent to the panic button server to allow emergency responders to connect to the video call. [0085]In accordance with embodiments, the application will stay in the video calling screen, waiting for the call from the call center, unless the user decides to leave the application by closing the browser or browsing to another URL. [0086] FIGs. 5 and 7 show a screenshot of an alert massage, in accordance with embodiments; [0087] FIGs. 6 and 8 show a video of the user once the panic button is activated, in accordance with embodiments; and [0088] FIGs 9 and 10 show panic alert screenshots including a map and location pointer of the call in accordance with embodiments. [0089]In further embodiments, the processing unit may be a digital processing device including one or more hardware central processing units (CPU) that carry out the device’s functions. In still further embodiments, the digital processing device further comprises an operating system configured to perform executable instructions. In some embodiments, the digital processing device is optionally connected to a computer network. In further embodiments, the digital processing device is optionally connected to the Internet such that it accesses the World Wide Web. In still further embodiments, the -14- PT001/IL digital processing device is optionally connected to a cloud computing infrastructure. In other embodiments, the digital processing device is optionally connected to an intranet. In other embodiments, the digital processing device is optionally connected to a data storage device. [0090]Those of skill in the art will recognize that many smartphones are suitable for use in the system described herein. Those of skill in the art will also recognize that select televisions with optional computer network connectivity are suitable for use in the system described herein. Suitable tablet computers include those with booklet, slate, and convertible configurations, known to those of skill in the art. [0091]In some embodiments, the digital processing device includes an operating system configured to perform executable instructions. The operating system is, for example, software, including programs and data, which manages the device’s hardware and provides services for execution of applications. [0092]In some embodiments, the digital processing device includes an input device to receive information from a user. In some embodiments, the input device is a keyboard. In some embodiments, the input device is a pointing device including, by way of non-limiting examples, a mouse, trackball, track pad, joystick, game controller, or stylus. In some embodiments, the input device is a touch screen or a multi-touch screen. In other embodiments, the input device is a microphone to capture voice or other sound input. In other embodiments, the input device is a video camera to capture motion or visual input. In still further embodiments, the input device is a combination of devices such as those disclosed herein. [0093]The functionality of the computer readable instructions may be combined or distributed as desired in various environments. In some embodiments, a computer program comprises one sequence of instructions. In some embodiments, a computer program comprises a plurality of sequences of instructions. In some embodiments, a computer program is provided from one location. In other embodiments, a computer program is provided from a plurality of locations. In various embodiments, a computer program includes one or more software modules. In various embodiments, a computer program includes, in part or in whole, one or more web applications, one or more mobile applications, one or more standalone applications, one or more web browser plug-ins, extensions, add-ins, or add-ons, or combinations thereof. In some embodiments, a computer program includes a mobile application provided to a mobile digital processing device. In some embodiments, the mobile application is provided to a mobile digital processing device at the time it is manufactured. In other -15- PT001/IL embodiments, the mobile application is provided to a mobile digital processing device via the computer network described herein. [0094]In some embodiments, the system disclosed herein includes software, server, and/or database modules, or use of the same. In view of the disclosure provided herein, software modules are created by techniques known to those of skill in the art using machines, software, and languages known to the art. The software modules disclosed herein are implemented in a multitude of ways. In various embodiments, a software module comprises a file, a section of code, a programming object, a programming structure, or combinations thereof. In further various embodiments, a software module comprises a plurality of files, a plurality of sections of code, a plurality of programming objects, a plurality of programming structures, or combinations thereof. In various embodiments, the one or more software modules comprise, by way of non-limiting examples, a web application, a mobile application, and a standalone application. In some embodiments, software modules are in one computer program or application. In other embodiments, software modules are in more than one computer program or application. In some embodiments, software modules are hosted on one machine. In other embodiments, software modules are hosted on more than one machine. In further embodiments, software modules are hosted on cloud computing platforms. In some embodiments, software modules are hosted on one or more machines in one location. In other embodiments, software modules are hosted on one or more machines in more than one location. [0095]In the above description, an embodiment is an example or implementation of the inventions. The various appearances of "one embodiment," "an embodiment" or "some embodiments" do not necessarily all refer to the same embodiments. [0096]Although various features of the invention may be described in the context of a single embodiment, the features may also be provided separately or in any suitable combination. Conversely, although the invention may be described herein in the context of separate embodiments for clarity, the invention may also be implemented in a single embodiment. [0097]Reference in the specification to "some embodiments", "an embodiment", "one embodiment" or "other embodiments" means that a particular feature, structure, or characteristic described in connection with the embodiments is included in at least some embodiments, but not necessarily all embodiments, of the inventions. [0098]It is to be understood that the phraseology and terminology employed herein is not to be construed as limiting and are for descriptive purpose only. -16- PT001/IL id="p-99" id="p-99"

[0099]The principles and uses of the teachings of the present invention may be better understood with reference to the accompanying description, figures and examples. [00100]It is to be understood that the details set forth herein do not construe a limitation to an application of the invention. [00101]Furthermore, it is to be understood that the invention can be carried out or practiced in various ways and that the invention can be implemented in embodiments other than the ones outlined in the description above. [00102]It is to be understood that the terms "including", "comprising", "consisting" and grammatical variants thereof do not preclude the addition of one or more components, features, steps, or integers or groups thereof and that the terms are to be construed as specifying components, features, steps or integers. [00103]If the specification or claims refer to "an additional" element, that does not preclude there being more than one of the additional element. [00104]It is to be understood that where the claims or specification refer to "a" or "an" element, such reference is not be construed that there is only one of that element. It is to be understood that where the specification states that a component, feature, structure, or characteristic "may", "might", "can" or "could" be included, that particular component, feature, structure, or characteristic is not required to be included. Where applicable, although state diagrams, flow diagrams or both may be used to describe embodiments, the invention is not limited to those diagrams or to the corresponding descriptions. For example, flow need not move through each illustrated box or state, or in exactly the same order as illustrated and described. Methods of the present invention may be implemented by performing or completing manually, automatically, or a combination thereof, selected steps or tasks. [00105]The descriptions, examples, methods and materials presented in the claims and the specification are not to be construed as limiting but rather as illustrative only. Meanings of technical and scientific terms used herein are to be commonly understood as by one of ordinary skill in the art to which the invention belongs, unless otherwise defined. The present invention may be implemented in the testing or practice with methods and materials equivalent or similar to those described herein. [00106]While the invention has been described with respect to a limited number of embodiments, these should not be construed as limitations on the scope of the invention, but rather as exemplifications of some of the preferred embodiments. Other possible variations, modifications, and applications are also within the scope of the invention. Accordingly, the scope of the invention should -17- PT001/IL not be limited by what has thus far been described, but by the appended claims and their legal equivalents. All publications, patents and patent applications mentioned in this specification are herein incorporated in their entirety by reference into the specification, to the same extent as if each individual publication, patent or patent application was specifically and individually indicated to be incorporated herein by reference. In addition, citation or identification of any reference in this application shall not be construed as an admission that such reference is available as prior art to the present invention. To the extent that section headings are used, they should not be construed as necessarily limiting.

Claims (12)

1.CLAIMS WHAT IS CLAIMED IS: 1. A panic button system comprising: at least one NFC (Near Field Communication) tag or QR code, wherein said NFC tag or QR code comprises data, said data comprises one or more of, Uniform Resource Locator (URL), location of said NFC tag or QR code; a mobile communication device, said mobile communication device comprising: a wireless communication circuitry to communicate with a remote server; a processor, and an NFC unit in communication with the processor; wherein, upon recognition of the NFC tag or QR code by the NFC unit, the NFC unit cause the processor to: download an emergency alarm application from the remote server; and activate the emergency alarm application, thereby activating an emergency alarm.

2. The system of claim 1 wherein said download comprises instructions to the processor to: retrieve the URL associated with the NFC tag or QR code; cause the emergency alarm application to be opened on the mobile communication device; automatically direct the emergency alarm application to load the URL retrieved from the NFC tag or QR code; and initiate an alarm signal using said emergency alarm application.

3. The system of claim 2 wherein said browser application is a web-based application.

4. The system of claim 1 wherein the mobile communication device is a mobile phone device or a smartphone.

5. The system of claim 3 wherein the emergency alarm application is configured to send an emergency message to a preconfigured set of contact entities.

6. The system of claim 1 wherein the activation being triggered by the user device scanning the NFC tag or QR code.

7. The system of claim 1 wherein the processor is configured to authenticate the user device based on a predetermined authentication protocol.

8. The system of claim 4 wherein the mobile phone device or smartphone comprises: one or more operating systems such as iOS or Android that support said application;a memory unit configured to store said application and any data associated with it; Input or output devices: comprising a display screen, speaker, and microphone to provide input and output to a user; connectivity: the ability to connect to the internet either through a cellular network or Wi-Fi to download and install the application, and to communicate with external systems; one or more sensors selected from the group consisting of: GPS, accelerometer, camera.

9. A panic button system, said system comprising: a mobile communication device comprising a processor and wireless communication circuitry to couple to NFC tag or QR Code and communicate with a remote server, the wherein the mobile communication device is configured to: recognize an NFC tag or QR code using the NFC unit; and cause the processor upon recognition of the NFC tag or QR code to: download an emergency alarm application from the remote server and activate the application, thereby activating the emergency alarm.

10. An NFC (Near Field Communication) tag or QR code, for initiating an emergency signal, wherein said NFC tag or QR code comprises data, said data comprises one or more of, URLs, location of said NFC tag or QR code; and wherein said NFC tag or QR code are configured to trigger an emergency alarm application from a remote server and activate the application, thereby activating an emergency alarm.

11. An NFC (Near Field Communication) tag or QR code configured to trigger an alarm in case of an emergency using a mobile phone, enabled to scan the NFC tag or QR code and open a URL in the browser upon recognition.

12. A mobile communication device comprising a computer software product, comprising a non-transitory computer-readable medium in which program instructions are stored, which instructions, when read by a computer, cause the computer, upon recognition of an NFC tag or QR code, to automatically: download an emergency alarm application from a remote server; and activate the emergency alarm application, thereby activating an emergency alarm.