A WEARABLE DEVICE FOR PERFORMING FUNCTIONS BASED ON ZONES
FIELD OF INVENTION
[001] The present disclosure relates to a field of wearable devices. More specifically, the present disclosure relates to a wearable device and a method of configuring the wearable device to execute various functions.
BACKGROUND
[002] It is known that users perform variety of tasks in a day-to-day life. With advent in technology, the user has to depend on variety of devices to perform each task. For instance, consider a user in a closed facility such as an office space where the user has to perform variety of tasks using various devices. In one example, the user may have to use an Identification Card (ID) comprising a Radio-frequency identification (RFID) tag to gain access to a room. In other example, the user may have to use a biometric system such as a fingerprint scanner to gain access to a room. Further, RFID tags may also be used to define a position the user in the closed facility. More specifically, a plurality of RF receivers is employed to determine the position of the user.
[003] Furthermore, if the user has to make payment towards any transaction performed, then the user may have to use his/her credit or debit card or any other payment mechanism. Furthermore, the user has to use a separate device to raise an alarm in case of an emergency or to alert someone of the situation. Similarly, there could be many devices that are used to perform different tasks.
[004] Based on the above, it is understood that the user has to carry a device for performing each of the task. In other words, as the functionalities that are to be performed in day-to-day life increase, the user has to carry many devices to execute each of the functionalities.

[005] Several methods have been proposed in the past to address the problems discussed above. None of them, however, disclose a device that can perform variety of functions and avoids the need to carry multiple devices.
[006] Applicant believes that a related reference corresponds to a United States patent application 20170024713. US20170024713 discloses a wearable device and system for event administration and event related transactions. A wearable device with unique identification may be given to each attendee of the event. The attendee may use the wearable device to perform one or more tasks in a facility. For example, the user may use the wearable device to gain access to various parts of the event. Further, the user may use the wearable device to make purchases at various vendors or merchants in the facility. The reference discloses that the user may press a plurality of buttons provided on the wearable device to perform the tasks described above. However, the reference differs from the present application because the system disclosed in US20170024713 allows the user to perform very limited functionalities i.e., allow access and make payment. Further, US20170024713 discloses use of multiple buttons to perform the tasks. It must be noted that if the user must perform more tasks, then more buttons must be provided on the wearable device which makes the wearable complex and bulky. Further, it is very difficult to configure each button to execute variety of functions. To perform additional tasks, the user may still have to carry multiple devices as in the past.
[007] Other documents describing the closest subject matter for a number of more or less complicated features fail to solve the problems in an efficient and economical way. None of the patents suggest the novel features of the present invention.
SUMMARY
[008] This summary is provided to introduce concepts related to a wearable device for performing a plurality of functions based on zones and the concepts are further described below in the detailed description. This summary is not intended to identify essential features of the claimed subject matter nor is it intended for use in determining or limiting the scope of the claimed subject matter.

[009] An example of a method for performing a plurality of functions by a wearable device based on zones is disclosed. The method comprises identifying, by the wearable device, a first sensor and a second sensor. The first sensor and the second sensor are placed at a first zone and a second zone, respectively. The method further comprises configuring the wearable device to perform a first function and a second function based on at least one of a first mode and a second mode. The first mode indicates configuring the wearable device to perform the first function or the second function without user intervention. The second mode indicates configuring the wearable device to perform the first function or the second function upon receiving an input on the wearable device by the user. The wearable device is configured to perform the first function when in proximity to the first sensor. The wearable device is configured to perform the second function when in proximity to the second sensor. The method further comprises determining proximity of the wearable device to one of the first sensor and the second sensor. The method further comprises executing, by the wearable device, the first function and the second function based on the first mode or the second mode. The first function is executed when the wearable device comes in proximity to the first sensor. The second function is executed when the wearable device comes in proximity to the second sensor.
[0010] Another example of a method for performing a plurality of functions based on zones is disclosed. The method comprises identifying, by a server, a first sensor and a second sensor. The first sensor and the second sensor are identified with respect to a first zone and a second zone, respectively. The method further comprises identifying, by the server, a location of a wearable device being in proximity to the first sensor or the second sensor. The method further comprises instructing, by the server, the wearable device to execute a first function and a second function based on at least one of a first mode and a second mode of the wearable device. The first mode indicates configuring the wearable device to perform the first function or the second function without user intervention. The second mode indicates configuring the wearable device to perform the first function or the second function upon receiving an input on the wearable device by the user. The wearable device is instructed to perform the first function when in proximity to the first sensor. The wearable device is instructed to perform the second function when in proximity to the second sensor. The method further comprises executing, by the wearable device,

the first function and the second function based on the instructions received from the server. The first function is executed when the wearable device comes in proximity to the first sensor. The second function is executed when the wearable device comes in proximity to the second sensor.
[0011] A wearable device for performing a plurality of functions based on zones is disclosed. The wearable device comprises an input means, a memory and a processor coupled to the memory. The processor executes program instructions stored in the memory to identify a first sensor and a second sensor. The first sensor and the second sensor are placed at a first zone and a second zone, respectively. The processor further determines a first function and a second function based on at least one of a first mode and a second mode. The first mode indicates configuring the wearable device to perform the first function or the second function without user intervention. The second mode indicates configuring the wearable device to perform the first function or the second function upon receiving an input on the wearable device by the user. The processor further performs the first function and the second function based on the first mode or the second mode. The first function is performed when in proximity to the first sensor. The second function is performed when in proximity to the second sensor.
BRIEF DESCRIPTION OF FIGURES
[0012] In the following drawings like reference numbers are used to refer to like elements. Although the following figures depict various examples of the disclosure, and the disclosure is not limited to the examples depicted in the figures.
[0013] FIG. 1A illustrates an environment of a wearable device for performing functions based on zones, in accordance with one embodiment of the present disclosure;
[0014] FIG. 1B illustrates the wearable device, in accordance with one exemplary embodiment of the present disclosure;
[0015] FIGS. 2A and 2B illustrate an environment of a wearable device for performing functions based on zones, in accordance with one exemplary embodiment of the present

