Techniques for managing cellular connection status of submerged wireless devices

Abstract

Techniques for managing cellular connection status of submerged wireless devices are described. The wireless device may include a sensor that analyzes environmental conditions to determine when (or not) the wireless device is submerged underwater and what depth the wireless device is submerged underwater. The sensor may also determine different types of water activities in which a user of the wireless device is currently participating, such as swimming, snorkeling, free diving, and water lung diving. In turn, the wireless device may utilize this information to manage its cellular connection status in order to avoid wasted energy consumption. In particular, the techniques enable the submerged wireless devices to eliminate them as long as any existing cellular connection and connection re-attempts are less likely to be successful. Further, the technique enables the wireless device to perform a connection re-attempt when the connection re-attempt is appropriate and possibly successful.

Description

Technical Field

[0001] The described embodiments set forth techniques for managing the cellular connection state of a submerged wireless device. Specifically, the techniques enable a submerged wireless device to eliminate any existing cellular connections and connection retry attempts whenever they are unlikely to succeed (e.g., while the wireless device remains submerged). Additionally, the techniques enable the wireless device to perform a connection retry when a connection retry is appropriate and likely to succeed (e.g., when the wireless device is no longer submerged). Background Art

[0002] There is a continuing interest in extending the battery life of wireless devices in order to be environmentally responsible and provide an enhanced user experience. Specifically, it is desirable to reduce the amount of energy consumed by wireless devices so that they require less overall energy to operate. In this regard, it may be beneficial to adjust the operational configuration of wireless devices so that they do not perform unnecessary tasks that wastefully consume energy. Such reductions may provide a variety of benefits, including smaller battery capacity (thereby enabling a smaller form factor), reduced charging cycle requirements, and extended battery life.

[0003] Wireless devices (particularly wearable devices, cell phones, tablet computers, etc.) continue to grow in popularity and overall complexity. For example, while some wearable devices typically have a small form factor, they now include a cellular radio that enables the wearable device to send and receive information via a cellular connection. In some cases, some wearable devices are waterproof (or water resistant) and enable the wearer to perform a variety of water activities, such as swimming, snorkeling, free diving, and even scuba diving, without damaging the wearable device.

[0004] Although cellular wireless technologies have improved greatly over the years, they continue to suffer from various connectivity constraints that present challenges in common operating scenarios. For example, such connectivity constraints may occur when a wireless device is deep inside a building, surrounded by tall buildings, or in an underground structure. In addition, such connectivity constraints occur when a wireless device (such as a wearable device) is submerged underwater, which causes cellular transmissions to degrade even at relatively shallow depths. Currently, when a wearable device is submerged and loses its cellular connection, it enters a network search mode and consumes energy by continuously attempting to reattach to an available cellular base station. This scenario is unfortunate because such attempts are unlikely to succeed as long as the wireless device remains submerged and a cellular connection is not possible.

[0005] In view of the foregoing, there is a need for a technique for managing the cellular connection status of a wireless device when the wireless device is submerged underwater. Summary of the invention

[0006] The present application describes techniques for managing the cellular connection state of a submerged wireless device. Specifically, the techniques enable a submerged wireless device to eliminate any existing cellular connections and connection retry attempts whenever they are unlikely to succeed (e.g., when the wireless device remains submerged). In addition, the techniques enable the wireless device to perform a connection retry when a connection retry is appropriate and likely to succeed (e.g., when the wireless device is no longer submerged).

[0007] One embodiment describes a method for managing a cellular connection state of a wireless device in connection with an aquatic activity performed using the wireless device. According to some embodiments, the method is performed at the wireless device and includes the following steps: (1) determining that the wireless device is submerged in water; (2) in response to determining that the wireless device meets a threshold depth: (i) starting a depth timer, wherein the wireless device: (a) terminates the depth timer whenever the wireless device no longer meets the threshold depth, and (b) restarts the depth timer whenever the wireless device meets the threshold depth after the depth timer is terminated; and (3) in response to identifying that the depth timer has expired: deactivating a baseband component of the wireless device to prevent the baseband component from attempting to establish a cellular connection.

[0008] The method also includes the following steps: after deactivating the baseband component: (4) determining that the wireless device is no longer submerged in water; (5) starting a hysteresis timer, wherein each time the wireless device is re-submerged in water, the wireless device restarts the hysteresis timer; and (6) in response to identifying that the hysteresis timer has expired: enabling the baseband component of the wireless device to enable the baseband component to establish the cellular connection.

[0009] Other embodiments include a non-transitory computer-readable storage medium configured to store instructions that, when executed by a processor included in a computing device, cause the computing device to implement the methods and techniques described in the present disclosure. Still other embodiments include a hardware computing device that includes a processor that can be configured to cause the hardware computing device to implement the methods and techniques described in the present disclosure.

[0010] Other aspects and advantages of the present invention will become apparent from the following detailed description taken in conjunction with the accompanying drawings which illustrate by way of example the principles of the described embodiments.

[0011] The present disclosure is provided for the purpose of summarizing some example embodiments only, so as to provide a basic understanding of some aspects of the subject matter described herein. Therefore, it should be understood that the above-mentioned features are only examples and should not be construed as narrowing the scope or essence of the subject matter described herein in any way. Other features, aspects and advantages of the subject matter described herein will become apparent through the following detailed description, drawings and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The present disclosure will be more readily understood through the following detailed description taken in conjunction with the accompanying drawings, in which like reference numerals designate like structural elements.

[0013] Figure 1 Illustrated is a block diagram of different components of an example system configured to implement the various techniques described herein, according to some embodiments.

[0014] Figure 2 Illustrated according to some embodiments Figure 1 A block diagram of a more detailed view of certain components of a wireless device illustrated in FIG.

[0015] Figure 3 Illustrated according to some embodiments Figure 1 and Figure 2 Conceptual illustration of the manner in which sensors of a wireless device may be configured to analyze environmental conditions.

[0016] Figure 4A and Figure 4B Illustrated are methods of techniques for modifying the cellular connection state of a wireless device when the wireless device is submerged in water according to some embodiments.

[0017] Figure 5 A conceptual diagram illustrating an example scenario involving a wireless device experiencing a modification in a cellular connection state related to a water activity in which a user of the wireless device is engaging in, according to some embodiments.

[0018] Figure 6 A conceptual diagram of an exemplary user interface that may be displayed by a wireless device that experiences a cellular connection status modification related to a water activity in which a user of the wireless device is engaging in, according to some embodiments, is illustrated.

[0019] Figure 7 A block diagram illustrating exemplary elements of a mobile wireless device according to some embodiments is illustrated. DETAILED DESCRIPTION

[0020] Representative applications of the methods and apparatus according to the present application are described in this section. These examples are provided only to add context and aid in understanding the described embodiments. Therefore, it will be apparent to those skilled in the art that the described embodiments may be practiced without some or all of these specific details. In other cases, in order to avoid unnecessarily obscuring the described embodiments, well-known processing steps are not described in detail. Other applications are possible, so that the following examples should not be considered limiting.

