Method and system for enabling call connectivity in extended-discontinuous reception (EDRX) cycle for wearable device

Abstract

A method performed by a wearable device comprising: configuring a Configured Grant- Small Data Transmission (CG-SDT) timer and an eDRX timer; detecting an expiry of the CG-SDT timer; based on detection of the expiry of the CG-SDT timer, changing a connection mode of the wearable device to an idle mode; sending, to a master device, a notification query request; receiving a notification query response from the master device; and performing one or more changes in the connection mode based on the notification query response.

Description

METHOD AND SYSTEM FOR ENABLING CALL CONNECTIVITY IN EXTENDED-DISCONTINUOUS RECEPTION (EDRX) CYCLE FOR WEARABLE DEVICE

[0001] The disclosure relates generally to the field of electronic devices. In particular the disclosure relates to a reduction of power consumption in wearable device(s). More particularly, the disclosure relates to a method and a system for enabling a call connectivity in an extended-Discontinuous Reception (eDRX) cycle for a wearable device.

[0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the disclosure, and not as admissions of the prior art.

[0003] A wearable device is an electronic device that is designed to be used while being worn by a user of such electronic device. Wearable devices may include but not limited to smartwatches and sunglasses. Some of the wearable devices such as a smartwatch may work in conjunction with a master device such as a smartphone through a connectivity mechanism such as a Wi-Fi connectivity or a Bluetooth connectivity. Also, these wearable devices may work in a standalone mode when the wearable device is away from the master device and the wearable device is not connected to the master device. In the standalone mode the wearable devices work independently of the master device. Also, these wearable devices may be cellular wearable devices, wherein a cellular wearable device is a wearable device that supports cellular operation(s).

[0004] Power consumption in the cellular wearable devices (may also referred hereinafter "wearable devices") is a huge problem. In the wearable devices a reduction in a battery level due to cellular voice calls or cellular video calls is more as compared to a reduction in a battery level at the master device due to cellular voice calls or cellular video calls. Further, power consumption in a cellular wearable device becomes major issue when the cellular wearable device operates in the standalone mode and the cellular wearable device is untethered from the master device. In such events more power consumption and low battery life may be because of at least one of a screen on-time of the wearable device, an application usage at the wearable device, a cellular paging at the wearable device, a battery capacity of the wearable device, and a wireless connection e.g., a Wi-Fi connection or a Bluetooth connection. The cellular paging is a mechanism that allows a mobile network / a cellular network to locate and notify a mobile station (MS) of an incoming call or an incoming message. The cellular paging may be one of the highest contributing factors in power consumption of the wearable device. The cause behind the cellular paging being the highest contributor of the power consumption is that in the standalone mode the cellular paging is performed at the wearable device. The cellular paging consumes significantly more power as compared to wireless connections such as a Wi-Fi connection or a Bluetooth connection or the like.

[0005] Moreover, with the advent of 5thgeneration (5G) technology in the wearable devices the power consumption in the wearable devices has further increased. The potential reason for higher battery drainage in the wearable device due to 5G may be because of faster data speed offered in the 5G as compared to long term evolution (LTE). The faster data speed results in higher utilisation of the wearable device's modem and related components, leading to a more usage of power to maintain the faster data speed offered by the 5G. Also, the 5G network operates at higher frequencies resulting in an increased power consumption as high frequencies require more energy to transmit and receive data. Moreover, currently the network infrastructure and the wearable devices are not optimized. Furthermore, currently hardware components and software components of the wearable devices fail to efficiently support the cellular networks such as the 5G network and optimize its battery level in an efficient manner. Moreover, when the wearable devices are in an area with a coverage of a lower generation cellular network and an upper generation cellular network (say 4G network and 5G network, respectively), the wearable devices may switch between the two-networks leading to more power consumption during the period of transitions between the networks.

[0006] Currently, for reducing the power consumption, a wearable device enters into a low power mode e.g., a power saving mode. In some scenarios this low power mode may be activated when the wearable device is operating in the standalone mode. The low power mode (say the power saving mode) turns off various functionalities say for example a wi-fi connectivity, a mobile data transmission, and cellular operation(s) in the wearable device to save a battery power, resulting the wearable device to go into a "Discontinuous Reception (DRX)" state. More specifically, the power saving mode in the wearable device may disable all features of the wearable device except an emergency call feature for emergency calling using the cellular network. Further, in the power saving mode the wearable device may not receive any cellular or data communication such as an incoming call, a message, and a notification and thus the user may miss the cellular or data communication when the wearable device is in the power saving mode. Therefore, there cannot be any call connectivity in the wearable device while being in the power saving mode. However, in the power saving mode the wearable device may receive one or more notifications from one or more applications that do not require the wearable device to be in connection with the network. Also, in an implementation the wearable device in the power saving mode may receive incoming call, message and notification when the wearable device is connected to the master device via the Bluetooth connectivity.

[0007] Also, in the existing solution the user fails to receive any notification of the missed calls until the user manually switches off the low power mode and / or checks the master device which may not be possible in the cases when the user is away from the master device. Further, when the user is operating the wearable device as the standalone device and the wearable device enters the power saving mode, a user experience of a caller may also get hampered as a call initiated by the caller at the wearable device will be unanswered.

[0008] Moreover, the wearable device in the low power mode or the power saving mode may use an Extended Discontinuous Reception (eDRX) sleep cycle. The eDRX is a feature of a cellular network that is designed to reduce a consumption of power on the Internet of Things (IoT) devices which include the wearable devices. The eDRX sleep cycle exponentially increases the battery life and decreases the power consumption of the wearable devices. The eDRX allows the wearable devices to enter in a deep sleep mode for extended period, during such extended period the wearable devices suspend its connection with a network and switches off its receiver resulting in not receiving any call or notification temporarily from the network, hence reducing the power consumption in the wearable devices. Further, if the eDRX time is greater than a call setup time (i.e., a time from a moment a user of a cellular network initiates a call until the user receives notification about a called party being alerted) in the wearable devices, the incoming calls may be missed by the wearable devices, hence lacking the call connectivity in the wearable device during the eDRX sleep cycle.

[0009] Thus, there exists an imperative need in the art to provide a technical solution for the above-mentioned and such other technical limitations of the existing solutions. Hence, there is a need in the art of a method and a system for enabling a call connectivity in an extended-Discontinuous Reception (eDRX) cycle for a wearable device.

[0010] This section is provided to introduce certain aspects of the disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.

[0011] An aspect of the disclosure may relate to a method for enabling a call connectivity in an extended-Discontinuous Reception (eDRX) cycle for a wearable device. The method comprises configuring by the wearable device a Configured Grant- Small Data Transmission (CG-SDT) timer and an eDRX timer. Further, the method comprises detecting an expiry of the CG-SDT timer at the wearable device, wherein a connection mode of the wearable device is a deep sleep mode. Further, the method comprises based on detection of the expiry of the CG-SDT timer, changing the connection mode of the wearable device to an idle mode. Further, the method comprises sending, by the wearable device to a master device, a notification query request via a Small Data transmission (SDT) (or small data transfer) protocol during the idle mode. Furthermore, the method comprises receiving a notification query response at the wearable device from the master device. Finally, the method comprises performing one or more changes in the connection mode at the wearable device based on the notification query response.

[0012] In an exemplary aspect of the disclosure, the notification query response is one of a positive response and a negative response, and wherein the performing the one or more changes in the connection mode further comprises one of: 1) changing the connection mode of the wearable device to a connected mode in an event of receipt of the positive response, and 2) changing the connection mode of the wearable device to the deep sleep mode from the idle mode in an event of the receipt of the negative response.

[0013] In an exemplary aspect of the disclosure, the configuring the CG-SDT timer and the eDRX timer for the wearable device comprises: 1) sending, by the wearable device to a network, an assistance information; 2) receiving, by the wearable device from the network, the CG-SDT timer and the eDRX timer; and 3) syncing, by wearable device the CG-SDT timer and the eDRX timer with the master device.