disclosure;
[0016] FIG. 3 shows a method of performing a plurality of functions based on zones is shown, in accordance with one embodiment of the present disclosure;
[0017] FIG. 4 illustrates an environment of a wearable device for performing functions based on zones, in accordance with one embodiment of the present disclosure;
[0018] FIG. 5 shows a method of booking the conference room using the wearable device, in accordance with an exemplary embodiment of the present disclosure; and
[0019] FIG. 6 shows a method of performing functions based on zones, in accordance with another embodiment of the present disclosure.
DETAILED DESCRIPTION
[0020] The following detailed description is intended to provide example implementations to one of ordinary skill in the art, and is not intended to limit the disclosure to the explicit disclosure, as one of ordinary skill in the art will understand that variations can be substituted that are within the scope of the disclosure as described.
[0021] A wearable device for performing functions based on zones is disclosed. The wearable device is communicatively coupled to a plurality of sensors. Each sensor of the plurality of sensors is associated with a respective zone (context). The wearable device is configured to perform a plurality of functions when the wearable device comes in proximity to the sensors in the zones. In other words, the wearable device performs a different function when the wearable device comes in proximity to each sensor. The wearable device is configured based on a first mode and a second mode. The first mode indicates configuring the wearable device to perform the first function or the second function without user intervention. In other words, when the wearable device is configured in the first mode and the user comes in proximity to the first sensor, then the first function is automatically executed by the wearable device without

intervention by the user. The second mode indicates configuring the wearable device to perform the first function or the second function upon receiving an input on the wearable device by the user. In others words, when the wearable device is configured in the second mode and the user comes in proximity to the first sensor, then the user has to provide the input e.g., press a button provided on the wearable device to execute the first function. The input may be received from one of hard button, soft button, touch input, and so on. The various embodiments of performing different functions by the wearable device are explained in detail with the help of FIGS 1A-6.
[0022] Referring to FIG. 1A, an environment 100 illustrating a wearable device 105 connected to a sensor 130 for performing a function based on a zone Z is shown, in accordance with one embodiment of the present disclosure. The wearable device 105 may be provided in the form of a wrist watch, a necklace, chain or an identification tag or in any other form that a user may wear on his body.
[0023] In one embodiment, the wearable device 105 may include at least one first processor 110, an I/O interface 115 and a first memory 120. The at least one processor 110 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the at least one first processor 110 is configured to fetch and execute computer-readable instructions stored in the first memory 120.
[0024] The I/O interface 115 may include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, and the like. The I/O interface 115 may enable the wearable device 105 to communicate with other computing devices, such as web servers, electronic devices, and external data servers (not shown). The I/O interface 115 may facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example, LAN, cable, Universal Serial Bus (USB), etc., and wireless networks, such as WLAN, cellular, Bluetooth, Machine-to-Machine (M-2-M) protocol, Near Field communication (NFC), Wi-Fi, Li-Fi, Infrared and so on. It should be understood that the wearable device 105 may include a transceiver (not shown) to broadcast or receive signal to

communicate with other devices wirelessly, such as using WLAN, cellular, Bluetooth, Machine-to-Machine (M-2-M) protocol, Near Field communication (NFC), Wi-Fi, Li-Fi, Radio Frequency Identification (RFID), Infrared and so on. The I/O interface 115 may include one or more ports for connecting several devices to one another or to another server.
[0025] The first memory 120 may include any computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, Solid State Drive (SSD) and so on.
[0026] Now, referring to FIG. 1B, the wearable device 105 in the form of a wrist watch is shown, in accordance with one embodiment of the present disclosure. As can be seen, the wearable device 105 comprises an input means 125. In one example, the input means 125 may include an external component affixed to the wearable device 105. The input means 125 may include, but not limited to, a hard button, a soft button, a switch, a crown, a touch screen or touch interface, and so on. In another example, the input means 125 may include a software interface provided in the wearable device 105 to detect user actions such as gestures performed by the user, a voice based input, a biometric input and so on. The wearable device 105 may include a gesture-based controller (not shown), a biometric sensor (not shown), a voice-based controller (not shown), or associated components to detect the user actions.
[0027] As specified above, the wearable device 105 is communicatively coupled to the sensor 130. The sensor 130 may be located at the zone Z. In one example, the sensor 130 may be affixed to a wall of the zone Z. In another example, the sensor 130 may be affixed to a device such as Point of Sale (PoS) terminal device, a biometric device, electrical equipment and so on present at the zone Z. In yet another example, the sensor 130 may be integrated into a device, e.g., an electronic door lock. The sensor 130 may be integrated into the device at the time of manufacturing.
[0028] In one embodiment, the sensor 130 may include at least one second processor 135 and a

second memory 140. The at least second processor 135 may be implemented as one or more microprocessors, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the at least one second processor 135 is configured to fetch and execute computer-readable instructions stored in the second memory 140.
[0029] The second memory 140 may include any computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read only memory (ROM), erasable programmable ROM and flash memories.
[0030] The sensor 130 is capable of communicating with other devices wirelessly, such as using WLAN, cellular, Bluetooth, Machine-to-Machine (M-2-M) protocol, Near Field communication (NFC), Wi-Fi, Li-Fi, Radio Frequency Identification (RFID), Infrared and so on. In order to communicate with other devices e.g., the wearable device 105, the sensor 130 uses a transceiver (not shown) to broadcast or receive signal. As such, the sensor 130 may communicate with the wearable device 105 using different protocols. In one implementation, the sensor 130 may communicate with the wearable device 105 using Bluetooth technology. In another example, the sensor 130 may communicate with the wearable device 105 using Near Field Communication (NFC) technology. In yet another example, the sensor 130 may communicate with the wearable device 105 using RFID techniques.
[0031] The sensor 130 located within the zone Z helps in estimating proximity of the wearable device 105 to the zone Z. Further, the sensor 130 is associated with a specific function. In one example, the sensor 130 may be associated with making a payment transaction. In another example, the sensor 130 may be associated with door access control. In another example, the sensor 130 may be associated with scheduling an event and so on.
[0032] In one implementation, the wearable device 105 is preconfigured with a firmware associated with the sensor 130. The firmware may include information associated with the sensor 130. The information may include, but not limited to, unique identification of the sensor 130.

