Patent Publication Number: US-2019187761-A1

Title: Religious application for mobile and wearable technology devices

Description:
CROSS-REFERENCE TO RELATED PATENT APPLICATION 
     This application is a continuation application of U.S. patent application Ser. No. 15/177,884, filed Jun. 9, 2016, which claims priority from U.S. Provisional Application No. 62/173,154 filed on Jun. 9, 2015, the disclosure of which is incorporated herein by reference in its entirety. 
    
    
     COLOR DRAWINGS/PHOTOGRAPHS 
     The file of this patent contains at least one drawing/photograph executed in color. Copies of this patent with color drawings/photographs will be provided by the Office upon request and payment of the necessary fee. 
     BACKGROUND 
     Technical Field 
     One or more exemplary embodiments relate to systems and methods for detecting prayer units while a device user is engaged in a prayer session comprising two or more prayer units, and more particularly to systems and methods for determining completion of each prayer unit and notifying the user, via the device, regarding completion of one or more prayer units. 
     Description of the Related Art 
     Activity tracking devices allow for tracking and monitoring a user&#39;s physical activity. For example, WO2011/028383 to Hoffman et al. discloses the collection and display of a user&#39;s athletic activity information while providing encouragement and maintaining the user&#39;s interest in continuing to perform the athletic activity. However, there has been no disclosure of systems, devices, or methods that are capable of tracking a user&#39;s prayer activity and providing the user with a detailed breakdown of the user&#39;s prayer activity. 
     SUMMARY 
     Muslims, followers of the teachings of the religion of Islam, are required to pray five times per day (at least) as one of the tenants of the religion. The five prayers include Fajr (dawn prayer), Dhuhr (noon prayer), Asr (afternoon prayer), Maghrib (sunset prayer), and Isha&#39;a (night prayer). Each prayer session involves an individual performing a physical routine which includes first raising ones hands to their heads (Takbir) and then engaging in two or more rakats (prayer units). The number of rakats or prayer units depends on which of the five prayer sessions the individual is engaged in. The dawn prayer includes two obligatory prayer units, the noon prayer includes four obligatory prayer units, the afternoon prayer includes four obligatory prayer units, the sunset prayer includes three obligatory prayer units, and the night prayer includes four obligatory prayer units. 
     In addition to the five obligatory prayers, there are other prayers that Muslims perform, each of which also has a predetermined number of prayer units. One example is the offering of recommended (but not obligatory) prayers before or after some of the aforementioned five obligatory prayer sessions. These recommended prayer sessions typically include two to four prayer units. Another example is during the month of Ramadan in the Islamic calendar, when additional prayers may be offered after the night prayer. The additional prayers are in sets of two prayer units and typically, four to ten sets of these additional prayers are offered. Yet another example is the offering of the celebratory Eid prayers marking the end of Ramadan. Hereinafter, such prayer sessions that are outside of the five obligatory prayer sessions may be referred to as non-obligatory prayer sessions throughout this description. 
     In any event, regardless of the prayer session, each rakat or prayer unit in the prayer session follows the same series of postures: first standing with arms folded across the chest, then bowing with hands on knees (referred to as Raku), then brief standing with hands on the side, then prostrating two times with a brief sitting in between the two prostrations (each prostration is referred to as a Sajda). In the even prayer units or in the last prayer unit of the prayer session (regardless of whether the last prayer unit is an even or odd prayer unit), there is also a sitting step after the second prostration. Each of these postures within each prayer unit also involves specific recitations. Details of the prayer positions and postures in a prayer session are also described in U.S. Pat. No. 8,286,286 with reference to  FIGS. 1-13 , therein. U.S. Pat. No. 8,286,286 is incorporated herein by reference in its entirely. 
     While an individual is performing the prayer, the individual may forget which of the prayer units they are performing. If the individual realizes they may have not performed the correct number of prayer units for the prayer session they just completed, they either perform a subset of the prayer session all over again or instead perform a ‘correction’ prayer. Worse, if they didn&#39;t realize they made a mistake and do nothing about it, they may feel that the prayer session they just completed may not be recognized. 
     The present inventors have recognized that a solution may be provided to individuals performing the prayer sessions such that they can be assured that they performed the correct number of prayer units within each prayer session. 
     Accordingly, a non-limiting embodiment provides a method of tracking a prayer session of a device user and notifying the device user regarding prayer session activity, the method including receiving altitude information from an altimeter of the device while the device user is engaged in the prayer session, determining a prayer unit number or prayer position based on the received altitude information, and notifying the device user of the determined prayer unit number or prayer position. 
     The method may further include reading time information from a clock of the device, determining location information using GPS or cell towers, determining, based on the read time information and the determined location information, a type of prayer the device user is performing, corresponding time of day, and corresponding number of prayer units for the type of prayer, and notifying the user of the determined prayer unit number or prayer unit position based on the determined type of prayer. 
     The notifying may further include notifying the device user of the determined prayer unit number or prayer position using one of a visual notification, audio notification, and haptic notification. 
     The method may further include storing user prayer activity information for each prayer session of the user, and displaying the user prayer activity information of the prayer sessions based on a comparison with other users&#39; prayer activity information. 
     In another non-limiting embodiment, the above-described method using the altimeter information may be implemented as an application stored in a non-transitory computer readable medium, and the method steps are executed as functions of the application. 
     Another non-limiting embodiment provides a method of tracking a prayer session of a device user and notifying the device user regarding prayer session activity, the method including receiving motion information from an accelerometer of the device while the device user is engaged in the prayer session, receiving position information from a gyroscope of the device while the device user is engaged in the prayer session, determining a prayer unit number or prayer position based on the received motion information and position information, and notifying the device user of the determined prayer unit number or prayer position. 
     The method may further include reading time information from a clock of the device, determining location information using GPS or cell towers, determining, based on the read time information and the determined location information, a type of prayer the device user is performing, corresponding time of day, and corresponding number of prayer units for the type of prayer, and notifying the user of the determined prayer unit number or prayer unit position based on the determined type of prayer. 
     The notifying may further include notifying the device user of the determined prayer unit number or prayer position using one of a visual notification, audio notification, and haptic notification. 
     The method may further include storing user prayer activity information for each prayer session of the user, and displaying the user prayer activity information of the prayer sessions based on a comparison with other users&#39; prayer activity information. 
     In another non-limiting embodiment, the above-described method using the motion information and position information may be implemented as an application stored in a non-transitory computer readable medium, and the method steps are executed as functions of the application. 
     In yet another non-limiting embodiment, provided is a method of tracking a prayer session of a device user and notifying the device user regarding prayer session activity, the method including receiving motion information from an accelerometer of the device while the device user is engaged in the prayer session, receiving altitude information from an altimeter of the device while the device user is engaged in the prayer session, receiving position information from a gyroscope of the device while the device user is engaged in the prayer session, reading time information from a clock of the device, determining location information using GPS or cell towers, determining, based on the read time information and the determined location information, a type of prayer the device user is performing and corresponding number of prayer units for the type of prayer, determining a prayer unit number or prayer position based on one or more of the received motion information, altitude information, and position information; and notifying the device user of the determined prayer unit number or prayer position based on the determined type of prayer and corresponding number of prayer units for the type of prayer. 
     In another non-limiting embodiment, the above-described method using one or more of the motion information, altitude information, and position information may be implemented as an application stored in a non-transitory computer readable medium, and the method steps are executed as functions of the application. 
    
    
     
       BRIEF DESCRIPTION OF DRAWINGS 
         FIG. 1  is a view of a system for detecting prayer units in a prayer session according to a non-limiting embodiment; 
         FIG. 2  is a flowchart illustrating the implementation of the method for detecting prayer units using output from an altimeter according to a non-limiting embodiment; 
         FIG. 3  is a flowchart illustrating the implementation of the method for detecting prayer units using output from an accelerometer and a gyroscope according to another non-limiting embodiment; 
         FIG. 4A  is a graph which shows collected roll, pitch, and yaw data from a device&#39;s gyroscope to show positional orientation of the device during an exemplary prayer session including three prayer units; 
         FIG. 4B  is a graph which shows a coded overlay on top of the data from  FIG. 4A  to show the breakdown of the positional orientation of the device corresponding to the specific posture of the user within each prayer unit of the three prayer units in the exemplary prayer session; 
         FIG. 5A  is a graph which shows collected XYZ gravity data from a device&#39;s gyroscope to show positional orientation of the device during an exemplary prayer session including three prayer units; 
         FIG. 5B  is a graph which shows a coded overlay on top of the data from  FIG. 5A  to show the breakdown of the positional orientation of the device corresponding to the specific posture of the user within each prayer unit of the three prayer units in the exemplary prayer session; 
         FIG. 6A  is a graph which shows collected XYZ acceleration data from a device&#39;s accelerometer to show the movement (and lack thereof) of the device when transitioning from one posture of a prayer unit to another and transitioning between prayer units during an exemplary prayer session including three prayer units; 
         FIG. 6B  is a graph which shows a coded overlay on top of the data from  FIG. 6A  to show the breakdown of the movement of the device corresponding to the user transitioning from one posture of a prayer unit to another and transitioning between prayer units in the exemplary prayer session; 
         FIG. 7A  is a graph which shows collected XYZ rotation data from a device&#39;s accelerometer to show the movement (and lack thereof) of the device when transitioning from one posture of a prayer unit to another and transitioning between prayer units during an exemplary prayer session including three prayer units; 
         FIG. 7B  is a graph which shows a coded overlay on top of the data from  FIG. 7A  to show the breakdown of the movement of the device corresponding to the user transitioning from one posture of a prayer unit to another and transitioning between prayer units in the exemplary prayer session; 
         FIG. 8A  is a graph which shows the collected Altitude data from a device&#39;s altimeter to show the altitude of the device during an exemplary prayer session including three prayer units; 
         FIG. 8B  is a graph which shows a coded overlay on top of the data from  FIG. 8A  to show the breakdown of the altitude of the device corresponding to the specific posture of the user within each prayer unit of the three prayer units in the exemplary prayer session; 
         FIG. 9A  is a graph which shows the combined collected data (‘roll, pitch, yaw’, XYZ gravity, XYZ acceleration, XYZ rotation and altitude) from a device&#39;s gyroscope, accelerometer and altimeter during an exemplary prayer session including three prayer units; and 
         FIG. 9B  is a graph which shows a coded overlay on top of the data from  FIG. 8A  to show the breakdown of the combined data of the device corresponding to the specific posture of the user within each prayer unit of the three prayer units in the exemplary prayer session. 
     
    
    
     DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS 
     All terms including descriptive or technical terms which are used herein should be construed as having their plain and ordinary meanings. However, the terms may have different meanings according to an intention of one of ordinary skill in the art, precedent cases, or the appearance of new technologies. Also, some terms may be arbitrarily selected by the applicant, and in this case, the meaning of the selected terms will be described in detail in the detailed description. Thus, the terms used herein have to be defined based on the meaning of the terms together with the description throughout the specification. 
     Also, when a part “includes” or “comprises” an element, unless there is a particular description contrary thereto, the part may further include other elements, not excluding the other elements. In the following description, terms such as “unit” and “module” indicate a unit for processing at least one function or operation, wherein the unit and the block may be embodied as hardware or software or may be embodied by combining hardware and software. 
     One or more exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, the one or more exemplary embodiments may be embodied in many different forms, and should not be construed as being limited to the exemplary embodiments set forth herein. Rather, these exemplary embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the one or more exemplary embodiments to those of ordinary skill in the art. In the following description, well-known functions or constructions are not described in detail since they would obscure the one or more exemplar embodiments with unnecessary detail, and like reference numerals in the drawings denote like or similar elements throughout the specification. 
     It will be readily understood that the components of the present invention, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following more detailed description of the embodiments as represented in  FIGS. 1-9B , is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. 
     Referring now to  FIGS. 1-9B , systems and methods for detecting prayer units while an individual is engaged in a prayer session will be described. 
     In one embodiment, a mobile application is provided for a device such as a smartphone (e.g., Apple iPhones, Android-based smartphones, etc.) and/or a wearable device (e.g., Apple Watch, Samsung wearable technology, Pebble, FitBit, Pendent, Clip-On, etc.). For example, the mobile application can work on both the smartphone and wearable device or work on only one of the smartphone and wearable device. The mobile application would allow users to keep track of the prayer units they are performing and/or keep track of prayer postures within each prayer unit (e.g., standing, bowing, sitting, or prostrating—in other words, any posture in the above-noted series of postures in a prayer unit) and alert the user of the prayer unit count and/or prayer postures via visual notifications (icons, flashing lights, graphics, colors, etc.), audio notifications (beeps, music, dialogue, etc.), and haptic notifications (pulse, vibrate, etc.) for the purpose of correctly performing prayers and/or tracking and reporting on prayers. Furthermore, the user can disable the alerting altogether (e.g., for the purpose of not being disturbed during the prayer), so that they can review their “tracking” of their prayer positions and sequence after their prayer to see if their prayer was performed properly or if they should repeat their prayer. 
     The mobile application utilizes one or more of the device&#39;s accelerometer, altimeter, gyroscope, and GPS to track and analyze the user&#39;s motion, altitude, position, and location (assuming the user is carrying or wearing the device) in order to determine the prayer unit count and/or prayer position/posture. Prayer position and prayer posture may be interchangeably used throughout this disclosure. The mobile application&#39;s algorithms gather data regarding accelerometer, altimeter, gyroscope, and location and assess the data individually or in combination with each other to determine the user&#39;s current sequence in the prayer session and predict the next action in the sequence. Additionally, depending on the device capabilities, only one data stream, such as the user&#39;s altitude information, could be used to determine the prayer unit count and/or prayer position without collecting or analyzing the other data streams (motion, position, location). Moreover, the algorithms may look at the user&#39;s historic data points for all the user&#39;s previous prayer sessions (or for all the user&#39;s previous prayer sessions for the particular prayer being offered) along with current data points to determine the User&#39;s current sequence and/or position and predict the next action in the sequence and/or to present the user&#39;s prayer activity information. Furthermore, the algorithms can alert the user of their current sequence without predicting the next action in the sequence. 
     The mobile application can be manually started by the user prior to a prayer session. In another embodiment, the application can self-activate when it detects the user has started the prayer session by monitoring the data points against a prayer sequence pattern of data points. In yet another embodiment, the application can self-activate when it detects the user has started the prayer session by monitoring the data points against a prayer sequence pattern of data points and also based on the time of day. The self-activation mode requires the mobile application to run in the background continuously upon device startup or when manually started by user. Furthermore, at any time, the user can restart/reset the prayer unit count manually to zero or the prayer position to an initial state if desired both in the manual start mode or the self-activate mode. 
     The mobile application utilizes the device&#39;s GPS and system clock to determine the user&#39;s location and time of day in order to determine which of the five prayers the user will most likely be conducting. Further, the application can recommend to the user which of the five prayers and number of prayer units to perform. The user can also manually enter their location and/or which prayer they will be conducting. 
     The mobile application has a calibration sequence which allows the user, if they desire, to standardize/tune the application&#39;s algorithms to their unique prayer positions in order to increase the accuracy of the prayer position identification and notification. The calibration sequence monitors and records the accelerometer, altimeter, and gyroscope data points for the user during a practice prayer sequence and uses this recorded information as a baseline to compare against to determine prayer positions and prayer units. For example, in order to calibrate the application, the user can direct the application to activate a calibration mode in which the user can perform a practice prayer session prior to performing an actual prayer session. This way, during the practice prayer session, the application can detect the user&#39;s tendencies in a prayer unit and more particularly within each prayer position and transitions between prayer positions. For example, the application can determine the average time a user spends in the standing position, bowing position, prostrating position, etc. Additionally, the calibration sequence can utilize application community user data as a baseline to compare against to determine prayer positions and prayer units. Both of these calibration methods are a form of machine learning in order to provide more accurate prayers positions identification and notification. This calibration sequence is optional for the user. The application community user data is described in more detail below. 
     The mobile application employs visual notifications (user configurable) in addition to audio and haptic notifications to alert the user of the current sequence of their prayer sequence and/or the predicted next sequence. The visual notifications can consist of images, avatars, logos, characters, numbers, and/or alphanumeric displayed on the device screen (smartphone, wearable technology, etc.) to indicate prayer sequence steps. In addition flashing lights and various screen colors can also be utilized as notifications. For example, a certain color, such as red, might be use to designate the first prayer unit while another color, such as yellow, might be used to designate the second prayer unit. In another example, certain images or symbols, such as a triangle, might be use to designate the first prayer unit while another image or symbol, such as a square, might be used to designate the second prayer unit. The visual notifications can occur on both the smartphone device and wearable device or just on a single device, either the smartphone device or the wearable device. 
     The mobile application employs audio notifications (user configurable) in addition to visual and haptic notifications to alert the user of the current sequence (e.g., prayer unit or prayer position) of their prayer sequence and/or the predicted next sequence. The audio notifications can consist of beeps, music, and/or human voice commands from the device (smartphone, wearable, etc.) to indicate prayer sequence steps. The audio notifications can occur on both the smartphone device and wearable device or just on a single device, either the smartphone device or the wearable device. 
     The mobile application employs haptic notifications (which may be user configurable) in addition to visual and audio notifications to alert the user of the current sequence of their prayer sequence and/or the predicted next sequence. The haptic notifications can consist of pulses and/or vibrations from the device (smartphone, wearable, etc.) to indicate prayer sequence steps. The haptic notifications can occur on both the smartphone device and wearable device or just on a single device, either the smartphone device or the wearable device. 
     The mobile application allows users to disable their notifications (audio, visual and haptic) altogether and the user can review their prayer unit count and prayer position details after the prayer session if they prefer not being bothered during the prayer. Of course, even if the notifications are enabled, the user could still review their prayer unit count and prayer position details after the prayer session. 
     The mobile application enables users to track their total, average, and other metrics for prayer units and prayer postures/positions performed for each of the five obligatory prayer sessions per day or for non-obligatory prayers, for all prayer units performed and all prayer positions the user engaged in per each of the five prayer sessions, for all prayer units performed per day of the week, for all prayer units performed per day/week/month/quarter/year both in Julian and Hijra (Islamic) calendar years and lifetime 
     Additionally, the user can share/post their total/average prayer unit and prayer position metrics with another user of the prayer unit counting and analysis mobile application, with a group of members, and/or to the entire user community (i.e., all users of the mobile application). Furthermore, users can compare their prayer unit totals either by prayer, day, day of week, week, month, etc. with the user community benchmarks (aggregated totals and averages across entire mobile application user community). Additionally, users can keep a running count of prayer units they have performed since installing the mobile application providing them with per lifetime prayer units tracking and reporting. Lastly, based on their performance metrics, users can receive digital badges, rewards, and other forms of recognition (Gamify) for their prayer unit metrics. 
     The mobile application also allows users to track their prayer positions/postures and provides analytics (prayer analytics) on how they are performing their prayers based on which of the five obligatory prayers or non-obligatory prayers or all prayers across a certain day, time, and/or period. For example, this allows users to review if they are taking more time in between the two prostrations during the dawn prayer versus the noon or afternoon prayers, or if the user&#39;s second prayer units frequently tends to be quicker than their first prayer unit (i.e., the time it takes the user to complete the second prayer unit tends to be less than the time it takes the user to complete the first prayer unit). By providing these trends to the user, in addition to providing visibility into the user&#39;s praying habits, the user can decide if they want to make certain changes to their prayers (for quality optimization purposes). Moreover, a user&#39;s data can be compared with community data to identify areas of optimization. For example, information may be provided to the user based on the user&#39;s data and the community data that the user was in the 95 th  percentile of performing his afternoon prayer on time. 
     Users are able to post their prayer session metrics and digital badges, rewards, and other recognitions to mobile and cloud application as well as other social media applications (Facebook, Twitter, Instagram, etc.). 
     In light of the above functionality, configuration, and capabilities of the disclosed mobile application, the mobile application can easily, accurately, and automatically count a user&#39;s prayer units when the user is performing prayers and notify the user of the current prayer unit count and/or prayer position in a non-obtrusive manner in order to perform prayers correctly. 
     Users can track and share (if desired) their prayer session metrics for a certain time period or prayer session. Users can also monitor their prayers session activity and make adjustments for quality optimization purposes. Users can also utilize the prayer session metrics to encourage a certain behavior. For example, users can be encouraged to make corrections in their prayer session, be encouraged to pray more regularly, and also inspire others to pray. 
       FIG. 1  is a view of a system for detecting prayer units in a prayer session according to a non-limiting embodiment. 
     In  FIG. 1 , device accelerometer A 10  is a device (smartphone and/or wearable) component that tracks, records, and reports acceleration and speed data of the device (xyz-axis acceleration and xyz-axis rotation rate). The device altimeter A 15  is a mobile device (smartphone and/or wearable) component that tracks, records and reports altitude data of the device. The device gyroscope A 20  is a mobile device (smartphone and/or wearable) component that tracks, records and reports alignment orientation data of the device relative to the earth&#39;s gravity (roll, pitch, yaw, and xyz-gravity). The device global positioning system (GPS) A 25  is a device (smartphone and/or wearable) component that tracks, records, and reports location data of the device. 
     The algorithms A 30  are procedures to determine rakat (prayer unit) count and prayer position based on data collected from the device accelerometer A 10 , device altimeter A 15 , device gyroscope A 20 , and/or device GPS A 25 . Examples of algorithms A 30  will be described in further detail with reference to  FIGS. 2-3 and 4A-9B . The processing engine A 35  is a hardware and/or software processor that determines the rakat (prayer unit) count and prayer position by executing the algorithms A 30  using the collected data as input. The processing engine A 35  also determines calculations for all reporting requirements and determines the notifications to be made and the timing of those notifications. 
     The local storage A 40  is a data store (e.g., physical memory) on the device (e.g., smartphone and/or wearable) that stores the data collected by the device sensors (accelerometer A 10 , altimeter A 15 , gyroscope A 20 , and GPS A 25 ) and the data/metrics calculated by the processing engine A 35  as a result of executing the algorithm(s) A 30 . The local storage A 40  also stores user configuration data. The mobile user interface (UI) reporting module A 45  is an application display module of the mobile application for generating the type and format of information (e.g. prayer activity information) to be presented from among the collected and calculated data/metrics mentioned above. 
     The device visual interface A 50  is a mobile device (smartphone and/or wearable) component that presents information (e.g., prayer activity information) to the user via visual elements (graphs, texts, diagrams, etc.) as determined by the processing engine A 35  and the mobile UI reporting module A 45 . The device audio interface A 55  is a mobile device (smartphone and/or wearable) component that presents information (e.g., prayer activity information) to the user via auditory elements (audible tones, voice, music, etc.) as determined by the processing engine A 35  and the mobile UI reporting module A 45 . The device haptic interface A 60  is a mobile device (smartphone and/or wearable) component that presents information (e.g., prayer activity information) to the user via vibratory elements (vibrations, etc.) as determined by the processing engine A 35  and the mobile UI reporting module A 45 . 
     The cloud storage user community reporting database is a data store on a central server that stores data and metrics collected by the device sensors (accelerometer A 10 , altimeter A 15 , gyroscope A 20 , and GPS A 25 ) and the data/metrics determined by the processing engine A 35  as a result of executing the algorithm(s) A 30  across the entire user community (i.e., all users executing the mobile application for prayer tracking). The website reporting module A 75  is an application display of collected and calculated data/metrics across the entire user community. 
     To be able to determine the prayer unit count and/or the prayer position or to predict and recommend the next step, multiple algorithms may be used either individually or in combination to increase accuracy. The algorithm(s) used will depend on the data that is available from the device. 
       FIG. 2  is a flowchart illustrating the implementation of the method for detecting prayer units using output from an altimeter according to a non-limiting embodiment. 
     The method in  FIG. 2  is an altimeter based algorithm, executed in the application running, e.g., on a smartphone. The altimeter based algorithm analyzes relative position and altitude using barometric pressure sensors. 
     As shown in  FIG. 2 , in the altimeter based algorithm, a user is allowed to set a “Relative Difference” setting(s) that the mobile application will use to assess patterns unique to the users. These settings might be adjusted as needed for fine tuning the accuracy of the application. For the altimeter based algorithm with the smartphone or other mobile device in the pocket while the user is engaged in the prayer session, a proper height difference should be set between a person&#39;s standing position and the prostration and/or sitting positions. If the phone were in a user&#39;s pocket, we would need to estimate the distance between height of the pocket when standing versus. when sitting, which is the relative distance in this scenario. The user should be able to tune this “Relative Distance” value to make the calculations more accurate. For example, the user may want to increase or decrease the distance. In this exemplary embodiment, 20 inches is set as the default, which may work for some people, but may not be ideal for others (in which case they can tune the value). In the wrist-based mobile devices such as the Apple watch, the “Relative Setting(s)” may be more nuanced which may include the distance between altitude from various positions (e.g., Takbir (raising of hands), standing, Raku (bowing), sitting). 
     In  FIG. 2 , the application will follow this overview of the algorithm below for the prayer tracking process (which involves tracking at least the rakats (prayer units) and the prayer positions within each rakat (prayer unit)).
         1) The altimeter based algorithm begins with step  101  where the user starts the application for prayer tracking.   2) Step  102  allows the user to set desired setting(s) (such as “Relative Difference”) that the application will use to assess patterns unique to the users. These settings might be adjusted as needed for fine tuning the accuracy of the application.   3) Once the user indicates to the application in step  103  (e.g., by making an appropriate selection in the application) that the application should start the prayer tracking process (e.g., right before the user begins a prayer session), the application will follow the following overview of an exemplary algorithm A 30  executed on the processing engine A 35  using data collected by the device altimeter A 15 .
           a) Capture “Current Altitude” settings multiple times a second ( 103 ).   b) Set Variables ( 104 ):
               i) Determine the current altitude of the user in ‘Standing’ position. Set the value as “Standing Altitude”.   ii) Set the “Current Position” to Standing.   iii) Set the “Prostration Altitude” to Standing Altitude—Relative Difference.   iv) Set Prostration_Num=0   v) Set Prayer_Unit_Num=1   
               c) Compare the “Current Altitude” to prior recorded altitude ( 110 ).
               i) Loop
                   (1) If the altitude changes by more than X units (Variance setting) from Prior position ( 110 ), then    (a) Set the “Current Position” to “Moving” ( 111 )    (b) If the altitude is within range of X units variance for the last 5 measurements, determine if the altitude is within the Standing Altitude or the Prostration Altitude ( 120 ).    (i) If in Standing Range ( 130 ):    1. Set “Current Position” to “Standing”    2. Update mobile UI A 45  with Prayer_Unit_Num value    (ii) If in Prostration Range ( 140 ):    1. If “Current Position” is not “Prostration”    a. Set Current Position to “Prostration”    b. Increment Prostration_Num by +1    c. Set Prayer_Unit_Num to ROUND_DOWN(Prostration_Num)+1    d. If Prostration_Num is even number, Alert user of the Prayer_Unit_Num ( 141 ).    2. If position is “Prostration”, no action.   
                   
               
               

       FIG. 3  is a flowchart illustrating the implementation of the method for detecting prayer units using output from an accelerometer and a gyroscope according to another non-limiting embodiment. 
     The method in  FIG. 3  is a gyroscope and accelerometer based algorithm that analyzes user position using device&#39;s 3-axis position and 3-axis acceleration sensors. 
     As shown in  FIG. 3 , in the gyroscope and accelerometer based algorithm, a user is allowed to set a calibrate setting(s) that the application will use to assess patterns unique to the users. These settings might be adjusted as needed for fine tuning the accuracy of the application. For example, the user can define or make the application aware of the following: 
     Multiple Takbirs (raising of hands multiple times): Some individuals do multiple Takbir&#39;s during the prayer session, and the application should know this to properly identify a prayer unit (rakat) number.
 