[0014] In an exemplary aspect of the disclosure, the method further comprises starting, by the wearable device, the CG-SDT timer based on the received CG-SDT timer from the network.

[0015] In an exemplary aspect of the disclosure, the CG-SDT timer for the wearable device is identified by a machine learning model, wherein the machine learning model is trained based on a battery usage history and a current battery level of the wearable device.

[0016] In an exemplary aspect of the disclosure, the method comprises: 1) receiving a cellular call paging notification from a caller device at the master device; 2) detecting that the eDRX timer and the CG-SDT timer is running at the wearable device; and 3) performing at least one of: i) notifying, by the master device to the caller device, a time duration after which the wearable device will switch to the idle mode, and ii) initiating a call hold procedure by the master device via the network until the expiry of the CG-SDT timer.

[0017] In an exemplary aspect of the disclosure, the method comprises: 1) receiving a data call paging notification from a caller device at the master device; 2) detecting that the eDRX timer and the CG-SDT timer is running at the wearable device; and 3) sending a notification from the master device to the wearable device to activate an Internet data connection on the wearable device.

[0018] In an exemplary aspect of the disclosure, the method comprises disabling a subscriber identity module (SIM) at the wearable device in an event of at least one of: 1) an identification of a successful wireless connection between the wearable device and the master device, and 2) an identification of a distance between the wearable device and the master device being within a proximity range.

[0019] In an exemplary aspect of the disclosure, the notification query response comprises a call notification.

[0020] In an exemplary aspect of the disclosure, post the changing of the connection mode of the wearable device to the connected mode, the method further comprises transferring a call associated with the call notification from the master device to the wearable device.

[0021] An aspect of the disclosure may relate to a system for enabling a call connectivity in an extended-Discontinuous Reception (eDRX) cycle for a wearable device. The system comprises a processing unit; and a memory unit connected to the processing unit. The processing unit is configured to: 1) configure, by the wearable device, a Configured Grant- Small Data Transmission (CG-SDT) timer and an eDRX timer; 2) detect an expiry of the CG-SDT timer at the wearable device, wherein a connection mode of the wearable device is a deep sleep mode; 3) based on detection of the expiry of the CG-SDT timer, change the connection mode of the wearable device to an idle mode; 4) send, by the wearable device to a master device, a notification query request via a Small Data transmission (SDT) protocol during the idle mode; 5) receive a notification query response at the wearable device from the master device; and 6) perform one or more changes in the connection mode at the wearable device based on the notification query response.

[0022] Another aspect of the disclosure may relate to a non-transitory computer readable storage medium storing instructions for enabling a call connectivity in an eDRX cycle for a wearable device, the instructions include executable code which, when executed by one or more units of a system, causes a processing unit of the system to configure, by the wearable device, a Configured Grant- Small Data Transmission (CG-SDT) timer and an eDRX time. Further, the executable code, when executed, causes the processing unit to detect an expiry of the CG-SDT timer at the wearable device, wherein a connection mode of the wearable device is a deep sleep mode. Further, the executable code, when executed, causes the processing unit to change the connection mode of the wearable device to an idle mode, based on detection of the expiry of the CG-SDT timer. Further, the executable code, when executed, causes the processing unit to send, by the wearable device to a master device, a notification query request via a Small Data transmission (SDT) protocol during the idle mode. Further, the executable code, when executed, causes the processing unit to receive a notification query response at the wearable device from the master device. Further, the executable code, when executed, causes the processing unit to perform one or more changes in the connection mode at the wearable device based on the notification query response.

[0023] Some of the objects of the disclosure, which at least one implementation disclosed herein satisfies are listed herein below.

[0024] It is an object of the disclosure to provide a method and a system for enabling a call connectivity in an extended-Discontinuous Reception (eDRX) cycle for a wearable device.

[0025] It is an object of the disclosure to provide a solution for establishing at the wearable device, a cellular eDRX sleep cycle and a Configured Grant- Small Data Transmission (CG-SDT) timer.

[0026] It is another object of the disclosure to provide a solution for syncing the eDRX cycle and the CG-SDT timer of the wearable device with the master device.

[0027] It is another object of the disclosure to provide a solution for achieving a call continuity and a call connectivity in the wearable device in an efficient and effective manner.

[0028] It is yet another object of the disclosure to provide a solution for configuring an eDRX sleep cycle on the wearable device to reduce a power consumption in the wearable device.

[0029] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary implementations of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0030] FIG. 1illustrates an exemplary block diagram of a system for enabling a call connectivity in an extended-Discontinuous Reception (eDRX) cycle for a wearable device, in accordance with the exemplary implementation of the disclosure.

[0031] FIG. 2illustrates an exemplary method flow diagram of a method for enabling a call connectivity in an extended-Discontinuous Reception (eDRX) cycle for a wearable device, in accordance with the exemplary implementation of the disclosure.

[0032] FIG. 3illustrates an exemplary graph of a power consumption with respect to a time in the wearable device operating in an eDRX sleep cycle, in accordance with the exemplary implementation of the disclosure.

[0033] FIG. 4 illustrates an exemplary signalling flow diagram depicting a process for configuring a CG-SDT timer and an eDRX timer for a wearable device, in accordance with the exemplary implementation of the disclosure.

[0034] FIG. 5 illustrates a signalling flow diagram depicting an exemplary process for enabling a call connectivity in an eDRX cycle for a wearable device in accordance with the exemplary implementation of the disclosure.

[0035] FIG. 6illustrate a signalling flow diagram depicting an exemplary process for transferring a call to the wearable device via a conference call with a master device, in accordance with the exemplary implementation of the disclosure.

[0036] FIG. 7 illustrates an exemplary block diagram indicating a communication between a wearable device and a master device, in accordance with the exemplary implementation of the disclosure.

[0037] FIG. 8illustrates an exemplary signaling flow diagram for performing a small data transmission (SDT) by way of Configured Grant- Small Data Transmission (CG-SDT) for enabling a call connectivity in an eDRX cycle for a wearable device in accordance with the exemplary implementation of the disclosure.

[0038] The foregoing shall be more apparent from the following more detailed description of the disclosure.

[0039] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the disclosure. It will be apparent, however, that embodiments of the disclosure may be practiced without these specific details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.

[0040] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0041] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.

[0042] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.

[0043] The word "exemplary" and / or "demonstrative" is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as "exemplary" and / or "demonstrative" is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms "includes," "has," "contains," and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive―in a manner similar to the term "comprising" as an open transition word―without precluding any additional or other elements.

[0044] As used herein, "a user equipment", "a user device", "a smart-user-device", "a smart-device", "an electronic device", "a mobile device", "a master device", "a handheld device", "a wireless communication device", "a mobile communication device", "a communication device" may be any electrical, electronic and / or computing device or equipment, capable of implementing the features of the disclosure. The user equipment / device may include, but is not limited to, a mobile phone (or referred herein as a phone), smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the disclosure.

[0045] As used herein, "storage unit" or "memory unit" refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory ("ROM"), random access memory ("RAM"), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.

[0046] As used herein "interface" or "user interface refers to a shared boundary across which two or more separate components of a system exchange information or data. The interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.

[0047] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.

[0048] As used herein, a "processing unit" or "processor" or "operating processor" may include one or a plurality of processors. At this time, one or a plurality of processors may be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an AI-dedicated processor such as a neural processing unit (NPU).

[0049] At least one of the plurality of modules / units may be implemented through an AI model. A function associated with AI may be performed through the non-volatile memory, the volatile memory, and the processor.

[0050] The one or a plurality of processors control the processing of the input data in accordance with a predefined operating rule or artificial intelligence (AI) model stored in the non-volatile memory and the volatile memory. The predefined operating rule or artificial intelligence model is provided through training or learning.

[0051] Here, being provided through learning means that, by applying a learning algorithm to a plurality of learning data, a predefined operating rule or AI model of a desired characteristic is made. The learning may be performed in a device itself in which AI according to an embodiment is performed, and / or may be implemented through a separate server / system.