[0021] In the following detailed description, reference is made to the accompanying drawings which form a part of the specification and in which are shown by way of illustration specific embodiments in accordance with the described embodiments. Although these embodiments are described in sufficient detail to enable those skilled in the art to practice the described embodiments, it is to be understood that these examples are not limiting; other embodiments may be used and modifications may be made without departing from the spirit and scope of the described embodiments.

[0022] The described embodiments set forth techniques for managing the cellular connection state of a submerged wireless device. Specifically, the techniques enable a submerged wireless device to eliminate any existing cellular connections and connection retry attempts whenever they are unlikely to succeed (e.g., while the wireless device remains submerged). Additionally, the techniques enable the wireless device to perform a connection retry when a connection retry is appropriate and likely to succeed (e.g., when the wireless device is no longer submerged).

[0023] According to some embodiments, the wireless device may include one or more sensors designed to analyze environmental conditions to effectively determine when the wireless device is (or is not) submerged underwater, at what depth the wireless device is submerged underwater, etc. The sensors may also enable the wireless device to effectively determine different types of water activities that the user of the wireless device is currently engaged in, such as swimming, snorkeling, free diving, scuba diving, etc. The wireless device may then utilize this information to manage its cellular connection state in order to avoid wasteful energy consumption.

[0024] Specifically, the wireless device may identify scenarios in which energy savings may be achieved, which may include, for example, when the wireless device is submerged underwater at at least a threshold depth and for at least a threshold amount of time (wherein a cellular connection is physically impossible due to interference caused by the water). The wireless device may then deactivate its baseband component such that (1) an existing cellular connection (if any) is eliminated, and (2) the baseband component will not reattempt to establish a cellular connection until the baseband component is reenabled. The wireless device may also identify scenarios in which it is appropriate to re-enable the baseband component. For example, such scenarios may include when the wireless device has resurfaced and remained at the surface for at least a threshold period of time (wherein physical interference has been eliminated). The wireless device may then re-enable the baseband component so that it may re-attempt to establish a cellular connection.

[0025] In addition, the wireless device may take into account the type of water activity that is occurring while performing the aforementioned (or other) techniques. Specifically, the water activity may affect the value of the depth threshold and the different timers that direct the deactivation / reactivation of the baseband component. The wireless device may also take into account the water activity and other conditions that arise. For example, when the wireless device determines that it is no longer submerged underwater but surface swimming activity is occurring (e.g., swimming back to the boat after scuba diving)—the wireless device may choose to reactivate the baseband only after it determines that the swimming activity has ended. These techniques provide considerable benefits because they enable the wireless device to automatically deactivate / reactivate the baseband component based on (1) physical limitations that arise with respect to cellular connectivity and (2) user activities in which the user may (or may not) desire / utilize a cellular connection.

[0026] These and other embodiments are referred to below. Figures 1 to 7 Discussion is made; however, those skilled in the art will readily appreciate that the detailed description given herein with respect to these figures is for illustrative purposes only and should not be construed as limiting.

[0027] Figure 1 1 illustrates a block diagram of various components of a system 100 configured to implement the various techniques described herein, according to some embodiments. More specifically, Figure 1 A brief overview of a system 100 is illustrated, which includes a wireless device 102 (also referred to as a device, wireless device, mobile device, user equipment (UE), etc.), a set of base stations 112-1 to 112-N managed by different mobile network operators (MNOs) 114. Additional MNO infrastructure servers such as those used for account management and billing are not shown. The wireless device 102 may represent a mobile computing device (e.g., of Apple Watch, etc.), base stations 112-1 to 112-n may represent cellular wireless network entities configured to communicate with wireless device 102, including evolved NodeBs (eNodeBs or eNBs) and / or next generation NodeBs (gNodeBs or gNBs), and MNO 114 may represent different wireless service providers that provide specific cellular wireless services (e.g., voice and data) to which wireless device 102 may subscribe, such as via a subscription account of a user of wireless device 102.

[0028] like Figure 1 As shown, the wireless device 102 may include processing circuitry (which may include one or more processors 104 and memory 106), at least one embedded universal integrated circuit card (eUICC) 108, and baseband radio circuitry 110 for sending and receiving cellular wireless radio frequency signals. The baseband radio circuitry 110 may include analog hardware components, such as antennas and amplifiers, and digital processing components, such as signal processors (and / or general / limited purpose processors) and associated memory. In some embodiments, in addition to or in lieu of the eUICC 108, the wireless device 102 includes one or more physical UICCs 118 (also referred to as subscriber identity modules (SIM) cards). The components of the wireless device 102 work together to enable the wireless device 102 to provide useful features to the user of the wireless device 102, such as cellular wireless network access, non-cellular wireless network access, localized computing, location-based services, and Internet connectivity. The eUICC 108 may be configured to store multiple electronic SIM (eSIM) profiles for accessing cellular wireless services provided by different MNOs 114 via connecting to their respective cellular wireless networks through base stations 112-1 to 112-N. For example, the eUICC 108 may be configured to store and manage one or more eSIM profiles of one or more MNOs 114 for different subscriptions associated with the wireless device 102. To enable access to services provided by the MNOs, the eSIM profiles may be reserved for subsequent download and installation to the eUICC 108.

[0029] In addition, and if Figure 1As shown, the wireless device 102 may include one or more sensors 120 capable of analyzing environmental conditions 122. Specifically, the sensors may represent hardware and / or software components that enable the wireless device 102 to detect and process environmental conditions 122 in order to provide the functionality described herein. For example, the sensors 120 may enable the wireless device 102 to accurately determine when the wireless device 102 is (or is not) submerged underwater, at what depth the wireless device is submerged underwater, etc. The sensors 120 may also enable the wireless device 102 to accurately determine different types of water activities that the user of the wireless device 102 is currently participating in, such as swimming, snorkeling, free diving, scuba diving, etc. The wireless device 102 may then use this information to manage its cellular connection state in order to avoid wasteful energy consumption. The following is in conjunction with Figure 3 A more detailed explanation of the sensors 120 and the environmental conditions 122 is provided.

[0030] Figure 2 Illustrated according to some embodiments Figure 1 A block diagram of a more detailed view 200 of certain components of the wireless device 102 is shown. Figure 2 As shown, the processor 104 in conjunction with the memory 106 may implement a main operating system (OS) 202 configured to execute applications 204 (eg, native OS applications and user applications). Figure 2 As shown, the eUICC 108 may be configured to implement an eUICC OS 206 that is configured to manage the hardware resources of the eUICC 108 (e.g., a processor and memory embedded in the eUICC 108). The eUICC OS 206 may also be configured to manage the eSIM profiles 208 stored by the eUICC 108, such as by downloading, installing, deleting, enabling, disabling, modifying, or otherwise performing management of the eSIM profiles 208 within the eUICC 108, and providing access to the eSIM profiles 208 to the baseband radio circuit 110 to provide access to wireless services to the wireless device 102. The eUICC 108 OS may include an eSIM profile manager 210 that may perform management functions for various eSIM profiles 208. Figure 2 In the illustrated example, each eSIM profile 208 may include a number of applets 212 that define the manner in which the eSIM profile 208 operates. For example, one or more of the applets 212, when implemented in conjunction with the baseband radio circuitry 110 and the eUICC 108, may be configured to enable the wireless device 102 to communicate with the MNO 114 and provide useful features (e.g., phone calls and Internet access) to a user of the wireless device 102.