The firmware may further comprise programmed instructions to execute a function when the wearable device comes in proximity to the sensor 130. The function may include, but not limited to, initiate payment, request for access control to a door, and so on.
[0033] In one implementation, the wearable device 105 is configured to function in a first mode, a second mode, or in combination thereof. When configured in the first mode, the wearable device 105 executes the function automatically when the wearable device 105 comes in proximity to the sensor 130. In the second mode, the wearable device 105 executes the function after receiving an input from the user. For example, consider that the user comes in proximity to the sensor. In order to execute the function with respect to the sensor 130, the user may have to press the input means 125. Subsequently, the wearable device 105 executes the function. It should be understood that the user presses the input means 125 with an intent to execute the function. Without the press of the input means 125, the wearable device 105 does not execute the function. Further, if the wearable device 105 is configured to execute the function in combination of the first mode and the second mode, then the function is executed with or without user intervention, when the user comes in proximity to the sensor 130.
[0034] Similarly, the sensor 130 is preconfigured with a firmware associated with the wearable device 105. The firmware may include information associated with the wearable device 105. The information may include, but not limited to, unique identification of the wearable device 105. The firmware may further comprise programmed instructions to execute a function when the wearable device 105 comes in proximity to the sensor 130. As explained above, the firmware associated with the sensor 130 is also pre-configured to function in a first mode, a second mode, and a combination thereof. In the first mode, the firmware associated with the sensor 130 is preconfigured to execute the function automatically when the wearable device 105 comes in proximity to the sensor 130. In the second mode, the firmware associated with the sensor 130 is preconfigured to execute the function based on an intent of a user of the wearable device 105. The intent of the user is determined based on the input provided received from the user by the wearable device 105 and the proximity of the wearable device 105 to the sensor 130. The function may include, but not limited to, receive or process payment, allow access to user of the wearable device 105, scheduling an event, raising an alarm, controlling Heating, Ventilation

and Air Conditioning (HVAC) control system, providing navigation, pairing one or more assets and so on.
[0035] It must be understood that the wearable device 105 may be configured to function in the first mode, the second mode, or in combination when the wearable device 105 comes in proximity to different sensors in the zone. Similarly, the sensor 130 may be configured to function in the first mode, the second mode, or in combination when different wearable devices 105 come in proximity to the sensor in the zone. Specifically, for each of the sensors 130 in the zone, the wearable device 105 is programmed to function in one of the first mode and the second mode. Similarly, the each of the sensors 130 is programmed to function in one of the first mode and the second mode corresponding to the wearable device 105 that comes in proximity to the sensors 130.
[0036] Pre-configuration of the wearable device 105 and the sensor 130 is explained using an example. In one example, consider that the sensor 130 is associated with door access control for an employee in an organization. The sensor 130 may be integrated into an electronic door lock located an entrance to the organization. The organization may issue the wearable device 105 to the employee. The wearable device 105 may be in the form of a wrist watch as shown in FIG. 1B. Further, each employee of the organization may be provided with an employee device ID. The employee device ID may be programmed into the first memory 120 of the wearable device 105, at the time of issuance. When the wearable device 105 comes in proximity to the sensor 130 for the first time, the sensor 130 configures the wearable device 105 to share the employee device ID with the sensor 130, upon detecting a single button press.
[0037] Upon configuration, the employee may use the wearable device 105 to unlock the electronic door lock. Consider that the wearable device 105 is configured to function in the first mode. As explained above, the user may wear the wearable device 105 and come in proximity to the sensor 130. When the wearable device 105 comes in proximity, the sensor 130 detects the employee device ID. Further, the sensor 130 compares the employee ID received with a plurality of employee device IDs in a database. In one example, the database is stored in the second memory 140 of the sensor 130. If the employee device ID received matches with any one of the

employee device IDs stored in the database, then the sensor 130 instructs the electronic door lock to unlock without further intervention by the user. In other words, the user is automatically provided with the access to the electronic door lock.
[0038] Consider that the wearable device 105 is configured to function in the second mode. As explained above, the user may have to press the button on the wearable device 105 to unlock the electronic door lock. In order to unlock the door, at first, the employee comes in proximity to the sensor 130. Subsequently, the employee presses the button once to transmit the employee device ID stored in the first memory 120 to the sensor 130. Further, the sensor 130 compares the employee ID received with a plurality of employee device IDs in a database. In one example, the database is stored in the second memory 140 of the sensor 130. If the employee device ID received matches with any one of the employee device IDs stored in the database, then the sensor 130 instructs the electronic door lock to unlock. Otherwise, access is restricted.
[0039] It should be noted that the electronic door lock may be locked after certain period of unlocking. The electronic door lock is locked to prevent unauthorized entry or re-entry of the same user/employee, or to avoid prolong opening of the electronic door lock. In order to unlock the electronic door lock, the above process is repeated.
[0040] In one example, the wearable device 105 is preconfigured by a user to perform a function in the second mode when in proximity to the sensor 130. In other words, the wearable device 105 is configured to perform a function, upon identifying the context, e.g., payment. In one example, the user may configure the wearable device 105 to perform a payment transaction when in proximity to sensors similar to sensor 130. In one example, similar sensors may indicate a similar context. Sensors similar to the sensor 130 may be identified based on a unique identification number (unique ID) transmitted by the sensor. For example, all sensors related to payments may have a unique ID beginning with the numbers ‘1110’.
[0041] In one example, the user may preconfigure the wearable device 105 by pairing the wearable device 105 with an external device (not shown). The external device may include at least one of a computer, a laptop, a smartphone, a Personal Digital Assistant and so on. The