[0052] The AI model may consist of a plurality of neural network layers. Each layer has a plurality of weight values and performs a layer operation through calculation of a previous layer and an operation of a plurality of weights. Examples of neural networks include, but are not limited to, convolutional neural network (CNN), deep neural network (DNN), recurrent neural network (RNN), restricted Boltzmann Machine (RBM), deep belief network (DBN), bidirectional recurrent deep neural network (BRDNN), generative adversarial networks (GAN), and deep Q-networks.

[0053] The learning algorithm is a method for training a predetermined target device (for example, a robot) using a plurality of learning data to cause, allow, or control the target device to make a determination or prediction. Examples of learning algorithms include, but are not limited to, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning.

[0054] As discussed in the background section, the current known solutions have several shortcomings. Currently, power consumption is a major problem in wearable devices and the problem becomes even more concerning when a wearable device is acting in a standalone mode i.e., when the wearable device (or an electronic device) is out of a connectivity range such as a Wi-Fi range or a Bluetooth range of a master device (or an external electronic device). Further, a high-power consumption or a low battery life in the wearable device may be because battery capacities of the wearable device are significantly smaller as compared to that of a master device. Also, cellular paging in the wearable devices is one of the highest contributing factors in the power consumption. Furthermore, with the advent of 5G technology in the wearable devices the power consumption has increased even more. The reason for more power consumption in the wearable devices due to 5G is because the 5G offers faster data speed as compared to LTE. The faster data speed results in higher utilization of the wearable device's modem and related components, leading to a more usage of power to maintain the faster data speed offered by the 5G. Also, the 5G network operates at higher frequencies resulting in an increased power consumption as high frequencies require more energy to transmit and receive data.

[0055] As per, the current known solutions for reducing the power consumption, a wearable device enters into a low power mode e.g., a power saving mode. In some scenarios, this low power mode may be activated when the wearable device is operating in the standalone mode. The low power mode (say the power saving mode) turns off various functionalities say for example a wi-fi connectivity, a mobile data transmission, and cellular operation(s) in the wearable device to save a battery power, resulting the wearable device to go into a "Discontinuous Reception (DRX)" state. In the "Discontinuous Reception (DRX) state, the wearable device may not receive any cellular or data communication such as an incoming call, a message and a notification, and the user of the wearable device may miss the cellular or data communication. Therefore, there cannot be any call connectivity or call continuity in the wearable device while being in the low power mode or the power saving mode, thereby hampering the user experience of both a caller and a callee. Further, in the power saving mode the wearable device may receive one or more notifications from one or more applications that do not require the wearable device to be in connection with the network. Also, in an implementation the wearable device in the power saving mode may receive incoming call, message and notification when the wearable device is connected to the master device via the Bluetooth connectivity.

[0056] The disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by setting up the extended Discontinuous Reception (eDRX) sleep cycle in the wearable device. During the eDRX sleep cycle the wearable device alternatively enters into two modes namely a deep sleep mode and an idle mode. In the deep sleep mode, the wearable device suspends its connection with a network and the master device and switches off its receiver resulting in not receiving any call or notification from the network, hence reducing the power consumption. Also, in the idle mode the wearable device is in a suspended connection with the network, but it may communicate with the master device.

[0057] According to the disclosure when the wearable device is in the idle mode, the wearable device releases SDT (Small Data Transmission) to communicate with the master device. The master device uses the SDT to notify the wearable device about missed call(s) and missed notification(s) that were received on the master device when the wearable device was in the deep sleep mode. Also, the master device uses the SDT to command the wearable device to change the operational mode i.e., may be from eDRX sleep mode to connected mode / active mode. In the connected mode or the active mode, the wearable device is in connection with the network and the master device and hence achieves call connectivity and call continuity.

[0058] Therefore, the disclosure provides a technical solution for achieving the call continuity and the call connectivity in the wearable device in an efficient and effective manner. The present solution enables the call connectivity and the call continuity in an extended-Discontinuous Reception (eDRX) cycle for the wearable device. More specifically, the disclosure provides a solution for establishing at the wearable device, a cellular eDRX sleep cycle and a Configured Grant- Small Data Transmission (CG-SDT) timer. The solution as disclosed in the disclosure is technically advanced over the existing solutions as it provides a synchronisation of the eDRX cycle and the CG-SDT timer of the wearable device with the master device. The configuration of the eDRX sleep cycle on the wearable device reduces a power consumption in the wearable device in an efficient and effective manner.

[0059] Hereinafter, exemplary embodiments of the disclosure will be described with reference to the accompanying drawings.

[0060] Referring to　FIG. 1,　an exemplary block diagram of a system 100 for enabling a call connectivity in an extended-Discontinuous Reception (eDRX) cycle for a wearable device in accordance with the exemplary implementation of the disclosure is shown. The system 100 comprises processing unit 102 and storage unit 104.　For example, the processing unit 102 may be referred as at least one processor (including processing circuitry). For example, the storage unit 104 may be referred as at least one storage medium or memory (including at least one storage medium). Also, all of the components / units of the system 100 are assumed to be connected to each other unless otherwise indicated below. Also, in Fig. 1 only a few units are shown, however, the system 100 may comprise multiple such units, or the system 100 may comprise any such numbers of said units, as required to implement the features of the disclosure. Further, in an implementation, the system 100 may reside in the wearable device to implement the features of the disclosure. The processing unit 102 may include various processing circuitry and / or multiple processors. For example, as used herein, including the claims, the term "processor" may include various processing circuitry, including at least one processor, wherein one or more of at least one processor, individually and / or collectively in a distributed manner, may be configured to perform various functions described herein. As used herein, when "a processor", "at least one processor", and "one or more processors" are described as being configured to perform numerous functions, these terms cover situations, for example and without limitation, in which one processor performs some of recited functions and another processor(s) performs other of recited functions, and also situations in which a single processor may perform all recited functions. Additionally, the at least one processor may include a combination of processors performing various of the recited / disclosed functions, e.g., in a distributed manner. At least one processor may execute program instructions to achieve or perform various functions.

[0061] Particularly, for enabling the call connectivity in the eDRX cycle for the wearable device, the processing unit 102 is configured to　configure, by the wearable device, a Configured Grant- Small Data Transmission (CG-SDT) timer and an eDRX timer. Further, a CG-SDT may also be referred to as a preconfigured radio resource. The CG-SDT is a way of performing Small Data Transmission (SDT) wherein the wearable device may transmit a small amount of data while remaining in an inactive state (i.e., an idle state). Further, the SDT may be performed by way of the CG-SDT when radio resource(s) are pre-allocated to the wearable device based on an estimation of the wearable device's traffic requirement. Also, the wearable device in order to configure the CG-SDT timer and the eDRX timer sends an assistance information to a network. In response to the same the wearable device receives the CG-SDT timer and the eDRX timer from the network. Thereafter, the wearable device syncs the CG-SDT timer and the eDRX timer with the master device. Moreover, the detailed description for configuring the CG-SDT timer and the eDRX timer for the wearable device is provided below in the description of Fig. 4.

[0062] Further, the processing unit 102 is configured to　detect an expiry of the CG-SDT timer at the wearable device, wherein a connection mode of the wearable device is a deep sleep mode. The wearable device during an eDRX sleep cycle may be in one of the deep sleep mode, and an idle mode. When the wearable device enters the deep sleep mode, the wearable device does not transmit or receive any communication data such as a call or a notification. Also, in the deep sleep mode the receiver of the wearable device switches off and the connection between the wearable device and the network may be suspended. The receiver of the wearable device may be referred as communication circuitry for communicating with the network device and / or the master device. For example, the wearable device may comprise the communication circuitry further the compontnents in Fig. 1. Further, the CG-SDT timer also starts when the wearable device enters into the deep sleep mode. Further, the processing unit 102,　based on detection of the expiry of the CG-SDT timer, changes the connection mode of the wearable device to the idle mode from the deep sleep mode. In the idle mode, the wearable device may transmit the SDT to a master device to sync the CG-SDT timer and the eDRX timer with the master device and the master device may use the SDT to communicate with the wearable device. Further, the detailed description regarding the deep sleep mode, the idle mode and the release of SDT from the wearable device is provided in below in the description of Fig. 3.