[0031] Likewise Figure 2As shown, the baseband radio circuit 110 of the wireless device 102 may include a baseband OS 214 configured to manage the hardware resources (e.g., processor, memory, different radio components, etc.) of the baseband radio circuit 110. According to some embodiments, the baseband radio circuit 110 may implement a baseband manager 216 configured to interface with the eUICC 108 to establish a secure channel with the MNO provisioning server and obtain information (such as eSIM profile data) from the MNO provisioning server for managing the eSIM profile 208. The baseband manager 216 may be configured to implement services 218, which represent a collection of software modules instantiated by various applets 212 of enabled eSIM profiles 208 included in the eUICC 108. For example, the services 218 may be configured to manage different connections between the wireless device 102 and the MNO 114 according to different eSIM profiles 208 enabled within the eUICC 108.

[0032] Figure 3 A conceptual diagram 300 illustrates the manner in which the sensor 120 of the wireless device 102 may be configured to analyze an environmental condition 122 according to some embodiments. Figure 3 As shown, the sensor 120 can be configured to analyze various environmental conditions 122, such as motion, sound, pressure, light, humidity, temperature, location, etc. Note that Figure 3 The environmental conditions 122 illustrated in FIG. 1 are exemplary only and are not meant to be limiting. Rather, any number and type of sensors 120 may be included in the wireless device 102 to analyze any environmental conditions 122 without departing from the scope of the present disclosure.

[0033] As previously discussed herein, each sensor 120 may represent a hardware and / or software component implemented on the wireless device 102. According to some embodiments, each sensor 120 may be configured to analyze a particular environmental condition 122 and output raw and / or processed information. For example, with respect to raw information, a sensor 120 designed to analyze motion may be configured to output acceleration information, orientation information, etc., while a sensor 120 designed to analyze sound may be configured to output decibel information, frequency information, etc. Continuing with the foregoing example, and with respect to processed information, the motion sensor 120 may generate an abstraction of the raw data in order to provide useful information, reduce the processing burden on the machine learning engine 302, etc. For example, the motion sensor 120 may determine that a particular activity (e.g., walking, running, swimming, etc.) is occurring based on the raw data it collects, and the sound sensor 120 may determine that a particular activity (e.g., speaking, exercising, etc.) is also occurring based on the raw data it collects. It is noted that the foregoing examples are not intended to be limiting, and any number of sensors 120 may be configured to provide raw / processed information at any level of granularity without departing from the scope of the present disclosure.

[0034] like Figure 3 As shown, the sensor 120 may be configured to output information (e.g., raw information, processed information, etc.) to a machine learning engine 302 implemented on the wireless device 102. According to some embodiments, the machine learning engine 302 may be configured based on training data 304 (collected by other wireless devices placed in the same or similar water scenes described herein), which enables the machine learning engine 302 to generate useful information based on what is collected by the sensor 120. Such useful information may include, for example, identifying when the wireless device 102 is (or is not) submerged underwater. In addition, the useful information may include the type of water activities in which the user of the wireless device 102 (and the wireless device 102 itself) participates, such as swimming, snorkeling, free diving, scuba diving, etc. It is noted that the foregoing examples are not intended to be limiting, and the machine learning engine 302 may be configured to generate any useful information at any level of granularity without departing from the scope of the present disclosure. As described in more detail below, the wireless device 102 may utilize such information to effectively determine when to prudently modify its cellular connection state for the purpose of energy conservation.

[0035] According to some embodiments, the machine learning engine 302 may determine when the wireless device 102 is submerged underwater by analyzing one or more of motion information, sound information, pressure information, light information, humidity information, temperature information, location information, etc. For example, the machine learning engine 302 may determine that the wireless device 102 is submerged underwater when: (1) the motion information indicates that the wireless device 102 is suspended in the water (e.g., on its surface or below it), (2) the sound information (e.g., chaotic noise, splashing, etc.) indicates that the user of the wireless device 102 is engaged in water activities, (3) the pressure information indicates that the wireless device 102 is at a specific depth underwater, (4) the light information indicates a specific intensity, hue, fluctuation pattern, etc. that suggests that the wireless device 102 is submerged underwater, (5) the humidity information indicates the presence of water, (6) the temperature information indicates a sudden drop (or increase) in ambient temperature (which suggests that the wireless device 102 has moved from air to water), and / or (7) the location information indicates that the wireless device 102 is located in a body of water. Note that the machine learning engine 302 is not required to analyze all of the aforementioned information in order to accurately determine when the wireless device 102 is submerged in water. Rather, the machine learning engine 302 may effectively determine when the wireless device 102 is submerged in water by analyzing fewer / other environmental conditions 122 under the same / different considerations without departing from the scope of the present disclosure.