wearable device 105 is paired with the external device through a wide variety of networks and protocol types, including wired networks, for example, LAN, cable, etc., and wireless networks, such as Bluetooth, Machine2Machine, WLAN or cellular. Further, the external device may comprise an application that provides the user with options for configuring the wearable device 105. The options may comprise a type of function and the type of input that the user may give through the input means 125 to execute the function. In one example, the user may configure the wearable device 105 to execute a payment transaction when in proximity to sensors similar to sensor 130, upon detecting a single press of a button. In another example, the user may configure the wearable device 105 to execute a payment transaction when in proximity to an NFC-based sensor. The user further provides details pertaining to each function configured. In the present example of payment transactions, the user may provide details such as a debit card/credit card number and a PIN number. Upon configuration, the details are stored in the first memory 120.
[0042] Consider that the wearable device 105 comes in proximity to the sensor 130 placed in the zone Z, after configuration as explained above. For example, the sensor 130 may be integrated into a Point-Of-Sales (POS) terminal in a grocery store (zone Z). The sensor 130 continuously transmits a unique ID. The wearable device 105 identifies that the unique ID of the sensor 130 is associated with the functionality of making payments. Consequently, the wearable device 105 invokes the function of making payments. After purchasing grocery, the user may go to the POS terminal to make the payment for the items purchased based on a total bill amount. The POS terminal may further communicate the total bill amount to the wearable device 105. Further, the user presses the button once to make the payment for the total bill amount. Subsequently, the wearable device 105 shares the debit/credit card number and the PIN stored in the first memory 120 with the POS terminal. In another example, the wearable device 105 may not communicate directly with the POS terminal. The POS terminal may transmit the total bill amount to the sensor 130. The sensor 130 transmits the total bill amount received to the wearable device 105. Subsequently, when the user presses the button once, the wearable device 105 transmits the debit/credit card details to the sensor 130. The sensor 130 further transmits the debit/credit card details received to the POS terminal. On receiving the debit/credit card details, the POS terminal uses to the debit/credit card number and the PIN to complete the payment transaction. In other words, an amount equal to the total bill amount is debited from a bank account of the user to

complete the payment.
[0043] In another example, the wearable device 105 may enable the user to place orders for items in a fast food outlet. In order to place the order, the user may access a menu of the fast food outlet provided on the wearable device 105. In one implementation, the wearable device 105 may fetch the menu of the fast food outlet from a remote server through an internet connection. In another implementation, the sensor 130 located at the fast food outlet may transmit the menu to the wearable device 105, when the wearable device 105 comes in proximity to the sensor 130. Further, the user may select items from the menu by scrolling the menu using the user interface of the wearable device 105. Subsequently, the user may press the input means 125 to place order for the item selected. Upon placing the order, the user may make payments for the order as explained in the previous example.
[0044] In yet another example, the sensor 130 may be associated with HVAC (Heating, Ventilation and Air Conditioning) control system installed in a facility (zone Z). The sensor 130 may detect the presence of a plurality of wearable devices 105 within the facility. Based on the number of wearable devices 105 detected by the sensor 130, the HVAC control system may modify the heating, ventilation or air conditioning within the facility. For example, consider that the facility is empty. When a user wearing the wearable device 105 enters the facility, the sensor 130 identifies the wearable device 105 based on data stored in the second memory 140. Upon identifying, the sensor 140 transmits the number of wearable devices identified to the HVAC control system as one. Further, the HVAC control system may switch ON an Air Conditioning system or heating system based on the ambient temperature. In another implementation, the HVAC control system may switch ON a ceiling fan or an exhaust fan when ten or more wearable devices 105 are detected within the facility, in order to maintain ambient air quality.
[0045] In yet another example, the wearable device 105 may be configured to raise an alarm upon detecting a long press of the button. For example, the alarm may be raised when the user presses the button for a duration of more than 2 seconds. The alarm may be raised by a long press of the button irrespective of the type of sensor in proximity. In other words, the alarm may

be raised without the help of sensors.
[0046] In yet another example, the wearable device 105 may be configured to lock upon receiving a predetermined input. In order to lock/unlock the wearable device 105, a plurality of buttons may be provided on the wearable device 105. For example, the plurality of buttons may be pressed in a sequence in order to lock the wearable device 105. For example, if the buttons on the wearable device 105 are numbered ‘1’, ‘2’ and ‘3’, then the predetermined input may include pressing the buttons in the order: ‘3’, ‘1’, ‘2’ to lock the wearable device 105. On locking, the wearable device 105 does not enable the user to perform any function using the wearable device 105. In order to unlock the wearable device 105, the user may have the press the plurality of buttons in the sequence ‘3’, ‘1’, ‘2’ to unlock the wearable device 105.
[0047] Referring to FIG. 2, an environment of a wearable device 205 is shown, in accordance with one exemplary embodiment of the present disclosure. Consider that the wearable device 205 comprises of a single button as input means (not shown). The wearable device 205 is communicatively coupled to a plurality of sensors 210-1, 210-2, 210-3…210-9 as shown. The plurality of sensors 210-1, 210-2, 210-3…210-9 are placed in zones Z-1, Z-2, Z-3…Z-9 respectively. In other words, the plurality of sensors 210-1, 210-2, 210-3…210-9 help the wearable device 205 to identify the zones Z-1, Z-2, Z-3…Z-9 respectively. Each of the zones Z-1, Z-2, Z-3…Z-9 are associated with a function. For example, the zones Z-1, Z-2 and Z-3 may represent different stalls in a cafeteria. The function associated with the sensors 210-1, 210-2 and 210-3 in the zones Z-1, Z-2 and Z-3 may be related to making payments for items bought by a user from a respective stall. The zones Z-4, Z-5…Z9 may represent different areas in an office space. The sensors 210-4, 210-5 … 210-9 may be associated with access control of users entering the zones Z-4, Z-5… Z9.
[0048] For the wearable device to perform the functions accurately, the zone or context is identified continuously. In other words, proximity of the wearable device 205 to each of the zones Z-1, Z-2, Z-3…Z-9 is tracked continuously. Several techniques may be used to track the wearable device 205. In one implementation, each of the sensors 210-1, 210-2, 210-3…210-9 comprises an RF transmitter. Further, the wearable device 205 may comprise an RF receiver.