[0063] The processing unit 102 is further configured to　send, by the wearable device to a master device, a notification query request via a Small Data transmission (SDT) protocol during the idle mode. Further, the processing unit is configured　to receive a notification query response at the wearable device from the master device. The detailed description regarding the sending notification query request and receiving the notification query response by the wearable device is provided below in the description of Fig. 5. The processing unit 102 is further configured to perform one or more changes in the connection mode at the wearable device based on the notification query response. The notification query response is one of a positive response and a negative response.　In an event of receipt of the positive response the processing unit 102 changes the connection mode of the wearable device to a connected mode from the eDRX sleep cycle, whereas in an event of receipt of the negative response the processing unit 102 changes the connection mode of the wearable device to the deep sleep mode from the idle mode.

[0064] Referring to FIG. 2, an exemplary method flow diagram of a method for enabling a call connectivity in an extended-Discontinuous Reception (eDRX) cycle for a wearable device is shown, in accordance with the exemplary implementation of the disclosure. In an implementation, the method 200 may be performed by the system 100 (or the wearable device). Also, the system 100 works in conjunction with the wearable device and a master device connected to the wearable device.

[0065] At step 204, the method 200 may comprise configuring by the wearable device a Configured Grant-Small Data Transmission (CG-SDT) timer and an eDRX timer. The process of configuring the CG-SDT timer and the eDRX timer for the wearable device may comprise sending, by the wearable device to a network, an assistance information. This process then leads to receiving, by the wearable device from the network, the CG-SDT timer and the eDRX timer. After receiving the CG-SDT timer and the eDRX timer, the process leads to syncing, by wearable device the CG-SDT timer and the eDRX timer with the master device. Also, the method 200 at step 204 encompasses starting, by the wearable device, the CG-SDT timer based on the received CG-SDT timer from the network. Furthermore, the CG-SDT timer for the wearable device is identified by a machine learning model, wherein the machine learning model is trained based on a battery usage history and a current battery level of the wearable device.

[0066] Also, the method 200 encompasses receiving a cellular call paging notification from a caller device at the master device. In this implementation the method leads to detecting that the eDRX timer and the CG-SDT timer are running at the wearable device. When at the wearable device the eDRX timer and the CG-SDT timer are running, the wearable device is in the deep sleep mode. Further in this implementation, the method after the process of detecting, performs at least one of: 1) notifying, by the master device to the caller device, a time duration after which the wearable device will switch to the idle mode; and 2) initiating a call hold procedure by the master device via the network until the expiry of the CG-SDT timer.

[0067] Also, the method 200 encompasses receiving a data call paging notification from a caller device at the master device. In this implementation the method leads to detecting that the eDRX timer and the CG-SDT timer are running at the wearable device. Further in this implementation, the method after the process of detecting encompasses sending a notification from the master device to the wearable device to activate an Internet data connection on the wearable device.

[0068] Moreover the method 200 encompasses disabling a subscriber identity module (SIM) at the wearable device in an event of at least one of: 1) an identification of a successful wireless connection between the wearable device and the master device, and 2) an identification of a distance between the wearable device and the master device being within a proximity range.

[0069] Next, at step 206, the method may comprise detecting an expiry of the CG-SDT timer at the wearable device, wherein a connection mode of the wearable device is a deep sleep mode.

[0070] Further, at step 208, based on detection of the expiry of the CG-SDT timer the method may comprise changing the connection mode of the wearable device to an idle mode.

[0071] Thereafter, at step 210, the method may comprise sending, by the wearable device to a master device, a notifications query request via a Small data transmission (SDT) protocol during the idle mode.

[0072] Next, at step 212, the method may comprise receiving a notification query response at the wearable device from the master device. The notification query response is one of a positive response and a negative response.

[0073] Further, at step 214, the method may comprise performing one or more changes in the connection mode at the wearable device based on the notification query response. The process of performing the one or more changes in the connection mode comprises one of: changing the connection mode of the wearable device to a connected mode from the eDRX sleep cycle in an event of receipt of the positive response; and changing the connection mode of the wearable device to the deep sleep mode from the idle mode in an event of the receipt of the negative response.

[0074] In an implementation the notification query response may comprise a call notification. Also, post the changing of the connection mode of the wearable device to the connected mode, the method 200 may further comprises transferring a call associated with the call notification from the master device to the wearable device.

[0075] Moreover, a detailed explanation of the steps that are performed in the method 200 is provided below in the description of the Fig. 3, Fig. 4, Fig. 5, Fig. 6, Fig. 7, and Fig. 8.

[0076] Referring to FIG. 3that illustrates an exemplary graph of a power consumption with respect to a time in the wearable device operating in an eDRX sleep cycle, in accordance with the exemplary implementation of the disclosure.

[0077] As depicted in the FIG. 3, the wearable device may be in the eDRX mode and the eDRX mode may be of 20 seconds. In a first second (i.e., for an initial 1 sec time duration), the wearable device may be in the idle mode during which the wearable device may release a Small Data Transmission (SDT) for syncing the eDRX timer and the CG-SDT timer of the wearable device with the master device. Further, for the next 9 seconds, the wearable device may go into the deep sleep mode. When the wearable device is in the deep sleep mode, the receiver of the wearable device is in an off state and hence the wearable device is not connected to a network or a network node. Therefore, the wearable device in the deep sleep mode fails to receive all cellular communications such as all calls, all messages, and notifications etc. Further, at the end of said 9 (nine) seconds (i.e., after 10thsecond) the wearable device may come into the idle mode for 1 (one) second (i.e., for 11thsecond) during which the master device may communicate with the wearable device using the SDT released by the wearable device in the idle mode. More specifically, using the SDT, the master device communicates to the wearable device that if any cellular communication (say any call, any message, and / or any notification etc.) is missed or not by the wearable device during the deep sleep mode (i.e., between the 2ndsecond to 10thsecond). Also, the wearable device during the idle mode does not go into a radio resource control (RRC) connected state. After the 11thsecond the wearable device may go back into the deep sleep mode for next 9 (nine) seconds (i.e., from 12thsecond till 20thsecond) if no call, no message and / or no notification is missed during the deep sleep mode enabled between the 2ndsecond to 10thsecond. If there is any call, any message, and / or any notification missed during the deep sleep mode enabled between the 2ndsecond to 10thsecond, then the wearable device may come into a connected state. In the connected state the wearable device is in connection with the master device. Therefore, in the connected state a call may be transferred from the master device to the wearable device to achieve the call connectivity and / or the call continuity. If there is no call, no message, or no notification missed by the wearable device during the deep sleep mode, the wearable device continues in the deep sleep mode i.e., a Discontinuous Reception (DRX) state, thereby reducing the power consumption, saving the battery life, and achieving the call continuity. Further, it is pertinent to note that the FIG. 3 is exemplary and not limiting the scope of the disclosure in any manner.

[0078] Referring to FIG. 4 that illustrates an exemplary signalling flow diagram depicting a process for configuring a CG-SDT timer and an eDRX timer for a wearable device, in accordance with the exemplary implementation of the disclosure. The process as depicted in the FIG. 4 starts when the wearable device is identified in a radio resource control (RRC) connected state with a network.

[0079] In FIG. 4, at step S1, the wearable device sends user equipment (UE) assistance information for eDRX cycle and CG-SDT configuration timers to the network. The UE Assistance information is a Radio Resource Control (RRC) message by which the wearable device may inform about a status of the wearable device to the network. Also, the UE assistance information messages may be sent to the network for indicating preferred parameter(s) for saving power in the wearable device. Further, extended Discontinuous Reception (eDRX) is a feature of cellular network that is designed to reduce consumption of power on Internet of Things (IoT) devices. The eDRX allows the wearable device to enter a deep sleep mode for extended period while still maintaining during an idle mode a connection of the wearable device with the master device. During the deep sleep mode, the wearable device suspends its connection with the network and switches off its receiver resulting in not receiving any call or message or notification etc. from the network, hence reducing the power consumption in the wearable device. Further, when the wearable device wakes up from the deep sleep mode and enters in a connected mode, the wearable device may quickly reconnect with the network and may receive any message or any notification (such as a notification of a call) that was missed when the device was in the deep sleep mode. Moreover, Small Data Transmission (SDT) is a procedure which allows the wearable device to send small amount of data while remaining in an inactive state (i.e., an idle state) without transitioning the wearable device to the connected state. Further, the SDT may be performed by way of preconfigured radio resources (such as Configured Grant- Small Data Transmission (CG-SDT)).