[0036] Additionally, and in accordance with some embodiments, the machine learning engine 302 may determine when the wireless device 102 is engaging in a water activity by analyzing one or more of motion information, sound information, pressure information, light information, humidity information, temperature information, location information, etc. In one example, the machine learning engine 302 may determine that the user of the wireless device 102 (and the wireless device 102 itself) is engaging in a swimming activity when: (1) the motion information reflects a particular swimming stroke (e.g., freestyle, breaststroke, backstroke, butterfly stroke, etc.), (2) the sound, pressure, light, and / or temperature information indicates rapid fluctuations between above and below the water (e.g., the user's arms repeatedly moving in and out of the water), and (3) the location information indicates that the wireless device 102 is located in a body of water.

[0037] In another example, the machine learning engine 302 may determine that the wireless device 102 (and its user) is engaging in a scuba diving activity when: (1) motion information indicates suspension in water combined with moderate upward / downward acceleration, (2) sound, pressure, light, and / or temperature information indicates that the wireless device 102 has entered and remained underwater for an extended period of time, and (3) location information indicates that the wireless device 102 is located in a body of water. Similar methods may be used to identify other water-based activities, such as free diving, snorkeling, etc. Note that the machine learning engine 302 is not required to analyze all of the foregoing information in order to accurately determine the different types of water activities that the user / wireless device 102 is engaging in. Rather, the machine learning engine 302 may effectively determine when the user / wireless device 102 is engaging in a water activity by analyzing fewer / other environmental conditions 122 under the same / different considerations without departing from the scope of the present disclosure.

[0038] It is noted that the foregoing environmental conditions 122 and the foregoing example ways in which they may be analyzed by the machine learning engine 302 are not meant to be limiting. Rather, the machine learning engine 302 may be configured to analyze any number of environmental conditions 122 in any manner to effectively identify different states of the wireless device 102 without departing from the scope of this disclosure. For example, the machine learning engine 302 may consider non-environmental conditions when performing its analysis. In one example, if a user of the wireless device 102 has granted the wireless device 102 permission to access the user's calendar information, the wireless device 102 may analyze such calendar information to at least partially determine the different states of the wireless device 102 discussed herein. For example, if a calendar entry indicates a scuba diving outing from 3PM to 4PM, and the current time is within that range, the machine learning engine 302 may incorporate such information in making its determination.

[0039] In another example, if the user of the wireless device 102 has granted the wireless device 102 permission to analyze the user's current / past activities, the wireless device 102 may analyze such information to at least partially determine the different states / activities discussed herein that the user / wireless device 102 may currently be engaged in. For example, the wireless device 102 may effectively determine that the user may be engaged in a water activity if the user has demonstrated a strong pattern of such engagement at a particular date / time when making the determination. In another example, the wireless device 102 may analyze past or current workout activities (e.g., swimming workouts, snorkeling workouts, free diving workouts, scuba diving workouts, etc.) identified on the device (automatically or through user input). Again, it is noted that these examples are not meant to be limiting, and the wireless device 102 may utilize any method for effectively identifying the various states / activities discussed herein.

[0040] In any case, and if Figure 3As shown, the information output by the machine learning engine 302 can be directed to the cellular connection manager 306. According to some embodiments, the cellular connection manager 306 can be configured to analyze the information output by the machine learning engine 302 and modify the cellular connection state of the wireless device 102 when appropriate. Figure 4A , Figure 4B , Figure 5 and Figure 6 Describes the details of the manner in which the machine learning engine 302 operates.

[0041] Figure 4A and Figure 4B A method 400 is illustrated for modifying the cellular connection state of a wireless device when the wireless device 102 is submerged in water according to some embodiments. According to some embodiments, the method 400 may be combined with the above Figure 3 The described implementation of the cellular connection manager 306 discussed above. However, it is noted that any number of entities implemented on the wireless device 102 may assist (or replace) the cellular connection manager 306 to provide the functionality discussed herein without departing from the scope of the present disclosure.

[0042] like Figure 4A As shown, method 400 begins at step 402, where cellular connection manager 306 receives an indication that wireless device 102 is submerged in water. For example, when machine learning engine 302 has effectively determined (e.g., using the above combined Figure 3 306) has entered a body of water. Note that the machine learning engine 302 and / or cellular connection manager 306 may ignore the submersion condition when appropriate (e.g., when the submersion condition is only transient in nature). This may occur, for example, when a user of the wireless device 102 is washing hands, showering, etc., where an existing cellular connection (if any) would not be affected by the temporary submersion and therefore should not be modified. In any scenario, Figure 4A Step 402 in represents a scenario in which the wireless device 102 has reliably determined that a legitimate immersion of the wireless device 102 has occurred.

[0043] At step 404, the cellular connection manager 306 determines whether the wireless device 102 is at or below a first depth. According to some embodiments, the first depth may reflect an immersion depth at which physical challenges arise with respect to maintaining a cellular connection between the wireless device 102 and the base station 112. For example, if it is known that the wireless device 102 is unable to maintain a cellular connection when it is at or below a depth of three (3) feet in water, it may be prudent to modify the cellular connection state of the wireless device 102 with respect to reaching such depths. If, at step 404, the wireless device 102 determines that the wireless device 102 is at or below the first depth, the method 400 proceeds to step 406. Otherwise, the method 400 repeats at step 404 until the wireless device 102 is at or below the first depth. Note that although the wireless device 102 is not at the first depth, the method 400 may proceed to step 406. Figure 4A 4. Although illustrated at step 404 in FIG. 4, the method 400 may also be restarted if the cellular connection manager 306 receives an indication that the wireless device 102 is no longer submerged in water.

[0044] At step 406, the cellular connection manager 306 starts a depth timer. According to some embodiments, the depth timer may be implemented to avoid a "thrashing" scenario in which the wireless device 102 rapidly (and unnecessarily) switches between different connection states in response to repeatedly rising above / below a first depth within a relatively brief period of time (e.g., a few seconds). In this regard, the depth timer effectively requires the wireless device 102 to remain at or below the first depth for a threshold period of time before any adjustments to the cellular connection state of the wireless device 102 are performed. In one example, the depth timer may be set to twenty (20) seconds. Note that the depth timer may also be dynamic in nature. Specifically, the depth timer may vary based on what the wireless device 102 knows about the user and / or the activity being performed. For example, the wireless device 102 may determine over time that its user, while participating in a surface swimming exercise (in which the cellular connection (if any) should remain active), typically swims approximately three (3) feet below the surface of the water along the entire length of the pool, and that this action typically takes forty-five (45) seconds to complete. In this scenario, the depth timer may be set based on this amount of time (eg, fifty (50) seconds) so that the wireless device 102 does not terminate its cellular connection near the time when the user may be about to surface.

[0045] In any case, at step 408, the cellular connection manager 306 determines whether the depth timer has expired. Here, the term "expired" means that the depth timer (e.g., a count-down or count-up timer) has run for its set length of time (e.g., twenty (20) seconds). At step 408, if the cellular connection manager 306 determines that the depth timer has expired, the method 400 proceeds to step 414, which will be described in more detail below. Otherwise, the method 400 proceeds to step 410.

[0046] At step 410, the cellular connection manager 306 determines whether the wireless device 102 is above the first depth. It is noted that step 410 is part of the jolt avoidance technique discussed above in conjunction with step 406. Specifically, step 410 is implemented to determine whether the wireless device 102 temporarily submerged at or below the first depth, but then rose above the first depth before the threshold time period occurred (i.e., before the depth timer expired). If, at step 410, the cellular connection manager 306 determines that the wireless device 102 is above the first depth, the method 400 proceeds to step 412, where the depth timer is terminated (i.e., ended). When step 412 is performed, the method 400 returns to step 402. In this regard, if there is an indication that the wireless device 102 remains submerged—but submerged above the first depth, the depth timer will not be restarted at step 406 until the wireless device 102 is at or below the first depth at step 404.

[0047] Alternatively, if at step 410, the cellular connection manager 306 determines that the wireless device 102 is above the first depth (i.e., the wireless device 102 remains at or below the first depth), the method 400 continues back to step 408, where a determination is made as to whether the depth timer has expired (as discussed above).

[0048] Thus, the depth timer will continue to advance toward expiration as long as the wireless device 102 remains at or below the first depth. On the other hand, and as described above, if the wireless device is above the first depth before the depth timer expires, the depth timer is terminated and may be restarted at step 406 depending on (1) whether the wireless device 102 is submerged and (2) the current depth at which it is submerged.

[0049] When the wireless device 102 has remained at or below the threshold depth for the amount of time associated with the depth timer, step 414 occurs. When step 414 occurs, the cellular connection manager 306 deactivates the baseband radio circuit 110 and outputs a notification. Deactivating the baseband radio circuit 110 may involve any number of methods that effectively prevent the baseband radio circuit 110 from attempting to establish a cellular connection with the base station 112. For example, power to the baseband radio circuit 110 may be terminated, a configuration profile of the baseband radio circuit 110 may be updated to prohibit it from searching for the base station 112, etc. It is noted that the foregoing examples are not meant to be limiting, and any method may be utilized at any level of granularity to prevent the baseband radio circuit 110 from attempting to establish a cellular connection until it is appropriate to do so.

[0050] At the end of step 414, the wireless device 102 is operating in a state where the baseband radio circuit 110 is neither maintaining a cellular connection nor attempting to establish a cellular connection with the base station 112. This operating state will remain unchanged as long as the wireless device 102 remains submerged in water. However, when the wireless device 102 is no longer submerged, appropriate measures should be taken to attempt to restore the cellular connection, the details of which are discussed below in conjunction with steps 416 to 424.

[0051] Now go to Figure 4B At step 416, the cellular connection manager 306 receives an indication that the device is no longer submerged. For example, when the machine learning engine 302 has effectively determined (e.g., using the above combined Figure 3 102 has reached the surface of a body of water. Note that the machine learning engine 302 and / or the cellular connection manager 306 may ignore the surfacing condition when appropriate (e.g., when the submersion condition is only momentary in nature). This may occur, for example, when a user of the wireless device 102 is engaged in a free diving exercise and periodically surfaces for brief moments to take in air. In any case, when the wireless device 102 has reliably determined that a legitimate surfacing of the wireless device 102 has occurred, Figure 4A Step 416 in occurs.

[0052] At step 418, the cellular connection manager 306 starts a hysteresis timer. According to some embodiments, the hysteresis timer (similar to the depth timer) may be implemented to avoid a "thrashing" scenario in which the wireless device 102 rapidly (and unnecessarily) switches between different connection states in response to repeatedly rising above / below the water surface within a relatively brief period of time (e.g., a few seconds). In this regard, the hysteresis timer effectively requires that the wireless device 102 remain above the water surface (i.e., not submerged) for a threshold period of time before any adjustments to the cellular connection state of the wireless device 102 are performed. In one example, the hysteresis timer may be set to four (4) seconds. Note that, similar to the depth timer, the hysteresis timer may also be dynamic in nature and may be based on what the wireless device 102 knows about the user and / or the activity being performed.

[0053] In any case, at step 420, the cellular connection manager 306 determines whether the hysteresis timer has expired. According to some embodiments, the hysteresis timer may be implemented as an up-counting or down-counting timer that terminates when the amount of time assigned to the hysteresis timer expires. Again, the term "expired" means that the hysteresis timer has run for its set length of time (e.g., four (4) seconds). According to some embodiments, the hysteresis timer may also be configured to reset (i.e., restart) when one or more conditions are met. In any case, at step 420, if the cellular connection manager 306 determines that the hysteresis timer has expired, the method 400 proceeds to step 424, which will be discussed in more detail below. Otherwise, the method 400 proceeds to step 422.

[0054] At step 422, the cellular connection manager 306 determines whether immersion activity is detected. This may occur, for example, when the user of the wireless device 102 temporarily resurfaces and then rushes back into the water, at which time it would be urgent to enable the baseband radio circuit 110. At step 422, if the cellular connection manager 306 detects immersion activity, the method 400 proceeds to step 418, where the hysteresis timer is restarted. Steps 420 to 422 are then repeated until no immersion activity is detected by the length of the hysteresis timer. Otherwise, if no immersion activity is detected at step 422, the hysteresis timer continues to run, and the method 400 proceeds back to step 420 to determine whether the hysteresis timer has expired.

[0055] Finally, when the hysteresis timer has expired (meaning that the wireless device 102 has remained on the surface for a period of time associated with the hysteresis timer), the method 400 proceeds to step 424, where the cellular connection manager 306 enables the baseband radio circuit 110 and outputs a notification. Enabling the baseband radio circuit 110 may involve any number of approaches that effectively cause / permit the baseband radio circuit 110 to attempt to establish a cellular connection with the base station 112. For example, power to the baseband radio circuit 110 may be restored, a configuration profile of the baseband radio circuit 110 may be updated (to permit it to search for the base station 112), etc. It is noted that the foregoing examples are not meant to be limiting, and any approach may be utilized at any level of granularity to cause / permit the baseband radio circuit 110 to attempt to establish a cellular connection (when appropriate to do so).

[0056] In addition, and although not in FIG. 4A to FIG. 4B 4. However, it is noted that the various water activities that may be detected by the cellular connection manager 306 described herein may affect the manner in which the method 400 is implemented. For example, at step 402, the cellular connection manager 306 may (in conjunction with receiving an indication that the wireless device 102 is submerged) wait until it receives one or more additional indications that some form of water activity is (or is not) occurring. This approach may be beneficial because it will strengthen the overall confidence of the cellular connection manager 306 that the wireless device 102 is in fact submerged underwater and that activity is occurring when a cellular connection is not required and / or physically impossible. Alternatively, the cellular connection manager 306 may omit (or add) steps of the method 400 based on the type of activity detected.

[0057] In another example, the cellular connection manager 306 can modify the various timers and depths discussed in the present disclosure based on the type of water activity detected. For example, when swimming and snorkeling activities are detected, the depth thresholds and timers can be modified to account for surface-based water activities. Conversely, when free diving and scuba diving activities are detected, the depth thresholds and timers can be modified to account for subsurface-based water activities.

[0058] In yet another example, at step 416, the cellular connection manager 306 (in conjunction with receiving an indication that the wireless device 102 is no longer submerged) waits until it receives one or more additional indications that some form of water activity is (or is not) occurring. This may be beneficial, for example, when a scuba dive has just concluded but the user is swimming on the surface of the body of water for some time until the user is able to exit the water (e.g., to a beach, dock, boat, etc.). In this scenario, the wireless device 102 may not need to re-enable its cellular connection given that the user will be unlikely to utilize Internet-based services on the wireless device 102 when swimming to the destination.

[0059] therefore, Figure 4A and Figure 4B Techniques for modifying the cellular connection state of a wireless device when the wireless device 102 is submerged in water according to some embodiments are described. Figure 5 to describe example scenarios of when and how this technique can be implemented.

[0060] Figure 5 A conceptual diagram of an example scenario 500 involving a wireless device 102 experiencing a modification in a cellular connection state related to an example water activity in which a user of the wireless device 102 is participating is set forth in accordance with some embodiments. Figure 5 As shown, event 502 involves the cellular connection manager 306 identifying that the wireless device 102 has been submerged in water. Figure 4A Step 402 of the discussion. Figure 5 As shown, when the wireless device 102 is initially submerged underwater, no modification of the cellular connection state of the wireless device 102 is performed because the wireless device 102, although submerged, has not yet reached the threshold depth (at Figure 5 , the threshold depth is set at a depth of three (3) feet). This time period relates to the above combined Figure 4A Step 404 is discussed.

[0061] continue Figure 5 , when the cellular connection manager 306 determines that the wireless device 102 is at or below the threshold depth, event 504 occurs. Figure 4A Step 404 of the discussion. Figure 5 As shown, event 504 involves starting a depth timer set at twenty (20) seconds. Figure 4A As discussed previously herein, the depth timer effectively requires the wireless device 102 to remain at or below the threshold depth for at least twenty (20) seconds before modifying the cellular connection state of the wireless device 102. This time period is related to the above combined Figure 4A Steps 408 to 410 are discussed.

[0062] exist Figure 5 Continuing in the description, when the cellular connection manager 306 determines that the wireless device 102 has risen above the threshold depth before the depth timer expires (at sixteen (16) seconds, rather than the twenty (20) seconds required by the depth timer), event 506 occurs. The depth timer is then terminated and remains inactive until the wireless device 102 again descends to or below the threshold depth. This event is related to the above combined Figure 4A Step 412 is discussed.

[0063] exist Figure 5Continuing in FIG. 5 , after event 506 occurs, the wireless device 102 continues to ascend for approximately four (4) seconds and then begins to descend for another four seconds until it reaches the threshold depth of three feet, at which time event 508 occurs. Figure 5 As shown, event 508 may involve restarting the depth timer (i.e., at twenty (20) seconds). Again, this event involves the above combined Figure 4A Step 406 is discussed.

[0064] like Figure 5 As shown, after the depth timer is restarted at event 508, the wireless device 102 continues to descend to a greater depth (for a period of at least twenty (20) seconds) such that there is no threshold depth violation that would otherwise cause the depth timer to expire. This time period relates to the above combined Figure 4A Thus, after the depth timer expires, event 510 occurs, at which time the cellular connection manager 306 deactivates the baseband radio circuit 110 (eg, using any number of methods discussed herein). This event involves the above-mentioned combination Figure 4A Step 414 of the discussion.

[0065] After the baseband radio circuitry 110 is deactivated in conjunction with event 510, the wireless device 102 begins ascending toward service over a ten second period until it reaches a depth of zero (0) feet and is no longer (or only partially / intermittently) submerged. Figure 4B 416 discussed above. However, at this point in time, no modification of the cellular connection state of the wireless device 102 is performed because the wireless device 102 must remain in service for a satisfactory period of time despite being at the surface. Therefore, event 512 may involve the cellular connection manager 306 starting a hysteresis timer that is set at Figure 5 The event involves the above combination Figure 4B Step 418 of the discussion.

[0066] exist Figure 5 Continuing in FIG. 1 , after the hysteresis timer is started, the wireless device 102 remains at or near the surface of the water for approximately two (2) seconds, but suddenly begins to descend to approximately one (1) foot below the surface of the water during the two (2) second period. This time period is represented by Figure 5 The event 514 in FIG. 1 is represented by the hysteresis timer being continuously restarted as long as the wireless device 102 continues to violate the hysteresis timer by not remaining at the surface. Figure 4B Steps 418 to 422 are discussed.

[0067] Finally, event 516 involves the restarting of the hysteresis timer in conjunction with the wireless device 102 reaching the surface. Figure 5As shown, the wireless device 102 remains at the surface for the four (4) second threshold required by the hysteresis timer, thereby allowing the hysteresis timer to expire. Figure 4B Step 420 of the discussion. Therefore, and Figure 5 At event 518 in , the cellular connection manager 306 enables the baseband radio circuit 110 (eg, using any of the techniques described herein).

[0068] therefore, Figure 5 A conceptual diagram illustrating an example scenario in which a given wireless device 102 may experience a cellular connection state modification related to a water activity in which a user of the wireless device 102 is participating, according to some embodiments. Figure 6 An exemplary user interface is provided that may be implemented to provide valuable feedback to users so that they remain informed of (and not confused by) automatic cellular connection status adjustments occurring in connection with their water activities.

[0069] Figure 6 A conceptual diagram 600 illustrates an exemplary user interface that may be displayed by a wireless device 102 that experiences a cellular connection status modification related to a water activity in which a user of the wireless device 102 is engaging in, in accordance with some embodiments.

[0070] like Figure 6 As shown, the wireless device 102 may initially display a user interface 602, which may constitute, for example, a lock screen or a welcome screen of the wireless device 102. Figure 6 As shown, user interface 602 includes a plurality of bars indicating both the active cellular connection and the overall strength of the cellular connection.

[0071] When the cellular connection manager 306 receives an indication that the wireless device 102 has been submerged in water (e.g., as described above in conjunction with Figure 4A As described in step 402, the wireless device 102 may display a user interface 604. Figure 6 As shown, despite being submerged, the user interface 604 continues to display information regarding the cellular connection (given that the depth threshold (e.g., three (3) feet) / depth timer (e.g., twenty (20) seconds) discussed herein has not been met / expired, and thus the cellular connection state of the wireless device 102 remains unmodified). However, due to the submersion, the cellular connection strength will likely decrease, which is indicated by the decreasing number of bars in the user interface 604. The user interface may also display a water drop icon indicating that the wireless device 102 has entered submerged mode.

[0072] like Figure 6As shown, the user interface 606 indicates that the wireless device 102 is at a depth of seven (7) feet and has been submerged for three (3) or more feet for seventeen (17) seconds. At this point, although the depth threshold has been met, the depth timer has not expired, so the cellular connection remains active. However, due to the increased depth, the cellular connection will likely drop, which is indicated by the lack of a bar in the user interface 606.

[0073] Next, and if Figure 6 As shown, user interface 608 indicates a point in time at which wireless device 102 is at a depth of twelve (12) feet and has been submerged for three (3) or more feet for twenty (20) seconds. At this point, the depth threshold has been met and the depth timer has expired, which results in conditions suitable for modifying the cellular connection state of wireless device 102. Therefore, and as shown in user interface 608, the cellular connection is terminated (as indicated by the "X" of the cellular reception bar), and a notification is provided to the user indicating that baseband radio circuitry 110 has been deactivated.

[0074] Next, and if Figure 6 As shown, the user interface 610 indicates a point in time at which the user / wireless device 102 has remained submerged underwater for twelve (12) minutes and forty-three (43) seconds. At this point, the baseband radio circuitry 110 has remained deactivated, such that the wireless device 102 has not expended any resources attempting to reestablish a connection with the base station 112 (which would be futile given the physical limitations imposed by the given depth).

[0075] Next, and if Figure 6 As shown, user interface 612 indicates the moment when the user / wireless device 102 has ascended and reached the surface of the water after eighteen (18) minutes and fifty-two (52) seconds. Accordingly, the next user interface 614 is displayed, which indicates that the immersion mode is no longer active (as indicated by the "X" of the water drop icon) and that the cellular connection has been restored. User interface 614 may also provide a notification to inform the user that the baseband wireless circuit 110 has been re-enabled. Subsequently, the wireless device 102 may display a user interface 618, such as a lock screen or home screen, after the user has ended the immersion activity and the cellular connection has been restored.

[0076] Please note that Figure 6 The user interfaces illustrated in (and described herein) are exemplary only and are not meant to be limiting in any way. Rather, any number of user interfaces may be implemented to effectively inform users of the various issues and processes described throughout this disclosure without departing from its scope.

[0077] In addition, it should be noted that the different values ​​assigned to various timers, depth thresholds, etc. discussed herein are merely exemplary and are not meant to be limiting. On the contrary, any value may be assigned to a timer / depth threshold at any level of granularity without departing from the scope of the present disclosure. In addition, it should be noted that the number of timers / depth thresholds discussed herein is merely exemplary and is not meant to be limiting. On the contrary, any number of timers / depth thresholds (or other condition control mechanisms) may be implemented to provide finer (or coarser) granular control of the manner in which the wireless device 102 modifies its cellular connection state. For example, multiple cellular connection states may be implemented, in which the wireless device progressively enters (or exits) different connection states according to different conditions of the application. For example, the total amount of power supplied to the baseband and / or the number of reconnection attempts performed by the baseband may be iteratively increased (and vice versa) as the depth at which the wireless device meets the possibility of indicating surfacing decreases. Again, it should be noted that these examples are not meant to be limiting, and any number of connection states may be implemented at any level of granularity without departing from the scope of the present disclosure.

[0078] Finally, it is noted that the various techniques provided herein can be overridden by a user at any time, regardless of the state in which the wireless device 102 is operating. For example, when the wireless device 102 determines that it is prudent to deactivate the baseband, the user can still cause the baseband to be re-enabled, causing the wireless device 102 to begin searching for a base station. This is particularly useful in emergency situations, where the user should be ignored or overridden when the user would benefit from the possibility of the wireless device 102 successfully connecting to a base station.

[0079] Exemplary embodiments

[0080] In an exemplary embodiment, a method for managing a cellular connection status of a wireless device related to a water activity performed using the wireless device includes: i) determining that the wireless device is submerged underwater; ii) in response to determining that the wireless device meets a threshold depth, starting a depth timer, wherein the wireless device: a) terminates the depth timer each time the wireless device no longer meets the threshold depth, and b) restarts the depth timer each time the wireless device meets the threshold depth after the depth timer is terminated; and iii) in response to identifying that the depth timer has expired, deactivating a baseband component of the wireless device to prevent the baseband component from attempting to establish a cellular connection.