The RF receiver in the wearable device 205 may measure a Received Signal Strength (RSS) of radio-frequency signals from the RF transmitters associated with the sensors 210-1, 210-2, 210-3…210-9. In one example, the received signal may comprise a unique ID of the sensor 210. Based on the RSS values, the wearable device 205 identifies the zone to which the wearable device 205 is closest. For example, consider that the user has purchased coffee from zone Z-1. As the user is closest to zone Z-1, the wearable device 205 determines that the RSS from sensor 210-1 is highest. In other words, the wearable device 205 determines that the function to be performed (i.e., the context) is making a payment. Further, the wearable device 105 waits for an input from the user. As already explained using FIGS. 1A and 1B, the input may be preconfigured by the sensor 210-1 or the user. Upon receiving the input, the wearable device 205 shares payment details, e.g., a debit card number and a PIN number with the payment terminal in the zone Z-1.
[0049] Alternatively, consider that the wearable device 205 determines that the RSS from the sensor 210-5 is highest. Consequently, the wearable device 205 determines that the function associated with the zone, i.e., zone Z-5, is access control. The wearable device 205 further awaits an input from the user. Upon receiving the input, the wearable device 205 may share a user identification number of the user with the sensor 210-5. The sensor 210-5 further verifies the user identification number against a database stored in a second memory of the sensor 210-5. Upon verifying, the sensor 210-5 may instruct an electronic door lock associated with the zone Z-5 to unlock, thereby giving the user access to the zone Z-5.
[0050] In another implementation, the location of the wearable device 205 is estimated by the sensors 210-1, 210-2, 210-3…210-9 using triangulation techniques. In one example, the triangulation techniques may use distance and angles between the sensors 210-1, 210-2, 210-3…210-9 as references to estimate the distance of the wearable device 205 from each of the sensors 210-1, 210-2, 210-3…210-9. Based on the distances calculated, the sensor closest to the wearable device 205 is determined.
[0051] In yet another implementation, considering NFC based sensors, the location of the wearable device 205 is estimated based on a magnetic field generated by the wearable device

205 using the sensors 210-1, 210-2, 210-3…210-9. In one example, the sensors 210-1, 210-2, 210-3…210-9 may estimate the location based on a change in polarity of magnetic field components of a time-varying current signal generated by the sensors 210-1, 210-2, 210-3…210-9 due to interaction with a magnetic field generated by the wearable device 205.
[0052] In one example, the location estimated by the sensors 210-1, 210-2, 210-3…210-9 may be transmitted to the wearable device 205. In one implementation, the wearable device 205 may provide navigation directions to the user based on the location e.g., in an airport. The user may set a destination using the user interface of the wearable device 205. Further, based on the location estimated by the sensors 210-1, 210-2, 210-3…210-9, the wearable device 205 provides directions to the user. The directions may be provided through or visual or audio feedbacks.
[0053] Referring to FIG. 3, a method 300 of performing a plurality of functions based on zones is shown, in accordance with one embodiment of the present disclosure. The method 300 may be described in the general context of computer executable instructions. Generally, computer executable instructions may include routines, programs, objects, components, data structures, procedures, modules, functions, etc., that perform particular functions or implement particular abstract data types. The method 300 may also be practiced in a distributed computing environment where functions are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, computer executable instructions may be located in both local and remote computer storage media, including memory storage devices.
[0054] The order in which the method 300 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method 300 or alternate methods. Additionally, individual blocks may be deleted from the method 300 without departing from the spirit and scope of the disclosure described herein. Furthermore, the method may be implemented in any suitable hardware, software, firmware, or combination thereof.
[0055] The method begins at step 305.

[0056] At step 310, a wearable device identifies a first sensor and a second sensor. The first sensor is placed in a first zone and the second sensor is placed in a second zone.
[0057] At step 315, the wearable device is configured, by a user, to perform a first function and a second function based on a first mode, and a second mode. The wearable device is configured to perform the first function when in proximity to the first sensor and the wearable device is configured to perform the second function when in proximity to the second sensor.
[0058] At step 320, the wearable device determines a proximity to one of the first sensor and the second sensor.
[0059] At step 325, the first function and the second function are executed based on the first mode or the second mode. The first function is executed if the wearable device is in proximity to the first sensor or the second function is executed if the wearable device is in proximity to the second sensor.
[0060] The method ends at step 330.
[0061] Referring to FIG. 4, an environment 400 of a wearable device 405 is shown, in accordance with another embodiment of the present disclosure. The wearable device 405, similar to wearable device 105 of FIG. 1, comprises a first memory, a first processor and an I/O interface (not shown). The wearable device 405 further comprises an input means (not shown), similar to input means 125, e.g., a button.
[0062] The wearable device 405 is further communicatively coupled to a plurality of sensors 415-1, 415-2…415-n. The sensors 415-1, 415-2…415-n are located within zones Z1, Z2, Z3…Zn respectively. Each of the zones Z1, Z2, Z3…Zn is associated with a function. In one example, zone Z-1 may be associated with a first function. The first function may comprise sharing credit card details of the user for completing a transaction with a POS terminal located within zone Z-1, upon detecting a single press of the button. The zone Z-2 may be associated