[0080] Further, as indicated in FIG. 4, at step S2, the network sends to the wearable device, the RRC release message along with CG-SDT Indication and eDRX Indication with respective timers and parameters configured. The network sends back in response the finalised CG-SDT and the eDRX timers back to the wearable device along with RRC release message, wherein the RRC release message is a signal that is sent to the wearable device to put the wearable device into the RRC idle state (i.e., eDRX sleep mode). Once, the wearable device receives the RRC release message along with the CG-SDT and the eDRX timers, the CG-SDT timer (i.e., timer for Inactive mode or Idle mode) starts at the wearable device.

[0081] Furthermore, as indicated in FIG. 4, at step S3, the wearable device sends to the network an Uplink Radio Resource Control (UL RRC) message and an Uplink Data. The uplink data may comprise information related to the eDRX, and the CG-SDT Timer parameters. Also, the UL RRC message may comprise of information related to a timer for the wearable device to go into the inactive state or the idle state (may also be referred herein as idle CG-SDT mode) and the information is sent to the network. The SDT is used, to send the UL RRC message and an Uplink Data to the network, while wearable device being in the idle mode for syncing the master device with the wearable device.

[0082] Once the network receives the UL RRC message along with the uplink Data, as indicated in the FIG.4 the network at step S4, sends the Uplink Radio Resource Control (UL RRC) message and the Uplink Data to the master device in downlink. The network sends the UL RRC message and the Uplink Data to the master device (or may be referred in the disclosure as a mobile device) to sync and update the master device with the wearable device about eDRX sleep cycle. The eDRX cycle may comprise eDRX cycle ON duration, a wake time of the wearable device, a deep sleep ON duration, a deep sleep OFF duration and a duration to release SDT in idle mode of the wearable device. Once the master device is synced with the wearable device, the master device will accurately know whether the eDRX mode is ON or the eDRX mode is OFF on the wearable device. Also, the master device will know when or whether the cellular communication such as a call may be received by the wearable device.

[0083] Further the FIG. 4 at step S5 depicts that the master device sends a data delivery acknowledgement to the network acknowledging the syncing of the eDRX Cycle and the CG-SDT timer of the wearable device with the master device.

[0084] Thereafter, at step S6 the FIG. 4 indicates that the network sends the RRC release message to the wearable device along with data delivery acknowledgement from the master device. Once the wearable device receives the data delivery acknowledgment, the wearable device goes into the deep sleep mode based on eDRX ON time duration.

[0085] Referring to FIG. 5 that illustrates a signalling flow diagram depicting an exemplary process for enabling a call connectivity in an eDRX cycle for a wearable device in accordance with the exemplary implementation of the disclosure.

[0086] As indicated at step 502 in the FIG. 5, CG-SDT timers running on the wearable device goes to a deep sleep mode after a DRX ON time duration.

[0087] Thereafter, as depicted in the FIG. 5, the process at step S1 encompasses tiggering a call to a callee having / a master device with number M1. The indication of the initiated call may be received by the network for triggering the call at number M1.

[0088] Once the signal is received by the network, process at step S2 as indicated in the FIG. 5 encompasses initiating a mobile terminal (MT) call paging at the callee device (i.e., the master device) with the number M1. Further, the wearable device of the callee may also be associated with the same number M1 as that of the master device of the callee.

[0089] Further, as depicted in FIG. 5 at step S3 at the network a ring is received from the master device of the callee for initiating call paging at the wearable device of the callee with the number M1.

[0090] Also, the eDRX sleep cycle is ON at the wearable device and the CG-SDT timer is running with the wearable device being in the deep sleep mode after the eDRX ON time. Further, at step S4 of the FIG. 5, the call paging at the number M1 is missed at the wearable device, as the eDRX sleep cycle is greater than call setup time. The call setup time may be the time from the moment when the caller initiates the call until the moment when the network confirms that the call is successfully connected. Since, the eDRX timer is greater than the call setup time, the network will page the call at the wearable device till the call setup time ends and then after the expiry of the call setup time the network may declare that the wearable device is unavailable and stops the call paging at the wearable device. Further, the call may continue ringing on the master device of the callee till the ringing time ends.

[0091] Further, FIG. 5 depicts that the process at step S5, encompasses notifying the caller, by the mobile device / master device, about the wake-up time of the wearable device as mobile device / master device may be in sync with the wearable device and may have the knowledge about the CG-SDT timer and the eDRX cycle of the wearable device.

[0092] Furthermore, after the CG-SDT timer ends, the wearable device may wake up from deep sleep mode and the wearable device may go into the idle mode (where it may be connected with the master device and is disconnected with the network) during which the wearable may release SDT for the master device for checking with the master device about any cellular communication such as any call and / or notification etc. missed by the wearable device during the deep sleep mode.

[0093] As indicated in the FIG. 5 at step S6, the process encompasses transmitting an Uplink Radio Resource Control (UL RRC) message and an Uplink Data to the network. Further, the uplink data may comprise a notification query request for querying any cellular communication such as any call and / or notification that is missed by the wearable device during the deep sleep mode.

[0094] After, the network receives the UL RRC message and the Uplink Data, as indicated in the Fig. 5 at step S7 the process encompasses, transmitting the UL RRC message and the Uplink Data to the master device from the network.

[0095] Further, at step S8, the FIG. 5 depicts that the process encompasses transmitting, by the master device, the notification query response at the network. The response may comprise information related to the cellular communication such as any call or notification that is missed by the wearable device during the deep sleep mode. Also, a wakeup trigger data for the wearable device, on downlink, is sent to the network by the master device at step S8.

[0096] Furthermore, the process at step S9 encompasses, transmitting, by the network, the response of the notification query request (i.e., the details received at the step S8 of the FIG. 5) to the wearable device.

[0097] Thereafter, at step S10 of the FIG. 5, in an event the information related to the cellular communication such as any call or notification that is missed by the wearable device during the deep sleep mode is received by the wearable device, the process encompasses, transmitting, by the wearable device, a RRC connection request to the network for reconnecting the wearable device with the network.

[0098] FIG 5, at step S11 depicts that the process encompasses, receiving by the wearable device the RRC connection accept response from the network and the wearable goes into the connected state (i.e., in connection with the network). After, the wearable device goes into the connected state seamless call connectivity and call continuity may be achieved on the wearable device even if the wearable may be in the eDRX sleep cycle mode thereby achieving call connectivity and call continuity in the power saving mode.

[0099] In an implementation, a cellular call may be transferred to the wearable device from the master device using any call transfer mechanism such as a conference call between three devices (i.e., the wearable device, the master device (i.e., the callee device), and the caller device). Once the conference call is established thereafter the method in this implementation encompasses removing the master device from the conference call and continuing the call received from the caller device on the wearable device only.

[0100] FIG. 6illustrate a signalling flow diagram depicting an exemplary process for transferring a call to the wearable device via a conference call with a master device in accordance with the exemplary implementation of the disclosure.

[0101] FIG. 6 at step S1 depicts that the process encompasses registering the master device at a Call Session Control Function (CSCF). Further, the CSCF may be a registration database.

[0102] Thereafter, at step S2, the process encompasses registering the Wearable device at the Call Session Control Function (CSCF).

[0103] Next, at step S3, the process encompasses registering the network at the Call Session Control Function (CSCF) for creating the conference with the master device and the wearable device.