[0081] In some embodiments, the method further includes the wireless device, after deactivating the baseband component: i) determining that the wireless device is no longer submerged in water; ii) starting a hysteresis timer, wherein each time the wireless device is re-submerged in water, the wireless device restarts the hysteresis timer; and iii) in response to identifying that the hysteresis timer has expired, enabling the baseband component of the wireless device to enable the baseband component to establish the cellular connection. In some embodiments, determining that the wireless device is submerged in water includes analyzing information including at least one of the following: motion information, sound information, pressure information, light information, humidity information, temperature information, or location information. In some embodiments, the wireless device analyzes the information by at least providing the information to a machine learning engine that has been trained at least in part using prior information collected from the wireless device related to being submerged in water and / or participating in water activities, and the machine learning engine indicates whether the wireless device is submerged in water. In some embodiments, the machine learning engine further indicates whether the user of the wireless device is engaged in an activity comprising at least one of: a swimming activity, a snorkeling activity, a free diving activity, or a scuba diving activity. In some embodiments, the threshold depth, the depth timer, and / or the hysteresis timer are assigned respective values ​​based on the activity. In some embodiments, the wireless device comprises a waterproof or water resistant wearable wireless device.

[0082] Exemplary Computing Devices

[0083] Figure 7 1 illustrates a detailed view of a representative computing device 700 that can be used to implement the various methods described herein according to some embodiments. In particular, the detailed view illustrates various components that can be included in the wireless device 102. Figure 7As shown, the computing device 700 may include a processor 702 representing a microprocessor or a controller for controlling the overall operation of the computing device 700. The computing device 700 may also include a user input device 708 that allows a user of the computing device 700 to interact with the computing device 700. For example, the user input device 708 can take a variety of forms, such as buttons, keypads, dials, touch screens, audio input interfaces, visual / image capture input interfaces, inputs in the form of sensor data, etc. Further, the computing device 700 can include a display 710 that can be controlled by the processor 702 to display information to the user. The data bus 716 can facilitate data transmission between at least the storage device 740, the processor 702, and the controller 713. The controller 713 can be used to interact with and control different equipment through the equipment control bus 714. The computing device 700 may also include a network / bus interface 711 that is communicatively coupled to the data link 712. In the case of a wireless connection, the network / bus interface 711 may include a wireless transceiver.