Certain sects of Muslims do not put their hands on their waist when they stand, while others do so this can be defined.
 
Some people with knee or joint issues cannot sit properly when they are in the prayer session, and the application can account for this if it is made aware of such issues.
 
     Men and women hold their hands at different positions while standing, and the application can make appropriate adjustments. 
     In essence, the more data unique to the user the application can capture or be made aware of, the more detailed the algorithm can be, especially by adjusting the reference positions and movement patterns dynamically for each person. 
     In  FIG. 3 , the application will follow the overview of the algorithm below for the prayer tracking process (which involves tracking at least the rakats (prayer units) and the prayer positions within each rakat (prayer unit)).
         1) The gyroscope and accelerometer based algorithm begins with step  201  where the user starts the application for prayer tracking.   2) Step  202  allows the user to set desired settings that the application will use to assess patterns unique to the users. These settings might be adjusted as needed for fine tuning the accuracy of the application.   3) Once the user indicates to the application in step  203  (e.g., by making an appropriate selection in the application) that the application should start the prayer tracking process ( 203 ) (e.g., right before the user begins a prayer session), the application will follow the following overview of an exemplary algorithm A 30  executed on the processing engine A 35  using data collected by the device accelerometer A 10  and device gyroscope A 20 .
           a) Load gyroscope and accelerometer position values for prayer positions for raising hands to head (Takbir), standing (Qiyam), bowing (Raku), prostration (Sajda), and sitting between prostrations (Tashahud). Each postion could have multiple possible setting to accommodate the different ways in which a user can wear a device (left/right hand, inside/outside of wrist etc.) ( 204 ).   b) Capture gyroscope and accelerometer values multiple times a second ( 210 ) using the device gyroscope A 20  and device accelerometer A 10 .   c) If Acceleration_Values&gt;0.03 ( 220 ), then
               i) Set User_State as “Moving” ( 221 )   
               d) If “Acceleration_Values”&lt;=0.03, Determine current position from Reference Data ( 230 )   i) If position values match those of Takbir ( 231 ), Set Variables:
               (1) If Position not equal to “Takbir”
                   (a) If Takbir_Count=0,    (i) Set Sajda_Num=0    (ii) Set Prayer_Unit_Started_Num=1+(RoundUp(Sajda/2))    (iii) Set Prayer_Unit_Finished_Num=RoundUp(Sajda/2)   (b) Increment Takbir_Count by 1   (c) Set Position=“Takbir”   
                   
               ii) If position values match those of Qiyam ( 250 ), Set Variables:
               (1) Set Position=“Qiyam”   
               iii) If position values match those of Raku ( 260 ), Set Variables:
               (1) Set Position=“Raku”   
               iv) If position values match those of Sajda ( 240 ), Set Variables:
               (1) If Postion is not equal to “Sajda”
                   (a) Set Position=“Sajda”   (b) Set Sajda_Num=Sajda_Num+1   (c) Set Prayer_Unit_Started_Num=1+(RoundDown (Sajda_Num/2))   (d) Set Prayer_Unit_Finished_Num=RoundDown (Sajda_Num/2)   (e) If Sajda_Num is even number, alert the user with a count number of “Prayer_Unit_Started_Num”   
                   
               v) If position values match those of Tashahud ( 270 ), Set Variables:
               (1) Set Position=“Tashahud”   
               
               

     The mobile application embodiments disclosed above with respect to  FIG. 2 or 3  or other such embodiments may utilize the device GPS A 25  and a system clock to determine the user&#39;s location and time of day in order to determine which of the five obligatory prayers or a non-obligatory prayer the user will most likely be conducting. Further, the application can recommend to the user which of the five obligatory prayers or non-obligatory prayer along with the number of prayer units to perform. The user can also manually enter their location and/or which prayer they will be conducting. 
       FIGS. 4A-9B  illustrate the present inventors&#39; work in identifying thresholds for determining prayer units and prayer positions while a user is engaged in a prayer session. 
       FIG. 4A  is a graph which shows collected roll, pitch, and yaw data from a device&#39;s gyroscope to show positional orientation of the device during an exemplary prayer session including three prayer units. 
       FIG. 4B  is a graph which shows a coded overlay on top of the data from  FIG. 4A  to show the breakdown of the positional orientation of the device corresponding to the specific posture of the user within each prayer unit of the three prayer units in the exemplary prayer session. 
       FIG. 5A  is a graph which shows collected XYZ gravity data from a device&#39;s gyroscope to show positional orientation of the device during an exemplary prayer session including three prayer units. 
       FIG. 5B  is a graph which shows a coded overlay on top of the data from  FIG. 5A  to show the breakdown of the positional orientation of the device corresponding to the specific posture of the user within each prayer unit of the three prayer units in the exemplary prayer session. 
       FIG. 6A  is a graph which shows collected XYZ acceleration data from a device&#39;s accelerometer to show the movement (and lack thereof) of the device when transitioning from one posture of a prayer unit to another and transitioning between prayer units during an exemplary prayer session including three prayer units. 
       FIG. 6B  is a graph which shows a coded overlay on top of the data from  FIG. 6A  to show the breakdown of the movement of the device corresponding to the user transitioning from one posture of a prayer unit to another and transitioning between prayer units in the exemplary prayer session. 
       FIG. 7A  is a graph which shows collected XYZ rotation data from a device&#39;s accelerometer to show the movement (and lack thereof) of the device when transitioning from one posture of a prayer unit to another and transitioning between prayer units during an exemplary prayer session including three prayer units. 
       FIG. 7B  is a graph which shows a coded overlay on top of the data from  FIG. 7A  to show the breakdown of the movement of the device corresponding to the user transitioning from one posture of a prayer unit to another and transitioning between prayer units in the exemplary prayer session. 
       FIG. 8A  is a graph which shows the collected Altitude data from a device&#39;s altimeter to show the altitude of the device during an exemplary prayer session including three prayer units. 
       FIG. 8B  is a graph which shows a coded overlay on top of the data from  FIG. 8A  to show the breakdown of the altitude of the device corresponding to the specific posture of the user within each prayer unit of the three prayer units in the exemplary prayer session. 
       FIG. 9A  is a graph which shows the combined collected data (‘roll pitch, yaw’, XYZ gravity, XYZ acceleration, XYZ rotation and altitude) from a device&#39;s gyroscope, accelerometer and altimeter during an exemplary prayer session including three prayer units. 
       FIG. 9B  is a graph which shows a coded overlay on top of the data from  FIG. 8A  to show the breakdown of the combined data of the device corresponding to the specific posture of the user within each prayer unit of the three prayer units in the exemplary prayer session. 
     As can be seen from  FIGS. 4A-9B , the collected data in each graph can be used to identify certain transition points when the user&#39;s prayer position changes and based on the values of the data points and the identified transition points, it can be determined which position the user is in (e.g., raising their hands at the outset of prayer (takbir), standing, bowing down (raku), prostrating (sajda), sitting, etc.). 
     Of note, smartphone and wearable device algorithms based on pocket versus wrist implementations are largely the same. The difference is that wearable wrist device will detect Takbir and also Raku, where the smartphone will not. The algorithm does not need to change. 
     The difference between the two is that the wearable wrist device and smartphone will trigger different Gyroscope data values for the various positions which will be distinctly different combination of Roll, Pitch, Yaw, and X, Y, Z gravity orientation. The accelerations values are not used to calculate the position, rather they are used to indicate the person is transitioning between various positions. 
     Furthermore, as data sets of user sessions are gathered, it is possible to use machine learning algorithms to decipher patterns in an individual user&#39;s motions to specifically tune the position algorithms to precisely calculate the number of Rakats (prayer units) that the user has completed and more accurately alert the user of their progress. As can be seen in  FIGS. 4-9 , where each graph is overlaid with specific prayer positions, the variance within the pattern of an individual person can be tuned. Calculating and understanding variances both between individuals as well as within different sessions of a specific person can make the algorithm dynamic and very accurate at an individual person level. 
     One or more exemplary embodiments may also be embodied as programmed commands to be executed in various computer means, and then may be recorded to a computer-readable storage medium. The computer-readable storage medium may include one or more of the programmed commands, data files, data structures, or the like. The programmed commands recorded to the computer-readable storage medium may be particularly designed or configured for one or more exemplary embodiments. Examples of the computer-readable storage medium include magnetic media including hard disks, magnetic tapes, and floppy disks, optical media including CD-ROMs and DVDs, magneto-optical media including optical disks, and a hardware apparatus designed to store and execute the programmed commands in ROM, RAM, a flash memory, and the like. The hardware apparatus may be configured to function as one or more software modules so as to perform operations of one or more exemplary embodiments. 
     It should be understood that the exemplary embodiments described herein should be considered in a descriptive sense only and not for purposes of limitation. Descriptions of features or aspects within each embodiment should typically be considered as available for other similar features or aspects in other embodiments. 
     While one or more exemplary embodiments have been described with reference to the figures, it will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the inventive concept as defined by the following claims.