[0104] After step S3, next atstep S4, the process encompasses transmitting, by the network, an invite message (SDP (session description protocol) Wearable Device) to the CSCF for the wearable device, to invite the wearable device for the conference call with the master device.

[0105] The process further at step S5 encompasses receiving, by the wearable device, the invite message (SDP Wearable Device) from the CSCF for the conference call.

[0106] Further, at step S6 the process encompasses, transmitting an ok message (200 OK / SDP), by the wearable device, in response to the conference call invite, to the CSCF. The CSCF, at step S7, further transmits the ok message (200 OK / SDP) to the network.

[0107] Once the ok message is received by the network from the CSCF, then the process further at step S8 encompasses transmitting, by the network, the invite message (SDP Master Device) to the CSCF for the master device, to invite the master device for the conference call with the wearable device.

[0108] The process further at step S9 encompasses receiving by the master device, the invite message (SDP Master Device) from the CSCF for the conference call. Further, the master device, at step S10, transmits the ok message (200 OK / SDP) in response to the conference call invite, to the CSCF. Furthermore, at step S11 the process encompasses, transmitting by the CSCF the ok message (200 OK / SDP) to the network. Thereafter the conference call starts.

[0109] Once the conference call starts, the process further at step S12 encompasses, transmitting, by the network, a BYE message (BYE Master Device or Remove Master Device) to the CSCF for removing the master device from the conference call. After step S12, next at step S13, the CSCF further transmits the BYE message to the master device.

[0110] Thereafter, at step S14 the process encompasses transmitting the ok message (200 OK), by the master device, to the CSCF. Finally, at step S15 of the FIG. 6, the CSCF transmits the ok message (200 OK) to the network, to indicate that the master device is removed from the conference call. Hence, the process as depicted in the FIG. 6 encompasses transferring the call to the wearable device and achieving the call continuity on the wearable device.

[0111] Referring to FIG. 7 that illustrates an exemplary block diagram indicating a communication between a wearable device and a master device, in accordance with the exemplary implementation of the disclosure. The wearable device 702 may comprise at least one first network operator module 702A, at least one first proximity detection module 702B, at least one first decision module 702C, at least one power saving module 702D, at least one first communication module 702E, at one wearable database sub-module 702F, at least one first modem processor 702G, and at least one first User Interface (UI) module 702H. Also, all the components / units of the wearable device 702 are assumed to be connected to each other unless otherwise indicated below. In an implementation the wearable device 702 also comprises the system 100, wherein in such implementation the wearable device 702 performs the technical functions as disclosed in the disclosure using the system 100 in conjunction with the one or more components of the wearable device 702. In another implementation the wearable device 702 itself (via its one or more components) performs the technical functions as disclosed in the disclosure.

[0112] Further, the master device 704 may comprise at least one second network operator module 704A, at least one second proximity detection module 704B, at least one second decision module 704C, at least one second communication module 704E, at least one phone database sub-module 704F, at least one second modem processor 704G, and at least one second User Interface (UI) module 704H. Also, all the components / units of the master device 704 (or the mobile device 704) are assumed to be connected to each other unless otherwise indicated below. Furthermore, the wearable device 702 and the master device 704 are assumed to be connected to each other.

[0113] The network operator modules, including the first network operator module 702A and the second network operator 704A facilitate one or more network functionalities in the wearable device 702 and the master device 704, respectively. For instance, the network operator modules may facilitate cellular communication such as a cellular call etc.

[0114] Further, the first proximity module 702B and the second proximity module 704B are proximity modules that are configured to detect a strength of connection between the wearable device 702 and the master device 704, wherein the first proximity module 702B may be configured in the wearable device 702 and the second proximity module 704B may be configured in the master device 704. Further, the proximity modules are configured to detect a presence of the wearable device 702 and the master device 704 within a near filed communication (NFC) range and / or the proximity modules are configured to determine if the wearable device 702 and the master device 704 are tethered to each other via a Wi-Fi connection. Furthermore, if the proximity modules detect: 1) the presence of the wearable device 702 and the master device 704 within the NFC range, and / or 2) the wearable device 702 and the master device 704 are tethered to each other via the Wi-Fi connection, then each of the proximity modules may notify a respective profiling module and a respective UI module (comprising the first UI module 702H configured in the wearable device 702 and the second UI module 704H configured in the master device 704), about disabling the eSIM in the wearable device 702. Furthermore, if the proximity modules do not detect: 1) the presence of the wearable device 702 and the master device 704 within the NFC range; and / or 2) the wearable device 702 and the master device 704 are tethered to each other, then the first proximity module 702B may notify the second communication module 702E and the power saving module 702D to trigger the call continuity in the wearable device during the power saving mode.

[0115] Moreover, the wearable device 702 and the master device 704 comprise decision modules, wherein the wearable device 702 comprises the first decision module 702C and the master device 704 comprises the second decision module 704C. Further, the decision modules are configured to make decisions and to take actions on the wearable device 702 and the master device 704 to achieve power consumption as well as the call continuity.

[0116] Also, the decision modules may predict the extended Discontinuous Reception (eDRX) cycle and the Configuration Grants-Small Data transmission (CG-SDT) timers for the wearable device 702. Further, to predict the eDRX cycle and the CG-SDT timers the decision modules may, in first phase, collect data comprising usage data, system context, and the battery log from the wearable device as input. The usage data includes system contexts, users' usage behavior, system events, etc. The battery log is a record of battery changes over time.

[0117] Further, the decision modules may process the raw data from the input data set to formulate features. For instance, the decision modules may randomly collect sample time points in each session from the battery log to simulate user's query. Finally, the decision module combines the session, the sampled time point, and the usage data to generate features of every single simulated query and build a vector in a multi-dimensional space.

[0118] Thereafter, the decision modules may use Artificial intelligence or Machine learning based models that may comprise but not limited to a neural network and / or a tree-based machine learning model to derive a correlation including both linear and non-linear correlations between the features and the battery life and generates the derived prediction model. Finally, the model extracts the features, and the derived model predicts the eDRX cycle and the CG-SDT timers.

[0119] Moreover, the decision modules may generate the decisions and the actions as one or more outputs based on one or more inputs. The one or more inputs may be provided by one or more modules such as the UI modules, the proximity modules, the communication modules, the power saving module 702D, and the network operator modules. Also, the inputs may include the battery state, the eDRX sleep cycle, the CG-SDT timer, the eSIM Mobile Directory Number (MDN number) and the network slicing requirements etc. The inputs may further include but are not limited to events on the master device 704, user preferences, user activity or inactivity and user pre-set configurations.

[0120] In an implementation, the first decision module 702C may provide based on an input, an output to disable the eSIM in the wearable device in an event the wearable device 702 is connected to the master device via connectivity mechanisms such as Bluetooth connectivity or Wi-Fi connectivity etc. By disabling the eSIM on the wearable device 702, significant amount of power consumption may be reduced at the wearable device.

[0121] In another implementation, the first decision module 702C may provide based on an input, an output to set the eDRX cycle on the wearable device 702 to save the power on the wearable device 702 and also to handle calls / messages (e.g., cellular calls / messages and / or Internet based calls / messages) on the wearable device 702 during the eDRX cycle for call continuity even in the power saving mode. Therefore, in such cases the user experience of both a caller and a callee may improve. The second decision module 704C may notify the caller when the callee may be available to receive the call as the master device 704 and the wearable device may be in sync with each other and the callee may be able to continue the call even in the power saving mode.

[0122] In another implementation, the first decision module 702C based on an input, provides as an output a call continuity through call forwarding when the wearable device 702 and the master device 704 have different eSIM numbers and are not connected with each other.

[0123] In another implementation, the first decision module 702C may as an output, based on an input, provides eSIM switching on the wearable device 702 based on a proximity and a context of the master device. For instance, when the wearable device 702 may not be in the proximity range of the master device i.e., the wearable device 702 may be out of the NFC range or untethered via say for e.g., a Bluetooth connectivity and / or a Wi-Fi connectivity, the first decision module 702C may allow automatically switching on the eSIM in the wearable device 702.