[0084] The computing device 700 also includes a storage device 740, which may include a single disk or multiple disks (e.g., a hard drive), and includes a storage management module that manages one or more partitions within the storage device 740. In some embodiments, the storage device 740 may include flash memory, semiconductor (solid-state) memory, etc. The computing device 700 may also include a random access memory (RAM) 720 and a read-only memory (ROM) 722. The ROM 722 may store programs, utilities, or processes to be executed in a non-volatile manner. The RAM 720 may provide volatile data storage and store instructions related to the operation of the computing device 700. The computing device 700 may also include a secure element (SE) 724, such as an eUICC 108, a UICC 118, or another secure storage for cellular wireless system access by the wireless device 102.

[0085] Wireless Terminology

[0086] According to various embodiments described herein, the terms "wireless communication device", "wireless device", "mobile wireless device", "mobile station", and "user equipment (UE)" may be used interchangeably herein to describe one or more common consumer electronic devices that may be capable of performing the processes associated with various embodiments of the present disclosure. According to various specific implementations, any of these consumer electronic devices may relate to: a cellular phone or smart phone, a tablet computer, a laptop computer, a notebook computer, a personal computer, a netbook computer, a media player device, an e-book device, Devices, wearable computing devices, and any other type of electronic computing device with wireless communication capabilities, which wireless communication capabilities may include communication via one or more wireless communication protocols, which wireless communication protocols, such as protocols used to communicate on the following networks: wireless wide area network (WWAN), wireless metropolitan area network (WMAN), wireless local area network (WLAN), wireless personal area network (WPAN), near field communication (NFC), cellular wireless networks, fourth generation (4G) long term evolution (LTE), advanced LTE (LTE-A), and / or 5G or other currently or future developed advanced cellular wireless networks.