with a second function. The second function may comprise sharing identity details of the user with an electronic door lock located within zone Z-2, upon detecting single press of the button. Further, there may be a third function that comprises booking a conference room from among a plurality of conference rooms, e.g., Room-1(zone Z-3), Room-2(zone Z-4), Room-3(zone Z-5) and Room-4(zone Z-6), upon detecting a double press of the button. Furthermore, there may be a fourth function that may be performed irrespective of the zone. For example, the fourth function may comprise raising an alarm upon detecting a single long press of the button. Further, the sensors 415-1, 415-2…415-n are communicatively coupled to a server 420. The sensors 415-1, 415-2…415-n communicate with the server 420 over a network 425.
[0063] In one embodiment, the server 420 may include at least one processor 430, an input/output (I/O) interface 435 and a memory 440. The at least one processor 430 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the at least one processor 430 is configured to fetch and execute computer-readable instructions stored in the memory 440.
[0064] The I/O interface 435 may include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, and the like. The I/O interface 435 may allow server 420 to interact with the wearable device 405 directly or through the sensors 415-1, 415-2…415-n. Further, the I/O interface 435 may enable the server 420 to communicate with other computing devices, such as web servers and external data servers (not shown). The I/O interface 435 may facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example, LAN, cable, etc., and wireless networks, such as WLAN, cellular, or satellite. The I/O interface 435 may include one or more ports for connecting a number of devices to one another or to another server.
[0065] The memory 440 may include any computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read only

memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes.
[0066] In one implementation, the network 425 may be a wireless network, a wired network or a combination thereof. The network 425 can be implemented as one of the different types of networks, such as intranet, local area network (LAN), wide area network (WAN), the internet, and the like. The network 425 may either be a dedicated network or a shared network. The shared network represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), and the like, to communicate with one another. Further the network 425 may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, and the like.
[0067] In the present embodiment, the server 420 monitors a position of the wearable device 405. In one implementation, the sensors 415-1, 415-2…415-n calculate the position of the wearable device 405 and updates the server 420 accordingly. In one example, the sensors 415-1, 415-2…415-n may update the server 420 with the position continuously. In another example, the sensors 415-1, 415-2…415-n may update the server 420 with the position only when data traffic on the network 425 is below a certain threshold value. In one embodiment, the sensors 415-1, 415-2…415-n may comprise a data traffic monitor to continuously monitor a bandwidth usage on the network 425.
[0068] In another implementation, the server 420 may calculate the position of the wearable device 405 based on data received from the sensors 415-1, 415-2…415-n. In one example, the sensors 415-1, 415-2…415-n may update the server 420 with RSS values of the signal received from the wearable device 405 in an instance. Further, the server 420 may map the position of the wearable device 405 based on the RSS values received. Further, the server 420 instructs the wearable device 405 to perform the function specific to the zone, e.g., zone Z-1. Further, upon receiving an input from the user, the wearable device 405 executes the function specific to the zone.

[0069] As explained above, the wearable device 405 is configured to function in a first mode, a second mode, or in combination thereof. When configured in the first mode, the wearable device 405 executes the function automatically when the wearable device 405 comes in proximity to the sensors e.g., sensors 415-2, 415-4 and so on. In the second mode, the wearable device 405 executes the function after receiving an input from the user. For example, consider that the user comes in proximity to the sensors 415-1, 415-5 and so on that is configured to execute the function after receiving the input on the wearable device 405. In order to execute the function with respect to the sensor 415-1 or 415-5, the user may have to press the input means. Subsequently, the wearable device 405 executes the function. It should be understood that the user presses the input means with an intent to execute the function. Without the press of the input means, the wearable device 405 does not execute the function. Further, if the wearable device 405 is configured to execute the function in combination of the first mode and the second mode, then the function is executed with or without user intervention, when the user comes in proximity to the sensors 415-1, 415-2…415-n.
[0070] Similarly, each of the sensors 415-1, 415-2…415-n may also be preconfigured with a firmware associated with the wearable device 405. The firmware may include information associated with the wearable device 405. The information may include, but not limited to, unique identification of the wearable device 405. The firmware may further comprise programmed instructions to execute a function when the wearable device 405 comes in proximity to the sensor 415-1, 415-2…415-n. As explained above, the firmware associated with the sensors 415-1, 415-2…415-n is also pre-configured to function in a first mode, a second mode, and a combination thereof. If configured with the first mode, the firmware associated with the sensors 415-1, 415-2…415-n is preconfigured to execute the function automatically when the wearable device 405 comes in proximity to the sensors 415-1, 415-2…415-n. If configured with the second mode, the firmware associated with the sensors 415-1, 415-2…415-n is preconfigured to execute the function based on an intent of a user of the wearable device 405. The intent of the user is determined based on the input provided received from the user by the wearable device 405 and the proximity of the wearable device 405 to the sensors 415-1, 415-2…415-n. The function may include, but not limited to, receive or process payment, allow access to user of the wearable device 405, scheduling an event, raising an alarm, controlling Heating, Ventilation

and Air Conditioning (HVAC) control system, providing navigation, pairing one or more assets and so on.
[0071] In the present example, consider that the user wishes to book a conference room using the wearable device 405 based on the second mode. The process of booking the conference room is explained using FIG. 5.
[0072] Referring to FIG. 5, in conjunction with FIG. 4, a process 500 of booking the conference room using the wearable device 405 is shown, in accordance with an exemplary embodiment of the present disclosure. It should be understood that the user may be located anywhere while booking the conference room and not necessarily within the zones Z-1, Z-2…Z-n.
[0073] To book the conference room, the user actuates the input means on the wearable device 405. Referring to the previous example of FIG. 4, the user actuates the input means by pressing the button on the wearable device 405 twice. Upon detecting the actuation of the input means, the wearable device 405 requests for additional information from the user. The additional details may include a choice of conference room, choice of time for occupancy of the conference room and so on. The choices may be displayed on a user interface (not shown) of the wearable device 405. The user may respond by providing his choices using the user interface of the wearable device 405. For example, the user may provide the choice of conference room as: ‘Room-1’ and the choice of time as ‘11:00 am on 26th March 2017’. Further, the wearable device 405 transmits the request for the conference room to the server 420. In addition to the choice of conference room and the choice of time, request may also comprise an employee ID of the user.
[0074] At step 510, the server 420 receives the request for the conference room from the wearable device 405.
[0075] At step 515, the server 420 enquires status of all conference room bookings from the sensors 415-3, 415-4, 415-5 and 415-6 that are located in Room-1, Room-2, Room-3 and Room-4 respectively. The sensors 415-3, 415-4, 415-5 and 415-6 may respond by transmitting details of all conference room bookings to the server 420.