[0124] In another implementation, the first decision module 702C may as an output, based on an input, provide a decision to perform data transmission of various processes based on the context of the master device. For instance, the first decision module 702C decides on various SDT / non-SDT procedures contextually and based on a priority, such as the first decision module 702C may decide to perform a RRC connection resume procedure and to come in a connected state in an event of non-SDT procedure. In another instance in an event of a SDT procedure the first decision module 702C may decide to perform a random access (RA)-SDT when a configuration grant is not valid. In yet another instance in an event of a SDT procedure the first decision module 702C may decide to perform a CG-SDT based on Preconfigured Uplink Resources (PUR) periodicity, when a configuration grant is valid.

[0125] Further, the power saving module 702D is configured to use the eDRX sleep cycle -and the power saving sleep mode for reducing the power consumption on the wearable device 702 due to cellular paging. Further, the power saving module 702D, may be configured to handle the missed calls and may also provide call continuity on the wearable device 702 during the eDRX sleep cycle. The power saving module 702D may further comprise a power monitoring sub-module and a cellular eDRX and SDT sub-module. Further, the power monitoring sub-module may be configured to monitor the consumption of the power and the battery life in the wearable device 702 and the cellular eDRX and the SDT sub-module may be configured to implement the eDRX sleep cycle and CG-SDT timer.

[0126] Further, the power saving module 702D may use Small Data Transmission (SDT) procedure to communicate with the master device 704 when the wearable device 702 is in the idle state and may not go into the connected state if not necessary. The SDT may be used to send small amounts of data while remaining in the inactive state or the idle state. Further, the SDT is the procedure that allows a small amount of data and / or signaling transmission while the wearable device may remain in the inactive state / idle state without transitioning into the connected state. Further, the power saving module 702D may interact with the proximity modules, the communication modules and the decision modules in the wearable device 702 and the master device 704 to provide the call continuity in the eDRX sleep cycle.

[0127] Further, both the wearable device 702 and the master device 704 comprise communication modules, wherein the wearable device 702 may comprise the first communication module 702E and the master device 704 may comprise the second communication module 704E.

[0128] The first communication module 702E may be configured to receive from the first proximity module 702B, the notification to trigger the call continuity and the power saving mode in the wearable device 702. Further, the first communication module 702E may be used by the wearable device 702 to over the air communicate and negotiate eDRX cycle and the CG-SDT timers with network. The first communication module 702E may further be used by the wearable device 702 to send eDRX cycle to the master device 704 using the CG-SDT timer. Furthermore, the first communication module 702E may be used by the wearable device 702 to receive over the air, the transferred calls, notifications and / or messages etc. from the master device 704 after the wearable device 702 wakes up from the deep sleep mode.

[0129] The second communication module 704E may be used by the master device 704 to communicate and receive eDRX sleep cycle and CG-SDT timers of the wearable device 702 via OTA procedure. Furthermore, the second communication module 704E may be used to transmit calls, notifications and / or messages etc. from the master device 704 to the wearable device 702 based on the wake-up time of the wearable device 704 from the deep sleep cycle.

[0130] Thereafter, the wearable device 702 may comprise the first UI module 702H. The first UI module 702H may be configured to receive a UI prompt to notify the user to turn on the power saving mode while handling call continuity. Further, the first UI module 702H may provide the user via the UI, the options to set the eDRX sleep cycle and CG-SDT timer for negotiating with the network. Further, the first UI module 702H may receive the transferred calls, notifications and / or messages etc. from the master device to be shown on UI of the wearable device 702. Moreover, the second UI module 704H may be configured at the master device 704 to handle communication with the wearable device 702 via the SDT. Further, the second UI module 704H may receive the eDRX sleep cycle and the CG-SDT timers from the wearable device 702.

[0131] Further, referring to the FIG. 8that illustrates an exemplary signaling flow diagram for performing a small data transmission (SDT) by way of Configured Grant-Small Data Transmission (CG-SDT) for enabling a call connectivity in an eDRX cycle for a wearable device in accordance with the exemplary implementation of the disclosure.

[0132] For CG-SDT, radio resources are allocated periodically based on an estimation of the wearable device's traffic requirements. This uplink scheduling method is called Configured Grant (CG). In the CG-SDT procedure the radio resources are dedicated for the wearable device. The resource allocation is signalled to the wearable device by the network when the wearable device leaves the connected state.

[0133] Further as depicted in the FIG. 6, the wearable device initially may be in a RRC connected state. At step S1, the wearable device transmits a UE Assistance Information to the network. The UE Assistance Information may include Configured Grant (CG) request.

[0134] Further, at step S2, the network transmits the RRC release message with the suspended indication. The suspended indication includes CG configuration. Thereafter, the wearable device goes into the RRC inactive state from the connected state. At the wearable device during the RRC inactive state, a data in stored in a transmit (tx) buffer.

[0135] Next at step S3, the wearable device transmits to the network, the RRC resume request along with a payload data. The wearable device may transmit the data using SDT method if the amount of data in the tx buffer is less than a defined limit. Further, if the amount of data in the tx buffer is larger than the defined limit, then the data may be transmitted through a non-SDT method.

[0136] Thereafter, at step S4, the network may transmit the RRC release message with suspended indication to the wearable device and then the wearable device may remain in the RRC inactive state.

[0137] Furthermore, an aspect of the disclosure may relate to a system 100 for enabling a call connectivity in an extended-Discontinuous Reception (eDRX) cycle for a wearable device. The system comprises a processing unit 102; and a memory unit 104 connected to the processing unit 102. The processing unit 102 is configured to: 1) configure, by the wearable device, a Configured Grant- Small Data Transmission (CG-SDT) timer and an eDRX timer; 2) detect an expiry of the CG-SDT timer at the wearable device, wherein a connection mode of the wearable device is a deep sleep mode; 3) based on detection of the expiry of the CG-SDT timer, change the connection mode of the wearable device to an idle mode; 4) send, by the wearable device to a master device, a notification query request via a Small data transmission (SDT) protocol during the idle mode; 5) receive a notification query response at the wearable device from the master device; and 6) perform one or more changes in the connection mode at the wearable device based on the notification query response.

[0138] Also, another aspect of the disclosure may relate to a non-transitory computer readable storage medium storing instructions for enabling a call connectivity in an eDRX cycle for a wearable device, the instructions include executable code which, when executed by one or more units of the system 100, causes the processing unit 102 of the system 100 to configure, by the wearable device, a Configured Grant- Small Data Transmission (CG-SDT) timer and an eDRX time. Further, the executable code, when executed, causes the processing unit 102to detect an expiry of the CG-SDT timer at the wearable device, wherein a connection mode of the wearable device is a deep sleep mode. Further, the executable code, when executed, causes the processing unit 102 to change the connection mode of the wearable device to an idle mode, based on detection of the expiry of the CG-SDT timer. Further, the executable code, when executed, causes the processing unit 102 to send, by the wearable device to a master device, a notification query request via a Small data transmission (SDT) protocol during the idle mode. Further, the executable code, when executed, causes the processing unit 102 to receive a notification query response at the wearable device from the master device. Further, the executable code, when executed, causes the processing unit 102 to perform one or more changes in the connection mode at the wearable device based on the notification query response.

[0139] Therefore, the disclosure provides a technical solution for achieving a call continuity and a call connectivity in the wearable device in an efficient and effective manner. The present solution enables the call connectivity and the call continuity in an extended-Discontinuous Reception (eDRX) cycle for the wearable device. More specifically, the disclosure provides a solution for establishing at the wearable device, a cellular eDRX sleep cycle and a Configured Grant- Small Data Transmission (CG-SDT) timer. The solution as disclosed in the disclosure is technically advanced over the existing solutions as it provides a synchronisation of the eDRX cycle and the CG-SDT timer of the wearable device with the master device. The configuration of the eDRX sleep cycle on the wearable device reduces a power consumption in the wearable device in an efficient and effective manner.