[0087] In some embodiments, the wireless communication device may also operate as part of a wireless communication system, which may include a group of client devices, which may also be referred to as stations, client wireless devices, or client wireless communication devices, interconnected to an access point (AP) (e.g., as part of a WLAN), and / or interconnected with each other (e.g., as part of a WPAN and / or "ad hoc" wireless network). In some embodiments, the client device may be any wireless communication device capable of communicating via WLAN technology (e.g., according to a wireless local area network communication protocol). In some embodiments, the WLAN technology may include a Wi-Fi (or more generally, a WLAN) wireless communication subsystem or radio component, which may implement the Institute of Electrical and Electronics Engineers (IEEE) 802.11 technology, such as one or more of the following: IEEE 802.11a; IEEE 802.11b; IEEE 802.11g; IEEE 802.11-2007; IEEE 802.11n; IEEE 802.11-2012; IEEE 802.11ac; or other currently or future developed IEEE 802.11 technology.

[0088] In addition, it should be understood that the UE described herein may be configured as a multi-mode wireless communication device that is also capable of communicating via different third generation (3G) and / or second generation (2G) RATs. In these scenarios, the multi-mode UE may be configured to prefer attaching to an LTE network that provides a faster data rate throughput over other 3G legacy networks that provide a lower data rate throughput. For example, in some specific implementations, the multi-mode UE may be configured to fall back to a 3G legacy network, such as an evolved high speed packet access (HSPA+) network, or a code division multiple access (CDMA) 2000 evolution-data only (EV-DO) network when LTE and LTE-A networks are otherwise unavailable.