[0076] At step 520, the server 420 determines whether the chosen conference room, i.e., Room-1 is available at the chosen time, i.e., 11:00 am on 26th March 2017 based on the responses received from the sensors 415-3, 415-4, 415-5 and 415-6. If Room-1 is available at the chosen time, then step 535 is performed. Otherwise, step 525 is performed.
[0077] At step 525, the server 420 transmits alternate options available to the wearable device 405. For example, the alternate option may show that Room-2 is available at 11:00 am on 26th March 2017.
[0078] At step 530, the server 420 receives a confirmation from the user for booking the alternate option. In one example, the confirmation may comprise receiving a single press of the button on the wearable device 405.
[0079] At step 535, the server 420 books the conference room. In one implementation, the server 420 may transmit the booking details to the respective sensor of the conference room booked. For example, if Room-2 is booked, then the booking details are sent to the sensor 415-4. Further, the sensor 415-4 may deny booking of Room-2 by any other user for the chosen time.
[0080] In one implementation, the sensor 415-4 may cancel conference room booking, if the wearable device 405 is not located in Room-2 within a predefined duration of a scheduled time. For example, if the scheduled time is 11:00 am, then the booking may be cancelled if the wearable device 405 is not located within the zone Room-2 within 10 minutes from 11:00 am, i.e., before 11:10 am.
[0081] In addition to the functions presented above, the wearable device may perform several other functions in the first mode or the second mode. In one example, the wearable device may share a location of the user with a pre-defined contact, in case of an emergency. The pre-defined contact may be a nearest fire/police station. In one implementation, the location may be shared with the pre-defined contact upon receiving an input from the user. For example, the user presses the button (as in the second mode) on the wearable device for more than 5 seconds. On pressing

the button, the wearable device transmits an SOS message along with the location of the user to the pre-defined contact. Further, based on the location received, the rescuers may track and rescue the user. In one implementation, the location of the user may be obtained by identifying the nearest sensor, say sensor 2. Similarly, the wearable device may be also used to locate children, elderly and people with special needs. The location may be shared with the pre-defined contact in the first mode or the second mode. In another embodiment, the location may be shared with the pre-defined contact automatically on a periodic basis.
[0082] In another example, the wearable device may be used for pairing an asset with the user. For example, the asset may be a suit case. The suit case may carry an electronic number lock. The electronic number lock may be programmed to unlock only when the wearable device is located in proximity. In one implementation, the electronic lock may be programmed with an identification number of the wearable device associated with the user. In an alternate implementation, the electronic lock may be programmed to unlock when the user actuates the input means of the wearable device in a predefined fashion. For example, the user may press the button twice to unlock the baggage.
[0083] In yet another example, the wearable device may be used to issue zone-based alerts to the user. For example, if the zone is a factory, then the user may be prompted to wear safety gloves. The user may be prompted through a warning displayed on the user interface of the wearable device.
[0084] In yet another example, the wearable device may be used for inventory management within a warehouse. The warehouse may contain a plurality of articles. Each of the articles may be attached with an electronic tag, i.e., the wearable device. The electronic tag may store information associated with each of the article such as a serial number, manufacturing date, expiry date and so on. Further, the warehouse is divided into a plurality of zones. Each of the zones may be identified using a respective sensor. When a new article is added to the warehouse, the sensor reads the information stored in a second memory of the electronic tag. Further, the sensor transmits the information to a centralized server. The centralized server may further update an inventory list based on the information received. Similarly, when the article is

removed from the warehouse, i.e., if the article is not detected by the sensor, then the inventory list is updated by removing information associated with the article. Further, the plurality of sensors may be used for tracking the article as explained using FIG. 2. In another example, the article may be a baggage or cargo that has arrived at an airport. The electronic tag on the baggage may store information such as a destination and user’s contact details. The location of the baggage or cargo may be continuously updated to the user by the centralized server. In one example, the centralized server may send an SMS to a mobile number provided in the user’s contact details.
[0085] The wearable device disclosed in the present disclosure, performs a specific function based on a zone or an intent. Further, one wearable device can perform different functions in different zone for the same input. As a result, the wearable device relieves the user from the need to carry multiple devices for different functions. In the simplest form, the wearable device may be implemented using a single button as input means. Further, the wearable device may also be locked by the user by providing a predetermined input, to prevent the wearable device from performing any function. Locking of the wearable device helps in avoiding misuse of the wearable device in the hands of a third party.
[0086] Referring to FIG. 6, a method 600 of performing a plurality of functions is shown in accordance with one embodiment of the present disclosure. The method 600 may be described in the general context of computer executable instructions. Generally, computer executable instructions may include routines, programs, objects, components, data structures, procedures, modules, functions, etc., that perform particular functions or implement particular abstract data types. The method 600 may also be practiced in a distributed computing environment where functions are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, computer executable instructions may be located in both local and remote computer storage media, including memory storage devices.
[0087] The order in which the method 600 is described and is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method 600 or alternate methods. Additionally, individual blocks may be deleted

from the method 600 without departing from the spirit and scope of the disclosure described herein. Furthermore, the method may be implemented in any suitable hardware, software, firmware, or combination thereof. However, for ease of explanation, in the embodiments described below, the method 600 may be implemented in the above-described server 420.
[0088] The method begins at step 605.
[0089] At step 610, the server identifies a first sensor and a second sensor.
[0090] At step 615, the server identifies a location of a wearable device. More specifically, the server determines whether the wearable device is in proximity to the first sensor or the second sensor.
[0091] At step 620, the server instructs the wearable device to execute a first function and a second function based on at least one of a first mode and a second mode of the wearable device. The first mode indicates configuring the wearable device to perform the first function or the second function without user intervention. The second mode indicates configuring the wearable device to perform the first function or the second function upon receiving an input on the wearable device by the user. The wearable device is instructed to perform the first function when in proximity to the first sensor. The wearable device is instructed to perform the second function when in proximity to the second sensor.
[0092] At step 625, the wearable device executes the first function and the second function based on the instructions received from the server. The first function is executed when the wearable device comes in proximity to the first sensor. The second function is executed when the wearable device comes in proximity to the second sensor.
[0093] The method ends at step 630.
[0094] Although embodiments of a wearable device for performing functions based on zones have been described in a language specific to features and/or methods, it is to be understood that