[0140] According to embodiments, a method performed by a wearable device may comprise configuring a Configured Grant- Small Data Transmission (CG-SDT) timer and an extended discontinuous reception (eDRX) timer. The method may comprise detecting an expiry of the CG-SDT timer. The method may comprise based on detection of the expiry of the CG-SDT timer, changing a connection mode of the wearable device to an idle mode from a sleep mode. The method may comprise sending, to a master device connected to the wearable device, a notification query request via a Small data transmission (SDT) protocol during the idle mode. The method may comprise receiving, from the master device, a notification query response. The method may comprise performing one or more changes in the connection mode of the wearable device based on the notification query response.

[0141] In an embodiment, the notification query response may be one of a positive response and a negative response. The performing the one or more changes in the connection mode may further comprise one of changing the connection mode of the wearable device to a connected mode in an event of receipt of the positive response, and changing the connection mode of the wearable device to the sleep mode from the idle mode in an event of the receipt of the negative response.

[0142] In an embodiment, the configuring the CG-SDT timer and the eDRX timer may comprise sending, to a network, assistance information. The configuring the CG-SDT timer and the eDRX timer may comprise receiving, from the network, the CG-SDT timer and the eDRX timer. The configuring the CG-SDT timer and the eDRX timer may comprise syncing the CG-SDT timer and the eDRX timer with the master device.

[0143] In an embodiment, the method may comprise starting the CG-SDT timer based on the received CG-SDT timer from the network.

[0144] In an embodiment, the CG-SDT timer may be identified by a machine learning model. The machine learning model may be trained based on a battery usage history and a current battery level of the wearable device.

[0145] In an embodiment, the method may comprise receiving, from the master device, a notification to activate an Internet data connection on the wearable device based on a data call paging notification transmitted from a caller device to the master device.

[0146] In an embodiment, the method may comprise disabling a subscriber identity module (SIM) of the wearable device in an event of at least one of: an identification of a successful wireless connection between the wearable device and the master device, and an identification of a distance between the wearable device and the master device being within a proximity range.

[0147] In an embodiment, the notification query response may comprise a call notification.

[0148] In an embodiment, the method may comprise transferring a call associated with the call notification from the master device to the wearable device based on the performing the one or more changes that the connection mode of the wearable device is changed to a connected mode.

[0149] In an embodiment, the method may comprise sending, to the master device via the network, an uplink (UL) radio resource control (RRC) message and an UL data. The method may comprise receiving, from the network, a RRC release message along with data delivery acknowledgement from the master network related to syncing the eDRX timer and the CG-SDT timer.

[0150] In an embodiment, the method may comprise based on the receiving the notification query response comprising a call notification, transmitting, to the network, a RRC connection request, and receiving, from the network, a RRC connection accept response. The method may comprise performing the one or more changes in the connection mode that the connection mode of the wearable device is changed to a connected mode.

[0151] In an embodiment, the CG-SDT timer may be running while the connection mode of the wearable device is in the sleep mode.

[0152] In an embodiment, the idle mode may be identified based on an eDRX on duration according to the eDRX timer.

[0153] In an embodiment, while the connection mode of the wearable device is in the idle mode, communication circuitry of the wearable device may be switched on. While the connection mode of the wearable device is in the sleep mode, the communication circuitry may be switched off.

[0154] According to embodiments, a wearable device may comprise at least one processor including processing circuitry. The wearable device may comprise memory including one or more storage media storing instructions. The instructions, when executed by the at least one processor individually or collectively, may cause the wearable device to configure a Configured Grant- Small Data Transmission (CG-SDT) timer and an extended discontinuous reception (eDRX) timer. The instructions, when executed by the at least one processor individually or collectively, may cause the wearable device to detect an expiry of the CG-SDT timer. The instructions, when executed by the at least one processor individually or collectively, may cause the wearable device to based on detection of the expiry of the CG-SDT timer, change a connection mode of the wearable device to an idle mode from a sleep mode. The instructions, when executed by the at least one processor individually or collectively, may cause the wearable device to send, to a master device connected to the wearable device, a notification query request via a Small data transmission (SDT) protocol during the idle mode. The instructions, when executed by the at least one processor individually or collectively, may cause the wearable device to receive, from the master device, a notification query response. The instructions, when executed by the at least one processor individually or collectively, may cause the wearable device to perform one or more changes in the connection mode of the wearable device based on the notification query response.

[0155] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the disclosure. These and other changes in the implementations of the disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

Claims

1.A method performed by a wearable device, the method comprising:configuring a Configured Grant- Small Data Transmission (CG-SDT) timer and an extended discontinuous reception (eDRX) timer;detecting an expiry of the CG-SDT timer;based on detection of the expiry of the CG-SDT timer, changing a connection mode of the wearable device to an idle mode from a sleep mode;sending, to a master device connected to the wearable device, a notification query request via a Small data transmission (SDT) protocol during the idle mode;receiving, from the master device, a notification query response; andperforming one or more changes in the connection mode of the wearable device based on the notification query response.2.The method of claim 1, wherein the notification query response is one of a positive response and a negative response, andwherein the performing the one or more changes in the connection mode further comprises one of:changing the connection mode of the wearable device to a connected mode in an event of receipt of the positive response, andchanging the connection mode of the wearable device to the sleep mode from the idle mode in an event of the receipt of the negative response.3.The method of claim 1, wherein the configuring the CG-SDT timer and the eDRX timer comprises:sending, to a network, assistance information;receiving, from the network, the CG-SDT timer and the eDRX timer; andsyncing the CG-SDT timer and the eDRX timer with the master device.4.The method of claim 3, further comprising:starting the CG-SDT timer based on the received CG-SDT timer from the network.5.The method of claim 1, wherein the CG-SDT timer is identified by a machine learning model, andwherein the machine learning model is trained based on a battery usage history and a current battery level of the wearable device.6.The method of claim 3, further comprising:receiving, from the master device, a notification to activate an Internet data connection on the wearable device based on a data call paging notification transmitted from a caller device to the master device.7.The method of claim 1, further comprising:disabling a subscriber identity module (SIM) of the wearable device in an event of at least one of: an identification of a successful wireless connection between the wearable device and the master device, and an identification of a distance between the wearable device and the master device being within a proximity range.8.The method of claim 1, wherein the notification query response comprises a call notification.9.The method of claim 8, further comprises: transferring a call associated with the call notification from the master device to the wearable device based on the performing the one or more changes that the connection mode of the wearable device is changed to a connected mode.10.The method of claim 4, further comprises:sending, to the master device via the network, an uplink (UL) radio resource control (RRC) message and an UL data; andreceiving, from the network, a RRC release message along with data delivery acknowledgement from the master network related to syncing the eDRX timer and the CG-SDT timer.11.The method of claim 10, further comprises:based on the receiving the notification query response comprising a call notification:transmitting, to the network, a RRC connection request, andreceiving, from the network, a RRC connection accept response; andperforming the one or more changes in the connection mode that the connection mode of the wearable device is changed to a connected mode.12.The method of claim 1, wherein the CG-SDT timer is running while the connection mode of the wearable device is in the sleep mode.13.The method of claim 1, wherein the idle mode is identified based on an eDRX on duration according to the eDRX timer.14.The method of claim 1, wherein, while the connection mode of the wearable device is in the idle mode, communication circuitry of the wearable device is switched on, andwherein, while the connection mode of the wearable device is in the sleep mode, the communication circuitry is switched off.1.A wearable device, comprising:at least one processor including processing circuitry; andmemory including one or more storage media storing instructions,wherein the instructions, when executed by the at least one processor individually or collectively, cause the wearable device to:configure a Configured Grant- Small Data Transmission (CG-SDT) timer and an extended discontinuous reception (eDRX) timer,detect an expiry of the CG-SDT timer;based on detection of the expiry of the CG-SDT timer, change a connection mode of the wearable device to an idle mode from a sleep mode;send, to a master device connected to the wearable device, a notification query request via a Small data transmission (SDT) protocol during the idle mode;receive, from the master device, a notification query response; andperform one or more changes in the connection mode of the wearable device based on the notification query response.

Images