[0089] The various aspects, embodiments, specific implementations or features of the described embodiments may be used individually or in any combination. Various aspects of the described embodiments may be implemented by software, hardware, or a combination of hardware and software. The described embodiments may also be implemented as computer-readable code on a non-transient computer-readable medium. A non-transient computer-readable medium is any data storage device that can store data, which can then be read by a computer system. Examples of non-transient computer-readable media include read-only memory, random access memory, CD-ROM, HDD, DVD, magnetic tape, and optical data storage devices. Non-transient computer-readable media may also be distributed on network-coupled computer systems so that the computer-readable code is stored and executed in a distributed manner.

[0090] In connection with this disclosure, it is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0091] For the purpose of explanation, the foregoing description uses specific nomenclature to provide a thorough understanding of the described embodiments. However, it will be apparent to those skilled in the art that specific details are not required in order to practice the described embodiments. Therefore, the foregoing description of specific embodiments is presented for the purpose of illustration and description. The foregoing description is not intended to be exhaustive or to limit the described embodiments to the precise form disclosed. It will be apparent to those of ordinary skill in the art that, in view of the above teachings, many modifications and variations are possible.

Claims

1. A method for managing a cellular connection status of a wireless device in relation to a water activity performed using the wireless device, the method comprising, at the wireless device: determining that the wireless device is submerged in water; In response to determining that the wireless device satisfies a threshold depth: A depth timer is started wherein the wireless device: terminating the depth timer whenever the wireless device no longer meets the threshold depth, and restarting the depth timer whenever the wireless device meets the threshold depth after the depth timer is terminated; as well as In response to identifying that the depth timer has expired: A baseband component of the wireless device is disabled to prevent the baseband component from attempting to establish a cellular connection.

2. The method of claim 1, further comprising, after deactivating the baseband component: determining that the wireless device is no longer submerged in water; starting a hysteresis timer, wherein each time the wireless device is re-submerged underwater, the wireless device restarts the hysteresis timer; as well as In response to identifying that the hysteresis timer has expired: The baseband component of the wireless device is enabled to enable the baseband component to establish the cellular connection.

3. The method of claim 2, wherein determining that the wireless device is submerged underwater comprises analyzing information comprising at least one of: Sports information, Sound information, Prescribing Information, Light information, Humidity information, Temperature information, or Location information.

4. The method according to claim 3, wherein: analyzing the information includes providing the information to a machine learning engine that has been trained at least in part using prior information collected from the wireless device related to being submerged in water and / or engaging in water activities, and The machine learning engine indicates whether the wireless device is submerged in water.

5. The method of claim 4, wherein the machine learning engine further indicates whether the user of the wireless device is engaged in an activity comprising at least one of: Swimming activities, Snorkeling activities, Free diving activities, or Scuba diving activities. 6 . The method of claim 5 , wherein the threshold depth, the depth timer and / or the hysteresis timer are assigned respective values ​​based on the activity.

7. The method of claim 1, wherein the wireless device comprises a wearable wireless device that is waterproof or water resistant.

8. A non-transitory computer-readable storage medium configured to store instructions that, when executed by a processor included in a wireless device, cause the wireless device to manage a cellular connection state of the wireless device related to a water activity performed using the wireless device by performing the following steps, the steps comprising: determining that the wireless device is submerged in water; In response to determining that the wireless device satisfies a threshold depth: A depth timer is started wherein the wireless device: terminating the depth timer whenever the wireless device no longer meets the threshold depth, and restarting the depth timer whenever the wireless device meets the threshold depth after the depth timer is terminated; as well as In response to identifying that the depth timer has expired: A baseband component of the wireless device is disabled to prevent the baseband component from attempting to establish a cellular connection.

9. The non-transitory computer readable storage medium of claim 8, wherein the steps further comprise, after deactivating the baseband component: determining that the wireless device is no longer submerged in water; starting a hysteresis timer, wherein each time the wireless device is re-submerged underwater, the wireless device restarts the hysteresis timer; as well as In response to identifying that the hysteresis timer has expired: The baseband component of the wireless device is enabled to enable the baseband component to establish the cellular connection.

10. The non-transitory computer-readable storage medium of claim 9, wherein determining that the wireless device is submerged underwater comprises analyzing information comprising at least one of: Sports information, Sound information, Prescribing Information, Light information, Humidity information, Temperature information, or Location information.

11. The non-transitory computer readable storage medium of claim 10, wherein: analyzing the information includes providing the information to a machine learning engine that has been trained at least in part using prior information collected from the wireless device related to being submerged in water and / or engaging in water activities, and The machine learning engine indicates whether the wireless device is submerged in water.

12. The non-transitory computer-readable storage medium of claim 11, wherein the machine learning engine further indicates whether a user of the wireless device is engaged in an activity comprising at least one of: Swimming activities, Snorkeling activities, Free diving activities, or Scuba diving activities.

13. The non-transitory computer-readable storage medium of claim 12, wherein the threshold depth, the depth timer, and / or the hysteresis timer are assigned respective values ​​based on the activity.

14. The non-transitory computer-readable storage medium of claim 8, wherein the wireless device comprises a wearable wireless device that is waterproof or water resistant.

15. A wireless device configured to manage a cellular connection status of the wireless device in relation to a water activity performed using the wireless device, the wireless device comprising a processor configured to cause the wireless device to perform the following steps, the steps comprising: determining that the wireless device is submerged in water; In response to determining that the wireless device satisfies a threshold depth: A depth timer is started wherein the wireless device: terminating the depth timer whenever the wireless device no longer meets the threshold depth, and restarting the depth timer whenever the wireless device meets the threshold depth after the depth timer is terminated; as well as In response to identifying that the depth timer has expired: A baseband component of the wireless device is disabled to prevent the baseband component from attempting to establish a cellular connection.

16. The wireless device of claim 15, wherein the steps further comprise, after deactivating the baseband component: determining that the wireless device is no longer submerged in water; starting a hysteresis timer, wherein each time the wireless device is re-submerged underwater, the wireless device restarts the hysteresis timer; as well as In response to identifying that the hysteresis timer has expired: The baseband component of the wireless device is enabled to enable the baseband component to establish the cellular connection.

17. The wireless device of claim 16, wherein determining that the wireless device is submerged underwater comprises analyzing information comprising at least one of: Sports information, Sound information, Prescribing Information, Light information, Humidity information, Temperature information, or Location information.

18. The wireless device of claim 17, wherein: analyzing the information includes providing the information to a machine learning engine that has been trained at least in part using prior information collected from the wireless device related to being submerged in water and / or engaging in water activities, and The machine learning engine indicates whether the wireless device is submerged in water.

19. The wireless device of claim 18, wherein the machine learning engine further indicates whether a user of the wireless device is engaged in an activity comprising at least one of: Swimming activities, Snorkeling activities, Free diving activities, or Scuba diving activities.

20. The wireless device of claim 19, wherein the threshold depth, the depth timer, and / or the hysteresis timer are assigned respective values ​​based on the activity.

Images