the description is not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as examples of implementations of the wearable device for performing the functions based on zones.

WE CLAIM:
1. A method of performing a plurality of functions by a wearable device based on zones, the
method comprising:
identifying, by a wearable device, a first sensor and a second sensor, wherein the first sensor and the second sensor are identified with respect to a first zone and a second zone, respectively;
configuring the wearable device to perform a first function and a second function based on at least one of a first mode and a second mode, wherein the first mode indicates configuring the wearable device to perform the first function or the second function without user intervention, wherein the second mode indicates configuring the wearable device to perform the first function or the second function upon receiving an input on the wearable device by the user, wherein the wearable device is configured to perform the first function when in proximity to the first sensor, and wherein the wearable device is configured to perform the second function when in proximity to the second sensor;
determining proximity of the wearable device to one of the first sensor and the second sensor; and
executing, by the wearable device, the first function and the second function based on the first mode or the second mode, wherein the first function is executed when the wearable device comes in proximity to the first sensor, and wherein the second function is executed when the wearable device comes in proximity to the second sensor.
2. The method as claimed in claim 1, wherein the input is one of a touch input, hard press,
voice input, a biometric input and a gesture control.
3. The method as claimed in claim 1, wherein the first function and the second function are
executed in the second mode based on a duration of the input received.
4. The method as claimed in claim 1, wherein the first function and the second function are
executed in the second mode based on a sequence in which the input is received.

5. The method as claimed in claim 1, wherein the first function comprises one of:
making a payment,
scheduling an event,
raising an alarm,
controlling Heating, Ventilation and Air Conditioning (HVAC) control system,
providing navigation,
pairing one or more assets, and
providing access control.
6. The method as claimed in claim 1, wherein the second function comprises one of:
making a payment,
scheduling an event,
raising an alarm,
controlling Heating, Ventilation and Air Conditioning (HVAC) control system,
providing navigation,
pairing one or more assets, and
providing access control.
7. A method of performing functions by a wearable device based on zones, the method
comprising:
identifying, by a server, a first sensor and a second sensor, wherein the first sensor and the second sensor are identified with respect to a first zone and a second zone, respectively;
identifying, by the server, a location of a wearable device being in proximity to the first sensor or the second sensor;
instructing, by the server, the wearable device to execute a first function and a second function based on at least one of a first mode and a second mode of the wearable device, wherein the first mode indicates configuring the wearable device to perform the first function or the second function without user intervention, wherein the second mode indicates configuring the wearable device to perform the first function or the second function upon receiving an input on the wearable device by the user, wherein the wearable device is instructed to perform the

first function when in proximity to the first sensor, and wherein the wearable device is instructed to perform the second function when in proximity to the second sensor;
executing, by the wearable device, the first function and the second function based on the instructions received from the server, wherein the first function is executed when the wearable device comes in proximity to the first sensor, and wherein the second function is executed when the wearable device comes in proximity to the second sensor.
8. The method as claimed in claim 7, wherein the input is one of a touch input, hard press,
voice input, a biometric input and a gesture control.
9. The method as claimed in claim 7, wherein the first function and the second function are
executed in the second mode based on a duration of the input received.
10. The method as claimed in claim 7, wherein the first function or the second function are
executed in the second mode based on a sequence in which the input is received.
11. The method as claimed in claim 7, wherein the first function comprises one of:
making a payment,
scheduling an event,
raising an alarm,
controlling Heating, Ventilation and Air Conditioning (HVAC) control system,
providing navigation,
pairing one or more assets, and
providing access control.
12. The method as claimed in claim 7, wherein the second function comprises one of:
making a payment,
scheduling an event,
raising an alarm
controlling Heating, Ventilation and Air Conditioning (HVAC) control system,
providing navigation,

pairing one or more assets, and providing access control.
13. A wearable device for performing a plurality of functions based on zones, the wearable
device comprising:
an input means; a memory; and
a processor coupled to the memory, wherein the processor executes program instructions stored in the memory, to:
identify a first sensor and a second sensor, wherein the first sensor and the second sensor are identified with respect to a first zone and a second zone, respectively;
determine a first function and a second function based on at least one of a first mode and a second mode, wherein the first mode indicates configuring the wearable device to perform the first function or the second function without user intervention, and wherein the second mode indicates configuring the wearable device to perform the first function or the second function upon receiving an input on the wearable device by the user; and
perform the first function and the second function based on the first mode or the second mode, wherein the first function is performed when in proximity to the first sensor, and wherein the second function is performed when in proximity to the second sensor.
14. The wearable device as claimed in claim 13, wherein the proximity of the wearable
device to one of the first sensor and the second sensor is determined based on one of:
a Received Signal Strength (RSS) of radio frequency signals received from the first sensor and the second sensor,
a change in polarity of magnetic field components of a time-varying current signal generated by the first sensor and the second sensor due to interaction with a magnetic field generated by the wearable device, and
a position of the wearable device obtained by triangulating signals from the first sensor and the second sensor.

15. The wearable device as claimed in claim 13, wherein the input from the input means is
received using one of a touch input, hard press, voice input, a biometric input and a gesture
control.
16. The wearable device as claimed in claim 13, wherein the first function or the second
function are executed in the second mode based on a duration of the input received.
17. The wearable device as claimed in claim 13, wherein the first function or the second
function are executed in the second mode based on a sequence in which the input is received.